b Commands

Context

[Tree] (back)

Full Context

back

Description

This command moves the context back one level of the command hierarchy. For example, if the current level is the config router ospf context, the back command moves the cursor to the config router context level.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>ies>if>ipv6>vrrp backup)

Full Context

configure service ies interface ipv6 vrrp backup

Description

This command configures virtual router IP addresses for the interface.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>ies>if>vrrp backup)

Full Context

configure service ies interface vrrp backup

Description

This command configures virtual router IP addresses for the interface.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>if>vrrp backup)

Full Context

configure service vprn interface vrrp backup

Description

This command configures virtual router IP addresses for the interface.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>if>ipv6>vrrp backup)

Full Context

configure service vprn interface ipv6 vrrp backup

Description

This command configures virtual router IP addresses for the interface.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>isa>tunnel-grp backup)

Full Context

configure isa tunnel-group backup

Description

This command assigns a tunnel ISA configured in the specified slot to this IPsec group. The backup module provides the IPsec group with warm redundancy when the primary module in the group is configured. An IPsec group must always have a primary configured.

Primary and backup modules have equal operational status and when both modules are coming up, the one that becomes operational first becomes the active module. An IPsec module can serve as a backup for multiple IPsec groups but the backup can become active for only one ISA IPsec group at a time.

All configuration information is pushed down to the backup MDA from the CPM once the CPM gets notice that the primary module has gone down. This allows multiple IPsec groups to use the same backup module. Any statistics not yet spooled are lost. Auto-switching from the backup to primary, after the primary becomes available again, is supported.

The user is notified through SNMP events when:

• When the ISA IPsec service goes down (all modules in the group are down) or comes back up (a module in the group becomes active).

• When ISA IPsec redundancy fails (one of the modules in the group is down) or recovers (the failed module comes back up).

• When an ISA IPsec activity switch took place.

The no form of this command removes the specified module from the IPsec group.

Default

no backup

Parameters

mda-id

Specifies the card/slot identifying a provisioned module to be used as a backup module.

Values

mda-id: slot/mda slot 1 to up to 10 depending on chassis model mda 1 to 2

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>if>vrrp backup)

Full Context

configure router interface vrrp backup

Description

This command associates router IP addresses with the parental IP interface IP addresses.

The backup command has two distinct functions when used in an owner or a non-owner context of the virtual router instance.

Non-owner virtual router instances actually create a routable IP interface address that is operationally dependent on the virtual router instance mode (master or backup). The backup command in owner virtual router instances does not create a routable IP interface address; it simply defines the existing parental IP interface IP addresses that are advertised by the virtual router instance.

For owner virtual router instances, the backup command defines the IP addresses that are advertised within VRRP advertisement messages. This communicates the IP addresses that the master is representing to backup virtual routers receiving the messages. Advertising a correct list is important. The specified ip-address must be equal to one of the existing parental IP interface IP addresses (primary or secondary) or the backup command fails.

For non-owner virtual router instances, the backup command actually creates an IP interface IP address used for routing IP packets and communicating with the system when the access commands are defined (ntp-reply, ping-reply, telnet-reply, and ssh-reply). The specified ip-address must be an IP address that is within one of the parental IP interface local subnets created with the address or secondary commands. If a local subnet does not exist that includes the specified ip-address or if ip-address is the same IP address as the parental IP interface IP address, the backup command fails.

The new interface IP address created with the backup command assumes the mask and parameters of the corresponding parent IP interface IP address. The ip-address is only active when the virtual router instance is operating in the master state. When not operating as master, the virtual router instance acts as if it is operationally down. It does not respond to ARP requests to ip-address, nor does it route packets received with its vrid derived source MAC address. A non-master virtual router instance always silently discards packets destined to ip-address. A single virtual router instance may only have a single virtual router IP address from a given parental local subnet. Multiple virtual router instances can define a virtual router IP address from the same local subnet as long as each is a different IP address.

In IPv4, up to sixteen backup ip-address commands can be executed within the same virtual router instance. Executing backup multiple times with the same ip-address results in no operation performed and no error generated. At least one successful backup ip-address command must be executed before the virtual router instance can enter the operational state.

When operating as (non-owner) master, the default functionality associated with ip-address is ARP response to ARP requests to ip-address, routing of packets destined to the virtual router instance source MAC address and silently discarding packets destined to ip-address. Enabling the non-owner-access parameters selectively allows ping, Telnet and SSH connectivity to ip-address when the virtual router instance is operating as master.

The no form of the command removes the specified virtual router IP address from the virtual router instance. For non-owner virtual router instances, this causes all routing and local access associated with the ip-address to cease. For owner virtual router instances, the no backup command only removes ip-address from the list of advertised IP addresses. If the last ip-address is removed from the virtual router instance, the virtual router instance will enter the operationally down state

Default

no backup — No virtual router IP address is assigned.

Parameters

ip-address

The virtual router IP address expressed in dotted decimal notation. The IP virtual router IP address must be in the same subnet of the parental IP interface IP address or equal to one of the primary or secondary IP addresses for owner virtual router instances.

Values

1.0.0.1 to 223.255.255.254

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>if>ipv6>vrrp backup)

Full Context

configure router interface ipv6 vrrp backup

Description

This command associates router IPv6 addresses with the parental IP interface IP addresses.

The backup command has two distinct functions when used in an owner or a non-owner context of the virtual router instance.

Non-owner virtual router instances actually create a routable IP interface address that is operationally dependent on the virtual router instance mode (master or backup). The backup command in owner virtual router instances does not create a routable IP interface address; it simply defines the existing parental IP interface IP addresses that are advertised by the virtual router instance.

For owner virtual router instances, the backup command defines the IP addresses that are advertised within VRRP advertisement messages. This communicates the IP addresses that the master is representing to backup virtual routers receiving the messages. Advertising a correct list is important. The specified ipv6-addr must be equal to one of the existing parental IP interface IP addresses (link-local or global) or the backup command will fail.

For non-owner virtual router instances, the backup command actually creates an IP interface IP address used for routing IP packets and communicating with the system when the access commands are defined (ntp-reply, ping-reply, telnet-reply, and ssh-reply). The specified ipv6-addr must be an IP address that is within one of the parental IP interface local subnets created with the link-local-address or address commands. If a local subnet does not exist that includes the specified ipv6-addr or if ipv6-addr is the same IP address as the parental IP interface IP address, the backup command will fail.

The new interface IP address created with the backup command assumes the mask and parameters of the corresponding parent IP interface IP address. The ipv6-addr is only active when the virtual router instance is operating in the master state. For IPv6 VRRP, the parental interface's IP address that is in the same subnet as the backup address must be manually-configured, non EUI-64 and configured to be in the preferred state.

When not operating as master, the virtual router instance acts as if it is operationally down. It will not respond to Neighbor Solicitation (NS) requests to ipv6-addr, nor will it route packets received with its vrid derived source MAC address. A non-master virtual router instance always silently discards packets destined to ipv6-addr.

IPv6 allows the configuration of a link-local IPv6 address and multiple global IPv6 addresses on an interface. For each of these configured subnets, a virtual router IP address can be configured. Each IPv6 enabled device on a particular IPv6 subnet dynamically learns the connected IPv6 routers and correlated subnets in addition to the IPv6 default gateway using IPv6 neighbor discovery protocol (RFC 4861). This protocol behavior is revised from IPv4 where the default gateway is manually configured or derived from supporting protocols (for example, DHCP). During the IPv6 neighbor discovery process, VRRP enabled routers will use backup IPv6 addresses and correlated derived virtual MAC addresses. Multiple virtual router instances can define a virtual router IP address from the same local subnet as long as each is a different IP address.

Executing backup multiple times with the same ipv6-addr results in no operation performed and no error generated. At least one successful backup ipv6-addr command must be executed before the virtual router instance can enter the operational state.

When operating as (non-owner) master, the default functionality associated with ipv6-addr results in the IPv6 Neighbor Advertisement response to IPv6 Neighbor Solicitation requests to ip-addr, routing of packets destined to the virtual router instance source MAC address, and silently discarding packets destined to ipv6-addr. An IPv6 virtual router instance can enter the operational state only if one of the configured backup addresses is a link-local address and the router advertisement of the interface is configured to use the virtual MAC address. Enabling the non-owner-access parameters selectively allows ping, Telnet, and traceroute connectivity to ipv6-addr when the virtual router instance is operating as master.

The no form of the command removes the specified virtual router IP address from the virtual router instance. For non-owner virtual router instances, this causes all routing and local access associated with the ipv6-addr to cease. For owner virtual router instances, the no backup command only removes ipv6-addr from the list of advertised IP addresses. If the last ipv6-addr or the link-local address is removed from the virtual router instance, the virtual router instance will enter the operationally down state

Default

no backup — No virtual router IP address is assigned.

Parameters

ipv6-address

The virtual router IP address is represented as eight groups of four hexadecimal digits, each group representing 16 bits (two octets). The groups are separated by colons (:). The IP virtual router IP address must be in the same subnet of the parental IP interface IP address or equal to one of the parent interface addresses for owner virtual router instances.

Values

ipv6-address	x:x:x:x:x:x:x:x (eight 16-bit pieces)
	x:x:x:x:x:x::d.d.d.d
	x: [0..FFFF]H
	d: [0..255]D

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>mpls>lsp>primary backup-class-type)

Full Context

configure router mpls lsp primary backup-class-type

Description

This command enables the use of the Diff-Serv backup Class-Type (CT), instead of the Diff-Serv main CT, to signal the LSP primary path when it fails and goes into retry. The Diff-Serv main CT is configured at the LSP level or at the primary path level using the following commands:

config>router>mpls>lsp>class-type ct-number

config>router>mpls>lsp>primary>class-type ct-number

When an LSP primary path retries due a failure, for example, it fails after being in the UP state, or undergoes any type of Make-Before-Break (MBB), MPLS will retry a new path for the LSP using the main CT. If the first attempt failed, the head-end node performs subsequent retries using the backup CT. This procedure must be followed regardless if the currently used CT by this path is the main or backup CT. This applies to both CSPF and non-CSPF LSPs.

The triggers for using the backup CT after the first retry attempt are:

1. A local interface failure or a control plane failure (hello timeout and so on).

2. Receipt of a PathErr message with a notification of a FRR protection becoming active downstream and/or Receipt of a Resv message with a 'Local-Protection-In-Use’ flag set. This invokes the FRR Global Revertive MBB.

3. Receipt of a PathErr message with error code=25 ("Notify”) and sub-code=7 ("Local link maintenance required”) or a sub-code=8 ("Local node maintenance required”). This invokes the TE Graceful Shutdown MBB.

4. Receipt of a Resv refresh message with the 'Preemption pending’ flag set or a PathErr message with error code=34 ("Reroute”) and a value=1 ("Reroute request soft preemption”). This invokes the soft preemption MBB.

5. Receipt of a ResvTear message.

6. A configuration change MBB.

7. The user executing the clear>router>mpls>lsp command.

When an unmapped LSP primary path goes into retry, it uses the main CT until the number of retries reaches the value of the new main-ct-retry-limit parameter. If the path did not come up, it must start using the backup CT at that point in time. By default, this parameter is set to infinite value. The new main-ct-retry-limit parameter has no effect on an LSP primary path which retries due to a failure event.

An unmapped LSP primary path is a path which has never received a Resv in response to the first Path message sent. This can occur when performing a 'shut/no-shut’ on the LSP or LSP primary path or when the node reboots. An unmapped LSP primary path goes into retry if the retry timer expired or the head-end node received a PathErr message before the retry timer expired.

When the re-signal timer expires, CSPF will try to find a path with the main CT. The head-end node must re-signal the LSP even if the new path found by CSPF is identical to the existing one since the idea is to restore the main CT for the primary path. A path with main CT is not found, the LSP remains on its current primary path using the backup CT.

When the user performs a manual re-signal of the primary path, CSPF will try to find a path with the main CT. The head-end node must re-signal the LSP as in current implementation.

The no form of this command disables the use of the Diff-Serv backup CT.

Default

no backup-class-type

Parameters

ct-number

Specifies the Diff-Serv Class Type number. One or more system forwarding classes can be mapped to a CT.

Values

0 to 7, integer

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>mpls>fwd-policies>fwd-policy>nh-grp backup-next-hop)

Full Context

configure router mpls forwarding-policies forwarding-policy next-hop-group backup-next-hop

Description

Commands in this context configure the backup next hop of an NHG entry in a forwarding policy.

The no form of this command removes the backup next hop context from an NHG entry in a forwarding policy.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>ospf>segm-rtng backup-node-sid)

Full Context

configure router ospf segment-routing backup-node-sid

Description

This command enables LFA Protection using segment routing backup node SID.

The objective of this feature is to reduce the label stack pushed in a LFA tunnel next hop of inter-area and inter-domain prefixes. This is applicable in MPLS deployments across multiple IGP areas or domains such in seamless MPLS design.

The user enables the feature by configuring a backup node SID at an ABR/ASBR that is acting as a backup to the primary exit ABR/ASBR of inter-area or inter-as routes learned as BGP labeled routes. The user can enter either a label or an index for the backup node SID.

When a node in a IGP domain resolves a BGP label route for an inter-area or inter-domain prefix via the primary ABR exit router, it will use the backup node SID of this router, which is advertised by the backup ABR/ABR, as the LFA backup instead of the SID to the remote LFA PQ node to save on the pushed label stack.

This feature only allows the configuration of a single backup node SID per IGP instance and per ABR/ASBR. In other words, only a pair of ABR/ASBR nodes can back up each other in an IGP domain. Each time the user invokes the above command within the same IGP instance, it will override any previous configuration of the backup node SID. The same ABR/ASBR can, however, participate in multiple IGP instances and provide backup support within each instance.

Default

no backup-node-sid

Parameters

ip-prefix/prefix-length

Specifies the IP prefix in dotted decimal notation for the range used by the ABR to advertise that summarizes the area into another area.

Values

ip-prefix/mask:

• ip-prefix a.b.c.d (host bits must be 0)

ipv6-prefix:

• x:x:x:x:x:x:x:x (eight 16-bit pieces)

• x:x:x:x:x:x:d.d.d.d

• x: [0 to FFFF]H

• d: [0 to 255]D

prefix-length: 0 to 128

index

Specifies the index for this backup node SID.

Values

0 to 4294967295

label

Specifies the SID value for this backup node SID.

Values

1 to 4294967295

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>ies>if>sap>ip-tunnel backup-remote-ip)

[Tree] (config>service>vprn>if>sap>ip-tunnel backup-remote-ip)

Full Context

configure service ies interface sap ip-tunnel backup-remote-ip

configure service vprn interface sap ip-tunnel backup-remote-ip

Description

This command configures the alternate destination IPv4 or IPv6 address to use for an IP tunnel. This destination address is used only if the primary destination configured with the remote-ip command is unreachable in the delivery service. The source address, remote-ip address and backup-remote-ip address of a tunnel must all belong to the same address family (IPv4 or IPv6). When the backup-remote-ip address contains an IPv6 address it must be a global unicast address.

