a Commands – Part II

Context

[Tree] (config>subscr-mgmt>diam-appl-plcy>gy>avp address-avp)

Full Context

configure subscriber-mgmt diameter-application-policy gy include-avp address-avp

Description

This command includes the following subscriber host/session address/prefix AVPs in all Diameter DCCA CCR messages:

• [8] Framed-IP-Address

• [97] Framed-IPv6-Prefix

• [123] Delegated-IPv6-Prefix

• [6527-99] Alc-IPv6-Address

Note: Only the address/prefix of the subscriber host that triggered the creation of the Diameter Gy session is included.

The no form of this command removes the address AVPs from the Diameter DCCA CCR messages.

Default

address-avp

Platforms

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

Context

[Tree] (config>service>vprn>nat>inside>deterministic address-map)

[Tree] (config>router>nat>inside>deterministic address-map)

Full Context

configure service vprn nat inside deterministic address-map

configure router nat inside deterministic address-map

Description

This command configures the mapping of the inside IP addresses of deterministic NAT44 subscribers to the outside IP addresses in a NAT pool. This mapping is applicable is applicable only to deterministic NAT44 with a single ESA-VM in a NAT-group. The number of subscribers per outside IP address is flexible and not restricted to a discrete range governed by the 2^n rule.

When configured, the classic-lsn-max-subscriber-limit command must be set to 1.

The no form of this command removes the configuration.

Parameters

start-inside-ip-address

Specifies the first IP address in the inside IP address range.

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

end-inside-ip-address

Specifies the last IP address in the inside IP address range.

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

nat-sub-type

Specifies the NAT subscriber type.

Values

classic-lsn-sub, dslite-lsn-sub

nat-policy-name

Specifies the NAT policy name, up to 32 characters, that is referencing a NAT pool.

Values

classic-lsn-sub, dslite-lsn-sub

create

Keyword used to create the address mapping.

Platforms

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

Context

[Tree] (config>router>nat>outside>pool address-pooling)

Full Context

configure router nat outside pool address-pooling

Description

This command configures address pooling to allocate outside ports for a NAT subscriber in relation to the outside IP address.

The behavior in NAT, as defined in RFC 7857, §4, allows the subscriber to be mapped to a single outside IP address and allows for outside ports always to be allocated from that same outside IP address. If this outside IP address becomes exhausted of ports, no new ports for the subscriber can be allocated. This behavior is called paired address pooling.

The alternative behavior is arbitrary address pooling, where a NAT subscriber is mapped to an alternate IP address when the current outside IP address runs out of ports. This way, the subscriber becomes associated with multiple outside IP addresses. While this results in better resource utilization in NAT, it may negatively affect the behavior of some applications.

Default

address-pooling paired

Parameters

paired

Specifies that the subscriber can allocate ports from a single outside IP address. When this IP address runs out of the ports, the subscriber is denied allocation of new ports.

arbitrary

Specifies that the subscriber can allocate ports from multiple outside IP addresses.

Platforms

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

Context

[Tree] (config>system>dns address-pref)

Full Context

configure system dns address-pref

Description

This command configures the DNS address resolving order preference. By default, DNS names are queried for A-records only (address-preference is IPv4-only).

If the address-preference is set to IPv6-first, the DNS server will be queried for AAAA-records (IPv6) first and if a successful replied is not received, then the DNS server is queried for A-records. IPv6 applies only to the 7750 SR and 7950 XRS.

Default

address-pref ipv4-only

Platforms

All

Context

[Tree] (config>router>dhcp>server>pool>subnet address-range)

Full Context

configure router dhcp local-dhcp-server pool subnet address-range

Description

This command configures a range of IP addresses to be served from the pool. All IP addresses between the start and end IP addresses are included (other than specific excluded addresses).

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

Parameters

start-ip-address

Specifies the start address of this range to include. 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

end-ip-address

Specifies the end address of this range to include. 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

local

Specifies that the local DHCP server has the ownership of this dress range in a redundant setup under normal operation.

remote

Specifies that the remote DHCP server has the ownership of this address range in a redundant setup under normal operation.

access-driven

Specifies that the DHCP server failover system is in control by the access protection mechanisms (SRRP or MC-LAG).

Platforms

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

Context

[Tree] (config>router>nat>outside>pool address-range)

[Tree] (config>service>vprn>nat>outside>pool address-range)

Full Context

configure router nat outside pool address-range

configure service vprn nat outside pool address-range

Description

This command configures a NAT address range.

Parameters

start-ip-address

Specifies the beginning IP address in a.b.c.d form.

end-ip-address

Specifies the ending IP address in a.b.c.d. form.

create

This parameter must be specified to create the address range instance

Platforms

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

Context

[Tree] (config>li>x-interfaces>x3 address-range)

Full Context

configure li x-interfaces x3 address-range

Description

This command configures the range of IP addresses to use for the X3 interface. The number of addresses should correspond to the number of ISAs used for the x-interface application.

The no form of this command reverts to the default.

Parameters

ipv4-address

Specifies an IPv4 address.

Values

a.b.c.d

Platforms

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

Context

[Tree] (config>service>vprn>if>sap>ipsec-gw>lcl-addr-assign>ipv6 address-source)

[Tree] (config>service>vprn>if>sap>ipsec-gw>lcl-addr-assign>ipv4 address-source)

[Tree] (config>service>ies>if>sap>ipsec-gw>lcl-addr-assign>ipv4 address-source)

[Tree] (config>service>ies>if>sap>ipsec-gw>lcl-addr-assign>ipv6 address-source)

Full Context

configure service vprn interface sap ipsec-gw local-address-assignment ipv6 address-source

configure service vprn interface sap ipsec-gw local-address-assignment ipv4 address-source

configure service ies interface sap ipsec-gw local-address-assignment ipv4 address-source

configure service ies interface sap ipsec-gw local-address-assignment ipv6 address-source

Description

This command specifies the IPv4 or IPv6 source of the local address assignment for the IPsec gateway, which is a pool of a local DHCPv4 or DHCPv6 server. The system will assign an internal address to an IKEv2 remote-access client from the specified pool.

Beside the IP address, netmask and DNS server can also be returned. For IPv4, the netmask and DNS server address can be returned from the specified pool, as well as the IP address. The netmask returned to the IPsec client is derived from the subnet length from the subnet x.x.x.x/m create configuration, not the subnet-mask configuration in the subnet context. For IPv6, the DNS server address can be returned from the specified pool, as well as the IP address.

For IPv4, a secondary pool can be optionally specified. The secondary pool is used if the system is unable to assign addresses from the primary pool.

Default

no address-source

Parameters

router-instance

Specifies the router instance ID where the local DHCPv4 or DHCPv6 server is defined, up to 32 characters.

This variant of this command is only supported in 'classic' configuration-mode (configure system management-interface configuration-mode classic). The address-source service-name service-name variant can be used in all configuration modes.

service-name

Specifies the name of the service where the local DHCPv4 or DHCPv6 server is defined, up to 64 characters.

local-dhcp4-svr-name

Specifies the name of the local DHCPv4 server, up to 32 characters.

local-dhcp6-svr-name

Specifies the name of the local DHCv6 server, up to 32 characters.

dhcp4-server-pool

The name of the pool defined in the specified DHCPv4 server, up to 32 characters.

dhcp6-server-pool

The name of the pool defined in the specified DHCPv6 server, up to 32 characters.

secondary-pool-name

The name of the secondary pool defined in the specified server, up to 32 characters.

Platforms

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

Context

[Tree] (config>aaa>isa-radius-plcy>acct-update-triggers address-state)

Full Context

configure aaa isa-radius-policy acct-update-triggers address-state

Description

If enabled, an interim-update will be sent for a DSM UE whenever a DHCP, SLAAC or DHCPv6 address gets allocated or freed.

Default

no address-state

Platforms

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

Context

[Tree] (config>subscr-mgmt>wlan-gw>tunnel-query address-type)

Full Context

configure subscriber-mgmt wlan-gw tunnel-query address-type

Description

This command specifies the address type to match on tunnels.

The no form of this command reverts to the default.

Default

address-type not-specified

Parameters

ipv4

Specifies the IPv4 address to match on tunnels.

ipv6

Specifies the IPv6 address to match on tunnels.

not-specified

Specifies that no address type matches on tunnels.

Platforms

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

Context

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

Full Context

configure subscriber-mgmt wlan-gw ue-query address-type

Description

This command enables matching on UEs that have an address of the specified type.

The no form of this command reverts to the default.

Default

address-type not-specified

Parameters

ipv4

Specifies matching on UEs that have an IPv4 stack active.

ipv6

Specifies matching on UEs that have an IPv6 stack active.

ipv4-only

Specifies matching on UEs that have only an IPv4 and no IPv6 stack active.

ipv6-only

Specifies matching on UEs that have only an IPv6 and no IPv4 stack active.

ipv4v6

Specifies matching on UEs that have both an IPv4 and IPv6 stack active.

not-specified

Specifies that no address type matches on UEs.

Platforms

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

Context

[Tree] (debug>service>id>video-interface adi)

Full Context

debug service id video-interface adi

Description

This command enables debugging for the ad insert server.

Parameters

zone-channel-name

Specifies the channel name up to 32 characters.

Platforms

7450 ESS, 7750 SR, 7750 SR-s

Context

[Tree] (config>router>ospf>segm-rtng>egress-statistics adj-set)

[Tree] (config>router>isis>segm-rtng>egress-statistics adj-set)

[Tree] (config>router>ospf>segm-rtng>ingress-statistics adj-set)

[Tree] (config>router>isis>segm-rtng>ingress-statistics adj-set)

Full Context

configure router ospf segment-routing egress-statistics adj-set

configure router isis segment-routing egress-statistics adj-set

configure router ospf segment-routing ingress-statistics adj-set

configure router isis segment-routing ingress-statistics adj-set

Description

This command enables the allocation of statistic indices to each adjacency set. All adjacencies of a set share the same statistics index. If a statistics index is not available at allocation time, the allocation fails, then the system re-tries the allocation. The system generates a log on the first fail and a log on the final successful allocation.

The no form of this command disables the allocation of statistic indices to each adjacency set, releases the statistic indices, and clears the associated counters.

Default

no adj-set

Platforms

All

Context

[Tree] (config>router>ospf>segm-rtng>egress-statistics adj-sid)

[Tree] (config>router>ospf3>segm-rtng>ingress-statistics adj-sid)

[Tree] (config>router>ospf3>segm-rtng>egress-statistics adj-sid)

[Tree] (config>router>isis>segm-rtng>egress-statistics adj-sid)

[Tree] (config>router>isis>segm-rtng>ingress-statistics adj-sid)

[Tree] (config>router>ospf>segm-rtng>ingress-statistics adj-sid)

Full Context

configure router ospf segment-routing egress-statistics adj-sid

configure router ospf3 segment-routing ingress-statistics adj-sid

configure router ospf3 segment-routing egress-statistics adj-sid

configure router isis segment-routing egress-statistics adj-sid

configure router isis segment-routing ingress-statistics adj-sid

configure router ospf segment-routing ingress-statistics adj-sid

Description

This command enables the allocation of statistic indices to each programmed NHLFE corresponding to Adjacency SIDs (local and received by means of IGP advertisement). All NHLFEs associated to a given SID share the same index. If a statistics index is not available at allocation time, the allocation fails, then the system re-tries the allocation. The system generates a log on the first fail and a log on the final successful allocation.

The no form of this command disables the allocation of statistic indices to each adjacency SID, releases the statistic indices, and clears the associated counters.

Default

no adj-sid

Platforms

All

Context

[Tree] (config>router>isis>segm-rtng adj-sid-hold)

Full Context

configure router isis segment-routing adj-sid-hold

Description

This command configures a timer to hold the ILM or LTN of an adjacency SID following a failure of the adjacency.

When an adjacency to a neighbor fails, the following procedures are followed for both the LFA protected SID and the LFA unprotected SID of this adjacency in SR-MPLS. An adjacency can have both types of SIDs assigned by configuration. An LFA protected adjacency SID is eligible for LFA protection, but the following procedures apply even if a LFA backup was not programmed at the time of the failure. An LFA unprotected adjacency SID is not eligible for LFA protection.

• IGP withdraws the advertisement of the link TLV as well as its adjacency SID sub-TLV.
• The adjacency SID hold timer starts.
• The LTN and ILM records of the adjacency are kept in the datapath for as long as the adjacency SID hold time is running. This allows packets to flow over the LFA backup path, when the adjacency is protected, and allows the ingress LER or PCE time to compute a new path of the SR-TE LSP after IGP converges.
• If the adjacency is restored while the adjacency SID hold timer is running, the timer is aborted, and the adjacency SID remains programmed in the datapath with the retained SID values. However, the backup NHLFE may change if a new LFA SPF runs while the adjacency SID hold timer running. An update to the backup NHLFE is performed immediately following the LFA SPF. In all cases, the adjacency keeps its assigned SID label value.

• If the adjacency SID hold timer expires before the adjacency is restored, the SID is deprogrammed from the datapath and the label returned into the common pool where it was drawn from. Users of the adjacency (for example, SR policy and SR-TE LSP) are also informed.

  When the adjacency is subsequently restored, it gets assigned its allocated static-label value or a new dynamic-label value.

• A new PG-ID is assigned each time an adjacency comes back up. This PG-ID is used by the ILM and LTN of the adjacency SID and of all downstream node SIDs that resolve to a next hop over this adjacency.

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

Default

adj-sid-hold 15

Parameters

seconds

Specifies the adjacency SID hold time, in seconds.

Values

1 to 1800

Platforms

All

Context

[Tree] (config>router>isis>srv6 adj-sid-hold)

Full Context

configure router isis segment-routing-v6 adj-sid-hold

Description

This command specifies the length of time the system holds the SRv6 adjacency route and tunnel entries programmed in datapath while the adjacency is down.

When an adjacency to a neighbor fails, the following procedures are followed for both the LFA protected SID and the LFA unprotected SID of this adjacency in SRv6. An adjacency can have both types of SIDs assigned by configuration. An LFA protected adjacency SID is eligible for LFA protection, but the following procedures apply even if a LFA backup was not programmed at the time of the failure. An LFA unprotected adjacency SID is not eligible for LFA protection.

• IGP withdraws the advertisement of the link TLV as well as its SRv6 End.X SID sub-TLV.
• The adjacency SID hold timer starts.
• The route table, FIB, and tunnel table entries are kept for as long as the adjacency SID hold timer is running. This allows packets to flow over the LFA backup path, when the adjacency is protected, and to allow the ingress LER or PCE time to compute a new path of a SRv6 policy after IGP converges.
• If the adjacency is restored while the adjacency SID hold timer is running, the timer is aborted, and the adjacency SID remains programmed in the datapath with the retained SID values. However, the backup NHLFE may change if a new LFA SPF runs while the adjacency SID hold timer is running. An update to the backup NHLFE is performed immediately following the LFA SPF. In all cases, the adjacency keeps its assigned SID value.

• If the adjacency SID hold timer expires before the adjacency is restored, the SID is deprogrammed from the datapath and the SID value returned into the locator subnet where it was drawn from. Users of the adjacency (for example, SRv6 policy) are also informed.

  When the adjacency is subsequently restored, it gets assigned its allocated static SID value or a new dynamic SID value.

• A new PG-ID is assigned each time an adjacency comes back up. This PG-ID is used by tunnel of the local adjacency SID and of all remote locator routes that resolve to a next hop over this adjacency.

configure router isis segment-routing
configure router isis segment-routing-v6

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

Default

adj-sid-hold 15

Parameters

seconds

Specifies the adjacency SID hold time, in seconds.

Values

1 to 1800

Platforms

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

Context

[Tree] (config>router>ospf>segm-rtng adj-sid-hold)

[Tree] (config>router>ospf3>segm-rtng adj-sid-hold)

Full Context

configure router ospf segment-routing adj-sid-hold

configure router ospf3 segment-routing adj-sid-hold

Description

This command configures a timer to hold the ILM or LTN of an adjacency SID following a failure of the adjacency.

When an adjacency to a neighbor fails, the following procedures are followed for both the LFA protected SID and the LFA unprotected SID of this adjacency in SR-MPLS. An adjacency can have both types of SIDs assigned by configuration. An LFA protected adjacency SID is eligible for LFA protection, but the following procedures apply even if a LFA backup was not programmed at the time of the failure. An LFA unprotected adjacency SID is not eligible for LFA protection.

• IGP withdraws the advertisement of the link TLV as well as its adjacency SID sub-TLV.
• The adjacency SID hold timer starts.
• The LTN and ILM records of the adjacency are kept in the datapath for as long as the adjacency SID hold time is running. This allows packets to flow over the LFA backup path, when the adjacency is protected, and allows the ingress LER or PCE time to compute a new path of the SR-TE LSP after IGP converges.
• If the adjacency is restored while the adjacency SID hold timer is running, the timer is aborted, and the adjacency SID remains programmed in the datapath with the retained SID values. However, the backup NHLFE may change when a new LFA SPF is run while the adjacency SID hold timer running. An update to the backup NHLFE is performed immediately following the LFA SPF. In all cases, the adjacency keeps its assigned SID label value.

• If the adjacency SID hold timer expires before the adjacency is restored, the SID is deprogrammed from the datapath and the label returned into the common pool where it was drawn from. Users of the adjacency (for example, SR policy and SR-TE LSP) are also informed.

  When the adjacency is subsequently restored, it gets assigned its allocated static label value or a new dynamic label value.

• A new PG-ID is assigned each time an adjacency comes back up. This PG-ID is used by the ILM and LTN of the adjacency SID and of all downstream node SIDs that resolve to a next hop over this adjacency.

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

Default

adj-sid-hold 15

Parameters

seconds

Specifies the adjacency SID hold time, in seconds.

Values

1 to 1800

Platforms

All

Context

[Tree] (debug>service>id>pim-snooping adjacency)

Full Context

debug service id pim-snooping adjacency

Description

This command enables or disables debugging for PIM adjacencies.

Platforms

All

Context

[Tree] (debug>router>pim adjacency)

Full Context

debug router pim adjacency

Description

This command enables debugging for PIM adjacencies.

The no form of this command disables debugging for PIM adjacencies.

