m Commands – Part I
mac
mac
Syntax
mac ieee-address
no mac
Context
[Tree] (config>subscr-mgmt>loc-user-db>ipoe>host>host-ident mac)
Full Context
configure subscriber-mgmt local-user-db ipoe 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
7705 SAR Gen 2
mac
Syntax
[no] mac ieee-mac-address
Context
[Tree] (config>service>vprn>if>ipv6>vrrp mac)
[Tree] (config>service>vprn>if mac)
[Tree] (config>service>vprn>if>vrrp mac)
[Tree] (config>service>vprn>nw-if mac)
Full Context
configure service vprn interface ipv6 vrrp mac
configure service vprn interface mac
configure service vprn interface vrrp mac
configure service vprn network-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
7705 SAR Gen 2
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
7705 SAR Gen 2
mac
Syntax
mac ieee-address
no mac [ieee-address]
Context
[Tree] (config>service>ies>if mac)
Full Context
configure service ies 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
7705 SAR Gen 2
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
7705 SAR Gen 2
mac
Syntax
mac ieee-address
no mac
Context
[Tree] (config>port>ethernet mac)
[Tree] (config>lag mac)
Full Context
configure port ethernet mac
configure lag 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
7705 SAR Gen 2
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
7705 SAR Gen 2
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 7705 SAR Gen 2, 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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
mac
Syntax
mac name
no mac
Context
[Tree] (config>service>template>vpls-sap-template>egress>filter-name mac)
[Tree] (config>service>template>vpls-sap-template>ingress>filter-name mac)
Full Context
configure service template vpls-sap-template egress filter-name mac
configure service template vpls-sap-template ingress 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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
mac
Syntax
mac mac-address
no mac
Context
[Tree] (config>router>if>ipv6>vrrp mac)
[Tree] (config>router>if>vrrp mac)
Full Context
configure router interface ipv6 vrrp mac
configure router interface 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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
mac-filter
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
mac-move
mac-move
Syntax
[no] mac-move
Context
[Tree] (config>service>vpls mac-move)
[Tree] (config>service>template>vpls-template mac-move)
Full Context
configure service vpls mac-move
configure service template vpls-template 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
7705 SAR Gen 2
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
7705 SAR Gen 2
mac-pinning
mac-pinning
Syntax
[no] mac-pinning
Context
[Tree] (config>service>vpls>spoke-sdp mac-pinning)
[Tree] (config>service>vpls>mesh-sdp mac-pinning)
[Tree] (config>service>vpls>sap mac-pinning)
[Tree] (config>service>vpls>endpoint mac-pinning)
Full Context
configure service vpls spoke-sdp mac-pinning
configure service vpls mesh-sdp mac-pinning
configure service vpls sap 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
7705 SAR Gen 2
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 7705 SAR Gen 2, 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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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 main-ct-retry-limit)
[Tree] (config>router>mpls>lsp-template main-ct-retry-limit)
Full Context
configure router mpls lsp main-ct-retry-limit
configure router mpls lsp-template 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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
managed-configuration
managed-configuration
Syntax
[no] managed-configuration
Context
[Tree] (config>router>router-advert>if managed-configuration)
[Tree] (config>service>vprn>router-advert>if managed-configuration)
Full Context
configure router router-advertisement interface managed-configuration
configure service vprn router-advertisement interface 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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
manual-keying
manual-keying
Syntax
[no] manual-keying
Context
[Tree] (config>service>vprn>if>sap>ipsec-tunnel manual-keying)
[Tree] (config>service>vprn>if>ipsec>ipsec-tunnel manual-keying)
[Tree] (config>service>ies>if>ipsec>ipsec-tunnel manual-keying)
[Tree] (config>router>if>ipsec>ipsec-tunnel manual-keying)
Full Context
configure service vprn interface sap ipsec-tunnel manual-keying
configure service vprn interface ipsec ipsec-tunnel manual-keying
configure service ies interface ipsec ipsec-tunnel manual-keying
configure router 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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
mask
mask
Syntax
mask type ppp-match-type {[prefix-string prefix-string | prefix-length prefix-length] [suffix-string suffix-string | suffix-length suffix-length]}
no mask type ppp-match-type
mask type ipoe-match-type {[prefix-string prefix-string | prefix-length prefix-length] [suffix-string suffix-string | suffix-length suffix-length]}
no mask type ipoe-match-type
Context
[Tree] (config>subscr-mgmt>loc-user-db>ipoe mask)
Full Context
configure subscriber-mgmt local-user-db ipoe mask
Description
This command configures a mask for the specified match type. The masking is applied on the parameter when performing an LUDB lookup to identify a host.
The no form of this command removes the mask from the configuration.
Parameters
- ppp-match-type
-
Specifies the parameter on which the mask should be applied for an LUDB lookup to identify a PPP host.
- ipoe-match-type
-
Specifies the parameter on which the mask should be applied for an LUDB lookup to identify an IPoE host.
The prefix-string and suffix-string command options are not supported when the ipoe-match-type value is set to duid-en or duid-ll-llt.
- prefix-string
-
Specifies a substring that is stripped of the start of the incoming parameter value before it is matched against the value configured in the LUDB host identification.
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 "\\".
This command option is unsupported when the ppp-match-type equals mac.
- prefix-length
-
Specifies the number of characters to remove from the start of the incoming parameter value before it is matched against the value configured in the LUDB host identification.
- suffix-string
-
Specifies a substring that is stripped of the end of the incoming parameter value before it is matched against the value configured in the LUDB host identification.
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 parameter value before it is matched against the value configured in the LUDB host identification.
When used with the mac or duid-ll-llt command option, the number of bits to remove from the end of the MAC address is specified.
Platforms
7705 SAR Gen 2
mask
Syntax
mask mask-value [type {included | excluded}]
no mask
Context
[Tree] (config>system>security>snmp>view mask)
Full Context
configure system security snmp view 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.
Platforms
7705 SAR Gen 2
mask-reply
mask-reply
Syntax
[no] mask-reply
Context
[Tree] (config>service>ies>if>icmp mask-reply)
[Tree] (config>service>vprn>nw-if>icmp mask-reply)
[Tree] (config>service>vprn>if>icmp mask-reply)
Full Context
configure service ies interface icmp mask-reply
configure service vprn network-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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
master-int-inherit
Syntax
[no] master-int-inherit
Context
[Tree] (config>service>vprn>if>ipv6>vrrp master-int-inherit)
[Tree] (config>service>vprn>if>vrrp master-int-inherit)
Full Context
configure service vprn interface ipv6 vrrp master-int-inherit
configure service vprn 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
7705 SAR Gen 2
master-int-inherit
Syntax
[no] master-int-inherit
Context
[Tree] (config>router>if>vrrp master-int-inherit)
[Tree] (config>router>if>ipv6>vrrp master-int-inherit)
Full Context
configure router interface vrrp master-int-inherit
configure router interface ipv6 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
7705 SAR Gen 2
match
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
7705 SAR Gen 2
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
7705 SAR Gen 2
match
Syntax
match [protocol protocol-id]
no match
Context
[Tree] (config>qos>sap-egress>ip-criteria>entry match)
[Tree] (config>qos>sap-ingress>ip-criteria>entry match)
Full Context
configure qos sap-egress ip-criteria entry match
configure qos sap-ingress 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
7705 SAR Gen 2
match
Syntax
match [next-header next-header]
no match
Context
[Tree] (config>qos>sap-ingress>ipv6-criteria>entry match)
[Tree] (config>qos>sap-egress>ipv6-criteria>entry match)
Full Context
configure qos sap-ingress ipv6-criteria entry match
configure qos sap-egress 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 7705 SAR Gen 2, 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
7705 SAR Gen 2
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.
Platforms
7705 SAR Gen 2
match
Syntax
match [protocol protocol-id]
no match
Context
[Tree] (config>qos>network>ingress>ip-criteria>entry match)
[Tree] (config>qos>network>egress>ip-criteria>entry match)
Full Context
configure qos network ingress ip-criteria entry match
configure qos network egress 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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
match
Syntax
[no] match
Context
[Tree] (config>log>filter>entry match)
Full Context
configure log filter entry match
Description
This command creates the context to enter and 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.
Platforms
7705 SAR Gen 2
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
7705 SAR Gen 2
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.
Evaluation stops when the first match is found, so 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
7705 SAR Gen 2
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
7705 SAR Gen 2
match-list
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 removes all match criteria.
Parameters
- match-type-x
-
Specifies up to four matching types to identify a host.
Platforms
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
match-qinq-dot1p
match-qinq-dot1p
Syntax
match-qinq-dot1p {top | bottom}
no match-qinq-dot1p
Context
[Tree] (config>service>ies>if>sap>ingress match-qinq-dot1p)
[Tree] (config>service>vpls>sap>ingress match-qinq-dot1p)
Full Context
configure service ies interface sap ingress match-qinq-dot1p
configure service vpls 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 7. 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 8. 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
7705 SAR Gen 2
match-qinq-dot1p
Syntax
match-qinq-dot1p {top | bottom}
no match-qinq-dot1p de
Context
[Tree] (config>service>epipe>sap>ingress match-qinq-dot1p)
Full Context
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 10. 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 11. 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 12. 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
7705 SAR Gen 2
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 14. 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 15. 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 16. 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
7705 SAR Gen 2
max
max
Syntax
max num-sessions
no max
Context
[Tree] (config>service>nat>nat-policy>session-limits max)
Full Context
configure service nat nat-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
7705 SAR Gen 2
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
7705 SAR Gen 2
max-age
max-age
Syntax
max-age max-age
no max-age [max-age]
Context
[Tree] (config>service>vpls>stp max-age)
[Tree] (config>service>template>vpls-template>stp max-age)
Full Context
configure service vpls stp max-age
configure service template vpls-template 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
7705 SAR Gen 2
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
7705 SAR Gen 2
max-bulk-duration
max-bulk-duration
Syntax
max-bulk-duration milliseconds
no max-bulk-duration
Context
[Tree] (config>system>snmp max-bulk-duration)
Full Context
configure system snmp max-bulk-duration
Description
This command sets the maximum duration to process an SNMP request before bulk responses are returned to avoid a timeout on the management system when a lot of information is returned in the response.
Default
no max-bulk-duration
Parameters
- milliseconds
-
Specifies the maximum duration to process requests before bulk responses are returned.
Platforms
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
max-channels-per-connection
max-channels-per-connection
Syntax
max-channels-per-connection number-of-channels
no max-channels-per-connection
Context
[Tree] (config>system>login-control>ssh max-channels-per-connection)
Full Context
configure system login-control ssh max-channels-per-connection
Description
This command configures the maximum number of channels supported on an SSH connection.
The no form of this command configures this value to 5, which is the default.
Default
max-channels-per-connection 5
Parameters
- number-of-channels
-
Specifies the number of channels.
Platforms
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
max-groups
max-groups
Syntax
max-groups max-groups
no max-groups
Context
[Tree] (config>service>vprn>igmp>if max-groups)
Full Context
configure service vprn igmp 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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
max-groups
Syntax
max-groups value
no max-groups
Context
[Tree] (config>router>igmp>if max-groups)
Full Context
configure router igmp 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
7705 SAR Gen 2
max-groups
Syntax
max-groups [1..16000]
no max-groups
Context
[Tree] (config>router>mld>if max-groups)
Full Context
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
7705 SAR Gen 2
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
7705 SAR Gen 2
max-grp-sources
max-grp-sources
Syntax
max-grp-sources max-group-sources
no max-grp-sources
Context
[Tree] (config>service>vprn>igmp>if max-grp-sources)
[Tree] (config>service>vprn>mld>interface max-grp-sources)
Full Context
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
7705 SAR Gen 2
max-grp-sources
Syntax
max-grp-sources value
no max-grp-sources
Context
[Tree] (config>router>igmp>if max-grp-sources)
Full Context
configure router igmp 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
7705 SAR Gen 2
max-grp-sources
Syntax
max-grp-sources [grp-source]
no max-grp-sources
Context
[Tree] (config>router>mld>if max-grp-sources)
Full Context
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
7705 SAR Gen 2
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>router>if>ipsec>ipsec-tunnel max-history-esp-key-records)
[Tree] (config>service>vprn>if>sap>ipsec-gw max-history-esp-key-records)
[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>ies>if>ipsec>ipsec-tunnel max-history-esp-key-records)
[Tree] (config>service>vprn>if>sap>ipsec-tunnel max-history-esp-key-records)
Full Context
configure router interface ipsec ipsec-tunnel max-history-esp-key-records
configure service vprn interface sap ipsec-gw max-history-esp-key-records
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 ies interface ipsec ipsec-tunnel max-history-esp-key-records
configure service vprn interface sap 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
7705 SAR Gen 2
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>ipsec>trans-mode-prof max-history-ike-key-records)
[Tree] (config>service>ies>if>ipsec>ipsec-tunnel max-history-ike-key-records)
[Tree] (config>service>vprn>if>sap>ipsec-gw max-history-ike-key-records)
[Tree] (config>service>vprn>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 ipsec ipsec-transport-mode-profile max-history-ike-key-records
configure service ies interface ipsec ipsec-tunnel max-history-ike-key-records
configure service vprn interface sap ipsec-gw max-history-ike-key-records
configure service vprn 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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
max-nbr-mac-addr
max-nbr-mac-addr
Syntax
max-nbr-mac-addr table-size
no max-nbr-mac-addr
Context
[Tree] (config>service>template>vpls-sap-template max-nbr-mac-addr)
[Tree] (config>service>vpls>spoke-sdp max-nbr-mac-addr)
[Tree] (config>service>vpls>sap max-nbr-mac-addr)
Full Context
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
Description
This command specifies the maximum number of FDB entries for both learned and static MAC addresses for this instance.
When the configured limit is reached, no new addresses are learned from the SAP or spoke SDP until at least one FDB entry is aged out or cleared.
When the configured limit is reached and the discard-unknown-source command is enabled for this instance, packets with unknown source MAC addresses are discarded. If discard-unknown-source is disabled, the packets are forwarded if their destination MAC addresses are known, or flooded if their destination MAC addresses are unknown.
However, if the configure service vpls discard-unknown command is enabled, packets with unknown destination MAC addresses are discarded, even if the limit of FDB entries on the specific VPLS instance is not reached.
The no form of this command restores the global MAC learning limitations for this 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
7705 SAR Gen 2
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 instance.
When the configured limit is reached, no new addresses are learned from the SAP or spoke SDP until at least one FDB entry is aged out or cleared.
When the configured limit is reached and the discard-unknown-source command is enabled for this instance, packets with unknown source MAC addresses are discarded. If discard-unknown-source is disabled, the packets are forwarded if their destination MAC addresses are known, or flooded if their destination MAC addresses are unknown.
However, if the configure service vpls discard-unknown command is enabled, packets with unknown destination MAC addresses are discarded, even if the limit of FDB entries on the specific VPLS instance is not reached.
The no form of this command restores the global MAC learning limitations for this 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
7705 SAR Gen 2
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)
Full Context
configure service vpls endpoint max-nbr-mac-addr
Description
This command specifies the maximum number of FDB entries for both learned and static MAC addresses for this instance.
When the configured limit is reached, no new addresses are learned from the SAP or spoke SDP until at least one FDB entry is aged out or cleared. Packets with unknown source MAC addresses are still forwarded if their destination MAC addresses are known, or flooded if their destination MAC addresses are unknown.
The no form of this command restores the global MAC learning limitations for this 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
7705 SAR Gen 2
max-num-groups
max-num-groups
Syntax
max-num-groups count
no max-num-groups
Context
[Tree] (config>service>vpls>spoke-sdp>mld-snooping max-num-groups)
[Tree] (config>service>vpls>mesh-sdp>igmp-snooping max-num-groups)
[Tree] (config>service>vpls>sap>igmp-snooping max-num-groups)
[Tree] (config>service>vpls>spoke-sdp>igmp-snooping max-num-groups)
[Tree] (config>service>vpls>sap>mld-snooping max-num-groups)
[Tree] (config>service>vpls>mesh-sdp>mld-snooping max-num-groups)
Full Context
configure service vpls spoke-sdp mld-snooping max-num-groups
configure service vpls mesh-sdp igmp-snooping max-num-groups
configure service vpls sap igmp-snooping max-num-groups
configure service vpls spoke-sdp igmp-snooping max-num-groups
configure service vpls sap mld-snooping max-num-groups
configure service vpls mesh-sdp 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
7705 SAR Gen 2
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
7705 SAR Gen 2
max-num-grp-sources
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>spoke-sdp>igmp-snooping max-num-grp-sources)
[Tree] (config>service>vpls>mesh-sdp>igmp-snooping max-num-grp-sources)
Full Context
configure service vpls sap igmp-snooping max-num-grp-sources
configure service vpls spoke-sdp igmp-snooping max-num-grp-sources
configure service vpls mesh-sdp igmp-snooping 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
7705 SAR Gen 2
max-num-sources
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>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 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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
max-rate
max-rate
Syntax
max-rate {rate | max}
no max-rate
Context
[Tree] (config>card>fp>ingress>acc>qgrp>policer-ctrl-over max-rate)
[Tree] (config>card>fp>ingress>network>qgrp>policer-ctrl-over max-rate)
Full Context
configure card fp ingress access queue-group policer-control-override max-rate
configure card fp ingress network 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
7705 SAR Gen 2
max-rate
Syntax
max-rate pir-rate
max-rate percent percent-rate
no max-rate
Context
[Tree] (config>port>ethernet>egr-scheduler-override max-rate)
Full Context
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
7705 SAR Gen 2
max-rate
Syntax
max-rate {rate | max}
Context
[Tree] (config>service>epipe>sap>ingress>policer-control-override max-rate)
[Tree] (config>service>epipe>sap>egress>policer-control-override max-rate)
Full Context
configure service epipe sap ingress 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
7705 SAR Gen 2
max-rate
Syntax
max-rate {rate | max}
Context
[Tree] (config>service>vpls>sap>ingress>policer-ctrl-over max-rate)
[Tree] (config>service>vpls>sap>egress>policer-ctrl-over max-rate)
Full Context
configure service vpls sap ingress policer-control-override max-rate
configure service vpls 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 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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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. 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
7705 SAR Gen 2
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.
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
max-sessions
max-sessions
Syntax
max-sessions number
Context
[Tree] (config>service>vprn>bgp>group>dynamic-neighbor>interface max-sessions)
[Tree] (config>router>bgp>group>dynamic-neighbor>interface max-sessions)
Full Context
configure service vprn bgp group dynamic-neighbor interface max-sessions
configure router 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
7705 SAR Gen 2
max-sources
max-sources
Syntax
max-sources max-sources
no max-sources
Context
[Tree] (config>service>vprn>mld>interface max-sources)
[Tree] (config>service>vprn>igmp>if max-sources)
Full Context
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
7705 SAR Gen 2
max-sources
Syntax
max-sources value
no max-sources
Context
[Tree] (config>router>igmp>if max-sources)
Full Context
configure router igmp 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
7705 SAR Gen 2
max-sources
Syntax
max-sources [grp-source]
no max-sources
Context
[Tree] (config>router>mld>if max-sources)
Full Context
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
7705 SAR Gen 2
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-template max-sr-labels)
[Tree] (config>router>mpls>lsp max-sr-labels)
Full Context
configure router mpls lsp-template max-sr-labels
configure router mpls lsp 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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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>dhcp>server>pool>failover maximum-client-lead-time)
[Tree] (config>router>dhcp6>server>failover maximum-client-lead-time)
[Tree] (config>router>dhcp6>server>pool>failover maximum-client-lead-time)
[Tree] (config>router>dhcp>server>failover maximum-client-lead-time)
[Tree] (config>service>vprn>dhcp>server>failover maximum-client-lead-time)
[Tree] (config>service>vprn>dhcp>server>pool>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 dhcp local-dhcp-server pool failover maximum-client-lead-time
configure router dhcp6 local-dhcp-server failover maximum-client-lead-time
configure router dhcp6 local-dhcp-server pool failover maximum-client-lead-time
configure router dhcp local-dhcp-server failover maximum-client-lead-time
configure service vprn dhcp local-dhcp-server failover maximum-client-lead-time
configure service vprn dhcp local-dhcp-server pool 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
7705 SAR Gen 2
maximum-declined
maximum-declined
Syntax
maximum-declined maximum-declined
no maximum-declined
Context
[Tree] (config>router>dhcp>server>pool>subnet maximum-declined)
[Tree] (config>service>vprn>dhcp>server>pool>subnet maximum-declined)
Full Context
configure router dhcp local-dhcp-server pool subnet maximum-declined
configure service vprn 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
7705 SAR Gen 2
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
7705 SAR Gen 2
maximum-number-upas
maximum-number-upas
Syntax
maximum-number-upas maximum-number-upas
no maximum-number-upas
Context
[Tree] (config>router>isis>upa maximum-number-upas)
Full Context
configure router isis prefix-unreachable maximum-number-upas
Description
This command configures a limit for the number of UPAs the router can advertise. If overrun, a system log is generated and additional UPAs are not advertised.
The no form of this command reverts to the default.
Default
32
Parameters
- maximum-number-upas
-
Specifies the maximum number of UPAs that the router can advertise.
Platforms
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
mbs
mbs
Syntax
mbs size [bytes | kilobytes]
no mbs
Context
[Tree] (config>service>ies>if>sap>ingress>queue-override>queue mbs)
[Tree] (config>service>vprn>if>sap>ingress>queue-override>queue mbs)
[Tree] (config>service>vprn>if>sap>egress>queue-override>queue mbs)
[Tree] (config>service>ies>if>sap>egress>queue-override>queue mbs)
Full Context
configure service ies interface sap ingress queue-override queue mbs
configure service vprn interface sap ingress queue-override queue mbs
configure service vprn interface sap egress 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
7705 SAR Gen 2
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'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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
mbs
Syntax
mbs {size [bytes | kilobytes] | default}
no mbs
Context
[Tree] (config>port>ethernet>network>egr>qgrp>qover>q mbs)
[Tree] (config>port>ethernet>access>egr>qgrp>qover>q mbs)
[Tree] (config>port>ethernet>access>ing>qgrp>qover>q mbs)
Full Context
configure port ethernet network egress queue-group queue-overrides queue mbs
configure port ethernet access egress queue-group queue-overrides queue mbs
configure port ethernet access ingress 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
7705 SAR Gen 2
mbs
Syntax
mbs size [bytes | kilobytes]
no mbs
Context
[Tree] (config>service>epipe>sap>egress>policer-over>plcr mbs)
[Tree] (config>service>epipe>sap>ingress>policer-over>plcr mbs)
Full Context
configure service epipe sap egress policer-override policer mbs
configure service epipe 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 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
7705 SAR Gen 2
mbs
Syntax
mbs {size [bytes | kilobytes] | default}
no mbs
Context
[Tree] (config>service>epipe>sap>ingress>queue-override>queue mbs)
[Tree] (config>service>epipe>sap>egress>queue-override>queue mbs)
Full Context
configure service epipe sap ingress queue-override queue mbs
configure service epipe 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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
mbs
Syntax
mbs {size [bytes | kilobytes] | default}
no mbs
Context
[Tree] (config>qos>sap-egress>policer mbs)
[Tree] (config>qos>sap-ingress>policer mbs)
Full Context
configure qos sap-egress policer mbs
configure qos sap-ingress 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
7705 SAR Gen 2
mbs
Syntax
mbs {size [bytes | kilobytes] | default}
mbs delay-time microseconds
mbs delay-percent percent
no mbs
Context
[Tree] (config>qos>sap-egress>queue mbs)
Full Context
configure qos sap-egress queue mbs
Description
This command configures the maximum number of buffers, in bytes or kilobytes, allowed for a specific queue. The value overrides the default value for the context.
The delay-time command option configures the MBS as a function of the expected delay. The system automatically translates this configuration into kilobytes based on the administrative rate of the queue parent (for example, the scheduler or aggregate-shaper).
The delay-percent command option configures the MBS as percentage of the SAP delay budget of the queue configured using the latency-budget command.
The no form of this command returns the queue to its default MBS.
Default
mbs default
Parameters
- size
-
This parameter is required when specifying mbs and is expressed as an integer representing the required size in either bytes or kilobytes.
- default
-
Keyword to set the MBS to its default value.
- bytes
-
Keyword to interpret the configured value is in bytes.
- kilobytes
-
Keyword to interpret the configured value is in kilobytes.
- microseconds
-
Specifies the MBS as a function of delay time.
- percent
-
Specifies the MBS as a percentage of the SAP latency budget.
Platforms
7705 SAR Gen 2
mbs
Syntax
mbs {size [bytes | kilobytes] | default}
no mbs
Context
[Tree] (config>qos>sap-ingress>queue mbs)
Full Context
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
7705 SAR Gen 2
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
7705 SAR Gen 2
mbs
Syntax
mbs {size [bytes | kilobytes] | default}
no mbs
Context
[Tree] (config>qos>qgrps>egr>qgrp>policer mbs)
[Tree] (config>qos>qgrps>ing>qgrp>policer mbs)
Full Context
configure qos queue-group-templates egress queue-group policer mbs
configure qos queue-group-templates ingress 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
7705 SAR Gen 2
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
7705 SAR Gen 2
mbs-contribution
mbs-contribution
Syntax
mbs-contribution size [bytes | kilobytes]
no mbs-contribution
Context
[Tree] (config>card>fp>ing>network>qgrp>policer-ctrl-over>mbs-thrshlds>prio mbs-contribution)
[Tree] (config>card>fp>ingress>access>qgrp>policer-ctrl-over>mbs-thrshlds>prio mbs-contribution)
Full Context
configure card fp ingress network queue-group policer-control-override priority-mbs-thresholds priority mbs-contribution
configure card fp ingress access 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.
-
The following table describes the FIR rates of the children based on weights.
Table 17. FIR Rates of the Children Based on Weights 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
7705 SAR Gen 2
mbs-contribution
Syntax
mbs-contribution size [bytes | kilobytes]
Context
[Tree] (config>service>epipe>sap>ingress>policer-ctrl-over>mbs-thrshlds>priority mbs-contribution)
[Tree] (config>service>epipe>sap>egress>policer-ctrl-over>mbs-thrshlds>priority mbs-contribution)
Full Context
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
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
7705 SAR Gen 2
mbs-contribution
Syntax
mbs-contribution size [{bytes | kilobytes}]
Context
[Tree] (config>service>vpls>sap>ingress>policer-ctrl-over>mbs-thrshlds>priority mbs-contribution)
[Tree] (config>service>vpls>sap>egress>policer-ctrl-over>mbs-thrshlds>priority mbs-contribution)
Full Context
configure service vpls sap ingress policer-control-override priority-mbs-thresholds priority mbs-contribution
configure service vpls sap egress 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
7705 SAR Gen 2
mbs-contribution
Syntax
mbs-contribution size [{bytes | kilobytes}]
Context
[Tree] (config>service>ies>if>sap>ingress>policer-ctrl-over>mbs-thrshlds>priority mbs-contribution)
[Tree] (config>service>ies>if>sap>egress>policer-ctrl-over>mbs-thrshlds>priority mbs-contribution)
Full Context
configure service ies interface sap ingress policer-control-override priority-mbs-thresholds priority mbs-contribution
configure service ies interface sap egress 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
7705 SAR Gen 2
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
7705 SAR Gen 2
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. 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 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.
Table 18. FIR Rates of the Children Based on Weights 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 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 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
7705 SAR Gen 2
mbytes
mbytes
Syntax
mbytes {mbytes | disable}
no mbytes
Context
[Tree] (config>system>security>ssh>key-re-exchange>server mbytes)
[Tree] (config>system>security>ssh>key-re-exchange>client mbytes)
Full Context
configure system security ssh key-re-exchange server mbytes
configure system security ssh key-re-exchange client 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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
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 should be synchronized with the multi-chassis peer.
Default
no mc-ring
Platforms
7705 SAR Gen 2
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
7705 SAR Gen 2
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
7705 SAR Gen 2
mcs
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
7705 SAR Gen 2
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
7705 SAR Gen 2