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

All

Context

[Tree] (config>service>vpls>pbb backbone-vpls)

Full Context

configure service vpls pbb backbone-vpls

Description

This command configures B-VPLS service associated with the I-VPLS.

Parameters

service-id

Specifies the service ID.

Values

1 to 2147483648

isid

Specifies the ISID.

Values

0 to 16777215

Platforms

All

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

All

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

All

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

All

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

All

Context

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

Full Context

configure isa application-assurance-group backup

Description

This command assigns an AA ISA or ESA-VM configured in the specified location to this application assurance group. The backup module provides the application assurance group with warm redundancy when the primary module in the group is configured. Primary and backup modules have equal operational status and when both module are coming up, the ones that becomes operational first becomes the active module. A module can serve as a backup for multiple AA ISA cards but only one can fail to it at one time.

On an activity switch from the primary module, configurations are already on the backup MDA but flow state information must be re-learned. Any statistics not yet spooled will be lost. Auto-switching from the backup to primary, once the primary becomes available again, is not supported.

Operator is notified through SNMP events when:

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

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

• When an AA activity switch occurred.

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

Parameters

mda-id

Specifies the slot and MDA, identifying a provisioned module to use as a backup module.

Values

slot/mda
slot	1 to 10, depending on chassis model
mda	1 to 2

esa-vm-id

Specifies the ESA and VM, identifying a provisioned module to use as a backup module; for example, an ESA 1 with VM2 would be referred to as esa-1/2.

Values

esa-esa-id/vm-id
esa-id	1 to 16
vm-id	1 to 4

Platforms

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

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 will be lost. Auto-switching from the backup to primary, once the primary becomes available again, is supported.

The operator 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

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

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

All

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 (RFC4861). 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

All

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

All

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

All

Context

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

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

Full Context

configure service vprn static-route-entry next-hop backup-next-hop

configure router static-route-entry next-hop backup-next-hop

Description

Commands in this context configure static route entry fast failover.

Platforms

All

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

All

Context

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

Full Context

configure service vprn bgp backup-path

Description

This command enables the computation and use of a backup path for IPv4 and/or IPv6 BGP-learned prefixes belonging to the base router or a particular VPRN. Multiple paths must be received for a prefix to take advantage of this feature. When a prefix has a backup path and its primary paths fail, the affected traffic is rapidly diverted to the backup path without waiting for control plane reconvergence to occur. When many prefixes share the same primary paths, and in some cases also the same backup path, the time to failover traffic to the backup path is independent of the number of prefixes.

By default, IPv4 and IPv6 prefixes do not have a backup path installed in the IOM.

Default

no backup-path

Parameters

ipv4

Keyword that enables the use of a backup path for BGP-learned unlabeled IPv4 prefixes.

ipv6

Keyword that enables the use of a backup path for BGP-learned unlabeled IPv6 prefixes.

label-ipv4

Keyword that enables the use of a backup path for BGP-learned labeled-IPv4 prefixes.

label-ipv6

Keyword that enables support for labeled-unicast IPv6 routes.

Platforms

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

Context

[Tree] (config>router>bgp backup-path)

Full Context

configure router bgp backup-path

Description

This command enables the computation and use of a backup path for IPv4 and/or IPv6 BGP-learned prefixes belonging to the base router. Multiple paths must be received for a prefix to take advantage of this feature. When a prefix has a backup path and its primary paths fail, the affected traffic is rapidly diverted to the backup path without waiting for control plane reconvergence to occur. When many prefixes share the same primary paths, and in some cases also the same backup path, the time to failover traffic to the backup path is independent of the number of prefixes.

By default, IPv4 and IPv6 prefixes do not have a backup path installed in the IOM.

Default

no backup-path

Parameters

ipv4

Keyword that enables BGP fast reroute for unlabeled unicast IPv4 routes.

ipv6

Keyword that enables BGP fast reroute for unlabeled unicast IPv6 routes.

label-ipv4

Keyword that enables BGP fast reroute for labeled-unicast IPv4 routes.

label-ipv6

Keyword that enables BGP fast reroute for labeled-unicast IPv6 routes.

Platforms

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

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

All

Context

[Tree] (config>service>vprn>static-route-entry backup-tag)

[Tree] (config>router>static-route-entry backup-tag)

Full Context

configure service vprn static-route-entry backup-tag

configure router static-route-entry backup-tag

Description

This command associates a 4-byte backup route tag with the static route when the backup-next-hop command is activated. The tag value is an identifier that can be used in route policies to control distribution of the static route into other protocols when the backup-next-hop is activated for the associated static route.

The tag specified at this level of the static route causes the tag values that are configured under the next-hop, black-hole, and indirect contexts of the static route to be ignored.

The no form of this command removes the tag association.

Default

no backup-tag

Parameters

tag-id

Specifies an integer tag value.

Values

1 to 4294967295

Platforms

All

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

All

Context

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

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

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

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

Full Context

configure service epipe sap bandwidth

configure service fpipe sap bandwidth

configure service apipe sap bandwidth

configure service ipipe 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

All

• configure service ipipe sap bandwidth
• configure service epipe sap bandwidth

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

• configure service fpipe sap bandwidth

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

• configure service apipe sap bandwidth

Context

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

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

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

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

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

Full Context

configure service ipipe spoke-sdp bandwidth

configure service apipe spoke-sdp bandwidth

configure service epipe spoke-sdp bandwidth

configure service fpipe spoke-sdp bandwidth

configure service cpipe 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-series 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

All

• configure service epipe spoke-sdp bandwidth
• configure service ipipe spoke-sdp bandwidth

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

• configure service apipe spoke-sdp bandwidth

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

• configure service fpipe spoke-sdp bandwidth
• configure service cpipe spoke-sdp bandwidth

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

All

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

All

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

All

Context

[Tree] (config>router>gmpls>lsp>protect-path bandwidth)

[Tree] (config>router>gmpls>lsp>working-path bandwidth)

Full Context

configure router gmpls lsp protect-path bandwidth

configure router gmpls lsp working-path bandwidth

Description

This command specifies the bandwidth to be signaled for the path of the GMPLS LSP. Bandwidth is specified in terms of the RFC 3471 signal type name.

If an empty path is configured or the first hop TE Link is not configured, the system will automatically select a TE Link to use for a GMPLS LSP path based on the lowest available TE Link ID with a matching bandwidth (if a bandwidth is configured for the GMPLS LSP). During a data-bearer link allocation request, an RSVP-requested GMPLS LSP BW can be either a non-zero value as per RFC 3471 signal-type, or it can be zero). There are the following cases:

• Case 1 — The requested BW is non-zero as per RFC 3471 Signal-type config:

  a) When a TE (or TE/DB) Link is configured in the related hop, LMP checks whether the related port BW is the same (exact match) as the requested BW, and allocates the port (provided any other checks are OK).

  b) When the related Hop is empty: LMP finds a db-link port to the peer node matching the requested BW, and allocates it.

• Case 2 — Requested BW is zero:

  a) When a TE (or TE/DB) Link is configured in the related hop, LMP allocates the port (provided the other checks are OK), and provides the port BW to RSVP to use in signaling.

  b) When the related Hop is empty, LMP finds the first available db-link to the peer (based on lower db-link Id), and allocates it and provides the port BW to RSVP to use in signaling.

The no form of the command updates the bandwidth to zero.

Default

no bandwidth

Parameters

signal-type

Specifies the RFC 3471 name of the signal type representing the requested bandwidth for the GMPLS LSP path.

Values