Platforms

All

Context

[Tree] (debug>router>isis adjacency)

Full Context

debug router isis adjacency

Description

This command enables debugging for IS-IS adjacency.

The no form of the command disables debugging.

Parameters

ip-address

When specified, only adjacencies with the specified interface address are debugged.

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

• d: [0 to 255]D

ip-int-name

When specified, only adjacencies with the specified interface name are debugged.

nbr-system-id

When specified, only the adjacency with the specified ID is debugged.

Platforms

All

Context

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

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

Full Context

configure router ospf segment-routing adjacency-set

configure router isis segment-routing adjacency-set

Description

This command creates an adjacency set. An adjacency set consists of one or more adjacency SIDs originating on this node. The constituent adjacencies may terminate on different nodes.

The no form of this command removes the specified adjacency set.

Parameters

id

Specifies an unsigned integer representing the identifier of the adjacency set.

Values

1 to 4294967295

Platforms

All

Context

[Tree] (config>router>isis>interface adjacency-set)

[Tree] (config>router>ospf>area>interface adjacency-set)

Full Context

configure router isis interface adjacency-set

configure router ospf area interface adjacency-set

Description

This command associates an interface with an adjacency set. The adjacency set must have been defined under the IS-IS or OSPF segment-routing context.

The no form of this command removes the association.

Parameters

id

Specifies an unsigned integer representing the identifier of the adjacency set.

Values

1 to 4294967295

Platforms

All

Context

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

Full Context

configure router ospf area interface adjacency-sid

Description

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

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

The no form of this command removes the adjacency SID.

Parameters

label value

Specifies the value of adjacency SID label.

Values

18432 to 52428 | 1048575 (FP4 or FP5 only)

Platforms

All

Context

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

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

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

Full Context

configure router ospf3 segment-routing adjacency-sid

configure router ospf segment-routing adjacency-sid

configure router isis segment-routing adjacency-sid

Description

Commands in this context configure two SR-MPLS adjacency SIDs per interface.

Platforms

All

Context

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

[Tree] (config>router>mpls>lsp>auto-bandwidth adjust-down)

Full Context

configure router mpls lsp-template auto-bandwidth adjust-down

configure router mpls lsp auto-bandwidth adjust-down

Description

This command configures the minimum threshold for decreasing the bandwidth of an LSP based on active measurement of LSP bandwidth.

The no form of this command is equivalent to adjust-down 5.

Default

adjust-down 5 bw 0

Parameters

percent

Specifies the minimum difference between the current bandwidth reservation of the LSP and the (measured) maximum average data rate, expressed as a percentage of the current bandwidth, for decreasing the bandwidth of the LSP.

Values

1 to 100

bandwidth-in-mbps

Specifies the minimum difference between the current bandwidth reservation of the LSP and the (measured) maximum average data rate, expressed as an absolute bandwidth (Mb/s), for decreasing the bandwidth of the LSP.

Values

0 to 6400000

Platforms

All

Context

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

[Tree] (config>router>mpls>lsp>auto-bandwidth adjust-up)

Full Context

configure router mpls lsp-template auto-bandwidth adjust-up

configure router mpls lsp auto-bandwidth adjust-up

Description

This command configures the minimum threshold for increasing the bandwidth of an LSP based on active measurement of LSP bandwidth.

The no form of this command is equivalent to adjust-up 5.

Default

adjust-up 5 bw 0

Parameters

percent

Specifies the minimum difference between the current bandwidth reservation of the LSP and the (measured) maximum average data rate, expressed as a percentage of the current bandwidth, for increasing the bandwidth of the LSP.

Values

1 to 100

bandwidth-in-mbps

Specifies the minimum difference between the current bandwidth reservation of the LSP and the (measured) maximum average data rate, expressed as an absolute bandwidth (Mb/s), for increasing the bandwidth of the LSP

Values

0 to 6400000

Platforms

All

Context

[Tree] (admin)

Full Context

admin

Description

Commands in this context configure administrative system parameters. Only authorized users can execute the commands in the admin context.

Platforms

All

Context

[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle admin-bw)

[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>channel admin-bw)

[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>channel>src-override admin-bw)

Full Context

configure mcast-management multicast-info-policy bundle admin-bw

configure mcast-management multicast-info-policy bundle channel admin-bw

configure mcast-management multicast-info-policy bundle channel source-override admin-bw

Description

This command specifies an administrative bandwidth for multicast channels. The specified bandwidth rate can be used by the multicast ingress path manger, multicast CAC manager or multicast ECMP manager.

The kbps value is closely tied to the bw-activity command. When the bw-activity command is set to use-admin-bw, the multicast ingress path manager uses the configured administrative bandwidth value as the managed ingress bandwidth. The admin-bw value must be defined for the bw-activity use-admin-bw command to succeed. Once the bw-activity command is set to use the admin-bw value, the value cannot be set to 0 and the no admin-bw command fails. Setting the bw-activity command to dynamic (the default setting), breaks the association between the commands.

The no form of this command restores the default value for admin-bw. If the command is executed in the channel context, the channels administrative bandwidth value is set to null. If the command is executed in the source-override context, the source override administrative bandwidth value is set to null.

Parameters

kbps

Specifies the administrative bandwidth for multicast channels.

Values

1 to 40000000 kb/s

Bundle default:	0
Channel default:	Null (undefined)
Source-override default:	Null (undefined)

Override sequence — The channel setting overrides the bundle setting. The source-override setting overrides the channel and bundle settings.

Platforms

All

Context

[Tree] (config>mcast-mgmt>bw-plcy admin-bw-threshold)

Full Context

configure mcast-management bandwidth-policy admin-bw-threshold

Description

This command defines at which bandwidth rate a multicast channel configured to use an administrative rate starts and stop using that rate as the in-use ingress bandwidth when managing ingress multicast paths. This parameter only applies to channels that are configured to use the admin-bw rate with the bw-activity use-admin-bw command (both are configured in the multicast-info-policy associated with the channel context).

To be effective, the admin-bw-threshold value must be less than the channels configured admin-bw. If the administrative bandwidth configured on the channel is less than the administrative bandwidth threshold defined in the bandwidth policy, the admin-bw value is ignored for ingress multicast path management and the system continually uses the dynamic ingress bandwidth associated with the channel. Since the value is defined in the bandwidth-policy and the channel admin-bw value is defined in the multicast-info-policy, it is not possible to pre-determine that a given administrative bandwidth value is less than an administrative bandwidth threshold. Since a typical administrative bandwidth threshold is set significantly lower than any administrative bandwidth values, this corner case is not expected to be prevalent. However, if the case does arise in a production environment, no ill behavior is expected as the threshold is simply a tuning parameter used to detect when the bandwidth associated with a channel has risen above any OAM or background type traffic.

While a channel that is configured to the use-admin-bw parameter (in the bw-activity command) current bandwidth is less than the admin-bw-threshold, the system treats the channel as a dynamic type channel. Once the threshold is crossed, the system immediately allocates the full admin-bw value to the channel and manages the ingress multicast path accordingly. If the bandwidth monitored on the channel rises above the admin-bw value, the system reverts to dynamic bandwidth management operation. If the bandwidth drops below the admin-bw value, but is above the admin-bw-threshold, the system uses the admin-bw value. If the bandwidth drops below the admin-bw-threshold, the system goes back to dynamic bandwidth management operation.

This command has no effect on multicast ECMP or egress CAC management operations.

The no form of this command reverts to the default, which is 10 kb/s.

Parameters

kilobits-per-second

Specifies the defines the rate at which channels configured to use administrative bandwidths change from dynamic bandwidth management to using the channels configured administrative bandwidth. The parameter is expressed as an integer value and represents multiples of 1,000 bits per second. A value of 3000 indicates 3,000,000 bits per second.

Values

1 to 40,000,000

Platforms

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

Context

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

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

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

[Tree] (config>router>mpls>interface admin-group)

Full Context

configure service vprn interface if-attribute admin-group

configure service ies interface if-attribute admin-group

configure router interface if-attribute admin-group

configure router mpls interface admin-group

Description

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

Each single operation of the admin-group command allows a maximum of five (5) groups to be specified at a time. However, a maximum of 32 groups can be added to a given interface through multiple operations. Once an admin group is bound to one or more interface, its value cannot be changed until all bindings are removed.

The configured admin-group membership will be applied in all levels or areas the interface is participating in. The same interface cannot have different memberships in different levels or areas.

Only the admin groups bound to an MPLS interface are advertised 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 admin-group memberships of an interface. The user can also delete all memberships of an interface by not specifying a group name.

Default

no admin-group

Parameters

group-name

Specifies up to five groups, each up to 32 characters. The association of group name and value should be unique within an IP/MPLS domain. Each single operation of the admin-group command allows a maximum of 5 groups to be specified. However, a maximum of 32 groups can be added to a given interface through multiple operations.

Platforms

All

Context

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

Full Context

configure router if-attribute admin-group

Description

This command defines an Administrative Group (AG) that can be associated with an IP or MPLS interface.

AGs, also known as affinity, are used to tag IP and MPLS interfaces that share a specific characteristic with the same identifier. For example, an AG identifier can represent:

• all links that connect to core routers
• all links that have a bandwidth higher than 10 Gb
• all links that are dedicated to a specific service

First configure locally on each router the name and identifier of each AG. A maximum of 32 AGs can be configured per system.

After configuring the router name and identifier, configure the AG membership of an interface. You can apply AGs to a IES, VPRN, network IP, or MPLS interface.

When applied to MPLS interfaces, the interfaces can be included or excluded in the LSP path definition by inferring the AG name. CSPF computes a path that satisfies the AG include and exclude constraints.

When applied to IES, VPRN, or network IP interfaces, the interfaces can be included or excluded in the route next-hop selection by inferring the AG name in a route next-hop policy template applied to an interface or a set of prefixes.

The following provisioning rules apply to the AG configuration. The system rejects the creation of an AG:

• if the name of the AG is the same as that of an existing group, even if the new AG group value is different from the existing group value
• if the AG reuses the same group value but with a different name from an existing group

Only the AGs 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.

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 or MPLS domain.

Values

0 to 31 – Specifies the value range to use with link LFA next-hop policies or is used as a link color (AG or EAG) with Segment Routing Flex-Algorithms.

32 to 255 – Specifies the value range to use when the EAG is used as a link color with Segment Routing Flex-Algorithms. This higher range fails if used for other applications, such as LFA next-hop policies.

Platforms

All

Context

[Tree] (config>router>fad>flex-algo>exclude admin-group)

Full Context

configure router flexible-algorithm-definitions flex-algo exclude admin-group

Description

This command configures an administrative group link that will be excluded from the topology graph of the flexible algorithm. If multiple administrative groups are configured, they are all excluded from the topology graph.

Administrative groups are attributes associated with a link. Frequently these administrative groups are described as link colors.

The no form of this command removes the admin-group from being excluded from the topology graph.

Default

no admin-group

Parameters

admin-group

Configures an administrative group link to exclude from the topology graph of the configured FAD.

Platforms

All

Context

[Tree] (config>router>fad>flex-algo>include-all admin-group)

Full Context

configure router flexible-algorithm-definitions flex-algo include-all admin-group

Description

This command configures an administrative group link that will be included in the topology graph of the defined FAD. If multiple administrative groups are configured, groups must be present in a link before the link is included in the flexible algorithm topology graph.

The no form of this command removes the specified admin-group from being included in the topology graph.

Default

no admin-group

Parameters

admin-group

Configures an administrative group to include in topology graph of the configured FAD.

Platforms

All

Context

[Tree] (config>router>fad>flex-algo>include-any admin-group)

Full Context

configure router flexible-algorithm-definitions flex-algo include-any admin-group

Description

This command configures an administrative group link that will be included in the topology graph of the configured FAD. If multiple administrative groups are configured, at least one of the administrative groups must be present in a link before the link is included into the flexible algorithm topology graph.

The no form of this command removes the admin-group from being included in the topology graph.

Default

no admin-group

Parameters

admin-group

Configures an administrative group to include in the topology graph of the configured FAD.

Platforms

All

Context

[Tree] (config>router>mpls admin-group-frr)

Full Context

configure router mpls admin-group-frr

Description

This command enables the use of the admin-group constraints in the association of a manual or dynamic bypass LSP with the primary LSP path at a Point-of-Local Repair (PLR) node.

When this command is enabled, each PLR node reads the admin-group constraints in the FAST_REROUTE object in the Path message of the LSP primary path. If the FAST_REROUTE object is not included in the Path message, then the PLR will read the admin-group constraints from the Session Attribute object in the Path message.

If the PLR is also the ingress LER for the LSP primary path, then it just uses the admin-group constraint from the LSP and/or path level configurations.

The PLR node then uses the admin-group constraints along with other constraints, such as hop-limit and SRLG, to select a manual or dynamic bypass among those that are already in use.

If none of the manual or dynamic bypass LSP satisfies the admin-group constraints, and/or the other constraints, the PLR node will request CSPF for a path that merges the closest to the protected link or node and that includes or excludes the specified admin-group IDs.

If the user changes the configuration of the above command, it will not have any effect on existing bypass associations. The change will only apply to new attempts to find a valid bypass.

The no form of this command disables the use of administrative group constraints on a FRR backup LSP at a PLR node.

Default

no frr-admin-group

Platforms

All

Context

[Tree] (config>system>security>password admin-password)

Full Context

configure system security password admin-password

Description

This command allows a user (with admin permissions) to configure a password that enables a user to become an administrator.

This password is valid only for one session. When enabled, no authorization to TACACS+ or RADIUS is performed and the user is locally regarded as an admin user.

This functionality can be enabled in two contexts:

config>system>security>password>admin-password

<global> enable-admin

If the admin-password is configured in the config>system>security>password context, then any user can enter the special mode by entering the enable-admin command.

enable-admin is in the default profile. By default, all users are given access to this command.

After the enable-admin command is entered, the user is prompted for a password. If the password matches, user is given unrestricted access to all the commands.

The minimum length of the password is determined by the minimum-length command. The complexity requirements for the password are determined by the complexity command.

The usernames and passwords in the FTP and TFTP URLs will not be sent to the authorization or accounting servers when the file>copy source-url dest-url command is executed.

For example:

file copy ftp://test:secret@10.20.31.79/test/srcfile cf1:\destfile

In this example, the username 'test' and password 'secret' will not be sent to the AAA servers (or to any logs). They will be replaced with ''****''.

The no form of this command removes the admin password from the configuration.

Default

no admin-password

Parameters

password

Configures the password that enables a user to become a system administrator. The maximum length can be up to 56 characters if unhashed, 60 characters if hashed with bcrypt, from 87 to 92 characters if hashed with sha2-pbkdf2, 32 characters if the hash keyword is specified, or 54 characters if the hash2 keyword is specified. The unhashed cleartext password form should meet all the requirements that are defined by the complexity command.

hash

Specifies the key is entered in an encrypted form. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form or hashed with bcrypt or PBKDF2. For security, all keys are stored in the configuration file in hashed form (using bcrypt or PBKDF2, depending on the hashing configuration parameter) or, for backward compatibility, can be stored in encrypted form with the hash or hash2 parameter specified.

hash2

Specifies the key is entered in a more complex encrypted form that involves more variables than the key value alone, meaning that the hash2 encrypted variable cannot be copied and pasted. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form or hashed with bcrypt or PBKDF2. For security, all keys are stored in the configuration file in hashed form (using bcrypt or PBKDF2, depending on the hashing configuration parameter) or, for backward compatibility, can be stored in encrypted form with the hash or hash2 parameter specified.

Platforms

All

Context

[Tree] (config>service>vprn>l2tp>group>tunnel>mlppp admin-state)

[Tree] (config>router>l2tp>group>tunnel>mlppp admin-state)

Full Context

configure service vprn l2tp group tunnel mlppp admin-state

configure router l2tp group tunnel mlppp admin-state

Description

This command enables MLPPP for this tunnel group and is applicable only to LNS.

The tunnel can be explicitly activated (if the parent group is in a no shutdown state) or deactivated by the up and down keywords.

If the admin state is not configured, the tunnel inherits its administrative state from its parent (group).

The no form of this command causes the tunnel administrative state to be inherited from the group.

Parameters

up

Specifies that the tunnel is to be administratively up.

down

Specifies that the tunnel is to be administratively down.

Platforms

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

Context

[Tree] (config>system>management-interface>cli>md-cli>environment>info-output>always-display admin-state)

Full Context

configure system management-interface cli md-cli environment info-output always-display admin-state

Description

This command configures that the values of the admin-state elements in the info output (without the detail option) are always displayed, even if they are the default values.

The no form of this command excludes the values of the admin-state elements from the info output display.

Default

no admin-state

Platforms

All

Context

[Tree] (config>port>ethernet>lldp>dstmac admin-status)

Full Context

configure port ethernet lldp dest-mac admin-status

Description

This command configures LLDP transmission/reception frame handling.

Default

admin-status disabled

Parameters

rx

Specifies the LLDP agent will receive, but will not transmit LLDP frames on this port.

tx

Specifies that the LLDP agent will transmit LLDP frames on this port and will not store any information about the remote systems connected.

tx-rx

Specifies that the LLDP agent transmits and receives LLDP frames on this port.

disabled

Specifies that the LLDP agent does not transmit or receive LLDP frames on this port. If there is remote systems information which is received on this port and stored in other tables, before the port's admin status becomes disabled, then the information will naturally age out.

Platforms

All

Context

[Tree] (config>lag>lldp-member-template>dstmac admin-status)

Full Context

configure lag lldp-member-template dest-mac admin-status

Description

This command configures the LLDP transmission and reception frame handling.

Default

admin-status disabled

Parameters

rx

Keyword to specify that the LLDP agent receives, but does not transmit LLDP frames on this port.

tx

Keyword to specify that the LLDP agent transmits LLDP frames on this port and does not store any information about the remote systems connected.

tx-rx

Keyword to specify that the LLDP agent transmits and receives LLDP frames on this port.

disabled

Keyword to specify that the LLDP agent does not transmit or receive LLDP frames on this port. If remote system information is received on this port and stored in other tables before the administrative status of the port becomes disabled, the information naturally ages out.

Platforms

All

Context

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

