m Commands – Part III

Context

[Tree] (config>subscr-mgmt>sub-prof>ingress>policer-control-policy>priority-mbs-thresholds min-thresh-separation)

[Tree] (config>subscr-mgmt>sub-prof>egress>policer-control-policy>priority-mbs-thresholds min-thresh-separation)

Full Context

configure subscriber-mgmt sub-profile ingress policer-control-policy priority-mbs-thresholds min-thresh-separation

configure subscriber-mgmt sub-profile egress policer-control-policy priority-mbs-thresholds min-thresh-separation

Description

The min-thresh-separation command defines the minimum required separation between each in-use discard threshold maintained for each parent policer context associated with the policer-control-policy. The min-thresh-separation value may be overridden on each SAP or sub-profile to which the policy is applied.

The system uses the default or specified min-thresh-separation value in order to determine the minimum separation required between each of the of the parent policer discard thresholds. The system enforces the minimum separation based on the following behavior in two ways. The first is determining the size of the shared-portion for each priority level (when the mbs-contribution command’s optional fixed keyword is not specified):

• When a parent policer instance’s priority level has less than two child policers associated, the shared-portion for the level is zero.

• When a parent policer instance’s priority level has two or more child policers associated, the shared-portion for the level is equal to the current value of min-thresh-separation.

The second function the system uses the min-thresh-separation value for is determining the value per priority level for the fair-portion:

• When a parent policer instance’s priority level has no child policers associated, the fair-portion for the level is zero.

• When a parent policer instance’s priority level has one child policer associated, the fair-portion is equal to the maximum of the min-thresh-separation value and the priority level’s mbs-contribution value.

• When a parent policer instance's priority level has two or more child policers associated, the fair-portion is equal to the maximum of the following:

  • min-thresh-separation value

  • The priority level’s mbs-contribution value less min-thresh-separation value

When the mbs-contribution command’s optional fixed keyword is defined for a priority level within the policy, the system will treat the defined mbs-contribution value as an explicit definition of the priority level’s MBS. While the system will continue to track child policer associations with the parent policer priority levels, the association counters will have no effect. Instead the following rules is used to determine a fixed priority level’s shared-portion and fair-portion:

• If a fixed priority level’s mbs-contribution value is set to zero, both the shared-portion and fair-portion is set to zero

• If the mbs-contribution value is not set to zero:

  • The shared-portion is set to the current min-thresh-separation value

  • The fair-portion is set to the maximum of the following:

min-thresh-separation value

mbs-contribution value less min-thresh-separation value

Each time the min-thresh-separation value is modified, the thresholds for all instances of the parent policer created through association with this policer-control-policy are reevaluated.

Determining the Correct Value for the Minimum Threshold Separation Value

The minimum value for min-thresh-separation should be set equal to the maximum size packet that is handled by the parent policer. This ensures that when a lower priority packet is incrementing the bucket, the size of the increment will not cause the bucket's depth to equal or exceed a higher priority threshold. It also ensures that an unfair packet within a priority level cannot cause the PIR bucket to increment to the discard-all threshold within the priority.

When evaluating maximum packet size, each child policer’s per-packet-offset setting should be taken into consideration. If the maximum size packet is 1518 bytes and a per-packet-offset parameter is configured to add 20 bytes per packet, min-thresh-separation should be set to 1538 due to the fact that the parent policer will increment its PIR bucket using the extra 20 bytes.

In most circumstances, a value larger than the maximum packet size is not necessary. Management of priority level aggregate burst tolerance is intended to be implemented using the priority level mbs-contribution command. Setting a value larger than the maximum packet size will not adversely affect the policer performance, but it may increase the aggregate burst tolerance for each priority level.

The no form of this command returns the policy’s min-thresh-separation value to the default value.

Parameters

size

The size parameter is required when executing the min-thresh-separation command. It is expressed as an integer and specifies the shared portion in bytes or kilobytes that is selected by the trailing bytes or kilobytes keywords. If both bytes and kilobytes are missing, kilobytes is the assumed value. Setting this value has no effect on parent policer instances where the min-thresh-separation value has been overridden.

Values

0 to 16777216

[bytes | kilobytes]

The bytes keyword is optional and is mutually exclusive with the kilobytes keyword. When specified, size is interpreted as specifying the size of min-thresh-separation in bytes.

The kilobytes keyword is optional and is mutually exclusive with the bytes keyword. When specified, size is interpreted as specifying the size of min-thresh-separation in kilobytes.

Default

kilobytes

Platforms

7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR

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.

Values

0 to 16777216

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.

Values

bytes or kilobytes

Default

kilobytes

Platforms

7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR

Context

[Tree] (config>service>ipipe>sap>egress>policy-ctrl-over>mbs-thrshlds min-thresh-separation)

[Tree] (config>service>ipipe>sap>ingress>policy-ctrl-over>mbs-thrshlds min-thresh-separation)

[Tree] (config>service>cpipe>sap>egress>policy-ctrl-over>mbs-thrshlds min-thresh-separation)

[Tree] (config>service>cpipe>sap>ingress>policy-ctrl-over>mbs-thrshlds min-thresh-separation)

[Tree] (config>service>epipe>sap>ingress>policy-ctrl-over>mbs-thrshlds min-thresh-separation)

[Tree] (config>service>epipe>sap>egress>policy-ctrl-over>mbs-thrshlds min-thresh-separation)

Full Context

configure service ipipe sap egress policer-control-override priority-mbs-thresholds min-thresh-separation

configure service ipipe sap ingress policer-control-override priority-mbs-thresholds min-thresh-separation

configure service cpipe sap egress policer-control-override priority-mbs-thresholds min-thresh-separation

configure service cpipe sap ingress policer-control-override priority-mbs-thresholds min-thresh-separation

configure service epipe sap ingress policer-control-override priority-mbs-thresholds min-thresh-separation

configure service epipe sap egress policer-control-override priority-mbs-thresholds min-thresh-separation

Description

This command, within the SAP ingress and egress contexts, is used to override the root arbiter’s parent policer min-thresh-separation parameter that is defined within the policer-control-policy applied to the SAP.

When the override is defined, modifications to the policer-control-policy min-thresh-separation parameter have no effect on the SAP’s parent policer until the override is removed using the no min-thresh-separation command within the SAP.

The no form of this command removes the override and allows the min-thresh-separation setting from the policer-control-policy to control the root arbiter’s parent policer’s minimum discard threshold separation size.

Default

no min-thresh-separation

Parameters

size

The minimum discard threshold separation override value.

Values

1 to 16777216 | default

bytes

Signifies that size is expressed in bytes. The bytes and kilobytes keywords are mutually exclusive and optional. The default is kilobytes.

kilobytes

Signifies that size is expressed in kilobytes. The bytes and kilobytes keywords are mutually exclusive and optional. The default is kilobytes.

Platforms

7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR

• configure service epipe sap ingress policer-control-override priority-mbs-thresholds min-thresh-separation
• configure service ipipe sap ingress policer-control-override priority-mbs-thresholds min-thresh-separation
• configure service ipipe sap egress policer-control-override priority-mbs-thresholds min-thresh-separation
• configure service epipe sap egress policer-control-override priority-mbs-thresholds min-thresh-separation

7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS

• configure service cpipe sap ingress policer-control-override priority-mbs-thresholds min-thresh-separation
• configure service cpipe sap egress policer-control-override priority-mbs-thresholds min-thresh-separation

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.

Values

0 to 16777216 or default

Default

kilobytes

Platforms

7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR

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.

Values

0 to 16777216 or default

Default

kilobytes

Platforms

7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR

Context

[Tree] (config>service>vprn>if>sap>ingress>policy-ctrl-over>mbs-thrshlds min-thresh-separation)

[Tree] (config>service>vprn>if>sap>egress>policy-ctrl-over>mbs-thrshlds min-thresh-separation)

Full Context

configure service vprn interface sap ingress policer-control-override priority-mbs-thresholds min-thresh-separation

configure service vprn 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.

Values

0 to 16777216 or default

Default

kilobytes

Platforms

7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR

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.

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.

Values

0 to 4194304 or default (applies to the 7450 ESS)

0 to 16777216 or default (applies to the 7750 SR or 7950 XRS)

Default

1536

bytes | kilobytes

This parameter indicates whether the size is expressed in bytes or kilobytes.

Default

kilobytes

Platforms

7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR

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.

Values

0 to 3600

Platforms

All

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.

Values

0 to 3600

Platforms

All

Context

[Tree] (config>router>dhcp6>server>pool>prefix>thresholds>minimum-free minimum)

[Tree] (config>service>vprn>dhcp6>server>pool>prefix>thresholds>minimum-free minimum)

Full Context

configure router dhcp6 local-dhcp-server pool prefix thresholds minimum-free minimum

configure service vprn 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.

Values

0 to 100

number

Specifies the number of prefixes.

Values

0 to 4294967295

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

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.

Values

0 to 1

hours

Specifies the minimum required hours of a password before it can be changed again.

Values

0 to 23

minutes

Specifies the minimum required minutes of a password before it can be changed again.

Values

0 to 59

seconds

Specifies the minimum required seconds of a password before it can be changed again.

Values

0 to 59

Note:

This command applies to local users.

Platforms

All

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.

Values

1 to 20

Note:

This command applies to local users.

Platforms

All

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.

Values

2 to 4

Platforms

All

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.

Values

1 to 10000000

Platforms

All

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.

Values

1 to 10000000

Platforms

All

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.

Values

0 to 255

percent

Specifies that the value indicates a percentage.

event-when-depleted

This parameter enables a system-generate event when all available addresses in the pool/subnet of local DHCP server are depleted.

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>service>vprn>dhcp>server>pool>subnet minimum-free)

[Tree] (config>router>dhcp>server>pool>subnet minimum-free)

Full Context

configure service vprn dhcp local-dhcp-server pool subnet minimum-free

configure router 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.

Values

0 to 255

percent

Specifies that the value indicates a percentage.

event-when-depleted

Enables a system-generate event when all available addresses in the pool or subnet of local DHCP server are depleted.

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

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.

Values

1 to 128

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>isa>aa-grp minimum-isa-generation)

Full Context

configure isa application-assurance-group minimum-isa-generation

Description

This command configures the scale parameters for the ISA group. When min-isa-generation is configured as 1, the group and per-ISA limits are the MS-ISA scale.

If there is a mix of ISA 1s and 2s, the min-isa-generation must be left as 1.

When min-isa-gen is configured as 2, the per-isa resource limits shown in the show isa application-assurance-group 1 load-balance output will increase to show ISA2 limits.

Default

minimum-isa-generation 1

Parameters

min-isa-generation

Specifies the minimum ISA Generation allowed in this group.

Values

1 – ISA (ISA1)

2 – ISA2

Platforms

7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s

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.

Values

6 to 50

Platforms

All

Context

[Tree] (config>python>py-pol>cache minimum-lifetimes)

Full Context

configure python python-policy cache minimum-lifetimes

Description

Commands in this context configure minimum-lifetime of Python cache information.

Platforms

All

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.

Values

0 to 59 (maximum 60 minute-numbers)

all

Specifies all minutes.

Platforms

All

Context

[Tree] (config>system>security>ssh>key-re-exchange>client minutes)

[Tree] (config>system>security>ssh>key-re-exchange>server minutes)

Full Context

configure system security ssh key-re-exchange client minutes

configure system security ssh key-re-exchange server minutes

Description

This command configures the maximum time, in minutes, before a key re-exchange is initiated by the server.

The no form of this command reverts to the default value.

Default

minutes 60

Parameters

minutes

Specifies the time interval, in minutes, after which the SSH client will initiate the key-re-exchange.

Values

1 to 1440

Default

60

disable

Specifies that a session will never timeout. To re-enable minutes, enter the command without the disable option.

Platforms

All

Context

[Tree] (config>test-oam>sath>svc-test>dur>perf minutes)

[Tree] (config>test-oam>sath>svc-test>dur>cir minutes)

[Tree] (config>test-oam>sath>svc-test>dur>policing minutes)

[Tree] (config>test-oam>sath>svc-test>dur>cir-pir minutes)

Full Context

configure test-oam service-activation-testhead service-test test-duration performance minutes

configure test-oam service-activation-testhead service-test test-duration cir minutes

configure test-oam service-activation-testhead service-test test-duration policing minutes

configure test-oam service-activation-testhead service-test test-duration cir-pir minutes

Description

This command configures the minutes portion of the duration of performance tests belonging to the service test.

Default

minutes 5

Parameters

minutes

Specifies the number of minutes to run the test.

Values

0 to 59

Platforms

7450 ESS, 7750 SR, 7750 SR-s, 7950 XRS

Context

[Tree] (config>service>vpls>mesh-sdp>eth-cfm mip)

[Tree] (config>service>epipe>spoke-sdp>eth-cfm mip)

[Tree] (config>service>epipe>sap>eth-cfm mip)

[Tree] (config>service>vpls>spoke-sdp>eth-cfm mip)

[Tree] (config>service>vpls>sap>eth-cfm mip)

Full Context

