m Commands – Part II

Context

[Tree] (config>test-oam>twamp>server>prefix max-sess-prefix)

Full Context

configure test-oam twamp server prefix max-sess-prefix

Description

This command configures the maximum number of concurrent TWAMP-Test sessions by clients with an IP address in a specific prefix. A new test session (described by a Request-TW-Session message) is rejected if accepting it would cause either the limit defined by this command or the server limit (max-sess-server) to be exceeded.

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

Default

max-sess-prefix 32

Parameters

count

Specifies the maximum number of concurrent test sessions.

Values

0 to 128

Default

32

Platforms

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

Context

[Tree] (config>test-oam>twamp>server max-sess-server)

Full Context

configure test-oam twamp server max-sess-server

Description

This command configures the maximum number of concurrent TWAMP-Test sessions across all allowed clients. A new test session (described by a Request-TW-Session message) is rejected if accepting it would cause either the limit defined by this command or a prefix limit (max-sess-prefix) to be exceeded.

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

Default

max-sess-server 32

Parameters

count

Specifies the maximum number of concurrent test sessions.

Values

0 to 128

Default

32

Platforms

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

Context

[Tree] (config>mcast-mgmt>mcast-info-plcy>video-policy>video-if max-sessions)

Full Context

configure mcast-management multicast-info-policy video-policy video-interface max-sessions

Description

This command configures the per-client maximum number of sessions.

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

Default

max-sessions 256

Parameters

sessions

Specifies the per-client maximum number of sessions.

Values

1 to 65536

Default

256

Platforms

7450 ESS, 7750 SR, 7750 SR-s

Context

[Tree] (config>router>bgp>group>dynamic-neighbor>interface max-sessions)

[Tree] (config>service>vprn>bgp>group>dynamic-neighbor>interface max-sessions)

Full Context

configure router bgp group dynamic-neighbor interface max-sessions

configure service vprn bgp group dynamic-neighbor interface max-sessions

Description

This command configures the maximum number of dynamic sessions that are allowed to be set up on the interface as a result of accepting sessions from link-local addresses or initiating sessions by receiving IPv6 router advertisements.

Default

max-sessions 1

Parameters

number

Specifies the maximum number of sessions.

Values

1 to 255

Platforms

All

Context

[Tree] (config>subscr-mgmt>ppp-policy max-sessions-per-cid)

Full Context

configure subscriber-mgmt ppp-policy max-sessions-per-cid

Description

This command configures the maximum number of PPPoE sessions with the same Agent Circuit ID that can be active on the same SAP or MSAP. The limit is enforced in the discovery phase, prior to PAP or CHAP authentication and is based on the Agent Circuit ID sub-option that is present in the vendor-specific PPPoE access loop identification tag added in PADI and PADR messages by a PPPoE intermediate agent.

When the optional allow-sessions-without-cid keyword is specified, PPPoE sessions without an Agent Circuit ID can be established. The configured sessions limit does not apply to these sessions.

By default, there is no limit for the number of PPPoE sessions with the same Agent Circuit ID that are active on the same SAP or MSAP. Sessions without Agent Circuit ID can be established.

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

Default

no max-sessions-per-cid

Parameters

sessions

Specifies the maximum number of sessions with the same circuit ID that can be active on the same SAP or MSAP.

Values

1 to 8190

allow-sessions-without-cid

Specifies to enable support for PPPoE sessions without a circuit ID while a max-sessions-per-cid limit is configured on a SAP or MSAP.

Platforms

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

Context

[Tree] (config>subscr-mgmt>loc-user-db>ppp>host>plcy-parms max-sessions-per-mac)

Full Context

configure subscriber-mgmt local-user-db ppp host ppp-policy-parameters max-sessions-per-mac

Description

This command configures the maximum number of PPPoE sessions created per MAC address. This number overrides the value defined within the PPPoE policy.

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

Default

no max-sessions-per-mac

Parameters

maximum

Specifies the maximum PPP sessions that can be opened for the given MAC address.

Values

1 to 8191

Platforms

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

Context

[Tree] (config>subscr-mgmt>ppp-policy max-sessions-per-mac)

Full Context

configure subscriber-mgmt ppp-policy max-sessions-per-mac

Description

This command sets the maximum PPP sessions that can be opened for a given MAC address.

To enable IPv4 address allocation using the internal DHCPv4 client for multiple PPPoE sessions on a single SAP and having the same MAC address and circuit-ID, the optional CLI parameter allow-same-circuit-id-for-dhcp should be added. The SR OS local DHCP server detects the additional vendor-specific options inserted by the internal DHCPv4 client and use an extended unique key for lease allocation.

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

Parameters

sessions

Specifies the maximum PPP sessions that can be opened for the given MAC address.

Values

1 to 8191

allow-same-circuit-id-for-dhcp

Sets the support for IPv4 address allocation using the internal DHCPv4 client for multiple PPPoE sessions on a single SAP that have the same MAC address and circuit ID.

Platforms

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

Context

[Tree] (config>lag>bfd>family max-setup-time)

Full Context

configure lag bfd family max-setup-time

Description

This command specifies the maximum amount of time the router will forward traffic over a link that has transitioned from Standby to Active, before the micro-BFD session must be fully established (Up state).

The no form of this command returns the timer value to the default (0) which indicates that forwarding will not start until the BFD session is established.

Default

max-setup-time infinite

Parameters

up-interval

Specifies the amount of time, in milliseconds.

Values

-1 to 60000

infinite

Specifies no end time to forward traffic.

Platforms

All

Context

[Tree] (config>open-flow>of-switch>flowtable max-size)

Full Context

configure open-flow of-switch flowtable max-size

Description

This command configures the size for the specified flow table. The OpenFlow switch instance must be shutdown to modify this parameter.

The no form of this command restores the default size.

Default

max-size 1000

Parameters

size

Specifies the maximum size limit for the flow table. The size limit is a total for both IPv4 and IPv6.

Values

1 to 262144

Default

1000

Platforms

VSR

Context

[Tree] (config>service>vprn>mld>interface max-sources)

[Tree] (config>service>vprn>igmp>if max-sources)

[Tree] (config>service>vprn>igmp>grp-if max-sources)

Full Context

configure service vprn mld interface max-sources

configure service vprn igmp interface max-sources

configure service vprn igmp group-interface max-sources

Description

This command specifies the maximum number of sources for which IGMP can have local receiver information based on received IGMP reports on this interface. When this configuration is changed dynamically to a value lower than currently accepted number of sources, the sources that are already accepted are not deleted. Only new sources will not be allowed.

Parameters

sources

Specifies the maximum number of sources for this interface.

Values

1 to 1000

Platforms

All

• configure service vprn igmp interface max-sources
• configure service vprn mld interface max-sources

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

• configure service vprn igmp group-interface max-sources

Context

[Tree] (config>router>igmp>group-interface max-sources)

[Tree] (config>router>igmp>if max-sources)

Full Context

configure router igmp group-interface max-sources

configure router igmp interface max-sources

Description

This command configures the maximum number of group sources for this group-interface.

Parameters

value

Specifies the maximum number of group sources.

Values

1 to 1000

Platforms

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

• configure router igmp group-interface max-sources

All

• configure router igmp interface max-sources

Context

[Tree] (config>router>mld>group-interface max-sources)

[Tree] (config>router>mld>if max-sources)

Full Context

configure router mld group-interface max-sources

configure router mld interface max-sources

Description

This command configures the maximum number of group sources for this interface.

The no form of this command reverts to the default.

Default

no max-sources

Parameters

grp-source

Specifies the maximum number of group sources for this interface.

Platforms

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

• configure router mld group-interface max-sources

All

• configure router mld interface max-sources

Context

[Tree] (config>router>mpls>lsp-template max-sr-labels)

[Tree] (config>router>mpls>lsp max-sr-labels)

Full Context

configure router mpls lsp-template max-sr-labels

configure router mpls lsp max-sr-labels

Description

This command configures the maximum number of labels which the ingress LER can push for a given SR-TE LSP.

This command is used to allow room to insert additional transport, service, and other labels when packets are forwarded in a given context.

The max-sr-labels label-stack-size value should reflect the desired maximum label stack of the primary path of the SR-TE LSP.

The value in additional-frr-labels labels should reflect additional labels inserted by remote LFA for the backup next-hop of the SR-TE LSP.

The sum of both label values represents the worst case transport of SR label stack size for this SR-TE LSP and is populated by MPLS in the TTM such that services and shortcut applications can check it to decide if a service can be bound or a route can be resolved to this SR-TE LSP.

The maximum label stack supported by the router is always signaled by PCC in the PCEP Open object as part of the as SR-PCE-CAPABILITY TLV. It is referred to as the Maximum Stack Depth (MSD).

In addition, the per-LSP value for the max-sr-labels option, if configured, is signaled by PCC to PCE in the Segment-ID (SID) Depth value in a METRIC object for both a PCE computed LSP and a PCE controlled LSP. PCE will compute and provide the full explicit path with TE-links specified. If there is no path with the number of hops lower than the MSD value, or the Segment-ID (SID) Depth value if signaled, a reply with no path will be returned to PCC.

For a PCC controlled LSP, if the label stack returned by the TE-DB’s hop-to-label translation exceeds the per LSP maximum SR label stack size, the LSP is brought down.

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

Default

max-sr-labels 6 additional-frr-labels 1

Parameters

label-stack-size

Specifies the label stack size.

Values

1 to 11

additional-frr-labels labels

Specifies the addition FRR labels.

Values

0 to 3

Platforms

All

Context

[Tree] (config>router>pcep>pcc max-srte-pce-init-lsps)

Full Context

configure router pcep pcc max-srte-pce-init-lsps

Description

This command configures the maximum number of PCE-initiated SR-TE LSPs that can be created by the router.

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

Default

max-srte-pce-init-lsps 8191

Parameters

max-number

Specifies the maximum number of SR-TE PCE-initiated LSPs.

Values

0 to 8191

Platforms

All

Context

[Tree] (config>router>mpls>lsp>egr-stats max-stats)

[Tree] (config>router>mpls>ingr-stats>p2p-template-lsp max-stats)

[Tree] (config>router>mpls>ingr-stats>p2mp-template-lsp max-stats)

[Tree] (config>router>mpls>lsp-template>egr-stats max-stats)

Full Context

configure router mpls lsp egr-stats max-stats

configure router mpls ingress-statistics p2p-template-lsp max-stats

configure router mpls ingress-statistics p2mp-template-lsp max-stats

configure router mpls lsp-template egr-stats max-stats

Description

This command enables accounting and statistical data collection. When applying accounting policies the data, by default, is collected in the appropriate records and written to the designated billing file.

When the no max-stats command is issued the statistics are still accumulated by the forwarding engine. However, the CPU will not obtain the results and write them to the billing file. If a subsequent max-stats command is issued then the counters written to the billing file include all the traffic while the no max-stats command was in effect.

Default

max-stats

Platforms

All

Context

[Tree] (config>router>policy-options>damping max-suppress)

Full Context

configure router policy-options damping max-suppress

Description

This command configures the maximum suppression parameter for the route damping profile.

This value indicates the maximum time, expressed in minutes, that a route can remain suppressed.

The no form of this command removes the maximum suppression parameter from the damping profile.

Default

no max-suppress

Parameters

minutes

Specifies the maximum suppression time, in minutes, expressed as a decimal integer.

Values

1 to 720

Platforms

All

Context

[Tree] (config>log>acct-policy>cr>aa>aa-to-sub-cntr max-throughput-octet-count)

[Tree] (config>log>acct-policy>cr>aa>aa-from-sub-cntr max-throughput-octet-count)

Full Context

configure log accounting-policy custom-record aa-specific to-aa-sub-counters max-throughput-octet-count

configure log accounting-policy custom-record aa-specific from-aa-sub-counters max-throughput-octet-count

Description

This command includes the maximum throughput as measured in the octet count.

The no form of this command excludes the maximum throughput octet count.

Platforms

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

Context

[Tree] (config>log>acct-policy>cr>aa>aa-to-sub-cntr max-throughput-packet-count)

[Tree] (config>log>acct-policy>cr>aa>aa-from-sub-cntr max-throughput-packet-count)

Full Context

configure log accounting-policy custom-record aa-specific to-aa-sub-counters max-throughput-packet-count

configure log accounting-policy custom-record aa-specific from-aa-sub-counters max-throughput-packet-count

Description

This command includes the maximum throughput as measured in the packet count.

The no form of this command excludes the maximum throughput packet count.

Platforms

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

Context

[Tree] (config>app-assure>group>statistics>aa-sub max-throughput-stats)

Full Context

configure application-assurance group statistics aa-sub max-throughput-stats

Description

This command enables the collection of max-throughput statistics.

The no form of this command disables the collection.

Default

no max-throughput-stats

Platforms

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

Context

[Tree] (config>log>acct-policy>cr>aa>aa-to-sub-cntr max-throughput-timestamp)

[Tree] (config>log>acct-policy>cr>aa>aa-from-sub-cntr max-throughput-timestamp)

Full Context

configure log accounting-policy custom-record aa-specific to-aa-sub-counters max-throughput-timestamp

configure log accounting-policy custom-record aa-specific from-aa-sub-counters max-throughput-timestamp

Description

This command includes the timestamp of the maximum throughput. This command only applies to the 7750 SR.

The no form of this command excludes the timestamp.

Platforms

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

Context

[Tree] (config>service>vprn>l2tp>tunnel-selection-blacklist max-time)

[Tree] (config>router>l2tp>tunnel-selection-blacklist max-time)

Full Context

configure service vprn l2tp tunnel-selection-blacklist max-time

configure router l2tp tunnel-selection-blacklist max-time

Description

This command configures time for which an entity (peer or a tunnel) are kept in the denylist.

The no form of this command reverts to the default.

Default

max-time 5

Parameters

minutes

Specifies the maximum time a tunnel or peer may remain in the denylist.

Values

1 to 60

Platforms

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

Context

[Tree] (config>system>telemetry>notification-bundling max-time-granularity)

Full Context

configure system telemetry notification-bundling max-time-granularity

Description

This command sets the maximum time interval during which telemetry notifications are bundled. All bundled notifications will have the same timestamp, which is the timestamp of the bundle.

The no form of this command returns the time granularity to the default value.

Default

max-time-granularity 100

Parameters

time

Specifies the maximum time interval during which telemetry notifications are bundled, in milliseconds.

Values

1 to 1000

Platforms

All

Context

[Tree] (config>test-oam>ldp-treetrace>path-discovery max-ttl)

Full Context

configure test-oam ldp-treetrace path-discovery max-ttl

Description

This command configures the maximum number of hops the path discovery traces in the path of each FEC to be discovered.

The no form of this command resets the time out to its default value.

Default

no max-ttl

Parameters

ttl-value

Specifies the maximum label time-to-live value for an LSP trace request during the tree discovery.

Values

1 to 255

Platforms

All

Context

[Tree] (config>mcast-mgmt>mcast-rprt-dest max-tx-delay)

Full Context

configure mcast-management mcast-reporting-dest max-tx-delay

Description

This command specifies the time interval before the packet starts transmitting towards the destination. When an IGMP event is encoded and ready to be transported, a buffer for the packet is allocated (if not already existent). The events are written into this buffer. Along with the initial buffer creation, a timer is started. The trigger for the transmission of the packet is either the TX buffer being filled up to 1400 B, or the timer expiry, whichever comes first.

The no form of this command reverts to the default.

Parameters

deci-seconds

Specifies the maximum delay after which any cached reports are flushed to the reporting destination.

Values

0 to 100

Platforms

All

Context

[Tree] (config>service>nat>syslog>syslog-export-policy max-tx-delay)

Full Context

configure service nat syslog syslog-export-policy max-tx-delay

Description

This command enables aggregation of flow log messages within a syslog frame. It introduces a delay during which logs are collected in each BB-ISA so they can be sent in a single syslog message to conserve system resources and network bandwidth.

When aggregation is enabled, generation of a syslog frame carrying multiple flow logs is triggered by one of the two events (whichever occurs first):

• Expiry of the max-tx-delay timer

• Exceeding MTU size

The no form of the command reverts to the default.

Default

max-tx-delay 3

Parameters

deciseconds

Specifies the maximum time a syslog message is delayed in the system's output buffer.

Values

1 to 100

Platforms

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

Context

[Tree] (config>service>vpls>bgp-vpls max-ve-id)

Full Context

configure service vpls bgp-vpls max-ve-id

Description

This command configures the allowed range for the VE-id value: locally configured and received in a NLRI. Configuration of a VE-id higher than the value specified in this command is not allowed.

Also upon reception of a higher VE-id in an NLRI imported in this VPLS instance (RT is the configured import RT) the following action must be taken:

• a trap must be generated informing the operator of the mismatch.

• NLRI must be dropped

• no service labels are to be installed for this VE-id

• no new NLRI must be generated if a new offset is required for VE-id.

The no form of this command sets the max-ve-id to un-configured. The BGP VPLS status should be administratively down for "no max-ve-id” to be used.

The max-ve-id value can be changed without shutting down bgp-vpls if the newly provisioned value does not conflict with the already configured local VE-ID. If the value of the local-VE-ID is higher than the new max-ve-id value the command is rejected. The operator needs to decrease first the VE-ID before running the command.

The actions taken for other max-ve-id values are as follows:

• max-ve-id value higher than all VE-IDs (local and received) is allowed and there are no effects.

• max-ve-id higher than the local VE-ID but smaller than the remote VE-IDs:

  • Provisioning is allowed

  • A warning message will be generated stating that "Higher VE-ID values were received in the BGP VPLS context. Related pseudowires will be removed.”

  • The pseudowires associated with the higher VE-IDs will be removed locally.

  • This is a situation that should be corrected by the operator as the pseudowire may be down just at the local PE, consuming unnecessarily core bandwidth. The higher VE-IDs should be removed or lowered.

If the max-ve-id has increased a BGP route refresh is sent to the VPLS community to get the routes which might have been rejected earlier due to max-ve-id check. A max-ve-id value needs to be provisioned for BGP VPLS to be in "no shutdown” state.

Default

no max-ve-id

Parameters

value

Specifies the allowed range of [1-value] for the VE-id. The configured value must be bigger than the existing VE-ids

Values

1 to 65535

Platforms

All

Context

[Tree] (config>service>vprn>bgp>convergence>family max-wait-to-advertise)

Full Context

configure service vprn bgp convergence family max-wait-to-advertise

Description

This command configures the maximum amount of time that BGP waits until it starts advertising IPv4-unicast or IPv6-unicast routes to its BGP peers. For IPv4-unicast routes, seconds is measured from the time when the first peer that supports the IPv4-unicast address family comes up. For IPv6-unicast routes seconds is measured from the time when the first peer that negotiates the IPv6-unicast address family comes up.

The time limit configured by this command should allow sufficient time for all important peers to re-establish their sessions with the restarting router and advertise their complete set of IPv4-unicast or IPv6-unicast routes (followed by the applicable End of RIB marker).

The no form of this command implements the default value, which is three times the value of the min-wait-to-advertise time limit.

Default

no max-wait-to-advertise

Parameters

seconds

Specifies the maximum amount of time, in seconds, that BGP waits until IPv4-unicast or IPv6-unicast routes are advertised to peers.

Values

0 to 3600

Platforms

All

Context

[Tree] (config>router>bgp>convergence>family max-wait-to-advertise)

Full Context

configure router bgp convergence family max-wait-to-advertise

Description

This command configures the maximum amount of time that BGP waits until it starts advertising IPv4-unicast or IPv6-unicast routes to its BGP peers. For IPv4-unicast routes, the time limit value is measured from the time when the first peer that supports the IPv4-unicast address family comes up. For IPv6-unicast routes the time limit value is measured from the time when the first peer that negotiates the IPv6-unicast address family comes up.