[Tree] (config>router>mpls>lsp admin-tag)

Full Context

configure router mpls lsp-template admin-tag

configure router mpls lsp admin-tag

Description

This assigns an administrative tag to an LSP. The administrative tag can be used to enable routes with certain administrative tags to resolve using LSPs of matching administrative tags.

Up to four tags can be assigned to an LSP.

The administrative tag must exist under config>router>admin-tags.

The no form of this command removes the administrative tag.

Parameters

tag-value

The value of the admin-tag, up to 32 characters.

Platforms

All

Context

[Tree] (config>router>admin-tags admin-tag)

Full Context

configure router admin-tags admin-tag

Description

This command configures an admin tag value in the nodal LSP administrative tag database.

Up to 256 admin tags can be configured.

The no form of this command removes the admin tag.

Parameters

tag

The value of the administrative tag, up to 32 characters.

Platforms

All

Context

[Tree] (config>router>policy-options>policy-statement>default-action admin-tag-policy)

[Tree] (config>router>policy-options>policy-statement>entry>action admin-tag-policy)

Full Context

configure router policy-options policy-statement default-action admin-tag-policy

configure router policy-options policy-statement entry action admin-tag-policy

Description

This command assigns a route admin tag policy as an action in a route policy.

The admin tag policy must exist under config>router>admin-tags.

The no form of this command removes the admin tag policy.

Parameters

policy-name

Specifies the name of the admin tag policy, up to 64 characters.

Platforms

All

Context

[Tree] (config>router admin-tags)

Full Context

configure router admin-tags

Description

Commands in this context configure admin tags and router admin tag policy templates used for route resolution to LSPs.

Platforms

All

Context

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

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

Full Context

configure router mpls lsp adspec

configure router mpls lsp-template adspec

Description

When enabled, the ADSPEC object will be included in RSVP messages for this LSP. The ADSPEC object is used by the ingress LER to discover the minimum value of the MTU for links in the path of the LSP. By default, the ingress LER derives the LSP MTU from that of the outgoing interface of the LSP path.

A bypass LSP always signals the ADSPEC object since it protects both primary paths which signal the ADSPEC object and primary paths which do not. This means that MTU of LSP at ingress LER may change to a different value from that derived from the outgoing interface even if the primary path has ADSPEC disabled.

Default

no adspec — No ADSPEC objects are included in RSVP messages.

Platforms

All

Context

[Tree] (config>router>ldp>session-params>peer adv-adj-addr-only)

Full Context

configure router ldp session-parameters peer adv-adj-addr-only

Description

This command provides a means for an LDP router to advertise only the local IPv4 or IPv6 interfaces it uses to establish hello adjacencies with an LDP peer. By default, when a router establishes an LDP session with a peer, it advertises in an LDP Address message the addresses of all local interfaces to allow the peer to resolve LDP FECs distributed by this router. Similarly, a router sends a Withdraw Address message to of all its peers to withdraw a local address if the corresponding interface went down or was deleted.

This new option reduces CPU processing when a large number of LDP neighbors come up or go down. The new CLI option is strongly recommended in mobile backhaul networks where the number of LDP peers can be very large.

The no form of this command reverts LDP to the default behavior of advertising all local interfaces.

Platforms

All

Context

[Tree] (config>qos adv-config-policy)

Full Context

configure qos adv-config-policy

Description

Commands in this context configure an advanced QoS policy. This command contains only queue and policer child control parameters within a child-control node.

The parameters within the child-control node are intended to allow more precise control of the method that hierarchical virtual scheduling employs to emulate the effect of a scheduling context upon a member child queue or policer.

When a policy is created, it may be applied to a queue or policer defined within a sap-egress or sap-ingress QoS policy. It may also be applied to a queue or policer defined within an ingress or egress queue-group template. When a policy is currently associated with a QoS policy or template, the policy may be modified but not deleted (even in the event that the QoS policy or template is not in use).

While the system maintains default values for the advanced configuration parameters, no default adv-config-policy exists.

The no form of this command removes the specified advanced policy.

Parameters

policy-name

The name of the advanced QoS policy. A policy-name must be specified and conform to the policy naming guidelines. If the specified name does not exist, the optional create keyword requirements are met and the total number of policies per system will not be exceeded, an adv-config-policy of that name will be created. If the specified name does exist, the system will switch context to that adv-config-policy for the purpose of modification of the policy’s contents.

Values

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

Platforms

All

Context

[Tree] (config>qos>sap-ingress>queue adv-config-policy)

[Tree] (config>qos>sap-egress>queue adv-config-policy)

[Tree] (config>qos>sap-ingress>policer adv-config-policy)

[Tree] (config>qos>sap-egress>policer adv-config-policy)

Full Context

configure qos sap-ingress queue adv-config-policy

configure qos sap-egress queue adv-config-policy

configure qos sap-ingress policer adv-config-policy

configure qos sap-egress policer adv-config-policy

Description

This command specifies the advanced QoS policy. The advanced QoS policy contains only queue and policer child control parameters within a child-control node.

When a policy is created, it may be applied to a queue or policer defined within a sap-egress or sap-ingress QoS policy. It may also be applied to a queue or policer defined within an ingress or egress queue-group template. When a policy is currently associated with a QoS policy or template, the policy may be modified but not deleted (even in the event that the QoS policy or template is not in use).

The no form of this command removes the specified advanced policy.

Default

no adv-config-policy

Parameters

policy-name

The name of the advanced QoS policy.

Values

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

Platforms

All

• configure qos sap-ingress queue adv-config-policy
• configure qos sap-egress queue adv-config-policy

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

• configure qos sap-egress policer adv-config-policy
• configure qos sap-ingress policer adv-config-policy

Context

[Tree] (config>qos>qgrps>egr>qgrp>queue adv-config-policy)

[Tree] (config>qos>qgrps>ing>qgrp>policer adv-config-policy)

[Tree] (config>qos>qgrps>ing>qgrp>queue adv-config-policy)

[Tree] (config>qos>qgrps>egr>qgrp>policer adv-config-policy)

Full Context

configure qos queue-group-templates egress queue-group queue adv-config-policy

configure qos queue-group-templates ingress queue-group policer adv-config-policy

configure qos queue-group-templates ingress queue-group queue adv-config-policy

configure qos queue-group-templates egress queue-group policer adv-config-policy

Description

This command specifies the name of the advanced configuration policy to be applied with this policer.

Parameters

adv-config-policy-name

Specifies an existing advanced configuration policy up to 32 characters.

Platforms

All

• configure qos queue-group-templates ingress queue-group queue adv-config-policy
• configure qos queue-group-templates egress queue-group queue adv-config-policy

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

• configure qos queue-group-templates egress queue-group policer adv-config-policy
• configure qos queue-group-templates ingress queue-group policer adv-config-policy

Context

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

Full Context

configure qos copy adv-config-policy

Description

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

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

Parameters

adv-config-policy

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

overwrite

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

Example:

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

Platforms

All

Context

[Tree] (config>router>ldp>session-params>peer adv-local-lsr-id)

[Tree] (config>router>ldp>targeted-session>peer-template adv-local-lsr-id)

Full Context

configure router ldp session-parameters peer adv-local-lsr-id

configure router ldp targeted-session peer-template adv-local-lsr-id

Description

This command advertises a local LSR ID over a specified LDP session.

Advertisement of a local LSR ID over a given LDP session is configured using the adv-local-lsr-id command in the peer session-parameters. If a user disables the adv-local-lsr-id command, then the system will withdraw the FEC for the local LSR ID.

The SR OS router uses the following rules when advertising a local LSR ID:

• If the session parameters have the default configuration and the targeted peer template has the default configuration, the local LSR ID is not advertised.

• If the session parameters have the default configuration but the targeted peer template has an explicit configuration for advertisement of the local LSR ID, the targeted peer template configuration is used.

• If the session parameters have an explicit configuration for advertisement of the local LSR ID but the targeted peer template has the default configuration, the session parameter configuration is used.

• If both the session parameters and the targeted peer template have an explicit configuration for advertisement of the local LSR ID, then the session parameter configuration is used.

The no form of this command withdraws the FEC for the local LSR ID.

Default

no adv-local-lsr-id

Platforms

All

Context

[Tree] (config>service>sdp adv-mtu-override)

Full Context

configure service sdp adv-mtu-override

Description

This command overrides the advertised VC-type MTU of all spoke-sdps of L2 services using this SDP-ID. When enabled, the router signals a VC MTU equal to the service MTU, which includes the Layer 2 header. It also allows this router to accept an MTU advertised by the far-end PE which value matches either its advertised MTU or its advertised MTU minus the L2 headers.

By default, the router advertises a VC-MTU equal to the L2 service MTU minus the Layer 2 header and always matches its advertised MTU to that signaled by the far-end PE router, otherwise the spoke-sdp goes operationally down.

When this command is enabled on the SDP, it has no effect on a spoke-sdp of an IES/VPRN spoke interface using this SDP-ID. The router continues to signal a VC MTU equal to the net IP interface MTU, which is min{ip-mtu, sdp operational path mtu - L2 headers}. The router also continues to make sure that the advertised MTU values of both PE routers match or the spoke-sdp goes operationally down.

The no form of the command disables the VC-type MTU override and returns to the default behavior.

Default

no adv-mtu-override

Platforms

All

Context

[Tree] (config>system>dhcp6 adv-noaddrs-global)

Full Context

configure system dhcp6 adv-noaddrs-global

Description

This command configures the different DHCPv6 applications to send the NoAddrsAvail Status-Code in DHCPv6 Advertise messages at the global DHCP message level.

By default, all applications send the NoAddrsAvail Status-Code in DHCPv6 Advertise messages at the IA_NA Option level.

Different applications for which NoAddrsAvail Status-Code in DHCPv6 Advertise messages can be configured at the global DHCP message level.

The only valid combination in current SR OS is adv-noaddrs-global esm-relay server.

The no form of this command reverts to the default.

Default

no adv-noaddrs-global. All applications send the NoAddrsAvail Status-Code in DHCPv6 Advertise messages at the IA_NA Option level.

Parameters

esm-proxy

Specifies the DHCPv6 proxy server on subscriber group-interfaces. Not supported in current SR OS.

esm-relay

Specifies the DHCPv6 relay on subscriber group-interfaces. Must be enabled together with the DHCPv6 server (server) application.

relay

Specifies the DHCPv6 relay on regular IES or VPRN interfaces. Not supported in current SR OS.

server

Specifies the DHCPv6 server. Must be enabled together with the DHCPv6 relay on subscriber interfaces (esm-relay) application.

Platforms

All

Context

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

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

Full Context

configure service epipe spoke-sdp adv-service-mtu

configure service vpls spoke-sdp adv-service-mtu

Description

This command configures the MTU value signaled in the targeted LDP for the spoke-SDP and is used to validate the value signaled by the far-end PE. If configured, this value is used instead of the service MTU. However, the configuration does not affect the locally enforced value, which is still based on the service MTU. This command cannot be configured on a spoke-SDP that is bound to an SDP with the adv-mtu-override command.

When configured, an adjusted service MTU is used. See the service-mtu command for more information.

The no form of this command removes the configuration.

Default

no adv-service-mtu

Parameters

octets

The size of the MTU in octets, expressed as a decimal integer.

Values

0 to 9782

Platforms

All

Context

[Tree] (config>service>epipe>bgp adv-service-mtu)

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

Full Context

configure service epipe bgp adv-service-mtu

configure service vpls bgp adv-service-mtu

Description

This command configures the Layer 2 MTU value (advertised for BGP signaling) or the MTU interface parameter (advertised for LDP signaling) for the service. The configured MTU information is used to validate the value signaled by the far-end PE. However, this configuration does not affect the locally enforced value, which is still based on the service MTU.

The no form of this command reverts to the default Layer 2 MTU value for BGP signaling or to the default MTU interface parameter for LDP signaling for the service, which uses an adjusted service-mtu value. See the service-mtu command for more information.

Default

no adv-service-mtu

Parameters

number

Specifies the size, in octets, of the Layer 2 MTU value to advertise for BGP signaling for the service.

Values

0 to 9782

Platforms

All

Context

[Tree] (config>service>ies>if>vpls>evpn>nd advertise)

[Tree] (config>service>ies>if>vpls>evpn>arp advertise)

Full Context

configure service ies interface vpls evpn nd advertise

configure service ies interface vpls evpn arp advertise

Description

This command enables the advertisement of static and dynamic ARP and ND entries that are installed in the ARP and ND cache into EVPN MAC/IP routes. This command must be used along with no learn-dynamic.

Default

no advertise

Parameters

static

Enables ARP/ND host routes to be created in the route table from EVPN ARP/ND entries

dynamic

Enables ARP/ND host routes to be created in the route table out of dynamic ARP/ND entries (learned from ARP/ND messages received from the hosts).

route-tag

Specifies the route tag that is added in the route table for ARP/ND host routes of type dynamic, or static. This tag can be matched on BGP VRF export and BGP peer export policies.

Values

1 to 255

Platforms

All

Context

[Tree] (config>service>vprn>if>vpls>evpn>arp advertise)

[Tree] (config>service>vprn>if>vpls>evpn>nd advertise)

Full Context

configure service vprn interface vpls evpn arp advertise

configure service vprn interface vpls evpn nd advertise

Description

This command enables the advertisement of static and dynamic ARP and ND entries that are installed in the ARP and ND cache into EVPN MAC/IP routes. This command must be used along with the no learn-dynamic command.

Default

no advertise

Parameters

static

Enables ARP or ND host routes to be created in the route table from EVPN ARP or ND entries

dynamic

Enables ARP or ND host routes to be created in the route table out of dynamic ARP or ND entries (learned from ARP or ND messages received from the hosts).

route-tag

Keyword to specify the route tag is added in the route table for ARP or ND host routes of type dynamic, or static. This tag can be matched on BGP VRF export and BGP peer export policies.

Values

1 to 255

interface-less-routing

Keyword to specify that the advertisement in EVPN MAC/IP advertisement routes include the label1 and route target of the R-VPLS EVPN service and the label2 value and route target of the EVPN interface-less instance in the linked VPRN.

bgp-evpn-instance

Keyword to specify the EVPN interface-less BGP instance from which the label and route target are taken when advertising the ARP or ND entry in an EVPN MAC/IP advertisement route.

Values

1 to 1

Platforms

All

Context

[Tree] (config>router>isis>flex-algos>flex-algo advertise)

[Tree] (config>router>ospf>flex-algos>flex-algo advertise)

Full Context

configure router isis flexible-algorithms flex-algo advertise

configure router ospf flexible-algorithms flex-algo advertise

Description

This command enables the advertisement of a locally configured Flexible Algorithm Definition (FAD).

A locally defined FAD is only advertised if it is administratively enabled. A router can advertise only a single locally defined FAD by using the fad-name as reference anchor.

The winning FAD used by a router must be consistent with the winning FAD on all other routers. This avoids routing loops and traffic blackholing. The winning FAD is selected using a tie-breaker algorithm that first selects the highest advertised FAD priority and next the highest system Id.

The no form of this command removes the advertisement of a flexible algorithm definition.

Default

no advertise

Parameters

fad-name

Configures the FAD name, up to 32 characters. By default, no locally configured FAD is advertised.

Platforms

All

Context

[Tree] (config>service>vpls>bind>evpn-mcast-gateway advertise)

Full Context

configure service vpls allow-ip-int-bind evpn-mcast-gateway advertise

Description

This command signals the OISM gateway function type in the Inclusive Multicast Ethernet Tag (IMET) routes.

Default

advertise mvpn-pim

Parameters

mvpn-pim

Specifies that the router signals the MVPN-to-OISM (MEG) and PIM-to-OISM (PEG) gateway capabilities.

mvpn-only

Specifies that the router signals the MVPN-to-OISM (MEG) gateway capabilities.

pim-only

Specifies that the router signals the PIM-to-OISM (PEG) gateway capabilities.

Platforms

All

Context

[Tree] (configure>service>vprn>bgp-evpn>srv6>evpn-link-bw advertise)

[Tree] (configure>service>vprn>bgp-evpn>mpls>evpn>evpn-link-bw advertise)

[Tree] (configure>service>vpls>bgp-evpn>ip-route-link-bw advertise)

[Tree] (configure>service>vprn>bgp-evpn>vxlan>evpn-link-bw advertise)

Full Context

configure service vprn bgp-evpn segment-routing-v6 evpn-link-bandwidth advertise

configure service vprn bgp-evpn mpls evpn-link-bandwidth advertise

configure service vpls bgp-evpn ip-route-link-bandwidth advertise

configure service vprn bgp-evpn vxlan evpn-link-bandwidth advertise

Description

This command enables the advertisement of the EVPN link bandwidth extended community along with the IP Prefix routes.

The no form of this command disables the advertisement of the EVPN link bandwidth extended community.

Default

no advertise

Parameters

weight

Specifies the weight advertised in the EVPN link bandwidth extended community for the advertised EVPN IP prefix routes for the service.

Values

1 to 128

weight dynamic

Keyword to specify that the weight is dynamically set based on the number of BGP PE-CE paths for the IP-Prefix that is advertised in an EVPN IP-Prefix route.

max-dynamic-weight

Specifies the maximum weight advertised in the EVPN link bandwidth extended community for the advertised EVPN IP-Prefix routes for the service. If weight dynamic is configured, the actual advertised weight is the minimum of the number of BGP PE-CE paths for the prefix and the configured maximum weight.

Values

1 to 128

Platforms

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

• configure service vprn bgp-evpn segment-routing-v6 evpn-link-bandwidth advertise

All

• configure service vprn bgp-evpn mpls evpn-link-bandwidth advertise
• configure service vpls bgp-evpn ip-route-link-bandwidth advertise

7750 SR-1, 7750 SR-s

• configure service vprn bgp-evpn vxlan evpn-link-bandwidth advertise

Context

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

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

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

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

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

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

Full Context

configure router bgp group neighbor bfd-strict-mode advertise

configure router bgp group bfd-strict-mode advertise

configure router bgp bfd-strict-mode advertise

configure service vprn bgp group neighbor bfd-strict-mode advertise

configure service vprn bgp group bfd-strict-mode advertise

configure service vprn bgp bfd-strict-mode advertise