configure service vpls mesh-sdp eth-cfm mip

configure service epipe spoke-sdp eth-cfm mip

configure service epipe sap eth-cfm mip

configure service vpls spoke-sdp eth-cfm mip

configure service vpls sap eth-cfm mip

Description

This command configures Maintenance Intermediate Points (MIPs). The creation rules of the MIP are dependent on the mhf-creation configuration for the MA.

The MIP can be created with a primary VLAN using the primary-vlan-enable vlan-id parameter matching the VLAN configured under the applicable association. Optional VLANs can be added the to the locally-generated CFM frames for egress processing using the cfm-vlan-tag option.

The no form of this command removes the MIP creation request.

Default

no mip

Parameters

qtag1

Specifies the outer VLAN ID.

Values

1 to 4094

qtag2

Specifies the inner VLAN ID and can only be specified if qtag1 is configured.

Values

1 to 4094

mac

Provides a method for manually configuring the MIP MAC address.

mac-address

Specifies the MAC address of the MIP.

Values

6-byte mac-address in the form of xx:xx:xx:xx:xx:xx or xx-xx-xx-xx-xx-xx of the MIP. The MAC address must be unicast. Using the all-zeros address is equivalent to the no form of this command.

default-mac

Specifies to change the MAC address back to the default MAC without having to delete and reconfigure the MIP.

primary-vlan-enable

Provides a method for linking the MIP with the primary VLAN configured under the bridge-identifier for the MA. This is only allowed if the mhf-creation method is static. MIPs cannot be changed from or to primary VLAN functions without first being deleted. This must be configured as part of the creation step and can only be changed by deleting the MIP and re-creating it. Primary VLANs are only supported under Layer 2 Epipe and VPLS services.

vlan-id

Specifies the VLAN ID. This parameter must match the VLAN ID under the bridge-identifier for the MA that is appropriate for this service.

Values

0 to 4094

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS

Context

[Tree] (config>service>template>vpls-sap-template>eth-cfm mip)

Full Context

configure service template vpls-sap-template eth-cfm mip

Description

This command allows Maintenance Intermediate Points (MIPs). The creation rules of the MIP are dependent on the mhf-creation configuration for the MA. This MIP option is only available for default and static mhf-creation methods.

Parameters

primary-vlan-enable

Provides a method for linking the MIP with the primary VLAN configured under the bridge-identifier for the MA. This is only allowed if the mhf-creation method is static. MIPs cannot be changed from or to primary VLAN functions without first being deleted. This must be configured as part of the creation step and can only be changed by deleting the MEP and re-creating it. Primary VLANs are only supported under Ethernet SAPs.

vlan

A required parameter when including primary-vlan-enable. Provides a method for associating the VLAN under the bride-identifier under the MA with the MIP.

vlan-id

Must match the vlan-id under the bridge-identifier for the MA that is appropriate for this service.

Values

0 to 4094

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS

Context

[Tree] (config>router>mpls>mpls-tp>transit-path>reverse-path mip)

[Tree] (config>router>mpls>mpls-tp>transit-path>forward-path mip)

Full Context

configure router mpls mpls-tp transit-path reverse-path mip

configure router mpls mpls-tp transit-path forward-path mip

Description

This command creates a context for maintenance entity group intermediate point (MIP) parameters for the forward path and the reverse path of an MPLS-TP LSP at an LSR.

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS

Context

[Tree] (debug>eth-cfm mip)

Full Context

debug eth-cfm mip

Description

This command specifies the MIP from which to debug the CFM PDUs.

The no form of this command removes the MIP parameters.

Parameters

md-index

Specifies the maintenance domain (MD) index value of the launch point.

Values

1 to 4294967295

ma-index

Specifies the maintenance association (MA) index value of the launch point.

Values

1 to 4294967295

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS

Context

[Tree] (cfg>eth-cfm>domain>assoc>bridge mip-ltr-priority)

Full Context

configure eth-cfm domain association bridge-identifier mip-ltr-priority

Description

This command allows the operator to set the priority of the Linktrace Response Message (ETH-LTR) from a MIP for this association.

Default

7

Parameters

priority

Specifies the priority of the Linktrace Response Message (ETH-LTR) from a MIP.

Values

0 to 7

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS

Context

[Tree] (config>eth-cfm>default-domain>bridge-identifier mip-ltr-priority)

Full Context

configure eth-cfm default-domain bridge-identifier mip-ltr-priority

Description

This command allows the operator to set the priority of the Linktrace Response Message (ETH-LTR) from a MIP for this association.

Default

defer

Parameters

priority

Specifies the priority of the Linktrace Response Message (ETH-LTR) from a MIP. The "defer” value is only supported under the default-domain context and causes mip-ltr-priority to inherit values from the global read-only-system values.

Values

0 to 7, defer

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS

Context

[Tree] (config>mirror mirror-dest)

Full Context

configure mirror mirror-dest

Description

This command creates a context to set up a service that is intended for packet mirroring. It is configured as a service to allow mirrored packets to be directed locally (within the same router) or remotely, over the core of the network and have a far-end decode mirror encapsulation.

The mirror destination service is comprised of destination parameters that define where the mirrored packets are to be sent. It also specifies whether the defined service-id will receive mirrored packets from far-end router over the network core.

The mirror destination service IDs are persistent between boots of the router and are included in the configuration saves. The local sources of mirrored packets for the service ID are defined within the debug mirror mirror-source command that references the same service-id. Up to 255 mirror destination service IDs can be created within a single system.

The mirror-dest command creates or edits a service ID for mirroring purposes. If the service-id does not exist within the context of all defined services, the mirror destination service is created and the context of the CLI is changed to that service ID. If the service-id exists within the context of defined mirror destination services, the CLI context is changed for editing parameters on that service ID. If the service-id exists within the context of another service type, an error message is returned and CLI context is not changed from the current context.

LI source configuration is saved using the li>save command.

The no form of this command removes a mirror destination from the system. The mirror source or li-source associations with the mirror destination service-id do not need to be removed or shutdown first. The mirror destination service-id must be shutdown before the service ID can be removed. When the service ID is removed, all mirror-source or li-source commands that have the service ID defined will also be removed from the system.

Parameters

service-id

The service identification identifies the service in the service domain. This ID is unique to this service and cannot be used by any other service, regardless of service type. The same service ID must be configured on every router that this particular service is defined on.

If particular a service ID already exists for a service, then the same value cannot be used to create a mirror destination service ID with the same value. For example:

If an Epipe service ID 11 exists, then a mirror destination service ID 11 cannot be created. If a VPLS service ID 12 exists, then a mirror destination service ID 12 cannot be created.

If an IES service ID 13 exists, then a mirror destination service ID 13 cannot be created.

Values

service-id:	1 to 2147483647
svc-name:	64 characters maximum

create

Keyword used to create a mirror destination service.

mirror-type

The type describes the encapsulation supported by the mirror service.

Values

The following values apply to the 7750 SR:

ether, ip-only

Values

The following values apply to the 7950 XRS:

ether, ip-only

Values

The following values apply to the 7450 ESS:

ether

name

Configures an optional service name identifier, up to 64 characters, to a given service. This service name can then be used in configuration references, display, and show commands throughout the system. A defined service name can help the service provider or administrator to identify and manage services within the SR OS platforms.

To create a service, you must assign a service ID; however, after it is created, either the service ID or the service name can be used to identify and reference a service.

If a name is not specified at creation time, then SR OS assigns a string version of the service-id as the name.

Service names may not begin with an integer (0 to 9).

Platforms

All

Context

[Tree] (config>li mirror-dest-reservation)

Full Context

configure li mirror-dest-reservation

Description

This command configures a range of service IDs reserved for RADIUS-triggered mirror destination. The range can be expanded or reduced in real time. The range cannot conflict with other service IDs.

The no form of this command removes the service IDs reserved for LI mirror destination services.

Parameters

service-id

Specifies the starting or ending service ID in the range for the mirror destination.

Values

1 to 2147483647

Platforms

All

Context

[Tree] (config>li mirror-dest-template)

Full Context

configure li mirror-dest-template

Description

This command creates a template used by RADIUS-triggered mirror destinations. RADIUS provides the IP destination (and other optional attributes) for the mirror destination and the mirror template provides the remaining mirror destination attributes for mirroring packets remotely over the core of an IP network.

The system supports up to eight mirror destination templates and allows a mirror destination to be swapped in real time. Only new LI sources will use the new attribute of the mirror destination template. Existing LI sources remain unchanged and continue to use the attribute of the previous mirror destination template.

The no form of this command removes a mirror destination template from the system.

Parameters

name

Specifies the template name, up to 32 characters.

mirror-type

Specifies the type of encapsulation supported by the mirror service.

Values

ether, frame-relay, ppp, ip-only, atm-sdu, satop-e1, satop-t1, cesopsn, cesopsn-cas

create

Keyword required to create a template.

Platforms

All

Context

[Tree] (config>li>radius mirror-dest-template)

Full Context

configure li radius mirror-dest-template

Description

This command enables or disables the use of a RADIUS triggered mirror destination template to be used by new LI sources.

Parameters

template-name

Specifies the template name, up to 32 characters. The template must already exist.

Platforms

All

Context

[Tree] (config>app-assure>group>policy>aqp>entry>action mirror-source)

Full Context

configure application-assurance group policy app-qos-policy entry action mirror-source

Description

This command configures an application-based policy mirroring service that uses this AA ISA group’s AQP entry as a mirror source. When configured, AQP entry becomes a mirror source for IP packets seen by the AA (the mirrored packet is an IP packet analyzed by AA and does not include encapsulations present on the incoming interfaces).

Default

no mirror-source

Parameters

all-inclusive

Specifies that all packets during identification phase that could match a given AQP rule are mirrored in addition to packets after an application identification completes that match the AQP rule. This ensures all packets of a given flow are mirrored at a cost of sending unidentified packets that once the application is identified will no longer match this AQP entry.

mirror-service-id

Specifies the mirror source service ID to use for flows that match this policy.

Values

1 to 2147483647

svc-name: 64 characters maximum

Platforms

7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR

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:

1. Filter entry

2. Subscriber (applies to the 7750 SR and 7450 ESS)

3. SAP

4. 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.

Values

service-id:	1 to 2147483647
svc-name:	64 characters maximum

Platforms

All

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:

1. Filter entry

2. Subscriber (applies to the 7750 SR and 7450 ESS)

3. SAP

4. Physical port

The precedence is structured so the most specific match criteria has precedence over a less specific match. For example, if a mirror-source defines a port and a SAP on that port, then a packet arriving on the SAP will be mirrored using the SAP mirror (and not mirrored using the Port mirror) because the SAP is more specific than the port.

The mirror-source configuration is not saved when a configuration is saved. A mirror-source manually configured within an ASCII configuration file will not be preserved if that file is overwritten by a save command. Define the mirror-source within a file associated with a config exec command to make a mirror-source persistent between system reboots.

By default, all mirror destination service IDs have a mirror-source associated with them. The mirror-source is not technically created with this command. Instead the service ID provides a contextual node for storing the current mirroring sources for the associated mirror destination service ID. The mirror-source is created for the mirror service when the operator enters the debug>mirror-source svcId for the first time. If the operator enters li>li-source svcId for the first time, an LI source is created for the mirror service. The mirror-source is also automatically removed when the mirror destination service ID is deleted from the system.

The no form of this command deletes all related source commands within the context of the mirror-source service-id. The command does not remove the service ID from the system.

Parameters

service-id

Specifies the mirror destination service ID for which match criteria will be defined. The service-id must already exist within the system.

Values

service-id: 1 to 2147483647

svc-name: 64 characters maximum

Platforms

All

Context

[Tree] (debug>router>igmp misc)

Full Context

debug router igmp misc

Description

This command enables debugging for IGMP miscellaneous information.

The no form of the command disables the debugging.

Platforms

All

Output

The following output is an example of debugged IGMP miscellaneous information.

A:ALA-CA# debug router 100 igmp misc 
*A:ALA-CA# show debug 
debug
    router "100"
        igmp
            misc
        exit
    exit
exit
*A:ALA-CA# 

Context

[Tree] (debug>router>rsvp>event misc)

[Tree] (debug>router>mpls>event misc)

Full Context

debug router rsvp event misc

debug router mpls event misc

Description

This command debugs miscellaneous events.

The no form of the command disables the debugging.

Parameters

detail

Displays detailed information about miscellaneous events.

Platforms

All

Context

[Tree] (debug>router>mtrace misc)

[Tree] (debug>router>mtrace2 misc)

Full Context

debug router mtrace misc

debug router mtrace2 misc

Description

This command enables debugging for mtrace and mtrace2 miscellaneous.

Platforms

All

Context

[Tree] (debug>router>isis misc)

Full Context

debug router isis misc

Description

This command enables debugging for IS-IS misc.

The no form of the command disables debugging.

Platforms

All

Context

[Tree] (debug>router>ospf misc)

[Tree] (debug>router>ospf3 misc)

Full Context

debug router ospf misc

debug router ospf3 misc

Description

This command enables debugging for miscellaneous OSPF events.