{ds0 | ds1 | e1 | ds2 | e2 | ethernet | e3 | ds3 | sts-1 | fast-ethernet | e4 | fc-0-133m | oc-3/stm1 | fc-0-266m | fc-0-531m | oc-12/stm-4 | gige | fc-0-1062m | oc-48/stm-16 | oc-192/stm-64 | 10gige-ieee | oc-768/stm-256 | 100gige-ieee}

Platforms

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

Context

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

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

Full Context

configure router mpls lsp primary-p2mp-instance bandwidth

configure router mpls lsp-template bandwidth

Description

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

The config>router>mpls>lsp>primary-p2mp-instance> bandwidth command is not supported on the 7450 ESS.

Parameters

bandwidth-in-mbps

Specifies the bandwidth, in Mb/s.

Values

0 to 6400000

Platforms

All

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

All

Context

[Tree] (config>isa>video-group>watermark bandwidth)

Full Context

configure isa video-group watermark bandwidth

Description

Commands in this context configure watermark parameters based on the bandwidth.

Platforms

7450 ESS, 7750 SR-1, 7750 SR-7/12/12e, 7750 SR-1s, 7750 SR-2s, 7750 SR-7s, 7750 SR-14s

Context

[Tree] (config>router>mcac>policy>bundle bandwidth)

Full Context

configure router mcac policy bundle bandwidth

Description

This command configures the MCAC policy bundle maximum bandwidth.

Parameters

bandwidth-in-kbps

Specifies the MCAC policy bandwidth.

Values

1 to 4294967295

Platforms

All

Context

[Tree] (config>card>mda>xcon>mac>lpbk bandwidth)

[Tree] (config>card>xiom>mda>xcon>mac>lpbk bandwidth)

Full Context

configure card mda xconnect mac loopback bandwidth

configure card xiom mda xconnect mac loopback bandwidth

Description

This command defines the bandwidth for a maximum Layer 2 rate for the MAC loopback. This is equivalent to a faceplate port rate with the difference that the bandwidth of a faceplate port is a Layer 1 rate, which on Ethernet- based ports includes 20B per frame (preamble and inter-packet gap).

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

Default

bandwidth 100

Parameters

gbps

Specifes the bandwidth in Gb/s.

Values

10, 25, 40, 100, 400

Platforms

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

• configure card mda xconnect mac loopback bandwidth

7750 SR-1s, 7750 SR-2s, 7750 SR-7s, 7750 SR-14s

• configure card xiom mda xconnect mac loopback bandwidth

Context

[Tree] (config>qos>adv-config-policy>child-control bandwidth-distribution)

Full Context

configure qos adv-config-policy child-control bandwidth-distribution

Description

This command modifies or controls the bandwidth distribution phase of the parent virtual scheduler.

This command edits the parameters that control the child given bandwidth for all policers and queues associated with the policy.

Platforms

All

Context

[Tree] (config>app-assure>group>policy>aqp>entry>action bandwidth-policer)

Full Context

configure application-assurance group policy app-qos-policy entry action bandwidth-policer

Description

This command assigns an existing bandwidth policer as an action on flows matching this AQP entry. The match criteria for the AQP entry must specify a uni-directional traffic direction before a policer action can be configured. If a policer is used in one direction in an AQP match entry the same policer name cannot be used by another AQP entry which uses a different traffic direction match criteria.

When multiple policers apply to a single flow, the final action on a packet is the worst case of all policer outcomes (for example, if one of the policers marks packet out of profile, the final marking will reflect that).

The no form of this command removes bandwidth policer from actions on flows matching this AQP entry.

Default

no bandwidth-policer

Parameters

policer-name

Specifies the name of the existing flow setup rate policer for this application assurance profile. The policer-name is configured in the config>app-assure>group>policer context.

Platforms

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

Context

[Tree] (config>mcast-mgmt bandwidth-policy)

Full Context

configure mcast-management bandwidth-policy

Description

This command creates a multicast bandwidth policy. Bandwidth policies are used to manage the ingress multicast path bandwidth. Each forwarding plane supports multicast forwarding paths into the switch fabric. By default, two paths are available; the multicast high priority path and the multicast low priority path. Multicast packets are forwarded on either path based on the expedited or non-expedited (best-effort) nature of the queue the packets are scheduled from. The ingress forwarding plane uses the classification rules to determine the forwarding class of each multicast packet and uses the forwarding class to queue mapping to decide which ingress multipoint queue forwards the packet.

When multicast path management is enabled, the ingress forwarding plane allows IP multicast snooped or routed packets to be placed on to the two multicast paths independently of the ingress classification rules. The high priority multicast path is treated as the primary path and the low priority multicast path is treated as the secondary path. The ingress bandwidth manager evaluates each multicast FIB (M-FIB) record to determine which path is best based on ingress bandwidth, number of switch fabric destinations and the fill level of each path. Explicit path association is also supported.

Dynamic Bandwidth Activity Monitoring

When ingress multicast path management is enabled on an MDA, the system monitors the in-use bandwidth associated with each Layer 2 and Layer 3 ingress multicast record. When records are first populated by static, snooping or routing protocols, they are first assumed to be inactive. An inactive record is not considered to be currently consuming ingress multicast path bandwidth.

Within the multicast-info-policy, the bandwidth activity of the new record was configured to be either managed based on an administrative bandwidth, or based on the dynamic bandwidth rate table. The bandwidth-policy associated with ingress MDA contains the configuration parameters for creating the dynamic bandwidth rate table. The purpose of the table is to allow for the system to monitor the bandwidth activity associated with a multicast record and compare the current rate against several rate thresholds. Rate thresholds are used to allow a multicast streams rate to fluctuate between a given range while keeping the managed rate at a certain level. Multiple dynamic managed rates are supported in the table to allow monitoring of different types of multicast traffic. Each rate threshold is associated with a rising and falling threshold that defines when the specified rate should be used and when the next lower rate should be used.

Once a record’s monitored current rate rises to the first dynamic rising threshold, the record is active and the system then manages the bandwidth the record represents based on the parameters associated with the record in the records multicast-info-policy and the configured path information in the MDAs associated bandwidth-policy.

Ingress Multicast Path Parameters

The bandwidth-policy also contains the configuration parameters for each of the managed ingress multicast paths. The queue default parameters can be overridden for each primary and secondary path. In addition, the number of secondary paths (and by implication the number of primary paths) can be overridden.

Default Bandwidth Policy

A bandwidth policy with the name ‛default’ always exists and is used as the default bandwidth policy when ingress multicast path management is enabled without an explicit bandwidth policy defined on an FP. The default policy cannot be deleted or edited.

The no form of this command removes the specified bandwidth policy from the system. The bandwidth policy associations must be removed from MDA configurations before it can be removed.

Default

bandwidth-policy ‟default”

Parameters

policy-name

Specifies the name of the bandwidth policy, up to 32 characters. Each bandwidth policy must be uniquely named within the system. 32 policies can be configured per system.

create

This keyword is required if creating a new bandwidth policy when the system is configured to require the explicit use of the keyword to prevent accidental object creation. Objects may be accidentally created when this protection is disabled and an object name is mistyped when attempting to edit the object. This keyword is not required when the protection is disabled. The keyword is ignored when the bandwidth policy name already exists.

Platforms

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

Context

[Tree] (config>card>fp>ingress>mcast-path-management bandwidth-policy)

Full Context

configure card fp ingress mcast-path-management bandwidth-policy

Description

This command explicitly associates a bandwidth policy to a forwarding plane. The bandwidth policy defines the dynamic rate table and the multicast paths bandwidth and queuing parameters.