The no form of this command deletes the backup-destination address from the tunnel configuration.

Default

no backup-remote-ip

Parameters

ip-address

Specifies the destination IPv4 address or IPv6 address of the tunnel.

Values

ipv4-address:

• a.b.c.d

ipv6-address:

• x:x:x:x:x:x:x:x (eight 16-bit pieces)

• x:x:x:x:x:x:d.d.d.d

• x: [0 to FFFF]H

• d: [0 to 255]D

Platforms

7705 SAR Gen 2

Context

[Tree] (config>lag>access bandwidth)

[Tree] (config>port>ethernet>access bandwidth)

Full Context

configure lag access bandwidth

configure port ethernet access bandwidth

Description

This command configures the administrator bandwidth assigned and available to ports and LAGs for use by SAP bandwidth Connection Admission Control (CAC). The administrator bandwidth on a port or LAG can be overbooked or underbooked using the booking-factor command.

Port or LAG: Increasing the port or LAG admin bandwidth will increase the available admin bandwidth on that port or LAG. Reducing the port or LAG admin bandwidth will reduce the available admin bandwidth on that port or LAG, however, if the reduction of available admin bandwidth would cause it to be insufficient to cover the sum of the current SAP admin bandwidth on the port or LAG then the command will fail.

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

Default

no bandwidth

Parameters

bandwidth

Specifies the administrator bandwidth, in kb/s, that is assigned to the port or LAG.

Values

1 to 6400000000

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>epipe>sap bandwidth)

Full Context

configure service epipe sap bandwidth

Description

This command configures the administrator bandwidth assigned and available to SAPs for use by SAP bandwidth Connection Admission Control (CAC).

Attempts to increase the SAP administrator bandwidth fail if there is insufficient available administrator bandwidth on its port or LAG, otherwise the available port or LAG administrator bandwidth is reduced by the incremental SAP administrator bandwidth. Reducing the SAP administrator bandwidth increases the available administrator bandwidth on its port or LAG.

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

Default

no bandwidth

Parameters

bandwidth

Specifies the administrator bandwidth, in kb/s, that is assigned to the SAP.

Values

1 to 6400000000

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>epipe>spoke-sdp bandwidth)

Full Context

configure service epipe spoke-sdp bandwidth

Description

This command specifies the bandwidth to be used for VLL bandwidth accounting by the VLL CAC feature.

The service manager keeps track of the available bandwidth for each SDP. The maximum value is the sum of the bandwidths of all constituent LSPs in the SDP. The SDP available bandwidth is adjusted by the user configured booking factor.

If an LSP consists of a primary and many secondary standby LSPs, then the bandwidth used in the maximum SDP available bandwidth is that of the active path. Any change to and LSP active path bandwidth will update the maximum SDP available bandwidth. Note however that a change to any constituent LSP bandwidth due to re-signaling of the primary LSP path or the activation of a secondary path which causes overbooking of the maximum SDP available bandwidth causes a warning and a trap to be issued but no further action is taken. The activation of a bypass or detour LSP in the path of the primary LSP does not change the maximum SDP available bandwidth.

When the user binds a VLL service to this SDP, an amount of bandwidth equal to bandwidth is subtracted from the SDP available bandwidth adjusted by the booking factor. When the user deletes this VLL service binding from this SDP, an amount of bandwidth equal to bandwidth is added back into the SDP available bandwidth.

If the total SDP available bandwidth when adding this VLL service is about to overbook, a warning is issued and the binding is rejected. This means that the spoke SDP bandwidth does not update the maximum SDP available bandwidth. In this case, the spoke SDP is put in operational down state and a status message of "pseudowire not forwarding” is sent to the remote SR OS PE node. A trap is also generated. The service manager will not put the spoke SDP into an operationally up state until the user executes a shutdown command and then a no-shutdown command of the spoke SDP and the bandwidth check succeeds. Therefore, the service manager will not automatically audit spoke SDPs subsequently to their creation to check if bandwidth is available.

If the VLL service contains an endpoint with multiple redundant spoke SDPs, each spoke SDP will have its bandwidth checked against the available bandwidth of the corresponding SDP.

If the VLL service performs a pseudowire switching (VC switching) function, each spoke SDP is separately checked for bandwidth against the corresponding SDP.

This feature does not alter the way service packets are sprayed over multiple RSVP LSPs, which are part of the same SDP. That is, by default load balancing of service packets occurs over the SDP LSPs based on service-id, or based on a hash of the packet header if ingress SAP shared queuing is enabled. In both cases, the VLL bandwidth is not checked against the available bandwidth of the selected LSPs but on the total SDP available bandwidth. Therefore, if there is a single LSP per SDP, these two matches.

If class-forwarding is enabled on the SDP, VLL service packets are forwarded to the SDP LSP which the packet forwarding class maps to, or if this is down to the default LSP. However, the VLL bandwidth is not checked against the selected LSP available bandwidth but on the total SDP available bandwidth. If there is a single LSP per SDP, these two matches.

If a non-zero bandwidth is specified for a VLL service and attempts to bind the service to an LDP or a GRE SDP, a warning is issued that CAC failed but the VLL is established. A trap is also generated.

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

Parameters

bw-value

The bandwidth to be used for VLL bandwidth accounting by the VLL CAC feature, in kilobits per second.

Values

0 to 100000000

Default

0

Platforms

7705 SAR Gen 2

Context

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

Full Context

configure service vpls sap bandwidth

Description

This command specifies the admin bandwidth assigned to SAPs, ports and LAGs which is used by SAP bandwidth CAC.

SAP: Attempts to increase the SAP admin bandwidth will fail if there is insufficient available admin bandwidth on its port or LAG, otherwise the port or LAG available admin bandwidth will be reduced by the incremental SAP admin bandwidth. Reducing the SAP admin bandwidth will increase the available admin bandwidth on its port or LAG. This is not supported for PW-SAPs, Ethernet tunnels or subscriber group interface SAPs.

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

Default

no bandwidth

Parameters

bandwidth

Specifies the admin bandwidth assigned to the SAP, port or LAG, in kb/s.

Values

1 to 6400000000

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>ies>if>sap bandwidth)

Full Context

configure service ies interface sap bandwidth

Description

This command specifies the admin bandwidth assigned to SAPs, ports and LAGs which is used by SAP bandwidth CAC.

SAP: Attempts to increase the SAP admin bandwidth will fail if there is insufficient available admin bandwidth on its port or LAG, otherwise the port or LAG available admin bandwidth will be reduced by the incremental SAP admin bandwidth. Reducing the SAP admin bandwidth will increase the available admin bandwidth on its port or LAG. This is not supported for PW-SAPs, Ethernet tunnels or subscriber group interface SAPs.

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

Default

no bandwidth

Parameters

bandwidth

Specifies the admin bandwidth assigned to the SAP, port or LAG, in kb/s.

Values

1 to 6400000000

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>if>sap bandwidth)

Full Context

configure service vprn interface sap bandwidth

Description

This command specifies the admin bandwidth assigned to SAPs, ports and LAGs which is used by SAP bandwidth CAC.

SAP: Attempts to increase the SAP admin bandwidth will fail if there is insufficient available admin bandwidth on its port or LAG, otherwise the port or LAG available admin bandwidth will be reduced by the incremental SAP admin bandwidth. Reducing the SAP admin bandwidth will increase the available admin bandwidth on its port or LAG. This is not supported for PW-SAPs, Ethernet tunnels or subscriber group interface SAPs.

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

Default

no bandwidth

Parameters

bandwidth

Specifies the admin bandwidth assigned to the SAP, port or LAG, in kb/s.

Values

1 to 6400000000

Platforms

7705 SAR Gen 2

Context

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

Full Context

configure router mpls lsp-template bandwidth

Description

This command specifies the amount of bandwidth to be reserved for the P2MP instance.

Parameters

bandwidth-in-mbps

Specifies the bandwidth, in Mb/s.

Values

0 to 6400000

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>mpls>lsp>secondary bandwidth)

[Tree] (config>router>mpls>lsp>primary bandwidth)

Full Context

configure router mpls lsp secondary bandwidth

configure router mpls lsp primary bandwidth

Description

This command specifies the amount of bandwidth to be reserved for the LSP path.

The no form of this command resets bandwidth parameters (no bandwidth is reserved).

Default

no bandwidth (bandwidth setting in the global LSP configuration)

Parameters

bandwidth-in-mbps

Specifies the amount of bandwidth reserved for the LSP path in Mb/s.

Values

0 to 6400000

Platforms

7705 SAR Gen 2

Context

[Tree] (config>system>security>profile>netconf base-op-authorization)

Full Context

configure system security profile netconf base-op-authorization

Description

Commands in this context configure the permission to use NETCONF operations at the base operation level for the specified profile.The NETCONF operations are authorized by default in the built-in system-generated administrative profile.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>bfd begin)

Full Context

configure router bfd begin

Description

This command switches to edit mode for a BFD template. Changes are not activated until the commit command is issued for the BFD template changes.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>route-next-hop-policy begin)

Full Context

configure router route-next-hop-policy begin

Description

This command switches to edit mode for route next-hop templates. Changes are not activated until the commit command is issued for the route next-hop templates changes.

Default

begin

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>policy-options begin)

Full Context

configure router policy-options begin

Description

This command is required in order to enter the mode to create or edit route policies.

Parameters

exclusive

Specifies an exclusive lock on the policy configuration. Other CLI and SNMP users will be unable to edit the policy configuration until the lock is removed (via commit, abort, a timeout occurring, or a forced override).

Platforms

7705 SAR Gen 2

Context

[Tree] (config>system>security>keychain>direction>uni>send>entry begin-time)

[Tree] (config>system>security>keychain>direction>bi>entry begin-time)

[Tree] (config>system>security>keychain>direction>uni>receive>entry begin-time)

Full Context

configure system security keychain direction uni send entry begin-time

configure system security keychain direction bi entry begin-time

configure system security keychain direction uni receive entry begin-time

Description

This command specifies the calendar date and time after which the key specified by the keychain authentication key is used to sign and/or authenticate the protocol stream.

If no date and time is set, the begin-time is represented by a date and time string with all NULLs and the key is not valid by default.

Default

begin-time forever

Parameters

date hours-minutes

Specifies the date and time for the key to become active.

Values

date: YYYY/MM/DD hours-minutes: hh:mm[:ss]

now

Specifies the key should become active immediately.

forever

Specifies that the key is always inactive.

UTC

Indicates that time is given with reference to Coordinated Universal Time in the input.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>bgp best-path-selection)

Full Context

configure service vprn bgp best-path-selection

Description

This command enables path selection configuration.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>bgp best-path-selection)

Full Context

configure router bgp best-path-selection

Description

Commands in this context configure path selection parameters.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>if bfd)

[Tree] (config>service>vprn>nw-if bfd)

[Tree] (config>service>vprn>if>ipv6 bfd)

[Tree] (config>service>ies>if bfd)

[Tree] (config>service>ies>if>ipv6 bfd)

Full Context

configure service vprn interface bfd

configure service vprn network-interface bfd

configure service vprn interface ipv6 bfd

configure service ies interface bfd

configure service ies interface ipv6 bfd

Description

This command specifies the BFD parameters for the associated IP interface. If no parameters are defined the default value are used.

The multiplier specifies the number of consecutive BFD messages that must be missed from the peer before the BFD session state is changed to down and the upper level protocols (OSPF, IS-IS, BGP or PIM) is notified of the fault.

The no form of this command removes BFD from the interface.

To remove the type cpm-np option, re-issue the bfd command without specifying the type parameter.

Parameters

transmit-interval

Sets the transmit interval for the BFD session.

Values

100 to 100000

10 to 100000

Default

100

receive receive-interval

Sets the receive interval for the BFD session.

Values

100 to 100000

10 to 100000

Default

100

multiplier multiplier

Sets the multiplier for the BFD session.

Values

3 to 20

Default

3

echo-receive echo-interval

Sets the minimum echo receive interval, in milliseconds, for the BFD session.

Values

100 to 100000

10 to 100000

Default

100

type cpm-np

Specifies that BFD sessions associated with this interface is created on the CPM network processor to allow for fast timers down to 10 ms granularity.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>if>ipv6 bfd)

[Tree] (config>router>if bfd)

Full Context

configure router interface ipv6 bfd

configure router interface bfd

Description

This command specifies the bidirectional forwarding detection (BFD) parameters for the associated IP interface. If no parameters are defined the default values are used.

The multiplier specifies the number of consecutive BFD messages that must be missed from the peer before the BFD session state is changed to down and the upper level protocols (OSPF, IS-IS, BGP or PIM) is notified of the fault.

The no form of this command removes BFD from the router interface regardless of the IGP/RSVP.

Important notes: The transmit-interval and receive receive-interval values can only be modified to a value less than 100 ms when:

1. The type cpm-np option is explicitly configured.

2. The service is shut down (shutdown)

3. The interval is specified 10 to 100000.

4. The service is re-enabled (no shutdown)

To remove the type cpm-np option, re-issue the bfd command without specifying the type parameter.

Default

no bfd

Parameters

transmit-interval

Sets the transmit interval, in milliseconds, for the BFD session.

Values

10 to 100000 (see Important Notes above)

Default

100

receive-interval

Sets the receive interval, in milliseconds, for the BFD session.

Values

10 to 100000 (see Important Notes above)

Default

100

multiplier

Sets the multiplier for the BFD session. A multiplier of less than 3 should not be used in production environments.

Values

1 to 20

Default

3

echo-interval

Sets the minimum echo receive interval, in milliseconds, for the session.

Values

100 to 100000

Default

0

cpm-np

Selects the CPM network processor type as the local termination point for the BFD session. See Important Notes, above.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>if>ipsec>ipsec-tunnel bfd-designate)

[Tree] (config>service>vprn>if>sap>ipsec-tunnel bfd-designate)

[Tree] (config>service>ies>if>ipsec>ipsec-tunnel bfd-designate)

[Tree] (config>router>if>ipsec>ipsec-tunnel bfd-designate)

Full Context

configure service vprn interface ipsec ipsec-tunnel bfd-designate

configure service vprn interface sap ipsec-tunnel bfd-designate

configure service ies interface ipsec ipsec-tunnel bfd-designate

configure router interface ipsec ipsec-tunnel bfd-designate

Description

This command specifies whether this IPsec tunnel is the BFD designated tunnel.

Default

no bfd-designate

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>bgp>group>neighbor bfd-enable)

[Tree] (config>redundancy>multi-chassis>peer>mc-ep bfd-enable)

[Tree] (config>router>bgp>group bfd-enable)

[Tree] (config>router>bgp bfd-enable)

Full Context

configure router bgp group neighbor bfd-enable

configure redundancy multi-chassis peer mc-endpoint bfd-enable

configure router bgp group bfd-enable

configure router bgp bfd-enable

Description

This command enables the use of bi-directional forwarding (BFD) to control the state of the associated protocol interface. By enabling BFD on a given protocol interface, the state of the protocol interface is tied to the state of the BFD session between the local node and the remote node. The parameters used for the BFD are set via the BFD command under the IP interface.