The time limit configured by this command should allow sufficient time for all important peers to re-establish their sessions with the restarting router and advertise their complete set of IPv4-unicast or IPv6-unicast routes (followed by the applicable End of RIB marker).

The no form of this command implements the default value, which is three times the value of the min-wait-to-advertise time-limit.

Default

no max-wait-to-advertise

Parameters

seconds

Specifies the maximum amount of time, in seconds, that BGP waits until IPv4-unicast or IPv6-unicast routes are advertised to peers.

Values

0 to 3600

Platforms

All

Context

[Tree] (config>system>security>pki maximum-cert-chain-depth)

Full Context

configure system security pki maximum-cert-chain-depth

Description

This command defines the maximum depth of certificate chain verification. This number is applied system wide.

The no form of this command reverts to the default.

Default

maximum-cert-chain-depth 7

Parameters

level

Specifies the maximum depth level of certificate chain verification, range from 1 to 7. the certificate under verification is not counted in. for example, if this parameter is set to 1, then the certificate under verification must be directly signed by trust anchor CA.

Values

1 to 7

Platforms

All

Context

[Tree] (config>router>dhcp6>server>pool>failover maximum-client-lead-time)

[Tree] (config>service>vprn>dhcp6>server>pool>failover maximum-client-lead-time)

[Tree] (config>router>dhcp>server>pool>failover maximum-client-lead-time)

[Tree] (config>service>vprn>dhcp>server>failover maximum-client-lead-time)

[Tree] (config>service>vprn>dhcp>server>pool>failover maximum-client-lead-time)

[Tree] (config>router>dhcp6>server>failover maximum-client-lead-time)

[Tree] (config>service>vprn>dhcp6>server>failover maximum-client-lead-time)

[Tree] (config>router>dhcp>server>failover maximum-client-lead-time)

Full Context

configure router dhcp6 server pool failover maximum-client-lead-time

configure service vprn dhcp6 local-dhcp-server pool failover maximum-client-lead-time

configure router dhcp server pool failover maximum-client-lead-time

configure service vprn dhcp local-dhcp-server failover maximum-client-lead-time

configure service vprn dhcp local-dhcp-server pool failover maximum-client-lead-time

configure router dhcp6 local-dhcp-server failover maximum-client-lead-time

configure service vprn dhcp6 local-dhcp-server failover maximum-client-lead-time

configure router dhcp local-dhcp-server failover maximum-client-lead-time

Description

The command configures the maximum time that a DHCP server can extend client’s lease time beyond the lease time currently known by the DHCP partner node. In dual-homed environment, the initial lease time for all DHCP clients is by default restricted to MCLT. Consecutive DHCP renews can extend the lease time beyond the MCLT.

The maximum client lead time (MCLT) is a safeguard against IP address/prefix duplication in cases of a lease synchronization failure when local-remote failover model is deployed.

Once the intercommunication link failure between the redundant DHCP servers is detected, the DHCP IP address range configured as remote will not be allowed to start delegating new leases until the MCLT + partner-down-delay intervals expire. This is to ensure that the new lease that was delegated from the local IP address-range/prefix on one node but was never synchronized due to the intercommunication link failure, will expire before the same IP address/prefix is allocated from the remote IP address-range/prefix on the other node.

However, the already existing (and synchronized) lease times can be renewed from the remote IP address range at any time, regardless of the state of the intercommunication link (operational or failed).

Lease synchronization failure can be caused either by a node failure, or a failure of the link over which the DHCP leases are synchronized (intercommunication link). Synchronization failure detection can take up to 3 seconds.

During the failure, the DHCP lease time for the new clients is restricted to MCLT while for the existing clients the lease time will over time (by consecutive DHCP renews) be gradually reduced to the MCLT.

The no form of this command reverts to the default.

Default

maximum-client-lead-time min 10

Parameters

maximum-client-lead-time

Specifies the maximum client lead time.

Values

hrs hours	1 to 23
min minutes	1 to 59
sec seconds	1 to 59

Platforms

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

Context

[Tree] (config>qos>sap-egress>queue maximum-data-transmission)

Full Context

configure qos sap-egress queue maximum-data-transmission

Description

This command sets the maximum amount of data transmitted at a single scheduling opportunity. If the frame to be scheduled is longer than the configured amount of data, the entire frame is still transmitted. This command is applicable only to FP4 and FP5 chipsets.

The no form of this command reverts to the default.

Default

maximum-data-transmission 8192 for FP4

maximum-data-transmission 20480 for FP5

Parameters

bytes

Specifies the maximum amount of data transmitted.

Values

512 to 32768

Platforms

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

Context

[Tree] (config>service>vprn>dhcp>server>pool>subnet maximum-declined)

[Tree] (config>router>dhcp>server>pool>subnet maximum-declined)

Full Context

configure service vprn dhcp local-dhcp-server pool subnet maximum-declined

configure router dhcp local-dhcp-server pool subnet maximum-declined

Description

This command configures the maximum number of declined addresses allowed.

The no form of the reverts to the default.

Default

maximum-declined 64

Parameters

maximum-declined

Specifies the maximum number of declined addresses allowed.

Values

0 to 4294967295

Platforms

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

Context

[Tree] (config>service>vprn maximum-ipv6-routes)

Full Context

configure service vprn maximum-ipv6-routes

Description

This command specifies the maximum number of remote IPv6 routes that can be held within a VPN routing/ forwarding (VRF) context. The local, host, static and aggregate routes are not counted.

The VPRN service ID must be in a shutdown state in order to modify maximum-routes command parameters.

If the log-only parameter is not specified and the maximum-routes value is set below the existing number of routes in a VRF, then the offending RIP peer (if applicable) is brought down (but the VPRN instance remains up). BGP peering will remain up but the exceeding BGP routes will not be added to the VRF.

The maximum route threshold can dynamically change to increase the number of supported routes even when the maximum has already been reached. Protocols will resubmit their routes which were initially rejected.

The no form of this command disables any limit on the number of routes within a VRF context. The threshold will not be raised. Issue the no form of this command only when the VPRN instance is shutdown.

Default

0 or disabled

Parameters

number

Specifies an integer that specifies the maximum number of routes to be held in a VRF context.

Values

1 to 2147483647

log-only

Specifies that if the maximum limit is reached, only log the event. log-only does not disable the learning of new routes.

threshold percentage

Specifies the percentage at which a warning log message and SNMP trap should be set. There are two warnings, the first is a mid-level warning at the threshold value set and the second is a high-level warning at level between the maximum number of routes and the mid-level rate ([mid+max] / 2).

Values

0 to 100

Platforms

All

Context

[Tree] (config>router>isis>upa maximum-number-upas)

Full Context

configure router isis prefix-unreachable maximum-number-upas

Description

This command configures a limit for the number of UPAs the router can advertise. If overrun, a system log is generated and additional UPAs are not advertised.

The no form of this command reverts to the default.

Default

32

Parameters

maximum-number-upas

Specifies the maximum number of UPAs that the router can advertise.

Values

1 to 8192

Platforms

All

Context

[Tree] (config>test-oam>icmp>ipv6 maximum-original-datagram)

Full Context

configure test-oam icmp ipv6 maximum-original-datagram

Description

This command enables the original datagram field of the ICMPv6 error message to be a maximum of 1232 bytes.

The no form of this command may result in an original datagram field of the ICMPv6 error message smaller than 1232 bytes be built smaller.

Default

no maximum-original-datagram

Platforms

All

Context

[Tree] (config>service>vpls>provider-tunnel>selective maximum-p2mp-spmsi)

[Tree] (config>service>vprn>mvpn>pt>selective maximum-p2mp-spmsi)

Full Context

configure service vpls provider-tunnel selective maximum-p2mp-spmsi

configure service vprn mvpn provider-tunnel selective maximum-p2mp-spmsi

Description

This command specifies the maximum number of S-PMSI tunnels for the MVPN or EVPN service. When the limit is reached, no more RSVP P2MP S-PMSI or LDP P2MP S-PMSI are created and traffic over the data threshold stays on I-PMSI.

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

Default

maximum-p2mp-spmsi 10

Parameters

range

Specifies the maximum number of RSVP P2MP or LDP P2MP S-PMSI tunnel for the MVPN or VPLS.

Values

1 to 4000

Default

10

Platforms

All

Context

[Tree] (config>router>gtm>provider-tunnel>selective maximum-p2mp-spmsi)

Full Context

configure router gtm provider-tunnel selective maximum-p2mp-spmsi

Description

This command specifies the maximum number of RSVP P2MP or LDP P2MP S-PMSI tunnels for the GTM. When the limit is reached, no more RSVP P2MP S-PMSI or LDP P2MP S-P MSI tunnels are created and traffic over the data-threshold will stay on I-PMSI.

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

Default

maximum-p2mp-spmsi 10

Parameters

range

Specifies the maximum number of RSVP P2MP or LDP P2MP S-PMSI tunnels for the GTM.

Values

1 to 4000

Default

10

Platforms

All

Context

[Tree] (config>service>vprn>bgp>multi-path maximum-paths)

Full Context

configure service vprn bgp multi-path maximum-paths

Description

This command sets ECMP multi-path parameters that apply to all address families for that BGP multi-path. For some address families it is possible to override these settings on a per address family basis.

When multi-path is enabled, traffic to the destination is load-shared across a set of paths (BGP routes) that the BGP decision process considers equal to the best path. The actual distribution of traffic over the multiple paths may be equal or unequal (that is, based on weights derived from the Link Bandwidth Extended Community).

To qualify as a multi-path, a non-best route must meet the following criteria (some criteria are controlled by this command):

• The multi-path route must be the same type of route as the best path (same AFI/SAFI and, in some cases, same next-hop resolution method).

• The multi-path route must be tied with the best path for all criteria of greater significance than next-hop cost, except for criteria that are configured to be ignored.

• If the best path selection reaches the next-hop cost comparison, the multi-path route must have the same next-hop cost as the best route unless the unequal-cost option is configured.

• The multi-path route must not have the same BGP next-hop as the best path or any other multi-path route.

• The multi-path route must not cause the ECMP limit of the routing instance to be exceeded (configured using the ecmp command with a value in the range 1 to 64).

• The multi-path route must not cause the applicable max-paths limit to be exceeded. If the best path is an EBGP learned route and the ebgp option is used, the ebgp-max-paths limit overrides the max-paths limit. If the best path is an IBGP-learned route and the ibgp option is used, the ibgp-max-paths limit overrides the max-paths limit. All path limits are configurable up to a maximum of 64. Multi-path is effectively disabled if a value is set to 1.

• The multi-path route must have the same neighbor AS in its AS path as the best path if the restrict same-neighbor-as option is configured. By default, any path with the same AS path length as the best path (regardless of neighbor AS) is eligible for multi-path.

• The route must have the same AS path as the best path if the restrict exact-as-path option is configured. By default, any path with the same AS path length as the best path (regardless of the actual AS numbers) is eligible for multi-path.

The no form of this command disables BGP multi-path.

Default

no maximum-paths

Parameters

max-paths

Specifies the maximum number of multipaths per prefix/NLRI if ebgp-max-paths or ibgp-max-paths does not apply.

Values

1 to 64

egp-max-paths

Specifies the maximum number of multipaths per prefix or NLRI when the best path is an EBGP learned route.

Values

1 to 64

ibgp-max-paths

Specifies the maximum number of multipaths per prefix or NLRI when the best path is an IBGP learned route.

Values

1 to 64

restrict same-neighbor-as

Specifies that the non-best path must have the same neighbor AS in its AS path as the best path.

restrict exact-as-path-as

Specifies that the non-best path must have the same AS path as the best path.

unequal-cost

Instructs BGP to ignore differences in the next-hop cost only when determining eligible multipaths.

Platforms

All

Context

[Tree] (config>router>bgp>multi-path maximum-paths)

Full Context

configure router bgp multi-path maximum-paths

Description

This command sets ECMP multipath parameters that apply to all address families for that BGP multipath. For some address families it is possible to override these settings on a per address family basis.

When multipath is enabled, traffic to the destination is load-shared across a set of paths (BGP routes) that the BGP decision process considers equal to the best path. The actual distribution of traffic over the multiple paths may be equal or unequal (that is, based on weights derived from the Link Bandwidth Extended Community).

The no form of this command disables BGP multipath.

Default

no maximum-paths

Parameters

max-paths

Specifies the maximum number of multipaths per prefix/NLRI if ebgp-max-paths or ibgp-max-paths does not apply.

Values

1 to 64

ebgp-max-paths

Specifies the maximum number of multipaths per prefix or NLRI when the best path is an EBGP learned route.

Values

1 to 64

ibgp-max-paths

Specifies the maximum number of multipaths per prefix or NLRI when the best path is an IBGP learned route.

Values

1 to 64

restrict same-neighbor-as

Specifies that the non-best path must have the same neighbor AS in its AS path as the best path.

restrict exact-as-path

Specifies that the non-best path must have the same AS path as the best path.

unequal-cost

Instructs BGP to ignore differences in the next-hop cost only when determining eligible multipaths.

Platforms

All

Context

[Tree] (config>router>ldp>graceful-restart maximum-recovery-time)

Full Context

configure router ldp graceful-restart maximum-recovery-time

Description

This command configures the local maximum recovery time.

The no form of this command returns the default value.

Default

no maximum-recovery-time (which equals a value of 120 seconds)

Parameters

interval

Specifies the length of time in seconds.

Values

15 to 1800

Platforms

All

Context

[Tree] (config>service>vprn maximum-routes)

Full Context

configure service vprn maximum-routes

Description

This command specifies the maximum number of remote routes that can be held within a VPN routing/ forwarding (VRF) context. The local, host, static and aggregate routes are not counted.

The VPRN service ID must be in a shutdown state in order to modify maximum-routes command parameters.

If the log-only parameter is not specified and the maximum-routes value is set below the existing number of routes in a VRF, then the offending RIP peer (if applicable) is brought down (but the VPRN instance remains up). BGP peering will remain up but the exceeding BGP routes will not be added to the VRF.

The maximum route threshold can dynamically change to increase the number of supported routes even when the maximum has already been reached. Protocols will resubmit their routes which were initially rejected.

The no form of this command disables any limit on the number of routes within a VRF context. Issue the no form of this command only when the VPRN instance is shutdown.

Default

0 or disabled — The threshold will not be raised.

Parameters

number

An integer that specifies the maximum number of routes to be held in a VRF context.

Values

1 to 2147483647

log-only

Specifies that if the maximum limit is reached, only log the event. log-only does not disable the learning of new routes.

threshold percentage

The percentage at which a warning log message and SNMP trap should be set. There are two warnings, the first is a mid-level warning at the threshold value set and the second is a high-level warning at level between the maximum number of routes and the mid-level rate ([mid+max] / 2).

Values

0 to 100

Platforms

All

Context

[Tree] (config>router>isis>segm-rtng maximum-sid-depth)

Full Context

configure router isis segment-routing maximum-sid-depth

Description

Commands in this context configure a manual override of the Maximum Segment Depths (MSD) that is announced by the router.

Platforms

All

Context

[Tree] (config>router>ospf>segm-rtng maximum-sid-depth)

Full Context

configure router ospf segment-routing maximum-sid-depth

Description

Commands in this context configure a manual override of the Maximum Segment Depths (MSD) that is announced by the router.

Platforms

All

Context

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

Full Context

debug router mpls event mbb

Description

This command debugs the state of the most recent invocation of the make-before-break (MBB) functionality.

The no form of the command disables the debugging.

Parameters

detail

Displays detailed information about MBB events.

Platforms

All

Context

[Tree] (config>router>mpls mbb-prefer-current-hops)

Full Context

configure router mpls mbb-prefer-current-hops

Description

This command implements a new option in the CSPF path computation during a Make-Before-Break (MBB) procedure of an RSVP LSP.

When MPLS performs an MBB for the primary or secondary path of a P2P LSP, or the S2L path of a P2MP LSP, and the new mbb-prefer-current-hops option is enabled in MPLS context, CSPF will select a path, among equal-cost candidate paths, with the most overlapping links with the current path. Normally, CSPF selects the path randomly.

The procedures of the new MBB CSPF path selection apply to LSP without the least-fill option enabled. If the least-fill rule results in a different path, the LSP path will be moved though. Users can still favor stability over least-fill condition by applying a larger value to the parameter least-fill-min-thd under the MPLS context such that a path will only be moved when the difference of the least-available bandwidth becomes significant enough between the most used links in the equal cost paths. If that difference is not significant enough, CSPF will select the path with the most overlapping links instead of selecting a path randomly.

The procedures when the new mbb-prefer-current-hops option is enabled apply to all MBB types. Thus, it applies to the auto-bandwidth MBB, the configuration change MBB, the soft preemption MBB, the TE graceful shutdown MBB, the delayed retry MBB (for SRLG secondary LSP path), the path change MBB, the timer resignal MBB, and the manual resignal MBB.

During the FRR global revertive MBB, CSPF selects a random link among the ones available between the PLR node and the Merge Point node, including the failed link if it has restored in the meantime. These links cannot be checked for overlap with the current path.

The TE graceful shutdown MBB will still avoid the link or node that is in maintenance and the soft preemption MBB will still avoid the link that is overbooked.

For an inter-area LSP, this feature applies to the subset of the path from the ingress LER to the exit ABR.

The procedures of this feature are not applied to a zero bandwidth CSPP LSP, including an auto-bandwidth CSPF LSP while its operational bandwidth is zero, and to a non-CSPF LSP.

Platforms

All

Context

[Tree] (config>mcast-mgmt>bw-plcy>t2>sec-path>queue mbs)

[Tree] (config>mcast-mgmt>bw-plcy>t2>prim-path>queue mbs)

Full Context

configure mcast-management bandwidth-policy t2-paths secondary-path queue-parameters mbs

configure mcast-management bandwidth-policy t2-paths primary-path queue-parameters mbs

Description

This command configures the override for the default maximum buffer size (MBS) for each individual path’s queue. The queue's MBS threshold defines the point at which all packets destined for the queue are discarded based on queue depth. The defined threshold also provides context for the queues drop-tail parameter.

The mbs percent-of-pool parameter is defined as a percentage of the total pool size. The system allows the sum of all MBS values to equal more than 100%, allowing for oversubscription of the pool.

For the primary-path and secondary-path queues, the mbs value is applied to a single queue for each path.

The no form of this command is used to restore the path queues default MBS value.

Parameters

percent-of-pool

Specifies the percent of buffers from the total buffer pool space for the number of buffers, expressed as a decimal integer. If 10 MB is the total buffers in the buffer pool, a value of 10 would limit the maximum queue size to 1 MB (10%) of buffer space for the forwarding class queue. If the total size is increased to 20 MB, the existing value of 10 automatically increases the maximum size of the queue to 2 MB.

Values

0 to 100

Default

Primary:	7
Secondary:	40

Platforms

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

Context

[Tree] (config>qos>sap-egress>dynamic-queue mbs)

Full Context

configure qos sap-egress dynamic-queue mbs

Description

This command configures the maximum buffer space (MBS) allowed for the dynamic queue. The MBS is applied to each dynamic queue and is not shared.

Default

no mbs (auto)

Parameters

size

Specifies that the MBS as an integer representing the required size.

Values

0 to 1073741824

default (auto)

bytes

Specifies that the value given for the size variable is interpreted as the queue's MBS value in bytes. The optional bytes and kilobytes keywords are mutually exclusive and are used to explicitly define the size.

kilobytes

Specifies that the value given for the size variable is interpreted as the queue's MBS value in kilobytes. The optional kilobytes and bytes keywords are mutually exclusive and are used to explicitly define the size.

Platforms

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

Context

[Tree] (config>subscr-mgmt>sla-prof>egress>qos>queue mbs)

Full Context

configure subscriber-mgmt sla-profile egress qos queue mbs