If a bandwidth policy is not explicitly associated with a forwarding plane, the default bandwidth policy is used when ingress multicast path management is enabled.

The no form of this command removes an explicit bandwidth policy from a forwarding plane or MDA and restores the default bandwidth policy.

Parameters

policy-name

The policy-name parameter is required and defines the bandwidth policy that should be associated with the MDA or forwarding plane for ingress multicast path management. If the policy name does not exist, the bandwidth-policy command will fail. The name can be up to 32 characters long.

Values

Any existing bandwidth policy name.

Default

default

Platforms

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

Context

[Tree] (config>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

All

Context

[Tree] (config>system>management-interface>yang-modules base-r13-modules)

Full Context

configure system management-interface yang-modules base-r13-modules

Description

This command enables the support of the Base-R13 YANG modules in the SR OS NETCONF server.

When the configure system management-interface configuration-mode command is set to model-driven, the configuration cannot be modified using Base-R13 modules in NETCONF, even if this command is configured.

The no form of this command disables Base-R13 YANG modules, and any NETCONF request that references the Base-R13 modules results in an error.

Default

no base-r13-modules

Platforms

All

Context

[Tree] (config>router>segment-routing>srv6 base-routing-instance)

Full Context

configure router segment-routing segment-routing-v6 base-routing-instance

Description

Commands in this context configure the function value for End SID, End.X SID, and service SID of an IPv4 or an IPv6 prefix in the global routing instance.

Platforms

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

Context

[Tree] (config>aaa>route-downloader base-user-name)

Full Context

configure aaa route-downloader base-user-name

Description

This command sets the prefix for the user name that shall be used as access requests. The actual name used is a concatenation of this string, the ‟-” (dash) character and a monotonically increasing integer.

The no form of this command removes the user-name from the configuration.

Default

The system’s configured name (system name).

Parameters

user-name

Specifies the prefix of the username that is used in the RADIUS access requests. The username used in the RADIUS access requests is a concatenation of this string, the dash character and an increasing integer.

Platforms

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

Context

[Tree] (config>subscr-mgmt>wlan-gw>ue-query bd)

Full Context

configure subscriber-mgmt wlan-gw ue-query bd

Description

This command enables matching on UEs that are part of the specified BD.

The no form of this command disables matching on the BD.

Default

no bd

Parameters

identifier

Specifies the BD identifier.

Values

0 to 4294967294

Platforms

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

Context

[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw>ranges>range>vrgw>lanext bd-mac-prefix)

[Tree] (config>service>ies>sub-if>grp-if>wlan-gw>ranges>range>vrgw>lanext bd-mac-prefix)

Full Context

configure service vprn subscriber-interface group-interface wlan-gw vlan-tag-ranges range vrgw lanext bd-mac-prefix

configure service ies subscriber-interface group-interface wlan-gw vlan-tag-ranges range vrgw lanext bd-mac-prefix

Description

This command specifies the prefix of the HLE BD MAC address.

The no form of this command removes the MAC prefix from the configuration.

Platforms

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

Context

[Tree] (config>subscr-mgmt>acct-plcy>include-radius-attribute bearer-fteid)

Full Context

configure subscriber-mgmt radius-accounting-policy include-radius-attribute bearer-fteid

Description

This command, in the case of ESM over GTP access includes the Alc-Bearer-Fteid VSA in accounting. This VSA contains the fully qualified TEID of the current GTP-U tunnel, including the bearer ID, endpoint IP addresses and TEIDs for both local and remote endpoints.

The no version of this command disables inclusion of the Alc-Bearer-Fteid VSA.

Default

no bearer-fteid

Platforms

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

Context

[Tree] (config>app-assure>group>policy begin)

Full Context

configure application-assurance group policy begin

Description

This command begins a policy editing session.

The editing session continues until one of the following conditions takes place:

• Abort or commit is issued.

• Control complex resets.

The editing session is not interrupted by:

• HA activity switch.

• CLI session termination (for example, as result of closing a Telnet session).

Platforms

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

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

All

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

All

Context

[Tree] (config>system>sync-if-timing begin)

Full Context

configure system sync-if-timing begin

Description

This command is required in order to enter the mode to create or edit the system synchronous interface timing configuration.

Platforms

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

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

All

Context

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

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

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

Full Context

configure system security keychain direction bi entry begin-time

configure system security keychain direction uni receive entry begin-time

configure system security keychain direction uni send 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

All

Context

[Tree] (config>port>tdm>e1>channel-group>ppp ber-sf-link-down)

[Tree] (config>port>tdm>ds1>channel-group>ppp ber-sf-link-down)

Full Context

configure port tdm e1 channel-group ppp ber-sf-link-down

configure port tdm ds1 channel-group ppp ber-sf-link-down

Description

This command enables the port down on BER-SF alarm. When enabled, the link will be placed out of service once ber-sf is detected.

The no form of this command reverts to normal operation where the link remains in-service when ber-sf is encountered.

Default

no ber-sf-link-down

Platforms

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

Context

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

[Tree] (config>port>tdm>e1 bert)

[Tree] (config>port>tdm>ds1 bert)

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

Full Context

configure port tdm e3 bert

configure port tdm e1 bert

configure port tdm ds1 bert

configure port tdm ds3 bert

Description

This command initiates or restarts a Bit Error Rate Test (BERT) on the associated DS-1/E-1 or DS-3/E-3 circuit.

The associated DS-1, E-1, DS-3, or E-3 must be in a shutdown (admin down) state to initiate this test.

The no form of this command terminates the BERT test if it has not yet completed.

Notes:

• This command is not saved in the router configuration between boots.

• The 4-port OC-3/STM-1 and the 1-port OC-12/STM-4 ASAP MDA supports up to 28 concurrent BERT tests per MDA. The 4-port and 12-port DS-3/E-3 ASAP MDAs support a single BERT test per MDA. An attempt to configure more BERT tests can result in an error indicating an operation failure due to resource exhaustion.

• If the ASAP MDA BERT error insertion rate command is executed when tests are running, it will not take effect until test is restarted.

Default

bert 2e3

Parameters

duration

Sets the duration for the BERT test.

Values

Up to 24 hours, in seconds or hh:mm:ss format

ones

Sends an all ones pattern.

zeros

Sends an all zeros pattern.

alternating

Sends an alternating ones and zeros pattern.

2e3

Sends a pseudo-random 2^3 -1 pattern.

2e9

Sends a pseudo-random 2^9 -1 pattern.

2e15

Sends a pseudo-random 2^15 -1 pattern.

2e20

Sends a pseudo-random 2^20 -1 pattern. Not available on channelized ASAP MDAs.

2e23

Sends a pseudo-random 2^23 -1 pattern.

Platforms

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

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

All

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

All

Context

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

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

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

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

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

Full Context

configure service vprn interface ipv6 bfd

configure service vprn interface bfd

configure service ies interface ipv6 bfd

configure service vprn network-interface bfd

configure service ies interface 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 (for the 7750 SR only; see the note above)

Default

100

receive receive-interval

Sets the receive interval for the BFD session.

Values

100 to 100000

10 to 100000 (for the 7750 SR only; see the note above)

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 (for the 7750 SR only; see the Note above)

Default

100

type cpm-np

For the 7750 SR only, 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

All

Context

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

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

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

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

Full Context

configure service vprn subscriber-interface group-interface ipv6 bfd

configure service vprn subscriber-interface ipv6 bfd

configure service vprn subscriber-interface group-interface bfd

configure service vprn subscriber-interface bfd

Description

This command specifies the BFD attributes for the associated retail subscriber interface or group interface. If no parameters are defined the default value are used.

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.

Default

no bfd

Parameters

transmit-interval

Sets the transmit interval for the BFD session.

Values

10 to 100000

Default

100

Note:

On the 7750 SR, the transmit-interval can only be modified to a value less than 100 when the type cpm-np option is explicitly configured.

receive-interval

Sets the receive interval for the BFD session.

Values

10 to 100000

Default

100

Note:

On the 7750 SR, the receive-interval can only be modified to a value less than 100 when the type cpm-np option is explicitly configured.

multiplier

Sets the multiplier for the BFD session. A multiplier of less than 3 should not be used in production environments. 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 protocol (BGP) is notified of the fault.

Values

1 to 20

Default

3

echo-interval

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

Values

100 to 100000

Default

0

type cpm-np

Sets the CPM network processor as the local termination point for the BFD session to allow for fast timers down to 10ms granularity.

Platforms

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

Context

[Tree] (config>lag bfd)

Full Context

configure lag bfd

Description

This command creates the bfd context and enables BFD over the associated LAG links.

Platforms

All

Context

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

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

[Tree] (config>router>mpls>lsp bfd)

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

Full Context

configure router mpls lsp-template bfd

configure router mpls lsp primary bfd

configure router mpls lsp bfd

configure router mpls lsp secondary bfd

Description

Commands in this context configure LSP BFD commands on RSVP LSPs or seamless BFD commands on SR-TE LSPs.

Platforms

All

Context

[Tree] (config bfd)

Full Context

configure bfd

Description

This command specifies the context for the configuration of BFD parameters global to a specific router.

The no form of this command removes the context.

Platforms

All

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: On the 7750 SR and 7950 XRS SR OS, 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) The minimum value is 300 msec for central BFD sessions in the 7950 XRS.

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 for the 7750 SR and 7950 XRS. See Important Notes, above.