Platforms

All

Context

[Tree] (config>port>otu>pm-tti mismatch-reaction)

Full Context

configure port otu pm-tti mismatch-reaction

Description

This command allows the user to configure the consequent action to a pm-tti mismatch.

The no form of this command reverts to the default value.

Default

n/a, the received traffic is passed through.

Parameters

squelch-rx

Specifies that the received traffic is blocked.

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS

Context

[Tree] (config>port>otu>psi-payload mismatch-reaction)

Full Context

configure port otu psi-payload mismatch-reaction

Description

This command allows the user to configure the consequent action to a psi-payload type mismatch.

Parameters

none

Specifies the received traffic is passed through.

squelch-rx

Specifies the received traffic is blocked.

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS

Context

[Tree] (config>port>otu>sm-tti mismatch-reaction)

Full Context

configure port otu sm-tti mismatch-reaction

Description

This command allows the user to configure the consequent action to a sm-tti mismatch.

Default

n/a

Parameters

none

Specifies that the received traffic is passed through.

squelch-rx

Specifies that the received traffic is blocked.

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS

Context

[Tree] (config>app-assure>group>statistics>tca>gtp-filter missing-mandatory-ie)

Full Context

configure application-assurance group statistics threshold-crossing-alert gtp-filter missing-mandatory-ie

Description

This command configures a TCA for the counter capturing drops due to the GTP filter missing mandatory IE check. A missing-mandatory-ie drop TCA can be created for traffic generated from the subscriber side of AA (from-sub) or for traffic generated from the network toward the AA subscriber (to-sub). The create keyword is mandatory when creating a missing-mandatory-ie TCA.

Parameters

direction

Specifies the traffic direction.

Values

from-sub, to-sub

create

Keyword used to create the TCA.

Platforms

7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR

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.

If the user changes the value of the sdp-revert-time timer, it will take effect only at the next use of the timer. Any timer which is outstanding at the time of the change will be restarted with the new value.

If class based forwarding is enabled for this SDP, the forwarding of the packets over the RSVP LSPs will be based on the FC of the packet as in current implementation. When the SDP activates the LDP LSP type, then packets are forwarded over the LDP ECMP paths using the regular hash routine.

In the case of the LDP/BGP SDP, the service manager will prefer the LDP LSP type over the BGP LSP type. The service manager will re-program the card with the BGP LSP if available otherwise it brings down the SDP operationally.

Also note the following difference in behavior of the LDP/BGP SDP compared to that of an RSVP/LDP SDP. For a given /32 prefix, only a single route will exist in the routing table: the IGP route or the BGP route. Thus, either the LDP FEC or the BGP label route is active at any given time. The impact of this is that the tunnel table needs to be re-programmed each time a route is deactivated and the other is activated. Furthermore, the SDP revert-time cannot be used since there is no situation where both LSP types are active for the same /32 prefix.

The no form of this command disables the mixed-LSP mode of operation. The user first has to remove one of the LSP types from the SDP configuration or the command will fail.

Default

no mixed-lsp-mode

Platforms

All

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.

Values

1 to 6 s in 1-s increments, 500ms

Platforms

All

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.

Values

0 to 255

Platforms

All

Context

[Tree] (config>anysec mka-over-ip)

Full Context

configure anysec mka-over-ip

Description

Commands in this context configure the MACsec Key Agreement (MKA) over IP.

Platforms

7750 SR-1-24D, 7750 SR-1-46S, 7750 SR-1-48D, 7750 SR-1-92S, 7750 SR-1x-48D, 7750 SR-1x-92S, 7750 SR-1se

Context

[Tree] (config>anysec>mka-ip mka-udp-port)

Full Context

configure anysec mka-over-ip mka-udp-port

Description

This command configures the UDP port that identifies the MKA packet on the system.

Nokia recommends configuring this UDP port network wide. In addition, the user should ensure the UDP port is not used by any other protocols in the network.

The no form of this command removes the configured UDP port.

Default

no mka-udp-port

Parameters

port

Specifies the UPD port that identifies the MKA packet.

Values

1024 to 49151

Platforms

7750 SR-1-24D, 7750 SR-1-46S, 7750 SR-1-48D, 7750 SR-1-92S, 7750 SR-1x-48D, 7750 SR-1x-92S, 7750 SR-1se

Context

[Tree] (config>redundancy>multi-chassis>peer>sync mld)

Full Context

configure redundancy multi-chassis peer sync mld

Description

This command specifies whether MLD protocol information should be synchronized with the multi-chassis peer.

Default

no mld

Platforms

All

Context

[Tree] (config>service>vprn mld)

Full Context

configure service vprn mld

Description

Commands in this context configure Multicast Listener Discovery (MLD) parameters.

The no form of this command disables MLD.

Default

no mld

Platforms

All

Context

[Tree] (config>router mld)

Full Context

configure router mld

Description

Commands in this context configure Multicast Listener Discovery (MLD) parameters.

The no form of the command disables MLD.

Default

no mld

Platforms

All

Context

[Tree] (config>subscr-mgmt>loc-user-db>ppp>host mld-parameters)

[Tree] (config>subscr-mgmt>loc-user-db>ipoe>host mld-parameters)

Full Context

configure subscriber-mgmt local-user-db ppp host mld-parameters

configure subscriber-mgmt local-user-db ipoe host mld-parameters

Description

Commands in this context configure an MLD import policy.

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>subscr-mgmt mld-policy)

Full Context

configure subscriber-mgmt mld-policy

Description

Commands in this context create an MLD policy.

The no form of this command reverts to the default.

Parameters

mld-policy-name

Specifies the MLD policy name up to 32 characters.

create

Keyword required to create the configuration context.

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>subscr-mgmt>sub-prof mld-policy)

Full Context

configure subscriber-mgmt sub-profile mld-policy

Description

This command enables Multicast Listener Discovery (MLD) processing per subscriber host.

The no form of this command reverts to the default.

Default

no mld-policy

Parameters

policy-name

Specifies the name of the MLD policy, up to 32 characters. The MLD policy must be defined in the config>subscr-mgmt context.

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>service>vpls>spoke-sdp mld-snooping)

[Tree] (config>service>vpls>allow-ip-int-bind mld-snooping)

[Tree] (config>service>vpls mld-snooping)

[Tree] (config>service>vpls>sap mld-snooping)

[Tree] (config>service>vpls>mesh-sdp mld-snooping)

Full Context

configure service vpls spoke-sdp mld-snooping

configure service vpls allow-ip-int-bind mld-snooping

configure service vpls mld-snooping

configure service vpls sap mld-snooping

configure service vpls mesh-sdp mld-snooping

Description

Commands in this context configure MLD snooping parameters.

Platforms

All

Context

[Tree] (config>redundancy>multi-chassis>peer>sync mld-snooping)

Full Context

configure redundancy multi-chassis peer sync mld-snooping

Description

This command is not supported. It is not blocked for backwards-compatibility reasons but has no effect on the system if configured.

Default

no mld-snooping

Platforms

All

Context

[Tree] (debug>service>id mld-snooping)

Full Context

debug service id mld-snooping

Description

This command enables and configures MLD-snooping debugging.

The no form of this command disables MLD-snooping debugging.

Platforms

All

Context

[Tree] (config>service>vpls>vxlan mld-snooping)

Full Context

configure service vpls vxlan mld-snooping

Description

This command enables the MLD snooping context.

Platforms

All

Context

[Tree] (config>service>vpls>pbb>bvpls mld-snooping)

[Tree] (config>service>vpls>pbb>bvpls>sdp mld-snooping)

[Tree] (config>service>vpls>pbb>bvpls>sap mld-snooping)

Full Context

configure service vpls pbb backbone-vpls mld-snooping

configure service vpls pbb backbone-vpls sdp mld-snooping

configure service vpls pbb backbone-vpls sap mld-snooping

Description

This command configures MLD snooping attributes for I-VPLS.

Platforms

All

Context

[Tree] (config>service>vpls>provider-tunnel>selective mldp)

[Tree] (config>service>vpls>provider-tunnel>inclusive mldp)

Full Context

configure service vpls provider-tunnel selective mldp

configure service vpls provider-tunnel inclusive mldp

Description

This command configures the use of MLDP as a protocol for an LDP P2MP LSP that is used for forwarding Broadcast, Unicast unknown, and Multicast (BUM) packets of a VPLS or B-VPLS instance. This command is also used for forwarding IP multicast packets of an EVPN VPLS or R-VPLS service (when used under the selective context).

The no form of this command disables the use of MLDP as a protocol to set up the P2MP LSP.

Platforms

All

Context

[Tree] (config>service>vprn>mvpn>pt>inclusive mldp)

[Tree] (config>service>vprn>mvpn>pt>selective mldp)

Full Context

configure service vprn mvpn provider-tunnel inclusive mldp

configure service vprn mvpn provider-tunnel selective mldp

Description

This command enables use of P2MP mLDP LSP as inclusive or selective PMSI tunnels.

For multi-stream S-PMSI, either LDP or RSVP-TE must first be configured before multi-stream policy can be configured.

Default

no mldp

Platforms

All

Context

[Tree] (config>subscr-mgmt>ppp-policy mlppp)

Full Context

configure subscriber-mgmt ppp-policy mlppp

Description

Commands in this context configure multi-link PPP parameters.

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s

Context

[Tree] (config>subscr-mgmt>gtp>peer-profile mme)

Full Context

configure subscriber-mgmt gtp peer-profile mme

Description

This command configures parameters specific to a Mobility Management Entity (MME) peer.

Platforms

7750 SR, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>service>vpls>mrp mmrp)

Full Context

configure service vpls mrp mmrp

Description

This command configures MMRP parameters.

Platforms

All

Context

[Tree] (config>mcast-mgmt>chassis-level mmrp-impm-override)

Full Context

configure mcast-management chassis-level mmrp-impm-override

Description

This command enables ingress Multicast Path Management (IMPM) from monitoring PIM and IGMP.

The no form of this command disables the IMPM monitoring.

Platforms

7450 ESS, 7750 SR-1x-48D, 7750 SR-1x-92S, 7750 SR-7/12/12e, 7750 SR-s, 7950 XRS, VSR

Context

[Tree] (debug>service>id>mrp mmrp-mac)

Full Context

debug service id mrp mmrp-mac

Description

This command filters debug events and only shows events related to the MAC address specified.

The no form of this command removes the debug filter.

Parameters

ieee-address

xx:xx:xx:xx:xx:xx or xx-xx-xx-xx-xx-xx (cannot be all zeros)

Platforms

All

Context

[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw mobility)

[Tree] (config>service>ies>sub-if>grp-if>wlan-gw mobility)

Full Context

configure service vprn subscriber-interface group-interface wlan-gw mobility

configure service ies subscriber-interface group-interface wlan-gw mobility

Description

Commands in this context configure mobility parameters.

Platforms

7750 SR, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw>vlan-tag-ranges>range>xconnect mobility-acct-updates)

[Tree] (config>service>ies>sub-if>grp-if>wlan-gw>vlan-tag-ranges>range>xconnect mobility-acct-updates)

Full Context

configure service vprn subscriber-interface group-interface wlan-gw vlan-tag-ranges range xconnect mobility-acct-updates

configure service ies subscriber-interface group-interface wlan-gw vlan-tag-ranges range xconnect mobility-acct-updates

Description

This command enables the administrative state to send mobility-triggered accounting interim updates.

The no form of this command disables sending the mobility-triggered accounting updates.

Platforms

7750 SR, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>service>vprn>wlan-gw mobility-triggered-acct)

[Tree] (config>router>wlan-gw mobility-triggered-acct)

Full Context

configure service vprn wlan-gw mobility-triggered-acct

configure router wlan-gw mobility-triggered-acct

Description

Commands in this context configure the mobility-triggered-accounting in wlan-gw context under router or VPRN service.

Platforms

7750 SR, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (debug>router>ip>dhcp mode)

[Tree] (debug>router>local-dhcp-server mode)

[Tree] (debug>router>ip>dhcp6 mode)

Full Context

debug router ip dhcp mode

debug router local-dhcp-server mode

debug router ip dhcp6 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

All

• debug router ip dhcp mode
• debug router ip dhcp6 mode

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

• debug router local-dhcp-server mode

Context

[Tree] (debug>service>id>ppp>packet mode)

Full Context

debug service id ppp packet mode

Description

This command specifies PPP packet debug mode.

The no form of this command disables debugging.

Parameters

dropped-only

Displays only dropped packets.

ingr-and-dropped

Displays only ingress packet and dropped packets.

egr-ingr-and-dropped

Displays ingress, egress and dropped packets.

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>service>ies>if>urpf-check mode)

[Tree] (config>service>vprn>sub-if>grp-if>urpf-check mode)

[Tree] (config>service>ies>if>ipv6>urpf-check mode)

[Tree] (config>service>vprn>if>ipv6>urpf-check mode)

[Tree] (config>service>ies>sub-if>grp-if>ipv6>urpf-check mode)

[Tree] (config>service>vprn>if>urpf-check mode)