Description

This command configures the maximum size for the queue.

The sum of the MBS for all queues on an egress access port can oversubscribe the total amount of buffering available. When congestion occurs and buffers become scarce, access to buffers is controlled by the RED slope a packet is associated with. A queue that has not exceeded its MBS size is not guaranteed that a buffer is available when needed or that the packet’s RED slope will not force the discard of the packet. Setting proper CBS parameters and controlling CBS oversubscription is one major safeguard to queue starvation (when a queue does not receive its fair share of buffers). Another is properly setting the RED slope parameters for the needs of services on this port or channel.

The no form of this command returns the MBS size to the size as configured in the QoS policy.

Parameters

size

This required parameter specifies that the MBS is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional byte and kilobyte keywords are mutually exclusive and are used to explicitly to define the size. By specifying the keyword default sets the MBS to its default value.

Values

0 to 1073741824, default

bytes

Specifies that the value given for size is interpreted as the queue's MBS value in bytes.

kilobytes

Specifies that the value given for size is interpreted as the queue's MBS value in kilobytes.

Platforms

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

Context

[Tree] (config>subscr-mgmt>sla-prof>ingress>qos>queue mbs)

Full Context

configure subscriber-mgmt sla-profile ingress qos queue mbs

Description

The Maximum Burst Size (MBS) command configures the explicit definition of the maximum number of buffers allowed for a specific queue.

The MBS value is used by a queue to determine whether it has exhausted all of its buffers while enqueuing packets. Once the queue has exceeded the number of buffers allowed by MBS, all packets are discarded until packets have been drained from the queue.

The sap-ingress context for mbs provides a mechanism for overriding the default maximum size for the queue.

The sum of the MBS for all queues on an ingress access port can oversubscribe the total amount of buffering available. When congestion occurs and buffers become scarce, access to buffers is controlled by the RED slope a packet is associated with. A queue that has not exceeded its MBS size is not guaranteed that a buffer is available when needed or that the packet’s RED slope does not force the discard of the packet. Setting proper CBS parameters and controlling CBS oversubscription is one major safeguard to queue starvation (when a queue does not receive its fair share of buffers). Another is properly setting the RED slope parameters for the needs of services on this port or channel.

The no form of this command returns the MBS size to the size as configured in the QoS policy.

Parameters

size

This required parameter specifies that the MBS is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional byte and kilobyte keywords are mutually exclusive and are used to explicitly to define the size. By specifying the keyword default sets the MBS to its default value.

Values

0 to 1073741824, default

bytes

Specifies that the value given for size is interpreted as the queue's MBS value is in bytes.

kilobytes

Specifies that the value given for size is interpreted as the queue's MBS value is in kilobytes.

Platforms

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

Context

[Tree] (config>subscr-mgmt>sla-prof>ingress>qos>policer mbs)

[Tree] (config>subscr-mgmt>sla-prof>egress>qos>policer mbs)

Full Context

configure subscriber-mgmt sla-profile ingress qos policer mbs

configure subscriber-mgmt sla-profile egress qos policer mbs

Description

This command configures the MBS for the QoS policer.

The no form of this command returns the MBS to its default value. By default, the MBS is 16 Mbytes when PIR equals max or is greater than or equal to the FP capacity (this overrides an explicit configured MBS value); otherwise, 10 ms volume of traffic for a configured non-zero/non-max PIR capped to 3968 kbytes, with a minimum of 256 bytes.

Parameters

size

This required parameter specifies that the MBS is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional byte and kilobyte keywords are mutually exclusive and are used to explicitly to define the size. By specifying the keyword default sets the MBS to its default value.

Values

0 to 2683435456, default

bytes

Specifies that the value given for size is interpreted as the queue's MBS value in bytes.

kilobytes

Specifies that the value given for size is interpreted as the queue's MBS value in kilobytes.

Platforms

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

Context

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

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

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

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

Full Context

configure service ies interface sap ingress queue-override queue mbs

configure service vprn interface sap egress queue-override queue mbs

configure service ies interface sap egress queue-override queue mbs

configure service vprn interface sap ingress queue-override queue mbs

Description

This command overrides specific attributes of the specified queue’s MBS parameters. The MBS is a mechanism to override the default maximum size for the queue.

The sum of the MBS for all queues on an egress access port can oversubscribe the total amount of buffering available. When congestion occurs and buffers become scarce, access to buffers is controlled by the RED slope a packet is associated with. A queue that has not exceeded its MBS size is not guaranteed that a buffer is available when needed or that the packets RED slope is not forced the discard of the packet. Setting proper CBS parameters and controlling CBS oversubscription is one major safeguard to queue starvation (when a queue does not receive its fair share of buffers). Another is properly setting the RED slope parameters for the needs of services on this port or channel.

If the CBS value is larger than the MBS value, an error will occur, preventing the MBS change.

The no form of this command returns the MBS size assigned to the queue.

Default

mbs default

Parameters

size

This required parameter specifies that the MBS is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional byte and kilobyte keywords are mutually exclusive and are used to explicitly to define the size. By specifying the keyword default sets the MBS to its default value.

Values

0 to 1073741824, default

bytes

Specifies that the value given for size is interpreted as the queue's MBS value in bytes.

kilobytes

Specifies that the value given for size is interpreted as the queue's MBS value in kb/s.

Platforms

All

Context

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

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

Full Context

configure service vprn interface sap egress queue-override queue mbs

configure service vprn interface sap ingress queue-override queue mbs

Description

This command can be used to override specific attributes of the specified queue’s MBS parameters. The MBS value is used by a queue to determine whether it has exhausted all of its buffers while enqueuing packets. Once the queue has exceeded the amount of buffers allowed by MBS, all packets are discarded until packets have been drained from the queue.

The sum of the MBS for all queues on an ingress access port can oversubscribe the total amount of buffering available. When congestion occurs and buffers become scarce, access to buffers is controlled by the RED slope a packet is associated with. A queue that has not exceeded its MBS size is not guaranteed that a buffer will be available when needed or that the packet’s RED slope will not force the discard of the packet. Setting proper CBS parameters and controlling CBS oversubscription is one major safeguard to queue starvation (when a queue does not receive its fair share of buffers). Another is properly setting the RED slope parameters for the needs of services on this port or channel.

If the CBS value is larger than the MBS value, an error will occur, preventing the MBS change.

The no form of this command returns the MBS size assigned to the queue to the value.

Default

mbs default

Parameters

size

The size parameter is required when specifying mbs and is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional bytes and kilobytes keywords are mutually exclusive and are used to explicitly define whether the size represents bytes or kilobytes.

Values

0 to 1073741824

default

bytes

When byte is defined, the value given for size is interpreted as the queue's MBS value given in bytes.

kilobytes

When kilobytes is defined, the value is interpreted as the queue's MBS value given in kilobytes.

default

Keyword that reverts the MBS to its default value.

Platforms

All

Context

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

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

Full Context

configure service vpls sap ingress queue-override queue mbs

configure service vpls sap egress queue-override queue mbs

Description

This command overrides specific attributes of the specified queue’s MBS parameters. The MBS value is used by a queue to determine whether it has exhausted all of its buffers while enqueuing packets. Once the queue has exceeded the amount of buffers allowed by MBS, all packets are discarded until packets have been drained from the queue.

The sum of the MBS for all queues on an ingress access port can oversubscribe the total amount of buffering available. When congestion occurs and buffers become scarce, access to buffers is controlled by the RED slope a packet is associated with. A queue that has not exceeded its MBS is not guaranteed that a buffer will be available when needed or that the packets RED slope will not force the discard of the packet. Setting correct CBS parameters and controlling CBS over-subscription is one major safeguard to queue starvation (when a queue does not receive its fair share of buffers). Another is properly setting the RED slope parameters for the needs of services on this port or channel.

The no form of this command returns the MBS assigned to the queue to the default value.

Default

mbs default

Parameters

size

The size parameter is required when specifying mbs and is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional bytes and kilobytes keywords are mutually exclusive and are used to explicitly define whether the size represents bytes or kilobytes.

Values

0 to 1073741824

default

bytes

When byte is defined, the value given for size is interpreted as the queue's MBS value given in bytes.

kilobytes

When kilobytes is defined, the value is interpreted as the queue's MBS value given in kilobytes.

Platforms

All

Context

[Tree] (config>subscr-mgmt>isa-policer mbs)

Full Context

configure subscriber-mgmt isa-policer mbs

Description

This command specifies the maximum burst-size value of this policer.

The no form of this command reverts to its default.

Default

mbs 0

Parameters

burst-size

The maximum burst-size in kbytes.

Values

0 to 131071

Platforms

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

Context

[Tree] (config>card>fp>ingress>network>qgrp>policer-over>plcr mbs)

[Tree] (config>card>fp>ingress>access>qgrp>policer-over>plcr mbs)

Full Context

configure card fp ingress network queue-group policer-override policer mbs

configure card fp ingress access queue-group policer-override policer mbs

Description

This command configures the policer’s PIR leaky bucket’s violate threshold. The high-prio-only command is applied to the MBS value to derive the bucket’s low priority violate threshold. For ingress, trusted in-profile packets and untrusted high priority packets use the policer’s high priority violate threshold while trusted out-of-profile and untrusted low priority packets use the policer’s low priority violate threshold.

The PIR bucket’s violate threshold represent the maximum burst tolerance allowed by the policer. If the policer’s offered rate is equal to or less than the policer’s defined rate, the PIR bucket depth hovers around the 0 depth with spikes up to the maximum packet size in the offered load. If the offered rate increases beyond the metering rate, the amount of data allowed above the rate is capped by the threshold. The low priority violate threshold provides a smaller burst size for the lower priority traffic associated with the policer. Since all lower priority traffic is discarded at the lower burst tolerance size, the remaining burst tolerance defined by high-prio-only is available for the higher priority traffic.

The policer’s mbs size defined in the QoS policy may be overridden on an sla-profile or SAP where the policy is applied.

The no form of this command reverts the policer to its default MBS size. By default, the MBS is 16 Mbytes when PIR equals max or is greater than or equal to the FP capacity (this overrides an explicit configured MBS value); otherwise, 10 ms volume of traffic for a configured non-zero/non-max PIR capped to 3968 kbytes, with a minimum of 256 bytes.

Parameters

size

The size parameter is required when specifying mbs and is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional bytes and kilobytes keywords are mutually exclusive and are used to explicitly define whether size represents bytes or kilobytes.

Values

0 to 2683435456, default

bytes

When bytes is defined, the value given for size is interpreted as the policer’s MBS value given in bytes.

kilobytes

When kilobytes is defined, the value is interpreted as the policer’s MBS value given in kilobytes.

default

Keyword that reverts the MBS to its default value.

Platforms

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

Context

[Tree] (config>port>ethernet>network>egr>qgrp>qover>q mbs)

[Tree] (config>port>ethernet>access>egr>qgrp>qover>q mbs)

[Tree] (config>port>ethernet>access>ing>qgrp>qover>q mbs)

Full Context

configure port ethernet network egress queue-group queue-overrides queue mbs

configure port ethernet access egress queue-group queue-overrides queue mbs

configure port ethernet access ingress queue-group queue-overrides queue mbs

Description

The Maximum Burst Size (MBS) command specifies the default maximum buffer size for the template queue. The value is given in kilobytes.

The MBS value is used by a queue to determine whether it has exhausted all of its buffers while enqueuing packets. Once the queue has exceeded the amount of buffers allowed by MBS, all packets are discarded until packets have been drained from the queue.

The queue-group or network egress QoS context for mbs provides a mechanism for overriding the default maximum size for the queue.

The sum of the MBS for all queues on an ingress access port can oversubscribe the total amount of buffering available. When congestion occurs and buffers become scarce, access to buffers is controlled by the RED slope a packet is associated with. A queue that has not exceeded its MBS size is not guaranteed that a buffer will be available when needed or that the packets RED slope will not force the discard of the packet. Setting proper CBS parameters and controlling CBS oversubscription is one major safeguard to queue starvation (when a queue does not receive its fair share of buffers). Another is properly setting the RED slope parameters for the needs of services on this port or channel.

This command applies to egress queue group queues as the queue-delay is only supported on egress queues. This command the queue-delay command are mutually exclusive.

The no form of this command returns the MBS size assigned to the queue to the value.

Default

mbs default

Parameters

size

The size parameter is required when specifying mbs and is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional byte and kilobyte keywords are mutually exclusive and are used to explicitly define whether size represents bytes or kilobytes.

Values

0 to 1073741824

bytes

When byte is defined, the value given for size is interpreted as the queue’s MBS value given in bytes.

kilobytes

When kilobytes is defined, the value is interpreted as the queue’s MBS value given in kilobytes.

default

Keyword that reverts the MBS to its default value.

Platforms

All

Context

[Tree] (config>service>ipipe>sap>ingress>policer-over>plcr mbs)

[Tree] (config>service>cpipe>sap>egress>policer-over>plcr mbs)

[Tree] (config>service>ipipe>sap>egress>policer-over>plcr mbs)

[Tree] (config>service>cpipe>sap>ingress>policer-over>plcr mbs)

[Tree] (config>service>epipe>sap>egress>policer-over>plcr mbs)

[Tree] (config>service>epipe>sap>ingress>policer-over>plcr mbs)

Full Context

configure service ipipe sap ingress policer-override policer mbs

configure service cpipe sap egress policer-override policer mbs

configure service ipipe sap egress policer-override policer mbs

configure service cpipe sap ingress policer-override policer mbs

configure service epipe sap egress policer-override policer mbs

configure service epipe sap ingress policer-override policer mbs

Description

This command, within the SAP ingress and egress policer-overrides contexts, is used to override the sap-ingress and sap-egress QoS policy configured mbs parameter for the specified policer-id.

The no form of this command is used to restore the MBS to the default value. By default, the MBS is 16 Mbytes when PIR equals max or is greater than or equal to the FP capacity (this overrides an explicit configured MBS value); otherwise, 10 ms volume of traffic for a configured non-zero/non-max PIR capped to 3968 kbytes, with a minimum of 256 bytes.

Default

no mbs

Parameters

size

The size parameter is required when specifying mbs override and is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional byte and kilobyte keywords are mutually exclusive and are used to explicitly define whether size represents bytes or kilobytes.

Values

0 to 2683435456, default

bytes

When bytes is defined, the value given for size is interpreted as the policer MBS value in bytes.

kilobytes

When kilobytes is defined, the value given for size is interpreted as the policer MBS value in kilobytes.

Platforms

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

• configure service ipipe sap ingress policer-override policer mbs
• configure service ipipe sap egress policer-override policer mbs
• configure service epipe sap egress policer-override policer mbs
• configure service epipe sap ingress policer-override policer mbs

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

• configure service cpipe sap ingress policer-override policer mbs
• configure service cpipe sap egress policer-override policer mbs

Context

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

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

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

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

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

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

Full Context

configure service cpipe sap egress queue-override queue mbs

configure service ipipe sap egress queue-override queue mbs

configure service ipipe sap ingress queue-override queue mbs

configure service epipe sap egress queue-override queue mbs

configure service epipe sap ingress queue-override queue mbs

configure service cpipe sap ingress queue-override queue mbs

Description

This command overrides specific attributes of the specified queue’s MBS parameters. A queue uses its MBS value to determine whether it has exhausted all of its buffers while enqueuing packets. Once the queue has exceeded the number of buffers allowed by the MBS, all packets are discarded until packets have been drained from the queue.

The sum of the MBS for all queues on an ingress access port can oversubscribe the total amount of buffering available. When congestion occurs and buffers become scarce, access to buffers is controlled by the RED slope associated with a packet. A queue that has not exceeded its MBS is not guaranteed to have buffer available when needed or that the packet’s RED slope will not force the discard of the packet. Setting correct CBS parameters and controlling CBS oversubscription is one major safeguard to queue starvation (when a queue does not receive its fair share of buffers). Another is properly setting the RED slope parameters for the needs of services on this port or channel.

The no form of this command returns the MBS assigned to the queue to the default value.

Default

mbs default

Parameters

size

The size parameter is an integer expression of the maximum number of kilobytes or bytes of buffering allowed for the queue. A value of 0 causes the queue to discard all packets.

Values

0 to 1073741824, default

bytes

Indicates that the size parameter value is expressed in bytes.

kilobytes

Indicates that the size parameter is expressed in kilobytes.

Platforms

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

• configure service cpipe sap egress queue-override queue mbs
• configure service cpipe sap ingress queue-override queue mbs

All

• configure service epipe sap egress queue-override queue mbs
• configure service ipipe sap egress queue-override queue mbs
• configure service epipe sap ingress queue-override queue mbs
• configure service ipipe sap ingress queue-override queue mbs

Context

[Tree] (config>service>vpls>sap>ingress>policer-override>plcr mbs)

[Tree] (config>service>vpls>sap>egress>policer-override>plcr mbs)

Full Context

configure service vpls sap ingress policer-override policer mbs

configure service vpls sap egress policer-override policer mbs

Description

This command, within the SAP ingress and egress policer-overrides contexts, is used to override the sap-ingress and sap-egress QoS policy configured mbs parameter for the specified policer-id.

The no form of this command restores the MBS to the default value. By default, the MBS is 16 Mbytes when PIR equals max or is greater than or equal to the FP capacity (this overrides an explicit configured MBS value); otherwise, 10 ms volume of traffic for a configured non-zero/non-max PIR capped to 3968 kbytes, with a minimum of 256 bytes.

Default

no mbs

Parameters

size

This parameter is required when specifying MBS override and is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional byte and kilobyte keywords are mutually exclusive and are used to explicitly define whether size represents bytes or kilobytes.

Values

0 to 2683435456, 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-override>plcr mbs)

[Tree] (config>service>ies>if>sap>egress>policer-override>plcr mbs)

Full Context

configure service ies interface sap ingress policer-override policer mbs

configure service ies interface sap egress policer-override policer mbs

Description

This command, within the SAP ingress and egress policer-overrides contexts, is used to override the sap-ingress and sap-egress QoS policy configured mbs parameter for the specified policer-id.

The no form of this command restores the MBS setting to the default value. By default, the MBS is 16 Mbytes when PIR equals max or is greater than or equal to the FP capacity (this overrides an explicit configured MBS value); otherwise, 10 ms volume of traffic for a configured non-zero/non-max PIR capped to 3968 kbytes, with a minimum of 256 bytes.

Default

no mbs

Parameters

size

This parameter is required when specifying MBS override and is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional byte and kilobyte keywords are mutually exclusive and are used to explicitly define whether size represents bytes or kilobytes.

Values

0 to 2683435456, 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>policer-override>plcr mbs)

[Tree] (config>service>vprn>if>sap>egress>policer-override>plcr mbs)

Full Context

configure service vprn interface sap ingress policer-override policer mbs

configure service vprn interface sap egress policer-override policer mbs

Description

This command, within the SAP ingress and egress policer-overrides contexts, is used to override the sap-ingress and sap-egress QoS policy configured mbs parameter for the specified policer-id.

The no form of this command restores the MBS to the default value. By default, the MBS is 16 Mbytes when PIR equals max or is greater than or equal to the FP capacity (this overrides an explicit configured MBS value); otherwise, 10 ms volume of traffic for a configured non-zero/non-max PIR capped to 3968 kbytes, with a minimum of 256 bytes.

Default

no mbs

Parameters

size

This parameter is required when specifying MBS override and is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional byte and kilobyte keywords are mutually exclusive and are used to explicitly define whether size represents bytes or kilobytes.

Values

0 to 2683435456, default

Default

kilobytes

Platforms

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

Context

[Tree] (config>app-assure>group>policer>congestion-override mbs)

Full Context

configure application-assurance group policer congestion-override mbs

Description

