p Commands
p2mp
p2mp
Syntax
p2mp {enable | disable}
Context
[Tree] (config>router>ldp>session-params>peer>fec-type-capability p2mp)
Full Context
configure router ldp session-parameters peer fec-type-capability p2mp
Description
This command enables or disables P2MP FEC capability for the session.
Platforms
All
p2mp-candidate-path
p2mp-candidate-path
Syntax
[no] p2mp-candidate-path candidate-path-name
Context
[Tree] (config>router>p2mp-sr-tree>p2mp-policy p2mp-candidate-path)
Full Context
configure router p2mp-sr-tree p2mp-policy p2mp-candidate-path
Description
This command configures a candidate path in the P2MP policy entry for the P2MP SR tree.
A P2MP SR policy can contain multiple candidate paths, which are redundant trees. Each candidate path represents a P2MP SR tree with its own traffic engineering constraints. Each candidate path has its own preference; the candidate path with the highest preference is the active P2MP SR tunnel.
The no form of this command removes the specified candidate path from the P2MP SR policy.
Parameters
- candidate-path-name
Specifies the name of the candidate path, up to 32 characters.
Platforms
All
p2mp-id
p2mp-id
Syntax
p2mp-id id
Context
[Tree] (config>router>mpls>lsp p2mp-id)
Full Context
configure router mpls lsp p2mp-id
Description
This command configures the identifier of an RSVP P2MP LSP. An RSVP P2MP LSP is fully identified by the combination of: <P2MP ID, tunnel ID, extended tunnel ID> part of the P2MP session object, and <tunnel sender address, LSP ID> fields in the p2mp sender_template object.
The p2mp-id is a 32-bit identifier used in the session object that remains constant over the life of the P2MP tunnel. It is unique within the scope of the ingress LER.
The no form restores the default value of this parameter.
This command is not supported on the 7450 ESS.
Default
0
Parameters
- id
Specifies a P2MP identifier.
Platforms
All
p2mp-ipv4
p2mp-ipv4
Syntax
p2mp {enable | disable}
Context
[Tree] (config>router>ldp>if-params>if>ipv6>fec-type-capability p2mp-ipv4)
[Tree] (config>router>ldp>if-params>if>ipv4>fec-type-capability p2mp-ipv4)
[Tree] (config>router>ldp>session-params>peer>fec-cap p2mp-ipv4)
Full Context
configure router ldp interface-parameters interface ipv6 fec-type-capability p2mp-ipv4
configure router ldp interface-parameters interface ipv4 fec-type-capability p2mp-ipv4
configure router ldp session-parameters peer fec-type-capability p2mp-ipv4
Description
This command enables or disables IPv4 P2MP FEC capability on the interface.
The config>router>ldp>if-params>if>ipv6>fec-type-capability>p2mp-ipv4 command is not supported on the 7450 ESS.
Platforms
All
p2mp-ipv6
p2mp-ipv6
Syntax
p2mp {enable | disable}
Context
[Tree] (config>router>ldp>if-params>if>ipv6>fec-type-capability p2mp-ipv6)
[Tree] (config>router>ldp>session-params>peer>fec-cap p2mp-ipv6)
[Tree] (config>router>ldp>if-params>if>ipv4>fec-type-capability p2mp-ipv6)
Full Context
configure router ldp interface-parameters interface ipv6 fec-type-capability p2mp-ipv6
configure router ldp session-parameters peer fec-type-capability p2mp-ipv6-address
configure router ldp interface-parameters interface ipv4 fec-type-capability p2mp-ipv6
Description
This command enables or disables IPv6 P2MP FEC capability on the interface.
This command is not supported on the 7450 ESS.
Platforms
All
p2mp-ldp-tree-join
p2mp-ldp-tree-join
Syntax
p2mp-ldp-tree-join
p2mp-ldp-tree-join ipv4
p2mp-ldp-tree-join ipv6
p2mp-ldp-tree-join ipv4 ipv6
no p2mp-ldp-tree-join [ipv4] [ipv6]
Context
[Tree] (config>service>vprn>pim>if p2mp-ldp-tree-join)
Full Context
configure service vprn pim interface p2mp-ldp-tree-join
Description
This command configures the option to join P2MP LDP tree towards the multicast source for the VPRN service. If p2mp-ldp-tree-join is enabled, a PIM multicast join received on an interface is processed to join P2MP LDP LSP using the in-band signaled P2MP tree for the same multicast flow. LDP P2MP tree is setup towards the multicast source. Route to source of the multicast node is looked up from the RTM. The next-hop address for the route to source is set as the root of LDP P2MP tree.
The no form of command disables joining P2MP LDP tree for IPv4 or IPv6 or both (if both or none is specified).
Default
no p2mp-ldp-tree-join
Parameters
- ipv4
Enables dynamic mLDP in-band signaling for IPv4 PIM joins. IPv4 multicast must be enabled; see ipv4-multicast-disable. For backward compatibility p2mp-ldp-tree-join is equivalent to p2mp-ldp-tree-join ipv4.
- ipv6
Enables dynamic mLDP in-band signaling for IPv6 PIM joins. IPv6 multicast must be enabled; see ipv6-multicast-disable.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
p2mp-ldp-tree-join
Syntax
[no] p2mp-ldp-tree-join [ipv4] [ipv6]
Context
[Tree] (config>router>pim>interface p2mp-ldp-tree-join)
Full Context
configure router pim interface p2mp-ldp-tree-join
Description
This command configures the option to join the P2MP LDP tree towards the multicast source. If p2mp-ldp-tree-join is enabled, a PIM multicast join received on an interface is processed to join the P2MP LDP LSP, using the in-band signaled P2MP tree for the same multicast flow. LDP P2MP tree is set up towards the multicast source. The route to the multicast node source is looked up from the RTM. The next-hop address for the route to source is set as the root of LDP P2MP tree.
The no form of this command disables joining the P2MP LDP tree for IPv4 or IPv6 or for both (if both or none is specified).
Default
no p2mp-ldp-tree-join
Parameters
- ipv4
Enables dynamic MLDP in-band signaling for IPv4 PIM joins. IPv4 multicast must be enabled. For backward compatibility p2mp-ldp-tree-join is equivalent to p2mp-ldp-tree-join ipv4.
- ipv6
Enables dynamic MLDP in-band signaling for IPv6 PIM joins. IPv6 multicast must be enabled.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
p2mp-lsp-ping
p2mp-lsp-ping
Syntax
p2mp-lsp-ping lsp-name [p2mp-instance instance-name [s2l-dest-address ipv4-address [ipv4-address]]] [ttl label-ttl]
p2mp-lsp-ping ldp p2mp-identifier [vpn-recursive-fec] [ sender-addr ipv4-address] [leaf-addr ipv4-address [ipv4-address]]
p2mp-lsp-ping ldp-ssm source ip-address group ip-address [{router router-instance | service-name service-name}] [ sender-addr ipv4-address] [leaf-addr ipv4-address [ipv4-address]]
NOTE: Options common to all p2mp-lsp-ping cases: [ fc fc-name [profile {in | out}]] [size octets] [ timeout timeout] [detail]
Context
[Tree] (oam p2mp-lsp-ping)
Full Context
oam p2mp-lsp-ping
Description
This command performs an in-band connectivity test for an RSVP P2MP LSP. The echo request message is sent on the active P2MP instance and is replicated in the data path over all branches of the P2MP LSP instance. By default, all egress LER nodes that are leaves of the P2MP LSP instance replies to the echo request message.
LDP P2MP generic-identifier along with source IP address of the head-end node can be used to uniquely identify LDP P2MP LSP in a 7750 SR or 7950 XRS network. LDP p2mp-identifier is a mandatory parameter to test LSP ping. LDP P2MP identifier specified to configure a tunnel-interface on head-end node must be used as p2mp-identifier to test an LSP.
To reduce the scope of the echo reply messages, explicitly enter a list of addresses for the egress LER nodes that are required to reply. A maximum of five addresses can be specified in a single run of the p2mp-lsp-ping command. An LER node can parse the list of egress LER addresses and, if its address is included, it replies with an echo reply message.
The output of the command without the detail option provides a high-level summary of received error codes and success codes. The output of the command with the detail option shows a line for each replying node, as in the output of the LSP ping for a P2P LSP.
The display is delayed until all responses are received or the timer configured in the timeout parameter expires. No other CLI commands can be entered while waiting for the display. Entering A ^C aborts the ping operation. Note that p2mp-lsp-ping is not supported in a VPLS/B-VPLS PMSI context.
The timestamp format to be sent, and to be expected when received in a PDU, is as configured by the config>test-oam>mpls-time-stamp-format command. If RFC 4379 (obsoleted by RFC 8029) is selected, then the timestamp is in seconds and microseconds since 1900, otherwise it is in seconds and microseconds since 1970.
Parameters
- lsp-name
Specifies the name, up to 64 characters, that identifies an P2MP LSP to ping.
- instance-name
Specifies the name, up to 32 characters, of the specific instance of the P2MP LSP to send the echo request.
- s2l-dest-addr ipv4-address
Specifies up to five egress LER system addresses that are required to reply to the LSP ping echo request message.
- label-ttl
Specifies the TTL value for the MPLS label, expressed as a decimal integer.
- p2mp-identifier
Specifies the identifier for an LDP P2MP LSP to ping (applies to the 7750 SR and 7950 XRS only).
- vpn-recursive-fec
Adds a VPN recursive FEC element to the launched packet (useful for pinging a VPN BGP inter-AS Option B leaf). This parameter issues an OAM p2mp-lsp-ping with RFC 6512 VPN recursive opaque FEC type 8.
Refer to the "OAM” subsection of the LDP chapter in the 7450 ESS, 7750 SR, 7950 XRS, and VSR MPLS Guide for more information.
- sender-addr ipv4-address
Specifies any local IP sender address for mLDP (applies to the 7750 SR and 7950 XRS only).
- leaf-addr ipv4-address
Specifies up to five egress LER system addresses that are required to reply to LSP ping echo request message (applies to the 7750 SR and 7950 XRS only).
- ldp-ssm
Specifies a specific multicast stream to be tested when using dynamic multicast in mLDP. The source and group addresses correspond to the <S,G> being advertised by this mLDP FEC.
- fc-name
Specifies the fc and profile parameters used to indicate the forwarding class and profile of the MPLS echo request packet.
When an MPLS echo request packet is generated in CPM and is forwarded to the outgoing interface, the packet is queued in the egress network queue corresponding to the specified fc and profile parameter values. The marking of the packet's EXP is dictated by the LSP-EXP mappings on the outgoing interface.
When the MPLS echo request packet is received on the responding node, the fc and profile parameter values are dictated by the LSP-EXP mappings of the incoming interface.
When an MPLS echo reply packet is generated in CPM and is forwarded to the outgoing interface, the packet is queued in an egress network queue. The egress network queue is selected according to the fc and profile parameter values determined by the classification of the echo request packet that is being replied to at the incoming interface. The marking of the packet's EXP is dictated by the LSP-EXP mappings on the outgoing interface. The ToS byte is not modified. p2mp-lsp-ping Request Packet and Behavior summarizes this behavior.
Table 1. p2mp-lsp-ping Request Packet and Behavior Request Packet
Behavior
CPM (sender node)
Echo request packet:
packet {tos=1, fc1, profile1}
fc1 and profile1 are as entered by the user in the OAM command or default values
tos1 as per mapping of {fc1, profile1} to IP precedence in network egress QoS policy of outgoing interface
Outgoing interface (sender node)
Echo request packet:
packet queued as {fc1, profile1}
ToS field=tos1 not remarked
EXP=exp1, as per mapping of {fc1, profile1} to EXP in network egress QoS policy of outgoing interface
Incoming interface (responder node)
Echo request packet:
packet {tos1, exp1}
exp1 mapped to {fc2, profile2} as per classification in network QoS policy of incoming interface
CPM (responder node)
Echo reply packet:
packet {tos=1, fc2, profile2}
Outgoing interface (responder node)
Echo reply packet:
packet queued as {fc2, profile2}
ToS filed= tos1 not remarked (reply inband or out-of-band)
EXP=exp2, if reply is inband, remarked as per mapping of {fc2, profile2} to EXP in network egress QoS policy of outgoing interface
Incoming interface (sender node)
Echo reply packet:
packet {tos1, exp2}
exp2 mapped to {fc1, profile1} as per classification in network QoS policy of incoming interface
- profile {in | out}
Specifies the profile of the LSP ping echo request message.
- octets
Specifies the size in octets, expressed as a decimal integer, of the MPLS echo request packet, including the IP header but not the label stack. The request payload is padded with zeros to the specified size. Note that an OAM command is not failed if the user enters a size lower than the minimum required to build the packet for the echo request message. The payload is automatically padded to meet the minimum size.
- timeout
Specifies the time, in seconds, that is used to override the default timeout value and is the amount of time that the router waits for an echo reply message from all leaves of the P2MP LSP after sending the message request message. Upon the expiration of the message time out, the requesting router no longer waits for reply messages. Any echo reply message received after the request times out is silently discarded.
- detail
Displays P2MP LSP detailed information.
Platforms
All
p2mp-lsp-trace
p2mp-lsp-trace
Syntax
p2mp-lsp-trace lsp-name p2mp-instance instance-name s2l-dest-address ip-address [fc fc-name [profile {in | out}]] [size octets] [max-fail no-response-count] [probe-count probes-per-hop] [min-ttl min-label-ttl] [ max-ttl max-label-ttl] [timeout timeout] [interval interval] [detail]
Context
[Tree] (oam p2mp-lsp-trace)
Full Context
oam p2mp-lsp-trace
Description
This command discovers and displays the hop-by-hop path for a source-to-leaf (S2L) sub-LSP of an RSVP P2MP LSP.
The LSP trace capability allows the user to trace the path of a single S2L path of a P2MP LSP. Its operation is like p2mp-lsp-ping, but the sender of the echo reply request message includes the downstream mapping TLV to request the downstream branch information from a branch LSR or bud LSR. The branch LSR or bud LSR also includes the downstream mapping TLV to report the information about the downstream branches of the P2MP LSP. An egress LER does not include this TLV in the echo response message.
The parameter probe-count operates in the same way as in LSP Trace on a P2P LSP. It represents the maximum number of probes sent per TTL value before stops waiting for echo reply messages. If a response is received from the traced node before reaching maximum number of probes, then no more probes are sent for the same TTL. The sender of the echo request then increments the TTL and uses the information it received in the downstream mapping TLV to start sending probes to the node downstream of the last node which replied. This continues until the egress LER for the traced S2L path replies.
Like p2mp-lsp-ping, an LSP trace probe reports on all egress LER nodes that eventually receive the echo request message, but only the traced egress LER node replies to the last probe.
Any branch LSR node or bud LSR node in the P2MP LSP tree may receive a copy of the echo request message with the TTL in the outer label expiring at this node. However, only a branch LSR or bud LSR that has a downstream branch over which the traced egress LER is reachable responds.
When a branch LSR or bud LSR responds, it sets the global return code in the echo response message to RC=14 - "See DDMAP TLV for Return Code and Return Sub-Code” and the return code in the DDMAP TLV corresponding to the outgoing interface of the branch used by the traced S2L path to RC=8 - "Label switched at stack-depth <RSC>”. Note that p2mp-lsp-trace is not supported in a VPLS/B-VPLS PMSI context.
The timestamp format to be sent, and to be expected when received in a PDU, is as configured by the config>test-oam>mpls-time-stamp-format command. If RFC 4379 (obsoleted by RFC 8029) is selected, then the timestamp is in seconds and microseconds since 1900, otherwise it is in seconds and microseconds since 1970.
Parameters
- lsp-name
Specifies the name that identifies an P2MP LSP, up to 64 characters, to ping.
- instance-name
Specifies the name, up to 32 characters, of the specific instance of the P2MP LSP to send the echo request.
- ip-address
Specifies the egress LER system address of the S2L sub-LSP path which is being traced.
- fc-name
Specifies the fc and profile parameters are used to indicate the forwarding class and profile of the MPLS echo request packet.
When an MPLS echo request packet is generated in CPM and is forwarded to the outgoing interface, the packet is queued in the egress network queue corresponding to the specified FC and profile parameter values. The marking of the packet's EXP is dictated by the LSP-EXP mappings on the outgoing interface.
When the MPLS echo request packet is received on the responding node, the fc and profile parameter values are dictated by the LSP-EXP mappings of the incoming interface.
When an MPLS echo reply packet is generated in CPM and is forwarded to the outgoing interface, the packet is queued in an egress network queue. The egress network queue is selected according to the fc and profile parameter values determined by the classification of the echo request packet that is being replied to at the incoming interface. The marking of the packet's EXP is dictated by the LSP-EXP mappings on the outgoing interface. The ToS byte is not modified. p2mp-lsp-trace Request Packet and Behavior summarizes this behavior.
Table 2. p2mp-lsp-trace Request Packet and Behavior Request Packet
Behavior
CPM (sender node)
Echo request packet:
packet {tos=1, fc1, profile1}
fc1 and profile1 are as entered by user in OAM command or default values
tos1 as per mapping of {fc1, profile1} to IP precedence in network egress QoS policy of outgoing interface
Outgoing interface (sender node)
Echo request packet:
packet queued as {fc1, profile1}
ToS field=tos1 not remarked
EXP=exp1, as per mapping of {fc1, profile1} to EXP in network egress QoS policy of outgoing interface
Incoming interface (responder node)
Echo request packet:
packet {tos1, exp1}
exp1 mapped to {fc2, profile2} as per classification in network QoS policy of incoming interface
CPM (responder node)
Echo reply packet:
packet {tos=1, fc2, profile2}
Outgoing interface (responder node)
Echo reply packet:
packet queued as {fc2, profile2}
ToS filed= tos1 not remarked (reply inband or out-of-band)
EXP=exp2, if reply is inband, remarked as per mapping of {fc2, profile2} to EXP in network egress QoS policy of outgoing interface
Incoming interface (sender node)
Echo reply packet:
packet{tos1, exp2}
exp2 mapped to {fc1, profile1} as per classification in network QoS policy of incoming interface
- profile {in | out}
Specifies the profile of the LSP trace echo request message.
- octets
Specifies the size in octets, expressed as a decimal integer, of the MPLS echo request packet, including the IP header but not the label stack. The request payload is padded with zeros to the specified size. Note that an OAM command is not failed if the user enters a size lower than the minimum required to build the packet for the echo request message. The payload is automatically padded to meet the minimum size.
- no-response-count
Specifies the maximum number of consecutive MPLS echo requests, expressed as a decimal integer that do not receive a reply before the trace operation fails for a given TTL.
- probes-per-hop
Specifies the number of LSP trace echo request messages to send per TTL value.
- min-label-ttl
Specifies the minimum TTL value in the MPLS label for the LSP trace test, expressed as a decimal integer.
- max-label-ttl
Specifies the maximum TTL value in the MPLS label for the LSP trace test, expressed as a decimal integer.
- timeout
Specifies the time, in seconds, used to override the default timeout value and is the amount of time that the router waits for an echo reply message from all leaves of the P2MP LSP after sending the message request message. Upon the expiration of the message time out, the requesting router no longer waits for reply messages. Any echo reply message received after the request times out is silently discarded.
- interval
Specifies the time, in seconds, used to override the default echo request message send interval and defines the minimum amount of time that must expire before the next echo request message is sent.
If the interval is set to 1 second, and the timeout value is set to 10 seconds, then the maximum time between message requests is 10 seconds and the minimum is 1 second. This depends upon the receipt of an echo reply message corresponding to the outstanding message request.
Platforms
All
Output
The following is an example of p2mp-lsp-trace information.
Sample Output*A:Dut-C# oam p2mp-lsp-trace "p2mp_1" p2mp-instance "1" s2l-dest-address 10.20.1.
10.20.1.4 10.20.1.5 10.20.1.6
*A:Dut-C# oam p2mp-lsp-trace "p2mp_1" p2mp-instance "1" s2l-dest-
address 10.20.1.5 detail
P2MP LSP p2mp_1: 132 bytes MPLS payload
P2MP Instance 1, S2L Egress 10.20.1.5
1 10.20.1.1 rtt=3.78 ms rc=8(DSRtrMatchLabel)
DS 1: ipaddr 10.20.1.2 iftype 'ipv4Unnumbered' ifaddr 2 MRU=1500 label=131060
proto=4(RSVP-TE) B/E flags:0/0
2 10.20.1.2 rtt=3.54 ms rc=8(DSRtrMatchLabel)
DS 1: ipaddr 10.20.1.4 iftype 'ipv4Unnumbered' ifaddr 3 MRU=1500 label=131061
proto=4(RSVP-TE) B/E flags:0/0
3 10.20.1.5 rtt=5.30 ms rc=5(DSMappingMismatched)
Probe returned multiple responses. Result may be inconsistent.
*A:Dut-C#
p2mp-merge-point-abort-timer
p2mp-merge-point-abort-timer
Syntax
p2mp-merge-point-abort-timer seconds
no p2mp-merge-point-abort-timer
Context
[Tree] (config>router>rsvp p2mp-merge-point-abort-timer)
Full Context
configure router rsvp p2mp-merge-point-abort-timer
Description
This command specifies a configurable timer to abort Merge-Point (MP) node procedures for an S2L of a P2MP LSP instance. When a value higher than zero is configured for this timer, it will enter into effect anytime this node activates Merge-Point procedures for one or more P2MP LSP S2L paths. As soon an ingress interface goes operationally down, the Merge-Point node starts the abort timer. Upon expiry of the timer, MPLS will clean up all P2MP LSP S2L paths which ILM is on the failed interface and which have not already received a Path refresh over the bypass LSP.
The no form of this command disables the timer.
Default
no p2mp-merge-point-abort-timer
Parameters
- seconds
Specifies the length of the abort timer in seconds
Platforms
All
p2mp-policy
p2mp-policy
Syntax
[no] p2mp-policy policy-name
Context
[Tree] (config>router>p2mp-sr-tree p2mp-policy)
Full Context
configure router p2mp-sr-tree p2mp-policy
Description
This command creates a P2MP policy entry for the P2MP SR tree.
The no form of this command deletes the specified policy entry.
Parameters
- policy-name
Specifies the policy name, up to 32 characters.
Platforms
All
p2mp-policy
Syntax
[no] p2mp-policy
Context
[Tree] (config>service>vprn>mvpn>pt>selective>p2mp-sr p2mp-policy)
[Tree] (config>service>vprn>mvpn>pt>inclusive>p2mp-sr p2mp-policy)
[Tree] (config>service>vprn>mvpn>pt>selective>multistream-spmsi p2mp-policy)
Full Context
configure service vprn mvpn provider-tunnel selective p2mp-sr p2mp-policy
configure service vprn mvpn provider-tunnel inclusive p2mp-sr p2mp-policy
configure service vprn mvpn provider-tunnel selective multistream-spmsi p2mp-policy
Description
This command enables a P2MP policy for the MVPN provider tunnel.
The no form of this command disables the P2MP policy.
Platforms
All
p2mp-resignal-timer
p2mp-resignal-timer
Syntax
p2mp-resignal-timer minutes
no p2mp-resignal-timer
Context
[Tree] (config>router>mpls p2mp-resignal-timer)
Full Context
configure router mpls p2mp-resignal-timer
Description
This command configures the re-signal timer for a P2MP LSP instance. MPLS will request CSPF to re-compute the whole set of S2L paths of a given active P2MP instance each time the P2MP re-signal timer expires. The P2MP re-signal timer is configured separately from the P2P LSP parameter. MPLS performs a global MBB and moves each S2L sub-LSP in the instance into its new path using a new P2MP LSP ID if the global MBB is successful, regardless of the cost of the new S2L path.
This command is supported on the 7750 SR, 7950 XRS, and with VPLS only on the 7450 ESS.
The no form of this command disables the timer-based re-signaling of P2MP LSPs on this system.
Parameters
- minutes
Specifies the time MPLS waits before attempting to re-signal the P2MP LSP instance.
Platforms
All
p2mp-s2l-fast-retry
p2mp-s2l-fast-retry
Syntax
p2mp-s2-fast-retry seconds
no p2mp-s2l-fast-retry
Context
[Tree] (config>router>rsvp p2mp-s2l-fast-retry)
[Tree] (config>router>mpls p2mp-s2l-fast-retry)
Full Context
configure router rsvp p2mp-s2l-fast-retry
configure router mpls p2mp-s2l-fast-retry
Description
This command configures a global parameter to allow the user to apply a shorter retry timer for the first try after an active LSP path went down due to a local failure or the receipt of a ResvTear. This timer is used only in the first try. Subsequent retries will continue to be governed by the existing LSP level retry-timer.
The config>router>mpls>p2mp-s2l-fast-retry command is supported on the 7750 SR, 7950 XRS, and with VPLS only on the 7450 ESS.
The no form of this command disables the timer.
Default
no p2mp-s2l-fast-retry
Parameters
- seconds
Specifies the length of time for retry timer, in seconds
Platforms
All
p2mp-sr
p2mp-sr
Syntax
[no] p2mp-sr
Context
[Tree] (config>service>vprn>mvpn>pt>inclusive p2mp-sr)
[Tree] (config>service>vprn>mvpn>pt>selective p2mp-sr)
Full Context
configure service vprn mvpn provider-tunnel inclusive p2mp-sr
configure service vprn mvpn provider-tunnel selective p2mp-sr
Description
This command enables P2MP SR for the MVPN provider tunnel.
The no form of this command disables P2MP SR.
Default
no p2mp-sr
Platforms
All
p2mp-sr-tree
p2mp-sr-tree
Syntax
[no] p2mp-sr-tree
Context
[Tree] (config>router p2mp-sr-tree)
Full Context
configure router p2mp-sr-tree
Description
Commands in this context configure P2MP SR parameters.
Default
no p2mp-sr-tree
Platforms
All
p2mp-template-lsp
p2mp-template-lsp
Syntax
[no] p2mp-template-lsp rsvp-session-name SessionNameString sender sender-address
Context
[Tree] (config>router>mpls>ingress-stats p2mp-template-lsp)
Full Context
configure router mpls ingress-statistics p2mp-template-lsp
Description
This command configures an ingress statistics context matching on the RSVP session name for a RSVP P2MP LSP at the egress LER.
This command is supported on the 7750 SR, 7950 XRS, and with VPLS only on the 7450 ESS.
When the ingress LER signals the path of the S2L sub-LSP, it includes the name of the LSP and that of the path in the Session Name field of the Session Attribute object in the Path message. The encoding is as follows:
Session Name: <lsp-name::path-name>, where lsp-name component is encoded as follows:
P2MP LSP through the user configuration for L3 multicast in global routing instance: "LspNameFromConfig”
P2MP LSP as I-PMSI or S-PMSI in L3 mVPN: templateName-SvcId-mTTmIndex
P2MP LSP as I-PMSI in VPLS/B-VPLS: templateName-SvcId-mTTmIndex
The ingress statistics CLI configuration allows the user to match either on the exact name of the P2MP LSP as configured at the ingress LER or on a context that matches on the template name and the service-id as configured at the ingress LER.
When the matching is performed on a context, the user must enter the RSVP session name string in the format "templateName-svcId” to include the LSP template name as well as the mVPN VPLS/B-VPLS service ID as configured at the ingress LER. In this case, one or more P2MP LSP instances signaled by the same ingress LER could be associated with the ingress statistics configuration and the user is provided with CLI parameter max-stats to limit the maximum number of stat indices that can be assigned to this context. If the context matches more than this value, the additional request for stat indices from this context will be rejected. A background tasks monitors the ingress statistics templates which have one or more matching LSP instances with unassigned stat index and assigns one to them as they are freed.
Note the following rules when configuring an ingress statistics context based on template matching:
max-stats, once allocated, can be increased but not decreased unless the entire ingress statistics context matching a template name is deleted.
In order to delete ingress statistics context matching a template name, a shutdown is required.
An accounting policy cannot be configured or de-configured until the ingress statistics context matching a template name is shut down.
After deleting an accounting policy from an ingress statistics context matching a template name, the policy is not removed from the log until a "no shut” is performed on the ingress statistics context.
If there are no stat indices available at the time the session of the P2MP LSP matching a template context is signaled and the session state installed by the egress LER, no stats are allocated to the session.
Furthermore, the assignment of stat indices to the LSP names that match the context will also be not deterministic. The latter is due to the fact that a stat index is assigned and released following the dynamics of the LSP creation or deletion by the ingress LER. For example, a multicast stream crosses the rate threshold and is moved to a newly signaled S-PMSI dedicated to this stream. Later on, the same steam crosses the threshold downwards and is moved back to the shared I-PMSI and the P2MP LSP corresponding to the S-PMSI is deleted by the ingress LER.
The no form deletes the ingress statistics context matching on the RSVP session name.
Parameters
- rsvp-session-name SessionNameString
Specifies the name of the RSVP P2MP session in the format of "templateName-svcId”. This field can hold up to 64 characters.
- sender sender-address
Specifies a string of 15 characters representing the IP address of the ingress LER for the LSP.
Platforms
All
p2p-active-path-fast-retry
p2p-active-path-fast-retry
Syntax
p2p-active-path-fast-retry seconds
no p2p-active-path-fast-retry
Context
[Tree] (config>router>mpls p2p-active-path-fast-retry)
Full Context
configure router mpls p2p-active-path-fast-retry
Description
This command configures a global parameter to allow the user to apply a shorter retry timer for the first try after an active LSP path went down due to a local failure or the receipt of a ResvTear. This timer is used only in the first try. Subsequent retries will continue to be governed by the existing LSP level retry-timer.
The no form of this command disables the timer.
Default
no p2p-active-path-fast-retry
Parameters
- seconds
Specifies the length of time for retry timer, in seconds
Platforms
All
p2p-merge-point-abort-timer
p2p-merge-point-abort-timer
Syntax
p2p-merge-point-abort-timer seconds
no p2p-merge-point-abort-timer
Context
[Tree] (config>router>rsvp p2p-merge-point-abort-timer)
Full Context
configure router rsvp p2p-merge-point-abort-timer
Description
This command configures a timer to abort Merge-Point (MP) node procedures for a P2P LSP path. When a value higher than zero is configured for this timer, it will enter into effect anytime this node activates Merge-Point procedures for one or more P2P LSP paths. As soon an ingress interface goes operationally down, the Merge-Point node starts the abort timer. Upon expiry of the timer, MPLS will clean up all P2P LSP paths which ILM is on the failed interface and which have not already received a Path refresh over the bypass LSP.
The no form of this command disables the timer.
Default
no p2p-merge-point-abort-timer
Parameters
- seconds
Specifies the length of the abort timer in seconds
Platforms
All
p2p-template-lsp
p2p-template-lsp
Syntax
[no] p2p-template-lsp rsvp-session-name SessionNameString sender sender-address
Context
[Tree] (config>router>mpls>ingress-stats p2p-template-lsp)
Full Context
configure router mpls ingress-statistics p2p-template-lsp
Description
This command configures an ingress statistics context matching on the RSVP session name for a RSVP P2P auto-LSP at the egress LER.
When the ingress LER signals the path of a template based one-hop-p2p or mesh-p2p auto-lsp, it includes the name of the LSP and that of the path in the Session Name field of the Session Attribute object in the Path message. The encoding is as follows:
Session Name: lsp-name::path-name, where lsp-name component is encoded as follows:
P2MP LSP through the user configuration for Layer 3 multicast in global routing instance: "LspNameFromConfig”
P2MP LSP as I-PMSI or S-PMSI in L3 mVPN: templateName-SvcId-mTTmIndex
P2MP LSP as I-PMSI in VPLS/B-VPLS: templateName-SvcId-mTTmIndex.
The ingress statistics CLI configuration allows the user to match either on the exact name of the P2P auto-LSP or on a context that matches on the template name and the destination of the LSP at the ingress LER.
When the matching is performed on a context, the user must enter the RSVP session name string in the format "templateName-svcId” to include the LSP template name as well as the mVPN VPLS/B-VPLS service ID as configured at the ingress LER. In this case, one or more P2MP LSP instances signaled by the same ingress LER could be associated with the ingress statistics configuration. In this case, the user is provided with CLI parameter max-stats to limit the maximum number of stat indices which can be assigned to this context. If the context matches more than this value, the additional request for stat indices from this context will be rejected.
Note the following rules when configuring an ingress statistics context based on template matching:
max-stats, once allocated, can be increased but not decreased unless the entire ingress statistics context matching a template name is deleted.
In order to delete ingress statistics context matching a template name, a shutdown is required.
An accounting policy cannot be configured or de-configured until the ingress statistics context matching a template name is shut down.
After deleting an accounting policy from an ingress statistics context matching a template name, the policy is not removed from the log until a no shut is performed on the ingress statistics context.
If there are no stat indices available at the time the session of the P2P LSP matching a template context is signaled and the session state installed by the egress LER, no stats are allocated to the session.
Furthermore, the assignment of stat indices to the LSP names that match the context will also be not deterministic. The latter is due to the fact that a stat index is assigned and released following the dynamics of the LSP creation or deletion by the ingress LER. For example, a multicast stream crosses the rate threshold and is moved to a newly signaled S-PMSI dedicated to this stream. Later on, the same steam crosses the threshold downwards and is moved back to the shared I-PMSI and the P2MP LSP corresponding to the S-PMSI is deleted by the ingress LER.
The no form deletes the ingress statistics context matching on the RSVP session name.
Parameters
- rsvp-session-name SessionNameString
Specifies the name of the RSVP P2MP session in the format of "templateName-svcId”. This field can hold up to 64 characters.
- sender sender-address
Specifies a string of 15 characters representing the IP address of the ingress LER for the LSP.
Platforms
All
packet
packet
Syntax
packet detail-level {high | low}
packet mode {all | dropped}
no packet
Context
[Tree] (debug>gtp packet)
Full Context
debug gtp packet
Description
This command enables debugging of GTP packets sent or received by the system’s control plane.
The no form of this command disables debugging of GTP packets.
Parameters
- detail-level {high | low}
Specifies how much detail is to be displayed when debugging a GTP packet.
- mode {all | dropped}
Specifies which packets is debugged.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
packet
Syntax
[no] packet
Context
[Tree] (debug>router>l2tp packet)
[Tree] (debug>router>l2tp>assignment-id packet)
[Tree] (debug>router>l2tp>group packet)
[Tree] (debug>router>l2tp>peer packet)
Full Context
debug router l2tp packet
debug router l2tp assignment-id packet
debug router l2tp group packet
debug router l2tp peer packet
Description
This command enables packet debugging.
The no form of this command disables packet debugging.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
packet
Syntax
[no] packet
Context
[Tree] (debug>service>id>ppp packet)
Full Context
debug service id ppp packet
Description
This command enables debugging for specific PPPoE packets.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
packet
packet
Syntax
packet jitter-buffer milliseconds [payload-size bytes]
packet payload-size bytes
no packet
Context
[Tree] (config>service>cpipe>sap>cem packet)
[Tree] (config>service>epipe>sap>cem packet)
Full Context
configure service cpipe sap cem packet
configure service epipe sap cem packet
Description
This command specifies the jitter buffer size, in milliseconds, and payload size, in bytes.
Default
The default value depends on the CEM SAP endpoint type, and if applicable, the number of timeslots as shown in Packet CEM SAP Endpoint Types.
Endpoint Type |
Timeslots |
Default Jitter Buffer (in ms) |
---|---|---|
unstructuredE1 |
— |
5 |
unstructuredT1 |
— |
5 |
nxDS0 (E1/T1) |
— |
32 |
N = 1 |
16 |
|
N = 2 to 4 |
8 |
|
N = 5 to 15 |
5 |
|
nxDS0WithCas (E1) |
N |
8 |
nxDS0WithCas (T1) |
N |
12 |
Parameters
- milliseconds
Specifies the jitter buffer size in milliseconds (ms).
Configuring the payload size and jitter buffer to values that result in less than 2 packet buffers or greater than 32 packet buffers is not allowed. Setting the jitter butter value to 0 sets it back to the default value.
- payload-size bytes
Specifies the payload size (in bytes) of packets transmitted to the packet service network (PSN) by the CEM SAP. This determines the size of the data that will be transmitted over the service. If the size of the data received is not consistent with the payload size then the packet is considered malformed.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
- configure service cpipe sap cem packet
7450 ESS, 7750 SR-7/12/12e, 7750 SR-a, 7750 SR-e
- configure service epipe sap cem packet
packet
Syntax
packet [hello | jp]
packet [hello | jp] evpn-mpls
packet [hello | jp] [ sap sap-id]
packet [hello | jp] [ sdp sdp-id:vc-id]
packet [hello | jp] vxlan vtep ip-address vni vni-id
no packet
Context
[Tree] (debug>service>id>pim-snooping packet)
Full Context
debug service id pim-snooping packet
Description
This command enables or disables debugging for PIM packets.
Parameters
- hello | jp
PIM packet types
- sap-id
Debugs packets associated with the specified SAP
- sdp-id:vc-id
Debugs packets associated with the specified SDP
- evpn-mpls
Debugs PIM snooping statistics for EVPN-MPLS destinations
Platforms
All
packet
Syntax
packet [query | v1-report | v2-report | v3-report | v2-leave] [ip-int-name | ip-address] [ mode {dropped-only | ingr-and-dropped | egr-ingr-and-dropped}]
packet [query | v1-report | v2-report | v3-report | v2-leave] [mode { dropped-only | ingr-and-dropped | egr-ingr-and-dropped}] group-interface ip-int-name
packet [query | v1-report | v2-report | v3-report | v2-leave] host ip-address [mode {dropped-only | ingr-and-dropped | egr-ingr-and-dropped}]
no packet [query | v1-report | v2-report | v3-report | v2-leave] [ip-int-name | ip-address]
no packet [query | v1-report | v2-report | v3-report | v2-leave] group-interface ip-int-name
no packet [query | v1-report | v2-report | v3-report | v2-leave] host ip-address
Context
[Tree] (debug>router>igmp packet)
Full Context
debug router igmp packet
Description
This command enables/disables debugging for IGMP packets.
Parameters
- query
Specifies to log the IGMP group- and source-specific queries transmitted and received on this interface.
- v1-report
Specifies to debug IGMP V1 reports transmitted and received on this interface.
- v2-report
Specifies to debug IGMP V2 reports transmitted and received on this interface.
- v3-report
Specifies to debug IGMP V3 reports transmitted and received on this interface.
- v2-leave
Specifies to debug the IGMP Leaves transmitted and received on this interface.
- ip-int-name
Debugs the information associated with the specified IP interface name.
- ip-address
Debugs the information associated with the specified IP address.
Platforms
All
packet
Syntax
[no] packet
Context
[Tree] (debug>router>gmpls packet)
Full Context
debug router gmpls packet
Description
This command enables and disables debugging for specific GMPLS packets.
Platforms
7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
packet
Syntax
packet [detail]
no packet
Context
[Tree] (debug>router>ldp>if packet)
[Tree] (debug>router>ldp>peer packet)
Full Context
debug router ldp interface packet
debug router ldp peer packet
Description
This command enables debugging for specific LDP packets.
The no form of the command disables the debugging output.
Parameters
- detail
Displays detailed information.
Platforms
All
packet
Syntax
[no] packet
Context
[Tree] (debug>router>rsvp packet)
Full Context
debug router rsvp packet
Description
Commands in this context debug packets.
Platforms
All
packet
Syntax
packet [pkt-type] [peer ip-address]
Context
[Tree] (debug>router>msdp packet)
Full Context
debug router msdp packet
Description
This command enables debugging for Multicast Source Discovery Protocol (MSDP) packets.
The no form of the command disables MSDP packet debugging.
Parameters
- pkt-type
Debugs information associated with the specified packet type.
- ip-address
Debugs information associated with the specified peer IP address.
Platforms
All
packet
Syntax
packet [hello | register | register-stop | jp | bsr | assert | crp | mdt-tlv | auto-rp-announcement | auto-rp-mapping | graft | graft-ack] [ip-int-name | mt-int-name | int-ip-address | mpls-if-name] [family {ipv4 | ipv6}] [ send | receive]
no packet
Context
[Tree] (debug>router>pim packet)
Full Context
debug router pim packet
Description
This command enables debugging for PIM packets.
The no form of this command disables debugging for PIM packets.
Parameters
- hello | register | register-stop | jp | bsr | assert | crp | mdt-tlv | auto-rp-announcement | auto-rp-mapping | graft | graft-ack
Specifies PIM packet types.
- ip-int-name
Debugs the information associated with the specified IP interface name, up to 32 characters.
- mt-int-name
Debugs the information associated with the specified VPRN ID and group address.
- int-ip-address
Debugs the information associated with the specified IP address.
- ipv4
Specifies to display IPv4 packets.
- ipv6
Specifies to display IPv6 packets.
- mpls-if-name
Debugs the information associated with the specified MPLS interface.
- receive
Specifies to display received packets.
- send
Specifies to display sent packets.
- family
Debugs database packet information.
Platforms
All
packet
Syntax
packet jitter-buffer milliseconds [payload-size bytes]
packet payload-size bytes
no packet
Context
[Tree] (config>mirror>mirror-dest>sap>cem packet)
Full Context
configure mirror mirror-dest sap cem packet
Description
This command specifies the jitter buffer size, in milliseconds, and payload size, in bytes.
Default
The default value depends on the CEM SAP endpoint type, and if applicable, the number of timeslots:
Endpoint Type |
Timeslots |
Default Jitter Buffer (in ms) |
---|---|---|
unstructuredE1 |
n/a |
5 |
unstructuredT1 |
n/a |
5 |
unstructuredE3 |
n/a |
5 |
unstructuredT3 |
n/a |
5 |
nxDS0 (E1/T1) |
N = 1 |
32 |
N = 2 to 4 |
16 |
|
N = 5 to 15 |
8 |
|
N >= 16 |
5 |
|
nxDS0WithCas (E1) |
N |
8 |
nxDS0WithCas (T1) |
N |
12 |
Parameters
- milliseconds
Specifies the jitter buffer size in milliseconds (ms).
Configuring the payload size and jitter buffer to values that result in less than 2 packet buffers or greater than 32 packet buffers is not allowed.
Setting the jitter butter value to 0 sets it back to the default value.
- bytes
Specifies the payload size (in bytes) of packets transmitted to the packet service network (PSN) by the CEM SAP. This determines the size of the data that will be transmitted over the service. If the size of the data received is not consistent with the payload size then the packet is considered malformed.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
packet
Syntax
packet packet-number [create]
no packet packet-number
Context
[Tree] (debug>oam>build-packet packet)
Full Context
debug oam build-packet packet
Description
This command configures a packet to be launched by the OAM find-egress tool.
The no form of this command removes the packet number value.
Parameters
- packet-number
Specifies a packet to be launched by the OAM find-egress tool.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
packet
Syntax
packet all
packet cfm-opcode opcode [opcode]
no packet
Context
[Tree] (debug>eth-cfm>mip packet)
[Tree] (debug>eth-cfm>mep packet)
Full Context
debug eth-cfm mip packet
debug eth-cfm mep packet
Description
This command defines the ETH-CFM opcodes of interest to be debugged.
The no form of this command stops packet debugging and the collection of PDUs.
Parameters
- all
Specifies that debugging is enabled for all ETH-CFM packets.
- opcode
Specifies a standard numerical reference or common three-letter acronym (TLA) that identifies the CFM PDU type. Up to five opcodes can be specified, and a combination of both numbers and TLAs can be used.
MEPs support all opcodes.
MIPs support 2 (LBR), 3 (LBM), 4 (LTR), and 5 (LTM).
Unknown or unsupported opcodes in TLA form are rejected. The applicable numerical opcode can be used instead. When numerical references are used, they are converted to a known TLA or left in numerical form if the TLA is unknown.
Re-entering the packet command overwrites the previous opcode entries for the MEP or MIP.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
packet
Syntax
packet [{ip-int-name | ip-address}] [headers] [ protocol-id]
no packet [{ip-int-name | ip-address}]
Context
[Tree] (debug>router>ip packet)
Full Context
debug router ip packet
Description
This command enables debugging for IP packets.
Parameters
- ip-int-name
Only displays the interface information associated with the specified IP interface name.
- ip-address
Only displays the interface information associated with the specified IP address.
- headers
Only displays information associated with the packet header.
- protocol-id
Specifies the decimal value representing the IP protocol to debug. Well-known protocol numbers include ICMP(1), TCP(6), UDP(17). The no form the command removes the protocol from the criteria.
Platforms
All
packet
Syntax
[no] packet
Context
[Tree] (debug>router>pcp>pcp-server packet)
Full Context
debug router pcp pcp-server packet
Description
This command enables packet debugging.
The no form of this command disables packet debugging.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
packet
Syntax
[no] packet [{query | request | response}]
Context
[Tree] (debug>router>mtrace packet)
Full Context
debug router mtrace packet
Description
This command enables debugging for mtrace packets.
Platforms
All
packet
Syntax
[no] packet [{query | request | reply}]
Context
[Tree] (debug>router>mtrace2 packet)
Full Context
debug router mtrace2 packet
Description
This command enables debugging for mtrace2 packets.
Platforms
All
packet
Syntax
[no] packet
Context
[Tree] (debug>router>rpki-session packet)
Full Context
debug router rpki-session packet
Description
This command enables debugging for specific RPKI packets.
The no form of this command disables debugging for specific RPKI packets.
Platforms
All
packet
Syntax
packet [packet-type] [ip-int-name | ip-address] [ detail]
Context
[Tree] (debug>router>isis packet)
Full Context
debug router isis packet
Description
This command enables debugging for IS-IS packets.
The no form of the command disables debugging.
Parameters
- ip-address
When specified, only packets with the specified interface address are debugged.
- ip-int-name
When specified, only packets with the specified interface name are debugged.
- packet-type
When specified, only packets of the specified type are debugged.
- detail
All output is displayed in the detailed format.
Platforms
All
packet
Syntax
packet [packet-type] [interface-name] [ingress | egress] [detail]
packet [packet-type] [interface-name] [ingress | egress | drop] [ detail]
no packet
Context
[Tree] (debug>router>ospf packet)
[Tree] (debug>router>ospf3 packet)
Full Context
debug router ospf packet
debug router ospf3 packet
Description
This command enables debugging for OSPF packets.
Parameters
- packet-type
Specifies the OSPF packet type to debug.
- interface-name
Specifies the interface to debug, up to 32 characters.
- ingress
Specifies to display ingress packets.
- egress
Specifies to display egress packets.
- drop
Specifies to display dropped packets.
Platforms
All
packet
Syntax
packet [high-detail] [dropped-only]
no packet
Context
[Tree] (debug>subscr-mgmt>pfcp packet)
Full Context
debug subscriber-mgmt pfcp packet
Description
This command debugs PFCP packets that are received or sent. The no form of this command disables any PFCP packet debugging.
Parameters
- high-detail
Specifies to provide a full packet dump; without this parameter only basic packet information is provided.
- dropped-only
Specifies to only debug dropped packets.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
packet-byte-offset
packet-byte-offset
Syntax
packet-byte-offset {add bytes | subtract bytes}
no packet-byte-offset
Context
[Tree] (config>subscr-mgmt>sla-prof>egress>qos>policer packet-byte-offset)
[Tree] (config>subscr-mgmt>sla-prof>ingress>qos>policer packet-byte-offset)
Full Context
configure subscriber-mgmt sla-profile egress qos policer packet-byte-offset
configure subscriber-mgmt sla-profile ingress qos policer packet-byte-offset
Description
This command is used to modify the size of each packet handled by the policer by adding or subtracting a number of bytes. The actual packet size is not modified; only the size used to determine the bucket depth impact is changed. The packet-byte-offset command is meant to be an arbitrary mechanism the can be used to either add downstream frame encapsulation or remove portions of packet headers. Both the policing metering and profiling throughput is affected by the offset as well as the stats associated with the policer.
When child policers are adding to or subtracting from the size of each packet, the parent policer’s min-thresh-separation value should also need to be modified by the same amount.
The policer’s packet-byte-offset defined in the QoS policy may be overridden on an sla-profile or SAP where the policy is applied. Packet byte offset settings are not included in the applied rate when (queue) frame based accounting is configured and the policer is managed by HQoS, however the offsets are applied to the statistics.
The no form of this command removes the per packet size modifications from the policer.
Parameters
- add bytes
Specifies the packet byte offset. The add keyword is mutually exclusive to the subtract keyword. Either add or subtract must be specified. When add is defined the corresponding bytes parameter specifies the number of bytes that is added to the size each packet associated with the policer for rate metering, profiling and accounting purposes. From the policer’s perspective, the maximum packet size is increased by the amount being added to the size of each packet.
- subtract bytes
Specifies the packet byte offset. The subtract keyword is mutually exclusive to the add keyword. Either add or subtract must be specified. When b is defined the corresponding bytes parameter specifies the number of bytes that is subtracted from the size of each packet associated with the policer for rate metering, profiling and accounting purposes. From the policer’s perspective, the maximum packet size is reduced by the amount being subtracted from the size of each packet.
Note:The minimum resulting packet size used by the system is 1 byte.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
packet-byte-offset
Syntax
packet-byte-offset {add add-bytes | subtract sub-bytes}
no packet-byte-offset
Context
[Tree] (config>card>fp>ingress>access>qgrp>policer-over>plcr packet-byte-offset)
[Tree] (config>card>fp>ingress>network>qgrp>policer-over>plcr packet-byte-offset)
Full Context
configure card fp ingress access queue-group policer-override policer packet-byte-offset
configure card fp ingress network queue-group policer-override policer packet-byte-offset
Description
This command modifies the size of each packet handled by the policer by adding or subtracting a number of bytes. The actual packet size is not modified; only the size used to determine the bucket depth impact is changed. The packet-byte-offset command is meant to be an arbitrary mechanism the can be used to either add downstream frame encapsulation or remove portions of packet headers. Both the policing metering and profiling throughput is affected by the offset as well as the stats associated with the policer.
When child policers are adding to or subtracting from the size of each packet, the parent policer’s min-thresh-separation value should also need to be modified by the same amount.
The policer’s packet-byte-offset 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 removes per packet size modifications from the policer.
Parameters
- add-bytes
The add keyword is mutually exclusive to the subtract keyword. Either add or subtract must be specified. When add is defined the corresponding bytes parameter specifies the number of bytes that is added to the size each packet associated with the policer for rate metering, profiling and accounting purposes. From the policer’s perspective, the maximum packet size is increased by the amount being added to the size of each packet.
- sub-bytes
The subtract keyword is mutually exclusive to the add keyword. Either add or subtract must be specified. When b is defined the corresponding bytes parameter specifies the number of bytes that is subtracted from the size of each packet associated with the policer for rate metering, profiling and accounting purposes. From the policer’s perspective, the maximum packet size is reduced by the amount being subtracted from the size of each packet. Note that the minimum resulting packet size used by the system is 1 byte.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
packet-byte-offset
Syntax
packet-byte-offset {add add-bytes | subtract sub-bytes}
no packet-byte-offset
Context
[Tree] (config>service>epipe>sap>ingress>policer-over>plcr packet-byte-offset)
[Tree] (config>service>cpipe>sap>ingress>policer-over>plcr packet-byte-offset)
[Tree] (config>service>epipe>sap>egress>policer-over>plcr packet-byte-offset)
[Tree] (config>service>fpipe>sap>ingress>policer-over>plcr packet-byte-offset)
[Tree] (config>service>apipe>sap>egress>policer-over>plcr packet-byte-offset)
[Tree] (config>service>ipipe>sap>egress>policer-over>plcr packet-byte-offset)
[Tree] (config>service>fpipe>sap>egress>policer-over>plcr packet-byte-offset)
[Tree] (config>service>ipipe>sap>ingress>policer-over>plcr packet-byte-offset)
[Tree] (config>service>cpipe>sap>egress>policer-over>plcr packet-byte-offset)
[Tree] (config>service>apipe>sap>ingress>policer-over>plcr packet-byte-offset)
Full Context
configure service epipe sap ingress policer-override policer packet-byte-offset
configure service cpipe sap ingress policer-override policer packet-byte-offset
configure service epipe sap egress policer-override policer packet-byte-offset
configure service fpipe sap ingress policer-override policer packet-byte-offset
configure service apipe sap egress policer-override policer packet-byte-offset
configure service ipipe sap egress policer-override policer packet-byte-offset
configure service fpipe sap egress policer-override policer packet-byte-offset
configure service ipipe sap ingress policer-override policer packet-byte-offset
configure service cpipe sap egress policer-override policer packet-byte-offset
configure service apipe sap ingress policer-override policer packet-byte-offset
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 packet-byte-offset parameter for the specified policer-id. Packet byte offset settings are not included in the applied rate when (queue) frame based accounting is configured; however, the offsets are applied to the statistics.
The no packet-byte-offset command is used to restore the policer’s packet-byte-offset setting to the policy defined value.
Default
no packet-byte-offset
Parameters
- add-bytes
Specifies the number of bytes that are added to the size each packet associated with the policer for rate metering, profiling and accounting purposes. From the policer’s perspective, the maximum packet size is increased by the amount being added to the size of each packet.
- sub-bytes
Specifies the number of bytes that are subtracted from the size of each packet associated with the policer for rate metering, profiling and accounting purposes. From the policer’s perspective, the maximum packet size is reduced by the amount being subtracted from the size of each packet.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
- configure service ipipe sap egress policer-override policer packet-byte-offset
- configure service epipe sap egress policer-override policer packet-byte-offset
- configure service epipe sap ingress policer-override policer packet-byte-offset
- configure service ipipe sap ingress policer-override policer packet-byte-offset
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS
- configure service fpipe sap ingress policer-override policer packet-byte-offset
- configure service cpipe sap ingress policer-override policer packet-byte-offset
- configure service fpipe sap egress policer-override policer packet-byte-offset
- configure service cpipe sap egress policer-override policer packet-byte-offset
7450 ESS, 7750 SR-7/12/12e, 7750 SR-e, 7950 XRS
- configure service apipe sap ingress policer-override policer packet-byte-offset
- configure service apipe sap egress policer-override policer packet-byte-offset
packet-byte-offset
Syntax
packet-byte-offset {add add-bytes | subtract sub-bytes}
no packet-byte-offset
Context
[Tree] (config>service>vpls>sap>ingress>policer-override>plcr packet-byte-offset)
[Tree] (config>service>vpls>sap>egress>policer-override>plcr packet-byte-offset)
Full Context
configure service vpls sap ingress policer-override policer packet-byte-offset
configure service vpls sap egress policer-override policer packet-byte-offset
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 packet-byte-offset parameter for the specified policer-id. Packet byte offset settings are not included in the applied rate when (queue) frame based accounting is configured, however the offsets are applied to the statistics.
The no form of this command restores the policer’s packet-byte-offset setting to the policy defined value.
Default
no packet-byte-offset
Parameters
- add-bytes
The add keyword is mutually exclusive to the subtract keyword. Either add or subtract must be specified. When add is defined the corresponding bytes parameter specifies the number of bytes that is added to the size each packet associated with the policer for rate metering, profiling and accounting purposes. From the policer’s perspective, the maximum packet size is increased by the amount being added to the size of each packet.
- sub-bytes
The subtract keyword is mutually exclusive to the add keyword. Either add or subtract must be specified. When subtract is defined the corresponding bytes parameter specifies the number of bytes that is subtracted from the size of each packet associated with the policer for rate metering, profiling and accounting purposes. From the policer’s perspective, the maximum packet size is reduced by the amount being subtracted from the size of each packet.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
packet-byte-offset
Syntax
packet-byte-offset {add add-bytes | subtract sub-bytes}
no packet-byte-offset
Context
[Tree] (config>service>ies>if>sap>ingress>policer-override>plcr packet-byte-offset)
[Tree] (config>service>ies>if>sap>egress>policer-override>plcr packet-byte-offset)
Full Context
configure service ies interface sap ingress policer-override policer packet-byte-offset
configure service ies interface sap egress policer-override policer packet-byte-offset
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 packet-byte-offset parameter for the specified policer-id. Packet byte offset settings are not included in the applied rate when (queue) frame based accounting is configured, however the offsets are applied to the statistics.
The no form of this command restores the policer’s packet-byte-offset setting to the policy defined value.
Default
no packet-byte-offset
Parameters
- add add-bytes
The add keyword is mutually exclusive to the subtract keyword. Either add or subtract must be specified. When add is defined, the corresponding bytes parameter specifies the number of bytes that is added to the size each packet associated with the policer for rate metering, profiling and accounting purposes. From the policer’s perspective, the maximum packet size is increased by the amount being added to the size of each packet.
- subtract sub-bytes
The subtract keyword is mutually exclusive to the add keyword. Either add or subtract must be specified. When subtract is defined, the corresponding bytes parameter specifies the number of bytes that is subtracted from the size of each packet associated with the policer for rate metering, profiling and accounting purposes. From the policer’s perspective, the maximum packet size is reduced by the amount being subtracted from the size of each packet.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
packet-byte-offset
Syntax
packet-byte-offset add add-bytes
packet-byte-offset subtract sub-bytes
no packet-byte-offset
Context
[Tree] (config>service>vprn>if>sap>egress>policer-override>plcr packet-byte-offset)
[Tree] (config>service>vprn>if>sap>ingress>policer-override>plcr packet-byte-offset)
Full Context
configure service vprn interface sap egress policer-override policer packet-byte-offset
configure service vprn interface sap ingress policer-override policer packet-byte-offset
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 packet-byte-offset parameter for the specified policer-id. Packet byte offset settings are not included in the applied rate when (queue) frame based accounting is configured, however the offsets are applied to the statistics.
The no form of this command restores the policer’s packet-byte-offset setting to the policy defined value.
Default
no packet-byte-offset
Parameters
- add add-bytes
The add keyword is mutually exclusive to the subtract keyword. Either add or subtract must be specified. When add is defined, the corresponding bytes parameter specifies the number of bytes that is added to the size each packet associated with the policer for rate metering, profiling and accounting purposes. From the policer’s perspective, the maximum packet size is increased by the amount being added to the size of each packet.
- subtract sub-bytes
The subtract keyword is mutually exclusive to the add keyword. Either add or subtract must be specified. When subtract is defined, the corresponding bytes parameter specifies the number of bytes that is subtracted from the size of each packet associated with the policer for rate metering, profiling and accounting purposes. From the policer’s perspective, the maximum packet size is reduced by the amount being subtracted from the size of each packet.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
packet-byte-offset
Syntax
packet-byte-offset {add add-bytes | subtract sub- bytes}
no packet-byte-offset
Context
[Tree] (config>qos>sap-ingress>dyn-policer packet-byte-offset)
[Tree] (config>qos>sap-egress>dyn-policer packet-byte-offset)
[Tree] (config>qos>sap-ingress>policer packet-byte-offset)
[Tree] (config>qos>sap-egress>policer packet-byte-offset)
Full Context
configure qos sap-ingress dynamic-policer packet-byte-offset
configure qos sap-egress dynamic-policer packet-byte-offset
configure qos sap-ingress policer packet-byte-offset
configure qos sap-egress policer packet-byte-offset
Description
This command is used to modify the size of each packet handled by the policer by adding or subtracting a number of bytes. The actual packet size is not modified; only the size used to determine the bucket depth impact is changed. The packet-byte-offset command is meant to be an arbitrary mechanism that can be used to either add downstream frame encapsulation or remove portions of packet headers. Both the policing metering and profiling throughput is affected by the offset as well as the stats associated with the policer.
When child policers are adding to or subtracting from the size of each packet, the parent policer’s min-thresh-separation value should also need to be modified by the same amount.
The policer’s packet-byte-offset defined in the QoS policy may be overridden on an sla-profile or SAP where the policy is applied. Packet byte offset settings are not included in the applied rate when (queue) frame-based accounting is configured and the policer is managed by HQoS; however, the offsets are applied to the statistics.
The no form of this command is used to remove per packet size modifications from the policer.
Parameters
- add add-bytes
The add keyword is mutually exclusive to the subtract keyword. Either add or subtract must be specified. When add is defined, the corresponding bytes parameter specifies the number of bytes that is added to the size of each packet associated with the policer for rate metering, profiling, and accounting purposes. From the policer’s perspective, the maximum packet size is increased by the amount being added to the size of each packet.
- subtract sub-bytes
The subtract keyword is mutually exclusive to the add keyword. Either add or subtract must be specified. When subtract is defined, the corresponding bytes parameter specifies the number of bytes that is subtracted from the size of each packet associated with the policer for rate metering, profiling, and accounting purposes. From the policer’s perspective, the maximum packet size is reduced by the amount being subtracted from the size of each packet. The minimum resulting packet size used by the system is 1 byte.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
- configure qos sap-egress dynamic-policer packet-byte-offset
- configure qos sap-ingress dynamic-policer packet-byte-offset
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
- configure qos sap-egress policer packet-byte-offset
- configure qos sap-ingress policer packet-byte-offset
packet-byte-offset
Syntax
packet-byte-offset {add add-bytes | subtract sub-bytes}
no packet-byte-offset
Context
[Tree] (config>qos>sap-ingress>queue packet-byte-offset)
Full Context
configure qos sap-ingress queue packet-byte-offset
Description
This command modifies the size of each packet handled by the queue by adding or subtracting the specified number of bytes. The actual packet size is not modified, only the size used to determine the ingress scheduling and profiling is changed. The packet-byte-offset command is an arbitrary mechanism that can be used to either add downstream frame encapsulation or remove portions of packet headers. Both the scheduling and profiling throughput is affected by the offset as well as the statistics (accounting) associated with the queue. The packet-byte-offset does not apply to drop statistics, received valid statistics, or the offered managed and unmanaged statistics used by Ingress Multicast Path Management.
The no form of this command removes per-packet size modifications from the queue.
Parameters
- add-bytes
Specifies the number of bytes added to the size of each packet associated with the queue for scheduling, profiling, and accounting purposes. From the queue’s perspective, the packet size is increased by the amount specified.
- sub-bytes
Specifies the number of bytes subtracted from the size of each packet associated with the queue for scheduling, profiling, and accounting purposes. From the queue’s perspective, the packet size is reduced by the amount specified. The minimum resulting packet size used by the system is 1 byte.
Platforms
All
packet-byte-offset
Syntax
packet-byte-offset {add add-bytes | subtract sub-bytes}
no packet-byte-offset
Context
[Tree] (config>qos>sap-egress>queue packet-byte-offset)
Full Context
configure qos sap-egress queue packet-byte-offset
Description
This command is used to modify the size of each packet handled by the queue by adding or subtracting a number of bytes. The actual packet size is not modified; only the size used to determine the bucket depth impact is changed.
The packet-byte-offset command is meant to be an arbitrary mechanism the can be used to either add downstream frame encapsulation or remove portions of packet headers.
When a packet-byte-offset value is applied to a queue instance, it adjusts the immediate packet size. This means that the queue rates, i.e., operational PIR and CIR, and queue bucket updates use the adjusted packet size. In addition, the queue statistics will also reflect the adjusted packet size. Scheduler policy rates, which are data rates, will use the adjusted packet size.
The port scheduler max-rate and the priority level rates and weights, if a Weighted Scheduler Group is used, are always on-the-wire rates and thus use the actual frame size. The same applies for the agg-rate-limit on a SAP, a subscriber, or a multiservice Site (MSS) when the queue is port-parented.
When the user enables frame-based-accounting in a scheduler policy or queue-frame-based-accounting with agg-rate-limit in a port scheduler policy, the queue rate will be capped to a user-configured on-the-wire rate and the packet-byte-offset is not included. However, the offsets are applied to the statistics.
The no form of this command is used to remove per packet size modifications from the queue.
Parameters
- add-bytes
The add keyword is mutually exclusive to the subtract keyword. Either parameter must be specified. When add is defined, the corresponding bytes parameter specifies the number of bytes that is added to the size of each packet associated with the queue for scheduling and accounting purposes.
- sub-bytes
The subtract keyword is mutually exclusive to the add keyword. Either parameter must be specified. When subtract is defined, the corresponding bytes parameter specifies the number of bytes that is subtracted from the size of each packet associated with the queue for scheduling and accounting purposes. The minimum resulting packet size used by the system is 1 byte.
Platforms
All
packet-byte-offset
Syntax
packet-byte-offset {add add-bytes | subtract sub-bytes}
no packet-byte-offset
Context
[Tree] (config>qos>qgrps>ing>qgrp>policer packet-byte-offset)
Full Context
configure qos queue-group-templates ingress queue-group policer packet-byte-offset
Description
This command configures a packet byte offset for the QoS ingress queue-group policer.
Default
no packet-byte-offset
Parameters
- add-bytes
Specifies the number of bytes to add as the offset amount.
- sub-bytes
Specifies the number of bytes to add as the offset amount.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
packet-byte-offset
Syntax
packet-byte-offset {add add-bytes | subtract sub-bytes}
no packet-byte-offset
Context
[Tree] (config>qos>qgrps>ing>qgrp>queue packet-byte-offset)
Full Context
configure qos queue-group-templates ingress queue-group queue packet-byte-offset
Description
This command is used to modify the size of each packet handled by the queue by adding or subtracting a number of bytes. The actual packet size is not modified; only the size used to determine the ingress scheduling and profiling is changed. The packet-byte-offset command is meant to be an arbitrary mechanism that can be used to either add downstream frame encapsulation or remove portions of packet headers. Both the scheduling and profiling throughput is affected by the offset as well as the stats (accounting) associated with the queue. The packet-byte-offset does not apply to drop statistics, received valid statistics, or the offered managed and unmanaged statistics used by Ingress Multicast Path Management.
The no form of this command is used to remove per packet size modifications from the queue.
Parameters
- add-bytes
The add keyword is mutually exclusive to the subtract keyword. Either add or subtract must be specified. When add is defined, the corresponding bytes parameter specifies the number of bytes that is added to the size each packet associated with the queue for scheduling, profiling and accounting purposes. From the queue’s perspective, the packet size is increased by the amount being added to the size of each packet.
- sub-bytes
The subtract keyword is mutually exclusive to the add keyword. Either add or subtract must be specified. When subtract is defined, the corresponding bytes parameter specifies the number of bytes that is subtracted from the size of each packet associated with the queue for scheduling, profiling and accounting purposes. From the queue’s perspective, the packet size is reduced by the amount being subtracted from the size of each packet. The minimum resulting packet size used by the system is 1 byte.
Platforms
All
packet-byte-offset
Syntax
packet-byte-offset {add add-bytes | subtract sub-bytes}
no packet-byte-offset
Context
[Tree] (config>qos>qgrps>egr>qgrp>policer packet-byte-offset)
[Tree] (config>qos>qgrps>egr>qgrp>queue packet-byte-offset)
Full Context
configure qos queue-group-templates egress queue-group policer packet-byte-offset
configure qos queue-group-templates egress queue-group queue packet-byte-offset
Description
This command is used to modify the size of each packet handled by the queue by adding or subtracting a number of bytes. The actual packet size is not modified; only the size used to determine the bucket depth impact is changed.
The packet-byte-offset command is meant to be an arbitrary mechanism that can be used to either add downstream frame encapsulation or remove portions of packet headers.
When a packet-byte-offset value is applied to a queue or policer instance, it adjusts the immediate packet size. This means that the queue rates (i.e., operational PIR and CIR) and policer or queue bucket updates use the adjusted packet size. In addition, the statistics will also reflect the adjusted packet size. Scheduler policy rates, which are data rates, will use the adjusted packet size.
The port scheduler max-rate and the priority level rates and weights, if a Weighted Scheduler Group is used, are always on-the-wire rates and thus use the actual frame size. The same applies for the agg-rate-limit on a SAP, a subscriber, or a Multiservice Site (MSS) when the queue is port-parented.
When the user enables frame-based-accounting in a scheduler policy or queue-frame-based-accounting with agg-rate-limit in a port scheduler policy, the policer or queue rate will be capped to a user-configured on-the-wire rate and the packet-byte-offset is not included; however, the offsets are applied to the statistics.
The no form of this command is used to remove per packet size modifications from the queue.
Parameters
- add-bytes
Specifies that the corresponding bytes parameter specifies the number of bytes that is added to the size of each packet associated with the queue for scheduling and accounting purposes.
- sub-bytes
Specifies that the corresponding bytes parameter specifies the number of bytes that is subtracted from the size of each packet associated with the queue for scheduling and accounting purposes. The minimum resulting packet size used by the system is 1 byte.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
- configure qos queue-group-templates egress queue-group policer packet-byte-offset
All
- configure qos queue-group-templates egress queue-group queue packet-byte-offset
packet-length
packet-length
Syntax
packet-length {lt | gt | eq} packet-length-value
packet-length range packet-length-value packet-length-value
no packet-length
Context
[Tree] (config>filter>ip-filter>entry>match packet-length)
Full Context
configure filter ip-filter entry match packet-length
Description
This command configures the IPv4 packet length value match criterion. The IPv4 packet length represents the total packet length including the IPv4 header and the payload.
Default
no packet-length
Parameters
- lt
Specifies "less than”. The lt parameter cannot be used with the lowest possible numerical value for the parameter.
- gt
Specifies "greater than”. The gt parameter cannot be used with the highest possible numerical value for the parameter.
- eq
Specifies "equal to”.
- packet-length-value
Specifies the packet length value.
- range
Specifies an inclusive range. When range is used, the beginning of the range must have a value less than the second value of the range.
Platforms
All
packet-length
Syntax
packet-length {lt | gt | eq} packet-length-value
packet-length range packet-length-value packet-length-value
no packet-length
Context
[Tree] (config>filter>ipv6-filter>entry>match packet-length)
Full Context
configure filter ipv6-filter entry match packet-length
Description
This command configures the IPv6 packet length value match criterion. The IPv6 packet length represents the total packet length including the IPv6 header and the payload.
Default
no packet-length
Parameters
- lt
Specifies "less than”. The lt parameter cannot be used with the lowest possible numerical value for the parameter.
- gt
Specifies "greater than”. The gt parameter cannot be used with the highest possible numerical value for the parameter.
- eq
Specifies "equal to”.
- packet-length-value
Specifies the packet length value.
- range
Specifies an inclusive range. When range is used, the beginning of the range must have a value less than the second value of the range.
Platforms
All
packet-rate-high-wmark
packet-rate-high-wmark
Syntax
packet-rate-high-wmark high-watermark
Context
[Tree] (config>app-assure packet-rate-high-wmark)
Full Context
configure application-assurance packet-rate-high-wmark
Description
This command configures the packet rate on the ISA-AA when a packet rate alarm will be raised by the agent.
Default
packet-rate-high-wmark max
Parameters
- high-watermark
Specifies the high watermark for packet rate alarms. The value must be larger than or equal to the packet-rate-low-wmark low-watermark value.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
packet-rate-low-wmark
packet-rate-low-wmark
Syntax
packet-rate-low-wmark low-watermark
no packet-rate-low-wmark
Context
[Tree] (config>app-assure packet-rate-low-wmark)
Full Context
configure application-assurance packet-rate-low-wmark
Description
This command configures the packet rate on the ISA-AA when a packet rate alarm will be cleared by the agent.
The no form of this command reverts to the default.
Default
packet-rate-low-wmark 0
Parameters
- low-watermark
Specifies the low watermark for packet rate alarms. The value must be lower than or equal to the packet-rate-high-wmark high-watermark value.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
packet-rx
packet-rx
Syntax
packet-rx [client client-ip [ source-port src-port]] [fcc-join] [fcc-leave] [ret-nack]
no packet-rx
Context
[Tree] (debug>service>id>video-interface packet-rx)
Full Context
debug service id video-interface packet-rx
Description
This command enables debugging of received RTCP messages. The options for this command allow the user to filter only certain types of messages to appear in the debug traces.
Parameters
- client client-ip
Specifies the client IP address.
- source-port src-port
Specifies the source port.
- fcc-join
Enables debugging for FCC joins.
- fcc-leave
Enables debugging for FCC leaves.
- ret-nack
Enables debugging for retransmission nack packets.
Platforms
7450 ESS, 7750 SR-1, 7750 SR-7/12/12e, 7750 SR-1s, 7750 SR-2s, 7750 SR-7s, 7750 SR-14s
packet-sanity
packet-sanity
Syntax
packet-sanity direction direction [create]
no packet-sanity direction direction
Context
[Tree] (config>app-assure>group>statistics>tca>sctp-filter packet-sanity)
Full Context
configure application-assurance group statistics threshold-crossing-alert sctp-filter packet-sanity
Description
This command configures a TCA for the counter capturing packet sanity hits for the specified SCTP filter. A packet sanity TCA can be created for traffic generated from the subscriber side of AA ( from-sub) or for traffic generated from the network toward the AA subscriber (to-sub). The create keyword is mandatory when creating a TCA.
Parameters
- direction
Specifies the traffic direction.
- create
Keyword used to create the TCA.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
packet-size
packet-size
Syntax
packet-size bytes
no packet-size
Context
[Tree] (config>system>snmp packet-size)
Full Context
configure system snmp packet-size
Description
This command configures the maximum SNMP packet size generated by this node.
The no form of this command restores the default value.
Default
packet-size 1500
Parameters
- bytes
Specifies the SNMP packet size in bytes.
Platforms
All
packet-too-big
packet-too-big
Syntax
packet-too-big [number seconds]
no packet-too-big
Context
[Tree] (config>service>ies>if>ipv6>icmp6 packet-too-big)
Full Context
configure service ies interface ipv6 icmp6 packet-too-big
Description
This command specifies whether packet-too-big ICMP messages should be sent. When enabled, ICMPv6 packet-too-big messages are generated by this interface.
The no form of this command disables the sending of ICMPv6 packet-too-big messages.
Default
packet-too-big 100 10
Parameters
- number
Specifies the number of ICMP messages that are too large to send in the time frame specified by the seconds parameter.
- seconds
Specifies the time frame, in seconds, that is used to limit the number of "packet-too-big” ICMP messages issued.
Platforms
All
packet-too-big
Syntax
packet-too-big [number seconds]
no packet-too-big
Context
[Tree] (config>service>vprn>if>ipv6>icmp6 packet-too-big)
Full Context
configure service vprn interface ipv6 icmp6 packet-too-big
Description
This command configures the rate for Internet Control Message Protocol version 6 (ICMPv6) packet-too-big messages.
Parameters
- number
Specifies the number of packet-too-big messages to send in the time frame specified by the seconds parameter.
- seconds
Specifies the time frame, in seconds, that is used to limit the number of packet-too-big messages issued.
Platforms
All
packet-too-big
Syntax
packet-too-big
packet-too-big number [10..1000] seconds [ 1..60]
no packet-too-big
Context
[Tree] (config>service>vprn>if>sap>ip-tunnel>icmp6-gen packet-too-big)
Full Context
configure service vprn interface sap ip-tunnel icmp6-generation packet-too-big
Description
This command enables the system to send ICMPv6 PTB (Packet Too Big) messages on the private side and optionally specifies the rate.
With this command configured, the system sends PTB back if it received an IPv6 packet on the private side that is bigger than 1280 bytes and also exceeds the private MTU of the tunnel.
The ip-mtu command (under ipsec-tunnel or tunnel-template) specifies the private MTU for the ipsec-tunnel or dynamic tunnel.
The no form of this command reverts interval and message-count values to their default values.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
packet-too-big
Syntax
packet-too-big [number seconds]
no packet-too-big
Context
[Tree] (config>router>if>ipv6>icmp6 packet-too-big)
Full Context
configure router interface ipv6 icmp6 packet-too-big
Description
This command configures the rate for ICMPv6 packet-too-big messages.
Parameters
- number
Limits the number of packet-too-big messages issued per time frame specified in the seconds parameter.
- seconds
Determines the time frame, in seconds, that is used to limit the number of packet-too-big messages issued per time frame.
Platforms
All
packet-tx
packet-tx
Syntax
packet-tx [group grp-addr [ source srcAddr]] [ret-nack]
no packet-tx
Context
[Tree] (debug>service>id>video-interface packet-tx)
Full Context
debug service id video-interface packet-tx
Description
This command enables debugging transmitted RTCP packets.
Parameters
- client client-ip
Specifies the client IP address.
- source src-srcAddr
Specifies the source port’s IP address.
Platforms
7450 ESS, 7750 SR-1, 7750 SR-7/12/12e, 7750 SR-1s, 7750 SR-2s, 7750 SR-7s, 7750 SR-14s
packet-type
packet-type
Syntax
packet-type [authentication] [accounting] [ coa]
no packet-type
Context
[Tree] (debug>router>radius packet-type)
Full Context
debug router radius packet-type
Description
This command specifies the RADIUS packet type filter of command debug router radius.
Default
authentication accounting coa
Parameters
- authentication
Specifies the RADIUS authentication packet.
- accounting
Specifies the RADIUS accounting packet.
- coa
Specifies the RADIUS change of authorization packet.
Platforms
All
packets
packets
Syntax
[no] packets [interface ip-int-name]
Context
[Tree] (debug>router>srrp packets)
Full Context
debug router srrp packets
Description
This command enables debugging for SRRP packets.
The no form of this command disables debugging.
Platforms
All
packets
Syntax
[no] packets
[no] packets interface ip-int-name [vrid virtual-router-id]
[no] packets interface ip-int-name vrid virtual-router-id ipv6
Context
[Tree] (debug>router>vrrp packets)
Full Context
debug router vrrp packets
Description
This command enables or disables debugging for VRRP packets.
Parameters
- ip-int-name
Specifies the interface name, up to 32 characters.
- virtual-router-id
Specifies the router ID.
- ipv6
Debugs the specified IPv6 VRRP interface.
Platforms
All
packets
Syntax
packets [neighbor ip-address | group name]
no packets
Context
[Tree] (debug>router>bgp packets)
Full Context
debug router bgp packets
Description
This command decodes and logs all sent and received BGP packets in the debug log.
The no form of this command disables debugging.
Parameters
- neighbor ip-address
Debugs only events affecting the specified BGP neighbor.
- group name
Debugs only events affecting the specified peer group name, up to 64 characters, and associated neighbors.
Platforms
All
packets
Syntax
packets [station station-name]
no packets
Context
[Tree] (debug>router>bmp packets)
Full Context
debug router bmp packets
Description
This command enables debugging for all BMP packets.
The no form of the command disables debugging for all BMP packets.
Parameters
- station-name
Specifies the station name of the BMP monitoring station, up to 32 characters.
Platforms
All
packets
Syntax
[no] packets [neighbor ip-int-name | ip-addr]
Context
[Tree] (debug>router>rip packets)
Full Context
debug router rip packets
Description
This command enables debugging for RIP packets.
Parameters
- ip-int-name | ip-address
Debugs the RIP packets sent on the neighbor IP address or interface.
Platforms
All
packets
Syntax
[no] packets [neighbor ip-int-name | ipv6-address]
Context
[Tree] (debug>router>ripng packets)
Full Context
debug router ripng packets
Description
This command enables debugging for RIPng packets.
Parameters
- ip-int-name| ipv6-address
Debugs the RIPng packets sent on the neighbor IP address or interface.
Platforms
All
packets-admitted-count
packets-admitted-count
Syntax
[no] packets-admitted-count
Context
[Tree] (config>log>acct-policy>cr>aa>aa-to-sub-cntr packets-admitted-count)
[Tree] (config>log>acct-policy>cr>aa>aa-from-sub-cntr packets-admitted-count)
Full Context
configure log accounting-policy custom-record aa-specific to-aa-sub-counters packets-admitted-count
configure log accounting-policy custom-record aa-specific from-aa-sub-counters packets-admitted-count
Description
This command includes the admitted packet count in the AA subscriber's custom record and only applies to the 7750 SR.
The no form of this command excludes the admitted packet count.
Default
no packets-admitted-count
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
packets-denied-count
packets-denied-count
Syntax
[no] packets-denied-count
Context
[Tree] (config>log>acct-policy>cr>aa>aa-to-sub-cntr packets-denied-count)
[Tree] (config>log>acct-policy>cr>aa>aa-from-sub-cntr packets-denied-count)
Full Context
configure log accounting-policy custom-record aa-specific to-aa-sub-counters packets-denied-count
configure log accounting-policy custom-record aa-specific from-aa-sub-counters packets-denied-count
Description
This command includes the denied packet count in the AA subscriber's custom record and only applies to the 7750 SR.
The no form of this command excludes the denied packet count.
Default
no packets-denied-count
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
pad-size
pad-size
Syntax
pad-size octets
no pad-size
Context
[Tree] (config>oam-pm>session>ip>twamp-light pad-size)
Full Context
configure oam-pm session ip twamp-light pad-size
Description
This command defines the amount by which the TWAMP Light packet is padded. TWAMP session controller packets are 27 bytes smaller than TWAMP session reflector packets. If symmetrical packet sizes in the forward and backward direction are required, the pad size must be configured to a minimum of 27 bytes.
The no form of this command removes all padding.
Default
pad-size 0
Parameters
- octets
Specifies the value, in octets, to pad the TWAMP Light packet.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
pad-tlv-size
pad-tlv-size
Syntax
pad-tlv-size octets
no pad-tlv-size
Context
[Tree] (config>oam-pm>session>mpls>dm pad-tlv-size)
Full Context
configure oam-pm session mpls dm pad-tlv-size
Description
This command allows the operator to add an optional Pad TLV to PDU and increase the frame on the wire by the specified amount. Note that this command only configures the size of the padding added to the PDU, and does not configure the total size of the frame on the wire. Since the bit count for the length is a maximum of 255 (8bits) the maximum pad per pad-tlv is between 0, 2 and 257 (type 1B, Length 1B, Length 255). Only a single pad-tlv can be added.
The no form of this command removes the optional TLV.
Parameters
- octets
Specifies the overall length of the pad-tlv.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
pad-tlv-size
Syntax
pad-tlv-size octets
Context
[Tree] (config>test-oam>link-meas>template>twl pad-tlv-size)
Full Context
configure test-oam link-measurement measurement-template twamp-light pad-tlv-size
Description
This command configures an optional pad TLV size that allows a STAMP PDU to include the PAD TLV. This increases the size of the STAMP PDU by the size of the added TLV. The PAD TLV includes an all zeros pattern.
Parameters
- octets
Specifies the length of the pad-tlv.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
padding-size
padding-size
Syntax
padding-size padding-size
no padding-size
Context
[Tree] (config>service>vprn>static-route-entry>next-hop>cpe-check padding-size)
[Tree] (config>service>vprn>static-route-entry>indirect>cpe-check padding-size)
Full Context
configure service vprn static-route-entry next-hop cpe-check padding-size
configure service vprn static-route-entry indirect cpe-check padding-size
Description
This optional parameter specifies the amount of padding to add to the ICMP packet in bytes. The parameter is only applicable when the cpe-check option is used with the associated static route.
Default
padding-size 56
Parameters
- padding-size
An integer value.
Platforms
All
padding-size
Syntax
padding-size padding-size
no padding-size
Context
[Tree] (config>router>static-route-entry>indirect>cpe-check padding-size)
[Tree] (config>router>static-route-entry>next-hop>cpe-check padding-size)
Full Context
configure router static-route-entry indirect cpe-check padding-size
configure router static-route-entry next-hop cpe-check padding-size
Description
This command specifies the amount of padding to add to the ICMP packet in bytes. The parameter is only applicable when the cpe-check option is used with the associated static route.
Default
padding-size 56
Parameters
- padding-size
Specifies the integer value.
Platforms
All
padding-size
Syntax
padding-size size
no padding-size
Context
[Tree] (config>vrrp>priority-event>host-unreachable padding-size)
Full Context
configure vrrp priority-event host-unreachable padding-size
Description
This command allows the operator to increase the size of IP packet by padding the PDU.
The no form of the command reverts to the default.
Default
padding-size 0
Parameters
- size
Specifies amount of increase to the ICMP PDU.
padi-auth-policy
padi-auth-policy
Syntax
padi-auth-policy policy-name
no padi-auth-policy
Context
[Tree] (config>subscr-mgmt>loc-user-db>ppp>host padi-auth-policy)
Full Context
configure subscriber-mgmt local-user-db ppp host padi-auth-policy
Description
This command configures the PADI authentication policy of this host.
Parameters
- policy-name
Specifies the authentication policy name, up to 32 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
pado-ac-name
pado-ac-name
Syntax
pado-ac-name name
no pado-ac-name
Context
[Tree] (config>subscr-mgmt>ppp-policy pado-ac-name)
Full Context
configure subscriber-mgmt ppp-policy pado-ac-name
Description
This command configures the Access Concentrator name that is used in the PPPoE PADO message.
By default, the system name or if not configured, the chassis Serial Number is used.
Parameters
- name
Specifies the string up to 128 characters to be used as AC name in the PPPoE PADO message.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
pado-delay
pado-delay
Syntax
pado-delay deci-seconds
no pado-delay
Context
[Tree] (config>subscr-mgmt>loc-user-db>ppp>host pado-delay)
Full Context
configure subscriber-mgmt local-user-db ppp host pado-delay
Description
This command configures the delay timeout before sending a PPPoE Active Discovery Offer (PADO).
Parameters
- deci-seconds
Specifies the delay timeout before sending a PADO.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
pado-delay
Syntax
pado-delay deci-seconds
no pado-delay
Context
[Tree] (config>subscr-mgmt>ppp-policy pado-delay)
Full Context
configure subscriber-mgmt ppp-policy pado-delay
Description
This command configures the delay timeout before sending a PPP Active Discovery Offer (PADO) packet.
Parameters
- deci-seconds
Specifies the delay timeout before sending a PADO.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
pairing-button
pairing-button
Syntax
pairing-button admin-state
Context
[Tree] (config>system>bluetooth pairing-button)
Full Context
configure system bluetooth pairing-button
Description
This command is used to allow or block the function of the pairing button. This can be used to block the accidental triggering of a pairing operation while there is already a paired device.
The actual behavior of the Bluetooth pairing is dependent on both this command and the power command.
If normal operation is to use the pairing button on the router and on the external device to initiate the Bluetooth connection, then set:
config>system>bluetooth>power enabled-manual
config>system>bluetooth>pairing-button enable
If normal operation is to only require the pairing to be initiated by the external device, then set:
config>system>bluetooth>power enabled-automatic
config>system>bluetooth>pairing-button disable
If normal operation is to not allow the local operator to connect without permission from the central management location, then set:
config>system>bluetooth>power enabled-manual
config>system>bluetooth>pairing-button disable
Then when a connection is desired, the central management station must change the configuration to one of the two options shown above for the time the local operator is connecting. The central management station can change the setting back to block local access after the operations is complete.
Default
pairing-button disable
Parameters
- admin-state
Specifies the administrative state.
Platforms
7750 SR-1, 7750 SR-s, 7950 XRS-20e
parallel
parallel
Syntax
parallel [no-advertise]
no parallel
Context
[Tree] (config>router>isis>segm-rtng>adjacency-set parallel)
[Tree] (config>router>ospf>segm-rtng>adjacency-set parallel)
Full Context
configure router isis segment-routing adjacency-set parallel
configure router ospf segment-routing adjacency-set parallel
Description
This command indicates that all members of the adjacency set must terminate on the same neighboring node. The system raises a trap if a user attempts to add an adjacency terminating on a neighboring node that differs from the existing members of the adjacency set. In addition, the system stops advertising the adjacency set in IS-IS or OSPF and locally deprograms it.
By default, parallel adjacency sets are advertised in the IGP. The no-advertise option prevents an adjacency set from being advertised in the IGP. It is only allowed in CLI and SNMP if the parallel command is configured.
The no form of this command indicates that the adjacency set can include adjacencies to different next hop nodes.
Default
parallel
Platforms
All
param-problem
param-problem
Syntax
param-problem [number seconds]
no param-problem
Context
[Tree] (config>service>ies>if>ipv6>icmp6 param-problem)
[Tree] (config>service>ies>sub-if>grp-if>icmp param-problem)
[Tree] (config>service>vprn>sub-if>grp-if>icmp param-problem)
[Tree] (config>service>ies>if>icmp param-problem)
Full Context
configure service ies interface ipv6 icmp6 param-problem
configure service ies subscriber-interface group-interface icmp param-problem
configure service vprn subscriber-interface group-interface icmp param-problem
configure service ies interface icmp param-problem
Description
This command specifies whether parameter-problem ICMP/ICMPv6 messages should be sent. When enabled, parameter-problem ICMP/ICMPv6 messages are generated by this interface.
The no form of this command disables the sending of parameter-problem ICMP/ICMPv6 messages.
Default
param-problem 100 10
Parameters
- number
Specifies the number of parameter-problem ICMPv6 messages to send in the time frame specified by the seconds parameter.
- seconds
Specifies the time frame, in seconds, that is used to limit the number of parameter-problem ICMPv6 messages issued.
Platforms
All
- configure service ies interface ipv6 icmp6 param-problem
- configure service ies interface icmp param-problem
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
- configure service vprn subscriber-interface group-interface icmp param-problem
- configure service ies subscriber-interface group-interface icmp param-problem
param-problem
Syntax
param-problem [number number] [ seconds seconds]
no param-problem
Context
[Tree] (config>subscr-mgmt>git>ipv4>icmp param-problem)
Full Context
configure subscriber-mgmt group-interface-template ipv4 icmp param-problem
Description
This command configures the parameter-problem ICMPv4 messages that are generated by this interface.
The no form of this command disables the sending of parameter-problem ICMPv4 messages.
Default
param-problem number 100 seconds 10
Parameters
- number
Specifies the number of parameter-problem ICMPv4 messages sent in the time specified by the seconds parameter.
- seconds
Specifies the time, in seconds, that is used to limit the number of parameter-problem ICMPv4 messages issued.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
param-problem
Syntax
param-problem number seconds
no param-problem [number seconds]
Context
[Tree] (config>service>vprn>if>ipv6>icmp6 param-problem)
[Tree] (config>service>vprn>nw-if>icmp param-problem)
[Tree] (config>service>vprn>if>icmp param-problem)
Full Context
configure service vprn interface ipv6 icmp6 param-problem
configure service vprn network-interface icmp param-problem
configure service vprn interface icmp param-problem
Description
This command specifies whether parameter-problem ICMP messages should be sent. When enabled, parameter-problem ICMP messages are generated by this interface. The no form of this command disables the sending of parameter-problem ICMP messages.
Parameters
- number
Specifies the number of parameter-problem ICMP messages to send in the time frame specified by the seconds parameter.
- seconds
Specifies the time frame, in seconds, that is used to limit the number of parameter-problem ICMP messages issued.
Platforms
All
param-problem
Syntax
param-problem [number seconds]
no param-problem
Context
[Tree] (config>router>if>icmp param-problem)
Full Context
configure router interface icmp param-problem
Description
This command specifies whether parameter-problem ICMP messages should be sent. When enabled, parameter-problem ICMP messages are generated by this interface.
The no form of this command disables the sending of parameter-problem ICMP messages.
Parameters
- number
Specifies the number of parameter-problem ICMP messages to send in the time frame specified by the seconds parameter.
- seconds
Specifies the time frame, in seconds, that is used to limit the number of parameter-problem ICMP messages issued.
Platforms
All
param-problem
Syntax
param-problem [number seconds]
no param-problem
Context
[Tree] (config>router>if>ipv6>icmp6 param-problem)
Full Context
configure router interface ipv6 icmp6 param-problem
Description
This command specifies whether parameter-problem ICMPv6 messages should be sent. When enabled, parameter-problem ICMPv6 messages are generated by this interface.
The no form of this command disables the sending of parameter-problem ICMPv6 messages.
Parameters
- number
Specifies the number of parameter-problem ICMPv6 messages to send in the time frame specified by the seconds parameter.
- seconds
Specifies the time frame, in seconds, that is used to limit the number of parameter-problem ICMPv6 messages issued.
Platforms
All
parent
parent
Syntax
parent [weight weight] [ cir-weight cir-weight]
no parent
Context
[Tree] (config>port>ethernet>access>egr>qgrp>qover>q parent)
Full Context
configure port ethernet access egress queue-group queue-overrides queue parent
Description
This command, when used in the queue-overrides context for a queue group queue, defines an optional weight and cir-weight for the queue treatment by the parent scheduler that further governs the available bandwidth given the queue aside from the queue PIR setting. When multiple schedulers and/or queues share a child status with the parent scheduler, the weight or level parameters define how this queue contends with the other children for the parent bandwidth.
Parameters
- weight
Specifies the relative weight of this queue in comparison to other child schedulers and queues while vying for bandwidth on the parent scheduler-name. Any queues or schedulers defined as weighted receive no parental bandwidth until all strict queues and schedulers on the parent have reached their maximum bandwidth or are idle. In this manner, weighted children are considered to be the lowest priority.
- cir-weight
Specifies the weight the queue uses at the within-cir port priority level. The weight is specified as an integer value from 0 to 100 with 100 being the highest weight. When the cir-weight parameter is set to a value of 0 (the default value), the queue or scheduler does not receive bandwidth during the port schedulers within-cir pass and the cir-level parameter is ignored. If the cir-weight parameter is 1 or greater, the cir-level parameter comes into play.
Platforms
All
parent
Syntax
parent [weight weight] [ cir-weight cir-weight]
no parent
Context
[Tree] (config>port>ethernet>access>egr>qgrp>sched-override>scheduler parent)
[Tree] (config>port>ethernet>access>ing>qgrp>sched-override>scheduler parent)
Full Context
configure port ethernet access egress queue-group scheduler-override scheduler parent
configure port ethernet access ingress queue-group scheduler-override scheduler parent
Description
This command can be used to override the scheduler's parent weight and CIR weight. The weights apply to the associated level/cir-level configured in the applied scheduler policy. The scheduler name must exist in the applied scheduler policy.
The override weights are ignored if the scheduler does not have a parent command configured in the scheduler policy - this allows the parent of the scheduler to be removed from the scheduler policy without having to remove all of the queue group overrides. If the parent scheduler does not exist, causing the configured scheduler to be fostered on an egress port scheduler, the override weights will be ignored and the default values used; this avoids having non-default weightings for fostered schedulers.
The no form of this command returns the scheduler's parent weight and cir-weight to the value configured in the applied scheduler policy.
Default
no parent
Parameters
- weight
Specifies the relative weight of this scheduler in comparison to other child schedulers and queues at the same strict level defined by the level parameter in the applied scheduler policy. Within the level, all weight values from active children at that level are summed and the ratio of each active child's weight to the total distributes the available bandwidth at that level. A weight is considered to be active when the queue or scheduler the weight pertains to has not reached its maximum rate and still has packets to transmit.
A 0 (zero) weight value signifies that the child scheduler will receive bandwidth only after bandwidth is distributed to all other non-zero weighted children in the strict level.
- cir-weight
Specifies the relative weight of this scheduler in comparison to other child schedulers and queues at the same cir-level defined by the cir-level parameter in the applied scheduler policy. Within the strict cir-level, all cir-weight values from active children at that level are summed and the ratio of each active child's cir-weight to the total distributes the available bandwidth at that level. A cir-weight is considered to be active when the policer, queue, or scheduler that the cir-weight pertains to has not reached the CIR and still has packets to transmit.
A 0 (zero) cir-weight value signifies that the child scheduler will receive bandwidth only after bandwidth is distributed to all other non-zero weighted children in the strict cir-level.
Platforms
All
parent
Syntax
parent {[weight weight] [cir-weight cir-weight]}
no parent
Context
[Tree] (config>service>cpipe>sap>egress>queue-override>queue parent)
[Tree] (config>service>ipipe>sap>ingress>queue-override>queue parent)
[Tree] (config>service>ipipe>sap>egress>queue-override>queue parent)
[Tree] (config>service>epipe>sap>ingress>queue-override>queue parent)
[Tree] (config>service>apipe>sap>ingress>queue-override>queue parent)
[Tree] (config>service>epipe>sap>egress>queue-override>queue parent)
[Tree] (config>service>apipe>sap>egress>queue-override>queue parent)
[Tree] (config>service>fpipe>sap>egress>queue-override>queue parent)
[Tree] (config>service>cpipe>sap>ingress>queue-override>queue parent)
[Tree] (config>service>fpipe>sap>ingress>queue-override>queue parent)
Full Context
configure service cpipe sap egress queue-override queue parent
configure service ipipe sap ingress queue-override queue parent
configure service ipipe sap egress queue-override queue parent
configure service epipe sap ingress queue-override queue parent
configure service apipe sap ingress queue-override queue parent
configure service epipe sap egress queue-override queue parent
configure service apipe sap egress queue-override queue parent
configure service fpipe sap egress queue-override queue parent
configure service cpipe sap ingress queue-override queue parent
configure service fpipe sap ingress queue-override queue parent
Description
This command defines an optional parent scheduler that further governs the available bandwidth given the queue aside from the queue’s PIR setting. When multiple schedulers and/or queues share a child status with the parent scheduler, the weight or level parameters define how this queue contends with the other children for the parent’s bandwidth.
Checks are not performed to see if a scheduler-name exists when the parent command is defined on the queue. Scheduler names are configured in the config>qos>scheduler-policy>tier level context. Multiple schedulers can exist with the scheduler-name and the association pertains to a scheduler that should exist on the egress SAP as the policy is applied and the queue created. When the queue is created on the egress SAP, the existence of the scheduler-name is dependent on a scheduler policy containing the scheduler-name being directly or indirectly applied (through a multi-service customer site) to the egress SAP. If the scheduler-name does not exist, the queue is placed in the orphaned operational state. The queue will accept packets but will not be bandwidth limited by a virtual scheduler or the scheduler hierarchy applied to the SAP. The orphaned state must generate a log entry and a trap message. The SAP which the queue belongs to must also depict an orphan queue status. The orphaned state of the queue is automatically cleared when the scheduler-name becomes available on the egress SAP.
The parent scheduler can be made unavailable due to the removal of a scheduler policy or scheduler. When an existing parent scheduler is removed or inoperative, the queue enters the orphaned state and automatically returns to normal operation when the parent scheduler is available again.
When a parent scheduler is defined without specifying weight or strict parameters, the default bandwidth access method is weight with a value of 1.
The no form of this command removes a child association with a parent scheduler. If a parent association does not currently exist, the command has no effect and returns without an error. Once a parent association has been removed, the former child queue attempts to operate based on its configured rate parameter. Removing the parent association on the queue within the policy takes effect immediately on all queues using the SAP egress QoS policy.
Parameters
- weight
These optional keywords are mutually exclusive to the level keyword. Specifies the relative weight of this queue in comparison to other child schedulers, policers, and queues while vying for bandwidth on the parent scheduler-name. Any policers, queues, or schedulers defined as weighted receive no parental bandwidth until all policers, queues, and schedulers with a higher (numerically larger) priority on the parent have reached their maximum bandwidth or are idle.
All weight values from all weighted active policers, queues, and schedulers with a common parent scheduler are added together. Then, each individual active weight is divided by the total, deriving the percentage of remaining bandwidth provided to the policer, queue, or scheduler. A weight is considered to be active when the pertaining policer, queue, or scheduler has not reached its maximum rate and still has packets to transmit. All child policers, queues, and schedulers with a weight of 0 are considered to have the lowest priority level and are not serviced until all non-zero weighted policers, queues, and schedulers at that level are operating at the maximum bandwidth or are idle.
- cir-weight
Specifies the weight the queue or scheduler will use at the within-cir port priority level (defined by the cir-level parameter). The weight is specified as an integer value from 0 to 100 with 100 being the highest weight. When the cir-weight parameter is set to a value of 0 (the default value), the policer, queue, or scheduler does not receive bandwidth during the port schedulers within-cir pass and the cir-level parameter is ignored. If the cir-weight parameter is 1 or greater, the cir-level parameter comes into play.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
- configure service fpipe sap ingress queue-override queue parent
- configure service fpipe sap egress queue-override queue parent
- configure service cpipe sap ingress queue-override queue parent
- configure service cpipe sap egress queue-override queue parent
All
- configure service epipe sap egress queue-override queue parent
- configure service ipipe sap ingress queue-override queue parent
- configure service ipipe sap egress queue-override queue parent
- configure service epipe sap ingress queue-override queue parent
7450 ESS, 7750 SR-7/12/12e, 7750 SR-a, 7750 SR-e, 7950 XRS
- configure service apipe sap ingress queue-override queue parent
- configure service apipe sap egress queue-override queue parent
parent
Syntax
parent [weight weight] [cir-weight cir-weight]
no parent
Context
[Tree] (config>service>fpipe>sap>egress>sched-override>scheduler parent)
[Tree] (config>service>cpipe>sap>egress>sched-override>scheduler parent)
[Tree] (config>service>cpipe>sap>ingress>sched-override>scheduler parent)
[Tree] (config>service>ipipe>sap>ingress>sched-override>scheduler parent)
[Tree] (config>service>epipe>sap>egress>sched-override>scheduler parent)
[Tree] (config>service>ipipe>sap>egress>sched-override>scheduler parent)
[Tree] (config>service>apipe>sap>ingress>sched-override>scheduler parent)
[Tree] (config>service>epipe>sap>ingress>sched-override>scheduler parent)
[Tree] (config>service>apipe>sap>egress>sched-override>scheduler parent)
[Tree] (config>service>fpipe>sap>ingress>sched-override>scheduler parent)
Full Context
configure service fpipe sap egress scheduler-override scheduler parent
configure service cpipe sap egress scheduler-override scheduler parent
configure service cpipe sap ingress scheduler-override scheduler parent
configure service ipipe sap ingress scheduler-override scheduler parent
configure service epipe sap egress scheduler-override scheduler parent
configure service ipipe sap egress scheduler-override scheduler parent
configure service apipe sap ingress scheduler-override scheduler parent
configure service epipe sap ingress scheduler-override scheduler parent
configure service apipe sap egress scheduler-override scheduler parent
configure service fpipe sap ingress scheduler-override scheduler parent
Description
This command can be used to override the scheduler’s parent weight and cir-weight information. The weights apply to the associated level/cir-level configured in the applied scheduler policy. The scheduler name must exist in the scheduler policy applied to the ingress or egress of the SAP or multi-service site.
The override weights are ignored if the scheduler does not have a parent command configured in the scheduler policy – this allows the parent of the scheduler to be removed from the scheduler policy without having to remove all of the SAP/MSS overrides. If the parent scheduler does not exist causing the configured scheduler to be fostered on an egress port scheduler, the override weights will be ignored and the default values used; this avoids having non-default weightings for fostered schedulers.
The no form of this command returns the scheduler’s parent weight and cir-weight to the value configured in the applied scheduler policy.
Default
no parent
Parameters
- weight
Specifies the relative weight of this scheduler in comparison to other child schedulers, policers, and queues at the same strict level defined by the level parameter in the applied scheduler policy. Within the level, all weight values from active children at that level are summed and the ratio of each active child’s weight to the total is used to distribute the available bandwidth at that level. A weight is considered to be active when the policer, queue, or scheduler the weight pertains to has not reached its maximum rate and still has packets to transmit.
A 0 (zero) weight value signifies that the child scheduler will receive bandwidth only after bandwidth is distributed to all other non-zero weighted children in the strict level.
- cir-weight
Specifies the relative weight of this scheduler in comparison to other child schedulers, policers, and queues at the same cir-level defined by the cir-level parameter in the applied scheduler policy. Within the strict cir-level, all cir-weight values from active children at that level are summed and the ratio of each active child’s cir-weight to the total is used to distribute the available bandwidth at that level. A cir-weight is considered to be active when the policer, queue, or scheduler that the cir-weight pertains to has not reached the CIR and still has packets to transmit.
A 0 (zero) cir-weight value signifies that the child scheduler will receive bandwidth only after bandwidth is distributed to all other non-zero weighted children in the strict cir-level.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
- configure service fpipe sap egress scheduler-override scheduler parent
- configure service cpipe sap ingress scheduler-override scheduler parent
- configure service cpipe sap egress scheduler-override scheduler parent
- configure service fpipe sap ingress scheduler-override scheduler parent
All
- configure service ipipe sap ingress scheduler-override scheduler parent
- configure service epipe sap egress scheduler-override scheduler parent
- configure service ipipe sap egress scheduler-override scheduler parent
- configure service epipe sap ingress scheduler-override scheduler parent
7450 ESS, 7750 SR-7/12/12e, 7750 SR-a, 7750 SR-e, 7950 XRS
- configure service apipe sap ingress scheduler-override scheduler parent
- configure service apipe sap egress scheduler-override scheduler parent
parent
Syntax
parent [weight weight] [cir-weight cir-weight]
no parent
Context
[Tree] (config>service>vpls>sap>egress>queue-override>queue parent)
[Tree] (config>service>vpls>sap>ingress>queue-override>queue parent)
Full Context
configure service vpls sap egress queue-override queue parent
configure service vpls sap ingress queue-override queue parent
Description
This command defines an optional parent scheduler that further governs the available bandwidth given the queue aside from the queue’s PIR setting. When multiple schedulers and/or queues share a child status with the parent scheduler, the weight or level parameters define how this queue contends with the other children for the parent’s bandwidth.
Checks are not performed to see if a scheduler-name exists when the parent command is defined on the queue. Scheduler names are configured in the config>qos>scheduler-policy>tier level context. Multiple schedulers can exist with the scheduler-name and the association pertains to a scheduler that should exist on the egress SAP as the policy is applied and the queue created. When the queue is created on the egress SAP, the existence of the scheduler-name is dependent on a scheduler policy containing the scheduler-name being directly or indirectly applied (through a multi-service customer site) to the egress SAP. If the scheduler-name does not exist, the queue is placed in the orphaned operational state. The queue will accept packets but will not be bandwidth limited by a virtual scheduler or the scheduler hierarchy applied to the SAP. The orphaned state must generate a log entry and a trap message. The SAP which the queue belongs to must also depict an orphan queue status. The orphaned state of the queue is automatically cleared when the scheduler-name becomes available on the egress SAP.
The parent scheduler can be made unavailable due to the removal of a scheduler policy or scheduler. When an existing parent scheduler is removed or inoperative, the queue enters the orphaned state mentioned above and automatically return to normal operation when the parent scheduler is available again.
When a parent scheduler is defined without specifying weight or strict parameters, the default bandwidth access method is weight with a value of 1.
The no form of this command removes a child association with a parent scheduler. If a parent association does not currently exist, the command has no effect and returns without an error. Once a parent association has been removed, the former child queue attempts to operate based on its configured rate parameter. Removing the parent association on the queue within the policy takes effect immediately on all queues using the SAP egress QoS policy.
Parameters
- weight
These optional keywords are mutually exclusive to the level keyword. The weight defines the relative weight of this queue in comparison to other child schedulers, policers, and queues while vying for bandwidth on the parent scheduler-name. Any policers, queues, or schedulers defined as weighted receive no parental bandwidth until all policers, queues, and schedulers with a higher (numerically larger) priority on the parent have reached their maximum bandwidth or are idle.
All weight values from all weighted active policers, queues, and schedulers with a common parent scheduler are added together. Then, each individual active weight is divided by the total, deriving the percentage of remaining bandwidth provided to the policer, queue, or scheduler. A weight is considered to be active when the pertaining policer, queue, or scheduler has not reached its maximum rate and still has packets to transmit. All child policers, queues, and schedulers with a weight of 0 are considered to have the lowest priority level and are not serviced until all non-zero weighted policers, queues, and schedulers at that level are operating at the maximum bandwidth or are idle.
- cir-weight
Specifies the weight the queue or scheduler will use at the within-cir port priority level (defined by the cir-level parameter). The weight is specified as an integer value from 0 to 100 with 100 being the highest weight. When the cir-weight parameter is set to a value of 0 (the default value), the policer, queue, or scheduler does not receive bandwidth during the port schedulers within-cir pass and the cir-level parameter is ignored. If the cir-weight parameter is 1 or greater, the cir-level parameter comes into play.
Platforms
All
parent
Syntax
parent [weight weight] [cir-weight cir-weight]
no parent
Context
[Tree] (config>service>vpls>sap>egress>sched-override>scheduler parent)
[Tree] (config>service>vpls>sap>ingress>sched-override>scheduler parent)
Full Context
configure service vpls sap egress scheduler-override scheduler parent
configure service vpls sap ingress scheduler-override scheduler parent
Description
This command can be used to override the scheduler’s parent weight and cir-weight information. The weights apply to the associated level/cir-level configured in the applied scheduler policy. The scheduler name must exist in the scheduler policy applied to the ingress or egress of the SAP or multi-service site.
The override weights are ignored if the scheduler does not have a parent command configured in the scheduler policy – this allows the parent of the scheduler to be removed from the scheduler policy without having to remove all of the SAP/MSS overrides. If the parent scheduler does not exist causing the configured scheduler to be fostered on an egress port scheduler, the override weights will be ignored and the default values used; this avoids having non-default weightings for fostered schedulers.
The no form of this command returns the scheduler’s parent weight and cir-weight to the value configured in the applied scheduler policy.
Default
no parent
Parameters
- weight
Specifies the relative weight of this scheduler in comparison to other child schedulers and queues at the same strict level defined by the level parameter in the applied scheduler policy. Within the level, all weight values from active children at that level are summed and the ratio of each active child’s weight to the total is used to distribute the available bandwidth at that level. A weight is considered to be active when the policer, queue, or scheduler the weight pertains to has not reached its maximum rate and still has packets to transmit.
A 0 (zero) weight value signifies that the child scheduler will receive bandwidth only after bandwidth is distributed to all other non-zero weighted children in the strict level.
- cir-weight
Specifies the relative weight of this scheduler in comparison to other child schedulers and queues at the same cir-level defined by the cir-level parameter in the applied scheduler policy. Within the strict cir-level, all cir-weight values from active children at that level are summed and the ratio of each active child’s cir-weight to the total is used to distribute the available bandwidth at that level. A cir-weight is considered to be active when the policer, queue, or scheduler that the cir-weight pertains to has not reached the CIR and still has packets to transmit.
A 0 (zero) cir-weight value signifies that the child scheduler will receive bandwidth only after bandwidth is distributed to all other non-zero weighted children in the strict cir-level.
Platforms
All
parent
Syntax
parent [weight weight] [ cir-weight cir-weight]
Context
[Tree] (config>service>ies>if>sap>egress>queue-override>queue parent)
[Tree] (config>service>ies>if>sap>ingress>queue-override>queue parent)
[Tree] (config>service>ies>if>sap>ingress>sched-override>scheduler parent)
[Tree] (config>service>ies>if>sap>egress>sched-override>scheduler parent)
Full Context
configure service ies interface sap egress queue-override queue parent
configure service ies interface sap ingress queue-override queue parent
configure service ies interface sap ingress scheduler-override scheduler parent
configure service ies interface sap egress scheduler-override scheduler parent
Description
This command can be used to override the scheduler’s parent weight and cir-weight information. The weights apply to the associated level/cir-level configured in the applied scheduler policy. The scheduler name must exist in the scheduler policy applied to the ingress or egress of the SAP or multi-service site.
The override weights are ignored if the scheduler does not have a parent command configured in the scheduler policy – this allows the parent of the scheduler to be removed from the scheduler policy without having to remove all of the SAP/MSS overrides. If the parent scheduler does not exist causing the configured scheduler to be fostered on an egress port scheduler, the override weights will be ignored and the default values used; this avoids having non default weightings for fostered schedulers.
The no form of this command returns the scheduler’s parent weight and cir-weight to the value configured in the applied scheduler policy.
Default
no parent
Parameters
- weight weight
Specifies the relative weight of this scheduler in comparison to other child schedulers and queues at the same strict level defined by the level parameter in the applied scheduler policy. Within the level, all weight values from active children at that level are summed and the ratio of each active child’s weight to the total is used to distribute the available bandwidth at that level. A weight is considered to be active when the queue or scheduler the weight pertains to has not reached its maximum rate and still has packets to transmit.
A 0 (zero) weight value signifies that the child scheduler will receive bandwidth only after bandwidth is distributed to all other non-zero weighted children in the strict level.
- cir-weight cir-weight
Specifies the relative weight of this scheduler in comparison to other child schedulers and queues at the same cir-level defined by the cir-level parameter in the applied scheduler policy. Within the strict cir-level, all cir-weight values from active children at that level are summed and the ratio of each active child’s cir-weight to the total is used to distribute the available bandwidth at that level. A cir-weight is considered to be active when the policer, queue, or scheduler that the cir-weight pertains to has not reached the CIR and still has packets to transmit.
A 0 (zero) cir-weight value signifies that the child scheduler will receive bandwidth only after bandwidth is distributed to all other non-zero weighted children in the strict cir-level.
Platforms
All
parent
Syntax
parent [weight weight] [ cir-weight cir-weight]
no parent
Context
[Tree] (config>service>vprn>if>sap>ingress>queue-override>queue parent)
[Tree] (config>service>vprn>if>sap>egress>queue-override>queue parent)
Full Context
configure service vprn interface sap ingress queue-override queue parent
configure service vprn interface sap egress queue-override queue parent
Description
This command can be used to override the scheduler’s parent weight and cir-weight information. The weights apply to the associated level/cir-level configured in the applied scheduler policy. The scheduler name must exist in the scheduler policy applied to the ingress or egress of the SAP or multi-service site.
The override weights are ignored if the scheduler does not have a parent command configured in the scheduler policy – this allows the parent of the scheduler to be removed from the scheduler policy without having to remove all of the SAP/MSS overrides. If the parent scheduler does not exist causing the configured scheduler to be fostered on an egress port scheduler, the override weights will be ignored and the default values used; this avoids having non default weightings for fostered schedulers.
The no form of this command returns the scheduler’s parent weight and cir-weight to the value configured in the applied scheduler policy.
Default
no parent
Parameters
- weight weight
Specifes the relative weight of this scheduler in comparison to other child schedulers and queues at the same strict level defined by the level parameter in the applied scheduler policy. Within the level, all weight values from active children at that level are summed and the ratio of each active child’s weight to the total is used to distribute the available bandwidth at that level. A weight is considered to be active when the queue or scheduler the weight pertains to has not reached its maximum rate and still has packets to transmit.
A 0 (zero) weight value signifies that the child scheduler will receive bandwidth only after bandwidth is distributed to all other non-zero weighted children in the strict level.
- cir-weight cir-weight
Specifies the relative weight of this scheduler in comparison to other child schedulers and queues at the same cir-level defined by the cir-level parameter in the applied scheduler policy. Within the strict cir-level, all cir-weight values from active children at that level are summed and the ratio of each active child’s cir-weight to the total is used to distribute the available bandwidth at that level. A cir-weight is considered to be active when the policer, queue, or scheduler that the cir-weight pertains to has not reached the CIR and still has packets to transmit.
A 0 (zero) cir-weight value signifies that the child scheduler will receive bandwidth only after bandwidth is distributed to all other non-zero weighted children in the strict cir-level.
Platforms
All
parent
Syntax
parent [weight weight] [ cir-weight cir-weight]
no parent
Context
[Tree] (config>service>vprn>if>sap>egress>sched-override>scheduler parent)
[Tree] (config>service>vprn>if>sap>ingress>sched-override>scheduler parent)
Full Context
configure service vprn interface sap egress scheduler-override scheduler parent
configure service vprn interface sap ingress scheduler-override scheduler parent
Description
This command can be used to override the scheduler’s parent weight and cir-weight information. The weights apply to the associated level/cir-level configured in the applied scheduler policy. The scheduler name must exist in the scheduler policy applied to the ingress or egress of the SAP or multi-service site.
The override weights are ignored if the scheduler does not have a parent command configured in the scheduler policy – this allows the parent of the scheduler to be removed from the scheduler policy without having to remove all of the SAP/MSS overrides. If the parent scheduler does not exist causing the configured scheduler to be fostered on an egress port scheduler, the override weights will be ignored and the default values used; this avoids having non default weightings for fostered schedulers.
The no form of this command returns the scheduler’s parent weight and cir-weight to the value configured in the applied scheduler policy.
Default
no parent
Parameters
- weight weight
Specifies the relative weight of this scheduler in comparison to other child schedulers and queues at the same strict level defined by the level parameter in the applied scheduler policy. Within the level, all weight values from active children at that level are summed and the ratio of each active child’s weight to the total is used to distribute the available bandwidth at that level. A weight is considered to be active when the policer, queue, or scheduler the weight pertains to has not reached its maximum rate and still has packets to transmit.
A 0 (zero) weight value signifies that the child scheduler will receive bandwidth only after bandwidth is distributed to all other non-zero weighted children in the strict level.
- cir-weight cir-weight
Specifies the relative weight of this scheduler in comparison to other child schedulers and queues at the same cir-level defined by the cir-level parameter in the applied scheduler policy. Within the strict cir-level, all cir-weight values from active children at that level are summed and the ratio of each active child’s cir-weight to the total is used to distribute the available bandwidth at that level. A cir-weight is considered to be active when the policer, queue, or scheduler that the cir-weight pertains to has not reached the CIR and still has packets to transmit.
A 0 (zero) cir-weight value signifies that the child scheduler will receive bandwidth only after bandwidth is distributed to all other non-zero weighted children in the strict cir-level.
Platforms
All
parent
Syntax
parent {root | arbiter-name} [ level priority-level] [weight weight-within-level]
no parent
Context
[Tree] (config>qos>plcr-ctrl-plcy>tier>arbiter parent)
Full Context
configure qos policer-control-policy tier arbiter parent
Description
This command is used to define from where the tiered arbiter receives bandwidth. Both tier 1 and tier 2 arbiters default to parenting to the root arbiter. Tier 2 arbiters may be modified to parent to a tier 1 arbiter. The tier 1 arbiter parent cannot be changed.
The no form of this command is used to return the tiered arbiter to the default parenting behavior.
Default
parent root level 1 weight 1
Parameters
- root
In tier 1, arbiter-name is not allowed and only root is accepted. When root is specified, the arbiter will receive all bandwidth directly from the root arbiter. This is the default parent for tiered arbiters.
- arbiter-name
In tier 1, arbiter-name is not allowed and only root is accepted. The specified arbiter-name must exist within the policer-control-policy at tier 1 or the parent command will fail. When a tiered arbiter is acting as a parent for another tiered arbiter, the parent arbiter cannot be removed from the policy. The child arbiter will receive all bandwidth directly from its parent arbiter (that receives bandwidth from the root arbiter).
- priority-level
Each child arbiter attaches to its parent on one of the parent’s eight strict levels. Level 1 is the lowest and 8 is the highest. The level attribute is used to define which level the child arbiter uses on its parent. The parent distributes its available bandwidth based on strict priority starting with priority level 8 and proceeding towards level 1.
- weight-within-level
The weight attribute is used to define how multiple children at the same parent strict level compete when insufficient bandwidth exists on the parent for that level. Each child's weight is divided by the sum of the active children's weights and the result is multiplied by the available bandwidth. If a child cannot receive its entire weighted fair share of bandwidth due to a defined child rate limit, the remainder of its bandwidth is distributed between the other children based on their weights.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
parent
Syntax
parent arbiter-name [weight weight-within-level] [level level]
no parent
Context
[Tree] (config>qos>sap-ingress>policer parent)
[Tree] (config>qos>sap-egress>dyn-policer parent)
[Tree] (config>qos>sap-egress>policer parent)
[Tree] (config>qos>sap-ingress>dyn-policer parent)
Full Context
configure qos sap-ingress policer parent
configure qos sap-egress dynamic-policer parent
configure qos sap-egress policer parent
configure qos sap-ingress dynamic-policer parent
Description
This command is used to create a child-to-parent mapping between each instance of the policer and either the root arbiter or a specific tiered arbiter on the object where the policy is applied. Defining a parent association for the policer causes the policer to compete for the parent policer’s available bandwidth with other child policers mapped to the policer control hierarchy.
Policer control hierarchies may be created on SAPs or on a subscriber or multiservice site context. To create a policer control hierarchy on an ingress or egress SAP context, a policer-control-policy must be applied to the SAP. When applied, the system will create a parent policer that is bandwidth limited by the policy’s max-rate value under the root arbiter. The root arbiter in the policy also provides the information used to determine the various priority-level discard-unfair and discard-all thresholds. Besides the root arbiter, the policy may also contain user-defined tiered arbiters that provide arbitrary bandwidth control for subsets of child policers that are either directly or indirectly parented by the arbiter.
When the QoS policy containing the policer with a parent mapping to an arbiter name exists on the SAP, the system will scan the available arbiters on the SAP. If an arbiter exists with the appropriate name, the policer to arbiter association is created. If the specified arbiter does not exist either because a policer-control-policy is not currently applied to the SAP or the arbiter name does not exist within the applied policy, the policer is placed in an orphan state. Orphan policers operate as if they are not parented and are not subject to any bandwidth constraints other than their own PIR. When a policer enters the orphan state, it is flagged as operationally degraded due to the fact that it is not operating as intended and a trap is generated. Whenever a policer-control-policy is added to the SAP or the existing policy is modified, the SAP's policer's parenting configurations must be reevaluated. If an orphan policer becomes parented, the degraded flag is cleared, and a resulting trap is generated.
For subscribers, the policer control hierarchy is created through the policer-control-policy applied to the sub-profile used by the subscriber. A unique policer control hierarchy is created for each subscriber associated with the sub-profile. The QoS policy containing the policer with the parenting command comes into play through the subscriber sla-profile, which references the QoS policy. The combining of the sub-profile and the sla-profile at the subscriber level provides the system with the proper information to create the policer control hierarchy instance for the subscriber. This functionality is available only for the 7450 ESS and 7750 SR.
Executing the parent command will fail if:
The policer’s stat-mode in the QoS policy is set to no-stats
A stat-mode no-stats override exists on an instance of the policer on a SAP or subscriber or multiservice site context
A policer with a parent command applied cannot be configured with stat-mode no-stats in either the QoS policy or as an override on an instance of the policer.
When a policer is successfully parented to an arbiter, the parent commands level and weight parameters are used to determine at what priority level and at which weight in the priority level that the child policer competes with other children (policers or other arbiters) for bandwidth.
The no form of this command is used to remove the parent association from all instances of the policer.
Parameters
- {root | arbiter-name}
When the parent command is executed, either the keyword root or an arbiter-name must be specified.
- root
Specifies that the policer is intended to become a child to the root arbiter where an instance of the policer is created. If the root arbiter does not exist, the policer will be placed in the orphan state.
- arbiter-name
Specifies that the policer is intended to become a child to one of the tiered arbiters with the given arbiter-name where an instance of the policer is created. If the specified arbiter-name does not exist, the policer will be placed in the orphan state.
- weight weight-within-level
The weight weight-within-level keyword and parameter are optional when executing the parent command. When weight is not specified, a default level of 1 is used in the parent arbiter’s priority level. When weight is specified, the weight-within-level parameter must be specified as an integer value from 1 through 100.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
- configure qos sap-ingress policer parent
- configure qos sap-egress policer parent
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
- configure qos sap-egress dynamic-policer parent
- configure qos sap-ingress dynamic-policer parent
parent
Syntax
parent scheduler-name [weight weight] [level level] [cir-weight cir-weight] [cir-level cir-level]
no parent
Context
[Tree] (config>qos>sap-egress>queue parent)
[Tree] (config>qos>sap-ingress>queue parent)
Full Context
configure qos sap-egress queue parent
configure qos sap-ingress queue parent
Description
This command defines an optional parent scheduler that further governs the available bandwidth given the queue aside from the queue’s PIR setting. When multiple schedulers, policers (at egress only), and/or queues share a child status with the parent scheduler, the weight or level parameters define how this queue contends with the other children for the parent’s bandwidth.
Checks are not performed to see if a scheduler-name exists when the parent command is defined on the queue. Scheduler names are configured in the config>qos>scheduler-policy>tier level context. Multiple schedulers can exist with the scheduler-name and the association pertains to a scheduler that should exist on the egress SAP as the policy is applied and the queue created. When the queue is created on the egress SAP, the existence of the scheduler-name is dependent on a scheduler policy containing the scheduler-name being directly or indirectly applied (through a multiservice customer site) to the egress SAP. If the scheduler-name does not exist, the queue is placed in the orphaned operational state. The queue will accept packets but will not be bandwidth limited by a virtual scheduler or the scheduler hierarchy applied to the SAP. The SAP that the queue belongs to also depicts an orphan queue status. The orphaned state of the queue is automatically cleared when the scheduler-name becomes available on the egress SAP.
The parent scheduler can be made unavailable due to the removal of a scheduler policy or scheduler. When an existing parent scheduler is removed or inoperative, the queue enters the orphaned state and automatically returns to normal operation when the parent scheduler is available again.
When a parent scheduler is defined without specifying the weight parameter, the default is a weight of 1.
The no form of this command removes a child association with a parent scheduler. If a parent association does not currently exist, the command has no effect and returns without an error. When a parent association has been removed, the former child queue attempts to operate based on its configured rate parameter. Removing the parent association on the queue within the policy takes effect immediately on all queues using the SAP egress QoS policy.
Parameters
- scheduler-name
The defined scheduler-name conforms to the same input criteria as the schedulers defined within a scheduler policy. Scheduler names are configured in the config>qos>scheduler-policy>tier level context. There are no checks performed at the time of definition to ensure that the scheduler-name exists within an existing scheduler policy. For the queue to use the defined scheduler-name, the scheduler exists on each egress SAP that the queue is eventually created on. For the duration where scheduler-name does not exist on the egress SAP, the queue operates in an orphaned state.
- weight
Specifies the relative weight of this queue in comparison to other child schedulers, policers, and queues, while vying for bandwidth on the parent scheduler-name. Any queues, policers, or schedulers defined as weighted receive no parental bandwidth until all policers, queues, and schedulers with a higher (numerically larger) priority on the parent have reached their maximum bandwidth or are idle.
All weight values from all weighted active queues, policers, and schedulers with a common parent scheduler are added together. Then, each individual active weight is divided by the total, deriving the percentage of remaining bandwidth provided to the queue, policer, or scheduler. A weight is considered to be active when the pertaining queue, policer, or scheduler has not reached its maximum rate and still has packets to transmit. All child queues, policers, and schedulers with a weight of 0 are considered to have the lowest priority level and are not serviced until all non-zero weighted queues, policers, and schedulers at that level are operating at the maximum bandwidth or are idle.
- level
The optional level parameter defines the level of hierarchy when compared to other schedulers and queues competing for bandwidth on the parent scheduler-name. Queues or schedulers will not receive parental bandwidth until all queues, policers, and schedulers with a higher (numerically larger) priority on the parent have reached their maximum bandwidth or are idle.
Children of the parent scheduler with a lower strict priority will not receive bandwidth until all children with a higher strict priority have either reached their maximum bandwidth or are idle. Children with the same strict level are serviced in relation to their relative weights.
- cir-weight
Specifies the weight that the queue or scheduler uses at the within-CIR port priority level (defined by the cir-level parameter). The weight is specified as an integer value from 0 to 100 with 100 being the highest weight. When the cir-weight parameter is set to a value of 0 (the default value), the queue or scheduler does not receive bandwidth during the port schedulers within-CIR pass and the cir-level parameter is ignored. If the cir-weight parameter is 1 or greater, the cir-level parameter comes into play.
- cir-level
Specifies the port priority that the queue or scheduler will use to receive bandwidth for its within-CIR offered-load. If the cir-weight parameter is set to a value of 0 (the default value), the queue or scheduler does not receive bandwidth during the port schedulers within-CIR pass and the cir-level parameter is ignored. If the cir-weight parameter is 1 or greater, the cir-level parameter comes into play.
Platforms
All
parent
Syntax
parent {root | arbiter-name} [ level level] [weight weight-within-level]
no parent
Context
[Tree] (config>qos>qgrps>egr>qgrp>policer parent)
[Tree] (config>qos>qgrps>ing>qgrp>policer parent)
Full Context
configure qos queue-group-templates egress queue-group policer parent
configure qos queue-group-templates ingress queue-group policer parent
Description
This command is used to create a child-to-parent mapping between each instance of the policer and either the root arbiter or a specific tiered arbiter on the object where the policy is applied. Defining a parent association for the policer causes the policer to compete for the parent policer’s available bandwidth with other child policers mapped to the policer control hierarchy.
Policer control hierarchies may be created on SAPs or on a subscriber or multiservice site context. To create a policer control hierarchy on an ingress or egress SAP context, a policer-control-policy must be applied to the SAP. When applied, the system will create a parent policer that is bandwidth limited by the policy’s max-rate value under the root arbiter. The root arbiter in the policy also provides the information used to determine the various priority level discard-unfair and discard-all thresholds. Besides the root arbiter, the policy may also contain user-defined tiered arbiters that provide arbitrary bandwidth control for subsets of child policers that are either directly or indirectly parented by the arbiter.
When the QoS policy containing the policer with a parent mapping to an arbiter name exists on the SAP, the system will scan the available arbiters on the SAP. If an arbiter exists with the appropriate name, the policer to arbiter association is created. If the specified arbiter does not exist either because a policer-control-policy is not currently applied to the SAP or the arbiter name does not exist within the applied policy, the policer is placed in an orphan state. Orphan policers operate as if they are not parented and are not subject to any bandwidth constraints other than their own PIR. When a policer enters the orphan state, it is flagged as operationally degraded due to the fact that it is not operating as intended and a trap is generated. Whenever a policer-control-policy is added to the SAP or the existing policy is modified, the SAP's policer's parenting configurations must be reevaluated. If an orphan policer becomes parented, the degraded flag is cleared and a resulting trap is generated.
For subscribers, the policer control hierarchy is created through the policer-control-policy applied to the sub-profile used by the subscriber. A unique policer control hierarchy is created for each subscriber associated with the sub-profile. The QoS policy containing the policer with the parenting command comes into play through the subscriber sla-profile that references the QoS policy. The combining of the sub-profile and the sla-profile at the subscriber level provides the system with the proper information to create the policer control hierarchy instance for the subscriber. This functionality is available only for the 7450 ESS and 7750 SR.
Executing the parent command will fail if:
The policer’s stat-mode in the QoS policy is set to no-stats
A stat-mode no-stats override exists on an instance of the policer on a SAP or subscriber or multiservice site context
A policer with a parent command applied cannot be configured with stat-mode no-stats in either the QoS policy or as an override on an instance of the policer.
When a policer is successfully parented to an arbiter, the parent commands level and weight parameters are used to determine at what priority level and at which weight in the priority level that the child policer competes with other children (policers or other arbiters) for bandwidth.
The no form of this command is used to remove the parent association from all instances of the policer.
Parameters
- {root | arbiter-name}
When the parent command is executed, either the keyword root or an arbiter-name must be specified.
- root
The root keyword specifies that the policer is intended to become a child to the root arbiter where an instance of the policer is created. If the root arbiter does not exist, the policer will be placed in the orphan state.
- arbiter-name
The arbiter-name parameter specifies that the policer is intended to become a child to one of the tiered arbiters with the given arbiter-name where an instance of the policer is created. If the specified arbiter-name does not exist, the policer will be placed in the orphan state.
- weight weight-within-level
The weight weight-within-level keyword and parameter are optional when executing the parent command. When weight is not specified, a default level of 1 is used in the parent arbiters priority level. When weight is specified, the weight-within-level parameter must be specified as an integer value from 1 through 100.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
parent
Syntax
parent scheduler-name [weight weight] [level level] [ cir-weight cir-weight] [cir-level cir-level]
no parent
Context
[Tree] (config>qos>qgrps>egr>qgrp>queue parent)
[Tree] (config>qos>qgrps>ing>qgrp>queue parent)
Full Context
configure qos queue-group-templates egress queue-group queue parent
configure qos queue-group-templates ingress queue-group queue parent
Description
This command defines an optional parent scheduler that further governs the available bandwidth given the queue aside from the queue’s PIR setting. When multiple schedulers, policers (at egress only), and/or queues share a child status with the parent scheduler, the weight or level parameters define how this queue contends with the other children for the parent’s bandwidth.
Checks are not performed to see if a scheduler-name exists when the parent command is defined on the queue. Scheduler names are configured in the config>qos>scheduler-policy>tier level context. Multiple schedulers can exist with the scheduler-name and the association pertains to a scheduler that should exist on the egress SAP as the policy is applied and the queue created. When the queue is created on the egress SAP, the existence of the scheduler-name is dependent on a scheduler policy containing the scheduler-name being directly or indirectly applied (through a multiservice customer site) to the egress SAP. If the scheduler-name does not exist, the queue is placed in the orphaned operational state. The queue will accept packets but will not be bandwidth limited by a virtual scheduler or the scheduler hierarchy applied to the SAP. The SAP that the queue belongs to must also depict an orphan queue status. The orphaned state of the queue is automatically cleared when the scheduler-name becomes available on the egress SAP.
The parent scheduler can be made unavailable due to the removal of a scheduler policy or scheduler. When an existing parent scheduler is removed or inoperative, the queue enters the orphaned state and automatically returns to normal operation when the parent scheduler is available again.
When a parent scheduler is defined without specifying weight or strict parameters, the default bandwidth access method is weight with a value of 1.
The no form of this command removes a child association with a parent scheduler. If a parent association does not currently exist, the command has no effect and returns without an error. When a parent association has been removed, the former child queue attempts to operate based on its configured rate parameter. Removing the parent association on the queue within the policy takes effect immediately on all queues using the SAP egress QoS policy.
Parameters
- scheduler-name
The defined scheduler-name conforms to the same input criteria as the schedulers defined within a scheduler policy. Scheduler names are configured in the config>qos>scheduler-policy>tier level context. There are no checks performed at the time of definition to ensure that the scheduler-name exists within an existing scheduler policy. For the queue to use the defined scheduler-name, the scheduler exists on each egress SAP the queue is eventually created on. For the duration where scheduler-name does not exist on the egress SAP, the queue operates in an orphaned state.
- weight weight
weight defines the relative weight of this queue in comparison to other child schedulers and queues while vying for bandwidth on the parent scheduler-name. Any queues or schedulers defined as weighted receive no parental bandwidth until all policers, queues, and schedulers with a higher (numerically larger) priority on the parent have reached their maximum bandwidth or are idle.
All weight values from all weighted active queues, policers, and schedulers with a common parent scheduler are added together. Then, each individual active weight is divided by the total, deriving the percentage of remaining bandwidth provided to the queue, policer, or scheduler. A weight is considered to be active when the pertaining queue or scheduler has not reached its maximum rate and still has packets to transmit. All child policers, queues, and schedulers with a weight of 0 are considered to have the lowest priority level and are not serviced until all non-zero weighted queues, policers, and schedulers at that level are operating at the maximum bandwidth or are idle.
- level level
The optional level parameter defines the level of hierarchy when compared to other schedulers and queues when vying for bandwidth on the parent scheduler-name. Queues or schedulers will not receive parental bandwidth until all queues and schedulers with a higher (numerically larger) priority on the parent have reached their maximum bandwidth or are idle.
Children of the parent scheduler with a lower strict priority will not receive bandwidth until all children with a higher strict priority have either reached their maximum bandwidth or are idle. Children with the same strict level are serviced relative to their weights.
- cir-weight cir-weight
Specifies the weight the queue or scheduler will use at the within-CIR port priority level (defined by the cir-level parameter). The weight is specified as an integer value from 0 to 100 with 100 being the highest weight. When the cir-weight parameter is set to a value of 0 (the default value), the queue or scheduler does not receive bandwidth during the port schedulers within-CIR pass and the cir-level parameter is ignored. If the cir-weight parameter is 1 or greater, the cir-level parameter comes into play.
- cir-level cir-level
Specifies the port priority the queue or scheduler will use to receive bandwidth for its within-CIR offered-load. If the cir-weight parameter is set to a value of 0 (the default value), the queue or scheduler does not receive bandwidth during the port schedulers within-CIR pass and the cir-level parameter is ignored. If the cir-weight parameter is 1 or greater, the cir-level parameter comes into play.
Platforms
All
parent
Syntax
parent scheduler-name [weight weight] [level level] [ cir-weight cir-weight] [cir-level cir-level]
no parent
Context
[Tree] (config>qos>scheduler-policy>tier>scheduler parent)
Full Context
configure qos scheduler-policy tier scheduler parent
Description
This command defines an optional parent scheduler that is higher up the policy hierarchy. Only schedulers in tier levels 2 and 3 can have a parental association. When multiple schedulers, policers (at egress only), and/or queues share a child status with the scheduler on the parent, the weight or strict parameters define how this scheduler contends with the other children for the parent’s bandwidth. The parent scheduler can be removed or changed at any time and is immediately reflected on the schedulers created by association of this scheduler policy.
When a parent scheduler is defined without specifying weight or strict parameters, the default bandwidth access method is weight with a value of 1.
The no form of this command removes a child association with a parent scheduler. If a parent association does not currently exist, the command has no effect and returns without an error. When a parent association has been removed, the former child scheduler attempts to operate based on its configured rate parameter. Removing the parent association on the scheduler within the policy will take effect immediately on all schedulers with scheduler-name that have been created using the scheduler-policy-name.
Parameters
- scheduler-name
Specifies a scheduler name. The scheduler-name must already exist within the context of the scheduler policy in a tier that is higher (numerically lower).
- weight weight
Specifies the relative weight of this scheduler in comparison to other child schedulers and queues at the same strict level defined by the level parameter. Within the level, all weight values from active children at that level are summed and the ratio of each active child’s weight to the total is used to distribute the available bandwidth at that level. A weight is considered to be active when the queue or scheduler the weight pertains to has not reached its maximum rate and still has packets to transmit.
A zero (0) weight value signifies that the child scheduler will receive bandwidth only after bandwidth is distributed to all other non-zero weighted children in the strict level.
- level level
Specifies the strict priority level of this scheduler in comparison to other child schedulers and queues vying for bandwidth on the parent scheduler-name during the above-CIR distribution phase of bandwidth allocation. During the above-CIR distribution phase, any queues or schedulers defined at a lower strict level receive no parental bandwidth until all queues and schedulers defined with a higher (numerically larger) strict level on the parent have reached their maximum bandwidth or have satisfied their offered load requirements.
When the similar cir-level parameter default (undefined) are retained for the child scheduler, bandwidth is only allocated to the scheduler during the above-CIR distribution phase.
Children of the parent scheduler with a lower strict priority level will not receive bandwidth until all children with a higher strict priority level have either reached their maximum bandwidth or are idle. Children with the same strict level are serviced in relation to their relative weights.
- cir-weight cir-weight
Specifies the relative weight of this scheduler in comparison to other child schedulers and queues at the same cir-level defined by the cir-level parameter. Within the strict cir-level, all cir-weight values from active children at that level are summed and the ratio of each active child’s cir-weight to the total is used to distribute the available bandwidth at that level. A cir-weight is considered to be active when the queue or scheduler that the cir-weight pertains to has not reached the CIR and still has packets to transmit.
A zero (0) cir-weight value signifies that the child scheduler will receive bandwidth only after bandwidth is distributed to all other non-zero weighted children in the strict cir-level.
- cir-level cir-level
Specifies the strict priority CIR level of this scheduler in comparison to other child schedulers and queues vying for bandwidth on the parent scheduler-name during the within-CIR distribution phase of bandwidth allocation. During the within-CIR distribution phase, any queues or schedulers defined at a lower strict CIR level receive no parental bandwidth until all queues and schedulers defined with a higher (numerically larger) strict CIR level on the parent have reached their CIR bandwidth or have satisfied their offered load requirements.
If the scheduler’s cir-level parameter retains the default (undefined) state, bandwidth is only allocated to the scheduler during the above-CIR distribution phase.
Children with the same strict cir-level are serviced according to their cir-weight.
Platforms
All
parent
Syntax
parent [weight weight] [cir-weight cir-weight]
no parent
Context
[Tree] (config>service>cust>multi-service-site>egress>sched-override>scheduler parent)
[Tree] (config>service>cust>multi-service-site>ingress>sched-override>scheduler parent)
Full Context
configure service customer multi-service-site egress scheduler-override scheduler parent
configure service customer multi-service-site ingress scheduler-override scheduler parent
Description
This command overrides the scheduler’s parent weight and CIR weight information. The weights apply to the associated level or cir-level configured in the applied scheduler policy. The scheduler name must exist in the scheduler policy applied to the ingress or egress of the SAP or multi-service site.
The override weights are ignored if the scheduler does not have a parent command configured in the scheduler policy. This allows the parent of the scheduler to be removed from the scheduler policy without having to remove all of the SAP/MSS overrides. If the parent scheduler does not exist causing the configured scheduler to be fostered on an egress port scheduler, the override weights will be ignored and the default values used; this avoids having non-default weightings for fostered schedulers.
The no form of the command returns the scheduler’s parent weight and CIR weight to the value configured in the applied scheduler policy.
Default
no parent
Parameters
- weight
Specifies the relative weight of this scheduler in comparison to other child schedulers and queues at the same strict level defined by the level parameter in the applied scheduler policy. Within the level, all weight values from active children at that level are summed and the ratio of each active child’s weight to the total is used to distribute the available bandwidth at that level. A weight is considered to be active when the policer, queue or scheduler the weight pertains to has not reached its maximum rate and still has packets to transmit. A 0 (zero) weight value signifies that the child scheduler will receive bandwidth only after bandwidth is distributed to all other non-zero weighted children in the strict level.
- cir-weight
Specifies the relative weight of this scheduler in comparison to other child schedulers and queues at the same cir-level defined by the cir-level parameter in the applied scheduler policy. Within the strict cir-level, all cir-weight values from active children at that level are summed and the ratio of each active child’s cir-weight to the total is used to distribute the available bandwidth at that level. A cir-weight is considered to be active when the policer, queue or scheduler that the cir-weight pertains to has not reached the CIR and still has packets to transmit. A 0 (zero) cir-weight value signifies that the child scheduler will receive bandwidth only after bandwidth is distributed to all other non-zero weighted children in the strict cir-level.
Platforms
All
parent-location
parent-location
Syntax
parent-location {default | sla}
no parent-location
Context
[Tree] (config>qos>sap-egress parent-location)
Full Context
configure qos sap-egress parent-location
Description
This command determines the expected location of the parent schedulers for queues configured with a parent command within the sap-egress policy. All parent schedulers must be configured within a scheduler-policy applied at the location corresponding to the parent-location parameter.
If a parent scheduler name does not exist at the specified location, the queue will not be parented and will be orphaned.
The no form of this command reverts to the default.
Default
parent-location default
Parameters
- default
When the sap-egress policy is applied to an sla-profile for a subscriber, the parent schedulers of the queues need to be configured in the scheduler-policy applied to the subscriber’s sub-profile.
When the sap-egress policy is applied to a SAP, the parent schedulers of the queues need to be configured in the scheduler-policy applied to the SAP or the multiservice site.
- sla
When the sap-egress policy is applied to an sla-profile for a subscriber, the parent schedulers of the queues need to be configured in the scheduler-policy applied to the same sla-profile.
If this parameter is configured within a sap-egress policy that is applied to any object except of the egress of an sla-profile, the configured parent schedulers will not be found and so the queues will not be parented and will be orphaned. This parameter is not supported when policers-hqos-manageable is configured in the SAP egress QoS policy.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
parent-location
Syntax
parent-location {none | sub | vport}
no parent-location
Context
[Tree] (config>qos>scheduler-policy>tier parent-location)
Full Context
configure qos scheduler-policy tier parent-location
Description
This command determines the expected location of the parent schedulers for the tier 1 schedulers configured with a parent command within the scheduler-policy. The parent schedulers must be configured within a scheduler-policy applied at the location corresponding to the parent-location parameter.
If a parent scheduler name does not exist at the specified location, the schedulers will not be parented and will be orphaned.
The configuration of parent-location and frame-based-accounting in a scheduler policy is mutually exclusive in order to ensure consistency between the different scheduling levels.
The no form of this command reverts to the default.
Default
parent-location none
Parameters
- none
This parameter indicates that the tier 1 schedulers do not have a parent scheduler and the configuration of the parent under a tier 1 scheduler is blocked. Conversely, this parameter is blocked when any tier 1 scheduler has a parent configured.
- sub
When the scheduler-policy is applied to an sla-profile for a subscriber, the parent schedulers of the tier 1 schedulers need to be configured in the scheduler-policy applied to the subscriber’s sub-profile.
If this parameter is configured within a scheduler-policy that is applied to any object except for the egress of an sla-profile, the configured parent schedulers will not be found and so the tier 1 schedulers will not be parented and will be orphaned.
- vport
When the scheduler-policy is applied to an sla-profile, a sub-profile for a subscriber, or to the egress of a pseudowire SAP, the parent schedulers of the tier 1 schedulers need to be configured in the scheduler-policy applied to the Vport to which the subscriber will be assigned.
If this parameter is configured within a scheduler-policy that is applied to any object except for the egress of an sla-profile or sub-profile, or to the egress of a PW SAP, the configured parent schedulers will not be found and so the tier 1 schedulers will not be parented and will be orphaned.
Platforms
All
parent-mid-pool
parent-mid-pool
Syntax
parent-mid-pool mid-pool-id
no parent-mid-pool
Context
[Tree] (config>qos>hs-port-pool-policy>alt-port-class-pools>class-pool parent-mid-pool)
[Tree] (config>qos>hs-port-pool-policy>std-port-class-pools>class-pool parent-mid-pool)
Full Context
configure qos hs-port-pool-policy alt-port-class-pools class-pool parent-mid-pool
configure qos hs-port-pool-policy std-port-class-pools class-pool parent-mid-pool
Description
This command creates the buffer allocation mapping between the associated class pool and the specified mid-pool. Use care when selecting a mid-pool in an active state (properly mapped to a root-pool with a non-zero allocation percentage). If a port-class pool is parented by an inactive mid-pool, the queues using the port-class pool are forced into an operational MBS setting of 0, causing all packet to be discarded. A port-class pool can be made inactive (no available buffers) by executing parent-mid-pool none in the port-class pool context.
The no form of the command reverts to the class-pool parenting value. For the standard port-class pools, this default is 1. For alternate port-class pools the default is none.
Default
alt-port-class-pools: none
std-port-class-pools: 1
Parameters
- mid-pool-id
Specifies the mid-pool identifier in the HS pool policy. Either a valid mid-pool ID or none must be specified when executing the parent-mid-pool command. The mid-pool-id parameter defines the parent mid-pool to which the port-class is associated. The none keyword deactivates the port-class pool, causing the pool to have a zero size. A queue can still map to an inactive port-class pool although all packets are discarded by the queue.
Platforms
7750 SR-7/12/12e
parent-root-pool
parent-root-pool
Syntax
parent-root-pool root-pool-id
no parent-root-pool
Context
[Tree] (config>qos>hs-pool-policy>mid-tier>mid-pool parent-root-pool)
Full Context
configure qos hs-pool-policy mid-tier mid-pool parent-root-pool
Description
This command creates a buffer allocation mapping between the associated mid-pool mid-pool-id and the specified parent-root-pool root-pool-id. The specified root pool ID must have a non-zero allocation-weight or the command fails. After a mid-pool is successfully associated with a root-pool, the parent root-pool’s allocation-weight value cannot be set to zero.
When the root-pool-id is set to none, no buffers are assigned to the mid-tier pool.
The no form of the command reverts to the default.
Default
parent-root-pool 1
Parameters
- root-pool-id
Specifies the parent root pool to which the mid-pool is associated. This parameter is required when executing the parent-root-pool command.
Platforms
7750 SR-7/12/12e
participant-id
participant-id
Syntax
participant-id participant-id
no participant-id
Context
[Tree] (config>app-assure>group>http-error-redirect participant-id)
Full Context
configure application-assurance group http-error-redirect participant-id
Description
This command specifies a 32-character string assigned to the operator by Barefruit. It is used by barefruit landing servers (applies to template # 1 only).
Default
no participant-id
Parameters
- participant-id
Specifies the 32-character string supplied by Barefruit.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
participate
participate
Syntax
[no] participate
Context
[Tree] (config>router>isis>flex-algos>flex-algo participate)
Full Context
configure router isis flexible-algorithms flex-algo participate
Description
This command enables IS-IS participation in a specific flexible algorithm.
The router advertises its capability to participate in a specific flexible algorithm within the IS-IS router-capability TLV. Router participation in a flexible algorithm assumes that segment routing and, consequently the advertise-router-capability area is enabled. However, a router only advertises flexible algorithm participation when it can support the corresponding winning flexible algorithm definition. The flexible algorithm participation is not enabled by default.
The no form of this command disables participation for a particular flexible algorithm.
Default
no participate
Platforms
All
participate
Syntax
[no] participate
Context
[Tree] (config>router>ospf>flex-algos>flex-algo participate)
Full Context
configure router ospf flexible-algorithms flex-algo participate
Description
This command enables OSPFv2 participation in a specific flexible algorithm.
The router advertises its capability to participate in a specific flexible algorithm within the OSPFv2 SR algorithm TLV of the router information opaque LSA. Router participation in a flexible algorithm assumes that segment routing and, consequently, the advertise-router-capability area is enabled. However, a router only advertises flexible algorithm participation when it can support the corresponding winning flexible algorithm definition. The flexible algorithm participation is not enabled by default.
The no form of this command disables participation for a specific flexible algorithm.
Default
no participate
Platforms
All
partitions
partitions
Syntax
[no] partitions
Context
[Tree] (config>isa>aa-grp partitions)
Full Context
configure isa application-assurance-group partitions
Description
This command enables partitions within an ISA-AA group. When enabled, partitions can be created.
The no form of this command disables partitions within an ISA-AA group.
Default
no partitions
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
partner-down-delay
partner-down-delay
Syntax
partner-down-delay [hrs hours] [min minutes] [sec seconds]
no partner-down-delay
Context
[Tree] (config>router>dhcp>server>failover partner-down-delay)
[Tree] (config>router>dhcp6>server>failover partner-down-delay)
[Tree] (config>service>vprn>dhcp6>server>failover partner-down-delay)
[Tree] (config>service>vprn>dhcp>server>failover partner-down-delay)
[Tree] (config>service>vprn>dhcp6>server>pool>failover partner-down-delay)
[Tree] (config>router>dhcp>server>pool>failover partner-down-delay)
[Tree] (config>service>vprn>dhcp>server>pool>failover partner-down-delay)
[Tree] (config>router>dhcp6>server>pool>failover partner-down-delay)
Full Context
configure router dhcp local-dhcp-server failover partner-down-delay
configure router dhcp6 local-dhcp-server failover partner-down-delay
configure service vprn dhcp6 local-dhcp-server failover partner-down-delay
configure service vprn dhcp local-dhcp-server failover partner-down-delay
configure service vprn dhcp6 local-dhcp-server pool failover partner-down-delay
configure router dhcp local-dhcp-server pool failover partner-down-delay
configure service vprn dhcp local-dhcp-server pool failover partner-down-delay
configure router dhcp6 local-dhcp-server pool failover partner-down-delay
Description
This command configures the partner down delay time. Since the DHCP lease synchronization failure can be caused by the failure of the intercommunication link (and not necessary the entire node), there is a possibility the redundant DHCP servers become isolated in the network. In other words, they can serve DHCP clients but they cannot synchronize the lease. This can lead to duplicate assignment of IP addresses, since the servers have configured overlapping IP address ranges but they are not aware of each other’s leases.
The purpose of the partner down delay is to prevent the IP lease duplication during the intercommunication link failure by not allowing new IP addresses to be assigned from the remote IP address range. This timer is intended to provide the operator with enough time to remedy the failed situation and to avoid duplication of IP addresses or prefixes during the failure.
During the partner-down-delay time, the prefix designated as remote is eligible only for renewals of the existing DHCP leases that have been synchronized by the peering node. Only after the sum of the partner-down-delay and the maximum-client-lead-time will the prefix designated as remote be eligible for delegation of the new DHCP leases. When this occurs, we say that the remote IP address range has been taken over.
It is possible to expedite the takeover of a remote IP address range so that the new IP leases can start being delegated from that range shortly after the intercommunication failure is detected. This can be achieved by configuring the partner-down-delay timer to 0 seconds, along with enabling the ignore-mclt-on-takeover CLI flag. Caution must be taken before enabling this functionality. It is safe to bypass safety timers (partner-down-delay + MCLT) only in cases where the operator is certain that the intercommunication between the nodes has failed due to the entire node failure and not due to the intercommunication (MCS) link failure. Failed intercommunication due to the nodal failure would ensure that only one node is present in the network for IP address delegation (as opposed to two isolated nodes with overlapping IP address ranges where address duplication can occur). For this reason, the operator must ensure that there are redundant paths between the nodes to ensure uninterrupted synchronization of DHCP leases.
In access-driven mode of operation, partner-down-delay has no effect.
The no form of this command reverts to the default.
Default
partner-down-delay hrs 23 min 59 sec 59
Parameters
- partner-down-delay
Specifies the partner down delay time.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
passive
passive
Syntax
[no] passive
Context
[Tree] (config>subscr-mgmt>bgp-prng-plcy passive)
Full Context
configure subscriber-mgmt bgp-peering-policy passive
Description
This command enables the passive mode for the BGP neighbors.
The no form of this command disables the passive mode.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
passive
Syntax
[no] passive
Context
[Tree] (config>service>vprn>bgp>group passive)
[Tree] (config>service>vprn>bgp>group>neighbor passive)
Full Context
configure service vprn bgp group passive
configure service vprn bgp group neighbor passive
Description
This command enables passive mode for the BGP group or neighbor.
When in passive mode, BGP will not attempt to actively connect to the configured BGP peers but responds only when it receives a connect open request from the peer.
The no form of this command used at the group level disables passive mode where BGP actively attempts to connect to its peers.
The no form of this command used at the neighbor level reverts to the value defined at the group level.
Default
no passive — BGP will actively try to connect to all the configured peers.
Platforms
All
passive
Syntax
[no] passive
Context
[Tree] (config>service>vprn>isis>if passive)
[Tree] (config>service>vprn>isis>if>level passive)
Full Context
configure service vprn isis interface passive
configure service vprn isis interface level passive
Description
This command adds the passive attribute which causes the interface to be advertised as an IS-IS interface without running the IS-IS protocol. Normally, only interface addresses that are configured for IS-IS are advertised as IS-IS interfaces at the level that they are configured.
When the passive mode is enabled, the interface or the interface at the level ignores ingress IS-IS protocol PDUs and does not transmit IS-IS protocol PDUs.
The no form of this command removes the passive attribute.
Default
no passive
Platforms
All
passive
Syntax
[no] passive
Context
[Tree] (config>service>vprn>ospf>area>if passive)
[Tree] (config>service>vprn>ospf3>area>if passive)
Full Context
configure service vprn ospf area interface passive
configure service vprn ospf3 area interface passive
Description
This command adds the passive property to the OSPF interface where passive interfaces are advertised as OSPF interfaces but do not run the OSPF protocol.
By default, only interface addresses that are configured for OSPF are advertised as OSPF interfaces. The passive parameter allows an interface to be advertised as an OSPF interface without running the OSPF protocol.
While in passive mode, the interface ignores ingress OSPF protocol packets and does not transmit any OSPF protocol packets.
The no form of this command removes the passive property from the OSPF interface.
Default
no passive
Platforms
All
passive
Syntax
[no] passive
Context
[Tree] (config>router>bgp>group passive)
[Tree] (config>router>bgp>group>neighbor passive)
Full Context
configure router bgp group passive
configure router bgp group neighbor passive
Description
Enables/disables passive mode for the BGP group or neighbor.
When in passive mode, BGP will not attempt to actively connect to the configured BGP peers but responds only when it receives a connect open request from the peer.
The no form of this command used at the group level disables passive mode where BGP actively attempts to connect to its peers.
The no form of this command used at the neighbor level reverts to the value defined at the group level.
Default
no passive
Platforms
All
passive
Syntax
[no] passive
Context
[Tree] (config>router>isis>if passive)
[Tree] (config>router>isis>if>level passive)
Full Context
configure router isis interface passive
configure router isis interface level passive
Description
This command adds the passive attribute which causes the interface to be advertised as an IS-IS interface without running the IS-IS protocol. Normally, only interface addresses that are configured for IS-IS are advertised as IS-IS interfaces at the level that they are configured.
When the passive mode is enabled, the interface or the interface at the level ignores ingress IS-IS protocol PDUs and does not transmit IS-IS protocol PDUs.
The no form of this command removes the passive attribute.
Default
no passive
Platforms
All
passive
Syntax
[no] passive
Context
[Tree] (config>router>ospf>area>interface passive)
[Tree] (config>router>ospf3>area>interface passive)
Full Context
configure router ospf area interface passive
configure router ospf3 area interface passive
Description
This command adds the passive property to the OSPF interface where passive interfaces are advertised as OSPF interfaces but do not run the OSPF protocol.
By default, only interface addresses that are configured for OSPF will be advertised as OSPF interfaces. The passive parameter allows an interface to be advertised as an OSPF interface without running the OSPF protocol.
While in passive mode, the interface will ignore ingress OSPF protocol packets and not transmit any OSPF protocol packets.
The no form of this command removes the passive property from the OSPF interface.
Default
no passive
Platforms
All
passive-dns
passive-dns
Syntax
passive-dns
Context
[Tree] (config>app-assure>group>ip-id-asst passive-dns)
Full Context
configure application-assurance group ip-identification-assist passive-dns
Description
Commands in this context configure passive DNS monitoring for the IP identification assist feature.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
passive-mode
passive-mode
Syntax
[no] passive-mode
Context
[Tree] (config>redundancy>multi-chassis>peer>mc-ep passive-mode)
Full Context
configure redundancy multi-chassis peer mc-endpoint passive-mode
Description
This command configures the passive mode behavior for the MC-EP protocol. When in passive mode the MC-EP pair will be dormant until two of the pseudowires in a MC-EP will be signaled as active by the remote PEs, being assumed that the remote pair is configured with regular MC-EP. As soon as more than one pseudowire is active, dormant MC-EP pair will activate. It will use the regular exchange to select the best pseudowire between the active ones and it will block the Rx and Tx directions of the other pseudowires.
The no form of this command will disable the passive mode behavior.
Default
no passive-mode
Platforms
All
passkey
passkey
Syntax
passkey passkey
Context
[Tree] (config>system>bluetooth passkey)
Full Context
configure system bluetooth passkey
Description
This command is used to define the Bluetooth pass key that is used during paring. This passkey must match in both devices attempting the pairing operation.
Default
passkey 123456
Parameters
- passkey
Must be six digits.
Platforms
7750 SR-1, 7750 SR-s, 7950 XRS-20e
password
password
Syntax
password
Context
[Tree] (password)
Full Context
password
Description
This operational command changes the local user password.
This command is automatically invoked when a user logs in after the administrator uses the new-password-at-login command to force a new password, or the password has expired ( aging). At this time, the user is prompted to enter the old password, new password, and then the new password again to verify the input.
If the user fails to create a new password, CLI access is denied.
A user cannot configure a nonconforming password using the global password command. In this case, the CLI displays an error message and the password change fails. To configure a password value that does not conform to the minimum length or other password complexity rules, use the config>system>security>user>password command (for example, executed by an administrator).
Platforms
All
password
Syntax
password {ignore | chap password | pap password} [hash | hash2 | custom]
no password
Context
[Tree] (config>subscr-mgmt>loc-user-db>ppp>host password)
Full Context
configure subscriber-mgmt local-user-db ppp host password
Description
This command specifies a password type or configures password string for pap or chap. The pap and chap passwords are stored in a hashed format in the config files. The hash|hash2 optional keywords are used for config execution.
This command will only be interpreted if the local user database is connected directly to the PPPoE node under the VPRN/IES group interface. It is not used if the local user database is accessed by a local DHCP server.
The no form of this command reverts to the default.
Parameters
- ignore
Specifies that the password be ignored, in which case authentication is always succeed, independent of the password used by the PPPoE client. The client must still perform authentication.
- chap password
Specifies that the password, up to 64 characters, for Challenge-Handshake Authentication Protocol) (CHAP) is used. Only a password received with the CHAP protocol is accepted.
- pap password
Specifies that the Password Authentication Protocol (PAP) is used, up to 64 characters. Only a password received with the PAP protocol is accepted, even though the CHAP protocol is proposed to the client first because it is unknown at the time of the offer which password type is allowed to the client.
- hash | hash2
Specifies hashing scheme.
- custom
Specifies the custom encryption to management interface.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
password
Syntax
password password [{hash | hash2 | custom}]
no password
Context
[Tree] (config>router>l2tp password)
[Tree] (config>router>l2tp>group>l2tpv3 password)
[Tree] (config>router>l2tp>l2tpv3 password)
[Tree] (config>router>l2tp>group password)
[Tree] (config>service>vprn>l2tp>l2tpv3 password)
[Tree] (config>router>l2tp>group>tunnel password)
[Tree] (config>service>vprn>l2tp>group password)
[Tree] (config>service>vprn>l2tp>group>l2tpv3 password)
[Tree] (config>service>vprn>l2tp password)
[Tree] (config>service>vprn>l2tp>group>tunnel password)
Full Context
configure router l2tp password
configure router l2tp group l2tpv3 password
configure router l2tp l2tpv3 password
configure router l2tp group password
configure service vprn l2tp l2tpv3 password
configure router l2tp group tunnel password
configure service vprn l2tp group password
configure service vprn l2tp group l2tpv3 password
configure service vprn l2tp password
configure service vprn l2tp group tunnel password
Description
This command configures the password between L2TP LAC and LNS
The no form of this command removes the password.
Default
no password
Parameters
- password
Configures the password used for challenge/response calculation and AVP hiding. The maximum length is up to 20 characters if unhashed, 32 characters if hashed, 54 characters if the hash2 keyword is specified.
- hash
Specifies the key is entered in an encrypted form. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, clear text form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- hash2
Specifies the key is entered in a more complex encrypted form that involves more variables than the key value alone, meaning that the hash2 encrypted variable cannot be copied and pasted. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, clear text form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- custom
Specifies the custom encryption to management interface.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
password
Syntax
password password [hash | hash2 | custom]
no password
Context
[Tree] (config>service>dynsvc>plcy>auth password)
Full Context
configure service dynamic-services dynamic-services-policy authentication password
Description
This command configures the password to be used for RADIUS authentication of data-triggered dynamic services.
The no form of this command removes the password from the configuration.
Parameters
- password
Specifies the password that is used in RADIUS authentication of a data-triggered dynamic service. The maximum length is 20 characters if unhashed, 32 characters if hashed, and 54 characters if the hash2 keyword is specified.
- hash
Specifies the key is entered in an encrypted form. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, clear text form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified
- hash2
Specifies the key is entered in a more complex encrypted form that involves more variables than the key value alone, meaning that the hash2 encrypted variable cannot be copied and pasted. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, clear text form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- custom
Specifies the custom encryption to management interface.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
password
Syntax
password password [hash | hash2| custom]
no password
Context
[Tree] (config>subscr-mgmt>auth-policy password)
Full Context
configure subscriber-mgmt authentication-policy password
Description
This command sets a password that is sent with user-name in every RADIUS authentication request sent to the RADIUS server upon receipt of DHCP discover or request messages. If no password is configured, no password AVP is sent.
The no form of this command reverts to the default value.
Parameters
- password
Specifies a text string containing the password. Allowed values are any string up to 64 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.
- hash
Specifies that the key is entered in an encrypted form. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, clear text form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- hash2
Specifies that the key is entered in a more complex encrypted form that involves more variables than the key value alone, meaning that the hash2 encrypted variable cannot be copied and pasted. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, clear text form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- custom
Specifies the custom encryption to management interface.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
password
Syntax
password password [hash | hash2 | custom]
no password
Context
[Tree] (config>subscr-mgmt>diam-appl-plcy>nasreq password)
Full Context
configure subscriber-mgmt diameter-application-policy nasreq password
Description
This command sets a password that is sent with user-name in every RADIUS authentication request sent to the RADIUS server upon receipt of DHCP discover or request messages. If no password is provided, an empty password is sent.
The no form of this command reverts to the default value.
Parameters
- password
Specifies a text string containing the password. Allowed values are any string up to 64 characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.
- hash
Specifies that the key is entered in an encrypted form. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, clear text form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- hash2
Specifies that the key is entered in a more complex encrypted form that involves more variables than the key value alone, meaning that the hash2 encrypted variable cannot be copied and pasted. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, clear text form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- custom
Specifies the custom encryption to management interface.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
password
Syntax
password password [hash | hash2 | custom]
no password
Context
[Tree] (config>aaa>route-downloader password)
Full Context
configure aaa route-downloader password
Description
This command specifies the password that is used in the RADIUS access requests.
The no form of this command resets the password to the default which is an empty string.
Parameters
- password
Specifies a password string up to 32 characters.
- hash
Specifies the key is entered in an encrypted form. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, clear text form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- hash2
Specifies the key is entered in a more complex encrypted form that involves more variables than the key value alone, meaning that the hash2 encrypted variable cannot be copied and pasted. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, clear text form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- custom
Specifies the custom encryption to management interface.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
password
Syntax
password password [hash | hash2| custom]
no password
Context
[Tree] (config>aaa>radius-srv-plcy>servers>health-check>test-account password)
[Tree] (config>subscr-mgmt>vrgw>brg>brg-profile>radius-authentication password)
Full Context
configure aaa radius-server-policy servers health-check test-account password
configure subscriber-mgmt vrgw brg brg-profile radius-authentication password
Description
This command specifies the password that the test account will use to send access requests to probe the RADIUS servers.
Parameters
- password
Specifies the probing password up to 64 characters.
- hash
Specifies the key is entered in an encrypted form. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, clear text form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- hash2
Specifies the key is entered in a more complex encrypted form that involves more variables than the key value alone, meaning that the hash2 encrypted variable cannot be copied and pasted. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, clear text form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- custom
Specifies the custom encryption to management interface.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
password
Syntax
password
Context
[Tree] (config>system>security password)
Full Context
configure system security password
Description
Commands in this context configure password-related parameters.
Platforms
All
password
Syntax
password password [hash | hash2 | custom]
no password
Context
[Tree] (config>ipsec>rad-auth-plcy password)
Full Context
configure ipsec radius-authentication-policy password
Description
This command specifies the password that is used in the RADIUS access requests.
The no form of this command resets the password to its default of ALU and will be stored using hash/hash2 encryption.
Default
no password
Parameters
- password
Specifies a password string up to 64characters.
- hash
Specifies the key is entered in an encrypted form. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, clear text form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- hash2
Specifies the key is entered in a more complex encrypted form that involves more variables than the key value alone, meaning that the hash2 encrypted variable cannot be copied and pasted. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, clear text form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- custom
Specifies the custom encryption to management interface.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
password
Syntax
password password [hash | hash2 | custom]
no password
Context
[Tree] (config>aaa>isa-radius-plcy password)
Full Context
configure aaa isa-radius-policy password
Description
This command specifies the password that is used in the RADIUS access requests. It shall be specified as a string of up to 32 characters in length.
The no form of the command resets the password to its default of ALU and will be stored using hash/hash2 encryption.
Default
no password
Parameters
- password
Specifies a password string up to 32 characters.
- hash
Specifies the key is entered in an encrypted form. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, clear text form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified
- hash2
Specifies the key is entered in a more complex encrypted form that involves more variables than the key value alone, meaning that the hash2 encrypted variable cannot be copied and pasted. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, clear text form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- custom
Specifies the custom encryption to management interface.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
password
Syntax
password hex-string
no password
Context
[Tree] (config>li>x-interfaces>lics>lic>authentication password)
Full Context
configure li x-interfaces lics lic authentication password
Description
This command configures the password for the X1 and X2 interfaces.
The no form of this command reverts to the default.
Parameters
- hex-string
Specifies the password. Must contain exactly 32 hex nibbles.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
password
Syntax
password [password]
Context
[Tree] (config>system>security>user password)
Full Context
configure system security user password
Description
This command configures the user password for console and FTP access.
The password is stored in an encrypted format in the configuration file when specified. Passwords should be encased in double quotes (" ") at the time of the password creation. The double quote character (") is not accepted inside a password. It is interpreted as the start or stop delimiter of a string.
The password can be entered as plain text or a hashed value. SR OS can distinguish between hashed passwords and plain text passwords and take the appropriate action to store the password correctly.
config>system>security>user# password testuser1
The password is hashed by default.
For example:
config>system>security# user testuser1
config>system>security>user$ password xyzabcd1
config>system>security>user# exit
config>system>security# info
-------------------------------------
...
user "testuser1"
password "$2y$10$pFoehOg/tCbBMPDJ/
kqpu.8af0AoVGY2xsR7WFqyn5fVTnwRzGmOK"
exit
...
-------------------------------------
config>system>security#
The password command allows you also to enter the password as a hashed value.
For example:
config>system>security# user testuser1
config>system>security>user$ password "$2y$10$pFoehOg/tCbBMPDJ/
kqpu.8af0AoVGY2xsR7WFqyn5fVTnwRzGmOK"
config>system>security>user# exit
config>system>security# info
-------------------------------------
...
user "testuser1"
password "$2y$10$pFoehOg/tCbBMPDJ/kqpu.8af0AoVGY2xsR7WFqyn5fVTnwRzGmOK"
exit
...
-------------------------------------
config>system>security#
Parameters
- password
This is the password for the user that must be entered by this user during the login procedure. The minimum length of the password is determined by the minimum-length command. The maximum length can be up to 20 chars if unhashed, 32 characters if hashed. The complexity requirements for the password is determined by the complexity-rules command and must be followed; otherwise, the password will not be accepted.
All password special characters (#, $, spaces, and so on) must be enclosed within double quotes.
For example: config>system>security>user# password "south#bay?”
The question mark character (?) cannot be directly inserted as input during a telnet connection because the character is bound to the help command during a normal Telnet/console connection.
To insert a # or ? characters, they must be entered inside a notepad or clipboard program and then cut and pasted into the Telnet session in the password field that is encased in the double quotes as delimiters for the password.
If a password is entered without any parameters, a password length of zero is implied: (carriage return).
Platforms
All
password
Syntax
password password [hash | hash2 | custom]
no password
Context
[Tree] (bof password)
Full Context
bof password
Description
This command configures the password to access the BOF interactive menu at startup.
If a password is configured, the BOF interactive menu is accessible only when the correct password is entered. If the correct password is not entered in 30 s, the node reboots.
The no form of this command removes the configured password.
Default
no password
Parameters
- password
Specifies the password.
If the hash, hash2, or custom parameter is not configured, the password is entered in plaintext and the password length must be between 8 and 32 characters. A plaintext password cannot contain embedded nulls or end with " hash”, " hash2”, or " custom”.
If the hash, hash2, or custom parameter is configured, the password is hashed and the password length must be between 1 and 64 characters.
- hash
Keyword to specify that the password is entered in an encrypted form.
- hash2
Keyword to specify that the password is entered in a more complex encrypted form. The hash2 encryption scheme is node-specific and the password cannot be transferred between nodes.
- custom
Keyword to specify that the password uses custom encryption.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
password-history
password-history
Syntax
password-history {user user-name | all}
Context
[Tree] (admin>clear password-history)
Full Context
admin clear password-history
Description
This command is used to clear old passwords used by a specific user, or for all users.
Parameters
- user-name
Clears the password history information about the specified user, up to 32 characters.
- all
Clears the password history information for all users.
Platforms
All
pat-repetition
pat-repetition
Syntax
pat-repetition [tnc tnc-milli-seconds qos qos-milli-seconds poa poa-milli-seconds]
no pat-repetition
Context
[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>video>analyzer>alarms pat-repetition)
[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>channel>source-override>video>analyzer>alarms pat-repetition)
[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>channel>video>analyzer>alarms pat-repetition)
Full Context
configure mcast-management multicast-info-policy bundle video analyzer alarms pat-repetition
configure mcast-management multicast-info-policy bundle channel source-override video analyzer alarms pat-repetition
configure mcast-management multicast-info-policy bundle channel video analyzer alarms pat-repetition
Description
This command configures the analyzer to check for the program association table (PAT). It is expected that the PAT arrives periodically within a certain interval range. It is possible to configure the type of alarm that is raised when the PAT fails to arrive within the specified interval. As the delay increases between two consecutive PATs, the type of alarm raised becomes more critical, from TNC to POA.
Default
no pat-repetition
Parameters
- tnc-milli-seconds
Specifies the time, in milliseconds, for which a TNC alarm is raised if the interval between two consecutive PATs is greater than or equal to this configured value.
- qos-milli-seconds
Specifies the time, in milliseconds, for which a QoS alarm is raised if the interval between two consecutive PATs is greater than or equal to this configured value.
- poa-milli-seconds
Specifies the time, in milliseconds, for which a POA alarm is raised if the interval between two consecutive PATs is greater than or equal to this configured value.
Platforms
7450 ESS, 7750 SR-1, 7750 SR-7/12/12e, 7750 SR-1s, 7750 SR-2s, 7750 SR-7s, 7750 SR-14s
pat-syntax
pat-syntax
Syntax
[no] pat-syntax
Context
[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>channel>video>analyzer>alarms pat-syntax)
[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>video>analyzer>alarms pat-syntax)
[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>channel>source-override>video>analyzer>alarms pat-syntax)
Full Context
configure mcast-management multicast-info-policy bundle channel video analyzer alarms pat-syntax
configure mcast-management multicast-info-policy bundle video analyzer alarms pat-syntax
configure mcast-management multicast-info-policy bundle channel source-override video analyzer alarms pat-syntax
Description
This command configures the analyzer to check for PAT syntax errors.
Default
no pat-syntax
Platforms
7450 ESS, 7750 SR-1, 7750 SR-7/12/12e, 7750 SR-1s, 7750 SR-2s, 7750 SR-7s, 7750 SR-14s
path
path
Syntax
path xc-a lag-id xc-b lag-id
path pxc pxc-id
no path
Context
[Tree] (config>fwd-path-ext>fpe path)
Full Context
configure fwd-path-ext fpe path
Description
This command references a PXC (pair of PXC sub-ports) and consequently create an association between the PXC and the application which is referenced under the same FPE object. Each application will utilize the PXC in the form of an internal cross-connect. The exact use and internal provisioning of this cross-connect depends on the application itself.
The no form of this command removes the reference and association from the configuration.
Default
no path
Parameters
- xc-a lag-id
Specifies the LAG identifier associated with one side of the cross-connect. The operator has the freedom to associate xc-a with LAG ID containing either sub-ports.a or sub-ports.b. In other words, the system does not perform automatic check that will ensure a match between xc-a and the LAG ID containing sub-ports.a.
- xc-b lag-id
Specifies the LAG identifier associated with one side of the cross-connect. The operator has the freedom to associate xc-a with LAG ID containing either sub-ports.a or sub-ports.b.
- pxc-id
Specifies the PXC identifier, the PXC construct that contains a physical port in a loopback mode that provides the cross-connect capability. The system creates two paired sub-ports on top of this physical port and each of these two sub-ports forwards traffic in one direction over the loopback. One sub-port is associated with the transit side of the loopback, while the other sub-port is associated with the termination side (see PXC Configuration Guides for further explanation).
Platforms
All
path
Syntax
path path-id pxc pxc-id
path path-id xc-a lag-id xc-b lag-id
no path path-id
Context
[Tree] (config>fwd-path-ext>fpe>multi-path-list path)
Full Context
configure fwd-path-ext fpe multi-path-list path
Description
This command configures a multipath FPE forwarding path. A single path in a multipath FPE can contain a single PXC port or LAG of PXC ports.
The PXC references a physical port in loopback mode that provides the cross-connect capability. The system creates two paired subports on top of the physical port, each of which forwards traffic in one direction over the loopback. One subport is associated with the transit side of the loopback, while the other is associated with the termination side.
The no form of the command removes the path.
Parameters
- path-id
Specifies a path ID for the forwarding path.
- pxc-id
Specifies a dedicated PXC ID for the forwarding path.
- xc-a lag-id
Specifies the LAG ID associated with one side (transit or termination) of the cross-connect. The operator can associate xc-a with the LAG containing either subports.a or subports.b. The system does not enforce a match between xc-a and the LAG ID containing subports.a.
- xc-b lag-id
Specifies the LAG ID associated with the other side of the cross-connect (not designated for xc-a). The operator can associate xc-b with the LAG containing either subports.a or subports.b. The system does not enforce a match between xc-b and the LAG ID containing subports.b.
Platforms
All
path
Syntax
[no] path [sonet-sdh-index]
Context
[Tree] (config>port>sonet-sdh path)
Full Context
configure port sonet-sdh path
Description
This command defines the SONET/SDH path.
The no form of this command removes the specified SONET/SDH path.
This command is supported on TDM satellite.
Default
full channel (or clear channel)
Parameters
- sonet-sdh-index
Specifies the components making up the specified SONET/SDH path. Depending on the type of SONET/SDH port the sonet-sdh-index must specify more path indexes to specify the payload location of the path. The sonet-sdh-index differs for SONET and SDH ports.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
path
Syntax
[no] path path-index
Context
[Tree] (config>eth-tunnel path)
Full Context
configure eth-tunnel path
Description
This command configures one of the two paths supported under the Ethernet tunnel.
The no form of this command removes the path from under the Ethernet tunnel. If this is the last path, the associated SAP need to be unconfigured before the path can be deleted.
Default
no path
Parameters
- path-index
Specifies the identifier for the path.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
path
Syntax
path name
no path
Context
[Tree] (config>service>epipe>spoke-sdp-fec path)
Full Context
configure service epipe spoke-sdp-fec path
Description
This command specifies the explicit path, containing a list of S-PE hops, that should be used for this spoke SDP. The path-name should correspond to the name of an explicit path configured in the config>service>pw-routing context.
If no path is configured, then each next-hop of the MS-PW used by the spoke SDP will be chosen locally at each T-PE and S-PE.
Default
no path
Parameters
- name
The name of the explicit path to be used, as configured under the config>service>pw-routing context.
Platforms
All
path
Syntax
path path-index tag qtag[. qtag]
no path path-index
Context
[Tree] (config>service>epipe>sap>eth-tunnel path)
[Tree] (config>service>ipipe>sap>eth-tunnel path)
Full Context
configure service epipe sap eth-tunnel path
configure service ipipe sap eth-tunnel path
Description
This command configures Ethernet tunnel SAP path parameters.
The no form of this command removes the values from the configuration.
Parameters
- path-index
Specifies the path index value.
- qtag[.qtag]
Specifies the qtag value.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
path
Syntax
path path-index tag qtag[. qtag]
no path path-index
Context
[Tree] (config>service>vpls>sap>eth-tunnel path)
Full Context
configure service vpls sap eth-tunnel path
Description
This command configures Ethernet tunnel SAP path parameters.
The no form of this command removes the values from the configuration.
Parameters
- path-index
Specifies the path index value.
- tag qtag[.qtag]
Specifies the qtag value.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
path
Syntax
path path-name
no path path-name
Context
[Tree] (config>router>gmpls path)
Full Context
configure router gmpls path
Description
This command creates the path to be used for a GMPLS LSP. A path can be used by multiple GMPLS LSPs. A path can specify some or all hops from ingress to egress and they can be either strict or loose.
Paths are created in a no shutdown state. A path must be shut down before making any changes (adding or deleting hops) to the path. When a path is shut down, any GMPLS LSP using the path becomes operationally down.
The no form of this command deletes the path and all its associated configuration information. All the GMPLS LSPs that are currently using this path will be affected. A path must be shut down and unbound from all GMPLS LSPs using the path before it can be deleted. The no path path-name command will not result in any action except a warning message on the console indicating that the path may be in use.
Parameters
- path-name
Specifies a unique case-sensitive name label for the LSP path.
Platforms
7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
path
Syntax
[no] path
Context
[Tree] (debug>router>gmpls>event path)
Full Context
debug router gmpls event path
Description
This command enables and disables debugging for GMPLS Path events.
Platforms
7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
path
Syntax
path [detail]
no path
Context
[Tree] (debug>router>gmpls>packet path)
Full Context
debug router gmpls packet path
Description
This command enables debugging for GMPLS Path packets.
The no form of the command disables debugging for GMPLS Path packets.
Parameters
- detail
Keyword to produce debug output in greater detail.
Platforms
7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
path
Syntax
[no] path path-name
Context
[Tree] (config>router>mpls path)
Full Context
configure router mpls path
Description
This command creates the path to be used for an LSP. A path can be used by multiple LSPs. A path can specify some or all hops from ingress to egress and they can be either strict or loose. A path can also be empty (no path-name specified) in which case the LSP is set up based on IGP (best effort) calculated shortest path to the egress router. Paths are created in a shutdown state. A path must be shutdown before making any changes (adding or deleting hops) to the path. When a path is shutdown, any LSP using the path becomes operationally down.
To create a strict path from the ingress to the egress router, the ingress and the egress routers must be included in the path statement.
The no form of this command deletes the path and all its associated configuration information. All the LSPs that are currently using this path will be affected. Additionally all the services that are actively using these LSPs will be affected. A path must be shutdown and unbound from all LSPs using the path before it can be deleted. The no path path-name command will not result in any action except a warning message on the console indicating that the path may be in use.
Parameters
- path-name
Specifies a unique case-sensitive alphanumeric name label for the LSP path up to 32 characters in length.
Platforms
All
path
Syntax
path [detail]
no path
Context
[Tree] (debug>router>rsvp>event path)
Full Context
debug router rsvp event path
Description
This command debugs path-related events.
The no form of the command disables the debugging.
Parameters
- detail
Displays detailed information about path-related events.
Platforms
All
path
Syntax
path [detail]
no path
Context
[Tree] (debug>router>rsvp>packet path)
Full Context
debug router rsvp packet path
Description
This command enables debugging for RSVP path packets.
The no form of the command disables the debugging.
Parameters
- detail
Displays detailed information about path-related events.
Platforms
All
path
Syntax
path name [create]
no path name
Context
[Tree] (config>service>pw-routing path)
Full Context
configure service pw-routing path
Description
This command configures an explicit path between this T-PE and a remote T-PE. For each path, one or more intermediate S-PE hops must be configured. A path can be used by multiple multi-segment pseudowires. Paths are used by a 7450 ESS, 7750 SR, or 7950 XRS T-PE to populate the list of Explicit Route TLVs included in the signaling of a dynamic MS-PW.
A path may specify all or only some of the hops along the route to reach a T-PE.
The no form of the command removes a specified explicit path from the configuration.
Parameters
- path-name
Specifies a locally-unique case-sensitive alphanumeric name label for the MS-PW path of up to 32 characters in length.
Platforms
All
path
Syntax
path {a | b} [{port-id | lag-id} raps-tag qtag1[. qtag2]]
no path {a | b}
Context
[Tree] (config>eth-ring path)
Full Context
configure eth-ring path
Description
This command assigns the ring (major or sub-ring) path to a port and defines the Ring APS tag. Rings typically have two paths: a and b.
The no form of this command removes the path a or b.
Default
no path
Parameters
- port-id
Specifies the port ID.
- lag-id
Specifies the LAG ID.
- raps-tag
Specifies the member encapsulation.
- qtag1
Specifies the top or outer VLAN ID.
- qtag2
Specifies the bottom or inner VLAN ID.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
path
Syntax
path path-name [create]
no path name
Context
[Tree] (config>system>telemetry>sensor-groups>sensor-group path)
Full Context
configure system telemetry sensor-groups sensor-group path
Description
This command configures a sensor path for the specified sensor-group. Multiple sensor paths can be defined for a single sensor-group. The path is defined in the form of an XML Path (XPath) syntax that refers to single or multiple objects within the YANG model.
The no form of the command removes the specified explicit path from the configuration.
Parameters
- path-name
Specifies a sensor path, up to 512 characters.
- create
Keyword used to create the sensor path.
Platforms
All
path-b
path-b
Syntax
[no] path-b
Context
[Tree] (config>redundancy>mc>peer>mcr>ring path-b)
Full Context
configure redundancy multi-chassis peer mc-ring ring path-b
Description
This command specifies the set of upper-VLAN IDs associated with the SAPs that belong to path B with respect to load-sharing. All other SAPs belong to path A.
Default
If not specified, the default is an empty set.
Platforms
All
path-computation-method
path-computation-method
Syntax
path-computation-method path-computation-method
no path-computation-method
Context
[Tree] (config>router>mpls>lsp-template path-computation-method)
[Tree] (config>router>mpls>lsp path-computation-method)
Full Context
configure router mpls lsp-template path-computation-method
configure router mpls lsp path-computation-method
Description
This command configures the path computation method of a RSVP-TE or SR-TE LSP.
The user can select among the hop-to-label translation, the local CSPF or the PCE for a configured SR-TE LSP. For SR-TE LSP templates, the PCE option is supported with the SR-TE LSP template type on-demand-p2p-srte and not other template types.
The user can select among the IGP-based path, the local CSPF, or the PCE for a configured RSVP-TE LSP. The PCE option is not supported with the RSVP-TE LSP template.
By default, the IGP-based path is used for an RSVP-TE LSP and the hop-to-label path computation method is used for an SR-TE LSP.
The no form of this command returns to the default path computation method for the type of LSP.
Default
no path-computation-method
Parameters
- path-computation-method
Specifies the path computation method for the LSP.
Platforms
All
path-cost
path-cost
Syntax
path-cost sap-path-cost
no path-cost [sap-path-cost]
Context
[Tree] (config>service>vpls>sap>stp path-cost)
[Tree] (config>service>template>vpls-sap-template>stp path-cost)
[Tree] (config>service>vpls>spoke-sdp>stp path-cost)
Full Context
configure service vpls sap stp path-cost
configure service template vpls-sap-template stp path-cost
configure service vpls spoke-sdp stp path-cost
Description
This command configures the Spanning Tree Protocol (STP) path cost for the SAP or spoke-SDP.
The path cost is used by STP to calculate the path cost to the root bridge. The path cost in BPDUs received on the root port is incremented with the configured path cost for that SAP or spoke-SDP. When BPDUs are sent out of other egress SAPs or spoke-SDPs, the newly calculated root path cost is used. These are the values used for CIST when running MSTP.
STP suggests that the path cost is defined as a function of the link bandwidth. Since SAPs and spoke-SDPs are controlled by complex queuing dynamics, in the 7450 ESS, 7750 SR, and 7950 XRS the STP path cost is a purely static configuration.
The no form of this command returns the path cost to the default value.
Parameters
- path-cost
The path cost for the SAP or spoke-SDP
Platforms
All
path-cost
Syntax
path-cost sap-path-cost
no path-cost
Context
[Tree] (config>service>pw-template>stp path-cost)
Full Context
configure service pw-template stp path-cost
Description
This command configures the Spanning Tree Protocol (STP) path cost for the SAP or spoke SDP.
The path cost is used by STP to calculate the path cost to the root bridge. The path cost in BPDUs received on the root port is incremented with the configured path cost for that SAP or spoke SDP. When BPDUs are sent out other egress SAPs or spoke SDPs, the newly calculated root path cost is used. These are the values used for CIST when running MSTP.
STP suggests that the path cost is defined as a function of the link bandwidth. Since SAPs and spoke SDPs are controlled by complex queuing dynamics, the STP path cost is a purely static configuration.
The no form of this command returns the path cost to the default value.
Default
path-cost 10
Parameters
- path-cost
Specifies the path cost for the SAP or spoke SDP.
Platforms
All
path-destination
path-destination
Syntax
path-destination ip-address interface if-name
path-destination ip-address [next-hop ip-address]
no path-destination
Context
[Tree] (config>saa>test>type-multi-line>lsp-trace>sr-policy path-destination)
[Tree] (config>saa>test>type-multi-line>lsp-ping>sr-policy path-destination)
Full Context
configure saa test type-multi-line lsp-trace sr-policy path-destination
configure saa test type-multi-line lsp-ping sr-policy path-destination
Description
This command configures the IP address of the path destination from the range 127/8. When the LDP FEC prefix is IPv6, the user must enter a 127/8 IPv4 mapped IPv6 address, that is, in the range ::ffff:127/104.
The no form of this command removes the configuration.
Parameters
- ip-address
Specifies the IP address.
- if-name
Specifies the name of an IP interface, up 32 characters, to send the MPLS echo request to. The name must already exist in the config>router>interface context.
Platforms
All
path-discovery
path-discovery
Syntax
path-discovery
Context
[Tree] (config>test-oam>ldp-treetrace path-discovery)
Full Context
configure test-oam ldp-treetrace path-discovery
Description
This command creates the context to configure the LDP ECMP OAM path discovery.
The ingress LER builds the ECMP tree for a given FEC (egress LER) by sending LSP Trace messages and including the LDP IPv4 Prefix FEC TLV as well as the downstream mapping TLV. It inserts an IP address range drawn from the 127/8 space. When received by the downstream LSR, it uses this range to determine which ECMP path is exercised by any IP address or a sub-range of addresses within that range based on its internal hash routine. When the MPLS Echo reply is received by the ingress LER, it records this information and proceeds with the next echo request message targeted for a node downstream of the first LSR node along one of the ECMP paths. The sub-range of IP addresses indicated in the initial reply is used since the objective is to have the LSR downstream of the ingress LER pass this message to its downstream node along the first ECMP path.
The user configures the frequency of running the tree discovery using the command config>test-oam>ldp-treetrace>path-discovery>interval.
The ingress LER gets the list of FECs from the LDP FEC database. New FECs are added to the discovery list at the next tree discovery and not when they are learned and added into the FEC database. The maximum number of FECs to be discovered with the tree building feature is limited to 500. The user can configure FECs to include or exclude using a policy profile by applying the command config>test-oam>ldp-treetrace>path-discovery>policy-statement.
Platforms
All
path-excl
path-excl
Syntax
[no] path-excl
Context
[Tree] (config>redundancy>mc>peer>mcr>ring path-excl)
Full Context
configure redundancy multi-chassis peer mc-ring ring path-excl
Description
This command specifies the set of upper-VLAN IDs associated with the SAPs that are to be excluded from control by the multi-chassis ring.
Default
If not specified, the default is an empty set.
Platforms
All
path-id
path-id
Syntax
path-id {lsp-num lsp-num | working-path | protect-path [src-global-id src-global-id] src-node-id src-node-id src-tunnel-num src-tunnel-num [dest-global-id dest-global-id] dest-node-id dest-node-id [dest-tunnel-num dest-tunnel-num]}
no path-id
Context
[Tree] (config>router>mpls>mpls-tp>transit-path path-id)
Full Context
configure router mpls mpls-tp transit-path path-id
Description
This command configures path ID for an MPLS-TP transit path at an LSR. The path ID is equivalent to the MPLS-TP LSP ID and is used to generate the maintenance entity group intermediate point (MIP) identifier for the LSP at the LSR. A path-id must be configured for on-demand OAM to verify an LSP at the LSR.
The path-id must contain at least the following parameters: lsp-num, src-node-id, src-global-id, src-tunnel-num, dest-node-id.
The path-id must be unique on a node. It is recommended that his is also configured to be a globally unique value.
The no form of this command removes the path ID from the configuration.
Default
no path-id
Parameters
- lsp-num
Specifies the LSP number.
- src-global-id
Specifies the source global ID.
- src-node-id
Specifies the source node ID.
- src-tunnel-num
Specifies the source tunnel number.
- dest-global-id
Specifies the destination global ID. If the destination global ID is not entered, then it is set to the same value as the source global ID.
- dest-node-id
Specifies the destination node ID.
- dest-tunnel-num
Specifies the destination tunnel number. If the destination tunnel number is not entered, then it is set to the same value as the source tunnel number.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
path-mtu
path-mtu
Syntax
path-mtu [bytes]
no path-mtu bytes
Context
[Tree] (config>service>sdp path-mtu)
Full Context
configure service sdp path-mtu
Description
This command configures the Maximum Transmission Unit (MTU) in bytes that the Service Distribution Point (SDP) can transmit to the far-end device router without packet dropping or IP fragmentation overriding the SDP-type default path-mtu.
The default SDP-type path-mtu can be overridden on a per SDP basis. Dynamic maintenance protocols on the SDP like RSVP may override this setting.
If the physical mtu on an egress interface or PoS channel indicates the next hop on an SDP path cannot support the current path-mtu, the operational path-mtu on that SDP will be modified to a value that can be transmitted without fragmentation.
The no form of this command removes any path-mtu defined on the SDP and the SDP will use the system default for the SDP type.
Default
no path-mtu — Specifies the default path-mtu defined on the system for the type of SDP is used.
Parameters
- bytes
Specifies the bytes.
Platforms
All
path-mtu-discovery
path-mtu-discovery
Syntax
[no] path-mtu-discovery
Context
[Tree] (config>router>ldp>tcp-session-params>peer-transport path-mtu-discovery)
Full Context
configure router ldp tcp-session-parameters peer-transport path-mtu-discovery
Description
This command enables Path MTU discovery for the associated TCP connections. When enabled, the MTU for the associated TCP session is initially set to the egress interface MTU. The DF bit is also set so that if a router along the path of the TCP connection cannot handle a packet of a particular size without fragmenting, it sends back an ICMP message to set the path MTU for the given session to a lower value that can be forwarded without fragmenting.
If one or more transport addresses used in the Hello adjacencies to the same peer LSR are different from the LSR-ID value, the user must add each of the transport addresses to the path MTU discovery configuration as a separate peer. This means when the TCP connection is bootstrapped by a given Hello adjacency, the path MTU discovery can operate over that specific TCP connection by using its specific transport address.
Default
no path-mtu-discovery
Platforms
All
path-mtu-discovery
Syntax
[no] path-mtu-discovery
Context
[Tree] (config>router>bgp path-mtu-discovery)
[Tree] (config>router>bgp>group path-mtu-discovery)
[Tree] (config>router>bgp>group>neighbor path-mtu-discovery)
Full Context
configure router bgp path-mtu-discovery
configure router bgp group path-mtu-discovery
configure router bgp group neighbor path-mtu-discovery
Description
This command enables Path MTU Discovery (PMTUD) for the associated TCP connections.
When enabled, PMTUD is activated toward an IPv4 BGP neighbor. The Don’t Fragment (DF) bit is set in the IP header of all IPv4 packets sent to the peer. If any device along the path toward the peer cannot forward the packet because the IP MTU of the interface is smaller than the IP packet size, the device drops the packet and sends an ICMP or ICMPv6 error message encoding the interface MTU. When the router receives the ICMP or ICMPv6 message, it lowers the TCP maximum segment size limit from the previous value to accomodate the IP MTU constraint.
When PMTUD is disabled and there is no tcp-mss configuration to associate with a BGP neighbor (in either the BGP configuration or the first-hop IP interface configuration), the router advertises a TCP MSS option of only 1024 bytes, limiting received TCP segments to that size.
The no form of this command disables PMTUD.
Default
no path-mtu-discovery
Platforms
All
path-preference
path-preference
Syntax
path-preference value
no path-preference
Context
[Tree] (config>router>mpls>lsp>secondary path-preference)
Full Context
configure router mpls lsp secondary path-preference
Description
This command enables the use of path preference among configured standby secondary paths per LSP. If all standby secondary paths have a default path-preference value then a non-standby secondary path will remain the active path while a standby secondary is available. A standby secondary path configured with the highest priority (for example, the lowest path-preference value) is made the active path when the primary is not in use. If multiple standby secondary paths have the same, lowest, path-preference value then the system will select the path with the highest up-time. Path preference can only be configured on the standby secondary paths.
The no form of this command resets the path-preference to the default value.
Default
path-preference 255
Parameters
- value
Specifies an alternate path for the LSP if the primary path is not available.
Platforms
All
path-probing
path-probing
Syntax
path-probing
Context
[Tree] (config>test-oam>ldp-treetrace path-probing)
Full Context
configure test-oam ldp-treetrace path-probing
Description
This command creates the context to configure the LDP tree trace path probing phase.
The periodic path exercising runs in the background to test the LDP ECMP paths discovered by the path discovery capability. The probe used is an LSP Ping message with an IP address drawn from the sub-range of 127/8 addresses indicated by the output of the tree discovery for this FEC.
The user configures the frequency of running the path probes using the config>test-oam>ldp-treetrace>path-probing>interval command. If an I/F is down on the ingress LER performing the LDP tree trace, then LSP Ping probes that normally go out this interface are not sent but the ingress LER node does not raise alarms.
The LSP Ping routine updates the content of the MPLS echo request message, specifically the IP address, as soon as the LDP ECMP path discovery phase has output the results of a new computation for the path in question.
Platforms
All
path-profile
path-profile
Syntax
path-profile profile-id [path-group group-id]
no path-profile profile-id
Context
[Tree] (config>router>mpls>lsp-template path-profile)
[Tree] (config>router>mpls>lsp path-profile)
Full Context
configure router mpls lsp-template path-profile
configure router mpls lsp path-profile
Description
This command configures the PCE path profile and path group ID.
The PCE supports the computation of disjoint paths for two different LSPs originating and/or terminating on the same or different PE routers. To indicate this constraint to the PCE, the user must configure the PCE path profile ID and path group ID to which the PCE computed or PCE controlled LSP belongs to. These parameters are passed transparently by the PCC to the PCE and are thus opaque data to the router.
The association of the optional path-group ID is to allow the PCE to determine the profile ID that must be used with this path-group ID. One path-group ID is allowed per profile ID. The user can, however, enter the same path-group ID with multiple profile IDs by executing this command multiple times. A maximum of five path-profile [path-group] entries can be associated with the same LSP.
The no form of this command removes the path profile association with the LSP.
Parameters
- profile-id
Specifies the profile ID.
- path-group group-id
Specifies the path group ID.
Platforms
All
path-restoration-time
path-restoration-time
Syntax
path-restoration-time minutes
no path-restoration-time
Context
[Tree] (config>subscr-mgmt>pfcp-association path-restoration-time)
Full Context
configure subscriber-mgmt pfcp-association path-restoration-time
Description
This command configures the time sessions are kept after a PFCP path failure is detected. When the timer expires, or if it is not configured, all sessions associated with the path are removed. If the path recovers without a restart before the timer expires, the timer is canceled, and no sessions are removed.
The no form of this command removes the path restoration configuration.
Default
no path-restoration-time
Parameters
- minutes
Specifies the time, in minutes, that sessions are kept after a PFCP path failure. This timer should be configured to a value that is at least twice the sum of the heartbeat interval plus the total heartbeat timeout (heartbeat retries x heartbeat timeout = N1 x T1).
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
path-threshold
path-threshold
Syntax
path-threshold num-paths
no path-threshold
Context
[Tree] (config>eth-tunnel>lag-emulation path-threshold)
Full Context
configure eth-tunnel lag-emulation path-threshold
Description
This command configures the behavior for the eth-tunnel if the number of operational members is equal to or below a threshold level
Default
no path-threshold
Parameters
- num-paths
Specifies the threshold for the Ethernet Tunnel group.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
path-type
path-type
Syntax
path-type {ibgp | ebgp}
no path-type
Context
[Tree] (config>router>policy-options>policy-statement>entry>from path-type)
Full Context
configure router policy-options policy-statement entry from path-type
Description
This command matches BGP routes based on their path type (EBGP or IBGP). A route learned from an EBGP peer has path-type ebgp. A route learned from an IBGP or confed-EBGP peer has path-type ibgp.
A non-BGP route does not match a policy entry if it contains the path-type command.
Default
no path-type
Parameters
- ibgp
Matches routes from internal BGP peers.
- ebgp
Matches routes from external BGP peers.
Platforms
All
patherr
patherr
Syntax
patherr [detail]
no patherr
Context
[Tree] (debug>router>gmpls>packet patherr)
Full Context
debug router gmpls packet patherr
Description
This command enables debugging for GMPLS PathErr packets.
The no form of the command disables debugging for GMPLS PathErr packets.
Parameters
- detail
Keyword to produce debug output in greater detail.
Platforms
7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
patherr
Syntax
patherr [detail]
no patherr
Context
[Tree] (debug>router>rsvp>packet patherr)
Full Context
debug router rsvp packet patherr
Description
This command debugs path error packets.
The no form of the command disables the debugging.
Parameters
- detail
Displays detailed information about path error packets.
Platforms
All
pathtear
pathtear
Syntax
pathtear [detail]
no pathtear
Context
[Tree] (debug>router>gmpls>packet pathtear)
Full Context
debug router gmpls packet pathtear
Description
This command enables debugging for GMPLS PathTear packets.
The no form of the command disables debugging for GMPLS PathTear packets.
Parameters
- detail
Keyword to produce debug output in greater detail.
Platforms
7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
pathtear
Syntax
pathtear [detail]
no pathtear
Context
[Tree] (debug>router>rsvp>packet pathtear)
Full Context
debug router rsvp packet pathtear
Description
This command debugs path tear packets.
The no form of the command disables the debugging.
Parameters
- detail
Displays detailed information about path tear packets.
Platforms
All
pattern
pattern
Syntax
pattern pad-value
no pattern
Context
[Tree] (config>oam-pm>session>ip pattern)
Full Context
configure oam-pm session ip pattern
Description
This command configures the pattern value to be repeated in the padding portion of the TWAMP Light packet.
The no form of this command uses an incrementing byte pattern beginning with 00 and ending with FF, wrapping back to 00.
Default
pattern 0
Parameters
- pad-value
Specifies the specific pattern to use.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
pattern
Syntax
pattern pad-value
no pattern
Context
[Tree] (config>oam-pm>session>mpls pattern)
Full Context
configure oam-pm session mpls pattern
Description
This command configures the pattern value to be repeated in the padding portion of pad-tlv length field of the dm PDU.
The no form of this command uses an incrementing byte pattern beginning with 00 and ending with FF, wrapping back to 00.
Parameters
- pad-value
Specifies a two octet pattern to be repeated to fill the padding field of each echo request packet launched for each test belonging to the specified session. For example, if 255 is specified, the padding field is filled with the octet values 00, FF, 00, FF, ... (hexadecimal).
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
payload
payload
Syntax
payload {sts3 | tug3 | ds3 | e3 | vt2 | vt15 | ds1 | e1}
Context
[Tree] (config>port>sonet-sdh>path payload)
Full Context
configure port sonet-sdh path payload
Description
This command specifies if the associated SONET/SDH path is an asynchronous circuit or a virtual tributary group (VT). This command is only applicable to channelized MDAs.
This command is supported on TDM satellite, however the sts3, ds3, and e3 parameters are not supported.
Parameters
- sts3
Configures STS3/STM1 payload as clear channel.
- tu3
Configures STS3/STM1 payload as Tributary Unit Group 3 (TUG3).
- ds3
Configures the port or channel as DS-3 STS1/VC3 payload as DS-3.
- e3
Configures the port or channel as E-3 STS1/VC3 payload as E-3.
- vt2
Configures the path STS1 payload as vt2 as a virtual tributary group. Only allowed on STS-1 nodes (SONET VT container).
- vt15
Configures the path as a virtual tributary group. Only allowed on STS-1 nodes (SONET VT container).
- ds1
Configures the port or channel as DS1.vt15 or vt2 payload as DS-1.
- e1
Configures VT2 payload as E-1.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
pbb
pbb
pbb
Syntax
pbb
Context
[Tree] (debug>oam>build-packet>packet>field-override>header pbb)
[Tree] (config>test-oam>build-packet>header pbb)
Full Context
debug oam build-packet packet field-override header pbb
configure test-oam build-packet header pbb
Description
This command configures a test Provider Backbone Bridge (PBB) packet header to be launched by the OAM find-egress tool.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
pbb-etype
pbb-etype
Syntax
pbb-etype [ethertype-value]
no pbb-etype
Context
[Tree] (config>port>ethernet pbb-etype)
Full Context
configure port ethernet pbb-etype
Description
This command configures the Ethertype used for PBB encapsulation.
Default
no pbb-etype
Parameters
- ethertype-value
Specifies the Ethertype value in the form of 0x600 to 0xfff.
Platforms
All
pbb-etype
Syntax
pbb-etype type
no pbb-etype [type]
Context
[Tree] (config>service>sdp pbb-etype)
Full Context
configure service sdp pbb-etype
Description
This command configures the Ethertype used for PBB.
Default
no pbb-etype
Parameters
- type
Specifies the Ethertype.
Platforms
All
pbr-down-action-override
pbr-down-action-override
Syntax
pbr-down-action-override filter-action
no pbr-down-action-override
Context
[Tree] (config>filter>mac-filter>entry pbr-down-action-override)
[Tree] (config>filter>ipv6-filter>entry pbr-down-action-override)
[Tree] (config>filter>ip-filter>entry pbr-down-action-override)
Full Context
configure filter mac-filter entry pbr-down-action-override
configure filter ipv6-filter entry pbr-down-action-override
configure filter ip-filter entry pbr-down-action-override
Description
This command allows overriding the default action that is applied for entries with PBR/PBF action defined, when the PBR/PBF target is down.
The no form of the command preserves default behavior when PBR/PBF target is down.
Default
no pbr-down-action-override
Parameters
- filter-action
Specifies the packets matching the entry.
drop — Specifies that packets matching the entry will be dropped if PBR/PBF target is down.
forward — Specifies that packets matching the entry will be forwarded if PBR/PBF target is down.
filter-default-action — Specifies that packets matching the entry will be processed as per default-action configuration for this filter if PBR/PBF target is down.
Platforms
All
pcap
pcap
Syntax
pcap session-name [create]
no pcap session-name
Context
[Tree] (config>mirror>mirror-dest pcap)
Full Context
configure mirror mirror-dest pcap
Description
This command specifies a PCAP instance used for packet capture.
The no form of this command removes the PCAP instance and stops the packet capture and file transfer session.
Parameters
- session-name
Specifies the session name, up to 32 characters.
Platforms
All
pcap
Syntax
pcap session-name
Context
[Tree] (debug pcap)
Full Context
debug pcap
Description
This command specifies the session for the packet capture process.
Parameters
- session-name
Specifies the session name, up to 32 characters.
Platforms
All
pcc
pcc
Syntax
[no] pcc
Context
[Tree] (debug>router>mpls>event pcc)
Full Context
debug router mpls event pcc
Description
This command debugs pcc events.
The no form of the command disables the debugging.
Platforms
All
pcc
Syntax
pcc
Context
[Tree] (config>router>pcep pcc)
Full Context
configure router pcep pcc
Description
Commands in this context configure PCC parameters.
Platforms
All
pce
pce
Syntax
pce
Context
[Tree] (config>router>pcep pce)
Full Context
configure router pcep pce
Description
Commands in this context configure PCE parameters.
Platforms
VSR-NRC
pce-associations
pce-associations
Syntax
pce-associations
Context
[Tree] (config>router>pcep>pcc pce-associations)
Full Context
configure router pcep pcc pce-associations
Description
Commands in this context configure PCE association groups.
Platforms
All
pce-associations
Syntax
pce-associations
Context
[Tree] (config>router>mpls>lsp-template pce-associations)
[Tree] (config>router>mpls>lsp pce-associations)
Full Context
configure router mpls lsp-template pce-associations
configure router mpls lsp pce-associations
Description
Commands in this context configure LSP binding with one or more PCEP association groups.
Platforms
All
pce-control
pce-control
Syntax
[no] pce-control
Context
[Tree] (config>router>mpls>lsp-template pce-control)
[Tree] (config>router>mpls>lsp pce-control)
Full Context
configure router mpls lsp-template pce-control
configure router mpls lsp pce-control
Description
This command enables a PCE controlled LSP mode of operation. The pce-control option means the router delegates full control of the LSP to the PCE (PCE controlled). Enabling it means the PCE is acting in stateful-active mode for this LSP and the PCE will be able to reroute the path following a failure or re-optimize the path and update the router without a request from the router.
The user can delegate CSPF and non-CSPF LSPs, or LSPs that have the path-computation-method pce option enabled or disabled. The LSP maintains its latest active path computed by PCE or the router at the time it is delegated. The PCE only makes an update to the path at the next network event or reoptimization.
When configured to no, the PCE controlled mode of operation for the LSP has not effect.
Default
no pce-control
Platforms
All
pce-initiated-lsp
pce-initiated-lsp
Syntax
[no] pce-initiated-lsp
Context
[Tree] (config>router>mpls pce-initiated-lsp)
Full Context
configure router mpls pce-initiated-lsp
Description
This command creates a context to configure support for PCE-initiated LSPs.
The no form of this command removes PCE-initiated LSP support. All PCE-initiated LSPs are deleted.
Platforms
All
pce-report
pce-report
Syntax
pce-report rsvp-te {enable | disable}
pce-report sr-te {enable | disable}
Context
[Tree] (config>router>mpls pce-report)
Full Context
configure router mpls pce-report
Description
This command separately configures the reporting modes to a PCE for RSVP-TE or SR-TE LSPs. The PCC LSP database is synchronized with the PCE LSP database using the PCEP PCRpt (PCE Report) message for PCC-controlled, PCE-computed, and PCE-controlled LSPs.
The global MPLS level pce-report command can be used to enable or disable PCE reporting for all SR-TE LSPs or RSVP-TE LSPs during PCE LSP database synchronization. This configuration is inherited by all LSPs of the specified type. The PCC reports both CSPF and non-CSPF LSPs. The default value is disabled for both types of LSP. This default value is meant to control the introduction of the PCE into an existing network and to let the operator decide if all LSPs of a particular type need to be reported.
The LSP-level pce-report command overrides the global configuration for the reporting of LSPs to the PCE. The default value is to inherit the global MPLS level value. The enable or disable value allows for the override of the inherited value. The inherit value explicitly resets the LSP to inherit the global configuration for that LSP type.
If PCE reporting is disabled for the LSP, either due to inheritance or due to LSP-level configuration, then enabling the pce-control option for the LSP has no effect.
Default
pce-report rsvp-te disable
pce-report sr-te disable
Parameters
- rsvp-te
Specifies the PCE reporting mode for all TE LSPs of RSVP-TE type.
- sr-te
Specifies the PCE reporting mode for all TE LSPs of SR-TE type.
Platforms
All
pce-report
Syntax
pce-report {enable | disable | inherit}
Context
[Tree] (config>router>mpls>lsp-template pce-report)
[Tree] (config>router>mpls>lsp pce-report)
Full Context
configure router mpls lsp-template pce-report
configure router mpls lsp pce-report
Description
This command separately configures the reporting modes to a PCE for RSVP-TE or SR-TE LSPs.
The PCC LSP database is synchronized with the PCE LSP database using the PCEP PCRpt (PCE Report) message for PCC-controlled, PCE-computed and PCE-controlled LSPs.
The global MPLS-level pce-report command can be used to enable or disable PCE reporting for all SR-TE LSPs or RSVP-TE LSPs during PCE LSP database synchronization. This configuration is inherited by all LSPs of the specified type. The PCC reports both CSPF and non-CSPF LSPs. The default value is disabled for both types of LSP. This default value is meant to control the introduction of the PCE into an existing network and to let the operator decide if all LSPs of a particular type need to be reported.
The LSP-level pce-report command overrides the global configuration for the reporting of LSP to the PCE. The default value is to inherit the global MPLS level value. The enable or disable value allows for the override of the inherited value. The inherit value explicitly resets the LSP to inherit the global configuration for that LSP type.
If PCE reporting is disabled for the LSP, either due to inheritance or due to LSP-level configuration, then enabling the pce-control option for the LSP has no effect.
Default
pce-report inherit
Parameters
- enable
Enables PCE reporting.
- disable
Disables PCE reporting.
- inherit
Inherits the global configuration for PCE reporting.
Platforms
All
pcep
pcep
Syntax
[no] pcep
Context
[Tree] (config>router pcep)
Full Context
configure router pcep
Description
This command enables Path Computation Element communications Protocol (PCEP), and enters the context to configure PCEP parameters.
The no form of the command disables PCEP.
Platforms
All
pcm
pcm
Syntax
[no] pcm pcm-slot [chassis chassis-id]
Context
[Tree] (config>system>pwr-mgmt pcm)
Full Context
configure system power-management pcm
Description
This command sets the PCM slot number.
Parameters
- pcm-slot
Identifies the PCM slot.
- chassis-id
Specifies chassis ID for the router chassis.
Platforms
7950 XRS-20e
pcm-type
pcm-type
Syntax
[no] pcm-type {dual | quad}
Context
[Tree] (cfg>sys>pwr-mgmt>pcm pcm-type)
Full Context
configure system power-management pcm pcm-type
Description
This command sets the PCM type.
Parameters
- dual
Specifies the dual PCM type.
- quad
Specifies the quad PCM type.
Platforms
7950 XRS-20e
pcp
pcp
Syntax
pcp
Context
[Tree] (debug>router pcp)
Full Context
debug router pcp
Description
This command enables debugging for the PCP servers.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
pcp-server
pcp-server
Syntax
pcp-server
Context
[Tree] (config>router pcp-server)
Full Context
configure router pcp-server
Description
Commands in this context configure a Port Control Policy (PCP) server.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
pcp-server
Syntax
pcp-server name
Context
[Tree] (debug>router>pcp pcp-server)
Full Context
debug router pcp pcp-server
Description
This command enables debugging for the PCP servers.
Parameters
- name
Debugs the PCP server associated with the specified name, up to 32 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
pcp-server-policy
pcp-server-policy
Syntax
pcp-server-policy name [create]
no pcp-server-policy name
Context
[Tree] (config>service>nat pcp-server-policy)
Full Context
configure service nat pcp-server-policy
Description
This command configures a PCP server policy name.
The no form of the command removes the name from the configuration.
Parameters
- name
Specifies a PCP server policy name up to 32 characters.
- create
Keyword used to create the PCP server policy.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
pcp-server-policy
Syntax
pcp-server-policy name
no pcp-server-policy
Context
[Tree] (config>router>pcp-server>server pcp-server-policy)
Full Context
configure router pcp-server server pcp-server-policy
Description
This command configures the PCP server policy.
The no form of this command reverts to the default value.
Default
no pcp-server-policy
Parameters
- name
Specifies the PCP server policy name, up to 32 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
pcr-repetition
pcr-repetition
Syntax
pcr-repetition [tnc tnc-milli-seconds qos qos-milli-seconds poa poa-milli-seconds]
no pcr-repetition
Context
[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>channel>video>analyzer>alarms pcr-repetition)
[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>video>analyzer>alarms pcr-repetition)
[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>channel>source-override>video>analyzer>alarms pcr-repetition)
Full Context
configure mcast-management multicast-info-policy bundle channel video analyzer alarms pcr-repetition
configure mcast-management multicast-info-policy bundle video analyzer alarms pcr-repetition
configure mcast-management multicast-info-policy bundle channel source-override video analyzer alarms pcr-repetition
Description
This command configures the analyzer to check for the program clock reference (PCR). It is expected that the PCR arrives periodically within a certain interval range. It is possible to configure the type of alarm that is raised when the PCR fails to arrive within the specified interval. As the delay increases between two consecutive PCRs, the type of alarm raised becomes more critical, from TNC to POA.
Default
no pcr-repetition
Parameters
- tnc-milli-seconds
Specifies the time, in milliseconds, for which a TNC alarm is raised if the interval between two consecutive PCRs is greater than or equal to this configured value.
- qos-milli-seconds
Specifies the time, in milliseconds, for which a QoS alarm is raised if the interval between two consecutive PCRs is greater than or equal to this configured value.
- poa-milli-seconds
Specifies the time, in milliseconds, for which a POA alarm is raised if the interval between two consecutive PCRs is greater than or equal to this configured value.
Platforms
7450 ESS, 7750 SR-1, 7750 SR-7/12/12e, 7750 SR-1s, 7750 SR-2s, 7750 SR-7s, 7750 SR-14s
pd-managed-route
pd-managed-route
Syntax
pd-managed-route [next-hop {ipv4 | ipv6}]
no pd-managed-route
Context
[Tree] (config>service>ies>sub-if>grp-if>ipv6>dhcp6 pd-managed-route)
[Tree] (config>service>vprn>sub-if>ipv6>dhcp6 pd-managed-route)
[Tree] (config>service>vprn>sub-if>grp-if>ipv6>dhcp6 pd-managed-route)
[Tree] (config>service>ies>sub-if>ipv6>dhcp6 pd-managed-route)
Full Context
configure service ies subscriber-interface group-interface ipv6 dhcp6 pd-managed-route
configure service vprn subscriber-interface ipv6 dhcp6 pd-managed-route
configure service vprn subscriber-interface group-interface ipv6 dhcp6 pd-managed-route
configure service ies subscriber-interface ipv6 dhcp6 pd-managed-route
Description
This command enables DHCP IA-PD (delegated prefix) to be modeled as managed (framed) route instead of as a subscriber-host. Antispoof filtering for the subscriber host associated with the IA-PD route must be set to nh-mac. The subscriber specific parameters (such as sla-profile or sub-profile) are ignored during the authentication phase because IA-PD is not modeled as a subscriber host. Other subscriber host-specific functions (for example, host overrides via CoA or host accounting) are not possible with a PD as the managed route.
By default, or when configured with the next-hop ipv6 parameter, the next-hop for PD managed route is an IPv6 WAN sub-host (DHCP IA-NA or SLAAC) with the same mac address as the one in the DHCP lease state for the managed IA-PD. The DHCP IA-NA next-hop host will always override the SLAAC next-hop host if both are available. If the IPv6 next-hop is not present when the framed IA-PD is instantiated, the IA-PD is set up but the PD managed route will not be installed in the IPv6 route table and the DHCPv6 lease state for the IA-PD will have the managed route status (DHCP6 MRt Status) set to "noNextHop”.
When configured with the next-hop ipv4 parameter the next-hop for PD managed route is a DHCPv4 sub-host that belongs to the same IPoE session or PPPoE session. For IPoE, ipoe-session must be enabled on the group-interface. If ipoe-session is disabled, an IPv4 next-hop will not be found. If the IPv4 next-hop is not found or not present at the time when the framed IA-PD is instantiated, the IA-PD is set up but the PD managed route is not installed in the IPv6 route table. In this case, the DHCPv6 lease state for the IA-PD will have the managed route status (DHCP6 MRt Status) set to noNextHop.
IPv6 filters, QoS IPv6 criteria, and IPv6 multicast are not supported for DHCPv6 IA-PD as managed route pointing to an IPv4 subscriber host as next-hop.
The DHCP IA-PD modeled as a route is displayed differently than regular subscriber hosts in show commands related to subscriber host state. The PD managed route is always shown directly below the host it is using as the next hop. The forwarding status of the PD managed route is also shown, where (N) indicate that the PD managed route is not forwarding. In addition, DHCP IA-PD route is displayed as a managed route for the corresponding IPv6 subscriber host (DHCP IA-NA or SLAAC) or DHCPv4 subscriber host.
DHCP IA-PD information for managed IA-PD route is still maintained in the DHCPv6 lease state.
The no form of this command reverts to the default.
Parameters
- next-hop
Specifies the next-hop type for the DHCP IA-PD managed route
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
pdn-connection-id
pdn-connection-id
Syntax
[no] pdn-connection-id
Context
[Tree] (config>subscr-mgmt>diam-appl-plcy>gx>include-avp pdn-connection-id)
Full Context
configure subscriber-mgmt diameter-application-policy gx include-avp pdn-connection-id
Description
This command enables the inclusion of the PDN-Connection-Id AVP, which contains the APN as signaled in the incoming GTP setup message.
The no form of this command disables the inclusion of the AVP.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
pdn-type
pdn-type
Syntax
pdn-type {ipv4 | ipv6 | ipv4v6}
no pdn-type
Context
[Tree] (config>service>vprn>gtp>uplink pdn-type)
[Tree] (config>router>gtp>uplink pdn-type)
Full Context
configure service vprn gtp uplink pdn-type
configure router gtp uplink pdn-type
Description
This command configures the PDP type to be signaled in GTP, determining which addresses are requested from the P-GW/GGSN and which hosts are set up afterwards. This can be overridden by RADIUS. If the ipv4v6 keyword is used, the P-GW/GGSN can fall back to either IPv4 or IPv6.
The no form of this command reverts to the default configuration.
Default
pdn-type ipv4
Parameters
- ipv4
Specifies the GTP connection requests an IPv4 address.
- ipv6
Specifies the GTP connection requests an IPv6 address.
- ipv4v6
Specifies the GTP connection requests both an IPv4 and an IPv6 address.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
pdp-context-type
pdp-context-type
Syntax
[no] pdp-context-type
Context
[Tree] (config>subscr-mgmt>diam-appl-plcy>gy>avp pdp-context-type)
Full Context
configure subscriber-mgmt diameter-application-policy gy include-avp pdp-context-type
Description
This command includes the [3GPP-1247] PDP-Context-Type AVP in Diameter DCCA CCR-Initial messages.
The no form of this command removes the PDP-Context-Type AVP from the Diameter DCCA CCR-Initial messages.
Default
pdp-context-type
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
pe-id-mac-flush-interop
pe-id-mac-flush-interop
Syntax
[no] pe-id-mac-flush-interop
Context
[Tree] (config>router>ldp>session-params>peer pe-id-mac-flush-interop)
Full Context
configure router ldp session-parameters peer pe-id-mac-flush-interop
Description
This command enables the addition of the PE-ID TLV in the LDP MAC withdrawal (mac-flush) message, under certain conditions, and modifies the mac-flush behavior for interoperability with other vendors that do not support the flush-all-from-me vendor-specific TLV. This flag can be enabled on a per LDP peer basis and allows the flush-all-from-me interoperability with other vendors. When the pe-id-mac-flush-interop flag is enabled for a given peer, the current mac-flush behavior is modified in terms of mac-flush generation, mac-flush propagation and behavior upon receiving a mac-flush.
The mac-flush generation will be changed depending on the type of event and according to the following rules:
Any all-from-me mac-flush event will trigger a mac-flush all-but-mine message (RFC 4762 compliant format) with the addition of a PE-ID TLV. The PE-ID TLV contains the IP address of the sending PE.
Any all-but-mine mac-flush event will trigger a mac-flush all-but-mine message WITHOUT the addition of the PE-ID TLV, as long as the source spoke SDP is not part of an end-point.
Any all-but-mine mac-flush event will trigger a mac-flush all-but-mine message WITH the addition of the PE-ID TLV, if the source spoke SDP is part of an end-point and the spoke-sdp goes from down/standby state to active state. In this case, the PE-ID TLV will contain the IP address of the PE to which the previous active spoke-sdp was connected to.
Any other case will follow the existing mac-flush procedures.
When the pe-id-mac-flush-interop flag is enabled for a given LDP peer, the mac-flush ingress processing is modified according to the following rules:
Any received all-from-me mac-flush will follow the existing mac-flush all-from-me rules regardless of the existence of the PE-ID.
Any received all-but-mine mac-flush will take into account the received PE-ID, that is all the mac addresses associated to the PE-ID will be flushed. If the PE-ID is not included, the mac addresses associated to the sending PE will be flushed.
Any other case will follow the existing mac-flush procedures.
When a mac-flush message has to be propagated (for an ingress sdp-binding to an egress sdp-binding) and the pe-id-mac-flush-interop flag is enabled for the ingress and egress TLDP peers, the following behavior is observed:
If the ingress and egress bindings are spoke SDP, the PE will propagate the mac-flush message with its own PE-ID.
If the ingress binding is an spoke SDP and the egress binding a mesh SDP, the PE will propagate the mac-flush message without modifying the PE-ID included in the PE-ID TLV.
If the ingress binding is a mesh SDP and the egress binding an spoke SDP, the PE will propagate the mac-flush message with its own PE-ID.
When ingress and egress bindings are mesh-sdp, the mac-flush message is never propagated. This is the behavior regardless of the pe-id-mac-flush-interop flag configuration.
The PE-ID TLV is never added when generating a mac-flush message on a B-VPLS if the send-bvpls-flush command is enabled in the I-VPLS. In the same way, no PE-ID is added when propagating mac-flush from a B-VPLS to a I-VPLS when the propagate-mac-flush-from-bvpls command is enabled. Mac-flush messages for peers within the same I-VPLS or within the same B-VPLS domain follow the procedures described above.
Default
no pe-id-mac-flush-interop
Platforms
All
peak-rate
peak-rate
Syntax
peak-rate rate
no peak-rate
Context
[Tree] (config>router>policy-acct-template>policer peak-rate)
Full Context
configure router policy-acct-template policer peak-rate
Description
This command sets the peak rate (the fill or drain rate of the bucket).
Each policer has a peak information rate and a maximum burst size. The default peak-rate (when no value is configured or the configured value is max) is the line rate of the ingress port.
The no form of this command reverts to the default value.
Default
peak-rate max
Parameters
- rate
Specifies the peak rate in Kb/s
Platforms
7450 ESS, 7750 SR, 7750 SR-s, 7950 XRS
peer
peer
Syntax
peer ip-address tag sync-tag
no peer
Context
[Tree] (config>router>dhcp6>server>pool>failover peer)
[Tree] (config>service>vprn>dhcp>server peer)
[Tree] (config>service>vprn>dhcp6>server peer)
[Tree] (config>router>dhcp>server>pool>failover peer)
[Tree] (config>service>vprn>dhcp6>server>pool peer)
[Tree] (config>router>dhcp>server>failover peer)
[Tree] (config>service>vprn>dhcp>server>pool peer)
[Tree] (config>router>dhcp6>server>failover peer)
Full Context
configure router dhcp6 server pool failover peer
configure service vprn dhcp server peer
configure service vprn dhcp6 server peer
configure router dhcp server pool failover peer
configure service vprn dhcp6 server pool peer
configure router dhcp local-dhcp-server failover peer
configure service vprn dhcp server pool peer
configure router dhcp6 local-dhcp-server failover peer
Description
This command creates a sync tag. DHCP leases can be synchronized per DHCP server or DHCP pool. The pair of synchronizing servers or pools is identified by a tag. The synchronization information is carried over the Multi-Chassis Synchronization (MCS) link between the two peers. MCS link is a logical link (IP, or MPLS).
MCS runs over TCP, port 45067 and it is using either data traffic or keepalives to detect failure on the communication link between the two nodes. In the absence of any MCS data traffic for more than 0.5sec, MCS will send its own keepalive to the peer. If a reply is not received within three sec, MCS will declare its operation state as DOWN and the DB Sync state as out-of-sync. MCS will consequently notify its clients (DHCP Server being one of them) of this. It can take up to three seconds before the DHCP client realizes that the inter-chassis communication link has failed.
The inter-chassis communication link failure does not necessarily assume the same failed fate for the access links. The two redundant nodes can become isolated from each other in the network. This occurs when only the intercommunication (MCS) link fails. It is important that this MCS link be highly redundant.
The no form of this command reverts to the default.
Parameters
- ip-address
Specifies the IPv4 or IPv6 address of the peer.
- tag sync-tag
Specifies a tag, up to 32 characters, that identifies the synchronizing DHCP servers or pools.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
peer
Syntax
[no] peer router router-instance address ip-address [udp-port port]
Context
[Tree] (debug>gtp peer)
Full Context
debug gtp peer
Description
This command restricts debugging to only data related to the specified GTP peer. This command can be repeated multiple times, where only data for any of the specified peers is debugged.
The no form of this command removes the restriction for the specified peer. When the last peer filter is removed, all data is debugged again, but may be restricted by other filters.
Parameters
- router-instance
Specifies the ID of the VRF where the peer is connected.
- ip-address
Specifies the IP address of the peer.
- port
Specifies the GTP-C port used by the peer.