The no form of this command disables BFD.

Default

no bfd-enable

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>ies>if>ipv6>vrrp bfd-enable)

[Tree] (config>service>ies>if>vrrp bfd-enable)

Full Context

configure service ies interface ipv6 vrrp bfd-enable

configure service ies interface vrrp bfd-enable

Description

This commands assigns a bi-directional forwarding (BFD) session providing heart-beat mechanism for the given VRRP/SRRP instance. There can be only one BFD session assigned to any given VRRP/SRRP instance, but there can be multiple SRRP/VRRP sessions using the same BFD session.

BFD control the state of the associated interface. By enabling BFD on a given protocol interface, the state of the protocol interface is tied to the state of the BFD session between the local node and the remote node. The parameters used for the BFD are set via the BFD command under the IP interface. The specified interface may not be configured with BFD; however, when it is, the virtual router will then initiate the BFD session.

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

Parameters

service-id

Specifies the service ID of the interface running BFD.

Values

service-id: 1 to 2147483648

No service ID indicates a network interface.

interface interface-name

Specifies the name of the interface running BFD.

dst-ip ip-address

Specifies the destination address to be used for the BFD session.

name name

Specifies the name, up to 64 characters.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>static-route-entry>next-hop bfd-enable)

Full Context

configure service vprn static-route-entry next-hop bfd-enable

Description

This command associates the static route state to a BFD session between the local system and the configured nexthop.

The remote end of the BFD session must also be configured to originate or accept the BFD session controlling the static route state.

The no form of this command removes the association of the static route state to that of the BFD session.

Default

no bfd-enable

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>if>ipv6>vrrp bfd-enable)

[Tree] (config>service>vprn>if>vrrp bfd-enable)

Full Context

configure service vprn interface ipv6 vrrp bfd-enable

configure service vprn interface vrrp bfd-enable

Description

This commands assigns a bi-directional forwarding (BFD) session providing heart-beat mechanism for the given VRRP/SRRP instance. There can be only one BFD session assigned to any given VRRP/SRRP instance, but there can be multiple SRRP/VRRP sessions using the same BFD session. If the interface used is configured with centralized BFD, the BFD transmit and receive intervals need to be set to at least 300 ms.

BFD control the state of the associated interface. By enabling BFD on a given protocol interface, the state of the protocol interface is tied to the state of the BFD session between the local node and the remote node. The parameters used for the BFD are set via the BFD command under the IP interface. The specified interface may not be configured with BFD; when it is, the virtual router will then initiate the BFD session.

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

Parameters

svc-id

Specifies the service ID of the interface running BFD. If no svc-id is specified then it indicates that the interface is a network interface in the Base router instance.

This variant of the command is only supported in 'classic' configuration-mode (configure system management-interface configuration-mode classic). The bfd-enable interface interface-name dst-ip ip-address name name variant can be used in all configuration modes.

Values

{id | svc-name}

id:	1 to 2147483647
svc-name:	Specifies an existing service name up to 64 characters (svc-name is an alias for input only. The svc-name gets replaced with an id automatically by SR OS in the configuration)

interface interface-name

Specifies the name of the interface running BFD, up to 32 characters.

dst-ip ip-address

Specifies the destination address to be used for the BFD session.

name name

Specifies a service name, up to 64 characters.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>isis>if bfd-enable)

Full Context

configure service vprn isis interface bfd-enable

Description

This command enables the use of bi-directional forwarding (BFD) to control IPv4 or adjacencies. By enabling BFD on an IPv4 or IPv6 protocol interface, the state of the protocol interface is tied to the state of the BFD session between the local node and the remote node. The parameters used for the BFD are set by the BFD command under the IP interface. This command must be given separately to enable or disable BFD for IPv4 and IPv6.

The no form of this command removes BFD from the associated adjacency.

Default

no bfd-enable ipv4

no bfd-enable ipv6

Parameters

ipv4

Keyword to enable BFD to control IPv4 adjacencies.

ipv6

Keyword to enable BFD to control IPv6 adjacencies.

include-bfd-tlv

Enables support for the IS-IS BFD TLV options in accordance with RFC 6213, which specifies that a BFD session must be established before an IS-IS adjacency can transition to the established state. This option must be enabled on all IS-IS neighbors on a shared interface.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>ospf3>area>if bfd-enable)

[Tree] (config>service>vprn>ospf>area>if bfd-enable)

Full Context

configure service vprn ospf3 area interface bfd-enable

configure service vprn ospf area interface bfd-enable

Description

This command configures Bidirectional Forwarding Detection (BFD) to control the state of the associated protocol interface. By enabling BFD on a protocol interface, the state of the protocol interface is tied to the state of the BFD session between the local node and the remote node. The parameters used for the BFD session are set using the bfd command in the associated IP interface context.

The no form of this command removes BFD from the associated IGP protocol adjacency.

Default

no bfd-enable

Parameters

remain-down-on-failure

Keyword to force adjacency down on BFD failure.

strict

Keyword to specify that the system uses BFD strict-mode, which requires that an active BFD session exists between the OSPF neighbors before establishing a full adjacency. When this keyword is configured, the router uses Link-Local Signaling (LLS) with the B-flag set to instruct OSPF neighbors that BFD must be enabled on the link. BFD strict-mode requires that both sides have the B-flag set.

During OSPFv3 BFD strict-mode operations, the router advertises the Local Interface IPv4 Address TLV using LLS, but the SR OS router continues to use IPv6-based BFD sessions for both the IPv4 and IPv6 address families.

strict-mode-holddown number

Specifies a delay in bringing up the OSPF adjacency after the BFD session is established. Holddown helps mitigate potential routing churn when BFD sessions are unstable. The holddown timer is reset on an adjacency when a BFD session operationally toggles.

Values

1 to 600

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>pim>if bfd-enable)

Full Context

configure service vprn pim interface bfd-enable

Description

This command enables the use of bi-directional forwarding (BFD) to control the state of the associated protocol interface. By enabling BFD on a given protocol interface, the state of the protocol interface is tied to the state of the BFD session between the local node and the remote node. The parameters used for the BFD are set via the BFD command under the IP interface.

The no form of this command removes BFD from the associated IGP protocol adjacency.

Default

no bfd-enable

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>bgp>group>neighbor bfd-enable)

[Tree] (config>service>vprn>bgp>group bfd-enable)

[Tree] (config>service>vprn>bgp bfd-enable)

Full Context

configure service vprn bgp group neighbor bfd-enable

configure service vprn bgp group bfd-enable

configure service vprn bgp bfd-enable

Description

This command enables the use of bi-directional forwarding (BFD) to control the state of the associated protocol interface. The parameters used for the BFD are set with the BFD command under the IP interface.

The no form of this command disables bfd-enable on the VPRN service.

Default

no bfd-enable

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>ripng>group>neighbor bfd-enable)

[Tree] (config>service>vprn>ripng>group bfd-enable)

[Tree] (config>service>vprn>ripng bfd-enable)

[Tree] (config>service>vprn>rip bfd-enable)

[Tree] (config>service>vprn>rip>group>neighbor bfd-enable)

[Tree] (config>service>vprn>rip>group bfd-enable)

Full Context

configure service vprn ripng group neighbor bfd-enable

configure service vprn ripng group bfd-enable

configure service vprn ripng bfd-enable

configure service vprn rip bfd-enable

configure service vprn rip group neighbor bfd-enable

configure service vprn rip group bfd-enable

Description

This command enables bi-directional forwarding (BFD) to control the state of the associated protocol adjacency. By enabling BFD on a given protocol interface, the state of the RIP neighbor is tied to the state of the BFD session between the local node and the remote node. The parameters used for the BFD are set using the bfd command under the IP interface configuration context.

The no form of this command removes BFD from the associated protocol adjacency.

Default

no bfd-enable

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>ldp>if-params>if bfd-enable)

Full Context

configure router ldp interface-parameters interface bfd-enable

Description

This command enables tracking of the Hello adjacency to an LDP peer using BFD.

When this command is enabled on an LDP interface, LDP registers with BFD and starts tracking the LSR-id of all peers it formed Hello adjacencies with over that LDP interface. The LDP hello mechanism is used to determine the remote address to be used for the BFD session. The parameters used for the BFD session, that is, transmit-interval, receive-interval, and multiplier are those configured under the IP interface in existing implementation: config>router>if>bfd.

The operation of BFD over an LDP interface tracks the next-hop of the IPv4 and IPv6 prefixes in addition to tracking the LDP peer address of the Hello adjacency over that link. This is required since LDP can resolve both IPv4 and IPv6 prefix FECs over a single IPv4 or IPv6 LDP session and as such the next-hop of a prefix will not necessarily match the LDP peer source address of the Hello adjacency.

The failure of either or both of the BFD session tracking the FEC next-hop and the one tracking the Hello adjacency will cause the LFA backup NHLFE for the FEC to be activated or the FEC to be re-resolved if there is no FRR backup.

When multiple links exist to the same LDP peer, a Hello adjacency is established over each link and a separate BFD session is enabled on each LDP interface. If a BFD session times out on a specific link, LDP will immediately associate the LDP session with one of the remaining Hello adjacencies and trigger the LDP FRR procedures. As soon as the last Hello adjacency goes down due to BFD timing out, the LDP session goes down and the LDP FRR procedures will be triggered.

The no form of this command disables BFD on the LDP interface.

Default

no bfd-enable

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>ldp>targ-session>peer bfd-enable)

[Tree] (config>router>ldp>targ-session>peer-template bfd-enable)

Full Context

configure router ldp targeted-session peer bfd-enable

configure router ldp targeted-session peer-template bfd-enable

Description

This command enables the bidirectional forwarding detection (BFD) session for the selected TLDP session. By enabling BFD for a selected targeted session, the state of that session is tied to the state of the underneath BFD session between the two nodes.

The parameters used for the BFD are set via the BFD command under the IP interface.

The no form of this command removes the TLDP session operational state binding to the central BFD session one.

Default

no bfd-enable

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>rsvp>interface bfd-enable)

Full Context

configure router rsvp interface bfd-enable

Description

This command enables the use of bi-directional forwarding (BFD) to control the state of the associated RSVP interface. This causes RSVP to register the interface with the BFD session on that interface.

The user configures the BFD session parameters, such as, transmit-interval, receive-interval, and multiplier, under the IP interface in the config>router> if>bfd context.

The registration of an RSVP interface with BFD is performed at the time of neighbor gets its first session. This means when this node sends or receives a new Path message over the interface. If however the session did not come up, due to not receiving a Resv for a new path message sent after the maximum number of re-tries, the LSP is shutdown and the node de-registers with BFD. In general, the registration of RSVP with BFD is removed as soon as the last RSVP session is cleared.

The registration of an RSVP interface with BFD is performed independent of whether RSVP hello is enabled on the interface or not. However, hello timeout will clear all sessions towards the neighbor and RSVP de-registers with BFD at clearing of the last session.

An RSVP session is associated with a neighbor based on the interface address the path message is sent to. If multiple interfaces exist to the same node, each interface is treated as a separate RSVP neighbor. The user will have to enable BFD on each interface and RSVP will register with the BFD session running with each of those neighbors independently

Similarly the disabling of BFD on the interface results in removing registration of the interface with BFD.

When a BFD session transitions to DOWN state, the following actions are triggered. For RSVP signaled LSPs, this triggers activation of FRR bypass/detour backup (PLR role), global revertive (head-end role), and switchover to secondary if any (head-end role) for affected LSPs with FRR enabled. It triggers switchover to secondary if any and scheduling of re-tries for signaling the primary path of the non-FRR affected LSPs (head-end role).

The no form of this command removes BFD from the associated RSVP protocol adjacency.

Default

no bfd-enable

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>ies>if>ipsec>ipsec-tunnel bfd-enable)

[Tree] (config>service>vprn>if>sap>ipsec-tunnel bfd-enable)

[Tree] (config>router>if>ipsec>ipsec-tunnel bfd-enable)

[Tree] (config>service>vprn>if>ipsec>ipsec-tunnel bfd-enable)

Full Context

configure service ies interface ipsec ipsec-tunnel bfd-enable

configure service vprn interface sap ipsec-tunnel bfd-enable

configure router interface ipsec ipsec-tunnel bfd-enable

configure service vprn interface ipsec ipsec-tunnel bfd-enable

Description

This command assigns a BFD session to provide a heart-beat mechanism for a given IPsec tunnel. There can be only one BFD session assigned to any given IPsec tunnel, but there can be multiple IPsec tunnels using same BFD session. BFD controls the state of the associated tunnel. If the BFD session goes down, the system will also bring down the associated non-designated IPsec tunnel.

Parameters

service-name

Specifies the service name, up to 64 characters, on which the BFD session resides.

interface-name

Specifies the name, up to 32 characters, of the interface used by the BFD session.

ip-address

Specifies the destination address to be used for the BFD session.

Platforms

7705 SAR Gen 2

Context

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

Full Context

configure redundancy multi-chassis peer mc-ipsec bfd-enable

Description

This command enables tracking a central BFD session, if the BFD session goes down, then system consider the peer is down and change the mc-ipsec status of configured tunnel-group accordingly.

The BFD session uses specified the loopback interface (in the specified service) address as the source address and uses specified dst-ip as the destination address. Other BFD parameters are configured with the bfd command on the specified interface.

Default

no bfd-enable

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>pim>interface bfd-enable)

Full Context

configure router pim interface bfd-enable

Description

This command enables the use of IPv4 or IPv6 bidirectional forwarding detection (BFD) to control the state of the associated protocol interface. By enabling BFD on a given protocol interface, the state of the protocol interface is tied to the state of the BFD session between the local node and the remote node. The parameters used for the BFD are set via the BFD command under the IP interface.

The no form of this command removes BFD from the associated IGP protocol adjacency.

Default

no bfd-enable

Parameters

ipv4

Enables the use of IPv4 BFD.

ipv6

Enables the use of IPv6 BFD.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>static-route-entry>next-hop bfd-enable)

Full Context

configure router static-route-entry next-hop bfd-enable

Description

This command associates the static route state to a BFD session between the local system and the configured nexthop.

The remote end of the BFD session must also be configured to originate or accept the BFD session controlling the static route state.

The no form of this command removes the association of the static route state to that of the BFD session.

Default

no bfd-enable

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>if>vrrp bfd-enable)

[Tree] (config>router>if>ipv6>vrrp bfd-enable)

Full Context

configure router interface vrrp bfd-enable

configure router interface ipv6 vrrp bfd-enable

Description

This commands assigns a bidirectional forwarding detect (BFD) session to a specific VRRP/SRRP instance. This BFD sessions provided a heartbeat mechanism that can be used to speed up the transition of the standby VRRP router to an active state. If the associated BFD session fails, the VRRP routers will immediately send a VRRP Advertisement message. In addition, the standby VRRP router(s) will transition to a Master state to speed convergence. The normal VRRP election process will then take place based on the Advertisement messages sent by all VRRP routers.

There can be only one BFD session assigned to any given VRRP/SRRP instance, but there can be multiple SRRP/VRRP sessions using the same BFD session.