[Tree] (config>service>vprn>nw-if>urpf-check mode)

Full Context

configure service ies interface urpf-check mode

configure service vprn subscriber-interface group-interface urpf-check mode

configure service ies interface ipv6 urpf-check mode

configure service vprn interface ipv6 urpf-check mode

configure service ies subscriber-interface group-interface ipv6 urpf-check mode

configure service vprn interface urpf-check mode

configure service vprn network-interface urpf-check mode

Description

This command specifies the mode of unicast RPF check.

The no form of this command reverts to the default (strict) mode.

Default

mode strict

Parameters

strict

When specified, uRPF checks whether incoming packet has a source address that matches a prefix in the routing table, and whether the interface expects to receive a packet with this source address prefix.

loose

In loose mode, uRPF checks whether incoming packet has source address with a corresponding prefix in the routing table. However, the loose mode does not check whether the interface expects to receive a packet with a specific source address prefix. This object is valid only when urpf-check is enabled.

strict-no-ecmp

When a packet is received on an interface in this mode and the SA matches an ECMP route the packet is dropped by uRPF.

Platforms

All

• configure service vprn network-interface urpf-check mode
• configure service ies interface ipv6 urpf-check mode
• configure service ies interface urpf-check mode
• configure service vprn interface urpf-check mode
• configure service vprn interface ipv6 urpf-check mode

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

• configure service ies subscriber-interface group-interface ipv6 urpf-check mode
• configure service vprn subscriber-interface group-interface urpf-check mode

Context

[Tree] (config>subscr-mgmt>git>ipv4>urpf-check mode)

Full Context

configure subscriber-mgmt group-interface-template ipv4 urpf-check mode

Description

This command configures the mode of Unicast RPF (uRPF) check.

The no form of this command reverts to the default.

Default

mode strict

Parameters

strict

Specifies that the uRPF checks whether the incoming packet has a source IP address that matches a prefix in the routing table, and whether the interface expects to receive a packet with this source IP address prefix.

loose

Specifies that the uRPF checks whether the incoming packet has a source IP address with a corresponding prefix in the routing table. However, the loose mode does not check whether the interface expects to receive a packet with a specific source IP address prefix. This object is valid only when the urpf-check command is enabled.

strict-no-ecmp

Specifies that when a packet is received on an interface in this mode and the SA matches an ECMP route, the packet is dropped by uRPF.

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>system>pwr-mgmt mode)

Full Context

configure system power-management mode

Description

This command sets the power mode.

Default

mode basic

Parameters

none

Specifies that there is no management of power to modules. In this mode, no gradual shutdown of active XCMs and XMAs is enforced. No spare capacity is reserved and any APEQ failure may result in brownouts or card failures.

basic

Specifies that the node will bring up as many provisioned modules (in order of priority) as possible using the N+1 algorithm. In basic mode the system shuts down IO cards when power capacity drops below the Power Safety Level.

advanced

Specifies that the operator can maintain a spare APEQ as long as possible to make it immune to the possibility of power brown-outs. In advanced mode, the system starts shutting down IO cards when the power capacity drops below the Power Safety Level + Max rated APEQ.

Platforms

7750 SR-1s, 7750 SR-2s, 7750 SR-2se, 7750 SR-7s, 7750 SR-14s, 7950 XRS

Context

[Tree] (config>port>dwdm>coherent mode)

Full Context

configure port dwdm coherent mode

Description

This command configures the mode used to compensate for chromatic dispersion.

Parameters

automatic

Sets to automatic mode.

manual

Sets to manual mode.

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS

Context

[Tree] (config>port>ethernet>elmi mode)

Full Context

configure port ethernet elmi mode

Description

This command configures the Ethernet LMI mode.

Parameters

none

Specifies that the E LMI mode is set to none.

uni-n

Specifies that the E LMI mode is set to UNI-N.

Platforms

All

Context

[Tree] (config>lag mode)

[Tree] (config>port>sonet-sdh>path mode)

[Tree] (config>port>tdm>e1>channel-group mode)

[Tree] (config>port>tdm>ds1>channel-group mode)

[Tree] (config>port>tdm>ds3 mode)

[Tree] (config>port>ethernet mode)

[Tree] (config>port>tdm>e3 mode)

Full Context

configure lag mode

configure port sonet-sdh path mode

configure port tdm e1 channel-group mode

configure port tdm ds1 channel-group mode

configure port tdm ds3 mode

configure port ethernet mode

configure port tdm e3 mode

Description

This command configures an Ethernet port, TDM channel, or SONET/SDH path (sub-port) for access, network, or hybrid mode operation.

An access port or channel is used for customer facing traffic on which services are configured. A Service Access Point (SAP) can only be configured on an access port or channel. When a port is configured for access mode, the appropriate encap-type must be specified to distinguish the services on the port or SONET path. Once an Ethernet port, a TDM channel or a SONET path has been configured for access mode, multiple services can be configured on the Ethernet port, a TDM channel or SONET path.

A network port or channel participates in the service provider transport or infrastructure network when a network mode is selected. When the network option is configured, the encap-type cannot be configured for the port/channel.

When network mode is selected on a SONET/SDH path, the appropriate control protocols are activated when the need arises. For example, configuring an IP interface on the SONET path activates IPCP while the removal of the IP interface causes the IPCP to be removed. The same applies for MPLS, MPLSCP, and OSICP. When configuring a SONET/SDH port, the mode command must be entered in the channel context or an error message is generated.

A hybrid Ethernet port allows the combination of network and access modes of operation on a per-VLAN basis and must be configured as either dot1q or QinQ encapsulation.

When the hybrid port is configured to the dot1q encapsulation, the user configures a SAP inside a service simply by providing the SAP ID which must include the port-id value of the hybrid mode port and an unused VLAN tag value. The format is <port-id>:qtag1. A SAP of format <port-id>:* also supported.

The user configures a network IP interface under config>router>if>port by providing the port name which consists of the port-id of the hybrid mode port and an unused VLAN tag value. The format is <port-id>:qtag1. The user must explicitly enter a valid value for qtag1. The <port-id>:* value is not supported on a network IP interface. The 4096 VLAN tag space on the port is shared among VLAN SAPs and VLAN network IP interfaces.

When the hybrid port is configured to QinQ encapsulation, the user configures a SAP inside a service simply by providing the SAP ID which must include the port-id value of the hybrid mode port and the outer and inner VLAN tag values. The format is <port-id>:qtag1.qtag2. A SAP of format <port-id>: qtag1.* is also supported. The outer VLAN tag value must not have been used to create an IP network interface on this port. In addition, the qtag1.qtag2 value combination must not have been used by another SAP on this port.

The user configures a network IP interface under config>router>if>port by providing the port name which consists of the port-id of the hybrid mode port and a VLAN tag value. The format is <port-id>:qtag1.*. An outer VLAN tag qtag2 of * creates an IP network interface. In addition, the qtag1.qtag2 value combination must not have been used on another SAP or IP network interface on this port.

The no form of this command restores the default.

Default

mode network — For Ethernet ports

mode access — For TDM channel or SONET paths

Parameters

access

Configures the Ethernet port, TDM channel or SONET path as service access.

network

Configures the Ethernet port, TDM channel or SONET path for transport network use.

hybrid

Configures the Ethernet port for hybrid use.

Platforms

All

• configure port ethernet mode
• configure lag mode

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS

• configure port sonet-sdh path mode

7450 ESS, 7750 SR-7/12/12e, 7750 SR-a, 7750 SR-e

• configure port tdm ds3 mode
• configure port tdm e1 channel-group mode
• configure port tdm ds1 channel-group mode
• configure port tdm e3 mode

Context

[Tree] (config>port>ethernet>efm-oam mode)

Full Context

configure port ethernet efm-oam mode

Description

This command configures the mode of OAM operation for this Ethernet port. These two modes differ in that active mode causes the port to continually send out efm-oam info PDUs while passive mode waits for the peer to initiate the negotiation process. A passive mode port cannot initiate monitoring activities (such as loopback) with the peer.

Default

mode active

Parameters

active

Provides capability to initiate negotiation and monitoring activities.

passive

Relies on peer to initiate negotiation and monitoring activities.

Platforms

All

Context

[Tree] (config>service>system>bgp-evpn>eth-seg>service-carving mode)

Full Context

configure service system bgp-evpn ethernet-segment service-carving mode

Description

This command configures the service-carving mode. This determines how the DF is elected for a specified Ethernet-Segment and service.

Default

mode auto

Parameters

auto

This mode is the service-carving algorithm defined in RFC 7432. The DF for the service is calculated based on the modulo function of the service (identified by either the evi or the isid) and the number of PEs.

manual

In this mode the DF is elected based on the manual configuration added in the service-carving>manual context.

off

In this mode all the services elect the same DF PE (assuming the same PEs are active for all the configured services). The PE with the lowest IP is elected as DF for the Ethernet-Segment.

Platforms

All

Context

[Tree] (config>service>vpls>pim-snooping mode)

Full Context

configure service vpls pim-snooping mode

Description

This command sets the PIM snooping mode to proxy or plain snooping.

Parameters

mode

Specifies PIM snooping mode

Values

snoop, proxy

Default

proxy

Platforms

All

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

All

Context

[Tree] (debug>service>id>arp-host mode)

Full Context

debug service id arp-host mode

Description

This command configures the ARP host tracing mode.

Parameters

all

Debugs all dropped packets.

dropped-only

Only displays dropped packets.

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (debug>service>id>igmp-snooping mode)

Full Context

debug service id igmp-snooping mode

Description

This command enables and configures the IGMP tracing mode.

The no form of this command disables the configures the IGMP tracing mode.

Platforms

All

Context

[Tree] (debug>service>id>mld mode)

Full Context

debug service id mld-snooping mode

Description

This command enables and configures the MLD tracing mode.

The no form of this command disables the configures the MLD tracing mode.

Platforms

All

Context

[Tree] (config>service>vprn>msdp>group mode)

Full Context

configure service vprn msdp group mode

Description

This command configures groups of peers in a full mesh topology to limit excessive flooding of source-active messages to neighboring peers.

Multicast Source Discovery Protocol (MSDP) peers can be configured grouped in a full-mesh topology that prevents excessive flooding of source-active messages to neighboring peers.

In a meshed configuration, all members of the group must have a peer connection with every other mesh group member. If this rule is not adhered to, then unpredictable results may occur.

Default

mode standard

Parameters

mesh-group

Specifies that source-active message received from a mesh group member are always accepted but are not flooded to other members of the same mesh group. These source-active messages are only flooded to non-mesh group peers or members of other mesh groups.

standard

Specifies a non-meshed mode.

Platforms

All

Context

[Tree] (config>service>vprn>nat>outside>pool mode)

Full Context

configure service vprn nat outside pool mode

Description

This command configures the mode of operation of this NAT address pool.

The mode value is only relevant while the value of pool type is equal to largeScale; while the value of pool type is equal to l2Aware, the mode of operation is always NAPT.

Default

mode auto

Parameters

napt

Specifies NAPT (Network Address Port Translation)

auto

The system selects the actual mode based upon other configuration parameters; the actual mode can be NAPT or 1:1 NAT (also known as 'Basic NAT').

one-to-one

Indicates 1:1 NAT (also known as 'Basic NAT')

Platforms

7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (debug>service>id>dhcp mode)

Full Context

debug service id dhcp mode

Description

This command configures the DHCP tracing mode.

The no form of the command disables debugging.

Parameters

dropped-only

Only displays dropped packets.

ingr-and-dropped

Only displays ingress packet and dropped packets.

egr-ingr-and-dropped

Displays ingress, egress and dropped packets.

Platforms

All

Context

[Tree] (config>app-assure>group>gtp mode)

Full Context

configure application-assurance group gtp mode

Description

This command is used to either untunnel GTP-U traffic received on UDP port number 2152, or apply GTP filtering/firewall rules as specified under this GTP CLI context.

Default

mode filtering

Parameters

mode

Specifies the operational mode of the command.

Values

filtering — AA applies GTP filtering rules to GTP-U traffic, without further analysis of IP traffic tunneled within GTP.

untunneling — AA untunnels GTP traffic and provides analytical reporting of the applications running within the GTP tunnels. The rest of the commands under GTP CLI context (such as GTP-filter and event-log) are not applicable in this mode.

For AA to untunnel GTP traffic, the operator must configure "gtp” under the partition by using the config>app-assure>group>gtp command.

The following caveats apply:

• Only GTP-U traffic with TID <> 0 is untunneled.

• Any UDP but non-GTP traffic that uses port 2152 will be identified as UDP traffic.

• Only GTP-U packets with message type: G-PDU (0xFF) is untunneled. Other GTP-U packets with different message types are reported as GTP Protocol.

• Only GTP-u packets with non-fragmented outer IP and no IPv4 options or IPv6 extension headers are untunneled. Otherwise, no inner GTP tunnel classification is performed and the traffic is identified and reported as GTP protocol.

Platforms

7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>router>nat>outside>pool mode)

Full Context

configure router nat outside pool mode

Description

This command specifies the mode of operation of this NAT address pool.

