s Commands – Part III

sid

sid

Syntax

sid label value

Context

[Tree] (config>router>ospf>segm-rtng>adjacency-set sid)

[Tree] (config>router>isis>segm-rtng>adjacency-set sid)

Full Context

configure router ospf segment-routing adjacency-set sid

configure router isis segment-routing adjacency-set sid

Description

This command allows a static SID value to be assigned to an adjacency set in IS-IS or OSPF segment routing.

The label option specifies the value is assigned to an MPLS label.

The no form of this command removes the adjacency SID.

Parameters

label value

Specifies the value of adjacency SID label.

Values

18432 to 524287 | 1048575 (FP4 only)

Platforms

All

sid-action

sid-action

Syntax

sid-action action

no sid-action

Context

[Tree] (config>router>p2mp-sr-tree>replication-segment>sr-mpls sid-action)

Full Context

configure router p2mp-sr-tree replication-segment segment-routing-mpls sid-action

Description

This command configures the SID action to take for the replication segment of the P2MP SR tree.

The no form of this command removes the SID action.

Default

no sid-action

Parameters

action

Specifies the name of the SID action.

Values

push — Specifies that an outgoing SID list is pushed and forwarded on to the corresponding programmed outgoing interfaces.

pop — Specifies that on the leaf node the incoming SID is popped on the underlay packet forwarded to the host.

swap — Specifies, if an incoming SID is configured, that the SID is swapped with an outgoing SID or SID list and forwarded to the corresponding OIF.

Platforms

All

sid-allocation

sid-allocation

Syntax

sid-allocation {sequential | random}

no sid-allocation

Context

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

Full Context

configure subscriber-mgmt ppp-policy sid-allocation

Description

This command configures the method for allocating the PPPoE session ID.

For both sequential and random options, the session ID range is 1 to 8191.

The no form of this command reverts to the default.

Default

sid-allocation sequential

Parameters

sequential

Specifies for PPPoE sessions with the same client MAC address and active on the same SAP, to allocate the session ID in sequential order starting with

ID = 1.

random

Specifies for PPPoE sessions with the same client MAC address and active on the same SAP, to allocate a unique session ID in random order.

Platforms

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

sid-length

sid-length

Syntax

sid-length sid-length

Context

[Tree] (conf>router>sr>srv6>micro-segment sid-length)

Full Context

configure router segment-routing segment-routing-v6 micro-segment sid-length

Description

This command configures the length of the micro-segments.

Default

sid-length 16

Parameters

sid-length

Specifies the length of micro-segments, in bits.

Values

16

Platforms

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

sid-map

sid-map

Syntax

sid-map node-sid {index value [range value]} prefix {{ip-address/mask} | {ip-address} {netmask}} [ set-flags {s}] [level { 1 | 2 | 1/2}] [clear-n-flag]

no sid-map node-sid index value

Context

[Tree] (config>router>isis>segm-rtng>mapping-server sid-map)

Full Context

configure router isis segment-routing mapping-server sid-map

Description

This command configures the Segment Routing mapping server database in IS-IS.

The user enters the node SID index for one or a range of prefixes by specifying the first index value and optionally a range value can be entered. The default value for the range option is 1. Only the first prefix in a consecutive range of prefixes must be entered. The user can enter the first prefix with a mask lower than 32 and the SID or label binding TLV is advertised, but the routers will not resolve these prefix SIDs and will generate a trap.

By setting the S-flag, the user can indicate to the IS-IS routers in the rest of the network that the flooding scope of the SID or label binding TLV is the entire domain. In that case, a router receiving the TLV advertisement should leak it between ISIS levels. If leaked from level 2 to level 1, the D-flag must be set and once set the TLV cannot be leaked back into level 2. Otherwise, the S-flag is clear by default and the TLV must not be leaked by routers that receive the mapping server advertisement.

Note that the SR OS does not leak this TLV between IS-IS instances and does not support the multi-topology SID/Label Binding TLV format.

In addition, the user can specify the mapping server own flooding scope for the generated SID or label binding TLV using the level option. This option allows the user to narrow the flooding scope configured under the router IS-IS level-capability for a one or more SID or label binding TLVs if required. The default flooding scope of the mapping server is Layer 1 or Layer 2, which can be narrowed by the value configured under the router IS-IS level-capability.

The A-flag and M-flag are not supported by the mapping server feature. The mapping client ignores the flags.

Each time a prefix or a range of prefixes is configured in the SR mapping database in any routing instance, the router issues for this prefix or range of prefixes, a prefix-SID sub-TLV within a ISIS SID or label binding TLV in that instance. The flooding scope of the TLV from the mapping server is determined as explained above. No further check of the reachability of that prefix in the mapping server route table is performed. Additionally, no check is performed if the SID index is a duplicate of an existing prefix in the local IGP instance database or if the SID index is out of range with the local SRGB.

The no form of this command deletes the range of node SIDs beginning with the specified index value.

Parameters

index

Specifies the node SID index for the IS-IS prefix that is advertised in a SID/Label Binding TLV.

Values

0 to 4294967295

value

Specifies the node SID range for the IS-IS prefix that is advertised in a SID/Label Binding TLV.

Values

0 to 65535

ip-address/mask

Specifies the IP address and mask.

Values

ip-address: a.b.c.d. (host bits must be 0)

mask: 0 to 32

ip-address netmask

Specifies the IP address netmask.

Values

a.b.c.d. (network bits all 1 and host bits all 0)

set-flags

Specifies the flooding scope of the SID/Label binding TLV.

Default

S-flag clear

The TLV is not leaked by routers receiving the mapping server advertisement

level {1 | 2| 1/2}

Configures the mapping server own flooding scope for the generated SID/Label binding TLV.

Default

1/2

clear-n-flag

Specifies whether the node-sid flag (N-flag) should be cleared in a SID Label Binding TLV.

Platforms

All

sid-map

Syntax

sid-map node-sid index index-value [range range-value] prefix ip-address/mask [netmask]

sid-map node-sid index index-value [range range-value] prefix ip-address/mask [netmask] scope {area area-id | as}

no sid-map node-sid index index-value

Context

[Tree] (config>router>ospf>segm-rtng>mapping-server sid-map)

Full Context

configure router ospf segment-routing mapping-server sid-map

Description

This command configures the Segment Routing mapping server database in OSPF.

The user enters the node SID index for one or a range of prefixes by specifying the first index value and optionally a range value. The default value for the range option is 1. Only the first prefix in a consecutive range of prefixes must be entered. If the user enters the first prefix with a mask lower than 32, the OSPF Extended Prefix Range TLV is advertised but a router which receives it will not resolve SID and instead originates a trap.

The user specifies the mapping server own flooding scope for the generated OSPF Extended Prefix Range TLV using the scope option. There is no default value. If the scope is a specific area, then the TLV is flooded only in that area.

An ABR that propagates an intra-area OSPF Extended Prefix Range TLV flooded by the mapping server in that area into other areas, sets the inter-area flag (IA-flag). The ABR also propagates the TLV if received with the inter-area flag set from other ABR nodes but only from the backbone to leaf areas and not vice-versa. However, if the exact same TLV is advertised as an intra-area TLV in a leaf area, the ABR will not flood the inter-area TLV into that leaf area.

Note:

SR OS does not leak this TLV between OSPF instances.

Each time a prefix or a range of prefixes is configured in the SR mapping database in any routing instance, the router issues for this prefix, or range of prefixes, a prefix-SID sub-TLV within a OSPF Extended Prefix Range TLV in that instance. The flooding scope of the TLV from the mapping server is determined as previously explained. No further check of the reachability of that prefix in the mapping server route table is performed and no check if the SID index is duplicate with some existing prefix in the local IGP instance database or if the SID index is out of range with the local SRGB.

The no form of this command deletes the range of node SIDs beginning with the specified index value.

Default

no prefix-sid-range

Parameters

index index-value

Specifies the index.

Values

0 to 4294967295

range range-value

Specifies the range.

Values

1 to 65535

prefix ip-address/mask

Specifies the IP address in dotted decimal notation.

Values

ip-address/mask:

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

mask: 0 to 132

netmask

Specifies the netmask.

Values

netmask — a.b.c.d (network bits all 1 and host bits all 0)

area area-id

Configures the mapping server own flooding scope for the generated OSPF Extended Prefix Range TLV.

Values

ip-address | 0 to 4294967295

Platforms

All

sid-protection

sid-protection

Syntax

[no] sid-protection

Context

[Tree] (config>router>isis>interface sid-protection)

Full Context

configure router isis interface sid-protection

Description

This command enables or disables adjacency SID protection by LFA and remote LFA.

While LFA and remote LFA Fast-Reroute (FRR) protection is enabled for all node SIDs and local adjacency SIDs when the user enables the loopfree-alternates option in IS-IS or OSPF at the LER and LSR, there are applications where the user wants traffic to never divert from the strict hop computed by CSPF for a SR-TE LSP. In that case, the user can disable protection for all adjacency SIDs formed over a given network IP interface using this command.

The protection state of an adjacency SID is advertised in the B-FLAG of the IS-IS or OSPF Adjacency SID sub-TLV.

Default

sid-protection

Platforms

All

sid-protection

Syntax

[no] sid-protection

Context

[Tree] (config>router>ospf>area>interface sid-protection)

Full Context

configure router ospf area interface sid-protection

Description

This command enables or disables adjacency SID protection by LFA and remote LFA.

LFA and remote LFA Fast-Reroute (FRR) protection is enabled for all node SIDs and local adjacency SIDs when the user enables the loopfree-alternate option in IS-IS or OSPF at the LER and LSR. However, may be applications where the user never wants traffic to divert from the strict hop computed by CSPF for an SR-TE LSP. In this case, the user can disable protection for all adjacency SIDs formed over a particular network IP interface using this command.

The protection state of an adjacency SID is advertised in the B-FLAG of the IS-IS or OSPF Adjacency SID sub-TLV.

Default

sid-protection

Platforms

All

signal-label

signal-label

Syntax

signal-label value

no signal-label

Context

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

Full Context

configure port sonet-sdh path signal-label

Description

This command sets the C2 byte value. The purpose of this byte is to communicate the payload type being encapsulated by SONET framing.

This command is supported on TDM satellite.

Default

signal-label 0xcf

Parameters

value

Specifies the C2 byte value, expressed as a decimal integer or a value in hex format.

Values

1 to 254 or 0x01 to 0xfe

Platforms

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

signal-mode

signal-mode

Syntax

signal-mode {cas}

no signal-mode

Context

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

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

Full Context

configure port tdm ds1 signal-mode

configure port tdm e1 signal-mode

Description

This command activates the signal mode on the channel. When enabled, it uses routing information to direct the payload of voice or data to its destination.

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

Default

no signal-mode

Parameters

cas

Specifies channel associated signaling.

Platforms

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

signaling

signaling

Syntax

signaling signaling

Context

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

Full Context

configure service epipe spoke-sdp-fec signaling

Description

This command enables a user to configure this router as the active or passive T-PE for signaling this MS-PW, or to automatically select whether this T-PE is active or passive based on the prefix. In an active role, this endpoint initiates MS-PW signaling without waiting for a T-LDP label mapping message to arrive from the far end T-PE. In a passive role, it will wait for the initial label mapping message from the far end before sending a label mapping for this end of the PW. In auto mode, if the SAII has the greater prefix value, then the router will initiate MS-PW signaling without waiting for a label mapping message from the far end. However, if the TAII has the greater value prefix, then the router will assume that the far end T-PE will initiate MS-PW signaling and will wait for that label mapping message before responding with a T-LDP label mapping message for the MS-PW in the reverse direction.

The no form of this command means that the router T-PE automatically selects the which router will initiate MS-PW signaling based on the prefix values configured in the SAII and TAII of the spoke SDP, as previously described.

Default

signaling auto

Parameters

signaling

Configures this router as the active T-PE for signaling this MS-PW.

Values

auto, master

Platforms

All

signaling

Syntax

signaling {off | tldp | bgp}

Context

[Tree] (config>service>sdp signaling)

Full Context

configure service sdp signaling

Description

This command specifies the signaling protocol used to obtain the ingress and egress pseudowire labels in frames transmitted and received on the SDP. When signaling is off then labels are manually configured when the SDP is bound to a service. The signaling value can only be changed while the administrative status of the SDP is down. Additionally, the signaling can only be changed on an SDP if that SDP is not in use by BGP-AD or BGP-VPLS. BGP signaling can only be enabled if that SDP does not already have pseudowires signaled over it.

Note:

If the tldp option is selected as the mechanism for exchanging service labels over an MPLS or GRE SDP and the T-LDP session is automatically established, an explicit T-LDP session that is subsequently configured takes precedence over the automatic T-LDP session. However, if the explicit, manually-configured session is then removed, the system does not revert to the automatic session and the automatic session is also deleted. To address this, recreate the T-LDP session by disabling and re-enabling the SDP using the shutdown and no shutdown commands.

The no form of this command is not applicable. To modify the signaling configuration, the SDP must be administratively shut down and then the signaling parameter can be modified and re-enabled.

Default

signaling tldp

Parameters

off

Ingress and egress signal auto-labeling is not enabled. If this parameter is selected, then each service using the specified SDP must manually configure VPN labels. This configuration is independent of the SDP’s transport type, GRE, MPLS (RSVP or LDP).

tldp

Ingress and egress pseudowire signaling using T-LDP is enabled. Default value used when BGP AD automatically instantiates the SDP.

bgp

Ingress and egress pseudowire signaling using BGP is enabled. Default value used when BGP VPLS automatically instantiates the SDP.

Platforms

All

signature-list

signature-list

Syntax

signature-list name

no signature-list

Context

[Tree] (config>system>security>tls>client-tls-profile signature-list)

Full Context

configure system security tls client-tls-profile signature-list

Description

This command assigns an existing TLS 1.3 signature list to the TLS client profile.

The no form of this command removes the signature list from the client profile.

Default

no signature-list

Parameters

name

Specifies the name of the signature list, up to 32 characters.

Platforms

All

signature-list

Syntax

signature-list name

no signature-list

Context

[Tree] (config>system>security>tls>server-tls-profile signature-list)

Full Context

configure system security tls server-tls-profile signature-list

Description

This command assigns an existing TLS 1.3 signature list to the TLS server profile.

The no form of this command removes the signature list from the server profile.

Default

no signature-list

Parameters

name

Specifies the name of the signature list, up to 32 characters.

Platforms

All

significant-change

significant-change

Syntax

significant-change delta

no significant-change

Context

[Tree] (config>subscr-mgmt>acct-plcy>cr significant-change)

Full Context

configure subscriber-mgmt radius-accounting-policy custom-record significant-change

Description

This command configures the significant change required to generate the record.

Parameters

delta

Specifies the delta change (significant change) that is required for the custom record to be generated.

Values

0 to 4294967295

Platforms

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

significant-change

Syntax

significant-change delta

no significant-change

Context

[Tree] (config>app-assure>rad-acct-plcy significant-change)

Full Context

configure application-assurance radius-accounting-policy significant-change

Description

This command configures the significant change required to generate the record.

The no form of this command reverts to the default.

Default

no significant-change

Parameters

delta

Specifies the delta change (significant change) that is required for the charging-group counts to be included in the RADIUS Accounting VSAs.

Values

0 to 4294967295

Platforms

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

significant-change

Syntax

significant-change delta

no significant-change

Context

[Tree] (config>log>acct-policy>cr significant-change)

Full Context

configure log accounting-policy custom-record significant-change

Description

This command configures the significant change required to generate the record. The custom record is only generated when the change in the reference counters equals or exceeds the configured (non-zero) significant change value. Only the reference counters for which there are corresponding counters configured under the related queues and policers are used for the significant change comparison. For reference queues and policers, the change applies to the sum of all configured reference queue and policer counters. When no reference counters are configured or significant-change is zero, the significant change reporting is not active.

Default

significant-change 0

Parameters

delta

Specifies the delta change (significant change) that is required for the custom record to be written to the XML file.

Values

0 to 4294967295 (For custom-record-aa-sub only values 0 or 1 are supported.)

Platforms

All

single-device

single-device

Syntax

single-device

Context

[Tree] (config>app-assure>group>tether-detect single-device)

Full Context

configure application-assurance group tethering-detection single-device

Description

Commands in this context configure the single-device fields and expected TTL values for flow-level tethering detection.

Platforms

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

single-fiber

single-fiber

Syntax

[no] single-fiber

Context

[Tree] (config>port>ethernet single-fiber)

[Tree] (config>port>sonet-sdh single-fiber)

Full Context

configure port ethernet single-fiber

configure port sonet-sdh single-fiber

Description

This command enables packet gathering and redirection of IP packets from a single fiber (RX) port of the Ethernet or SONET/SDH interface and redistributes packets to other interfaces through either static routes or policy-based forwarding.

This parameter can be applied in conjunction with the strip-label command. If they are applied together, the port must have the single-fiber option configured before it can be associated with an interface that is configured with the strip-label option.

Once a port is configured with single-fiber, traffic will no longer be transmitted out of that port. This command can be used in conjunction with strip-label.

Default

no single-fiber

Platforms

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

single-mac

single-mac

Syntax

[no] single-mac

Context

[Tree] (config>service>ies>sub-if>grp-if>sap>static-host-mgmt>mac-learning-options single-mac)

[Tree] (config>service>vprn>sub-if>grp-if>sap>static-host-mgmt>mac-learning-options single-mac)

Full Context

configure service ies subscriber-interface group-interface sap static-host-mgmt mac-learning-options single-mac

configure service vprn subscriber-interface group-interface sap static-host-mgmt mac-learning-options single-mac

Description

This command controls how the SAP learns the IPv6 static host MAC address. Enabling this command indicates that this particular SAP only has one subscriber and only has one MAC address for all hosts. With this parameter enabled, the subscriber’s NS and RS source MAC address is used to automatically populate the subscriber MAC address. To allow this auto-populate behavior, the subscriber’s NS and RS source IP must be of type link local address.

Platforms

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

single-sfm-overload

single-sfm-overload

Syntax

single-sfm-overload [holdoff-time holdoff-time]

no single-sfm-overload

Context

[Tree] (config>service>vprn single-sfm-overload)

Full Context

configure service vprn single-sfm-overload

Description

This command configures OSPF, OSPFv3 and IS-IS to set overload when the router has fewer than the full set of SFMs functioning, which reduces forwarding capacity. Setting overload enables a router to still participate in exchanging routing information, but routes all traffic away from it.

The conditions to set overload are as follows:

  • 7950 XRS-20, 7750 SR-12/SR-7, and 7450 ESS-12/ESS-7 platforms: if an SF/CPMs fails, the protocol will set the overload

  • 7950-40 XRS and 7750 SR-12e platforms: if two SFMs fail (a connected pair on the XRS-40) the protocol will set the overload

The no form of this command configures the router to not set overload if an SFM fails.

Default

no single-sfm-overload

Parameters

holdoff-time

Specifies the delay between detecting SFM failures and setting overload.

Values

1 to 600 seconds

Default

0 seconds

Platforms

7450 ESS, 7750 SR-1, 7750 SR-7/12/12e, 7750 SR-a, 7750 SR-e, 7750 SR-2s, 7750 SR-2se, 7750 SR-7s, 7750 SR-14s, 7950 XRS, VSR

single-sfm-overload

Syntax

single-sfm-overload [holdoff-time holdoff-time]

no single-sfm-overload

Context

[Tree] (config>router single-sfm-overload)

Full Context

configure router single-sfm-overload

Description

This command configures OSPF, OSPFv3 and IS-IS to set overload when the router has fewer than the full set of SFMs functioning, which reduces forwarding capacity. Setting overload enables a router to still participate in exchanging routing information, but routes all traffic away from it.

The conditions to set overload are as follows:

  • 7750 SR-12/SR-7 and 7450 ESS-12/ESS-7 platforms: protocol sets overload if one of the SF/CPMs fails

  • 7750 SR-12e and 7950 XRS platforms: protocol sets overload if two SFMs fail (two SFMs belonging to different SFM pairs on the XRS-40)

The no form of this command configures the router to not set overload if an SFM fails.

Default

no single-sfm-overload

Parameters

holdoff-time

Specifies the delay between detecting SFM failures and setting overload.

Values

1 to 600 seconds

Default

0 seconds

Platforms

7450 ESS, 7750 SR-1, 7750 SR-7/12/12e, 7750 SR-a, 7750 SR-e, 7750 SR-2s, 7750 SR-2se, 7750 SR-7s, 7750 SR-14s, 7950 XRS, VSR

single-sub-parameters

single-sub-parameters

Syntax

single-sub-parameters

Context

[Tree] (config>subscr-mgmt>msap-policy>sub-sla-mgmt single-sub-parameters)

Full Context

configure subscriber-mgmt msap-policy sub-sla-mgmt single-sub-parameters

Description

Commands in this context configure single subscriber MSAP parameters.

Platforms

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

single-sub-parameters

Syntax

single-sub-parameters

Context

[Tree] (config>service>ies>if>sap>sub-sla-mgmt single-sub-parameters)

[Tree] (config>service>vprn>sub-if>grp-if>sap>sub-sla-mgmt single-sub-parameters)

[Tree] (config>service>vpls>sap>sub-sla-mgmt single-sub-parameters)

[Tree] (config>service>ies>sub-if>grp-if>sap>sub-sla-mgmt single-sub-parameters)

Full Context

configure service ies interface sap sub-sla-mgmt single-sub-parameters

configure service vprn subscriber-interface group-interface sap sub-sla-mgmt single-sub-parameters

configure service vpls sap sub-sla-mgmt single-sub-parameters

configure service ies subscriber-interface group-interface sap sub-sla-mgmt single-sub-parameters

Description

Commands in this context configure single subscriber SAP parameters.

Platforms

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

sip

sip

Syntax

[no] sip

Context

[Tree] (config>service>nat>firewall-policy>alg sip)

[Tree] (config>service>nat>up-nat-policy>alg sip)

[Tree] (config>service>nat>nat-policy>alg sip)

Full Context

configure service nat firewall-policy alg sip

configure service nat up-nat-policy alg sip

configure service nat nat-policy alg sip

Description

This command enables SIP ALG.

The no form of the command disables SIP ALG.

Default

no sip

Platforms

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

  • configure service nat firewall-policy alg sip

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

  • configure service nat nat-policy alg sip
  • configure service nat up-nat-policy alg sip

sip

Syntax

sip [hrs hours] [min minutes] [ sec seconds]

no sip

Context

[Tree] (config>service>nat>firewall-policy>timeouts sip)

[Tree] (config>service>nat>up-nat-policy>timeouts sip)

[Tree] (config>service>nat>nat-policy>timeouts sip)

Full Context

configure service nat firewall-policy timeouts sip

configure service nat up-nat-policy timeouts sip

configure service nat nat-policy timeouts sip

Description

This command configures the SIP inactive media timeout.

Default

sip min 2

Parameters

hours

Specifies the SIP inactive media timeout, in hours.

Values

1 to 2

minutes

Specifies the SIP inactive media timeout, in minutes.

Values

1 to 59

seconds

Specifies the SIP inactive media timeout, in seconds.

Values

1 to 59

Platforms

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

  • configure service nat firewall-policy timeouts sip

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

  • configure service nat nat-policy timeouts sip
  • configure service nat up-nat-policy timeouts sip

site

site

Syntax

site name [create]

no site name

Context

[Tree] (config>service>vpls site)

Full Context

configure service vpls site

Description

This command configures a VPLS site.

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

Parameters

name

Specifies a site name up to 32 characters in length.

create

This keyword is mandatory while creating a VPLS site.

Platforms

All

site

Syntax

site name [create]

no site name

Context

[Tree] (config>service>epipe site)

Full Context

configure service epipe site

Description

This command configures a Epipe site.

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

Parameters

name

Specifies a site name up to 32 characters in length.

create

This keyword is mandatory while creating a Epipe service.

Platforms

All

site-activation-timer

site-activation-timer

Syntax

site-activation-timer seconds

no site-activation-timer

Context

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

Full Context

configure redundancy bgp-multi-homing site-activation-timer

Description

This command defines the amount of time the service manager will keep the local sites in standby status, waiting for BGP updates from remote PEs before running the DF election algorithm to decide whether the site should be unblocked. The timer is started when one of the following event occurs only if the site is operationally up:

  • Manual site activation using "no shutdown” at site-id level or at member object(s) level (for example, SAP(s) or PW(s)

  • Site activation after a failure

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

Default

no site-activation-timer

Parameters

seconds

Specifies the timer, in seconds.

Values

1 to 100

Platforms

All

site-activation-timer

Syntax

site-activation-timer seconds

no site-activation-timer

Context

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

Full Context

configure redundancy bgp-multi-homing site-activation-timer

Description

This command defines the amount of time the service manager will keep the local sites in standby status, waiting for BGP updates from remote PEs before running the DF election algorithm to decide whether the site should be unblocked. The timer is started when one of the following events occurs if the site is operationally up:

  • Manual site activation using the no shutdown command at site-id level or at member object(s) level (SAP(s) or PW(s))

  • Site activation after a failure

Default

no site-activation-timer

Parameters

seconds

Specifies the standby status in seconds.

Values

0 to 100

Default

2

Platforms

All

site-activation-timer

Syntax

site-activation-timer seconds

no site-activation-timer

Context

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

Full Context

configure service vpls site site-activation-timer

Description

This command configures the time-period the system keeps the local sites in standby status, waiting for BGP updates from remote PEs before running the DF (designated-forwarder) election algorithm to decide whether the site should be unblocked. This timer if terminated if an update is received for which the remote PE has transitioned from DF to non-DF.

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

Default

site-activation-timer 2

Parameters

seconds

Specifies the site activation timer in seconds.

Values

0 to 100

Platforms

All

site-activation-timer

Syntax

site-activation-timer seconds

no site-activation-timer

Context

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

Full Context

configure service epipe site site-activation-timer

Description

This command configures the time-period the system keeps the local sites in standby status, waiting for BGP updates from remote PEs before running the DF (designated-forwarder) election algorithm to decide whether the site should be unblocked. This timer is terminated if an update is received for which the remote PE has transitioned from DF to non-DF.

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

Default

site-activation-timer 2

Parameters

seconds

Specifies the site activation timer in seconds.

Values

0 to 100

Platforms

All

site-id

site-id

Syntax

site-id value

no site-id

Context

[Tree] (config>service>vpls>site site-id)

Full Context

configure service vpls site site-id

Description

This command configures the identifier for the site in this service.

Parameters

value

Specifies the site identifier.

Values

1 to 65535

Platforms

All

site-id

Syntax

site-id value

no site-id

Context

[Tree] (config>service>epipe>site site-id)

Full Context

configure service epipe site site-id

Description

This command configures the identifier for the site in this service. It must match between services but it is local to the service.

Parameters

value

Specifies the site identifier.

Values

1 to 65535

Platforms

All

site-min-down-timer

site-min-down-timer

Syntax

site-min-down-timer seconds

no site-min-down-timer

Context

[Tree] (config>redundancy>bgp-multi-homing site-min-down-timer)

Full Context

configure redundancy bgp-multi-homing site-min-down-timer

Description

This command configures the BGP multi-homing site minimum down time. When this value is set and the site goes operationally down, it remains operationally down for at least the length of time configured by this timer, regardless of whether other state changes might cause the site to go operationally up. This timer is restarted every time the site transitions from operationally up to down.

This timer is optimized in the following circumstances:

  • If the site goes down on the DF but there are no BGP multi-homing peers with the same site in an up state, this timer is not used.

  • If the site goes down on the DF but there are no active BGP multi-homing peers, this timer is not used.

  • If this timer is active and a BGP multihoming update is received from the DF indicating its site is down, this timer is immediately terminated and the BGP multihoming algorithm is triggered to determine whether this PE should become the DF.

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

Default

no site-min-down-timer

Parameters

seconds

Specifies the time, in seconds, that a BGP multi-homing site remains operationally down after a transition from up to down.

Values

1 to 100

Platforms

All

site-min-down-timer

Syntax

site-min-down-timer min-down-time

no site-min-down-timer

Context

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

Full Context

configure service vpls site site-min-down-timer

Description

This command configures the BGP multi-homing site minimum down time. When set to a non-zero value, if the site goes operationally down it will remain operationally down for at least the length of time configured for the site-min-down-timer, regardless of whether other state changes would have caused it to go operationally up. This timer is restarted every time that the site transitions from up to down. Setting this parameter to zero allows the minimum down timer to be disabled for this service.

The above operation is optimized in the following circumstances:

  • If the site goes down on the designated forwarder but there are no BGP multi-homing peers with the same site in an operationally up state, then the site-min-down-timer is not started and is not used.

  • If the site goes down on the designated forwarder but there are no active BGP multi-homing peers, then the site-min-down-timer is not started and is not used.

  • If the site-min-down-timer is active and a BGP multi-homing update is received from the designated forwarder indicating its site has gone down, the site-min-down-timer is immediately terminated and this PE becomes the designated forwarder if the BGP multi-homing algorithm determines it should be the designated forwarder.

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

Default

Taken from the value of site-min-down-timer configured for Multi-Chassis BGP multi-homing under the config>redundancy>bgp-multi-homing context.

Parameters

min-down-time

Specifies the time, in seconds, that a BGP multi-homing site remains operationally down after a transition from up to down.

Values

0 to 100 seconds

Platforms

All

site-min-down-timer

Syntax

site-min-down-timer min-down-time

no site-min-down-timer

Context

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

Full Context

configure service epipe site site-min-down-timer

Description

This command configures the BGP multi-homing site minimum down time. When set to a non-zero value, if the site goes operationally down it will remain operationally down for at least the length of time configured for the site-min-down-timer, regardless of whether other state changes would have caused it to go operationally up. This timer is restarted every time that the site transitions from up to down. Setting this parameter to zero allows the minimum down timer to be disabled for this service.