Platforms

All

Context

[Tree] (config>service>fpipe>spoke-sdp bfd)

[Tree] (config>service>ipipe>spoke-sdp bfd)

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

[Tree] (config>service>ies>if>spoke-sdp bfd)

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

[Tree] (config>service>cpipe>spoke-sdp bfd)

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

[Tree] (config>service>apipe>spoke-sdp bfd)

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

Full Context

configure service fpipe spoke-sdp bfd

configure service ipipe spoke-sdp bfd

configure service vpls mesh-sdp bfd

configure service ies interface spoke-sdp bfd

configure service vpls spoke-sdp bfd

configure service cpipe spoke-sdp bfd

configure service vprn interface spoke-sdp bfd

configure service apipe spoke-sdp bfd

configure service epipe spoke-sdp bfd

Description

This command creates a context for the configuration of VCCV BFD.

Platforms

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

• configure service fpipe spoke-sdp bfd
• configure service cpipe spoke-sdp bfd

All

• configure service vpls mesh-sdp bfd
• configure service vpls spoke-sdp bfd
• configure service ipipe spoke-sdp bfd
• configure service epipe spoke-sdp bfd
• configure service vprn interface spoke-sdp bfd
• configure service ies interface spoke-sdp bfd

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

• configure service apipe spoke-sdp bfd

Context

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

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

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

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

Full Context

configure service ies interface ipsec ipsec-tunnel bfd-designate

configure router interface ipsec ipsec-tunnel bfd-designate

configure service vprn interface ipsec ipsec-tunnel bfd-designate

configure service vprn interface sap ipsec-tunnel bfd-designate

Description

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

Default

no bfd-designate

Platforms

VSR

• configure router interface ipsec ipsec-tunnel bfd-designate
• configure service vprn interface ipsec ipsec-tunnel bfd-designate
• configure service ies interface ipsec ipsec-tunnel bfd-designate

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

• configure service vprn interface sap ipsec-tunnel bfd-designate

Context

[Tree] (config>service>vprn>sub-if>grp-if>srrp bfd-enable)

[Tree] (config>service>ies>sub-if>grp-if>srrp bfd-enable)

Full Context

configure service vprn subscriber-interface group-interface srrp bfd-enable

configure service ies subscriber-interface group-interface srrp 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 configured with BFD is using a LAG or a spoke-SDP, the BFD transmit and receive intervals need to be set to a minimum of 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

service-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 for the BFD session.

name service-name

Specifies a service name, up to 64 characters.

Platforms

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

Context

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

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

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

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

Full Context

configure router bgp bfd-enable

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

configure router bgp group neighbor bfd-enable

configure router bgp group 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

All

Context

[Tree] (config>service>ipipe>spoke-sdp>bfd bfd-enable)

[Tree] (config>service>fpipe>spoke-sdp>bfd bfd-enable)

[Tree] (config>service>apipe>spoke-sdp>bfd bfd-enable)

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

[Tree] (config>service>cpipe>spoke-sdp>bfd bfd-enable)

Full Context

configure service ipipe spoke-sdp bfd bfd-enable

configure service fpipe spoke-sdp bfd bfd-enable

configure service apipe spoke-sdp bfd bfd-enable

configure service epipe spoke-sdp bfd bfd-enable

configure service cpipe spoke-sdp bfd bfd-enable

Description

This command enables VCCV BFD on the PW associated with the VLL, BGP VPWS, or VPLS service. The parameters for the BFD session are derived from the named BFD template, which must have been first configured using the bfd-template command.

The no form of this command disables VCCV BFD on the spoke-SDP.

Default

no bfd-enable

Platforms

All

• configure service ipipe spoke-sdp bfd bfd-enable
• configure service epipe spoke-sdp bfd bfd-enable

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

• configure service fpipe spoke-sdp bfd bfd-enable
• configure service cpipe spoke-sdp bfd bfd-enable

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

• configure service apipe spoke-sdp bfd bfd-enable

Context

[Tree] (config>service>epipe>bgp>pw-template-binding bfd-enable)

Full Context

configure service epipe bgp pw-template-binding bfd-enable

Description

This command enables VCCV BFD on the PW associated with the VLL, BGP VPWS, or VPLS service. The parameters for the BFD session are derived from the named BFD template, which must have been first configured using the bfd-template command.

The no form of this command disables VCCV BFD.

Default

no bfd-enable

Platforms

All

Context

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

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

Full Context

configure service vpls spoke-sdp bfd bfd-enable

configure service vpls mesh-sdp bfd bfd-enable

Description

This command enables VCCV BFD on the PWs associated with the VPLS service's spoke or mesh SDPs. The parameters for the BFD session are derived from the named BFD template, which must have been first configured using the bfd-template command.

The no form of this command disables VCCV BFD on the mesh-SDP or spoke-SDP.

Default

no bfd-enable

Platforms

All

Context

[Tree] (config>service>vpls>bgp>pw-template-binding bfd-enable)

[Tree] (config>service>vpls>bgp-ad>pw-template-binding bfd-enable)

Full Context

configure service vpls bgp pw-template-binding bfd-enable

configure service vpls bgp-ad pw-template-binding bfd-enable

Description

This command enables VCCV BFD on the PWs associated with the BGP AD VPLS service. The parameters for the BFD session are derived from the named BFD template, which must have been first configured using the bfd-template command.

The no form of this command disables VCCV BFD.

Default

no bfd-enable

Platforms

All

Context

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

Full Context

configure service ies interface spoke-sdp bfd bfd-enable

Description