Description

This command configures BGP to advertise the Strict-BFD capability to peers that are within scope of this command and meet the following requirements:

• The bfd-enable command that applies to the peer is enabled (through either configuration or inheritance).

• The interface associated with the peer has a valid BFD configuration.

When the preceding conditions are satisfied and two peers attempting to form a session both advertise the Strict-BFD capability, the BGP finite state machine in each router transitions the session state to established after the BFD session with the peer enters the up state.

The no form of this command prevents BGP from advertising the Strict-BFD capability to peers.

Default

no advertise

Parameters

seconds

Specifies the maximum time (in seconds) BGP waits for the BFD session to come up, provided that the Strict-BFD procedures apply to a session, and the negotiated BGP hold time is zero (no keepalives). If the negotiated BGP hold time is greater than zero, the holdtime parameter is not considered.

Values

1 to 65535

Default

30

Platforms

All

Context

[Tree] (config>router>ospf>flex-algos advertise-admin-group)

[Tree] (config>router>isis>flex-algos advertise-admin-group)

Full Context

configure router ospf flexible-algorithms advertise-admin-group

configure router isis flexible-algorithms advertise-admin-group

Description

This command configures the type of Aministrative Group (AG) or Extended Administrative Group (EAG) TLVs the router advertises as the Interior Gateway Protocol (IGP) link attribute. This command is configured for this IGP instance.

The no form of this command removes the configuration.

Default

prefer-ag

Parameters

prefer-ag

Keyword to specify that the router advertises the Administrative Group (AG) TLV as the IGP link attribute if the affinity bits in the configure router if-attribute admin-group value command are configured between 0 to 31. If no EAG (32 to 255) affinity bits are configured, only the AG TLV is advertised as the IGP link attribute.

If the affinity bits are configured in both the AG (0 to 31) and EAG (32 to 255) range, the router advertises both the AG and the EAG TLVs as the IGP link attributes.

eag-only

Keyword to specify that the router advertises only the EAG TLV as the IGP link attribute. No AG TLV is advertised if this keyword is configured.

ag-eag

Keyword to specify that the router can advertise both the AG and the EAG TLVs as the IGP link attributes, even without the affinity bit in the EAG range configured in the configure router if-attribute admin-group value command. If no affinity bit is configured in the AG range (0 to 31), the router prunes the AG TLV. Configuring this keyword allows for backward compatibility for vendor implementations that support only AG, while still supporting EAG.

Platforms

All

Context

[Tree] (config>service>pw-routing>local-prefix advertise-bgp)

Full Context

configure service pw-routing local-prefix advertise-bgp

Description

This command enables a given prefix to be advertised in MP-BGP for dynamic MS-PW routing.

The no form of this command will explicitly withdraw a route if it has been previously advertised.

Default

no advertise-bgp

Parameters

rd

Specifies an 8-octet route distinguisher associated with the prefix. Up to 4 unique route distinguishers can be configured and advertised for a given prefix though multiple instances of the advertise-bgp command. This parameter is mandatory.

Values

(6 bytes, other 2 Bytes of type will be automatically generated) asn:number1 (RD Type 0): 2bytes ASN and 4 bytes locally administered number ip-address:number2 (RD Type 1): 4bytes IPv4 and 2 bytes locally administered number;

community

An optional BGP communities attribute associated with the advertisement. To delete a previously advertised community, advertise-bgp route-distinguisher must be run again with the same value for the RD but excluding the community attribute.

Values

community	{2-byte-as-number:comm-va1}
2-byte-asnumber	0 to 65535
comm.-val	0 to 65535

Platforms

All

Context

[Tree] (config>port>ethernet>efm-oam>discovery advertise-capabilities)

Full Context

configure port ethernet efm-oam discovery advertise-capabilities

Description

This is the top level of the hierarchy which allows for the overriding of default advertising of capabilities to a remote peer.

Platforms

All

Context

[Tree] (config>router>ospf>te-opts advertise-delay)

Full Context

configure router ospf traffic-engineering-options advertise-delay

Description

This command configures the advertisement of link delay in the IGP LSDB within the OSPF-TE TLV attribute or when the Application Specific Link Attribute (ASLA) is enabled within the SR-TE ASLA.

When the router is configured with the configure router ospf traffic-engineering-options sr-te application-specific-link-attributes command to generate SR-TE ASLA attributes, link delay is advertised as a legacy RFC 3630 TE TLV when RSVP-TE is enabled and as an ASLA RFC 8920 TLV for SR-TE when MPLS is enabled for an interface.

SR OS accepts and handles both legacy RSVP-TE TLVs and ASLAs for the RSVP application. However, SR OS only advertises RFC 3630 legacy RSVP-TE TLVs (as recommended by RFC 8920) to avoid compatibility issues.

Default

no advertise-delay

Platforms

All

Context

[Tree] (config>router>isis>te advertise-delay)

Full Context

configure router isis traffic-engineering-options advertise-delay

Description

This command enables the advertisement of link delay in the IGP LSDB within legacy Traffic Engineering (TE) attributes in IS-IS or within the Application Specific Link Attribute (ASLA) when ASLA is enabled for SR-TE or RSVP-TE applications.

When application-link-attributes legacy command is configured for SR-TE or RSVP-TE, link delay is advertised as a legacy TE TLV with the ASLA legacy bit set.

The no form of this command disables link delay advertisement.

Default

no advertise-delay

Platforms

All

Context

[Tree] (config>router>bgp advertise-external)

Full Context

configure router bgp advertise-external

Description

This command allows BGP to advertise its best external route to a destination even when its best overall route is an internal route. Entering the command (or its no form) with no address family parameters is equivalent to specifying all supported address families.

The no form of this command disables Advertise Best External for the BGP family.

Default

no advertise-external

Parameters

ipv4

Enables the best-external advertisement for unlabeled unicast IPv4 routes.

ipv6

Enables the best-external advertisement for unlabeled unicast IPv6 routes.

label-ipv4

Enables the best-external advertisement for labeled-unicast IPv4 routes.

label-ipv6

Enables the best-external advertisement for labeled-unicast IPv6 routes.

Platforms

All

Context

[Tree] (config>subscr-mgmt>bgp-prng-plcy advertise-inactive)

Full Context

configure subscriber-mgmt bgp-peering-policy advertise-inactive

Description

This command enables the advertising of inactive BGP routers to other BGP peers.

By default, BGP only advertises BGP routes to other BGP peers if a given BGP route is chosen by the route table manager as the most preferred route within the system and is active in the forwarding plane. This command allows system administrators to advertise a BGP route even though it is not the most preferred route within the system for a given destination.

The no form of this command disables the advertising.

Platforms

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

Context

[Tree] (config>service>vprn>bgp>group advertise-inactive)

[Tree] (config>service>vprn>bgp advertise-inactive)

[Tree] (config>service>vprn>bgp>group>neighbor advertise-inactive)

Full Context

configure service vprn bgp group advertise-inactive

configure service vprn bgp advertise-inactive

configure service vprn bgp group neighbor advertise-inactive

Description

This command enables or disables the advertising of inactive BGP routers to other BGP peers.

By default, BGP only advertises BGP routes to other BGP peers if a given BGP route is chosen by the route table manager as the most preferred route within the system and is active in the forwarding plane. This command allows system administrators to advertise a BGP route even though it is not the most preferred route within the system for a given destination.

When the BGP advertise-inactive command is configured so that it applies to a BGP session it has the following effect on the IPv4, IPv6, mcast-ipv4, mcast-ipv6, label-IPv4 and label-IPv6 routes advertised to that peer:

• If the active route for the IP prefix is a BGP route then that route is advertised.

• If the active route for the IP prefix is a non-BGP route and there is at least one valid but inactive BGP route for the same destination then the best of the inactive and valid BGP routes is advertised unless the non-BGP active route is matched and accepted by an export policy applied to the session.

• If the active route for the IP prefix is a non-BGP route and there are no (valid) BGP routes for the same destination then no route is advertised for the prefix unless the non-BGP active route is matched and accepted by an export policy applied to the session.

Default

no advertise-inactive

Platforms

All

Context

[Tree] (config>router>bgp>group advertise-inactive)

[Tree] (config>router>bgp advertise-inactive)

[Tree] (config>router>bgp>group>neighbor advertise-inactive)

Full Context

configure router bgp group advertise-inactive

configure router bgp advertise-inactive

configure router bgp group neighbor advertise-inactive

Description

This command enables the advertising of inactive BGP routes to other BGP peers. By default, BGP only advertises BGP routes to other BGP peers if a given BGP route is chosen by the route table manager as the most preferred route within the system and is active in the forwarding plane. This command allows system administrators to advertise a BGP route even though it is not the used route within the system for a given destination.

The no form of this command disables the advertising of inactive BGP routers to other BGP peers.

Default

no advertise-inactive

Platforms

All

Context

[Tree] (config>port>aps advertise-interval)

Full Context

configure port aps advertise-interval

Description

This command specifies the time interval, in 100s of milliseconds, between 'I am operational' messages sent by both protect and working circuits to their neighbor for multi-chassis APS.

The advertise-interval value is valid only for a multi-chassis APS as indicated by the value of the neighbor command value if it is not set to 0.0.0.0.

Default

10

Parameters

advertise-interval

Specifies the time interval, in 100s of milliseconds, between 'I am operational' messages sent by both protect and working circuits to their neighbor for multi-chassis APS.

Values

10 to 650

Platforms

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

Context

[Tree] (config>service>vprn>bgp>group>neighbor advertise-ipv6-next-hops)

[Tree] (config>service>vprn>bgp advertise-ipv6-next-hops)

[Tree] (config>service>vprn>bgp>group advertise-ipv6-next-hops)

Full Context

configure service vprn bgp group neighbor advertise-ipv6-next-hops

configure service vprn bgp advertise-ipv6-next-hops

configure service vprn bgp group advertise-ipv6-next-hops

Description

When this command is configured, with the IPv4 option, so that it applies to a BGP session established on top of IPv6 transport, IPv4 BGP routes can be advertised with a true IPv6 address when originated or when next-hop-self (configured or automatic) is applied.

If an IPv4 route must originate or be advertised with a next-hop-self and the corresponding advertise-ipv6-next-hops command option does not apply to the session or if an appropriate extended-nh-encoding capability was not received from the remote peer, then the route is advertised with the IPv4 system address as the BGP next-hop.

If an IPv4 route is matched by a BGP export policy entry that tries to change the next hop to an IPv6 address and the corresponding advertise-ipv6-next-hops command option does not apply to the session or if an appropriate extended-nh-encoding capability was not received from the remote peer, then the route is handled as though it was rejected by the policy entry.

This command has no effect on sessions established over IPv4 transport.

The no form of this command reverts to the default.

Default

no advertise-ipv6-next-hops

Parameters

ipv4

Allows IPv4 unicast routes to be advertised to IPv6-transport peers with an IPv6 address as the BGP next-hop in cases of route origination or next-hop-self (configured or automatic). It also allows export policies to change the BGP next-hop of an IPv4 route to an IPv6 address. All of these cases require the remote peer to advertise the necessary extended NH encoding capability. It may be necessary to configure the forward-ipv4-packets command under the appropriate interface>ipv6 contexts in order to enable datapath support for these control plane exchanges.

Platforms

All

Context

[Tree] (config>router>bgp>group advertise-ipv6-next-hops)

[Tree] (config>router>bgp advertise-ipv6-next-hops)

[Tree] (config>router>bgp>group>neighbor advertise-ipv6-next-hops)

Full Context

configure router bgp group advertise-ipv6-next-hops

configure router bgp advertise-ipv6-next-hops

configure router bgp group neighbor advertise-ipv6-next-hops

Description

This command applies to a BGP session established on top of IPv6 transport; BGP routes belonging to the specified families can be advertised with a true IPv6 address when originated or when next-hop-self (configured or automatic) is applied.

This command has no effect on routes advertised to IPv4 peers.

When this command is not enabled, the following considerations apply:

• If a VPN IPv6 or label IPv6 route needs to be originated or advertised with next-hop-self to an IPv6 transport peer the route is advertised with the IPv4 system address as BGP next-hop (encoded as an IPv4-mapped IPv6 address).

• If a VPN-IPv4 or label IPv4 route needs to be originated or advertised with next-hop-self or if an appropriate extended-nh-encoding capability was not received from the remote peer, the route is advertised with the IPv4 system address as the BGP next-hop.

• If a VPN IPv4 or label IPv4 route is matched by a BGP export policy entry that tries to change the next-hop to an IPv6 address and an appropriate extended-nh-encoding capability was not received from the remote peer, the route is handled as though it was rejected by the policy entry.

The no form of this command disables the setting of next hops to a global IPv6 address for the family.

Default

no advertise-ipv6-next-hops

Parameters

vpn-ipv6

Allows VPN IPv6 routes to be advertised to IPv6 transport peers with an IPv6 address as the BGP next-hop in cases of route origination or next-hop-self (configured or automatic).

label-ipv6

Allows label IPv6 routes to be advertised to IPv6 transport peers with an IPv6 address as the BGP next-hop in cases of route origination or next-hop-self (configured or automatic).

vpn-ipv4

Allows VPN IPv4 routes to be advertised to IPv6 transport peers with an IPv6 address as the BGP next-hop in cases of route origination or next-hop-self (configured or automatic). It also allows export policies to change the BGP next-hop of a VPN IPv4 route to an IPv6 address. All of these cases require the remote peer to advertise the necessary extended NH encoding capability.

label-ipv4

Allows label IPv4 routes to be advertised to IPv6 transport peers with an IPv6 address as the BGP next-hop in cases of route origination or next-hop-self (configured or automatic). It also allows export policies to change the BGP next-hop of a label IPv4 route to an IPv6 address. All of these cases require the remote peer to advertise the necessary extended NH encoding capability.

ipv4

Instructs BGP to advertise an extended NH encoding capability for NLRI AFI=1, NLRI SAFI=1 and next-hop AFI=2.

evpn

Allows EVPN routes to be advertised to IPv6 transport peers.

Platforms

All

Context

[Tree] (config>router>policy-options>policy-statement>default-action advertise-label)

[Tree] (config>router>policy-options>policy-statement>entry>action advertise-label)

Full Context

configure router policy-options policy-statement default-action advertise-label

configure router policy-options policy-statement entry action advertise-label

Description

This command configures the label allocation method for advertised routes. The effect of the advertise-label command depends on the context where the associated policy is applied.

Use the per-prefix option and configure the command in the default action or entry-specific action of a VRF export policy to advertise every qualifying matched route with a per-prefix label in the resulting VPN-IP routes. In this situation, non-qualifying routes include local interface routes and BGP-VPN routes. The command overrides, for specific routes, the configured label-mode of the exporting VPRN service.

Use the per-prefix option and configure the command in the default action or entry-specific action of a BGP import policy to assign a per-prefix label to qualifying label-IPv4 and label-IPv6 routes when:

• these routes are the best path for their prefix in the respective RIB

• there is a BGP next-hop change

A label-IPv4 or label-IPv6 route advertised with a pre-prefix label supports ECMP forwarding across multiple BGP next-hops.

The pop option is applicable in route-table-import policies. The advertised BGP label is programmed for a pop operation when:

• a /32 IPv4 static, OSPF, or IS-IS route is matched and accepted by a label-IPv4 or label-IPv6 RIB route-table-import policy entry or default-action with this command

• the route is a candidate to be advertised as a label-IPv4 or label-IPv6 route (due to a BGP export policy)

When the label-IPv4 RIB imports a /32 static, OSPF, or IS-IS route and then exports the route as a BGP route, the default behavior is to program a swap operation in the datapath, which swaps the BGP label with the tunnel label that takes traffic to the destination of the /32 route.

The pop-and-forward option is applicable in route-table-import policies, when these policies match an unlabeled BGP route and apply this policy action.

Use the pop-and-forward option to program the label that is advertised in the BGP-LU route to forward the packet according to the resolution of the unlabeled route that triggered the origination of the BGP-LU route. The forwarding is done without an IP FIB lookup, which can be useful in situations where the IP FIB at the exit of the MPLS tunnel is not synchronized with the FIB at the head-end of the MPLS tunnel. The advertisement of a pop-and-forward label overrides the configuration to advertise label-ipv6 routes with an explicit null label and the configuration to advertise BGP-LU with a prefix SID attribute. Those features are not available when using the pop-and-forward label.

Default

no advertise-label

Parameters

per-prefix

Sets the per-prefix label allocation for matched routes. This takes effect only in VRF export policies and BGP import policies, and only for certain types of routes.

pop

Sets the pop label allocation for matched routes. This takes effect only in label-IPv4 route-table-import policies and only applies to /32 IPv4 routes that were learned through static configuration, OSPF, or IS-IS.

pop-and-forward

Sets the pop-and-forward label allocation for matched routes. This takes effect only when an unlabeled BGP IPv4 or IPv6 route is matched by a label-IPv4 or label-IPv6 route-table-import policy.

Platforms

All

Context

[Tree] (config>router>bgp>group>neighbor advertise-ldp-prefix)

Full Context

configure router bgp group neighbor advertise-ldp-prefix

Description

This command, when configured for a session that supports the IPv4 labeled-unicast address family, allows (subject to BGP export policies) active /32 LDP FEC prefixes to be advertised to the BGP peer with an RFC 8277 label, even though there may be BGP paths for the same prefix.

Default

no advertise-ldp-prefix

Platforms

All

Context

[Tree] (config>service>vpls>isid-policy>entry advertise-local)

Full Context

configure service vpls isid-policy entry advertise-local

Description

The no advertise-local option prevents the advertisement of any locally defined I-VPLS ISIDs or static-isids in the range in a B-VPLS. For I-VPLS services or static-isids that are primarily unicast traffic, the use-def-mcast and no advertise-local options allows the forwarding of ISID based multicast frames locally using the default multicast. The no advertise-local option also suppresses this range of ISIDs from being advertised in ISIS. When using the use-def-mcast and no advertise-local policies, the ISIDs configured under this static-isid declarations SPBM treats the ISIDs as belonging to the default tree.

Default

advertise-local

Platforms

All

Context

[Tree] (config>service>vprn>ospf>area advertise-ne-profile)

Full Context