The no form of the command reverts to the default.

Default

auto

Parameters

{auto | napt | one-to-one}

Specifies the mode of operation of this NAT pool.

Platforms

7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>router>msdp>group mode)

Full Context

configure router msdp group mode

Description

This command configures the MSDP group topology. MSDP peers can be configured in a full-mesh topology to prevent excessive flooding of SA messages to neighboring peers.

In a mesh group, SA messages received from a mesh group member are always accepted but are not flooded to other members of the same mesh group. These SA messages are only flooded to non-mesh group peers or members of other mesh groups.

Default

mode standard

Parameters

mesh-group

Keyword to configure to group in meshed mode.

standard

Keyword to configure the group in non-meshed mode.

Platforms

All

Context

[Tree] (config>router>if>urpf-check mode)

[Tree] (config>router>if>ipv6>urpf-check mode)

Full Context

configure router interface urpf-check mode

configure router interface ipv6 urpf-check mode

Description

This command specifies the mode of unicast RPF check.

The no form of this command reverts to the default (strict) mode.

Default

mode strict

Parameters

strict

When specified, uRPF checks whether incoming packet has a source address that matches a prefix in the routing table, and whether the interface expects to receive a packet with this source address prefix.

loose

In loose mode, uRPF checks whether incoming packet has source address with a corresponding prefix in the routing table. However, the loose mode does not check whether the interface expects to receive a packet with a specific source address prefix. This object is valid only when urpf-check is enabled.

strict-no-ecmp

When a packet is received on an interface in this mode and the SA matches an ECMP route the packet is dropped by uRPF.

Platforms

All

Context

[Tree] (config>router>segment-routing>maintenance-policy mode)

Full Context

configure router segment-routing maintenance-policy mode

Description

This command specifies the data path programming and protection mechanism for SR policy candidate paths to which the maintenance policy is applied.

In both the linear mode and ecmp-protected modes, if two or more candidate paths of the same {headend, color, endpoint} and also have the same mode, then the best preference path is treated as the primary while the next best preference path is the standby. If a third path is present in the linear mode, then this is treated as a tertiary and also programmed in the IOM.

If the currently active path goes unavailable due to S-BFD, the system failovers to the next best preference available candidate path. If S-BFD is down on all segment lists of all programmed candidate paths of an SR Policy, then the SR Policy is marked as down in TTM.

If the default mode is specified, the router only programs the segment lists of the best preference paths in the IOM.

The no form of this command removes the configured mode.

Default

no mode

Parameters

ecmp-protected

Specifies only the top two routes (paths) are programmed in the IOM. Up to 32 segment lists can be programmed for each path.

linear

Specifies the top three routes are programmed in the IOM. Only one segment list is allowed per path.

Platforms

All

Context

[Tree] (config>system>telemetry>persistent-subscriptions>subscription mode)

Full Context

configure system telemetry persistent-subscriptions subscription mode

Description

This command configures the subscription path mode for telemetry notifications that are sent for the persistent subscription.

Default

mode target-defined

Parameters

target-defined

Keyword specifying that target defined mode is used.

on-change

Keyword specifying that on change mode is used.

sample

Keyword specifying that sample mode is used.

Platforms

All

Context

[Tree] (config>port>aps mode-annexb)

Full Context

configure port aps mode-annexb

Description

This command configures the APS group for 1+1 Optimized operation as described in Annex B of ITU.T G.841. Note that Annex B operates in non-revertive bi-directional switching mode only as defined in G.841.

Platforms

7450 ESS, 7750 SR-7/12/12e, 7750 SR-a, 7750 SR-e

Context

[Tree] (config>port modify-buffer-allocation-rate)

Full Context

configure port modify-buffer-allocation-rate

Description

Commands in this context configure ingress and egress percentage of rate parameters. This command only applies to physical ports (for example, it will not work on APS or similar logical ports). The percentage of rate commands are used to define a percentage value that affects the amount of buffers used by ingress and egress port managed buffer space. Enter the modify-buffer-allocation-rate context when editing the port’s percentage of rate commands.

Platforms

All

Context

[Tree] (config>system>bluetooth module)

Full Context

configure system bluetooth module

Description

Commands in this context define Bluetooth parameters for the specific CPM slot.

Parameters

cpm-slot

Specifies the CPM slot.

Values

{A | B | C | D}

Platforms

7750 SR-1, 7750 SR-s, 7950 XRS-20e

Context

[Tree] (debug>router>pim mofrr)

Full Context

debug router pim mofrr

Description

This command enables debugging for PIM multicast fast failover (MoFRR).

The no form of this command disables MoFRR debugging.

Platforms

All

Context

[Tree] (config>port>ethernet>access>egress>vport mon-hw-agg-shaper-sch)

[Tree] (config>port>ethernet>egress mon-hw-agg-shaper-sch)

Full Context

configure port ethernet access egress vport mon-hw-agg-shaper-sch

configure port ethernet egress mon-hw-agg-shaper-sch

Description

This command enables congestion monitoring of the hardware aggregate shaper scheduler on the specified port or vport.

The no form of this command disables congestion monitoring.

Default

no mon-hw-agg-shaper-sch

Platforms

7750 SR-1, 7750 SR-s

Context

[Tree] (config>port>ethernet>access>egress>vport mon-port-sch)

[Tree] (config>port>ethernet mon-port-sch)

Full Context

configure port ethernet access egress vport mon-port-sch

configure port ethernet mon-port-sch

Description

This command enables congestion monitoring on an Egress Port Scheduler (EPS) that is applied to a physical port or to a Vport.

Congestion monitoring must be further configured under the port-scheduler CLI hierarchy. Once the congestion monitoring is in effect, the offered rate (incoming traffic) is compared to the configured port-scheduler congestion threshold. The results of these measurements are stored as the number of samples representing the number of times the offered rates exceeded the configured congestion threshold since the last clearing of the stats. Therefore, the results represent the number of times that the port-scheduler that is applied to a port/Vport was congested since the last reset of the stats (via a clear command).

The no form of this command disables congestion monitoring.

Default

no mon-port-sch

Platforms

All

Context

[Tree] (config>service>ies>sub-if>wlan-gw>redundancy monitor)

Full Context

configure service ies subscriber-interface wlan-gw redundancy monitor

Description

This command specifies an IPv4 route (prefix/length) per subscriber-interface to be monitored in the FDB to determine liveness of the subscriber-interface (and consequently all associated group-interfaces of type wlangw) on a peer WLAN-GW. This route is the one that is advertised in routing by the peer WLAN-GW when the subscriber-interface and WLAN-GW group are operationally up.

Parameters

ip-prefix/length

Specifies the IP prefix and length.

Values

ip-prefix: a.b.c.d

ip-prefix-length: 0 to 32

Platforms

7750 SR, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>service>vprn>nat>outside>pool>redundancy monitor)

[Tree] (config>router>nat>outside>pool>redundancy monitor)

Full Context

configure service vprn nat outside pool redundancy monitor

configure router nat outside pool redundancy monitor

Description

This command configures the monitoring route based on which the NAT multi-chassis switchover is triggered. Monitoring route of a NAT pool on the local node must match the export route of a corresponding NAT pool on the peering node. Presence of the monitoring route in the routing table is an indication that the peering NAT pool is active (since it is advertising its export route). The disappearance of the monitoring route from the routing table is an indication that the peering pool has failed and consequently the nodal switchover is triggered, the local pool becomes active and its export route is consequently advertised. The export route can be advertised only from:

• The active lead pool.

• Active pool for which fate-sharing is disabled.

Default

no monitor

Parameters

ip-prefix/length

Specifies the IP prefix and length.

Values

ip-prefix/length:	ip-prefix	a.b.c.d
	ip-prefix-length	0 to 32

Platforms

7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>service>vprn>bgp>group>neighbor monitor)

[Tree] (config>router>bgp>group>neighbor monitor)

[Tree] (config>router>bgp monitor)

[Tree] (config>router>bgp>group monitor)

[Tree] (config>service>vprn>bgp>group monitor)

Full Context

configure service vprn bgp group neighbor monitor

configure router bgp group neighbor monitor

configure router bgp monitor

configure router bgp group monitor

configure service vprn bgp group monitor

Description

Commands in this context configure monitor parameters.

The no form of this command disables BGP BMP monitoring.

Platforms

All

Context

[Tree] (config>app-assure>group>ip-id-asst>pdns monitor)

Full Context

configure application-assurance group ip-identification-assist passive-dns monitor

Description

This command configures the router to collect IP addresses by passively monitoring DNS traffic. The router uses the collected IP addresses to build its internal database.

The no form of this command disables passive DNS monitoring.

Default

monitor

Platforms

7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>port monitor-agg-egress-queue-stats)

Full Context

configure port monitor-agg-egress-queue-stats

Description

This command enables the monitoring of aggregate egress queue statistics on the port. All queues on the port are monitored, including SAP egress, network egress, subscriber egress, and egress queue group queues, as well as system queues that can be used, for example, to send port-related protocol packets (LACP, EFM, and so on). The aggregate in-profile, out-of-profile, and total statistics are provided for both forwarded and dropped packets and octets.

Monitoring of aggregate statistics is supported on PXC sub-ports but not on a PXC physical port. It is also not supported on satellite ports.

The no form of this command disables aggregate egress queue statistics monitoring on the specified port.

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS

Context

[Tree] (config>router>mpls>lsp-template>auto-bandwidth monitor-bandwidth)

[Tree] (config>router>mpls>lsp>auto-bandwidth monitor-bandwidth)

Full Context

configure router mpls lsp-template auto-bandwidth monitor-bandwidth

configure router mpls lsp auto-bandwidth monitor-bandwidth

Description

This command enables the collection and display of auto-bandwidth measurements, but prevents any automatic bandwidth adjustments from taking place.

The no form of this command disables the collection and display of auto-bandwidth measurements.

Platforms

All

Context

[Tree] (config>service>vprn>sub-if>grp-if>srrp monitor-oper-group)

[Tree] (config>service>ies>sub-if>grp-if>srrp monitor-oper-group)

Full Context

configure service vprn subscriber-interface group-interface srrp monitor-oper-group

configure service ies subscriber-interface group-interface srrp monitor-oper-group

Description

This command will configure the association between the SRRP instance in a Fate Sharing Group and the operational-group that contains messaging SAPs. A state transition of a messaging SAP within an operational-group will trigger calculation of the priority for all SRRP instances that are associated with that operational-group.

The no form of this command reverts to the default.

Parameters

name

Specifies the name of the operational-group, up to 32 characters, that is tracking operational state of SRRP messaging SAPs

priority-step

Specifies the priority step for which the priority of an SRRP instance is changed. If a messaging SAP within an operational-group transition to a non-UP state, the priority is decreased by the step value. If the messaging SAP within the operational-group transition into the UP state, the priority of the SRRP instance is increased by the step value.

Values

1 to 10

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>lag monitor-oper-group)

Full Context

configure lag monitor-oper-group

Description

This command, supported on access LAG only, specifies the operational group to monitor. The state of the operational group affects the state of this LAG. When the operational group is inactive, the state of the LAG goes down and the LAG uses the configured lag>standby-signaling mechanism (lacp or power-off) to signal the CE that the LAG is not available.

Default

no monitor-oper-group

Parameters

name

Specifies the name of the oper-group, up to 32 characters.

Platforms

All

Context

[Tree] (config>service>vpls>sap monitor-oper-group)

[Tree] (config>service>vpls>bgp>pw-template-binding monitor-oper-group)

[Tree] (config>service>vpls>site monitor-oper-group)

[Tree] (config>service>vpls>spoke-sdp monitor-oper-group)

Full Context

configure service vpls sap monitor-oper-group

configure service vpls bgp pw-template-binding monitor-oper-group

configure service vpls site monitor-oper-group

configure service vpls spoke-sdp monitor-oper-group

Description

This command specifies the operational group to be monitored by the object under which it is configured. The oper-group name must be already configured under the config>service context before its name is referenced in this command.

The no form of this command removes the association.

Default

no monitor-oper-group

Parameters

group-name

Specifies a character string of maximum 32 ASCII characters identifying the group instance.

Platforms

All

Context

[Tree] (config>service>epipe>sap monitor-oper-group)

[Tree] (config>service>epipe>spoke-sdp monitor-oper-group)

Full Context

configure service epipe sap monitor-oper-group

configure service epipe spoke-sdp monitor-oper-group

Description

This command specifies the operational group to be monitored by the object under which it is configured. The oper-group name must be already configured under the config>service context before its name is referenced in this command.

The no form of this command removes the association.

Parameters

group-name

Specifies an oper group name.

Platforms

All

Context

[Tree] (config>service>epipe>pw-port monitor-oper-group)

Full Context

configure service epipe pw-port monitor-oper-group

Description

This command configures the monitoring operational group name, up to 32 characters in length, associated with this PW-port entry.

Parameters

group-name

Specifies an operational group to monitor.

Platforms

All

Context

[Tree] (config>service>ies>if monitor-oper-group)

Full Context

configure service ies interface monitor-oper-group