This command configures the maximum burst size for the policer. It is recommended that MBS is configured larger than twice the MTU for the traffic handled by the policer to allow for some burstiness of the traffic. MBS is configurable for single-bucket, dual-bucket bandwidth and flow setup rate policers only.

The no form of this command removes the congested MBS value from the configuration.

Default

mbs 0

Parameters

congested-mbs

Specifies the maximum burst size, in kbytes, when the access-network-level, which the subscriber belongs to, is in a congested state.

Values

0 to 131071

Platforms

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

Context

[Tree] (config>app-assure>group>tod-override mbs)

Full Context

configure application-assurance group policer tod-override mbs

Description

This command provides a mechanism to configure the maximum burst size for the policer. It is recommended that MBS is configured larger than twice the MTU for the traffic handled by the policer to allow for some burstiness of the traffic. MBS is configurable for single-bucket, dual-bucket bandwidth and flow setup rate policers only.

The no form of this command resets the MBS value to its default.

Default

mbs 0

Parameters

maximum-burst-size

Specifies an integer value defining either size, in kbytes, for the MBS of the bandwidth policer, or flow count for the MBS of the flow setup rate policers.

Values

0 to 131071

Platforms

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

Context

[Tree] (config>qos>sap-ingress>policer mbs)

[Tree] (config>qos>sap-ingress>dyn-policer mbs)

[Tree] (config>qos>sap-egress>policer mbs)

[Tree] (config>qos>sap-egress>dyn-policer mbs)

Full Context

configure qos sap-ingress policer mbs

configure qos sap-ingress dynamic-policer mbs

configure qos sap-egress policer mbs

configure qos sap-egress dynamic-policer mbs

Description

This command is used to configure the policer’s PIR leaky bucket’s high-priority violate threshold. The high-prio-only command is applied to the MBS value to derive the bucket’s low-priority violate threshold. For ingress, trusted in-profile packets and untrusted high-priority packets use the policer’s high-priority violate threshold while trusted out-of-profile and untrusted low-priority packets use the policer's low-priority violate threshold. At egress, inplus-profile, and in-profile packets use the policer’s high-priority violate threshold and out-of-profile packets use the policer's low-priority violate threshold. Exceed-profile packets are discarded unless enable-exceed-pir is configured, in which case they are forwarded.

The PIR bucket’s violate threshold represents the maximum burst tolerance allowed by the policer. If the policer's offered rate is equal to or less than the policer's defined rate, the PIR bucket depth hovers around the 0 depth with spikes up to the maximum packet size in the offered load. If the offered rate increases beyond the metering rate, the amount of data allowed above the rate is capped by the threshold. The low-priority violate threshold provides a smaller burst size for the lower priority traffic associated with the policer. Since all lower priority traffic is discarded at the lower burst tolerance size, the remaining burst tolerance defined by high-prio-only is available for the higher priority traffic.

The policer’s MBS size defined in the QoS policy may be overridden on an SLA profile or SAP where the policy is applied.

The no form of this command returns the queue to its default MBS size. By default, the MBS is 16 Mbytes when PIR equals max or is greater than or equal to the FP capacity (this overrides an explicit configured MBS value); otherwise, 10 ms volume of traffic for a configured non-zero/non-max PIR capped to 3968 kbytes, with a minimum of 256 bytes.

Parameters

size [bytes | kilobytes]

The size parameter is required when specifying mbs and is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional bytes and kilobytes keywords are mutually exclusive and are used to explicitly define whether size represents bytes or kilobytes.

Values

0 to 2683435456, default

Platforms

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

• configure qos sap-ingress policer mbs
• configure qos sap-egress policer mbs

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

• configure qos sap-egress dynamic-policer mbs
• configure qos sap-ingress dynamic-policer mbs

Context

[Tree] (config>qos>sap-egress>queue mbs)

Full Context

configure qos sap-egress queue mbs

Description

This command configures the maximum number of buffers, in bytes or kilobytes, allowed for a specific queue. The value overrides the default value for the context.

The delay-time command option configures the MBS as a function of the expected delay. The system automatically translates this configuration into kilobytes based on the administrative rate of the queue parent (for example, the scheduler or aggregate-shaper).

The delay-percent command option configures the MBS as percentage of the SAP delay budget of the queue configured using the latency-budget command.

The no form of this command returns the queue to its default MBS.

Default

mbs default

Parameters

size

This parameter is required when specifying mbs and is expressed as an integer representing the required size in either bytes or kilobytes.

Default

kilobyte

default

Keyword to set the MBS to its default value.

bytes

Keyword to interpret the configured value is in bytes.

Values

0 to 1073741824

kilobytes

Keyword to interpret the configured value is in kilobytes.

Values

0 to 1048576

Default

kilobytes

microseconds

Specifies the MBS as a function of delay time.

Values

0 to 1000000

percent

Specifies the MBS as a percentage of the SAP latency budget.

Values

0.00 to 100.00

Platforms

All

Context

[Tree] (config>qos>sap-ingress>queue mbs)

Full Context

configure qos sap-ingress queue mbs

Description

This command configures the maximum number of buffers allowed for a specific queue. The value is given in bytes or kilobytes and overrides the default value for the context.

The no form of this command returns the policer to its default MBS.

Default

no mbs

Parameters

size

The size parameter is required when specifying mbs and is expressed as an integer representing the required size in either bytes or kilobytes.

Default

kilobyte

default

Sets the MBS to its default value.

bytes

Specifies that the value given for size is interpreted as the queue’s MBS value given in bytes.

Values

0 to 2688000

kilobytes

Specifies the value is interpreted as the queue’s MBS value given in kilobytes.

Values

0 to 2625

Default

kilobytes

Platforms

All

Context

[Tree] (config>qos>network-queue>queue mbs)

Full Context

configure qos network-queue queue mbs

Description

This command specifies the relative amount of buffer pool space for the maximum buffers for a specific ingress network FP forwarding class queue or egress network port forwarding class queue. The value is entered as a percentage.

The MBS value is used by a queue to determine whether it has exhausted its total allowed buffers while enqueuing packets. When the queue has exceeded its maximum amount of buffers, all packets are discarded until the queue transmits a packet. A queue that has not exceeded its MBS is not guaranteed to have a buffer available when needed or that the packet’s RED slope will not force the discard of the packet. In order to safeguard against queue starvation (when a queue does not receive its fair share of buffers), set proper CBS parameters and control CBS oversubscription. Another safeguard is to properly set the RED slope parameters for the needs of the network queues.

The MBS can sometimes be smaller than the CBS. This will result in a portion of the CBS for the queue to be unused and should be avoided.

The no form of this command returns the MBS for the queue to the default for the forwarding class.

Parameters

percent

The percent of buffers from the total buffer pool space for the maximum number of buffers, expressed as a decimal integer. If 10 Mbytes is the total buffer space in the buffer pool, a value of 10 would limit the maximum queue size to 1 Mbyte (10%) of buffer space for the forwarding class queue. If the total size is increased to 20 Mbytes, the existing value of 10 would automatically increase the maximum size of the queue to 2 Mbytes.

Values

0 to 100

Platforms

All

Context

[Tree] (config>qos>qgrps>egr>qgrp>policer mbs)

[Tree] (config>qos>qgrps>ing>qgrp>policer mbs)

Full Context

configure qos queue-group-templates egress queue-group policer mbs

configure qos queue-group-templates ingress queue-group policer mbs

Description

This command specifies the default maximum buffer size for the template queue in bytes or kilobytes.

The MBS value is used by a queue to determine whether it has exhausted all of its buffers while enqueuing packets. When the queue has exceeded the amount of buffers allowed by MBS, all packets are discarded until packets have been drained from the queue.

The port>ethernet>access>ingress>queue-group and port>ethernet>access>egress>queue-group contexts for mbs provides a mechanism for overriding the default maximum size for the queue.

The sum of the MBS for all queues on an ingress access port can oversubscribe the total amount of buffering available. When congestion occurs and buffers become scarce, access to buffers is controlled by the RED slope that a packet is associated with. A queue that has not exceeded its MBS size is not guaranteed that a buffer will be available when needed or that the packet’s RED slope will not force the discard of the packet. Setting proper CBS parameters and controlling CBS oversubscription is one major safeguard against queue starvation (when a queue does not receive its fair share of buffers). Another is properly setting the RED slope parameters for the needs of services on this port or channel.

When configured on an egress queue group queue, this command and the queue-delay command are mutually exclusive. In order to change between the mbs and queue-delay parameters, the current parameter must be removed before adding the new parameter; that is, changing from mbs to queue-delay requires a no mbs before the queue-delay is configured and changing from queue-delay to mbs requires a no queue-delay before the mbs is configured. If queue-delay is configured for an egress queue group queue, it is not possible to override the MBS for that queue.

For policers, this command is used to configure the policer’s PIR leaky bucket’s high-priority violate threshold. The high-prio-only command is applied to the MBS value to derive the bucket’s low-priority violate threshold.

At ingress, trusted in-profile packets and untrusted high-priority packets use the policer’s high-priority violate threshold while trusted out-of-profile and untrusted low-priority packets use the policer's low-priority violate threshold.

At egress, inplus-profile and in-profile packets use the policer’s high-priority violate threshold and out-of-profile packets use the policer's low-priority violate threshold. Exceed-profile packets are discarded unless enable-exceed-pir is configured, in which case they are forwarded.

The PIR bucket’s violate threshold represents the maximum burst tolerance allowed by the policer. If the policer's offered rate is equal to or less than the policer's defined rate, the PIR bucket depth hovers around the 0 depth with spikes up to the maximum packet size in the offered load. If the offered rate increases beyond the metering rate, the amount of data allowed above the rate is capped by the threshold. The low-priority violate threshold provides a smaller burst size for the lower priority traffic associated with the policer. Since all lower priority traffic is discarded at the lower burst tolerance size, the remaining burst tolerance defined by high-prio-only is available for the higher priority traffic.

The policer’s mbs size defined in the QoS policy may be overridden on an SLA profile or SAP where the policy is applied.

The no form of this command returns the MBS size to its default value. By default, the MBS is 16 Mbytes when PIR equals max or is greater than or equal to the FP capacity (this overrides an explicit configured MBS value); otherwise, 10 ms volume of traffic for a configured non-zero/non-max PIR capped to 3968 kbytes, with a minimum of 256 bytes.

Default

default

Parameters

size

For queues, the size parameter is an integer expression of the maximum number of bytes or kilobytes of buffering allowed for the queue. For a value of 100 kbytes, enter the value 100. A value of 0 causes the queue to discard all packets. For policers, the size parameter is an integer expression of the maximum number of bytes for the policer's MBS. The queue MBS maximum value used is constrained by the pool size in which the queue exists and by the shared pool space in the corresponding megapool.

Values

0 to 2683435456

Default value: 16 Mbytes when PIR equals max or is greater than or equal to the FP capacity (this overrides an explicitly configured MBS value); otherwise, 10 ms volume of traffic for a configured non-zero/non-max PIR capped to 3968 kbytes, with a minimum of 256 bytes.

[bytes | kilobytes]

Specifies bytes or kilobytes.

Default

kilobytes

default

Sets the MBS to its default value.

Platforms

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

Context

[Tree] (config>qos>qgrps>egr>qgrp>queue mbs)

[Tree] (config>qos>qgrps>ing>qgrp>queue mbs)

Full Context

configure qos queue-group-templates egress queue-group queue mbs

configure qos queue-group-templates ingress queue-group queue mbs

Description

This command specifies the default maximum buffer size for the template queue in bytes or kilobytes.

The MBS value is used by a queue to determine whether it has exhausted all of its buffers while enqueuing packets. When the queue has exceeded the amount of buffers allowed by MBS, all packets are discarded until packets have been drained from the queue.

The port>ethernet>access>ingress>queue-group and port>ethernet>access>egress>queue-group contexts for mbs provides a mechanism for overriding the default maximum size for the queue.

The sum of the MBS for all queues on an ingress access port can oversubscribe the total amount of buffering available. When congestion occurs and buffers become scarce, access to buffers is controlled by the RED slope that a packet is associated with. A queue that has not exceeded its MBS size is not guaranteed that a buffer will be available when needed or that the packet’s RED slope will not force the discard of the packet. Setting proper CBS parameters and controlling CBS oversubscription is one major safeguard against queue starvation (when a queue does not receive its fair share of buffers). Another is properly setting the RED slope parameters for the needs of services on this port or channel.

When configured on an egress queue group queue, this command and the queue-delay command are mutually exclusive. In order to change between the mbs and queue-delay parameters, the current parameter must be removed before adding the new parameter; that is, changing from mbs to queue-delay requires a no mbs before the queue-delay is configured and changing from queue-delay to mbs requires a no queue-delay before the mbs is configured. If queue-delay is configured for an egress queue group queue, it is not possible to override the MBS for that queue.

For policers, this command is used to configure the policer’s PIR leaky bucket’s high-priority violate threshold. The high-prio-only command is applied to the MBS value to derive the bucket’s low-priority violate threshold.

At ingress, trusted in-profile packets and untrusted high-priority packets use the policer’s high-priority violate threshold while trusted out-of-profile and untrusted low-priority packets use the policer's low-priority violate threshold.

At egress, inplus-profile and in-profile packets use the policer’s high-priority violate threshold and out-of-profile packets use the policer's low-priority violate threshold. Exceed-profile packets are discarded unless enable-exceed-pir is configured, in which case they are forwarded.

The PIR bucket’s violate threshold represents the maximum burst tolerance allowed by the policer. If the policer's offered rate is equal to or less than the policer's defined rate, the PIR bucket depth hovers around the 0 depth with spikes up to the maximum packet size in the offered load. If the offered rate increases beyond the metering rate, the amount of data allowed above the rate is capped by the threshold. The low-priority violate threshold provides a smaller burst size for the lower priority traffic associated with the policer. Since all lower priority traffic is discarded at the lower burst tolerance size, the remaining burst tolerance defined by high-prio-only is available for the higher priority traffic.

The policer’s mbs size defined in the QoS policy may be overridden on an SLA profile or SAP where the policy is applied.

The no form of this command returns the MBS size assigned by the queue.

Default

default

Parameters

size

For queues, the size parameter is an integer expression of the maximum number of bytes or kilobytes of buffering allowed for the queue. For a value of 100 kbytes, enter the value 100. A value of 0 causes the queue to discard all packets. For policers, the size parameter is an integer expression of the maximum number of bytes for the policer's MBS. The queue MBS maximum value used is constrained by the pool size in which the queue exists and by the shared pool space in the corresponding megapool.

Values

0 to 1048576 or default

Minimum configurable non-zero value: 6 kbytes on an FP2, 7680 bytes on an FP3, and 16 kbytes on an FP4

Minimum non-zero default value: maximum of 10 ms of CIR, or 6 kbytes on an FP2, 7680 bytes on an FP3, and 16 kbytes on an FP4

[bytes | kilobytes]

Specifies bytes or kilobytes.

Default

kilobytes

default

Sets the MBS to its default value.

Platforms

All

Context

[Tree] (config>qos>shared-queue>queue mbs)

Full Context

configure qos shared-queue queue mbs

Description

This command specifies the relative amount of the buffer pool space for the maximum buffers for a specific ingress shared queue.

The MBS value is used by a queue to determine whether it has exhausted its total allowed buffers while enqueuing packets. When the queue has exceeded its maximum amount of buffers, all packets are discarded until the queue transmits a packet. A queue that has not exceeded its MBS size is not guaranteed that a buffer will be available when needed. Setting proper CBS parameters and controlling CBS oversubscription is one major safeguard against queue starvation (when a queue does not receive its fair share of buffers).

The MBS size can sometimes be smaller than the CBS. This will result in a portion of the CBS for the queue to be unused and should be avoided.

Default

The queue MBS defaults are listed in Queue MBS Default Values.

Parameters

percent

The percent of buffers from the total buffer pool space for the maximum amount of buffers, expressed as a decimal integer.

Values

0 to 100

Platforms

All

Context

[Tree] (config>system>security>cpm-queue>queue mbs)

Full Context

configure system security cpm-queue queue mbs

Description

This command specifies the maximum queue depth to which a queue can grow.

Parameters

mbs

Specifies the maximum burst size in kbytes.

Platforms

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

Context

[Tree] (config>subscr-mgmt>sub-prof>egr>plcr-ctrl-plcy>mbs-thrshlds>prio mbs-contribution)

[Tree] (config>subscr-mgmt>sub-prof>ing>plcr-ctrl-plcy>mbs-thrshlds>prio mbs-contribution)

Full Context

configure subscriber-mgmt sub-profile egress policer-control-policy priority-mbs-thresholds priority mbs-contribution

configure subscriber-mgmt sub-profile ingress policer-control-policy priority-mbs-thresholds priority mbs-contribution

Description

This command is used to configure the policy-based burst tolerance for a parent policer instance created when the policy is applied to a SAP or subscriber context. The system uses the parent policer’s min-thresh-separation value, the priority level’s mbs-contribution value and the number of child policers currently attached to the priority level to derive the priority level’s shared-portion and fair-portion of burst tolerance within the local priority level. The shared-portion and fair-portions for each priority level are then used by the system to calculate each priority level’s discard-unfair threshold and discard-all threshold.

The value for a priority level’s mbs-contribution within the policer-control-policy may be overridden on the SAP or subscriber sub-profile where the policy is applied in order to allow fine tuning of the discard-unfair and discard-all thresholds relevant to the needs of the local child policers on the object.

Accumulative Nature of Burst Tolerance for a Parent Policer Priority Level

When defining mbs-contribution, the specified size may only be a portion of the burst tolerance associated with the priority level. The packets associated with the priority level share the burst tolerance of lower within the parent policer. As the parent policer PIR bucket depth increases during congestion, the lower priority packets eventually experience discard based on each priority’s discard-unfair and discard-all thresholds. Assuming congestion continues once all the lower priority packets have been prevented from consuming bucket depth, the burst tolerance for the priority level is consumed by its own packets and any packets associated with higher priorities.

The Effect of Fair and Unfair Child Policer Traffic at a Parent Policer Priority Level

The system continually monitors the offered rate of each child policer on each parent policer priority level and detects when the policer is in a congested state (the aggregate offered load is greater than the decrement rate defined on the parent policer). As previously stated, the result of congestion is that the parent policer's bucket depth will increase until it eventually hovers around either a discard-unfair or discard-all threshold belonging to one of the priority levels. This threshold is the point where enough packets are being discarded that the increment rate and decrement rate begin to even out. If only a single child policer is associated to the priority level, the discard-unfair threshold is not used since fairness is only applicable when multiple child policers are competing at the same priority level.

When multiple child policers are sharing the congested priority level, the system uses the offered rates and the parenting parameters of each child to determine the fair rate per child when the parent policer is unable to meet the bandwidth needs of each child. The fair rate represents the number of bandwidth that each child at the priority level should receive relative to the other children at the same level according to the policer control policy instance managing the child policers. This fair rate is applied as the decrement rate for each child's FIR bucket. Changing a child’s FIR rate does not modify the number of packets forwarded by the parent policer for the child’s priority level. It simply modifies the forwarded ratio between the children on that priority level. Since each child FIR bucket has some level of burst tolerance before marking its packets as unfair, the current parent policer bucket depth may at times rise above the discard-unfair threshold. The mbs-contribution value provides a means to define how much separation is provided between the priority level’s discard-unfair and discard-all threshold to allow the parent policer to absorb some of the FIR burst before reaching the priority’s discard-all threshold.

This level of fair aggregate burst tolerance is based on the decrement rate of the parent policer’s PIR bucket while the individual fair bursts making up the aggregate are based on each child’s FIR decrement rate. The aggregate fair rate of the priority level is managed by the system with consideration of the current rate of traffic in higher priority levels. In essence, the system ensures that for each iteration of the child FIR rate calculation, the sum of the child FIR decrement rates plus the sum of the higher priority traffic increment rates equals the parent policers decrement rate. This means that dynamic numbers of higher priority traffic can be ignored when sizing a lower priority’s fair aggregate burst tolerance. Consider the following:

