m Commands – Part II
md-auto-id
md-auto-id
Syntax
md-auto-id
Context
[Tree] (config>qos md-auto-id)
Full Context
configure qos md-auto-id
Description
This command automatically assigns numerical ID values for QoS policies in model-driven (MD) management interfaces.
Classic management interfaces use a numerical policy ID as the primary key for sap-ingress, sap-egress, and network QoS policies. In model-driven interfaces, SAP and network policies use string names as keys. The SAP and network policies can optionally be created in MD interfaces without having to explicitly select and specify a numerical policy ID. In this case, SR OS assigns an ID using the configured ID range.
Platforms
7705 SAR Gen 2
md-auto-id
Syntax
md-auto-id
Context
[Tree] (config>filter md-auto-id)
Full Context
configure filter md-auto-id
Description
This command automatically assigns numerical ID values for filter policies in model-driven management interfaces.
Classic management interfaces use a numerical filter ID as the primary key for IP filters, IPv6 filters, and MAC filters. In model-driven interfaces, IP, IPv6, and MAC filters use string names as keys. The filters can optionally be created in MD interfaces without having to explicitly select and specify a numerical filter ID. In this case, SR OS assigns an ID using the configured ID range.
Platforms
7705 SAR Gen 2
md-auto-id
Syntax
md-auto-id
Context
[Tree] (config>service md-auto-id)
Full Context
configure service md-auto-id
Description
This command automatically assigns numerical ID values for services, customers, and PW templates in model-driven (MD) management interfaces.
Classic management interfaces use a numerical service ID, customer ID, and PW template ID as the primary key for services, customers, and PW templates. In model-driven interfaces, services, customers, and PW templates use string names as keys. The services, customers, and PW templates can optionally be created in MD interfaces without having to explicitly select and specify a numerical ID. In this case, SR OS assigns an ID using the configured ID range.
Platforms
7705 SAR Gen 2
md-cli
md-cli
Syntax
md-cli
Context
[Tree] (config>system>management-interface>cli md-cli)
Full Context
configure system management-interface cli md-cli
Description
Commands in this context configure the MD-CLI management interface.
Platforms
7705 SAR Gen 2
md-cli
Syntax
md-cli
Context
[Tree] (config>system>security>management-interface md-cli)
Full Context
configure system security management-interface md-cli
Description
Commands in this context configure hash-control for the MD-CLI interface.
Platforms
7705 SAR Gen 2
md-cli-session
md-cli-session
Syntax
md-cli-session {permit | deny}
Context
[Tree] (config>system>security>profile>grpc>rpc-authorization md-cli-session)
Full Context
configure system security profile grpc rpc-authorization md-cli-session
Description
This command configures the use of the MdCli Session RPC for the user profile.
The no form of this command reverts to the default value.
Default
md-cli-session permit
Parameters
- deny
-
Specifies that the use of MdCli Session RPC is denied.
- permit
-
Specifies that the use of MdCli Session RPC is permitted.
Platforms
7705 SAR Gen 2
md-interfaces
md-interfaces
Syntax
[no] md-interfaces
Context
[Tree] (config>system>security>management-interface>output-authorization md-interfaces)
Full Context
configure system security management-interface output-authorization md-interfaces
Description
This command controls output authorization of commands or RPCs for model-driven interfaces that display configuration or state.
When enabled, output authorization is performed for the following commands:
-
MD-CLI info and compare commands
-
NETCONF <get> and <get-config> RPCs
-
gNMI Get RPC
When disabled, output authorization is not performed, which may significantly decrease the system response time by reducing command authorization requests, especially when remote AAA servers are used. Input to edit configuration is always authorized based on the AAA configuration.
By default, authorization checks are performed for configuration and state output.
The no form of this command disables authorization checks, allowing the output to be displayed immediately.
Default
md-interfaces
Platforms
7705 SAR Gen 2
mda
mda
Syntax
[no] mda mda-slot
Context
[Tree] (config>card mda)
Full Context
configure card mda
Description
This mandatory command enables access to a card’s MDA context. In SR OS, MDAs cover MDA and XMA.
Parameters
- mda-slot
-
Specifies the MDA slot number to be configured. Slots are numbered 1 and 2. On vertically oriented slots, the top MDA slot is number 1, and the bottom MDA slot is number 2. On horizontally oriented slots, the left MDA is number 1, and the right MDA slot is number 2.
Platforms
7705 SAR Gen 2
mda
Syntax
[no] mda mda-id
Context
[Tree] (config>service>vpls>mesh-sdp>egress>mfib-allowed-mda-destinations mda)
[Tree] (config>service>vpls>spoke-sdp>egress>mfib-allowed-mda-destinations mda)
Full Context
configure service vpls mesh-sdp egress mfib-allowed-mda-destinations mda
configure service vpls spoke-sdp egress mfib-allowed-mda-destinations mda
Description
This command specifies an MFIB-allowed MDA destination for an SDP binding configured in the system.
Parameters
- mda-id
-
Specifies an MFIB-allowed MDA destination
Platforms
7705 SAR Gen 2
mda
Syntax
[no] mda mda-id
Context
[Tree] (config>isa>tunnel-grp mda)
Full Context
configure isa tunnel-group mda
Description
This command specifies the MDA ID of the MS-ISA as the member of tunnel-group with multi-active enabled. Up to 16 MDA could be configured under the same tunnel-group.
Parameters
- mda-id
-
Specifies the id of MS-ISA.
Platforms
7705 SAR Gen 2
mda
Syntax
[no] mda mda-id
Context
[Tree] (config>isa>nat-group mda)
Full Context
configure isa nat-group mda
Description
This command configures an ISA NAT group MDA.
Parameters
- mda-id
-
Specifies the MDA ID in the slot/mda format.
Platforms
7705 SAR Gen 2
mda
Syntax
[no] mda mda-id
Context
[Tree] (config>service>pw-template>egress>mfib-mda mda)
Full Context
configure service pw-template egress mfib-allowed-mda-destinations mda
Description
This command specifies an MFIB-allowed media adapter destination for an SDP binding configured in the system.
Parameters
- mda-id
-
Specifies an MFIB-allowed media adapters destination.
Platforms
7705 SAR Gen 2
mda
Syntax
mda mda
no mda
Context
[Tree] (config>isa>tunnel-mem-pool mda)
Full Context
configure isa tunnel-member-pool mda
Description
This command configures an association between an MDA and the tunnel member pool.
The no form of this command removes the association between the MDA and the tunnel member pool.
Parameters
- name
-
Specifies the name of the MDA, up to 32 characters.
Platforms
7705 SAR Gen 2
mda-type
mda-type
Syntax
mda-type mda-type [level mda-level]
no mda-type
Context
[Tree] (config>card>mda mda-type)
Full Context
configure card mda mda-type
Description
This mandatory command provisions a specific MDA type to the device configuration for the slot. The MDA can be preprovisioned but an MDA must be provisioned before ports can be configured. Ports can be configured once the MDA is properly provisioned.
A maximum of two MDAs can be provisioned on an IOM or XCM. To modify an MDA slot, shut down all port associations.
XMAs are provisioned using MDA commands. A medium severity alarm is generated if an MDA is inserted that does not match the MDA type configured for the slot. This alarm is cleared when the correct MDA is inserted or the configuration is modified. A high severity alarm is raised when an administratively enabled MDA is removed from the chassis. This alarm is cleared if the either the correct MDA type is inserted or the configuration is modified. A low severity trap is issued if an MDA is removed that is administratively disabled.
An MDA can only be provisioned in a slot if the MDA type is allowed in the MDA slot. An error message is generated when an MDA is provisioned in a slot where it is not allowed.
Some MDA hardware can support two different firmware loads. One load includes the base Ethernet functionality, including 10G WAN mode, but does not include 1588 port-based timestamping. The second load includes the base Ethernet functionality and 1588 port-based timestamping, but does not include 10G WAN mode. These are identified as two MDA types that are the same, except for a "-ptp” suffix to indicate the second loadset; for example, x40-10gb-sfp and x40-10gb-sfp-ptp. A hard reset of the MDA occurs when switching between the two provisioned types.
A medium severity alarm is generated if an MDA is inserted that does not match the MDA type configured for the slot. This alarm is cleared when the correct MDA is inserted or the configuration is modified.
A high severity alarm is raised when an administratively enabled MDA is removed from the chassis. This alarm is cleared if the either the correct MDA type is inserted or the configuration is modified. A low severity trap is issued if an MDA is removed that is administratively disabled.
An alarm is raised if partial or complete MDA failure is detected. The alarm is cleared when the error condition ceases.
All parameters in the MDA context remain and if non-default values are required then their configuration remains as it is on all existing MDAs.
New generations of XMAs include variants controlled through hardware and software licensing. For these XMAs, the license level must be provisioned in addition to the MDA type. An XMA cannot become operational unless the provisioned license level matches the license level of the XMA installed into the slot. The set of license levels varies by MDA type.
The provisioned level controls aspects related to connector provisioning and the consumption of hardware egress queues and egress policers. Changes to the provisioned license level may be blocked if configuration that would not be permitted with the new target license level exists.
If the license level is not specified, the level is set to the highest license level for that XMA.
The no form of this command deletes the MDA from the configuration. The MDA must be administratively shut down before it can be deleted from the configuration.
Parameters
- mda-type
-
Specifies the type of MDA selected for the slot position. Values for this attribute vary by platform and release. The release notes include a listing of all supported mda-types and their CLI strings. In addition, the command can be queried to check which mda-types are relevant for the active platform type. Some examples include me6-10gb-spf+ and x4-100g-cfp2.
- mda-level
-
Specifies the MDA level. Possible values vary by MDA type.
Platforms
7705 SAR Gen 2
meas-interval
meas-interval
Syntax
meas-interval {5-mins | 15-mins | 1-hour | 1-day} [create]
no meas-interval {5-mins | 15-mins | 1-hour | 1-day}
Context
[Tree] (config>oam-pm>session meas-interval)
Full Context
configure oam-pm session meas-interval
Description
This command establishes the parameters of the individual measurement intervals utilized by the session. Multiple measurement intervals may be specified within the session. A maximum of three different measurement intervals may be configured under each session.
The no form of this command deletes the specified measurement interval.
Parameters
- meas-interval
-
Specifies the duration of the measurement interval.
- create
-
Creates the measurement interval.
Platforms
7705 SAR Gen 2
med-out
med-out
Syntax
med-out {number | igp-cost}
no med-out
Context
[Tree] (config>service>vprn>bgp>group med-out)
[Tree] (config>service>vprn>bgp med-out)
[Tree] (config>service>vprn>bgp>group>neighbor med-out)
Full Context
configure service vprn bgp group med-out
configure service vprn bgp med-out
configure service vprn bgp group neighbor med-out
Description
This command enables advertising the Multi-Exit Discriminator (MED) and assigns the value used for the path attribute for the MED advertised to BGP peers if the MED is not already set.
The specified value can be overridden by any value set via a route policy.
This configuration parameter can be set at three levels: global level (applies to all peers), group level (applies to all peers in peer-group) or neighbor level (only applies to specified peer). The most specific value is used.
The no form of this command used at the global level reverts to default where the MED is not advertised.
The no form of this command used at the group level reverts to the value defined at the global level.
The no form of this command used at the neighbor level reverts to the value defined at the group level.
Default
no med-out
Parameters
- number
-
Specifies the MED path attribute value, expressed as a decimal integer.
- igp-cost
-
Specifies the MED is set to the IGP cost of the given IP prefix.
Platforms
7705 SAR Gen 2
med-out
Syntax
med-out {number | igp-cost}
no med-out
Context
[Tree] (config>router>bgp>group>neighbor med-out)
[Tree] (config>router>bgp med-out)
[Tree] (config>router>bgp>group med-out)
Full Context
configure router bgp group neighbor med-out
configure router bgp med-out
configure router bgp group med-out
Description
This command enables advertising the Multi-Exit Discriminator (MED) and assigns the value used for the path attribute for the MED advertised to BGP peers if the MED is not already set.
The specified value can be overridden by any value set via a route policy.
This configuration parameter can be set at three levels: global level (applies to all peers), group level (applies to all peers in peer-group) or neighbor level (only applies to specified peer). The most specific value is used.
The no form of this command used at the global level reverts to default where the MED is not advertised.
The no form of this command used at the group level reverts to the value defined at the global level.
The no form of this command used at the neighbor level reverts to the value defined at the group level.
Default
no med-out
Parameters
- number
-
Specifies the MED path attribute value, expressed as a decimal integer.
- igp-cost
-
Sets MED to the IGP cost of the given IP prefix.
Platforms
7705 SAR Gen 2
member
member
Syntax
[no] member interface-name
Context
[Tree] (config>service>vprn>isis>link-group>level member)
Full Context
configure service vprn isis link-group level member
Description
This command adds or removes a links to the associated link-group. The interface name should already exist before it is added to a link-group.
The no form of this command removes the specified interface from the associated link-group.
Parameters
- interface-name
-
Specifies the name of the interface to be added or removed from the associated link-group.
Platforms
7705 SAR Gen 2
member
Syntax
member user-profile-name [user-profile-name]
no member user-profile-name
Context
[Tree] (config>system>security>user>console member)
Full Context
configure system security user console member
Description
This command is used to associate the user with a local command authorization profile.
A user can be associated with up to eight profiles.
When a user is a member of multiple profiles, profiles are evaluated in the order that they are configured. Evaluation stops if there is a match, or when the default action of the a profile is deny-all, permit-all or read-only-all. When the profile default action is none and if no match conditions are met in the profile, the next profile is evaluated. When the default action of the last profile is none and no explicit match is found, the command is denied.
The no form of this command removes the association between the user and the profile.
Default
member default
Parameters
- user-profile-name
-
Specifies up to eight user profile names, up to 32 characters.
Platforms
7705 SAR Gen 2
member
Syntax
[no] member interface-name
Context
[Tree] (config>router>isis>link-group>level member)
Full Context
configure router isis link-group level member
Description
This command adds or removes a link to the associated link-group. The interface name should already exist before it is added to a link-group.
The no form of this command removes the specified interface from the associated link-group.
Parameters
- interface-name
-
Specifies the name of the interface to be added or removed from the associated link-group.
Platforms
7705 SAR Gen 2
member-pool
member-pool
Syntax
member-pool name
no member-pool
Context
[Tree] (config>isa>tunnel-grp member-pool)
Full Context
configure isa tunnel-group member-pool
Description
This command associates the tunnel group with a tunnel member pool. This tunnel group is used as the designated standby in an N:M IPsec redundancy configuration.
The no form of this command removes the tunnel member pool from the configuration.
Parameters
- name
-
Specifies the name of the member pool, up to 32 characters.
Platforms
7705 SAR Gen 2
members
members
Syntax
[no] members comm-id [comm-id]
Context
[Tree] (config>router>policy-options>community members)
Full Context
configure router policy-options community members
Description
This command adds members to a route policy community list to use in route policy entries.
Each member of a community list is a standard, extended, or large community value or a regular expression that potentially matches many community values. A regular expression incorporates terms and operators that use the terms. An individual numerical digit is an elementary term in the community regular expression. More complex terms can be built from elementary terms. The following are key operators supported by SR OS:
-
.
-
*
-
?
-
{n}
-
{m,n}
-
{m, }
To reverse the match criteria when specifying a list of ranges or single values using square brackets, use the non-match operator (^) before the elements within the square brackets.
The no version of this command deletes route policy community members.
Parameters
- comm-id
-
Specifies a BGP community value, up to 72 characters. A community ID can be specified in different forms.
Platforms
7705 SAR Gen 2
memory-use-alarm
memory-use-alarm
Syntax
memory-use-alarm rising-threshold threshold [falling-threshold threshold] interval seconds [rmon-event-type] [startup-alarm alarm-type]
no memory-use-alarm
Context
[Tree] (config>system>thresholds memory-use-alarm)
Full Context
configure system thresholds memory-use-alarm
Description
The memory thresholds are based on monitoring the TIMETRA-SYSTEM-MIB sgiMemoryUsed object. This object contains the amount of memory currently used by the system. The severity level is Alarm. The absolute sample type method is used.
The no form of this command removes the configured memory threshold warning.
Parameters
- rising-threshold threshold
-
Specifies a threshold for the sampled statistic. When the current sampled value is greater than or equal to this threshold, and the value at the last sampling interval was less than this threshold, a single threshold crossing event will be generated. A single threshold crossing event will also be generated if the first sample taken is greater than or equal to this threshold and the associated startup-alarm is equal to rising or either.
After a rising threshold crossing event is generated, another such event will not be generated until the sampled value falls below this threshold and reaches less than or equal the falling-threshold value.
The threshold value represents units in bytes.
- falling-threshold threshold
-
Specifies a threshold for the sampled statistic. When the current sampled value is less than or equal to this threshold, and the value at the last sampling interval was greater than this threshold, a single threshold crossing event will be generated. A single threshold crossing event will also be generated if the first sample taken is less than or equal to this threshold and the associated startup-alarm is equal to falling or either.
After a falling threshold crossing event is generated, another such event will not be generated until the sampled value rises above this threshold and reaches greater than or equal the rising-threshold value.
The threshold value represents units in bytes.
- seconds
-
Specifies the polling period over which the data is sampled and compared with the rising and falling thresholds.
The threshold value represents units in bytes.
- rmon-event-type
-
Specifies the type of notification action to be taken when this event occurs.
- alarm-type
-
Specifies the alarm that may be sent when this alarm is first created. If the first sample is greater than or equal to the rising threshold value and startup-alarm is equal to rising or either, then a single rising threshold crossing event is generated. If the first sample is less than or equal to the falling threshold value and startup-alarm is equal to falling or either, a single falling threshold crossing event is generated.
Platforms
7705 SAR Gen 2
memory-use-warn
memory-use-warn
Syntax
memory-use-warn rising-threshold threshold [falling-threshold threshold] interval seconds [rmon-event-type] [startup-alarm alarm-type]
no memory-use-warn
Context
[Tree] (config>system>thresholds memory-use-warn)
Full Context
configure system thresholds memory-use-warn
Description
The memory thresholds are based on monitoring MemoryUsed object. This object contains the amount of memory currently used by the system. The severity level is Alarm.
The absolute sample type method is used.
The no form of this command removes the configured compact flash threshold warning.
Parameters
- rising-threshold threshold
-
Specifies a threshold for the sampled statistic. When the current sampled value is greater than or equal to this threshold, and the value at the last sampling interval was less than this threshold, a single threshold crossing event will be generated. A single threshold crossing event will also be generated if the first sample taken is greater than or equal to this threshold and the associated startup-alarm is equal to rising or either.
After a rising threshold crossing event is generated, another such event will not be generated until the sampled value falls below this threshold and reaches less than or equal the falling-threshold value.
The threshold value represents units in bytes.
- falling-threshold threshold
-
Specifies a threshold for the sampled statistic. When the current sampled value is less than or equal to this threshold, and the value at the last sampling interval was greater than this threshold, a single threshold crossing event will be generated. A single threshold crossing event will also be generated if the first sample taken is less than or equal to this threshold and the associated startup-alarm is equal to falling or either.
After a falling threshold crossing event is generated, another such event will not be generated until the sampled value rises above this threshold and reaches greater than or equal the rising-threshold value.
The threshold value represents units in bytes.
- seconds
-
Specifies the polling period over which the data is sampled and compared with the rising and falling thresholds.
- rmon-event-type
-
Specifies the type of notification action to be taken when this event occurs.
- startup-alarm alarm-type
-
Specifies the alarm that may be sent when this alarm is first created. If the first sample is greater than or equal to the rising threshold value and startup-alarm is equal to rising or either, then a single rising threshold crossing event is generated. If the first sample is less than or equal to the falling threshold value and startup-alarm is equal to falling or either, a single falling threshold crossing event is generated.
Platforms
7705 SAR Gen 2
mesh-group
mesh-group
Syntax
mesh-group {value | blocked}
no mesh-group
Context
[Tree] (config>service>vprn>isis>if mesh-group)
Full Context
configure service vprn isis interface mesh-group
Description
This command assigns an interface to a mesh group. Mesh groups limit the amount of flooding that occurs when a new or changed LSP is advertised throughout an area.
All routers in a mesh group should be fully meshed. When LSPs need to be flooded, only a single copy is received rather than a copy per neighbor.
To create a mesh group, configure the same mesh group value for each interface that is part of the mesh group. All routers must have the same mesh group value configured for all interfaces that are part of the mesh group.
To prevent an interface from flooding LSPs, the optional blocked parameter can be specified. Configure mesh groups carefully. It is easy to create isolated islands that do not receive updates as (other) links fail.
The no form of this command removes the interface from the mesh group. The interface does not belong to a mesh group.
Default
no mesh-group
Parameters
- value
-
Specifies a unique decimal integer value distinguishes this mesh group from other mesh groups on this or any other router that is part of this mesh group.
- blocked
-
Prevents an interface from flooding LSPs.
Platforms
7705 SAR Gen 2
mesh-group
Syntax
mesh-group {value | blocked}
no mesh-group
Context
[Tree] (config>router>isis>interface mesh-group)
Full Context
configure router isis interface mesh-group
Description
This command assigns an interface to a mesh group. Mesh groups limit the amount of flooding that occurs when a new or changed LSP is advertised throughout an area.
All routers in a mesh group should be fully meshed. When LSPs need to be flooded, only a single copy is received rather than a copy per neighbor.
To create a mesh group, configure the same mesh group value for each interface that is part of the mesh group. All routers must have the same mesh group value configured for all interfaces that are part of the mesh group.
To prevent an interface from flooding LSPs, the optional blocked parameter can be specified. Configure mesh groups carefully to avoid creating isolated islands that do not receive updates as (other) links fail.
The no form of this command removes the interface from the mesh group.
Parameters
- value
-
Specifies the unique decimal integer value that distinguishes this mesh group from other mesh groups on this or any other router that is part of this mesh group.
- blocked
-
Prevents an interface from flooding LSPs.
Platforms
7705 SAR Gen 2
mesh-sdp
mesh-sdp
Syntax
mesh-sdp sdp-id[:vc-id] [vc-type {ether | vlan}] [create]
mesh-sdp sdp-id[:vc-id] [vc-type {ether | vlan}] [create] leaf-ac
mesh-sdp sdp-id[:vc-id] [vc-type {ether | vlan}] [create] root-leaf-tag
no mesh-sdp sdp-id[:vc-id]
Context
[Tree] (config>service>vpls mesh-sdp)
Full Context
configure service vpls mesh-sdp
Description
This command binds a VPLS service to an existing service destination point (SDP).
Mesh SDPs bound to a service are logically treated like a single bridge "port” for flooded traffic where flooded traffic received on any mesh SDP on the service is replicated to other "ports” (spoke SDPs and SAPs) and not transmitted on any mesh SDPs.
This command creates a binding between a service and an SDP. The SDP has an operational state which determines the operational state of the SDP within the service. For example, if the SDP is administratively or operationally down, the SDP for the service is down.
The SDP must already be defined in the config>service>sdp context in order to associate the SDP with an Epipe or VPLS service. If the sdp sdp-id is not already configured, an error message is generated. If the sdp-id does exist, a binding between that sdp-id and the service is created.
SDPs must be explicitly associated and bound to a service. If an SDP is not bound to a service, no far-end router devices can participate in the service.
The no form of this command removes the SDP binding from the service. The SDP configuration is not affected; only the binding of the SDP to a service. Once removed, no packets are forwarded to the far-end router.
Default
No sdp-id is bound to a service.
Parameters
- sdp-id
-
Specifies an SDP identifier.
- vc-id
-
Specifies a virtual circuit identifier. This value is used to validate the VC ID portion of each mesh SDP binding defined in the service. The default value of this object is equal to the service ID. Any value may be used for the vc-id when there is no existing mesh SDP within the service; if a mesh SDP exists then all other mesh SDPs in the service must be configured with the same vc-id.
- vc-type
-
Specifies to override the default VC type signaled for the spoke or mesh binding to the far end of the SDP. The VC type is a 15 bit-quantity containing a value which represents the type of VC. The actual signaling of the VC type depends on the signaling parameter defined for the SDP. If signaling is disabled, the vc-type command can still be used to define the dot1q value expected by the far-end provider equipment. A change of the binding’s VC type causes the binding to signal the new VC type to the far end when signaling is enabled.
VC types are derived according to IETF draft-martini-l2circuit-trans-mpls.
The VC type value for Ethernet is 0x0005.
The VC type value for an Ethernet VLAN is 0x0004.
- ether
-
Defines the VC type as Ethernet. The vlan keyword is mutually exclusive. When the VC type is not defined then the default is Ethernet for spoke SDP bindings. Defining Ethernet is the same as executing no vc-type and restores the default VC type for the spoke SDP binding (hex 5).
- vlan
-
Defines the VC type as VLAN. The top VLAN tag, if a VLAN tag is present, is stripped from traffic received on the pseudowire, and a vlan-tag is inserted when forwarding into the pseudowire. The ethernet and vlan keywords are mutually exclusive. When the VC type is not defined then the default is Ethernet for mesh SDP bindings.
Note:The system expects a symmetrical configuration with its peer, specifically it expects to remove the same number of VLAN tags from received traffic as it adds to transmitted traffic. As some of the related configuration parameters are local and not communicated in the signaling plane, an asymmetrical behavior cannot always be detected and so cannot be blocked. Consequently, protocol extractions will not necessarily function for asymmetrical configurations as they would with a symmetrical configurations resulting in an unexpected operation.
- root-leaf-tag
-
Specifies a tagging mesh SDP under an E-Tree VPLS. When a tag SDP binding is required, it is created with a root-leaf-tag flag. Only VLAN tag SDP bindings are supported. The VLAN type must be set to VC VLAN type. The root-leaf-tag parameter indicates this SDP binding is a tag SDP that uses a default VID 1 for root and 2 for leaf. The SDP binding tags egress E-Tree traffic with root and leaf VIDs as appropriate. Root and leaf VIDs are only significant between peering VPLS but the values must be consistent on each end. On ingress a tag SDP binding removes the VID tag on the interface between VPLS in the same E-Tree service. The tag SDP receives root tagged traffic and marks the traffic with a root indication internally. This option is not available on BGP EVPN-enabled E-Tree services.
- leaf-ac
-
Specifies an access (AC) mesh SDP binding under a E-Tree VPLS as a leaf access (AC) SDP. The default E-Tree SDP type is a root AC if leaf-ac or root-leaf-tag is not specified at SDP binding creation. This option is only available when the VPLS is designated as an E-Tree VPLS. BGP EVPN-enabled E-Tree VPLS services support the leaf-ac option.
- create
-
Keyword used to create the mesh SDP. The create keyword requirement can be enabled or disabled in the environment>create context.
Platforms
7705 SAR Gen 2
mesh-sdp-binding
mesh-sdp-binding
Syntax
[no] mesh-sdp-binding
Context
[Tree] (config>service>vpls>site mesh-sdp-binding)
Full Context
configure service vpls site mesh-sdp-binding
Description
This command enables applications to all mesh SDPs.
The no form of reverts the default.
Default
no mesh-sdp-binding
Platforms
7705 SAR Gen 2
message
message
Syntax
message {eq | neq} pattern pattern [regexp]
no message
Context
[Tree] (config>service>vprn>log>filter>entry>match message)
Full Context
configure service vprn log filter entry match message
Description
This command adds system messages as a match criterion.
The no form of this command removes messages as a match criterion.
Parameters
- eq
-
Specifies if the matching criteria should be equal to the specified value.
- neq
-
Specifies if the matching criteria should not be equal to the specified value.
- pattern
-
Specifies a message, up to 400 characters, to be used in the match criteria.
- regexp
-
Specifies the type of string comparison to use to determine if the log event matches the value of message command parameters. When the regexp keyword is not specified, the default matching algorithm used is a basic substring match.
Platforms
7705 SAR Gen 2
message
Syntax
message {eq | neq} pattern pattern [ regexp]
no message
Context
[Tree] (config>log>filter>entry>match message)
Full Context
configure log filter entry match message
Description
This command adds system messages as a match criterion.
The no form of this command removes messages as a match criterion.
Parameters
- eq
-
Determines if the matching criteria should be equal to the specified value.
- neq
-
Determines if the matching criteria should not be equal to the specified value.
- pattern
-
Specifies a message up to 400 characters in length to be used in the match criteria.
- regexp
-
Specifies the type of string comparison to use to determine if the log event matches the value of message command parameters. When the regexp keyword is not specified, the default matching algorithm used is a basic substring match.
Platforms
7705 SAR Gen 2
message-count
message-count
Syntax
message-count count
Context
[Tree] (config>service>ies>if>ipsec>ipsec-tunnel>icmp6-gen>pkt-too-big message-count)
[Tree] (config>service>vprn>if>sap>ipsec-tun>icmp6-gen>pkt-too-big message-count)
[Tree] (config>ipsec>tnl-temp>icmp6-gen>pkt-too-big message-count)
[Tree] (config>service>vprn>if>ipsec>ipsec-tunnel>icmp6-gen>pkt-too-big message-count)
Full Context
configure service ies interface ipsec ipsec-tunnel icmp6-generation pkt-too-big message-count
configure service vprn interface sap ipsec-tunnel icmp6-generation pkt-too-big message-count
configure ipsec tunnel-template icmp6-generation pkt-too-big message-count
configure service vprn interface ipsec ipsec-tunnel icmp6-generation pkt-too-big message-count
Description
This command configures the maximum number of ICMPv6 messages that can be sent during the configured interval.
Parameters
- count
-
Specifies the maximum number of ICMPv6 messages that can be sent during the configured interval
Platforms
7705 SAR Gen 2
message-count
Syntax
message-count number
Context
[Tree] (config>router>if>ipsec>ipsec-tunnel>icmp-gen>frag-required message-count)
[Tree] (config>service>vprn>if>ipsec>ipsec-tunnel>icmp-gen>frag-required message-count)
[Tree] (config>ipsec>tnl-temp>icmp-gen>frag-required message-count)
[Tree] (config>service>ies>if>ipsec>ipsec-tunnel>icmp-gen>frag-required message-count)
[Tree] (config>service>vprn>if>sap>ip-tunnel>icmp-gen>frag-required message-count)
[Tree] (config>service>vprn>if>sap>ipsec-tunnel>icmp-gen>frag-required message-count)
Full Context
configure router interface ipsec ipsec-tunnel icmp-generation frag-required message-count
configure service vprn interface ipsec ipsec-tunnel icmp-generation frag-required message-count
configure ipsec tunnel-template icmp-generation frag-required message-count
configure service ies interface ipsec ipsec-tunnel icmp-generation frag-required message-count
configure service vprn interface sap ip-tunnel icmp-generation frag-required message-count
configure service vprn interface sap ipsec-tunnel icmp-generation frag-required message-count
Description
This command configures the maximum number of ICMP Destination Unreachable "fragmentation needed and DF set" messages (type 3, code 4) that can be sent during the period specified by the interval seconds command.
Default
message-count 100
Parameters
- number
-
Specifies the number of ICMP Destination Unreachable "fragmentation needed and DF set" messages that are transmitted within the interval seconds command time.
Platforms
7705 SAR Gen 2
message-digest-key
message-digest-key
Syntax
message-digest-key keyid md5 [ key | hash-key] [hash | hash2 | custom]
no message-digest-key keyid
Context
[Tree] (config>service>vprn>ospf>area>sham-link message-digest-key)
[Tree] (config>service>vprn>ospf>area>if message-digest-key)
[Tree] (config>service>vprn>ospf>area>virtual-link message-digest-key)
Full Context
configure service vprn ospf area sham-link message-digest-key
configure service vprn ospf area interface message-digest-key
configure service vprn ospf area virtual-link message-digest-key
Description
This command configures a message digest key when MD5 authentication is enabled on the interface, virtual-link or sham-link. Multiple message digest keys can be configured.
This command is not valid in the OSPF3 context.
The no form of this command removes the message digest key identified by the key-id.
Default
No message digest keys are defined.
Parameters
- keyid
-
Specifies the key ID. The keyid is expressed as a decimal integer.
- md5 key
-
Specifies the MD5 key. The key can be any alphanumeric string up to 16 characters in length.
- md5 hash-key
-
Specifies the MD5 hash key. The key can be any combination of ASCII characters up to 32 characters in length (encrypted). If spaces are used in the string, enclose the entire string in quotation marks (" ”).
This is useful when a user must configure the parameter, but, for security purposes, the actual unencrypted key value is not provided.
- hash
-
Specifies the key is entered in an encrypted form. If the hash parameter is not used, the key is assumed to be in a non-encrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash parameter specified.
- hash2
-
Specifies the key is entered in a more complex encrypted form that involves more variables than the key value alone, meaning that the hash2 encrypted variable cannot be copied and pasted. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- custom
-
Specifies the custom encryption to management interface.
Platforms
7705 SAR Gen 2
message-digest-key
Syntax
message-digest-key key-id md5 [key | hash-key | hash2-key] [hash | hash2 | custom]
no message-digest-key key-id
Context
[Tree] (config>router>ospf>area>interface message-digest-key)
[Tree] (config>router>ospf>area>virtual-link message-digest-key)
Full Context
configure router ospf area interface message-digest-key
configure router ospf area virtual-link message-digest-key
Description
This command configures a message digest key when MD5 authentication is enabled on the interface. Multiple message digest keys can be configured.
The no form of this command removes the message digest key identified by the key-id.
By default, no message keys are defined.
Parameters
- key-id
-
Specifies the key ID. The keyid is expressed as a decimal integer.
- key
-
Specifies the MD5 key. The key can be any alphanumeric string up to 16 characters in length.
- hash-key | hash2-key
-
Specifies the MD5 hash or hash2 key. the hash key. The key can be any combination of ASCII characters up to 32 (hash1-key) or 55 (hash2-key) characters in length (encrypted). If spaces are used in the string, enclose the entire string in quotation marks (" ”).
This is useful when a user must configure the parameter, but, for security purposes, the actual unencrypted key value is not provided.
- hash
-
Specifies the key is entered in an encrypted form. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- hash2
-
Specifies the key is entered in a more complex encrypted form that involves more variables than the key value alone, meaning that the hash2 encrypted variable cannot be copied and pasted. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- custom
-
Specifies the custom encryption to management interface.
Platforms
7705 SAR Gen 2
message-fast-tx
message-fast-tx
Syntax
message-fast-tx time
no message-fast-tx
Context
[Tree] (config>system>lldp message-fast-tx)
Full Context
configure system lldp message-fast-tx
Description
This command configures the duration of the fast transmission period.
Default
no message-fast-tx
Parameters
- time
-
Specifies the fast transmission period in seconds.
Platforms
7705 SAR Gen 2
message-fast-tx-init
message-fast-tx-init
Syntax
message-fast-tx-init count
no message-fast-tx-init
Context
[Tree] (config>system>lldp message-fast-tx-init)
Full Context
configure system lldp message-fast-tx-init
Description
This command configures the number of LLDPDUs to send during the fast transmission period.
Default
no message-fast-tx-init
Parameters
- count
-
Specifies the number of LLDPDUs to send during the fast transmission period.
Platforms
7705 SAR Gen 2
message-interval
message-interval
Syntax
message-interval {[seconds] [milliseconds milliseconds]}
no message-interval
Context
[Tree] (config>service>ies>if>ipv6>vrrp message-interval)
Full Context
configure service ies interface ipv6 vrrp message-interval
Description
This command sets the advertisement timer and indirectly sets the master down timer on the virtual router instance. The message-interval setting must be the same for all virtual routers participating as a virtual router. Any VRRP advertisement message received with an Advertisement Interval field different than the virtual router instance configured message-interval value will be silently discarded.
The message-interval command is available in both non-owner and owner vrrp virtual-router-id nodal contexts. If the message-interval command is not executed, the default message interval of 1 second will be used.
The no form of this command restores the default message interval value of 1 second to the virtual router instance.
Default
message-interval 1
Parameters
- seconds
-
The number of seconds that will transpire before the advertisement timer expires.
- milliseconds milliseconds
-
Specifies the time interval, in milliseconds, between sending advertisement messages.
Platforms
7705 SAR Gen 2
message-interval
Syntax
message-interval {[seconds] [milliseconds milliseconds]}
no message-interval
Context
[Tree] (config>service>ies>if>vrrp message-interval)
Full Context
configure service ies interface vrrp message-interval
Description
This command sets the advertisement timer and indirectly sets the master down timer on the virtual router instance. The message-interval setting must be the same for all virtual routers participating as a virtual router. Any VRRP advertisement message received with an Advertisement Interval field different than the virtual router instance configured message-interval value will be silently discarded.
The message-interval command is available in both non-owner and owner vrrp virtual-router-id nodal contexts. If the message-interval command is not executed, the default message interval of 1 second will be used.
The no form of this command restores the default message interval value of 1 second to the virtual router instance.
Parameters
- seconds
-
The number of seconds that will transpire before the advertisement timer expires.
- milliseconds milliseconds
-
Specifies the time interval, in milliseconds, between sending advertisement messages. This parameter is not supported on non-redundant chassis.
Platforms
7705 SAR Gen 2
message-interval
Syntax
message-interval {[seconds] [milliseconds milliseconds]}
no message-interval
Context
[Tree] (config>service>vprn>if>ipv6>vrrp message-interval)
Full Context
configure service vprn interface ipv6 vrrp message-interval
Description
This command sets the advertisement timer and indirectly sets the master down timer on the virtual router instance. The message-interval setting must be the same for all virtual routers participating as a virtual router. Any VRRP advertisement message received with an Advertisement Interval field different than the virtual router instance configured message-interval value will be silently discarded.
The message-interval command is available in both non-owner and owner vrrp virtual-router-id nodal contexts. If the message-interval command is not executed, the default message interval of 1 second will be used.
The no form of this command restores the default message interval value of 1 second to the virtual router instance.
Parameters
- seconds
-
The number of seconds that will transpire before the advertisement timer expires.
- milliseconds milliseconds
-
Specifies the time interval, in milliseconds, between sending advertisement messages. This parameter is not supported on single-slot chassis.
Platforms
7705 SAR Gen 2
message-interval
Syntax
message-interval {[seconds] [milliseconds milliseconds]}
no message-interval
Context
[Tree] (config>router>if>vrrp message-interval)
[Tree] (config>router>if>ipv6>vrrp message-interval)
Full Context
configure router interface vrrp message-interval
configure router interface ipv6 vrrp message-interval
Description
This command configures the administrative advertisement message timer used by the master virtual router instance to send VRRP advertisement messages and to derive the master down timer as backup.
For an owner virtual router instance, the administrative advertisement timer directly sets the operational advertisement timer and indirectly sets the master down timer for the virtual router instance.
Non-owner virtual router instances usage of the message-interval setting is dependent on the state of the virtual router (master or backup) and the state of the master-int-inherit parameter.
-
When a non-owner is operating as master for the virtual router, the configured message-interval is used as the operational advertisement timer similar to an owner virtual router instance. The master-int-inherit command has no effect when operating as master.
-
When a non-owner is in the backup state with master-int-inherit disabled, the configured message-interval value is used to match the incoming VRRP advertisement message advertisement interval field. If the locally configured message interval does not match the advertisement interval field, the VRRP advertisement is discarded.
-
When a non-owner is in the backup state with master-int-inherit enabled, the configured message-interval is ignored. The master down timer is indirectly derived from the incoming VRRP advertisement message advertisement interval field value.
VRRP advertisements messages that are fragmented, or contain IP options (IPv4), or contain extension headers (IPv6) require a longer message interval to be configured.
The in-use value of the message interval is used to derive the master down timer to be used when the virtual router is operating in backup mode based on the following formula:
(3x (in-use message interval) + skew time)
The skew time portion is used to slow down virtual routers with relatively low priority values when competing in the master election process.
The command is available in both non-owner and owner vrrp nodal contexts.
By default, a message-interval of 1 second is used.
The no form of the command reverts to the default value.
Default
message-interval 1 — Advertisement timer set to 1 second.
Parameters
- seconds
-
The number of seconds that will transpire before the advertisement timer expires expressed as a decimal integer.
- milliseconds
-
Specifies the time interval, in milliseconds, between sending advertisement messages.
Platforms
7705 SAR Gen 2
message-length
message-length
Syntax
message-length message-length
no message-length
Context
[Tree] (config>service>sdp>keep-alive message-length)
Full Context
configure service sdp keep-alive message-length
Description
This command configures the SDP monitoring keepalive request message length transmitted.
The no form of this command reverts the message-length octets value to the default setting.
Default
no message-length — The message length should be equal to the SDP’s operating path MTU as configured in the config>service>sdp path-mtu command. If the default size is overridden, the actual size used will be the smaller of the operational SDP ID Path MTU and the size specified.
Parameters
- message-length
-
Specifies the size of the keepalive request messages in octets, expressed as a decimal integer. The size keyword overrides the default keepalive message size.
Platforms
7705 SAR Gen 2
message-severity-level
message-severity-level
Syntax
message-severity-level
Context
[Tree] (config>system>management-interface>cli>md-cli>environment message-severity-level)
Full Context
configure system management-interface cli md-cli environment message-severity-level
Description
This command configures the message severity level.
Platforms
7705 SAR Gen 2
message-size
message-size
Syntax
message-size max-num-of-routes
no message-size
Context
[Tree] (config>service>vprn>ripng>group>neighbor message-size)
[Tree] (config>service>vprn>ripng>group message-size)
[Tree] (config>service>vprn>rip>group message-size)
[Tree] (config>service>vprn>rip message-size)
[Tree] (config>service>vprn>rip>group>neighbor message-size)
[Tree] (config>service>vprn>ripng message-size)
Full Context
configure service vprn ripng group neighbor message-size
configure service vprn ripng group message-size
configure service vprn rip group message-size
configure service vprn rip message-size
configure service vprn rip group neighbor message-size
configure service vprn ripng message-size
Description
This command sets the maximum number of routes per RIP update message.
The no form of this command resets the maximum number of routes back to the default of 25.
Default
no message-size
Parameters
- size
-
An Integer.
Platforms
7705 SAR Gen 2
message-size
Syntax
message-size max-num-of-routes
no message-size
Context
[Tree] (config>router>rip message-size)
[Tree] (config>router>rip>group message-size)
[Tree] (config>router>ripng>group>neighbor message-size)
[Tree] (config>router>ripng message-size)
[Tree] (config>router>rip>group>neighbor message-size)
[Tree] (config>router>ripng>group message-size)
Full Context
configure router rip message-size
configure router rip group message-size
configure router ripng group neighbor message-size
configure router ripng message-size
configure router rip group neighbor message-size
configure router ripng group message-size
Description
This command configures the maximum number of routes per RIP update message.
The no form of the command reverts to the default value.
Default
message-size 25
Parameters
- max-num-of-routes
-
The maximum number of RIP routes per RIP update message expressed as a decimal integer.
Platforms
7705 SAR Gen 2
messages
messages
Syntax
[no] messages
Context
[Tree] (debug>router>ldp>if>event messages)
[Tree] (debug>router>ldp>peer>event messages)
Full Context
debug router ldp interface event messages
debug router ldp peer event messages
Description
This command displays specific information (for example, message type, source, and destination) regarding LDP messages sent to and received from LDP peers.
The no form of the command disables debugging output for LDP messages.
Platforms
7705 SAR Gen 2
metric
metric
Syntax
metric metric-value
no metric [metric-value]
Context
[Tree] (config>service>vprn>static-route-entry>ipsec-tunnel metric)
[Tree] (config>service>vprn>static-route-entry>black-hole metric)
[Tree] (config>service>vprn>static-route-entry>next-hop metric)
[Tree] (config>service>vprn>static-route-entry>grt metric)
[Tree] (config>service>vprn>static-route-entry>indirect metric)
Full Context
configure service vprn static-route-entry ipsec-tunnel metric
configure service vprn static-route-entry black-hole metric
configure service vprn static-route-entry next-hop metric
configure service vprn static-route-entry grt metric
configure service vprn static-route-entry indirect metric
Description
This command specifies the cost metric for the static route, expressed as a decimal integer. This value is used when importing the static route into other protocols such as OSPF. When the metric is configured as 0 then the metric configured in OSPF, default-import-metric, applies. When modifying the metric of an existing static route, the preference will not change unless specified. This value is also used to determine which static route to install in the forwarding table.
If there are multiple static routes with the same preference but different metrics then the lower cost (metric) route will be installed.
The no form of this command returns the metric to the default value
Default
metric 1
Parameters
- metric-value
-
Specifies the cost metric value.
Platforms
7705 SAR Gen 2
metric
Syntax
metric metric
no metric
Context
[Tree] (config>service>vprn>isis>if>level metric)
Full Context
configure service vprn isis interface level metric
Description
This command configures the metric used for the level on the interface.
In order to calculate the lowest cost to reach a given destination, each configured level on each interface must have a cost. The costs for each level on an interface may be different.
If the metric is not configured, the default of 10 is used unless reference bandwidth is configured.
The no form of this command reverts to the default value.
Default
no metric
Parameters
- metric
-
The metric assigned for this level on this interface.
Platforms
7705 SAR Gen 2
metric
Syntax
metric metric
no metric
Context
[Tree] (config>service>vprn>ospf3>area>if metric)
[Tree] (config>service>vprn>ospf>area>sham-link metric)
[Tree] (config>service>vprn>ospf>area>if metric)
Full Context
configure service vprn ospf3 area interface metric
configure service vprn ospf area sham-link metric
configure service vprn ospf area interface metric
Description
This command configures an explicit route cost metric for the OSPF interface that overrides the metrics calculated based on the speed of the underlying link.
The no form of this command deletes the manually configured interface metric, so the interface uses the computed metric based on the reference-bandwidth command setting and the speed of the underlying link.
Default
no metric
Parameters
- metric
-
The metric to be applied to the interface expressed as a decimal integer.
Platforms
7705 SAR Gen 2
metric
Syntax
metric metric
no metric
Context
[Tree] (config>router>mpls>static-lsp metric)
[Tree] (config>router>mpls>lsp-template metric)
[Tree] (config>router>mpls>lsp metric)
Full Context
configure router mpls static-lsp metric
configure router mpls lsp-template metric
configure router mpls lsp metric
Description
This command allows the user to override the LSP operational metric with a constant administrative value that will not change regardless of the actual path the LSP is using over its lifetime.
The LSP operational metric will match the metric the active path of this LSP is using at any given time. For a CSPF LSP, this metric represents the cumulative IGP metric of all the links the active path is using. If CSPF for this LSP is configured to use the TE metric, the LSP operational metric is set to the maximum value. For a non-CSPF LSP, the operational metric is the shortest IGP cost to the destination of the LSP.
The LSP operational metric is used by some applications to select an LSP among a set of LSPs that are destined to the same egress router. The LSP with the lowest operational metric will be selected. If more than one LSP with the same lowest LSP metric exists, the LSP with the lowest tunnel index will be selected. The configuration of a constant metric by the user will make sure the LSP always maintains its preference in this selection regardless of the path it is using at any given time. Applications that use the LSP operational metric include LDP-over-RSVP, VPRN auto-bind, and IGP, BGP and static route shortcuts.
The no form of this command disables the administrative LSP metric and reverts to the default setting in which the metric value will represent the LSP metric returned by MPLS. The same behavior is obtained if the user entered a metric of value zero (0).
Default
no metric. The LSP operational metric defaults to the metric returned by MPLS.
Parameters
- metric
-
Specifies the integer value which specifies the value of the LSP administrative metric. A value of zero command reverts to the default setting and disables the administrative LSP metric.
Platforms
7705 SAR Gen 2
metric
Syntax
metric metric
no metric [metric]
Context
[Tree] (config>router>static-route-entry>black-hole metric)
[Tree] (config>router>static-route-entry>indirect metric)
[Tree] (config>router>static-route-entry>next-hop metric)
Full Context
configure router static-route-entry black-hole metric
configure router static-route-entry indirect metric
configure router static-route-entry next-hop metric
Description
This command specifies the cost metric for the static route, expressed as a decimal integer. This value is used when importing the static route into other protocols such as OSPF. When the metric is configured as 0 then the metric configured in OSPF, default-import-metric, applies. When modifying the metric of an existing static route, the preference will not change unless specified. This value is also used to determine which static route to install in the forwarding table.
If there are multiple static routes with the same preference but different metrics then the lower cost (metric) route will be installed.
The no form of this command returns the metric to the default value
Default
metric 1
Parameters
- metric
-
Specifies the cost metric value.
Platforms
7705 SAR Gen 2
metric
Syntax
metric metric
no metric
Context
[Tree] (config>service>sdp metric)
Full Context
configure service sdp metric
Description
This command specifies the metric to be used within the tunnel table manager for decision making purposes. When multiple SDPs going to the same destination exist, this value is used as a tie-breaker by tunnel table manager users such as MP-BGP to select the route with the lower value.
Parameters
- metric
-
Specifies the SDP metric.
Platforms
7705 SAR Gen 2
metric
Syntax
metric metric
no metric
Context
[Tree] (config>router>isis>if>level metric)
Full Context
configure router isis interface level metric
Description
This command configures the metric used for the level on the interface.
In order to calculate the lowest cost to reach a given destination, each configured level on each interface must have a cost. The costs for each level on an interface may be different.
If the metric is not configured, the default of 10 is used unless reference bandwidth is configured.
The no form of this command reverts to the default value.
Default
metric 10
Parameters
- metric
-
Specifies the metric assigned for this level on this interface.
Platforms
7705 SAR Gen 2
metric
Syntax
metric metric
no metric
Context
[Tree] (config>router>ospf>area>interface metric)
[Tree] (config>router>ospf3>area>interface metric)
Full Context
configure router ospf area interface metric
configure router ospf3 area interface metric
Description
This command configures an explicit route cost metric for the OSPF interface that overrides the metrics calculated based on the speed of the underlying link.
The no form of this command deletes the manually configured interface metric, so the interface uses the computed metric based on the reference-bandwidth command setting and the speed of the underlying link.
Default
no metric
Parameters
- metric
-
Specifies the metric to be applied to the interface expressed as a decimal integer.
Platforms
7705 SAR Gen 2
metric
Syntax
metric metric [equal | or-higher | or-lower]
no metric
Context
[Tree] (config>router>policy-options>policy-statement>entry>from metric)
Full Context
configure router policy-options policy-statement entry from metric
Description
This command matches BGP routes based on local preference (the value in the MULTI_EXIT_DISC attribute).
If no comparison qualifiers are present (equal, or-higher, or-lower), then equal is the implied default.
A non-BGP route does not match a policy entry if it contains the metric command. In addition, a BGP route without a MED attribute also does not match a policy entry if it contains a metric command.
Default
no metric
Parameters
- metric
-
Specifies the MED value.
- equal
-
Specifies that matched routes should have the same MED as the value specified.
- or-higher
-
Specifies that matched routes should have the same or a greater MED as the value specified.
- or-lower
-
Specifies that matched routes should have the same or a lower MED as the value specified.
Platforms
7705 SAR Gen 2
metric
Syntax
metric {add | subtract} metric
metric set [igp | metric-value]
no metric
Context
[Tree] (config>router>policy-options>policy-statement>entry>action metric)
[Tree] (config>router>policy-options>policy-statement>default-action metric)
Full Context
configure router policy-options policy-statement entry action metric
configure router policy-options policy-statement default-action metric
Description
In a BGP import or export policy, this command assigns a MED value to routes matched by the policy statement entry. The MED value may be set to a fixed value (overriding the received value), set to the routing table cost of the route used to resolve the next hop of the BGP route, or modified by adding or subtracting a fixed value offset.
The no form of this command removes the MED attribute from the matched routes.
Default
no metric
Parameters
- add
-
Specifies that an integer is added to any existing metric. If the result of the addition results in a number greater than 4294967295, the value 4294967295 is used.
- subtract
-
Specified integer is subtracted from any existing metric. If the result of the subtraction results in a number less than 0, the value of 0 is used.
- set
-
Specifies that integer replaces any existing metric.
- igp
-
Sets the MED value to the routing table cost of the route used to resolve the next hop of the BGP route.
- metric
-
Specifies the metric modifier expressed as a decimal integer.
Platforms
7705 SAR Gen 2
metric
Syntax
metric metric
Context
[Tree] (config>ipsec>tnl-temp>rev-route metric)
Full Context
configure ipsec tunnel-template reverse-route metric
Description
This command configures the metric for reverse routes. The system uses the metric when selecting a route to install in the route table.
Default
metric 0
Parameters
- metric
- Specifies the metric value for reverse routes.
Platforms
7705 SAR Gen 2
metric-in
metric-in
Syntax
metric-in metric
no metric-in
Context
[Tree] (config>service>vprn>ripng metric-in)
[Tree] (config>service>vprn>rip metric-in)
[Tree] (config>service>vprn>ripng>group>neighbor metric-in)
[Tree] (config>service>vprn>rip>group>neighbor metric-in)
[Tree] (config>service>vprn>rip>group metric-in)
[Tree] (config>service>vprn>ripng>group metric-in)
Full Context
configure service vprn ripng metric-in
configure service vprn rip metric-in
configure service vprn ripng group neighbor metric-in
configure service vprn rip group neighbor metric-in
configure service vprn rip group metric-in
configure service vprn ripng group metric-in
Description
This command sets the metric added to routes received from a RIP neighbor.
The no form of this command reverts the metric value back to the default.
Default
no metric-in
Parameters
- metric
-
The value added to the metric of routes received from a RIP neighbor, expressed as a decimal integer.
Platforms
7705 SAR Gen 2
metric-in
Syntax
metric-in metric
no metric-in
Context
[Tree] (config>router>ripng>group metric-in)
[Tree] (config>router>ripng metric-in)
[Tree] (config>router>rip metric-in)
[Tree] (config>router>rip>group metric-in)
[Tree] (config>router>rip>group>neighbor metric-in)
[Tree] (config>router>ripng>group>neighbor metric-in)
Full Context
configure router ripng group metric-in
configure router ripng metric-in
configure router rip metric-in
configure router rip group metric-in
configure router rip group neighbor metric-in
configure router ripng group neighbor metric-in
Description
This command configures the metric added to routes received from a RIP neighbor.
When applying an export policy to a RIP configuration, the policy overrides the metric values determined through calculations involving the metric-in and metric-out values.
The no form of the command reverts to the default value.
Default
metric-in 1
Parameters
- metric
-
Specifies the value added to the metric of routes received from a RIP neighbor expressed as a decimal integer.
Platforms
7705 SAR Gen 2
metric-out
metric-out
Syntax
metric-out metric
no metric-out
Context
[Tree] (config>service>vprn>rip>group metric-out)
[Tree] (config>service>vprn>rip>group>neighbor metric-out)
[Tree] (config>service>vprn>ripng>group metric-out)
[Tree] (config>service>vprn>ripng>group>neighbor metric-out)
[Tree] (config>service>vprn>rip metric-out)
[Tree] (config>service>vprn>ripng metric-out)
Full Context
configure service vprn rip group metric-out
configure service vprn rip group neighbor metric-out
configure service vprn ripng group metric-out
configure service vprn ripng group neighbor metric-out
configure service vprn rip metric-out
configure service vprn ripng metric-out
Description
This command sets the metric added to routes exported into RIP and advertised to RIP neighbors.
The no form of this command removes the command from the config and resets the metric-in value back to the default.
Default
no metric-out
Parameters
- metric
-
The value added to the metric for routes exported into RIP and advertised to RIP neighbors, expressed as a decimal integer.
Platforms
7705 SAR Gen 2
metric-out
Syntax
metric-out metric
no metric-out
Context
[Tree] (config>router>ripng>group>neighbor metric-out)
[Tree] (config>router>ripng metric-out)
[Tree] (config>router>rip>group>neighbor metric-out)
[Tree] (config>router>rip>group metric-out)
[Tree] (config>router>ripng>group metric-out)
[Tree] (config>router>rip metric-out)
Full Context
configure router ripng group neighbor metric-out
configure router ripng metric-out
configure router rip group neighbor metric-out
configure router rip group metric-out
configure router ripng group metric-out
configure router rip metric-out
Description
This command configures the metric assigned to routes exported into RIP and advertised to RIP neighbors.
When applying an export policy to a RIP configuration, the policy overrides the metric values determined through calculations involving the metric-in and metric-out values.
The no form of the command reverts to the default value.
Default
metric-out 1
Parameters
- metric
-
Specifies the value added to the metric for routes exported into RIP and advertised to RIP neighbors expressed as a decimal integer.
Platforms
7705 SAR Gen 2
metric-type
metric-type
Syntax
metric-type metric-type
no metric-type
Context
[Tree] (config>router>mpls>lsp-template metric-type)
[Tree] (config>router>mpls>lsp metric-type)
Full Context
configure router mpls lsp-template metric-type
configure router mpls lsp metric-type
Description
This command configures the link metric type used by the local CSPF or the PCE controller in the SR-TE LSP path computation.
The no form of this command returns the link metric type to its default value.
Default
metric-type igp
Parameters
- metric-type
-
Specifies the metric type for the LSP.
Platforms
7705 SAR Gen 2
metric-type
Syntax
metric-type {igp | te-metric | delay}
no metric-type
Context
[Tree] (config>router>fad>flex-algo metric-type)
Full Context
configure router flexible-algorithm-definitions flex-algo metric-type
Description
This command configures the type of metric for the flexible algorithm. The topology graph assumes that all links are configured with the correct metric type.
For example, if the flexible algorithm definition instructs the use of te-metric keyword, it is assumed that all links have te-metric configured. Links without the te-metric configuration are excluded from the flexible algorithm topology graph.
The no form of this command removes the configured metric type and sets it to its default value.
Default
metric-type igp
Parameters
- igp
-
Keyword to use the IGP metric for the flexible algorithm topology graph.
- te-metric
-
Keyword to use the TE metric for the flexible algorithm topology graph.
- delay
-
Keyword to use the delay metric for the flexible algorithm topology graph.
Platforms
7705 SAR Gen 2
mfib-allowed-mda-destinations
mfib-allowed-mda-destinations
Syntax
mfib-allowed-mda-destinations
Context
[Tree] (config>service>vpls>mesh-sdp>egress mfib-allowed-mda-destinations)
[Tree] (config>service>vpls>spoke-sdp>egress mfib-allowed-mda-destinations)
Full Context
configure service vpls mesh-sdp egress mfib-allowed-mda-destinations
configure service vpls spoke-sdp egress mfib-allowed-mda-destinations
Description
Commands in this context configure MFIB-allowed MDA destinations.
The allowed-mda-destinations node and the corresponding mda command are used on spoke and mesh SDP bindings to provide a list of MDA destinations in the chassis that are allowed as destinations for multicast streams represented by [*,g] and [s,g] multicast flooding records on the VPLS service. The MDA list only applies to IP multicast forwarding when IGMP snooping is enabled on the VPLS service. The MDA list has no effect on normal VPLS flooding such as broadcast, L2 multicast, unknown destinations or non-snooped IP multicast.
At the IGMP snooping level, a spoke or mesh SDP binding is included in the flooding domain for an IP multicast stream when it has either been defined as a multicast router port, received a IGMP query through the binding or has been associated with the multicast stream through an IGMP request by a host over the binding. Due to the dynamic nature of the way that a spoke or mesh SDP binding is associated with one or more egress network IP interfaces, the system treats the binding as appearing on all network ports. This causes all possible network destinations in the switch fabric to be included in the multicast streams flooding domain. The MDA destination list provides a simple mechanism that narrows the IP multicast switch fabric destinations for the spoke or mesh SDP binding.
If no MDAs are defined within the allowed-mda-destinations node, the system operates normally and will forward IP multicast flooded packets associated with the spoke or mesh SDP binding to all switch fabric taps containing network IP interfaces.
The MDA inclusion list should include all MDAs that the SDP binding may attempt to forward through. A simple way to ensure that an MDA that is not included in the list is not being used by the binding is to define the SDP the binding is associated with as MPLS and use an RSVP-TE LSP with a strict egress hop. The MDA associated with the IP interface defined as the strict egress hop should be present in the inclusion list. If the inclusion list does not currently contain the MDA that the binding is forwarding through, the multicast packets will not reach the destination represented by the binding.
By default, the MDA inclusion list is empty.
If an MDA is removed from the list, the MDA is automatically removed from the flooding domain of any snooped IP multicast streams associated with a destination on the MDA unless the MDA was the last MDA on the inclusion list. Once the inclusion list is empty, all MDAs are eligible for snooped IP multicast flooding for streams associated with the SDP binding.
Platforms
7705 SAR Gen 2
mfib-allowed-mda-destinations
Syntax
mfib-allowed-mda-destinations
Context
[Tree] (config>service>pw-template>egress mfib-allowed-mda-destinations)
Full Context
configure service pw-template egress mfib-allowed-mda-destinations
Description
Commands in this context configure MFIB-allowed XMA or MDA destinations.
The allowed-mda-destinations node and the corresponding mda command are used on spoke and mesh SDP bindings to provide a list of XMA or MDA destinations in the chassis that are allowed as destinations for multicast streams represented by [*,g] and [s,g] multicast flooding records on the VPLS service. The XMA or MDA list only applies to IP multicast forwarding when IGMP snooping is enabled on the VPLS service. The XMA or MDA list has no effect on normal VPLS flooding such as broadcast, Layer 2 multicast, unknown destinations or non-snooped IP multicast.
At the IGMP snooping level, a spoke or mesh SDP binding is included in the flooding domain for an IP multicast stream when it has either been defined as a multicast router port, received a IGMP query through the binding or has been associated with the multicast stream through an IGMP request by a host over the binding. Due to the dynamic nature of the way that a spoke or mesh SDP binding is associated with one or more egress network IP interfaces, the system treats the binding as appearing on all network ports. This causes all possible network destinations in the switch fabric to be included in the multicast streams flooding domain. The XMA or MDA destination list provides a simple mechanism that narrows the IP multicast switch fabric destinations for the spoke or mesh SDP binding.
If no XMAs or MDAs are defined within the allowed-mda-destinations node, the system operates normally and will forward IP multicast flooded packets associated with the spoke or mesh SDP binding to all switch fabric taps containing network IP interfaces.
The XMA or MDA inclusion list should include all XMAs or MDAs that the SDP binding may attempt to forward through. A simple way to ensure that an XMA or MDA that is not included in the list is not being used by the binding is to define the SDP the binding is associated with as MPLS and use an RSVP-TE LSP with a strict egress hop. The XMA or MDA associated with the IP interface defined as the strict egress hop should be present in the inclusion list.
If the inclusion list does not currently contain the XMA or MDA that the binding is forwarding through, the multicast packets will not reach the destination represented by the binding. By default, the XMA or MDA inclusion list is empty.
If an XMA or MDA is removed from the list, the XMA or MDA is automatically removed from the flooding domain of any snooped IP multicast streams associated with a destination on the XMA or MDA unless the XMA or MDA was the last XMA or MDA on the inclusion list. Once the inclusion list is empty, all XMAs or MDAs are eligible for snooped IP multicast flooding for streams associated with the SDP binding.
Platforms
7705 SAR Gen 2
mfib-table-high-wmark
mfib-table-high-wmark
Syntax
[no] mfib-table-high-wmark high-water-mark
Context
[Tree] (config>service>vpls mfib-table-high-wmark)
Full Context
configure service vpls mfib-table-high-wmark
Description
This command specifies the multicast FIB high watermark. When the percentage filling level of the multicast FIB exceeds the configured value, a trap is generated and a log entry is added.
The no form of this command reverts to the default.
Default
mfib-table-high-wmark 95
Parameters
- high-water-mark
-
Specifies the multicast FIB high watermark as a percentage.
Platforms
7705 SAR Gen 2
mfib-table-low-wmark
mfib-table-low-wmark
Syntax
[no] mfib-table-low-wmark low-water-mark
Context
[Tree] (config>service>vpls mfib-table-low-wmark)
Full Context
configure service vpls mfib-table-low-wmark
Description
This command specifies the multicast FIB low watermark. When the percentage filling level of the multicast FIB drops below the configured value, the corresponding trap is cleared and a log entry is added.
The no form of this command reverts to the default.
Default
mfib-table-low-wmark
Parameters
- low-water-mark
-
Specifies the multicast FIB low watermark as a percentage.
Platforms
7705 SAR Gen 2
mfib-table-size
mfib-table-size
Syntax
mfib-table-size size
no mfib-table-size
Context
[Tree] (config>service>vpls mfib-table-size)
Full Context
configure service vpls mfib-table-size
Description
This command specifies the maximum number of (s,g) entries in the multicast forwarding database (MFIB) for this VPLS instance.
The mfib-table-size parameter specifies the maximum number of multicast database entries for both learned and static multicast addresses for the VPLS instance. When a table-size limit is set on the mfib of a service which is lower than the current number of dynamic entries present in the mfib then the number of entries remains above the limit.
The no form of this command removes the configured maximum MFIB table size.
Default
no mfib-table-size
Parameters
- size
-
Specifies the maximum number of (s,g) entries allowed in the Multicast FIB
Platforms
7705 SAR Gen 2
mh-mode
mh-mode
Syntax
mh-mode {access | network}
Context
[Tree] (config>service>vpls>bgp-evpn>mpls mh-mode)
Full Context
configure service vpls bgp-evpn mpls mh-mode
Description
This command configures each BGP-EVPN instance in a multi-instance EVPN VPLS service to behave as network or access.
You can only configure one network instance for the service. If the service has a provider tunnel enabled, it requires a network instance.
Default
mh-mode network
Parameters
- access
-
Specifies that the BGP-EVPN instance does not participate in multihoming procedures, such as DF election processing or local bias forwarding.
- network
-
Specifies that the BGP-EVPN instance participates in multihoming procedures, such as DF election processing or local bias forwarding.
In services with two instances, only one of the two instances can be configured as network.
Platforms
7705 SAR Gen 2
mh-mode
Syntax
mh-mode {access | network}
Context
[Tree] (config>service>epipe>bgp-evpn>mpls mh-mode)
Full Context
configure service epipe bgp-evpn mpls mh-mode
Description
This command configures each BGP-EVPN instance in a multi-instance Epipe service to behave as network or access.
You can only configure one network instance for the service. If the service has a provider tunnel enabled, it requires a network instance.
Default
mh-mode network
Parameters
- access
-
Specifies that the BGP-EVPN instance does not participate in multihoming procedures, such as DF election processing or local bias forwarding.
- network
-
Specifies that the BGP-EVPN instance participates in multihoming procedures, such as DF election processing or local bias forwarding.
In services with two instances, only one of the two instances can be configured as network.
Platforms
7705 SAR Gen 2
micro-loop-avoidance
micro-loop-avoidance
Syntax
micro-loop-avoidance [fib-delay fib-delay]
no micro-loop-avoidance
Context
[Tree] (config>router>isis>segment-routing micro-loop-avoidance)
Full Context
configure router isis segment-routing micro-loop-avoidance
Description
This command enables, in the IGP instance, the microloop avoidance feature to prevent microloops from using segment routing (SR) loop-free tunnels for packets that are forwarded over SR IS-IS node SIDs.
This command enables microloop avoidance for MT0. Microloop avoidance for MT2 is enabled when this command is enabled along with SR-MPLS MT2 using the configure router isis segment-routing multi-topology mt2 command.
When enabled, the behavior of the feature is triggered by the receipt of a single event on a P2P link or broadcast link with two neighbors:
-
link addition or restoration
-
link removal or failure
-
link metric change
IGP then performs the following procedures:
-
IGP runs the main SPF and LFA SPFs.
-
For a node or a prefix in which the SPF resulted in no change to its next hops and metrics, IGP takes no action.
-
For a node or a prefix in which SPF resulted in a change to its next hops or metrics, IGP marks the route as eligible for microloop avoidance.
-
Activate, for each node SID that uses a microloop avoidance eligible route with ECMP next hops, the common set of next hops between the previous and new SPF.
-
Compute and activate, for each node SID which uses a microloop avoidance eligible route, with a single next hop loop-free SR tunnel that is applicable to the specific link event.
This tunnel acts the microloop avoidance primary path for the route and uses the same outgoing interface as the new computed primary next hop.
-
Program the TI-LFA, base LFA, or remote LFA backup path that protects the new primary next hop for the node SID.
-
-
Start the fib-delay timer to delay programming of new main and LFA SPF results into the FIB.
-
After the expiry of the fib-delay timer, program the new primary next hops for node SIDs routes that were marked eligible for microloop avoidance procedures.
The no form of this command disables the microloop avoidance feature.
Default
no micro-loop-avoidance
Parameters
- fib-delay
-
Specifies the delay, in 100s of milliseconds, before the system programs the new next hops for the SR tunnel.
Platforms
7705 SAR Gen 2
micro-loop-avoidance
Syntax
[no] micro-loop-avoidance
Context
[Tree] (config>router>isis>flex-algos>flex-algo micro-loop-avoidance)
Full Context
configure router isis flexible-algorithms flex-algo micro-loop-avoidance
Description
This command enables flexible algorithms-aware microloop avoidance. When enabled, the microloop configuration parameters are inherited from the base SPF.
This command enables microloop avoidance with flexible algorithms for MT0. Microloop avoidance with flexible algorithms for MT2 is enabled when this command is enabled along with SR-MPLS MT2 using the configure router isis segment-routing multi-topology mt2 command.
The no form of this command disables the microloop avoidance for flexible algorithms.
Default
no micro-loop-avoidance
Platforms
7705 SAR Gen 2
micro-loop-avoidance
Syntax
[no] micro-loop-avoidance
Context
[Tree] (config>router>ospf>flex-algos>flex-algo micro-loop-avoidance)
Full Context
configure router ospf flexible-algorithms flex-algo micro-loop-avoidance
Description
This command enables microloop avoidance for an SR-OSPF flexible algorithm, and consequently, inherits the FIB delay timer from the SR-OSPF configure router ospf segment-routing context.
When enabled, FIB updates are delayed before programming new primary next hops to avoid microloops.
- OSPFv2 SR-OSPF IPv4 tunnel (node SID)
- IPv4 and IPv6 SR-TE LSPs that use a node SID in their segment list
- IPv4 and IPv6 SR policies that use a node SID in their segment list
The no form of this command disables microloop avoidance. When microloop avoidance is disabled, the system forces any running FIB delay to expire immediately and programs the new next hops for all impacted node SIDs. When disabled, microloop avoidance is disabled instantaneously and will be disabled for the next SPF runs. Microloop avoidance remains disabled until it is re-enabled.
Default
no micro-loop-avoidance
Platforms
7705 SAR Gen 2
micro-loop-avoidance
Syntax
micro-loop-avoidance [fib-delay fib-delay]
no micro-loop-avoidance
Context
[Tree] (config>router>ospf>segm-rtng micro-loop-avoidance)
Full Context
configure router ospf segment-routing micro-loop-avoidance
Description
This command enables microloop avoidance for SR-OSPF.
- SPFv2 SR-OSPF IPv4 tunnel (node SID)
- IPv4 and IPv6 SR-TE LSPs that use a node SID in their segment list
- IPv4 and IPv6 SR policies that use a node SID in their segment list
The no form of this command disables microloop avoidance. When microloop avoidance is disabled, the system forces any running FIB delay to expire immediately and programs the new next hops for all impacted node SIDs. When disabled, microloop avoidance is disabled instantaneously and will be disabled for the next SPF runs. Microloop avoidance remains disabled until it is re-enabled.
Default
no micro-loop-avoidance
Parameters
- fib-delay
-
Specifies the FIB delay before programming new primary next hops. Configure the FIB delay timer to a value that corresponds to the worst-case IGP convergence in a network domain. The default FIB delay timer value corresponds to a network with a nominal convergence time.
Platforms
7705 SAR Gen 2
min-advertisement-interval
min-advertisement-interval
Syntax
[no] min-advertisement-interval seconds
Context
[Tree] (config>router>router-advert>if min-advertisement-interval)
Full Context
configure router router-advertisement interface min-advertisement-interval
Description
This command configures the minimum interval between sending ICMPv6 neighbor discovery router advertisement messages.
Default
min-advertisement-interval 200
Parameters
- seconds
-
Specifies the minimum interval in seconds between sending ICMPv6 neighbor discovery router advertisement messages.
Platforms
7705 SAR Gen 2
min-delay
min-delay
Syntax
min-delay [delay]
no min-delay
Context
[Tree] (config>log>event-handling>handler>action-list>entry min-delay)
Full Context
configure log event-handling handler action-list entry min-delay
Description
This command specifies the minimum delay in seconds between subsequent executions of the action specified in this entry. This is useful, for example, to ensure that a script does not get triggered to execute too often.
Default
no min-delay
Parameters
- delay
-
Specifies the unit in seconds.
Platforms
7705 SAR Gen 2
min-frame-length
min-frame-length
Syntax
min-frame-length byte-length
Context
[Tree] (config>port>ethernet min-frame-length)
Full Context
configure port ethernet min-frame-length
Description
This command configures the minimum transmitted frame length.
Parameters
- byte-length
-
Specifies the number of bytes for the minimum frame length.
Platforms
7705 SAR Gen 2
min-lease-time
min-lease-time
Syntax
min-lease-time [days days] [hrs hours] [min minutes] [sec seconds]
no min-lease-time
Context
[Tree] (config>service>vprn>dhcp>server>pool min-lease-time)
[Tree] (config>router>dhcp>server>pool min-lease-time)
Full Context
configure service vprn dhcp local-dhcp-server pool min-lease-time
configure router dhcp local-dhcp-server pool min-lease-time
Description
This command configures the minimum lease time.
The no form of this command reverts to the default.
Default
min-lease-time min 10
Parameters
- min-lease-time
-
Specifies the minimum lease time.
Platforms
7705 SAR Gen 2
min-route-advertisement
min-route-advertisement
Syntax
min-route-advertisement seconds
no min-route-advertisement
Context
[Tree] (config>service>vprn>bgp>group>neighbor min-route-advertisement)
[Tree] (config>service>vprn>bgp>group min-route-advertisement)
[Tree] (config>service>vprn>bgp min-route-advertisement)
Full Context
configure service vprn bgp group neighbor min-route-advertisement
configure service vprn bgp group min-route-advertisement
configure service vprn bgp min-route-advertisement
Description
This command configures the minimum interval, in seconds, at which a prefix can be advertised to a peer.
This configuration parameter can be set at three levels: global level (applies to all peers), group level (applies to all peers in peer-group) or neighbor level (only applies to specified peer). The most specific value is used.
The no form of this command reverts to default values.
Default
min-route-advertisement 30
Parameters
- seconds
-
Specifies the minimum route advertising interval, in seconds, expressed as a decimal integer.
Platforms
7705 SAR Gen 2
min-route-advertisement
Syntax
min-route-advertisement seconds
no min-route-advertisement
Context
[Tree] (config>router>bgp>group>neighbor min-route-advertisement)
[Tree] (config>router>bgp min-route-advertisement)
[Tree] (config>router>bgp>group min-route-advertisement)
Full Context
configure router bgp group neighbor min-route-advertisement
configure router bgp min-route-advertisement
configure router bgp group min-route-advertisement
Description
This command configures the minimum interval, in seconds, between successive updates of a prefix towards a peer.
This configuration parameter can be set at three levels: global level (applies to all peers), group level (applies to all peers in peer-group), or neighbor level (only applies to specified peer). The most specific value is used.
The no form of this command used at the global level reverts to default.
The no form of this command used at the group level reverts to the value defined at the global level.
The no form of this command used at the neighbor level reverts to the value defined at the group level.
The rapid-update command can be used to override the peer-level min-route-advertisement time and applies the minimum setting (0 seconds) to routes belonging to address families specified by the rapid-update command; routes of other address families continue to be advertised according to the session-level MRAI setting.
The rapid-update and rapid-withdrawal commands may result in the routes being sent before the peer-level MRAI timer expires.
Default
min-route-advertisement 30
Parameters
- seconds
-
Specifies the minimum route advertising interval, in seconds, expressed as a decimal integer.
Platforms
7705 SAR Gen 2
min-thresh-separation
min-thresh-separation
Syntax
min-thresh-separation size [bytes | kilobytes]
no min-thresh-separation
Context
[Tree] (config>card>fp>ingress>network>queue-group>policer-control-override>priority-mbs-thresholds min-thresh-separation)
[Tree] (config>card>fp>ingress>access>queue-group>policer-control-override>priority-mbs-thresholds min-thresh-separation)
Full Context
configure card fp ingress network queue-group policer-control-override priority-mbs-thresholds min-thresh-separation
configure card fp ingress access queue-group policer-control-override priority-mbs-thresholds min-thresh-separation
Description
This command defines the minimum required separation between each in-use discard threshold maintained for each parent policer context associated with the policer-control-policy. The min-thresh-separation value may be overridden on each SAP or sub-profile to which the policy is applied.
The system uses the default or specified min-thresh-separation value in order to determine the minimum separation required between each of the of the parent policer discard thresholds. The system enforces the minimum separation based on the following behavior in two ways. The first is determining the size of the shared-portion for each priority level (when the mbs-contribution command’s optional fixed keyword is not specified):
-
When a parent policer instance’s priority level has less than two child policers associated, the shared-portion for the level will be zero.
-
When a parent policer instance’s priority level has two or more child policers associated, the shared-portion for the level will be equal to the current value of min-thresh-separation.
The second function the system uses the min-thresh-separation value for is determining the value per priority level for the fair-portion:
-
When a parent policer instance’s priority level has no child policers associated, the fair-portion for the level will be zero.
-
When a parent policer instance’s priority level has one child policer associated, the fair-portion will be equal to the maximum of the min-thresh-separation value and the priority level’s mbs-contribution value.
-
When a parent policer instance's priority level has two or more child policers associated, the fair-portion will be equal to the maximum of the following:
-
min-thresh-separation value
-
The priority level’s mbs-contribution value less min-thresh-separation value
-
When the mbs-contribution command’s optional fixed keyword is defined for a priority level within the policy, the system will treat the defined mbs-contribution value as an explicit definition of the priority level’s MBS. While the system will continue to track child policer associations with the parent policer priority levels, the association counters will have no effect. Instead the following rules will be used to determine a fixed priority level’s shared-portion and fair-portion:
-
If a fixed priority level’s mbs-contribution value is set to zero, both the shared-portion and fair-portion will be set to zero
-
If the mbs-contribution value is not set to zero:
-
The shared-portion will be set to the current min-thresh-separation value
-
The fair-portion will be set to the maximum of the following:
-
min-thresh-separation value
-
mbs-contribution value less min-thresh-separation value
-
-
Each time the min-thresh-separation value is modified, the thresholds for all instances of the parent policer created through association with this policer-control-policy are reevaluated except for parent policer instances that currently have a min-thresh-separation override.
Determining the Correct Value for the Minimum Threshold Separation Value
The minimum value for min-thresh-separation should be set equal to the maximum size packet that will be handled by the parent policer. This ensures that when a lower priority packet is incrementing the bucket, the size of the increment will not cause the bucket's depth to equal or exceed a higher priority threshold. It also ensures that an unfair packet within a priority level cannot cause the PIR bucket to increment to the discard-all threshold within the priority.
When evaluating maximum packet size, each child policer’s per-packet-offset setting should be taken into consideration. If the maximum size packet is 1518 bytes and a per-packet-offset parameter is configured to add 20 bytes per packet, min-thresh-separation should be set to 1538 due to the fact that the parent policer will increment its PIR bucket using the extra 20 bytes.
In most circumstances, a value larger than the maximum packet size is not necessary. Management of priority level aggregate burst tolerance is intended to be implemented using the priority level mbs-contribution command. Setting a value larger than the maximum packet size will not adversely affect the policer performance, but it may increase the aggregate burst tolerance for each priority level.
One thing to note is that a priority level’s shared-portion of the parent policer’s PIR bucket depth is only necessary to provide some separation between a lower priority’s discard-all threshold and this priority’s discard-unfair threshold. It is expected that the burst tolerance for the unfair packets is relatively minimal since the child policers feeding the parent policer priority level all have some amount of fair burst before entering into an FIR exceed or unfair state. The fair burst amount for a priority level is defined using the mbs-contribution command.
The no form of this command returns the policy’s min-thresh-separation value to the default value. This has no effect on instances of the parent policer where min-thresh-separation is overridden unless the override is removed.
Default
no min-thresh-separation
Parameters
- size
-
Specifies that the size parameter is required when executing the min-thresh-separation command. It is expressed as an integer and specifies the shared portion in bytes or kilobytes that is selected by the trailing bytes or kilobytes keywords. If both bytes and kilobytes are missing, kilobytes is the assumed value. Setting this value has no effect on parent policer instances where the min-thresh-separation value has been overridden. Clearing an override on parent policer instance causes this value to be enforced.
- bytes | kilobytes
-
Specifies that the bytes keyword is optional and is mutually exclusive with the kilobytes keyword. When specified, size is interpreted as specifying the size of min-thresh-separation in bytes.
The kilobytes keyword is optional and is mutually exclusive with the bytes keyword. When specified, size is interpreted as specifying the size of min-thresh-separation in kilobytes.
Platforms
7705 SAR Gen 2
min-thresh-separation
Syntax
min-thresh-separation size [bytes | kilobytes]
Context
[Tree] (config>service>epipe>sap>egress>policy-ctrl-over>mbs-thrshlds min-thresh-separation)
[Tree] (config>service>epipe>sap>ingress>policy-ctrl-over>mbs-thrshlds min-thresh-separation)
Full Context
configure service epipe sap egress policer-control-override priority-mbs-thresholds min-thresh-separation
configure service epipe sap ingress policer-control-override priority-mbs-thresholds min-thresh-separation
Description
This command, within the SAP ingress and egress contexts, is used to override the root arbiter’s parent policer min-thresh-separation parameter that is defined within the policer-control-policy applied to the SAP.
When the override is defined, modifications to the policer-control-policy min-thresh-separation parameter have no effect on the SAP’s parent policer until the override is removed using the no min-thresh-separation command within the SAP.
The no form of this command removes the override and allows the min-thresh-separation setting from the policer-control-policy to control the root arbiter’s parent policer’s minimum discard threshold separation size.
Default
no min-thresh-separation
Parameters
- size
-
The minimum discard threshold separation override value.
- bytes
-
Signifies that size is expressed in bytes. The bytes and kilobytes keywords are mutually exclusive and optional. The default is kilobytes.
- kilobytes
-
Signifies that size is expressed in kilobytes. The bytes and kilobytes keywords are mutually exclusive and optional. The default is kilobytes.
Platforms
7705 SAR Gen 2
min-thresh-separation
Syntax
min-thresh-separation size [{bytes | kilobytes}]
Context
[Tree] (config>service>vpls>sap>egress>policer-ctrl-over>mbs-thrshlds min-thresh-separation)
[Tree] (config>service>vpls>sap>ingress>policer-ctrl-over>mbs-thrshlds min-thresh-separation)
Full Context
configure service vpls sap egress policer-control-override priority-mbs-thresholds min-thresh-separation
configure service vpls sap ingress policer-control-override priority-mbs-thresholds min-thresh-separation
Description
This command within the SAP ingress and egress contexts is used to override the root arbiter’s parent policer min-thresh-separation parameter that is defined within the policer-control-policy applied to the SAP.
When the override is defined, modifications to the policer-control-policy min-thresh-separation parameter have no effect on the SAP’s parent policer until the override is removed using the no min-thresh-separation command within the SAP.
The no form of this command removes the override and allows the min-thresh-separation setting from the policer-control-policy to control the root arbiter’s parent policer’s minimum discard threshold separation size.
Default
no min-thresh-separation
Parameters
- size
-
This parameter is required when specifying min-thresh-separation override and is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional byte and kilobyte keywords are mutually exclusive and are used to explicitly define whether size represents bytes or kilobytes.
Platforms
7705 SAR Gen 2
min-thresh-separation
Syntax
min-thresh-separation size [{bytes | kilobytes}]
Context
[Tree] (config>service>ies>if>sap>ingress>policer-ctrl-over>mbs-thrshlds min-thresh-separation)
[Tree] (config>service>ies>if>sap>egress>policer-ctrl-over>mbs-thrshlds min-thresh-separation)
Full Context
configure service ies interface sap ingress policer-control-override priority-mbs-thresholds min-thresh-separation
configure service ies interface sap egress policer-control-override priority-mbs-thresholds min-thresh-separation
Description
This command within the SAP ingress and egress contexts is used to override the root arbiter’s parent policer min-thresh-separation parameter that is defined within the policer-control-policy applied to the SAP.
When the override is defined, modifications to the policer-control-policy min-thresh-separation parameter have no effect on the SAP’s parent policer until the override is removed using the no min-thresh-separation command within the SAP.
The no form of this command removes the override and allows the min-thresh-separation setting from the policer-control-policy to control the root arbiter’s parent policer’s minimum discard threshold separation size.
Default
no min-thresh-separation
Parameters
- size
-
This parameter is required when specifying min-thresh-separation override and is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional byte and kilobyte keywords are mutually exclusive and are used to explicitly define whether size represents bytes or kilobytes.
Platforms
7705 SAR Gen 2
min-thresh-separation
Syntax
min-thresh-separation size [{bytes | kilobytes}]
Context
[Tree] (config>service>vprn>if>sap>egress>policy-ctrl-over>mbs-thrshlds min-thresh-separation)
[Tree] (config>service>vprn>if>sap>ingress>policy-ctrl-over>mbs-thrshlds min-thresh-separation)
Full Context
configure service vprn interface sap egress policer-control-override priority-mbs-thresholds min-thresh-separation
configure service vprn interface sap ingress policer-control-override priority-mbs-thresholds min-thresh-separation
Description
This command within the SAP ingress and egress contexts is used to override the root arbiter’s parent policer min-thresh-separation parameter that is defined within the policer-control-policy applied to the SAP.
When the override is defined, modifications to the policer-control-policy min-thresh-separation parameter have no effect on the SAP’s parent policer until the override is removed using the no min-thresh-separation command within the SAP.
The no form of this command removes the override and allows the min-thresh-separation setting from the policer-control-policy to control the root arbiter’s parent policer’s minimum discard threshold separation size.
Default
no min-thresh-separation
Parameters
- size
-
This parameter is required when specifying min-thresh-separation override and is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional byte and kilobyte keywords are mutually exclusive and are used to explicitly define whether size represents bytes or kilobytes.
Platforms
7705 SAR Gen 2
min-thresh-separation
Syntax
min-thresh-separation size [bytes | kilobytes]
no min-thresh-separation
Context
[Tree] (config>qos>plcr-ctrl-plcy>root>priority-mbs-thresholds min-thresh-separation)
Full Context
configure qos policer-control-policy root priority-mbs-thresholds min-thresh-separation
Description
The min-thresh-separation command defines the minimum required separation between each in-use discard threshold maintained for each parent policer context associated with the policer-control-policy. The min-thresh-separation value may be overridden on each SAP or sub-profile to which the policy is applied.
The system uses the default or specified min-thresh-separation value in order to determine the minimum separation required between each of the of the parent policer discard thresholds. The system enforces the minimum separation based on the following behavior in two ways. The first is determining the size of the shared-portion for each priority level (when the mbs-contribution command’s optional fixed keyword is not specified):
-
When a parent policer instance’s priority level has less than two child policers associated, the shared-portion for the level will be zero.
-
When a parent policer instance’s priority level has two or more child policers associated, the shared-portion for the level will be equal to the current value of min-thresh-separation.
The second function the system uses the min-thresh-separation value for is determining the value per priority level for the fair-portion:
-
When a parent policer instance’s priority level has no child policers associated, the fair-portion for the level will be zero.
-
When a parent policer instance’s priority level has one child policer associated, the fair-portion will be equal to the maximum of the min-thresh-separation value and the priority level’s mbs-contribution value.
-
When a parent policer instance's priority level has two or more child policers associated, the fair-portion will be equal to the maximum of the following:
-
min-thresh-separation value
-
mbs-contribution value less min-thresh-separation value
-
When the mbs-contribution command’s optional fixed keyword is defined for a priority level within the policy, the system will treat the defined mbs-contribution value as an explicit definition of the priority level’s MBS. While the system will continue to track child policer associations with the parent policer priority levels, the association counters will have no effect. Instead, the following rules will be used to determine a fixed priority level’s shared-portion and fair-portion:
-
If a fixed priority level’s mbs-contribution value is set to zero, both the shared-portion and fair-portion will be set to zero
-
If the mbs-contribution value is not set to zero:
-
The shared-portion will be set to the current min-thresh-separation value
-
The fair-portion will be set to the maximum of the following:
min-thresh-separation value
mbs-contribution value less min-thresh-separation value
-
Each time the min-thresh-separation value is modified, the thresholds for all instances of the parent policer created through association with this policer-control-policy are reevaluated.
Determining the Correct Value for the Minimum Threshold Separation Value
The minimum value for min-thresh-separation should be set equal to the maximum size packet that will be handled by the parent policer. This ensures that when a lower priority packet is incrementing the bucket, the size of the increment will not cause the bucket's depth to equal or exceed a higher priority threshold. It also ensures that an unfair packet within a priority level cannot cause the PIR bucket to increment to the discard-all threshold within the priority.
When evaluating maximum packet size, each child policer’s per-packet-offset setting should be taken into consideration. If the maximum size packet is 1518 bytes and a per-packet-offset parameter is configured to add 20 bytes per packet, min-thresh-separation should be set to 1538 due to the fact that the parent policer will increment its PIR bucket using the extra 20 bytes.
In most circumstances, a value larger than the maximum packet size is not necessary. Management of priority level aggregate burst tolerance is intended to be implemented using the priority level mbs-contribution command. Setting a value larger than the maximum packet size will not adversely affect the policer performance, but it may increase the aggregate burst tolerance for each priority level.
A priority level’s shared-portion of the parent policer’s PIR bucket depth is only necessary to provide some separation between a lower priority’s discard-all threshold and this priority’s discard-unfair threshold. It is expected that the burst tolerance for the unfair packets is relatively minimal since the child policers feeding the parent policer priority level all have some amount of fair burst before entering into an FIR exceed or unfair state. The fair burst amount for a priority level is defined using the mbs-contribution command.
The no form of this command returns the policy’s min-thresh-separation value to the default value.
Parameters
- size
-
The size parameter is required when executing the min-thresh-separation command. It is expressed as an integer. Setting this value has no effect on parent policer instances where the min-thresh-separation value has been overridden.
- bytes | kilobytes
-
This parameter indicates whether the size is expressed in bytes or kilobytes.
Platforms
7705 SAR Gen 2
min-wait-to-advertise
min-wait-to-advertise
Syntax
min-wait-to-advertise seconds
no min-wait-to-advertise
Context
[Tree] (config>service>vprn>bgp>convergence min-wait-to-advertise)
Full Context
configure service vprn bgp convergence min-wait-to-advertise
Description
This command configures the minimum amount of time that BGP waits, after the first session establishment following a restart of the BGP instance, until it can start advertising IPv4-unicast and IPv6-unicast routes to its BGP peers, to allow time for re-convergence.
The time limit configured by this command should allow sufficient time for all important peers to re-establish their sessions with the restarting router.
The no form of this command implements the default time limit of 0 seconds, which disables all forms of delayed route advertisement. In other words, it causes IPv4-unicast and IPv6-unicast routes to be re-advertised as soon as possible after BGP instance restart.
Default
no min-wait-to-advertise
Parameters
- seconds
-
Specifies the minimum amount of time, in seconds, that BGP waits until IPv4-unicast and IPv6-unicast routes can be advertised to peers.
Platforms
7705 SAR Gen 2
min-wait-to-advertise
Syntax
min-wait-to-advertise seconds
no min-wait-to-advertise
Context
[Tree] (config>router>bgp>convergence min-wait-to-advertise)
Full Context
configure router bgp convergence min-wait-to-advertise
Description
This command configures the minimum amount of time that BGP waits, after the first session establishment following a restart of the BGP instance, until it can start advertising IPv4-unicast and IPv6-unicast routes to its BGP peers, to allow time for re-convergence.
The time limit configured by this command should allow sufficient time for all important peers to re-establish their sessions with the restarting router.
The no form of this command implements the default time limit of 0 seconds, which disables all forms of delayed route advertisement. In other words, it causes IPv4-unicast and IPv6-unicast routes to be re-advertised as soon as possible after BGP instance restart.
Default
no min-wait-to-advertise
Parameters
- seconds
-
Specifies the minimum amount of time, in seconds, that BGP waits until IPv4-unicast and IPv6-unicast routes can be advertised to peers.
Platforms
7705 SAR Gen 2
minimum
minimum
Syntax
minimum [percent [percent]] [number [number]]
no minimum
Context
[Tree] (config>service>vprn>dhcp6>server>pool>prefix>thresholds>minimum-free minimum)
[Tree] (config>router>dhcp6>server>pool>prefix>thresholds>minimum-free minimum)
Full Context
configure service vprn dhcp6 local-dhcp-server pool prefix thresholds minimum-free minimum
configure router dhcp6 local-dhcp-server pool prefix thresholds minimum-free minimum
Description
This command configures a percentage-based or number-based threshold which represents the minimal available percentage or number of the prefix with a configured length in the provisioned prefix. The system sends out a warning if the actual percentage or number is lower than the configured threshold.
For example:
prefix 2001:0:0:ffe0::/50 pd wan-host create
thresholds
minimum-free prefix-length 64
minimum number 3
With the above configuration, the system sends a warning when the number of available /64 in prefix 2001:0:0:ffe0::/50 is less than 3.
The no form of this command removes the command parameters from the configuration.
Parameters
- percent
-
Specifies the percentage of used prefixes with the minimum free threshold length in the pool compared to the number of provisioned prefixes.
- number
-
Specifies the number of prefixes.
Platforms
7705 SAR Gen 2
minimum-age
minimum-age
Syntax
minimum-age [days days] [hrs hours] [min minutes] [sec seconds]
no minimum-age
Context
[Tree] (config>system>security>password minimum-age)
Full Context
configure system security password minimum-age
Description
Configure the minimum required age of a password before it can be changed again.
Default
minimum-age min 10
Parameters
- days
-
Specifies the minimum required days of a password before it can be changed again.
- hours
-
Specifies the minimum required hours of a password before it can be changed again.
- minutes
-
Specifies the minimum required minutes of a password before it can be changed again.
- seconds
-
Specifies the minimum required seconds of a password before it can be changed again.
Platforms
7705 SAR Gen 2
minimum-change
minimum-change
Syntax
minimum-change distance
no minimum-change
Context
[Tree] (config>system>security>password minimum-change)
Full Context
configure system security password minimum-change
Description
This command configures the minimum number of characters required to be different in the new password from a previous password.
The no form of this command reverts to default value.
Default
minimum-change 5
Parameters
- distance
-
Specifies how many characters must be different in the new password from the old password.
Platforms
7705 SAR Gen 2
minimum-classes
minimum-classes
Syntax
minimum-classes minimum
no minimum-classes
Context
[Tree] (config>system>security>password>complexity-rules minimum-classes)
Full Context
configure system security password complexity-rules minimum-classes
Description
Force the use of at least this many different character classes
The no form of this command resets to default.
Default
no minimum-classes
Parameters
- minimum
-
Specifies the minimum number of classes to be configured.
Platforms
7705 SAR Gen 2
minimum-delay
minimum-delay
Syntax
minimum-delay [minimum-delay]
no minimum-delay
Context
[Tree] (config>router>isis>if>delay-normalization minimum-delay)
Full Context
configure router isis interface delay-normalization minimum-delay
Description
This command configures the minimum delay on the interface. For example, if 5 microseconds is configured, the system advertises this value as the minimum delay, even if TWAMP measures a delay of 2 microseconds.
The no form of this command reverts to the default.
Default
1 usec
Parameters
- minimum-delay
-
Specifies the minimum delay in microseconds.
Platforms
7705 SAR Gen 2
minimum-delay
Syntax
minimum-delay [minimum-delay]
no minimum-delay
Context
[Tree] (config>router>ospf>area>if>delay-normalization minimum-delay)
Full Context
configure router ospf area interface delay-normalization minimum-delay
Description
This command configures the minimum delay on the interface. For example, if 5 microseconds is configured, the system advertises this value as the minimum delay, even if TWAMP measures a delay of 2 microseconds.
The no form of this command reverts to the default.
Default
1 usec
Parameters
- minimum-delay
-
Specifies the minimum delay, in microseconds.
Platforms
7705 SAR Gen 2
minimum-free
minimum-free
Syntax
minimum-free minimum-free [percent] [event-when-depleted]
no minimum-free
Context
[Tree] (config>router>dhcp>server>pool minimum-free)
[Tree] (config>service>vprn>dhcp>server>pool minimum-free)
Full Context
configure router dhcp local-dhcp-server pool minimum-free
configure service vprn dhcp local-dhcp-server pool minimum-free
Description
This command specifies the desired minimum number of free addresses in this pool.
The no form of this command reverts to the default.
Default
minimum-free 1
Parameters
- minimum-free
-
Specifies the minimum number of free addresses.
- percent
-
Specifies that the value indicates a percentage.
- event-when-depleted
-
This parameter enables a system-generate event when all available addresses in the pool/subnet of local DHCP server are depleted.
Platforms
7705 SAR Gen 2
minimum-free
Syntax
minimum-free minimum-free [percent] [event-when-depleted]
no minimum-free
Context
[Tree] (config>router>dhcp>server>pool>subnet minimum-free)
[Tree] (config>service>vprn>dhcp>server>pool>subnet minimum-free)
Full Context
configure router dhcp local-dhcp-server pool subnet minimum-free
configure service vprn dhcp local-dhcp-server pool subnet minimum-free
Description
This command configures the minimum number of free addresses in this subnet. If the actual number of free addresses in this subnet falls below this configured minimum, a notification is generated.
The no form of the reverts to the default.
Default
minimum-free 1
Parameters
- minimum-free
-
Specifies the minimum number of free addresses in this subnet.
- percent
-
Specifies that the value indicates a percentage.
- event-when-depleted
-
Enables a system-generate event when all available addresses in the pool or subnet of local DHCP server are depleted.
Platforms
7705 SAR Gen 2
minimum-free
Syntax
[no] minimum-free prefix-length [prefix-length]
Context
[Tree] (config>service>vprn>dhcp6>server>pool>thresholds minimum-free)
[Tree] (config>router>dhcp6>server>pool>thresholds minimum-free)
Full Context
configure service vprn dhcp6 local-dhcp-server pool thresholds minimum-free
configure router dhcp6 local-dhcp-server pool thresholds minimum-free
Description
This command creates a threshold for a given prefix length on the pool level. Up to 128 thresholds could be created. For example, with minimum-free prefix-length 64, then the usage of /64 prefix in the pool is counted.
There are two types of thresholds that could be defined at the pool level:
-
Depleted — The system sends out a warning when the prefix with the configured length is no long available in the pool.
-
Minimum free — A percentage-based threshold which represents the minimal available percentage of prefix with the configured length in the pool. The system will send out warning if the actual percentage is lower than the configured percentage.
Configuring this command also enables the system stats collection for configure prefix length, which could be displayed with the show router router-id dhcp6 local-dhcp-server dhcp6-server-name pool-threshold-stats command.
The no form of this command removes the prefix-length from the configuration.
Parameters
- prefix-length
-
Specifies the IPv6 prefix length.
Platforms
7705 SAR Gen 2
minimum-length
minimum-length
Syntax
minimum-length length
no minimum-length
Context
[Tree] (config>system>security>password>complexity-rules minimum-length)
Full Context
configure system security password complexity-rules minimum-length
Description
This command configures the minimum number of characters required for locally administered passwords, HMAC-MD5-96, HMAC-SHA-96, and des-keys configured in the system security section.
If multiple minimum-length commands are entered each command overwrites the previous entered command.
The no form of this command reverts to default value.
Default
minimum-length 6
Parameters
- value
-
Specifies the minimum number of characters required for a password.
Platforms
7705 SAR Gen 2
minute
minute
Syntax
minute {minute-number [..minute-number] | all}
no minute
Context
[Tree] (config>system>cron>sched minute)
Full Context
configure system cron schedule minute
Description
This command specifies the minute to schedule a command. Multiple minutes of the hour can be specified. When multiple minutes are configured, each of them will cause the schedule to occur. If a minute is configured, but no hour or day is configured, the event will not execute. If a minute is configured without configuring the month, weekday, day-of-month, and minute, the event will not execute.
The no form of this command removes the specified minute from the configuration.
Default
no minute
Parameters
- minute-number
-
Specifies the minute to schedule a command.
- all
-
Specifies all minutes.
Platforms
7705 SAR Gen 2
minutes
minutes
Syntax
minutes {minutes | disable}
no minutes
Context
[Tree] (config>system>security>ssh>key-re-exchange>server minutes)
[Tree] (config>system>security>ssh>key-re-exchange>client minutes)
Full Context
configure system security ssh key-re-exchange server minutes
configure system security ssh key-re-exchange client minutes
Description
This command configures the maximum time, in minutes, before a key re-exchange is initiated by the server.
The no form of this command reverts to the default value.
Default
minutes 60
Parameters
- minutes
-
Specifies the time interval, in minutes, after which the SSH client will initiate the key-re-exchange.
- disable
-
Specifies that a session will never timeout. To re-enable minutes, enter the command without the disable option.
Platforms
7705 SAR Gen 2
mirror-dest
mirror-dest
Syntax
mirror-dest service-id [create] [type mirror-type] [name name]
no mirror-dest service-id
Context
[Tree] (config>mirror mirror-dest)
Full Context
configure mirror mirror-dest
Description
This command creates a context to set up a service that is intended for packet mirroring. It is configured as a service to allow mirrored packets to be directed locally (within the same router) or remotely, over the core of the network and have a far-end decode mirror encapsulation.
The mirror destination service is comprised of destination parameters that define where the mirrored packets are to be sent. It also specifies whether the defined service-id will receive mirrored packets from far-end router over the network core.
The mirror destination service IDs are persistent between boots of the router and are included in the configuration saves. The local sources of mirrored packets for the service ID are defined within the debug mirror mirror-source command that references the same service-id. Up to 255 mirror destination service IDs can be created within a single system.
The mirror-dest command creates or edits a service ID for mirroring purposes. If the service-id does not exist within the context of all defined services, the mirror destination service is created and the context of the CLI is changed to that service ID. If the service-id exists within the context of defined mirror destination services, the CLI context is changed for editing parameters on that service ID. If the service-id exists within the context of another service type, an error message is returned and CLI context is not changed from the current context.
The no form of this command removes a mirror destination from the system. The mirror source associations with the mirror destination service-id do not need to be removed or shutdown first. The mirror destination service-id must be shutdown before the service ID can be removed. When the service ID is removed, all mirror-source commands that have the service ID defined will also be removed from the system.
Parameters
- service-id
-
The service identification identifies the service in the service domain. This ID is unique to this service and cannot be used by any other service, regardless of service type. The same service ID must be configured on every router that this particular service is defined on.
If particular a service ID already exists for a service, then the same value cannot be used to create a mirror destination service ID with the same value. For example:
If an Epipe service ID 11 exists, then a mirror destination service ID 11 cannot be created. If a VPLS service ID 12 exists, then a mirror destination service ID 12 cannot be created.
If an IES service ID 13 exists, then a mirror destination service ID 13 cannot be created.
- create
-
Keyword used to create a mirror destination service.
- mirror-type
-
The type describes the encapsulation supported by the mirror service.
- name
-
Configures an optional service name identifier, up to 64 characters, to a given service. This service name can then be used in configuration references, display, and show commands throughout the system. A defined service name can help the service provider or administrator to identify and manage services within the SR OS platforms.
To create a service, you must assign a service ID; however, after it is created, either the service ID or the service name can be used to identify and reference a service.
If a name is not specified at creation time, then SR OS assigns a string version of the service-id as the name.
Service names may not begin with an integer (0 to 9).
Platforms
7705 SAR Gen 2
mirror-source
mirror-source
Syntax
[no] mirror-source service-id
Context
[Tree] (config>mirror mirror-source)
Full Context
configure mirror mirror-source
Description
This command configures mirror source parameters for a mirrored service.
The mirror-source command is used to enable mirroring of packets specified by the association of the mirror-source to sources of packets defined within the context of the mirror-dest-service-id. The mirror destination service must already exist within the system.
A mirrored packet cannot be mirrored to multiple destinations. If a packet matches multiple mirror source entries (for example, a SAP on one mirror-source and a port on another mirror-source), then the packet is mirrored to a single mirror-dest-service-id based on the following precedence:
-
Filter entry
-
SAP
-
Physical port
The precedence is structured so the most specific match criteria has precedence over a less specific match. For example, if a mirror-source defines a port and a SAP on that port, then a packet arriving on the SAP will be mirrored using the SAP mirror (and not mirrored using the Port mirror) because the SAP is more specific than the port.
The no form of this command deletes all related source commands within the context of the mirror-source service-id. The command does not remove the service ID from the system.
Parameters
- service-id
-
Specifies the service identification identifies the service in the service domain. This ID is unique to this service and cannot be used by any other service, regardless of service type. The same service ID must be configured on every router that this particular service is defined on.
Platforms
7705 SAR Gen 2
mirror-source
Syntax
[no] mirror-source service-id
Context
[Tree] (debug mirror-source)
Full Context
debug mirror-source
Description
This command configures mirror source parameters for a mirrored service.
The mirror-source command is used to enable mirroring of packets specified by the association of the mirror-source to sources of packets defined within the context of the mirror-dest-service-id. The mirror destination service must already exist within the system.
A mirrored packet cannot be mirrored to multiple destinations. If a packet matches multiple mirror source entries (for example, a SAP on one mirror-source and a port on another mirror-source), then the packet is mirrored to a single mirror-dest-service-id based on the following precedence:
-
Filter entry
-
SAP
-
Physical port
The precedence is structured so the most specific match criteria has precedence over a less specific match. For example, if a mirror-source defines a port and a SAP on that port, then a packet arriving on the SAP will be mirrored using the SAP mirror (and not mirrored using the Port mirror) because the SAP is more specific than the port.
The mirror-source configuration is not saved when a configuration is saved. A mirror-source manually configured within an ASCII configuration file will not be preserved if that file is overwritten by a save command. Define the mirror-source within a file associated with a config exec command to make a mirror-source persistent between system reboots.
By default, all mirror destination service IDs have a mirror-source associated with them. The mirror-source is not technically created with this command. Instead the service ID provides a contextual node for storing the current mirroring sources for the associated mirror destination service ID. The mirror-source is created for the mirror service when the operator enters the debug>mirror-source svcId for the first time. The mirror-source is also automatically removed when the mirror destination service ID is deleted from the system.
The no form of this command deletes all related source commands within the context of the mirror-source service-id. The command does not remove the service ID from the system.
Parameters
- service-id
-
Specifies the mirror destination service ID for which match criteria will be defined. The service-id must already exist within the system.
Platforms
7705 SAR Gen 2
misc
misc
Syntax
[no] misc
Context
[Tree] (debug>router>igmp misc)
Full Context
debug router igmp misc
Description
This command enables debugging for IGMP miscellaneous information.
The no form of the command disables the debugging.
Platforms
7705 SAR Gen 2
Output
The following output is an example of debugged IGMP miscellaneous information.
Output ExampleA:ALA-CA# debug router 100 igmp misc
*A:ALA-CA# show debug
debug
router "100"
igmp
misc
exit
exit
exit
*A:ALA-CA#
misc
Syntax
misc [detail]
no misc
Context
[Tree] (debug>router>mpls>event misc)
[Tree] (debug>router>rsvp>event misc)
Full Context
debug router mpls event misc
debug router rsvp event misc
Description
This command debugs miscellaneous events.
The no form of the command disables the debugging.
Parameters
- detail
-
Displays detailed information about miscellaneous events.
Platforms
7705 SAR Gen 2
misc
Syntax
[no] misc
Context
[Tree] (debug>router>isis misc)
Full Context
debug router isis misc
Description
This command enables debugging for IS-IS misc.
The no form of the command disables debugging.
Platforms
7705 SAR Gen 2
misc
mixed-lsp-mode
mixed-lsp-mode
Syntax
[no] mixed-lsp-mode
Context
[Tree] (config>service>sdp mixed-lsp-mode)
Full Context
configure service sdp mixed-lsp-mode
Description
This command enables the use by an SDP of the mixed-LSP mode of operation. This command indicates to the service manager that it must allow a primary LSP type and a backup LSP type in the same SDP configuration. For example, the lsp and ldp commands are allowed concurrently in the SDP configuration. The user can configure one or two types of LSPs under the same SDP. Without this command, these commands are mutually exclusive.
The user can configure an RSVP LSP as a primary LSP type with an LDP LSP as a backup type. The user can also configure an RFC 8277 BGP LSP as a backup LSP type.
If the user configures an LDP LSP as a primary LSP type, then the backup LSP type must be an RFC 8277 BGP labeled route.
At any given time, the service manager programs only one type of LSP in the linecard that will activate it to forward service packets according to the following priority order:
-
RSVP LSP type. Up to 16 RSVP LSPs can be entered by the user and programmed by the service manager in ingress linecard to load balance service packets. This is the highest priority LSP type.
-
LDP LSP type. One LDP FEC programmed by the service manager but the ingress card can use up to 16 LDP ECMP paths for the FEC to load balance service packets when ECMP is enabled on the node.
-
BGP LSP type. One RFC 8277-labeled BGP prefix programmed by the service manager. The ingress card can use more than one next-hop for the prefix.
In the case of the RSVP/LDP SDP, the service manager will program the NHLFE(s) for the active LSP type preferring the RSVP LSP type over the LDP LSP type. If no RSVP LSP is configured or all configured RSVP LSPs go down, the service manager will re-program the card with the LDP LSP if available. If not, the SDP goes operationally down.
When a higher priority type LSP becomes available, the service manager reverts back to this LSP at the expiry of the sdp-revert-time timer or the failure of the currently active LSP, whichever comes first. The service manager then re-programs the card accordingly. If the infinite value is configured, then the SDP reverts to the highest priority type LSP only if the currently active LSP failed.
LDP uses a tunnel down damp timer which is set to three seconds by default. When the LDP LSP fails, the SDP will revert to the RSVP LSP type after the expiry of this timer. For an immediate switchover, this timer must be set to zero. Use the config>router>ldp>tunnel-down-damp-time command.
If the user changes the value of the sdp-revert-time timer, it will take effect only at the next use of the timer. Any timer which is outstanding at the time of the change will be restarted with the new value.
If class based forwarding is enabled for this SDP, the forwarding of the packets over the RSVP LSPs will be based on the FC of the packet as in current implementation. When the SDP activates the LDP LSP type, then packets are forwarded over the LDP ECMP paths using the regular hash routine.
In the case of the LDP/BGP SDP, the service manager will prefer the LDP LSP type over the BGP LSP type. The service manager will re-program the card with the BGP LSP if available otherwise it brings down the SDP operationally.
Also note the following difference in behavior of the LDP/BGP SDP compared to that of an RSVP/LDP SDP. For a given /32 prefix, only a single route will exist in the routing table: the IGP route or the BGP route. Thus, either the LDP FEC or the BGP label route is active at any given time. The impact of this is that the tunnel table needs to be re-programmed each time a route is deactivated and the other is activated. Furthermore, the SDP revert-time cannot be used since there is no situation where both LSP types are active for the same /32 prefix.
The no form of this command disables the mixed-LSP mode of operation. The user first has to remove one of the LSP types from the SDP configuration or the command will fail.
Default
no mixed-lsp-mode
Platforms
7705 SAR Gen 2
mka-hello-interval
mka-hello-interval
Syntax
mka-hello-interval interval
no mka-hello-interval
Context
[Tree] (config>macsec>conn-assoc>static-cak mka-hello-interval)
Full Context
configure macsec connectivity-association static-cak mka-hello-interval
Description
This command specifies the MKA hello interval.
The no form of this command disables the MKA hello interval.
Default
mka-hello-interval 2
Parameters
- interval
-
Specifies the MKA hello interval, in seconds.
Platforms
7705 SAR Gen 2
mka-key-server-priority
mka-key-server-priority
Syntax
mka-key-server-priority priority
no mka-key-server-priority
Context
[Tree] (config>macsec>conn-assoc>static-cak mka-key-server-priority)
Full Context
configure macsec connectivity-association static-cak mka-key-server-priority
Description
This command specifies the key server priority used by the MACsec Key Agreement (MKA) protocol to select the key server when MACsec is enabled using static connectivity association key (CAK) security mode.
The no form of this command disables the mka-key-server-priority.
Default
mka-key-server-priority 16
Parameters
- priority
-
Specifies the priority of the server.
Platforms
7705 SAR Gen 2
mld
mld
Syntax
[no] mld
Context
[Tree] (config>service>vprn mld)
Full Context
configure service vprn mld
Description
Commands in this context configure Multicast Listener Discovery (MLD) parameters.
The no form of this command disables MLD.
Default
no mld
Platforms
7705 SAR Gen 2
mld
Syntax
[no] mld
Context
[Tree] (config>router mld)
Full Context
configure router mld
Description
Commands in this context configure Multicast Listener Discovery (MLD) parameters.
The no form of the command disables MLD.
Default
no mld
Platforms
7705 SAR Gen 2
mld-snooping
mld-snooping
Syntax
mld-snooping
Context
[Tree] (config>service>vpls>allow-ip-int-bind mld-snooping)
[Tree] (config>service>vpls>sap mld-snooping)
[Tree] (config>service>vpls mld-snooping)
[Tree] (config>service>vpls>mesh-sdp mld-snooping)
[Tree] (config>service>vpls>spoke-sdp mld-snooping)
Full Context
configure service vpls allow-ip-int-bind mld-snooping
configure service vpls sap mld-snooping
configure service vpls mld-snooping
configure service vpls mesh-sdp mld-snooping
configure service vpls spoke-sdp mld-snooping
Description
Commands in this context configure MLD snooping parameters.
Platforms
7705 SAR Gen 2
mld-snooping
Syntax
[no] mld-snooping
Context
[Tree] (debug>service>id mld-snooping)
Full Context
debug service id mld-snooping
Description
This command enables and configures MLD-snooping debugging.
The no form of this command disables MLD-snooping debugging.
Platforms
7705 SAR Gen 2
mode
mode
Syntax
mode {dropped-only | ingr-and-dropped | egr-ingr-and-dropped}
no mode
Context
[Tree] (debug>router>local-dhcp-server mode)
[Tree] (debug>router>ip>dhcp6 mode)
[Tree] (debug>router>ip>dhcp mode)
Full Context
debug router local-dhcp-server mode
debug router ip dhcp6 mode
debug router ip dhcp mode
Description
This command debugs the DHCP tracing detail level.
Parameters
- dropped-only
-
Displays only dropped packets.
- ingr-and-dropped
-
Displays only ingress packet and dropped packets.
- egr-ingr-and-dropped
-
Displays ingress, egress and dropped packets.
Platforms
7705 SAR Gen 2
mode
Syntax
mode {strict | loose | strict-no-ecmp}
no mode
Context
[Tree] (config>service>vprn>if>ipv6>urpf-check mode)
[Tree] (config>service>vprn>nw-if>urpf-check mode)
[Tree] (config>service>ies>if>ipv6>urpf-check mode)
[Tree] (config>service>vprn>if>urpf-check mode)
[Tree] (config>service>ies>if>urpf-check mode)
Full Context
configure service vprn interface ipv6 urpf-check mode
configure service vprn network-interface urpf-check mode
configure service ies interface ipv6 urpf-check mode
configure service vprn interface urpf-check mode
configure service ies interface urpf-check mode
Description
This command specifies the mode of unicast RPF check.
The no form of this command reverts to the default (strict) mode.
Default
mode strict
Parameters
- strict
-
When specified, uRPF checks whether incoming packet has a source address that matches a prefix in the routing table, and whether the interface expects to receive a packet with this source address prefix.
- loose
-
In loose mode, uRPF checks whether incoming packet has source address with a corresponding prefix in the routing table. However, the loose mode does not check whether the interface expects to receive a packet with a specific source address prefix. This object is valid only when urpf-check is enabled.
- strict-no-ecmp
-
When a packet is received on an interface in this mode and the SA matches an ECMP route the packet is dropped by uRPF.
Platforms
7705 SAR Gen 2
mode
Syntax
mode {automatic | manual}
Context
[Tree] (config>port>dwdm>coherent mode)
Full Context
configure port dwdm coherent mode
Description
This command configures the mode used to compensate for chromatic dispersion.
Parameters
- automatic
-
Sets to automatic mode.
- manual
-
Sets to manual mode.
Platforms
7705 SAR Gen 2
mode
Syntax
mode {access | network | hybrid}
no mode
Context
[Tree] (config>lag mode)
[Tree] (config>port>ethernet mode)
Full Context
configure lag mode
configure port ethernet mode
Description
This command configures an Ethernet port, TDM channel, or SONET/SDH path (sub-port) for access, network, or hybrid mode operation.
An access port or channel is used for customer facing traffic on which services are configured. A Service Access Point (SAP) can only be configured on an access port or channel. When a port is configured for access mode, the appropriate encap-type must be specified to distinguish the services on the port or SONET path. Once an Ethernet port, a TDM channel or a SONET path has been configured for access mode, multiple services can be configured on the Ethernet port, a TDM channel or SONET path.
A network port or channel participates in the service provider transport or infrastructure network when a network mode is selected. When the network option is configured, the encap-type cannot be configured for the port/channel.
When network mode is selected on a SONET/SDH path, the appropriate control protocols are activated when the need arises. For example, configuring an IP interface on the SONET path activates IPCP while the removal of the IP interface causes the IPCP to be removed. The same applies for MPLS, MPLSCP, and OSICP. When configuring a SONET/SDH port, the mode command must be entered in the channel context or an error message is generated.
A hybrid Ethernet port allows the combination of network and access modes of operation on a per-VLAN basis and must be configured as either dot1q or QinQ encapsulation.
When the hybrid port is configured to the dot1q encapsulation, the user configures a SAP inside a service simply by providing the SAP ID which must include the port-id value of the hybrid mode port and an unused VLAN tag value. The format is <port-id>:qtag1. A SAP of format <port-id>:* also supported.
The user configures a network IP interface under config>router>if>port by providing the port name which consists of the port-id of the hybrid mode port and an unused VLAN tag value. The format is <port-id>:qtag1. The user must explicitly enter a valid value for qtag1. The <port-id>:* value is not supported on a network IP interface. The 4096 VLAN tag space on the port is shared among VLAN SAPs and VLAN network IP interfaces.
When the hybrid port is configured to QinQ encapsulation, the user configures a SAP inside a service simply by providing the SAP ID which must include the port-id value of the hybrid mode port and the outer and inner VLAN tag values. The format is <port-id>:qtag1.qtag2. A SAP of format <port-id>: qtag1.* is also supported. The outer VLAN tag value must not have been used to create an IP network interface on this port. In addition, the qtag1.qtag2 value combination must not have been used by another SAP on this port.
The user configures a network IP interface under config>router>if>port by providing the port name which consists of the port-id of the hybrid mode port and a VLAN tag value. The format is <port-id>:qtag1.*. An outer VLAN tag qtag2 of * creates an IP network interface. In addition, the qtag1.qtag2 value combination must not have been used on another SAP or IP network interface on this port.
The no form of this command restores the default.
Default
mode network — For Ethernet ports
mode access — For TDM channel or SONET paths
Parameters
- access
-
Configures the Ethernet port, TDM channel or SONET path as service access.
- network
-
Configures the Ethernet port, TDM channel or SONET path for transport network use.
- hybrid
-
Configures the Ethernet port for hybrid use.
Platforms
7705 SAR Gen 2
mode
Syntax
mode {rstp | comp-dot1w | dot1w | mstp | pmstp}
no mode
Context
[Tree] (config>service>vpls>stp mode)
[Tree] (config>service>template>vpls-template>stp mode)
Full Context
configure service vpls stp mode
configure service template vpls-template stp mode
Description
This command specifies the version of Spanning Tree Protocol the bridge is currently running.
See section Spanning Tree Operating Modes for more information about these modes.
The no form of this command returns the STP variant to the default.
Default
mode rstp
Parameters
- rstp
-
Corresponds to the Rapid Spanning Tree Protocol specified in IEEE 802.1D/D4-2003
- dot1w
-
Corresponds to the mode where the Rapid Spanning Tree is backward compatible with IEEE 802.1w
- compdot1w
-
Corresponds to the Rapid Spanning Tree Protocol in conformance with IEEE 802.1w
- mstp
-
Sets MSTP as the STP mode of operation. Corresponds to the Multiple Spanning Tree Protocol specified in 802.1Q REV/D5.0-09/200
- pmstp
-
The PMSTP mode is only supported in VPLS services where the M-VPLS flag is configured
Platforms
7705 SAR Gen 2
mode
Syntax
mode {dropped-only | ingr-and-dropped | egr-ingr-and-dropped}
no mode
Context
[Tree] (debug>service>id>igmp-snooping mode)
Full Context
debug service id igmp-snooping mode
Description
This command enables and configures the IGMP tracing mode.
The no form of this command disables the configures the IGMP tracing mode.
Platforms
7705 SAR Gen 2
mode
Syntax
mode {dropped-only | ingr-and-dropped | egr-ingr-and-dropped}
no mode
Context
[Tree] (debug>service>id>mld mode)
Full Context
debug service id mld-snooping mode
Description
This command enables and configures the MLD tracing mode.
The no form of this command disables the configures the MLD tracing mode.
Platforms
7705 SAR Gen 2
mode
Syntax
mode {auto | napt | one-to-one}
no mode
Context
[Tree] (config>service>vprn>nat>outside>pool mode)
Full Context
configure service vprn nat outside pool mode
Description
This command configures the mode of operation of this NAT address pool.
The mode value is only relevant while the value of pool type is equal to largeScale; while the value of pool type is equal to l2Aware, the mode of operation is always NAPT.
Default
mode auto
Parameters
- napt
-
Specifies NAPT (Network Address Port Translation)
- auto
-
The system selects the actual mode based upon other configuration parameters; the actual mode can be NAPT or 1:1 NAT (also known as 'Basic NAT').
- one-to-one
-
Indicates 1:1 NAT (also known as 'Basic NAT')
Platforms
7705 SAR Gen 2
mode
Syntax
mode {dropped-only | ingr-and-dropped | egr-ingr-and-dropped}
no mode
Context
[Tree] (debug>service>id>dhcp mode)
Full Context
debug service id dhcp mode
Description
This command configures the DHCP tracing mode.
The no form of the command disables debugging.
Parameters
- dropped-only
-
Only displays dropped packets.
- ingr-and-dropped
-
Only displays ingress packet and dropped packets.
- egr-ingr-and-dropped
-
Displays ingress, egress and dropped packets.
Platforms
7705 SAR Gen 2
mode
Syntax
mode {auto | napt | one-to-one}
no mode
Context
[Tree] (config>router>nat>outside>pool mode)
Full Context
configure router nat outside pool mode
Description
This command specifies the mode of operation of this NAT address pool.
The no form of the command reverts to the default.
Default
auto
Parameters
- {auto | napt | one-to-one}
-
Specifies the mode of operation of this NAT pool.
Platforms
7705 SAR Gen 2
mode
Syntax
mode {strict | loose | strict-no-ecmp}
Context
[Tree] (config>router>if>ipv6>urpf-check mode)
[Tree] (config>router>if>urpf-check mode)
Full Context
configure router interface ipv6 urpf-check mode
configure router interface urpf-check mode
Description
This command specifies the mode of unicast RPF check.
The no form of this command reverts to the default (strict) mode.
Default
mode strict
Parameters
- strict
-
When specified, uRPF checks whether incoming packet has a source address that matches a prefix in the routing table, and whether the interface expects to receive a packet with this source address prefix.
- loose
-
In loose mode, uRPF checks whether incoming packet has source address with a corresponding prefix in the routing table. However, the loose mode does not check whether the interface expects to receive a packet with a specific source address prefix. This object is valid only when urpf-check is enabled.
- strict-no-ecmp
-
When a packet is received on an interface in this mode and the SA matches an ECMP route the packet is dropped by uRPF.
Platforms
7705 SAR Gen 2
mode
Syntax
mode {ecmp-protected | linear}
no mode
Context
[Tree] (config>router>segment-routing>maintenance-policy mode)
Full Context
configure router segment-routing maintenance-policy mode
Description
This command specifies the data path programming and protection mechanism for SR policy candidate paths to which the maintenance policy is applied.
In both the linear mode and ecmp-protected modes, if two or more candidate paths of the same {headend, color, endpoint} and also have the same mode, then the best preference path is treated as the primary while the next best preference path is the standby. If a third path is present in the linear mode, then this is treated as a tertiary and also programmed in the IOM.
If the currently active path goes unavailable due to S-BFD, the system failovers to the next best preference available candidate path. If S-BFD is down on all segment lists of all programmed candidate paths of an SR Policy, then the SR Policy is marked as down in TTM.
If the default mode is specified, the router only programs the segment lists of the best preference paths in the IOM.
The no form of this command removes the configured mode.
Default
no mode
Parameters
- ecmp-protected
-
Specifies only the top two routes (paths) are programmed in the IOM. Up to 32 segment lists can be programmed for each path.
- linear
-
Specifies the top three routes are programmed in the IOM. Only one segment list is allowed per path.
Platforms
7705 SAR Gen 2
mode
Syntax
mode {target-defined | on-change | sample}
Context
[Tree] (config>system>telemetry>persistent-subscriptions>subscription mode)
Full Context
configure system telemetry persistent-subscriptions subscription mode
Description
This command configures the subscription path mode for telemetry notifications that are sent for the persistent subscription.
Default
mode target-defined
Parameters
- target-defined
-
Keyword specifying that target defined mode is used.
- on-change
-
Keyword specifying that on change mode is used.
- sample
-
Keyword specifying that sample mode is used.
Platforms
7705 SAR Gen 2
monitor-oper-group
monitor-oper-group
Syntax
monitor-oper-group name
no monitor-oper-group
Context
[Tree] (config>lag monitor-oper-group)
Full Context
configure lag monitor-oper-group
Description
This command, supported on access LAG only, specifies the operational group to monitor. The state of the operational group affects the state of this LAG. When the operational group is inactive, the state of the LAG goes down and the LAG uses the configured lag>standby-signaling mechanism (lacp or power-off) to signal the CE that the LAG is not available.
Default
no monitor-oper-group
Parameters
- name
-
Specifies the name of the oper-group, up to 32 characters.
Platforms
7705 SAR Gen 2
monitor-oper-group
Syntax
monitor-oper-group name
no monitor-oper-group
Context
[Tree] (config>service>vpls>sap monitor-oper-group)
[Tree] (config>service>vpls>spoke-sdp monitor-oper-group)
[Tree] (config>service>vpls>bgp>pw-template-binding monitor-oper-group)
[Tree] (config>service>vpls>site monitor-oper-group)
Full Context
configure service vpls sap monitor-oper-group
configure service vpls spoke-sdp monitor-oper-group
configure service vpls bgp pw-template-binding monitor-oper-group
configure service vpls site monitor-oper-group
Description
This command specifies the operational group to be monitored by the object under which it is configured. The oper-group name must be already configured under the config>service context before its name is referenced in this command.
The no form of this command removes the association.
Default
no monitor-oper-group
Parameters
- group-name
-
Specifies a character string of maximum 32 ASCII characters identifying the group instance.
Platforms
7705 SAR Gen 2
monitor-oper-group
Syntax
monitor-oper-group group-name
no monitor-oper-group
Context
[Tree] (config>service>epipe>spoke-sdp monitor-oper-group)
[Tree] (config>service>epipe>sap monitor-oper-group)
Full Context
configure service epipe spoke-sdp monitor-oper-group
configure service epipe sap monitor-oper-group
Description
This command specifies the operational group to be monitored by the object under which it is configured. The oper-group name must be already configured under the config>service context before its name is referenced in this command.
The no form of this command removes the association.
Parameters
- group-name
-
Specifies an oper group name.
Platforms
7705 SAR Gen 2
monitor-oper-group
Syntax
monitor-oper-group name
no monitor-oper-group
Context
[Tree] (config>service>ies>if monitor-oper-group)
Full Context
configure service ies interface monitor-oper-group
Description
This command specifies the operational group to be monitored by the object under which it is configured. The oper-group name must be already configured under the config>service context before its name is referenced in this command.
The no form of this command removes the association from the configuration.
Default
no monitor-oper-group
Parameters
- name
-
Specifies a character string of maximum 32 ASCII characters identifying the group instance.
Platforms
7705 SAR Gen 2
monitor-oper-group
Syntax
monitor-oper-group name
no monitor-oper-group
Context
[Tree] (config>service>vprn>if monitor-oper-group)
Full Context
configure service vprn interface monitor-oper-group
Description
This command specifies the operational group to be monitored by the object under which it is configured. The oper-group name must be already configured under the config>service context before its name is referenced in this command.
The no form of this command removes the association from the configuration.
Default
no monitor-oper-group
Parameters
- name
-
Specifies a character string, up to 32 ASCII characters, identifying the group instance.
Platforms
7705 SAR Gen 2
monitor-oper-group
Syntax
monitor-oper-group group-name family {ipv4 | ipv6} add [1..4294967295]
monitor-oper-group group-name family {ipv4 | ipv6} set [1..4294967295]
monitor-oper-group group-name family {ipv4 | ipv6} subtract [1..4294967295]
no monitor-oper-group [family {ipv4 | ipv6}]
Context
[Tree] (config>service>vprn>pim>if monitor-oper-group)
Full Context
configure service vprn pim interface monitor-oper-group
Description
This command configures PIM to monitor the state of an operational group to provide a redundancy mechanism. PIM monitors the operational group and changes its DR priority to the specified value when the status of the operational group is up. This enables the router to become the PIM DR only when the operational group is up. If the operational group status changes to down, PIM changes its DR priority to the default or the value configured with priority under config>service>vprn>pim>if. The oper-group group-name must already be configured under the config>service context before its name is referenced in this command. Two operational groups are supported per PIM interface.
The no form of this command removes the operational group from the configuration.
Parameters
- group-name
-
Specifies the operational group identifier up to 32 characters in length.
- family
-
Specifies the address family.
- ipv4
-
Specifies the IPv4 designated router priority.
- ipv6
-
Specifies the IPv6 designated router priority.
- add
-
Specifies that the value is to be added to the existing priority to become the designated router.
- subtract
-
Specifies that the value is to be subtracted from the existing priority to become the designated router.
- set
-
Specifies the priority to become the designated router.
- value
-
Specifies the priority modifier expressed as a decimal integer.
Platforms
7705 SAR Gen 2
monitor-oper-group
Syntax
monitor-oper-group group-name family {ipv4 | ipv6} add [value]
monitor-oper-group group-name family {ipv4 | ipv6} set [value]
monitor-oper-group group-name family {ipv4 | ipv6} subtract [value]
no monitor-oper-group [family {ipv4 | ipv6}]
Context
[Tree] (config>router>pim>if monitor-oper-group)
Full Context
configure router pim interface monitor-oper-group
Description
This command configures PIM to monitor the state of an operational group to provide a redundancy mechanism. PIM monitors the operational group and changes its DR priority to the specified value when the status of the operational group is up. This enables the router to become the PIM DR only when the operational group is up. If the operational group status changes to down, PIM changes its DR priority to the default or the value configured with priority under config>router>pim>if. The oper-group group-name must already be configured under the config>service context before its name is referenced in this command. Two operational groups are supported per PIM interface.
The no form of this command removes the operational group from the configuration.
Parameters
- group-name
-
Specifies the operational group identifier, up to 32 characters.
- family
-
Specifies the address family.
- ipv4
-
Specifies the IPv4 designated router priority.
- ipv6
-
Specifies the IPv6 designated router priority.
- add
-
Specifies that the value is to be added to the existing priority to become the designated router.
- subtract
-
Specifies that the value is to be subtracted from the existing priority to become the designated router.
- set
-
Specifies the priority to become the designated router.
- value
-
Specifies the priority modifier expressed as a decimal integer.
Platforms
7705 SAR Gen 2
monitor-oper-group
Syntax
monitor-oper-group group-name
no monitor-oper-group
Context
[Tree] (config>port monitor-oper-group)
Full Context
configure port monitor-oper-group
Description
This command configures the operational group to monitor the operational group state. The state of the operational group affects the state of this port. When the operational group is inactive, the state of the port goes down and powers off the port to signal the CE that the connected port is not available.
Default
no monitor-oper-group
Parameters
- group-name
-
Specifies operational group name to monitor, up to 32 characters.
Platforms
7705 SAR Gen 2
month
month
Syntax
month {month-number [..month-number] | month-name [..month-name] | all}
no month
Context
[Tree] (config>system>cron>sched month)
Full Context
configure system cron schedule month
Description
This command specifies the month when the event should be executed. Multiple months can be specified. When multiple months are configured, each of them will cause the schedule to trigger. If a month is configured without configuring the month, weekday, day-of-month, and minute, the event will not execute.
The no form of this command removes the specified month from the configuration.
Default
no month
Parameters
- month-number
-
Specifies a month number.
- month-name
-
Specifies a month by name.
- all
-
Specifies all months.
Platforms
7705 SAR Gen 2
more
more
Syntax
[no] more
Context
[Tree] (environment more)
Full Context
environment more
Description
This command enables per-screen CLI output, meaning that the output is displayed on a screen-by- screen basis. The terminal screen length can be modified with the terminal command.
The following prompt appears at the end of each screen of paginated output:
Press any key to continue (Q to quit)
The no form of the command displays the output all at once. If the output length is longer than one screen, the entire output will be displayed, which may scroll the screen.
Default
more
Platforms
7705 SAR Gen 2
more
Syntax
[no] more
Context
[Tree] (config>system>management-interface>cli>md-cli>environment more)
Full Context
configure system management-interface cli md-cli environment more
Description
This command configures pagination of the output text.
The no form of this command reverts to the default value.
Default
more
Platforms
7705 SAR Gen 2
motd
motd
Syntax
motd {url url-prefix: source-url | text motd-text-string}
no motd
Context
[Tree] (config>system>login-control motd)
Full Context
configure system login-control motd
Description
This command creates the message of the day displayed after a successful console login. Only one message can be configured.
The no form of this command removes the message.
Default
no motd
Parameters
- url url-prefix: source-url
-
When the message of the day is present as a text file, provide both url-prefix and the source-url of the file containing the message of the day. The URL prefix can be local or remote.
- text motd-text-string
-
Specifies the text of the message of the day. The motd-text-string must be enclosed in double quotes. Multiple text strings are not appended to one another.
Some special characters can be used to format the message text. The \n character can be used to create multi-line messages. A \n in the message moves to the beginning of the next line by sending ASCII/UTF-8 chars 0xA (LF) and 0xD (CR) to the client terminal. An \r in the message sends the ASCII/UTF-8 char 0xD (CR) to the client terminal.
Platforms
7705 SAR Gen 2
move
move
Syntax
move old-file-url new-file-url [force] [no-redirect] [client-tls-profile profile] [proxy proxy-url]
Context
[Tree] (file move)
Full Context
file move
Description
This command moves a local file, system file, or a directory. If the target already exists, the command fails and an error message displays.
The following prompt appears if the destination file already exists:
"Overwrite destination file (y/n)?”
Parameters
- old-file-url
-
Specifies the file or directory to be moved.
- new-file-url
-
Specifies the new destination to place the old-file-url.
- force
-
Forces an immediate move of the specified file(s).
The file move force command moves the specified file(s) without displaying a user prompt message. This command also automatically accepts HTTP redirects unless overridden by the no-redirect parameter.
- profile
-
Specifies the TLS client profile configured under config>system>security>tls>client-tls-profile to use.
- proxy-url
-
Specifies the URL of an HTTP proxy. For example, http://proxy.mydomain.com:8000. This URL must be an HTTP URL and not an HTTPS URL.
- no-redirect
-
Specifies to automatically refuse any HTTP redirects without prompting the user.
Platforms
7705 SAR Gen 2
move-frequency
move-frequency
Syntax
move-frequency frequency
no move-frequency
Context
[Tree] (config>service>vpls>mac-move move-frequency)
[Tree] (config>service>template>vpls-template>mac-move move-frequency)
Full Context
configure service vpls mac-move move-frequency
configure service template vpls-template mac-move move-frequency
Description
This command indicates the maximum rate at which MACs can be relearned in the VPLS service before the SAP where the moving MAC was last seen is automatically disabled to protect the system against undetected loops or duplicate MACs. The rate (relearns per second) is measured in a 5-second window.
The no form of this command reverts to the default value.
Default
2 (relearns per second, when mac-move is enabled). For example, the value 2 requires 10 MAC relearns in a 5-second period for the MAC to be considered duplicate.
Parameters
- frequency
-
Specifies the rate, in relearns per second.
Platforms
7705 SAR Gen 2
mp-bgp-keep
mp-bgp-keep
Syntax
[no] mp-bgp-keep
Context
[Tree] (config>router>bgp mp-bgp-keep)
Full Context
configure router bgp mp-bgp-keep
Description
As a result of enabling this command, route refresh messages are no longer needed, or issued when VPN route policy changes are made; RIB-IN will retain all MP-BGP routes.
The no form of this command is used to disable this feature.
Default
no mp-bgp-keep
Platforms
7705 SAR Gen 2
mpls
mpls
Syntax
mpls [bgp bgp] [endpoint endpoint-name]
no mpls [bgp bgp]
Context
[Tree] (config>service>vprn>bgp-evpn mpls)
[Tree] (config>service>epipe>bgp-evpn mpls)
[Tree] (config>service>vpls>bgp-evpn mpls)
Full Context
configure service vprn bgp-evpn mpls
configure service epipe bgp-evpn mpls
configure service vpls bgp-evpn mpls
Description
Commands in this context configure the BGP EVPN MPLS parameters. In VPLS, either instance BGP 1 or BGP 2 can be configured, but not both simultaneously in the same service. Epipe and VPRN services only support instance 1. If the bgp bgp parameter is not specified, the instance is set to 1.
The endpoint option is only supported for Epipe services. When configured, the same endpoint name can be configured for the bgp-evpn>mpls context and an additional spoke SDP. An EVPN MPLS destination always has higher preference than a spoke SDP.
The no form of this command removes the MPLS instance from the service.
Parameters
- bgp
-
Indicates the BGP instance identifier.
- endpoint-name
-
Specifies the endpoint name for Epipe services, up to 32 characters.
Platforms
7705 SAR Gen 2
mpls
Syntax
mpls
Context
[Tree] (config>service>vprn>bgp-ipvpn mpls)
Full Context
configure service vprn bgp-ipvpn mpls
Description
Commands in this context configure the BGP IPVPN parameters.
Platforms
7705 SAR Gen 2
mpls
Syntax
[no] mpls
Context
[Tree] (config>router mpls)
Full Context
configure router mpls
Description
Commands in this context configure MPLS parameters. MPLS is not enabled by default and must be explicitly enabled (no shutdown).
The no form of this command deletes this MPLS protocol instance and removes all configuration parameters for this MPLS instance.
You must remove all SDP bindings and use the shutdown command to administratively disable the MPLS instance before deleting it.
Platforms
7705 SAR Gen 2
mpls
Syntax
mpls [lsp lsp-name] [sender source-address] [endpoint endpoint-address] [tunnel-id tunnel-id] [lsp-id lsp-id]
no mpls
Context
[Tree] (debug>router mpls)
Full Context
debug router mpls
Description
This command enables and configures debugging for MPLS.
Parameters
- lsp lsp-name
-
Specifies the LSP name up to 64 characters in length.
- sender source-address
-
Specifies the IP address of the sender.
- endpoint endpoint-address
-
Specifies the far-end IP address.
- tunnel-id tunnel-id
-
Specifies the MPLS SDP ID.
- lsp-id lsp-id
-
Specifies the LSP ID.
Platforms
7705 SAR Gen 2
mpls
Syntax
[no] mpls
Context
[Tree] (config>oam-pm>session>ip>tunnel mpls)
Full Context
configure oam-pm session ip tunnel mpls
Description
Commands in this context configure the MPLS packet tunneling options for the session. Configure the tunnel oam-pm session ip router-instance to Base to configure commands in the MPLS context. When entering a context under MPLS, the system removes any previous configuration of any sibling context. You can only configure one of the contexts for each OAM-PM session.
The no form of this command deletes the mpls context and all configurations under it.
Platforms
7705 SAR Gen 2
mpls-echo-request-downstream-map
mpls-echo-request-downstream-map
Syntax
mpls-echo-request-downstream-map {dsmap | ddmap}
Context
[Tree] (config>test-oam mpls-echo-request-downstream-map)
Full Context
configure test-oam mpls-echo-request-downstream-map
Description
This command specifies which format of the downstream mapping TLV to use in all LSP trace packets and LDP tree trace packets originated on this node. The Downstream Mapping (DSMAP) TLV is the original format in RFC 4379 (obsoleted by RFC 8029) and is the default value. The new Downstream Detailed Mapping (DDMAP) TLV is the new enhanced format specified in RFC 6424 and RFC 8029.
This command applies to LSP trace of an RSVP P2P LSP, a MPLS-TP LSP, or LDP unicast FEC, and to LDP tree trace of a unicast LDP FEC. It does not apply to LSP trace of an RSVP P2MP LSP which always uses the DDMAP TLV.
The global DSMAP/DDMAP setting impacts the behavior of both OAM LSP trace packets and SAA test packets of type lsp-trace and is used by the sender node when one of the following events occurs:
-
An SAA test of type lsp-trace is created (not modified) and no value is specified for the per-test downstream-map-tlv {dsmap | ddmap | none} option. In this case, the SAA test downstream-map-tlv value defaults to the global mpls-echo-request-downstream-map value.
-
An OAM test of type lsp-trace test is executed and no value is specified for the per-test downstream-map-tlv {dsmap | ddmap | none} option. In this case, the OAM test downstream-map-tlv value defaults to the global mpls-echo-request-downstream-map value.
A consequence of the rules above is that a change to the value of mpls-echo-request-downstream-map option does not affect the value inserted in the downstream mapping TLV of existing tests.
Following are the details of the processing of the new DDMAP TLV:
-
When either the DSMAP TLV or the DDMAP TLV is received in an echo request message, the responder node includes the same type of TLV in the echo reply message with the proper downstream interface information and label stack information.
-
If an echo request message without a Downstream Mapping TLV (DSMAP or DDMAP) expires at a node which is not the egress for the target FEC stack, the responder node always includes the DSMAP TLV in the echo reply message. This can occur in the following cases:
-
The user issues a LSP trace from a sender node with a min-ttl value higher than 1 and a max-ttl value lower than the number of hops to reach the egress of the target FEC stack. This is the sender node behavior when the global configuration or the per-test setting of the DSMAP/DDMAP is set to DSMAP.
-
The user issues a LSP ping from a sender node with a ttl value lower than the number of hops to reach the egress of the target FEC stack. This is the sender node behavior when the global configuration of the DSMAP/DDMAP is set to DSMAP.
-
The behavior in (a) is changed when the global configuration or the per-test setting of the Downstream Mapping TLV is set to DDMAP. The sender node includes in this case the DDMAP TLV with the Downstream IP address field set to the all-routers multicast address as per Section 3.4 of RFC 8029. The responder node then bypasses the interface and label stack validation and replies with a DDMAP TLV with the correct downstream information for the target FEC stack.
-
-
A sender node never includes the DSMAP or DDMAP TLV in an lsp-ping message.
In addition to performing the same features as the DSMAP TLV, the new DDMAP TLV addresses the following scenarios:
-
Full validation of an LDP FEC stitched to a BGP IPv4 label route. In this case, the LSP trace message is inserted from the LDP LSP segment or from the stitching point.
-
Full validation of a BGP IPv4 label route stitched to an LDP FEC. This includes the case of explicit configuration of the LDP-BGP stitching in which the BGP label route is active in Route Table Manager (RTM) and the case of a BGP IPv4 label route resolved to the LDP FEC due to the IGP route of the same prefix active in RTM. In this case, the LSP trace message is inserted from the BGP LSP segment or from the stitching point.
-
Full validation of an LDP FEC which is stitched to a BGP LSP and stitched back into an LDP FEC. In this case, the LSP trace message is inserted from the LDP segments or the or from the stitching points.
-
Full validation of an LDP FEC tunneled over an RSVP LSP using LSP trace.
To properly check a target FEC which is stitched to another FEC (stitching FEC) of the same or a different type, or which is tunneled over another FEC (tunneling FEC), it is necessary for the responding nodes to provide details about the FEC manipulation back to the sender node. This is achieved via the use of the new FEC stack change sub-TLV in the Downstream Detailed Mapping TLV (DDMAP) defined in RFC 6424.
When the user configures the use of the DDMAP TLV on a trace for an LSP that does not undergo stitching or tunneling operation in the network, the procedures at the sender and responder nodes are the same as in the case of the DSMAP TLV.
This feature however introduces changes to the target FEC stack validation
procedures at the sender and responder nodes in the case of LSP stitching
and LSP hierarchy. These changes pertain to the processing of the new FEC
stack change sub-TLV in the new DDMAP TLV and the new return code of value
15 Label switched with FEC change.
The no form of this command reverts to the default behavior of using the DSMAP TLV in a LSP trace packet and LDP tree trace packet.
Default
mpls-echo-request-downstream-map dsmap
Parameters
- dsmap
-
Specifies that the DSMAP TLV should be used in all LSP trace packets and LDP tree trace packets originating on the node.
- ddmap
-
Specifies that the DDMAP TLV should be used in all LSP trace packets and LDP tree trace packets originating on the node.
Platforms
7705 SAR Gen 2
Output
The following output is an example of mpls-echo-request-downstream-map information.
Output Example: LDP-over-RSVPA B D F E C
o -------- o -------- o -------- o -------- o -------- o
| \______/ | \____________________________/ | \______/ |
\ RSVP / LDP \ RSVP /
\______/ \______/
LDP LDP
Testing LDP FEC of Node C with DSMAP TLV
----------------------------------------
*A:Dut-A#
*A:Dut-A# oam lsp-trace prefix 10.20.1.3/32 downstream-map-tlv dsmap detail
lsp-trace to 10.20.1.3/32: 0 hops min, 0 hops max, 104 byte packets
1 10.20.1.2 rtt=3.90ms rc=8(DSRtrMatchLabel) rsc=1
DS 1: ipaddr=10.10.4.4 ifaddr=10.10.4.4 iftype=ipv4Numbered MRU=1500
label[1]=131068 protocol=3(LDP)
2 10.20.1.4 rtt=5.69ms rc=8(DSRtrMatchLabel) rsc=1
DS 1: ipaddr=10.10.9.6 ifaddr=10.10.9.6 iftype=ipv4Numbered MRU=1500
label[1]=131066 protocol=3(LDP)
3 10.20.1.6 rtt=7.88ms rc=8(DSRtrMatchLabel) rsc=1
DS 1: ipaddr=10.10.10.5 ifaddr=10.10.10.5 iftype=ipv4Numbered MRU=1500
label[1]=131060 protocol=3(LDP)
4 10.20.1.5 rtt=23.2ms rc=8(DSRtrMatchLabel) rsc=1
DS 1: ipaddr=10.10.5.3 ifaddr=10.10.5.3 iftype=ipv4Numbered MRU=1496
label[1]=131071 protocol=3(LDP)
5 10.20.1.3 rtt=12.0ms rc=3(EgressRtr) rsc=1
*A:Dut-A#
Testing LDP FEC of Node C with DDMAP TLV
----------------------------------------
*A:Dut-A# oam lsp-trace prefix 10.20.1.3/32 downstream-map-tlv ddmap detail
lsp-trace to 10.20.1.3/32: 0 hops min, 0 hops max, 136 byte packets
1 10.20.1.2 rtt=4.00ms rc=3(EgressRtr) rsc=2
1 10.20.1.2 rtt=3.48ms rc=8(DSRtrMatchLabel) rsc=1
DS 1: ipaddr=10.10.4.4 ifaddr=10.10.4.4 iftype=ipv4Numbered MRU=1500
label[1]=131068 protocol=3(LDP)
2 10.20.1.4 rtt=5.34ms rc=8(DSRtrMatchLabel) rsc=1
DS 1: ipaddr=10.10.9.6 ifaddr=10.10.9.6 iftype=ipv4Numbered MRU=1500
label[1]=131066 protocol=3(LDP)
3 10.20.1.6 rtt=7.78ms rc=8(DSRtrMatchLabel) rsc=1
DS 1: ipaddr=10.10.10.5 ifaddr=10.10.10.5 iftype=ipv4Numbered MRU=1500
label[1]=131060 protocol=3(LDP)
4 10.20.1.5 rtt=12.8ms rc=15(LabelSwitchedWithFecChange) rsc=1
DS 1: ipaddr=10.10.5.3 ifaddr=10.10.5.3 iftype=ipv4Numbered MRU=1496
label[1]=131054 protocol=4(RSVP-TE)
label[2]=131071 protocol=3(LDP)
fecchange[1]=PUSH fectype=RSVP IPv4 prefix=10.20.1.3 remotepeer=10.10.5.3
5 10.20.1.3 rtt=12.8ms rc=3(EgressRtr) rsc=2
5 10.20.1.3 rtt=13.4ms rc=3(EgressRtr) rsc=1
*A:Dut-A#
D F E C A B
o -------- o -------- o -------- o -------- o -------- o
\_________________/ | \_________________/ | \______/ |
LDP \ RSVP ECA / \ RSVP /
\_________________/ \______/
LDP LDP
Testing LDP FEC of Node B with DDMAP TLV
----------------------------------------
*A:Dut-D#
*A:Dut-D# oam lsp-trace prefix 10.20.1.2/32 downstream-map-tlv ddmap detail
lsp-trace to 10.20.1.2/32: 0 hops min, 0 hops max, 108 byte packets
1 10.20.1.6 rtt=3.17ms rc=8(DSRtrMatchLabel) rsc=1
DS 1: ipaddr=10.10.10.5 ifaddr=10.10.10.5 iftype=ipv4Numbered MRU=1500
label[1]=131065 protocol=3(LDP)
2 10.20.1.5 rtt=8.27ms rc=15(LabelSwitchedWithFecChange) rsc=1
DS 1: ipaddr=10.10.5.3 ifaddr=10.10.5.3 iftype=ipv4Numbered MRU=1496
label[1]=131068 protocol=4(RSVP-TE)
label[2]=131065 protocol=3(LDP)
fecchange[1]=PUSH fectype=RSVP IPv4 prefix=10.20.1.1 remotepeer=10.10.5.3
3 10.20.1.3 rtt=9.50ms rc=8(DSRtrMatchLabel) rsc=2
DS 1: ipaddr=10.10.2.1 ifaddr=10.10.2.1 iftype=ipv4Numbered MRU=1500
label[1]=131068 protocol=4(RSVP-TE)
4 10.20.1.1 rtt=10.4ms rc=3(EgressRtr) rsc=2
4 10.20.1.1 rtt=10.2ms rc=15(LabelSwitchedWithFecChange) rsc=1
DS 1: ipaddr=10.10.1.2 ifaddr=10.10.1.2 iftype=ipv4Numbered MRU=1496
label[1]=131066 protocol=4(RSVP-TE)
label[2]=131071 protocol=3(LDP)
fecchange[1]=PUSH fectype=RSVP IPv4 prefix=10.20.1.2 remotepeer=10.10.1.2
5 10.20.1.2 rtt=13.7ms rc=3(EgressRtr) rsc=2
5 10.20.1.2 rtt=13.6ms rc=3(EgressRtr) rsc=1
*A:Dut-D#
A B C D E F
o ------- o -------- o --------- o ------- o ------- o
\_____/ | \_______/ | \_____/
LDP | RSVP | LDP
|\______________________________/|
| LDP |
\______________________________/
BGP
Testing LDP FEC of Node F with DSMAP TLV
----------------------------------------
*A:Dut-A# *A:Dut-A# oam lsp-trace prefix 10.20.1.6/32 downstream-map-
tlv dsmap detail lsp-trace to 10.20.1.6/32: 0 hops min, 0 hops max, 104 byte packets
1 10.20.1.2 rtt=2.65ms rc=8(DSRtrMatchLabel) rsc=1
2 10.20.1.3 rtt=4.89ms rc=8(DSRtrMatchLabel) rsc=1
3 10.20.1.4 rtt=6.49ms rc=5(DSMappingMismatched) rsc=1
*A:Dut-A#
Testing LDP FEC of Node F with DDMAP TLV
----------------------------------------
*A:Dut-A# oam lsp-trace prefix 10.20.1.6/32 downstream-map-tlv ddmap detail lsp-
trace to 10.20.1.6/32: 0 hops min, 0 hops max, 108 byte packets
1 10.20.1.2 rtt=3.50ms rc=15(LabelSwitchedWithFecChange) rsc=1
DS 1: ipaddr=10.10.3.3 ifaddr=10.10.3.3 iftype=ipv4Numbered MRU=1496
label[1]=131068 protocol=3(LDP)
label[2]=131060 protocol=2(BGP)
fecchange[1]=POP fectype=LDP IPv4 prefix=10.20.1.6 remotepeer=0.0.0.0
(Unknown)
fecchange[2]=PUSH fectype=BGP IPv4 prefix=10.20.1.6 remotepeer=10.20.1.5
fecchange[3]=PUSH fectype=LDP IPv4 prefix=10.20.1.5 remotepeer=10.10.3.3
2 10.20.1.3 rtt=6.53ms rc=15(LabelSwitchedWithFecChange) rsc=2
DS 1: ipaddr=10.10.11.4 ifaddr=10.10.11.4 iftype=ipv4Numbered MRU=1496
label[1]=131060 protocol=4(RSVP-TE)
label[2]=131070 protocol=3(LDP)
label[3]=131060 protocol=2(BGP)
fecchange[1]=PUSH fectype=RSVP IPv4 prefix=10.20.1.4 remotepeer=10.10.11.4
3 10.20.1.4 rtt=7.94ms rc=3(EgressRtr) rsc=3
3 10.20.1.4 rtt=6.69ms rc=8(DSRtrMatchLabel) rsc=2
DS 1: ipaddr=10.10.6.5 ifaddr=10.10.6.5 iftype=ipv4Numbered MRU=1500
label[1]=131071 protocol=3(LDP)
label[2]=131060 protocol=2(BGP)
4 10.20.1.5 rtt=10.1ms rc=3(EgressRtr) rsc=2
4 10.20.1.5 rtt=8.97ms rc=15(LabelSwitchedWithFecChange) rsc=1
DS 1: ipaddr=10.10.10.6 ifaddr=10.10.10.6 iftype=ipv4Numbered MRU=1500
label[1]=131071 protocol=3(LDP)
fecchange[1]=POP fectype=BGP IPv4 prefix=10.20.1.6 remotepeer=0.0.0.0
(Unknown)
fecchange[2]=PUSH fectype=LDP IPv4 prefix=10.20.1.6 remotepeer=10.10.10.6
5 10.20.1.6 rtt=11.8ms rc=3(EgressRtr) rsc=1 *A:Dut-A#
A B C D E
o ------- o -------- o --------- o ---3--- o
\_____/ | \_______/ |
LDP | RSVP |
|\______________________________/|
| LDP |
\______________________________/
BGP
Testing BGP Label Route of Node E with DDMAP TLV
-------------------------------------------------
*A:Dut-B# oam lsp-trace prefix 11.20.1.5/32 bgp-label downstream-map-
tlv ddmap detail lsp-trace to 11.20.1.5/32: 0 hops min, 0 hops max, 124 byte packets
1 10.20.1.3 rtt=2.35ms rc=15(LabelSwitchedWithFecChange) rsc=2
DS 1: ipaddr=10.10.11.4 ifaddr=10.10.11.4 iftype=ipv4Numbered MRU=1496
label[1]=131060 protocol=4(RSVP-TE)
label[2]=131070 protocol=3(LDP)
label[3]=131070 protocol=2(BGP)
fecchange[1]=PUSH fectype=RSVP IPv4 prefix=10.20.1.4 remotepeer=10.10.11.4
2 10.20.1.4 rtt=4.17ms rc=3(EgressRtr) rsc=3
2 10.20.1.4 rtt=4.50ms rc=8(DSRtrMatchLabel) rsc=2
DS 1: ipaddr=10.10.6.5 ifaddr=10.10.6.5 iftype=ipv4Numbered MRU=1500
label[1]=131071 protocol=3(LDP)
label[2]=131070 protocol=2(BGP)
3 10.20.1.5 rtt=7.78ms rc=3(EgressRtr) rsc=2
3 10.20.1.5 rtt=6.80ms rc=3(EgressRtr) rsc=1 *A:Dut-B#
B C D E F
o -------- o --------- o ---3--- o ---3--- o
| \_______/ | \_____/
| RSVP |
|\______________________________/|
| LDP |
\______________________________/
BGP
Testing with DDMAP TLV LDP FEC of Node F when stitched to a BGP Label Route
----------------------------------------------------------------------------
*A:Dut-B# oam lsp-trace prefix 10.20.1.6/32 bgp-label downstream-map-
tlv ddmap detail lsp-trace to 10.20.1.6/32: 0 hops min, 0 hops max, 124 byte packets
1 10.20.1.3 rtt=3.21ms rc=15(LabelSwitchedWithFecChange) rsc=2
DS 1: ipaddr=10.10.11.4 ifaddr=10.10.11.4 iftype=ipv4Numbered MRU=1496
label[1]=131060 protocol=4(RSVP-TE)
label[2]=131070 protocol=3(LDP)
label[3]=131060 protocol=2(BGP)
fecchange[1]=PUSH fectype=RSVP IPv4 prefix=10.20.1.4 remotepeer=10.10.11.4
2 10.20.1.4 rtt=5.50ms rc=3(EgressRtr) rsc=3
2 10.20.1.4 rtt=5.37ms rc=8(DSRtrMatchLabel) rsc=2
DS 1: ipaddr=10.10.6.5 ifaddr=10.10.6.5 iftype=ipv4Numbered MRU=1500
label[1]=131071 protocol=3(LDP)
label[2]=131060 protocol=2(BGP)
3 10.20.1.5 rtt=7.82ms rc=3(EgressRtr) rsc=2
3 10.20.1.5 rtt=6.11ms rc=15(LabelSwitchedWithFecChange) rsc=1
DS 1: ipaddr=10.10.10.6 ifaddr=10.10.10.6 iftype=ipv4Numbered MRU=1500
label[1]=131071 protocol=3(LDP)
fecchange[1]=POP fectype=BGP IPv4 prefix=10.20.1.6 remotepeer=0.0.0.0
(Unknown)
fecchange[2]=PUSH fectype=LDP IPv4 prefix=10.20.1.6 remotepeer=10.10.10.6
4 10.20.1.6 rtt=10.2ms rc=3(EgressRtr) rsc=1 *A:Dut-B#
mpls-label
mpls-label
Syntax
mpls-label value
no mpls-label
Context
[Tree] (conf>router>segment-routing>sr-policies>policy>seg-list>segment mpls-label)
Full Context
configure router segment-routing sr-policies static-policy segment-list segment mpls-label
Description
This command configures the MPLS label value this is associated with a segment.
The no form of this command removes the label value.
Default
no mpls-label
Parameters
- value
-
Specifies the MPLS label value.
Platforms
7705 SAR Gen 2
mpls-labels
mpls-labels
Syntax
mpls-labels
Context
[Tree] (config>router mpls-labels)
Full Context
configure router mpls-labels
Description
This command creates a context for the configuration of global parameters related to MPLS labels.
Platforms
7705 SAR Gen 2
mpls-time-stamp-format
mpls-time-stamp-format
Syntax
mpls-time-stamp-format {rfc4379 | unix}
Context
[Tree] (config>test-oam mpls-time-stamp-format)
Full Context
configure test-oam mpls-time-stamp-format
Description
This command configures the format of the timestamp used by for lsp-ping, lsp-trace, p2mp-lsp-ping and p2mp-lsp-trace, vccv-ping, vccv-trace, and lsp-trace.
If rfc4379 is selected, then the timestamp is in seconds and microseconds since 1900, otherwise it is in seconds and microseconds since 1970.
Changing this system-wide setting does not affect tests that are currently in progress, but SAAs starts to use the new timestamp when they are restarted. When an SR OS receives an echo request, it replies with the locally configured timestamp format, and does not try to match the timestamp format of the incoming echo request message.
Default
mpls-time-stamp-format unix
Parameters
- rfc4379
-
Specifies the RFC 4379 (obsoleted by RFC 8029) time stamp format. The timestamp's seconds field holds the integral number of seconds since 1-Jan-1900 00:00:00 UTC. The timestamp's microseconds field contains a microseconds value in the range 0 to 999999. This setting is used to inter-operate with network elements which are fully compliant with RFC 4379, Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures, (such as an SR OS system with the same setting, or any other RFC 4379 compliant router).
- unix
-
Specifies the Unix time stamp format. The time stamps seconds field holds a Unix time, the integral number of seconds since 1-Jan-1970 00:00:00 UTC. The time stamps microseconds field contains a microseconds value in the range 0 to 999999. This setting is used to inter-operate with network elements which send and expect a 1970-based timestamp in MPLS Echo Request/Reply PDUs (such as an SR OS system with the same setting, or an SR OS system running software earlier than R8.0 R4).
Platforms
7705 SAR Gen 2
mrib
mrib
Syntax
mrib [group grp-ip-address] [source ip-address] [detail]
no mrib
Context
[Tree] (debug>router>pim mrib)
Full Context
debug router pim mrib
Description
This command enables debugging for PIM MRIB.
The no form of this command disables debugging for PIM MRIB.
Parameters
- grp-ip-address
-
Debugs information associated with the specified PIM MRIB.
- ip-address
-
Debugs information associated with the specified PIM MRIB.
- detail
-
Debugs detailed MRIB information.
Platforms
7705 SAR Gen 2
mrouter-port
mrouter-port
Syntax
[no] mrouter-port
Context
[Tree] (config>service>vpls>spoke-sdp>mld-snooping mrouter-port)
[Tree] (config>service>vpls>bind>mld-snooping mrouter-port)
[Tree] (config>service>vpls>spoke-sdp>igmp-snooping mrouter-port)
[Tree] (config>service>vpls>sap>igmp-snooping mrouter-port)
[Tree] (config>service>vpls>mesh-sdp>igmp-snooping mrouter-port)
Full Context
configure service vpls spoke-sdp mld-snooping mrouter-port
configure service vpls allow-ip-int-bind mld-snooping mrouter-port
configure service vpls spoke-sdp igmp-snooping mrouter-port
configure service vpls sap igmp-snooping mrouter-port
configure service vpls mesh-sdp igmp-snooping mrouter-port
Description
This command specifies whether a multicast router is attached behind this SAP, SDP, or routed VPLS IP interface.
Configuring these objects as an mrouter-port will have a double effect. Firstly, all multicast traffic received on another SAP, SDP, or routed VPLS IP interface will be copied to this SAP, SDP, or routed VPLS IP interface. Secondly, IGMP/MLD reports generated by the system as a result of a router joining or leaving a multicast group, will be sent to this SAP, SDP, or routed VPLS IP interface.
If two multicast routers exist in the network, one of them will become the active querier. While the other multicast router (non-querier) stops sending IGMP queries, it should still receive reports to keep its multicast trees up-to-date. To support this, the mrouter-port should be enabled on all SAPs, SDPs, or routed VPLS IP interfaces connecting to a multicast router.
The IGMP version to be used for the reports (v1, v2, or v3) can only be determined after an initial query has been received. Until such time, no reports are sent on the SAP, spoke-SDP, or routed VPLS IP interface, even if mrouter-port is enabled.
If the send-queries command is enabled on this SAP or spoke-SDP, the mrouter-port parameter cannot be set.
When PIM-snooping is enabled within a VPLS service, all IP multicast traffic and PIM messages will be sent to any SAP or SDP binding configured with an IGMP-snooping mrouter port. This occurs even without IGMP-snooping enabled, but is not supported in a BGP-VPLS or M-VPLS service.
The no form of this command reverts to the default.
Default
no mrouter-port
Platforms
7705 SAR Gen 2
msap-defaults
msap-defaults
Syntax
msap-default
Context
[Tree] (config>service>vpls>sap msap-defaults)
Full Context
configure service vpls sap msap-defaults
Description
This command configures MSAP authentication defaults.
Platforms
7705 SAR Gen 2
msg
msg
Syntax
[no] msg
Context
[Tree] (debug>router>pim msg)
Full Context
debug router pim msg
Description
This command enables debugging for PIM messaging.
The no form of this command disables debugging for PIM messaging.
Platforms
7705 SAR Gen 2
msg
Syntax
msg [detail]
no msg
Context
[Tree] (debug>router>pcep>pcc>conn msg)
[Tree] (debug>router>pcep>pcc msg)
Full Context
debug router pcep pcc connection msg
debug router pcep pcc msg
Description
This command enables debugging for PCC or connection messaging events.
The no form of this command disables debugging.
Parameters
- detail
-
Keyword used to specify detailed information about PCC or connection messaging events.
Platforms
7705 SAR Gen 2
msg-pacing
msg-pacing
Syntax
[no] msg-pacing
Context
[Tree] (config>router>rsvp msg-pacing)
Full Context
configure router rsvp msg-pacing
Description
This command enables RSVP message pacing in which the specified number of RSVP messages, specified in the max-burst command, are sent in a configured interval, specified in the period command. A count is kept of the messages that were dropped because the output queue for the interface used for message pacing was full.
Default
no msg-pacing
Platforms
7705 SAR Gen 2
mss-adjust-group
mss-adjust-group
Syntax
mss-adjust-group bb-group-id segment-size segment-size
no mss-adjust-group
Context
[Tree] (config>router mss-adjust-group)
[Tree] (config>service>vprn mss-adjust-group)
Full Context
configure router mss-adjust-group
configure service vprn mss-adjust-group
Description
This command associates the MSS adjust group consisting of multiple ISAs with the routing context in which the application requiring TCP MSS adjust resides.
Parameters
- bb-group-id
-
Specifies the group used for TCP MSS adjust
- segment-size
-
Specifies the value to put into the TCP Maximum Segment Size (MSS) option if it is not already present, or if the present value is higher
Platforms
7705 SAR Gen 2
mst-instance
mst-instance
Syntax
mst-instance mst-inst-number
Context
[Tree] (config>service>vpls>sap>stp mst-instance)
Full Context
configure service vpls sap stp mst-instance
Description
Commands in this context configure MSTI related parameters at SAP level. This context can be open only for existing mst-instances defined at the service level (see config>service>vpls>stp mst-instance).
Parameters
- mst-inst-number
-
Specifies an existing Multiple Spanning Tree Instance number.
Platforms
7705 SAR Gen 2
mst-instance
Syntax
mst-instance mst-inst-number [create]
no mst-instance [mst-inst-number]
Context
[Tree] (config>service>vpls>stp mst-instance)
Full Context
configure service vpls stp mst-instance
Description
This command creates the context to configure MST instance (MSTI) related parameters. Up to 16 instances will be supported by MSTP. The instance 0 is mandatory by protocol and therefore, it cannot be created by the CLI. The software will maintain this instance automatically.
Parameters
- mst-inst-number
-
Specifies the Multiple Spanning Tree instance
Platforms
7705 SAR Gen 2
mst-max-hops
mst-max-hops
Syntax
mst-max-hops hops-count
no mst-max-hops
Context
[Tree] (config>service>vpls>stp mst-max-hops)
Full Context
configure service vpls stp mst-max-hops
Description
This command specifies the number of hops in the region before BPDU is discarded and the information held for the port is aged out. The root bridge of the instance sends a BPDU (or M-record) with remaining-hop-count set to configured <max-hops>. When a bridge receives the BPDU (or M-record), it decrements the received remaining-hop-count by 1 and propagates it in BPDU (or M-record) it generates.
The no form of this command sets the hops-count to its default value.
Default
mst-max-hops 20
Parameters
- hops-count
-
Specifies the maximum number of hops.
Platforms
7705 SAR Gen 2
mst-name
mst-name
Syntax
mst-name region-name
no mst-name
Context
[Tree] (config>service>vpls>stp mst-name)
Full Context
configure service vpls stp mst-name
Description
This command defines an MST region name. Two bridges are considered as a part of the same MST region as soon as their configuration of the MST region name, the MST-revision and VLAN-to-instance assignment is identical.
The no form of this command removes region-name from the configuration.
Default
no mst-name
Parameters
- region-name
-
Specifies an MST-region name up to 32 characters in length.
Platforms
7705 SAR Gen 2
mst-path-cost
mst-path-cost
Syntax
mst-path-cost inst-path-cost
no mst-path-cost
Context
[Tree] (config>service>vpls>sap>stp>mst-instance mst-path-cost)
Full Context
configure service vpls sap stp mst-instance mst-path-cost
Description
This commands specifies path-cost within a specified instance, expressing probability that a specified port will be put into the forwarding state in case a loop occurs (the highest value expresses lowest priority).
The no form of this command sets port-priority to its default value.
Default
The path-cost is proportional to link speed.
Parameters
- inst-path-cost
-
Specifies the contribution of this port to the MSTI path cost of paths toward the spanning tree regional root that include this port.
Platforms
7705 SAR Gen 2
mst-port-priority
mst-port-priority
Syntax
mst-port-priority stp-priority
no mst-port-priority
Context
[Tree] (config>service>vpls>sap>stp>mst-instance mst-port-priority)
Full Context
configure service vpls sap stp mst-instance mst-port-priority
Description
This commands specifies the port priority within a specified instance, expressing probability that a specified port will be put into the forwarding state if a loop occurs.
The no form of this command sets port-priority to its default value.
Default
mst-port-priority 128
Parameters
- stp-priority
-
Specifies the value of the port priority field.
Platforms
7705 SAR Gen 2
mst-priority
mst-priority
Syntax
mst-priority bridge-priority
no mst-priority
Context
[Tree] (config>service>vpls>stp>mst-instance mst-priority)
Full Context
configure service vpls stp mst-instance mst-priority
Description
This command specifies the bridge priority for this specific Multiple Spanning Tree Instance for this service. The bridge-priority value reflects likelihood that the switch will be chosen as the regional root switch (65535 represents the least likely). It is used as the highest 4 bits of the Bridge ID included in the MSTP BPDUs generated by this bridge.
The priority can only take on values that are multiples of 4096 (4k). If a value is specified that is not a multiple of 4K, then the value will be replaced by the closest multiple of 4K, which is lower than the value entered.
All instances created by the configure service vpls stp mst-instance vlan-range command and not having explicit definition of bridge-priority inherit the default value.
The no form of this command sets the bridge-priority to its default value.
Default
mst-priority 32768
Parameters
- bridge-priority
-
Specifies the priority of this specific Multiple Spanning Tree Instance for this service.
Platforms
7705 SAR Gen 2
mst-revision
mst-revision
Syntax
mst-revision revision-number
no mst-revision
Context
[Tree] (config>service>vpls>stp mst-revision)
Full Context
configure service vpls stp mst-revision
Description
This command defines the MST configuration revision number. Two bridges are considered as a part of the same MST region as soon as their configuration of MST-region name, MST-revision and VLAN-to-instance assignment is identical.
The no form of this command returns MST configuration revision to its default value.
Default
mst-revision 0
Parameters
- revision-number
-
Specifies the MSTP region revision number to define the MSTP region.
Platforms
7705 SAR Gen 2
mtu
mtu
Syntax
mtu bytes
no mtu
Context
[Tree] (config>service>vprn>router-advert>if mtu)
[Tree] (config>router>router-advert>if mtu)
Full Context
configure service vprn router-advertisement interface mtu
configure router router-advertisement interface mtu
Description
This command specifies the value to be placed in link MTU options sent by the router on this interface.
The no form of this command reverts to the default.
Default
no mtu — The MTU option is not sent in the router advertisement messages.
Parameters
- bytes
-
Specifies the advertised MTU value in bytes for this interface.
Platforms
7705 SAR Gen 2
mtu
Syntax
mtu mtu-bytes
no mtu
Context
[Tree] (config>port>ethernet mtu)
Full Context
configure port ethernet mtu
Description
This command configures the maximum payload MTU size for an Ethernet port, PPP-enabled port or sub-port and Frame Relay-enabled port or subport. The Ethernet port level MTU parameter indirectly defines the largest physical packet the port can transmit or the far-end Ethernet port can receive. Packets that cannot be fragmented at egress and exceed the MTU are discarded.
The value specified for the MTU includes the destination MAC address, source MAC address, the Ethertype or Length field and the complete Ethernet payload. The MTU value does not include the preamble, start of frame delimiter or the trailing CRC.
PoS channels use the MTU to define the largest PPP payload a PoS frame may contain. A significant difference between SONET/SDH PoS channel and Ethernet physical MTU values the overhead considered part of the framing method and the overhead considered to be part of the application using the frame. In Ethernet, the preamble, start of frame delimiter and the CRC are considered part of the framing overhead and not part of the frame payload. For a PoS channel, the HDLC framing overhead is not included in the physical MTU; only the PPP and PPP payload are included. If the port mode or encapsulation type is changed, the MTU assumes the default values of the new mode or encapsulation type.
The no form of this command restores the default values.
Default
The default MTU value depends on the (sub-)port type, mode and encapsulation and are listed in Default MTU Values:
|
Type |
Mode |
Encap Type |
Default (Bytes) |
|---|---|---|---|
|
10/100, Gig, or 10GigE |
Access |
null |
1514 |
|
10/100, Gig, or 10GigE |
Access |
dot1q |
1518 |
|
10/100, Gig, or 10GigE |
Access |
q-in-q |
1522 |
|
SONET/SDH or TDM |
Access |
mpls |
1506 |
|
SONET/SDH or TDM |
Access |
bcp-null |
1518 |
|
SONET/SDH or TDM |
Access |
bcp-dot1q |
1522 |
|
SONET/SDH or TDM |
Access |
ipcp |
1502 |
|
SONET/SDH or TDM |
Access |
frame-relay |
1578 |
|
ATM, SONET/SDH or TDM |
Access |
atm |
1524 |
|
10/100 or 100FX Ethernet |
Network |
null |
1514 |
|
10/100 or 100FX Ethernet |
Network |
dot1q |
1518 |
|
SONET/SDH |
Network |
ppp-auto |
1524 |
Parameters
- mtu-bytes
-
Sets the maximum allowable size of the MTU, expressed as an integer.
Platforms
7705 SAR Gen 2
mtu
Syntax
mtu mtu-bytes
no mtu
Context
[Tree] (config>service>vprn>ospf3>area>if mtu)
[Tree] (config>service>vprn>ospf>area>if mtu)
Full Context
configure service vprn ospf3 area interface mtu
configure service vprn ospf area interface mtu
Description
This command configures the OSPF packet size used on this interface. If this parameter is not configured, OSPF derives the MTU value from the MTU configured (default or explicitly) in the following contexts:
config>port>ethernet, config>port>sonet-sdh>path, config>port>tdm>t3-e3, config>port>tdm>t1-e1>channel-group
If this parameter is configured, the smaller value between the value configured here and the MTU configured (default or explicitly) in an above-mentioned contexts is used.
To determine the actual packet size, add 14 bytes for an Ethernet packet and 18 bytes for a tagged Ethernet packet to the size of the OSPF (IP) packet MTU configured in this command.
The no form of this command reverts to default value derived from the MTU configured in the config>port context.
Default
no mtu
Parameters
- mtu-bytes
-
Specifies the MTU to be used by OSPF for this logical interface, in bytes.
Platforms
7705 SAR Gen 2
mtu
Syntax
mtu value
no mtu
Context
[Tree] (config>service>vprn>nat>outside mtu)
Full Context
configure service vprn nat outside mtu
Description
This command configures the Maximum Transmission Unit (MTU) for downstream traffic flowing through this router (as outside NAT router). The system fragments IP datagrams exceeding the MTU.
The no form of the command reverts to the default.
Default
no mtu
Parameters
- value
-
Specifies the MTU for downstream traffic.
Platforms
7705 SAR Gen 2
mtu
Syntax
mtu mtu-size
no mtu
Context
[Tree] (config>router>nat>outside mtu)
Full Context
configure router nat outside mtu
Description
This command configures the MTU for downstream traffic flowing through this router (as outside NAT router). The system fragments IP datagrams exceeding the MTU.
Default
no mtu
Parameters
- mtu-size
-
Specifies the MTU for downstream traffic.
Platforms
7705 SAR Gen 2
mtu
Syntax
mtu bytes
no mtu
Context
[Tree] (config>router>ospf3>area>interface mtu)
[Tree] (config>router>ospf>area>interface mtu)
Full Context
configure router ospf3 area interface mtu
configure router ospf area interface mtu
Description
This command configures the OSPF packet size used on this interface. If this parameter is not configured OSPF derives the MTU value from the MTU configured (default or explicitly) in the following contexts:
-
config>port>ethernet
-
config>port>sonet-sdh>path
-
config>port>tdm>t3-e3
-
config>port>tdm>t1-e1>channel-group
If this parameter is configured, the smaller value between the value configured here and the MTU configured (default or explicitly) in an above-mentioned context is used.
To determine the actual packet size, add 14 bytes for an Ethernet packet and 18 bytes for a tagged Ethernet packet to the size of the OSPF (IP) packet MTU configured in this command.
The no form of this command reverts to the default derived from the MTU configured in the config>port context.
Default
no mtu
Parameters
- bytes
-
Specifies the MTU to be used by OSPF for this logical interface in bytes.
Platforms
7705 SAR Gen 2
mtu-over-head
mtu-over-head
Syntax
mtu-over-head mtu-value
no mtu-over-head
Context
[Tree] (config>service>vprn>pim mtu-over-head)
Full Context
configure service vprn pim mtu-over-head
Description
This commands subtracts the specified value from the MVPN MTU to allow a BIER header to be added without exceeding the network MTU.
Default
no mtu-over-head
Parameters
- mtu-value
-
Specifies the value subtracted from the MVPN MTU.
Platforms
7705 SAR Gen 2
multi-active
multi-active
Syntax
[no] multi-active
Context
[Tree] (config>isa>tunnel-grp multi-active)
Full Context
configure isa tunnel-group multi-active
Description
This command enables configuring multiple active MS-ISA in the tunnel-group. IPsec traffic will be load balanced to configured active MS-ISAs.
Operational notes:
-
A shutdown of group and removal of all existing configured tunnels of the tunnel-group are needed before provisioning command "multi-active”.
-
If the tunnel-group is admin-up with "multi-active” configured then the configuration of "primary” and "backup” are not allowed.
-
The active-mda-number must be =< total number of ISA configured.
-
If active-mda-number is less than total number of ISA configured then the delta number of ISA will become backup ISA.
-
Default
no multi-active
Platforms
7705 SAR Gen 2
multi-chassis
multi-chassis
Syntax
multi-chassis
Context
[Tree] (config>redundancy multi-chassis)
Full Context
configure redundancy multi-chassis
Description
Commands in this context configure multi-chassis parameters.
Platforms
7705 SAR Gen 2
multi-chassis-shunt-interface
multi-chassis-shunt-interface
Syntax
multi-chassis-shunt-interface ip-int-name [create]
no multi-chassis-shunt-interface ip-int-name
Context
[Tree] (config>router>ipsec multi-chassis-shunt-interface)
[Tree] (config>service>vprn>ipsec multi-chassis-shunt-interface)
Full Context
configure router ipsec multi-chassis-shunt-interface
configure service vprn ipsec multi-chassis-shunt-interface
Description
Commands in this context configure a multi-chassis IPsec shunt interface.
The no form of this command removes the interface name from the configuration.
Parameters
- ip-int-name
-
Specifies the shunt interface name, up to 32 characters.
- create
-
Keyword used to create the command instance.
Platforms
7705 SAR Gen 2
multi-chassis-shunt-interface
Syntax
multi-chassis-shunt-interface ip-int-name
no multi-chassis-shunt-interface ip-int-name
Context
[Tree] (config>router>ipsec>mc-shunt-profile>peer multi-chassis-shunt-interface)
[Tree] (config>service>vprn>ipsec>mc-shunt-profile>peer multi-chassis-shunt-interface)
Full Context
configure router ipsec multi-chassis-shunting-profile peer multi-chassis-shunt-interface
configure service vprn ipsec multi-chassis-shunting-profile peer multi-chassis-shunt-interface
Description
This command associates a multi-chassis-shunt-interface for the peer. The specified interface shunts traffic to the peer.
The no form of this command removes association from the configuration.
Parameters
- ip-int-name
-
Specifies the shunt interface name, up to 32 characters.
Platforms
7705 SAR Gen 2
multi-chassis-shunting-profile
multi-chassis-shunting-profile
Syntax
multi-chassis-shunting-profile name [create]
no multi-chassis-shunting-profile name
Context
[Tree] (config>router>ipsec multi-chassis-shunting-profile)
[Tree] (config>service>vprn>ipsec multi-chassis-shunting-profile)
Full Context
configure router ipsec multi-chassis-shunting-profile
configure service vprn ipsec multi-chassis-shunting-profile
Description
Commands in this context configure a multi-chassis IPsec shunting profile.
The no form of this command removes the name from the configuration.
Parameters
- name
-
Specifies the profile name of a MC shunting profile, up to 32 characters.
- create
-
Keyword used to create the command instance.
Platforms
7705 SAR Gen 2
multi-chassis-shunting-profile
Syntax
multi-chassis-shunting-profile name
no multi-chassis-shunting-profile
Context
[Tree] (config>service>vprn>if multi-chassis-shunting-profile)
[Tree] (config>service>ies>if multi-chassis-shunting-profile)
Full Context
configure service vprn interface multi-chassis-shunting-profile
configure service ies interface multi-chassis-shunting-profile
Description
This command associates an existing multi-chassis IPsec shunting profile with the service interface.
The no form of this command removes the name from the configuration.
Parameters
- name
-
Specifies the profile name of a multi-chassis-shunting profile, up to 32 characters.
Platforms
7705 SAR Gen 2
multi-homed-prefix
multi-homed-prefix
Syntax
[no] multi-homed-prefix
Context
[Tree] (config>router>ospf>lfa multi-homed-prefix)
Full Context
configure router ospf loopfree-alternates multi-homed-prefix
Description
This command enables multi-homed prefix LFA for OSPF routes (IP FRR) and SR-OSPF node SID tunnels.
This feature makes use of the multi-homed prefix model described in RFC 8518 to compute a backup IP next hop using an alternate ABR or ASBR for external prefixes and to an alternate router owner for local anycast prefixes.
This feature further enhances the multi-homed prefix backup path calculation beyond RFC 8518 with the addition of repair tunnels that make use of a PQ node or a P-Q set to reach the alternate exit ABR or ASBR of external prefixes or the alternate owner router of local anycast prefixes.
The computed IP next-hop based backup path is added to OSPF routes of external /32 prefixes (OSPFv2 routes types 3, 4, 5, and 7) and local /32 anycast prefixes in the RTM if the prefix is not protected by base LFA or if the user set leaf preference value to all. The user must enable the ip-fast-reroute leaf to have these backup paths programmed into the FIB in data path.
The computed IP next hop or repair tunnel based backup path is also programmed for SR-OSPF node SID tunnels of external /32 prefixes and to /32 prefixes in same area as the computing node S and which are advertised by multiple routers (anycast prefix) in both algorithm 0 and flexible-algorithm numbers.
The no form of this command disables multi-homed prefix LFA.
Default
no multi-homed-prefix
Platforms
7705 SAR Gen 2
multi-homed-prefix
Syntax
[no] multi-homed-prefix
Context
[Tree] (config>router>isis>lfa multi-homed-prefix)
Full Context
configure router isis loopfree-alternates multi-homed-prefix
Description
This command enables multihomed prefix LFA for IS-IS routes (IP FRR), SR-ISIS tunnels, and SRv6-ISIS tunnels.
This feature uses the multihomed prefix model described in RFC 8518 to compute a backup IP next hop using an alternate ABR or ASBR for external prefixes and to an alternate router owner for local anycast prefixes.
This feature further enhances the multihomed prefix backup path calculation beyond RFC 8518 with the addition of repair tunnels that make use of a PQ node or a P-Q set to reach the alternate exit ABR or ASBR of external prefixes or the alternate owner router of intra-area anycast prefixes.
The computed IP next hop-based backup path is added to IS-IS routes of external /32 or /128 prefixes and intra-area /32 or /128 anycast prefixes in the RTM if the prefix is not protected by base LFA or if the user set leaf preference command option to all. The user must enable the ip-fast-reroute leaf to have these backup paths programmed into the FIB in datapath.
The computed IP next hop or repair tunnel-based backup path is also programmed for:
- SR-ISIS node SID tunnels of external /32 IPv4 prefixes and /128 IPv6 prefixes, and node SID tunnels of intra-area /32 IPv4 anycast prefixes and /128 anycast IPv6 prefixes, in both algorithm 0 and flexible-algorithms
-
SRv6-ISIS locator routes and tunnels of external prefixes and of intra-area anycast prefixes of any size, in both algorithm 0 and flexible algorithm numbers
As a result, an SR-TE LSP, an SR-MPLS policy, or an SRv6 policy which uses an SR-ISIS SID or an SRv6-ISIS SID of those same prefixes in its configured or computed SID list benefits from the multi-homed prefix LFA protection.
Once the IP next-hop based multihomed prefix LFA is enabled, the extensions to compute an SR-TE repair tunnel for the multihomed prefix LFA in the case of SR-ISIS and SRv6-ISIS are automatically enabled if the user also enabled TI-LFA or Remote LFA. The computation reuses the SID list of the primary path or of the TI-LFA or Remote LFA backup path of the alternate ABR or ASBR or alternate owner router.
The no form of this command disables multihomed prefix LFA.
Default
no multi-homed-prefix
Platforms
7705 SAR Gen 2
multi-instance
multi-instance
Syntax
[no] multi-instance
Context
[Tree] (config>router>ospf multi-instance)
Full Context
configure router ospf multi-instance
Description
This command enables OSPF multi-instance RFC 6549, OSPFv2 Multi-Instance Extensions, support in the BASE router. This support is enabled per instance and allows flexibility when migrating a specific instance from the classic OSPFv2 to a multi-instance OSPFv2.
The no form of this command disables OSPF multi-instance support in the BASE router.
Default
no multi-instance
Platforms
7705 SAR Gen 2
multi-path
multi-path
Syntax
multi-path
Context
[Tree] (config>service>vprn>bgp multi-path)
Full Context
configure service vprn bgp multi-path
Description
This command configures ECMP multipath parameters to apply to address families that support BGP multipath.
Platforms
7705 SAR Gen 2
multi-path
Syntax
multi-path
Context
[Tree] (config>router>bgp multi-path)
Full Context
configure router bgp multi-path
Description
This command configures ECMP multipath parameters to apply to address families that support BGP multipath.
Platforms
7705 SAR Gen 2
multi-service-site
multi-service-site
Syntax
[no] multi-service-site customer-site-name
Context
[Tree] (config>service>ies>if>sap multi-service-site)
Full Context
configure service ies interface sap multi-service-site
Description
This command creates a new customer site or edits an existing customer site with the customer-site-name parameter. A customer site is an anchor point to create an ingress and egress virtual scheduler hierarchy. When a site is created, it must be assigned to a chassis slot or port. When scheduler policies are defined for ingress and egress, the scheduler names contained in each policy are created according to the parameters defined in the policy. Multi-service customer sites exist for the sole purpose of creating a virtual scheduler hierarchy and making it available to queues on multiple Service Access Points (SAPs).
The scheduler policy association with the customer site normally prevents the scheduler policy from being deleted until after the scheduler policy is removed from the customer site. The multi-service-site object generates a log message indicating that the association was deleted due to scheduler policy removal.
When the multi-service customer site is created, an ingress and egress scheduler policy association does not exist. This does not prevent the site from being assigned to a chassis slot or prevent service SAP assignment. After the site has been created, the ingress and egress scheduler policy associations can be assigned or removed at any time.
The no form of this command removes the value from the configuration.
Default
n/a — Each customer site must be explicitly created.
Parameters
- customer-site-name
-
Each customer site must have a unique name within the context of the customer. If customer-site-name already exists for the customer ID, the CLI context changes to that site name for the purpose of editing the site scheduler policies or assignment. Any modifications made to an existing site affects all SAPs associated with the site. Changing a scheduler policy association may cause new schedulers to be created and existing policers and queues on the SAPs to no longer be orphaned. Existing schedulers on the site may cease to exist, causing policers and queues relying on that scheduler to be orphaned.
If the customer-site-name does not exist, it is assumed that an attempt is being made to create a site of that name in the customer ID context. The success of the command execution depends on the following:
The maximum number of customer sites defined for the chassis slot has not been met.
The customer-site-name is valid.
The create keyword is included in the command line syntax (if the system requires it).
When the maximum number of customer sites has been exceeded a configuration error occurs, the command will not execute and the CLI context will not change.
If the customer-site-name is invalid, a syntax error occurs, the command will not execute and the CLI context will not change.
Platforms
7705 SAR Gen 2
multi-service-site
Syntax
multi-service-site customer-site-name
no multi-service-site
Context
[Tree] (config>service>vprn>if>sap multi-service-site)
[Tree] (config>service>vpls>sap multi-service-site)
Full Context
configure service vprn interface sap multi-service-site
configure service vpls sap multi-service-site
Description
This command associates the SAP with a customer-site-name. If the specified customer-site-name does not exist in the context of the service customer ID an error occurs and the command is not executed. If customer-site-name exists, the current and future defined queues on the SAP (ingress and egress) attempts to use the scheduler hierarchies created within customer-site-name as parent schedulers.
This command is mutually exclusive with the SAP ingress and egress scheduler policy commands. If a scheduler policy has been applied to either the ingress or egress nodes on the SAP, the multi-service-site command fails without executing. The locally applied scheduler policies must be removed prior to executing the multi-service-site command.
The no form of this command removes the SAP from any multi-service customer site the SAP belongs to. Removing the site can cause existing or future policers and queues to enter an orphaned state.
Parameters
- customer-site-name
-
Specifies an existing customer site name, up to 32 characters. If the customer-site-name exists and local scheduler policies have not been applied to the SAP, the current and future policers queues defined on the SAP looks for their parent schedulers within the scheduler hierarchies defined in the customer-site-name.
Platforms
7705 SAR Gen 2
multi-service-site
Syntax
multi-service-site customer-site-name
no multi-service-site
Context
[Tree] (config>service>epipe>sap multi-service-site)
Full Context
configure service epipe sap multi-service-site
Description
This command associates the SAP with a customer-site-name. If the specified customer-site-name does not exist in the context of the service customer ID an error occurs and the command will not execute. If customer-site-name exists, the current and future defined queues on the SAP (ingress and egress) will attempt to use the scheduler hierarchies created within customer-site-name as parent schedulers.
The no form of this command removes the SAP from any multi-service customer site the SAP belongs to. Removing the site can cause existing or future queues to enter an orphaned state.
Parameters
- customer-site-name
-
The customer-site-name must exist in the context of the customer-id defined as the service owner. If customer-site-name exists and local scheduler policies have not been applied to the SAP, the current and future queues defined on the SAP will look for their parent schedulers within the scheduler hierarchies defined on customer-site-name.
Platforms
7705 SAR Gen 2
multi-service-site
Syntax
multi-service-site customer-site-name [create]
no multi-service-site customer-site-name
Context
[Tree] (config>service>cust multi-service-site)
Full Context
configure service customer multi-service-site
Description
This command creates a new customer site or edits an existing customer site with the customer-site-name parameter. A customer site is an anchor point to create an ingress and egress virtual scheduler hierarchy. When a site is created, it must be assigned to a chassis slot or port. When scheduler policies are defined for ingress and egress, the scheduler names contained in each policy are created according to the parameters defined in the policy. Multi-service customer sites exist for the sole purpose of creating a virtual scheduler hierarchy and making it available to queues on multiple Service Access Points (SAPs).
The scheduler policy association with the customer site normally prevents the scheduler policy from being deleted until after the scheduler policy is removed from the customer site. The multi-service-site object will generate a log message indicating that the association was deleted due to scheduler policy removal.
When the multi-service customer site is created, an ingress and egress scheduler policy association does not exist. This does not prevent the site from being assigned to a chassis slot or prevent service SAP assignment. After the site has been created, the ingress and egress scheduler policy associations can be assigned or removed at any time.
Parameters
- customer-site-name
-
Specifies the customer site name. Each customer site must have a unique name within the context of the customer. If customer-site-name already exists for the customer ID, the CLI context changes to that site name for the purpose of editing the site scheduler policies or assignment. Any modifications made to an existing site will affect all SAPs associated with the site. Changing a scheduler policy association may cause new schedulers to be created and existing policers and queues on the SAPs to no longer be orphaned. Existing schedulers on the site may cease to exist, causing policers and queues relying on that scheduler to be orphaned.
If the customer-site-name does not exist, it is assumed that an attempt is being made to create a site of that name in the customer ID context. The success of the command execution depends on the following:
-
The maximum number of customer sites defined for the chassis has not been met.
-
The customer-site-name is valid.
-
The create keyword is included in the command line syntax (if the system requires).
When the maximum number of customer sites has been exceeded a configuration error occurs; the command will not execute and the CLI context will not change.
If the customer-site-name is invalid, a syntax error occurs; the command will not execute and the CLI context will not change.
-
Platforms
7705 SAR Gen 2
multi-topology
multi-topology
Syntax
[no] multi-topology
Context
[Tree] (config>service>vprn>isis multi-topology)
Full Context
configure service vprn isis multi-topology
Description
This command enables IS-IS multi-topology support.
The no form of this command disables IS-IS multi-topology.
Default
no multi-topology
Platforms
7705 SAR Gen 2
multi-topology
Syntax
[no] multi-topology
Context
[Tree] (config>router>isis multi-topology)
Full Context
configure router isis multi-topology
Description
This command enables IS-IS multi-topology support.
Default
no multi-topology
Platforms
7705 SAR Gen 2
multi-topology
Syntax
multi-topology mt2
no multi-topology
Context
[Tree] (config>router>isis>segment-routing multi-topology)
Full Context
configure router isis segment-routing multi-topology
Description
This command configures SR-MPLS for SR-ISIS MT, which enables Segment Routing in MT2.
The no form of this command disables Segment Routing in MT2.
Default
no multi-topology
Platforms
7705 SAR Gen 2
multicast
multicast
Syntax
multicast [key-id key-id | authentication-keychain keychain-name] [version version]
no multicast
Context
[Tree] (config>system>time>ntp multicast)
Full Context
configure system time ntp multicast
Description
This command configures NTP the node to transmit multicast packets on the CPM/CCM MGMT port. Broadcast and multicast messages can easily be spoofed; authentication is strongly recommended.
The no form of this command removes the multicast address from the configuration.
Parameters
- key-id
-
Specifies the configured authentication key and authentication type used by this version to transmit NTP packets. If this command is omitted from the configuration, packets are sent unencrypted.
- keychain-name
-
Identifies the keychain name, up to 32 characters.
- version
-
Specifies the NTP version number that is generated by this node. This parameter does not need to be configured when in client mode in which case all three versions are accepted.
Platforms
7705 SAR Gen 2
multicast-import
multicast-import
Syntax
[no] multicast-import
Context
[Tree] (config>service>vprn>isis multicast-import)
Full Context
configure service vprn isis multicast-import
Description
This command enables ISIS to submit routes into the multicast Route Table Manager (RTM).
The no form of this command disables the submission of routes into the multicast RTM.
Default
no multicast-import
Platforms
7705 SAR Gen 2
multicast-import
Syntax
[no] multicast-import
Context
[Tree] (config>service>vprn>ospf3 multicast-import)
[Tree] (config>service>vprn>ospf multicast-import)
Full Context
configure service vprn ospf3 multicast-import
configure service vprn ospf multicast-import
Description
This command enables the submission of routes into the multicast Route Table Manager (RTM) by OSPF.
The no form of this command disables the submission of routes into the multicast RTM.
Default
no multicast-import
Platforms
7705 SAR Gen 2
multicast-import
Syntax
[no] multicast-import [{both | ipv4 | ipv6}]
Context
[Tree] (config>router>isis multicast-import)
Full Context
configure router isis multicast-import
Description
This command enables the submission of routes into the multicast Route Table Manager (RTM) by IS-IS.
The no form of this command disables the submission of routes into the multicast RTM.
Default
no multicast-import
Parameters
- both
-
Allows submission of both IPv4 and IPv6 routes.
- ipv4
-
Allows submission of IPv4 routes only.
- ipv6
-
Allows submission of IPv6 routes only.
Platforms
7705 SAR Gen 2
multicast-import
Syntax
[no] multicast-import
Context
[Tree] (config>router>ospf multicast-import)
[Tree] (config>router>ospf3 multicast-import)
Full Context
configure router ospf multicast-import
configure router ospf3 multicast-import
Description
This command enables the submission of routes into the multicast Route Table Manager (RTM) by OSPF.
The no form of this command disables the submission of routes into the multicast RTM.
Default
no multicast-import
Platforms
7705 SAR Gen 2
multicast-leave-sync-propagation
multicast-leave-sync-propagation
Syntax
multicast-leave-sync-propagation time
Context
[Tree] (config>service>system>bgp-evpn multicast-leave-sync-propagation)
Full Context
configure service system bgp-evpn multicast-leave-sync-propagation
Description
This command configures the additional amount of time that the system waits before removing a multicast state that was synchronized in an Ethernet Segment via Multicast Join or Leave Synch routes. This value represents a delta corresponding to the time it takes for a BGP advertisement to propagate to ES peers.
The node triggering the route computes the maximum response time as the product of the locally configured values, Last Member Query Count and Last Member Query Interval (this value is taken from the config>service>vpls>sap>igmp-snooping>last-member-query-interval or config>service>vpls>spoke-sdp>igmp-snooping> last-member-query-interval commands depending on the Ethernet Segment being used), and adds the delta value to the Maximum Response Time. Increasing the Maximum Response Time by this value can help minimize the churn of removing and recreating the state on the node.
The maximum response time value should be configured consistently in all ES peers. For example, in a scenario where a maximum response time of five seconds is advertised by PE-A and there is a delay of four seconds in the BGP propagation to PE-B, the timer could already expire on PE-A while PE-B is still in LMQ time and can still receive joins (which would recreate state in A after a join synch route from B). To minimize this situation, adding an extra delta timer on PE-A, reduces the potential churn of PE-A removing and recreating the state.
Default
multicast-leave-sync-propagation 5
Parameters
- time
-
Specifies the multicast leave sync propagation delay time, in seconds.
Platforms
7705 SAR Gen 2
multicast-network-domain
multicast-network-domain
Syntax
multicast-network-domain multicast-network-domain
no multicast-network-domain
Context
[Tree] (config>service>ies>if multicast-network-domain)
Full Context
configure service ies interface multicast-network-domain
Description
This command is used to enable efficient multicast replication over a spoke SDP. Multicast traffic is copied to only a subset of network interfaces that may be used as egress for a spoke SDP. A network domain is defined by associating multiple interfaces to a logical group that may participate in multicast replication for a spoke SDP.
The no form of command disables efficient multicast replication to a network domain for a spoke SDP and traffic is replicated to all forwarding complexes.
Default
no multicast-network-domain
Platforms
7705 SAR Gen 2
multicast-policer
multicast-policer
Syntax
multicast-policer policer-id [fp-redirect-group]
no multicast-policer
Context
[Tree] (config>qos>sap-ingress>fc multicast-policer)
Full Context
configure qos sap-ingress fc multicast-policer
Description
Within a sap-ingress QoS policy forwarding class context, the multicast-policer command is used to map packets that match the forwarding class and are considered multicast in nature to the specified policer-id. The specified policer-id must already exist within the sap-ingress QoS policy. While the system is determining the forwarding class of a packet, it is also looking up its forwarding destination based on the ingress service type and the service instance forwarding records. Two basic types of services support multicast packets: routed services (IES and VPRN) and L2 multipoint services (VPLS, I-VPLS, and B-VPLS). For the routed service types, a multicast packet is destined to an IPv4 or IPv6 multicast address. For the L2 multipoint services, a multicast packet is a packet destined to a multicast MAC address (multicast bit set in the destination MAC address but not the ff:ff:ff:ff:ff:ff broadcast address). The VPLS services also support two other multipoint forwarding types (broadcast and unknown), which are considered separate from the multicast forwarding type.
If ingress forwarding logic has resolved a packet to the multicast forwarding type within the forwarding class, it will be mapped to either an ingress multipoint queue (using the multicast queue-id or multicast queue-id group ingress-queue-group commands) or an ingress policer (multicast-policer policer-id). The multicast and multicast-policer commands within the forwarding class context are mutually exclusive. By default, the multicast forwarding type is mapped to the SAP ingress default multipoint queue. If the multicast-policer policer-id command is executed, any previous policer mapping or queue mapping for the multicast forwarding type within the forwarding class is overridden if the policer mapping is successful.
A policer defined within the sap-ingress policy is not actually created on an ingress SAP or a subscriber using an sla-profile where the policy is applied until at least one forwarding type (unicast, broadcast, unknown, or multicast) from one of the forwarding classes is mapped to the policer. If insufficient policer resources exist to create the policer for a SAP or subscriber or multiservice site, or ingress policing is not supported on the port associated with the SAP or subscriber or multiservice site, the initial forwarding class forwarding type mapping will fail.
The multicast-policer command is ignored for instances of the policer applied to SAPs subscribers or multiservice site where broadcast packets are not supported.
When the multicast forwarding type within a forwarding class is mapped to a policer, the multicast packets classified to the subclasses within the forwarding class are also mapped to the policer.
The no form of this command is used to restore the mapping of the multicast forwarding type within the forwarding class to the default multipoint queue. If all forwarding class forwarding types had been removed from the default multipoint queue, the queue will not exist on the SAPs subscribers or multiservice site associated with the QoS policy, and the no multicast-policer command will cause the system to attempt to create the default multipoint queue on each object. If the system cannot create the queue on each instance, the no multicast-policer command will fail and the multicast forwarding type within the forwarding class will continue its mapping to the existing policer-id. If the no multicast-policer command results in a policer without any current mappings, the policer will be removed from the SAPs and subscribers associated with the QoS policy. All statistics associated with the policer on each SAP and subscriber will be lost.
Parameters
- policer-id
-
When the forwarding class multicast-policer command is executed, a valid policer-id must be specified. The parameter policer-id references a policer-id that has already been created within the sap-ingress QoS policy.
- fp-redirect-group
-
Redirects a forwarding class to a forwarding plane queue-group as specified in a SAP QoS policy.
Platforms
7705 SAR Gen 2
multicast-queue
multicast-queue
Syntax
multicast-queue queue-id [group queue-group-name]
no multicast-queue
Context
[Tree] (config>qos>sap-ingress>fc multicast-queue)
Full Context
configure qos sap-ingress fc multicast-queue
Description
This command overrides the default multicast forwarding type queue mapping for fc fc-name. The specified queue-id must exist within the policy as a multipoint queue before the mapping can be made. When the forwarding class mapping is executed, all multicast traffic on a SAP using this policy is forwarded using the queue-id.
The multicast forwarding type includes the unknown unicast forwarding type and the broadcast forwarding type unless each is explicitly defined to a different multipoint queue. When the unknown and broadcast forwarding types are left as default, they will track the defined queue for the multicast forwarding type.
The no form of this command sets the multicast forwarding type queue-id back to the default queue for the forwarding class. If the broadcast and unknown forwarding types were not explicitly defined to a multipoint queue, they will also be set back to the default multipoint queue (queue 11).
Parameters
- queue-id
-
The queue-id parameter specified must be an existing, multipoint queue defined in the config>qos>sap-ingress context.
- group queue-group-name
-
This optional parameter is used to redirect the forwarding type within the forwarding class to the specified queue-id within the queue-group-name. When the policy is applied, all packets matching the forwarding class and forwarding type will be redirected to the queue within the specified queue group. The queue-group-name are configured in the config>qos>queue-group-templates egress and ingress contexts.
Platforms
7705 SAR Gen 2
multicast-queue
Syntax
multicast-queue queue-id
no multicast-queue
Context
[Tree] (config>qos>network-queue>fc multicast-queue)
Full Context
configure qos network-queue fc multicast-queue
Description
This command overrides the default multicast forwarding type queue mapping for fc fc-name. The specified queue-id must exist within the policy as a multipoint queue before the mapping can be made. When the forwarding class mapping is executed, all multicast traffic using this policy is forwarded using the queue-id.
The multicast forwarding type includes the unknown unicast forwarding type and the broadcast forwarding type, unless each is explicitly defined to a different multipoint queue. When the unknown and broadcast forwarding types are left as default, they will track the defined queue for the multicast forwarding type.
The no form of this command sets the multicast forwarding type queue-id back to the default queue for the forwarding class. If the broadcast and unknown forwarding types were not explicitly defined to a multipoint queue, they will also be set back to the default multipoint queue (queue 11).
Resource Utilization
When a multipoint queue is created and at least one forwarding class is mapped to the queue using the multipoint-queue command, a single ingress multipoint hardware queue is created per instance of the applied network-queue policy, using the queue-policy command at the ingress network FP level. Multipoint queues are not created at egress and the multipoint queues defined in the network-queue policy are ignored when the policy is applied to an egress port.
Parameters
- queue-id
-
Specifies any valid multipoint queue-ID in the policy. The queue-id parameter specified must be an existing, multipoint queue defined in the config>qos>network-queue>queue context.
Platforms
7705 SAR Gen 2
multicast-senders
multicast-senders
Syntax
multicast-senders {auto | always | never}
no multicast-senders
Context
[Tree] (config>service>vprn>pim>if multicast-senders)
Full Context
configure service vprn pim interface multicast-senders
Description
This command configures the way subnet matching is done for incoming data packets on this interface. An IP multicast sender is an user entity to be authenticated in a receiving host.
Parameters
- auto
-
Subnet matching is automatically performed for incoming data packets on this interface.
- always
-
Subnet matching is always performed for incoming data packets on this interface.
- never
-
Subnet matching is never performed for incoming data packets on this interface.
Platforms
7705 SAR Gen 2
multicast-senders
Syntax
multicast-senders {auto | always | never}
no multicast-senders
Context
[Tree] (config>router>pim>interface multicast-senders)
Full Context
configure router pim interface multicast-senders
Description
This command configures how traffic from directly-attached multicast sources should be treated on broadcast interfaces. It can also be used to treat all traffic received on an interface as traffic coming from a directly-attached multicast source. This is particularly useful if a multicast source is connected to a point-to-point or unnumbered interface.
The no form of this command reverts to the default value.
Default
multicast-senders auto
Parameters
- auto
-
Specifies that, on broadcast interfaces, the forwarding plane performs subnet-match check on multicast packets received on the interface to determine if the packet is from a directly-attached source. On unnumbered/point-to-point interfaces, all traffic is implicitly treated as coming from a remote source.
- always
-
Treats all traffic received on the interface as coming from a directly-attached multicast source.
- never
-
Specifies that, on broadcast interfaces, traffic from directly-attached multicast sources will not be forwarded; however, traffic from a remote source will still be forwarded if there is a multicast state for it. On unnumbered/point-to-point interfaces, it means that all traffic received on that interface must not be forwarded.
Platforms
7705 SAR Gen 2
multicastclient
multicastclient
Syntax
multicastclient [authenticate]
no multicastclient
Context
[Tree] (config>system>time>ntp multicastclient)
Full Context
configure system time ntp multicastclient
Description
This command configures the node to receive multicast NTP messages on the CPM MGMT port. If multicastclient is not configured, received NTP multicast traffic will be ignored. Use the show command to view the state of the configuration.
The no construct of this message removes the multicast client for the specified interface from the configuration.
Parameters
- authenticate
-
Specifies to make authentication a requirement (optional). If authentication is required, the authentication key-id received must have been configured in the authentication-key command, and that key-id type and key value must also match.
Platforms
7705 SAR Gen 2
multihop
multihop
Syntax
multihop ttl-value
no multihop
Context
[Tree] (config>service>vprn>bgp>group multihop)
[Tree] (config>service>vprn>bgp>group>neighbor multihop)
[Tree] (config>service>vprn>bgp multihop)
Full Context
configure service vprn bgp group multihop
configure service vprn bgp group neighbor multihop
configure service vprn bgp multihop
Description
This command configures the time to live (TTL) value entered in the IP header of packets sent to an EBGP peer multiple hops away.
This parameter is meaningful only when configuring EBGP peers. It is ignored if set for an IBGP peer.
The no form of this command is used to convey to the BGP instance that the EBGP peers are directly connected.
The no form of this command reverts to default values.
Default
multihop 1 (EBGP peers are directly connected)
multihop 64 (IBGP)
Parameters
- ttl-value
-
Specifies the TTL value, expressed as a decimal integer.
Platforms
7705 SAR Gen 2
multihop
Syntax
multihop ttl-value
no multihop
Context
[Tree] (config>router>bgp>group multihop)
[Tree] (config>router>bgp>group>neighbor multihop)
[Tree] (config>router>bgp multihop)
Full Context
configure router bgp group multihop
configure router bgp group neighbor multihop
configure router bgp multihop
Description
This command configures the time to live (TTL) value entered in the IP header of packets sent to an EBGP peer multiple hops away.
The no form of this command is used to convey to the BGP instance that the EBGP peers are directly connected.
The no form of this command used at the global level reverts to default.
The no form of this command used at the group level reverts to the value defined at the global level.
The no form of this command used at the neighbor level reverts to the value defined at the group level.
Default
multihop 1 — EBGP peers are directly connected.
multihop 64 — IBGP
Parameters
- ttl-value
-
Specifies the TTL value, expressed as a decimal integer.
Platforms
7705 SAR Gen 2
multipath-eligible
multipath-eligible
Syntax
[no] multipath-eligible
Context
[Tree] (config>service>vprn>bgp>group multipath-eligible)
Full Context
configure service vprn bgp group multipath-eligible
Description
This command specifies that a BGP neighbor or the set of BGP neighbors in a peer group should be part of a selective multipath set. Selective multipaths are only supported by the ipv4, label-ipv4, ipv6, and label-ipv6 address families.
If no candidate multipath route for an IP prefix came from a multipath-eligible peer, multipaths are selected without further constraints.
If the best route for an IP prefix is received from a neighbor marked as multipath-eligible, other routes for the same prefix are not eligible to be used as multipaths unless they also came from peers marked as multipath-eligible.
If the best route for an IP prefix did not come from a multipath-eligible peer but there is at least one candidate multipath route for the same prefix from a multipath-eligible peer, multipath is not used.
The no form of this command marks a neighbor or group as non-multipath eligible. The effect of this depends on whether other neighbors and groups are marked as multipath eligible.
Default
no multipath-eligible
Platforms
7705 SAR Gen 2
multipath-eligible
Syntax
[no] multipath-eligible
Context
[Tree] (config>router>bgp>group>neighbor multipath-eligible)
[Tree] (config>router>bgp>group multipath-eligible)
Full Context
configure router bgp group neighbor multipath-eligible
configure router bgp group multipath-eligible
Description
This command specifies that a BGP neighbor or the set of BGP neighbors in a peer group should be part of a selective multipath set. Selective multipaths are only supported by the ipv4, label-ipv4, ipv6, and label-ipv6 address families.
If no candidate multipath route for an IP prefix came from a multipath-eligible peer then multipaths are selected without further constraints.
If the best route for an IP prefix is received from a neighbor marked as multipath-eligible, then other routes for the same prefix are not eligible to be used as multipaths unless they also came from peers marked as multipath-eligible.
If the best route for an IP prefix did not come from a multipath-eligible peer but there is at least one candidate multipath route for the same prefix from a multipath-eligible peer then multipath is not used.
The no form of this command marks a neighbor or group as non-multipath eligible. The effect of this depends on whether other neighbors and groups are marked as multipath eligible.
Default
no multipath-eligible
Platforms
7705 SAR Gen 2
multiple-option
multiple-option
Syntax
multiple-option {true | false}
no multiple-option
Context
[Tree] (config>filter>ip-filter>entry>match multiple-option)
Full Context
configure filter ip-filter entry match multiple-option
Description
This command configures matching packets that contain one or more than one option fields in the IP header as an IP filter match criterion.
The no form of the command removes the checking of the number of option fields in the IP header as a match criterion.
Default
no multiple-option
Parameters
- true
-
Specifies matching on IP packets that contain more than one option field in the header.
- false
-
Specifies matching on IP packets that do not contain multiple option fields present in the header.
Platforms
7705 SAR Gen 2
multiplier
multiplier
Syntax
multiplier multiplier
no multiplier
Context
[Tree] (config>router>bfd>bfd-template multiplier)
Full Context
configure router bfd bfd-template multiplier
Description
This command specifies the detect multiplier for a BFD session. If a BFD control packet is not received for a period of multiplier x receive-interval (the parameter value of the receive-interval command), the session is declared down.
The no form of this command reverts to the default value.
Default
multiplier 3
Parameters
- multiplier
-
Specifies the multiplier.
Platforms
7705 SAR Gen 2
mvpn-rtcache
mvpn-rtcache
Syntax
mvpn-rtcache [group grp-ip-address] [peer ip-address]
no mvpn-rtcache
Context
[Tree] (debug>router>pim mvpn-rtcache)
Full Context
debug router pim mvpn-rtcache
Description
This command enables debugging for the PIM MVPN route cache.
The no form of this command disables debugging for the PIM MVPN route cache.
Parameters
- grp-ip-address
-
Debugs information associated with the specified group.
- peer-ip-address
-
Debugs information associated with the specified peer.
Platforms
7705 SAR Gen 2
mvrp-control
mvrp-control
Syntax
[no] mvrp-control
Context
[Tree] (config>service>vpls>vpls-group mvrp-control)
Full Context
configure service vpls vpls-group mvrp-control
Description
This command enables MVRP control in the VPLS instances instantiated using the templates for the specified vpls-group. That means the flooding FDB will be created empty and will be populated with endpoints whenever MVRP receives a declaration and a registration on a specific endpoint. Also the VLAN ID associated by the control VPLS with the instantiated VPLS will be declared on service activation by MVRP on all virtual MVRP ports in the control VPLS. Service activation takes place when at least one other SAP is provisioned and brought up under the data VPLS. This is usually a customer facing SAP or a SAP leading outside of the MVRP controlled domain.
The no form of this command disallows MVRP control over this VPLS. The VPLS will be created with a regular FDB and will become as a result active upon creation time. Command change is allowed only when the related vpls-group is in shutdown state.
Default
no mvrp-control
Platforms
7705 SAR Gen 2