Description

This command specifies the operational group to be monitored by the object under which it is configured. The oper-group name must be already configured under the config>service context before its name is referenced in this command.

The no form of this command removes the association from the configuration.

Default

no monitor-oper-group

Parameters

name

Specifies a character string of maximum 32 ASCII characters identifying the group instance.

Platforms

All

Context

[Tree] (config>service>vprn>if monitor-oper-group)

Full Context

configure service vprn interface monitor-oper-group

Description

This command specifies the operational group to be monitored by the object under which it is configured. The oper-group name must be already configured under the config>service context before its name is referenced in this command.

The no form of this command removes the association from the configuration.

Default

no monitor-oper-group

Parameters

name

Specifies a character string, up to 32 ASCII characters, identifying the group instance.

Platforms

All

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.

Values

1 to 4294967295

Platforms

All

Context

[Tree] (config>isa>nat-group>inter-chassis-redundancy monitor-oper-group)

Full Context

configure isa nat-group inter-chassis-redundancy monitor-oper-group

Description

This command enables monitoring of the objects, such as SAPs, BFD sessions, or VRRP sessions for the purpose of adjusting the overall health of the node in a redundant inter- chassis NAT system. A state change of the objects in the oper-group influences the health of a NAT node in a redundant configuration.

The no form of this command reverts to the default.

Default

no monitor-oper-group

Parameters

name

Specifies the name of the operational group that is being monitored, up to 32 characters.

drop

A state change of an object in the oper-group influences the overall health of the system in the context of NAT inter-chassis redundancy. For example, a transition into a non-operational (down) state of an object within the monitored oper-group triggers a decrease of the overall health of the node for the amount specified by the health-drop value.

Values

1 to 255

Platforms

7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>service>vprn>subscriber-mgmt>up-resiliency monitor-oper-group)

[Tree] (config>service>ies>subscriber-mgmt>up-resiliency monitor-oper-group)

Full Context

configure service vprn subscriber-mgmt up-resiliency monitor-oper-group

configure service ies subscriber-mgmt up-resiliency monitor-oper-group

Description

This command defines parameters to derive the service health based on monitored operational groups. The BNG-UP sends the health value to the MAG-c. The MAG-c uses the value to determine the need for a BNG-UP status change (active or standby).

The no form of the command removes the configuration.

Parameters

name

Specifies the operational group name, up to 32 characters.

drop

Specifies the drop in the health value for every operational group member failure. Every failure of an operational group member decreases the base health value to a possible minimum of 0.

Values

1 to 100

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>service>vpls>sap>pfcp>up-resiliency monitor-oper-group)

Full Context

configure service vpls sap pfcp up-resiliency monitor-oper-group

Description

This command defines parameters to derive the service health based on monitored operational groups. The BNG-UP sends the health value to the BNG CPF. The BNG CPF uses the value to determine the need for a BNG-UP status change (active or standby).

If the configured groups are not the same for all capture SAPs sharing the same underlying port or LAG, the configuration of a Layer 2 access ID alias is required, or else the system chooses arbitrarily one set of configured groups.

The no form of the command removes the configuration.

Parameters

name

Specifies the operational group name, up to 32 characters.

drop

Specifies the drop in the health value for every operational group member failure. Every failure of an operational group member decreases the base health value to a possible minimum of 0.

Values

1 to 100

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

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.

Values

1 to 4294967295

Platforms

All

Context

[Tree] (config>service>sdp>binding>pw-port monitor-oper-group)

Full Context

configure service sdp binding pw-port monitor-oper-group

Description

This command specifies the operational group to be monitored by the object under which it is configured. The oper-group name must be already configured under the config>service context before its name is referenced in this command.

The no form of the command removes the association from the configuration.

Default

no monitor-oper-group

Parameters

name

Specifies a character string of maximum 32 ASCII characters identifying the group instance.

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS

Context

[Tree] (config>port monitor-oper-group)

Full Context

configure port monitor-oper-group

Description

This command configures the operational group to monitor the operational group state. The state of the operational group affects the state of this port. When the operational group is inactive, the state of the port goes down and powers off the port to signal the CE that the connected port is not available.

Default

no monitor-oper-group

Parameters

group-name

Specifies operational group name to monitor, up to 32 characters.

Platforms

All

Context

[Tree] (config>service>vpls>sap>eth-cfm>mep monitor-oper-group)

[Tree] (config>service>vprn>if>sap>eth-cfm>mep monitor-oper-group)

[Tree] (config>service>epipe>sap>eth-cfm>mep monitor-oper-group)

[Tree] (config>service>ies>if>sap>eth-cfm>mep monitor-oper-group)

Full Context

configure service vpls sap eth-cfm mep monitor-oper-group

configure service vprn interface sap eth-cfm mep monitor-oper-group

configure service epipe sap eth-cfm mep monitor-oper-group

configure service ies interface sap eth-cfm mep monitor-oper-group

Description

This command configures the operational group that operationally affects the state of the SAP based on the state of the operational group. When the monitoring function detects an operationally down state for the operational group, the SAP is set to operationally down and any CFM defects present on the MEP are cleared. The MEP enters a pseudo down state and does not try to transmit CFM packets, and it is not expecting to receive CFM packets. When the monitoring function detects an operationally up state for the operational group, the CFM reason code that brought the SAP operationally down is removed. Assuming no other conditions prevent this, the SAP transitions to operationally up and the MEP is initialized.

This command is applicable to MEPs with a direction of down (configure service sap eth-cfm mep direction down) and a configure eth-cfm domain association ccm-interval of 1 second or higher.

The no form of this command removes the operational group.

Default

no monitor-oper-group

Parameters

name

Specifies the operational group name, up to 32 characters.

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS

Context

[Tree] (config>port>network>egress>pool monitor-pool-depth)

[Tree] (config>card>fp>ingress>network>pool monitor-pool-depth)

[Tree] (config>port>access>ingress>pool monitor-pool-depth)

[Tree] (config>port>access>egress>pool monitor-pool-depth)

Full Context

configure port network egress pool monitor-pool-depth

configure card fp ingress network pool monitor-pool-depth

configure port access ingress pool monitor-pool-depth

configure port access egress pool monitor-pool-depth

Description

Commands in this context configure alarm thresholds for pool buffer statistics.

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS

Context

[Tree] (config>isa>nat-group>inter-chassis-redundancy monitor-port)

Full Context

configure isa nat-group inter-chassis-redundancy monitor-port

Description

This command enables monitoring of the ports to adjust the overall health of the node in a redundant inter-chassis NAT system. A state change of a monitored port influences the health of a NAT node in a redundant configuration.

The no form of this command reverts to the default.

Default

no monitor-port

Parameters

port-id

Specifies the port being monitored.

Values

slot/mda/port

drop

A state change of an object in the oper-group influences the overall health of the system in the context of NAT inter-chassis redundancy. For example, a transition into a non-operational (down) state of an object within the monitored oper-group triggers a decrease of the overall health of the node for the amount specified by the health-drop value.

Values

1 to 255

Platforms

7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>system>ptp>ptsf monitor-ptsf-unusable)

Full Context

configure system ptp ptsf monitor-ptsf-unusable

Description

Commands in this context configure the monitoring of neighbor clocks for the Packet Timing Signal Fail (PTSF) unusable state (condition) when the profile is set to g8275dot1-2014.

When enabled, the local clock monitors the noise level of PTP event messages exchanged between external neighbor PTP ports and the local clock. If there is too much noise and the expectation is these event message would not allow the clock to meet its output performance requirements, that neighbor port is considered unusable. This relates to declaring the PTSF-unusable state as defined in the profile.

Once a neighbor port is declared unusable, its Announce messages are excluded from the BTCA and the port cannot be selected as the parent clock.

The unusable condition can be cleared using the following command:

clear system ptp port port-id neighbor mac-address ptsf-unusable

When disabled, PTP clears the PTSF-unusable state from all neighbor PTP ports.

Deleting or disabling the local PTP port clears the PTSF-unusable state from all neighbor PTP ports that are accessed through the local PTP port.

Disabling the monitor-ptsf-unusable function of the PTP clock clears the PTSF-unusable state from all neighbor PTP ports.

In addition, if no PTP messages have been received from a neighbor for 15 minutes, the neighbor information is purged, which also clears the PTSF-unusable state.

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS

Context

[Tree] (config>port>eth>access>egr>qgrp>qover>q monitor-queue-depth)

[Tree] (config>service>epipe>sap>egress>queue-override>queue monitor-queue-depth)

[Tree] (config>port>ethernet>network>egress-port-queue-overrides>queue monitor-queue-depth)

[Tree] (config>port>ethernet>network>egr>qgrp>qover>q monitor-queue-depth)

[Tree] (config>service>cpipe>sap>egress>queue-override>queue monitor-queue-depth)

[Tree] (config>service>vprn>if>sap>egress>queue-override>queue monitor-queue-depth)

[Tree] (config>service>ies>if>sap>egress>queue-override>queue monitor-queue-depth)

[Tree] (config>service>ipipe>sap>egress>queue-override>queue monitor-queue-depth)

[Tree] (config>service>vpls>sap>egress>queue-override>queue monitor-queue-depth)

Full Context

configure port ethernet access egress queue-group queue-overrides queue monitor-queue-depth

configure service epipe sap egress queue-override queue monitor-queue-depth

configure port ethernet network egress-port-queue-overrides queue monitor-queue-depth

configure port ethernet network egress queue-group queue-overrides queue monitor-queue-depth

configure service cpipe sap egress queue-override queue monitor-queue-depth

configure service vprn interface sap egress queue-override queue monitor-queue-depth

configure service ies interface sap egress queue-override queue monitor-queue-depth

configure service ipipe sap egress queue-override queue monitor-queue-depth

configure service vpls sap egress queue-override queue monitor-queue-depth

Description

This command configures queue depth monitoring for the specified queue.

The no form of this command disables queue depth monitoring for the specified queue.

Parameters

fast-polling

Keyword used to specify that fast queue polling is enabled. Fast queue polling is only supported on FP3- and FP4-based hardware.

percentage

Specifies a percentage, up to two decimal places, of the queue MBS. When the depth of the queue exceeds this percentage, a violation is registered.

Values

00.01 to 99.99

Platforms

All

• configure port ethernet network egress queue-group queue-overrides queue monitor-queue-depth
• configure port ethernet network egress-port-queue-overrides queue monitor-queue-depth
• configure service ipipe sap egress queue-override queue monitor-queue-depth
• configure service vpls sap egress queue-override queue monitor-queue-depth
• configure service vprn interface sap egress queue-override queue monitor-queue-depth
• configure port ethernet access egress queue-group queue-overrides queue monitor-queue-depth
• configure service epipe sap egress queue-override queue monitor-queue-depth
• configure service ies interface sap egress queue-override queue monitor-queue-depth

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS

• configure service cpipe sap egress queue-override queue monitor-queue-depth

Context

[Tree] (config>service>vpls>sap>ingress>queue-override>queue monitor-queue-depth)

[Tree] (config>service>ies>if>sap>ingress>queue-override>queue monitor-queue-depth)

[Tree] (config>port>eth>access>ingress>qgrp>qover>q monitor-queue-depth)

[Tree] (config>service>ipipe>sap>ingress>queue-override>queue monitor-queue-depth)

[Tree] (config>service>cpipe>sap>ingress>queue-override>queue monitor-queue-depth)

[Tree] (config>service>vprn>if>sap>ingress>queue-override>queue monitor-queue-depth)

[Tree] (config>service>epipe>sap>ingress>queue-override>queue monitor-queue-depth)

Full Context

configure service vpls sap ingress queue-override queue monitor-queue-depth

configure service ies interface sap ingress queue-override queue monitor-queue-depth

configure port ethernet access ingress queue-group queue-overrides queue monitor-queue-depth

configure service ipipe sap ingress queue-override queue monitor-queue-depth

configure service cpipe sap ingress queue-override queue monitor-queue-depth

configure service vprn interface sap ingress queue-override queue monitor-queue-depth

configure service epipe sap ingress queue-override queue monitor-queue-depth

Description

This command enters the context for queue depth monitoring for the specified queue. The fast-polling option is not supported at ingress.

The no form of this command disables queue depth monitoring.

Platforms

All

• configure service epipe sap ingress queue-override queue monitor-queue-depth
• configure service ipipe sap ingress queue-override queue monitor-queue-depth
• configure service ies interface sap ingress queue-override queue monitor-queue-depth
• configure service vpls sap ingress queue-override queue monitor-queue-depth
• configure port ethernet access ingress queue-group queue-overrides queue monitor-queue-depth
• configure service vprn interface sap ingress queue-override queue monitor-queue-depth

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS

• configure service cpipe sap ingress queue-override queue monitor-queue-depth

Context

[Tree] (config>system>ptp>port monitor-receiver)

[Tree] (config>service>vprn>ptp>peer monitor-receiver)

[Tree] (config>system>ptp>peer monitor-receiver)

Full Context

configure system ptp port monitor-receiver

configure service vprn ptp peer monitor-receiver