The preceding operation is optimized in the following circumstances:

  • If the site goes down on the designated forwarder but there are no BGP multi-homing peers with the same site in an operationally up state, then the site-min-down-timer is not started and is not used.

  • If the site goes down on the designated forwarder but there are no active BGP multi-homing peers, then the site-min-down-timer is not started and is not used.

  • If the site-min-down-timer is active and a BGP multi-homing update is received from the designated forwarder indicating its site has gone down, the site-min-down-timer is immediately terminated and this PE becomes the designated forwarder if the BGP multi-homing algorithm determines it should be the designated forwarder.

The no form of this command reverts to default value.

Default

Taken from the value of site-min-down-timer configured for Multi-Chassis BGP multi-homing under the config>redundancy>bgp-multi-homing context.

Parameters

min-down-time

Specifies the time, in seconds, that a BGP multi-homing site remains operationally down after a transition from up to down.

Values

0 to 100

Platforms

All

site-preference

site-preference

Syntax

site-preference preference-value

no site-preference

Context

[Tree] (config>service>epipe>site site-preference)

Full Context

configure service epipe site site-preference

Description

This command defines the value to advertise in the VPLS preference field of the BGP VPWS and BGP Multi-homing NLRI extended community. This value can be changed without having to shutdown the site itself. The site-preference is only applicable to VPWS services.

When not configured, the default is zero, indicating that the VPLS preference is not in use.

Default

no site-preference, value=0

Parameters

preference-value

Specifies the preference value to advertise in the NLRI L2 extended community for this site.

Values

1 to 65535

primary

Sets the site-preference to 65535.

backup

Sets the site-preference to 1.

Platforms

All

size

size

Syntax

size queue-set-size allocation-weight weight

Context

[Tree] (config>qos>fp-resource-policy>aggregate-shapers>queue-sets size)

Full Context

configure qos fp-resource-policy aggregate-shapers queue-sets size

Description

This command configures the size and allocation weight for the specified queue set. The available queue sets are distributed based on the allocation weight between different queue sets.

Parameters

queue-set-size

Specifies the size of the queue sets.

Values

2 to 8

weight

Specifies the allocation weight of the queue set.

Values

0 to 100

Platforms

7750 SR-1, 7750 SR-s

size

Syntax

size cache-size

Context

[Tree] (config>app-assure>group>dns-ip-cache>ip-cache size)

Full Context

configure application-assurance group dns-ip-cache ip-cache size

Description

This command configures the maximum number of entries in the cache.

Default

size 10

Parameters

cache-size

Specifies the maximum number of IP addresses that can be stored in the cache.

Values

10 to 32000

Default

10

Platforms

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

size

Syntax

size url-list-size

Context

[Tree] (config>app-assure>group>url-list size)

Full Context

configure application-assurance group url-list size

Description

This command specifies the size of the URL list that can be filtered. The size can be set to either standard or extended. Configuring the specified url-list as extended provides support for filtering on a larger number of URLs.

Default

size standard

Parameters

url-list-size

Specifies the size of the AA url-list for URL filtering.

Values

standard, extended

Platforms

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

size

Syntax

size octets

no size

Context

[Tree] (config>saa>test>type-multi-line>lsp-trace>sr-policy size)

[Tree] (config>saa>test>type-multi-line>lsp-ping>sr-policy size)

[Tree] (config>saa>test>type-multi-line>lsp-ping size)

Full Context

configure saa test type-multi-line lsp-trace sr-policy size

configure saa test type-multi-line lsp-ping sr-policy size

configure saa test type-multi-line lsp-ping size

Description

This command configures the MPLS echo request packet size.

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

Default

size 1

Parameters

octets

Specifies the size in octets. The request payload is padded with zeros to the specified size.

Values

1 to 9786

Default

1

Platforms

All

size

Syntax

size octets

no size

Context

[Tree] (config>test-oam>icmp>ping-template size)

Full Context

configure test-oam icmp ping-template size

Description

This command configures the size of the Data field (in other words, padding) of the outgoing ICMP echo packet. Minimum packet sizes should be used to test connectivity. Larger packet size should only be used if there is a requirement to spot-check large packet size issues on a very limited number of tests and should not be used for normal connectivity testing. Packet sizes should never be configured to require fragmentation anywhere along the path. Exceeding these recommendations will negatively affect the scale and performance of icmp ping check testing.

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

Default

size 56

Parameters

octets

Specifies the size of the ICMP echo ping padding field, in octets.

Values

12 to 9786

Platforms

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

size

Syntax

size number

Context

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

Full Context

configure system management-interface cli md-cli environment history size

Description

This command configures the maximum size of the command history.

Parameters

number

Specifies the maximum size of the command history. A value of 0 disables the command history.

Values

0 to 1000

Platforms

All

size-a

size-a

Syntax

size-a bytes

Context

[Tree] (config>test-oam>sath>frame-size-tmpl size-a)

Full Context

configure test-oam service-activation-testhead frame-size-template size-a

Description

This command configures the Ethernet frame size for the letter "a”.

Parameters

bytes

Specifies the Ethernet frame value, in bytes.

Values

64 to 9212

Default

64

Platforms

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

size-b

size-b

Syntax

size-b bytes

Context

[Tree] (config>test-oam>sath>frame-size-tmpl size-b)

Full Context

configure test-oam service-activation-testhead frame-size-template size-b

Description

This command configures the Ethernet frame size for the letter "b”.

Parameters

bytes

Specifies the Ethernet frame value, in bytes.

Values

64 to 9212

Default

128

Platforms

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

size-c

size-c

Syntax

size-c bytes

Context

[Tree] (config>test-oam>sath>frame-size-tmpl size-c)

Full Context

configure test-oam service-activation-testhead frame-size-template size-c

Description

This command configures the Ethernet frame size for the letter "c”.

Parameters

bytes

Specifies the Ethernet frame value, in bytes.

Values

64 to 9212

Default

256

Platforms

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

size-d

size-d

Syntax

size-d bytes

Context

[Tree] (config>test-oam>sath>frame-size-tmpl size-d)

Full Context

configure test-oam service-activation-testhead frame-size-template size-d

Description

This command configures the Ethernet frame size for the letter "d”.

Parameters

bytes

Specifies the Ethernet frame value, in bytes.

Values

64 to 9212

Default

512

Platforms

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

size-e

size-e

Syntax

size-e bytes

Context

[Tree] (config>test-oam>sath>frame-size-tmpl size-e)

Full Context

configure test-oam service-activation-testhead frame-size-template size-e

Description

This command configures the Ethernet frame size the letter "e”.

Parameters

bytes

Specifies the Ethernet frame value, in bytes.

Values

64 to 9212

Default

1024

Platforms

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

size-f

size-f

Syntax

size-f bytes

Context

[Tree] (config>test-oam>sath>frame-size-tmpl size-f)

Full Context

configure test-oam service-activation-testhead frame-size-template size-f

Description

This command configures the Ethernet frame size for the letter "f”.

Parameters

bytes

Specifies the Ethernet frame value, in bytes.

Values

64 to 9212

Default

1280

Platforms

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

size-g

size-g

Syntax

size-g bytes

Context

[Tree] (config>test-oam>sath>frame-size-tmpl size-g)

Full Context

configure test-oam service-activation-testhead frame-size-template size-g

Description

This command configures the Ethernet frame size for the letter "g”.

Parameters

bytes

Specifies the Ethernet frame value, in bytes.

Values

64 to 9212

Default

1518

Platforms

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

size-h

size-h

Syntax

size-h bytes

Context

[Tree] (config>test-oam>sath>frame-size-tmpl size-h)

Full Context

configure test-oam service-activation-testhead frame-size-template size-h

Description

This command configures the Ethernet frame size for the letter "h”.

Parameters

bytes

Specifies the Ethernet frame value, in bytes.

Values

64 to 9212

Default

9212

Platforms

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

size-limit

size-limit

Syntax

size-limit limit-value

no size-limit

Context

[Tree] (config>call-trace>location size-limit)

Full Context

configure call-trace location size-limit

Description

This command limits the total size of call-trace files on the specified compact flash card.

The no form of this command removes the size restriction.

Default

size-limit 1000

Parameters

limit-value

Specifies the total size of call-trace files on the specified compact flash card, in Mbytes.

Values

1 to 65536

Platforms

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

size-limit

Syntax

size-limit limit-value

Context

[Tree] (config>call-trace>trace-profile size-limit)

Full Context

configure call-trace trace-profile size-limit

Description

This command specifies a maximum of how big a trace may grow before it is stopped.

Default

size-limit 10

Parameters

limit-value

Specifies the maximum data volume generated by a single call trace job to the output in megabytes. After reaching the limit the call trace job for a given host is automatically terminated.

Values

1 to 1000

Platforms

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

size-u

size-u

Syntax

size-u bytes

Context

[Tree] (config>test-oam>sath>frame-size-tmpl size-u)

Full Context

configure test-oam service-activation-testhead frame-size-template size-u

Description

This command configures the Ethernet frame size for the letter "u”, which is user-defined.

Parameters

bytes

Specifies the Ethernet frame value, in bytes.

Values

64 to 9212

Default

2000

Platforms

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

skip-gtp-ipv4-alloc

skip-gtp-ipv4-alloc

Syntax

[no] skip-gtp-ipv4-alloc

Context

[Tree] (config>subscr-mgmt>gtp>apn-policy>apn skip-gtp-ipv4-alloc)

Full Context

configure subscriber-mgmt gtp apn-policy apn skip-gtp-ipv4-alloc

Description

This command enables the ability to skip IPv4 address assignment using a GTP session setup response when PCO "allocation via NAS" is not present in a GTP session creation request. Without this configuration, IPv4 address allocation is done using GTP session setup response, even in absence of the PCO "allocation via NAS" in a GTP session setup request.

The no form of this command reverts to IPv4 address allocation using GTP.

Platforms

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

skip-ttl-decrement

skip-ttl-decrement

Syntax

[no] skip-ttl-decrement

Context

[Tree] (config>filter>gre-tun-tmp>ipv4 skip-ttl-decrement)

Full Context

configure filter gre-tunnel-template ipv4 skip-ttl-decrement

Description

This command enables an option to not decrement the TTL of the IP packet matching the IPv4/IPv6 filter, when it is encapsulated into the GRE tunnel header.

The no form of this command disables this option (default). This results in the matching of IP packet’s TTL field to be decremented before it is encapsulated in the GRE tunnel header.

Platforms

All

sla-profile

sla-profile

Syntax

[no] sla-profile

Context

[Tree] (config>subscr-mgmt>acct-plcy>include-radius-attribute sla-profile)

Full Context

configure subscriber-mgmt radius-accounting-policy include-radius-attribute sla-profile

Description

This command specifies that SLA profile attributes should be included into RADIUS accounting messages.

The no form of this command reverts to the default.

Platforms

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

sla-profile

Syntax

sla-profile sla-profile-name

no sla-profile

Context

[Tree] (config>service>ies>if>sap>static-host sla-profile)

[Tree] (config>service>vpls>sap>static-host sla-profile)

[Tree] (config>service>ies>sub-if>grp-if>sap>static-host sla-profile)

[Tree] (config>service>vprn>sub-if>grp-if>sap>static-host sla-profile)

[Tree] (config>service>vprn>if>sap>static-host sla-profile)

Full Context

configure service ies interface sap static-host sla-profile

configure service vpls sap static-host sla-profile

configure service ies subscriber-interface group-interface sap static-host sla-profile

configure service vprn subscriber-interface group-interface sap static-host sla-profile

configure service vprn interface sap static-host sla-profile

Description

This command specifies an existing SLA profile name to be associated with the static subscriber host. The SLA profile is configured in the config>subscr-mgmt>sla-profile context.

The no form of this command reverts to the default.

Parameters

sla-profile-name

Specifies the SLA profile name.

Platforms

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

sla-profile

Syntax

sla-profile sla-profile-name [create]

no sla-profile sla-profile-name

Context

[Tree] (config>subscr-mgmt sla-profile)

Full Context

configure subscriber-mgmt sla-profile

Description

This command configures an SLA profile mapping. Hosts associated with a subscriber are subdivided into Service Level Agreement (SLA) profiles. For each subscriber host an SLA profile can be specified. For a subscriber host, the SLA profile determines:

  • The QoS-policies to use

    • The classification

    • The queues

    • The queue mapping

  • The IP filters to use

The SLA profile also has the attribute host-limits which limits the total number of hosts (belonging to the same subscriber) on a certain SAP that can be using this SLA profile.

The no form of this command reverts to the default.

Parameters

sla-profile-name

Specifies the name of the SLA profile.

create

Keyword used to create the SLA profile.

Platforms

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

sla-profile-map

sla-profile-map

Syntax

sla-profile-map

Context

[Tree] (config>subscr-mgmt>sub-ident-pol sla-profile-map)

Full Context

configure subscriber-mgmt sub-ident-policy sla-profile-map

Description

Commands in this context configure SLA profile mapping parameters.

Platforms

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

sla-profile-map

Syntax

sla-profile-map

Context

[Tree] (config>subscr-mgmt>sub-prof sla-profile-map)

Full Context

configure subscriber-mgmt sub-profile sla-profile-map

Description

Commands in this context configure SLA profile mapping.

Platforms

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

sla-profile-string

sla-profile-string

Syntax

sla-profile-string sla-profile-string

no sla-profile-string

Context

[Tree] (config>subscr-mgmt>loc-user-db>ppp>host>ident-strings sla-profile-string)

[Tree] (config>subscr-mgmt>loc-user-db>ipoe>host>ident-strings sla-profile-string)

Full Context

configure subscriber-mgmt local-user-db ppp host identification-strings sla-profile-string

configure subscriber-mgmt local-user-db ipoe host identification-strings sla-profile-string

Description

This command specifies the SLA profile string which is encoded in the identification strings.

The no form of this command returns to the default.

Parameters

sla-profile-string

Specifies the SLA profile string, up to 16 characters.

Platforms

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

sla-profile-string

Syntax

sla-profile-string string

no sla-profile-string

Context

[Tree] (config>subscr-mgmt>vrgw>brg>brg-profile sla-profile-string)

Full Context

configure subscriber-mgmt vrgw brg brg-profile sla-profile-string

Description

This command configures the SLA profile string which will be used as a default for SLA-profile lookup. This string can be overridden during BRG or host authentication.

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

Default

no sla-profile-string

Parameters

string

Specifies the string to use to look up the subscriber profile.

Platforms

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

slaac

slaac

Syntax

slaac

Context

[Tree] (config>service>ies>sub-if>wlan-gw>pool-manager>dhcp6-client slaac)

[Tree] (config>service>vprn>sub-if>wlan-gw>pool-manager>dhcp6-client slaac)

Full Context

configure service ies subscriber-interface wlan-gw pool-manager dhcpv6-client slaac

configure service vprn subscriber-interface wlan-gw pool-manager dhcpv6-client slaac

Description

This command configures SLAAC for the DHCPv6 client.

Platforms

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

slaac-prefix

slaac-prefix

Syntax

slaac-prefix ipv6-address

no slaac-prefix

Context

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

Full Context

configure subscriber-mgmt wlan-gw ue-query slaac-prefix

Description

This command enables matching on UEs with the specified SLAAC prefix.

The no form of this command disables matching on the SLAAC prefix.

Default

no slaac-prefix

Parameters

ipv6-address

Specifies the SLAAC prefix.

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 to FFFF]H

d: [0 to 255]D

Platforms

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

sleep

sleep

Syntax

sleep [seconds]

Context

[Tree] (sleep)

Full Context

sleep

Description

This command causes the console session to pause operation (sleep) for 1 second (default) or for the specified number of seconds.

Default

sleep 1

Parameters

seconds

Specifies the number of seconds for the console session to sleep, expressed as a decimal integer.

Values

1 to 100

Default

1

Platforms

All

slice-size

slice-size

Syntax

slice-size slice-size

no slice-size

Context

[Tree] (config>mirror>mirror-dest slice-size)

Full Context

configure mirror mirror-dest slice-size

Description

This command enables mirrored frame truncation and specifies the maximum size, in bytes, of a mirrored frame that can be transmitted to the mirror destination.

This command enables mirroring larger frames than the destination packet decode equipment can handle. It also allows conservation of mirroring resources by limiting the size of the packet stream through the router and the core network.

When defined, the mirror slice-size creates a threshold that truncates a mirrored frame to a specific size. For example, if the value of 256 bytes is defined, a frame larger than 256 bytes will only have the first 256 bytes transmitted to the mirror destination. The original frame is not affected by the truncation. The mirrored frame size may increase if encapsulation information is added during transmission through the network core or out the mirror destination SAP to the packet/protocol decode equipment.

The actual capability of the router to transmit a sliced or non-sliced frame is also dictated by the mirror destination SDP path-mtu or the mirror destination SAP physical MTU. Packets that require a larger MTU than the mirroring destination supports are discarded if the defined slice-size does not truncate the packet to an acceptable size.

Notes:

  • When configuring IP mirroring, packet slice is rejected as an incorrect option as it will cause IP packets to be rejected by the next hop with an IP header verification error.

  • Slice-size is not supported by CEM encap-types or IP-mirroring.

The no form of this command disables mirrored packet truncation.

Parameters

slice-size

Specifies the number of bytes to which mirrored frames are truncated, expressed as a decimal integer.

Values

128 to 9216

Platforms

All

slm

slm

Syntax

slm [test-id test-id] [create]

no slm

Context

[Tree] (config>oam-pm>session>ethernet slm)

Full Context

configure oam-pm session ethernet slm

Description

This command defines the test ID to be assigned to the synthetic loss test and creates the container to allow the individual test parameters to be configured.

The no form of this command removes the SLM test function from the PM Session.

Parameters

test-id

Specifies the value placed in the 4-byte test ID field of the ETH-SLM PDU.

Values

0 to 2147483647 | auto

auto - automatically assigns a test-id
create

Creates the test.

Platforms

All

slm

Syntax

slm

Context

[Tree] (config>eth-cfm slm)

Full Context

configure eth-cfm slm

Description

This is the container that provides the global configuration parameters for ITU-T Synthetic Loss Measurement (ETH-SL).

Platforms

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

slope-policy

slope-policy

Syntax

slope-policy name

no slope-policy

Context

[Tree] (config>port>network>egress>pool slope-policy)

[Tree] (config>port>access>ingress>pool slope-policy)

[Tree] (config>port>access>egress>pool slope-policy)

Full Context

configure port network egress pool slope-policy

configure port access ingress pool slope-policy

configure port access egress pool slope-policy

Description

This command specifies an existing slope policy which defines high and low priority RED slope parameters and the time average factor. The policy is defined in the config>qos>slope-policy context.

Default

slope-policy default

Parameters

name

Specifies the policy name, a string up to 32 characters.

Platforms

All

slope-policy

Syntax

slope-policy slope-policy-name

no slope-policy

Context

[Tree] (config>card>fp>egress>wred-queue-control slope-policy)

Full Context

configure card fp egress wred-queue-control slope-policy

Description

This command configures WRED slopes within the WRED mega-pool. The WRED slopes in the WRED mega-pool are used when WRED queues are requesting buffers from the mega-pool while they are over their CBS threshold. Once over the CBS threshold, the WRED queue stops receiving buffers from the CBS reserve in the mega-pool and starts competing for buffers in the shared portion of the mega-pool. If the packet resulting in the buffer request is inplus-profile, the packet will be associated with the highplus-slope. In-profile packets are associated with the high slope. Out-of-profile packets are associated with the low slope. Exceed-profile packets are associated with the exceed slope. While the queue is within its CBS threshold, the slopes are ignored.

Within the defined slope-policy, each slope is enabled or disabled (no shutdown or shutdown) and each slope’s geometry is defined as percentages of shared portion depth. If a slope is shutdown, the related traffic uses the minimum of the queue MBS and egress WRED megapool size as a drop tail.

The slope-policy also defines the time average factor (TAF) value that is used to determine how the pool’s weighted average depth is calculated. The higher the factor, the slower the average depth tracks the actual pool depth.

The no form of this command reverts to the default slope policy to the WRED mega-pool.

Default

slope-policy default

Parameters

slope-policy-name

Specifies which slope policy the system should apply to the WRED mega-pool. When slope-policy is not executed, the WRED mega-pool will use the default slope policy. The defined slope policy must already exist or the command will fail. 32 characters maximum.

Platforms

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

slope-policy

Syntax

slope-policy name

no slope-policy

Context

[Tree] (config>card>fp>ingress>network>pool slope-policy)

Full Context

configure card fp ingress network pool slope-policy

Description

This command specifies an existing slope policy which defines high and low priority RED slope parameters and the time average factor. The policy is defined in the config>qos>slope-policy context.

Default

slope-policy default

Parameters

name

Specifies the policy name, a string up to 32 characters.

Platforms

All

slope-policy

Syntax

slope-policy slope-policy-name

no slope-policy

Context

[Tree] (config>isa>aa-grp>qos>egress>from-subscriber>pool slope-policy)

[Tree] (config>isa>aa-grp>qos>egress>to-subscriber>pool slope-policy)

Full Context

configure isa application-assurance-group qos egress from-subscriber pool slope-policy

configure isa application-assurance-group qos egress to-subscriber pool slope-policy

Description

This command specifies an existing slope policy which defines high and low priority RED slope parameters and the time average factor. The slope policy is defined in the config>qos>slope-policy context.

Parameters

slope-policy-name

Specifies the name of the slope policy, up to 32 characters.

Platforms

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

slope-policy

Syntax

slope-policy policy-name

no slope-policy

Context

[Tree] (config>qos>hs-pool-policy>mid-tier>mid-pool slope-policy)

[Tree] (config>qos>hs-pool-policy>root-tier>root-pool slope-policy)

Full Context

configure qos hs-pool-policy mid-tier mid-pool slope-policy

configure qos hs-pool-policy root-tier root-pool slope-policy

Description

This command specifies the slope policy to be used to define the high, low, and exceed slopes within the pool. The slope (high, low, or exceed) used on the egress queue for the packet that generated the buffer request is also used in the mid-pool from the applied slope policy. The pool’s current allocation amount is applied to the appropriate slope to derive the buffer rejection probability. The probability value is compared to a randomly-generated number. If the probability decision generates a rejection decision or the buffer pool has no remaining free buffers, the buffer request fails and the arriving packet is discarded. Otherwise, a buffer is allocated as long as the port-class and root-tier buffer pools also honor the buffer request.

The no form of the command restores the default slope policy to the associated pool.

Default

slope-policy _tmnx_hs_default

Parameters

policy-name

Specifies the slope policy associated with this pool, up to 32 characters.

Platforms

7750 SR-7/12/12e

slope-policy

Syntax

slope-policy policy-name

no slope-policy

Context

[Tree] (config>qos>hs-port-pool-policy>std-port-class-pools>class-pool slope-policy)

[Tree] (config>qos>hs-port-pool-policy>alt-port-class-pools>class-pool slope-policy)

Full Context

configure qos hs-port-pool-policy std-port-class-pools class-pool slope-policy

configure qos hs-port-pool-policy alt-port-class-pools class-pool slope-policy

Description

This command specifies the slope policy that is used to define the high, low, and exceed slopes within the port-class pool. The slope used on the egress queue for the packet that generated the buffer request is also used in the class-pool. The pool’s current allocation amount is applied to the appropriate slope to derive the buffer rejection probability. The probability value is compared to a randomly generated number. If the probability decision generates a rejection or the buffer pool has no remaining free buffers, the buffer request fails and the arriving packet is discarded. Otherwise, a buffer is allocated as long as the mid-tier and root-tier buffer pools also honor the buffer request.

The no form of the command restores the default slope policy to the associated class-pool.

Default

slope-policy _tmnx_hs_default

Parameters

policy-name

Specifies the policy name, up to 32 characters. This parameter is required when executing the slope-policy command and must refer to an existing slope policy within the system. If a slope policy with the specified name does not exist, the slope-policy command fails without modifying the slope behavior on the pool. A non-existent slope-policy error is generated. After a slope policy is associated with any HSQ queue or buffer pool, the policy cannot be deleted.

Platforms

7750 SR-7/12/12e

slope-policy

Syntax

slope-policy name [create]

no slope-policy name

Context

[Tree] (config>qos slope-policy)

Full Context

configure qos slope-policy

Description

Commands in this context configure a QoS slope policy.

Default

slope-policy "default”

Parameters

name

The name of the slope policy.

Values

Valid names consist of any string up to 32 characters, composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes.

Platforms

All

slope-policy

Syntax

slope-policy src-name dst-name [overwrite]

Context

[Tree] (config>qos>copy slope-policy)

Full Context

configure qos copy slope-policy

Description

This command copies existing QoS policy entries for a QoS policy-id to another QoS policy-id.

The copy command is a configuration-level maintenance tool used to create new policies using existing policies. It also allows bulk modifications to an existing policy with the use of the overwrite keyword.

Parameters

slope-policy

Indicates that the source policy ID and the destination policy ID are slope policy IDs. Specify the source policy ID that the copy command will attempt to copy from and specify the destination policy ID to which the command will copy a duplicate of the policy.

overwrite

Specifies to replace the existing destination policy. Everything in the existing destination policy will be overwritten with the contents of the source policy. If overwrite is not specified, an error will occur if the destination policy ID exists.

ALA-7>config>qos# copy slope-policy default sp1
MINOR: CLI Destination "sp1" exists - use {overwrite}.
ALA-7>config>qos#overwrite

Platforms

All

slow-psc-timer

slow-psc-timer

Syntax

slow-psc-timer interval

no slow-psc-timer

Context

[Tree] (config>router>mpls>mpls-tp>protection-template slow-psc-timer)

Full Context

configure router mpls mpls-tp protection-template slow-psc-timer

Description

This command configures the slow timer value to be used for protection switching coordination (PSC) packets for MPLS-TP linear protection (RFC 6378).

Default

slow-psc-timer 5

Parameters

interval

Specifies the slow timer interval in seconds.

Values

5 to 60

Platforms

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

slow-queue-threshold

slow-queue-threshold

Syntax

slow-queue-threshold kilobits-per-second

no slow-queue-threshold

Context

[Tree] (config>card>virt-sched-adj slow-queue-threshold)

Full Context

configure card virtual-scheduler-adjustment slow-queue-threshold

Description

This command overrides the system default rate threshold where policers and queues are placed in the "slow” queue category. Slow rate policers and queues use a different minimum rate calculation interval time than fast rate queues. The rate is determined based on the previous calculated offered rate for the policer or queue.

The default slow policer or queue rate is 1 Mb/s. The fast rate is derived by multiplying the slow rate by a factor of 1.5 resulting in a default fast rate of 1.5 Mb/s. The slow-queue-threshold command uses a "Kilobit-Per-Second” value to modify the default slow queue rate threshold and indirectly changes the fast queue rate threshold.

The no form of this command restores the default slow queue and fast rate thresholds.

Default

no slow-queue-threshold

Parameters

kilobits-per-second

Specifies that the kilobit-per-second parameter is required and is used to modify the default slow rate threshold. Defining a value of 0 forces all policers and queues to be treated as fast rate. Defining a value of 1000 (1 Mb/s) returns the threshold to the default value and is equivalent to executing no slow-queue-threshold.

The fast rate threshold is derived by multiplying the new slow rate threshold by a factor of 1.5.

Values

0 to 1000000 kb/s

Default

1000 kb/s

Platforms

All

sm-tti

sm-tti

Syntax

sm-tti

Context

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

Full Context

configure port otu sm-tti

Description

Commands in this context configure section monitoring trail trace identifier parameters.

Platforms

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

snap-oui

snap-oui

Syntax

snap-oui {zero | non-zero}

no snap-oui

Context

[Tree] (config>qos>sap-ingress>mac-criteria>entry>match snap-oui)

Full Context

configure qos sap-ingress mac-criteria entry match snap-oui

Description

Configures an IEEE 802.3 LLC SNAP Ethernet frame OUI zero or non-zero value to be used as a service ingress QoS policy match criterion.

The no form of this command removes the criterion from the match criteria.

Default

no snap-oui

Parameters

zero

Specifies to match packets with the 3-byte OUI field in the SNAP-ID set to zero.

non-zero

Specifies to match packets with the 3-byte OUI field in the SNAP-ID not set to zero.

Platforms

All

snap-oui

Syntax

snap-oui {zero | non-zero}

no snap-oui

Context

[Tree] (config>filter>mac-filter>entry>match snap-oui)

Full Context

configure filter mac-filter entry match snap-oui

Description

This command configures an IEEE 802.3 LLC SNAP Ethernet Frame OUI zero or non-zero value to be used as a MAC filter match criterion.

The no form of the command removes the criterion from the match criteria.

Default

no snap-oui

Parameters

zero

Specifies to match packets with the three-byte OUI field in the SNAP-ID set to zero.

non-zero

Specifies to match packets with the three-byte OUI field in the SNAP-ID not set to zero.

Platforms

All

snap-oui

Syntax

snap-oui {zero | non-zero}

no snap-oui

Context

[Tree] (config>system>security>mgmt-access-filter>mac-filter>entry>match snap-oui)

Full Context

configure system security management-access-filter mac-filter entry match snap-oui

Description

This command configures an IEEE 802.3 LLC SNAP Ethernet Frame OUI zero or non-zero value to be used as a MAC filter match criterion.

The no form of this command removes the criterion from the match criteria.

Default

no snap-oui

Parameters

zero

Specifies to match packets with the three-byte OUI field in the SNAP-ID set to zero.

non-zero

Specifies to match packets with the three-byte OUI field in the SNAP-ID not set to zero.

Platforms

All

snap-pid

snap-pid

Syntax

snap-pid snap-pid

no snap-pid

Context

[Tree] (config>qos>sap-ingress>mac-criteria>entry>match snap-pid)

Full Context

configure qos sap-ingress mac-criteria entry match snap-pid