The parameters used for the BFD sessions are set by the BFD command under the IP interface.

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

Parameters

interface-name

Specifies the name of the interface running BFD. The specified interface may not yet be configured with BFD. However, when it is, this virtual router will then initiate the BFD session.

ip-address

Specifies the destination address to be used for the BFD session.

svc-id

Specifies the service ID of the interface running BFD.

Values

service-id:1 to 2147483647

svc-name: 64 characters maximum

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>oper-group bfd-enable)

Full Context

configure service oper-group bfd-enable

Description

This command associates a BFD sessions with the named oper-group so that if the BFD session fails then the oper-group is changed to operationally down and all monitoring interfaces should also be brought operationally down.

Parameters

interface-name

Specifies the source interface, up to 32 characters in length, for the BFD sessions to be monitored for the associated oper-group.

ipv4-address

Specifies the destination IPv4 address for the BFD sessions to be monitored for the associated oper-group.

service-id

Specifies the service ID, up to 64 characters in length, in which the BFD session exists if it is not in the base routing context.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>isis>if bfd-enable)

Full Context

configure router isis interface bfd-enable

Description

This command enables the use of bidirectional forwarding detection (BFD) to control IPv4 or IPv6 adjacencies. By enabling BFD on an IPv4 or IPv6 protocol interface, the state of the protocol interface is tied to the state of the BFD session between the local node and the remote node. The parameters used for the BFD are set by the BFD command under the IP interface. This command must be given separately to enable or disable BFD for both IPv4 and IPv6.

The no form of this command removes BFD from the associated adjacency.

Default

no bfd-enable ipv4

no bfd-enable ipv6

Parameters

ipv4

Keyword to enable BFD to control IPv4 adjacencies.

ipv6

Keyword to enable BFD to control IPv6 adjacencies.

include-bfd-tlv

Enables support for the IS-IS BFD TLV options in accordance with RFC 6213, which specifies that a BFD session must be established before an IS-IS adjacency can transition to the established state. This option must be enabled on all IS-IS neighbors on a shared interface.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>ospf3>area>interface bfd-enable)

[Tree] (config>router>ospf>area>interface bfd-enable)

Full Context

configure router ospf3 area interface bfd-enable

configure router ospf area interface bfd-enable

Description

This command configures BFD to control the state of the associated protocol interface. By enabling BFD on a protocol interface, the state of the protocol interface is tied to the state of the BFD session between the local node and the remote node. The parameters used for the BFD session are set through the bfd command under the IP interface.

The no form of this command removes BFD from the associated OSPF protocol adjacency.

Default

no bfd-enable

Parameters

remain-down-on-failure

Keyword to specify that OSPF brings down the adjacency and waits on BFD again if the BFD session does not come back up within 10 seconds. This can cause OSPF neighbors to flap, because OSPF will form the adjacency and then bring it down if the BFD session is still down. If this parameter is not configured, the OSPF adjacency will form even if the BFD adjacency does not come back up after a failure.

strict

Keyword to specify that the system uses BFD strict-mode, which requires that an active BFD session exists between the OSPF neighbors before establishing a full adjacency. When this keyword is configured, the router uses Link-Local Signaling (LLS) with the B-flag set to instruct OSPF neighbors that BFD must be enabled on the link. BFD strict-mode requires that both sides have the B-flag set.

During OSPFv3 BFD strict-mode operations, the router advertises the Local Interface IPv4 Address TLV using LLS, but the SR OS router continues to use IPv6-based BFD sessions for both the IPv4 and IPv6 address families.

strict-mode-holddown number

Keyword to specify a delay in bringing up the OSPF adjacency after the BFD session is established. Holddown helps mitigate potential routing churn when BFD sessions are unstable. The holddown timer is reset on an adjacency when a BFD session operationally toggles.

Values

1 to 600

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>rip>group bfd-enable)

[Tree] (config>router>ripng>group bfd-enable)

[Tree] (config>router>rip bfd-enable)

[Tree] (config>router>ripng>group>neighbor bfd-enable)

[Tree] (config>router>ripng bfd-enable)

[Tree] (config>router>rip>group>neighbor bfd-enable)

Full Context

configure router rip group bfd-enable

configure router ripng group bfd-enable

configure router rip bfd-enable

configure router ripng group neighbor bfd-enable

configure router ripng bfd-enable

configure router rip group neighbor bfd-enable

Description

This command enables bidirectional forwarding detection (BFD) to control the state of the associated protocol adjacency. By enabling BFD on a given protocol interface, the state of the RIP neighbor is tied to the state of the BFD session between the local node and the remote node. The parameters used for the BFD are set using the bfd command under the IP interface configuration context.

The no form of this command removes BFD from the associated protocol adjacency.

Platforms

7705 SAR Gen 2

Context

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

Full Context

configure router segment-routing maintenance-policy bfd-enable

Description

This command enables seamless BFD on every programmed segment list of an SR policy candidate path to which the maintenance policy is applied. BFD session parameters are taken from the BFD template that is configured for the maintenance policy.

The no form of this command disables seamless BFD on every segment list of an SR policy.

Default

no bfd-enable

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>bgp bfd-strict-mode)

[Tree] (config>service>vprn>bgp>group>neighbor bfd-strict-mode)

[Tree] (config>router>bgp>group bfd-strict-mode)

[Tree] (config>router>bgp>group>neighbor bfd-strict-mode)

[Tree] (config>service>vprn>bgp bfd-strict-mode)

[Tree] (config>service>vprn>bgp>group bfd-strict-mode)

Full Context

configure router bgp bfd-strict-mode

configure service vprn bgp group neighbor bfd-strict-mode

configure router bgp group bfd-strict-mode

configure router bgp group neighbor bfd-strict-mode

configure service vprn bgp bfd-strict-mode

configure service vprn bgp group bfd-strict-mode

Description

Commands in this context configure the BFD Strict-Mode feature.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>bfd bfd-template)

Full Context

configure router bfd bfd-template

Description

This command configures a BFD template. A BFD template defines the set of configurable parameters used by a BFD session. These include the transmit and receive timer intervals used for BFD CC packets, the transmit timer interval used when the session is providing a CV function, the multiplier value, the echo-receive interval, and whether the BFD session terminates in the CPM network processor.

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

Default

no bfd-template

Parameters

name

Specifies a text string name for the template, up to 32 characters in printable 7-bit ASCII, enclosed in double quotes.

Platforms

7705 SAR Gen 2

Context

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

Full Context

configure router segment-routing maintenance-policy bfd-template

Description

This command references a named BFD template that is used by seamless BFD. The template specifies parameters, such as the minimum transmit and receive control packet timer intervals, that are used by the BFD session. Templates are configured under the config>router>bfd context.

A BFD template must exist on the system before being referenced from a maintenance policy.

The no form of this command removes the configured template.

Parameters

bfd-template

Specifies the name of the BFD template, up to 32 characters.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>epipe bgp)

Full Context

configure service epipe bgp

Description

Commands in this context configure the BGP-related parameters BGP uses for multihoming and BGP VPWS.

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

Default

bgp 1

Parameters

bgp-instance

The BGP instance.

Values

1 to 2

Platforms

7705 SAR Gen 2

Context

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

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

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

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

Full Context

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

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

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

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

Description

This command selects the BGP tunnel type.

This command instructs BGP EVPN to search for a BGP LSP to the address of the BGP next hop. If the user does not enable the BGP tunnel type, inter-area or inter-as prefixes are not resolved.

The no form of this command removes the BGP tunnel type configuration.

Default

bgp

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vpls bgp)

Full Context

configure service vpls bgp

Description

Commands in this context configure the BGP related parameters for BGP VPLS.

A maximum of two BGP instances can be configured in a VPLS service. The bgp-instance parameter value can be configured as 1 or 2. If it is not specified, the parameter value is configured as 1 by default.

The route-distinguisher configured in BGP instance 1 and 2 must be different. However, the route-target value may be configured the same or different for the two instances.

Only BGP-EVPN MPLS is allowed to be assigned to instance 2. Instance 1 must be used for the VXLAN and L2VPN address families.

BGP-EVPN VXLAN and BGP-EVPN MPLS can only be configured as no shutdown in the same service if they are associated with different instances (When the two BGP instances are created, the bgp-instance command must be configured in the bgp-evpn mpls context).

The evi value in bgp-evpn can be used to auto-derive the route distinguisher in instance 1 only. However, the evi value can be used to auto-derive the route-target in both instances.

The no version of the command removes the BGP instance.

Parameters

bgp-instance

Specifies the value associated with the BGP instance.

Values

1 to 2

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router bgp)

Full Context

configure router bgp

Description

This command creates the BGP protocol instance and BGP configuration context. BGP is administratively enabled upon creation.

The no form of this command deletes the BGP protocol instance and removes all configuration parameters for the BGP instance. BGP must be shutdown before deleting the BGP instance. An error occurs if BGP is not shutdown first.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn bgp)

Full Context

configure service vprn bgp

Description

This command enables the BGP protocol with the VPRN service.

The no form of this command disables the BGP protocol from the given VPRN service.

Default

no bgp

Platforms

7705 SAR Gen 2

Context

[Tree] (debug>router>pim bgp)

Full Context

debug router pim bgp

Description

This command enables debugging for PIM/BGP-specific interoperation.

The no form of this command disables debugging for PIM/BGP-specific interoperation.

Parameters

src-Addr

Debugs BGP information associated with the specified source.

Values

source address (ipv4, ipv6)

grp-Addr

Debugs BGP information associated with the specified group.

Values

group address (ipv4, ipv6)

PeerAddr

Debugs BGP information associated with the specified peer.

Values

peer address (ipv4, ipv6)

Platforms

7705 SAR Gen 2

Context

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

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

Full Context

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

configure router bgp next-hop-resolution shortcut-tunnel family resolution-filter bgp

Description

This command selects BGP tunneling for next-hop resolution and specifies the IPv4 tunnels created by receiving BGP label-unicast IPv4 routes for /32.

The no form of this command disables the selection of BGP tunneling for next-hop resolution.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>auto-bind-tunnel>res-filter bgp)

Full Context

configure service vprn auto-bind-tunnel resolution-filter bgp

Description

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vpls bgp-ad)

Full Context

configure service vpls bgp-ad

Description

This command configures BGP auto-discovery.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>system bgp-auto-rd-range)

Full Context

configure service system bgp-auto-rd-range

Description

This command defines the type-1 route-distinguisher IPv4 address and community value range within which the system will select a route-distinguisher for the bgp-enabled services using auto-rd.

Interactions:

This command is used along with the route-distinguisher auto-rd command supported in VPLS, VPRN and Epipe services. The system forces the user to create a bgp-auto-range before the auto-rd option can be used in the services.

The system will keep allocating values for services configured with route-distinguisher auto-rd as long as there are available community values within the configured range. After the command is added, the following changes are allowed:

• The ip-address can be changed without modifying the comm-val range, even if services using auto-rd are present. The affected routes will be withdrawn and re-advertised with the new route-distinguishers.

• The comm-val range can be modified as long as no conflicting values are present in the new range. For example, the user may expand the range as long as the new range does not overlap with existing manual route-distinguishers. The user may also reduce the range as long as the new range can accommodate the already allocated auto-RDs.

Parameters

ip-address

Specifies the IPv4 address used in the first 4 octets of all the type-1 auto route-distinguishers selected by the system.

comm-val

Specifies the community value of the type-1 auto route-distinguisher.

Values

1 to 65535

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>system bgp-evpn)

[Tree] (config>service>epipe bgp-evpn)

[Tree] (config>service>vpls bgp-evpn)

Full Context

configure service system bgp-evpn

configure service epipe bgp-evpn

configure service vpls bgp-evpn

Description

Commands in this context configure the BGP EVPN parameters in the base instance.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn bgp-evpn)

Full Context

configure service vprn bgp-evpn

Description

Commands in this context configure the BGP EVPN parameters.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>policy-options>policy-statement>entry>action bgp-high-priority)

[Tree] (config>router>policy-options>policy-statement>default-action bgp-high-priority)

Full Context

configure router policy-options policy-statement entry action bgp-high-priority

configure router policy-options policy-statement default-action bgp-high-priority

Description

This command enables eligible BGP routes matched by the policy entry or policy default-action that are tagged for faster route table updates.

This action applies only when the policy is applied as a BGP import policy to a base router BGP peer or VPRN BGP peer and applies only to the following route types:

• IPv4

• label-IPv4

• IPv6

• label-IPv6

This command is useful when the BGP RIB contains a large number of routes and quick routing table updates are needed for a small subset of these routes. The effectiveness of this command decreases as the subset becomes a larger proportion of the total RIB.

The no form of this command disables the routes that are tagged for faster route table updates.

Default

no bgp-high-priority

Platforms

7705 SAR Gen 2

Context

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

Full Context

configure service vprn bgp-ipvpn

Description

Commands in this context configure the BGP IPVPN parameters.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>mpls-labels bgp-labels-hold-timer)

Full Context

configure router mpls-labels bgp-labels-hold-timer

Description

This command configures the time to delay before the label-forwarding entries programmed by BGP are removed from the datapath. A non-zero delay is useful in the following situations:

• label-unicast route is readvertised by an ABR/ASBR operating in label-per-next-hop mode to choose a new primary path

• IP VPN route is readvertised by an ABR/ASBR operating in label-per-next-hop mode to choose a new primary path

• IP VPN best-external route is readvertised by a VPRN to choose a new backup path

• IP VPN route is readvertised by a VPRN in label-per-next-hop mode to choose a new primary path

In the preceding situations, configure the hold timer to be large enough to account for the propagation delay of the route withdrawal to all ingress routers.

Default

bgp-labels-hold-timer 0

Parameters

seconds

Specifies the time delay, in seconds.

Values

0 to 255

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>policy-options>policy-statement>entry>action bgp-leak)

[Tree] (config>router>policy-options>policy-statement>default-action bgp-leak)

Full Context

configure router policy-options policy-statement entry action bgp-leak

configure router policy-options policy-statement default-action bgp-leak

Description

This command causes qualifying matched BGP routes to be marked as leakable, meaning they are candidates to be leaked into other routing instances (copied with their complete set of path attributes). A BGP route is a qualifying route if it is an IPv4 route (unlabeled), IPv6 route (unlabeled) or a label-IPv4 route.

The bgp-leak command has an effect only when the policy is applied as a BGP import policy in the base router or a VPRN context.

Default

no bgp-leak

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>policy-options>policy-statement>entry>action bgp-med)

[Tree] (config>router>policy-options>policy-statement>default-action bgp-med)

Full Context

configure router policy-options policy-statement entry action bgp-med

configure router policy-options policy-statement default-action bgp-med

Description

This command changes the BGP MED attribute value in BGP routes matched by the route policy entry (or the policy default action).

If the matched route already has a MED attribute, this command overwrites the existing value. If the matched route does not have a MED attribute, then one is added and the value is set based on the parameters of this command.

This command has no effect on non-BGP routes. The default, no bgp-med, does not modify MED values.

Default

no bgp-med