• The parent policer decrement rate is set to 20 Mb/s (max-rate 20,000).

• A priority level’s fair burst size is set to 30 kbytes (mbs-contribution 30 kbytes).

• Higher priority traffic is currently taking 12 Mb/s.

• The priority level has three child policers attached.

• Each child’s PIR MBS is set to 10 kbytes, which makes each child’s FIR MBS 10 kbytes.

• The children want 10 Mb/s, but only 8 Mb/s is available,

• Based on weights, the children's FIR rates are set as follows.

  Table 2. FIR Rates of the Children Based on Weights

  	FIR Rate	FIR MBS
  Child 1	4 Mb/s	10 kbytes
  Child 2	3 Mb/s	10 kbytes
  Child 3	1 Mb/s	10 kbytes

The 12 Mb/s of the higher priority traffic and the 8 Mb/s of fair traffic equal the 20 Mb/s decrement rate of the parent policer.

It is clear that the higher priority traffic is consuming 12 Mb/s of the parent policer’s decrement rate, leaving 8 Mb/s of decrement rate for the lower priority’s fair traffic.

• The burst tolerance of child 1 is based on 10 kbytes above 4 Mb/s,

• The burst tolerance of child 2 is based on 10 kbytes above 3 Mb/s,

• The burst tolerance of child 3 is based on 10 kbytes above 1 Mb/s.

If all three children burst simultaneously (unlikely), they will consume 30 kbytes above 8 Mb/s. This is the same as the remaining decrement rate after the higher priority traffic.

Parent Policer Total Burst Tolerance and Downstream Buffering

The highest in-use priority level’s discard-all threshold is the total burst tolerance of the parent policer. In some cases the parent policer represents downstream bandwidth capacity and the max-rate of the parent policer is set to prevent overrunning the downstream bandwidth. The burst tolerance of the parent policer defines how much more traffic may be sent beyond the downstream scheduling capacity. In the worst case scenario, when the downstream buffering is insufficient to handle the total possible burst from the parent policer, downstream discards based on lack of buffering may occur. However, in all likelihood, this is not the case.

In most cases, lower priority traffic in the policer is responsible for the greater part of congestion above the parent policer rate. Since this traffic is discarded with a lower threshold, this lowers the effective burst tolerance even while the highest priority traffic is present.

Configuring a Priority Level's MBS Contribution Value

In the most conservative case, a priority level’s mbs-contribution value may be set to be greater than the sum of child policer’s mbs and one max-size-frame per child policer. This ensures that even in the absolute worst case where all the lower priority levels are simultaneously bursting to the maximum capacity of each child, enough burst tolerance for the priority’s children will exist if they also burst to their maximum capacity.

Since simply adding up all the child policer’s PIR MBS values may result in large overall burst tolerances that are not ever likely to be needed, you should consider some level of burst oversubscription when configuring the mbs-contribution value for each priority level. The number of oversubscription should be determined based on the needs of each priority level.

Using the Fixed Keyword to Create Deterministic Parent Policer Discard Thresholds

In the default behavior, the system ignores the mbs-contribution values for a priority level on a subscriber or SAP parent policer when a child policer is not currently associated with the level. This prevents additional burst tolerance from being added to higher priority traffic within the parent policer.

This does cause fluctuations in the defined threshold values when child policers are added or removed from a parent policer instance. If this behavior is undesirable, the fixed keyword may be used which causes the mbs-contribution value to always be included in the calculation of parent policer’s discard thresholds. The defined mbs-contribution value may be overridden on a subscriber sla-profile or on a SAP instance, but the fixed nature of the contribution cannot be overridden.

If the defined mbs-contribution value for the priority level is zero, the priority level will have no effect on the parent policer’s defined discard thresholds. A packet associated with the priority level will use the next lower priority level’s discard-unfair and discard-all thresholds.

The form of this command returns the policy’s priority level’s MBS contribution to the default value. When changed, the thresholds for the priority level and all higher priority levels for all instances of the parent policer is recalculated.

Parameters

size [bytes | kilobytes]

The size parameter is required when executing the mbs-contribution command. It is expressed as an integer and specifies the priority’s specific portion of accumulative MBS for the priority level in bytes or kilobytes which is selected by the trailing bytes or kilobytes keywords. If both bytes and kilobytes are missing, kilobytes is assumed. Setting this value has no effect on parent policer instances where the priority level’s mbs-contribution value has been overridden.

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. Size is interpreted as specifying the size of min-thresh-separation in kilobytes.

Default

kilobytes

fixed

This optional fixed keyword is used to force the inclusion of the defined mbs-contribution value in the parent policer’s discard threshold calculations. If the mbs-contribution command is executed without the fixed keyword, the fixed calculation behavior for the priority level is removed.

Platforms

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

Context

[Tree] (config>card>fp>ingress>access>qgrp>policer-ctrl-over>mbs-thrshlds>prio mbs-contribution)

[Tree] (config>card>fp>ing>network>qgrp>policer-ctrl-over>mbs-thrshlds>prio mbs-contribution)

Full Context

configure card fp ingress access queue-group policer-control-override priority-mbs-thresholds priority mbs-contribution

configure card fp ingress network queue-group policer-control-override priority-mbs-thresholds priority mbs-contribution

Description

This command configures the policy-based burst tolerance for a parent policer instance created when the policy is applied to a SAP or subscriber context. The system uses the parent policer’s min-thresh-separation value, the priority level’s mbs-contribution value and the number of child policers currently attached to the priority level to derive the priority level’s shared-portion and fair-portion of burst tolerance within the local priority level. The shared-portion and fair-portions for each priority level are then used by the system to calculate each priority level’s discard-unfair threshold and discard-all threshold.

The value for a priority level’s mbs-contribution within the policer-control-policy may be overridden on the SAP or subscriber sub-profile where the policy is applied in order to allow fine tuning of the discard-unfair and discard-all thresholds relevant to the needs of the local child policers on the object.

Accumulative Nature of Burst Tolerance for a Parent Policer Priority Level

When defining mbs-contribution, the specified size may only be a portion of the burst tolerance associated with the priority level. The packets associated with the priority level share the burst tolerance of lower within the parent policer. As the parent policer PIR bucket depth increases during congestion, the lower priority packets eventually experience discard based on each priority’s discard-unfair and discard-all thresholds. Assuming congestion continues once all the lower priority packets have been prevented from consuming bucket depth, the burst tolerance for the priority level will be consumed by its own packets and any packets associated with higher priorities.

The Effect of Fair and Unfair Child Policer Traffic at a Parent Policer Priority Level

The system continually monitors the offered rate of each child policer on each parent policer priority level and detects when the policer is in a congested state (the aggregate offered load is greater than the decrement rate defined on the parent policer). As previously stated, the result of congestion is that the parent policer's bucket depth will increase until it eventually hovers around either a discard-unfair or discard-all threshold belonging to one of the priority levels. This threshold is the point where enough packets are being discarded that the increment rate and decrement rate begin to even out. If only a single child policer is associated to the priority level, the discard-unfair threshold is not used since fairness is only applicable when multiple child policers are competing at the same priority level.

When multiple child policers are sharing the congested priority level, the system uses the offered rates and the parenting parameters of each child to determine the fair rate per child when the parent policer is unable to meet the bandwidth needs of each child. The fair rate represents the amount of bandwidth that each child at the priority level should receive relative to the other children at the same level according to the policer control policy instance managing the child policers. This fair rate is applied as the decrement rate for each child’s FIR bucket. Changing a child’s FIR rate does not modify the amount of packets forwarded by the parent policer for the child’s priority level. It simply modifies the forwarded ratio between the children on that priority level. Since each child FIR bucket has some level of burst tolerance before marking its packets as unfair, the current parent policer bucket depth may at times rise above the discard-unfair threshold. The mbs-contribution value provides a means to define how much separation is provided between the priority level’s discard-unfair and discard-all threshold to allow the parent policer to absorb some amount of FIR burst before reaching the priority’s discard-all threshold.

This level of fair aggregate burst tolerance is based on the decrement rate of the parent policer’s PIR bucket while the individual fair bursts making up the aggregate are based on each child’s FIR decrement rate. The aggregate fair rate of the priority level is managed by the system with consideration of the current rate of traffic in higher priority levels. In essence, the system ensures that for each iteration of the child FIR rate calculation, the sum of the child FIR decrement rates plus the sum of the higher priority traffic increment rates equals the parent policers decrement rate. This means that dynamic amounts of higher priority traffic can be ignored when sizing a lower priority’s fair aggregate burst tolerance. Consider the following:

• The parent policer decrement rate is set to 20 Mb/s (max-rate 20,000).

• A priority level’s fair burst size is set to 30 kbytes (mbs-contribution 30 kilobytes).

• Higher priority traffic is currently taking 12 Mb/s.

• The priority level has three child policers attached.

• Each child’s PIR MBS is set to 10 kbytes, which makes each child’s FIR MBS 10 kbytes.

• The children want 10 Mb/s, but only 8 Mb/s is available.

• The following table describes the FIR rates of the children based on weights.

  Table 3. FIR Rates of the Children Based on Weights

  	FIR Rate	FIR MBS
  Child 1	4 Mb/s	10 kbytes
  Child 2	3 Mb/s	10 kbytes
  Child 3	1 Mb/s	10 kbytes

The 12 Mb/s of the higher priority traffic and the 8 Mb/s of fair traffic equal the 20 Mb/s decrement rate of the parent policer.

It is clear that the higher priority traffic is consuming 12 Mb/s of the parent policer’s decrement rate, leaving 8 Mb/s of decrement rate for the lower priority’s fair traffic.

• The burst tolerance of child 1 is based on 10 kbytes above 4 Mb/s,

• The burst tolerance of child 2 is based on 10 kbytes above 3 Mb/s,

• The burst tolerance of child 3 is based on 10 kbytes above 1 Mb/s.

If all three children burst simultaneously (unlikely), they will consume 30 kbytes above 8 Mb/s. This is the same as the remaining decrement rate after the higher priority traffic.

Parent Policer Total Burst Tolerance and Downstream Buffering

The highest in-use priority level’s discard-all threshold is the total burst tolerance of the parent policer. In some cases the parent policer represents downstream bandwidth capacity and the max-rate of the parent policer is set to prevent overrunning the downstream bandwidth. The burst tolerance of the parent policer defines how much more traffic may be sent beyond the downstream scheduling capacity. In the worst case scenario, when the downstream buffering is insufficient to handle the total possible burst from the parent policer, downstream discards based on lack of buffering may occur. However, in all likelihood, this is not the case.

In most cases, lower priority traffic in the policer will be responsible for the greater part of congestion above the parent policer rate. Since this traffic is discarded with a lower threshold, this lowers the effective burst tolerance even while the highest priority traffic is present.

Configuring a Priority Level's MBS Contribution Value

In the most conservative case, a priority level’s mbs-contribution value may be set to be greater than the sum of child policer’s MBS and one max-size-frame per child policer. This ensures that even in the absolute worst case where all the lower priority levels are simultaneously bursting to the maximum capacity of each child, enough burst tolerance for the priority’s children will exist if they also burst to their maximum capacity.

Since simply adding up all the child policer’s PIR MBS values may result in large overall burst tolerances that are not ever likely to be needed, you should consider some level of burst oversubscription when configuring the mbs-contribution value for each priority level. The amount of oversubscription should be determined based on the needs of each priority level.

Using the Fixed Keyword to Create Deterministic Parent Policer Discard Thresholds

In the default behavior, the system ignores the mbs-contribution values for a priority level on a subscriber or SAP parent policer when a child policer is not currently associated with the level. This prevents additional burst tolerance from being added to higher priority traffic within the parent policer.

This does cause fluctuations in the defined threshold values when child policers are added or removed from a parent policer instance. If this behavior is undesirable, the fixed keyword may be used which causes the mbs-contribution value to always be included in the calculation of parent policer’s discard thresholds. The defined mbs-contribution value may be overridden on a subscriber SLA profile or on a SAP instance, but the fixed nature of the contribution cannot be overridden.

If the defined mbs-contribution value for the priority level is zero, the priority level will have no effect on the parent policer’s defined discard thresholds. A packet associated with the priority level will use the next lower priority level’s discard-unfair and discard-all thresholds.

The no form of this command reverts to the policy’s priority level’s MBS contribution to the default value. When changed, the thresholds for the priority level and all higher priority levels for all instances of the parent policer are recalculated.

Default

no mbs-contribution

Parameters

size

Specifies that the size parameter is required when executing the mbs-contribution command. It is expressed as an integer and specifies the priority’s specific portion amount of accumulative MBS for the priority level in bytes or kilobytes which is selected by the trailing bytes or kilobytes keywords. If both bytes and kilobytes are missing, kilobytes is assumed. Setting this value has no effect on parent policer instances where the priority level’s mbs-contribution value has been overridden. Clearing an override on parent policer instance causes this value to be enforced.

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.

Default

kilobytes

Platforms

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

Context

[Tree] (config>service>cpipe>sap>ingress>policer-ctrl-over>mbs-thrshlds>priority mbs-contribution)

[Tree] (config>service>ipipe>sap>egress>policer-ctrl-over>mbs-thrshlds>priority mbs-contribution)

[Tree] (config>service>ipipe>sap>ingress>policer-ctrl-over>mbs-thrshlds>priority mbs-contribution)

[Tree] (config>service>epipe>sap>egress>policer-ctrl-over>mbs-thrshlds>priority mbs-contribution)

[Tree] (config>service>epipe>sap>ingress>policer-ctrl-over>mbs-thrshlds>priority mbs-contribution)

[Tree] (config>service>cpipe>sap>egress>policer-ctrl-over>mbs-thrshlds>priority mbs-contribution)

Full Context

configure service cpipe sap ingress policer-control-override priority-mbs-thresholds priority mbs-contribution

configure service ipipe sap egress policer-control-override priority-mbs-thresholds priority mbs-contribution

configure service ipipe sap ingress policer-control-override priority-mbs-thresholds priority mbs-contribution

configure service epipe sap egress policer-control-override priority-mbs-thresholds priority mbs-contribution

configure service epipe sap ingress policer-control-override priority-mbs-thresholds priority mbs-contribution

configure service cpipe sap egress policer-control-override priority-mbs-thresholds priority mbs-contribution

Description

The mbs-contribution override command within the SAP ingress and egress contexts is used to override a parent policer’s priority level’s mbs-contribution parameter that is defined within the policer-control-policy applied to the SAP. This override allow the priority level’s burst tolerance to be tuned based on the needs of the SAP’s child policers attached to the priority level.

When the override is defined, modifications to the policer-control-policy priority level’s mbs-contribution parameter have no effect on the SAP’s parent policer priority level until the override is removed using the no mbs-contribution command within the SAP.

The no form of this command removes the override and allows the mbs-contribution setting from the policer-control-policy to control the parent policer’s priority level’s burst tolerance.

Default

no mbs-contribution

Parameters

size

Specifies the mbs-contribution override value.

Values

1 to 16777216 | default

bytes

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

kilobytes

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

Platforms

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

• configure service cpipe sap egress policer-control-override priority-mbs-thresholds priority mbs-contribution
• configure service cpipe sap ingress policer-control-override priority-mbs-thresholds priority mbs-contribution

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

• configure service epipe sap ingress policer-control-override priority-mbs-thresholds priority mbs-contribution
• configure service ipipe sap ingress policer-control-override priority-mbs-thresholds priority mbs-contribution
• configure service ipipe sap egress policer-control-override priority-mbs-thresholds priority mbs-contribution
• configure service epipe sap egress policer-control-override priority-mbs-thresholds priority mbs-contribution

Context

[Tree] (config>service>vpls>sap>ingress>policer-ctrl-over>mbs-thrshlds>priority mbs-contribution)

[Tree] (config>service>vpls>sap>egress>policer-ctrl-over>mbs-thrshlds>priority mbs-contribution)

Full Context

configure service vpls sap ingress policer-control-override priority-mbs-thresholds priority mbs-contribution

configure service vpls sap egress policer-control-override priority-mbs-thresholds priority mbs-contribution

Description

The mbs-contribution override command within the SAP ingress and egress contexts is used to override a parent policer’s priority level’s mbs-contribution parameter that is defined within the policer-control-policy applied to the SAP. This override allow the priority level’s burst tolerance to be tuned based on the needs of the SAP’s child policers attached to the priority level.

When the override is defined, modifications to the policer-control-policy priority level’s mbs-contribution parameter have no effect on the SAP’s parent policer priority level until the override is removed using the no mbs-contribution command within the SAP.

The no form of this command removes the override and allows the mbs-contribution setting from the policer-control-policy to control the parent policer’s priority level’s burst tolerance.

Default

no mbs-contribution

Parameters

size

This parameter is required when specifying MBS contribution override and is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional byte and kilobyte keywords are mutually exclusive and are used to explicitly define whether size represents bytes or kilobytes.

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>priority mbs-contribution)

[Tree] (config>service>ies>if>sap>egress>policer-ctrl-over>mbs-thrshlds>priority mbs-contribution)

Full Context

configure service ies interface sap ingress policer-control-override priority-mbs-thresholds priority mbs-contribution

configure service ies interface sap egress policer-control-override priority-mbs-thresholds priority mbs-contribution

Description

The mbs-contribution override command within the SAP ingress and egress contexts is used to override a parent policer’s priority level’s mbs-contribution parameter that is defined within the policer-control-policy applied to the SAP. This override allow the priority level’s burst tolerance to be tuned based on the needs of the SAP’s child policers attached to the priority level.

When the override is defined, modifications to the policer-control-policy priority level’s mbs-contribution parameter have no effect on the SAP’s parent policer priority level until the override is removed using the no mbs-contribution command within the SAP.

The no form of this command removes the override and allows the mbs-contribution setting from the policer-control-policy to control the parent policer’s priority level’s burst tolerance.

Default

no mbs-contribution

Parameters

size

This parameter is required when specifying MBS contribution override and is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional byte and kilobyte keywords are mutually exclusive and are used to explicitly define whether size represents bytes or kilobytes.

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>egress>policer-ctrl-over>mbs-thrshlds>priority mbs-contribution)

[Tree] (config>service>vprn>if>sap>ingress>policer-ctrl-over>mbs-thrshlds>priority mbs-contribution)

Full Context

configure service vprn interface sap egress policer-control-override priority-mbs-thresholds priority mbs-contribution

configure service vprn interface sap ingress policer-control-override priority-mbs-thresholds priority mbs-contribution

Description

The mbs-contribution override command within the SAP ingress and egress contexts is used to override a parent policer’s priority level’s mbs-contribution parameter that is defined within the policer-control-policy applied to the SAP. This override allow the priority level’s burst tolerance to be tuned based on the needs of the SAP’s child policers attached to the priority level.

When the override is defined, modifications to the policer-control-policy priority level’s mbs-contribution parameter have no effect on the SAP’s parent policer priority level until the override is removed using the no mbs-contribution command within the SAP.

The no form of this command removes the override and allows the mbs-contribution setting from the policer-control-policy to control the parent policer’s priority level’s burst tolerance.

Default

no mbs-contribution

Parameters

size

This parameter is required when specifying MBS contribution override and is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional byte and kilobyte keywords are mutually exclusive and are used to explicitly define whether size represents bytes or kilobytes.

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>priority mbs-contribution)

Full Context

configure qos policer-control-policy root priority-mbs-thresholds priority mbs-contribution

Description