Description

Configures an IEEE 802.3 LLC SNAP Ethernet frame PID value to be used as a service ingress QoS policy match criterion.

This is a 2-byte protocol id that is part of the IEEE 802.3 LLC SNAP Ethernet Frame that follows the 3-byte OUI field.

The snap-pid field, etype field, ssap, and dsap fields are mutually exclusive and cannot be part of the same match criteria.

The snap-pid match criteria is independent of the OUI field within the SNAP header. Two packets with different 3-byte OUI fields, but the same PID field, will both match the same policy entry based on a snap-pid match criteria.

The no form of this command removes the snap-pid value as the match criteria.

Default

no snap-pid

Parameters

snap-pid

The 2-byte snap-pid value to be used as a match criterion in hexadecimal.

Values

0x0000 to 0xFFFF

Platforms

All

snap-pid

Syntax

snap-pid snap-pid

no snap-pid

Context

[Tree] (config>filter>mac-filter>entry>match snap-pid)

Full Context

configure filter mac-filter entry match snap-pid

Description

Configures an IEEE 802.3 LLC SNAP Ethernet Frame PID value to be used as a MAC filter match criterion.

This is a two-byte protocol id that is part of the IEEE 802.3 LLC SNAP Ethernet Frame that follows the three-byte OUI field.

The snap-pid field, etype field, ssap and dsap fields are mutually exclusive and may not be part of the same match criteria.

The snap-pid match criterion is independent of the OUI field within the SNAP header. Two packets with different three-byte OUI fields but the same PID field will both match the same filter entry based on a snap-pid match criteria.

The no form of the command removes the snap-pid value as the match criteria.

Default

no snap-pid

Parameters

snap-pid

Specifies the two-byte snap-pid value to be used as a match criterion. The value can be expressed in decimal integer or hexadecimal format.

Values

0 to 65535 or 0x0000 to 0xFFFF

Platforms

All

snap-pid

Syntax

snap-pid snap-pid

no snap-pid

Context

[Tree] (config>system>security>mgmt-access-filter>mac-filter>entry>match snap-pid)

Full Context

configure system security management-access-filter mac-filter entry match snap-pid

Description

This command configures an IEEE 802.3 LLC SNAP Ethernet Frame PID value to be used as a MAC filter match criterion.

This is a two-byte protocol id that is part of the IEEE 802.3 LLC SNAP Ethernet Frame that follows the three-byte OUI field.

The snap-pid field, etype field, ssap and dsap fields are mutually exclusive and may not be part of the same match criteria. Refer to the 7450 ESS, 7750 SR, 7950 XRS, and VSR Router Configuration Guide for information about MAC Match Criteria Exclusivity Rules fields that are exclusive based on the frame format.

Note:

The snap-pid match criterion is independent of the OUI field within the SNAP header. Two packets with different three-byte OUI fields but the same PID field will both match the same filter entry based on a snap-pid match criteria.

The no form of this command removes the snap-pid value as the match criteria.

Default

no snap-pid

Parameters

pid-value

Specifies the two-byte snap-pid value to be used as a match criterion in hexadecimal.

Values

0x0000 to 0xFFFF

Platforms

All

snmp

snmp

Syntax

snmp

Context

[Tree] (config>service>vprn snmp)

Full Context

configure service vprn snmp

Description

Commands in this context configure SNMP parameters for this VPRN.

Platforms

All

snmp

Syntax

snmp

Context

[Tree] (config>system>security>user snmp)

Full Context

configure system security user snmp

Description

This command creates the context to configure SNMP group membership for a specific user and defines encryption and authentication parameters.

All SNMPv3 users must be configured with the commands available in this CLI node.

The OS always uses the configured SNMPv3 user name as the security user name.

Platforms

All

snmp

Syntax

snmp

Context

[Tree] (config>system snmp)

[Tree] (config>system>security snmp)

Full Context

configure system snmp

configure system security snmp

Description

This command creates the context to configure SNMPv1, SNMPv2, and SNMPv3 parameters.

Platforms

All

snmp-trap-group

snmp-trap-group

Syntax

snmp-trap-group log-id | log-name [name log-name]

no snmp-trap-group log-id | log-name

Context

[Tree] (config>service>vprn>log snmp-trap-group)

Full Context

configure service vprn log snmp-trap-group

Description

This command creates the context to configure a group of SNMP trap receivers and their operational parameters for a specific log-id.

A group specifies the types of SNMP traps and specifies the log ID that will receive the group of SNMP traps. The user must configure a trap group before SNMP traps can be sent.

To suppress the generation of all alarms and traps, see the event-control command. To suppress alarms and traps that are sent to this log-id, see the filter command. After alarms and traps are generated, they can be directed to one or more SNMP trap groups. Log events that can be forwarded as SNMP traps are always defined on the main event source.

The no form of this command deletes the SNMP trap group.

Parameters

log-id | log-name

Specifies the log ID or name (up to 32 characters).

Values

log-id: 1 to 100

name log-name

Specifies an optional log name of a log configured in the log-id context, up to 32 characters, that can be used to refer to the log after it is created. Alarms and traps cannot be sent to the trap receivers until a valid log-id exists.

Platforms

All

snmp-trap-group

Syntax

snmp-trap-group log-id | log-name [name log-name]

no snmp-trap-group log-id | log-name

Context

[Tree] (config>log snmp-trap-group)

Full Context

configure log snmp-trap-group

Description

This command creates the context to configure a group of SNMP trap receivers and their operational parameters for a specified log-id.

A group specifies the types of SNMP traps and the log ID which that will receive the SNMP trap group. The user must configure a trap to send SNMP traps.

To suppress the generation of all alarms and traps, see the event-control command. To suppress alarms and traps that are sent to this log ID, see the filter command. When alarms and traps are generated, they can be directed to one or more SNMP trap groups. Log events that can be forwarded as SNMP traps are always defined at the main event source.

The no form of this command deletes the SNMP trap group.

Parameters

log-id | log-name

Specifies the log ID or log name (up to 32 characters).

Values

log-id: 1 to 100

name log-name

Specifies an optional log name of a log configured in the log-id context, up to 32 characters, that can be used to refer to the log after it is created. Alarms and traps cannot be sent to the trap receivers until a valid log-id exists.

Platforms

All

snoop

snoop

Syntax

[no] snoop

Context

[Tree] (config>service>vprn>if>dhcp>option snoop)

[Tree] (config>service>vpls>sap>dhcp snoop)

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

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

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

Full Context

configure service vprn interface dhcp option snoop

configure service vpls sap dhcp snoop

configure service vprn nw-if dhcp snoop

configure service vpls mesh-sdp dhcp snoop

configure service vpls spoke-sdp dhcp snoop

Description

This command enables snooping of DHCP or DHCP6 messages on the SAP or SDP. Enabling DHCP or DHCP6 snooping on interfaces (SAPs and SDP bindings) is required where DHCP or DHCP6 messages important to lease state table population are received, or where Option 82 information is to be inserted. This includes interfaces that are in the path to receive messages from either DHCP or DHCP6 servers or from subscribers.

The no form of this command disables DHCP or DHCP6 snooping on the specified SAP or SDP binding.

Default

no snoop

Platforms

All

snooping

snooping

Syntax

[no] snooping

Context

[Tree] (config>service>ies>sub-if>grp-if>ipv6>dhcp6 snooping)

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

Full Context

configure service ies subscriber-interface group-interface ipv6 dhcp6 snooping

configure service vprn subscriber-interface group-interface ipv6 dhcp6 snooping

Description

This command enables the group-interface to snoop DHCPv6 relay messages exchange between the subscriber host and the DHCPv6 server. A successful DHCPv6 address assignment triggers ESM DHCPv6 host creation and a release of the lease triggers host deletion. This feature is for ESMv6 applications where a Layer 3 aggregation network is upstream from the BNG.

The no form of this command reverts to the default.

Platforms

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

sntp

sntp

Syntax

[no] sntp

Context

[Tree] (config>system>time sntp)

Full Context

configure system time sntp

Description

This command creates the context to edit the Simple Network Time Protocol (SNTP).

SNTP can be configured in either broadcast or unicast client mode. SNTP is a compact, client-only version of the NTP. SNTP can only receive the time from SNTP/NTP servers. It cannot be used to provide time services to other systems.

The system clock is automatically adjusted at system initialization time or when the protocol first starts up.

When the time differential between the SNTP/NTP server and the system is more than 2.5 seconds, the time on the system is gradually adjusted.

SNTP is created in an administratively enabled state (no shutdown).

The no form of the command removes the SNTP instance and configuration. SNTP does not need to be administratively disabled when removing the SNTP instance and configuration.

Default

sntp

Platforms

All

socket

socket

Syntax

socket [neighbor ip-address | group name]

no socket

Context

[Tree] (debug>router>bgp socket)

Full Context

debug router bgp socket

Description

This command logs all TCP socket events to the debug log.

The no form of this command disables debugging.

Parameters

neighbor ip-address

Debugs only events affecting the specified BGP neighbor.

Values

ipv4-address:

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

ipv6-address:

  • x:x:x:x:x:x:x:x [-interface] (eight 16-bit pieces)

  • x:x:x:x:x:x:d.d.d.d [-interface]

  • x: [0 to FFFF]H

  • d: [0 to 255]D

  • interface: up to 32 characters for link local addresses

group name

Debugs only events affecting the specified peer group name, up to 64 characters, and associated neighbors.

Platforms

All

soft-preemption

soft-preemption

Syntax

[no] soft-preemption

Context

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

[Tree] (config>router>mpls>lsp soft-preemption)

Full Context

configure router mpls lsp-template soft-preemption

configure router mpls lsp soft-preemption

Description

This command enables soft preemption for LSPs of type p2mp-lsp and LSP templates of type p2mp. The soft preemption bit is set to 1 if the following conditions are met; otherwise, the bit is set to 0.

  • soft preemption is enabled, and

  • the P2MP LSP is adaptive, has non-zero bandwidth, and is computed using the local CSPF method

The no form of the command disables soft preemption on the P2MP LSP and P2MP LSP template.

Note:

Soft preemption is always enabled for P2P LSPs and P2P LSP templates and cannot be disabled.

Default

no soft-preemption

Platforms

All

soft-quota-exhausted

soft-quota-exhausted

Syntax

[no] soft-quota-exhausted

Context

[Tree] (config>subscr-mgmt>wlan-gw>ue-query soft-quota-exhausted)

[Tree] (config>aaa>isa-radius-policy>acct-update-triggers soft-quota-exhausted)

Full Context

configure subscriber-mgmt wlan-gw ue-query soft-quota-exhausted

configure aaa isa-radius-policy acct-update-triggers soft-quota-exhausted

Description

This command sends an interim update message when a soft volume quota is reached.

Default

soft-quota-exhausted

Platforms

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

soft-quota-exhausted-filter

soft-quota-exhausted-filter

Syntax

soft-quota-exhausted-filter dsm-ip-filter-name

no soft-quota-exhausted-filter

Context

[Tree] (config>service>ies>sub-if>grp-if>wlan-gw>ranges>range>dsm soft-quota-exhausted-filter)

[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw>ranges>range>dsm soft-quota-exhausted-filter)

Full Context

configure service ies subscriber-interface group-interface wlan-gw vlan-tag-ranges range distributed-sub-mgmt soft-quota-exhausted-filter

configure service vprn subscriber-interface group-interface wlan-gw vlan-tag-ranges range distributed-sub-mgmt soft-quota-exhausted-filter

Description

This command applies a filter when a soft volume quota is reached. The filter replaces the currently applied filter (which can be preconfigured using the vlan-range ip-filter command or be set using RADIUS authentication/ CoA message) for the UE upon quota exhaustion. If the quota is extended using a RADIUS CoA message, the filter is automatically reverted. Configuration changes apply only to new DSM UEs and not to existing UEs.

Platforms

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

software-repository

software-repository

Syntax

software-repository repository-name

no software-repository

Context

[Tree] (config>system>satellite>tdm-sat software-repository)

[Tree] (config>system>satellite>eth-sat software-repository)

Full Context

configure system satellite tdm-sat software-repository

configure system satellite eth-sat software-repository

Description

This command binds the specified software repository to the associated satellite. The software repository is used to locate and serve the correct software image to the satellite at boot time.

The configured software repository is only used when the satellite boots. Changing the software repository for an active satellite does not have an effect until the next time a satellite boots.

A satellite cannot be booted if there is no software repository defined for it.

The no form of the command removes the software repository.

Default

no software-repository

Parameters

repository-name

Specifies a string, up to 32 characters, that uniquely identifies the software repository.

Platforms

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

  • configure system satellite tdm-sat software-repository

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

  • configure system satellite eth-sat software-repository

software-repository

Syntax

software-repository repository-name [create]

no software-repository repository-name

Context

[Tree] (config>system software-repository)

Full Context

configure system software-repository

Description

This command creates or deletes an instance of a software repository. The instance is identified by a repository name.

A software repository is used to obtain files to upgrade software on certain subsystems of the router (for example, Ethernet satellites).

Up to three locations can be specified within a software repository for the router to access files in the repository. The router will first attempt to access the file at the primary location. If the primary location is not configured or the files are not found at the primary location, then the router will attempt to access the files at the secondary location. If the secondary location is not configured or the files are not found at the secondary location, then the router will attempt to access the files at the tertiary location. If the tertiary location is not configured or the files are not found at the tertiary location, then the software repository access will fail.

The no form of the command removes the software repository.

Parameters

repository-name

Specifies a string, up to 32 characters, that uniquely identifies the software repository.

create

Specifies the keyword required when the software-repository context is first created. Once the context is created, it can be accessed without the create keyword.

Platforms

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

solicit-delay

solicit-delay

Syntax

solicit-delay delay

no solicit-delay

Context

[Tree] (config>service>vprn>sub-if>grp-if>ipv6>dhcp6>relay>advertise-selection solicit-delay)

[Tree] (config>service>vprn>sub-if>ipv6>dhcp6>relay>advertise-selection solicit-delay)

[Tree] (config>service>ies>sub-if>grp-if>ipv6>dhcp6>relay>advertise-selection solicit-delay)

Full Context

configure service vprn subscriber-interface group-interface ipv6 dhcp6 relay advertise-selection solicit-delay

configure service vprn subscriber-interface ipv6 dhcp6 relay advertise-selection solicit-delay

configure service ies subscriber-interface group-interface ipv6 dhcp6 relay advertise-selection solicit-delay

Description

This command configures the default time to delay DHCPv6 Solicit messages. The delay is applied to all DHCPv6 Solicit messages for which no per DHCPv6 server or per client MAC delay or preference option value is configured.

The no form of this command removes the delay timeout.

Parameters

delay

Specifies the default amount of time to delay DHCPv6 Solicit messages, in deciseconds.

Values

1 to 100

Platforms

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

solicit-delay

Syntax

solicit-delay delay

no solicit-delay

Context

[Tree] (config>service>vprn>sub-if>grp-if>ipv6>dhcp6>relay>advertise-selection>client-mac solicit-delay)

[Tree] (config>service>vprn>sub-if>ipv6>dhcp6>relay>advertise-selection>client-mac solicit-delay)

[Tree] (config>service>ies>sub-if>grp-if>ipv6>dhcp6>relay>advertise-selection>client-mac solicit-delay)

Full Context

configure service vprn subscriber-interface group-interface ipv6 dhcp6 relay advertise-selection client-mac solicit-delay

configure service vprn subscriber-interface ipv6 dhcp6 relay advertise-selection client-mac solicit-delay

configure service ies subscriber-interface group-interface ipv6 dhcp6 relay advertise-selection client-mac solicit-delay

Description

This command configures the time to delay DHCPv6 Solicit messages with an odd or even source MAC address.

The no form of this command removes the delay timeout.

Parameters

delay

Specifies the time to delay DHCPv6 Solicit messages with an odd or even source MAC address, in deciseconds.

Values

1 to 100

Platforms

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

solicit-delay

Syntax

solicit-delay delay

no solicit-delay

Context

[Tree] (config>service>vprn>sub-if>grp-if>ipv6>dhcp6>relay>advertise-selection>server solicit-delay)

[Tree] (config>service>ies>sub-if>grp-if>ipv6>dhcp6>relay>advertise-selection>server solicit-delay)

[Tree] (config>service>vprn>sub-if>ipv6>dhcp6>relay>advertise-selection>server solicit-delay)

Full Context

configure service vprn subscriber-interface group-interface ipv6 dhcp6 relay advertise-selection server solicit-delay

configure service ies subscriber-interface group-interface ipv6 dhcp6 relay advertise-selection server solicit-delay

configure service vprn subscriber-interface ipv6 dhcp6 relay advertise-selection server solicit-delay

Description

This command configures the time to delay DHCPv6 Solicit messages relayed to the server.

The no form of this command removes the delay timeout.

Parameters

delay

Specifies the time to delay DHCPv6 Solicit messages that are relayed to the server, in deciseconds.

Values

1 to 100

Platforms

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

solicited-release

solicited-release

Syntax

[no] solicited-release

Context

[Tree] (config>service>vprn>dhcp>server>lease-hold-time-for solicited-release)

[Tree] (config>service>vprn>dhcp6>server>lease-hold-time-for solicited-release)

[Tree] (config>router>dhcp6>server>lease-hold-time-for solicited-release)

[Tree] (config>router>dhcp>server>lease-hold-time-for solicited-release)

Full Context

configure service vprn dhcp local-dhcp-server lease-hold-time-for solicited-release

configure service vprn dhcp6 local-dhcp-server lease-hold-time-for solicited-release

configure router dhcp6 local-dhcp-server lease-hold-time-for solicited-release

configure router dhcp local-dhcp-server lease-hold-time-for solicited-release

Description

This command enables the server to hold up a lease even in case of solicited release; for example, when the server receives a normal DHCP release message.

The no form of this command disables the ability of the server to hold up a lease when a solicited release is received.

Platforms

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

sonet-sdh

sonet-sdh

Syntax

sonet-sdh

Context

[Tree] (config>port sonet-sdh)

Full Context

configure port sonet-sdh

Description

This command enables access to the context to configure SONET/SDH ports. This context can only be used when configuring an OC-3 and OC-12 SONET/SDH ports on an appropriate MDA.

This command also enables access to the context to configure SONET/SDH parameters for an Ethernet port in WAN PHY (xgig wan) mode.

The 10 Gigabit Ethernet LAN port also has SONET/SDH characteristics. However, these characteristics are predetermined and not configurable.

This command is supported by TDM satellite.

Platforms

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

source

source

Syntax

[no] source ipv6-address

Context

[Tree] (config>subscr-mgmt>igmp-policy source)

[Tree] (config>subscr-mgmt>igmp-policy>static>group source)

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

Full Context

configure subscriber-mgmt igmp-policy source

configure subscriber-mgmt igmp-policy static group source

configure subscriber-mgmt mld-policy static group source

Description

This command adds or removes a static multicast source.

The no form of this command reverts to the default.

Parameters

grp-ipv6-address

Specifies the IPv6 address.

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 to FFFF]H

d - [0 to 255]D

- multicast group IPv6 address

Platforms

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

source

Syntax

[no] source ip-address

[no] source src-ipv6-address

Context

[Tree] (config>service>vpls>mesh-sdp>igmp-snooping>static>group source)

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

[Tree] (config>service>vpls>spoke-sdp>igmp-snooping>static>group source)

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

[Tree] (config>service>vpls>sap>igmp-snooping>static>group source)

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

Full Context

configure service vpls mesh-sdp igmp-snooping static group source

configure service vpls sap mld-snooping static group source

configure service vpls spoke-sdp igmp-snooping static group source

configure service vpls mesh-sdp mld-snooping static group source

configure service vpls sap igmp-snooping static group source

configure service vpls spoke-sdp mld-snooping static group source

Description

This command specifies a IPv4 or IPv6 unicast address that sends data on an interface. This enables a multicast receiver host to signal a router the group to receive multicast traffic from, and from the sources that the traffic is expected.

The source command is mutually exclusive with the specification of individual sources for the same group.

The source command in combination with the group is used to create a specific (S,G) static group entry.

Static (s,g) entries cannot be entered when a starg is already created.

Use the no form of this command to remove the source from the configuration.

Parameters

ip-address

Specifies the IPv4 unicast address

src-ipv6-address

Specifies the IPv6 unicast address.

Platforms

All

source

Syntax

source ip-address

no source

Context

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

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

Full Context

configure service ies interface sap ip-tunnel source

configure service vprn interface sap ip-tunnel source

Description

This command configures the source IPv4 or IPv6 address to use for an IP tunnel. This configuration applies to the outer IP header of the encapsulated packets. The IPv4 or IPv6 address must belong to the one of the IP subnets associated with the public SAP interface of the tunnel-group. 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 source address contains an IPv6 address it must be a global unicast address.

The no form of this command deletes the source address from the tunnel configuration. The tunnel must be administratively shutdown before issuing the no source command.

Default

no source

Parameters

Ip-address

Specifies an IPv4 address or an IPv6 address.

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..FFFF]H

d

[0..255]D

Platforms

All

source

Syntax

[no] source ip-address

Context

[Tree] (config>service>vprn>igmp>ssm-translate>grp-range source)

Full Context

configure service vprn igmp ssm-translate grp-range source

Description

This command specifies the source IP address for the group range. Whenever a (*,G) report is received in the range specified by grp-range start and end parameters, it is translated to an (S,G) report with the value of this object as the source address.

Parameters

ip-address

Specifies the IP address that will be sending data.

Platforms

All

source

Syntax

source ip-address

Context

[Tree] (config>service>vprn>igmp>if>static>group source)

Full Context

configure service vprn igmp interface static group source

Description

This command specifies an IPv4 unicast address that sends data on an interface. This enables a multicast receiver host to signal a router the group is to receive multicast traffic from, and from the sources that the traffic is expected.

The source command is mutually exclusive with the specification of individual sources for the same group.

The source command in combination with the group is used to create a specific (S,G) static group entry.

Use the no form of this command to remove the source from the configuration.

Parameters

ip-address

Specifies the IPv4 unicast address.

Platforms

All

source

Syntax

[no] source src-ipv6-address

Context

[Tree] (config>service>vprn>mld>if>static>group source)

Full Context

configure service vprn mld interface static group source

Description

This command specifies an IPv6 unicast address that sends data on an interface. This enables a multicast receiver host to signal a router the group to receive multicast traffic from, and from the sources that the traffic is expected.

The source command is mutually exclusive with the specification of individual sources for the same group.

The source command, in combination with the group, is used to create a specific (S,G) static group entry.

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

Parameters

src-ipv6-address

Specifies the IPv6 unicast address.

Platforms

All

source

Syntax

[no] source ip-address

Context

[Tree] (config>service>vprn>mld>ssm-translate>grp-range source)

Full Context

configure service vprn mld ssm-translate grp-range source

Description

This command specifies the source IP address for the group range. Whenever a (*,G) report is received in the range specified by grp-range start and end parameters, it is translated to an (S,G) report with the value of this object as the source address.

Parameters

ip-address

Specifies the IP address that will be sending data.

Platforms

All

source

Syntax

[no] source unicast-ip-prefix/mask

Context

[Tree] (config>service>vprn>msdp source)

Full Context

configure service vprn msdp source

Description

This command limits the number of active source messages the router accepts from sources in the specified address range.

If the prefix and mask provided is already a configured then this command only provides the context to configure the parameters pertaining to this active source-message filter.

If the prefix and mask provided is not already a configured, then the source node instance must be created and the context to configure the parameters pertaining to this node should be provided. In this case, the $ prompt to indicate that a new entity (source) is being created should be used.

The source active msdp messages are not rate limited based on the source address range.

The no form of this message removes the source active rate limiter for this source address range.

Parameters

unicast-ip-prefix

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)

mask

Specifies the subnet mask for the range expressed as a decimal integer mask length or in dotted decimal notation.

Values

0 to 32 (mask length), 0.0.0.0 to 255.255.255.255 (dotted decimal)

Platforms

All

source

Syntax

[no] source ip-address [/mask]

[no] source any

Context

[Tree] (config>service>vprn>mvpn>pt>selective>multistream-spmsi>group source)

[Tree] (config>service>vprn>mvpn>pt>selective>umh-rm>group source)

Full Context

configure service vprn mvpn provider-tunnel selective multistream-spmsi group source

configure service vprn mvpn provider-tunnel selective umh-rate-monitoring group source

Description

This command creates source prefixes for specific groups that map to the multicast stream.

The no form removes the source prefix.

Parameters

ip-address/mask

Specifies the IP address of the group.

Values

ipv4-prefix

a.b.c.d

ipv4-prefix-length

[0..32]

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..FFFF]H

d

[0..255]D

ipv6-prefix-length

[0..128]

Platforms

All

source

Syntax

source source-type

source source-type level level

no source source-type

Context

[Tree] (config>app-assure>group>anl source)

Full Context

configure application-assurance group access-network-location source

Description

This command configures location sources for the dynamic experience management. The location source types are, for example, 3G and congestion point.

Default

source mobile-3g

Parameters

source-type

Specifies the location or access technology.

Values

access-point — Provides Dynamic Experience Management (DEM) for the WLGW access point.

Note:

The access points do not need to support the Nokia CEA function.

level

Specifies which congestion point within the specified source-type to monitor for congestion.

Values

MAC+VLAN — WLGW access point (MAC) and radio (VLAN).

Note:

The access points do not need to support the Nokia CEA function.

Platforms

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

source

Syntax

[no] source ip-address

Context

[Tree] (config>router>igmp>ssm-translate>grp-range source)

[Tree] (config>router>igmp>if>ssm-translate>grp-range source)

Full Context

configure router igmp ssm-translate grp-range source

configure router igmp interface ssm-translate grp-range source

Description

This command specifies the source IP address for the group range. Whenever a (*,G) report is received in the range specified by grp-range start and end parameters, it is translated to an (S,G) report with the value of this object as the source address.

Parameters

ip-address

Specifies the IP address that will be sending data.

Platforms

All

source

Syntax

[no] source ip-address

Context

[Tree] (config>router>igmp>if>static>group source)

Full Context

configure router igmp interface static group source

Description

This command specifies a IPv4 unicast address that sends data on an interface. This enables a multicast receiver host to signal a router the group to receive multicast traffic from, and from the source(s) that the traffic is expected.

The source command is mutually exclusive with the specification of individual sources for the same group.

The source command in combination with the group is used to create a specific (S,G) static group entry.

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

Parameters

ip-address

Specifies the IPv4 unicast address.

Platforms

All

source

Syntax

[no] source ip-address

Context

[Tree] (config>router>igmp>tunnel-interface>static>group source)

Full Context

configure router igmp tunnel-interface static group source

Description

This command specifies a IPv4 unicast address of a multicast source. The source command is mutually exclusive with the specification of individual sources for the same group. The source command in combination with the group is used to create a specific (S,G) group entry in a static group join on a tunnel interface associated with a P2MP RSVP LSP.

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

Parameters

ip-address

Specifies the IPv4 unicast address.

Platforms

All

source

Syntax

[no] source src-ipv6-address

Context

[Tree] (config>router>mld>if>static>group source)

Full Context

configure router mld interface static group source

Description

This command specifies an IPv6 unicast address that sends data on an interface. This enables a multicast receiver host to signal a router the group to receive multicast traffic from, and from the source(s) that the traffic is expected.

The source command is mutually exclusive with the specification of individual sources for the same group.

The source command, in combination with the group, is used to create a specific (S,G) static group entry.

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

Parameters

src-ipv6-address

Specifies the IPv6 unicast address.

Platforms

All

source

Syntax

[no] source ipv6-address

Context

[Tree] (config>router>mld>ssm-translate>grp-range source)

[Tree] (config>router>mld>if>ssm-translate>grp-range source)

Full Context

configure router mld ssm-translate grp-range source

configure router mld interface ssm-translate grp-range source

Description

This command specifies the source IP address for the group range. Whenever a (*,G) report is received in the range specified by grp-range start and end parameters, it is translated to an (S,G) report with the value of this object as the source address.

The no form of this command removes the IPv6 address form the group range configuration.

Parameters

ipv6-address

Specifies the IPv6 address that will be sending data.

Platforms

All

source

Syntax

[no] source unicast-ip-prefix/mask

Context

[Tree] (config>router>msdp source)

Full Context

configure router msdp source

Description

This command configures the parameters for the specified source instance.

The source active config>router msdp messages are not rate limited based on the source address range.

The no form of this command removes the source address instance.

Parameters

unicast-ip-prefix/mask

Specifies the IP address and subnet mask for the range, expressed as a decimal integer mask length or in dotted-decimal notation.

Values

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

mask: 0 to 32 (mask length), 0.0.0.0 to 255.255.255.255 (dotted-decimal)

Platforms

All

source

Syntax

source mep mep-id domain md-index association ma-index

source mep mep-id domain-name admin-name association-name admin-name

no source

Context

[Tree] (config>oam-pm>session>ethernet source)

Full Context

configure oam-pm session ethernet source

Description

This command defines the source launch point identification Y.1731 parameters that are used by the individual tests within the session. If an MEP matching the configuration does not exist, the session is allowed to become active, however the frames sent frames and received as seen under the show >oam-pm>statistics>session session-name command is zero. The preferred reference to the MEP launch point is by admin-name. Therefore, the syntax source mep mep-id domain-name admin-name association-name admin-name should be used.

The no form of this command removes this session parameter.

Parameters

mep-id

Specifies the maintenance association end point identifier of the launch point.

Values

1 to 8191

md-index

Specifies the maintenance domain (MD) index value of the launch point. The domain-name admin-name parameter is preferred for specifying the domain information.

Values

1 to 4294967295

ma-index

Specifies the maintenance association (MA) index value of the launch point. The association-name ma-name parameter is preferred for specifying the association information.

Values

1 to 4294967295

admin-name

