m Commands
ma-index-range
ma-index-range
Syntax
ma-index-range start ma-index end ma-index
no ma-index-range
Context
[Tree] (config>eth-cfm>md-auto-id ma-index-range)
Full Context
configure eth-cfm md-auto-id ma-index-range
Description
This command specifies the range of indexes used by SR OS to automatically assign an index to ETH-CFM associations that are created in model-driven interfaces without an index explicitly specified by the user or client.
An association created with an explicitly-specified index cannot use an index in this range. In classic CLI and SNMP, the ID range cannot be changed while objects exist inside the previous or new range. In MD interfaces, the range can be changed, which causes any previously existing objects in the previous ID range to be deleted and re-created using a new ID in the new range.
The no form of this command removes the range values.
See the md-auto-id command for further details.
Parameters
- start ma-index
-
Specifies the lower value of the index range. The value must be less than or equal to the end value.
- end ma-index
-
Specifies the upper value of the index range. The value must be greater than or equal to the start value.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
mac
mac
Syntax
mac ieee-address
no mac
Context
[Tree] (config>subscr-mgmt>loc-user-db>ipoe>host>host-ident mac)
[Tree] (config>subscr-mgmt>loc-user-db>ppp>host>host-ident mac)
Full Context
configure subscriber-mgmt local-user-db ipoe host host-identification mac
configure subscriber-mgmt local-user-db ppp host host-identification mac
Description
This command specifies the MAC address to match for a host lookup.
This command is only used when mac is configured as one of the match-list parameters.
The no form of this command removes the MAC address from the configuration.
Parameters
- ieee-address
-
Specifies the 48-bit MAC address in the form aa:bb:cc:dd:ee:ff or aa-bb-cc-dd-ee-ff where aa, bb, cc, dd, ee, and ff are hexadecimal numbers.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
mac
Syntax
[no] mac ieee-mac-address
Context
[Tree] (config>service>vprn>if>ipv6>vrrp mac)
[Tree] (config>service>vprn>if>vrrp mac)
[Tree] (config>service>vprn>sub-if>grp-if mac)
[Tree] (config>service>vprn>if>sap>eth-cfm>mep mac)
[Tree] (config>service>vprn>nw-if mac)
[Tree] (config>service>vprn>if mac)
Full Context
configure service vprn interface ipv6 vrrp mac
configure service vprn interface vrrp mac
configure service vprn subscriber-interface group-interface mac
configure service vprn interface sap eth-cfm mep mac
configure service vprn network-interface mac
configure service vprn interface mac
Description
This command assigns a specific MAC address to a VPRN IP interface.
The no form of this command returns the MAC address of the IP interface to the default value.
Default
The physical MAC address associated with the Ethernet interface on which the SAP is configured.
Parameters
- ieee-mac-address
-
Specifies the 48-bit MAC address for the static ARP in the form aa:bb:cc:dd:ee:ff or aa-bb-cc-dd-ee-ff where aa, bb, cc, dd, ee and ff are hexadecimal numbers. Allowed values are any non-broadcast, non-multicast MAC and non-IEEE reserved MAC addresses.
Platforms
All
- configure service vprn interface ipv6 vrrp mac
- configure service vprn network-interface mac
- configure service vprn interface mac
- configure service vprn interface vrrp mac
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
- configure service vprn subscriber-interface group-interface mac
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
- configure service vprn interface sap eth-cfm mep mac
mac
Syntax
[no] mac ieee-address
Context
[Tree] (debug>service>id>ppp mac)
Full Context
debug service id ppp mac
Description
This command shows PPP packets for the specified MAC address.
Parameters
- ieee-address
-
Sets debugging for the specified MAC address.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
mac
Syntax
[no] mac ieee-address
Context
[Tree] (config>service>vpls>mac-protect mac)
Full Context
configure service vpls mac-protect mac
Description
This command specifies the 48-bit IEEE 802.3 MAC address.
The no form of the command reverts to the default.
Parameters
- ieee-address
-
Specifies the 48-bit MAC address in the form aa:bb:cc:dd:ee:ff or aa-bb-cc-dd-ee-ff where aa, bb, cc, dd, ee, and ff are hexadecimal numbers.
Platforms
All
mac
Syntax
mac ieee-address
no mac [ieee-address]
Context
[Tree] (config>service>ies>if mac)
[Tree] (config>service>ies>sub-if>grp-if mac)
Full Context
configure service ies interface mac
configure service ies subscriber-interface group-interface mac
Description
This command assigns a specific MAC address to an IES IP interface.
For Routed Central Office (CO), a group interface has no IP address explicitly configured but inherits an address from the parent subscriber interface when needed. For example, a MAC will respond to an ARP request when an ARP is requested for one of the IPs associated with the subscriber interface through the group interface.
The no form of this command returns the MAC address of the IP interface to the default value.
Default
The physical MAC address associated with the Ethernet interface that the SAP is configured on (the default MAC address assigned to the interface, assigned by the system).
Parameters
- ieee-address
-
Specifies the 48-bit MAC address for the static ARP in the form aa:bb:cc:dd:ee:ff or aa-bb-cc-dd-ee-ff, where aa, bb, cc, dd, ee, and ff are hexadecimal numbers. Allowed values are any non-broadcast, non-multicast MAC and non-IEEE reserved MAC addresses.
Platforms
All
- configure service ies interface mac
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
- configure service ies subscriber-interface group-interface mac
mac
Syntax
mac ieee-address
no mac
Context
[Tree] (config>service>vpls>mcr-default-gtw mac)
Full Context
configure service vpls mcr-default-gtw mac
Description
This command relates to a system configured for Dual Homing in L2-TPSDA. It defines the MAC address used when the system sends out a gratuitous ARP on an active SAP after a ring heals or fails in order to attract traffic from subscribers on the ring with connectivity to that SAP.
The no form of this command reverts to the default.
Default
no mac
Parameters
- ieee-address
-
Specifies the address in xx:xx:xx:xx:xx:xx or xx-xx-xx-xx-xx-xx format (cannot be all zeros).
Platforms
All
mac
Syntax
mac ieee-address
no mac
Context
[Tree] (config>port>ethernet mac)
[Tree] (config>lag mac)
[Tree] (config>port>tdm>ds3 mac)
[Tree] (config>port>sonet-sdh>path mac)
[Tree] (config>port>tdm>ds1>channel-group mac)
[Tree] (config>port>tdm>e3 mac)
[Tree] (config>eth-tunnel mac)
[Tree] (config>port>tdm>e1>channel-group mac)
Full Context
configure port ethernet mac
configure lag mac
configure port tdm ds3 mac
configure port sonet-sdh path mac
configure port tdm ds1 channel-group mac
configure port tdm e3 mac
configure eth-tunnel mac
configure port tdm e1 channel-group mac
Description
This command assigns a specific MAC address to an Ethernet port, Link Aggregation Group (LAG), Ethernet tunnel, or BCP-enabled port or sub-port.
Only one MAC address can be assigned to a port. When multiple mac commands are entered, the last command overwrites the previous command. When the command is issued while the port is operational, IP will issue an ARP, if appropriate, and BPDUs are sent with the new MAC address.
The no form of this command returns the MAC address to the default value.
By default, a MAC address is assigned by the system from the chassis MAC address pool. The use of an all-zeroes MAC address indicates that an operational MAC address should be assigned from the chassis MAC address pool.
Default
mac 00:00:00:00:00:00
Parameters
- ieee-address
-
Specifies the 48-bit MAC address in the form aa:bb:cc:dd:ee:ff or aa-bb-cc-dd-ee-ff where aa, bb, cc, dd, ee and ff are hexadecimal numbers. Allowed values are any non-broadcast, non-multicast MAC and non-IEEE reserved MAC addresses.
Platforms
All
- configure port ethernet mac
- configure lag mac
7450 ESS, 7750 SR-7/12/12e, 7750 SR-a, 7750 SR-e
- configure port tdm e3 mac
- configure port tdm ds3 mac
- configure port tdm ds1 channel-group mac
- configure port tdm e1 channel-group mac
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
- configure port sonet-sdh path mac
- configure eth-tunnel mac
mac
Syntax
mac ieee-address
no mac
Context
[Tree] (config>eth-tunnel>ethernet mac)
Full Context
configure eth-tunnel ethernet mac
Description
This command assigns a specific MAC address to an Ethernet port, Link Aggregation Group (LAG), Ethernet tunnel, or BCP-enabled port or sub-port.
Only one MAC address can be assigned to a port. When multiple mac commands are entered, the last command overwrites the previous command. When the command is issued while the port is operational, IP will issue an ARP, if appropriate, and BPDUs are sent with the new MAC address.
The no form of this command returns the MAC address to the default value.
Default
no mac
Parameters
- ieee-address
-
Specifies the 48-bit MAC address in the form aa:bb:cc:dd:ee:ff or aa-bb-cc-dd-ee-ff where aa, bb, cc, dd, ee and ff are hexadecimal numbers. Allowed values are any non-broadcast, non-multicast MAC and non-IEEE reserved MAC addresses 6-byte unicast mac-address (xx:xx:xx:xx:xx:xx or xx-xx-xx-xx-xx-xx) of the MEP. Using the all zeros address is equivalent to the no form of this command.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
mac
Syntax
[no] mac ieee-address
Context
[Tree] (config>service>proxy-arp-nd>mac-list mac)
Full Context
configure service proxy-arp-nd mac-list mac
Description
This command configures the proxy ARP or ND MAC address information.
The no form of the command deletes the MAC address.
Parameters
- ieee-address
-
Specifies the MAC address added to the list. The MAC list can be empty or contain up to 10 addresses.
Platforms
All
mac
Syntax
mac ieee-address [create] black-holemac ieee-address [create] sap sap-id monitor {fwd-status}
mac ieee-address [create] spoke-sdp sdp-id:vc-id monitor {fwd-status}
no mac ieee-address
Context
[Tree] (config>service>vpls>static-mac mac)
Full Context
configure service vpls static-mac mac
Description
This command assigns a conditional static MAC address entry to an SPBM B-VPLS SAP/spoke-SDP allowing external MACs for single and multi-homed operation.
For the 7450 ESS or 7750 SR, this command also assigns a conditional static MAC address entry to an EVPN VPLS SAP/spoke-SDP.
Static MACs are used for PBB Epipe and I-VPLS services that may terminate external to SPBM. If this is configured under a Control B-VPLS the interface referenced will not use IS-IS for this neighbor. This may also be configured under a User B-VPLS where the corresponding interface is not supported under the Control B-VPLS.
Parameters
- ieee-address
-
Specifies the static MAC address to an SPBM/sdp-binding interface.
- sap-id
-
Specifies the SAP identifier.
- sdp-id
-
Specifies the SDP identifier.
- vc-id
-
Specifies the virtual circuit identifier.
- create
-
Mandatory keyword used to create a static MAC.
- fwd-status
-
Specifies that this static mac is based on the forwarding status of the SAP or spoke-SDP for multi-homed operation.
- black-hole
-
Specifies for TLS FDB entries defined on a local SAP the value 'sap', remote entries defined on an SDP have the value 'sdp'.
Platforms
All
mac
Syntax
[no] mac ieee-address
Context
[Tree] (config>service>ipipe>sap mac)
Full Context
configure service ipipe sap mac
Description
This command assigns a specific MAC address to an Ipipe SAP.
The no form of this command returns the MAC address of the SAP to the default value.
Default
The physical MAC address associated with the Ethernet interface where the SAP is configured.
Parameters
- ieee-address
-
Specifies the 48-bit MAC address in the form aa:bb:cc:dd:ee:ff or aa-bb-cc-dd-ee-ff where aa, bb, cc, dd, ee, and ff are hexadecimal numbers.
Platforms
All
mac
Syntax
mac mac-filter-id
no mac
Context
[Tree] (config>service>template>epipe-sap-template>egress>filter mac)
[Tree] (config>service>template>epipe-sap-template>ingress>filter mac)
Full Context
configure service template epipe-sap-template egress filter mac
configure service template epipe-sap-template ingress filter mac
Description
This command associates an existing MAC filter policy with the template.
This command is only supported in 'classic' configuration-mode (configure system management-interface configuration-mode classic).
Parameters
- mac-filter-id
-
Specifies the MAC filter policy. The specified filter ID must already exist within the created MAC filters. The filter policy must already exist within the created MAC filters.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
mac
Syntax
mac name
no mac
Context
[Tree] (config>service>template>epipe-sap-template>ingress>filter-name mac)
[Tree] (config>service>template>epipe-sap-template>egress>filter-name mac)
Full Context
configure service template epipe-sap-template ingress filter-name mac
configure service template epipe-sap-template egress filter-name mac
Description
This command associates an existing IP filter policy with the template.
Parameters
- name
-
Specifies the MAC filter policy name, up to 64 characters.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
mac
Syntax
mac ieee-address [mask six-byte-mask]
no mac ieee-address
Context
[Tree] (config>service>mac-list mac)
Full Context
configure service mac-list mac
Description
This command adds a protected MAC address entry.
The no form of this command removes the protected MAC address entry.
Parameters
- ieee-address
-
Specifies the address in xx:xx:xx:xx:xx:xx or xx-xx-xx-xx-xx-xx format (cannot be all zeros), up to 30 characters.
- six-byte-mask
-
Specifies the mask address in xx:xx:xx:xx:xx:xx or xx-xx-xx-xx-xx-xx format (cannot be all zeros), up to 30 characters.
Platforms
All
mac
Syntax
mac ieee-address
no mac
Context
[Tree] (config>service>vpls>interface mac)
Full Context
configure service vpls interface mac
Description
This command assigns a specific MAC address to a VPLS IP interface.
For Routed Central Office (CO), a group interface has no IP address explicitly configured but inherits an address from the parent subscriber interface when needed. For example, a MAC will respond to an ARP request when an ARP is requested for one of the IPs associated with the subscriber interface through the group interface.
The no form of this command returns the MAC address of the IP interface to the default value.
Default
mac
Parameters
- ieee-address
-
Specifies the 48-bit MAC address for the static ARP in the form aa:bb:cc:dd:ee:ff or aa-bb-cc-dd-ee-ff where aa, bb, cc, dd, ee, and ff are hexadecimal numbers. Allowed values are any non-broadcast, non-multicast MAC and non-IEEE reserved MAC addresses.
Platforms
All
mac
Syntax
mac name
no mac
Context
[Tree] (config>service>template>vpls-sap-template>ingress>filter-name mac)
[Tree] (config>service>template>vpls-sap-template>egress>filter-name mac)
Full Context
configure service template vpls-sap-template ingress filter-name mac
configure service template vpls-sap-template egress filter-name mac
Description
This command associates an existing IP filter policy with the template.
Parameters
- name
-
Specifies the MAC filter policy name, up to 64 characters.
Platforms
All
mac
Syntax
[no] mac ieee-address
Context
[Tree] (debug>service>id>arp-host mac)
Full Context
debug service id arp-host mac
Description
This command displays ARP host events for a particular MAC address.
Parameters
- mac-address
-
Specifies the 48-bit MAC address for the static ARP in the form aa:bb:cc:dd:ee:ff or aa-bb-cc-dd-ee-ff where aa, bb, cc, dd, ee, and ff are hexadecimal numbers. Allowed values are any non-broadcast, non-multicast MAC and non-IEEE reserved MAC addresses.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
mac
Syntax
[no] mac ieee-address
Context
[Tree] (debug>service>id>igmp-snooping mac)
Full Context
debug service id igmp-snooping mac
Description
This command shows IGMP packets for the specified MAC address.
The no form of this command disables the MAC debugging.
Platforms
All
mac
Syntax
[no] mac ieee-address
Context
[Tree] (debug>service>id>mld mac)
Full Context
debug service id mld-snooping mac
Description
This command shows MLD packets for the specified MAC address.
The no form of this command disables the MAC debugging.
Platforms
All
mac
Syntax
[no] mac ieee-address
Context
[Tree] (debug>service>id>host-connectivity-verify mac)
Full Context
debug service id host-connectivity-verify mac
Description
This command displays Subscriber Host Connectivity Verification (SHCV) events for a particular MAC address.
Parameters
- mac-address
-
Specifies the 48-bit MAC address for the static ARP in the form aa:bb:cc:dd:ee:ff or aa-bb-cc-dd-ee-ff where aa, bb, cc, dd, ee, and ff are hexadecimal numbers. Allowed values are any non-broadcast, non-multicast MAC and non-IEEE reserved MAC addresses.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
mac
Syntax
mac mac-address
no mac
Context
[Tree] (config>service>ies>if>ipv6>vrrp mac)
Full Context
configure service ies interface ipv6 vrrp mac
Description
This command assigns a specific MAC address to an IES IP interface.
The no form of this command returns the MAC address of the IP interface to the default value.
Default
The physical MAC address associated with the Ethernet interface that the SAP is configured on (the default MAC address assigned to the interface, assigned by the system).
Parameters
- mac-address
-
Specifies the 48-bit MAC address for the static ARP in the form aa:bb:cc:dd:ee:ff or aa-bb-cc-dd-ee-ff where aa, bb, cc, dd, ee, and ff are hexadecimal numbers. Allowed values are any non-broadcast, non-multicast MAC and non-IEEE reserved MAC addresses.
Platforms
All
mac
Syntax
mac mac-address
no mac
Context
[Tree] (config>service>ies>if>vrrp mac)
Full Context
configure service ies interface vrrp mac
Description
This command assigns a specific MAC address to an IES IP interface.
The no form of this command returns the MAC address of the IP interface to the default value.
Default
The physical MAC address associated with the Ethernet interface that the SAP is configured on (the default MAC address assigned to the interface, assigned by the system).
Parameters
- mac-address
-
Specifies the 48-bit MAC address for the static ARP in the form aa:bb:cc:dd:ee:ff or aa-bb-cc-dd-ee-ff, where aa, bb, cc, dd, ee, and ff are hexadecimal numbers. Allowed values are any non-broadcast, non-multicast MAC and non-IEEE reserved MAC addresses.
Platforms
All
mac
Syntax
mac ieee-address
no mac
Context
[Tree] (config>router>if mac)
Full Context
configure router interface mac
Description
This command assigns a specific MAC address to an IP interface. Only one MAC address can be assigned to an IP interface. When multiple mac commands are entered, the last command overwrites the previous command.
The no form of this command returns the MAC address of the IP interface to the default value.
Default
no mac
Parameters
- ieee-address
-
Specifies the 48-bit MAC address for the IP interface in the form aa:bb:cc:dd:ee:ff or aa-bb-cc-dd-ee-ff, where aa, bb, cc, dd, ee and ff are hexadecimal numbers. Allowed values are any non-broadcast, non-multicast MAC and non-IEEE reserved MAC addresses.
Platforms
All
mac
Syntax
mac mac-address
no mac
Context
[Tree] (config>router>if>vrrp mac)
[Tree] (config>router>if>ipv6>vrrp mac)
Full Context
configure router interface vrrp mac
configure router interface ipv6 vrrp mac
Description
This command sets an explicit MAC address used by the virtual router instance overriding the VRRP default derived from the VRID.
Changing the default MAC address is useful when an existing HSRP or other non-VRRP default MAC is in use by the IP hosts using the virtual router IP address. Many hosts do not monitor unessential ARPs and continue to use the cached non-VRRP MAC address after the virtual router becomes master of the host’s gateway address.
The mac command sets the MAC address used in ARP responses when the virtual router instance is master. Routing of IP packets with mac-address as the destination MAC is also enabled. The mac setting must be the same for all virtual routers participating as a virtual router or indeterminate connectivity by the attached IP hosts will result. All VRRP advertisement messages are transmitted with mac-address as the source MAC.
The command can be configured in both non-owner and owner vrrp nodal contexts.
The mac command can be executed at any time and takes effect immediately. When the virtual router MAC on a master virtual router instance changes, a gratuitous ARP is immediately sent with a VRRP advertisement message. If the virtual router instance is disabled or operating as backup, the gratuitous ARP and VRRP advertisement message is not sent.
The no form of the command restores the default VRRP MAC address to the virtual router instance.
Default
no mac
Parameters
- mac-address
-
The 48-bit MAC address for the virtual router instance in the form aa:bb:cc:dd:ee:ff or aa-bb-cc-dd-ee-ff where aa, bb, cc, dd, ee and ff are hexadecimal numbers. Allowed values are any non-broadcast, non-multicast MAC, and non-IEEE reserved MAC addresses.
Platforms
All
mac
Syntax
mac index name mac-name
no mac index
Context
[Tree] (config>system>security>ssh>client-mac-list mac)
[Tree] (config>system>security>ssh>server-mac-list mac)
Full Context
configure system security ssh client-mac-list mac
configure system security ssh server-mac-list mac
Description
This command configures SSH MAC algorithms for SR OS as an SSH server or an SSH client.
The no form of this command removes the specified mac index.
Default
no mac index
Parameters
- index
-
Specifies the index of the algorithm in the list.
- mac-name
-
Specifies the algorithm for calculating the message authentication code.
Platforms
All
mac
Syntax
mac mac-id [create]
no mac mac-id
Context
[Tree] (config>card>mda>xconnect mac)
[Tree] (config>card>xiom>mda>xconnect mac)
Full Context
configure card mda xconnect mac
configure card xiom mda xconnect mac
Description
This command creates a loopback in the MAC chip. It does not require the allocation of a faceplate. After the loopback is instantiated, a PXC can be configured on top of it.
For a list of MAC chip IDs per forwarding complex (datapath), use the show datapath datapath-id datapath-id command.
When considering loopback creation, the operation should consider the MAC chip’s bandwidth capacity and the bandwidth utilization of all the faceplate ports connected to it.The selection of MAC chips for loopback creation should be taken into consideration.
The no form of this command removes the MAC ID from the configuration.
Parameters
- mac-id
-
Specifies the MAC ID.
- create
-
Keyword used to create the MAC ID instance. The create keyword requirement can be enabled or disabled in the environment>create context.
Platforms
7450 ESS, 7750 SR, 7750 SR-s, 7950 XRS
- configure card mda xconnect mac
7750 SR-1s, 7750 SR-2s, 7750 SR-7s, 7750 SR-14s
- configure card xiom mda xconnect mac
mac-address
mac-address
Syntax
[no] mac-address
Context
[Tree] (config>subscr-mgmt>acct-plcy>include-radius-attribute mac-address)
[Tree] (config>subscr-mgmt>auth-policy>include-radius-attribute mac-address)
Full Context
configure subscriber-mgmt radius-accounting-policy include-radius-attribute mac-address
configure subscriber-mgmt authentication-policy include-radius-attribute mac-address
Description
This command enables the generation of the client MAC address RADIUS attribute.
The no form of this command disables the generation of the client MAC address RADIUS attribute.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
mac-address
Syntax
mac-address ieee-address
no mac-address
Context
[Tree] (config>subscr-mgmt>wlan-gw>ue-query mac-address)
Full Context
configure subscriber-mgmt wlan-gw ue-query mac-address
Description
This command enables matching on UEs with the specified MAC address.
The no form of this command disables matching on the MAC address.
Default
no mac-address
Parameters
- ieee-address
-
Specifies the ethernet MAC address.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
mac-address
Syntax
mac-address mac-address
no mac-address
Context
[Tree] (config>eth-tunnel>path>eth-cfm>mep mac-address)
[Tree] (config>eth-ring>path>eth-cfm>mep mac-address)
Full Context
configure eth-tunnel path eth-cfm mep mac-address
configure eth-ring path eth-cfm mep mac-address
Description
This command specifies the MAC address of the MEP.
The no form of this command reverts the MAC address of the MEP back to that of the port (if the MEP is on a SAP) or the bridge (if the MEP is on a spoke SDP).
Parameters
- mac-address
-
Specifies the MAC address of the MEP.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
mac-address
Syntax
mac-address mac-address
no mac-address
Context
[Tree] (config>lag>eth-cfm>mep mac-address)
[Tree] (config>router>if>eth-cfm>mep mac-address)
[Tree] (config>port>ethernet>eth-cfm>mep mac-address)
Full Context
configure lag eth-cfm mep mac-address
configure router interface eth-cfm mep mac-address
configure port ethernet eth-cfm mep mac-address
Description
This command specifies the MAC address of the MEP.
The no form of this command reverts to the MAC address of the MEP back to the default, that of the port, since this is SAP based.
Default
no mac-address
Parameters
- mac-address
-
Specifies the MAC address of the MEP.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
mac-address
Syntax
mac-address mac-address
no mac-address
Context
[Tree] (config>service>epipe>spoke-sdp>eth-cfm>mep mac-address)
Full Context
configure service epipe spoke-sdp eth-cfm mep mac-address
Description
This command specifies the MAC address of the MEP.
The no form of this command reverts the MAC address of the MEP back to that of the port (if the MEP is on a SAP) or the bridge (if the MEP is on a spoke).
Parameters
- mac-address
-
Specifies the MAC address of the MEP.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
mac-address
Syntax
mac-address mac-address
no mac-address
Context
[Tree] (config>service>vpls>mesh-sdp>eth-cfm>mep mac-address)
[Tree] (config>service>vpls>spoke-sdp>eth-cfm>mep mac-address)
[Tree] (config>service>vpls>sap>eth-cfm>mep mac-address)
[Tree] (config>service>vpls>eth-cfm>mep mac-address)
Full Context
configure service vpls mesh-sdp eth-cfm mep mac-address
configure service vpls spoke-sdp eth-cfm mep mac-address
configure service vpls sap eth-cfm mep mac-address
configure service vpls eth-cfm mep mac-address
Description
This command specifies the MAC address of the MEP.
The no form of this command reverts the MAC address of the MEP back to that of the port (if the MEP is on a SAP) or the bridge (if the MEP is on a spoke).
Parameters
- mac-address
-
Specifies the MAC address of the MEP
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
mac-address
Syntax
mac-address mac-address
Context
[Tree] (config>service>vprn>if>sap>eth-cfm>mep mac-address)
[Tree] (config>service>vprn>if>spoke-sdp>eth-cfm>mep mac-address)
[Tree] (config>service>vprn>sub-if>grp-if>sap>eth-cfm mac-address)
Full Context
configure service vprn interface sap eth-cfm mep mac-address
configure service vprn interface spoke-sdp eth-cfm mep mac-address
configure service vprn subscriber-interface group-interface sap eth-cfm mac-address
Description
This command assigns a specific MAC address to an IP interface.
The no form of this command returns the MAC address of the IP interface to the default value.
Default
The physical MAC address associated with the Ethernet interface that the SAP is configured on.
Parameters
- mac-address
-
Specifies the 48-bit MAC address for the static ARP in the form aa:bb:cc:dd:ee:ff or aa-bb-cc-dd-ee-ff where aa, bb, cc, dd, ee and ff are hexadecimal numbers. Allowed values are any non-broadcast, non-multicast MAC and non-IEEE reserved MAC addresses.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
- configure service vprn interface spoke-sdp eth-cfm mep mac-address
- configure service vprn interface sap eth-cfm mep mac-address
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s
- configure service vprn subscriber-interface group-interface sap eth-cfm mac-address
mac-address
Syntax
[no] mac-address
Context
[Tree] (config>aaa>isa-radius-plcy>auth-include-attributes mac-address)
[Tree] (config>aaa>isa-radius-plcy>acct-include-attributes mac-address)
Full Context
configure aaa isa-radius-policy auth-include-attributes mac-address
configure aaa isa-radius-policy acct-include-attributes mac-address
Description
This command enables the generation of the client MAC address RADIUS attribute.
Default
no mac-address
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
mac-address
Syntax
mac-address mac-address
no mac-address
Context
[Tree] (config>system>satellite>tdm-sat mac-address)
[Tree] (config>system>satellite>eth-sat mac-address)
Full Context
configure system satellite tdm-sat mac-address
configure system satellite eth-sat mac-address
Description
This command configures the MAC address for the associated satellite chassis. This MAC address is used to validate the identity of an satellite that attempts to associate with the local host.
The no form of the command deletes the MAC address for the associated satellite.
Parameters
- mac-address
-
Specifies the MAC address of the associated satellite chassis; do not use a broadcast or multicast MAC. Enter the MAC address in either of the following formats: xx:xx:xx:xx:xx:xx or xx-xx-xx-xx-xx-xx.
Platforms
7450 ESS, 7750 SR-7/12/12e, 7750 SR-a, 7750 SR-e
- configure system satellite tdm-sat mac-address
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
- configure system satellite eth-sat mac-address
mac-address
Syntax
mac-address ieee-address
no mac-address ieee-address
Context
[Tree] (config>port>ethernet>dot1x>per-host-authentication>allowed-source-macs mac-address)
Full Context
configure port ethernet dot1x per-host-authentication allowed-source-macs mac-address
Description
This command configures the host MAC address on the allowed MAC list.
The no form of the command deletes the MAC address from the list.
Default
no mac
Parameters
- ieee-address
-
Specifies the MAC address.
Platforms
All
mac-advertisement
mac-advertisement
Syntax
[no] mac-advertisement
Context
[Tree] (config>service>vpls>bgp-evpn mac-advertisement)
Full Context
configure service vpls bgp-evpn mac-advertisement
Description
This command enables the advertisement in BGP of the learned macs on SAPs and SDP bindings. When the mac-advertisement is disabled, the local macs will be withdrawn in BGP.
Default
mac-advertisement
Platforms
All
mac-criteria
mac-criteria
Syntax
[no] mac-criteria
Context
[Tree] (config>qos>sap-ingress mac-criteria)
Full Context
configure qos sap-ingress mac-criteria
Description
This command is used to enter the node to create or edit policy entries that specify MAC criteria.
The mac-criteria based SAP ingress policies are used to select the appropriate ingress queue and corresponding forwarding class for matched traffic.
Router implementation will exit on the first match found and execute the actions in accordance with the accompanying action command. For this reason, entries must be sequenced correctly from most to least explicit.
The no form of this command deletes all the entries specified under this node. When mac-criteria entries are removed from a SAP ingress policy, the mac-criteria is removed from all services where that policy is applied.
Platforms
All
mac-da-hashing
mac-da-hashing
Syntax
[no] mac-da-hashing
Context
[Tree] (config>subscr-mgmt>msap-policy>vpls-only mac-da-hashing)
Full Context
configure subscriber-mgmt msap-policy vpls-only-sap-parameters mac-da-hashing
Description
This command specifies whether subscriber traffic egressing a LAG SAP has its egress LAG link selected by a function of the MAC destination address instead of the subscriber ID.
This command is only meaningful if subscriber management is enabled and can be configured for a VPLS service.
The no form of this command reverts to the default.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
mac-da-hashing
Syntax
mac-da-hashing
no mac-da-hashing
Context
[Tree] (config>service>vpls>sap>sub-sla-mgmt mac-da-hashing)
Full Context
configure service vpls sap sub-sla-mgmt mac-da-hashing
Description
This command specifies whether subscriber traffic egressing a LAG SAP has its egress LAG link selected by a function of the MAC destination address instead of the subscriber ID.
The no form of this command reverts to the default setting.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
mac-duplication
mac-duplication
Syntax
mac-duplication
Context
[Tree] (config>service>vpls>bgp-evpn mac-duplication)
Full Context
configure service vpls bgp-evpn mac-duplication
Description
Commands in this context configure the BGP EVPN MAC duplication parameters.
Platforms
All
mac-filter
mac-filter
Syntax
mac-filter mac-filter-id entry entry-id [entry-id]
no mac-filter mac-filter-id [entry entry-id]
Context
[Tree] (config>mirror>mirror-source mac-filter)
Full Context
configure mirror mirror-source mac-filter
Description
This command enables mirroring of packets that match specific entries in an existing MAC filter.
The mac-filter command directs packets which match the defined list of entry IDs to be mirrored to the mirror destination referenced by the mirror-dest-service-id of the mirror-source.
The MAC filter must already exist in order for the command to execute. Filters are configured in the config>filter context. If the MAC filter does not exist, an error will occur. If the filter exists but has not been associated with a SAP or IP interface, an error is not be generated but mirroring will not be enabled (there are no packets to mirror). Once the filter is defined to a SAP or MAC interface, mirroring is enabled.
If the MAC filter is defined as ingress, only ingress packets are mirrored. Ingress mirrored packets are mirrored to the mirror destination prior to any ingress packet modifications.
If the MAC filter is defined as egress, only egress packets are mirrored. Egress mirrored packets are mirrored to the mirror destination after all egress packet modifications.
An entry-id within a MAC filter can only be mirrored to a single mirror destination. If the same entry-id is defined multiple times, an error occurs and only the first mirror-source definition is in effect.
By default, no packets matching any MAC filters are mirrored. Mirroring of MAC filter entries must be explicitly defined.
The no form of this command, without the entry keyword, removes mirroring on all entry-id’s within the mac-filter-id.
When the no command is executed with the entry keyword and one or more entry-id’s, mirroring of that list of entry-id’s is terminated within the mac-filter-id. If an entry-id is listed that does not exist, an error will occur and the command will not execute. If an entry-id is listed that is not currently being mirrored, no error will occur for that entry-id and the command will execute normally.
Parameters
- mac-filter-id
-
Specifies the MAC filter ID whose entries are mirrored. If the mac-filter-id does not exist, an error will occur and the command will not execute. Mirroring of packets will commence once the mac-filter-id is defined on a SAP.
- entry-id
-
Specifies the MAC filter entries to use as match criteria for packet mirroring. The entry keyword begins a list of entry-id’s for mirroring. Multiple entry-id entries may be specified with a single command. Each entry-id must be separated by a space. Up to 8 entry IDs may be specified in a single command.
Each entry-id must exist within the mac-filter-id. If the entry-id is renumbered within the MAC filter definition, the old entry-id is removed from the list and the new entry-id will need to be manually added to the list if mirroring is still desired.
If no entry-id entries are specified in the command, mirroring will not occur for that MAC filter ID. The command will have no effect.
Platforms
All
mac-filter
Syntax
[no] mac-filter mac-filter-id
Context
[Tree] (config>li>li-filter-block-reservation>li-reserved-block mac-filter)
Full Context
configure li li-filter-block-reservation li-reserved-block mac-filter
Description
This command configures to which normal MAC filters the entry reservation is applied.
This command is only supported in 'classic' configuration-mode (configure system management-interface configuration-mode classic).
Parameters
- mac-filter-id
-
Specifies the filter identification identifies the normal MAC filters.
Platforms
All
mac-filter
Syntax
[no] mac-filter mac-filter-id
Context
[Tree] (config>li>li-filter-assoc>li-mac-fltr mac-filter)
Full Context
configure li li-filter-associations li-mac-filter mac-filter
Description
Specifies the MAC filter(s) into which the entries from the specified li-mac-filter are to be inserted. The li-mac-filter and mac-filter must already exist before the association is made. If the normal MAC filter is deleted then the association is also removed (and not re-created if the MAC filter comes into existence in the future).
The no form of this command removes the MAC filter ID from the configuration.
Parameters
- mac-filter-id
-
Specifies a filter identification to identify the MAC filter.
Platforms
All
mac-filter
Syntax
mac-filter mac-filter-id entry entry-id [entry-id] [ intercept-id intercept-id [intercept-id]] [session-id [session-id] [[session-id]]]
no mac-filter mac-filter-id
Context
[Tree] (config>li>li-source mac-filter)
Full Context
configure li li-source mac-filter
Description
This command enables lawful interception (LI) of packets that match specific entries in an existing MAC filter. Multiple entries can be created using unique entry-id numbers within the filter. The router implementation exits the filter on the first match found and executes the actions in accordance with the accompanying action command. For this reason, entries must be sequenced correctly from most to least explicit.
An entry may not have any match criteria defined (in which case, everything matches) but must have at least the keyword action for it to be considered complete. Entries without the action keyword will be considered incomplete and hence will be rendered inactive.
An entry-id within an MAC filter can only be intercepted to a single destination. If the same entry-id is defined multiple times, an error occurs and only the first definition is in effect.
The no form of this command removes the specified entry from the IP or MAC filter. Entries removed from the IP or MAC filter are immediately removed from all services or network ports where that filter is applied.
Parameters
- mac-filter-id
-
Specifies the MAC filter ID. If the mac-filter-id does not exist, an error will occur and the command will not execute.
- entry-id
-
The MAC filter entries to use as match criteria.
- intercept-id
-
Specifies the intercept-id that is inserted into the packet header for all mirrored packets of the associated li-source entry. This intercept-id can be used (for example by a downstream LI gateway) to identify the particular LI session to which the packet belongs. For all types of li-source entries (filter, nat, sap, subscriber), when the mirror service is configured with ip-udp-shim routable encap, an intercept-id field (as part of the routable encap) is always present in the mirrored packets. If there is no intercept-id configured for an li-source entry, then the default value will be inserted. When the mirror service is configured with ip-gre routable encap, no intercept-id is inserted and none should be specified against the li-source entries.
- session-id
-
Specifies the session-id that is inserted into the packet header for all mirrored packets of the associated li-source entry. This session-id can be used (for example by a downstream LI gateway) to identify the particular LI session to which the packet belongs. The session-id is only valid and used for mirror services that are configured with ip-udp-shim routable encap (config>mirror>mirror-dest>encap>ip-udp-shim). For all types of li-source entries (filter, nat, sap, or subscriber), when the mirror service is configured with ip-udp-shim routable encap, a session-id field (as part of the routable encap) is always present in the mirrored packets. If there is no session-id configured for an li-source entry, then the default value will be inserted. When a mirror service is configured with ip-gre routable encap, no session-id is inserted and none should be specified against the li-source entries.
Platforms
All
mac-filter
Syntax
mac-filter mac-filter-id entry entry-id [entry-id]
no mac-filter mac-filter-id [entry entry-id]
Context
[Tree] (debug>mirror-source mac-filter)
Full Context
debug mirror-source mac-filter
Description
This command enables mirroring of packets that match specific entries in an existing MAC filter.
The mac-filter command directs packets which match the defined list of entry IDs to be mirrored to the mirror destination referenced by the mirror-dest-service-id of the mirror-source.
The MAC filter must already exist in order for the command to execute. Filters are configured in the config>filter context. If the MAC filter does not exist, an error will occur. If the filter exists but has not been associated with a SAP or IP interface, an error is not be generated but mirroring will not be enabled (there are no packets to mirror). Once the filter is defined to a SAP or MAC interface, mirroring is enabled.
If the MAC filter is defined as ingress, only ingress packets are mirrored. Ingress mirrored packets are mirrored to the mirror destination prior to any ingress packet modifications.
If the MAC filter is defined as egress, only egress packets are mirrored. Egress mirrored packets are mirrored to the mirror destination after all egress packet modifications.
An entry-id within a MAC filter can only be mirrored to a single mirror destination. If the same entry-id is defined multiple times, an error occurs and only the first mirror-source definition is in effect.
By default, no packets matching any MAC filters are mirrored. Mirroring of MAC filter entries must be explicitly defined.
The no form of this command command, without the entry keyword, removes mirroring on all entry-id’s within the mac-filter-id.
When the no command is executed with the entry keyword and one or more entry-id’s, mirroring of that list of entry-id’s is terminated within the mac-filter-id. If an entry-id is listed that does not exist, an error will occur and the command will not execute. If an entry-id is listed that is not currently being mirrored, no error will occur for that entry-id and the command will execute normally.
Parameters
- mac-filter-id
-
Specifies the MAC filter ID whose entries are mirrored. If the mac-filter-id does not exist, an error will occur and the command will not execute. Mirroring of packets will commence once the mac-filter-id is defined on a SAP.
- entry-id
-
Specifies the MAC filter entries to use as match criteria for packet mirroring. The entry keyword begins a list of entry-id’s for mirroring. Multiple entry-id entries may be specified with a single command. Each entry-id must be separated by a space. Up to 8 entry IDs may be specified in a single command.
Each entry-id must exist within the mac-filter-id. If the entry-id is renumbered within the MAC filter definition, the old entry-id is removed from the list and the new entry-id will need to be manually added to the list if mirroring is still desired.
If no entry-id entries are specified in the command, mirroring will not occur for that MAC filter ID. The command will have no effect.
Platforms
All
mac-filter
Syntax
mac-filter filter-id [create] [ name name]
mac-filter {filter-id | filter-name}
no mac-filter {filter-id | filter-name}
Context
[Tree] (config>filter mac-filter)
Full Context
configure filter mac-filter
Description
This command creates a configuration context for the specified MAC filter policy.
The no form of the command deletes the MAC filter policy. A filter policy cannot be deleted until it is removed from all objects where it is applied.
Parameters
- filter-id
-
Specifies the MAC filter policy ID expressed as a decimal integer.
- create
-
Keyword required to create the configuration context. After it is created, the context can be enabled with or without the create keyword.
- name
-
Sets an optional filter name, up to 64 characters in length, to a given filter. This filter name can then be used in configuration references, display, and show commands throughout the system. A defined filter name can help the service provider or administrator to identify and manage filters within the SR OS platforms.
To create a filter, you must assign a filter ID, however, after it is created, either the filter ID or filter name can be used to identify and reference a filter.
If a name is not specified at creation time, then SR OS assigns a string version of the filter-id as the name.
Filter names may not begin with an integer (0 to 9).
- filter-name
-
Specifies a string of up to 64 characters uniquely identifying this MAC filter policy.
Platforms
All
mac-filter
Syntax
[no] mac-filter
Context
[Tree] (config>system>security>mgmt-access-filter mac-filter)
Full Context
configure system security management-access-filter mac-filter
Description
This command configures a management access MAC-filter.
Platforms
All
mac-filter
Syntax
[no] mac-filter
Context
[Tree] (config>system>security>cpm-filter mac-filter)
Full Context
configure system security cpm-filter mac-filter
Description
Commands in this context configure CPM MAC-filter parameters.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
mac-filter
Syntax
ip-filter src-filter-id [src-entry src-entry-id] to dst-filter-id [dst-entry dst-entry-id] [overwrite]
Context
[Tree] (config>filter>copy mac-filter)
Full Context
configure filter copy mac-filter
Description
This command copies an existing filter entry for a specific filter ID to another filter ID. The copy command is a configuration level maintenance tool used to create new entries using an existing filter policy. If overwrite is not specified, an error will occur if the destination filter entry exists.
Parameters
- src-filter-id
-
Specifies the source filter policy from which the copy command will attempt to copy. The filter policy must exist within the context of the preceding keyword (mac-filter).
- dst-filter-id
-
Specifies the destination filter policy to which the copy command will attempt to copy. If the overwrite keyword is not specified, the filter entry ID cannot already exist in the destination filter policy. If the overwrite keyword is present, the destination entry ID may or may not exist.
- overwrite
-
Specifies that the destination filter entry may exist. If it does, everything in the existing destination filter entry will be completely overwritten with the contents of the source filter entry. If the destination filter entry exists, either overwrite must be specified or an error message will be returned. If overwrite is specified, the function of copying from source to destination occurs in a ‟break before make” manner and therefore should be handled with care.
Platforms
All
mac-filter-name
mac-filter-name
Syntax
[no] mac-filter-name filter-name
Context
[Tree] (config>li>li-filter-block-reservation>li-reserved-block mac-filter-name)
Full Context
configure li li-filter-block-reservation li-reserved-block mac-filter-name
Description
This command configures a MAC filter in which the reservation is done through name.
The no form of this command removes the MAC filter name.
Parameters
- filter-name
-
Specifies the MAC filter name, up to 64 characters.
Platforms
All
mac-filter-name
Syntax
[no] mac-filter-name filter-name
Context
[Tree] (config>li>li-filter-assoc>li-mac-fltr mac-filter-name)
Full Context
configure li li-filter-associations li-mac-filter mac-filter-name
Description
This command associates a MAC filter with a specified LI MAC filter through its name.
The no form of this command removes the MAC filter name.
Parameters
- filter-name
-
Specifies the MAC filter name, up to 64 characters.
Platforms
All
mac-format
mac-format
Syntax
mac-format format
no mac-format
Context
[Tree] (config>subscr-mgmt>loc-user-db>ipoe>host>match-radprox-cache mac-format)
Full Context
configure subscriber-mgmt local-user-db ipoe host match-radius-proxy-cache mac-format
Description
This command specifies the format of MAC address used for matching incoming DHCP DISCOVER against the RADIUS proxy cache.
The no form of this command reverts to the default.
Default
mac-format "aa:"
Parameters
- format
-
Specifies the format string that specifies the format of MAC address.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
mac-format
Syntax
mac-format mac-format
no mac-format
Context
[Tree] (config>subscr-mgmt>diam-appl-plcy>nasreq mac-format)
[Tree] (config>subscr-mgmt>diam-appl-plcy>gy mac-format)
[Tree] (config>subscr-mgmt>diam-appl-plcy>gx mac-format)
Full Context
configure subscriber-mgmt diameter-application-policy nasreq mac-format
configure subscriber-mgmt diameter-application-policy gy mac-format
configure subscriber-mgmt diameter-application-policy gx mac-format
Description
This command configures the format of the MAC address when reported in Gx, Gy, or NASREQ application message AVPs such as Calling-Station-Id or User-Name.
The no form of this command resets the command to the default setting.
Default
mac-format ab
Parameters
- mac-format
-
Specifies the MAC address format.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
mac-format
Syntax
mac-format mac-format
no mac-format
Context
[Tree] (config>service>ies>sub-if>grp-if>wlan-gw>ranges>range>track-mobility mac-format)
[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw>ranges>range>track-mobility mac-format)
Full Context
configure service ies subscriber-interface group-interface wlan-gw vlan-tag-ranges range track-mobility mac-format
configure service vprn subscriber-interface group-interface wlan-gw vlan-tag-ranges range track-mobility mac-format
Description
This command configures how the MAC address is represented by the RADIUS proxy server.
Default
no mac-format "aa:"
Parameters
- mac-format
-
Specifies how the MAC address is represented by the RADIUS proxy server.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
mac-learning-options
mac-learning-options
Syntax
[no] mac-learning-options
Context
[Tree] (config>service>vprn>sub-if>grp-if>sap>static-host-mgmt mac-learning-options)
[Tree] (config>service>ies>sub-if>grp-if>sap>static-host-mgmt mac-learning-options)
Full Context
configure service vprn subscriber-interface group-interface sap static-host-mgmt mac-learning-options
configure service ies subscriber-interface group-interface sap static-host-mgmt mac-learning-options
Description
This command configures additional methods by which the BNG learns the subscriber host MAC.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
mac-linking
mac-linking
Syntax
mac-linking ip-address
no mac-linking
Context
[Tree] (config>service>vprn>sub-if>grp-if>sap>static-host mac-linking)
[Tree] (config>service>ies>sub-if>grp-if>sap>static-host mac-linking)
Full Context
configure service vprn subscriber-interface group-interface sap static-host mac-linking
configure service ies subscriber-interface group-interface sap static-host mac-linking
Description
This command associates this IPv6 host to the specified IPv4 host through the learned MAC address. A learned MAC from the IPv6 host is associated with the IPv4 host and vice versa.
The no form of this command removes the IP address from the configuration.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
mac-list
mac-list
Syntax
mac-list name [create]
no mac-list name
Context
[Tree] (config>service>proxy-arp-nd mac-list)
Full Context
configure service proxy-arp-nd mac-list
Description
This command creates a list of MAC addresses that can be pointed at from the service for a specified IP. The list may contain up to 10 MAC addresses; an empty list is also allowed.
The MAC list allows on-the-fly changes, but a change in the list deletes the proxy entries for all the IPs using that list.
The no form of the command deletes the entire MAC-list. Deleting a MAC list is only possible if it is not referenced in the configuration.
Parameters
- name
-
Specifies the name of the MAC address list, which can be up to 32 characters.
- create
-
Mandatory keyword to create a MAC list.
Platforms
All
mac-list
Syntax
mac-list name
no mac-list
Context
[Tree] (config>service>vpls>proxy-nd>dynamic mac-list)
[Tree] (config>service>vpls>proxy-arp>dynamic mac-list)
Full Context
configure service vpls proxy-nd dynamic mac-list
configure service vpls proxy-arp dynamic mac-list
Description
This command associates a previously created MAC list to a dynamic IP. The MAC list is created using the configure service proxy-arp-nd mac-list command.
The no form of the command deletes the association of the MAC list and the dynamic IP.
Parameters
- name
-
Specifies the name of the MAC list previously created using the configure service proxy-arp-nd mac-list command.
Platforms
All
mac-list
Syntax
mac-list name [create]
no mac-list name
Context
[Tree] (config>service mac-list)
Full Context
configure service mac-list
Description
This command configures a MAC list name. The MAC list is composed of a list of MAC addresses and masks, which along with Auto-Learn Mac Protect (ALMP) can be used to exclude certain MACs from being protected in a given object. This is typically used on SAPs and spoke SDPs configured with ALMP where certain MACs must be able to move to other objects (for example, VRRP virtual MACs).
The no form of this command removes the MAC list name.
Parameters
- name
-
Specifies the MAC list name, up to 32 characters.
- create
-
Keyword used to create the MAC list.
Platforms
All
mac-move
mac-move
Syntax
[no] mac-move
Context
[Tree] (config>service>template>vpls-template mac-move)
[Tree] (config>service>vpls mac-move)
Full Context
configure service template vpls-template mac-move
configure service vpls mac-move
Description
Commands in this context configure MAC move attributes. A sustained high re-learn rate can be a sign of a loop somewhere in the VPLS topology. Typically, STP detects loops in the topology, but for those networks that do not run STP, the mac-move feature is an alternative way to protect your network against loops.
When enabled in a VPLS, mac-move monitors the re-learn rate of each MAC. If the rate exceeds the configured maximum allowed limit, it disables the SAP where the source MAC was last seen. The SAP can be disabled permanently (until a shutdown/no shutdown command is executed) or for a length of time that grows linearly with the number of times the specified SAP was disabled. You have the option of marking a SAP as non-blockable in the config>service>vpls>sap>limit-mac-move or config>service>vpls>spoke-sdp>limit-mac-move contexts. This means that when the re-learn rate has exceeded the limit, another (blockable) SAP will be disabled instead.
The mac-move command enables the feature at the service level for SAPs and spoke-SDPs, as only those objects can be blocked by this feature. Mesh SDPs are never blocked, but their re-learn rates (sap-to-mesh/spoke-to-mesh or vice versa) are still measured.
The operation of this feature is the same on the SAP and spoke-SDP. For example, if a MAC address moves from SAP to SAP, from SAP to spoke-SDP, or between spoke-SDPs, one will be blocked to prevent thrashing. If the MAC address moves between a SAP and mesh SDP or spoke-SDP and mesh SDP combinations, the respective SAP or spoke-SDP will be blocked.
mac-move will disable a VPLS port when the number of relearns detected has reached the number of relearns needed to reach the move-frequency in the 5-second interval. For example, when the move-frequency is configured to 1 (relearn per second) mac-move will disable one of the VPLS ports when 5 relearns were detected during the 5-second interval because then the average move-frequency of 1 relearn per second has been reached. This can already occur in the first second if the real relearn rate is 5 relearns per second or higher.
The no form of this command disables MAC move.
Platforms
All
mac-move-level
mac-move-level
Syntax
mac-move-level {primary | secondary| tertiary}
Context
[Tree] (config>service>template>vpls-sap-template mac-move-level)
Full Context
configure service template vpls-sap-template mac-move-level
Description
When a SAP is instantiated using vpls-sap-template, if the MAC move feature is enabled at VPLS level, the command mac-move-level indicates whether the sap should be populated as primary-port, secondary-port, or tertiary-port in the instantiated VPLS.
If configured to the default, SAP is populated as a tertiary-port.
Default
no mac-move-level
Platforms
All
mac-name
mac-name
Syntax
mac-name name ieee-address
no mac-name name
Context
[Tree] (config>service>pbb mac-name)
Full Context
configure service pbb mac-name
Description
This command configures the MAC name for the MAC address. It associates an ASCII name with an IEEE MAC to improve the PBB Epipe configuration. It can also change the dest-BMAC in one place instead of 1000s of Epipe.
Parameters
- name
-
Specifies the MAC name up to 32 characters in length.
- ieee-address
-
Specifies the MAC address assigned to the MAC name. The value should be input in either a xx:xx:xx:xx:xx:xx or xx-xx-xx-xx-xx-xx format.
Platforms
All
mac-notification
mac-notification
Syntax
mac-notification
Context
[Tree] (config>service mac-notification)
Full Context
configure service mac-notification
Description
This command controls the settings for the MAC notification message.
The MAC notification message must be generated under the following events:
-
When enabled in the BVPLS using no shutdown, a MAC notification will be sent for every active MC-LAG link. The following 3 cases assume no shutdown in the BVPLS.
-
Whenever a related MC-LAG link becomes active (the related MC-LAG link has at least 1 SAP associated with the BVPLS) if the MC-LAG peering is initialized and the PE peers are synchronized.
-
First SAP on an active MC-LAG is associated (via IVPLS/Epipe) with the BVPLS.
-
The link between IVPLS/Epipe and BVPLS is configured and there are I-SAPs configured on an active MC-LAG link.
The MAC notification is not sent for the following events:
-
Change of source-bmac or source-bmac-lsb
-
On changes of use-sap-bmac parameter
-
If MC-LAG peering is not (initialized and in sync).
Platforms
All
mac-notification
Syntax
mac-notification
Context
[Tree] (config>service>vpls mac-notification)
Full Context
configure service vpls mac-notification
Description
This command controls the settings for the MAC notification message.
The MAC notification message must be generated under the following events:
-
When enabled in the BVPLS using no shutdown, a MAC notification will be sent for every active MC-LAG link. The following three cases assume no shutdown in the BVPLS.
-
Whenever a related MC-LAG link becomes active (the related MC-LAG link has at least 1 SAP associated with the BVPLS) if the MC-LAG peering is initialized and the PE peers are synchronized.
-
First SAP on an active MC-LAG is associated (via IVPLS/Epipe) with the BVPLS
-
The link between IVPLS/Epipe and BVPLS is configured and there are I-SAPs configured on an active MC-LAG link.
The MAC notification is not sent for the following events:
-
Change of source-bmac or source-bmac-lsb
-
On changes of use-sap-bmac parameter
-
If MC-LAG peering is not (initialized and in sync).
Platforms
All
mac-ping
mac-ping
Syntax
mac-ping service service-id destination dst-ieee-address [source src-ieee-address] [fc fc-name [profile {in | out}]] [size octets] [ttl vc-label-ttl] [count send-count] [return-control] [interval interval] [timeout timeout]
Context
[Tree] (oam mac-ping)
[Tree] (config>saa>test>type mac-ping)
Full Context
oam mac-ping
configure saa test type mac-ping
Description
This command determines the existence of an egress SAP binding of a given MAC within a VPLS service.
A mac-ping packet is sent via the data plane.
A mac-ping is forwarded along the flooding domain if no MAC address bindings exist. If MAC address bindings exist, then the packet is forwarded along those paths, provided they are active. A response is generated only when there is an egress SAP binding for that MAC address or if the MAC address is a ‟local” OAM MAC address associated with the device’s control plan.
A mac-ping reply can be sent using the data plane or the control plane. The return-control option specifies the reply be sent using the control plane. If return-control is not specified, the request is sent using the data plane.
A mac-ping with data plane reply can only be initiated on nodes that can have an egress MAC address binding. A node without a FDB and without any SAPs cannot have an egress MAC address binding, so it is not a node where replies in the data plane are trapped and sent up to the control plane.
A control plane request is responded to via a control plane reply only.
By default, MAC OAM requests are sent with the system or chassis MAC address as the source MAC. The source option allows overriding of the default source MAC for the request with a specific MAC address.
When a source ieee-address value is specified and the source MAC address is locally registered within a split horizon group (SHG), then this SHG membership is used as if the packet originated from this SHG. In all other cases, SHG 0 (zero) is used. If the mac-trace is originated from a non-zero SHG, such packets do not go out to the same SHG.
Parameters
- service-id
-
Specifies the service ID of the service to diagnose or manage.
- dst-ieee-address
-
Specifies the destination MAC address for the OAM MAC request.
- src-ieee-address
-
Specifies the source MAC address from which the OAM MAC request originates. By default, the system MAC address for the chassis is used.
- fc-name
-
Specifies that the fc parameter be used to test the forwarding class of the MPLS echo request packets. The actual forwarding class encoding is controlled by the network egress LSP-EXP mappings.
- profile {in | out}
-
Specifies the profile state of the MPLS echo request encapsulation.
- octets
-
Specifies the MAC OAM request packet size in octets, expressed as a decimal integer. The request payload is padded to the specified size with a 6 byte PAD header and a byte payload of 0xAA as necessary. If the octet size specified is less than the minimum packet, the minimum sized packet necessary to send the request is used.
- vc-label-ttl
-
Specifies the TTL value in the VC label for the OAM MAC request, expressed as a decimal integer.
- send-count
-
Specifies the number of messages to send, expressed as a decimal integer. The count parameter is used to override the default number of message requests sent. Each message request must either time out or receive a reply before the next message request is sent. The message interval value must be expired before the next message request is sent.
- return-control
-
Specifies the MAC OAM reply to a data plane MAC OAM request be sent using the control plane instead of the data plane.
- interval
-
Specifies the time, in seconds, used to override the default request message send interval and defines the minimum amount of time that must expire before the next message request is sent.
If the interval is set to 1 second where the timeout value is set to 10 seconds, then the maximum time between message requests is 10 seconds and the minimum is 1 second. This depends upon the receipt of a message reply corresponding to the outstanding message request.
- timeout
-
Specifies the time, in seconds, used to override the default timeout value and is the amount of time that the router waits for a message reply after sending the message request. Upon the expiration of message time out, the requesting router assumes that the message response is not received. Any response received after the request times out is silently discarded.
Platforms
All
mac-pinning
mac-pinning
Syntax
[no] mac-pinning
Context
[Tree] (config>service>vpls>sap mac-pinning)
[Tree] (config>service>vpls>spoke-sdp mac-pinning)
[Tree] (config>service>vpls>mesh-sdp mac-pinning)
[Tree] (config>service>vpls>endpoint mac-pinning)
Full Context
configure service vpls sap mac-pinning
configure service vpls spoke-sdp mac-pinning
configure service vpls mesh-sdp mac-pinning
configure service vpls endpoint mac-pinning
Description
This command disables re-learning of MAC addresses on other SAPs within the VPLS. The MAC address will remain attached to a given SAP for duration of its age-timer.
The age of the MAC address entry in the FDB is set by the age timer. If mac-aging is disabled on a given VPLS service, any MAC address learned on a SAP or SDP with mac-pinning enabled will remain in the FDB on this SAP or SDP forever.
Every event that would otherwise result in re-learning is logged (MAC address; original-SAP; new-SAP).
When a SAP or spoke SDP is part of a Residential Split Horizon Group (RSHG), MAC pinning is activated at creation of the SAP. Otherwise MAC pinning is not enabled by default.
The no form of the command enables re-learning of MAC addresses.
MAC addresses learned during DHCP address assignment (DHCP snooping enabled) are not impacted by this command. MAC-pinning for such addresses is implicit.
Default
no mac-pinning
Platforms
All
mac-pinning
Syntax
[no] mac-pinning
Context
[Tree] (config>service>pw-template mac-pinning)
Full Context
configure service pw-template mac-pinning
Description
Enabling this command will disable re-learning of MAC addresses on other SAPs within the service. The MAC address will remain attached to a given SAP for duration of its age-timer.
The age of the MAC address entry in the FDB is set by the age timer. If mac-aging is disabled on a given VPLS service, any MAC address learned on a SAP or SDP with mac-pinning enabled will remain in the FDB on this SAP or SDP forever. Every event that would otherwise result in re-learning will be logged (MAC address; original-SAP; new-SAP).
When a SAP or spoke SDP is part of a Residential Split Horizon Group (RSHG), MAC pinning is activated at creation of the SAP. Otherwise MAC pinning is not enabled by default.
For 7750 SR and 7450 ESS, MAC addresses learned during DHCP address assignment (DHCP snooping enabled) are not impacted by this command. MAC-pinning for such addresses is implicit.
Default
no mac-pinning
Platforms
All
mac-policy
mac-policy
Syntax
mac-policy mac-policy-id [create]
no mac-policy mac-policy-id
Context
[Tree] (config>macsec mac-policy)
Full Context
configure macsec mac-policy
Description
This command configures MAC address policy groups.
The no form of this command removes the MAC address policy group configuration.
Parameters
- mac-policy-id
-
Specifies the value of the MAC address policy.
- create
-
Mandatory keyword used to create the configuration.
Platforms
All
mac-populate
mac-populate
Syntax
mac-populate {service-id | service service-name} mac ieee-address [flood] [ age seconds] [force] [ target-sap sap-id]
Context
[Tree] (oam mac-populate)
Full Context
oam mac-populate
Description
This command populates the FDB with an OAM-type MAC entry indicating the node is the egress node for the MAC address and optionally floods the OAM MAC association throughout the service. The mac-populate command installs an OAM MAC into the service FDB indicating the device is the egress node for a MAC address. The MAC address can be bound to a SAP (the target-sap) or can be associated with the control plane in that any data destined to the MAC address is forwarded to the control plane (CPM). As a result, if the service on the node has neither a FDB nor an egress SAP, then it is not allowed to initiate a mac-populate.
The MAC address that is populated in the FDBs in the provider network is given a type OAM, so that it can be treated distinctly from regular dynamically learned or statically configured MACs. Note that OAM MAC addresses are operational MAC addresses and are not saved in the device configuration. An exec file can be used to define OAM MACs after system initialization.
The force option in mac-populate forces the MAC in the table to be type OAM in the case it already exists as a dynamic, static or an OAM induced learned MAC with some other type binding.
An OAM-type MAC cannot be overwritten by dynamic learning and allows customer packets with the MAC to either ingress or egress the network while still using the OAM MAC entry.
The flood option causes each upstream node to learn the MAC (that is, populate the local FDB with an OAM MAC entry) and to flood the request along the data plane using the flooding domain. The flooded mac-populate request is sent via the data plane.
An age can be provided to age an OAM MAC using a specific interval. By default, OAM MAC addresses are not aged and can be removed with a mac-purge or with an FDB clear operation.
When split horizon group (SHG) is configured, the flooding domain depends on which SHG the packet originates from. The target-sap sap-id value dictates the originating SHG information.
Parameters
- service-id
-
Specifies the service ID of the service to diagnose or manage.
- service-name
-
Specifies the name of the service to diagnose or manage. 64 characters maximum.
- ieee-address
-
Specifies the MAC address to be populated.
- flood
-
Sends the OAM MAC populate to all upstream nodes.
- seconds
-
Specifies the age for the OAM MAC, in seconds, expressed as a decimal integer.
- force
-
Converts the MAC to an OAM MAC.
- sap-id
-
Specifies the local target SAP bound to a service on which to associate the OAM MAC. By default, the OAM MAC is associated with the control place, that is, it is associated with the CPU on the router.
When the target-sap sap-id value is not specified the MAC is bound to the CPM or CFM. The originating SHG is 0 (zero). When the target-sap sap-id value is specified, the originating SHG is the SHG of the target-sap.
Platforms
All
mac-prefix
mac-prefix
Syntax
mac-prefix mac-prefix
no mac-prefix
Context
[Tree] (config>subscr-mgmt>isa-svc-chain mac-prefix)
Full Context
configure subscriber-mgmt isa-service-chaining mac-prefix
Description
This command configures the unique MAC prefix per ISA and per outside service for all NAT group configured for service-chaining.
The no form of this command removes the MAC prefix from the configuration.
Parameters
- mac-prefix
-
Specifies the MAC prefix, up to eight characters, including separators.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
mac-protect
mac-protect
Syntax
[no] mac-protect
Context
[Tree] (config>service>vpls mac-protect)
Full Context
configure service vpls mac-protect
Description
This command indicates if this MAC is protected on the MAC protect list. When enabled, the agent will protect the MAC from being learned or re-learned on a SAP, spoke SDP or mesh SDP that has restricted learning enabled. The MAC protect list is used in conjunction with restrict-protected-src, restrict-unprotected-dst and auto-learn-mac-protect.
The no form of the command reverts to the default.
Platforms
All
mac-purge
mac-purge
Syntax
mac-purge {service-id | service service-name} target ieee-address [flood] [force] [register]
Context
[Tree] (oam mac-purge)
Full Context
oam mac-purge
Description
This command removes an OAM-type MAC entry from the FDB and optionally floods the OAM MAC removal throughout the service. A mac-purge can be sent via the forwarding path or via the control plane.
When sending the MAC purge using the data plane, the TTL in the VC label is set to 1.
A MAC address is purged only if it is marked as OAM. A mac-purge request is an HVPLS OAM packet, with the following fields. The Reply Flags is set to 0 (since no reply is expected), the Reply Mode and Reserved fields are set to 0. The Ethernet header has source set to the (system) MAC address, the destination set to the broadcast MAC address. There is a VPN TLV in the FEC Stack TLV to identify the service domain.
If the register option is provided, the R bit in the Address Delete flags is turned on.
The flood option causes each upstream node to be sent the OAM MAC delete request and to flood the request along the data plane using the flooding domain. The flooded mac-purge request is sent via the data plane.
The register option reserves the MAC for OAM testing where it is no longer an active MAC in the FDB for forwarding, but it is retained in the FDB as a registered OAM MAC. Registering an OAM MAC prevents relearns for the MAC based on customer packets. Relearning a registered MAC can only be done through a mac-populate request. The originating SHG is always 0 (zero).
Parameters
- service-id
-
Specifies the service ID of the service to diagnose or manage.
- service-name
-
Specifies the name, up to 64 characters, of the service to diagnose or manage.
- ieee-address
-
Specifies the MAC address to be purged.
- flood
-
Sends the OAM MAC purge to all upstream nodes.
- force
-
Purges the entry regardless of the entry’s originating node.
- register
-
Reserves the MAC for OAM testing.
Platforms
All
mac-refresh
mac-refresh
Syntax
mac-refresh refresh interval
no mac-refresh
Context
[Tree] (config>service>ipipe>sap mac-refresh)
Full Context
configure service ipipe sap mac-refresh
Description
This command specifies the interval between ARP requests sent on this Ipipe SAP. When the SAP is first enabled, an ARP request will be sent to the attached CE device and the received MAC address will be used in addressing unicast traffic to the CE. Although this MAC address will not expire while the Ipipe SAP is enabled and operational, it is verified by sending periodic ARP requests at the specified interval.
The no form of this command restores mac-refresh to the default value.
Default
mac-refresh 14400
Parameters
- refresh interval
-
Specifies the interval, in seconds, between ARP requests sent on this Ipipe SAP.
Platforms
All
mac-subnet-length
mac-subnet-length
Syntax
mac-subnet-length subnet-length
no mac-subnet-length
Context
[Tree] (config>service>vpls mac-subnet-length)
Full Context
configure service vpls mac-subnet-length
Description
This command specifies the number of bits to be considered when performing MAC learning (MAC source) and MAC switching (MAC destination). Specifically, this value identifies how many bits, starting from the beginning of the MAC address are used. For example, if the mask-value of 28 is used, MAC learning only performs a lookup for the first 28 bits of the source MAC address when comparing with existing FDB entries. Then, it installs the first 28 bits in the FDB while zeroing out the last 20 bits of the MAC address. When performing switching in the reverse direction, only the first 28 bits of the destination MAC address are used to perform a FDB lookup to determine the next hop.
The no form of this command switches back to full MAC lookup.
Default
mac-subnet-length 48
Parameters
- subnet-length
-
Specifies the number of bits to be considered when performing MAC learning or MAC switching.
Platforms
All
mac-trace
mac-trace
Syntax
mac-trace service service-id destination ieee-address [source ieee-address] [fc fc-name [profile {in | out}]] [size octets] [min-ttl vc-label-ttl] [max-ttl vc-label-ttl] [probe-count send-count] [return-control] [interval interval] [timeout timeout]
Context
[Tree] (oam mac-trace)
[Tree] (config>saa>test>type mac-trace)
Full Context
oam mac-trace
configure saa test type mac-trace
Description
This command displays the hop-by-hop path for a destination MAC address within a VPLS.
The MAC traceroute operation is modeled after the IP traceroute utility which uses ICMP echo request and reply packets with increasing TTL values to determine the hop-by-hop route to a destination IP. The MAC traceroute command uses Nokia OAM packets with increasing TTL values to determine the hop-by-hop route to a destination MAC.
In a MAC traceroute, the originating device creates a MAC ping echo request packet for the MAC to be tested with increasing values of the TTL. The echo request packet is sent via the data plane and awaits a TTL exceeded response or the echo reply packet from the device with the destination MAC. The devices that reply to the echo request packets with the TTL exceeded and the echo reply are displayed.
When a source ieee-address value is specified and the source MAC address is locally registered within a split horizon group (SHG), then this SHG membership is used as if the packet originated from this SHG. In all other cases, SHG 0 (zero) is used. Note that if the mac-ping is originated from a non-zero SHG, such packets do not go out to the same SHG.
Parameters
- service-id
-
Specifies the service ID of the service to diagnose or manage.
This variant of the command is only supported in the classic configuration-mode (configure system management-interface configuration-mode classic).
- destination ieee-address
-
Specifies the destination MAC address to be traced.
- source ieee-address
-
The source MAC address from which the OAM MAC request originates. By default, the system MAC address for the chassis is used.
- fc-name
-
Specifies the forwarding class to test the forwarding class of the ICMP echo request packets. The actual forwarding class encoding is controlled by the network egress LSP-EXP mappings.
- profile {in | out}
-
Specifies the profile state of the ICMP echo request encapsulation.
- octets
-
Specifies the MAC OAM request packet size in octets, expressed as a decimal integer. The request payload is padded to the specified size with a 6 byte PAD header and a byte payload of 0xAA as necessary. If the octet size specified is less than the minimum packet, the minimum sized packet necessary to send the request is used.
- min-ttl vc-label-ttl
-
Specifies the minimum TTL value in the VC label for the MAC trace test, expressed as a decimal integer.
- max-ttl vc-label-ttl
-
Specifies the maximum TTL value in the VC label for the MAC trace test, expressed as a decimal integer.
- send-count
-
Specifies the number of MAC OAM requests sent for a TTL value, expressed as a decimal integer.
- return-control
-
Specifies the MAC OAM reply to a data plane MAC OAM request be sent using the control plane instead of the data plane.
- interval
-
Specifies the time, in seconds, used to override the default request message send interval and defines the minimum amount of time that must expire before the next message request is sent.
If the interval is set to 1 second, and the timeout value is set to 10 seconds, then the maximum time between message requests is 10 seconds and the minimum is 1 second. This depends upon the receipt of a message reply corresponding to the outstanding message request.
- timeout
-
Specifies the time, in seconds, used to override the default timeout value and is the amount of time that the router waits for a message reply after sending the message request. Upon the expiration of message time out, the requesting router assumes that the message response is not received. Any response received after the request times out is silently discarded.
Platforms
All
mac-translation
mac-translation
Syntax
[no] mac-translation
Context
[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw>ranges>range>vrgw>lanext mac-translation)
[Tree] (config>service>ies>sub-if>grp-if>wlan-gw>ranges>range>vrgw>lanext mac-translation)
Full Context
configure service vprn subscriber-interface group-interface wlan-gw vlan-tag-ranges range vrgw lanext mac-translation
configure service ies subscriber-interface group-interface wlan-gw vlan-tag-ranges range vrgw lanext mac-translation
Description
This command enables MAC address translation for HLE services.
The no form of this command disables MAC address translation for HLE services.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
macsec
macsec
Syntax
macsec
Context
[Tree] (config macsec)
Full Context
configure macsec
Description
Commands in this context configure MACsec, including the MACsec MKA profile.
Platforms
All
macsec
Syntax
[no] macsec
Context
[Tree] (config>port>ethernet>dot1x macsec)
Full Context
configure port ethernet dot1x macsec
Description
This command configures MACsec under this port.
Platforms
All
macsec-encrypt
macsec-encrypt
Syntax
[no] macsec-encrypt
Context
[Tree] (config>macsec>connectivity-association macsec-encrypt)
Full Context
configure macsec connectivity-association macsec-encrypt
Description
This command specifies that all PDUs are encrypted and authenticated (ICV payload).
The no form of this command specifies that all PDUs are transmitted with cleartext, but still authenticated and have the trailing ICV.
Default
macsec-encrypt
Platforms
All
magic-number
magic-number
Syntax
[no] magic-number
Context
[Tree] (config>port>ml-bundle>mlppp magic-number)
Full Context
configure port multilink-bundle mlppp magic-number
Description
This command allows loopback detection to be enabled and disabled for MLPPP bundles. It is disabled by default. When the magic number option is disabled, the magic number option will not be requested when a member is trying to bring up the LCP layer on a member link; if the remote peer requests this option, it will be rejected. When transmitting echo-requests a magic number of 0 is used. When responding to echo-requests a magic number of 0 is sent.
The magic number option is sent to the remote peer during protocol negotiation. If this option is rejected by the remote peer, the router will bring the link up but will be unable to detect loopbacks since the router will always send a magic number of 0 in the echo messages. If this option is accepted by the remote peer, the router will send echo messages with randomly generated magic-numbers. If the SR receives a config-req with the same magic number that was sent out, the router will calculate a new magic number to use and send out another config-request. If the router is persistently seeing the randomly generated magic number in the received config-req, the router will declare a loopback.
The no form of this command disables the loopback detection.
Default
no magic-number
Platforms
7450 ESS, 7750 SR-7/12/12e
main-ct-retry-limit
main-ct-retry-limit
Syntax
main-ct-retry-limit number
no main-ct-retry-limit
Context
[Tree] (config>router>mpls>lsp-template main-ct-retry-limit)
[Tree] (config>router>mpls>lsp main-ct-retry-limit)
Full Context
configure router mpls lsp-template main-ct-retry-limit
configure router mpls lsp main-ct-retry-limit
Description
This command configures the maximum number of retries the LSP primary path should be retried with the LSP Diff-Serv main Class Type (CT).
When an unmapped LSP primary path goes into retry, it uses the main CT until the number of retries reaches the value of the new main-ct-retry-limit parameter. If the path did not come up, it must start using the backup CT at that point in time. By default, this parameter is set to infinite value. The new main-ct-retry-limit parameter has no effect on an LSP primary path which retries due to a failure event.
An unmapped LSP primary path is a path which has never received a Resv in response to the first Path message sent. This can occur when performing a ‟shut/no-shut” on the LSP or LSP primary path or when the node reboots. An unmapped LSP primary path goes into retry if the retry timer expired or the head-end node received a PathErr message before the retry timer expired.
If the user entered a value of the main-ct-retry-limit parameter that is greater than the value of the LSP retry-limit, the number of retries will still stop when the LSP primary path reaches the value of the LSP retry-limit. In other words, the meaning of the LSP retry-limit parameter is not changed and always represents the upper bound on the number of retries. The unmapped LSP primary path behavior applies to both CSPF and non-CSPF LSPs.
The no form of this command sets the parameter to the default value of zero (0) which means the LSP primary path will retry forever.
Default
no main-ct-retry-limit
Parameters
- number
-
Specifies the number of times MPLS will attempt to re-establish the LSP primary path using the Diff-Serv main CT. Allowed values are integers in the range of zero (0) to 10,000, where zero indicates to retry infinitely.
Platforms
All
maintenance-policy
maintenance-policy
Syntax
[no] maintenance-policy maintenance-policy-name
Context
[Tree] (config>router>segment-routing maintenance-policy)
Full Context
configure router segment-routing maintenance-policy
Description
This command configures a named maintenance policy that can be applied to SR Policy candidate paths that are either statically configured or imported via BGP. A maintenance policy is used to configure seamless BFD and protection for an SR Policy candidate path.
A maintenance policy must be administratively disabled in order to change any of the parameters.
A maintenance policy cannot be enabled unless a mode, bfd-enable, and bfd-template are configured.
If a maintenance-template is administratively disabled, then all candidate paths to which it is applied are deprogrammed from the data path.
The no form of this command removes the specified maintenance policy.
Parameters
- maintenance-policy-name
-
Specifies the name of the maintenance policy, up to 32 characters and cannot start with a space or underscore.
Platforms
All
maintenance-policy
Syntax
[no] maintenance-policy maintenance-policy-name
Context
[Tree] (conf>router>segment-routing>sr-policies>policy maintenance-policy)
Full Context
configure router segment-routing sr-policies static-policy maintenance-policy
Description
This command applies a named maintenance policy to the static SR policy path. The maintenance policy must exist under the configure router segment-routing context.
The no form of this command removes the specified maintenance policy.
Parameters
- maintenance-policy-name
-
Specifies the name of the maintenance policy, up to 32 characters and cannot start with a space or underscore.
Platforms
All
managed-configuration
managed-configuration
Syntax
[no] managed-configuration
Context
[Tree] (config>service>vprn>router-advert>if managed-configuration)
[Tree] (config>router>router-advert>if managed-configuration)
[Tree] (config>service>ies>sub-if>grp-if>ipv6>rtr-adv managed-configuration)
[Tree] (config>service>ies>sub-if>ipv6>rtr-adv managed-configuration)
[Tree] (config>service>vprn>sub-if>grp-if>ipv6 managed-configuration)
[Tree] (config>service>vprn>sub-if>grp-if>ipv6>rtr-adv managed-configuration)
[Tree] (config>subscr-mgmt>rtr-adv-plcy managed-configuration)
[Tree] (config>service>vprn>sub-if>ipv6>rtr-adv managed-configuration)
[Tree] (config>service>ies>sub-if>grp-if>ipv6 managed-configuration)
Full Context
configure service vprn router-advertisement interface managed-configuration
configure router router-advertisement interface managed-configuration
configure service ies subscriber-interface group-interface ipv6 router-advertisements managed-configuration
configure service ies subscriber-interface ipv6 router-advertisements managed-configuration
configure service vprn subscriber-interface group-interface ipv6 managed-configuration
configure service vprn subscriber-interface group-interface ipv6 router-advertisements managed-configuration
configure subscriber-mgmt router-advertisement-policy managed-configuration
configure service vprn subscriber-interface ipv6 router-advertisements managed-configuration
configure service ies subscriber-interface group-interface ipv6 managed-configuration
Description
This command sets or resets managed address configuration flag for this group-interface. This flag indicates that DHCPv6 is available for address configuration in addition to any address auto-configured using stateless address auto-configuration. See RFC 3315 for additional details.
The no form of this command reverts to the default.
Default
no managed-configuration
Platforms
All
- configure router router-advertisement interface managed-configuration
- configure service vprn router-advertisement interface managed-configuration
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
- configure service ies subscriber-interface ipv6 router-advertisements managed-configuration
- configure service vprn subscriber-interface ipv6 router-advertisements managed-configuration
- configure service vprn subscriber-interface group-interface ipv6 router-advertisements managed-configuration
- configure service vprn subscriber-interface group-interface ipv6 managed-configuration
- configure subscriber-mgmt router-advertisement-policy managed-configuration
- configure service ies subscriber-interface group-interface ipv6 managed-configuration
- configure service ies subscriber-interface group-interface ipv6 router-advertisements managed-configuration
managed-routes
managed-routes
Syntax
managed-routes
Context
[Tree] (config>service>ies>sub-if>grp-if>sap>static-host managed-routes)
[Tree] (config>service>vprn>sub-if>grp-if>sap>static-host managed-routes)
Full Context
configure service ies subscriber-interface group-interface sap static-host managed-routes
configure service vprn subscriber-interface group-interface sap static-host managed-routes
Description
Commands in this context configure managed route parameters.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
managed-vlan-list
managed-vlan-list
Syntax
managed-vlan-list
Context
[Tree] (config>service>vpls>sap managed-vlan-list)
Full Context
configure service vpls sap managed-vlan-list
Description
Commands in this context configure VLAN ranges to be managed by a management VPLS. The list indicates, for each SAP, the ranges of associated VLANs that will be affected when the SAP changes state. This managed-vlan-list is not used when STP mode is MSTP in which case the vlan-range is taken from the config>service>vpls>stp>msti configuration.
This command is only valid when the VPLS in which it is entered was created as a management VPLS.
Platforms
All
management
management
Syntax
management [create]
no management
Context
[Tree] (config>service>vprn management)
Full Context
configure service vprn management
Description
Commands in this context configure node management within the VPRN.
Parameters
- create
-
Keyword used to create a management server entry.
Platforms
All
management
Syntax
management
Context
[Tree] (config>system>security management)
Full Context
configure system security management
Description
Commands in this context allow access to management servers.
Platforms
All
management-access-filter
management-access-filter
Syntax
[no] management-access-filter
Context
[Tree] (config>system>security management-access-filter)
Full Context
configure system security management-access-filter
Description
This command creates the context to edit management access filters and to reset match criteria.
Management access filters control all traffic in and out of the CPM. They can be used to restrict management of the router by other nodes outside either specific (sub)networks or through designated ports.
Management filters, as opposed to other traffic filters, are enforced by system software.
The no form of this command removes management access filters from the configuration.
Platforms
All
management-interface
management-interface
Syntax
management-interface
Context
[Tree] (config>system management-interface)
Full Context
configure system management-interface
Description
Commands in this context configure the capabilities of router management interfaces such as CLI and NETCONF.
Platforms
All
management-interface
Syntax
management-interface
Context
[Tree] (config>system>security management-interface)
Full Context
configure system security management-interface
Description
Commands in this context configure the selection of a management interface for hash configuration. The management interfaces are classic-cli, md-cli, netconf, or grpc.
Platforms
All
manager
manager
Syntax
manager manager-name [create]
no manager manager-name
Context
[Tree] (config>system>management-interface>remote-management manager)
Full Context
configure system management-interface remote-management manager
Description
Commands configured in this context take precedence over command values specified directly in the configure management-interface remote-management context.
If a command is not configured in this context, the command setting is inherited from the higher level context.
The no form of this command removes the remote manager configuration.
Default
system-name
Parameters
- manager-name
-
Specifies the name of the remote manager, up to 32 characters.
Platforms
All
manager-address
manager-address
Syntax
manager-address ip-address | fqdn
no manager-address
Context
[Tree] (config>system>management-interface>remote-management>manager manager-address)
Full Context
configure system management-interface remote-management manager manager-address
Description
This command configures the destination IP address or FQDN of the manager.
The no form of this command removes the configured IP address or FQDN of the configured manager.
Parameters
- ip-address
-
Specifies the IP address, up to 255 characters.
- fqdn
-
Specifies the FQDN, up to 255 characters.
Platforms
All
manager-port
manager-port
Syntax
manager-port port
no manager-port
Context
[Tree] (config>system>management-interface>remote-management>manager manager-port)
Full Context
configure system management-interface remote-management manager manager-port
Description
This command assigns a destination TCP port to be used for opening gRPC connections to the specified remote manager.
The no form of this command reverts the destination TCP port for the remote manager to the default gRPC port (57400).
Parameters
- port
-
Specifies the TCP destination port.
Platforms
All
manual
manual
Syntax
manual
Context
[Tree] (config>service>system>bgp-evpn>eth-seg>service-carving manual)
Full Context
configure service system bgp-evpn ethernet-segment service-carving manual
Description
Commands in this context manually configure the service-carving algorithm, that is, configure the EVIs or ISIDs for which the PE is DF.
Platforms
All
manual-keying
manual-keying
Syntax
[no] manual-keying
Context
[Tree] (config>service>vprn>if>sap>ipsec-tunnel manual-keying)
[Tree] (config>router>if>ipsec>ipsec-tunnel manual-keying)
[Tree] (config>service>ies>if>ipsec>ipsec-tunnel manual-keying)
[Tree] (config>service>vprn>if>ipsec>ipsec-tunnel manual-keying)
Full Context
configure service vprn interface sap ipsec-tunnel manual-keying
configure router interface ipsec ipsec-tunnel manual-keying
configure service ies interface ipsec ipsec-tunnel manual-keying
configure service vprn interface ipsec ipsec-tunnel manual-keying
Description
This command configures Security Association (SA) for manual keying. When enabled, the command specifies whether this SA entry is created manually, by the user, or dynamically by the IPsec sub-system.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
- configure service vprn interface sap ipsec-tunnel manual-keying
VSR
- configure router interface ipsec ipsec-tunnel manual-keying
- configure service vprn interface ipsec ipsec-tunnel manual-keying
- configure service ies interface ipsec ipsec-tunnel manual-keying
map
map
Syntax
map start lsn-sub-address end lsn-sub-address to outside-ip-address
no map start lsn-sub-address end lsn-sub-address
Context
[Tree] (config>service>vprn>nat>inside>deterministic>prefix map)
[Tree] (config>router>nat>inside>deterministic>prefix map)
Full Context
configure service vprn nat inside deterministic prefix map
configure router nat inside deterministic prefix map
Description
This command is applicable to prefixes in deterministic NAT (LSN44 and DS-Lite) and static 1:1 NAT (LSN44). In deterministic NAT, its purpose is to split the number of subscribers within the configured prefix over available sequence of outside IP addresses. In static 1:1 NAT, its purpose it to statically map source IPv4 address of an LSN44 subscriber to a configured IPv4 address on the public side.
In deterministic NAT, there are several rules guiding the usage of the map statement:
-
If the number of subscribers per configured prefix is greater than the subscriber-limit per outside IP parameter (2^n), then the lowest n bits of the map start <inside-addr-start> must be set to 0.
Subscriber in LSN44 is equals to an inside IPv4 address, while in DS-Lite, the subscriber can be an IPv6 address or IPv6 prefix. If the subscriber-prefix-length command is set to 128, then the subscriber in DS-Lite is an IPv6 address. Otherwise, it will be an IPv6 prefix with length in the range of 32 to 64 as set by the subscriber-prefix-length command.
-
If the number of subscribers per configured prefix is equal or less than the subscriber-limit per outside IP parameter (2^n), then only one map command for this prefix is allowed. In this case there is no restriction on the lower n bits of the map start lsn-sub-address. The range of the inside IP addresses in such map statement represents the prefix itself.
-
outside-ip-address in the map statements must be unique amongst all map statements referencing the same pool. In other words, two map statements cannot reference the same outside-ip-address in a pool.
To modify map statements in classic CLI, the corresponding prefix must be in a shutdown mode.
The map statements can be configured automatically by the system, as soon as the prefix is enabled (no shutdown state) or they can be configured manually by the operator while the prefix is disabled.
The following is an example of the map statement for the LSN44 case:
-
The subscriber-limit in the pool is 128
-
The pool has an address range 192.168.0.1 - 192.168.0.10
-
The prefix is 10.0.0.0/24
-
The map statement is configured as:
map start 10.0.0.0 end 10.0.0.255 to 192.168.0.1
Since each outside IP address can accommodate only 128 hosts, the subscribers (IPv4 addresses in LSN44) from the 10.0.0.0/24 prefix are split and mapped into two outside IP addresses:
10.0.0.0 – 10.0.0.127 (10.0.0.0/25) - 192.168.0.1
10.0.0.128 – 10.0.0.255 (10.0.0.128/25) - 192.168.0.2
The first IP address range is mapped to the to address in the map statement => 192.168.0.1. The second IP address range is mapped into the next consecutive IP address in the pool assuming that this IP address is free. In this case, this consecutive address (192.168.0,2) would not be shown in the map statement.
For Deterministic DS-Lite, the example would be:
-
The subscriber-limit in the pool is 128
-
The pool has an address range 192.168.0.1 - 192.168.0.10
-
The prefix is 2001:db8::/56
-
The subscriber-prefix-length = 64
-
The map statement is configured as:
map start 2001:db8::/64 end 2001:db8::FF:0:0:0:0/64 to 192.168.0.1
There are 256 DS-Lite subscribers within the 2001:db8::/56 prefix. Each subscriber has a /64 IPv6 prefix as dictated by the subscriber-prefix-length command.
Since each outside IP address can accommodate only 128 hosts, the subscribers from the 2001:db8::/56 prefix is split and mapped into two outside IP addresses:
2001:db8:: – 2001:db8:0:7F:: (2001:db8::/57) - 192.168.0.1
2001:db8:0:80:: – 2001:db8:0:FF::(2001:db8:0:FF::/57) - 192.168.0.2
The first IP prefix range is mapped to the to address in the map statement => 192.168.0.1. The second IP prefix range is mapped into the next consecutive IP address in the pool assuming that this IP address is free. In this case, this consecutive address (192.168.0,2) would not be shown in the map statement.
Default
The system automatically divides the prefix and creates the map statements when the prefix command is enabled (no shutdown). However, this automatic map provisioning can be overruled by manual configuration in classic CLI.
Parameters
- inside-ip-start
-
Specifies the start IPv4/v6 address or IPv6 prefix on the inside.
- inside-ip-end
-
Specifies the end IPv4/v6 address or IPv6 prefix on the inside. The number of subscribers (range of inside IPv4 addresses in LSN44 or IPv6 addresses or prefixes in DS-Lite) in the map statement does not have to be a power of 2. Rather, it must be a multiple of a power of two m * 2^n, where m is the number of consecutive outside IP addresses to which the subscribers are mapped and the 2^n is the subscriber-limit per outside IP.
- outside-ip-start
-
Specifies the first outside IPv4 address in the pool to which the subscribers are mapped. In case that the number of subscribers in the map statement is larger than the subscriber-limit for the outside-ip address, the consecutive outside IP addresses will be used for additional mappings. Those additional (consecutive) outside IP addresses are not shown in the map statement (only the first address is shown in the map statement).
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
map
Syntax
[no] map
Context
[Tree] (config>service>nat>pcp-server-policy>opcode map)
Full Context
configure service nat pcp-server-policy opcode map
Description
This command enables/disables support for the map opcode.
Default
no map
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
map-domain
map-domain
Syntax
map-domain domain-name [create]
no map-domain
Context
[Tree] (config>service>nat map-domain)
Full Context
configure service nat map-domain
Description
This command creates a MAP domain template, which is used to define MAP rules and parameters specific to the MAP domain. A MAP domain represents a set of CEs that share the same default gateway (BR's IPv6 prefix - DMR rule) and a set of basic MAP rules (BMRs). As a bordering node between the IPv6 and IPv4 realm, the BR performs stateless IPv4 and IPv6 translation based on MAP rules.
A MAP domain can be instantiated within a routing context by referencing an existing MAP domain template in the context.
Parameters
- domain-name
-
Specifies the name of the MAP domain, up to 32 characters. The MAP domain name has local significance.
Platforms
VSR
map-domain
Syntax
map-domain domain-name
no map-domain domain-name
Context
[Tree] (config>service>vprn>nat>map map-domain)
[Tree] (config>router>nat>map map-domain)
Full Context
configure service vprn nat map map-domain
configure router nat map map-domain
Description
This command instantiates a MAP-T domain within a routing context, assuming that the MAP-T domain template is administratively enabled (no shutdown). When the MAP-T is instantiated, the forwarding for the MAP-T domain is enabled and its routes can be exported in routing protocols.
Multiple MAP-T domains can be instantiated within a routing context.
Interactions:
The referenced MAP domain is defined under the config>service>nat context.
Parameters
- domain-name
-
Specifies the name of the MAP domain template, up to 32 characters.
Platforms
VSR
mapping
mapping
Syntax
mapping mapping
Context
[Tree] (config>port>tdm>ds3>atm mapping)
Full Context
configure port tdm ds3 atm mapping
Description
This command configures the ATM cell mapping for DS-3 channels. The mapping value specifies the cell mapping that is to be used on this ATM interface.
Default
mapping direct
Parameters
- mapping
-
Specifies the cell mapping that is to be used on this ATM interface.
Platforms
7450 ESS, 7750 SR-7/12/12e, 7750 SR-a, 7750 SR-e
mapping-limit
mapping-limit
Syntax
mapping-limit limit
no mapping-limit
Context
[Tree] (config>service>upnp>upnp-policy mapping-limit)
Full Context
configure service upnp upnp-policy mapping-limit
Description
This command specifies the maximum number of UPnP mapping per subscriber.
The no form of the command reverts to the default.
Default
mapping-limit 256
Parameters
- limit
-
Specifies the upper limit of the number of UPnP mappings per subscriber.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
mapping-rule
mapping-rule
Syntax
mapping-rule map-rule-name [create]
no mapping-rule map-rule-name
Context
[Tree] (config>service>nat>map-domain mapping-rule)
Full Context
configure service nat map-domain mapping-rule
Description
This command provides a CLI context for configuring MAP rules.
Parameters
- map-rule-name
-
Specifies the name of the MAP rule; the name has a local significance.
Platforms
VSR
mapping-server
mapping-server
Syntax
[no] mapping-server
Context
[Tree] (config>router>isis>segment-routing mapping-server)
Full Context
configure router isis segment-routing mapping-server
Description
Commands in this context configures the Segment Routing mapping server feature in an IS-IS instance.
SR mapping server enables the configuration and advertisement, via IS-IS, of the node SID index for IS-IS prefixes of routers which are in the LDP domain. This is performed in the router acting as a mapping server, which uses a prefix-SID sub-TLV within the SID/Label binding TLV in IS-IS.
The no form of this command deletes all node SID entries in the IS-IS instance.
Platforms
All
mapping-server
Syntax
[no] mapping-server
Context
[Tree] (config>router>ospf>segm-rtng mapping-server)
Full Context
configure router ospf segment-routing mapping-server
Description
Commands in this context configure the Segment Routing mapping server feature in an OSPF instance.
The mapping server feature allows the configuration and advertisement in OSPF of the node SID index for OSPF prefixes of routers which are in the LDP domain. This is performed in the router acting as a mapping server and using a prefix-SID sub-TLV within the Extended Prefix Range TLV in OSPF.
The no form of this command deletes all node SID entries in the OSPF instance.
Platforms
All
maps-to
maps-to
Syntax
maps-to fc fc-name profile profile
Context
[Tree] (config>qos>post-policer-mapping>fc maps-to)
Full Context
configure qos post-policer-mapping fc maps-to
Description
This command remaps the forwarding class and profile state of an egress policed packet that is to be mapped to another forwarding class and profile, where the profile state is that of the resulting profile after the packet has been processed by the egress policer.
The new forwarding class is used to select the egress queue on which the post-policer traffic is placed. The new profile is used to determine the congestion control handling in that queue, specifically the drop tail or slope that is applied to the traffic.
The maps-to command parameters can be overwritten by reissuing the command with a different FC or profile.
The traffic remarking is based on the marking configured for the forwarding class and profile of the traffic after being policed but before it is remapped.
Parameters
- fc-name
-
Specifies one of the eight forwarding classes supported by the system.
- profile
-
Specifies one of the egress packet profile states.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
mark
mark
Syntax
mark entity high percentage-high low percentage-low
no mark entity
Context
[Tree] (config>isa>wlan-gw-group>watermarks mark)
Full Context
configure isa wlan-gw-group watermarks mark
Description
This command enables a watermark notification. If the watermark is set, it generates a notification when the corresponding resource consumption goes above the high percentage. No additional notifications are sent until resource consumption goes under the low watermark, upon which, a notification is sent indicating the high watermark is no longer hit.
The no form of this command disables the watermark notification.
Parameters
- entity
-
Specifies which watermark to set.
- percentage-high
-
Specifies the high watermark in percentage of total resources available.
- percentage-low
-
Specifies the low watermark in percentage of total resources available.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
mask
mask
Syntax
mask type match-type {[prefix-string prefix-string | prefix-length prefix-length] [suffix-string suffix-string | suffix-length suffix-length]}
no mask type match-type
mask type dhcp-match-type {[prefix-string prefix-string | prefix-length prefix-length] [suffix-string suffix-string | suffix-length suffix-length]}
no mask type dhcp-match-type
Context
[Tree] (config>subscr-mgmt>loc-user-db>ppp mask)
[Tree] (config>subscr-mgmt>loc-user-db>ipoe mask)
Full Context
configure subscriber-mgmt local-user-db ppp mask
configure subscriber-mgmt local-user-db ipoe mask
Description
This command configures the IPoE mask.
The no form of this command removes the mask parameters from the configuration.
Parameters
- ppp-match-type
-
Specifies up to four matching types to identify a host.
- dhcp-match-type
-
Specifies the data type that represents the type of matching done to identify a DHCP host.
- prefix-string
-
Specifies a substring that is stripped of the start of the incoming circuit ID before it is matched against the value configured in the DHCP or PPPoE circuit ID.
This string can only contain printable ASCII characters. The ‟*” character is a wildcard that matches any substring. If a "\" character is masked, use the escape key so it becomes "\\".
- prefix-length
-
Specifies the number of characters to remove from the start of the incoming circuit ID before it is matched against the value configured in the circuit ID.
- suffix-string
-
Specifies a substring that is stripped of the end of the incoming circuit ID before it is matched against the value configured in circuit ID.
This string can only contain printable ASCII characters. The ‟*” character is a wildcard that matches any substring. If a "\" character is masked, use the escape key so it becomes "\\".
- suffix-length
-
Specifies the number of characters to remove from the end of the incoming circuit ID before it is matched against the value configured in the circuit ID.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
mask
Syntax
mask mask-value [type {included | excluded}]
no mask
Context
[Tree] (config>system>security>snmp>view>view-name mask)
Full Context
configure system security snmp view view-name mask
Description
The mask value and the mask type, along with the oid-value configured in the view command, determines the access of each sub-identifier of an object identifier (MIB subtree) in the view.
Each bit in the mask corresponds to a sub-identifier position. For example, the most significant bit for the first sub-identifier, the next most significant bit for the second sub-identifier, and so on. If the bit position on the sub-identifier is available, it can be included or excluded.
For example, the MIB subtree that represents MIB-II is 1.3.6.1.2.1. The mask that catches all MIB-II would be 0xfc or 0b11111100.
Only a single mask may be configured per view and OID value combination. If more than one entry is configured, each subsequent entry overwrites the previous entry.
The no form of this command removes the mask from the configuration.
Parameters
- mask-value
-
The mask value associated with the OID value determines whether the sub-identifiers are included or excluded from the view. (Default: all 1s)
The mask can be entered either:
-
In hex. For example, 0xfc.
-
In binary. For example, 0b11111100.
Note:If the number of bits in the bit mask is less than the number of sub-identifiers in the MIB subtree, then the mask is extended with ones until the mask length matches the number of sub-identifiers in the MIB subtree.
-
- type
-
Specifies to include or exclude MIB subtree objects.
mask-reply
mask-reply
Syntax
[no] mask-reply
Context
[Tree] (config>service>ies>sub-if>grp-if mask-reply)
[Tree] (config>service>vprn>if mask-reply)
[Tree] (config>service>vprn>nw-if>icmp mask-reply)
[Tree] (config>service>ies>if>icmp mask-reply)
[Tree] (config>service>vprn>if>icmp mask-reply)
Full Context
configure service ies subscriber-interface group-interface mask-reply
configure service vprn interface mask-reply
configure service vprn network-interface icmp mask-reply
configure service ies interface icmp mask-reply
configure service vprn interface icmp mask-reply
Description
This command enables responses to Internet Control Message Protocol (ICMP) mask requests on the router interface.
If a local node sends an ICMP mask request to the router interface, the mask-reply command configures the router interface to reply to the request.
By default, the router instance replies to mask requests.
The no form of this command disables replies to ICMP mask requests on the router interface.
Default
mask-reply — Specifies to reply to ICMP mask requests.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
- configure service ies subscriber-interface group-interface mask-reply
All
- configure service vprn interface mask-reply
- configure service ies interface icmp mask-reply
- configure service vprn network-interface icmp mask-reply
- configure service vprn interface icmp mask-reply
mask-reply
Syntax
[no] mask-reply
Context
[Tree] (config>subscr-mgmt>git>ipv4>icmp mask-reply)
Full Context
configure subscriber-mgmt group-interface-template ipv4 icmp mask-reply
Description
This command enables responses to ICMP mask requests on the router interface. If a local node sends an ICMP mask request to the router interface, the router interface replies to the request.
By default, the router instance replies to mask requests.
The no form of this command disables replies to ICMP mask requests on the router interface.
Default
mask-reply
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
mask-reply
Syntax
[no] mask-reply
Context
[Tree] (config>router>if>icmp mask-reply)
Full Context
configure router interface icmp mask-reply
Description
This command enables responses to ICMP mask requests on the router interface.
If a local node sends an ICMP mask request to the router interface, the mask-reply command configures the router interface to reply to the request.
The no form of this command disables replies to ICMP mask requests on the router interface.
Default
mask-reply — Replies to ICMP mask requests.
Platforms
All
master-int-inherit
master-int-inherit
Syntax
[no] master-int-inherit
Context
[Tree] (config>service>ies>if>ipv6>vrrp master-int-inherit)
Full Context
configure service ies interface ipv6 vrrp master-int-inherit
Description
This command allows the master instance to dictate the master down timer (non-owner context only).
Default
no master-int-inherit
Platforms
All
master-int-inherit
Syntax
[no] master-int-inherit
Context
[Tree] (config>service>ies>if>vrrp master-int-inherit)
Full Context
configure service ies interface vrrp master-int-inherit
Description
This command allows the master instance to dictate the master down timer (non-owner context only).
Default
no master-int-inherit
Platforms
All
master-int-inherit
Syntax
[no] master-int-inherit
Context
[Tree] (config>service>vprn>if>vrrp master-int-inherit)
[Tree] (config>service>vprn>if>ipv6>vrrp master-int-inherit)
Full Context
configure service vprn interface vrrp master-int-inherit
configure service vprn interface ipv6 vrrp master-int-inherit
Description
This command allows the master instance to dictate the master down timer (non-owner context only).
Default
no master-int-inherit
Platforms
All
master-int-inherit
Syntax
[no] master-int-inherit
Context
[Tree] (config>router>if>ipv6>vrrp master-int-inherit)
[Tree] (config>router>if>vrrp master-int-inherit)
Full Context
configure router interface ipv6 vrrp master-int-inherit
configure router interface vrrp master-int-inherit
Description
This command enables the virtual router instance to inherit the master VRRP router’s advertisement interval timer which is used by backup routers to calculate the master down timer.
The master-int-inherit command is only available in the non-owner nodal context and is used to allow the current virtual router instance master to dictate the master down timer for all backup virtual routers. The master-int-inherit command has no effect when the virtual router instance is operating as master.
If master-int-inherit is not enabled, the locally configured message-interval must match the master’s VRRP advertisement message advertisement interval field value or the message is discarded.
The no form of the command restores the default operating condition which requires the locally configured message-interval to match the received VRRP advertisement message advertisement interval field value. The virtual router instance does not inherit the master VRRP router’s advertisement interval timer and uses the locally configured message interval.
Default
no master-int-inherit
Platforms
All
master-only
master-only
Syntax
master-only {true | false}
Context
[Tree] (config>system>ptp>port master-only)
Full Context
configure system ptp port master-only
Description
This command is used to restrict the local port to never enter the timeReceiver state. Use the command to ensure that the 7750 SR never draws synchronization from the attached external device.
This parameter is only effective when the profile is set to g8275dot1-2014 or g8275dot2-2016.
The ITU-T G.8275.1 (07/2014) recommendation used the term notSlave for this functionality; however, the IEEE has added this capability into the next edition of the 1588 standard using the term masterOnly. These are equivalent.
Default
master-only true
Parameters
- true
-
Enables the master-only parameter of the PTP port.
- false
-
Disables the master-only parameter of the PTP port.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
master-selection-mode
master-selection-mode
Syntax
master-selection-mode mode
Context
[Tree] (config>app-assure>aarp master-selection-mode)
Full Context
configure application-assurance aarp master-selection-mode
Description
This command configures the AARP mode of operation with the peer instance. The modes affect the AARP state machine behavior according to the desired behavior. Minimize-switchover will change AARP state based on Master ISA failure, and be non-revertive in that when the priority ISA returns a switch does not occur, which is optimal for AA flow identification. Inter-chassis efficiency mode considers both priority (revertive) and the endpoint status of the AARP instance and will switch activity in case of EP failure in order to avoid sending all the traffic over the ICL. The priority-based-balance mode will be revertive after a priority master returns to service, but excludes EP status. The master-selection-mode configuration must match on both peer AARP instances, or the AARP operational status will stay down.
Default
master-selection-mode minimize-switchovers
Parameters
- mode
-
Specifies the AARP master selection mode.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
match
match
Syntax
match {circuit-id | mac | remote-id}
match option [number] [option6 [number]
match option6 [number]
no match
Context
[Tree] (config>subscr-mgmt>loc-user-db>ipoe>host>match-radprox-cache match)
Full Context
configure subscriber-mgmt local-user-db ipoe host match-radius-proxy-cache match
Description
This command specifies in what DHCPv6 option to retrieve the value to be used as lookup key in the RADIUS proxy cache.
The no form of this command reverts to the default.
Default
match mac
Parameters
- circuit-id
-
Specifies to use the circuit Id to match against.
- mac
-
Specifies the MAC address to match against.
- remote-id
-
Specifies the remote ID to match against.
- option number
-
Specifies the option number that the DHCP server uses to send the identification strings to the client.
- option6 number
-
Specifies the DHCPv6 option to retrieve the value to be used as lookup key in the RADIUS proxy cache.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
match
Syntax
match
Context
[Tree] (config>app-assure>group>policy>chrg-fltr>entry match)
Full Context
configure application-assurance group policy charging-filter entry match
Description
Commands in this context configure the match criterion for a AA charging-filter entry.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
match
Syntax
match
Context
[Tree] (config>subscr-mgmt>isa-svc-chain>vas-filter>entry match)
Full Context
configure subscriber-mgmt isa-service-chaining vas-filter entry match
Description
Commands in this context configure the match criterion for a VAS filter entry.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
match
Syntax
match [next-header next-header]
no match
Context
[Tree] (config>subscr-mgmt>cat-map>category>exh-lvl>ingr-ipv6>entry match)
[Tree] (config>subscr-mgmt>cat-map>category>exh-lvl>egr-ipv6>entry match)
Full Context
configure subscriber-mgmt category-map category exhausted-credit-service-level ingress-ipv6-filter-entries entry match
configure subscriber-mgmt category-map category exhausted-credit-service-level egress-ipv6-filter-entries entry match
Description
This command configures the match criteria for this IP filter entry.
The no form of this command reverts to the default.
Parameters
- next-header
-
protocol-number, protocol-name
- protocol-number
-
Specifies the protocol number accepted in DBH for IPv6 filter entries.
- protocol-name
-
Specifies the protocol name accepted in DBH for IPv6 filter entries.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
match
Syntax
match [protocol protocol-id]
no match
Context
[Tree] (config>subscr-mgmt>cat-map>category>exh-lvl>ingr-ip>entry match)
[Tree] (config>subscr-mgmt>cat-map>category>exh-lvl>egr-ip>entry match)
Full Context
configure subscriber-mgmt category-map category exhausted-credit-service-level ingress-ip-filter-entries entry match
configure subscriber-mgmt category-map category exhausted-credit-service-level egress-ip-filter-entries entry match
Description
This command configures the match criteria for this IP filter entry.
The no form of this command reverts to the default.
Parameters
- protocol-id
-
Specifies the protocol ID or protocol name accepted in DHB.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
match
Syntax
match protocol {any | icmp | tcp | udp | gre}
no match
Context
[Tree] (config>subscr-mgmt>isa-filter>ipv6>entry match)
Full Context
configure subscriber-mgmt isa-filter ipv6 entry match
Description
This command creates a match context for this entry. The protocol value specifies which Layer-4 protocol the packet should match.
The no form of this command removes the match context of this entry.
Default
match protocol any
Parameters
- protocol
-
Specifies that the only supported match context is protocol.
- any
-
Specifies to match any protocol.
- icmp
-
Specifies to match ICMP packets in a v4 filter.
- tcp
-
Specifies to match TCP packets.
- udp
-
Specifies to match UDP packets.
- gre
-
Specifies to match GRE over IP packets.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
match
Syntax
[no] match
Context
[Tree] (config>service>mrp>mrp-policy>entry match)
Full Context
configure service mrp mrp-policy entry match
Description
This command creates the context for entering/editing match criteria for the mrp-policy entry. When the match criteria have been satisfied the action associated with the match criteria is executed. In the current implementation just one match criteria (ISID based) is possible in the entry associated with the mrp-policy. Only one match statement can be entered per entry.
The no form of this command removes the match criteria for the entry-id.
Platforms
All
match
Syntax
match
Context
[Tree] (config>service>vprn>bgp>group>dynamic-neighbor match)
Full Context
configure service vprn bgp group dynamic-neighbor match
Description
This command configures match conditions for the dynamic neighbors.
Platforms
All
match
Syntax
[no] match
Context
[Tree] (config>service>vprn>log>filter>entry match)
Full Context
configure service vprn log filter entry match
Description
This command creates context to enter/edit match criteria for a filter entry. When the match criteria is satisfied, the action associated with the entry is executed.
If more than one match parameter (within one match statement) is specified, then all the criteria must be satisfied (AND functional) before the action associated with the match is executed.
Use the match command to display a list of the valid applications.
Match context can consist of multiple match parameters (application, event-number, severity, subject), but multiple match statements cannot be entered per entry.
The no form of this command removes the match criteria for the entry-id.
Default
no match
Platforms
All
match
Syntax
match
Context
[Tree] (config>app-assure>group>policy>aqp>entry match)
Full Context
configure application-assurance group policy app-qos-policy entry match
Description
Commands in this context configure flow match rules for this AQP entry. A flow matches this AQP entry only if it matches all the match rules defined (logical and of all rules). If no match rule is specified, the entry will match all flows.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
match
Syntax
match
Context
[Tree] (config>app-assure>group>sess-fltr>entry match)
Full Context
configure application-assurance group session-filter entry match
Description
Commands in this context configure session conditions for this entry.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
match
Syntax
match
Context
[Tree] (config>app-assure>group>transit-prefix-policy>entry match)
Full Context
configure application-assurance group transit-prefix-policy entry match
Description
Commands in this context configure transit prefix policy entry match criteria.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
match
Syntax
[no] match
Context
[Tree] (debug>app-assure>group>traffic-capture match)
Full Context
debug application-assurance group traffic-capture match
Description
This command configures debugging for traffic match criteria.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
match
Syntax
match protocol ip-protocol
no match
Context
[Tree] (config>service>nat>nat-classifier>entry match)
Full Context
configure service nat nat-classifier entry match
Description
This command configures an IP protocol to be used as a nat-classifier match criterion. When the match criteria have been satisfied the action associated with the match criteria is executed.
The no form of the command removes the match criteria for the entry-id.
Default
match protocol udp
Parameters
- protocol ip-protocol
-
Specifies the text value representing the IP protocol to be used as a match criterion.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
match
Syntax
match [frame-type frame-type]
no match
Context
[Tree] (config>li>li-filter>li-mac-filter>entry match)
Full Context
configure li li-filter li-mac-filter entry match
Description
Commands in this context configure match criteria for the filter entry and specifies an Ethernet frame type for the entry.
If more than one match criteria (within one match statement) are configured then all criteria must be satisfied (and function) for a match to occur.
A match context may consist of multiple match criteria, but multiple match statements cannot be entered per entry.
The no form of this command removes the match criteria for the entry.
Parameters
- frame-type
-
Filters can continue to be edited by all users even when an li-source references an entry in that filter.
Platforms
All
match
Syntax
match [protocol protocol-id]
no match
Context
[Tree] (config>li>li-filter>li-ip-filter>entry match)
Full Context
configure li li-filter li-ip-filter entry match
Description
This command enables context to enter match criteria for LI IPv4 filter and optionally allows specifying protocol value to match on.
If more than one match criterion are configured then all criteria must be satisfied for a match to occur (logical ‟AND”). Multiple criteria must be configured within a single match context for a given entry.
The no form of this command removes the match criteria for the entry.
Parameters
- protocol-id
-
Configures the decimal value representing the IP protocol to be used as an IP filter match criterion. Well known protocol numbers include ICMP(1), TCP(6), UDP(17).
Platforms
All
match
Syntax
match [next-header next-header]
no match
Context
[Tree] (config>li>li-filter>li-ipv6-filter>entry match)
Full Context
configure li li-filter li-ipv6-filter entry match
Description
Commands in this context enter match criteria for an LI IPv6 filter and optionally allows specification IPv6 next-header value to match on.
If more than one match criterion are configured, then all criteria must be satisfied for a match to occur (logical ‟AND”). Multiple criteria must be configured within a single match context for a given entry.
The no form removes the match criteria for the entry.
Parameters
- next-header
-
protocol-number, protocol-name
Specifies the IPv6 next header to match. This parameter is analogous to the protocol parameter used in IP filter match criteria.
- protocol-number
-
Specifies the protocol number value to be configured as a match criterion.
- protocol-name
-
Specifies the protocol name to be configured as a match criterion.
Platforms
All
match
Syntax
match [protocol protocol-id]
no match
Context
[Tree] (config>qos>sap-ingress>ip-criteria>entry match)
[Tree] (config>qos>sap-egress>ip-criteria>entry match)
Full Context
configure qos sap-ingress ip-criteria entry match
configure qos sap-egress ip-criteria entry match
Description
This command creates a context to configure match criteria for SAP QoS policy match criteria. When the match criteria have been satisfied, the action associated with the match criteria is executed.
If more than one match criteria (within one match statement) are configured, all criteria must be satisfied (AND function) before the action associated with the match is executed.
A match context can consist of multiple match criteria, but multiple match statements cannot be entered per entry.
It is possible that a SAP policy includes the dscp map command, the dot1p map command, and an IP match criteria. When multiple matches occur for the traffic, the order of precedence is used to arrive at the final action. The order of precedence is as follows:
-
802.1p bits
-
DSCP
-
IP quintuple or MAC headers
The no form of this command removes the match criteria for the entry-id.
Parameters
- protocol protocol-id
-
Specifies an IP protocol to be used as a SAP QoS policy match criterion.
The protocol type such as TCP / UDP / OSPF is identified by its respective protocol number. Well-known protocol numbers include ICMP(1), TCP(6), UDP(17)
IP Protocol Names lists the IP protocols and their respective IDs and descriptions.
Platforms
All
match
Syntax
match [next-header next-header]
no match
Context
[Tree] (config>qos>sap-egress>ipv6-criteria>entry match)
[Tree] (config>qos>sap-ingress>ipv6-criteria>entry match)
Full Context
configure qos sap-egress ipv6-criteria entry match
configure qos sap-ingress ipv6-criteria entry match
Description
This command creates a context to configure match criteria for ingress SAP QoS policy match IPv6 criteria. When the match criteria have been satisfied, the action associated with the match criteria is executed.
If more than one match criteria (within one match statement) are configured, all criteria must be satisfied (logical AND) before the action associated with the match is executed.
A match context can consist of multiple match criteria, but multiple match statements cannot be created per entry.
A SAP ingress policy may include the dscp map command, the dot1p map command, and an IPv6 match criteria. When multiple matches occur for the traffic, the following order of precedence is used to arrive at the final action.
-
802.1p bits
-
DSCP
-
IP quintuple or MAC headers
The no form of this command removes the match criteria for the entry-id.
Parameters
- next-header
-
protocol-number, protocol-name
Specifies the IPv6 next header to match.
On the 7750 SR and 7950 XRS, the protocol type such as TCP, UDP, or OSPF is identified by its respective protocol number. Well-known protocol numbers include ICMP(1), TCP(6) and UDP(17).
- protocol-number
-
Specifies the protocol number value to be configured as a match criterion.
- protocol-name
-
Specifies the protocol name to be configured as a match criterion.
Platforms
All
match
Syntax
match [frame-type {802dot3 | 802dot2-llc | 802dot2-snap | ethernet-II | atm}]
no match
Context
[Tree] (config>qos>sap-ingress>mac-criteria>entry match)
Full Context
configure qos sap-ingress mac-criteria entry match
Description
This command creates a context for entering/editing match MAC criteria for ingress SAP QoS policy match criteria. When the match criteria have been satisfied, the action associated with the match criteria is executed.
If more than one match criteria (within one match statement) are configured, all criteria must be satisfied (AND function) before the action associated with the match will be executed.
A match context can consist of multiple match criteria, but multiple match statements cannot be entered per entry.
The no form of this command removes the match criteria for the entry-id.
Parameters
- frame-type
-
The frame-type keyword configures an Ethernet frame type or an ATM frame type to be used for the MAC filter match criteria.
- 802dot3
-
Specifies the frame type is Ethernet IEEE 802.3.
- 802dot2-llc
-
Specifies the frame type is Ethernet IEEE 802.2 LLC.
- 802dot2-snap
-
Specifies the frame type is Ethernet IEEE 802.2 SNAP.
- ethernet-II
-
Specifies the frame type is Ethernet Type II.
- atm
-
Specifies the frame type as ATM cell. The user is not allowed to configure entries with frame type of atm and a frame type of other supported values in the same QoS policy. This parameter applies only to the 7750 SR and 7950 XRS.
Platforms
All
match
Syntax
match [protocol protocol-id]
no match
Context
[Tree] (config>qos>network>egress>ip-criteria>entry match)
[Tree] (config>qos>network>ingress>ip-criteria>entry match)
Full Context
configure qos network egress ip-criteria entry match
configure qos network ingress ip-criteria entry match
Description
This command creates a context to configure match criteria for a network QoS policy. When the match criteria have been satisfied, the action associated with it is executed.
If more than one match criteria (within one match statement) are configured, then all criteria must be satisfied before the associated action with the match is executed.
A match context can consist of multiple match criteria, but multiple match statements cannot be entered per entry.
A network QoS policy can include the DSCP map command, the dot1p map command (ingress only), the prec map command (egress only), and an IP match criteria. When multiple matches occur for the traffic, the order of precedence is used to arrive at the final action. The order of precedence is as follows:
-
802.1p bits (ingress only)
-
DSCP
-
prec (egress only)
-
IP quintuple
The no form of this command removes the match criteria for the entry identifier.
Parameters
- protocol protocol-id
-
Specifies an IP protocol to be used as an ingress or egress network QoS policy match criterion.
The protocol type is identified by its respective protocol number. Well-known protocol numbers include ICMP(1), TCP(6), and UDP(17).
Platforms
All
match
Syntax
match [next-header next-header]
no match
Context
[Tree] (config>qos>network>ingress>ipv6-criteria>entry match)
[Tree] (config>qos>network>egress>ipv6-criteria>entry match)
Full Context
configure qos network ingress ipv6-criteria entry match
configure qos network egress ipv6-criteria entry match
Description
This command creates a context to configure match criteria for a network QoS policy match IPv6 criteria. When the match criteria have been satisfied, the action associated with the match criteria is executed.
If more than one match criteria (within one match statement) are configured, all criteria must be satisfied (logical AND) before the action associated with the match is executed.
A match context can consist of multiple match criteria, but multiple match statements cannot be created per entry.
A network policy can include the DSCP map command, the dot1p map command (ingress only), the prec map command (egress only), and an IPv6 match criteria. When multiple matches occur for the traffic, the following order of precedence is used to arrive at the final action.
-
802.1p bits (ingress only)
-
DSCP
-
prec (egress only)
-
IP quintuple
The no form of this command removes the match criteria for the entry identifier.
Parameters
- next-header
-
protocol-number, protocol-name
Specifies the next header to match.
The protocol type is identified by its respective protocol number. Well-known protocol numbers include ICMP(1), TCP(6), and UDP(17).
- protocol-number
-
Specifies the protocol number value to be configured as a match criterion.
- protocol-name
-
Specifies the protocol name to be configured as a match criterion.
Platforms
All
match
Syntax
match field-value instance instance-id
no match field-value
Context
[Tree] (config>qos>queue-group-redirect-list match)
Full Context
configure qos queue-group-redirect-list match
Description
This command configures the value of the field in the ingress or egress packet which, when matched, will cause the packet to be redirected to the specified queue group instance. The field-value is dependent on the setting of the type and therefore must be a valid VXLAN VNI.
A maximum of 16 match statements are supported in a queue group redirect list.
The no form of this command removes the match statement from the redirect list.
Parameters
- field-value
-
Specifies the value of the field in the ingress or egress packet which, when matched, will cause the packet to be redirected to the specified queue group instance. Because the only permitted type is vxlan-vni, the field must be a valid VXLAN VNI. The VNI can be specified in any of the available formats but is always shown in decimal.
- instance-id
-
Specifies the instance of the queue group template to which the VXLAN traffic is redirected. The traffic can be redirected to the default instance, which is the instance specified with the QoS policy under the SAP ingress or egress.
Platforms
All
match
Syntax
match [protocol protocol-id]
match protocol none
no match
Context
[Tree] (config>filter>ip-exception>entry match)
Full Context
configure filter ip-exception entry match
Description
Commands in this context enter match criteria for the filter entry. When the match criteria have been satisfied the action associated with the match criteria is executed.
A match context may consist of multiple match criteria, but multiple match statements cannot be entered per entry. More precisely, the command can be entered multiple times but this only results in modifying the protocol-id. and does not affect the underlying match criteria configuration.
The no form of the command removes all the match criteria from the filter entry and sets the protocol-id of the match command to none (keyword). As per above, match protocol none is however not equivalent to no match.
Default
match protocol none
Parameters
- protocol-id
-
Sets an IP protocol to be used as an IP filter match criterion. The protocol type, such as TCP or UDP, is identified by its respective protocol number.
Platforms
VSR
match
Syntax
match [{protocol protocol-id | protocol-list protocol-list-name}]
match protocol none
no match
Context
[Tree] (config>filter>ip-filter>entry match)
Full Context
configure filter ip-filter entry match
Description
Commands in this context enter match criteria for the filter entry. When the match criteria have been satisfied, the action associated with the match criteria is executed.
A match context may consist of multiple match criteria, but multiple match statements cannot be created per entry. More precisely, the protocol command can be entered multiple times but this only results in modifying the protocol-id. Matching on more than one protocol can be achieved using the protocol-list match criteria in an IP filter policy.
The no form of the command removes all the match criteria from the filter entry and sets the protocol-id of the match command to none. However, match protocol none is not equivalent to no match.
Default
match protocol none
Parameters
- protocol-id
-
protocol-number | protocol-name
- protocol-number
-
Specifies the protocol number value to be configured as a match criterion. The value can be expressed as a decimal integer, or in hexadecimal or binary format.
- protocol-name
-
Specifies the protocol name to be configured as a match criterion.
- protocol-list-name
-
Specifies the name of the protocol list, up to 32 characters.
Platforms
All
match
Syntax
match [next-header next-header]
no match
Context
[Tree] (config>filter>ipv6-exception>entry match)
Full Context
configure filter ipv6-exception entry match
Description
Commands in this context enter match criteria for the IPv6 filter exception. When the match criteria have been satisfied, the action associated with the match criteria is executed.
The no form of the command removes all the match criteria from the IPv6 filter exception.
Parameters
- next-header
-
protocol-number, protocol-name
Specifies the next header to match.
- protocol-number
-
Specifies the protocol number value to be configured as a match criterion.
- protocol-name
-
Specifies the protocol name to be configured as a match criterion.
Platforms
VSR
match
Syntax
match [{next-header protocol-id | next-header-list protocol-list-name}]
match next-header none
no match
Context
[Tree] (config>filter>ipv6-filter>entry match)
Full Context
configure filter ipv6-filter entry match
Description
Commands in this context enter match criteria for the filter entry. When the match criteria have been satisfied, the action associated with the match criteria is executed.
A match context may consist of multiple match criteria, but multiple match statements cannot be created per entry. More precisely, the next-header command can be entered multiple times, but this only results in modifying the protocol-id. Matching on more than one protocol can be achieved using the next-header-list match criteria.
The no form of the command removes all the match criteria from the filter entry and sets the protocol-id of the match command to none. However, match next-header none is not equivalent to no match.
Default
match next-header none
Parameters
- next-header
-
protocol-number, protocol-name
Specifies the IPv6 next header to match. This parameter is analogous to the protocol parameter used in IPv4 filter match command.
- protocol-number
-
Specifies the protocol number value to be configured as a match criterion.
- protocol-name
-
Specifies the protocol name to be configured as a match criterion.
- protocol-list-name
-
Specifies the name of the protocol list, up to 32 characters.
Platforms
All
match
Syntax
match [frame-type {802dot3 | 802dot2-llc | 802dot2-snap | ethernet_II}]
no match
Context
[Tree] (config>filter>mac-filter>entry match)
Full Context
configure filter mac-filter entry match
Description
This command creates the context for entering/editing match criteria for the filter entry and specifies an Ethernet frame type for the entry.
A match context may consist of multiple match criteria, but multiple match statements cannot be entered per entry.
The no form of the command removes the match criteria for the entry-id.
Parameters
- frame-type
-
Keyword used to configure an Ethernet frame type to be used for the MAC filter match criteria.
- 802dot3
-
Specifies the frame type is Ethernet IEEE 802.3.
- 802dot2-llc
-
Specifies the frame type is Ethernet IEEE 802.2 LLC.
- 802dot2-snap
-
Specifies the frame type is Ethernet IEEE 802.2 SNAP.
- ethernet_II
-
Specifies the frame type is Ethernet Type II.
Platforms
All
match
Syntax
[no] match
Context
[Tree] (config>log>filter>filter-id>entry match)
Full Context
configure log filter filter-id entry match
Description
This command creates context to enter/edit match criteria for a filter entry. When the match criteria is satisfied, the action associated with the entry is executed.
If more than one match parameter (within one match statement) is specified, then all the criteria must be satisfied (AND functional) before the action associated with the match is executed.
Use the application command to display a list of the valid applications.
Match context can consist of multiple match parameters (application, event-number, severity, subject), but multiple match statements cannot be entered per entry.
The no form of this command removes the match criteria for the entry-id.
match
Syntax
match [frame-type frame-type]
no match
Context
[Tree] (config>system>security>mgmt-access-filter>mac-filter>entry match)
Full Context
configure system security management-access-filter mac-filter entry match
Description
This command configures math criteria for this MAC filter entry.
Parameters
- frame-type
-
Specifies the type of MAC frame to use as match criteria.
Platforms
All
match
Syntax
match [protocol protocol-id]
no match
Context
[Tree] (cfg>sys>sec>cpm>ip-filter>entry match)
Full Context
configure system security cpm-filter ip-filter entry match
Description
Commands in this context enter match criteria for the filter entry. When the match criteria have been satisfied the action associated with the match criteria is executed. If more than one match criteria (within one match statement) are configured then all criteria must be satisfied (AND function) before the action associated with the match is executed.
A match context may consist of multiple match criteria, but multiple match statements cannot be entered per entry.
The no form of this command removes the match criteria for the entry-id.
Parameters
- protocol
-
Sets an IP protocol to be used as an IP filter match criterion. The protocol type such as TCP or UDP is identified by its respective protocol number.
- protocol-id
-
Sets the decimal value representing the IP protocol to be used as an IP filter match criterion. Well known protocol numbers include ICMP(1), TCP(6), UDP(17). The no form the command removes the protocol from the match criteria.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
match
Syntax
match [next-header next-header]
no match
Context
[Tree] (cfg>sys>sec>cpm>ipv6-filter>entry match)
Full Context
configure system security cpm-filter ipv6-filter entry match
Description
This command specifies match criteria for the IP filter entry.
The no form of this command removes the match criteria for the entry-id.
Parameters
- next-header
-
protocol-number, protocol-name
Specifies the next header to match.
The protocol type such as TCP, UDP or OSPF is identified by its respective protocol number. Well-known protocol numbers include ICMP(1), TCP(6) and UDP(17).
- protocol-number
-
Specifies the protocol number value to be configured as a match criterion.
- protocol-name
-
Specifies the protocol name to be configured as a match criterion.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
match
Syntax
match command-string
no match
Context
[Tree] (config>system>security>profile>entry match)
Full Context
configure system security profile entry match
Description
This command configures a command or subtree commands in subordinate command levels are specified.
Because the OS exits when the first match is found, subordinate levels cannot be modified with subsequent action commands. More specific action commands should be entered with a lower entry number or in a profile that is evaluated prior to this profile.
All commands below the hierarchy level of the matched command are denied.
The no form of this command removes a match condition.
Parameters
- command-string
-
Specifies the CLI command or CLI tree level that is the scope of the profile entry.
Platforms
All
match
Syntax
match
Context
[Tree] (config>router>bgp>group>dynamic-neighbor match)
Full Context
configure router bgp group dynamic-neighbor match
Description
This command configures match conditions for the dynamic neighbors.
Platforms
All
match-circuit-id
match-circuit-id
Syntax
[no] match-circuit-id
Context
[Tree] (config>service>vprn>sub-if>grp-if>dhcp match-circuit-id)
[Tree] (config>service>ies>sub-if>grp-if>dhcp match-circuit-id)
[Tree] (config>service>vprn>sub-if>dhcp match-circuit-id)
Full Context
configure service vprn subscriber-interface group-interface dhcp match-circuit-id
configure service ies subscriber-interface group-interface dhcp match-circuit-id
configure service vprn subscriber-interface dhcp match-circuit-id
Description
This command enables Option 82 circuit ID on relayed DHCP packet matching. For routed CO, the group interface DHCP relay process is stateful. When packets are relayed to the server the virtual router ID, transaction ID, SAP ID, and client hardware MAC address of the relayed packet are tracked.
When a response is received from the server the virtual router ID, transaction ID, and client hardware MAC address must be matched to determine the SAP on which to send the packet out. In some cases, the virtual router ID, transaction ID, and client hardware MAC address are not guaranteed to be unique.
When the match-circuit-id command is enabled this as part of the key is used to guarantee correctness in our lookup. This is only needed when dealing with an IP aware DSLAM that proxies the client hardware MAC address.
The no form of this command disables Option 82 circuit ID on relayed DHCP packet matching.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
match-list
match-list
Syntax
match-list ppp-match-type-1 [ppp-match-type-2]
no match-list
Context
[Tree] (config>subscr-mgmt>loc-user-db>ppp match-list)
Full Context
configure subscriber-mgmt local-user-db ppp match-list
Description
This command specifies the type of matching done to identify a host. There are different match-types for PPPoE hosts of which a maximum of three can be specified.
The no form of this command reverts to the default.
Parameters
- match-type-x
-
Specifies up to three matching types to identify a host.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
match-list
Syntax
match-list ipoe-match-type-1 [ipoe-match-type-2]
no match-list
Context
[Tree] (config>subscr-mgmt>loc-user-db>ipoe match-list)
Full Context
configure subscriber-mgmt local-user-db ipoe match-list
Description
This command specifies the type of matching done to identify a host. There are different match-types for IPoE hosts of which a maximum of four can be specified.
The no form of this command reverts to the default.
Parameters
- match-type-x
-
Specifies up to four matching types to identify a host.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
match-list
Syntax
match-list
Context
[Tree] (config>ipsec>client-db match-list)
Full Context
configure ipsec client-db match-list
Description
This command enables the match list context on a client database. The match list defines the match input used during IPsec’s tunnel setup. If there are multiple inputs configured in the match list, then they all must have matches before the system considers a client entry is a match.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
match-list
Syntax
match-list
Context
[Tree] (config>qos match-list)
Full Context
configure qos match-list
Description
This command is used to enter the context to create or edit match lists used in QoS policies.
Platforms
All
match-list
Syntax
match-list
Context
[Tree] (config>filter match-list)
Full Context
configure filter match-list
Description
This command enables the configuration context for match lists to be used in filter policies (IOM/FP and CPM).
Platforms
All
match-peer-id-to-cert
match-peer-id-to-cert
Syntax
[no] match-peer-id-to-cert
Context
[Tree] (config>ipsec>ike-policy match-peer-id-to-cert)
Full Context
configure ipsec ike-policy match-peer-id-to-cert
Description
This command enables checking the IKE peer's ID matches the peer's certificate when performing certificate authentication.
Default
no match-peer-id-to-cert
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
match-qinq-dot1p
match-qinq-dot1p
Syntax
match-qinq-dot1p {top | bottom}
no match-qinq-dot1p
Context
[Tree] (config>service>vpls>sap>ingress match-qinq-dot1p)
[Tree] (config>service>ies>if>sap>ingress match-qinq-dot1p)
[Tree] (config>service>vprn>sub-if>grp-if>sap>ingress match-qinq-dot1p)
[Tree] (config>service>ies>sub-if>grp-if>sap>ingress match-qinq-dot1p)
Full Context
configure service vpls sap ingress match-qinq-dot1p
configure service ies interface sap ingress match-qinq-dot1p
configure service vprn subscriber-interface group-interface sap ingress match-qinq-dot1p
configure service ies subscriber-interface group-interface sap ingress match-qinq-dot1p
Description
This command specifies which dot1Q tag position dot1P bits in a QinQ encapsulated packet should be used to evaluate dot1P QoS classification.
The match-qinq-dot1p command allows the top or bottom PBits to be used when evaluating the applied sap-ingress QoS policy’s dot1P entries. The top and bottom keywords specify which position should be evaluated for QinQ encapsulated packets.
By default, the bottom-most service delineating dot1Q tag’s dot1P bits are used. Default QinQ and TopQ SAP Dot1P Evaluation defines the default behavior for dot1P evaluation when the match-qinq-dot1p command is not executed.
|
Port/SAP Type |
Existing Packet Tags |
PBits Used for Match |
|---|---|---|
|
Null |
None |
None |
|
Null |
Dot1P (VLAN-ID 0) |
Dot1P PBits |
|
Null |
Dot1Q |
Dot1Q PBits |
|
Null |
TopQ BottomQ |
TopQ PBits |
|
Null |
TopQ (No BottomQ) |
TopQ PBits |
|
Dot1Q |
None (Default SAP) |
None |
|
Dot1Q |
Dot1P (Default SAP VLAN-ID 0) |
Dot1P PBits |
|
Dot1Q |
Dot1Q |
Dot1Q PBits |
|
QinQ/TopQ |
TopQ |
TopQ PBits |
|
QinQ/TopQ |
TopQ BottomQ |
TopQ PBits |
|
QinQ/TopQ |
TopQ BottomQ |
BottomQ PBits |
The no form of this command restores the default dot1p evaluation behavior for the SAP.
Default
no match-qinq-dot1p (no filtering based on p-bits)
(top or bottom must be specified to override the default QinQ dot1p behavior)
Parameters
- top
-
The top parameter is mutually exclusive to the bottom parameter. When the top parameter is specified, the topmost PBits are used (if existing) to match any dot1p dot1p-value entries. Top Position QinQ and TopQ SAP Dot1P Evaluation defines the dot1p evaluation behavior when the top parameter is specified.
Table 8. Top Position QinQ and TopQ SAP Dot1P Evaluation Port/SAP Type
Existing Packet Tags
PBits Used for Match
Null
None
None
Null
Dot1P (VLAN-ID 0)
Dot1P PBits
Null
Dot1Q
Dot1Q PBits
Null
TopQ BottomQ
TopQ PBits
Null
TopQ (No BottomQ)
TopQ PBits
Dot1Q
None (Default SAP)
None
Dot1Q
Dot1P (Default SAP VLAN-ID 0)
Dot1P PBits
Dot1Q
Dot1Q
Dot1Q PBits
QinQ/TopQ
TopQ
TopQ PBits
QinQ/TopQ
TopQ BottomQ
TopQ PBits
QinQ/QinQ
TopQ BottomQ
TopQ PBits
- bottom
-
The bottom parameter is mutually exclusive to the top parameter. When the bottom parameter is specified, the bottom most PBits are used (if existing) to match any dot1p dot1p-value entries. Bottom Position QinQ and TopQ SAP Dot1P Evaluation defines the dot1p evaluation behavior when the bottom parameter is specified.
Table 9. Bottom Position QinQ and TopQ SAP Dot1P Evaluation Port/SAP Type
Existing Packet Tags
PBits Used for Match
Null
None
None
Null
Dot1P (VLAN-ID 0)
Dot1P PBits
Null
Dot1Q
Dot1Q PBits
Null
TopQ BottomQ
BottomQ PBits
Null
TopQ (No BottomQ)
TopQ PBits
Dot1Q
None (Default SAP)
None
Dot1Q
Dot1P (Default SAP VLAN-ID 0)
Dot1P PBits
Dot1Q
Dot1Q
Dot1Q PBits
QinQ/TopQ
TopQ
TopQ PBits
QinQ/TopQ
TopQ BottomQ
BottomQ PBits
QinQ/QinQ
TopQ BottomQ
BottomQ PBits
Platforms
All
- configure service vpls sap ingress match-qinq-dot1p
- configure service ies interface sap ingress match-qinq-dot1p
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
- configure service vprn subscriber-interface group-interface sap ingress match-qinq-dot1p
- configure service ies subscriber-interface group-interface sap ingress match-qinq-dot1p
match-qinq-dot1p
Syntax
match-qinq-dot1p {top | bottom}
no match-qinq-dot1p de
Context
[Tree] (config>service>ipipe>sap>ingress match-qinq-dot1p)
[Tree] (config>service>epipe>sap>ingress match-qinq-dot1p)
Full Context
configure service ipipe sap ingress match-qinq-dot1p
configure service epipe sap ingress match-qinq-dot1p
Description
This command specifies which Dot1Q tag position Dot1P bits in a QinQ encapsulated packet should be used to evaluate Dot1P QoS classification.
The match-qinq-dot1p command allows the top or bottom PBits to be used when evaluating the applied sap-ingress QoS policy’s Dot1P entries. The top and bottom keywords specify which position should be evaluated for QinQ encapsulated packets.
The setting also applies to classification based on the DE indicator bit.
The no form of this command reverts the dot1p and de bits matching to the default tag.
By default, the bottom most service delineating Dot1Q tags Dot1P bits are used. Default QinQ and TopQ SAP Dot1P Evaluation defines the default behavior for Dot1P evaluation. Top or bottom must be specified to override the default QinQ dot1p behavior.
|
Port/SAP Type |
Existing Packet Tags |
PBits Used for Match |
|---|---|---|
|
Null |
None |
None |
|
Null |
Dot1P (VLAN ID 0) |
Dot1P PBits |
|
Null |
Dot1Q |
Dot1Q PBits |
|
Null |
TopQ BottomQ |
TopQ PBits |
|
Null |
TopQ (No BottomQ) |
TopQ PBits |
|
Dot1Q |
None (Default SAP) |
None |
|
Dot1Q |
Dot1P (Default SAP VLAN ID 0) |
Dot1P PBits |
|
Dot1Q |
Dot1Q |
Dot1Q PBits |
|
QinQ / TopQ |
TopQ |
TopQ PBits |
|
QinQ / TopQ |
TopQ BottomQ |
TopQ PBits |
|
QinQ / QinQ |
TopQ BottomQ |
BottomQ PBits |
Default
no match-qinq-dot1p (no filtering based on p-bits)
Parameters
- top
-
The top parameter is mutually exclusive to the bottom parameter. When the top parameter is specified, the top most PBits are used (if existing) to match any dot1p dot1p-value entries. Top Position QinQ dpt1p Evaluation Behavior defines the dot1p evaluation behavior when the top parameter is specified.
Table 11. Top Position QinQ dpt1p Evaluation Behavior Port/SAP Type
Existing Packet Tags
PBits Used for Match
Null
None
None
Null
Dot1P (VLAN ID 0)
Dot1P PBits
Null
Dot1Q
Dot1Q PBits
Null
TopQ BottomQ
TopQ PBits
Null
TopQ (No BottomQ)
TopQ PBits
Dot1Q
None (Default SAP)
None
Dot1Q
Dot1P (Default SAP VLAN ID 0)
Dot1P PBits
Dot1Q
Dot1Q
Dot1Q PBits
QinQ / TopQ
TopQ
TopQ PBits
QinQ / TopQ
TopQ BottomQ
TopQ PBits
QinQ / QinQ
TopQ BottomQ
TopQ PBits
- bottom
-
The bottom parameter and the top parameter are mutually exclusive. When the bottom parameter is specified, the bottom most PBits are used (if existing) to match any dot1p dot1p-value entries. Bottom Position QinQ and TopQ SAP Dot1P Evaluation defines the dot1p evaluation behavior when the bottom parameter is specified.
Table 12. Bottom Position QinQ and TopQ SAP Dot1P Evaluation Port/SAP Type
Existing Packet Tags
PBits Used for Match
Null
None
None
Null
Dot1P (VLAN ID 0)
Dot1P PBits
Null
Dot1Q
Dot1Q PBits
Null
TopQ BottomQ
TopQ PBits
Null
TopQ (No BottomQ)
TopQ PBits
Dot1Q
None (Default SAP)
None
Dot1Q
Dot1P (Default SAP VLAN ID 0)
Dot1P PBits
Dot1Q
Dot1Q
Dot1Q PBits
QinQ / TopQ
TopQ
TopQ PBits
QinQ / TopQ
TopQ BottomQ
BottomQ PBits
QinQ / QinQ
TopQ BottomQ
BottomQ PBits
Table 13. Egress SAP Types Egress SAP Type
Ingress Packet Preserved Dot1P State
Marked (or Remarked) PBits
Null
No preserved Dot1P bits
None
Null
Preserved Dot1P bits
Preserved tag PBits remarked using dot1p-value
Dot1Q
No preserved Dot1P bits
New PBits marked using dot1p-value
Dot1Q
Preserved Dot1P bits
Preserved tag PBits remarked using dot1p-value
TopQ
No preserved Dot1P bits
TopQ PBits marked using dot1p-value
TopQ
Preserved Dot1P bits (used as TopQ and BottomQ PBits)
TopQ PBits marked using dot1p-value, BottomQ PBits preserved
QinQ
No preserved Dot1P bits
TopQ PBits and BottomQ PBits marked using dot1p-value
QinQ
Preserved Dot1P bits (used as TopQ and BottomQ PBits)
TopQ PBits and BottomQ PBits marked using dot1p-value
The QinQ and TopQ SAP PBit/DEI bit marking follows the default behavior defined in the preceding table when qinq-mark-top-only is not specified.
The dot1p dot1p-value command must be configured without the qinq-mark-top-only parameter to remove the TopQ PBits only marking restriction.
A QinQ-encapsulated Ethernet port can have two different sap types:
For a TopQ SAP type, only the outer (top) tag is explicitly specified. For example, sap 1/1/1:10.*
For QinQ SAP type, both inner (bottom) and outer (top) tags are explicitly specified. For example, sap 1/1/1:10.100.
Platforms
All
match-qinq-dot1p
Syntax
match-qinq-dot1p {top | bottom}
no match-qinq-dot1p
Context
[Tree] (config>service>vprn>if>sap>ingress match-qinq-dot1p)
Full Context
configure service vprn interface sap ingress match-qinq-dot1p
Description
This command specifies which Dot1Q tag position Dot1P bits in a QinQ encapsulated packet should be used to evaluate Dot1P QoS classification.
The match-qinq-dot1p command allows the top or bottom PBits to be used when evaluating the applied sap-ingress QoS policy’s Dot1P entries. The top and bottom keywords specify which position should be evaluated for QinQ encapsulated packets.
The no form of this command restores the default dot1p evaluation behavior for the SAP.
By default, the bottom most service delineating Dot1Q tags Dot1P bits are used. Dot1P Default Behavior defines the default behavior for Dot1P evaluation when the match-qinq-dot1p command is not executed.
|
Port / SAP Type |
Existing Packet Tags |
PBits Used for Match |
|---|---|---|
|
null |
none |
none |
|
null |
Dot1P (VLAN-ID 0) |
Dot1P PBits |
|
null |
— |
Dot1Q PBits |
|
null |
TopQ BottomQ |
TopQ PBits |
|
null |
TopQ (No BottomQ) |
TopQ PBits |
|
Dot1Q |
none (Default SAP) |
none |
|
Dot1Q |
Dot1P (Default SAP VLAN-ID 0) |
Dot1P PBits |
|
Dot1Q |
Dot1Q |
Dot1Q PBits |
|
QinQ / TopQ |
TopQ |
TopQ PBits |
|
QinQ / TopQ |
TopQ BottomQ |
TopQ PBits |
|
QinQ / QinQ |
TopQ BottomQ |
BottomQ PBits |
Default
no match-qinq-dot1p - No filtering based on p-bits.
top or bottom must be specified to override the default QinQ dot1p behavior.
Parameters
- top
-
The top parameter is mutually exclusive to the bottom parameter. When the top parameter is specified, the top most PBits are used (if existing) to match any dot1p dot1p-value entries. Dot1P Evaluation Behavior defines the dot1p evaluation behavior when the top parameter is specified.
Table 15. Dot1P Evaluation Behavior Port / SAP Type
Existing Packet Tags
PBits Used for Match
null
none
none
null
Dot1P (VLAN-ID 0)
Dot1P PBits
null
Dot1Q
Dot1Q PBits
null
TopQ BottomQ
TopQ PBits
null
TopQ (No BottomQ)
TopQ PBits
Dot1Q
none (Default SAP)
none
Dot1Q
Dot1P (Default SAP VLAN-ID 0)
Dot1P PBits
Dot1Q
Dot1Q
Dot1Q PBits
QinQ / TopQ
TopQ
TopQ PBits
QinQ / TopQ
TopQ BottomQ
TopQ PBits
QinQ / TopQ
TopQ BottomQ
TopQ PBits
- bottom
-
The bottom parameter is mutually exclusive to the top parameter. When the bottom parameter is specified, the bottom most PBits are used (if existing) to match any dot1p dot1p-value entries. The following tables define the bottom position QinQ and TopQ SAP dot1p evaluation and the default dot1p explicit marking actions.
Table 16. Bottom Position QinQ and TopQ SAP Dot1P Evaluation Port / SAP Type
Existing Packet Tags
PBits Used for Match
null
none
none
null
Dot1P (VLAN-ID 0)
Dot1P PBits
null
Dot1Q
Dot1Q PBits
null
TopQ BottomQ
BottomQ PBits
null
TopQ (No BottomQ)
TopQ PBits
Dot1Q
none (default SAP)
none
Dot1Q
Dot1P (default SAP VLAN-ID 0)
Dot1P PBits
Dot1Q
Dot1Q
Dot1Q PBits
QinQ / TopQ
TopQ
TopQ PBits
QinQ / TopQ
TopQ BottomQ
BottomQ PBits
QinQ / QinQ
TopQ BottomQ
BottomQ PBits
Table 17. Default Dot1P Explicit Marking Actions Egress SAP Type
Ingress Packet Preserved Dot1P State
Marked (or Remarked) PBits
null
no preserved Dot1P bits
none
null
preserved Dot1P bits
preserved tag PBits remarked using dot1p-value
Dot1Q
no preserved Dot1P bits
new PBits marked using dot1p-value
Dot1Q
preserved Dot1P bits
preserved tag PBits remarked using dot1p-value
TopQ
no preserved Dot1P bits
TopQ PBits marked using dot1p-value
TopQ
preserved Dot1P bits (used as TopQ and BottomQ PBits)
TopQ PBits marked using dot1p-value, BottomQ PBits preserved
QinQ
no preserved Dot1P bits
TopQ PBits and BottomQ PBits marked using dot1p-value
QinQ
preserved Dot1P bits (used as TopQ and BottomQ PBits)
TopQ PBits and BottomQ PBits marked using dot1p-value
The dot1p dot1p-value command must be configured without the qinq-mark-top-only parameter to remove the TopQ PBits only marking restriction.
Platforms
All
match-radius-proxy-cache
match-radius-proxy-cache
Syntax
match-radius-proxy-cache
Context
[Tree] (config>subscr-mgmt>loc-user-db>ipoe>host match-radius-proxy-cache)
Full Context
configure subscriber-mgmt local-user-db ipoe host match-radius-proxy-cache
Description
Commands in this context configure RADIUS proxy cache match parameters.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
max
max
Syntax
max num-sessions
no max
Context
[Tree] (config>service>nat>up-nat-policy>session-limits max)
[Tree] (config>service>nat>nat-policy>session-limits max)
[Tree] (config>service>nat>firewall-policy>session-limits max)
Full Context
configure service nat up-nat-policy session-limits max
configure service nat nat-policy session-limits max
configure service nat firewall-policy session-limits max
Description
This command configures the session limit of this policy. The session limit is the maximum number of sessions allowed for a subscriber associated with this policy.
Default
max 65535
Parameters
- num-sessions
-
Specifies the session limit.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
- configure service nat nat-policy session-limits max
- configure service nat up-nat-policy session-limits max
7750 SR, 7750 SR-e, 7750 SR-s, VSR
- configure service nat firewall-policy session-limits max
max-admin-down-time
max-admin-down-time
Syntax
max-admin-down-time [[down-interval] | infinite]
no max-admin-down-time
Context
[Tree] (config>lag>bfd>family max-admin-down-time)
Full Context
configure lag bfd family max-admin-down-time
Description
This command specifies the maximum amount of time the router will continue to forward traffic over a link after the micro-BFD sessions has transitioned to a Down state because it received an ADMIN-DOWN state from the far-end. This timer provide the administrator the configured amount of time to disable or de-provision the micro-BFD session on the local node before forwarding is halted over the associated link(s).
The no form of this command removes the time interval from the configuration.
Default
max-admin-down-time 0
Parameters
- down-interval
-
Specifies the amount of time, in seconds.
- infinite
-
Specifies no end time to forward traffic.
Platforms
All
max-advertisement
max-advertisement
Syntax
max-advertisement seconds
no max-advertisement
Context
[Tree] (config>service>vprn>sub-if>grp-if>ipv6 max-advertisement)
[Tree] (config>service>vprn>sub-if>grp-if>ipv6>rtr-adv max-advertisement)
[Tree] (config>service>ies>sub-if>grp-if>ipv6 max-advertisement)
[Tree] (config>service>vprn>sub-if>ipv6>rtr-adv max-advertisement)
[Tree] (config>service>ies>sub-if>grp-if>ipv6>rtr-adv max-advertisement)
[Tree] (config>subscr-mgmt>rtr-adv-plcy max-advertisement)
[Tree] (config>service>vprn>router-advert>if max-advertisement)
[Tree] (config>service>ies>sub-if>ipv6>rtr-adv max-advertisement)
Full Context
configure service vprn subscriber-interface group-interface ipv6 max-advertisement
configure service vprn subscriber-interface group-interface ipv6 router-advertisements max-advertisement
configure service ies subscriber-interface group-interface ipv6 max-advertisement
configure service vprn subscriber-interface ipv6 router-advertisements max-advertisement
configure service ies subscriber-interface group-interface ipv6 router-advertisements max-advertisement
configure subscriber-mgmt router-advertisement-policy max-advertisement
configure service vprn router-advert interface max-advertisement
configure service ies subscriber-interface ipv6 router-advertisements max-advertisement
Description
This command specifies the maximum time allowed between sending unsolicited router advertisements from this interface.
The no form of this command reverts to the default.
Default
max-advertisement 1800
Parameters
- seconds
-
Specifies the maximum advertisement interval, in seconds.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
max-advertisement-interval
max-advertisement-interval
Syntax
[no] max-advertisement-interval seconds
Context
[Tree] (config>service>vprn>router-advert>if max-advertisement-interval)
[Tree] (config>router>router-advert>if max-advertisement-interval)
Full Context
configure service vprn router-advertisement interface max-advertisement-interval
configure router router-advertisement interface max-advertisement-interval
Description
This command configures the maximum interval between sending router advertisement messages.
Default
max-advertisement-interval 600
Parameters
- seconds
-
Specifies the maximum interval in seconds between sending router advertisement messages.
Platforms
All
max-age
max-age
Syntax
max-age max-age
no max-age [max-age]
Context
[Tree] (config>service>template>vpls-template>stp max-age)
[Tree] (config>service>vpls>stp max-age)
Full Context
configure service template vpls-template stp max-age
configure service vpls stp max-age
Description
This command indicates how many hops a BPDU can traverse the network starting from the root bridge. The message age field in a BPDU transmitted by the root bridge is initialized to 0. Each other bridge will take the message_age value from BPDUs received on their root port and increment this value by 1. The message_age therefore reflects the distance from the root bridge. BPDUs with a message age exceeding max-age are ignored.
STP uses the max-age value configured in the root bridge. This value is propagated to the other bridges via the BPDUs.
The no form of this command returns the max age to the default value.
Default
max-age 20
Parameters
- max-age
-
The max info age for the STP instance in seconds. Allowed values are integers in the range 6 to 40.
Platforms
All
max-attempts
max-attempts
Syntax
max-attempts count
max-attempts infinite
no max-attempts
Context
[Tree] (config>subscr-mgmt>diam-appl-plcy>gy>efh>interim-c max-attempts)
Full Context
configure subscriber-mgmt diameter-application-policy gy extended-failure-handling interim-credit max-attempts
Description
This command configures the maximum number of attempts made to establish a new Diameter Gy session with the Online Charging Server (OCS) when Extended Failure Handling (EFH) is active.
A new attempt is made when the volume or time interim credit of a rating group is consumed or when the validity time expires for a rating group.
When the maximum number of attempts is reached, the user session associated with the Diameter session is terminated (the corresponding subscriber hosts are deleted from the system).
The no form of this command resets the value to the default value.
Default
max-attempts 10
Parameters
- count
-
Specifies the maximum number attempts that is made to establish a Diameter Gy session with the OCS when EFH is active.
- infinite
-
Specifies that an unlimited number of attempts is made to establish a Diameter Gy session with the OCS when EFH is active.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
max-auth-req
max-auth-req
Syntax
max-auth-req max-auth-request
Context
[Tree] (config>port>ethernet>dot1x max-auth-req)
Full Context
configure port ethernet dot1x max-auth-req
Description
This command configures the maximum number of times that the router will send an access request RADIUS message to the RADIUS server. If a reply is not received from the RADIUS server after the specified number attempts, the 802.1x authentication procedure is considered to have failed.
The no form of this command returns the value to the default.
Default
max-auth-req 2
Parameters
- max-auth-request
-
The maximum number of RADIUS retries.
Platforms
All
max-avg
max-avg
Syntax
max-avg percent
no max-avg
Context
[Tree] (config>qos>slope-policy>high-slope max-avg)
[Tree] (config>qos>slope-policy>exceed-slope max-avg)
[Tree] (config>qos>slope-policy>low-slope max-avg)
[Tree] (config>qos>slope-policy>highplus-slope max-avg)
Full Context
configure qos slope-policy high-slope max-avg
configure qos slope-policy exceed-slope max-avg
configure qos slope-policy low-slope max-avg
configure qos slope-policy highplus-slope max-avg
Description
Sets the exceed, low, high, or highplus Random Early Detection (RED) slope position for the shared buffer average utilization value where the packet discard probability rises directly to one. The percent parameter is expressed as a percentage of the shared buffer size.
The no form of this command restores the max-avg value to the default setting. If the current start-avg setting is larger than the default, an error will occur and the max-avg setting will not be changed to the default.
Default
max-avg 100 - Highplus slope default is 100% buffer utilization before discard probability is 1.
max-avg 90 — High slope default is 90% buffer utilization before discard probability is 1.
max-avg 75 — Low slope default is 75% buffer utilization before discard probability is 1.
max-avg 55 — Exceed slope default is 55% buffer utilization before discard probability is 1.
Parameters
- percent
-
The percentage of the shared buffer space for the buffer pool at which point the drop probability becomes one. The value entered must be greater or equal to the current setting of start-avg. If the entered value is smaller than the current value of start-avg, an error will occur and no change will take place.
Platforms
All
max-bandwidth
max-bandwidth
Syntax
max-bandwidth number-links
no max-bandwidth
Context
[Tree] (config>port>ml-bundle>ima max-bandwidth)
Full Context
configure port multilink-bundle ima max-bandwidth
Description
This command specifies the number of links used to determine the maximum configurable bandwidth that is allowed to be used for this IMA group.
The maximum bandwidth is computed as:
Maximum Configurable ATM Bandwidth (MCAB) =
(number-links) * (M-1)/M * (2048/2049) * primary member link speed
|
Where: |
M is the IMA frame size (128) |
|
Primary member link speed is either E-1 — 1920 kb/s or DS-1 — 1539 kb/s. E-1 speed is used for a group with no members. |
The total ATM bandwidth of services over shaped VCs cannot exceed the MCAB value as result of adding more services or removing member links.
The no form of this command resets the max-bandwidth to its default value.
Default
max-bandwidth 8
Parameters
- number-links
-
Specifies the number of links that determines the maximum configurable bandwidth that is allowed to be used for this IMA group.
Platforms
7450 ESS, 7750 SR-7/12/12e
max-bandwidth
Syntax
max-bandwidth bandwidth-in-mbps
no max-bandwidth
Context
[Tree] (config>router>mpls>lsp>auto-bandwidth max-bandwidth)
[Tree] (config>router>mpls>lsp-template>auto-bandwidth max-bandwidth)
Full Context
configure router mpls lsp auto-bandwidth max-bandwidth
configure router mpls lsp-template auto-bandwidth max-bandwidth
Description
This command configures the maximum bandwidth that auto-bandwidth allocation is allowed to request for an LSP.
The LSP maximum applies whether the bandwidth adjustment is triggered by normal adjust-interval expiry, the overflow limit having been reached, or manual request.
The no form of this command reverts to the default value.
The max-bandwidth must be greater than the min-bandwidth.
Default
max-bandwidth 100000
Parameters
- bandwidth-in-mbps
-
Specifies the maximum bandwidth in Mb/s.
Platforms
All
max-burst
max-burst
Syntax
max-burst number
no max-burst
Context
[Tree] (config>router>rsvp>msg-pacing max-burst)
Full Context
configure router rsvp msg-pacing max-burst
Description
This command specifies the maximum number of RSVP messages that are sent in the specified period under normal operating conditions.
Default
max-burst 650
Parameters
- number
-
Specifies the maximum number of RSVP messages to be sent in increments of 10.
Platforms
All
max-burst-size
max-burst-size
Syntax
max-burst-size size [bytes | kilobytes]
no max-burst-size
Context
[Tree] (config>router>policy-acct-template>policer max-burst-size)
Full Context
configure router policy-acct-template policer max-burst-size
Description
This command configures the MBS for the policer. When this threshold value is exceeded, packets are considered violating and are dropped.
When this value is not configured, the default value is dependent on the peak-rate setting. When peak-rate is set to max or is greater than or equal to the FP capacity (overriding an explicitly configured MBS value), the default value is 16 megabytes; otherwise the value is capped at 3988 kilobytes with a minimum of 256 bytes.
The no form of this command reverts to the default value.
Parameters
- size
-
Specifies the maximum number of RSVP messages to be sent in increments of 10.
- bytes
-
Specifies that the value is in bytes.
- kilobytes
-
Specifies that the value is in kilobytes.
Platforms
7450 ESS, 7750 SR, 7750 SR-s, 7950 XRS
max-bypass-associations
max-bypass-associations
Syntax
max-bypass-associations integer
no max-bypass-associations
Context
[Tree] (config>router>mpls max-bypass-associations)
Full Context
configure router mpls max-bypass-associations
Description
This command allows the user to set a maximum number of LSP primary path associations with each manual or dynamic bypass LSP that is created in the system.
By default, a Point of Local Repair (PLR) node will associate a maximum of 1000 primary LSP paths with a given bypass before using the next available manual bypass or signaling a new dynamic bypass.
Note that a new bypass LSP may need to be signaled if the constraint of a given primary LSP path is not met by an existing bypass LSP even if the max-bypass-associations for this bypass LSP has not been reached.
The no form of this command reinstates the default value of this parameter.
Default
max-bypass-associations 1000
Parameters
- integer
-
Configures the number of LSP primary path associations
Platforms
All
max-bypass-plr-associations
max-bypass-plr-associations
Syntax
max-bypass-plr-associations plr-value
no max-bypass-plr-associations
Context
[Tree] (config>router>mpls max-bypass-plr-associations)
Full Context
configure router mpls max-bypass-plr-associations
Description
This command enables the configuration of the maximum number of Points of Local Repair (PLRs) per RSVP-TE bypass LSP.
A PLR summarizes the constraints applied to the computation of the path of the bypass LSP. It consists of the avoid link/node constraint, and potentially other TE constraints such as exclude SRLG, that are needed to protect against the failure of the primary path of the RSVP-TE LSP that is associated with this bypass LSP.
Additional PLRs with the same avoid link/node constraint are associated with the same bypass to minimize the number of bypass LSPs created. This command controls the maximum number of such PLRs.
Because MPLS saves only the PLR constraints of the first LSP that triggered the dynamic bypass creation, subsequent LSPs for the same avoid link/node and with the non-strict bypass SRLG disjointness enabled may be associated with the same bypass. This is even in cases where there exists a bypass LSP path that strictly satisfies the SRLG constraint.
When the maximum PLRs per bypass is configured with a value of 1, MPLS triggers the signaling of a new dynamic bypass LSP for each new PLR and saves each PLR constraint separately with its own bypass. As a result, when MPLS re-optimizes a bypass LSP it guarantees that SRLG disjointness of that PLR are checked and enforced.
The no form of this command returns the command to its default value.
Default
max-bypass-plr-associations 16
Parameters
- plr-value
-
Configures the number of LSP primary path associations
Platforms
All
max-cells
max-cells
Syntax
max-cells cell-count
no max-cells [cell-count]
Context
[Tree] (config>service>apipe>spoke-sdp>cell-concat max-cells)
Full Context
configure service apipe spoke-sdp cell-concatenation max-cells
Description
This command enables the configuration of the maximum number of ATM cells to accumulate into an MPLS packet. The remote peer will also signal the maximum number of concatenated cells it is willing to accept in an MPLS packet. When the lesser of (the configured value and the signaled value) number of cells is reached, the MPLS packet is queued for transmission onto the pseudowire. It is ensured that the MPLS packet MTU conforms to the configured service MTU.
The no form of this command sets max-cells to the value ‛1’ indicating that no concatenation will be performed.
Parameters
- cell-count
-
Specifies the maximum number of ATM cells to be accumulated into an MPLS packet before queuing the packet for transmission onto the pseudowire.
Platforms
7450 ESS, 7750 SR-7/12/12e, 7750 SR-a, 7750 SR-e, 7950 XRS
max-cleared
max-cleared
Syntax
max-cleared maximum
Context
[Tree] (config>system>alarms max-cleared)
Full Context
configure system alarms max-cleared
Description
This command configures the maximum number of cleared alarms that the system will store and display.
Default
max-cleared 500
Parameters
- maximum
-
Specifies the maximum number of cleared alarms, up to 500.
Platforms
All
max-completed
max-completed
Syntax
max-completed unsigned
Context
[Tree] (config>system>script-control>script-policy max-completed)
Full Context
configure system script-control script-policy max-completed
Description
This command is used to configure the maximum number of script run history status entries to keep.
Default
max-completed 1
Parameters
- unsigned
-
Specifies the maximum number of script run history status entries to keep.
Platforms
All
max-conn-prefix
max-conn-prefix
Syntax
max-conn-prefix count
no max-conn-prefix
Context
[Tree] (config>test-oam>twamp>server>prefix max-conn-prefix)
Full Context
configure test-oam twamp server prefix max-conn-prefix
Description
This command configures the maximum number of control connections by clients with an IP address in a specific prefix. A new control connection is rejected if accepting it would cause either the prefix limit defined by this command or the server limit (max-conn-server) to be exceeded.
The no form of this command returns the value to the default.
Default
max-conn-prefix 32
Parameters
- count
-
Specifies the maximum number of control connections.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
max-conn-server
max-conn-server
Syntax
max-conn-server count
no max-conn-server
Context
[Tree] (config>test-oam>twamp>server max-conn-server)
Full Context
configure test-oam twamp server max-conn-server
Description
This command configures the maximum number of TWAMP control connections from all TWAMP clients. A new control connection is rejected if accepting it would cause either this limit or a prefix limit (max-conn-prefix) to be exceeded.
The no form of this command returns the value to the default.
Default
max-conn-server 32
Parameters
- count
-
Specifies the maximum number of control connections.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
max-data-size
max-data-size
Syntax
max-data-size bytes
Context
[Tree] (config>sflow>receiver max-data-size)
Full Context
configure sflow receiver max-data-size
Description
This configures the maximum data size for sFlow UDP datagrams sent to the collector.
To restore default configuration, execute max-data-size 1400.
Default
max-data-size 1400
Parameters
- bytes
-
Specifies the data size.
Platforms
7750 SR, 7750 SR-s, 7950 XRS
max-debounce-time
max-debounce-time
Syntax
max-debounce-time max-debounce-time
no max-debounce-time
Context
[Tree] (config>redundancy>mc>peer>mcr>ring>in-band-control-path max-debounce-time)
[Tree] (config>redundancy>mc>peer>mc>l3-ring>in-band-control-path max-debounce-time)
Full Context
configure redundancy multi-chassis peer mc-ring ring in-band-control-path max-debounce-time
configure redundancy multi-chassis peer multi-chassis l3-ring in-band-control-path max-debounce-time
Description
This command configures the inband control path maximum debounce time.
The no form of this command reverts to the default.
Default
max-debounce-time 10
Parameters
- max-debounce-time
-
Specifies the maximum debounce time on the transition of the operational state of the inband control connection.
Platforms
All
max-decrement
max-decrement
Syntax
max-decrement {percent percent-of-admin-pir | rate rate-in-kilobits-per-second}
no max-decrement
Context
[Tree] (config>qos>adv-config-policy>child-control>offered-measurement max-decrement)
Full Context
configure qos adv-config-policy child-control offered-measurement max-decrement
Description
This command is used to limit how fast a child queue or policer can ‛give up’ bandwidth that it has been allotted from the virtual scheduler in a single iteration. If the child’s new offered rate has decreased by more than the maximum decrement limit, the system ignores the new offered rate and instead uses the old offered rate less the maximum decrement limit.
A possible reason to define a maximum decrement limit is to allow a child queue or policer to hold on to a portion of bandwidth that has been distributed by the parent virtual scheduler in case the child’s offered rate fluctuates in an erratic manor. The max-decrement limit has a dampening effect to changes in the offered rate.
A side effect of using a maximum decrement limit is that unused bandwidth allocated to the child queue or policer will not be given to another child as quickly. This may result in an underrun of the virtual scheduler’s aggregate rate.
The max-decrement limit has no effect on any increase in a child’s offered rate. If the rate increase is above the change sensitivity, the new offered rate is immediately used.
If the max-decrement command is used with a percent-based value, the decrement limit will be a function of the configured PIR value on the policer or queue. In this case, care should be taken that the child is either configured with an explicit PIR rate (other than max) or the child’s administrative PIR is defined using the percent-rate command with the local parameter enabled if an explicit value is not desired. When a maximum PIR is in use on the child, the system attempts to interpret the maximum child forwarding rate. This rate could be very large if the child is associated with multiple ingress or egress ports.
Except for the overall cap on the offered input into the virtual scheduler, the child’s administrative PIR has no effect on the calculated sensitivity if an explicit rate is specified.
If the child’s administrative PIR is modified while a percent based max-decrement is in effect, the system automatically uses the new relative maximum decrement limit value the next time the child’s offered rate is determined.
When the max-decrement command is not specified or removed, the virtual scheduler does not limit a decreasing offered rate to a specific limit.
The no form of this command is used to remove any currently configured maximum decrement limit for all child policers and queues associated with the policy.
Parameters
- percent-of-admin-pir
-
When the percent qualifier is used, this parameter specifies the percentage of the child’s administrative PIR that should be used as the decrement limit to offered rate change. If a value of 100 or 100.00 is used, the system will interpret this equivalent to no max-decrement.
- rate-in-kilobits-per-second
-
When the rate qualifier is used, this parameter specifies an explicit rate, in kb/s, that should be used as the child’s offered rate change sensitivity value. If a rate sensitivity of 0 is specified, the system interprets this equivalent to no max-decrement.
Platforms
All
max-delay
max-delay
Syntax
max-delay delay-time
no max-delay [delay-time]
Context
[Tree] (config>service>apipe>spoke-sdp>cell-concat max-delay)
Full Context
configure service apipe spoke-sdp cell-concatenation max-delay
Description
This command enables the configuration of the maximum amount of time to wait while performing ATM cell concatenation into an MPLS packet before transmitting the MPLS packet. This places an upper bound on the amount of delay introduced by the concatenation process. When this amount of time is reached from when the first ATM cell for this MPLS packet was received, the MPLS packet is queued for transmission onto the pseudowire.
The no form of this command resets max-delay to its default value.
Parameters
- delay-time
-
Specifies the maximum amount of time, in hundreds of microseconds, to wait before transmitting the MPLS packet with whatever ATM cells have been received. For example, to bound the delay to 1 ms the user would configure 10 (hundreds of microseconds). The delay-time is rounded up to one of the following values 1, 5, 10, 50, 100, 200, 300 and 400.
Platforms
7450 ESS, 7750 SR-7/12/12e, 7750 SR-a, 7750 SR-e, 7950 XRS
max-description-size
max-description-size
Syntax
max-description-size size
no max-description-size
Context
[Tree] (config>service>nat>pcp-server-policy max-description-size)
Full Context
configure service nat pcp-server-policy max-description-size
Description
This command specifies the maximum length of mapping descriptions made by the PCP servers using this PCP policy.
Default
max-description-size 64
Parameters
- size
-
Specifies the maximum length of mapping descriptions made by the PCP servers.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
max-drop-count
max-drop-count
Syntax
max-drop-count count
no max-drop-count
Context
[Tree] (config>service>sdp>keep-alive max-drop-count)
Full Context
configure service sdp keep-alive max-drop-count
Description
This command configures the number of consecutive SDP keepalive failed request attempts or remote replies that can be missed after which the SDP is operationally downed. If the max-drop-count consecutive keepalive request messages cannot be sent or no replies are received, the SDP-ID will be brought operationally down by the keepalive SDP monitoring.
The no form of this command reverts the max-drop-count count value to the default settings.
Default
max-drop-count 3
Parameters
- count
-
Specifies the number of consecutive SDP keepalive requests that are failed to be sent or replies missed, expressed as a decimal integer.
Platforms
All
max-ecmp-routes
max-ecmp-routes
Syntax
max-ecmp-routes max-routes
no max-ecmp-routes
Context
[Tree] (config>router>ldp max-ecmp-routes)
Full Context
configure router ldp max-ecmp-routes
Description
This command sets the maximum number of ECMP routes that LDP may use to resolve the next hop for a FEC.
The system-wide maximum number of ECMP routes is limited by the config>router>ecmp command. This command, under the LDP context, simply allows LDP to use more than 32 routes, if they are available in RTM or TTM. When configured, the actual number of ECMP routes used by LDP is therefore min[config>router>ecmp, config>router>ldp>max-ecmp-routes].
The no form of this command reverts to the default value.
Default
max-ecmp-routes 32
Parameters
- max-routes
-
Specifies the maximum number of routes.
Platforms
All
max-entries
max-entries
Syntax
max-entries count
no max-entries
Context
[Tree] (config>python>py-pol>cache max-entries)
Full Context
configure python python-policy cache max-entries
Description
This command configures the maximum number of Python cache entries that can be stored in the cache of this Python policy.
If the limit has been reached, a Python exception will be thrown when requested to store another data structure.
The no form of this command reverts to the default.
Default
max-entries 128000
Parameters
- count
-
Specifies the maximum number of cache entries allowed.
Platforms
All
max-entries
Syntax
max-entries max-entries
no shutdown
Context
[Tree] (config>app-assure>group>evt-log max-entries)
Full Context
configure application-assurance group event-log max-entries
Description
This command configures the number of entries in the buffer.
Default
max-entries 500
Parameters
- max-entries
-
Specifies the maximum number of entries for the event log.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
max-entries
Syntax
max-entries max-entries
no max-entries
Context
[Tree] (conf>router>segment-routing>srv6>loc>static-function max-entries)
Full Context
configure router segment-routing segment-routing-v6 locator static-function max-entries
Description
This command configures the maximum number of entries from the function field that must be reserved for static End, End.X, or a service SID function assignment.
The no form of this command reverts to the default value.
Default
max-entries 1
Parameters
- max-entries
-
Specifies the maximum number of entries for the SRv6 locator.
Platforms
7450 ESS, 7750 SR, 7750 SR-s, 7950 XRS, VSR
max-entries
Syntax
max-entries max-entries
no max-entries
Context
[Tree] (conf>router>sr>srv6>ms>block>static-function max-entries)
Full Context
configure router segment-routing segment-routing-v6 micro-segment block static-function max-entries
Description
This command configures the maximum number of entries from the function field that must be reserved for static uA or a micro-service SID function assignment. This value must be smaller than the number of local micro-SIDs, calculated as: 2^sid-length - 1024 * global-sid-entries.
The no form of this command reverts to the default value.
Default
max-entries 1
Parameters
- max-entries
-
Specifies the maximum number of entries for the SRv6 micro-segment locator.
Platforms
7450 ESS, 7750 SR, 7750 SR-s, 7950 XRS, VSR
max-entry-lifetime
max-entry-lifetime
Syntax
max-entry-lifetime [days days] [hrs hours] [min minutes] [sec seconds]
no max-entry-lifetime
Context
[Tree] (config>python>py-pol>cache max-entry-lifetime)
Full Context
configure python python-policy cache max-entry-lifetime
Description
This command configures the maximum allowed lifetime for each entry of the Python cache of this Python policy.
When adding data to the Python cache the lifetime of the given object must always be specified. If the specified lifetime is bigger than the configured value, then the value of the max-entry-lifetime will be used instead of the lifetime that was specified.
The no form of this command reverts to the default.
Default
max-entry-lifetime days 1
Parameters
- days days
-
Specifies the maximum lifetime that can be set on a cache entry in days.
- hrs hours
-
Specifies the maximum lifetime that can be set on a cache entry in hours.
- min minutes
-
Specifies the maximum lifetime that can be set on a cache entry in minutes.
- sec seconds
-
Specifies the maximum lifetime that can be set on a cache entry in seconds.
Platforms
All
max-fail
max-fail
Syntax
max-fail no-response-count
no max-fail
Context
[Tree] (config>saa>test>type-multi-line>lsp-trace>sr-policy max-fail)
Full Context
configure saa test type-multi-line lsp-trace sr-policy max-fail
Description
This command configures the maximum number of consecutive MPLS echo requests that do not receive a reply before the trace operation fails for a TTL.
The no form of this command reverts to the default value.
Default
max-fail 5
Parameters
- no-response-count
-
Specifies the maximum number of consecutive MPLS echo requests, expressed as a decimal integer, that do not receive a reply before the trace operation fails for a TTL.
Platforms
All
max-files-number
max-files-number
Syntax
max-files-number number
Context
[Tree] (config>call-trace max-files-number)
Full Context
configure call-trace max-files-number
Description
This command configures the maximum number of files call trace can create.
Default
max-files-number 200
Parameters
- number
-
Specifies the maximum number of all call trace log files stored on all compact flash cards together.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
max-fragment-delay
max-fragment-delay
Syntax
max-fragment-delay milliseconds
no max-fragment-delay
Context
[Tree] (config>router>l2tp>group>mlppp max-fragment-delay)
[Tree] (config>router>l2tp>group>tunnel>mlppp max-fragment-delay)
[Tree] (config>service>vprn>l2tp>group>mlppp max-fragment-delay)
[Tree] (config>service>vprn>l2tp>group>tunnel>mlppp max-fragment-delay)
Full Context
configure router l2tp group mlppp max-fragment-delay
configure router l2tp group tunnel mlppp max-fragment-delay
configure service vprn l2tp group mlppp max-fragment-delay
configure service vprn l2tp group tunnel mlppp max-fragment-delay
Description
This command is applicable only to LNS. It determines the maximum fragment delay caused by the transmission that will be imposed on a link.
Fragmentation can be used to interleave high priority packet in-between low priority fragments on a MLPPPoX session with a single link or on a MLPPPoX session with multiple links to better load balance traffic over multiple member links.
Default
no max-fragment-delay
Parameters
- milliseconds
-
Specifies the interval, in milliseconds.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s
max-groups
max-groups
Syntax
max-groups max-groups
no max-groups
Context
[Tree] (config>service>vprn>igmp>if max-groups)
[Tree] (config>service>vprn>igmp>grp-if max-groups)
Full Context
configure service vprn igmp interface max-groups
configure service vprn igmp group-interface max-groups
Description
This command configures the maximum number of groups for which IGMP can have local receiver information based on received IGMP reports on this interface. When this configuration is changed dynamically to a value lower than currently accepted number of groups, the groups that are already accepted are not deleted. Only new groups will not be allowed.
The no form of this command removes the value.
Parameters
- max-groups
-
Specifies the maximum number of groups for this interface.
Platforms
All
- configure service vprn igmp interface max-groups
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
- configure service vprn igmp group-interface max-groups
max-groups
Syntax
max-groups value
no max-groups
Context
[Tree] (config>service>vprn>mld>if max-groups)
Full Context
configure service vprn mld interface max-groups
Description
This command specifies the maximum number of groups for which MLD can have local receiver information based on received MLD reports on this interface. When this configuration is changed dynamically to a value lower than the currently accepted number of groups, the groups that are already accepted are not deleted. Only new groups will not be allowed.
Default
0 (no limit to the number of groups)
Parameters
- value
-
Specifies the maximum number of groups for this interface.
Platforms
All
max-groups
Syntax
max-groups value
no max-groups
Context
[Tree] (config>service>vprn>pim>if max-groups)
Full Context
configure service vprn pim interface max-groups
Description
This command configures the maximum number of groups for which PIM can have downstream state based on received PIM Joins on this interface. This does not include IGMP local receivers on the interface. When this configuration is changed dynamically to a value lower than the currently accepted number of groups, the groups that are already accepted are not deleted. Only new groups will not be allowed. When this object has a value of 0, there is no limit to the number of groups.
Parameters
- value
-
Specifies the maximum number of groups for this interface.
Platforms
All
max-groups
Syntax
max-groups value
no max-groups
Context
[Tree] (config>router>igmp>if max-groups)
[Tree] (config>router>igmp>group-interface max-groups)
Full Context
configure router igmp interface max-groups
configure router igmp group-interface max-groups
Description
This command specifies the maximum number of groups for which IGMP can have local receiver information based on received IGMP reports on this interface. When this configuration is changed dynamically to a value lower than the currently accepted number of groups, the groups that are already accepted are not deleted. Only new groups will not be allowed. This command is applicable for IPv4 and IPv6.
The no form of the command sets no limit to the number of groups.
Default
no max-groups
Parameters
- value
-
Specifies the maximum number of groups for this interface.
Platforms
All
- configure router igmp interface max-groups
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
- configure router igmp group-interface max-groups
max-groups
Syntax
max-groups [1..16000]
no max-groups
Context
[Tree] (config>router>mld>group-interface max-groups)
[Tree] (config>router>mld>if max-groups)
Full Context
configure router mld group-interface max-groups
configure router mld interface max-groups
Description
This command specifies the maximum number of groups for which MLD can have local receiver information based on received MLD reports on this interface. When this configuration is changed dynamically to a value lower than the currently accepted number of groups, the groups that are already accepted are not deleted. New groups are not allowed.
The no form of this command reverts to the default value.
Default
max-groups 0 (no limit to the number of groups)
Parameters
- 1..16000
-
Specifies the maximum number of groups for this interface.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
- configure router mld group-interface max-groups
All
- configure router mld interface max-groups
max-groups
Syntax
max-groups [value]
no max-groups
Context
[Tree] (config>router>pim>interface max-groups)
Full Context
configure router pim interface max-groups
Description
This command specifies the maximum number of groups for which PIM can have local receiver information based on received PIM reports on this interface. When this configuration is changed dynamically to a value lower than the currently accepted number of groups, the groups that are already accepted are not deleted. Only new groups will not be allowed. This command is applicable for IPv4 and IPv6.
The no form of this command sets no limit to the number of groups.
Default
no max-groups
Parameters
- value
-
Specifies the maximum number of groups for this interface.
Platforms
All
max-grp-sources
max-grp-sources
Syntax
max-grp-sources max-group-sources
no max-grp-sources
Context
[Tree] (config>service>vprn>igmp>grp-if max-grp-sources)
[Tree] (config>service>vprn>igmp>if max-grp-sources)
[Tree] (config>service>vprn>mld>interface max-grp-sources)
Full Context
configure service vprn igmp group-interface max-grp-sources
configure service vprn igmp interface max-grp-sources
configure service vprn mld interface max-grp-sources
Description
This command configures the maximum number of group sources for which IGMP can have local receiver information based on received IGMP reports on this interface. When this configuration is changed dynamically to a value lower than currently accepted number of group sources, the group sources that are already accepted are not deleted. Only new group sources will not be allowed.
The no form of this command reverts to the default.
Default
max-grp-sources 0
Parameters
- max-grp-sources
-
Specifies the maximum number of group source.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
- configure service vprn igmp group-interface max-grp-sources
All
- configure service vprn igmp interface max-grp-sources
- configure service vprn mld interface max-grp-sources
max-grp-sources
Syntax
max-grp-sources value
no max-grp-sources
Context
[Tree] (config>router>igmp>if max-grp-sources)
[Tree] (config>router>igmp>group-interface max-grp-sources)
Full Context
configure router igmp interface max-grp-sources
configure router igmp group-interface max-grp-sources
Description
This command configures the maximum number of group sources for which IGMP can have local receiver information based on received IGMP reports on this interface. When this configuration is changed dynamically to a value lower than currently accepted number of group sources, the group sources that are already accepted are not deleted. Only new group sources will not be allowed.
The no form of the command reverts to the default.
Default
no max-grp-sources
Parameters
- value
-
Specifies the maximum number of group sources.
Platforms
All
- configure router igmp interface max-grp-sources
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
- configure router igmp group-interface max-grp-sources
max-grp-sources
Syntax
max-grp-sources [grp-source]
no max-grp-sources
Context
[Tree] (config>router>mld>group-interface max-grp-sources)
[Tree] (config>router>mld>if max-grp-sources)
Full Context
configure router mld group-interface max-grp-sources
configure router mld interface max-grp-sources
Description
This command configures the maximum number of group sources for which MLD can have local receiver information based on received IGMP reports on this interface. When this configuration is changed dynamically to a value lower than currently accepted number of group sources, the group sources that are already accepted are not deleted. Only new group sources will not be allowed.
The no form of this command reverts to the default.
Default
max-grp-sources 0 (no limit to the number of sources)
Parameters
- grp-source
-
Specifies the maximum number of group sources.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
- configure router mld group-interface max-grp-sources
All
- configure router mld interface max-grp-sources
max-held-sessions
max-held-sessions
Syntax
max-held-sessions max-held-sessions
no max-held-sessions
Context
[Tree] (config>subscr-mgmt>gtp max-held-sessions)
Full Context
configure subscriber-mgmt gtp max-held-sessions
Description
This command configures the maximum number of GTP sessions to be held while their UE is disconnected.
The no form of this command reverts to the default.
Default
max-held-sessions 2000
Parameters
- max-held-sessions
-
Specifies the maximum number of GTP sessions.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
max-history-esp-key-records
max-history-esp-key-records
Syntax
max-history-esp-key-records max-records
no max-history-esp-key-records
Context
[Tree] (config>service>vprn>if>ipsec>ipsec-tunnel max-history-esp-key-records)
[Tree] (config>ipsec>trans-mode-prof max-history-esp-key-records)
[Tree] (config>service>ies>if>sap>ipsec-gw max-history-esp-key-records)
[Tree] (config>service>vprn>if>sap>ipsec-tunnel max-history-esp-key-records)
[Tree] (config>service>vprn>if>sap>ipsec-gw max-history-esp-key-records)
[Tree] (config>service>ies>if>ipsec>ipsec-tunnel max-history-esp-key-records)
[Tree] (config>router>if>ipsec>ipsec-tunnel max-history-esp-key-records)
Full Context
configure service vprn interface ipsec ipsec-tunnel max-history-esp-key-records
configure ipsec ipsec-transport-mode-profile max-history-esp-key-records
configure service ies interface sap ipsec-gw max-history-esp-key-records
configure service vprn interface sap ipsec-tunnel max-history-esp-key-records
configure service vprn interface sap ipsec-gw max-history-esp-key-records
configure service ies interface ipsec ipsec-tunnel max-history-esp-key-records
configure router interface ipsec ipsec-tunnel max-history-esp-key-records
Description
This command enables the system to keep records of CHILD-SA keys. There is a system wide limit of maximum number of IPsec tunnels that save keys. If the number of tunnel exceeds that limit, the system does not save keys for the new tunnels. Contact Nokia support for details of the limitation.
This command is ignored if the config>ipsec>no show-ipsec-keys command is configured.
The no form of this command prevents the system from keeping records.
Default
no max-history-esp-key-records
Parameters
- max-records
-
Specifies the maximum number of recent records.
Platforms
VSR
- configure router interface ipsec ipsec-tunnel max-history-esp-key-records
- configure service vprn interface ipsec ipsec-tunnel max-history-esp-key-records
- configure service ies interface ipsec ipsec-tunnel max-history-esp-key-records
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
- configure ipsec ipsec-transport-mode-profile max-history-esp-key-records
- configure service vprn interface sap ipsec-gw max-history-esp-key-records
- configure service ies interface sap ipsec-gw max-history-esp-key-records
- configure service vprn interface sap ipsec-tunnel max-history-esp-key-records
max-history-ike-key-records
max-history-ike-key-records
Syntax
max-history-ike-key-records max-records
no max-history-ike-key-records
Context
[Tree] (config>service>ies>if>sap>ipsec-gw max-history-ike-key-records)
[Tree] (config>service>vprn>if>sap>ipsec-tunnel max-history-ike-key-records)
[Tree] (config>router>if>ipsec>ipsec-tunnel>manual-keying max-history-ike-key-records)
[Tree] (config>service>vprn>if>ipsec>ipsec-tunnel max-history-ike-key-records)
[Tree] (config>service>vprn>if>sap>ipsec-gw max-history-ike-key-records)
[Tree] (config>ipsec>trans-mode-prof max-history-ike-key-records)
[Tree] (config>service>ies>if>ipsec>ipsec-tunnel max-history-ike-key-records)
Full Context
configure service ies interface sap ipsec-gw max-history-ike-key-records
configure service vprn interface sap ipsec-tunnel max-history-ike-key-records
configure router interface ipsec ipsec-tunnel manual-keying max-history-ike-key-records
configure service vprn interface ipsec ipsec-tunnel max-history-ike-key-records
configure service vprn interface sap ipsec-gw max-history-ike-key-records
configure ipsec ipsec-transport-mode-profile max-history-ike-key-records
configure service ies interface ipsec ipsec-tunnel max-history-ike-key-records
Description
This command enables the system to keep records of IKE-SA keys for the corresponding ipsec-gw, ipsec-tunnel, or ipsec-transport-mode-profile.
This command is ignored if the config>ipsec>no show-ipsec-keys command is enabled. There is a system-wide limit for the maximum number of IPsec tunnels that save keys. If the number of tunnels exceeds that limit, the system does not save keys for the new tunnels. Contact Nokia support for details of the limitation.
The no form of this command prevents the system from keeping records.
Default
no max-history-ike-key-records
Parameters
- max-records
-
Specifies the maximum number of recent records.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
- configure ipsec ipsec-transport-mode-profile max-history-ike-key-records
- configure service vprn interface sap ipsec-tunnel max-history-ike-key-records
- configure service vprn interface sap ipsec-gw max-history-ike-key-records
- configure service ies interface sap ipsec-gw max-history-ike-key-records
VSR
- configure service ies interface ipsec ipsec-tunnel max-history-ike-key-records
- configure service vprn interface ipsec ipsec-tunnel max-history-ike-key-records
- configure router interface ipsec ipsec-tunnel manual-keying max-history-ike-key-records
max-igmp-latency
max-igmp-latency
Syntax
max-igmp-latency milli-seconds
Context
[Tree] (config>mcast-mgmt>mcast-info-plcy>video-policy>video-if max-igmp-latency)
Full Context
configure mcast-management multicast-info-policy video-policy video-interface max-igmp-latency
Description
After the subscriber requests a fast channel change using RTCP, the video ISA bursts the video content as unicast to the subscriber. When the unicasted content has caught up to the multicast, the video ISA sends a notification message using RTCP to the subscriber to switch over to multicast with an IGMP request. When the notification message from the video ISA is sent, the max-igmp-latency timer starts. The video ISA continues to send unicast video until the max-igmp-latency expires or until the subscriber, using RTCP, informs the video ISA of the exact sequence number to stop (whichever occurs first). The max-igmp-latency is the maximum delay that the multicast router takes to respond and deliver the multicast upon the subscriber IGMP request.
Parameters
- milli-seconds
-
Specifies the maximum delay in milliseconds.
Platforms
7450 ESS, 7750 SR-1, 7750 SR-7/12/12e, 7750 SR-1s, 7750 SR-2s, 7750 SR-7s, 7750 SR-14s
max-lanext-bd
max-lanext-bd
Syntax
max-lanext-bd [value]
no max-lanext-bd
Context
[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw max-lanext-bd)
[Tree] (config>service>ies>sub-if>grp-if>wlan-gw max-lanext-bd)
Full Context
configure service vprn subscriber-interface group-interface wlan-gw max-lanext-bd
configure service ies subscriber-interface group-interface wlan-gw max-lanext-bd
Description
This command specifies the maximum number of HLE BDs for this group interface.
The no form of this command disables HLE for the group interface.
Parameters
- value
-
Specifies the maximum number of Bridged Domains for this interface.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
max-lease-time
max-lease-time
Syntax
max-lease-time [days days] [hrs hours] [min minutes] [sec seconds]
no max-lease-time
Context
[Tree] (config>router>dhcp>server>pool max-lease-time)
Full Context
configure router dhcp local-dhcp-server pool max-lease-time
Description
This command configures the maximum lease time.
The no form of this command reverts to the default.
Default
max-lease-time days 10
Parameters
- max-lease-time
-
Specifies the maximum lease time.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
max-lifetime
max-lifetime
Syntax
max-lifetime hours
no max-lifetime
Context
[Tree] (config>subscr-mgmt>diam-appl-plcy>gy>ccrt-replay max-lifetime)
[Tree] (config>subscr-mgmt>diam-appl-plcy>gx>ccrt-replay max-lifetime)
Full Context
configure subscriber-mgmt diameter-application-policy gy ccrt-replay max-lifetime
configure subscriber-mgmt diameter-application-policy gx ccrt-replay max-lifetime
Description
This command specifies the maximum period of time that CCR-T messages for Diameter Gx or Gy sessions that belong to the Diameter application policy are replayed.
The no form of this command resets the maximum lifetime to the default value setting.
Default
max-lifetime 24
Parameters
- hours
-
Specifies the maximum lifetime after which the CCR-T messages are no longer replayed.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
max-links
max-links
Syntax
max-links max-links
no max-links
Context
[Tree] (config>router>l2tp>group>mlppp max-links)
[Tree] (config>service>vprn>l2tp>group>tunnel>mlppp max-links)
[Tree] (config>router>l2tp>group>tunnel>mlppp max-links)
[Tree] (config>service>vprn>l2tp>group>mlppp max-links)
Full Context
configure router l2tp group mlppp max-links
configure service vprn l2tp group tunnel mlppp max-links
configure router l2tp group tunnel mlppp max-links
configure service vprn l2tp group mlppp max-links
Description
This command is applicable only to LNS. It determines the maximum number of links that can be put in a bundle.
Any attempt of a session to join a bundle that is above the max-link limit will be rejected.
If interleaving is configured, it is recommended that max-links be set to 1 or a version of the command is used (no max-links). Both have the same effect.
The configuration under the tunnel hierarchy will override the configuration under the group hierarchy.
The no form of this command limits the number of links in the bundle to 1.
Default
no max-links
Parameters
- max-links
-
Specifies the maximum number of links in a bundle.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s
max-list-length
max-list-length
Syntax
max-list-length unlimited
max-list-length count
no max-list-length
Context
[Tree] (config>router>l2tp>tunnel-sel max-list-length)
[Tree] (config>service>vprn>l2tp>tunnel-sel max-list-length)
Full Context
configure router l2tp tunnel-selection-blacklist max-list-length
configure service vprn l2tp tunnel-selection-blacklist max-list-length
Description
This command specifies the number of tunnels or peers that can be in the tunnel-selection-blacklist. If a tunnel or peer needs to be added to the denylist and the denylist is full, the system removes the item (tunnel or peer) from the denylist that was in this denylist for the longest time.
The no form of this command reverts to the default.
Default
max-list-length unlimited
Parameters
- unlimited
-
Specifies there is no limit.
- count
-
Specifies how many items (tunnels or peers) can be in the denylist.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
max-lockout-hosts
max-lockout-hosts
Syntax
max-lockout-hosts hosts
no max-lockout-hosts
Context
[Tree] (config>subscr-mgmt>host-lockout-plcy max-lockout-hosts)
Full Context
configure subscriber-mgmt host-lockout-policy max-lockout-hosts
Description
When a client enters lockout, authentication and ESM host creation is suppressed. A lightweight context maintains the lockout state and the timeouts for the client in lockout. This command allows the number of lockout contexts to be configured per SAP. If the number of existing contexts reaches the configured count, incoming hosts that fail authentication or creation are not subject to lockout, and are retried as normal.
The no form of this command reverts to the default value.
Default
max-lockout-hosts 100
Parameters
- hosts
-
Specifies the maximum number of lockout host.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
max-mac
max-mac
Syntax
max-mac [value]
no max-mac
Context
[Tree] (config>service>ies>sub-if>grp-if>wlan-gw>ranges>range>vrgw>lanext>access max-mac)
[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw>ranges>range>vrgw>lanext>access max-mac)
Full Context
configure service ies subscriber-interface group-interface wlan-gw vlan-tag-ranges range vrgw lanext access max-mac
configure service vprn subscriber-interface group-interface wlan-gw vlan-tag-ranges range vrgw lanext access max-mac
Description
This command specifies the maximum number of allowed MAC addresses on the access side of HLE.
The no form of this command reverts to the default.
Default
max-mac 20
Parameters
- value
-
Specifies the maximum number of MAC entries in bridged domains.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
max-mac
Syntax
max-mac [value]
no max-mac
Context
[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw>ranges>range>vrgw>lanext>xconnect max-mac)
[Tree] (config>service>ies>sub-if>grp-if>wlan-gw>ranges>range>vrgw>lanext>xconnect max-mac)
Full Context
configure service vprn subscriber-interface group-interface wlan-gw ranges range vrgw lanext xconnect max-mac
configure service ies subscriber-interface group-interface wlan-gw ranges range vrgw lanext xconnect max-mac
Description
This command specifies the maximum number of allowed MAC in the bridge domain.
The no form of this command reverts to the default.
Default
max-mac 20
Parameters
- value
-
Specifies the maximum number of MAC entries in bridged domains.
max-mac
Syntax
max-mac [value]
no max-mac
Context
[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw>ranges>range>vrgw>lanext>network max-mac)
[Tree] (config>service>ies>sub-if>grp-if>wlan-gw>ranges>range>vrgw>lanext>network max-mac)
Full Context
configure service vprn subscriber-interface group-interface wlan-gw vlan-tag-ranges range vrgw lanext network max-mac
configure service ies subscriber-interface group-interface wlan-gw vlan-tag-ranges range vrgw lanext network max-mac
Description
This command specifies the maximum number of allowed VM MAC addresses on the access side of HLE.
The no form of this command reverts to the default.
Default
max-mac 20
Parameters
- value
-
Specifies the maximum number of VM MAC entries in bridged domains.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
max-msg-count
max-msg-count
Syntax
max-msg-count count
Context
[Tree] (config>system>telemetry>notification-bundling max-msg-count)
Full Context
configure system telemetry notification-bundling max-msg-count
Description
This command sets the maximum number of notifications that can be bundled in a single telemetry message.
The no form of this command returns the message count to the default value.
Default
max-msg-count 100
Parameters
- count
-
Specifies the maximum of notifications that can be bundled in a single telemetry message.
Platforms
All
max-msg-size
max-msg-size
Syntax
max-msg-size number
no max-msg-size
Context
[Tree] (config>system>grpc max-msg-size)
Full Context
configure system grpc max-msg-size
Description
This command configures the maximum rx message size that can be received.
The no form of this command reverts to the default.
Default
max-msg-size 512
Parameters
- number
-
Specifies the message size, in MB.
Platforms
All
max-nbr-mac-addr
max-nbr-mac-addr
Syntax
max-nbr-mac-addr table-size
no max-nbr-mac-addr
Context
[Tree] (config>service>vpls>endpoint max-nbr-mac-addr)
[Tree] (config>service>vpls>vxlan max-nbr-mac-addr)
[Tree] (config>service>vpls>spoke-sdp max-nbr-mac-addr)
[Tree] (config>service>template>vpls-sap-template max-nbr-mac-addr)
[Tree] (config>service>vpls>sap max-nbr-mac-addr)
Full Context
configure service vpls endpoint max-nbr-mac-addr
configure service vpls vxlan max-nbr-mac-addr
configure service vpls spoke-sdp max-nbr-mac-addr
configure service template vpls-sap-template max-nbr-mac-addr
configure service vpls sap max-nbr-mac-addr
Description
This command specifies the maximum number of FDB entries for both learned and static MAC addresses for this SAP, spoke-SDP, endpoint, or VXLAN instance.
When the configured limit is reached, and discard-unknown-source is enabled for this SAP, spoke-SDP, or static VXLAN instance (see config>service>vpls>sap discard-unknown-source or config>service>vpls>spoke-sdp discard-unknown-source), then packets with unknown source MAC addresses are discarded.
The no form of the command restores the global MAC learning limitations for the SAP or spoke-SDP, or VXLAN instance.
Default
no max-nbr-mac-addr
Parameters
- table-size
-
Specifies the maximum number of learned and static entries allowed in the FDB of this service.
Platforms
All
- configure service template vpls-sap-template max-nbr-mac-addr
- configure service vpls spoke-sdp max-nbr-mac-addr
- configure service vpls sap max-nbr-mac-addr
- configure service vpls endpoint max-nbr-mac-addr
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
- configure service vpls vxlan max-nbr-mac-addr
max-nbr-mac-addr
Syntax
max-nbr-mac-addr table-size
no max-nbr-mac-addr
Context
[Tree] (config>service>pw-template max-nbr-mac-addr)
Full Context
configure service pw-template max-nbr-mac-addr
Description
This command specifies the maximum number of FDB entries for both learned and static MAC addresses for this SAP or spoke SDP.
When the configured limit has been reached, and discard-unknown-source has been enabled for this SAP or spoke SDP (see config>service>vpls>sap discard-unknown-source or config>service>vpls>spoke-sdp discard-unknown-source), packets with unknown source MAC addresses will be discarded.
The no form of the command restores the global MAC learning limitations for the SAP or spoke SDP.
Default
no max-nbr-mac-addr
Parameters
- table-size
-
Specifies the maximum number of learned and static entries allowed in the FDB of this service.
Platforms
All
max-nbr-of-leases
max-nbr-of-leases
Syntax
max-nbr-of-leases max-nbr-of-leases
no max-nbr-of-leases
Context
[Tree] (config>service>ies>if>ipv6>dhcp6-server max-nbr-of-leases)
Full Context
configure service ies interface ipv6 dhcp6-server max-nbr-of-leases
Description
This command configures the maximum number of lease states installed by the DHCPv6 server function allowed on this interface.
The no form of this command returns the value to the default.
Default
max-nbr-of-leases 8000
Parameters
- max-nbr-of-leases
-
Specifies the maximum number of lease states installed by the DHCPv6 server function allowed on this interface.
Platforms
All
max-num-groups
max-num-groups
Syntax
max-num-groups count
no max-num-groups
Context
[Tree] (config>service>vpls>sap>igmp-snooping max-num-groups)
[Tree] (config>service>vpls>mesh-sdp>mld-snooping max-num-groups)
[Tree] (config>service>vpls>spoke-sdp>igmp-snooping max-num-groups)
[Tree] (config>service>vpls>mesh-sdp>igmp-snooping max-num-groups)
[Tree] (config>service>vpls>spoke-sdp>mld-snooping max-num-groups)
[Tree] (config>service>vpls>sap>mld-snooping max-num-groups)
Full Context
configure service vpls sap igmp-snooping max-num-groups
configure service vpls mesh-sdp mld-snooping max-num-groups
configure service vpls spoke-sdp igmp-snooping max-num-groups
configure service vpls mesh-sdp igmp-snooping max-num-groups
configure service vpls spoke-sdp mld-snooping max-num-groups
configure service vpls sap mld-snooping max-num-groups
Description
This command defines the maximum number of multicast groups that can be joined on this SAP or SDP. If the node receives an IGMP join message that would exceed the configured number of groups, the request is ignored.
The no form of this command reverts to the default value.
Default
no max-num-groups
Parameters
- count
-
Specifies the maximum number of groups that can be joined on this SAP or SDP.
Platforms
All
max-num-groups
Syntax
max-num-groups max-num-groups
no max-num-groups
Context
[Tree] (config>service>ies>sub-if>grp-if>sap>igmp-trk max-num-groups)
Full Context
configure service ies subscriber-interface group-interface sap igmp-host-tracking max-num-groups
Description
This command configures the maximum number of multicast groups allowed to be tracked.
The no form of this command disables the check.
Default
no max-num-groups
Parameters
- max-num-groups
-
Specifies the maximum number of multicast groups allowed to be tracked.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
max-num-groups
Syntax
max-num-groups max-num-groups
no max-num-groups
Context
[Tree] (config>subscr-mgmt>igmp-policy max-num-groups)
Full Context
configure subscriber-mgmt igmp-policy max-num-groups
Description
This command configures the maximum number of multicast groups.
The no form of this command reverts to the default value.
Parameters
- max-num-groups
-
Specifies the maximum number of multicast groups.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
max-num-groups
Syntax
max-num-groups max-num-groups
no max-num-groups
Context
[Tree] (config>service>vprn>sub-if>grp-if>sap>igmp-trk max-num-groups)
Full Context
configure service vprn subscriber-interface group-interface sap igmp-host-tracking max-num-groups
Description
This command configures the maximum number of multicast groups allowed to be tracked.
The no form of this command removes the values from the configuration.
Default
no max-num-groups
Parameters
- max-num-groups
-
Specifies the maximum number of multicast groups allowed to be tracked.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
max-num-groups
Syntax
max-num-groups max-num-groups
no max-num-groups
Context
[Tree] (config>subscr-mgmt>msap-policy>igmp-host-tracking max-num-groups)
Full Context
configure subscriber-mgmt msap-policy igmp-host-tracking max-num-groups
Description
This command configures the maximum number of multicast groups allowed to be tracked.
The no form of this command removes the values from the configuration.
Parameters
- max-num-groups
-
Specifies the maximum number of multicast groups allowed to be tracked.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
max-num-groups
Syntax
max-num-groups max-num-groups
no max-num-groups
Context
[Tree] (config>subscr-mgmt>msap-policy>vpls-only>igmp-snp max-num-groups)
Full Context
configure subscriber-mgmt msap-policy vpls-only-sap-parameters igmp-snooping max-num-groups
Description
This command configures the maximum number of multicast groups that can be joined on an MSAP or SDP. If the router receives an IGMP join message that would exceed the configured number of groups, the request is ignored.
Parameters
- max-num-groups
-
Specifies the maximum number of groups that can be joined on an MSAP or SDP.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
max-num-groups
Syntax
max-num-groups count
no max-num-groups
Context
[Tree] (config>subscr-mgmt>mld-policy max-num-groups)
Full Context
configure subscriber-mgmt mld-policy max-num-groups
Description
This command defines the maximum number of multicast groups that can be joined. If the router receives a join message that would exceed the configured number of groups, the request is ignored.
The no form of this command reverts to the default.
Parameters
- count
-
Specifies the maximum number of groups that can be joined.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
max-num-groups
Syntax
max-num-groups max-num-groups
no max-num-groups
Context
[Tree] (config>service>vprn>sub-if>grp-if>sap>igmp-snooping max-num-groups)
Full Context
configure service vprn subscriber-interface group-interface sap igmp-snooping max-num-groups
Description
This command configures the maximum number of multicast groups allowed to be tracked.
The no form of this command removes the values from the configuration.
Parameters
- max-num-groups
-
Specifies the maximum number of multicast groups allowed to be tracked.
max-num-groups
Syntax
max-num-groups max-num-groups
no max-num-groups
Context
[Tree] (config>service>vpls>sap>igmp-host-tracking max-num-groups)
Full Context
configure service vpls sap igmp-host-tracking max-num-groups
Description
This command configures the maximum number of multicast groups allowed to be tracked.
The no form of this command removes the values from the configuration.
Default
no max-num-groups
Parameters
- max-num-groups
-
Specifies the maximum number of multicast groups allowed to be tracked.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
max-num-groups
Syntax
max-num-groups num-groups
no max-num-groups
Context
[Tree] (config>service>vpls>sap>pim-snooping max-num-groups)
[Tree] (config>service>vpls>spoke-sdp>pim-snooping max-num-groups)
Full Context
configure service vpls sap pim-snooping max-num-groups
configure service vpls spoke-sdp pim-snooping max-num-groups
Description
This command configures the maximum groups for PIM snooping.
Parameters
- num-groups
-
Specifies the maximum groups for PIM snooping.
Platforms
All
max-num-groups
Syntax
max-num-groups count
no max-num-groups
Context
[Tree] (config>service>pw-template>igmp-snooping max-num-groups)
Full Context
configure service pw-template igmp-snooping max-num-groups
Description
This command defines the maximum number of multicast groups that can be joined. If the router receives an IGMP join message that would exceed the configured number of groups, the request is ignored.
Default
no max-num-groups
Parameters
- count
-
Specifies the maximum number of groups that can be joined.
Platforms
All
max-num-grp-sources
max-num-grp-sources
Syntax
max-num-grp-sources [max-num-grp-sources]
no max-num-grp-sources
Context
[Tree] (config>subscr-mgmt>igmp-policy max-num-grp-sources)
Full Context
configure subscriber-mgmt igmp-policy max-num-grp-sources
Description
This command configures the maximum number of group sources for which IGMP can have local receiver information based on received IGMP reports on this interface. When this configuration is changed dynamically to a value lower than currently accepted number of group sources, the group sources that are already accepted are not deleted. Only new group sources will not be allowed. When this object has a value of 0, there is no limit to the number of group sources.
The no form of this command removes the value from the configuration.
Parameters
- max-num-grp-sources
-
Specifies the maximum number of multicast sources allowed to be tracked per group.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
max-num-grp-sources
Syntax
max-num-grp-sources [max-num-grp-sources]
no max-num-grp-sources
Context
[Tree] (config>subscr-mgmt>msap-policy>igmp-trk max-num-grp-sources)
Full Context
configure subscriber-mgmt msap-policy igmp-host-tracking max-num-grp-sources
Description
This command configures the maximum number of group sources for which IGMP can have local receiver information based on received IGMP reports on this interface. When this configuration is changed dynamically to a value lower than currently accepted number of group sources, the group sources that are already accepted are not deleted. Only new group sources will not be allowed. When this object has a value of 0, there is no limit to the number of group sources.
The no form of this command removes the value from the configuration.
Parameters
- max-num-grp-sources
-
Specifies the maximum number of multicast sources allowed to be tracked per group.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
max-num-grp-sources
Syntax
max-num-grp-sources [max-num-grp-sources]
no max-num-grp-sources
Context
[Tree] (config>subscr-mgmt>mld-policy max-num-grp-sources)
Full Context
configure subscriber-mgmt mld-policy max-num-grp-sources
Description
This command configures the maximum number of group sources for which MLD can have local receiver information based on received MLD reports on this interface. When this configuration is changed dynamically to a value lower than currently accepted number of group sources, the group sources that are already accepted are not deleted. Only new group sources are not allowed. When this object has a value of 0, there is no limit to the number of group sources.
The no form of this command removes the value from the configuration.
Parameters
- max-num-grp-sources
-
Specifies the maximum number of multicast sources allowed to be tracked per group.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
max-num-grp-sources
Syntax
[no] max-num-grp-sources [number]
Context
[Tree] (config>service>vprn>sub-if>grp-if>sap>igmp-snooping max-num-grp-sources)
Full Context
configure service vprn subscriber-interface group-interface sap igmp-snooping max-num-grp-sources
Description
This command configures the maximum number of group sources for which IGMP can have local receiver information based on received IGMP reports on this interface. When this configuration is changed dynamically to a value lower than currently accepted number of group sources, the group sources that are already accepted are not deleted. Only new group sources are not allowed. When this object has a value of 0, there is no limit to the number of group sources.
The no form of this command removes the value from the configuration.
Parameters
- number
-
Specifies the maximum number of multicast sources allowed to be tracked per group.
max-num-grp-sources
Syntax
max-num-grp-sources [1 to 32000]
no max-num-grp-sources
Context
[Tree] (config>service>vpls>sap>igmp-snooping max-num-grp-sources)
[Tree] (config>service>vpls>mesh-sdp>igmp-snooping max-num-grp-sources)
[Tree] (config>service>vpls>spoke-sdp>igmp-snooping max-num-grp-sources)
[Tree] (config>service>vpls>sap>igmp-host-tracking max-num-grp-sources)
Full Context
configure service vpls sap igmp-snooping max-num-grp-sources
configure service vpls mesh-sdp igmp-snooping max-num-grp-sources
configure service vpls spoke-sdp igmp-snooping max-num-grp-sources
configure service vpls sap igmp-host-tracking max-num-grp-sources
Description
This command defines the maximum number of multicast SGs that can be joined on this SAP or SDP. If the node receives an IGMP join message that would exceed the configured number of SGs, the request is ignored.
The no form of this command disables the check.
Default
no max-num-grp-sources
Parameters
- 1 to 32000
-
Specifies the maximum number of multicast sources allowed to be tracked per group.
Platforms
All
- configure service vpls spoke-sdp igmp-snooping max-num-grp-sources
- configure service vpls mesh-sdp igmp-snooping max-num-grp-sources
- configure service vpls sap igmp-snooping max-num-grp-sources
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
- configure service vpls sap igmp-host-tracking max-num-grp-sources
max-num-grp-sources
Syntax
max-num-grp-sources max-num-sources
no max-num-grp-sources
Context
[Tree] (config>service>ies>sub-if>grp-if>sap>igmp-host-tracking max-num-grp-sources)
Full Context
configure service ies subscriber-interface group-interface sap igmp-host-tracking max-num-grp-sources
Description
This command configures the max number of multicast (S,G)s allowed to be tracked.
The no form of this command disables the check.
Default
no max-num-grp-sources
Parameters
- max-num-sources
-
Specifies the maximum number of multicast sources allowed to be tracked per group.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
max-num-sources
max-num-sources
Syntax
max-num-sources max-num-sources
no max-num-sources
Context
[Tree] (config>subscr-mgmt>igmp-policy max-num-sources)
Full Context
configure subscriber-mgmt igmp-policy max-num-sources
Description
This command configures the maximum number of multicast sources.
The no form of this command disables the command.
Parameters
- max-num-sources
-
Specifies the maximum number of multicast sources.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
max-num-sources
Syntax
max-num-sources max-num-sources
no max-num-sources
Context
[Tree] (config>subscr-mgmt>msap-policy>igmp-host-tracking max-num-sources)
Full Context
configure subscriber-mgmt msap-policy igmp-host-tracking max-num-sources
Description
This command configures the maximum number of multicast sources allowed to be tracked per group.
The no form of this command removes the value from the configuration.
Parameters
- max-num-sources
-
Specifies the maximum number of multicast sources allowed to be tracked per group.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
max-num-sources
Syntax
max-num-sources max-num-sources
no max-num-sources
Context
[Tree] (config>subscr-mgmt>mld-policy max-num-sources)
Full Context
configure subscriber-mgmt mld-policy max-num-sources
Description
This command configures the maximum number of multicast sources allowed per group.
The no form of this command removes the value from the configuration.
Parameters
- max-num-sources
-
Specifies the maximum number of multicast sources allowed per group.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
max-num-sources
Syntax
max-num-sources max-num-sources
no max-num-sources
Context
[Tree] (config>service>vprn>sub-if>grp-if>sap>igmp-snooping max-num-sources)
Full Context
configure service vprn subscriber-interface group-interface sap igmp-snooping max-num-sources
Description
This command configures the maximum number of multicast sources allowed to be tracked per group.
The no form of this command removes the value from the configuration.
Parameters
- max-num-sources
-
Specifies the maximum number of multicast sources allowed to be tracked per group.
max-num-sources
Syntax
max-num-sources max-num-sources
no max-num-sources
Context
[Tree] (config>service>vpls>mesh-sdp>igmp-snooping max-num-sources)
[Tree] (config>service>vpls>sap>igmp-host-tracking max-num-sources)
[Tree] (config>service>vpls>spoke-sdp>igmp-snooping max-num-sources)
[Tree] (config>service>vpls>sap>igmp-snooping max-num-sources)
Full Context
configure service vpls mesh-sdp igmp-snooping max-num-sources
configure service vpls sap igmp-host-tracking max-num-sources
configure service vpls spoke-sdp igmp-snooping max-num-sources
configure service vpls sap igmp-snooping max-num-sources
Description
This command defines the maximum number of multicast sources that can be joined on this SAP or SDP. If the node receives an IGMP join message that would exceed the configured number of sources, the request is ignored.
The no form of this command removes the value from the configuration.
Parameters
- max-num-sources
-
Specifies the maximum number of multicast sources allowed per group.
Platforms
All
- configure service vpls mesh-sdp igmp-snooping max-num-sources
- configure service vpls sap igmp-snooping max-num-sources
- configure service vpls spoke-sdp igmp-snooping max-num-sources
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
- configure service vpls sap igmp-host-tracking max-num-sources
max-num-sources
Syntax
max-num-sources max-num-sources
no max-num-sources
Context
[Tree] (config>service>ies>sub-if>grp-if>sap>igmp-host-tracking max-num-sources)
Full Context
configure service ies subscriber-interface group-interface sap igmp-host-tracking max-num-sources
Description
This command configures the maximum number of multicast sources allowed to be tracked per group.
The no form of this command removes the value from the configuration.
Parameters
- max-num-sources
-
Specifies the maximum number of multicast sources allowed to be tracked per group.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
max-num-ue
max-num-ue
Syntax
max-num-ue maximum
Context
[Tree] (config>subscr-mgmt>wlan-gw>tunnel-query max-num-ue)
Full Context
configure subscriber-mgmt wlan-gw tunnel-query max-num-ue
Description
This command enables matching only on tunnels that have, at most, the specified number of UEs connected.
Default
max-num-ue 4294967295
Parameters
- maximum
-
Specifies the maximum number of UEs.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
max-path
max-path
Syntax
max-path max-paths
no max-path
Context
[Tree] (config>test-oam>ldp-treetrace>path-discovery max-path)
Full Context
configure test-oam ldp-treetrace path-discovery max-path
Description
This command configures the maximum number of ECMP paths the path discovery attempts to discover for each run every interval minute.
The no form of this command resets the time out to its default value.
Default
no max-path
Parameters
- max-paths
-
Specifies the tree discovery maximum path.
Platforms
All
max-payload-length
max-payload-length
Syntax
max-payload-length direction direction [create]
no max-payload-length direction direction
Context
[Tree] (config>app-assure>group>statistics>tca>gtp-filter max-payload-length)
Full Context
configure application-assurance group statistics threshold-crossing-alert gtp-filter max-payload-length
Description
This command configures a TCA for the counter capturing drops due to the GTP filter maximum payload length. A maximum payload length drop TCA can be created for traffic generated from the subscriber side of AA (from-sub) or for traffic generated from the network toward the AA subscriber (to-sub). The create keyword is mandatory when creating a maximum payload length drop TCA.
Parameters
- direction
-
Specifies the traffic direction.
- create
-
Keyword used to create the TCA.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
max-payload-length
Syntax
max-payload-length bytes
no max-payload-length
Context
[Tree] (config>app-assure>group>gtp>gtp-filter max-payload-length)
Full Context
configure application-assurance group gtp gtp-filter max-payload-length
Description
This command specifies the maximum allowed GTP payload size.
The no form of this command removes this GTP message length filter.
Default
no max-payload-length
Parameters
- bytes
-
Specifies the packet length in bytes.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
max-peer
max-peer
Syntax
max-peer max-peer
no max-peer
Context
[Tree] (config>port>ethernet>dot1x>macsec>sub-port max-peer)
Full Context
configure port ethernet dot1x macsec sub-port max-peer
Description
This command configures the max peer allowed under this MACsec instance.
The peer establishment is a race condition and first come first serve. On any security zone, only 32 peers can be supported. See SA Exhaustion Behavior for more details.
The no form of this command returns the value to the default.
Default
no max-peer
Parameters
- max-peer
-
The maximum number of peers supported on this port.
Platforms
All
max-percent-rate
max-percent-rate
Syntax
max-percent-rate percentage [local-limit | reference-port-limit]
no max-percent-rate
Context
[Tree] (config>qos>plcr-ctrl-plcy>root max-percent-rate)
Full Context
configure qos policer-control-policy root max-percent-rate
Description
This command configures the maximum percentage rate for the policer control policy.
The no form of this command removes the configuration.
Parameters
- percentage
-
Specifies the percentage.
- local-limit
-
Keyword used to specify the local limit.
- reference-port-limit
-
Keyword used to specify the reference port limit.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
max-prob
max-prob
Syntax
max-prob percent
no max-prob
Context
[Tree] (config>qos>slope-policy>highplus-slope max-prob)
[Tree] (config>qos>slope-policy>low-slope max-prob)
[Tree] (config>qos>slope-policy>high-slope max-prob)
[Tree] (config>qos>slope-policy>exceed-slope max-prob)
Full Context
configure qos slope-policy highplus-slope max-prob
configure qos slope-policy low-slope max-prob
configure qos slope-policy high-slope max-prob
configure qos slope-policy exceed-slope max-prob
Description
This command sets the exceed, low, high, or highplus Random Early Detection (RED) slope position for the maximum non-one packet discard probability value before the packet discard probability rises directly to one. The percent parameter is expressed as a percentage of packet discard probability where always discard is a probability of 1. A max-prob value of 80 represents 80% of 1, or a packet discard probability of 0.8.
The no form of this command restores the max-prob value to the default setting.
Default
max-prob 80
Parameters
- percent
-
The maximum drop probability percentage corresponding to the max-avg, expressed as a decimal integer.
Platforms
All
max-queue-size
max-queue-size
Syntax
max-queue-size queue-size
no max-queue-size
Context
[Tree] (config>qos>mlppp-profile-egress>class max-queue-size)
Full Context
configure qos mlppp-profile-egress class max-queue-size
Description
This command configures the maximum queue size for each MLPPP class queue for this profile.
Parameters
- queue-size
-
Specifies the maximum queue size in ms of buffer space.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
max-queue-size
Syntax
max-queue-size queue-size
no max-queue-size
Context
[Tree] (config>qos>mc-fr-profile-egress>class max-queue-size)
Full Context
configure qos mc-fr-profile-egress class max-queue-size
Description
This command configures the maximum size for each Frame Relay scheduling class queue for this profile.
Default
max-queue-size 10 — class 0
max-queue-size 50 — class 1
max-queue-size 150 — class 2
max-queue-size 750 — class 3
Parameters
- queue-size
-
Specifies the number, in ms, of the available link or bundle rate.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
max-rate
max-rate
Syntax
max-rate percent percent-rate
max-rate pir-rate
no max-rate
Context
[Tree] (config>qos>hw-agg-shap-sched-plcy max-rate)
Full Context
configure qos hw-agg-shaper-scheduler-policy max-rate
Description
This command configures the maximum frame-based rate of the hardware aggregate shaper scheduler policy expressed as a percentage of the port rate or as the PIR rate.
The no form of this command removes the rate from the configuration.
Parameters
- percent-rate
-
Specifies the percentage rate.
- pir-rate
-
Specifies the PIR rate in kb/s.
Platforms
7750 SR-1, 7750 SR-s
max-rate
Syntax
max-rate {rate | max}
no max-rate
Context
[Tree] (config>subscr-mgmt>sub-prof>ingress>policer-control-policy max-rate)
[Tree] (config>subscr-mgmt>sub-prof>egress>policer-control-policy max-rate)
Full Context
configure subscriber-mgmt sub-profile ingress policer-control-policy max-rate
configure subscriber-mgmt sub-profile egress policer-control-policy max-rate
Description
This command defines the parent policer’s PIR leaky bucket’s decrement rate. A parent policer is created for each time the policer-control-policy is applied to either a SAP or subscriber instance. Packets that are not discarded by the child policers associated with the SAP or subscriber instance are evaluated against the parent policer’s PIR leaky bucket.
For each packet, the bucket is first decremented by the correct amount based on the decrement rate to derive the current bucket depth. The current depth is then compared to one of two discard thresholds associated with the packet. The first discard threshold (discard-unfair) is applied if the FIR (Fair Information Rate) leaky bucket in the packet’s child policer is in the confirming state. The second discard threshold (discard-all) is applied if the child policer's FIR leaky bucket is in the exceed state. Only one of the two thresholds is applied per packet. If the current depth of the parent policer PIR bucket is less than the threshold value, the parent PIR bucket is in the conform state for that particular packet. If the depth is equal to or greater than the applied threshold, the bucket is in the violate state for the packet.
If the result is ‟conform,” the bucket depth is increased by the size of the packet (plus or minus the per-packet-offset setting in the child policer) and the packet is not discarded by the parent policer. If the result is ‟violate,” the bucket depth is not increased and the packet is discarded by the parent policer. When the parent policer discards a packet, any bucket depth increases (PIR, CIR and FIR) in the parent policer caused by the packet are canceled. This prevents packets that are discarded by the parent policer from consuming the child policers PIR, CIR and FIR bandwidth.
The policer-control-policy root max-rate setting may be overridden on each SAP or sub-profile where the policy is applied.
The no form of this command reverts to the default.
Default
max-rate max
Parameters
- rate
-
Specifies the max rate in kilobits per second. Defining the rate value is mutually exclusive with the max parameter. The rate (in kilobits per second) value must be defined as an integer that represents the number of kilobytes that the parent policer is decremented per second. The actual decrement is performed per packet based on the time that has elapsed since the last packet associated with the parent policer.
- max
-
Specifies the maximum frame-based bandwidth limit of this policer. The max parameter is mutually exclusive with defining a rate (in kilobits per second) value. When max is specified, the parent policer does not enforce a maximum rate on the aggregate throughput of the child policers. This is the default setting when the policer-control-policy is first created and is the value that the parent policer returns to when a no max-rate command is executed. In order for the parent policer to be effective, a rate (in kilobits per second) value should be specified.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
max-rate
Syntax
max-rate {rate | max}
no max-rate
Context
[Tree] (config>card>fp>ingress>network>qgrp>policer-ctrl-over max-rate)
[Tree] (config>card>fp>ingress>acc>qgrp>policer-ctrl-over max-rate)
Full Context
configure card fp ingress network queue-group policer-control-override max-rate
configure card fp ingress access queue-group policer-control-override max-rate
Description
This command defines the parent policer’s PIR leaky bucket’s decrement rate. A parent policer is created for each time the policer-control-policy is applied to either a SAP or subscriber instance. Packets that are not discarded by the child policers associated with the SAP or subscriber instance are evaluated against the parent policer’s PIR leaky bucket.
For each packet, the bucket is first decremented by the correct amount based on the decrement rate to derive the current bucket depth. The current depth is then compared to one of two discard thresholds associated with the packet. The first discard threshold (discard-unfair) is applied if the FIR (Fair Information Rate) leaky bucket in the packet’s child policer is in the confirming state. The second discard threshold (discard-all) is applied if the child policer's FIR leaky bucket is in the exceed state. Only one of the two thresholds is applied per packet. If the current depth of the parent policer PIR bucket is less than the threshold value, the parent PIR bucket is in the conform state for that particular packet. If the depth is equal to or greater than the applied threshold, the bucket is in the violate state for the packet.
If the result is ‟conform,” the bucket depth is increased by the size of the packet (plus or minus the per-packet-offset setting in the child policer) and the packet is not discarded by the parent policer. If the result is ‟violate,” the bucket depth is not increased and the packet is discarded by the parent policer. When the parent policer discards a packet, any bucket depth increases (PIR, CIR and FIR) in the parent policer caused by the packet are canceled. This prevents packets that are discarded by the parent policer from consuming the child policers PIR, CIR and FIR bandwidth.
The policer-control-policy root max-rate setting may be overridden on each SAP or sub-profile where the policy is applied.
The no form of this command returns the policer-control-policy’s parent policer maximum rate to max.
Default
max-rate max
Parameters
- rate
-
Specifies that a kilobits-per-second value is mutually exclusive with the max keyword. The kilobits-per-second value must be defined as an integer that represents the number of kilobytes that the parent policer will be decremented per second. The actual decrement is performed per packet based on the time that has elapsed since the last packet associated with the parent policer.
- max
-
The max keyword is mutually exclusive with defining a kilobits-per-second value. When max is specified, the parent policer does not enforce a maximum rate on the aggregate throughput of the child policers. This is the default setting when the policer-control-policy is first created and is the value that the parent policer returns to when no max-rate is executed. In order for the parent policer to be effective, a kilobits-per-second value should be specified.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
max-rate
Syntax
max-rate pir-rate
max-rate percent percent-rate
no max-rate
Context
[Tree] (config>port>sonet-sdh>path>egr-scheduler-override max-rate)
[Tree] (config>port>tdm>e3>egr-scheduler-override max-rate)
[Tree] (config>port>tdm>ds1>channel-group>egr-scheduler-override max-rate)
[Tree] (config>port>tdm>ds3>egr-scheduler-override max-rate)
[Tree] (config>port>tdm>e1>channel-group>egr-scheduler-override max-rate)
[Tree] (config>port>ethernet>egr-scheduler-override max-rate)
Full Context
configure port sonet-sdh path egress-scheduler-override max-rate
configure port tdm e3 egress-scheduler-override max-rate
configure port tdm ds1 channel-group egress-scheduler-override max-rate
configure port tdm ds3 egress-scheduler-override max-rate
configure port tdm e1 channel-group egress-scheduler-override max-rate
configure port ethernet egress-scheduler-override max-rate
Description
This command overrides the max-rate parameter found in the port-scheduler-policy associated with the port. When a max-rate is defined at the port or channel level, the port scheduler policies max-rate parameter is ignored.
The egress-scheduler-override max-rate command supports a parameter that allows the override command to restore the default of not having a rate limit on the port scheduler. This is helpful when the port scheduler policy has an explicit maximum rate defined and it is desirable to remove this limit at the port instance.
The no form of this command removes the maximum rate override from the egress port or channels port scheduler context. Once removed, the max-rate parameter from the port scheduler policy associated with the port or channel will be used by the local scheduler context.
Parameters
- pir-rate
-
Specifies the explicit maximum frame based bandwidth limit, in kilobits per second. This value overrides the QoS scheduler policy rate.
- percent-rate
-
Specifies the percent rate.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
- configure port sonet-sdh path egress-scheduler-override max-rate
7450 ESS, 7750 SR-7/12/12e, 7750 SR-a, 7750 SR-e
- configure port tdm e3 egress-scheduler-override max-rate
- configure port tdm ds1 channel-group egress-scheduler-override max-rate
- configure port tdm ds3 egress-scheduler-override max-rate
- configure port tdm e1 channel-group egress-scheduler-override max-rate
All
- configure port ethernet egress-scheduler-override max-rate
max-rate
Syntax
max-rate rate
no max-rate
Context
[Tree] (config>port>ethernet>egress>hs-sched-ovr max-rate)
Full Context
configure port ethernet egress hs-scheduler-overrides max-rate
Description
This command overrides the max-rate configured in the HS scheduler policy applied to the port egress.
The no form of this command removes the max-rate override from the port egress configuration.
Parameters
- rate
-
Specifies the explicit maximum frame based bandwidth limit, in megabits per second. This parameter is required when executing this command.
Platforms
7750 SR-7/12/12e
max-rate
Syntax
max-rate {rate | max}
Context
[Tree] (config>service>ipipe>sap>ingress>policer-control-override max-rate)
[Tree] (config>service>epipe>sap>ingress>policer-control-override max-rate)
[Tree] (config>service>ipipe>sap>egress>policer-control-override max-rate)
[Tree] (config>service>cpipe>sap>ingress>policer-control-override max-rate)
[Tree] (config>service>cpipe>sap>egress>policer-control-override max-rate)
[Tree] (config>service>epipe>sap>egress>policer-control-override max-rate)
Full Context
configure service ipipe sap ingress policer-control-override max-rate
configure service epipe sap ingress policer-control-override max-rate
configure service ipipe sap egress policer-control-override max-rate
configure service cpipe sap ingress policer-control-override max-rate
configure service cpipe sap egress policer-control-override max-rate
configure service epipe sap egress policer-control-override max-rate
Description
This command, within the SAP ingress and egress contexts, overrides the root arbiter parent policer max-rate that is defined within the policer-control-policy applied to the SAP.
When the override is defined, modifications to the policer-control-policy max-rate parameter have no effect on the SAP’s parent policer until the override is removed using the no max-rate command within the SAP.
The no form of this command returns the policer-control-policy’s parent policer maximum rate to max.
Parameters
- rate
-
Specifies the rate override in kilobits per second.
- max
-
Specifies the maximum rate override.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
- configure service ipipe sap egress policer-control-override max-rate
- configure service ipipe sap ingress policer-control-override max-rate
- configure service epipe sap egress policer-control-override max-rate
- configure service epipe sap ingress policer-control-override max-rate
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS
- configure service cpipe sap egress policer-control-override max-rate
- configure service cpipe sap ingress policer-control-override max-rate
max-rate
Syntax
max-rate {rate | max}
Context
[Tree] (config>service>vpls>sap>egress>policer-ctrl-over max-rate)
[Tree] (config>service>vpls>sap>ingress>policer-ctrl-over max-rate)
Full Context
configure service vpls sap egress policer-control-override max-rate
configure service vpls sap ingress policer-control-override max-rate
Description
This command, within the SAP ingress and egress contexts, overrides the root arbiter parent policer max-rate that is defined within the policer-control-policy applied to the SAP.
When the override is defined, modifications to the policer-control-policy max-rate parameter have no effect on the SAP’s parent policer until the override is removed using the no max-rate command within the SAP.
The no form of this command removes an explicit rate value from the aggregate rate therefore returning it to its default value.
Parameters
- rate | max
-
Specifies the max rate override in kilobits per second or use the maximum
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
max-rate
Syntax
max-rate {rate | max}
Context
[Tree] (config>service>ies>if>sap>ingress>policer-ctrl-over max-rate)
[Tree] (config>service>ies>if>sap>egress>policer-ctrl-over max-rate)
Full Context
configure service ies interface sap ingress policer-control-override max-rate
configure service ies interface sap egress policer-control-override max-rate
Description
This command, within the SAP ingress and egress contexts, overrides the root arbiter parent policer max-rate that is defined within the policer-control-policy applied to the SAP.
When the override is defined, modifications to the policer-control-policy max-rate parameter have no effect on the SAP’s parent policer until the override is removed using the no max-rate command within the SAP.
Parameters
- rate | max
-
Specifies the rate override in kilobits per second or use the maximum override value.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
max-rate
Syntax
max-rate {rate | max}
Context
[Tree] (config>service>vprn>if>sap>egress>policer-ctrl-over max-rate)
[Tree] (config>service>vprn>if>sap>ingress>policer-ctrl-over max-rate)
Full Context
configure service vprn interface sap egress policer-control-override max-rate
configure service vprn interface sap ingress policer-control-override max-rate
Description
This command, within the SAP ingress and egress contexts, overrides the root arbiter parent policer max-rate that is defined within the policer-control-policy applied to the SAP.
When the override is defined, modifications to the policer-control-policy max-rate parameter have no effect on the SAP’s parent policer until the override is removed using the no max-rate command within the SAP.
The no form of this command returns the policer-control-policy’s parent policer maximum rate to max.
Parameters
- rate | max
-
Specifies the rate override in kilobits per second or use the maximum override value.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
max-rate
Syntax
max-rate rate
no max-rate
Context
[Tree] (config>qos>plcr-ctrl-plcy>root max-rate)
Full Context
configure qos policer-control-policy root max-rate
Description
The max-rate command defines the parent policer’s PIR leaky bucket’s decrement rate. A parent policer is created for each time the policer-control-policy is applied to either a SAP or subscriber instance for the 7450 ESS and 7750 SR, or multiservice site instance for the 7950 XRS. Packets that are not discarded by the child policers associated with the SAP or subscriber or multiservice site instances are evaluated against the parent policer’s PIR leaky bucket.
For each packet, the bucket is first decremented by the correct amount based on the decrement rate to derive the current bucket depth. The current depth is then compared to one of two discard thresholds associated with the packet. The first discard threshold (discard-unfair) is applied if the FIR (Fair Information Rate) leaky bucket in the packet’s child policer is in the confirming state. The second discard threshold (discard-all) is applied if the child policer's FIR leaky bucket is in the exceed state. Only one of the two thresholds is applied per packet. If the current depth of the parent policer PIR bucket is less than the threshold value, the parent PIR bucket is in the conform state for that particular packet. If the depth is equal to or greater than the applied threshold, the bucket is in the violate state for the packet.
If the result is ‟conform,” the bucket depth is increased by the size of the packet (plus or minus the per-packet-offset setting in the child policer) and the packet is not discarded by the parent policer. If the result is ‟violate,” the bucket depth is not increased and the packet is discarded by the parent policer. When the parent policer discards a packet, any bucket depth increases (PIR, CIR and FIR) in the parent policer caused by the packet are canceled. This prevents packets that are discarded by the parent policer from consuming the child policers PIR, CIR, and FIR bandwidth.
The policer-control-policy root max-rate setting may be overridden on each SAP or sub-profile where the policy is applied.
The no form of this command returns the policer-control-policy’s parent policer maximum rate to max.
Parameters
- rate
-
The kilobits-per-second value must be defined as an integer that represents the number of kilobytes that the parent policer will be decremented per second. The actual decrement is performed per packet, based on the time that has elapsed since the last packet associated with the parent policer.
- max
-
When max is specified, the parent policer does not enforce a maximum rate on the aggregate throughput of the child policers. This is the default setting when the policer-control-policy is first created and is the value that the parent policer returns to when no max-rate is executed. In order for the parent policer to be effective, a kilobits-per-second value should be specified.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
max-rate
Syntax
max-rate rate
no max-rate
Context
[Tree] (config>qos>hs-scheduler-policy max-rate)
Full Context
configure qos hs-scheduler-policy max-rate
Description
This command defines an explicit maximum frame-based bandwidth limit for the HS scheduler policy scheduler context. If a maximum rate is defined that is smaller than the port rate, the port is rate-limited to the configured megabits per second value. This command can be executed at any time for any non-default existing HS scheduler policy.
The no form of the command removes an explicit rate value from the HS scheduler policy. After the explicit rate value is removed, all instances of the scheduler policy on HSQ egress ports are allowed to run at the available line rate unless the instance has a max rate override in place.
Parameters
- rate
-
Specifies the explicit maximum frame-based bandwidth limit, in megabits per second. This parameter is required when executing this command.
Platforms
7750 SR-7/12/12e
max-rate
Syntax
max-rate pir-rate
max-rate percent percent-rate
no max-rate
Context
[Tree] (config>qos>port-scheduler-policy max-rate)
Full Context
configure qos port-scheduler-policy max-rate
Description
This command defines an explicit maximum frame-based bandwidth limit for the port scheduler policies scheduler context. By default, when a scheduler policy is associated with a port or channel, the instance of the scheduler on the port automatically limits the bandwidth to the lesser of port or channel line rate and a possible egress-rate value (for Ethernet ports). If a max-rate is defined that is smaller than the port or channel rate, the expressed kilobits per second value is used instead. The max-rate command is another way to sub-rate the port or channel. This command can be used on channels only on the 7450 ESS and 7750 SR.
The max-rate command may be executed at any time for an existing port-scheduler-policy. When a new max-rate is given for a policy, the system evaluates all instances of the policy to see if the configured rate is smaller than the available port or channel bandwidth. If the rate is smaller and the maximum rate is not currently overridden on the scheduler instance, the scheduler instance is updated with the new maximum rate value.
The max-rate value defined in the policy may be overridden on each scheduler instance. If the maximum rate is explicitly defined as an override on a port or channel, the policies max-rate value has no effect.
The no form of this command removes an explicit rate value from the port scheduler policy. When removed, all instances of the scheduler policy on egress ports or channel are allowed to run at the available line rate unless the instance has a max-rate override in place.
Parameters
- pir-rate
-
Specifies the PIR rate, in kilobits per second.
- percent percent-rate
-
Specifies the percent rate.
Platforms
All
max-retries-estab
max-retries-estab
Syntax
max-retries-estab max-retries
no max-retries-estab
Context
[Tree] (config>router>l2tp>group>tunnel max-retries-estab)
[Tree] (config>router>l2tp max-retries-estab)
[Tree] (config>service>vprn>l2tp max-retries-estab)
[Tree] (config>service>vprn>l2tp>group>tunnel max-retries-estab)
[Tree] (config>router>l2tp>group max-retries-estab)
[Tree] (config>service>vprn>l2tp>group max-retries-estab)
Full Context
configure router l2tp group tunnel max-retries-estab
configure router l2tp max-retries-estab
configure service vprn l2tp max-retries-estab
configure service vprn l2tp group tunnel max-retries-estab
configure router l2tp group max-retries-estab
configure service vprn l2tp group max-retries-estab
Description
This command configures the number of retries allowed for this L2TP tunnel while it is established, before its control connection goes down.
The no form of this command removes the value from the configuration.
Default
no max-retries-estab
Parameters
- max-retries
-
Specifies the maximum number of retries for an established tunnel.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
max-retries-not-estab
max-retries-not-estab
Syntax
max-retries-not-estab max-retries
no max-retries-not-estab
Context
[Tree] (config>service>vprn>l2tp>group>tunnel max-retries-not-estab)
[Tree] (config>router>l2tp>group max-retries-not-estab)
[Tree] (config>service>vprn>l2tp max-retries-not-estab)
[Tree] (config>router>l2tp max-retries-not-estab)
[Tree] (config>service>vprn>l2tp>group max-retries-not-estab)
[Tree] (config>router>l2tp>group>tunnel max-retries-not-estab)
Full Context
configure service vprn l2tp group tunnel max-retries-not-estab
configure router l2tp group max-retries-not-estab
configure service vprn l2tp max-retries-not-estab
configure router l2tp max-retries-not-estab
configure service vprn l2tp group max-retries-not-estab
configure router l2tp group tunnel max-retries-not-estab
Description
This command configures the number of retries allowed for this L2TP tunnel while it is not established, before its control connection goes down.
The no form of this command removes the value from the configuration.
Default
no max-retries-not-estab
Parameters
- max-retries
-
Specifies the maximum number of retries for non-established tunnels.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
max-routes
max-routes
Syntax
max-routes routes
no max-routes
Context
[Tree] (config>aaa>route-downloader max-routes)
Full Context
configure aaa route-downloader max-routes
Description
This command determines the upper limits for total number of routes to be received and accepted by the system. The total number is inclusive of both IPv4 and IPv6 addresses and no differentiation is needed across protocols. It includes the sum of both. Once this limit is reached, the download process stops sending new access-requests until the next download-interval expires.
The no form of this command reverts to the default value.
Default
max-routes 200000
Parameters
- routes
-
Specifies the maximum number of the routes imported.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
max-rx-defect-window
max-rx-defect-window
Syntax
max-rx-defect-window seconds
no max-rx-defect-window
Context
[Tree] (config>eth-tunnel>path>eth-cfm>mep>grace>eth-ed max-rx-defect-window)
[Tree] (config>lag>eth-cfm>mep>grace>eth-ed max-rx-defect-window)
[Tree] (config>port>ethernet>eth-cfm>mep>grace>eth-ed max-rx-defect-window)
[Tree] (config>eth-ring>path>eth-cfm>mep>grace>eth-ed max-rx-defect-window)
Full Context
configure eth-tunnel path eth-cfm mep grace eth-ed max-rx-defect-window
configure lag eth-cfm mep grace eth-ed max-rx-defect-window
configure port ethernet eth-cfm mep grace eth-ed max-rx-defect-window
configure eth-ring path eth-cfm mep grace eth-ed max-rx-defect-window
Description
This command limits the duration of the received ETH-ED expected defect window to the lower value of either the received value from the peer or this parameter.
The no form of this command removes the limitation, and any valid defect window value received from a peer MEP in the ETH-ED PDU will be used.
Default
no max-rx-defect-window
Parameters
- seconds
-
Specifies the duration, in seconds, of the maximum expected defect window.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
max-rx-defect-window
Syntax
max-rx-defect-window seconds
no max-rx-defect-window
Context
[Tree] (config>service>ipipe>sap>eth-cfm>mep>grace>eth-ed max-rx-defect-window)
[Tree] (config>service>epipe>sap>eth-cfm>mep>grace>eth-ed max-rx-defect-window)
[Tree] (config>service>epipe>spoke-sdp>eth-cfm>mep>grace>eth-ed max-rx-defect-window)
Full Context
configure service ipipe sap eth-cfm mep grace eth-ed max-rx-defect-window
configure service epipe sap eth-cfm mep grace eth-ed max-rx-defect-window
configure service epipe spoke-sdp eth-cfm mep grace eth-ed max-rx-defect-window
Description
This command limits the duration of the received ETH-ED expected defect window to the lower value of either the received value from the peer or this parameter.
The no form of this command removes the limitation, and any valid defect window value received from a peer MEP in the ETH-ED PDU will be used.
Default
no max-rx-defect-window
Parameters
- seconds
-
Specifies the duration, in seconds, of the maximum expected defect window.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
max-rx-defect-window
Syntax
max-rx-defect-window seconds
no max-rx-defect-window
Context
[Tree] (config>service>vpls>eth-cfm>mep>grace>eth-ed max-rx-defect-window)
[Tree] (config>service>vpls>mesh-sdp>eth-cfm>mep>grace>eth-ed max-rx-defect-window)
[Tree] (config>service>vpls>spoke-sdp>eth-cfm>mep>grace>eth-ed max-rx-defect-window)
[Tree] (config>service>vpls>sap>eth-cfm>mep>grace>eth-ed max-rx-defect-window)
Full Context
configure service vpls eth-cfm mep grace eth-ed max-rx-defect-window
configure service vpls mesh-sdp eth-cfm mep grace eth-ed max-rx-defect-window
configure service vpls spoke-sdp eth-cfm mep grace eth-ed max-rx-defect-window
configure service vpls sap eth-cfm mep grace eth-ed max-rx-defect-window
Description
This command limits the duration of the received ETH-ED expected defect window to the lower value of either the received value from the peer or this parameter.
The no form of this command removes the limitation, and any valid defect window value received from a peer MEP in the ETH-ED PDU will be used.
Default
no max-rx-defect-window
Parameters
- seconds
-
Specifies the duration, in seconds, of the maximum expected defect window.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
max-rx-defect-window
Syntax
max-rx-defect-window seconds
no max-rx-defect-window
Context
[Tree] (config>service>ies>if>sap>eth-cfm>mep>grace>eth-ed max-rx-defect-window)
[Tree] (config>service>ies>if>spoke-sdp>eth-cfm>mep>grace>eth-ed max-rx-defect-window)
[Tree] (config>service>ies>sub-if>grp-if>sap>eth-cfm>mep>grace>eth-ed max-rx-defect-window)
Full Context
configure service ies interface sap eth-cfm mep grace eth-ed max-rx-defect-window
configure service ies interface spoke-sdp eth-cfm mep grace eth-ed max-rx-defect-window
configure service ies subscriber-interface group-interface sap eth-cfm mep grace eth-ed max-rx-defect-window
Description
This command limits the duration of the received ETH-ED expected defect window to the lower value of either the received value from the peer or this parameter.
The no form of this command removes the limitation, and any valid defect window value received from a peer MEP in the ETH-ED PDU will be used.
Default
no max-rx-defect-window
Parameters
- seconds
-
Specifies the duration, in seconds, of the maximum expected defect window
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
- configure service ies interface sap eth-cfm mep grace eth-ed max-rx-defect-window
- configure service ies interface spoke-sdp eth-cfm mep grace eth-ed max-rx-defect-window
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s
- configure service ies subscriber-interface group-interface sap eth-cfm mep grace eth-ed max-rx-defect-window
max-rx-defect-window
Syntax
max-rx-defect-window seconds
no max-rx-defect-window
Context
[Tree] (config>service>vprn>if>sap>eth-cfm>mep>grace>eth-ed max-rx-defect-window)
[Tree] (config>service>vprn>sub-if>grp-if>sap>eth-cfm>mep>grace>eth-ed max-rx-defect-window)
[Tree] (config>service>vprn>if>spoke-sdp>eth-cfm>mep>grace>eth-ed max-rx-defect-window)
Full Context
configure service vprn interface sap eth-cfm mep grace eth-ed max-rx-defect-window
configure service vprn subscriber-interface group-interface sap eth-cfm mep grace eth-ed max-rx-defect-window
configure service vprn interface spoke-sdp eth-cfm mep grace eth-ed max-rx-defect-window
Description
This command limits the duration of the received ETH-ED expected defect window to the lower value of either the received value from the peer or this parameter.
The no form of this command removes the limitation, and any valid defect window value received from a peer MEP in the ETH-ED PDU will be used.
Default
no max-rx-defect-window
Parameters
- seconds
-
Specifies the duration, in seconds, of the maximum expected defect window
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
- configure service vprn interface sap eth-cfm mep grace eth-ed max-rx-defect-window
- configure service vprn interface spoke-sdp eth-cfm mep grace eth-ed max-rx-defect-window
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s
- configure service vprn subscriber-interface group-interface sap eth-cfm mep grace eth-ed max-rx-defect-window
max-rx-defect-window
Syntax
max-rx-defect-window seconds
no max-rx-defect-window
Context
[Tree] (config>router>if>eth-cfm>mep>grace>eth-ed max-rx-defect-window)
Full Context
configure router interface eth-cfm mep grace eth-ed max-rx-defect-window
Description
This command limits the duration of the received ETH-ED expected defect window to the lower value of either the received value from the peer or this parameter.
The no form of this command removes the limitation, and any valid defect window value received from a peer MEP in the ETH-ED PDU will be used.
Default
no max-rx-defect-window
Parameters
- seconds
-
Specifies the duration, in seconds, of the maximum expected defect window.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
max-sess-prefix
max-sess-prefix
Syntax
max-sess-prefix count
no max-sess-prefix
Context
[Tree] (config>test-oam>twamp>server>prefix max-sess-prefix)
Full Context
configure test-oam twamp server prefix max-sess-prefix
Description
This command configures the maximum number of concurrent TWAMP-Test sessions by clients with an IP address in a specific prefix. A new test session (described by a Request-TW-Session message) is rejected if accepting it would cause either the limit defined by this command or the server limit (max-sess-server) to be exceeded.
The no form of this command returns the value to the default.
Default
max-sess-prefix 32
Parameters
- count
-
Specifies the maximum number of concurrent test sessions.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
max-sess-server
max-sess-server
Syntax
max-sess-server count
no max-sess-server
Context
[Tree] (config>test-oam>twamp>server max-sess-server)
Full Context
configure test-oam twamp server max-sess-server
Description
This command configures the maximum number of concurrent TWAMP-Test sessions across all allowed clients. A new test session (described by a Request-TW-Session message) is rejected if accepting it would cause either the limit defined by this command or a prefix limit (max-sess-prefix) to be exceeded.
The no form of this command returns the value to the default.
Default
max-sess-server 32
Parameters
- count
-
Specifies the maximum number of concurrent test sessions.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
max-sessions
max-sessions
Syntax
max-sessions sessions
no max-sessions
Context
[Tree] (config>mcast-mgmt>mcast-info-plcy>video-policy>video-if max-sessions)
Full Context
configure mcast-management multicast-info-policy video-policy video-interface max-sessions
Description
This command configures the per-client maximum number of sessions.
The no form of the command reverts to the default value.
Default
max-sessions 256
Parameters
- sessions
-
Specifies the per-client maximum number of sessions.
Platforms
7450 ESS, 7750 SR-1, 7750 SR-7/12/12e, 7750 SR-1s, 7750 SR-2s, 7750 SR-7s, 7750 SR-14s
max-sessions
Syntax
max-sessions number
Context
[Tree] (config>router>bgp>group>dynamic-neighbor>interface max-sessions)
[Tree] (config>service>vprn>bgp>group>dynamic-neighbor>interface max-sessions)
Full Context
configure router bgp group dynamic-neighbor interface max-sessions
configure service vprn bgp group dynamic-neighbor interface max-sessions
Description
This command configures the maximum number of dynamic sessions that are allowed to be set up on the interface as a result of accepting sessions from link-local addresses or initiating sessions by receiving IPv6 router advertisements.
Default
max-sessions 1
Parameters
- number
-
Specifies the maximum number of sessions.
Platforms
All
max-sessions-per-cid
max-sessions-per-cid
Syntax
max-sessions-per-cid sessions [allow-sessions-without-cid]
no max-sessions-per-cid
Context
[Tree] (config>subscr-mgmt>ppp-policy max-sessions-per-cid)
Full Context
configure subscriber-mgmt ppp-policy max-sessions-per-cid
Description
This command configures the maximum number of PPPoE sessions with the same Agent Circuit ID that can be active on the same SAP or MSAP. The limit is enforced in the discovery phase, prior to PAP or CHAP authentication and is based on the Agent Circuit ID sub-option that is present in the vendor-specific PPPoE access loop identification tag added in PADI and PADR messages by a PPPoE intermediate agent.
When the optional allow-sessions-without-cid keyword is specified, PPPoE sessions without an Agent Circuit ID can be established. The configured sessions limit does not apply to these sessions.
By default, there is no limit for the number of PPPoE sessions with the same Agent Circuit ID that are active on the same SAP or MSAP. Sessions without Agent Circuit ID can be established.
The no form of this command reverts to the default value.
Default
no max-sessions-per-cid
Parameters
- sessions
-
Specifies the maximum number of sessions with the same circuit ID that can be active on the same SAP or MSAP.
- allow-sessions-without-cid
-
Specifies to enable support for PPPoE sessions without a circuit ID while a max-sessions-per-cid limit is configured on a SAP or MSAP.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
max-sessions-per-mac
max-sessions-per-mac
Syntax
max-sessions-per-mac sessions [allow-same-circuit-id-for-dhcp]
no max-sessions-per-mac
Context
[Tree] (config>subscr-mgmt>ppp-policy max-sessions-per-mac)
Full Context
configure subscriber-mgmt ppp-policy max-sessions-per-mac
Description
This command sets the maximum PPP sessions that can be opened for a given MAC address.
To enable IPv4 address allocation using the internal DHCPv4 client for multiple PPPoE sessions on a single SAP and having the same MAC address and circuit-ID, the optional CLI parameter allow-same-circuit-id-for-dhcp should be added. The SR OS local DHCP server detects the additional vendor-specific options inserted by the internal DHCPv4 client and use an extended unique key for lease allocation.
The no form of this command reverts to the default value.
Parameters
- sessions
-
Specifies the maximum PPP sessions that can be opened for the given MAC address.
- allow-same-circuit-id-for-dhcp
-
Sets the support for IPv4 address allocation using the internal DHCPv4 client for multiple PPPoE sessions on a single SAP that have the same MAC address and circuit ID.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
max-setup-time
max-setup-time
Syntax
max-setup-time [[up-interval] | infinite]
no max-setup-time
Context
[Tree] (config>lag>bfd>family max-setup-time)
Full Context
configure lag bfd family max-setup-time
Description
This command specifies the maximum amount of time the router will forward traffic over a link that has transitioned from Standby to Active, before the micro-BFD session must be fully established (Up state).
The no form of this command returns the timer value to the default (0) which indicates that forwarding will not start until the BFD session is established.
Default
max-setup-time infinite
Parameters
- up-interval
-
Specifies the amount of time, in milliseconds.
- infinite
-
Specifies no end time to forward traffic.
Platforms
All
max-size
max-size
Syntax
max-size size
no max-size
Context
[Tree] (config>open-flow>of-switch>flowtable max-size)
Full Context
configure open-flow of-switch flowtable max-size
Description
This command configures the size for the specified flow table. The OpenFlow switch instance must be shutdown to modify this parameter.
The no form of this command restores the default size.
Default
max-size 1000
Parameters
- size
-
Specifies the maximum size limit for the flow table. The size limit is a total for both IPv4 and IPv6.
Platforms
All
max-sources
max-sources
Syntax
max-sources max-sources
no max-sources
Context
[Tree] (config>service>vprn>igmp>grp-if max-sources)
[Tree] (config>service>vprn>mld>interface max-sources)
[Tree] (config>service>vprn>igmp>if max-sources)
Full Context
configure service vprn igmp group-interface max-sources
configure service vprn mld interface max-sources
configure service vprn igmp interface max-sources
Description
This command specifies the maximum number of sources for which IGMP can have local receiver information based on received IGMP reports on this interface. When this configuration is changed dynamically to a value lower than currently accepted number of sources, the sources that are already accepted are not deleted. Only new sources will not be allowed.
Parameters
- sources
-
Specifies the maximum number of sources for this interface.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
- configure service vprn igmp group-interface max-sources
All
- configure service vprn mld interface max-sources
- configure service vprn igmp interface max-sources
max-sources
Syntax
max-sources value
no max-sources
Context
[Tree] (config>router>igmp>if max-sources)
[Tree] (config>router>igmp>group-interface max-sources)
Full Context
configure router igmp interface max-sources
configure router igmp group-interface max-sources
Description
This command configures the maximum number of group sources for this group-interface.
Parameters
- value
-
Specifies the maximum number of group sources.
Platforms
All
- configure router igmp interface max-sources
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
- configure router igmp group-interface max-sources
max-sources
Syntax
max-sources [grp-source]
no max-sources
Context
[Tree] (config>router>mld>group-interface max-sources)
[Tree] (config>router>mld>if max-sources)
Full Context
configure router mld group-interface max-sources
configure router mld interface max-sources
Description
This command configures the maximum number of group sources for this interface.
The no form of this command reverts to the default.
Default
no max-sources
Parameters
- grp-source
-
Specifies the maximum number of group sources for this interface.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
- configure router mld group-interface max-sources
All
- configure router mld interface max-sources
max-sr-labels
max-sr-labels
Syntax
max-sr-labels label-stack-size [additional-frr-labels labels]
no max-sr-labels
Context
[Tree] (config>router>mpls>lsp max-sr-labels)
[Tree] (config>router>mpls>lsp-template max-sr-labels)
Full Context
configure router mpls lsp max-sr-labels
configure router mpls lsp-template max-sr-labels
Description
This command configures the maximum number of labels which the ingress LER can push for a given SR-TE LSP.
This command is used to allow room to insert additional transport, service, and other labels when packets are forwarded in a given context.
The max-sr-labels label-stack-size value should reflect the desired maximum label stack of the primary path of the SR-TE LSP.
The value in additional-frr-labels labels should reflect additional labels inserted by remote LFA for the backup next-hop of the SR-TE LSP.
The sum of both label values represents the worst case transport of SR label stack size for this SR-TE LSP and is populated by MPLS in the TTM such that services and shortcut applications can check it to decide if a service can be bound or a route can be resolved to this SR-TE LSP.
The maximum label stack supported by the router is always signaled by PCC in the PCEP Open object as part of the as SR-PCE-CAPABILITY TLV. It is referred to as the Maximum Stack Depth (MSD).
In addition, the per-LSP value for the max-sr-labels option, if configured, is signaled by PCC to PCE in the Segment-ID (SID) Depth value in a METRIC object for both a PCE computed LSP and a PCE controlled LSP. PCE will compute and provide the full explicit path with TE-links specified. If there is no path with the number of hops lower than the MSD value, or the Segment-ID (SID) Depth value if signaled, a reply with no path will be returned to PCC.
For a PCC controlled LSP, if the label stack returned by the TE-DB’s hop-to-label translation exceeds the per LSP maximum SR label stack size, the LSP is brought down.
The no form of this command reverts to the default value.
Default
max-sr-labels 6 additional-frr-labels 1
Parameters
- label-stack-size
-
Specifies the label stack size.
- additional-frr-labels labels
-
Specifies the addition FRR labels.
Platforms
All
max-srte-pce-init-lsps
max-srte-pce-init-lsps
Syntax
max-srte-pce-init-lsps max-number
no max-srte-pce-init-lsps
Context
[Tree] (config>router>pcep>pcc max-srte-pce-init-lsps)
Full Context
configure router pcep pcc max-srte-pce-init-lsps
Description
This command configures the maximum number of PCE-initiated SR-TE LSPs that can be created by the router.
The no form of the command sets this value to the default.
Default
max-srte-pce-init-lsps 8191
Parameters
- max-number
-
Specifies the maximum number of SR-TE PCE-initiated LSPs.
Platforms
All
max-stats
max-stats
Syntax
[no] max-stats
Context
[Tree] (config>router>mpls>ingr-stats>p2mp-template-lsp max-stats)
[Tree] (config>router>mpls>ingr-stats>p2p-template-lsp max-stats)
[Tree] (config>router>mpls>lsp-template>egr-stats max-stats)
[Tree] (config>router>mpls>lsp>egr-stats max-stats)
Full Context
configure router mpls ingress-statistics p2mp-template-lsp max-stats
configure router mpls ingress-statistics p2p-template-lsp max-stats
configure router mpls lsp-template egr-stats max-stats
configure router mpls lsp egr-stats max-stats
Description
This command enables accounting and statistical data collection. When applying accounting policies the data, by default, is collected in the appropriate records and written to the designated billing file.
The config>router>mpls>ingr-stats>p2mp-template-lsp>max-stats command is supported on the 7750 SR, 7950 XRS, and with VPLS only on the 7450 ESS.
When the no max-stats command is issued the statistics are still accumulated by the forwarding engine. However, the CPU will not obtain the results and write them to the billing file. If a subsequent max-stats command is issued then the counters written to the billing file include all the traffic while the no max-stats command was in effect.
Default
max-stats
Platforms
All
max-suppress
max-suppress
Syntax
max-suppress minutes
no max-suppress
Context
[Tree] (config>router>policy-options>damping max-suppress)
Full Context
configure router policy-options damping max-suppress
Description
This command configures the maximum suppression parameter for the route damping profile.
This value indicates the maximum time, expressed in minutes, that a route can remain suppressed.
The no form of this command removes the maximum suppression parameter from the damping profile.
Default
no max-suppress
Parameters
- minutes
-
Specifies the maximum suppression time, in minutes, expressed as a decimal integer.
Platforms
All
max-throughput-octet-count
max-throughput-octet-count
Syntax
[no] max-throughput-octet-count
Context
[Tree] (config>log>acct-policy>cr>aa>aa-from-sub-cntr max-throughput-octet-count)
[Tree] (config>log>acct-policy>cr>aa>aa-to-sub-cntr max-throughput-octet-count)
Full Context
configure log accounting-policy custom-record aa-specific from-aa-sub-counters max-throughput-octet-count
configure log accounting-policy custom-record aa-specific to-aa-sub-counters max-throughput-octet-count
Description
This command includes the maximum throughput as measured in the octet count.
The no form of this command excludes the maximum throughput octet count.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
max-throughput-packet-count
max-throughput-packet-count
Syntax
[no] max-throughput-packet-count
Context
[Tree] (config>log>acct-policy>cr>aa>aa-from-sub-cntr max-throughput-packet-count)
[Tree] (config>log>acct-policy>cr>aa>aa-to-sub-cntr max-throughput-packet-count)
Full Context
configure log accounting-policy custom-record aa-specific from-aa-sub-counters max-throughput-packet-count
configure log accounting-policy custom-record aa-specific to-aa-sub-counters max-throughput-packet-count
Description
This command includes the maximum throughput as measured in the packet count. This command only applies to the 7750 SR.
The no form of this command excludes the maximum throughput packet count.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
max-throughput-stats
max-throughput-stats
Syntax
[no] max-throughput-stats
Context
[Tree] (config>app-assure>group>statistics>aa-sub max-throughput-stats)
Full Context
configure application-assurance group statistics aa-sub max-throughput-stats
Description
This command enables the collection of max-throughput statistics.
The no form of this command disables the collection.
Default
no max-throughput-stats
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
max-throughput-timestamp
max-throughput-timestamp
Syntax
[no] max-throughput-timestamp
Context
[Tree] (config>log>acct-policy>cr>aa>aa-to-sub-cntr max-throughput-timestamp)
[Tree] (config>log>acct-policy>cr>aa>aa-from-sub-cntr max-throughput-timestamp)
Full Context
configure log accounting-policy custom-record aa-specific to-aa-sub-counters max-throughput-timestamp
configure log accounting-policy custom-record aa-specific from-aa-sub-counters max-throughput-timestamp
Description
This command includes the timestamp of the maximum throughput. This command only applies to the 7750 SR.
The no form of this command excludes the timestamp.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
max-time
max-time
Syntax
max-time minutes
no max-time
Context
[Tree] (config>router>l2tp>tunnel-selection-blacklist max-time)
[Tree] (config>service>vprn>l2tp>tunnel-selection-blacklist max-time)
Full Context
configure router l2tp tunnel-selection-blacklist max-time
configure service vprn l2tp tunnel-selection-blacklist max-time
Description
This command configures time for which an entity (peer or a tunnel) are kept in the denylist.
The no form of this command reverts to the default.
Default
max-time 5
Parameters
- minutes
-
Specifies the maximum time a tunnel or peer may remain in the denylist.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
max-time-granularity
max-time-granularity
Syntax
[no] max-time-granularity time
Context
[Tree] (config>system>telemetry>notification-bundling max-time-granularity)
Full Context
configure system telemetry notification-bundling max-time-granularity
Description
This command sets the maximum time interval during which telemetry notifications are bundled. All bundled notifications will have the same timestamp, which is the timestamp of the bundle.
The no form of this command returns the time granularity to the default value.
Default
max-time-granularity 100
Parameters
- time
-
Specifies the maximum time interval during which telemetry notifications are bundled, in milliseconds.
Platforms
All
max-ttl
max-ttl
Syntax
max-ttl ttl-value
no max-ttl
Context
[Tree] (config>test-oam>ldp-treetrace>path-discovery max-ttl)
Full Context
configure test-oam ldp-treetrace path-discovery max-ttl
Description
This command configures the maximum number of hops the path discovery traces in the path of each FEC to be discovered.
The no form of this command resets the time out to its default value.
Default
no max-ttl
Parameters
- ttl-value
-
Specifies the maximum label time-to-live value for an LSP trace request during the tree discovery.
Platforms
All
max-tx-delay
max-tx-delay
Syntax
max-tx-delay deci-seconds
no max-tx-delay
Context
[Tree] (config>mcast-mgmt>mcast-rprt-dest max-tx-delay)
Full Context
configure mcast-management mcast-reporting-dest max-tx-delay
Description
This command specifies the time interval before the packet starts transmitting towards the destination. When an IGMP event is encoded and ready to be transported, a buffer for the packet is allocated (if not already existent). The events are written into this buffer. Along with the initial buffer creation, a timer is started. The trigger for the transmission of the packet is either the TX buffer being filled up to 1400 B, or the timer expiry, whichever comes first.
The no form of this command reverts to the default.
Parameters
- deci-seconds
-
Specifies the maximum delay after which any cached reports are flushed to the reporting destination.
Platforms
All
max-tx-delay
Syntax
max-tx-delay deciseconds
no max-tx-delay
Context
[Tree] (config>service>nat>syslog>syslog-export-policy max-tx-delay)
Full Context
configure service nat syslog syslog-export-policy max-tx-delay
Description
This command enables aggregation of flow log messages within a syslog frame. It introduces a delay during which logs are collected in each BB-ISA so they can be sent in a single syslog message to conserve system resources and network bandwidth.
When aggregation is enabled, generation of a syslog frame carrying multiple flow logs is triggered by one of the two events (whichever occurs first):
-
Expiry of the max-tx-delay timer
-
Exceeding MTU size
The no form of the command reverts to the default.
Default
max-tx-delay 3
Parameters
- deciseconds
-
Specifies the maximum time a syslog message is delayed in the system's output buffer.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
max-ve-id
max-ve-id
Syntax
max-ve-id value
no max-ve-id
Context
[Tree] (config>service>vpls>bgp-vpls max-ve-id)
Full Context
configure service vpls bgp-vpls max-ve-id
Description
This command configures the allowed range for the VE-id value: locally configured and received in a NLRI. Configuration of a VE-id higher than the value specified in this command is not allowed.
Also upon reception of a higher VE-id in an NLRI imported in this VPLS instance (RT is the configured import RT) the following action must be taken:
-
a trap must be generated informing the operator of the mismatch.
-
NLRI must be dropped
-
no service labels are to be installed for this VE-id
-
no new NLRI must be generated if a new offset is required for VE-id.
The no form of this command sets the max-ve-id to un-configured. The BGP VPLS status should be administratively down for ‟no max-ve-id” to be used.
The max-ve-id value can be changed without shutting down bgp-vpls if the newly provisioned value does not conflict with the already configured local VE-ID. If the value of the local-VE-ID is higher than the new max-ve-id value the command is rejected. The operator needs to decrease first the VE-ID before running the command.
The actions taken for other max-ve-id values are as follows:
-
max-ve-id value higher than all VE-IDs (local and received) is allowed and there are no effects.
-
max-ve-id higher than the local VE-ID but smaller than the remote VE-IDs:
-
Provisioning is allowed
-
A warning message will be generated stating that ‟Higher VE-ID values were received in the BGP VPLS context. Related pseudowires will be removed.”
-
The pseudowires associated with the higher VE-IDs will be removed locally.
-
This is a situation that should be corrected by the operator as the pseudowire may be down just at the local PE, consuming unnecessarily core bandwidth. The higher VE-IDs should be removed or lowered.
-
If the max-ve-id has increased a BGP route refresh is sent to the VPLS community to get the routes which might have been rejected earlier due to max-ve-id check. A max-ve-id value needs to be provisioned for BGP VPLS to be in ‟no shutdown” state.
Default
no max-ve-id
Parameters
- value
-
Specifies the allowed range of [1-value] for the VE-id. The configured value must be bigger than the existing VE-ids
Platforms
All
max-wait-to-advertise
max-wait-to-advertise
Syntax
max-wait-to-advertise seconds
no max-wait-to-advertise
Context
[Tree] (config>service>vprn>bgp>convergence>family max-wait-to-advertise)
Full Context
configure service vprn bgp convergence family max-wait-to-advertise
Description
This command configures the maximum amount of time that BGP waits until it starts advertising IPv4-unicast or IPv6-unicast routes to its BGP peers. For IPv4-unicast routes, seconds is measured from the time when the first peer that supports the IPv4-unicast address family comes up. For IPv6-unicast routes seconds is measured from the time when the first peer that negotiates the IPv6-unicast address family comes up.
The time limit configured by this command should allow sufficient time for all important peers to re-establish their sessions with the restarting router and advertise their complete set of IPv4-unicast or IPv6-unicast routes (followed by the applicable End of RIB marker).
The no form of this command implements the default value, which is three times the value of the min-wait-to-advertise time limit.
Default
no max-wait-to-advertise
Parameters
- seconds
-
Specifies the maximum amount of time, in seconds, that BGP waits until IPv4-unicast or IPv6-unicast routes are advertised to peers.
Platforms
All
max-wait-to-advertise
Syntax
max-wait-to-advertise seconds
no max-wait-to-advertise
Context
[Tree] (config>router>bgp>convergence>family max-wait-to-advertise)
Full Context
configure router bgp convergence family max-wait-to-advertise
Description
This command configures the maximum amount of time that BGP waits until it starts advertising IPv4-unicast or IPv6-unicast routes to its BGP peers. For IPv4-unicast routes, the time limit value is measured from the time when the first peer that supports the IPv4-unicast address family comes up. For IPv6-unicast routes the time limit value is measured from the time when the first peer that negotiates the IPv6-unicast address family comes up.
The time limit configured by this command should allow sufficient time for all important peers to re-establish their sessions with the restarting router and advertise their complete set of IPv4-unicast or IPv6-unicast routes (followed by the applicable End of RIB marker).
The no form of this command implements the default value, which is three times the value of the min-wait-to-advertise time-limit.
Default
no max-wait-to-advertise
Parameters
- seconds
-
Specifies the maximum amount of time, in seconds, that BGP waits until IPv4-unicast or IPv6-unicast routes are advertised to peers.
Platforms
All
maximum-cert-chain-depth
maximum-cert-chain-depth
Syntax
maximum-cert-chain-depth level
no maximum-cert-chain-depth
Context
[Tree] (config>system>security>pki maximum-cert-chain-depth)
Full Context
configure system security pki maximum-cert-chain-depth
Description
This command defines the maximum depth of certificate chain verification. This number is applied system wide.
The no form of this command reverts to the default.
Default
maximum-cert-chain-depth 7
Parameters
- level
-
Specifies the maximum depth level of certificate chain verification, range from 1 to 7. the certificate under verification is not counted in. for example, if this parameter is set to 1, then the certificate under verification must be directly signed by trust anchor CA.
Platforms
All
maximum-client-lead-time
maximum-client-lead-time
Syntax
maximum-client-lead-time [hrs hours] [min minutes] [sec seconds]
no maximum-client-lead-time
Context
[Tree] (config>router>dhcp6>server>failover maximum-client-lead-time)
[Tree] (config>router>dhcp6>server>pool>failover maximum-client-lead-time)
[Tree] (config>service>vprn>dhcp>server>pool>failover maximum-client-lead-time)
[Tree] (config>router>dhcp>server>pool>failover maximum-client-lead-time)
[Tree] (config>service>vprn>dhcp>server>failover maximum-client-lead-time)
[Tree] (config>router>dhcp>server>failover maximum-client-lead-time)
[Tree] (config>service>vprn>dhcp6>server>pool>failover maximum-client-lead-time)
[Tree] (config>service>vprn>dhcp6>server>failover maximum-client-lead-time)
Full Context
configure router dhcp6 local-dhcp-server failover maximum-client-lead-time
configure router dhcp6 server pool failover maximum-client-lead-time
configure service vprn dhcp local-dhcp-server pool failover maximum-client-lead-time
configure router dhcp server pool failover maximum-client-lead-time
configure service vprn dhcp local-dhcp-server failover maximum-client-lead-time
configure router dhcp local-dhcp-server failover maximum-client-lead-time
configure service vprn dhcp6 local-dhcp-server pool failover maximum-client-lead-time
configure service vprn dhcp6 local-dhcp-server failover maximum-client-lead-time
Description
The command configures the maximum time that a DHCP server can extend client’s lease time beyond the lease time currently known by the DHCP partner node. In dual-homed environment, the initial lease time for all DHCP clients is by default restricted to MCLT. Consecutive DHCP renews can extend the lease time beyond the MCLT.
The maximum client lead time (MCLT) is a safeguard against IP address/prefix duplication in cases of a lease synchronization failure when local-remote failover model is deployed.
Once the intercommunication link failure between the redundant DHCP servers is detected, the DHCP IP address range configured as remote will not be allowed to start delegating new leases until the MCLT + partner-down-delay intervals expire. This is to ensure that the new lease that was delegated from the local IP address-range/prefix on one node but was never synchronized due to the intercommunication link failure, will expire before the same IP address/prefix is allocated from the remote IP address-range/prefix on the other node.
However, the already existing (and synchronized) lease times can be renewed from the remote IP address range at any time, regardless of the state of the intercommunication link (operational or failed).
Lease synchronization failure can be caused either by a node failure, or a failure of the link over which the DHCP leases are synchronized (intercommunication link). Synchronization failure detection can take up to 3 seconds.
During the failure, the DHCP lease time for the new clients is restricted to MCLT while for the existing clients the lease time will over time (by consecutive DHCP renews) be gradually reduced to the MCLT.
The no form of this command reverts to the default.
Default
maximum-client-lead-time min 10
Parameters
- maximum-client-lead-time
-
Specifies the maximum client lead time.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
maximum-declined
maximum-declined
Syntax
maximum-declined maximum-declined
no maximum-declined
Context
[Tree] (config>service>vprn>dhcp>server>pool>subnet maximum-declined)
[Tree] (config>router>dhcp>server>pool>subnet maximum-declined)
Full Context
configure service vprn dhcp local-dhcp-server pool subnet maximum-declined
configure router dhcp local-dhcp-server pool subnet maximum-declined
Description
This command configures the maximum number of declined addresses allowed.
The no form of the reverts to the default.
Default
maximum-declined 64
Parameters
- maximum-declined
-
Specifies the maximum number of declined addresses allowed.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
maximum-ipv6-routes
maximum-ipv6-routes
Syntax
maximum-ipv6-routes number [log-only] [ threshold percentage]
no maximum-ipv6-routes
Context
[Tree] (config>service>vprn maximum-ipv6-routes)
Full Context
configure service vprn maximum-ipv6-routes
Description
This command specifies the maximum number of remote IPv6 routes that can be held within a VPN routing/ forwarding (VRF) context. The local, host, static and aggregate routes are not counted.
The VPRN service ID must be in a shutdown state in order to modify maximum-routes command parameters.
If the log-only parameter is not specified and the maximum-routes value is set below the existing number of routes in a VRF, then the offending RIP peer (if applicable) is brought down (but the VPRN instance remains up). BGP peering will remain up but the exceeding BGP routes will not be added to the VRF.
The maximum route threshold can dynamically change to increase the number of supported routes even when the maximum has already been reached. Protocols will resubmit their routes which were initially rejected.
The no form of this command disables any limit on the number of routes within a VRF context. The threshold will not be raised. Issue the no form of this command only when the VPRN instance is shutdown.
Default
0 or disabled
Parameters
- number
-
Specifies an integer that specifies the maximum number of routes to be held in a VRF context.
- log-only
-
Specifies that if the maximum limit is reached, only log the event. log-only does not disable the learning of new routes.
- threshold percentage
-
Specifies the percentage at which a warning log message and SNMP trap should be set. There are two warnings, the first is a mid-level warning at the threshold value set and the second is a high-level warning at level between the maximum number of routes and the mid-level rate ([mid+max] / 2).
Platforms
All
maximum-original-datagram
maximum-original-datagram
Syntax
[no] maximum-original-datagram
Context
[Tree] (config>test-oam>icmp>ipv6 maximum-original-datagram)
Full Context
configure test-oam icmp ipv6 maximum-original-datagram
Description
This command enables the original datagram field of the ICMPv6 error message to be a maximum of 1232 bytes.
The no form of this command may result in an original datagram field of the ICMPv6 error message smaller than 1232 bytes be built smaller.
Default
no maximum-original-datagram
Platforms
All
maximum-p2mp-spmsi
maximum-p2mp-spmsi
Syntax
maximum-p2mp-spmsi range
no maximum-p2mp-spmsi
Context
[Tree] (config>service>vprn>mvpn>pt>selective maximum-p2mp-spmsi)
Full Context
configure service vprn mvpn provider-tunnel selective maximum-p2mp-spmsi
Description
This command specifies the maximum number of RSVP P2MP or LDP P2MP S-PMSI tunnels for the mVPN. When the limit is reached, no more RSVP P2MP S-PMSI or LDP P2MP S-PMSI is created and traffic over the data-threshold will stay on I-PMSI.
Default
10
Parameters
- range
-
Specifies the maximum number of RSVP P2MP or LDP P2MP S-PMSI tunnel for the mVPN.
Platforms
All
maximum-p2mp-spmsi
Syntax
maximum-p2mp-spmsi range
no maximum-p2mp-spmsi
Context
[Tree] (config>router>gtm>provider-tunnel>selective maximum-p2mp-spmsi)
Full Context
configure router gtm provider-tunnel selective maximum-p2mp-spmsi
Description
This command specifies the maximum number of RSVP P2MP or LDP P2MP S-PMSI tunnels for the GTM. When the limit is reached, no more RSVP P2MP S-PMSI or LDP P2MP S-P MSI tunnels are created and traffic over the data-threshold will stay on I-PMSI.
The no form of this command reverts to the default values.
Default
maximum-p2mp-spmsi 10
Parameters
- range
-
Specifies the maximum number of RSVP P2MP or LDP P2MP S-PMSI tunnels for the GTM.
Platforms
All
maximum-paths
maximum-paths
Syntax
maximum-paths max-paths [ebgp ebgp-max-paths] [ibgp ibgp-max-paths] [restrict {same-neighbor-as | exact-as-path}] [unequal-cost]
no maximum-paths
Context
[Tree] (config>service>vprn>bgp>multi-path maximum-paths)
Full Context
configure service vprn bgp multi-path maximum-paths
Description
This command sets ECMP multi-path parameters that apply to all address families for that BGP multi-path. For some address families it is possible to override these settings on a per address family basis.
When multi-path is enabled, traffic to the destination is load-shared across a set of paths (BGP routes) that the BGP decision process considers equal to the best path. The actual distribution of traffic over the multiple paths may be equal or unequal (that is, based on weights derived from the Link Bandwidth Extended Community).
To qualify as a multi-path, a non-best route must meet the following criteria (some criteria are controlled by this command):
-
The multi-path route must be the same type of route as the best path (same AFI/SAFI and, in some cases, same next-hop resolution method).
-
The multi-path route must be tied with the best path for all criteria of greater significance than next-hop cost, except for criteria that are configured to be ignored.
-
If the best path selection reaches the next-hop cost comparison, the multi-path route must have the same next-hop cost as the best route unless the unequal-cost option is configured.
-
The multi-path route must not have the same BGP next-hop as the best path or any other multi-path route.
-
The multi-path route must not cause the ECMP limit of the routing instance to be exceeded (configured using the ecmp command with a value in the range 1 to 64).
-
The multi-path route must not cause the applicable max-paths limit to be exceeded. If the best path is an EBGP learned route and the ebgp option is used, the ebgp-max-paths limit overrides the max-paths limit. If the best path is an IBGP-learned route and the ibgp option is used, the ibgp-max-paths limit overrides the max-paths limit. All path limits are configurable up to a maximum of 64. Multi-path is effectively disabled if a value is set to 1.
-
The multi-path route must have the same neighbor AS in its AS path as the best path if the restrict same-neighbor-as option is configured. By default, any path with the same AS path length as the best path (regardless of neighbor AS) is eligible for multi-path.
-
The route must have the same AS path as the best path if the restrict exact-as-path option is configured. By default, any path with the same AS path length as the best path (regardless of the actual AS numbers) is eligible for multi-path.
The no form of this command disables BGP multi-path.
Default
no maximum-paths
Parameters
- max-paths
-
Specifies the maximum number of multipaths per prefix/NLRI if ebgp-max-paths or ibgp-max-paths does not apply.
- egp-max-paths
-
Specifies the maximum number of multipaths per prefix or NLRI when the best path is an EBGP learned route.
- ibgp-max-paths
-
Specifies the maximum number of multipaths per prefix or NLRI when the best path is an IBGP learned route.
- restrict same-neighbor-as
-
Specifies that the non-best path must have the same neighbor AS in its AS path as the best path.
- restrict exact-as-path-as
-
Specifies that the non-best path must have the same AS path as the best path.
- unequal-cost
-
Instructs BGP to ignore differences in the next-hop cost only when determining eligible multipaths.
Platforms
All
maximum-paths
Syntax
maximum-paths max-paths [ebgp ebgp-max-paths] [ibgp ibgp-max-paths] [restrict {same-neighbor-as | exact-as-path}] [unequal-cost]
no maximum-paths
Context
[Tree] (config>router>bgp>multi-path maximum-paths)
Full Context
configure router bgp multi-path maximum-paths
Description
This command sets ECMP multipath parameters that apply to all address families for that BGP multipath. For some address families it is possible to override these settings on a per address family basis.
When multipath is enabled, traffic to the destination is load-shared across a set of paths (BGP routes) that the BGP decision process considers equal to the best path. The actual distribution of traffic over the multiple paths may be equal or unequal (that is, based on weights derived from the Link Bandwidth Extended Community).
The no form of this command disables BGP multipath.
Default
no maximum-paths
Parameters
- max-paths
-
Specifies the maximum number of multipaths per prefix/NLRI if ebgp-max-paths or ibgp-max-paths does not apply.
- ebgp-max-paths
-
Specifies the maximum number of multipaths per prefix or NLRI when the best path is an EBGP learned route.
- ibgp-max-paths
-
Specifies the maximum number of multipaths per prefix or NLRI when the best path is an IBGP learned route.
- restrict same-neighbor-as
-
Specifies that the non-best path must have the same neighbor AS in its AS path as the best path.
- restrict exact-as-path
-
Specifies that the non-best path must have the same AS path as the best path.
- unequal-cost
-
Instructs BGP to ignore differences in the next-hop cost only when determining eligible multipaths.
Platforms
All
maximum-recovery-time
maximum-recovery-time
Syntax
maximum-recovery-time interval
no maximum-recovery-time
Context
[Tree] (config>router>ldp>graceful-restart maximum-recovery-time)
Full Context
configure router ldp graceful-restart maximum-recovery-time
Description
This command configures the local maximum recovery time.
The no form of this command returns the default value.
Default
no maximum-recovery-time (which equals a value of 120 seconds)
Parameters
- interval
-
Specifies the length of time in seconds.
Platforms
All
maximum-routes
maximum-routes
Syntax
maximum-routes number [log-only] [ threshold percentage]
no maximum-routes
Context
[Tree] (config>service>vprn maximum-routes)
Full Context
configure service vprn maximum-routes
Description
This command specifies the maximum number of remote routes that can be held within a VPN routing/ forwarding (VRF) context. The local, host, static and aggregate routes are not counted.
The VPRN service ID must be in a shutdown state in order to modify maximum-routes command parameters.
If the log-only parameter is not specified and the maximum-routes value is set below the existing number of routes in a VRF, then the offending RIP peer (if applicable) is brought down (but the VPRN instance remains up). BGP peering will remain up but the exceeding BGP routes will not be added to the VRF.
The maximum route threshold can dynamically change to increase the number of supported routes even when the maximum has already been reached. Protocols will resubmit their routes which were initially rejected.
The no form of this command disables any limit on the number of routes within a VRF context. Issue the no form of this command only when the VPRN instance is shutdown.
Default
0 or disabled — The threshold will not be raised.
Parameters
- number
-
An integer that specifies the maximum number of routes to be held in a VRF context.
- log-only
-
Specifies that if the maximum limit is reached, only log the event. log-only does not disable the learning of new routes.
- threshold percentage
-
The percentage at which a warning log message and SNMP trap should be set. There are two warnings, the first is a mid-level warning at the threshold value set and the second is a high-level warning at level between the maximum number of routes and the mid-level rate ([mid+max] / 2).
Platforms
All
maximum-sid-depth
maximum-sid-depth
Syntax
maximum-sid-depth
Context
[Tree] (config>router>isis>segm-rtng maximum-sid-depth)
Full Context
configure router isis segment-routing maximum-sid-depth
Description
Commands in this context configure a manual override of the Maximum Segment Depths (MSD) that is announced by the router.
Platforms
All
maximum-sid-depth
Syntax
maximum-sid-depth
Context
[Tree] (config>router>ospf>segm-rtng maximum-sid-depth)
Full Context
configure router ospf segment-routing maximum-sid-depth
Description
Commands in this context configure a manual override of the Maximum Segment Depths (MSD) that is announced by the router.
Platforms
All
mbb
mbb
Syntax
mbb [detail]
no mbb
Context
[Tree] (debug>router>mpls>event mbb)
Full Context
debug router mpls event mbb
Description
This command debugs the state of the most recent invocation of the make-before-break (MBB) functionality.
The no form of the command disables the debugging.
Parameters
- detail
-
Displays detailed information about MBB events.
Platforms
All
mbb-prefer-current-hops
mbb-prefer-current-hops
Syntax
[no] mbb-prefer-current-hops
Context
[Tree] (config>router>mpls mbb-prefer-current-hops)
Full Context
configure router mpls mbb-prefer-current-hops
Description
This command implements a new option in the CSPF path computation during a Make-Before-Break (MBB) procedure of an RSVP LSP.
When MPLS performs an MBB for the primary or secondary path of a P2P LSP, or the S2L path of a P2MP LSP, and the new mbb-prefer-current-hops option is enabled in MPLS context, CSPF will select a path, among equal-cost candidate paths, with the most overlapping links with the current path. Normally, CSPF selects the path randomly.
The procedures of the new MBB CSPF path selection apply to LSP without the least-fill option enabled. If the least-fill rule results in a different path, the LSP path will be moved though. Users can still favor stability over least-fill condition by applying a larger value to the parameter least-fill-min-thd under the MPLS context such that a path will only be moved when the difference of the least-available bandwidth becomes significant enough between the most used links in the equal cost paths. If that difference is not significant enough, CSPF will select the path with the most overlapping links instead of selecting a path randomly.
The procedures when the new mbb-prefer-current-hops option is enabled apply to all MBB types. Thus, it applies to the auto-bandwidth MBB, the configuration change MBB, the soft preemption MBB, the TE graceful shutdown MBB, the delayed retry MBB (for SRLG secondary LSP path), the path change MBB, the timer resignal MBB, and the manual resignal MBB.
During the FRR global revertive MBB, CSPF selects a random link among the ones available between the PLR node and the Merge Point node, including the failed link if it has restored in the meantime. These links cannot be checked for overlap with the current path.
The TE graceful shutdown MBB will still avoid the link or node that is in maintenance and the soft preemption MBB will still avoid the link that is overbooked.
For an inter-area LSP, this feature applies to the subset of the path from the ingress LER to the exit ABR.
The procedures of this feature are not applied to a zero bandwidth CSPP LSP, including an auto-bandwidth CSPF LSP while its operational bandwidth is zero, and to a non-CSPF LSP.
Platforms
All
mbs
mbs
Syntax
mbs percent-of-pool
no mbs
Context
[Tree] (config>mcast-mgmt>bw-plcy>t2-paths>secondary-paths>queue-parameters mbs)
[Tree] (config>mcast-mgmt>bw-plcy>t2-paths>primary-paths>queue-parameters mbs)
Full Context
configure mcast-management bandwidth-policy t2-paths secondary-paths queue-parameters mbs
configure mcast-management bandwidth-policy t2-paths primary-paths queue-parameters mbs
Description
This command configures the override for the default Maximum Buffer Size (MBS) for each individual path’s queue. The queues MBS threshold defines the point at which all packets destined for the queue are discarded based on queue depth. The defined threshold also provides context for the queues drop-tail parameter.
The mbs percent-of-pool parameter is defined as a percentage of the total pool size. The system allows the sum of all MBS values to equal more than 100% allowing for oversubscription of the pool.
For the primary-path and secondary-path queues, the mbs percent is applied to a single queue for each path.
The no form of this command is used to restore the path queues default MBS value.
Parameters
- percent-of-pool
-
Specifies the percent of buffers from the total buffer pool space for the number of buffers, expressed as a decimal integer. If 10 MB is the total buffers in the buffer pool, a value of 10 would limit the maximum queue size to 1MB (10%) of buffer space for the forwarding class queue. If the total size is increased to 20MB, the existing value of 10 would automatically increase the maximum size of the queue to 2MB.
mbs
Syntax
mbs size [bytes | kilobytes]
no mbs
Context
[Tree] (config>subscr-mgmt>sla-prof>egress>qos>queue mbs)
Full Context
configure subscriber-mgmt sla-profile egress qos queue mbs
Description
This command configures the maximum size for the queue.
The sum of the MBS for all queues on an egress access port can oversubscribe the total amount of buffering available. When congestion occurs and buffers become scarce, access to buffers is controlled by the RED slope a packet is associated with. A queue that has not exceeded its MBS size is not guaranteed that a buffer is available when needed or that the packet’s RED slope will not force the discard of the packet. Setting proper CBS parameters and controlling CBS oversubscription is one major safeguard to queue starvation (when a queue does not receive its fair share of buffers). Another is properly setting the RED slope parameters for the needs of services on this port or channel.
The no form of this command returns the MBS size to the size as configured in the QoS policy.
Parameters
- size
-
This required parameter specifies that the MBS is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional byte and kilobyte keywords are mutually exclusive and are used to explicitly to define the size. By specifying the keyword default sets the MBS to its default value.
- bytes
-
Specifies that the value given for size is interpreted as the queue's MBS value in bytes.
- kilobytes
-
Specifies that the value given for size is interpreted as the queue's MBS value in kilobytes.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
mbs
Syntax
mbs size [bytes | kilobytes]
no mbs
Context
[Tree] (config>subscr-mgmt>sla-prof>ingress>qos>queue mbs)
Full Context
configure subscriber-mgmt sla-profile ingress qos queue mbs
Description
The Maximum Burst Size (MBS) command configures the explicit definition of the maximum number of buffers allowed for a specific queue.
The MBS value is used by a queue to determine whether it has exhausted all of its buffers while enqueuing packets. Once the queue has exceeded the number of buffers allowed by MBS, all packets are discarded until packets have been drained from the queue.
The sap-ingress context for mbs provides a mechanism for overriding the default maximum size for the queue.
The sum of the MBS for all queues on an ingress access port can oversubscribe the total amount of buffering available. When congestion occurs and buffers become scarce, access to buffers is controlled by the RED slope a packet is associated with. A queue that has not exceeded its MBS size is not guaranteed that a buffer is available when needed or that the packet’s RED slope does not force the discard of the packet. Setting proper CBS parameters and controlling CBS oversubscription is one major safeguard to queue starvation (when a queue does not receive its fair share of buffers). Another is properly setting the RED slope parameters for the needs of services on this port or channel.
The no form of this command returns the MBS size to the size as configured in the QoS policy.
Parameters
- size
-
This required parameter specifies that the MBS is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional byte and kilobyte keywords are mutually exclusive and are used to explicitly to define the size. By specifying the keyword default sets the MBS to its default value.
- bytes
-
Specifies that the value given for size is interpreted as the queue's MBS value is in bytes.
- kilobytes
-
Specifies that the value given for size is interpreted as the queue's MBS value is in kilobytes.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
mbs
Syntax
mbs size [bytes | kilobytes]
no mbs
Context
[Tree] (config>subscr-mgmt>sla-prof>ingress>qos>policer mbs)
[Tree] (config>subscr-mgmt>sla-prof>egress>qos>policer mbs)
Full Context
configure subscriber-mgmt sla-profile ingress qos policer mbs
configure subscriber-mgmt sla-profile egress qos policer mbs
Description
This command configures the MBS for the QoS policer.
The no form of this command returns the MBS to its default value. By default, the MBS is 16 Mbytes when PIR equals max or is greater than or equal to the FP capacity (this overrides an explicit configured MBS value); otherwise, 10 ms volume of traffic for a configured non-zero/non-max PIR capped to 3968 kbytes, with a minimum of 256 bytes.
Parameters
- size
-
This required parameter specifies that the MBS is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional byte and kilobyte keywords are mutually exclusive and are used to explicitly to define the size. By specifying the keyword default sets the MBS to its default value.
- bytes
-
Specifies that the value given for size is interpreted as the queue's MBS value in bytes.
- kilobytes
-
Specifies that the value given for size is interpreted as the queue's MBS value in kilobytes.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
mbs
Syntax
mbs size [bytes | kilobytes]
no mbs
Context
[Tree] (config>service>vprn>sap>egress>queue-override>queue mbs)
[Tree] (config>service>ies>if>sap>ingress>queue-override>queue mbs)
[Tree] (config>service>vprn>sap>ingress>queue-override>queue mbs)
[Tree] (config>service>ies>if>sap>egress>queue-override>queue mbs)
Full Context
configure service vprn sap egress queue-override queue mbs
configure service ies interface sap ingress queue-override queue mbs
configure service vprn sap ingress queue-override queue mbs
configure service ies interface sap egress queue-override queue mbs
Description
This command overrides specific attributes of the specified queue’s MBS parameters. The MBS is a mechanism to override the default maximum size for the queue.
The sum of the MBS for all queues on an egress access port can oversubscribe the total amount of buffering available. When congestion occurs and buffers become scarce, access to buffers is controlled by the RED slope a packet is associated with. A queue that has not exceeded its MBS size is not guaranteed that a buffer is available when needed or that the packets RED slope is not forced the discard of the packet. Setting proper CBS parameters and controlling CBS oversubscription is one major safeguard to queue starvation (when a queue does not receive its fair share of buffers). Another is properly setting the RED slope parameters for the needs of services on this port or channel.
If the CBS value is larger than the MBS value, an error will occur, preventing the MBS change.
The no form of this command returns the MBS size assigned to the queue.
Default
mbs default
Parameters
- size
-
This required parameter specifies that the MBS is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional byte and kilobyte keywords are mutually exclusive and are used to explicitly to define the size. By specifying the keyword default sets the MBS to its default value.
- bytes
-
Specifies that the value given for size is interpreted as the queue's MBS value in bytes.
- kilobytes
-
Specifies that the value given for size is interpreted as the queue's MBS value in kb/s.
Platforms
All
mbs
Syntax
mbs size [bytes | kilobytes]
no mbs
Context
[Tree] (config>service>vpls>sap>egress>queue-override>queue mbs)
[Tree] (config>service>vpls>sap>ingress>queue-override>queue mbs)
Full Context
configure service vpls sap egress queue-override queue mbs
configure service vpls sap ingress queue-override queue mbs
Description
This command overrides specific attributes of the specified queue’s MBS parameters. The MBS value is used by a queue to determine whether it has exhausted all of its buffers while enqueuing packets. Once the queue has exceeded the amount of buffers allowed by MBS, all packets are discarded until packets have been drained from the queue.
The sum of the MBS for all queues on an ingress access port can oversubscribe the total amount of buffering available. When congestion occurs and buffers become scarce, access to buffers is controlled by the RED slope a packet is associated with. A queue that has not exceeded its MBS is not guaranteed that a buffer will be available when needed or that the packets RED slope will not force the discard of the packet. Setting correct CBS parameters and controlling CBS over-subscription is one major safeguard to queue starvation (when a queue does not receive its fair share of buffers). Another is properly setting the RED slope parameters for the needs of services on this port or channel.
The no form of this command returns the MBS assigned to the queue to the default value.
Default
mbs default
Parameters
- size
-
The size parameter is required when specifying mbs and is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional bytes and kilobytes keywords are mutually exclusive and are used to explicitly define whether the size represents bytes or kilobytes.
- bytes
-
When byte is defined, the value given for size is interpreted as the queue's MBS value given in bytes.
- kilobytes
-
When kilobytes is defined, the value is interpreted as the queue's MBS value given in kilobytes.
Platforms
All
mbs
Syntax
mbs burst-size
no mbs
Context
[Tree] (config>subscr-mgmt>isa-policer mbs)
Full Context
configure subscriber-mgmt isa-policer mbs
Description
This command specifies the maximum burst-size value of this policer.
The no form of this command reverts to its default.
Default
mbs 0
Parameters
- burst-size
-
The maximum burst-size in kbytes.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
mbs
Syntax
mbs {size [bytes | kilobyte] | default}
no mbs
Context
[Tree] (config>card>fp>ingress>network>qgrp>policer-over>plcr mbs)
[Tree] (config>card>fp>ingress>access>qgrp>policer-over>plcr mbs)
Full Context
configure card fp ingress network queue-group policer-override policer mbs
configure card fp ingress access queue-group policer-override policer mbs
Description
This command configures the policer’s PIR leaky bucket’s violate threshold. The high-prio-only command is applied to the MBS value to derive the bucket’s low priority violate threshold. For ingress, trusted in-profile packets and untrusted high priority packets use the policer’s high priority violate threshold while trusted out-of-profile and untrusted low priority packets use the policer’s low priority violate threshold.
The PIR bucket’s violate threshold represent the maximum burst tolerance allowed by the policer. If the policer’s offered rate is equal to or less than the policer’s defined rate, the PIR bucket depth hovers around the 0 depth with spikes up to the maximum packet size in the offered load. If the offered rate increases beyond the metering rate, the amount of data allowed above the rate is capped by the threshold. The low priority violate threshold provides a smaller burst size for the lower priority traffic associated with the policer. Since all lower priority traffic is discarded at the lower burst tolerance size, the remaining burst tolerance defined by high-prio-only is available for the higher priority traffic.
The policer’s mbs size defined in the QoS policy may be overridden on an sla-profile or SAP where the policy is applied.
The no form of this command reverts the policer to its default MBS size. By default, the MBS is 16 Mbytes when PIR equals max or is greater than or equal to the FP capacity (this overrides an explicit configured MBS value); otherwise, 10 ms volume of traffic for a configured non-zero/non-max PIR capped to 3968 kbytes, with a minimum of 256 bytes.
Parameters
- size
-
The size parameter is required when specifying mbs and is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional bytes and kilobytes keywords are mutually exclusive and are used to explicitly define whether size represents bytes or kilobytes.
- bytes
-
When bytes is defined, the value given for size is interpreted as the policer’s MBS value given in bytes.
- kilobytes
-
When kilobytes is defined, the value is interpreted as the policer’s MBS value given in kilobytes.
- default
-
Keyword that reverts the MBS to its default value.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
mbs
Syntax
mbs {size [bytes | kilobytes] | default}
no mbs
Context
[Tree] (config>port>ethernet>access>ing>qgrp>qover>q mbs)
[Tree] (config>port>ethernet>network>egr>qgrp>qover>q mbs)
[Tree] (config>port>ethernet>access>egr>qgrp>qover>q mbs)
Full Context
configure port ethernet access ingress queue-group queue-overrides queue mbs
configure port ethernet network egress queue-group queue-overrides queue mbs
configure port ethernet access egress queue-group queue-overrides queue mbs
Description
The Maximum Burst Size (MBS) command specifies the default maximum buffer size for the template queue. The value is given in kilobytes.
The MBS value is used by a queue to determine whether it has exhausted all of its buffers while enqueuing packets. Once the queue has exceeded the amount of buffers allowed by MBS, all packets are discarded until packets have been drained from the queue.
The queue-group or network egress QoS context for mbs provides a mechanism for overriding the default maximum size for the queue.
The sum of the MBS for all queues on an ingress access port can oversubscribe the total amount of buffering available. When congestion occurs and buffers become scarce, access to buffers is controlled by the RED slope a packet is associated with. A queue that has not exceeded its MBS size is not guaranteed that a buffer will be available when needed or that the packets RED slope will not force the discard of the packet. Setting proper CBS parameters and controlling CBS oversubscription is one major safeguard to queue starvation (when a queue does not receive its fair share of buffers). Another is properly setting the RED slope parameters for the needs of services on this port or channel.
This command applies to egress queue group queues as the queue-delay is only supported on egress queues. This command the queue-delay command are mutually exclusive.
The no form of this command returns the MBS size assigned to the queue to the value.
Default
mbs default
Parameters
- size
-
The size parameter is required when specifying mbs and is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional byte and kilobyte keywords are mutually exclusive and are used to explicitly define whether size represents bytes or kilobytes.
- bytes
-
When byte is defined, the value given for size is interpreted as the queue’s MBS value given in bytes.
- kilobytes
-
When kilobytes is defined, the value is interpreted as the queue’s MBS value given in kilobytes.
- default
-
Keyword that reverts the MBS to its default value.
Platforms
All
mbs
Syntax
mbs size [bytes | kilobytes]
no mbs
Context
[Tree] (config>service>apipe>sap>ingress>policer-over>plcr mbs)
[Tree] (config>service>epipe>sap>ingress>policer-over>plcr mbs)
[Tree] (config>service>apipe>sap>egress>policer-over>plcr mbs)
[Tree] (config>service>ipipe>sap>ingress>policer-over>plcr mbs)
[Tree] (config>service>cpipe>sap>ingress>policer-over>plcr mbs)
[Tree] (config>service>ipipe>sap>egress>policer-over>plcr mbs)
[Tree] (config>service>epipe>sap>egress>policer-over>plcr mbs)
[Tree] (config>service>cpipe>sap>egress>policer-over>plcr mbs)
Full Context
configure service apipe sap ingress policer-override policer mbs
configure service epipe sap ingress policer-override policer mbs
configure service apipe sap egress policer-override policer mbs
configure service ipipe sap ingress policer-override policer mbs
configure service cpipe sap ingress policer-override policer mbs
configure service ipipe sap egress policer-override policer mbs
configure service epipe sap egress policer-override policer mbs
configure service cpipe sap egress policer-override policer mbs
Description
This command, within the SAP ingress and egress policer-overrides contexts, is used to override the sap-ingress and sap-egress QoS policy configured mbs parameter for the specified policer-id.
The no form of this command is used to restore the MBS to the default value. By default, the MBS is 16 Mbytes when PIR equals max or is greater than or equal to the FP capacity (this overrides an explicit configured MBS value); otherwise, 10 ms volume of traffic for a configured non-zero/non-max PIR capped to 3968 kbytes, with a minimum of 256 bytes.
Default
no mbs
Parameters
- size
-
The size parameter is required when specifying mbs override and is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional byte and kilobyte keywords are mutually exclusive and are used to explicitly define whether size represents bytes or kilobytes.
- bytes
-
When bytes is defined, the value given for size is interpreted as the policer MBS value in bytes.
- kilobytes
-
When kilobytes is defined, the value given for size is interpreted as the policer MBS value in kilobytes.
Platforms
7450 ESS, 7750 SR-7/12/12e, 7750 SR-e, 7950 XRS
- configure service apipe sap egress policer-override policer mbs
- configure service apipe sap ingress policer-override policer mbs
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
- configure service ipipe sap egress policer-override policer mbs
- configure service ipipe sap ingress policer-override policer mbs
- configure service epipe sap egress policer-override policer mbs
- configure service epipe sap ingress policer-override policer mbs
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS
- configure service cpipe sap ingress policer-override policer mbs
- configure service cpipe sap egress policer-override policer mbs
mbs
Syntax
mbs {size [bytes | kilobytes] | default}
no mbs
Context
[Tree] (config>service>apipe>sap>ingress>queue-override>queue mbs)
[Tree] (config>service>epipe>sap>ingress>queue-override>queue mbs)
[Tree] (config>service>cpipe>sap>ingress>queue-override>queue mbs)
[Tree] (config>service>epipe>sap>egress>queue-override>queue mbs)
[Tree] (config>service>ipipe>sap>egress>queue-override>queue mbs)
[Tree] (config>service>ipipe>sap>ingress>queue-override>queue mbs)
[Tree] (config>service>fpipe>sap>ingress>queue-override>queue mbs)
[Tree] (config>service>cpipe>sap>egress>queue-override>queue mbs)
[Tree] (config>service>fpipe>sap>egress>queue-override>queue mbs)
[Tree] (config>service>apipe>sap>egress>queue-override>queue mbs)
Full Context
configure service apipe sap ingress queue-override queue mbs
configure service epipe sap ingress queue-override queue mbs
configure service cpipe sap ingress queue-override queue mbs
configure service epipe sap egress queue-override queue mbs
configure service ipipe sap egress queue-override queue mbs
configure service ipipe sap ingress queue-override queue mbs
configure service fpipe sap ingress queue-override queue mbs
configure service cpipe sap egress queue-override queue mbs
configure service fpipe sap egress queue-override queue mbs
configure service apipe sap egress queue-override queue mbs
Description
This command overrides specific attributes of the specified queue’s MBS parameters. A queue uses its MBS value to determine whether it has exhausted all of its buffers while enqueuing packets. Once the queue has exceeded the number of buffers allowed by the MBS, all packets are discarded until packets have been drained from the queue.
The sum of the MBS for all queues on an ingress access port can oversubscribe the total amount of buffering available. When congestion occurs and buffers become scarce, access to buffers is controlled by the RED slope associated with a packet. A queue that has not exceeded its MBS is not guaranteed to have buffer available when needed or that the packet’s RED slope will not force the discard of the packet. Setting correct CBS parameters and controlling CBS oversubscription is one major safeguard to queue starvation (when a queue does not receive its fair share of buffers). Another is properly setting the RED slope parameters for the needs of services on this port or channel.
The no form of this command returns the MBS assigned to the queue to the default value.
Default
mbs default
Parameters
- size
-
The size parameter is an integer expression of the maximum number of kilobytes or bytes of buffering allowed for the queue. A value of 0 causes the queue to discard all packets.
- bytes
-
Indicates that the size parameter value is expressed in bytes.
- kilobytes
-
Indicates that the size parameter is expressed in kilobytes.
Platforms
7450 ESS, 7750 SR-7/12/12e, 7750 SR-a, 7750 SR-e, 7950 XRS
- configure service apipe sap egress queue-override queue mbs
- configure service apipe sap ingress queue-override queue mbs
All
- configure service epipe sap egress queue-override queue mbs
- configure service ipipe sap egress queue-override queue mbs
- configure service epipe sap ingress queue-override queue mbs
- configure service ipipe sap ingress queue-override queue mbs
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
- configure service cpipe sap egress queue-override queue mbs
- configure service fpipe sap egress queue-override queue mbs
- configure service fpipe sap ingress queue-override queue mbs
- configure service cpipe sap ingress queue-override queue mbs
mbs
Syntax
mbs size [{bytes | kilobytes}]
no mbs
Context
[Tree] (config>service>vpls>sap>ingress>policer-override>plcr mbs)
[Tree] (config>service>vpls>sap>egress>policer-override>plcr mbs)
Full Context
configure service vpls sap ingress policer-override policer mbs
configure service vpls sap egress policer-override policer mbs
Description
This command, within the SAP ingress and egress policer-overrides contexts, is used to override the sap-ingress and sap-egress QoS policy configured mbs parameter for the specified policer-id.
The no form of this command restores the MBS to the default value. By default, the MBS is 16 Mbytes when PIR equals max or is greater than or equal to the FP capacity (this overrides an explicit configured MBS value); otherwise, 10 ms volume of traffic for a configured non-zero/non-max PIR capped to 3968 kbytes, with a minimum of 256 bytes.
Default
no mbs
Parameters
- size
-
This parameter is required when specifying MBS override and is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional byte and kilobyte keywords are mutually exclusive and are used to explicitly define whether size represents bytes or kilobytes.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
mbs
Syntax
mbs size [{bytes | kilobytes}]
no mbs
Context
[Tree] (config>service>ies>if>sap>egress>policer-override>plcr mbs)
[Tree] (config>service>ies>if>sap>ingress>policer-override>plcr mbs)
Full Context
configure service ies interface sap egress policer-override policer mbs
configure service ies interface sap ingress policer-override policer mbs
Description
This command, within the SAP ingress and egress policer-overrides contexts, is used to override the sap-ingress and sap-egress QoS policy configured mbs parameter for the specified policer-id.
The no form of this command restores the MBS setting to the default value. By default, the MBS is 16 Mbytes when PIR equals max or is greater than or equal to the FP capacity (this overrides an explicit configured MBS value); otherwise, 10 ms volume of traffic for a configured non-zero/non-max PIR capped to 3968 kbytes, with a minimum of 256 bytes.
Default
no mbs
Parameters
- size
-
This parameter is required when specifying MBS override and is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional byte and kilobyte keywords are mutually exclusive and are used to explicitly define whether size represents bytes or kilobytes.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
mbs
Syntax
mbs size [{bytes | kilobytes}]
no mbs
Context
[Tree] (config>service>vprn>if>sap>egress>policer-override>plcr mbs)
[Tree] (config>service>vprn>if>sap>ingress>policer-override>plcr mbs)
Full Context
configure service vprn interface sap egress policer-override policer mbs
configure service vprn interface sap ingress policer-override policer mbs
Description
This command, within the SAP ingress and egress policer-overrides contexts, is used to override the sap-ingress and sap-egress QoS policy configured mbs parameter for the specified policer-id.
The no form of this command restores the MBS to the default value. By default, the MBS is 16 Mbytes when PIR equals max or is greater than or equal to the FP capacity (this overrides an explicit configured MBS value); otherwise, 10 ms volume of traffic for a configured non-zero/non-max PIR capped to 3968 kbytes, with a minimum of 256 bytes.
Default
no mbs
Parameters
- size
-
This parameter is required when specifying MBS override and is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional byte and kilobyte keywords are mutually exclusive and are used to explicitly define whether size represents bytes or kilobytes.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
mbs
Syntax
mbs {size [bytes | kilobytes] | default}
no mbs
Context
[Tree] (config>service>vprn>if>sap>ingress>queue-override>queue mbs)
[Tree] (config>service>vprn>if>sap>egress>queue-override>queue mbs)
Full Context
configure service vprn interface sap ingress queue-override queue mbs
configure service vprn interface sap egress queue-override queue mbs
Description
This command can be used to override specific attributes of the specified queue’s MBS parameters. The MBS value is used by a queue to determine whether it has exhausted all of its buffers while enqueuing packets. Once the queue has exceeded the amount of buffers allowed by MBS, all packets are discarded until packets have been drained from the queue.
The sum of the MBS for all queues on an ingress access port can oversubscribe the total amount of buffering available. When congestion occurs and buffers become scarce, access to buffers is controlled by the RED slope a packet is associated with. A queue that has not exceeded its MBS size is not guaranteed that a buffer will be available when needed or that the packet’s RED slope will not force the discard of the packet. Setting proper CBS parameters and controlling CBS oversubscription is one major safeguard to queue starvation (when a queue does not receive its fair share of buffers). Another is properly setting the RED slope parameters for the needs of services on this port or channel.
If the CBS value is larger than the MBS value, an error will occur, preventing the MBS change.
The no form of this command returns the MBS size assigned to the queue to the value.
Default
mbs default
Parameters
- size
-
The size parameter is required when specifying mbs and is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional bytes and kilobytes keywords are mutually exclusive and are used to explicitly define whether the size represents bytes or kilobytes.
- bytes
-
When byte is defined, the value given for size is interpreted as the queue'sMBS value given in bytes.
- kilobytes
-
When kilobytes is defined, the value is interpreted as the queue's MBSvalue given in kilobytes.
- default
-
Keyword that reverts the MBS to its default value.
Platforms
All
mbs
Syntax
mbs congested-mbs
no mbs
Context
[Tree] (config>app-assure>group>policer>congestion-override mbs)
Full Context
configure application-assurance group policer congestion-override mbs
Description
This command configures the maximum burst size for the policer. It is recommended that MBS is configured larger than twice the MTU for the traffic handled by the policer to allow for some burstiness of the traffic. MBS is configurable for single-bucket, dual-bucket bandwidth and flow setup rate policers only.
The no form of this command removes the congested MBS value from the configuration.
Default
mbs 0
Parameters
- congested-mbs
-
Specifies the maximum burst size, in kbytes, when the access-network-level, which the subscriber belongs to, is in a congested state.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
mbs
Syntax
mbs maximum-burst-size
no mbs
Context
[Tree] (config>app-assure>group>tod-override mbs)
Full Context
configure application-assurance group tod-override mbs
Description
This command provides a mechanism to configure the maximum burst size for the policer. It is recommended that MBS is configured larger than twice the MTU for the traffic handled by the policer to allow for some burstiness of the traffic. MBS is configurable for single-bucket, dual-bucket bandwidth and flow setup rate policers only.
The no form of this command resets the MBS value to its default.
Default
mbs 0
Parameters
- maximum-burst-size
-
Specifies an integer value defining either size, in kbytes, for the MBS of the bandwidth policer, or flow count for the MBS of the flow setup rate policers.
mbs
Syntax
mbs {size [bytes | kilobytes] | default}
no mbs
Context
[Tree] (config>qos>sap-ingress>dyn-policer mbs)
[Tree] (config>qos>sap-ingress>policer mbs)
[Tree] (config>qos>sap-egress>dyn-policer mbs)
[Tree] (config>qos>sap-egress>policer mbs)
Full Context
configure qos sap-ingress dynamic-policer mbs
configure qos sap-ingress policer mbs
configure qos sap-egress dynamic-policer mbs
configure qos sap-egress policer mbs
Description
This command is used to configure the policer’s PIR leaky bucket’s high-priority violate threshold. The high-prio-only command is applied to the MBS value to derive the bucket’s low-priority violate threshold. For ingress, trusted in-profile packets and untrusted high-priority packets use the policer’s high-priority violate threshold while trusted out-of-profile and untrusted low-priority packets use the policer's low-priority violate threshold. At egress, inplus-profile, and in-profile packets use the policer’s high-priority violate threshold and out-of-profile packets use the policer's low-priority violate threshold. Exceed-profile packets are discarded unless enable-exceed-pir is configured, in which case they are forwarded.
The PIR bucket’s violate threshold represents the maximum burst tolerance allowed by the policer. If the policer's offered rate is equal to or less than the policer's defined rate, the PIR bucket depth hovers around the 0 depth with spikes up to the maximum packet size in the offered load. If the offered rate increases beyond the metering rate, the amount of data allowed above the rate is capped by the threshold. The low-priority violate threshold provides a smaller burst size for the lower priority traffic associated with the policer. Since all lower priority traffic is discarded at the lower burst tolerance size, the remaining burst tolerance defined by high-prio-only is available for the higher priority traffic.
The policer’s MBS size defined in the QoS policy may be overridden on an SLA profile or SAP where the policy is applied.
The no form of this command returns the queue to its default MBS size. By default, the MBS is 16 Mbytes when PIR equals max or is greater than or equal to the FP capacity (this overrides an explicit configured MBS value); otherwise, 10 ms volume of traffic for a configured non-zero/non-max PIR capped to 3968 kbytes, with a minimum of 256 bytes.
Parameters
- size [bytes | kilobytes]
-
The size parameter is required when specifying mbs and is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional bytes and kilobytes keywords are mutually exclusive and are used to explicitly define whether size represents bytes or kilobytes.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
- configure qos sap-egress dynamic-policer mbs
- configure qos sap-ingress dynamic-policer mbs
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
- configure qos sap-ingress policer mbs
- configure qos sap-egress policer mbs
mbs
Syntax
mbs {size [bytes | kilobytes] | default}
no mbs
Context
[Tree] (config>qos>sap-egress>queue mbs)
[Tree] (config>qos>sap-ingress>queue mbs)
Full Context
configure qos sap-egress queue mbs
configure qos sap-ingress queue mbs
Description
This command configures the maximum number of buffers allowed for a specific queue. The value is given in bytes or kilobytes and overrides the default value for the context.
The no form of this command returns the policer to its default MBS.
Default
no mbs
Parameters
- size
-
The size parameter is required when specifying mbs and is expressed as an integer representing the required size in either bytes or kilobytes.
- default
-
Sets the MBS to its default value.
- bytes
-
Specifies that the value given for size is interpreted as the queue’s MBS value given in bytes.
- kilobytes
-
Specifies the value is interpreted as the queue’s MBS value given in kilobytes.
Platforms
All
mbs
Syntax
mbs percent
no mbs
Context
[Tree] (config>qos>network-queue>queue mbs)
Full Context
configure qos network-queue queue mbs
Description
This command specifies the relative amount of buffer pool space for the maximum buffers for a specific ingress network FP forwarding class queue or egress network port forwarding class queue. The value is entered as a percentage.
The MBS value is used by a queue to determine whether it has exhausted its total allowed buffers while enqueuing packets. When the queue has exceeded its maximum amount of buffers, all packets are discarded until the queue transmits a packet. A queue that has not exceeded its MBS is not guaranteed to have a buffer available when needed or that the packet’s RED slope will not force the discard of the packet. In order to safeguard against queue starvation (when a queue does not receive its fair share of buffers), set proper CBS parameters and control CBS oversubscription. Another safeguard is to properly set the RED slope parameters for the needs of the network queues.
The MBS can sometimes be smaller than the CBS. This will result in a portion of the CBS for the queue to be unused and should be avoided.
The no form of this command returns the MBS for the queue to the default for the forwarding class.
Parameters
- percent
-
The percent of buffers from the total buffer pool space for the maximum number of buffers, expressed as a decimal integer. If 10 Mbytes is the total buffer space in the buffer pool, a value of 10 would limit the maximum queue size to 1 Mbyte (10%) of buffer space for the forwarding class queue. If the total size is increased to 20 Mbytes, the existing value of 10 would automatically increase the maximum size of the queue to 2 Mbytes.
Platforms
All
mbs
Syntax
mbs {size [bytes | kilobytes] | default}
no mbs
Context
[Tree] (config>qos>qgrps>ing>qgrp>policer mbs)
[Tree] (config>qos>qgrps>egr>qgrp>policer mbs)
Full Context
configure qos queue-group-templates ingress queue-group policer mbs
configure qos queue-group-templates egress queue-group policer mbs
Description
This command specifies the default maximum buffer size for the template queue in bytes or kilobytes.
The MBS value is used by a queue to determine whether it has exhausted all of its buffers while enqueuing packets. When the queue has exceeded the amount of buffers allowed by MBS, all packets are discarded until packets have been drained from the queue.
The port>ethernet>access>ingress>queue-group and port>ethernet>access>egress>queue-group contexts for mbs provides a mechanism for overriding the default maximum size for the queue.
The sum of the MBS for all queues on an ingress access port can oversubscribe the total amount of buffering available. When congestion occurs and buffers become scarce, access to buffers is controlled by the RED slope that a packet is associated with. A queue that has not exceeded its MBS size is not guaranteed that a buffer will be available when needed or that the packet’s RED slope will not force the discard of the packet. Setting proper CBS parameters and controlling CBS oversubscription is one major safeguard against queue starvation (when a queue does not receive its fair share of buffers). Another is properly setting the RED slope parameters for the needs of services on this port or channel.
When configured on an egress queue group queue, this command and the queue-delay command are mutually exclusive. In order to change between the mbs and queue-delay parameters, the current parameter must be removed before adding the new parameter; that is, changing from mbs to queue-delay requires a no mbs before the queue-delay is configured and changing from queue-delay to mbs requires a no queue-delay before the mbs is configured. If queue-delay is configured for an egress queue group queue, it is not possible to override the MBS for that queue.
For policers, this command is used to configure the policer’s PIR leaky bucket’s high-priority violate threshold. The high-prio-only command is applied to the MBS value to derive the bucket’s low-priority violate threshold.
At ingress, trusted in-profile packets and untrusted high-priority packets use the policer’s high-priority violate threshold while trusted out-of-profile and untrusted low-priority packets use the policer's low-priority violate threshold.
At egress, inplus-profile and in-profile packets use the policer’s high-priority violate threshold and out-of-profile packets use the policer's low-priority violate threshold. Exceed-profile packets are discarded unless enable-exceed-pir is configured, in which case they are forwarded.
The PIR bucket’s violate threshold represents the maximum burst tolerance allowed by the policer. If the policer's offered rate is equal to or less than the policer's defined rate, the PIR bucket depth hovers around the 0 depth with spikes up to the maximum packet size in the offered load. If the offered rate increases beyond the metering rate, the amount of data allowed above the rate is capped by the threshold. The low-priority violate threshold provides a smaller burst size for the lower priority traffic associated with the policer. Since all lower priority traffic is discarded at the lower burst tolerance size, the remaining burst tolerance defined by high-prio-only is available for the higher priority traffic.
The policer’s mbs size defined in the QoS policy may be overridden on an SLA profile or SAP where the policy is applied.
The no form of this command returns the MBS size to its default value. By default, the MBS is 16 Mbytes when PIR equals max or is greater than or equal to the FP capacity (this overrides an explicit configured MBS value); otherwise, 10 ms volume of traffic for a configured non-zero/non-max PIR capped to 3968 kbytes, with a minimum of 256 bytes.
Default
default
Parameters
- size
-
For queues, the size parameter is an integer expression of the maximum number of bytes or kilobytes of buffering allowed for the queue. For a value of 100 kbytes, enter the value 100. A value of 0 causes the queue to discard all packets. For policers, the size parameter is an integer expression of the maximum number of bytes for the policer's MBS. The queue MBS maximum value used is constrained by the pool size in which the queue exists and by the shared pool space in the corresponding megapool.
- [bytes | kilobytes]
-
Specifies bytes or kilobytes.
- default
-
Sets the MBS to its default value.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
mbs
Syntax
mbs {size [bytes | kilobytes] | default}
no mbs
Context
[Tree] (config>qos>qgrps>ing>qgrp>queue mbs)
[Tree] (config>qos>qgrps>egr>qgrp>queue mbs)
Full Context
configure qos queue-group-templates ingress queue-group queue mbs
configure qos queue-group-templates egress queue-group queue mbs
Description
This command specifies the default maximum buffer size for the template queue in bytes or kilobytes.
The MBS value is used by a queue to determine whether it has exhausted all of its buffers while enqueuing packets. When the queue has exceeded the amount of buffers allowed by MBS, all packets are discarded until packets have been drained from the queue.
The port>ethernet>access>ingress>queue-group and port>ethernet>access>egress>queue-group contexts for mbs provides a mechanism for overriding the default maximum size for the queue.
The sum of the MBS for all queues on an ingress access port can oversubscribe the total amount of buffering available. When congestion occurs and buffers become scarce, access to buffers is controlled by the RED slope that a packet is associated with. A queue that has not exceeded its MBS size is not guaranteed that a buffer will be available when needed or that the packet’s RED slope will not force the discard of the packet. Setting proper CBS parameters and controlling CBS oversubscription is one major safeguard against queue starvation (when a queue does not receive its fair share of buffers). Another is properly setting the RED slope parameters for the needs of services on this port or channel.
When configured on an egress queue group queue, this command and the queue-delay command are mutually exclusive. In order to change between the mbs and queue-delay parameters, the current parameter must be removed before adding the new parameter; that is, changing from mbs to queue-delay requires a no mbs before the queue-delay is configured and changing from queue-delay to mbs requires a no queue-delay before the mbs is configured. If queue-delay is configured for an egress queue group queue, it is not possible to override the MBS for that queue.
For policers, this command is used to configure the policer’s PIR leaky bucket’s high-priority violate threshold. The high-prio-only command is applied to the MBS value to derive the bucket’s low-priority violate threshold.
At ingress, trusted in-profile packets and untrusted high-priority packets use the policer’s high-priority violate threshold while trusted out-of-profile and untrusted low-priority packets use the policer's low-priority violate threshold.
At egress, inplus-profile and in-profile packets use the policer’s high-priority violate threshold and out-of-profile packets use the policer's low-priority violate threshold. Exceed-profile packets are discarded unless enable-exceed-pir is configured, in which case they are forwarded.
The PIR bucket’s violate threshold represents the maximum burst tolerance allowed by the policer. If the policer's offered rate is equal to or less than the policer's defined rate, the PIR bucket depth hovers around the 0 depth with spikes up to the maximum packet size in the offered load. If the offered rate increases beyond the metering rate, the amount of data allowed above the rate is capped by the threshold. The low-priority violate threshold provides a smaller burst size for the lower priority traffic associated with the policer. Since all lower priority traffic is discarded at the lower burst tolerance size, the remaining burst tolerance defined by high-prio-only is available for the higher priority traffic.
The policer’s mbs size defined in the QoS policy may be overridden on an SLA profile or SAP where the policy is applied.
The no form of this command returns the MBS size assigned by the queue.
Default
default
Parameters
- size
-
For queues, the size parameter is an integer expression of the maximum number of bytes or kilobytes of buffering allowed for the queue. For a value of 100 kbytes, enter the value 100. A value of 0 causes the queue to discard all packets. For policers, the size parameter is an integer expression of the maximum number of bytes for the policer's MBS. The queue MBS maximum value used is constrained by the pool size in which the queue exists and by the shared pool space in the corresponding megapool.
- [bytes | kilobytes]
-
Specifies bytes or kilobytes.
- default
-
Sets the MBS to its default value.
Platforms
All
mbs
Syntax
mbs percent
no mbs
Context
[Tree] (config>qos>shared-queue>queue mbs)
Full Context
configure qos shared-queue queue mbs
Description
This command specifies the relative amount of the buffer pool space for the maximum buffers for a specific ingress shared queue.
The MBS value is used by a queue to determine whether it has exhausted its total allowed buffers while enqueuing packets. When the queue has exceeded its maximum amount of buffers, all packets are discarded until the queue transmits a packet. A queue that has not exceeded its MBS size is not guaranteed that a buffer will be available when needed. Setting proper CBS parameters and controlling CBS oversubscription is one major safeguard against queue starvation (when a queue does not receive its fair share of buffers).
The MBS size can sometimes be smaller than the CBS. This will result in a portion of the CBS for the queue to be unused and should be avoided.
Default
The queue MBS defaults are listed in Queue MBS Default Values.
|
Queue |
Default MBS |
|---|---|
|
1 |
50 |
|
2 |
50 |
|
3 |
50 |
|
4 |
25 |
|
5 |
50 |
|
6 |
50 |
|
7 |
25 |
|
8 |
25 |
|
9 |
50 |
|
10 |
50 |
|
11 |
50 |
|
12 |
25 |
|
13 |
50 |
|
14 |
50 |
|
15 |
25 |
|
16 |
25 |
Parameters
- percent
-
The percent of buffers from the total buffer pool space for the maximum amount of buffers, expressed as a decimal integer.
Platforms
All
mbs
Syntax
mbs mbs
no mbs
Context
[Tree] (config>system>security>cpm-queue>queue mbs)
Full Context
configure system security cpm-queue queue mbs
Description
This command specifies the maximum queue depth to which a queue can grow.
Parameters
- mbs
-
Specifies the maximum burst size in kbytes.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
mbs-contribution
mbs-contribution
Syntax
mbs-contribution size [bytes | kilobytes] [fixed]
no mbs-contribution
Context
[Tree] (config>subscr-mgmt>sub-prof>egr>plcr-ctrl-plcy>mbs-thrshlds>prio mbs-contribution)
[Tree] (config>subscr-mgmt>sub-prof>ing>plcr-ctrl-plcy>mbs-thrshlds>prio mbs-contribution)
Full Context
configure subscriber-mgmt sub-profile egress policer-control-policy priority-mbs-thresholds priority mbs-contribution
configure subscriber-mgmt sub-profile ingress policer-control-policy priority-mbs-thresholds priority mbs-contribution
Description
This command is used to configure the policy-based burst tolerance for a parent policer instance created when the policy is applied to a SAP or subscriber context. The system uses the parent policer’s min-thresh-separation value, the priority level’s mbs-contribution value and the number of child policers currently attached to the priority level to derive the priority level’s shared-portion and fair-portion of burst tolerance within the local priority level. The shared-portion and fair-portions for each priority level are then used by the system to calculate each priority level’s discard-unfair threshold and discard-all threshold.
The value for a priority level’s mbs-contribution within the policer-control-policy may be overridden on the SAP or subscriber sub-profile where the policy is applied in order to allow fine tuning of the discard-unfair and discard-all thresholds relevant to the needs of the local child policers on the object.
Accumulative Nature of Burst Tolerance for a Parent Policer Priority Level
When defining mbs-contribution, the specified size may only be a portion of the burst tolerance associated with the priority level. The packets associated with the priority level share the burst tolerance of lower within the parent policer. As the parent policer PIR bucket depth increases during congestion, the lower priority packets eventually experience discard based on each priority’s discard-unfair and discard-all thresholds. Assuming congestion continues once all the lower priority packets have been prevented from consuming bucket depth, the burst tolerance for the priority level is consumed by its own packets and any packets associated with higher priorities.
The Effect of Fair and Unfair Child Policer Traffic at a Parent Policer Priority Level
The system continually monitors the offered rate of each child policer on each parent policer priority level and detects when the policer is in a congested state (the aggregate offered load is greater than the decrement rate defined on the parent policer). As previously stated, the result of congestion is that the parent policer's bucket depth will increase until it eventually hovers around either a discard-unfair or discard-all threshold belonging to one of the priority levels. This threshold is the point where enough packets are being discarded that the increment rate and decrement rate begin to even out. If only a single child policer is associated to the priority level, the discard-unfair threshold is not used since fairness is only applicable when multiple child policers are competing at the same priority level.
When multiple child policers are sharing the congested priority level, the system uses the offered rates and the parenting parameters of each child to determine the fair rate per child when the parent policer is unable to meet the bandwidth needs of each child. The fair rate represents the number of bandwidth that each child at the priority level should receive relative to the other children at the same level according to the policer control policy instance managing the child policers. This fair rate is applied as the decrement rate for each child's FIR bucket. Changing a child’s FIR rate does not modify the number of packets forwarded by the parent policer for the child’s priority level. It simply modifies the forwarded ratio between the children on that priority level. Since each child FIR bucket has some level of burst tolerance before marking its packets as unfair, the current parent policer bucket depth may at times rise above the discard-unfair threshold. The mbs-contribution value provides a means to define how much separation is provided between the priority level’s discard-unfair and discard-all threshold to allow the parent policer to absorb some of the FIR burst before reaching the priority’s discard-all threshold.
This level of fair aggregate burst tolerance is based on the decrement rate of the parent policer’s PIR bucket while the individual fair bursts making up the aggregate are based on each child’s FIR decrement rate. The aggregate fair rate of the priority level is managed by the system with consideration of the current rate of traffic in higher priority levels. In essence, the system ensures that for each iteration of the child FIR rate calculation, the sum of the child FIR decrement rates plus the sum of the higher priority traffic increment rates equals the parent policers decrement rate. This means that dynamic numbers of higher priority traffic can be ignored when sizing a lower priority’s fair aggregate burst tolerance. Consider the following:
-
The parent policer decrement rate is set to 20 Mb/s (max-rate 20,000).
-
A priority level’s fair burst size is set to 30 kbytes (mbs-contribution 30 kbytes).
-
Higher priority traffic is currently taking 12 Mb/s.
-
The priority level has three child policers attached.
-
Each child’s PIR MBS is set to 10 kbytes, which makes each child’s FIR MBS 10 kbytes.
-
The children want 10 Mb/s, but only 8 Mb/s is available,
-
Based on weights, the children's FIR rates are set as follows:
FIR Rate
FIR MBS
Child 1
4 Mb/s
10 kbytes
Child 2
3 Mb/s
10 kbytes
Child 3
1 Mb/s
10 kbytes
The 12 Mb/s of the higher priority traffic and the 8 Mb/s of fair traffic equal the 20 Mb/s decrement rate of the parent policer.
It is clear that the higher priority traffic is consuming 12 Mb/s of the parent policer’s decrement rate, leaving 8 Mb/s of decrement rate for the lower priority’s fair traffic.
-
The burst tolerance of child 1 is based on 10 kbytes above 4 Mb/s,
-
The burst tolerance of child 2 is based on 10 kbytes above 3 Mb/s,
-
The burst tolerance of child 3 is based on 10 kbytes above 1 Mb/s.
If all three children burst simultaneously (unlikely), they will consume 30 kbytes above 8 Mb/s. This is the same as the remaining decrement rate after the higher priority traffic.
Parent Policer Total Burst Tolerance and Downstream Buffering
The highest in-use priority level’s discard-all threshold is the total burst tolerance of the parent policer. In some cases the parent policer represents downstream bandwidth capacity and the max-rate of the parent policer is set to prevent overrunning the downstream bandwidth. The burst tolerance of the parent policer defines how much more traffic may be sent beyond the downstream scheduling capacity. In the worst case scenario, when the downstream buffering is insufficient to handle the total possible burst from the parent policer, downstream discards based on lack of buffering may occur. However, in all likelihood, this is not the case.
In most cases, lower priority traffic in the policer is responsible for the greater part of congestion above the parent policer rate. Since this traffic is discarded with a lower threshold, this lowers the effective burst tolerance even while the highest priority traffic is present.
Configuring a Priority Level's MBS Contribution Value
In the most conservative case, a priority level’s mbs-contribution value may be set to be greater than the sum of child policer’s mbs and one max-size-frame per child policer. This ensures that even in the absolute worst case where all the lower priority levels are simultaneously bursting to the maximum capacity of each child, enough burst tolerance for the priority’s children will exist if they also burst to their maximum capacity.
Since simply adding up all the child policer’s PIR MBS values may result in large overall burst tolerances that are not ever likely to be needed, you should consider some level of burst oversubscription when configuring the mbs-contribution value for each priority level. The number of oversubscription should be determined based on the needs of each priority level.
Using the Fixed Keyword to Create Deterministic Parent Policer Discard Thresholds
In the default behavior, the system ignores the mbs-contribution values for a priority level on a subscriber or SAP parent policer when a child policer is not currently associated with the level. This prevents additional burst tolerance from being added to higher priority traffic within the parent policer.
This does cause fluctuations in the defined threshold values when child policers are added or removed from a parent policer instance. If this behavior is undesirable, the fixed keyword may be used which causes the mbs-contribution value to always be included in the calculation of parent policer’s discard thresholds. The defined mbs-contribution value may be overridden on a subscriber sla-profile or on a SAP instance, but the fixed nature of the contribution cannot be overridden.
If the defined mbs-contribution value for the priority level is zero, the priority level will have no effect on the parent policer’s defined discard thresholds. A packet associated with the priority level will use the next lower priority level’s discard-unfair and discard-all thresholds.
The form of this command returns the policy’s priority level’s MBS contribution to the default value. When changed, the thresholds for the priority level and all higher priority levels for all instances of the parent policer is recalculated.
Parameters
- size [bytes | kilobytes]
-
The size parameter is required when executing the mbs-contribution command. It is expressed as an integer and specifies the priority’s specific portion of accumulative MBS for the priority level in bytes or kilobytes which is selected by the trailing bytes or kilobytes keywords. If both bytes and kilobytes are missing, kilobytes is assumed. Setting this value has no effect on parent policer instances where the priority level’s mbs-contribution value has been overridden.
- bytes | kilobytes:
-
The bytes keyword is optional and is mutually exclusive with the kilobytes keyword. When specified, size is interpreted as specifying the size of min-thresh-separation in bytes.
The kilobytes keyword is optional and is mutually exclusive with the bytes keyword. Size is interpreted as specifying the size of min-thresh-separation in kilobytes.
- fixed
-
This optional fixed keyword is used to force the inclusion of the defined mbs-contribution value in the parent policer’s discard threshold calculations. If the mbs-contribution command is executed without the fixed keyword, the fixed calculation behavior for the priority level is removed.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
mbs-contribution
Syntax
mbs-contribution size [bytes | kilobytes]
no mbs-contribution
Context
[Tree] (config>card>fp>ingress>access>qgrp>policer-ctrl-over>mbs-thrshlds>prio mbs-contribution)
[Tree] (config>card>fp>ing>network>qgrp>policer-ctrl-over>mbs-thrshlds>prio mbs-contribution)
Full Context
configure card fp ingress access queue-group policer-control-override priority-mbs-thresholds priority mbs-contribution
configure card fp ingress network queue-group policer-control-override priority-mbs-thresholds priority mbs-contribution
Description
This command configures the policy-based burst tolerance for a parent policer instance created when the policy is applied to a SAP or subscriber context. The system uses the parent policer’s min-thresh-separation value, the priority level’s mbs-contribution value and the number of child policers currently attached to the priority level to derive the priority level’s shared-portion and fair-portion of burst tolerance within the local priority level. The shared-portion and fair-portions for each priority level are then used by the system to calculate each priority level’s discard-unfair threshold and discard-all threshold.
The value for a priority level’s mbs-contribution within the policer-control-policy may be overridden on the SAP or subscriber sub-profile where the policy is applied in order to allow fine tuning of the discard-unfair and discard-all thresholds relevant to the needs of the local child policers on the object.
Accumulative Nature of Burst Tolerance for a Parent Policer Priority Level
When defining mbs-contribution, the specified size may only be a portion of the burst tolerance associated with the priority level. The packets associated with the priority level share the burst tolerance of lower within the parent policer. As the parent policer PIR bucket depth increases during congestion, the lower priority packets eventually experience discard based on each priority’s discard-unfair and discard-all thresholds. Assuming congestion continues once all the lower priority packets have been prevented from consuming bucket depth, the burst tolerance for the priority level will be consumed by its own packets and any packets associated with higher priorities.
The Effect of Fair and Unfair Child Policer Traffic at a Parent Policer Priority Level
The system continually monitors the offered rate of each child policer on each parent policer priority level and detects when the policer is in a congested state (the aggregate offered load is greater than the decrement rate defined on the parent policer). As previously stated, the result of congestion is that the parent policer's bucket depth will increase until it eventually hovers around either a discard-unfair or discard-all threshold belonging to one of the priority levels. This threshold is the point where enough packets are being discarded that the increment rate and decrement rate begin to even out. If only a single child policer is associated to the priority level, the discard-unfair threshold is not used since fairness is only applicable when multiple child policers are competing at the same priority level.
When multiple child policers are sharing the congested priority level, the system uses the offered rates and the parenting parameters of each child to determine the fair rate per child when the parent policer is unable to meet the bandwidth needs of each child. The fair rate represents the amount of bandwidth that each child at the priority level should receive relative to the other children at the same level according to the policer control policy instance managing the child policers. This fair rate is applied as the decrement rate for each child’s FIR bucket. Changing a child’s FIR rate does not modify the amount of packets forwarded by the parent policer for the child’s priority level. It simply modifies the forwarded ratio between the children on that priority level. Since each child FIR bucket has some level of burst tolerance before marking its packets as unfair, the current parent policer bucket depth may at times rise above the discard-unfair threshold. The mbs-contribution value provides a means to define how much separation is provided between the priority level’s discard-unfair and discard-all threshold to allow the parent policer to absorb some amount of FIR burst before reaching the priority’s discard-all threshold.
This level of fair aggregate burst tolerance is based on the decrement rate of the parent policer’s PIR bucket while the individual fair bursts making up the aggregate are based on each child’s FIR decrement rate. The aggregate fair rate of the priority level is managed by the system with consideration of the current rate of traffic in higher priority levels. In essence, the system ensures that for each iteration of the child FIR rate calculation, the sum of the child FIR decrement rates plus the sum of the higher priority traffic increment rates equals the parent policers decrement rate. This means that dynamic amounts of higher priority traffic can be ignored when sizing a lower priority’s fair aggregate burst tolerance. Consider the following:
-
The parent policer decrement rate is set to 20 Mb/s (max-rate 20,000).
-
A priority level’s fair burst size is set to 30 kbytes (mbs-contribution 30 kilobytes).
-
Higher priority traffic is currently taking 12 Mb/s.
-
The priority level has three child policers attached.
-
Each child’s PIR MBS is set to 10 kbytes, which makes each child’s FIR MBS 10 kbytes.
-
The children want 10 Mb/s, but only 8 Mb/s is available,
-
Based on weights, the children's FIR rates are set as follows:
FIR Rate
FIR MBS
Child 1
4 Mb/s
10 kbytes
Child 2
3 Mb/s
10 kbytes
Child 3
1 Mb/s
10 kbytes
The 12 Mb/s of the higher priority traffic and the 8 Mb/s of fair traffic equal the 20 Mb/s decrement rate of the parent policer.
It is clear that the higher priority traffic is consuming 12 Mb/s of the parent policer’s decrement rate, leaving 8 Mb/s of decrement rate for the lower priority’s fair traffic.
-
The burst tolerance of child 1 is based on 10 kbytes above 4 Mb/s,
-
The burst tolerance of child 2 is based on 10 kbytes above 3 Mb/s,
-
The burst tolerance of child 3 is based on 10 kbytes above 1 Mb/s.
If all three children burst simultaneously (unlikely), they will consume 30 kbytes above 8 Mb/s. This is the same as the remaining decrement rate after the higher priority traffic.
Parent Policer Total Burst Tolerance and Downstream Buffering
The highest in-use priority level’s discard-all threshold is the total burst tolerance of the parent policer. In some cases the parent policer represents downstream bandwidth capacity and the max-rate of the parent policer is set to prevent overrunning the downstream bandwidth. The burst tolerance of the parent policer defines how much more traffic may be sent beyond the downstream scheduling capacity. In the worst case scenario, when the downstream buffering is insufficient to handle the total possible burst from the parent policer, downstream discards based on lack of buffering may occur. However, in all likelihood, this is not the case.
In most cases, lower priority traffic in the policer will be responsible for the greater part of congestion above the parent policer rate. Since this traffic is discarded with a lower threshold, this lowers the effective burst tolerance even while the highest priority traffic is present.
Configuring a Priority Level's MBS Contribution Value
In the most conservative case, a priority level’s mbs-contribution value may be set to be greater than the sum of child policer’s MBS and one max-size-frame per child policer. This ensures that even in the absolute worst case where all the lower priority levels are simultaneously bursting to the maximum capacity of each child, enough burst tolerance for the priority’s children will exist if they also burst to their maximum capacity.
Since simply adding up all the child policer’s PIR MBS values may result in large overall burst tolerances that are not ever likely to be needed, you should consider some level of burst oversubscription when configuring the mbs-contribution value for each priority level. The amount of oversubscription should be determined based on the needs of each priority level.
Using the Fixed Keyword to Create Deterministic Parent Policer Discard Thresholds
In the default behavior, the system ignores the mbs-contribution values for a priority level on a subscriber or SAP parent policer when a child policer is not currently associated with the level. This prevents additional burst tolerance from being added to higher priority traffic within the parent policer.
This does cause fluctuations in the defined threshold values when child policers are added or removed from a parent policer instance. If this behavior is undesirable, the fixed keyword may be used which causes the mbs-contribution value to always be included in the calculation of parent policer’s discard thresholds. The defined mbs-contribution value may be overridden on a subscriber SLA profile or on a SAP instance, but the fixed nature of the contribution cannot be overridden.
If the defined mbs-contribution value for the priority level is zero, the priority level will have no effect on the parent policer’s defined discard thresholds. A packet associated with the priority level will use the next lower priority level’s discard-unfair and discard-all thresholds.
The no form of this command reverts to the policy’s priority level’s MBS contribution to the default value. When changed, the thresholds for the priority level and all higher priority levels for all instances of the parent policer are recalculated.
Default
no mbs-contribution
Parameters
- size
-
Specifies that the size parameter is required when executing the mbs-contribution command. It is expressed as an integer and specifies the priority’s specific portion amount of accumulative MBS for the priority level in bytes or kilobytes which is selected by the trailing bytes or kilobytes keywords. If both bytes and kilobytes are missing, kilobytes is assumed. Setting this value has no effect on parent policer instances where the priority level’s mbs-contribution value has been overridden. Clearing an override on parent policer instance causes this value to be enforced.
- bytes, kilobytes
-
Specifies that the bytes keyword is optional and is mutually exclusive with the kilobytes keyword. When specified, size is interpreted as specifying the size of min-thresh-separation in bytes.
The kilobytes keyword is optional and is mutually exclusive with the bytes keyword. When specified, size is interpreted as specifying the size of min-thresh-separation in kilobytes.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
mbs-contribution
Syntax
mbs-contribution size [bytes | kilobytes]
Context
[Tree] (config>service>epipe>sap>egress>policer-ctrl-over>mbs-thrshlds>priority mbs-contribution)
[Tree] (config>service>cpipe>sap>egress>policer-ctrl-over>mbs-thrshlds>priority mbs-contribution)
[Tree] (config>service>apipe>sap>egress>policer-ctrl-over>mbs-thrshlds>priority mbs-contribution)
[Tree] (config>service>fpipe>sap>egress>policer-ctrl-over>mbs-thrshlds>priority mbs-contribution)
[Tree] (config>service>cpipe>sap>ingress>policer-ctrl-over>mbs-thrshlds>priority mbs-contribution)
[Tree] (config>service>ipipe>sap>ingress>policer-ctrl-over>mbs-thrshlds>priority mbs-contribution)
[Tree] (config>service>epipe>sap>ingress>policer-ctrl-over>mbs-thrshlds>priority mbs-contribution)
[Tree] (config>service>fpipe>sap>ingress>policer-ctrl-over>mbs-thrshlds>priority mbs-contribution)
[Tree] (config>service>ipipe>sap>egress>policer-ctrl-over>mbs-thrshlds>priority mbs-contribution)
[Tree] (config>service>apipe>sap>ingress>policer-ctrl-over>mbs-thrshlds>priority mbs-contribution)
Full Context
configure service epipe sap egress policer-control-override priority-mbs-thresholds priority mbs-contribution
configure service cpipe sap egress policer-control-override priority-mbs-thresholds priority mbs-contribution
configure service apipe sap egress policer-control-override priority-mbs-thresholds priority mbs-contribution
configure service fpipe sap egress policer-control-override priority-mbs-thresholds priority mbs-contribution
configure service cpipe sap ingress policer-control-override priority-mbs-thresholds priority mbs-contribution
configure service ipipe sap ingress policer-control-override priority-mbs-thresholds priority mbs-contribution
configure service epipe sap ingress policer-control-override priority-mbs-thresholds priority mbs-contribution
configure service fpipe sap ingress policer-control-override priority-mbs-thresholds priority mbs-contribution
configure service ipipe sap egress policer-control-override priority-mbs-thresholds priority mbs-contribution
configure service apipe sap ingress policer-control-override priority-mbs-thresholds priority mbs-contribution
Description
The mbs-contribution override command within the SAP ingress and egress contexts is used to override a parent policer’s priority level’s mbs-contribution parameter that is defined within the policer-control-policy applied to the SAP. This override allow the priority level’s burst tolerance to be tuned based on the needs of the SAP’s child policers attached to the priority level.
When the override is defined, modifications to the policer-control-policy priority level’s mbs-contribution parameter have no effect on the SAP’s parent policer priority level until the override is removed using the no mbs-contribution command within the SAP.
The no form of this command removes the override and allows the mbs-contribution setting from the policer-control-policy to control the parent policer’s priority level’s burst tolerance.
Default
no mbs-contribution
Parameters
- size
-
Specifies the mbs-contribution override value.
- bytes
-
Specifies that size is expressed in bytes. The bytes and kilobytes keywords are mutually exclusive and optional. The default is kilobytes.
- kilobytes
-
Specifies that size is expressed in kilobytes. The bytes and kilobytes keywords are mutually exclusive and optional. The default is kilobytes.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
- configure service ipipe sap ingress policer-control-override priority-mbs-thresholds priority mbs-contribution
- configure service epipe sap ingress policer-control-override priority-mbs-thresholds priority mbs-contribution
- configure service epipe sap egress policer-control-override priority-mbs-thresholds priority mbs-contribution
- configure service ipipe sap egress policer-control-override priority-mbs-thresholds priority mbs-contribution
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS
- configure service fpipe sap ingress policer-control-override priority-mbs-thresholds priority mbs-contribution
- configure service cpipe sap ingress policer-control-override priority-mbs-thresholds priority mbs-contribution
- configure service fpipe sap egress policer-control-override priority-mbs-thresholds priority mbs-contribution
- configure service cpipe sap egress policer-control-override priority-mbs-thresholds priority mbs-contribution
7450 ESS, 7750 SR-7/12/12e, 7750 SR-e, 7950 XRS
- configure service apipe sap ingress policer-control-override priority-mbs-thresholds priority mbs-contribution
- configure service apipe sap egress policer-control-override priority-mbs-thresholds priority mbs-contribution
mbs-contribution
Syntax
mbs-contribution size [{bytes | kilobytes}]
Context
[Tree] (config>service>vpls>sap>egress>policer-ctrl-over>mbs-thrshlds>priority mbs-contribution)
[Tree] (config>service>vpls>sap>ingress>policer-ctrl-over>mbs-thrshlds>priority mbs-contribution)
Full Context
configure service vpls sap egress policer-control-override priority-mbs-thresholds priority mbs-contribution
configure service vpls sap ingress policer-control-override priority-mbs-thresholds priority mbs-contribution
Description
The mbs-contribution override command within the SAP ingress and egress contexts is used to override a parent policer’s priority level’s mbs-contribution parameter that is defined within the policer-control-policy applied to the SAP. This override allow the priority level’s burst tolerance to be tuned based on the needs of the SAP’s child policers attached to the priority level.
When the override is defined, modifications to the policer-control-policy priority level’s mbs-contribution parameter have no effect on the SAP’s parent policer priority level until the override is removed using the no mbs-contribution command within the SAP.
The no form of this command removes the override and allows the mbs-contribution setting from the policer-control-policy to control the parent policer’s priority level’s burst tolerance.
Default
no mbs-contribution
Parameters
- size
-
This parameter is required when specifying MBS contribution override and is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional byte and kilobyte keywords are mutually exclusive and are used to explicitly define whether size represents bytes or kilobytes.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
mbs-contribution
Syntax
mbs-contribution size [{bytes | kilobytes}]
Context
[Tree] (config>service>ies>if>sap>egress>policer-ctrl-over>mbs-thrshlds>priority mbs-contribution)
[Tree] (config>service>ies>if>sap>ingress>policer-ctrl-over>mbs-thrshlds>priority mbs-contribution)
Full Context
configure service ies interface sap egress policer-control-override priority-mbs-thresholds priority mbs-contribution
configure service ies interface sap ingress policer-control-override priority-mbs-thresholds priority mbs-contribution
Description
The mbs-contribution override command within the SAP ingress and egress contexts is used to override a parent policer’s priority level’s mbs-contribution parameter that is defined within the policer-control-policy applied to the SAP. This override allow the priority level’s burst tolerance to be tuned based on the needs of the SAP’s child policers attached to the priority level.
When the override is defined, modifications to the policer-control-policy priority level’s mbs-contribution parameter have no effect on the SAP’s parent policer priority level until the override is removed using the no mbs-contribution command within the SAP.
The no form of this command removes the override and allows the mbs-contribution setting from the policer-control-policy to control the parent policer’s priority level’s burst tolerance.
Default
no mbs-contribution
Parameters
- size
-
This parameter is required when specifying MBS contribution override and is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional byte and kilobyte keywords are mutually exclusive and are used to explicitly define whether size represents bytes or kilobytes.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
mbs-contribution
Syntax
mbs-contribution size [bytes | kilobytes]
Context
[Tree] (config>service>vprn>if>sap>egress>policer-ctrl-over>mbs-thrshlds>priority mbs-contribution)
[Tree] (config>service>vprn>if>sap>ingress>policer-ctrl-over>mbs-thrshlds>priority mbs-contribution)
Full Context
configure service vprn interface sap egress policer-control-override priority-mbs-thresholds priority mbs-contribution
configure service vprn interface sap ingress policer-control-override priority-mbs-thresholds priority mbs-contribution
Description
The mbs-contribution override command within the SAP ingress and egress contexts is used to override a parent policer’s priority level’s mbs-contribution parameter that is defined within the policer-control-policy applied to the SAP. This override allow the priority level’s burst tolerance to be tuned based on the needs of the SAP’s child policers attached to the priority level.
When the override is defined, modifications to the policer-control-policy priority level’s mbs-contribution parameter have no effect on the SAP’s parent policer priority level until the override is removed using the no mbs-contribution command within the SAP.
The no form of this command removes the override and allows the mbs-contribution setting from the policer-control-policy to control the parent policer’s priority level’s burst tolerance.
Default
no mbs-contribution
Parameters
- size
-
This parameter is required when specifying MBS contribution override and is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional byte and kilobyte keywords are mutually exclusive and are used to explicitly define whether size represents bytes or kilobytes.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
mbs-contribution
Syntax
mbs-contribution size [bytes | kilobytes] [fixed]
no mbs-contribution
Context
[Tree] (config>qos>plcr-ctrl-plcy>root>priority-mbs-thresholds>priority mbs-contribution)
Full Context
configure qos policer-control-policy root priority-mbs-thresholds priority mbs-contribution
Description
The mbs-contribution command is used to configure the policy-based burst tolerance for a parent policer instance created when the policy is applied to a SAP, or a subscriber context for the 7450 ESS and 7750 SR, or a 7950 XRS multiservice site. The system uses the parent policer’s min-thresh-separation value, the priority level’s mbs-contribution value, and the number of child policers currently attached to the priority level to derive the priority level’s shared-portion and fair-portion of burst tolerance within the local priority level. The shared-portion and fair-portions for each priority level are then used by the system to calculate each priority level’s discard-unfair threshold and discard-all threshold. The mbs-contribution is the minimum separation between two adjacent active discard-all thresholds.
The value for a priority level’s mbs-contribution within the policer-control-policy may be overridden on the SAP, or subscriber sub-profile (applies to the 7450 ESS and 7750 SR) or multiservice site (for 7950 XRS) where the policy is applied in order to allow fine tuning of the discard-unfair and discard-all thresholds relevant to the needs of the local child policers on the object.
Accumulative Nature of Burst Tolerance for a Parent Policer Priority Level
When defining mbs-contribution, the specified size may only be a portion of the burst tolerance associated with the priority level. The packets associated with the priority level share the burst tolerance of lower within the parent policer. As the parent policer PIR bucket depth increases during congestion, the lower priority packets eventually experience discard based on each priority’s discard-unfair and discard-all thresholds. Assuming congestion continues when all the lower priority packets have been prevented from consuming bucket depth, the burst tolerance for the priority level will be consumed by its own packets and any packets associated with higher priorities.
The Effect of Fair and Unfair Child Policer Traffic at a Parent Policer Priority Level
The system continually monitors the offered rate of each child policer on each parent policer priority level and detects when the policer is in a congested state (the aggregate offered load is greater than the decrement rate defined on the parent policer). As previously stated, the result of congestion is that the parent policer's bucket depth will increase until it eventually hovers around either a discard-unfair or discard-all threshold belonging to one of the priority levels. This threshold is the point where enough packets are being discarded that the increment rate and decrement rate begin to even out. If only a single child policer is associated with the priority level, the discard-unfair threshold is not used since fairness is only applicable when multiple child policers are competing at the same priority level.
When multiple child policers are sharing the congested priority level, the system uses the offered rates and the parenting parameters of each child to determine the fair rate per child when the parent policer is unable to meet the bandwidth needs of each child. The fair rate represents the amount of bandwidth that each child at the priority level should receive relative to the other children at the same level according to the policer control policy instance managing the child policers. This fair rate is applied as the decrement rate for each child's FIR bucket. Changing a child’s FIR rate does not modify the number of packets forwarded by the parent policer for the child’s priority level. It just modifies the forwarded ratio between the children on that priority level. Since each child FIR bucket has some level of burst tolerance before marking its packets as unfair, the current parent policer bucket depth may at times rise above the discard-unfair threshold. The mbs-contribution value provides a means to define how much separation is provided between the priority level’s discard-unfair and discard-all threshold to allow the parent policer to absorb some amount of FIR burst before reaching the priority’s discard-all threshold.
This level of fair aggregate burst tolerance is based on the decrement rate of the parent policer’s PIR bucket while the individual fair bursts making up the aggregate are based on each child’s FIR decrement rate. The aggregate fair rate of the priority level is managed by the system with consideration of the current rate of traffic in higher priority levels. In essence, the system ensures that for each iteration of the child FIR rate calculation, the sum of the child FIR decrement rates plus the sum of the higher priority traffic increment rates equals the parent policers decrement rate. This means that dynamic amounts of higher priority traffic can be ignored when sizing a lower priority’s fair aggregate burst tolerance. Consider the following:
-
The parent policer decrement rate is set to 20 Mb/s (max-rate 20,000).
-
A priority level’s fair burst size is set to 30 kbytes (mbs-contribution 30 kbytes).
-
Higher priority traffic is currently taking 12 Mb/s.
-
The priority level has three child policers attached.
-
Each child’s PIR MBS is set to 10 kbytes, which makes each child’s FIR MBS 10 kbytes.
-
The children want 10 Mb/s, but only 8 Mb/s is available
-
Based on weights, the children's FIR rates are set as follows:
FIR Rate
FIR MBS
Child 1
4 Mb/s
10 kbytes
Child 2
3 Mb/s
10 kbytes
Child 3
1 Mb/s
10 kbytes
The 12 Mb/s of the higher priority traffic and the 8 Mb/s of fair traffic equal the 20 Mb/s decrement rate of the parent policer.
It is clear that the higher priority traffic is consuming 12 Mb/s of the parent policer’s decrement rate, leaving 8 Mb/s of decrement rate for the lower priority’s fair traffic.
-
The burst tolerance of child 1 is based on 10 kbytes above 4 Mb/s.
-
The burst tolerance of child 2 is based on 10 kbytes above 3 Mb/s.
-
The burst tolerance of child 3 is based on 10 kbytes above 1 Mb/s.
If all three children burst simultaneously (unlikely), they will consume 30 kbytes above 8 Mb/s. This is the same as the remaining decrement rate after the higher priority traffic.
Parent Policer Total Burst Tolerance and Downstream Buffering
The highest in-use priority level’s discard-all threshold is the total burst tolerance of the parent policer. In some cases, the parent policer represents downstream bandwidth capacity and the max-rate of the parent policer is set to prevent overrunning the downstream bandwidth. The burst tolerance of the parent policer defines how much more traffic may be sent beyond the downstream scheduling capacity. In the worst-case scenario, when the downstream buffering is insufficient to handle the total possible burst from the parent policer, downstream discards based on lack of buffering may occur. However, in all likelihood, this is not the case.
In most cases, lower priority traffic in the policer will be responsible for the greater part of congestion above the parent policer rate. Since this traffic is discarded with a lower threshold, this lowers the effective burst tolerance even while the highest priority traffic is present.
Configuring a Priority Level's MBS Contribution Value
In the most conservative case, a priority level’s mbs-contribution value may be set to be greater than the sum of child policer’s mbs and one max-size-frame per child policer. This ensures that even in the absolute worst case where all the lower priority levels are simultaneously bursting to the maximum capacity of each child, enough burst tolerance for the priority’s children will exist if they also burst to their maximum capacity.
Since simply adding up all the child policer’s PIR MBS values may result in large overall burst tolerances that are not ever likely to be needed, consider some level of burst oversubscription when configuring the mbs-contribution value for each priority level. The amount of oversubscription should be determined based on the needs of each priority level.
Using the Fixed Keyword to Create Deterministic Parent Policer Discard Thresholds
In the default behavior, the system ignores the mbs-contribution values for a priority level on a subscriber for 7450 ESS and 7750 SR, or a multiservice site for 7950 XRS, or SAP parent policer when a child policer is not currently associated with the level. This prevents additional burst tolerance from being added to higher priority traffic within the parent policer.
This does cause fluctuations in the defined threshold values when child policers are added or removed from a parent policer instance. If this behavior is undesirable, the fixed keyword may be used that causes the mbs-contribution value to always be included in the calculation of parent policer’s discard thresholds. The defined mbs-contribution value may be overridden on a subscriber sla-profile for the 7450 ESS and 7750 SR, or on a multiservice site for the 7950 XRS, or on a SAP instance, but the fixed nature of the contribution cannot be overridden.
If the defined mbs-contribution value for the priority level is zero, the priority level will have no effect on the parent policer’s defined discard thresholds. A packet associated with the priority level will use the next lower priority level’s discard-unfair and discard-all thresholds.
The no form of this command returns the policy’s priority level’s MBS contribution to the default value. When changed, the thresholds for the priority level and all higher priority levels for all instances of the parent policer will be recalculated.
Parameters
- size
-
The size parameter is required when executing the mbs-contribution command. It is expressed as an integer and specifies the priority’s specific portion amount of accumulative MBS for the priority level. Setting this value has no effect on parent policer instances where the priority level’s mbs-contribution value has been overridden.
- bytes | kilobytes:
-
This parameter indicates whether the size is expressed in bytes or kilobytes.
- fixed
-
The optional fixed keyword is used to force the inclusion of the defined mbs-contribution value in the parent policer’s discard threshold calculations. If the mbs-contribution command is executed without the fixed keyword, the fixed calculation behavior for the priority level is removed.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
mbytes
mbytes
Syntax
mbytes {mbytes | disable}
no mbytes
Context
[Tree] (config>system>security>ssh>key-re-exchange>client mbytes)
[Tree] (config>system>security>ssh>key-re-exchange>server mbytes)
Full Context
configure system security ssh key-re-exchange client mbytes
configure system security ssh key-re-exchange server mbytes
Description
This command configures the maximum bytes to be transmitted before a key re-exchange is initiated by the server.
The no form of this command reverts to the default value.
Default
mbytes 1024
Parameters
- mbytes
-
Specifies the number of megabytes, on a SSH session, after which the SSH client initiates the key-re-exchange.
- disable
-
Specifies that a session will never timeout. To re-enable mbytes, enter the command without the disable option.
Platforms
All
mc-constraints
mc-constraints
Syntax
mc-constraints
Context
[Tree] (config>subscr-mgmt>msap-policy>vpls-only>igmp-snp>mcac mc-constraints)
Full Context
configure subscriber-mgmt msap-policy vpls-only-sap-parameters igmp-snooping mcac mc-constraints
Description
Commands in this context configure the level and its associated bandwidth for a bundle or a logical interface.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
mc-constraints
Syntax
mc-constraints
Context
[Tree] (config>service>vpls>sap>mld-snooping>mcac mc-constraints)
[Tree] (config>service>vpls>sap>igmp-snooping>mcac mc-constraints)
Full Context
configure service vpls sap mld-snooping mcac mc-constraints
configure service vpls sap igmp-snooping mcac mc-constraints
Description
Commands in this context configure multicast CAC constraints.
Platforms
All
mc-constraints
Syntax
mc-constraints
Context
[Tree] (config>service>vprn>igmp>grp-if>mcac mc-constraints)
[Tree] (config>service>vprn>pim>if>mcac mc-constraints)
[Tree] (config>service>vprn>igmp>if>mcac mc-constraints)
[Tree] (config>service>vprn>mld>if>mcac mc-constraints)
[Tree] (config>service>vprn>mld>grp-if>mcac mc-constraints)
Full Context
configure service vprn igmp group-interface mcac mc-constraints
configure service vprn pim interface mcac mc-constraints
configure service vprn igmp interface mcac mc-constraints
configure service vprn mld interface mcac mc-constraints
configure service vprn mld group-interface mcac mc-constraints
Description
Commands in this context configure multicast CAC constraints.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
- configure service vprn mld group-interface mcac mc-constraints
- configure service vprn igmp group-interface mcac mc-constraints
All
- configure service vprn igmp interface mcac mc-constraints
- configure service vprn pim interface mcac mc-constraints
- configure service vprn mld interface mcac mc-constraints
mc-constraints
Syntax
mc-constraints
Context
[Tree] (config>router>mld>interface>mcac mc-constraints)
[Tree] (config>router>igmp>grp-if>mcac mc-constraints)
[Tree] (config>router>mld>grp-if>mcac mc-constraints)
[Tree] (config>router>igmp>interface>mcac mc-constraints)
[Tree] (config>router>pim>interface>mcac mc-constraints)
[Tree] (config>router>mcac>policy>bundle mc-constraints)
Full Context
configure router mld interface mcac mc-constraints
configure router igmp group-interface mcac mc-constraints
configure router mld group-interface mcac mc-constraints
configure router igmp interface mcac mc-constraints
configure router pim interface mcac mc-constraints
configure router mcac policy bundle mc-constraints
Description
Commands in this context configure the level and its associated bandwidth for a bundle or a logical interface.
Platforms
All
- configure router pim interface mcac mc-constraints
- configure router mld interface mcac mc-constraints
- configure router mcac policy bundle mc-constraints
- configure router igmp interface mcac mc-constraints
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
- configure router igmp group-interface mcac mc-constraints
- configure router mld group-interface mcac mc-constraints
mc-ecmp-balance
mc-ecmp-balance
Syntax
[no] mc-ecmp-balance
Context
[Tree] (config>router>pim mc-ecmp-balance)
Full Context
configure router pim mc-ecmp-balance
Description
This command enables multicast balancing of traffic over ECMP links based on the number of (S, G) distributed over each link. When enabled, each new multicast stream that needs to be forwarded over an ECMP link is compared to the count of (S, G) already using each link, so that the link with the fewest (S, G) is chosen.
This command cannot be used together with the mc-ecmp-hashing-enabled command.
The no form of this command disables multicast ECMP balancing.
Platforms
All
mc-ecmp-balance
Syntax
[no] mc-ecmp-balance
Context
[Tree] (config>service>vprn>pim mc-ecmp-balance)
Full Context
configure service vprn pim mc-ecmp-balance
Description
This command enables multicast balancing of traffic over ECMP links based on the number of (S, G) distributed over each link. When enabled, each new multicast stream that needs to be forwarded over an ECMP link is compared to the count of (S, G) already using each link, so that the link with the fewest (S, G) is chosen.
This command cannot be used together with the mc-ecmp-hashing-enabled command.
The no form of this command disables multicast ECMP balancing.
Platforms
All
mc-ecmp-balance-hold
mc-ecmp-balance-hold
Syntax
mc-ecmp-balance-hold minutes
no mc-ecmp-balance-hold
Context
[Tree] (config>router>pim mc-ecmp-balance-hold)
Full Context
configure router pim mc-ecmp-balance-hold
Description
This command defines a hold period that applies after an interface has been added to the ECMP link. It is also used periodically to rebalance if channels have been removed from the ECMP link.
If the ECMP interface has not changed in the hold period and if no multicast streams have been removed, then no action is taken when the timer triggers.
This parameter should be used to avoid excessive changes to the multicast distribution.
A rebalance will not occur to multicast streams that have a priority greater than the configured ecmp-opt-threshold.
The no form of this command removes the minutes value from the configuration.
Parameters
- minutes
-
Specifies the hold time, in minutes, that applies after an interface has been added to the ECMP link.
Platforms
All
mc-ecmp-balance-hold
Syntax
mc-ecmp-balance-hold minutes
no mc-ecmp-balance-hold
Context
[Tree] (config>service>vprn>pim mc-ecmp-balance-hold)
Full Context
configure service vprn pim mc-ecmp-balance-hold
Description
This command configures the hold time for multicast balancing over ECMP links.
Parameters
- minutes
-
Specifies the hold time, in minutes, that applies after an interface has been added to the ECMP link.
Platforms
All
mc-ecmp-hashing-enabled
mc-ecmp-hashing-enabled
Syntax
mc-ecmp-hashing-enabled [rebalance]
no mc-ecmp-hashing-enabled
Context
[Tree] (config>service>vprn>pim mc-ecmp-hashing-enabled)
Full Context
configure service vprn pim mc-ecmp-hashing-enabled
Description
This command enables hash-based multicast balancing of traffic over ECMP links and causes PIM joins to be distributed over the multiple ECMP paths based on a hash of S and G (and possibly next-hop IP address). When a link in the ECMP set is removed, the multicast flows that were using that link are redistributed over the remaining ECMP links using the same hash algorithm. When a link is added to the ECMP set new joins may be allocated to the new link based on the hash algorithm, but existing multicast flows using the other ECMP links stay on those links until they are pruned.
Hash-based multicast balancing is supported for both IPv4 and IPv6.
This command cannot be used together with the mc-ecmp-balance command. Using this command and the lag-usage-optimization command on mixed port speed LAGs is not recommended, because some groups may be forwarded incorrectly.
The no form of this command disables the hash-based multicast balancing of traffic over ECMP links.
The no form of this command means that the use of multiple ECMP paths if enabled at the config>router or config>service>vprn context is controlled by the existing implementation and CLI commands mc-ecmp-balance.
Default
no mc-ecmp-hashing-enabled
Parameters
- rebalance
-
Specifies to rebalance flows to newly added links immediately, instead of waiting until they are pruned.
Platforms
All
mc-ecmp-hashing-enabled
Syntax
[no] mc-ecmp-hashing-enabled [rebalance]
Context
[Tree] (config>router>pim mc-ecmp-hashing-enabled)
Full Context
configure router pim mc-ecmp-hashing-enabled
Description
This command enables hash-based multicast balancing of traffic over ECMP links and causes PIM joins to be distributed over the multiple ECMP paths based on a hash of S and G (and possibly next-hop IP address). When a link in the ECMP set is removed, the multicast flows that were using that link are redistributed over the remaining ECMP links using the same hash algorithm. When a link is added to the ECMP set new joins may be allocated to the new link based on the hash algorithm, but existing multicast flows using the other ECMP links stay on those links until they are pruned.
Hash-based multicast balancing is supported for both IPv4 and IPv6.
This command cannot be used together with the mc-ecmp-balance command. Using this command and the lag-usage-optimization command on mixed port speed LAGs is not recommended, because some groups may be forwarded incorrectly.
The no form of this command disables the hash-based multicast balancing of traffic over ECMP links.
Default
no mc-ecmp-hashing-enabled
Parameters
- rebalance
-
Specifies to rebalance flows to newly added links immediately, instead of waiting until they are pruned.
Platforms
All
mc-endpoint
mc-endpoint
Syntax
[no] mc-endpoint
Context
[Tree] (config>redundancy>multi-chassis>peer mc-endpoint)
Full Context
configure redundancy multi-chassis peer mc-endpoint
Description
This command specifies that the endpoint is multi-chassis. This value should be the same on both MC-EP peers for the pseudowires that must be part of the same group.
The no form of this command removes the endpoint from the MC-EP. Single chassis behavior applies.
Default
no mc-endpoint
Platforms
All
mc-endpoint
Syntax
mc-endpoint mc-ep-id
no mc-endpoint
Context
[Tree] (config>service>vpls>endpoint mc-endpoint)
Full Context
configure service vpls endpoint mc-endpoint
Description
This command specifies the identifier associated with the multi-chassis endpoint. This value should be the same on both MC-EP peers for the pseudowires that must be part of the same group.
The no form of this command removes the endpoint from the MC-EP. Single chassis behavior applies.
Default
no mc-endpoint
Parameters
- mc-ep-id
-
Specifies a multi-chassis endpoint ID
Platforms
All
mc-enh-load-balancing
mc-enh-load-balancing
Syntax
[no] mc-enh-load-balancing
Context
[Tree] (config>system>load-balancing mc-enh-load-balancing)
Full Context
configure system load-balancing mc-enh-load-balancing
Description
This command enables enhanced egress multicast load balancing behavior for Layer 3 multicast. When enabled, the router will spray the multicast traffic using as hash inputs from the packet based on lsr-load-balancing, l4-load-balancing and system-ip-load-balancing configurations. That is, an ingress LER or IP PE will spray traffic based on the IP hash criteria: SA/DA + optional Layer 4 port + optional system IP egress LER or LSR will spray traffic based on label or IP hash criteria outlined above or both based on configuration of lsr-load-balancing, l4-load-balancing, and system-ip-load-balancing.
The no form of the command preserves the default behavior for per flow hashing of multicast traffic.
Default
no mc-enh-load-balancing
Platforms
All
mc-ep-peer
mc-ep-peer
Syntax
mc-ep-peer name
mc-ep-peer ip-address
no mc-ep-peer
Context
[Tree] (config>service>vpls>endpoint>mc-ep mc-ep-peer)
Full Context
configure service vpls endpoint mc-endpoint mc-ep-peer
Description
This command adds multi-chassis endpoint object.
The no form of this command removes the multi-chassis endpoint object.
Default
no mc-ep-peer
Parameters
- name
-
Specifies the name of the multi-chassis endpoint peer
- ip-address
-
Specifies the IP address of multi-chassis endpoint peer
Platforms
All
mc-fr-profile-egress
mc-fr-profile-egress
Syntax
mc-fr-profile-egress profile-id [create]
no mc-fr-profile-egress profile-id
Context
[Tree] (config>qos mc-fr-profile-egress)
Full Context
configure qos mc-fr-profile-egress
Description
This command creates a profile for the user to configure the egress QoS parameters of an MLFR bundle or an FRF.12 UNI/NNI link. A maximum of 128 egress QoS profiles may be created on the system.
The no form of this command deletes the profile.
Parameters
- profile-id
-
Specifies the profile number.
- create
-
Required parameter when creating a multi-class Frame Relay egress profile.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
mc-fr-profile-egress
Syntax
mc-fr-profile-egress src-mc-fr-prof dst-mc-fr-prof [overwrite]
Context
[Tree] (config>qos>copy mc-fr-profile-egress)
Full Context
configure qos copy mc-fr-profile-egress
Description
This command copies an existing mc-fr-profile-egress profile ID to another multi-class frame-relay egress profile ID. The copy command is a configuration level maintenance tool used to create new entries using an existing profile ID. If overwrite is not specified, an error occurs if the destination profile ID exists.
Parameters
- src-mc-fr-prof
-
Specifies the existing source mc-fr-profile-egress profile ID from which the copy command attempts to copy.
- src-mc-fr-prof
-
Specifies the destination mc-fr-profile-egress profile ID to which the copy command attempts to copy.
- overwrite
-
Use this parameter when the mc-fr-profile-egress dst-mc-fr-prof already exists. If it does, everything in the existing destination mc-fr-profile-egress dst-mc-fr-prof is completely overwritten with the contents of the mc-fr-profile-egress src-mc-fr-prof. The overwrite parameter must be specified or else the following error message is returned:
MINOR: CLI use {overwrite}; destination mc-fr-egress-profile "4" exists.If overwrite is specified, the function of copying from source to destination occurs in a ‟break before make” manner and therefore should be handled with care.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
mc-fr-profile-ingress
mc-fr-profile-ingress
Syntax
mc-fr-profile-ingress profile-id [create]
no mc-fr-profile-ingress profile-id
Context
[Tree] (config>qos mc-fr-profile-ingress)
Full Context
configure qos mc-fr-profile-ingress
Description
This command creates a profile for the user to configure the ingress QoS parameters of a Multi-Link Frame Relay (MLFR) bundle. A maximum of 128 ingress QoS profiles may be created on the system.
The no form of this command deletes the profile.
Parameters
- profile-id
-
Specifies the profile number.
- create
-
Required keyword used to create a multi-class Frame Relay ingress profile.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
mc-handover
mc-handover
Syntax
mc-handover percentage
no mc-handover
Context
[Tree] (config>mcast-mgmt>mcast-info-plcy>video-policy>video-if>sd mc-handover)
[Tree] (config>mcast-mgmt>mcast-info-plcy>video-policy>video-if>hd mc-handover)
[Tree] (config>mcast-mgmt>mcast-info-plcy>video-policy>video-if>pip mc-handover)
Full Context
configure mcast-management multicast-info-policy video-policy video-interface sd mc-handover
configure mcast-management multicast-info-policy video-policy video-interface hd mc-handover
configure mcast-management multicast-info-policy video-policy video-interface pip mc-handover
Description
This command sets the rate at which the Fast Channel Change (FCC) server will send unicast data to the FCC client during the handover to the multicast stream.
The no form of the command returns the parameter to the default value.
Default
mc-handover 25
Parameters
- percentage
-
Specifies the percentage of nominal bandwidth.
Platforms
7450 ESS, 7750 SR-1, 7750 SR-7/12/12e, 7750 SR-1s, 7750 SR-2s, 7750 SR-7s, 7750 SR-14s
mc-ipsec
mc-ipsec
Syntax
[no] mc-ipsec
Context
[Tree] (config>redundancy>multi-chassis>peer mc-ipsec)
Full Context
configure redundancy multi-chassis peer mc-ipsec
Description
Commands in this context configure multi-chassis peer parameters.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
mc-ipsec-non-forwarding
mc-ipsec-non-forwarding
Syntax
[no] mc-ipsec-non-forwarding tunnel-grp-id
Context
[Tree] (config>vrrp>policy>priority-event mc-ipsec-non-forwarding)
Full Context
configure vrrp policy priority-event mc-ipsec-non-forwarding
Description
This command configures an instance of a multi-chassis IPsec tunnel-group Priority Event used to override the base priority value of a VRRP virtual router instance depending on the operational state of the event.
Parameters
- tunnel-grp-id
-
Identifies the multi-chassis IPsec tunnel group whose non-forwarding state is monitored by this priority control event.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
mc-lag
mc-lag
Syntax
[no] mc-lag
Context
[Tree] (config>redundancy>multi-chassis>peer mc-lag)
Full Context
configure redundancy multi-chassis peer mc-lag
Description
Commands in this context configure multi-chassis LAG operations and related parameters.
The no form of this command administratively disables multi-chassis LAG. MC-LAG can be issued only when mc-lag is shutdown.
Default
no mc-lag
Platforms
All
mc-lag
Syntax
mc-lag
Context
[Tree] (config>eth-cfm>redundancy mc-lag)
Full Context
configure eth-cfm redundancy mc-lag
Description
Commands in this context configure the MC-LAG specific ETH-CFM redundancy parameters.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
mc-maximum-routes
mc-maximum-routes
Syntax
mc-maximum-routes number [log-only] [ threshold threshold]
Context
[Tree] (config>service>vprn mc-maximum-routes)
Full Context
configure service vprn mc-maximum-routes
Description
This command specifies the maximum number of multicast routes that can be held in the form of this command in a VPN routing or forwarding (VRF) context. When this limit is reached, a log and SNMP trap are sent. If the log-only parameter is not specified and the maximum-routes value is set below the existing number of routes in a VRF, then no new joins are processed.
The no form of this command disables the limit of multicast routes within a VRF context. Issue the no form of this command only when the VPRN instance is shutdown.
Default
no mc-maximum-routes
Parameters
- number
-
Specifies the maximum number of routes to be held in a VRF context.
- log-only
-
Specifies that if the maximum limit is reached, only log the event. log-only does not disable the learning of new routes.
- threshold
-
Specifies the percentage at which a warning log message and SNMP trap should be sent.
Platforms
All
mc-maximum-routes
Syntax
mc-maximum-routes number [log-only] [ threshold threshold]
no mc-maximum-routes
Context
[Tree] (config>router mc-maximum-routes)
Full Context
configure router mc-maximum-routes
Description
This command specifies the maximum number of multicast routes that can be held within a VPN routing/forwarding (VRF) context. When this limit is reached, a log and SNMP trap are sent. If the log-only parameter is not specified and the maximum-routes value is set below the existing number of routes in a VRF, then no new joins will be processed.
The no form of this command disables the limit of multicast routes within a VRF context. Issue the no form of this command only when the VPRN instance is shutdown.
Default
no mc-maximum-routes
Parameters
- number
-
Specifies the maximum number of routes to be held in a VRF context.
- log-only
-
Specifies that if the maximum limit is reached, only log the event. log-only does not disable the learning of new routes.
- threshold
-
Specifies the percentage at which a warning log message and SNMP trap should be sent.
Platforms
All
mc-ring
mc-ring
Syntax
mc-ring
Context
[Tree] (config>redundancy>multi-chassis>peer mc-ring)
Full Context
configure redundancy multi-chassis peer mc-ring
Description
Commands in this context configure the multi-chassis ring parameters.
The no form of this command reverts to the default.
Default
mc-ring
Platforms
All
mc-ring
Syntax
[no] mc-ring
Context
[Tree] (config>redundancy>multi-chassis>peer>sync mc-ring)
Full Context
configure redundancy multi-chassis peer sync mc-ring
Description
This command specifies whether multi-chassis ring information shoud be synchronized with the multi-chassis peer.
Default
no mc-ring
Platforms
All
mcac
mcac
Syntax
mcac
Context
[Tree] (config>service>vpls>mesh-sdp>snooping mcac)
[Tree] (config>service>pw-template>igmp-snooping mcac)
Full Context
configure service vpls mesh-sdp snooping mcac
configure service pw-template igmp-snooping mcac
Description
Commands in this context configure multicast CAC policy parameters and constraints for this interface.
Platforms
All
mcac
Syntax
mcac
Context
[Tree] (config>subscr-mgmt>msap-policy>vpls-only>igmp-snp mcac)
Full Context
configure subscriber-mgmt msap-policy vpls-only-sap-parameters igmp-snooping mcac
Description
Commands in this context configure multicast CAC parameters.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
mcac
Syntax
mcac
Context
[Tree] (config>service>vpls>mesh-sdp>igmp-snooping mcac)
[Tree] (config>service>vpls>spoke-sdp>igmp-snooping mcac)
[Tree] (config>service>vpls>sap>mld-snooping mcac)
[Tree] (config>service>vpls>sap>igmp-snooping mcac)
[Tree] (config>service>vpls>spoke-sdp>mld-snooping mcac)
[Tree] (config>service>vpls>mesh-sdp>mld-snooping mcac)
Full Context
configure service vpls mesh-sdp igmp-snooping mcac
configure service vpls spoke-sdp igmp-snooping mcac
configure service vpls sap mld-snooping mcac
configure service vpls sap igmp-snooping mcac
configure service vpls spoke-sdp mld-snooping mcac
configure service vpls mesh-sdp mld-snooping mcac
Description
This command configures multicast CAC policy and constraints for this interface.
Platforms
All
mcac
Syntax
mcac
Context
[Tree] (config>service>vprn>mld>if mcac)
[Tree] (config>service>vprn>igmp>grp-if mcac)
[Tree] (config>service>vprn>mld>grp-if mcac)
[Tree] (config>service>vprn>pim>if mcac)
[Tree] (config>service>vprn>igmp>if mcac)
Full Context
configure service vprn mld interface mcac
configure service vprn igmp group-interface mcac
configure service vprn mld group-interface mcac
configure service vprn pim interface mcac
configure service vprn igmp interface mcac
Description
This command configures multicast CAC policy and constraints for this interface.
Platforms
All
- configure service vprn igmp interface mcac
- configure service vprn mld interface mcac
- configure service vprn pim interface mcac
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
- configure service vprn mld group-interface mcac
- configure service vprn igmp group-interface mcac
mcac
Syntax
mcac
Context
[Tree] (config>router mcac)
[Tree] (config>router>pim>if mcac)
[Tree] (config>router>igmp>group-interface mcac)
[Tree] (config>router>mld>interface mcac)
[Tree] (config>router>igmp>interface mcac)
[Tree] (config>router>mld>group-interface mcac)
Full Context
configure router mcac
configure router pim interface mcac
configure router igmp group-interface mcac
configure router mld interface mcac
configure router igmp interface mcac
configure router mld group-interface mcac
Description
Commands in this context configure multicast CAC parameters.
Platforms
All
- configure router pim interface mcac
- configure router mld interface mcac
- configure router igmp interface mcac
- configure router mcac
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
- configure router mld group-interface mcac
- configure router igmp group-interface mcac
mcast-capacity
mcast-capacity
Syntax
mcast-capacity primary-percentage secondary secondary-percentage
no mcast-capacity
Context
[Tree] (config>mcast-mgmt>chassis-level>plane-capacity mcast-capacity)
Full Context
configure mcast-management chassis-level per-mcast-plane-capacity mcast-capacity
Description
This command configures the primary and secondary multicast plane capacities used when the full complement of possible switch fabrics in the system is not up (at least one possible switch fabric is not provisioned or is down). The rates are defined as a percentage of the total multicast plane capacity which is configured using the total-capacity command.
The no form of this command reverts to the default values.
Default
mcast-capacity 87.50 secondary 87.50
Parameters
- primary-percentage
-
Specifies the percentage of the total multicast plane capacity to be used for primary multicast planes.
- secondary-percentage
-
Specifies the percentage of the total multicast plane capacity to be used for secondary multicast planes.
Platforms
7450 ESS, 7750 SR-1x-48D, 7750 SR-1x-92S, 7750 SR-7/12/12e, 7750 SR-s, 7950 XRS, VSR
mcast-ipv4
mcast-ipv4
Syntax
[no] mcast-ipv4
Context
[Tree] (config>cflowd>collector>export-filter>family mcast-ipv4)
Full Context
configure cflowd collector export-filter family mcast-ipv4
Description
This command filters multicast IPv4 flow data from being sent to the associated collector.
The no form of this command removes the filter, allowing multicast IPv4 flow data to be sent to the associated collector.
Default
no mcast-ipv4
Platforms
All
mcast-ipv6
mcast-ipv6
Syntax
[no] mcast-ipv6
Context
[Tree] (config>cflowd>collector>export-filter>family mcast-ipv6)
Full Context
configure cflowd collector export-filter family mcast-ipv6
Description
This command filters multicast IPv6 flow data from being sent to the associated collector.
The no form of this command removes the filter, allowing multicast IPv6 flow data to be sent to the associated collector.
Default
no mcast-ipv6
Platforms
All
mcast-ipv6-snooping-scope
mcast-ipv6-snooping-scope
Syntax
mcast-ipv6-snooping-scope {mac-based | sg-based}
no mcast-ipv6-snooping-scope
Context
[Tree] (config>service>vpls mcast-ipv6-snooping-scope)
Full Context
configure service vpls mcast-ipv6-snooping-scope
Description
This command specifies the forwarding scope used for IPv6 multicast traffic when PIM snooping for IPv6 is enabled.
By default, the scope is mac-based; IPv6 snooped multicast traffic is forwarded is based on the low-order 32 bits of the destination IPv6 address.
When the scope is configured as sg-based, the IPv6 snooped multicast traffic is forwarded based on both its full source (if specified in the join) and destination IPv6 address. SG-based forwarding is only supported on FP3- (or higher) based line cards.
PIM snooping for IPv6 must be disabled to change the forwarding mode within a VPLS service between mac-based and sg-based.
The no form of this command configures the router to use the default value.
Default
mcast-ipv6-snooping-scope mac-based
Parameters
- mac-based
-
Sets forwarding for PIM-snooped IPv6 multicast traffic based on the low-order 32 bits of its destination IPv6 address.
- sg-based
-
Sets forwarding for PIM-snooped IPv6 multicast traffic based on its full source (if specified in the join) and destination IPv6 address.
Platforms
All
mcast-management
mcast-management
Syntax
mcast-management
Context
[Tree] (config mcast-management)
Full Context
configure mcast-management
Description
Commands in this context configure multicast management parameters. The mcast-management CLI node contains the bandwidth-policy and multicast-info-policy definitions. The bandwidth-policy is used to manage the ingress multicast paths into the switch fabric. The multicast-info-policy defines how each multicast channel is handled by the system. The policy may be used by the ingress multicast bandwidth manager, the ECMP path manager and the egress multicast CAC manager.
The mcast-management node always exists and contains the default bandwidth-policy and the default multicast-info-policy. Enter the mcast-management node when editing, deleting or creating a bandwidth policy or multicast info policy. The default bandwidth policy and multicast-info-policy cannot be edited or deleted.
A chassis-level node within multicast-management is used to control the switch fabric multicast planes replication limits. The switch fabric multicast planes are the individual multicast spatial replication contexts available in the system.
Platforms
All
mcast-path-management
mcast-path-management
Syntax
mcast-path-management
Context
[Tree] (config>card>fp>ingress mcast-path-management)
Full Context
configure card fp ingress mcast-path-management
Description
This CLI node contains the forwarding plane settings for ingress multicast path management. Enter the node to configure the bandwidth-policy and the administrative state of ingress multicast path management.
Platforms
7450 ESS, 7750 SR-1x-48D, 7750 SR-1x-92S, 7750 SR-7/12/12e, 7750 SR-s, 7950 XRS, VSR
mcast-pool
mcast-pool
Syntax
mcast-pool percent-of-total percent-of-buffers resv-cbs percent-of-pool slope-policy policy-name
no mcast-pool
Context
[Tree] (config>mcast-mgmt>bw-plcy mcast-pool)
Full Context
configure mcast-management bandwidth-policy mcast-pool
Description
This command configures the ingress multicast path management buffer pool. The pool is used by the primary and secondary path queues through which all ingress managed multicast traffic must flow. The parameters may be used to configure the size of the pool relative to the total ingress buffer space, the amount of reserved CBS buffers within the pool and the slope policy used to manage early congestion detection functions in the shared portion of the pool.
Care should be taken when managing the buffer pool space as changes to the systems buffer pool behavior can have negative effects on multicast and unicast forwarding.
Sizing the Pool
The percent-of-total command defines how much of the total ingress buffer pool space for the MDA is dedicated for multicast channels managed by the bandwidth policy. Since multicast typically has a higher scheduling priority through the switch fabric, the buffer pool does not need to be large. By default, the system reserves 10% of the buffers on the ingress side of the MDA once multicast path management is enabled.
Reserved CBS Portion of the Pool
The multicast pool is divided into two portions; reserved and shared. The reserved portion is used by the multicast path queues until they cross there individual CBS thresholds. Since the CBS thresholds are configured as percentages and the percentages can oversubscribe the reserved portion of the pool, it is possible for some of the queues CBS buffer allocation to be met by the shared portion of the pool. By default, 50% of the pool is defined as reserved. This may be changed using the resv-cbs percentage parameter.
Shared Portion WRED Slopes
The shared portion of the buffer pool is used by queues that have crossed over their CBS thresholds. Since the total MBS values for the multicast path queues may oversubscribe the pool size, a buffer congestion control mechanism is supported within the pool in the form of two WRED slopes. The slope-policy parameter defines how the slopes are configured and whether they are activated. Each packet entering a path queue is defined as high or low priority within the queue based on the channel’s preference value relative to the cong-priority-threshold command. When getting a shared buffer of a high priority packet, the high WRED slope is used. Low priority packets use the low WRED slope.
The no form of this command returns the managed multicast path pool to its default settings.
Parameters
- percent-of-buffers
-
Specifies the percentage of ingress buffers that is allocated to the multicast pool.
- percent-of-pool
-
Specifies the percentage of the pool that is reserved for multicast path queues within their CBS threshold.
- slope-policy-name
-
Specifies the WRED slopes within the multicast pool. Once a slope policy is associated with a buffer pool, it cannot be deleted.
Platforms
7450 ESS, 7750 SR-1x-48D, 7750 SR-1x-92S, 7750 SR-7/12/12e, 7750 SR-s, 7950 XRS, VSR
mcast-reporting
mcast-reporting
Syntax
[no] mcast-reporting
Context
[Tree] (config>subscr-mgmt>igmp-policy mcast-reporting)
Full Context
configure subscriber-mgmt igmp-policy mcast-reporting
Description
Commands in this context configure mcast reporting.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
mcast-reporting-dest
mcast-reporting-dest
Syntax
mcast-reporting-dest dest-name [create]
no mcast-reporting-dest dest-name
Context
[Tree] (config>mcast-management mcast-reporting-dest)
Full Context
configure mcast-management mcast-reporting-dest
Description
This command creates a multicast reporting destination hierarchy in CLI under which parameters defining this destination can be specified. The destination refers to an external node that collects and analyze IGMP events.
The multicast reporting destination is associated with a name that each subscriber can reference to send the IGMP related events.
It can be also referenced in the host tracking policy in case that IGMP events are related to the host tracking feature.
The no form of this command removes the destination name from the configuration.
Parameters
- dest-name
-
Specifies the multicast reporting destination name.
Platforms
All
mcast-reporting-dest
Syntax
[no] mcast-reporting-dest [dest-name]
Context
[Tree] (debug>mcast-mgmt mcast-reporting-dest)
Full Context
debug mcast-management mcast-reporting-dest
Description
This command debugs multicast path management reporting destinations and applies only to the 7750 SR.
Platforms
All
mcast-reporting-dest
Syntax
mcast-reporting-dest dest-name
no mcast-reporting-dest
Context
[Tree] (config>subscr-mgmt>igmp-policy>mcast-reporting mcast-reporting-dest)
Full Context
configure subscriber-mgmt igmp-policy mcast-reporting mcast-reporting-dest
Description
This command references the multicast reporting destination to which IGMP-related events are exported. The multicast-reporting-destination is referenced within the IGMP policy for the subscriber.
The no form of this command reverts to the default value.
Parameters
- dest-name
-
Specifies the name of the multicast reporting destination, up to 32 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
mcast-tunneling
mcast-tunneling
Syntax
[no] mcast-tunneling
Context
[Tree] (config>router>ldp>targ-session>peer-template mcast-tunneling)
[Tree] (config>router>ldp>targ-session>peer mcast-tunneling)
Full Context
configure router ldp targeted-session peer-template mcast-tunneling
configure router ldp targeted-session peer mcast-tunneling
Description
At the downstream router, the FEC is resolved and the result of the resolution is a Label Mapping advertisement to the upstream peer.
At the upstream router, if the RSVP LSP does not exist to the peer address, the upstream router does not use the T-LDP session for FEC resolution.
The no form of this command reverts to the default value.
Default
no mcast-tunneling
Platforms
All
mcast-upstream-asbr-frr
mcast-upstream-asbr-frr
Syntax
[no] mcast-upstream-asbr-frr
Context
[Tree] (config>router>ldp mcast-upstream-asbr-frr)
Full Context
configure router ldp mcast-upstream-asbr-frr
Description
This command enables ASBR MoFRR.
When ASBR MoFRR is enabled, the local leaf will perform MoFRR for multiple ASBRs; for example, if there are two ASBRs, the local leaf will select one ASBR as the primary and another ASBR as the backup.
If the mcast-upstream-frr command is enabled, disabling ASBR MoFRR will only allow IGP MoFRR in the local AS; for example, a single ASBR will be selected and two separate, disjointed paths will be selected as the primary and backup LSPs from the local leaf to ASBR.
If the mcast-upstream-frr command is disabled, disabling ASBR MoFRR will disable MoFRR entirely.
The no form of the command disables ASBR MoFRR.
Default
no mcast-upstream-asbr-frr
Platforms
All
mcast-upstream-frr
mcast-upstream-frr
Syntax
[no] mcast-upstream-frr
Context
[Tree] (config>router>ldp mcast-upstream-frr)
Full Context
configure router ldp mcast-upstream-frr
Description
This command enables the mLDP fast upstream switchover feature.
When this command is enabled and LDP is resolving a mLDP FEC received from a downstream LSR, it checks if an ECMP next-hop or a LFA next-hop exist to the root LSR node. If LDP finds one, it programs a primary ILM on the interface corresponding to the primary next-hop and a backup ILM on the interface corresponding to the ECMP or LFA next-hop. LDP then sends the corresponding labels to both upstream LSR nodes. In normal operation, the primary ILM accepts packets while the backup ILM drops them. If the interface or the upstream LSR of the primary ILM goes down causing the LDP session to go down, the backup ILM will then start accepting packets.
In order to make use of the ECMP next-hop, the user must configure the ecmp value in the system to at least 2 using the following command:
configure router ecmp
In order to make use of the LFA next-hop, the user must enable LFA using the following commands:
configure router isis loopfree-alternates
configure router ospf loopfree-alternates
Enabling IP FRR or LDP FRR features is not strictly required since LDP only needs to know where the alternate next-hop to the root LSR is to be able to send the Label Mapping message to program the backup ILM at the initial signaling of the tree. Thus enabling the LFA option is sufficient. If however, unicast IP and LDP prefixes need to be protected, then these features and the mLDP fast upstream switchover can be enabled concurrently.
The mLDP FRR fast switchover relies on the fast detection of loss of **LDP session** to the upstream peer to which the primary ILM label had been advertised. We strongly recommended to perform the following:
-
Enable BFD on all LDP interfaces to upstream LSR nodes. When BFD detects the loss of the last adjacency to the upstream LSR, it will bring down immediately the LDP session which will cause the IOM to activate the backup ILM.
-
If there is a concurrent TLDP adjacency to the same upstream LSR node, enable BFD on the T-LDP peer in addition to enabling it on the interface.
-
Enable the ldp-sync-timer option on all interfaces to the upstream LSR nodes. If an LDP session to the upstream LSR to which the primary ILM is resolved goes down for any other reason than a failure of the interface or of the upstream LSR, routing and LDP will go out of sync. This means the backup ILM will remain activated until the next time SPF is rerun by IGP. By enabling IGP-LDP synchronization feature, the advertised link metric will be changed to max value as soon as the LDP session goes down. This in turn will trigger an SPF and LDP will likely download a new set of primary and backup ILMs.
The no form of this command disables the fast upstream switchover for mLDP FECs.
Default
no mcast-upstream-frr
Platforms
All
mcast-vpn-ipv4
mcast-vpn-ipv4
Syntax
mcast-vpn-ipv4 send send-limit receive [none]
mcast-vpn-ipv4 send send-limit
no mcast-vpn-ipv4
Context
[Tree] (config>router>bgp>group>add-paths mcast-vpn-ipv4)
[Tree] (config>router>bgp>group>neighbor>add-paths mcast-vpn-ipv4)
[Tree] (config>router>bgp>add-paths mcast-vpn-ipv4)
Full Context
configure router bgp group add-paths mcast-vpn-ipv4
configure router bgp group neighbor add-paths mcast-vpn-ipv4
configure router bgp add-paths mcast-vpn-ipv4
Description
This command configures the add-paths capability for multicast IPv4 VPN routes. By default, add-paths is not enabled for multicast IPv4 VPN routes.
The maximum number of multicast paths per IPv4 VPN prefix to send is the configured send-limit, which is a mandatory parameter. The capability to receive multiple multicast paths per prefix from a peer is configurable using the receive keyword, which is optional. If the receive keyword is not included in the command, receive capability is enabled by default. The none option disables the receive capability.
The no form of this command disables add-paths support for multicast IPv4 VPN routes, causing sessions established using add-paths for multicast IPv4 VPN to go down and come back up without the add-paths capability.
Default
no mcast-vpn-ipv4
Parameters
- send-limit
-
Specifies the maximum number of paths per multicast IPv4 VPN prefix that are allowed to be advertised to add-paths peers. The actual number of advertised routes may be less. If the value is none, the router does not negotiate the send capability with respect to multicast IPv4 VPN AFI/SAFI.
- receive
-
Specifies that the router negotiates to receive multiple multicast routes per IPv4 VPN prefix.
- none
-
Specifies that the router does not negotiate to receive multiple multicast routes per IPv4 VPN prefix.
Platforms
All
mcast-vpn-ipv6
mcast-vpn-ipv6
Syntax
mcast-vpn-ipv6 send send-limit receive [none]
mcast-vpn-ipv6 send send-limit
no mcast-vpn-ipv6
Context
[Tree] (config>router>bgp>add-paths mcast-vpn-ipv6)
[Tree] (config>router>bgp>group>add-paths mcast-vpn-ipv6)
[Tree] (config>router>bgp>group>neighbor>add-paths mcast-vpn-ipv6)
Full Context
configure router bgp add-paths mcast-vpn-ipv6
configure router bgp group add-paths mcast-vpn-ipv6
configure router bgp group neighbor add-paths mcast-vpn-ipv6
Description
This command configures the add-paths capability for multicast IPv6 VPN routes. By default, add-paths is not enabled for multicast IPv6 VPN routes.
The maximum number of multicast paths per IPv6 VPN prefix to send is the configured send-limit, which is a mandatory parameter. The capability to receive multiple multicast paths per prefix from a peer is configurable using the receive keyword, which is optional. If the receive keyword is not included in the command, receive capability is enabled by default. The none option disables the receive capability.
The no form of this command disables add-paths support for multicast IPv6 VPN routes, causing sessions established using add-paths for multicast IPv6 VPN to go down and come back up without the add-paths capability.
Default
no mcast-vpn-ipv6
Parameters
- send-limit
-
Specifies the maximum number of paths per multicast IPv6 VPN prefix that are allowed to be advertised to add-paths peers. The actual number of advertised routes may be less. If the value is none, the router does not negotiate the send capability with respect to multicast IPv6 VPN AFI/SAFI.
- receive
-
Specifies that the router negotiates to receive multiple multicast routes per IPv6 VPN prefix.
- none
-
Specifies that the router does not negotiate to receive multiple multicast routes per IPv6 VPN prefix.
Platforms
All
mcc-mnc-prefix
mcc-mnc-prefix
Syntax
mcc-mnc-prefix imsi-prefix-string
no mcc-mnc-prefix
Context
[Tree] (config>app-assure>group>gtp>gtp-fltr>imsi-apn-fltr>entry mcc-mnc-prefix)
Full Context
configure application-assurance group gtp gtp-filter imsi-apn-filter entry mcc-mnc-prefix
Description
This command configures a matching condition for the IMSI (MCC-MNC) prefix.
Parameters
- imsi-prefix-string
-
Specifies a string of 1 to 6 decimal digits representing the IMSI prefix to be matched against the IMSI IE of the packet, or the special value ANY_IMSI to indicate that an IMSI IE must be present as a matching condition regardless of the IMSI IE value.
If no MCC-MNC prefix is specified, the entry will match GTP packets that have an IMSI IE containing any value.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
mcr-default-gtw
mcr-default-gtw
Syntax
mcr-default-gtw
Context
[Tree] (config>service>vpls mcr-default-gtw)
Full Context
configure service vpls mcr-default-gtw
Description
Commands in this context configure the default gateway information when using Dual Homing in L2-TPSDA. The IP and MAC address of the default gateway used for subscribers on an L2 MC-Ring are configured in this context. After a ring heals or fails, the system sends out a gratuitous ARP on an active ring SAP in order to attract traffic from subscribers on the ring with connectivity to that SAP.
Platforms
All
mcs
mcs
Syntax
mcs [detail]
no mcs
Context
[Tree] (debug>service>id>pim-snooping mcs)
Full Context
debug service id pim-snooping mcs
Description
This command enables or disables debugging for PIM snooping multi-chassis synchronization.
Parameters
- detail
-
Provides detailed debugging information
Platforms
All
mcs
Syntax
mcs [ip-int-name]
no mcs
Context
[Tree] (debug>router>igmp mcs)
Full Context
debug router igmp mcs
Description
This command enables debugging for IGMP multicast servers (MCS).
The no form of the command disables the IGMP interface debugging for the specifies interface name.
Parameters
- ip-int-name
-
Debugs the information associated with the specified IP interface name.
Platforms
All
mcs-interval
mcs-interval
Syntax
mcs-interval minutes
mcs-interval use-update-interval
no mcs-interval
Context
[Tree] (config>subscr-mgmt>acct-plcy mcs-interval)
Full Context
configure subscriber-mgmt radius-accounting-policy mcs-interval
Description
This command specifies the interval at which the active BNG in a dual-homed deployment synchronizes subscriber accounting data using MCS to the standby BNG. The MCS interval is a statically configured value or is equal to the configured RADIUS accounting update-interval.
The no form of the command reverts to the default value.
Default
no mcs-interval
Parameters
- minutes
-
Specifies the interval, in minutes, at which accounting data of the subscriber is synchronized.
- use-update-interval
-
Synchronizes subscriber accounting data at the same time as the RADIUS interim-update. For this, the configured update-interval in the RADIUS accounting policy is used, ignoring RADIUS overrides.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
mcs-peer
mcs-peer
Syntax
mcs-peer ip-address sync-tag [sync-tag]
no mcs-peer
Context
[Tree] (config>python>py-pol>cache mcs-peer)
Full Context
configure python python-policy cache mcs-peer
Description
This command specifies the MCS peer’s address and sync-tag for syncing the cached entries of the python-policy. The sync-tag must be match on both chassis.
The no form of this command reverts to the default.
Parameters
- ip-address
-
Specifies the IPv4 address of the MCS peer.
- sync-tag
-
Specifies the tag for sync, up to 32 characters.
Platforms
All
mcs-peer
Syntax
mcs-peer ip-address sync-tag name
no mcs-peer
Context
[Tree] (config>aaa>diam-peer-plcy>proxy mcs-peer)
Full Context
configure aaa diameter-peer-policy proxy mcs-peer
Description
This command configures the IP address and the synchronization tag for the multi-chassis synchronization (MCS) peer.
This command is applicable only to legacy implementations of Diameter base in SR OS.
The no form of this command reverts to the default.
Parameters
- ip-address
-
Specifies the IPv4 or IPv6 address of the MCS peer.
- name
-
Specifies the sync tag name, up to 32 characters. The name must match on both nodes for the pair of redundant diameter proxies.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
md
md
Syntax
md file-url
Context
[Tree] (file md)
Full Context
file md
Description
This command creates a new directory in a file system.
Directories can only be created one level at a time.
Parameters
- file-url
-
Specifies the directory name to be created.
Platforms
All
md-auto-id
md-auto-id
Syntax
md-auto-id
Context
[Tree] (config>eth-cfm md-auto-id)
Full Context
configure eth-cfm md-auto-id
Description
This command automatically assigns numerical index values for ma-index and md-index in model-driven management interfaces.
Classic management interfaces use a numerical index as the primary key for ETH-CFM domains and associations. In model-driven interfaces, domains and associations use string names as keys. The domain and association can optionally be created without having to explicitly select and specify a numerical index in model-driven interfaces. In this case, SR OS assigns an index using the configured index range.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
md-auto-id
Syntax
md-auto-id
Context
[Tree] (config>qos md-auto-id)
Full Context
configure qos md-auto-id
Description
This command automatically assigns numerical ID values for QoS policies in model-driven (MD) management interfaces.
Classic management interfaces use a numerical policy ID as the primary key for sap-ingress, sap-egress, and network QoS policies. In model-driven interfaces, SAP and network policies use string names as keys. The SAP and network policies can optionally be created in MD interfaces without having to explicitly select and specify a numerical policy ID. In this case, SR OS assigns an ID using the configured ID range.
Platforms
All
md-auto-id
Syntax
md-auto-id
Context
[Tree] (config>filter md-auto-id)
Full Context
configure filter md-auto-id
Description
This command automatically assigns numerical ID values for filter policies in model-driven management interfaces.
Classic management interfaces use a numerical filter ID as the primary key for IP filters, IPv6 filters, and MAC filters. In model-driven interfaces, IP, IPv6, and MAC filters use string names as keys. The filters can optionally be created in MD interfaces without having to explicitly select and specify a numerical filter ID. In this case, SR OS assigns an ID using the configured ID range.
Platforms
All
md-auto-id
Syntax
md-auto-id
Context
[Tree] (config>service md-auto-id)
Full Context
configure service md-auto-id
Description
This command automatically assigns numerical ID values for services, customers, and PW templates in model-driven (MD) management interfaces.
Classic management interfaces use a numerical service ID, customer ID, and PW template ID as the primary key for services, customers, and PW templates. In model-driven interfaces, services, customers, and PW templates use string names as keys. The services, customers, and PW templates can optionally be created in MD interfaces without having to explicitly select and specify a numerical ID. In this case, SR OS assigns an ID using the configured ID range.
Platforms
All
md-cli
md-cli
Syntax
md-cli
Context
[Tree] (config>system>management-interface>cli md-cli)
Full Context
configure system management-interface cli md-cli
Description
Commands in this context configure the MD-CLI management interface.
Platforms
All
md-cli
Syntax
md-cli
Context
[Tree] (config>system>security>management-interface md-cli)
Full Context
configure system security management-interface md-cli
Description
Commands in this context configure hash-control for the MD-CLI interface.
Platforms
All
md-cli-session
md-cli-session
Syntax
md-cli-session {permit | deny}
Context
[Tree] (config>system>security>profile>grpc>rpc-authorization md-cli-session)
Full Context
configure system security profile grpc rpc-authorization md-cli-session
Description
This command configures the use of the MdCli Session RPC for the user profile.
The no form of this command reverts to the default value.
Default
md-cli-session permit
Parameters
- deny
-
Specifies that the use of MdCli Session RPC is denied.
- permit
-
Specifies that the use of MdCli Session RPC is permitted.
Platforms
All
md-index-range
md-index-range
Syntax
md-index-range start md-index end md-index
no md-index-range
Context
[Tree] (config>eth-cfm>md-auto-id md-index-range)
Full Context
configure eth-cfm md-auto-id md-index-range
Description
This command specifies the range of indexes used by SR OS to automatically assign an index to ETH-CFM domains that are created in model-driven interfaces without an index explicitly specified by the user or client.
A domain created with an explicitly-specified index cannot use an index in this range. In classic CLI and SNMP, the ID range cannot be changed while objects exist inside the previous or new range. In MD interfaces, the range can be changed, which causes any previously existing objects in the previous ID range to be deleted and re-created using a new ID in the new range.
The no form of this command removes the range values.
See the md-auto-id command for further details.
Parameters
- start md-index
-
Specifies the lower value of the index range. The value must be less than or equal to the end value.
- end md-index
-
Specifies the upper value of the index range. The value must be greater than or equal to the start value.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
md-interfaces
md-interfaces
Syntax
[no] md-interfaces
Context
[Tree] (config>system>security>management-interface>output-authorization md-interfaces)
Full Context
configure system security management-interface output-authorization md-interfaces
Description
This command controls output authorization of commands or RPCs for model-driven interfaces that display configuration or state.
When enabled, output authorization is performed for the following commands:
-
MD-CLI info and compare commands
-
NETCONF <get> and <get-config> RPCs
-
gNMI Get RPC
When disabled, output authorization is not performed, which may significantly decrease the system response time by reducing command authorization requests, especially when remote AAA servers are used. Input to edit configuration is always authorized based on the AAA configuration.
By default, authorization checks are performed for configuration and state output.
The no form of this command disables authorization checks, allowing the output to be displayed immediately.
Default
md-interfaces
Platforms
All
md5-salt
md5-salt
Syntax
[no] md5-salt string
Context
[Tree] (config>app-assure>group>http-enrich>field md5-salt)
Full Context
configure application-assurance group http-enrich field md5-salt
Description
This command configures an MD5 salt string. The configured string is appended to the parameter before performing MD5 hashing of the field.
The no form of this command removes the configuration of the MD5 salt string.
Default
no md5-salt
Parameters
- string
-
Specifies the MD5 string, up to 16 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
mda
mda
Syntax
[no] mda mda-id
Context
[Tree] (config>isa>wlan-gw-group mda)
Full Context
configure isa wlan-gw-group mda
Description
This command enables an ISA for WLAN-GW functionality.
The no form of this command removes the ISA from the WLAN-GW configuration.
Parameters
- mda-id
-
Indicates the IOM and MDA slot in format slot/mda.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s
mda
Syntax
[no] mda mda-slot
Context
[Tree] (config>card mda)
Full Context
configure card mda
Description
This mandatory command enables access to a card’s MDA context. In SR OS, MDAs cover MDA and XMA.
Parameters
- mda-slot
-
Specifies the MDA slot number to be configured. Slots are numbered 1 and 2. On vertically oriented slots, the top MDA slot is number 1, and the bottom MDA slot is number 2. On horizontally oriented slots, the left MDA is number 1, and the right MDA slot is number 2.
Platforms
All
mda
Syntax
[no] mda mda-slot
Context
[Tree] (config>card>xiom mda)
Full Context
configure card xiom mda
Description
Configures an MDA-s in one of the slots of an XIOM.
Parameters
- mda-slot
-
Specifies the MDA-s slot number.
Platforms
7750 SR-1s, 7750 SR-2s, 7750 SR-7s, 7750 SR-14s
mda
Syntax
[no] mda mda-id
Context
[Tree] (config>service>vpls>spoke-sdp>egress>mfib-allowed-mda-destinations mda)
[Tree] (config>service>vpls>mesh-sdp>egress>mfib-allowed-mda-destinations mda)
Full Context
configure service vpls spoke-sdp egress mfib-allowed-mda-destinations mda
configure service vpls mesh-sdp egress mfib-allowed-mda-destinations mda
Description
This command specifies an MFIB-allowed MDA destination for an SDP binding configured in the system.
Parameters
- mda-id
-
Specifies an MFIB-allowed MDA destination
Platforms
All
mda
Syntax
[no] mda mda-id
Context
[Tree] (config>isa>tunnel-grp mda)
Full Context
configure isa tunnel-group mda
Description
This command specifies the MDA ID of the MS-ISA as the member of tunnel-group with multi-active enabled. Up to 16 MDA could be configured under the same tunnel-group.
Parameters
- mda-id
-
Specifies the id of MS-ISA.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
mda
Syntax
mda mda-id [drain]
no mda mda-id
Context
[Tree] (config>isa>lns-group mda)
Full Context
configure isa lns-group mda
Description
This command configures an ISA LNS group MDA.
The no form of the command removes the MDA ID from the LNS group configuration.
Parameters
- mda-id
-
Specifies the MDA identifier.
- drain
-
Prevents new L2TP sessions being associated with the ISA. If an ISA is removed from the lns-group or if the lns-group be shutdown all associated L2TP sessions will be immediately terminated (and L2TP CDN messages sent to the L2TP peer). View show commands to determine which ISA is terminating which session (show router l2tp session).
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
mda
Syntax
[no] mda mda-id
Context
[Tree] (config>isa>nat-group mda)
Full Context
configure isa nat-group mda
Description
This command configures an ISA NAT group MDA.
Parameters
- mda-id
-
Specifies the MDA ID in the slot/mda format.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
mda
Syntax
[no] mda mda-id
Context
[Tree] (config>service>pw-template>egress>mfib-mda mda)
Full Context
configure service pw-template egress mfib-allowed-mda-destinations mda
Description
This command specifies an MFIB-allowed media adapter destination for an SDP binding configured in the system.
Parameters
- mda-id
-
Specifies an MFIB-allowed media adapters destination.
Platforms
All
mda
Syntax
mda mda
no mda
Context
[Tree] (config>isa>tunnel-mem-pool mda)
Full Context
configure isa tunnel-member-pool mda
Description
This command configures an association between an MDA and the tunnel member pool.
The no form of this command removes the association between the MDA and the tunnel member pool.
Parameters
- name
-
Specifies the name of the MDA, up to 32 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
mda-type
mda-type
Syntax
mda-type mda-type [level mda-level]
no mda-type
Context
[Tree] (config>card>mda mda-type)
Full Context
configure card mda mda-type
Description
This mandatory command provisions a specific MDA type to the device configuration for the slot. The MDA can be preprovisioned but an MDA must be provisioned before ports can be configured. Ports can be configured once the MDA is properly provisioned.
A maximum of two MDAs can be provisioned on an IOM or XCM. To modify an MDA slot, shut down all port associations.
XMAs are provisioned using MDA commands. A medium severity alarm is generated if an MDA is inserted that does not match the MDA type configured for the slot. This alarm is cleared when the correct MDA is inserted or the configuration is modified. A high severity alarm is raised when an administratively enabled MDA is removed from the chassis. This alarm is cleared if the either the correct MDA type is inserted or the configuration is modified. A low severity trap is issued if an MDA is removed that is administratively disabled.
An MDA can only be provisioned in a slot if the MDA type is allowed in the MDA slot. An error message is generated when an MDA is provisioned in a slot where it is not allowed.
Some MDA hardware can support two different firmware loads. One load includes the base Ethernet functionality, including 10G WAN mode, but does not include 1588 port-based timestamping. The second load includes the base Ethernet functionality and 1588 port-based timestamping, but does not include 10G WAN mode. These are identified as two MDA types that are the same, except for a ‟-ptp” suffix to indicate the second loadset; for example, x40-10gb-sfp and x40-10gb-sfp-ptp. A hard reset of the MDA occurs when switching between the two provisioned types.
A medium severity alarm is generated if an MDA is inserted that does not match the MDA type configured for the slot. This alarm is cleared when the correct MDA is inserted or the configuration is modified.
A high severity alarm is raised when an administratively enabled MDA is removed from the chassis. This alarm is cleared if the either the correct MDA type is inserted or the configuration is modified. A low severity trap is issued if an MDA is removed that is administratively disabled.
An alarm is raised if partial or complete MDA failure is detected. The alarm is cleared when the error condition ceases.
All parameters in the MDA context remain and if non-default values are required then their configuration remains as it is on all existing MDAs.
New generations of XMAs include variants controlled through hardware and software licensing. For these XMAs, the license level must be provisioned in addition to the MDA type. An XMA cannot become operational unless the provisioned license level matches the license level of the XMA installed into the slot. The set of license levels varies by MDA type.
The provisioned level controls aspects related to connector provisioning and the consumption of hardware egress queues and egress policers. Changes to the provisioned license level may be blocked if configuration that would not be permitted with the new target license level exists.
If the license level is not specified, the level is set to the highest license level for that XMA.
The no form of this command deletes the MDA from the configuration. The MDA must be administratively shut down before it can be deleted from the configuration.
Parameters
- mda-type
-
Specifies the type of MDA selected for the slot position. Values for this attribute vary by platform and release. The release notes include a listing of all supported mda-types and their CLI strings. In addition, the command can be queried to check which mda-types are relevant for the active platform type. Some examples include me6-10gb-spf+ and x4-100g-cfp2.
- mda-level
-
Specifies the MDA level. Possible values vary by MDA type.
Platforms
All
mda-type
Syntax
mda-type mda-type
no mda-type
Context
[Tree] (config>card>xiom>mda mda-type)
Full Context
configure card xiom mda mda-type
Description
This command adds an MDA-s to the device configuration for the slot. The MDA-s type can be preprovisioned, which means that the MDA-s does not have to be installed in the chassis.
An MDA-s must be provisioned before a connector or a port can be configured.
An MDA-s can only be provisioned in a slot that is vacant. No other MDA-s can be provisioned (configured) for that particular slot. To reconfigure a slot position, use the no form of this command to remove the current information.
An MDA-s can only be provisioned in a slot if the MDA-s type is allowed in the slot. An error message is generated if an attempt is made to provision an MDA-s type that is not allowed.
If an MDA-s is inserted that does not match the configured MDA-s type for the slot, then a log event and a facility alarm are raised. The alarm is cleared when the correct MDA-s type is installed or the configuration is modified.
A log event and a facility alarm are raised if an administratively enabled MDA-s is removed from the chassis. The alarm is cleared when the correct MDA-s type is installed or the configuration is modified. A log event is issued when a MDA-s is removed that is administratively disabled.
The no form of this command removes the MDA-s from the configuration.
Parameters
- mda-type
-
Specifies the type of MDA-s to be configured and installed in the slot. Values for this attribute vary by platform and release. The release notes include a listing of all supported mda-types and their CLI strings. In addition, the command can be queried to check which mda-types are relevant for the active platform type.
Platforms
7750 SR-1s, 7750 SR-2s, 7750 SR-7s, 7750 SR-14s
mdl
mdl
Syntax
mdl {eic | lic | fic | unit | pfi | port | gen} mdl-string
no mdl [eic | lic | fic | unit | pfi | port | gen]
Context
[Tree] (config>port>tdm>ds3 mdl)
Full Context
configure port tdm ds3 mdl
Description
This command configures the maintenance data link (MDL) message for a DS-3/E-3.
This command is only applicable if the DS-3/E-3 is using C-bit framing (see the config>port>tdm>ds3 framing command).
The no form of this command removes the MDL string association and stops the transmission of any IDs.
Default
no mdl
Parameters
- mdl-string
-
Specifies an MDL message up to 38 characters long on a DS-3.
- eic
-
Specifies the equipment ID code up to 10 characters long.
- lic
-
Specifies the equipment ID code up to 11 characters long.
- fic
-
Specifies the ID code up to 10 characters long.
- unit
-
Specifies the unit ID code up to 6 characters long.
- pfi
-
Specifies the facility ID code up to 38 characters long.
- port
-
Specifies the port ID code up to 38 characters long.
- gen
-
Specifies the generator number to send in the MDL test signal message up to 38 characters long.
Platforms
7450 ESS, 7750 SR-7/12/12e, 7750 SR-a, 7750 SR-e
mdl-transmit
mdl-transmit
Syntax
mdl-transmit {path | idle-signal | test-signal}
no mdl-transmit [path | idle-signal | test-signal]
Context
[Tree] (config>port>tdm>ds3 mdl-transmit)
Full Context
configure port tdm ds3 mdl-transmit
Description
This command enables the transmission of an MDL message on a DS-3/E-3 over channelized interface.
The no form of this command disables transmission of the specified message or all messages.
Default
no mdl-transmit
Parameters
- path
-
Specifies the MDL path message.
- idle-signal
-
Specifies the MDL idle signal message.
- test-signal
-
Specifies the MDL test signal message.
Platforms
7450 ESS, 7750 SR-7/12/12e, 7750 SR-a, 7750 SR-e
mdt-pim
mdt-pim
Syntax
mdt-pim mode {asm | ssm} group-address group-ip-address
no mdt-pim
Context
[Tree] (config>service>vprn>mvpn>pt>selective>multistream-spmsi mdt-pim)
Full Context
configure service vprn mvpn provider-tunnel selective multistream-spmsi mdt-pim
Description
This command creates a multi-stream MDT that could match many (C-S,C-G)s into a single data MDT.
Parameters
- group-ip-address
-
Specifies the group address of this data MDT, that is the provider group address.
Platforms
All
mdt-type
mdt-type
Syntax
mdt-type {sender-receiver | sender-only | receiver-only}
no mdt-type
Context
[Tree] (config>service>vprn>mvpn mdt-type)
Full Context
configure service vprn mvpn mdt-type
Description
This command allows restricting MVPN instance per PE node to a specific role. By default, MVPN instance on a given PE node assumes the role of being a sender as well as receiver. This creates a mesh of MDT/PMSI across all PE nodes from this PE.
This command provides an option to configure either a sender-only or receiver-only mode per PE node. Restricting the role of a PE node prevents creating full mesh of MDT/PMSI across all PE nodes that are participating in MVPN instance.
auto-rp-discovery cannot be enabled together with mdt-type sender-only or mdt-type receiver-only, or wildcard-spmsi configurations.
The no version of this command restores the default (sender-receiver).
Default
mdt-type sender-receiver
Parameters
- sender-receiver
-
Specifies MVPN has both sender and receivers connected to PE node.
- sender-only
-
Specifies MVPN has only senders connected to PE node.
- receiver-only
-
Specifies MVPN has only receivers connected to PE node.
Platforms
All
meas-interval
meas-interval
Syntax
meas-interval {5-mins | 15-mins | 1-hour | 1-day} [create]
no meas-interval {5-mins | 15-mins | 1-hour | 1-day}
Context
[Tree] (config>oam-pm>session meas-interval)
Full Context
configure oam-pm session meas-interval
Description
This command establishes the parameters of the individual measurement intervals utilized by the session. Multiple measurement intervals may be specified within the session. A maximum of three different measurement intervals may be configured under each session.
The no form of this command deletes the specified measurement interval.
Parameters
- meas-interval
-
Specifies the duration of the measurement interval.
- create
-
Creates the measurement interval.
Platforms
All
measurement-template
measurement-template
Syntax
measurement-template template-name [create]
no measurement-template template-name
Context
[Tree] (config>test-oam>link-meas measurement-template)
Full Context
configure test-oam link-measurement measurement-template
Description
This command configures a measurement template identifier that can be assigned to the IP interface by name.
Configuration modifications can be made to the measurement template without disabling the template and while IP interfaces are actively referencing the measurement-template. Refer to the 7250 IXR OAM and Diagnostics Guide for more information about which modifications will cause the test on associated IP interfaces to ‟Terminate” and restart.
The no form of this command removes the template name. A measurement template can be removed if no interfaces are referencing the template.
Parameters
- template-name
-
Specifies the measurement template name, up to 64 characters.
- create
-
Keyword used to create the measurement template. The create keyword requirement can be enabled or disabled in the environment>create context.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
measurement-template
Syntax
measurement-template [64 chars max]
no measurement-template
Context
[Tree] (config>router>if>if-attr>delay>dyn measurement-template)
Full Context
configure router interface if-attribute delay dynamic measurement-template
Description
This command specifies the measurement template name used on the interface. The measurement-template associated with the interface can be changed without disabling the test protocol used to carry the test packet. Changing or removing the measurement-template associated with the IP interface stops the test and removes all test results for the IP interface.
The no form of this command removes the measurement-template, which stops the test and removes all test results for the interface.
Default
no measurement-template
Parameters
- 64 chars max
-
Specifies the measurement template name, up to 64 characters
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
med-out
med-out
Syntax
med-out {number | igp-cost}
no med-out
Context
[Tree] (config>subscr-mgmt>bgp-prng-plcy med-out)
Full Context
configure subscriber-mgmt bgp-peering-policy med-out
Description
This command enables advertising the Multi-Exit Discriminator (MED) and assigns the value used for the path attribute for the MED advertised to BGP peers if the MED is not already set.
The specified value can be overridden by any value set with a route policy.
The no form of this command used at the global level reverts to default where the MED is not advertised.
Parameters
- number
-
Specifies the MED path attribute value, expressed as a decimal integer.
- igp-cost
-
Specifies that the MED is set to the IGP cost of the given IP prefix.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
med-out
Syntax
med-out {number | igp-cost}
no med-out
Context
[Tree] (config>service>vprn>bgp>group>neighbor med-out)
[Tree] (config>service>vprn>bgp med-out)
[Tree] (config>service>vprn>bgp>group med-out)
Full Context
configure service vprn bgp group neighbor med-out
configure service vprn bgp med-out
configure service vprn bgp group med-out
Description
This command enables advertising the Multi-Exit Discriminator (MED) and assigns the value used for the path attribute for the MED advertised to BGP peers if the MED is not already set.
The specified value can be overridden by any value set via a route policy.
This configuration parameter can be set at three levels: global level (applies to all peers), group level (applies to all peers in peer-group) or neighbor level (only applies to specified peer). The most specific value is used.
The no form of this command used at the global level reverts to default where the MED is not advertised.
The no form of this command used at the group level reverts to the value defined at the global level.
The no form of this command used at the neighbor level reverts to the value defined at the group level.
Default
no med-out
Parameters
- number
-
Specifies the MED path attribute value, expressed as a decimal integer.
- igp-cost
-
Specifies the MED is set to the IGP cost of the given IP prefix.
Platforms
All
med-out
Syntax
med-out {number | igp-cost}
no med-out
Context
[Tree] (config>router>bgp med-out)
[Tree] (config>router>bgp>group>neighbor med-out)
[Tree] (config>router>bgp>group med-out)
Full Context
configure router bgp med-out
configure router bgp group neighbor med-out
configure router bgp group med-out
Description
This command enables advertising the Multi-Exit Discriminator (MED) and assigns the value used for the path attribute for the MED advertised to BGP peers if the MED is not already set.
The specified value can be overridden by any value set via a route policy.
This configuration parameter can be set at three levels: global level (applies to all peers), group level (applies to all peers in peer-group) or neighbor level (only applies to specified peer). The most specific value is used.
The no form of this command used at the global level reverts to default where the MED is not advertised.
The no form of this command used at the group level reverts to the value defined at the global level.
The no form of this command used at the neighbor level reverts to the value defined at the group level.
Default
no med-out
Parameters
- number
-
Specifies the MED path attribute value, expressed as a decimal integer.
- igp-cost
-
Sets MED to the IGP cost of the given IP prefix.
Platforms
All
medium-duration-flow-count
medium-duration-flow-count
Syntax
[no] medium-duration-flow-count
Context
[Tree] (config>log>acct-policy>cr>aa>aa-sub-cntr medium-duration-flow-count)
Full Context
configure log accounting-policy custom-record aa-specific aa-sub-counters medium-duration-flow-count
Description
This command includes the medium duration flow count in the AA subscriber's custom record. This command only applies to the 7750 SR.
The no form of this command excludes the medium duration flow count.
Default
no medium-duration-flow-count
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
member
member
Syntax
[no] member port-id
Context
[Tree] (config>interface-group-handler member)
Full Context
configure interface-group-handler member
Description
This command binds the specified port with the associate Interface Group Handler. Up to eight member commands can be issued to add multiple ports to the associated IGH. The member must be a port or channel on a SONET or POS MDA. It must be a physical port or channel in network mode, and not bound to any router interfaces. A port or channel cannot be a member of more than one IGH at the same time. MLPPP bundles and their members cannot be IGH members.
The no form of this command removes the specified port ID from the associated IGH.
Parameters
- port-id
-
specifies the port to be associated with the interface group handler.
Platforms
All
member
Syntax
[no] member port-id
Context
[Tree] (config>port>multilink-bundle member)
Full Context
configure port multilink-bundle member
Description
This command binds a channel group to a multilink bundle. For IMA and MLFR groups, this command binds a channel group filling up the entire DS-1 or E-1. For MLPPP groups, fractional (n x ds0) DS1 or E1 links are also allowed. However, fractional DS1 links and fractional E1 links may not be combined in the same multilink bundle. If a channel with a different number of timeslots than the primary-link member is added to the bundle, a warning will be provided.
The no form of this command removes the specified channel group from the multilink bundle.
Parameters
- port-id
-
Specifies the physical port ID in the following format:
Platforms
7450 ESS, 7750 SR-7/12/12e
member
Syntax
member port-id
no member
Context
[Tree] (config>eth-tunnel>path member)
Full Context
configure eth-tunnel path member
Description
This command associates a port with the path defined under the Ethernet tunnel. If the operator wants to replace an existing member port or control tag, the whole path needs to be shutdown first. The alternate path will be activated as a result keeping traffic interruption to a minimum. Then the whole path must be deleted, the alternate path precedence modified to primary before re-creating the new path.
The following port-level configuration needs to be the same across the two member ports of an Ethernet tunnel:
-
port>ethernet>access>{ingress|egress}>queue-group
-
port>ethernet>egress-scheduler-policy
-
port>access>egress>pool
-
port>ethernet>dot1q-etype
-
port>ethernet>qinq-etype
-
port>ethernet>pbb-etype
-
port>ethernet>mtu
The Ethernet tunnel will inherit the configuration from the first member port for these parameters. Additional member port that is added must have the same configuration.
The operator is allowed to update these port parameters only if the port is the sole member of an Ethernet tunnel. This means that in the example below, the operator needs to remove port 1/1/4 and port 1/1/5 before being allowed to modify 1/1/1 for the above parameters.
eth-tunnel 1
path 1
member 1/1/1
path 2
member 1/1/4
eth-tunnel 2
path 1
member 1/1/1
path 2
member 1/1/5
The no form of this command is used just to indicate that a member is not configured. The procedure described above, based on the no path command must be used to un-configure/change the member port assigned to the path.
Default
no member
Parameters
- port-id
-
Specifies the port-id associated with the path in the format x/y/z where x represents the IOM, y the MDA and z the port numbers.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
member
Syntax
member encap-value [create]
no member encap-value
Context
[Tree] (config>connection-profile member)
Full Context
configure connection-profile member
Description
This command allows the adding of discrete VPI/VCI values to an ATM connection profile for assignment to an ATM SAP of an Apipe VLL of vc-type atm-cell.
Up to a maximum of 16 discrete VPI/VCI values can be configured in a connection profile. The user can modify the content of a profile which triggers a re-evaluation of all the ATM SAPs which are currently using the profile.
The no form of this command deletes the member from the configuration.
Parameters
- encap-value
-
Specifies the VPI and VCI values of this connection profile member.
Platforms
7450 ESS, 7750 SR-7/12/12e
member
Syntax
[no] member encap-id [to encap-id]
Context
[Tree] (config>service>vpls>sap>egress>encap-defined-qos>encap-group member)
Full Context
configure service vpls sap egress encap-defined-qos encap-group member
Description
This command adds or removes a member ISID or a range of contiguous ISID members to an encap-group. The user can add or remove members to the encap-group one at a time or as a range of contiguous values using the member command. However, when the qos-per-member option is enabled, members must be added or removed one at a time.
The no form of this command removes the single or range of ISID values from the encap-group.
Parameters
- encap-id
-
Specifies the value of the single encap-id or the start encap-id of the range. ISID is the only encap-id supported.
- to encap-id
-
Specifies the value of the end encap-id of the range. ISID is the only encap-id supported.
Platforms
All
member
Syntax
[no] member interface-name
Context
[Tree] (config>service>vprn>isis>link-group>level member)
Full Context
configure service vprn isis link-group level member
Description
This command adds or removes a links to the associated link-group. The interface name should already exist before it is added to a link-group.
The no form of this command removes the specified interface from the associated link-group.
Parameters
- interface-name
-
Specifies the name of the interface to be added or removed from the associated link-group.
Platforms
All
member
Syntax
[no] member member-id
Context
[Tree] (config>gmpls-tun-grp member)
Full Context
configure gmpls-tun-grp member
Description
This command configures a member of a GMPLS tunnel group. A member of a GMPLS tunnel group is a GMPLS LSP. All members of a tunnel group must have the same bandwidth. Up to 16 members may be configured for each GMPLS tunnel group.
The no form of this command removes the member.
Default
no member
Parameters
- member-id
-
Specifies the identifier of the GMPLS tunnel group member.
Platforms
7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
member
Syntax
member user-profile-name [user-profile-name]
no member user-profile-name
Context
[Tree] (config>system>security>user>console member)
Full Context
configure system security user console member
Description
This command is used to associate the user with a local command authorization profile.
A user can be associated with up to eight profiles.
The no form of this command removes the association between the user and the profile.
Default
member default
Parameters
- user-profile-name
-
Specifies up to eight user profile names, up to 32 characters.
Platforms
All
member
Syntax
[no] member interface-name
Context
[Tree] (config>router>isis>link-group>level member)
Full Context
configure router isis link-group level member
Description
This command adds or removes a link to the associated link-group. The interface name should already exist before it is added to a link-group.
The no form of this command removes the specified interface from the associated link-group.
Parameters
- interface-name
-
Specifies the name of the interface to be added or removed from the associated link-group.
Platforms
All
member-pool
member-pool
Syntax
member-pool name
no member-pool
Context
[Tree] (config>isa>tunnel-grp member-pool)
Full Context
configure isa tunnel-group member-pool
Description
This command associates the tunnel group with a tunnel member pool. This tunnel group is used as the designated standby in an N:M IPsec redundancy configuration.
The no form of this command removes the tunnel member pool from the configuration.
Parameters
- name
-
Specifies the name of the member pool, up to 32 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
member-threshold
member-threshold
Syntax
[no] member-threshold threshold
Context
[Tree] (config>gmpls-tun-grp member-threshold)
Full Context
configure gmpls-tun-grp member-threshold
Description
The member-threshold is the number of member GMPLS LSPs that must be operationally up before the GMPLS tunnel group is considered operationally up. If that number is not reached, then the GMPLS tunnel group is taken operationally down.
A member of a GMPLS tunnel group may be treated as down for one of the following reasons. These reason codes are recorded in the tmnxGmplsTunGrpMemberTable in the MIB:
-
adminDn — The member or the related tunnel group is admin down.
-
wpLspDn — The associated GMPLS LSP working path is down.
-
wpPortDn — The data-bearer port associated with the GMPLS LSP working path is down.
-
wpPortNoRsrc — The data bearer port associated with the LSP working path has no resource to support the services over the GMPLS tunnel group logical port.
-
ppLspDn — The associated GMPLS LSP protect path is down.
-
ppPortDn — The data-bearer port associated with the GMPLS LSP protect path is down.
-
ppPortNoRsrc — The data bearer port associated with the GMPLS LSP protect path has no resource to support the services over the GMPLS tunnel group logical port.
The no form of this command resets the member threshold to 0.
Default
member-threshold 0
Parameters
- threshold
-
Specifies the minimum number of GMPLS LSPs that must be operationally up before the GMPLS tunnel group is considered operationally up.
Platforms
7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
members
members
Syntax
[no] members comm-id [comm-id]
Context
[Tree] (config>router>policy-options>community members)
Full Context
configure router policy-options community members
Description
This command adds members to a route policy community list to use in route policy entries.
The no version of this command deletes route policy community members.
Parameters
- comm-id
-
Specifies a BGP community value, up to 72 characters. A community ID can be specified in different forms.
Platforms
All
memory
memory
Syntax
memory memory-size
no memory
Context
[Tree] (config>esa>vm memory)
Full Context
configure esa vm memory
Description
This command configures the amount of memory (in gigabytes) that is allocated to the ESA-VM instance.
The no form of this command removes the memory allocation. To modify the memory allocation, first invoke the no memory command.
Parameters
- memory-size
-
Specifies the amount of memory in GB.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s
memory-alarm
memory-alarm
Syntax
memory-alarm high-threshold high-percentage low-threshold low-percentage
no memory-alarm
Context
[Tree] (config>li>x-interfaces>x3>alarms memory-alarm)
Full Context
configure li x-interfaces x3 alarms memory-alarm
Description
This command configures the thresholds for raising the memory alarm. The low threshold value must be configured with a smaller value than the high threshold.
The no form of this command reverts to the default values.
Parameters
- high-percentage
-
Specifies the high threshold value, as a percentage.
- low-percentage
-
Specifies the low threshold value, as a percentage.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
memory-use-alarm
memory-use-alarm
Syntax
memory-use-alarm rising-threshold threshold [falling-threshold threshold] interval seconds [rmon-event-type] [startup-alarm alarm-type]
no memory-use-alarm
Context
[Tree] (config>system>thresholds memory-use-alarm)
Full Context
configure system thresholds memory-use-alarm
Description
The memory thresholds are based on monitoring the TIMETRA-SYSTEM-MIB sgiMemoryUsed object. This object contains the amount of memory currently used by the system. The severity level is Alarm. The absolute sample type method is used.
The no form of this command removes the configured memory threshold warning.
Parameters
- rising-threshold threshold
-
Specifies a threshold for the sampled statistic. When the current sampled value is greater than or equal to this threshold, and the value at the last sampling interval was less than this threshold, a single threshold crossing event will be generated. A single threshold crossing event will also be generated if the first sample taken is greater than or equal to this threshold and the associated startup-alarm is equal to rising or either.
After a rising threshold crossing event is generated, another such event will not be generated until the sampled value falls below this threshold and reaches less than or equal the falling-threshold value.
The threshold value represents units in bytes.
- falling-threshold threshold
-
Specifies a threshold for the sampled statistic. When the current sampled value is less than or equal to this threshold, and the value at the last sampling interval was greater than this threshold, a single threshold crossing event will be generated. A single threshold crossing event will also be generated if the first sample taken is less than or equal to this threshold and the associated startup-alarm is equal to falling or either.
After a falling threshold crossing event is generated, another such event will not be generated until the sampled value rises above this threshold and reaches greater than or equal the rising-threshold value.
The threshold value represents units in bytes.
- seconds
-
Specifies the polling period over which the data is sampled and compared with the rising and falling thresholds.
The threshold value represents units in bytes.
- rmon-event-type
-
Specifies the type of notification action to be taken when this event occurs.
- alarm-type
-
Specifies the alarm that may be sent when this alarm is first created. If the first sample is greater than or equal to the rising threshold value and startup-alarm is equal to rising or either, then a single rising threshold crossing event is generated. If the first sample is less than or equal to the falling threshold value and startup-alarm is equal to falling or either, a single falling threshold crossing event is generated.
Platforms
All
memory-use-warn
memory-use-warn
Syntax
memory-use-warn rising-threshold threshold [falling-threshold threshold] interval seconds [rmon-event-type] [startup-alarm alarm-type]
no memory-use-warn
Context
[Tree] (config>system>thresholds memory-use-warn)
Full Context
configure system thresholds memory-use-warn
Description
The memory thresholds are based on monitoring MemoryUsed object. This object contains the amount of memory currently used by the system. The severity level is Alarm.
The absolute sample type method is used.
The no form of this command removes the configured compact flash threshold warning.
Parameters
- rising-threshold threshold
-
Specifies a threshold for the sampled statistic. When the current sampled value is greater than or equal to this threshold, and the value at the last sampling interval was less than this threshold, a single threshold crossing event will be generated. A single threshold crossing event will also be generated if the first sample taken is greater than or equal to this threshold and the associated startup-alarm is equal to rising or either.
After a rising threshold crossing event is generated, another such event will not be generated until the sampled value falls below this threshold and reaches less than or equal the falling-threshold value.
The threshold value represents units in bytes.
- falling-threshold threshold
-
Specifies a threshold for the sampled statistic. When the current sampled value is less than or equal to this threshold, and the value at the last sampling interval was greater than this threshold, a single threshold crossing event will be generated. A single threshold crossing event will also be generated if the first sample taken is less than or equal to this threshold and the associated startup-alarm is equal to falling or either.
After a falling threshold crossing event is generated, another such event will not be generated until the sampled value rises above this threshold and reaches greater than or equal the rising-threshold value.
The threshold value represents units in bytes.
- seconds
-
Specifies the polling period over which the data is sampled and compared with the rising and falling thresholds.
- rmon-event-type
-
Specifies the type of notification action to be taken when this event occurs.
- startup-alarm alarm-type
-
Specifies the alarm that may be sent when this alarm is first created. If the first sample is greater than or equal to the rising threshold value and startup-alarm is equal to rising or either, then a single rising threshold crossing event is generated. If the first sample is less than or equal to the falling threshold value and startup-alarm is equal to falling or either, a single falling threshold crossing event is generated.
Platforms
All
mep
mep
Syntax
[no] mep mep-id domain md-index association ma-index
Context
[Tree] (config>eth-tunnel>path>eth-cfm mep)
Full Context
configure eth-tunnel path eth-cfm mep
Description
This command provisions an 802.1ag maintenance endpoint (MEP).
The no form of this command reverts to the default values.
Parameters
- mep-id
-
Specifies the maintenance association end point identifier.
- md-index
-
Specifies the maintenance domain (MD) index value.
- ma-index
-
Specifies the MA index value.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
mep
Syntax
[no] mep mep-id domain md-index association ma-index [vlan vlan-id]
Context
[Tree] (config>port>ethernet>eth-cfm mep)
[Tree] (config>lag>eth-cfm mep)
[Tree] (config>router>if>eth-cfm mep)
Full Context
configure port ethernet eth-cfm mep
configure lag eth-cfm mep
configure router interface eth-cfm mep
Description
This command provisions the maintenance endpoint (MEP).
The no form of this command reverts to the default values.
Parameters
- mep-id
-
Specifies the maintenance association end point identifier.
- md-index
-
Specifies the maintenance domain (MD) index value.
- ma-index
-
Specifies the MA index value.
- vlan-id
-
Specific to tunnel facility MEPs which means this option is only applicable to the lag>eth-cfm> context. Used to specify the outer vlan id of the tunnel.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
mep
Syntax
mep mep-id domain md-index association ma-index [direction {up | down}] [primary-vlan-enable]
no mep mep-id domain md-index association ma-index
Context
[Tree] (config>service>epipe>sap>eth-cfm mep)
[Tree] (config>service>epipe>spoke-sdp>eth-cfm mep)
[Tree] (config>service>ipipe>sap>eth-cfm mep)
Full Context
configure service epipe sap eth-cfm mep
configure service epipe spoke-sdp eth-cfm mep
configure service ipipe sap eth-cfm mep
Description
This command provisions the maintenance endpoint (MEP).
The no form of this command reverts to the default values.
Parameters
- mep-id
-
Specifies the maintenance endpoint identifier.
- md-index
-
Specifies the maintenance domain (MD) index value.
- ma-index
-
Specifies the maintenance association (MA) index value.
- direction {up | down}
-
Indicates the direction in which the MEP faces on the bridge port. The UP direction is not supported for all Fpipe services. For example, Ipipe does not support the direction of UP for MEPs.
- up
-
Sends ETH-CFM messages toward the MAC relay entity.
- down
-
Sends ETH-CFM messages away from the MAC relay entity.
- primary-vlan-enable
-
Provides a method for linking the MEP with the primary VLAN configured under the bridge-identifier for the MA. This must be configured as part of the creation step and can only be changed by deleting the MEP and re-creating it. Primary VLANs are only supported under Layer 2 Epipe and VPLS services.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
mep
Syntax
mep mep-id domain md-index association ma-index [direction {up | down}] [primary-vlan-enable]
no mep mep-id domain md-index association ma-index
Context
[Tree] (config>service>vpls>spoke-sdp>eth-cfm mep)
[Tree] (config>service>vpls>sap>eth-cfm mep)
[Tree] (config>service>vpls>mesh-sdp>eth-cfm mep)
[Tree] (config>service>vpls>eth-cfm mep)
Full Context
configure service vpls spoke-sdp eth-cfm mep
configure service vpls sap eth-cfm mep
configure service vpls mesh-sdp eth-cfm mep
configure service vpls eth-cfm mep
Description
This command configures the ETH-CFM maintenance endpoint (MEP). A MEP created at the VPLS service level vpls>eth-cfm creates a virtual MEP.
The no version of the command will remove the MEP.
Parameters
- mep-id
-
Specifies the MEP identifier.
- md-index
-
Specifies the maintenance domain (MD) index value.
- ma-index
-
Specifies the maintenance association (MA) index value.
- direction up | down
-
Sets the direction in which the MEP faces on the bridge port. Direction is not supported when a MEP is created directly under the vpls>eth-cfm construct (vMEP).
down — Sends ETH-CFM messages away from the MAC relay entity.
up — Sends ETH-CFM messages toward the MAC relay entity.
- primary-vlan-enable
-
Sets a method for linking the MEP with the primary VLAN configured under the bridge-identifier for the MA. MEPs cannot be changed from or to primary VLAN functions. This must be configured as part of the creation step and can only be changed by deleting the MEP and re-creating it. Primary VLANs are only supported under Layer 2 Epipe and VPLS services.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
mep
Syntax
mep mep-id domain md-index association ma-index [direction {up | down}]
no mep mep-id domain md-index association ma-index
Context
[Tree] (config>service>ies>if>sap>eth-cfm mep)
[Tree] (config>service>ies>sub-if>grp-if>sap>eth-cfm mep)
[Tree] (config>service>ies>if>spoke-sdp>eth-cfm mep)
Full Context
configure service ies interface sap eth-cfm mep
configure service ies subscriber-interface group-interface sap eth-cfm mep
configure service ies interface spoke-sdp eth-cfm mep
Description
This command configures the ETH-CFM maintenance endpoint (MEP).
Parameters
- mep-id
-
Specifies the maintenance association end point identifier.
- md-index
-
Specifies the maintenance domain (MD) index value.
- ma-index
-
Specifies the MA index value.
- direction up | down
-
The direction in which the maintenance association (MEP) faces on the bridge port. Direction UP is not applicable to IES MEPs.
down — Sends ETH-CFM messages away from the MAC relay entity.
up — Sends ETH-CFM messages towards the MAC relay entity.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
- configure service ies interface spoke-sdp eth-cfm mep
- configure service ies interface sap eth-cfm mep
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s
- configure service ies subscriber-interface group-interface sap eth-cfm mep
mep
Syntax
mep mep-id domain md-index association ma-index [direction {up | down}]
no mep mep-id domain md-index association ma-index
Context
[Tree] (config>service>vprn>if>spoke-sdp>eth-cfm mep)
[Tree] (config>service>vprn>sub-if>grp-if>sap>eth-cfm mep)
[Tree] (config>service>vprn>if>sap>eth-cfm mep)
Full Context
configure service vprn interface spoke-sdp eth-cfm mep
configure service vprn subscriber-interface group-interface sap eth-cfm mep
configure service vprn interface sap eth-cfm mep
Description
This command configures the ETH-CFM maintenance endpoint (MEP).
Parameters
- mep-id
-
Specifies the maintenance association end point identifier.
- md-index
-
Specifies the maintenance domain (MD) index value.
- ma-index
-
Specifies the MA index value.
- direction up | down
-
Indicates the direction in which the maintenance association (MEP) faces on the bridge port. Direction UP is not supported on VPRN MEPs.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
- configure service vprn interface spoke-sdp eth-cfm mep
- configure service vprn interface sap eth-cfm mep
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s
- configure service vprn subscriber-interface group-interface sap eth-cfm mep
mep
Syntax
[no] mep
Context
[Tree] (config>router>mpls>lsp>working-tp-path mep)
[Tree] (config>router>mpls>lsp>protect-tp-path mep)
Full Context
configure router mpls lsp working-tp-path mep
configure router mpls lsp protect-tp-path mep
Description
This command creates or edits an MPLS-TP maintenance entity group (MEG) endpoint (MEP) on and MPLS-TP path. MEPs represent the termination point for OAM flowing on the path, as well as linear protection for the LSP. Only one MEP can be configured at each end of the path.
The following commands are applicable to a MEP on an MPLS-TP working or protect path: oam-template, bfd-enable, and shutdown. In addition, a protection-template may be configured on a protect path.
The no form of this command removes a MEP from an MPLS-TP path.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
mep
Syntax
[no] mep mep-id domain md-index association ma-index
Context
[Tree] (debug>eth-cfm mep)
Full Context
debug eth-cfm mep
Description
This command specifies the MEP from which to debug the CFM PDUs.
The no form of this command removes the MEP parameters.
Parameters
- mep-id
-
Specifies the maintenance association endpoint identifier of the launch point.
- md-index
-
Specifies the maintenance domain (MD) index value of the launch point.
- ma-index
-
Specifies the maintenance association (MA) index value of the launch point.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
mep
Syntax
[no] mep mep-id domain md-index association ma-index
Context
[Tree] (config>eth-ring>path>eth-cfm mep)
Full Context
configure eth-ring path eth-cfm mep
Description
This command provisions an 802.1ag maintenance endpoint (MEP).
The no form of the command deletes the MEP.
Parameters
- mep-id
-
Specifies the maintenance association end point identifier.
- md-index
-
Specifies the maintenance domain (MD) index value.
- ma-index
-
Specifies the MA index value.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
mesh-group
mesh-group
Syntax
mesh-group {value | blocked}
no mesh-group
Context
[Tree] (config>service>vprn>isis>if mesh-group)
Full Context
configure service vprn isis interface mesh-group
Description
This command assigns an interface to a mesh group. Mesh groups limit the amount of flooding that occurs when a new or changed LSP is advertised throughout an area.
All routers in a mesh group should be fully meshed. When LSPs need to be flooded, only a single copy is received rather than a copy per neighbor.
To create a mesh group, configure the same mesh group value for each interface that is part of the mesh group. All routers must have the same mesh group value configured for all interfaces that are part of the mesh group.
To prevent an interface from flooding LSPs, the optional blocked parameter can be specified. Configure mesh groups carefully. It is easy to create isolated islands that do not receive updates as (other) links fail.
The no form of this command removes the interface from the mesh group. The interface does not belong to a mesh group.
Default
no mesh-group
Parameters
- value
-
Specifies a unique decimal integer value distinguishes this mesh group from other mesh groups on this or any other router that is part of this mesh group.
- blocked
-
Prevents an interface from flooding LSPs.
Platforms
All
mesh-group
Syntax
mesh-group {value | blocked}
no mesh-group
Context
[Tree] (config>router>isis>interface mesh-group)
Full Context
configure router isis interface mesh-group
Description
This command assigns an interface to a mesh group. Mesh groups limit the amount of flooding that occurs when a new or changed LSP is advertised throughout an area.
All routers in a mesh group should be fully meshed. When LSPs need to be flooded, only a single copy is received rather than a copy per neighbor.
To create a mesh group, configure the same mesh group value for each interface that is part of the mesh group. All routers must have the same mesh group value configured for all interfaces that are part of the mesh group.
To prevent an interface from flooding LSPs, the optional blocked parameter can be specified. Configure mesh groups carefully to avoid creating isolated islands that do not receive updates as (other) links fail.
The no form of this command removes the interface from the mesh group.
Parameters
- value
-
Specifies the unique decimal integer value that distinguishes this mesh group from other mesh groups on this or any other router that is part of this mesh group.
- blocked
-
Prevents an interface from flooding LSPs.
Platforms
All
mesh-sdp
mesh-sdp
Syntax
mesh-sdp sdp-id[:vc-id] [vc-type {ether | vlan}] [create]
mesh-sdp sdp-id[:vc-id] [vc-type {ether | vlan}] [create] leaf-ac
mesh-sdp sdp-id[:vc-id] [vc-type {ether | vlan}] [create] root-leaf-tag
no mesh-sdp sdp-id[:vc-id]
Context
[Tree] (config>service>vpls mesh-sdp)
Full Context
configure service vpls mesh-sdp
Description
This command binds a VPLS service to an existing Service Distribution Point (SDP).
Mesh SDPs bound to a service are logically treated like a single bridge ‟port” for flooded traffic where flooded traffic received on any mesh SDP on the service is replicated to other ‟ports” (spoke SDPs and SAPs) and not transmitted on any mesh SDPs.
This command creates a binding between a service and an SDP. The SDP has an operational state which determines the operational state of the SDP within the service. For example, if the SDP is administratively or operationally down, the SDP for the service is down.
The SDP must already be defined in the config>service>sdp context in order to associate the SDP with an Epipe or VPLS service. If the sdp sdp-id is not already configured, an error message is generated. If the sdp-id does exist, a binding between that sdp-id and the service is created.
SDPs must be explicitly associated and bound to a service. If an SDP is not bound to a service, no far-end router devices can participate in the service.
The no form of this command removes the SDP binding from the service. The SDP configuration is not affected; only the binding of the SDP to a service. Once removed, no packets are forwarded to the far-end router.
Default
No sdp-id is bound to a service.
Parameters
- sdp-id
-
Specifies an SDP identifier.
- vc-id
-
Specifies a virtual circuit identifier. This value is used to validate the VC ID portion of each mesh SDP binding defined in the service. The default value of this object is equal to the service ID. Any value may be used for the vc-id when there is no existing mesh SDP within the service; if a mesh SDP exists then all other mesh SDPs in the service must be configured with the same vc-id.
- vc-type
-
Specifies to override the default VC type signaled for the spoke or mesh binding to the far end of the SDP. The VC type is a 15 bit-quantity containing a value which represents the type of VC. The actual signaling of the VC type depends on the signaling parameter defined for the SDP. If signaling is disabled, the vc-type command can still be used to define the dot1q value expected by the far-end provider equipment. A change of the binding’s VC type causes the binding to signal the new VC type to the far end when signaling is enabled.
VC types are derived according to IETF draft-martini-l2circuit-trans-mpls.
The VC type value for Ethernet is 0x0005.
The VC type value for an Ethernet VLAN is 0x0004.
- ether
-
Defines the VC type as Ethernet. The vlan keyword is mutually exclusive. When the VC type is not defined then the default is Ethernet for spoke SDP bindings. Defining Ethernet is the same as executing no vc-type and restores the default VC type for the spoke SDP binding (hex 5).
- vlan
-
Defines the VC type as VLAN. The top VLAN tag, if a VLAN tag is present, is stripped from traffic received on the pseudowire, and a vlan-tag is inserted when forwarding into the pseudowire. The ethernet and vlan keywords are mutually exclusive. When the VC type is not defined then the default is Ethernet for mesh SDP bindings.
Note:The system expects a symmetrical configuration with its peer, specifically it expects to remove the same number of VLAN tags from received traffic as it adds to transmitted traffic. As some of the related configuration parameters are local and not communicated in the signaling plane, an asymmetrical behavior cannot always be detected and so cannot be blocked. Consequently, protocol extractions will not necessarily function for asymmetrical configurations as they would with a symmetrical configurations resulting in an unexpected operation.
- root-leaf-tag
-
Specifies a tagging mesh SDP under an E-Tree VPLS. When a tag SDP binding is required, it is created with a root-leaf-tag flag. Only VLAN tag SDP bindings are supported. The VLAN type must be set to VC VLAN type. The root-leaf-tag parameter indicates this SDP binding is a tag SDP that uses a default VID 1 for root and 2 for leaf. The SDP binding tags egress E-Tree traffic with root and leaf VIDs as appropriate. Root and leaf VIDs are only significant between peering VPLS but the values must be consistent on each end. On ingress a tag SDP binding removes the VID tag on the interface between VPLS in the same E-Tree service. The tag SDP receives root tagged traffic and marks the traffic with a root indication internally. This option is not available on BGP EVPN-enabled E-Tree services.
- leaf-ac
-
Specifies an access (AC) mesh SDP binding under a E-Tree VPLS as a leaf access (AC) SDP. The default E-Tree SDP type is a root AC if leaf-ac or root-leaf-tag is not specified at SDP binding creation. This option is only available when the VPLS is designated as an E-Tree VPLS. BGP EVPN-enabled E-Tree VPLS services support the leaf-ac option.
- create
-
Keyword used to create the mesh SDP. The create keyword requirement can be enabled or disabled in the environment>create context.
Platforms
All
mesh-sdp-binding
mesh-sdp-binding
Syntax
[no] mesh-sdp-binding
Context
[Tree] (config>service>vpls>site mesh-sdp-binding)
Full Context
configure service vpls site mesh-sdp-binding
Description
This command enables applications to all mesh SDPs.
The no form of reverts the default.
Default
no mesh-sdp-binding
Platforms
All
message
message
Syntax
message {eq | neq} pattern pattern [regexp]
no message
Context
[Tree] (config>service>vprn>log>filter>entry>match message)
Full Context
configure service vprn log filter entry match message
Description
This command adds system messages as a match criterion.
The no form of this command removes messages as a match criterion.
Parameters
- eq
-
Specifies if the matching criteria should be equal to the specified value.
- neq
-
Specifies if the matching criteria should not be equal to the specified value.
- pattern
-
Specifies a message, up to 400 characters, to be used in the match criteria.
- regexp
-
Specifies the type of string comparison to use to determine if the log event matches the value of message command parameters. When the regexp keyword is not specified, the default matching algorithm used is a basic substring match.
Platforms
All
message
Syntax
message {eq | neq} pattern pattern [ regexp]
no message
Context
[Tree] (config>log>filter>entry>match message)
Full Context
configure log filter entry match message
Description
This command adds system messages as a match criterion.
The no form of this command removes messages as a match criterion.
Parameters
- eq
-
Determines if the matching criteria should be equal to the specified value.
- neq
-
Determines if the matching criteria should not be equal to the specified value.
- pattern
-
Specifies a message up to 400 characters in length to be used in the match criteria.
- regexp
-
Specifies the type of string comparison to use to determine if the log event matches the value of message command parameters. When the regexp keyword is not specified, the default matching algorithm used is a basic substring match.
Platforms
All
message-count
message-count
Syntax
message-count count
Context
[Tree] (config>ipsec>tnl-temp>icmp6-gen>pkt-too-big message-count)
[Tree] (config>service>ies>if>ipsec>ipsec-tunnel>icmp6-gen>pkt-too-big message-count)
[Tree] (config>service>vprn>if>sap>ipsec-tun>icmp6-gen>pkt-too-big message-count)
[Tree] (config>service>vprn>if>ipsec>ipsec-tunnel>icmp6-gen>pkt-too-big message-count)
[Tree] (config>router>if>ipsec-tunnel>icmp-gen>pkt-too-big message-count)
Full Context
configure ipsec tunnel-template icmp6-generation pkt-too-big message-count
configure service ies interface ipsec ipsec-tunnel icmp6-generation pkt-too-big message-count
configure service vprn interface sap ipsec-tunnel icmp6-generation pkt-too-big message-count
configure service vprn interface ipsec ipsec-tunnel icmp6-generation pkt-too-big message-count
configure router interface ipsec-tunnel icmp-gen pkt-too-big message-count
Description
This command configures the maximum number of ICMPv6 messages that can be sent during the configured interval.
Parameters
- count
-
Specifies the maximum number of ICMPv6 messages that can be sent during the configured interval
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
- configure service vprn interface sap ipsec-tunnel icmp6-generation pkt-too-big message-count
- configure ipsec tunnel-template icmp6-generation pkt-too-big message-count
VSR
- configure service ies interface ipsec ipsec-tunnel icmp6-generation pkt-too-big message-count
- configure service vprn interface ipsec ipsec-tunnel icmp6-generation pkt-too-big message-count
message-count
Syntax
message-count number
Context
[Tree] (config>router>if>ipsec>ipsec-tunnel>icmp-gen>frag-required message-count)
[Tree] (config>service>vprn>if>sap>ip-tunnel>icmp-gen>frag-required message-count)
[Tree] (config>ipsec>tnl-temp>icmp-gen>frag-required message-count)
[Tree] (config>service>vprn>if>sap>ipsec-tunnel>icmp-gen>frag-required message-count)
[Tree] (config>service>vprn>if>ipsec>ipsec-tunnel>icmp-gen>frag-required message-count)
[Tree] (config>service>ies>if>ipsec>ipsec-tunnel>icmp-gen>frag-required message-count)
Full Context
configure router interface ipsec ipsec-tunnel icmp-generation frag-required message-count
configure service vprn interface sap ip-tunnel icmp-generation frag-required message-count
configure ipsec tunnel-template icmp-generation frag-required message-count
configure service vprn interface sap ipsec-tunnel icmp-generation frag-required message-count
configure service vprn interface ipsec ipsec-tunnel icmp-generation frag-required message-count
configure service ies interface ipsec ipsec-tunnel icmp-generation frag-required message-count
Description
This command configures the maximum number of ICMP Destination Unreachable "fragmentation needed and DF set" messages (type 3, code 4) that can be sent during the period specified by the interval seconds command.
Default
message-count 100
Parameters
- number
-
Specifies the number of ICMP Destination Unreachable "fragmentation needed and DF set" messages that are transmitted within the interval seconds command time.
Platforms
VSR
- configure service ies interface ipsec ipsec-tunnel icmp-generation frag-required message-count
- configure router interface ipsec ipsec-tunnel icmp-generation frag-required message-count
- configure service vprn interface ipsec ipsec-tunnel icmp-generation frag-required message-count
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
- configure ipsec tunnel-template icmp-generation frag-required message-count
- configure service vprn interface sap ip-tunnel icmp-generation frag-required message-count
- configure service vprn interface sap ipsec-tunnel icmp-generation frag-required message-count
message-digest-key
message-digest-key
Syntax
message-digest-key keyid md5 [ key | hash-key] [hash | hash2 | custom]
no message-digest-key keyid
Context
[Tree] (config>service>vprn>ospf>area>virtual-link message-digest-key)
[Tree] (config>service>vprn>ospf>area>sham-link message-digest-key)
[Tree] (config>service>vprn>ospf>area>if message-digest-key)
Full Context
configure service vprn ospf area virtual-link message-digest-key
configure service vprn ospf area sham-link message-digest-key
configure service vprn ospf area interface message-digest-key
Description
This command configures a message digest key when MD5 authentication is enabled on the interface, virtual-link or sham-link. Multiple message digest keys can be configured.
This command is not valid in the OSPF3 context.
The no form of this command removes the message digest key identified by the key-id.
Default
No message digest keys are defined.
Parameters
- keyid
-
Specifies the key ID. The keyid is expressed as a decimal integer.
- md5 key
-
Specifies the MD5 key. The key can be any alphanumeric string up to 16 characters in length.
- md5 hash-key
-
Specifies the MD5 hash key. The key can be any combination of ASCII characters up to 32 characters in length (encrypted). If spaces are used in the string, enclose the entire string in quotation marks (‟ ”).
This is useful when a user must configure the parameter, but, for security purposes, the actual unencrypted key value is not provided.
- hash
-
Specifies the key is entered in an encrypted form. If the hash parameter is not used, the key is assumed to be in a non-encrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash parameter specified.
- hash2
-
Specifies the key is entered in a more complex encrypted form that involves more variables than the key value alone, meaning that the hash2 encrypted variable cannot be copied and pasted. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- custom
-
Specifies the custom encryption to management interface.
Platforms
All
message-digest-key
Syntax
message-digest-key key-id md5 [key | hash-key | hash2-key] [hash | hash2 | custom]
no message-digest-key key-id
Context
[Tree] (config>router>ospf>area>virtual-link message-digest-key)
[Tree] (config>router>ospf>area>interface message-digest-key)
Full Context
configure router ospf area virtual-link message-digest-key
configure router ospf area interface message-digest-key
Description
This command configures a message digest key when MD5 authentication is enabled on the interface. Multiple message digest keys can be configured.
The no form of this command removes the message digest key identified by the key-id.
By default, no message keys are defined.
Parameters
- key-id
-
Specifies the key ID. The keyid is expressed as a decimal integer.
- key
-
Specifies the MD5 key. The key can be any alphanumeric string up to 16 characters in length.
- hash-key | hash2-key
-
Specifies the MD5 hash or hash2 key. the hash key. The key can be any combination of ASCII characters up to 32 (hash1-key) or 55 (hash2-key) characters in length (encrypted). If spaces are used in the string, enclose the entire string in quotation marks (‟ ”).
This is useful when a user must configure the parameter, but, for security purposes, the actual unencrypted key value is not provided.
- hash
-
Specifies the key is entered in an encrypted form. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- hash2
-
Specifies the key is entered in a more complex encrypted form that involves more variables than the key value alone, meaning that the hash2 encrypted variable cannot be copied and pasted. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- custom
-
Specifies the custom encryption to management interface.
Platforms
All
message-fast-tx
message-fast-tx
Syntax
message-fast-tx time
no message-fast-tx
Context
[Tree] (config>system>lldp message-fast-tx)
Full Context
configure system lldp message-fast-tx
Description
This command configures the duration of the fast transmission period.
Default
no message-fast-tx
Parameters
- time
-
Specifies the fast transmission period in seconds.
Platforms
All
message-fast-tx-init
message-fast-tx-init
Syntax
message-fast-tx-init count
no message-fast-tx-init
Context
[Tree] (config>system>lldp message-fast-tx-init)
Full Context
configure system lldp message-fast-tx-init
Description
This command configures the number of LLDPDUs to send during the fast transmission period.
Default
no message-fast-tx-init
Parameters
- count
-
Specifies the number of LLDPDUs to send during the fast transmission period.
Platforms
All
message-interval
message-interval
Syntax
message-interval {[seconds] [milliseconds milliseconds]}
no message-interval
Context
[Tree] (config>service>ies>if>ipv6>vrrp message-interval)
Full Context
configure service ies interface ipv6 vrrp message-interval
Description
This command sets the advertisement timer and indirectly sets the master down timer on the virtual router instance. The message-interval setting must be the same for all virtual routers participating as a virtual router. Any VRRP advertisement message received with an Advertisement Interval field different than the virtual router instance configured message-interval value will be silently discarded.
The message-interval command is available in both non-owner and owner vrrp virtual-router-id nodal contexts. If the message-interval command is not executed, the default message interval of 1 second will be used.
The no form of this command restores the default message interval value of 1 second to the virtual router instance.
Default
message-interval 1
Parameters
- seconds
-
The number of seconds that will transpire before the advertisement timer expires.
- milliseconds milliseconds
-
Specifies the time interval, in milliseconds, between sending advertisement messages.
Platforms
All
message-interval
Syntax
message-interval {[seconds] [milliseconds milliseconds]}
no message-interval
Context
[Tree] (config>service>ies>if>vrrp message-interval)
Full Context
configure service ies interface vrrp message-interval
Description
This command sets the advertisement timer and indirectly sets the master down timer on the virtual router instance. The message-interval setting must be the same for all virtual routers participating as a virtual router. Any VRRP advertisement message received with an Advertisement Interval field different than the virtual router instance configured message-interval value will be silently discarded.
The message-interval command is available in both non-owner and owner vrrp virtual-router-id nodal contexts. If the message-interval command is not executed, the default message interval of 1 second will be used.
The no form of this command restores the default message interval value of 1 second to the virtual router instance.
Parameters
- seconds
-
The number of seconds that will transpire before the advertisement timer expires.
- milliseconds milliseconds
-
Specifies the time interval, in milliseconds, between sending advertisement messages. This parameter is not supported on non-redundant chassis.
Platforms
All
message-interval
Syntax
message-interval {[seconds] [milliseconds milliseconds]}
no message-interval
Context
[Tree] (config>service>vprn>if message-interval)
[Tree] (config>service>vprn>if>ipv6>vrrp message-interval)
Full Context
configure service vprn interface message-interval
configure service vprn interface ipv6 vrrp message-interval
Description
This command sets the advertisement timer and indirectly sets the master down timer on the virtual router instance. The message-interval setting must be the same for all virtual routers participating as a virtual router. Any VRRP advertisement message received with an Advertisement Interval field different than the virtual router instance configured message-interval value will be silently discarded.
The message-interval command is available in both non-owner and owner vrrp virtual-router-id nodal contexts. If the message-interval command is not executed, the default message interval of 1 second will be used.
The no form of this command restores the default message interval value of 1 second to the virtual router instance.
Parameters
- seconds
-
The number of seconds that will transpire before the advertisement timer expires.
- milliseconds milliseconds
-
Specifies the time interval, in milliseconds, between sending advertisement messages. This parameter is not supported on single-slot chassis.
Platforms
All
message-interval
Syntax
message-interval {[seconds] [milliseconds milliseconds]}
no message-interval
Context
[Tree] (config>router>if>ipv6>vrrp message-interval)
[Tree] (config>router>if>vrrp message-interval)
Full Context
configure router interface ipv6 vrrp message-interval
configure router interface vrrp message-interval
Description
This command configures the administrative advertisement message timer used by the master virtual router instance to send VRRP advertisement messages and to derive the master down timer as backup.
For an owner virtual router instance, the administrative advertisement timer directly sets the operational advertisement timer and indirectly sets the master down timer for the virtual router instance.
Non-owner virtual router instances usage of the message-interval setting is dependent on the state of the virtual router (master or backup) and the state of the master-int-inherit parameter.
-
When a non-owner is operating as master for the virtual router, the configured message-interval is used as the operational advertisement timer similar to an owner virtual router instance. The master-int-inherit command has no effect when operating as master.
-
When a non-owner is in the backup state with master-int-inherit disabled, the configured message-interval value is used to match the incoming VRRP advertisement message advertisement interval field. If the locally configured message interval does not match the advertisement interval field, the VRRP advertisement is discarded.
-
When a non-owner is in the backup state with master-int-inherit enabled, the configured message-interval is ignored. The master down timer is indirectly derived from the incoming VRRP advertisement message advertisement interval field value.
VRRP advertisements messages that are fragmented, or contain IP options (IPv4), or contain extension headers (IPv6) require a longer message interval to be configured.
The in-use value of the message interval is used to derive the master down timer to be used when the virtual router is operating in backup mode based on the following formula:
(3x (in-use message interval) + skew time)
The skew time portion is used to slow down virtual routers with relatively low priority values when competing in the master election process.
The command is available in both non-owner and owner vrrp nodal contexts.
By default, a message-interval of 1 second is used.
The no form of the command reverts to the default value.
Default
message-interval 1 — Advertisement timer set to 1 second.
Parameters
- seconds
-
The number of seconds that will transpire before the advertisement timer expires expressed as a decimal integer.
- milliseconds
-
Specifies the time interval, in milliseconds, between sending advertisement messages.
Platforms
All
message-length
message-length
Syntax
message-length message-length
no message-length
Context
[Tree] (config>service>sdp>keep-alive message-length)
Full Context
configure service sdp keep-alive message-length
Description
This command configures the SDP monitoring keepalive request message length transmitted.
The no form of this command reverts the message-length octets value to the default setting.
Default
no message-length — The message length should be equal to the SDP’s operating path MTU as configured in the config>service>sdp path-mtu command. If the default size is overridden, the actual size used will be the smaller of the operational SDP ID Path MTU and the size specified.
Parameters
- message-length
-
Specifies the size of the keepalive request messages in octets, expressed as a decimal integer. The size keyword overrides the default keepalive message size.
Platforms
All
message-path
message-path
Syntax
message-path sap-id
no message-path
Context
[Tree] (config>service>ies>sub-if>grp-if>srrp message-path)
[Tree] (config>service>vprn>sub-if>grp-if>srrp message-path)
Full Context
configure service ies subscriber-interface group-interface srrp message-path
configure service vprn subscriber-interface group-interface srrp message-path
Description
This command defines a specific SAP for SRRP in-band messaging. A message-path SAP must be defined prior to activating the SRRP instance. The defined SAP must exist on the SRRP instances group IP interface for the command to succeed and cannot currently be associated with any dynamic or static subscriber hosts. Once a group IP interface SAP has been defined as the transmission path for SRRP Advertisement messages, it cannot be administratively shutdown, will not support static or dynamic subscriber hosts and cannot be removed from the group IP interface.
The SRRP instance message-path command may be executed at any time on the SRRP instance. Changing the message SAP fails if a dynamic or static subscriber host is associated with the new SAP. Once successfully changed, the SRRP instance immediately disables anti-spoof on the SAP and starts sending SRRP Advertisement messages, if the SRRP instance is activated.
Changing the current SRRP message SAP on an active pair of routers should be done in the following manner:
-
Shutdown the backup SRRP instance.
-
Change the message SAP on the shutdown node.
-
Change the message SAP on the active master node.
-
Re-activate the shutdown SRRP instance.
Shutting down the backup SRRP instance prevents the SRRP instances from becoming master due to temporarily using differing message path SAPs.
If an MCS peering is operational between the redundant nodes and the SRRP instance has been associated with the peering, the designated message path SAP is sent from each member.
The no form of this command can only be executed when the SRRP instance is shutdown. Executing no message-path allows the existing SAP to be used for subscriber management functions. A new message-path SAP must be defined prior to activating the SRRP instance.
Parameters
- sap-id
-
Specifies the physical port identifier portion of the SAP definition.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
message-retransmit
message-retransmit
Syntax
message-retransmit [timeout timeout] [retry-count value]
no message-retransmit
Context
[Tree] (config>subscr-mgmt>gtp>peer-profile message-retransmit)
Full Context
configure subscriber-mgmt gtp peer-profile message-retransmit
Description
This command configures the retry-count and response-timeout for GTP messages.
The no form of this command reverts to the default values.
Default
message-retransmit timeout 5 retry-count 3
Parameters
- timeout
-
Specifies the interval, in seconds, between retransmission of signaling request messages towards the same peer Mobile Gateway.
- value
-
Specifies the number of times a signaling request message is transmitted towards the same peer Mobile Gateway.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
message-severity-level
message-severity-level
Syntax
message-severity-level
Context
[Tree] (config>system>management-interface>cli>md-cli>environment message-severity-level)
Full Context
configure system management-interface cli md-cli environment message-severity-level
Description
This command configures the message severity level.
Platforms
All
message-size
message-size
Syntax
message-size max-num-of-routes
no message-size
Context
[Tree] (config>service>vprn>rip message-size)
[Tree] (config>service>vprn>ripng>group>neighbor message-size)
[Tree] (config>service>vprn>rip>group message-size)
[Tree] (config>service>vprn>ripng message-size)
[Tree] (config>service>vprn>rip>group>neighbor message-size)
[Tree] (config>service>vprn>ripng>group message-size)
Full Context
configure service vprn rip message-size
configure service vprn ripng group neighbor message-size
configure service vprn rip group message-size
configure service vprn ripng message-size
configure service vprn rip group neighbor message-size
configure service vprn ripng group message-size
Description
This command sets the maximum number of routes per RIP update message.
The no form of this command resets the maximum number of routes back to the default of 25.
Default
no message-size
Parameters
- size
-
An Integer.
Platforms
All
message-size
Syntax
message-size max-num-of-routes
no message-size
Context
[Tree] (config>router>rip>group>neighbor message-size)
[Tree] (config>router>rip message-size)
[Tree] (config>router>rip>group message-size)
[Tree] (config>router>ripng>group message-size)
[Tree] (config>router>ripng message-size)
[Tree] (config>router>ripng>group>neighbor message-size)
Full Context
configure router rip group neighbor message-size
configure router rip message-size
configure router rip group message-size
configure router ripng group message-size
configure router ripng message-size
configure router ripng group neighbor message-size
Description
This command configures the maximum number of routes per RIP update message.
The no form of the command reverts to the default value.
Default
message-size 25
Parameters
- max-num-of-routes
-
The maximum number of RIP routes per RIP update message expressed as a decimal integer.
Platforms
All
message-timeout
message-timeout
Syntax
message-timeout seconds
Context
[Tree] (config>li>x-interfaces>x1>timeouts message-timeout)
Full Context
configure li x-interfaces x1 timeouts message-timeout
Description
This command configures the maximum time that the LIC must reply to an X1 message. If the timer expires, the session is released.
Parameters
- seconds
-
Specifies the maximum timeout value, in seconds.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
message-type
message-type
Syntax
message-type [ccr] [cca] [rar] [raa] [ asr] [asa] [aar] [aaa]
message-type all
no message-type
Context
[Tree] (debug>diam>diam-peer-plcy>avp-match message-type)
Full Context
debug diameter diameter-peer-policy avp-match message-type
Description
This command specifies the message type match criteria for AVP value matching. Only specified diameter application messages are used for AVP value matching. This is a mandatory criteria in an avp-match id command.
This command does not restrict the debug output to the specified messages.
Parameters
- ccr
-
credit control request
- cca
-
credit control answer
- rar
-
re-authentication request
- raa
-
re-authentication answer
- asr
-
abort session request
- asa
-
abort session answer
- aar
-
aa request
- aaa
-
aa answer
- all
-
all message types
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
message-type
Syntax
message-type [ccr] [cca] [cer] [cea] [ dwr] [dwa] [dpr] [dpa] [rar] [ raa] [asr] [asa] [aar] [aaa]
message-type all
no message-type
Context
[Tree] (debug>diam message-type)
[Tree] (debug>diam>diam-peer-plcy message-type)
Full Context
debug diameter message-type
debug diameter diameter-peer-policy message-type
Description
This command restricts the debug output to the specified message types.
When specified within a diameter peer policy, it overrides the message type configuration at the debug>diam level for messages received and sent on that diameter peer policy.
The no form of this command removes the message type from the debug configuration.
Parameters
- ccr
-
credit control request
- cca
-
credit control answer
- cer
-
capabilities exchange request
- cea
-
capabilities exchange answer
- dwr
-
device watchdog request
- dwa
-
device watchdog answer
- dpr
-
disconnect peer request
- dpa
-
disconnect peer answer
- rar
-
re-authentication request
- raa
-
re-authentication answer
- asr
-
abort session request
- asa
-
abort session answer
- aar
-
aa request
- aaa
-
aa answer
- all
-
all message types
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
message-type
Syntax
message-type
Context
[Tree] (config>app-assure>group>statistics>tca>gtp-filter message-type)
Full Context
configure application-assurance group statistics threshold-crossing-alert gtp-filter message-type
Description
This command configures a TCA for the counter capturing hits due to the GTP filter message type.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
message-type
Syntax
message-type
Context
[Tree] (config>app-assure>group>gtp>gtp-filter message-type)
Full Context
configure application-assurance group gtp gtp-filter message-type
Description
This command specifies the context for configuration of GTP message-type filtering. If no message-type is specified within a filter, then all GTP message types are allowed.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
message-type-gtpv2
message-type-gtpv2
Syntax
message-type-gtpv2
Context
[Tree] (config>app-assure>group>statistics>tca>gtp-filter message-type-gtpv2)
Full Context
configure application-assurance group statistics threshold-crossing-alert gtp-filter message-type-gtpv2
Description
This command configures a TCA for the counter capturing hits due to the GTPv2 message type filter.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
message-type-gtpv2
Syntax
message-type-gtpv2
Context
[Tree] (config>app-assure>group>gtp>gtp-fltr message-type-gtpv2)
Full Context
configure application-assurance group gtp gtp-filter message-type-gtpv2
Description
This command specifies the context for the configuration of GTP-v2 message-type filtering. If no message-type-gtpv2 is specified within a filter, then all GTP message types are allowed, except for the messages that are dropped by GTP-C inspection because they violate the expected GTP protocol for the deployment interface (for example, roaming deployment).
The gtpc-inspection command must be enabled before configuring message-type-gtpv2 filtering.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
messages
messages
Syntax
[no] messages
Context
[Tree] (debug>router>ldp>peer>event messages)
[Tree] (debug>router>ldp>if>event messages)
Full Context
debug router ldp peer event messages
debug router ldp interface event messages
Description
This command displays specific information (for example, message type, source, and destination) regarding LDP messages sent to and received from LDP peers.
The no form of the command disables debugging output for LDP messages.
Platforms
All
meta-data
meta-data
Syntax
meta-data
Context
[Tree] (config>subscr-mgmt>isa-svc-chain>vas-filter>entry>action>insert-nsh meta-data)
Full Context
configure subscriber-mgmt isa-service-chaining vas-filter entry action insert-nsh meta-data
Description
Commands in this context configure opaque metadata to be inserted in NSH in the steered traffic if the forward action indicates NSH insertion.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
metering-process
metering-process
Syntax
metering-process {standard | fp-accelerated}
Context
[Tree] (config>cflowd>sample-profile metering-process)
Full Context
configure cflowd sample-profile metering-process
Description
This command specifies the method used to process cflowd samples.
Default
metering-process standard
Parameters
- standard
-
Specifies that the samples are extracted at the CPM and are processed there.
- fp-accelerated
-
Specifies to use FP acceleration for cflowd processing, in which flow processing and reporting is performed by the FP complex on the CPM.
Platforms
7750 SR-7s, 7950 XRS-20e
metric
metric
Syntax
metric value
no metric
Context
[Tree] (config>service>vpls>sap>spb>level metric)
[Tree] (config>service>vpls>spoke-sdp>spb>level metric)
Full Context
configure service vpls sap spb level metric
configure service vpls spoke-sdp spb level metric
Description
This configures metric for this SPB interface SAP/spoke-sdp. This command is valid only for interfaces on control B-VPLS.
Parameters
- value
-
Specifies the configuration metric value.
Platforms
All
metric
Syntax
metric metric-value
no metric [metric-value]
Context
[Tree] (config>service>vprn>static-route-entry>indirect metric)
[Tree] (config>service>vprn>static-route-entry>next-hop metric)
[Tree] (config>service>vprn>static-route-entry>grt metric)
[Tree] (config>service>vprn>static-route-entry>ipsec-tunnel metric)
[Tree] (config>service>vprn>static-route-entry>black-hole metric)
Full Context
configure service vprn static-route-entry indirect metric
configure service vprn static-route-entry next-hop metric
configure service vprn static-route-entry grt metric
configure service vprn static-route-entry ipsec-tunnel metric
configure service vprn static-route-entry black-hole metric
Description
This command specifies the cost metric for the static route, expressed as a decimal integer. This value is used when importing the static route into other protocols such as OSPF. When the metric is configured as 0 then the metric configured in OSPF, default-import-metric, applies. When modifying the metric of an existing static route, the preference will not change unless specified. This value is also used to determine which static route to install in the forwarding table.
If there are multiple static routes with the same preference but different metrics then the lower cost (metric) route will be installed.
The no form of this command returns the metric to the default value
Default
metric 1
Parameters
- metric-value
-
Specifies the cost metric value.
Platforms
All
metric
Syntax
metric metric
no metric
Context
[Tree] (config>service>vprn>isis>if>level metric)
Full Context
configure service vprn isis interface level metric
Description
This command configures the metric used for the level on the interface.
In order to calculate the lowest cost to reach a given destination, each configured level on each interface must have a cost. The costs for each level on an interface may be different.
If the metric is not configured, the default of 10 is used unless reference bandwidth is configured.
The no form of this command reverts to the default value.
Default
no metric
Parameters
- metric
-
The metric assigned for this level on this interface.
Platforms
All
metric
Syntax
metric metric
no metric
Context
[Tree] (config>service>vprn>ospf>area>if metric)
[Tree] (config>service>vprn>ospf3>area>if metric)
[Tree] (config>service>vprn>ospf>area>sham-link metric)
Full Context
configure service vprn ospf area interface metric
configure service vprn ospf3 area interface metric
configure service vprn ospf area sham-link metric
Description
This command configures an explicit route cost metric for the OSPF interface that overrides the metrics calculated based on the speed of the underlying link.
The no form of this command deletes the manually configured interface metric, so the interface uses the computed metric based on the reference-bandwidth command setting and the speed of the underlying link.
Default
no metric
Parameters
- metric
-
The metric to be applied to the interface expressed as a decimal integer.
Platforms
All
metric
Syntax
metric metric
no metric
Context
[Tree] (config>router>mpls>lsp-template metric)
[Tree] (config>router>mpls>static-lsp metric)
[Tree] (config>router>mpls>lsp metric)
Full Context
configure router mpls lsp-template metric
configure router mpls static-lsp metric
configure router mpls lsp metric
Description
This command allows the user to override the LSP operational metric with a constant administrative value that will not change regardless of the actual path the LSP is using over its lifetime.
The LSP operational metric will match the metric the active path of this LSP is using at any given time. For a CSPF LSP, this metric represents the cumulative IGP metric of all the links the active path is using. If CSPF for this LSP is configured to use the TE metric, the LSP operational metric is set to the maximum value. For a non-CSPF LSP, the operational metric is the shortest IGP cost to the destination of the LSP.
The LSP operational metric is used by some applications to select an LSP among a set of LSPs that are destined to the same egress router. The LSP with the lowest operational metric will be selected. If more than one LSP with the same lowest LSP metric exists, the LSP with the lowest tunnel index will be selected. The configuration of a constant metric by the user will make sure the LSP always maintains its preference in this selection regardless of the path it is using at any given time. Applications that use the LSP operational metric include LDP-over-RSVP, VPRN auto-bind, and IGP, BGP and static route shortcuts.
The no form of this command disables the administrative LSP metric and reverts to the default setting in which the metric value will represent the LSP metric returned by MPLS. The same behavior is obtained if the user entered a metric of value zero (0).
Default
no metric. The LSP operational metric defaults to the metric returned by MPLS.
Parameters
- metric
-
Specifies the integer value which specifies the value of the LSP administrative metric. A value of zero command reverts to the default setting and disables the administrative LSP metric.
Platforms
All
metric
Syntax
metric metric
no metric
Context
[Tree] (config>router>mpls>fwd-policies>fwd-policy metric)
Full Context
configure router mpls forwarding-policies forwarding-policy metric
Description
This command configures the metric of an MPLS forwarding policy.
The metric parameter is supported with the endpoint policy only and is inherited by the routes which resolve their next hop to this policy.
The no form of this command removes the metric parameter from the MPLS forwarding policy.
Parameters
- metric
-
Specifies the metric value.
Platforms
All
metric
Syntax
metric metric
no metric [metric]
Context
[Tree] (config>router>static-route-entry>next-hop metric)
[Tree] (config>router>static-route-entry>indirect metric)
[Tree] (config>router>static-route-entry>black-hole metric)
Full Context
configure router static-route-entry next-hop metric
configure router static-route-entry indirect metric
configure router static-route-entry black-hole metric
Description
This command specifies the cost metric for the static route, expressed as a decimal integer. This value is used when importing the static route into other protocols such as OSPF. When the metric is configured as 0 then the metric configured in OSPF, default-import-metric, applies. When modifying the metric of an existing static route, the preference will not change unless specified. This value is also used to determine which static route to install in the forwarding table.
If there are multiple static routes with the same preference but different metrics then the lower cost (metric) route will be installed.
The no form of this command returns the metric to the default value
Default
metric 1
Parameters
- metric
-
Specifies the cost metric value.
Platforms
All
metric
Syntax
metric metric
no metric
Context
[Tree] (config>service>sdp metric)
Full Context
configure service sdp metric
Description
This command specifies the metric to be used within the tunnel table manager for decision making purposes. When multiple SDPs going to the same destination exist, this value is used as a tie-breaker by tunnel table manager users such as MP-BGP to select the route with the lower value.
Parameters
- metric
-
Specifies the SDP metric.
Platforms
All
metric
Syntax
metric metric
no metric
Context
[Tree] (config>router>isis>if>level metric)
Full Context
configure router isis interface level metric
Description
This command configures the metric used for the level on the interface.
In order to calculate the lowest cost to reach a given destination, each configured level on each interface must have a cost. The costs for each level on an interface may be different.
If the metric is not configured, the default of 10 is used unless reference bandwidth is configured.
The no form of this command reverts to the default value.
Default
metric 10
Parameters
- metric
-
Specifies the metric assigned for this level on this interface.
Platforms
All
metric
Syntax
metric metric
no metric
Context
[Tree] (config>router>ospf>area>interface metric)
[Tree] (config>router>ospf3>area>interface metric)
Full Context
configure router ospf area interface metric
configure router ospf3 area interface metric
Description
This command configures an explicit route cost metric for the OSPF interface that overrides the metrics calculated based on the speed of the underlying link.
The no form of this command deletes the manually configured interface metric, so the interface uses the computed metric based on the reference-bandwidth command setting and the speed of the underlying link.
Default
no metric
Parameters
- metric
-
Specifies the metric to be applied to the interface expressed as a decimal integer.
Platforms
All
metric
Syntax
metric metric [equal | or-higher | or-lower]
no metric
Context
[Tree] (config>router>policy-options>policy-statement>entry>from metric)
Full Context
configure router policy-options policy-statement entry from metric
Description
This command matches BGP routes based on local preference (the value in the MULTI_EXIT_DISC attribute).
If no comparison qualifiers are present (equal, or-higher, or-lower), then equal is the implied default.
A non-BGP route does not match a policy entry if it contains the metric command. In addition, a BGP route without a MED attribute also does not match a policy entry if it contains a metric command.
Default
no metric
Parameters
- metric
-
Specifies the MED value.
- equal
-
Specifies that matched routes should have the same MED as the value specified.
- or-higher
-
Specifies that matched routes should have the same or a greater MED as the value specified.
- or-lower
-
Specifies that matched routes should have the same or a lower MED as the value specified.
Platforms
All
metric
Syntax
metric {add | subtract} metric
metric set [igp | metric-value]
no metric
Context
[Tree] (config>router>policy-options>policy-statement>default-action metric)
[Tree] (config>router>policy-options>policy-statement>entry>action metric)
Full Context
configure router policy-options policy-statement default-action metric
configure router policy-options policy-statement entry action metric
Description
In a BGP import or export policy, this command assigns a MED value to routes matched by the policy statement entry. The MED value may be set to a fixed value (overriding the received value), set to the routing table cost of the route used to resolve the next hop of the BGP route, or modified by adding or subtracting a fixed value offset.
The no form of this command removes the MED attribute from the matched routes.
Default
no metric
Parameters
- add
-
Specifies that an integer is added to any existing metric. If the result of the addition results in a number greater than 4294967295, the value 4294967295 is used.
- subtract
-
Specified integer is subtracted from any existing metric. If the result of the subtraction results in a number less than 0, the value of 0 is used.
- set
-
Specifies that integer replaces any existing metric.
- igp
-
Sets the MED value to the routing table cost of the route used to resolve the next hop of the BGP route.
- metric
-
Specifies the metric modifier expressed as a decimal integer.
Platforms
All
metric
Syntax
metric metric
no metric
Context
[Tree] (config>router>isis>srv6>msloc>level metric)
[Tree] (config>router>isis>srv6>locator>level metric)
Full Context
configure router isis segment-routing-v6 micro-segment-locator level metric
configure router isis segment-routing-v6 locator level metric
Description
This command configures the Level 1 or Level 2 metric to advertise in the locator TLV.
The no form of this command takes the value from the configuration of the Level 1 or Level 2 MT0 default metric parameter config>router>isis>level>default-metric which has a default value of 10.
Default
no metric
Parameters
- metric
-
Specifies the configuration metric value.
Platforms
7450 ESS, 7750 SR, 7750 SR-s, 7950 XRS, VSR
metric-in
metric-in
Syntax
metric-in metric
no metric-in
Context
[Tree] (config>service>vprn>ripng>group>neighbor metric-in)
[Tree] (config>service>vprn>ripng>group metric-in)
[Tree] (config>service>vprn>rip>group metric-in)
[Tree] (config>service>vprn>rip metric-in)
[Tree] (config>service>vprn>ripng metric-in)
[Tree] (config>service>vprn>rip>group>neighbor metric-in)
Full Context
configure service vprn ripng group neighbor metric-in
configure service vprn ripng group metric-in
configure service vprn rip group metric-in
configure service vprn rip metric-in
configure service vprn ripng metric-in
configure service vprn rip group neighbor metric-in
Description
This command sets the metric added to routes received from a RIP neighbor.
The no form of this command reverts the metric value back to the default.
Default
no metric-in
Parameters
- metric
-
The value added to the metric of routes received from a RIP neighbor, expressed as a decimal integer.
Platforms
All
metric-in
Syntax
metric-in metric
no metric-in
Context
[Tree] (config>router>ripng metric-in)
[Tree] (config>router>rip>group metric-in)
[Tree] (config>router>rip>group>neighbor metric-in)
[Tree] (config>router>ripng>group>neighbor metric-in)
[Tree] (config>router>rip metric-in)
[Tree] (config>router>ripng>group metric-in)
Full Context
configure router ripng metric-in
configure router rip group metric-in
configure router rip group neighbor metric-in
configure router ripng group neighbor metric-in
configure router rip metric-in
configure router ripng group metric-in
Description
This command configures the metric added to routes received from a RIP neighbor.
When applying an export policy to a RIP configuration, the policy overrides the metric values determined through calculations involving the metric-in and metric-out values.
The no form of the command reverts to the default value.
Default
metric-in 1
Parameters
- metric
-
Specifies the value added to the metric of routes received from a RIP neighbor expressed as a decimal integer.
Platforms
All
metric-out
metric-out
Syntax
metric-out metric
no metric-out
Context
[Tree] (config>service>vprn>ripng>group>neighbor metric-out)
[Tree] (config>service>vprn>rip>group metric-out)
[Tree] (config>service>vprn>rip>group>neighbor metric-out)
[Tree] (config>service>vprn>ripng>group metric-out)
[Tree] (config>service>vprn>rip metric-out)
[Tree] (config>service>vprn>ripng metric-out)
Full Context
configure service vprn ripng group neighbor metric-out
configure service vprn rip group metric-out
configure service vprn rip group neighbor metric-out
configure service vprn ripng group metric-out
configure service vprn rip metric-out
configure service vprn ripng metric-out
Description
This command sets the metric added to routes exported into RIP and advertised to RIP neighbors.
The no form of this command removes the command from the config and resets the metric-in value back to the default.
Default
no metric-out
Parameters
- metric
-
The value added to the metric for routes exported into RIP and advertised to RIP neighbors, expressed as a decimal integer.
Platforms
All
metric-out
Syntax
metric-out metric
no metric-out
Context
[Tree] (config>router>ripng>group metric-out)
[Tree] (config>router>rip>group metric-out)
[Tree] (config>router>rip>group>neighbor metric-out)
[Tree] (config>router>rip metric-out)
[Tree] (config>router>ripng metric-out)
[Tree] (config>router>ripng>group>neighbor metric-out)
Full Context
configure router ripng group metric-out
configure router rip group metric-out
configure router rip group neighbor metric-out
configure router rip metric-out
configure router ripng metric-out
configure router ripng group neighbor metric-out
Description
This command configures the metric assigned to routes exported into RIP and advertised to RIP neighbors.
When applying an export policy to a RIP configuration, the policy overrides the metric values determined through calculations involving the metric-in and metric-out values.
The no form of the command reverts to the default value.
Default
metric-out 1
Parameters
- metric
-
Specifies the value added to the metric for routes exported into RIP and advertised to RIP neighbors expressed as a decimal integer.
Platforms
All
metric-type
metric-type
Syntax
metric-type metric-type
no metric-type
Context
[Tree] (config>router>mpls>lsp-template metric-type)
[Tree] (config>router>mpls>lsp metric-type)
Full Context
configure router mpls lsp-template metric-type
configure router mpls lsp metric-type
Description
This command specifies the link metric type to use in the RSVP-TE LSP or SR-TE LSP path computation by either the local CSPF or the PCE.
The no form of this command returns the metric to its default value.
Default
metric-type igp
Parameters
- metric-type
-
Specifies the metric type for the LSP.
Platforms
All
metric-type
Syntax
metric-type {igp | te-metric | delay}
no metric-type
Context
[Tree] (config>router>fad>flex-algo metric-type)
Full Context
configure router flexible-algorithm-definitions flex-algo metric-type
Description
This command configures the type of metric for the flexible algorithm. The topology graph assumes that all links are configured with the correct metric type.
For example, if the flexible algorithm definition instructs the use of te-metric keyword, it is assumed that all links have te-metric configured. Links without the te-metric configuration are excluded from the flexible algorithm topology graph.
The no form of this command removes the configured metric type and sets it to its default value.
Default
metric-type igp
Parameters
- igp
-
Keyword to use the IGP metric for the flexible algorithm topology graph.
- te-metric
-
Keyword to use the TE metric for the flexible algorithm topology graph.
- delay
-
Keyword to use the delay metric for the flexible algorithm topology graph.
Platforms
All
mfib-allowed-mda-destinations
mfib-allowed-mda-destinations
Syntax
mfib-allowed-mda-destinations
Context
[Tree] (config>service>vpls>mesh-sdp>egress mfib-allowed-mda-destinations)
[Tree] (config>service>vpls>spoke-sdp>egress mfib-allowed-mda-destinations)
Full Context
configure service vpls mesh-sdp egress mfib-allowed-mda-destinations
configure service vpls spoke-sdp egress mfib-allowed-mda-destinations
Description
Commands in this context configure MFIB-allowed MDA destinations.
The allowed-mda-destinations node and the corresponding mda command are used on spoke and mesh SDP bindings to provide a list of MDA destinations in the chassis that are allowed as destinations for multicast streams represented by [*,g] and [s,g] multicast flooding records on the VPLS service. The MDA list only applies to IP multicast forwarding when IGMP snooping is enabled on the VPLS service. The MDA list has no effect on normal VPLS flooding such as broadcast, L2 multicast, unknown destinations or non-snooped IP multicast.
At the IGMP snooping level, a spoke or mesh SDP binding is included in the flooding domain for an IP multicast stream when it has either been defined as a multicast router port, received a IGMP query through the binding or has been associated with the multicast stream through an IGMP request by a host over the binding. Due to the dynamic nature of the way that a spoke or mesh SDP binding is associated with one or more egress network IP interfaces, the system treats the binding as appearing on all network ports. This causes all possible network destinations in the switch fabric to be included in the multicast streams flooding domain. The MDA destination list provides a simple mechanism that narrows the IP multicast switch fabric destinations for the spoke or mesh SDP binding.
If no MDAs are defined within the allowed-mda-destinations node, the system operates normally and will forward IP multicast flooded packets associated with the spoke or mesh SDP binding to all switch fabric taps containing network IP interfaces.
The MDA inclusion list should include all MDAs that the SDP binding may attempt to forward through. A simple way to ensure that an MDA that is not included in the list is not being used by the binding is to define the SDP the binding is associated with as MPLS and use an RSVP-TE LSP with a strict egress hop. The MDA associated with the IP interface defined as the strict egress hop should be present in the inclusion list. If the inclusion list does not currently contain the MDA that the binding is forwarding through, the multicast packets will not reach the destination represented by the binding.
By default, the MDA inclusion list is empty.
If an MDA is removed from the list, the MDA is automatically removed from the flooding domain of any snooped IP multicast streams associated with a destination on the MDA unless the MDA was the last MDA on the inclusion list. Once the inclusion list is empty, all MDAs are eligible for snooped IP multicast flooding for streams associated with the SDP binding.
Platforms
All
mfib-allowed-mda-destinations
Syntax
mfib-allowed-mda-destinations
Context
[Tree] (config>service>pw-template>egress mfib-allowed-mda-destinations)
Full Context
configure service pw-template egress mfib-allowed-mda-destinations
Description
Commands in this context configure MFIB-allowed XMA or MDA destinations.
The allowed-mda-destinations node and the corresponding mda command are used on spoke and mesh SDP bindings to provide a list of XMA or MDA destinations in the chassis that are allowed as destinations for multicast streams represented by [*,g] and [s,g] multicast flooding records on the VPLS service. The XMA or MDA list only applies to IP multicast forwarding when IGMP snooping is enabled on the VPLS service. The XMA or MDA list has no effect on normal VPLS flooding such as broadcast, Layer 2 multicast, unknown destinations or non-snooped IP multicast.
At the IGMP snooping level, a spoke or mesh SDP binding is included in the flooding domain for an IP multicast stream when it has either been defined as a multicast router port, received a IGMP query through the binding or has been associated with the multicast stream through an IGMP request by a host over the binding. Due to the dynamic nature of the way that a spoke or mesh SDP binding is associated with one or more egress network IP interfaces, the system treats the binding as appearing on all network ports. This causes all possible network destinations in the switch fabric to be included in the multicast streams flooding domain. The XMA or MDA destination list provides a simple mechanism that narrows the IP multicast switch fabric destinations for the spoke or mesh SDP binding.
If no XMAs or MDAs are defined within the allowed-mda-destinations node, the system operates normally and will forward IP multicast flooded packets associated with the spoke or mesh SDP binding to all switch fabric taps containing network IP interfaces.
The XMA or MDA inclusion list should include all XMAs or MDAs that the SDP binding may attempt to forward through. A simple way to ensure that an XMA or MDA that is not included in the list is not being used by the binding is to define the SDP the binding is associated with as MPLS and use an RSVP-TE LSP with a strict egress hop. The XMA or MDA associated with the IP interface defined as the strict egress hop should be present in the inclusion list.
If the inclusion list does not currently contain the XMA or MDA that the binding is forwarding through, the multicast packets will not reach the destination represented by the binding. By default, the XMA or MDA inclusion list is empty.
If an XMA or MDA is removed from the list, the XMA or MDA is automatically removed from the flooding domain of any snooped IP multicast streams associated with a destination on the XMA or MDA unless the XMA or MDA was the last XMA or MDA on the inclusion list. Once the inclusion list is empty, all XMAs or MDAs are eligible for snooped IP multicast flooding for streams associated with the SDP binding.
Platforms
All
mfib-ping
mfib-ping
Syntax
mfib-ping service service-id source src-ip destination mcast-address [size size] [ttl vc-label-ttl] [count send-count] [return-control] [timeout timeout] [interval interval]
Context
[Tree] (oam mfib-ping)
Full Context
oam mfib-ping
Description
This command determines the list of SAPs which egress a certain IP multicast stream (identified by source unicast and destination multicast IP addresses) within a VPLS service. An MFIB ping packet is always sent via the data plane.
An MFIB ping is forwarded across the VPLS following the MFIB. If an entry for the specified source unicast and destination multicast IP addresses exist in the MFIB for that VPLS, then the packet is forwarded along those paths, provided they are active. A response is generated only when there is an egress SAP binding for the specified IP multicast stream.
An MFIB ping reply can be sent using the data plane or the control plane. The return-control option configures the reply to be sent using the control plane. If return-control is not specified, the reply is sent using the data plane.
Parameters
- service-id
-
Specifies the service ID of the VPLS to diagnose or manage.
- src-ip
-
Specifies the source IP address for the OAM request.
- mcast-address
-
Specifies the destination multicast address for the OAM request.
- size
-
Specifies the multicast OAM request packet size, in octets, expressed as a decimal integer. The request payload is padded to the specified size with a 6-byte PAD header and a byte payload of 0xAA as necessary.
If the octet size specified is less than the minimum packet, the minimum sized packet necessary to send the request is used.
- vc-label-ttl
-
Specifies the TTL value in the VC label for the OAM request, expressed as a decimal integer.
- send-count
-
Specifies the number of messages to send, expressed as a decimal integer. The count parameter override the default number of message requests sent. Each message request must either time out or receive a reply before the next message request is sent.
The message interval value must be expired before the next message request is sent.
- return-control
-
Specifies that the OAM reply must be sent using the control plane instead of the data plane.
- timeout
-
Specifies the value used to override the default timeout value and is the amount of time that the router waits for a message reply after sending the next message request.
Upon the expiration of the message time out, the requesting router assumes that the message response is not received. A request timeout message is displayed by the CLI for each message request sent that expires. Any response received after the request times out is silently discarded.
- interval
-
Specifies the value used to override the default request message send interval and defines the minimum amount of time that must expire before the next message request is sent.
If the interval is set to 1 second where the timeout value is set to 10 seconds, then the maximum time between message requests is 10 seconds and the minimum is 1 second. This depends upon the receipt of a message reply corresponding to the outstanding message request.
Platforms
All
Output
The following output displays multicast FIB connectivity test information
Sample OutputA:ALA-A# oam mfib-ping service 10 source 10.10.10.1 destination 225.0.0.1 count 2
Seq Node-id Path Size RTT
-------------------------------------------------------------------------------
[Send request Seq. 1.]
1 51.51.51.51:sap1/1/1 Self 100 0ms
1 54.54.54.54:sap1/1/2 In-Band 100 20ms
1 54.54.54.54:sap1/1/3 In-Band 100 10ms
1 52.52.52.52:sap1/1/3 In-Band 100 20ms
[Send request Seq. 2.]
2 51.51.51.51:sap1/1/1 Self 100 0ms
2 52.52.52.52:sap1/1/2 In-Band 100 10ms
2 54.54.54.54:sap1/1/2 In-Band 100 10ms
2 52.52.52.52:sap1/1/3 In-Band 100 20ms
2 54.54.54.54:sap1/1/3 In-Band 100 30ms
-------------------------------------------------------------------------------
A:ALA-AIM# oam mfib-ping service 1 source 11.11.0.0 destination 224.0.0.1
Seq Node-id Path Size RTT
-------------------------------------------------------------------------------
[Send request Seq. 1.]
1 10.20.1.3:sap1/1/5:1 Not in MFIB Self 40 0ms
1 10.20.1.3:sap1/1/2:1 Self 40 10ms
[Echo replies received: 2]
-------------------------------------------------------------------------------
A:ALA-AIM#
mfib-table-high-wmark
mfib-table-high-wmark
Syntax
[no] mfib-table-high-wmark high-water-mark
Context
[Tree] (config>service>vpls mfib-table-high-wmark)
Full Context
configure service vpls mfib-table-high-wmark
Description
This command specifies the multicast FIB high watermark. When the percentage filling level of the multicast FIB exceeds the configured value, a trap is generated and a log entry is added.
The no form of this command reverts to the default.
Default
mfib-table-high-wmark 95
Parameters
- high-water-mark
-
Specifies the multicast FIB high watermark as a percentage.
Platforms
All
mfib-table-low-wmark
mfib-table-low-wmark
Syntax
[no] mfib-table-low-wmark low-water-mark
Context
[Tree] (config>service>vpls mfib-table-low-wmark)
Full Context
configure service vpls mfib-table-low-wmark
Description
This command specifies the multicast FIB low watermark. When the percentage filling level of the multicast FIB drops below the configured value, the corresponding trap is cleared and a log entry is added.
The no form of this command reverts to the default.
Default
mfib-table-low-wmark
Parameters
- low-water-mark
-
Specifies the multicast FIB low watermark as a percentage.
Platforms
All
mfib-table-size
mfib-table-size
Syntax
mfib-table-size size
no mfib-table-size
Context
[Tree] (config>service>vpls mfib-table-size)
Full Context
configure service vpls mfib-table-size
Description
This command specifies the maximum number of (s,g) entries in the multicast forwarding database (MFIB) for this VPLS instance.
The mfib-table-size parameter specifies the maximum number of multicast database entries for both learned and static multicast addresses for the VPLS instance. When a table-size limit is set on the mfib of a service which is lower than the current number of dynamic entries present in the mfib then the number of entries remains above the limit.
The no form of this command removes the configured maximum MFIB table size.
Default
no mfib-table-size
Parameters
- size
-
Specifies the maximum number of (s,g) entries allowed in the Multicast FIB
Platforms
All
mgmt-ethernet
mgmt-ethernet
Syntax
mgmt-ethernet [revert seconds]
no mgmt-ethernet
Context
[Tree] (config>redundancy mgmt-ethernet)
Full Context
configure redundancy mgmt-ethernet
Description
If the management Ethernet port on the active CPM goes down, this command allows the active CPM to be configured to use the management Ethernet port of the standby CPM.
The revert option allows the administrator to control when to revert back to the management Ethernet port of the primary CPM once it comes up again.
The no form of the command disables redundancy, so that connectivity to the active CPM is lost if its Ethernet port goes down.
Default
no mgmt-ethernet
Parameters
- seconds
-
Specifies the duration to wait (in seconds) before reverting back to the primary CPM’s management Ethernet port.
Platforms
7450 ESS, 7750 SR-7/12/12e, 7750 SR-7s, 7750 SR-14s, 7950 XRS
mh-mode
mh-mode
Syntax
mh-mode {access | network}
Context
[Tree] (config>service>vpls>bgp-evpn>vxlan mh-mode)
Full Context
configure service vpls bgp-evpn vxlan mh-mode
Description
This command configures multihoming mode.
Default
mh-mode access
Parameters
- access
-
When configured in this mode, the BGP-EVPN instance does not participate in multihoming procedures, such as processing DF election for the service or enabling local bias forwarding mode.
- network
-
When configured in this mode, the BGP-EVPN instance participates in multihoming procedures, such as processing DF election for the service or enable local bias forwarding mode.
In services with two VXLAN instances, only one of the two instances can be configured as network.
Platforms
All
mh-mode
Syntax
mh-mode {access | network}
Context
[Tree] (config>service>vpls>bgp-evpn>mpls mh-mode)
[Tree] (config>service>vpls>bgp-evpn>srv6 mh-mode)
Full Context
configure service vpls bgp-evpn mpls mh-mode
configure service vpls bgp-evpn segment-routing-v6 mh-mode
Description
This command configures each BGP-EVPN instance in a multi-instance EVPN VPLS service to behave as network or access.
You can only configure one network instance for the service. If the service has a provider tunnel enabled, it requires a network instance.
Default
mh-mode network
Parameters
- access
-
Specifies that the BGP-EVPN instance does not participate in multihoming procedures, such as DF election processing or local bias forwarding.
- network
-
Specifies that the BGP-EVPN instance participates in multihoming procedures, such as DF election processing or local bias forwarding.
In services with two instances, only one of the two instances can be configured as network.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
- configure service vpls bgp-evpn mpls mh-mode
7450 ESS, 7750 SR, 7750 SR-s, 7950 XRS, VSR
- configure service vpls bgp-evpn segment-routing-v6 mh-mode
mhf-creation
mhf-creation
Syntax
mhf-creation {default | none | explicit | static}
no mhf-creation
Context
[Tree] (cfg>eth-cfm>domain>assoc>bridge mhf-creation)
Full Context
configure eth-cfm domain association bridge-identifier mhf-creation
Description
This command defines the MIP method of creation. MIP creation mode and other factors are part of the MIP creation authority (association or default-domain) logic. The MIP creation algorithm may result in multiple potential MIPs. Only the lowest-level valid MIP is installed. The static creation mode is the exception to the single MIP installation rule.
Under the association context, the level level parameter is not supported as part of this command. The level is derived from the level configuration of the domain.
The no form of this command is only available under the association context, and reverts the current mode of creation to the default none. In order to transition to and from the static mode of operation, the active mhf-creation mode must be none.
Default
mhf-creation none
Parameters
- default
-
Specifies MHFs (MIPs) can be created for this SAP or spoke SDP without the requirement for a MEP at some lower MA level. If a lower-level MEP exists, the creation method will behave as explicit.
- none
-
Specifies that no MHFs (MIPs) can be created for this SAP or spoke SDP.
- explicit
-
Specifies that MHFs (MIPs) can be created for this SAP or spoke SDP only if a MEP is created at some lower MD Level. There must be at least one lower MD Level MEP provisioned on the same SAP or spoke SDP.
- static
-
Specifies the exact level of the MHF (MIP) that will be created for this SAP. Multiple MHFs (MIPs) are allowed as long as the MD Level hierarchy is properly configured for the particular Primary VLAN. Ingress MHFs (MIPs) with primary VLAN are not supported on SDP Bindings.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
mhf-creation
Syntax
mhf-creation {none | default | explicit | static} level level
no mhf-creation
Context
[Tree] (config>eth-cfm>default-domain>bridge-identifier mhf-creation)
Full Context
configure eth-cfm default-domain bridge-identifier mhf-creation
Description
This command defines the MIP method of creation. MIP creation mode and other factors are part of the MIP creation authority (association or default-domain) logic. The MIP creation algorithm may result in multiple potential MIPs. Only the lowest-level valid MIP is installed. The static creation mode is the exception to the single MIP installation rule.
Under the association context, the level level parameter is not supported as part of this command. The level is derived from the level configuration of the domain.
The no form of this command is only available under the association context, and reverts the current mode of creation to the default none. In order to transition to and from the static mode of operation, the active mhf-creation mode must be none.
Default
mhf-creation defer (config>eth-cfm>default-domain>bridge-identifier)
Parameters
- none
-
Specifies that no MHFs (MIPs) can be created for this SAP or spoke SDP.
- default
-
Specifies MHFs (MIPs) can be created for this SAP or spoke SDP without the requirement for a MEP at some lower MA level. If a lower-level MEP exists, the creation method will behave as explicit.
- explicit
-
Specifies that MHFs (MIPs) can be created for this SAP or spoke SDP only if a MEP is created at some lower MD Level. There must be at least one lower MD Level MEP provisioned on the same SAP or spoke SDP.
- defer
-
Defers the MIP creation process to the system-wide read-only values. This parameter is only configurable under the default-domain context.
- level
-
Specifies the requested level of the MIP. This is used by the MIP creation algorithm to determine its validity in comparison to other ETH-CFM MIPs in the same service. If level is configured as ‟defer”, the level value will be inherited from the global read-only system values, and ‟-1” will be stored as a MIB value in the table.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
micro-loop-avoidance
micro-loop-avoidance
Syntax
micro-loop-avoidance [fib-delay fib-delay]
no micro-loop-avoidance
Context
[Tree] (config>router>isis>segment-routing micro-loop-avoidance)
Full Context
configure router isis segment-routing micro-loop-avoidance
Description
This command enables, in the IGP instance, the micro-loop avoidance feature to prevent micro-loops from using Segment Routing (SR) loop-free tunnels for packets that are forwarded over SR IS-IS node SIDs.
When enabled, the behavior of the feature is triggered by the receipt of a single event on a on a P2P link or broadcast link with two neighbors:
-
link addition or restoration
-
link removal or failure
-
link metric change
IGP then performs the following procedures.
-
IGP runs the main SPF and LFA SPFs.
-
For a node or a prefix in which the SPF resulted in no change to its next hop(s) and metric(s), then IGP takes no action.
-
For a node or a prefix in which SPF resulted in a change to its next hop(s) or metric(s), IGP marks the route as eligible for micro-loop avoidance.
-
Activate, for each node SID that uses a micro-loop avoidance eligible route with ECMP next hops, the common set of next hops between the previous and new SPF.
-
Compute and activate, for each node SID which uses a micro-loop avoidance eligible route, with a single next hop loop-free SR tunnel that is applicable to the specific link event.
This tunnel acts the micro-loop avoidance primary path for the route and uses the same outgoing interface as the new computed primary next hop.
-
Program the TI-LFA, base LFA, or remote LFA backup path that protects the new primary next hop for the node SID.
-
-
Start the fib-delay timer to delay programming of new main and LFA SPF results into the FIB.
-
After the expiry of the fib-delay timer, program the new primary next hop(s) for node SIDs routes that were marked eligible for micro-loop avoidance procedures.
The no form of this command disables the micro-loop avoidance feature.
Default
no micro-loop-avoidance
Parameters
- fib-delay
-
Specifies the delay, in 100s of milliseconds, before the system programs the new next hops for the SR tunnel.
Platforms
All
micro-loop-avoidance
Syntax
[no] micro-loop-avoidance
Context
[Tree] (config>router>isis>flex-algos>flex-algo micro-loop-avoidance)
Full Context
configure router isis flexible-algorithms flex-algo micro-loop-avoidance
Description
This command enables flexible algorithms-aware micro-loop avoidance. When enabled, the micro-loop configuration parameters are inherited from the base SPF.
The no form of this command disables the micro-loop avoidance for flexible algorithms.
Default
no micro-loop-avoidance
Platforms
All
micro-segment
micro-segment
Syntax
[no] micro-segment
Context
[Tree] (config>router>segment-routing>srv6 micro-segment)
Full Context
configure router segment-routing segment-routing-v6 micro-segment
Description
Commands in this context configure micro-segment SRv6.
The no form of this command removes the configuration.
Platforms
7450 ESS, 7750 SR, 7750 SR-s, 7950 XRS, VSR
micro-segment-locator
micro-segment-locator
Syntax
[no] micro-segment-locator ms-locator-name
Context
[Tree] (config>router>segment-routing>srv6 micro-segment-locator)
Full Context
configure router segment-routing segment-routing-v6 micro-segment-locator
Description
This command configures the name of an SRv6 micro-segment locator for use by the routing protocols and services. This also creates the context to configure the associated parameters.
A limit of 16 locators (regular and micro) per system is enforced.
The no form of this command removes the micro-segment locator.
Parameters
- ms-locator-name
-
Specifies a micro-segment locator name, up to 64 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-s, 7950 XRS, VSR
micro-segment-locator
Syntax
[no] micro-segment-locator ms-locator-name
Context
[Tree] (config>router>segment-routing>srv6>inst micro-segment-locator)
Full Context
configure router segment-routing segment-routing-v6 base-routing-instance micro-segment-locator
Description
This command assigns a micro-segment locator to BGP for use with base router routes.
This command refers to a micro-segment locator name defined under the following context.
configure router segment-routing segment-routing-v6The no form of this command removes the micro-segment locator.
Parameters
- ms-locator-name
-
Specifies a micro-segment locator name, up to 64 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-s, 7950 XRS, VSR
micro-segment-locator
Syntax
[no] micro-segment-locator ms-locator-name
Context
[Tree] (config>service>vpls>srv6 micro-segment-locator)
[Tree] (config>service>vprn>srv6 micro-segment-locator)
[Tree] (config>service>epipe>srv6 micro-segment-locator)
Full Context
configure service vpls segment-routing-v6 micro-segment-locator
configure service vprn segment-routing-v6 micro-segment-locator
configure service epipe segment-routing-v6 micro-segment-locator
Description
This command assigns a micro-segment locator to the SRv6 instance in the service. The same micro-segment locator can be referenced in multiple BGP instances used by IPVPN or EVPN.
This command refers to a micro-segment locator name defined under the following context.
configure router segment-routing segment-routing-v6The no form of this command removes the micro-segment locator name.
Parameters
- ms-locator-name
-
Specifies a micro-segment locator name, up to 64 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-s, 7950 XRS, VSR
micro-segment-locator
Syntax
[no] micro-segment-locator ms-locator-name
Context
[Tree] (config>router>isis>srv6 micro-segment-locator)
Full Context
configure router isis segment-routing-v6 micro-segment-locator
Description
This command assigns a micro-segment locator to each algorithm in an IS-IS instance. The same micro-segment locator of a specific algorithm number can be shared with other IGP instances and BGP instances in IP-VPN or EVPN.
This command refers to a micro-segment locator name defined under the following context.
configure router segment-routing segment-routing-v6The no form of this command removes the micro-segment locator.
Default
no micro-segment-locator
Parameters
- ms-locator-name
-
Specifies a micro-segment locator name, up to 64 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-s, 7950 XRS, VSR
mid-pool
mid-pool
Syntax
[no] mid-pool mid-pool-id
Context
[Tree] (config>qos>hs-pool-policy>mid-tier mid-pool)
Full Context
configure qos hs-pool-policy mid-tier mid-pool
Description
Commands in this context configure mid-pool tier parameters for an HS pool policy. Parameters allow for allocating the percentage of the root pool size, defining a mid-tier pool’s root-pool parent, specifying the port bandwidth oversubscription factor, or specifying a slope policy for the specific mid-tier pool.
The no form of the command reverts the parent root pool association to root-pool 1, reverts to the default allocation-percentage value, the default port-bw-oversub-factor, and default slope-policy to the specified mid-pool.
Parameters
- mid-pool-id
-
Specifies the mid pool ID. This is a required parameter when this command is executed and specifies which mid-pool context is being entered.
Platforms
7750 SR-7/12/12e
mid-tier
mid-tier
Syntax
mid-tier
Context
[Tree] (config>qos>hs-pool-policy mid-tier)
Full Context
configure qos hs-pool-policy mid-tier
Description
Commands in this context configure HS pool policy parameters. Within the mid-tier context, mid-pools can be associated with a root pool, sized as a percentage of the root pool, have an HS slope policy applied, or be configured with a port bandwidth oversubscription factor parameter used to influence the port-class pool sizes associated with the mid-tier pool.
Platforms
7750 SR-7/12/12e
migrant
migrant
Syntax
[no] migrant
Context
[Tree] (config>subscr-mgmt>wlan-gw>tunnel-query>ue-state migrant)
Full Context
configure subscriber-mgmt wlan-gw tunnel-query ue-state migrant
Description
This command enables matching on tunnels with migrant UEs.
The no form of this command disables matching on migrant UEs, unless UE state matching is disabled altogether.
Default
no migrant
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
millisecond-event-timestamp
millisecond-event-timestamp
Syntax
[no] millisecond-event-timestamp
Context
[Tree] (config>aaa>isa-radius-plcy>acct-include-attributes millisecond-event-timestamp)
Full Context
configure aaa isa-radius-policy acct-include-attributes millisecond-event-timestamp
Description
This command enables the router to include the Alc-Millisecond-Event-Timestamp attribute in the accounting message. This attribute specifies the time the accounting event was logged, in milliseconds since Jan 1, 1970 00:00:00 UTC.
The no form of this command disables the router from including the Alc-Millisecond-Event-Timestamp attribute in the accounting message.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
min-advertisement
min-advertisement
Syntax
min-advertisement seconds
no min-advertisement
Context
[Tree] (config>service>vprn>sub-if>ipv6>rtr-adv min-advertisement)
[Tree] (config>service>vprn>sub-if>grp-if>ipv6 min-advertisement)
[Tree] (config>service>vprn>sub-if>grp-if>ipv6>rtr-adv min-advertisement)
[Tree] (config>service>ies>sub-if>ipv6>rtr-adv min-advertisement)
[Tree] (config>subscr-mgmt>rtr-adv-plcy min-advertisement)
[Tree] (config>service>vprn>router-advert>if min-advertisement)
[Tree] (config>service>ies>sub-if>grp-if>ipv6>rtr-adv min-advertisement)
[Tree] (config>service>ies>sub-if>grp-if>ipv6 min-advertisement)
Full Context
configure service vprn subscriber-interface ipv6 router-advertisements min-advertisement
configure service vprn subscriber-interface group-interface ipv6 min-advertisement
configure service vprn subscriber-interface group-interface ipv6 router-advertisements min-advertisement
configure service ies subscriber-interface ipv6 router-advertisements min-advertisement
configure subscriber-mgmt router-advertisement-policy min-advertisement
configure service vprn router-advert interface min-advertisement
configure service ies subscriber-interface group-interface ipv6 router-advertisements min-advertisement
configure service ies subscriber-interface group-interface ipv6 min-advertisement
Description
This command specifies the minimum time allowed between sending unsolicited router advertisements.
The no form of this command reverts to the default.
Default
min-advertisement 900
Parameters
- seconds
-
Specifies the minimum advertisement interval, in seconds.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
min-advertisement-interval
min-advertisement-interval
Syntax
[no] min-advertisement-interval seconds
Context
[Tree] (config>router>router-advert>if min-advertisement-interval)
[Tree] (config>service>vprn>router-advert>if min-advertisement-interval)
Full Context
configure router router-advertisement interface min-advertisement-interval
configure service vprn router-advertisement interface min-advertisement-interval
Description
This command configures the minimum interval between sending ICMPv6 neighbor discovery router advertisement messages.
Default
min-advertisement-interval 200
Parameters
- seconds
-
Specifies the minimum interval in seconds between sending ICMPv6 neighbor discovery router advertisement messages.
Platforms
All
min-auth-interval
min-auth-interval
Syntax
min-auth-interval min-auth-interval
no min-auth-interval
Context
[Tree] (config>service>ies>sub-if>grp-if min-auth-interval)
[Tree] (config>service>vprn>sub-if>grp-if>arp-host min-auth-interval)
[Tree] (config>service>vpls>sap>arp-host min-auth-interval)
[Tree] (config>subscr-mgmt>msap-policy>vpls-only>arp-host min-auth-interval)
Full Context
configure service ies subscriber-interface group-interface min-auth-interval
configure service vprn subscriber-interface group-interface arp-host min-auth-interval
configure service vpls sap arp-host min-auth-interval
configure subscriber-mgmt msap-policy vpls-only-sap-parameters arp-host min-auth-interval
Description
This command configures the minimum authentication interval.
The no form of this command reverts to the default.
Default
min-auth-interval 15
Parameters
- min-auth-interval
-
Specifies the minimum authentication interval, in minutes.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
min-auth-interval
Syntax
min-auth-interval [days days] [hrs hours] [min minutes] [sec seconds]
no min-auth-interval
Context
[Tree] (config>service>ies>sub-if>grp-if>ipv6>rtr-sol min-auth-interval)
Full Context
configure service ies subscriber-interface group-interface ipv6 router-solicit min-auth-interval
Description
This command specify the minimum interval between two consecutive authentication attempts from the same host.
The no form of this command reverts to the default.
Parameters
- days
-
Specifies the number of days that a user must wait for the next authentication attempt.
- hours
-
Specifies the number of hours that a user must wait for the next authentication attempt.
- minutes
-
Specifies the number of minutes that a user must wait for the next authentication attempt.
- seconds
-
Specifies the number of seconds that a user must wait for the next authentication attempt.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
min-auth-interval
Syntax
min-auth-interval [days days] [hrs hours] [min minutes] [sec seconds]
min-auth-interval infinite
no min-auth-interval
Context
[Tree] (config>service>ies>sub-if>grp-if>ipoe-session min-auth-interval)
[Tree] (config>service>vprn>sub-if>grp-if>ipoe-session min-auth-interval)
Full Context
configure service ies subscriber-interface group-interface ipoe-session min-auth-interval
configure service vprn subscriber-interface group-interface ipoe-session min-auth-interval
Description
Re-authentication for IPoE sessions enable dynamic policy changes.
This command configures the maximum frequency of re-authentications by specifying a minimum interval between two non-forced authentications for the same IPoE session.
A forced authentication is by default triggered by a circuit-id, interface-id or remote-id change (see the force-auth [config>service>ies>sub-if>grp-if>ipoe-session force-auth, config>service>vprn>sub-if>grp-if>ipoe-session force-auth] command).
Re-authentications are, by default, disabled and can be enabled by configuring a min-auth-interval.
Setting the min-auth-interval to zero seconds always re-authenticates on each trigger packet.
The no form of this command reverts to the default behavior.
Default
min-auth-interval infinite
Parameters
- days
-
Specifies the min number of days between two non-forced authentications for IPoE sessions.
- hours
-
Specifies the min number of hours between two non-forced authentications for IPoE sessions.
- minutes
-
Specifies the min number of minutes between two non-forced authentications for IPoE sessions.
- seconds
-
Specifies the min number of seconds between two non-forced authentications for IPoE sessions.
- infinite
-
Specifies that non-forced re-authentications for IPoE sessions is not performed.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
min-bandwidth
min-bandwidth
Syntax
min-bandwidth bandwidth-in-mbps
no min-bandwidth
Context
[Tree] (config>router>mpls>lsp-template>auto-bandwidth min-bandwidth)
[Tree] (config>router>mpls>lsp>auto-bandwidth min-bandwidth)
Full Context
configure router mpls lsp-template auto-bandwidth min-bandwidth
configure router mpls lsp auto-bandwidth min-bandwidth
Description
This command configures the minimum bandwidth that auto-bandwidth allocation is allowed to request for an LSP.
The LSP minimum applies whether the bandwidth adjustment is triggered by normal adjust-timer expiry or manual request.
The no form of this command reverts to the default value.
Default
min-bandwidth 0
Parameters
- bandwidth-in-mbps
-
Specifies the minimum bandwidth in Mb/s.
Platforms
All
min-delay
min-delay
Syntax
min-delay [delay]
no min-delay
Context
[Tree] (config>log>event-handling>handler>action-list>entry min-delay)
Full Context
configure log event-handling handler action-list entry min-delay
Description
This command specifies the minimum delay in seconds between subsequent executions of the action specified in this entry. This is useful, for example, to ensure that a script does not get triggered to execute too often.
Default
no min-delay
Parameters
- delay
-
Specifies the unit in seconds.
Platforms
All
min-first-fragment-size-rx
min-first-fragment-size-rx
Syntax
min-first-fragment-size-rx mtu-bytes
no min-first-fragment-size-rx
Context
[Tree] (config>service>vprn>nat>inside>dslite>address min-first-fragment-size-rx)
[Tree] (config>router>nat>inside>dslite>address min-first-fragment-size-rx)
Full Context
configure service vprn nat inside dual-stack-lite address min-first-fragment-size-rx
configure router nat inside dual-stack-lite address min-first-fragment-size-rx
Description
This command configures the minimum MTU size for the first fragment in the upstream direction. This command can be used to enable processing of first IPv6 fragments smaller than 1280 bytes. RFC 8200 recommends the minimum MTU in IPv6 be 1280 bytes which allows fragmentation only for packets that are larger than 1280 bytes. If a first fragment is smaller than 1280 bytes, DS-lite implementation in the SR OS, by default, drops the first fragment.
The no form of the command reverts to the default value.
Default
min-first-fragment-size-rx 1280
Parameters
- mtu-bytes
-
Specifies the minimum MTU size for the first fragment in the upstream direction
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
min-frame-length
min-frame-length
Syntax
min-frame-length byte-length
Context
[Tree] (config>port>ethernet min-frame-length)
Full Context
configure port ethernet min-frame-length
Description
This command configures the minimum transmitted frame length.
Parameters
- byte-length
-
Specifies the number of bytes for the minimum frame length.
Platforms
All
min-lease-time
min-lease-time
Syntax
min-lease-time [days days] [hrs hours] [min minutes] [sec seconds]
no min-lease-time
Context
[Tree] (config>router>dhcp>server>pool min-lease-time)
[Tree] (config>service>vprn>dhcp>server>pool min-lease-time)
Full Context
configure router dhcp local-dhcp-server pool min-lease-time
configure service vprn dhcp local-dhcp-server pool min-lease-time
Description
This command configures the minimum lease time.
The no form of this command reverts to the default.
Default
min-lease-time min 10
Parameters
- min-lease-time
-
Specifies the minimum lease time.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
min-num-ue
min-num-ue
Syntax
min-num-ue minimum
no min-num-ue
Context
[Tree] (config>subscr-mgmt>wlan-gw>tunnel-query min-num-ue)
Full Context
configure subscriber-mgmt wlan-gw tunnel-query min-num-ue
Description
This command enables matching only on tunnels that have at least the specified number of UEs connected.
The no form of this command disables matching on a minimum number of UEs.
Default
no min-num-ue
Parameters
- minimum
-
Specifies the minimum number of UEs.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
min-route-advertisement
min-route-advertisement
Syntax
min-route-advertisement seconds
no min-route-advertisement
Context
[Tree] (config>subscr-mgmt>bgp-prng-plcy min-route-advertisement)
Full Context
configure subscriber-mgmt bgp-peering-policy min-route-advertisement
Description
This command configures the minimum interval, in seconds, at which a prefix can be advertised to a peer.
The no form of this command reverts to default values.
Default
min-route-advertisement 30
Parameters
- seconds
-
Specifies the minimum route advertising interval, in seconds, expressed as a decimal integer.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
min-route-advertisement
Syntax
min-route-advertisement seconds
no min-route-advertisement
Context
[Tree] (config>service>vprn>bgp>group min-route-advertisement)
[Tree] (config>service>vprn>bgp min-route-advertisement)
[Tree] (config>service>vprn>bgp>group>neighbor min-route-advertisement)
Full Context
configure service vprn bgp group min-route-advertisement
configure service vprn bgp min-route-advertisement
configure service vprn bgp group neighbor min-route-advertisement
Description
This command configures the minimum interval, in seconds, at which a prefix can be advertised to a peer.
This configuration parameter can be set at three levels: global level (applies to all peers), group level (applies to all peers in peer-group) or neighbor level (only applies to specified peer). The most specific value is used.
The no form of this command reverts to default values.
Default
min-route-advertisement 30
Parameters
- seconds
-
Specifies the minimum route advertising interval, in seconds, expressed as a decimal integer.
Platforms
All
min-route-advertisement
Syntax
min-route-advertisement seconds
no min-route-advertisement
Context
[Tree] (config>router>bgp min-route-advertisement)
[Tree] (config>router>bgp>group min-route-advertisement)
[Tree] (config>router>bgp>group>neighbor min-route-advertisement)
Full Context
configure router bgp min-route-advertisement
configure router bgp group min-route-advertisement
configure router bgp group neighbor min-route-advertisement
Description
This command configures the minimum interval, in seconds, between successive updates of a prefix towards a peer.
This configuration parameter can be set at three levels: global level (applies to all peers), group level (applies to all peers in peer-group), or neighbor level (only applies to specified peer). The most specific value is used.
The no form of this command used at the global level reverts to default.
The no form of this command used at the group level reverts to the value defined at the global level.
The no form of this command used at the neighbor level reverts to the value defined at the group level.
The rapid-update command can be used to override the peer-level min-route-advertisement time and applies the minimum setting (0 seconds) to routes belonging to address families specified by the rapid-update command; routes of other address families continue to be advertised according to the session-level MRAI setting.
The rapid-update and rapid-withdrawal commands may result in the routes being sent before the peer-level MRAI timer expires.
Default
min-route-advertisement 30
Parameters
- seconds
-
Specifies the minimum route advertising interval, in seconds, expressed as a decimal integer.
Platforms
All
min-thresh-separation
min-thresh-separation
Syntax
min-thresh-separation size [bytes | kilobytes]
no min-thresh-separation
Context
[Tree] (config>subscr-mgmt>sub-prof>ingress>policer-control-policy>priority-mbs-thresholds min-thresh-separation)
[Tree] (config>subscr-mgmt>sub-prof>egress>policer-control-policy>priority-mbs-thresholds min-thresh-separation)
Full Context
configure subscriber-mgmt sub-profile ingress policer-control-policy priority-mbs-thresholds min-thresh-separation
configure subscriber-mgmt sub-profile egress policer-control-policy priority-mbs-thresholds min-thresh-separation
Description
The min-thresh-separation command defines the minimum required separation between each in-use discard threshold maintained for each parent policer context associated with the policer-control-policy. The min-thresh-separation value may be overridden on each SAP or sub-profile to which the policy is applied.
The system uses the default or specified min-thresh-separation value in order to determine the minimum separation required between each of the of the parent policer discard thresholds. The system enforces the minimum separation based on the following behavior in two ways. The first is determining the size of the shared-portion for each priority level (when the mbs-contribution command’s optional fixed keyword is not specified):
-
When a parent policer instance’s priority level has less than two child policers associated, the shared-portion for the level is zero.
-
When a parent policer instance’s priority level has two or more child policers associated, the shared-portion for the level is equal to the current value of min-thresh-separation.
The second function the system uses the min-thresh-separation value for is determining the value per priority level for the fair-portion:
-
When a parent policer instance’s priority level has no child policers associated, the fair-portion for the level is zero.
-
When a parent policer instance’s priority level has one child policer associated, the fair-portion is equal to the maximum of the min-thresh-separation value and the priority level’s mbs-contribution value.
-
When a parent policer instance's priority level has two or more child policers associated, the fair-portion is equal to the maximum of the following:
-
min-thresh-separation value
-
The priority level’s mbs-contribution value less min-thresh-separation value
-
When the mbs-contribution command’s optional fixed keyword is defined for a priority level within the policy, the system will treat the defined mbs-contribution value as an explicit definition of the priority level’s MBS. While the system will continue to track child policer associations with the parent policer priority levels, the association counters will have no effect. Instead the following rules is used to determine a fixed priority level’s shared-portion and fair-portion:
-
If a fixed priority level’s mbs-contribution value is set to zero, both the shared-portion and fair-portion is set to zero
-
If the mbs-contribution value is not set to zero:
-
The shared-portion is set to the current min-thresh-separation value
-
The fair-portion is set to the maximum of the following:
-
min-thresh-separation value
mbs-contribution value less min-thresh-separation value
Each time the min-thresh-separation value is modified, the thresholds for all instances of the parent policer created through association with this policer-control-policy are reevaluated.
Determining the Correct Value for the Minimum Threshold Separation Value
The minimum value for min-thresh-separation should be set equal to the maximum size packet that is handled by the parent policer. This ensures that when a lower priority packet is incrementing the bucket, the size of the increment will not cause the bucket's depth to equal or exceed a higher priority threshold. It also ensures that an unfair packet within a priority level cannot cause the PIR bucket to increment to the discard-all threshold within the priority.
When evaluating maximum packet size, each child policer’s per-packet-offset setting should be taken into consideration. If the maximum size packet is 1518 bytes and a per-packet-offset parameter is configured to add 20 bytes per packet, min-thresh-separation should be set to 1538 due to the fact that the parent policer will increment its PIR bucket using the extra 20 bytes.
In most circumstances, a value larger than the maximum packet size is not necessary. Management of priority level aggregate burst tolerance is intended to be implemented using the priority level mbs-contribution command. Setting a value larger than the maximum packet size will not adversely affect the policer performance, but it may increase the aggregate burst tolerance for each priority level.
A priority level’s shared-portion of the parent policer’s PIR bucket depth is only necessary to provide some separation between a lower priority’s discard-all threshold and this priority’s discard-unfair threshold. It is expected that the burst tolerance for the unfair packets is relatively minimal since the child policers feeding the parent policer priority level all have some amount of fair burst before entering into an FIR exceed or unfair state. The fair burst amount for a priority level is defined using the mbs-contribution command.
The no form of this command returns the policy’s min-thresh-separation value to the default value.
Parameters
- size
-
The size parameter is required when executing the min-thresh-separation command. It is expressed as an integer and specifies the shared portion in bytes or kilobytes that is selected by the trailing bytes or kilobytes keywords. If both bytes and kilobytes are missing, kilobytes is the assumed value. Setting this value has no effect on parent policer instances where the min-thresh-separation value has been overridden.
- [bytes | kilobytes]
-
The bytes keyword is optional and is mutually exclusive with the kilobytes keyword. When specified, size is interpreted as specifying the size of min-thresh-separation in bytes.
The kilobytes keyword is optional and is mutually exclusive with the bytes keyword. When specified, size is interpreted as specifying the size of min-thresh-separation in kilobytes.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
min-thresh-separation
Syntax
min-thresh-separation size [bytes | kilobytes]
no min-thresh-separation
Context
[Tree] (config>card>fp>ingress>access>queue-group>policer-control-override>priority-mbs-thresholds min-thresh-separation)
[Tree] (config>card>fp>ingress>network>queue-group>policer-control-override>priority-mbs-thresholds min-thresh-separation)
Full Context
configure card fp ingress access queue-group policer-control-override priority-mbs-thresholds min-thresh-separation
configure card fp ingress network queue-group policer-control-override priority-mbs-thresholds min-thresh-separation
Description
This command defines the minimum required separation between each in-use discard threshold maintained for each parent policer context associated with the policer-control-policy. The min-thresh-separation value may be overridden on each SAP or sub-profile to which the policy is applied.
The system uses the default or specified min-thresh-separation value in order to determine the minimum separation required between each of the of the parent policer discard thresholds. The system enforces the minimum separation based on the following behavior in two ways. The first is determining the size of the shared-portion for each priority level (when the mbs-contribution command’s optional fixed keyword is not specified):
-
When a parent policer instance’s priority level has less than two child policers associated, the shared-portion for the level will be zero.
-
When a parent policer instance’s priority level has two or more child policers associated, the shared-portion for the level will be equal to the current value of min-thresh-separation.
The second function the system uses the min-thresh-separation value for is determining the value per priority level for the fair-portion:
-
When a parent policer instance’s priority level has no child policers associated, the fair-portion for the level will be zero.
-
When a parent policer instance’s priority level has one child policer associated, the fair-portion will be equal to the maximum of the min-thresh-separation value and the priority level’s mbs-contribution value.
-
When a parent policer instance's priority level has two or more child policers associated, the fair-portion will be equal to the maximum of the following:
-
min-thresh-separation value
-
The priority level’s mbs-contribution value less min-thresh-separation value
-
When the mbs-contribution command’s optional fixed keyword is defined for a priority level within the policy, the system will treat the defined mbs-contribution value as an explicit definition of the priority level’s MBS. While the system will continue to track child policer associations with the parent policer priority levels, the association counters will have no effect. Instead the following rules will be used to determine a fixed priority level’s shared-portion and fair-portion:
-
If a fixed priority level’s mbs-contribution value is set to zero, both the shared-portion and fair-portion will be set to zero
-
If the mbs-contribution value is not set to zero:
-
The shared-portion will be set to the current min-thresh-separation value
-
The fair-portion will be set to the maximum of the following:
-
min-thresh-separation value
-
mbs-contribution value less min-thresh-separation value
-
-
Each time the min-thresh-separation value is modified, the thresholds for all instances of the parent policer created through association with this policer-control-policy are reevaluated except for parent policer instances that currently have a min-thresh-separation override.
Determining the Correct Value for the Minimum Threshold Separation Value
The minimum value for min-thresh-separation should be set equal to the maximum size packet that will be handled by the parent policer. This ensures that when a lower priority packet is incrementing the bucket, the size of the increment will not cause the bucket's depth to equal or exceed a higher priority threshold. It also ensures that an unfair packet within a priority level cannot cause the PIR bucket to increment to the discard-all threshold within the priority.
When evaluating maximum packet size, each child policer’s per-packet-offset setting should be taken into consideration. If the maximum size packet is 1518 bytes and a per-packet-offset parameter is configured to add 20 bytes per packet, min-thresh-separation should be set to 1538 due to the fact that the parent policer will increment its PIR bucket using the extra 20 bytes.
In most circumstances, a value larger than the maximum packet size is not necessary. Management of priority level aggregate burst tolerance is intended to be implemented using the priority level mbs-contribution command. Setting a value larger than the maximum packet size will not adversely affect the policer performance, but it may increase the aggregate burst tolerance for each priority level.
One thing to note is that a priority level’s shared-portion of the parent policer’s PIR bucket depth is only necessary to provide some separation between a lower priority’s discard-all threshold and this priority’s discard-unfair threshold. It is expected that the burst tolerance for the unfair packets is relatively minimal since the child policers feeding the parent policer priority level all have some amount of fair burst before entering into an FIR exceed or unfair state. The fair burst amount for a priority level is defined using the mbs-contribution command.
The no form of this command returns the policy’s min-thresh-separation value to the default value. This has no effect on instances of the parent policer where min-thresh-separation is overridden unless the override is removed.
Default
no min-thresh-separation
Parameters
- size
-
Specifies that the size parameter is required when executing the min-thresh-separation command. It is expressed as an integer and specifies the shared portion in bytes or kilobytes that is selected by the trailing bytes or kilobytes keywords. If both bytes and kilobytes are missing, kilobytes is the assumed value. Setting this value has no effect on parent policer instances where the min-thresh-separation value has been overridden. Clearing an override on parent policer instance causes this value to be enforced.
- bytes | kilobytes
-
Specifies that the bytes keyword is optional and is mutually exclusive with the kilobytes keyword. When specified, size is interpreted as specifying the size of min-thresh-separation in bytes.
The kilobytes keyword is optional and is mutually exclusive with the bytes keyword. When specified, size is interpreted as specifying the size of min-thresh-separation in kilobytes.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
min-thresh-separation
Syntax
min-thresh-separation size [bytes | kilobytes]
Context
[Tree] (config>service>ipipe>sap>egress>policy-ctrl-over>mbs-thrshlds min-thresh-separation)
[Tree] (config>service>ipipe>sap>ingress>policy-ctrl-over>mbs-thrshlds min-thresh-separation)
[Tree] (config>service>fpipe>sap>egress>policy-ctrl-over>mbs-thrshlds min-thresh-separation)
[Tree] (config>service>epipe>sap>egress>policy-ctrl-over>mbs-thrshlds min-thresh-separation)
[Tree] (config>service>cpipe>sap>ingress>policy-ctrl-over>mbs-thrshlds min-thresh-separation)
[Tree] (config>service>fpipe>sap>ingress>policy-ctrl-over>mbs-thrshlds min-thresh-separation)
[Tree] (config>service>apipe>sap>ingress>policy-ctrl-over>mbs-thrshlds min-thresh-separation)
[Tree] (config>service>epipe>sap>ingress>policy-ctrl-over>mbs-thrshlds min-thresh-separation)
[Tree] (config>service>apipe>sap>egress>policy-ctrl-over>mbs-thrshlds min-thresh-separation)
[Tree] (config>service>cpipe>sap>egress>policy-ctrl-over>mbs-thrshlds min-thresh-separation)
Full Context
configure service ipipe sap egress policer-control-override priority-mbs-thresholds min-thresh-separation
configure service ipipe sap ingress policer-control-override priority-mbs-thresholds min-thresh-separation
configure service fpipe sap egress policer-control-override priority-mbs-thresholds min-thresh-separation
configure service epipe sap egress policer-control-override priority-mbs-thresholds min-thresh-separation
configure service cpipe sap ingress policer-control-override priority-mbs-thresholds min-thresh-separation
configure service fpipe sap ingress policer-control-override priority-mbs-thresholds min-thresh-separation
configure service apipe sap ingress policer-control-override priority-mbs-thresholds min-thresh-separation
configure service epipe sap ingress policer-control-override priority-mbs-thresholds min-thresh-separation
configure service apipe sap egress policer-control-override priority-mbs-thresholds min-thresh-separation
configure service cpipe sap egress policer-control-override priority-mbs-thresholds min-thresh-separation
Description
This command, within the SAP ingress and egress contexts, is used to override the root arbiter’s parent policer min-thresh-separation parameter that is defined within the policer-control-policy applied to the SAP.
When the override is defined, modifications to the policer-control-policy min-thresh-separation parameter have no effect on the SAP’s parent policer until the override is removed using the no min-thresh-separation command within the SAP.
The no form of this command removes the override and allows the min-thresh-separation setting from the policer-control-policy to control the root arbiter’s parent policer’s minimum discard threshold separation size.
Default
no min-thresh-separation
Parameters
- size
-
The minimum discard threshold separation override value.
- bytes
-
Signifies that size is expressed in bytes. The bytes and kilobytes keywords are mutually exclusive and optional. The default is kilobytes.
- kilobytes
-
Signifies that size is expressed in kilobytes. The bytes and kilobytes keywords are mutually exclusive and optional. The default is kilobytes.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
- configure service ipipe sap egress policer-control-override priority-mbs-thresholds min-thresh-separation
- configure service epipe sap egress policer-control-override priority-mbs-thresholds min-thresh-separation
- configure service ipipe sap ingress policer-control-override priority-mbs-thresholds min-thresh-separation
- configure service epipe sap ingress policer-control-override priority-mbs-thresholds min-thresh-separation
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS
- configure service fpipe sap egress policer-control-override priority-mbs-thresholds min-thresh-separation
- configure service fpipe sap ingress policer-control-override priority-mbs-thresholds min-thresh-separation
- configure service cpipe sap ingress policer-control-override priority-mbs-thresholds min-thresh-separation
- configure service cpipe sap egress policer-control-override priority-mbs-thresholds min-thresh-separation
7450 ESS, 7750 SR-7/12/12e, 7750 SR-e, 7950 XRS
- configure service apipe sap ingress policer-control-override priority-mbs-thresholds min-thresh-separation
- configure service apipe sap egress policer-control-override priority-mbs-thresholds min-thresh-separation
min-thresh-separation
Syntax
min-thresh-separation size [{bytes | kilobytes}]
Context
[Tree] (config>service>vpls>sap>egress>policer-ctrl-over>mbs-thrshlds min-thresh-separation)
[Tree] (config>service>vpls>sap>ingress>policer-ctrl-over>mbs-thrshlds min-thresh-separation)
Full Context
configure service vpls sap egress policer-control-override priority-mbs-thresholds min-thresh-separation
configure service vpls sap ingress policer-control-override priority-mbs-thresholds min-thresh-separation
Description
This command within the SAP ingress and egress contexts is used to override the root arbiter’s parent policer min-thresh-separation parameter that is defined within the policer-control-policy applied to the SAP.
When the override is defined, modifications to the policer-control-policy min-thresh-separation parameter have no effect on the SAP’s parent policer until the override is removed using the no min-thresh-separation command within the SAP.
The no form of this command removes the override and allows the min-thresh-separation setting from the policer-control-policy to control the root arbiter’s parent policer’s minimum discard threshold separation size.
Default
no min-thresh-separation
Parameters
- size
-
This parameter is required when specifying min-thresh-separation override and is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional byte and kilobyte keywords are mutually exclusive and are used to explicitly define whether size represents bytes or kilobytes.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
min-thresh-separation
Syntax
min-thresh-separation size [{bytes | kilobytes}]
Context
[Tree] (config>service>ies>if>sap>egress>policer-ctrl-over>mbs-thrshlds min-thresh-separation)
[Tree] (config>service>ies>if>sap>ingress>policer-ctrl-over>mbs-thrshlds min-thresh-separation)
Full Context
configure service ies interface sap egress policer-control-override priority-mbs-thresholds min-thresh-separation
configure service ies interface sap ingress policer-control-override priority-mbs-thresholds min-thresh-separation
Description
This command within the SAP ingress and egress contexts is used to override the root arbiter’s parent policer min-thresh-separation parameter that is defined within the policer-control-policy applied to the SAP.
When the override is defined, modifications to the policer-control-policy min-thresh-separation parameter have no effect on the SAP’s parent policer until the override is removed using the no min-thresh-separation command within the SAP.
The no form of this command removes the override and allows the min-thresh-separation setting from the policer-control-policy to control the root arbiter’s parent policer’s minimum discard threshold separation size.
Default
no min-thresh-separation
Parameters
- size
-
This parameter is required when specifying min-thresh-separation override and is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional byte and kilobyte keywords are mutually exclusive and are used to explicitly define whether size represents bytes or kilobytes.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
min-thresh-separation
Syntax
min-thresh-separation size [{bytes | kilobytes}]
Context
[Tree] (config>service>vprn>if>sap>ingress>policer-ctrl-over>mbs-thrshlds min-thresh-separation)
[Tree] (config>service>vprn>if>sap>egress>policer-ctrl-over>mbs-thrshlds min-thresh-separation)
Full Context
configure service vprn interface sap ingress policer-ctrl-over priority-mbs-thresholds min-thresh-separation
configure service vprn interface sap egress policer-ctrl-over priority-mbs-thresholds min-thresh-separation
Description
This command within the SAP ingress and egress contexts is used to override the root arbiter’s parent policer min-thresh-separation parameter that is defined within the policer-control-policy applied to the SAP.
When the override is defined, modifications to the policer-control-policy min-thresh-separation parameter have no effect on the SAP’s parent policer until the override is removed using the no min-thresh-separation command within the SAP.
The no form of this command removes the override and allows the min-thresh-separation setting from the policer-control-policy to control the root arbiter’s parent policer’s minimum discard threshold separation size.
Default
no min-thresh-separation
Parameters
- size
-
This parameter is required when specifying min-thresh-separation override and is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional byte and kilobyte keywords are mutually exclusive and are used to explicitly define whether size represents bytes or kilobytes.
min-thresh-separation
Syntax
min-thresh-separation size [bytes | kilobytes]
no min-thresh-separation
Context
[Tree] (config>qos>plcr-ctrl-plcy>root>priority-mbs-thresholds min-thresh-separation)
Full Context
configure qos policer-control-policy root priority-mbs-thresholds min-thresh-separation
Description
The min-thresh-separation command defines the minimum required separation between each in-use discard threshold maintained for each parent policer context associated with the policer-control-policy. The min-thresh-separation value may be overridden on each SAP or sub-profile to which the policy is applied.
The system uses the default or specified min-thresh-separation value in order to determine the minimum separation required between each of the of the parent policer discard thresholds. The system enforces the minimum separation based on the following behavior in two ways. The first is determining the size of the shared-portion for each priority level (when the mbs-contribution command’s optional fixed keyword is not specified):
-
When a parent policer instance’s priority level has less than two child policers associated, the shared-portion for the level will be zero.
-
When a parent policer instance’s priority level has two or more child policers associated, the shared-portion for the level will be equal to the current value of min-thresh-separation.
The second function the system uses the min-thresh-separation value for is determining the value per priority level for the fair-portion:
-
When a parent policer instance’s priority level has no child policers associated, the fair-portion for the level will be zero.
-
When a parent policer instance’s priority level has one child policer associated, the fair-portion will be equal to the maximum of the min-thresh-separation value and the priority level’s mbs-contribution value.
-
When a parent policer instance's priority level has two or more child policers associated, the fair-portion will be equal to the maximum of the following:
-
min-thresh-separation value
-
mbs-contribution value less min-thresh-separation value
-
When the mbs-contribution command’s optional fixed keyword is defined for a priority level within the policy, the system will treat the defined mbs-contribution value as an explicit definition of the priority level’s MBS. While the system will continue to track child policer associations with the parent policer priority levels, the association counters will have no effect. Instead, the following rules will be used to determine a fixed priority level’s shared-portion and fair-portion:
-
If a fixed priority level’s mbs-contribution value is set to zero, both the shared-portion and fair-portion will be set to zero
-
If the mbs-contribution value is not set to zero:
-
The shared-portion will be set to the current min-thresh-separation value
-
The fair-portion will be set to the maximum of the following:
min-thresh-separation value
mbs-contribution value less min-thresh-separation value
-
Each time the min-thresh-separation value is modified, the thresholds for all instances of the parent policer created through association with this policer-control-policy are reevaluated.
Determining the Correct Value for the Minimum Threshold Separation Value
The minimum value for min-thresh-separation should be set equal to the maximum size packet that will be handled by the parent policer. This ensures that when a lower priority packet is incrementing the bucket, the size of the increment will not cause the bucket's depth to equal or exceed a higher priority threshold. It also ensures that an unfair packet within a priority level cannot cause the PIR bucket to increment to the discard-all threshold within the priority.
When evaluating maximum packet size, each child policer’s per-packet-offset setting should be taken into consideration. If the maximum size packet is 1518 bytes and a per-packet-offset parameter is configured to add 20 bytes per packet, min-thresh-separation should be set to 1538 due to the fact that the parent policer will increment its PIR bucket using the extra 20 bytes.
In most circumstances, a value larger than the maximum packet size is not necessary. Management of priority level aggregate burst tolerance is intended to be implemented using the priority level mbs-contribution command. Setting a value larger than the maximum packet size will not adversely affect the policer performance, but it may increase the aggregate burst tolerance for each priority level.
A priority level’s shared-portion of the parent policer’s PIR bucket depth is only necessary to provide some separation between a lower priority’s discard-all threshold and this priority’s discard-unfair threshold. It is expected that the burst tolerance for the unfair packets is relatively minimal since the child policers feeding the parent policer priority level all have some amount of fair burst before entering into an FIR exceed or unfair state. The fair burst amount for a priority level is defined using the mbs-contribution command.
The no form of this command returns the policy’s min-thresh-separation value to the default value.
Parameters
- size
-
The size parameter is required when executing the min-thresh-separation command. It is expressed as an integer. Setting this value has no effect on parent policer instances where the min-thresh-separation value has been overridden.
- bytes | kilobytes
-
This parameter indicates whether the size is expressed in bytes or kilobytes.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
min-vp-vpi
min-vp-vpi
Syntax
min-vp-vpi value
Context
[Tree] (config>port>ml-bundle>ima>atm min-vp-vpi)
[Tree] (config>port>tdm>e3>atm min-vp-vpi)
[Tree] (config>port>tdm>ds1>channel-group>atm min-vp-vpi)
[Tree] (config>port>tdm>ds3>atm min-vp-vpi)
[Tree] (config>port>tdm>e1>channel-group>atm min-vp-vpi)
Full Context
configure port multilink-bundle ima atm min-vp-vpi
configure port tdm e3 atm min-vp-vpi
configure port tdm ds1 channel-group atm min-vp-vpi
configure port tdm ds3 atm min-vp-vpi
configure port tdm e1 channel-group atm min-vp-vpi
Description
This command sets the minimum allowable virtual path identifier (VPI) value that can be used on the ATM interface for a VPC.
Parameters
- value
-
Specifies the minimum allowable VPI value that can be used on the ATM interface for a VPC.
Platforms
7450 ESS, 7750 SR-7/12/12e
- configure port multilink-bundle ima atm min-vp-vpi
7450 ESS, 7750 SR-7/12/12e, 7750 SR-a, 7750 SR-e
- configure port tdm e3 atm min-vp-vpi
- configure port tdm ds3 atm min-vp-vpi
- configure port tdm ds1 channel-group atm min-vp-vpi
- configure port tdm e1 channel-group atm min-vp-vpi
min-wait-to-advertise
min-wait-to-advertise
Syntax
min-wait-to-advertise seconds
no min-wait-to-advertise
Context
[Tree] (config>service>vprn>bgp>convergence min-wait-to-advertise)
Full Context
configure service vprn bgp convergence min-wait-to-advertise
Description
This command configures the minimum amount of time that BGP waits, after the first session establishment following a restart of the BGP instance, until it can start advertising IPv4-unicast and IPv6-unicast routes to its BGP peers, to allow time for re-convergence.
The time limit configured by this command should allow sufficient time for all important peers to re-establish their sessions with the restarting router.
The no form of this command implements the default time limit of 0 seconds, which disables all forms of delayed route advertisement. In other words, it causes IPv4-unicast and IPv6-unicast routes to be re-advertised as soon as possible after BGP instance restart.
Default
no min-wait-to-advertise
Parameters
- seconds
-
Specifies the minimum amount of time, in seconds, that BGP waits until IPv4-unicast and IPv6-unicast routes can be advertised to peers.
Platforms
All
min-wait-to-advertise
Syntax
min-wait-to-advertise seconds
no min-wait-to-advertise
Context
[Tree] (config>router>bgp>convergence min-wait-to-advertise)
Full Context
configure router bgp convergence min-wait-to-advertise
Description
This command configures the minimum amount of time that BGP waits, after the first session establishment following a restart of the BGP instance, until it can start advertising IPv4-unicast and IPv6-unicast routes to its BGP peers, to allow time for re-convergence.
The time limit configured by this command should allow sufficient time for all important peers to re-establish their sessions with the restarting router.
The no form of this command implements the default time limit of 0 seconds, which disables all forms of delayed route advertisement. In other words, it causes IPv4-unicast and IPv6-unicast routes to be re-advertised as soon as possible after BGP instance restart.
Default
no min-wait-to-advertise
Parameters
- seconds
-
Specifies the minimum amount of time, in seconds, that BGP waits until IPv4-unicast and IPv6-unicast routes can be advertised to peers.
Platforms
All
minimum
minimum
Syntax
minimum [percent [percent]] [number [number]]
no minimum
Context
[Tree] (config>service>vprn>dhcp6>server>pool>prefix>thresholds>minimum-free minimum)
[Tree] (config>router>dhcp6>server>pool>prefix>thresholds>minimum-free minimum)
Full Context
configure service vprn dhcp6 local-dhcp-server pool prefix thresholds minimum-free minimum
configure router dhcp6 local-dhcp-server pool prefix thresholds minimum-free minimum
Description
This command configures a percentage-based or number-based threshold which represents the minimal available percentage or number of the prefix with a configured length in the provisioned prefix. The system sends out a warning if the actual percentage or number is lower than the configured threshold.
For example:
prefix 2001:0:0:ffe0::/50 pd wan-host create
thresholds
minimum-free prefix-length 64
minimum number 3
With the above configuration, the system sends a warning when the number of available /64 in prefix 2001:0:0:ffe0::/50 is less than 3.
The no form of this command removes the command parameters from the configuration.
Parameters
- percent
-
Specifies the percentage of used prefixes with the minimum free threshold length in the pool compared to the number of provisioned prefixes.
- number
-
Specifies the number of prefixes.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
minimum-age
minimum-age
Syntax
minimum-age [days days] [hrs hours] [min minutes] [sec seconds]
no minimum-age
Context
[Tree] (config>system>security>password minimum-age)
Full Context
configure system security password minimum-age
Description
Configure the minimum required age of a password before it can be changed again.
Default
minimum-age min 10
Parameters
- days
-
Specifies the minimum required days of a password before it can be changed again.
- hours
-
Specifies the minimum required hours of a password before it can be changed again.
- minutes
-
Specifies the minimum required minutes of a password before it can be changed again.
- seconds
-
Specifies the minimum required seconds of a password before it can be changed again.
Platforms
All
minimum-change
minimum-change
Syntax
minimum-change distance
no minimum-change
Context
[Tree] (config>system>security>password minimum-change)
Full Context
configure system security password minimum-change
Description
This command configures the minimum number of characters required to be different in the new password from a previous password.
The no form of this command reverts to default value.
Default
minimum-change 5
Parameters
- distance
-
Specifies how many characters must be different in the new password from the old password.
Platforms
All
minimum-classes
minimum-classes
Syntax
minimum-classes minimum
no minimum-classes
Context
[Tree] (config>system>security>password>complexity-rules minimum-classes)
Full Context
configure system security password complexity-rules minimum-classes
Description
Force the use of at least this many different character classes
The no form of this command resets to default.
Default
no minimum-classes
Parameters
- minimum
-
Specifies the minimum number of classes to be configured.
Platforms
All
minimum-free
minimum-free
Syntax
minimum-free minimum-free [percent] [event-when-depleted]
no minimum-free
Context
[Tree] (config>service>vprn>dhcp>server>pool minimum-free)
[Tree] (config>router>dhcp>server>pool minimum-free)
Full Context
configure service vprn dhcp local-dhcp-server pool minimum-free
configure router dhcp local-dhcp-server pool minimum-free
Description
This command specifies the desired minimum number of free addresses in this pool.
The no form of this command reverts to the default.
Default
minimum-free 1
Parameters
- minimum-free
-
Specifies the minimum number of free addresses.
- percent
-
Specifies that the value indicates a percentage.
- event-when-depleted
-
This parameter enables a system-generate event when all available addresses in the pool/subnet of local DHCP server are depleted.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
minimum-free
Syntax
minimum-free minimum-free [percent] [event-when-depleted]
no minimum-free
Context
[Tree] (config>router>dhcp>server>pool>subnet minimum-free)
[Tree] (config>service>vprn>dhcp>server>pool>subnet minimum-free)
Full Context
configure router dhcp local-dhcp-server pool subnet minimum-free
configure service vprn dhcp local-dhcp-server pool subnet minimum-free
Description
This command configures the minimum number of free addresses in this subnet. If the actual number of free addresses in this subnet falls below this configured minimum, a notification is generated.
The no form of the reverts to the default.
Default
minimum-free 1
Parameters
- minimum-free
-
Specifies the minimum number of free addresses in this subnet.
- percent
-
Specifies that the value indicates a percentage.
- event-when-depleted
-
Enables a system-generate event when all available addresses in the pool or subnet of local DHCP server are depleted.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
minimum-free
Syntax
[no] minimum-free prefix-length [prefix-length]
Context
[Tree] (config>router>dhcp6>server>pool>thresholds minimum-free)
[Tree] (config>service>vprn>dhcp6>server>pool>thresholds minimum-free)
Full Context
configure router dhcp6 local-dhcp-server pool thresholds minimum-free
configure service vprn dhcp6 local-dhcp-server pool thresholds minimum-free
Description
This command creates a threshold for a given prefix length on the pool level. Up to 128 thresholds could be created. For example, with minimum-free prefix-length 64, then the usage of /64 prefix in the pool is counted.
There are two types of thresholds that could be defined at the pool level:
-
Depleted — The system sends out a warning when the prefix with the configured length is no long available in the pool.
-
Minimum free — A percentage-based threshold which represents the minimal available percentage of prefix with the configured length in the pool. The system will send out warning if the actual percentage is lower than the configured percentage.
Configuring this command also enables the system stats collection for configure prefix length, which could be displayed with the show router router-id dhcp6 local-dhcp-server dhcp6-server-name pool-threshold-stats command.
The no form of this command removes the prefix-length from the configuration.
Parameters
- prefix-length
-
Specifies the IPv6 prefix length.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
minimum-isa-generation
minimum-isa-generation
Syntax
minimum-isa-generation min-isa-generation
Context
[Tree] (config>isa>aa-grp minimum-isa-generation)
Full Context
configure isa application-assurance-group minimum-isa-generation
Description
This command configures the scale parameters for the ISA group. When min-isa-generation is configured as 1, the group and per-ISA limits are the MS-ISA scale.
If there is a mix of ISA 1s and 2s, the min-isa-generation must be left as 1.
When min-isa-gen is configured as 2, the per-isa resource limits shown in the show isa application-assurance-group 1 load-balance output will increase to show ISA2 limits.
Default
minimum-isa-generation 1
Parameters
- min-isa-generation
-
Specifies the minimum ISA Generation allowed in this group.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s
minimum-length
minimum-length
Syntax
minimum-length length
no minimum-length
Context
[Tree] (config>system>security>password>complexity-rules minimum-length)
Full Context
configure system security password complexity-rules minimum-length
Description
This command configures the minimum number of characters required for locally administered passwords, HMAC-MD5-96, HMAC-SHA-96, and des-keys configured in the system security section.
If multiple minimum-length commands are entered each command overwrites the previous entered command.
The no form of this command reverts to default value.
Default
minimum-length 6
Parameters
- value
-
Specifies the minimum number of characters required for a password.
Platforms
All
minimum-lifetimes
minimum-lifetimes
Syntax
minimum-lifetimes
Context
[Tree] (config>python>py-pol>cache minimum-lifetimes)
Full Context
configure python python-policy cache minimum-lifetimes
Description
Commands in this context configure minimum-lifetime of Python cache information.
Platforms
All
minimum-links
minimum-links
Syntax
minimum-links minimum-links
no minimum-links
Context
[Tree] (config>port>multilink-bundle minimum-links)
Full Context
configure port multilink-bundle minimum-links
Description
This command sets the minimum number of links that must be active for the bundle to be active.
If the number of active links drops below the configured minimum then the multilink bundle will transition to an operationally down state.
The no form of this command removes the minimum link limit.
Default
minimum-links 1
Parameters
- minimum-link
-
Specifies the minimum link limit, expressed as an integer.
Platforms
7450 ESS, 7750 SR-7/12/12e
minute
minute
Syntax
minute {minute-number [..minute-number] | all}
no minute
Context
[Tree] (config>system>cron>sched minute)
Full Context
configure system cron schedule minute
Description
This command specifies the minute to schedule a command. Multiple minutes of the hour can be specified. When multiple minutes are configured, each of them will cause the schedule to occur. If a minute is configured, but no hour or day is configured, the event will not execute. If a minute is configured without configuring the month, weekday, day-of-month, and minute, the event will not execute.
The no form of this command removes the specified minute from the configuration.
Default
no minute
Parameters
- minute-number
-
Specifies the minute to schedule a command.
- all
-
Specifies all minutes.
Platforms
All
minutes
minutes
Syntax
minutes {minutes | disable}
no minutes
Context
[Tree] (config>system>security>ssh>key-re-exchange>client minutes)
[Tree] (config>system>security>ssh>key-re-exchange>server minutes)
Full Context
configure system security ssh key-re-exchange client minutes
configure system security ssh key-re-exchange server minutes
Description
This command configures the maximum time, in minutes, before a key re-exchange is initiated by the server.
The no form of this command reverts to the default value.
Default
minutes 60
Parameters
- minutes
-
Specifies the time interval, in minutes, after which the SSH client will initiate the key-re-exchange.
- disable
-
Specifies that a session will never timeout. To re-enable minutes, enter the command without the disable option.
Platforms
All
mip
mip
Syntax
mip [mac mac-address] [primary-vlan-enable vlan-id] [cfm-vlan-tag qtag1[.qtag2]]
mip default-mac [primary-vlan-enable vlan-id] [cfm-vlan-tag qtag1[.qtag2]]
no mip [primary-vlan-enable vlan-id]
Context
[Tree] (config>service>vpls>mesh-sdp>eth-cfm mip)
[Tree] (config>service>vpls>spoke-sdp>eth-cfm mip)
[Tree] (config>service>epipe>spoke-sdp>eth-cfm mip)
[Tree] (config>service>epipe>sap>eth-cfm mip)
[Tree] (config>service>vpls>sap>eth-cfm mip)
Full Context
configure service vpls mesh-sdp eth-cfm mip
configure service vpls spoke-sdp eth-cfm mip
configure service epipe spoke-sdp eth-cfm mip
configure service epipe sap eth-cfm mip
configure service vpls sap eth-cfm mip
Description
This command configures Maintenance Intermediate Points (MIPs). The creation rules of the MIP are dependent on the mhf-creation configuration for the MA.
The MIP can be created with a primary VLAN using the primary-vlan-enable vlan-id parameter matching the VLAN configured under the applicable association. Optional VLANs can be added the to the locally-generated CFM frames for egress processing using the cfm-vlan-tag option.
The no form of this command removes the MIP creation request.
Default
no mip
Parameters
- qtag1
-
Specifies the outer VLAN ID.
- qtag2
-
Specifies the inner VLAN ID and can only be specified if qtag1 is configured.
- mac
-
Provides a method for manually configuring the MIP MAC address.
- mac-address
-
Specifies the MAC address of the MIP.
- default-mac
-
Specifies to change the MAC address back to the default MAC without having to delete and reconfigure the MIP.
- primary-vlan-enable
-
Provides a method for linking the MIP with the primary VLAN configured under the bridge-identifier for the MA. This is only allowed if the mhf-creation method is static. MIPs cannot be changed from or to primary VLAN functions without first being deleted. This must be configured as part of the creation step and can only be changed by deleting the MIP and re-creating it. Primary VLANs are only supported under Layer 2 Epipe and VPLS services.
- vlan-id
-
Specifies the VLAN ID. This parameter must match the VLAN ID under the bridge-identifier for the MA that is appropriate for this service.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
mip
Syntax
mip primary-vlan-enable [vlan vlan-id]
no mip
Context
[Tree] (config>service>template>vpls-sap-template>eth-cfm mip)
Full Context
configure service template vpls-sap-template eth-cfm mip
Description
This command allows Maintenance Intermediate Points (MIPs). The creation rules of the MIP are dependent on the mhf-creation configuration for the MA. This MIP option is only available for default and static mhf-creation methods.
Parameters
- primary-vlan-enable
-
Provides a method for linking the MIP with the primary VLAN configured under the bridge-identifier for the MA. This is only allowed if the mhf-creation method is static. MIPs cannot be changed from or to primary VLAN functions without first being deleted. This must be configured as part of the creation step and can only be changed by deleting the MEP and re-creating it. Primary VLANs are only supported under Ethernet SAPs.
- vlan
-
A required parameter when including primary-vlan-enable. Provides a method for associating the VLAN under the bride-identifier under the MA with the MIP.
- vlan-id
-
Must match the vlan-id under the bridge-identifier for the MA that is appropriate for this service.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
mip
Syntax
[no] mip
Context
[Tree] (config>router>mpls>mpls-tp>transit-path>reverse-path mip)
[Tree] (config>router>mpls>mpls-tp>transit-path>forward-path mip)
Full Context
configure router mpls mpls-tp transit-path reverse-path mip
configure router mpls mpls-tp transit-path forward-path mip
Description
This command creates a context for maintenance entity group intermediate point (MIP) parameters for the forward path and the reverse path of an MPLS-TP LSP at an LSR.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
mip
Syntax
[no] mip domain md-index association ma-index
Context
[Tree] (debug>eth-cfm mip)
Full Context
debug eth-cfm mip
Description
This command specifies the MIP from which to debug the CFM PDUs.
The no form of this command removes the MIP parameters.
Parameters
- md-index
-
Specifies the maintenance domain (MD) index value of the launch point.
- ma-index
-
Specifies the maintenance association (MA) index value of the launch point.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
mip-ltr-priority
mip-ltr-priority
Syntax
mip-ltr-priority priority
Context
[Tree] (cfg>eth-cfm>domain>assoc>bridge mip-ltr-priority)
Full Context
configure eth-cfm domain association bridge-identifier mip-ltr-priority
Description
This command allows the operator to set the priority of the Linktrace Response Message (ETH-LTR) from a MIP for this association.
Default
7
Parameters
- priority
-
Specifies the priority of the Linktrace Response Message (ETH-LTR) from a MIP.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
mip-ltr-priority
Syntax
mip-ltr-priority priority
Context
[Tree] (config>eth-cfm>default-domain>bridge-identifier mip-ltr-priority)
Full Context
configure eth-cfm default-domain bridge-identifier mip-ltr-priority
Description
This command allows the operator to set the priority of the Linktrace Response Message (ETH-LTR) from a MIP for this association.
Default
defer
Parameters
- priority
-
Specifies the priority of the Linktrace Response Message (ETH-LTR) from a MIP. The ‟defer” value is only supported under the default-domain context and causes mip-ltr-priority to inherit values from the global read-only-system values.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
mir
mir
Syntax
mir mir-value
no mir
Context
[Tree] (config>qos>mlppp-profile-egress>class mir)
Full Context
configure qos mlppp-profile-egress class mir
Description
This command configures the minimum information rate (MIR) scheduling parameter for each MLPPP class queue for this profile.
Parameters
- mir-value
-
Specifies the MIR scheduling parameter.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
mir
Syntax
mir mir
no mir
Context
[Tree] (config>qos>mc-fr-profile-egress>class mir)
Full Context
configure qos mc-fr-profile-egress class mir
Description
This command configures the minimum information rate scheduling parameter for each Frame Relay scheduling class queue for this profile.
Default
90% for all classes
Parameters
- mir
-
Specifies the percentage of the available link or bundle rate.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
mirror-dest
mirror-dest
Syntax
mirror-dest service-id [create] [type mirror-type] [name name]
no mirror-dest service-id
Context
[Tree] (config>mirror mirror-dest)
Full Context
configure mirror mirror-dest
Description
This command creates a context to set up a service that is intended for packet mirroring. It is configured as a service to allow mirrored packets to be directed locally (within the same router) or remotely, over the core of the network and have a far-end decode mirror encapsulation.
The mirror destination service is comprised of destination parameters that define where the mirrored packets are to be sent. It also specifies whether the defined service-id will receive mirrored packets from far-end router over the network core.
The mirror destination service IDs are persistent between boots of the router and are included in the configuration saves. The local sources of mirrored packets for the service ID are defined within the debug mirror mirror-source command that references the same service-id. Up to 255 mirror destination service IDs can be created within a single system.
The mirror-dest command creates or edits a service ID for mirroring purposes. If the service-id does not exist within the context of all defined services, the mirror destination service is created and the context of the CLI is changed to that service ID. If the service-id exists within the context of defined mirror destination services, the CLI context is changed for editing parameters on that service ID. If the service-id exists within the context of another service type, an error message is returned and CLI context is not changed from the current context.
LI source configuration is saved using the li>save command.
The no form of this command removes a mirror destination from the system. The mirror source or li-source associations with the mirror destination service-id do not need to be removed or shutdown first. The mirror destination service-id must be shutdown before the service ID can be removed. When the service ID is removed, all mirror-source or li-source commands that have the service ID defined will also be removed from the system.
Parameters
- service-id
-
The service identification identifies the service in the service domain. This ID is unique to this service and cannot be used by any other service, regardless of service type. The same service ID must be configured on every router that this particular service is defined on.
If particular a service ID already exists for a service, then the same value cannot be used to create a mirror destination service ID with the same value. For example:
If an Epipe service ID 11 exists, then a mirror destination service ID 11 cannot be created. If a VPLS service ID 12 exists, then a mirror destination service ID 12 cannot be created.
If an IES service ID 13 exists, then a mirror destination service ID 13 cannot be created.
- create
-
Keyword used to create a mirror destination service.
- mirror-type
-
The type describes the encapsulation supported by the mirror service.
- name
-
Configures an optional service name identifier, up to 64 characters, to a given service. This service name can then be used in configuration references, display, and show commands throughout the system. A defined service name can help the service provider or administrator to identify and manage services within the SR OS platforms.
To create a service, you must assign a service ID; however, after it is created, either the service ID or the service name can be used to identify and reference a service.
If a name is not specified at creation time, then SR OS assigns a string version of the service-id as the name.
Service names may not begin with an integer (0 to 9).
Platforms
All
mirror-dest-reservation
mirror-dest-reservation
Syntax
mirror-dest-reservation service-id to service-id
no mirror-dest-reservation
Context
[Tree] (config>li mirror-dest-reservation)
Full Context
configure li mirror-dest-reservation
Description
This command configures a range of service IDs reserved for RADIUS-triggered mirror destination. The range can be expanded or reduced in real time. The range cannot conflict with other service IDs.
The no form of this command removes the service IDs reserved for LI mirror destination services.
Parameters
- service-id
-
Specifies the starting or ending service ID in the range for the mirror destination.
Platforms
All
mirror-dest-template
mirror-dest-template
Syntax
mirror-dest-template name [type mirror-type] [create]
no mirror-dest-template name
Context
[Tree] (config>li mirror-dest-template)
Full Context
configure li mirror-dest-template
Description
This command creates a template used by RADIUS-triggered mirror destinations. RADIUS provides the IP destination (and other optional attributes) for the mirror destination and the mirror template provides the remaining mirror destination attributes for mirroring packets remotely over the core of an IP network.
The system supports up to eight mirror destination templates and allows a mirror destination to be swapped in real time. Only new LI sources will use the new attribute of the mirror destination template. Existing LI sources remain unchanged and continue to use the attribute of the previous mirror destination template.
The no form of this command removes a mirror destination template from the system.
Parameters
- name
-
Specifies the template name, up to 32 characters.
- mirror-type
-
Specifies the type of encapsulation supported by the mirror service.
- create
-
Keyword required to create a template.
Platforms
All
mirror-dest-template
Syntax
mirror-dest-template template-name
no mirror-dest-template
Context
[Tree] (config>li>radius mirror-dest-template)
Full Context
configure li radius mirror-dest-template
Description
This command enables or disables the use of a RADIUS triggered mirror destination template to be used by new LI sources.
Parameters
- template-name
-
Specifies the template name, up to 32 characters. The template must already exist.
Platforms
All
mirror-source
mirror-source
Syntax
mirror-source [all-inclusive] mirror-service-id
no mirror-source
Context
[Tree] (config>app-assure>group>policy>aqp>entry>action mirror-source)
Full Context
configure application-assurance group policy app-qos-policy entry action mirror-source
Description
This command configures an application-based policy mirroring service that uses this AA ISA group’s AQP entry as a mirror source. When configured, AQP entry becomes a mirror source for IP packets seen by the AA (the mirrored packet is an IP packet analyzed by AA and does not include encapsulations present on the incoming interfaces).
Default
no mirror-source
Parameters
- all-inclusive
-
Specifies that all packets during identification phase that could match a given AQP rule are mirrored in addition to packets after an application identification completes that match the AQP rule. This ensures all packets of a given flow are mirrored at a cost of sending unidentified packets that once the application is identified will no longer match this AQP entry.
- mirror-service-id
-
Specifies the mirror source service ID to use for flows that match this policy.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
mirror-source
Syntax
[no] mirror-source service-id
Context
[Tree] (debug>app-assure>group>traffic-capture>match mirror-source)
Full Context
debug app-assure group traffic-capture match mirror-source
Description
This command configures debugging on a mirror source.
mirror-source
Syntax
[no] mirror-source service-id
Context
[Tree] (config>mirror mirror-source)
Full Context
configure mirror mirror-source
Description
This command configures mirror source parameters for a mirrored service.
The mirror-source command is used to enable mirroring of packets specified by the association of the mirror-source to sources of packets defined within the context of the mirror-dest-service-id. The mirror destination service must already exist within the system.
A mirrored packet cannot be mirrored to multiple destinations. If a packet matches multiple mirror source entries (for example, a SAP on one mirror-source and a port on another mirror-source), then the packet is mirrored to a single mirror-dest-service-id based on the following precedence:
-
Filter entry
-
Subscriber (applies to the 7750 SR and 7450 ESS)
-
SAP
-
Physical port
The precedence is structured so the most specific match criteria has precedence over a less specific match. For example, if a mirror-source defines a port and a SAP on that port, then a packet arriving on the SAP will be mirrored using the SAP mirror (and not mirrored using the Port mirror) because the SAP is more specific than the port.
The no form of this command deletes all related source commands within the context of the mirror-source service-id. The command does not remove the service ID from the system.
Parameters
- service-id
-
Specifies the service identification identifies the service in the service domain. This ID is unique to this service and cannot be used by any other service, regardless of service type. The same service ID must be configured on every router that this particular service is defined on.
Platforms
All
mirror-source
Syntax
[no] mirror-source service-id
Context
[Tree] (debug mirror-source)
Full Context
debug mirror-source
Description
This command configures mirror source parameters for a mirrored service.
The mirror-source command is used to enable mirroring of packets specified by the association of the mirror-source to sources of packets defined within the context of the mirror-dest-service-id. The mirror destination service must already exist within the system.
A mirrored packet cannot be mirrored to multiple destinations. If a packet matches multiple mirror source entries (for example, a SAP on one mirror-source and a port on another mirror-source), then the packet is mirrored to a single mirror-dest-service-id based on the following precedence:
-
Filter entry
-
Subscriber (applies to the 7750 SR and 7450 ESS)
-
SAP
-
Physical port
The precedence is structured so the most specific match criteria has precedence over a less specific match. For example, if a mirror-source defines a port and a SAP on that port, then a packet arriving on the SAP will be mirrored using the SAP mirror (and not mirrored using the Port mirror) because the SAP is more specific than the port.
The mirror-source configuration is not saved when a configuration is saved. A mirror-source manually configured within an ASCII configuration file will not be preserved if that file is overwritten by a save command. Define the mirror-source within a file associated with a config exec command to make a mirror-source persistent between system reboots.
By default, all mirror destination service IDs have a mirror-source associated with them. The mirror-source is not technically created with this command. Instead the service ID provides a contextual node for storing the current mirroring sources for the associated mirror destination service ID. The mirror-source is created for the mirror service when the operator enters the debug>mirror-source svcId for the first time. If the operator enters li>li-source svcId for the first time, an LI source is created for the mirror service. The mirror-source is also automatically removed when the mirror destination service ID is deleted from the system.
The no form of this command deletes all related source commands within the context of the mirror-source service-id. The command does not remove the service ID from the system.
Parameters
- service-id
-
Specifies the mirror destination service ID for which match criteria will be defined. The service-id must already exist within the system.
Platforms
All
misc
misc
Syntax
[no] misc
Context
[Tree] (debug>router>igmp misc)
Full Context
debug router igmp misc
Description
This command enables debugging for IGMP miscellaneous information.
The no form of the command disables the debugging.
Platforms
All
Output
The following shows debugged IGMP miscellaneous information.
Sample OutputA:ALA-CA# debug router 100 igmp misc
*A:ALA-CA# show debug
debug
router "100"
igmp
misc
exit
exit
exit
*A:ALA-CA#
misc
Syntax
[no] misc
Context
[Tree] (debug>router>gmpls>event misc)
Full Context
debug router gmpls event misc
Description
This command enables and disables debugging for GMPLS Misc events.
Platforms
7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
misc
Syntax
misc [detail]
no misc
Context
[Tree] (debug>router>mpls>event misc)
[Tree] (debug>router>rsvp>event misc)
Full Context
debug router mpls event misc
debug router rsvp event misc
Description
This command debugs miscellaneous events.
The no form of the command disables the debugging.
Parameters
- detail
-
Displays detailed information about miscellaneous events.
Platforms
All
misc
misc
Syntax
[no] misc
Context
[Tree] (debug>router>isis misc)
Full Context
debug router isis misc
Description
This command enables debugging for IS-IS misc.
The no form of the command disables debugging.
Platforms
All
misc
mismatch-reaction
mismatch-reaction
Syntax
mismatch-reaction {squelch-rx}
no mismatch-reaction
Context
[Tree] (config>port>otu>pm-tti mismatch-reaction)
Full Context
configure port otu pm-tti mismatch-reaction
Description
This command allows the user to configure the consequent action to a pm-tti mismatch.
The no form of this command reverts to the default value.
Default
n/a, the received traffic is passed through.
Parameters
- squelch-rx
-
Specifies that the received traffic is blocked.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
mismatch-reaction
Syntax
mismatch-reaction {none | squelch-rx}
Context
[Tree] (config>port>otu>psi-payload mismatch-reaction)
Full Context
configure port otu psi-payload mismatch-reaction
Description
This command allows the user to configure the consequent action to a psi-payload type mismatch.
Parameters
- none
-
Specifies the received traffic is passed through.
- squelch-rx
-
Specifies the received traffic is blocked.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
mismatch-reaction
Syntax
mismatch-reaction {none | squelch-rx}
Context
[Tree] (config>port>otu>sm-tti mismatch-reaction)
Full Context
configure port otu sm-tti mismatch-reaction
Description
This command allows the user to configure the consequent action to a sm-tti mismatch.
Default
n/a
Parameters
- none
-
Specifies that the received traffic is passed through.
- squelch-rx
-
Specifies that the received traffic is blocked.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
missing-mandatory-ie
missing-mandatory-ie
Syntax
missing-mandatory-ie direction direction [create]
no missing-mandatory-ie direction direction
Context
[Tree] (config>app-assure>group>statistics>tca>gtp-filter missing-mandatory-ie)
Full Context
configure application-assurance group statistics threshold-crossing-alert gtp-filter missing-mandatory-ie
Description
This command configures a TCA for the counter capturing drops due to the GTP filter missing mandatory IE check. A missing-mandatory-ie drop TCA can be created for traffic generated from the subscriber side of AA (from-sub) or for traffic generated from the network toward the AA subscriber (to-sub). The create keyword is mandatory when creating a missing-mandatory-ie TCA.
Parameters
- direction
-
Specifies the traffic direction.
- create
-
Keyword used to create the TCA.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
mixed-lsp-mode
mixed-lsp-mode
Syntax
[no] mixed-lsp-mode
Context
[Tree] (config>service>sdp mixed-lsp-mode)
Full Context
configure service sdp mixed-lsp-mode
Description
This command enables the use by an SDP of the mixed-LSP mode of operation. This command indicates to the service manager that it must allow a primary LSP type and a backup LSP type in the same SDP configuration. For example, the lsp and ldp commands are allowed concurrently in the SDP configuration. The user can configure one or two types of LSPs under the same SDP. Without this command, these commands are mutually exclusive.
The user can configure an RSVP LSP as a primary LSP type with an LDP LSP as a backup type. The user can also configure an RFC 8277 BGP LSP as a backup LSP type.
If the user configures an LDP LSP as a primary LSP type, then the backup LSP type must be an RFC 8277 BGP labeled route.
At any given time, the service manager programs only one type of LSP in the linecard that will activate it to forward service packets according to the following priority order:
-
RSVP LSP type. Up to 16 RSVP LSPs can be entered by the user and programmed by the service manager in ingress linecard to load balance service packets. This is the highest priority LSP type.
-
LDP LSP type. One LDP FEC programmed by the service manager but the ingress card can use up to 16 LDP ECMP paths for the FEC to load balance service packets when ECMP is enabled on the node.
-
BGP LSP type. One RFC 8277-labeled BGP prefix programmed by the service manager. The ingress card can use more than one next-hop for the prefix.
In the case of the RSVP/LDP SDP, the service manager will program the NHLFE(s) for the active LSP type preferring the RSVP LSP type over the LDP LSP type. If no RSVP LSP is configured or all configured RSVP LSPs go down, the service manager will re-program the card with the LDP LSP if available. If not, the SDP goes operationally down.
When a higher priority type LSP becomes available, the service manager reverts back to this LSP at the expiry of the sdp-revert-time timer or the failure of the currently active LSP, whichever comes first. The service manager then re-programs the card accordingly. If the infinite value is configured, then the SDP reverts to the highest priority type LSP only if the currently active LSP failed.
LDP uses a tunnel down damp timer which is set to three seconds by default. When the LDP LSP fails, the SDP will revert to the RSVP LSP type after the expiry of this timer. For an immediate switchover, this timer must be set to zero. Use the config>router>ldp>tunnel-down-damp-time command.
If the user changes the value of the sdp-revert-time timer, it will take effect only at the next use of the timer. Any timer which is outstanding at the time of the change will be restarted with the new value.
If class based forwarding is enabled for this SDP, the forwarding of the packets over the RSVP LSPs will be based on the FC of the packet as in current implementation. When the SDP activates the LDP LSP type, then packets are forwarded over the LDP ECMP paths using the regular hash routine.
In the case of the LDP/BGP SDP, the service manager will prefer the LDP LSP type over the BGP LSP type. The service manager will re-program the card with the BGP LSP if available otherwise it brings down the SDP operationally.
Also note the following difference in behavior of the LDP/BGP SDP compared to that of an RSVP/LDP SDP. For a given /32 prefix, only a single route will exist in the routing table: the IGP route or the BGP route. Thus, either the LDP FEC or the BGP label route is active at any given time. The impact of this is that the tunnel table needs to be re-programmed each time a route is deactivated and the other is activated. Furthermore, the SDP revert-time cannot be used since there is no situation where both LSP types are active for the same /32 prefix.
The no form of this command disables the mixed-LSP mode of operation. The user first has to remove one of the LSP types from the SDP configuration or the command will fail.
Default
no mixed-lsp-mode
Platforms
All
mka-hello-interval
mka-hello-interval
Syntax
mka-hello-interval interval
no mka-hello-interval
Context
[Tree] (config>macsec>conn-assoc>static-cak mka-hello-interval)
Full Context
configure macsec connectivity-association static-cak mka-hello-interval
Description
This command specifies the MKA hello interval.
The no form of this command disables the MKA hello interval.
Default
mka-hello-interval 2
Parameters
- interval
-
Specifies the MKA hello interval, in seconds.
Platforms
All
mka-key-server-priority
mka-key-server-priority
Syntax
mka-key-server-priority priority
no mka-key-server-priority
Context
[Tree] (config>macsec>conn-assoc>static-cak mka-key-server-priority)
Full Context
configure macsec connectivity-association static-cak mka-key-server-priority
Description
This command specifies the key server priority used by the MACsec Key Agreement (MKA) protocol to select the key server when MACsec is enabled using static connectivity association key (CAK) security mode.
The no form of this command disables the mka-key-server-priority.
Default
mka-key-server-priority 16
Parameters
- priority
-
Specifies the priority of the server.
Platforms
All
mld
mld
Syntax
[no] mld
Context
[Tree] (config>redundancy>multi-chassis>peer>sync mld)
Full Context
configure redundancy multi-chassis peer sync mld
Description
This command specifies whether MLD protocol information should be synchronized with the multi-chassis peer.
Default
no mld
Platforms
All
mld
Syntax
[no] mld
Context
[Tree] (config>service>vprn mld)
Full Context
configure service vprn mld
Description
Commands in this context configure Multicast Listener Discovery (MLD) parameters.
The no form of this command disables MLD.
Default
no mld
Platforms
All
mld
Syntax
[no] mld
Context
[Tree] (config>router mld)
Full Context
configure router mld
Description
Commands in this context configure Multicast Listener Discovery (MLD) parameters.
The no form of the command disables MLD.
Default
no mld
Platforms
All
mld-parameters
mld-parameters
Syntax
mld-parameters
Context
[Tree] (config>subscr-mgmt>loc-user-db>ipoe>host mld-parameters)
[Tree] (config>subscr-mgmt>loc-user-db>ppp>host mld-parameters)
Full Context
configure subscriber-mgmt local-user-db ipoe host mld-parameters
configure subscriber-mgmt local-user-db ppp host mld-parameters
Description
Commands in this context configure an MLD import policy.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
mld-policy
mld-policy
Syntax
mld-policy mld-policy-name [create]
no mld-policy mld-policy-name
Context
[Tree] (config>subscr-mgmt mld-policy)
Full Context
configure subscriber-mgmt mld-policy
Description
Commands in this context create an MLD policy.
The no form of this command reverts to the default.
Parameters
- mld-policy-name
-
Specifies the MLD policy name up to 32 characters.
- create
-
Keyword required to create the configuration context.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
mld-policy
Syntax
mld-policy policy name
no mld-policy
Context
[Tree] (config>subscr-mgmt>sub-prof mld-policy)
Full Context
configure subscriber-mgmt sub-profile mld-policy
Description
This command enables Multicast Listener Discovery (MLD) processing per subscriber host.
The no form of this command reverts to the default.
Default
no mld-policy
Parameters
- policy-name
-
Specifies the name of the MLD policy, up to 32 characters. The MLD policy must be defined in the config>subscr-mgmt context.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
mld-snooping
mld-snooping
Syntax
mld-snooping
Context
[Tree] (config>service>vpls>sap mld-snooping)
[Tree] (config>service>vpls>allow-ip-int-bind mld-snooping)
[Tree] (config>service>vpls>spoke-sdp mld-snooping)
[Tree] (config>service>vpls mld-snooping)
[Tree] (config>service>vpls>mesh-sdp mld-snooping)
Full Context
configure service vpls sap mld-snooping
configure service vpls allow-ip-int-bind mld-snooping
configure service vpls spoke-sdp mld-snooping
configure service vpls mld-snooping
configure service vpls mesh-sdp mld-snooping
Description
Commands in this context configure MLD snooping parameters.
Platforms
All
mld-snooping
Syntax
[no] mld-snooping
Context
[Tree] (config>redundancy>multi-chassis>peer>sync mld-snooping)
Full Context
configure redundancy multi-chassis peer sync mld-snooping
Description
This command is not supported. It is not blocked for backwards-compatibility reasons but has no effect on the system if configured.
Default
no mld-snooping
Platforms
All
mld-snooping
Syntax
[no] mld-snooping
Context
[Tree] (debug>service>id mld-snooping)
Full Context
debug service id mld-snooping
Description
This command enables and configures MLD-snooping debugging.
The no form of this command disables MLD-snooping debugging.
Platforms
All
mld-snooping
Syntax
mld-snooping
Context
[Tree] (config>service>vpls>vxlan mld-snooping)
Full Context
configure service vpls vxlan mld-snooping
Description
This command enables the MLD snooping context.
Platforms
All
mld-snooping
Syntax
mld-snooping
Context
[Tree] (config>service>vpls>pbb>bvpls>sap mld-snooping)
[Tree] (config>service>vpls>pbb>bvpls mld-snooping)
[Tree] (config>service>vpls>pbb>bvpls>sdp mld-snooping)
Full Context
configure service vpls pbb backbone-vpls sap mld-snooping
configure service vpls pbb backbone-vpls mld-snooping
configure service vpls pbb backbone-vpls sdp mld-snooping
Description
This command configures MLD snooping attributes for I-VPLS.
Platforms
All
mldp
mldp
Syntax
[no] mldp
Context
[Tree] (config>service>vpls>provider-tunnel>inclusive mldp)
Full Context
configure service vpls provider-tunnel inclusive mldp
Description
Commands in this context configure the parameters of an LDP P2MP LSP used for forwarding Broadcast, Unicast unknown and Multicast (BUM) packets of a VPLS or B-VPLS instance.
Platforms
All
mldp
Syntax
[no] mldp
Context
[Tree] (config>service>vprn>mvpn>pt>selective mldp)
[Tree] (config>service>vprn>mvpn>pt>inclusive mldp)
Full Context
configure service vprn mvpn provider-tunnel selective mldp
configure service vprn mvpn provider-tunnel inclusive mldp
Description
This command enables use of P2MP mLDP LSP as inclusive or selective PMSI tunnels.
For multi-stream S-PMSI, either LDP or RSVP-TE must first be configured before multi-stream policy can be configured.
Default
no mldp
Platforms
All
mlfr
mlfr
Syntax
mlfr
Context
[Tree] (config>port>multilink-bundle mlfr)
Full Context
configure port multilink-bundle mlfr
Description
Commands in this context configure a Multi-link Frame Relay (MLFR) bundle.
Platforms
7450 ESS, 7750 SR-7/12/12e
mlppp
mlppp
Syntax
mlppp
Context
[Tree] (config>port>ml-bundle mlppp)
[Tree] (config>subscr-mgmt>ppp-policy mlppp)
Full Context
configure port multilink-bundle mlppp
configure subscriber-mgmt ppp-policy mlppp
Description
Commands in this context configure multi-link PPP parameters.
Platforms
7450 ESS, 7750 SR-7/12/12e
- configure port multilink-bundle mlppp
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s
- configure subscriber-mgmt ppp-policy mlppp
mlppp-profile-egress
mlppp-profile-egress
Syntax
mlppp-profile-egress profile-id [create]
no mlppp-profile-egress profile-id
Context
[Tree] (config>qos mlppp-profile-egress)
Full Context
configure qos mlppp-profile-egress
Description
This command creates a profile for the user to configure the egress QoS parameters of a multiclass MLPPP bundle.
A maximum of 128 egress QoS profiles can be created on the system.
The no form of this command deletes the profile.
Parameters
- profile-id
-
Specifies an ingress mlppp-profile ID.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
mlppp-profile-egress
Syntax
mlppp-profile-egress src-mlppp-prof dst-mlppp-prof [overwrite]
Context
[Tree] (config>qos>copy mlppp-profile-egress)
Full Context
configure qos copy mlppp-profile-egress
Description
This command copies an existing ingress mlppp-profile-egress profile ID to another egress mlppp-profile-egress profile ID. The copy command is a configuration level maintenance tool used to create new entries using an existing profile ID. If overwrite is not specified, an error occurs if the destination profile ID exists.
Parameters
- src-mlppp-prof
-
Specifies the existing source egress mlppp-profile-egress profile ID from which the copy command attempts to copy.
- dst-mlppp-prof
-
Specifies the destination egress mlppp-profile-egress profile ID to which the copy command attempts to copy.
- overwrite
-
Use this parameter when the mlppp-profile-egress dst-mlppp-prof already exists. If it does, everything in the existing destination mlppp-profile-egress dst-mlppp-prof is completely overwritten with the contents of the mlppp-profile-egress src-mlppp-prof. The overwrite parameter must be specified or else the following error message is returned:
MINOR: CLI use {overwrite}; destination mlppp-egress-profile "1010" existsIf overwrite is specified, the function of copying from source to destination occurs in a ‟break before make” manner and therefore should be handled with care.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
mlppp-profile-ingress
mlppp-profile-ingress
Syntax
[no] mlppp-profile-ingress profile-id [create]
Context
[Tree] (config>qos mlppp-profile-ingress)
Full Context
configure qos mlppp-profile-ingress
Description
This command creates a profile for the user to configure the ingress QoS parameters of a multiclass MLPPP bundle.
A maximum of 128 ingress QoS profiles can be created on the system.
The no form of this command deletes the profile.
Parameters
- profile-id
-
Specifies a specific multi-class ingress profile.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
mlppp-profile-ingress
Syntax
mlppp-profile-ingress src-mlppp-prof dst-mlppp-prof [overwrite]
Context
[Tree] (config>qos>copy mlppp-profile-ingress)
Full Context
configure qos copy mlppp-profile-ingress
Description
This command copies an existing ingress mlppp-profile-ingress profile ID to another ingress mlppp-profile-ingress profile ID. The copy command is a configuration level maintenance tool used to create new entries using an existing profile ID. If overwrite is not specified, an error occurs if the destination profile ID exists.
Parameters
- src-mlppp-prof
-
Specifies the existing source MLPPP profile ID from which the copy command attempts to copy.
- dst-mlppp-prof
-
Specifies the destination MLPPP profile ID to which the copy command attempts to copy.
- overwrite
-
Use this parameter when the mlppp-profile-ingress dst-mlppp-prof already exists. If it does, everything in the existing destination mlppp-profile-ingress dst-mlppp-prof is completely overwritten with the contents of the mlppp-profile-ingress src-mlppp-prof. The overwrite parameter must be specified or else the following error message is returned:
MINOR: CLI use {overwrite}; destination mlppp-ingress-profile "100" existsIf overwrite is specified, the function of copying from source to destination occurs in a ‟break before make” manner and therefore should be handled with care.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
mme
mme
Syntax
mme
Context
[Tree] (config>subscr-mgmt>gtp>peer-profile mme)
Full Context
configure subscriber-mgmt gtp peer-profile mme
Description
This command configures parameters specific to a Mobility Management Entity (MME) peer.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
mmrp
mmrp
Syntax
mmrp
Context
[Tree] (config>service>vpls>mrp mmrp)
Full Context
configure service vpls mrp mmrp
Description
This command configures MMRP parameters.
Platforms
All
mmrp-impm-override
mmrp-impm-override
Syntax
[no] mmrp-impm-override
Context
[Tree] (config>mcast-mgmt>chassis-level mmrp-impm-override)
Full Context
configure mcast-management chassis-level mmrp-impm-override
Description
This command enables ingress Multicast Path Management (IMPM) from monitoring PIM and IGMP.
The no form of this command disables the IMPM monitoring.
Platforms
7450 ESS, 7750 SR-1x-48D, 7750 SR-1x-92S, 7750 SR-7/12/12e, 7750 SR-s, 7950 XRS, VSR
mmrp-mac
mmrp-mac
Syntax
[no] mmrp-mac ieee-address
Context
[Tree] (debug>service>id>mrp mmrp-mac)
Full Context
debug service id mrp mmrp-mac
Description
This command filters debug events and only shows events related to the MAC address specified.
The no form of this command removes the debug filter.
Parameters
- ieee-address
-
xx:xx:xx:xx:xx:xx or xx-xx-xx-xx-xx-xx (cannot be all zeros)
Platforms
All
mobility
mobility
Syntax
mobility
Context
[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw mobility)
[Tree] (config>service>ies>sub-if>grp-if>wlan-gw mobility)
Full Context
configure service vprn subscriber-interface group-interface wlan-gw mobility
configure service ies subscriber-interface group-interface wlan-gw mobility
Description
Commands in this context configure mobility parameters.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
mobility-acct-updates
mobility-acct-updates
Syntax
[no] mobility-acct-updates
Context
[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw>vlan-tag-ranges>range>xconnect mobility-acct-updates)
[Tree] (config>service>ies>sub-if>grp-if>wlan-gw>vlan-tag-ranges>range>xconnect mobility-acct-updates)
Full Context
configure service vprn subscriber-interface group-interface wlan-gw vlan-tag-ranges range xconnect mobility-acct-updates
configure service ies subscriber-interface group-interface wlan-gw vlan-tag-ranges range xconnect mobility-acct-updates
Description
This command enables the administrative state to send mobility-triggered accounting interim updates.
The no form of this command disables sending the mobility-triggered accounting updates.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
mobility-triggered-acct
mobility-triggered-acct
Syntax
mobility-triggered-acct
Context
[Tree] (config>service>vprn>wlan-gw mobility-triggered-acct)
[Tree] (config>router>wlan-gw mobility-triggered-acct)
Full Context
configure service vprn wlan-gw mobility-triggered-acct
configure router wlan-gw mobility-triggered-acct
Description
Commands in this context configure the mobility-triggered-accounting in wlan-gw context under router or VPRN service.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
mode
mode
Syntax
mode {dropped-only | ingr-and-dropped | egr-ingr-and-dropped}
no mode
Context
[Tree] (debug>router>local-dhcp-server mode)
[Tree] (debug>router>ip>dhcp6 mode)
[Tree] (debug>router>ip>dhcp mode)
Full Context
debug router local-dhcp-server mode
debug router ip dhcp6 mode
debug router ip dhcp mode
Description
This command debugs the DHCP tracing detail level.
Parameters
- dropped-only
-
Displays only dropped packets.
- ingr-and-dropped
-
Displays only ingress packet and dropped packets.
- egr-ingr-and-dropped
-
Displays ingress, egress and dropped packets.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
- debug router local-dhcp-server mode
All
- debug router ip dhcp6 mode
- debug router ip dhcp mode
mode
Syntax
mode {dropped-only | ingr-and-dropped | egr-ingr-and-dropped}
no mode
Context
[Tree] (debug>service>id>ppp>packet mode)
Full Context
debug service id ppp packet mode
Description
This command specifies PPP packet debug mode.
The no form of this command disables debugging.
Parameters
- dropped-only
-
Displays only dropped packets.
- ingr-and-dropped
-
Displays only ingress packet and dropped packets.
- egr-ingr-and-dropped
-
Displays ingress, egress and dropped packets.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
mode
Syntax
mode {strict | loose | strict-no-ecmp}
no mode
Context
[Tree] (config>service>vprn>if>ipv6>urpf-check mode)
[Tree] (config>service>vprn>if>urpf-check mode)
[Tree] (config>service>vprn>nw-if>urpf-check mode)
[Tree] (config>service>ies>if>urpf-check mode)
[Tree] (config>service>ies>sub-if>grp-if>ipv6>urpf-check mode)
[Tree] (config>service>vprn>sub-if>grp-if>urpf-check mode)
[Tree] (config>service>ies>if>ipv6>urpf-check mode)
Full Context
configure service vprn interface ipv6 urpf-check mode
configure service vprn interface urpf-check mode
configure service vprn network-interface urpf-check mode
configure service ies interface urpf-check mode
configure service ies subscriber-interface group-interface ipv6 urpf-check mode
configure service vprn subscriber-interface group-interface urpf-check mode
configure service ies interface ipv6 urpf-check mode
Description
This command specifies the mode of unicast RPF check.
The no form of this command reverts to the default (strict) mode.
Default
mode strict
Parameters
- strict
-
When specified, uRPF checks whether incoming packet has a source address that matches a prefix in the routing table, and whether the interface expects to receive a packet with this source address prefix.
- loose
-
In loose mode, uRPF checks whether incoming packet has source address with a corresponding prefix in the routing table. However, the loose mode does not check whether the interface expects to receive a packet with a specific source address prefix. This object is valid only when urpf-check is enabled.
- strict-no-ecmp
-
When a packet is received on an interface in this mode and the SA matches an ECMP route the packet is dropped by uRPF.
Platforms
All
- configure service vprn interface urpf-check mode
- configure service vprn interface ipv6 urpf-check mode
- configure service vprn network-interface urpf-check mode
- configure service ies interface urpf-check mode
- configure service ies interface ipv6 urpf-check mode
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
- configure service ies subscriber-interface group-interface ipv6 urpf-check mode
- configure service vprn subscriber-interface group-interface urpf-check mode
mode
Syntax
mode {strict | loose | strict-no-ecmp}
no mode
Context
[Tree] (config>subscr-mgmt>git>ipv4>urpf-check mode)
Full Context
configure subscriber-mgmt group-interface-template ipv4 urpf-check mode
Description
This command configures the mode of Unicast RPF (uRPF) check.
The no form of this command reverts to the default.
Default
mode strict
Parameters
- strict
-
Specifies that the uRPF checks whether the incoming packet has a source IP address that matches a prefix in the routing table, and whether the interface expects to receive a packet with this source IP address prefix.
- loose
-
Specifies that the uRPF checks whether the incoming packet has a source IP address with a corresponding prefix in the routing table. However, the loose mode does not check whether the interface expects to receive a packet with a specific source IP address prefix. This object is valid only when the urpf-check command is enabled.
- strict-no-ecmp
-
Specifies that when a packet is received on an interface in this mode and the SA matches an ECMP route, the packet is dropped by uRPF.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
mode
Syntax
mode {none | basic | advanced}
Context
[Tree] (config>system>pwr-mgmt mode)
Full Context
configure system power-management mode
Description
This command sets the power mode.
Default
mode basic
Parameters
- none
-
Specifies that there is no management of power to modules. In this mode, no gradual shutdown of active XCMs and XMAs is enforced. No spare capacity is reserved and any APEQ failure may result in brownouts or card failures.
- basic
-
Specifies that the node will bring up as many provisioned modules (in order of priority) as possible using the N+1 algorithm. In basic mode the system shuts down IO cards when power capacity drops below the Power Safety Level.
- advanced
-
Specifies that the operator can maintain a spare APEQ as long as possible to make it immune to the possibility of power brown-outs. In advanced mode, the system starts shutting down IO cards when the power capacity drops below the Power Safety Level + Max rated APEQ.
Platforms
7750 SR-1s, 7750 SR-2s, 7750 SR-7s, 7750 SR-14s, 7950 XRS
mode
Syntax
mode {automatic | manual}
Context
[Tree] (config>port>dwdm>coherent mode)
Full Context
configure port dwdm coherent mode
Description
This command configures the mode used to compensate for chromatic dispersion.
Parameters
- automatic
-
Sets to automatic mode.
- manual
-
Sets to manual mode.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
mode
Syntax
mode {none | uni-n}
Context
[Tree] (config>port>ethernet>elmi mode)
Full Context
configure port ethernet elmi mode
Description
This command configures the Ethernet LMI mode.
Parameters
- none
-
Specifies that the E LMI mode is set to none.
- uni-n
-
Specifies that the E LMI mode is set to UNI-N.
Platforms
All
mode
Syntax
mode {access | network | hybrid}
no mode
Context
[Tree] (config>port>ethernet mode)
[Tree] (config>port>sonet-sdh>path mode)
[Tree] (config>port>tdm>e3 mode)
[Tree] (config>lag mode)
[Tree] (config>port>tdm>e1>channel-group mode)
[Tree] (config>port>tdm>ds1>channel-group mode)
[Tree] (config>port>tdm>ds3 mode)
Full Context
configure port ethernet mode
configure port sonet-sdh path mode
configure port tdm e3 mode
configure lag mode
configure port tdm e1 channel-group mode
configure port tdm ds1 channel-group mode
configure port tdm ds3 mode
Description
This command configures an Ethernet port, TDM channel, or SONET/SDH path (sub-port) for access, network, or hybrid mode operation.
An access port or channel is used for customer facing traffic on which services are configured. A Service Access Point (SAP) can only be configured on an access port or channel. When a port is configured for access mode, the appropriate encap-type must be specified to distinguish the services on the port or SONET path. Once an Ethernet port, a TDM channel or a SONET path has been configured for access mode, multiple services can be configured on the Ethernet port, a TDM channel or SONET path.
A network port or channel participates in the service provider transport or infrastructure network when a network mode is selected. When the network option is configured, the encap-type cannot be configured for the port/channel.
When network mode is selected on a SONET/SDH path, the appropriate control protocols are activated when the need arises. For example, configuring an IP interface on the SONET path activates IPCP while the removal of the IP interface causes the IPCP to be removed. The same applies for MPLS, MPLSCP, and OSICP. When configuring a SONET/SDH port, the mode command must be entered in the channel context or an error message is generated.
A hybrid Ethernet port allows the combination of network and access modes of operation on a per-VLAN basis and must be configured as either dot1q or QinQ encapsulation.
When the hybrid port is configured to the dot1q encapsulation, the user configures a SAP inside a service simply by providing the SAP ID which must include the port-id value of the hybrid mode port and an unused VLAN tag value. The format is <port-id>:qtag1. A SAP of format <port-id>:* also supported.
The user configures a network IP interface under config>router>if>port by providing the port name which consists of the port-id of the hybrid mode port and an unused VLAN tag value. The format is <port-id>:qtag1. The user must explicitly enter a valid value for qtag1. The <port-id>:* value is not supported on a network IP interface. The 4096 VLAN tag space on the port is shared among VLAN SAPs and VLAN network IP interfaces.
When the hybrid port is configured to QinQ encapsulation, the user configures a SAP inside a service simply by providing the SAP ID which must include the port-id value of the hybrid mode port and the outer and inner VLAN tag values. The format is <port-id>:qtag1.qtag2. A SAP of format <port-id>: qtag1.* is also supported. The outer VLAN tag value must not have been used to create an IP network interface on this port. In addition, the qtag1.qtag2 value combination must not have been used by another SAP on this port.
The user configures a network IP interface under config>router>if>port by providing the port name which consists of the port-id of the hybrid mode port and a VLAN tag value. The format is <port-id>:qtag1.*. An outer VLAN tag qtag2 of * creates an IP network interface. In addition, the qtag1.qtag2 value combination must not have been used on another SAP or IP network interface on this port.
The no form of this command restores the default.
Default
mode network — For Ethernet ports
mode access — For TDM channel or SONET paths
Parameters
- access
-
Configures the Ethernet port, TDM channel or SONET path as service access.
- network
-
Configures the Ethernet port, TDM channel or SONET path for transport network use.
- hybrid
-
Configures the Ethernet port for hybrid use.
Platforms
All
- configure lag mode
- configure port ethernet mode
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
- configure port sonet-sdh path mode
7450 ESS, 7750 SR-7/12/12e, 7750 SR-a, 7750 SR-e
- configure port tdm ds3 mode
- configure port tdm e1 channel-group mode
- configure port tdm e3 mode
- configure port tdm ds1 channel-group mode
mode
Syntax
mode {active | passive}
Context
[Tree] (config>port>ethernet>efm-oam mode)
Full Context
configure port ethernet efm-oam mode
Description
This command configures the mode of OAM operation for this Ethernet port. These two modes differ in that active mode causes the port to continually send out efm-oam info PDUs while passive mode waits for the peer to initiate the negotiation process. A passive mode port cannot initiate monitoring activities (such as loopback) with the peer.
Default
mode active
Parameters
- active
-
Provides capability to initiate negotiation and monitoring activities.
- passive
-
Relies on peer to initiate negotiation and monitoring activities.
Platforms
All
mode
Syntax
mode {dce | dte | bidir}
Context
[Tree] (config>port>ml-bundle>mlfr>frame-relay mode)
Full Context
configure port multilink-bundle mlfr frame-relay mode
Description
This command configures the DCE/DTE mode of the Frame Relay interface.
Parameters
- dce
-
Enables the DCE mode.
- dte
-
Enables the DTE mode.
- bidir
-
Enables the bidirectional mode for LMI types ANSI and ITU.
Platforms
7450 ESS, 7750 SR-7/12/12e
mode
Syntax
mode {dce | dte | bidir}
Context
[Tree] (config>port>tdm>e3>frame-relay mode)
[Tree] (config>port>tdm>ds1>channel-group>frame-relay mode)
[Tree] (config>port>sonet-sdh>path>frame-relay mode)
[Tree] (config>port>tdm>ds3>frame-relay mode)
[Tree] (config>port>tdm>e1>channel-group>frame-relay mode)
[Tree] (config>port>multi-link-bundle>mlfr>frame-relay mode)
Full Context
configure port tdm e3 frame-relay mode
configure port tdm ds1 channel-group frame-relay mode
configure port sonet-sdh path frame-relay mode
configure port tdm ds3 frame-relay mode
configure port tdm e1 channel-group frame-relay mode
configure port multilink-bundle mlfr frame-relay mode
Description
This command sets the Frame Relay interface into the DCE, DTE, or Bidirectional mode of LMI operation. The DTE mode causes the router to send status inquiries over the interface. The DCE mode causes the router to respond to status inquiries. In bidirectional mode, the router performs both DTE and DCE operation over the FR interface. The bidirectional mode applies to the ANSI and ITU LMI types only.
This feature is used when two routers are connected back-to-back, running frame relay encapsulation.
Default
mode dte
Parameters
- dce
-
Enables the DCE mode.
- dte
-
Enables the DTE mode.
- bidir
-
Enables the bidirectional mode for LMI types ANSI and ITU.
Platforms
7450 ESS, 7750 SR-7/12/12e, 7750 SR-a, 7750 SR-e
- configure port tdm e3 frame-relay mode
- configure port tdm e1 channel-group frame-relay mode
- configure port tdm ds3 frame-relay mode
- configure port tdm ds1 channel-group frame-relay mode
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
- configure port sonet-sdh path frame-relay mode
7450 ESS, 7750 SR-7/12/12e
- configure port multilink-bundle mlfr frame-relay mode
mode
Syntax
mode {manual | auto | off}
Context
[Tree] (config>service>system>bgp-evpn>eth-seg>service-carving mode)
Full Context
configure service system bgp-evpn ethernet-segment service-carving mode
Description
This command configures the service-carving mode. This determines how the DF is elected for a specified Ethernet-Segment and service.
Default
mode auto
Parameters
- auto
-
This mode is the service-carving algorithm defined in RFC 7432. The DF for the service is calculated based on the modulo function of the service (identified by either the evi or the isid) and the number of PEs.
- manual
-
In this mode the DF is elected based on the manual configuration added in the service-carving>manual context.
- off
-
In this mode all the services elect the same DF PE (assuming the same PEs are active for all the configured services). The PE with the lowest IP is elected as DF for the Ethernet-Segment.
Platforms
All
mode
Syntax
mode mode
Context
[Tree] (config>service>vpls>pim-snooping mode)
Full Context
configure service vpls pim-snooping mode
Description
This command sets the PIM snooping mode to proxy or plain snooping.
Parameters
- mode
-
Specifies PIM snooping mode
Platforms
All
mode
Syntax
mode {rstp | comp-dot1w | dot1w | mstp | pmstp}
no mode
Context
[Tree] (config>service>template>vpls-template>stp mode)
[Tree] (config>service>vpls>stp mode)
Full Context
configure service template vpls-template stp mode
configure service vpls stp mode
Description
This command specifies the version of Spanning Tree Protocol the bridge is currently running.
See section Spanning Tree Operating Modes for more information about these modes.
The no form of this command returns the STP variant to the default.
Default
mode rstp
Parameters
- rstp
-
Corresponds to the Rapid Spanning Tree Protocol specified in IEEE 802.1D/D4-2003
- dot1w
-
Corresponds to the mode where the Rapid Spanning Tree is backward compatible with IEEE 802.1w
- compdot1w
-
Corresponds to the Rapid Spanning Tree Protocol in conformance with IEEE 802.1w
- mstp
-
Sets MSTP as the STP mode of operation. Corresponds to the Multiple Spanning Tree Protocol specified in 802.1Q REV/D5.0-09/200
- pmstp
-
The PMSTP mode is only supported in VPLS services where the M-VPLS flag is configured
Platforms
All
mode
Syntax
mode {all | dropped-only}
no mode
Context
[Tree] (debug>service>id>arp-host mode)
Full Context
debug service id arp-host mode
Description
This command configures the ARP host tracing mode.
Parameters
- all
-
Debugs all dropped packets.
- dropped-only
-
Only displays dropped packets.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
mode
Syntax
mode {dropped-only | ingr-and-dropped | egr-ingr-and-dropped}
no mode
Context
[Tree] (debug>service>id>igmp-snooping mode)
Full Context
debug service id igmp-snooping mode
Description
This command enables and configures the IGMP tracing mode.
The no form of this command disables the configures the IGMP tracing mode.
Platforms
All
mode
Syntax
mode {dropped-only | ingr-and-dropped | egr-ingr-and-dropped}
no mode
Context
[Tree] (debug>service>id>mld mode)
Full Context
debug service id mld-snooping mode
Description
This command enables and configures the MLD tracing mode.
The no form of this command disables the configures the MLD tracing mode.
Platforms
All
mode
Syntax
mode {mesh-group | standard}
Context
[Tree] (config>service>vprn>msdp>group mode)
Full Context
configure service vprn msdp group mode
Description
This command configures groups of peers in a full mesh topology to limit excessive flooding of source-active messages to neighboring peers.
Multicast Source Discovery Protocol (MSDP) peers can be configured grouped in a full-mesh topology that prevents excessive flooding of source-active messages to neighboring peers.
In a meshed configuration, all members of the group must have a peer connection with every other mesh group member. If this rule is not adhered to, then unpredictable results may occur.
Default
mode standard
Parameters
- mesh-group
-
Specifies that source-active message received from a mesh group member are always accepted but are not flooded to other members of the same mesh group. These source-active messages are only flooded to non-mesh group peers or members of other mesh groups.
- standard
-
Specifies a non-meshed mode.
Platforms
All
mode
Syntax
mode {auto | napt | one-to-one}
no mode
Context
[Tree] (config>service>vprn>nat>outside>pool mode)
Full Context
configure service vprn nat outside pool mode
Description
This command configures the mode of operation of this NAT address pool.
The mode value is only relevant while the value of pool type is equal to largeScale; while the value of pool type is equal to l2Aware, the mode of operation is always NAPT.
Default
mode auto
Parameters
- napt
-
Specifies NAPT (Network Address Port Translation)
- auto
-
The system selects the actual mode based upon other configuration parameters; the actual mode can be NAPT or 1:1 NAT (also known as 'Basic NAT').
- one-to-one
-
Indicates 1:1 NAT (also known as 'Basic NAT')
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
mode
Syntax
mode {dropped-only | ingr-and-dropped | egr-ingr-and-dropped}
no mode
Context
[Tree] (debug>service>id>dhcp mode)
Full Context
debug service id dhcp mode
Description
This command configures the DHCP tracing mode.
The no form of the command disables debugging.
Parameters
- dropped-only
-
Only displays dropped packets.
- ingr-and-dropped
-
Only displays ingress packet and dropped packets.
- egr-ingr-and-dropped
-
Displays ingress, egress and dropped packets.
Platforms
All
mode
Syntax
mode mode
Context
[Tree] (config>gmpls-tun-grp mode)
Full Context
configure gmpls-tun-grp mode
Description
This command sets the operating mode of the GMPLS tunnel group.
In load-sharing mode, traffic is load-shared across the member GMPLS LSPs of the tunnel group. The same hashing algorithm is used as for LAG (see the "LAG and ECMP hashing" chapter of the 7450 ESS, 7750 SR, 7950 XRS, and VSR Interface Configuration Guide). If load-sharing is configured, then all of the GMPLS LSPs must terminate on the same far-end node. All of the ports used by GMPLS LSPs must be equivalent in that they must have the same named QoS policy, bandwidth, and so on Once more than one gLSP is associated with a tunnel group, the QoS policy / scheduler policy cannot be changed for any of the ports. All GMPLS LSPs must be unprotected end-to-end. Segment protection is allowed for GMPLS LSPs associated in a load sharing mode tunnel group.
In active-standby mode, only one member gLSP can be associated with the tunnel group.
The no form of this command removes the member.
Default
mode load-sharing
Parameters
- mode
-
Specifies the operating mode of the GMPLS tunnel group.
Platforms
7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
mode
Syntax
mode mode
Context
[Tree] (config>app-assure>group>gtp mode)
Full Context
configure application-assurance group gtp mode
Description
This command is used to either untunnel GTP-U traffic received on UDP port number 2152, or apply GTP filtering/firewall rules as specified under this GTP CLI context.
Default
mode filtering
Parameters
- mode
-
Specifies the operational mode of the command.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
mode
Syntax
mode {auto | napt | one-to-one}
no mode
Context
[Tree] (config>router>nat>outside>pool mode)
Full Context
configure router nat outside pool mode
Description
This command specifies the mode of operation of this NAT address pool.
The no form of the command reverts to the default.
Default
auto
Parameters
- {auto | napt | one-to-one}
-
Specifies the mode of operation of this NAT pool.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
mode
Syntax
mode {mesh-group | standard}
Context
[Tree] (config>router>msdp>group mode)
Full Context
configure router msdp group mode
Description
This command configures groups of peers in a full mesh topology to limit excessive flooding of source-active messages to neighboring peers.
Multicast Source Discovery Protocol (MSDP) peers can be configured grouped in a full-mesh topology that prevents excessive flooding of source-active messages to neighboring peers.
In a meshed configuration, all members of the group must have a peer connection with every other mesh group member. If this rule is not adhered to, then unpredictable results may occur.
Default
mode standard
Parameters
- mesh-group
-
Specifies that source-active message received from a mesh group member are always accepted but are not flooded to other members of the same mesh group. These source-active messages are only flooded to non-mesh group peers or members of other mesh groups.
- standard
-
Specifies a non-meshed mode.
Platforms
All
mode
Syntax
mode {strict | loose | strict-no-ecmp}
Context
[Tree] (config>router>if>ipv6>urpf-check mode)
[Tree] (config>router>if>urpf-check mode)
Full Context
configure router interface ipv6 urpf-check mode
configure router interface urpf-check mode
Description
This command specifies the mode of unicast RPF check.
The no form of this command reverts to the default (strict) mode.
Default
mode strict
Parameters
- strict
-
When specified, uRPF checks whether incoming packet has a source address that matches a prefix in the routing table, and whether the interface expects to receive a packet with this source address prefix.
- loose
-
In loose mode, uRPF checks whether incoming packet has source address with a corresponding prefix in the routing table. However, the loose mode does not check whether the interface expects to receive a packet with a specific source address prefix. This object is valid only when urpf-check is enabled.
- strict-no-ecmp
-
When a packet is received on an interface in this mode and the SA matches an ECMP route the packet is dropped by uRPF.
Platforms
All
mode
Syntax
mode {ecmp-protected | linear}
no mode
Context
[Tree] (config>router>segment-routing>maintenance-policy mode)
Full Context
configure router segment-routing maintenance-policy mode
Description
This command specifies the data path programming and protection mechanism for SR policy candidate paths to which the maintenance policy is applied.
In both the linear mode and ecmp-protected modes, if two or more candidate paths of the same {headend, color, endpoint} and also have the same mode, then the best preference path is treated as the primary while the next best preference path is the standby. If a third path is present in the linear mode, then this is treated as a tertiary and also programmed in the IOM.
If the currently active path goes unavailable due to S-BFD, the system failovers to the next best preference available candidate path. If S-BFD is down on all segment lists of all programmed candidate paths of an SR Policy, then the SR Policy is marked as down in TTM.
If the default mode is specified, the router only programs the segment lists of the best preference paths in the IOM.
The no form of this command removes the configured mode.
Default
no mode
Parameters
- ecmp-protected
-
Specifies only the top two routes (paths) are programmed in the IOM. Up to 32 segment lists can be programmed for each path.
- linear
-
Specifies the top three routes are programmed in the IOM. Only one segment list is allowed per path.
Platforms
All
mode
Syntax
mode {target-defined | on-change | sample}
Context
[Tree] (config>system>telemetry>persistent-subscriptions>subscription mode)
Full Context
configure system telemetry persistent-subscriptions subscription mode
Description
This command configures the subscription path mode for telemetry notifications that are sent for the persistent subscription.
Default
mode target-defined
Parameters
- target-defined
-
Keyword specifying that target defined mode is used.
- on-change
-
Keyword specifying that on change mode is used.
- sample
-
Keyword specifying that sample mode is used.
Platforms
All
mode-annexb
mode-annexb
Syntax
[no] mode-annexb
Context
[Tree] (config>port>aps mode-annexb)
Full Context
configure port aps mode-annexb
Description
This command configures the APS group for 1+1 Optimized operation as described in Annex B of ITU.T G.841. Note that Annex B operates in non-revertive bi-directional switching mode only as defined in G.841.
Platforms
7450 ESS, 7750 SR-7/12/12e, 7750 SR-a, 7750 SR-e
modify-buffer-allocation-rate
modify-buffer-allocation-rate
Syntax
modify-buffer-allocation-rate
Context
[Tree] (config>port modify-buffer-allocation-rate)
Full Context
configure port modify-buffer-allocation-rate
Description
Commands in this context configure ingress and egress percentage of rate parameters. This command only applies to physical ports (for example, it will not work on APS or similar logical ports). The percentage of rate commands are used to define a percentage value that affects the amount of buffers used by ingress and egress port managed buffer space. Enter the modify-buffer-allocation-rate context when editing the port’s percentage of rate commands.
Platforms
All
module
module
Syntax
module cpm-slot
Context
[Tree] (config>system>bluetooth module)
Full Context
configure system bluetooth module
Description
Commands in this context define Bluetooth parameters for the specific CPM slot.
Parameters
- cpm-slot
-
Specifies the CPM slot.
Platforms
7750 SR-1, 7750 SR-s, 7950 XRS-20e
mofrr
mofrr
Syntax
[no] mofrr
Context
[Tree] (debug>router>pim mofrr)
Full Context
debug router pim mofrr
Description
This command enables debugging for PIM multicast fast failover (MoFRR).
The no form of this command disables MoFRR debugging.
Platforms
All
mon-hw-agg-shaper-sch
mon-hw-agg-shaper-sch
Syntax
[no] mon-hw-agg-shaper-sch
Context
[Tree] (config>port>ethernet>access>egress>vport mon-hw-agg-shaper-sch)
Full Context
configure port ethernet access egress vport mon-hw-agg-shaper-sch
Description
This command enables congestion monitoring of the hardware aggregate shaper scheduler on the specified vport.
The no form of this command disables congestion monitoring.
Default
no mon-hw-agg-shaper-sch
Platforms
7750 SR-1, 7750 SR-s
mon-port-sch
mon-port-sch
Syntax
[no] mon-port-sch
Context
[Tree] (config>port>ethernet mon-port-sch)
[Tree] (config>port>ethernet>access>egress>vport mon-port-sch)
Full Context
configure port ethernet mon-port-sch
configure port ethernet access egress vport mon-port-sch
Description
This command enables congestion monitoring on an Egress Port Scheduler (EPS) that is applied to a physical port or to a Vport.
Congestion monitoring must be further configured under the port-scheduler CLI hierarchy. Once the congestion monitoring is in effect, the offered rate (incoming traffic) is compared to the configured port-scheduler congestion threshold. The results of these measurements are stored as the number of samples representing the number of times the offered rates exceeded the configured congestion threshold since the last clearing of the stats. Therefore, the results represent the number of times that the port-scheduler that is applied to a port/Vport was congested since the last reset of the stats (via a clear command).
The no form of this command disables congestion monitoring.
Default
no mon-port-sch
Platforms
All
monitor
monitor
Syntax
monitor ip-prefix/length
no monitor
Context
[Tree] (config>service>ies>sub-if>wlan-gw>redundancy monitor)
Full Context
configure service ies subscriber-interface wlan-gw redundancy monitor
Description
This command specifies an IPv4 route (prefix/length) per subscriber-interface to be monitored in the FDB to determine liveness of the subscriber-interface (and consequently all associated group-interfaces of type wlangw) on a peer WLAN-GW. This route is the one that is advertised in routing by the peer WLAN-GW when the subscriber-interface and WLAN-GW group are operationally up.
Parameters
- ip-prefix/length
-
Specifies the IP prefix and length.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
monitor
Syntax
monitor ip-prefix/length
no monitor
Context
[Tree] (config>service>vprn>nat>outside>pool>redundancy monitor)
[Tree] (config>router>nat>outside>pool>redundancy monitor)
Full Context
configure service vprn nat outside pool redundancy monitor
configure router nat outside pool redundancy monitor
Description
This command configures the monitoring route based on which the NAT multi-chassis switchover is triggered. Monitoring route of a NAT pool on the local node must match the export route of a corresponding NAT pool on the peering node. Presence of the monitoring route in the routing table is an indication that the peering NAT pool is active (since it is advertising its export route). The disappearance of the monitoring route from the routing table is an indication that the peering pool has failed and consequently the nodal switchover is triggered, the local pool becomes active and its export route is consequently advertised. The export route can be advertised only from:
-
The active lead pool.
-
Active pool for which fate-sharing is disabled.
Default
no monitor
Parameters
- ip-prefix/length
-
Specifies the IP prefix and length.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
monitor
Syntax
[no] monitor
Context
[Tree] (config>service>vprn>bgp>group monitor)
[Tree] (config>router>bgp monitor)
[Tree] (config>router>bgp>group monitor)
[Tree] (config>service>vprn>bgp>group>neighbor monitor)
[Tree] (config>router>bgp>group>neighbor monitor)
Full Context
configure service vprn bgp group monitor
configure router bgp monitor
configure router bgp group monitor
configure service vprn bgp group neighbor monitor
configure router bgp group neighbor monitor
Description
Commands in this context configure monitor parameters.
The no form of this command disables BGP BMP monitoring.
Platforms
All
monitor
Syntax
[no] monitor
Context
[Tree] (config>app-assure>group>ip-id-asst>pdns monitor)
Full Context
configure application-assurance group ip-identification-assist passive-dns monitor
Description
This command configures the router to collect IP addresses by passively monitoring DNS traffic. The router uses the collected IP addresses to build its internal database.
The no form of this command disables passive DNS monitoring.
Default
monitor
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
monitor-agg-egress-queue-stats
monitor-agg-egress-queue-stats
Syntax
[no] monitor-agg-egress-queue-stats
Context
[Tree] (config>port monitor-agg-egress-queue-stats)
Full Context
configure port monitor-agg-egress-queue-stats
Description
This command enables the monitoring of aggregate egress queue statistics on the port. All queues on the port are monitored, including SAP egress, network egress, subscriber egress, and egress queue group queues, as well as system queues that can be used, for example, to send port-related protocol packets (LACP, EFM, and so on). The aggregate in-profile, out-of-profile, and total statistics are provided for both forwarded and dropped packets and octets.
Monitoring of aggregate statistics is supported on PXC sub-ports but not on a PXC physical port. It is also not supported on satellite ports.
The no form of this command disables aggregate egress queue statistics monitoring on the specified port.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
monitor-bandwidth
monitor-bandwidth
Syntax
[no] monitor-bandwidth
Context
[Tree] (config>router>mpls>lsp>auto-bandwidth monitor-bandwidth)
[Tree] (config>router>mpls>lsp-template>auto-bandwidth monitor-bandwidth)
Full Context
configure router mpls lsp auto-bandwidth monitor-bandwidth
configure router mpls lsp-template auto-bandwidth monitor-bandwidth
Description
This command enables the collection and display of auto-bandwidth measurements, but prevents any automatic bandwidth adjustments from taking place.
The no form of this command disables the collection and display of auto-bandwidth measurements.
Platforms
All
monitor-oper-group
monitor-oper-group
Syntax
monitor-oper-group name priority-step step
no monitor-oper-group
Context
[Tree] (config>service>ies>sub-if>grp-if>srrp monitor-oper-group)
[Tree] (config>service>vprn>sub-if>grp-if>srrp monitor-oper-group)
Full Context
configure service ies subscriber-interface group-interface srrp monitor-oper-group
configure service vprn subscriber-interface group-interface srrp monitor-oper-group
Description
This command will configure the association between the SRRP instance in a Fate Sharing Group and the operational-group that contains messaging SAPs. A state transition of a messaging SAP within an operational-group will trigger calculation of the priority for all SRRP instances that are associated with that operational-group.
The no form of this command reverts to the default.
Parameters
- name
-
Specifies the name of the operational-group, up to 32 characters, that is tracking operational state of SRRP messaging SAPs
- priority-step
-
Specifies the priority step for which the priority of an SRRP instance is changed. If a messaging SAP within an operational-group transition to a non-UP state, the priority is decreased by the step value. If the messaging SAP within the operational-group transition into the UP state, the priority of the SRRP instance is increased by the step value.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
monitor-oper-group
Syntax
monitor-oper-group name
no monitor-oper-group
Context
[Tree] (config>lag monitor-oper-group)
Full Context
configure lag monitor-oper-group
Description
This command, supported on access LAG only, specifies the operational group to monitor. The state of the operational group affects the state of this LAG. When the operational group is inactive, the state of the LAG goes down and the LAG uses the configured lag>standby-signaling mechanism (lacp or power-off) to signal the CE that the LAG is not available.
Default
no monitor-oper-group
Parameters
- name
-
Specifies the name of the oper-group, up to 32 characters.
Platforms
All
monitor-oper-group
Syntax
monitor-oper-group name
no monitor-oper-group
Context
[Tree] (config>service>vpls>sap monitor-oper-group)
[Tree] (config>service>vpls>site monitor-oper-group)
[Tree] (config>service>vpls>spoke-sdp monitor-oper-group)
[Tree] (config>service>vpls>bgp>pw-template-binding monitor-oper-group)
Full Context
configure service vpls sap monitor-oper-group
configure service vpls site monitor-oper-group
configure service vpls spoke-sdp monitor-oper-group
configure service vpls bgp pw-template-binding monitor-oper-group
Description
This command specifies the operational group to be monitored by the object under which it is configured. The oper-group name must be already configured under the config>service context before its name is referenced in this command.
The no form of this command removes the association.
Default
no monitor-oper-group
Parameters
- group-name
-
Specifies a character string of maximum 32 ASCII characters identifying the group instance.
Platforms
All
monitor-oper-group
Syntax
monitor-oper-group group-name
no monitor-oper-group
Context
[Tree] (config>service>epipe>sap monitor-oper-group)
[Tree] (config>service>epipe>spoke-sdp monitor-oper-group)
Full Context
configure service epipe sap monitor-oper-group
configure service epipe spoke-sdp monitor-oper-group
Description
This command specifies the operational group to be monitored by the object under which it is configured. The oper-group name must be already configured under the config>service context before its name is referenced in this command.
The no form of this command removes the association.
Parameters
- group-name
-
Specifies an oper group name.
Platforms
All
monitor-oper-group
Syntax
monitor-oper-group group-name
no monitor-oper-group
Context
[Tree] (config>service>epipe>pw-port monitor-oper-group)
Full Context
configure service epipe pw-port monitor-oper-group
Description
This command configures the monitoring operational group name, up to 32 characters in length, associated with this PW-port entry.
Parameters
- group-name
-
Specifies an operational group to monitor.
Platforms
All
monitor-oper-group
Syntax
monitor-oper-group name
no monitor-oper-group
Context
[Tree] (config>service>ies>if monitor-oper-group)
Full Context
configure service ies interface monitor-oper-group
Description
This command specifies the operational group to be monitored by the object under which it is configured. The oper-group name must be already configured under the config>service context before its name is referenced in this command.
The no form of this command removes the association from the configuration.
Default
no monitor-oper-group
Parameters
- name
-
Specifies a character string of maximum 32 ASCII characters identifying the group instance.
Platforms
All
monitor-oper-group
Syntax
monitor-oper-group name
no monitor-oper-group
Context
[Tree] (config>service>vprn>if monitor-oper-group)
Full Context
configure service vprn interface monitor-oper-group
Description
This command specifies the operational group to be monitored by the object under which it is configured. The oper-group name must be already configured under the config>service context before its name is referenced in this command.
The no form of this command removes the association from the configuration.
Default
no monitor-oper-group
Parameters
- name
-
Specifies a character string, up to 32 ASCII characters, identifying the group instance.
Platforms
All
monitor-oper-group
Syntax
monitor-oper-group group-name family {ipv4 | ipv6} add [1..4294967295]
monitor-oper-group group-name family {ipv4 | ipv6} set [1..4294967295]
monitor-oper-group group-name family {ipv4 | ipv6} subtract [1..4294967295]
no monitor-oper-group [family {ipv4 | ipv6}]
Context
[Tree] (config>service>vprn>pim>if monitor-oper-group)
Full Context
configure service vprn pim interface monitor-oper-group
Description
This command configures PIM to monitor the state of an operational group to provide a redundancy mechanism. PIM monitors the operational group and changes its DR priority to the specified value when the status of the operational group is up. This enables the router to become the PIM DR only when the operational group is up. If the operational group status changes to down, PIM changes its DR priority to the default or the value configured with priority under config>service>vprn>pim>if. The oper-group group-name must already be configured under the config>service context before its name is referenced in this command. Two operational groups are supported per PIM interface.
The no form of this command removes the operational group from the configuration.
Parameters
- group-name
-
Specifies the operational group identifier up to 32 characters in length.
- family
-
Specifies the address family.
- ipv4
-
Specifies the IPv4 designated router priority.
- ipv6
-
Specifies the IPv6 designated router priority.
- add
-
Specifies that the value is to be added to the existing priority to become the designated router.
- subtract
-
Specifies that the value is to be subtracted from the existing priority to become the designated router.
- set
-
Specifies the priority to become the designated router.
- value
-
Specifies the priority modifier expressed as a decimal integer.
Platforms
All
monitor-oper-group
Syntax
monitor-oper-group name health-drop drop
no monitor-oper-group name
Context
[Tree] (config>isa>nat-group>inter-chassis-redundancy monitor-oper-group)
Full Context
configure isa nat-group inter-chassis-redundancy monitor-oper-group
Description
This command enables monitoring of the objects, such as SAPs, BFD sessions, or VRRP sessions for the purpose of adjusting the overall health of the node in a redundant inter- chassis NAT system. A state change of the objects in the oper-group influences the health of a NAT node in a redundant configuration.
The no form of this command reverts to the default.
Default
no monitor-oper-group
Parameters
- name
-
Specifies the name of the operational group that is being monitored, up to 32 characters.
- drop
-
A state change of an object in the oper-group influences the overall health of the system in the context of NAT inter-chassis redundancy. For example, a transition into a non-operational (down) state of an object within the monitored oper-group triggers a decrease of the overall health of the node for the amount specified by the health-drop value.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
monitor-oper-group
Syntax
monitor-oper-group name health-drop drop
no monitor-oper-group name
Context
[Tree] (config>service>ies>subscriber-mgmt>up-resiliency monitor-oper-group)
[Tree] (config>service>vprn>subscriber-mgmt>up-resiliency monitor-oper-group)
Full Context
configure service ies subscriber-mgmt up-resiliency monitor-oper-group
configure service vprn subscriber-mgmt up-resiliency monitor-oper-group
Description
This command defines parameters to derive the service health based on monitored operational groups. The BNG UPF sends the health value to the BNG CPF. The BNG CPF uses the value to determine the need for a BNG UPF status change (active or standby).
The no form of the command removes the configuration.
Parameters
- name
-
Specifies the operational group name, up to 32 characters.
- drop
-
Specifies how the failure of an operational group member affects the health value. The base health value is 255; the value decreases with the defined drop per member failure to a minimum of 0.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
monitor-oper-group
Syntax
monitor-oper-group name health-drop drop
no monitor-oper-group name
Context
[Tree] (config>service>vpls>sap>pfcp>up-resiliency monitor-oper-group)
Full Context
configure service vpls sap pfcp up-resiliency monitor-oper-group
Description
This command defines parameters to derive the service health based on monitored operational groups. The BNG UPF sends the health value to the BNG CPF. The BNG CPF uses the value to determine the need for a BNG UPF status change (active or standby).
If the configured groups are not the same for all capture SAPs sharing the same underlying port or LAG, the configuration of a Layer 2 access ID alias is required, or else the system chooses arbitrarily one set of configured groups.
The no form of the command removes the configuration.
Parameters
- name
-
Specifies the operational group name, up to 32 characters.
- drop
-
Specifies how the failure of an operational group member affects the health value. The base health value is 255; the value decreases with the defined drop per member failure to a minimum of 0.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
monitor-oper-group
Syntax
monitor-oper-group group-name family {ipv4 | ipv6} add [value]
monitor-oper-group group-name family {ipv4 | ipv6} set [value]
monitor-oper-group group-name family {ipv4 | ipv6} subtract [value]
no monitor-oper-group [family {ipv4 | ipv6}]
Context
[Tree] (config>router>pim>if monitor-oper-group)
Full Context
configure router pim interface monitor-oper-group
Description
This command configures PIM to monitor the state of an operational group to provide a redundancy mechanism. PIM monitors the operational group and changes its DR priority to the specified value when the status of the operational group is up. This enables the router to become the PIM DR only when the operational group is up. If the operational group status changes to down, PIM changes its DR priority to the default or the value configured with priority under config>router>pim>if. The oper-group group-name must already be configured under the config>service context before its name is referenced in this command. Two operational groups are supported per PIM interface.
The no form of this command removes the operational group from the configuration.
Parameters
- group-name
-
Specifies the operational group identifier, up to 32 characters.
- family
-
Specifies the address family.
- ipv4
-
Specifies the IPv4 designated router priority.
- ipv6
-
Specifies the IPv6 designated router priority.
- add
-
Specifies that the value is to be added to the existing priority to become the designated router.
- subtract
-
Specifies that the value is to be subtracted from the existing priority to become the designated router.
- set
-
Specifies the priority to become the designated router.
- value
-
Specifies the priority modifier expressed as a decimal integer.
Platforms
All
monitor-oper-group
Syntax
monitor-oper-group group name
no monitor-oper-group
Context
[Tree] (config>service>sdp>binding>pw-port monitor-oper-group)
Full Context
configure service sdp binding pw-port monitor-oper-group
Description
This command specifies the operational group to be monitored by the object under which it is configured. The oper-group name must be already configured under the config>service context before its name is referenced in this command.
The no form of the command removes the association from the configuration.
Default
no monitor-oper-group
Parameters
- name
-
Specifies a character string of maximum 32 ASCII characters identifying the group instance.
Platforms
All
monitor-oper-group
Syntax
monitor-oper-group group-name
no monitor-oper-group
Context
[Tree] (config>port monitor-oper-group)
Full Context
configure port monitor-oper-group
Description
This command configures the operational group to monitor the operational group state. The state of the operational group affects the state of this port. When the operational group is inactive, the state of the port goes down and powers off the port to signal the CE that the connected port is not available.
Default
no monitor-oper-group
Parameters
- group-name
-
Specifies operational group name to monitor, up to 32 characters.
Platforms
All
monitor-port
monitor-port
Syntax
monitor-port port-id health-drop drop
no monitor-port port-id
Context
[Tree] (config>isa>nat-group>inter-chassis-redundancy monitor-port)
Full Context
configure isa nat-group inter-chassis-redundancy monitor-port
Description
This command enables monitoring of the ports to adjust the overall health of the node in a redundant inter-chassis NAT system. A state change of a monitored port influences the health of a NAT node in a redundant configuration.
The no form of this command reverts to the default.
Default
no monitor-port
Parameters
- port-id
-
Specifies the port being monitored.
- drop
-
A state change of an object in the oper-group influences the overall health of the system in the context of NAT inter-chassis redundancy. For example, a transition into a non-operational (down) state of an object within the monitored oper-group triggers a decrease of the overall health of the node for the amount specified by the health-drop value.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
monitor-ptsf-unusable
monitor-ptsf-unusable
Syntax
monitor-ptsf-unusable
Context
[Tree] (config>system>ptp>ptsf monitor-ptsf-unusable)
Full Context
configure system ptp ptsf monitor-ptsf-unusable
Description
Commands in this context configure the monitoring of neighbor clocks for the Packet Timing Signal Fail (PTSF) unusable state (condition) when the profile is set to g8275dot1-2014.
When enabled, the local clock monitors the noise level of PTP event messages exchanged between external neighbor PTP ports and the local clock. If there is too much noise and the expectation is these event message would not allow the clock to meet its output performance requirements, that neighbor port is considered unusable. This relates to declaring the PTSF-unusable state as defined in the profile.
Once a neighbor port is declared unusable, its Announce messages are excluded from the BMCA and the port cannot be selected as the parent clock.
The unusable condition can be cleared using the following command:
clear system ptp port port-id neighbor mac-address ptsf-unusable
When disabled, PTP clears the PTSF-unusable state from all neighbor PTP ports.
Deleting or disabling the local PTP port clears the PTSF-unusable state from all neighbor PTP ports that are accessed through the local PTP port.
Disabling the monitor-ptsf-unusable function of the PTP clock clears the PTSF-unusable state from all neighbor PTP ports.
In addition, if no PTP messages have been received from a neighbor for 15 minutes, the neighbor information is purged, which also clears the PTSF-unusable state.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
monitor-queue-depth
monitor-queue-depth
Syntax
monitor-queue-depth [fast-polling] [violation-threshold percentage]
no monitor-queue-depth
Context
[Tree] (config>port>ethernet>network>egress-port-queue-overrides>queue monitor-queue-depth)
[Tree] (config>service>apipe>sap>egress>queue-override>queue monitor-queue-depth)
[Tree] (config>service>epipe>sap>egress>queue-override>queue monitor-queue-depth)
[Tree] (config>service>vprn>if>sap>egress>queue-override>queue monitor-queue-depth)
[Tree] (config>service>fpipe>sap>egress>queue-override>queue monitor-queue-depth)
[Tree] (config>service>ies>if>sap>egress>queue-override>queue monitor-queue-depth)
[Tree] (config>port>ethernet>network>egr>qgrp>qover>q monitor-queue-depth)
[Tree] (config>service>ipipe>sap>egress>queue-override>queue monitor-queue-depth)
[Tree] (config>port>eth>access>egr>qgrp>qover>q monitor-queue-depth)
[Tree] (config>service>vpls>sap>egress>queue-override>queue monitor-queue-depth)
[Tree] (config>service>cpipe>sap>egress>queue-override>queue monitor-queue-depth)
Full Context
configure port ethernet network egress-port-queue-overrides queue monitor-queue-depth
configure service apipe sap egress queue-override queue monitor-queue-depth
configure service epipe sap egress queue-override queue monitor-queue-depth
configure service vprn interface sap egress queue-override queue monitor-queue-depth
configure service fpipe sap egress queue-override queue monitor-queue-depth
configure service ies interface sap egress queue-override queue monitor-queue-depth
configure port ethernet network egress queue-group queue-overrides queue monitor-queue-depth
configure service ipipe sap egress queue-override queue monitor-queue-depth
configure port ethernet access egress queue-group queue-overrides queue monitor-queue-depth
configure service vpls sap egress queue-override queue monitor-queue-depth
configure service cpipe sap egress queue-override queue monitor-queue-depth
Description
This command configures queue depth monitoring for the specified queue.
The no form of this command disables queue depth monitoring for the specified queue.
Parameters
- fast-polling
-
Keyword used to specify that fast queue polling is enabled. Fast queue polling is only supported on FP3- and FP4-based hardware.
- percentage
-
Specifies a percentage, up to two decimal places, of the queue MBS. When the depth of the queue exceeds this percentage, a violation is registered.
Platforms
All
- configure service epipe sap egress queue-override queue monitor-queue-depth
- configure port ethernet network egress-port-queue-overrides queue monitor-queue-depth
- configure port ethernet network egress queue-group queue-overrides queue monitor-queue-depth
- configure port ethernet access egress queue-group queue-overrides queue monitor-queue-depth
- configure service vpls sap egress queue-override queue monitor-queue-depth
- configure service ipipe sap egress queue-override queue monitor-queue-depth
- configure service vprn interface sap egress queue-override queue monitor-queue-depth
- configure service ies interface sap egress queue-override queue monitor-queue-depth
7450 ESS, 7750 SR-7/12/12e, 7750 SR-a, 7750 SR-e, 7950 XRS
- configure service apipe sap egress queue-override queue monitor-queue-depth
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
- configure service cpipe sap egress queue-override queue monitor-queue-depth
- configure service fpipe sap egress queue-override queue monitor-queue-depth
monitor-queue-depth
Syntax
monitor-queue-depth [fast-polling]
no monitor-queue-depth
Context
[Tree] (config>service>ipipe>sap>ingress>queue-override>queue monitor-queue-depth)
[Tree] (config>service>epipe>sap>ingress>queue-override>queue monitor-queue-depth)
[Tree] (config>service>ies>if>sap>ingress>queue-override>queue monitor-queue-depth)
[Tree] (config>service>apipe>sap>ingress>queue-override>queue monitor-queue-depth)
[Tree] (config>port>eth>access>ingress>qgrp>qover>q monitor-queue-depth)
[Tree] (config>service>vpls>sap>ingress>queue-override>queue monitor-queue-depth)
[Tree] (config>service>cpipe>sap>ingress>queue-override>queue monitor-queue-depth)
[Tree] (config>service>vprn>if>sap>ingress>queue-override>queue monitor-queue-depth)
[Tree] (config>service>fpipe>sap>ingress>queue-override>queue monitor-queue-depth)
Full Context
configure service ipipe sap ingress queue-override queue monitor-queue-depth
configure service epipe sap ingress queue-override queue monitor-queue-depth
configure service ies interface sap ingress queue-override queue monitor-queue-depth
configure service apipe sap ingress queue-override queue monitor-queue-depth
configure port ethernet access ingress queue-group queue-overrides queue monitor-queue-depth
configure service vpls sap ingress queue-override queue monitor-queue-depth
configure service cpipe sap ingress queue-override queue monitor-queue-depth
configure service vprn interface sap ingress queue-override queue monitor-queue-depth
configure service fpipe sap ingress queue-override queue monitor-queue-depth
Description
This command enters the context for queue depth monitoring for the specified queue. The fast-polling option is not supported at ingress.
The no form of this command disables queue depth monitoring.
Platforms
All
- configure service ipipe sap ingress queue-override queue monitor-queue-depth
- configure service vpls sap ingress queue-override queue monitor-queue-depth
- configure port ethernet access ingress queue-group queue-overrides queue monitor-queue-depth
- configure service vprn interface sap ingress queue-override queue monitor-queue-depth
- configure service ies interface sap ingress queue-override queue monitor-queue-depth
- configure service epipe sap ingress queue-override queue monitor-queue-depth
7450 ESS, 7750 SR-7/12/12e, 7750 SR-a, 7750 SR-e, 7950 XRS
- configure service apipe sap ingress queue-override queue monitor-queue-depth
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
- configure service cpipe sap ingress queue-override queue monitor-queue-depth
- configure service fpipe sap ingress queue-override queue monitor-queue-depth
monitor-threshold
monitor-threshold
Syntax
monitor-threshold percent
no monitor-threshold
Context
[Tree] (config>qos>port-scheduler-policy>group monitor-threshold)
[Tree] (config>qos>port-scheduler-policy monitor-threshold)
Full Context
configure qos port-scheduler-policy group monitor-threshold
configure qos port-scheduler-policy monitor-threshold
Description
This command defines the congestion monitoring threshold for the desired monitoring entity under the port-scheduler for per aggregate port-scheduler rate, per individual level, and per group that is aggregating multiple levels.
The congestion threshold is specified in percentages of the configured PIR rate for the entity for which congestion monitoring is desired. For example, if the configured PIR rate for level 1 is 100,000 kb/s, and the monitoring threshold is set to 90%, then an event where the offered rate is >90,000 kb/s will be recorded. This event is shown as part of the cumulative count of congestion threshold exceeds since the last clearing of the counters.
The no form of this command removes the congestion monitoring threshold.
Default
no monitor-threshold
Parameters
- percent
-
Specifies the percent of the configured rate. If the offered rate exceeds the configured threshold, a counter monitoring the threshold will be increased.
Platforms
All
monitor-threshold
Syntax
monitor-threshold percent
no monitor-threshold
Context
[Tree] (config>qos>hw-agg-shap-sched-plcy monitor-threshold)
Full Context
configure qos hw-agg-shaper-scheduler-policy monitor-threshold
Description
This command configures the egress scheduler monitor threshold for the hardware aggregate shaper scheduler policy. The value is expressed as a percentage of the scheduler rate, which is considered as a limit for determining congestion.
The no form of this command removes the congestion monitoring threshold.
Default
no monitor-threshold
Parameters
- percent
-
Specifies the percent of the configured rate.
Platforms
7750 SR-1, 7750 SR-s
month
month
Syntax
month {month-number [..month-number] | month-name [..month-name] | all}
no month
Context
[Tree] (config>system>cron>sched month)
Full Context
configure system cron schedule month
Description
This command specifies the month when the event should be executed. Multiple months can be specified. When multiple months are configured, each of them will cause the schedule to trigger. If a month is configured without configuring the month, weekday, day-of-month, and minute, the event will not execute.
The no form of this command removes the specified month from the configuration.
Default
no month
Parameters
- month-number
-
Specifies a month number.
- month-name
-
Specifies a month by name.
- all
-
Specifies all months.
Platforms
All
more
more
Syntax
[no] more
Context
[Tree] (environment more)
Full Context
environment more
Description
This command enables per-screen CLI output, meaning that the output is displayed on a screen-by- screen basis. The terminal screen length can be modified with the terminal command.
The following prompt appears at the end of each screen of paginated output:
Press any key to continue (Q to quit)
The no form of the command displays the output all at once. If the output length is longer than one screen, the entire output will be displayed, which may scroll the screen.
Default
more
Platforms
All
more
Syntax
[no] more
Context
[Tree] (config>system>management-interface>cli>md-cli>environment more)
Full Context
configure system management-interface cli md-cli environment more
Description
This command configures pagination of the output text.
The no form of this command reverts to the default value.
Default
more
Platforms
All
more-fragments
more-fragments
Syntax
more-fragments more-fragments
no more-fragments
Context
[Tree] (debug>oam>build-packet>packet>field-override>header>ipv4 more-fragments)
[Tree] (config>test-oam>build-packet>header>ipv4 more-fragments)
Full Context
debug oam build-packet packet field-override header ipv4 more-fragments
configure test-oam build-packet header ipv4 more-fragments
Description
This command defines if the MF flag should be set in the associated IPv4 header.
The no form of this command reverts to the default value.
Default
more-fragments 0
Parameters
- more-fragments
-
Specifies an MF flag for an IPv4 packet header to be launched by the OAM find-egress tool. A value of 1 means there are more fragments to be sent.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
motd
motd
Syntax
motd {url url-prefix: source-url | text motd-text-string}
no motd
Context
[Tree] (config>system>login-control motd)
Full Context
configure system login-control motd
Description
This command creates the message of the day displayed after a successful console login. Only one message can be configured.
The no form of this command removes the message.
Default
no motd
Parameters
- url url-prefix: source-url
-
When the message of the day is present as a text file, provide both url-prefix and the source-url of the file containing the message of the day. The URL prefix can be local or remote.
- text motd-text-string
-
Specifies the text of the message of the day. The motd-text-string must be enclosed in double quotes. Multiple text strings are not appended to one another.
Some special characters can be used to format the message text. The \n character can be used to create multi-line messages. A \n in the message moves to the beginning of the next line by sending ASCII/UTF-8 chars 0xA (LF) and 0xD (CR) to the client terminal. An \r in the message sends the ASCII/UTF-8 char 0xD (CR) to the client terminal.
Platforms
All
move
move
Syntax
move old-file-url new-file-url [force] [no-redirect] [client-tls-profile profile] [proxy proxy-url]
Context
[Tree] (file move)
Full Context
file move
Description
This command moves a local file, system file, or a directory. If the target already exists, the command fails and an error message displays.
The following prompt appears if the destination file already exists:
‟Overwrite destination file (y/n)?”
Parameters
- old-file-url
-
Specifies the file or directory to be moved.
- new-file-url
-
Specifies the new destination to place the old-file-url.
- force
-
Forces an immediate move of the specified file(s).
The file move force command moves the specified file(s) without displaying a user prompt message. This command also automatically accepts HTTP redirects unless overridden by the no-redirect parameter.
- profile
-
Specifies the TLS client profile configured under config>system>security>tls>client-tls-profile to use.
- proxy-url
-
Specifies the URL of an HTTP proxy. For example, http://proxy.mydomain.com:8000. This URL must be an HTTP URL and not an HTTPS URL.
- no-redirect
-
Specifies to automatically refuse any HTTP redirects without prompting the user.
Platforms
All
move-frequency
move-frequency
Syntax
move-frequency frequency
no move-frequency
Context
[Tree] (config>service>template>vpls-template>mac-move move-frequency)
[Tree] (config>service>vpls>mac-move move-frequency)
Full Context
configure service template vpls-template mac-move move-frequency
configure service vpls mac-move move-frequency
Description
This command indicates the maximum rate at which MACs can be re-learned in the VPLS service, before the SAP where the moving MAC was last seen is automatically disabled in order to protect the system against undetected loops or duplicate MACs.
The no form of this command reverts to the default value.
Default
move-frequency 2 (when mac-move is enabled). For example, 10 relearns in a 5 second period.
Parameters
- frequency
-
Specifies the rate, in 5-second intervals for the maximum number of relearns
Platforms
All
mp-bgp-keep
mp-bgp-keep
Syntax
[no] mp-bgp-keep
Context
[Tree] (config>router>bgp mp-bgp-keep)
Full Context
configure router bgp mp-bgp-keep
Description
As a result of enabling this command, route refresh messages are no longer needed, or issued when VPN route policy changes are made; RIB-IN will retain all MP-BGP routes.
The no form of this command is used to disable this feature.
Default
no mp-bgp-keep
Platforms
All
mp-mbb-time
mp-mbb-time
Syntax
mp-mbb-time interval
no mp-mbb-time
Context
[Tree] (config>router>ldp mp-mbb-time)
Full Context
configure router ldp mp-mbb-time
Description
This command configures the maximum time a P2MP transit/bud node must wait before switching over to the new path if the new node does not send MBB TLV to inform of the availability of data plane.
The no form of this command reverts to the default value.
Default
no mp-mbb-time (which equals a value of 3 seconds)
Parameters
- interval
-
Specifies the MP MBB time, in seconds.
Platforms
All
mpls
mpls
Syntax
mpls [bgp bgp] [endpoint endpoint-name]
no mpls [bgp bgp]
Context
[Tree] (config>service>vprn>bgp-evpn mpls)
[Tree] (config>service>epipe>bgp-evpn mpls)
[Tree] (config>service>vpls>bgp-evpn mpls)
Full Context
configure service vprn bgp-evpn mpls
configure service epipe bgp-evpn mpls
configure service vpls bgp-evpn mpls
Description
Commands in this context configure the BGP EVPN MPLS parameters. In VPLS, either instance BGP 1 or BGP 2 can be configured, but not both simultaneously in the same service. Epipe and VPRN services only support instance 1. If the bgp bgp parameter is not specified, the instance is set to 1.
The endpoint option is only supported for Epipe services. When configured, the same endpoint name can be configured for the bgp-evpn>mpls context and an additional spoke SDP. An EVPN MPLS destination always has higher preference than a spoke SDP.
The no form of this command removes the MPLS instance from the service.
Parameters
- bgp
-
Indicates the BGP instance identifier.
- endpoint-name
-
Specifies the endpoint name for Epipe services, up to 32 characters.
Platforms
All
mpls
Syntax
mpls
Context
[Tree] (config>service>vprn>bgp-ipvpn mpls)
Full Context
configure service vprn bgp-ipvpn mpls
Description
Commands in this context configure the BGP IPVPN parameters.
Platforms
All
mpls
Syntax
[no] mpls
Context
[Tree] (config>router mpls)
Full Context
configure router mpls
Description
Commands in this context configure MPLS parameters. MPLS is not enabled by default and must be explicitly enabled (no shutdown).
The no form of this command deletes this MPLS protocol instance and removes all configuration parameters for this MPLS instance.
You must remove all SDP bindings and use the shutdown command to administratively disable the MPLS instance before deleting it.
Platforms
All
mpls
Syntax
mpls
Context
[Tree] (config>router>rib-api mpls)
Full Context
configure router rib-api mpls
Description
Commands in this context configure MPLS parameters related to the RIB-API gRPC service.
Platforms
All
mpls
Syntax
mpls [lsp lsp-name] [sender source-address] [endpoint endpoint-address] [tunnel-id tunnel-id] [lsp-id lsp-id]
no mpls
Context
[Tree] (debug>router mpls)
Full Context
debug router mpls
Description
This command enables and configures debugging for MPLS.
Parameters
- lsp lsp-name
-
Specifies the LSP name up to 64 characters in length.
- sender source-address
-
Specifies the IP address of the sender.
- endpoint endpoint-address
-
Specifies the far-end IP address.
- tunnel-id tunnel-id
-
Specifies the MPLS SDP ID.
- lsp-id lsp-id
-
Specifies the LSP ID.
Platforms
All
mpls
Syntax
mpls
Context
[Tree] (debug>oam>build-packet>packet>field-override>header mpls)
[Tree] (config>test-oam>build-packet>header mpls)
Full Context
debug oam build-packet packet field-override header mpls
configure test-oam build-packet header mpls
Description
This command causes the associated header to be defined as an MPLS label header template and enables the context to define the MPLS parameters.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
mpls
Syntax
mpls
Context
[Tree] (config>oam-pm>session mpls)
Full Context
configure oam-pm session mpls
Description
Commands in this context configure MPLS-specific source and destination, LSP type and tunnel information, the priority, and the MPLS DM test configuration on the launch point.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
mpls
Syntax
[no] mpls
Context
[Tree] (config>cflowd>collector>export-filter>family mpls)
Full Context
configure cflowd collector export-filter family mpls
Description
This command filters MPLS flow data from being sent to the associated collector.
The no form of this command removes the filter, allowing MPLS flow data to be sent to the associated collector.
Default
no mpls
Platforms
All
mpls
Syntax
mpls
Context
[Tree] (config>system>ip mpls)
Full Context
configure system ip mpls
Description
Commands in this context configure system-wide MPLS parameters.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
mpls-dm
mpls-dm
Syntax
mpls-dm
Context
[Tree] (config>test-oam mpls-dm)
Full Context
configure test-oam mpls-dm
Description
Commands in this context configure global MPLS delay measurement parameters.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
mpls-echo-request-downstream-map
mpls-echo-request-downstream-map
Syntax
mpls-echo-request-downstream-map {dsmap | ddmap}
Context
[Tree] (config>test-oam mpls-echo-request-downstream-map)
Full Context
configure test-oam mpls-echo-request-downstream-map
Description
This command specifies which format of the downstream mapping TLV to use in all LSP trace packets and LDP tree trace packets originated on this node. The Downstream Mapping (DSMAP) TLV is the original format in RFC 4379 (obsoleted by RFC 8029) and is the default value. The new Downstream Detailed Mapping (DDMAP) TLV is the new enhanced format specified in RFC 6424 and RFC 8029.
This command applies to LSP trace of an RSVP P2P LSP, a MPLS-TP LSP, or LDP unicast FEC, and to LDP tree trace of a unicast LDP FEC. It does not apply to LSP trace of an RSVP P2MP LSP which always uses the DDMAP TLV.
The global DSMAP/DDMAP setting impacts the behavior of both OAM LSP trace packets and SAA test packets of type lsp-trace and is used by the sender node when one of the following events occurs:
-
An SAA test of type lsp-trace is created (not modified) and no value is specified for the per-test downstream-map-tlv {dsmap | ddmap | none} option. In this case, the SAA test downstream-map-tlv value defaults to the global mpls-echo-request-downstream-map value.
-
An OAM test of type lsp-trace test is executed and no value is specified for the per-test downstream-map-tlv {dsmap | ddmap | none} option. In this case, the OAM test downstream-map-tlv value defaults to the global mpls-echo-request-downstream-map value.
A consequence of the rules above is that a change to the value of mpls-echo-request-downstream-map option does not affect the value inserted in the downstream mapping TLV of existing tests.
Following are the details of the processing of the new DDMAP TLV:
-
When either the DSMAP TLV or the DDMAP TLV is received in an echo request message, the responder node includes the same type of TLV in the echo reply message with the proper downstream interface information and label stack information.
-
If an echo request message without a Downstream Mapping TLV (DSMAP or DDMAP) expires at a node which is not the egress for the target FEC stack, the responder node always includes the DSMAP TLV in the echo reply message. This can occur in the following cases:
-
The user issues a LSP trace from a sender node with a min-ttl value higher than 1 and a max-ttl value lower than the number of hops to reach the egress of the target FEC stack. This is the sender node behavior when the global configuration or the per-test setting of the DSMAP/DDMAP is set to DSMAP.
-
The user issues a LSP ping from a sender node with a ttl value lower than the number of hops to reach the egress of the target FEC stack. This is the sender node behavior when the global configuration of the DSMAP/DDMAP is set to DSMAP.
-
The behavior in (a) is changed when the global configuration or the per-test setting of the Downstream Mapping TLV is set to DDMAP. The sender node includes in this case the DDMAP TLV with the Downstream IP address field set to the all-routers multicast address as per Section 3.4 of RFC 8029. The responder node then bypasses the interface and label stack validation and replies with a DDMAP TLV with the correct downstream information for the target FEC stack.
-
-
A sender node never includes the DSMAP or DDMAP TLV in an lsp-ping message.
In addition to performing the same features as the DSMAP TLV, the new DDMAP TLV addresses the following scenarios:
-
Full validation of an LDP FEC stitched to a BGP IPv4 label route. In this case, the LSP trace message is inserted from the LDP LSP segment or from the stitching point.
-
Full validation of a BGP IPv4 label route stitched to an LDP FEC. This includes the case of explicit configuration of the LDP-BGP stitching in which the BGP label route is active in Route Table Manager (RTM) and the case of a BGP IPv4 label route resolved to the LDP FEC due to the IGP route of the same prefix active in RTM. In this case, the LSP trace message is inserted from the BGP LSP segment or from the stitching point.
-
Full validation of an LDP FEC which is stitched to a BGP LSP and stitched back into an LDP FEC. In this case, the LSP trace message is inserted from the LDP segments or the or from the stitching points.
-
Full validation of an LDP FEC tunneled over an RSVP LSP using LSP trace.
To properly check a target FEC which is stitched to another FEC (stitching FEC) of the same or a different type, or which is tunneled over another FEC (tunneling FEC), it is necessary for the responding nodes to provide details about the FEC manipulation back to the sender node. This is achieved via the use of the new FEC stack change sub-TLV in the Downstream Detailed Mapping TLV (DDMAP) defined in RFC 6424.
When the user configures the use of the DDMAP TLV on a trace for an LSP that does not undergo stitching or tunneling operation in the network, the procedures at the sender and responder nodes are the same as in the case of the DSMAP TLV.
This feature however introduces changes to the target FEC stack validation
procedures at the sender and responder nodes in the case of LSP stitching
and LSP hierarchy. These changes pertain to the processing of the new FEC
stack change sub-TLV in the new DDMAP TLV and the new return code of value
15 Label switched with FEC change.
The no form of this command reverts to the default behavior of using the DSMAP TLV in a LSP trace packet and LDP tree trace packet.
Default
mpls-echo-request-downstream-map dsmap
Parameters
- dsmap
-
Specifies that the DSMAP TLV should be used in all LSP trace packets and LDP tree trace packets originating on the node.
- ddmap
-
Specifies that the DDMAP TLV should be used in all LSP trace packets and LDP tree trace packets originating on the node.
Platforms
All
Output
The following output is an example of mpls-echo-request-downstream-map information.
Sample Output for LDP-over-RSVPA B D F E C
o -------- o -------- o -------- o -------- o -------- o
| \______/ | \____________________________/ | \______/ |
\ RSVP / LDP \ RSVP /
\______/ \______/
LDP LDP
Testing LDP FEC of Node C with DSMAP TLV
----------------------------------------
*A:Dut-A#
*A:Dut-A# oam lsp-trace prefix 10.20.1.3/32 downstream-map-tlv dsmap detail
lsp-trace to 10.20.1.3/32: 0 hops min, 0 hops max, 104 byte packets
1 10.20.1.2 rtt=3.90ms rc=8(DSRtrMatchLabel) rsc=1
DS 1: ipaddr=10.10.4.4 ifaddr=10.10.4.4 iftype=ipv4Numbered MRU=1500
label[1]=131068 protocol=3(LDP)
2 10.20.1.4 rtt=5.69ms rc=8(DSRtrMatchLabel) rsc=1
DS 1: ipaddr=10.10.9.6 ifaddr=10.10.9.6 iftype=ipv4Numbered MRU=1500
label[1]=131066 protocol=3(LDP)
3 10.20.1.6 rtt=7.88ms rc=8(DSRtrMatchLabel) rsc=1
DS 1: ipaddr=10.10.10.5 ifaddr=10.10.10.5 iftype=ipv4Numbered MRU=1500
label[1]=131060 protocol=3(LDP)
4 10.20.1.5 rtt=23.2ms rc=8(DSRtrMatchLabel) rsc=1
DS 1: ipaddr=10.10.5.3 ifaddr=10.10.5.3 iftype=ipv4Numbered MRU=1496
label[1]=131071 protocol=3(LDP)
5 10.20.1.3 rtt=12.0ms rc=3(EgressRtr) rsc=1
*A:Dut-A#
Testing LDP FEC of Node C with DDMAP TLV
----------------------------------------
*A:Dut-A# oam lsp-trace prefix 10.20.1.3/32 downstream-map-tlv ddmap detail
lsp-trace to 10.20.1.3/32: 0 hops min, 0 hops max, 136 byte packets
1 10.20.1.2 rtt=4.00ms rc=3(EgressRtr) rsc=2
1 10.20.1.2 rtt=3.48ms rc=8(DSRtrMatchLabel) rsc=1
DS 1: ipaddr=10.10.4.4 ifaddr=10.10.4.4 iftype=ipv4Numbered MRU=1500
label[1]=131068 protocol=3(LDP)
2 10.20.1.4 rtt=5.34ms rc=8(DSRtrMatchLabel) rsc=1
DS 1: ipaddr=10.10.9.6 ifaddr=10.10.9.6 iftype=ipv4Numbered MRU=1500
label[1]=131066 protocol=3(LDP)
3 10.20.1.6 rtt=7.78ms rc=8(DSRtrMatchLabel) rsc=1
DS 1: ipaddr=10.10.10.5 ifaddr=10.10.10.5 iftype=ipv4Numbered MRU=1500
label[1]=131060 protocol=3(LDP)
4 10.20.1.5 rtt=12.8ms rc=15(LabelSwitchedWithFecChange) rsc=1
DS 1: ipaddr=10.10.5.3 ifaddr=10.10.5.3 iftype=ipv4Numbered MRU=1496
label[1]=131054 protocol=4(RSVP-TE)
label[2]=131071 protocol=3(LDP)
fecchange[1]=PUSH fectype=RSVP IPv4 prefix=10.20.1.3 remotepeer=10.10.5.3
5 10.20.1.3 rtt=12.8ms rc=3(EgressRtr) rsc=2
5 10.20.1.3 rtt=13.4ms rc=3(EgressRtr) rsc=1
*A:Dut-A#
D F E C A B
o -------- o -------- o -------- o -------- o -------- o
\_________________/ | \_________________/ | \______/ |
LDP \ RSVP ECA / \ RSVP /
\_________________/ \______/
LDP LDP
Testing LDP FEC of Node B with DDMAP TLV
----------------------------------------
*A:Dut-D#
*A:Dut-D# oam lsp-trace prefix 10.20.1.2/32 downstream-map-tlv ddmap detail
lsp-trace to 10.20.1.2/32: 0 hops min, 0 hops max, 108 byte packets
1 10.20.1.6 rtt=3.17ms rc=8(DSRtrMatchLabel) rsc=1
DS 1: ipaddr=10.10.10.5 ifaddr=10.10.10.5 iftype=ipv4Numbered MRU=1500
label[1]=131065 protocol=3(LDP)
2 10.20.1.5 rtt=8.27ms rc=15(LabelSwitchedWithFecChange) rsc=1
DS 1: ipaddr=10.10.5.3 ifaddr=10.10.5.3 iftype=ipv4Numbered MRU=1496
label[1]=131068 protocol=4(RSVP-TE)
label[2]=131065 protocol=3(LDP)
fecchange[1]=PUSH fectype=RSVP IPv4 prefix=10.20.1.1 remotepeer=10.10.5.3
3 10.20.1.3 rtt=9.50ms rc=8(DSRtrMatchLabel) rsc=2
DS 1: ipaddr=10.10.2.1 ifaddr=10.10.2.1 iftype=ipv4Numbered MRU=1500
label[1]=131068 protocol=4(RSVP-TE)
4 10.20.1.1 rtt=10.4ms rc=3(EgressRtr) rsc=2
4 10.20.1.1 rtt=10.2ms rc=15(LabelSwitchedWithFecChange) rsc=1
DS 1: ipaddr=10.10.1.2 ifaddr=10.10.1.2 iftype=ipv4Numbered MRU=1496
label[1]=131066 protocol=4(RSVP-TE)
label[2]=131071 protocol=3(LDP)
fecchange[1]=PUSH fectype=RSVP IPv4 prefix=10.20.1.2 remotepeer=10.10.1.2
5 10.20.1.2 rtt=13.7ms rc=3(EgressRtr) rsc=2
5 10.20.1.2 rtt=13.6ms rc=3(EgressRtr) rsc=1
*A:Dut-D#
A B C D E F
o ------- o -------- o --------- o ------- o ------- o
\_____/ | \_______/ | \_____/
LDP | RSVP | LDP
|\______________________________/|
| LDP |
\______________________________/
BGP
Testing LDP FEC of Node F with DSMAP TLV
----------------------------------------
*A:Dut-A# *A:Dut-A# oam lsp-trace prefix 10.20.1.6/32 downstream-map-
tlv dsmap detail lsp-trace to 10.20.1.6/32: 0 hops min, 0 hops max, 104 byte packets
1 10.20.1.2 rtt=2.65ms rc=8(DSRtrMatchLabel) rsc=1
2 10.20.1.3 rtt=4.89ms rc=8(DSRtrMatchLabel) rsc=1
3 10.20.1.4 rtt=6.49ms rc=5(DSMappingMismatched) rsc=1
*A:Dut-A#
Testing LDP FEC of Node F with DDMAP TLV
----------------------------------------
*A:Dut-A# oam lsp-trace prefix 10.20.1.6/32 downstream-map-tlv ddmap detail lsp-
trace to 10.20.1.6/32: 0 hops min, 0 hops max, 108 byte packets
1 10.20.1.2 rtt=3.50ms rc=15(LabelSwitchedWithFecChange) rsc=1
DS 1: ipaddr=10.10.3.3 ifaddr=10.10.3.3 iftype=ipv4Numbered MRU=1496
label[1]=131068 protocol=3(LDP)
label[2]=131060 protocol=2(BGP)
fecchange[1]=POP fectype=LDP IPv4 prefix=10.20.1.6 remotepeer=0.0.0.0
(Unknown)
fecchange[2]=PUSH fectype=BGP IPv4 prefix=10.20.1.6 remotepeer=10.20.1.5
fecchange[3]=PUSH fectype=LDP IPv4 prefix=10.20.1.5 remotepeer=10.10.3.3
2 10.20.1.3 rtt=6.53ms rc=15(LabelSwitchedWithFecChange) rsc=2
DS 1: ipaddr=10.10.11.4 ifaddr=10.10.11.4 iftype=ipv4Numbered MRU=1496
label[1]=131060 protocol=4(RSVP-TE)
label[2]=131070 protocol=3(LDP)
label[3]=131060 protocol=2(BGP)
fecchange[1]=PUSH fectype=RSVP IPv4 prefix=10.20.1.4 remotepeer=10.10.11.4
3 10.20.1.4 rtt=7.94ms rc=3(EgressRtr) rsc=3
3 10.20.1.4 rtt=6.69ms rc=8(DSRtrMatchLabel) rsc=2
DS 1: ipaddr=10.10.6.5 ifaddr=10.10.6.5 iftype=ipv4Numbered MRU=1500
label[1]=131071 protocol=3(LDP)
label[2]=131060 protocol=2(BGP)
4 10.20.1.5 rtt=10.1ms rc=3(EgressRtr) rsc=2
4 10.20.1.5 rtt=8.97ms rc=15(LabelSwitchedWithFecChange) rsc=1
DS 1: ipaddr=10.10.10.6 ifaddr=10.10.10.6 iftype=ipv4Numbered MRU=1500
label[1]=131071 protocol=3(LDP)
fecchange[1]=POP fectype=BGP IPv4 prefix=10.20.1.6 remotepeer=0.0.0.0
(Unknown)
fecchange[2]=PUSH fectype=LDP IPv4 prefix=10.20.1.6 remotepeer=10.10.10.6
5 10.20.1.6 rtt=11.8ms rc=3(EgressRtr) rsc=1 *A:Dut-A#
A B C D E
o ------- o -------- o --------- o ---3--- o
\_____/ | \_______/ |
LDP | RSVP |
|\______________________________/|
| LDP |
\______________________________/
BGP
Testing BGP Label Route of Node E with DDMAP TLV
-------------------------------------------------
*A:Dut-B# oam lsp-trace prefix 11.20.1.5/32 bgp-label downstream-map-
tlv ddmap detail lsp-trace to 11.20.1.5/32: 0 hops min, 0 hops max, 124 byte packets
1 10.20.1.3 rtt=2.35ms rc=15(LabelSwitchedWithFecChange) rsc=2
DS 1: ipaddr=10.10.11.4 ifaddr=10.10.11.4 iftype=ipv4Numbered MRU=1496
label[1]=131060 protocol=4(RSVP-TE)
label[2]=131070 protocol=3(LDP)
label[3]=131070 protocol=2(BGP)
fecchange[1]=PUSH fectype=RSVP IPv4 prefix=10.20.1.4 remotepeer=10.10.11.4
2 10.20.1.4 rtt=4.17ms rc=3(EgressRtr) rsc=3
2 10.20.1.4 rtt=4.50ms rc=8(DSRtrMatchLabel) rsc=2
DS 1: ipaddr=10.10.6.5 ifaddr=10.10.6.5 iftype=ipv4Numbered MRU=1500
label[1]=131071 protocol=3(LDP)
label[2]=131070 protocol=2(BGP)
3 10.20.1.5 rtt=7.78ms rc=3(EgressRtr) rsc=2
3 10.20.1.5 rtt=6.80ms rc=3(EgressRtr) rsc=1 *A:Dut-B#
B C D E F
o -------- o --------- o ---3--- o ---3--- o
| \_______/ | \_____/
| RSVP |
|\______________________________/|
| LDP |
\______________________________/
BGP
Testing with DDMAP TLV LDP FEC of Node F when stitched to a BGP Label Route
----------------------------------------------------------------------------
*A:Dut-B# oam lsp-trace prefix 10.20.1.6/32 bgp-label downstream-map-
tlv ddmap detail lsp-trace to 10.20.1.6/32: 0 hops min, 0 hops max, 124 byte packets
1 10.20.1.3 rtt=3.21ms rc=15(LabelSwitchedWithFecChange) rsc=2
DS 1: ipaddr=10.10.11.4 ifaddr=10.10.11.4 iftype=ipv4Numbered MRU=1496
label[1]=131060 protocol=4(RSVP-TE)
label[2]=131070 protocol=3(LDP)
label[3]=131060 protocol=2(BGP)
fecchange[1]=PUSH fectype=RSVP IPv4 prefix=10.20.1.4 remotepeer=10.10.11.4
2 10.20.1.4 rtt=5.50ms rc=3(EgressRtr) rsc=3
2 10.20.1.4 rtt=5.37ms rc=8(DSRtrMatchLabel) rsc=2
DS 1: ipaddr=10.10.6.5 ifaddr=10.10.6.5 iftype=ipv4Numbered MRU=1500
label[1]=131071 protocol=3(LDP)
label[2]=131060 protocol=2(BGP)
3 10.20.1.5 rtt=7.82ms rc=3(EgressRtr) rsc=2
3 10.20.1.5 rtt=6.11ms rc=15(LabelSwitchedWithFecChange) rsc=1
DS 1: ipaddr=10.10.10.6 ifaddr=10.10.10.6 iftype=ipv4Numbered MRU=1500
label[1]=131071 protocol=3(LDP)
fecchange[1]=POP fectype=BGP IPv4 prefix=10.20.1.6 remotepeer=0.0.0.0
(Unknown)
fecchange[2]=PUSH fectype=LDP IPv4 prefix=10.20.1.6 remotepeer=10.10.10.6
4 10.20.1.6 rtt=10.2ms rc=3(EgressRtr) rsc=1 *A:Dut-B#
mpls-fwd-policy
mpls-fwd-policy
Syntax
[no] mpls-fwd-policy
Context
[Tree] (config>service>epipe>bgp-evpn>mpls>auto-bind-tunnel>resolution-filter mpls-fwd-policy)
[Tree] (config>service>vpls>bgp-evpn>mpls>auto-bind-tunnel>resolution-filter mpls-fwd-policy)
[Tree] (config>service>vprn>bgp-ipvpn>mpls>auto-bind-tunnel>resolution-filter mpls-fwd-policy)
[Tree] (config>service>vprn>bgp-evpn>mpls>auto-bind-tunnel>resolution-filter mpls-fwd-policy)
Full Context
configure service epipe bgp-evpn mpls auto-bind-tunnel resolution-filter mpls-fwd-policy
configure service vpls bgp-evpn mpls auto-bind-tunnel resolution-filter mpls-fwd-policy
configure service vprn bgp-ipvpn mpls auto-bind-tunnel resolution-filter mpls-fwd-policy
configure service vprn bgp-evpn mpls auto-bind-tunnel resolution-filter mpls-fwd-policy
Description
This command selects the MPLS forwarding policy type.
The mpls-fwd-policy value instructs BGP to use the MPLS forwarding policy to determine the address of the BGP next hop.
The no form of this command removes the selected the MPLS forwarding policy type.
Default
no mpls-fwd-policy
Platforms
All
mpls-fwd-policy
Syntax
[no] mpls-fwd-policy
Context
[Tree] (config>router>static-route-entry>indirect>tunnel-next-hop>resolution-filter mpls-fwd-policy)
Full Context
configure router static-route-entry indirect tunnel-next-hop resolution-filter mpls-fwd-policy
Description
This command enables the use of the MPLS forwarding policy to resolve the indirect next hops of statically-configured routes.
Default
no mpls-fwd-policy
Platforms
All
mpls-fwd-policy
Syntax
[no] mpls-fwd-policy
Context
[Tree] (config>router>bgp>next-hop-resolution>labeled-routes>transport-tunnel>family>resolution-filter mpls-fwd-policy)
[Tree] (config>router>bgp>next-hop-resolution>shortcut-tunn>family>resolution-filter mpls-fwd-policy)
Full Context
configure router bgp next-hop-resolution labeled-routes transport-tunnel family resolution-filter mpls-fwd-policy
configure router bgp next-hop-resolution shortcut-tunnel family resolution-filter mpls-fwd-policy
Description
This command selects MPLS forwarding policy to be used for next-hop resolution.
Platforms
All
mpls-label
mpls-label
Syntax
mpls-label value
no mpls-label
Context
[Tree] (conf>router>segment-routing>sr-policies>policy>seg-list>segment mpls-label)
Full Context
configure router segment-routing sr-policies static-policy segment-list segment mpls-label
Description
This command configures the MPLS label value this is associated with a segment.
The no form of this command removes the label value.
Default
no mpls-label
Parameters
- value
-
Specifies the MPLS label value.
Platforms
All
mpls-labels
mpls-labels
Syntax
mpls-labels
Context
[Tree] (config>router mpls-labels)
Full Context
configure router mpls-labels
Description
This command creates a context for the configuration of global parameters related to MPLS labels.
Platforms
All
mpls-time-stamp-format
mpls-time-stamp-format
Syntax
mpls-time-stamp-format {rfc4379 | unix}
Context
[Tree] (config>test-oam mpls-time-stamp-format)
Full Context
configure test-oam mpls-time-stamp-format
Description
This command configures the format of the timestamp used by for lsp-ping, lsp-trace, p2mp-lsp-ping and p2mp-lsp-trace, vccv-ping, vccv-trace, and lsp-trace.
If rfc4379 is selected, then the timestamp is in seconds and microseconds since 1900, otherwise it is in seconds and microseconds since 1970.
Changing this system-wide setting does not affect tests that are currently in progress, but SAAs starts to use the new timestamp when they are restarted. When an SR OS receives an echo request, it replies with the locally configured timestamp format, and does not try to match the timestamp format of the incoming echo request message.
Default
mpls-time-stamp-format unix
Parameters
- rfc4379
-
Specifies the RFC 4379 (obsoleted by RFC 8029) time stamp format. The timestamp's seconds field holds the integral number of seconds since 1-Jan-1900 00:00:00 UTC. The timestamp's microseconds field contains a microseconds value in the range 0 to 999999. This setting is used to inter-operate with network elements which are fully compliant with RFC 4379, Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures, (such as an SR OS system with the same setting, or any other RFC 4379 compliant router).
- unix
-
Specifies the Unix time stamp format. The time stamps seconds field holds a Unix time, the integral number of seconds since 1-Jan-1970 00:00:00 UTC. The time stamps microseconds field contains a microseconds value in the range 0 to 999999. This setting is used to inter-operate with network elements which send and expect a 1970-based timestamp in MPLS Echo Request/Reply PDUs (such as an SR OS system with the same setting, or an SR OS system running software earlier than R8.0 R4).
Platforms
All
mpls-tp
mpls-tp
Syntax
[no] mpls-tp
Context
[Tree] (config>router>mpls mpls-tp)
Full Context
configure router mpls mpls-tp
Description
Generic MPLS-TP parameters and MPLS-TP transit paths are configured under this context. If a user configures no mpls, normally the entire mpls configuration is deleted. However, in the case of mpls-tp, a check is made that there is no other mpls-tp configuration (e.g., services or LSPs using mpls-tp on the node). The mpls-tp context cannot be deleted if MPLS-TP LSPs or SDPs exist on the system.
A shutdown of mpls-tp will bring down all MPLS-TP LSPs on the system.
Default
no mpls-tp
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
mpls-tp-mep
mpls-tp-mep
Syntax
[no] mpls-tp-mep
Context
[Tree] (config>router>mpls>interface mpls-tp-mep)
Full Context
configure router mpls interface mpls-tp-mep
Description
Commands in this context configure a section layer MEP for MPLS-TP on an MPLS interface.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
mpls-tp-static
mpls-tp-static
Syntax
mpls-tp-static
Context
[Tree] (config>oam-pm>session>mpls>lsp mpls-tp-static)
Full Context
configure oam-pm session mpls lsp mpls-tp-static
Description
Commands in this context configure an MPLS TP LSP and its attributes to be tested.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
mrib
mrib
Syntax
mrib [group grp-ip-address] [source ip-address] [detail]
no mrib
Context
[Tree] (debug>router>pim mrib)
Full Context
debug router pim mrib
Description
This command enables debugging for PIM MRIB.
The no form of this command disables debugging for PIM MRIB.
Parameters
- grp-ip-address
-
Debugs information associated with the specified PIM MRIB.
- ip-address
-
Debugs information associated with the specified PIM MRIB.
- detail
-
Debugs detailed MRIB information.
Platforms
All
mrinfo
mrinfo
Syntax
mrinfo {ip-address | dns-name} [router router-instance | service-name service-name]
Context
[Tree] (mrinfo)
Full Context
mrinfo
Description
This command is used to print relevant multicast information from the target multicast router. Information displayed includes adjacency information, protocol, metrics, thresholds, and flags from the target multicast route.
Parameters
- ip-address
-
Specifies the IP address of the multicast-capable target router.
- dns-name
-
Specifies the DNS name (if DNS name resolution is configured), up to 63 characters.
- router-instance
-
Specifies the router name or service ID for the router instance.
- service-name
-
Specifies the service name, up to 64 characters.
Platforms
All
Output
The following output displays mrinfo information. The output fields are described in the following table.
Output SampleA:dut-f# mrinfo 10.1.1.2
10.1.1.2 [version 3.0,prune,genid,mtrace]:
10.1.1.2 -> 10.1.1.1 [1/0/pim]
10.1.1.3 -> 0.0.0.0 [1/0/pim/down/disabled]
10.1.1.4 -> 0.0.0.0 [1/0/pim/querier/leaf]
239.200.200.3 -> 239.200.200.5 [1/0/tunnel/pim]...
|
Label |
Description |
|---|---|
|
General flags |
|
|
version |
Indicates software version on queried router |
|
prune |
Indicates that router understands pruning |
|
genid |
Indicates that router sends generation IDs |
|
mtrace |
Indicates that the router handles mtrace requests |
|
Neighbors flags |
|
|
1 |
Metric |
|
0 |
Threshold (multicast time-to-live) |
|
pim |
PIM enabled on interface |
|
down |
Operational status of interface |
|
disabled |
Administrative status of interface |
|
leaf |
No downstream neighbors on interface |
|
querier |
Interface is IGMP querier |
|
tunnel |
Neighbor reached via tunnel |
mrouter-dest
mrouter-dest
Syntax
[no] mrouter-dest mac-name
Context
[Tree] (config>service>vpls>pbb>bvpls>mld-snooping mrouter-dest)
[Tree] (config>service>vpls>pbb>bvpls>igmp-snooping mrouter-dest)
Full Context
configure service vpls pbb backbone-vpls mld-snooping mrouter-dest
configure service vpls pbb backbone-vpls igmp-snooping mrouter-dest
Description
This command configures the destination B-MAC address name to be used in the related backbone VPLS to reach a specific IGMP or MLD snooping MRouter. The name is associated at system level with the MAC address, using the command config>service>pbb mac-name.
Parameters
- mac-name
-
Specifies the MAC name.
Platforms
All
mrouter-port
mrouter-port
Syntax
[no] mrouter-port
Context
[Tree] (config>service>vpls>spoke-sdp>mld-snooping mrouter-port)
[Tree] (config>service>vpls>mesh-sdp>igmp-snooping mrouter-port)
[Tree] (config>service>vpls>sap>igmp-snooping mrouter-port)
[Tree] (config>service>vpls>bind>mld-snooping mrouter-port)
[Tree] (config>service>vpls>spoke-sdp>igmp-snooping mrouter-port)
[Tree] (config>service>vpls>bind>igmp-snooping mrouter-port)
Full Context
configure service vpls spoke-sdp mld-snooping mrouter-port
configure service vpls mesh-sdp igmp-snooping mrouter-port
configure service vpls sap igmp-snooping mrouter-port
configure service vpls allow-ip-int-bind mld-snooping mrouter-port
configure service vpls spoke-sdp igmp-snooping mrouter-port
configure service vpls allow-ip-int-bind igmp-snooping mrouter-port
Description
This command specifies whether a multicast router is attached behind this SAP, SDP, or routed VPLS IP interface.
Configuring these objects as an mrouter-port will have a double effect. Firstly, all multicast traffic received on another SAP, SDP, or routed VPLS IP interface will be copied to this SAP, SDP, or routed VPLS IP interface. Secondly, IGMP/MLD reports generated by the system as a result of a router joining or leaving a multicast group, will be sent to this SAP, SDP, or routed VPLS IP interface.
If two multicast routers exist in the network, one of them will become the active querier. While the other multicast router (non-querier) stops sending IGMP queries, it should still receive reports to keep its multicast trees up-to-date. To support this, the mrouter-port should be enabled on all SAPs, SDPs, or routed VPLS IP interfaces connecting to a multicast router.
The IGMP version to be used for the reports (v1, v2, or v3) can only be determined after an initial query has been received. Until such time, no reports are sent on the SAP, spoke-SDP, or routed VPLS IP interface, even if mrouter-port is enabled.
If the send-queries command is enabled on this SAP or spoke-SDP, the mrouter-port parameter cannot be set.
When PIM-snooping is enabled within a VPLS service, all IP multicast traffic and PIM messages will be sent to any SAP or SDP binding configured with an IGMP-snooping mrouter port. This occurs even without IGMP-snooping enabled, but is not supported in a BGP-VPLS or M-VPLS service.
The no form of this command reverts to the default.
Default
no mrouter-port
Platforms
All
mrouter-port
Syntax
[no] mrouter-port
Context
[Tree] (config>service>vpls>vxlan>igmp-snooping mrouter-port)
Full Context
configure service vpls vxlan igmp-snooping mrouter-port
Description
This command enables all VXLAN binds to be mrouter ports, indicating that a multicast router is attached behind each VXLAN binding. Configuring these objects as an mrouter-port has two effects. Firstly, all multicast traffic received on another object is copied to each VXLAN binding. Secondly, IGMP reports generated by the system as a result of a router joining or leaving a multicast group is sent to all VXLAN bindings. When PIM snooping for IPv4 is enabled within a VPLS service, all IP multicast traffic and PIM for IPv4 messages are sent to all VXLAN bindings configured with an igmp-snooping mrouter-port. This occurs even without igmp-snooping enabled.
Default
no mrouter-port
Platforms
All
mrouter-port
Syntax
[no] mrouter-port
Context
[Tree] (config>service>vpls>vxlan>mld-snooping mrouter-port)
Full Context
configure service vpls vxlan mld-snooping mrouter-port
Description
This command enables all VXLAN binds to be mrouter ports, indicating that a multicast router is attached behind each VXLAN binding. Configuring these objects as an mrouter-port has two effects. Firstly, all multicast traffic received on another object is copied to each VXLAN binding. Secondly, MLD reports generated by the system as a result of a router joining or leaving a multicast group is sent to all VXLAN bindings.
Default
no mrouter-port
Platforms
All
mrouter-port
Syntax
[no] mrouter-port
Context
[Tree] (config>service>vpls>pbb>bvpls>sap>mld-snooping mrouter-port)
[Tree] (config>service>vpls>pbb>bvpls>sdp>mld-snooping mrouter-port)
[Tree] (config>service>vpls>pbb>bvpls>sap>igmp-snooping mrouter-port)
[Tree] (config>service>vpls>pbb>bvpls>sdp>igmp-snooping mrouter-port)
Full Context
configure service vpls pbb backbone-vpls sap mld-snooping mrouter-port
configure service vpls pbb backbone-vpls sdp mld-snooping mrouter-port
configure service vpls pbb backbone-vpls sap igmp-snooping mrouter-port
configure service vpls pbb backbone-vpls sdp igmp-snooping mrouter-port
Description
This command specifies whether a multicast router is attached behind this SAP or spoke-SDP.
Configuring a SAP or spoke-SDP as an mrouter-port will have a double effect. Firstly, all multicast traffic received on another SAP or spoke-SDP will be copied to this SAP or spoke-SDP. Secondly, IGMP or MLD reports generated by the system as a result of someone joining or leaving a multicast group, will be sent to this SAP or SDP.
If two multicast routers exist in the local area network, one of them will become the active querier. The other multicast router (non-querier) stops sending IGMP or MLD queries, but it should still receive reports to keep its multicast trees up to date. To support this, the mrouter-port should be enabled on all SAPs or spoke-SDPs connecting to a multicast router.
The IGMP version to be used for the reports (v1, v2 or v3) or MLD version (v1 or v2) can only be determined after an initial query has been received. Until such time no reports are sent on the SAP, even if mrouter-port is enabled.
If the send-queries command is enabled on this SAP or spoke-SDP, the mrouter-port parameter cannot be set.
Default
no mrouter-port
Platforms
All
mrp
mrp
Syntax
mrp
Context
[Tree] (config>service>vpls>mesh-sdp mrp)
[Tree] (config>service>vpls mrp)
[Tree] (config>service>vpls>spoke-sdp mrp)
[Tree] (config>service>vpls>sap mrp)
Full Context
configure service vpls mesh-sdp mrp
configure service vpls mrp
configure service vpls spoke-sdp mrp
configure service vpls sap mrp
Description
This command configures Multiple Registration Protocol (MRP) parameters. MRP is valid only under B-VPLS.
Platforms
All
mrp
Syntax
mrp
Context
[Tree] (config>service mrp)
Full Context
configure service mrp
Description
This command configures a Multi-service Route Processor (MRP).
Platforms
All
mrp
Syntax
[no] mrp
Context
[Tree] (debug>service>id mrp)
Full Context
debug service id mrp
Description
This command enables and configures MRP debugging.
Platforms
All
mrp-policy
mrp-policy
Syntax
mrp-policy policy-name [create]
no mrp-policy policy-name
Context
[Tree] (config>service>mrp mrp-policy)
Full Context
configure service mrp mrp-policy
Description
Commands in this context configure an MRP policy. The mrp-policy specifies either a forward or a drop action for the Group B-MAC attributes associated with the ISIDs specified in the match criteria. The mrp-policy can be applied to multiple BVPLS services as long as the scope of the policy is template.
Any changes made to the existing policy, using any of the sub-commands, will be applied immediately to all services where this policy is applied. For this reason, when many changes are required on a mrp-policy, Nokia recommends that the policy be copied to a work area. That work-in-progress policy can be modified until complete and then written over the original mrp-policy. Use the config mrp-policy copy command to maintain policies in this manner.
The no form of this command deletes the mrp-policy. An MRP policy cannot be deleted until it is removed from all the SAPs or SDPs where it is applied.
Default
no mrp-policy
Parameters
- policy-name
-
Specifies the redirect policy name. Allowed values are any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes.
- create
-
This keyword is required when first creating the configuration context. When the context is created, it is possible to navigate into the context without the create keyword.
Platforms
All
mrp-policy
Syntax
mrp-policy policy-name
no mrp-policy
Context
[Tree] (config>service>vpls>sap>mrp mrp-policy)
[Tree] (config>service>vpls>mesh-sdp>mrp mrp-policy)
[Tree] (config>service>vpls>spoke-sdp>mrp mrp-policy)
Full Context
configure service vpls sap mrp mrp-policy
configure service vpls mesh-sdp mrp mrp-policy
configure service vpls spoke-sdp mrp mrp-policy
Description
This command instructs MMRP to use the mrp-policy specified in the command to control which Group B-MAC attributes will be declared and registered on the egress SAP/Mesh-SDP/Spoke-SDP. The Group B-MACs will be derived from the ISIDs using the procedure used in the PBB solution. The Group MAC is standard OUI with the last 24 bits being the ISID value. If the policy-name refers to a non-existing mrp-policy the command should return error. Changes to a mrp-policy are allowed and applied to the SAP/SDPs under which the policy is referenced.
Default
no mrp-policy
Parameters
- policy-name
-
Specifies the redirect policy name. Allowed values are any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.
Platforms
All
mrpdu
mrpdu
Syntax
[no] mrpdu
Context
[Tree] (debug>service>id>mrp mrpdu)
Full Context
debug service id mrp mrpdu
Description
This command enables debugging of the MRP PDUs that are received or transmitted.
The no form of this command disables debugging of MRP PDUs.
Platforms
All
mrru
mrru
Syntax
mrru mrru
no mrru
Context
[Tree] (config>port>multilink-bundle mrru)
Full Context
configure port multilink-bundle mrru
Description
This command specifies the maximum received reconstructed unit (MRRU), similar to a maximum transmission unit (MTU), but applies only to MLPPP multilink bundles. The MRRU is the maximum frame size that can be reconstructed from multilink fragments. This command is only valid for MLPPP bundles.
The no form of this command resets the MRRU to the default.
Default
mrru 1524
Parameters
- mrru
-
Specifies the maximum received reconstructed unit size, in bytes.
Platforms
7450 ESS, 7750 SR-7/12/12e
mru
mru
Syntax
mru mru-bytes
no mru
Context
[Tree] (config>subscr-mgmt>pppoe-client-policy mru)
Full Context
configure subscriber-mgmt pppoe-client-policy mru
Description
This command defines which Maximum Receive Unit (MRU) value is signaled by the PPPoE client.
The no form of this command reverts to the default.
Default
mru 1492
Parameters
- mru-bytes
-
Specifies the MRU value in octets.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
mru-mismatch-detection
mru-mismatch-detection
Syntax
mru-mismatch-detection
no mru-mismatch-detection
Context
[Tree] (config>service>vprn>isis mru-mismatch-detection)
[Tree] (config>router>isis mru-mismatch-detection)
Full Context
configure service vprn isis mru-mismatch-detection
configure router isis mru-mismatch-detection
Description
This command verifies that the received IS-IS Hello (IIH) packet size does not exceed the maximum configured port MTU size. The received IIH packet is dropped when its size exceeds the maximum port MTU size.
By default, FP-based hardware does not send IS-IS packets larger than the configured port MTU size, but can accept IS-IS packets larger than the configured port MTU size.
The no form of this command allows the IS-IS router instance not to drop oversized received IIH packets.
Default
no mru-mismatch-detection
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
msap
msap
Syntax
[no] msap msap-id
Context
[Tree] (debug>service>id>ppp msap)
Full Context
debug service id ppp msap
Description
This command enable PPP debug for the specified managed SAP.
Multiple msap filters could be specified in the same debug command.
The no form of this command disables debugging.
Parameters
- msap-id
-
Specifies the managed SAP ID.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
msap-defaults
msap-defaults
Syntax
msap-default
Context
[Tree] (config>subscr-mgmt>loc-user-db>ipoe>host msap-defaults)
[Tree] (config>subscr-mgmt>loc-user-db>ppp>host msap-defaults)
[Tree] (config>service>vpls>sap msap-defaults)
Full Context
configure subscriber-mgmt local-user-db ipoe host msap-defaults
configure subscriber-mgmt local-user-db ppp host msap-defaults
configure service vpls sap msap-defaults
Description
This command configures MSAP authentication defaults.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
- configure subscriber-mgmt local-user-db ipoe host msap-defaults
- configure subscriber-mgmt local-user-db ppp host msap-defaults
All
- configure service vpls sap msap-defaults
msap-policy
msap-policy
Syntax
msap-policy msap-policy-name [create]
no msap-policy msap-policy-name
Context
[Tree] (config>subscr-mgmt msap-policy)
Full Context
configure subscriber-mgmt msap-policy
Description
This command configures a managed SAP policy. Managed SAPs allow the use of policies and a SAP template for the creation of a SAP.
The no form of this command removes the MSAP policy from the configuration.
Parameters
- msap-policy-name
-
Specifies the managed SAP policy name, up to 32 characters, composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.
- create
-
Keyword used to create the managed SAP policy. The create keyword requirement can be enabled or disabled in the environment>create context.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
msdp
msdp
Syntax
[no] msdp
Context
[Tree] (config>service>vprn msdp)
Full Context
configure service vprn msdp
Description
This command enables a Multicast Source Discovery Protocol (MSDP) instance. When an MSDP instance is created, the protocol is enabled. To start or suspend execution of the MSDP protocol without affecting the configuration, use the [no] shutdown command.
For the MSDP protocol to function, at least one peer must be configured.
When MSDP is configured and started, an appropriate event message should be generated.
When the no form of this command is executed, all sessions must be terminated and an appropriate event message should be generated.
When all peering sessions are terminated, an event message per peer is not required.
The no form of this command deletes the MSDP protocol instance, removing all associated configuration parameters.
Default
no msdp
Platforms
All
msdp
Syntax
[no] msdp
Context
[Tree] (debug>router msdp)
Full Context
debug router msdp
Description
This command enables debugging for Multicast Source Discovery Protocol (MSDP).
The no form of the command disables MSDP debugging.
Platforms
All
msdp
Syntax
[no] msdp
Context
[Tree] (config>router msdp)
Full Context
configure router msdp
Description
This command enables a Multicast Source Discovery Protocol (MSDP) instance. When an MSDP instance is created, the protocol is enabled. To start or suspend execution of the MSDP protocol without affecting the configuration, use the [no] shutdown command.
For the MSDP protocol to function, at least one peer must be configured.
When MSDP is configured and started an appropriate event message should be generated.
When the no form of the command is executed, all sessions must be terminated and an appropriate event message should be generated.
When all peering sessions are terminated, an event message per peer is not required.
The no form of the command deletes the MSDP protocol instance, removing all associated configuration parameters.
Default
no msdp
Platforms
All
msg
msg
Syntax
[no] msg
Context
[Tree] (debug>router>pim msg)
Full Context
debug router pim msg
Description
This command enables debugging for PIM messaging.
The no form of this command disables debugging for PIM messaging.
Platforms
All
msg-pacing
msg-pacing
Syntax
[no] msg-pacing
Context
[Tree] (config>router>rsvp msg-pacing)
Full Context
configure router rsvp msg-pacing
Description
This command enables RSVP message pacing in which the specified number of RSVP messages, specified in the max-burst command, are sent in a configured interval, specified in the period command. A count is kept of the messages that were dropped because the output queue for the interface used for message pacing was full.
Default
no msg-pacing
Platforms
All
msisdn
msisdn
Syntax
[no] msisdn
Context
[Tree] (config>subscr-mgmt>acct-plcy>include-radius-attribute msisdn)
[Tree] (config>subscr-mgmt>auth-plcy>include-radius-attribute msisdn)
Full Context
configure subscriber-mgmt radius-accounting-policy include-radius-attribute msisdn
configure subscriber-mgmt authentication-policy include-radius-attribute msisdn
Description
This command enables the inclusion of the MSISDN in AAA protocols as signaled in the incoming GTP setup message.
The no form of this command disables the inclusion of the attribute.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
mss-adjust-group
mss-adjust-group
Syntax
mss-adjust-group bb-group-id segment-size segment-size
no mss-adjust-group
Context
[Tree] (config>service>vprn mss-adjust-group)
[Tree] (config>router mss-adjust-group)
Full Context
configure service vprn mss-adjust-group
configure router mss-adjust-group
Description
This command associates the MSS adjust group consisting of multiple ISAs with the routing context in which the application requiring TCP MSS adjust resides.
Parameters
- bb-group-id
-
Specifies the group used for TCP MSS adjust
- segment-size
-
Specifies the value to put into the TCP Maximum Segment Size (MSS) option if it is not already present, or if the present value is higher
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
mst-instance
mst-instance
Syntax
mst-instance mst-inst-number
Context
[Tree] (config>service>vpls>sap>stp mst-instance)
Full Context
configure service vpls sap stp mst-instance
Description
Commands in this context configure MSTI related parameters at SAP level. This context can be open only for existing mst-instances defined at the service level (see config>service>vpls>stp mst-instance).
Parameters
- mst-inst-number
-
Specifies an existing Multiple Spanning Tree Instance number.
Platforms
All
mst-instance
Syntax
mst-instance mst-inst-number [create]
no mst-instance [mst-inst-number]
Context
[Tree] (config>service>vpls>stp mst-instance)
Full Context
configure service vpls stp mst-instance
Description
This command creates the context to configure MST instance (MSTI) related parameters. Up to 16 instances will be supported by MSTP. The instance 0 is mandatory by protocol and therefore, it cannot be created by the CLI. The software will maintain this instance automatically.
Parameters
- mst-inst-number
-
Specifies the Multiple Spanning Tree instance
Platforms
All
mst-max-hops
mst-max-hops
Syntax
mst-max-hops hops-count
no mst-max-hops
Context
[Tree] (config>service>vpls>stp mst-max-hops)
Full Context
configure service vpls stp mst-max-hops
Description
This command specifies the number of hops in the region before BPDU is discarded and the information held for the port is aged out. The root bridge of the instance sends a BPDU (or M-record) with remaining-hop-count set to configured <max-hops>. When a bridge receives the BPDU (or M-record), it decrements the received remaining-hop-count by 1 and propagates it in BPDU (or M-record) it generates.
The no form of this command sets the hops-count to its default value.
Default
mst-max-hops 20
Parameters
- hops-count
-
Specifies the maximum number of hops.
Platforms
All
mst-name
mst-name
Syntax
mst-name region-name
no mst-name
Context
[Tree] (config>service>vpls>stp mst-name)
Full Context
configure service vpls stp mst-name
Description
This command defines an MST region name. Two bridges are considered as a part of the same MST region as soon as their configuration of the MST region name, the MST-revision and VLAN-to-instance assignment is identical.
The no form of this command removes region-name from the configuration.
Default
no mst-name
Parameters
- region-name
-
Specifies an MST-region name up to 32 characters in length.
Platforms
All
mst-path-cost
mst-path-cost
Syntax
mst-path-cost inst-path-cost
no mst-path-cost
Context
[Tree] (config>service>vpls>sap>stp>mst-instance mst-path-cost)
Full Context
configure service vpls sap stp mst-instance mst-path-cost
Description
This commands specifies path-cost within a specified instance, expressing probability that a specified port will be put into the forwarding state in case a loop occurs (the highest value expresses lowest priority).
The no form of this command sets port-priority to its default value.
Default
The path-cost is proportional to link speed.
Parameters
- inst-path-cost
-
Specifies the contribution of this port to the MSTI path cost of paths toward the spanning tree regional root that include this port.
Platforms
All
mst-port-priority
mst-port-priority
Syntax
mst-port-priority stp-priority
no mst-port-priority
Context
[Tree] (config>service>vpls>sap>stp>mst-instance mst-port-priority)
Full Context
configure service vpls sap stp mst-instance mst-port-priority
Description
This commands specifies the port priority within a specified instance, expressing probability that a specified port will be put into the forwarding state if a loop occurs.
The no form of this command sets port-priority to its default value.
Default
mst-port-priority 128
Parameters
- stp-priority
-
Specifies the value of the port priority field.
Platforms
All
mst-priority
mst-priority
Syntax
mst-priority bridge-priority
no mst-priority
Context
[Tree] (config>service>vpls>stp>mst-instance mst-priority)
Full Context
configure service vpls stp mst-instance mst-priority
Description
This command specifies the bridge priority for this specific Multiple Spanning Tree Instance for this service. The bridge-priority value reflects likelihood that the switch will be chosen as the regional root switch (65535 represents the least likely). It is used as the highest 4 bits of the Bridge ID included in the MSTP BPDUs generated by this bridge.
The priority can only take on values that are multiples of 4096 (4k). If a value is specified that is not a multiple of 4K, then the value will be replaced by the closest multiple of 4K, which is lower than the value entered.
All instances created by the configure service vpls stp mst-instance vlan-range command and not having explicit definition of bridge-priority inherit the default value.
The no form of this command sets the bridge-priority to its default value.
Default
mst-priority 32768
Parameters
- bridge-priority
-
Specifies the priority of this specific Multiple Spanning Tree Instance for this service.
Platforms
All
mst-revision
mst-revision
Syntax
mst-revision revision-number
no mst-revision
Context
[Tree] (config>service>vpls>stp mst-revision)
Full Context
configure service vpls stp mst-revision
Description
This command defines the MST configuration revision number. Two bridges are considered as a part of the same MST region as soon as their configuration of MST-region name, MST-revision and VLAN-to-instance assignment is identical.
The no form of this command returns MST configuration revision to its default value.
Default
mst-revision 0
Parameters
- revision-number
-
Specifies the MSTP region revision number to define the MSTP region.
Platforms
All
mstat
mstat
Syntax
mstat source [ip-address | dns-name] group {ip-address | dns-name} [destination ip-address | dns-name] [hop hop] [router router-instance | service-name service-name] [wait-time wait-time]
Context
[Tree] (mstat)
Full Context
mstat
Description
This command traces a multicast path from a source to a receiver and displays multicast packet rate and loss information.
Parameters
- source ip-address
-
Specifies the ip-address of the multicast capable target router.
- dns-name
-
Specifies the DNS name (if DNS name resolution is configured), up to 63 characters.
- group ip-address
-
Specifies the multicast address or DNS name of the group that resolves to the multicast group address that will be used. If the group is not specified, address 224.2.0.1 (the MBone audio) is used. This will suffice if packet loss statistics for a particular multicast group are not needed.
- destination ip-address
-
Specifies either the IP address or the DNS name of the unicast destination. If this parameter is omitted the IP address of the system where the command is entered will be used. The receiver parameter can also be used to specify a local interface address as the destination address for sending the trace query. The response is also returned to the address specified as the receiver.
- hop
-
Specifies the maximum number of hops that will be traced from the receiver back toward the source.
- router-instance
-
Specifies the router name or service ID used to identify the router instance.
- service-name
-
Specifies the service name up to 64 characters in length.
- wait-time
-
Specifies the number of seconds to wait for the response.
Platforms
All
Output
The following output is an example of mstat information. The output fields are described in the following table.
Output Sample Source Response Dest Overall Packet Statistics for Traffic From
10.10.16.9 10.20.1.6 Mcast Pkt 10.10.16.9 to 239.5.6.7
| __/ rtt 29 ms Rate Lost/Sent = Pct Rate
v / --------- --------------------
10.10.16.3
10.10.2.3 ?
| ^ ttl 2 1pps 0/0 = -- 0 pps
v |
10.10.2.1
10.10.1.1 ?
| ^ ttl 3 1pps 0/0 = -- 0 pps
v |
10.10.1.2
10.10.4.2 ? Reached RP/Core
| ^ ttl 4 1pps 0/0 = -- 0 pps
v |
10.10.4.4
10.10.6.4 ?
| ^ ttl 5 1pps 0/0 = -- 0 pps
v |
10.10.6.5
10.10.10.5 ?
| \__ ttl 6 1pps 0/0 = -- 0 pps
v \
10.10.10.6 10.20.1.6
Receiver Query Source
|
Label |
Description |
|---|---|
|
hop |
The number of hops from the source to the listed router |
|
router name |
The number of the router for this hop or ‟?” when not reverse DNS translated |
|
address |
The address of the router for this hop |
|
protocol |
The protocol used |
|
ttl |
The forward TTL threshold. TTL that a packet is required to have before it is forwarded over the outgoing interface. |
|
forwarding code |
Forwarding information/error code for this hop |
For each interface between two nodes a line is printed, following the same layout as other routers with an implementation derived from mrouted. Consider the following:
-
The forwarding information/error code is only displayed when different from ‟No Error”.
-
‟?” means there is no reverse DNS translation.
-
There is no ‟Overall Mcast Pkt Rate” available in the PE for the VPRN case.
mstat2
mstat2
Syntax
mstat2 source [ip-address | dns-name | starg] group {ip-address | dns-name} [destination ip-address | dns-name] [hop hop] [router router-instance | service-name vprn-service-name] [wait-time seconds]
Context
[Tree] (mstat2)
Full Context
mstat2
Description
This command traces a multicast path from a source to a receiver and displays multicast packet rate and loss information.
Parameters
- source ip-address
-
Specifies the ip-address of the multicast capable target router.
- dns-name
-
Specifies the DNS name (if DNS name resolution is configured), up to 63 characters.
- starg
-
Specifies a static (*,G) entry. This command can only be enabled if no existing source addresses for this source is specified.
- group ip-address
-
Specifies the multicast address or DNS name of the group that resolves to the multicast group address that will be used. If the group is not specified, address 224.2.0.1 (the MBone audio) is used. This will suffice if packet loss statistics for a particular multicast group are not needed.
- destination ip-address
-
Specifies either the IP address or the DNS name of the unicast destination. If this parameter is omitted the IP address of the system where the command is entered will be used. The receiver parameter can also be used to specify a local interface address as the destination address for sending the trace query. The response is also returned to the address specified as the receiver.
- hop
-
Specifies the maximum number of hops that are traced from the receiver back toward the source.
- router-instance
-
Specifies the router name or service ID used to identify the router instance.
- vprn-service-name
-
Specifies the service name, up to 64 characters.
- seconds
-
Specifies the number of seconds to wait for the response.
Platforms
All
Output
|
Label |
Description |
|---|---|
|
hop |
Number of hops from the source to the listed router. |
|
router name |
Name of the router for this hop or ‟?” when not reverse DNS translated. |
|
address |
Address of the router for this hop. |
|
protocol |
Protocol used. |
|
ttl |
Forward TTL threshold. TTL that a packet is required to have before it will be forwarded over the outgoing interface. |
|
forwarding code |
Forwarding information/error code for this hop. |
For each interface between two nodes a line is printed, following the same layout as other routers with an implementation derived from mrouted. Consider the following:
-
The forwarding information/error code is only displayed when different from ‟No Error”.
-
‟?” means there is no reverse DNS translation.
-
There is no ‟Overall Mcast Pkt Rate” available in the PE for the VPRN case.
*A:Dut-A# mstat2 group 239.225.6.1 source 10.0.1.66
Mtrace2 from 150.0.1.66 via group 225.6.6.1 Querying full reverse path...
Waiting to accumulate statistics...Results after 10 seconds:
Source Response Dest Overall Packet Statistics For
Traffic From
10.0.1.66 10.0.0.1 Mcast Pkt 10.10.1.66 To 239.5.6.7
| __/ rtt 24.0ms Rate Lost/Sent = Pct Rate
v / ------- ---------------------
10.0.1.6
10.0.1.6 ?
| ^ ttl 2 10 pps 0/100 = 0% 10 pps
v |
10.0.1.4
10.10.4.4 usilhc03-hb2.ndc.lucent.com Reached RP/Core
| ^ ttl 3 10 pps 0/100 = 0% 10 pps
v |
10.10.4.2
10.0.1.2 10.1.0.110.ap.yournet.ne.jp
| \__ ttl 4 10 pps 0/100 = 0% 10 pps
v \
10.0.1.1 10.0.0.1
Receiver Query Source
*A:Dut-A# mstat2 group ff05::225:6:6:1 source 3ffe::150:0:1:66
Mtrace2 from source
<S> = 3ffe::150:0:1:66
via group
<G> = ff05::225:6:6:1
Querying full reverse path...
Waiting to accumulate statistics...Results after 10 seconds:
Destination <D> = 3ffe::120:0:1:1
Response Destination <RD> = 3ffe::1
Source Response Dest Overall Packet Statistics For
Traffic From
<S> <RD> Mcast Pkt Source <S> To Group <G>
| __/ rtt 23.0ms Rate Lost/Sent = Pct Rate
v / ------- ---------------------
Remote Address ::
Incoming IF 4
3ffe::6 ?
Outgoing IF 3
| ^ ttl 2 20 pps 0/100 = 0% 10 pps
v |
Remote Address fe80::a248:1ff:fe01:2
Incoming IF 2
3ffe::5 ? Reached RP/Core
Outgoing IF 3
| ^ ttl 3 20 pps 0/100 = 0% 10 pps
v |
Remote Address fe80::a246:1ff:fe01:1
Incoming IF 3
3ffe::3 ?
Outgoing IF 2
| \__ ttl 4 30 pps 0/100 = 0% 10 pps
v \
<D> <RD>
Receiver Query Source
mt
mt
Syntax
mt {ipv4-unicast | ipv4-multicast | ipv6-unicast | ipv6-multicast}
no mt
Context
[Tree] (config>router>bier>template>sub-domain mt)
Full Context
configure router bier template sub-domain mt
Description
This command specifies the multi-topology for this sub-domain.
The no form of this command removes the multi-topology from this sub-domain.
Parameters
- ipv4-unicast
-
Specifies that the sub-domain uses IPv4 unicast topology. IPv4 unicast imports routes into the unicast RTM.
- ipv4-multicast
-
Specifies that the sub-domain uses IPv4 multicast topology. IPv4 multicast imports routes into the multicast RTM.
- ipv6-unicast
-
Specifies that the sub-domain uses IPv6 unicast topology. IPv6 unicast imports routes into the unicast RTM.
- ipv6-multicast
-
Specifies that the sub-domain uses IPv6 multicast topology. IPv6 multicast imports routes into the multicast RTM.
Platforms
All
mtrace
mtrace
Syntax
mtrace source [ip-address | dns-name] group {ip-address | dns-name} [destination ip-address | dns-name] [hop hop] [router router-instance | service-name service-name] [wait-time wait-time]
Context
[Tree] (mtrace)
Full Context
mtrace
Description
This command traces a multicast path from a source to a receiver.
Parameters
- source ip-address
-
Specifies the ip-address of the multicast capable target router.
- dns-name
-
Specifies the DNS name (if DNS name resolution is configured). 63 characters maximum.
- group ip-address
-
Specifies the multicast address or DNS name of the group that resolves to the multicast group address that will be used. If the group is not specified, address 224.2.0.1 (the MBone audio) will be used. This will suffice if packet loss statistics for a particular multicast group are not needed.
- destination ip-address
-
Specifies either the IP address or the DNS name of the unicast destination. If this parameter is omitted the IP address of the system where the command is entered will be used. The receiver parameter can also be used to specify a local interface address as the destination address for sending the trace query. The response will also be returned to the address specified as the receiver.
- hop
-
Specifies the maximum number of hops that will be traced from the receiver back toward the source.
- router-instance
-
Specifies the router name or service ID used the identify the router instance.
- service-name
-
Specifies the service name up, to 64 characters.
- wait-time
-
Specifies the time, in seconds, to wait for the response.
Platforms
All
Output
The following output is an example of mtrace information.
Output SampleA:Dut-F# mtrace source 10.10.16.9 group 239.5.6.7
Mtrace from 10.10.16.9 via group 239.5.6.7
Querying full reverse path...
0 ? (10.10.10.6)
-1 ? (10.10.10.5) PIM thresh^ 1 No Error
-2 ? (10.10.6.4) PIM thresh^ 1 No Error
-3 ? (10.10.4.2) PIM thresh^ 1 Reached RP/Core
-4 ? (10.10.1.1) PIM thresh^ 1 No Error
-5 ? (10.10.2.3) PIM thresh^ 1 No Error
-6 ? (10.10.16.9)
Round trip time 29 ms; total ttl of 5 required.
|
Label |
Description |
|---|---|
|
hop |
The number of hops from the source to the listed router |
|
router name |
The name of the router for this hop. If a DNS name query is not successful a ‟?” displays. |
|
address |
The address of the router for this hop |
|
protocol |
The protocol used |
|
ttl |
The forward TTL threshold. TTL that a packet is required to have before it will be forwarded over the outgoing interface. |
|
forwarding code |
The forwarding information/error code for this hop |
mtrace
Syntax
[no] mtrace
Context
[Tree] (debug>router mtrace)
Full Context
debug router mtrace
Description
This command configures debugging for mtrace.
Platforms
All
mtrace2
mtrace2
mtrace2
Syntax
mtrace2 source [ip-address | dns-name | starg] group {ip-address | dns-name} [destination ip-address | dns-name] [hop hop-count] [router router-instance | service-name service-name] [wait-time wait-time]
Context
[Tree] (mtrace2)
Full Context
mtrace2
Description
This command traces a multicast path from a source to a receiver.
Parameters
- source ip-address
-
Specifies the IP address of the multicast capable target router.
- dns-name
-
Specifies the DNS name (if DNS name resolution is configured), up to 63 characters.
- starg
-
Specifies a static (*,G) entry. This command can only be enabled if no existing source addresses for this source is specified.
- group ip-address
-
Specifies the multicast address or DNS name of the group that resolves to the multicast group address that is used. If the group is not specified, address 224.2.0.1 (the MBone audio) is used. This suffices if packet loss statistics for a particular multicast group are not needed.
- destination ip-address
-
Specifies either the IP address or the DNS name of the unicast destination. If this parameter is omitted, the IP address of the system where the command is entered is used. The receiver parameter can also be used to specify a local interface address as the destination address for sending the trace query. The response is returned to the address specified as the receiver.
- hop-count
-
Specifies the maximum number of hops that are traced from the receiver back toward the source.
- router-instance
-
Specifies the router name or service ID used the identify the router instance.
- service-name
-
Specifies the service name, up to 64 characters.
- wait-time
-
Specifies the number of seconds to wait for the response.
Platforms
All
mtrace2
Syntax
[no] mtrace2
Context
[Tree] (debug>router mtrace2)
Full Context
debug router mtrace2
Description
This command configures debugging for mtrace2.
Platforms
All
mtu
mtu
Syntax
mtu mtu-bytes
no mtu
Context
[Tree] (config>service>vprn>l2tp>group>ppp mtu)
[Tree] (config>service>vprn>l2tp>group>tunnel>ppp mtu)
[Tree] (config>router>l2tp>group>ppp mtu)
[Tree] (config>router>l2tp>group>tunnel>ppp mtu)
Full Context
configure service vprn l2tp group ppp mtu
configure service vprn l2tp group tunnel ppp mtu
configure router l2tp group ppp mtu
configure router l2tp group tunnel ppp mtu
Description
This command configures the maximum PPP MTU size.
Default
mtu 1500
Parameters
- mtu-bytes
-
Specifies, in bytes, the maximum PPP MTU size.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
mtu
Syntax
mtu bytes
no mtu
Context
[Tree] (config>service>ies>sub-if>ipv6>rtr-adv mtu)
[Tree] (config>service>vprn>sub-if>grp-if>ipv6 mtu)
[Tree] (config>service>vprn>sub-if>grp-if>ipv6>rtr-adv mtu)
[Tree] (config>router>router-advert>if mtu)
[Tree] (config>service>ies>sub-if>grp-if>ipv6>rtr-adv mtu)
[Tree] (config>service>vprn>sub-if>ipv6>rtr-adv mtu)
[Tree] (config>service>vprn>router-advert>if mtu)
[Tree] (config>subscr-mgmt>rtr-adv-plcy mtu)
[Tree] (config>service>ies>sub-if>grp-if>ipv6 mtu)
Full Context
configure service ies subscriber-interface ipv6 router-advertisements mtu
configure service vprn subscriber-interface group-interface ipv6 mtu
configure service vprn subscriber-interface group-interface ipv6 router-advertisements mtu
configure router router-advertisement interface mtu
configure service ies subscriber-interface group-interface ipv6 router-advertisements mtu
configure service vprn subscriber-interface ipv6 router-advertisements mtu
configure service vprn router-advertisement interface mtu
configure subscriber-mgmt router-advertisement-policy mtu
configure service ies subscriber-interface group-interface ipv6 mtu
Description
This command specifies the value to be placed in link MTU options sent by the router on this interface.
The no form of this command reverts to the default.
Default
no mtu — The MTU option is not sent in the router advertisement messages.
Parameters
- bytes
-
Specifies the advertised MTU value in bytes for this interface.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
- configure service vprn subscriber-interface ipv6 router-advertisements mtu
- configure service vprn subscriber-interface group-interface ipv6 router-advertisements mtu
- configure service ies subscriber-interface group-interface ipv6 mtu
- configure service vprn subscriber-interface group-interface ipv6 mtu
- configure subscriber-mgmt router-advertisement-policy mtu
- configure service ies subscriber-interface ipv6 router-advertisements mtu
- configure service ies subscriber-interface group-interface ipv6 router-advertisements mtu
All
- configure service vprn router-advertisement interface mtu
- configure router router-advertisement interface mtu
mtu
Syntax
mtu mtu-bytes
no mtu
Context
[Tree] (config>subscr-mgmt>pppoe-client-policy mtu)
Full Context
configure subscriber-mgmt pppoe-client-policy mtu
Description
This command defines which Maximum Transmission Unit (MTU) is applied, by default, for packets egressing the PPP link. If a lower MRU is sent during PPP link establishment, the MRU value is used.
The no form of this command reverts to the default.
Default
mtu 1492
Parameters
- mtu-bytes
-
Specifies the MTU value in octets.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
mtu
Syntax
mtu mtu-bytes
no mtu
Context
[Tree] (config>port>tdm>ds1>channel-group mtu)
[Tree] (config>port>tdm>ds3 mtu)
[Tree] (config>port>tdm>e1>channel-group mtu)
[Tree] (config>port>ethernet mtu)
[Tree] (config>port>tdm>e3 mtu)
[Tree] (config>port>sonet-sdh>path mtu)
Full Context
configure port tdm ds1 channel-group mtu
configure port tdm ds3 mtu
configure port tdm e1 channel-group mtu
configure port ethernet mtu
configure port tdm e3 mtu
configure port sonet-sdh path mtu
Description
This command configures the maximum payload MTU size for an Ethernet port, PPP-enabled port or sub-port and Frame Relay-enabled port or subport. The Ethernet port level MTU parameter indirectly defines the largest physical packet the port can transmit or the far-end Ethernet port can receive. Packets that cannot be fragmented at egress and exceed the MTU are discarded.
The value specified for the MTU includes the destination MAC address, source MAC address, the Ethertype or Length field and the complete Ethernet payload. The MTU value does not include the preamble, start of frame delimiter or the trailing CRC.
PoS channels use the MTU to define the largest PPP payload a PoS frame may contain. A significant difference between SONET/SDH PoS channel and Ethernet physical MTU values the overhead considered part of the framing method and the overhead considered to be part of the application using the frame. In Ethernet, the preamble, start of frame delimiter and the CRC are considered part of the framing overhead and not part of the frame payload. For a PoS channel, the HDLC framing overhead is not included in the physical MTU; only the PPP and PPP payload are included. If the port mode or encapsulation type is changed, the MTU assumes the default values of the new mode or encapsulation type.
The no form of this command restores the default values.
Default
The default MTU value depends on the (sub-)port type, mode and encapsulation and are listed in Default MTU Values:
|
Type |
Mode |
Encap Type |
Default (Bytes) |
|---|---|---|---|
|
10/100, Gig, or 10GigE |
Access |
null |
1514 |
|
10/100, Gig, or 10GigE |
Access |
dot1q |
1518 |
|
10/100, Gig, or 10GigE |
Access |
q-in-q |
1522 |
|
SONET/SDH or TDM |
Access |
mpls |
1506 |
|
SONET/SDH or TDM |
Access |
bcp-null |
1518 |
|
SONET/SDH or TDM |
Access |
bcp-dot1q |
1522 |
|
SONET/SDH or TDM |
Access |
ipcp |
1502 |
|
SONET/SDH or TDM |
Access |
frame-relay |
1578 |
|
ATM, SONET/SDH or TDM |
Access |
atm |
1524 |
|
10/100 or 100FX Ethernet |
Network |
null |
1514 |
|
10/100 or 100FX Ethernet |
Network |
dot1q |
1518 |
|
SONET/SDH |
Network |
ppp-auto |
1524 |
Parameters
- mtu-bytes
-
Sets the maximum allowable size of the MTU, expressed as an integer.
Platforms
7450 ESS, 7750 SR-7/12/12e, 7750 SR-a, 7750 SR-e
- configure port tdm e1 channel-group mtu
- configure port tdm e3 mtu
- configure port tdm ds3 mtu
- configure port tdm ds1 channel-group mtu
All
- configure port ethernet mtu
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
- configure port sonet-sdh path mtu
mtu
Syntax
mtu mtu-bytes
no mtu
Context
[Tree] (config>service>vprn>ospf3>area>if mtu)
[Tree] (config>service>vprn>ospf>area>if mtu)
Full Context
configure service vprn ospf3 area interface mtu
configure service vprn ospf area interface mtu
Description
This command configures the OSPF packet size used on this interface. If this parameter is not configured, OSPF derives the MTU value from the MTU configured (default or explicitly) in the following contexts:
config>port>ethernet, config>port>sonet-sdh>path, config>port>tdm>t3-e3, config>port>tdm>t1-e1>channel-group
If this parameter is configured, the smaller value between the value configured here and the MTU configured (default or explicitly) in an above-mentioned contexts is used.
To determine the actual packet size, add 14 bytes for an Ethernet packet and 18 bytes for a tagged Ethernet packet to the size of the OSPF (IP) packet MTU configured in this command.
The no form of this command reverts to default value derived from the MTU configured in the config>port context.
Default
no mtu
Parameters
- mtu-bytes
-
Specifies the MTU to be used by OSPF for this logical interface, in bytes.
Platforms
All
mtu
Syntax
mtu value
no mtu
Context
[Tree] (config>service>vprn>nat>outside mtu)
Full Context
configure service vprn nat outside mtu
Description
This command configures the Maximum Transmission Unit (MTU) for downstream traffic flowing through this router (as outside NAT router). The system fragments IP datagrams exceeding the MTU.
The no form of the command reverts to the default.
Default
no mtu
Parameters
- value
-
Specifies the MTU for downstream traffic.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
mtu
Syntax
mtu mtu-size
no mtu
Context
[Tree] (config>router>nat>outside mtu)
Full Context
configure router nat outside mtu
Description
This command configures the MTU for downstream traffic flowing through this router (as outside NAT router). The system fragments IP datagrams exceeding the MTU.
Default
no mtu
Parameters
- mtu-size
-
Specifies the MTU for downstream traffic.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
mtu
Syntax
mtu mtu
no mtu
Context
[Tree] (config>service>ipfix>export-policy>collector mtu)
Full Context
configure service ipfix ipfix-export-policy collector mtu
Description
This command sets the MTU size of the UDP packet containing IPFIX records destined for the collector node. Multiple records will be stuffed into a single IP packet until stuffing an additional data record would exceed MTU or the internal timer of 250 ms expires.
Default
mtu 1500
Parameters
- mtu
-
Specifies the Maximum Transmission Unit range.
Platforms
All
mtu
Syntax
mtu mtu-size
Context
[Tree] (config>service>nat>syslog>syslog-export-policy mtu)
Full Context
configure service nat syslog syslog-export-policy mtu
Description
The command defines the MTU, the maximum size of the IP frame that can be transmitted. The size of the frame includes the syslog message and the IP header. This is an IP-MTU value.
When aggregation is enabled (the max-tx-delay command), generation of a syslog frame carrying multiple flow logs is triggered by one of the two events (whichever occurs first):
-
Expiry of the max-tx-delay timer
-
Exceeding MTU size
Default
mtu 1500
Parameters
- mtu-size
-
Specifies the MTU size in bytes.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
mtu
Syntax
mtu mtu-size
no mtu
Context
[Tree] (config>service>nat>map-domain mtu)
Full Context
configure service nat map-domain mtu
Description
This command configures the IPv6 MTU in a MAP domain. The configured MTU applies to traffic in the downstream direction, towards the CE. The configured MTU value must be lower than the MTU of the outgoing port for the traffic, which includes L2 overhead.
Default
mtu 8686
Parameters
- mtu-size
-
Specifies the IPMTU size of the translated IPv6 packet.
Platforms
VSR
mtu
Syntax
mtu bytes
no mtu
Context
[Tree] (config>router>ospf3>area>interface mtu)
[Tree] (config>router>ospf>area>interface mtu)
Full Context
configure router ospf3 area interface mtu
configure router ospf area interface mtu
Description
This command configures the OSPF packet size used on this interface. If this parameter is not configured OSPF derives the MTU value from the MTU configured (default or explicitly) in the following contexts:
-
config>port>ethernet
-
config>port>sonet-sdh>path
-
config>port>tdm>t3-e3
-
config>port>tdm>t1-e1>channel-group
If this parameter is configured, the smaller value between the value configured here and the MTU configured (default or explicitly) in an above-mentioned context is used.
To determine the actual packet size, add 14 bytes for an Ethernet packet and 18 bytes for a tagged Ethernet packet to the size of the OSPF (IP) packet MTU configured in this command.
The no form of this command reverts to the default derived from the MTU configured in the config>port context.
Default
no mtu
Parameters
- bytes
-
Specifies the MTU to be used by OSPF for this logical interface in bytes.
Platforms
All
mtu
Syntax
mtu mtu-size
no mtu
Context
[Tree] (config>fwd-path-ext>fpe>srv6>interface-b mtu)
Full Context
configure fwd-path-ext fpe srv6 interface-b mtu
Description
This command configures the Maximum Transfer Unit (MTU) of interface-b of the SRv6 originating FPE.
The MTU is used to check if an IPv4 service packet should be fragmented and if an IPv6 service packet should be dropped when tunneled over SRv6.
The minimum value is the IPv6 minimum MTU value. The maximum value is set to the FP4 maximum Ethernet port MTU of 9800 minus 14 bytes for Null Ethernet encapsulation.
The no form of this command reverts to the default value.
Default
mtu 9786
Parameters
- mtu-size
-
Specifies the MTU size, in bytes.
Platforms
7450 ESS, 7750 SR, 7750 SR-s, 7950 XRS, VSR
mtu
Syntax
mtu mtu-size
no mtu
Context
[Tree] (config>aaa>isa-radius-plcy>servers>ipv6 mtu)
Full Context
configure aaa isa-radius-policy servers ipv6 mtu
Description
This command configures the MTU used to fragment outgoing IPv6 RADIUS packets.
The no form of this command configures the router to use the default value.
Default
mtu 9000
Parameters
- mtu-size
-
Specifies the MTU size, in bytes.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
mtu-over-head
mtu-over-head
Syntax
mtu-over-head mtu-value
no mtu-over-head
Context
[Tree] (config>service>vprn>pim mtu-over-head)
Full Context
configure service vprn pim mtu-over-head
Description
This commands subtracts the specified value from the MVPN MTU to allow a BIER header to be added without exceeding the network MTU.
Default
no mtu-over-head
Parameters
- mtu-value
-
Specifies the value subtracted from the MVPN MTU.
Platforms
All
multi-access
multi-access
Syntax
[no] multi-access
Context
[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw>ranges>range>vrgw>lanext>access multi-access)
[Tree] (config>service>ies>sub-if>grp-if>wlan-gw>ranges>range>vrgw>lanext>access multi-access)
Full Context
configure service vprn subscriber-interface group-interface wlan-gw vlan-tag-ranges range vrgw lanext access multi-access
configure service ies subscriber-interface group-interface wlan-gw vlan-tag-ranges range vrgw lanext access multi-access
Description
This command enables access from multiple APs into a per-tenant BD and the associated vRGW (BRG) instance.
The no form of this command disables access from multiple APs and limits access from a single AP into per tenant bridge domain (BD) and the associated vRGW (BRG) instance.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
multi-active
multi-active
Syntax
[no] multi-active
Context
[Tree] (config>isa>tunnel-grp multi-active)
Full Context
configure isa tunnel-group multi-active
Description
This command enables configuring multiple active MS-ISA in the tunnel-group. IPsec traffic will be load balanced to configured active MS-ISAs.
Operational notes:
-
A shutdown of group and removal of all existing configured tunnels of the tunnel-group are needed before provisioning command ‟multi-active”.
-
If the tunnel-group is admin-up with ‟multi-active” configured then the configuration of ‟primary” and ‟backup” are not allowed.
-
The active-mda-number must be =< total number of ISA configured.
-
If active-mda-number is less than total number of ISA configured then the delta number of ISA will become backup ISA.
-
Default
no multi-active
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
multi-chassis
multi-chassis
Syntax
multi-chassis
Context
[Tree] (config>redundancy multi-chassis)
Full Context
configure redundancy multi-chassis
Description
Commands in this context configure multi-chassis parameters.
Platforms
All
multi-chassis-redundancy
multi-chassis-redundancy
Syntax
multi-chassis-redundancy seconds
no multi-chassis-redundancy
Context
[Tree] (config>python>py-pol>cache>minimum-lifetimes multi-chassis-redundancy)
Full Context
configure python python-policy cache minimum-lifetimes multi-chassis-redundancy
Description
This command specifies the minimum lifetime for a cache entry to be synchronized with the MCS peer.
The no form of this command reverts to the default.
Parameters
- seconds
-
Specifies the multi-chassis redundancy time in second.
Platforms
All
multi-chassis-shunt-id
multi-chassis-shunt-id
Syntax
multi-chassis-shunt-id id
no multi-chassis-shunt-id
Context
[Tree] (config>service>vprn>subscriber-mgmt multi-chassis-shunt-id)
[Tree] (config>service>ies>subscriber-mgmt multi-chassis-shunt-id)
Full Context
configure service vprn subscriber-mgmt multi-chassis-shunt-id
configure service ies subscriber-mgmt multi-chassis-shunt-id
Description
This command configures the shunt ID that is used to shunt downstream traffic from a standby node to an active node. Because this ID identifies the traffic service on the standby node, the same ID must be configured per service on each node.This configuration is required for BNG CUPS inter-UPF resiliency shunting, not for non-BNG CUPS shunting. However, when configured, it is also used for shunting non-BNG CUPS sessions in the same service.
The no form of the command removes the configuration.
Parameters
- id
-
Specifies the shunt ID.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
multi-chassis-shunt-interface
multi-chassis-shunt-interface
Syntax
multi-chassis-shunt-interface ip-int-name [create]
no multi-chassis-shunt-interface ip-int-name
Context
[Tree] (config>service>vprn>ipsec multi-chassis-shunt-interface)
[Tree] (config>router>ipsec multi-chassis-shunt-interface)
Full Context
configure service vprn ipsec multi-chassis-shunt-interface
configure router ipsec multi-chassis-shunt-interface
Description
Commands in this context configure a multi-chassis IPsec shunt interface.
The no form of this command removes the interface name from the configuration.
Parameters
- ip-int-name
-
Specifies the shunt interface name, up to 32 characters.
- create
-
Keyword used to create the command instance.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
multi-chassis-shunt-interface
Syntax
multi-chassis-shunt-interface ip-int-name
no multi-chassis-shunt-interface ip-int-name
Context
[Tree] (config>router>ipsec>mc-shunt-profile>peer multi-chassis-shunt-interface)
[Tree] (config>service>vprn>ipsec>mc-shunt-profile>peer multi-chassis-shunt-interface)
Full Context
configure router ipsec multi-chassis-shunting-profile peer multi-chassis-shunt-interface
configure service vprn ipsec multi-chassis-shunting-profile peer multi-chassis-shunt-interface
Description
This command associates a multi-chassis-shunt-interface for the peer. The specified interface shunts traffic to the peer.
The no form of this command removes association from the configuration.
Parameters
- ip-int-name
-
Specifies the shunt interface name, up to 32 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
multi-chassis-shunting-profile
multi-chassis-shunting-profile
Syntax
multi-chassis-shunting-profile name [create]
no multi-chassis-shunting-profile name
Context
[Tree] (config>router>ipsec multi-chassis-shunting-profile)
[Tree] (config>service>vprn>ipsec multi-chassis-shunting-profile)
Full Context
configure router ipsec multi-chassis-shunting-profile
configure service vprn ipsec multi-chassis-shunting-profile
Description
Commands in this context configure a multi-chassis IPsec shunting profile.
The no form of this command removes the name from the configuration.
Parameters
- name
-
Specifies the profile name of a MC shunting profile, up to 32 characters.
- create
-
Keyword used to create the command instance.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
multi-chassis-shunting-profile
Syntax
multi-chassis-shunting-profile name
no multi-chassis-shunting-profile
Context
[Tree] (config>service>ies>if multi-chassis-shunting-profile)
[Tree] (config>service>vprn>if multi-chassis-shunting-profile)
Full Context
configure service ies interface multi-chassis-shunting-profile
configure service vprn interface multi-chassis-shunting-profile
Description
This command associates an existing multi-chassis IPsec shunting profile with the service interface.
The no form of this command removes the name from the configuration.
Parameters
- name
-
Specifies the profile name of a multi-chassis-shunting profile, up to 32 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
multi-homed-prefix
multi-homed-prefix
Syntax
[no] multi-homed-prefix
Context
[Tree] (config>router>ospf>lfa multi-homed-prefix)
Full Context
configure router ospf loopfree-alternates multi-homed-prefix
Description
This command enables multi-homed prefix LFA for OSPF routes (IP FRR) and SR-OSPF node SID tunnels.
This feature makes use of the multi-homed prefix model described in RFC 8518 to compute a backup IP next hop using an alternate ABR or ASBR for external prefixes and to an alternate router owner for local anycast prefixes.
This feature further enhances the multi-homed prefix backup path calculation beyond RFC 8518 with the addition of repair tunnels that make use of a PQ node or a P-Q set to reach the alternate exit ABR or ASBR of external prefixes or the alternate owner router of local anycast prefixes.
The computed IP next-hop based backup path is added to OSPF routes of external /32 prefixes (OSPFv2 routes types 3, 4, 5, and 7) and local /32 anycast prefixes in the RTM if the prefix is not protected by base LFA or if the user set leaf preference value to all. The user must enable the ip-fast-reroute leaf to have these backup paths programmed into the FIB in data path.
The computed IP next hop or repair tunnel based backup path is also programmed for SR-OSPF node SID tunnels of external /32 prefixes and to /32 prefixes in same area as the computing node S and which are advertised by multiple routers (anycast prefix) in both algorithm 0 and flexible-algorithm numbers.
The no form of this command disables multi-homed prefix LFA.
Default
no multi-homed-prefix
Platforms
All
multi-homed-prefix
Syntax
[no] multi-homed-prefix
Context
[Tree] (config>router>isis>lfa multi-homed-prefix)
Full Context
configure router isis loopfree-alternates multi-homed-prefix
Description
This command enables multihomed prefix LFA for IS-IS routes (IP FRR), SR-ISIS tunnels, and SRv6-ISIS tunnels.
This feature uses the multihomed prefix model described in RFC 8518 to compute a backup IP next hop using an alternate ABR or ASBR for external prefixes and to an alternate router owner for local anycast prefixes.
This feature further enhances the multihomed prefix backup path calculation beyond RFC 8518 with the addition of repair tunnels that make use of a PQ node or a P-Q set to reach the alternate exit ABR or ASBR of external prefixes or the alternate owner router of intra-area anycast prefixes.
The computed IP next hop-based backup path is added to IS-IS routes of external /32 or /128 prefixes and intra-area /32 or /128 anycast prefixes in the RTM if the prefix is not protected by base LFA or if the user set leaf preference command option to all. The user must enable the ip-fast-reroute leaf to have these backup paths programmed into the FIB in datapath.
The computed IP next hop or repair tunnel-based backup path is also programmed for:
- SR-ISIS node SID tunnels of external /32 IPv4 prefixes and /128 IPv6 prefixes, and node SID tunnels of intra-area /32 IPv4 anycast prefixes and /128 anycast IPv6 prefixes, in both algorithm 0 and flexible-algorithms
-
SRv6-ISIS locator routes and tunnels of external prefixes and of intra-area anycast prefixes of any size, in both algorithm 0 and flexible algorithm numbers
As a result, an SR-TE LSP, an SR-MPLS policy, or an SRv6 policy which uses an SR-ISIS SID or an SRv6-ISIS SID of those same prefixes in its configured or computed SID list benefits from the multi-homed prefix LFA protection.
Once the IP next-hop based multihomed prefix LFA is enabled, the extensions to compute an SR-TE repair tunnel for the multihomed prefix LFA in the case of SR-ISIS and SRv6-ISIS are automatically enabled if the user also enabled TI-LFA or Remote LFA. The computation reuses the SID list of the primary path or of the TI-LFA or Remote LFA backup path of the alternate ABR or ASBR or alternate owner router.
The no form of this command disables multihomed prefix LFA.
Default
no multi-homed-prefix
Platforms
All
multi-homing
multi-homing
Syntax
multi-homing single-active [no-esi-label]
multi-homing all-active
no multi-homing
Context
[Tree] (config>service>system>bgp-evpn>eth-seg multi-homing)
Full Context
configure service system bgp-evpn ethernet-segment multi-homing
Description
This command configures the multi-homing mode for the Ethernet-Segment as single-active or all-active multi-homing, as defined in RFC7432.
By default, the use of esi-label is enabled for all-active and single-active as defined in RFC7432 (for single-active multi-homing, the esi-label is used to avoid transient loops).
When single-active no-esi-label is specified, the system will not allocate a label for the esi and hence advertise esi label 0 to peers. Even if the esi is configured to not send the esi-label, upon reception of an esi-label from a peer, the PE will always send traffic to that peer using the received esi-label.
Default
no multi-homing
Parameters
- single-active
-
Configures single-active mode for the Ethernet-Segment.
- all-active
-
Configures the system to not send an esi-label for single-active mode.
- no-esi-label
-
Configures single-active mode for the Ethernet-Segment.
Platforms
All
multi-instance
multi-instance
Syntax
[no] multi-instance
Context
[Tree] (config>router>ospf multi-instance)
Full Context
configure router ospf multi-instance
Description
This command enables OSPF multi-instance RFC 6549, OSPFv2 Multi-Instance Extensions, support in the BASE router. This support is enabled per instance and allows flexibility when migrating a specific instance from the classic OSPFv2 to a multi-instance OSPFv2.
The no form of this command disables OSPF multi-instance support in the BASE router.
Default
no multi-instance
Platforms
All
multi-path
multi-path
Syntax
multi-path
Context
[Tree] (config>service>vprn>bgp multi-path)
Full Context
configure service vprn bgp multi-path
Description
This command configures ECMP multipath parameters to apply to address families that support BGP multipath.
Platforms
All
multi-path
Syntax
multi-path
Context
[Tree] (config>router>bgp multi-path)
Full Context
configure router bgp multi-path
Description
This command configures ECMP multipath parameters to apply to address families that support BGP multipath.
Platforms
All
multi-path
Syntax
[no] multi-path
Context
[Tree] (config>fwd-path-ext>fpe multi-path)
Full Context
configure fwd-path-ext fpe multi-path
Description
This command enables configuration of multipath FPEs that can contain multiple port cross-connect (PXC) ports or LAGs of PXC ports.
The no form of the command disables multipath FPE.
Default
no multi-path
Platforms
All
multi-path-list
multi-path-list
Syntax
multi-path-list
Context
[Tree] (config>fwd-path-ext>fpe multi-path-list)
Full Context
configure fwd-path-ext fpe multi-path-list
Description
This command enables the context to configure a multipath FPE list instance, which can contain multiple PXC ports or LAGs of PXC ports.
Platforms
All
multi-service-site
multi-service-site
Syntax
[no] multi-service-site customer-site-name
Context
[Tree] (config>service>ies>sub-if>grp-if>sap multi-service-site)
[Tree] (config>service>vprn>sub-if>grp-if>sap multi-service-site)
[Tree] (config>service>ies>if>sap multi-service-site)
Full Context
configure service ies subscriber-interface group-interface sap multi-service-site
configure service vprn subscriber-interface group-interface sap multi-service-site
configure service ies interface sap multi-service-site
Description
This command creates a new customer site or edits an existing customer site with the customer-site-name parameter. A customer site is an anchor point to create an ingress and egress virtual scheduler hierarchy. When a site is created, it must be assigned to a chassis slot or port. When scheduler policies are defined for ingress and egress, the scheduler names contained in each policy are created according to the parameters defined in the policy. Multi-service customer sites exist for the sole purpose of creating a virtual scheduler hierarchy and making it available to queues on multiple Service Access Points (SAPs).
The scheduler policy association with the customer site normally prevents the scheduler policy from being deleted until after the scheduler policy is removed from the customer site. The multi-service-site object generates a log message indicating that the association was deleted due to scheduler policy removal.
When the multi-service customer site is created, an ingress and egress scheduler policy association does not exist. This does not prevent the site from being assigned to a chassis slot or prevent service SAP assignment. After the site has been created, the ingress and egress scheduler policy associations can be assigned or removed at any time.
The no form of this command removes the value from the configuration.
Default
n/a — Each customer site must be explicitly created.
Parameters
- customer-site-name
-
Each customer site must have a unique name within the context of the customer. If customer-site-name already exists for the customer ID, the CLI context changes to that site name for the purpose of editing the site scheduler policies or assignment. Any modifications made to an existing site affects all SAPs associated with the site. Changing a scheduler policy association may cause new schedulers to be created and existing policers and queues on the SAPs to no longer be orphaned. Existing schedulers on the site may cease to exist, causing policers and queues relying on that scheduler to be orphaned.
If the customer-site-name does not exist, it is assumed that an attempt is being made to create a site of that name in the customer ID context. The success of the command execution depends on the following:
The maximum number of customer sites defined for the chassis slot has not been met.
The customer-site-name is valid.
The create keyword is included in the command line syntax (if the system requires it).
When the maximum number of customer sites has been exceeded a configuration error occurs, the command will not execute and the CLI context will not change.
If the customer-site-name is invalid, a syntax error occurs, the command will not execute and the CLI context will not change.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
- configure service vprn subscriber-interface group-interface sap multi-service-site
- configure service ies subscriber-interface group-interface sap multi-service-site
All
- configure service ies interface sap multi-service-site
multi-service-site
Syntax
multi-service-site customer-site-name
no multi-service-site
Context
[Tree] (config>service>vpls>sap multi-service-site)
[Tree] (config>service>vprn>if>sap multi-service-site)
[Tree] (config>service>ies>sap multi-service-site)
Full Context
configure service vpls sap multi-service-site
configure service vprn interface sap multi-service-site
configure service ies sap multi-service-site
Description
This command associates the SAP with a customer-site-name. If the specified customer-site-name does not exist in the context of the service customer ID an error occurs and the command is not executed. If customer-site-name exists, the current and future defined queues on the SAP (ingress and egress) attempts to use the scheduler hierarchies created within customer-site-name as parent schedulers.
This command is mutually exclusive with the SAP ingress and egress scheduler policy commands. If a scheduler policy has been applied to either the ingress or egress nodes on the SAP, the multi-service-site command fails without executing. The locally applied scheduler policies must be removed prior to executing the multi-service-site command.
The no form of this command removes the SAP from any multi-service customer site the SAP belongs to. Removing the site can cause existing or future policers and queues to enter an orphaned state.
Parameters
- customer-site-name
-
Specifies an existing customer site name, up to 32 characters. If the customer-site-name exists and local scheduler policies have not been applied to the SAP, the current and future policers queues defined on the SAP looks for their parent schedulers within the scheduler hierarchies defined in the customer-site-name.
Platforms
All
multi-service-site
Syntax
multi-service-site customer-site-name
no multi-service-site customer-site-name
Context
[Tree] (config>service>vprn>if>sap multi-service-site)
Full Context
configure service vprn interface sap multi-service-site
Description
This command creates a new customer site or edits an existing customer site with the customer-site-name parameter. A customer site is an anchor point to create an ingress and egress virtual scheduler hierarchy. When a site is created, it must be assigned to a chassis slot or port on the 7750 SR. When scheduler policies are defined for ingress and egress, the scheduler names contained in each policy are created according to the parameters defined in the policy. Multi-service customer sites exist for the sole purpose of creating a virtual scheduler hierarchy and making it available to queues on multiple Service Access Points (SAPs).
The scheduler policy association with the customer site normally prevents the scheduler policy from being deleted until after the scheduler policy is removed from the customer site. The multi-service-site object will generate a log message indicating that the association was deleted due to scheduler policy removal.
When the multi-service customer site is created, an ingress and egress scheduler policy association does not exist. This does not prevent the site from being assigned to a chassis slot or prevent service SAP assignment. After the site has been created, the ingress and egress scheduler policy associations can be assigned or removed at any time.
Parameters
- customer-site-name
-
Each customer site must have a unique name within the context of the customer. If customer-site-name already exists for the customer ID, the CLI context changes to that site name for the purpose of editing the site scheduler policies or assignment. Any modifications made to an existing site will affect all SAPs associated with the site. Changing a scheduler policy association may cause new schedulers to be created and existing policers and queues on the SAPs to no longer be orphaned. Existing schedulers on the site may cease to exist, causing policers and queues relying on that scheduler to be orphaned.
If the customer-site-name does not exist, it is assumed that an attempt is being made to create a site of that name in the customer ID context. The success of the command execution depends on the following:
-
The maximum number of customer sites defined for the chassis slot has not been met.
-
The customer-site-name is valid.
-
The create keyword is included in the command line syntax (if the system requires it).
When the maximum number of customer sites has been exceeded a configuration error occurs; the command will not execute and the CLI context will not change.
If the customer-site-name is invalid, a syntax error occurs; the command will not execute and the CLI context will not change.
-
Platforms
All
multi-service-site
Syntax
multi-service-site customer-site-name
no multi-service-site
Context
[Tree] (config>service>ipipe>sap multi-service-site)
[Tree] (config>service>epipe>sap multi-service-site)
[Tree] (config>service>cpipe>sap multi-service-site)
[Tree] (config>service>fpipe>sap multi-service-site)
[Tree] (config>service>apipe>sap multi-service-site)
Full Context
configure service ipipe sap multi-service-site
configure service epipe sap multi-service-site
configure service cpipe sap multi-service-site
configure service fpipe sap multi-service-site
configure service apipe sap multi-service-site
Description
This command associates the SAP with a customer-site-name. If the specified customer-site-name does not exist in the context of the service customer ID an error occurs and the command will not execute. If customer-site-name exists, the current and future defined queues on the SAP (ingress and egress) will attempt to use the scheduler hierarchies created within customer-site-name as parent schedulers.
The no form of this command removes the SAP from any multi-service customer site the SAP belongs to. Removing the site can cause existing or future queues to enter an orphaned state.
Parameters
- customer-site-name
-
The customer-site-name must exist in the context of the customer-id defined as the service owner. If customer-site-name exists and local scheduler policies have not been applied to the SAP, the current and future queues defined on the SAP will look for their parent schedulers within the scheduler hierarchies defined on customer-site-name.
Platforms
All
- configure service epipe sap multi-service-site
- configure service ipipe sap multi-service-site
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
- configure service cpipe sap multi-service-site
- configure service fpipe sap multi-service-site
7450 ESS, 7750 SR-7/12/12e, 7750 SR-a, 7750 SR-e, 7950 XRS
- configure service apipe sap multi-service-site
multi-service-site
Syntax
multi-service-site customer-site-name [create]
no multi-service-site customer-site-name
Context
[Tree] (config>service>cust multi-service-site)
Full Context
configure service customer multi-service-site
Description
This command creates a new customer site or edits an existing customer site with the customer-site-name parameter. A customer site is an anchor point to create an ingress and egress virtual scheduler hierarchy. When a site is created, it must be assigned to a chassis slot or port. When scheduler policies are defined for ingress and egress, the scheduler names contained in each policy are created according to the parameters defined in the policy. Multi-service customer sites exist for the sole purpose of creating a virtual scheduler hierarchy and making it available to queues on multiple Service Access Points (SAPs).
The scheduler policy association with the customer site normally prevents the scheduler policy from being deleted until after the scheduler policy is removed from the customer site. The multi-service-site object will generate a log message indicating that the association was deleted due to scheduler policy removal.
When the multi-service customer site is created, an ingress and egress scheduler policy association does not exist. This does not prevent the site from being assigned to a chassis slot or prevent service SAP assignment. After the site has been created, the ingress and egress scheduler policy associations can be assigned or removed at any time.
Parameters
- customer-site-name
-
Specifies the customer site name. Each customer site must have a unique name within the context of the customer. If customer-site-name already exists for the customer ID, the CLI context changes to that site name for the purpose of editing the site scheduler policies or assignment. Any modifications made to an existing site will affect all SAPs associated with the site. Changing a scheduler policy association may cause new schedulers to be created and existing policers and queues on the SAPs to no longer be orphaned. Existing schedulers on the site may cease to exist, causing policers and queues relying on that scheduler to be orphaned.
If the customer-site-name does not exist, it is assumed that an attempt is being made to create a site of that name in the customer ID context. The success of the command execution depends on the following:
-
The maximum number of customer sites defined for the chassis has not been met.
-
The customer-site-name is valid.
-
The create keyword is included in the command line syntax (if the system requires).
When the maximum number of customer sites has been exceeded a configuration error occurs; the command will not execute and the CLI context will not change.
If the customer-site-name is invalid, a syntax error occurs; the command will not execute and the CLI context will not change.
-
Platforms
All
multi-session-id
multi-session-id
Syntax
[no] multi-session-id
Context
[Tree] (config>aaa>isa-radius-plcy>acct-include-attributes multi-session-id)
Full Context
configure aaa isa-radius-policy acct-include-attributes multi-session-id
Description
This command enables the inclusion of the multi-session-id attributes.
The no form of the command excludes the multi-session-id attributes.
Default
no multi-session-id
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
multi-sub-sap
multi-sub-sap
Syntax
multi-sub-sap [subscriber limit]
no multi-sub-sap
Context
[Tree] (config>subscr-mgmt>msap-policy>sub-sla-mgmt multi-sub-sap)
Full Context
configure subscriber-mgmt msap-policy sub-sla-mgmt multi-sub-sap
Description
This command defines the maximum number of subscribers (dynamic + static) that can be simultaneously active on an MSAP.
If the limit is reached, a new host is denied access and the corresponding DHCP ACK is dropped.
The no form of this command reverts back to the default setting.
Default
multi-sub-sap 1
Parameters
- limit
-
Specifies the maximum number of subscribers allowed.
Note:The operational maximum value may be smaller due to equipped hardware dependencies.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
multi-sub-sap
Syntax
multi-sub-sap subscriber-limit
no multi-sub-sap
Context
[Tree] (config>service>vpls>sap>sub-sla-mgmt multi-sub-sap)
[Tree] (config>service>vprn>sub-if>grp-if>sap>sub-sla-mgmt multi-sub-sap)
[Tree] (config>service>ies>sub-if>grp-if>sap>sub-sla-mgmt multi-sub-sap)
Full Context
configure service vpls sap sub-sla-mgmt multi-sub-sap
configure service vprn subscriber-interface group-interface sap sub-sla-mgmt multi-sub-sap
configure service ies subscriber-interface group-interface sap sub-sla-mgmt multi-sub-sap
Description
This command defines the maximum number of subscribers (dynamic and static) that can be simultaneously active on this SAP.
If the limit is reached, a new host is denied access and the corresponding DHCP ACK is dropped.
The no form of this command reverts back to the default setting.
Parameters
- subscriber-limit
-
Specifies the maximum number of subscribers allowed for this SAP. The operational maximum value may be smaller than the configured value due to equipped hardware dependencies.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
multi-topology
multi-topology
Syntax
[no] multi-topology
Context
[Tree] (config>service>vprn>isis multi-topology)
Full Context
configure service vprn isis multi-topology
Description
This command enables IS-IS multi-topology support.
The no form of this command disables IS-IS multi-topology.
Default
no multi-topology
Platforms
All
multi-topology
Syntax
[no] multi-topology
Context
[Tree] (config>router>isis multi-topology)
Full Context
configure router isis multi-topology
Description
This command enables IS-IS multi-topology support.
Default
no multi-topology
Platforms
All
multi-topology
Syntax
multi-topology [mt0] [mt2]
no multi-topology
Context
[Tree] (config>router>isis>srv6>locator multi-topology)
Full Context
configure router isis segment-routing-v6 locator multi-topology
Description
This command configures the use of a local SRv6 locator in an IS-IS IPv6 topology. A user can enable one or more locators in an IS-IS instance. Each locator can be enabled in a single topology of an IS-IS instance, topology 0 (MT0) or topology 2 (MT2). A local locator can be used in multiple IS-IS instances, but can only be assigned to at most one IPv6 topology independently within each IS-IS instance.
To enable the processing of local and remote IPv6 prefixes and SRv6 locators in MT0 and MT2, use the configure router isis segment-routing-v6 no shutdown command. In addition, to enable SRv6 forwarding in the MT0, MT2, or both topologies, use the configure router isis ipv6-routing native, configure router isis multi-topology ipv6-unicast, or both commands.
By default, a locator name added to an IS-IS instance is enabled in MT0.
The no form of this command returns to the default operation of the locator.
Default
multi-topology mt0
Parameters
- mt0
-
Specifies to use the standard topology (topology 0) in an IS-IS instance.
- mt2
-
Specifies to use the IPv6 routing topology (topology 2) in an IS-IS instance.
Platforms
7450 ESS, 7750 SR, 7750 SR-s, 7950 XRS, VSR
multi-topology
Syntax
multi-topology [mt0] [mt2]
no multi-topology
Context
[Tree] (config>router>isis>srv6>msloc multi-topology)
Full Context
configure router isis segment-routing-v6 micro-segment-locator multi-topology
Description
This command configures the use of a local SRv6 micro-segment locator in an IS-IS IPv6 topology. A user can enable one or more micro-segment locators in an IS-IS instance. Each micro-segment locator can be enabled in a single topology of an IS-IS instance, topology 0 (MT0) or topology 2 (MT2). A local micro-segment locator can be used in multiple IS-IS instances, but can only be assigned to at most one IPv6 topology independently within each IS-IS instance.
To enable the processing of local and remote IPv6 prefixes and SRv6 locators in MT0 and MT2, use the configure router isis segment-routing-v6 no shutdown command. In addition, to enable SRv6 forwarding in the MT0, MT2, or both topologies, use the configure router isis ipv6-routing native, configure router isis multi-topology ipv6-unicast, or both commands.
By default, a micro-segment locator name added to an IS-IS instance is enabled in MT0.
The no form of this command returns to the default operation of the micro-segment locator.
Default
multi-topology mt0
Parameters
- mt0
-
Specifies to use the standard topology (topology 0) in an IS-IS instance.
- mt2
-
Specifies to use the IPv6 routing topology (topology 2) in an IS-IS instance.
Platforms
7450 ESS, 7750 SR, 7750 SR-s, 7950 XRS, VSR
multi-tunnel-type
multi-tunnel-type
Syntax
[no] multi-tunnel-type
Context
[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw>mobility multi-tunnel-type)
[Tree] (config>service>ies>sub-if>grp-if>wlan-gw>mobility multi-tunnel-type)
Full Context
configure service vprn subscriber-interface group-interface wlan-gw mobility multi-tunnel-type
configure service ies subscriber-interface group-interface wlan-gw mobility multi-tunnel-type
Description
This command enables terminating multiple types of tunnels.
The no form of this command disables terminating multiple types of tunnels.
Default
no multi-tunnel-type
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
multicast
multicast
Syntax
multicast
Context
[Tree] (config>service>vprn>sub-if>grp-if>bonding-parameters multicast)
[Tree] (config>service>ies>sub-if>grp-if>bonding-parameters multicast)
Full Context
configure service vprn subscriber-interface group-interface bonding-parameters multicast
configure service ies subscriber-interface group-interface bonding-parameters multicast
Description
Commands in this context configure multicast in a bonding environment.
multicast
Syntax
multicast [key-id key-id] [version version]
no multicast
Context
[Tree] (config>system>time>ntp multicast)
Full Context
configure system time ntp multicast
Description
This command configures NTP the node to transmit multicast packets on the CPM/CCM MGMT port. Broadcast and multicast messages can easily be spoofed; authentication is strongly recommended.
The no form of this command removes the multicast address from the configuration.
Parameters
- key-id
-
Specifies the configured authentication key and authentication type used by this version to transmit NTP packets. If this command is omitted from the configuration, packets are sent unencrypted.
- version
-
Specifies the NTP version number that is generated by this node. This parameter does not need to be configured when in client mode in which case all three versions are accepted.
Platforms
All
multicast-fast-failover
multicast-fast-failover
Syntax
[no] multicast-fast-failover
Context
[Tree] (config>router>pim multicast-fast-failover)
Full Context
configure router pim multicast-fast-failover
Description
This command configures the option to enable Multicast-Only Fast Reroute (MoFRR) functionality for IPv4 PIM-SSM interfaces in the global routing table instance.
The no form of this command disables MoFRR for IPv4 PIM-SSM interfaces.
Default
no multicast-fast-failover
Platforms
All
multicast-import
multicast-import
Syntax
[no] multicast-import
Context
[Tree] (config>service>vprn>isis multicast-import)
Full Context
configure service vprn isis multicast-import
Description
This command enables ISIS to submit routes into the multicast Route Table Manager (RTM).
The no form of this command disables the submission of routes into the multicast RTM.
Default
no multicast-import
Platforms
All
multicast-import
Syntax
[no] multicast-import
Context
[Tree] (config>service>vprn>ospf multicast-import)
[Tree] (config>service>vprn>ospf3 multicast-import)
Full Context
configure service vprn ospf multicast-import
configure service vprn ospf3 multicast-import
Description
This command enables the submission of routes into the multicast Route Table Manager (RTM) by OSPF.
The no form of this command disables the submission of routes into the multicast RTM.
Default
no multicast-import
Platforms
All
multicast-import
Syntax
[no] multicast-import [{both | ipv4 | ipv6}]
Context
[Tree] (config>router>isis multicast-import)
Full Context
configure router isis multicast-import
Description
This command enables the submission of routes into the multicast Route Table Manager (RTM) by IS-IS.
The no form of this command disables the submission of routes into the multicast RTM.
Default
no multicast-import
Parameters
- both
-
Allows submission of both IPv4 and IPv6 routes.
- ipv4
-
Allows submission of IPv4 routes only.
- ipv6
-
Allows submission of IPv6 routes only.
Platforms
All
multicast-import
Syntax
[no] multicast-import
Context
[Tree] (config>router>ospf3 multicast-import)
[Tree] (config>router>ospf multicast-import)
Full Context
configure router ospf3 multicast-import
configure router ospf multicast-import
Description
This command enables the submission of routes into the multicast Route Table Manager (RTM) by OSPF.
The no form of this command disables the submission of routes into the multicast RTM.
Default
no multicast-import
Platforms
All
multicast-info-policy
multicast-info-policy
Syntax
multicast-info-policy policy-name [create]
no multicast-info-policy
Context
[Tree] (config>mcast-management multicast-info-policy)
Full Context
configure mcast-management multicast-info-policy
Description
This command configures a multicast information policy. Multicast information policies are used to manage parameters associated with Layer 2 and Layer 3 multicast records. Multiple features use the configured information within the policy. The multicast ingress path manager uses the policy to decide the inactive and active state behavior for each multicast record using the ingress paths to the switch fabric. The system’s multicast ECMP join decisions are influenced by the channel information contained within the policy.
Multicast Bundles:
A multicast information policy consists of one or multiple named bundles. Multicast streams are mapped to a bundle based on matching the destination address of the multicast stream to configured channel ranges defined within the bundles. Each policy has a bundle named ‛default’ that is used when a destination address does not fall within any of the configured channel ranges.
Each bundle has a set of default parameters used as the starting point for multicast channels matching the bundle. The default parameters may be overridden by optional exception parameters defined under each channel range. Further optional parameter overrides are possible under explicit source address contexts within each channel range.
Default Multicast Information Policy
A multicast information policy always exists with the name ‛default’ and cannot be edited or deleted. The following parameters are contained in the default multicast information policy:
|
Policy Description: |
Default policy, cannot be edited or deleted. |
|
Bundle: |
default |
|
Bundle Description: |
Default Bundle, cannot be edited or deleted. |
|
Congestion-Priority-Threshold: |
4 |
|
ECMP-Optimization-Limit-Threshold: |
7 |
|
Bundle Defaults: |
|
|
Administrative Bandwidth: |
0 (undefined) |
|
Preference: |
0 |
|
CAC-Type: |
Optional |
|
Bandwidth Activity: |
Dynamic with no black-hole rate |
|
Explicit Ingress SF Path: |
None (undefined) |
|
Configured Channel Ranges: |
None |
The default multicast information policy is applied to all VPLS and VPRN services and all routing contexts until an explicitly defined multicast information policy has been mapped.
Explicit Multicast Information Policy Associations
Each VPLS service and each routing context (including VPRN routing contexts) supports an explicit association with an pre-existing multicast information policy. The policy may need to be unique per service or routing context since that each context has its own multicast address space. The same multicast channels may be and most likely be used for completely different multicast streams and applications in each forwarding context.
Interaction with Ingress Multicast Path Management
When ingress multicast path management is enabled on an MDA, the system automatically creates a bandwidth manager context that manages the multicast path bandwidth into the switch fabric used by the ingress ports on the MDA. As routing or snooping protocols generate Layer 2 or Layer 3 multicast FIB records that are populated on the MDA’s forwarding plane, they are processed though the multicast information policy that is associated with the service or routing context associated with the record. The policy returns the following information for the record to be used by the ingress bandwidth manager:
-
The records administrative bandwidth (0 if undefined)
-
Preference level (0 to 7 with 7 being highest)
-
Bandwidth activity monitoring setting (use admin bw or dynamic monitoring) If admin bw is indicated, also returns active and inactive thresholds
-
Initial switch fabric multicast path (primary or secondary)
-
Explicit switch fabric multicast path (primary, secondary, or none)
Interaction with Multicast ECMP Optimization
The multicast information policy is used by the multicast ECMP optimization function to derive each channels administrative bandwidth. The ECMP function tallies all bandwidth information for channels joined and attempts to equalize the load between the various paths to the sender. The multicast information policy returns the following information to the ECMP path manager:
-
Administrative bandwidth (0 if undefined)
-
Preference (0 to 7 with 7 the highest preference value)
Default
multicast-info-policy ‟default”
Parameters
- policy-name
-
Identifies the name of the policy to be either created or edited. Each multicast information policy must be uniquely named within the system. Names of up to 32 ASCII characters are supported with the normal character restrictions.
- create
-
The create keyword is required if creating a new multicast information policy when the system is configured to require the explicit use of the keyword to prevent accidental object creation. Objects may be accidentally created when this protection is disabled and an object name is mistyped when attempting to edit the object. This keyword is not required when the protection is disabled. The keyword is ignored when the multicast information policy name already exists.
Platforms
All
multicast-info-policy
Syntax
multicast-info-policy policy-name
no multicast-info-policy
Context
[Tree] (config>service>ies multicast-info-policy)
[Tree] (config>router multicast-info-policy)
[Tree] (config>service>vprn multicast-info-policy)
[Tree] (config>service>vpls multicast-info-policy)
Full Context
configure service ies multicast-info-policy
configure router multicast-info-policy
configure service vprn multicast-info-policy
configure service vpls multicast-info-policy
Description
This command overrides the default multicast information policy on a service or routing context. When the policy association is changed, all multicast channels in the service or routing context must be reevaluated.
If a multicast information policy is not explicitly associated with the service or routing context, the default multicast information policy is used when ingress multicast path management is enabled.
While a multicast information policy is associated with a service or routing context, the policy cannot be deleted from the system.
The no form of the command removes an explicit multicast information policy from the service or routing context and restores the default multicast information policy.
Parameters
- policy-name
-
Specifies the policy name, up to 32 characters. The policy-name parameter is required and specifies an existing multicast information policy that should be associated with the service or routing context.
Platforms
All
multicast-leave-sync-propagation
multicast-leave-sync-propagation
Syntax
multicast-leave-sync-propagation time
Context
[Tree] (config>service>system>bgp-evpn multicast-leave-sync-propagation)
Full Context
configure service system bgp-evpn multicast-leave-sync-propagation
Description
This command configures the additional amount of time that the system waits before removing a multicast state that was synchronized in an Ethernet Segment via Multicast Join or Leave Synch routes. This value represents a delta corresponding to the time it takes for a BGP advertisement to propagate to ES peers.
The node triggering the route computes the maximum response time as the product of the locally configured values, Last Member Query Count and Last Member Query Interval (this value is taken from the config>service>vpls>sap>igmp-snooping>last-member-query-interval or config>service>vpls>spoke-sdp>igmp-snooping> last-member-query-interval commands depending on the Ethernet Segment being used), and adds the delta value to the Maximum Response Time. Increasing the Maximum Response Time by this value can help minimize the churn of removing and recreating the state on the node.
The maximum response time value should be configured consistently in all ES peers. For example, in a scenario where a maximum response time of five seconds is advertised by PE-A and there is a delay of four seconds in the BGP propagation to PE-B, the timer could already expire on PE-A while PE-B is still in LMQ time and can still receive joins (which would recreate state in A after a join synch route from B). To minimize this situation, adding an extra delta timer on PE-A, reduces the potential churn of PE-A removing and recreating the state.
Default
multicast-leave-sync-propagation 5
Parameters
- time
-
Specifies the multicast leave sync propagation delay time, in seconds.
Platforms
All
multicast-lsp
multicast-lsp
Syntax
multicast-lsp lsp-name
no multicast-lsp
Context
[Tree] (config>service>sdp>class-forwarding multicast-lsp)
Full Context
configure service sdp class-forwarding multicast-lsp
Description
This command specifies the RSVP or static LSP in this SDP to use to forward VPLS multicast and broadcast packets. The LSP name must exist and must have been associated with this SDP using the command config>service>sdp>lsp. In the absence of an explicit configuration by the user, the default LSP is used.
Default
no multicast-lsp — traffic mapped to default-lsp name
Parameters
- lsp-name
-
Specifies the RSVP or static LSP to use.
Platforms
All
multicast-network-domain
multicast-network-domain
Syntax
multicast-network-domain multicast-network-domain
no multicast-network-domain
Context
[Tree] (config>service>ies>if multicast-network-domain)
Full Context
configure service ies interface multicast-network-domain
Description
This command is used to enable efficient multicast replication over a spoke SDP. Multicast traffic is copied to only a subset of network interfaces that may be used as egress for a spoke SDP. A network domain is defined by associating multiple interfaces to a logical group that may participate in multicast replication for a spoke SDP.
The no form of command disables efficient multicast replication to a network domain for a spoke SDP and traffic is replicated to all forwarding complexes.
Default
no multicast-network-domain
Platforms
All
multicast-policer
multicast-policer
Syntax
multicast-policer policer-id [fp-redirect-group]
no multicast-policer
Context
[Tree] (config>qos>sap-ingress>fc multicast-policer)
Full Context
configure qos sap-ingress fc multicast-policer
Description
Within a sap-ingress QoS policy forwarding class context, the multicast-policer command is used to map packets that match the forwarding class and are considered multicast in nature to the specified policer-id. The specified policer-id must already exist within the sap-ingress QoS policy. While the system is determining the forwarding class of a packet, it is also looking up its forwarding destination based on the ingress service type and the service instance forwarding records. Two basic types of services support multicast packets: routed services (IES and VPRN) and L2 multipoint services (VPLS, I-VPLS, and B-VPLS). For the routed service types, a multicast packet is destined to an IPv4 or IPv6 multicast address. For the L2 multipoint services, a multicast packet is a packet destined to a multicast MAC address (multicast bit set in the destination MAC address but not the ff:ff:ff:ff:ff:ff broadcast address). The VPLS services also support two other multipoint forwarding types (broadcast and unknown), which are considered separate from the multicast forwarding type.
If ingress forwarding logic has resolved a packet to the multicast forwarding type within the forwarding class, it will be mapped to either an ingress multipoint queue (using the multicast queue-id or multicast queue-id group ingress-queue-group commands) or an ingress policer (multicast-policer policer-id). The multicast and multicast-policer commands within the forwarding class context are mutually exclusive. By default, the multicast forwarding type is mapped to the SAP ingress default multipoint queue. If the multicast-policer policer-id command is executed, any previous policer mapping or queue mapping for the multicast forwarding type within the forwarding class is overridden if the policer mapping is successful.
A policer defined within the sap-ingress policy is not actually created on an ingress SAP or a subscriber using an sla-profile where the policy is applied until at least one forwarding type (unicast, broadcast, unknown, or multicast) from one of the forwarding classes is mapped to the policer. If insufficient policer resources exist to create the policer for a SAP or subscriber or multiservice site, or ingress policing is not supported on the port associated with the SAP or subscriber or multiservice site, the initial forwarding class forwarding type mapping will fail.
The multicast-policer command is ignored for instances of the policer applied to SAPs subscribers or multiservice site where broadcast packets are not supported.
When the multicast forwarding type within a forwarding class is mapped to a policer, the multicast packets classified to the subclasses within the forwarding class are also mapped to the policer.
The no form of this command is used to restore the mapping of the multicast forwarding type within the forwarding class to the default multipoint queue. If all forwarding class forwarding types had been removed from the default multipoint queue, the queue will not exist on the SAPs subscribers or multiservice site associated with the QoS policy, and the no multicast-policer command will cause the system to attempt to create the default multipoint queue on each object. If the system cannot create the queue on each instance, the no multicast-policer command will fail and the multicast forwarding type within the forwarding class will continue its mapping to the existing policer-id. If the no multicast-policer command results in a policer without any current mappings, the policer will be removed from the SAPs and subscribers associated with the QoS policy. All statistics associated with the policer on each SAP and subscriber will be lost.
Parameters
- policer-id
-
When the forwarding class multicast-policer command is executed, a valid policer-id must be specified. The parameter policer-id references a policer-id that has already been created within the sap-ingress QoS policy.
- fp-redirect-group
-
Redirects a forwarding class to a forwarding plane queue-group as specified in a SAP QoS policy.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
multicast-queue
multicast-queue
Syntax
multicast-queue queue-id [group queue-group-name]
no multicast-queue
Context
[Tree] (config>qos>sap-ingress>fc multicast-queue)
Full Context
configure qos sap-ingress fc multicast-queue
Description
This command overrides the default multicast forwarding type queue mapping for fc fc-name. The specified queue-id must exist within the policy as a multipoint queue before the mapping can be made. When the forwarding class mapping is executed, all multicast traffic on a SAP using this policy is forwarded using the queue-id.
The multicast forwarding type includes the unknown unicast forwarding type and the broadcast forwarding type unless each is explicitly defined to a different multipoint queue. When the unknown and broadcast forwarding types are left as default, they will track the defined queue for the multicast forwarding type.
The no form of this command sets the multicast forwarding type queue-id back to the default queue for the forwarding class. If the broadcast and unknown forwarding types were not explicitly defined to a multipoint queue, they will also be set back to the default multipoint queue (queue 11).
Parameters
- queue-id
-
The queue-id parameter specified must be an existing, multipoint queue defined in the config>qos>sap-ingress context.
- group queue-group-name
-
This optional parameter is used to redirect the forwarding type within the forwarding class to the specified queue-id within the queue-group-name. When the policy is applied, all packets matching the forwarding class and forwarding type will be redirected to the queue within the specified queue group. The queue-group-name are configured in the config>qos>queue-group-templates egress and ingress contexts.
Platforms
All
multicast-queue
Syntax
multicast-queue queue-id
no multicast-queue
Context
[Tree] (config>qos>network-queue>fc multicast-queue)
Full Context
configure qos network-queue fc multicast-queue
Description
This command overrides the default multicast forwarding type queue mapping for fc fc-name. The specified queue-id must exist within the policy as a multipoint queue before the mapping can be made. When the forwarding class mapping is executed, all multicast traffic using this policy is forwarded using the queue-id.
The multicast forwarding type includes the unknown unicast forwarding type and the broadcast forwarding type, unless each is explicitly defined to a different multipoint queue. When the unknown and broadcast forwarding types are left as default, they will track the defined queue for the multicast forwarding type.
The no form of this command sets the multicast forwarding type queue-id back to the default queue for the forwarding class. If the broadcast and unknown forwarding types were not explicitly defined to a multipoint queue, they will also be set back to the default multipoint queue (queue 11).
Resource Utilization
When a multipoint queue is created and at least one forwarding class is mapped to the queue using the multipoint-queue command, a single ingress multipoint hardware queue is created per instance of the applied network-queue policy, using the queue-policy command at the ingress network FP level. Multipoint queues are not created at egress and the multipoint queues defined in the network-queue policy are ignored when the policy is applied to an egress port.
Parameters
- queue-id
-
Specifies any valid multipoint queue-ID in the policy. The queue-id parameter specified must be an existing, multipoint queue defined in the config>qos>network-queue>queue context.
Platforms
All
multicast-queue
Syntax
multicast-queue queue-id
Context
[Tree] (config>qos>shared-queue>fc multicast-queue)
Full Context
configure qos shared-queue fc multicast-queue
Description
This command configures the multicast forwarding type queue mapping for fc fc-name. The specified queue-id must exist within the policy as a multipoint queue before the mapping can be made. When the forwarding class mapping is executed, all multicast traffic on a SAP using this policy is forwarded using the queue-id.
The multicast forwarding type includes the unknown unicast forwarding type and the broadcast forwarding type unless each is explicitly defined to a different multipoint queue. When the unknown and broadcast forwarding types are left as default, they will track the defined queue for the multicast forwarding type.
The no form of this command sets the multicast forwarding type queue-id back to the default queue for the forwarding class. If the broadcast and unknown forwarding types were not explicitly defined to a multipoint queue, they will also be set back to the default multipoint queue (queue 11).
Parameters
- queue-id
-
The queue-id parameter specified must be an existing, multipoint queue defined in the config>qos>sap-ingress context policer-output-queues profile. For the 7950 XRS, this is not configurable in the policer-output-queues profile.
Platforms
All
multicast-redirection
multicast-redirection
Syntax
multicast-redirection [fwd-service service-id] ip-int-name
no multicast-redirection
Context
[Tree] (config>router>policy-options>policy-statement>entry>action multicast-redirection)
Full Context
configure router policy-options policy-statement entry action multicast-redirection
Description
This command configures the interface where to redirect IGMP multicast traffic to.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
multicast-redirection
Syntax
multicast-redirection [fwd-service service-id] ip-int-name
no multicast-redirection
Context
[Tree] (config>router>policy-options>policy-statement>default-action multicast-redirection)
Full Context
configure router policy-options policy-statement default-action multicast-redirection
Description
This command enables a redirection under a filtering policy. The filtering policy in this case becomes a redirection policy and it is defined under the router>policy-option hierarchy.
After the redirection policy is applied to the subscriber, all IGMP messages will be processed per subscriber host before they get redirected to the referenced interface (and possibly service). However, multicast traffic will not be replicated directly per subscriber host but instead it will be forwarded on the interface that is referenced in the redirection policy. The redirected interface must have IGMP enabled.
Currently all traffic is redirected and there is no ability to selectively redirect multicast traffic based on match conditions (such as, multicast-groups, source IP address of IGMP messages). Multicast redirection is supported between VPRN services and also between interfaces within the Global Routing Context. Multicast redirection is not supported between the VPRN services and the Global Routing Context. Multicast redirection is supported in the wholesale/retail VPRN context.
Redirecting from a VPRN instance to the GRT is not supported. Redirecting from a VPRN to a different VPRN is supported and redirecting from an IES to another IES is also supported.
Default
no multicast-redirection
Parameters
- fwd-service service-id
-
Specifies the service to which traffic should be redirected. This option is applied only in the VPRN context. It is possible to redirect the multicast group into another service instance routing interface.
- ip-int-name
-
specifies the alternate interface to which IGMP messages are redirected.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
multicast-senders
multicast-senders
Syntax
multicast-senders {auto | always | never}
no multicast-senders
Context
[Tree] (config>service>vprn>pim>if multicast-senders)
Full Context
configure service vprn pim interface multicast-senders
Description
This command configures the way subnet matching is done for incoming data packets on this interface. An IP multicast sender is an user entity to be authenticated in a receiving host.
Parameters
- auto
-
Subnet matching is automatically performed for incoming data packets on this interface.
- always
-
Subnet matching is always performed for incoming data packets on this interface.
- never
-
Subnet matching is never performed for incoming data packets on this interface.
Platforms
All
multicast-senders
Syntax
multicast-senders {auto | always | never}
no multicast-senders
Context
[Tree] (config>router>pim>interface multicast-senders)
Full Context
configure router pim interface multicast-senders
Description
This command configures how traffic from directly-attached multicast sources should be treated on broadcast interfaces. It can also be used to treat all traffic received on an interface as traffic coming from a directly-attached multicast source. This is particularly useful if a multicast source is connected to a point-to-point or unnumbered interface.
The no form of this command reverts to the default value.
Default
multicast-senders auto
Parameters
- auto
-
Specifies that, on broadcast interfaces, the forwarding plane performs subnet-match check on multicast packets received on the interface to determine if the packet is from a directly-attached source. On unnumbered/point-to-point interfaces, all traffic is implicitly treated as coming from a remote source.
- always
-
Treats all traffic received on the interface as coming from a directly-attached multicast source.
- never
-
Specifies that, on broadcast interfaces, traffic from directly-attached multicast sources will not be forwarded; however, traffic from a remote source will still be forwarded if there is a multicast state for it. On unnumbered/point-to-point interfaces, it means that all traffic received on that interface must not be forwarded.
Platforms
All
multicast-service
multicast-service
Syntax
multicast-service service-id
no multicast-service
Context
[Tree] (config>service>ies>video-interface multicast-service)
[Tree] (config>service>vprn>video-interface multicast-service)
[Tree] (config>service>vpls>video-interface multicast-service)
Full Context
configure service ies video-interface multicast-service
configure service vprn video-interface multicast-service
configure service vpls video-interface multicast-service
Description
This command adds a multicast service association to the video interface. This parameter is not required on the video interface when the service carries both unicast and multicast traffic.
When multicast and unicast are carried in separate service instances, the operator can set this parameter on the unicast video interface to form an association with the multicast service when replies need to be sent in the multicast service instance.
When multicast and unicast are carried in separate services when a downstream device (such as a DSLAM) can perform a service cross connect between the services and performs multicast replication.
The no form of the command removes the multicast service association.
Parameters
- service-id
-
The service ID of the associated multicast service.
Platforms
7450 ESS, 7750 SR-1, 7750 SR-7/12/12e, 7750 SR-1s, 7750 SR-2s, 7750 SR-7s, 7750 SR-14s
multicast6-fast-failover
multicast6-fast-failover
Syntax
[no] multicast6-fast-failover
Context
[Tree] (config>router>pim multicast6-fast-failover)
Full Context
configure router pim multicast6-fast-failover
Description
This command enables Multicast-Only Fast Reroute (MoFRR) functionality for IPv6 PIM-SSM interfaces in the global routing table instance.
The no form of this command disables MoFRR for IPv6 PIM-SSM interfaces.
Default
no multicast6-fast-failover
Platforms
All
multicastclient
multicastclient
Syntax
multicastclient [authenticate]
no multicastclient
Context
[Tree] (config>system>time>ntp multicastclient)
Full Context
configure system time ntp multicastclient
Description
This command configures the node to receive multicast NTP messages on the CPM MGMT port. If multicastclient is not configured, received NTP multicast traffic will be ignored. Use the show command to view the state of the configuration.
The no construct of this message removes the multicast client for the specified interface from the configuration.
Parameters
- authenticate
-
Specifies to make authentication a requirement (optional). If authentication is required, the authentication key-id received must have been configured in the authentication-key command, and that key-id type and key value must also match.
Platforms
All
multiclass
multiclass
Syntax
multiclass count
no multiclass
Context
[Tree] (config>port>ml-bundle>mlpp multiclass)
Full Context
configure port multilink-bundle mlppp multiclass
Description
This command enables multi-class MLPPP as defined by RFC 2686, The Multi-Class Extension to Multi-Link PPP, on a MLPPP bundle (including MLPPP bundle protection groups) with 2, 3 or 4 classes. For multiclass MLPPP bundles with a non-zero count, the class index takes valid values from 0 to one less than the maximum number of classes inclusive. For example a 4-class MLPPP bundle has 4 classes with indexes 0, 1, 2, and 3. A bundle must be shutdown with no links for this value to be changed.
Entries are created and deleted by the system depending on the number of classes being used by a given MLPPP bundle.
The no form of this command disables multi-class MLPPP.
Default
multiclass 4
Parameters
- count
-
Specifies the number of classes in a MLPPP bundle.
Platforms
7450 ESS, 7750 SR-7/12/12e
multihop
multihop
Syntax
multihop ttl-value
no multihop
Context
[Tree] (config>subscr-mgmt>bgp-prng-plcy multihop)
Full Context
configure subscriber-mgmt bgp-peering-policy multihop
Description
This command configures the time to live (TTL) value entered in the IP header of packets sent to an EBGP peer multiple hops away.
This parameter is meaningful only when configuring EBGP peers. It is ignored if set for an IBGP peer.
The no form of this command is used to convey to the BGP instance that the EBGP peers are directly connected.
The no form of this command reverts to default values.
Default
multihop 1 (EBGP peers are directly connected)
multihop 64 (IBGP)
Parameters
- ttl-value
-
Specifies the TTL value, expressed as a decimal integer.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
multihop
Syntax
multihop ttl-value
no multihop
Context
[Tree] (config>service>vprn>bgp>group>neighbor multihop)
[Tree] (config>service>vprn>bgp multihop)
[Tree] (config>service>vprn>bgp>group multihop)
Full Context
configure service vprn bgp group neighbor multihop
configure service vprn bgp multihop
configure service vprn bgp group multihop
Description
This command configures the time to live (TTL) value entered in the IP header of packets sent to an EBGP peer multiple hops away.
This parameter is meaningful only when configuring EBGP peers. It is ignored if set for an IBGP peer.
The no form of this command is used to convey to the BGP instance that the EBGP peers are directly connected.
The no form of this command reverts to default values.
Default
multihop 1 (EBGP peers are directly connected)
multihop 64 (IBGP)
Parameters
- ttl-value
-
Specifies the TTL value, expressed as a decimal integer.
Platforms
All
multihop
Syntax
multihop ttl-value
no multihop
Context
[Tree] (config>router>bgp multihop)
[Tree] (config>router>bgp>group>neighbor multihop)
[Tree] (config>router>bgp>group multihop)
Full Context
configure router bgp multihop
configure router bgp group neighbor multihop
configure router bgp group multihop
Description
This command configures the time to live (TTL) value entered in the IP header of packets sent to an EBGP peer multiple hops away.
The no form of this command is used to convey to the BGP instance that the EBGP peers are directly connected.
The no form of this command used at the global level reverts to default.
The no form of this command used at the group level reverts to the value defined at the global level.
The no form of this command used at the neighbor level reverts to the value defined at the group level.
Default
multihop 1 — EBGP peers are directly connected.
multihop 64 — IBGP
Parameters
- ttl-value
-
Specifies the TTL value, expressed as a decimal integer.
Platforms
All
multilink-bundle
multilink-bundle
Syntax
[no] multilink-bundle
Context
[Tree] (config>port multilink-bundle)
Full Context
configure port multilink-bundle
Description
This command creates the context to configure bundle properties for this bundle port.
Platforms
7450 ESS, 7750 SR-7/12/12e
multipath-eligible
multipath-eligible
Syntax
[no] multipath-eligible
Context
[Tree] (config>service>vprn>bgp>group multipath-eligible)
[Tree] (config>service>vprn>bgp>neighbor multipath-eligible)
Full Context
configure service vprn bgp group multipath-eligible
configure service vprn bgp neighbor multipath-eligible
Description
This command specifies that a BGP neighbor or the set of BGP neighbors in a peer group should be part of a selective multipath set. Selective multipaths are only supported by the ipv4, label-ipv4, ipv6, and label-ipv6 address families.
If no candidate multipath route for an IP prefix came from a multipath-eligible peer, multipaths are selected without further constraints.
If the best route for an IP prefix is received from a neighbor marked as multipath-eligible, other routes for the same prefix are not eligible to be used as multipaths unless they also came from peers marked as multipath-eligible.
If the best route for an IP prefix did not come from a multipath-eligible peer but there is at least one candidate multipath route for the same prefix from a multipath-eligible peer, multipath is not used.
The no form of this command marks a neighbor or group as non-multipath eligible. The effect of this depends on whether other neighbors and groups are marked as multipath eligible.
Default
no multipath-eligible
Platforms
All
multipath-eligible
Syntax
[no] multipath-eligible
Context
[Tree] (config>router>bgp>group>neighbor multipath-eligible)
[Tree] (config>router>bgp>group multipath-eligible)
Full Context
configure router bgp group neighbor multipath-eligible
configure router bgp group multipath-eligible
Description
This command specifies that a BGP neighbor or the set of BGP neighbors in a peer group should be part of a selective multipath set. Selective multipaths are only supported by the ipv4, label-ipv4, ipv6, and label-ipv6 address families.
If no candidate multipath route for an IP prefix came from a multipath-eligible peer then multipaths are selected without further constraints.
If the best route for an IP prefix is received from a neighbor marked as multipath-eligible, then other routes for the same prefix are not eligible to be used as multipaths unless they also came from peers marked as multipath-eligible.
If the best route for an IP prefix did not come from a multipath-eligible peer but there is at least one candidate multipath route for the same prefix from a multipath-eligible peer then multipath is not used.
The no form of this command marks a neighbor or group as non-multipath eligible. The effect of this depends on whether other neighbors and groups are marked as multipath eligible.
Default
no multipath-eligible
Platforms
All
multiple-option
multiple-option
Syntax
multiple-option {true | false}
Context
[Tree] (config>subscr-mgmt>cat-map>category>exh-lvl>egr-ip>entry>match multiple-option)
[Tree] (config>subscr-mgmt>cat-map>category>exh-lvl>ingr-ip>entry>match multiple-option)
Full Context
configure subscriber-mgmt category-map category exhausted-credit-service-level egress-ip-filter-entries entry match multiple-option
configure subscriber-mgmt category-map category exhausted-credit-service-level ingress-ip-filter-entries entry match multiple-option
Description
This command configures the multiple-option match condition.
The no form of this command reverts to the default.
Parameters
- true
-
Enables checking the number of IP options in the IP header.
- false
-
Disables checking the number of IP options in the IP header.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
multiple-option
Syntax
multiple-option {true | false}
no multiple-option
Context
[Tree] (config>filter>ip-filter>entry>match multiple-option)
Full Context
configure filter ip-filter entry match multiple-option
Description
This command configures matching packets that contain one or more than one option fields in the IP header as an IP filter match criterion.
The no form of the command removes the checking of the number of option fields in the IP header as a match criterion.
Default
no multiple-option
Parameters
- true
-
Specifies matching on IP packets that contain more than one option field in the header.
- false
-
Specifies matching on IP packets that do not contain multiple option fields present in the header.
Platforms
All
multiple-option
Syntax
multiple-option {true | false}
no multiple-option
Context
[Tree] (cfg>sys>sec>cpm>ip-filter>entry>match multiple-option)
Full Context
configure system security cpm-filter ip-filter entry match multiple-option
Description
This command configures matching packets that contain more than one option fields in the IP header as an IP filter match criterion.
The no form of this command removes the checking of the number of option fields in the IP header as a match criterion.
Default
no multiple-option
Parameters
- true
-
Specifies matching on IP packets that contain more than one option field in the header.
- false
-
Specifies matching on IP packets that do not contain multiple option fields present in the header.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
multiplier
multiplier
Syntax
multiplier [multiplier]
no multiplier
Context
[Tree] (config>lag>bfd>family multiplier)
Full Context
configure lag bfd family multiplier
Description
This command specifies the detect multiplier used for a micro-BFD session over the associated LAG links. If a BFD control packet is not received for a period of multiplier X receive-interval then the session is declared down.
The no form of this command removes multiplier from the configuration.
Default
multiplier 3
Parameters
- multiplier
-
Specifies the multiplier value.
Platforms
All
multiplier
Syntax
multiplier multiplier-value
no multiplier
Context
[Tree] (config>port>ethernet>eth-cfm>mep>csf-enable multiplier)
[Tree] (cfg>lag>eth-cfm>mep>csf multiplier)
Full Context
configure port ethernet eth-cfm mep csf-enable multiplier
configure lag eth-cfm mep csf-enable multiplier
Description
This command configures the multiplier used for timing out the CSF.
Parameters
- multiplier-value
-
Specifies the multiplier used for timing out CSF.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
multiplier
Syntax
multiplier multiplier-value
no multiplier
Context
[Tree] (config>service>epipe>sap>eth-cfm>mep>csf-enable multiplier)
[Tree] (config>service>vpls>mesh-sdp>eth-cfm>mep>csf-enable multiplier)
[Tree] (config>service>ies>if>sap>eth-cfm>mep>csf-enable multiplier)
[Tree] (config>service>epipe>spoke-sdp>eth-cfm>mep>csf-enable multiplier)
[Tree] (config>service>vpls>sap>eth-cfm>mep>csf-enable multiplier)
[Tree] (config>service>vprn>sub-if>grp-if>sap>eth-cfm>mep>csf-enable multiplier)
[Tree] (config>service>vprn>if>spoke-sdp>eth-cfm>mep>csf-enable multiplier)
[Tree] (config>service>ies>if>spoke-sdp>eth-cfm>mep>csf-enable multiplier)
[Tree] (config>service>ies>sub-if>grp-if>sap>eth-cfm>csf-enable multiplier)
[Tree] (config>service>vpls>spoke-sdp>eth-cfm>mep>csf-enable multiplier)
[Tree] (config>service>ies>sub-if>grp-if>sap>eth-cfm>mep multiplier)
[Tree] (config>service>vprn>if>sap>eth-cfm>mep>csf-enable multiplier)
Full Context
configure service epipe sap eth-cfm mep csf-enable multiplier
configure service vpls mesh-sdp eth-cfm mep csf-enable multiplier
configure service ies interface sap eth-cfm mep csf-enable multiplier
configure service epipe spoke-sdp eth-cfm mep csf-enable multiplier
configure service vpls sap eth-cfm mep csf-enable multiplier
configure service vprn subscriber-interface group-interface sap eth-cfm mep csf-enable multiplier
configure service vprn interface spoke-sdp eth-cfm mep csf-enable multiplier
configure service ies interface spoke-sdp eth-cfm mep csf-enable multiplier
configure service ies subscriber-interface group-interface sap eth-cfm csf-enable multiplier
configure service vpls spoke-sdp eth-cfm mep csf-enable multiplier
configure service ies subscriber-interface group-interface sap eth-cfm mep multiplier
configure service vprn interface sap eth-cfm mep csf-enable multiplier
Description
This command configures the multiplication factor applied to the receive time that is used to clear the CSF condition.
The no form of this command disables the multiplier used for timing out CSF.
Default
multiplier 3.5
Parameters
- multiplier-value
-
Specifies the multiplication factor applied to the receive time that is used to clear the CSF condition. This value can only be configured in increments of 0.5. Configuring a value of 0.0 means that the CSF condition is cleared only when C-DCI is received.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
- configure service epipe spoke-sdp eth-cfm mep csf-enable multiplier
- configure service vpls mesh-sdp eth-cfm mep csf-enable multiplier
- configure service vpls spoke-sdp eth-cfm mep csf-enable multiplier
- configure service ies interface sap eth-cfm mep csf-enable multiplier
- configure service ies interface spoke-sdp eth-cfm mep csf-enable multiplier
- configure service vprn interface spoke-sdp eth-cfm mep csf-enable multiplier
- configure service vpls sap eth-cfm mep csf-enable multiplier
- configure service vprn interface sap eth-cfm mep csf-enable multiplier
- configure service epipe sap eth-cfm mep csf-enable multiplier
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s
- configure service vprn subscriber-interface group-interface sap eth-cfm mep csf-enable multiplier
- configure service ies subscriber-interface group-interface sap eth-cfm mep multiplier
multiplier
Syntax
multiplier multiplier
no multiplier
Context
[Tree] (config>router>bfd>bfd-template multiplier)
Full Context
configure router bfd bfd-template multiplier
Description
This command specifies the detect multiplier for a BFD session. If a BFD control packet is not received for a period of multiplier x receive-interval (the parameter value of the receive-interval command), the session is declared down.
The no form of this command reverts to the default value.
Default
multiplier 3
Parameters
- multiplier
-
Specifies the multiplier.
Platforms
All
multiplier
Syntax
multiplier sample-window-durations
Context
[Tree] (config>test-oam>link-meas>template>asw multiplier)
Full Context
configure test-oam link-measurement measurement-template aggregate-sample-window multiplier
Description
This command configures the number of sample windows in an aggregate sample window.
Default
multiplier 12
Parameters
- sample-window-durations
-
Specifies the number of sample windows
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
multiplier
Syntax
multiplier interval-durations
Context
[Tree] (config>test-oam>link-meas>template>sw multiplier)
Full Context
configure test-oam link-measurement measurement-template sample-window multiplier
Description
This command configures the number of probe results that should be in the sample window. For example, a multiplier of 10 and an interval of 5 results in 50 probes being transmitted from an individual sample window. Consequently, 50 probe results are expected within the 50 second duration that the sample window is ‟In-progress”.
Default
multiplier 10
Parameters
- interval-durations
-
Specifies the number of intervals in a sample window.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
multipliers
multipliers
Syntax
multipliers sample-multiplier num1 adjust-multiplier num2
no multipliers
Context
[Tree] (config>router>mpls>lsp-template>auto-bandwidth multipliers)
[Tree] (config>router>mpls>lsp>auto-bandwidth multipliers)
Full Context
configure router mpls lsp-template auto-bandwidth multipliers
configure router mpls lsp auto-bandwidth multipliers
Description
This command configures the sample-multiplier and adjust-multiplier applicable to one particular LSP.
The sample-multiplier configures the number of collection intervals between measurements of the number of bytes that have been transmitted on the LSP. The byte counts include the layer 2 encapsulation of MPLS packets and represent traffic of all forwarding classes and priorities (in-profile vs, out-of-profile) belonging to the LSP. The router calculates the average data rate in each sample interval. The maximum of this average data rate over multiple sample intervals is the measured bandwidth input to the auto-bandwidth adjustment algorithms.
The adjust-multiplier is the number of collection intervals between periodic evaluations by the ingress LER about whether to adjust the LSP bandwidth. The router keeps track of the maximum average data rate of each LSP since the last reset of the adjust-count.
The adjust-multiplier is not allowed to be set to a value less than the sample-multiplier. It is recommended that the adjust-multiplier be a multiple of the sample-multiplier.
The no form of this command instructs the system to take the value from the auto-bandwidth-multipliers command.
Default
no multipliers
Parameters
- number1
-
Specifies the number of collection intervals in a sample interval.
- number2
-
Specifies the number of collection intervals in an adjust interval.
Platforms
All
multistream-spmsi
multistream-spmsi
Syntax
multistream-spmsi index [create]
no multistream-spmsi index
Context
[Tree] (config>service>vprn>mvpn>pt>selective multistream-spmsi)
Full Context
configure service vprn mvpn provider-tunnel selective multistream-spmsi
Description
This command creates a multi-stream S-PMSI policy. Having multiple multi-stream S-PMSIs per MVPN creates a link list, in which the first match (lowest index) will be chosen for a multicast stream. The number of configured multi-stream S-PMSIs cannot exceed the configured maximum S-PMSI for a given MVPN.
Parameters
- index
-
Specifies the index number.
Platforms
All
mvpn
mvpn
Syntax
mvpn
Context
[Tree] (config>service>vprn mvpn)
Full Context
configure service vprn mvpn
Description
Commands in this context configure MVPN-related parameters for the IP VPN.
Platforms
All
mvpn
Syntax
[no] mvpn
Context
[Tree] (config>router>ldp>import-pmsi-routes mvpn)
Full Context
configure router ldp import-pmsi-routes mvpn
Description
This command specifies that the SR OS is to cache inter-as MVPN PMSI AD routes for option B.
The no form of this command disables caching of MVPN PMSI AD routes. The default is disabled, however when an upgrade from a software load that does not supports this command is performed, this command will be enabled after the upgrade.
This command is not enabled if the user is using an older config file.
Default
no mvpn
Platforms
All
mvpn
Syntax
[no] mvpn
Context
[Tree] (config>router>gtm mvpn)
Full Context
configure router gtm mvpn
Description
This command enables and disables the context to configure MVPN-related parameters.
Platforms
All
mvpn-ipv4
mvpn-ipv4
Syntax
mvpn-ipv4 send send-limit receive [none]
mvpn-ipv4 send send-limit
no mvpn-ipv4
Context
[Tree] (config>router>bgp>group>add-paths mvpn-ipv4)
[Tree] (config>router>bgp>group>neighbor>add-paths mvpn-ipv4)
[Tree] (config>router>bgp>add-paths mvpn-ipv4)
Full Context
configure router bgp group add-paths mvpn-ipv4
configure router bgp group neighbor add-paths mvpn-ipv4
configure router bgp add-paths mvpn-ipv4
Description
This command configures the add-paths capability for multicast VPN IPv4 routes. By default, add-paths is not enabled for multicast VPN IPv4 routes.
The maximum number of paths per multicast VPN IPv4 NRLI to send is the configured send-limit, which is a mandatory parameter. The capability to receive multiple multicast paths per prefix from a peer is configurable using the receive keyword, which is optional. If the receive keyword is not included in the command, receive capability is enabled by default. The none option disables the receive capability.
The no form of this command disables add-paths support for multicast VPN IPv4 routes, causing sessions established using add-paths for multicast VPN IPv4 to go down and come back up without the add-paths capability.
Default
no mvpn-ipv4
Parameters
- send-limit
-
Specifies the maximum number of paths per multicast VPN IPv4 NRLI that are allowed to be advertised to add-paths peers. The actual number of advertised routes may be less. If the value is none, the router does not negotiate the send capability with respect to multicast VPN IPv4 AFI/SAFI.
- receive
-
Specifies that the router negotiates to receive multiple routes per multicast VPN IPv4 NRLI.
- none
-
Specifies that the router does not negotiate to receive multiple routes per multicast VPN IPv4 NRLI.
Platforms
All
mvpn-ipv6
mvpn-ipv6
Syntax
mvpn-ipv6 send send-limit receive [none]
mvpn-ipv6 send send-limit
no mvpn-ipv6
Context
[Tree] (config>router>bgp>group>neighbor>add-paths mvpn-ipv6)
[Tree] (config>router>bgp>add-paths mvpn-ipv6)
[Tree] (config>router>bgp>group>add-paths mvpn-ipv6)
Full Context
configure router bgp group neighbor add-paths mvpn-ipv6
configure router bgp add-paths mvpn-ipv6
configure router bgp group add-paths mvpn-ipv6
Description
This command configures the add-paths capability for multicast VPN IPv6 routes. By default, add-paths is not enabled for multicast VPN IPv6 routes.
The maximum number of paths per multicast VPN IPv6 NRLI to send is the configured send-limit, which is a mandatory parameter. The capability to receive multiple multicast VPN paths per prefix from a peer is configurable using the receive keyword, which is optional. If the receive keyword is not included in the command, receive capability is enabled by default. The none option disables the receive capability.
The no form of this command disables add-paths support for multicast VPN IPv6 routes, causing sessions established using add-paths for multicast VPN IPv6 to go down and come back up without the add-paths capability.
Default
no mvpn-ipv6
Parameters
- send-limit
-
Specifies the maximum number of paths per multicast VPN IPv6 NRLI that are allowed to be advertised to add-paths peers. The actual number of advertised routes may be less. If the value is none, the router does not negotiate the send capability with respect to multicast VPN IPv6 AFI/SAFI.
- receive
-
Specifies that the router negotiates to receive multiple routes per multicast VPN IPv6 NRLI.
- none
-
Specifies that the router does not negotiate to receive multiple routes per multicast VPN IPv6 NRLI.
Platforms
All
mvpn-no-export
mvpn-no-export
Syntax
[no] mvpn-no-export
Context
[Tree] (config>router>ldp>import-pmsi-routes mvpn-no-export)
Full Context
configure router ldp import-pmsi-routes mvpn-no-export
Description
This command specifies that the SR OS is to cache intra-as MVPN PMSI AD routes for option B.
The no form of this command disables caching of intra-as MVPN PMSI AD routes. The default is disabled, however when an upgrade from a software load that does not supports this command is performed, this command will be enabled after the upgrade.
This command is enabled if the user is using an older config file.
Default
no mvpn-no-export
Platforms
All
mvpn-rtcache
mvpn-rtcache
Syntax
mvpn-rtcache [group grp-ip-address] [peer ip-address]
no mvpn-rtcache
Context
[Tree] (debug>router>pim mvpn-rtcache)
Full Context
debug router pim mvpn-rtcache
Description
This command enables debugging for the PIM MVPN route cache.
The no form of this command disables debugging for the PIM MVPN route cache.
Parameters
- grp-ip-address
-
Debugs information associated with the specified group.
- peer-ip-address
-
Debugs information associated with the specified peer.
Platforms
All
mvpn-type
mvpn-type
Syntax
mvpn-type {1 | 2 | 3 | 4 | 5 | 6 | 7}
no mvpn-type
Context
[Tree] (config>router>policy-options>policy-statement>entry>from mvpn-type)
Full Context
configure router policy-options policy-statement entry from mvpn-type
Description
This command allows match on ng-MVPN BGP route type when the policy is used for VRF-import/VRF-export/BGP global export policy. The policy will only be applied to multicast routes.
The no form of this command disables mvpn-type in the policy evaluation.
Default
no mvpn-type
Parameters
- 1 | 2 | 3 | 4 | 5 | 6 | 7
-
BGP MVPN route-type as per RFC 6514.
Platforms
All
mvpn-vrf-import-subtype-new
mvpn-vrf-import-subtype-new
Syntax
[no] mvpn-vrf-import-subtype-new
Context
[Tree] (config>router>bgp mvpn-vrf-import-subtype-new)
Full Context
configure router bgp mvpn-vrf-import-subtype-new
Description
When enabled, the type/subtype in advertised routes is encoded as 0x010b.
The no form of this command (the default) encodes the type/subtype as 0x010a (to preserve backwards compatibility).
Default
no mvpn-vrf-import-subtype-new
Platforms
All
mvr
mvr
Syntax
mvr
Context
[Tree] (config>service>vpls>igmp-snooping mvr)
[Tree] (config>service>vpls>sap>mld-snooping mvr)
[Tree] (config>service>vpls>sap>igmp-snooping mvr)
[Tree] (config>service>vpls>mld-snooping mvr)
Full Context
configure service vpls igmp-snooping mvr
configure service vpls sap mld-snooping mvr
configure service vpls sap igmp-snooping mvr
configure service vpls mld-snooping mvr
Description
Commands in this context configure Multicast VPLS Registration (MVR) parameters.
Platforms
All
mvr
Syntax
mvr
Context
[Tree] (config>subscr-mgmt>msap-policy>vpls-only>igmp-snp mvr)
Full Context
configure subscriber-mgmt msap-policy vpls-only-sap-parameters igmp-snooping mvr
Description
Commands in this context configure Multicast VPLS Registration (MVR) parameters.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
mvrp
mvrp
Syntax
mvrp
Context
[Tree] (config>service>vpls>mrp mvrp)
[Tree] (config>service>vpls>sap>mrp mvrp)
Full Context
configure service vpls mrp mvrp
configure service vpls sap mrp mvrp
Description
This object consolidates the MVRP attributes. MVRP is only supported initially in the management VPLS so the object is not supported under BVPLS, IVPLS or regular VPLS not marked with the m-vpls tag.
Platforms
All
mvrp-control
mvrp-control
Syntax
[no] mvrp-control
Context
[Tree] (config>service>vpls>vpls-group mvrp-control)
Full Context
configure service vpls vpls-group mvrp-control
Description
This command enables MVRP control in the VPLS instances instantiated using the templates for the specified vpls-group. That means the flooding FDB will be created empty and will be populated with endpoints whenever MVRP receives a declaration and a registration on a specific endpoint. Also the VLAN ID associated by the control VPLS with the instantiated VPLS will be declared on service activation by MVRP on all virtual MVRP ports in the control VPLS. Service activation takes place when at least one other SAP is provisioned and brought up under the data VPLS. This is usually a customer facing SAP or a SAP leading outside of the MVRP controlled domain.
The no form of this command disallows MVRP control over this VPLS. The VPLS will be created with a regular FDB and will become as a result active upon creation time. Command change is allowed only when the related vpls-group is in shutdown state.
Default
no mvrp-control
Platforms
All