Parameters

expression

Specifies a logical expression parsed as a string. The string can contain:

• parentheses () to change the order of operations

• mathematical operators: + (addition), - (subtraction) and * (multiplication)

• directly entered decimal values that act as operands of the mathematical operators. Each decimal value supports up to three decimal places precision in the range of 0.000 to 4294967295.000

• decimal values represented by parameter names (using the usual @parameter-name@ syntax) that act as operands of the mathematical operators. Each parameterized decimal value supports up to three decimal places precision in the range of 0.000 to 4294967295.000

igp

Instructs the policy to set the MED based on the current route table or tunnel table cost to resolve the BGP next-hop address.

min-igp

Instructs the policy to set the MED based on the minimum route table or tunnel table cost to resolve the BGP next-hop of the route, over its lifetime in the local RIB.

med-value

Specifies a new MED value (or parameter name to use for the new MED value) to use with the route.

Values

value

• 0 to 4294967295

param-name

• up to 32 characters

• Must start and end with an at-sign (@)

Platforms

7705 SAR Gen 2

Context

[Tree] (config>redundancy bgp-multi-homing)

Full Context

configure redundancy bgp-multi-homing

Description

This command configures BGP multi-homing parameters.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>system>bgp-evpn>ad-per-evi-routes bgp-path-selection)

Full Context

configure service system bgp-evpn ad-per-evi-routes bgp-path-selection

Description

This command compares the received EVPN VPWS AD per-EVI routes based on BGP path attributes.

Attribute propagation must be configured before configuring this command.

The no form of this command disables the comparison of the routes.

Default

no bgp-path-selection

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>system>bgp-evpn>ip-prefix-routes>iff bgp-path-selection)

Full Context

configure service system bgp-evpn ip-prefix-routes interface-ful bgp-path-selection

Description

This command enables BGP path selection for EVPN-IFF (Interface-ful) routes.

Once the command is enabled, the EVPN-IFF routes are ordered and selected in a similar manner as IPVPN or EVPN-IFL routes, that is, based on the regular BGP path selection process.

The no form of this command causes the system to order EVPN-IFF routes based on their {R-VPLS Ifindex, RD, Ethernet Tag}. For example, if two EVPN-IFF routes with different Route Distinguishers (RDs) are received for the same prefix on the same R-VPLS, the route with the lowest RD is selected.

Default

no bgp-path-selection

Parameters

d-path-length-ignore

Keyword used to make EVPN ignore the D-PATH length when iff-bgp-path-selection is enabled.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>filter>match-list>ipv6-prefix-list>apply-path bgp-peers)

[Tree] (config>filter>match-list>ip-prefix-list>apply-path bgp-peers)

Full Context

configure filter match-list ipv6-prefix-list apply-path bgp-peers

configure filter match-list ip-prefix-list apply-path bgp-peers

Description

This command configures auto-generation of IPv4 or IPv6 address prefixes (as required by the context that the command is executed within) based on the base router BGP instance configuration.

The no form of this command removes the bgp-peers configuration for auto-generation of address prefixes for the specified index value.

Parameters

service-name

Specifies the service name, up to 64 characters in length.

group

Configures a match against the base router BGP instance group configuration.

Regex match (.*) can be used to match against any group.

neighbor

Configures a match against the base router BGP instance neighbor configuration.

Regex match (.*) can be used to match against any neighbor.

criterion-index

Specifies an integer from 1 to 255 enumerating BGP peers auto-generation configuration within this list.

router-instance

Specifies the router name or service ID.

Values

router-instance: router-name or vprn-svc-id

router-name: "Base"

vprn-svc-id: 1 to 2147483647

service-name: Specifies the service name, up to 64 characters in length.

router

Configures a match against the base router BGP instance configuration.

reg-exp

Specifies a regular expression that defines a match string, up to 255 characters in length, to be used to auto-generate address prefixes. Matching is performed from the least-significant digit. For example, a string 10.0 matches all neighbors with addresses starting with 10, such as 10.0.x.x or 10.0xx.x.x.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn bgp-shared-queue)

Full Context

configure service vprn bgp-shared-queue

Description

This command enables all BGP peers within a VPRN instance to share a single CPM queue. This command takes effect on new BGP connections established; already established BGP peers continue to use their own CPM queue. Any changes to PIR/CIR of the shared queue takes effect only after BGP connections are re-established.

Parameters

cir rate

Specifies the CIR rate for the shared queue.

pir rate

Specifies the PIR rate for the shared queue.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>mpls>lsp bgp-shortcut)

[Tree] (config>router>mpls>lsp-template bgp-shortcut)

Full Context

configure router mpls lsp bgp-shortcut

configure router mpls lsp-template bgp-shortcut

Description

This command enables the use of RSVP LSP for IPv4 BGP routes.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>mpls>lsp bgp-transport-tunnel)

[Tree] (config>router>mpls>lsp-template bgp-transport-tunnel)

Full Context

configure router mpls lsp bgp-transport-tunnel

configure router mpls lsp-template bgp-transport-tunnel

Description

This command allows or blocks RSVP-TE LSP to be used as a transport LSP for BGP tunnel routes.

Default

bgp-transport-tunnel include

Parameters

include

Allows RSVP-TE LSP to be used as transport LSP from the ASBR to local PE router, from ingress PE to ASBR in the local AS or between multi-hop External Border Gateway Protocol (EBGP) peers with ASBR to ASBR adjacency.

exclude

Blocks RSVP-TE LSP to be used as transport LSP from the ASBR to local PE router, from ingress PE to ASBR in the local AS or between multi-hop EBGP peers with ASBR to ASBR adjacency.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>sdp bgp-tunnel)

Full Context

configure service sdp bgp-tunnel

Description

This command allows the use of BGP route tunnels available in the tunnel table to reach SDP far-end nodes. Use of BGP route tunnels are only available with MPLS-SDP. Only one of the transport methods is allowed per SDP - LDP, RSVP-LSP BGP, SR-ISIS, or SR-OSPF. This restriction is relaxed for some combinations of the transport methods when the mixed-lsp-mode option is enabled within the SDP.

The no form of the command disables resolving BGP route tunnel LSP for SDP far-end.

Default

no bgp-tunnel (BGP tunnel route to SDP far-end is disabled)

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>bgp bgp-tunnel-metric)

Full Context

configure router bgp bgp-tunnel-metric

Description

This command sets the TTM metric of all BGP tunnels to a fixed value or a value derived from the AIGP or the MED metric of the BGP-LU route, if the BGP-LU route has an AIGP or MED path attribute. Otherwise, the TTM metric is set to the number specified using the value parameter. BGP import policies override the configuration of this command.

By default, BGP tunnels are installed with a fixed cost of 1000 in the tunnel table. This can overstate or understate their true cost when compared to other tunnels with IGP-derived costs.

The no form of the command configures the router to use the default value.

Default

no bgp-tunnel-metric

Parameters

value

Specifies the BGP tunnel metric.

Values

0 to 4294967295

prefer-aigp

Specifies that the TTM metric is based on the AIGP metric value of the BGP-LU route. When a BGP-LU route is selected for installation in TTM and is not matched by a BGP import policy entry that overrides the BGP tunnel metric action, the TTM metric of the tunnel is set to the AIGP metric value of the BGP-LU route with the resolved cost to the BGP next hop of the route added to it. Otherwise, the metric is set to the value configured using the value parameter.

prefer-med

Specifies that the TTM metric is based on the MED metric value of the BGP-LU route. When a BGP-LU route is selected for installation in TTM and is not matched by a BGP import policy entry that overrides the BGP tunnel metric action, the TTM metric of the tunnel is set to the MED metric value of the BGP-LU route with the resolved cost to the BGP next hop of the route added to it. Otherwise, the metric is set to the value configured using the value parameter.

Note: prefer-aigp takes precedence over this parameter if the received BGP-LU has both attributes.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>policy-options>policy-statement>default-action bgp-tunnel-metric)

[Tree] (config>router>policy-options>policy-statement>entry>action bgp-tunnel-metric)

Full Context

configure router policy-options policy-statement default-action bgp-tunnel-metric

configure router policy-options policy-statement entry action bgp-tunnel-metric

Description

This command sets the TTM metric of all BGP tunnels matched by the policy entry or the policy default action to a fixed value or a value derived from the AIGP or the MED metric of the BGP-LU route, if the BGP-LU route has an AIGP or MED path attribute. Otherwise, the TTM metric is set to the number specified using the value parameter.

The no form of this command configures the router to use the default value.

Default

no bgp-tunnel-metric

Parameters

value

Specifies the BGP tunnel metric.

Values

0 to 4294967295

param-name

Specifies the parameter name, up to 32 characters that starts and ends with an at-sign (@).

prefer-aigp

Specifies that if a BGP-LU route is selected for installation in the TTM and is matched by this action in a BGP import policy, the TTM metric of the tunnel is set to the AIGP metric value of the BGP-LU route with the IGP cost to reach the BGP next hop added to it.

prefer-med

Specifies that if a BGP-LU route is selected for installation in the TTM and is matched by this action in a BGP import policy, the TTM metric of the tunnel is set to the MED metric value of the BGP-LU route with the IGP cost to reach the BGP next hop added to it.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>bgp bgp-tunnel-preference)

Full Context

configure router bgp bgp-tunnel-preference

Description

This command configures the tunnel table preference for BGP-LU tunnel type away from its default value.

The tunnel table preference applies to the next-hop resolution of BGP routes of the following families: EVPN, IPv4, IPv6, VPN-IPv4, VPN-IPv6, label-IPv4, and label-IPv6 in the tunnel table.

This feature does not apply to a VPRN, VPLS, or VLL service with explicit binding to an SDP which enabled the mixed-lsp-mode option. The tunnel preference, in such an SDP, is fixed and is controlled by the service manager. The configuration of the tunnel table preference parameter does not modify the behavior of such an SDP and the services that bind to it.

It is recommended to not set two or more tunnel types to the same preference value. In such a situation, the tunnel table prefers the tunnel type which was first introduced in SR OS implementation historically.

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

Default

bgp-tunnel-preference 12

Parameters

preference

Specifies the BGP tunnel preference.

Values

1 to 255

Default

12

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vpls bgp-vpls)

Full Context

configure service vpls bgp-vpls

Description

Commands in this context configure the BGP-VPLS parameters and addressing.

Platforms

7705 SAR Gen 2

Context

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

Full Context

configure service vpls sap bgp-vpls-mh-ve-id

Description

This command upon the configuration of the ve-id under the SAP and if BGP-VPLS is configured and is operationally up, causes the PE to advertise a bgp-mh route for the ve-id (the route does not contain label information). The bgp-mh route contains the F and D flags properly set based on the SAP operational state. Upon switchover, the former active PE (DF in case of EVPN-MH) sends an update with a transition of the F bit from 1 to 0. This is an indication for the remote PEs to flush their MACs associated to the advertising PE.

This command is required when MC-LAG or EVPN-MH is used for multi-homing redundancy and mac-flush is required at remote BGP-VPLS PEs when there is a failure in the active PE.

The no form of this command withdraws the L2 VPN route.

Parameters

number

Specifies the BGP-VPLS multi-homing virtual-edge identifier.

Values

1 to 65535

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>epipe bgp-vpws)

Full Context

configure service epipe bgp-vpws

Description

Commands in this context configure BGP-VPWS parameters and addressing.

Default

no bgp-vpws

Platforms

7705 SAR Gen 2

Context

[Tree] (config>system>security>keychain>direction bi)

Full Context

configure system security keychain direction bi

Description

This command configures keys for both send and receive stream directions.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>oam-pm>bin-group>bin-type bin)

Full Context

configure oam-pm bin-group bin-type bin

Description

Commands in this context configure the thresholds for the specified bin.

Parameters

bin-number

Specifies bin to configure.

Values

1 to 9

Platforms

7705 SAR Gen 2

Context

[Tree] (config>oam-pm bin-group)

Full Context

configure oam-pm bin-group

Description

This command allows the operator to configure the parameters for a specific bin group. Bin-group 1 is a default bin-group and cannot be modified. If no bin group is assigned to an oam-pm session, this is assigned by default. The default values for bin-group 1 are (fd-bin-count 3 bin 1 lower-bound 5000us, bin 2 lower-bound 10000us fdr-bin-count 2 bin 1lower-bound 5000us and ifdv-bin-count 2 bin 1lower-bound 5000us)

The no form of this command disables the OAM Performance Monitoring bin group.

Parameters

bin-group-number

Specifies an identifier for a bin-group that is referenced by oam-pm sessions. A bin group can only shutdown and modified when all the PM Sessions referencing the bin group have been shutdown. The only exception is the description parameter.

Values

1 to 255

fd-bin-count

Specifies the number of frame delay bins that are created.

Values

2 to 10

fdr-bin-count

Specifies the number of frame delay range bins that are created.

Values

2 to 10

ifdv-bin-count

Specifies the number of inter-frame delay variation bins that are created.

Values

2 to 10

create

Keyword that creates the bin group.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>oam-pm>session bin-group)

Full Context

configure oam-pm session bin-group

Description

This command links the individual test to the group of bins that map the probe responses.

The no form of this command installs the default bin-group 1 as the bin-group for the session.

Parameters

bin-group-number

Specifies the number that was used to create the specific bin-group that is referenced for this session.

Values

1 to 255

Default

1

Platforms

7705 SAR Gen 2

Context

[Tree] (config>oam-pm>bin-group bin-type)

Full Context

configure oam-pm bin-group bin-type

Description

This command is the start of the hierarchy where the specific delay metric bin structure isis defined.

Parameters

fd

Keyword to enter the frame delay bin threshold configuration.

fdr

Keyword to enter the frame delay range bin threshold configuration.

ifdv

Keyword to enter the inter-frame delay variation bin thresholds configuration.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>system>security>ldap>server bind-authentication)

Full Context

configure system security ldap server bind-authentication

Description

This command configures the LDAP binding used to log into LDAP server. A string of domain components (DC) and common names (CN) can be programmed to identify the user in addition to the password field. The password is hashed. For example, "cn=admin,dc=nokia,dc=com” indicates the user admin in domain nokia.com. LDAP Attributes lists the LDAP attributes.

The no version of this command removes the bind-authentication.

Parameters

root-dn

Up to 512 characters.

password

Configures the password which enables a user to bind to the LDAP server. The maximum length is 128 characters.

hash

Specifies that the password is entered in an encrypted form. If the hash or hash2 parameter is not used, the password is assumed to be in an unencrypted, clear text form. For security, all passwords are stored in encrypted form in the configuration file with the hash or hash2 parameter specified

hash2

Specifies the password is entered in a more complex encrypted form that involves more variables than the password value alone, meaning that the hash2 encrypted variable cannot be copied and pasted. If the hash or hash2 parameter is not used, the password is assumed to be in an unencrypted, clear text form. For security, all passwords are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.

custom

Specifies the custom encryption to management interface.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>mpls>fwd-policies>fwd-policy binding-label)

Full Context

configure router mpls forwarding-policies forwarding-policy binding-label

Description