Specifies the name reference for the maintenance domain (MD), or the association (MA) admin-name value of the launch point, up to 64 characters.

Platforms

All

source

Syntax

source ip-address

no source

Context

[Tree] (config>oam-pm>session>ip source)

Full Context

configure oam-pm session ip source

Description

This command defines the source IP address that the session controller (launch point) uses for the test. The source address must be a local resident IP address in the context; otherwise, the response packets are processed by the TWAMP Light application. Only source addresses configured as part of TWAMP tests can process the reflected TWAMP packets from the session reflector.

The no form of this command removes the source address parameters.

Parameters

source

Indicates the launch point.

ip-address

Specifies the source IP address that the session controller (launch point) uses for the test.

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

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

source

Syntax

source {line-ref | internal-clock}

Context

[Tree] (config>system>sync-if-timing>bits>output source)

Full Context

configure system sync-if-timing bits output source

Description

This command configures the values used to identify the source of the BITS (Building Integrated Timing Supply) output. This is either the signal recovered directly from ref1, ref2 or ptp, or it is the output of the node’s central clock. The directly recovered signal would be used when the BITS output signal is feeding into an external standalone timing distribution device (BITS/SASE). The specific directly recovered signal used is the best of the available signals based of the QL and/or the ref-order. The central clock output would be used when no BITS/SASE device is present and the BITS output signal is used to monitor the quality of the recovered clock within the system.

Default

source line-ref

Parameters

line-ref

Specifies that the BITS output timing is selected from one of the input references, without any filtering.

internal-clock

Specifies that the BITS output timing is driven from the system timing.

Platforms

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

source

Syntax

source ip-address

no source

Context

[Tree] (config>router>if>if-attr>delay>dyn>twamp>ipv4 source)

Full Context

configure router interface if-attribute delay dynamic twamp-light ipv4 source

Description

This command configures the unicast IPv4 address used as the source of the TWAMP Light test packet. When this command is not configured, the primary IPv4 address, or the reference IPv4 address in the case of unnumbered interfaces, is used as the source. This command can be used when the IPv4 primary address or reference interface is not the desired source address for the packet.

Changes are allowed without administratively disabling the IPv4 protocol.

The no form of this command removes the specified address, which causes the source address to be auto-learned.

Default

no source

Parameters

ip-address

Specifies TWAMP Light IPv4 source address.

Values

a.b.c.d

Platforms

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

source

Syntax

source ipv6-address

no source

Context

[Tree] (config>router>if>if-attr>delay>dyn>twamp>ipv6 source)

Full Context

configure router interface if-attribute delay dynamic twamp-light ipv6 source

Description

This command configures the IPv6 address used as the source of the TWAMP Light test packet. When this command is not configured, no source address is present and an error is raised to prevent the transmission of the test packet.

The IPv6 protocol can be enabled even without addressing. However, the test will not transmit packets. The link local address must be in the form fe80::/64 in accordance with RFC 4291, IP Version 6 Addressing Architecture.

The no form of this command removes the specified address.

Default

no source

Parameters

ipv6-address

Specifies the TWAMP Light IPv6 source address.

Values

ipv6-address:

x:x:x:x:x:x:x:x

x - [0 to FFFF]H

unicast and link local IPv6 address only

Platforms

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

source

Syntax

source mep mep-id domain md-index association ma-index

no source

Context

[Tree] (config>test-oam>sath>svc-test>svc-stream>frm-payl>eth>eth-cfm source)

Full Context

configure test-oam service-activation-testhead service-test service-stream frame-payload ethernet eth-cfm source

Description

This command defines the source launch maintenance association end point (MEP) for service activation. If a MEP that matches this configuration does not exist, the service activation test will not start.

The no form of this command disables the source launch point.

Default

no source

Parameters

mep-id

Specifies the MEP identifier of the launch point.

Values

1 to 8191

md-index

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

Values

1 to 4294967295

ma-index

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

Values

1 to 4294967295

Platforms

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

source-address

source-address

Syntax

source-address ipv6-address

no source-address

Context

[Tree] (config>service>vprn>sub-if>ipv6>dhcp6>relay source-address)

[Tree] (config>service>ies>sub-if>ipv6>dhcp6>relay source-address)

[Tree] (config>service>vprn>if>ipv6>dhcp6-relay source-address)

[Tree] (config>service>vprn>sub-if>grp-if>ipv6>dhcp6>relay source-address)

[Tree] (config>service>ies>sub-if>grp-if>ipv6>dhcp6>relay source-address)

[Tree] (config>service>ies>if>ipv6>dhcp6-relay source-address)

Full Context

configure service vprn subscriber-interface ipv6 dhcp6 relay source-address

configure service ies subscriber-interface ipv6 dhcp6 relay source-address

configure service vprn interface ipv6 dhcp6-relay source-address

configure service vprn subscriber-interface group-interface ipv6 dhcp6 relay source-address

configure service ies subscriber-interface group-interface ipv6 dhcp6 relay source-address

configure service ies interface ipv6 dhcp6-relay source-address

Description

This command configures the source IPv6 address of the DHCPv6 relay messages.

The no form of this command reverts to the default.

Parameters

ipv6-address

Specifies the source IPv6 address of the DHCPv6 relay messages.

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 to FFFF]H

d: [0 to 255]D

Platforms

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

  • configure service vprn subscriber-interface group-interface ipv6 dhcp6 relay source-address
  • configure service vprn subscriber-interface ipv6 dhcp6 relay source-address
  • configure service ies subscriber-interface ipv6 dhcp6 relay source-address
  • configure service ies subscriber-interface group-interface ipv6 dhcp6 relay source-address

All

  • configure service ies interface ipv6 dhcp6-relay source-address
  • configure service vprn interface ipv6 dhcp6-relay source-address

source-address

Syntax

source-address ip-address

no source-address

Context

[Tree] (config>aaa>l2tp-acct-plcy>radius-acct-server source-address)

Full Context

configure aaa l2tp-accounting-policy radius-accounting-server source-address

Description

This command configures the source address of the RADIUS messages.

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

Parameters

ip-address

Specifies the source address to be used for NAT RADIUS accounting.

Platforms

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

source-address

Syntax

source-address ip-address | ipv6-address

no source-address

Context

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

Full Context

configure router mpls lsp bfd source-address

Description

This command configures a source address for the seamless BFD (S-BFD) packets sent on the SR-TE LSP. If this command is not configured, the system uses the LSP from address, where applicable. Otherwise, the system uses the system IPv4 address for IPv4 SR-TE LSPs or the IPv6 address corresponding to the IPv6 TE router ID for IPv6 SR-TE LSPs.

The no form of this command reverts to the default.

Default

no source-address

Parameters

ip-address | ipv6-address

Specifies the IPv4 or IPv6 address.

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

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

source-address

Syntax

source-address ip-address | ipv6-address

no source-address

Context

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

Full Context

configure router mpls lsp primary bfd source-address

Description

This command configures a source address for the S-BFD packets sent on the SR-TE LSP primary path. The system uses the LSP from address, where applicable. Otherwise. the system uses the system IPv4 address for IPv4 SR-TE LSPs or the IPv6 address corresponding to the IPv6 TE router ID for IPv6 SR-TE LSPs.

The no form of this command reverts to the default.

Default

no source-address

Parameters

ip-address | ipv6-address

Specifies the IPv4 or IPv6 address.

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

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

source-address

Syntax

source-address ip-address | ipv6-address

no source-address

Context

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

Full Context

configure router mpls lsp secondary bfd source-address

Description

This command configures a source address for the S-BFD packets sent on the SR-TE LSP secondary path. The system uses the LSP from address, where applicable. Otherwise. the system uses the system IPv4 address for IPv4 SR-TE LSPs or the IPv6 address corresponding to the IPv6 TE router ID for IPv6 SR-TE LSPs.

The no form of this command reverts to the default.

Default

no source-address

Parameters

ip-address | ipv6-address

Specifies the IPv4 or IPv6 address.

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

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

source-address

Syntax

source-address ip-address | ipv6-address

no source-address

Context

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

Full Context

configure router mpls lsp-template bfd source-address

Description

This command configures a source address for the S-BFD packets sent on the SR-TE LSP path instantiated according to the LSP template. The system uses the LSP from address, where applicable. Otherwise, the system uses the system IPv4 address for IPv4 SR-TE LSPs or the IPv6 address corresponding to the IPv6 TE router ID for IPv6 SR-TE LSPs.

The no form of this command reverts to the default.

Default

no source-address

Parameters

ip-address | ipv6-address

Specifies the IPv4 or IPv6 address.

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

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

source-address

Syntax

source-address ip-address

no source-address

Context

[Tree] (config>system>management-interface>remote-management source-address)

Full Context

configure system management-interface remote-management source-address

Description

This command configures the address local to this device that NISH uses to connect to this node.

If this command is also configured for a specific manager in the config>system> management-interface>remote-management>manager context, that configuration takes precedence.

The no form of this command causes the system to select the source address based on the selected routing instance of the manager.

Parameters

ip-address

Specifies the IP address that NISH managers use to connect to the node.

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

source-address

Syntax

source-address ip-address

no source-address

Context

[Tree] (config>system>management-interface>remote-management>manager source-address)

Full Context

configure system management-interface remote-management manager source-address

Description

This command configures the address local to this device that this NISH manager uses to connect to this node.

This command takes precedence over the command configured in the global context (config>system>management-interface>remote-management).

The no form of this command causes the source address to be inherited from the global context (config>system>management-interface>remote-management).

Parameters

ip-address

Specifies the IP address that NISH managers use to connect to the node.

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

source-address

Syntax

source-address ip-address

no source-address

Context

[Tree] (config>subscr-mgmt>auth-plcy>radius-auth-server source-address)

[Tree] (config>subscr-mgmt>acct-plcy>server source-address)

Full Context

configure subscriber-mgmt authentication-policy radius-authentication-server source-address

configure subscriber-mgmt radius-accounting-policy radius-accounting-server source-address

Description

This command configures the source address of the RADIUS packet.

The system IP address must be configured in order for the RADIUS client to work. See Configuring a System Interface in the Router Configuration Guide.

Note:

The system IP address must only be configured if the source-address is not specified. When the no source-address command is executed, the source address is determined at the moment the request is sent. This address is also used in the nas-ip-address attribute: over there it is set to the system IP address if no source-address was given.

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

Default

System IP address

Parameters

ip-address

Specifies the IP prefix for the IP match criterion in dotted decimal notation.

Values

0.0.0.0 to 255.255.255.255

Platforms

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

source-address

Syntax

source-address ip-address [allow-connections]

no source-address

Context

[Tree] (config>aaa>diam>node source-address)

Full Context

configure aaa diameter node source-address

Description

This command configures IPv4 source address that the SR OS node will use for its peering connection.

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

Parameters

ip-address

Specifies IP prefix for the IP match criterion in dotted decimal notation

Values

0.0.0.0 to 255.255.255.255

allow-connections

Specifies to accept peering connections on the configured source IPv4 address. The peer initiating the connection can only be an inter-chassis peer.

Platforms

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

source-address

Syntax

source-address ip-address

no source-address

Context

[Tree] (config>redundancy>multi-chassis>peer source-address)

Full Context

configure redundancy multi-chassis peer source-address

Description

This command specifies the source address used to communicate with the multi-chassis peer.

The no form of this command reverts to the default.

Parameters

ip-address

Specifies the source address used to communicate with the multi-chassis peer.

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

source-address

Syntax

source-address ip-address

no source-address

Context

[Tree] (config>aaa>radius-srv-plcy>servers source-address)

Full Context

configure aaa radius-server-policy servers source-address

Description

This command configures the source address of the RADIUS packet. The system IP address must be configured in order for the RADIUS client to work. See "Configuring a System Interface” in the 7450 ESS, 7750 SR, 7950 XRS, and VSR Router Configuration Guide.

Note:

The system IP address must only be configured if the source-address is not specified. When the no source-address command is executed, the source address is determined at the moment the request is sent. This address is also used in the nas-ip-address attribute: over there it is set to the system IP address if no source-address was given.

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

Parameters

ip-address

Specifies the source address of RADIUS packet.

Platforms

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

source-address

Syntax

source-address

Context

[Tree] (config>service>vprn source-address)

Full Context

configure service vprn source-address

Description

Commands in this context specify the source address and application that should be used in all unsolicited packets.

Platforms

All

source-address

Syntax

source-address ip-address

no source-address

Context

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

Full Context

configure router ldp lsp-bfd source-address

Description

This command configures the source address of periodic LSP ping packets and BFD control packets for LSP BFD sessions that are associated with LDP prefixes in the prefix list. The system IP address is used by default. If the system IP address is not routable from the far-end node of the BFD session, then an alternate routable IP address that is local to the source node should be used.

Default

no source-address

Parameters

ip-address

Specifies a routable IPv4 or IPv6 address that is local to the node.

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 in hexadecimal

d — 0 to 255 in decimal

Default

system IP address

Platforms

All

source-address

Syntax

source-address ip-address

no source-address

Context

[Tree] (config>app-assure>rad-acct-plcy>server source-address)

Full Context

configure application-assurance radius-accounting-policy radius-accounting-server source-address

Description

This command configures the source address of the RADIUS packet. The system IP address must be configured in order for the RADIUS client to work. See "Configuring a System Interface” in the 7450 ESS, 7750 SR, 7950 XRS, and VSR Router Configuration Guide. The system IP address must only be configured if the source-address is not specified. When the no source-address command is executed, the source address is determined at the moment the request is sent. This address is also used in the nas-ip-address attribute: over there it is set to the system IP address if no source address was given.

The no form of this command reverts to the default value, where the source address is the system IP address.

Default

no source-address

Parameters

ip-address

The IP prefix for the IP match criterion in dotted decimal notation.

Values

0.0.0.0 - 255.255.255.255

Platforms

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

source-address

Syntax

source-address ip-address

no source-address

Context

[Tree] (config>service>ipfix>export-policy>collector source-address)

Full Context

configure service ipfix ipfix-export-policy collector source-address

Description

This command configures the source address from which UDP streams containing IPFIX flow records will be sourced.

Default

no source-address

Parameters

ip-address

Source IPv4 address from which UDP streams are sent.

Platforms

All

source-address

Syntax

source-address ip-address

no source-address

Context

[Tree] (config>filter>gre-tun-tmp>ipv4 source-address)

Full Context

configure filter gre-tunnel-template ipv4 source-address

Description

This command defines the source IPv4 address to be used in the GRE IP header used to encapsulate the matching IPv4/IPv6 packet. This IP address can be configured as any value and is not validated against a local IP address. The source-address command must be configured for the template to be valid.

The no form of this command removes the source IP address configuration from the associated GRE tunnel template.

Parameters

ip-address

Specifies the IPv4 address (in dotted decimal notation) to be used as the source address.

Platforms

All

source-address

Syntax

source-address [ip-address]

no source-address

Context

[Tree] (config>filter>redirect-policy>dest>ping-test source-address)

Full Context

configure filter redirect-policy destination ping-test source-address

Description

This command configures the source address to use in the IP packet of the ping test for this destination.

Default

no source-address

Parameters

ip-address

The source address of the IP packet. This can be IPv4 only for an IPv4 destination and IPv6 only for an IPv6 destination.

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

source-address

Syntax

source-address

Context

[Tree] (config>system>security source-address)

Full Context

configure system security source-address

Description

This command configures the IP source address that is used in all unsolicited packets sent by the application.

The configured source address applies only to packets transmitted in-band (for example, a network port on an IOM). Packets transmitted out-of-band on the management interface on the CPM Ethernet port use the address of the CPM Ethernet port as the IP source address in the packet.

When a source address is specified for the ptp application, the port-based 1588 hardware timestamping assist function will be applied to PTP packets matching the IPv4 address of the router interface used to ingress the SR/ESS or IP address specified in this command. If the IP address is removed, then the port-based 1588 hardware timestamping assist function will only be applied to PTP packets matching the IPv4 address of the router interface.

Platforms

All

source-address

Syntax

source-address ip-address

Context

[Tree] (config>system>security>dot1x>radius-plcy source-address)

Full Context

configure system security dot1x radius-plcy source-address

Description

This command configures the NAS IP address to be sent in the RADIUS packet.

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

Parameters

ip-address

Specifies the IP prefix for the IP match criterion in dotted decimal notation.

Values

0.0.0.0 to 255.255.255.255

Platforms

All

source-address

Syntax

source-address ip-address

source-address prefix-list prefix-list-name

no source-address

Context

[Tree] (config>router>policy-options>policy-statement>entry>from source-address)

Full Context

configure router policy-options policy-statement entry from source-address

Description

This command specifies the source address that is embedded in the join or prune packet as a filter criterion.

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

This command specifies a multicast data source address as a match criterion for this entry.

Default

no source-address

Parameters

ip-address

Specifies the IP prefix for the IP match criterion in dotted decimal notation.

Values

ipv4-address:

  • a.b.c.d

ipv6-address:

  • x:x:x:x:x:x:x:x

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

  • x: [0 to FFFF]H

  • d: [0 to 255]D

prefix-list-name

The prefix list name. Allowed values are any string up to 64 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, ?, space), the entire string must be enclosed within double quotes.

Platforms

All

source-address

Syntax

source-address ipv6-address

no source-address

Context

[Tree] (config>router>segment-routing>srv6 source-address)

Full Context

configure router segment-routing segment-routing-v6 source-address

Description

This command configures the global default source IPv6 address used in the SA field of the outer IPv6 header of the SRv6 encapsulated packet. This value is inherited in the BGP and service contexts by default, but can be overwritten in each context. A maximum of 16 address values can be configured in all contexts in the system.

There is no default value for this command. A default source IPv6 address must be configured in this context or in the BGP or service context. The system does not check if the entered address is a valid local address.

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

Parameters

ipv6-address

Specifies the source IPv6 address of the SRv6.

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 to FFFF]H

d: [0 to 255]D

Platforms

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

source-address

Syntax

source-address ipv6-address

no source-address

Context

[Tree] (config>router>bgp>srv6 source-address)

Full Context

configure router bgp segment-routing-v6 source-address

Description

This command configures the source IPv6 address for SRv6.

This command overrides the source IPv6 address for all address families in the base router instance. By default, BGP uses the value from the top level configuration under config>router>segment-routing>segment-routing-v6.

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

Default

no source-address

Parameters

ipv6-address

Specifies the source IPv6 address of the SRv6.

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 to FFFF]H

d: [0 to 255]D

Platforms

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

source-address

Syntax

source-address ipv6-address

no source-address

Context

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

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

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

Full Context

configure service epipe bgp-evpn segment-routing-v6 source-address

configure service vpls bgp-evpn segment-routing-v6 source-address

configure service vprn bgp-ipvpn segment-routing-v6 source-address

Description

This command configures the source IPv6 address used in the instance for SRv6 packets.

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

Default

no source-address

Parameters

ipv6-address

Specifies the source IPv6 address of the SRv6.

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 to FFFF]H

d: [0 to 255]D

Platforms

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

source-address

Syntax

source-address

Context

[Tree] (config>router>pim source-address)

[Tree] (config>service>vprn>pim source-address)

Full Context

configure router pim source-address

configure service vprn pim source-address

Description

Commands in this context configure the source IP address for PIM messages.

Platforms

All

source-address-range

source-address-range

Syntax

source-address-range start-ip-address

no source-address-range

Context

[Tree] (config>aaa>isa-radius-plcy>servers source-address-range)

Full Context

configure aaa isa-radius-policy servers source-address-range

Description

This command specifies the first IP address in the range of IPv4 addresses that are assigned to a BB-ISA in a given NAT group for NAT RADIUS accounting. The IP addresses are unique within the NAT group and are used to bind the RADIUS client instantiated on each BB-ISA card. The number of IPv4 addresses allocated is equal to the number of BB-ISAs in a NAT group that are enabled for NAT RADIUS accounting. Although only the first IPv4 address is explicitly configured with this command, each internally allocated IPv4 address associated with the BB-ISA card can be seen in the routing table (via show commands) as /32 with protocol designation 'NAT’.

Default

no source-address-range

Parameters

start-ip-address

The starting IP address of the IP address range.

Values

0.0.0.0 - 255.255.255.255

Platforms

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

source-bmac

source-bmac

Syntax

source-bmac ieee-address

no source-bmac

Context

[Tree] (config>service>pbb source-bmac)

Full Context

configure service pbb source-bmac

Description

This command configures the source B-VPLS MAC address to use with PBB and provisions a chassis level source B-MAC.

Parameters

ieee-address

The MAC address assigned to the B-MAC. The value should be input in either a xx:xx:xx:xx:xx:xx or xx-xx-xx-xx-xx-xx format.

Platforms

All

source-bmac

Syntax

source-bmac ieee-address

Context

[Tree] (config>service>vpls>pbb source-bmac)

Full Context

configure service vpls pbb source-bmac

Description

This command configures the base source B-MAC for the B-VPLS. The first 32 bits must be the same with what is configured in the MC-LAG peer. If not configured here, it will inherit the chassis level B-MAC configured under the new PBB object added in the previous section. If the use-sap-bmac command is on, the value of the last 16 bits (lsb) of the source B-MAC must be part of the reserved-source-bmac-lsb configured at chassis level, under service PBB component. If that is not the case, the command will fail.

Platforms

All

source-bmac-lsb

source-bmac-lsb

Syntax

source-bmac-lsb MAC-Lsb [es-bmac-table-size size]

no source-bmac-lsb

Context

[Tree] (config>service>system>bgp-evpn>eth-seg source-bmac-lsb)

Full Context

configure service system bgp-evpn ethernet-segment source-bmac-lsb

Description

This command configures the least significant two bytes of the B-MAC used as the source B-MAC for packets generated from the Ethernet-Segment in PBB-EVPN.

When the multi-homing mode is all-active, this value and the first high order four bytes must match on all the PEs that are part of the same Ethernet-Segment.

The es-bmac-table-size parameter modifies the default value (8) for the maximum number of virtual bmacs that can be associated to the Ethernet-Segment, that is, the es-bmacs. When the source-bmac-lsb is configured, the associated es-bmac-table-size is reserved out of the total FDB. The es-bmac will consume a separate B-MAC per B-VPLS that is linked to an Ethernet-Segment.

Parameters

MAC-Lsb

Specifies the two least significant bytes of the es-bmac.

Values

1 to 65535, or xx-xx or xx:xx

size

Specifies the reserved space in the FDB for a specified es-bmac. By default the system reserves 8 entries for a specified Ethernet-Segment B-MAC.

Values

1 to 511999

Default

8

Platforms

All

source-bmac-lsb

Syntax

source-bmac-lsb mac-lsb control-pw-vc-id vc-id

no source-bmac-lsb

Context

[Tree] (config>service>sdp source-bmac-lsb)

Full Context

configure service sdp source-bmac-lsb

Description

This command defines the 16 least significant bits (lsb) which, when combined with the 32 most significant bits of the PBB source-bmac, are used as the virtual backbone MAC associated with this SDP. The virtual backbone MAC is used as the source backbone MAC for traffic received on a PBB EPIPE spoke-SDP with use-sdp-bmac configured (that is, a redundant pseudowire) and forwarded into the B-VPLS domain.

The control-pw-vc-id defines VC identifier of the spoke-SDP relating to the control pseudowire whose status is to be used to determine whether SPBM advertises this virtual backbone MAC. This is a mandatory parameter when the source-bmac-lsb is added or changed. The spoke SDP must have the parameter use-sdp-bmac for the control pseudowire to be active.

Default

no source-bmac-lsb

Parameters

mac-lsb

Specifies the 16 least significant bits of the virtual backbone MAC associated with this SDP.

Values

1 to 65535 or xx-xx or xx:xx

control-pw-vc-id vc-id

Specifies the VC identifier of the control pseudowire.

Values

1 to 4294967295

Platforms

All

source-class

source-class

Syntax

source-class source-index

no source-class [source-index]

Context

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

[Tree] (config>service>vprn>static-route-entry>ipsec-tunnel source-class)

[Tree] (config>service>vprn>static-route-entry>indirect source-class)

Full Context

configure service vprn static-route-entry next-hop source-class

configure service vprn static-route-entry ipsec-tunnel source-class

configure service vprn static-route-entry indirect source-class

Description

This command configures the policy accounting source-class index to be used when incrementing accounting statistic for traffic matching the associated static route.

If source route policy accounting is enabled and a source-class index is configured, traffic with a source IP address matches the associated static route, the source accounting statistics for the specified class will be incremented.

The no form of this command removes the associated destination-class from the associated static route nexthop.

Default

no source-class

Parameters

source-index

Specifies an integer value for the accounting source class index.

Values

1 to 255

Platforms

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

source-class

Syntax

source-class source-index

no source-class [source-index]

Context

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

[Tree] (config>router>static-route-entry>indirect source-class)

Full Context

configure router static-route-entry next-hop source-class

configure router static-route-entry indirect source-class

Description

This command configures the policy accounting source-class index to be used when incrementing accounting statistic for traffic matching the associated static route.

If source route policy accounting is enabled and a source-class index is configured, traffic with a source IP address matches the associated static route, the source accounting statistics for the specified class will be incremented.

The no form of this command removes the associated destination-class from the associated static route nexthop.

Default

no source-class

Parameters

source-index

Specifies an integer value for the accounting source class index.

Values

1 to 255

Platforms

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

source-class

Syntax

source-class index [ index]

source-class {index | all}

Context

[Tree] (config>router>policy-acct-template source-class)

Full Context

configure router policy-acct-template source-class

Description

This command configures a source class index.

The no form of this command deletes the specified source class index.

Parameters

index

Specifies the index value.

Values

1 to 255

all

Deletes all the source class indices.

Platforms

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

source-class

Syntax

source-class [value]

no source-class

Context

[Tree] (config>router>policy-options>policy-statement>entry>action source-class)

[Tree] (config>router>policy-options>policy-statement>default-action source-class)

Full Context

configure router policy-options policy-statement entry action source-class

configure router policy-options policy-statement default-action source-class

Description

This command specifies the policy accounting source class index to associate with matched routes.

Parameters

value

Specifies the default operational source-class for this policy statement.

Values

1 to 255

Platforms

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

source-destination-prefix

source-destination-prefix

Syntax

[no] source-destination-prefix

Context

[Tree] (config>cflowd>collector>aggregation source-destination-prefix)

Full Context

configure cflowd collector aggregation source-destination-prefix

Description

This command configures cflowd aggregation based on source and destination prefixes.

The no form of this command removes this type of aggregation from the collector configuration.

Platforms

All

source-ip

source-ip

Syntax

source-ip ip-address

no source-ip

Context

[Tree] (config>subscr-mgmt>shcv-policy>vpls source-ip)

Full Context

configure subscriber-mgmt shcv-policy vpls source-ip

Description

This command configures the IPv4 address to be used as source address for connectivity verification in a VPLS service.

The no form of this command reverts to the default.

Parameters

ip-address

Specifies the IPv4 address to be used as source address for connectivity verification in a VPLS service.

Platforms

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

source-ip

Syntax

source-ip ipv6-address

no source-ip

Context

[Tree] (config>service>ies>sub-if>wlan-gw>pool-manager>dhcp6-client source-ip)

[Tree] (config>service>vprn>sub-if>wlan-gw>pool-manager>dhcp6-client source-ip)

Full Context

configure service ies subscriber-interface wlan-gw pool-manager dhcpv6-client source-ip

configure service vprn subscriber-interface wlan-gw pool-manager dhcpv6-client source-ip

Description

This command specifies the source-ip to be used by the DHCPv6 client.

The no form of this command removes the specific source-ip. In this case the DHCPv6 client will fall back to the IP address configured on the outgoing interface.

Parameters

ipv6-address

Specifies the IPv6 address, up to 32 characters.

Platforms

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

source-ip-address

source-ip-address

Syntax

source-ip-address ip-address

no source-ip-address

Context

[Tree] (config>service>vprn>sub-if>grp-if>sap>static-host>managed-routes>route-entry>cpe-check source-ip-address)

[Tree] (config>service>ies>sub-if>grp-if>sap>static-host>managed-routes>route-entry>cpe-check source-ip-address)

Full Context

configure service vprn subscriber-interface group-interface sap static-host managed-routes route-entry cpe-check source-ip-address

configure service ies subscriber-interface group-interface sap static-host managed-routes route-entry cpe-check source-ip-address

Description

This command configures the source IP address used in ICMP messages. When not specified, the system uses the address of the appropriate address family.

The no form of this command removes the IP address.

Parameters

ip-address

Specifies the source IP address.

Values

ipv4-prefix: a.b.c.d

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

Platforms

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

source-ip-origin

source-ip-origin

Syntax

source-ip-origin {interface | vrrp}

no source-ip-origin

Context

[Tree] (config>subscr-mgmt>shcv-policy>layer-3 source-ip-origin)

Full Context

configure subscriber-mgmt shcv-policy layer-3 source-ip-origin

Description

This command selects the source IP address to be used for SHCV messages.

The no form of this command reverts to the default.

Parameters

interface

Specifies to use the interface IP as the source address of SHCV.

vrrp

Specifies to use the VRRP configured IP as the source address of SHCV.

Platforms

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

source-mac

source-mac

Syntax

source-mac ieee-address

no source-mac

Context

[Tree] (config>subscr-mgmt>shcv-policy>vpls source-mac)

Full Context

configure subscriber-mgmt shcv-policy vpls source-mac

Description

Specifies the MAC address to be used as source address for connectivity verification in a VPLS service.

The no form of this command reverts to the default.

Parameters

ieee-address

Specifies the 48-bit MAC address in the xx:xx:xx:xx:xx:xx or xx-xx-xx-xx-xx-xx format.

Platforms

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

source-override

source-override

Syntax

source-override ip-address [create]

no source-override ip-address

Context

[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>channel source-override)

Full Context

configure mcast-management multicast-info-policy bundle channel source-override