configure service vprn ospf area advertise-ne-profile

Description

This command enables advertising of a specific NE profile using OSPFv2 LSA type 10 opaque.

The no version of this command disables advertising of NE profiles.

Default

no advertise-ne-profile

Parameters

name

Specifies the name of the NE profile to be advertised, up to 32 characters.

Platforms

All

Context

[Tree] (config>service>vprn>isis advertise-passive-only)

Full Context

configure service vprn isis advertise-passive-only

Description

This command enables IS-IS for the VPRN instance to advertise only prefixes that belong to passive interfaces.

The no form of this command disables IS-IS for the VPRN instance from advertising only prefixes that belong to passive interfaces.

Platforms

All

Context

[Tree] (config>router>isis advertise-passive-only)

Full Context

configure router isis advertise-passive-only

Description

This command enables and disables IS-IS to advertise only prefixes that belong to passive interfaces.

Default

no advertise-passive-only

Platforms

All

Context

[Tree] (config>service>vprn>isis advertise-router-capability)

[Tree] (config>service>vprn>isis>level advertise-router-capability)

Full Context

configure service vprn isis advertise-router-capability

configure service vprn isis level advertise-router-capability

Description

This command enables advertisement of a router's capabilities to its neighbors for informational and troubleshooting purposes. A new TLV as defined in RFC 4971 advertises the TE Node Capability Descriptor capability.

The parameters (area & as) control the scope of the capabilities advertisements.

The no form of this command disables this capability.

Default

no advertise-router-capability

Parameters

area

Capabilities are only advertised within the area of origin.

as

Capabilities are only advertised throughout the entire autonomous system.

Platforms

All

Context

[Tree] (config>service>vprn>ospf3>area>if advertise-router-capability)

[Tree] (config>service>vprn>ospf advertise-router-capability)

[Tree] (config>service>vprn>ospf>area>if advertise-router-capability)

[Tree] (config>service>vprn>ospf>area advertise-router-capability)

[Tree] (config>service>vprn>ospf3 advertise-router-capability)

Full Context

configure service vprn ospf3 area interface advertise-router-capability

configure service vprn ospf advertise-router-capability

configure service vprn ospf area interface advertise-router-capability

configure service vprn ospf area advertise-router-capability

configure service vprn ospf3 advertise-router-capability

Description

This command enables advertisement of a router's capabilities to its neighbors for informational and troubleshooting purposes. A Router Information (RI) LSA as defined in RFC 4970 advertises the following capabilities:

• OSPF graceful restart capable: no

• OSPF graceful restart helper: yes, when enabled

• OSPF Stub Router support: yes

• OSPF Traffic Engineering support: yes, when enabled

• OSPF point-to-point over LAN: yes

• OSPF Experimental TE: no

The parameters (link, area and as) control the advertisement scope of the router capabilities.

The no form of this command disables this capability.

Default

no advertise-router-capability

Parameters

link

Capabilities are only advertised over local link and not flooded beyond.

area

Capabilities are only advertised within the area of origin.

as

Capabilities are only advertised throughout the entire autonomous system.

Platforms

All

Context

[Tree] (config>router>isis advertise-router-capability)

Full Context

configure router isis advertise-router-capability

Description

This command enables advertisement of a router's capabilities to its neighbors for informational and troubleshooting purposes. A TLV as defined in RFC 4971 advertises the TE Node Capability Descriptor capability.

The parameters (area and as) control the scope of the capability advertisements.

The no form of this command disables this capability.

Parameters

area

Specifies to only advertise within the area of origin.

as

Specifies to advertise throughout the entire autonomous system.

Platforms

All

Context

[Tree] (config>router>isis>level advertise-router-capability)

Full Context

configure router isis level advertise-router-capability

Description

This command enables router advertisement capabilities.

The no form of this command disables router advertisement capabilities.

Default

advertise-router-capability

Platforms

All

Context

[Tree] (config>router>ospf advertise-router-capability)

[Tree] (config>router>ospf3 advertise-router-capability)

Full Context

configure router ospf advertise-router-capability

configure router ospf3 advertise-router-capability

Description

This command enables advertisement of a router's capabilities to its neighbors for informational and troubleshooting purposes. A Router Information (RI) LSA as defined in RFC 4970 advertises the following capabilities:

• OSPF graceful restart capable: no

• OSPF graceful restart helper: yes, when enabled

• OSPF stub router support: yes

• OSPF traffic engineering support: yes, when enabled

• OSPF point-to-point over LAN: yes

• OSPF experimental TE: no

The parameters (link, area and as) control the scope of the capability advertisements.

The no form of this command disables this capability.

Default

no advertise-router-capability

Parameters

link

capabilities are only advertised over local links and not flooded beyond.

area

capabilities are only advertised within the area of origin.

as

capabilities are advertised throughout the entire autonomous system.

Platforms

All

Context

[Tree] (config>router>ospf3>area>interface advertise-router-capability)

[Tree] (config>router>ospf3>area advertise-router-capability)

[Tree] (config>router>ospf>area>interface advertise-router-capability)

[Tree] (config>router>ospf>area advertise-router-capability)

Full Context

configure router ospf3 area interface advertise-router-capability

configure router ospf3 area advertise-router-capability

configure router ospf area interface advertise-router-capability

configure router ospf area advertise-router-capability

Description

This command enables advertisement of a router’s capabilities to its neighbors for informational and troubleshooting purposes. A Router Information (RI) LSA as defined in RFC 4970 advertises the following capabilities:

• OSPF graceful restart capable: no

• OSPF graceful restart helper: yes, when enabled

• OSPF stub router support: yes

• OSPF traffic engineering support: yes, when enabled

• OSPF point-to-point over LAN: yes

• OSPF experimental TE: no

The no form of this command disables this capability.

Default

advertise-router-capability

Platforms

All

Context

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

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

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

Full Context

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

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

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

Description

Commands in this context configure a solicit delay or a DHCPv6 preference option value to influence the advertise selection of DHCPv6 clients.

Platforms

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

Context

[Tree] (config>service>vprn>bgp>group>graceful-restart>long-lived advertise-stale-to-all-neighbors)

[Tree] (config>service>vprn>bgp>group>neighbor>graceful-restart>long-lived advertise-stale-to-all-neighbors)

[Tree] (config>service>vprn>bgp>graceful-restart>long-lived advertise-stale-to-all-neighbors)

Full Context

configure service vprn bgp group graceful-restart long-lived advertise-stale-to-all-neighbors

configure service vprn bgp group neighbor graceful-restart long-lived advertise-stale-to-all-neighbors

configure service vprn bgp graceful-restart long-lived advertise-stale-to-all-neighbors

Description

This command allows BGP routes marked as LLGR stale to be advertised to BGP peers that did not advertise the LLGR capability when the session was opened. The no version of this command causes advertisement behavior to follow the rule that stale routes cannot be advertised to a peer that does not understand or implement the LLGR capability. Stale routes are withdrawn towards such peers.

When this command is configured with the without-no-export option, LLGR stales routes can be advertised to any peer (EBGP or IBGP) that did not signal the LLGR capability. Towards IBGP and confederation-EBGP peers that did not advertise the LLGR capability, the LOCAL_PREFERENCE attribute in the advertised stale routes is automatically set to zero.

When this command is configured without the without-no-export option, LLGR stale routes are not advertised to any EBGP peer that did not signal the LLGR capability. Towards IBGP and confederation-EBGP peers that did not advertise the LLGR capability the LOCAL_PREFERENCE attribute in the advertised stale routes is automatically set to zero and a NO_EXPORT standard community is automatically added to the routes.

Default

no advertise-stale-to-all-neighbors

Parameters

without-no-export

Allows LLGR stale routes to be advertised to all peers, such that they can exit the local AS.

Platforms

All

Context

[Tree] (config>router>bgp>graceful-restart>long-lived advertise-stale-to-all-neighbors)

[Tree] (config>router>bgp>group>graceful-restart>long-lived advertise-stale-to-all-neighbors)

[Tree] (config>router>bgp>group>neighbor>graceful-restart>long-lived advertise-stale-to-all-neighbors)

Full Context

configure router bgp graceful-restart long-lived advertise-stale-to-all-neighbors

configure router bgp group graceful-restart long-lived advertise-stale-to-all-neighbors

configure router bgp group neighbor graceful-restart long-lived advertise-stale-to-all-neighbors

Description

This command allows BGP routes marked as LLGR stale to be advertised to BGP peers that did not advertise the LLGR capability when the session was opened.

When this command is configured with the without-no-export option, LLGR stale routes can be advertised to any peer (EBGP or IBGP) that did not signal the LLGR capability. Towards IBGP and confederation-EBGP peers that did not advertise the LLGR capability, the LOCAL_PREFERENCE attribute in the advertised stale routes is automatically set to zero.

When this command is configured without the without-no-export option, LLGR stale routes are not advertised to any EBGP peer that did not signal the LLGR capability. Towards IBGP and confederation-EBGP peers that did not advertise the LLGR capability the LOCAL_PREFERENCE attribute in the advertised stale routes is automatically set to zero and a NO_EXPORT standard community is automatically added to the routes.

The no version of this command causes advertisement behavior to follow the rule that stale routes cannot be advertised to a peer that does not understand or implement the LLGR capability. Stale routes are withdrawn towards such peers.

Default

no advertise-stale-to-all-neighbors

Parameters

without-no-export

Allows LLGR stale routes to be advertised to all peers, such that they can exit the local AS.

Platforms

All

Context

[Tree] (config>service>vprn>ospf>area>if advertise-subnet)

Full Context

configure service vprn ospf area interface advertise-subnet

Description

This command enables advertising point-to-point interfaces as subnet routes (network number and mask). When disabled, point-to-point interfaces are advertised as host routes.

This command is not supported in the OSPF3 context.

The no form of this command disables advertising point-to-point interfaces as subnet routes meaning they are advertised as host routes.

Default

advertise-subnet — Advertises point-to-point interfaces as subnet routes.

Platforms

All

Context

[Tree] (config>router>ospf>area>interface advertise-subnet)

Full Context

configure router ospf area interface advertise-subnet

Description

This command enables advertising point-to-point interfaces as subnet routes (network number and mask). When disabled, point-to-point interfaces are advertised as host routes.

The no form of this command disables advertising point-to-point interfaces as subnet routes meaning they are advertised as host routes.

Default

advertise-subnet

Platforms

All

Context

[Tree] (config>router>ospf advertise-tunnel-link)

[Tree] (config>router>isis advertise-tunnel-link)

Full Context

configure router ospf advertise-tunnel-link

configure router isis advertise-tunnel-link

Description

This command enables the forwarding adjacency feature. With this feature, IS-IS or OSPF advertises an RSVP LSP as a link so that other routers in the network can include it in their SPF computations. The RSVP LSP is advertised as an unnumbered point-to-point link and the link LSP or LSA has no Traffic Engineering opaque sub-TLVs, as per RFC 3906. An SR-TE LSP is not supported with forwarding adjacency.

The forwarding adjacency feature can be enabled independently from the IGP shortcut feature in CLI. If both igp-shortcut and advertise-tunnel-link options are enabled for a given IGP instance, then the advertise-tunnel-link takes precedence.

When the forwarding adjacency feature is enabled, each node advertises a p2p unnumbered link for each best metric tunnel to the router ID of any endpoint node. The node does not include the tunnels as IGP shortcuts in SPF computation directly. Instead, when the LSA or LSP that advertises the corresponding P2P unnumbered link is installed in the local routing database, the node performs an SPF using it like any other link LSA or LSP. The bidirectional check of the link requires that a link, regular or tunnel, exists in the reverse direction for the tunnel to be used in SPF.

The igp-shortcut option under the LSP name governs the use of the LSP with both the igp-shortcut and the advertise-tunnel-link options in IGP. In other words, the user can exclude a specific RSVP LSP from being used as a forwarding adjacency by entering the command config>router>mpls>lsp>no igp-shortcut.

Support is provided for resolving and forwarding IPv4 and IPv6 prefixes over IPv4 forwarding adjacency RSVP-TE LSP. Specifically, the forwarding adjacency feature supports family IPv4 in OSPFv2, family IPv6 in OSPFv3, families IPv4 and IPv6 in ISIS MT=0, and family IPv6 in ISIS MT=2.

In addition, both IPv4 and IPv6 SR-ISIS tunnels can be resolved and further tunneled over one or more RSVP-TE LSPs used as forwarding adjacencies. This is enabled by configuring both segment routing and forwarding adjacency features within an IS-IS instance in a multi-topology MT=0.

IS-IS forwarding adjacency using the advertise-tunnel-link command is not supported in combination with the IS-IS link bundling and the IS-IS metric link quality adjustment features.

The no form of this command disables forwarding adjacency and disables the advertisement of RSVP LSP into IGP.

Default

no advertise-tunnel-link

Platforms

All

Context

[Tree] (config>service>vprn>bgp>graceful-restart>long-lived advertised-stale-time)

[Tree] (config>service>vprn>bgp>group>graceful-restart>long-lived advertised-stale-time)

[Tree] (config>service>vprn>bgp>group>neighbor>graceful-restart>long-lived advertised-stale-time)

[Tree] (config>service>vprn>bgp>graceful-restart>long-lived>family advertised-stale-time)

[Tree] (config>service>vprn>bgp>group>neighbor>graceful-restart>long-lived>family advertised-stale-time)

[Tree] (config>service>vprn>bgp>group>graceful-restart>long-lived>family advertised-stale-time)

Full Context

configure service vprn bgp graceful-restart long-lived advertised-stale-time

configure service vprn bgp group graceful-restart long-lived advertised-stale-time

configure service vprn bgp group neighbor graceful-restart long-lived advertised-stale-time

configure service vprn bgp graceful-restart long-lived family advertised-stale-time

configure service vprn bgp group neighbor graceful-restart long-lived family advertised-stale-time

configure service vprn bgp group graceful-restart long-lived family advertised-stale-time

Description

This command sets the value of the long-lived stale time that is advertised by the router in its LLGR capability. When configured in the long-lived configuration context, advertised-stale-time applies to all AFI/SAFI in the advertised LLGR capability except for any AFI/SAFI with a family-specific override. A family-specific override is configured with the advertised-stale-time command in a family context.

The no version of this command sets the advertised-stale-time value to 24 hours (86400 seconds).

Default

no advertised-stale-time

Parameters

seconds

Specifies the advertised long-lived stale time in seconds.

Values

0 to 16777215

Platforms

All

Context

[Tree] (config>router>bgp>group>graceful-restart>long-lived advertised-stale-time)

[Tree] (config>router>bgp>group>graceful-restart>long-lived>family advertised-stale-time)

[Tree] (config>router>bgp>group>neighbor>graceful-restart>long-lived advertised-stale-time)

[Tree] (config>router>bgp>graceful-restart>long-lived advertised-stale-time)

[Tree] (config>router>bgp>graceful-restart>long-lived>family advertised-stale-time)

[Tree] (config>router>bgp>group>neighbor>graceful-restart>long-lived>family advertised-stale-time)

Full Context

configure router bgp group graceful-restart long-lived advertised-stale-time

configure router bgp group graceful-restart long-lived family advertised-stale-time

configure router bgp group neighbor graceful-restart long-lived advertised-stale-time

configure router bgp graceful-restart long-lived advertised-stale-time

configure router bgp graceful-restart long-lived family advertised-stale-time

configure router bgp group neighbor graceful-restart long-lived family advertised-stale-time

Description

This command sets the value of the long-lived stale time that is advertised by the router in its LLGR capability. When configured in the long-lived configuration context, advertised-stale-time applies to all AFI/SAFI in the advertised LLGR capability except for any AFI/SAFI with a family-specific override. A family-specific override is configured with the advertised-stale-time command in a family context.

The no version of this command sets the advertised-stale-time value to 24 hours (86400 seconds).

Default

no advertised-stale-time

Parameters

seconds

Specifies the advertised long-lived stale time in seconds.

Values

0 to 16777215

Platforms

All

Context

[Tree] (config>system>bluetooth advertising-timeout)

Full Context

configure system bluetooth advertising-timeout

Description

When the power is enabled, this command configures the pairing timeout interval for the Bluetooth device during which it advertises that it is ready to pair. If an external device does not complete the pairing within this time, then the pairing must be reinitiated.

The no form of this command disables the timeout.

Default

advertising-timeout 30

Parameters

seconds

Specifies the pairing timeout interval.

Values

30 to 3600

Platforms

7750 SR-1, 7750 SR-s, 7950 XRS-20e

Context

[Tree] (config>system>bluetooth advertising-timeout)

Full Context

configure system bluetooth advertising-timeout

Description

When the power is enabled, this timer controls the amount of time the Bluetooth device will advertise that is ready to pair. If an external device does not complete the pairing within this time, then the pairing must be re-initiated.

The no form of this command disables the timeout.

Default

advertising-timeout 30

Parameters

seconds

Specifies the paring timeout interval.

Values

30 to 3600

Platforms

7750 SR-1, 7750 SR-s, 7950 XRS-20e

Context

[Tree] (config>app-assure>group>http-enrich>field aes-initialization-vector)

Full Context

configure application-assurance group http-enrich field aes-initialization-vector

Description

This command configures the initialization vector that is used for the AES CBC encryption.

The no form of this command removes the initialization vector.

Default

no aes-initialization-vector

Parameters

hex-string

Specifies the AES initialization vector in 34 characters, that is, 0x followed by exactly 32 hexadecimal characters.

Platforms

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

Context

[Tree] (config>service>ies>if>sap>egress agg-rate)

[Tree] (config>service>ies>sub-if>grp-if>sap>egress agg-rate)

[Tree] (config>service>vprn>sub-if>grp-if>sap>egress agg-rate)

Full Context

configure service ies interface sap egress agg-rate

configure service ies subscriber-interface group-interface sap egress agg-rate

configure service vprn subscriber-interface group-interface sap egress agg-rate

Description

Commands in this context configure aggregation rate parameters. This command is used to control an HQoS aggregate rate limit. It is used in conjunction with the following parameter commands: rate, limit-unused-bandwidth, and queue-frame-based-accounting.