This command configures a binding label for the MPLS forwarding policy.

The policy associates an incoming label, referred to as a binding label, to an NHG in which the primary and backup direct or indirect next hops are defined. This type of MPLS forwarding policy is referred to as a label-binding policy.

The no form of the command removes the binding label from the MPLS forwarding policy.

Parameters

label-number

Specifies the label number.

Values

32 to 1048575

Platforms

7705 SAR Gen 2

Context

[Tree] (config>filter>redirect-policy-binding binding-operator)

Full Context

configure filter redirect-policy-binding binding-operator

Description

This command configures the logical operator to use with the destinations test results to obtain the master test result (the redirect-policy binding test result). A change in this configuration results in the re-evaluation of the master test result.

The no version of this command sets the value to its default

Default

binding-operator and

Parameters

and | or

Keyword to specify the type of logical or boolean operation to perform between the individual destinations test results to obtain the master result.

Platforms

7705 SAR Gen 2

Context

[Tree] (conf>router>segment-routing>sr-policies>policy binding-sid)

Full Context

configure router segment-routing sr-policies static-policy binding-sid

Description

This command associates a binding SID with a statically defined segment routing policy. This is a mandatory parameter and configuration command to enable the segment routing policy; if the binding SID label value is not configured, the execution of the no shutdown command on the static segment routing policy fails.The BSID label should be an available label in the reserved-label-block range.

The no form of this command removes the BSID association.

Default

no binding-sid

Parameters

number

Specifies the binding SID label value.

Values

32 to 1048575

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>mpls>lsp binding-sid)

Full Context

configure router mpls lsp binding-sid

Description

This command configures a binding SID label for the LSP. The label value must belong to the reserved label block that is configured with the configure router mpls lsp-bsid-block command.

The no form of this command unbinds the label, removes the ILM entry, and triggers the appropriate PCEP messages.

Parameters

label

Specifies an MPLS label value from a specific reserved label block.

Values

32 to 1048575

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>mpls>lsp-template binding-sid)

Full Context

configure router mpls lsp-template binding-sid

Description

This command configures the system to allocate and bind a label to any LSP that is created using the template.

The no form of this command removes the configuration but does not affect LSPs that were already created using the template.

Default

no binding-sid

Platforms

7705 SAR Gen 2

Context

[Tree] (debug>router>ldp>peer>event bindings)

Full Context

debug router ldp peer event bindings

Description

This command displays debugging information about addresses and label bindings learned from LDP peers for LDP bindings.

The no form of the command disables the debugging output.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>static-route-entry black-hole)

Full Context

configure service vprn static-route-entry black-hole

Description

This command specifies that the route is a black hole route. If the destination address on a packet matches this static route, it will be silently discarded.

Default

no black-hole

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>static-route-entry black-hole)

Full Context

configure router static-route-entry black-hole

Description

This command specifies that the route is a black hole route. If the destination address on a packet matches this static route, it will be silently discarded.

Default

no black-hole

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vpls>bgp-evpn>mac-duplication black-hole-dup-mac)

Full Context

configure service vpls bgp-evpn mac-duplication black-hole-dup-mac

Description

The black-hole-dup-mac command is disabled by default. If enabled, a duplicated MAC detected in the network is programmed as a black-hole MAC in the FDB and displayed in the show service id fdb detail command as follows:

• Source-Identifier—black-hole

• Type—EvpnD:P

Because the MAC is now programmed in the FDB as a black-hole, all received frames with MAC DA matching the duplicate MAC are discarded. The duplicate black-hole MACs are installed as Protected, therefore, all received frames with MAC SA matching the duplicate MAC are discarded by default.

A BGP-EVPN (MPLS or VXLAN) shutdown is required to add or remove the black-hole-dup-mac command.

The no form of the command removes the feature, and duplicate MACs are no longer programmed as black-hole MACs.

Default

no black-hole-dup-mac

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>ospf>area blackhole-aggregate)

[Tree] (config>service>vprn>ospf3>area blackhole-aggregate)

Full Context

configure service vprn ospf area blackhole-aggregate

configure service vprn ospf3 area blackhole-aggregate

Description

This command installs a low priority blackhole route for the entire aggregate. Existing routes that make up the aggregate have a higher priority and only the components of the range for which no route exists are blackholed.

It is possible that when performing area aggregation, addresses may be included in the range for which no actual route exists. This can cause routing loops. To avoid this problem, configure the blackhole-aggregate command.

The no form of this command removes this configuration.

Default

blackhole-aggregate

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>ospf>area blackhole-aggregate)

[Tree] (config>router>ospf3>area blackhole-aggregate)

Full Context

configure router ospf area blackhole-aggregate

configure router ospf3 area blackhole-aggregate

Description

This command installs a low priority blackhole route for the entire aggregate. Existing routes that make up the aggregate will have a higher priority and only the components of the range for which no route exists are blackholed.

When performing area aggregation, addresses may be included in the range for which no actual route exists, which can cause routing loops. To avoid this problem, configure the blackhole-aggregate option.

The no form of this command removes this option.

Default

blackhole-aggregate

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>nat>nat-policy block-limit)

Full Context

configure service nat nat-policy block-limit

Description

This command configures the maximum number of port blocks per subscriber.

The no form of the command reverts to the default.

Default

block-limit 1

Parameters

1..40

Specifies the maximum number of port-blocks per NAT subscriber.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vpls>endpoint block-on-mesh-failure)

[Tree] (config>service>vpls>spoke-sdp block-on-mesh-failure)

Full Context

configure service vpls endpoint block-on-mesh-failure

configure service vpls spoke-sdp block-on-mesh-failure

Description

This command enables blocking (brings the entity to an operationally down state) after all configured SDPs or endpoints are in operationally down state. This event is signaled to corresponding T-LDP peer by withdrawing service label (status-bit-signaling non-capable peer) or by setting "PW not forwarding” status bit in T-LDP message (status-bit-signaling capable peer).

The no form of this command reverts to the default.

Default

no block-on-mesh-failure

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>epipe>spoke-sdp block-on-peer-fault)

Full Context

configure service epipe spoke-sdp block-on-peer-fault

Description

When enabled, this command blocks the transmit direction of a PW when any of the following PW status codes is received from the far end PE:

The transmit direction is unblocked when the following PW status code is received:

This command is mutually exclusive with no pw-status-signaling, and standby-signaling-slave. It is not applicable to spoke SDPs forming part of an MC-LAG or spoke SDPs in an endpoint.

Default

no block-on-peer-fault

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>pw-template block-on-peer-fault)

Full Context

configure service pw-template block-on-peer-fault

Description

When enabled, this command blocks the transmit direction of a pseudowire when any of the following pseudowire status codes is received from the far end PE:

The transmit direction is unblocked when the following pseudowire status code is received:

This command is mutually exclusive with no pw-status-signaling, and standby-signaling-slave. It is not applicable to spoke SDPs forming part of an MC-LAG or spoke SDPs in an endpoint.

Default

no block-on-peer-fault

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>bgp>group>neighbor block-prefix-sid)

[Tree] (config>router>bgp block-prefix-sid)

[Tree] (config>router>bgp>group block-prefix-sid)

Full Context

configure router bgp group neighbor block-prefix-sid

configure router bgp block-prefix-sid

configure router bgp group block-prefix-sid

Description

This command specifies whether all prefix SID attributes are removed from label IPv4 and label IPv6 routes when they are exchanges with EBGP and IBGP peers covered by the scope of the command. Even locally-imposed prefix SID attributes are removed.

A change of this configuration causes the affected BGP sessions to flap.

The no form of this command allows prefix SID attributes associated with label IPv4 and label IPv6 routes to be propagated without restriction.

Default

no block-prefix-sid

Platforms

7705 SAR Gen 2

Context

[Tree] (bof)

Full Context

bof

Description

This command creates or edits the boot option file (BOF) for the specified local storage device.

A BOF file specifies where the system searches for runtime images, configuration files, and other operational parameters during system initialization.

BOF parameters can be modified. Changes can be saved to a specified compact flash. The BOF must be located in the root directory of either an internal or external compact flash local to the system and have the mandatory filename of bof.cfg.

When modifications are made to in-memory parameters that are currently in use or operating, the changes are effective immediately. For example, if the IP address of the management port is changed, the change takes place immediately.

Only one entry of the BOF configuration command statement can be saved once the statement has been found to be syntactically correct.

When opening an existing BOF that is not the BOF used in the most recent boot, a message is issued notifying the user that the parameters will not affect the operation of the node.

No default boot option file exists. The router boots with the factory default boot sequence and options.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>lag>access booking-factor)

[Tree] (config>port>ethernet>access booking-factor)

Full Context

configure lag access booking-factor

configure port ethernet access booking-factor

Description

This command specifies the booking factor applied against the port or LAG administrator bandwidth by SAP administrator bandwidth CAC.

The service manager keeps track of the available administrator bandwidth for each port or LAG configured with an administrator bandwidth. The port or LAG available administrator bandwidth is adjusted by the user configured booking factor, allowing the port or LAG bandwidth to be overbooked or under booked.

If the booking factor is increased then available administrator bandwidth on the port or LAG increases. If the booking factor is decreased then available administrator bandwidth on the port or LAG decreases. However, if the reduction of available administrator bandwidth is insufficient to cover the sum of the current SAP administrator bandwidth on the port or LAG, the command fails.

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

Default

booking-factor 100

Parameters

factor

Specifies the percentage of the port or LAG admin bandwidth for SAP bandwidth CAC.

Values

1 to 1000

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>sdp booking-factor)

Full Context

configure service sdp booking-factor

Description

This command specifies the booking factor applied against the maximum SDP available bandwidth by the VLL CAC feature.

The service manager keeps track of the available bandwidth for each SDP. The maximum value is the sum of the bandwidths of all constituent LSPs in the SDP. The SDP available bandwidth is adjusted by the user configured booking factor. A value of 0 means no VLL can be admitted into the SDP.

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

Default

no booking-factor

Parameters

percentage

Specifies the percentage of the SDP maximum available bandwidth for VLL call admission. When the value of this parameter is set to zero (0), no new VLL spoke SDP bindings with non-zero bandwidth are permitted with this SDP. Overbooking, >100% is allowed.

Values

0 to 1000%

Default

100

Platforms

7705 SAR Gen 2

Context

[Tree] (config>system boot-bad-exec)

Full Context

configure system boot-bad-exec

Description

Use this command to configure a URL for a CLI script to exec following a failure of a bootup configuration. The command specifies a URL for the CLI scripts to be run following the completion of the bootup configuration. A URL must be specified or no action is taken.

The commands are persistent between router (re)boots and are included in the configuration saves (admin>save).

Related Commands

exec — This command executes the contents of a text file as if they were CLI commands entered at the console.

Default

no boot-bad-exec

Parameters

file-url

Specifies the location and name of the CLI script file executed following failure of the bootup configuration file execution. When this parameter is not specified, no CLI script file is executed.

Values

file url	local-url | remote-url	255 chars max
local-url	[cflash-id/][file-path]
remote-url	[{ftp://} login:pswd@remote-locn/][file-path]
	remote-locn	[hostname | ipv4-address | [ipv6- address]]
	ipv4-address	a.b.c.d
	ipv6-address	x:x:x:x:x:x:x:x[-interface]
		x:x:x:x:x:x:d.d.d.d[-interface]
		x - [0 to FFFF]H
		d - [0 to 255]D
		interface - 32 chars max, for link local addresses
cflash-id	cf1:, cf1-A:, cf1-B:, cf2:, cf2-A:, cf2-B:, cf3:, cf3-A:, cf3-B:

Platforms

7705 SAR Gen 2

Context

[Tree] (config>subscr-mgmt>loc-user-db>ipoe>host>options6 boot-file-param)

Full Context

configure subscriber-mgmt local-user-db ipoe host options6 boot-file-param

Description

This command configures a hexadecimal string that contains the value for the concatenation of all param-len n and parameter n fields of DHCPv6 option BOOTFILE_PARAM (60).

The no form of this command removes the configured string.

Parameters

hex-string

Specifies the hexadecimal format for this option, up to 254 hex nibbles.

Values

0x0 to 0xFFFFFFFF

Platforms

7705 SAR Gen 2

Context

[Tree] (config>subscr-mgmt>loc-user-db>ipoe>host>options6 boot-file-url)

Full Context

configure subscriber-mgmt local-user-db ipoe host options6 boot-file-url

Description

This command configures an ASCII string that contains the value for the boot-file-url field in the DHCPv6 option BOOTFILE_URL (59).

The no form of this command removes the configuration.

Parameters

ascii-string

Specifies the ASCII string, up to 127 characters.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>system boot-good-exec)

Full Context

configure system boot-good-exec

Description

Use this command to configure a URL for a CLI script to exec following the success of a bootup configuration.

Related Commands

exec - This command executes the contents of a text file as if they were CLI commands entered at the console.

Default

no boot-good-exec

Parameters

file-url

Specifies the location and name of the file executed following successful completion of the bootup configuration file execution. When this parameter is not specified, no CLI script file is executed.

Values

file url	local-url | remote-url	255 chars max
local-url	[cflash-id/][file-path]
remote-url	[{ftp://} login:pswd@remote-locn/][file-path]
	remote-locn	[hostname | ipv4-address | [ipv6- address]]
	ipv4-address	a.b.c.d
	ipv6-address	x:x:x:x:x:x:x:x[-interface]
		x:x:x:x:x:x:d.d.d.d[-interface]
		x - [0 to FFFF]H
		d - [0 to 255]D
		interface - 32 chars max, for link local addresses
cflash-id	cf1:, cf1-A:, cf1-B:, cf2:, cf2-A:, cf2-B:, cf3:, cf3-A:, cf3-B:

Platforms

7705 SAR Gen 2

Context

[Tree] (config>redundancy>multi-chassis>peer>mc-ep boot-timer)

Full Context

configure redundancy multi-chassis peer mc-endpoint boot-timer

Description

This command configures the boot timer interval. This command applies only when the node reboots. It specifies the time the MC-EP protocol keeps trying to establish a connection before assuming a failure of the remote peer. This is different from the keep-alive mechanism which is used just after the peer-peer communication was established. After this time interval passed all the mc-endpoints configured under services will revert to single chassis behavior, activating the best local PW.

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

Default

no boot-timer

Parameters

interval

Specifies the boot timer interval.

Values

1 to 600

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vpls>site boot-timer)

Full Context

configure service vpls site boot-timer

Description

This command configures for how long the service manager waits after a node reboot before running the DF election algorithm. The boot-timer value should be configured to allow for the BGP sessions to come up and for the NLRI information to be refreshed/exchanged.

The no form of this command reverts the default.

Default

boot-timer 10

Parameters

seconds

Specifies the site boot-timer in seconds.

Values

0 to 100

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>epipe>site boot-timer)

Full Context

configure service epipe site boot-timer

Description

This command configures for how long the service manager waits after a node reboot before running the DF election algorithm. The boot-timer value should be configured to allow for the BGP sessions to come up and for the NLRI information to be refreshed/exchanged.

The no form of this command reverts the default.

Default

boot-timer 10

Parameters

seconds

Specifies the site boot-timer in seconds.

Values

0 to 600

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>pw-routing boot-timer)