Description

This command defines a multicast channel parameter override context for a specific multicast sender within the channel range. The specified sender’s IP address must be the same IP type, IPv4 or IPv6, as defined in the channel command.

The no form of this command removes the specified sender override context from the channel range.

Parameters

ip-address

Specifies either an IPv4 or IPv6 address and must be the same IP type as the containing channel command range.

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

create

The create keyword is required if creating a new source override 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 specified source override IP address already exists.

Platforms

All

source-port

source-port

Syntax

source-port port-num

no source-port

Context

[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>video source-port)

Full Context

configure mcast-management multicast-info-policy bundle video source-port

Description

This command configures the source port for upstream RET requests. The source-port port-num value is the only configuration parameter in the bundle "default” context.

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

Parameters

port-num

Specifies the source port in the received RTP multicast stream.

Values

1024 to 65535

Platforms

7450 ESS, 7750 SR, 7750 SR-s

source-port

Syntax

source-port port-id

no source-port

Context

[Tree] (config>system>sync-if-timing>ref2 source-port)

[Tree] (config>system>sync-if-timing>ref1 source-port)

Full Context

configure system sync-if-timing ref2 source-port

configure system sync-if-timing ref1 source-port

Description

This command configures the source port for timing reference ref1 or ref2. If the port is unavailable or the link is down, then the reference sources are re-evaluated according to the reference order configured in the ref-order command.

In addition to physical port on the 7750 SR, T1 or E1 channels on a channelized OC3/OC12/STM1/STM4 Circuit Emulation Service port can be specified if they are using adaptive timing.

There are restrictions on the source-port location for ref1 and ref2 based on platform. Refer to the 7450 ESS, 7750 SR, 7950 XRS, and VSR Basic System Configuration Guide.

Default

no source-port

Parameters

port-id

Identifies the physical port in the slot/mda/port, esat-id/slot/port, or pxc-id.sub-port format.

Values

slot/mda/port [.channel]

Platforms

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

source-port

Syntax

source-port port-id

no source-port

Context

[Tree] (conf>sys>sat>eth-sat>sync-if>ref2 source-port)

[Tree] (conf>sys>sat>eth-sat>sync-if>ref1 source-port)

Full Context

configure system satellite eth-sat sync-if-timing ref2 source-port

configure system satellite eth-sat sync-if-timing ref1 source-port

Description

This command configures the source port used for the input reference to the frequency clock. The port can be any port of the Ethernet satellite.

The no form of this command removes the configuration.

Default

no source-port

Parameters

port-id

Specifies the physical port.

port-id

slot/mda/port

eth-sat-id

esat-<id>/<slot>/[u]<port>

esat

keyword

id

1 to 20

u

keyword for uplink port

Platforms

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

source-port

Syntax

source-port port

source-port grpc

no source-port

Context

[Tree] (config>system>management-interface>remote-management source-port)

Full Context

configure system management-interface remote-management source-port

Description

This command configures the TCP port local to this device that NISH uses to send packets to this node.

If this command is also configured for a specific manager in the config>system> management-interface>remote-management>manager context, that configuration takes precedence.

The no form of this command causes the system to select the default gRPC port, 57400.

Default

source-port grpc

Parameters

port

Specifies the TCP source port.

Values

1 to 65535

grpc

Keyword that specifies the default gRPC protocol port as the source port.

Platforms

All

source-port

Syntax

source-port port

source-port grpc

no source-port

Context

[Tree] (config>system>management-interface>remote-management>manager source-port)

Full Context

configure system management-interface remote-management manager source-port

Description

This command configures the TCP port local to this device that this NISH manager uses to send packets to this node.

This command takes precedence over the same command configured in the global context (config>system>management-interface>remote-management).

The no form of this command causes the source port to be inherited from the global context (config>system>management-interface>remote-management).

Parameters

port

Specifies the TCP source port.

Values

1 to 65535

Default

57400

grpc

Keyword that specifies the default gRPC protocol port as the source port.

Platforms

All

source-prefix

source-prefix

Syntax

[no] source-prefix

Context

[Tree] (config>cflowd>collector>aggregation source-prefix)

Full Context

configure cflowd collector aggregation source-prefix

Description

This command configures cflowd aggregation based on source prefix information.

The no form of this command removes this type of aggregation from the collector configuration.

Platforms

All

source-prefix

Syntax

no source-prefix

source-prefix ipv6-address/prefix-length

Context

[Tree] (config>aaa>isa-radius-plcy>servers>ipv6 source-prefix)

Full Context

configure aaa isa-radius-policy servers ipv6 source-prefix

Description

This command configures an IPv6 prefix containing individual /128 addresses. These addresses are used as the source address for connections to IPv6 RADIUS servers.

The prefix must be large enough to accommodate all BB-ISAs or ESA VMs in the system.

The no form of this command removes the IPv6 prefix.

Default

no source-prefix

Parameters

ipv6-address/prefix-length
Specifies an IPv6 address and prefix length for the address.
Values

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

Platforms

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

source-prefix

Syntax

source-prefix ip-prefix/length nat-policy nat-policy-name

no source-prefix ip-prefix/length

Context

[Tree] (config>router>nat>inside source-prefix)

[Tree] (config>service>vprn>nat>inside source-prefix)

Full Context

configure router nat inside source-prefix

configure service vprn nat inside source-prefix

Description

This command configures the source prefix used to identify traffic for NAT processing. After the traffic is diverted to the ESA-VM or vISA, its source IP address is checked to determine if it belongs to the configured prefix. If it does, the traffic is processed by NAT, otherwise, it is dropped.

The no form of this command removes the source prefix used to identify traffic for NAT processing.

Parameters

nat-policy-name

Specifies the NAT policy name, up to 32 characters.

Platforms

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

source-prefix-list

source-prefix-list

Syntax

source-prefix-list prefix-list-name

no source-prefix-list

Context

[Tree] (config>service>vprn>nat>inside source-prefix-list)

[Tree] (config>router>nat>inside source-prefix-list)

Full Context

configure service vprn nat inside source-prefix-list

configure router nat inside source-prefix-list

Description

This command references the nat-prefix-list that contains source IP addresses on the inside (private side).

The source IP addresses on the inside must be known in advance in a dnat-only instance. This is required so the corresponding routes can be installed in the routing table and thus the downstream traffic is properly routed towards the MS-ISAs where the original translation was performed (and state is kept).

In the dnat-only case, it is mandatory that the inside (private side) and the outside (public side) are in separated VPRNs.

Parameters

prefix-list-name

Specifies the name, up to 32 characters in length, of the NAT prefix list that contains the source IP addresses (original IP addresses).

Platforms

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

source-prefix-only

source-prefix-only

Syntax

[no] source-prefix-only

Context

[Tree] (config>service>vprn>nat>inside>traffic-identification source-prefix-only)

[Tree] (config>router>nat>inside>traffic-identification source-prefix-only)

Full Context

configure service vprn nat inside traffic-identification source-prefix-only

configure router nat inside traffic-identification source-prefix-only

Description

This command enables the identification of traffic that is subject to NAT processing based on the source IP address in the packet.

Traffic is diverted to the ESA-VM or vISA for NAT processing using a configured destination prefix or a IPv4 filter. When this command is configured, after traffic arrives on the ESA-VM or vISA, the source IP address in the packet determines whether the traffic is processed by NAT or dropped. If the source IP address belongs to the configured source-prefix, traffic is processed by NAT. Otherwise, it is discarded.

Use the following commands to configure the source prefix:

configure service vprn nat inside source-prefix

configure router nat inside source-prefix

If traffic identification based on the source IP address is disabled, all traffic arriving to the ESA-VM or vISA is subject to NAT processing.

The no form of this command disables the identification of traffic that is subject to NAT processing.

Default

no source-prefix-only

Platforms

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

source-specific-mcac

source-specific-mcac

Syntax

[no] source-specific-mcac

Context

[Tree] (config>router>mcac>policy source-specific-mcac)

Full Context

configure router mcac policy source-specific-mcac

Description

This command specifies that both multicast group and multicast source are used for MCAC accounting. For example, if multiple, multicast joins are for the same multicast group but each are a different multicast source, the MCAC accounts for for each multicast group and source combination.

If the multicast source is configured as a subnet instead of an address, the MCAC automatically accounts for every source address within the subnet.

If the multicast source is not configured, the MCAC only accounts for the multicast groups and ignores the source address from the multicast joins. In other words, only one source is accounted for.

The no form of this specifies that only the multicast group is used for MCAC accounting. The multicast source address is not used for MCAC accounting. For example, if multiple, multicast joins are for the same multicast group but each with a different multicast source, the MCAC only accounts for the multicast group once.

Default

no source-specific-mcac

Platforms

All

source-specific-mcac

Syntax

source-specific-mcac {true | false | use-policy-settings}

Context

[Tree] (config>router>mcac>policy>bundle source-specific-mcac)

Full Context

configure router mcac policy bundle source-specific-mcac

Description

This command configures configures the the MCAC policy accounting behavior.

Default

source-specific-mcac false

Parameters

true

Keyword used to specify that both multicast group and multicast source are used for MCAC accounting. For example, if multiple, multicast joins are for the same multicast group but each has a different multicast source, the MCAC accounts for for each multicast group and source combination.

false

Keyword used to specify that only the multicast group is used for MCAC accounting. The multicast source address is not used for MCAC accounting. For example, if multiple, multicast joins are for the same multicast group but each has a different multicast source, the MCAC only accounts for the multicast group once.

use-policy-setting

Keyword used to specify that the bundle uses the source-specific accounting setting in the MCAC policy level.

Platforms

All

source-udp-port

source-udp-port

Syntax

source-udp-port udp-port-number

no source-udp-port

Context

[Tree] (config>oam-pm>session>ip source-udp-port)

Full Context

configure oam-pm session ip source-udp-port

Description

This command should only be used when the source UDP port for the session-sender twamp-test packet must be specified.

The no form of this command means the session-sender automatically assigns the source UDP port from the available dynamic (private) UDP range.

Parameters

udp-port-number

Specifies the UDP source port.

Values

64374 to 64383

Platforms

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

source-udp-port-pools

source-udp-port-pools

Syntax

source-udp-port-pools

Context

[Tree] (config>test-oam>twamp>twamp-light source-udp-port-pools)

Full Context

configure test-oam twamp twamp-light source-udp-port-pools

Description

Commands in this context configure the source UDP port pool allocation for TWAMP Light applications.

Platforms

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

source-vtep

source-vtep

Syntax

source-vtep ip-address

no source-vtep

Context

[Tree] (cfg>service>vprn>vxlan source-vtep)

Full Context

configure service vprn vxlan source-vtep

Description

This command enables the router to use the configured IPv4 address as the tunnel source IP address (source VTEP) when originating VXLAN-encapsulated packets for this VPRN service. This command does modify the next hop of the EVPN IFL routes advertised for the VPRN service.

When unconfigured, the system uses the IPv4 address as the VTEP source.

The no form of this command removes the IPv4 address as the source VTEP.

Default

no source-vtep

Parameters

ip-address

Specifies the source VTEP IP address.

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

7750 SR-1, 7750 SR-s

source-vtep-security

source-vtep-security

Syntax

[no] source-vtep-security

Context

[Tree] (config>service>vpls>vxlan source-vtep-security)

Full Context

configure service vpls vxlan source-vtep-security

Description

This command enables the outer IP Source Address lookup of incoming VXLAN packets, and discards those coming from untrusted VTEPs. The list of trusted VTEPs is shown in the show service vxlan command. Specifically, it shows the existing learned EVPN VTEPs (always trusted), and the statically configured VTEPs in any service (Epipe and VPLS).

The command is supported in VXLAN instances with static egress VTEPs or VXLAN instances with EVPN created VTEPs.

The no version of this command disables the outer IP source address lookup.

Default

no source-vtep-security

Platforms

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

source-vtep-security

Syntax

[no] source-vtep-security

Context

[Tree] (cfg>service>vprn>vxlan>instance source-vtep-security)

Full Context

configure service vprn vxlan instance source-vtep-security

Description

This command enables the lookup of the source VXLAN Termination End Point (VTEP) on received VXLAN packets and discards packets coming from untrusted VTEPs.

The no form of this command disables the lookup.

Default

no source-vtep-security

Platforms

7750 SR-1, 7750 SR-s

sp-reverse-route

sp-reverse-route

Syntax

sp-reverse-route [ignore-default-route]

no sp-reverse-route

Context

[Tree] (config>ipsec>tnl-temp sp-reverse-route)

Full Context

configure ipsec tunnel-template sp-reverse-route

Description

This command enables the system to automatically create a reverse route based on dynamic LAN-to-LAN tunnel’s TSi in private service.

If ignore-default-route is specified, the system ignores any full range traffic selector when creating a reverse route. Otherwise, the system refuses to create a CHILD_SA if any full range traffic selector is included in TSi.

The no form of this command disables sp-reverse-route.

Default

no sp-reverse-route

Parameters

ignore-default-route

Specifies to ignore any full range traffic selector in TSi.

Platforms

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

space

space

Syntax

[no] space

Context

[Tree] (config>system>management-interface>cli>md-cli>environment>command-completion space)

Full Context

configure system management-interface cli md-cli environment command-completion space

Description

This command enables completion on the space character.

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

Default

space

Platforms

All

spb

spb

Syntax

spb [isis-instance] [fid fid] [create]

no spb

Context

[Tree] (config>service>vpls spb)

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

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

Full Context

configure service vpls spb

configure service vpls sap spb

configure service vpls spoke-sdp spb

Description

This command enables Shortest Path Bridging (SPB) on a B-VPLS instance. SPB uses IS-IS that supports multiple instances, therefore an instance must be specified. The declaration of SPB in this context is the control configuration for the SPB. This is an SPB management interface and it manages the configuration for IS-IS. Various parameters that define this SPB instance are configured under this SPB instance. Several of the parameters are shared with other B-VPLS service instances using SPB.

SPB enables an instance of IS-IS protocol with the no shutdown command. Alternatively, the IS-IS protocol instance under SPB is disabled with the shutdown command in the config>service>vpls b-vpls>spb context.

A Forwarding Identifier (FID) is optionally specified which is an abstraction of the BVID used for forwarding in SPB. When no FID is configured the control VPLS is advertised with FID value 1. When a FID value is specified, the control VPLS is advertised and associated with the FID value specified. The default algorithm for any FID declared or implicit is low-path-id. When a FID is specified, the ect-algorithm can be specified for the FID and changed only when there are no VPLS, SAPs or SDP bindings associated with the FID. The FID for a control instance cannot be changed after it is created. To change a FID the SPB component would have to be shutdown, deleted and re-created with a new FID.

Note:

SPB operates with disable-learning, disable aging and discard-unknown. The state of these commands is ignored when SPB is configured.

Default

no spb

Parameters

isis-instance

Specifies the instance ID for an SPB IS-IS instance.

Values

1024 to 2047 (4 available)

Default

1024

FID

Specifies the FID value.

Values

1 to 4095

Default

1

Platforms

All

spbm-control-vpls

spbm-control-vpls

Syntax

spbm-control-vpls service-id fid fid

no spbm-control-vpls

Context

[Tree] (config>service>vpls spbm-control-vpls)

Full Context

configure service vpls spbm-control-vpls

Description

This command associates a user B-VPLS with a particular control B-VPLS and a FID. The ECT algorithm and the behavior of unicast and multicast come from the association to the FID.

A Forwarding Identifier (FID) is specified which is an abstraction of the BVID used for forwarding in SPB. The ect-algorithm is associated with the FID and can be changed only when there are no VPLS, SAPs or SDP bindings associated with the FID. The FID must be independent from the FID assigned to other services.

Parameters

service-id

The B-VPLS service identifier.

Values

1 to 2147483647 | svc-name: 64 characters max

fid

The forwarding identifier.

Values

1 to 4095

Platforms

All

spe-address

spe-address

Syntax

spe-address global-id:prefix

no spe-address

Context

[Tree] (config>service>pw-routing spe-address)

Full Context

configure service pw-routing spe-address

Description

This command configures a single S-PE Address for the node to be used for dynamic MS-PWs. This value is used for the pseudowire switching point TLV used in LDP signaling, and is the value used by pseudowire status signaling to indicate the PE that originates a pseudowire status message. Configuration of this parameter is mandatory to enable dynamic MS-PW support on a node.

If the S-PE Address is not configured, spoke-sdps that use dynamic MS-PWs and pw-routing local-prefixes cannot be configured on a T-PE. Furthermore, the node will send a label release for any label mappings received for FEC129 AII type 2.

The S-PE Address cannot be changed unless the dynamic ms-pw configuration is removed. Furthermore, changing the S-PE Address will also result in all dynamic MS-PWs for which this node is an S-PE being released. It is recommended that the S-PE Address should be configured for the life of an MS-PW configuration after reboot of the router.

The no form of this command removes the configured S-PE Address.

Default

no spe-address

Parameters

global-id

Specifies a 4-octet value that is unique to the service provider. For example, the global ID can contain the 2-octet or 4-octet value of the provider's Autonomous System Number (ASN).

Values

<global-id:prefix>:

<global-id>:{<prefix>| <ipaddress>}

global-id

1 to 4294967295

prefix

1 to 4294967295

ipaddress

a.b.c.d

Platforms

All

speed

speed

Syntax

speed {10 | 100 | 1000 | 10000 | 25000 | 40000 | 50000 | 100000}

Context

[Tree] (config>port>ethernet speed)

Full Context

configure port ethernet speed

Description

For ports that support multiple speeds, this command configures the port speed to be used. This applies to the following:

  • fast Ethernet when autonegotiate is disabled

  • 10/100/1000 Ethernet when autonegotiate is disabled

  • 10/1G ports supporting 10G SFP+ or 1G SFP

  • 40/100G ports supporting QSFP28s on non-connector-based MDAs

If the port is configured to autonegotiate this parameter is ignored. Speed cannot be configured for ports that are part of a Link Aggregation Group (LAG).

Default

dependent on port type

Parameters

10

Sets the link to 10 Mb/s speed.

100

Sets the link to 100 Mb/s speed.

1000

Sets the link to 1000 Mb/s speed.

10000

Sets the link to 10000 Mb/s speed.

25000

Sets the link to 25000 Mb/s speed.

40000

Sets the link to 40000 Mb/s speed.

50000

Sets the link to 50000 Mb/s speed.

100000

Sets the link to 100000 Mb/s speed.

Platforms

All

speed

Syntax

speed {oc3 | oc12}

no speed

Context

[Tree] (config>port>sonet-sdh speed)

Full Context

configure port sonet-sdh speed

Description

This command configures the speed of a SONET/SDH port as either OC3 or OC12. The framer for this MDA operates in groups of four. Changing the port speed for a port requires resetting the framer and causes a slight disruption on all four ports. The first framer controls ports 1,2,3,4, the second framer controls ports 5,6,7,8 and so on.

To change the port speed on a SONET/SDH port, the port must be administratively shut down and all channels must be removed. When the port speed is changed, the default channel configuration is recreated.

The no form of this command reverts back to default.

This command is supported on TDM satellite.

Default

speed oc12

Parameters

oc3

Sets the speed of the port to OC-3.

oc12

Sets the speed of the port to OC-12.

Platforms

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

speed

Syntax

speed {56 | 64}

Context

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

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

Full Context

configure port tdm ds1 channel-group speed

configure port tdm e1 channel-group speed

Description

This command sets the speed of the DS-0 channels used in the associated channel-group.

Default

speed 64

Parameters

56

Specifies that 56k byte (7-bits per byte) encoding will be used for the associated DS-0 channels. This channel speed value is only supported on the m4-chds3-as and m12-chds3-as MDAs and on DS-1 channels (ESF and SF framing) and not on E-1 (G.704) channels.

64

Specifies that 64k byte (8-bits per byte) encoding will be used for the associated DS-0 channels.

Platforms

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

speed

Syntax

speed speed

Context

[Tree] (bof speed)

Full Context

bof speed

Description

This command configures the speed for the CPM management Ethernet port when autonegotiation is disabled in the running configuration and the Boot Option File (BOF).

If the port is configured to autonegotiate, this parameter is ignored.

Available speed options are dependent on the specific CPM variant in the system.

Default

speed 100

Parameters

speed

Sets the link speed, in Mb/s.

Values

10, 100, 1000

Platforms

All

spf

spf

Syntax

[no] spf [level-number] [system-id]

Context

[Tree] (debug>router>isis spf)

Full Context

debug router isis spf

Description

This command enables debugging for IS-IS SFP.

The no form of the command disables debugging.

Parameters

system-id

When specified, only the specified system-id is debugged. A 6-octet system identifier (xxxx.xxxx.xxxx).

level-number

Specifies the interface level (1, 2, or 1 and 2).

Platforms

All

spf

Syntax

spf [type] [dest-addr]

no spf

Context

[Tree] (debug>router>ospf spf)

[Tree] (debug>router>ospf3 spf)

Full Context

debug router ospf spf

debug router ospf3 spf

Description

This command enables debugging for OSPF SPF. Information regarding overall SPF start and stop times will be shown. To see detailed information regarding the SPF calculation of a given route, the route must be specified as an optional argument.

Parameters

type

Specifies the area to debug.

Values

intra-area, inter-area, external

dest-addr

Specifies the destination IP address to debug.

Platforms

All

spf-policy

spf-policy

Syntax

spf-policy

Context

[Tree] (config>router>nat>inside spf-policy)

[Tree] (config>service>vprn>nat>inside spf-policy)

Full Context

configure router nat inside spf-policy

configure service vprn nat inside spf-policy

Description

This command enables the context to configure a SPF NAT policy.

Platforms

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

spf-wait

spf-wait

Syntax

spf-wait spf-wait [spf-initial-wait spf-initial-wait] [spf-second-wait spf-second-wait]

no spf-wait

Context

[Tree] (config>service>vpls>spb>timers spf-wait)

Full Context

configure service vpls spb timers spf-wait

Description

This command defines the maximum interval between two consecutive SPF calculations in milliseconds. Timers that determine when to initiate the first, second, and subsequent SPF calculations after a topology change occurs can be controlled with this command.

Subsequent SPF runs (if required) occur at exponentially increasing intervals of the spf-second-wait interval. For example, if the spf-second-wait interval is 1000, the next SPF runs after 2000 milliseconds, and then the next SPF runs after 4000 milliseconds, etc., until it reaches the spf-wait value. The SPF interval stays at spf-wait value until there are no more SPF runs scheduled in that interval. After a full interval without any SPF runs, the SPF interval drops back to spf-initial-wait.

Default

no spf-wait

Parameters

spf-wait

Specifies the maximum interval in milliseconds between two consecutive SPF calculations.

Values

10 to 120000

Default

10000

spf-initial-wait

Specifies the initial SPF calculation delay in milliseconds after a topology change.

Values

10 to 100000

Default

1000

spf-second-wait

Specifies the hold time in milliseconds between the first and second SPF calculation.

Values

10 to 100000

Default

1000

Platforms

All

spf-wait

Syntax

spf-wait spf-wait [spf-initial-wait spf-initial-wait] [spf-second-wait spf-second-wait]

no spf-wait

Context

[Tree] (config>service>vpls>spb>timers spf-wait)

Full Context

configure service vpls spb timers spf-wait

Description

This command defines the maximum interval between two consecutive SPF calculations in milliseconds. Timers that determine when to initiate the first, second and subsequent SPF calculations after a topology change occurs can be controlled with this command.

Subsequent SPF runs (if required) will occur at exponentially increasing intervals of the spf-second-wait interval. For example, if the spf-second-wait interval is 1000, then the next SPF will run after 2000 milliseconds, and then next SPF will run after 4000 milliseconds, and so on, until it reaches the spf-wait value. The SPF interval will stay at spf-wait value until there are no more SPF runs scheduled in that interval. After a full interval without any SPF runs, the SPF interval will drop back to spf-initial-wait.

Note:

The IS-IS timer granularity is 100 ms. Timer values are rounded down to the nearest granularity, for example a configured value of 550 ms is internally rounded down to 500 ms.

Default

spf-wait 10000 spf-initial-wait 1000 spf-second-wait 1000

Parameters

spf-wait

Specifies the maximum interval in milliseconds between two consecutive SPF calculations.

Values

10 to 120000

Default

10000

initial-wait

Specifies the initial SPF calculation delay in milliseconds after a topology change

Values

10 to 100000

Default

1000

second-wait

Specifies the hold time in milliseconds between the first and second SPF calculation

Values

10 to 100000

Default

1000

Platforms

All

spf-wait

Syntax

spf-wait spf-wait [spf-initial-wait initial-wait] [spf-second-wait second-wait]

no spf-wait

Context

[Tree] (config>service>vprn>isis>timers spf-wait)

Full Context

configure service vprn isis timers spf-wait

Description

This command configures the maximum interval, in milliseconds, between two consecutive SPF calculations. Timers that determine when to initiate the first, second, and subsequent SPF calculations after a topology change occurs are controlled with this command.

Subsequent SPF runs (if required) occur at exponentially increasing intervals of the spf-second-wait interval. For example, if the spf-second-wait interval is 1000, the next SPF will run after 2000 milliseconds, and the next SPF after 4000 milliseconds, and so on, until it reaches the spf-wait value. The SPF interval remains at the spf-wait value until no more SPF runs are scheduled in that interval. After a full interval without any SPF runs, the SPF interval drops back to the spf-initial-wait value.

Note:

The timer granularity is 100 ms. Timer values are rounded down to the nearest granularity, for example a configured value of 550 ms is internally rounded down to 500 ms.

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

Default

spf-wait 10000 spf-initial-wait 1000 spf-second-wait 1000

Parameters

spf-wait

Specifies the maximum interval, in milliseconds, between two consecutive SPF calculations.

Values

10 to 120000

initial-wait

Specifies the initial SPF calculation delay, in milliseconds, after a topology change.

Values

10 to 100000

second-wait

Specifies the hold time, in milliseconds, between the first and second SPF calculation.

Values

10 to 100000

Platforms

All

spf-wait

Syntax

spf-wait max-spf-wait [spf-initial-wait spf-initial-wait] [spf-second-wait spf-second-wait]

no spf-wait

Context

[Tree] (config>service>vprn>ospf3>timers spf-wait)

[Tree] (config>service>vprn>ospf>timers spf-wait)

Full Context

configure service vprn ospf3 timers spf-wait

configure service vprn ospf timers spf-wait

Description

This command configures the maximum interval between two consecutive SPF calculations, in milliseconds. Timers that determine when to initiate the first, second, and subsequent SPF calculations after a topology change occurs are controlled with this command.

Subsequent SPF runs (if required) occur at exponentially increasing intervals of the spf-second-wait interval. For example, if the spf-second-wait interval is 1000, the next SPF will run after 2000 milliseconds, and the next SPF after 4000 milliseconds, and so on, until it reaches the spf-wait value. The SPF interval stays at the spf-wait value until there are no more SPF runs scheduled in that interval. After a full interval without any SPF runs, the SPF interval drops back to spf-initial-wait value.

Note: The timer granularity is 10 ms if the value is less than 500 ms, and 100 ms if the value is greater than or equal to 500 ms. Timer values are rounded down to the nearest granularity; for example, a configured value of 550 ms is internally rounded down to 500 ms.

The no form of this command reverts to the default.

Default

spf-wait 10000 spf-initial-wait 1000 spf-second-wait 1000

Parameters

max-spf-wait

Specifies the maximum interval, in milliseconds, between two consecutive SPF calculations.

Values

10 to 120000

spf-initial-wait

Specifies the initial SPF calculation delay, in milliseconds, after a topology change.

Values

10 to 100000

spf-second-wait

Specifies the hold time, in milliseconds, between the first and second SPF calculation.

Values

10 to 100000

Platforms

All

spf-wait

Syntax

spf-wait max-wait [initial-wait initial-wait] [second-wait second-wait]

no spf-wait

Context

[Tree] (config>router>bgp>optimal-route-reflection spf-wait)

Full Context

configure router bgp optimal-route-reflection spf-wait

Description

This command controls the interval between consecutive SPF calculations performed by the TE DB in support of BGP optimal route reflection. The time parameters of this command implement an exponential back-off algorithm.

The no form of this command causes a return to default values.

Default

no spf-wait

Parameters

max-wait

Specifies the maximum interval in seconds between two consecutive SPF calculations.

Values

1 to 600

Default

60

initial-wait initial-wait

Specifies the initial SPF calculation delay in seconds after a topology change.

Values

1 to 300

Default

5

second-wait second-wait

Specifies the delay in seconds between the first and second SPF calculation.

Values

1 to 300

Default

15

Platforms

All

spf-wait

Syntax

spf-wait spf-wait [spf-initial-wait initial-wait] [spf-second-wait second-wait]]

no spf-wait

Context

[Tree] (config>router>isis>timers spf-wait)

Full Context

configure router isis timers spf-wait

Description

This command configures the maximum interval between two consecutive SPF calculations, in milliseconds. Timers that determine when to initiate the first, second, and subsequent SPF calculations after a topology change occurs are controlled with this command.

Subsequent SPF runs (if required) occur at exponentially increasing intervals of the spf-second-wait interval. For example, if the spf-second-wait interval is 1000, the next SPF will run after 2000 milliseconds, and the next SPF after 4000 milliseconds, and so on, until it reaches the spf-wait value. The SPF interval stays at the spf-wait value until there are no more SPF runs scheduled in that interval. After a full interval without any SPF runs, the SPF interval drops back to the spf-initial-wait value.

Note:

The timer granularity is 100 ms. Timer values are rounded down to the nearest granularity; for example, a configured value of 550 ms is internally rounded down to 500 ms.

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

Default

spf-wait 10000 spf-initial-wait 1000 spf-second-wait 1000

Parameters

spf-wait

Specifies the maximum interval, in milliseconds, between two consecutive SPF calculations.

Values

10 to 120000