This command enables VCCV BFD on the PW associated with the spoke-SDP terminated on the IES interface. The parameters for the BFD session are derived from the named BFD template, which must have been first configured using the bfd-template command.

The no form of this command disables VCCV BFD on the spoke-SDP.

Platforms

All

Context

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

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

Full Context

configure service ies interface vrrp bfd-enable

configure service ies interface ipv6 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

All

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

All

Context

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

Full Context

configure service vprn interface spoke-sdp bfd bfd-enable

Description

This command enables VCCV BFD on the PW associated with the spoke-SDP terminated on the VPRN interface service. The parameters for the BFD session are derived from the named BFD template, which must have been first configured using the bfd-template command.

The no form of this command disables VCCV BFD on the spoke-SDP.

Platforms

All

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

All

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

All

Context

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

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

Full Context

configure service vprn ospf3 area interface bfd-enable

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

Forces adjacency down on BFD failure.

Platforms

All

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

All

Context

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

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

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

Full Context

configure service vprn bgp bfd-enable

configure service vprn bgp group bfd-enable

configure service vprn bgp group neighbor 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

All

Context

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

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

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

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

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

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

Full Context

configure service vprn ripng group neighbor bfd-enable

configure service vprn rip bfd-enable

configure service vprn ripng group bfd-enable

configure service vprn rip group bfd-enable

configure service vprn ripng bfd-enable

configure service vprn rip group neighbor 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

All

Context

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

Full Context

configure router ldp lsp-bfd bfd-enable

Description

This command enables BFD on LDP LSPs with FECs that match the prefix list specified using the lsp-bfd command. A named BFD template must be configured and applied prior to enabling BFD.

The no form of this command disables BFD.

Default

no bfd-enable

Platforms

All

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.

The ipv6 option for this command is not supported on the 7450 ESS.

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

All

Context

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

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

Full Context

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

configure router ldp targeted-session peer 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

All

Context

[Tree] (config>router>mpls>lsp>primary>bfd bfd-enable)

[Tree] (config>router>mpls>lsp>secondary>bfd bfd-enable)

[Tree] (config>router>mpls>lsp>bfd bfd-enable)

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

Full Context

configure router mpls lsp primary bfd bfd-enable

configure router mpls lsp secondary bfd bfd-enable

configure router mpls lsp bfd bfd-enable

configure router mpls lsp-template bfd bfd-enable

Description

This command enables LSP BFD on the RSVP LSP or S-BFD for the SR-TE LSP. LSP BFD must also be configured under config>router to enable LSP BFD. The parameters for the BFD session are derived from the named BFD Template, which must have been configured prior to the bfd-enable command and associated with the service using the bfd-template command.

The no form of this command disables LSP BFD on the RSVP LSP or S-BFD on the SR-TE LSP.

Default

no bfd-enable

Platforms

All

Context

[Tree] (config>router>mpls>lsp>protect-tp-path>mep bfd-enable)

[Tree] (config>router>mpls>lsp>working-tp-path>mep bfd-enable)

Full Context

configure router mpls lsp protect-tp-path mep bfd-enable

configure router mpls lsp working-tp-path mep bfd-enable

Description

The command associates the operational state of an MPLS-TP path with a BFD session whose control packets flow on the path. The BFD packets are encapsulated in a generic associated channel (G-ACh) on the path. The timer parameters of the BFD session are taken from the OAM template of the MEP.

A value of cc means that the BFD session is only used for continuity check of the MPLS-TP path. In this case, the CC timer parameters of the OAM template apply. A value of cv means that the BFD session is used for both continuity checking and connectivity verification, and the CV timers of the OAM template apply.

This form of the bfd-enable command is only applicable when it is configured under a MEP used on an MPLS-TP working or protection path.

Default

no bfd-enable

Parameters

cc

Indicates that BFD runs in CC only mode. This mode uses G-ACh channel type 0x07.

cc_cv

Indicates that BFD runs in combined CC and CV mode. This mode uses channel type 0x22 for MPLS-TP CC packets, and 0x23 for MPLS-TP CV packets.

Platforms

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

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

All

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

VSR

• configure service vprn interface ipsec ipsec-tunnel bfd-enable
• configure service ies interface ipsec ipsec-tunnel bfd-enable
• configure router interface ipsec ipsec-tunnel bfd-enable

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

• configure service vprn interface sap ipsec-tunnel bfd-enable

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

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

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

All

Context

[Tree] (config>router>p2mp-sr-tree bfd-enable)

Full Context

configure router p2mp-sr-tree bfd-enable

Description

This command enables BFD tracking at the P2MP SR tree level, which causes all next-hops of the replication segments that use a BFD-enabled Layer 3 interface to register with the BFD module.

The no form of this command disables BFD tracking of the P2MP SR tree.

Default

no bfd-enable

Parameters

ipv4

Enables the use of IPv4 BFD tracking.

ipv6

Enables the use of IPv6 BFD tracking.

Platforms

All

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

All

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

All

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

All

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

All

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 enables the use of 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 OSPF protocol adjacency.

Default

no bfd-enable

Parameters

remain-down-on-failure

If the BFD session does not come back up within 10 seconds, then OSPF brings down the adjacency and wait on BFD again. 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.

Platforms

All

Context

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

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

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

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

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

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

Full Context

configure router ripng group neighbor bfd-enable

configure router rip bfd-enable

configure router rip group bfd-enable

configure router ripng group bfd-enable

configure router rip group neighbor bfd-enable

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

All

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

All

Context

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

Full Context

configure router bier bfd-enable

Description

This command configures BFD tracking for BIER, which means that all next-hops that use a BFD-enabled interface register with the BFD module.

The no form of this command disables BFD tracking under BIER.

Default

no bfd-enable

Parameters

ipv4

Enables the use of IPv4 BFD tracking.

Platforms

All

Context

[Tree] (config>subscr-mgmt>bgp-prng-plcy bfd-enable)

Full Context

configure subscriber-mgmt bgp-peering-policy bfd-enable

Description

This command enables bi-directional forwarding (BFD) to control the state of an ESM dynamic BGP peer that is setup with this BGP peering policy. The parameters used for the BFD session are configured in the bfd context of the group-interface or retail subscriber-interface.

The no form of this command disables BFD for new ESM dynamic BGP peers that are setup with this BGP peering policy.

Default

no bfd-enable

Platforms

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

Context

[Tree] (config>subscr-mgmt>pfcp-association bfd-expedited-path-down)

Full Context

configure subscriber-mgmt pfcp-association bfd-expedited-path-down

Description

This command enables BFD session tracking to expedite PFCP path down detection. When enabled, the system tracks BFD sessions to expedite PFCP path down detection on BFD down events. This requires the configuration of path-restoration-time.

The no form of this command disables BFD session tracking to expedite PFCP path down detection.

Default

no bfd-expedited-path-down

Platforms

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

Context

[Tree] (config>lag>bfd>family bfd-on-distributing-only)

Full Context

configure lag bfd family bfd-on-distributing-only

Description

This command enables standardized implementation for interworking with other vendors by restricting micro-BFD sessions to links in LACP state distributing.

The no form of this command disables restricting micro-BFD sessions, which is an enhanced proprietary solution.

Default

no bfd-on-distributing-only

Platforms

All

Context

[Tree] (config>router>lsp-bfd bfd-sessions)

Full Context

configure router lsp-bfd bfd-sessions

Description

This command enables or disables LSP BFD at the tail end of LSPs on the system. It is also used to limit the maximum number of LSP BFD sessions that may be established at the tail-end of LSPs on a node to max-limit. It has no impact on the number of LSP BFD sessions that may be configured at the head end.