Full Context

configure service pw-routing boot-timer

Description

This command configures a hold-off timer for MS-PW routing advertisements and signaling and is used at boot time.

The no form of this command removes a previously configured timer and restores it to its default.

Default

no boot-timer

Parameters

timer-value

Specifies the value of the boot timer in seconds.

Values

0 to 600

Platforms

7705 SAR Gen 2

Context

[Tree] (config>redundancy>bgp-multi-homing boot-timer)

Full Context

configure redundancy bgp-multi-homing boot-timer

Description

This command configures the time the service manager waits after a node reboot before running the DF election algorithm. The boot-timer value should be configured to allow for the BGP sessions to come up and for the NLRI information to be refreshed or exchanged.

The no form of the command reverts the default.

Default

no boot-timer

Parameters

seconds

Specifies the BGP multi-homing boot-timer in seconds.

Values

0 to 600

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>pim>rp bootstrap-export)

Full Context

configure service vprn pim rp bootstrap-export

Description

This command exports policies to control the flow of bootstrap messages from the RP. Up to five policies can be defined.

The no form of this command removes the specified policy names from the configuration.

Parameters

policy-name

Specifies up to five policy names. The policy statement must already be configured in the config>router>policy-options context.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>pim>rp bootstrap-export)

Full Context

configure router pim rp bootstrap-export

Description

This command applies export policies to control the flow of bootstrap messages from the RP, and apply them to the PIM configuration.

The no form of this command removes the policy name from the PIM RP configuration.

Default

no bootstrap-export

Parameters

policy-name

Specifies up to five export policy names, up to 32 characters.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>pim>rp bootstrap-import)

Full Context

configure service vprn pim rp bootstrap-import

Description

This command imports policies to control the flow of bootstrap messages into the RP. Up to five policies can be defined.

The no form of this command removes the specified policy names from the configuration.

Parameters

policy-name

Specifies the policy name. The policy statement must already be configured in the config>router>policy-options context.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>pim>rp bootstrap-import)

Full Context

configure router pim rp bootstrap-import

Description

This command applies import policies to control the flow of bootstrap messages to the RP, and apply them to the PIM configuration.

The no form of this command removes the policy name from the

Default

no bootstrap-import

Parameters

policy-name

Specifies up to five import policy names, up to 32 characters.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>oam-pm>session>meas-interval boundary-type)

Full Context

configure oam-pm session meas-interval boundary-type

Description

This command establishes the alignment of the start of the measurement interval with either the time of day clock or the start of the test. Alignment with the time of day clock always defaults to the representative top of the hour. Clock-aligned 15-minute measurement intervals divide the hour into four equal sections 00, 15, 30, 45. Clock-aligned 1-hour measurement intervals start at 00. Clock-aligned 1-day measurement intervals start at midnight. Test relative start times launches the measurement interval when the individual test enters the active (no shutdown) state. It is typical for the first measurement interval of a clock-aligned test to have the suspect flag set to yes because it is unlikely the no shutdown exactly corresponds to the clock based measurement interval start time. Clock-aligned measurement intervals can include an additional offset.

The no form of this command sets the boundary to the default clock-aligned.

Default

boundary-type clock-aligned

Parameters

clock-aligned

Aligns the start of the measurement interval with the time of day clock.

test-relative

Aligns the start of the measurement interval with the start of the test.

Platforms

7705 SAR Gen 2

Context

[Tree] (debug>service>id>stp bpdu)

Full Context

debug service id stp bpdu

Description

This command enables STP debugging for received and transmitted BPDUs.

Platforms

7705 SAR Gen 2

Context

[Tree] (debug>service>id>stp bpdu)

Full Context

debug service id stp bpdu

Description

This command enables STP debugging for received and transmitted BPDUs.

The no form of the command disables debugging.

Platforms

7705 SAR Gen 2

Context

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

[Tree] (config>service>vpls>sap bpdu-translation)

Full Context

configure service vpls spoke-sdp bpdu-translation

configure service vpls sap bpdu-translation

Description

This command enables the translation of BPDUs to a specified format, meaning that all BPDUs transmitted on a specified SAP or spoke-SDP will have a specified format.

The no form of this command reverts to the default.

Default

no bpdu-translation

Parameters

auto

Specifies that appropriate format will be detected automatically, based on type of BPDUs received on such port.

auto-rw

Specifies that appropriate format will be detected automatically and the VLAN ID will be rewritten as follows:

• BPDU sent on egress of dot1q SAP will contain the VLAN ID of the SAP in BPDU-PVID TLV

• BPDU sent on egress of default QinQ SAP will contain the outer VLAN ID of the SAP in BPDU-PVID TLV

• BPDU sent on egress of QinQ SAP will contain the inner VLAN ID of the SAP in BPDU-PVID TLV

pvst

Specifies the BPDU-format as PVST. Note: the correct VLAN tag is included in the payload (depending on encapsulation value of outgoing SAP).

pvst-rw

Specifies the BPDU-format as PVST. The VLAN ID will be rewritten as follows:

• BPDU sent on egress of dot1q SAP will contain the VLAN ID of the SAP in BPDU-PVID TLV

• BPDU sent on egress of default QinQ SAP will contain the outer VLAN ID of the SAP in BPDU-PVID TLV

• BPDU sent on egress of QinQ SAP will contain the inner VLAN ID of the SAP in BPDU-PVID TLV

stp

Specifies the BPDU-format as STP.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>port>connector breakout)

Full Context

configure port connector breakout

Description

This command configures the transceiver port breakout for use in the connector. Specifying the breakout type triggers the creation of accessible ports for the connector.

When a QSFP28 connector uses an SFP+ optical module with the QSFP28-to-SFP+/SFP28 adapter, the user should set the breakout parameter to c1-10g, which indicates the presence of this adapter.

The options for breakout on specific connectors depend on both the card type and level (or XMA type and level). See the applicable installation guides for more information.

For some connectors (such as QSFPDD), there can be overlap in the breakout for different host interfaces. The same port breakout can be supported on an optical module that uses a host interface of CAUI-4 as another optical module that uses 100GAUI-2. To distinguish from the CAUI-4 host interface, the "-aui2" suffix is used on some breakout options. This is only necessary where there is overlap. In other situations, SR OS sets the host interface correctly without requiring the distinction in the breakout option.

The no form of this command removes the ports under the connector.

Default

no breakout

Parameters

breakout

Specifies the breakout type.

Values

c1-40g, c4-10g, c1-100g, c4-25g, c10-10g, c1-400g, c2-100g, c4-100g, c1-10g, c1-25g, c1-50g, c8-50g, c1-800g, c3-100g, c8-100g, c2-400g, c1-100g-aui2, c2-100g-aui2, c1-400g-aui4, c4-100g-aui1

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>ntp broadcast)

Full Context

configure service vprn ntp broadcast

Description

This command configures the node to transmit NTP packets on a given interface. Broadcast and multicast messages can easily be spoofed, therefore, authentication is strongly recommended.

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

Parameters

ip-int-name

Specifies the local interface on which to transmit NTP broadcast packets. If the string contains special characters (#, ?, space), the entire string must be enclosed between double quotes.

Values

32 character maximum

key-id

Identifies the configured authentication key and authentication type used by this node to receive and transmit NTP packets to and from an NTP server and peers. If an NTP packet is received by this node both authentication key and authentication type must be valid otherwise the packet is rejected and an event/trap generated.

Values

1 to 255

keychain-name

Identifies the keychain name, up to 32 characters.

version

Specifies the NTP version number that is generated by this node. This parameter does not need to be configured when in client mode in which case all versions are accepted.

Values

2 to 4

Default

4

ttl

Specifies the IP Time To Live (TTL) value.

Values

1 to 255

Platforms

7705 SAR Gen 2

Context

[Tree] (config>system>time>ntp broadcast)

Full Context

configure system time ntp broadcast

Description

This command configures the node to transmit NTP packets on a given interface. Broadcast and multicast messages can easily be spoofed, therefore, authentication is strongly recommended.

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

Parameters

router-name

Specifies the router name used to transmit NTP packets. Base is the default. Select management to use the management port (Ethernet port on the CPM). Note that broadcast server capability can also be enabled on an interface within a VPRN context. Refer to "NTP Within a VPRN Service” in the 7705 SAR Gen 2 Layer 3 Services Guide: IES and VPRN for more information.

Values

Base | Management

Default

Base

ip-int-name

Specifies the local interface on which to transmit NTP broadcast packets, up to 32 characters. If the string contains special characters (#, ?, space), the entire string must be enclosed within double quotes.

key-id

Identifies the configured authentication key and authentication type used by this node to receive and transmit NTP packets to and from an NTP server and peers. If an NTP packet is received by this node both authentication key and authentication type must be valid otherwise the packet is rejected and an event or trap generated.

Values

1 to 255

keychain-name

Identifies the keychain name, up to 32 characters.

version

Specifies the NTP version number that is generated by this node. This parameter does not need to be configured when in client mode in which case all versions are accepted.

Values

2 to 4

Default

4

ttl

Specifies the IP Time To Live (TTL) value.

Values

1 to 255

Platforms

7705 SAR Gen 2

Context

[Tree] (config>system>time>sntp broadcast-client)

Full Context

configure system time sntp broadcast-client

Description

This command enables listening to SNTP/NTP broadcast messages on interfaces with broadcast client enabled at global device level.

SNTP must be shutdown prior to changing either to or from broadcast mode.

The no form of the command disables broadcast client mode.

Default

no broadcast-client

Platforms

7705 SAR Gen 2

Context

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

Full Context

configure qos sap-ingress fc broadcast-policer

Description

Within a sap-ingress QoS policy forwarding class context, the broadcast-policer command is used to map packets that match the forwarding class and are considered broadcast in nature to the specified policer-id. The specified policer-id must already exist within the sap-ingress QoS policy. While the system is determining the forwarding class of a packet, it is also looking up its forwarding destination based on the ingress service type and the service instance forwarding records. If the service type is VPLS and the destination MAC address is the broadcast address (ff:ff:ff:ff:ff:ff), the packet is classified into the broadcast forwarding type.

Broadcast forwarding type packets are mapped to either an ingress multipoint queue (using the broadcast queue-id or broadcast queue-id group ingress-queue-group commands) or an ingress policer (broadcast-policer policer-id). The broadcast and broadcast-policer commands within the forwarding class context are mutually exclusive. By default, the broadcast forwarding type is mapped to the SAP ingress default multipoint queue. If the broadcast-policer policer-id command is executed, any previous policer mapping or queue mapping for the broadcast forwarding type within the forwarding class is overridden if the policer mapping is successful.

A policer defined within the sap-ingress policy is not actually created on an ingress SAP or a subscriber using an sla-profile where the policy is applied until at least one forwarding type (unicast, broadcast, unknown, or multicast) from one of the forwarding classes is mapped to the policer. If insufficient policer resources exist to create the policer for a SAP or subscriber or multiservice site, or ingress policing is not supported on the port associated with the SAP or subscriber or multiservice site, the initial forwarding class forwarding type mapping will fail.

The broadcast-policer command is ignored for instances of the policer applied to SAPs or subscribers’ multiservice site where broadcast packets are not supported.

When the broadcast forwarding type within a forwarding class is mapped to a policer, the broadcast packets classified to the subclasses within the forwarding class are also mapped to the policer.

The no form of this command is used to restore the mapping of the broadcast forwarding type within the forwarding class to the default multipoint queue. If all forwarding class forwarding types had been removed from the default multipoint queue, the queue will not exist on the SAPs or subscribers or multiservice site associated with the QoS policy and the no broadcast-policer command will cause the system to attempt to create the default multipoint queue on each object. If the system cannot create the queue on each instance, the no broadcast-policer command will fail and the broadcast forwarding type within the forwarding class will continue its mapping to the existing policer-id. If the no broadcast-policer command results in a policer without any current mappings, the policer will be removed from the SAPs and subscribers associated with the QoS policy. All statistics associated with the policer on each SAP and subscriber will be lost.

Parameters

policer-id

When the forwarding class broadcast-policer command is executed, a valid policer-id must be specified. The parameter policer-id references a policer-id that has already been created within the sap-ingress QoS policy.

Values

1 to 63

fp-redirect-group

Redirects a forwarding class to a forwarding plane queue-group as specified in a SAP QoS policy.

Platforms

7705 SAR Gen 2

Context

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

Full Context

configure qos sap-ingress fc broadcast-queue

Description

This command overrides the default broadcast forwarding type queue mapping for fc fc-name. The specified queue-id must exist within the policy as a multipoint queue before the mapping can be made. When the forwarding class mapping is executed, all broadcast traffic on a SAP using this policy will be forwarded using the queue-id.

The broadcast forwarding type usually tracks the multicast forwarding type definition. This command overrides that default behavior.

The no form of this command sets the broadcast forwarding type queue-id back to the default of tracking the multicast forwarding type queue mapping.

Parameters

queue-id

The queue-id parameter must be an existing, multipoint queue defined in the config>qos>sap-ingress context.

Values

Any valid multipoint queue ID in the policy including 2 through 32.

Default

11

group queue-group-name

This optional parameter is used to redirect the forwarding type within the forwarding class to the specified queue-id within the queue-group-name. When the policy is applied, all packets matching the forwarding class and forwarding type will be redirected to the queue within the specified queue group. The queue-group-name are configured in the config>qos>queue-group-templates egress and ingress contexts.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>system>time>ntp broadcastclient)

Full Context

configure system time ntp broadcastclient

Description

When configuring NTP, the node can be configured to receive broadcast packets on a specified subnet. This command configures a specific interface to listen for broadcast NTP messages. The interface may exist within a VPRN service.

Broadcast and multicast messages can easily be spoofed, so authentication is strongly recommended. If broadcast is not configured, then any received NTP broadcast traffic will be ignored. Use the show command to view the state of the configuration.

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

Parameters

router-instance

Specifies the routing context that contains the interface in the form of router-name or service-id.

Values

router-name — Base | Management

service-id — 1 to 2147483647

Default

Base

service name

Specifies the service name for the VPRN. The name can be up to 64 characters in length. Note that CPM routing instances are not supported.

ip-int-name

Specifies the VPRN interface on which to receive NTP broadcast packets. If the string contains special characters (such as #, $, or spaces) the entire string must be enclosed within double quotes.

authenticate

Specifies whether or not to require authentication of NTP PDUs. When enabled, NTP PDUs are authenticated upon receipt.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>pim>if bsm-check-rtr-alert)

Full Context

configure service vprn pim interface bsm-check-rtr-alert

Description

This command enables the checking of router alert option in the bootstrap messages received on this interface.

Default

no bsm-check-rtr-alert

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>pim>interface bsm-check-rtr-alert)

Full Context

configure router pim interface bsm-check-rtr-alert

Description

This command enables the checking of the router alert option in the bootstrap messages received on this interface.

The no form of this command disables accepting BSM packets without the router alert option.

Default