When specified under a Vport, the agg-rate, port-scheduler-policy and scheduler-policy commands are mutually exclusive. Changing between the use of a scheduler policy and the use of an agg-rate or port-scheduler-policy involves removing the existing command and applying the new command.

The no form of this command disables the aggregation rate.

Platforms

All

• configure service ies interface sap egress agg-rate

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

• configure service vprn subscriber-interface group-interface sap egress agg-rate
• configure service ies subscriber-interface group-interface sap egress agg-rate

Context

[Tree] (config>port>ethernet>access>egr>qgrp agg-rate)

[Tree] (config>port>ethernet>access>egr>vport agg-rate)

[Tree] (config>port>ethernet>network>egr>qgrp agg-rate)

Full Context

configure port ethernet access egress queue-group agg-rate

configure port ethernet access egress vport agg-rate

configure port ethernet network egress queue-group agg-rate

Description

This command controls an H-QoS aggregate rate limit. It is used in conjunction with the following parameter commands: rate, limit-unused-bandwidth, and queue-frame-based-accounting.

When specified under a Vport, the agg-rate rate, port-scheduler-policy and scheduler-policy commands are mutually exclusive. Changing between the use of a scheduler policy and the use of an agg-rate/port-scheduler-policy involves removing the existing command and applying the new command.

Platforms

All

Context

[Tree] (config>service>ipipe>sap>egress agg-rate)

[Tree] (config>service>epipe>sap>egress agg-rate)

[Tree] (config>service>cpipe>sap>egress agg-rate)

Full Context

configure service ipipe sap egress agg-rate

configure service epipe sap egress agg-rate

configure service cpipe sap egress agg-rate

Description

This command is used to control an HQoS aggregate rate limit. It is used in conjunction with the following parameter commands: rate, limit-unused-bandwidth, and queue-frame-based-accounting.

Platforms

All

• configure service ipipe sap egress agg-rate
• configure service epipe sap egress agg-rate

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

• configure service cpipe sap egress agg-rate

Context

[Tree] (config>service>vpls>sap>egress>encap-defined-qos>encap-group agg-rate)

[Tree] (config>service>template>vpls-sap-template>egress agg-rate)

[Tree] (config>service>vpls>sap>egress agg-rate)

Full Context

configure service vpls sap egress encap-defined-qos encap-group agg-rate

configure service template vpls-sap-template egress agg-rate

configure service vpls sap egress agg-rate

Description

This command is used to control an HQoS aggregate rate limit. It is used in conjunction with the following parameter commands: rate, limit-unused-bandwidth, and queue-frame-based-accounting.

Platforms

All

Context

[Tree] (config>service>vprn>if>sap>egress agg-rate)

Full Context

configure service vprn interface sap egress agg-rate

Description

This command is used to control an HQoS aggregate rate limit. It is used in conjunction with the following parameter commands: rate, limit-unused-bandwidth, and queue-frame-based-accounting.

Platforms

All

Context

[Tree] (config>service>cust>multi-service-site>egress agg-rate)

Full Context

configure service customer multi-service-site egress agg-rate

Description

Commands in this context control an HQoS aggregate rate limit. It is used in conjunction with the following parameter commands: rate, limit-unused-bandwidth, and queue-frame-based-accounting.

The no form of the command disables the aggregate rate limit parameters.

Platforms

All

Context

[Tree] (config>subscr-mgmt>sub-prof>egress agg-rate-limit)

Full Context

configure subscriber-mgmt sub-profile egress agg-rate-limit

Description

This command defines a subscriber aggregate limit when the subscriber profile is directly associated with an egress port based scheduler instead of a scheduler policy. The optional queue-frame-based-accounting keyword allows the subscriber queues to operate in the frame based accounting mode.

Once egress frame based accounting is enabled on the subscriber profile, all queues associated with the subscriber (created through the sla-profile associated with each subscriber host) will have their rate and CIR values interpreted as frame based values. When shaping, the queues will include the 12-byte Inter-Frame Gap (IFG) and 8-byte preamble for each packet scheduled out the queue. The profiling CIR threshold will also include the 20-byte frame encapsulation overhead. Statistics associated with the queue do not include the frame encapsulation overhead. Packet byte offset settings are not included in the applied rate when queue frame based accounting is configured, however the offsets are applied to the statistics.

The queue-frame-based-accounting keyword does not change the behavior of the egress-agg-rate-limit rate value. Since the egress-agg-rate-limit is always associated with egress port based scheduling and egress port based scheduling is dependent on frame based operation, the egress-agg-rate-limit rate is always interpreted as a frame based value.

Enabling queue-frame-based-accounting will not cause statistics for queues associated with the subscriber to be cleared.

The no form of this command removes both an egress aggregate rate limit and egress frame based accounting for all subscribers associated with the sub-profile. If a subscriber’s accounting mode is changed, the subscriber’s queue statistics are cleared.

Parameters

agg-rate

Specifies the egress aggregate rate.

Values

1 to 800000000, max

min-rate

Specifies the minimum rate of the minimum reserved bandwidth for unicast data traffic. Since minimum rate can oversubscribe subscriber bandwidth to guarantee a minimum bandwidth for unicast traffic, care must be taken in QoS provisioning to prioritize packets accordingly (downstream network elements such as the access node or aggregation nodes) when congestion occurs.

Values

0 to 800000000

queue-frame-based-accounting

Specifies whether to use frame-based accounting when evaluating the aggregation rate limit for the egress queues for this SAP.

Platforms

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

Context

[Tree] (config>port>ethernet>access>egress>vport agg-rate-limit)

Full Context

configure port ethernet access egress vport agg-rate-limit

Description

This command configures an aggregate rate for the Vport. This command is mutually exclusive with the port-scheduler-policy command.

The no form of this command reverts to the default.

Parameters

agg-rate

Specifies the rate limit for the Vport.

Values

max, 1 to 10000000

Platforms

All

Context

[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw>egress agg-rate-limit)

[Tree] (config>service>ies>sub-if>grp-if>wlan-gw>egress agg-rate-limit)

Full Context

configure service vprn subscriber-interface group-interface wlan-gw egress agg-rate-limit

configure service ies subscriber-interface group-interface wlan-gw egress agg-rate-limit

Description

This command configures an HQoS aggregate rate limit. It is used in conjunction with the following parameter commands: rate, limit-unused-bandwidth, and queue-frame-based-accounting.

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

Parameters

kilobits-per-second

Specifies the aggregate rate limit.

Values

1 to 100000000, max

Platforms

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

Context

[Tree] (config>subscr-mgmt>sub-prof>egr agg-rate-limit)

Full Context

configure subscriber-mgmt sub-profile egress agg-rate-limit

Description

This command configures a hardware-assisted HQoS aggregate rate limit.

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

Parameters

agg-rate

Specifies the aggregate rate limit in kb/s.

Values

1 to 800000000, max

min-rate

Specifies the minimum reserved bandwidth rate.

Values

0 to 800000000, max

queue-frame-based-accounting

Enables frame-based accounting at the queue level.

adaptation-rule

Specifies the adaptation rule for the PIR value of the subscriber aggregate rate. This rule determines which configured value is adapted to oper-agg-rate based on hardware capabilities.

Values

max, min, closest

Default

closest

size

Specifies the burst limit size.

Values

1 to 14000000, default

bytes | kilobytes

Specifies whether the value is in bytes or kilobytes.

Default

bytes

Platforms

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

Context

[Tree] (config>qos>qgrps>egr>qgrp>queue agg-shaper-weight)

[Tree] (config>qos>sap-egress>queue agg-shaper-weight)

Full Context

configure qos queue-group-templates egress queue-group queue agg-shaper-weight

configure qos sap-egress queue agg-shaper-weight

Description

This command specifies the aggregate shaper weight of the SAP-egress or queue-group queue.

The no form of this command returns the aggregate shaper weight to the default value.

Default

agg-shaper-weight 1

Parameters

weight

Specifies the aggregate shaper weight.

Values

1 to 100

Platforms

7750 SR-1, 7750 SR-s

Context

[Tree] (config>port>ethernet>egress>hs-sec-shaper aggregate)

Full Context

configure port ethernet egress hs-secondary-shaper aggregate

Description

Commands in this context configure aggregate parameters.

The no form of this command removes all of the aggregate parameter values from the configuration of this HS secondary shaper.

Platforms

7750 SR-7/12/12e

Context

[Tree] (config>service>vprn aggregate)

Full Context

configure service vprn aggregate

Description

This command creates an aggregate route. Use this command to automatically install an aggregate route in the routing table when there are one or more component routes. A component route is any route used for forwarding that is a more specific match of the aggregate.

The use of aggregate routes can reduce the number of routes that need to be advertised to neighbor routers, leading to smaller routing table sizes.

Overlapping aggregate routes may be configured; in this case a route becomes a component of only the one aggregate route with the longest prefix match. For example if one aggregate is configured as 10.0.0.0/16 and another as 10.0.0.0/24, then route 10.0.128/17 would be aggregated into 10.0.0.0/16, and route 10.0.0.128/25 would be aggregated into 10.0.0.0/24. If multiple entries are made with the same prefix and the same mask the previous entry is overwritten.

A list of up to 12 BGP communities (any mix of standard, extended, and large communities) may be associated with an aggregate route. These communities can be matched in route policies and are automatically added to BGP routes that are created from the aggregate route.

By default, aggregate routes are not installed in the forwarding table, however there are configuration options that allow an aggregate route to be installed with a black-hole next hop or with an indirect IP address as next hop.

Aggregate routes can be advertised via MP-BGP to other PEs within the network. Aggregate routes advertised using MP-BGP do not include aggregated BGP path attributes from the component routes which were used to activate the aggregate route. The aggregate route will be advertised with the minimal set of path attributes as if the aggregate was originated by the advertising routes. Export route policies should be used to control and modify the advertisement and path attributes of the aggregate routes.

The no form of this command removes the aggregate.

Default

no aggregate

Parameters

ip-prefix

The destination address of the aggregate route in dotted decimal notation.

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

the ipv6-prefix and ipv6-prefix-length apply only to the 7750 SR and 7950 XRS

the mask associated with the network address expressed as a mask length

Values: 0 to 32

summary-only

This optional parameter suppresses advertisement of more specific component routes for the aggregate.

To remove the summary-only option, enter the same aggregate command without the summary-only parameter.

as-set

This optional parameter is only applicable to BGP and creates an aggregate where the path advertised for this route will be an AS_SET consisting of all elements contained in all paths that are being summarized. Use this feature carefully as it can increase the amount of route churn due to best path changes.

aggregator as-number:ip-address

This optional parameter specifies the BGP aggregator path attribute to the aggregate route. When configuring the aggregator, a two-octet AS number used to form the aggregate route must be entered, followed by the IP address of the BGP system that created the aggregate route.

discard-component-communities

This optional keyword causes the aggregate to be advertised with only the configured BGP community set, none of the communities from the component routes activating the aggregate are included. (Component attributes are never included in aggregate routes advertised to other PE routers via MP-BGP).

black-hole

This optional parameter installs the aggregate route, when activated, in the FIB with a black-hole next-hop, where packets matching this route are discarded.

generate-icmp

This optional parameter keyword generates an ICMP.

community

This configuration option associates a BGP community with the aggregate route. The community can be matched in route policies and is automatically added to BGP routes exported from the aggregate route.

comm-id

Specifies a BGP community value, up to 72 characters.

Values

[as-num:comm-val | well-known-comm | ext-comm | large-comm]

where:

• as-num — 0 to 65535

• comm-val — 0 to 65535

• well-known-comm — null | no-export | no-export-subconfed | no-advertise | llgr-stale | no-llgr | blackhole

• ext-comm — the extended community, defined as one of the following:

  • {target | origin}:ip-address:comm-val

  • {target | origin}:asnum:ext-comm-val

  • {target | origin}:ext-asnum:comm-val

  • bandwidth:asnum:val-in-mbps

  • ext:4300:ovstate

  • ext:value1:value2

  • color:co-bits:color-value

  where:

  • target — route target

  • origin — route origin

  • ip-address — a.b.c.d

  • ext-comm-val — 0 to 4294967295

  • ext-asnum — 0 to 4294967295

  • val-in-mbps — 0 to 16777215

  • ovstate — 0, 1, or 2 (0 for valid, 1 for not found, 2 for invalid)

  • value1 — 0000 to FFFF

  • value2 — 0 to FFFFFFFFFFFF

  • co-bits — 00, 01, 10 or 11

  • color-value — 0 to 4294967295

• large-comm — asn-or-ex:val-or-ex:val-or-ex

description

Specifies a text description stored in the configuration file for a configuration context.

local-preference

Specifies a BGP local-preference value with the aggregate route. The local-preference overrides the default local preference value of a BGP route originated by exporting the aggregate route.

Values

0 to 4294967295

indirect ip-address

This configuration option specifies that the aggregate route should be installed in the FIB with a next-hop taken from the route used to forward packets to 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

The ipv6-prefix applies only to the 7750 SR and 7950 XRS.

tunnel-group-id

Specifies that the MC-IPsec state of the specific tunnel-group is added to the aggregate route.

Values

1 to 16

Platforms

All

Context

[Tree] (config>router aggregate)

Full Context

configure router aggregate

Description

This command creates an aggregate route.

Use this command to automatically install an aggregate route in the routing table when there are one or more component routes. A component route is any route used for forwarding that is a more-specific match of the aggregate.

The use of aggregate routes can reduce the number of routes that need to be advertised to neighbor routers, leading to smaller routing table sizes.

Overlapping aggregate routes may be configured; in this case a route becomes a component of only the one aggregate route with the longest prefix match. For example if one aggregate is configured as 10.0.0.0/16 and another as 10.0.0.0/24, then route 10.0.128/17 would be aggregated into 10.0.0.0/16, and route 10.0.0.128/25 would be aggregated into 10.0.0.0/24. If multiple entries are made with the same prefix and the same mask the previous entry is overwritten.

A standard 4-byte BGP community may be associated with an aggregate route in order to facilitate route policy matching.

By default aggregate routes are not installed in the forwarding table, however there are configuration options that allow an aggregate route to be installed with a black-hole next hop or with an indirect IP address as next hop.

The no form of this command removes the aggregate.

Default

no aggregate

Parameters

ip-prefix

Specifies the destination address of the aggregate route in dotted decimal notation.

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

Specifies the mask associated with the network address expressed as a mask length.

Values

0 to 32

summary-only

Suppresses advertisement of more specific component routes for the aggregate.

To remove the summary-only option, enter the same aggregate command without the summary-only parameter.

as-set

This optional parameter is only applicable to BGP and creates an aggregate where the path advertised for this route will be an AS_SET consisting of all elements contained in all paths that are being summarized. Use this feature carefully as it can increase the amount of route churn due to best path changes.

as-number:ip-address

Specifies the BGP aggregator path attribute to the aggregate route. When configuring the aggregator, a two-octet AS number used to form the aggregate route must be entered, followed by the IP address of the BGP system that created the aggregate route.

discard-component-communities

Causes the aggregate to be advertised with only the configured BGP community set, none of the communities from the component routes activating the aggregate are included.

black-hole

Installs the aggregate route, when activated, in the FIB with a black-hole next-hop, where packets matching this route are discarded.

generate-icmp

Mandatory keyword to generate an ICMP.

community

Associates a BGP community with the aggregate route. The community can be matched in route policies and is automatically added to BGP routes exported from the aggregate route.

comm-id

Specifies a BGP community value, up to 72 characters. A maximum of twelve community IDs can be specified in a single statement.

Values

[as-num:comm-val | well-known-comm | ext-comm | large-comm]

where:

• as-num — 0 to 65535

• comm-val — 0 to 65535

• well-known-comm — null | no-export | no-export-subconfed | no-advertise | llgr-stale | no-llgr | blackhole

• ext-comm — the extended community, defined as one of the following:

  • {target | origin}:ip-address:comm-val

  • {target | origin}:asnum:ext-comm-val

  • {target | origin}:ext-asnum:comm-val

  • bandwidth:asnum:val-in-mbps

  • ext:4300:ovstate

  • ext:value1:value2

  • color:co-bits:color-value

  where:

  • target — route target

  • origin — route origin

  • ip-address — a.b.c.d

  • ext-comm-val — 0 to 4294967295

  • ext-asnum — 0 to 4294967295

  • val-in-mbps — 0 to 16777215

  • ovstate — 0, 1, or 2 (0 for valid, 1 for not found, 2 for invalid)

  • value1 — 0000 to FFFF

  • value2 — 0 to FFFFFFFFFFFF

  • co-bits — 00, 01, 10 or 11

  • color-value — 0 to 4294967295

• large-comm — asn-or-ex:val-or-ex:val-or-ex

indirect ip-address

Specifies that the aggregate route should be installed in the FIB with a next-hop taken from the route used to forward packets to ip-address.

Values

The following values apply to the 7750 SR and 7950 XRS:

ipv4-prefix	a.b.c.d
ipv6-prefix	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

Values

The following values apply to the 7450 ESS:

ipv4-prefix: a.b.c.d

description

Specifies a text description stored in the configuration file for a configuration context, up to 80 characters.

local-preference

Specifies a BGP local-preference value with the aggregate route. The local-preference overrides the default local preference value of a BGP route originated by exporting the aggregate route.

Values

0 to 4294967295

policy-name

Specifies the route policy, up to 64 characters.

Platforms

All

Context

[Tree] (config>router>policy-options>policy-statement>entry>from>aggregate-contributor aggregate-contributor)

Full Context

configure router policy-options policy-statement entry from aggregate-contributor aggregate-contributor

Description

This command matches all routes (BGP and non-BGP) that contributed to an active aggregate route. If the prefix tree above a particular route includes no active aggregate routes, or the most specific active aggregate route in the prefix tree above this route has a policy that rejects the route, then it is not considered as an aggregate-contributor.

This match condition is only supported when used in a BGP export policy. If it is used in an entry of a BGP import policy, VRF export policy or VRF import policy, no routes are matched by that entry.

The no form of this command disables matching of routes (BGP and non-BGP) that contributed to an active aggregate route.

Platforms

All

Context

[Tree] (config>router>ldp aggregate-prefix-match)

Full Context

configure router ldp aggregate-prefix-match

Description

The command enables the use by LDP of the aggregate prefix match procedures.