The no version of this command disables the creation of LSP BFD sessions by the node at the tail end of LSPs.

Default

no bfd-sessions

Parameters

max-limit

Specifies the maximum number of LSP BFD sessions at the tail end of LSPs that can be established on a system. The maximum value that can be entered is constrained by the system wide limit for centralized BFD sessions.

Values

1- max, where max is the platform specific limit on centralized BFD sessions.

Platforms

All

Context

[Tree] (config>service>apipe>spoke-sdp>bfd bfd-template)

[Tree] (config>service>ipipe>spoke-sdp>bfd bfd-template)

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

[Tree] (config>service>fpipe>spoke-sdp>bfd bfd-template)

[Tree] (config>service>cpipe>spoke-sdp>bfd bfd-template)

Full Context

configure service apipe spoke-sdp bfd bfd-template

configure service ipipe spoke-sdp bfd bfd-template

configure service epipe spoke-sdp bfd bfd-template

configure service fpipe spoke-sdp bfd bfd-template

configure service cpipe spoke-sdp bfd bfd-template

Description

This command configures a named BFD template to be used by VCCV BFD on PWs belonging to the VLL service. The template specifies parameters, such as the minimum transmit and receive control packet timer intervals, used by the BFD session. Template parameters are configured under the config>router>bfd context.

The no form of this command removes the binding of the BFD template to the spoke-SDP.

Default

no bfd-template

Parameters

name

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

Platforms

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

• configure service apipe spoke-sdp bfd bfd-template

All

• configure service ipipe spoke-sdp bfd bfd-template
• configure service epipe spoke-sdp bfd bfd-template

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

• configure service cpipe spoke-sdp bfd bfd-template
• configure service fpipe spoke-sdp bfd bfd-template

Context

[Tree] (config>service>epipe>bgp>pw-template-binding bfd-template)

Full Context

configure service epipe bgp pw-template-binding bfd-template

Description

This command configures a named BFD template to be used by VCCV BFD on PWs belonging to the BGP VPWS service. The template specifies parameters, such as the minimum transmit and receive control packet timer intervals, to be used by the BFD session. Template parameters are configured under the config>router>bfd context.

The no form of this command removes the binding of the BFD template to the BGP VPWS.

Default

no bfd-template

Parameters

name

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

Platforms

All

Context

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

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

Full Context

configure service vpls spoke-sdp bfd bfd-template

configure service vpls mesh-sdp bfd bfd-template

Description

This command configures a named BFD template to be used by VCCV BFD on the PW belonging to the VPLS spoke-SDP or mesh-SDP. The template specifies parameters, such as the minimum transmit and receive control packet timer intervals, to be used by the BFD session. Template parameters are configured under the config>router>bfd context.

The no form of this command removes the binding of the BFD template to the spoke-SDP.

Default

no bfd-template

Parameters

name

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

Platforms

All

Context

[Tree] (config>service>vpls>bgp>pw-template-binding bfd-template)

[Tree] (config>service>vpls>bgp-ad>pw-template-binding bfd-template)

Full Context

configure service vpls bgp pw-template-binding bfd-template

configure service vpls bgp-ad pw-template-binding bfd-template

Description

This command configures a named BFD template to be used by VCCV BFD on PWs belonging to the BGP VPWS, or BGP AD VPLS service. The template specifies parameters, such as the minimum transmit and receive control packet timer intervals, to be used by the BFD session. Template parameters are configured under the config>router>bfd context.

Default

no bfd-template

Parameters

name

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

Platforms

All

Context

[Tree] (config>service>ies>if>spoke-sdp>bfd bfd-template)

Full Context

configure service ies interface spoke-sdp bfd bfd-template

Description

This command configures a named BFD template to be used by VCCV BFD on the PW belonging to the spoke-SDP that is terminated on the IES interface. The template specifies parameters, such as the minimum transmit and receive control packet timer intervals, to be used by the BFD session. Template parameters are configured under the config>router>bfd context.

The no form of this command removes the binding of the BFD template to the spoke-SDP.

Default

no bfd-template

Parameters

name

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

Platforms

All

Context

[Tree] (config>service>vprn>if>spoke-sdp>bfd bfd-template)

Full Context

configure service vprn interface spoke-sdp bfd bfd-template

Description

This command configures a named BFD template to be used by VCCV BFD on the PW belonging to spoke-SDP that is terminated on the VPRN interface. The template specifies parameters, such as the minimum transmit and receive control packet timer intervals, to be used by the BFD session. Template parameters are configured under the config>router>bfd context.

The no form of this command removes the binding of the BFD template to the spoke-SDP.

Default

no bfd-template

Parameters

name

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

Platforms

All

Context

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

Full Context

configure router ldp lsp-bfd bfd-template

Description

This command applies the specified BFD template to the BFD sessions for LDP LSPs with FECs that match the prefix list. The specified BFD template must exist prior to its application to LSP BFD.

The no form of this command removes the application of the BFD template.

Default

no bfd-template

Parameters

bfd-template-name

Specifies the name of the BFD template configured using the config>router>bfd>bfd-template command, up to 32 characters maximum.

Platforms

All

Context

[Tree] (config>router>mpls>mpls-tp>oam-template bfd-template)

Full Context

configure router mpls mpls-tp oam-template bfd-template

Description

This command configures a named BFD template to be referenced by an OAM template.

Default

no bfd-template

Parameters

name

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

Platforms

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

Context

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

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

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

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

Full Context

configure router mpls lsp bfd bfd-template

configure router mpls lsp secondary bfd bfd-template

configure router mpls lsp primary bfd bfd-template

configure router mpls lsp-template bfd bfd-template

Description

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

The no form of this command removes the association of the named BFD template to the LSP.

Default

no bfd-template

Parameters

name

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

Platforms

All

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

All

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

All

Context

[Tree] (config>router>mpls>lsp>working-tp-path>mep bfd-trap-suppression)

[Tree] (config>router>mpls>lsp>protect-tp-path>mep bfd-trap-suppression)

Full Context

configure router mpls lsp working-tp-path mep bfd-trap-suppression

configure router mpls lsp protect-tp-path mep bfd-trap-suppression

Description

This command enables AIS packets on a working or protection path of an MPLS-TP LSP to suppress BFD Down traps if a BFD session goes down on that path. It also causes BFD Up traps to be suppressed, and enables the 2.5 s hold-down timer.

Suppression only occurs as a result of a received AIS packet. Traps generated as a result of a local failure at an LER are not suppressed.

The no form of this command disables BFD Down/Up trap suppression when AIS packets are received.

Default

no bfd-trap-suppression

Platforms

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

Context

[Tree] (config>router>bier>template>sub-domain bfr-id)

Full Context

configure router bier template sub-domain bfr-id

Description

This command specifies the BIER-ID for this sub-domain. BIER-IDs should be assigned sequentially as the SI and BIER bit position are driven by the IDs. The equation used to drive BIER SI and bit positions from the ID is as follows:

SI = (BFR-id -1) /BitStringLength

bit position = ((BFR-id -1) modulo BitStringLength) +1

If the BIER-ID is sequential then the all bit positions in a bit string length will be utilized before moving on to the next SetID (SI).

BFR ID configuration is only necessary for BFIR and BFER, and not for transit BFRs

The no form of this command removes the BIER-ID.

Parameters

bfr-id

The BIER-ID of the router.

Values

1 to 4096

Platforms

All

Context

[Tree] (config>subscr-mgmt>isa-svc-chain>evpn bgp)

