s Commands – Part II

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 soft-preemption)

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

Full Context

configure router mpls lsp soft-preemption

configure router mpls lsp-template 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>ies>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)

Full Context

configure service vprn subscriber-interface group-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

configure service vprn subscriber-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>vprn>sub-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)

Full Context

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

configure service ies subscriber-interface group-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>router>dhcp6>server>lease-hold-time-for solicited-release)

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

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

Full Context

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

configure service vprn dhcp6 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>mld-policy>static>group source)

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

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

Full Context

configure subscriber-mgmt mld-policy static group source

configure subscriber-mgmt igmp-policy source

configure subscriber-mgmt igmp-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>mld-snooping>static>group source)

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

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

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

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

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

Full Context

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

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

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

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

configure service vpls sap mld-snooping static group source

configure service vpls sap igmp-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>vprn>if>sap>ip-tunnel source)

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

Full Context

configure service vprn interface sap ip-tunnel source

configure service ies 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>if>ssm-translate>grp-range source)

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

Full Context

configure router mld interface ssm-translate grp-range source

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

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>vprn>if>ipv6>dhcp6-relay source-address)

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

[Tree] (config>service>ies>sub-if>grp-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>ipv6>dhcp6>relay source-address)

Full Context

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

configure service vprn interface ipv6 dhcp6-relay source-address

configure service ies interface ipv6 dhcp6-relay source-address

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

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

configure service ies subscriber-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 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
  • configure service vprn 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

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>acct-plcy>server source-address)

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

Full Context

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

configure subscriber-mgmt authentication-policy radius-authentication-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 (#, $, spaces, and so on), 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>ipsec-tunnel source-class)

[Tree] (config>service>vprn>static-route-entry>indirect source-class)

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

Full Context

configure service vprn static-route-entry ipsec-tunnel source-class

configure service vprn static-route-entry indirect source-class

configure service vprn static-route-entry next-hop 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>indirect source-class)

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

Full Context

configure router static-route-entry indirect source-class

configure router static-route-entry next-hop 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>vprn>sub-if>wlan-gw>pool-manager>dhcp6-client source-ip)

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

Full Context

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

configure service ies 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>ref1 source-port)

[Tree] (config>system>sync-if-timing>ref2 source-port)

Full Context

configure system sync-if-timing ref1 source-port

configure system sync-if-timing ref2 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>ref1 source-port)

[Tree] (conf>sys>sat>eth-sat>sync-if>ref2 source-port)

Full Context

configure system satellite eth-sat sync-if-timing ref1 source-port

configure system satellite eth-sat sync-if-timing ref2 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>service>vprn>nat>inside source-prefix)

[Tree] (config>router>nat>inside source-prefix)

Full Context

configure service vprn nat inside source-prefix

configure router 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>router>nat>inside source-prefix-list)

[Tree] (config>service>vprn>nat>inside source-prefix-list)

Full Context

configure router nat inside source-prefix-list

configure service vprn 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>router>nat>inside>traffic-identification source-prefix-only)

[Tree] (config>service>vprn>nat>inside>traffic-identification source-prefix-only)

Full Context

configure router nat inside traffic-identification source-prefix-only

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

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>spoke-sdp spb)

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

[Tree] (config>service>vpls spb)

Full Context

configure service vpls spoke-sdp spb

configure service vpls sap spb

configure service vpls 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>e1>channel-group speed)

[Tree] (config>port>tdm>ds1>channel-group speed)

Full Context

configure port tdm e1 channel-group speed

configure port tdm ds1 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>service>vprn>nat>inside spf-policy)

[Tree] (config>router>nat>inside spf-policy)

Full Context

configure service vprn nat inside spf-policy

configure router 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>ospf3>timers spf-wait)

[Tree] (config>router>ospf>timers spf-wait)

Full Context

configure router ospf3 timers spf-wait

configure router 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) 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-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 split-horizon)

[Tree] (config>service>vprn>bgp>group split-horizon)

[Tree] (config>service>vprn>bgp>group>neighbor split-horizon)

Full Context

configure service vprn bgp split-horizon

configure service vprn bgp group 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 split-horizon)

[Tree] (config>service>vprn>ripng>group split-horizon)

[Tree] (config>service>vprn>rip>group split-horizon)

[Tree] (config>service>vprn>ripng>group>neighbor split-horizon)

[Tree] (config>service>vprn>rip>group>neighbor split-horizon)

[Tree] (config>service>vprn>ripng split-horizon)

Full Context

configure service vprn rip split-horizon

configure service vprn ripng group split-horizon

configure service vprn rip group split-horizon

configure service vprn ripng group neighbor split-horizon

configure service vprn rip group neighbor split-horizon

configure service vprn ripng 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 split-horizon)

[Tree] (config>router>bgp>group>neighbor split-horizon)

[Tree] (config>router>bgp>group split-horizon)

Full Context

configure router bgp split-horizon

configure router bgp group neighbor split-horizon

configure router bgp group 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>rip split-horizon)

[Tree] (config>router>ripng>group split-horizon)

[Tree] (config>router>rip>group split-horizon)

[Tree] (config>router>ripng>group>neighbor split-horizon)

[Tree] (config>router>ripng split-horizon)

[Tree] (config>router>rip>group>neighbor split-horizon)

Full Context

configure router rip split-horizon

configure router ripng group split-horizon

configure router rip group split-horizon

configure router ripng group neighbor split-horizon

configure router ripng split-horizon

configure router rip group neighbor 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>if spoke-sdp)

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

[Tree] (config>service>ies>redundant-interface spoke-sdp)

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

Full Context

configure service vprn interface spoke-sdp

configure service ies interface spoke-sdp

configure service ies redundant-interface spoke-sdp

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

All

  • configure service vprn interface spoke-sdp
  • configure service ies interface spoke-sdp

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

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>primary-ports spoke-sdp)

[Tree] (config>service>vpls>mac-move>secondary-ports spoke-sdp)

Full Context

configure service vpls mac-move primary-ports spoke-sdp

configure service vpls mac-move secondary-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>sap>eth-cfm squelch-ingress-ctag-levels)

[Tree] (config>service>vpls>mesh-sdp>eth-cfm squelch-ingress-ctag-levels)

[Tree] (config>service>epipe>sap>eth-cfm squelch-ingress-ctag-levels)

[Tree] (config>service>epipe>spoke-sdp>eth-cfm squelch-ingress-ctag-levels)

[Tree] (config>service>vpls>spoke-sdp>eth-cfm squelch-ingress-ctag-levels)

Full Context

configure service vpls sap eth-cfm squelch-ingress-ctag-levels

configure service vpls mesh-sdp eth-cfm squelch-ingress-ctag-levels

configure service epipe sap eth-cfm squelch-ingress-ctag-levels

configure service epipe spoke-sdp eth-cfm squelch-ingress-ctag-levels

configure service vpls spoke-sdp 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>epipe>sap>eth-cfm squelch-ingress-levels)

[Tree] (config>service>vpls>sap>eth-cfm squelch-ingress-levels)

[Tree] (config>service>vpls>spoke-sdp>eth-cfm squelch-ingress-levels)

[Tree] (config>service>ies>if>spoke-sdp>eth-cfm squelch-ingress-levels)

[Tree] (config>service>ies>if>sap>eth-cfm squelch-ingress-levels)

[Tree] (config>service>vprn>sub-if>grp-if>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>ies>sub-if>grp-if>sap>eth-cfm squelch-ingress-levels)

[Tree] (config>service>vpls>mesh-sdp>eth-cfm squelch-ingress-levels)

[Tree] (config>service>template>vpls-sap-template>eth-cfm squelch-ingress-levels)

[Tree] (config>service>ipipe>sap>eth-cfm squelch-ingress-levels)

[Tree] (config>service>epipe>spoke-sdp>eth-cfm squelch-ingress-levels)

Full Context

configure service epipe sap eth-cfm squelch-ingress-levels

configure service vpls sap eth-cfm squelch-ingress-levels

configure service vpls spoke-sdp 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 vprn subscriber-interface group-interface 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 ies subscriber-interface group-interface sap eth-cfm squelch-ingress-levels

configure service vpls mesh-sdp eth-cfm squelch-ingress-levels

configure service template vpls-sap-template eth-cfm squelch-ingress-levels

configure service ipipe sap 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 vprn interface spoke-sdp eth-cfm squelch-ingress-levels
  • configure service ies interface spoke-sdp eth-cfm squelch-ingress-levels
  • configure service vpls spoke-sdp eth-cfm squelch-ingress-levels
  • configure service template vpls-sap-template eth-cfm squelch-ingress-levels
  • configure service vpls sap eth-cfm squelch-ingress-levels
  • configure service epipe spoke-sdp eth-cfm squelch-ingress-levels
  • configure service epipe sap eth-cfm squelch-ingress-levels
  • configure service ies interface sap eth-cfm squelch-ingress-levels
  • configure service vprn interface sap eth-cfm squelch-ingress-levels
  • configure service vpls mesh-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>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)

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

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

Full Context

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

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

configure service vprn bgp-evpn 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>labeled-routes>transport-tunnel>family>resolution-filter sr-isis)

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

Full Context

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

configure router bgp next-hop-resolution shortcut-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 (#, $, spaces, and so on), 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>default-action sr-maintenance-policy)

[Tree] (config>router>policy-options>policy-statement>entry>action sr-maintenance-policy)

Full Context

configure router policy-options policy-statement default-action sr-maintenance-policy

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

[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)

Full Context

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

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

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>vpls>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)

Full Context

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

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

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>vprn>bgp-evpn>mpls>auto-bind-tunnel>resolution-filter sr-policy)

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

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

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

Full Context

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

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

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

configure service vprn bgp-ipvpn 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-ping sr-policy)

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

Full Context

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

configure saa test type-multi-line lsp-trace 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-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>default-action sr-return-path-bfd-label)

[Tree] (config>router>policy-options>policy-statement>entry>action sr-return-path-bfd-label)

Full Context

configure router policy-options policy-statement default-action sr-return-path-bfd-label

configure router policy-options policy-statement entry 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>vpls>bgp-evpn>mpls>auto-bind-tunnel>resolution-filter sr-te)

[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>epipe>bgp-evpn>mpls>auto-bind-tunnel>resolution-filter sr-te)

Full Context

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

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

src-access-list

src-access-list

Syntax

src-access-list list-name

no src-access-list list-name

Context

[Tree] (config>system>security>snmp src-access-list)

Full Context

configure system security snmp src-access-list

Description

This command configures a list of source IP addresses used to validate SNMPv1 and SNMPv2c requests after the list is associated with one or more SNMPv1 and SNMPv2c communities.

A source access list referenced by one or more community instances is used to verify the source IP addresses of an SNMP request using the community, regardless of the VPRN/VRF interface (or "Base” interface) on which the request arrived. For example, if an SNMP request arrives on an interface in VPRN "100" but the request is referencing a community, the source IP address in the packet is validated against the source address list configured for the community. This occurs regardless of whether the request is destined to a VPRN interface address and the VPRN has SNMP access enabled, or the request is destined to the base system address via GRT leaking. If the source IP address of the request message does not match the IP address of any of the src-host entries contained in the list, the request is discarded and logged as an SNMP authentication failure.

Caution:

Using source access list validation can impact the time it takes for an SR OS node to reply to an SNMP request. Nokia recommends keeping the lists short by including only the addresses that are needed, and to place SNMP managers that send the highest volume of requests, such as the NSP NFM-P, at the top of the list.

A maximum of 16 source access lists can be configured. Each source access lists can contain a maximum of 16 source hosts.

The no form of this command removes the named source access list. Users cannot remove a source access list that is referenced by one or more community instances.

Parameters

list-name

Specifies the name or key of the source access list. This parameter must begin with a letter (a-z or A-Z).

Platforms

All

src-gsn

src-gsn

Syntax

src-gsn ip address

src-gsn ip-prefix-list ip-prefix-list-name

no src-gsn

Context

[Tree] (config>app-assure>group>gtp>gtp-fltr>imsi-apn-fltr>entry src-gsn)

Full Context

configure application-assurance group gtp gtp-filter imsi-apn-filter entry src-gsn

Description

This command configures a matching condition for the GSN IP address. The IP address value is checked only against the source IP address of the GTP packets that contain an APN IE or an IMSI IE.

Parameters

ip address

Specifies a valid unicast address associated with the IMSI-APN filter entry.

Values

ipv4-address

a.b.c.d[/mask]

mask - [1..32]

ipv6-address

x:x:x:x:x:x:x:x/prefix-length

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

x - [0..FFFF]H

d - [0..255]D

prefix-length [1..128]

ip-prefix-list-name

Specifies an IP address prefix list for the source IP address match criteria, up to 32 characters.

Platforms

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

src-host

src-host

Syntax

src-host host-name address ip-address

no src-host host-name

Context

[Tree] (config>system>security>snmp>src-access-list src-host)

Full Context

configure system security snmp src-access-list src-host

Description

This command configures a source IP address entry used to validate SNMPv1 and SNMPv2c requests.

The no form of this command removes the specified entry.

Parameters

host-name

Specifies a name for the entry, up to 32 characters.

ip-address

Specifies an allowed IPv4 or IPv6 source address for SNMP requests.

Values

ipv4-address —

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

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 (hexadecimal)

d — 0 to 255 (decimal)

Platforms

All

src-ip

src-ip

Syntax

src-ip {ip-address/mask | ip-address netmask}

src-ip {ipv6-address | prefix-length}

no src-ip

Context

[Tree] (config>subscr-mgmt>cat-map>category>exh-lvl>egr-ipv6>entry>match src-ip)

[Tree] (config>subscr-mgmt>cat-map>category>exh-lvl>egr-ip>entry>match src-ip)

Full Context

configure subscriber-mgmt category-map category exhausted-credit-service-level egress-ipv6-filter-entries entry match src-ip

configure subscriber-mgmt category-map category exhausted-credit-service-level egress-ip-filter-entries entry match src-ip

Description

This command configures the source IP match condition.

The no form of this command reverts to the default.

Parameters

ipv6-address

Specifies the IPv6 address (applies only to the 7750 SR).

Values

ipv6-address

x:x:x:x:x:x:x:x (where x is [0 to FFFF]H)

x:x:x:x:x:x:d.d.d.d (where d is [0 to 255]D)

prefix-length

Specifies the prefix length (applies only to the 7750 SR).

Values

1 to 128

ip-address/mask

Specifies the IPv4 address and mask.

Values

ip-address a.b.c.d

mask 0 to 32

netmask

Specifies the mask, expressed as a dotted quad.

Values

a.b.c.d

Platforms

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

src-ip

Syntax

src-ip ip-address

no src-ip

Context

[Tree] (config>redundancy>mc>peer>mcr>l3ring>node>cv src-ip)

Full Context

configure redundancy multi-chassis peer mc-ring l3-ring ring-node connectivity-verify src-ip

Description

This command specifies the source IP address used in ring-node connectivity verification of this ring node.

The no form of this command reverts to the default.

Parameters

ip-address

Specifies the source IP address used in ring-node connectivity verification of this ring node.

Platforms

All

src-ip

Syntax

src-ip ip-address

no src-ip

Context

[Tree] (config>redundancy>mc>peer>mcr>node>cv src-ip)

Full Context

configure redundancy multi-chassis peer mc-ring ring ring-node connectivity-verify src-ip

Description

This command specifies the source IP address used in the ring-node connectivity verification of this ring node.

Default

no src-ip

Parameters

ip-address

Specifies the source IP address.

Values

a.b.c.d (no multicast address)

Platforms

All

src-ip

Syntax

src-ip {eq | neq} ip-address

src-ip {eq | neq} ip-prefix-list ip-prefix-list-name

no src-ip

Context

[Tree] (config>app-assure>group>policy>aqp>entry>match src-ip)

Full Context

configure application-assurance group policy app-qos-policy entry match src-ip

Description

This command specifies a source TCP/UDP address to use as match criteria.

Default

no src-ip

Parameters

eq

Specifies that a successful match occurs when the flow matches the specified address or prefix.

neq

Specifies that a successful match occurs when the flow does not match the specified address or prefix.

ip-address

Specifies a valid unicast address.

Values

ipv4-address

a.b.c.d[/mask]

mask - [1..32]

ipv6-address

x:x:x:x:x:x:x:x/prefix-length

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

x - [0..FFFF]H

d - [0..255]D

prefix-length [1..128]

ip-prefix-list-name

Specifies an IP prefix list name, up to 32 characters.

Platforms

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

src-ip

Syntax

src-ip ip-address

src-ip ip-prefix-list ip-prefix-list-name

no src-ip

Context

[Tree] (config>app-assure>group>sess-fltr>entry>match src-ip)

Full Context

configure application-assurance group session-filter entry match src-ip

Description

This command specifies a source TCP/UDP address to use as match criteria.

Default

no src-ip

Parameters

ip-address

Specifies a valid unicast address.

Values

ipv4-address

a.b.c.d[/mask]

mask - [1..32]

ipv6-address

x:x:x:x:x:x:x:x/prefix-length

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

x - [0..FFFF]H

d - [0..255]D

prefix-length [1..128]

ip-prefix-list-name

Specifies an IP prefix list name, up to 32 characters.

Platforms

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

src-ip

Syntax

src-ip {eq | neq} ip-address

no src-ip

Context

[Tree] (debug>app-assure>group>traffic-capture>match src-ip)

Full Context

debug application-assurance group traffic-capture match src-ip

Description

This command configures debugging on a source IP address.

Platforms

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

src-ip

Syntax

src-ip {ip-address/mask | ip-address ipv4-address-mask}

Context

[Tree] (config>li>li-filter>li-ip-filter>entry>match src-ip)

Full Context

configure li li-filter li-ip-filter entry match src-ip

Description

This command configures source IP address LI filter match criterion.

The no form of this command removes any configured source IP. The match criterion is ignored.

Parameters

ip-address

Specifies an address specified as dotted quad.

Values

a.b.c.d

mask

Specifies eight 16-bit hexadecimal pieces representing bit match criteria.

Values

1 to 32

ipv4-address-mask

Any mask expressed in dotted quad notation.

Values

0.0.0.0 to 255.255.255.255

Platforms

All

src-ip

Syntax

src-ip {ipv6-address/prefix-length | ipv6-address ipv6-address-mask}

no src-ip

Context

[Tree] (config>li>li-filter>li-ipv6-filter>entry>match src-ip)

Full Context

configure li li-filter li-ipv6-filter entry match src-ip

Description

This command configures source IPv6 address LI filter match criterion.

The no form of this command removes any configured source IPv6 address. The match criterion is ignored.

Parameters

ipv6-address

Specifies an IPv6 address entered as:.

Values

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

Specifies a length.

Values

1 to 128

ipv6-address-mask

Specifies an IPv6 address mask expressed as:

Values

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

src-ip

Syntax

src-ip {ip-address/mask | ip-address [ipv4-address-mask] | ip-prefix-list prefix-list-name}

no src-ip

Context

[Tree] (config>qos>sap-ingress>ip-criteria>entry>match src-ip)

[Tree] (config>qos>sap-egress>ip-criteria>entry>match src-ip)

Full Context

configure qos sap-ingress ip-criteria entry match src-ip

configure qos sap-egress ip-criteria entry match src-ip

Description

This command configures a source IPv4 address range to be used as an SAP QoS policy match criterion.

To match on the source IPv4 or IPv6 address, specify the address and its associated mask; for example, 10.1.0.0/16. The conventional notation of 10.1.0.0 255.255.0.0 can also be used for IPv4.

The no form of this command removes the source IPv4 or IPv6 address match criterion.

Default

no src-ip

Parameters

ip-address

Specifies the source IPv4 address specified in dotted decimal notation.

Values

ip-address: a.b.c.d

mask

Specifies the length in bits of the subnet mask.

Values

1 to 32

ipv4-address-mask

Specifies the subnet mask in dotted decimal notation.

Values

a.b.c.d (dotted quad equivalent of mask length)

prefix-list-name

Specifies the IPv4 prefix list name, a string of up to 32 printable ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.

Platforms

All

src-ip

Syntax

src-ip {ipv6-address/prefix-length | ipv6-address ipv6-address-mask | ipv6-prefix-list ipv6-prefix-list-name}

no src-ip

Context

[Tree] (config>qos>sap-egress>ipv6-criteria>entry>match src-ip)

[Tree] (config>qos>sap-ingress>ipv6-criteria>entry>match src-ip)

Full Context

configure qos sap-egress ipv6-criteria entry match src-ip

configure qos sap-ingress ipv6-criteria entry match src-ip

Description

This command configures a source IPv6 address range to be used as an SAP QoS policy match criterion.

To match on the source IPv6 address, specify the address and its associated mask, for example, 2001:db8:1000::/64.

The no form of this command removes the source IPv6 address match criterion.

Default

no src-ip

Parameters

ipv6-address

Specifies the IPv6 address for the IP match criterion in hexadecimal digits.

Values

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

Specifies the IPv6 prefix length for the IPv6 address expressed as a decimal integer.

Values

1 to 128

ipv6-address-mask

Specifies the IPv6 address mask.

Values

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

ipv6-prefix-list-name

Specifies the IPv6 prefix list name, a string of up to 32 printable ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.

Platforms

All

src-ip

Syntax

src-ip {ip-address/mask | ip-address ipv4-address-mask | ip-prefix-list ip-prefix-list-name}

src-ip {ipv6-address/mask | ipv6-address ipv6-address-mask | ipv6-prefix-list ipv6-prefix-list-name}

no src-ip

Context

[Tree] (config>qos>network>egress>ipv6-criteria>entry>match src-ip)

[Tree] (config>qos>network>egress>ip-criteria>entry>match src-ip)

[Tree] (config>qos>network>ingress>ipv6-criteria>entry>match src-ip)

[Tree] (config>qos>network>ingress>ip-criteria>entry>match src-ip)

Full Context

configure qos network egress ipv6-criteria entry match src-ip

configure qos network egress ip-criteria entry match src-ip

configure qos network ingress ipv6-criteria entry match src-ip

configure qos network ingress ip-criteria entry match src-ip

Description

This command configures a source IPv4 or IPv6 address range to be used as a network QoS policy match criterion.

To match on the source IPv4 or IPv6 address, specify the address and its associated mask, for example, when specifying an IPv4 address, 10.1.0.0/16 or 10.1.0.0 255.255.0.0 can be used.

The no form of this command removes the source IPv4 or IPv6 address match criterion.

Parameters

ip-address

Specifies the source IPv4 address specified in dotted decimal notation.

Values

ip-address: a.b.c.d

mask

Specifies the length in bits of the subnet mask.

Values

1 to 32

ipv4-address-mask

Specifies the subnet mask in dotted decimal notation.

Values

a.b.c.d (dotted quad equivalent of mask length)

ip-prefix-list-name

Specifies an IPv4 prefix list which contains IPv4 address prefixes to be matched.

Values

A string of up to 32 characters of printable ASCII characters. If special characters are used, the string must be enclosed within double quotes.

ipv6-address

Specifies the IPv6 prefix for the IP match criterion in hex digits.

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

mask

Specifies the length of the ipv6-address expressed as a decimal integer.

Values

1 to 128

ipv6-address-mask

Specifies the eight 16-bit hexadecimal pieces representing bit match criteria.

Values

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

ipv6-prefix-list-name

Specifies an IPv6 prefix list which contains IPv6 address prefixes to be matched.

Values

A string of up to 32 characters of printable ASCII characters. If special characters are used, the string must be enclosed within double quotes.

Platforms

All

src-ip

Syntax

IPv4:

src-ip {ip-address/mask | ip-address ipv4-address-mask | ip-prefix-list prefix-list-name}

IPv6:

src-ip {ipv6-address/prefix-length | ipv6-address ipv6-address-mask | ipv6-prefix-list prefix-list-name}

no src-ip

Context

[Tree] (config>filter>ip-exception>entry>match src-ip)

[Tree] (config>filter>ipv6-exception>entry>match src-ip)

[Tree] (config>filter>ipv6-filter>entry>match src-ip)

Full Context

configure filter ip-exception entry match src-ip

configure filter ipv6-exception entry match src-ip

configure filter ipv6-filter entry match src-ip

Description

This command configures a source IPv4 or IPv6 address range to be used as an IP filter or IP exception match criterion.

To match on the source IPv4 or IPv6 address, specify the address and its associated mask, for example, 10.1.0.0/16 for IPv4. The conventional notation of 10.1.0.0 255.255.0.0 may also be used for IPv4.

The no form of the command removes the source IP address match criterion.

Default

no src-ip

Parameters

ip-address

Specifies the destination IPv4 address specified in dotted decimal notation.

Values

a.b.c.d

mask

Specifies the length in bits of the subnet mask.

Values

1 to 32

ipv4-address-mask

Specifies the subnet mask in dotted decimal notation.

Values

a.b.c.d (dotted quad equivalent of mask length)

ip-prefix-listoripv6-prefix-list prefix-list-name

Specifies to use a list of IP prefixes, which is a string of up to 32 characters of printable ASCII characters. If special characters are used, the string must be enclosed within double quotes.

ipv6-address

Specifies an IPv6 prefix for the IP match criterion in hex digits.

Values

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

prefix-length

Specifies whether a the IPv6 prefix length for the specified ipv6-address expressed as a decimal integer.

Values

1 to 128

ipv6-address-mask

Specifies eight 16-bit hexadecimal pieces representing bit match criteria.

Values

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

VSR

  • configure filter ip-exception entry match src-ip
  • configure filter ipv6-exception entry match src-ip

All

  • configure filter ipv6-filter entry match src-ip

src-ip

Syntax

src-ip ip-prefix[/mask] [netmask]

src-ip ip-prefix-list ip-prefix-list-name

no src-ip

Context

[Tree] (config>system>security>mgmt-access-filter>ip-filter>entry src-ip)

Full Context

configure system security management-access-filter ip-filter entry src-ip

Description

This command configures a source IP address range or an IP prefix list to be used as a management access filter match criterion.

The no form of this command removes the source IP address match criterion.

Default

no src-ip

Parameters

ip-prefix

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

mask

Specifies the subnet mask length expressed as a decimal integer.

Values

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

netmask

Specifies the dotted quad equivalent of the mask length.

Values

0.0.0.0 to 255.255.255.255

ip-prefix-list-name

Specifies the IP prefix list used as a match criterion for the source IP address. It is a string of up to 32 characters of printable ASCII characters. If special characters are used, the string must be enclosed within double quotes .

Platforms

All

src-ip

Syntax

src-ip ipv6-address/prefix-length

src-ip ipv6-prefix-list ipv6-prefix-list-name

no src-ip

Context

[Tree] (config>system>security>mgmt-access-filter>ipv6-filter>entry src-ip)

Full Context

configure system security management-access-filter ipv6-filter entry src-ip

Description

This command configures a source IPv6 address range or an IPv6 prefix list to be used as a management access filter match criterion. This command only applies to the 7750 SR and 7950 XRS.

The no form of this command removes the source IPv6 address match criterion.

Default

no src-ip

Parameters

ipv6-address/prefix-length

Specifies the IPv6 address for the IPv6 match criterion in dotted decimal notation. An IPv6 IP address is written as eight 4-digit (16-bit) hexadecimal numbers separated by colons. One string of zeros per address can be left out, so that 2001:db8::0:217A is the same as 2001:db8:0:0:0:0:0:217A.

Values

ipv6-address

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

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

x: [0..FFFF]H

d: [0..255]D

prefix-length

1 to 128

ipv6-prefix-list-name

Specifies the IPv6 prefix list used a match criterion for the source IP address. It is a string of up to 32 characters of printable ASCII characters. If special characters are used, the string must be enclosed within double quotes .

Platforms

All

src-ip

Syntax

src-ip [ipv6-address/ prefix-length | ip-prefix-list prefix-list-name]

no src-ip

Context

[Tree] (cfg>sys>sec>cpm>ip-filter>entry>match src-ip)

Full Context

configure system security cpm-filter ip-filter entry match src-ip

Description

This command specifies the IP address to match the source IP address of the packet.

To match on the source IP address, specify the address and its associated mask, such as 10.1.0.0/16. The conventional notation of 10.1.0.0 255.255.0.0 may also be used.

The no form of this command removes the source IP address match criterion.

Default

no src-ip

Parameters

ipv6-address/prefix-length

Specifies the IP address for the match criterion in dotted decimal notation. An IP address is written as eight 4-digit (16-bit) hexadecimal numbers separated by colons. One string of zeros per address can be left out, so that 2001:db8::0:217A is the same as 2001:db8:0:0:0:0:0:217A.

Values

ipv4-address

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

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

x: [0..FFFF]H

d: [0..255]D

interface: 32 characters maximum, mandatory for link local addresses

prefix-length

1 to 128

ip-prefix-list

Creates a list of IPv4 prefixes for match criteria in IPv4 ACL and CPM filter policies.

ip-prefix-list-name

Specifies a string of up to 32 characters of printable ASCII characters. If special characters are used, the string must be enclosed within double quotes.

Platforms

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

src-ip

Syntax

src-ip [ip-address/mask | ipv6-prefix-list ipv6-prefix-list-name]

no src-ip

Context

[Tree] (cfg>sys>sec>cpm>ipv6-filter>entry>match src-ip)

Full Context

configure system security cpm-filter ipv6-filter entry match src-ip

Description

This command specifies the IPv6 address to match the source IPv6 address of the packet.

To match on the source IP address, specify the address and its associated mask, such as 10.1.0.0/16. The conventional notation of 10.1.0.0 255.255.0.0 may also be used.

The no form of this command removes the source IP address match criterion.

This command only applies to the 7750 SR and 7950 XRS.

Default

no src-ip

Parameters

ip-address/mask

Specifies the IP address for the match criterion in dotted decimal notation. An IP address is written as eight 4-digit (16-bit) hexadecimal numbers separated by colons. One string of zeros per address can be left out, so that 2001:db8::0:217A is the same as 2001:db8:0:0:0:0:0:217A.

Values

ipv6-address

x:x:x:x:x:x:x:x[-interface]

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

x: [0..FFFF]H

d: [0..255]D

interface: 32 characters maximum, mandatory for link local addresses

mask:

Specifies eight 16-bit hexadecimal pieces representing bit match criteria.

Values

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

ipv6-prefix-list

Creates a list of IPv6 prefixes for match criteria in IPv6 ACL and CPM filter policies.

ipv6-prefix-list-name

Specifies a string of up to 32 characters of printable ASCII characters. If special characters are used, the string must be enclosed within double quotes.

Platforms

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

src-ip-address

src-ip-address

Syntax

src-ip-address ip-address

no src-ip-address

Context

[Tree] (config>saa>test>type-multi-line>lsp-ping src-ip-address)

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

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

Full Context

configure saa test type-multi-line lsp-ping src-ip-address

configure saa test type-multi-line lsp-ping sr-policy src-ip-address

configure saa test type-multi-line lsp-trace sr-policy src-ip-address

Description

This command configures the source IP address. This option is used when an OAM packet must be generated from a different address than the node’s system interface address. For example, when the OAM packet is sent over an LDP LSP and the LDP LSR-ID of the corresponding LDP session to the next hop is set to an address other than the system interface address.

The no form of this command removes the configuration.

Parameters

ip-address

Specifies the source 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

All

src-ipv4-address

src-ipv4-address

Syntax

src-ipv4-address a.b.c.d

no src-ipv4-address

Context

[Tree] (debug>oam>build-packet>packet>field-override>header>ipv4 src-ipv4-address)

[Tree] (config>test-oam>build-packet>header>ipv4 src-ipv4-address)

Full Context

debug oam build-packet packet field-override header ipv4 src-ipv4-address

configure test-oam build-packet header ipv4 src-ipv4-address

Description

This command defines the source IPv4 address to be used in the IPv4 header.

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

Default

src-ipv4-address 0.0.0.0

Parameters

a.b.c.d

Specifies the IPv4 source address to be used in the IPv4 header.

Platforms

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

src-ipv6-address

src-ipv6-address

Syntax

src-ipv6-address ipv6-address

no src-ipv6-address

Context

[Tree] (config>test-oam>build-packet>header>ipv6 src-ipv6-address)

[Tree] (debug>oam>build-packet>packet>field-override>header>ipv6 src-ipv6-address)

Full Context

configure test-oam build-packet header ipv6 src-ipv6-address

debug oam build-packet packet field-override header ipv6 src-ipv6-address

Description

This command defines the source IPv6 address to be used in the IPv6 header.

The no form of the removes the source IPv6 address.

Parameters

ipv6-address

Specifies the IPv6 source address to be used in the IPv6 header.

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, 7950 XRS

src-mac

src-mac

Syntax

src-mac ieee-address

no src-mac

Context

[Tree] (config>redundancy>mc>peer>mcr>l3ring>node>cv src-mac)

Full Context

configure redundancy multi-chassis peer mc-ring l3-ring ring-node connectivity-verify src-mac

Description

This command specifies the source MAC address used for the ring-node connectivity verification of this ring node.

If all zeros are specified, the MAC address of the system management processor (CPM) is used.

The no form of this command reverts to the default.

Parameters

ieee-address

Specifies the 48-bit MAC address for the static ARP in the form aa:bb:cc:dd:ee:ff or aa-bb-cc-dd-ee-ff where aa, bb, cc, dd, ee, and ff are hexadecimal numbers. Allowed values are any non-broadcast, non-multicast MAC and non-IEEE reserved MAC addresses.

Platforms

All

src-mac

Syntax

src-mac ieee-address

no src-mac

Context

[Tree] (config>redundancy>mc>peer>mcr>node>cv src-mac)

Full Context

configure redundancy multi-chassis peer mc-ring ring ring-node connectivity-verify src-mac

Description

This command specifies the source MAC address used for the Ring-Node Connectivity Verification of this ring node.

A value of all zeros (000000000000 H (0:0:0:0:0:0)) specifies that the MAC address of the system management processor (CPM) is used.

Default

no src-mac

Parameters

ieee-address

Specifies the source MAC address.

Values

xx:xx:xx:xx:xx:xx or xx-xx-xx-xx-xx-xx

Platforms

All

src-mac

Syntax

src-mac ieee-address [ieee-address-mask]

no src-mac

Context

[Tree] (config>li>li-filter>li-mac-filter>entry>match src-mac)

Full Context

configure li li-filter li-mac-filter entry match src-mac

Description

This command configures a source MAC address or range to be used as a MAC filter match criterion.

The no form of this command removes the source mac as the match criteria.

Parameters

ieee-address

Specifies the 48-bit IEEE mac address to be used as a match criterion.

Values

HH:HH:HH:HH:HH:HH or HH-HH-HH-HH-HH-HH where H is a hexadecimal digit

ieee-address-mask

Specifies a 48-bit mask. The following table describes the format styles to configure the 48-bit mask.

Table 1. Format Styles to Configure Mask

Format Style

Format Syntax

Example

Decimal

DDDDDDDDDDDDDD

281474959933440

Hexadecimal

0xHHHHHHHHHHHH

0x0FFFFF000000

Binary

0bBBBBBBB...B

0b11110000...B

To configure so that all packets with a source MAC OUI value of 00-03-FA are subject to a match condition then the entry should be specified as: 003FA000000 0xFFFFFF000000

Default

0xFFFFFFFFFFFF (exact match)

Values

0x00000000000000 to 0xFFFFFFFFFFFF

Platforms

All

src-mac

Syntax

src-mac ieee-address [ieee-address-mask]

no src-mac

Context

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

Full Context

configure qos sap-ingress mac-criteria entry match src-mac

Description

This command configures a source MAC address or range to be used as a service ingress QoS policy match criterion.

The no form of this command removes the source mac as the match criteria.

Default

no src-mac

Parameters

ieee-address

Enter the 48-bit IEEE MAC address to be used as a match criterion.

Values

HH:HH:HH:HH:HH:HH or HH-HH-HH-HH-HH-HH where H is a hexadecimal digit

ieee-address-mask

This 48-bit mask can be configured using the following formats:

Table 2. Format Styles to Configure Mask

Format Style

Format Syntax

Example

Decimal

DDDDDDDDDDDDDD

281474959933440

Hexadecimal

0xHHHHHHHHHHHH

0x0FFFFF000000

Binary

0bBBBBBBB...B

0b11110000...B

To configure all packets with a source MAC OUI value of 00-03-FA to be subject to a match condition, the entry should be specified as: 003FA000000 0xFFFFFF000000

Values

0x00000000000000 to 0xFFFFFFFFFFFF (hex)

Default

0xFFFFFFFFFFFF (hex) (exact match)

Platforms

All

src-mac

Syntax

src-mac ieee-address [ieee-address-mask]

no src-mac

Context

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

[Tree] (config>filter>ipv6-filter>entry>match src-mac)

[Tree] (config>filter>ip-filter>entry>match src-mac)

Full Context

configure filter mac-filter entry match src-mac

configure filter ipv6-filter entry match src-mac

configure filter ip-filter entry match src-mac

Description

Configures a source MAC address or range to be used as a MAC filter match criterion.

The no form of the command removes the source mac as the match criteria.

Default

no src-mac

Parameters

ieee-address

Specifies the 48-bit IEEE MAC address to be used as a match criterion.

Values

HH:HH:HH:HH:HH:HH or HH-HH-HH-HH-HH-HH where H is a hexadecimal digit; both upper and lower case are supported.

ieee-address-mask

Specifies the 48-bit mask to match a range of MAC address values.

To configure so that all packets with a source MAC OUI value of 00:03:FA are subject to a match condition then the entry should be specified as: 00:03:FA:00:00:00 FF:FF:FF:00:00:00

Default

ff:ff:ff:ff:ff:ff (exact match)

Values

HH:HH:HH:HH:HH:HH or HH-HH-HH-HH-HH-HH where H is an hexadecimal digit; both upper and lower case are supported.

Platforms

All

src-mac

Syntax

src-mac ieee-address [ieee-address-mask]

no src-mac

Context

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

Full Context

configure system security management-access-filter mac-filter entry match src-mac

Description

This command configures a source MAC address or range to be used as a MAC filter match criterion.

The no form of this command removes the source mac as the match criteria.

Default

no src-mac

Parameters

ieee-address

Specifies the 48-bit IEEE mac address to be used as a match criterion.

Values

HH:HH:HH:HH:HH:HH or HH-HH-HH-HH-HH-HH where H is a hexadecimal digit

ieee-address-mask

Specifies a 48-bit mask that can be configured using the formats listed in ieee-address-mask Formats:

Table 3. ieee-address-mask Formats

Format Style

Format Syntax

Example

Decimal

DDDDDDDDDDDDDD

281474959933440

Hexadecimal

0xHHHHHHHHHHHH

0x0FFFFF000000

Binary

0bBBBBBBB...B

0b11110000...B

To configure so that all packets with a source MAC OUI value of 00-03-FA are subject to a match condition then the entry should be specified as: 003FA000000 0xFFFFFF000000

Default

0xFFFFFFFFFFFF (exact match)

Values

0x00000000000000 to 0xFFFFFFFFFFFF

Platforms

All

src-mac-address

src-mac-address

Syntax

src-mac-address ieee-address

no src-mac-address

Context

[Tree] (debug>oam>build-packet>packet>field-override>header>ethernet src-mac-address)

[Tree] (config>test-oam>build-packet>header>ethernet src-mac-address)

Full Context

debug oam build-packet packet field-override header ethernet src-mac-address

configure test-oam build-packet header ethernet src-mac-address

Description

This command defines the source MAC address for the Ethernet header.

The no form of this command deletes the configured MAC address.

Default

no override

Parameters

ieee-address

Specifies the source Ethernet MAC address to be used in the Ethernet header. Specifies the 48-bit MAC address.

Values

xx:xx:xx:xx:xx:xx

Platforms

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

src-port

src-port

Syntax

src-port {lt | gt | eq} src-port-number

src-port range start end

no src-port

Context

[Tree] (config>subscr-mgmt>cat-map>category>exh-lvl>egr-ip>entry>match src-port)

[Tree] (config>subscr-mgmt>cat-map>category>exh-lvl>egr-ipv6>entry>match src-port)

[Tree] (config>subscr-mgmt>cat-map>category>exh-lvl>ingr-ip>entry>match src-port)

[Tree] (config>subscr-mgmt>cat-map>category>exh-lvl>ingr-ipv6>entry>match src-port)

Full Context

configure subscriber-mgmt category-map category exhausted-credit-service-level egress-ip-filter-entries entry match src-port

configure subscriber-mgmt category-map category exhausted-credit-service-level egress-ipv6-filter-entries entry match src-port

configure subscriber-mgmt category-map category exhausted-credit-service-level ingress-ip-filter-entries entry match src-port

configure subscriber-mgmt category-map category exhausted-credit-service-level ingress-ipv6-filter-entries entry match src-port

Description

This command configures the source port match condition.

The no form of this command reverts to the default.

Parameters

lt | gt | eq

Specifies the operators.

src-port-number

Specifies the source port number as a decimal hex or binary.

Values

0 to 65535

dst-port-number

Specifies the destination port number as a decimal hex or binary.

Values

0 to 65535

Platforms

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

src-port

Syntax

src-port {eq | neq} port-num

src-port {eq | neq} port-list port-list-name

src-port {eq | neq} range start-port-num end-port-num

no src-port

Context

[Tree] (config>app-assure>group>policy>aqp>entry>match src-port)

Full Context

configure application-assurance group policy app-qos-policy entry match src-port

Description

This command specifies a source IP port, source port list, or source range to use as match criteria.

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

Default

no src-port

Parameters

eq

Specifies that a successful match occurs when the flow matches the specified port.

neq

Specifies that a successful match occurs when the flow does not match the specified port.

port-num

Specifies the source port number.

Values

0 to 65535

start-port-num end-port-num

Specifies the start or end source port number.

Values

0 to 65535

port-list-name

Specifies a named port-list, up to 32 characters, containing a set of ports or ranges of ports.

Platforms

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

src-port

Syntax

src-port {eq | gt | lt} port-num

src-port port-list port-list-name

src-port range start-port-num end-port-num

no src-port

Context

[Tree] (config>app-assure>group>sess-fltr>entry>match src-port)

Full Context

configure application-assurance group session-filter entry match src-port

Description

This command specifies a source IP port, source port list, or source range to use as match criteria.

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

Default

no src-port

Parameters

eq

Specifies that a successful match occurs when the flow matches the specified port.

gt

Specifies all port numbers greater than the port-number match.

lt

Specifies all port numbers less than the port-number match.

port-num

Specifies the source port number.

Values

0 to 65535

start-port-num end-port-num

Specifies the start or end source port number.

Values

0 to 65535

port-list-name

Specifies a named port-list, up to 32 characters, containing a set of ports or ranges of ports.

Platforms

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

src-port

Syntax

src-port {eq | neq} port-num

no src-port

Context

[Tree] (debug>app-assure>group>traffic-capture>match src-port)

Full Context

debug application-assurance group traffic-capture match src-port

Description

This command configures debugging on a source port.

Platforms

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

src-port

Syntax

src-port {lt | gt | eq} src-port-number

src-port range src-port-number src-port-number

no src-port

Context

[Tree] (config>li>li-filter>li-ipv6-filter>entry>match src-port)

[Tree] (config>li>li-filter>li-ip-filter>entry>match src-port)

Full Context

configure li li-filter li-ipv6-filter entry match src-port

configure li li-filter li-ip-filter entry match src-port

Description

This command configures a source TCP or UDP port number or port range for an IP LI filter match criterion. Note that an entry containing Layer 4 match criteria will not match non-initial (second, third, and so on) fragments of a fragmented packet since only the first fragment contains the Layer 4 information.

The no form of this command removes the source port match criterion.

Parameters

lt

Specifies all port numbers less than src-port-number match.

gt

Specifies all port numbers greater than src-port-number match.

eq

Specifies that src-port-number must be an exact match.

src-port-number

Specifies the source port number to be used as a match criteria expressed as a decimal integer.

Values

[0..65535]D

[0x0..0xFFFF]H

[0b0..0b1111111111111111]B

Platforms

All

src-port

Syntax

src-port {lt | gt | eq} src-port-number

src-port range start end

no src-port

Context

[Tree] (config>qos>sap-egress>ip-criteria>entry>match src-port)

[Tree] (config>qos>sap-ingress>ipv6-criteria>entry>match src-port)

[Tree] (config>qos>sap-egress>ipv6-criteria>entry>match src-port)

[Tree] (config>qos>sap-ingress>ip-criteria>entry>match src-port)

Full Context

configure qos sap-egress ip-criteria entry match src-port

configure qos sap-ingress ipv6-criteria entry match src-port

configure qos sap-egress ipv6-criteria entry match src-port

configure qos sap-ingress ip-criteria entry match src-port

Description

This command configures a source TCP or UDP port number or port range for a SAP QoS policy match criterion.

The no form of this command removes the source port match criterion.

Default

no src-port

Parameters

{lt | gt | eq} src-port-number

The TCP or UDP port numbers to match, specified as less than (lt), greater than (gt), or equal to (eq) to the source port value, specified as a decimal integer.

Values

1 to 65535 (decimal)

range startend

The range of TCP or UDP port values to match, specified as between the start and end source port values inclusive.

Values

1 to 65535 (decimal)

Platforms

All

src-port

Syntax

src-port {lt | gt | eq} src-port-number

src-port port-list port-list-name

src-port range start end

no src-port

Context

[Tree] (config>qos>network>egress>ipv6-criteria>entry>match src-port)

[Tree] (config>qos>network>ingress>ipv6-criteria>entry>match src-port)

[Tree] (config>qos>network>egress>ip-criteria>entry>match src-port)

[Tree] (config>qos>network>ingress>ip-criteria>entry>match src-port)

Full Context

configure qos network egress ipv6-criteria entry match src-port

configure qos network ingress ipv6-criteria entry match src-port

configure qos network egress ip-criteria entry match src-port

configure qos network ingress ip-criteria entry match src-port

Description

This command configures a source TCP or UDP port number, port range, or a port list for a network QoS policy match criterion.

The no form of this command removes the source port match criterion.

Default

no src-port

Parameters

lt

Keyword used to specify TCP or UDP port numbers to match that are less than the source port value.

gt

Keyword used to specify TCP or UDP port numbers to match that are greater than the source port value.

eq

Keyword used to specify TCP or UDP port numbers to match that are equal to the source port value.

src-port-number

The source port value, specified as a decimal integer.

Values

1 to 65535

port-list-name

Specifies a port list name, up to 32 characters of printable ASCII characters. If special characters are used, the string must be enclosed within double quotes.

start

Specifies the starting range of TCP or UDP source port values to match.

Values

1 to 65535

end

Specifies the end range of TCP or UDP source port values to match.

Values

1 to 65535

Platforms

All

src-port

Syntax

src-port {lt | gt | eq} src-port-number

src-port port-list port-list-name

src-port range src-port-number src-port-number

no src-port

Context

[Tree] (config>filter>ip-exception>entry>match src-port)

[Tree] (config>filter>ipv6-exception>entry>match src-port)

[Tree] (config>filter>ip-filter>entry>match src-port)

[Tree] (config>filter>ipv6-filter>entry>match src-port)

Full Context

configure filter ip-exception entry match src-port

configure filter ipv6-exception entry match src-port

configure filter ip-filter entry match src-port

configure filter ipv6-filter entry match src-port

Description

This command configures a source TCP, UDP, or SCTP port number, port range, or port match list for an IP filter or IP exception match criterion. An entry containing Layer 4 non-zero match criteria will not match non-initial (2nd, 3rd, and so on) fragments of a fragmented packet since only the first fragment contains the Layer 4 information. Similarly an entry containing "src-port eq 0" match criterion, may match non-initial fragments when the source port value is not present in a packet fragment and other match criteria are also met.

The no form of the command removes the source port match criterion.

Default

no src-port

Parameters

lt | gt | eq

Specifies the operator to use relative to src-port-number for specifying the port number match criteria.

lt specifies that all port numbers less than src-port-number match.

gt specifies that all port numbers greater than src-port-number match.

eq specifies that src-port-number must be an exact match.

src-port-number

Specifies the source port number to be used as a match criteria expressed as a decimal integer, and in hexadecimal or binary format. Below shows decimal integer only.

Values

0 to 65535

port-list-name

Specifies to use a list of ports referred to by port-list-name, which is a string of up to 32 characters of printable ASCII characters. If special characters are used, the string must be enclosed within double quotes.

src-port-number src-port-number

Specifies inclusive port range between two src-port-number values.

Platforms

VSR

  • configure filter ip-exception entry match src-port
  • configure filter ipv6-exception entry match src-port

All

  • configure filter ipv6-filter entry match src-port
  • configure filter ip-filter entry match src-port

src-port

Syntax

src-port {port-id | cpm | lag lag-id}

no src-port

Context

[Tree] (config>system>security>mgmt-access-filter>ip-filter>entry src-port)

[Tree] (config>system>security>mgmt-access-filter>ipv6-filter>entry src-port)

Full Context

configure system security management-access-filter ip-filter entry src-port

configure system security management-access-filter ipv6-filter entry src-port

Description

This command restricts ingress management traffic to either the CPM/CCM Ethernet port or any other logical port (for example LAG) on the device.

When the source interface is configured, only management traffic arriving on those ports satisfy the match criteria.

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

Default

no src-port

Parameters

port-id

Specifies the port ID in formats shown below.

Values

slot/mda/port[.channel]

aps

keyword

group-id

1 to 128

ccag-id

ccag-id. path-id[cc-type]

ccag

keyword

id

1 to 8

path-id

a, b

cc-type

.sap-net, .net-sap

cpm

Matches any traffic received on any Ethernet port.

lag-id

Specifies the LAG identifier.

Values

1 to 800

Platforms

All

src-port

Syntax

src-port tcp/udp port-number [mask]

scr-port port-list port-list-name

scr-port range tcp/udp port-number tcp/udp port-number

no scr-port

Context

[Tree] (cfg>sys>sec>cpm>ip-filter>entry>match src-port)

[Tree] (cfg>sys>sec>cpm>ipv6-filter>entry>match src-port)

Full Context

configure system security cpm-filter ip-filter entry match src-port

configure system security cpm-filter ipv6-filter entry match src-port

Description

This command specifies the TCP/UDP port to match the source port of the packet.

Note:

An entry containing Layer 4 match criteria will not match non-initial (2nd, 3rd, etc) fragments of a fragmented packet since only the first fragment contains the Layer 4 information.

Default

no src-port

Parameters

tcp/udp port-number

Specifies the source port number to be used as a match criteria expressed as a decimal integer.

Values

0 to 65535

port-list-name

Specifies the port list name to be used as a match criteria for the destination port.

mask

Specifies the 16 bit mask to be applied when matching the destination port.

Values

[0x0000..0xFFFF] | [0..65535] | [0b0000000000000000..0b1111111111111111]

Platforms

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

src-prefix

src-prefix

Syntax

src-prefix ip-address/mask [ip-address/mask]

no src-prefix ip-address/mask

Context

[Tree] (config>service>vprn>mvpn>red-source-list src-prefix)

Full Context

configure service vprn mvpn red-source-list src-prefix

Description

This command configures multicast source IPv4 prefixes for preferred source selection. Single or multi-line inputs are allowed.

The no form of this command deletes specified prefix from the list.

Default

No prefixes are specified.

Parameters

ip-address/mask

IPv4 address prefix with mask. Up to 8 maximum.

Platforms

All

src-prefix

Syntax

src-prefix ipv6-ip-address/prefix-length [ ipv6-address/prefix-length]

no ipv6-ip-address/prefix-length

Context

[Tree] (config>service>vprn>mvpn>red-source-list>ipv6 src-prefix)

Full Context

configure service vprn mvpn red-source-list ipv6 src-prefix

Description

This command configures multicast source IPv6 prefixes for preferred source selection. Single or multi-line inputs are allowed.

The no form of this command deletes specified prefix from the list

Default

No prefixes are specified.

Parameters

ipv6-ip-address/mask

IPv6 address prefix with prefix-length. Up to 8 maximum.

Platforms

All

src-route-option

src-route-option

Syntax

src-route-option {true | false}

no source-route-option

Context

[Tree] (config>filter>ip-filter>entry>match src-route-option)

Full Context

configure filter ip-filter entry match src-route-option

Description

This command enables source route option match conditions. When enabled, this filter should match if a (strict or loose) source route option is present/not present at any location within the IP header, as per the value of this object. The no form of the command removes the criterion from the match entry.

Default

no src-route-option

Parameters

true

Enables source route option match conditions.

false

Disables source route option match conditions.

Platforms

All

src-tcp-port

src-tcp-port

Syntax

src-tcp-port tcp-port

no src-tcp-port

Context

[Tree] (config>test-oam>build-packet>header>tcp src-tcp-port)

Full Context

configure test-oam build-packet header tcp src-tcp-port

Description

This command defines the source TCP port to be used in the test TCP header.

The no form of this command reverts to the default.

Default

src-tcp-port 0

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

src-tcp-port

Syntax

src-tcp-port tcp-port

no src-tcp-port

Context

[Tree] (debug>oam>build-packet>packet>field-override>header>tcp src-tcp-port)

Full Context

debug oam build-packet packet field-override header tcp src-tcp-port

Description

This command defines the source TCP port to be used in the TCP header.

The no form of this command reverts to the default.

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

src-udp-port

src-udp-port

Syntax

src-udp-port udp-port

no src-udp-port

Context

[Tree] (config>test-oam>build-packet>header>udp src-udp-port)

Full Context

configure test-oam build-packet header udp src-udp-port

Description

This command defines the source UDP port to be used in the test UDP header.

The no form of this command reverts to the default.

Default

src-udp-port 0

Parameters

udp-port

Specifies the source UDP port to be used in the test UDP header.

Values

0 to 65535

Platforms

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

src-udp-port

Syntax

src-udp-port udp-port

no src-udp-port

Context

[Tree] (debug>oam>build-packet>packet>field-override>header>udp src-udp-port)

Full Context

debug oam build-packet packet field-override header udp src-udp-port

Description

This command defines the source UDP port to be used in the UDP header.

The no form of this command reverts to the default.

Default

no override

Parameters

udp-port

Specifies the source UDP port to be used in the UDP header.

Values

0 to 65535

Platforms

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

src-udp-port

Syntax

src-udp-port port-number

no src-udp-port

Context

[Tree] (config>test-oam>link-meas>template>twl src-udp-port)

Full Context

configure test-oam link-measurement measurement-template twamp-light src-udp-port

Description

This command configures a source UDP port to be used by the link measurement tests linked to this template.

Unless required, Nokia suggests that the link measurement dynamically select an available source UDP port from the dynamic range. Before a UDP port in the configurable range can be configured as a source it must be owned by the application. Use the config>test-oam>twamp>twamp-light> source-udp-port-pools>port>pool-type command to map the port range to the application.

To use a source port in this range for link-measurement, the selected port number must have a pool-type link-measurement configured. The source UDP port must be owned by the application prior to the configuration under the application. A configured source-udp-port cannot be used when multiple tests are configured between the same source IP, destination IP and destination UDP port. A conflict may occur when non-unique addressing is used between two peers. A conflicting situation may occur when tests between peers are using IPv6 discovery and the link-local addresses on both nodes are the same. Other conflicts exist, such as, multiple tests between peers using the same source and destination IP system address instead of an interface address. When this condition exists, the operational state of the link-measurement test is operationally down with a failure condition UdpPortUnavailable.

The no form of the command removes the port number from the link measurement template.

Default

no src-udp-port

Parameters

port-number

Specifies the source UDP port number.

Values

64374 to 64383

Platforms

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

srefresh

srefresh

Syntax

srefresh [detail]

no srefresh

Context

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

Full Context

debug router rsvp packet srefresh

Description

This command debugs srefresh packets.

The no form of the command disables the debugging.

Parameters

detail

Displays detailed information about srefresh packets.

Platforms

All

srh-mode

srh-mode

Syntax

srh-mode srh-mode

no srh-mode

Context

[Tree] (config>router>segment-routing>srv6>inst>loc>func>end srh-mode)

[Tree] (config>router>segment-routing>srv6>inst>ms-loc>func>ua srh-mode)

[Tree] (conf>router>segment-routing>srv6>ms-locator>un srh-mode)

[Tree] (config>router>segment-routing>srv6>inst>loc>func>end-x srh-mode)

Full Context

configure router segment-routing segment-routing-v6 base-routing-instance locator function end srh-mode

configure router segment-routing segment-routing-v6 base-routing-instance micro-segment-locator function ua srh-mode

configure router segment-routing segment-routing-v6 micro-segment-locator un srh-mode

configure router segment-routing segment-routing-v6 base-routing-instance locator function end-x srh-mode

Description

This command configures the SRH penultimate or ultimate pop mode, as well as the ultimate decapsulation mode, for the SID.

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

Default

srh-mode psp

Parameters

srh-mode

Specifies the SRH mode for the SID.

Values

psp — Penultimate Segment Pop (PSP) of the SRH

usp — Ultimate Segment Pop (USP) of the SRH

psp-usd — Supports both PSP of the SRH and Ultimate Segment Decapsulation (USD) on the same SID

usp-usd — Supports both USP of the SRH and USD on the same SID

psp-usp-usd — Supports PSP and USP of the SRH with USD on the same SID

Platforms

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

srlb

srlb

Syntax

srlb reserved-label-block-name

no srlb

Context

[Tree] (config>router>ospf>segm-rtng srlb)

[Tree] (config>router>isis>segm-rtng srlb)

Full Context

configure router ospf segment-routing srlb

configure router isis segment-routing srlb

Description

This command specifies the reserved label block to use for the Segment Routing Local Block (SRLB) for the specified IS-IS or OSPF instance. The named reserved label block must already have been configured under config>router>mpls>mpls-labels.

The no form of this command removes an SRLB.

Parameters

reserved-label-block-name

Specifies the name of the reserved label block, up to 64 characters.

Platforms

All

srlg

srlg

Syntax

[no] srlg

Context

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

Full Context

configure router mpls lsp secondary srlg

Description

This command enables the use of the SRLG constraint in the computation of a secondary path for an LSP at the head-end LER. The command is configurable for both RSVP-TE and SR-TE LSPs.

When SRLG is enabled, CSPF includes the SRLG constraint in the computation of the secondary LSP path if path-computation-method local-cspf is configured on the LSP. CSPF returns the list of SRLG groups along with the ERO during primary path CSPF computation. At a subsequent establishment of a secondary path with the SRLG constraint, the MPLS task again queries CSPF by providing the list of SRLG group numbers to be avoided. CSPF prunes all links with interfaces that belong to the same SRLGs as the interfaces included in the ERO of the primary path. If CSPF finds a path, the secondary path is set up. If a path is not found, MPLS keeps retrying the requests to CSPF.

An SRLG enabled secondary or standby path of the LSP configured with a value of the path-computation-method command other than local-cspf remains operationally down with a failure code of srlgPrimaryCspfDisabled(25).

When an LSP is administratively enabled, the SRLG-enabled secondary path is not tried if the first attempt to bring up the primary path is in progress. The SRLG enabled secondary path is kept down temporarily with failure code srlgPrimaryPathDown(26). After this first attempt, MPLS begins setting up the SRLG-enabled standby paths. If primary path computation fails or primary path was not configured, MPLS requests CSPF to compute the secondary path using an empty primary SRLG list. The SRLG disjoint state field shows True in this scenario.

If the primary path is re-optimized, has undergone MBB, or has come back up after being down, the MPLS task check determines if any SRLG secondary paths should be re-signaled. If MPLS finds that a secondary path is no longer SRLG disjointed, and therefore becomes ineligible, MPLS puts it on a delayed MBB immediately after the expiry of the retry timer. If MBB fails at the first try, the secondary path is torn down and the path is put on retry if not active. If the secondary path is active, then it is only torn down and resignaled when the primary path is activated. The secondary path can remain active even when ineligible while the revert timer to activate the primary path is still running.

If the primary goes down while active, the LSP uses the path of an eligible SRLG secondary path if it is up. If all secondary eligible SRLG paths are down, MPLS uses a non-SRLG secondary path, if configured and up. While the LSP is using a non-SRLG secondary path, if an eligible SRLG secondary path comes back up, MPLS switches the path of the LSP to the eligible SRLG secondary path. As soon as a path for the primary is successfully computed by CSPF, MPLS schedules the delay retry MBB for the secondary path using the new SRLG list.

If the primary path goes down while inactive, for example it is waiting for the revert timer to expire, MPLS resets the SRLG list of the primary to empty and changes the state of all secondary paths, including the currently active one, to the Disjointed state. A delay retry MBB is still performed but results in no change to the active secondary path.

A secondary path that becomes ineligible as a result of an update to the SRLG membership list of the primary path has the ineligibility status removed on any of the following events:

  • a successful delay retry MBB of the secondary SRLG path that makes it eligible again

  • the secondary path goes down. MPLS puts the standby on retry at the expiry of the retry timer. If successful, it becomes eligible. If not successful after the retry-timer expires or the number of retries reached the number configured under the retry-limit parameter, it is left down.

Once the primary path of the LSP is set up and is operationally up, any subsequent changes to the SRLG group membership of an interface that the primary path is using is not considered until the next opportunity the primary path is re-signaled. The primary path may be re-signaled due to a failure or to a make-before-break operation. Make-before-break occurs as a result of a global revertive operation, a timer based or manual re-optimization of the LSP path, or an operator change to any of the path constraints.

Once an SRLG secondary path is set up and is operationally up, any subsequent changes to the SRLG group membership of an interface the secondary path is using is not considered until the next opportunity when the secondary path is re-signaled. The secondary path is re-signaled due to a failure, to a re-signaling of the primary path, or to a make before break operation. Make-before-break occurs as a result of a timer based or manual re-optimization of the secondary path, or an operator change to any of the path constraints of the secondary path, except for enabling or disabling the srlg command itself. Enabling or disabling the srlg command on an active secondary or on an active or inactive secondary standby path causes the path to be torn down and re-signaled.

In addition, the user-configured include or exclude admin group statements for a secondary path are also checked together with the SRLG constraints by CSPF.

The following behavior of the feature is specific to the SR-TE LSP.

  • An SRLG-enabled SR-TE LSP secondary path with SID label hops remains operational with failure code srlgPathWithSidHops(59).

  • An SR-TE LSP uses IGP advertised link SRLG information in the TE database. It does not support the use of SRLG information in the static user SRLG database (configure router mpls srlg-database).

  • Delay Retry MBB for making a non-disjointed path a disjointed one is not supported with an SR-TE LSP. Instead, the system performs a break-before-make (that is, teardown and retry) operation. If a non-disjointed path is the active path of the LSP, that path is torn down and retried after the router switches to another path (for example, after revert-timer expires). If the non-disjointed path is not an active path, it is torn down and retried immediately.

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

Default

no srlg

Platforms

All

srlg-database

srlg-database

Syntax

[no] srlg-database

Context

[Tree] (config>router>mpls srlg-database)

Full Context

configure router mpls srlg-database

Description

Commands in this context configure the link members of SRLG groups for the entire network at any node that needs to signal LSP paths (for example, a head-end node).

The no form of this command deletes the entire SRLG database. CSPF assumes all interfaces have no SRLG membership association if the database was not disabled with the command config>router>mpls>user-srlg-db disable.

Platforms

All

srlg-enable

srlg-enable

Syntax

[no] srlg-enable

Context

[Tree] (config>router>route-next-hop-policy>template srlg-enable)

Full Context

configure router route-next-hop-policy template srlg-enable

Description

This command configures the SRLG constraint into the route next-hop policy template.

When this command is applied to a prefix, the LFA SPF will attempt to select an LFA next-hop, among the computed ones, which uses an outgoing interface that does not participate in any of the SLRGs of the outgoing interface used by the primary next-hop.

The SRLG criterion is applied before running the LFA next-hop selection algorithm.

The no form deletes the SRLG constraint from the route next-hop policy template.

Default

no srlg-enable

Platforms

All

srlg-frr

srlg-frr

Syntax

srlg-frr [strict]

no srlg-frr

Context

[Tree] (config>router>mpls srlg-frr)

Full Context

configure router mpls srlg-frr

Description

This command enables the use of the SRLG constraint in the computation of FRR bypass or detour to be associated with any primary LSP path on this system.

When this option is enabled, CSPF includes the SRLG constraint in the computation of a FRR detour or bypass for protecting the primary LSP path.

CSPF prunes all links with interfaces that belong to the same SRLG as the interface that is being protected, that is, the outgoing interface at the PLR the primary path is using. If one or more paths are found, the MPLS task will select one based on best cost and will signal the bypass/detour. If not found and the user has included the strict option, the bypass/detour is not setup and the MPLS task will keep retrying the request to CSPF. Otherwise, if a path exists that meets the other TE constraints, other than the SRLG one, the bypass/detour is setup.

A bypass or a detour LSP path is not intended to be SRLG disjoint from the entire primary path. Only the SRLGs of the outgoing interface at the PLR that the primary path is using are avoided.

When the MPLS task is searching for an SRLG bypass tunnel to associate with the primary path of the protected LSP, it will first check if any configured manual bypass LSP with CSPF enabled satisfies the SRLG constraints. The search skips any non-CSPF manual bypass LSP because there is no ERO returned to check the SRLG constraint. If no path is found, the task will check if an existing dynamic bypass LSP satisfies the SRLG and other primary path constraints. If not found, it will make a request to CSPF.

Once the primary path of the LSP is configured and is operationally up, subsequent changes to the SRLG group membership of an interface the primary path is using are not considered by the MPLS task at the PLR for bypass/detour association until the next opportunity the bypass LSP path or the primary path is resignaled. The path may be resignaled due to a failure or a Make-Before-Break (MBB) operation. MBB occurs as a result of a global revertive operation, a timer based or manual re-optimization of the bypass LSP or LSP primary path, or a user update of the primary path constraints.

Once the bypass or detour path is set up and is operationally up, subsequent changes to the SRLG group membership of an interface the bypass/detour path is using are not considered by the MPLS task at the PLR until the next opportunity when the association with the primary LSP path is rechecked. The association is rechecked if the bypass path is re-optimized using the timer or manual resignal MBB. Detour paths cannot be re-optimized separately from the primary path.

Enabling or disabling srlg-frr command only takes effect when the LSP primary path or the bypass path is resignaled. The user can either wait for the resignal timer to expire or cause the paths to be resignaled immediately by executing, at the ingress LER, the manual resignal command for the LSP primary path or for the bypass LSP path.

A MPLS interface can belong to a maximum of 64 SRLG groups. The SRLG groups are configured using the config>router>if-attribute>srlg-group command. The SRLG groups that an RSVP interface belong to are configured using the srlg-group command in the config>router>mpls>interface context.

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

Default

no srlg-frr

Parameters

strict

Specifies the name of the SRLG group within a virtual router instance.

Values

no srlg-frr (default) srlg-frr (non-strict) srlg-frr strict (strict)

Platforms

All

srlg-group

srlg-group

Syntax

[no] srlg-group group-name [group-name]

no srlg-group

Context

[Tree] (config>service>ies>if>if-attribute srlg-group)

[Tree] (config>router>mpls>if srlg-group)

[Tree] (config>service>vprn>if>if-attribute srlg-group)

[Tree] (config>router>if>if-attribute srlg-group)

Full Context

configure service ies interface if-attribute srlg-group

configure router mpls interface srlg-group

configure service vprn interface if-attribute srlg-group

configure router interface if-attribute srlg-group

Description

This command configures the SRLG membership of an interface. The user can apply SRLGs to an IES, VPRN, network IP, or MPLS interface.

An interface can belong to up to 64 SRLG groups. However, each single operation of the srlg-group command allows a maximum of five (5) groups to be specified at a time. Once an SRLG group is bound to one or more interface, its value cannot be changed until all bindings are removed.

The configured SRLG membership is applied in all levels/areas the interface is participating in. The same interface cannot have different memberships in different levels/areas.

Only the SRLGs bound to an MPLS interface are advertised area-wide in TE link TLVs and sub-TLVs when the traffic-engineering option is enabled in IS-IS or OSPF. IES and VPRN interfaces do not have their attributes advertised in TE TLVs.

The no form of this command deletes one or more of the SRLG memberships of an interface. The user can also delete all memberships of an interface by not specifying a group name.

Parameters

group-name

Specifies the name of the group, up to 32 characters. The association of group name and value should be unique within an IP/MPLS domain. Each single operation of the srlg-group command allows a maximum of 5 groups to be specified at a time.

Platforms

All

srlg-group

Syntax

srlg-group group-name value group-value [penalty-weight penalty-weight]

no srlg-group group-name

Context

[Tree] (config>router>if-attribute srlg-group)

Full Context

configure router if-attribute srlg-group

Description

This command defines a Shared Risk Link Group (SRLG) which can be associated with an IP or MPLS interface.

SRLG is used to tag IP or MPLS interfaces which share a specific fate with the same identifier. For example, an SRLG group identifier could represent all links which use separate fibers but are carried in the same fiber conduit. If the conduit is accidentally cut, all the fiber links are cut which means all interfaces using these fiber links will fail.

The user first configures locally on each router the name and identifier of each SRLG group. A maximum of 1024 SRLGs can be configured per system.

The user then configures the SRLG membership of an interface. The user can apply SRLGs to an IES, VPRN, network IP, or MPLS interface. A maximum of 64 SRLGs can be applied to a given interface.

When SRLGs are applied to MPLS interfaces, CSPF at an LER will exclude the SRLGs of interfaces used by the LSP primary path when computing the path of the secondary path. CSPF at an LER or LSR will also exclude the SRLGs of the outgoing interface of the primary LSP path in the computation of the path of the FRR backup LSP. This provides path disjointness between the primary path and the secondary path or FRR backup path of an LSP.

When SRLGs applied to IES, VPRN, or network IP interfaces, they are evaluated in the route next-hop selection by adding the srlg-enable option in a route next-hop policy template applied to an interface or a set of prefixes. For instance, the user can enable the SRLG constraint to select a LFA next-hop for a prefix which avoids all interfaces that share fate with the primary next-hop.

The following provisioning rules are applied to SRLG configuration. The system will reject the creation of a SRLG if it re-uses the same name but with a different group value than an existing group. The system will also reject the creation of an SRLG if it re-uses the same group value but with a different name than an existing group.

Only the SRLGs bound to an MPLS interface are advertised area-wide in TE link TLVs and sub-TLVs when the traffic-engineering option is enabled in IS-IS or OSPF. IES and VPRN interfaces do not have their attributes advertised in TE TLVs.

A user may specify a penalty weight (penalty-weight) associated with an SRLG. This controls the likelihood of paths with links sharing SRLG values with a primary path being used by a bypass or detour LSP. The higher the penalty weight, the less desirable it is to use the link with a given SRLG.

Parameters

group-name

Specifies the name of the group, up to 32 characters. The association of group name and value should be unique within an IP/MPLS domain.

group-value

Specifies the integer value associated with the group. The association of group name and value should be unique within an IP/MPLS domain.

Values

0 to 4294967295

penalty-weight

Specifies the integer value of the penalty weight that is assigned to the SRLG group

Values

0 to 65535

Default

0

Platforms

All

srrp

srrp

Syntax

srrp srrp-id [create]

no srrp srrp-id

Context

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

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

Full Context

configure service vprn subscriber-interface group-interface srrp

configure service ies subscriber-interface group-interface srrp

Description

This command creates a Subscriber Router Redundancy Protocol (SRRP) instance on a group IP interface. An SRRP instance manages all subscriber subnets within the group interfaces subscriber IP interface or other subscriber IP interfaces that are associated through a wholesale/retail relationship. Only one unique SRRP instance can be configured per group interface.

The no form of this command removes an SRRP instance from a group IP interface. Once removed, the group interface ignores ARP requests for the SRRP gateway IP addresses that may exist on subscriber subnets associated with the group IP interface. Then the group interface stops routing using the redundant IP interface associated with the group IP interface and will stop routing with the SRRP gateway MAC address. Ingress packets destined to the SRRP gateway MAC will also be silently discarded. This is the same behavior as a group IP interface that is disabled (shutdown).

The no form of this command removes the SRRP ID from the configuration.

Default

no srrp

Parameters

srrp-id

Specifies a 32 bit instance ID that must be unique to the system. The instance ID must also match the instance ID used by the remote router that is participating in the same SRRP context. SRRP is intended to perform a function similar to VRRP where adjacent IP hosts within local subnets use a default gateway to access IP hosts on other subnets.

Values

1 to 4294967295

Platforms

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

srrp

Syntax

[no] srrp

Context

[Tree] (debug>router srrp)

Full Context

debug router srrp

Description

This command enables debugging for SRRP packets.

The no form of this command disables debugging.

Platforms

All

srrp

Syntax

[no] srrp

Context

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

Full Context

configure redundancy multi-chassis peer sync srrp

Description

This command specifies whether subscriber routed redundancy protocol (SRRP) information should be synchronized with the multi-chassis peer.

Default

no srrp

Platforms

All

srrp

Syntax

srrp

Context

[Tree] (config>redundancy srrp)

Full Context

configure redundancy srrp

Description

Commands in this context configure SSRP system parameters for BNG CUPS inter-BNG-UP resiliency.

Platforms

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

srrp-enabled-routing

srrp-enabled-routing

Syntax

srrp-enabled-routing [hold-time hold-time]

no srrp-enabled-routing

Context

[Tree] (config>service>vprn>sub-if>grp-if srrp-enabled-routing)

[Tree] (config>service>ies>sub-if>grp-if srrp-enabled-routing)

Full Context

configure service vprn subscriber-interface group-interface srrp-enabled-routing

configure service ies subscriber-interface group-interface srrp-enabled-routing

Description

This command configures SRRP-enabled routing.

The no form of this command reverts to the default.

Parameters

hold-time hold-time

Specifies the hold time, in deci-seconds.

Values

1 to 50

Platforms

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

srrp-instance

srrp-instance

Syntax

[no] srrp-instance srrp-id

Context

[Tree] (config>redundancy>mc>peer>mcr>l3ring srrp-instance)

Full Context

configure redundancy multi-chassis peer mc-ring l3-ring srrp-instance

Description

This command configures an SRRP instance for a Layer 3 ring.

The no form of this command reverts to the default.

Parameters

srrp-id

Specifies the SRRP ID of this SRRP instance.

Values

1 to 4294967295

Platforms

All

srv6

srv6

Syntax

srv6 {origination| termination}

no srv6

Context

[Tree] (config>fwd-path-ext>fpe srv6)

Full Context

configure fwd-path-ext fpe srv6

Description

This command configures if the SRv6 FPE application type is used for the origination or termination of SRv6 tunnels.

The origination or termination of SRv6 on services requires the configuration of a dedicated SRv6 FPE and cannot share the same FPE. A single FPE can be configured for SRv6 origination. One or more FPEs can be configured for SRv6 termination, where a termination SRv6 FPE is assigned one or more configured locators. Transit SRv6 routers do not need SRv6 FPEs.

The no form of this command disables SRv6 on an FPE.

Parameters

origination

Keyword used to specify the origination FPE application type.

termination

Keyword used to specify the termination FPE application type.

Platforms

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

srv6-instance

srv6-instance

Syntax

srv6-instance id default-locator name

no srv6-instance

Context

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

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

Full Context

configure service vprn bgp-evpn segment-routing-v6 srv6-instance

configure service vprn bgp-ipvpn segment-routing-v6 srv6-instance

Description

This command configures an SRv6 instance.

The no form of this command removes the SRv6 instance from the BGP IP-VPN or BGP EVPN control plane for the service.

Parameters

id

Specifies the SRv6 instance ID that exists in the service and is associated to a IP-VPN or EVPN control plane.

Values

1, 2

name

Specifies a default regular or micro-segment locator name, up to 64 characters.

Platforms

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

srv6-locator

srv6-locator

Syntax

srv6-locator name

no srv6-locator

Context

[Tree] (config>router>policy-options>policy-statement>default-action srv6-locator)

[Tree] (config>router>policy-options>policy-statement>entry>action srv6-locator)

Full Context

configure router policy-options policy-statement default-action srv6-locator

configure router policy-options policy-statement entry action srv6-locator

Description

This command configures either a string encoding a midstring parameter delimited by at signs (@), or a reference to a named locator for the SRv6 TLV to use.

For a VRF export policy, the referenced locator must already be configured using the commands in the configure service vprn segment-routing-v6 locator context.

For a BGP export policy, the referenced locator must already be configured using the commands in the configure router segment-routing segment-routing-v6 base-routing-instance locator context.

The no form of this command specifies not to use a locator for the SRv6 TLV.

Default

no srv6-locator

Parameters

name

Specifies either a string encoding a midstring parameter delimited by at signs (@) or a reference to a named locator for the SRv6 TLV to use, up to 64 characters.

Platforms

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

srv6-micro-segment-locator

srv6-micro-segment-locator

Syntax

srv6-micro-segment-locator name

no srv6-micro-segment-locator

Context

[Tree] (config>router>policy-options>policy-statement>entry>action srv6-micro-segment-locator)

[Tree] (config>router>policy-options>policy-statement>default-action srv6-micro-segment-locator)

Full Context

configure router policy-options policy-statement entry action srv6-micro-segment-locator

configure router policy-options policy-statement default-action srv6-micro-segment-locator

Description

This command configures either a string encoding a midstring parameter delimited by at signs (@), or a reference to a named micro-segment (uSID) locator for the SRv6 TLV to use.

For a VRF export policy, the referenced uSID locator must already be configured using the commands in the configure service vprn segment-routing-v6 micro-segment-locator context.

For a BGP export policy, the referenced uSID locator must already be configured using the commands in the configure router segment-routing segment-routing-v6 base-routing-instance micro-segment-locator context.

The no form of this command specifies not to use a uSID locator for the SRv6 TLV.

Default

no srv6-micro-segment-locator

Parameters

name

Specifies either a string encoding a midstring parameter delimited by at signs (@) or a reference to a named uSID locator for the SRv6 TLV to use, up to 64 characters.

Platforms

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

srv6-return-path-bfd-sid

srv6-return-path-bfd-sid

Syntax

srv6-return-path-bfd-sid ipv6-address | param-name

no srv6-return-path-bfd-sid

Context

[Tree] (config>router>policy-options>policy-statement>entry>action srv6-return-path-bfd-sid)

[Tree] (config>router>policy-options>policy-statement>default-action srv6-return-path-bfd-sid)

Full Context

configure router policy-options policy-statement entry action srv6-return-path-bfd-sid

configure router policy-options policy-statement default-action srv6-return-path-bfd-sid

Description

This command applies to the initiator of Seamless Bidirectional Forwarding Detection sessions. This command configures the S-BFD session to echo mode and pushes an additional SRv6 SID in the SRH for S-BFD packets only when it is sent on the imported SRv6 policy.

The return-path SID refers to a binding SID on a SRv6 policy configured on the far-end router. Instead of being routed through the IGP path, the S-BFD packet returns to the initiator through this SRv6 return path. The no form of this command disables the controlled return-path SID and echo mode for S-BFD.

Parameters

ipv6-address

Specifies the IPv6 address.

Values
  • 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

param-name

Specifies the parameter variable name, up to 32 characters. Policy parameters must start and end with an at-sign (@).

Platforms

All

srv6-sid

srv6-sid

Syntax

srv6-sid ipv6-address

no srv6-sid

Context

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

Full Context

configure router segment-routing sr-policies static-policy segment-list segment srv6-sid

Description

This command defines the 128-bit SRv6 SID for the segment. The policy can only be administratively enabled if its type (defined with the configure router segment-routing sr-policies static-policy type command) and all its segments (defined with the configure router segment-routing sr-policies static-policy segment-list segment command) are SRv6.

Parameters

ipv6-address

Specifies the SID, up to 72 characters.

Platforms

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

srv6-sid-prefix

srv6-sid-prefix

Syntax

srv6-sid-prefix {ipv6-prefix/prefix-length | param-name}

no srv6-sid-prefix

Context

[Tree] (config>router>policy-options>policy-statement>entry>from srv6-sid-prefix)

Full Context

configure router policy-options policy-statement entry from srv6-sid-prefix

Description

This command configures either the name of a prefix policy variable or an IPv6 prefix and prefix length, as match criterion for a BGP route.

Note: If the name of a prefix policy variable is the match criterion, the name must start and end with an at sign (@).

A BGP route matches this criterion if it has an SRv6 TLV, and the SID or micro-segment (uSID) value in that TLV is matched by the bits of the IPv6 prefix (up to the specified prefix length).

This match criterion is supported in BGP import policies, BGP export policies, and VRF or VSI import policies.

Default

no srv6-sid-prefix

Parameters

ipv6-prefix/prefix-length

Specifies the IPv6 address and prefix length.

Values

ipv6-prefix:

x:x:x:x:x:x:x:x (host bits must be 0)

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

x - [0..FFFF]H

d - [0..255]D

prefix-length:

0 to 128

param-name

Specifies the name of a prefix policy variable, which can be up to 32 characters and must start and end with an at sign (@)

Platforms

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

srv6-tlv

srv6-tlv

Syntax

srv6-tlv {present | not-present}

no srv6-tlv

Context

[Tree] (config>router>policy-options>policy-statement>entry>from srv6-tlv)

Full Context

configure router policy-options policy-statement entry from srv6-tlv

Description

This command configures whether the entry matches a BGP route with a prefix SID attribute containing an SRv6 TLV. This match criterion is supported in BGP import policies, BGP export policies, and VRF or VSI import policies.

The no form of this command disables the router from taking whether a BGP route has a prefix SID attribute containing an SRv6 TLV into consideration when matching a BGP route with the entry.

Default

no srv6-tlv

Parameters

present

Specifies that a BGP route only matches this entry if it has a prefix SID attribute containing an SRv6 TLV.

not-present

Specifies that a BGP route only matches this entry if it does not have a prefix SID attribute containing an SRv6 TLV.

Platforms

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

ssap

ssap

Syntax

ssap ssap-value [ssap-mask]

no ssap

Context

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

Full Context

configure qos sap-ingress mac-criteria entry match ssap

Description

This command configures an Ethernet 802.2 LLC SSAP value or range for an ingress SAP QoS policy match criterion.

This is a 1-byte field that is part of the 802.2 LLC header of the IEEE 802.3 Ethernet Frame.

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

The no form of this command removes the ssap match criterion.

Default

no ssap

Parameters

ssap-value

The 8-bit ssap match criteria value in hex.

Values

0x00 to 0xFF (hex)

ssap-mask

This is optional and can be used when specifying a range of ssap values to use as the match criteria.

This 8-bit mask can be configured using the following formats.

Table 4. Format Styles to Configure Mask

Format Style

Format Syntax

Example

Decimal

DDD

240

Hexadecimal

0xHH

0xF0

Binary

0bBBBBBBBB

0b11110000

Values

0x00 to 0xFF

Platforms

All

ssap

Syntax

ssap ssap-value [ssap-mask]

no ssap

Context

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

Full Context

configure filter mac-filter entry match ssap

Description

This command configures an Ethernet 802.2 LLC SSAP value or range for a MAC filter match criterion.

This is a one-byte field that is part of the 802.2 LLC header of the IEEE 802.3 Ethernet Frame.

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

The no form of the command removes the ssap match criterion.

Default

no ssap

Parameters

ssap-value

Specifies the 8-bit ssap match criteria value in decimal, hexadecimal or binary.

Values

0 to 255

ssap-mask

Specifies an optional parameter that may be used when specifying a range of ssap values to use as the match criteria.

This 8 bit mask and the ssap value can be configured as described in 8-bit Mask Syntax.

Table 5. 8-bit Mask Syntax

Format Style

Format Syntax

Example

Decimal

DDD

240

Hexadecimal

0xHH

0xF0

Binary

0bBBBBBBBB

0b11110000

Values

0 to 255

Platforms

All

ssap

Syntax

ssap ssap-value [ssap-mask]

no ssap

Context

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

Full Context

configure system security management-access-filter mac-filter entry match ssap

Description

This command configures an Ethernet 802.2 LLC SSAP value or range for a MAC filter match criterion.

This is a one-byte field that is part of the 802.2 LLC header of the IEEE 802.3 Ethernet Frame.

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.

The no form of this command removes the SSAP match criterion.

Default

no ssap

Parameters

ssap-value

Specifies the 8-bit SSAP match criteria value in hex.

Values

0x00 to 0xFF

ssap-mask

Specifies a range of SSAP values to use as the match criteria.

Platforms

All

ssh

ssh

Syntax

ssh host [-l username] [-v ssh-version] [{router router-instance | service-name service-name}] [re-exchange-min minutes] [re-exchange-mbyte megabytes] [-i private-key-filename] [-p port]

Context

[Tree] (ssh)

Full Context

ssh

Description

This command initiates a client SSH session with the remote host and is independent from the administrative or operational state of the SSH server. However, to be the target of an SSH session, the SSH server must be operational. This command also allows the user to initiate an SSH session, with a key reexchange, based on maximum megabytes or minutes, whichever occurs first. If the reexchange options are not set, the default behavior does not perform a key reexchange.

Quitting SSH while in the process of authentication is accomplished by either executing a ctrl-c or "~." (tilde and dot), assuming the "~” is the default escape character for the SSH session.

Parameters

host

Specifies the remote host for the SSH session.

Values

host: user@hostname - [up to 255 characters]

user

up to 32 characters

hostname

[dns-name | ipv4-address | ipv6-address]

ipv4-address

a.b.c.d

ipv6-address

x:x:x:x:x:x:x:x[-interface]

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

x - [0 to FFFF]H

d - [0 to 255]D

interface: up to 32 characters, mandatory for link local addresses

dns-name

up to128 characters

username

Specifies the user name to use when opening the SSH session, up to 32 characters.

router-instance

Specifies the router name or service ID.

Values

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

router-name

"Base”, "management”, "vpls-management”

vprn-svc-id

1 to 2147483647

Default

Base

service-name

Specifies the service name, up to 64 characters.

minutes

Specifies the time interval after which the SSH client will initiate the key reexchange.

Values

1 to 1440 minutes

megabytes

Specifies the number of megabytes, on a SSH session, after which the SSH client will initiate the key reexchange.

Values

1 to 64000 MB

private-key-filename

Specifies the name of the file containing the private key for public-key authentication, up to 255 characters. (The public key must be provided to the SSH server.) When using the private-key-filename option, if the password is required, the user enters the password twice after executing the ssh command.

port

Specifies the listening port for the SR OS SSH client to establish the SSH session with the SSH server.

Values

1 to 65535

Platforms

All

ssh

Syntax

ssh

Context

[Tree] (config>system>security ssh)

[Tree] (config>system>login-control ssh)

Full Context

configure system security ssh

configure system login-control ssh

Description

Commands in this context configure the SSH parameters.

Platforms

All

ssh-authentication-method

ssh-authentication-method

Syntax

ssh-authentication-method

Context

[Tree] (config>system>security>user ssh-authentication-method)

Full Context

configure system security user ssh-authentication-method

Description

Commands in this context configure, at the user level, the authentication method accepted by the SSH server. The user-level configuration overrides the system-level configuration.

Platforms

All

ssh-max-sessions

ssh-max-sessions

Syntax

ssh-max-sessions number-of-sessions

no ssh-max-sessions

Context

[Tree] (config>system>security>cli-session-group ssh-max-sessions)

[Tree] (config>system>security>profile ssh-max-sessions)

Full Context

configure system security cli-session-group ssh-max-sessions

configure system security profile ssh-max-sessions

Description

This command is used to limit the number of SSH-based sessions available to all users that are part of a particular profile, or to all users of all profiles that are part of the same cli-session-group.

The no form of this command disables the command and the profile or group limit is not applied on the number of sessions.

Default

no ssh-max-sessions

Parameters

number-of-sessions

Specifies the maximum number of allowed SSH-based sessions.

Values

0 to 50

Platforms

All

ssh-reply

ssh-reply

Syntax

[no] ssh-reply

Context

[Tree] (config>service>ies>if>vrrp ssh-reply)

Full Context

configure service ies interface vrrp ssh-reply

Description

This command enables the non-owner master to reply to SSH Requests directed at the virtual router instances IP addresses. The SSH request can be received on any routed interface. SSH must not have been disabled at the management security level (either on the parental IP interface or based on the SSH source host address). Proper login and CLI command authentication is still enforced.

When ssh-reply is not enabled, SSH packets to non-owner master virtual IP addresses are silently discarded.

Non-owner backup virtual routers never respond to SSH regardless of the ssh-reply configuration.

The ssh-reply command is only available in non-owner vrrp virtual-router-id nodal context. If the ssh-reply command is not executed, SSH packets to the virtual router instance IP addresses is silently discarded.

The no form of this command restores the default operation of discarding all SSH packets destined to the non-owner virtual router instance IP addresses.

Default

no ssh-reply

Platforms

All

ssh-reply

Syntax

[no] ssh-reply

Context

[Tree] (config>service>vprn>if>vrrp ssh-reply)

Full Context

configure service vprn interface vrrp ssh-reply

Description

This command enables the non-owner master to reply to SSH Requests directed at the virtual router instance’s IP addresses. The SSH request can be received on any routed interface. SSH must not have been disabled at the management security level (either on the parental IP interface or based on the SSH source host address). Proper login and CLI command authentication is still enforced.

When ssh-reply is not enabled, SSH packets to non-owner master virtual IP addresses are silently discarded. Non-owner backup virtual routers never respond to SSH regardless of the ssh-reply configuration.

The ssh-reply command is only available in non-owner vrrp virtual-router-id nodal context. If the ssh-reply command is not executed, SSH packets to the virtual router instance IP addresses is silently discarded.

The no form of this command restores the default operation of discarding all SSH packets destined to the non-owner virtual router instance IP addresses.

Default

no ssh-reply

Platforms

All

ssh-reply

Syntax

[no] ssh-reply

Context

[Tree] (config>router>if>vrrp ssh-reply)

Full Context

configure router interface vrrp ssh-reply

Description

This command enables the non-owner master to reply to SSH requests directed at the virtual router instance IP addresses. This command is only applicable to IPv4.

Non-owner virtual router instances are limited by the VRRP specifications to responding to ARP requests destined to the virtual router IP addresses and routing IP packets not addressed to the virtual router IP addresses.

This limitation can be disregarded for certain applications. Ping, Telnet and SSH can be individually enabled or disabled on a per-virtual-router-instance basis.

The ssh-reply command enables the non-owner master to reply to SSH requests directed at the virtual router instances IP addresses. The SSH request can be received on any routed interface. SSH must not have been disabled at the management security level (either on the parental IP interface or based on the SSH source host address). Correct login and CLI command authentication is still enforced.

When ssh-reply is not enabled, SSH requests to non-owner master virtual IP addresses are silently discarded.

Non-owner backup virtual routers never respond to SSH requests regardless of the ssh-reply setting.

The ssh-reply command is only available in non-owner vrrp nodal context.

By default, SSH requests to the virtual router instance IP addresses are silently discarded.

The no form of the command discards all SSH request messages destined to the non-owner virtual router instance IP addresses.

Default

no ssh-reply — SSH requests to the virtual router instance IP addresses are discarded.

Platforms

All

ssm

ssm

Syntax

ssm

Context

[Tree] (config>port>ethernet ssm)

Full Context

configure port ethernet ssm

Description

This command enables the Ethernet Synchronization Messaging Channel (ESMC) for the Ethernet port. ESMC carries the Synchronization Status Message (SSM) code representing the quality level of the source of frequency of the central clock of the node.

Platforms

All

ssm-assert-compatible-mode

ssm-assert-compatible-mode

Syntax

ssm-assert-compatible-mode [enable | disable]

Context

[Tree] (config>service>vprn>pim ssm-assert-compatible-mode)

Full Context

configure service vprn pim ssm-assert-compatible-mode

Description

This command specifies whether SSM assert is enabled in compatibility mode for this PIM protocol instance. When enabled, for SSM groups, PIM will consider the SPT bit to be implicitly set to compute the value of CouldAssert (S,G,I) as defined in RFC 4601, Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised). When disabled, for SSM groups, PIM will not assume the SPT bit to be set. The SPT bit is set by Update_SPTbit(S,G,iif) macro defined in RFC 4601.

Default

ssm-assert-compatible-mode disable

Parameters

enable

enables SSM assert in compatibility mode for this PIM protocol instance

disable

disabled SSM assert in compatibility mode for this PIM protocol instance

Platforms

All

ssm-bit

ssm-bit

Syntax

ssm-bit sa-bit

Context

[Tree] (config>system>sync-if-timing>bits ssm-bit)

Full Context

configure system sync-if-timing bits ssm-bit

Description

This command configures which sa-bit to use for conveying SSM information when the interface-type is E1.

Default

ssm-bit 8

Parameters

sa-bit

Specifies the sa-bit value.

Values

4 to 8

Platforms

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

ssm-default-range-disable

ssm-default-range-disable

Syntax

ssm-default-range-disable ipv4

Context

[Tree] (config>service>vprn>pim ssm-default-range-disable)

Full Context

configure service vprn pim ssm-default-range-disable

Description

This command specifies whether to disable the use of default range (232/8) for SSM so that it can be used by ASM to process (*,G). When enabled, the use of default range is disabled for SSM and it can be used by ASM. When disabled, the SSM default range is enabled.

Default

ssm-default-range-disable

Platforms

All

ssm-groups

ssm-groups

Syntax

[no] ssm-groups

Context

[Tree] (config>service>vprn ssm-groups)

Full Context

configure service vprn ssm-groups

Description

This command enables access to the context to enable a source-specific multicast (SSM) configuration instance.

Platforms

All

ssm-groups

Syntax

[no] ssm-groups

Context

[Tree] (config>router>pim ssm-groups)

Full Context

configure router pim ssm-groups

Description

Commands in this context enable an ssm-group configuration instance.

Platforms

All

ssm-translate

ssm-translate

Syntax

ssm-translate

Context

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

[Tree] (config>service>vprn>igmp>if ssm-translate)

Full Context

configure service vprn igmp ssm-translate

configure service vprn igmp interface ssm-translate

Description

Commands in this context configure group ranges which are translated to SSM (S,G) entries. If the static entry needs to be created, it has to be translated from a IGMPv1 IGMPv2 request to a Source Specific Multicast (SSM) join. An SSM translate source can only be added if the starg command is not enabled. An error message is generated if you try to configure the source command with starg command enabled.

Platforms

All

ssm-translate

Syntax

ssm-translate

Context

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

Full Context

configure service vprn mld ssm-translate

Description

Commands in this context configure group ranges which are translated to SSM (S,G) entries. If the static entry needs to be created, it has to be translated from a IGMPv1 IGMPv2 request to a Source Specific Multicast (SSM) join. An SSM translate source can only be added if the starg command is not enabled. An error message is generated if you try to configure the source command with starg command enabled.

Platforms

All

ssm-translate

Syntax

ssm-translate

Context

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

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

Full Context

configure router igmp interface ssm-translate

configure router igmp ssm-translate

Description

Commands in this context configure group ranges which are translated to SSM (S,G) entries. If the static entry needs to be created, it has to be translated from a IGMPv1 IGMPv2 request to a Source Specific Multicast (SSM) join. An SSM translate source can only be added if the starg command is not enabled. An error message is generated if you try to configure the source command with starg command enabled.

Platforms

All

ssm-translate

Syntax

ssm-translate

Context

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

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

Full Context

configure router mld interface ssm-translate

configure router mld ssm-translate

Description

Commands in this context configure group ranges which are translated to SSM (S,G) entries. If the static entry needs to be created, it has to be translated from a IGMPv1 IGMPv2 request to a Source Specific Multicast (SSM) join. An SSM translate source can only be added if the starg command is not enabled. An error message is generated if you try to configure the source command with starg command enabled.

Platforms

All

stable-pool-sizing

stable-pool-sizing

Syntax

[no] stable-pool-sizing

Context

[Tree] (config>card>fp stable-pool-sizing)

Full Context

configure card fp stable-pool-sizing

Description

This command provides a stable buffer pool allocation environment for all default port buffer pools on a forwarding plane. This stable environment is provided at the expense of optimal buffer allocation between the various port buffer pools. Normally, port pools are sized according to a ports relative bandwidth with other ports and the ability of a port to use pool buffers. As an example, on a forwarding plane with two potential MDAs and only one equipped, the normal behavior is to provide all available default pool buffers to the ports on the currently equipped MDA. If a second MDA is equipped in the future, buffers are freed from the existing MDA and provided to the ports on the new MDA. Stable pool sizing alters this behavior by reserving buffers for both MDAs whether they are equipped or not thus preventing a resizing event when an MDA is equipped. In addition, existing ports on a module always receive their maximum bandwidth share of buffers independent on any sub-rate condition that may currently exist. This provides a stable amount of buffers to other ports on the module independent of link or configuration events that may occur on the port.

Stable pool sizing preserves the ability to modify the effective bandwidth used to determine a port’s relative share of the available buffers through the use of the ing-percentage-of-rate and egr-percentage-of-rate commands under the port configuration. Changing the values associated with these commands will cause a reevaluation of buffer distribution and thus a possible resizing of pools on each port within the module. These commands have no effect on ports associated with other modules on the forwarding plane.

Stable pool sizing may be enabled or disabled at any time on a forwarding plane. The system will dynamically change the pool sizes according to the stable pool sizing state.

When a port connector breakout is configured, its ports is included in the stable pool sizing calculation. Consequently, adding or removing a port connector breakout to or from the configuration will cause the buffer pool allocation to be recalculated even when stable pool sizing is enabled.

The no form of this command disables stable pool sizing on a forwarding plane. Existing buffer pools are resized according to normal pool sizing behavior.

Platforms

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

stack

stack

Syntax

stack [ipv4] [ipv6-slaac]

no stack

Context

[Tree] (config>subscr-mgmt>pppoe-client-policy stack)

Full Context

configure subscriber-mgmt pppoe-client-policy stack

Description

This command defines which NCP session is started in the PPPoE client and how addresses are retrieved within that NCP session.

Default

stack ipv4

Parameters

ipv4

Indicates that IPCP should be started and used to retrieve an IPv4 address.

ipv6-slaac

Indicates that IPv6CP should be started and that SLAAC is used to retrieve an IPv6 prefix.

Platforms

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

stack-capability-signaling

stack-capability-signaling

Syntax

[no] stack-capability-signaling

Context

[Tree] (config>service>ipipe stack-capability-signaling)

Full Context

configure service ipipe stack-capability-signaling

Description

This command enables stack-capability signaling in the initial label mapping message of the Ipipe PW to indicate that IPv6 is supported.

When enabled, the 7750 SR includes the stack-capability TLV with the IPv6 stack bit set according to the ce-address-discovery ipv6 keyword, and also checks the value of the stack-capability TLV received from the far end.

This command must be blocked if no ce-address-discovery is specified, or the ipv6 keyword is not included with the ce-address-discovery command.

This command if only applicable to the Ipipe service and must be blocked for all other services.

This command has no effect if both SAPs on the Ipipe service are local to the node.

Default

no stack-capability-signaling

Platforms

All

stale-routes-time

stale-routes-time

Syntax

[no] stale-routes-time time

Context

[Tree] (config>service>vprn>bgp>group>neighbor>graceful-restart stale-routes-time)

[Tree] (config>service>vprn>bgp>graceful-restart stale-routes-time)

[Tree] (config>service>vprn>bgp>group>graceful-restart stale-routes-time)

Full Context

configure service vprn bgp group neighbor graceful-restart stale-routes-time

configure service vprn bgp graceful-restart stale-routes-time

configure service vprn bgp group graceful-restart stale-routes-time

Description

This command configures the time period to keep stale routes before the END-OF-RIB message is received from the restarting router.

Default

360 seconds

Parameters

time

1 to 3600 seconds

Platforms

All

stale-routes-time

Syntax

stale-routes-time time

no stale-routes-time

Context

[Tree] (config>router>bgp>graceful-restart stale-routes-time)

[Tree] (config>router>bgp>group>neighbor>graceful-restart stale-routes-time)

[Tree] (config>router>bgp>group>graceful-restart stale-routes-time)

Full Context

configure router bgp graceful-restart stale-routes-time

configure router bgp group neighbor graceful-restart stale-routes-time

configure router bgp group graceful-restart stale-routes-time

Description

This command configures the maximum amount of time in seconds that stale routes should be maintained after a graceful restart is initiated.

The no form of this command resets the stale routes time back to the default of 360 seconds.

Default

no stale-routes-time

Parameters

time

Specifies the amount of time that stale routes should be maintained after a graceful restart is initiated.

Values

1 to 3600 seconds

Platforms

All

stale-time

stale-time

Syntax

stale-time seconds

no stale-time

Context

[Tree] (config>service>vprn>if>ipv6 stale-time)

[Tree] (config>service>ies>if>ipv6 stale-time)

[Tree] (config>service>vprn>ipv6 stale-time)

[Tree] (config>service>ies>ipv6 stale-time)

Full Context

configure service vprn interface ipv6 stale-time

configure service ies interface ipv6 stale-time

configure service vprn ipv6 stale-time

configure service ies ipv6 stale-time

Description

This command configures the time a neighbor discovery cache entry can remain stale before being removed.

The no form of this command removes the stale-time value.

Default

no stale-time

Parameters

seconds

The allowed stale time (in seconds) before a neighbor discovery cache entry is removed.

Values

60 to 65535

Platforms

All

stale-time

Syntax

stale-time seconds

no stale-time

Context

[Tree] (config>router>ipv6 stale-time)

Full Context

configure router ipv6 stale-time

Description

This command configures the time a neighbor discovery cache entry can remain stale before being removed.

The no form of this command removes the stale-time value.

Default

stale-time 14400

Parameters

seconds

Specifies the allowed stale time (in seconds) before a neighbor discovery cache entry is removed.

Values

60 to 65535

Platforms

All

stale-time

Syntax

stale-time seconds

no stale-time

Context

[Tree] (config>router>origin-validation>rpki-session stale-time)

Full Context

configure router origin-validation rpki-session stale-time

Description

This command configures the maximum length of time that prefix origin validation records learned from the cache server remain usable after the RPKI-Router session goes down. The default stale-time is 3600 seconds (1 hour). When the timer expires all remaining stale entries associated with the session are deleted.

Default

no stale-time

Parameters

seconds

Specifies a time, in seconds.

Values

60 to 3600

Platforms

All

stale-time

Syntax

stale-time seconds

no stale-time

Context

[Tree] (config>router>if>ipv6 stale-time)

Full Context

configure router interface ipv6 stale-time

Description

This command configures the time a neighbor discovery cache entry can remain stale before being removed.

The no form of this command removes the stale-time value.

Default

no stale-time

Parameters

seconds

The allowed stale time (in seconds) before a neighbor discovery cache entry is removed.

Values

60 to 65535

Platforms

All

standard-multi-instance

standard-multi-instance

Syntax

[no] standard-multi-instance

Context

[Tree] (config>service>vprn>isis standard-multi-instance)

Full Context

configure service vprn isis standard-multi-instance

Description

This command enables IS-IS multi-instance (MI) as described in draft-ginsberg-isis-mi-bis-01. Multiple instances allow instance-specific adjacencies to be formed that support multiple network topologies on the same physical interfaces. Each instance has an LSDB, and each PDU contains a TLV identifying the instance and the topology to which the PDU belongs. A single topology is supported in each instance, so the instance-specific topology identifier (ITID) is set to 0 and cannot be changed.

The standard-multi-instance (based on draft-ginsberg-isis-mi-bis-01) and iid-tlv-enable (based on draft-ietf-isis-mi-02) commands cannot be configured in the same instance, because the MAC addresses and PDUs from the two standards are incompatible.

The no form of this command removes the standard-multi-instance configuration.

Default

no standard-multi-instance

Platforms

All

standard-multi-instance

Syntax

[no] standard-multi-instance

Context

[Tree] (config>router>isis standard-multi-instance)

Full Context

configure router isis standard-multi-instance

Description

This command enables IS-IS multi-instance (MI) as described in draft-ginsberg-isis-mi-bis-01. Multiple instances allow instance-specific adjacencies to be formed that support multiple network topologies on the same physical interfaces. Each instance has an LSDB, and each PDU contains a TLV identifying the instance and the topology to which the PDU belongs. A single topology is supported in each instance, so the instance-specific topology identifier (ITID) is set to 0 and cannot be changed.

The standard-multi-instance (based on draft-ginsberg-isis-mi-bis-01) and iid-tlv-enable (based on draft-ietf-isis-mi-02) commands cannot be configured in the same instance, because the MAC addresses and PDUs from the two standards are incompatible.

The no form of this command removes the standard-multi-instance configuration.

Default

no standard-multi-instance

Platforms

All

standby

standby

Syntax

[no] standby

Context

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

Full Context

configure router mpls lsp secondary standby

Description

The secondary path LSP is normally signaled once the primary path LSP fails. The standby keyword ensures that the secondary path LSP is signaled and maintained indefinitely in a hot standby state. Standby paths are selected in preference to non-standby secondary paths. When multiple standby secondary paths exist, then the path-preference is used to determine the order in which the paths are selected. If multiple standby secondary paths have the same, lowest, path-preference value then the system will select the path with the lowest up-time. When the primary path is re-established then the traffic is switched back to the primary path LSP.

The no form of this command specifies that the secondary LSP is signaled when the primary path LSP fails.

Platforms

All

standby-forwarding

standby-forwarding

Syntax

[no] standby-forwarding

Context

[Tree] (config>service>ies>if>ipv6>vrrp standby-forwarding)

Full Context

configure service ies interface ipv6 vrrp standby-forwarding

Description

This command allows the forwarding of packets by a standby router.

The no form of this command specifies that a standby router should not forward traffic sent to virtual router's MAC address. However, the standby router should forward traffic sent to the standby router’s real MAC address.

Default

no standby-forwarding

Platforms

All

standby-forwarding

Syntax

[no] standby-forwarding

Context

[Tree] (config>service>ies>if>vrrp standby-forwarding)

Full Context

configure service ies interface vrrp standby-forwarding

Description

This command allows the forwarding of packets by a standby router.

The no form of this command specifies that a standby router should not forward traffic sent to virtual router's MAC address. However, the standby router should forward traffic sent to the standby router’s real MAC address.

Default

no standby-forwarding

Platforms

All

standby-forwarding

Syntax

[no] standby-forwarding

Context

[Tree] (config>service>vprn>if>ipv6>vrrp standby-forwarding)

[Tree] (config>service>vprn>if>vrrp standby-forwarding)

Full Context

configure service vprn interface ipv6 vrrp standby-forwarding

configure service vprn interface vrrp standby-forwarding

Description

This command allows the forwarding of packets by a standby router.

The no form of this command specifies that a standby router should not forward traffic sent to virtual router's MAC address. However, the standby router should forward traffic sent to the standby router’s real MAC address.

Default

no standby-forwarding

Platforms

All

standby-forwarding

Syntax

[no] standby-forwarding

Context

[Tree] (config>router>if>vrrp standby-forwarding)

[Tree] (config>router>if>ipv6>vrrp standby-forwarding)

Full Context

configure router interface vrrp standby-forwarding

configure router interface ipv6 vrrp standby-forwarding

Description

This command specifies whether this VRRP instance allows forwarding packets to a standby router. When disabled, a standby router should not forward traffic sent to virtual router's MAC address. However, the standby router should forward traffic sent to the standby router’s real MAC address. When enabled, a standby router should forward all traffic.

Default

no standby-forwarding

Platforms

All

standby-ip-lifetime

standby-ip-lifetime

Syntax

standby-ip-lifetime [days days] [hrs hrs] [min min] [sec sec]

standby-ip-lifetime [seconds]

standby-ip-lifetime

Context

[Tree] (config>subscr-mgmt>vrgw>brg>brg-profile>dhcp-pool standby-ip-lifetime)

Full Context

configure subscriber-mgmt vrgw brg brg-profile dhcp-pool standby-ip-lifetime

Description

This command defines how long these addresses are kept aside when standby addresses are signaled to the pool. During this time these addresses can only be used by devices explicitly requesting the IP (for example, datatrigger or DHCP renew/rebind). When the timer expires the addresses will again become available for dynamic allocation.

Default

standby-ip-lifetime hrs 6

Parameters

days

Specifies the standby IP lifetime in days.

Values

1 to 3650

hrs

Specifies the standby IP lifetime in hours.

Values

1 to 23

min

Specifies the standby IP lifetime in minutes.

Values

1 to 59

sec

Specifies the standby IP lifetime in seconds.

Values

1 to 59

seconds

Specifies the lifetime of the standby IP addresses

Values

300 to 315446399

seconds

Specifies the lifetime in seconds.

Values

300 to 315446399

Platforms

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

standby-mep-shutdown

standby-mep-shutdown

Syntax

[no] standby-mep-shutdown

Context

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

Full Context

configure eth-cfm redundancy mc-lag standby-mep-shutdown

Description

This system wide command enables MEPs to track the state of MC-LAG. This allows MEPs on the standby MC-LAG to act administratively down.

The no form of command disables the MEP tracking.

Default

no standby-mep-shutdown

Platforms

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

standby-signaling

standby-signaling

Syntax

standby-signaling {lacp | power-off}

no standby-signaling

Context

[Tree] (config>lag standby-signaling)

Full Context

configure lag standby-signaling

Description

This command specifies how the state of a member port is signaled to the remote side when the status corresponding to this member port has the standby value.

Default

standby-signaling lacp

Platforms

All

standby-signaling-master

standby-signaling-master

Syntax

[no] standby-signaling-master

Context

[Tree] (config>service>ipipe>endpoint standby-signaling-master)

[Tree] (config>service>epipe>endpoint standby-signaling-master)

Full Context

configure service ipipe endpoint standby-signaling-master

configure service epipe endpoint standby-signaling-master

Description

When this command is enabled, the pseudowire standby bit (value 0x00000020) is sent to T-LDP peer for each spoke SDP of the endpoint that is selected as a standby.

This command is mutually exclusive with a VLL mate SAP created on a mc-lag/mc-aps or ICB. It is also mutually exclusive with vc-switching.

Default

standby-signaling-master

Platforms

All

standby-signaling-slave

standby-signaling-slave

Syntax

[no] standby-signaling-slave

Context

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

Full Context

configure service epipe spoke-sdp-fec standby-signaling-slave

Description

This command enables standby-signaling-slave for an Epipe.

Platforms

All

standby-signaling-slave

Syntax

[no] standby-signaling-slave

Context

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

[Tree] (config>service>epipe>endpoint standby-signaling-slave)

Full Context

configure service epipe spoke-sdp standby-signaling-slave

configure service epipe endpoint standby-signaling-slave

Description

When this command is enabled, the node will block the transmit forwarding direction of a spoke SDP based on the pseudowire standby bit received from a T-LDP peer.

This command is present at the endpoint level as well as the spoke SDP level. If the spoke SDP is part of an explicit-endpoint, it will not be possible to change this setting at the spoke SDP level. An existing spoke SDP can be made part of the explicit endpoint only if the settings do not conflict. A newly created spoke SDP, which is part of a specific explicit-endpoint, will inherit this setting from the endpoint configuration.

This command is mutually exclusive with an endpoint that is part of an mc-lag, mc-aps or an ICB.

If the command is disabled, the node assumes the existing independent mode of behavior for the forwarding on the spoke SDP.

Default

no standby-signaling-slave

Platforms

All

starg

starg

Syntax

[no] starg

Context

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

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

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

Full Context

configure subscriber-mgmt igmp-policy static group starg

configure subscriber-mgmt mld-policy static group starg

configure subscriber-mgmt igmp-policy starg

Description

This command adds a static (*,G) entry. This command can only be enabled if no existing source addresses for this group are specified.

The no form of this command removes the starg entry from the configuration.

Platforms

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

starg

Syntax

[no] starg

Context

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

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

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

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

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

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

Full Context

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

configure service vpls sap igmp-snooping static group starg

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

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

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

configure service vpls sap mld-snooping static group starg

Description

This command adds a static (*,g) entry to allow multicast traffic for the corresponding multicast group from any source. This command can only be enabled if no existing source addresses for this group are specified.

The no form of this command removes the starg entry from the configuration.

Default

no starg

Platforms

All

starg

Syntax

starg

Context

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

Full Context

configure service vprn igmp interface static group starg

Description

This command adds a static (*,G) entry. This command can only be enabled if no existing source addresses for this group are specified.

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

Platforms

All

starg

Syntax

[no] starg

Context

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

Full Context

configure service vprn mld interface static group starg

Description

This command adds a static (*,G) entry. This command can only be enabled if no existing source addresses for this group are specified.

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

Platforms

All

starg

Syntax

[no] starg

Context

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

Full Context

configure router igmp interface static group starg

Description

This command adds a static (*,G) entry. This command can only be enabled if no existing source addresses for this group are specified.

Use the no form of the command to remove the (*,G) entry from the configuration.

Platforms

All

starg

Syntax

[no] starg

Context

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

Full Context

configure router igmp tunnel-interface static group starg

Description

This command adds a static (*,G) group entry in a static group join on a tunnel interface associated with a P2MP RSVP LSP.

This command can only be enabled if no existing source addresses for this group are specified.

The no form of the command removes the (*,G) entry from the configuration.

Platforms

All

starg

Syntax

[no] starg

Context

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

Full Context

configure router mld interface static group starg

Description

This command adds a static (*,G) entry. This command can only be enabled if no existing source addresses for this group are specified.

The no form of this command removes the starg entry from the configuration.

Platforms

All

start

start

Syntax

start {immediate | on-new-session}

Context

[Tree] (debug>app-assure>group>traffic-capture>record start)

Full Context

debug application-assurance group traffic-capture record start

Description

This command records limit conditions.

Parameters

immediate

Start recording immediately for new or existing flows or sessions.

on-new-session

Only start recording record for new flows or sessions.

Platforms

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

start

Syntax

start start-week start-day start-month hours-minutes

Context

[Tree] (config>system>time>dst-zone start)

Full Context

configure system time dst-zone start

Description

This command configures start of summer time settings.

Default

start first sunday january 00:00

Parameters

start-week

Specifies the starting week of the month when the summer time takes effect.

Values

first, second, third, fourth, last

Default

first

start-day

Specifies the starting day of the week when the summer time takes effect.

Values

sunday, monday, tuesday, wednesday, thursday, friday, saturday

Default

sunday

start-month

Specifies the starting month of the year when the summer time takes effect.

Values

january, february, march, april, may, june, july, august, september, october, november, december

Default

january

hours-minutes

Specifies the time at which the summer time takes effect, in hh:mm format.

Values

hours: 00 to 23

minutes: 00 to 59

Default

00:00

Platforms

All

start-avg

start-avg

Syntax

start-avg percent

no start-avg

Context

[Tree] (config>qos>slope-policy>high-slope start-avg)

[Tree] (config>qos>slope-policy>low-slope start-avg)

[Tree] (config>qos>slope-policy>highplus-slope start-avg)

[Tree] (config>qos>slope-policy>exceed-slope start-avg)

Full Context

configure qos slope-policy high-slope start-avg

configure qos slope-policy low-slope start-avg

configure qos slope-policy highplus-slope start-avg

configure qos slope-policy exceed-slope start-avg

Description

This command sets the exceed, low, high, or highplus Random Early Detection (RED) slope position for the shared buffer average utilization value where the packet discard probability starts to increase above zero. The percent parameter is expressed as a percentage of the shared buffer size.

The no form of this command restores the start-avg value to the default setting. If the max-avg setting is smaller than the default, an error will occur and the start-avg setting will not be changed to the default.

Default

start-avg 85 - Highplus slope default is 85% buffer utilization before discard probability starts to increase above zero.

start-avg 70 — High slope default is 70% buffer utilization before discard probability starts to increase above zero.

start-avg 50 — Low slope default is 50% buffer utilization before discard probability starts to increase above zero.

start-avg 30 — Exceed slope default is 30% buffer utilization before discard probability starts to increase above zero.

Parameters

percent

The percentage of the shared buffer space for the buffer pool at which point the drop probability starts to increase above zero. The value entered must be less than or equal to the current setting of max-avg. If the entered value is greater than the current value of max-avg, an error will occur and no change will take place.

Values

0 to 100

Platforms

All

start-entry

start-entry

Syntax

start-entry entry-id count count

no start-entry

Context

[Tree] (config>li>li-filter-block-reservation>li-reserved-block start-entry)

Full Context

configure li li-filter-block-reservation li-reserved-block start-entry

Description

This command defines a block of reserved filter entries that are used to insert LI filter entries into a normal filter.

The no form of this command removes the entry ID and count from the configuration.

Parameters

entry-id

Specifies an entry identification to start a block of reserved filter entries.

Values

1 to 65536

count

Specifies the number of entries in the block.

Values

1 to 8192

Platforms

All

start-label

start-label

Syntax

start-label start-value end-label end-value

no start-label

Context

[Tree] (config>router>mpls-labels>reserved-label-block start-label)

Full Context

configure router mpls-labels reserved-label-block start-label

Description

This command configures start and end labels for a reserved label block. This command must be configured for a reserved label block to be created.

Default

start-label 0, end-label 0

Parameters

start-value

Specifies a starting value.

Values

18432 to 524287 within dynamic label range | 1048575 (FP4 or FP5 only)

end-value

Specifies an ending value.

Values

18432 to 524287 within dynamic label range | 1048575 (FP4 or FP5 only)

Platforms

All

startup-wait-time

startup-wait-time

Syntax

startup-wait-time [min minutes] [sec seconds] [hrs hours]

no startup-wait-time [min minutes] [sec seconds]

Context

[Tree] (config>router>dhcp6>server>failover startup-wait-time)

[Tree] (config>router>dhcp>server>failover startup-wait-time)

[Tree] (config>router>dhcp6>server>pool>failover startup-wait-time)

[Tree] (config>router>dhcp>server>pool>failover startup-wait-time)

Full Context

configure router dhcp6 local-dhcp-server failover startup-wait-time

configure router dhcp local-dhcp-server failover startup-wait-time

configure router dhcp6 server pool failover startup-wait-time

configure router dhcp server pool failover startup-wait-time

Description

This command enables the startup wait time during which each peer waits after the initialization process before assuming the active role for the prefix designated as local or access-driven. This is to avoid transient issues during the initialization process.

The startup-wait-time should be configured to an interval in which, after boot, both nodes can set up an MCS TCP link and start MCS. The timer is restarted each time the server downloads a lease from the MCS database and stops when the last state record from the peer is synchronized. The next state is (PRE-)NORMAL, unless the timer times out or is forced to stop via the tools command (tools>perform>router>dhcp or dhcp6>local-dhcp-server server-name>pool/failover>abort-startup-wait), in which case the local DHCP server transitions immediately to the COMMUNICATIONS-INTERRUPTED state.

Default

startup-wait-time min 2

Parameters

minutes

Specifies the startup wait time, in minutes.

Values

1 to 59

seconds

Specifies the startup wait time, in seconds.

Values

1 to 59

hours

Specifies the startup wait time, in hours.

Values

1

Platforms

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

stat-mode

stat-mode

Syntax

stat-mode stat-mode

no stat mode

Context

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

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

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

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

Full Context

configure subscriber-mgmt sla-profile egress qos policer stat-mode

configure subscriber-mgmt sla-profile ingress qos queue stat-mode

configure subscriber-mgmt sla-profile egress qos queue stat-mode

configure subscriber-mgmt sla-profile ingress qos policer stat-mode

Description

This command is used to configure the forwarding plane octet and packet counters of a policer or queue to count packets of a specific type or state. For example separate counters for IPv4/IPv6 or separate counters for offered high and low priority policed traffic.

For policers, this command overrides the policer stat-mode configuration as defined in the sap-ingress or sap-egress qos policy. For details on sap-ingress and sap-egress policer stat-mode, refer to the 7450 ESS, 7750 SR, 7950 XRS, and VSR Quality of Service Guide. For use in Enhanced Subscriber Management (ESM) context only, an additional stat-mode enables separate counters for IPv4 and IPv6 packets.

When a policer’s stat-mode is changed while the sla profile is in use, any previous counter values are lost and any new counters are set to zero.

For queues, this command sets the stat-mode. Queue stat-mode is only available for use in Enhanced Subscriber Management (ESM) context to enable separate IPv4/IPv6 counters.

A queue’s stat-mode cannot be changed while the SLA profile is in use.

The no form of this command reverts to the default.

Default

For policers, the default is no stat-mode override. The sap-ingress or sap-egress stat-mode is used instead.

For queues, the default is to count in-/out-of-profile octets and packets.

Parameters

stat-mode

Specifies the stat mode for the policer.

For ingress and egress qos queue stat-mode overrides.

For ingress and egress qos policer stat-mode overrides, refer to the 7450 ESS, 7750 SR, 7950 XRS, and VSR Quality of Service Guide for details on the sap-ingress and sap-egress policer stat-mode parameters.

For use in Enhanced Subscriber Management (ESM) context only:

Values

no-stats, minimal, offered-profile-no-cir, offered-priority-no-cir, offered-profile-cir, offered-priority-cir, offered-total-cir, offered-limited-profile-cir, offered-profile-capped-cir, offered-limited-capped-cir, v4-v6 (count IPv4 and IPv6 forwarded/dropped octets and packets separately)

Platforms

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

  • configure subscriber-mgmt sla-profile ingress qos policer stat-mode
  • configure subscriber-mgmt sla-profile egress qos policer stat-mode

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

  • configure subscriber-mgmt sla-profile egress qos queue stat-mode
  • configure subscriber-mgmt sla-profile ingress qos queue stat-mode

stat-mode

Syntax

stat-mode stat-mode

no stat mode

Context

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

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

Full Context

configure card fp ingress access queue-group policer-override policer stat-mode

configure card fp ingress network queue-group policer-override policer stat-mode

Description

This command configures the forwarding plane counters that allow offered, output and discard accounting to occur for the policer. An ingress policer has multiple types of offered packets (explicit in-profile, explicit out-of-profile, high priority or low priority) and each of these offered types is interacting with the policer’s metering and profiling functions resulting in colored output packets (green, yellow and red). Due to the large number of policers, it is not economical to allocate counters in the forwarding plane for all possible offered packet types and output conditions. Many policers will not be configured with a CIR profiling rate and not all policers will receive explicitly profiled offered packets. The stat-mode command allows provisioning of the number of counters each policer requires and how the offered packet types and output conditions should be mapped to the counters.

While a no-stats mode is supported which prevents any packet accounting, the use of the policer’s parent command requires at the policer's stat-mode to be set at least to the minimal setting so that offered stats are available for the policer's Fair Information Rate (FIR) to be calculated. Once a policer has been made a child to a parent policer, the stat-mode cannot be changed to no-stats unless the policer parenting is first removed.

Each time the policer’s stat-mode is changed, any previous counter values are lost and any new counters are set to zero.

Each mode uses a certain number of counters per policer instance that are allocated from the forwarding plane’s policer counter resources. You can view the total/allocated/free stats by using the tools dump resource-usage command. If insufficient counters exist to implement a mode on any policer instance, the stat-mode change will fail and the previous mode will continue unaffected for all instances of the policer.

The default stat-mode when a policer is created within the policy is minimal.

The stat-mode setting defined for the policer in the QoS policy may be overridden on an sla-profile or SAP where the policy is applied. If insufficient policer counter resources exist to implement the override, the stat-mode override command will fail. The previous stat-mode setting active for the policer will continue to be used by the policer.

The no form of this command attempts to return the policer’s stat-mode setting to minimal. The command will fail if insufficient policer counter resources exist to implement minimal where the QoS policer is currently applied and has a forwarding class mapping.

Parameters

See the 7450 ESS, 7750 SR, 7950 XRS, and VSR Quality of Service Guide for details on the policer stat-mode parameters.

Platforms

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

stat-mode

Syntax

stat-mode stat-mode

no stat-mode

Context

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

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

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

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

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

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

Full Context

configure service epipe sap ingress policer-override policer stat-mode

configure service cpipe sap ingress policer-override policer stat-mode

configure service cpipe sap egress policer-override policer stat-mode

configure service ipipe sap egress policer-override policer stat-mode

configure service ipipe sap ingress policer-override policer stat-mode

configure service epipe sap egress policer-override policer stat-mode

Description

The SAP QoS policy’s policer stat-mode command is used to configure the forwarding plane counters that allow offered, output, and discard accounting to occur for the policer. A policer has multiple types of offered packets (for example, soft in-profile and out-of-profile from ingress and hard in-profile and out-of-profile due to egress profile overrides) and each of these offered types is interacting with the policers metering and profiling functions resulting in colored output packets (green, yellow, and red). Due to the potentially large number of egress policers, it is not economical to allocate counters in the forwarding plane for all possible offered packet types and output conditions. Many policers will not be configured with a CIR profiling rate and not all policers will receive explicitly re-profiled offered packets. The stat-mode command allows provisioning of the number of counters each policer requires and indicates how the offered packet types and output conditions should be mapped to the counters.

While a no-stats mode is supported that prevents any packet accounting, the use of the policer’s parent command requires that the policer’s stat-mode to be set at least to the minimal setting so that offered statistics are available for the policer’s Fair Information Rate (FIR) to be calculated.

Each time the policer’s stat mode is changed, any previous counter values are lost and any new counters are set to zero.

Each mode uses a certain number of counters per policer instance that are allocated from the forwarding plane’s policer counter resources. The total/allocated/free statistics can be viewed by using the tools dump resource-usage card slot-num fp fp-number command. If insufficient counters exist to implement a mode on any policer instance, the stat-mode change will fail and the previous mode will continue unaffected for all instances of the policer.

The stat-mode setting defined for the policer in the QoS policy may be overridden on a SAP where the policy is applied. If insufficient policer counter resources exist to implement the override, the stat-mode override command will fail. The current active stat mode setting will continue to be used by the policer.

The command will fail if insufficient policer counter resources exist to implement minimal where the QoS policer is currently applied and has a forwarding class mapping.

The no form of this command attempts to return the policer’s stat-mode setting to minimal.

Refer to the 7450 ESS, 7750 SR, 7950 XRS, and VSR Quality of Service Guide for detailed information about the supported parameters for the policer stat-mode command.

Platforms

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

  • configure service ipipe sap ingress policer-override policer stat-mode
  • configure service ipipe sap egress policer-override policer stat-mode
  • configure service epipe sap egress policer-override policer stat-mode
  • configure service epipe sap ingress policer-override policer stat-mode

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

  • configure service cpipe sap egress policer-override policer stat-mode
  • configure service cpipe sap ingress policer-override policer stat-mode

stat-mode

Syntax

stat-mode stat-mode

no stat-mode

Context

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

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

Full Context

configure service vpls sap egress policer-override policer stat-mode

configure service vpls sap ingress policer-override policer stat-mode

Description

The SAP-egress QoS policy’s policer stat-mode command is used to configure the forwarding plane counters that allow offered, output and discard accounting to occur for the policer. A policer has multiple types of offered packets (for example, soft in-profile and out-of-profile from ingress and hard in-profile and out-of-profile due to egress profile overrides) and each of these offered types is interacting with the policers metering and profiling functions resulting in colored output packets (green, yellow and red). Due to the potential large number of egress policers, it is not economical to allocate counters in the forwarding plane for all possible offered packet types and output conditions. Many policers will not be configured with a CIR profiling rate and not all policers will receive explicitly re-profiled offered packets. The stat-mode command allows provisioning of the number of counters each policer requires and how the offered packet types and output conditions should be mapped to the counters.

While a no-stats mode is supported which prevents any packet accounting, the use of the policer’s parent command requires that the policer’s stat-mode to be set at least to the minimal setting so that offered stats are available for the policer’s Fair Information Rate (FIR) to be calculated.

Each time the policer’s stat-mode is changed, any previous counter values are lost and any new counters are set to zero.

Each mode uses a certain number of counters per policer instance that are allocated from the forwarding plane’s policer counter resources. You can view the total/allocated/free stats by using the tools dump resource-usage card slot-num fp fp-number command. If insufficient counters exist to implement a mode on any policer instance, the stat-mode change will fail and the previous mode will continue unaffected for all instances of the policer.

The default stat-mode when a policer is created within the policy is minimal.

The stat-mode setting defined for the policer in the QoS policy may be overridden on a SAP where the policy is applied. If insufficient policer counter resources exist to implement the override, the stat-mode override command will fail. The previous stat-mode setting active for the policer will continue to be used by the policer.

The no form of the command returns the policer’s stat-mode setting to minimal.

Refer to the 7450 ESS, 7750 SR, 7950 XRS, and VSR Quality of Service Guide for detailed information about the policer stat-mode command parameters.

Platforms

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

stat-mode

Syntax

stat-mode stat-mode

no stat-mode

Context

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

[Tree] (config>service>ies>if>sap>ingress>policer-override>plcr stat-mode)

Full Context

configure service ies interface sap egress policer-override policer stat-mode

configure service ies interface sap ingress policer-override policer stat-mode

Description

The SAP-egress QoS policy’s policer stat-mode command is used to configure the forwarding plane counters that allow offered, output and discard accounting to occur for the policer. A policer has multiple types of offered packets (for example, soft in-profile and out-of-profile from ingress and hard in-profile and out-of-profile due to egress profile overrides) and each of these offered types is interacting with the policers metering and profiling functions resulting in colored output packets (green, yellow and red). Due to the potential large number of egress policers, it is not economical to allocate counters in the forwarding plane for all possible offered packet types and output conditions. Many policers will not be configured with a CIR profiling rate and not all policers will receive explicitly re-profiled offered packets. The stat-mode command allows provisioning of the number of counters each policer requires and how the offered packet types and output conditions should be mapped to the counters.

While a no-stats mode is supported which prevents any packet accounting, the use of the policer’s parent command requires that the policer’s stat-mode to be set at least to the minimal setting so that offered stats are available for the policer’s Fair Information Rate (FIR) to be calculated.

Each time the policer’s stat-mode is changed, any previous counter values are lost and any new counters are set to zero.

Each mode uses a certain number of counters per policer instance that are allocated from the forwarding plane’s policer counter resources. You can view the total/allocated/free stats by using the tools dump resource-usage card slot-num fp fp-number command. If insufficient counters exist to implement a mode on any policer instance, the stat-mode change will fail and the previous mode will continue unaffected for all instances of the policer.

The default stat-mode when a policer is created within the policy is minimal.

The stat-mode setting defined for the policer in the QoS policy may be overridden on a SAP where the policy is applied. If insufficient policer counter resources exist to implement the override, the stat-mode override command will fail. The previous stat-mode setting active for the policer will continue to be used by the policer.

The no form of this command returns the policer’s stat-mode setting to minimal.

Refer to the 7450 ESS, 7750 SR, 7950 XRS, and VSR Quality of Service Guide for detailed information about the policer stat-mode command parameters.

Platforms

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

stat-mode

Syntax

stat-mode stat-mode

no stat-mode

Context

[Tree] (config>service>vprn>if>sap>ingress>policer-override>plcr stat-mode)

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

Full Context

configure service vprn interface sap ingress policer-override policer stat-mode

configure service vprn interface sap egress policer-override policer stat-mode

Description

The SAP-egress QoS policy’s policer stat-mode command is used to configure the forwarding plane counters that allow offered, output and discard accounting to occur for the policer. A policer has multiple types of offered packets (for example, soft in-profile and out-of-profile from ingress and hard in-profile and out-of-profile due to egress profile overrides) and each of these offered types is interacting with the policers metering and profiling functions resulting in colored output packets (green, yellow and red). Due to the potential large number of egress policers, it is not economical to allocate counters in the forwarding plane for all possible offered packet types and output conditions. Many policers will not be configured with a CIR profiling rate and not all policers will receive explicitly re-profiled offered packets. The stat-mode command allows provisioning of the number of counters each policer requires and how the offered packet types and output conditions should be mapped to the counters.

While a no-stats mode is supported which prevents any packet accounting, the use of the policer’s parent command requires that the policer’s stat-mode to be set at least to the minimal setting so that offered stats are available for the policer’s Fair Information Rate (FIR) to be calculated.

Each time the policer’s stat-mode is changed, any previous counter values are lost and any new counters are set to zero.

Each mode uses a certain number of counters per policer instance that are allocated from the forwarding plane’s policer counter resources. You can view the total/allocated/free stats by using the tools dump resource-usage card slot-num fp fp-number command. If insufficient counters exist to implement a mode on any policer instance, the stat-mode change will fail and the previous mode will continue unaffected for all instances of the policer.

The default stat-mode when a policer is created within the policy is minimal.

The stat-mode setting defined for the policer in the QoS policy may be overridden on a SAP where the policy is applied. If insufficient policer counter resources exist to implement the override, the stat-mode override command will fail. The previous stat-mode setting active for the policer will continue to be used by the policer.

The no form of this command returns the policer’s stat-mode setting to minimal.

Refer to the 7450 ESS, 7750 SR, 7950 XRS, and VSR Quality of Service Guide for detailed information about the policer stat-mode command parameters.

Platforms

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

stat-mode

Syntax

stat-mode {no-stats | minimal | offered-profile-no-cir | offered-priority-no-cir | offered-profile-cir | offered-priority-cir | offered-total-cir | offered-limited-profile-cir | offered-profile-capped-cir | offered-limited-capped-cir}

no stat mode

Context

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

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

Full Context

configure qos sap-ingress policer stat-mode

configure qos sap-ingress dynamic-policer stat-mode

Description

This command is used to configure the forwarding plane counters that allow offered, forwarded, and dropped accounting to occur for the policer. An ingress policer has multiple types of offered packets (explicit in-profile, explicit out-of-profile, uncolored, high-priority, or low priority) and each of these offered types is interacting with the policer’s metering and profiling functions resulting in colored output packets (green, yellow, and red). Due to the large number of policers, it is not economical to allocate counters in the forwarding plane for all possible offered packet types and output conditions. Many policers, for example, will not be configured with a CIR profiling rate and not all policers will receive explicitly profiled offered packets. The stat-mode command allows provisioning of the number of counters each policer requires and how the offered packet types and output conditions should be mapped to the counters.

While a no-stats mode is supported that prevents any packet accounting, the use of the policer’s parent command requires that the policer's stat-mode be set at least to the minimal setting so that offered stats are available for the policer's Fair Information Rate (FIR) to be calculated. When a policer has been made a child to a parent policer, the stat-mode cannot be changed to no-stats unless the policer parenting is first removed.

Each time the policer’s stat-mode is changed, any previous counter values are lost and any new counters are set to zero.

Each mode uses a certain number of counters per policer instance that are allocated from the forwarding plane’s policer counter resources. The total/allocated/free stats can be viewed by using the tools dump resource-usage card fp command. If insufficient counters exist to implement a mode on any policer instance, the stat-mode change will fail and the previous mode will continue unaffected for all instances of the policer.

The ingress policer stat-modes are described in Ingress Policer Stat Mode Summary .

Table 6. Ingress Policer Stat Mode Summary

Stat Mode

Stat Resources

Traffic Counters (Packet/Octets)

Comments

Offered

Dropped/Forwarded

no-stats

0

Minimal

1

Single counter entering policer

Single counter for dropped/forwarded exiting policer

offered-profile-no-cir

2

In/out entering policer

In/out entering policer

Intended for when the policer does not change the profile of packets. Includes only in-profile and out-of-profile.

offered-priority-no-cir

2

High/low entering policer

High/low entering policer

Intended for when only packet priority stats are required.

offered-profile-cir

4

In/out/uncolored entering policer

In/out exiting policer

Intended for when the policer can change the profile of packets to in-profile and out-of-profile.

offered-priority-cir

4

High/low entering policer

In/out exiting policer

Intended for when packet priority entering the policer and profile exiting the policer is required.

offered-total-cir

2

Single counter entering policer

In/out exiting policer

offered-limited-profile-cir

3

Out/uncolored entering policer

In/out exiting policer

Intended for when the policer can change the profile of packet to in-profile and out-of-profile. The information is limited compared to offered-profile-capped-cir with the benefit of using one less stat resource.

offered-profile-capped-cir

5

In/out/uncolored entering policer

In/out exiting policer

Intended for when the policer has profile-capped configured.

offered-limited-capped-cir

4

In/uncolored entering policer

In/out exiting policer

Intended for when the policer has profile-capped configured. The information is limited compared to offered-profile-capped-cir with the benefit of using one less stat resource.

The default stat-mode when a policer is created within the policy is minimal.

The stat-mode setting defined for the policer in the QoS policy may be overridden on an sla-profile or SAP where the policy is applied. If insufficient policer counter resources exist to implement the override, the stat-mode override command will fail. The previous stat-mode setting active for the policer will continue to be used by the policer.

The no form of this command attempts to return the policer’s stat-mode setting to minimal. The command will fail if insufficient policer counter resources exist to implement minimal where the QoS policer is currently applied and has a forwarding class mapping.

Parameters

no-stats

Counter resource allocation: 0

The policer does not have any forwarding plane counters allocated and cannot provide offered, dropped, and forwarded statistics. A policer using no-stats cannot be a child to a parent policer and the policer’s parent command will fail.

When collect-stats is enabled, no statistics are generated.

minimal

Counter resource allocation: 1

This stat-mode provides the minimal accounting resource usage and counter information, and includes the total offered, dropped and forwarded packet and octet counters for traffic entering (offered) and exiting (dropped/forwarded) the policer.

The default stat-mode for a policer is minimal. The minimal mode allocates 1 forwarding plane offered counter and one traffic manager discard counter. The forwarding counter is derived by subtracting the discard counter from the offered counter. The counters do not differentiate possible offered types (profile or priority) and do not count in-profile or out-of-profile output. This does not prevent the policer from supporting different offered packet types and does not prevent the policer from supporting a CIR rate.

This counter mode is useful when only the most basic accounting information is required.

The counters displayed in the show output and those collected when collect-stats is enabled (the actual fields collected depends on the record configured in the applied accounting policy) are described in Ingress Accounting Statistics Collected in minimal stat-mode .

Table 7. Ingress Accounting Statistics Collected in minimal stat-mode

Show Output

Accounting Statistics Collected

Field

Field Description

Off. All

apo

AllPacketsOffered

aoo

AllOctetsOffered

Dro. All

apd

AllPacketsDropped

aod

AllOctetsDropped

For. All

apf

AllPacketsForwarded

aof

AllOctetsForwarded

offered-profile-no-cir

Counter resource allocation: 2

This stat-mode provides offered, dropped and forwarded packet and octet counters corresponding to the profile of traffic entering the policer.

The offered-profile-no-cir mode allocates two forwarding plane offered counters and two traffic manager discard counters.

The offered-profile-no-cir mode is most useful when the policer is receiving only in-profile and out-of-profile premarked (and trusted) packets. It is expected that, in this instance, a CIR rate will not be defined since all packets are already premarked. This mode does not prevent the policer from receiving untrusted (color undefined) traffic nor does it prevent the policer from being configured with a CIR rate.

This mode is intended to be used without profile-capped configured within the policer as it could cause the traffic profile to be modified by the policer.

The counters displayed in the show output and those collected when collect-stats is enabled (the actual fields collected depends on the record configured in the applied accounting policy) are described in Ingress Accounting Statistics Collected in offered-profile-no-cir stat-mode .

Table 8. Ingress Accounting Statistics Collected in offered-profile-no-cir stat-mode

Show Output

Accounting Statistics Collected

Field

Field Description

Off. InProf

ipo

InProfilePacketsOffered

ioo

InProfileOctetsOffered

Off. OutProf

opo

OutOfProfilePacketsOffered

ooo

OutOfProfileOctetsOffered

Dro. InProf

ipd

InProfilePacketsDropped

iod

InProfileOctetsDropped

Dro. OutProf

opd

OutOfProfilePacketsDropped

ood

OutOfProfileOctetsDropped

For. InProf

ipf

InProfilePacketsForwarded

iof

InProfileOctetsForwarded

For. OutProf

opf

OutOfProfilePacketsForwarded

oof

OutOfProfileOctetsForwarded

offered-priority-no-cir

Counter resource allocation: 2

This stat-mode provides offered, dropped and forwarded packet and octet counters corresponding to the packet priority of traffic entering the policer.

The offered-priority-no-cir mode allocates two forwarding plane offered counters and two traffic manager discard counters.

The offered-priority-no-cir mode is most useful when the policer is receiving only untrusted packets and the ingress priority high and priority low classification options are being used without a CIR profiling rate defined. This mode does not prevent the policer from receiving trusted packets that are premarked in-profile or out-of-profile nor does it prevent the policer from being configured with a CIR rate.

This mode is intended to be used without profile-capped configured within the policer as it could cause the traffic profile to be modified by the policer.

The counters displayed in the show output and those collected when collect-stats is enabled (the actual fields collected depends on the record configured in the applied accounting policy) are described in Ingress Accounting Statistics Collected in offered-priority-no-cir stat-mode .

Table 9. Ingress Accounting Statistics Collected in offered-priority-no-cir stat-mode

Show Output

Accounting Statistics Collected

Field

Field Description

Off. HiPrio

hpo

HighPriorityPacketsOffered

hoo

HighPriorityOctetsOffered

Off. LowPrio

lpo

LowPriorityPacketsOffered

loo

LowPriorityOctetsOffered

Dro. HiPrio

hpd

HighPriorityPacketsDropped

hod

HighPriorityOctetsDropped

Dro. LowPrio

lpd

LowPriorityPacketsDropped

lod

LowPriorityOctetsDropped

For. HiPrio

hpf

HighPriorityPacketsForwarded

hof

HighPriorityOctetsForwarded

For. LowPrio

lpf

LowPriorityPacketsForwarded

lof

LowPriorityOctetsForwarded

offered-profile-cir

Counter resource allocation: 4

This stat-mode provides offered, dropped and forwarded packet and octet counters corresponding to the profile of traffic entering (offered) and exiting (dropped/forwarded) the policer when ingress reclassification is performed so that the traffic entering the policer comprises hard in/out and uncolored traffic. The offered counters cover traffic explicitly profiled to in-profile, traffic explicitly profiled to out-of-profile, and traffic that has not been explicitly profiled at ingress (uncolored).

The offered-profile-cir mode allocates four forwarding plane offered counters and four traffic manager discard counters.

The offered-profile-cir mode is most useful when the policer is receiving trusted out-of-profile and in-profile traffic and is also receiving untrusted packets that are being applied to a defined CIR profiling rate. This mode differs from offered-limited-profile-cir mode in that it expects both trusted in-profile and out-of-profile packets while still performing CIR profiling on packets with untrusted markings. If trusted in-profile packets are not being received, the offered-limited-profile-cir stat-mode could be used instead, which has the benefit of using a reduced number of stat resources.

This mode is intended to be used without profile-capped configured within the policer as this could cause the traffic profile to be modified by the policer in a way that is not accounted for in the statistics.

The counters displayed in the show output and those collected when collect-stats is enabled (the actual fields collected depends on the record configured in the applied accounting policy) are described in Ingress Accounting Statistics Collected in offered-profile-cir stat-mode .

Table 10. Ingress Accounting Statistics Collected in offered-profile-cir stat-mode

Show Output

Accounting Stats Collected

Field

Field Description

Off. InProf

ipo

InProfilePacketsOffered

ioo

InProfileOctetsOffered

Off. OutProf

opo

OutOfProfilePacketsOffered

ooo

OutOfProfileOctetsOffered

Off. Uncolor

ucp

UncoloredPacketsOffered

uco

UncoloredOctetsOffered

Dro. InProf

ipd

InProfilePacketsDropped

iod

InProfileOctetsDropped

Dro. OutProf

opd

OutOfProfilePacketsDropped

ood

OutOfProfileOctetsDropped

For. InProf

ipf

InProfilePacketsForwarded

iof

InProfileOctetsForwarded

For. OutProf

opf

OutOfProfilePacketsForwarded

oof

OutOfProfileOctetsForwarded

offered-priority-cir

Counter resource allocation: 4

This stat-mode provides offered, dropped and forwarded packet and octet counters corresponding to the priority of traffic entering the policer and the profile exiting the policer.

The offered-priority-cir mode allocates four forwarding plane offered counters and four traffic manager discard counters.

The offered-priority-cir mode is most useful when the policer is receiving only untrusted packets that are being classified as high priority or low priority and are being applied to a defined CIR profiling rate. This mode differs from offered-profile-cir mode in that it does not expect trusted in-profile and out-of-profile packets but does not exclude the ability of the policer to receive them.

This mode is intended to be used without profile-capped configured within the policer as it could cause the traffic profile to be modified by the policer in a way that is not accounted for in the statistics.

The counters displayed in the show output and those collected when collect-stats is enabled (the actual fields collected depends on the record configured in the applied accounting policy) are described in Ingress Accounting Statistics Collected in offered-priority-cir stat-mode .

Table 11. Ingress Accounting Statistics Collected in offered-priority-cir stat-mode

Show Output

Accounting Stats Collected

Field

Field Description

Off. HiPrio

hpo

HighPriorityPacketsOffered

hoo

HighPriorityOctetsOffered

Off. LowPrio

lpo

LowPriorityPacketsOffered

loo

LowPriorityOctetsOffered

Dro. InProf

ipd

InProfilePacketsDropped

iod

InProfileOctetsDropped

Dro. OutProf

opd

OutOfProfilePacketsDropped

ood

OutOfProfileOctetsDropped

For. InProf

ipf

InProfilePacketsForwarded

iof

InProfileOctetsForwarded

For. OutProf

opf

OutOfProfilePacketsForwarded

oof

OutOfProfileOctetsForwarded

offered-total-cir

Counter resource allocation: 2

This stat-mode provides offered, dropped and forwarded packet and octet counters corresponding to the profile of traffic entering (offered) and exiting (dropped/forwarded) the policer. All offered traffic is provided in a single counter.

The offered-total-cir mode allocates two forwarding plane offered counters and two traffic manager discard counters.

The offered-total-cir mode is most useful when the policer is not receiving trusted in-profile or out-of-profile traffic and both high- and low-priority classifications are not being used on the untrusted packets and the offered packets are being applied to a defined CIR profiling rate. This mode does not prevent the policer from receiving trusted in-profile or out-of-profile packets and does not prevent the use of priority high or low classifications on the untrusted packets.

This mode is intended to be used without profile-capped configured within the policer as it could cause the traffic profile to be modified by the policer in a way that is not accounted for in the statistics.

The counters displayed in the show output and those collected when collect-stats is enabled (the actual fields collected depends on the record configured in the applied accounting policy) are described in Ingress Accounting Statistics Collected in offered-total-cir stat-mode .

Table 12. Ingress Accounting Statistics Collected in offered-total-cir stat-mode

Show Output

Accounting Stats Collected

Field

Field Description

Off. All

apo

AllPacketsOffered

aoo

AllOctetsOffered

Dro. InProf

ipd

InProfilePacketsDropped

iod

InProfileOctetsDropped

Dro. OutProf

opd

OutOfProfilePacketsDropped

ood

OutOfProfileOctetsDropped

For. InProf

ipf

InProfilePacketsForwarded

iof

InProfileOctetsForwarded

For. OutProf

opf

OutOfProfilePacketsForwarded

oof

OutOfProfileOctetsForwarded

offered-limited-profile-cir

Counter resource allocation: 3

This stat-mode provides offered, dropped and forwarded packet and octet counters corresponding to the profile of traffic entering (offered) and exiting (dropped/forwarded) the policer when ingress reclassification is performed so that the traffic entering the policer comprises of hard out and uncolored. The offered counters cover traffic explicitly profiled to out-of-profile and traffic that has not been explicitly profiled at ingress (Uncolor). The traffic explicitly profiled to in-profile is counted with the uncolored traffic.

The offered-limited-profile-cir mode allocates three forwarding plane offered counters and three traffic manager discard counters.

The offered-limited-profile-cir mode is most useful when the policer is receiving trusted out-of-profile (profile out but no profile in) traffic and untrusted packets are being applied to a defined CIR profiling rate. This mode does not prevent the policer from receiving trusted in-profile packets. If trusted in-profile packets are not being received, the offered-limited-profile-cir is preferred over offered-profile-cir because it uses a reduced number of stat resources.

This mode is intended to be used without profile-capped configured within the policer as it could cause the traffic profile to be modified by the policer in a way that is not accounted for in the statistics.

The counters displayed in the show output and those collected when collect-stats is enabled (the actual fields collected depends on the record configured in the applied accounting policy) are described in Ingress Accounting Statistics Collected in offered-limited-profile-cir stat-mode .

Table 13. Ingress Accounting Statistics Collected in offered-limited-profile-cir stat-mode

Show Output

Accounting Stats Collected

Field

Field Description

Off. OutProf

opo

OutOfProfilePacketsOffered

ooo

OutOfProfileOctetsOffered

Off. Uncolor

ucp

UncoloredPacketsOffered

uco

UncoloredOctetsOffered

Dro. InProf

ipd

InProfilePacketsDropped

iod

InProfileOctetsDropped

Dro. OutProf

opd

OutOfProfilePacketsDropped

ood

OutOfProfileOctetsDropped

For. InProf

ipf

InProfilePacketsForwarded

iof

InProfileOctetsForwarded

For. OutProf

opf

OutOfProfilePacketsForwarded

oof

OutOfProfileOctetsForwarded

offered-profile-cir

Counter resource allocation: 4

offered-profile-capped-cir

Counter resource allocation: 5

This stat-mode provides offered, dropped and forwarded packet and octet counters corresponding to the profile of traffic entering (offered) and exiting (dropped/forwarded) the policer when ingress reclassification is performed so that the traffic entering the policer comprises of hard in/out and uncolored. The offered counters cover traffic explicitly profiled to in-profile, traffic explicitly profiled to out-of-profile, and traffic that has not been explicitly profiled at ingress (Uncolor).

When offered-profile-capped-cir is defined, the system creates five offered-output counters in the forwarding plane and five discard counters in the traffic manager.

The offered-profile-capped-cir mode is similar to the offered-profile-cir mode except that it includes support for profile in and soft-in-profile that may be output as out-of-profile due to enabling profile-capped mode on the ingress policer.

The impact of using offered-profile-capped-cir stat-mode while profile-capped mode is disabled is that one of the counting resources in the forwarding plane and traffic manager will not be used.

The counters displayed in the show output and those collected when collect-stats is enabled (the actual fields collected depends on the record configured in the applied accounting policy) are described in Ingress Accounting Statistics Collected in offered-profile-capped-cir stat-mode .

Table 14. Ingress Accounting Statistics Collected in offered-profile-capped-cir stat-mode

Show Output

Accounting Stats Collected

Field

Field Description

Off. InProf

ipo

InProfilePacketsOffered

ioo

InProfileOctetsOffered

Off. OutProf

opo

OutOfProfilePacketsOffered

ooo

OutOfProfileOctetsOffered

Off. Uncolor

ucp

UncoloredPacketsOffered

uco

UncoloredOctetsOffered

Dro. InProf

ipd

InProfilePacketsDropped

iod

InProfileOctetsDropped

Dro. OutProf

opd

OutOfProfilePacketsDropped

ood

OutOfProfileOctetsDropped

For. InProf

ipf

InProfilePacketsForwarded

iof

InProfileOctetsForwarded

For. OutProf

opf

OutOfProfilePacketsForwarded

oof

OutOfProfileOctetsForwarded

offered-limited-capped-cir

Counter resource allocation: 4

This stat-mode provides offered, dropped and forwarded packet and octet counters corresponding to the profile of traffic entering (offered) and exiting (dropped/forwarded) the policer when ingress reclassification is performed resulting in the traffic entering the policer comprising of hard in/out and uncolored. The offered counters cover in-profile traffic and traffic that has not been explicitly profiled at ingress (Uncolor). The traffic explicitly profiled to out-of-profile is counted with the uncolored traffic.

When offered-limited-capped-cir is defined, the system creates four forwarding plane offered-output counters in the network processor and four discard counters in the traffic manager.

The offered-limited-capped-cir mode is similar to the offered-profile-capped-cir mode except that it combines soft in-profile with profile in (InProf) and profile out (OutProf) with soft-out-of-profile (Uncolor) and eliminates the "offered undefined” statistic. If trusted out-of-profile packets are not being received, the offered-limited-capped-cir is preferred over offered-profile-capped-cir because it uses a reduced number of stat resources.

This mode is intended to be used with profile-capped configured within the policer.

The impact of using offered-limited-capped-cir stat-mode while profile-capped mode is disabled is that one of the counting resources in the forwarding plane and traffic manager will not be used.

The counters displayed in the show output and those collected when collect-stats is enabled (the actual fields collected depends on the record configured in the applied accounting policy) are described in Ingress Accounting Statistics Collected in offered-limited-capped-cir stat-mode .

Table 15. Ingress Accounting Statistics Collected in offered-limited-capped-cir stat-mode

Show Output

Accounting Stats Collected

Field

Field Description

Off. InProf

ipo

InProfilePacketsOffered

ioo

InProfileOctetsOffered

Off. Uncolor

ucp

UncoloredPacketsOffered

uco

UncoloredOctetsOffered

Dro. InProf

ipd

InProfilePacketsDropped

iod

InProfileOctetsDropped

Dro. OutProf

opd

OutOfProfilePacketsDropped

ood

OutOfProfileOctetsDropped

For. InProf

ipf

InProfilePacketsForwarded

iof

InProfileOctetsForwarded

For. OutProf

opf

OutOfProfilePacketsForwarded

oof

OutOfProfileOctetsForwarded

Platforms

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

  • configure qos sap-ingress policer stat-mode

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

  • configure qos sap-ingress dynamic-policer stat-mode

stat-mode

Syntax

stat-mode {no-stats | minimal | offered-profile-no-cir | offered-profile-cir | offered-total-cir | offered-limited-capped-cir | offered-profile-capped-cir}

no stat mode

Context

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

Full Context

configure qos sap-egress dynamic-policer stat-mode

Description

The sap-egress QoS policy's policer stat-mode command is used to configure the forwarding plane counters that allow offered, forwarded, and dropped accounting to occur for the policer. An egress policer has multiple types of offered packets (soft in-profile and out-of-profile from ingress and hard in-profile, out-of-profile, and exceed-profile due to egress profile overrides) and each of these offered types is interacting with the policer’s metering and profiling functions resulting in colored output packets (green, yellow, and red). Due to the potential large number of egress policers, it is not economical to allocate counters in the forwarding plane for all possible offered packet types and output conditions. Many policers, for example, will not be configured with a CIR profiling rate and not all policers will receive explicitly reprofiled offered packets. The stat-mode command allows provisioning of the number of counters each policer requires and how the offered packet types and output conditions should be mapped to the counters.

While a no-stats mode is supported that prevents any packet accounting, the use of the policer's parent command requires that the policer’s stat-mode be set at least to the minimal setting so that offered stats are available for the policer’s Fair Information Rate (FIR) to be calculated. When a policer has been made a child to a parent policer, the stat-mode cannot be changed to no-stats unless the policer parenting is first removed.

Each time the policer's stat-mode is changed, any previous counter values are lost and any new counters are set to zero.

Each mode uses a certain number of counters per policer instance that are allocated from the forwarding plane's policer counter resources. The total, allocated, and free statistics can be viewed by using the tools dump resource-usage card fp command. If insufficient counters exist to implement a mode on any policer instance, the stat-mode change will fail and the previous mode will continue unaffected for all instances of the policer.

The egress policer stat-modes are described in Egress Policer Stat-mode Summary.

Table 16. Egress Policer Stat-mode Summary

Stat Mode

Stat Resources

Traffic Counters (Packet/Octets)

Comments

Offered

Dropped/Forwarded

no-stats

0

minimal

1

Single counter entering policer

Single counter for dropped/forwarded exiting policer

offered-profile-no-cir

2

In or out entering policer

In/out entering policer

Intended for when the policer does not change the profile of packets. Includes only in-profile and out-of-profile.

offered-profile-cir

4

In, out, or uncolored (which corresponds to hard in-profile, hard out-of-profile, or soft in- or out-of-profile) entering policer

In/out exiting policer

Intended for when the policer can change the profile of packets to in-profile and out-of-profile.

offered-total-cir

2

Single counter entering policer

In/out exiting policer

offered-limited-capped-cir

4

In or out entering policer

In/out exiting policer

Intended for when the policer has profile-capped configured. The information is limited compared to offered-profile-capped-cir with the benefit of using one less stat resource.

offered-profile-capped-cir

5

In, out, or uncolored (which corresponds to hard in-profile, hard out-of-profile, or soft in- or out-of-profile) entering policer

In/out exiting policer

Intended for when the policer has profile-capped configured

When a policer is created within the policy, the default setting for stat-mode is minimal.

The stat-mode setting defined for the policer in the QoS policy may be overridden on an sla-profile or SAP where the policy is applied. If insufficient policer counter resources exist to implement the override, the stat-mode override command will fail. The previous stat-mode setting active for the policer will continue to be used by the policer.

The no form of this command attempts to return the policer’s stat-mode setting to minimal. The command will fail if insufficient policer counter resources exist to implement minimal where the QoS policer is currently applied and has a forwarding class mapping.

Parameters

no-stats

Counter resource allocation: 0

The policer does not have any forwarding plane counters allocated and cannot provide offered, discard, and forward statistics. A policer using no-stats cannot be a child to a parent policer and the policer’s parent command will fail.

When collect-stats is enabled, no statistics are generated.

minimal

Counter resource allocation: 1

This stat-mode provides the minimal accounting resource usage and counter information, and includes only the total offered, dropped and forwarded packet and octet counters for traffic entering (offered) and exiting (dropped/forwarded) the policer.

The default stat-mode for a policer is minimal. The minimal mode allocates 1 forwarding plane offered counter and one traffic manager discard counter. The forwarding counter is derived by subtracting the discard counter from the offered counter. The counters do not differentiate possible offered types and do not count different profile output. This does not prevent the policer from supporting different offered packet types and does not prevent the policer from supporting a CIR rate or using exceed PIR.

The counters displayed in the show output and those collected when collect-stats is enabled (the actual fields collected depends on the record configured in the applied accounting policy) are described in Egress Accounting Statistics Collected in minimal stat-mode .

Table 17. Egress Accounting Statistics Collected in minimal stat-mode

Show Output

Accounting Stats Collected

Field

Field Description

Off. All

apo

AllPacketsOffered

aoo

AllOctetsOffered

Dro. All

apd

AllPacketsDropped

aod

AllOctetsDropped

For. All

apf

AllPacketsForwarded

aof

AllOctetsForwarded

offered-profile-no-cir

Counter resource allocation: 2

This stat-mode provides offered, dropped, and forwarded packet and octet counters corresponding to the profile of traffic entering the policer. inplus-profile traffic is counted with the in-profile counters and exceed-profile traffic is counted with the out-of-profile counters.

The offered-profile-no-cir mode allocates two forwarding plane offered counters and two traffic manager discard counters.

The offered-profile-no-cir mode is most useful when profile-based offered, dropped, and forwarded stats are required from the egress policer, but a CIR or enable-exceed-pir is not being used to recolor the soft in-profile and out-of-profile packets. This mode does not prevent the policer from being configured with a CIR rate or using enable-exceed-pir.

This mode is intended to be used without profile-capped configured within the policer as it could cause the traffic profile to be modified by the policer.

The counters displayed in the show output and those collected when collect-stats is enabled (the actual fields collected depends on the record configured in the applied accounting policy) are described in Egress Accounting Statistics Collected in offered-profile-no-cir stat-mode .

Table 18. Egress Accounting Statistics Collected in offered-profile-no-cir stat-mode

Show Output

Accounting Stats Collected

Field

Field Description

Off. InProf

ipo

InProfilePacketsOffered

ioo

InProfileOctetsOffered

Off. OutProf

opo

OutOfProfilePacketsOffered

ooo

OutOfProfileOctetsOffered

Dro. InProf

ipd

InProfilePacketsDropped

iod

InProfileOctetsDropped

Dro. OutProf

opd

OutOfProfilePacketsDropped

ood

OutOfProfileOctetsDropped

For. InProf

ipf

InProfilePacketsForwarded

iof

InProfileOctetsForwarded

For. OutProf

opf

OutOfProfilePacketsForwarded

oof

OutOfProfileOctetsForwarded

offered-profile-cir

Counter resource allocation: 4

This stat-mode provides offered, dropped, and forwarded packet and octet counters corresponding to the profile of traffic entering (offered) and exiting (dropped/forwarded) the policer when egress reclassification is performed so that the traffic entering the policer is made up of traffic that is inplus-profile, in-profile, out-of-profile, exceed-profile, soft in-profile, and soft out-of-profile. The offered counters cover traffic reclassified to in-profile (which includes traffic reclassified to inplus-profile), traffic reclassified to out-of-profile (which includes traffic reclassified to exceed-profile) and traffic which has not been reclassified at egress (Uncolor). In the dropped and forwarded counters, inplus-profile traffic is counted with the in-profile counter and exceed-profile traffic is counted with the out-of-profile counter.

The offered-profile-cir mode allocates four forwarding plane offered counters and four traffic manager discard counters.

The offered-profile-cir mode is most useful when profile-based offered, dropped and forwarded stats are required from the egress policer and a CIR rate is being used to recolor the soft in-profile and out-of-profile packets.

This mode is intended to be used without profile-capped or enable-exceed-pir configured within the policer as these could cause the traffic profile to be modified by the policer in a way that is not accounted for in the statistics.

The counters displayed in the show output and those collected when collect-stats is enabled (the actual fields collected depends on the record configured in the applied accounting policy) are described in Egress Accounting Statistics Collected in offered-profile-cir stat-mode .

Table 19. Egress Accounting Statistics Collected in offered-profile-cir stat-mode

Show Output

Accounting Stats Collected

Field

Field Description

Off. InProf

ipo

InProfilePacketsOffered

ioo

InProfileOctetsOffered

Off. OutProf

opo

OutOfProfilePacketsOffered

ooo

OutOfProfileOctetsOffered

Off. Uncolor

ucp

UncoloredPacketsOffered

uco

UncoloredOctetsOffered

Dro. InProf

ipd

InProfilePacketsDropped

iod

InProfileOctetsDropped

Dro. OutProf

opd

OutOfProfilePacketsDropped

ood

OutOfProfileOctetsDropped

For. InProf

ipf

InProfilePacketsForwarded

iof

InProfileOctetsForwarded

For. OutProf

opf

OutOfProfilePacketsForwarded

oof

OutOfProfileOctetsForwarded

offered-total-cir

Counter resource allocation: 2

This stat-mode provides offered, dropped, and forwarded packet and octet counters corresponding to the profile of traffic entering (offered) and exiting (dropped/forwarded) the policer. All offered traffic is provided in a single counter. In the dropped and forwarded counters, inplus-profile traffic is counted with the in-profile counter and exceed-profile traffic is counted with the out-of-profile counter.

The offered-total-cir mode allocates two forwarding plane offered counters and two traffic manager discard counters.

The offered-total-cir mode is most useful when the policer is not receiving trusted in-profile or out-of-profile traffic, and both high- and low- priority classifications are not being used on the untrusted packets, and the offered packets are being applied to a defined CIR profiling rate. This mode does not prevent the policer from receiving trusted in-profile or out-of-profile packets and does not prevent the use of priority high or low classifications on the untrusted packets.

This mode is intended to be used without profile-capped or enable-exceed-pir configured within the policer as these could cause the traffic profile to be modified by the policer in a way that is not accounted for in the statistics.

The counters displayed in the show output and those collected when collect-stats is enabled (the actual fields collected depends on the record configured in the applied accounting policy) are described in Egress Accounting Statistics Collected in offered-total-cir stat-mode .

Table 20. Egress Accounting Statistics Collected in offered-total-cir stat-mode

Show Output

Accounting Stats Collected

Field

Field Description

Off. All

apo

AllPacketsOffered

aoo

AllOctetsOffered

Dro. InProf

ipd

InProfilePacketsDropped

iod

InProfileOctetsDropped

Dro. OutProf

opd

OutOfProfilePacketsDropped

ood

OutOfProfileOctetsDropped

For. InProf

ipf

InProfilePacketsForwarded

iof

InProfileOctetsForwarded

For. OutProf

opf

OutOfProfilePacketsForwarded

oof

OutOfProfileOctetsForwarded

offered-limited-capped-cir

Counter resource allocation: 4

This stat-mode provides offered, dropped and forwarded packet and octet counters corresponding to the profile of traffic entering (offered) and exiting (dropped/forwarded) the policer when egress reclassification is performed so that the traffic entering the policer is made up of traffic that is inplus-profile, in-profile, out-of-profile, exceed-profile, soft in-profile, and soft out-of-profile. The offered counters cover in-profile traffic (which includes traffic reclassified to inplus-profile) and out-of-profile traffic (which includes traffic reclassified to exceed-profile). In the dropped and forwarded counters, inplus-profile traffic is counted with the in-profile counter and exceed-profile traffic is counted with the out-of-profile counter.

offered-limited-capped-cir is defined, the system creates four forwarding plane offered-output counters in the network processor and three discard counters in the traffic manager.

The offered-limited-capped-cir mode is similar to the offered-profile-capped-cir mode except that it combines soft in-profile with profile in and soft-out-of-profile with profile out and eliminates the offered-undefined statistic.

The impact of using offered-limited-capped-cir stat-mode while profile-capped mode is disabled is that one of the counting resources in the forwarding plane and traffic manager will not be used and soft-in-profile will be treated as offered-in instead of offered-undefined.

This mode is intended to be used with profile-capped configured within the policer but without enable-exceed-pir configured as this could cause the traffic profile to be modified by the policer in a way that is not accounted for in the statistics.

The counters displayed in the show output and those collected when collect-stats is enabled (the actual fields collected depends on the record configured in the applied accounting policy) are described in Egress Accounting Statistics Collected in offered-limited-capped-cir stat-mode .

Table 21. Egress Accounting Statistics Collected in offered-limited-capped-cir stat-mode

Show Output

Accounting Stats Collected

Field

Field Description

Off. InProf

ipo

InProfilePacketsOffered

ioo

InProfileOctetsOffered

Off. OutProf

opo

OutOfProfilePacketsOffered

ooo

OutOfProfileOctetsOffered

Dro. InProf

ipd

InProfilePacketsDropped

iod

InProfileOctetsDropped

Dro. OutProf

opd

OutOfProfilePacketsDropped

ood

OutOfProfileOctetsDropped

For. InProf

ipf

InProfilePacketsForwarded

iof

InProfileOctetsForwarded

For. OutProf

opf

OutOfProfilePacketsForwarded

oof

OutOfProfileOctetsForwarded

offered-profile-capped-cir

Counter resource allocation: 5

This stat-mode provides offered, dropped, and forwarded packet and octet counters corresponding to the profile of traffic entering (offered) and exiting (dropped/forwarded) the policer when egress reclassification is performed so that the traffic entering the policer is made up of traffic that is inplus-profile, in-profile, out-of-profile, exceed-profile, soft in-profile, and soft out-of-profile. The offered counters cover traffic reclassified to in-profile (which includes traffic reclassified to inplus-profile), traffic reclassified to out-of-profile (which includes traffic reclassified to exceed-profile) and traffic that has not been reclassified at egress (uncolored). In the dropped and forwarded counters, inplus-profile traffic is counted with the in-profile counter and exceed-profile traffic is counted with the out-of-profile counter.

When offered-profile-capped-cir is defined, the system creates five offered-output counters in the forwarding plane and five discard counters in the traffic manager.

The offered-profile-capped-cir mode is similar to the offered-profile-cir mode except that it includes support for profile inplus, profile in and soft-in-profile that may be output as out-of-profile due to enabling profile-capped mode on the ingress policer.

The impact of using offered-profile-capped-cir stat-mode while profile-capped mode is disabled is that one of the counting resources in the forwarding plane and traffic manager will not be used and soft-in-profile will be treated as offered-in (hard in-profile) instead of offered-undefined (uncolored).

This mode is intended to be used with profile-capped configured within the policer but without enable-exceed-pir configured as this could cause the traffic profile to be modified by the policer in a way that is not accounted for in the statistics.

The counters displayed in the show output and those collected when collect-stats is enabled (the actual fields collected depends on the record configured in the applied accounting policy) are described in Egress Accounting Statistics Collected in offered-profile-capped-cir stat-mode .

Table 22. Egress Accounting Statistics Collected in offered-profile-capped-cir stat-mode

Show Output

Accounting Stats Collected

Field

Field Description

Off. InProf

ipo

InProfilePacketsOffered

ioo

InProfileOctetsOffered

Off. OutProf

opo

OutOfProfilePacketsOffered

ooo

OutOfProfileOctetsOffered

Off. Uncolor

ucp

UncoloredPacketsOffered

uco

UncoloredOctetsOffered

Dro. InProf

ipd

InProfilePacketsDropped

iod

InProfileOctetsDropped

Dro. OutProf

opd

OutOfProfilePacketsDropped

ood

OutOfProfileOctetsDropped

For. InProf

ipf

InProfilePacketsForwarded

iof

InProfileOctetsForwarded

For. OutProf

opf

OutOfProfilePacketsForwarded

oof

OutOfProfileOctetsForwarded

Platforms

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

stat-mode

Syntax

stat-mode {no-stats | minimal | offered-profile-no-cir | offered-profile-cir | offered-total-cir | offered-limited-capped-cir | offered-profile-capped-cir | offered-total-cir-exceed | offered-four-profile-no-cir | offered-total-cir-four-profile}

no stat mode

Context

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

Full Context

configure qos sap-egress policer stat-mode

Description

The sap-egress QoS policy's policer stat-mode command is used to configure the forwarding plane counters that allow offered, forwarded, and dropped accounting to occur for the policer. An egress policer has multiple types of offered packets (soft in-profile and out-of-profile from ingress and hard in-profile, out-of-profile, and exceed-profile due to egress profile overrides) and each of these offered types is interacting with the policer’s metering and profiling functions resulting in colored output packets (green, yellow, and red). Due to the potential large number of egress policers, it is not economical to allocate counters in the forwarding plane for all possible offered packet types and output conditions. Many policers, for example, will not be configured with a CIR profiling rate and not all policers will receive explicitly reprofiled offered packets. The stat-mode command allows provisioning of the number of counters each policer requires and how the offered packet types and output conditions should be mapped to the counters.

While a no-stats mode is supported that prevents any packet accounting, the use of the policer's parent command requires that the policer’s stat-mode be set at least to the minimal setting so that offered stats are available for the policer’s Fair Information Rate (FIR) to be calculated. When a policer has been made a child to a parent policer, the stat-mode cannot be changed to no-stats unless the policer parenting is first removed.

Each time the policer's stat-mode is changed, any previous counter values are lost and any new counters are set to zero.

Each mode uses a certain number of counters per policer instance that are allocated from the forwarding plane's policer counter resources. The total, allocated, and free statistics can be viewed by using the tools dump resource-usage card fp command. If insufficient counters exist to implement a mode on any policer instance, the stat-mode change will fail and the previous mode will continue unaffected for all instances of the policer.

The egress policer stat-modes are described in Egress Policer Stat-mode Summary.

Table 23. Egress Policer Stat-mode Summary

Stat Mode

Stat Resources

Traffic Counters (Packet/Octets)

Comments

Offered

Dropped/Forwarded

no-stats

0

minimal

1

Single counter entering policer

Single counter for dropped/forwarded exiting policer

offered-profile-no-cir

2

In or out entering policer

In/out entering policer

Intended for when the policer does not change the profile of packets. Includes only in-profile and out-of-profile.

offered-profile-cir

4

In, out, or uncolored (which corresponds to hard in-profile, hard out-of-profile, or soft in- or out-of-profile) entering policer

In/out exiting policer

Intended for when the policer can change the profile of packets to in-profile and out-of-profile.

offered-total-cir

2

Single counter entering policer

In/out exiting policer

offered-limited-capped-cir

4

In or out entering policer

In/out exiting policer

Intended for when the policer has profile-capped configured. The information is limited compared to offered-profile-capped-cir with the benefit of using one less stat resource.

offered-profile-capped-cir

5

In, out, or uncolored (which corresponds to hard in-profile, hard out-of-profile, or soft in- or out-of-profile) entering policer

In/out exiting policer

Intended for when the policer has profile-capped configured

offered-total-cir-exceed

3

Single counter entering policer

In/out/exceed exiting policer

Intended for when the policer is configured with enable-exceed-pir to forward packets that exceed its configured PIR or when traffic is reclassified at egress to exceed-profile

offered-four-profile-no-cir

4

Inplus, in, out, or exceed entering policer

Inplus/in/out/exceed entering policer

Intended to be used when the policer does not change the profile of the packets and traffic is reclassified at egress to inplus and/or exceed-profile

offered-total-cir-four-profile

4

Single counter entering policer

Inplus, in, out, or exceed exiting policer

Intended to be used when the policer can change the profile of the packet and traffic is reclassified at egress to profile inplus

When a policer is created within the policy, the default setting for stat-mode is minimal.

The stat-mode setting defined for the policer in the QoS policy may be overridden on an sla-profile or SAP where the policy is applied. If insufficient policer counter resources exist to implement the override, the stat-mode override command will fail. The previous stat-mode setting active for the policer will continue to be used by the policer.

The no form of this command attempts to return the policer’s stat-mode setting to minimal. The command will fail if insufficient policer counter resources exist to implement minimal where the QoS policer is currently applied and has a forwarding class mapping.

Parameters

no-stats

Counter resource allocation: 0

The policer does not have any forwarding plane counters allocated and cannot provide offered, discard, and forward statistics. A policer using no-stats cannot be a child to a parent policer and the policer’s parent command will fail.

When collect-stats is enabled, no statistics are generated.

minimal

Counter resource allocation: 1

This stat-mode provides the minimal accounting resource usage and counter information, and includes only the total offered, dropped and forwarded packet and octet counters for traffic entering (offered) and exiting (dropped/forwarded) the policer.

The default stat-mode for a policer is minimal. The minimal mode allocates 1 forwarding plane offered counter and one traffic manager discard counter. The forwarding counter is derived by subtracting the discard counter from the offered counter. The counters do not differentiate possible offered types and do not count different profile output. This does not prevent the policer from supporting different offered packet types and does not prevent the policer from supporting a CIR rate or using exceed PIR.

The counters displayed in the show output and those collected when collect-stats is enabled (the actual fields collected depends on the record configured in the applied accounting policy) are described in Egress Accounting Statistics Collected in minimal stat-mode .

Table 24. Egress Accounting Statistics Collected in minimal stat-mode

Show Output

Accounting Stats Collected

Field

Field Description

Off. All

apo

AllPacketsOffered

aoo

AllOctetsOffered

Dro. All

apd

AllPacketsDropped

aod

AllOctetsDropped

For. All

apf

AllPacketsForwarded

aof

AllOctetsForwarded

offered-profile-no-cir

Counter resource allocation: 2

This stat-mode provides offered, dropped, and forwarded packet and octet counters corresponding to the profile of traffic entering the policer. inplus-profile traffic is counted with the in-profile counters and exceed-profile traffic is counted with the out-of-profile counters.

The offered-profile-no-cir mode allocates two forwarding plane offered counters and two traffic manager discard counters.

The offered-profile-no-cir mode is most useful when profile-based offered, dropped, and forwarded stats are required from the egress policer, but a CIR or enable-exceed-pir is not being used to recolor the soft in-profile and out-of-profile packets. This mode does not prevent the policer from being configured with a CIR rate or using enable-exceed-pir.

This mode is intended to be used without profile-capped configured within the policer as it could cause the traffic profile to be modified by the policer.

The counters displayed in the show output and those collected when collect-stats is enabled (the actual fields collected depends on the record configured in the applied accounting policy) are described in Egress Accounting Statistics Collected in offered-profile-no-cir stat-mode .

Table 25. Egress Accounting Statistics Collected in offered-profile-no-cir stat-mode

Show Output

Accounting Stats Collected

Field

Field Description

Off. InProf

ipo

InProfilePacketsOffered

ioo

InProfileOctetsOffered

Off. OutProf

opo

OutOfProfilePacketsOffered

ooo

OutOfProfileOctetsOffered

Dro. InProf

ipd

InProfilePacketsDropped

iod

InProfileOctetsDropped

Dro. OutProf

opd

OutOfProfilePacketsDropped

ood

OutOfProfileOctetsDropped

For. InProf

ipf

InProfilePacketsForwarded

iof

InProfileOctetsForwarded

For. OutProf

opf

OutOfProfilePacketsForwarded

oof

OutOfProfileOctetsForwarded

offered-profile-cir

Counter resource allocation: 4

This stat-mode provides offered, dropped, and forwarded packet and octet counters corresponding to the profile of traffic entering (offered) and exiting (dropped/forwarded) the policer when egress reclassification is performed so that the traffic entering the policer is made up of traffic that is inplus-profile, in-profile, out-of-profile, exceed-profile, soft in-profile, and soft out-of-profile. The offered counters cover traffic reclassified to in-profile (which includes traffic reclassified to inplus-profile), traffic reclassified to out-of-profile (which includes traffic reclassified to exceed-profile) and traffic which has not been reclassified at egress (Uncolor). In the dropped and forwarded counters, inplus-profile traffic is counted with the in-profile counter and exceed-profile traffic is counted with the out-of-profile counter.

The offered-profile-cir mode allocates four forwarding plane offered counters and four traffic manager discard counters.

The offered-profile-cir mode is most useful when profile-based offered, dropped and forwarded stats are required from the egress policer and a CIR rate is being used to recolor the soft in-profile and out-of-profile packets.

This mode is intended to be used without profile-capped or enable-exceed-pir configured within the policer as these could cause the traffic profile to be modified by the policer in a way that is not accounted for in the statistics.

The counters displayed in the show output and those collected when collect-stats is enabled (the actual fields collected depends on the record configured in the applied accounting policy) are described in Egress Accounting Statistics Collected in offered-profile-cir stat-mode .

Table 26. Egress Accounting Statistics Collected in offered-profile-cir stat-mode

Show Output

Accounting Stats Collected

Field

Field Description

Off. InProf

ipo

InProfilePacketsOffered

ioo

InProfileOctetsOffered

Off. OutProf

opo

OutOfProfilePacketsOffered

ooo

OutOfProfileOctetsOffered

Off. Uncolor

ucp

UncoloredPacketsOffered

uco

UncoloredOctetsOffered

Dro. InProf

ipd

InProfilePacketsDropped

iod

InProfileOctetsDropped

Dro. OutProf

opd

OutOfProfilePacketsDropped

ood

OutOfProfileOctetsDropped

For. InProf

ipf

InProfilePacketsForwarded

iof

InProfileOctetsForwarded

For. OutProf

opf

OutOfProfilePacketsForwarded

oof

OutOfProfileOctetsForwarded

offered-total-cir

Counter resource allocation: 2

This stat-mode provides offered, dropped, and forwarded packet and octet counters corresponding to the profile of traffic entering (offered) and exiting (dropped/forwarded) the policer. All offered traffic is provided in a single counter. In the dropped and forwarded counters, inplus-profile traffic is counted with the in-profile counter and exceed-profile traffic is counted with the out-of-profile counter.

The offered-total-cir mode allocates two forwarding plane offered counters and two traffic manager discard counters.

The offered-total-cir mode is most useful when the policer is not receiving trusted in-profile or out-of-profile traffic, and both high- and low- priority classifications are not being used on the untrusted packets, and the offered packets are being applied to a defined CIR profiling rate. This mode does not prevent the policer from receiving trusted in-profile or out-of-profile packets and does not prevent the use of priority high or low classifications on the untrusted packets.

This mode is intended to be used without profile-capped or enable-exceed-pir configured within the policer as these could cause the traffic profile to be modified by the policer in a way that is not accounted for in the statistics.

The counters displayed in the show output and those collected when collect-stats is enabled (the actual fields collected depends on the record configured in the applied accounting policy) are described in Egress Accounting Statistics Collected in offered-total-cir stat-mode .

Table 27. Egress Accounting Statistics Collected in offered-total-cir stat-mode

Show Output

Accounting Stats Collected

Field

Field Description

Off. All

apo

AllPacketsOffered

aoo

AllOctetsOffered

Dro. InProf

ipd

InProfilePacketsDropped

iod

InProfileOctetsDropped

Dro. OutProf

opd

OutOfProfilePacketsDropped

ood

OutOfProfileOctetsDropped

For. InProf

ipf

InProfilePacketsForwarded

iof

InProfileOctetsForwarded

For. OutProf

opf

OutOfProfilePacketsForwarded

oof

OutOfProfileOctetsForwarded

offered-limited-capped-cir

Counter resource allocation: 4

This stat-mode provides offered, dropped and forwarded packet and octet counters corresponding to the profile of traffic entering (offered) and exiting (dropped/forwarded) the policer when egress reclassification is performed so that the traffic entering the policer is made up of traffic that is inplus-profile, in-profile, out-of-profile, exceed-profile, soft in-profile, and soft out-of-profile. The offered counters cover in-profile traffic (which includes traffic reclassified to inplus-profile) and out-of-profile traffic (which includes traffic reclassified to exceed-profile). In the dropped and forwarded counters, inplus-profile traffic is counted with the in-profile counter and exceed-profile traffic is counted with the out-of-profile counter.

offered-limited-capped-cir is defined, the system creates four forwarding plane offered-output counters in the network processor and three discard counters in the traffic manager.

The offered-limited-capped-cir mode is similar to the offered-profile-capped-cir mode except that it combines soft in-profile with profile in and soft-out-of-profile with profile out and eliminates the offered-undefined statistic.

The impact of using offered-limited-capped-cir stat-mode while profile-capped mode is disabled is that one of the counting resources in the forwarding plane and traffic manager will not be used and soft-in-profile will be treated as offered-in instead of offered-undefined.

This mode is intended to be used with profile-capped configured within the policer but without enable-exceed-pir configured as this could cause the traffic profile to be modified by the policer in a way that is not accounted for in the statistics.

The counters displayed in the show output and those collected when collect-stats is enabled (the actual fields collected depends on the record configured in the applied accounting policy) are described in Egress Accounting Statistics Collected in offered-limited-capped-cir stat-mode .

Table 28. Egress Accounting Statistics Collected in offered-limited-capped-cir stat-mode

Show Output

Accounting Stats Collected

Field

Field Description

Off. InProf

ipo

InProfilePacketsOffered

ioo

InProfileOctetsOffered

Off. OutProf

opo

OutOfProfilePacketsOffered

ooo

OutOfProfileOctetsOffered

Dro. InProf

ipd

InProfilePacketsDropped

iod

InProfileOctetsDropped

Dro. OutProf

opd

OutOfProfilePacketsDropped

ood

OutOfProfileOctetsDropped

For. InProf

ipf

InProfilePacketsForwarded

iof

InProfileOctetsForwarded

For. OutProf

opf

OutOfProfilePacketsForwarded

oof

OutOfProfileOctetsForwarded

offered-profile-capped-cir

Counter resource allocation: 5

This stat-mode provides offered, dropped, and forwarded packet and octet counters corresponding to the profile of traffic entering (offered) and exiting (dropped/forwarded) the policer when egress reclassification is performed so that the traffic entering the policer is made up of traffic that is inplus-profile, in-profile, out-of-profile, exceed-profile, soft in-profile, and soft out-of-profile. The offered counters cover traffic reclassified to in-profile (which includes traffic reclassified to inplus-profile), traffic reclassified to out-of-profile (which includes traffic reclassified to exceed-profile) and traffic that has not been reclassified at egress (uncolored). In the dropped and forwarded counters, inplus-profile traffic is counted with the in-profile counter and exceed-profile traffic is counted with the out-of-profile counter.

When offered-profile-capped-cir is defined, the system creates five offered-output counters in the forwarding plane and five discard counters in the traffic manager.

The offered-profile-capped-cir mode is similar to the offered-profile-cir mode except that it includes support for profile inplus, profile in and soft-in-profile that may be output as out-of-profile due to enabling profile-capped mode on the ingress policer.

The impact of using offered-profile-capped-cir stat-mode while profile-capped mode is disabled is that one of the counting resources in the forwarding plane and traffic manager will not be used and soft-in-profile will be treated as offered-in (hard in-profile) instead of offered-undefined (uncolored).

This mode is intended to be used with profile-capped configured within the policer but without enable-exceed-pir configured as this could cause the traffic profile to be modified by the policer in a way that is not accounted for in the statistics.

The counters displayed in the show output and those collected when collect-stats is enabled (the actual fields collected depends on the record configured in the applied accounting policy) are described in Egress Accounting Statistics Collected in offered-profile-capped-cir stat-mode .

Table 29. Egress Accounting Statistics Collected in offered-profile-capped-cir stat-mode

Show Output

Accounting Stats Collected

Field

Field Description

Off. InProf

ipo

InProfilePacketsOffered

ioo

InProfileOctetsOffered

Off. OutProf

opo

OutOfProfilePacketsOffered

ooo

OutOfProfileOctetsOffered

Off. Uncolor

ucp

UncoloredPacketsOffered

uco

UncoloredOctetsOffered

Dro. InProf

ipd

InProfilePacketsDropped

iod

InProfileOctetsDropped

Dro. OutProf

opd

OutOfProfilePacketsDropped

ood

OutOfProfileOctetsDropped

For. InProf

ipf

InProfilePacketsForwarded

iof

InProfileOctetsForwarded

For. OutProf

opf

OutOfProfilePacketsForwarded

oof

OutOfProfileOctetsForwarded

offered-total-cir-exceed

Counter resource allocation: 3

This stat-mode provides offered, dropped, and forwarded packet and octet counters corresponding to the profile of traffic entering (offered) and exiting (dropped/forwarded) the policer. All offered traffic is provided in a single counter. In the dropped and forwarded counters, inplus-profile traffic is counted with the in-profile counter. The offered-total-cir-exceed mode allocates three forwarding plane offered counters and three traffic manager discard counters.

The offered-total-cir-exceed mode is similar to the offered-total-cir mode except that it includes support for forwarded and dropped counters for profile exceed.

This mode is intended to be used when the policer is configured with enable-exceed-pir to forward packets that exceed its configured PIR or when traffic is egress reclassified to profile exceed. The mode gives the forwarded and dropped counters per profile (in, out, exceed). It is also intended to be used without profile-capped configured within the policer as it could cause the traffic profile to be modified by the policer. This stat-mode is not supported for dynamic policers.

The counters displayed in the show output and those collected when collect-stats is enabled (the actual fields collected depends on the record configured in the applied accounting policy) are described in Egress Accounting Statistics Collected in offered-total-cir-exceed stat-mode .

Table 30. Egress Accounting Statistics Collected in offered-total-cir-exceed stat-mode

Show Output

Accounting Stats Collected

Field

Field Description

Off. All

apo

AllPacketsOffered

aoo

AllOctetsOffered

Dro. InProf

ipd

InProfilePacketsDropped

iod

InProfileOctetsDropped

Dro. OutProf

opd

OutOfProfilePacketsDropped

ood

OutOfProfileOctetsDropped

Dro. ExcProf

xpd

ExceedProfilePktsDropped

xod

ExceedProfileOctetsDropped

For. InProf

ipf

InProfilePacketsForwarded

iof

InProfileOctetsForwarded

For. OutProf

opf

OutOfProfilePacketsForwarded

oof

OutOfProfileOctetsForwarded

For. ExcProf

xpf

ExceedProfilePktsForwarded

xof

ExceedProfileOctetsForwarded

offered-four-profile-no-cir

Counter resource allocation: 4

This stat-mode provides offered, dropped, and forwarded packet and octet counters corresponding to the profile of traffic entering the policer. Offered, dropped, and forwarded counters are provided for inplus, in, out and exceed-profile traffic.

The offered-four-profile-no-cir mode allocates four forwarding plane offered counters and four traffic manager discard counters.

The offered-four-profile-no-cir mode is similar to the offered-profile-no-cir mode except that it includes support for offered, dropped, and forwarded counters for both inplus-profile and exceed-profile.

This mode is intended to be used when traffic is egress reclassified to inplus and/or exceed-profile. It is also intended to be used without profile-capped configured within the policer as it could cause the traffic profile to be modified by the policer. This stat-mode is not supported for dynamic policers.

The counters displayed in the show output and those collected when collect-stats is enabled (the actual fields collected depends on the record configured in the applied accounting policy) are described in Egress Accounting Statistics Collected in offered-four-profile-no-cir stat-mode .

Table 31. Egress Accounting Statistics Collected in offered-four-profile-no-cir stat-mode

Show Output

Accounting Stats Collected

Field

Field Description

Off. InProf

ipo

InProfilePacketsOffered

ioo

InProfileOctetsOffered

Off. OutProf

opo

OutOfProfilePacketsOffered

ooo

OutOfProfileOctetsOffered

Off. ExcProf

xpo

ExceedProfilePacketsOffered

xoo

ExceedProfileOctetsOffered

Off. InplusProf

ppo

InplusProfilePacketsOffered

poo

InplusProfileOctetsOffered

Dro. InProf

ipd

InProfilePacketsDropped

iod

InProfileOctetsDropped

Dro. OutProf

opd

OutOfProfilePacketsDropped

ood

OutOfProfileOctetsDropped

Dro. ExcProf

xpd

ExceedProfilePktsDropped

xod

ExceedProfileOctetsDropped

Dro. InprofProf

ppd

InplusProfilePktsDropped

pod

InplusProfileOctetsDropped

For. InProf

ipf

InProfilePacketsForwarded

iof

InProfileOctetsForwarded

For. OutProf

opf

OutOfProfilePacketsForwarded

oof

OutOfProfileOctetsForwarded

For. ExcProf

xpf

ExceedProfilePktsForwarded

xof

ExceedProfileOctetsForwarded

For. InplusProf

ppf

InplusProfilePktsForwarded

pof

InplusProfileOctetsForwarded

offered-total-cir-four-profile

Counter resource allocation: 4

This stat-mode provides offered, dropped, and forwarded packet and octet counters corresponding to the profile of traffic entering (offered) and exiting (dropped/forwarded) the policer. All offered traffic is provided in a single counter. There is a separate dropped and forwarded counter for inplus, in, out and exceed-profile traffic.

The offered-total-cir-four-profile mode allocates four forwarding plane offered counters and four traffic manager discard counters.

The offered-total-cir-four-profile mode is similar to the offered-total-cir except that it includes support for forwarded and dropped counters for both profile inplus and profile exceed.

This mode is intended to be used when traffic is reclassified at egress to inplus-profile. It is also intended to be used without profile-capped configured within the policer as it could cause the traffic profile to be modified by the policer. This stat-mode is not supported for dynamic policers.

The counters displayed in the show output and those collected when collect-stats is enabled (the actual fields collected depends on the record configured in the applied accounting policy) are described in Egress Accounting Statistics Collected in offered-total-cir-four-profile stat-mode .

Table 32. Egress Accounting Statistics Collected in offered-total-cir-four-profile stat-mode

Show Output

Accounting Stats Collected

Field

Field Description

Off. All

apo

AllPacketsOffered

aoo

AllOctetsOffered

Dro. InProf

ipd

InProfilePacketsDropped

iod

InProfileOctetsDropped

Dro. OutProf

opd

OutOfProfilePacketsDropped

ood

OutOfProfileOctetsDropped

Dro. ExcProf

xpd

ExceedProfilePktsDropped

xod

ExceedProfileOctetsDropped

Dro. InprofProf

ppd

InplusProfilePktsDropped

pod

InplusProfileOctetsDropped

For. InProf

ipf

InProfilePacketsForwarded

iof

InProfileOctetsForwarded

For. OutProf

opf

OutOfProfilePacketsForwarded

oof

OutOfProfileOctetsForwarded

For. ExcProf

xpf

ExceedProfilePktsForwarded

xof

ExceedProfileOctetsForwarded

For. InplusProf

ppf

InplusProfilePktsForwarded

pof

InplusProfileOctetsForwarded

Platforms

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

stat-mode

Syntax

stat-mode {no-stats | minimal | offered-profile-no-cir | offered-priority-no-cir | offered-profile-cir | offered-priority-cir | offered-total-cir | offered-limited-profile-cir | offered-profile-capped-cir | offered-limited-capped-cir}

no stat mode

Context

[Tree] (config>qos>qgrps>ing>qgrp>policer stat-mode)

Full Context

configure qos queue-group-templates ingress queue-group policer stat-mode

Description

This command is used to configure the forwarding plane counters that allow offered, forwarded, and dropped accounting to occur for the policer. An ingress policer has multiple types of offered packets (explicit in-profile, explicit out-of-profile, uncolored, high-priority or low-priority) and each of these offered types is interacting with the policer’s metering and profiling functions resulting in colored output packets (green, yellow, and red). Due to the large number of policers, it is not economical to allocate counters in the forwarding plane for all possible offered packet types and output conditions. Many policers, for example, will not be configured with a CIR profiling rate and not all policers will receive explicitly profiled offered packets. The stat-mode command allows provisioning of the number of counters each policer requires and how the offered packet types and output conditions should be mapped to the counters.

While a no-stats mode is supported that prevents any packet accounting, the use of the policer’s parent command requires that the policer's stat-mode be set at least to the minimal setting so that offered stats are available for the policer's Fair Information Rate (FIR) to be calculated. When a policer has been made a child to a parent policer, the stat-mode cannot be changed to no-stats unless the policer parenting is first removed.

Each time the policer’s stat-mode is changed, any previous counter values are lost and any new counters are set to zero.

Each mode uses a certain number of counters per policer instance that are allocated from the forwarding plane’s policer counter resources. The total/allocated/free stats can be viewed by using the tools dump resource-usage card fp command. If insufficient counters exist to implement a mode on any policer instance, the stat-mode change will fail and the previous mode will continue unaffected for all instances of the policer.

The stat-modes are described in Stat Mode Descriptions.

Table 33. Stat Mode Descriptions

Stat Mode

Stat Resources

Traffic Counters (Packet/Octets)

Comments

Offered

Dropped/Forwarded

no-stats

0

None

None

Minimal

1

Single counter entering policer

Single counter for dropped/forwarded exiting policer

offered-profile-no-cir

2

In/out entering policer

In/out entering policer

Intended for when the policer does not change the profile of packets. Includes only in- and out-of-profile.

offered-priority-no-cir

2

High/low entering policer

High/low entering policer

Intended for when only packet priority stats are required.

offered-profile-cir

4

In/out/uncolored entering policer

In/out exiting policer

Intended for when the policer can change the profile of packets to in- and out-of-profile.

offered-priority-cir

4

High/low entering policer

In/out exiting policer

Intended for when packet priority entering the policer and profile exiting the policer is required.

offered-total-cir

2

Single counter entering policer

In/out exiting policer

offered-limited-profile-cir

3

Out/uncolored entering policer

In/out exiting policer

Intended for when the policer can change the profile of packet to in- and out-of-profile. The information is limited compared to offered-profile-capped-cir with the benefit of using one less stat resource.

offered-profile-capped-cir

5

In/out/uncolored entering policer

In/out exiting policer

Intended for when the policer has profile-capped configured.

offered-limited-capped-cir

4

In/uncolored entering policer

In/out exiting policer

Intended for when the policer has profile-capped configured. The information is limited compared to offered-profile-capped-cir with the benefit of using one less stat resource.

The default stat-mode when a policer is created within the policy is minimal.

The stat-mode setting defined for the policer in the QoS policy may be overridden on an sla-profile or SAP where the policy is applied. If insufficient policer counter resources exist to implement the override, the stat-mode override command will fail. The previous stat-mode setting active for the policer will continue to be used by the policer.

The no form of this command attempts to return the policer’s stat-mode setting to minimal. The command will fail if insufficient policer counter resources exist to implement minimal where the QoS policer is currently applied and has a forwarding class mapping.

Parameters

no-stats

Counter resource allocation: 0

The policer does not have any forwarding plane counters allocated and cannot provide offered, dropped and forwarded statistics. A policer using no-stats cannot be a child to a parent policer and the policer’s parent command will fail.

When collect-stats is enabled, no statistics are generated.

minimal

Counter resource allocation: 1

This stat-mode provides the minimal accounting resource usage and counter information, and includes the total offered, dropped and forwarded packet and octet counters for traffic entering (offered) and exiting (dropped/forwarded) the policer.

The default stat-mode for a policer is minimal. The minimal mode allocates 1 forwarding plane offered counter and one traffic manager discard counter. The forwarding counter is derived by subtracting the discard counter from the offered counter. The counters do not differentiate possible offered types (profile or priority) and do not count in-profile or out-of-profile output. This does not prevent the policer from supporting different offered packet types and does not prevent the policer from supporting a CIR rate.

This counter mode is useful when only the most basic accounting information is required.

The counters displayed in the show output and those collected when collect-stats is enabled (the actual fields collected depends on the record configured in the applied accounting policy) are described in Ingress Accounting Statistics Collected in minimal stat-mode .

Table 34. Ingress Accounting Statistics Collected in minimal stat-mode

Show Output

Accounting Stats Collected

Field

Field Description

Off. All

apo

AllPacketsOffered

aoo

AllOctetsOffered

Dro. All

apd

AllPacketsDropped

aod

AllOctetsDropped

For. All

apf

AllPacketsForwarded

aof

AllOctetsForwarded

offered-profile-no-cir

Counter resource allocation: 2

This stat-mode provides offered, dropped and forwarded packet and octet counters corresponding to the profile of traffic entering the policer.

The offered-profile-no-cir mode allocates two forwarding plane offered counters and two traffic manager discard counters.

The offered-profile-no-cir mode is most useful when the policer is receiving only in-profile and out-of-profile premarked (and trusted) packets. It is expected that, in this instance, a CIR rate will not be defined since all packets are already premarked. This mode does not prevent the policer from receiving untrusted (color undefined) nor does it prevent the policer from being configured with a CIR rate.

This mode is intended to be used without profile-capped configured within the policer as it could cause the traffic profile to be modified by the policer.

The counters displayed in the show output and those collected when collect-stats is enabled (the actual fields collected depends on the record configured in the applied accounting policy) are described in Ingress Accounting Statistics Collected in offered-profile-no-cir stat-mode .

Table 35. Ingress Accounting Statistics Collected in offered-profile-no-cir stat-mode

Show Output

Accounting Stats Collected

Field

Field Description

Off. InProf

ipo

InProfilePacketsOffered

ioo

InProfileOctetsOffered

Off. OutProf

opo

OutOfProfilePacketsOffered

ooo

OutOfProfileOctetsOffered

Dro. InProf

ipd

InProfilePacketsDropped

iod

InProfileOctetsDropped

Dro. OutProf

opd

OutOfProfilePacketsDropped

ood

OutOfProfileOctetsDropped

For. InProf

ipf

InProfilePacketsForwarded

iof

InProfileOctetsForwarded

For. OutProf

opf

OutOfProfilePacketsForwarded

oof

OutOfProfileOctetsForwarded

offered-priority-no-cir

Counter resource allocation: 2

This stat-mode provides offered, dropped and forwarded packet and octet counters corresponding to the packet priority of traffic entering the policer.

The offered-priority-no-cir mode allocates two forwarding plane offered counters and two traffic manager discard counters.

The offered-priority-no-cir mode is most useful when the policer is receiving only untrusted packets and the ingress priority high and priority low classification options are being used without a CIR profiling rate defined. This mode does not prevent the policer from receiving trusted packets that are premarked in-profile or out-of-profile nor does it prevent the policer from being configured with a CIR rate.

This mode is intended to be used without profile-capped configured within the policer as it could cause the traffic profile to be modified by the policer.

The counters displayed in the show output and those collected when collect-stats is enabled (the actual fields collected depends on the record configured in the applied accounting policy) are described in Ingress Accounting Statistics Collected in offered-priority-no-cir stat-mode .

Table 36. Ingress Accounting Statistics Collected in offered-priority-no-cir stat-mode

Show Output

Accounting Stats Collected

Field

Field Description

Off. HiPrio

hpo

HighPriorityPacketsOffered

hoo

HighPriorityOctetsOffered

Off. LowPrio

lpo

LowPriorityPacketsOffered

loo

LowPriorityOctetsOffered

Dro. HiPrio

hpd

HighPriorityPacketsDropped

hod

HighPriorityOctetsDropped

Dro. LowPrio

lpd

LowPriorityPacketsDropped

lod

LowPriorityOctetsDropped

For. HiPrio

hpf

HighPriorityPacketsForwarded

hof

HighPriorityOctetsForwarded

For. LowPrio

lpf

LowPriorityPacketsForwarded

lof

LowPriorityOctetsForwarded

offered-profile-cir

Counter resource allocation: 4

This stat-mode provides offered, dropped and forwarded packet and octet counters corresponding to the profile of traffic entering (offered) and exiting (dropped/forwarded) the policer when ingress reclassification is performed so that the traffic entering the policer comprises of hard in/out and uncolored. The offered counters cover traffic explicitly profiled to in-profile, traffic explicitly profiled to out-of-profile, and traffic that has not been explicitly profiled at ingress (uncolored).

The offered-profile-cir mode allocates four forwarding plane offered counters and four traffic manager discard counters.

The offered-profile-cir mode is most useful when the policer is receiving trusted out-of-profile and in-profile traffic and is also receiving untrusted packets that are being applied to a defined CIR profiling rate. This mode differs from offered-limited-profile-cir mode in that it expects both trusted in-profile and out-of-profile packets while still performing CIR profiling on packets with untrusted markings. If trusted in-profile packets are not being received, the offered-limited-profile-cir stat-mode could be used instead, which has the benefit of using a reduced number of stat resources.

This mode is intended to be used without profile-capped configured within the policer as this could cause the traffic profile to be modified by the policer in a way that is not accounted for in the statistics.

The counters displayed in the show output and those collected when collect-stats is enabled (the actual fields collected depends on the record configured in the applied accounting policy) are described in Ingress Accounting Statistics Collected in offered-profile-cir stat-mode .

Table 37. Ingress Accounting Statistics Collected in offered-profile-cir stat-mode

Show Output

Accounting Stats Collected

Field

Field Description

Off. InProf

ipo

InProfilePacketsOffered

ioo

InProfileOctetsOffered

Off. OutProf

opo

OutOfProfilePacketsOffered

ooo

OutOfProfileOctetsOffered

Off. Uncolor

ucp

UncoloredPacketsOffered

uco

UncoloredOctetsOffered

Dro. InProf

ipd

InProfilePacketsDropped

iod

InProfileOctetsDropped

Dro. OutProf

opd

OutOfProfilePacketsDropped

ood

OutOfProfileOctetsDropped

For. InProf

ipf

InProfilePacketsForwarded

iof

InProfileOctetsForwarded

For. OutProf

opf

OutOfProfilePacketsForwarded

oof

OutOfProfileOctetsForwarded

offered-priority-cir

Counter resource allocation: 4

This stat-mode provides offered, dropped and forwarded packet and octet counters corresponding to the priority of traffic entering the policer and the profile exiting the policer.

The offered-priority-cir mode allocates four forwarding plane offered counters and four traffic manager discard counters.

The offered-priority-cir mode is most useful when the policer is receiving only untrusted packets that are being classified as high priority or low priority and are being applied to a defined CIR profiling rate. This mode differs from offered-profile-cir mode in that it does not expect trusted in-profile and out-of-profile packets but does not exclude the ability of the policer to receive them.

This mode is intended to be used without profile-capped configured within the policer as it could cause the traffic profile to be modified by the policer in a way that is not accounted for in the statistics.

The counters displayed in the show output and those collected when collect-stats is enabled (the actual fields collected depends on the record configured in the applied accounting policy) are described in Ingress Accounting Statistics Collected in offered-priority-cir stat-mode .

Table 38. Ingress Accounting Statistics Collected in offered-priority-cir stat-mode

Show Output

Accounting Stats Collected

Field

Field Description

Off. HiPrio

hpo

HighPriorityPacketsOffered

hoo

HighPriorityOctetsOffered

Off. LowPrio

lpo

LowPriorityPacketsOffered

loo

LowPriorityOctetsOffered

Dro. InProf

ipd

InProfilePacketsDropped

iod

InProfileOctetsDropped

Dro. OutProf

opd

OutOfProfilePacketsDropped

ood

OutOfProfileOctetsDropped

For. InProf

ipf

InProfilePacketsForwarded

iof

InProfileOctetsForwarded

For. OutProf

opf

OutOfProfilePacketsForwarded

oof

OutOfProfileOctetsForwarded

offered-total-cir

Counter resource allocation: 2

This stat-mode provides offered, dropped and forwarded packet and octet counters corresponding to the profile of traffic entering (offered) and exiting (dropped/forwarded) the policer. All offered traffic is provided in a single counter.

The offered-total-cir mode allocates two forwarding plane offered counters and two traffic manager discard counters.

The offered-total-cir mode is most useful when the policer is not receiving trusted in-profile or out-of-profile traffic and both high- and low-priority classifications are not being used on the untrusted packets and the offered packets are being applied to a defined CIR profiling rate. This mode does not prevent the policer from receiving trusted in-profile or out-of-profile packets and does not prevent the use of priority high or low classifications on the untrusted packets.

This mode is intended to be used without profile-capped configured within the policer as it could cause the traffic profile to be modified by the policer in a way that is not accounted for in the statistics.

The counters displayed in the show output and those collected when collect-stats is enabled (the actual fields collected depends on the record configured in the applied accounting policy) are described in Ingress Accounting Statistics collected in offered-total-cir stat-mode .

Table 39. Ingress Accounting Statistics collected in offered-total-cir stat-mode

Show Output

Accounting Stats Collected

Field

Field Description

Off. All

apo

AllPacketsOffered

aoo

AllOctetsOffered

Dro. InProf

ipd

InProfilePacketsDropped

iod

InProfileOctetsDropped

Dro. OutProf

opd

OutOfProfilePacketsDropped

ood

OutOfProfileOctetsDropped

For. InProf

ipf

InProfilePacketsForwarded

iof

InProfileOctetsForwarded

For. OutProf

opf

OutOfProfilePacketsForwarded

oof

OutOfProfileOctetsForwarded

offered-limited-profile-cir

Counter resource allocation: 3

This stat-mode provides offered, dropped and forwarded packet and octet counters corresponding to the profile of traffic entering (offered) and exiting (dropped/forwarded) the policer when ingress reclassification is performed so that the traffic entering the policer comprises of hard out and uncolored. The offered counters cover traffic explicitly profiled to out-of-profile and traffic that has not been explicitly profiled at ingress (uncolored). The traffic explicitly profiled to in-profile is counted with the uncolored traffic.

The offered-limited-profile-cir mode allocates three forwarding plane offered counters and three traffic manager discard counters.

The offered-limited-profile-cir mode is most useful when the policer is receiving trusted out-of-profile (profile out but no profile in) traffic and untrusted packets are being applied to a defined CIR profiling rate. This mode does not prevent the policer from receiving trusted in-profile packets. If trusted in-profile packets are not being received, the offered-limited-profile-cir is preferred over offered-profile-cir because it uses a reduced number of stat resources.

This mode is intended to be used without profile-capped configured within the policer as it could cause the traffic profile to be modified by the policer in a way that is not accounted for in the statistics.

The counters displayed in the show output and those collected when collect-stats is enabled (the actual fields collected depends on the record configured in the applied accounting policy) are described in Ingress Accounting Statistics Collected in offered-limited-profile-cir stat-mode .

Table 40. Ingress Accounting Statistics Collected in offered-limited-profile-cir stat-mode

Show Output

Accounting Stats Collected

Field

Field Description

Off. OutProf

opo

OutOfProfilePacketsOffered

ooo

OutOfProfileOctetsOffered

Off. Uncolor

ucp

UncoloredPacketsOffered

uco

UncoloredOctetsOffered

Dro. InProf

ipd

InProfilePacketsDropped

iod

InProfileOctetsDropped

Dro. OutProf

opd

OutOfProfilePacketsDropped

ood

OutOfProfileOctetsDropped

For. InProf

ipf

InProfilePacketsForwarded

iof

InProfileOctetsForwarded

For. OutProf

opf

OutOfProfilePacketsForwarded

oof

OutOfProfileOctetsForwarded

offered-profile-capped-cir

Counter resource allocation: 5

This stat-mode provides offered, dropped and forwarded packet and octet counters corresponding to the profile of traffic entering (offered) and exiting (dropped/forwarded) the policer when ingress reclassification is performed so that the traffic entering the policer comprises of hard in/out and uncolored. The offered counters cover traffic explicitly profiled to in-profile, traffic explicitly profiled to out-of-profile, and traffic that has not been explicitly profiled at ingress (uncolored).

When offered-profile-capped-cir is defined, the system creates five offered-output counters in the forwarding plane and five discard counters in the traffic manager.

The offered-profile-capped-cir mode is similar to the offered-profile-cir mode except that it includes support for profile in and soft-in-profile that may be output as 'out-of-profile’ due to enabling profile-capped mode on the ingress policer.

The impact of using offered-profile-capped-cir stat-mode while profile-capped mode is disabled is that one of the counting resources in the forwarding plane and traffic manager will not be used.

The counters displayed in the show output and those collected when collect-stats is enabled (the actual fields collected depends on the record configured in the applied accounting policy) are described in Ingress Accounting Statistics Collected in offered-profile-capped-cir stat-mode .

Table 41. Ingress Accounting Statistics Collected in offered-profile-capped-cir stat-mode

Show Output

Accounting Stats Collected

Field

Field Description

Off. InProf

ipo

InProfilePacketsOffered

ioo

InProfileOctetsOffered

Off. OutProf

opo

OutOfProfilePacketsOffered

ooo

OutOfProfileOctetsOffered

Off. Uncolor

ucp

UncoloredPacketsOffered

uco

UncoloredOctetsOffered

Dro. InProf

ipd

InProfilePacketsDropped

iod

InProfileOctetsDropped

Dro. OutProf

opd

OutOfProfilePacketsDropped

ood

OutOfProfileOctetsDropped

For. InProf

ipf

InProfilePacketsForwarded

iof

InProfileOctetsForwarded

For. OutProf

opf

OutOfProfilePacketsForwarded

oof

OutOfProfileOctetsForwarded

offered-limited-capped-cir

Counter resource allocation: 4

This stat-mode provides offered, dropped and forwarded packet and octet counters corresponding to the profile of traffic entering (offered) and exiting (dropped/forwarded) the policer when ingress reclassification is performed resulting in the traffic entering the policer comprising of hard in/out and uncolored. The offered counters cover in-profile traffic and traffic that has not been explicitly profiled at ingress (uncolored). The traffic explicitly profiled to out-of-profile is counted with the uncolored traffic.

offered-limited-capped-cir is defined, the system creates four forwarding plane offered-output counters in the network processor and four discard counters in the traffic manager.

The offered-limited-capped-cir mode is similar to the offered-profile-capped-cir mode except that it combines soft in-profile with profile in (InProf) and profile out (OutProf) with soft-out-of-profile (Uncolor) and eliminates the 'offered undefined' statistic. If trusted out-of-profile packets are not being received, the offered-limited-capped-cir is preferred over offered-profile-capped-cir because it uses a reduced number of stat resources.

This mode is intended to be used with profile-capped configured within the policer.

The impact of using offered-limited-capped-cir stat-mode while profile-capped mode is disabled is that one of the counting resources in the forwarding plane and traffic manager will not be used.

The counters displayed in the show output and those collected when collect-stats is enabled (the actual fields collected depends on the record configured in the applied accounting policy) are described in Ingress Accounting Statistics Collected in offered-limited-capped-cir stat-mode .

Table 42. Ingress Accounting Statistics Collected in offered-limited-capped-cir stat-mode

Show Output

Accounting Stats Collected

Field

Field Description

Off. InProf

ipo

InProfilePacketsOffered

ioo

InProfileOctetsOffered

Off. Uncolor

ucp

UncoloredPacketsOffered

uco

UncoloredOctetsOffered

Dro. InProf

ipd

InProfilePacketsDropped

iod

InProfileOctetsDropped

Dro. OutProf

opd

OutOfProfilePacketsDropped

ood

OutOfProfileOctetsDropped

For. InProf

ipf

InProfilePacketsForwarded

iof

InProfileOctetsForwarded

For. OutProf

opf

OutOfProfilePacketsForwarded

oof

OutOfProfileOctetsForwarded

Platforms

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

stat-mode

Syntax

stat-mode {no-stats | minimal | offered-profile-no-cir | offered-profile-cir | offered-total-cir | offered-limited-capped-cir | offered-profile-capped-cir | offered-total-cir-exceed | offered-four-profile-no-cir | offered-total-cir-four-profile}

no stat mode

Context

[Tree] (cfg>qos>qgrps>egr>qgrp>policer stat-mode)

Full Context

configure qos queue-group-templates egress queue-group policer stat-mode

Description

The sap-egress QoS policy's policer stat-mode command is used to configure the forwarding plane counters that allow offered, forwarded, and dropped accounting to occur for the policer. An egress policer has multiple types of offered packets (soft in-profile and out-of-profile from ingress and hard in-profile, out-of-profile, and exceed-profile due to egress profile overrides) and each of these offered types is interacting with the policer’s metering and profiling functions resulting in colored output packets (green, yellow, and red). Due to the potential large number of egress policers, it is not economical to allocate counters in the forwarding plane for all possible offered packet types and output conditions. Many policers, for example, will not be configured with a CIR profiling rate and not all policers will receive explicitly reprofiled offered packets. The stat-mode command allows provisioning of the number of counters each policer requires and how the offered packet types and output conditions should be mapped to the counters.

While a no-stats mode is supported that prevents any packet accounting, the use of the policer's parent command requires that the policer’s stat-mode to be set at least to the minimal setting so that offered stats are available for the policer’s Fair Information Rate (FIR) to be calculated. When a policer has been made a child to a parent policer, the stat-mode cannot be changed to no-stats unless the policer parenting is first removed.

Each time the policer's stat-mode is changed, any previous counter values are lost and any new counters are set to zero.

Each mode uses a certain number of counters per policer instance that are allocated from the forwarding plane's policer counter resources. The total/allocated/free stats can be viewed by using the tools dump resource-usage card fp command. If insufficient counters exist to implement a mode on any policer instance, the stat-mode change will fail and the previous mode will continue unaffected for all instances of the policer.

The ingress policer stat-modes are described in Egress Policer Stat Mode Summary.

Table 43. Egress Policer Stat Mode Summary

Stat Mode

Stat Resources

Traffic Counters (Packet/Octets)

Comments

Offered

Dropped/Forwarded

no-stats

0

None

None

Minimal

1

Single counter entering policer

Single counter for dropped/forwarded exiting policer

offered-profile-no-cir

2

In/out entering policer

In/out entering policer

Intended for when the policer does not change the profile of packets. Includes only in- and out-of-profile.

offered-profile-cir

4

In/out/uncolored (that corresponds to in- or out-of-profile from the ingress processing) entering policer

In/out exiting policer

Intended for when the policer can change the profile of packets to in- and out-of-profile.

offered-total-cir

2

Single counter entering policer

In/out exiting policer

offered-limited-capped-cir

4

In/out entering policer

In/out exiting policer

Intended for when the policer has profile-capped configured. The information is limited compared to offered-profile-capped-cir with the benefit of using one less stat resource.

offered-profile-capped-cir

5

In/out/uncolored (that corresponds to in- or out-of-profile from the ingress processing) entering policer

In/out exiting policer

Intended for when the policer has profile-capped configured.

offered-total-cir-exceed

3

Single counter entering policer

In/out/exceed exiting policer

Intended for when the policer is configured with enable-exceed-pir to forward packets that exceed its configured PIR or when traffic is egress reclassified to profile exceed.

offered-four-profile-no-cir

4

Inplus/in/out/exceed entering policer

Inplus/in/out/exceed entering policer

Intended to be used when the policer does not change the profile of the packets and traffic is egress reclassified to profile inplus and/or exceed.

offered-total-cir-four-profile

4

Single counter entering policer

Inplus/in/out/exceed exiting policer

Intended to be used when the policer can change the profile of the packet and traffic is egress reclassified to profile inplus.

The default stat-mode when a policer is created within the policy is minimal.

The stat-mode setting defined for the policer in the QoS policy may be overridden on an sla-profile or SAP where the policy is applied. If insufficient policer counter resources exist to implement the override, the stat-mode override command will fail. The previous stat-mode setting active for the policer will continue to be used by the policer.

The no form of this command attempts to return the policer’s stat-mode setting to minimal. The command will fail if insufficient policer counter resources exist to implement minimal where the QoS policer is currently applied and has a forwarding class mapping.

Parameters

no-stats

Counter resource allocation: 0

The policer does not have any forwarding plane counters allocated and cannot provide offered, discard, and forward statistics. A policer using no-stats cannot be a child to a parent policer and the policer’s parent command will fail.

When collect-stats is enabled, no statistics are generated.

minimal

Counter resource allocation: 1

This stat-mode provides the minimal accounting resource usage and counter information, and includes only the total offered, dropped and forwarded packet and octet counters for traffic entering (offered) and exiting (dropped/forwarded) the policer.

The default stat-mode for a policer is minimal. The minimal mode allocates one forwarding plane offered counter and one traffic manager discard counter. The forwarding counter is derived by subtracting the discard counter from the offered counter. The counters do not differentiate possible offered types and do not count different profile output. This does not prevent the policer from supporting different offered packet types and does not prevent the policer from supporting a CIR rate or using exceed PIR.

The counters displayed in the show output and those collected when collect-stats is enabled are described in Egress Accounting Statistics Collected in minimal stat-mode (the actual fields collected depends on the record configured in the applied accounting policy).

Table 44. Egress Accounting Statistics Collected in minimal stat-mode

Show Output

Accounting Stats Collected

Field

Field Description

Off. All

apo

AllPacketsOffered

aoo

AllOctetsOffered

Dro. All

apd

AllPacketsDropped

aod

AllOctetsDropped

For. All

apf

AllPacketsForwarded

aof

AllOctetsForwarded

offered-profile-no-cir

Counter resource allocation: 2

This stat-mode provides offered, dropped and forwarded packet and octet counters corresponding to the profile of traffic entering the policer. inplus-profile traffic is counted with the in-profile counters and exceed-profile traffic is counted with the out-of-of profile counters.

The offered-profile-no-cir mode allocates two forwarding plane offered counters and two traffic manager discard counters.

The offered-profile-no-cir mode is most useful when profile-based offered, dropped and forwarded statistics are required from the egress policer, but a CIR or enable-exceed-pir is not being used to recolor the soft in-profile and out-of-profile packets. This mode does not prevent the policer from being configured with a CIR rate or using enable-exceed-pir.

This mode is intended to be used without profile-capped configured within the policer as it could cause the traffic profile to be modified by the policer.

The counters displayed in the show output and those collected when collect-stats is enabled are described in Egress Accounting Statistics Collected in offered-profile-no-cir stat-mode (the actual fields collected depends on the record configured in the applied accounting policy).

Table 45. Egress Accounting Statistics Collected in offered-profile-no-cir stat-mode

Show Output

Accounting Stats Collected

Field

Field Description

Off. InProf

ipo

InProfilePacketsOffered

ioo

InProfileOctetsOffered

Off. OutProf

opo

OutOfProfilePacketsOffered

ooo

OutOfProfileOctetsOffered

Dro. InProf

ipd

InProfilePacketsDropped

iod

InProfileOctetsDropped

Dro. OutProf

opd

OutOfProfilePacketsDropped

ood

OutOfProfileOctetsDropped

For. InProf

ipf

InProfilePacketsForwarded

iof

InProfileOctetsForwarded

For. OutProf

opf

OutOfProfilePacketsForwarded

oof

OutOfProfileOctetsForwarded

offered-profile-cir

Counter resource allocation: 4

This stat-mode provides offered, dropped and forwarded packet and octet counters corresponding to the profile of traffic entering (offered) and exiting (dropped/forwarded) the policer when egress reclassification is performed so that the traffic entering the policer comprises of hard inplus/in/out/exceed and soft in/out. The offered counters cover traffic reclassified to in-profile (that includes traffic reclassified to inplus-profile), traffic reclassified to out-of-profile (that includes traffic reclassified to exceed-profile), and traffic that has not been reclassified at egress (Uncolor). In the dropped and forwarded counters, inplus-profile traffic is counted with the in-profile counter and exceed-profile traffic is counted with the out-of-profile counter.

The offered-profile-cir mode allocates four forwarding plane offered counters and four traffic manager discard counters.

The offered-profile-cir mode is most useful when profile-based offered, dropped and forwarded stats are required from the egress policer and a CIR rate is being used to recolor the soft in-profile and out-of-profile packets.

This mode is intended to be used without profile-capped or enable-exceed-pir configured within the policer as these could cause the traffic profile to be modified by the policer in a way that is not accounted for in the statistics.

The counters displayed in the show output and those collected when collect-stats is enabled are described in Egress Accounting Statistics Collected in offered-profile-cir stat-mode (the actual fields collected depends on the record configured in the applied accounting policy).

Table 46. Egress Accounting Statistics Collected in offered-profile-cir stat-mode

Show Output

Accounting Stats Collected

Field

Field Description

Off. InProf

ipo

InProfilePacketsOffered

ioo

InProfileOctetsOffered

Off. OutProf

opo

OutOfProfilePacketsOffered

ooo

OutOfProfileOctetsOffered

Off. Uncolor

ucp

UncoloredPacketsOffered

uco

UncoloredOctetsOffered

Dro. InProf

ipd

InProfilePacketsDropped

iod

InProfileOctetsDropped

Dro. OutProf

opd

OutOfProfilePacketsDropped

ood

OutOfProfileOctetsDropped

For. InProf

ipf

InProfilePacketsForwarded

iof

InProfileOctetsForwarded

For. OutProf

opf

OutOfProfilePacketsForwarded

oof

OutOfProfileOctetsForwarded

offered-total-cir

Counter resource allocation: 2

This stat-mode provides offered, dropped, and forwarded packet and octet counters corresponding to the profile of traffic entering (offered) and exiting (dropped/forwarded) the policer. All offered traffic is provided in a single counter. In the dropped and forwarded counters, inplus-profile traffic is counted with the in-profile counter and exceed-profile traffic is counted with the out-of-profile counter.

The offered-total-cir mode allocates two forwarding plane offered counters and two traffic manager discard counters.

The offered-total-cir mode is most useful when the policer is not receiving trusted in-profile or out-of-profile traffic and both high- and low-priority classifications are not being used on the untrusted packets and the offered packets are being applied to a defined CIR profiling rate. This mode does not prevent the policer from receiving trusted in-profile or out-of-profile packets and does not prevent the use of priority high or low classifications on the untrusted packets.

This mode is intended to be used without profile-capped or enable-exceed-pir configured within the policer as these could cause the traffic profile to be modified by the policer in a way that is not accounted for in the statistics.

The counters displayed in the show output and those collected when collect-stats is enabled are described in Egress Accounting Statistics Collected in offered-total-cir stat-mode (the actual fields collected depends on the record configured in the applied accounting policy).

Table 47. Egress Accounting Statistics Collected in offered-total-cir stat-mode

Show Output

Accounting Stats Collected

Field

Field Description

Off. All

apo

AllPacketsOffered

aoo

AllOctetsOffered

Dro. InProf

ipd

InProfilePacketsDropped

iod

InProfileOctetsDropped

Dro. OutProf

opd

OutOfProfilePacketsDropped

ood

OutOfProfileOctetsDropped

For. InProf

ipf

InProfilePacketsForwarded

iof

InProfileOctetsForwarded

For. OutProf

opf

OutOfProfilePacketsForwarded

oof

OutOfProfileOctetsForwarded

offered-limited-capped-cir

Counter resource allocation: 4

This stat-mode provides offered, dropped and forwarded packet and octet counters corresponding to the profile of traffic entering (offered) and exiting (dropped/forwarded) the policer when egress reclassification is performed so that the traffic entering the policer comprises of hard inplus/in/out/exceed and soft in/out. The offered counters cover in-profile traffic (that includes traffic reclassified to inplus-profile) and out-of-profile traffic (that includes traffic reclassified to exceed-profile). In the dropped and forwarded counters, inplus-profile traffic is counted with the in-profile counter and exceed-profile traffic is counted with the out-of-profile counter.

When offered-limited-capped-cir is defined, the system creates four forwarding plane offered-output counters in the network processor and three discard counters in the traffic manager.

The offered-limited-capped-cir mode is similar to the offered-profile-capped-cir mode except that it combines soft-in-profile with profile in and soft-out-of-profile with profile out and eliminates the offered-undefined statistic.

The impact of using offered-limited-capped-cir stat-mode while profile-capped mode is disabled is that one of the counting resources in the forwarding plane and traffic manager will not be used and soft-in-profile will be treated as offered-in instead of offered-undefined.

This mode is intended to be used with profile-capped configured within the policer but without enable-exceed-pir configured as this could cause the traffic profile to be modified by the policer in a way that is not accounted for in the statistics.

The counters displayed in the show output and those collected when collect-stats is enabled are described in Egress Accounting Statistics Collected in offered-limited-capped-cir stat-mode (the actual fields collected depends on the record configured in the applied accounting policy).

Table 48. Egress Accounting Statistics Collected in offered-limited-capped-cir stat-mode

Show Output

Accounting Stats Collected

Field

Field Description

Off. InProf

ipo

InProfilePacketsOffered

ioo

InProfileOctetsOffered

Off. OutProf

opo

OutOfProfilePacketsOffered

ooo

OutOfProfileOctetsOffered

Dro. InProf

ipd

InProfilePacketsDropped

iod

InProfileOctetsDropped

Dro. OutProf

opd

OutOfProfilePacketsDropped

ood

OutOfProfileOctetsDropped

For. InProf

ipf

InProfilePacketsForwarded

iof

InProfileOctetsForwarded

For. OutProf

opf

OutOfProfilePacketsForwarded

oof

OutOfProfileOctetsForwarded

offered-profile-capped-cir

Counter resource allocation: 5

This stat-mode provides offered, dropped, and forwarded packet and octet counters corresponding to the profile of traffic entering (offered) and exiting (dropped/forwarded) the policer when egress reclassification is performed so that the traffic entering the policer is comprised of hard inplus, hard in, hard out, and hard exceed, as well as soft in and soft out. The offered counters cover traffic reclassified to in-profile (that includes traffic reclassified to inplus-profile), traffic reclassified to out-of-profile (that includes traffic reclassified to exceed-profile), and traffic that has not been reclassified at egress (uncolor). In the dropped and forwarded counters, inplus-profile traffic is counted with the in-profile counter and exceed-profile traffic is counted with the out-of-profile counter.

When offered-profile-capped-cir is defined, the system creates five offered-output counters in the forwarding plane and five discard counters in the traffic manager.

The offered-profile-capped-cir mode is similar to the offered-profile-cir mode except that it includes support for profile inplus, profile in, and soft-in-profile that may be output as out-of-profile due to enabling profile-capped mode on the ingress policer.

The impact of using offered-profile-capped-cir stat-mode while profile-capped mode is disabled is that one of the counting resources in the forwarding plane and traffic manager will not be used and soft-in-profile will be treated as offered-in (hard in-profile) instead of offered-undefined (uncolored).

This mode is intended to be used with profile-capped configured within the policer but without enable-exceed-pir configured as this could cause the traffic profile to be modified by the policer in a way that is not accounted for in the statistics.

The counters displayed in the show output and those collected when collect-stats is enabled are described in Egress Accounting Statistics Collected in offered-profile-capped-cir stat-mode (the actual fields collected depends on the record configured in the applied accounting policy).

Table 49. Egress Accounting Statistics Collected in offered-profile-capped-cir stat-mode

Show Output

Accounting Stats Collected

Field

Field Description

Off. InProf

ipo

InProfilePacketsOffered

ioo

InProfileOctetsOffered

Off. OutProf

opo

OutOfProfilePacketsOffered

ooo

OutOfProfileOctetsOffered

Off. Uncolor

ucp

UncoloredPacketsOffered

uco

UncoloredOctetsOffered

Dro. InProf

ipd

InProfilePacketsDropped

iod

InProfileOctetsDropped

Dro. OutProf

opd

OutOfProfilePacketsDropped

ood

OutOfProfileOctetsDropped

For. InProf

ipf

InProfilePacketsForwarded

iof

InProfileOctetsForwarded

For. OutProf

opf

OutOfProfilePacketsForwarded

oof

OutOfProfileOctetsForwarded

offered-total-cir-exceed

Counter resource allocation: 3

This stat-mode provides offered, dropped, and forwarded packet and octet counters corresponding to the profile of traffic entering (offered) and exiting (dropped/forwarded) the policer. All offered traffic is provided in a single counter. In the dropped and forwarded counters, inplus-profile traffic is counted with the in-profile counter. The offered-total-cir-exceed mode allocates three forwarding plane offered counters and three traffic manager discard counters.

The offered-total-cir-exceed mode is similar to the offered-total-cir mode except that it includes support for forwarded and dropped counters for profile exceed.

This mode is intended to be used when the policer is configured with enable-exceed-pir to forward packets that exceed its configured PIR or when traffic is egress reclassified to profile exceed. The mode gives the forwarded and dropped counters per profile (in, out, exceed). It is also intended to be used without profile-capped configured within the policer as it could cause the traffic profile to be modified by the policer. This stat-mode is not supported for dynamic policers.

The counters displayed in the show output and those collected when collect-stats is enabled are described in Egress Accounting Statistics Collected in offered-total-cir-exceed stat-mode (the actual fields collected depends on the record configured in the applied accounting policy).

Table 50. Egress Accounting Statistics Collected in offered-total-cir-exceed stat-mode

Show Output

Accounting Stats Collected

Field

Field Description

Off. All

apo

AllPacketsOffered

aoo

AllOctetsOffered

Dro. InProf

ipd

InProfilePacketsDropped

iod

InProfileOctetsDropped

Dro. OutProf

opd

OutOfProfilePacketsDropped

ood

OutOfProfileOctetsDropped

Dro. ExcProf

xpd

ExceedProfilePktsDropped

xod

ExceedProfileOctetsDropped

For. InProf

ipf

InProfilePacketsForwarded

iof

InProfileOctetsForwarded

For. OutProf

opf

OutOfProfilePacketsForwarded

oof

OutOfProfileOctetsForwarded

For. ExcProf

xpf

ExceedProfilePktsForwarded

xof

ExceedProfileOctetsForwarded

offered-four-profile-no-cir

Counter resource allocation: 4

This stat-mode provides offered, dropped, and forwarded packet and octet counters corresponding to the profile of traffic entering the policer. Offered, dropped, and forwarded counters are provided for inplus-profile, in-profile, out-of-profile, and exceed-profile traffic.

The offered-four-profile-no-cir mode allocates four forwarding plane offered counters and four traffic manager discard counters.

The offered-four-profile-no-cir mode is similar to the offered-profile-no-cir mode except that it includes support for offered, dropped and forwarded counters for both profile inplus and profile exceed.

This mode is intended to be used when traffic is egress reclassified to profile inplus and/or exceed. It is also intended to be used without profile-capped configured within the policer as it could cause the traffic profile to be modified by the policer. This stat-mode is not supported for dynamic policers.

The counters displayed in the show output and those collected when collect-stats is enabled are described in Egress Accounting Statistics Collected in offered-four-profile-no-cir stat-mode (the actual fields collected depends on the record configured in the applied accounting policy).

Table 51. Egress Accounting Statistics Collected in offered-four-profile-no-cir stat-mode

Show Output

Accounting Stats Collected

Field

Field Description

Off. InProf

ipo

InProfilePacketsOffered

ioo

InProfileOctetsOffered

Off. OutProf

opo

OutOfProfilePacketsOffered

ooo

OutOfProfileOctetsOffered

Off. ExcProf

xpo

ExceedProfilePacketsOffered

xoo

ExceedProfileOctetsOffered

Off. InplusProf

ppo

InplusProfilePacketsOffered

poo

InplusProfileOctetsOffered

Dro. InProf

ipd

InProfilePacketsDropped

iod

InProfileOctetsDropped

Dro. OutProf

opd

OutOfProfilePacketsDropped

ood

OutOfProfileOctetsDropped

Dro. ExcProf

xpd

ExceedProfilePktsDropped

xod

ExceedProfileOctetsDropped

Dro. InplusProf

ppd

InplusProfilePktsDropped

pod

InplusProfileOctetsDropped

For. InProf

ipf

InProfilePacketsForwarded

iof

InProfileOctetsForwarded

For. OutProf

opf

OutOfProfilePacketsForwarded

oof

OutOfProfileOctetsForwarded

For. ExcProf

xpf

ExceedProfilePktsForwarded

xof

ExceedProfileOctetsForwarded

For. InplusProf

ppf

InplusProfilePktsForwarded

pof

InplusProfileOctetsForwarded

offered-total-cir-four-profile

Counter resource allocation: 4

This stat-mode provides offered, dropped, and forwarded packet and octet counters corresponding to the profile of traffic entering (offered) and exiting (dropped/forwarded) the policer. All offered traffic is provided in a single counter. There is a separate dropped and forwarded counter for inplus, in, out, and exceed-profile traffic.

The offered-total-cir-four-profile mode allocates four forwarding plane offered counters and four traffic manager discard counters.

The offered-total-cir-four-profile mode is similar to the offered-total-cir except that it includes support for forwarded and dropped counters for both inplus-profile and exceed-profile.

This mode is intended to be used when traffic is egress reclassified to inplus-profile. It is also intended to be used without profile-capped configured within the policer as it could cause the traffic profile to be modified by the policer. This stat-mode is not supported for dynamic policers.

The counters displayed in the show output and those collected when collect-stats is enabled are described in Egress Accounting Statistics Collected in offered-total-cir-four-profile stat-mode (the actual fields collected depends on the record configured in the applied accounting policy).

Table 52. Egress Accounting Statistics Collected in offered-total-cir-four-profile stat-mode

Show Output

Accounting Stats Collected

Field

Field Description

Off. All

apo

AllPacketsOffered

aoo

AllOctetsOffered

Dro. InProf

ipd

InProfilePacketsDropped

iod

InProfileOctetsDropped

Dro. OutProf

opd

OutOfProfilePacketsDropped

ood

OutOfProfileOctetsDropped

Dro. ExcProf

xpd

ExceedProfilePktsDropped

xod

ExceedProfileOctetsDropped

Dro. InprofProf

ppd

InplusProfilePktsDropped

pod

InplusProfileOctetsDropped

For. InProf

ipf

InProfilePacketsForwarded

iof

InProfileOctetsForwarded

For. OutProf

opf

OutOfProfilePacketsForwarded

oof

OutOfProfileOctetsForwarded

For. ExcProf

xpf

ExceedProfilePktsForwarded

xof

ExceedProfileOctetsForwarded

For. InplusProf

ppf

InplusProfilePktsForwarded

pof

InplusProfileOctetsForwarded

Platforms

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

stat-mode

Syntax

stat-mode {per-fc | aggregate}

no stat-mode

Context

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

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

[Tree] (config>router>mpls>lsp>ingr-stats stat-mode)

Full Context

configure router mpls lsp-template egress-statistics stat-mode

configure router mpls lsp egress-statistics stat-mode

configure router mpls lsp ingress-statistics stat-mode

Description

This command sets the mode used for collecting LSP statistics.

The no form of this command reverts to the default.

Default

stat-mode per-fc

Parameters

per-fc

Specifies that RSVP-TE statistics will be collected per FC.

aggregate

Specifies that SR-TE statistics will be collected as an aggregate across all FCs.

Platforms

All

  • configure router mpls lsp-template egress-statistics stat-mode
  • configure router mpls lsp egress-statistics stat-mode

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

  • configure router mpls lsp ingress-statistics stat-mode

state

state

Syntax

[no] state

Context

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

Full Context

configure subscriber-mgmt wlan-gw ue-query state

Description

This command enables matching on a specific UE state. Multiple states can be provisioned.

The no form of this command disables matching on the specified UE state (all UEs match).

Platforms

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

state

Syntax

state state

no state

Context

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

Full Context

configure router policy-options policy-statement entry from state

Description

This command identifies in resilient gateways which routes are associated with an active context and which routes are associated with a standby context.

Default

no state

Parameters

state

Specifies the state.

Values

srrp-master — This is used in non-CUPS BNG resiliency to identify routes associated with an active SRRP instance.

srrp-non-master — This is used in non-CUPS BNG resiliency to identify routes associated with a standby SRRP instance.

ipsec-master-with-peer — This is used in stateful multi-chassis IPsec (MC-IPsec) redundancy to identify routes associated with an active MC-IPsec node with a reachable peer.

ipsec-non-master — This is used in stateful MC-IPsec redundancy to identify routes associated with a standby MC-IPsec node.

ipsec-master-without-peer — This is used in stateful MC-IPsec redundancy to identify routes associated with an active MC-IPsec node without a reachable peer.

fsg-active — This is used in BNG CUPS inter-BNG-UP resiliency to identify routes associated with an FSG on the active BNG-UP. This covers all session-related routes, including framed routes, IPv6 gateway addresses, and aggregated routes. It does not include loopback addresses.

fsg-active-path-restoration — This is used in BNG CUPS inter-BNG-UP resiliency to identify routes associated with an FSG on an active BNG-UP that is in a headless state. This covers all session-related routes, including framed routes, IPv6 gateway addresses, and aggregated routes. It does not include loopback addresses.

fsg-standby — This is used in BNG CUPS inter-BNG-UP resiliency to identify routes associated with an FSG on the standby BNG-UP. This covers all session-related routes, including framed routes, IPv6 gateway addresses, and aggregated routes. It does not include loopback addresses.

Platforms

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

state-change

state-change

Syntax

[no] state-change

Context

[Tree] (debug>dynsvc>scripts>script>event state-change)

[Tree] (debug>dynsvc>scripts>event state-change)

[Tree] (debug>dynsvc>scripts>inst>event state-change)

Full Context

debug dynamic-services scripts script event state-change

debug dynamic-services scripts event state-change

debug dynamic-services scripts instance event state-change

Description

This command enables/disables the generation of a specific dynamic data service script debugging event output: state-change.

Platforms

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

state-timer

state-timer

Syntax

state-timer seconds [ action action]

no state-timer

Context

[Tree] (config>router>pcep>pcc state-timer)

Full Context

configure router pcep pcc state-timer

Description

This command configures the state timer for PCE-initiated LSPs. The state timer must be set to a value greater than the redelegation timer.

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

Default

state-timer 180 action remove

Parameters

seconds

Specifies the number of seconds before the state timer expires.

Values

1 to 3600

action

Specifies the actions that are taken on undelegated LSPs upon the state timer expiration.

Values

remove, none

Default

remove

Platforms

All

stateful

stateful

Syntax

[no] stateful

Context

[Tree] (config>subscr-mgmt>rtr-adv-plcy>pfx-opt stateful)

Full Context

configure subscriber-mgmt router-advertisement-policy prefix-options stateful

Description

This command enables the configuration of RA options for stateful DHCP prefixes used by the subscriber host.

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

stateless

stateless

Syntax

[no] stateless

Context

[Tree] (config>subscr-mgmt>rtr-adv-plcy>pfx-opt stateless)

Full Context

configure subscriber-mgmt router-advertisement-policy prefix-options stateless

Description

This command enables the configuration of RA options for stateless SLAAC prefixes used by the subscriber host.

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

static

static

Syntax

static

Context

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

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

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

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

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

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

Full Context

configure service vpls mesh-sdp mld-snooping static

configure service vpls spoke-sdp mld-snooping static

configure service vpls mesh-sdp igmp-snooping static

configure service vpls sap mld-snooping static

configure service vpls spoke-sdp igmp-snooping static

configure service vpls sap igmp-snooping static

Description

Commands in this context configure static group addresses. Static group addresses can be configured on a SAP or SDP. When present, either as a (*, g) or a (s,g) entry, multicast packets matching the configuration are forwarded even if no join message was registered for the specific group.

Platforms

All

static

Syntax

static

Context

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

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

Full Context

configure subscriber-mgmt igmp-policy static

configure subscriber-mgmt mld-policy static

Description

Commands in this context configure MLD static group membership parameters.

Platforms

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

static

Syntax

static ip-address ieee-address

no static ip-address

Context

[Tree] (config>service>vpls>proxy-arp static)

Full Context

configure service vpls proxy-arp static

Description

This command configures static entries to be added to the table. A static MAC-IP entry requires the addition of the MAC address to the FDB as either learned or CStatic (conditional static MAC) in order to become active.

Parameters

ip-address

Specifies the IPv4 address for the static entry.

ieee-address

Specifies a 48-bit MAC address in the form xx:xx:xx:xx:xx:xx or xx-xx-xx-xx-xx-xx, where xx represents a hexadecimal number.

Platforms

All

static

Syntax

static ipv6-address ieee-address {host | router}

no static ipv6-address

Context

[Tree] (config>service>vpls>proxy-nd static)

Full Context

configure service vpls proxy-nd static

Description

This command configures static entries to be added to the table. A static MAC-IP entry requires the addition of the MAC address to the FDB as either dynamic or CStatic (Conditional Static MAC) in order to become active. Along with the IPv6 and MAC, the entry must also be configured as either host or router. This will determine if the received NS for the entry will be replied with the R flag set to 1 (router) or 0 (host).

Parameters

ipv6-address

Specifies the IPv6 address for the static entry.

ieee-address

Specifies a 48-bit MAC address in the form xx:xx:xx:xx:xx:xx or xx-xx-xx-xx-xx-xx, where xx represents a hexadecimal number.

host

Specifies that the entry is type "host”.

router

Specifies that the entry is type "router”.

Platforms

All

static

Syntax

static

Context

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

Full Context

configure service vprn igmp interface static

Description

This command tests forwarding on an interface without a receiver host. When enabled, data is forwarded to an interface without receiving membership reports from host members.

Platforms

All

static

Syntax

static

Context

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

Full Context

configure service vprn mld interface static

Description

This command tests multicast forwarding on an interface without a receiver host. When enabled, data is forwarded to an interface without receiving membership reports from host members.

Platforms

All

static

Syntax

static

Context

[Tree] (config>service>vprn>pim>rp static)

Full Context

configure service vprn pim rp static

Description

This command enables access to the context to configure a static rendezvous point (RP) of a PIM-SM protocol instance.

Platforms

All

static

Syntax

static

Context

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

Full Context

configure router igmp interface static

Description

This command tests multicast forwarding on an interface without a receiver host. When enabled, data is forwarded to an interface without receiving membership reports from host members.

Platforms

All

static

Syntax

static

Context

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

Full Context

configure router igmp tunnel-interface static

Description

Commands in this context configure static multicast receiver hosts on a tunnel interface associated with an RSVP P2MP LSP.

When enabled, data is forwarded to an interface without receiving membership reports from host members.

Platforms

All

static

Syntax

static

Context

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

Full Context

configure router mld interface static

Description

This command tests multicast forwarding on an interface without a receiver host. When enabled, data is forwarded to an interface without receiving membership reports from host members.

Platforms

All

static

Syntax

static

Context

[Tree] (config>router>pim>rp>ipv6 static)

[Tree] (config>router>pim>rp static)

Full Context

configure router pim rp ipv6 static

configure router pim rp static

Description

Commands in this context configure static Rendezvous Point (RP) addresses for a multicast group range.

Entries can be created or destroyed. If no IP addresses are configured in the config>router>pim>rp>static>address context, then the multicast group to RP mapping is derived from the RP-set messages received from the Bootstrap Router.

Platforms

All

static

Syntax

static microseconds

no static

Context

[Tree] (config>router>if>if-attribute>delay static)

Full Context

configure router interface if-attribute delay static

Description

This command configures the unidirectional link delay. By default there is no configured delay, the link delay metric TLV is pruned in the IGP.

The no form of this command removes the configured unidirectional link delay.

Default

no static

Parameters

microseconds

Specifies the unidirectional link delay in microseconds.

Values

1 to 16777214

Platforms

All

static

Syntax

[no] static

Context

[Tree] (config>router>bgp>next-hop-res>use-leaked-routes static)

Full Context

configure router bgp next-hop-resolution use-leaked-routes static

Description

This command configures the router to resolve any non-leaked, unlabeled unicast IPv4 or IPv6 route in the base router BGP RIB by using a static route with direct next hops leaked from any VPRN instance. A BGP route resolved this way cannot resolve other routes (including BGP routes) and cannot be redistributed into non-BGP protocols, such as IGP.

The no form of this command prevents the use of leaked static routes to resolve BGP routes of the base router.

Default

no static

Platforms

All

static

Syntax

[no] static

Context

[Tree] (config>service>vprn>bgp>next-hop-res>use-leaked-routes static)

Full Context

configure service vprn bgp next-hop-resolution use-leaked-routes static

Description

This command configures the router to resolve any non-leaked, unlabeled unicast IPv4 or IPv6 route in the VPRN BGP RIB by using a static route with direct next hops leaked from the GRT. A BGP route resolved this way cannot resolve other routes (including BGP routes) and cannot be redistributed into non-BGP protocols, such as IGP.

The no form of this command prevents the use of leaked static routes to resolve BGP routes of the VPRN.

Default

no static

Platforms

All

static-aa-sub

static-aa-sub

Syntax

static-aa-sub transit-aasub-name

static-aa-sub transit-aasub-name app-profile app-profile-name [create]

no static-aa-sub transit-aasub-name

Context

[Tree] (config>app-assure>group>transit-ip-policy static-aa-sub)

Full Context

configure application-assurance group transit-ip-policy static-aa-sub

Description

This command configures static transit aa-subs with a name and an app-profile. A new transit sub with both a name and an app-profile is configured with the create command. Static transit aa-sub must have an explicitly assigned app-profile. An existing transit sub can optionally be assigned a different app-profile, or this command can be used to enter the static-aa-sub context.

The no form of this command deletes the named static transit aa-sub from the configuration.

Parameters

transit-aasub-name

Specifies the name of a transit subscriber up to 32 characters in length.

app-profile-name

Specifies the name of an existing application profile up to 32 characters in length.

create

Keyword used to create a new app-profile entry.

Platforms

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

static-aa-sub

Syntax

static-aa-sub transit-aasub-name

static-aa-sub transit-aasub-name app-profile app-profile-name [create]

no static-aa-sub transit-aasub-name

Context

[Tree] (config>app-assure>group>transit-prefix-policy static-aa-sub)

Full Context

configure application-assurance group transit-prefix-policy static-aa-sub

Description

This command configures a static transit aa-sub with a name and an app-profile. A new transit sub with both a name and an app-profile is configured with the create command. Static transit aa-sub must have an explicitly assigned app-profile. An existing transit sub can optionally be assigned a different app-profile, or this command can be used to enter the static-aa-sub context.

The no form of this command deletes the named static transit aa-sub from the configuration.

Parameters

transit-aasub-name

Specifies a transit aasub-name up to 32 characters.

app-profile-name

Specifies the name of an existing application profile up to 32 characters.

create

Keyword used to create a new app-profile entry

Platforms

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

static-address

static-address

Syntax

[no] static-address {ip-address | ipv6-address}

Context

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

Full Context

configure application-assurance group dns-ip-cache ip-cache static-address

Description

This command configures a static address in the cache.

Parameters

ip-address | ipv6-address

Specifies a character string up to 64 characters.

Platforms

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

static-arp

static-arp

Syntax

static-arp ieee-mac-address unnumbered

static-arp ip-address ieee-mac-address

no static-arp [ieee-mac-address] unnumbered

no static-arp ip-address [ieee-mac-address]

Context

[Tree] (config>service>vprn>if static-arp)

[Tree] (config>service>ies>if static-arp)

Full Context

configure service vprn interface static-arp

configure service ies interface static-arp

Description

This command configures a static address resolution protocol (ARP) entry associating a subscriber IP address with a MAC address for the core router instance. This static ARP appears in the core routing ARP table. A static ARP can only be configured if it exists on the network attached to the IP interface.

If an entry for a particular IP address already exists and a new MAC address is configured for the IP address, the existing MAC address will be replaced with the new MAC address.

The no form of this command removes a static ARP entry.

Parameters

ip-address

Specifies the IP address for the static ARP in IP address dotted decimal notation.

ieee-mac-address

Specifies the 48-bit MAC address for the static ARP in the form aa:bb:cc:dd:ee:ff or aa-bb-cc-dd-ee-ff, where aa, bb, cc, dd, ee and ff are hexadecimal numbers. Allowed values are any non-broadcast, non-multicast MAC and non-IEEE reserved MAC addresses.

unnumbered

Specifies the static ARP MAC for an unnumbered interface. Unnumbered interfaces support dynamic ARP. Once this command is configured, it overrides any dynamic ARP.

Platforms

All

static-arp

Syntax

static-arp ieee-mac-addr unnumbered

static-arp ip-address ieee-mac-address

no static-arp [ieee-mac-addr] unnumbered

no static-arp ip-address [ieee-mac-address]

Context

[Tree] (config>service>vpls>interface static-arp)

Full Context

configure service vpls interface static-arp

Description

This command configures a static address resolution protocol (ARP) entry associating a subscriber IP address with a MAC address for the core router instance. A static ARP can only be configured if it exists on the network attached to the IP interface.

If an entry for a particular IP address already exists and a new MAC address is configured for the IP address, the existing MAC address will be replaced with the new MAC address.

The no form of this command removes a static ARP entry.

Parameters

ip-address

Specifies the IP address for the static ARP in dotted decimal notation

ieee-mac-address

Specifies the 48-bit MAC address for the static ARP in the form aa:bb:cc:dd:ee:ff or aa-bb-cc-dd-ee-ff where aa, bb, cc, dd, ee and ff are hexadecimal numbers. Allowed values are any non-broadcast, non-multicast MAC and non-IEEE reserved MAC addresses.

unnumbered

Specifies the static ARP MAC for an unnumbered interface. Unnumbered interfaces support dynamic ARP. Once this command is configured, it overrides any dynamic ARP.

Platforms

All

static-arp

Syntax

static-arp ip-address ieee-mac-address

no static-arp ip-address

Context

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

Full Context

configure service vprn network-interface static-arp

Description

This command configures a static address resolution protocol (ARP) entry associating a subscriber IP address with a MAC address for the core router instance. This static ARP will appear in the core routing ARP table. A static ARP can only be configured if it exists on the network attached to the IP interface. If an entry for a particular IP address already exists and a new MAC address is configured for the IP address, the existing MAC address will be replaced with the new MAC address.

The no form of this command removes a static ARP entry.

Parameters

ip-address

Specifies the IP address for the static ARP in IP address dotted decimal notation.

ieee-mac-address

Specifies the 48-bit MAC address for the static ARP in the form aa:bb:cc:dd :ee:ff or aa-bb-cc-dd -ee-ff where aa, bb, cc, dd, ee and ff are hexadecimal numbers. Allowed values are any non-broadcast, non-multicast MAC and non-IEEE reserved MAC addresses.

Platforms

All

static-arp

Syntax

static-arp ip-address ieee-address

no static-arp ip-address

static-arp ieee-address unnumbered

no static-arp unnumbered

Context

[Tree] (config>router>if static-arp)

Full Context

configure router interface static-arp

Description

This command configures a static Address Resolution Protocol (ARP) entry associating an IP address with a MAC address for the core router instance. This static ARP appears in the core routing ARP table. A static ARP can only be configured if it exists on the network attached to the IP interface.

If an entry for a specific IP address already exists and a new MAC address is configured for the IP address, the existing MAC address is replaced by the new MAC address.

The number of static-arp entries that can be configured on a single node is limited to 1000.

Static ARP is used when a router needs to know about a device on an interface that cannot or does not respond to ARP requests. Therefore, the router configuration can state that if it has a packet that has a certain IP address to send it to the corresponding ARP address. Use proxy ARP so the router responds to ARP requests on behalf of another device.

The no form of this command removes a static ARP entry.

Parameters

ieee-address

Specifies the 48-bit MAC address for the static ARP in the form aa:bb:cc:dd :ee:ff or aa-bb-cc-dd -ee-ff, where aa, bb, cc, dd, ee and ff are hexadecimal numbers. Allowed values are any non-broadcast, non-multicast MAC and non-IEEE reserved MAC addresses.

unnumbered

Specifies the static ARP MAC for an unnumbered interface. Unnumbered interfaces support dynamic ARP. Once this command is configured, it overrides any dynamic ARP.

Platforms

All

static-cak

static-cak

Syntax

[no] static-cak

Context

[Tree] (config>macsec>connectivity-association static-cak)

Full Context

configure macsec connectivity-association static-cak

Description

This command allows the configuration of a Connectivity Association Key (CAK). The CAK is responsible for managing the MKA.

Platforms

All

static-entry

static-entry

Syntax

static-entry ip-prefix/ip-prefix-length upto prefix-length2 origin-as as-number [{valid | invalid}]

no static-entry ip-prefix/ip-prefix-length upto prefix-length2 origin-as as-number

Context

[Tree] (config>router>origin-validation static-entry)

Full Context

configure router origin-validation static-entry

Description

This command configures a static VRP entry indicating that a specific origin AS is either valid or invalid for a specific IP prefix range. Static VRP entries are stored along with dynamic VRP entries (learned from local cache servers using the RPKI-Router protocol) in the origin validation database of the router. This database is used for determining the origin-validation state of IPv4 and/or IPv6 BGP routes received over sessions with the enable-origin-validation command configured.

Static entries can only be configured under the config>router>origin-validation context of the base router.

Parameters

ip-prefix/ip-prefix-length

Specifies an IPv4 or IPv6 address with a minimum prefix length value.

Values

60 to 3600

prefix-length2

Specifies the maximum prefix length.

Values

1 to 128

as-number

Specifies as-number.

Values

0 to 4294967295

valid

Specifies a keyword meaning the static entry expresses a valid combination of origin AS and prefix range.

invalid

Specifies a keyword meaning the static entry expresses an invalid combination of origin AS and prefix range.

Platforms

All

static-function

static-function

Syntax

static-function

Context

[Tree] (config>router>segment-routing>srv6>locator static-function)

Full Context

configure router segment-routing segment-routing-v6 locator static-function

Description

Commands in this context configure the function field parameters of a static End, End.X, or service SID assignment.

Platforms

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

static-function

Syntax

static-function

Context

[Tree] (conf>router>sr>srv6>ms>block static-function)

Full Context

configure router segment-routing segment-routing-v6 micro-segment block static-function

Description

Commands in this context configure the function field parameters of a static uA or service micro-segment assignment.

Platforms

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

static-host

static-host

Syntax

static-host ip ip-prefix[/prefix-length] [mac ieee-address] [create]

no static-host ip ip-prefix[/prefix-length] [mac ieee-address]

no static-host all [force]

no static-host ip ip-prefix[/prefix-length]

Context

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

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

Full Context

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

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

Description

This command creates a static subscriber host for the SAP. Static subscriber hosts may be used by the system for various purposes. Applications within the system that make use of static host entries include anti-spoof, ARP reply agent and source MAC population into the VPLS forwarding database.

Multiple static hosts may be defined on the SAP. Each host is identified by either a source IP address, a source MAC address or both a source IP and source MAC address. Every static host definition must have at least one address defined, IP or MAC.

Static hosts can exist on the SAP even with anti-spoof and ARP reply agent features disabled. When enabled, each feature has different requirements for static hosts.

The no form of this command removes a static entry from the system. The specified ip-address and mac-address must match the host’s exact IP and MAC addresses as defined when it was created. When a static host is removed from the SAP, the corresponding anti-spoof filter entry and/or FDB entry is also removed.

Parameters

ip-prefix[/prefix-length

Specifies information for the specified IP address and mask.

mac-address

Specifies a MAC address. The MAC address must be specified for anti-spoof mac, and anti-spoof ip-mac and arp-reply-agent (arp-reply-agent is supported by the 7450 ESS only). Multiple static hosts may be configured with the same MAC address given that each definition is distinguished by a unique IP address.

Every static host definition must have at least one address defined, IP or MAC.

force

Specifies the forced removal of the static host addresses.

create

Keyword used to create the static host instance. 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

static-host

Syntax

static-host ip ip-address [mac ieee-address] [create]

static-host mac ieee-address [create]

no static-host ip ip-address mac ieee-address

no static-host all [force]

no static-host ip ip-address

Context

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

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

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

Full Context

configure service ies interface sap static-host

configure service vprn interface sap static-host

configure service vpls sap static-host

Description

This command creates a static subscriber host for the SAP. Static subscriber hosts may be used by the system for various purposes. Applications within the system that make use of static host entries include anti-spoof, ARP reply agent and source MAC population into the VPLS forwarding database.

Multiple static hosts may be defined on the SAP. Each host is identified by either a source IP address, a source MAC address or both a source IP and source MAC address. Every static host definition must have at least one address defined, IP or MAC.

Static hosts can exist on the SAP even with anti-spoof and ARP reply agent features disabled. When enabled, each feature has different requirements for static hosts.

The no form of this command removes a static entry from the system. The specified ip-address and mac-address must match the host’s exact IP and MAC addresses as defined when it was created. When a static host is removed from the SAP, the corresponding anti-spoof filter entry and/or FDB entry is also removed.

Parameters

ip-address

Specify this optional parameter when defining a static host. The IP address must be specified for anti-spoof ip, anti-spoof ip-mac and arp-reply-agent (arp-reply-agent is supported by the 7450 ESS only). Only one static host may be configured on the SAP with a given IP address.

mac-address

Specify this optional parameter when defining a static host. The MAC address must be specified for anti-spoof mac, and anti-spoof ip-mac and arp-reply-agent (arp-reply-agent is supported by the 7450 ESS only). Multiple static hosts may be configured with the same MAC address given that each definition is distinguished by a unique IP address.

Every static host definition must have at least one address defined, IP or MAC.

force

Specifies the forced removal of the static host addresses.

create

Keyword used to create the static host instance. 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

static-host-mgmt

static-host-mgmt

Syntax

static-host-mgmt

Context

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

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

Full Context

configure service ies subscriber-interface group-interface sap static-host-mgmt

configure service vprn subscriber-interface group-interface sap static-host-mgmt

Description

Commands in this context configure common parameters for static hosts.

Platforms

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

static-isid

static-isid

Syntax

static-isid

Context

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

[Tree] (config>service>vpls>sap static-isid)

Full Context

configure service vpls spoke-sdp static-isid

configure service vpls sap static-isid

Description

This command configures the static-isid context.

Platforms

All

static-label-range

static-label-range

Syntax

static-label-range static-range

no static-label-range

Context

[Tree] (config>router>mpls-labels static-label-range)

Full Context

configure router mpls-labels static-label-range

Description

This command configures the range of MPLS static label values shared among static LSP, MPLS-TP LSP, and static service VC label. Once this range is configured, it is reserved and cannot be used by other protocols such as RSVP, LDP, BGP, or Segment Routing to assign a label dynamically.

Default

static-label-range 18400

Parameters

static-range

Specifies the size of the static label range in number of labels. The minimum label value in the range is 32. The maximum label value is therefore computed as {32+ static-range-1}.

Values

0 to 262112

Default

18400

Platforms

All

static-lsp

static-lsp

Syntax

[no] static-lsp lsp-name

Context

[Tree] (config>router>mpls static-lsp)

Full Context

configure router mpls static-lsp

Description

This command is used to configure a static LSP on the ingress router. The static LSP is a manually set up LSP where the nexthop IP address and the outgoing label (push) must be specified.

The no form of this command deletes this static LSP and associated information.

The LSP must be shutdown first in order to delete it. If the LSP is not shut down, the no static-lsp lsp-name command does nothing except generate a warning message on the console indicating that the LSP is administratively up.

Parameters

lsp-name

Specifies the name that identifies the LSP.

Values

Up to 32 alphanumeric characters.

Platforms

All

static-lsp-fast-retry

static-lsp-fast-retry

Syntax

static-lsp-fast-retry seconds

no static-lsp-fast-retry

Context

[Tree] (config>router>mpls static-lsp-fast-retry)

Full Context

configure router mpls static-lsp-fast-retry

Description

This command specifies the value used as the fast retry timer for a static LSP.

When a static LSP is trying to come up, the MPLS request for the ARP entry of the LSP next-hop may fail when it is made while the next-hop is still down or unavailable. In that case, MPLS starts a retry timer before making the next request. This enhancement allows the user to configure the retry timer, so that the LSP comes up as soon as the next-hop is up.

The no form of this command reverts to the default.

Default

no static-lsp-fast-retry

Parameters

seconds

Specifies the value (in s), used as the fast retry timer for a static LSP.

Values

1 to 30

Platforms

All

static-mac

static-mac

Syntax

static-mac ieee-mac-address [create]

no static-mac ieee-mac-address

Context

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

[Tree] (config>service>vpls>sap static-mac)

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

Full Context

configure service vpls mesh-sdp static-mac

configure service vpls sap static-mac

configure service vpls spoke-sdp static-mac

Description

This command creates a remote static MAC entry in the Virtual Private LAN Service (VPLS) forwarding database (FDB) associated with the service destination point (SDP).

In a VPLS service, MAC addresses are associated with a SAP or with an SDP. MACs associated with a SAP are classified as local MACs, and MACs associated with an SDP are remote MACs.

Local and remote static MAC entries create a permanent MAC address to SDP association in the forwarding database for the VPLS instance so that MAC address is not learned on the edge device.

Note:

Static MAC definitions on one edge device are not propagated to other edge devices participating in the VPLS instance, that is, each edge device has an independent forwarding database for the VPLS.

Only one static MAC entry (local or remote) can be defined per MAC address per VPLS instance.

By default, no static MAC address entries are defined for the SDP.

The no form of this command deletes the static MAC entry with the specified MAC address associated with the SDP from the VPLS forwarding database.

Parameters

ieee-mac-address

Specifies the 48-bit MAC address for the static ARP in the form aa:bb:cc:dd :ee:ff or aa-bb-cc-dd -ee-ff where aa, bb, cc, dd, ee and ff are hexadecimal numbers. Allowed values are any non-broadcast, non-multicast MAC and non-IEEE reserved MAC addresses.

create

Keyword used to create the static MAC instance. The create keyword requirement can be enabled or disabled in the environment>create context.

Platforms

All

static-mac

Syntax

static-mac

Context

[Tree] (config>service>vpls static-mac)

Full Context

configure service vpls static-mac

Description

A set of conditional static MAC addresses can be created within a VPLS supporting BGP-EVPN. Conditional Static Macs are also supported in B-VPLS with SPBs. Unless they are configured as black-hole, conditional Static Macs are dependent on the SAP/SDP state.

This command allows the assignment of a set of conditional Static MAC addresses to a SAP/ spoke-SDP or black-hole. In the FDB, the static MAC is then associated with the active SAP or spoke-SDP.

When configured in conjunction with SPBM services, Static MACs are used for PBB Epipe and I-VPLS services that may terminate external to SPBM. If this is configured under a Control B-VPLS the interface referenced will not use IS-IS for this neighbor. This may also be configured under a User B-VPLS where the corresponding interface is not supported under the Control B-VPLS.

Static MACs configured in a BGP-EVPN service are advertised as protected (EVPN will signal the MAC as protected).

Platforms

All

static-mac

Syntax

static-mac

Context

[Tree] (config>service>vpls>interface static-mac)

Full Context

configure service vpls interface static-mac

Description

A set of conditional static MAC addresses can be created within a VPLS supporting bgp-evpn. Conditional static macs are also supported in B-VPLS with SPBM. Conditional Static MACs are dependent on the SAP/SDP state.

This command allows assignment of a set of conditional static MAC addresses to a SAP/ spoke-SDP. In the FDB, the static MAC is then associated with the active SAP or spoke-SDP.

Static MACs are used for PBB Epipe and I-VPLS services that may terminate external to SPBM. If this is configured under a Control B-VPLS the interface referenced will not use IS-IS for this neighbor. This may also be configured under a User B-VPLS where the corresponding interface is not supported under the Control B-VPLS.

Static MACs configured in a bgp-evpn service are advertised as protected (EVPN will signal the mac as protected).

Platforms

All

static-mac

Syntax

static-mac ieee-address [create]

no static-mac ieee-address

Context

[Tree] (config>service>vpls>endpoint static-mac)

Full Context

configure service vpls endpoint static-mac

Description

This command assigns a static MAC address to the endpoint. In the FDB, the static MAC is then associated with the active spoke-SDP.

Parameters

ieee-address

Specifies the static MAC address to the endpoint

Values

6-byte mac-address (xx:xx:xx:xx:xx:xx or xx-xx-xx-xx-xx-xx) Cannot be all zeros

create

This keyword is mandatory while creating a static MAC

Platforms

All

static-policer

static-policer

Syntax

[no] static-policer policer-name [create]

Context

[Tree] (config>sys>security>dist-cpu-protection>policy static-policer)

Full Context

configure system security dist-cpu-protection policy static-policer

Description

Configures a static enforcement policer that can be referenced by one or more protocols in the policy. Once this policer-name is referenced by a protocol, then this policer will be instantiated for each object (for example, a SAP or network interface) that is created and references this policy. If there is no policer resource available on the associated card or fp then the object is be blocked from being created. Multiple protocols can use the same static-policer.

Parameters

policy-name

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

Platforms

All

static-policy

static-policy

Syntax

static-policy name [ create]

no static-policy name

Context

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

Full Context

configure router segment-routing sr-policies static-policy

Description

This command creates a context to configure a segment routing policy. The resulting segment routing policy is targeted for local installation or propagation by BGP to another router.

The no form of this command deletes the statically defined segment routing policy.

Default

no static-policy

Parameters

name

Specifies the name assigned to the statically defined segment routing policy, up to 64 characters.

create

Keyword used to create the policy.

Platforms

All

static-policy-mpls

static-policy-mpls

Syntax

static-policy-mpls policy-name

no static-policy-mpls

Context

[Tree] (config>service>vprn>mvpn>pt>selective>p2mp-sr static-policy-mpls)

[Tree] (config>service>vprn>mvpn>pt>selective>multistream-spmsi static-policy-mpls)

[Tree] (config>service>vprn>mvpn>pt>inclusive>p2mp-sr static-policy-mpls)

Full Context

configure service vprn mvpn provider-tunnel selective p2mp-sr static-policy-mpls

configure service vprn mvpn provider-tunnel selective multistream-spmsi static-policy-mpls

configure service vprn mvpn provider-tunnel inclusive p2mp-sr static-policy-mpls

Description

This command assigns the specified static policy to the MVPN tunnel.

The no form of this command removes the static policy from the MVPN tunnel.

Default

no static-policy-mpls

Parameters

policy-name

Specifies the policy name, up to 32 characters.

Platforms

All

static-remote-aa-sub

static-remote-aa-sub

Syntax

static-remote-aa-sub transit-aasub-name

static-remote-aa-sub transit-aasub-name app-profile app-profile-name [create]

no static-remote-aa-sub transit-aasub-name

Context

[Tree] (config>app-assure>group>transit-prefix-policy static-remote-aa-sub)

Full Context

configure application-assurance group transit-prefix-policy static-remote-aa-sub

Description

This command configures static remote transit aa-subs with a name and an app-profile. Remote transit subscribers are configured for sites on the opposite side of the system as the parent SAP/spoke- SDP. A new remote transit sub with both a name and an app-profile is configured with the create command. Static remote transit aa-subs must have an explicitly assigned app-profile. An existing remote transit sub can optionally be assigned a different app-profile.

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

Parameters

transit-aasub-name

Specifies a transit aasub-name up to 32 characters.

app-profile-name

Specifies the name of an existing application profile up to 32 characters.

create

Keyword used to create a new app-profile entry.

Platforms

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

static-route

static-route

Syntax

[no] static-route route-name

Context

[Tree] (config>service>pw-routing static-route)

Full Context

configure service pw-routing static-route

Description

This command configures a static route to a next hop S-PE or T-PE. Static routes may be configured on either S-PEs or T-PEs.

A default static route is entered as follows:

static-route 0:0:next_hop_ip_addresss

or

static-route 0:0.0.0.0:next_hop_ip_address

The no form of this command removes a previously configured static route.

Parameters

route-name

Specifies the static pseudowire route.

Values

route-name

<global-id>:<prefix>:<next-hop-ip_addr>

global-id

0 to 4294967295

prefix

a.b.c.d | 0 to 4294967295

next-hop-ip_addr

a.b.c.d

Platforms

All

static-route

Syntax

[no] static-route ip-prefix/ip-prefix-length next-hop ip-address

Context

[Tree] (bof static-route)

Full Context

bof static-route

Description

This command creates a static route entry for the CPM management Ethernet port in the running configuration and the Boot Option File (BOF).

This command allows manual configuration of static routing table entries. These static routes are only used by traffic generated by the CPM Ethernet port. To reduce configuration, manual address aggregation should be applied where possible.

A maximum of 10 static routes can be configured on the CPM port.

The no form of this command deletes the static route.

Default

no static-route

Parameters

ip-prefix/ip-prefix-length

Specifies the destination address of the static route in dotted decimal notation.

Values

ip-prefix/ip-prefix-length

ipv4-prefix

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

ipv4-prefix-le

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

d: [0to 255]D

ipv6-prefix-le

0 to128

ip-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

Note:

IPv6 is applicable to the 7750 SR and 7950 XRS only.

mask

Specifies the subnet mask, expressed as an integer or in dotted decimal notation.

Values

1 to 32 (mask length), 128.0.0.0 to255.255.255.255 (dotted decimal)

ip-address

Specifies the next hop IP address used to reach the destination.

Platforms

All

static-route-entry

static-route-entry

Syntax

static-route-entry ip-prefix/prefix-length [mcast]

no static-route-entry ip-prefix/prefix-length [mcast]

Context

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

Full Context

configure service vprn static-route-entry

Description

This command creates a static route entry for both the network and access routes. A prefix and netmask must be specified.

Once the static route context for the specified prefix and netmask has been created, additional parameters associated with the static route(s) may be specified through the inclusion of additional static-route parameter commands.

The no form of this command deletes the static route entry. If a static route needs to be removed when multiple static routes exist to the same destination, then as many parameters to uniquely identify the static route must be entered.

IPv6 static routes are not supported on the 7450 ESS except in mixed mode.

Default

No static routes are defined.

Parameters

ip-prefix/prefix-length

The destination address of the static route.

Values

The following values apply to the 7750 SR and 7950 XRS:

ipv4-prefix

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

ipv4-prefix-length

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

d: [0 to 255]D

ipv6-prefix-length

0 to 128

Values

The following values apply to the 7450 ESS:

ipv4-prefix

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

ipv4-prefix-length

0 to 32

mcast

Specifies that the associated static route should be populated in the associated VPRN multicast route table.

Platforms

All

static-route-entry

Syntax

[no] static-route-entry ip-prefix/prefix-length [mcast]

Context

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

Full Context

configure router static-route-entry

Description

This command creates a static route entry for both the network and access routes. A prefix and netmask must be specified.

After the static route context for the specified prefix and netmask has been created, additional parameters associated with the static routes may be specified through the inclusion of additional static route parameter commands.

The no form of this command deletes the static route entry. If a static route needs to be removed when multiple static routes exist to the same destination, then as many parameters to uniquely identify the static route must be entered.

Default

No static routes are defined.

Parameters

ip-prefix/prefix-length

Specifies the destination address of the static route.

Values

The following values apply to the 7750 SR and 7950 XRS:

ipv4-prefix

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

ipv4-prefix-length

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

d

[0 to 255]D

ipv6-prefix-length

0 to 128

Values

The following values apply to the 7450 ESS:

ipv4-prefix

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

ipv4-prefix-length

0 to 32

ip-address

Specifies the IP address of the IP interface. The ip-addr portion of the address command specifies the IP host address that will be used by the IP interface within the subnet. This address must be unique within the subnet and specified in dotted decimal notation.

Values

The following values apply to the 7750 SR and 7950 XRS:

ipv4-address

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

ipv6-address

x:x:x:x:x:x:x:x[-interface]

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

x: [0..FFFF]H

d: [0..255]D

interface: 32 characters maximum, mandatory for link local addresses

Values

The following value applies to the 7450 ESS:

ipv4-address

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

mcast

Indicates that static route being configured is used for multicast table only.

Platforms

All

static-route-hold-down

static-route-hold-down

Syntax

static-route-hold-down initial initial multiplier multiplier max-value max-value

no static-route-hold-down

Context

[Tree] (config>router static-route-hold-down)

Full Context

configure router static-route-hold-down

Description

This command enables the hold down time feature globally for static routes in the system.

The static route hold-down time is a mechanism to protect from rapid, fluctuating state changes of static routes resulting from issues with reachability because of link flap.

This command applies to all static routes in the VPRN and the base router instance in which this hold-down time is configured.

The no form of this command disables the hold down time feature globally for static routes in the system.

Default

no static-route-hold-down

Parameters

initial

Specifies the initial value of the hold down time, in seconds, globally for static routes in the system.

Values

1 to 65535

multiplier

Specifies the multiplier value of the hold down time feature globally for static routes in the system.

Values

1 to 10

max-value

Specifies the maximum value of the hold down time, in seconds, globally for static routes in the system.

Values

1 to 65535

Platforms

All

static-sa

static-sa

Syntax

static-sa sa-name [create]

no static-sa sa-name

Context

[Tree] (config>ipsec static-sa)

Full Context

configure ipsec static-sa

Description

This command configures an IPsec static SA.

Platforms

All

static-string

static-string

Syntax

static-string static-string

no static-string

Context

[Tree] (config>app-assure>group>http-enrich>field static-string)

Full Context

configure application-assurance group http-enrich field static-string

Description

This command configures an HTTP header enrichment template field static string.

The no form of this command removes the template field static string.

Default

no static-string

Parameters

static-string

Specifies a static string.

Platforms

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

static-tunnel-redundant-next-hop

static-tunnel-redundant-next-hop

Syntax

static-tunnel-redundant-next-hop ip-address

no static-tunnel-redundant-next-hop

Context

[Tree] (config>service>vprn>if static-tunnel-redundant-next-hop)

[Tree] (config>service>ies>if static-tunnel-redundant-next-hop)

Full Context

configure service vprn interface static-tunnel-redundant-next-hop

configure service ies interface static-tunnel-redundant-next-hop

Description

This command specifies redundant next-hop address on public or private IPsec interface (with public or private tunnel-sap) for static IPsec tunnel. The specified next-hop address will be used by standby node to shunt traffic to master in case of it receives them. Refer to the 7450 ESS, 7750 SR, and VSR Multiservice Integrated Service Adapter and Extended Services Appliance Guide for information about IPsec commands and descriptions.

The next-hop address will be resolved in routing table of corresponding service.

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

Parameters

ip-address

Specifies the static ISA tunnel redundant next-hop address.

Platforms

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

station

station

Syntax

station station-name [create]

no station station-name

Context

[Tree] (config>bmp station)

Full Context

configure bmp station

Description

The command configures the BMP monitoring station name.

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

Parameters

station-name

Specifies the station name of the BMP monitoring station up to 32 characters.

create

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

Platforms

All

station

Syntax

station all

station name [name]

no station

Context

[Tree] (config>service>vprn>bgp>group>monitor station)

[Tree] (config>router>bgp>group>monitor station)

[Tree] (config>router>bgp>monitor station)

[Tree] (config>router>bgp>group>neighbor>monitor station)

[Tree] (config>service>vprn>bgp>group>neighbor>monitor station)

Full Context

configure service vprn bgp group monitor station

configure router bgp group monitor station

configure router bgp monitor station

configure router bgp group neighbor monitor station

configure service vprn bgp group neighbor monitor station

Description

This command configures the set of BMP monitoring stations for which BMP messages are to be sent, at the global BGP instance level, per group or for a particular neighbor.

Whatever value is configured for the station parameter at the most specific BGP hierarchy level is used.

  • If a station list or the no station command is configured at a neighbor context, then that value is used.

  • If no station command is configured at the neighbor context, the group value is used.

  • If a station list or the no station command is configured at a group context, then that value is used.

  • If no station command is configured at the group context, the global value is used.

  • If a station list or the no station command is configured at the global context, then that value is used.

  • If no station command is configured at the global context, then a no station is assumed.

The no form of this command disables sending BMP messages to BMP monitoring stations.

Parameters

name

Specifies up to eight station names up to 32 characters. Allowed values are any string up to 32 characters long composed of printable,7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.

all

Specifies all configured stations.

Platforms

All

station-address

station-address

Syntax

station-address ip-address | ipv6-address port port

no station-address

Context

[Tree] (config>bmp>station>connection station-address)

Full Context

configure bmp station connection station-address

Description

This command configures the IP address and TCP port number of the remote BMP monitoring station. This is a mandatory parameter and must be configured before the associated station can transitioned out of the shut down state.

The no form of this command removes the configured station IP address and port number for the BMP session. The no station-address command cannot be accepted unless the BMP or station instance is shut down.

Parameters

ip-address

Specifies the station address expressed in dotted decimal notation. Allowed value is a valid routable IP address on the router, either an interface or system IP address.

Values

ipv4-address:

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

ipv6-address

Specifies the station address expressed in dotted decimal notation. Allowed value is a valid routable IPv6 address on the router, either an interface or system 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

port

Specifies the TCP (destination) port number to be used when establishing the connection to the associated BMP station.

Values

1 to 65535

Platforms

All

statistic

statistic

Syntax

statistic type type name name

no statistic

Context

[Tree] (debug>wlan-gw>group statistic)

Full Context

debug wlan-gw group statistic

Description

This command enables debugging of the specified statistic. The first packet that causes an increase of the specified statistic is shown in debug output. After the first packet, debugging of the counter is stopped.

Parameters

type

Displays the type of statistic to be debugged; for example, DHCP or RADIUS.

Values

packet-errors, host-errors, bd-errors, forwarding, reassembly, aa, radius, arp, dhcp, dhcp6, icmp, icmp6

name

Specifies the name, up to 256 characters, of the statistic within that group. For a complete list, see the command show isa wlan-gw-group wlan-gw-group-id member member-id statistics.

Platforms

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

statistics

statistics

Syntax

statistics

Context

[Tree] (config>app-assure>group statistics)

Full Context

configure application-assurance group statistics

Description

Commands in this context configure accounting and billing statistics for this AA ISA group.

Platforms

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

statistics

Syntax

statistics

Context

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

Full Context

configure isa application-assurance-group statistics

Description

Commands in this context configure statistics generation.

Platforms

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

stats-collection

stats-collection

Syntax

stats-collection

Context

[Tree] (config>isa>tunnel-grp stats-collection)

Full Context

configure isa tunnel-group stats-collection

Description

Commands in this context configure ISA statistics collection parameters.

Platforms

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

stats-report-interval

stats-report-interval

Syntax

stats-report-interval [seconds]

no stats-report-interval

Context

[Tree] (config>bmp>station stats-report-interval)

Full Context

configure bmp station stats-report-interval

Description

This command configures the frequency of sending statistics reporting messages to the BMP monitoring station.

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

Parameters

seconds

Specifies the frequency of sending statistics reporting messages, in seconds, to the BMP monitoring station.

Values

15 to 65535

Platforms

All

stats-type

stats-type

Syntax

stats-type {time | volume-time}

no stats-type

Context

[Tree] (config>service>dynsvc>acct-2 stats-type)

[Tree] (config>service>dynsvc>acct-1 stats-type)

Full Context

configure service dynamic-services dynamic-services-policy accounting-2 stats-type

configure service dynsvc acct-1 stats-type

Description

This command configures the type of statistics to be reported in dynamic data services RADIUS accounting. A RADIUS specified Stats Type overrides the CLI configured value.

The no form of this command resets the default value.

Default

stats-type volume-time

Parameters

time

Only report Session-Time in the RADIUS Accounting Interim-Update and Stop message.

volume-time

Report both Session-Time and Volume counter attributes in the RADIUS. Accounting Interim-Update and Stop messages.

Platforms

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

stats-type

Syntax

stats-type {volume-time | time}

no stats-type

Context

[Tree] (config>service>dynsvc>ladb>user>idx>acct stats-type)

Full Context

configure service dynamic-services local-auth-db user-name index accounting stats-type

Description

This command specifies whether dynamic service accounting should be enabled or disabled for this destination. RADIUS accounting is enabled by specifying the stats type: volume and time or time only. This command overrides the local configured value in the dynamic services policy.

The no form of this command disables RADIUS accounting (stats-type off).

Parameters

volume-time | time

Enables RADIUS accounting for this dynamic service and specifies if volume counters should be included (volume-time) or time only (time) in the RADIUS accounting messages.

Platforms

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

status-verify

status-verify

Syntax

status-verify

Context

[Tree] (config>service>vprn>if>sap>ipsec-gw>cert status-verify)

[Tree] (config>router>if>ipsec>ipsec-tun>dyn>cert status-verify)

[Tree] (config>service>ies>if>sap>ipsec-gw>cert status-verify)

[Tree] (config>service>ies>if>ipsec>ipsec-tunnel>dyn>cert status-verify)

[Tree] (config>service>vprn>if>ipsec>ipsec-tunnel>dyn>cert status-verify)

[Tree] (config>ipsec>trans-mode-prof>dyn>cert status-verify)

[Tree] (config>service>vprn>if>sap>ipsec-tun>dyn>cert status-verify)

Full Context

configure service vprn interface sap ipsec-gw cert status-verify

configure router interface ipsec ipsec-tunnel dynamic-keying cert status-verify

configure service ies interface sap ipsec-gw cert status-verify

configure service ies interface ipsec ipsec-tunnel dynamic-keying cert status-verify

configure service vprn interface ipsec ipsec-tunnel dynamic-keying cert status-verify

configure ipsec ipsec-transport-mode-profile dynamic-keying cert status-verify

configure service vprn interface sap ipsec-tunnel dynamic-keying cert status-verify

Description

Commands in this context configure Certificate Status Verification (CSV) parameters.

Platforms

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

  • configure service vprn interface sap ipsec-gw cert status-verify
  • configure service vprn interface sap ipsec-tunnel dynamic-keying cert status-verify
  • configure ipsec ipsec-transport-mode-profile dynamic-keying cert status-verify
  • configure service ies interface sap ipsec-gw cert status-verify

VSR

  • configure router interface ipsec ipsec-tunnel dynamic-keying cert status-verify
  • configure service vprn interface ipsec ipsec-tunnel dynamic-keying cert status-verify
  • configure service ies interface ipsec ipsec-tunnel dynamic-keying cert status-verify

status-verify

Syntax

status-verify default-result {revoked | good}

no status-verify

Context

[Tree] (config>system>security>tls>server-tls-profile status-verify)

[Tree] (config>system>security>tls>client-tls-profile status-verify)

Full Context

configure system security tls server-tls-profile status-verify

configure system security tls client-tls-profile status-verify

Description

This command configures the certificate revocation status verification parameters for end-entity (EE) certificates in the TLS client or server. This configuration overrides the existing revocation check policy.

By default the router checks the certification revocation status, but if this command is set to good, the end-entity certificate revocation status is overwritten and a good revocation status is returned for the EE certificate.

If this command is set to revoked, the router returns the actual revocation status of the end-entity certificate.

The no form of this command returns the actual revocation status to that of the end entity certificate.

Default

status-verify default-result revoked

Parameters

good

Specifies that the certificate is considered acceptable.

revoked

Specifies that the certificate is considered revoked.

Platforms

All

std-acct-attributes

std-acct-attributes

Syntax

[no] std-acct-attributes

Context

[Tree] (config>subscr-mgmt>acct-plcy>include-radius-attribute std-acct-attributes)

Full Context

configure subscriber-mgmt radius-accounting-policy include-radius-attribute std-acct-attributes

Description

This command enables reporting of aggregated forwarded IPv4 and IPv6 octet, packet and gigaword counters using standard RADIUS attributes. This attribute is by default. It can be enabled simultaneously with detailed per queue or policer counters (detailed-acct-attributes).

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

std-port-class-pools

std-port-class-pools

Syntax

std-port-class-pools

Context

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

Full Context

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

Description

Commands in this context configure standard port-class pools parameters. Within this context, the corresponding port-class pools can be associated with a mid-pool, explicitly sized as a percentage of the mid-pool size, dynamically-sized based on relative port bandwidth, or have a slope policy applied.

Platforms

7750 SR-7/12/12e

steering-profile

steering-profile

Syntax

steering-profile steering-profile-name

no steering-profile

Context

[Tree] (config subscr-mgmt loc-user-db ppp host steering-profile)

Full Context

configure subscriber-mgmt local-user-db ppp host steering-profile

Description

This command configures the steering profile for the specific host.

The no form of this command removes the steering profile for the host.

Parameters

steering-profile-name

Specifies the name of the steering profile, up to 32 characters.

Platforms

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

steering-profile

Syntax

steering-profile steering-profile-name [create]

no steering-profile steering-profile-name

Context

[Tree] (config subscr-mgmt steering-profile)

Full Context

configure subscriber-mgmt steering-profile

Description

This command configures a steering profile mapping. A steering profile can be applied to each L2TP LAC subscriber host that requires traffic steering.

The no form of this command removes the specified steering profile.

Parameters

steering-profile-name

Specifies the name of the steering profile, up to 32 characters.

Platforms

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

steering-profile

Syntax

[no] steering-profile

Context

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

Full Context

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

Description

This command enables including the Alc-Steering-Profile RADIUS attribute.

The no form of the command disables including the Alc-Steering-Profile RADIUS attribute.

Platforms

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

steering-route

steering-route

Syntax

steering-route ip-prefix/length

no steering-route

Context

[Tree] (config>service>vprn>nat>inside>redundancy steering-route)

Full Context

configure service vprn nat inside redundancy steering-route

Description

This command configures specifies the IP address and prefix length of the steering route. The steering route is used in the realm of this virtual router instance as an indirect next-hop for all the traffic that must be routed to the large scale NAT function.

Platforms

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

steering-route

Syntax

steering-route ip-prefix/length

no steering-route

Context

[Tree] (config>router>nat>inside>redundancy steering-route)

Full Context

configure router nat inside redundancy steering-route

Description

This command is optionally used in LSN44 multi-chassis redundancy when filters are used on the inside to send traffic destined for the LSN44 function to MS-ISA, where NAT is performed.

If configured, the steering-route is advertised only from the active LSN44 node: the purpose is to bring the LSN44 node activity awareness to downstream routers. In this fashion, downstream routers can make a more intelligent decision when forwarding traffic in the upstream direction. Based on the steering-route, traffic can be sent directly towards the active LSN44 node. This route avoids an extra forwarding hop which would ensue in the case without LSN44 activity awareness, where the upstream traffic can be forwarded to the standby LSN44 node and then to the active LSN44 node.

LSN44 node activity (active/standby) is evaluated per isa-group based on monitoring routes advertised on the outside.

The no form of the command removes the ip-prefix/length from the configuration.

Parameters

ip-prefix/length

Specifies the IP address and length of the steering route.

Values

ip-prefix:

a.b.c.d

ip-prefix-length:

0 to 32

Platforms

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

sticky-dest

sticky-dest

Syntax

sticky-dest hold-time-up

sticky-dest no-hold-time-up

no sticky-dest

Context

[Tree] (config>filter>ip-filter>entry sticky-dest)

[Tree] (config>filter>redirect-policy sticky-dest)

[Tree] (config>filter>mac-filter>entry sticky-dest)

[Tree] (config>filter>ipv6-filter>entry sticky-dest)

Full Context

configure filter ip-filter entry sticky-dest

configure filter redirect-policy sticky-dest

configure filter mac-filter entry sticky-dest

configure filter ipv6-filter entry sticky-dest

Description

This command configures sticky destination behavior for redundant PBR/PBF actions. Configuring sticky destination has an effect on PBR/PBF actions whether a secondary action is configured.

The hold-time-up parameter allows the operator to delay programming of a PBR/PBF action for a specified amount of time. The timer is only started when transitioning from all configured targets being down (that is, the primary target if no secondary target is configured, or both the primary and secondary targets when both are configured) to at least one target being up.

When the timer expires, the primary PBR/PBF action is programmed if its target is up. If the primary PBR/PBF target is down and a secondary PBR/PBF action has been configured and its target is up, then this secondary PBR/PBF action is programmed. In all other cases, no specific programming occurs when the timer expires.

When sticky destination is configured and the secondary PBR/PBF target is up and its associated action is programmed, it is not automatically replaced by the primary PBR/PBF action when its target transitions from down to up. In this situation, programming the primary PBR/PBF action can be forced using the activate-primary-action tools command.

Changing the value of the timer while the timer is running takes effect immediately (that is, the timer is restarted immediately using the new value).

The no form of the command disables sticky destination behavior.

Default

no sticky-dest

Parameters

hold-time-up

Specifies the initial delay in seconds. Zero is equivalent to no-hold-time-up (no delay).

Values

0 to 65535 seconds

Platforms

All

sticky-dr

sticky-dr

Syntax

sticky-dr [priority dr-priority]

no sticky-dr

Context

[Tree] (config>service>vprn>pim>if sticky-dr)

Full Context

configure service vprn pim interface sticky-dr

Description

This command enables sticky-dr operation on this interface. When enabled, the priority in PIM hellos sent on this interface when elected as the designated router (DR) is modified to the value configured in dr-priority. This is done to avoid the delays in forwarding caused by DR recovery, when switching back to the old DR on a LAN when it comes back up.

By enabling sticky-dr on this interface, it will continue to act as the DR for the LAN even after the old DR comes back up.

The no form of this command disables sticky-dr operation on this interface.

Default

no sticky-dr

Parameters

priority dr-priority

Sets the DR priority to be sent in PIM Hello messages following the election of that interface as the DR, when sticky-dr operation is enabled.

Values

1 to 4294967295

Platforms

All

sticky-dr

Syntax

sticky-dr [priority dr-priority]

no sticky-dr

Context

[Tree] (config>router>pim>interface sticky-dr)

Full Context

configure router pim interface sticky-dr

Description

This command enables sticky-dr operation on this interface. When enabled, the priority in PIM hellos sent on this interface when elected as the designated router (DR) will be modified to the value configured in dr-priority. This is done to avoid the delays in forwarding caused by DR recovery, when switching back to the old DR on a LAN when it comes back up.

By enabling sticky-dr on this interface, it will continue to act as the DR for the LAN even after the old DR comes back up.

The no form of this command disables sticky-dr operation on this interface.

Default

no sticky-dr

Parameters

priority dr-priority

Sets the DR priority to be sent in PIM Hello messages following the election of that interface as the DR, when sticky-dr operation is enabled.

Values

1 to 4294967295

Platforms

All

sticky-ecmp

sticky-ecmp

Syntax

sticky-ecmp

no sticky-ecmp

Context

[Tree] (config>router>policy-options>policy-statement>default-action sticky-ecmp)

[Tree] (config>router>policy-options>policy-statement>entry>action sticky-ecmp)

Full Context

configure router policy-options policy-statement default-action sticky-ecmp

configure router policy-options policy-statement entry action sticky-ecmp

Description

This command specifies that BGP routes matching an entry or default-action of a route policy should be tagged internally as requiring sticky ECMP behavior. When a BGP route with multiple equal-cost BGP next-hops is programmed for sticky ECMP the failure of one or more of its BGP next-hops causes only the affected traffic flows to be re-distributed to the remaining next-hops; by default (without sticky-ECMP) all flows are potentially affected, even those using a next-hop that did not fail.

Default

no sticky-ecmp

Platforms

All

sticky-msaps

sticky-msaps

Syntax

sticky-msaps [idle-timeout seconds]

no sticky-msaps

Context

[Tree] (config>subscr-mgmt>msap-policy sticky-msaps)

Full Context

configure subscriber-mgmt msap-policy sticky-msaps

Description

This command prevents MSAPs associated with the specified MSAP policy from being deleted unless a manual clear command is issued. If this command is not enabled, an MSAP is deleted when a host creation fails or when a subscriber is no longer associated with the MSAP, for example, when a subscriber ends the session. This feature is useful for an operator who wants to keep historical statistics on MSAPs. It can also speed up host creation on an MSAP since the MSAP is already created. The idle-timeout parameter allows the removal of MSAPs that are idle for longer than the specified time.

The no form of this command allows an MSAP to be deleted when a host creation fails or when a subscriber is no longer associated with the MSAP.

Default

no sticky-msaps

Parameters

seconds

Specifies the idle timeout, in seconds.

Values

5 to 604800

Platforms

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

stp

stp

Syntax

[no] stp

Context

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

Full Context

configure service vpls pbb backbone-vpls stp

Description

This command enables or disable STP through B-VPLS service.

Platforms

All

stp

Syntax

[no] stp

Context

[Tree] (config>service>vpls>pbb>bvpls stp)

Full Context

configure service vpls pbb backbone-vpls stp

Description

This command enables STP on the backbone VPLS service.

The no form of this command disables STP on the backbone VPLS service.

Platforms

All

stp

Syntax

stp

Context

[Tree] (config>service>template>vpls-sap-template stp)

[Tree] (config>service>vpls stp)

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

[Tree] (config>service>template>vpls-template stp)

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

Full Context

configure service template vpls-sap-template stp

configure service vpls stp

configure service vpls spoke-sdp stp

configure service template vpls-template stp

configure service vpls sap stp

Description

Commands in this context configure the Spanning Tree Protocol (STP) parameters. Nokia’s STP is simply the Spanning Tree Protocol (STP) with a few modifications to better suit the operational characteristics of VPLS services. The most evident change is to the root bridge election. Since the core network operating between Nokia’s service routers should not be blocked, the root path is calculated from the core perspective.

Platforms

All

stp

Syntax

[no] stp

Context

[Tree] (debug>service>id stp)

Full Context

debug service id stp

Description

Commands in this context debug STP.

The no form of the command disables debugging.

Platforms

All

stp

Syntax

stp

Context

[Tree] (config>service>pw-template stp)

Full Context

configure service pw-template stp

Description

Commands in this context configure the Spanning Tree Protocol (STP) parameters. The STP is simply the Spanning Tree Protocol (STP) with a few modifications to better suit the operational characteristics of VPLS services. The most evident change is to the root bridge election. Since the core network operating between service routers should not be blocked, the root path is calculated from the core perspective.

Platforms

All

stream-run-type

stream-run-type

Syntax

stream-run-type {sequential | parallel}

no stream-run-type

Context

[Tree] (config>test-oam>sath>svc-test stream-run-type)

Full Context

configure test-oam service-activation-testhead service-test stream-run-type

Description

This command configures the execution sequence for service streams that are run during the specified service test.

The no form of this command removes the configured run type.

Default

stream-run-type parallel

Parameters

sequential

Keyword to run the streams consecutively.

parallel

Keyword to run the streams in parallel.

Platforms

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

stream-selection

stream-selection

Syntax

[no] stream-selection

Context

[Tree] (config>isa>video-group stream-selection)

Full Context

configure isa video-group stream-selection

Description

This command specifies whether or not stream selection is enabled on this video group.

The no form of the command disables stream-selection for the group.

Default

no stream-selection

Platforms

7450 ESS, 7750 SR, 7750 SR-s

streaming

streaming

Syntax

streaming

Context

[Tree] (config>oam-pm streaming)

Full Context

configure oam-pm streaming

Description

This command specifies the context to configure the OAM-PM streaming template and its associated parameters.

Platforms

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

streaming

Syntax

streaming

Context

[Tree] (config>system>snmp streaming)

Full Context

configure system snmp streaming

Description

This command enables the proprietary SNMP request/response bundling and TCP-based transport mechanism for optimizing network management of the router nodes. In higher latency networks, synchronizing router MIBs from network management via streaming takes less time than synchronizing via classic SNMP UDP requests. Streaming operates on TCP port 1491 and runs over IPv4 or IPv6.

Platforms

All

strict

strict

Syntax

[no] strict

Context

[Tree] (config>app-assure>group>tcp-validate strict)

Full Context

configure application-assurance group tcp-validate strict

Description

This command specifies whether enforcement of TCP sequence and acknowledgment numbers is applied. If a packet does not meet the expected sequence or acknowledgment number, it is dropped.

This command should only be enabled if the expected bit error rate or packet loss is low. For example, if acknowledgments are lost before being detected by AA, the server timeouts are triggered and retransmissions occur. If strict is enabled, these retransmissions would resemble a reply attack and would be dropped by AA.

The no form of this command removes TCP sequence and acknowledgment number enforcement.

Default

no strict

Platforms

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

strict-adjacency-check

strict-adjacency-check

Syntax

[no] strict-adjacency-check

Context

[Tree] (config>service>vprn>isis strict-adjacency-check)

Full Context

configure service vprn isis strict-adjacency-check

Description

This command enables strict checking of address families (IPv4 and IPv6) for IS-IS adjacencies. When enabled, adjacencies do not come up unless both routers have exactly the same address families configured. If there is an existing adjacency with unmatched address families, it is torn down.

This command is used to prevent black-holing traffic when IPv4 and IPv6 topologies are different. When disabled (no strict-adjacency-check) a BFD session failure for either IPv4 or IPv6 will cause the routes for the other address family to be removed as well.

When disabled (no strict-adjacency-check), both routers only need to have one common address family to establish the adjacency.

Default

no strict-adjacency-check

Platforms

All

strict-adjacency-check

Syntax

[no] strict-adjacency-check

Context

[Tree] (config>router>isis strict-adjacency-check)

Full Context

configure router isis strict-adjacency-check

Description

This command enables strict checking of address families (IPv4 and IPv6) for IS-IS adjacencies. When enabled, adjacencies will not come up unless both routers have exactly the same address families configured. If there is an existing adjacency with unmatched address families, it will be torn down. This command is used to prevent black-holing traffic when IPv4 and IPv6 topologies are different. When disabled (no strict-adjacency-check) a BFD session failure for either IPv4 or Ipv6 will cause the routes for the other address family to be removed as well.

When disabled (no strict-adjacency-check), both routers only need to have one common address family to establish the adjacency.

Platforms

All

strict-ero-nhop-direct-resolution

strict-ero-nhop-direct-resolution

Syntax

[no] strict-ero-nhop-direct-resolution

Context

[Tree] (config>router>mpls strict-ero-nhop-direct-resolution)

Full Context

configure router mpls strict-ero-nhop-direct-resolution

Description

This command enables the strict Explicit Route Object (ERO) next-hop direct resolution. The feature restricts the routes used to resolve the next hop of an ERO address to local and host routes. This command avoids using a next hop over a parallel link when a half link is up in the routing table.

When enabled, this command applies to an ERO when all of the following conditions are met:

  • the ERO next hop is an IPv4 address

  • the ERO object is a strict hop

  • the IPv4 address matches the primary subnet of a local numbered interface

An ERO that meets the preceding conditions restricts resolution of the next hop to a LOCAL or a HOST route. If no such route exists, RSVP rejects the PATH message with ErrCode = Routing Error (24) and SubErrCode = Bad Strict Node (2).

The no form of this command disables the strict ERO next-hop direct resolution.

Default

no strict-ero-nhop-direct-resolution

Platforms

All

strict-esp-seq-number-ordering

strict-esp-seq-number-ordering

Syntax

[no] strict-esp-seq-number-ordering

Context

[Tree] (config>isa>tunnel-grp strict-esp-seq-number-ordering)

Full Context

configure isa tunnel-group strict-esp-seq-number-ordering

Description

This command configures the router to use strict ESP sequence number ordering.

When ESP sequence number ordering is enabled, the outbound ESP sequence number of a CHILD_SA must be in the same order as when clear packets are received by the same CHILD_SA.

The no form of this command disables strict ESP sequence number ordering.

Default

no strict-esp-seq-number-ordering

Platforms

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

strict-lsa-checking

strict-lsa-checking

Syntax

[no] strict-lsa-checking

Context

[Tree] (config>service>vprn>ospf>graceful-restart strict-lsa-checking)

[Tree] (config>service>vprn>ospf3>graceful-restart strict-lsa-checking)

Full Context

configure service vprn ospf graceful-restart strict-lsa-checking

configure service vprn ospf3 graceful-restart strict-lsa-checking

Description

This command indicates whether an OSPF restart helper should terminate graceful restart when there is a change to an LSA that would be flooded to the restarting router during the restart process.

The default OSPF behavior is to terminate a graceful restart if an LSA changes, which causes the OSPF neighbor to go down.

The no strict-lsa-checking command disables strict LSA checking.

Default

strict-lsa-checking

Platforms

All

strict-lsa-checking

Syntax

[no] strict-lsa-checking

Context

[Tree] (config>router>ospf3>graceful-restart strict-lsa-checking)

[Tree] (config>router>ospf>graceful-restart strict-lsa-checking)

Full Context

configure router ospf3 graceful-restart strict-lsa-checking

configure router ospf graceful-restart strict-lsa-checking

Description

This command indicates whether an OSPF restart helper should terminate graceful restart when there is a change to an LSA that would be flooded to the restarting router during the restart process.

The default OSPF behavior is to terminate a graceful restart if an LSA changes, which causes the OSPF neighbor to go down.

The no form of this command disables strict LSA checking.

Default

strict-lsa-checking

Platforms

All

strict-mode

strict-mode

Syntax

[no] strict-mode

Context

[Tree] (config>service>upnp>upnp-policy strict-mode)

Full Context

configure service upnp upnp-policy strict-mode

Description

This command enable UPnP strict mode. With strict-mode, system only allows changes to existing UPnP mapping if the request comes from same UPnP client.

Default

no strict-mode

Platforms

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

string

string

Syntax

string string

no string

Context

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

Full Context

configure subscriber-mgmt local-user-db ipoe host host-identification string

Description

This command specifies the string from the Nokia vendor-specific sub-option (VSO) in Option 82 to match when the LUDB is accessed using a DHCPv4 server.

Note:

This command is only used when string is configured as one of the match-list parameters.

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

Parameters

string

Specifies the VSO string of this host, up to 255 characters.

Platforms

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

string

Syntax

[no] string text

Context

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

[Tree] (config>service>vpls>sap>dhcp>option>vendor string)

[Tree] (config>subscr-mgmt>msap-policy>vpls-only>dhcp>option>vendor string)

[Tree] (config>service>ies>sub-if>grp-if>dhcp>option>vendor string)

[Tree] (config>service>vprn>sub-if>grp-if>dhcp>option>vendor string)

Full Context

configure service vprn interface dhcp option vendor-specific-option string

configure service vpls sap dhcp option vendor-specific-option string

configure subscriber-mgmt msap-policy vpls-only-sap-parameters dhcp option vendor-specific-option string

configure service ies subscriber-interface group-interface dhcp option vendor-specific-option string

configure service vprn subscriber-interface group-interface dhcp option vendor-specific-option string

Description

This command specifies the string in the Nokia vendor-specific sub-option of the DHCP relay packet.

The no form of this command reverts to the default.

Parameters

text

Specifies a string that can be any combination of ASCII characters, up to 32 characters. If spaces are used in the string, enclose the entire string in quotation marks (" ").

Platforms

All

  • configure service vpls sap dhcp option vendor-specific-option string
  • configure service vprn interface dhcp option vendor-specific-option string

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

  • configure service ies subscriber-interface group-interface dhcp option vendor-specific-option string
  • configure subscriber-mgmt msap-policy vpls-only-sap-parameters dhcp option vendor-specific-option string
  • configure service vprn subscriber-interface group-interface dhcp option vendor-specific-option string

string

Syntax

[no] string text

Context

[Tree] (config>router>if>dhcp>option>vendor-specific-option string)

Full Context

configure router interface dhcp option vendor-specific-option string

Description

This command specifies the vendor-specific sub-option string of the DHCP relay packet.

The no form of this command returns the default value.

Default

no string

Parameters

text

Specifies a string that can be any combination of ASCII characters, up to 32 characters in length. If spaces are used in the string, enclose the entire string in quotation marks (" ”).

Platforms

All

strings-from-option

strings-from-option

Syntax

strings-from-option dhcp-option-number

no strings-from-option

Context

[Tree] (config>subscr-mgmt>sub-ident-pol strings-from-option)

Full Context

configure subscriber-mgmt sub-ident-policy strings-from-option

Description

This command enables DHCPv4 option processing on DHCP ACK for subscriber host identification.

The parameter dhcp-option-number specifies the DHCPv4 option number containing subscriber host identification strings such as subscriber ID, sub-profile, sla-profile strings, and so on. The identification strings can be inserted by an SR OS based DHCPv4 server via a local user database lookup.

Applicable to DHCPv4 hosts and PPP hosts that use the internal DHCP client to get an IPv4 address from an SR OS based DHCPv4 server.

The no form of this command reverts to the default.

Default

no strings-from-option

Parameters

dhcp-option-number

Specifies the DHCPv4 option number containing subscriber host identification strings.

Values

1 to 254

Platforms

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

strip-label

strip-label

Syntax

[no] strip-label

Context

[Tree] (config>router>if strip-label)

Full Context

configure router interface strip-label

Description

This command forces packets to be stripped of all (max 5) MPLS labels before the packets are handed over for possible filter (PBR) processing.

If the packets do not have an IP header immediately following the MPLS label stack after the strip, they are discarded. Only MPLS encapsulated IP, IGP shortcuts and VPRN over MPLS packets will be processed. However, IPv4 and IPv6 packets that arrive without any labels are supported on an interface with strip-label enabled.

This command operates in promiscuous mode. This means that the router does not filter on the destination MAC address of the Ethernet frames. In some network designs, multiple ports may be tapped and combined into interface toward the router. Promiscuous mode allows all of these flows to be processed without requiring the destination MAC address to be updated to match the router address.

This command is supported on:

  • Optical ports for the 7750 SR and 7450 ESS

  • Null/Dot1q encaps

  • Network ports

  • IPv4

  • IPv6

In order to associate an interface that is configured with the strip-label parameter with a port, the port must be configured as single-fiber for the command to be valid.

Packets that are subject to the strip-label action and are mirrored (using mirrors or lawful interception) will contain the original MPLS labels (and other L2 encapsulation) in the mirrored copy of the packet, as they appeared on the wire, when the mirror-dest type is the default type "ether”. If the mirror-dest type is "ip-only”, then the mirrored copy of the packet will not contain the original L2 encapsulation or the stripped MPLS labels.

The no form of this command removes the strip-label command.

Default

no strip-label

Platforms

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

strip-srv6-tlvs

strip-srv6-tlvs

Syntax

[no] strip-srv6-tlvs

Context

[Tree] (config>router>bgp>group>neighbor>srv6>route>family strip-srv6-tlvs)

[Tree] (config>router>bgp>group>srv6>route>fam strip-srv6-tlvs)

Full Context

configure router bgp group neighbor segment-routing-v6 route-advertisement family strip-srv6-tlvs

configure router bgp group segment-routing-v6 route-advertisement family strip-srv6-tlvs

Description

This command specifies that BGP routes that belong to the address family configured in the family command are advertised to peers with SRv6 TLVs removed. Locally or remotely added SRv6 TLVs can be removed.

The no form of this command configures the router not to strip SRv6 TLVs from the BGP routes advertised to peers.

Default

no strip-srv6-tlvs

Platforms

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

stub

stub

Syntax

[no] stub

Context

[Tree] (config>service>vprn>ospf3>area stub)

[Tree] (config>service>vprn>ospf>area stub)

Full Context

configure service vprn ospf3 area stub

configure service vprn ospf area stub

Description

This command enables access to the context to configure an OSPF stub area and adds/removes the stub designation from the area. External routing information is not flooded into stub areas. All routers in the stub area must be configured with the stub command. An OSPF area cannot be both an NSSA and a stub area. Existing virtual links of a non STUB or NSSA area will be removed when its designation is changed to NSSA or STUB.

By default, an area is not a stub area.

The no form of this command removes the stub designation and configuration context from the area.

Default

no stub — The area is not configured as a stub area.

Platforms

All

stub

Syntax

[no] stub

Context

[Tree] (config>router>ospf3>area stub)

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

Full Context

configure router ospf3 area stub

configure router ospf area stub

Description

This command enables access to the context to configure an OSPF or OSPF3 stub area and adds/removes the stub designation from the area.

External routing information is not flooded into stub areas. All routers in the stub area must be configured with the stub command. An OSPF or OSPF3 area cannot be both an NSSA and a stub area.

Existing virtual links of a non STUB or NSSA area will be removed when its designation is changed to NSSA or STUB.

By default, an area is not a stub area.

The no form of this command removes the stub designation and configuration context from the area.

Default

no stub

Platforms

All

sub-domain

sub-domain

Syntax

sub-domain sub-domain

no sub-domain

Context

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

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

Full Context

configure service vprn mvpn provider-tunnel inclusive bier sub-domain

configure service vprn mvpn provider-tunnel selective bier sub-domain

Description

This command sets the sub-domain used to attach the BIER provider tunnel. Both PMSI within the MVPN need to have the same sub-domain.

The no form of this command removes the sub-domain.

Parameters

sub-domain

The identifier of the sub-domain.

Values

0 to 255

Platforms

All

sub-domain

Syntax

[no] sub-domain sub-domain

[no] sub-domain start sub-domain end sub-domain

Context

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

Full Context

configure router bier template sub-domain

Description

This command creates a BIER sub-domain or range of sub-domains. For example, for IS-IS each sub-domain is associated with a single IS-IS topology, which may be any of the topologies supported by IS-IS.

The no form of this command removes a sub-domain.

Default

sub-domain 0

Parameters

sub-domain

The ID of the sub-domain to be created or removed.

Values

0 to 255

Platforms

All

sub-host-trk

sub-host-trk

Syntax

[no] sub-host-trk

Context

[Tree] (config>redundancy>multi-chassis>peer>sync sub-host-trk)

Full Context

configure redundancy multi-chassis peer sync sub-host-trk

Description

This command specifies whether subscriber host tracking information should be synchronized with the multi-chassis peer.

Default

no sub-host-trk

Platforms

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

sub-hosts-only

sub-hosts-only

Syntax

[no] sub-hosts-only

Context

[Tree] (config>service>vprn>igmp>grp-if sub-hosts-only)

Full Context

configure service vprn igmp group-interface sub-hosts-only

Description

This command enables the IGMP traffic from known hosts only.

The no form of this command disable the IGMP traffic from known hosts only

Platforms

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

sub-hosts-only

Syntax

[no] sub-hosts-only

Context

[Tree] (config>router>igmp>group-interface sub-hosts-only)

Full Context

configure router igmp group-interface sub-hosts-only

Description

This command disables the processing of IGMP messages outside of the subscriber-host context. No other hosts outside of the subscriber-hosts can create IGMP states.

Disabling this command allows the creation of the IGMP states that correspond to the AN that operate in IGMP proxy mode. In this mode, the AN will hide source IP addresses of IGMP messages and will source IGMP messages with its own IP address. In this case, an IGMP state can be created under the sap context. This IGMP state creation under the SAP is controlled via the import policy under the group-interface.

The IGMP state processing for regular subscriber-hosts is unaffected by this command.

The no form of the command disables the command.

Default

sub-hosts-only

Platforms

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

sub-hosts-only

Syntax

[no] sub-hosts-only

Context

[Tree] (config>router>mld>group-interface sub-hosts-only)

Full Context

configure router mld group-interface sub-hosts-only

Description

This command processes the handling of MLD joins received from hosts that are not known in subscriber management or on which no MLD policy is applied.

Disabling this command allows the creation of the MLD states that correspond to the AN that operate in MLD proxy mode. In this mode, the AN will hide source IP addresses of MLD messages and will source MLD messages with its own IP address. In this case, an MLD state can be created under the sap context. This MLD state creation under the SAP is controlled via the import policy under the group-interface.

The MLD state processing for regular subscriber-hosts is unaffected by this command.

The no form of the command enables the command.

Default

sub-hosts-only

Platforms

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

sub-id

sub-id

Syntax

[no] sub-id

Context

[Tree] (config>service>nat>syslog>syslog-export-policy>include sub-id)

Full Context

configure service nat syslog syslog-export-policy include sub-id

Description

This command includes the sub-id string in the flow log. The sub-id is applicable only in subscriber-aware NAT. If subscriber-aware NAT is not enabled, the sub-id string is set to '-'.

The no form of the command disables the feature.

Platforms

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

sub-ident-policy

sub-ident-policy

Syntax

[no] sub-ident-policy sub-ident-policy-name

Context

[Tree] (config>subscr-mgmt sub-ident-policy)

Full Context

configure subscriber-mgmt sub-ident-policy

Description

This command configures a subscriber identification policy. Each subscriber identification policy can have a default subscriber profile defined. The subscriber identification policy default subscriber profile overrides the system default and the subscriber SAP default subscriber profiles. Defining a subscriber identification policy default subscriber profile is optional.

The subscriber identification policy default subscriber profile cannot be defined with the subscriber profile name default.

Defining a subscriber profile as a subscriber identification policy default subscriber profile will cause all active subscribers currently associated with a subscriber SAP using the policy and associated with a subscriber policy through the system default or subscriber SAP default subscriber profiles to be reassigned to the subscriber policy defined as default on the subscriber identification policy.

Attempting to delete a subscriber profile that is currently defined as a default for a subscriber identification policy will fail.

When attempting to remove a subscriber identification policy default subscriber profile definition, the system will evaluate each active subscriber on all subscriber SAPs the subscriber identification policy is currently associated with that are using the default definition to determine whether the active subscriber can be either reassigned to a subscriber SAP default or the system default subscriber profile. If all active subscribers cannot be reassigned, the removal attempt will fail.

The no form of this command reverts to the default.

Parameters

sub-ident-policy-name

Specifies the name of the subscriber identification policy, up to 32 characters.

Platforms

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

sub-ident-policy

Syntax

sub-ident-policy sub-ident-policy-name

Context

[Tree] (config>service>vpls>sap>sub-sla-mgmt sub-ident-policy)

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

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

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

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

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

Full Context

configure service vpls sap sub-sla-mgmt sub-ident-policy

configure subscriber-mgmt msap-policy sub-sla-mgmt sub-ident-policy

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

configure service vprn subscriber-interface group-interface sap sub-sla-mgmt sub-ident-policy

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

configure service ies subscriber-interface group-interface sap sub-sla-mgmt sub-ident-policy

Description

This command associates a subscriber identification policy to this SAP. The subscriber identification policy must be defined prior to associating the profile with a SAP in the config>subscr-mgmt>sub-ident-policy context.

Subscribers are managed by the system through the use of subscriber identification strings such as a subscriber identifier, an sla-profile string, a sub-profile string and an app-profile string.

The subscriber identification policy performs following functions for subscriber hosts and sessions associated with the SAP or MSAP:

  • mapping of sla-profile, sub-profile and app-profile strings obtained from authentication (for example, LUDB, RADIUS, Diameter, or Python) into profile names that are configured on the router

  • for IPoE DHCPv4 hosts, the subscriber identification strings can be derived from the DHCP ACK message sent to the subscriber host using a Python script referenced in the sub-ident-policy

  • for PPPoE hosts that get an IPv4 address via the PPPoE DHCPv4 client and for IPoE DHCPv4 hosts, an SR OS DHCPv4 server in combination with an LUDB returns the identification strings in a DHCPv4 option. The strings-from-option command in the sub-ident-policy tells the system from which option to extract the identification strings.

The no form of this command removes the default subscriber identification policy from the SAP configuration.

Parameters

sub-ident-policy-name

Specifies a subscriber identification policy for this SAP.

Platforms

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

  • configure service ies subscriber-interface group-interface sap sub-sla-mgmt sub-ident-policy
  • configure service vpls sap sub-sla-mgmt sub-ident-policy
  • configure subscriber-mgmt msap-policy sub-sla-mgmt sub-ident-policy
  • configure service vprn subscriber-interface group-interface sap sub-sla-mgmt sub-ident-policy

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

  • configure service ies subscriber-interface group-interface sap-parameters sub-sla-mgmt sub-ident-policy
  • configure service vprn subscriber-interface group-interface sap-parameters sub-sla-mgmt sub-ident-policy

sub-ident-policy

Syntax

[no] sub-ident-policy policy-name

Context

[Tree] (debug>subscr-mgmt sub-ident-policy)

Full Context

debug subscriber-mgmt sub-ident-policy

Description

This command debugs subscriber identification policies.

The no form of this command disables debugging.

Parameters

policy-name

Specifies the subscriber identification policy to debug.

Platforms

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

sub-ident-policy

Syntax

sub-ident-policy sub-ident-policy-name

no sub-ident-policy

Context

[Tree] (config>app-assure>group>transit-ip-policy sub-ident-policy)

Full Context

configure application-assurance group transit-ip-policy sub-ident-policy

Description

This command associates a subscriber identification policy to this SAP. The subscriber identification policy must be defined prior to associating the profile with a SAP in the config>subscribermgmt>sub-ident-policy context.

Subscribers are managed by the system through the use of subscriber identification strings. A subscriber identification string uniquely identifies a subscriber. For static hosts, the subscriber identification string is explicitly defined with each static subscriber host.

For dynamic hosts, the subscriber identification string must be derived from the DHCP ACK message sent to the subscriber host. The default value for the string is the content of Option 82 CIRCUIT-ID and REMOTE-ID fields interpreted as an octet string. As an option, the DHCP ACK message may be processed by a subscriber identification policy which has the capability to parse the message into an alternative ASCII or octet string value.

When multiple hosts on the same port are associated with the same subscriber identification string they are considered to be host members of the same subscriber.

A sub-ident-policy can also be used for identifying dynamic transit subscriber names.

The no form of this command removes the default subscriber identification policy from the SAP configuration.

Default

no sub-ident-policy

Parameters

sub-ident-policy-name

Specifies the subscriber identification policy name, up to 32 characters.

Platforms

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

sub-insert-credit-control

sub-insert-credit-control

Syntax

sub-insert-credit-control start-entry entry-id count count

no sub-insert-credit-control

Context

[Tree] (config>filter>ip-filter sub-insert-credit-control)

[Tree] (config>filter>ipv6-filter sub-insert-credit-control)

Full Context

configure filter ip-filter sub-insert-credit-control

configure filter ipv6-filter sub-insert-credit-control

Description

This command inserts point information for credit control for the filter.

The no form of the command reverts to the default.

Default

no sub-insert-credit-control

Parameters

entry-id

Identifies a filter on this system.

Values

1 to 2097151

count

Specifies the count

Values

1 to 65535

Platforms

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

sub-insert-radius

sub-insert-radius

Syntax

sub-insert-radius start-entry entry-id count count

no sub-insert-radius

Context

[Tree] (config>filter>ipv6-filter sub-insert-radius)

[Tree] (config>filter>ip-filter sub-insert-radius)

Full Context

configure filter ipv6-filter sub-insert-radius

configure filter ip-filter sub-insert-radius

Description

This command inserts point information for RADIUS for the filter.

The no form of the command reverts to the default.

Default

no sub-insert-radius

Parameters

entry-id

Specifies at what place the filter entries received from RADIUS will be inserted in the filter.

Values

1 to 2097151

count

Specifies the count.

Values

1 to 65535

Platforms

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

sub-insert-shared-pccrule

sub-insert-shared-pccrule

Syntax

sub-insert-shared-pccrule start-entry entry-id count count

no sub-insert-shared-pccrule

Context

[Tree] (config>qos>sap-egress sub-insert-shared-pccrule)

[Tree] (config>qos>sap-ingress sub-insert-shared-pccrule)

Full Context

configure qos sap-egress sub-insert-shared-pccrule

configure qos sap-ingress sub-insert-shared-pccrule

Description

This command defines the range of filter and QoS policy entries that are reserved for shared entries received in Flow-Information AVP via Gx interface (PCC rules – Policy and Charging Control).

The no form of this command disables the insertion, which will result in a failure of PCC rule installation.

Default

no sub-insert-shared-pccrule

Parameters

entry-id

Specifies the lowest entry in the range.

Values

1 to 65535

count

Specifies the number of entries in the range.

Values

1 to 65535

Platforms

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

sub-insert-shared-pccrule

Syntax

sub-insert-shared-pccrule start-entry entry-id count count

no sub-insert-shared-pccrule

Context

[Tree] (config>filter>ip-filter sub-insert-shared-pccrule)

[Tree] (config>filter>ipv6-filter sub-insert-shared-pccrule)

Full Context

configure filter ip-filter sub-insert-shared-pccrule

configure filter ipv6-filter sub-insert-shared-pccrule

Description

This command defines the range of filter and QoS policy entries that are reserved for shared entries received in Flow-Information AVP via Gx interface (PCC rules – Policy and Charging Control). The no form of this command disables the insertion, which will result in a failure of PCC rule installation.

Default

no sub-insert-shared-pccrule

Parameters

entry-id

Specifies the lowest entry in the range.

Values

1 to 2097151

count

Specifies the number of entries in the range.

Values

1 to 65535

Platforms

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

sub-insert-shared-radius

sub-insert-shared-radius

Syntax

sub-insert-shared-radius start-entry entry-id count count

no sub-insert-shared-radius

Context

[Tree] (config>filter>ipv6-filter sub-insert-shared-radius)

[Tree] (config>filter>ip-filter sub-insert-shared-radius)

Full Context

configure filter ipv6-filter sub-insert-shared-radius

configure filter ip-filter sub-insert-shared-radius

Description

This command configures the insert point for shared host rules from RADIUS.

Default

no sub-insert-shared-radius

Parameters

entry-id

Identifies a filter on this system.

Values

1 to 2097151

count

Specifies the count.

Values

1 to 65535

Platforms

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

sub-insert-wmark

sub-insert-wmark

Syntax

sub-insert-wmark low low-watermark high high-watermark

no sub-insert-wmark

Context

[Tree] (config>filter>ip-filter sub-insert-wmark)

[Tree] (config>filter>ipv6-filter sub-insert-wmark)

Full Context

configure filter ip-filter sub-insert-wmark

configure filter ipv6-filter sub-insert-wmark

Description

This command configures the low and high watermark percentage for inserted filter entry usage reporting.

The no form of the command reverts to the default.

Default

sub-insert-wmark low 90 high 95

Parameters

low-watermark

Specifies the utilization of the filter ranges for filter entry insertion, at which a table full alarm will be cleared by the agent.

Values

0 to 100

high-watermark

Specifies the utilization of the filter ranges for filter entry insertion, at which a table full alarm will be raised by the agent.

Values

0 to 100

Platforms

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

sub-mcac-policy

sub-mcac-policy

Syntax

sub-mcac-policy sub-mcac-policy-name [create]

no sub-mcac-policy b

Context

[Tree] (config>subscr-mgmt sub-mcac-policy)

Full Context

configure subscriber-mgmt sub-mcac-policy

Description

This command creates a policy template with MCAC bandwidth limits that are applied to the subscriber.

Per interface mcac bandwidth limits are set directly under the interface (regular interface or group-interface) and no such policy templates are needed.

The need for a separate policy template for subscribers is due to the fact that groups of subscribers under the same group-interface can share certain settings that can be configured via this template.

To summarize, the MCAC bandwidth constraints for subscribers are defined in the sub-mcac-policy while the mcac bandwidth constraints for the interface are configured directly under the igmp>interface>mcac or igmp>grp-if>mcac context without the need for policy templates.

Note:

The sub-mcac-policy only deals with the mcac bandwidth limits and not the channel bandwidth definitions. Channels bandwidth is defined in a different policy (in the config>router>mcac context) and that policy is applied on the interface level as follows:

  • For group-interface: under the config>service>vprn>igmp>grp-if>mcac context

  • For regular interface: under the config>service/router>igmp>interface>mcac context.

In case of HQoS Adjustment, it is mandatory that the sub-mcac-policy be created and applied to the subscriber. The sub-mac-policy does not have to contain any bandwidth constrains, but it has to be in a no shutdown state in order for HQoS Adjustment to work.

The no form of this command reverts to the default.

Parameters

policy-name

Specifies the name of the policy up to 32 characters.

Platforms

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

sub-mcac-policy

Syntax

sub-mcac-policy policy-name

no sub-mcac-policy

Context

[Tree] (config>subscr-mgmt>sub-prof sub-mcac-policy)

Full Context

configure subscriber-mgmt sub-profile sub-mcac-policy

Description

This command references the policy template in which the mcac bandwidth limits are defined. Mcac for the subscriber is effectively enabled with this command when the sub-profile is applied to the subscriber. The bandwidth of the channels is defined in a different policy (under the config>router>mcac context) and this policy is applied on the interface level as follows:

  • For group-interfaces under the config>service>vprn>igmp>grp-if>mcac context

  • For regular interfaces under the config>service/router>igmp>interface>mcac context

In case of HQoS Adjustment, it is mandatory that the sub-mcac-policy be created and applied to the subscriber. The sub-mac-policy does not have to contain any bandwidth constrains, but it has to be in a no shutdown state in order for HQoS Adjustment to work.

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

Parameters

policy-name

Specifies the policy name configured in the config>subscr-mgmt>sub-mcac-policy context.

Platforms

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

sub-mgmt

sub-mgmt

Syntax

[no] sub-mgmt

Context

[Tree] (config>redundancy>multi-chassis>options sub-mgmt)

Full Context

configure redundancy multi-chassis options sub-mgmt

Description

This command enables the CLI context to configure subscriber management multi-chassis options parameters.

Default

sub-mgmt

Platforms

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

sub-mgmt-extensions

sub-mgmt-extensions

Syntax

[no] sub-mgmt-extensions

Context

[Tree] (config>fwd-path-ext>fpe sub-mgmt-extensions)

Full Context

configure fwd-path-ext fpe sub-mgmt-extensions

Description

This command configures FPE for subscriber management extensions. The FPE cannot be used for other applications but can be used for multiple subscriber management applications.

The no version of this command disables FPE for subscriber management extensions.

Default

no sub-mgmt-extensions

Platforms

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

sub-port

sub-port

Syntax

sub-port port-id [create]

no sub-port port-id

Context

[Tree] (config>port>ethernet>dot1x>macsec sub-port)

Full Context

configure port ethernet dot1x macsec sub-port

Description

This command creates a MACsec instance on a physical port, targeting the specific subset of traffic defined by the encap-match command.

The no form of this command removes the MACsec instance.

Parameters

port-id

Specifies the sub-port id index.

Values

1 to 1023

create

Creates a new sub-port.

Platforms

All

sub-profile

sub-profile

Syntax

[no] sub-profile

Context

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

Full Context

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

Description

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

The no form of this command excludes subscriber profile attributes into RADIUS accounting messages.

Platforms

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

sub-profile

Syntax

sub-profile sub-profile-name

no sub-profile

Context

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

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

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

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

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

Full Context

configure service vpls sap static-host sub-profile

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

configure service ies interface sap static-host sub-profile

configure service vprn interface sap static-host sub-profile

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

Description

This command specifies an existing subscriber profile name to be associated with the static subscriber host.

The no form of this command reverts to the default.

Parameters

sub-profile-name

Specifies the sub-profile name.

Platforms

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

sub-profile

Syntax

[no] sub-profile subscriber-profile-name

Context

[Tree] (config subscr-mgmt sub-profile)

Full Context

configure subscriber-mgmt sub-profile

Description

Commands in this context configure a subscriber profile. A subscriber profile is a template used to define the aggregate QoS for all hosts within a subscriber context. This is done through the definition of the egress and ingress scheduler policies that govern the aggregate SLA for subscribers using the subscriber profile. Subscriber profiles also allow for specific SLA profile definitions when the default definitions from the subscriber identification policy must be overridden.

Subscribers are either explicitly mapped to a subscriber profile template or are dynamically associated by one of various non-provisioned subscriber profile definitions.

A subscriber host can be associated with a subscriber profile in the following ways, listed from lowest to highest precedence:

  1. The subscriber profile named default.

  2. The subscriber profile defined as the subscriber SAP default.

  3. The subscriber profile found by the subscriber identification policy sub-profile-map.

  4. The subscriber profile found by the subscriber identification policy explicit map.

In the event that no defaults are defined and the subscriber identification string is not explicitly provisioned to map to a subscriber profile, either the static subscriber host creation will fail or the dynamic subscriber host DHCP ACK is discarded.

Default Subscriber profile:

When a subscriber profile is created with the subscriber-profile-name default, it is used when no other subscriber profile is associated with the subscriber host by the system. Creating a subscriber profile with the subscriber-profile-name default is optional. If a default subscriber profile is not created, all subscriber hosts subscriber identification strings must match either a non-provisioned default or be provisioned as an explicit match to a subscriber profile.

The default profile has no effect on existing active subscriber on the system as they exist due to higher precedence mappings.

Attempting to delete any subscriber profile (including the profile named default) while in use by existing active subscribers will fail.

The no form of this command reverts to the default.

Parameters

subscriber-profile-name

Specifies the name of the subscriber profile, up to 32 characters.

create

Keyword used to create the subscriber profile.

Platforms

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

sub-profile-map

sub-profile-map

Syntax

sub-profile-map

Context

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

Full Context

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

Description

Commands in this context configure subscriber profile mapping parameters.

Platforms

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

sub-profile-string

sub-profile-string

Syntax

sub-profile-string sub-profile-string

no sub-profile-string

Context

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

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

Full Context

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

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

Description

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

The no form of this command returns to the default.

Parameters

sub-profile-string

Specifies the subscriber profile string, up to 32 characters.

Platforms

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

sub-profile-string

Syntax

sub-profile-string string

no sub-profile-string

Context

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

Full Context

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

Description

This string will be used as a default for subscriber-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 sub-profile-string

Parameters

string

Specifies the string used to look up the subscriber profile.

Platforms

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

sub-ring

sub-ring

Syntax

[no] sub-ring {virtual-link | non-virtual-link}

Context

[Tree] (config>eth-ring sub-ring)

Full Context

configure eth-ring sub-ring

Description

This command specifies this ring-id to be sub-ring as defined in G.80312. By declaring this ring as a sub-ring object, this ring will only have one valid path and the sub-ring will be connected to a major ring or a VPLS instance.

The virtual-link keyword declares that a sub-ring is connected to another ring and control messages can be sent over the attached ring to the other side of the sub-ring.

The non-virtual-link channel parameter declares that a sub-ring may be connected to another ring or to a VPLS instance but no control messages from the sub-ring use the attached ring or VPLS instance. The non-virtual channel behavior is standard G.8032 capability.

The no form of this command deletes the sub-ring and its virtual channel associations.

Default

no sub-ring

Parameters

virtual-link

Specifies that the interconnection is to a ring and a virtual link will be used.

non-virtual-link

Specifies that the interconnection is to a ring or a VPLS instance and a virtual link will not be used.

Platforms

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

sub-sla-mgmt

sub-sla-mgmt

Syntax

[no] sub-sla-mgmt

Context

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

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

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

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

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

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

Full Context

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

configure service vpls sap sub-sla-mgmt

configure service vprn interface sap sub-sla-mgmt

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

configure service ies interface sap sub-sla-mgmt

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

Description

Commands in this context configure subscriber management parameters for this SAP.

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

  • configure service vpls sap sub-sla-mgmt
  • configure subscriber-mgmt msap-policy sub-sla-mgmt
  • configure service ies subscriber-interface group-interface sap sub-sla-mgmt
  • configure service vprn subscriber-interface group-interface sap sub-sla-mgmt

All

  • configure service vprn interface sap sub-sla-mgmt
  • configure service ies interface sap sub-sla-mgmt

sub-sla-mgmt

Syntax

[no] sub-sla-mgmt

Context

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

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

Full Context

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

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

Description

Commands in this context configure subscriber management parameters.

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

Default

sub-sla-mgmt

Platforms

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

subinterface

subinterface

Syntax

subinterface subinterface

no subinterface

Context

[Tree] (config>router>if>extref>oc subinterface)

[Tree] (config>svc>vprn>if>extref>oc subinterface)

Full Context

configure router interface external-reference openconfig subinterface

configure service vprn interface external-reference openconfig subinterface

Description

This command configures the subinterface ID used to map a Nokia vendor-specific configuration and the OpenConfig state.

This command configures the ability to query the OpenConfig state through NETCONF, gRPC, and the MD-CLI from any configuration mode without having to add any OpenConfig model configuration. As part of the configuration, a user must also add a port to the Layer 3 interface.

The no form of this command reverts to the default.

Default

no subinterface

Parameters

subinterface
Specifies the subinterface ID.
Values
0 to 4294967295

Platforms

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

subject

subject

Syntax

subject {eq | neq} subject [regexp]

no subject

Context

[Tree] (config>service>vprn>log>filter>entry>match subject)

Full Context

configure service vprn log filter entry match subject

Description

This command adds an event subject as a match criterion.

The subject is the entity for which the event is reported, such as a port. In this case the port-id string would be the subject. Only one subject command can be entered per event filter entry. The latest subject command overwrites the previous command.

The no form of this command removes the subject match criterion.

Default

no subject

Parameters

eq | neq

This operator specifies the type of match. Valid operators are listed below.

Values
Table 53. Valid Operators

Operator

Notes

eq

equal to

neq

not equal to

subject

A string used as the subject match criterion.

regexp

Specifies the type of string comparison to use to determine if the log event matches the value of subject command parameters. When the regexp keyword is specified, the string in the subject command is a regular expression string that will be matched against the subject string in the log event being filtered.

When regexp keyword is not specified, the subject command string is matched exactly by the event filter.

Platforms

All

subject

Syntax

subject {eq | neq} subject [regexp]

no subject

Context

[Tree] (config>log>filter>entry>match subject)

Full Context

configure log filter entry match subject

Description

This command adds an event subject as a match criterion.

The subject is the entity for which the event is reported, such as a port. In this case the port-id string would be the subject. Only one subject command can be entered per event filter entry. The latest subject command overwrites the previous command.

The no form of this command removes the subject match criterion.

Parameters

eq | neq

Specifies the match type. Valid operators are listed in Valid Operators.

Table 54. Valid Operators

Operator

Notes

eq

equal to

neg

not equal to

subject

Specifies a string up to 32 characters, used as the subject match criterion.

regexp

Specifies the type of string comparison to use to determine if the log event matches the value of subject command parameters. When the regexp keyword is specified, the string in the subject command is a regular expression string that will be matched against the subject string in the log event being filtered. When the regexp keyword is not specified, the subject command string is matched exactly by the event filter.

Platforms

All

subnet

subnet

Syntax

subnet {ip-address/mask | ip-address netmask} [create]

no subnet {ip-address/mask | ip-address netmask}

Context

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

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

Full Context

configure service vprn dhcp local-dhcp-server pool subnet

configure router dhcp local-dhcp-server pool subnet

Description

This command creates a subnet of IP addresses to be served from the pool. The subnet cannot include any addresses that were assigned to subscribers without those addresses specifically excluded. When the subnet is created, no IP addresses are made available until a range is defined.

The no form of the removes the subnet parameters from the configuration.

Parameters

ip-prefix/mask

Specifies the address prefix and mask. A mask of 255.255.255.255 is reserved for system IP addresses.

Values

ip-prefix: a.b.c.d

mask: 8 to 32

netmask

Specifies a string of 0s and 1s that mask or screen out the network part of an IP address so that only the host computer part of the address remains.

Values

a.b.c.d, any mask expressed as dotted quad

create

Keyword used to create the subnet. 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

subnet-check

subnet-check

Syntax

[no] subnet-check

Context

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

[Tree] (config>service>vprn>igmp>if subnet-check)

Full Context

configure service vprn igmp group-interface subnet-check

configure service vprn igmp interface subnet-check

Description

This command enables subnet checking for IGMP messages received on this interface. All IGMP packets with a source address that is not in the local subnet are dropped.

The no form of this command disables local subnet checking for IGMP.

Platforms

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

  • configure service vprn igmp group-interface subnet-check

All

  • configure service vprn igmp interface subnet-check

subnet-check

Syntax

[no] subnet-check

Context

[Tree] (config>router>igmp>if subnet-check)

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

Full Context

configure router igmp interface subnet-check

configure router igmp group-interface subnet-check

Description

This command enables subnet checking for IGMP messages received on this interface. All IGMP packets with a source address that is not in the local subnet are dropped.

Default

subnet-check

Platforms

All

  • configure router igmp interface subnet-check

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

  • configure router igmp group-interface subnet-check

subnet-check

Syntax

[no] subnet-check

Context

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

Full Context

configure router mld group-interface subnet-check

Description

This command enables subnet checking for MLD messages received on this interface. All MLD packets with a source address that is not in the local subnet are dropped.

Default

subnet-check

Platforms

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

subnet-mask

subnet-mask

Syntax

subnet-mask ip-address

no subnet-mask

Context

[Tree] (config>subscr-mgmt>loc-user-db>ipoe>host>options subnet-mask)

[Tree] (config>router>dhcp>server>pool>subnet>options subnet-mask)

Full Context

configure subscriber-mgmt local-user-db ipoe host options subnet-mask

configure router dhcp local-dhcp-server pool subnet options subnet-mask

Description

This command specifies the subnet-mask option to the client. The mask can either be defined (for supernetting) or taken from the pool address.

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

Parameters

ip-address

Specifies the IP address of the subnet mask. This address must be unique within the subnet and specified in dotted decimal notation. Allowed values are IP addresses in the range 1.0.0.0 – 223.255.255.255 (with support of /31 subnets).

Values

a.b.c.d

Platforms

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

subrate

subrate

Syntax

subrate {digital-link | larscom} rate-step

no subrate

Context

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

Full Context

configure port tdm ds3 subrate

Description

This command configures the channel service unit (CSU) compatibility mode to interoperate with existing DS-3 subrate standards.

This configuration applies only for non-channelized DS-3s on ASAP TDM MDAs.

The no form of this command remove the subrate functionality.

Default

no subrate

Parameters

digital-link

Enables the Digital-Link (Quick Eagle) CSU compatibility mode.

larscom

Enables the Larscom CSU compatibility mode.

rate-step

Specifies the subrate value for the associated DS-3.

Values

1 to 147 (digital-link) 1 to 14 (larscom)

Platforms

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

subscriber

subscriber

Syntax

subscriber sub-ident

no subscriber

Context

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

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

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

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

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

Full Context

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

configure service vprn interface sap static-host subscriber

configure service ies interface sap static-host subscriber

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

configure service vpls sap static-host subscriber

Description

This command specifies an existing subscriber identification profile to be associated with the static subscriber host.

Parameters

sub-ident

Specifies the subscriber identification.

Platforms

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

subscriber

Syntax

subscriber sub-ident-string [sap sap-id] [ip ip-address] [{[mac ieee-address] | sla-profile sla-profile-name}] [fc {[be] [l2] [af] [l1] [ h2] [ef] [h1] [nc]}] {[ingress] [ egress]} [host-type host-type] [family family]

no subscriber sub-ident-string

Context

[Tree] (config>mirror>mirror-source subscriber)

Full Context

configure mirror mirror-source subscriber

Description

This command adds hosts of a subscriber to mirroring service.

Parameters

sub-ident-string

Specifies the name of the subscriber identification policy.

sap-id

Specifies the physical port identifier portion of the SAP definition.

ip-address

Specifies the service IP address (system IP address) of the remote device sending LI traffic. If 0.0.0.0 is specified, any remote router is allowed to send to this service.

Values

1.0.0.1 to 223.255.255.254

ieee-address

Specify this optional parameter when defining a static host. The MAC address must be specified for anti-spoof ip-mac and arp-populate. Multiple static hosts may be configured with the same MAC address given that each definition is distinguished by a unique IP address.

sla-profile-name

Each host of a subscriber can use a different sla-profile. This option allows interception of only the hosts using the specified sla-profile. In some deployments sla-profiles are assigned per type of traffic. There can be, for example, a specific sla-profile for voice traffic (which could be used for all SIP-hosts). The name can have up to 32 characters.

fc

Specifies the name of the forwarding class with which to associate traffic. The forwarding class name must already be defined within the system. If the fc-name does not exist, an error will be returned and the fc command will have no effect. If the fc-name does exist, the forwarding class associated with fc-name will override the default forwarding class.

Values

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

egress

Specifies that packets egressing the SAP should be mirrored. Egress packets are mirrored to the mirror destination after egress packet modification.

ingress

Specifies that packets ingressing the SAP should be mirrored. Ingress packets are mirrored to the mirror destination prior to ingress packet modification.

host-type

Specifies the host type for mirroring. The anti-spoof filter on the SAP must be configured as ip-mac.

Values

any, ipoe, ppp

family

Specifies the IP family for mirroring. The anti-spoof filter on the SAP must be configured as ip-mac.

Values

any, ipv4, ipv6

Platforms

All

subscriber

Syntax

subscriber sub-ident-string [sap sap-id [ip ip-address] [mac ieee-address] | sla-profile sla-profile-name] [fc {[be] [l2] [af] [l1] [ h2] [ef] [h1] [nc]}] [intercept-id intercept-id] [session-id session-id] {[ingress] [egress]} [ host-type host-type] [family ip-family]

no subscriber sub-ident-string

Context

[Tree] (config>li>li-source subscriber)

Full Context

configure li li-source subscriber

Description

This command adds hosts of a subscriber to mirroring service.

Parameters

sub-ident-string

Specifies the name of the subscriber identification policy.

sap-id

Specifies the physical port identifier portion of the SAP definition.

ip-address

Specifies the service IP address (system IP address) of the remote device sending LI traffic. If 0.0.0.0 is specified, any remote router is allowed to send to this service.

Values

1.0.0.1 to 223.255.255.254

ieee-address

Specifies a MAC address when defining a static host. The MAC address must be specified for anti-spoof ip-mac and arp-populate. Multiple static hosts may be configured with the same MAC address given that each definition is distinguished by a unique IP address.

sla-profile-name

Specifies an SLA profile name, up to 32 characters. Each host of a subscriber can use a different sla-profile. This option allows interception of only the hosts using the specified sla-profile. In some deployments sla-profiles are assigned per type of traffic. There can be, for example, a specific sla-profile for voice traffic (which could be used for all SIP-hosts).

fc

The name of the forwarding class with which to associate LI traffic. The forwarding class name must already be defined within the system. If the fc-name does not exist, an error will be returned and the fc command will have no effect. If the fc-name does exist, the forwarding class associated with fc-name will override the default forwarding class.

Values

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

intercept-id

Specifies the intercept-id that is inserted into the packet header for all mirrored packets of the associated li-source entry. This intercept-id can be used (for example by a downstream LI Gateway) to identify the particular LI session to which the packet belongs.

For all types of li-source entries (filter, nat, sap, or subscriber), when the mirror service is configured with ip-udp-shim routable encap, an intercept-id field (as part of the routable encap) is always present in the mirrored packets. If there is no intercept-id configured for an li-source entry, then the default value will be inserted. When the mirror service is configured with ip-gre or ip-udp-shim-sampled routable encap, no intercept-id is inserted and none can be specified against the li-source entries.

Values

1 to 4294967295 (32b) For nat li-source entries that are using a mirror service that is not configured with routable encap

Values

1 to 1,073,741,824 (30b) For all types of li-source entries that are using a mirror service with routable ip-udp-shim encapsulation and no direction-bit.

Values

1 to 536,870,912 (29b) For all types of li-source entries that are using a mirror service with routable ip-udp-shim encapsulation and with the direction-bit enabled.

session-id

Specifies the session-id that is inserted into the packet header for all mirrored packets of the associated li-source entry. This session-id can be used (for example by a downstream LI gateway) to identify the particular LI session to which the packet belongs. The session-id is only valid and used for mirror services that are configured with ip-udp-shim routable encapsulation (config>mirror>mirror-dest>encap>ip-udp-shim).

For all types of li-source entries (filter, nat, sap, or subscriber), when the mirror service is configured with ip-udp-shim routable encap, a session-id field (as part of the routable encapsulation) is always present in the mirrored packets. If there is no session-id configured for an li-source entry, then the default value will be inserted. When a mirror service is configured with ip-gre or ip-udp-shim-sampled routable encap, no session-id is inserted and none can be specified against the li-source entries.

Values

1 to 4,294,967,295 (32b)

ingress

Specifies the ingress policy for lawful intercept.

egress

Specifies the egress policy for lawful intercept.

host-type

Specifies the host type for lawful intercept. The anti-spoof filter on the SAP must be configured as ip-mac.

Values

any, ipoe, ppp

ip-family

Specifies the IP family for lawful intercept. The anti-spoof filter on the SAP must be configured as ip-mac.

Values

any, ipv4, ipv6

Platforms

All

subscriber

Syntax

subscriber sub-ident-string [sap sap-id] [ip ip-address] [{mac ieee-address] | sla-profile sla-profile-name}] [fc {[be] [l2] [af] [l1] [ h2] [ef] [h1] [nc]}] {[ingress] [ egress]}

no subscriber sub-ident-string

Context

[Tree] (debug>mirror-source subscriber)

Full Context

debug mirror-source subscriber

Description

This command adds hosts of a subscriber to mirroring service.

Parameters

sub-ident-string

Specifies the name of the subscriber identification policy.

sap-id

Specifies the physical port identifier portion of the SAP definition.

ip-address

The service IP address (system IP address) of the remote 7750 SR or 7450 ESS device sending LI traffic.

Values

1.0.0.1 to 223.255.255.254

ieee-address

Specify this optional parameter when defining a static host. The MAC address must be specified for anti-spoof ip-mac and arp-populate. Multiple static hosts may be configured with the same MAC address given that each definition is distinguished by a unique IP address.

sla-profile-name

Specifies the SLA profile name, up to 32 characters.

fc

Specifies name of the forwarding class with which to associate LI traffic.

Values

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

ingress

Specifies information for the ingress policy.

egress

Specifies information for the egress policy.

Platforms

All

subscriber-bw-limit

subscriber-bw-limit

Syntax

subscriber-bw-limit bandwidth

no subscriber-bw-limit

Context

[Tree] (config>mcast-mgmt>mcast-info-plcy>video-policy>video-if subscriber-bw-limit)

Full Context

configure mcast-management multicast-info-policy video-policy video-interface subscriber-bw-limit

Description

This command configures of an egress per-subscriber bandwidth limit for the combined retransmission and Fast Channel Change (FCC) replies for requests received directed to the IP address. If the bandwidth for a request will exceed the bandwidth limit, the request is logged and dropped.

The no form of the command disables enforcement of an egress bandwidth limit.

Default

no subscriber-bw-limit

Parameters

bandwidth

The per-subscriber egress bandwidth limit for retransmission and FCC packets in kilobits per second expressed as an integer indicates infinity or no limit.

Values

1 to 4294967295 kb/s

Platforms

7450 ESS, 7750 SR, 7750 SR-s

subscriber-data

subscriber-data

Syntax

[no] subscriber-data

Context

[Tree] (config>aaa>isa-radius-plcy>acct-include-attributes subscriber-data)

Full Context

configure aaa isa-radius-policy acct-include-attributes subscriber-data

Description

This command enables the inclusion of subscriber data attributes.

The no form of the command excludes subscriber data attributes.

Default

no subscriber-data

Platforms

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

subscriber-id

subscriber-id

Syntax

subscriber-id sub-ident-string

no subscriber-id

Context

[Tree] (config>subscr-mgmt>loc-user-db>ipoe>host>ident-strings subscriber-id)

[Tree] (config>subscr-mgmt>loc-user-db>ppp>host>ident-strings subscriber-id)

Full Context

configure subscriber-mgmt local-user-db ipoe host identification-strings subscriber-id

configure subscriber-mgmt local-user-db ppp host identification-strings subscriber-id

Description

This command specifies the subscriber ID which is encoded in the identification strings.

The no form of this command returns to the default.

Parameters

sub-ident-string

Specifies the subscriber ID string, up to 32 characters.

Platforms

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

subscriber-id

Syntax

[no] subscriber-id

Context

[Tree] (config>subscr-mgmt>acct-plcy>include-radius-attribute subscriber-id)

Full Context

configure subscriber-mgmt radius-accounting-policy include-radius-attribute subscriber-id

Description

This command specifies that subscriber ID attributes should be included into RADIUS accounting messages.

The no form of this command excludes subscriber ID attributes into RADIUS accounting messages.

Platforms

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

subscriber-id

Syntax

[no] subscriber-id

Context

[Tree] (config>aaa>isa-radius-plcy>acct-include-attributes subscriber-id)

Full Context

configure aaa isa-radius-policy acct-include-attributes subscriber-id

Description

This command specifies that subscriber ID attributes should be included into RADIUS accounting messages.

Default

no subscriber-id

Platforms

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

subscriber-identification

subscriber-identification

Syntax

subscriber-identification

Context

[Tree] (config>router>nat>inside subscriber-identification)

Full Context

configure router nat inside subscriber-identification

Description

Commands in this context configure subscriber identification for Large Scale NAT.

Platforms

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

subscriber-interface

subscriber-interface

Syntax

subscriber-interface ip-int-name [create] [wan-mode mode]

subscriber-interface ip-int-name [create] fwd-service service-id fwd-subscriber-interface fwd-int-name [wan-mode mode]

no subscriber-interface ip-int-name

Context

[Tree] (config>service>vprn subscriber-interface)

[Tree] (config>service>ies subscriber-interface)

Full Context

configure service vprn subscriber-interface

configure service ies subscriber-interface

Description

This command allows the operator to create special subscriber-based interfaces. It is used to contain multiple group interfaces. Multiple subnets associated with the subscriber interface can be applied to any of the contained group interfaces in any combination. The subscriber interface allows subnet sharing between group interfaces.

The no form of this command reverts to the default.

Parameters

ip-int-name

Specifies the interface name of a subscriber interface, up to 32 characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.

create

Keyword used to create the subscriber interface.

fwd-service service-id

Specifies the wholesale service ID or service name.

Values

service-id: 1 to 214748364

svc-name: A string up to 64 characters

ip-int-name

Specifies the wholesale subscriber interface.

wan-mode mode

Specifies the WAN mode as 64-bit or 128-bit. To change the WAN mode after creation, the interface must first be removed then recreated.

Values

mode64, mode128

Default

mode64

Platforms

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

subscriber-interface-statistics

subscriber-interface-statistics

Syntax

subscriber-interface-statistics

Context

[Tree] (config>subscr-mgmt subscriber-interface-statistics)

Full Context

configure subscriber-mgmt subscriber-interface-statistics

Description

Commands in this context enable or disable the collection of subscriber interface statistics.

Platforms

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

subscriber-limit

subscriber-limit

Syntax

subscriber-limit limit

no subscriber-limit

Context

[Tree] (config>service>vprn>nat>outside>pool subscriber-limit)

Full Context

configure service vprn nat outside pool subscriber-limit

Description

This command configures the maximum number of subscribers per outside IP address.

If multiple port blocks per subscriber are used, the block size is typically small; all blocks assigned to a given subscriber belong to the same IP address; the subscriber limit guarantees that any subscriber can get a minimum number of ports.

The subscribers are counted per protocol (UDP, TCP and ICMP). For example, in LSN44 a source IPv4 address that uses ports on each of the three protocols (UDP, TCP and ICMP) on an outside IP address count as 3 subscribers on that outside IP address. The ‘no subscriber-limit’ removes the limit for the number of subscribers per outside IP address.

This command is not applicable to pools with:

  • arbitrary address pooling enabled
  • flexible port allocations (application configured under a pool)

Parameters

limit

Specifies the maximum number of subscribers per outside IP address.

Values

1 to 65535

Platforms

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

subscriber-mgmt

subscriber-mgmt

Syntax

subscriber-mgmt

Context

[Tree] (config>service>vprn subscriber-mgmt)

[Tree] (config>service>ies subscriber-mgmt)

Full Context

configure service vprn subscriber-mgmt

configure service ies subscriber-mgmt

Description

Commands in this context configure per service subscriber management parameters.

Platforms

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

subscriber-mgmt

Syntax

subscriber-mgmt

Context

[Tree] (config subscriber-mgmt)

Full Context

configure subscriber-mgmt

Description

Commands in this context configure subscriber management entities. A subscriber is uniquely identified by a subscriber identification string. Each subscriber can have several DHCP sessions active at any time. Each session is referred to as a subscriber host and is identified by its IP address and MAC address.

All subscriber hosts belonging to the same subscriber are subject to the same hierarchical QoS (HQoS) processing. The HQoS processing is defined in the sub-profile (the subscriber profile). A sub-profile refers to an existing scheduler policy (configured in the config>qos>scheduler-policy context) and offers the possibility to overrule the rate of individual schedulers within this policy.

Because all subscriber hosts use the same scheduler policy instance, they must all reside on the same complex.

Platforms

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

subscriber-mgmt

Syntax

subscriber-mgmt

Context

[Tree] (config>system>persistence subscriber-mgmt)

Full Context

configure system persistence subscriber-mgmt

Description

This command configures subscriber management persistence parameters.

Platforms

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

subscriber-mgmt

Syntax

[no] subscriber-mgmt

Context

[Tree] (config>redundancy>multi-chassis>peer>sync subscriber-mgmt)

Full Context

configure redundancy multi-chassis peer sync subscriber-mgmt

Description

Commands in this context configure the synchronization of subscriber management information with the multi-chassis peer.

The no form of this command disables the router from synchronizing subscriber management information with the multi-chassis peer.

Default

no subscriber-mgmt

Platforms

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

subscriber-prefix-length

subscriber-prefix-length

Syntax

subscriber-prefix-length prefix-length

no subscriber-prefix-length

Context

[Tree] (config>service>vprn>nat>inside>dslite subscriber-prefix-length)

Full Context

configure service vprn nat inside dual-stack-lite subscriber-prefix-length

Description

This command configures the IPv6 prefix length of the DS-Lite subscribers.

The no form of this command reverts the default.

Default

subscriber-prefix-length 128

Parameters

prefix-length prefix-length

Specifies the IPv6 prefix length of the DS-Lite subscriber.

Values

32 to 64, 128

Default

128

Platforms

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

subscriber-prefix-length

Syntax

subscriber-prefix-length prefix-length

no subscriber-prefix-length

Context

[Tree] (config>router>nat>inside>dual-stack-lite subscriber-prefix-length)

Full Context

configure router nat inside dual-stack-lite subscriber-prefix-length

Description

This command sets the value for the number of high order bits of the source IPv6 address that will be considered as DS-Lite subscriber. The remaining bits of the source IPv6 address will be masked off, effectively aggregation all IPv6 source addresses under the configured prefix length into a single DS-Lite subscriber. Source IPv4 addresses/ports of the traffic carried within the DS-Lite subscriber will be translated into a single outside IPv4 address and the corresponding deterministic port-block (port-blocks can be extended).

The range of values for subscriber-prefix-length in non-deterministic DS-Lite is limited from 32 to 64 (a prefix will be considered as a DS-Lite subscriber) or it can be set to a value of 128 (the source IPv6 address is considered as a DS-Lite subscriber).

In cases where deterministic DS-Lite is enabled in a giver inside routing context, the range of values of the subscriber-prefix-length depends on the value of dslite-max-subscriber-limit parameter as follows:

subscriber-prefix-length – n = [32..64,128]

where n = log2(dslite-max-subscriber-limit)

[or in an alternate form: dslite-max-subscriber-limit = 2^n.]

In other words the largest prefix length for the deterministic DS-Lite subscriber will be 32+n, where n = log2(dslite-max-subscriber-limit). The subscriber prefix length can extend up to 64 bits. Beyond 64 bits for the subscriber prefix length, there only one value is allowed: 128. In the case n must be 0, which means that the mapping between B4 elements (or IPv6 address) and the IPv4 outside addresses is in 1:1 ratio (no sharing of outside IPv4 addresses).

This parameter can be changed only when there are no deterministic prefixes configured in the same routing context.

The no form of the command reverts to the default.

Default

128

Parameters

prefix-length

In non-deterministic DS-Lite this value can be [32..64,128], assuming that the deterministic DS-Lite is not concurrently enabled in the same inside routing context. In case that deterministic DS-Lite is enabled, this value can be within the range [(32+n)..64,128] where n = log2(dslite-max-subscriber-limit). The value of 128 is allowed only when n=0 (each subscriber is mapped to a single outside IPv4 IP address).

Values

32 to 64

Platforms

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

subscriber-prefix-length

Syntax

subscriber-prefix-length prefix-length

no subscriber-prefix-length

Context

[Tree] (config>router>nat>inside>nat64 subscriber-prefix-length)

[Tree] (config>service>vprn>nat>inside>nat64 subscriber-prefix-length)

Full Context

configure router nat inside nat64 subscriber-prefix-length

configure service vprn nat inside nat64 subscriber-prefix-length

Description

This command specifies the IPv6 address prefix length to be used for the NAT64 subscribers in this virtual router instance.

Default

subscriber-prefix-length128

Parameters

prefix-length

Specifies the subscriber identification for Large Scale NAT.

Values

32 to 64, 128

Platforms

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

subscriber-prefixes

subscriber-prefixes

Syntax

subscriber-prefixes

Context

[Tree] (config>service>ies>sub-if>ipv6 subscriber-prefixes)

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

Full Context

configure service ies subscriber-interface ipv6 subscriber-prefixes

configure service vprn subscriber-interface ipv6 subscriber-prefixes

Description

Commands in this context configure aggregate off-link subscriber prefixes associated with this subscriber interface. Individual prefixes are specified under the prefix context list aggregate routes in which the next hop is indirect via the subscriber interface.

Platforms

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

subscriber-retention

subscriber-retention

Syntax

subscriber-retention [hrs hours] [min minutes]

no subscriber-retention

Context

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

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

Full Context

configure service nat up-nat-policy timeouts subscriber-retention

configure service nat nat-policy timeouts subscriber-retention

Description

This command specifies the subscriber retention timeout, which is the time a NAT subscriber and its associated IP address are kept after all hosts and associated port blocks have expired. If a NAT subscriber host appears before the retention timeout has elapsed, it is given the same outside IP address.

Default

no subscriber-retention

Parameters

hrs hours

Specifies the hours a subscriber’s IP address is kept after all hosts and port blocks have expired.

Values

1 to 24

min minutes

Specifies the minutes a subscriber’s IP address is kept after all hosts and port blocks have expired.

Values

1 to 59

Platforms

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

subscriber-sap-id

subscriber-sap-id

Syntax

[no] subscriber-sap-id

Context

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

[Tree] (config>service>vprn>if>sap>static-host subscriber-sap-id)

[Tree] (config>service>ies>if>sap>static-host subscriber-sap-id)

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

[Tree] (config>service>vpls>sap>static-host subscriber-sap-id)

Full Context

configure service vprn subscriber-interface group-interface sap static-host subscriber-sap-id

configure service vprn interface sap static-host subscriber-sap-id

configure service ies interface sap static-host subscriber-sap-id

configure service ies subscriber-interface group-interface sap static-host subscriber-sap-id

configure service vpls sap static-host subscriber-sap-id

Description

This command enables using the SAP ID as the subscriber ID.

Parameters

subscriber-sap-id

Specifies to use the sap-id as the subscriber-id.

Platforms

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

subscribers

subscribers

Syntax

subscribers {qset-size size | non-shaper-queues}

Context

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

Full Context

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

Description

This command configures the default queue-set size for subscribers.

Parameters

size

Specifies the size of the queue sets.

Values

2 to 8

non-shaper-queues

Specifies that subscribers will not use hardware aggregate shapers on FPs where the FP resource policy is applied.

Platforms

7750 SR-1, 7750 SR-s

subscription

subscription

Syntax

subscription percentage

no subscription

Context

[Tree] (config>router>rsvp>interface subscription)

Full Context

configure router rsvp interface subscription

Description

This command configures the percentage of the link bandwidth that RSVP can use for reservation and sets a limit for the amount of over-subscription or under-subscription allowed on the interface.

When the subscription is set to zero, no new sessions are permitted on this interface. If the percentage is exceeded, the reservation is rejected and a log message is generated.

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

Default

subscription 100

Parameters

percentage

Specifies the percentage of the interface's bandwidth that RSVP allows to be used for reservations.

Values

0 to 1000

Platforms

All

subscription

Syntax

subscription subscription-id cancel

subscription cancel-all

Context

[Tree] (admin>system>telemetry>grpc subscription)

Full Context

admin system telemetry grpc subscription

Description

This command cancels an active telemetry subscription.

Parameters

subscription-id

Specifies the ID of the telemetry subscription to cancel.

Values

0 to 4294967295

Platforms

All

subscription

Syntax

subscription name [create]

no subscription name

Context

[Tree] (config>system>telemetry>persistent-subscriptions subscription)

Full Context

configure system telemetry persistent-subscriptions subscription

Description

Commands in this context configure persistent subscription commands.

The no form of this command removes the configuration.

Parameters

name

Specifies the subscription name, up to 32 characters.

create

Keyword used to create the subscription.

Platforms

All

suggest-internal-objects

suggest-internal-objects

Syntax

[no] suggest-internal-objects

Context

[Tree] (environment suggest-internal-objects)

Full Context

environment suggest-internal-objects

Description

This command enables suggesting of internally created objects while auto completing.

The no form of the command disables the command.

Platforms

All

summaries

summaries

Syntax

[no] summaries

Context

[Tree] (config>service>vprn>ospf>area>stub summaries)

[Tree] (config>service>vprn>ospf3>area>nssa summaries)

[Tree] (config>service>vprn>ospf>area>nssa summaries)

Full Context

configure service vprn ospf area stub summaries

configure service vprn ospf3 area nssa summaries

configure service vprn ospf area nssa summaries

Description

This command enables sending summary (type 3) advertisements into a stub area or Not So Stubby Area (NSSA) on an Area Border Router (ABR). This parameter is particularly useful to reduce the size of the routing and Link State Database (LSDB) tables within the stub or nssa area. By default, summary route advertisements are sent into the stub area or NSSA.

The no form of this command disables sending summary route advertisements and, for stub areas, only the default route is advertised by the ABR.

Default

summaries — Summary routes are advertised by the ABR into the stub area or NSSA.

Platforms

All

summaries

Syntax

[no] summaries

Context

[Tree] (config>router>ospf>area>nssa summaries)

[Tree] (config>router>ospf>area>stub summaries)

[Tree] (config>router>ospf3>area>nssa summaries)

[Tree] (config>router>ospf3>area>stub summaries)

Full Context

configure router ospf area nssa summaries

configure router ospf area stub summaries

configure router ospf3 area nssa summaries

configure router ospf3 area stub summaries

Description

This command enables sending summary (type 3) advertisements into a stub area or Not So Stubby Area (NSSA) on an Area Border Router (ABR).

This parameter is particularly useful to reduce the size of the routing and Link State Database (LSDB) tables within the stub or NSSA area (default: summary).

By default, summary route advertisements are sent into the stub area or NSSA.

The no form of this command disables sending summary route advertisements and, for stub areas; only the default route is advertised by the ABR.

Default

summaries

Platforms

All

summary

summary

Syntax

summary

Context

[Tree] (config>filter>log summary)

Full Context

configure filter log summary

Description

Commands in this context configure log summarization. These settings will only be taken into account when syslog is the log destination.

Platforms

All

summary

Syntax

summary [ip-address]

no summary

Context

[Tree] (debug>router>isis summary)

Full Context

debug router isis summary

Description

This command enables debugging for ISIS summary addresses.

The no form of the command disables the debugging.

Parameters

ip-address

When specified, only packets with the specified address are debugged.

Platforms

All

summary-address

summary-address

Syntax

summary-address {ip-prefix/mask | ip-prefix [netmask]} [level] [ tag tag]

no summary-address {ip-prefix/mask | ip-prefix [netmask]}

Context

[Tree] (config>service>vprn>isis summary-address)

Full Context

configure service vprn isis summary-address

Description

This command creates summary-addresses for the specified router or VPRN instance.

Parameters

ip-prefix/mask

Specifies information for the specified IP prefix and mask length.

Values

ip-prefix

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

ipv4-prefix-length

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

d: [0 to 255]D

ipv6-prefix-length

0 to 128

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)

level

Specifies IS-IS level area attributes. If no level parameter is specified, the default is level-1/2.

Values

level-1, level-2, level-1/2

tag tag

Assigns a route tag to the summary address.

Values

1 to 4294967295

Platforms

All

summary-address

Syntax

summary-address {ip-prefix/ip-prefix-length | ip-prefix netmask} [level] [tag tag] [algorithm algo-id]

summary-address {ip-prefix/ip-prefix-length | ip-prefix netmask} [level] [tag tag] [algorithm algo-id] advertise-unreachable [match-route-tag tag] [advertise-route-tag tag]

no summary-address {ip-prefix/ip-prefix-length | ip-prefix netmask}

Context

[Tree] (config>router>isis summary-address)

Full Context

configure router isis summary-address

Description

This command creates a summary IPv4, IPv6, or SRv6 locator address.

When an IS-IS domain exists out of multiple areas, the user must redistribute IP addresses and SRv6 locators between areas for inter-area SRv6-based transport services.

Scaling may be impacted if all existing IPv4, IPv6, and SRv6 locators are redistributed between all existing areas. SRv6 locators and IP addresses can be summarized when they are redistributed from one area into another area. Summarization reduces the number of entries redistributed, which reduces the size of the Link State Database (LSDB) and increases network stability.

The no form of this command reverts to the default.

Default

no summary-address

Parameters

ip-prefix/ip-prefix-length

Specifies the IP prefix and prefix length of the summary address.

Values

ipv4-prefix

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

ipv4-prefix-length

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

d: [0 to 255]D

ipv6-prefix-length

0 to 128

netmask

Specifies 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)

level

Specifies IS-IS level area attributes.

Values

level-1, level-2, level-1/2

Default

level-1/2

tag

Specifies the route tag to assign for the summary address.

Values

1 to 4294967295

algo-id

Specifies the algorithm topology applied for the summary address.

Values

0, 128 to 255

Default

0

match-route-tag tag

Specifies the route tag to match the Unreachable Prefix Announcements (UPAs). This selects a subset of summary member prefixes to monitor for reachability.

Values

1 to 4294967295

Default

no match-route-tag

advertise-route-tag tag

Specifies the route tag to advertise in the UPA. The UPA tag can be used when there are multiple ASBR redistributing prefixes between two IGP areas.

Values

1 to 4294967295

Default

no advertise-route-tag

Platforms

All

summary-crit

summary-crit

Syntax

summary-crit dst-addr

summary-crit src-addr

no summary-crit

Context

[Tree] (config>filter>log>summary summary-crit)

Full Context

configure filter log summary summary-crit

Description

This command defines the key of the index of the mini-table. If key information is changed while summary is administratively enabled (no shutdown), the filter summary mini-table is flushed and recreated with different key information. Log packets received during the reconfiguration time will be handled as if summary was not active.

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

Default

summary-crit src-addr

Parameters

dst-addr

Specifies that received log packets are summarized based on the destination IPv4, IPv6, or MAC address.

src-addr

Specifies that received log packets are summarized based on the source IPv4, IPv6 or MAC address.

Platforms

All

super-backbone

super-backbone

Syntax

[no] super-backbone

Context

[Tree] (config>service>vprn>ospf super-backbone)

Full Context

configure service vprn ospf super-backbone

Description

This command specifies whether CE-PE functionality is required or not. The OSPF super backbone indicates the type of the LSA generated as a result of routes redistributed into OSPF. When enabled, the redistributed routes are injected as summary, external or NSSA LSAs. When disabled, the redistributed routes are injected as either external or NSSA LSAs only.

Default

no super-backbone

Platforms

All

supplicant-timeout

supplicant-timeout

Syntax

supplicant-timeout seconds

no supplicant-timeout

Context

[Tree] (config>port>ethernet>dot1x supplicant-timeout)

Full Context

configure port ethernet dot1x supplicant-timeout

Description

This command configures the period during which the router waits for a client to respond to its EAPOL messages. When the supplicant-timeout expires, the 802.1x authentication session is considered to have failed.

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

Default

supplicant-timeout 30

Parameters

seconds

Specifies the server timeout period in seconds.

Values

1 to 300

Platforms

All

supported-features

supported-features

Syntax

[no] supported-features

Context

[Tree] (config>subscr-mgmt>diam-appl-plcy>gx>include-avp supported-features)

Full Context

configure subscriber-mgmt diameter-application-policy gx include-avp supported-features

Description

This command includes the supported-features in CCR messages.

The no form of this command resets the command to the default setting.

Platforms

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

suppress

suppress

Syntax

suppress integer

no suppress

Context

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

Full Context

configure router policy-options damping suppress

Description

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

A route is suppressed when it has flapped frequently enough to increase the Figure of Merit (FoM) value to exceed the suppress threshold limit. When the FoM value exceeds the suppress threshold limit, the route is removed from the route table or inclusion in advertisements.

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

Default

no suppress

Parameters

integer

Specifies the suppress value expressed as a decimal integer.

Values

1 to 20000

Platforms

All

suppress-attached-bit

suppress-attached-bit

Syntax

[no] suppress-attached-bit

Context

[Tree] (config>service>vprn>isis suppress-attached-bit)

Full Context

configure service vprn isis suppress-attached-bit

Description

This command configures IS-IS to suppress setting the attached bit on originated Level 1 LSPs to prevent all L1 routers in the area from installing a default route to it.

Platforms

All

suppress-attached-bit

Syntax

[no] suppress-attached-bit

Context

[Tree] (config>router>isis suppress-attached-bit)

Full Context

configure router isis suppress-attached-bit

Description

This command configures IS-IS to suppress setting the attached bit on originated Level 1 LSPs to prevent all L1 routers in the area from installing a default route to it.

Default

no suppress-attached-bit

Platforms

All

suppress-dn-bit

suppress-dn-bit

Syntax

[no] suppress-dn-bit

Context

[Tree] (config>service>vprn>ospf suppress-dn-bit)

[Tree] (config>service>vprn>ospf3 suppress-dn-bit)

Full Context

configure service vprn ospf suppress-dn-bit

configure service vprn ospf3 suppress-dn-bit

Description

This command specifies whether to suppress the setting of the DN bit for OSPF LSA packets generated by this instance of OSPF on the router. When enabled, the DN bit for OSPF LSA packets generated by this instance of the OSPF router will not be set. When disabled, this instance of the OSPF router will follow the normal procedure to determine whether to set the DN bit.

Default

no suppress-dn-bit

Platforms

All

suppress-lo-alarm

suppress-lo-alarm

Syntax

[no] suppress-lo-alarm

Context

[Tree] (config>port>sonet-sdh suppress-lo-alarm)

Full Context

configure port sonet-sdh suppress-lo-alarm

Description

This command enables the suppression of lower order alarms on SONET/SDH port such as MLPPP bundle alarms, DS1/E1 links alarms and 336 APS channel groups alarms.

The no form of this command disables the suppression of lower order alarms on SONET/SDH port.

Platforms

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

suppress-lsn-events

suppress-lsn-events

Syntax

[no] suppress-lsn-events

Context

[Tree] (configure>isa>wlan-gw-group>nat suppress-lsn-events)

Full Context

configure isa wlan-gw-group nat suppress-lsn-events

Description

This command suppresses the generation of Large Scale NAT (LSN) events when RADIUS accounting is enabled.

By default, only one logging facility for tracking subscribers in LSN44, DS-Lite, and NAT64 can be enabled at the time, either the SR OS event logging facility or the RADIUS logging facility. Note that SR OS event logs can be sent to multiple destinations, such as the console session, a telnet or SSH session, memory logs, file destinations, SNMP trap groups, and syslog destinations.

If RADIUS logging is enabled, the NAT logs are sent to the RADIUS destination and the NAT logs are suppressed in the SR OS event logging facility, for example, NAT logs are not sent to the syslog server.

If RADIUS logging is disabled, the NAT logs are sent to the SR OS event logging facility, for example, syslog, assuming that the events are enabled via the SR OS event-control (configure log event-control nat event generate).

The no form of this command, the NAT logs can be sent to both logging facilities simultaneously, the SR OS event logging facility and RADIUS logging facility.

Default

suppress-lsn-events

Platforms

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

suppress-lsn-events

Syntax

[no] suppress-lsn-events

Context

[Tree] (config>isa>nat-group suppress-lsn-events)

Full Context

configure isa nat-group suppress-lsn-events

Description

This command suppresses the generation of Large Scale NAT (LSN) events when RADIUS accounting is enabled.

By default, only one logging facility for tracking subscribers in LSN44, DS-Lite, and NAT64 can be enabled at the time: either the SR OS event logging facility or the RADIUS logging facility. SR OS event logs can be sent to multiple destinations, such as the console session, a telnet or SSH session, memory logs, file destinations, SNMP trap groups, and syslog destinations.

If RADIUS logging is enabled, the NAT logs are sent to the RADIUS destination and the NAT logs are suppressed in the SR OS event logging facility, for example, NAT logs are not sent to the syslog server.

If RADIUS logging is disabled, the NAT logs are sent to the SR OS event logging facility; for example, syslog, assuming that the events are enabled via the event-control command (configure log event-control nat event generate).

By explicitly disabling this command (no suppress-lsn-events), the NAT logs can be sent to both logging facilities simultaneously, the SR OS event logging facility, and the RADIUS logging facility.

Default

suppress-lsn-events

Platforms

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

suppress-lsn-sub-blks-free

suppress-lsn-sub-blks-free

Syntax

[no] suppress-lsn-sub-blks-free

Context

[Tree] (configure>isa>wlan-gw-group>nat suppress-lsn-sub-blks-free)

Full Context

configure isa wlan-gw-group nat suppress-lsn-sub-blks-free

Description

This command suppresses the tmnxNatLsnSubBlksFree summary notification and use the tmnxNatPlBlockAllocationLsn notifications. When the SR OS node is in a state of excessive logging, the queue associated with the transmission of logs on the MS-ISA can become congested. This event further delays the generation of logs, and with this, further allocations and deallocations of NAT resources (port-blocks) is stalled until the queue is relieved of congestion. For example, an excessive logging state in the system can be caused by issuing a command to clear a large number of NAT subscribers where a large number of resources (port-blocks) are released at once.

The suppress-lsn-sub-blks-free command enables the generation of individual logs carried in event-id 2012 for every released port block regardless of the state of the transmission queue (whether congested or not). If NAT subscribers have a large number of allocated port blocks (this could be hundreds of port blocks per subscriber), generating individual logs per port-block release contributes to the congestion.

To alleviate transmission queue congestion, this behavior can be changed by disabling this command (no suppress-lsn-sub-blks-free). This causes the suppression of logs related to the release of individual port blocks of a NAT subscriber when the transmission queue is congested. As a result, only a summarized release log via event-id 2021 for the subscriber is generated. The purpose of this new log is to inform the operator in a single message that all ports blocks for the subscriber are released. For example, the log message for LSN is "LSN subscriber all blocks freed”. The benefit of such summarization (or log aggregation) is to alleviate the congestion of the transmission queue and consequently accelerate resource releases. An effect is the decreased granularity of information.

If summarization is enabled (no suppress-lsn-sub-blks-free) while there is no logging congestion in the system, the port block releases continue to be logged individually via the event-id 2012 (assuming that this is enabled in the event control), except for the last port block of the subscriber. When the last port block is released, the log with event-id 2021 is generated indicating that all port blocks for the subscriber are now released without carrying the specific information about this last port block that is released.

Platforms

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

suppress-lsn-sub-blks-free

Syntax

[no] suppress-lsn-sub-blks-free

Context

[Tree] (config>isa>nat-group suppress-lsn-sub-blks-free)

Full Context

configure isa nat-group suppress-lsn-sub-blks-free

Description

This command suppresses the tmnxNatLsnSubBlksFree summary notification and use the tmnxNatPlBlockAllocationLsn notifications. When the SR OS node is in a state of excessive logging, the queue associated with the transmission of logs on the MS-ISA can become congested. This event further delays the generation of logs, and with this, further allocations and deallocations of NAT resources (port-blocks) will be stalled until the queue is relieved of congestion. For example, an excessive logging state in the system can be caused by issuing a command to clear a large number of NAT subscribers where a large number of resources (port-blocks) are released at once.

The suppress-lsn-sub-blks-free command enables the generation of individual logs carried in event-id 2012 for every released port block regardless of the state of the transmission queue (whether congested or not). If NAT subscribers have a large number of allocated port blocks (this could be hundreds of port blocks per subscriber), generating individual logs per port-block release contributes to the congestion.

To alleviate transmission queue congestion, this behavior can be changed by disabling this command (no suppress-lsn-sub-blks-free). This causes the suppression of logs related to the release of individual port blocks of a NAT subscriber when the transmission queue is congested. As a result, only a summarized release log via event-id 2021 for the subscriber is generated. The purpose of this new log is to inform the operator in a single message that all ports blocks for the subscriber are released. For example, the log message for LSN will be "LSN subscriber all blocks freed”. The benefit of such summarization (or log aggregation) is to alleviate the congestion of the transmission queue and consequently accelerate resource releases. An effect is the decreased granularity of information.

If summarization is enabled (no suppress-lsn-sub-blks-free) while there is no logging congestion in the system, the port block releases continue to be logged individually via the event-id 2012 (assuming that this is enabled in the event control), except for the last port block of the subscriber. When the last port block is released, the log with event-id 2021 is generated indicating that all port blocks for the subscriber are now released without carrying the specific information about this last port block that is released.

Default

no suppress-lsn-sub-blks-free

Platforms

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

suppress-standby-signaling

suppress-standby-signaling

Syntax

[no] suppress-standby-signaling

Context

[Tree] (config>service>vpls>endpoint suppress-standby-signaling)

Full Context

configure service vpls endpoint suppress-standby-signaling

Description

When this command is enabled, the pseudowire standby bit (value 0x00000020) will not be sent to T-LDP peer when the specified spoke is selected as a standby. This allows faster switchover as the traffic will be sent over this SDP and discarded at the blocking side of the connection. This is particularly applicable to multicast traffic.

Default

suppress-standby-signaling

Platforms

All

suppress-threshold

suppress-threshold

Syntax

suppress-threshold suppress-penalties reuse-threshold reuse-penalties

Context

[Tree] (config>port>ethernet>dampening suppress-threshold)

Full Context

configure port ethernet dampening suppress-threshold

Description

This command configures the penalties thresholds at which the port state events to the upper layer are dampened (suppress threshold) and then permitted (reuse threshold).

Parameters

suppress-penalties

Specifies the threshold at which the port up state is suppressed until the accumulated penalties drop below the reuse threshold again.

Values

1 to 20000

Default

2000

reuse-penalties

Specifies the threshold at which the port up state is no longer suppressed, after the port has been in a suppressed state and the accumulated penalties decay drops below this threshold. The reuse threshold value must be less than the suppress threshold value.

Values

1 to 20000

Default

1000

Platforms

All

svc-id

svc-id

Syntax

svc-id service-id

no svc-id

Context

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

Full Context

configure system security management-access-filter mac-filter entry match svc-id

Description

This command specifies an existing svc-id to use as a match condition.

Parameters

service-id

Specifies a service-id to match.

Values

service-id: 1 to 2147483647svc-name: 64 characters maximum

Platforms

All

svc-path

svc-path

Syntax

svc-path path-id svc-index service-index

no svc-path

Context

[Tree] (config>subscr-mgmt>isa-svc-chain>vas-filter>entry>action>insert-nsh svc-path)

Full Context

configure subscriber-mgmt isa-service-chaining vas-filter entry action insert-nsh svc-path

Description

This command configures the service path identifier and service index to be inserted in NSH in the steered traffic if the forward action indicates NSH insertion.

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

Parameters

path-id

Specifies the 24-bit path ID in the base part of NSH.

Values

0 to 16777215

service-index

Specifies the 8-bit service index inserted in the base part of NSH.

Values

0 to 255

Platforms

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

svc-ping

svc-ping

Syntax

svc-ping ip-address [ service service-id] [local-sdp] [ remote-sdp]

Context

[Tree] (oam svc-ping)

Full Context

oam svc-ping

Description

This command tests a service ID for correct and consistent provisioning between two service end points.

The svc-ping command accepts a far-end IP address and a service ID for local and remote service testing. The following information can be determined from svc-ping:

Local and remote service existence

  • Local and remote service state

  • Local and remote service type correlation

  • Local and remote customer association

  • Local and remote service-to-SDP bindings and state

  • Local and remote ingress and egress service label association

Unlike sdp-ping, only a single message is sent per command; no count nor interval parameter is supported and round trip time is not calculated. A time out value of 10 seconds is used before failing the request. The forwarding class is assumed to be Best-Effort Out-of-Profile.

If no request is sent or a reply is not received, all remote information is shown as N/A.

To terminate a svc-ping in progress, use the CLI break sequence <Ctrl-C>.

Upon request time out, message response, request termination, or request error the following local and remote information is displayed. See Svc-ping. Local and remote information is dependent upon service existence and reception of reply.

Table 55. Svc-ping

Field

Description

Values

Request Result

The result of the svc-ping request message.

Sent - Request Timeout

Sent - Request Terminated

Sent - Reply Received

Not Sent - Non-Existent Service-ID

Not Sent - Non-Existent SDP for Service

Not Sent - SDP For Service Down

Not Sent - Non-existent Service Egress Label

Service-ID

The ID of the service being tested.

service-id

Local Service Type

The type of service being tested. If service-id does not exist locally, N/A is displayed.

Epipe, Ipipe, Fpipe, Apipe

TLS

IES

Mirror-Dest

Local Service Admin State

The local administrative state of service-id. If the service does not exist locally, the administrative state is Non-Existent.

Admin-Up

Admin-Down

Non-Existent

Local Service Oper State

The local operational state of service-id. If the service does not exist locally, the state is N/A.

Oper-Up

Oper-Down

Remote Service Type

The remote type of service being tested. If service-id does not exist remotely, N/A is displayed.

Epipe, Ipipe, Fpipe, Apipe

TLS

IES

Mirror-Dest

Remote Service Admin State

The remote administrative state of service-id. If the service does not exist remotely, the administrative state is Non-Existent.

Up

Down

Non-Existent

Local Service MTU

The local service-mtu for service-id. If the service does not exist, N/A is displayed.

service-mtu

Remote Service MTU

The remote service-mtu for service-id. If the service does not exist remotely, N/A is displayed.

remote-service-mtu

Local Customer ID

The local customer-id associated with service-id. If the service does not exist locally, N/A is displayed.

customer-id

Remote Customer ID

The remote customer-id associated with service-id. If the service does not exist remotely, N/A is displayed.

customer-id

Local Service IP Address

The local system IP address used to terminate remotely configured SDP-ID (as the far-end address). If an IP interface has not been configured to be the system IP address, N/A is displayed.

system-ip-address

Local Service IP Interface Name

The name of the local system IP interface. If the local system IP interface has not been created, N/A is displayed.

system-interface-name

Local Service IP Interface State

The state of the local system IP interface. If the local system IP interface has not been created, Non-Existent is displayed.

Up

Down

Non-Existent

Expected Far-end Address

The expected IP address for the remote system IP interface. This must be the far-end address entered for the svc-ping command.

orig-sdp-far-end-addr

dest-ip-addr

Actual Far-end Address

The returned remote IP address. If a response is not received, the displayed value is N/A. If the far-end service IP interface is down or non-existent, a message reply is not expected. sdp-ping should also fail.

resp-ip-addr

Responders Expected Far-end Address

The expected source of the originator’s sdp-id from the perspective of the remote router terminating the sdp-id. If the far-end cannot detect the expected source of the ingress sdp-id or the request is transmitted outside the sdp-id, N/A is displayed.

resp-rec-tunnel-far-end-address

Originating SDP-ID

The sdp-id used to reach the far-end IP address if sdp-path is defined. The originating sdp-id must be bound to the service-id and terminate on the far-end IP address. If an appropriate originating sdp-id is not found, Non-Existent is displayed.

orig-sdp-id

Non-Existent

Originating SDP-ID Path Used

Whether the Originating router used the originating sdp-id to send the svc-ping request. If a valid originating sdp-id is found, operational and has a valid egress service label, the originating router should use the sdp-id as the requesting path if sdp-path has been defined. If the originating router uses the originating sdp-id as the request path, Yes is displayed. If the originating router does not use the originating sdp-id as the request path, No is displayed. If the originating sdp-id is non-existent, N/A is displayed.

Yes

No

Originating SDP-ID Administrative State

The local administrative state of the originating sdp-id. If the sdp-id has been shutdown, Admin-Down is displayed. If the originating sdp-id is in the no shutdown state, Admin-Up is displayed. If an originating sdp-id is not found, N/A is displayed.

Admin-Up

Admin-Up

Originating SDP-ID Operating State

The local operational state of the originating sdp-id. If an originating sdp-id is not found, N/A is displayed.

Oper-Up

Oper-Down

Originating SDP-ID Binding Admin State

The local administrative state of the originating sdp-ids binding to service-id. If an sdp-id is not bound to the service, N/A is displayed.

Admin-Up

Admin-Up

Originating SDP-ID Binding Oper State

The local operational state of the originating sdp-ids binding to service-id. If an sdp-id is not bound to the service, N/A is displayed.

Oper-Up

Oper-Down

Responding SDP-ID

The sdp-id used by the far end to respond to the svc-ping request. If the request was received without the sdp-path parameter, the responding router does not use an sdp-id as the return path, but the appropriate responding sdp-id is displayed. If a valid sdp-id return path is not found to the originating router that is bound to the service-id, Non-Existent is displayed.

resp-sdp-id

Non-Existent

Responding SDP-ID Path Used

Whether the responding router used the responding sdp-id to respond to the svc-ping request. If the request was received via the originating sdp-id and a valid return sdp-id is found, operational and has a valid egress service label, the far-end router should use the sdp-id as the return sdp-id. If the far end uses the responding sdp-id as the return path, Yes is displayed. If the far end does not use the responding sdp-id as the return path, No is displayed. If the responding sdp-id is non-existent, N/A is displayed.

Yes

No

Responding SDP-ID Administrative State

The administrative state of the far-end sdp-id associated with the return path for service-id. When a return path is administratively down, Admin-Down is displayed. If the return sdp-id is administratively up, Admin-Up is displayed. If the responding sdp-id is non-existent, N/A is displayed.

Admin-Up

Admin-Up

N/A

Responding SDP-ID Operational State

The operational state of the far-end sdp-id associated with the return path for service-id. When a return path is operationally down, Oper-Down is displayed. If the return sdp-id is operationally up, Oper-Up is displayed. If the responding sdp-id is non-existent, N/A is displayed.

Oper-Up

Oper-Down

Responding SDP-ID Binding Admin State

The local administrative state of the responder’s sdp-id binding to service-id. If an sdp-id is not bound to the service, N/A is displayed.

Admin-Up

Admin-Down

Responding SDP-ID Binding Oper State

The local operational state of the responder’s sdp-id binding to service-id. If an sdp-id is not bound to the service, N/A is displayed.

Oper-Up

Oper-Down

Originating VC-ID

The originator’s VC-ID associated with the sdp-id to the far-end address that is bound to service-id. If the sdp-id signaling is off, originator-vc-id is 0. If the originator-vc-id does not exist, N/A is displayed.

originator-vc-id

Responding VC-ID

The responder’s VC-ID associated with the sdp-id to originator-id that is bound to service-id. If the sdp-id signaling is off or the service binding to sdp-id does not exist, responder-vc-id is 0. If a response is not received, N/A is displayed.

responder-vc-id

Originating Egress Service Label

The originating service label (VC-Label) associated with the service-id for the originating sdp-id. If service-id does not exist locally, N/A is displayed. If service-id exists, but the egress service label has not been assigned, Non-Existent is displayed.

egress-vc-label

Non-Existent

Originating Egress Service Label Source

The originating egress service label source. If the displayed egress service label is manually defined, Manual is displayed. If the egress service label is dynamically signaled, Signaled is displayed. If the service-id does not exist or the egress service label is non-existent, N/A is displayed.

Manual

Signaled

Originating Egress Service Label State

The originating egress service label state. If the originating router considers the displayed egress service label operational, Up is displayed. If the originating router considers the egress service label inoperative, Down is displayed. If the service-id does not exist or the egress service label is non-existent, N/A is displayed.

Up

Down

Responding Service Label

The actual responding service label in use by the far-end router for this service-id to the originating router. If service-id does not exist in the remote router, N/A is displayed. If service-id does exist remotely but the remote egress service label has not been assigned, Non-Existent is displayed.

rec-vc-label

Non-Existent

Responding Egress Service Label Source

The responder’s egress service label source. If the responder’s egress service label is manually defined, Manual is displayed. If the responder’s egress service label is dynamically signaled, Signaled is displayed. If the service-id does not exist on the responder or the responder’s egress service label is non-existent, N/A is displayed.

Manual

Signaled

Responding Service Label State

The responding egress service label state. If the responding router considers its egress service label operational, Up is displayed. If the responding router considers its egress service label inoperative, Down is displayed. If the service-id does not exist or the responder’s egress service label is non-existent, N/A is displayed.

Up

Down

Expected Ingress Service Label

The locally assigned ingress service label. This is the service label that the far-end is expected to use for service-id when sending to the originating router. If service-id does not exist locally, N/A is displayed. If service-id exists but an ingress service label has not been assigned, Non-Existent is displayed.

ingress-vc-label

Non-Existent

Expected Ingress Label Source

The originator’s ingress service label source. If the originator’s ingress service label is manually defined, Manual is displayed. If the originator’s ingress service label is dynamically signaled, Signaled is displayed. If the service-id does not exist on the originator or the originators ingress service label has not been assigned, N/A is displayed.

Manual

Signaled

Expected Ingress Service Label State

The originator’s ingress service label state. If the originating router considers its ingress service label operational, Up is displayed. If the originating router considers its ingress service label inoperative, Down is displayed. If the service-id does not exist locally, N/A is displayed.

Up

Down

Responders Ingress Service Label

The assigned ingress service label on the remote router. This is the service label that the far end is expecting to receive for service-id when sending to the originating router. If service-id does not exist in the remote router, N/A is displayed. If service-id exists, but an ingress service label has not been assigned in the remote router, Non-Existent is displayed.

resp-ingress-vc-label

Non-Existent

Responders Ingress Label Source

The assigned ingress service label source on the remote router. If the ingress service label is manually defined on the remote router, Manual is displayed. If the ingress service label is dynamically signaled on the remote router, Signaled is displayed. If the service-id does not exist on the remote router, N/A is displayed.

Manual

Signaled

Responders Ingress Service Label State

The assigned ingress service label state on the remote router. If the remote router considers its ingress service label operational, Up is displayed. If the remote router considers its ingress service label inoperative, Down is displayed. If the service-id does not exist on the remote router or the ingress service label has not been assigned on the remote router, N/A is displayed.

Up

Down

Parameters

ip-address

Specifies the far-end IP address to which to send the svc-ping request message in dotted decimal notation.

Values

a.b.c.d

service-id

Specifies the service ID of the service being tested must be indicated with this parameter. The service ID need not exist on the local router to receive a reply message.

Values

1 to 2147483647, service-name: up to 64 characters

local-sdp

Specifies the svc-ping request message should be sent using the same service tunnel encapsulation labeling as service traffic. If local-sdp is specified, the command attempts to use an egress sdp-id bound to the service with the specified far-end IP address with the VC-Label for the service. The far-end address of the specified sdp-id is the expected responder-id within the reply received. The sdp-id defines the encapsulation of the SDP tunnel encapsulation used to reach the far end; this can be IP/GRE or MPLS. On originator egress, the service-ID must have an associated VC-Label to reach the far-end address of the sdp-id and the sdp-id must be operational for the message to be sent.

If local-sdp is not specified, the svc-ping request message is sent with GRE encapsulation with the OAM label.

Message Encapsulation indicates whether a message is sent and how the message is encapsulated based on the state of the service ID.

Table 56. Message Encapsulation

Local Service State

local-sdp Not Specified

local-sdp Specified

Message Sent

Message Encapsulation

Message Sent

Message Encapsulation

Invalid Local Service

Yes

Generic IP/GRE OAM (PLP)

No

None

No Valid SDP-ID Bound

Yes

Generic IP/GRE OAM (PLP)

No

None

SDP-ID Valid But Down

Yes

Generic IP/GRE OAM (PLP)

No

None

SDP-ID Valid and Up, But No Service Label

Yes

Generic IP/GRE OAM (PLP)

No

None

SDP-ID Valid, Up and Egress Service Label

Yes

Generic IP/GRE OAM (PLP)

Yes

SDP Encapsulation with Egress Service Label (SLP)

remote-sdp

Specifies svc-ping reply message from the far-end should be sent using the same service tunnel encapsulation labeling as service traffic.

If remote-sdp is specified, the far-end responder attempts to use an egress sdp-id bound to the service with the message originator as the destination IP address with the VC-Label for the service. The sdp-id defines the encapsulation of the SDP tunnel encapsulation used to reply to the originator; this can be IP/GRE or MPLS. On responder egress, the service-ID must have an associated VC-Label to reach the originator address of the sdp-id and the sdp-id must be operational for the message to be sent.

If remote-sdp is not specified, the svc-ping request message is sent with GRE encapsulation with the OAM label.

Message Response Encapsulation indicates how the message response is encapsulated based on the state of the remote service ID.

Table 57. Message Response Encapsulation

Remote Service State

Message Encapsulation

remote-sdp

Not Specified

remote-sdp

Specified

Invalid Ingress Service Label

Generic IP/GRE OAM (PLP)

Generic IP/GRE OAM (PLP)

Invalid Service-ID

Generic IP/GRE OAM (PLP)

Generic IP/GRE OAM (PLP)

No Valid SDP-ID Bound on Service-ID

Generic IP/GRE OAM (PLP)

Generic IP/GRE OAM (PLP)

SDP-ID Valid But Down

Generic IP/GRE OAM (PLP)

Generic IP/GRE OAM (PLP)

SDP-ID Valid and Up, but No Service Label

Generic IP/GRE OAM (PLP)

Generic IP/GRE OAM (PLP)

SDP-ID Valid and Up, Egress Service Label, but VC-ID Mismatch

Generic IP/GRE OAM (PLP)

Generic IP/GRE OAM (PLP)

SDP-ID Valid and Up, Egress Service Label, but VC-ID Match

Generic IP/GRE OAM (PLP)

SDP Encapsulation with Egress Service Label (SLP)

Platforms

All

Output

Output Example
*A:router1> svc-ping far-end 10.10.10.10 service 101 local-sdp remote-sdp
Request Result: Sent – Reply Received

Service-ID: 101

Err       Basic Info              Local     Remote
---       -----------------       ------    ------
__        Type:                   TLS       TLS
__        Admin State:            Up        Up
__        Oper State:             Up        Up
__        Service-MTU:            1514      1514
__        Customer ID:            1001      1001

Err       System IP Interface Info
---       -------------------------------------------------------------
Local Interface Name: "7750 SR-System-IP-Interface (Up to 32 chars)…”
__        Local IP Interface State:         Up
__        Local IP Address:                 10.10.10.11
__        IP Address Expected By Remote:    10.10.10.11
__        Expected Remote IP Address:       10.10.10.10
__        Actual Remote IP Address:         10.10.10.10

Err       SDP-ID Info             Local     Remote
---       -----------------       ------    ------
__        Path Used:              Yes       Yes
__        SDP-ID:                 123       325
__        Administrative State:   Up        Up
__        Operative State:        Up        Up
__        Binding Admin State:    Up        Up
__        Binding Oper State:     Up        Up
__        Binding VC-ID:          101       101

Err       Service Label Information   Label     Source        State
---       -------------------------   -----     -----------   -----
__        Local Egress Label:         45        Signaled      Up
__        Remote Expected Ingress:    45        Signaled      Up
__        Remote Egress:              34        Signaled      Up
__        Local Expected Ingress:     34        Signaled      Up

svlan-statistics

svlan-statistics

Syntax

svlan-statistics

Context

[Tree] (config>subscr-mgmt svlan-statistics)

Full Context

configure subscriber-mgmt svlan-statistics

Description

Commands in this context enable subscriber VLAN statistics collection.

Platforms

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

swap

swap

Syntax

swap {out-label | implicit-null-label} nexthop ip-address

no swap

Context

[Tree] (config>router>mpls>if>label-map swap)

Full Context

configure router mpls interface label-map swap

Description

This command swaps the incoming label and specifies the outgoing label and next hop IP address on an LSR for a static LSP.

The no form of this command removes the swap action associated with the in-label.

Parameters

implicit-null-label

Specifies the use of the implicit label value for the outgoing label of the swap operation.

out-label

Specifies the label value to be swapped with the in-label. Label values 16 through 1,048,575 are defined as follows:

  • label values 16 through 31 are reserved

  • label values 32 through 1,023 are available for static assignment

  • label values 1,024 through 2,047 are reserved for future use

  • label values 2,048 through 18,431 are statically assigned for services

  • label values 28,672 through 131,071 are dynamically assigned for both MPLS and services

  • label values 131,072 through 1,048,575 are reserved for future use

Values

16 to 1048575

nexthop ip-address

Specifies the IP address to forward to. If an ARP entry for the next hop exists, then the static LSP will be marked operational. If ARP entry does not exist, software will set the operational status of the static LSP to down and continue to ARP for the configured nexthop. Software will continuously try to ARP for the configured nexthop at a fixed interval.

Platforms

All

sweep

sweep

Syntax

sweep start dispersion-start end dispersion-end

Context

[Tree] (config>port>dwdm>coherent sweep)

Full Context

configure port dwdm coherent sweep

Description

This command allows users to configure the dispersion sweep 'start’ and 'end’ values for the automatic mode of coherent control. If the user knows the approximate or theoretical residual dispersion of the link, this command can be used to limit the range of sweeping for the automatic control mode and thus achieve faster link up.

Parameters

dispersion-start

Specifies the lower range limit for the dispersion compensation.

Values

-50000 to 50000

Default

-25500

dispersion-end

Specifies the upper range limit for the dispersion compensation.

Values

-50000 to 50000

Default

2000

Platforms

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

switch-defined-cookie

switch-defined-cookie

Syntax

[no] switch-defined-cookie

Context

[Tree] (config>open-flow>of-switch>flowtable switch-defined-cookie)

Full Context

configure open-flow of-switch flowtable switch-defined-cookie

Description

This command enables OpenFlow switch-defined Flow Table cookie encoding for flowtable 0 that allows multi-service operation.

The no form of the command disables the above function.

Default

no switch-defined-cookie

Platforms

VSR

switch-fabric

switch-fabric

Syntax

switch-fabric

Context

[Tree] (config>system switch-fabric)

Full Context

configure system switch-fabric

Description

Commands in this context configure switch fabric parameters.

Platforms

7450 ESS, 7750 SR-7, 7750 SR-12e, 7750 SR-7s, 7750 SR-14s, 7950 XRS

switching-mode

switching-mode

Syntax

switching-mode {bi-directional | uni-directional}

Context

[Tree] (config>port>aps switching-mode)

Full Context

configure port aps switching-mode

Description

This command configures the switching mode for the APS group.

Parameters

bi-directional

Configures the group to operate in Bidirectional 1+1 Signaling APS mode.

uni-directional

Configures the group to operate in Unidirectional 1+1 Signaling APS mode.

Platforms

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

switchover-exec

switchover-exec

Syntax

switchover-exec file-url

no switchover-exec

Context

[Tree] (config>system switchover-exec)

Full Context

configure system switchover-exec

Description

This command specifies the location and name of the CLI script file executed following a redundancy switchover from the previously active CPM card. A switchover can happen because of a fatal failure or by manual action.

The CLI script file can contain commands for environment settings, classic CLI debug configuration (excluding mirroring settings), and other commands not maintained by the configuration redundancy.

The following commands are not supported in the switchover-exec file: clear, configure, candidate, oam, tools, oam, ping, traceroute, mstat, mtrace and mrinfo.

Default

no switch-over-exec

Parameters

file-url

Specifies the location and name of the CLI script file.

Values

local-url | remote-url

local-url

[cflash-id/][file-path] 200 chars max, including cflash-id

directory length 99 chars max each

remote-url

[{ftp:// | tftp://}login:pswd@remote-locn/][file-path]

243 chars max

directory length 99 chars max each

remote-locn

[hostname | ipv4-address | ipv6-address]

ipv4-address

a.b.c.d

ipv6-address

x:x:x:x:x:x:x:x[-interface]

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

x - [0 to FFFF]H

d - [0 to 255]D

interface - 32 chars max, for link local addresses

cflash-id

cf1:, cf1-A:, cf1-B:, cf2:, cf2-A:, cf2-B:, cf3:, cf3-A:, cf3-B:

Platforms

All

symbol-monitor

symbol-monitor

Syntax

symbol-monitor

Context

[Tree] (config>port>ethernet symbol-monitor)

Full Context

configure port ethernet symbol-monitor

Description

This command configures Ethernet Symbol Monitoring parameters. Support for symbol monitoring is hardware dependent. An error message indicating that the port setting cannot be modified will be presented when attempting to enable the feature or configure the individual parameters on unsupported hardware.

Platforms

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

sync

sync

Syntax

[no] sync

Context

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

Full Context

configure redundancy multi-chassis peer sync

Description

Commands in this context configure synchronization parameters.

Default

no sync

Platforms

All

sync

Syntax

[no] sync

Context

[Tree] (config>isa>nat-group>inter-chassis-redundancy sync)

Full Context

configure isa nat-group inter-chassis-redundancy sync

Description

This command configures synchronization of NAT flows between the nodes.

The no form of this command disables synchronization of NAT flows that were enabled between the ISAs or ESAs across the nodes. This allows NAT reconfiguration on both nodes. The synchronization of flows must be disabled on both nodes, active and standby, while NAT configuration changes are performed. The active NAT node continues to forward traffic while flow synchronization is disabled.

Default

no sync

Platforms

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

sync-boot-env

sync-boot-env

Syntax

sync-boot-env

Context

[Tree] (admin>satellite>eth-sat sync-boot-env)

Full Context

admin satellite eth-sat sync-boot-env

Description

The command forces the specified Ethernet-satellite chassis to synchronize the boot image.

Platforms

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

sync-e

sync-e

Syntax

[no] sync-e

Context

[Tree] (config>card>xiom>mda sync-e)

[Tree] (config>card>mda sync-e)

Full Context

configure card xiom mda sync-e

configure card mda sync-e

Description

This command enables synchronous Ethernet on the MDA. Then any port on the MDA can be used as a source port in the sync-if-timing configuration.

The no form of this command disables synchronous Ethernet on the MDA.

Platforms

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

  • configure card xiom mda sync-e

All

  • configure card mda sync-e

sync-e

Syntax

[no] sync-e

Context

[Tree] (config>system>satellite>eth-sat sync-e)

Full Context

configure system satellite eth-sat sync-e

Description

This command enables the Ethernet satellite for synchronous Ethernet operation so that the transmit timing of the satellite access ports use the frequency of the host router’s central clock.

To enable this functionality, both host ports on the router that connect to the U1 and U2 ports of the satellite must be synchronous Ethernet-capable ports.

When the Ethernet satellite is configured for synchronous Ethernet, ESMC frames are enabled on the host ports. The SSM code-type used between the host and the satellite should be manually configured on the host ports to match the code-type desired on the satellite client ports. The code-type setting on the host ports does not restrict the code-type used on the satellite client ports, as those may be configured on an individual port basis.

Platforms

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

sync-if-timing

sync-if-timing

Syntax

sync-if-timing

Context

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

Full Context

configure system sync-if-timing

Description

This command creates or edits the context to create or modify timing reference parameters.

Platforms

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

sync-if-timing

Syntax

sync-if-timing

Context

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

Full Context

configure system satellite eth-sat sync-if-timing

Description

Commands in this context configure references used in the Ethernet satellite.

The configure system satellite eth-sat sync-e command must first be configured before commands in this context are accepted.

Platforms

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

sync-if-timing

Syntax

sync-if-timing

Context

[Tree] (debug sync-if-timing)

Full Context

debug sync-if-timing

Description

The context to debug synchronous interface timing references.

Platforms

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

synce

synce

Syntax

synce

Context

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

Full Context

configure system sync-if-timing synce

Description

Commands in this context configure attributes related to the CPM/CCM SyncE/1588 ports.

Platforms

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

synchronize

synchronize

Syntax

synchronize {boot-env | config}

Context

[Tree] (config>redundancy synchronize)

Full Context

configure redundancy synchronize

Description

This command enables the automatic synchronization of the standby CPM's images and/or config files from the active CPM. Either the boot-env or config parameter must be specified. When the standby CPM takes over operation following a failure or reset of the active CPM, it is important to ensure that the active and standby CPMs have identical software images and configuration files. This includes the saved configuration, saved incremental configuration files in model-driven configuration mode, CPM, XCM, and IOM images.

The active CPM ensures that the active configuration is maintained on the standby CPM. However, to ensure smooth operation under all circumstances, runtime images and system initialization configurations must also be automatically synchronized between the active and standby CPM.

If synchronization fails, alarms and log messages that indicate the type of error that caused the failure of the synchronization operation are generated. When the error condition ceases to exist, the alarm is cleared.

Only files stored on the router are synchronized. If a configuration file or image is stored in a location other than on a local compact flash, the file is not synchronized (for example, storing a configuration file on an FTP server).

Default

synchronize config

Parameters

boot-env

Synchronizes all files required for the boot process (boot loader, BOF configuration, SR OS images, and all configuration files).

config

Synchronizes the primary, secondary, and tertiary configuration files, SSH keys, the password history and the model-driven commit history.

Default

config

Platforms

All

synchronize

Syntax

synchronize cert

synchronize {boot-env | config}

Context

[Tree] (admin>redundancy synchronize)

Full Context

admin redundancy synchronize

Description

This command performs a synchronization of the standby CPM’s images and/or configuration files to the active CPM. Either the boot-env or config parameter must be specified.

In the admin>redundancy context, this command performs a manually triggered standby CPM synchronization. When the standby CPM takes over operation following a failure or reset of the active CPM, it is important to ensure that the active and standby CPM have identical operational parameters. This includes the saved configuration, CPM, XCM, and IOM images.

The active CPM ensures that the active configuration is maintained on the standby CPM. However, to ensure smooth operation under all circumstances, runtime images and system initialization configurations must also be automatically synchronized between the active and standby CPM. If synchronization fails, alarms and log messages that indicate the type of error that caused the failure of the synchronization operation are generated. When the error condition ceases to exist, the alarm is cleared.

Only files stored on the router are synchronized. If a configuration file or image is stored in a location other than on a local compact flash, the file is not synchronized (for example, storing a configuration file on an FTP server).

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

Default

no synchronize

Parameters

cert

Synchronizes the imported certificate, key, and CRL files.

boot-env

Synchronizes all files required for the boot process (boot loader, BOF, images, and configuration).

config

Synchronizes the primary, secondary, and tertiary configuration files.

Platforms

All

synchronous-execution

synchronous-execution

Syntax

synchronous-execution seconds

synchronous-execution never

Context

[Tree] (config>system>management-interface>ops>global-timeouts synchronous-execution)

Full Context

configure system management-interface operations global-timeouts synchronous-execution

Description

This command configures the period of time that operations launched as "'synchronous” (the default method for all operations) are allowed to execute before they are automatically stopped, and their associated data is deleted.

If a specific execution timeout is not included in the request for a particular synchronous operation, this system-level timeout applies.

Note:

This execution timeout is part of the general global operations infrastructure and is separate and independent from any operation-specific timeouts (for example, the ping operation also has its own timeout parameter).

Caution:

This timeout also applies to operations requested in the MD-CLI interface (for example, ping, file dir, and so on). If synchronous-execution is enabled with a specific time value, MD-CLI operations are subject to this timeout and are interrupted if they execute longer than the configured synchronous-execution time.

Default

synchronous-execution never

Parameters

seconds

Specifies the period of time, in seconds, that synchronous operations are allowed to execute.

Values

1 to 604800

never

Keyword to specify that an execution timeout is not applied to synchronous operations.

Platforms

All

syslog

syslog

Syntax

syslog script name

no syslog

Context

[Tree] (config>python>py-policy syslog)

Full Context

configure python python-policy syslog

Description

This command enables Python script to process syslog related messages and events.

The no form of this command disables the Python script to process syslog related messages and events.

Parameters

name

Specifies the name of the Python script, up to 32 characters, that is used to handle the specified message.

Platforms

All

syslog

Syntax

syslog syslog-id [name syslog-name]

no syslog syslog-id

Context

[Tree] (config>service>vprn>log syslog)

Full Context

configure service vprn log syslog

Description

This command creates the context to configure a Syslog target host that is capable of receiving selected Syslog messages from this network element.

A valid syslog-id must have the target Syslog host address configured.

A maximum of 30 Syslog IDs can be configured.

No log events are sent to a Syslog target address until the syslog-id has been configured as the log destination (to) in the log-id node.

The Syslog ID configured in the configure>service>vprn context has a local VPRN scope and only needs to be unique within the specific VPRN instance. The same ID can be reused under a different VPRN service or in the global log context under config>log.

Default

No syslog IDs are defined.

Parameters

syslog-id

Specifies the Syslog ID for the Syslog destination.

Values

1 to 30

name syslog-name

Specifies an optional Syslog name, up to 64 characters, that can be used to refer to the Syslog destination after it is created.

Platforms

All

syslog

Syntax

syslog

Context

[Tree] (config>app-assure>group>evt-log syslog)

Full Context

configure application-assurance group event-log syslog

Description

Commands in this context configure the target syslog server.

Platforms

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

syslog

Syntax

syslog

Context

[Tree] (config>service>nat syslog)

Full Context

configure service nat syslog

Description

Commands in this context configure syslog reporting of NAT flow parameters.

Platforms

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

syslog

Syntax

syslog syslog-id [name syslog-name]

no syslog syslog-id

Context

[Tree] (config>log syslog)

Full Context

configure log syslog

Description

Commands in this context configure a Syslog target host capable of receiving selected syslog messages from this network element.

A valid syslog-id must have the target Syslog host address configured.

A maximum of 10 Syslog IDs can be configured.

Log events are not sent to a Syslog target address until the syslog-id is configured as the log destination (to) in the node specified by the Log ID.

The Syslog ID configured in the config>service>vprn context has a local VPRN scope and only needs to be unique within the specific VPRN instance. The same ID can be reused under a different VPRN service or in the global log context under config>log.

The no form of this command removes the Syslog configuration.

Parameters

syslog-id

Specifies the Syslog ID for the Syslog destination.

Values

1 to 10

name syslog-name

Configures an optional Syslog name, up to 64 characters, that can be used to refer to the Syslog destination after it is created.

Platforms

All

syslog-export-policy

syslog-export-policy

Syntax

syslog-export-policy policy-name

no syslog-export-policy

Context

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

Full Context

configure service nat nat-policy syslog-export-policy

Description

This command creates a syslog export policy with a set of transport parameters that will be used to transmit NAT flow records in syslog format to an external collector node. This policy name is then referenced from the nat-policy applied to an inside routing context.

Default

no syslog-export-policy

Parameters

policy-name

Specifies the name of the syslog export policy.

Platforms

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

syslog-export-policy

Syntax

syslog-export-policy name [create]

no syslog-export-policy name

Context

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

Full Context

configure service nat syslog syslog-export-policy

Description

This command creates a syslog export policy with a set of transport parameters that are used to transmit NAT flow records in syslog format to an external collector node. This policy name is then referenced from the NAT policy applied to an inside routing context.

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

Parameters

name

Specifies the syslog export policy name, up to 32 characters.

create

Keyword used to create the syslog export policy.

Platforms

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

system

system

Syntax

system

Context

[Tree] (config>eth-cfm system)

Full Context

configure eth-cfm system

Description

Commands in this context configure Connectivity Fault Management (CFM) general system parameters.

Platforms

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

system

Syntax

[no] system

Context

[Tree] (debug system)

Full Context

debug system

Description

This command displays system debug information.

Platforms

All

system-base-mac

system-base-mac

Syntax

system-base-mac mac-address

no system-base-mac

Context

[Tree] (bof system-base-mac)

Full Context

bof system-base-mac

Description

This command is used to specify the base MAC address for a VSR-based system. The specified MAC address is used as the first MAC address by the system to assign MAC addresses to individual interfaces.

It is strongly recommended that a unique base MAC address is assigned to each VSR instance with a minimum gap of 1024 between base addresses to avoid a MAC address overlap.

The no form of this command removes the configured system base MAC address.

Default

no system-base-mac

Parameters

mac-address

Specifies the MAC address.

Values

xx:xx:xx:xx:xx:xx or xx-xx-xx-xx-xx-xx

Platforms

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

system-behavior

system-behavior

Syntax

system-behavior

Context

[Tree] (config>subscr-mgmt system-behavior)

Full Context

configure subscriber-mgmt system-behavior

Description

Commands in this context configure system-wide subscriber management behavior parameters.

Platforms

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

system-filter

system-filter

Syntax

system-filter

Context

[Tree] (config>filter system-filter)

Full Context

configure filter system-filter

Description

Commands in this context activate system filter policies.

Platforms

All

system-id

system-id

Syntax

system-id system-id

no system-id

Context

[Tree] (config>subscr-mgmt>loc-user-db>ipoe>host>host-ident system-id)

Full Context

configure subscriber-mgmt local-user-db ipoe host host-identification system-id

Description

This command specifies the system ID to match for a host lookup. When the LUDB is accessed through a DHCPv4 server, the system ID is matched against the Nokia vendor specific sub-option in DHCP Option 82.

Note:

This command is only used when system-id is configured as one of the match-list parameters.

The no form of this command removes the system ID from the configuration.

Parameters

system-id

Specifies the system ID, up to 255 characters

Platforms

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

system-id

Syntax

[no] system-id

Context

[Tree] (config>service>vprn>if>dhcp>option>vendor system-id)

[Tree] (config>service>vpls>sap>dhcp>option>vendor system-id)

[Tree] (config>service>ies>sub-if>grp-if>dhcp>option>vendor system-id)

[Tree] (config>subscr-mgmt>msap-policy>vpls-only>dhcp>option>vendor system-id)

[Tree] (config>service>vprn>sub-if>grp-if>dhcp>option>vendor system-id)

Full Context

configure service vprn interface dhcp option vendor-specific-option system-id

configure service vpls sap dhcp option vendor-specific-option system-id

configure service ies subscriber-interface group-interface dhcp option vendor-specific-option system-id

configure subscriber-mgmt msap-policy vpls-only-sap-parameters dhcp option vendor-specific-option system-id

configure service vprn subscriber-interface group-interface dhcp option vendor-specific-option system-id

Description

This command specifies whether the system-id is encoded in the Nokia vendor-specific sub-option of Option 82.

The no form of this command reverts to the default.

Platforms

All

  • configure service vprn interface dhcp option vendor-specific-option system-id
  • configure service vpls sap dhcp option vendor-specific-option system-id

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

  • configure subscriber-mgmt msap-policy vpls-only-sap-parameters dhcp option vendor-specific-option system-id
  • configure service vprn subscriber-interface group-interface dhcp option vendor-specific-option system-id
  • configure service ies subscriber-interface group-interface dhcp option vendor-specific-option system-id

system-id

Syntax

system-id isis-system-id

no system-id

Context

[Tree] (config>service>vprn>isis system-id)

Full Context

configure service vprn isis system-id

Description

This command configures the IS-IS system ID. The system ID has a fixed length of 6 octets; it is determined using the following preference order:

  1. config>service>vprn>isis>system-id

  2. config>service>vprn>isis>router-id

  3. config>service>vprn>router-id

  4. config>service>vprn>if>address

  5. The default system ID 2550.0000.0000, based on the default router ID 255.0.0.0

The system ID is integral to IS-IS; therefore, for the system-id command to take effect, a shutdown and then no shutdown must be performed on the IS-IS instance. This will ensure that the configured and operational system ID are always the same.

The no form of this command removes the system ID from the configuration. The router ID is used when no system ID is specified.

Default

no system-id

Parameters

isis-system-id

12 hexadecimal characters in dotted-quad notation.

Values

aaaa.bbbb.cccc, where aaaa, bbbb, and cccc are hexadecimal numbers

Platforms

All

system-id

Syntax

[no] system-id

Context

[Tree] (config>router>if>dhcp>option>vendor-specific-option system-id)

Full Context

configure router interface dhcp option vendor-specific-option system-id

Description

This command specifies whether the system-id is encoded in the Nokia vendor-specific sub-option of Option 82.

Default

no system-id

Platforms

All

system-id

Syntax

system-id isis-system-id

no system-id

Context

[Tree] (config>router>isis system-id)

Full Context

configure router isis system-id

Description

This command configures the IS-IS system ID. The system ID has a fixed length of 6 octets; it is determined using the following preference:

  1. config>router>isis>system-id

  2. config>router>isis>router-id

  3. config>router>router-id

  4. config>router>interface>system> address

  5. The default system ID 2550.0000.0000, based on the default router ID 255.0.0.0

The system ID is integral to IS-IS; therefore, for the system-id command to take effect, the IS-IS instance must be shutdown and then no shutdown. This will ensure that the configured and operational system ID are always the same.

The no form of this command removes the system ID from the configuration. The router ID is used when no system ID is specified.

Parameters

isis-system-id

Specifies 12 hexadecimal characters in dotted-quad notation.

Values

aaaa.bbbb.cccc, where aaaa, bbbb, and cccc are hexadecimal numbers

Platforms

All

system-ip-load-balancing

system-ip-load-balancing

Syntax

[no] system-ip-load-balancing

Context

[Tree] (config>system>load-balancing system-ip-load-balancing)

Full Context

configure system load-balancing system-ip-load-balancing

Description

This command enables the use of the system IP address in the ECMP hash algorithm to add a per system variable. This can help guard against cases where multiple routers, in series, will end up hashing traffic to the same ECMP/LAG path.

This command is set at a system wide basis, however if certain IOMs do not support the new load-balancing algorithm, they will continue to use the default algorithm. By default, the IPv4 system IP address is used in the hash algorithm. When no IPv4 system IP address is configured, the IPv6 system IP address, when configured, is used in the hash algorithm.

The no form of the command resets the system wide algorithm to default.

Default

no system-ip-load-balancing

Platforms

All

system-mac

system-mac

Syntax

system-mac mac-address

no system-mac

Context

[Tree] (config>system>ned>profile system-mac)

Full Context

configure system network-element-discovery profile system-mac

Description

This command configures the MAC address to be advertised.

The no form of this command removes any explicitly defined MAC address and chassis MAC address will be advertised.

Default

no system-mac

Parameters

mac-address

Specifies the MAC address to be associated with the profile in xx:xx:xx:xx:xx:xx or xx-xx-xx-xx-xx-xx format.

Platforms

All

system-name

system-name

Syntax

system-name name

[no] system-name

Context

[Tree] (config>app-assure>group>cflowd system-name)

Full Context

configure application-assurance group cflowd system-name

Description

This command configures the system name of the cflowd AA group. This is exported to the comprehensive cflowd template as aaSystemName.

The no form of this command removes the cflowd system name.

Default

no system-name

Parameters

name

Specifies the name of the system, up to 32 characters.

Platforms

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

system-password

system-password

Syntax

system-password admin-password

system-password dynsvc-password

Context

[Tree] (admin>system>security system-password)

Full Context

admin system security system-password

Description

This operational command changes a local system password.

Parameters

admin-password

Specifies to change the administrative password.

dynsvc-password

Specifies to change the dynamic services password.

Platforms

All

system-priority

system-priority

Syntax

system-priority value

no system-priority

Context

[Tree] (config>redundancy>multi-chassis>peer>mc-ep system-priority)

Full Context

configure redundancy multi-chassis peer mc-endpoint system-priority

Description

This command allows the operator to set the system priority. The peer configured with the lowest value is chosen to be the master. If system-priority are equal then the one with the highest system-id (chassis MAC address) is chosen as the master.

The no form of this command sets the system priority to default.

Default

no system-priority

Parameters

value

Specifies the priority assigned to the local MC-EP peer.

Values

1 to 255

Platforms

All

system-profile

system-profile

Syntax

system-profile {profile-a | profile-b}

no system-profile

Context

[Tree] (bof system-profile)

Full Context

bof system-profile

Description

This command configures the system profile in the BOF.

System profile none represents the existing system capabilities and allows hardware based on FP3 and later generations (for example, FP4, FP5) to co-exist within a system. This profile is indicated by the omission of the system-profile parameter in the BOF.

System profile profile-a is primarily targeted at subscriber services and layer 2 and 3 VPN business services.

System profile profile-b is primarily targeted at infrastructure routing, core, peering, and DC-GW applications.

System profiles profile-a and profile-b support only line cards based on FP4 and later generations (for example, FP5).

On 7750 SR-1 and 7750 SR-s systems, the following conditions apply about the profile parameter:

  • The parameter should be configured to either profile-a or profile-b.

  • If the parameter is omitted, profile profile-a is used by the system.

  • If the parameter is configured to an invalid value, it is ignored and profile profile-a is used by the system.

On 7750 SR-7-B/12-B/12e and 7950 XRS-20/20e systems, the following conditions apply about the profile parameter:

  • The default system profile is none when the parameter is omitted.

  • The parameter can be configured to either profile-a or profile-b, in which case only FP4-based line cards are supported.

  • If the parameter is configured to an invalid value, it is ignored and profile none is used by the system.

On all other systems, the following conditions apply about the profile parameter:

  • These systems must use profile none (the existing system capabilities). As a result, the parameter must not be configured.

  • If the parameter is configured to profile-a or profile-b, the system boots, allowing access using the console and CPM management interface, but FP2-based and FP3-based line cards cannot be provisioned; if these card types are present in the boot configuration, the boot sequence aborts loading the configuration file when it encounters their configuration. This issue can be corrected by removing the parameter and rebooting the system.

  • If the parameter is configured to an invalid value, it is ignored and profile none is used by the system.

See "System profiles" in the 7450 ESS, 7750 SR, 7950 XRS, and VSR Basic System Configuration Guide for more information.

The no form of this command removes the system-profile parameter from the BOF.

Parameters

profile-a

Specifies that the system profile is for subscriber services and Layer 2 and 3 VPN business services.

profile-b

Specifies that the system profile is primarily targeted at infrastructure routing, core, peering, and DC-GW applications.

Platforms

All

system-reserve

system-reserve

Syntax

system-reserve percent-of-buffers

no system-reserve

Context

[Tree] (config>qos>hs-pool-policy system-reserve)

Full Context

configure qos hs-pool-policy system-reserve

Description

This command defines the amount of HSQ IOM buffers that is set aside for internal system use. By default, 5% of the total buffer space is reserved for system internal queues. The command is provided for the case where the reserved buffer space is either insufficient or excessive. Exercise care when modifying this value.

When the system reserve value is changed, all the provisioned port-class, mid-tier, and root pool sizes are reevaluated and possibly changed.

Use the show hs-pools card-slot-number fp forwarding-plane egress command to display the current buffer allocation and buffer usage conditions on an HSQ IOM.

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

Default

system-reserve 5.0

Parameters

percent-of-buffers

Specifies the percentage of HS buffers that are reserved for internal system use. This parameter is required when executing the system-reserve command. The parameter accepts a percent value with two decimal places (100th of a percent).

Values

1.00 to 30.00

Platforms

7750 SR-7/12/12e