When this option is enabled, LDP performs the following procedures for all prefixes. When an LSR receives a FEC-label binding from an LDP neighbor for a given specific FEC1 element, it will install the binding in the LDP FIB if:

• It is able to perform a successful longest IP match of the FEC prefix with an entry in the routing table, and

• The advertising LDP neighbor is the next-hop to reach the FEC prefix.

When such a FEC-label binding has been installed in the LDP FIB, then LDP programs an NHLFE entry in the egress data path to forward packets to FEC1. It also advertises a new FEC-label binding for FEC1 to all its LDP neighbors.

When a new prefix appears in the routing table, LDP inspects the LDP FIB to determine if this prefix is a better match (a more specific match) for any of the installed FEC elements. For any FEC for which this is true, LDP may have to update the NHLFE entry for this FEC.

When a prefix is removed from the routing table, LDP inspects the LDP FIB for all FEC elements which matched this prefix to determine if another match exists in the routing table. If so, it updates the NHLFE entry accordingly. If not, it sends a label withdraw message to its LDP neighbors to remove the binding.

When the next hop for a routing prefix changes, LDP updates the LDP FIB entry for the FEC elements which matched this prefix. It also updates the NHLFE entry for these FEC elements accordingly.

The no form of this command disables the use by LDP of the aggregate prefix procedures and deletes the configuration. LDP resumes performing exact prefix match for FEC elements.

Default

no aggregate-prefix-match

Platforms

All

Context

[Tree] (config>subscr-mgmt>sla-prof aggregate-qos-stats)

Full Context

configure subscriber-mgmt sla-profile aggregate-qos-stats

Description

Commands in this context configure how aggregate QoS statistics are calculated for the SLA profile.

Platforms

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

Context

[Tree] (config>test-oam>link-meas>template aggregate-sample-window)

Full Context

configure test-oam link-measurement measurement-template aggregate-sample-window

Description

Commands in this context configure the aggregate sample window parameters to be used when the measurement template is assigned to an IP interface. The aggregate sample window is the collection of sample windows.

Platforms

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

Context

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

Full Context

configure qos fp-resource-policy aggregate-shapers

Description

This command enters the aggregate-shapers context.

Platforms

7750 SR-1, 7750 SR-s

Context

[Tree] (config>app-assure>group>statistics>aa-sub aggregate-stats)

Full Context

configure application-assurance group statistics aa-sub aggregate-stats

Description

This command configures aa-sub accounting statistics for export of aggregate statistics of a given subscriber.

Default

aggregate-stats no-export

Parameters

export-method

Specifies the method of statistics export to be used.

Values

accounting-policy (this is the only option for sub-aggregate statistics, and it is only supported in residential and VPN sub-scale modes).

no-export

Disables the export.

Platforms

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

Context

[Tree] (config>service>vprn>bgp>group>neighbor>link-bandwidth aggregate-used-paths)

[Tree] (config>service>vprn>bgp>group>link-bandwidth aggregate-used-paths)

Full Context

configure service vprn bgp group neighbor link-bandwidth aggregate-used-paths

configure service vprn bgp group link-bandwidth aggregate-used-paths

Description

This command configures BGP to aggregate the bandwidth values from the link-bandwidth extended communities of the used multipaths towards an IP prefix when it is re-advertising a route with next-hop-self towards peers within the scope of the command, as long as the route belongs to one of the listed address families.

Aggregation is not supported unless all of the used multipaths (up to the configured ECMP limit) correspond to received BGP routes with a link-bandwidth extended community. If add-path is also enabled toward the peer, then all of the add-paths advertised to the peer encode the aggregated bandwidth in a link-bandwidth extended community.

Up to three families may be configured.

The no form of this command disables aggregation in a next-hop-self scenario and the link-bandwidth extended community in the advertised route is a copy of the link-bandwidth extended community in the received route (which may have been added by import policy or by the effect of the add-to-received-ebgp command).

Default

no aggregate-used-paths

Parameters

family

Specifies the address families for which receiving the link-bandwidth extended community from EBGP peers should be supported.

Values

ipv4 — Adds a link-bandwidth extended community to unlabeled unicast IPv4 routes.

label-ipv4 — Adds a link-bandwidth extended community to labeled-unicast IPv4 routes.

ipv6 — Adds a link-bandwidth extended community to unlabeled unicast IPv6 routes.

Platforms

All

Context

[Tree] (config>router>bgp>group>neighbor>link-bandwidth aggregate-used-paths)

[Tree] (config>router>bgp>group>link-bandwidth aggregate-used-paths)

Full Context

configure router bgp group neighbor link-bandwidth aggregate-used-paths

configure router bgp group link-bandwidth aggregate-used-paths

Description

This command configures BGP to aggregate the bandwidth values from the link-bandwidth extended communities of the used multipaths towards an IP prefix when it is re-advertising a route with next-hop-self towards peers within the scope of the command, as long as the route belongs to one of the listed address families.

Aggregation is not supported unless all of the used multipaths (up to the configured ECMP limit) correspond to received BGP routes with a link-bandwidth extended community. If add-path is also enabled toward the peer, then all of the add-paths advertised to the peer encode the aggregated bandwidth in a link-bandwidth extended community.

Up to six families may be configured.

The no form of this command disables aggregation in a next-hop-self scenario and the link-bandwidth extended community in the advertised route is a copy of the link-bandwidth extended community in the received route (which may have been added by import policy or by the effect of the add-to-received-ebgp command).

Default

no aggregate-used-paths

Parameters

family

Specifies the address families for which receiving the link-bandwidth extended community from EBGP peers should be supported.

Values

ipv4 — Adds a link-bandwidth extended community to unlabeled unicast IPv4 routes.

label-ipv4 — Adds a link-bandwidth extended community to labeled-unicast IPv4 routes.

vpn-ipv4 — Adds a link-bandwidth extended community to IPv4 VPN (SAFI 128) routes.

ipv6 — Adds a link-bandwidth extended community to unlabeled unicast IPv6 routes.

label-ipv6 — Adds a link-bandwidth extended community to labeled-unicast IPv6 routes.

vpn-ipv6 — Adds a link-bandwidth extended community to IPv6 VPN (SAFI 128) routes.

Platforms

All

Context

[Tree] (config>cflowd>collector aggregation)

Full Context

configure cflowd collector aggregation

Description

This command configures the type of aggregation scheme to be exported.

Specifies the type of data to be aggregated and to the collector.

To configure aggregation, you must decide which type of aggregation scheme to configure: autonomous system, destination prefix, protocol port, raw, source destination, or source prefix.

This can only be configured if the collector version is configured as V8.

The no form of this command removes all aggregation types from the collector configuration.

Default

no aggregation

Platforms

All

Context

[Tree] (config>subscr-mgmt>bgp-prng-plcy aggregator-id-zero)

Full Context

configure subscriber-mgmt bgp-peering-policy aggregator-id-zero

Description

This command is used to set the router ID in the BGP aggregator path attribute to zero when BGP aggregates routes. This prevents different routers within an AS from creating aggregate routes that contain different AS paths.

When BGP is aggregating routes, it adds the aggregator path attribute to the BGP update messages. By default, BGP adds the AS number and router ID to the aggregator path attribute.

When this command is enabled, BGP adds the router ID to the aggregator path attribute. The no form of this command used at the global level reverts to default where BGP adds the AS number and router ID to the aggregator path attribute.

Platforms

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

Context

[Tree] (config>service>vprn>bgp>group aggregator-id-zero)

[Tree] (config>service>vprn>bgp>group>neighbor aggregator-id-zero)

[Tree] (config>service>vprn>bgp aggregator-id-zero)

Full Context

configure service vprn bgp group aggregator-id-zero

configure service vprn bgp group neighbor aggregator-id-zero

configure service vprn bgp aggregator-id-zero

Description

This command is used to set the router ID in the BGP aggregator path attribute to zero when BGP aggregates routes. This prevents different routers within an AS from creating aggregate routes that contain different AS paths.

When BGP is aggregating routes, it adds the aggregator path attribute to the BGP update messages. By default, BGP adds the AS number and router ID to the aggregator path attribute.

When this command is enabled, BGP adds the router ID to the aggregator path attribute. This command is used at the group level to revert to the value defined under the global level, while this command is used at the neighbor level to revert to the value defined under the group level.

The no form of this command used at the global level reverts to default where BGP adds the AS number and router ID to the aggregator path attribute.

The no form of this command used at the group level reverts to the value defined at the group level.

The no form of this command used at the neighbor level reverts to the value defined at the group level.

Default

no aggregator-id-zero — BGP adds the AS number and router ID to the aggregator path attribute.

Platforms

All

Context

[Tree] (config>router>bgp>group aggregator-id-zero)

[Tree] (config>router>bgp>group>neighbor aggregator-id-zero)

[Tree] (config>router>bgp aggregator-id-zero)

Full Context

configure router bgp group aggregator-id-zero

configure router bgp group neighbor aggregator-id-zero

configure router bgp aggregator-id-zero

Description

This command sets the router ID in the BGP aggregator path attribute to zero when BGP aggregates routes. This prevents different routers within an AS from creating aggregate routes for the same prefix with different path attributes.

When BGP is aggregating routes, it adds the aggregator path attribute to the BGP update messages. By default, BGP adds the AS number and router ID to the aggregator path attribute.

When this command is enabled, BGP adds the router ID to the aggregator path attribute. This command is used at the group level to revert to the value defined under the global level, while this command is used at the neighbor level to revert to the value defined under the group level.

The no form of this command used at the global level reverts to default where BGP adds the AS number and router ID to the aggregator path attribute.

The no form of this command used at the group level reverts to the value defined at the global level.

The no form of this command used at the neighbor level reverts to the value defined at the group level.

Default

no aggregator-id-zero

Platforms

All

Context

[Tree] (config>service>cpipe>spoke-sdp>pw-path-id agi)

[Tree] (config>service>epipe>spoke-sdp>pw-path-id agi)

[Tree] (config>service>vpls>spoke-sdp>pw-path-id agi)

Full Context

configure service cpipe spoke-sdp pw-path-id agi

configure service epipe spoke-sdp pw-path-id agi

configure service vpls spoke-sdp pw-path-id agi

Description

This command configures the attachment group identifier for an MPLS-TP PW.

Parameters

agi

Specifies the attachment group identifier.

Values

0 to 4294967295

Platforms

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

Context

[Tree] (config>service>ies>red-if>spoke-sdp>pw-path-id agi)

[Tree] (config>service>ies>if>spoke-sdp>pw-path-id agi)

Full Context

configure service ies redundant-interface spoke-sdp pw-path-id agi

configure service ies interface spoke-sdp pw-path-id agi

Description

This command configures the attachment group identifier for an MPLS-TP PW.

Parameters

agi

Specifies the attachment group identifier.

Values

0 to 4294967295

Platforms

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

• configure service ies redundant-interface spoke-sdp pw-path-id agi

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

• configure service ies interface spoke-sdp pw-path-id agi

Context

[Tree] (config>service>vprn>if>spoke-sdp>pw-path-id agi)

[Tree] (config>service>vprn>red-if>spoke-sdp>pw-path-id agi)

Full Context

configure service vprn interface spoke-sdp pw-path-id agi

configure service vprn redundant-interface spoke-sdp pw-path-id agi

Description

This command configures the attachment group identifier for an MPLS-TP PW.

Parameters

attachment-group-identifier

Specifies the attachment group identifier.

Values

0 to 4294967295

Platforms

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

• configure service vprn interface spoke-sdp pw-path-id agi

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

• configure service vprn redundant-interface spoke-sdp pw-path-id agi

Context

[Tree] (config>mirror>mirror-dest>spoke-sdp>pw-path-id agi)

[Tree] (config>mirror>mirror-dest>remote-src>spoke-sdp>pw-path-id agi)

Full Context

configure mirror mirror-dest spoke-sdp pw-path-id agi

configure mirror mirror-dest remote-source spoke-sdp pw-path-id agi

Description

This command configures the attachment group identifier for an MPLS-TP PW.

Parameters

route-identifier

Specifies the attachment group identifier.

Values

0 to 4294967295

Platforms

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

Context

[Tree] (config>system>security>password aging)

Full Context

configure system security password aging

Description

This command configures the number of days a user password is valid before the user must change their password. This parameter can be used to force the user to change the password at the configured interval. Note the aging starts after the last password configuration or update. This timer is persistence (per user) over a node reboot or activity switch between CPMs. When the user changes the password, the timer is reset to the maximum age. When the password for a user ages out, the user is prompted at login to change the password. Console/SSH/Telnet supports password change prompt.

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

Parameters

days

Specifies the maximum number of days the password is valid.

Values

1 to 500

Note:

This command applies to local users.

Platforms

All

Context

[Tree] (config>filter>ipv6-filter>entry>match ah-ext-hdr)

Full Context

configure filter ipv6-filter entry match ah-ext-hdr

Description

This command enables match on existence of AH Extension Header in the IPv6 filter policy.

The no form of this command ignores AH Extension Header presence/absence in a packet when evaluating match criteria of a given filter policy entry.

Default

no ah-ext-hdr

Parameters

true

Matches a packet with an AH Extension Header.

false

Matches a packet without an AH Extension Header.

Platforms

All

Context

[Tree] (config>router>bgp>group aigp)

[Tree] (config>router>bgp>group>neighbor aigp)

Full Context

configure router bgp group aigp

configure router bgp group neighbor aigp

Description

This command enables or disables Accumulated IGP (AIGP) path attribute support with one or more BGP peers. BGP path selection among routes with an associated AIGP metric is based on the end-to-end IGP metrics of the different BGP paths, even when these BGP paths span more than one AS and IGP instance.

The effect of disabling AIGP (using the no form of this command or implicit) is to remove the AIGP attribute from advertised routes, if present, and to ignore the AIGP attribute in received routes.

Default

no aigp

Platforms

All

Context

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

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

Full Context

configure router policy-options policy-statement default-action aigp-metric

configure router policy-options policy-statement entry action aigp-metric

Description

This command assigns a BGP AIGP metric to routes matching the entry. The effect of this command on a route matched and accepted by a route policy entry depends on how the policy is applied (BGP import policy vs. BGP export policy), the type of route and the specific form of this command.

In a BGP import policy this command is used to:

• Associate an AIGP metric with an IBGP route received with an empty AS path and no AIGP attribute.

• Associate an AIGP metric with an EBGP route received without an AIGP attribute that has an AS path containing only AS numbers belonging to the local AIGP administrative domain.

• Modify the received AIGP metric value prior to BGP path selection.

In a BGP export policy this command is used to:

• Add the AIGP attribute and set the AIGP metric value in a BGP route originated by exporting a direct, static or IGP route from the routing table.

• Remove the AIGP attribute from a route advertisement to a particular peer.

• Modify the AIGP metric value in a route advertisement to a particular peer.

Default

no aigp-metric

Parameters

metric

Administratively defined metric.

Values

0 to 4294967295

Default

name — The AIGP metric parameter variable name. Allowed values are any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, ?, space), the entire string must be enclosed within double quotes. Policy parameters must start and end with at-signs (@); for example, "@variable@”.

add

Adds the AIGP attribute.

igp

Sets the AIGP metric to the IGP metric.

Platforms

All

Context

[Tree] (config>port>ethernet>eth-cfm>mep ais-enable)

[Tree] (config>lag>eth-cfm>mep ais-enable)

Full Context

configure port ethernet eth-cfm mep ais-enable

configure lag eth-cfm mep ais-enable

Description

This command enables the reception of AIS messages.

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

Platforms

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

Context

[Tree] (config>service>epipe>sap>eth-cfm ais-enable)

[Tree] (config>service>epipe>spoke-sdp>eth-cfm>mep ais-enable)

[Tree] (config>service>epipe>sap>eth-cfm>mep ais-enable)

Full Context

configure service epipe sap eth-cfm ais-enable

configure service epipe spoke-sdp eth-cfm mep ais-enable

configure service epipe sap eth-cfm mep ais-enable

Description

This command enables the generation and the reception of AIS messages.

Platforms

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

Context

[Tree] (config>service>vpls>spoke-sdp>eth-cfm>mep ais-enable)

[Tree] (config>service>vpls>sap>eth-cfm>mep ais-enable)

[Tree] (config>service>vpls>mesh-sdp>eth-cfm>mep ais-enable)

Full Context

configure service vpls spoke-sdp eth-cfm mep ais-enable

configure service vpls sap eth-cfm mep ais-enable

configure service vpls mesh-sdp eth-cfm mep ais-enable

Description

This command enables the generation and the reception of AIS messages.

Platforms

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

Context

[Tree] (config>service>ies>if>spoke-sdp>eth-cfm ais-enable)

Full Context

configure service ies interface spoke-sdp eth-cfm ais-enable

Description

This command configures the reception of Alarm Indication Signal (AIS) message.

Platforms

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

Context

[Tree] (cfg>svc>vprn>if>sap>eth-cfm>mep ais-enable)

[Tree] (config>service>vprn>if>spoke-sdp>eth-cfm ais-enable)

[Tree] (config>service>vprn>sub-if>grp-if>sap>eth-cfm ais-enable)

Full Context

configure service vprn interface sap eth-cfm mep ais-enable

configure service vprn interface spoke-sdp eth-cfm ais-enable

configure service vprn subscriber-interface group-interface sap eth-cfm ais-enable

Description

This command configures the reception of Alarm Indication Signal (AIS) message.

Platforms

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

• configure service vprn interface sap eth-cfm mep ais-enable
• configure service vprn interface spoke-sdp eth-cfm ais-enable

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

• configure service vprn subscriber-interface group-interface sap eth-cfm ais-enable

Context

[Tree] (config>router>mpls>if>mpls-tp-mep ais-enable)

Full Context

configure router mpls interface mpls-tp-mep ais-enable

Description

This command enables MPLS-TP AIS insertion for the forward and reverse directions of all MPLS-TP transit paths using the MPLS interface. This causes the generation of AIS packets in the forward or reverse directions of a path if a fault is detected on the applicable underlying interface for the ingress of the path direction.

The no form of this command disables AIS insertion.

Default

no ais-enable

Platforms

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

Context

[Tree] (config>system>thresholds>rmon alarm)

Full Context