initial-wait

Specifies the initial SPF calculation delay, in milliseconds, after a topology change.

Values

10 to 100000

second-wait

Specifies the hold time, in milliseconds, between the first and second SPF calculation.

Values

10 to 100000

Platforms

All

spf-wait

Syntax

spf-wait max-spf-wait [spf-initial-wait spf-initial-wait [spf-second-wait spf-second-wait]]

no spf-wait

Context

[Tree] (config>router>ospf>timers spf-wait)

[Tree] (config>router>ospf3>timers spf-wait)

Full Context

configure router ospf timers spf-wait

configure router ospf3 timers spf-wait

Description

This command configures the maximum interval between two consecutive SPF calculations, in milliseconds. Timers that determine when to initiate the first, second, and subsequent SPF calculations after a topology change occurs are controlled with this command.

Subsequent SPF runs (if required) occurs at exponentially increasing intervals of the spf-second-wait interval. For example, if the spf-second-wait interval is 1000, the next SPF will run after 2000 milliseconds, and the next SPF after 4000 milliseconds, and so on, until it reaches the spf-wait value. The SPF interval stays at the spf-wait value until there are no more SPF runs scheduled in that interval. After a full interval without any SPF runs, the SPF interval drops back to the spf-initial-wait value.

The timer must be entered in increments of 100 milliseconds. Values entered that do not match this requirement are rejected.

Note:

The timer granularity is 10 ms if the value is less than 500 ms, and 100 ms if the value is greater than or equal to 500 ms. Timer values are rounded down to the nearest granularity, for example a configured value of 550 ms is internally rounded down to 500 ms.

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

Default

spf-wait 10000 spf-initial-wait 1000 spf-second-wait 1000

Parameters

max-spf-wait

Specifies the maximum interval, in milliseconds, between two consecutive SPF calculations.

Values

10 to 120000

spf-initial-wait

Specifies the initial SPF calculation delay, in milliseconds, after a topology change.

Values

10 to 100000

spf-second-wait

Specifies the hold time, in milliseconds, between the first and second SPF calculation.

Values

10 to 100000

Platforms

All

spi

spi

Syntax

spi spi

no spi

Context

[Tree] (config>ipsec>static-sa spi)

Full Context

configure ipsec static-sa spi

Description

This command configures the SPI key value for an IPsec manual SA.

This command specifies the SPI (Security Parameter Index) used to lookup the instruction to verify and decrypt the incoming IPsec packets when the value of the direction command is inbound.

The SPI value specifies the SPI that will be used in the encoding of the outgoing packets when the when the value of the direction command is outbound. The remote node can use this SPI to lookup the instruction to verify and decrypt the packet.

If no spi is selected, then this static SA cannot be used.

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

Default

no spi

Parameters

spi

Specifies the security parameter index for this SA.

Values

256 to 16383

Platforms

All

spi-load-balancing

spi-load-balancing

Syntax

[no] spi-load-balancing

Context

[Tree] (config>service>template>vpls-template>load-balancing spi-load-balancing)

[Tree] (config>service>vpls>load-balancing spi-load-balancing)

Full Context

configure service template vpls-template load-balancing spi-load-balancing

configure service vpls load-balancing spi-load-balancing

Description

This command enables use of the SPI in hashing for ESP/AH encrypted IPv4/v6 traffic. This is a per interface setting.

The no form disables the SPI function.

Default

no spi-load-balancing

Platforms

All

spi-load-balancing

Syntax

[no] spi-load-balancing

Context

[Tree] (config>service>ies>if>load-balancing spi-load-balancing)

Full Context

configure service ies interface load-balancing spi-load-balancing

Description

This command enables use of the SPI in hashing for ESP/AH encrypted IPv4/v6 traffic. This is a per interface setting.

The no form disables the SPI function.

Default

no spi-load-balancing

Platforms

All

spi-load-balancing

Syntax

[no] spi-load-balancing

Context

[Tree] (config>service>vprn>nw-if>load-balancing spi-load-balancing)

Full Context

configure service vprn network-interface load-balancing spi-load-balancing

Description

This command enables use of the SPI in hashing for ESP/AH encrypted IPv4/v6 traffic. This is a per interface setting.

The no form disables the SPI function.

Default

no spi-load-balancing

Platforms

All

spi-load-balancing

Syntax

[no] spi-load-balancing

Context

[Tree] (config>router>if>load-balancing spi-load-balancing)

Full Context

configure router interface load-balancing spi-load-balancing

Description

This command enables use of the SPI in hashing for ESP/AH encrypted IPv4/v6 traffic. This is a per interface setting.

The no form disables the SPI function.

Default

no spi-load-balancing

Platforms

All

spi-range-index

spi-range-index

Syntax

spi-range-index 1..4

no spi-range-index

Context

[Tree] (config>isa>tunnel-grp spi-range-index)

Full Context

configure isa tunnel-group spi-range-index

Description

This command configures the SPI range index value for the tunnel group. Each index value corresponds to a subrange of SPI values from the entire SPI space to allocate to the tunnel group.

This command must be configured with a unique value across all multichassis peering systems in following cases:

  • A multichassis-enabled tunnel group contains ESA-VMs with weight.
  • The active-mda-number configurations of a tunnel group are different on different peering systems.

See the 7450 ESS, 7750 SR, and VSR Multiservice ISA and ESA Guide for more information.

The tunnel group must be shut down to modify the SPI range allocation.

The no form of this command removes the SPI range allocation for the tunnel group.

Default

no spi-range-index

Parameters

1..4
Specifies the SPI range index value.
Values
1 to 4

Platforms

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

spi-sharing-group-id

spi-sharing-group-id

Syntax

spi-sharing-group-id group-id

no spi-sharing-group-id

Context

[Tree] (config>subscr-mgmt>loc-user-db>ppp>host>ident-strings spi-sharing-group-id)

[Tree] (config>subscr-mgmt>loc-user-db>ipoe>host>ident-strings spi-sharing-group-id)

Full Context

configure subscriber-mgmt local-user-db ppp host identification-strings spi-sharing-group-id

configure subscriber-mgmt local-user-db ipoe host identification-strings spi-sharing-group-id

Description

This command configures the SLA Profile Instance (SPI) sharing group identifier for an IPoE or PPPoE session. It overrides the default SPI sharing method (def-instance-sharing) configured in the SLA profile.

When an spi-sharing-group-id is configured, the IPoE or PPPoE session shares the SLA Profile Instance with other IPoE or PPPoE sessions from the same subscriber that: have the same SLA profile associated, are active on the same SAP, and have the same group identifier.

Configuring an spi-sharing-group-id group-id for an IPoE host, when the IPoE session is disabled on the group interface, results in a setup failure.

The no form of this command returns the SPI sharing group identifier to its default.

Parameters

group-id

Specifies the SPI group identifier.

Values

0 to 65535

Platforms

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

spi-sharing-id

spi-sharing-id

Syntax

[no] spi-sharing-id

Context

[Tree] (config>subscr-mgmt>acct-plcy>include-radius-attribute spi-sharing-id)

Full Context

configure subscriber-mgmt radius-accounting-policy include-radius-attribute spi-sharing-id

Description

This command enables RADIUS accounting messages to include the Alc-SPI-Sharing-Id RADIUS attribute. Together with the SLA profile name, this attribute provides details on the applicable SPI or queuing instance for this accounting session.

The no form of this command reverts to the default.

Platforms

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

split-horizon

split-horizon

Syntax

split-horizon

no split-horizon

Context

[Tree] (config>service>vprn>bgp>group split-horizon)

[Tree] (config>service>vprn>bgp split-horizon)

[Tree] (config>service>vprn>bgp>group>neighbor split-horizon)

Full Context

configure service vprn bgp group split-horizon

configure service vprn bgp split-horizon

configure service vprn bgp group neighbor split-horizon

Description

This command enables the use of split-horizon. When applied globally, to a group, or a specific peer, split-horizon prevents routes from being reflected back to a peer that sends the best route. It applies to routes of all address families and to any type of sending peer; confed-EBGP, EBGP and IBGP.

The configuration default is no split-horizon, meaning that no effort is taken to prevent a best route from being reflected back to the sending peer.

CAUTION:

Use of the split-horizon command may have a detrimental impact on peer and route scaling and therefore operators are encouraged to use it only when absolutely needed.

The no form of this command disables split horizon command which allows the lower level to inherit the setting from an upper level.

Default

no split-horizon

Platforms

All

split-horizon

Syntax

split-horizon {enable | disable}

no split-horizon

Context

[Tree] (config>service>vprn>rip>group split-horizon)

[Tree] (config>service>vprn>rip>group>neighbor split-horizon)

[Tree] (config>service>vprn>ripng>group>neighbor split-horizon)

[Tree] (config>service>vprn>ripng split-horizon)

[Tree] (config>service>vprn>rip split-horizon)

[Tree] (config>service>vprn>ripng>group split-horizon)

Full Context

configure service vprn rip group split-horizon

configure service vprn rip group neighbor split-horizon

configure service vprn ripng group neighbor split-horizon

configure service vprn ripng split-horizon

configure service vprn rip split-horizon

configure service vprn ripng group split-horizon

Description

This command enables the use of split-horizon. RIP uses split horizon with poison reverse to protect from such problems as "counting to infinity”. Split horizon with poison reverse means that routes learned from a neighbor through a given interface are advertised in updates out of the same interface but with a metric of 16 (infinity).

The no form of this command disables the split-horizon command, which allows the lower level to inherit the setting from an upper level.

Default

split-horizon enable

Parameters

enable

Enables split horizon and poison reverse.

disable

Enables split horizon without poison reverse. This allows the routes to be readvertised on interfaces other than the interface that learned the route, with the advertised metric equaling an increment of the metric-in value.This configuration parameter can be set at three levels: global level (applies to all groups and neighbor interfaces), group level (applies to all neighbor interfaces in the group) or neighbor level (only applies to the specified neighbor interface). The most specific value is used. In particular, if no value is set (no split-horizon), the lower level inherits the setting from the less-specific level.

Platforms

All

split-horizon

Syntax

[no] split-horizon

Context

[Tree] (config>router>bgp>group split-horizon)

[Tree] (config>router>bgp split-horizon)

[Tree] (config>router>bgp>group>neighbor split-horizon)

Full Context

configure router bgp group split-horizon

configure router bgp split-horizon

configure router bgp group neighbor split-horizon

Description

This command enables the use of split-horizon. Split-horizon prevents routes from being reflected back to a peer that sends the best route. It applies to routes of all address families and to any type of sending peer; confed-EBGP, EBGP and IBGP.

The configuration default is no split-horizon, meaning that no effort is taken to prevent a best route from being reflected back to the sending peer.

Default

no split-horizon

Platforms

All

split-horizon

Syntax

split-horizon {enable | disable}

no split-horizon

Context

[Tree] (config>router>ripng>group>neighbor split-horizon)

[Tree] (config>router>ripng>group split-horizon)

[Tree] (config>router>ripng split-horizon)

[Tree] (config>router>rip split-horizon)

[Tree] (config>router>rip>group>neighbor split-horizon)

[Tree] (config>router>rip>group split-horizon)

Full Context

configure router ripng group neighbor split-horizon

configure router ripng group split-horizon

configure router ripng split-horizon

configure router rip split-horizon

configure router rip group neighbor split-horizon

configure router rip group split-horizon

Description

This command enables the use of split-horizon.

RIP uses split-horizon with poison-reverse to protect from such problems as "counting to infinity”. Split-horizon with poison reverse means that routes learned from a neighbor through a given interface are advertised in updates out of the same interface but with a metric of 16 (infinity).

The split-horizon disable command enables split horizon without poison reverse. This allows the routes to be re-advertised on interfaces other than the interface that learned the route, with the advertised metric equaling an increment of the metric-in value.

This configuration parameter can be set at three levels: global level (applies to all groups and neighbor interfaces), group level (applies to all neighbor interfaces in the group) or neighbor level (only applies to the specified neighbor interface). The most specific value is used. In particular if no value is set (no split-horizon), the setting from the less specific level is inherited by the lower level.

The no form of the command disables split horizon command which allows the lower level to inherit the setting from an upper level.

Default

enabled

Parameters

enable

Specifies enable split horizon and poison reverse.

disable

Specifies disable split horizon allowing routes to be re-advertised on the same interface on which they were learned with the advertised metric incremented by the metric-in value.

Platforms

All

split-horizon-group

split-horizon-group

Syntax

split-horizon-group [group-name] [residential-group] [create]

Context

[Tree] (config>service>vpls split-horizon-group)

Full Context

configure service vpls split-horizon-group

Description

This command creates a new split horizon group for the VPLS instance. Traffic arriving on a SAP or spoke-SDP within this split horizon group will not be copied to other SAPs or spoke-SDPs in the same split horizon group.

A split horizon group must be created before SAPs and spoke-SDPs can be assigned to the group.

The split horizon group is defined within the context of a single VPLS. The same group-name can be re-used in different VPLS instances.

Up to 30 split horizon groups can be defined per VPLS instance. Half are supported in i-VPLS.

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

Default

A split horizon group is by default not created as a residential-group.

Parameters

group-name

Specifies the name of the split horizon group to which the SDP belongs

residential-group

Defines a split horizon group as a residential split horizon group (RSHG). Doing so entails that:

a) SAPs which are members of this Residential Split Horizon Group will have:

  • Double-pass queuing at ingress as default setting (can be disabled)

  • STP disabled (cannot be enabled)

  • ARP reply agent enabled per default (can be disabled)

  • MAC pinning enabled per default (can be disabled)

  • Downstream broadcast packets are discarded thus also blocking the unknown, flooded traffic

  • Downstream multicast packets are allowed when IGMP snooping is enabled

b) Spoke SDPs which are members of this Residential Split Horizon Group will have:

  • Downstream multicast traffic supported

  • Double-pass queuing is not applicable

  • STP is disabled (can be enabled)

  • ARP reply agent is not applicable (dhcp-lease-states are not supported on spoke-SDPs)

  • MAC pinning enabled per default (can be disabled)

Platforms

All

split-horizon-group

Syntax

split-horizon-group group-name

Context

[Tree] (config>subscr-mgmt>msap-policy>vpls-only split-horizon-group)

Full Context

configure subscriber-mgmt msap-policy vpls-only-sap-parameters split-horizon-group

Description

This command specifies the name of the split horizon group to which the MSAP belongs.

Parameters

group-name

Specifies the split horizon group name up to 32 characters.

Platforms

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

split-horizon-group

Syntax

split-horizon-group name

no split-horizon-group

Context

[Tree] (config>service>vpls>bgp-evpn>srv6 split-horizon-group)

[Tree] (config>service>vpls>bgp-evpn>mpls split-horizon-group)

Full Context

configure service vpls bgp-evpn segment-routing-v6 split-horizon-group

configure service vpls bgp-evpn mpls split-horizon-group

Description

This command allows the user to configure an explicit split-horizon-group for all BGP-EVPN MPLS or SRv6 destinations that can be shared by other SAPs and/or spoke SDPs. The use of explicit split-horizon-groups for EVPN-MPLS or SRv6 and spoke SDPs allows the integration of VPLS and EVPN-MPLS or SRv6 networks.

If the split-horizon-group command for bgp-evpn>mpls/srv6 contexts is not used, the default split-horizon-group (that contains all the EVPN destinations) is still used, but it is not possible to refer to it on SAPs/spoke SDPs. User-configured split-horizon-groups can be configured within the service context. The same group-name can be associated to SAPs, spoke SDPs, pw-templates, pw-template-bindings and EVPN-MPLS or SRv6 destinations. The configuration of bgp-evpn>mpls/srv6> split-horizon-group is only allowed if bgp-evpn>mpls/srv6 is shutdown; no changes are allowed when bgp-evpn>mpls/srv6 is no shutdown.

When the SAPs and/or spoke SDPs (manual or BGP-AD-discovered) are configured within the same split-horizon-group as the EVPN-MPLS or SRv6 endpoints, MAC addresses are still learned on them but they are not advertised in BGP-EVPN. If provider-tunnel is enabled in the bgp-evpn service, the SAPs and SDP bindings that share the same split-horizon-group of the EVPN-MPLS provider-tunnel are brought operationally down if the point-to-multipoint tunnel is operationally up.

Default

no split-horizon-group

Parameters

name

Specifies the split-horizon-group name.

Platforms

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

  • configure service vpls bgp-evpn segment-routing-v6 split-horizon-group

All

  • configure service vpls bgp-evpn mpls split-horizon-group

split-horizon-group

Syntax

split-horizon-group group-name

no split-horizon-group

Context

[Tree] (config>service>vpls>site split-horizon-group)

Full Context

configure service vpls site split-horizon-group

Description

This command configures the value of split-horizon group associated with this site.

The no form of this command reverts the default.

Default

no split-horizon-group

Parameters

group-name

Specifies a split-horizon group name

Platforms

All

split-horizon-group

Syntax

split-horizon-group group-name

no split-horizon-group

Context

[Tree] (config>service>pw-template split-horizon-group)

Full Context

configure service pw-template split-horizon-group

Description

This command creates a new split horizon group (SGH).

Comparing a "residential” SGH and a "regular” SHG is that a residential SHG:

  • Has different defaults for the SAP or SDP that belong to this group (ARP reply agent enabled (SAP only), MAC pinning enabled). These can be disabled in the configuration.

  • Does not allow enabling spanning tree (STP) on a SAP. It is allowed on an SDP.

  • Does not allow for downstream broadcast (broadcast/unknown unicast) on a SAP. It is allowed on an SDP.

  • On a SAP, downstream multicast is only allowed when IGMP is enabled (for which an MFIB state exists; only IP multicast); on a SDP, downstream mcast is allowed.

When the feature was initially introduced, residential SHGs were also using ingress shared queuing by default to increase SAP scaling.

A residential SAP (SAP that belongs to a RSHG) is used to scale the number of SAPs in a single VPLS instance. The limit depends on the hardware used and is higher for residential SAPs (where there is no need for egress multicast replication on residential SAPs) than for regular SAPs. Therefore, residential SAPs are useful in residential aggregation environments (for example, triple play networks) with a VLAN/subscriber model.

The no form of the command removes the group name from the configuration.

Parameters

group-name

Specifies the name of the split horizon group to which the SDP belongs.

residential-group

Defines a split horizon group as a residential split horizon group (RSHG). Doing so entails that:

  • SAPs which are members of this Residential Split Horizon Group will have:

    • Double-pass queuing at ingress as default setting (can be disabled)

    • STP disabled (cannot be enabled)

    • ARP reply agent enabled per default (can be disabled)

    • MAC pinning enabled per default (can be disabled)

    • Downstream Broadcast packets are discarded thus also blocking the unknown, flooded traffic

    • Downstream Multicast packets are allowed when IGMP snooping is enabled

  • Spoke SDPs which are members of this Residential Split Horizon Group will have:

    • Downstream multicast traffic supported

    • Double-pass queuing is not applicable

    • STP is disabled (can be enabled)

    • ARP reply agent is not applicable on the 7750 SR and 7450 ESS (dhcp-lease-states are not supported on spoke SDPs)

    • MAC pinning enabled per default (can be disabled)

Platforms

All

spoke-sdp

spoke-sdp

Syntax

spoke-sdp sdp-id[:vc-id] [vc-type {ether | vlan}] [split-horizon-group group-name] [create]

no spoke-sdp sdp-id[:vc-id]

Context

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

Full Context

configure service vpls spoke-sdp

Description

This command binds a service to an existing service destination point (SDP). A spoke SDP is treated like the equivalent of a traditional bridge "port” where flooded traffic received on the spoke SDP is replicated on all other "ports” (other spoke and mesh SDPs or SAPs) and not transmitted on the port it was received.

The SDP has an operational state which determines the operational state of the SDP within the service. For example, if the SDP is administratively or operationally down, the SDP for the service is down.

The SDP must already be defined in the config>service>sdp context in order to associate an SDP with a VPLS service. If the sdp sdp-id is not already configured, an error message is generated. If the sdp-id does exist, a binding between that sdp-id and the service is created.

SDPs must be explicitly associated and bound to a service. If an SDP is not bound to a service, no far-end devices can participate in the service.

The no form of this command removes the SDP binding from the service. The SDP configuration is not affected; only the binding of the SDP to a service. When removed, no packets are forwarded to the far-end router.

Default

No sdp-id is bound to a service.

Parameters

sdp-id

Specifies the SDP identifier

Values

1 to 32767

vc-id

Specifies the virtual circuit identifier

Values

1 to 4294967295

vc-type

This command overrides the default VC type signaled for the spoke or mesh binding to the far end of the SDP. The VC type is a 15 bit-quantity containing a value which represents the type of VC. The actual signaling of the VC type depends on the signaling parameter defined for the SDP. If signaling is disabled, the vc-type command can still be used to define the dot1q value expected by the far-end provider equipment. Changing the binding’s VC type causes the binding to signal the new VC type to the far end when signaling is enabled. VC types are derived according to IETF draft-martini-l2circuit-trans-mpls.

The VC type value for Ethernet is 0x0005.

The VC type value for an Ethernet VLAN is 0x0004.

Values

ether, vlan

ether

Defines the VC type as Ethernet. The ethernet and vlan keywords are mutually exclusive. When the VC type is not defined then the default is Ethernet for spoke SDP bindings. Defining Ethernet is the same as executing no vc-type and restores the default VC type for the spoke SDP binding. (hex 5)

vlan

Defines the VC type as VLAN. The ethernet and vlan keywords are mutually exclusive. When the VC type is not defined then the default is Ethernet for spoke SDP bindings.

The VLAN VC-type inserts one dot1q tag within each encapsulated Ethernet packet transmitted to the far end and strips one dotQ tag, if a tag is present, from traffic received on the pseudowire.

The system expects a symmetrical configuration with its peer, specifically it expects to remove the same number of VLAN tags from received traffic as it adds to transmitted traffic. As some of the related configuration parameters are local and not communicated in the signaling plane, an asymmetrical behavior cannot always be detected and so cannot be blocked. Consequently, protocol extractions will not necessarily function for asymmetrical configurations as they would with a symmetrical configurations resulting in an unexpected operation.

group-name

Specifies the name of the split horizon group to which the SDP belongs

endpoint

Specifies the service endpoint to which this SDP bind is attached. The service ID of the SDP binding must match the service ID of the service endpoint.

no endpoint

Removes the association of a spoke SDP with an explicit endpoint name

root-leaf-tag

Specifies a tagging spoke SDP under an E-Tree VPLS. When a tag SDP binding is required, it is created with a root-leaf-tag flag. Only VLAN tag SDP bindings are supported. The VLAN type must be set to VC VLAN type. The root-leaf-tag parameter indicates this SDP binding is a tag SDP that will use a default VID tag of 1 for root and 2 for leaf. The SDP binding tags egress E-Tree traffic with root and leaf VIDs as appropriate. Root and leaf VIDs are only significant between peering VPLS but the values must be consistent on each end. On ingress a tag SDP binding removes the VID tag on the interface between VPLS in the same E-Tree service. The tag SDP receives root tagged traffic and marks the traffic with a root indication internally. This option is not available on BGP EVPN-enabled E-Tree services.

leaf-ac

Specifies an access (AC) spoke SDP binding under a E-Tree VPLS as a leaf access (AC) SDP. The default E-Tree SDP binding type is a root-ac if leaf-ac or root-leaf-tag is not specified at SDP creation. This option is only available when the VPLS is designated as an E-Tree VPLS. BGP EVPN-enabled E-Tree VPLS services support the leaf-ac option.

Platforms

All

spoke-sdp

Syntax

spoke-sdp sdp-id[:vc-id] [vc-type {ether | vlan}] [split-horizon-group group-name] [create] endpoint endpoint root-leaf-tag

spoke-sdp sdp-id[:vc-id] [vc-type {ether | vlan}] [split-horizon-group group-name] [create] endpoint endpoint leaf-ac

spoke-sdp sdp-id[:vc-id] [vc-type {ether | vlan}] [split-horizon-group group-name] [create] [no-endpoint]

spoke-sdp sdp-id[:vc-id] [vc-type {ether | vlan}] [split-horizon-group group-name] [create] endpoint endpoint

spoke-sdp sdp-id[:vc-id] [vc-type {ether | vlan}] [split-horizon-group group-name] [create] [no-endpoint] leaf-ac

spoke-sdp sdp-id[:vc-id] [vc-type {ether | vlan}] [split-horizon-group group-name] [create] [no-endpoint] root-leaf-tag

no spoke-sdp sdp-id[:vc-id]

Context

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

Full Context

configure service vpls spoke-sdp

Description

This command binds a service to an existing service destination point (SDP).

A spoke SDP is treated like the equivalent of a traditional bridge port where flooded traffic received on the spoke SDP is replicated on all other ports (other spoke and mesh SDPs or SAPs) and not transmitted on the port it was received.

The SDP has an operational state which determines the operational state of the SDP within the service. For example, if the SDP is administratively or operationally down, the SDP for the service is down.

The SDP must already be defined in the config>service>sdp context in order to associate an SDP with a VPLS service. If the sdp sdp-id is not already configured, an error message is generated. If the sdp-id does exist, a binding between that sdp-id and the service is created.

SDPs must be explicitly associated and bound to a service. If an SDP is not bound to a service, no far-end 7450 ESS or 7750 SR devices can participate in the service.

The no form of this command removes the SDP binding from the service. The SDP configuration is not affected; only the binding of the SDP to a service. Once removed, no packets are forwarded to the far-end router.

Parameters

sdp-id

Specifies the SDP identifier.

Values

1 to 17407

vc-id

Specifies the virtual circuit identifier.

Values

1 to 4294967295

vc-type

This command overrides the default VC type signaled for the spoke or mesh binding to the far end of the SDP. The VC type is a 15 bit-quantity containing a value which represents the type of VC. The actual signaling of the VC type depends on the signaling parameter defined for the SDP. If signaling is disabled, the vc-type command can still be used to define the dot1q value expected by the far-end provider equipment. A change of the binding’s VC type causes the binding to signal the new VC type to the far end when signaling is enabled.

VC types are derived according to IETF draft-martini-l2circuit-trans-mpls.

The VC type value for Ethernet is 0x0005.

The VC type value for an Ethernet VLAN is 0x0004.

Values

ether, vlan

ether

Defines the VC type as Ethernet. The ethernet, vlan, and vpls keywords are mutually exclusive. When the VC type is not defined then the default is Ethernet for spoke SDP bindings. Defining Ethernet is the same as executing no vc-type and restores the default VC type for the spoke SDP binding (hex 5).

vlan

Defines the VC type as VLAN. The ethernet, vlan, and vpls keywords are mutually exclusive. When the VC type is not defined then the default is Ethernet for spoke SDP bindings. The VLAN VC-type requires at least one dot1Q tag within each encapsulated Ethernet packet transmitted to the far end.

group-name

Specifies the name of the split horizon group to which the SDP belongs.

root-leaf-tag

Specifies a SAP as a root leaf tag SDP. This option is only available when the VPLS is designated as an E-Tree VPLS.

leaf-tag-vid

Specifies to replace the outer SDP ID for leaf traffic. The leaf tag VID is only significant between peering VPLS but the values must be consistent on each end.

leaf-ac

Specifies a SDP as a leaf access (AC) SDP. The default E-Tree SAP type is root AC if leaf-ac (or root-leaf-tag) is not specified at SDP creation. This option is only available when the VPLS is designated as an E-Tree VPLS.

create

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

Platforms

All

spoke-sdp

Syntax

spoke-sdp sdp-id:vc-id [vc-type { ether | vlan}] [split-horizon-group group-name] endpoint [no-endpoint] [root-leaf-tag | leaf-ac]

no spoke-sdp sdp-id:vc-id

Context

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

Full Context

configure service vpls spoke-sdp

Description

This command binds a service to an existing service destination point (SDP). A spoke-SDP is treated like the equivalent of a traditional bridge "port” where flooded traffic received on the spoke-SDP is replicated on all other "ports” (other spoke and mesh SDPs or SAPs) and not transmitted on the port it was received.

The SDP has an operational state which determines the operational state of the SDP within the service. For example, if the SDP is administratively or operationally down, the SDP for the service will be down.

The SDP must already be defined in the config>service>sdp context in order to associate an SDP with a VPLS service. If the sdp sdp-id is not already configured, an error message is generated. If the sdp-id does exist, a binding between that sdp-id and the service is created.

SDPs must be explicitly associated and bound to a service. If an SDP is not bound to a service, no far-end devices can participate in the service.

The no form of this command removes the SDP binding from the service. The SDP configuration is not affected; only the binding of the SDP to a service. After it is removed, no packets are forwarded to the far-end router.

Parameters

sdp-id

Specifies the SDP identifier

Values

1 to 17407

vc-id

Specifies the virtual circuit identifier

Values

1 to 4294967295

vc-type

This command overrides the default VC type signaled for the spoke or mesh binding to the far end of the SDP. The VC type is a 15 bit-quantity containing a value which represents the type of VC. The actual signaling of the VC type depends on the signaling parameter defined for the SDP. If signaling is disabled, the vc-type command can still be used to define the dot1q value expected by the far-end provider equipment. A change of the bindings VC type causes the binding to signal the new VC type to the far end when signaling is enabled. VC types are derived according to IETF draft-martini-l2circuit-trans-mpls.

The VC type value for Ethernet is 0x0005.

The VC type value for an Ethernet VLAN is 0x0004.

Values

ether, vlan

ether

Defines the VC type as Ethernet. The ethernet and vlan keywords are mutually exclusive. When the VC type is not defined then the default is Ethernet for spoke-SDP bindings. Defining Ethernet is the same as executing no vc-type and restores the default VC type for the spoke-SDP binding. (hex 5)

vlan