configure system ptp peer monitor-receiver

Description

This command enables this PTP peer as a monitorReceiver for PTP. When not in TimeReceiver mode, the PTP port runs a time-recovery engine for PTP monitoring. This object is supported only when the PTP profile is set to G.8275.1 or G.8275.2.

The no form of this command disables this PTP peer as a monitorReceiver.

Default

no monitor-receiver

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS

Context

[Tree] (config>system>ptp>port monitor-sender)

Full Context

configure system ptp port monitor-sender

Description

This command enables this PTP port as a monitorSender for PTP. When not in TimeTransmitter mode, the PTP port sends Announce, Sync, and Delay_Resp messages with the alternateMasterFlag set to TRUE for PTP monitoring at the remote clock. This object is supported only when the PTP profile is set to G.8275.1 or G.8275.2.

The no form of this command disables the PTP port as a monitorSender.

Default

no monitor-sender

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS

Context

[Tree] (config>qos>port-scheduler-policy>group monitor-threshold)

[Tree] (config>qos>port-scheduler-policy monitor-threshold)

Full Context

configure qos port-scheduler-policy group monitor-threshold

configure qos port-scheduler-policy monitor-threshold

Description

This command defines the congestion monitoring threshold for the desired monitoring entity under the port-scheduler for per aggregate port-scheduler rate, per individual level, and per group that is aggregating multiple levels.

The congestion threshold is specified in percentages of the configured PIR rate for the entity for which congestion monitoring is desired. For example, if the configured PIR rate for level 1 is 100,000 kb/s, and the monitoring threshold is set to 90%, then an event where the offered rate is >90,000 kb/s will be recorded. This event is shown as part of the cumulative count of congestion threshold exceeds since the last clearing of the counters.

The no form of this command removes the congestion monitoring threshold.

Default

no monitor-threshold

Parameters

percent

Specifies the percent of the configured rate. If the offered rate exceeds the configured threshold, a counter monitoring the threshold will be increased.

Values

0 to 100

Platforms

All

Context

[Tree] (config>qos>hw-agg-shap-sched-plcy monitor-threshold)

Full Context

configure qos hw-agg-shaper-scheduler-policy monitor-threshold

Description

This command configures the egress scheduler monitor threshold for the hardware aggregate shaper scheduler policy. The value is expressed as a percentage of the scheduler rate, which is considered as a limit for determining congestion.

The no form of this command removes the congestion monitoring threshold.

Default

no monitor-threshold

Parameters

percent

Specifies the percent of the configured rate.

Values

0 to 100

Platforms

7750 SR-1, 7750 SR-s

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.

Values

1 to 12 (maximum 12 month-numbers)

month-name

Specifies a month by name.

Values

january, february, march, april, may, june, july, august, september, october, november, december (maximum 12 month names)

all

Specifies all months.

Platforms

All

Context

[Tree] (environment more)

Full Context

environment more

Description

This command enables per-screen CLI output, meaning that the output is displayed on a screen-by- screen basis. The terminal screen length can be modified with the terminal command.

The following prompt appears at the end of each screen of paginated output:

Press any key to continue (Q to quit)

The no form of the command displays the output all at once. If the output length is longer than one screen, the entire output will be displayed, which may scroll the screen.

Default

more

Platforms

All

Context

[Tree] (config>system>management-interface>cli>md-cli>environment more)

Full Context

configure system management-interface cli md-cli environment more

Description

This command configures pagination of the output text.

The no form of this command reverts to the default value.

Default

more

Platforms

All

Context

[Tree] (config>test-oam>build-packet>header>ipv4 more-fragments)

[Tree] (debug>oam>build-packet>packet>field-override>header>ipv4 more-fragments)

Full Context

configure test-oam build-packet header ipv4 more-fragments

debug oam build-packet packet field-override header ipv4 more-fragments

Description

This command defines if the MF flag should be set in the associated IPv4 header.

The no form of this command reverts to the default value.

Default

more-fragments 0

Parameters

more-fragments

Specifies an MF flag for an IPv4 packet header to be launched by the OAM find-egress tool. A value of 1 means there are more fragments to be sent.

Values

0, 1

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS

Context

[Tree] (config>system>login-control motd)

Full Context

configure system login-control motd

Description

This command creates the message of the day displayed after a successful console login. Only one message can be configured.

The no form of this command removes the message.

Default

no motd

Parameters

url url-prefix: source-url

When the message of the day is present as a text file, provide both url-prefix and the source-url of the file containing the message of the day. The URL prefix can be local or remote.

text motd-text-string

Specifies the text of the message of the day. The motd-text-string must be enclosed in double quotes. Multiple text strings are not appended to one another.

Some special characters can be used to format the message text. The \n character can be used to create multi-line messages. A \n in the message moves to the beginning of the next line by sending ASCII/UTF-8 chars 0xA (LF) and 0xD (CR) to the client terminal. An \r in the message sends the ASCII/UTF-8 char 0xD (CR) to the client terminal.

Platforms

All

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.

Values