Full Context

configure subscriber-mgmt isa-service-chaining evpn bgp

Description

Commands in this context configure EVPN BGP-specific information.

The no form of this command reverts to the default.

Platforms

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

Context

[Tree] (config>service>epipe bgp)

Full Context

configure service epipe bgp

Description

Commands in this context configure the BGP related parameters BGP used for multi-homing and BGP VPWS.

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

Platforms

All

Context

[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>vprn>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-ipvpn mpls auto-bind-tunnel resolution-filter bgp

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

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

All

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

All

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

All

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

All

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

All

Context

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

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

Full Context

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

configure router bgp next-hop-resolution labeled-routes transport-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

All

Context

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

Full Context

configure service vpls bgp-ad

Description

This command configures BGP auto-discovery.

Platforms

All

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

All

Context

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

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

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

Full Context

configure service vpls bgp-evpn

configure service epipe bgp-evpn

configure service system bgp-evpn

Description

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

Platforms

All

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

All

Context

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

Full Context

configure redundancy bgp-evpn-multi-homing

Description

Commands in this context configure the BGP-EVPN global timers

Platforms

All

Context

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

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

Full Context

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

configure router policy-options policy-statement entry 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

All

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

All

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 BGP labels hold timer on the ingress router.

Default

bgp-labels-hold-timer 0

Parameters

seconds

Specifies the seconds

Values

0 to 255

Platforms

All

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

All

Context

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

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

Full Context

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

configure router policy-options policy-statement entry 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

All

Context

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

Full Context

configure redundancy bgp-multi-homing

Description

This command configures BGP multi-homing parameters.

Platforms

All

Context

[Tree] (config>subscr-mgmt bgp-peering-policy)

Full Context

configure subscriber-mgmt bgp-peering-policy

Description

This command configures the name of the BGP peering policy.

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

Parameters

policy-name

Specifies the BGP peer policy name, up to 32 characters.

create

Keyword used to create the peering policy. The create keyword requirement can be enabled or disabled in the environment>create context.

Platforms

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

Context

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

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

Full Context

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

configure filter match-list ipv6-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

All

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

All

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

All

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

All

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

All

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 metric of the BGP-LU route, if the BGP-LU route has an AIGP path attribute; otherwise, it is set to the number specified by value. The effect of this command can be overridden by BGP import policies.

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 this command reverts to the default.

Default

no bgp-tunnel-metric

Parameters

value

Specifies the BGP tunnel metric.

Values

0 to 4294967295

prefer-aigp

Specifies that the TTM metric be based on the Accumulated IGP (AIGP) metric if the route has the path attribute. When prefer-aigp is configured and a BGP-LU route is selected for installation in TTM and it 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, plus the resolved cost to the BGP next-hop of the route if the tunnel has the AIGP path attribute. Otherwise, the number in value is set as the metric.

Platforms

All

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 provides the ability to set 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 metric of the BGP-LU route, if the BGP-LU route has an AIGP path attribute, otherwise it reverts to the value parameter.

The no form of this command reverts to the default.

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 the TTM metric be based on the Accumulated IGP (AIGP) metric if the route has the path attribute.

Platforms

All

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

All

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

All

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

All

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

All

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

All

Context

[Tree] (config>service>vprn>mvpn>provider-tunnel>inclusive bier)

[Tree] (config>service>vprn>mvpn>provider-tunnel>selective bier)

Full Context

configure service vprn mvpn provider-tunnel inclusive bier

configure service vprn mvpn provider-tunnel selective bier

Description

This command creates a BIER inclusive or selective provider tunnel.

The no form of this command deletes the tunnel.

Platforms

All

Context

[Tree] (config>router bier)

Full Context

configure router bier

Description

Commands in this context configure BIER.

Platforms

All

Context

[Tree] (config>router>isis>level bier)

Full Context

configure router isis level bier

Description

This command enables BIER capabilities.

The no form of this command disables BIER capabilities.

Platforms

All

Context

[Tree] (config>router>ospf>area bier)

Full Context

configure router ospf area bier

Description

This command enables BIER capabilities.

The no form of this command disables BIER capabilities.

Default

no bier

Platforms

All

Context

[Tree] (oam bier-ping)

Full Context

oam bier-ping

Description

This command performs connectivity tests on the BIER data plane.

Parameters

sub-domain-id

Specifies the ID of the sub-domain where the BIER OAM packet is generated.

Values

0 to 255

Default

0

bfr-id

Specifies the BIER-ID of the router.

Values

1 to 4096

ipv4-address

Specifies the routable IPv4 address of the BFR, used by BIER to identify the BFR. Up to 16 IPv4 addresses can be specified.

Values

a.b.c.d

detail

Keyword to display more information.

fc-name

Specifies the FC and profile parameters that are used to indicate the forwarding class and profile of the BIER echo request packet.

Values

be, l2, af, l1, h2, ef, h1, nc

Default

be

{in | out}

Specifies the profile state of the BIER echo request packet.

Default

out

timeout

Specifies the number, in seconds, used to override the default timeout value and is the amount of time that the router waits for a message reply after sending the message request. Upon the expiration of the timeout, the test is marked complete and no more packets are processed.

Values

1 to 120

Default

10

ttl

Specifies the TTL value for the BIER ping test, expressed as a decimal integer.

Values

1 to 255

Default

255

Platforms

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

Context

[Tree] (debug>router>pim bier-signaling)

Full Context

debug router pim bier-signaling

Description

This command enables debugging for bier inband.

The no form of this command disables debugging for bier inband.

Parameters

detail

Debugs detailed information on the bier inband.

Platforms

All

Context

[Tree] (config>router>pim>interface bier-signaling)

Full Context

configure router pim interface bier-signaling

Description

This commands enables PIM signaling through a BIER domain. PIM signaling only functions in the context of SD0. PIM signaling can signal PIM IPv4 and IPv6 over a BIER IPV4 core.

The no form of this command disables PIM signaling through a BIER domain.

Default

no bier-signaling

Parameters

ipv4

Enables the use of IPv4 PIM signaling through a BIER domain.

ipv6

Enables the use of IPv6 PIM signaling through a BIER domain.

Platforms

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

Context

[Tree] (oam bier-trace)

Full Context

oam bier-trace

Description

This command performs trace tests on the BIER data plane.

Parameters

sub-domain-id

Specifies the ID of the sub-domain where the BIER OAM packet is generated.

Values

0 to 255

Default

0

bfr-id

Specifies the BIER-ID of the router.

Values

1 to 4096

ipv4-address

Specifies the routable IPv4 address of the BFR, used by BIER to identify the BFR.

Values

a.b.c.d

detail

Keyword to display more information.

fc-name

Specifies the FC and profile parameters that are used to indicate the forwarding class and profile of the BIER OAM packet.

Values

be, l2, af, l1, h2, ef, h1, nc

Default

be

{in | out}

Specifies the profile state of the BIER echo request packet.

Default

out

min-ttl

Specifies the minimum TTL value for the BIER trace test, expressed as a decimal integer.

Values

1 to 255

Default

1

max-ttl

Specifies the maximum TTL value for the BIER trace test, expressed as a decimal integer.

Values

1 to 255

Default

30

probes-per-hop

Specifies the probes-per-hop count, expressed as number of packets.

Values

1 to 10

Default

1

timeout

Specifies the number, in seconds, used to override the default timeout value and is the amount of time that the router waits for a message reply after sending each probe for a specific test. Upon the expiration of the timeout, the test is marked complete and no more packets are processed for the request probe.

When the test consists of multiple probes, the timeout is the interval, in seconds, between request probes.

A BIER trace test terminates after five consecutive timeouts.

Values

1 to 60

Default

3

Platforms

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

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

All

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

All

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

All

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

All

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

All

Context

[Tree] (config>service>sdp binding)

Full Context

configure service sdp binding

Description

Commands in this context configure SDP bindings.

Platforms

All

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

All

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

All

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

All

Context

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

Full Context

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

Description

Commands in this context configure an SRv6 binding SID.

The binding SID ID is a 32-bit unsigned integer. Only one binding SID ID is supported.

The no form of this command deletes the SRv6 binding SID.

Parameters

binding-sid-id

Specifies the binding SID number.

Values

1

create

Keyword to creating a binding SID. The create keyword requirement can be enabled or disabled in the environment>create context.

Platforms

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

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

All

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

All

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

All

Context

[Tree] (config>port>tdm>ds1 bit-error-insertion)

[Tree] (config>port>tdm>e3 bit-error-insertion)

[Tree] (config>port>tdm>ds3 bit-error-insertion)

[Tree] (config>port>tdm>e1 bit-error-insertion)

Full Context

configure port tdm ds1 bit-error-insertion

configure port tdm e3 bit-error-insertion

configure port tdm ds3 bit-error-insertion

configure port tdm e1 bit-error-insertion

Description

This command inserts bit errors into a running BERT test. The number of errors inserted corresponds to 10^(-rate). A rate of 0 will cause 1 error in every bit transmitted. A rate of 7 will cause an error rate of 10^(-7), or 1 error in every one billion bits transmitted.

The no command disables the insertion of bit errors into the bit error rate test stream.

Note that this command is not saved in the router configuration between boots.

Default

no bit-error-insertion

Parameters

rate

Specifies the bit error rate, expressed as an integer.

Values

2 to 7

Platforms

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

Context

[Tree] (config>eth-tunnel>path>eth-cfm>mep>eth-test-enable bit-error-threshold)

[Tree] (config>lag>eth-cfm>mep bit-error-threshold)

Full Context

configure eth-tunnel path eth-cfm mep eth-test-enable bit-error-threshold

configure lag eth-cfm mep bit-error-threshold

Description

This command specifies the lowest priority defect that is allowed to generate a fault alarm.

Default

bit-error-threshold 1

Parameters

bit-errors

Specifies the lowest priority defect.

Values

0 to 11840

Platforms

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

Context

[Tree] (config>service>epipe>spoke-sdp>eth-cfm>mep>eth-test-enable bit-error-threshold)

[Tree] (config>service>epipe>sap>eth-cfm>mep>eth-test-enable bit-error-threshold)

Full Context

configure service epipe spoke-sdp eth-cfm mep eth-test-enable bit-error-threshold

configure service epipe sap eth-cfm mep eth-test-enable bit-error-threshold

Description

This command is used to specify the threshold value of bit errors.

Parameters

errors

The threshold value of bit errors.

Values

0 to 11840

Default

1

Platforms

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

Context

[Tree] (config>service>vpls>eth-cfm>mep>eth-test-enable bit-error-threshold)

[Tree] (config>service>vpls>mesh-sdp>eth-cfm>mep>eth-test-enable bit-error-threshold)

[Tree] (config>service>vpls>spoke-sdp>eth-cfm>mep>eth-test-enable bit-error-threshold)

[Tree] (config>service>vpls>sap>eth-cfm>mep>eth-test-enable bit-error-threshold)

Full Context

configure service vpls eth-cfm mep eth-test-enable bit-error-threshold

configure service vpls mesh-sdp eth-cfm mep eth-test-enable bit-error-threshold

configure service vpls spoke-sdp eth-cfm mep eth-test-enable bit-error-threshold

configure service vpls sap eth-cfm mep eth-test-enable bit-error-threshold

Description

This command specifies the lowest priority defect that is allowed to generate a fault alarm.

Default

bit-error-threshold 1

Parameters

bit-errors

Specifies the lowest priority defect.

Values

0 to 11840

Platforms

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

Context

[Tree] (config>service>ies>if>sap>eth-cfm>mep>eth-test-enable bit-error-threshold)

[Tree] (config>service>ies>if>spoke-sdp>eth-cfm>mep>eth-test-enable bit-error-threshold)

[Tree] (config>service>ies>sub-if>grp-if>sap>eth-cfm>mep>eth-test-enable bit-error-threshold)

Full Context

configure service ies interface sap eth-cfm mep eth-test-enable bit-error-threshold

configure service ies interface spoke-sdp eth-cfm mep eth-test-enable bit-error-threshold

configure service ies subscriber-interface group-interface sap eth-cfm mep eth-test-enable bit-error-threshold

Description

This command specifies the lowest priority defect that is allowed to generate a fault alarm.

Default

bit-error-threshold 1

Parameters

bit-errors

Specifies the lowest priority defect.

Values

0 to 11840

Platforms

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

• configure service ies interface sap eth-cfm mep eth-test-enable bit-error-threshold
• configure service ies interface spoke-sdp eth-cfm mep eth-test-enable bit-error-threshold

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

• configure service ies subscriber-interface group-interface sap eth-cfm mep eth-test-enable bit-error-threshold

Context

[Tree] (config>service>vprn>if>spoke-sdp>eth-cfm>mep bit-error-threshold)

[Tree] (config>service>vprn>sub-if>grp-if>sap>eth-cfm bit-error-threshold)

[Tree] (config>service>vprn>if>sap>eth-cfm>mep bit-error-threshold)

Full Context

configure service vprn interface spoke-sdp eth-cfm mep bit-error-threshold

configure service vprn subscriber-interface group-interface sap eth-cfm bit-error-threshold

configure service vprn interface sap eth-cfm mep bit-error-threshold

Description

This command specifies the lowest priority defect that is allowed to generate a fault alarm.

Default

bit-error-threshold 1

Parameters

bit-errors

Specifies the lowest priority defect.

Values

0 to 11840

Platforms

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

• configure service vprn interface spoke-sdp eth-cfm mep bit-error-threshold
• configure service vprn interface sap eth-cfm mep bit-error-threshold

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

• configure service vprn subscriber-interface group-interface sap eth-cfm bit-error-threshold

Context

[Tree] (config>router>if>eth-cfm>mep>eth-test-enable bit-error-threshold)

Full Context

configure router interface eth-cfm mep eth-test-enable bit-error-threshold

Description

This command specifies the lowest priority defect that generates a fault alarm.

Default

bit-error-threshold 1

Parameters

bit-errors

Specifies the priority defect threshold.

Values

0 to 11840

Platforms

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

Context

[Tree] (config>eth-ring>path>eth-cfm>mep>eth-test-enable bit-error-threshold)

Full Context

configure eth-ring path eth-cfm mep eth-test-enable bit-error-threshold

Description

This command specifies the lowest priority defect that is allowed to generate a fault alarm.

Default

bit-error-threshold 1

Parameters

bit-errors

Specifies the lowest priority defect.

Values

0 to 11840

Platforms

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

Context

[Tree] (config>application-assurance bit-rate-high-wmark)

Full Context

configure application-assurance bit-rate-high-wmark

Description

This command configures the high watermark for bit rate alarms.

Default

bit-rate-high-wmark max

Parameters

high-watermark

Specifies the high watermark for bit rate alarms, in Mb/s. The value must be larger than or equal to the low watermark value.

Values

1 to 40000, max (disabled)

Platforms

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