Defines the VC type as VLAN. The ethernet and vlan keywords are mutually exclusive. When the VC type is not defined then the default is Ethernet for spoke-SDP bindings. The VLAN VC-type inserts one dot1q tag within each encapsulated Ethernet packet transmitted to the far end and strips one dotQ tag, if a tag is present, from traffic received on the pseudowire.

Note: The system expects a symmetrical configuration with its peer, specifically it expects to remove the same number of VLAN tags from received traffic as it adds to transmitted traffic. As some of the related configuration parameters are local and not communicated in the signaling plane, an asymmetrical behavior cannot always be detected and so cannot be blocked. Consequently, protocol extractions will not necessarily function for asymmetrical configurations as they would with a symmetrical configurations resulting in an unexpected operation.

group-name

Specifies the name of the split horizon group to which the SDP belongs.

endpoint

Specifies the service endpoint to which this SDP bind is attached. The service ID of the SDP binding must match the service ID of the service endpoint.

no endpoint

Removes the association of a spoke-SDP with an explicit endpoint name.

root-leaf-tag

Specifies a tagging spoke-SDP under an E-Tree VPLS. When a tag SDP binding is required, it is created with a root-leaf-tag flag. Only VLAN tag SDP bindings are supported. The VLAN type must be set to VC VLAN type. The root-leaf-tag parameter indicates this SDP binding is a tag SDP that will use a default VID tag of 1 for root and 2 for leaf. The SDP binding tags egress E-Tree traffic with root and leaf VIDs as appropriate. Root and leaf VIDs are only significant between peering VPLS but the values must be consistent on each end. On ingress a tag SDP binding removes the VID tag on the interface between VPLS in the same E-Tree service. The tag SDP receives root tagged traffic and marks the traffic with a root indication internally. This option is not available on BGP EVPN-enabled E-Tree services.

leaf-ac

Specifies an access (AC) spoke-SDP binding under a E-Tree VPLS as a leaf access (AC) SDP. The default E-Tree SDP binding type is a root-ac if leaf-ac or root-leaf-tag is not specified at SDP creation. This option is only available when the VPLS is designated as an E-Tree VPLS. BGP EVPN-enabled E-Tree VPLS services support the leaf-ac option.

Platforms

All

spoke-sdp

Syntax

spoke-sdp sdp-id[:vc-id] [vc-type {ether | vlan}] [split-horizon-group group-name] endpoint [no-endpoint] [root-leaf-tag | leaf-ac]

no spoke-sdp sdp-id[:vc-id]

Context

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

Full Context

configure service vpls spoke-sdp

Description

This command binds a service to an existing service destination point (SDP). A spoke-SDP is treated like the equivalent of a traditional bridge "port” where flooded traffic received on the spoke-SDP is replicated on all other "ports” (other spoke and mesh SDPs or SAPs) and not transmitted on the port it was received.

The SDP has an operational state which determines the operational state of the SDP within the service. For example, if the SDP is administratively or operationally down, the SDP for the service will be down.

The SDP must already be defined in the config>service>sdp context in order to associate an SDP with a VPLS service. If the sdp sdp-id is not already configured, an error message is generated. If the sdp-id does exist, a binding between that sdp-id and the service is created.

SDPs must be explicitly associated and bound to a service. If an SDP is not bound to a service, no far-end devices can participate in the service.

The no form of this command removes the SDP binding from the service. The SDP configuration is not affected; only the binding of the SDP to a service. Once removed, no packets are forwarded to the far-end router.

Default

No sdp-id is bound to a service.

Parameters

sdp-id

Specifies the SDP identifier

Values

1 to 17407

vc-id

Specifies the virtual circuit identifier

Values

1 to 4294967295

vc-type

This command overrides the default VC type signaled for the spoke or mesh binding to the far end of the SDP. The VC type is a 15 bit-quantity containing a value which represents the type of VC. The actual signaling of the VC type depends on the signaling parameter defined for the SDP. If signaling is disabled, the vc-type command can still be used to define the dot1q value expected by the far-end provider equipment. A change of the bindings VC type causes the binding to signal the new VC type to the far end when signaling is enabled. VC types are derived according to IETF draft-martini-l2circuit-trans-mpls.

The VC type value for Ethernet is 0x0005.

The VC type value for an Ethernet VLAN is 0x0004.

Values

ether, vlan

ether

Defines the VC type as Ethernet. The ethernet and vlan keywords are mutually exclusive. When the VC type is not defined then the default is Ethernet for spoke-SDP bindings. Defining Ethernet is the same as executing no vc-type and restores the default VC type for the spoke-SDP binding. (hex 5)

vlan

Defines the VC type as VLAN. The ethernet and vlan keywords are mutually exclusive. When the VC type is not defined then the default is Ethernet for spoke-SDP bindings. The VLAN VC-type inserts one dot1q tag within each encapsulated Ethernet packet transmitted to the far end and strips one dotQ tag, if a tag is present, from traffic received on the pseudowire.

Note: The system expects a symmetrical configuration with its peer, specifically it expects to remove the same number of VLAN tags from received traffic as it adds to transmitted traffic. As some of the related configuration parameters are local and not communicated in the signaling plane, an asymmetrical behavior cannot always be detected and so cannot be blocked. Consequently, protocol extractions will not necessarily function for asymmetrical configurations as they would with a symmetrical configurations resulting in an unexpected operation.

group-name

Specifies the name of the split horizon group to which the SDP belongs

endpoint

Specifies the service endpoint to which this SDP bind is attached. The service ID of the SDP binding must match the service ID of the service endpoint.

no endpoint

Removes the association of a spoke-SDP with an explicit endpoint name

root-leaf-tag

Specifies a tagging spoke-SDP under an E-Tree VPLS. When a tag SDP binding is required, it is created with a root-leaf-tag flag. Only VLAN tag SDP bindings are supported. The VLAN type must be set to VC VLAN type. The root-leaf-tag parameter indicates this SDP binding is a tag SDP that will use a default VID tag of 1 for root and 2 for leaf. The SDP binding tags egress E-Tree traffic with root and leaf VIDs as appropriate. Root and leaf VIDs are only significant between peering VPLS but the values must be consistent on each end. On ingress a tag SDP binding removes the VID tag on the interface between VPLS in the same E-Tree service. The tag SDP receives root tagged traffic and marks the traffic with a root indication internally. This option is not available on BGP EVPN-enabled E-Tree services.

leaf-ac

Specifies an access (AC) spoke-SDP binding under a E-Tree VPLS as a leaf access (AC) SDP. The default E-Tree SDP binding type is a root-ac if leaf-ac or root-leaf-tag is not specified at SDP creation. This option is only available when the VPLS is designated as an E-Tree VPLS. BGP EVPN-enabled E-Tree VPLS services support the leaf-ac option.

Platforms

All

spoke-sdp

Syntax

[no] spoke-sdp sdp-id

Context

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

Full Context

configure service vprn spoke-sdp

Description

This command binds a service to an existing service destination point (SDP).

A spoke SDP is treated like the equivalent of a traditional bridge "port” where flooded traffic received on the spoke SDP is replicated on all other "ports” (other spoke and mesh SDPs or SAPs) and not transmitted on the port it was received.

The SDP has an operational state which determines the operational state of the SDP within the service. For example, if the SDP is administratively or operationally down, the SDP for the service is down.

The SDP must already be defined in the config>service>sdp context in order to associate an SDP with a VPRN service. If the sdp sdp-id is not already configured, an error message is generated. If the sdp-id does exist, a binding between that sdp-id and the service is created.

SDPs must be explicitly associated and bound to a service. If an SDP is not bound to a service, no far-end 7750 SR devices can participate in the service.

The no form of this command removes the SDP binding from the service. The SDP configuration is not affected; only the binding of the SDP to a service. Once removed, no packets are forwarded to the far-end router.

Parameters

sdp-id

Specifies the SDP identifier. Allowed values are integers in the range of 1 and 17407 for existing SDPs.

vc-id

Specifies the virtual circuit identifier.

Values

1 to 4294967295

Platforms

All

spoke-sdp

Syntax

spoke-sdp sdp-id[:vc-id] [vc-type {ether | ipipe}] [create]

no spoke-sdp sdp-id[:vc-id]

Context

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

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

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

[Tree] (config>service>ies>redundant-interface spoke-sdp)

Full Context

configure service vprn redundant-interface spoke-sdp

configure service ies interface spoke-sdp

configure service vprn interface spoke-sdp

configure service ies redundant-interface spoke-sdp

Description

This command binds a service to an existing service destination point (SDP).

A spoke SDP is treated like the equivalent of a traditional bridge "port” where flooded traffic received on the spoke SDP is replicated on all other "ports” (other spoke and mesh SDPs or SAPs) and not transmitted on the port it was received.

The SDP has an operational state which determines the operational state of the SDP within the service. For example, if the SDP is administratively or operationally down, the SDP for the service is down.

The SDP must already be defined in the config>service>sdp context in order to associate an SDP with an IES service. If the sdp sdp-id is not already configured, an error message is generated. If the sdp-id does exist, a binding between that sdp-id and the service is created.

SDPs must be explicitly associated and bound to a service. If an SDP is not bound to a service, no far-end devices can participate in the service.

Class-based forwarding is not supported on a spoke SDP used for termination on an IES or VPRN services. All packets are forwarded over the default LSP.

The no form of this command removes the SDP binding from the service. The SDP configuration is not affected; only the binding of the SDP to a service. Once removed, no packets are forwarded to the far-end router. The spoke SDP must be shut down first before it can be deleted from the configuration.

Default

no spoke-sdp

Parameters

sdp-id

Specifies the SDP identifier. Allowed values are integers in the range of 1 and 17407 for existing SDPs.

vc-id

Specifies the virtual circuit identifier.

Values

1 to 4294967295

vc-type

Specifies the encapsulation and pseudowire type for the spoke SDP.

Values

ether: specifies Ethernet pseudowire as the type of virtual circuit (VC) associated with the SDP binding

ipipe: specifies Ipipe pseudowire as the type of virtual circuit (VC) associated with the SDP binding

Default

ether

create

Keyword used to create the spoke SDP. 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

  • configure service ies redundant-interface spoke-sdp
  • configure service vprn redundant-interface spoke-sdp

All

  • configure service vprn interface spoke-sdp
  • configure service ies interface spoke-sdp

spoke-sdp

Syntax

spoke-sdp sdp-id:vc-id

no spoke-sdp

Context

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

Full Context

configure service vpls site spoke-sdp

Description

This command binds a service to an existing service destination point (SDP).

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

Parameters

sdp-id

Specifies the SDP identifier

Values

1 to 17407

vc-id

Specifies the virtual circuit identifier.

Values

1 to 429496729

Platforms

All

spoke-sdp

Syntax

spoke-sdp sdp-id[:vc-id] [no-endpoint]

spoke-sdp sdp-id[:vc-id] endpoint endpoint-name [icb]

no spoke-sdp sdp-id[:vc-id]

Context

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

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

Full Context

configure service ipipe spoke-sdp

configure service cpipe spoke-sdp

Description

This command binds a service to an existing service destination point (SDP). A spoke SDP is treated like the equivalent of a traditional bridge "port” where flooded traffic received on the spoke SDP is replicated on all other "ports” (other spoke and mesh SDPs or SAPs) and not transmitted on the port it was received.

The SDP has an operational state which determines the operational state of the SDP within the service. For example, if the SDP is administratively or operationally down, the SDP for the service will be down.

The SDP must already be defined in the config>service>sdp context in order to associate an SDP with a service. If the sdp sdp-id is not already configured, an error message is generated. If the sdp-id does exist, a binding between that sdp-id and the service is created.

SDPs must be explicitly associated and bound to a service. If an SDP is not bound to a service, no far-end SR/ESS devices can participate in the service.

The no form of this command removes the SDP binding from the service. The SDP configuration is not affected; only the binding of the SDP to a service. Once removed, no packets are forwarded to the far-end router.

Default

No sdp-id is bound to a service.

Parameters

sdp-id

The SDP identifier.

Values

1 to 32767

vc-id

The virtual circuit identifier.

Values

1 to 4294967295

no-endpoint

Adds or removes a spoke SDP association.

endpoint-name

Specifies the name of the service endpoint.

icb

Configures the spoke SDP as an inter-chassis backup SDP binding.

Platforms

All

  • configure service ipipe spoke-sdp

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

  • configure service cpipe spoke-sdp

spoke-sdp

Syntax

spoke-sdp sdp-id[:vc-id] [vc-type {ether | vlan}] [create] [no-endpoint]

spoke-sdp sdp-id[:vc-id] [vc-type {ether | vlan}] [create] endpoint endpoint-name [icb]

no spoke-sdp sdp-id[:vc-id]

Context

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

Full Context

configure service epipe spoke-sdp

Description

This command binds a service to an existing service destination point (SDP). A spoke SDP is treated like the equivalent of a traditional bridge "port” where flooded traffic received on the spoke SDP is replicated on all other "ports” (other spoke and mesh SDPs or SAPs) and not transmitted on the port it was received.

The SDP has an operational state which determines the operational state of the SDP within the service. For example, if the SDP is administratively or operationally down, the SDP for the service will be down.

The SDP must already be defined in the config>service>sdp context in order to associate an SDP with an Epipe, VPLS, VPRN, VPRN service. If the sdp sdp-id is not already configured, an error message is generated. If the sdp-id does exist, a binding between that sdp-id and the service is created.

SDPs must be explicitly associated and bound to a service. If an SDP is not bound to a service, no far-end devices can participate in the service.

This command can also be used to associate a GRE tunnel carrying Ethernet payload with an Epipe and terminate it on a PW port referenced within the same Epipe service. The spoke SDP represents a L2oGRE tunnel with SDP delivery type set to eth-gre-bridged. With this configuration, the vc-id is unused since there is no multiplexing of Ethernet payload within the same tunnel. The vc-id value is included only to maintain the expected spoke SDP structure within an EPIPE service. For L2oGRE tunnels, the vc-id can be set to any arbitrary value within its configurable range.

The no form of this command removes the SDP binding from the service. The SDP configuration is not affected; only the binding of the SDP to a service. Once removed, no packets are forwarded to the far-end router.

Default

No sdp-id is bound to a service.

Parameters

sdp-id

The SDP identifier.

Values

1 to 17407

vc-id

The virtual circuit identifier. The VC-ID is not used with L2TPv3 SDPs or L2oGRE tunnels, however it must be configured.

Values

1 to 4294967295

vc-type

This command overrides the default VC type signaled for the spoke or mesh binding to the far end of the SDP. The VC type is a 15 bit-quantity containing a value which represents the type of VC. The actual signaling of the VC type depends on the signaling parameter defined for the SDP. If signaling is disabled, the vc-type command can still be used to define the dot1q value expected by the far-end provider equipment. A change of the bindings VC type causes the binding to signal the new VC type to the far end when signaling is enabled.

VC types are derived according to IETF draft-martini-l2circuit-trans-mpls.

The VC type value for Ethernet is 0x0005.

The VC type value for an Ethernet VLAN is 0x0004.

Values

ethernet

ether

Defines the VC type as Ethernet. The ethernet and vlan keywords are mutually exclusive. When the VC type is not defined then the default is Ethernet for spoke SDP bindings. Defining Ethernet is the same as executing no vc-type and restores the default VC type for the spoke SDP binding.

vlan

Defines the VC type as VLAN. The top VLAN tag, if a VLAN tag is present, is stripped from traffic received on the pseudowire, and a VLAN tag is inserted when forwarding into the pseudowire. The ethernet and vlan keywords are mutually exclusive. When the VC type is not defined then the default is Ethernet for spoke SDP bindings.

The VLAN VC-type requires at least one dot1q tag within each encapsulated Ethernet packet transmitted to the far end.

Note: The system expects a symmetrical configuration with its peer, specifically it expects to remove the same number of VLAN tags from received traffic as it adds to transmitted traffic. As some of the related configuration parameters are local and not communicated in the signaling plane, an asymmetrical behavior cannot always be detected and so cannot be blocked. Consequently, protocol extractions will not necessarily function for asymmetrical configurations as they would with a symmetrical configurations resulting in an unexpected operation.

no-endpoint

Removes the association of a spoke SDP with an explicit endpoint name.

endpoint-name

Specifies the name of the service endpoint.

icb

Specifies the spoke SDP as an inter-chassis backup SDP binding.

Platforms

All

spoke-sdp

Syntax

[no] spoke-sdp spoke-id

Context

[Tree] (config>service>vpls>mac-move>secondary-ports spoke-sdp)

[Tree] (config>service>vpls>mac-move>primary-ports spoke-sdp)

Full Context

configure service vpls mac-move secondary-ports spoke-sdp

configure service vpls mac-move primary-ports spoke-sdp

Description

This command declares a specified spoke-SDP as a primary (or secondary) VPLS port.

Parameters

spoke-id

Specifies the SDP ID to configure as the primary VPLS port

Values

1 to 17407

vc-id

Specifies the virtual circuit identifier

Values

1 to 4294967295

Platforms

All

spoke-sdp

Syntax

spoke-sdp sdp-id:vc-id [create]

no spoke-sdp sdp-id:vc-id

Context

[Tree] (config>service>ies>aarp-interface spoke-sdp)

Full Context

configure service ies aarp-interface spoke-sdp

Description

This command binds a service to an existing SDP. A spoke SDP is treated like the equivalent of a traditional bridge port where flooded traffic received on the spoke SDP is replicated on all other "ports” (other spoke and mesh SDPs or SAPs) and not transmitted on the port it was received.

The SDP has an operational state which determines the operational state of the SDP within the service. For example, if the SDP is administratively or operationally down, the SDP for the service will be down.

SDPs must be explicitly associated and bound to a service. If an SDP is not bound to a service, no far-end devices can participate in the service.

The no form of this command removes the SDP binding from the service. The SDP configuration is not affected; only the binding of the SDP to a service. Once removed, no packets are forwarded to the far-end router.

Default

no spoke-sdp

Parameters

sdp-id

Specifies the SDP identifier.

Values

1 to 17407

vc-id

Specifies the virtual circuit identifier. The VC-ID is not used with L2TPv3 SDPs, however it must be configured.

Values

1 to 4294967295

create

Keyword used to create the spoke SDP.

Platforms

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

spoke-sdp

Syntax

spoke-sdp sdp-id:vc-id [create]

no spoke-sdp sdp-id:vc-id

Context

[Tree] (config>service>vprn>aarp-interface spoke-sdp)

Full Context

configure service vprn aarp-interface spoke-sdp

Description

This command binds a service to an existing SDP. A spoke SDP is treated like the equivalent of a traditional bridge port where flooded traffic received on the spoke SDP is replicated on all other "ports” (other spoke and mesh SDPs or SAPs) and not transmitted on the port it was received.

The SDP has an operational state which determines the operational state of the SDP within the service. For example, if the SDP is administratively or operationally down, the SDP for the service will be down.

SDPs must be explicitly associated and bound to a service. If an SDP is not bound to a service, no far-end devices can participate in the service.

The no form of this command removes the SDP binding from the service. The SDP configuration is not affected; only the binding of the SDP to a service. Once removed, no packets are forwarded to the far-end router.

Default

no spoke-sdp

Parameters

sdp-id

Specifies the SDP identifier.

Values

1 to 17407

vc-id

The virtual circuit identifier. The VC-ID is not used with L2TPv3 SDPs, however it must be configured.

Values

1 to 4294967295

create

Keyword used to create the spoke SDP.

Platforms

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

spoke-sdp

Syntax

spoke-sdp sdp-id:vc-id [create] [no-endpoint]

spoke-sdp sdp-id:vc-id [create] endpoint name [icb]

no sdp sdp-id:vc-id

Context

[Tree] (config>mirror>mirror-dest>remote-source spoke-sdp)

[Tree] (config>mirror>mirror-dest spoke-sdp)

Full Context

configure mirror mirror-dest remote-source spoke-sdp

configure mirror mirror-dest spoke-sdp

Description

This command binds an existing (mirror) service distribution path (SDP) to the mirror destination service ID.

Spoke SDPs are used to send and receive mirrored traffic between mirror source and destination routers in a remote mirroring solution. A spoke SDP configured in the remote-source context (remote-src>spoke-sdp) is used on the destination router. A spoke SDP configured in the mirror service context (mirror-dest>spoke-sdp) is used on the source router.

The destination node should be configured with remote-src>spoke-sdp entries when using L2TPv3, MPLS-TP or LDP IPv6 LSP SDPs in the remote mirroring solution. For all other types of SDPs, remote-source>far-end entries should be used.

Spoke SDPs are not applicable when routable LI encapsulation is employed (mirror-dest>encap).

A mirror destination service that is configured for a destination router must not be configured as for a source router.

The no form of this command removes the SDP binding from the mirror destination service.

Default

An SDP ID is bound to a mirror destination service ID. If no SDP is bound to the service, the mirror destination will be local and cannot be sent to another router over the core network.

Parameters

sdp-id:vc-id

Specifies a locally unique SDP identification (ID) number. The SDP ID must exist. If the SDP ID does not exist, an error will occur and the command will not execute.

For mirror services, the vc-id defaults to the service-id. However, there are scenarios where the vc-id is being used by another service. In this case, the SDP binding cannot be created. So, to avoid this, the mirror service SDP bindings now accepts vc-ids.

Values

1 to 17407

no-endpoint

Removes the association of a SAP or a SDP with an explicit endpoint name.

name

Specifies the name of the endpoint associated with the SAP.

icb

Indicates that the SDP is of type Inter-Chassis Backup (ICB). This is a special pseudowire used for MC-LAG and pseudowire redundancy application.

An explicitly named endpoint can have a maximum of one SAP and one ICB. Once a SAP is added to the endpoint, only one more object of type ICB SDP is allowed. The ICB SDP cannot be added to the endpoint if the SAP is not part of a MC-LAG instance. This means that all other SAP types cannot exist on the same endpoint as an ICB SDP since non Ethernet SAP cannot be part of a MC-LAG instance. Conversely, a SAP which is not part of a MC-LAG instance cannot be added to an endpoint which already has an ICB SDP.

An explicitly named endpoint, which does not have a SAP object, can have a maximum of four SDPs, which can include any of the following: a single primary SDP, one or many secondary SDPs with precedence, and a single ICB SDP.

Default

Null. The user should explicitly configure this option at create time. The user can remove the ICB type simply by retyping the SDP configuration without the icb keyword.

Platforms

All

spoke-sdp

Syntax

spoke-sdp sdp-id:vc-id [create]

no spoke-sdp sdp-id:vc-id

Context

[Tree] (config>service>vprn>ip-mirror-interface spoke-sdp)

Full Context

configure service vprn ip-mirror-interface spoke-sdp

Description

This command binds a service to an existing SDP.

The SDP must already be defined in the config>service>sdp context in order to associate an SDP with the VPRN service. SDPs must be explicitly associated and bound to a service. If an SDP is not bound to a service, no far-end devices can participate in the service.

The no form of this command removes the SDP binding from the service. The SDP configuration is not affected; only the binding of the SDP to a service. Once removed, no packets are forwarded to the far-end router. The spoke SDP must be shut down before it can be deleted from the configuration.

Parameters

sdp-id

Specifies SDP identifier.

Values

1 to 32767

vc-id

Specifies the virtual circuit identifier.

Values

1 to 4294967295

create

Keyword used to create an IP mirror interface.

Platforms

All

spoke-sdp-fec

spoke-sdp-fec

Syntax

spoke-sdp-fec

spoke-sdp-fec spoke-sdp-fec-id [fec fec-type] [aii-type aii-type] [create]

spoke-sdp-fec spoke-sdp-fec-id no-endpoint

spoke-sdp-fec spoke-sdp-fec-id [fec fec-type] [aii-type aii-type] [create] endpoint name [icb]

Context

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

Full Context

configure service epipe spoke-sdp-fec

Description

This command binds a service to an existing service destination point (SDP), using a dynamic MS-PW.

A spoke SDP is treated like the equivalent of a traditional bridge "port” where flooded traffic received on the spoke SDP is replicated on all other "ports” (other spoke and mesh SDPs or SAPs) and not transmitted on the port it was received.

The SDP has an operational state which determines the operational state of the SDP within the service. For example, if the SDP is administratively or operationally down, the SDP for the service will be down.

When using dynamic MS-PWs, the particular SDP to bind-to is automatically selected based on the Target Attachment Individual Identifier (TAII) and the path to use, specified under spoke SDP FEC. The selected SDP will terminate on the first hop S-PE of the MS-PW. Therefore, an SDP must already be defined in the config>service>sdp context that reaches the first hop router of the MS-PW. The router will in order to associate an SDP with a service. If an SDP to that is not already configured, an error message is generated. If the sdp-id does exist, a binding between that sdp-id and the service is created.

It differs from the spoke-sdp command in that the spoke-sdp command creates a spoke SDP binding that uses a pseudowire with the PW ID FEC. However, the spoke-sdp-fec command enables pseudowires with other FEC types to be used. Only the Generalized ID FEC (FEC129) may be specified using this command.

The no form of this command removes the SDP binding from the service. The SDP configuration is not affected; only the binding of the SDP to a service. Once removed, no packets are forwarded to the far-end router.

Parameters

spoke-sdp-fec-id

An unsigned integer value identifying the spoke SDP.

Values

1 to 4294967295

fec-type

An unsigned integer value for the type of the FEC used by the MS-PW.

Values

129 to 130

aii-type

An unsigned integer value for the Attachment Individual Identifier (AII) type used to identify the MS-PW endpoints.

Values

1 to 2

endpoint-name

Specifies the name of the service endpoint.

no endpoint

Adds or removes a spoke SDP association.

icb

Configures the spoke SDP as an inter-chassis backup SDP binding.

Platforms

All

spt-switchover-threshold

spt-switchover-threshold

Syntax

spt-switchover-threshold {grp-ip-address/mask | grp-ip-address netmask} spt-threshold

spt-switchover-threshold grp-ipv6-addr/prefix-length spt-threshold

no spt-switchover-threshold {grp-ip-address/mask | grp-ip-address netmask}

no spt-switchover-threshold grp-ipv6-addr/prefix-length

Context

[Tree] (config>service>vprn>pim spt-switchover-threshold)

Full Context

configure service vprn pim spt-switchover-threshold

Description

This command configures a shortest path tree (SPT tree) switchover threshold for a group prefix.

Parameters

grp-ip-address

Specifies the multicast group address.

grp-ipv6-address

Specifies the multicast group address.

prefix-length

Specifies the address prefix length.

Values

grp-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

prefix-length

[1 to 128]

mask

Defines the mask of the multicast-ip-address.

Values

4 to 32

netmask

The subnet mask in dotted decimal notation.

Values

0.0.0.0 to 255.255.255.255 (network bits all 1 and host bits all 0)

spt-threshold

Specifies the configured threshold in kilobits per second (kb/s) for the group to which this (S,G) belongs. For a group G configured with a threshold, switchover to SPT for an (S,G) is attempted only if the (S,G)'s rate exceeds this configured threshold.

Platforms

All

spt-switchover-threshold

Syntax

spt-switchover-threshold {grp-ipv4-prefix/ipv4-prefix-length | grp-ipv4-prefix netmask | grp-ipv6-prefix/ipv6-prefix-length} spt-threshold

no spt-switchover-threshold {grp-ipv4-prefix/ipv4-prefix-length | grp-ipv4-prefix netmask | grp-ipv6-prefix/ipv6-prefix-length}

Context

[Tree] (config>router>pim spt-switchover-threshold)

Full Context

configure router pim spt-switchover-threshold

Description

This command configures shortest path (SPT) tree switchover thresholds for group prefixes.

PIM-SM routers with directly connected routers receive multicast traffic initially on a shared tree rooted at the Rendezvous Point (RP). Once the traffic arrives on the shared tree and the source of the traffic is known, a switchover to the SPT tree rooted at the source is attempted.

For a group that falls in the range of a prefix configured in the table, the corresponding threshold value determines when the router should switch over from the shared tree to the source specific tree. The switchover is attempted only if the traffic rate on the shared tree for the group exceeds the configured threshold.

In the absence of any matching prefix in the table, the default behavior is to switchover when the first packet is seen. In the presence of multiple prefixes matching a given group, the most specific entry is used.

The no form of this command removes the parameters from the PIM configuration.

Parameters

grp-ipv4-prefix

Specifies the group IPv4 multicast address in dotted decimal notation.

Values

a.b.c.d

ipv4-prefix-length

Specifies the length of the IPv4 prefix.

Values

4 to 32

netmask

Specifies the netmask associated with the IPv4 prefix, expressed in dotted decimal notation. Network bits must be 1, and host bits must be 0.

Values

a.b.c.d

grp-ipv6-prefix

Specifies the group IPv6 multicast address in hexadecimal notation.

Values

xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx (eight 16-bit pieces)

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

xx — 0 to FF (hex)

ipv6-prefix-length

Specifies the length of the IPv6 prefix.

Values

8 to 128

spt-threshold

Specifies the configured threshold in kilobits per second (kb/s) for a group prefix. A switchover is attempted only if the traffic rate on the shared tree for the group exceeds this configured threshold. When the infinity keyword is specified, no switchover will occur at any time, regardless of the traffic level is detected.

Values

1 to 4294967294, infinity

Platforms

All

squelch

squelch

Syntax

[no] squelch

Context

[Tree] (config>system>sync-if-timing>bits>output squelch)

Full Context

configure system sync-if-timing bits output squelch

Description

This command configures the behavior of the BITSout port when there is no valid reference selected. When enabled with no valid reference, no signal is sent out the port. When disabled with no valid reference, an AIS signal is presented along with the QL-DNU/TL-DUS SSM code if the signal format supports SSM.

Default

no squelch

Platforms

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

squelch-ingress-ctag-levels

squelch-ingress-ctag-levels

Syntax

squelch-ingress-ctag-levels [md-level [md-level]]

no squelch-ingress-ctag-levels

Context