local-url	[cflash-id/][file-path] up to 200 characters, including cflash-id directory length up to 99 each
remote-url	[{ftp:// | tftp:// | http:// | https://}login:pswd@remote-locn/][file-path]
	up to 247 characters
	directory length up to 99 characters each
remote-locn	[hostname | ipv4-address | [ipv6-address]]
ipv4-address	a.b.c.d
ipv6-address	x:x:x:x:x:x:x:x[-interface]
	x:x:x:x:x:x:d.d.d.d[-interface]
	x - [0 to FFFF]H
	d - [0 to 255]D
	interface - up to 32 characters, for link local addresses 255
cflash-id	cf1:, cf1-A:, cf1-B:, cf2:, cf2-A:, cf2-B:, cf3:, cf3-A:, cf3-B:

new-file-url

Specifies the new destination to place the old-file-url.

Values

local-url	[cflash-id/][file-path] up to 200 characters, including cflash-id directory length up to 99 each
remote-url	[{ftp:// | tftp://}login:pswd@remote-locn/][file-path]
	up to 247 characters
	directory length up to 99 characters each
remote-locn	[hostname | ipv4-address | [ipv6-address]]
ipv4-address	a.b.c.d
ipv6-address	x:x:x:x:x:x:x:x[-interface]
	x:x:x:x:x:x:d.d.d.d[-interface]
	x - [0 to FFFF]H
	d - [0 to 255]D
	interface - up to 32 characters, for link local addresses 255
cflash-id	cf1:, cf1-A:, cf1-B:, cf2:, cf2-A:, cf2-B:, cf3:, cf3-A:, cf3-B:

force

Forces an immediate move of the specified file(s).

The file move force command moves the specified file(s) without displaying a user prompt message. This command also automatically accepts HTTP redirects unless overridden by the no-redirect parameter.

profile

Specifies the TLS client profile configured under config>system>security>tls>client-tls-profile to use.

proxy-url

Specifies the URL of an HTTP proxy. For example, http://proxy.mydomain.com:8000. This URL must be an HTTP URL and not an HTTPS URL.

no-redirect

Specifies to automatically refuse any HTTP redirects without prompting the user.

Platforms

All

Context

[Tree] (config>service>template>vpls-template>mac-move move-frequency)

[Tree] (config>service>vpls>mac-move move-frequency)

Full Context

configure service template vpls-template mac-move move-frequency

configure service vpls mac-move move-frequency

Description

This command indicates the maximum rate at which MACs can be 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.

Values

1 to 10

Platforms

All

Context

[Tree] (config>router>bgp mp-bgp-keep)

Full Context

configure router bgp mp-bgp-keep

Description

As a result of enabling this command, route refresh messages are no longer needed, or issued when VPN route policy changes are made; RIB-IN will retain all MP-BGP routes.

The no form of this command is used to disable this feature.

Default

no mp-bgp-keep

Platforms

All

Context

[Tree] (config>router>ldp mp-mbb-time)

Full Context

configure router ldp mp-mbb-time

Description

This command configures the maximum time a P2MP transit/bud node must wait before switching over to the new path if the new node does not send MBB TLV to inform of the availability of data plane.

The no form of this command reverts to the default value.

Default

no mp-mbb-time (which equals a value of 3 seconds)

Parameters

interval

Specifies the MP MBB time, in seconds.

Values

0 to 10

Platforms

All

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.

Values

1, 2

endpoint-name

Specifies the endpoint name for Epipe services, up to 32 characters.

Platforms

All

Context

[Tree] (config>service>vprn>bgp-ipvpn mpls)

Full Context

configure service vprn bgp-ipvpn mpls

Description

Commands in this context configure the BGP IPVPN parameters.

Platforms

All

Context

[Tree] (config>router mpls)

Full Context

configure router mpls

Description

Commands in this context configure MPLS parameters. MPLS is not enabled by default and must be explicitly enabled (no shutdown).

The no form of this command deletes this MPLS protocol instance and removes all configuration parameters for this MPLS instance.

You must remove all SDP bindings and use the shutdown command to administratively disable the MPLS instance before deleting it.

Platforms

All

Context

[Tree] (config>router>rib-api mpls)

Full Context

configure router rib-api mpls

Description

Commands in this context configure MPLS parameters related to the RIB-API gRPC service.

Platforms

All

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.

Values

0 to 4294967295

lsp-id lsp-id

Specifies the LSP ID.

Values

1 to 65535

Platforms

All

Context

[Tree] (debug>oam>build-packet>packet>field-override>header mpls)

[Tree] (config>test-oam>build-packet>header mpls)

Full Context

debug oam build-packet packet field-override header mpls

configure test-oam build-packet header mpls

Description

This command causes the associated header to be defined as an MPLS label header template and enables the context to define the MPLS parameters.

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS

Context

[Tree] (config>oam-pm>session mpls)

Full Context

configure oam-pm session mpls

Description

Commands in this context configure MPLS-specific source and destination, LSP type and tunnel information, the priority, and the MPLS DM test configuration on the launch point.

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS

Context

[Tree] (config>cflowd>collector>export-filter>family mpls)

Full Context

configure cflowd collector export-filter family mpls

Description

This command filters MPLS flow data from being sent to the associated collector.

The no form of this command removes the filter, allowing MPLS flow data to be sent to the associated collector.

Default

no mpls

Platforms

All

Context

[Tree] (config>system>ip mpls)

Full Context

configure system ip mpls

Description

Commands in this context configure system-wide MPLS parameters.

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS

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

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS

Context

[Tree] (config>test-oam mpls-dm)

Full Context

configure test-oam mpls-dm

Description

Commands in this context configure global MPLS delay measurement parameters.

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS

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:

1. 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.

2. 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:

1. 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.

2. 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:

   1. 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.

   2. 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.

   3. 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.

3. 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:

1. 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.

2. 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.

3. 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.

4. Full validation of an LDP FEC tunneled over an RSVP LSP using LSP trace.

To properly check a target FEC which is stitched to another FEC (stitching FEC) of the same or a different type, or which is tunneled over another FEC (tunneling FEC), it is necessary for the responding nodes to provide details about the FEC manipulation back to the sender node. This is achieved via the use of the new FEC stack change sub-TLV in the Downstream Detailed Mapping TLV (DDMAP) defined in RFC 6424.

When the user configures the use of the DDMAP TLV on a trace for an LSP that does not undergo stitching or tunneling operation in the network, the procedures at the sender and responder nodes are the same as in the case of the DSMAP TLV.

This feature however introduces changes to the target FEC stack validation procedures at the sender and responder nodes in the case of LSP stitching and LSP hierarchy. These changes pertain to the processing of the new FEC stack change sub-TLV in the new DDMAP TLV and the new return code of value 15 Label switched with FEC change.

The no form of this command reverts to the default behavior of using the DSMAP TLV in a LSP trace packet and LDP tree trace packet.

Default

mpls-echo-request-downstream-map dsmap

Parameters

dsmap

Specifies that the DSMAP TLV should be used in all LSP trace packets and LDP tree trace packets originating on the node.

ddmap

Specifies that the DDMAP TLV should be used in all LSP trace packets and LDP tree trace packets originating on the node.

Platforms

All

Output

The following output is an example of mpls-echo-request-downstream-map information.

A          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#

Context

[Tree] (config>service>vprn>bgp-ipvpn>mpls>auto-bind-tunnel>resolution-filter mpls-fwd-policy)

[Tree] (config>service>epipe>bgp-evpn>mpls>auto-bind-tunnel>resolution-filter mpls-fwd-policy)

[Tree] (config>service>vpls>bgp-evpn>mpls>auto-bind-tunnel>resolution-filter mpls-fwd-policy)

[Tree] (config>service>vprn>bgp-evpn>mpls>auto-bind-tunnel>resolution-filter mpls-fwd-policy)

Full Context

configure service vprn bgp-ipvpn mpls auto-bind-tunnel resolution-filter mpls-fwd-policy

configure service epipe bgp-evpn mpls auto-bind-tunnel resolution-filter mpls-fwd-policy

configure service vpls bgp-evpn mpls auto-bind-tunnel resolution-filter mpls-fwd-policy

configure service vprn bgp-evpn mpls auto-bind-tunnel resolution-filter mpls-fwd-policy

Description

This command selects the MPLS forwarding policy type.

The mpls-fwd-policy value instructs BGP to use the MPLS forwarding policy to determine the address of the BGP next hop.

The no form of this command removes the selected the MPLS forwarding policy type.

Default

no mpls-fwd-policy

Platforms

All

Context

[Tree] (config>router>static-route-entry>indirect>tunnel-next-hop>resolution-filter mpls-fwd-policy)

Full Context

configure router static-route-entry indirect tunnel-next-hop resolution-filter mpls-fwd-policy

Description

This command enables the use of the MPLS forwarding policy to resolve the indirect next hops of statically-configured routes.

Default

no mpls-fwd-policy

Platforms

All

Context

[Tree] (config>router>bgp>next-hop-resolution>shortcut-tunn>family>resolution-filter mpls-fwd-policy)

[Tree] (config>router>bgp>next-hop-resolution>labeled-routes>transport-tunnel>family>resolution-filter mpls-fwd-policy)

Full Context

configure router bgp next-hop-resolution shortcut-tunnel family resolution-filter mpls-fwd-policy

configure router bgp next-hop-resolution labeled-routes transport-tunnel family resolution-filter mpls-fwd-policy

Description

This command selects MPLS forwarding policy to be used for next-hop resolution.

Platforms

All

Context

[Tree] (config>service>vprn>auto-bind-tunnel>res-filter mpls-fwd-policy)

Full Context

configure service vprn auto-bind-tunnel resolution-filter mpls-fwd-policy

Description

Platforms

All

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.

Values

0 to 1048575

Platforms

All

Context

[Tree] (config>router mpls-labels)

Full Context

configure router mpls-labels

Description

This command creates a context for the configuration of global parameters related to MPLS labels.

Platforms

All

Context

[Tree] (config>test-oam mpls-time-stamp-format)

Full Context

configure test-oam mpls-time-stamp-format

Description

This command configures the format of the timestamp used by for lsp-ping, lsp-trace, p2mp-lsp-ping and p2mp-lsp-trace, vccv-ping, vccv-trace, and lsp-trace.

If rfc4379 is selected, then the timestamp is in seconds and microseconds since 1900, otherwise it is in seconds and microseconds since 1970.

Changing this system-wide setting does not affect tests that are currently in progress, but SAAs starts to use the new timestamp when they are restarted. When an SR OS receives an echo request, it replies with the locally configured timestamp format, and does not try to match the timestamp format of the incoming echo request message.

Default

mpls-time-stamp-format unix

Parameters

rfc4379

Specifies the RFC 4379 (obsoleted by RFC 8029) time stamp format. The timestamp's seconds field holds the integral number of seconds since 1-Jan-1900 00:00:00 UTC. The timestamp's microseconds field contains a microseconds value in the range 0 to 999999. This setting is used to inter-operate with network elements which are fully compliant with RFC 4379, Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures, (such as an SR OS system with the same setting, or any other RFC 4379 compliant router).

unix

Specifies the Unix time stamp format. The time stamps seconds field holds a Unix time, the integral number of seconds since 1-Jan-1970 00:00:00 UTC. The time stamps microseconds field contains a microseconds value in the range 0 to 999999. This setting is used to inter-operate with network elements which send and expect a 1970-based timestamp in MPLS Echo Request/Reply PDUs (such as an SR OS system with the same setting, or an SR OS system running software earlier than R8.0 R4).

Platforms

All

Context

[Tree] (config>router>mpls mpls-tp)

Full Context

configure router mpls mpls-tp

Description

Generic MPLS-TP parameters and MPLS-TP transit paths are configured under this context. If a user configures no mpls, normally the entire mpls configuration is deleted. However, in the case of mpls-tp, a check is made that there is no other mpls-tp configuration (e.g., services or LSPs using mpls-tp on the node). The mpls-tp context cannot be deleted if MPLS-TP LSPs or SDPs exist on the system.

A shutdown of mpls-tp will bring down all MPLS-TP LSPs on the system.

Default

no mpls-tp

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS

Context

[Tree] (config>router>mpls>interface mpls-tp-mep)

Full Context

configure router mpls interface mpls-tp-mep

Description

Commands in this context configure a section layer MEP for MPLS-TP on an MPLS interface.

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS

Context

[Tree] (config>oam-pm>session>mpls>lsp mpls-tp-static)

Full Context

configure oam-pm session mpls lsp mpls-tp-static

Description

Commands in this context configure an MPLS TP LSP and its attributes to be tested.

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS

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.

Values

multicast group address (ipv4, ipv6)

ip-address

Debugs information associated with the specified PIM MRIB.

Values

source address (ipv4, ipv6)

detail

Debugs detailed MRIB information.

Platforms

All

Context

[Tree] (mrinfo)

Full Context

mrinfo

Description

This command is used to print relevant multicast information from the target multicast router. Information displayed includes adjacency information, protocol, metrics, thresholds, and flags from the target multicast route.

Parameters

ip-address

Specifies the IP address of the multicast-capable target router.

Values

ipv4 unicast address (a.b.c.d)

dns-name

Specifies the DNS name (if DNS name resolution is configured), up to 63 characters.

router-instance

Specifies the router name or service ID for the router instance.

Values

router-name: Base

vprn-service-id: 1 to 2147483647

Default

Base

service-name

Specifies the service name, up to 64 characters.

Platforms

All

Output

The following output is an example of mrinfo information. The output fields are described in the following table.

A:dut-f# mrinfo 10.1.1.2

10.1.1.2  [version 3.0,prune,genid,mtrace]:
  10.1.1.2 -> 10.1.1.1 [1/0/pim]
  10.1.1.3 -> 0.0.0.0 [1/0/pim/down/disabled]
  10.1.1.4 -> 0.0.0.0 [1/0/pim/querier/leaf]
  239.200.200.3 -> 239.200.200.5 [1/0/tunnel/pim]... 

Context

[Tree] (config>service>vpls>pbb>bvpls>mld-snooping mrouter-dest)

[Tree] (config>service>vpls>pbb>bvpls>igmp-snooping mrouter-dest)

Full Context

configure service vpls pbb backbone-vpls mld-snooping mrouter-dest

configure service vpls pbb backbone-vpls igmp-snooping mrouter-dest

Description

This command configures the destination B-MAC address name to be used in the related backbone VPLS to reach a specific IGMP or MLD snooping MRouter. The name is associated at system level with the MAC address, using the command config>service>pbb mac-name.

Parameters

mac-name

Specifies the MAC name.

Values

32 chars max

Platforms

All

Context

[Tree] (config>service>vpls>bind>igmp-snooping mrouter-port)

[Tree] (config>service>vpls>sap>igmp-snooping mrouter-port)

[Tree] (config>service>vpls>mesh-sdp>igmp-snooping mrouter-port)

[Tree] (config>service>vpls>spoke-sdp>igmp-snooping mrouter-port)

[Tree] (config>service>vpls>bind>mld-snooping mrouter-port)

[Tree] (config>service>vpls>spoke-sdp>mld-snooping mrouter-port)

Full Context

configure service vpls allow-ip-int-bind igmp-snooping mrouter-port

configure service vpls sap igmp-snooping mrouter-port

configure service vpls mesh-sdp igmp-snooping mrouter-port

configure service vpls spoke-sdp igmp-snooping mrouter-port

configure service vpls allow-ip-int-bind mld-snooping mrouter-port

configure service vpls spoke-sdp mld-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.

If the send-queries command is enabled on this SAP or spoke-SDP, the mrouter-port parameter cannot be set.

When PIM-snooping is enabled within a VPLS service, all IP multicast traffic and PIM messages will be sent to any SAP or SDP binding configured with an IGMP-snooping mrouter port. This occurs even without IGMP-snooping enabled, but is not supported in a BGP-VPLS or M-VPLS service.

The no form of this command reverts to the default.

Default

no mrouter-port

Platforms

All

Context

[Tree] (config>service>vpls>vxlan>igmp-snooping mrouter-port)

Full Context

configure service vpls vxlan igmp-snooping mrouter-port

Description

This command enables all VXLAN binds to be mrouter ports, indicating that a multicast router is attached behind each VXLAN binding. Configuring these objects as an mrouter-port has two effects. Firstly, all multicast traffic received on another object is copied to each VXLAN binding. Secondly, IGMP reports generated by the system as a result of a router joining or leaving a multicast group is sent to all VXLAN bindings. When PIM snooping for IPv4 is enabled within a VPLS service, all IP multicast traffic and PIM for IPv4 messages are sent to all VXLAN bindings configured with an igmp-snooping mrouter-port. This occurs even without igmp-snooping enabled.

Default

no mrouter-port

Platforms

All

Context

[Tree] (config>service>vpls>vxlan>mld-snooping mrouter-port)

Full Context

configure service vpls vxlan mld-snooping mrouter-port

Description

This command enables all VXLAN binds to be mrouter ports, indicating that a multicast router is attached behind each VXLAN binding. Configuring these objects as an mrouter-port has two effects. Firstly, all multicast traffic received on another object is copied to each VXLAN binding. Secondly, MLD reports generated by the system as a result of a router joining or leaving a multicast group is sent to all VXLAN bindings.

Default

no mrouter-port

Platforms

All

Context

[Tree] (config>service>vpls>pbb>bvpls>sdp>mld-snooping mrouter-port)

[Tree] (config>service>vpls>pbb>bvpls>sdp>igmp-snooping mrouter-port)

[Tree] (config>service>vpls>pbb>bvpls>sap>igmp-snooping mrouter-port)

[Tree] (config>service>vpls>pbb>bvpls>sap>mld-snooping mrouter-port)

Full Context

configure service vpls pbb backbone-vpls sdp mld-snooping mrouter-port

configure service vpls pbb backbone-vpls sdp igmp-snooping mrouter-port

configure service vpls pbb backbone-vpls sap igmp-snooping mrouter-port

configure service vpls pbb backbone-vpls sap mld-snooping mrouter-port

Description

This command specifies whether a multicast router is attached behind this SAP or spoke-SDP.

Configuring a SAP or spoke-SDP as an mrouter-port will have a double effect. Firstly, all multicast traffic received on another SAP or spoke-SDP will be copied to this SAP or spoke-SDP. Secondly, IGMP or MLD reports generated by the system as a result of someone joining or leaving a multicast group, will be sent to this SAP or SDP.

If two multicast routers exist in the local area network, one of them will become the active querier. The other multicast router (non-querier) stops sending IGMP or MLD queries, but it should still receive reports to keep its multicast trees up to date. To support this, the mrouter-port should be enabled on all SAPs or spoke-SDPs connecting to a multicast router.

The IGMP version to be used for the reports (v1, v2 or v3) or MLD version (v1 or v2) can only be determined after an initial query has been received. Until such time no reports are sent on the SAP, even if mrouter-port is enabled.

If the send-queries command is enabled on this SAP or spoke-SDP, the mrouter-port parameter cannot be set.

Default

no mrouter-port

Platforms

All

Context

[Tree] (config>service>vpls>mesh-sdp mrp)

[Tree] (config>service>vpls>sap mrp)

[Tree] (config>service>vpls mrp)

[Tree] (config>service>vpls>spoke-sdp mrp)

Full Context

configure service vpls mesh-sdp mrp

configure service vpls sap mrp

configure service vpls mrp

configure service vpls spoke-sdp mrp

Description

This command configures Multiple Registration Protocol (MRP) parameters. MRP is valid only under B-VPLS.

Platforms

All

Context

[Tree] (config>service mrp)

Full Context

configure service mrp

Description

This command configures a Multi-service Route Processor (MRP).

Platforms

All

Context

[Tree] (debug>service>id mrp)

Full Context

debug service id mrp

Description

This command enables and configures MRP debugging.

Platforms

All

Context

[Tree] (config>service>mrp mrp-policy)

Full Context

configure service mrp mrp-policy

Description

Commands in this context configure an MRP policy. The mrp-policy specifies either a forward or a drop action for the Group B-MAC attributes associated with the ISIDs specified in the match criteria. The mrp-policy can be applied to multiple BVPLS services as long as the scope of the policy is template.

Any changes made to the existing policy, using any of the sub-commands, will be applied immediately to all services where this policy is applied. For this reason, when many changes are required on a mrp-policy, Nokia recommends that the policy be copied to a work area. That work-in-progress policy can be modified until complete and then written over the original mrp-policy. Use the config mrp-policy copy command to maintain policies in this manner.

The no form of this command deletes the mrp-policy. An MRP policy cannot be deleted until it is removed from all the SAPs or SDPs where it is applied.

Default

no mrp-policy

Parameters

policy-name

Specifies the redirect policy name. Allowed values are any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes.

create

This keyword is required when first creating the configuration context. When the context is created, it is possible to navigate into the context without the create keyword.

Platforms

All

Context

[Tree] (config>service>vpls>sap>mrp mrp-policy)

[Tree] (config>service>vpls>spoke-sdp>mrp mrp-policy)

[Tree] (config>service>vpls>mesh-sdp>mrp mrp-policy)