The mbs-contribution command is used to configure the policy-based burst tolerance for a parent policer instance created when the policy is applied to a SAP, or a subscriber context for the 7450 ESS and 7750 SR, or a 7950 XRS multiservice site. The system uses the parent policer’s min-thresh-separation value, the priority level’s mbs-contribution value, and the number of child policers currently attached to the priority level to derive the priority level’s shared-portion and fair-portion of burst tolerance within the local priority level. The shared-portion and fair-portions for each priority level are then used by the system to calculate each priority level’s discard-unfair threshold and discard-all threshold. The mbs-contribution is the minimum separation between two adjacent active discard-all thresholds.

The value for a priority level’s mbs-contribution within the policer-control-policy may be overridden on the SAP, or subscriber sub-profile (applies to the 7450 ESS and 7750 SR) or multiservice site (for 7950 XRS) where the policy is applied in order to allow fine tuning of the discard-unfair and discard-all thresholds relevant to the needs of the local child policers on the object.

Accumulative Nature of Burst Tolerance for a Parent Policer Priority Level

When defining mbs-contribution, the specified size may only be a portion of the burst tolerance associated with the priority level. The packets associated with the priority level share the burst tolerance of lower within the parent policer. As the parent policer PIR bucket depth increases during congestion, the lower priority packets eventually experience discard based on each priority’s discard-unfair and discard-all thresholds. Assuming congestion continues when all the lower priority packets have been prevented from consuming bucket depth, the burst tolerance for the priority level will be consumed by its own packets and any packets associated with higher priorities.

The Effect of Fair and Unfair Child Policer Traffic at a Parent Policer Priority Level

The system continually monitors the offered rate of each child policer on each parent policer priority level and detects when the policer is in a congested state (the aggregate offered load is greater than the decrement rate defined on the parent policer). As previously stated, the result of congestion is that the parent policer's bucket depth will increase until it eventually hovers around either a discard-unfair or discard-all threshold belonging to one of the priority levels. This threshold is the point where enough packets are being discarded that the increment rate and decrement rate begin to even out. If only a single child policer is associated with the priority level, the discard-unfair threshold is not used since fairness is only applicable when multiple child policers are competing at the same priority level.

When multiple child policers are sharing the congested priority level, the system uses the offered rates and the parenting parameters of each child to determine the fair rate per child when the parent policer is unable to meet the bandwidth needs of each child. The fair rate represents the amount of bandwidth that each child at the priority level should receive relative to the other children at the same level according to the policer control policy instance managing the child policers. This fair rate is applied as the decrement rate for each child's FIR bucket. Changing a child’s FIR rate does not modify the number of packets forwarded by the parent policer for the child’s priority level. It just modifies the forwarded ratio between the children on that priority level. Since each child FIR bucket has some level of burst tolerance before marking its packets as unfair, the current parent policer bucket depth may at times rise above the discard-unfair threshold. The mbs-contribution value provides a means to define how much separation is provided between the priority level’s discard-unfair and discard-all threshold to allow the parent policer to absorb some amount of FIR burst before reaching the priority’s discard-all threshold.

This level of fair aggregate burst tolerance is based on the decrement rate of the parent policer’s PIR bucket while the individual fair bursts making up the aggregate are based on each child’s FIR decrement rate. The aggregate fair rate of the priority level is managed by the system with consideration of the current rate of traffic in higher priority levels. In essence, the system ensures that for each iteration of the child FIR rate calculation, the sum of the child FIR decrement rates plus the sum of the higher priority traffic increment rates equals the parent policers decrement rate. This means that dynamic amounts of higher priority traffic can be ignored when sizing a lower priority’s fair aggregate burst tolerance. Consider the following:

• The parent policer decrement rate is set to 20 Mb/s (max-rate 20,000).

• A priority level’s fair burst size is set to 30 kbytes (mbs-contribution 30 kbytes).

• Higher priority traffic is currently taking 12 Mb/s.

• The priority level has three child policers attached.

• Each child’s PIR MBS is set to 10 kbytes, which makes each child’s FIR MBS 10 kbytes.

• The children want 10 Mb/s, but only 8 Mb/s is available

• Based on weights, the children's FIR rates are set as follows.

  Table 4. FIR Rates of the Children Based on Weights

  	FIR Rate	FIR MBS
  Child 1	4 Mb/s	10 kbytes
  Child 2	3 Mb/s	10 kbytes
  Child 3	1 Mb/s	10 kbytes

The 12 Mb/s of the higher priority traffic and the 8 Mb/s of fair traffic equal the 20 Mb/s decrement rate of the parent policer.

It is clear that the higher priority traffic is consuming 12 Mb/s of the parent policer’s decrement rate, leaving 8 Mb/s of decrement rate for the lower priority’s fair traffic.

• The burst tolerance of child 1 is based on 10 kbytes above 4 Mb/s.

• The burst tolerance of child 2 is based on 10 kbytes above 3 Mb/s.

• The burst tolerance of child 3 is based on 10 kbytes above 1 Mb/s.

If all three children burst simultaneously (unlikely), they will consume 30 kbytes above 8 Mb/s. This is the same as the remaining decrement rate after the higher priority traffic.

Parent Policer Total Burst Tolerance and Downstream Buffering

The highest in-use priority level’s discard-all threshold is the total burst tolerance of the parent policer. In some cases, the parent policer represents downstream bandwidth capacity and the max-rate of the parent policer is set to prevent overrunning the downstream bandwidth. The burst tolerance of the parent policer defines how much more traffic may be sent beyond the downstream scheduling capacity. In the worst-case scenario, when the downstream buffering is insufficient to handle the total possible burst from the parent policer, downstream discards based on lack of buffering may occur. However, in all likelihood, this is not the case.

In most cases, lower priority traffic in the policer will be responsible for the greater part of congestion above the parent policer rate. Since this traffic is discarded with a lower threshold, this lowers the effective burst tolerance even while the highest priority traffic is present.

Configuring a Priority Level's MBS Contribution Value

In the most conservative case, a priority level’s mbs-contribution value may be set to be greater than the sum of child policer’s mbs and one max-size-frame per child policer. This ensures that even in the absolute worst case where all the lower priority levels are simultaneously bursting to the maximum capacity of each child, enough burst tolerance for the priority’s children will exist if they also burst to their maximum capacity.

Since simply adding up all the child policer’s PIR MBS values may result in large overall burst tolerances that are not ever likely to be needed, consider some level of burst oversubscription when configuring the mbs-contribution value for each priority level. The amount of oversubscription should be determined based on the needs of each priority level.

Using the Fixed Keyword to Create Deterministic Parent Policer Discard Thresholds

In the default behavior, the system ignores the mbs-contribution values for a priority level on a subscriber for 7450 ESS and 7750 SR, or a multiservice site for 7950 XRS, or SAP parent policer when a child policer is not currently associated with the level. This prevents additional burst tolerance from being added to higher priority traffic within the parent policer.

This does cause fluctuations in the defined threshold values when child policers are added or removed from a parent policer instance. If this behavior is undesirable, the fixed keyword may be used that causes the mbs-contribution value to always be included in the calculation of parent policer’s discard thresholds. The defined mbs-contribution value may be overridden on a subscriber sla-profile for the 7450 ESS and 7750 SR, or on a multiservice site for the 7950 XRS, or on a SAP instance, but the fixed nature of the contribution cannot be overridden.

If the defined mbs-contribution value for the priority level is zero, the priority level will have no effect on the parent policer’s defined discard thresholds. A packet associated with the priority level will use the next lower priority level’s discard-unfair and discard-all thresholds.

The no form of this command returns the policy’s priority level’s MBS contribution to the default value. When changed, the thresholds for the priority level and all higher priority levels for all instances of the parent policer will be recalculated.

Parameters

size

The size parameter is required when executing the mbs-contribution command. It is expressed as an integer and specifies the priority’s specific portion amount of accumulative MBS for the priority level. Setting this value has no effect on parent policer instances where the priority level’s mbs-contribution value has been overridden.

Values

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

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

Default

8

bytes | kilobytes:

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

Default

kilobytes

fixed

The optional fixed keyword is used to force the inclusion of the defined mbs-contribution value in the parent policer’s discard threshold calculations. If the mbs-contribution command is executed without the fixed keyword, the fixed calculation behavior for the priority level is removed.

Platforms

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

Context

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

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

Full Context

configure system security ssh key-re-exchange client mbytes

configure system security ssh key-re-exchange server mbytes

Description

This command configures the maximum bytes to be transmitted before a key re-exchange is initiated by the server.

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

Default

mbytes 1024

Parameters

mbytes

Specifies the number of megabytes, on a SSH session, after which the SSH client initiates the key-re-exchange.

Values

1 to 64000

Default

1024

disable

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

Platforms

All

Context

[Tree] (config>subscr-mgmt>msap-policy>vpls-only>igmp-snp>mcac mc-constraints)

Full Context

configure subscriber-mgmt msap-policy vpls-only-sap-parameters igmp-snooping mcac mc-constraints

Description

Commands in this context configure the level and its associated bandwidth for a bundle or a logical interface.

Platforms

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

Context

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

[Tree] (config>service>vpls>sap>igmp-snooping>mcac mc-constraints)

Full Context

configure service vpls sap mld-snooping mcac mc-constraints

configure service vpls sap igmp-snooping mcac mc-constraints

Description

Commands in this context configure multicast CAC constraints.

Platforms

All

Context

[Tree] (config>service>vprn>igmp>grp-if>mcac mc-constraints)

[Tree] (config>service>vprn>pim>if>mcac mc-constraints)

[Tree] (config>service>vprn>mld>if>mcac mc-constraints)

[Tree] (config>service>vprn>igmp>if>mcac mc-constraints)

[Tree] (config>service>vprn>mld>grp-if>mcac mc-constraints)

Full Context

configure service vprn igmp group-interface mcac mc-constraints

configure service vprn pim interface mcac mc-constraints

configure service vprn mld interface mcac mc-constraints

configure service vprn igmp interface mcac mc-constraints

configure service vprn mld group-interface mcac mc-constraints

Description

Commands in this context configure multicast CAC constraints.

Platforms

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

• configure service vprn mld group-interface mcac mc-constraints
• configure service vprn igmp group-interface mcac mc-constraints

All

• configure service vprn pim interface mcac mc-constraints
• configure service vprn mld interface mcac mc-constraints
• configure service vprn igmp interface mcac mc-constraints

Context

[Tree] (config>router>mld>grp-if>mcac mc-constraints)

[Tree] (config>router>mld>interface>mcac mc-constraints)

[Tree] (config>router>igmp>grp-if>mcac mc-constraints)

[Tree] (config>router>igmp>interface>mcac mc-constraints)

[Tree] (config>router>pim>interface>mcac mc-constraints)

[Tree] (config>router>mcac>policy>bundle mc-constraints)

Full Context

configure router mld group-interface mcac mc-constraints

configure router mld interface mcac mc-constraints

configure router igmp group-interface mcac mc-constraints

configure router igmp interface mcac mc-constraints

configure router pim interface mcac mc-constraints

configure router mcac policy bundle mc-constraints

Description

Commands in this context configure the level and its associated bandwidth for a bundle or a logical interface.

Platforms

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

• configure router igmp group-interface mcac mc-constraints
• configure router mld group-interface mcac mc-constraints

All

• configure router pim interface mcac mc-constraints
• configure router mcac policy bundle mc-constraints
• configure router igmp interface mcac mc-constraints
• configure router mld interface mcac mc-constraints

Context

[Tree] (config>router>pim mc-ecmp-balance)

Full Context

configure router pim mc-ecmp-balance

Description

This command enables multicast balancing of traffic over ECMP links based on the number of (S, G) distributed over each link. When enabled, each new multicast stream that needs to be forwarded over an ECMP link is compared to the count of (S, G) already using each link, so that the link with the fewest (S, G) is chosen.

This command cannot be used together with the mc-ecmp-hashing-enabled command.

The no form of this command disables multicast ECMP balancing.

Platforms

All

Context

[Tree] (config>service>vprn>pim mc-ecmp-balance)

Full Context

configure service vprn pim mc-ecmp-balance

Description

This command enables multicast balancing of traffic over ECMP links based on the number of (S, G) distributed over each link. When enabled, each new multicast stream that needs to be forwarded over an ECMP link is compared to the count of (S, G) already using each link, so that the link with the fewest (S, G) is chosen.

This command cannot be used together with the mc-ecmp-hashing-enabled command.

The no form of this command disables multicast ECMP balancing.

Platforms

All

Context

[Tree] (config>router>pim mc-ecmp-balance-hold)

Full Context

configure router pim mc-ecmp-balance-hold

Description

This command defines a hold period that applies after an interface has been added to the ECMP link. It is also used periodically to rebalance if channels have been removed from the ECMP link.

If the ECMP interface has not changed in the hold period and if no multicast streams have been removed, then no action is taken when the timer triggers.

This parameter should be used to avoid excessive changes to the multicast distribution.

A rebalance will not occur to multicast streams that have a priority greater than the configured ecmp-opt-threshold.

The no form of this command removes the minutes value from the configuration.

Parameters

minutes

Specifies the hold time, in minutes, that applies after an interface has been added to the ECMP link.

Values

2 to 600

Platforms

All

Context

[Tree] (config>service>vprn>pim mc-ecmp-balance-hold)

Full Context

configure service vprn pim mc-ecmp-balance-hold

Description

This command configures the hold time for multicast balancing over ECMP links.

Parameters

minutes

Specifies the hold time, in minutes, that applies after an interface has been added to the ECMP link.

Platforms

All

Context

[Tree] (config>service>vprn>pim mc-ecmp-hashing-enabled)

Full Context

configure service vprn pim mc-ecmp-hashing-enabled

Description

This command enables hash-based multicast balancing of traffic over ECMP links and causes PIM joins to be distributed over the multiple ECMP paths based on a hash of S and G (and possibly next-hop IP address). When a link in the ECMP set is removed, the multicast flows that were using that link are redistributed over the remaining ECMP links using the same hash algorithm. When a link is added to the ECMP set new joins may be allocated to the new link based on the hash algorithm, but existing multicast flows using the other ECMP links stay on those links until they are pruned.

Hash-based multicast balancing is supported for both IPv4 and IPv6.

This command cannot be used together with the mc-ecmp-balance command. Using this command and the lag-usage-optimization command on mixed port speed LAGs is not recommended, because some groups may be forwarded incorrectly.

The no form of this command disables the hash-based multicast balancing of traffic over ECMP links.

The no form of this command means that the use of multiple ECMP paths if enabled at the config>router or config>service>vprn context is controlled by the existing implementation and CLI commands mc-ecmp-balance.

Default

no mc-ecmp-hashing-enabled

Parameters

rebalance

Specifies to rebalance flows to newly added links immediately, instead of waiting until they are pruned.

Platforms

All

Context

[Tree] (config>router>pim mc-ecmp-hashing-enabled)

Full Context

configure router pim mc-ecmp-hashing-enabled

Description

This command enables hash-based multicast balancing of traffic over ECMP links and causes PIM joins to be distributed over the multiple ECMP paths based on a hash of S and G (and possibly next-hop IP address). When a link in the ECMP set is removed, the multicast flows that were using that link are redistributed over the remaining ECMP links using the same hash algorithm. When a link is added to the ECMP set new joins may be allocated to the new link based on the hash algorithm, but existing multicast flows using the other ECMP links stay on those links until they are pruned.

Hash-based multicast balancing is supported for both IPv4 and IPv6.

This command cannot be used together with the mc-ecmp-balance command. Using this command and the lag-usage-optimization command on mixed port speed LAGs is not recommended, because some groups may be forwarded incorrectly.

The no form of this command disables the hash-based multicast balancing of traffic over ECMP links.

Default

no mc-ecmp-hashing-enabled

Parameters

rebalance

Specifies to rebalance flows to newly added links immediately, instead of waiting until they are pruned.

Platforms

All

Context

[Tree] (config>redundancy>multi-chassis>peer mc-endpoint)

Full Context

configure redundancy multi-chassis peer mc-endpoint

Description

This command specifies that the endpoint is multi-chassis. This value should be the same on both MC-EP peers for the pseudowires that must be part of the same group.

The no form of this command removes the endpoint from the MC-EP. Single chassis behavior applies.

Default

no mc-endpoint

Platforms

All

Context

[Tree] (config>service>vpls>endpoint mc-endpoint)

Full Context

configure service vpls endpoint mc-endpoint

Description

This command specifies the identifier associated with the multi-chassis endpoint. This value should be the same on both MC-EP peers for the pseudowires that must be part of the same group.

The no form of this command removes the endpoint from the MC-EP. Single chassis behavior applies.

Default

no mc-endpoint

Parameters

mc-ep-id

Specifies a multi-chassis endpoint ID

Values

1 to 4294967295

Platforms

All

Context

[Tree] (config>system>load-balancing mc-enh-load-balancing)

Full Context

configure system load-balancing mc-enh-load-balancing

Description

This command enables enhanced egress multicast load balancing behavior for Layer 3 multicast. When enabled, the router will spray the multicast traffic using as hash inputs from the packet based on lsr-load-balancing, l4-load-balancing and system-ip-load-balancing configurations. That is, an ingress LER or IP PE will spray traffic based on the IP hash criteria: SA/DA + optional Layer 4 port + optional system IP egress LER or LSR will spray traffic based on label or IP hash criteria outlined above or both based on configuration of lsr-load-balancing, l4-load-balancing, and system-ip-load-balancing.

The no form of the command preserves the default behavior for per flow hashing of multicast traffic.

Default

no mc-enh-load-balancing

Platforms

All

Context

[Tree] (config>service>vpls>endpoint>mc-ep mc-ep-peer)

Full Context

configure service vpls endpoint mc-endpoint mc-ep-peer

Description

This command adds multi-chassis endpoint object.

The no form of this command removes the multi-chassis endpoint object.

Default

no mc-ep-peer

Parameters

name

Specifies the name of the multi-chassis endpoint peer

ip-address

Specifies the IP address of multi-chassis endpoint peer

Platforms

All

Context

[Tree] (config>mcast-mgmt>mcast-info-plcy>video-policy>video-if>sd mc-handover)

[Tree] (config>mcast-mgmt>mcast-info-plcy>video-policy>video-if>hd mc-handover)

[Tree] (config>mcast-mgmt>mcast-info-plcy>video-policy>video-if>pip mc-handover)

Full Context

configure mcast-management multicast-info-policy video-policy video-interface sd mc-handover

configure mcast-management multicast-info-policy video-policy video-interface hd mc-handover

configure mcast-management multicast-info-policy video-policy video-interface pip mc-handover

Description

This command sets the rate at which the Fast Channel Change (FCC) server will send unicast data to the FCC client during the handover to the multicast stream.

The no form of the command returns the parameter to the default value.

Default

mc-handover 25

Parameters

percentage

Specifies the percentage of nominal bandwidth.

Values

HD:	0 to 100
SD and PIP:	0 to 600

Default

25

Platforms

7450 ESS, 7750 SR, 7750 SR-s

Context

[Tree] (config>redundancy>multi-chassis>peer mc-ipsec)

Full Context

configure redundancy multi-chassis peer mc-ipsec

Description

Commands in this context configure multi-chassis peer parameters.

Platforms

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

Context

[Tree] (config>vrrp>policy>priority-event mc-ipsec-non-forwarding)

Full Context

configure vrrp policy priority-event mc-ipsec-non-forwarding

Description

This command configures an instance of a multi-chassis IPsec tunnel-group Priority Event used to override the base priority value of a VRRP virtual router instance depending on the operational state of the event.

Parameters

tunnel-grp-id

Identifies the multi-chassis IPsec tunnel group whose non-forwarding state is monitored by this priority control event.

Platforms

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

Context

[Tree] (config>redundancy>multi-chassis>peer mc-lag)

Full Context

configure redundancy multi-chassis peer mc-lag

Description

Commands in this context configure multi-chassis LAG operations and related parameters.

The no form of this command administratively disables multi-chassis LAG. MC-LAG can be issued only when mc-lag is shutdown.