configure system thresholds rmon alarm

Description

The alarm command configures an entry in the RMON-MIB alarmTable. The alarm command controls the monitoring and triggering of threshold crossing events. In order for notification or logging of a threshold crossing event to occur there must be at least one associated rmon>event configured.

The agent periodically takes statistical sample values from the MIB variable specified for monitoring and compares them to thresholds that have been configured with the alarm command. The alarm command configures the MIB variable to be monitored, the polling period (interval), sampling type (absolute or delta value), and rising and falling threshold parameters. If a sample has crossed a threshold value, the associated event is generated.

Use the no form of this command to remove an rmon-alarm-id from the configuration.

Parameters

rmon-alarm-id

Specifies a numerical identifier for the alarm being configured. The number of alarms that can be created is limited to 1200. Alarm ID values above 65400 are used for dynamic system threshold commands and should be avoided.

Values

1 to 65535

oid-string

Specifies the SNMP object identifier of the particular variable to be sampled. Only SNMP variables that resolve to an ASN.1 primitive type of integer (integer, Integer32, Counter32, Counter64, Gauge, or TimeTicks) may be sampled. The oid-string, up to 255 characters, may be expressed using either the dotted string notation or as object name plus dotted instance identifier. For example, "1.3.6.1.2.1.2.2.1.10.184582144" or "ifInOctets.184582144".

seconds

Specifies the polling period over which the data is sampled and compared with the rising and falling thresholds. When setting this interval value, care should be taken in the case of ’delta’ type sampling - the interval should be set short enough that the sampled variable is very unlikely to increase or decrease by more than 2147483647 - 1 during a single sampling interval. Care should also be taken not to set the interval value too low to avoid creating unnecessary processing overhead.

Values

1 to 2147483647

sample-type

Specifies the method of sampling the selected variable and calculating the value to be compared against the thresholds.

Values

absolute — Specifies that the value of the selected variable will be compared directly with the thresholds at the end of the sampling interval.

delta — Specifies that the value of the selected variable at the last sample will be subtracted from the current value, and the difference compared with the thresholds.

Default

absolute

alarm-type

Specifies the alarm that may be sent when this alarm is first created.

If the first sample is greater than or equal to the rising threshold value and startup-alarm is equal to rising or either, then a single rising threshold crossing event is generated.

If the first sample is less than or equal to the falling threshold value and startup-alarm is equal to falling or either, a single falling threshold crossing event is generated.

Values

rising, falling, either

Default

either

rising-event rmon-event-id

Specifies the identifier of the rmon>event that specifies the action to be taken when a rising threshold crossing event occurs.

If there is no corresponding event configured for the specified rmon-event-id, then no association exists and no action is taken.

If the rising-event rmon-event-id has a value of zero (0), no associated event exists.

If a rising-event rmon-event-id is configured, the CLI requires a rising-threshold to also be configured.

Values

0 to 65535

Default

0

rising-threshold threshold

Specifies a threshold for the sampled statistic. When the current sampled value is greater than or equal to this threshold, and the value at the last sampling interval was less than this threshold, a single threshold crossing event will be generated. A single threshold crossing event will also be generated if the first sample taken is greater than or equal to this threshold and the associated startup-alarm is equal to rising or either.

After a rising threshold crossing event is generated, another such event will not be generated until the sampled value falls below this threshold and reaches less than or equal the falling-threshold value.

Values

-2147483648 to 2147483647

Default

0

falling-event rmon-event-id

Specifies the identifier of the rmon>event that specifies the action to be taken when a falling threshold crossing event occurs. If there is no corresponding event configured for the specified rmon-event-id, then no association exists and no action is taken. If the falling-event has a value of zero (0), no associated event exists.

If a falling-event is configured, the CLI requires a falling-threshold to also be configured.

Values

0 to 65535

Default

0

falling-threshold threshold

Specifies a threshold for the sampled statistic. When the current sampled value is less than or equal to this threshold, and the value at the last sampling interval was greater than this threshold, a single threshold crossing event will be generated. A single threshold crossing event will also be generated if the first sample taken is less than or equal to this threshold and the associated startup-alarm is equal to falling or either.

After a falling threshold crossing event is generated, another such event will not be generated until the sampled value rises above this threshold and reaches greater than or equal the rising-threshold value.

Values

-2147483648 to 2147483647

Default

0

owner-string

Specifies the owner string; the owner identifies the creator of this alarm. It defaults to "TiMOS CLI". This parameter is defined primarily to allow entries that have been created in the RMON-MIB alarmTable by remote SNMP managers to be saved and reloaded in a CLI configuration file. The owner will not normally be configured by CLI users and can be a maximum of 80 characters long.

Default

TiMOS CLI

Configuration example

alarm 3 variable-oid ifInOctets.184582144 interval 20 sample-type delta 
start-alarm either rising-event 5 rising-threshold 10000 falling-event 5 
falling-threshold 9000 owner "TiMOS CLI"

Platforms

All

Context

[Tree] (config>sys>security>cpu-protection>policy alarm)

Full Context

configure system security cpu-protection policy alarm

Description

This command enables the generation of an event when a rate is exceed. The event includes information about the offending source. Only one event is generated per monitor period.

The no form of this command disables the notifications.

Default

no alarm

Platforms

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

Context

[Tree] (config>system alarm-contact-in-power)

Full Context

configure system alarm-contact-in-power

Description

This command allows the user to enable a supply of +24V output power on the +24VDC pin of the Alarm Interface Port of the CPM. When enabled, the power supplied through the +24VDC output pin can be used as a source voltage for the alarm contact input pins. The +24VDC output can be used to supply power for monitoring external sensor devices such as cabinet door sensors instead of using an external power source. If users want to use a separate external power source, they should disable the supply of power to the +24VDC output pin by using this CLI command.

Default

alarm-contact-in-power off

Parameters

on

Specifies to turn on power to the +24VDC output pin of the Alarm Interface Port of the CPM.

off

Specifies to turn off power to the +24VDC output pin of the Alarm Interface Port of the CPM.

Platforms

7750 SR-a

Context

[Tree] (config>system alarm-contact-input)

Full Context

configure system alarm-contact-input

Description

Commands in this context configure the alarm contact input pin parameters for the specified input pin.

Parameters

input-pin-number

Specifies the alarm contact input pin.

Values

1 to 4

Platforms

7750 SR-a

Context

[Tree] (config>lag>eth-cfm>mep alarm-notification)

[Tree] (config>eth-tunnel>path>eth-cfm>mep alarm-notification)

Full Context

configure lag eth-cfm mep alarm-notification

configure eth-tunnel path eth-cfm mep alarm-notification

Description

This command configures the MEP alarm notification parameter.

Platforms

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

Context

[Tree] (config>service>ies>sub-if>grp-if>sap>eth-cfm>mep alarm-notification)

[Tree] (config>service>epipe>sap>eth-cfm>mep alarm-notification)

[Tree] (config>service>vpls>sap>eth-cfm>mep alarm-notification)

[Tree] (config>service>epipe>spoke-sdp>eth-cfm>mep alarm-notification)

[Tree] (config>router>if>eth-cfm>mep alarm-notification)

[Tree] (config>service>ies>if>spoke-sdp>eth-cfm>mep alarm-notification)

[Tree] (config>service>vpls>spoke-sdp>eth-cfm>mep alarm-notification)

[Tree] (config>service>ies>if>sap>eth-cfm>mep alarm-notification)

[Tree] (config>service>vprn>if>sap>eth-cfm>mep alarm-notification)

[Tree] (config>service>vpls>mesh-sdp>eth-cfm>mep alarm-notification)

[Tree] (config>service>vpls>eth-cfm>mep alarm-notification)

[Tree] (config>service>vprn>sub-if>grp-if>sap>eth-cfm>mep alarm-notification)

[Tree] (config>service>ipipe>sap>eth-cfm>mep alarm-notification)

[Tree] (config>service>vprn>if>spoke-sdp>eth-cfm>mep alarm-notification)

[Tree] (config>port>ethernet>eth-cfm>mep alarm-notification)

Full Context

configure service ies subscriber-interface group-interface sap eth-cfm mep alarm-notification

configure service epipe sap eth-cfm mep alarm-notification

configure service vpls sap eth-cfm mep alarm-notification

configure service epipe spoke-sdp eth-cfm mep alarm-notification

configure router interface eth-cfm mep alarm-notification

configure service ies interface spoke-sdp eth-cfm mep alarm-notification

configure service vpls spoke-sdp eth-cfm mep alarm-notification

configure service ies interface sap eth-cfm mep alarm-notification

configure service vprn interface sap eth-cfm mep alarm-notification

configure service vpls mesh-sdp eth-cfm mep alarm-notification

configure service vpls eth-cfm mep alarm-notification

configure service vprn subscriber-interface group-interface sap eth-cfm mep alarm-notification

configure service ipipe sap eth-cfm mep alarm-notification

configure service vprn interface spoke-sdp eth-cfm mep alarm-notification

configure port ethernet eth-cfm mep alarm-notification

Description

Commands in this context configure the Fault Notification Generation time values for raising the alarm and resetting the CCM defect alarm. These timers are used for network management processes and are not tied into delaying the notification to the fault management system on the network element. These timers do not affect fault propagation mechanisms.

Platforms

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

• configure service vprn subscriber-interface group-interface sap eth-cfm mep alarm-notification
• configure service ies subscriber-interface group-interface sap eth-cfm mep alarm-notification

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

• configure service vpls sap eth-cfm mep alarm-notification
• configure port ethernet eth-cfm mep alarm-notification
• configure service ies interface sap eth-cfm mep alarm-notification
• configure service ipipe sap eth-cfm mep alarm-notification
• configure service vprn interface sap eth-cfm mep alarm-notification
• configure service vpls spoke-sdp eth-cfm mep alarm-notification
• configure service ies interface spoke-sdp eth-cfm mep alarm-notification
• configure service vprn interface spoke-sdp eth-cfm mep alarm-notification
• configure service epipe spoke-sdp eth-cfm mep alarm-notification
• configure router interface eth-cfm mep alarm-notification
• configure service epipe sap eth-cfm mep alarm-notification
• configure service vpls eth-cfm mep alarm-notification
• configure service vpls mesh-sdp eth-cfm mep alarm-notification

Context

[Tree] (config>eth-ring>path>eth-cfm>mep alarm-notification)

Full Context

configure eth-ring path eth-cfm mep alarm-notification

Description

Commands in this context configure the MEP alarm notification parameters.

Platforms

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

Context

[Tree] (config>port>network>egress>pool>monitor-depth alarm-thresholds)

[Tree] (config>port>access>egress>pool>monitor-depth alarm-thresholds)

[Tree] (config>card>fp>ingress>network>pool>monitor-depth alarm-thresholds)

[Tree] (config>port>access>ingress>pool>monitor-depth alarm-thresholds)

Full Context

configure port network egress pool monitor-pool-depth alarm-thresholds

configure port access egress pool monitor-pool-depth alarm-thresholds

configure card fp ingress network pool monitor-pool-depth alarm-thresholds

configure port access ingress pool monitor-pool-depth alarm-thresholds

Description

Commands in this context configure the alarm thresholds for pool usage.

The no form of this command removes the configured alarm thresholds.

Default

no alarm-thresholds

Platforms

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

Context

[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>video>analyzer alarms)

[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>channel>source-override>video>analyzer alarms)

[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>channel>video>analyzer alarms)

Full Context

configure mcast-management multicast-info-policy bundle video analyzer alarms

configure mcast-management multicast-info-policy bundle channel source-override video analyzer alarms

configure mcast-management multicast-info-policy bundle channel video analyzer alarms

Description

Commands in this context configure alarms for the analyzer (VQM).

Platforms

7450 ESS, 7750 SR, 7750 SR-s

Context

[Tree] (config>li>x-interfaces>x3 alarms)

Full Context

configure li x-interfaces x3 alarms

Description

This command enables the configuration of X3 alarms.

Platforms

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

Context

[Tree] (config>system alarms)

Full Context

configure system alarms

Description

Commands in this context configure facility alarm parameters. Alarm support is intended to cover a focused subset of router states that are likely to indicate service impacts (or imminent service impacts) related to the overall state of hardware assemblies (cards, fans, links, and so on).

Platforms

All

Context

[Tree] (config>subscr-mgmt>acct-plcy>include-radius-attribute alc-acct-triggered-reason)

Full Context

configure subscriber-mgmt radius-accounting-policy include-radius-attribute alc-acct-triggered-reason

Description

This command includes the alc-acct-triggered-reason attribute.

Platforms

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

Context

[Tree] (config>subscr-mgmt>acct-plcy>include-radius-attribute alc-error-code)

Full Context

configure subscriber-mgmt radius-accounting-policy include-radius-attribute alc-error-code

Description

This command enables RADIUS accounting messages to include an error number and error code when the subscriber host session terminates. To obtain a complete list of error numbers and their corresponding codes, use the tools>dump>aaa>radius-acct-terminate-cause command.

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

Context

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

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

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

Full Context

configure service nat up-nat-policy alg

configure service nat firewall-policy alg

configure service nat nat-policy alg

Description

Commands in this context configure application layer gateway (ALG) parameters of this policy.

Platforms

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

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

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

• configure service nat firewall-policy alg

Context

[Tree] (conf>router>segment-routing>srv6>micro-segment-locator algorithm)

[Tree] (config>router>segment-routing>srv6>locator algorithm)

Full Context

configure router segment-routing segment-routing-v6 micro-segment-locator algorithm

configure router segment-routing segment-routing-v6 locator algorithm

Description

This command configures an IGP flexible algorithm identifier for an SRv6 or micro-segment locator.

A locator can only be part of a single algorithm but it can be used in multiple IGP instances.

The no form of this command returns the locator to the base IGP algorithm 0.

Default

no algorithm

Parameters

flex-algo-id

Specifies the flexible algorithm ID.

Values

128 to 255

Platforms

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

Context

[Tree] (environment alias)

Full Context

environment alias

Description

This command enables the substitution of a command line (or part of a command line) by an alias. Use this command to create alternative or easier to remember or understand names for an entity or command string. If the string contains special characters (#, ?, space), the entire string must be enclosed within double quotes. The special characters forward slash (/) and backslash (\) cannot be used as the first character inside an alias string. An alias can contain a double quote character by preceding the quote with a backslash (\) character (for example, alias my-alias "| match \"string\""). Only a single command can be present in the command string (the command can be long with many parameters but there is no support for aliases that include multiple CLI commands or lines). This command can be entered in any context but must be created in the root environment context.

For example, to create an alias named soi to display OSPF interfaces, enter the following command:

alias soi "show router ospf interface”

Complex aliases can be created to have shortcuts for customized show routine output.

environment alias my-summary "| match expression \"----|Description|Interface|Admin State|Oper State|Transceiver Type|Optical Compliance|Link Length\" | match invert-match expression \"Ethernet Interface|OTU Interface\" | match invert-match expression \"----\" post-lines 1"

and then used like this:

show port detail my-summary

Parameters

alias-name

Specifies the alias name, up to 80 characters. Do not use a valid command string for the name of the alias. If the alias specified is an actual command, this causes the command to be replaced by the alias.

alias-command-name

Specifies the command name to be associated, up to 320 characters.

Platforms

All

Context

[Tree] (config>log>acct-policy align)

Full Context

configure log accounting-policy align

Description

This command enables alignment of statistics collection to the nearest interval within an hour. Enabling the alignment allows statistics collection into an accounting file that is being synchronized across multiple network nodes in the network.

The no form of this command disables alignment of statistics collection.

Default

no align

Platforms

All

Context

[Tree] (debug>service>id>pim-snooping all)

Full Context

debug service id pim-snooping all

Description

This command enables or disables debugging for all the PIM modules.

Parameters

grp-ip-address

Debugs information associated with all PIM modules

Values

multicast group address (IPv4 or IPv6)

ip-address

Debugs information associated with all PIM modules

Values

IPv4 or IPv6 address

detail

Debugs detailed information on all PIM modules

Platforms

All

Context

[Tree] (debug>router>rsvp>event all)

[Tree] (debug>router>mpls>event all)

Full Context

debug router rsvp event all

debug router mpls event all

Description

This command debugs all events.

The no form of the command disables the debugging.

Parameters

detail

Displays detailed information about all events.

Platforms

All

Context

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

Full Context

debug router rsvp packet all

Description

This command debugs all packets.

The no form of the command disables the debugging.

Parameters

detail

Displays detailed information about all RSVP packets.

Platforms

All

Context

[Tree] (debug>router>pim all)

Full Context

debug router pim all

Description

This command enables debugging for all the PIM modules.

The no form of this command disables debugging PIM modules.

Parameters

grp-ip-address

Debugs information associated with all PIM modules.

Values

IPv4 or IPv6 address

ip-address

Debugs information associated with all PIM modules.

Values

IPv4 or IPv6 address

detail

Debugs detailed information on all PIM modules.

Platforms

All

Context

[Tree] (debug>router>rpki-session>packet all)

Full Context

debug router rpki-session packet all

Description

This command enables debugging for all RPKI packets.

The no form of this command disables debugging for all RPKI packets.

Platforms

All

Context

[Tree] (config>log>acct-policy>cr>aa>aa-to-sub-cntr all)

[Tree] (config>log>acct-policy>cr>aa>aa-sub-attr all)

[Tree] (config>log>acct-policy>cr>aa>aa-sub-cntr all)

[Tree] (config>log>acct-policy>cr>aa>aa-from-sub-cntr all)

Full Context

configure log accounting-policy custom-record aa-specific to-aa-sub-counters all

configure log accounting-policy custom-record aa-specific aa-sub-attributes all

configure log accounting-policy custom-record aa-specific aa-sub-counters all

configure log accounting-policy custom-record aa-specific from-aa-sub-counters all

Description

This command includes all counters and only applies to the 7750 SR.

Platforms

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

Context

[Tree] (debug>router>pcep>pcc>conn all)

[Tree] (debug>router>pcep>pcc all)

Full Context

debug router pcep pcc connection all

debug router pcep pcc all

Description

This command enables debugging for all PCEP PCC or connection events.

The no form of this command disables debugging.

Parameters

detail

Keyword used to specify detailed information about all events.

Platforms

All