[Tree] (config>service>vpls>spoke-sdp>eth-cfm squelch-ingress-ctag-levels)

[Tree] (config>service>vpls>sap>eth-cfm squelch-ingress-ctag-levels)

[Tree] (config>service>vpls>mesh-sdp>eth-cfm squelch-ingress-ctag-levels)

[Tree] (config>service>epipe>spoke-sdp>eth-cfm squelch-ingress-ctag-levels)

[Tree] (config>service>epipe>sap>eth-cfm squelch-ingress-ctag-levels)

Full Context

configure service vpls spoke-sdp eth-cfm squelch-ingress-ctag-levels

configure service vpls sap eth-cfm squelch-ingress-ctag-levels

configure service vpls mesh-sdp eth-cfm squelch-ingress-ctag-levels

configure service epipe spoke-sdp eth-cfm squelch-ingress-ctag-levels

configure service epipe sap eth-cfm squelch-ingress-ctag-levels

Description

This command defines the levels of the ETH-CFM packets that are silently discarded on ingress into the SAP or SDP binding from the wire that matches the service delineation of the SAP or SDP binding plus an additional VLAN, up to a maximum tag length of two tags. All ETH-CFM packets inbound to the SAP or SDP binding that match the configured levels are dropped without regard for any other ETH-CFM criteria. No statistical information or drop count is available for any ETH-CFM packet that is silently discarded by this option. The list of levels must be a complete contiguous list from 0 up to the highest level to be dropped. The command must be retyped in complete form to modify a previous configuration, if the operator does not want to delete it first. Entering the command without any valid level information removes the command from the configuration and disables the feature.

The no form of this command removes the silent discarding of previously matching ETH-CFM PDUs.

Default

no squelch-ingress-ctag-levels

Parameters

md-level

Identifies the level

Values

0 to 7

Platforms

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

squelch-ingress-levels

squelch-ingress-levels

Syntax

squelch-ingress-levels [md-level [md-level]]

no squelch-ingress-levels

Context

[Tree] (config>service>ies>if>sap>eth-cfm squelch-ingress-levels)

[Tree] (config>service>ipipe>sap>eth-cfm squelch-ingress-levels)

[Tree] (config>service>vprn>if>spoke-sdp>eth-cfm squelch-ingress-levels)

[Tree] (config>service>vprn>if>sap>eth-cfm squelch-ingress-levels)

[Tree] (config>service>epipe>sap>eth-cfm squelch-ingress-levels)

[Tree] (config>service>vpls>spoke-sdp>eth-cfm squelch-ingress-levels)

[Tree] (config>service>vprn>sub-if>grp-if>sap>eth-cfm squelch-ingress-levels)

[Tree] (config>service>vpls>mesh-sdp>eth-cfm squelch-ingress-levels)

[Tree] (config>service>ies>sub-if>grp-if>sap>eth-cfm squelch-ingress-levels)

[Tree] (config>service>vpls>sap>eth-cfm squelch-ingress-levels)

[Tree] (config>service>template>vpls-sap-template>eth-cfm squelch-ingress-levels)

[Tree] (config>service>ies>if>spoke-sdp>eth-cfm squelch-ingress-levels)

[Tree] (config>service>epipe>spoke-sdp>eth-cfm squelch-ingress-levels)

Full Context

configure service ies interface sap eth-cfm squelch-ingress-levels

configure service ipipe sap eth-cfm squelch-ingress-levels

configure service vprn interface spoke-sdp eth-cfm squelch-ingress-levels

configure service vprn interface sap eth-cfm squelch-ingress-levels

configure service epipe sap eth-cfm squelch-ingress-levels

configure service vpls spoke-sdp eth-cfm squelch-ingress-levels

configure service vprn subscriber-interface group-interface sap eth-cfm squelch-ingress-levels

configure service vpls mesh-sdp eth-cfm squelch-ingress-levels

configure service ies subscriber-interface group-interface sap eth-cfm squelch-ingress-levels

configure service vpls sap eth-cfm squelch-ingress-levels

configure service template vpls-sap-template eth-cfm squelch-ingress-levels

configure service ies interface spoke-sdp eth-cfm squelch-ingress-levels

configure service epipe spoke-sdp eth-cfm squelch-ingress-levels

Description

This command defines the levels of the ETH-CFM packets that are silently discarded on ingress into the SAP or SDP binding from the wire that matches the service delineation of the SAP or SDP binding. All ETH-CFM packets inbound to the SAP or SDP binding that match the configured levels are dropped without regard for any other ETH-CFM criteria. No statistical information or drop count is available for any ETH-CFM packet that is silently discarded by this option. The operator must configure a complete contiguous list of md-levels up to the highest level that are to be dropped. The command must be retyped in complete form to modify a previous configuration, if the operator does not want to delete it first. Entering the command with no associated md-level information is equivalent to the no version of the command.

The no form of this command removes the silent discarding of previously matching ETH-CFM PDUs.

Default

no squelch-ingress-levels

Parameters

md-level

Identifies the level

Values

0 to 7

Platforms

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

  • configure service vpls mesh-sdp eth-cfm squelch-ingress-levels
  • configure service vprn interface spoke-sdp eth-cfm squelch-ingress-levels
  • configure service vprn interface sap eth-cfm squelch-ingress-levels
  • configure service vpls sap eth-cfm squelch-ingress-levels
  • configure service template vpls-sap-template eth-cfm squelch-ingress-levels
  • configure service vpls spoke-sdp eth-cfm squelch-ingress-levels
  • configure service epipe sap eth-cfm squelch-ingress-levels
  • configure service ies interface spoke-sdp eth-cfm squelch-ingress-levels
  • configure service ies interface sap eth-cfm squelch-ingress-levels
  • configure service epipe spoke-sdp eth-cfm squelch-ingress-levels
  • configure service ipipe sap eth-cfm squelch-ingress-levels

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

  • configure service ies subscriber-interface group-interface sap eth-cfm squelch-ingress-levels
  • configure service vprn subscriber-interface group-interface sap eth-cfm squelch-ingress-levels

sr-isis

sr-isis

Syntax

[no] sr-isis

Context

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

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

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

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

Full Context

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

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

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

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

Description

This command selects the Segment Routing (SR) tunnel type programed by an IS-IS instance in TTM.

When the sr-isis value (or sr-ospf) is enabled, an SR tunnel to the BGP next hop is selected in the TTM from the lowest-numbered IS-IS (OSPF) instance.

The no form of this command disables the SR-ISIS setting for the auto-bind tunnel.

Default

no sr-isis

Platforms

All

sr-isis

Syntax

[no] sr-isis

Context

[Tree] (config>router>static-route-entry>indirect>tunnel-next-hop>resolution-filter sr-isis)

Full Context

configure router static-route-entry indirect tunnel-next-hop resolution-filter sr-isis

Description

This command enables the use of SR-ISIS sourced tunnel entries in the TTM to resolve the associated static route next hop.

Default

no sr-isis

Platforms

All

sr-isis

Syntax

[no] sr-isis

Context

[Tree] (config>service>sdp sr-isis)

Full Context

configure service sdp sr-isis

Description

This command configures an MPLS SDP of LSP type ISIS Segment Routing. The SDP of LSP type sr-isis can be used with the far-end option. The signaling protocol for the service labels for an SDP using an SR tunnel can be configured to static (off), T-LDP (tldp), or BGP (bgp).

Platforms

All

sr-isis

Syntax

[no] sr-isis

Context

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

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

Full Context

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

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

Description

This command selects the Segment Routing (SR) tunnel type programmed by an IS-IS instance in TTM for next-hop resolution of BGP routes and labeled routes. This option allows BGP to use the segment- routing tunnel in the tunnel table submitted by the lowest preference IS-IS instance or, in case of a tie, the lowest numbered IS-IS instance.

Platforms

All

sr-isis

Syntax

[no] sr-isis

Context

[Tree] (config>oam-pm>session>ip>tunnel>mpls sr-isis)

Full Context

configure oam-pm session ip tunnel mpls sr-isis

Description

This command configures the specification of sr-isis specific tunnel information that is used to transport the test packets. Entering this context removes all other tunnel type options configured under the configure oam-pm session ip tunnel mpls context. Only a single mpls type can be configured for an OAM-PM session.

The no form of this command deletes the context and all configurations under it.

Parameters

ipv4-address

Specifies IPv4 address.

Values

ipv4-address: a.b.c.d (host bits must be 0)

Platforms

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

sr-isis

Syntax

sr-isis

Context

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

Full Context

configure service vprn auto-bind-tunnel resolution-filter sr-isis

Description

Note: This command is no longer supported and will be removed in a future release.

Platforms

All

sr-label-index

sr-label-index

Syntax

sr-label-index {value | param-name} [prefer-igp]

no sr-label-index

Context

[Tree] (config>router>policy-options>policy-statement>default-action sr-label-index)

[Tree] (config>router>policy-options>policy-statement>entry>action sr-label-index)

Full Context

configure router policy-options policy-statement default-action sr-label-index

configure router policy-options policy-statement entry action sr-label-index

Description

This command associates a BGP segment-routing label index value with all /32 BGP labeled IPv4 routes matching the entry or policy default-action.

Note:

Avoid using this action in a policy entry that matches more than one /32 label-ipv4 route, otherwise SID conflicts are created.

The sr-label-index action only takes effect in BGP peer import policies (and only on received /32 label-ipv4 routes) and in route-table-import policies associated with the label-ipv4 RIB.

The prefer-igp applies only in a route-table-import policy. If prefer-igp is specified and BGP segment-routing uses prefix-sid-range global, then BGP tries, as a first priority, to use the IGP segment routing label index for the IGP route matched by the route-table-import policy. If the IGP route does not have an SID index, or prefer-igp is not configured or prefix-sid-range is not global, BGP tries to use the label index value specified by this command.

When this action occurs in a policy applied as a peer-import policy, it can add a prefix SID attribute to a received /32 label-ipv4 route that was not sent with this attribute, or it can replace the received prefix SID attribute with a new one.

If this command specifies an index value that causes a SID conflict with another BGP route, then all conflicting BGP routes are re-advertised with label values based on dynamic allocation rather than SID-based allocation.

If this command specifies an index value that causes a SID conflict with an IGP route, the BGP route is re-advertised with a label value based on dynamic allocation rather than an SID-based allocation.

The no form of this command causes matched BGP routes to be advertised without any new or changed prefix SID attributes.

Default

no sr-label-index

Parameters

value

Specifies the BGP segment routing label index to associate with the matched route or routes.

Values

0 to 52487

param-name

Specifies the type parameter variable name, up to 32 characters. If the string contains special characters (#, ?, space), the entire string must be enclosed within double quotes. Policy parameters must start and end with at-signs (@); for example, "@variable@”.

prefer-igp

A keyword that is applicable only in route-table-import policies, to instruct BGP to borrow the SID index from the IGP route if it has an SID index and the prefix-sid-range is global.

Platforms

All

sr-labels

sr-labels

Syntax

sr-labels start start-value end end-value

no sr-labels

Context

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

Full Context

configure router mpls-labels sr-labels

Description

This command configures the range of the Segment Routing Global Block (SRGB). It is a label block which is used for assigning labels to segment routing prefix SIDs originated by this router. This range is carved from the system dynamic label range and is not instantiated by default.

This is a reserved label and once configured it cannot be used by other protocols such as RSVP, LDP, and BGP to assign a label dynamically.

Default

no sr-labels

Parameters

start-value

Specifies the start label value in the SRGB

Values

18432 to 524287 within dynamic label range | 1048575 (FP4 or FP5 only)

end-value

Specifies the end label value in the SRGB

Values

18432 to 524287 within dynamic label range | 1048575 (FP4 or FP5 only)

Platforms

All

sr-maintenance-policy

sr-maintenance-policy

Syntax

sr-maintenance-policy maintenance-policy-name

no sr-maintenance-policy

Context

[Tree] (config>router>policy-options>policy-statement>entry>action sr-maintenance-policy)

[Tree] (config>router>policy-options>policy-statement>default-action sr-maintenance-policy)

Full Context

configure router policy-options policy-statement entry action sr-maintenance-policy

configure router policy-options policy-statement default-action sr-maintenance-policy

Description

This command applies a named segment routing maintenance policy to the matching routes. It is only used for SR policy routes. The named policy must exist under the config>router>segment-routing context.

The no form of this command removes the specified maintenance policy.

Parameters

maintenance-policy-name

Specifies the name of the maintenance policy, up to 32 characters and cannot start with a space or underscore.

Platforms

All

sr-mpls

sr-mpls

Syntax

sr-mpls

Context

[Tree] (config>router>segment-routing sr-mpls)

Full Context

configure router segment-routing sr-mpls

Description

Commands in this context configure the SR MPLS properties.

Platforms

All

sr-mpls-local

sr-mpls-local

Syntax

sr-mpls-local {none | all}

Context

[Tree] (config>router>ttl-propagate sr-mpls-local)

Full Context

configure router ttl-propagate sr-mpls-local

Description

This command configures TTL or hop-limit propagation for all segment routing MPLS tunnels carrying IPv4 or IPv6 packets. This applies to IPv4 and IPv6 packets of IGP, BGP unlabelled (except 6PE), and static routes in the base router whose next hop is resolved to a Segment Routing MPLS (SR-MPLS) tunnel of any of the following types: SR-ISIS, SR-OSPF, SR-OSPF3, SR-TE LSP, and SR policy.

This command configures TTL or hop-limit propagation for CPM originated IP packets. Use the sr-mpls-transit command to configure TTL or hop-limit propagation for transit IP packets.

Default

sr-mpls-local all

Parameters

none

Keyword to specify that the IP TTL or hop limit is not propagated into the segment routing transport label stack.

all

Keyword to specify that the IP TTL or hop limit is propagated to all labels in the segment routing transport label stack.

Platforms

All

sr-mpls-transit

sr-mpls-transit

Syntax

sr-mpls-transit {none | all}

Context

[Tree] (config>router>ttl-propagate sr-mpls-transit)

Full Context

configure router ttl-propagate sr-mpls-transit

Description

This command configures TTL or hop-limit propagation for all segment routing MPLS tunnels carrying IPv4 or IPv6 packets. This applies to IPv4 and IPv6 packets of IGP, BGP unlabelled (except 6PE), and static routes in the base router whose next hop is resolved to a Segment Routing MPLS (SR-MPLS) tunnel of any of the following types: SR-ISIS, SR-OSPF, SR-OSPF3, SR-TE LSP, and SR policy.

This command configures TTL or hop-limit propagation for transit IP packets. Transit IP packets are packets of base router prefixes received on an access interface or a network interface (with or without tunnel encapsulation) and whose FIB lookup results in forwarding them over an SR-MPLS tunnel. Use the sr-mpls-local command to configure TTL or hop-limit propagation for CPM originated IP packets.

Default

sr-mpls-transit all

Parameters

none

Keyword to specify that the IP TTL or hop limit is not propagated into the segment routing transport label stack.

all

Keyword to specify that the IP TTL or hop limit is propagated to all labels in the segment routing transport label stack.

Platforms

All

sr-ospf

sr-ospf

Syntax

[no] sr-ospf

Context

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

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

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

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

Full Context

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

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

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

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

Description

This command selects the Segment Routing (SR) tunnel type programed by an OSPF instance in TTM.

When the sr-ospf (or sr-isis) value is enabled, an SR tunnel to the BGP next hop is selected in the TTM from the lowest-numbered IS-IS (OSPF) instance.

The no form of this command disables the SR-OSPF setting for the auto-bind tunnel.

Default

no sr-ospf

Platforms

All

sr-ospf

Syntax

[no] sr-ospf

Context

[Tree] (config>router>static-route-entry>indirect>tunnel-next-hop>resolution-filter sr-ospf)

Full Context

configure router static-route-entry indirect tunnel-next-hop resolution-filter sr-ospf

Description

This command enables the use of SR-OSPF sourced tunnel entries in the TTM to resolve the associated static route next hop.

Default

no sr-ospf

Platforms

All

sr-ospf

Syntax

[no] sr-ospf

Context

[Tree] (config>service>sdp sr-ospf)

Full Context

configure service sdp sr-ospf

Description

This command configures an MPLS SDP of LSP type OSPF Segment Routing. The SDP of LSP type sr-ospf can be used with the far-end option. The signaling protocol for the service labels for an SDP using an SR tunnel can be configured to static (off), T-LDP (tldp), or BGP (bgp).

Platforms

All

sr-ospf

Syntax

[no] sr-ospf

Context

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

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

Full Context

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

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

Description

This command selects the Segment Routing (SR) tunnel type programmed by an OSPF instance in TTM for next-hop resolution of BGP routes and labeled routes. This option allows BGP to use the segment routing tunnel in the tunnel table submitted by the lowest preference OSPF instance or, in case of a tie, the lowest numbered OSPF instance.

The no form of this command disables the use of SR-OSPF tunneling for next-hop resolution.

Platforms

All

sr-ospf

Syntax

[no] sr-ospf

Context

[Tree] (config>oam-pm>session>ip>tunnel>mpls sr-ospf)

Full Context

configure oam-pm session ip tunnel mpls sr-ospf

Description

This commmand configures the specification of sr-ospfv3 specific tunnel information that is used to transport the test packets. Entering this context removes all other tunnel type options configured under the configure oam-pm session ip tunnel mpls context. Only a single mpls type can be configured for an OAM-PM session.

The no form of this command deletes the context and all configurations under it.

Platforms

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

sr-ospf

Syntax

sr-ospf

Context

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

Full Context

configure service vprn auto-bind-tunnel resolution-filter sr-ospf

Description

Note: This command is no longer supported and will be removed in a future release.

Platforms

All

sr-ospf3

sr-ospf3

Syntax

[no] sr-ospf3

Context

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

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

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

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

Full Context

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

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

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

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

Description

This command selects the Segment Routing (SR) tunnel type programed by an OSPFv3 instance in TTM.

When the sr-ospf3 (or sr-isis) command is enabled, an SR tunnel to the BGP next hop is selected in the TTM from the lowest-numbered IS-IS (OSPFv3) instance.

The no form of this command disables the OSPFv3 setting for the auto-bind tunnel.

Default

no sr-ospf3

Platforms

All

sr-ospf3

Syntax

[no] sr-ospf3

Context

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

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

Full Context

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

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

Description

This command selects the IPv6 segment routing tunnel type programmed by an OSPFv3 instance in the TTMv6 for next-hop resolution of BGP routes and labeled routes. This option allows BGP to use the segment routing tunnel in the tunnel table submitted by the lowest preference OSPFv3 instance or, in case of a tie, the lowest-numbered OSPFv3 instance.

The no form of this command disables the use of SR-OSPF3 for next-hop resolution.

Default

no sr-ospf3

Platforms

All

sr-ospf3

Syntax

[no] sr-ospf3

Context

[Tree] (config>oam-pm>session>ip>tunnel>mpls sr-ospf3)

Full Context

configure oam-pm session ip tunnel mpls sr-ospf3

Description

Commands in this context configure the SR-OSPFv3 feature and sr-ospfv3 packet tunneling options for the session. Enabling this context removes all tunnel type options configured under the configure oam-pm session ip tunnel mpls context.

The no form of this command deletes the context and all configurations under it.

Platforms

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

sr-ospf3

Syntax

sr-ospf3

Context

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

Full Context

configure service vprn auto-bind-tunnel resolution-filter sr-ospf3

Description

Note: This command is no longer supported and will be removed in a future release.

Platforms

All

sr-policies

sr-policies

Syntax

sr-policies

Context

[Tree] (config>router>segment-routing sr-policies)

Full Context

configure router segment-routing sr-policies

Description

This command creates the context to configure segment routing policies. A segment routing policy specifies traffic to be matched by the policy and actions to take on the matched traffic by applying the instructions encoded in one or more segment lists.

Platforms

All

sr-policy

sr-policy

Syntax

[no] sr-policy

Context

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

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

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

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

Full Context

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

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

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

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

Description

This command selects the tunnel type for the SR policy.

The sr-policy value instructs BGP to search for an SR policy with a non-null endpoint and color value that matches the BGP next hop and color extended community value of the EVPN route.

The no form of this command disables the SR policy setting for the auto-bind tunnel.

Default

no sr-policy

Platforms

All

sr-policy

Syntax

sr-policy

sr-policy color color-id endpoint ip-address

Context

[Tree] (config>saa>test>type-multi-line>lsp-trace sr-policy)

[Tree] (config>saa>test>type-multi-line>lsp-ping sr-policy)

Full Context

configure saa test type-multi-line lsp-trace sr-policy

configure saa test type-multi-line lsp-ping sr-policy

Description

This command configures the SR policy target FEC.

Note:

The sr-policy target FEC type is supported under the OAM context and under type-multi-line node in the SAA context.

Parameters

color color

Specifies the color ID.

Values

0 to 4294967295

endpoint ip-address

Specifies the endpoint address.

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

sr-policy

Syntax

sr-policy

Context

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

Full Context

configure service vprn auto-bind-tunnel resolution-filter sr-policy

Description

Note: This command is no longer supported and will be removed in a future release.

Platforms

All

sr-policy

Syntax

[no] sr-policy

Context

[Tree] (config>oam-pm>session>ip>tunnel>mpls sr-policy)

Full Context

configure oam-pm session ip tunnel mpls sr-policy

Description

Commands in this context identify the SR policy used to tunnel IP packets for session tests.

The no form of this command disables the SR policy used to tunnel IP packets.

Default

no sr-policy

Platforms

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

sr-policy-import

sr-policy-import

Syntax

[no] sr-policy-import

Context

[Tree] (config>router>bgp sr-policy-import)

Full Context

configure router bgp sr-policy-import

Description

This command instructs BGP to import all statically-configured non-local segment routing policies from the segment routing DB into the BGP RIB so that they can be advertised, as originated routes, towards BGP peers supporting the sr-policy-ipv4 address family.

The no form of this command instructs BGP to not import any statically defined segment routing policies into BGP.

Default

no sr-policy-import

Platforms

All

sr-return-path-bfd-label

sr-return-path-bfd-label

Syntax

sr-return-path-bfd-label value | param-name

no sr-return-path-bfd-label

Context

[Tree] (config>router>policy-options>policy-statement>entry>action sr-return-path-bfd-label)

[Tree] (config>router>policy-options>policy-statement>default-action sr-return-path-bfd-label)

Full Context

configure router policy-options policy-statement entry action sr-return-path-bfd-label

configure router policy-options policy-statement default-action sr-return-path-bfd-label

Description

This command configures an additional MPLS label to add to the bottom of the label stack for the S-BFD packet and sets the S-BFD session to echo mode.

This command applies to the initiator of the S-BFD sessions. The label value can either be a binding SID for an SR policy or another MPLS path configured on the reflector router. Instead of being routed through the IGP path, the S-BFD packet returns to the initiator through the MPLS return path. This value takes precedence over the return path label value in a maintenance policy (configured using the configure router segment-routing maintenance-policy return-path-label command) that is also applied as the policy-statement action. This command can only be configured if the sr-maintenance-policy command is also configured.

The no form of this command deletes the label value. If this command is not configured and there is no return-path-label command configuration in the maintenance policy that is also applied as an action, S-BFD returns to asynchronous mode and no return path label is pushed by the initiator node. S-BFD packets for this LSP or path received by the reflector are routed through the IGP path.

Default

no sr-return-path-bfd-label

Parameters

value

Specifies the label value.

Values

32 to 1048575

param-name

Specifies the parameter name to use as the label value, which can be up to 32 characters and must start and end with an at sign (@).

Platforms

All

sr-te

sr-te

Syntax

[no] sr-te

Context

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

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

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

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

Full Context

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

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

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

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

Description

This command selects the Segment Routing (SR) Traffic Engineered (SR-TE) LSP programmed in TTM.

The sr-te value instructs the system to search for the best metric SR-TE LSP to the address of the BGP next hop. The LSP metric is provided by MPLS in the tunnel table. In the case of multiple SR-TE LSPs with the same lowest metric, BGP selects the LSP with the lowest tunnel ID.

The no form of this command disables the SR-TE LSP setting for the auto-bind tunnel.

Default

no sr-te

Platforms

All

sr-te

Syntax

[no] sr-te

Context

[Tree] (config>router>mpls>pce-initiated-lsp sr-te)

Full Context

configure router mpls pce-initiated-lsp sr-te

Description

This command enables support for SR-TE PCE-initiated LSPs.

The no form of this command removes SR-TE PCE-initiated LSP support. All PCE-initiated SR-TE LSPs are deleted.

Platforms

All

sr-te

Syntax

sr-te value

no sr-te

Context

[Tree] (config>router>mpls>tunnel-table-pref sr-te)

Full Context

configure router mpls tunnel-table-pref sr-te

Description

This command configures the tunnel table preference for an SR-TE LSP 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 that 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

sr-te 8

Parameters

value

Specifies the tunnel table preference value for SR-TE LSP.

Values

1 to 255

Default

8

Platforms

All

sr-te

Syntax

[no] sr-te

Context

[Tree] (config>router>static-route-entry>indirect>tunnel-next-hop>resolution-filter sr-te)

Full Context

configure router static-route-entry indirect tunnel-next-hop resolution-filter sr-te

Description

The sr-te value instructs the code to search for the set of lowest metric SR-TE LSPs to the address of the indirect next-hop. The LSP metric is provided by MPLS in the tunnel table. The static route treats a set of SR-TE LSPs with the same lowest metric as an ECMP set. The user has the option of configuring a list of SR-TE LSP names to be used exclusively instead of searching in the tunnel table. In that case, all LSPs must have the same LSP metric in order for the static route to use them as an ECMP set. Otherwise, only the LSPs with the lowest common metric value are selected.

Default

no sr-te

Platforms

All

sr-te

Syntax

[no] sr-te

Context

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

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

Full Context

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

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

Description

This command selects the Segment Routing (SR) tunnel type programmed by a traffic engineered (TE) instance in TTM for next-hop resolution. In the case of multiple SR-TE tunnels with the same lowest metric, BGP selects the tunnel with the lowest tunnel ID.

Platforms

All

sr-te

Syntax

[no] sr-te

Context

[Tree] (config>router>isis>igp-shortcut>tunnel-next-hop>family sr-te)

Full Context

configure router isis igp-shortcut tunnel-next-hop family sr-te

Description

This command selects the SR-TE tunnel type in the resolution of the IP prefix or SR tunnel family using IGP shortcuts.

Platforms

All

sr-te

Syntax

[no] sr-te

Context

[Tree] (config>router>ospf>igp-shortcut>tunnel-next-hop>family sr-te)

[Tree] (config>router>ospf3>igp-shortcut>tunnel-next-hop>family sr-te)

Full Context

configure router ospf igp-shortcut tunnel-next-hop family sr-te

configure router ospf3 igp-shortcut tunnel-next-hop family sr-te

Description

This command selects the SR-TE tunnel type in the resolution of the IP prefix or SR tunnel family using IGP shortcuts.

Platforms

All

sr-te

Syntax

sr-te {legacy | application-specific-link-attributes}

no sr-te

Context

[Tree] (config>router>ospf>traffic-engineering-options sr-te)

Full Context

configure router ospf traffic-engineering-options sr-te

Description

This command configures the advertisement of TE attributes of each link on a per-application basis. Two applications are supported in SR OS: RSVP-TE and SR-TE. Although the legacy mode of advertising TE attributes is supported, additional configurations are possible.

The no form of this command deletes the context.

Default

no sr-te

Parameters

legacy

Advertises the TE attributes for MPLS-enabled SR links using TE Opaque LSAs.

Note:

Do not configure the legacy mode if the network has both RSVP-TE and SR-TE attributes and the links are not congruent.

application-specific-link-attributes

Advertises TE information for MPLS-enabled SR links using the new Application Specific Link Attributes (ASLA) TLVs.

Platforms

All

sr-te

Syntax

[no] sr-te

Context

[Tree] (config>oam-pm>session>ip>tunnel>mpls sr-te)

Full Context

configure oam-pm session ip tunnel mpls sr-te

Description

This command configures specification of SR-TE specific tunnel information that is used to transport the test packets. Entering this context removes all other tunnel type options configured under the configure oam-pm session ip tunnel mpls context. Only a single mpls type can be configured for an OAM-PM session.

The no form of this command removes the SR-TE LSP name from the configuration.

Default

no override

Parameters

tcp-port

Specifies the source TCP port to be used in the test TCP header.

Values

0 to 65535

Platforms

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

sr-te

Syntax

sr-te

Context

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

Full Context

configure service vprn auto-bind-tunnel resolution-filter sr-te

Description

Note: This command is no longer supported and will be removed in a future release.

Platforms

All

sr-te-lsp

sr-te-lsp

Syntax

[no] sr-te-lsp lsp-name

Context

[Tree] (config>service>sdp sr-te-lsp)

Full Context

configure service sdp sr-te-lsp

Description

This command configures an MPLS SDP of LSP type SR-TE.

The user can specify up to 16 SR-TE LSP names. The destination address of all LSPs must match that of the SDP far-end option. Service data packets are sprayed over the set of LSPs in the SDP using the same procedures as for tunnel selection in ECMP. Each SR-TE LSP can, however, have up to 32 next-hops at the ingress LER when the first segment is a node SID-based SR tunnel. Thus, the service data packet is forwarded over one of a maximum of 16x32 next-hops.

The tunnel-far-end option is not supported. In addition, the mixed-lsp-mode option does not support the sr-te tunnel type.

The signaling protocol for the service labels for an SDP using a SR-TE LSP can be configured to static (off), T-LDP (tldp), or BGP (bgp).

Platforms

All

sr-te-resignal

sr-te-resignal

Syntax

sr-te-resignal

Context

[Tree] (config>router>mpls sr-te-resignal)

Full Context

configure router mpls sr-te-resignal

Description

Commands in this context configure the re-optimization parameters of SR-TE LSPs.

Platforms

All