no bsm-check-rtr-alert

Platforms

7705 SAR Gen 2

Context

[Tree] (debug>router>pim bsr)

Full Context

debug router pim bsr

Description

This command enables/disables debugging for the PIM bootstrap mechanism.

The no form of the command disables debugging.

Parameters

detail

Debugs detailed information on the PIM bootstrap mechanism.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>pim>rp>ipv6 bsr-candidate)

[Tree] (config>service>vprn>pim>rp bsr-candidate)

Full Context

configure service vprn pim rp ipv6 bsr-candidate

configure service vprn pim rp bsr-candidate

Description

Commands in this context configure Candidate Bootstrap (BSR) parameters.

Either bsr-candidate for IPv4 or auto-rp-discovery can be configured; the two mechanisms cannot be enabled together. bsr-candidate for IPv6 and auto-rp-discovery for IPv4 can be enabled together.

The no form of this command disables BSR.

Default

no bsr-candidate

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>pim>rp>ipv6 bsr-candidate)

[Tree] (config>router>pim>rp bsr-candidate)

Full Context

configure router pim rp ipv6 bsr-candidate

configure router pim rp bsr-candidate

Description

Commands in this context configure Candidate Bootstrap (BSR) parameters.

Either bsr-candidate for IPv4 or auto-rp-discovery can be configured; the two mechanisms cannot be enabled together. bsr-candidate for IPv6 and auto-rp-discovery for IPv4 can be enabled together.

Default

bsr-candidate shutdown

Platforms

7705 SAR Gen 2

Context

[Tree] (config>system>ip buffer-unresolved-packets)

Full Context

configure system ip buffer-unresolved-packets

Description

This command configures the buffering of unresolved IPv4 and IPv6 packets waiting for an address resolution process (ARP) or neighbor discovery (ND) reply.

The no form of this command configures the system to discard IPv4 and IPv6 traffic needing a destination resolution that is buffered while waiting for a response to avoid any potential of out-of-order delivery of packets to the resolved destination. As a result, after the ARP or ND entry is populated, the system delivers only newly received packets in order.

Default

buffer-unresolved-packets

Platforms

7705 SAR Gen 2

Context

[Tree] (debug>router>rsvp>packet bundle)

Full Context

debug router rsvp packet bundle

Description

This command debugs bundle events.

The no form of the command disables the debugging.

Parameters

detail

Displays detailed information about bundle events.

Platforms

7705 SAR Gen 2

Context

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

Full Context

configure service vprn interface sap egress queue-override queue burst-limit

Description

The queue burst-limit command defines an explicit shaping burst size for a queue. The configured size defines the shaping leaky bucket threshold level that indicates the maximum burst over the queue shaping rate.

The no form of this command restores the default burst limit to the specified queue. This is equivalent to specifying burst-limit default within the QoS policies. When specified within a queue-override queue context, any current burst limit override for the queue is removed and the queue burst limit is controlled by its defining policy.

Default

no burst-limit

Parameters

default

Reverts the queues burst limit to the system default value.

size

When a numeric value is specified (size), the system interprets the value as an explicit burst limit size. The value is expressed as an integer and, by default, is interpreted as the burst limit in kilobytes. If the value is intended to be interpreted in bytes, the bytes qualifier must be added following size.

Values

0 to 13671 kilobytes

0 to 14000000 bytes

Default

No default for size; use the default keyword to specify default burst limit.

bytes

Specifies that the value given for size must be interpreted as the burst limit in bytes.

kilobytes

Specifies that the value given for size must be interpreted as the burst limit in kilobytes. If neither bytes, nor kilobytes is specified, the default qualifier is kilobytes.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>port>ethernet>access>egr>qgrp>qover>q burst-limit)

Full Context

configure port ethernet access egress queue-group queue-overrides queue burst-limit

Description

The queue burst-limit command overrides the shaping burst size for a queue. The configured size defines the shaping leaky bucket threshold level that indicates the maximum burst over the queue’s shaping rate.

The no form of this command removes the current burst limit override for the queue. The queue’s burst limit is controlled by its defining template.

Default

no burst-limit

Parameters

default

Reverts the queue's burst limit to the system default value.

size

When a numeric value is specified (size), the system interprets the value as an explicit burst limit size. The value is expressed as an integer and, by default, is interpreted as the burst limit in kilobytes. If the value is intended to be interpreted in bytes, the bytes qualifier must be added following size.

Values

1 to 13671 kilobytes

1 to 14000000 bytes

Default

No default for size; use the default keyword to specify default burst limit.

bytes

Specifies that the value given for size must be interpreted as the burst limit in bytes.

kilobytes

Specifies that the value given for size must be interpreted as the burst limit in kilobytes. If neither bytes nor kilobytes is specified, the default qualifier is kilobytes.

Platforms

7705 SAR Gen 2

Context

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

Full Context

configure service epipe sap egress queue-override queue burst-limit

Description

The queue burst-limit command defines an explicit shaping burst size for a queue. The configured size defines the shaping leaky bucket threshold level that indicates the maximum burst over the queue’s shaping rate.

The no form of this command restores the default burst limit to the specified queue. This is equivalent to specifying burst-limit default within the QoS policies. When specified within a queue-override queue context, any current burst limit override for the queue is removed and the queue’s burst limit is controlled by its defining policy.

Default

no burst-limit

Parameters

default

Reverts the queue's burst limit to the system default value.

size

When a numeric value is specified (size), the system interprets the value as an explicit burst limit size. The value is expressed as an integer and, by default, is interpreted as the burst limit in kilobytes. If the value is intended to be interpreted in bytes, the bytes qualifier must be added following size.

Values

1 to 13671 kilobytes

14000000 bytes

Default

No default for size; use the default keyword to specify default burst limit.

bytes

Specifies that the value given for size must be interpreted as the burst limit in bytes.

kilobytes

Specifies that the value given for size must be interpreted as the burst limit in kilobytes. If neither bytes nor kilobytes is specified, the default qualifier is kilobytes.

Platforms

7705 SAR Gen 2

Context

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

Full Context

configure service vpls sap egress queue-override queue burst-limit

Description

The queue burst-limit command defines an explicit shaping burst size for a queue. The configured size defines the shaping leaky bucket threshold level that indicates the maximum burst over the queue's shaping rate. The no form of this command restores the default burst limit to the specified queue. This is equivalent to specifying burst-limit default within the QoS policies. When specified within a queue-override queue context, any current burst limit override for the queue is removed and the queue's burst limit is controlled by its defining policy.

Default

no burst-limit

Parameters

default

Reverts the queue's burst limit to the system default value.

size

When a numeric value is specified (size), the system interprets the value as an explicit burst limit size. The value is expressed as an integer and by default is interpreted as the burst limit in kilobytes. If the value is intended to be interpreted in bytes, the bytes qualifier must be added following size.

Values

1 to 13671 kilobytes

1 to 14000000 bytes

Default

No default for size; use the default keyword to specify default burst limit.

bytes

Specifies that the value given for size must be interpreted as the burst limit in bytes.

kilobytes

Specifies that the value given for size must be interpreted as the burst limit in kilobytes. If neither bytes nor kilobytes is specified, the default qualifier is kilobytes.

Platforms

7705 SAR Gen 2

Context

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

Full Context

configure service ies interface sap egress queue-override queue burst-limit

Description

The queue burst-limit command defines an explicit shaping burst size for a queue. The configured size defines the shaping leaky bucket threshold level that indicates the maximum burst over the queues shaping rate.

The no form of this command restores the default burst limit to the specified queue. This is equivalent to specifying burst-limit default within the QoS policies. When specified within a queue-override queue context, any current burst limit override for the queue is removed and the queue's burst limit is controlled by its defining policy.

Default

no burst-limit

Parameters

default

Reverts the queues burst limit to the system default value.

size

When a numeric value is specified (size), the system interprets the value as an explicit burst limit size. The value is expressed as an integer and, by default, is interpreted as the burst limit in kilobytes. If the value is intended to be interpreted in bytes, the bytes qualifier must be added following size.

Values

0 to 13671 kilobytes

0 to or 14000000 bytes

Default

No default for size; use the default keyword to specify default burst limit.

bytes

Specifies that the value given for size must be interpreted as the burst limit in bytes.

kilobytes

Specifies that the value given for size must be interpreted as the burst limit in kilobytes. If neither bytes, nor kilobytes is specified, the default qualifier is kilobytes.

Platforms

7705 SAR Gen 2

Context

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

Full Context

configure qos sap-ingress queue burst-limit

Description

The queue burst-limit command is used to define an explicit shaping burst size for a queue. The configured size defines the shaping leaky bucket threshold level that indicates the maximum burst over the queue’s shaping rate.

The burst-limit command is supported under the sap-ingress and sap-egress QoS policy queues. The command is also supported under the ingress and egress queue-group-templates queues.

The no form of this command is used to restore the default burst limit to the specified queue. This is equivalent to specifying burst-limit default within the QoS policies or queue group templates. When specified within a queue-override queue context, any current burst limit override for the queue will be removed and the queue’s burst limit will be controlled by its defining policy or template.

Default

no burst-limit

Parameters

size

Specifies an explicit burst limit size. The value is expressed as an integer and, by default, is interpreted as the burst limit in kilobytes. If the value is intended to be interpreted in bytes, the byte qualifier must be added following size.

Values

1 to 13,671 kbytes or 14,000,000 bytes

Default

No default for size; use the default keyword to specify default burst limit.

bytes

Specifies that the value given for size must be interpreted as the burst limit in bytes.

kilobytes

Specifies that the value given for size must be interpreted as the burst limit in kilobytes. If neither bytes nor kilobytes is specified, the default qualifier is kilobytes.

Platforms

7705 SAR Gen 2

Context

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

Full Context

configure qos sap-egress queue burst-limit

Description

The queue burst-limit command configures an explicit shaping burst size for a queue. The configured size defines the shaping leaky bucket threshold level that indicates the maximum burst over the queue’s shaping rate.

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

The no form of this command restores the default burst limit to the specified queue. This is equivalent to specifying burst-limit default within the QoS policies or queue group templates.

Default

no burst-limit

Parameters

default

Reverts the burst limit of the queue to the system default value.

size

Specifies an explicit burst limit size. The value is expressed as an integer and, by default, is interpreted as the burst limit in kilobytes. If the value is intended to be interpreted in bytes, the bytes keyword must be added following size.

Values

1 to 13671 kilobytes

1 to 14,000,000 bytes

bytes

Specifies that the configured size value must be interpreted as the burst limit in bytes.

kilobytes

Specifies that the configure size value must be interpreted as the burst limit in kilobytes. If neither bytes nor kilobytes is specified, the default qualifier is kilobytes.

microseconds

Specifies the burst limit as a function of delay time.

Values

0 to 1000000

Platforms

7705 SAR Gen 2

Context

[Tree] (config>qos>qgrps>egr>qgrp>queue burst-limit)

[Tree] (config>qos>qgrps>ing>qgrp>queue burst-limit)

Full Context

configure qos queue-group-templates egress queue-group queue burst-limit

configure qos queue-group-templates ingress queue-group queue burst-limit

Description

The queue burst-limit command is used to define an explicit shaping burst size for a queue. The configured size defines the shaping leaky bucket threshold level that indicates the maximum burst over the queue’s shaping rate.

The burst-limit command is supported under the sap-ingress and sap-egress QoS policy queues. The command is also supported under the ingress and egress queue-group-templates queues.

The no form of this command is used to restore the default burst limit to the specified queue. This is equivalent to specifying burst-limit default within the QoS policies or queue group templates. When specified within a queue-override queue context, any current burst limit override for the queue will be removed and the queue’s burst limit will be controlled by its defining policy or template.

Parameters

size

When a numeric value is specified (size), the system interprets the value as an explicit burst limit size. The value is expressed as an integer and by default is interpreted as the burst limit in kilobytes. If the value is intended to be interpreted in bytes, the byte qualifier must be added following size.

Values

1 to 14,000 (14,000 or 14,000,000 depending on bytes or kilobytes)

bytes

Specifies that the value given for size must be interpreted as the burst limit in bytes.

kilobytes

Specifies that the value given for size must be interpreted as the burst limit in kilobytes.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>mpls bypass-resignal-timer)

Full Context

configure router mpls bypass-resignal-timer

Description

This command triggers the periodic global re-optimization of all dynamic bypass LSP paths associated with RSVP P2P LSP. The operation is performed at each expiry of the user configurable bypass LSP resignal timer.

When this command is enabled, MPLS requests CSPF for the best path for each dynamic bypass LSP originated on this node. The constraints, hop-limit, SRLG and admin-group constraints, of the first associated LSP primary path that originally triggered the signaling of the bypass LSP must be satisfied. To do this, MPLS saves this initial Path State Block (PSB) of that LSP primary path, even if the latter is torn down.

CSPF first updates the SRLG membership of the current bypass LSP path and checks if the path violates the SRLG constraint of the initial PSB. It then attempts a new path computation for the bypass LSP using the initial PSB constraints. If CSPF returns no path or returns a new path with a cost that is lower than the current path, MPLS does not signal the new bypass path. If CSPF returns a new path with a cost that is lower than the current one, MPLS signals it. Also, if the new bypass path is SRLG strict disjoint with the primary path of the original PSB while the current path is SRLG loose disjoint, the manual bypass path is resignaled regardless of cost comparison.

Once the new path is successfully signaled, MPLS evaluates each PSB of each PLR (that is, each unique avoid-node or avoid-link constraint) associated with the current bypass LSP path to check if the corresponding LSP primary path constraints are still satisfied by the new bypass LSP path. If so, the PSB association is moved to the new bypass LSP.

Each PSB for which the constraints are not satisfied remains associated with the PLR on the current bypass LSP and is checked at the next timer or manual bypass re-optimization. Additionally, if SRLG FRR loose disjointness is configured using the configure router mpls srlg-frr command and the current bypass LSP is SRLG disjoint with a primary path while the new bypass LSP is not SRLG disjoint, the PSB association is not moved. When CSPF does not return a new bypass path or it returns a less optimal one, the PSBs remain associated with the current bypass path. However, it is possible that CSPF found the current bypass LSP path no longer satisfies the SRLG constraint of one or more PLRs after the update of the current path SRLG information. In that case, MPLS detaches from current bypass path the PSB associations of these PLRs. These orphaned PSBs are re-evaluated by the FRR background task which checks unprotected PSBs on a regular basis and following the same above procedure.

If a specific PLR associated with a bypass LSP is active, the corresponding PSBs remain associated with the current PLR until the Global Revertive Make-Before-Break (MBB) tears down all corresponding primary paths, which also causes the current PLR to be removed.

This feature is not supported with inter-area dynamic bypass LSP and bypass LSP protecting S2L paths of a P2MP LSP.

The no form of this command disables the periodic global re-optimization of dynamic bypass LSP paths.

Default

no bypass-resignal timer.

Parameters

minutes

Specifies the time, in minutes, MPLS waits before attempting to resignal dynamic bypass LSP paths originated on the system.

Values

1 to 10080

Platforms

7705 SAR Gen 2