Default

no mc-lag

Platforms

All

Context

[Tree] (config>eth-cfm>redundancy mc-lag)

Full Context

configure eth-cfm redundancy mc-lag

Description

Commands in this context configure the MC-LAG specific ETH-CFM redundancy parameters.

Platforms

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

Context

[Tree] (config>service>vprn mc-maximum-routes)

Full Context

configure service vprn mc-maximum-routes

Description

This command specifies the maximum number of multicast routes that can be held in the form of this command in a VPN routing or forwarding (VRF) context. When this limit is reached, a log and SNMP trap are sent. If the log-only parameter is not specified and the maximum-routes value is set below the existing number of routes in a VRF, then no new joins are processed.

The no form of this command disables the limit of multicast routes within a VRF context. Issue the no form of this command only when the VPRN instance is shutdown.

Default

no mc-maximum-routes

Parameters

number

Specifies the maximum number of routes to be held in a VRF context.

Values

1 to 2147483647

log-only

Specifies that if the maximum limit is reached, only log the event. log-only does not disable the learning of new routes.

threshold

Specifies the percentage at which a warning log message and SNMP trap should be sent.

Values

0 to 100

Default

10

Platforms

All

Context

[Tree] (config>router mc-maximum-routes)

Full Context

configure router mc-maximum-routes

Description

This command specifies the maximum number of multicast routes that can be held within a VPN routing/forwarding (VRF) context. When this limit is reached, a log and SNMP trap are sent. If the log-only parameter is not specified and the maximum-routes value is set below the existing number of routes in a VRF, then no new joins will be processed.

The no form of this command disables the limit of multicast routes within a VRF context. Issue the no form of this command only when the VPRN instance is shutdown.

Default

no mc-maximum-routes

Parameters

number

Specifies the maximum number of routes to be held in a VRF context.

Values

1 to 2147483647

log-only

Specifies that if the maximum limit is reached, only log the event. log-only does not disable the learning of new routes.

threshold

Specifies the percentage at which a warning log message and SNMP trap should be sent.

Values

0 to 100

Default

10

Platforms

All

Context

[Tree] (config>redundancy>multi-chassis>peer mc-ring)

Full Context

configure redundancy multi-chassis peer mc-ring

Description

Commands in this context configure the multi-chassis ring parameters.

The no form of this command reverts to the default.

Default

mc-ring

Platforms

All

Context

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

Full Context

configure redundancy multi-chassis peer sync mc-ring

Description

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

Default

no mc-ring

Platforms

All

Context

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

[Tree] (config>service>pw-template>igmp-snooping mcac)

Full Context

configure service vpls mesh-sdp snooping mcac

configure service pw-template igmp-snooping mcac

Description

Commands in this context configure multicast CAC policy parameters and constraints for this interface.

Platforms

All

Context

[Tree] (config>subscr-mgmt>msap-policy>vpls-only>igmp-snp mcac)

Full Context

configure subscriber-mgmt msap-policy vpls-only-sap-parameters igmp-snooping mcac

Description

Commands in this context configure multicast CAC parameters.

Platforms

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

Context

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

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

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

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

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

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

Full Context

configure service vpls sap igmp-snooping mcac

configure service vpls sap mld-snooping mcac

configure service vpls spoke-sdp igmp-snooping mcac

configure service vpls mesh-sdp mld-snooping mcac

configure service vpls spoke-sdp mld-snooping mcac

configure service vpls mesh-sdp igmp-snooping mcac

Description

This command configures multicast CAC policy and constraints for this interface.

Platforms

All

Context

[Tree] (config>service>vprn>mld>if mcac)

[Tree] (config>service>vprn>igmp>if mcac)

[Tree] (config>service>vprn>igmp>grp-if mcac)

[Tree] (config>service>vprn>pim>if mcac)

[Tree] (config>service>vprn>mld>grp-if mcac)

Full Context

configure service vprn mld interface mcac

configure service vprn igmp interface mcac

configure service vprn igmp group-interface mcac

configure service vprn pim interface mcac

configure service vprn mld group-interface mcac

Description

This command configures multicast CAC policy and constraints for this interface.

Platforms

All

• configure service vprn pim interface mcac
• configure service vprn mld interface mcac
• configure service vprn igmp interface mcac

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

• configure service vprn igmp group-interface mcac
• configure service vprn mld group-interface mcac

Context

[Tree] (config>router>pim>if mcac)

[Tree] (config>router>igmp>interface mcac)

[Tree] (config>router>igmp>group-interface mcac)

[Tree] (config>router>mld>group-interface mcac)

[Tree] (config>router mcac)

[Tree] (config>router>mld>interface mcac)

Full Context

configure router pim interface mcac

configure router igmp interface mcac

configure router igmp group-interface mcac

configure router mld group-interface mcac

configure router mcac

configure router mld interface mcac

Description

Commands in this context configure multicast CAC parameters.

Platforms

All

• configure router mcac
• configure router igmp interface mcac
• configure router pim interface mcac
• configure router mld interface mcac

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

• configure router igmp group-interface mcac
• configure router mld group-interface mcac

Context

[Tree] (config>mcast-mgmt>chassis-level>plane-capacity mcast-capacity)

Full Context

configure mcast-management chassis-level per-mcast-plane-capacity mcast-capacity

Description

This command configures the primary and secondary multicast plane capacities used when the full complement of possible switch fabrics in the system is not up (at least one possible switch fabric is not provisioned or is down). The rates are defined as a percentage of the total multicast plane capacity which is configured using the total-capacity command.

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

Default

mcast-capacity 87.50 secondary 87.50

Parameters

primary-percentage

Specifies the percentage of the total multicast plane capacity to be used for primary multicast planes.

secondary-percentage

Specifies the percentage of the total multicast plane capacity to be used for secondary multicast planes.

Values

0.01 to 100

Platforms

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

Context

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

Full Context

configure cflowd collector export-filter family mcast-ipv4

Description

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

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

Default

no mcast-ipv4

Platforms

All

Context

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

Full Context

configure cflowd collector export-filter family mcast-ipv6

Description

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

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

Default

no mcast-ipv6

Platforms

All

Context

[Tree] (config>service>vpls mcast-ipv6-snooping-scope)

Full Context

configure service vpls mcast-ipv6-snooping-scope

Description

This command specifies the forwarding scope used for IPv6 multicast traffic when PIM snooping for IPv6 is enabled.

By default, the scope is mac-based; IPv6 snooped multicast traffic is forwarded is based on the low-order 32 bits of the destination IPv6 address.

When the scope is configured as sg-based, the IPv6 snooped multicast traffic is forwarded based on both its full source (if specified in the join) and destination IPv6 address. SG-based forwarding is only supported on FP3- (or higher) based line cards.

PIM snooping for IPv6 must be disabled to change the forwarding mode within a VPLS service between mac-based and sg-based.

The no form of this command configures the router to use the default value.

Default

mcast-ipv6-snooping-scope mac-based

Parameters

mac-based

Sets forwarding for PIM-snooped IPv6 multicast traffic based on the low-order 32 bits of its destination IPv6 address.

sg-based

Sets forwarding for PIM-snooped IPv6 multicast traffic based on its full source (if specified in the join) and destination IPv6 address.

Platforms

All

Context

[Tree] (config mcast-management)

Full Context

configure mcast-management

Description

Commands in this context configure multicast management parameters. The mcast-management CLI node contains the bandwidth-policy and multicast-info-policy definitions. The bandwidth-policy is used to manage the ingress multicast paths into the switch fabric. The multicast-info-policy defines how each multicast channel is handled by the system. The policy may be used by the ingress multicast bandwidth manager, the ECMP path manager and the egress multicast CAC manager.

The mcast-management node always exists and contains the default bandwidth-policy and the default multicast-info-policy. Enter the mcast-management node when editing, deleting or creating a bandwidth policy or multicast info policy. The default bandwidth policy and multicast-info-policy cannot be edited or deleted.

A chassis-level node within multicast-management is used to control the switch fabric multicast planes replication limits. The switch fabric multicast planes are the individual multicast spatial replication contexts available in the system.

Platforms

All

Context

[Tree] (config>card>fp>ingress mcast-path-management)

Full Context

configure card fp ingress mcast-path-management

Description

This CLI node contains the forwarding plane settings for ingress multicast path management. Enter the node to configure the bandwidth-policy and the administrative state of ingress multicast path management.

Platforms

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

Context

[Tree] (config>mcast-mgmt>bw-plcy mcast-pool)

Full Context

configure mcast-management bandwidth-policy mcast-pool

Description

This command configures the ingress multicast path management buffer pool. The pool is used by the primary and secondary path queues through which all ingress managed multicast traffic must flow. The parameters may be used to configure the size of the pool relative to the total ingress buffer space, the amount of reserved CBS buffers within the pool and the slope policy used to manage early congestion detection functions in the shared portion of the pool.

Care should be taken when managing the buffer pool space as changes to the systems buffer pool behavior can have negative effects on multicast and unicast forwarding.

Sizing the Pool

The percent-of-total command defines how much of the total ingress buffer pool space for the MDA is dedicated for multicast channels managed by the bandwidth policy. Since multicast typically has a higher scheduling priority through the switch fabric, the buffer pool does not need to be large. By default, the system reserves 10% of the buffers on the ingress side of the MDA once multicast path management is enabled.

Reserved CBS Portion of the Pool

The multicast pool is divided into two portions; reserved and shared. The reserved portion is used by the multicast path queues until they cross there individual CBS thresholds. Since the CBS thresholds are configured as percentages and the percentages can oversubscribe the reserved portion of the pool, it is possible for some of the queues CBS buffer allocation to be met by the shared portion of the pool. By default, 50% of the pool is defined as reserved. This may be changed using the resv-cbs percentage parameter.

Shared Portion WRED Slopes

The shared portion of the buffer pool is used by queues that have crossed over their CBS thresholds. Since the total MBS values for the multicast path queues may oversubscribe the pool size, a buffer congestion control mechanism is supported within the pool in the form of two WRED slopes. The slope-policy parameter defines how the slopes are configured and whether they are activated. Each packet entering a path queue is defined as high or low priority within the queue based on the channel’s preference value relative to the cong-priority-threshold command. When getting a shared buffer of a high priority packet, the high WRED slope is used. Low priority packets use the low WRED slope.

The no form of this command returns the managed multicast path pool to its default settings.

Parameters

percent-of-buffers

Specifies the percentage of ingress buffers that is allocated to the multicast pool.

Values

1 to 50

Default

10

percent-of-pool

Specifies the percentage of the pool that is reserved for multicast path queues within their CBS threshold.

Values

1 to 100

Default

50

slope-policy-name

Specifies the WRED slopes within the multicast pool. Once a slope policy is associated with a buffer pool, it cannot be deleted.

Default

default

Platforms

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

Context

[Tree] (config>subscr-mgmt>igmp-policy mcast-reporting)

Full Context

configure subscriber-mgmt igmp-policy mcast-reporting

Description

Commands in this context configure mcast reporting.

Platforms

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

Context

[Tree] (config>mcast-management mcast-reporting-dest)

Full Context

configure mcast-management mcast-reporting-dest

Description

This command creates a multicast reporting destination hierarchy in CLI under which parameters defining this destination can be specified. The destination refers to an external node that collects and analyze IGMP events.

The multicast reporting destination is associated with a name that each subscriber can reference to send the IGMP related events.

It can be also referenced in the host tracking policy in case that IGMP events are related to the host tracking feature.

The no form of this command removes the destination name from the configuration.

Parameters

dest-name

Specifies the multicast reporting destination name.

Platforms

All

Context

[Tree] (debug>mcast-mgmt mcast-reporting-dest)

Full Context

debug mcast-management mcast-reporting-dest

Description

This command debugs multicast path management reporting destinations.

Platforms

All

Context

[Tree] (config>subscr-mgmt>igmp-policy>mcast-reporting mcast-reporting-dest)

Full Context

configure subscriber-mgmt igmp-policy mcast-reporting mcast-reporting-dest

Description

This command references the multicast reporting destination to which IGMP-related events are exported. The multicast-reporting-destination is referenced within the IGMP policy for the subscriber.

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

Parameters

dest-name

Specifies the name of the multicast reporting destination, up to 32 characters.

Platforms

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

Context

[Tree] (config>router>ldp>targ-session>peer-template mcast-tunneling)

[Tree] (config>router>ldp>targ-session>peer mcast-tunneling)

Full Context

configure router ldp targeted-session peer-template mcast-tunneling

configure router ldp targeted-session peer mcast-tunneling

Description

At the downstream router, the FEC is resolved and the result of the resolution is a Label Mapping advertisement to the upstream peer.

At the upstream router, if the RSVP LSP does not exist to the peer address, the upstream router does not use the T-LDP session for FEC resolution.

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

Default

no mcast-tunneling

Platforms

All

Context

[Tree] (config>router>ldp mcast-upstream-asbr-frr)

Full Context

configure router ldp mcast-upstream-asbr-frr

Description

This command enables ASBR MoFRR.

When ASBR MoFRR is enabled, the local leaf will perform MoFRR for multiple ASBRs; for example, if there are two ASBRs, the local leaf will select one ASBR as the primary and another ASBR as the backup.

If the mcast-upstream-frr command is enabled, disabling ASBR MoFRR will only allow IGP MoFRR in the local AS; for example, a single ASBR will be selected and two separate, disjointed paths will be selected as the primary and backup LSPs from the local leaf to ASBR.

If the mcast-upstream-frr command is disabled, disabling ASBR MoFRR will disable MoFRR entirely.

The no form of the command disables ASBR MoFRR.

Default

no mcast-upstream-asbr-frr

Platforms

All

Context

[Tree] (config>router>ldp mcast-upstream-frr)

Full Context

configure router ldp mcast-upstream-frr

Description

This command enables the mLDP fast upstream switchover feature.

When this command is enabled and LDP is resolving a mLDP FEC received from a downstream LSR, it checks if an ECMP next-hop or a LFA next-hop exist to the root LSR node. If LDP finds one, it programs a primary ILM on the interface corresponding to the primary next-hop and a backup ILM on the interface corresponding to the ECMP or LFA next-hop. LDP then sends the corresponding labels to both upstream LSR nodes. In normal operation, the primary ILM accepts packets while the backup ILM drops them. If the interface or the upstream LSR of the primary ILM goes down causing the LDP session to go down, the backup ILM will then start accepting packets.

In order to make use of the ECMP next-hop, the user must configure the ecmp value in the system to at least 2 using the following command:

configure router ecmp

In order to make use of the LFA next-hop, the user must enable LFA using the following commands:

configure router isis loopfree-alternates

configure router ospf loopfree-alternates

Enabling IP FRR or LDP FRR features is not strictly required since LDP only needs to know where the alternate next-hop to the root LSR is to be able to send the Label Mapping message to program the backup ILM at the initial signaling of the tree. Thus enabling the LFA option is sufficient. If however, unicast IP and LDP prefixes need to be protected, then these features and the mLDP fast upstream switchover can be enabled concurrently.

The mLDP FRR fast switchover relies on the fast detection of loss of **LDP session** to the upstream peer to which the primary ILM label had been advertised. We strongly recommended to perform the following:

• Enable BFD on all LDP interfaces to upstream LSR nodes. When BFD detects the loss of the last adjacency to the upstream LSR, it will bring down immediately the LDP session which will cause the IOM to activate the backup ILM.

• If there is a concurrent TLDP adjacency to the same upstream LSR node, enable BFD on the T-LDP peer in addition to enabling it on the interface.

• Enable the ldp-sync-timer option on all interfaces to the upstream LSR nodes. If an LDP session to the upstream LSR to which the primary ILM is resolved goes down for any other reason than a failure of the interface or of the upstream LSR, routing and LDP will go out of sync. This means the backup ILM will remain activated until the next time SPF is rerun by IGP. By enabling IGP-LDP synchronization feature, the advertised link metric will be changed to max value as soon as the LDP session goes down. This in turn will trigger an SPF and LDP will likely download a new set of primary and backup ILMs.

The no form of this command disables the fast upstream switchover for mLDP FECs.

Default

no mcast-upstream-frr

Platforms

All

Context

[Tree] (config>router>bgp>add-paths mcast-vpn-ipv4)

[Tree] (config>router>bgp>group>add-paths mcast-vpn-ipv4)

[Tree] (config>router>bgp>group>neighbor>add-paths mcast-vpn-ipv4)

Full Context

configure router bgp add-paths mcast-vpn-ipv4

configure router bgp group add-paths mcast-vpn-ipv4

configure router bgp group neighbor add-paths mcast-vpn-ipv4

Description

This command configures the add-paths capability for multicast IPv4 VPN routes. By default, add-paths is not enabled for multicast IPv4 VPN routes.

The maximum number of multicast paths per IPv4 VPN prefix to send is the configured send-limit, which is a mandatory parameter. The capability to receive multiple multicast paths per prefix from a peer is configurable using the receive keyword, which is optional. If the receive keyword is not included in the command, receive capability is enabled by default. The none option disables the receive capability.

The no form of this command disables add-paths support for multicast IPv4 VPN routes, causing sessions established using add-paths for multicast IPv4 VPN to go down and come back up without the add-paths capability.

Default

no mcast-vpn-ipv4

Parameters

send-limit

Specifies the maximum number of paths per multicast IPv4 VPN prefix that are allowed to be advertised to add-paths peers. The actual number of advertised routes may be less. If the value is none, the router does not negotiate the send capability with respect to multicast IPv4 VPN AFI/SAFI.

Values

1 to 16, none

receive

Specifies that the router negotiates to receive multiple multicast routes per IPv4 VPN prefix.

none

Specifies that the router does not negotiate to receive multiple multicast routes per IPv4 VPN prefix.

Platforms

All

Context

[Tree] (config>router>bgp>group>neighbor>add-paths mcast-vpn-ipv6)

[Tree] (config>router>bgp>group>add-paths mcast-vpn-ipv6)

[Tree] (config>router>bgp>add-paths mcast-vpn-ipv6)

Full Context

configure router bgp group neighbor add-paths mcast-vpn-ipv6

configure router bgp group add-paths mcast-vpn-ipv6

configure router bgp add-paths mcast-vpn-ipv6

Description

This command configures the add-paths capability for multicast IPv6 VPN routes. By default, add-paths is not enabled for multicast IPv6 VPN routes.

The maximum number of multicast paths per IPv6 VPN prefix to send is the configured send-limit, which is a mandatory parameter. The capability to receive multiple multicast paths per prefix from a peer is configurable using the receive keyword, which is optional. If the receive keyword is not included in the command, receive capability is enabled by default. The none option disables the receive capability.

The no form of this command disables add-paths support for multicast IPv6 VPN routes, causing sessions established using add-paths for multicast IPv6 VPN to go down and come back up without the add-paths capability.

Default

no mcast-vpn-ipv6

Parameters

send-limit

Specifies the maximum number of paths per multicast IPv6 VPN prefix that are allowed to be advertised to add-paths peers. The actual number of advertised routes may be less. If the value is none, the router does not negotiate the send capability with respect to multicast IPv6 VPN AFI/SAFI.

Values

1 to 16, none

receive

Specifies that the router negotiates to receive multiple multicast routes per IPv6 VPN prefix.

none

Specifies that the router does not negotiate to receive multiple multicast routes per IPv6 VPN prefix.

Platforms

All

Context

[Tree] (config>app-assure>group>gtp>gtp-fltr>imsi-apn-fltr>entry mcc-mnc-prefix)

Full Context

configure application-assurance group gtp gtp-filter imsi-apn-filter entry mcc-mnc-prefix

Description

This command configures a matching condition for the IMSI (MCC-MNC) prefix.

Parameters

imsi-prefix-string

Specifies a string of 1 to 6 decimal digits representing the IMSI prefix to be matched against the IMSI IE of the packet, or the special value ANY_IMSI to indicate that an IMSI IE must be present as a matching condition regardless of the IMSI IE value.

If no MCC-MNC prefix is specified, the entry will match GTP packets that have an IMSI IE containing any value.

Values

0 to 999999, ANY_IMSI

Platforms

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

Context

[Tree] (config>service>vpls mcr-default-gtw)

Full Context

configure service vpls mcr-default-gtw

Description

Commands in this context configure the default gateway information when using Dual Homing in L2-TPSDA. The IP and MAC address of the default gateway used for subscribers on an L2 MC-Ring are configured in this context. After a ring heals or fails, the system sends out a gratuitous ARP on an active ring SAP in order to attract traffic from subscribers on the ring with connectivity to that SAP.

Platforms

All

Context

[Tree] (debug>service>id>pim-snooping mcs)

Full Context

debug service id pim-snooping mcs

Description

This command enables or disables debugging for PIM snooping multi-chassis synchronization.

Parameters

detail

Provides detailed debugging information

Platforms

All

Context

[Tree] (debug>router>igmp mcs)

Full Context

debug router igmp mcs

Description

This command enables debugging for IGMP multicast servers (MCS).

The no form of the command disables the IGMP interface debugging for the specifies interface name.

Parameters

ip-int-name

Debugs the information associated with the specified IP interface name.

Values

IP interface address

Platforms

All

Context

[Tree] (config>subscr-mgmt>acct-plcy mcs-interval)

Full Context

configure subscriber-mgmt radius-accounting-policy mcs-interval

Description

This command specifies the interval at which the active BNG in a dual-homed deployment synchronizes subscriber accounting data using MCS to the standby BNG. The MCS interval is a statically configured value or is equal to the configured RADIUS accounting update-interval.

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

Default

no mcs-interval

Parameters

minutes

Specifies the interval, in minutes, at which accounting data of the subscriber is synchronized.

Values

5 to 60

use-update-interval

Synchronizes subscriber accounting data at the same time as the RADIUS interim-update. For this, the configured update-interval in the RADIUS accounting policy is used, ignoring RADIUS overrides.

Platforms

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

Context

[Tree] (config>python>py-pol>cache mcs-peer)

Full Context

configure python python-policy cache mcs-peer

Description

This command specifies the MCS peer’s address and sync-tag for syncing the cached entries of the python-policy. The sync-tag must be match on both chassis.

The no form of this command reverts to the default.

Parameters

ip-address

Specifies the IPv4 address of the MCS peer.

sync-tag

Specifies the tag for sync, up to 32 characters.

Platforms

All

Context

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

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

Full Context

configure service vprn subscriber-interface group-interface wlan-gw mcs-peer

configure service ies subscriber-interface group-interface wlan-gw mcs-peer

Description

This command specifies the MCS peer address and sync-tag for synchronization of ESM and the tunnel state for ESM over soft-GRE with an MCS peer.

The no form of this command specifies no MCS synchronization of WLAN-GW ESM host and tunnel state on this group interface.

Default

no mcs-peer

Parameters

ip-address

Specifies the IPv4 address or the global IPv6 unicast address for an MCS peer.

sync-tag

Specifies the sync tag for synchronization of ESM and the tunnel state for ESM over soft-GRE with an MCS peer.

Platforms

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

Context

[Tree] (file md)

Full Context

file md

Description

This command creates a new directory in a file system.

Directories can only be created one level at a time.

Parameters

file-url

Specifies the directory name to be created.

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:

Platforms

All

Context

[Tree] (config>eth-cfm md-auto-id)

Full Context

configure eth-cfm md-auto-id

Description

This command automatically assigns numerical index values for ma-index and md-index in model-driven management interfaces.

Classic management interfaces use a numerical index as the primary key for ETH-CFM domains and associations. In model-driven interfaces, domains and associations use string names as keys. The domain and association can optionally be created without having to explicitly select and specify a numerical index in model-driven interfaces. In this case, SR OS assigns an index using the configured index range.

Platforms

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

Context

[Tree] (config>qos md-auto-id)

Full Context

configure qos md-auto-id

Description

This command automatically assigns numerical ID values for QoS policies in model-driven (MD) management interfaces.

Classic management interfaces use a numerical policy ID as the primary key for sap-ingress, sap-egress, and network QoS policies. In model-driven interfaces, SAP and network policies use string names as keys. The SAP and network policies can optionally be created in MD interfaces without having to explicitly select and specify a numerical policy ID. In this case, SR OS assigns an ID using the configured ID range.

Platforms

All

Context

[Tree] (config>filter md-auto-id)

Full Context

configure filter md-auto-id

Description

This command automatically assigns numerical ID values for filter policies in model-driven management interfaces.

Classic management interfaces use a numerical filter ID as the primary key for IP filters, IPv6 filters, and MAC filters. In model-driven interfaces, IP, IPv6, and MAC filters use string names as keys. The filters can optionally be created in MD interfaces without having to explicitly select and specify a numerical filter ID. In this case, SR OS assigns an ID using the configured ID range.

Platforms

All

Context

[Tree] (config>service md-auto-id)

Full Context

configure service md-auto-id

Description

This command automatically assigns numerical ID values for services, customers, and PW templates in model-driven (MD) management interfaces.

Classic management interfaces use a numerical service ID, customer ID, and PW template ID as the primary key for services, customers, and PW templates. In model-driven interfaces, services, customers, and PW templates use string names as keys. The services, customers, and PW templates can optionally be created in MD interfaces without having to explicitly select and specify a numerical ID. In this case, SR OS assigns an ID using the configured ID range.

Platforms

All

Context

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

Full Context

configure system management-interface cli md-cli

Description

Commands in this context configure the MD-CLI management interface.

Platforms

All

Context

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

Full Context

configure system security management-interface md-cli

Description

Commands in this context configure hash-control for the MD-CLI interface.

Platforms

All

Context

[Tree] (config>system>security>profile>grpc>rpc-authorization md-cli-session)

Full Context

configure system security profile grpc rpc-authorization md-cli-session

Description

This command configures the use of the MdCli Session RPC for the user profile.

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

Default

md-cli-session permit

Parameters

deny

Specifies that the use of MdCli Session RPC is denied.

permit

Specifies that the use of MdCli Session RPC is permitted.

Platforms

All

Context

[Tree] (config>eth-cfm>md-auto-id md-index-range)

Full Context

configure eth-cfm md-auto-id md-index-range

Description

This command specifies the range of indexes used by SR OS to automatically assign an index to ETH-CFM domains that are created in model-driven interfaces without an index explicitly specified by the user or client.

A domain created with an explicitly-specified index cannot use an index in this range. In classic CLI and SNMP, the ID range cannot be changed while objects exist inside the previous or new range. In MD interfaces, the range can be changed, which causes any previously existing objects in the previous ID range to be deleted and re-created using a new ID in the new range.

The no form of this command removes the range values.

See the md-auto-id command for further details.

Parameters

start md-index

Specifies the lower value of the index range. The value must be less than or equal to the end value.

Values

1 to 4294967295

end md-index

Specifies the upper value of the index range. The value must be greater than or equal to the start value.

Values

1 to 4294967295

Platforms

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

Context

[Tree] (config>system>security>management-interface>output-authorization md-interfaces)

Full Context

configure system security management-interface output-authorization md-interfaces

Description

This command controls output authorization of commands or RPCs for model-driven interfaces that display configuration or state.

When enabled, output authorization is performed for the following commands:

• MD-CLI info and compare commands

• NETCONF <get> and <get-config> RPCs

• gNMI Get RPC

When disabled, output authorization is not performed, which may significantly decrease the system response time by reducing command authorization requests, especially when remote AAA servers are used. Input to edit configuration is always authorized based on the AAA configuration.

By default, authorization checks are performed for configuration and state output.

The no form of this command disables authorization checks, allowing the output to be displayed immediately.

Default

md-interfaces

Platforms

All

Context

[Tree] (config>app-assure>group>http-enrich>field md5-salt)

Full Context

configure application-assurance group http-enrich field md5-salt

Description

This command configures an MD5 salt string. The configured string is appended to the parameter before performing MD5 hashing of the field.

The no form of this command removes the configuration of the MD5 salt string.

Default

no md5-salt

Parameters

string

Specifies the MD5 string, up to 16 characters.

Platforms

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

Context

[Tree] (config>isa>wlan-gw-group mda)

Full Context

configure isa wlan-gw-group mda

Description

This command enables an ISA for WLAN-GW functionality.

The no form of this command removes the ISA from the WLAN-GW configuration.

Parameters

mda-id

Indicates the IOM and MDA slot in format slot/mda.

Values

slot — 1 to 10

mda — 1 to 2

Platforms

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

Context

[Tree] (config>card mda)

Full Context

configure card mda

Description

This mandatory command enables access to a card’s MDA context. In SR OS, MDAs cover MDA and XMA.

Parameters

mda-slot

Specifies the MDA slot number to be configured. Slots are numbered 1 and 2. On vertically oriented slots, the top MDA slot is number 1, and the bottom MDA slot is number 2. On horizontally oriented slots, the left MDA is number 1, and the right MDA slot is number 2.

Values

1, 2

Platforms

All

Context

[Tree] (config>card>xiom mda)

Full Context

configure card xiom mda

Description

Configures an MDA-s in one of the slots of an XIOM.

Parameters

mda-slot

Specifies the MDA-s slot number.

Values

1 or 2

Platforms

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

Context

[Tree] (config>service>vpls>spoke-sdp>egress>mfib-allowed-mda-destinations mda)

[Tree] (config>service>vpls>mesh-sdp>egress>mfib-allowed-mda-destinations mda)

Full Context

configure service vpls spoke-sdp egress mfib-allowed-mda-destinations mda

configure service vpls mesh-sdp egress mfib-allowed-mda-destinations mda

Description

This command specifies an MFIB-allowed MDA destination for an SDP binding configured in the system.

Parameters

mda-id

Specifies an MFIB-allowed MDA destination

Values

slot/mda	slot: 1 to 10
	mda: 1, 2
slot/xiom/mda	slot: 1 to 10
	xiom: "x1” or "x2”
	mda: 1, 2

Platforms

All

Context

[Tree] (config>isa>tunnel-grp mda)

Full Context

configure isa tunnel-group mda

Description

This command specifies the MDA ID of the MS-ISA as the member of tunnel-group with multi-active enabled. Up to 16 MDA could be configured under the same tunnel-group.

Parameters

mda-id

Specifies the id of MS-ISA.

Values

iom-slot-id/mda-slot-id

Platforms

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

Context

[Tree] (config>isa>lns-group mda)

Full Context

configure isa lns-group mda

Description

This command configures an ISA LNS group MDA.

The no form of the command removes the MDA ID from the LNS group configuration.

Parameters

mda-id

Specifies the MDA identifier.

Values

mda-id:	slot/mda
	slot: 1 to 10
	mda: 1, 2

drain

Prevents new L2TP sessions being associated with the ISA. If an ISA is removed from the lns-group or if the lns-group be shutdown all associated L2TP sessions will be immediately terminated (and L2TP CDN messages sent to the L2TP peer). View show commands to determine which ISA is terminating which session (show router l2tp session).

Platforms

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

Context

[Tree] (config>isa>nat-group mda)

Full Context

configure isa nat-group mda

Description

This command configures an ISA NAT group MDA.

Parameters

mda-id

Specifies the MDA ID in the slot/mda format.

Values

slot: 1 to 10

mda: 1 to 16

Note:

Available parameter values may differ by platform.

Platforms

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

Context

[Tree] (config>service>pw-template>egress>mfib-mda mda)

Full Context

configure service pw-template egress mfib-allowed-mda-destinations mda

Description

This command specifies an MFIB-allowed media adapter destination for an SDP binding configured in the system.

Parameters

mda-id

Specifies an MFIB-allowed media adapters destination.

Values

1, 2

Platforms

All

Context

[Tree] (config>isa>tunnel-mem-pool mda)

Full Context

configure isa tunnel-member-pool mda

Description

This command configures an association between an MDA and the tunnel member pool.

The no form of this command removes the association between the MDA and the tunnel member pool.

Parameters

name

Specifies the name of the MDA, up to 32 characters.

Platforms

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

Context

[Tree] (config>card>mda mda-type)

Full Context

configure card mda mda-type

Description

This mandatory command provisions a specific MDA type to the device configuration for the slot. The MDA can be preprovisioned but an MDA must be provisioned before ports can be configured. Ports can be configured once the MDA is properly provisioned.

A maximum of two MDAs can be provisioned on an IOM or XCM. To modify an MDA slot, shut down all port associations.

XMAs are provisioned using MDA commands. A medium severity alarm is generated if an MDA is inserted that does not match the MDA type configured for the slot. This alarm is cleared when the correct MDA is inserted or the configuration is modified. A high severity alarm is raised when an administratively enabled MDA is removed from the chassis. This alarm is cleared if the either the correct MDA type is inserted or the configuration is modified. A low severity trap is issued if an MDA is removed that is administratively disabled.

An MDA can only be provisioned in a slot if the MDA type is allowed in the MDA slot. An error message is generated when an MDA is provisioned in a slot where it is not allowed.

Some MDA hardware can support two different firmware loads. One load includes the base Ethernet functionality, including 10G WAN mode, but does not include 1588 port-based timestamping. The second load includes the base Ethernet functionality and 1588 port-based timestamping, but does not include 10G WAN mode. These are identified as two MDA types that are the same, except for a "-ptp” suffix to indicate the second loadset; for example, x40-10gb-sfp and x40-10gb-sfp-ptp. A hard reset of the MDA occurs when switching between the two provisioned types.

A medium severity alarm is generated if an MDA is inserted that does not match the MDA type configured for the slot. This alarm is cleared when the correct MDA is inserted or the configuration is modified.

A high severity alarm is raised when an administratively enabled MDA is removed from the chassis. This alarm is cleared if the either the correct MDA type is inserted or the configuration is modified. A low severity trap is issued if an MDA is removed that is administratively disabled.

An alarm is raised if partial or complete MDA failure is detected. The alarm is cleared when the error condition ceases.

All parameters in the MDA context remain and if non-default values are required then their configuration remains as it is on all existing MDAs.

New generations of XMAs include variants controlled through hardware and software licensing. For these XMAs, the license level must be provisioned in addition to the MDA type. An XMA cannot become operational unless the provisioned license level matches the license level of the XMA installed into the slot. The set of license levels varies by MDA type.

The provisioned level controls aspects related to connector provisioning and the consumption of hardware egress queues and egress policers. Changes to the provisioned license level may be blocked if configuration that would not be permitted with the new target license level exists.

If the license level is not specified, the level is set to the highest license level for that XMA.

The no form of this command deletes the MDA from the configuration. The MDA must be administratively shut down before it can be deleted from the configuration.

Parameters

mda-type

Specifies the type of MDA selected for the slot position. Values for this attribute vary by platform and release. The release notes include a listing of all supported mda-types and their CLI strings. In addition, the command can be queried to check which mda-types are relevant for the active platform type. Some examples include me6-10gb-spf+ and x4-100g-cfp2.

mda-level

Specifies the MDA level. Possible values vary by MDA type.

Platforms

All

Context

[Tree] (config>card>xiom>mda mda-type)

Full Context

configure card xiom mda mda-type

Description

This command adds an MDA-s to the device configuration for the slot. The MDA-s type can be preprovisioned, which means that the MDA-s does not have to be installed in the chassis.

An MDA-s must be provisioned before a connector or a port can be configured.

An MDA-s can only be provisioned in a slot that is vacant. No other MDA-s can be provisioned (configured) for that particular slot. To reconfigure a slot position, use the no form of this command to remove the current information.

An MDA-s can only be provisioned in a slot if the MDA-s type is allowed in the slot. An error message is generated if an attempt is made to provision an MDA-s type that is not allowed.

If an MDA-s is inserted that does not match the configured MDA-s type for the slot, then a log event and a facility alarm are raised. The alarm is cleared when the correct MDA-s type is installed or the configuration is modified.

A log event and a facility alarm are raised if an administratively enabled MDA-s is removed from the chassis. The alarm is cleared when the correct MDA-s type is installed or the configuration is modified. A log event is issued when a MDA-s is removed that is administratively disabled.

The no form of this command removes the MDA-s from the configuration.

Parameters

mda-type

Specifies the type of MDA-s to be configured and installed in the slot. Values for this attribute vary by platform and release. The release notes include a listing of all supported mda-types and their CLI strings. In addition, the command can be queried to check which mda-types are relevant for the active platform type.

Platforms

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

Context

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

Full Context

configure port tdm ds3 mdl

Description

This command configures the maintenance data link (MDL) message for a DS-3/E-3.

This command is only applicable if the DS-3/E-3 is using C-bit framing (see the config>port>tdm>ds3 framing command).

The no form of this command removes the MDL string association and stops the transmission of any IDs.

Default

no mdl

Parameters

mdl-string

Specifies an MDL message up to 38 characters long on a DS-3.

eic

Specifies the equipment ID code up to 10 characters long.

lic

Specifies the equipment ID code up to 11 characters long.

fic

Specifies the ID code up to 10 characters long.

unit

Specifies the unit ID code up to 6 characters long.

pfi

Specifies the facility ID code up to 38 characters long.

port

Specifies the port ID code up to 38 characters long.

gen

Specifies the generator number to send in the MDL test signal message up to 38 characters long.

Platforms

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

Context

[Tree] (config>port>tdm>ds3 mdl-transmit)

Full Context

configure port tdm ds3 mdl-transmit

Description

This command enables the transmission of an MDL message on a DS-3/E-3 over channelized interface.

The no form of this command disables transmission of the specified message or all messages.

Default

no mdl-transmit

Parameters

path

Specifies the MDL path message.

idle-signal

Specifies the MDL idle signal message.

test-signal

Specifies the MDL test signal message.

Platforms

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

Context

[Tree] (config>service>vprn>mvpn>pt>selective>multistream-spmsi mdt-pim)

Full Context

configure service vprn mvpn provider-tunnel selective multistream-spmsi mdt-pim

Description

This command creates a multi-stream MDT that could match many (C-S,C-G)s into a single data MDT.

Parameters

group-ip-address

Specifies the group address of this data MDT, that is the provider group address.

Platforms

All

Context

[Tree] (config>service>vprn>mvpn mdt-type)

Full Context

configure service vprn mvpn mdt-type

Description

This command allows restricting MVPN instance per PE node to a specific role. By default, MVPN instance on a given PE node assumes the role of being a sender as well as receiver. This creates a mesh of MDT/PMSI across all PE nodes from this PE.

This command provides an option to configure either a sender-only or receiver-only mode per PE node. Restricting the role of a PE node prevents creating full mesh of MDT/PMSI across all PE nodes that are participating in MVPN instance.

auto-rp-discovery cannot be enabled together with mdt-type sender-only or mdt-type receiver-only, or wildcard-spmsi configurations.

The no version of this command restores the default (sender-receiver).

Default

mdt-type sender-receiver

Parameters

sender-receiver

Specifies MVPN has both sender and receivers connected to PE node.

sender-only

Specifies MVPN has only senders connected to PE node.

receiver-only

Specifies MVPN has only receivers connected to PE node.

Platforms

All

Context

[Tree] (config>oam-pm>session meas-interval)

Full Context

configure oam-pm session meas-interval

Description

This command establishes the parameters of the individual measurement intervals utilized by the session. Multiple measurement intervals may be specified within the session. A maximum of three different measurement intervals may be configured under each session.

The no form of this command deletes the specified measurement interval.

Parameters

meas-interval

Specifies the duration of the measurement interval.

Values

1-min, 5-mins, 15-mins, 1-hour, 1-day

create

Creates the measurement interval.

Platforms

All

Context

[Tree] (config>test-oam>link-meas measurement-template)