i Commands

i-counters

i-counters

Syntax

i-counters [all]

no i-counters

Context

[Tree] (config>subscr-mgmt>acct-plcy>cr>ref-queue i-counters)

[Tree] (config>subscr-mgmt>acct-plcy>cr>queue i-counters)

Full Context

configure subscriber-mgmt radius-accounting-policy custom-record ref-queue i-counters

configure subscriber-mgmt radius-accounting-policy custom-record queue i-counters

Description

This command configures ingress counter parameters for this custom record.

The no form of this command reverts to the default.

Parameters

all

Includes all counters.

Platforms

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

i-counters

Syntax

i-counters [all]

no i-counters

Context

[Tree] (config>log>acct-policy>cr>policer i-counters)

[Tree] (config>log>acct-policy>cr>ref-policer i-counters)

[Tree] (config>log>acct-policy>cr>queue i-counters)

[Tree] (config>log>acct-policy>cr>ref-queue i-counters)

Full Context

configure log accounting-policy custom-record policer i-counters

configure log accounting-policy custom-record ref-policer i-counters

configure log accounting-policy custom-record queue i-counters

configure log accounting-policy custom-record ref-queue i-counters

Description

This command configures ingress counter parameters for this custom record.

The no form of this command reverts all ingress counters to their default value.

Default

i-counters

Parameters

all

Specifies that all ingress counters should be included.

Platforms

All

i-sid

i-sid

Syntax

i-sid i-sid

no i-sid

Context

[Tree] (config>test-oam>build-packet>header>pbb i-sid)

[Tree] (debug>oam>build-packet>packet>field-override>header>pbb i-sid)

Full Context

configure test-oam build-packet header pbb i-sid

debug oam build-packet packet field-override header pbb i-sid

Description

This command defines the iSID value to be used in the test PBB header.

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

Default

i-sid 0

Parameters

i-sid

Specifies the iSID value to be used in the test PBB header.

Values

0 to 16777215

Platforms

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

ia-na

ia-na

Syntax

ia-na

Context

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

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

Full Context

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

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

Description

This command configures the IA-NA for the DHCPv6 client.

Platforms

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

ibgp-multipath

ibgp-multipath

Syntax

[no] ibgp-multipath

Context

[Tree] (config>service>vprn>bgp ibgp-multipath)

Full Context

configure service vprn bgp ibgp-multipath

Description

This command defines the type of IBGP multipath to use when adding BGP routes to the route table if the route resolving the BGP nexthop offers multiple next-hops.

The no form of this command disables the IBGP multipath load balancing feature.

Platforms

All

ibgp-multipath

Syntax

[no] ibgp-multipath

Context

[Tree] (config>router>bgp ibgp-multipath)

Full Context

configure router bgp ibgp-multipath

Description

This command enables IBGP multipath load balancing when adding BGP routes to the route table if the route resolving the BGP nexthop offers multiple next-hops.

The no form of this command disables the IBGP multipath load balancing feature.

Default

no ibgp-multipath

Platforms

All

icmp

icmp

Syntax

icmp

Context

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

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

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

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

Full Context

configure service ies interface icmp

configure service vprn interface icmp

configure service ies subscriber-interface group-interface icmp

configure service vprn network-interface icmp

Description

Commands in this context configure Internet Control Message Protocol (ICMP) parameters on a service.

Platforms

All

  • configure service ies interface icmp
  • configure service vprn interface icmp
  • configure service vprn network-interface icmp

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

  • configure service ies subscriber-interface group-interface icmp

icmp

Syntax

icmp

Context

[Tree] (config>subscr-mgmt>git>ipv4 icmp)

Full Context

configure subscriber-mgmt group-interface-template ipv4 icmp

Description

Commands in this context configure IPv4 Internet Control Message Protocol (ICMP) parameters.

Default

icmp

Platforms

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

icmp

Syntax

icmp

Context

[Tree] (config>router>if icmp)

Full Context

configure router interface icmp

Description

This command enables access to the context to configure Internet Control Message Protocol (ICMP) parameters on a network IP interface. ICMP is a message control and error reporting protocol that also provides information relevant to IP packet processing.

Platforms

All

icmp

Syntax

[no] icmp

Context

[Tree] (debug>router>ip icmp)

Full Context

debug router ip icmp

Description

This command enables ICMP debugging.

Platforms

All

icmp

Syntax

[no] icmp

Context

[Tree] (config>sys>security>cpu-protection>ip>included-protocols icmp)

Full Context

configure system security cpu-protection ip-src-monitoring included-protocols icmp

Description

This command includes the extracted IPv4 ICMP packets for ip-src-monitoring. IPv4 ICMP packets will be subject to the per-source-rate of CPU protection policies.

Default

no icmp

Platforms

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

icmp

Syntax

icmp

Context

[Tree] (config>test-oam icmp)

Full Context

configure test-oam icmp

Description

Commands in this context configure test ICMP OAM parameters.

Platforms

All

icmp-code

icmp-code

Syntax

icmp-code icmp-code

no icmp-code

Context

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

[Tree] (config>filter>ipv6-filter>entry>match icmp-code)

[Tree] (config>filter>ip-filter>entry>match icmp-code)

[Tree] (config>filter>ipv6-exception>entry>match icmp-code)

Full Context

configure filter ip-exception entry match icmp-code

configure filter ipv6-filter entry match icmp-code

configure filter ip-filter entry match icmp-code

configure filter ipv6-exception entry match icmp-code

Description

Configures matching on /ICMPv6 code field in the /ICMPv6 header of an IPv4 or IPv6 packet as a filter match criterion or configures matching on the ICMP code field in the ICMP header of an IPv4 packet as an exception filter match criterion. An entry containing Layer 4 non-zero match criteria will not match non-initial (for example, 2nd, 3rd) fragments of a fragmented packet since only the first fragment contains the Layer 4 information. Similarly an entry containing " icmp-code 0" match criterion, may match non-initial fragments when the Layer 4 header is not present in a packet fragment and other match criteria are also met.

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

Default

no icmp-code

Parameters

icmp-code

Specifies the /ICMPv6 code value that must be present to match. Value can be expressed as a decimal integer, as well as in hexadecimal or binary format, or even using keywords. The following value shows decimal integer only.

Values

0 to 255

Platforms

VSR

  • configure filter ip-exception entry match icmp-code
  • configure filter ipv6-exception entry match icmp-code

All

  • configure filter ip-filter entry match icmp-code
  • configure filter ipv6-filter entry match icmp-code

icmp-code

Syntax

icmp-code icmp-code

no icmp-code

Context

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

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

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

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

Full Context

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

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

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

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

Description

This command configures the ICMP code match condition.

The no form of this command reverts to the default.

Parameters

icmp-code

Specifies the ICMP code numbers accepted in DHB.

Values

[0 to 255]D, [0X0..0XFF]H, [0b0..0b11111111]B

Platforms

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

icmp-code

Syntax

icmp-code icmp-code

no icmp-code

Context

[Tree] (cfg>sys>sec>cpm>ipv6-filter>entry>match icmp-code)

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

Full Context

configure system security cpm-filter ipv6-filter entry match icmp-code

configure system security cpm-filter ip-filter entry match icmp-code

Description

This command configures matching on ICMP code field in the ICMP header of an IP packet as an IP filter match criterion.

Note:

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

The behavior of the icmp-code value is dependent on the configured icmp-type value, thus a configuration with only an icmp-code value specified will have no effect. To match on the icmp-code, an associated icmp-type must also be specified.

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

Default

no icmp-code

Parameters

icmp-code

Specifies the ICMP code values that must be present to match.

Values

0 to 255

Platforms

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

icmp-echo-reply

icmp-echo-reply

Syntax

[no] icmp-echo-reply

Context

[Tree] (config>service>vprn>nat>outside>pool icmp-echo-reply)

[Tree] (config>router>nat>outside>pool icmp-echo-reply)

Full Context

configure service vprn nat outside pool icmp-echo-reply

configure router nat outside pool icmp-echo-reply

Description

IPv4 addresses in a NAT pool can be configured to respond to ICMP Echo Requests (PINGs). The configuration can be toggled online while the pool is in use.

In L2-aware NAT when port-block-extensions is disabled, the reply from an outside IP address is generated only when this IP address has at least one host (binding) behind it.

In L2-aware NAT when port-block-extensions is enabled, the reply from an outside IP address is generated regardless if a binding is present.

In LSN, the reply from an outside IP address is generated regardless if a binding is present.

The no form of the command disables ICMP echo replies.

Default

no icmp-echo-reply

Platforms

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

icmp-generation

icmp-generation

Syntax

icmp-generation

Context

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

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

[Tree] (config>ipsec>tunnel-template icmp-generation)

[Tree] (config>router>if>ipsec>ipsec-tunnel icmp-generation)

[Tree] (config>service>vprn>if>sap>ipsec-tunnel icmp-generation)

Full Context

configure service ies interface sap ip-tunnel icmp-generation

configure service vprn interface sap ip-tunnel icmp-generation

configure ipsec tunnel-template icmp-generation

configure router interface ipsec ipsec-tunnel icmp-generation

configure service vprn interface sap ipsec-tunnel icmp-generation

Description

This command enables the context to configure ICMP generation information.

Platforms

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

  • configure ipsec tunnel-template icmp-generation
  • configure service ies interface sap ip-tunnel icmp-generation
  • configure service vprn interface sap ip-tunnel icmp-generation
  • configure service vprn interface sap ipsec-tunnel icmp-generation

VSR

  • configure router interface ipsec ipsec-tunnel icmp-generation

icmp-ping

icmp-ping

Syntax

icmp-ping {ip-address | dns-name} [{bypass-routing | {interface interface-name} | {next-hop ip-address}}] [count requests] [do-not-fragment] [fc fc-name] [interval { centisecs | secs}] [pattern pattern] [rapid] [{router router-or-service | router-instance router-instance | service-name service-name}] [size bytes] [source ip-address] [ timeout timeout] [ tos type-of-service] [ttl time-to-live]

Context

[Tree] (config>saa>test>type icmp-ping)

Full Context

configure saa test type icmp-ping

Description

This command configures an ICMP traceroute test.

Parameters

ip-address | dns-name

Specifies the far-end IP address or DNS name to which to send the svc-ping request message in dotted decimal notation.

Values

ipv4-address:

a.b.c.d

ipv6-address:

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

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

x:

[0 to FFFF]H

d:

[0 to 255]D

interface

up to 32 characters. This is mandatory for link local addresses.

dns-name

up to 128 characters

bypass-routing

Specifies whether to send the ping request to a host on a directly attached network bypassing the routing table.

interface-name

Specifies the name used to refer to the interface, up to 32 characters. The name must already exist in the config>router>interface context.

next-hop ip-address

Displays only static routes with the specified next-hop IP address.

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

requests

Specifies the number of times to perform an OAM ping probe operation. Each OAM echo message request must either time out or receive a reply before the next message request is sent.

Values

1 to 100000

Default

5

do-not-fragment

Sets the DF (Do Not Fragment) bit in the ICMP ping packet (does not apply to ICMPv6).

fc-name

Specifies the forwarding class of the SAA.

Values

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

Default

nc

interval {centisecs | secs}

Specifies the minimum amount of time, in seconds, that must expire before the next message request is sent. If the rapid parameter is configured, this value is measured in centiseconds (hundredths of a second) instead of seconds.

Values

1 to 10000

Default

1

pattern

Specifies the date portion in a ping packet is filled with the pattern value specified. If not specified, a system-generated sequential pattern is used.

Values

0 to 65535

rapid

Configures the interval parameter to use centiseconds (hundredths of a second) instead of seconds.

router-or-service

Specifies the numerical reference to the router instance or service. Well known router names "Base", "management", "vpm-vr-name”, and " vpls-management" are allowed for convenience, but are mapped numerically.

Values

{router-name | vprn-svc-id}

router-name:

Base, management, cmp-vr-name, vpls-management

vprn-svc-id:

1 to 2147483647

cpm-vr-name:

Up to 32 characters

The parameter router-instance is preferred for specifying the router or service.

Default

Base

router-instance

Specifies the preferred method for entering a service name. Stored as the service name. Only the service linking function is allowed for both mixed-mode and model-driven configuration modes.

Values

router-name, vprn-svc-name

router-name: Base, management, vpls-management, cpm-vr-name

vprn-svc-name: up to 64 characters

cpm-vr-name: up to 32 characters

service-name

Specifies the alias function that allows the service name to be used, converted and stored as a service ID, up to 64 characters.

The router-instance parameter is preferred for specifying the router or service.

bytes

Specifies the request packet size in bytes, expressed as a decimal integer.

Values

0 to 16384

Default

56

source ip-address

Specifies the IP address to be used.

Values

ipv4-address:

a.b.c.d

ipv6-address:

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

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

x:

[0 to FFFF]H

d:

[0 to 255]D

timeout

Specifies the override time that the router waits for a message reply after sending the last probe for a specific test. Upon the expiration of the time out, the test is marked complete and no more packets are processed for any of those request probes.

Values

1 to 10

Default

5

type-of-service

Specifies the service type.

Values

0 to 255

Default

0

time-to-live

Specifies the TTL value for the MPLS label, expressed as a decimal integer.

Values

1 to 128

Default

64

Platforms

All

icmp-query

icmp-query

Syntax

icmp-query [min minutes] [ sec seconds]

no icmp-query

Context

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

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

Full Context

configure service nat nat-policy timeouts icmp-query

configure service nat up-nat-policy timeouts icmp-query

Description

This command configures the timeout applied to an ICMP query session.

Default

icmp-query min 1

Parameters

min minutes

Specifies the timeout, in minutes, applied to an ICMP query session.

Values

1 to 4

Default

1

sec seconds

Specifies the timeout, in seconds, applied to an ICMP query session.

Values

1 to 59

Platforms

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

icmp-trace

icmp-trace

Syntax

icmp-trace [ip-address | dns-name] [router router-or-service | router-instance router-instance | service-name service-name] [source ip-address] [tos type-of-service] [ttl ttl] [wait milliseconds]

Context

[Tree] (config>saa>test>type icmp-trace)

Full Context

configure saa test type icmp-trace

Description

This command configures an ICMP traceroute test.

Parameters

ip-address

Specifies the far-end IP address to which to send the svc-ping request message in dotted decimal notation.

Values

ipv4-address:

a.b.c.d

ipv6-address:

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

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

x:

[0 to FFFF]H

d:

[0 to 255]D

dns-name

up to 63 characters

dns-name

Specifies the DNS name of the far-end device to which to send the svc-ping request message, up to 63 characters.

router-instance

Specifies the preferred method for entering a service name. Stored as the service name. Only the service linking function is allowed for both mixed-mode and model-driven configuration modes.

Values

{router-name | vprn-svc-name}

router-name: Base, management, vpls-management, cpm-vr-name

vprn-svc-name: up to 64 characters

cpm-vr-name: up to 32 characters

Default

Base

router-or-service

Specifies the numerical reference to the router instance or service. Well known router names "Base", "management" and " vpls-management" are allowed for convenience, but are mapped numerically.

Values

{router-name | vprn-svc-id}

router-name:

Base, management, vpls-management

vprn-svc-id:

1 to 2147483647

The parameter router-instance is preferred for specifying the router or service.

Default

Base

service-name

Specifies the alias function that allows the service name to be used, converted and stored as service ID, up to 64 characters.

The parameter router-instance is preferred for specifying the router or service.

source ip-address

Specifies the IP address to be used.

Values

ipv4-address:

a.b.c.d

ipv6-address:

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

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

x:

[0 to FFFF]H

d:

[0 to 255]D

type-of-service

Specifies the service type.

Values

0 to 255

Default

0

ttl

Specifies the TTL value for the MPLS label, expressed as a decimal integer.

Values

1 to 255

Default

30

milliseconds

Specifies the time, in milliseconds, to wait for a response to a probe, expressed as a decimal integer.

Values

10 to 60000

Default

5000

Platforms

All

icmp-tunneling

icmp-tunneling

Syntax

[no] icmp-tunneling

Context

[Tree] (config>router icmp-tunneling)

Full Context

configure router icmp-tunneling

Description

This command enables the tunneling of ICMP reply packets over MPLS LSP at a LSR node as per RFC 3032.

The LSR part of this feature consists of crafting the reply ICMP packet of type=11- 'time exceeded', with a source address set to a local address of the LSR node, and appending the IP header and leading payload octets of the original datagram. The system skips the lookup of the source address of the sender of the label TTL expiry packet, which becomes the destination address of the ICMP reply packet. Instead, CPM injects the ICMP reply packet in the forward direction of the MPLS LSP the label TTL expiry packet was received from. The TTL of pushed labels should be set to 255.

The source address of the ICMP reply packet is determined as follows. The LSR uses the address of the outgoing interface for the MPLS LSP. With LDP LSP or BGP LSP multiple ECMP next-hops can exist and in such a case the first outgoing interface is selected. If that interface does not have an address of the same family (IPv4 or IPv6) as the ICMP packet, then the system address of the same family is selected. If one is not configured, the packet is dropped.

When the packet is received by the egress LER, it performs a regular user packet lookup in the data path in the GRT context for BGP shortcut, 6PE, and BGP label route prefixes, or in VPRN context for VPRN and 6VPE prefixes. It then forwards it to the destination, which is the sender of the original packet which TTL expired at the LSR.

If the egress LER does not have a route to the destination of the ICMP packet, it drops the packets.

The rate of the tunneled ICMP replies at the LSR can be directly or indirectly controlled by the existing IOM level and CPM levels mechanisms. Specifically, the rate of the incoming UDP traceroute packets received with a label stack can be controlled at ingress IOM using the distributed CPU protection feature. The rate of the ICMP replies by CPM can also be directly controlled by configuring a system wide rate limit for packets ICMP replies to MPLS expired packets which are successfully forwarded to CPM using the command 'configure system security vprn-network-exceptions'. While this command's name refers to VPRN service, this feature rate limits ICMP replies for packets received with any label stack, including VPRN and shortcuts.

The 7450 ESS, 7750 SR, and 7950 XRS implementation supports appending to the ICMP reply of type Time Exceeded the MPLS label stack object defined in RFC 4950. It does not include it in the ICMP reply type of Destination unreachable.

The new MPLS Label Stack object permits an LSR to include label stack information including label value, EXP, and TTL field values, from the encapsulation header of the packet that expired at the LSR node. The ICMP message continues to include the IP header and leading payload octets of the original datagram.

In order to include the MPLS Label Stack object, SR OS implementation adds support of RFC 4884 which defines extensions for a multi-part ICMPv4/v6 message of type Time Exceeded.

The no form of command disables the tunneling of ICMP reply packets over MPLS LSP at a LSR node.

Default

no icmp-tunneling

Platforms

All

icmp-type

icmp-type

Syntax

icmp-type icmp-type

no icmp-type

Context

[Tree] (config>filter>ip-filter>entry>match icmp-type)

[Tree] (config>filter>ipv6-filter>entry>match icmp-type)

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

[Tree] (config>filter>ipv6-exception>entry>match icmp-type)

Full Context

configure filter ip-filter entry match icmp-type

configure filter ipv6-filter entry match icmp-type

configure filter ip-exception entry match icmp-type

configure filter ipv6-exception entry match icmp-type

Description

This command configures matching on the /ICMPv6 type field in the /ICMPv6 header of an IPv4 or IPv6 packet as a filter match criterion or configures matching on the ICMP type field in the ICMP header of an IPv4 packet as an exception filter match criterion. An entry containing Layer 4 non-zero match criteria will not match non-initial (2nd, 3rd, etc.) fragments of a fragmented packet since only the first fragment contains the Layer 4 information. Similarly an entry containing " icmp-type 0" match criterion, may match non-initial fragments when the Layer 4 header is not present in a packet fragment and other match criteria are also met.

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

Default

no icmp-type

Parameters

icmp-type

Specifies the /ICMPv6 type value that must be present to match. Value can be expressed as a decimal integer, as well as in hexadecimal or binary format, or even using keywords. The following value shows decimal integer only.

Values

0 to 255

Platforms

All

  • configure filter ip-filter entry match icmp-type
  • configure filter ipv6-filter entry match icmp-type

VSR

  • configure filter ipv6-exception entry match icmp-type
  • configure filter ip-exception entry match icmp-type

icmp-type

Syntax

icmp-type icmp-type

no icmp-type

Context

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

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

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

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

Full Context

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

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

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

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

Description

This command configures the ICMP type match condition.

The no form of this command reverts to the default.

Parameters

icmp-type

Specifies the ICMP type numbers accepted in DHB.

Values

[0 to 255]D, [0X0..0XFF]H, [0b0..0b11111111]B

Platforms

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

icmp-type

Syntax

icmp-type icmp-type

no icmp-type

Context

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

[Tree] (config>qos>network>egress>ipv6-criteria>entry>match icmp-type)

Full Context

configure qos network egress ip-criteria entry match icmp-type

configure qos network egress ipv6-criteria entry match icmp-type

Description

This command configures matching on the ICMP or ICMPv6 type field in the ICMP or ICMPv6 header of an IPv4 or IPv6 packet as a network QoS match criterion.

An entry containing Layer 4 non-zero match criteria will not match non-initial (2nd, 3rd, etc.) fragments of a fragmented packet since only the first fragment contains the Layer 4 information. Similarly, an entry containing " icmp-type 0" match criterion, may match non-initial fragments when the Layer 4 header is not present in a packet fragment and other match criteria are also met.

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

Default

no icmp-type

Parameters

icmp-type

Specifies the ICMP or ICMPv6 type value that must be present to match. Value can be expressed as a decimal integer, or in hexadecimal or binary format, or even using keywords.

Values

0 to 255 (Decimal)

0 to FF (Hexadecimal)

0 to 11111111 (Binary)

Platforms

All

icmp-type

Syntax

icmp-type icmp-type

no icmp-type

Context

[Tree] (cfg>sys>sec>cpm>ipv6-filter>entry>match icmp-type)

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

Full Context

configure system security cpm-filter ipv6-filter entry match icmp-type

configure system security cpm-filter ip-filter entry match icmp-type

Description

This command configures matching on ICMP type field in the ICMP header of an IP packet as an IP filter match criterion.

Note:

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

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

Default

no icmp-type

Parameters

icmp-type

Specifies the ICMP type values that must be present to match.

Values

0 to 255

Platforms

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

icmp6

icmp6

Syntax

icmp6

Context

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

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

Full Context

configure service ies interface ipv6 icmp6

configure service vprn interface ipv6 icmp6

Description

This command configures ICMPv6 parameters for the interface.

Platforms

All

icmp6

Syntax

icmp6

Context

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

Full Context

configure router interface ipv6 icmp6

Description

Commands in this context configure ICMPv6 parameters for the interface.

Platforms

All

icmp6

Syntax

icmp6 [ip-int-name]

no icmp6

Context

[Tree] (debug>router>ip icmp6)

Full Context

debug router ip icmp6

Description

This command enables ICMPv6 debugging.

Platforms

All

icmp6-generation

icmp6-generation

Syntax

icmp6-generation

Context

[Tree] (config>router>if>ipsec>ipsec-tunnel icmp6-generation)

[Tree] (config>router>if>ipsec>ipsec-tunnel>dyn icmp6-generation)

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

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

[Tree] (config>service>vprn>if>sap>ipsec-tun icmp6-generation)

[Tree] (config>service>ies>if>ipsec>ipsec-tunnel icmp6-generation)

[Tree] (config>service>vprn>if>ipsec>ipsec-tunnel icmp6-generation)

[Tree] (config>ipsec>tnl-temp icmp6-generation)

Full Context

configure router interface ipsec ipsec-tunnel icmp6-generation

configure router interface ipsec ipsec-tunnel dyn icmp6-generation

configure service vprn interface sap ip-tunnel icmp6-generation

configure service ies interface sap ip-tunnel icmp6-generation

configure service vprn interface sap ipsec-tunnel icmp6-generation

configure service ies interface ipsec ipsec-tunnel icmp6-generation

configure service vprn interface ipsec ipsec-tunnel icmp6-generation

configure ipsec tunnel-template icmp6-generation

Description

This command enables the ICMPv6 packet generation configuration context.

Platforms

VSR

  • configure router interface ipsec ipsec-tunnel icmp6-generation
  • configure service ies interface ipsec ipsec-tunnel icmp6-generation
  • configure service vprn interface ipsec ipsec-tunnel icmp6-generation

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

  • configure service ies interface sap ip-tunnel icmp6-generation
  • configure ipsec tunnel-template icmp6-generation
  • configure service vprn interface sap ipsec-tunnel icmp6-generation
  • configure service vprn interface sap ip-tunnel icmp6-generation

icmp6-query

icmp6-query

Syntax

icmp6-query [min minutes] [ sec seconds]

no icmp6-query

Context

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

Full Context

configure service nat firewall-policy timeouts icmp6-query

Description

This command configures the timeout interval for ICMPv6 query mappings.

The no form of the command reverts the timeout interval to the default of 1 minute.

Default

icmp6-query min 1

Parameters

minutes

Specifies the number of minutes in the ICMP query mapping timeout interval.

Values

1 to 4

seconds

Specifies the number of seconds in the ICMP query mapping timeout interval.

Values

0 to 59

Platforms

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

id

id

Syntax

[no] id service-id

Context

[Tree] (debug>service id)

Full Context

debug service id

Description

This command enables debugging for the specified service ID.

The no form of this command disables the debugging.

Parameters

service-id

The ID that uniquely identifies a service.

Values

service-id: 1 to 214748364

svc-name: A string up to 64 characters in length

Platforms

All

id-permission

id-permission

Syntax

id-permission {chassis}

no id-permission

Context

[Tree] (cfg>eth-cfm>domain>assoc>bridge id-permission)

Full Context

configure eth-cfm domain association bridge-identifier id-permission

Description

This command allows the operator to include the sender-id TLV information that was specified under the config>eth>system>sender-id configuration for service MEPs and MIPs. When this option is present under the maintenance association, the specific MPs in the association includes the sender-id TLV information in ETH-CFM PDUs. MEPs include the sender-id TLV for CCM (not sub second CCM enabled MEPs), LBM/LBR, and LTM/LTR. MIPs includes this value in the LBR and LTR PDUs.

Note:

LBR functions reflect all TLVs received in the LBM unchanged including the SenderID TLV. Transmission of the Management Domain and Management Address fields are not supported in this TLV.

Parameters

chassis

Sends the configured chassis information defined under in the eth-cfm>system>sender-id context.

Platforms

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

id-permission

Syntax

id-permission {chassis | defer}

no id-permission

Context

[Tree] (config>eth-cfm>default-domain>bridge-identifier id-permission)

Full Context

configure eth-cfm default-domain bridge-identifier id-permission

Description

This command enables the inclusion of the Sender ID TLV information specified under the config> eth>system>sender-id command for installed MEPs and MIPs. The inclusion of the Sender ID TLV is based on the configured value. The Sender ID TLV is supported for ETH-CC, ETH-LB, and ETH-LB PDUs.

Note: LBR functions reflect back all TLVs received in the LBM, unchanged, including the Sender ID TLV. Transmission of the Management Domain and Management Address fields are not supported in this TLV.

The no form of this command disables the inclusion of the Sender ID TLV.

Default

id-permission defer (config>eth-cfm>default-domain>bridge-identifier)

no id-permission (config>eth-cfm>domain>association>bridge)

Parameters

chassis

Keyword to include the Sender ID TLV with a value equal to the sender-id configured under the eth-cfm>system context.

defer

Keyword to specify that id-permission will inherit the value from the global read-only system values.

Platforms

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

identification-strings

identification-strings

Syntax

identification-strings option-number [create]

no identification-strings

Context

[Tree] (config>subscr-mgmt>loc-user-db>ppp>host identification-strings)

[Tree] (config>subscr-mgmt>loc-user-db>ipoe>host identification-strings)

Full Context

configure subscriber-mgmt local-user-db ppp host identification-strings

configure subscriber-mgmt local-user-db ipoe host identification-strings

Description

This command specifies identification strings for the subscriber. This is useful when the server is centralized with Enhanced Subscriber Management (ESM) in a lower level in the network. These strings are parsed by a downstream Python script or they can be used literally if the strings-from-option option in the config>subscr-mgmt>sub-ident-policy context is set to this option number. In this case, the option number may be set to any allowed number (between 224 and 254 is suggested, as these are not dedicated to specific purposes). If the option number is not given, a default value of 254 is used. For PPPoE only, if the local user database is attached to the PPPoE node under the group interface and not to a local DHCP server, the strings are used internally so the option number is not used.

The no form of this command returns to the default.

Parameters

option-number

Specifies identification strings for the subscriber.

Values

1 to 254

Platforms

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

identifier

identifier

Syntax

identifier identifier

no identifier

Context

[Tree] (config>system>bluetooth>module identifier)

Full Context

configure system bluetooth module identifier

Description

This command configures an identifier string used to advertise the Bluetooth module during pairing operations.

If no identifier is specified by the user, the default is derived from the platform type, the CPM slot, and the serial number of the chassis.

For example, a device with a platform field of 7750, SR-12 chassis, and a CPM serial number of NS23456 would have a Bluetooth identifier of "7750-SR-12-CPM-A-NS23456." for the CPM in slot A.

The no form of this command resets the identifier back to the default.

Parameters

identifier

Specifies string, up to 32 characters, using the values in the range 0-9, a-z, or A-Z.

Platforms

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

idi

idi

Syntax

idi any

idi ipv4-prefix {any | ipv4-prefix/ipv4-prefix-length}

idi ipv6-prefix {any | ipv6-prefix/ipv6-prefix-length}

idi string-type string-type string-value string-value

no idi

Context

[Tree] (config>ipsec>client-db>client>client-id idi)

Full Context

configure ipsec client-db client client-identification idi

Description

This command specifies a match criteria that uses the peer’s identification initiator (IDi) as the input, only one IDi criteria can be configured for a given client entry. This command supports the following matching methods:

  • idi any: Matches any type of IDi with any value.

  • idi ipv4-prefix: Matches an IDi with the type ID_IPV4_ADDR. If the any parameter is specified, then it will match any IPv4 address. If an IPv4 prefix is specified, then it will match an IPv4 address that is within the specified prefix.

  • idi ipv6-prefix: Matches an IDi with the type ID_IPV6_ADDR. If the any parameter is specified, then it will match any IPv6 address. If an IPv6 prefix is specified, then it will match an IPv6 address that is within the specified prefix.

  • idi string-type: Supports following type of IDi:

    • FQDN: Either a full match or a suffix match

    • RFC822: Either a full match or a suffix match

The no form of this command reverts to the default.

Default

no idi

Parameters

any

Matches any type of IDi with any value.

ipv4-prefix/ipv4-prefix-length

Matches any IPv4 address and prefix.

ipv6-prefix/ipv6-prefix-length

Matches any IPv6 address and prefix.

string-type

Matches the type of IDi value for this IPsec client entry.

Values

fqdn, fqdn-suffix, rfc822, rfc822-suffix

string-value

Matches the IDi value within the client ID for this IPsec client entry up to 256 characters.

Platforms

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

idi

Syntax

[no] idi

Context

[Tree] (config>ipsec>client-db>match-list idi)

Full Context

configure ipsec client-db match-list idi

Description

This command enables the Identification Initiator (IDi) type in the IPsec client matching process.

The no form of this command disables the IDi matching process.

Default

no idi

Platforms

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

idle-cycle-flag

idle-cycle-flag

Syntax

idle-cycle-flag {flags | ones}

no idle-cycle-flag

Context

[Tree] (config>port>tdm>ds3 idle-cycle-flag)

[Tree] (config>port>tdm>e3 idle-cycle-flag)

Full Context

configure port tdm ds3 idle-cycle-flag

configure port tdm e3 idle-cycle-flag

Description

This command configures the value that the HDLC TDM DS-0, E-3, or DS-3 interface transmits during idle cycles. For ATM ports/channels/channel-groups, the configuration does not apply and only the no form is accepted.

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

Default

flags (0x7E)

no flags (ATM)

Parameters

flags

Specifies that 0x7E is used as the idle cycle flag.

ones

Specifies that 0xFF is used as the idle cycle flag.

Platforms

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

idle-filter

idle-filter

Syntax

[no] idle-filter

Context

[Tree] (config>service>vpls>gsmp>group idle-filter)

[Tree] (config>service>vprn>gsmp>group idle-filter)

Full Context

configure service vpls gsmp group idle-filter

configure service vprn gsmp group idle-filter

Description

This command when applied will filter out new incoming ANCP messages while the subscriber DSL-line-state is idle. The command takes effect at the time that it is applied. Existing subscribers already in idle state are not purged from the database.

The no form of this command reverts to the default.

Platforms

All

idle-filter

Syntax

[no] idle-filter

Context

[Tree] (config>service>vpls>gsmp idle-filter)

Full Context

configure service vpls gsmp idle-filter

Description

This command when applied will filter out new subscriber’s ANCP messages from subscriber with "DSL-line-state” IDLE.

Default

no idle-filter

Platforms

All

idle-filter

Syntax

idle-filter

no idle-filter

Context

[Tree] (config>service>vprn>gsmp idle-filter)

Full Context

configure service vprn gsmp idle-filter

Description

This command when applied will filter out new subscriber’s ANCP messages from subscriber with "DSL-line-state” IDLE.

Default

no idle-filter

Platforms

All

idle-payload-fill

idle-payload-fill

Syntax

idle-payload-fill {all-ones}

idle-payload-fill pattern pattern

no idle-payload-fill

Context

[Tree] (config>port>tdm>ds1>channel-group idle-payload-fill)

[Tree] (config>port>tdm>e1>channel-group idle-payload-fill)

Full Context

configure port tdm ds1 channel-group idle-payload-fill

configure port tdm e1 channel-group idle-payload-fill

Description

This command defines the data pattern to be transmitted when the circuit emulation service is not operational or temporarily experiences under-run conditions. This command is only valid for cesopsn and cesopsn-cas circuit emulation services. It is blocked with a warning for unstructured (satop) circuit emulation services.

Default

idle-payload-fill all-ones

Parameters

all-ones

Defines the 8 bit value to be transmitted as 11111111.

pattern

Transmits a user-defined pattern.

Values

0 to 255, accepted in decimal, hex or binary

Platforms

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

idle-signal-fill

idle-signal-fill

Syntax

idle-signal-fill {all-ones}

idle-signal-fill pattern pattern

no idle-signal-fill

Context

[Tree] (config>port>tdm>e1>channel-group idle-signal-fill)

[Tree] (config>port>tdm>ds1>channel-group idle-signal-fill)

Full Context

configure port tdm e1 channel-group idle-signal-fill

configure port tdm ds1 channel-group idle-signal-fill

Description

This command defines the signaling pattern to be transmitted when the circuit emulation service is not operational or temporarily experiences under-run conditions. This command is only valid for cesopsn-cas circuit emulation services. It is blocked with a warning for unstructured (satop) and basic cesopsn circuit emulation services.

Default

idle-signal-fill all-ones

Parameters

all-ones

Defines the 8 bit value to be transmitted as 11111111.

pattern

Transmits a user-defined pattern.

Values

0 to 15, accepted in decimal, hex or binary

Platforms

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

idle-time

idle-time

Syntax

idle-time idle

no idle-time

Context

[Tree] (config>system>grpc-tunnel>destination-group>tcp-keepalive idle-time)

[Tree] (config>system>telemetry>destination-group>tcp-keepalive idle-time)

[Tree] (config>system>grpc>tcp-keepalive idle-time)

Full Context

configure system grpc-tunnel destination-group tcp-keepalive idle-time

configure system telemetry destination-group tcp-keepalive idle-time

configure system grpc tcp-keepalive idle-time

Description

This command configures the amount of time, in seconds, that the connection must remain idle before TCP keepalive probes are sent.

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

Default

idle-time 600

Parameters

idle

Specifies the number of seconds before the first TCP keepalive probe is sent.

Values

1 to 100000

Default

600

Platforms

All

idle-timeout

idle-timeout

Syntax

idle-timeout idle-timeout

idle-timeout infinite

no idle-timeout

Context

[Tree] (config>router>l2tp>group>tunnel idle-timeout)

[Tree] (config>service>vprn>l2tp>group idle-timeout)

[Tree] (config>router>l2tp>group idle-timeout)

[Tree] (config>service>vprn>l2tp idle-timeout)

[Tree] (config>service>vprn>l2tp>group>tunnel idle-timeout)

Full Context

configure router l2tp group tunnel idle-timeout

configure service vprn l2tp group idle-timeout

configure router l2tp group idle-timeout

configure service vprn l2tp idle-timeout

configure service vprn l2tp group tunnel idle-timeout

Description

This command configures the period of time that an established tunnel with no active sessions persists before being disconnected.

Enter the no form of this command to maintain a persistent tunnel.

The no form of this command removes the idle timeout from the configuration.

Default

no idle-timeout

Parameters

idle-timeout

Specifies the idle timeout value, in seconds until the group is removed.

Default

no idle-timeout

Values

0 to 3600

infinite

Specifies that the tunnel is not closed when idle.

Platforms

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

idle-timeout

Syntax

idle-timeout timeout

no idle-timeout

Context

[Tree] (config>subscr-mgmt>sla-prof>cat-map>category idle-timeout)

Full Context

configure subscriber-mgmt sla-profile category-map category idle-timeout

Description

This command defines the idle-timeout value.

The no form of this command reverts to the default.

Parameters

timeout

Specifies the idle-timeout, in seconds.

Values

60 to 15552000

Platforms

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

idle-timeout

Syntax

idle-timeout action idle-timeout-action

no idle-timeout

Context

[Tree] (config>service>ies>sub-if>grp-if>wlan-gw>ranges>range idle-timeout)

[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw>ranges>range idle-timeout)

Full Context

configure service ies subscriber-interface group-interface wlan-gw vlan-tag-ranges range idle-timeout

configure service vprn subscriber-interface group-interface wlan-gw vlan-tag-ranges range idle-timeout

Description

This command specifies idle-timeout behavior for DSM UEs and UEs undergoing (ISA-based) portal authentication. This knob only specifies the desired action, idle-timeout is activated by RADIUS on a per-UE basis.

The no form of this command resets the idle-timeout to its default.

Default

idle-timeout action remove

Parameters

action

Specifies which action to perform when the idle-timeout timer goes off.

Values

remove, shcv

Platforms

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

idle-timeout

Syntax

idle-timeout {minutes | disable}

no idle-timeout

Context

[Tree] (config>system>login-control idle-timeout)

Full Context

configure system login-control idle-timeout

Description

This command configures the idle timeout for console, Telnet, SSH, and FTP sessions before the session is terminated by the system.

By default, each idle console, Telnet, SSH, or FTP session times out after 30 minutes of inactivity.

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

Default

idle-timeout 30

Parameters

minutes

Specifies the idle timeout in minutes. Allowed values are 1 to 1440.

Values

1 to 1440

disable

When the disable option is specified, a session will never timeout. To re-enable idle timeout, enter the command without the disable option.

Platforms

All

idle-timeout-action

idle-timeout-action

Syntax

idle-timeout-action {shcv-check | terminate}

no idle-timeout-action

Context

[Tree] (config>subscr-mgmt>sla-prof>cat-map>category idle-timeout-action)

Full Context

configure subscriber-mgmt sla-profile category-map category idle-timeout-action

Description

This command defines the action to be executed when the idle-timeout is reached. The action is performed for all hosts associated with the sla-profile instance.

The no form of this command reverts to the default.

Default

idle-timeout-action terminate

Parameters

shcv-check

Performs a subscriber host connectivity verification check (IPoE hosts only).

Note:

Host connectivity verification must be enabled on the group-interface where the host is connected.

If the check is successful, the hosts are not disconnected and the idle-timeout timer is reset.

If the check fails, the hosts are deleted, similar as for idle-timeout-action terminate.

terminate

Deletes the subscriber host from the system: for PPP hosts, a terminate request is send; for IPoE hosts a DHCP release is send to the DHCP server.

Platforms

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

ies

ies

Syntax

ies service-id [customer customer-id] [create] [ vpn vpn-id] [name name]

no ies service-id

Context

[Tree] (config>service ies)

Full Context

configure service ies

Description

This command creates or edits an IES service instance.

The ies command creates or maintains an Internet Ethernet Service (IES). If the service-id does not exist, a context for the service is created. If the service-id exists, the context for editing the service is entered.

IES services allow the creation of customer facing IP interfaces in the same routing instance used for service network core routing connectivity. IES services require that the IP addressing scheme used by the subscriber must be unique between it and other addressing schemes used by the provider and potentially the entire Internet.

IP interfaces defined within the context of an IES service ID must have a SAP created as the access point to the subscriber network. This allows a combination of bridging and IP routing for redundancy purposes.

When a service is created, the customer keyword and customer-id must be specified and associates the service with a customer. The customer-id must already exist having been created using the customer command in the service context. Once a service has been created with a customer association, it is not possible to edit the customer association. The service must be deleted and recreated with a new customer association.

Once a service is created, the use of the customer customer-id is optional for navigating into the service configuration context. Attempting to edit a service with the incorrect customer-id specified results in an error.

Multiple IES services are created to separate customer owned IP interfaces. More than one IES service may be created for a single customer ID. More than one IP interface may be created within a single IES service ID. All IP interfaces created within an IES service ID belongs to the same customer.

By default, no IES service instances exist until they are explicitly created.

The no form of this command deletes the IES service instance with the specified service-id. The service cannot be deleted until all the IP interfaces defined within the service ID have been shut down and deleted.

Parameters

service-id

Specifies the unique service identification number identifying the service in the service domain. This ID must be unique to this service and may not be used for any other service of any type. The service-id must be the same number used for every router on which this service is defined.

Values

service-id: 1 to 214748364

svc-name: A string up to 64 characters

customer-id

Specifies the customer ID number to be associated with the service. This parameter is required on service creation and optional for service editing or deleting.

Values

1 to 2147483647

vpn-id

Specifies the VPN ID number used to identify virtual private networks (VPNs) by a VPN identification number.

Values

1 to 2147483647

Default

null (0)

create

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

name name

This parameter configures an optional service name, up to 64 characters, which adds a name identifier to a given service to then use that service name in configuration references as well as display and use service names in show commands throughout the system. This helps the service provider or administrator to identify and manage services within the SR OS platforms.

All services are required to assign a service ID to initially create a service. However, either the service ID or the service name can be used to identify and reference a given service once it is initially created.

If a name is not specified at creation time, then SR OS assigns a string version of the service-id as the name.

Service names may not begin with an integer (0 to 9).

Values

name: up to 64 characters

Platforms

All

ies

Syntax

[no] ies service-id interface ip-int-name

[no] ies service-id subscriber-interface ip-int-name group-interface ip-int-name

Context

[Tree] (config>cflowd>collector>exp-filter>if-list>svc ies)

Full Context

configure cflowd collector export-filter interface-list service ies

Description

This command configures which IES service interfaces' flow data is being sent to this collector.

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

Parameters

service-id

Specifies the unique service identification number or string identifying the service in the service domain. This ID must be unique to this service and may not be used for any other service of any type. The service-id must be the same number used for every SR OS on which this service is defined.

Values

service-id: 1 to 2147483647

svc-name: 64 characters maximum

interface ip-int-name

Specifies the name of the IP interface. Interface names must be unique within the group of defined IP interfaces for config router interface and config service ies interface commands. An interface name cannot be in the form of an IP address. Interface names can be from 1 to 32 alphanumeric characters and must start with a letter. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.

subscriber-interface ip-int-name

Specifies the interface name of a subscriber interface. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes and must start with a letter.

group-interface ip-int-name

Specifies the interface name of a group interface. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes and must start with a letter.

Platforms

All

ies-vprn-only-sap-parameters

ies-vprn-only-sap-parameters

Syntax

ies-vprn-only-sap-parameters

Context

[Tree] (config>subscr-mgmt>msap-policy ies-vprn-only-sap-parameters)

Full Context

configure subscriber-mgmt msap-policy ies-vprn-only-sap-parameters

Description

Commands in this context configure managed SAP IES and VPRN properties. VPRN services are supported on the 7750 SR only.

Platforms

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

if-attribute

if-attribute

Syntax

if-attribute

Context

[Tree] (config>router if-attribute)

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

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

[Tree] (config>router>interface if-attribute)

Full Context

configure router if-attribute

configure service ies interface if-attribute

configure service vprn interface if-attribute

configure router interface if-attribute

Description

This command creates the context to configure or apply IP interface attributes such as administrative group (admin-group) or Shared Risk Loss Group (SRLG).

Platforms

All

if-num

if-num

Syntax

if-num if-num

no if-num

Context

[Tree] (config>router>mpls>if>mpls-tp-mep if-num)

Full Context

configure router mpls interface mpls-tp-mep if-num

Description

This command configures the MPLS-TP interface number for the MPLS interface. This is a 32-bit unsigned integer that is node-wide unique.

Parameters

if-num

Specifies a 32-bit value that is unique to the node.

Values

1 to 4294967295

Platforms

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

if-num-validation

if-num-validation

Syntax

if-num-validation {enable | disable}

no if-num-validation

Context

[Tree] (config>router>mpls>if>mpls-tp-mep if-num-validation)

Full Context

configure router mpls interface mpls-tp-mep if-num-validation

Description

The if-num-validation command is used to enable or disable validation of the if-num in LSP Trace packet against the locally configured if-num for the interface over which the LSP Trace packet was received at the egress LER. This is because some third-party implementations may not perform interface validation for unnumbered MPLS-TP interfaces and instead set the if-num in the DSMAP TLV to 0. If the value is enable, the node performs the validation of the ingress and egress if-nums received in the LSP echo request messages that ingress on this MPLS-interface. It validates that the message arrives on the interface as identified by the ingress if-num, and is forwarded on the interface as identified by the egress if-num.

If the value is disable, no validation is performed for the ingress and egress if-nums received in the LSP echo request messages that ingress on this MPLS-interface.

Default

if-num-validation enable

Parameters

enable

Enables interface number validation.

disable

Disables interface number validation.

Platforms

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

if-policy

if-policy

Syntax

if-policy mcac-if-policy-name

no if-policy

Context

[Tree] (config>subscr-mgmt>msap-policy>vpls-only>igmp-snp>mcac if-policy)

Full Context

configure subscriber-mgmt msap-policy vpls-only-sap-parameters igmp-snooping mcac if-policy

Description

This command assigns an existing MCAC interface policy to this MSAP policy.

The no form of this command removes the MCAC interface policy association.

Parameters

mcac-if-policy-name

Specifies an existing MCAC interface policy up to 32 characters.

Platforms

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

if-policy

Syntax

if-policy if-policy-name

no if-policy

Context

[Tree] (config>service>vpls>mesh-sdp>igmp-snooping>mcac if-policy)

[Tree] (config>service>vpls>spoke-sdp>mld-snooping>mcac if-policy)

[Tree] (config>service>vpls>mesh-sdp>mld-snooping>mcac if-policy)

[Tree] (config>service>vpls>sap>igmp-snooping>mcac if-policy)

[Tree] (config>service>vpls>spoke-sdp>igmp-snooping>mcac if-policy)

[Tree] (config>service>vpls>sap>mld-snooping>mcac if-policy)

Full Context

configure service vpls mesh-sdp igmp-snooping mcac if-policy

configure service vpls spoke-sdp mld-snooping mcac if-policy

configure service vpls mesh-sdp mld-snooping mcac if-policy

configure service vpls sap igmp-snooping mcac if-policy

configure service vpls spoke-sdp igmp-snooping mcac if-policy

configure service vpls sap mld-snooping mcac if-policy

Description

This command assigns existing MCAC interface policy to this interface. MCAC interface policy is not supported with MLD-snooping, therefore executing the command in the mld-snooping contexts will return an error.

The no form of this command removes the MCAC interface policy association.

Default

no if-policy

Parameters

mcac-if-policy-name

Specifies an existing MCAC interface policy

Platforms

All

if-policy

Syntax

if-policy if-policy-name

no if-policy

Context

[Tree] (config>service>vprn>mld>if>mcac if-policy)

[Tree] (config>service>vprn>mld>grp-if>mcac if-policy)

[Tree] (config>service>vprn>pim>if>mcac if-policy)

[Tree] (config>service>vprn>igmp>if>mcac if-policy)

[Tree] (config>service>vprn>igmp>grp-if>mcac if-policy)

Full Context

configure service vprn mld interface mcac if-policy

configure service vprn mld group-interface mcac if-policy

configure service vprn pim interface mcac if-policy

configure service vprn igmp interface mcac if-policy

configure service vprn igmp group-interface mcac if-policy

Description

This command assigns existing an MCAC interface policy to this interface.

The no form of this command removes the MCAC interface policy association.

Default

no if-policy

Parameters

if-policy-name

Specifies an existing MCAC interface policy, up to 32 characters.

Platforms

All

  • configure service vprn pim interface mcac if-policy
  • configure service vprn igmp interface mcac if-policy
  • configure service vprn mld interface mcac if-policy

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

  • configure service vprn mld group-interface mcac if-policy
  • configure service vprn igmp group-interface mcac if-policy

if-policy

Syntax

ip-policy if-policy-name

no if-policy

Context

[Tree] (config>router>mld>grp-if>mcac if-policy)

[Tree] (config>router>pim>if>mcac if-policy)

[Tree] (config>router>mld>if>mcac if-policy)

[Tree] (config>router>igmp>if>mcac if-policy)

[Tree] (config>router>igmp>grp-if>mcac if-policy)

Full Context

configure router mld group-interface mcac if-policy

configure router pim interface mcac if-policy

configure router mld interface mcac if-policy

configure router igmp interface mcac if-policy

configure router igmp group-interface mcac if-policy

Description

This command assigns an existing MCAC interface policy to the interface.

The no form removes the MCAC interface policy association.

Default

no if-policy

Parameters

if-policy-name

Specifies an existing MCAC interface policy, up to 32 characters.

Platforms

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

  • configure router mld group-interface mcac if-policy
  • configure router igmp group-interface mcac if-policy

All

  • configure router pim interface mcac if-policy
  • configure router mld interface mcac if-policy
  • configure router igmp interface mcac if-policy

if-policy

Syntax

[no] if-policy if-policy-name

Context

[Tree] (config>router>mcac if-policy)

Full Context

configure router mcac if-policy

Description

This command creates an MCAC interface policy and enables the context to configure parameters for the policy.

The no form of this command deletes the MCAC interface policy.

Parameters

if-policy-name

Specifies the name of the MCAC interface policy, up to 32 characters.

Platforms

All

ifdv-avg

ifdv-avg

Syntax

[no] ifdv-avg {forward | backward | round-trip}

Context

[Tree] (config>oam-pm>streaming>delay-template ifdv-avg)

Full Context

configure oam-pm streaming delay-template ifdv-avg

Description

This command specifies the sending of average inter-frame delay variation for a specified direction.

The no form of this command deletes the specified average direction.

Note:

All directions can be specified if all directions are important for reporting. However, only enable those directions that are required.

Parameters

forward

Specifies the measurement in the forward direction.

backward

Specifies the measurement in the backward direction.

round-trip

Specifies the measurement for the round trip.

Platforms

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

iff-attribute-uniform-propagation

iff-attribute-uniform-propagation

Syntax

[no] iff-attribute-uniform-propagation

Context

[Tree] (config>service>system>bgp-evpn>ip-prefix-routes iff-attribute-uniform-propagation)

Full Context

configure service system bgp-evpn ip-prefix-routes iff-attribute-uniform-propagation

Description

This command enables the uniform propagation of BGP attributes for EVPN Interface-ful (EVPN-IFF) routes. EVPN-IFF is used in R-VPLS services with bgp-evpn>ip-route-advertisement. When enabled, the received EVPN-IFF routes for the R-VPLS can be propagated with the original BGP path attributes into EVPN-IFL, IPVPN, EVPN-IFF (in other R-VPLS services), or BGP IP routes advertised for the attached VPRN. This command also enables the attribute propagation in the opposite direction; for example, from EVPN-IFL, IPVPN, IP, or EVPN-IFF routes into EVPN-IFF routes.

The propagation is in accordance with the uniform mode defined in draft-ietf-bess-evpn-ipvpn-interworking.

The no form of this command re-originates the BGP path attributes when propagating EVPN-IFF routes into other inter-subnet forwarding families.

Default

no iff-attribute-uniform-propagation

Platforms

All

iff-bgp-path-selection

iff-bgp-path-selection

Syntax

iff-bgp-path-selection [d-path-length-ignore]

no iff-bgp-path-selection

Context

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

Full Context

configure service system bgp-evpn ip-prefix-routes iff-bgp-path-selection

Description

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

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

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

Default

no iff-bgp-path-selection

Parameters

d-path-length-ignore

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

Platforms

All

igmp

igmp

Syntax

[no] igmp [host ip-address] [ group grp-address]

Context

[Tree] (debug>mcast-mgmt>mcast-rprt-dest igmp)

Full Context

debug mcast-management mcast-reporting-dest igmp

Description

This command sets mcast reporting dest debug filtering options and applies only to the 7750 SR.

Platforms

All

igmp

Syntax

[no] igmp

Context

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

Full Context

configure redundancy multi-chassis peer sync igmp

Description

This command specifies whether IGMP protocol information should be synchronized with the multi-chassis peer.

Default

no igmp

Platforms

All

igmp

Syntax

[no] igmp

Context

[Tree] (config>service>vprn igmp)

Full Context

configure service vprn igmp

Description

Commands in this context configure IGMP parameters.

The no form of this command disables IGMP.

Default

no igmp

Platforms

All

igmp

Syntax

[no] igmp

Context

[Tree] (config>router igmp)

Full Context

configure router igmp

Description

This command enables the Internet Group Management Protocol (IGMP) context. When the context is created, the IGMP protocol is enabled.

The Internet Group Management Protocol (IGMP) is used by IPv4 systems (hosts and routers) to report their IP multicast group memberships to neighboring multicast routers. An IP multicast router can be a member of one or more multicast groups, in which case it performs both the "multicast router part” of the protocol which collects the membership information needed by its multicast routing protocol, and the "group member part” of the protocol which informs itself and other neighboring multicast routers of its memberships.

The no form of the command disables the IGMP instance. To start or suspend execution of IGMP without affecting the configuration, use the no shutdown command.

Platforms

All

igmp

Syntax

[no] igmp

Context

[Tree] (config>sys>security>cpu-protection>ip>included-protocols igmp)

Full Context

configure system security cpu-protection ip-src-monitoring included-protocols igmp

Description

This command includes the extracted IPv4 IGMP packets for ip-src-monitoring. IPv4 IGMP packets will be subject to the per-source-rate of CPU protection policies.

Default

no igmp

Platforms

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

igmp-host-tracking

igmp-host-tracking

Syntax

igmp-host-tracking

Context

[Tree] (config>subscr-mgmt>msap-policy igmp-host-tracking)

Full Context

configure subscriber-mgmt msap-policy igmp-host-tracking

Description

Commands in this context configure IGMP host tracking parameters.

Platforms

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

igmp-host-tracking

Syntax

igmp-host-tracking

Context

[Tree] (config>service>vprn>sub-if>grp-if>sap igmp-host-tracking)

Full Context

configure service vprn subscriber-interface group-interface sap igmp-host-tracking

Description

Commands in this context configure IGMP host tracking parameters.

Platforms

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

igmp-host-tracking

Syntax

igmp-host-tracking

Context

[Tree] (config>service>vpls>sap igmp-host-tracking)

[Tree] (config>service>vpls igmp-host-tracking)

Full Context

configure service vpls sap igmp-host-tracking

configure service vpls igmp-host-tracking

Description

Commands in this context configure IGMP host tracking parameters.

Platforms

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

igmp-host-tracking

Syntax

igmp-host-tracking

Context

[Tree] (config>service>ies igmp-host-tracking)

[Tree] (config>service>ies>sub-if>grp-if>sap igmp-host-tracking)

Full Context

configure service ies igmp-host-tracking

configure service ies subscriber-interface group-interface sap igmp-host-tracking

Description

Commands in this context configure IGMP host tracking parameters.

Platforms

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

igmp-host-tracking

Syntax

igmp-host-tracking

Context

[Tree] (config>service>vprn>sap igmp-host-tracking)

[Tree] (config>service>vprn igmp-host-tracking)

Full Context

configure service vprn sap igmp-host-tracking

configure service vprn igmp-host-tracking

Description

Commands in this context configure IGMP host tracking parameters.

Platforms

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

igmp-policy

igmp-policy

Syntax

igmp-policy policy-name [create]

no igmp-policy

Context

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

Full Context

configure subscriber-mgmt igmp-policy

Description

This command configures an IGMP policy.

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

Parameters

policy-name

Specifies the policy name up to 32 characters.

create

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

Platforms

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

igmp-policy

Syntax

igmp-policy policy-name

no igmp-policy

Context

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

Full Context

configure subscriber-mgmt sub-profile igmp-policy

Description

This command will enable IGMP processing per subscriber host. Without this command IGMP states will not be maintained per subscriber hosts. The referenced policy is defined under the configure>subscr-mgmt context and can be only applied via the sub-profile.

The referenced policy contains entries such as:

  • description statement

  • import statement — IGMP filters

  • egress-rate-modify statement—HQoS Adjustment

  • mcast-redirection statement—redirection to alternate interface

  • static statement—definition of static IGMP groups

  • version statement —IGMP version

  • fast-leave statement

  • max-num-groups statement—the maximum number of multicast groups allowed

The no form of this command reverts to the default.

Parameters

policy-name

Specifies the name of the IGMP policy for the subscriber. The policy itself is defined under the configure>sub-mgmt context.

Platforms

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

igmp-snooping

igmp-snooping

Syntax

igmp-snooping

Context

[Tree] (config>service>vpls>allow-ip-int-bind igmp-snooping)

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

[Tree] (config>service>vpls igmp-snooping)

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

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

Full Context

configure service vpls allow-ip-int-bind igmp-snooping

configure service vpls spoke-sdp igmp-snooping

configure service vpls igmp-snooping

configure service vpls sap igmp-snooping

configure service vpls mesh-sdp igmp-snooping

Description

This command enables the Internet Group Management Protocol (IGMP) snooping context.

Platforms

All

igmp-snooping

Syntax

igmp-snooping

Context

[Tree] (config>subscr-mgmt>msap-policy>vpls-only igmp-snooping)

Full Context

configure subscriber-mgmt msap-policy vpls-only-sap-parameters igmp-snooping

Description

Commands in this context configure Internet Group Management Protocol (IGMP) snooping parameters.

Platforms

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

igmp-snooping

Syntax

[no] igmp-snooping

Context

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

Full Context

configure redundancy multi-chassis peer sync igmp-snooping

Description

This command specifies whether IGMP snooping information should be synchronized with the multi-chassis peer.

Default

no igmp-snooping

Platforms

All

igmp-snooping

Syntax

igmp-snooping

Context

[Tree] (config>service>vpls>vxlan igmp-snooping)

Full Context

configure service vpls vxlan igmp-snooping

Description

This command enables the Internet Group Management Protocol (IGMP) snooping context.

Platforms

All

igmp-snooping

Syntax

igmp-snooping

Context

[Tree] (config>service>vpls>pbb>bvpls>sap igmp-snooping)

[Tree] (config>service>vpls>pbb>bvpls>sdp igmp-snooping)

[Tree] (config>service>vpls>pbb>bvpls igmp-snooping)

Full Context

configure service vpls pbb backbone-vpls sap igmp-snooping

configure service vpls pbb backbone-vpls sdp igmp-snooping

configure service vpls pbb backbone-vpls igmp-snooping

Description

This command configures IGMP snooping attributes for I-VPLS.

Platforms

All

igmp-snooping

Syntax

[no] igmp-snooping

Context

[Tree] (debug>service>id igmp-snooping)

Full Context

debug service id igmp-snooping

Description

This command enables and configures IGMP-snooping debugging.

Platforms

All

igmp-snooping

Syntax

igmp-snooping

Context

[Tree] (config>service>pw-template igmp-snooping)

Full Context

configure service pw-template igmp-snooping

Description

This command enables the Internet Group Management Protocol (IGMP) snooping context.

Platforms

All

ignore-app-profile

ignore-app-profile

Syntax

ignore-app-profile

no ignore-app-profile

Context

[Tree] (config>subscr-mgmt>http-redirect-policy ignore-app-profile)

Full Context

configure subscriber-mgmt http-redirect-policy ignore-app-profile

Description

When enabled, the Alc-App-Prof-Str VSA is ignored in a RADIUS Accept that enables portal redirection using this redirect policy. AA functionality is disabled during portal authentication.

The no form of this command allows an Alc-App-Prof-Str to be present and enables Application Assurance during portal authentication. In this case redirection rules defined in this policy are bypassed and it is assumed the AA function is configured for portal redirection.

Default

no ignore-app-profile

Platforms

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

ignore-attached-bit

ignore-attached-bit

Syntax

ignore-attached-bit

no ignore-attached-bit

Context

[Tree] (config>service>vprn>isis ignore-attached-bit)

Full Context

configure service vprn isis ignore-attached-bit

Description

This command configures IS-IS to ignore the attached bit on received Level 1 LSPs to disable installation of default routes.

Platforms

All

ignore-attached-bit

Syntax

ignore-attached-bit

[no] ignore-attached-bit

Context

[Tree] (config>router>isis ignore-attached-bit)

Full Context

configure router isis ignore-attached-bit

Description

This command configures IS-IS to ignore the attached bit on received Level 1 LSPs to disable installation of default routes.

Platforms

All

ignore-avps

ignore-avps

Syntax

ignore-avps [sequencing-required]

no ignore-avps

Context

[Tree] (config>service>vprn>l2tp ignore-avps)

[Tree] (config>router>l2tp ignore-avps)

Full Context

configure service vprn l2tp ignore-avps

configure router l2tp ignore-avps

Description

This command specifies the L2TP AVPs that should be ignored in L2TP session control.

The no form of this command reverts to the default.

Parameters

sequencing-required

Ignores the [39] Sequencing Required AVP on LNS when present in the L2TP ICCN message received from LAC. By default, the session at LNS would be disconnected, in this case with the Call Disconnect Notify (CDN) error code unknownMandatoryReceive(8). Note that when configured, to ignore the Sequencing Required AVP there is no Sequence Numbers inserted into the data channel.

Platforms

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

ignore-default

ignore-default

Syntax

[no] ignore-default

Context

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

[Tree] (config>service>ies>if>ipv6 ignore-default)

[Tree] (config>service>ies>sub-if>grp-if>ipv6 ignore-default)

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

[Tree] (config>service>ies>if ignore-default)

Full Context

configure service vprn subscriber-interface group-interface ignore-default

configure service ies interface ipv6 ignore-default

configure service ies subscriber-interface group-interface ipv6 ignore-default

configure service ies subscriber-interface group-interface ignore-default

configure service ies interface ignore-default

Description

This command enables the default route when performing a uRPF check.

The no form of this command disables the default route.

Platforms

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

  • configure service vprn subscriber-interface group-interface ignore-default
  • configure service ies subscriber-interface group-interface ignore-default
  • configure service ies subscriber-interface group-interface ipv6 ignore-default

All

  • configure service ies interface ignore-default
  • configure service ies interface ipv6 ignore-default

ignore-default

Syntax

[no] ignore-default

Context

[Tree] (config>router>if>ipv6>urpf-check ignore-default)

[Tree] (config>router>if>urpf-check ignore-default)

Full Context

configure router interface ipv6 urpf-check ignore-default

configure router interface urpf-check ignore-default

Description

This command configures the uRPF check (if enabled) to ignore default routes for purposes of determining the validity of incoming packets. By default, default routes are considered eligible.

Platforms

All

ignore-df-bit

ignore-df-bit

Syntax

[no] ignore-df-bit

Context

[Tree] (config>subscr-mgmt>loc-user-db>ppp>host ignore-df-bit)

Full Context

configure subscriber-mgmt local-user-db ppp host ignore-df-bit

Description

When this command is enabled for a subscriber host, the do-not-fragment (DF) bit in the IPv4 header for frames egressing the subscriber interface is ignored, the frames are fragmented according the applicable egress MTU. The DF bit is reset for frames that are fragmented.

This command applies to PPPoE PTA and L2TP LNS frames only. It is not applicable for L2TP LAC frames.

Platforms

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

ignore-df-bit

Syntax

[no] ignore-df-bit

Context

[Tree] (config>service>vprn>sub-if>grp-if ignore-df-bit)

[Tree] (config>service>ies>sub-if>grp-if ignore-df-bit)

Full Context

configure service vprn subscriber-interface group-interface ignore-df-bit

configure service ies subscriber-interface group-interface ignore-df-bit

Description

This command enables the ignore-df-bit flag that ignores the do-not-fragment (DF) bit for frames egressing the WLAN-GW group interface and fragments the frame according to the applicable egress MTU. The DF bit is reset for the frames that are fragmented.

The no form of this command causes the router to fragment a packet larger than the MTU if the DF bit is set to 0 and drops the packet if the DF bit is set to 1.

Default

no ignore-df-bit

Platforms

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

ignore-dn-bit

ignore-dn-bit

Syntax

[no] ignore-dn-bit

Context

[Tree] (config>service>vprn>ospf3 ignore-dn-bit)

[Tree] (config>service>vprn>ospf ignore-dn-bit)

Full Context

configure service vprn ospf3 ignore-dn-bit

configure service vprn ospf ignore-dn-bit

Description

This command specifies whether to ignore the DN bit for OSPF LSA packets for this instance of OSPF on the router. When enabled, the DN bit for OSPF LSA packets are ignored.

The no form of this command does not ignore the DN bit for OSPF LSA packets.

Default

no ignore-dn-bit

Platforms

All

ignore-efm-state

ignore-efm-state

Syntax

[no] ignore-efm-state

Context

[Tree] (config>port>ethernet>efm-oam ignore-efm-state)

Full Context

configure port ethernet efm-oam ignore-efm-state

Description

When the ignore-efm-state command is configured, any failure in the protocol state machine (discovery, configuration, timeout, loops, and so on) does not impact the state of the port. There is only be a protocol warning message on the port. If this optional command is not configured, the port state is affected by any existing EFM-OAM protocol fault condition.

Default

no ignore-efm-state

Platforms

All

ignore-l2vpn-mtu-mismatch

ignore-l2vpn-mtu-mismatch

Syntax

ignore-l2vpn-mtu-mismatch

no ignore-l2vpn-mtu-mismatch

Context

[Tree] (config>service>epipe ignore-l2vpn-mtu-mismatch)

Full Context

configure service epipe ignore-l2vpn-mtu-mismatch

Description

This command enables the router to bring up a BGP-VPWS service regardless of any MTU mismatch. The router does not check the value of the Layer 2 MTU in the Layer2 Info Extended Community received in a BGP update message against the local service MTU or locally signaled MTU.

The no form of this command disables the functionality. When this command is disabled, the router does not bring up a BGP-VPWS service if an MTU mismatch occurs.

Default

no ignore-l2vpn-mtu-mismatch

Platforms

All

ignore-l2vpn-mtu-mismatch

Syntax

ignore-l2vpn-mtu-mismatch

no ignore-l2vpn-mtu-mismatch

Context

[Tree] (config>service>vpls ignore-l2vpn-mtu-mismatch)

Full Context

configure service vpls ignore-l2vpn-mtu-mismatch

Description

This command enables the router to bring up a BGP-VPLS service regardless of any MTU mismatch. The router does not check the value of the Layer 2 MTU in the Layer2 Info Extended Community received in a BGP update message against the local service MTU or locally signaled MTU.

The no form of this command disables the functionality. When this command is disabled, the router does not bring up a BGP-VPLS service if an MTU mismatch occurs.

Default

no ignore-l2vpn-mtu-mismatch

Platforms

All

ignore-lsp-errors

ignore-lsp-errors

Syntax

[no] ignore-lsp-errors

Context

[Tree] (config>service>vprn>isis ignore-lsp-errors)

[Tree] (config>router>isis ignore-lsp-errors)

Full Context

configure service vprn isis ignore-lsp-errors

configure router isis ignore-lsp-errors

Description

This command specifies that for this VPRN instance, ISIS will ignore LSP packets with errors. When enabled, IS-IS LSP errors will be ignored and the associated record will not be purged.

This command enables ISIS to ignore the ATT bit and therefore suppress the installation of default routes.

The no form of this command specifies that ISIS will not ignore LSP errors.

Platforms

All

ignore-match

ignore-match

Syntax

ignore-match

Context

[Tree] (config>filter>ipv6-filter>entry>action ignore-match)

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

[Tree] (config>filter>ip-filter>entry>action ignore-match)

Full Context

configure filter ipv6-filter entry action ignore-match

configure filter mac-filter entry action ignore-match

configure filter ip-filter entry action ignore-match

Description

This command sets the filter entry action to ignore-match, as a result this filter entry is ignored and not programmed in hardware.

Platforms

All

ignore-mclt-on-takeover

ignore-mclt-on-takeover

Syntax

[no] ignore-mclt-on-takeover

Context

[Tree] (config>service>vprn>dhcp>server>pool>failover ignore-mclt-on-takeover)

[Tree] (config>router>dhcp>server>pool>failover ignore-mclt-on-takeover)

[Tree] (config>router>dhcp6>server>pool>failover ignore-mclt-on-takeover)

[Tree] (config>router>dhcp6>server>failover ignore-mclt-on-takeover)

[Tree] (config>service>vprn>dhcp6>server>failover ignore-mclt-on-takeover)

[Tree] (config>router>dhcp>server>failover ignore-mclt-on-takeover)

[Tree] (config>service>vprn>dhcp>server>failover ignore-mclt-on-takeover)

[Tree] (config>service>vprn>dhcp6>server>pool>failover ignore-mclt-on-takeover)

Full Context

configure service vprn dhcp local-dhcp-server pool failover ignore-mclt-on-takeover

configure router dhcp server pool failover ignore-mclt-on-takeover

configure router dhcp6 server pool failover ignore-mclt-on-takeover

configure router dhcp6 local-dhcp-server failover ignore-mclt-on-takeover

configure service vprn dhcp6 local-dhcp-server failover ignore-mclt-on-takeover

configure router dhcp local-dhcp-server failover ignore-mclt-on-takeover

configure service vprn dhcp local-dhcp-server failover ignore-mclt-on-takeover

configure service vprn dhcp6 local-dhcp-server pool failover ignore-mclt-on-takeover

Description

With this flag enabled, the remote IP address or prefix can be taken over immediately upon entering the PARTNER-DOWN state of the intercommunication link, without having to wait for the Maximum Client Lead Time (MCLT) to expire. By setting this flag, the lease times of the existing DHCP clients, while the intercommunication link is in the PARTNER-DOWN state, will still be reduced to the MCLT over time and all new lease times are set to MCLT. This behavior remains the same as originally intended for MCLT.

Some deployments require that the remote IP address/prefix range starts delegating new IP addresses and prefixes upon the failure of the intercommunication link, without waiting for the intercommunication link to transition from the COMM-INT state into the PARTNER-DOWN state and the MCLT to expire while in PARTNER-DOWN state.

This can be achieved by enabling the ignore-mclt-on-takeover flag and by configuring the partner-down-delay to 0.

Enabling this functionality must be exercised with caution. One needs to keep in mind that the partner-down-delay and MCLT timers were originally introduced to prevent IP address duplication in cases where DHCP redundant nodes transition out-of-sync due to the failure of intercommunication link. These timers ( partner-down-delay and MCLT) would ensure that during their duration, the new IP addresses and prefixes are delegated only from one node, the one with local IP address-range/prefix. This causes the new IP address delegation to be delayed and the service is impacted.

If it can be assured that the intercommunication link is always available, then the DHCP nodes would stay in sync and the two timers would not be needed. Therefore, it is important that in this mode of operation, the intercommunication link is well protected by providing multiple paths between the two DHCP nodes. The only event that should cause intercommunication link to fail is the entire nodal failure. This failure is acceptable since in this case only one DHCP node is available to provide new IP addresses and prefixes.

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

ignore-mtu-mismatch

ignore-mtu-mismatch

Syntax

[no] ignore-mtu-mismatch

Context

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

Full Context

configure service vpls bgp-evpn ignore-mtu-mismatch

Description

This command enables the system to ignore the received Layer-2 MTU in the L2 Attributes extended community of the IMET route for a peer.

The no form of this command configures the system to compare the local service MTU against the received Layer 2 MTU and if there is a mismatch, keep the EVPN destination to the peer with operational state down.

Default

no ignore-mtu-mismtach

Platforms

All

ignore-narrow-metric

ignore-narrow-metric

Syntax

[no] ignore-narrow-metric

Context

[Tree] (config>service>vprn>isis ignore-narrow-metric)

Full Context

configure service vprn isis ignore-narrow-metric

Description

This command specifies that IS-IS ignores links with narrow metrics when wide-metrics support has been enabled.

The no form of this command specifies that IS-IS does not ignore these links.

Platforms

All

ignore-narrow-metric

Syntax

[no] ignore-narrow-metric

Context

[Tree] (config>router>isis ignore-narrow-metric)

Full Context

configure router isis ignore-narrow-metric

Description

This command specifies that IS-IS will ignore links with narrow metrics when wide-metrics support has been enabled.

The no form of this command specifies that IS-IS will not ignore these links.

Platforms

All

ignore-nh-metric

ignore-nh-metric

Syntax

[no] ignore-nh-metric

Context

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

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

[Tree] (config>service>vprn ignore-nh-metric)

Full Context

configure service vprn bgp best-path-selection ignore-nh-metric

configure router bgp best-path-selection ignore-nh-metric

configure service vprn ignore-nh-metric

Description

This command instructs BGP to disregard the resolved distance to the BGP next-hop in its decision process for selecting the best route to a destination. When configured in the config>router>bgp>best-path-selection context, this command applies to the comparison of two BGP routes with the same NLRI learned from base router BGP peers. When configured in the config>service>vprn context, this command applies to the comparison of two BGP-VPN routes for the same IP prefix imported into the VPRN from the base router BGP instance. When configured in the config>service>vprn>bgp>best-path-selection context, this command applies to the comparison of two BGP routes for the same IP prefix learned from VPRN BGP peers.

The no form of this command (no ignore-nh-metric) restores the default behavior whereby BGP factors distance to the next-hop into its decision process.

Default

no ignore-nh-metric

Platforms

All

ignore-oper-down

ignore-oper-down

Syntax

[no] ignore-oper-down

Context

[Tree] (config>service>epipe>sap ignore-oper-down)

Full Context

configure service epipe sap ignore-oper-down

Description

This command enables the ability to ignore the operationally down status for service oper state calculation. An Epipe service does not transition to Oper State: Down when a SAP fails and when this optional command is configured under that specific SAP. Only a single SAP in an Epipe may have this optional command included. The command can be used in Epipes with or without EVPN enabled.

The no form of this command disables whether a service ignores the operationally down state of the SAP.

Default

no ignore-oper-down

Platforms

All

ignore-rapid-commit

ignore-rapid-commit

Syntax

[no] ignore-rapid-commit

Context

[Tree] (config>service>vprn>dhcp6>server ignore-rapid-commit)

[Tree] (config>router>dhcp6>server ignore-rapid-commit)

Full Context

configure service vprn dhcp6 local-dhcp-server ignore-rapid-commit

configure router dhcp6 local-dhcp-server ignore-rapid-commit

Description

This command enables the Rapid Commit Option for DHCP6.

The no form of this command disables the Rapid Commit Option.

Platforms

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

ignore-received-srv6-tlvs

ignore-received-srv6-tlvs

Syntax

[no] ignore-received-srv6-tlvs

Context

[Tree] (config>router>bgp>srv6>family ignore-received-srv6-tlvs)

Full Context

configure router bgp segment-routing-v6 family ignore-received-srv6-tlvs

Description

This command specifies that SRv6 TLVs are ignored when present in received routes of the associated family. In this case the route resolution is only based on the BGP next hop.

The no form of this command specifies that the SRv6 TLV is processed when a route of the family is received with a prefix SID attribute carrying an SRv6 TLV. In this case, a route is resolved only if both its BGP next hop and the locator prefix are reachable. The datapath programming and IGP cost to reach the next hop (used by the BGP decision process) is based on the route to the locator prefix.

Default

ignore-received-srv6-tlvs

Platforms

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

ignore-router-id

ignore-router-id

Syntax

ignore-router-id include-internal family [ family]

[no] ignore-router-id

Context

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

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

Full Context

configure router bgp best-path-selection ignore-router-id

configure service vprn bgp best-path-selection ignore-router-id

Description

When the ignore-router-id command is present, and the current best path to a destination was learned from EBGP peer X with BGP identifier x and a new path is received from EBGP peer Y with BGP identifier y, the best path remains unchanged if the new path is equivalent to the current best path up to the BGP identifier comparison – even if y is less than x.

The no form of this command restores the default behavior of selecting the route with the lowest BGP identifier (y) as best.

Default

no ignore-router-id

Parameters

family

Specifies up to two internal families to be included in this configuration.

Values

mvpn-ipv4, mvpn-ipv6

include-internal

Specifies to ignore the router ID value even when comparing two IGBP paths or an EBGP and an IBGP path.

Platforms

All

ignore-standby-signaling

ignore-standby-signaling

Syntax

[no] ignore-standby-signaling

Context

[Tree] (config>service>vpls>spoke-sdp ignore-standby-signaling)

[Tree] (config>service>vpls>endpoint ignore-standby-signaling)

Full Context

configure service vpls spoke-sdp ignore-standby-signaling

configure service vpls endpoint ignore-standby-signaling

Description

When this command is enabled, the node ignores the standby-bit received from the TLDP peers for the specific spoke-SDP and performs internal tasks without taking it into account.

This command is present at the endpoint level and the spoke-SDP level. If the spoke-SDP is part of the explicit-endpoint, this setting cannot be changed at the spoke-SDP level. The existing spoke-SDP will become part of the explicit-endpoint only if the setting is not conflicting. The newly created spoke-SDP, which is a part of the specified explicit-endpoint, will inherit this setting from the endpoint configuration.

Default

no ignore-standby-signaling

Platforms

All

ignore-tos

ignore-tos

Syntax

[no] ignore-tos

Context

[Tree] (config>service>vprn>inside>nat64 ignore-tos)

Full Context

configure service vprn inside nat64 ignore-tos

Description

This command specifies if the IPv4 Type-of-Service (ToS) is ignored and the IPv6 traffic class bits set to zero.

If this command is disabled, the system copies the IPv4 ToS into the IPv6 traffic class.

Default

disabled

ignore-tos

Syntax

[no] ignore-tos

Context

[Tree] (config>service>vprn>nat>inside>nat64 ignore-tos)

[Tree] (config>router>nat>inside>nat64 ignore-tos)

Full Context

configure service vprn nat inside nat64 ignore-tos

configure router nat inside nat64 ignore-tos

Description

This command specifies whether the IPv4 ToS is ignored and the IPv6 traffic class bits set to zero.

When disabled, the system copies the IPv4 ToS into the IPv6 traffic class.

The no form of the command recognizes the IPv4 ToS.

Default

disabled

Platforms

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

igp-instance

igp-instance

Syntax

igp-instance igp-instance

Context

[Tree] (config>oam-pm>session>ip>tunnel>mpls>sr-ospf3 igp-instance)

[Tree] (config>oam-pm>session>ip>tunnel>mpls>sr-ospf igp-instance)

[Tree] (config>oam-pm>session>ip>tunnel>mpls>sr-isis igp-instance)

Full Context

configure oam-pm session ip tunnel mpls sr-ospf3 igp-instance

configure oam-pm session ip tunnel mpls sr-ospf igp-instance

configure oam-pm session ip tunnel mpls sr-isis igp-instance

Description

This command configures the IGP instance to tunnel IP packets for the session test.

Default

igp-instance 0

Parameters

igp-instance

Specifies the IGP instance used to tunnel packets for the session.

Values

isis-inst

0 to 127

ospf-inst

0 to 31

ospf3-inst

0 to 31,64 to 95

Platforms

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

igp-shortcut

igp-shortcut

Syntax

igp-shortcut [lfa-protect | lfa-only] [allow-sr-over-srte]

igp-shortcut relative-metric [offset] [allow-sr-over-srte]

no igp-shortcut

Context

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

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

Full Context

configure router mpls lsp-template igp-shortcut

configure router mpls lsp igp-shortcut

Description

This command enables the use of a specific RSVP LSP by IS-IS and OSPF routing protocols as a shortcut or as a forwarding adjacency for resolving IGP routes.

When the igp-shortcut or the advertise-tunnel-link option is enabled at the IGP instance level, all RSVP LSPs originating on this node are eligible by default as long as the destination address of the LSP, as configured in config>router>mpls>lsp>to, corresponds to a router-id of a remote node.

The lfa-protect option allows an LSP to be included in both the main SPF and the Loop-Free Alternate (LFA) SPF. For a given prefix, the LSP can be used either as a primary next-hop or as an LFA next-hop, but not both. If the main SPF computation selected a tunneled primary next-hop for a prefix, the LFA SPF will not select an LFA next-hop for this prefix and the protection of this prefix will rely on the RSVP LSP FRR protection. If the main SPF computation selected a direct primary next-hop, then the LFA SPF will select an LFA next-hop for this prefix but will prefer a direct LFA next-hop over a tunneled LFA next-hop.

The lfa-only option allows an LSP to be included in the LFA SPF only such that the introduction of IGP shortcuts does not impact the main SPF decision. For a given prefix, the main SPF always selects a direct primary next-hop. The LFA SPF selects an LFA next-hop for this prefix but will prefer a direct LFA next-hop over a tunneled LFA next-hop.

When the relative-metric option is enabled, IGP will apply the shortest IGP cost between the endpoints of the LSP plus the value of the offset (instead of the LSP operational metric) when computing the cost of a prefix which is resolved to the LSP. The offset value is optional and it defaults to zero. The minimum net cost for a prefix is one (1) after applying the offset. The TTM continues the show the LSP operational metric as provided by MPLS. In other words, applications such as LDP-over-RSVP (when IGP shortcut is disabled) and BGP and static route shortcuts will continue to use the LSP operational metric.

The relative-metric option is mutually exclusive with the lfa-protect or the lfa-only options. In other words, an LSP with the relative-metric option enabled cannot be included in the LFA SPF, and vice-versa, when the igp-shortcut option is enabled in the IGP.

Finally, the relative-metric option is ignored when forwarding adjacency is enabled in IS-IS or OSPF. In this case, IGP advertises the LSP as a point-to-point unnumbered link along with the LSP operational metric as returned by MPLS and capped to maximum link metric allowed in that IGP. Both the main SPF and the LFA SPFs will use the local IGP database to resolve the routes.

When the router performs local SPF, the SR-TE LSP is used as an eligible IGP shortcut for SRv4 or SRv6 only if the LSP is explicitly allowed using the allow-sr-over-srte option when the top SID in the SR-TE LSP is an adjacency SID.

The no form of this command disables the use of a specific RSVP LSP by IS-IS and OSPF routing protocols as a shortcut or a forwarding adjacency for resolving IGP routes.

Default

igp-shortcut. All RSVP LSPs originating on this node are eligible by default as long as the destination address of the LSP corresponds to a router-id of a remote node.

Parameters

lfa-protect

Specifies an LSP is included in both the main SPF and the LFA SPF.

lfa-only

Specifies an LSP is included in the LFA SPF only.

relative-metric [offset]

Specifies the shortest IGP cost between the endpoints of the LSP plus the configured offset, instead of the LSP operational metric returned by MPLS, is used when calculating the cost of prefix resolved to this LSP. The offset parameter is an integer and is optional. An offset value of zero is used when the relative-metric option is enabled without specifying the offset parameter value.

Values

[-10, +10]

allow-sr-over-srte

Specifies that the LSP or LSP template is eligible as an IGP shortcut.

Platforms

All

igp-shortcut

Syntax

igp-shortcut

Context

[Tree] (config>router>isis igp-shortcut)

Full Context

configure router isis igp-shortcut

Description

This command enables the use of an RSVP-TE or SR-TE shortcut for resolving IGP routes by OSPF or IS-IS routing protocols.

This command instructs IGP to include RSVP LSPs and SR-TE LSPs originating on this node and terminating on the router ID of a remote node as direct links with a metric equal to the metric provided by MPLS.

During the IP reach calculation to determine the reachability of nodes and prefixes, LSPs are overlaid and the LSP metric is used to determine the subset of paths that are equal lowest cost to reach a node or a prefix. If the user enabled the relative-metric option for this LSP, IGP will apply the shortest IGP cost between the endpoints of the LSP plus the value of the offset, instead of the LSP operational metric, when computing the cost of a prefix that is resolved to the LSP.

When a prefix is resolved to a tunnel next-hop, the packet is sent labeled with the label stack corresponding to the NHLFE of the RSVP-TE or SR-TE LSP, as well as the explicit-null IPv6 label at the bottom of the stack in the case of an IPv6 prefix. Any network event causing one or more IGP shortcuts to go down will trigger a full SPF computation, which may result in installing a new route over an updated set of tunnel next-hops and IP next-hops.

When igp-shortcut is enabled at the IGP instance level, all RSVP-TE and SR-TE LSPs originating on this node are eligible by default as long as the destination address of the LSP, as configured in config>router>mpls>lsp>to, corresponds to a router ID of a remote node. LSPs with a destination corresponding to an interface address or any other loopback interface address of a remote node are automatically not considered by IGP. The user can, however, exclude a specific RSVP-TE or SR-TE LSP from being used as a shortcut for resolving IGP routes by entering the config>router>mpls>lsp>no igp-shortcut command.

The SPF in IGP only uses RSVP LSPs as forwarding adjacencies, IGP shortcuts, or as endpoints for LDP-over-RSVP. These applications of RSVP LSPs are mutually exclusive at the IGP instance level. If two or more options are enabled in the same IGP instance, then forwarding adjacency takes precedence over the shortcut application, which takes precedence over the LDP-over-RSVP application.

The SPF in IGP uses SR-TE LSPs as IGP shortcuts only.

When ECMP is enabled on the system and multiple equal-cost paths exist for a prefix, the following selection criteria are used to pick up the set of tunnel and IP next-hops to program in the data path.

  • Where a destination is a tunnel-endpoint (including external prefixes with tunnel-endpoint as the next-hop), the tunnel with lowest tunnel-index is selected (the IP next-hop is never used in this case).

  • Where a destination is not a tunnel-endpoint:

    • LSPs with metric higher than underlying IGP cost between the endpoint of the LSP are excluded

    • Tunnel next-hops are preferred over IP next-hops

    • Within tunnel next-hops, the following priority applies to selection:

      1. The lowest endpoint-to-destination cost is selected

      2. If the endpoint-to-destination costs are the same, the lowest endpoint node router ID is selected

      3. If the router IDs are the same, the lowest tunnel index is selected

    • Within IP next-hops, the following priority applies to selection:

      1. The lowest downstream router ID is selected

      2. If the downstream router IDs are the same, the lowest interface-index is selected

Note:

Although ECMP is not performed across both the IP and tunnel next-hops, the tunnel endpoint may lie in one of the shortest IGP paths for that prefix. In that case, the tunnel next-hop is always selected as long as the prefix cost using the tunnel is equal to or lower than the IGP cost.

When both RSVP-TE and SR-TE IGP shortcuts are available, the IP reach calculation, in the unicast routing table, will first follow the above ECMP tunnel and IP next-hop selection rules when resolving a prefix over IGP shortcuts. After the set of ECMP tunnel and IP next-hops have been selected, the preference of tunnel type is then applied based on the user setting for prefix family resolution. If the user enabled resolution of the prefix family to both RSVP-TE and SR-TE tunnel types, the TTM tunnel preference value is used to select one type for the prefix. In other words, an RSVP-TE LSP type is preferred to an SR-TE LSP type on a per-prefix basis.

The ingress IOM sprays the packets for this prefix over the set of tunnel next-hops and IP next-hops based on the hashing routine currently supported for IPv4 packets.

This feature provides IGP with the capability to populate the multicast RTM with the prefix IP next-hop when both the igp-shortcut and the multicast-import options are enabled in IGP. The unicast RTM can still use the tunnel next-hop for the same prefix. The SPF keeps track of both the direct first hop and the tunneled first hop of a node, which is added to the Dijkstra tree.

Platforms

All

igp-shortcut

Syntax

igp-shortcut

Context

[Tree] (config>router>ospf3 igp-shortcut)

[Tree] (config>router>ospf igp-shortcut)

Full Context

configure router ospf3 igp-shortcut

configure router ospf igp-shortcut

Description

This command enables the use of an RSVP-TE or SR-TE shortcut for resolving IGP routes by OSPF or IS-IS routing protocols.

This command instructs IGP to include RSVP LSPs and SR-TE LSPs originating on this node and terminating on the router ID of a remote node as direct links with a metric equal to the metric provided by MPLS.

During the IP reach calculation to determine the reachability of nodes and prefixes, LSPs are overlaid and the LSP metric is used to determine the subset of paths that are equal lowest cost to reach a node or a prefix. If the user enabled the relative-metric option for this LSP, IGP will apply the shortest IGP cost between the endpoints of the LSP plus the value of the offset, instead of the LSP operational metric, when computing the cost of a prefix that is resolved to the LSP.

When a prefix is resolved to a tunnel next hop, the packet is sent labeled with the label stack corresponding to the NHLFE of the RSVP-TE or SR-TE LSP, as well as the explicit-null IPv6 label at the bottom of the stack in the case of an IPv6 prefix. Any network event causing one or more IGP shortcuts to go down will trigger a full SPF computation, which may result in installing a new route over an updated set of tunnel next-hops and IP next-hops.

When igp-shortcut is enabled at the IGP instance level, all RSVP-TE and SR-TE LSPs originating on this node are eligible by default as long as the destination address of the LSP, as configured in config>router>mpls>lsp>to, corresponds to a router ID of a remote node. LSPs with a destination corresponding to an interface address or any other loopback interface address of a remote node are automatically not considered by IGP. The user can, however, exclude a specific RSVP-TE or SR-TE LSP from being used as a shortcut for resolving IGP routes by entering the config>router>mpls>lsp>no igp-shortcut command.

The SPF in IGP only uses RSVP LSPs as forwarding adjacencies, IGP shortcuts, or as endpoints for LDP-over-RSVP. These applications of RSVP LSPs are mutually exclusive at the IGP instance level. If two or more options are enabled in the same IGP instance, then forwarding adjacency takes precedence over the shortcut application, which takes precedence over the LDP-over-RSVP application.

The SPF in IGP uses SR-TE LSPs as IGP shortcuts only.

When ECMP is enabled on the system and multiple equal-cost paths exist for a prefix, the following selection criteria are used to pick up the set of tunnel and IP next-hops to program in the data path.

  • Where a destination is a tunnel-endpoint (including external prefixes with tunnel-endpoint as the next hop), the tunnel with lowest tunnel-index is selected (the IP next hop is never used in this case).

  • Where a destination is not a tunnel-endpoint:

    • LSPs with metric higher than underlying IGP cost between the endpoint of the LSP are excluded

    • Tunnel next-hops are preferred over IP next-hops

    • Within tunnel next-hops:

      1. The lowest endpoint-to-destination cost is selected

      2. If the endpoint-to-destination costs are the same, the lowest endpoint node router ID is selected

      3. If the router IDs are the same, the lowest tunnel index is selected

    • Within IP next-hops:

      1. The lowest downstream router ID is selected

      2. If the downstream router IDs are the same, the lowest interface-index is selected

Note:

Although ECMP is not performed across both the IP and tunnel next-hops, the tunnel endpoint may lie in one of the shortest IGP paths for that prefix. In that case, the tunnel next hop is always selected as long as the prefix cost using the tunnel is equal or lower than the IGP cost.

When both RSVP-TE and SR-TE IGP shortcuts are available, the IP reach calculation, in the unicast routing table, will first follow the above ECMP tunnel and IP next hop selection rules when resolving a prefix over IGP shortcuts. After the set of ECMP tunnel and IP next-hops have been selected, the preference of tunnel type is then applied based on the user setting of the resolution of the family of the prefix. If the user enabled resolution of the prefix family to both RSVP-TE and SR-TE tunnel types, the TTM tunnel preference value is used to select one type for the prefix. In other words, the RSVP-TE LSP type is preferred to an SR-TE LSP type on a per-prefix basis.

The ingress IOM sprays the packets for this prefix over the set of tunnel next-hops and IP next-hops based on the hashing routine currently supported for IPv4 packets.

This feature provides IGP with the capability to populate the multicast RTM with the prefix IP next hop when both the igp-shortcut and the multicast-import options are enabled in IGP. The unicast RTM can still make use of the tunnel next hop for the same prefix. This change is made possible with the enhancement by which SPF keeps track of both the direct first hop and the tunneled first hop of a node which is added to the Dijkstra tree.

Platforms

All

iid-tlv-enable

iid-tlv-enable

Syntax

[no] iid-tlv-enable

Context

[Tree] (config>service>vprn>isis iid-tlv-enable)

Full Context

configure service vprn isis iid-tlv-enable

Description

This command enables IS-IS multi-instance (MI) as described in draft-ietf-isis-mi-02. Multiple instances allow instance-specific adjacencies to be formed that support multiple network topologies on the same physical interfaces. Each instance has an LSDB, and each PDU contains a TLV identifying the instance and the topology to which the PDU belongs.

The iid-tlv-enable (based on draft-ietf-isis-mi-02) and standard-multi-instance (based on draft-ginsberg-isis-mi-bis-01) commands cannot be configured in the same instance, because the MAC addresses and PDUs in each standard are incompatible.

Default

no iid-tlv-enable

Platforms

All

iid-tlv-enable

Syntax

[no] iid-tlv-enable

Context

[Tree] (config>router>isis iid-tlv-enable)

Full Context

configure router isis iid-tlv-enable

Description

This command enables IS-IS multi-instance (MI) as described in draft-ietf-isis-mi-02. Multiple instances allows the formation of instance-specific adjacencies that support multiple network topologies on the same physical interfaces. Each instance has an LSDB, and each PDU contains a TLV that identifies the instance and the topology to which the PDU belongs.

The iid-tlv-enable (based on draft-ietf-isis-mi-02) and standard-multi-instance (based on draft-ginsberg-isis-mi-bis-01) commands cannot be configured in the same instance, because the MAC addresses and PDUs in each standard are incompatible.

The no form of this command disables IS-IS MI.

Platforms

All

ike-auth-algorithm

ike-auth-algorithm

Syntax

ike-auth-algorithm {md5 | sha1 | sha256 | sha384 | sha512 | aes-xcbc | auth-encryption}

Context

[Tree] (config>ipsec>ike-transform ike-auth-algorithm)

Full Context

configure ipsec ike-transform ike-auth-algorithm

Description

This command specifies the IKE authentication algorithm for the IKE transform

Default

ike-auth-algorithm sha1

Parameters

auth-algorithm

Specifies the values used to identify the hashing algorithm

Values

md5 — Configures the use of the hmac-md5 algorithm for authentication

sha1 — Configures the use of the hmac-sha1 algorithm for authentication

sha256 — Configures the use of the hmac-sha256 algorithm for authentication.

sha384 — Configures the use of the hmac-sha384 algorithm for authentication

sha512 — Configures the use of the hmac-sha512 algorithm for authentication.

aes-xcbc — Configures the use of aes-xcbc (RFC 3566, The AES-XCBC-MAC-96 Algorithm and Its Use With IPsec) algorithm for authentication.

Platforms

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

ike-encryption-algorithm

ike-encryption-algorithm

Syntax

ike-encryption-algorithm {des | 3des | aes128 | aes192 | aes256 | aes128-gcm8 | aes128-gcm16 | aes256-gcm8 | aes256-gcm16}

Context

[Tree] (config>ipsec>ike-transform ike-encryption-algorithm)

Full Context

configure ipsec ike-transform ike-encryption-algorithm

Description

This command specifies the IKE encryption algorithm to be used in the IKE transform instance.

Default

ike-encryption-algorithm aes128

Parameters

encryption-algorithm

Specifies the IKE encryption algorithm.

Values

des — Configures the 56-bit des algorithm for encryption. This is an older algorithm with relatively weak security. While better than nothing, it should only be used where a strong algorithm is not available on both ends at an acceptable performance level.

3des — Configures the 3-des algorithm for encryption. This is a modified application of the des algorithm which uses multiple des operations to make information more secure.

aes128 — Configures the aes algorithm with a block size of 128 bits. This is a mandatory implementation size for aes. This is a very strong algorithm choice.

aes192 — Configures the aes algorithm with a block size of 192 bits. This is a stronger version of aes.

aes256 — Configures the aes algorithm with a block size of 256 bits. This is the strongest available version of aes.

aes128-gcm8 - Configures ESP to use aes-gcm with a 128-bit key size and an 8-byte ICV for encryption and authentication.

aes128-gcm16 - Configures ESP to use aes-gcm with a 128-bit key size and a 16-byte ICV for encryption and authentication.

aes256-gcm8 - Configures ESP to use aes-gcm with a 256-bit key size and an 8-byte ICV for encryption and authentication.

aes256-gcm16 - This parameter configures ESP to use aes-gcm with a 256-bit key size and a 16-byte ICV for encryption and authentication.

Platforms

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

ike-mode

ike-mode

Syntax

ike-mode {main | aggressive}

no ike-mode

Context

[Tree] (config>ipsec>ike-policy ike-mode)

Full Context

configure ipsec ike-policy ike-mode

Description

This command specifies one of either two modes of operation. IKE version 1 can support main mode and aggressive mode. The difference lies in the number of messages used to establish the session.

The no form of this command reverts to the default.

Default

no ike-mode

Parameters

main

Specifies identity protection for the hosts initiating the IPsec session. This mode takes slightly longer to complete.

aggressive

Specifies that the aggressive mode provides no identity protection but is faster.

Platforms

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

ike-policy

ike-policy

Syntax

ike-policy ike-policy-id [create]

no ike-policy ike-policy-id

Context

[Tree] (config>ipsec ike-policy)

Full Context

configure ipsec ike-policy

Description

Commands in this context configure an IKE policy.

The no form of this command

Parameters

ike-policy-id

Specifies a policy ID value to identify the IKE policy.

Values

1 to 2048

Platforms

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

ike-policy

Syntax

ike-policy ike-policy-id

no ike-policy

Context

[Tree] (config>ipsec>trans-mode-prof>dyn ike-policy)

[Tree] (config>service>ies>if>ipsec>ipsec-tunnel>dyn ike-policy)

[Tree] (config>service>vprn>if>sap>ipsec-gw ike-policy)

[Tree] (config>service>ies>if>sap>ipsec-gw ike-policy)

[Tree] (config>service>vprn>if>ipsec>ipsec-tunnel>dyn ike-policy)

[Tree] (config>router>if>ipsec>ipsec-tunnel>dyn ike-policy)

Full Context

configure ipsec ipsec-transport-mode-profile dynamic-keying ike-policy

configure service ies interface ipsec ipsec-tunnel dynamic-keying ike-policy

configure service vprn interface sap ipsec-gw ike-policy

configure service ies interface sap ipsec-gw ike-policy

configure service vprn interface ipsec ipsec-tunnel dynamic-keying ike-policy

configure router interface ipsec ipsec-tunnel dynamic-keying ike-policy

Description

This command specifies the ID of the IKE policy used for IKE negotiation.

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

Parameters

ike-policy-id

Specifies the IKE policy ID.

Values

1 to 2048

Platforms

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

  • configure service ies interface sap ipsec-gw ike-policy
  • configure service vprn interface sap ipsec-gw ike-policy
  • configure ipsec ipsec-transport-mode-profile dynamic-keying ike-policy

VSR

  • configure service vprn interface ipsec ipsec-tunnel dynamic-keying ike-policy
  • configure service ies interface ipsec ipsec-tunnel dynamic-keying ike-policy
  • configure router interface ipsec ipsec-tunnel dynamic-keying ike-policy

ike-prf-algorithm

ike-prf-algorithm

Syntax

ike-prf-algorithm {md5 | sha1 | sha256 | sha384 | sha512 | aes-xcbc | same-as-auth}

Context

[Tree] (config>ipsec>ike-transform ike-prf-algorithm)

Full Context

configure ipsec ike-transform ike-prf-algorithm

Description

This command specifies the PRF algorithm to use for IKE security association.

Note:

If an authenticated encryption algorithm like AES-GCM is used for IKE encryption algorithm, same-as-auth cannot be used for ike-prf-algorithm.

Default

ike-prf-algorithm same-as-auth

Parameters

md5

This parameter configures IKE to use the hmac-md5 algorithm for PRF.

sha1

This parameter configures IKE to use the hmac-sha1 algorithm for PRF.

sha256

This parameter configures IKE to use the hmac-sha256 algorithm for PRF.

sha384

This parameter configures IKE to use the hmac-sha384 algorithm for PRF.

sha512

This parameter configures IKE to use the hmac-sha512 algorithm for PRF.

aes-xcbc

This parameter configures IKE to use the aes128-xcbc algorithm for PRF.

same-as-auth

This parameter configures the same algorithm as IKE authentication algorithm.

Platforms

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

ike-transform

ike-transform

Syntax

ike-transform ike-transform-id [ike-transform-id ...(up to 4 max)]

no ike-transform

Context

[Tree] (config>ipsec>ike-policy ike-transform)

Full Context

configure ipsec ike-policy ike-transform

Description

This command specifies the IKE transform to be used in the IKE policy. Up to four IKE transforms can be specified. If multiple IDs are specified, the system selects an IKE transform based on the peer's proposal. If the system is a tunnel initiator, it uses the configured IKE transform to generate the SA payload.

Default

no ike-transform

Parameters

ike-transform-id

Specifies up to four existing IKE transform instances to be associated with this IKE policy.

Values

1 to 4096

Platforms

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

ike-transform

Syntax

ike-transform ike-transform-id [create]

no ike-transform ike-transform-id

Context

[Tree] (config>ipsec ike-transform)

Full Context

configure ipsec ike-transform

Description

This commands creates a new or enters an existing IKE transform instance. The IKE transform include following configuration for IKE SA:

  • DH Group

  • IKE authentication algorithm

  • IKE encryption algorithm

  • IKE SA lifetime

The ike-transform-id is referenced in the ike-policy configuration.

Parameters

ike-transform

Specifies a number used to uniquely identify an IKE transform instance.

Values

1 to 4096

create

Keyword used to create the ike-transform instance. The create keyword requirement can be enabled or disabled in the environment>create context.

Platforms

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

ike-version

ike-version

Syntax

ike-version {1 | 2}

Context

[Tree] (config>ipsec>ike-policy ike-version)

Full Context

configure ipsec ike-policy ike-version

Description

This command sets the IKE version (1 or 2) that the ike-policy will use.

Default

ike-version 1

Parameters

1 | 2

Specifies the version of IKE protocol.

Platforms

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

ikev1-ph1-responder-delete-notify

ikev1-ph1-responder-delete-notify

Syntax

[no] ikev1-ph1-responder-delete-notify

Context

[Tree] (config>ipsec>ike-policy ikev1-ph1-responder-delete-notify)

Full Context

configure ipsec ike-policy ikev1-ph1-responder-delete-notify

Description

This command specifies the system, when deleting an IKEv1 phase 1 SA for which it was the responder, to send a delete notification to the peer. This command only applies when the configured ike-version 1. This command is ignored with IKE version 2.

The no form of this command reverts to the default.

Default

ikev1-ph1-responder-delete-notify

Platforms

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

ikev2-fragment

ikev2-fragment

Syntax

ikev2-fragment mtu octets reassembly-timeout seconds

no ikev2-fragment

Context

[Tree] (config>ipsec>ike-policy ikev2-fragment)

Full Context

configure ipsec ike-policy ikev2-fragment

Description

This command enables IKEv2 protocol level fragmentation (RFC 7383). The specified MTU is the maximum size of IKEv2 packet.

Default

no ikev2-fragment

Parameters

octets

Specifies the MTU for IKEv2 messages.

Values

512 to 9000

seconds

Specifies the timeout for reassembly.

Values

1 to 5

Platforms

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

imei

imei

Syntax

[no] imei

Context

[Tree] (config>subscr-mgmt>auth-plcy>include-radius-attribute imei)

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

Full Context

configure subscriber-mgmt authentication-policy include-radius-attribute imei

configure subscriber-mgmt radius-accounting-policy include-radius-attribute imei

Description

This command enables the inclusion of the IMEI in AA protocols as signaled in the incoming GTP setup message.

The no form of this command disables the inclusion of the attribute.

Platforms

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

imei

Syntax

[no] imei

Context

[Tree] (config>subscr-mgmt>diam-appl-plcy>nasreq>include-avp imei)

Full Context

configure subscriber-mgmt diameter-application-policy nasreq include-avp imei

Description

This command enables the inclusion of the IMEI AVP, as signaled in the incoming GTP setup message.

The no form of this command disables the inclusion of the AVP.

Platforms

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

implicit-generation

implicit-generation

Syntax

[no] implicit-generation

Context

[Tree] (config>subscr-mgmt>auto-sub-id-key implicit-generation)

Full Context

configure subscriber-mgmt auto-sub-id-key implicit-generation

Description

By default, the system automatically generates a subscriber identifier, using the characters A to Z and 0 to 9, that is used when a subscriber ID is not provided during the authentication of a subscriber host or session and when no explicit default def-sub-id is configured at the SAP or in the MSAP policy.

A subscriber ID obtained from authentication sources can conflict with the format of an implicit, automatically generated subscriber ID. When this happens, the subscriber host or session setup fails and generates the following message: "Non auto-generated sub-id 4574233754 with an auto sub-id format not allowed”. Therefore, when implicit subscriber ID generation is enabled (the default behavior), a 10-character string containing characters A to Z and 0 to 9 should not be returned from authentication sources.

The no form of this command disables the implicit automatic generation of subscriber IDs. When a subscriber ID is not provided in authentication and no explicit def-sub-id is configured, then the host or session setup fails and generates the following message: "Missing subscriber id”. A 10-character (A to Z and 0 to 9) subscriber ID format can be returned from authentication sources without the risk of conflicts.

Disabling the implicit automatic generation of subscriber IDs fail when there are active subscribers with an implicit automatically generated subscriber ID.

Enabling the implicit automatic generation of subscriber IDs fails when there are active subscribers.

Default

implicit-generation

Platforms

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

implicit-null-label

implicit-null-label

Syntax

[no] implicit-null-label

Context

[Tree] (config>router>ldp implicit-null-label)

Full Context

configure router ldp implicit-null-label

Description

This command enables the use of the implicit null label. Use this command to signal the implicit null option for all LDP FECs for which this node is the egress LER.

The no form of this command disables the signaling of the implicit null label.

Default

no implicit-null-label

Platforms

All

implicit-null-label

Syntax

[no] implicit-null-label

Context

[Tree] (config>router>rsvp implicit-null-label)

Full Context

configure router rsvp implicit-null-label

Description

This command enables the use of the implicit null label.

Signaling the IMPLICIT NULL label value for all RSVP LSPs can be enabled for which this node is the egress LER. RSVP must be shut down before being able to change this configuration option.

The egress LER does not signal the implicit null label value on P2MP RSVP LSPs. However, the Penultimate Hop Popping (PHP) node can honor a Resv message with the label value set to the implicit null.

The no form of this command disables the signaling of the implicit null label.

Default

no implicit-null-label

Platforms

All

implicit-null-label

Syntax

implicit-null-label [enable | disable]

no implicit-null-label

Context

[Tree] (config>router>rsvp>interface implicit-null-label)

Full Context

configure router rsvp interface implicit-null-label

Description

This command enables the use of the implicit null label over a specific RSVP interface.

All LSPs for which this node is the egress LER and for which the path message is received from the previous hop node over this RSVP interface will signal the implicit null label. This means that if the egress LER is also the merge-point (MP) node, then the incoming interface for the path refresh message over the bypass dictates if the packet will use the implicit null label or not. The same for a 1-to-1 detour LSP.

The user must shut down the RSVP interface before being able to change the implicit null configuration option.

The no form of this command returns the RSVP interface to use the RSVP level configuration value.

Default

no implicit-null-label

Parameters

enable

Enables the implicit null label.

disable

Disables the implicit null label.

Platforms

All

import

import

Syntax

import policy-name

no import

Context

[Tree] (config>subscr-mgmt>loc-user-db>ipoe>host>mld-parameters import)

[Tree] (config>subscr-mgmt>loc-user-db>ppp>host>mld-parameters import)

Full Context

configure subscriber-mgmt local-user-db ipoe host mld-parameters import

configure subscriber-mgmt local-user-db ppp host mld-parameters import

Description

This command configures an MLD import policy.

The LUDB allows a list of up to 14 MLD import policies per host. The MLD policy also allows the configuration of an additional import policy, providing a total of 15 MLD import policies per host. The import policy inside the MLD policy is always applied last, which determines if the list is a black list or a white list. To configure an MLD white list, the import policies in the LUDB should all be allowed or forward entries and the import policy in the MLD policy should have a default action to deny all. To configure a black list, the import policies inside the LUDB should drop entries and the MLD policy import policy default action should be to forward all. The 15 import policies can be configured to be a mixed white and black list. Since it is difficult to control the order of the import policies within the LUDB, it is recommended to provision the import policy inside the MLD policy first for deterministic behavior.

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

Parameters

policy-name

Specifies the MLD import policy, up to 32 characters, used to control the multicast group accessible for the subscriber host.

Platforms

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

import

Syntax

import policy-name

no import

Context

[Tree] (config>service>vpls>mesh-sdp>mld-snooping import)

[Tree] (config>service>vpls>sap>igmp-snooping import)

[Tree] (config>service>vpls>spoke-sdp>mld-snooping import)

[Tree] (config>service>vpls>mesh-sdp>igmp-snooping import)

[Tree] (config>service>vpls>spoke-sdp>igmp-snooping import)

[Tree] (config>service>vpls>sap>mld-snooping import)

Full Context

configure service vpls mesh-sdp mld-snooping import

configure service vpls sap igmp-snooping import

configure service vpls spoke-sdp mld-snooping import

configure service vpls mesh-sdp igmp-snooping import

configure service vpls spoke-sdp igmp-snooping import

configure service vpls sap mld-snooping import

Description

This command specifies the import routing policy to be used for IGMP packets to be used on this SAP or SDP. Only a single policy can be imported on a SAP at any time.

The no form of this command removes the policy association from the SAP or SDP.

Default

no import

Parameters

policy-name

Specifies the routing policy name. Allowed values are any string up to 32 characters long composed of printable, 7-bit ASCII characters excluding double quotes. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes. Routing policies are configured in the config>router>policy-options context The router policy must be defined before it can be imported.

Platforms

All

import

Syntax

import policy [policy]

no import

Context

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

Full Context

configure subscriber-mgmt bgp-peering-policy import

Description

This command specifies the import policies to be used to control routes advertised to BGP neighbors. Route policies are configured in the config>router>policy-options context. When multiple policy names are specified, the policies are evaluated in the order they are specified. The first policy that matches is applied.

The no form of this command removes all route policy names from the import list.

Default

no import — BGP accepts all routes from configured BGP neighbors. Import policies can be used to limit or modify the routes accepted and their corresponding parameters and metrics.

Parameters

policy

Specifies route policy statement name, up to 32 characters. Up to five policies can be specified.

Platforms

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

import

Syntax

import policy-name

no import

Context

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

Full Context

configure subscriber-mgmt igmp-policy import

Description

This command specifies the import policy to filter IGMP packets.

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

Parameters

policy-name

Specifies the policy name up to 32 characters.

Platforms

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

import

Syntax

import policy-name

no import

Context

[Tree] (config>subscr-mgmt>msap-policy>igmp-host-tracking import)

Full Context

configure subscriber-mgmt msap-policy igmp-host-tracking import

Description

This command specifies the import routing policy to be used for IGMP packets to be used on this SAP or SDP. Only a single policy can be imported on a single SAP at any time.

The no form of this command removes the policy association from the SAP or SDP.

Parameters

policy-name

Specifies the routing policy name, up to 32 characters.

Platforms

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

import

Syntax

import policy-name

no import

Context

[Tree] (config>subscr-mgmt>msap-policy>vpls-only>igmp-snp import)

Full Context

configure subscriber-mgmt msap-policy vpls-only-sap-parameters igmp-snooping import

Description

This command specifies the import routing policy to be used for IGMP packets to be used on this SAP or SDP. Only a single policy can be imported on a single SAP at any time.

The no form of this command removes the policy association from the SAP or SDP.

Parameters

policy-name

Specifies the routing policy name. Allowed values are any string up to 32 characters long composed of printable, 7-bit ASCII characters excluding double quotes. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes. Routing policies are configured in the config>router>policy-options context The router policy must be defined before it can be imported.

Platforms

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

import

Syntax

import policy-name

no import

Context

[Tree] (config>subscr-mgmt>mld-policy import)

Full Context

configure subscriber-mgmt mld-policy import

Description

This command specifies the import routing policy to be used. Only a single policy can be imported at a time.

The no form of this command removes the policy association.

Parameters

policy-name

Specifies the import policy name. Allowed values are any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes. Routing policies are configured in the config>router>policy-options context The router policy must be defined before it can be imported.

Platforms

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

import

Syntax

import policy-name

no import

Context

[Tree] (config>service>vprn>sub-if>grp-if>sap>igmp-snooping import)

Full Context

configure service vprn subscriber-interface group-interface sap igmp-snooping import

Description

This command specifies the import routing policy to be used for IGMP packets to be used on this SAP or SDP. Only a single policy can be imported on a single SAP at any time.

The no form of this command removes the policy association from the SAP or SDP.

Parameters

policy-name

Specifies the routing policy name. Allowed values are any string up to 32 characters long composed of printable, 7-bit ASCII characters excluding double quotes. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes. Routing policies are configured in the config>router>policy-options context The router policy must be defined before it can be imported.

import

Syntax

import policy-name

no import

Context

[Tree] (config>service>vpls>sap>igmp-host-tracking import)

Full Context

configure service vpls sap igmp-host-tracking import

Description

This command associates an import policy to filter IGMP packets.

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

Default

no import

Parameters

policy-name

Specifies the import policy name

Platforms

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

import

Syntax

import policy-name

no import

Context

[Tree] (config>service>ies>sub-if>grp-if>sap>igmp-host-tracking import)

Full Context

configure service ies subscriber-interface group-interface sap igmp-host-tracking import

Description

This command specifies the import routing policy to be used for IGMP packets to be used on this SAP. Only a single policy can be imported on a single SAP at any time.

The no form of this command removes the policy association from the SAP.

Default

no import — No import policy is specified.

Parameters

policy-name

Specifies the import policy name. Values can be string up to 32 characters long of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes. These policies are configured in the config>router> policy-options context. The router policy must be defined before it can be imported.

Platforms

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

import

Syntax

import plcy-or-long-expr [plcy-or-expr]

no import

Context

[Tree] (config>service>vprn>bgp>group>neighbor import)

[Tree] (config>service>vprn>bgp import)

[Tree] (config>service>vprn>bgp>group import)

Full Context

configure service vprn bgp group neighbor import

configure service vprn bgp import

configure service vprn bgp group import

Description

This command is used to specify route policies that control the handling of inbound routes received from certain peers. Route policies are configured in the config>router>policy-options context.

This configuration parameter can be set at three levels: global level (applies to all peers), group level (applies to all peers in a peer-group) or neighbor level (only applies to the specified peer). The most specific level is used

The import command can reference up to 15 objects, where each object is either a policy logical expression or the name of a single policy. The objects are evaluated in the specified order to determine the modifications of each route and the final action to accept or reject the route.

Only one of the 15 objects referenced by the import command can be a policy logical expression consisting of policy names (enclosed in square brackets) and logical operators (AND, OR, NOT). The first of the 15 objects has a maximum length of 255 characters while the remaining 14 objects have a maximum length of 64 characters each.

When multiple import commands are issued, the last command entered overrides the previous command.

When an import policy is not specified, BGP routes are accepted by default.

The no form of this command removes the policy association.

Default

no import

Parameters

plcy-or-long-expr

Specifies the route policy name (up to 64 characters) or a policy logical expression (up to 255 characters).

plcy-or-expr

Specifies the route policy name (up to 64 characters) or a policy logical expression (up to 255 characters).

Platforms

All

import

Syntax

import policy-name

no import

Context

[Tree] (config>service>vprn>igmp>if import)

[Tree] (config>service>vprn>igmp>grp-if import)

Full Context

configure service vprn igmp interface import

configure service vprn igmp group-interface import

Description

This command imports a policy to filter IGMP packets.

The no form of this command removes the policy association from the IGMP instance.

Default

no import — No import policy specified.

Parameters

policy-name

Specifies the import route policy name. Allowed values are any string up to 32 characters composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed between double quotes.

The specified name(s) must already be defined.

Platforms

All

  • configure service vprn igmp interface import

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

  • configure service vprn igmp group-interface import

import

Syntax

import policy-name

no import

Context

[Tree] (config>service>vprn>sap>igmp-trk import)

Full Context

configure service vprn sap igmp-trk import

Description

This command associates an import policy to filter IGMP packets.

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

Default

no import

Parameters

policy-name

Specifies the import policy name.

import

Syntax

import policy-name [policy-name ... (up to 5 max)]

no import

Context

[Tree] (config>service>vprn>isis import)

Full Context

configure service vprn isis import

Description

This command applies one or more (up to five) route polices as IS-IS import policies.

When a prefix received in an IS-IS LSP is accepted by an entry in an IS-IS import policy, it is installed in the routing table, if it is the most preferred route to the destination.

When a prefix received in an IS-IS LSP is rejected by an entry in an IS-IS import policy, it is not installed in the routing table, even if it has the lowest preference value among all the routes to that destination.

The flooding of LSPs is unaffected by IS-IS import policy actions.

The no form of this command removes all policies from the configuration.

Default

no import

Parameters

policy-name

Identifies the export route policy name. Allowed values are any string up to 32 characters, composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed between double quotes. The specified name(s) must already be defined.

Platforms

All

import

Syntax

import policy-name

no import

Context

[Tree] (config>service>vprn>mld>if import)

Full Context

configure service vprn mld interface import

Description

This command specifies the import route policy to be used for determining which membership reports are accepted by the router. Route policies are configured in the config>router>policy-options context.

When an import policy is not specified, all the MLD reports are accepted.

The no form of this command removes the policy association from the MLD instance.

Default

no import

Parameters

policy-name

Specifies the route policy name. Allowed values are any string up to 32 characters composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed between double quotes. Route policies are configured in the config>router>policy-options context.

Platforms

All

import

Syntax

import policy-name [policy-name ...(up to 5 max)]

no import

Context

[Tree] (config>service>vprn>msdp>peer import)

[Tree] (config>service>vprn>msdp>group import)

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

[Tree] (config>service>vprn>msdp>group>peer import)

Full Context

configure service vprn msdp peer import

configure service vprn msdp group import

configure service vprn msdp import

configure service vprn msdp group peer import

Description

This command specifies the policies to import source active state from Multicast Source Discovery Protocol (MSDP) into source active list.

If multiple policy names are specified, the policies are evaluated in the order they are specified. The first policy that matches is applied. If multiple import commands are issued, the last command entered will override the previous command. A maximum of five policy names can be specified.

If you configure an import policy at the global level, each individual peer inherits the global policy.

If you configure an import policy at the group level, each individual peer in a group inherits the group’s policy.

If you configure an import policy at the peer level, then policy only applies to the peer where it is configured.

The no form of this command removes all policies from the configuration.

Default

no import

Parameters

policy-name

Specifies the import policy name. Up to five policy-name arguments can be specified.

Platforms

All

import

Syntax

import {unicast | ext-community}

Context

[Tree] (config>service>vprn>mvpn>vrf-target import)

Full Context

configure service vprn mvpn vrf-target import

Description

This command specifies communities to be accepted from peers.

Parameters

unicast

Specifies to use unicast vrf-target ext-community for the multicast VPN.

ext-comm

An extended BGP community in the type:x:y format. The value x can be an integer or IP address. The type can be the target or origin. x and y are 16-bit integers.

Values

target:{ip-address:comm-val | 2byte-asnumber:ext-comm-val | 4byte-asnumber:comm-val}

ip-address:

a.b.c.d

comm-val:

0 to 65535

2byte-asnumber:

1 to 65535

4byte-asnumber

0 to 4294967295

Platforms

All

import

Syntax

import policy-name [policy-name]

no import

Context

[Tree] (config>service>vprn>ospf3>area import)

[Tree] (config>service>vprn>ospf>area import)

Full Context

configure service vprn ospf3 area import

configure service vprn ospf area import

Description

This command configures ABR import policies to filter OSPFv2 Type 3 Summary-LSAs or OSPFv3 Inter-Area-Prefix-LSA between areas, to only permit the specified routes from being imported into an area.

This command cannot be used in OSPF area 0.

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

Default

no import

Parameters

policy-name

Specifies the export route policy name. A maximum of five policy names can be specified. Allowed values are any string up to 32 characters composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.

The specified policy names must be predefined and already exist in the system.

Platforms

All

import

Syntax

import policy-name [policy-name]

no import

Context

[Tree] (config>service>vprn>ospf3 import)

[Tree] (config>service>vprn>ospf import)

Full Context

configure service vprn ospf3 import

configure service vprn ospf import

Description

This command applies one or more (up to five) route polices as OSPF import policies. When a prefix received in an OSPF LSA is accepted by an entry in an OSPF import policy it is installed in the routing table if it is the most preferred route to the destination. When a prefix received in an OSPF LSA is rejected by an entry in an OSPF import policy it is not installed in the routing table, even if it has the lowest preference value among all the routes to that destination. The flooding of LSAs is unaffected by OSPF import policy actions. This command only applies to the 7750 SR.

Default

If an OSPF route has the lowest preference value among all routes to a destination it is installed in the routing table.

Parameters

policy-name

Specifies the import route policy name. A maximum of five policy names can be specified. Allowed values are any string up to 32 characters composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed between double quotes.

The specified policy name(s) must be predefined and already exist in the system.

Platforms

All

import

Syntax

import {join-policy | register-policy} policy-name [policy-name ...( up to 5 max)]

no import {join-policy | register-policy}

Context

[Tree] (config>service>vprn>pim import)

Full Context

configure service vprn pim import

Description

This command specifies the import route policy to be used for determining which routes are accepted from peers. Route policies are configured in the config>router>policy-options context. When an import policy is not specified, BGP routes are accepted by default.

The no form of this command removes the policy association from the IGMP instance.

Default

no import join-policy

no import register-policy

Parameters

join-policy

Use this command to filter PIM join messages which prevents unwanted multicast streams from traversing the network.

register-policy

This keyword filters register messages. PIM register filters prevent register messages from being processed by the RP. This filter can only be defined on an RP. When a match is found, the RP immediately sends back a register-stop message.

policy-name

Specifies the route policy name. Allowed values are any string up to 32 characters composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed between double quotes. Route policies are configured in the config>router>policy-options context.

Platforms

All

import

Syntax

import policy-name [policy-name ...(up to 5 max)]

no import

Context

[Tree] (config>service>vprn>ripng import)

[Tree] (config>service>vprn>rip>group>neighbor import)

[Tree] (config>service>vprn>ripng>group import)

[Tree] (config>service>vprn>ripng>group>neighbor import)

[Tree] (config>service>vprn>rip import)

[Tree] (config>service>vprn>rip>group import)

Full Context

configure service vprn ripng import

configure service vprn rip group neighbor import

configure service vprn ripng group import

configure service vprn ripng group neighbor import

configure service vprn rip import

configure service vprn rip group import

Description

This command configures import route policies to determine routes that will be accepted from RIP neighbors. If no import policy is specified, RIP accepts all routes from configured RIP neighbors. Import policies can be used to limit or modify the routes accepted and their corresponding parameters and metrics.

If multiple policy names are specified, the policies are evaluated in the order that they are specified. The first policy that matches is applied. If multiple import commands are issued, the last command entered will override the previous command. A maximum of five policy names can be specified.

The no form of this command removes all policies from the configuration.

Default

no import

Parameters

policy-name

The import route policy name. Allowed values are any string up to 32 characters in length and composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed between double quotes. The specified names must already be defined.

Platforms

All

import

Syntax

import policy-name [policy-name]

no import

Context

[Tree] (config>router>ldp import)

Full Context

configure router ldp import

Description

This command configures import route policies to determine which label bindings (FECs) are accepted from LDP neighbors. Policies are configured in the config>router>policy-options context.

If no import policy is specified, LDP accepts all label bindings from configured LDP neighbors. Import policies can be used to limit or modify the routes accepted and their corresponding parameters and metrics.

If multiple policy names are specified, the policies are evaluated in the order they are specified. The first policy that matches is applied. If multiple import commands are issued, the last command entered will override the previous command. A maximum of five policy names can be specified.

The no form of this command removes all policies from the configuration.

Default

no import

Parameters

policy-name

Specifies up to five import route policy names, up to 32 characters composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.

The specified name(s) must already be defined.

Platforms

All

import

Syntax

import policy-name

no import

Context

[Tree] (config>router>igmp>group-interface import)

[Tree] (config>router>igmp>if import)

Full Context

configure router igmp group-interface import

configure router igmp interface import

Description

This command applies the referenced IGMP policy (filter) to an interface subscriber or a group-interface. An IGMP filter is also known as a black/white list and it is defined under the config>router>policy-options.

When redirection is applied, only the import policy from the subscriber will be in effect. The import policy under the group interface is applicable only for IGMP states received directly on the SAP (AN in IGMP proxy mode).

The no form of the command removes the policy association from the IGMP instance.

Default

no import

Parameters

policy-name

The route policy name. Allowed values are any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes. Route policies are configured in the config>router>policy-options context.

Platforms

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

  • configure router igmp group-interface import

All

  • configure router igmp interface import

import

Syntax

import policy-name

no import

Context

[Tree] (config>router>mld>group-interface import)

[Tree] (config>router>mld>if import)

Full Context

configure router mld group-interface import

configure router mld interface import

Description

This command specifies the import route policy to determine which membership reports are accepted by the router. Route policies are configured in the config>router>policy-options context.

When an import policy is not specified, all the MLD reports are accepted.

The no form of this command removes the policy association from the MLD instance.

Default

no import

Parameters

policy-name

Specifies the route policy name. Allowed values are any string up to 32 characters composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes. Route policies are configured in the config>router>policy-options context.

Platforms

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

  • configure router mld group-interface import

All

  • configure router mld interface import

import

Syntax

import policy-name [policy-name]

no import

Context

[Tree] (config>router>msdp>peer import)

[Tree] (config>router>msdp>group import)

[Tree] (config>router>msdp>group>peer import)

[Tree] (config>router>msdp import)

Full Context

configure router msdp peer import

configure router msdp group import

configure router msdp group peer import

configure router msdp import

Description

This command specifies the policies to import source active state from Multicast Source Discovery Protocol (MSDP) into source active list.

If multiple policy names are specified, the policies are evaluated in the order they are specified. The first policy that matches is applied. If multiple import commands are issued, the last command entered will override the previous command. A maximum of five policy names can be specified.

If an import policy is configured at the global level, each individual peer inherits the global policy.

If an import policy is configured at the group level, each individual peer in a group inherits the group’s policy.

If an import policy is configured at the peer level, then policy only applies to the peer where it is configured.

The no form of the command applies no import policies and all source active messages are allowed.

Default

no import

Parameters

policy-name

Specifies the import policy name, up to 32 characters. Up to five policy-name arguments can be specified.

Platforms

All

import

Syntax

import {join-policy | register-policy} [ policy-name [policy-name]]

no import {join-policy | register-policy}

Context

[Tree] (config>router>pim import)

Full Context

configure router pim import

Description

This command specifies the import route policy to be used. Route policies are configured in the config>router>policy-options context.

When an import policy is not specified, BGP routes are accepted by default. Up to five import policy names can be specified.

The no form of this command removes the policy association from the instance.

Default

no import

Parameters

join-policy

Filters PIM join messages which prevents unwanted multicast streams from traversing the network.

register-policy

Filters register messages. PIM register filters prevent register messages from being processed by the RP. This filter can only be defined on an RP. When a match is found, the RP immediately sends back a register-stop message.

policy-name

Specifies the route policy name, up to 32 characters. Route policies are configured in the config>router>policy-options context.

Platforms

All

import

Syntax

import policy-name

no import

Context

[Tree] (config>service>pw-template>igmp-snooping import)

Full Context

configure service pw-template igmp-snooping import

Description

This command specifies the import routing policy to be used for IGMP packets. Only a single policy can be imported at a time.

The no form of the command removes the policy association.

Default

no import

Parameters

policy-name

Specifies the import policy name. Allowed values are any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes. Routing policies are configured in the config>router>policy-options context The router policy must be defined before it can be imported.

Platforms

All

import

Syntax

import type {cert | key | crl} input url-string output filename format input-format [password [32 chars max]]

Context

[Tree] (admin>certificate import)

Full Context

admin certificate import

Description

This command converts an input file (key/certificate/CRL) to a system format file. The following list summarizes the formats supported by this command:

  • Certificate

    • PKCS #12

    • PKCS #7 PEM encoded

    • PKCS #7 DER encoded

    • PEM

    • DER

  • Key

    • PKCS #12

    • PEM

    • DER

  • CRL

    • PKCS #7 PEM encoded

    • PKCS #7 DER encoded

    • PEM

    • DER

Note:

If there are multiple objects with the same type in the input file, only the first object is extracted and converted.

Parameters

input url-string

Specifies the URL for the input file. This URL could be either a local CF card URL file or a FP URL to download the input file.

Values

url-string

<local-url> up to 99 characters

local-url

<cflash-id>/<file-path>

cflash-id

cf1:| cf2:| cf3:

output filename

Specifies the name of output file up to 95 characters. The output directory depends on the file type like following:

  • Key: cf3:\system-pki\key

  • Cert: cf3:\system-pki\cert

  • CRL: cf3:\system-pki\CRL

type

The type of input file.

Values

cert, key, crl

format

Specifies the format of input file.

Values

pkcs12, pkcs7-der, pkcs7-pem, pem, der

password

Specifies the password to decrypt the input file in case that it is an encrypted PKCS#12 file.

Platforms

All

import

Syntax

import plcy-or-long-expr [plcy-or-expr [ plcy-or-expr]]

no import

Context

[Tree] (config>router>bgp import)

[Tree] (config>router>bgp>group>neighbor import)

[Tree] (config>router>bgp>group import)

Full Context

configure router bgp import

configure router bgp group neighbor import

configure router bgp group import

Description

This command specifies route policies that control the handling of inbound routes received from certain peers. Route policies are configured in the config>router>policy-options context.

This configuration parameter can be set at three levels: global level (applies to all peers), group level (applies to all peers in peer-group) or neighbor level (only applies to specified peer). The most specific level is used.

The import command can reference up to 15 objects, where each object is either a policy logical expression or the name of a single policy. The objects are evaluated in the specified order to determine the modifications of each route and the final action to accept or reject the route.

Only one of the 15 objects referenced by the import command is allowed to be a policy logical expression consisting of policy names (enclosed in square brackets) and logical operators (AND, OR, NOT). The first of the 15 objects has a maximum length of 255 characters; the remaining 14 objects have a maximum length of 64 characters each.

When multiple import commands are issued, the last command entered overrides the previous command.

When an import policy is not specified, BGP routes are accepted by default.

The no form of this command removes the policy association.

Default

no import

Parameters

plcy-or-long-expr

Specifies the route policy name (up to 64 characters long) or a policy logical expression (up to 255 characters long). Allowed values are any string up to 255 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.

plcy-or-expr

Specifies the route policy name (up to 64 characters long) or a policy logical expression (up to 64 characters long). Allowed values are any string up to 64 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.

Platforms

All

import

Syntax

import policy-name [policy-name]

no import

Context

[Tree] (config>router>isis import)

Full Context

configure router isis import

Description

This command specifies up to five route polices as IS-IS import policies.

When a prefix received in an IS-IS LSP is accepted by an entry in an IS-IS import policy, it is installed in the routing table, if it is the most preferred route to the destination.

When a prefix received in an IS-IS LSP is rejected by an entry in an IS-IS import policy, it is not installed in the routing table, even if it has the lowest preference value among all the routes to that destination.

The flooding of LSPs is unaffected by IS-IS import policy actions.

The no form of this command removes all policies from the configuration.

Default

no import

Parameters

policy-name

Specifies the import route policy name. Allowed values are any string up to 32 characters, composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes. The specified names must already be defined.

Platforms

All

import

Syntax

import policy-name [policy-name]

no import

Context

[Tree] (config>router>ospf import)

[Tree] (config>router>ospf3 import)

Full Context

configure router ospf import

configure router ospf3 import

Description

This command applies one or more (up to 5) route polices as OSPF import policies. When a prefix received in an OSPF LSA is accepted by an entry in an OSPF import policy, it is installed in the routing table if it is the most preferred route to the destination. When a prefix received in an OSPF LSA is rejected by an entry in an OSPF import policy, it is not installed in the routing table, even if it has the lowest preference value among all the routes to that destination. The flooding of LSAs is unaffected by OSPF import policy actions. The no form of this command removes all policies from the configuration.

Default

no import

Parameters

policy-name

Specifies up to 5 export route policy names. Allowed values are any string up to 32 characters composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes. The specified names must already be defined.

Platforms

All

import

Syntax

[no] import policy-name [ policy-name]

Context

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

[Tree] (config>router>ospf3>area import)

Full Context

configure router ospf area import

configure router ospf3 area import

Description

This command configures ABR import policies to filter OSPFv2 Type 3 Summary-LSAs or OSPFv3 Inter-Area-Prefix-LSA between areas, in order to only permit the specified routes from being imported into an area.

This command cannot be used in OSPF area 0.

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

Default

no import

Parameters

policy-name

Specifies up to five import route policy names. Allowed values are any string up to 32 characters composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes. The specified names must already be defined.

Platforms

All

import

Syntax

import policy-name [policy-name]

no import

Context

[Tree] (config>router>ripng>group>neighbor import)

[Tree] (config>router>rip>group>neighbor import)

[Tree] (config>router>ripng>group import)

[Tree] (config>router>rip>group import)

[Tree] (config>router>rip import)

[Tree] (config>router>ripng import)

Full Context

configure router ripng group neighbor import

configure router rip group neighbor import

configure router ripng group import

configure router rip group import

configure router rip import

configure router ripng import

Description

This command configures import route policies to determine which routes are accepted from RIP neighbors. If no import policy is specified, RIP accepts all routes from configured RIP neighbors. Import policies can be used to limit or modify the routes accepted and their corresponding parameters and metrics.

If multiple policy names are specified, the policies are evaluated in the order they are specified. The first policy that matches is applied. If multiple import commands are issued, the last command entered will override the previous command. A maximum of five policy names can be specified.

The no form of the command removes all policies from the configuration.

Default

no import

Parameters

policy-name

Specifies up to five import route policy names. Allowed values are any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.

The specified names must already be defined.

Platforms

All

import-grt

import-grt

Syntax

import-grt plcy-or-long-expr [plcy-or-expr]

no import-grt

Context

[Tree] (config>service>vprn>grt import-grt)

Full Context

configure service vprn grt-lookup import-grt

Description

This command associates policies to control the leaking of GRT routes into the associated VPRN.

The GRT route must have first been leaked by a leak-export policy defined under the config>router context. Then the route must match a route entry in the specified import-grt policy with an accept action. Refer to the IP Router Configuration Command Reference section in the 7750 SR Extensible Routing System Virtualized Service Router.

The no form of this command removes route leaking policy associations and disables the leaking of GRT routes into the local VPRN.

Parameters

plcy-or-long-expr

Specifies route policy names, up to 64 characters, or a policy logical expression, up to 255 characters.

Values

plcy-or-long-expr: policy-name | long-expr

policy-name: up to 64 characters

long-expr: up to 255 characters

plcy-or-expr

Specifies up to four route policy names, up to 64 characters, or a policy logical expression, up to 64 characters.

Values

plcy-or-expr: policy-name | expr

policy-name: up to 64 characters

expr: up to 64 characters

Platforms

All

import-mcast-policy

import-mcast-policy

Syntax

import-mcast-policy policy-name [policy-name]

no import-mcast-policy

Context

[Tree] (config>router>ldp import-mcast-policy)

Full Context

configure router ldp import-mcast-policy

Description

This command configures an import policy for mLDP FECs arriving on the node. This command does not work for self-generated mLDP FECs. The action of the policy will accept or reject the FEC. If the FEC is rejected, it will be kept but is not resolved.

The no form of this command removes all policies from the configuration.

Default

no import-mcast-policy

Parameters

policy-name

Specifies up to five import route policy names, up to 32 characters, to be assigned to mLDP. The specified name(s) must already be defined.

Platforms

All

import-pmsi-routes

import-pmsi-routes

Syntax

import-pmsi-routes

Context

[Tree] (config>router>ldp import-pmsi-routes)

Full Context

configure router ldp import-pmsi-routes

Description

Commands in this context configure import-pmsi-routes.

For option B, the leafs or ABR/ASBR that are not directly connected to the root have no visibility of the root. As such, for LDP to build the recursive FEC it needs to cache the MVPN PMSI AD routes, this command gives the user the ability to manually enable caching of MVPN PMSI AD routes internally in LDP for EVPN or MVPN inter-as or mvpn_no_export_community intra-as.

Platforms

All

import-prefixes

import-prefixes

Syntax

[no] import-prefixes policy-name

Context

[Tree] (config>router>ldp>session-params>peer import-prefixes)

Full Context

configure router ldp session-parameters peer import-prefixes

Description

This command configures the import FEC prefix policy to determine which prefixes received from this LDP peer are imported and installed by LDP on this node. If resolved these FEC prefixes are then re-distributed to other LDP and T-LDP peers. A FEC prefix that is filtered out (deny) will not be imported. A FEC prefix that is filtered in (accept) will be imported.

If no import policy is specified, the node will import all prefixes received from this LDP/T-LDP peer. This policy is applied in addition to the global LDP policy and targeted session policy.

Policies are configured in the config>router>policy-options context. A maximum of five policy names can be specified. Peer address has to be the peer LSR-ID address.

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

Default

no import-prefixes - no import route policy is specified

Parameters

policy-name

Specifies up to five import-prefix route policy names. Allowed values are any string up to 32 characters long composed of printable, 7-bit ASCII characters excluding double quotes. If the string contains spaces, use double quotes to delimit the start and end of the string. The specified name(s) must already be defined.

Platforms

All

import-prefixes

Syntax

import-prefixes policy-name [policy-name]

no import-prefixes

Context

[Tree] (config>router>ldp>targeted-session import-prefixes)

Full Context

configure router ldp targeted-session import-prefixes

Description

This command configures the import route policy to determine which FEC prefix label bindings are accepted from targeted LDP neighbors into this node. A label binding that is filtered out (deny) will not be imported. A route that is filtered in (accept) will be imported.

If no import policy is specified, this node session will accept all bindings from configured targeted LDP neighbors. This policy is applied in addition to the global LDP policy.

Policies are configured in the config>router>policy-options context. A maximum of five policy names can be specified.

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

Parameters

policy-name

Specifies up to five import policy names. Allowed values are any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.

Platforms

All

import-tunnel-table

import-tunnel-table

Syntax

import-tunnel-table policy-name [policy-name]

no import-tunnel-table

Context

[Tree] (config>router>ldp import-tunnel-table)

Full Context

configure router ldp import-tunnel-table

Description

This command controls the import, in the tunnel table, of LDP tunnels to non-host prefixes. This command is only intended for importing tunnels; it cannot be used for preventing the import of any specific prefix and only non-host prefixes will be considered when evaluating this policy in this context. The LDP tunnels to these non-host prefixes must be created before they can be imported.

This command does not affect the automatic import of LDP tunnels to host prefixes.

The no version of this command removes all of the import policies and, by consequence, any tunnels to non-host prefixes from the tunnel table. If a non-host prefix tunnel is currently being used for forwarding, disabling this command may be service-impacting.

Default

no import-tunnel-table

Parameters

policy-name

Specifies up to five import route policy names. Allowed values are any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.

The specified policy names must already be defined.

Platforms

All

imported-format

imported-format

Syntax

imported-format {any | secure}

Context

[Tree] (config>system>security>pki imported-format)

Full Context

configure system security pki imported-format

Description

This command specifies the allowed format of imported certificates or keys in the cf3:/system-pki directory.

Default

imported-format any

Parameters

any

Allows any imported format.

secure

Only allows enhanced secure imported formats.

Platforms

All

improved-assert

improved-assert

Syntax

[no] improved-assert

Context

[Tree] (config>service>vprn>mvpn>pt>inclusive>pim improved-assert)

Full Context

configure service vprn mvpn provider-tunnel inclusive pim improved-assert

Description

This command enables improved assert procedure on the PIM inclusive provider tunnel.

The no form of this command disables improved assert procedure.

Default

enabled

Platforms

All

improved-assert

Syntax

[no] improved-assert

Context

[Tree] (config>service>vprn>pim>if improved-assert)

Full Context

configure service vprn pim interface improved-assert

Description

This command enables improved assert processing on this interface. The PIM assert process establishes a forwarder for a LAN and requires interaction between the control and forwarding planes.

The assert process is started when data is received on an outgoing interface. This could impact performance if data is continuously received on an outgoing interface.

When enabled, the PIM assert process is done entirely on the control-plane with no interaction between the control and forwarding plane.

Default

improved-assert

Platforms

All

improved-assert

Syntax

[no] improved-assert

Context

[Tree] (config>router>pim>interface improved-assert)

Full Context

configure router pim interface improved-assert

Description

This command enables improved assert processing. The PIM assert process establishes a forwarder for a LAN and requires interaction between the control and forwarding planes. The assert process is started when data is received on an outgoing interface meaning that duplicate traffic is forwarded to the LAN until the forwarder is negotiated among the routers.

When the improved-assert command is enabled, the PIM assert process is done entirely in the control plane. The advantages are that it eliminates duplicate traffic forwarding to the LAN. It also improves performance since it removes the required interaction between the control and data planes.

Note:

improved-assert is still fully interoperable with the RFC 4601, Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised) and RFC 2362, Protocol Independent Multicast-Sparse Mode (PIM-SM), implementations. However, there may be conformance tests that may fail if the tests expect control-data plane interaction in determining the assert winner. Disabling the improved-assert command when performing conformance tests is recommended.

Default

improved-assert

Platforms

All

imsi

imsi

Syntax

[no] imsi imsi

Context

[Tree] (debug>gtp imsi)

Full Context

debug gtp imsi

Description

This command restricts debugging to only data related to the specified IMSI. This command can be repeated multiple times, where only data for any of the specified IMSIs is debugged.

The no form of this command removes the filter for the specified IMSI. If the last IMSI filter is removed, all data is debugged again, but may be restricted by other filters.

Parameters

imsi

Specifies the mobile subscriber identity, as a string of up to 15 characters.

Platforms

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

imsi

Syntax

[no] imsi

Context

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

[Tree] (config>subscr-mgmt>auth-plcy>include-radius-attribute imsi)

Full Context

configure subscriber-mgmt radius-accounting-policy include-radius-attribute imsi

configure subscriber-mgmt authentication-policy include-radius-attribute imsi

Description

This command includes the IMSI RADIUS attribute for FWA sessions.

The no form of this command excludes the RADIUS IMSI attribute.

Default

no imsi

Platforms

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

imsi-apn-filter

imsi-apn-filter

Syntax

imsi-apn-filter

Context

[Tree] (config>app-assure>group>statistics>tca>gtp-filter imsi-apn-filter)

Full Context

configure application-assurance group statistics threshold-crossing-alert gtp-filter imsi-apn-filter

Description

This command configures a TCA for the counter capturing hits due to the GTP IMSI-APN filter.

Platforms

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

imsi-apn-filter

Syntax

imsi-apn-filter

Context

[Tree] (config>app-assure>group>gtp>gtp-fltr imsi-apn-filter)

Full Context

configure application-assurance group gtp gtp-filter imsi-apn-filter

Description

Commands in this context configure IMSI and APN filtering. By default, no APN or IMSI filtering is performed.

The gtpc-inspection command must be enabled before using this command.

This command applies only to the GTP packets that contain IMSI or APN information elements (IEs).

Platforms

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

in-band-control-path

in-band-control-path

Syntax

in-band-control-path

Context

[Tree] (config>redundancy>mc>peer>mcr>ring in-band-control-path)

[Tree] (config>redundancy>mc>peer>mc>l3-ring in-band-control-path)

Full Context

configure redundancy multi-chassis peer mc-ring ring in-band-control-path

configure redundancy multi-chassis peer multi-chassis l3-ring in-band-control-path

Description

Commands in this context configure control path parameters.

The no form of this command reverts to the default.

Platforms

All

in-label

in-label

Syntax

in-label in-label out-label out-label out-link if-name [next-hop next-hop]

no in-label

Context

[Tree] (config>router>mpls>mpls-tp>transit-path>forward-path in-label)

[Tree] (config>router>mpls>mpls-tp>transit-path>reverse-path in-label)

Full Context

configure router mpls mpls-tp transit-path forward-path in-label

configure router mpls mpls-tp transit-path reverse-path in-label

Description

This command configures the label mapping associated with a forward path or reverse path of an MPLS-TP transit path to be configured.

The incoming label, outgoing label and outgoing interface must be configured, using the in-label, out-label and out-link parameters. If the out-link refers to a numbered IP interface, the user may optionally configure the next-hop parameter and the system will determine the interface to use to reach the configured next-hop, but will check that the user-entered value for the out-link corresponds to the link returned by the system. If they do not correspond, then the path will not come up.

Default

no in-label

Parameters

in-label

Specifies the in label.

Values

32 to 16415

out-label

Specifies the out label.

Values

32 to 16415

if-name

Specifies the name of the outgoing interface use for the path.

next-hop

Specifies the next-hop.

Values

a.b.c.d

Platforms

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

in-label

Syntax

in-label in-label

no in-label

Context

[Tree] (config>router>mpls>lsp>protect-tp-path in-label)

[Tree] (config>router>mpls>lsp>working-tp-path in-label)

Full Context

configure router mpls lsp protect-tp-path in-label

configure router mpls lsp working-tp-path in-label

Description

This command configures the incoming label for the reverse path or the working path or the protect path of an MPLS-TP LSP. MPLS-TP LSPs are bidirectional, and so an incoming label value must be specified for each path.

Default

no in-label

Parameters

in-label

Specifies the in label.

Values

32 to 16415

Platforms

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

in-plus-profile-octets-discarded-count

in-plus-profile-octets-discarded-count

Syntax

[no] in-plus-profile-octets-discarded-count

Context

[Tree] (config>log>acct-policy>cr>ref-policer>e-counters in-plus-profile-octets-discarded-count)

[Tree] (config>log>acct-policy>cr>policer>e-counters in-plus-profile-octets-discarded-count)

Full Context

configure log accounting-policy custom-record ref-policer e-counters in-plus-profile-octets-discarded-count

configure log accounting-policy custom-record policer e-counters in-plus-profile-octets-discarded-count

Description

This command includes the in-plus profile octets discarded count.

The no form of this command excludes the in-plus profile octets discarded count.

Default

no in-plus-profile-octets-discarded-count

Platforms

All

in-plus-profile-octets-forwarded-count

in-plus-profile-octets-forwarded-count

Syntax

[no] in-plus-profile-octets-forwarded-count

Context

[Tree] (config>log>acct-policy>cr>policer>e-counters in-plus-profile-octets-forwarded-count)

[Tree] (config>log>acct-policy>cr>ref-policer>e-counters in-plus-profile-octets-forwarded-count)

Full Context

configure log accounting-policy custom-record policer e-counters in-plus-profile-octets-forwarded-count

configure log accounting-policy custom-record ref-policer e-counters in-plus-profile-octets-forwarded-count

Description

This command includes the in-plus profile octets forwarded count.

The no form of this command excludes the in-plus profile octets forwarded count.

Default

no in-plus-profile-octets-forwarded-count

Platforms

All

in-plus-profile-octets-offered-count

in-plus-profile-octets-offered-count

Syntax

[no] in-plus-profile-octets-offered-count

Context

[Tree] (config>log>acct-policy>cr>ref-policer>e-counters in-plus-profile-octets-offered-count)

[Tree] (config>log>acct-policy>cr>policer>e-counters in-plus-profile-octets-offered-count)

Full Context

configure log accounting-policy custom-record ref-policer e-counters in-plus-profile-octets-offered-count

configure log accounting-policy custom-record policer e-counters in-plus-profile-octets-offered-count

Description

This command includes the in-plus profile octets offered count.

The no form of this command excludes the in-plus profile octets offered count.

Default

no in-plus-profile-octets-offered-count

Platforms

All

in-plus-profile-packets-discarded-count

in-plus-profile-packets-discarded-count

Syntax

[no] in-plus-profile-packets-discarded-count

Context

[Tree] (config>log>acct-policy>cr>ref-policer>e-counters in-plus-profile-packets-discarded-count)

[Tree] (config>log>acct-policy>cr>policer>e-counters in-plus-profile-packets-discarded-count)

Full Context

configure log accounting-policy custom-record ref-policer e-counters in-plus-profile-packets-discarded-count

configure log accounting-policy custom-record policer e-counters in-plus-profile-packets-discarded-count

Description

This command includes the in-plus profile packets discarded count.

The no form of this command excludes the in-plus profile packets discarded count.

Default

no in-plus-profile-packets-discarded-count

Platforms

All

in-plus-profile-packets-forwarded-count

in-plus-profile-packets-forwarded-count

Syntax

[no] in-plus-profile-packets-forwarded-count

Context

[Tree] (config>log>acct-policy>cr>policer>e-counters in-plus-profile-packets-forwarded-count)

[Tree] (config>log>acct-policy>cr>ref-policer>e-counters in-plus-profile-packets-forwarded-count)

Full Context

configure log accounting-policy custom-record policer e-counters in-plus-profile-packets-forwarded-count

configure log accounting-policy custom-record ref-policer e-counters in-plus-profile-packets-forwarded-count

Description

This command includes the in-plus profile packets forwarded count.

The no form of this command excludes the in-plus profile packets forwarded count.

Default

no in-plus-profile-packets-forwarded-count

Platforms

All

in-plus-profile-packets-offered-count

in-plus-profile-packets-offered-count

Syntax

[no] in-plus-profile-packets-offered-count

Context

[Tree] (config>log>acct-policy>cr>ref-policer>e-counters in-plus-profile-packets-offered-count)

[Tree] (config>log>acct-policy>cr>policer>e-counters in-plus-profile-packets-offered-count)

Full Context

configure log accounting-policy custom-record ref-policer e-counters in-plus-profile-packets-offered-count

configure log accounting-policy custom-record policer e-counters in-plus-profile-packets-offered-count

Description

This command includes the in-plus profile packets offered count.

The no form of this command excludes the in-plus profile packets offered count.

Default

no in-plus-profile-packets-offered-count

Platforms

All

in-profile-octets-discarded-count

in-profile-octets-discarded-count

Syntax

[no] in-profile-octets-discarded-count

Context

[Tree] (config>subscr-mgmt>acct-plcy>cr>ref-queue>e-counters in-profile-octets-discarded-count)

[Tree] (config>subscr-mgmt>acct-plcy>cr>queue>e-counters in-profile-octets-discarded-count)

Full Context

configure subscriber-mgmt radius-accounting-policy custom-record ref-queue e-counters in-profile-octets-discarded-count

configure subscriber-mgmt radius-accounting-policy custom-record queue e-counters in-profile-octets-discarded-count

Description

This command includes the in-profile octets discarded count.

For queues with stat-mode v4-v6, this command includes the IPv4 octets discarded count instead.

The no form of this command excludes the in-profile octets discarded count.

Platforms

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

in-profile-octets-discarded-count

Syntax

[no] in-profile-octets-discarded-count

Context

[Tree] (config>log>acct-policy>cr>policer>e-counters in-profile-octets-discarded-count)

[Tree] (config>log>acct-policy>cr>queue>e-counters in-profile-octets-discarded-count)

[Tree] (config>log>acct-policy>cr>ref-queue>e-counters in-profile-octets-discarded-count)

[Tree] (config>log>acct-policy>cr>ref-policer>e-counters in-profile-octets-discarded-count)

Full Context

configure log accounting-policy custom-record policer e-counters in-profile-octets-discarded-count

configure log accounting-policy custom-record queue e-counters in-profile-octets-discarded-count

configure log accounting-policy custom-record ref-queue e-counters in-profile-octets-discarded-count

configure log accounting-policy custom-record ref-policer e-counters in-profile-octets-discarded-count

Description

This command includes the in-profile octets discarded count.

The no form of this command excludes the in-profile octets discarded count.

Default

no in-profile-octets-discarded-count

Platforms

All

in-profile-octets-discarded-count

Syntax

[no] in-profile-octets-discarded-count

Context

[Tree] (config>log>acct-policy>cr>ref-policer>i-counters in-profile-octets-discarded-count)

[Tree] (config>log>acct-policy>cr>policer>i-counters in-profile-octets-discarded-count)

Full Context

configure log accounting-policy custom-record ref-policer i-counters in-profile-octets-discarded-count

configure log accounting-policy custom-record policer i-counters in-profile-octets-discarded-count

Description

This command includes the in-profile octets discarded count.

The no form of this command excludes the in-profile octets discarded count.

Default

no in-profile-octets-discarded-count

Platforms

All

in-profile-octets-forwarded-count

in-profile-octets-forwarded-count

Syntax

[no] in-profile-octets-forwarded-count

Context

[Tree] (config>subscr-mgmt>acct-plcy>cr>ref-queue>e-count in-profile-octets-forwarded-count)

[Tree] (config>subscr-mgmt>acct-plcy>cr>queue>e-count in-profile-octets-forwarded-count)

[Tree] (config>subscr-mgmt>acct-plcy>cr>ref-queue>i-count in-profile-octets-forwarded-count)

[Tree] (config>subscr-mgmt>acct-plcy>cr>queue>i-count in-profile-octets-forwarded-count)

Full Context

configure subscriber-mgmt radius-accounting-policy custom-record ref-queue e-counters in-profile-octets-forwarded-count

configure subscriber-mgmt radius-accounting-policy custom-record queue e-counters in-profile-octets-forwarded-count

configure subscriber-mgmt radius-accounting-policy custom-record ref-queue i-counters in-profile-octets-forwarded-count

configure subscriber-mgmt radius-accounting-policy custom-record queue i-counters in-profile-octets-forwarded-count

Description

This command includes the in-profile octets forwarded count. For queues with stat-mode v4-v6, this command includes the IPv4 octets forwarded count instead.

The no form of this command excludes the in-profile octets forwarded count.

Platforms

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

in-profile-octets-forwarded-count

Syntax

[no] in-profile-octets-forwarded-count

Context

[Tree] (config>log>acct-policy>cr>ref-queue>e-counters in-profile-octets-forwarded-count)

[Tree] (config>log>acct-policy>cr>queue>e-counters in-profile-octets-forwarded-count)

[Tree] (config>log>acct-policy>cr>ref-policer>e-counters in-profile-octets-forwarded-count)

[Tree] (config>log>acct-policy>cr>policer>e-counters in-profile-octets-forwarded-count)

Full Context

configure log accounting-policy custom-record ref-queue e-counters in-profile-octets-forwarded-count

configure log accounting-policy custom-record queue e-counters in-profile-octets-forwarded-count

configure log accounting-policy custom-record ref-policer e-counters in-profile-octets-forwarded-count

configure log accounting-policy custom-record policer e-counters in-profile-octets-forwarded-count

Description

This command includes the in-profile octets forwarded count.

The no form of this command excludes the in-profile octets forwarded count.

Default

no in-profile-octets-forwarded-count

Platforms

All

in-profile-octets-forwarded-count

Syntax

[no] in-profile-octets-forwarded-count

Context

[Tree] (config>log>acct-policy>cr>queue>i-counters in-profile-octets-forwarded-count)

[Tree] (config>log>acct-policy>cr>policer>i-counters in-profile-octets-forwarded-count)

[Tree] (config>log>acct-policy>cr>ref-policer>i-counters in-profile-octets-forwarded-count)

[Tree] (config>log>acct-policy>cr>ref-queue>i-counters in-profile-octets-forwarded-count)

Full Context

configure log accounting-policy custom-record queue i-counters in-profile-octets-forwarded-count

configure log accounting-policy custom-record policer i-counters in-profile-octets-forwarded-count

configure log accounting-policy custom-record ref-policer i-counters in-profile-octets-forwarded-count

configure log accounting-policy custom-record ref-queue i-counters in-profile-octets-forwarded-count

Description

This command includes the in profile octets forwarded count.

The no form of this command excludes the in profile octets forwarded count.

Default

no in-profile-octets-forwarded-count

Platforms

All

in-profile-octets-offered-count

in-profile-octets-offered-count

Syntax

[no] in-profile-octets-offered-count

Context

[Tree] (config>log>acct-policy>cr>policer>e-counters in-profile-octets-offered-count)

[Tree] (config>log>acct-policy>cr>ref-policer>e-counters in-profile-octets-offered-count)

Full Context

configure log accounting-policy custom-record policer e-counters in-profile-octets-offered-count

configure log accounting-policy custom-record ref-policer e-counters in-profile-octets-offered-count

Description

This command includes the in profile octets offered count.

The no form of this command excludes the in-profile octets offered count.

Default

no in-profile-octets-offered-count

Platforms

All

in-profile-octets-offered-count

Syntax

[no] in-profile-octets-offered-count

Context

[Tree] (config>log>acct-policy>cr>policer>i-counters in-profile-octets-offered-count)

[Tree] (config>log>acct-policy>cr>ref-policer>i-counters in-profile-octets-offered-count)

Full Context

configure log accounting-policy custom-record policer i-counters in-profile-octets-offered-count

configure log accounting-policy custom-record ref-policer i-counters in-profile-octets-offered-count

Description

This command includes the in-profile octets offered count.

The no form of this command excludes the in-profile octets offered count.

Default

no in-profile-octets-offered-count

Platforms

All

in-profile-packets-discarded-count

in-profile-packets-discarded-count

Syntax

[no] in-profile-packets-discarded-count

Context

[Tree] (config>subscr-mgmt>acct-plcy>cr>ref-queue>e-counters in-profile-packets-discarded-count)

[Tree] (config>subscr-mgmt>acct-plcy>cr>queue>e-counters in-profile-packets-discarded-count)

Full Context

configure subscriber-mgmt radius-accounting-policy custom-record ref-queue e-counters in-profile-packets-discarded-count

configure subscriber-mgmt radius-accounting-policy custom-record queue e-counters in-profile-packets-discarded-count

Description

This command includes the in-profile packets discarded count.

For queues with stat-mode v4-v6, this command includes the IPv4 packets discarded count instead.

The no form of this command excludes the in-profile packets discarded count.

Platforms

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

in-profile-packets-discarded-count

Syntax

[no] in-profile-packets-discarded-count

Context

[Tree] (config>log>acct-policy>cr>policer>e-counters in-profile-packets-discarded-count)

[Tree] (config>log>acct-policy>cr>queue>e-counters in-profile-packets-discarded-count)

[Tree] (config>log>acct-policy>cr>ref-queue>e-counters in-profile-packets-discarded-count)

[Tree] (config>log>acct-policy>cr>ref-policer>e-counters in-profile-packets-discarded-count)

Full Context

configure log accounting-policy custom-record policer e-counters in-profile-packets-discarded-count

configure log accounting-policy custom-record queue e-counters in-profile-packets-discarded-count

configure log accounting-policy custom-record ref-queue e-counters in-profile-packets-discarded-count

configure log accounting-policy custom-record ref-policer e-counters in-profile-packets-discarded-count

Description

This command includes the in-profile packets discarded count.

The no form of this command excludes the in-profile packets discarded count.

Default

no in-profile-packets-discarded-count

Platforms

All

in-profile-packets-discarded-count

Syntax

[no] in-profile-packets-discarded-count

Context

[Tree] (config>log>acct-policy>cr>policer>i-counters in-profile-packets-discarded-count)

[Tree] (config>log>acct-policy>cr>ref-policer>i-counters in-profile-packets-discarded-count)

Full Context

configure log accounting-policy custom-record policer i-counters in-profile-packets-discarded-count

configure log accounting-policy custom-record ref-policer i-counters in-profile-packets-discarded-count

Description

This command includes the in-profile packets discarded count.

The no form of this command excludes the in-profile packets discarded count.

Default

no in-profile-packets-discarded-count

Platforms

All

in-profile-packets-forwarded-count

in-profile-packets-forwarded-count

Syntax

[no] in-profile-packets-forwarded-count

Context

[Tree] (config>subscr-mgmt>acct-plcy>cr>ref-queue>i-count in-profile-packets-forwarded-count)

[Tree] (config>subscr-mgmt>acct-plcy>cr>queue>e-count in-profile-packets-forwarded-count)

[Tree] (config>subscr-mgmt>acct-plcy>cr>ref-queue>e-count in-profile-packets-forwarded-count)

[Tree] (config>subscr-mgmt>acct-plcy>cr>queue>i-count in-profile-packets-forwarded-count)

Full Context

configure subscriber-mgmt radius-accounting-policy custom-record ref-queue i-counters in-profile-packets-forwarded-count

configure subscriber-mgmt radius-accounting-policy custom-record queue e-counters in-profile-packets-forwarded-count

configure subscriber-mgmt radius-accounting-policy custom-record ref-queue e-counters in-profile-packets-forwarded-count

configure subscriber-mgmt radius-accounting-policy custom-record queue i-counters in-profile-packets-forwarded-count

Description

This command includes the in-profile packets forwarded count.

For queues with stat-mode v4-v6, this command includes the IPv4 packets forwarded count instead.

The no form of this command excludes the in-profile packets forwarded count.

Platforms

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

in-profile-packets-forwarded-count

Syntax

[no] in-profile-packets-forwarded-count

Context

[Tree] (config>log>acct-policy>cr>ref-policer>e-counters in-profile-packets-forwarded-count)

[Tree] (config>log>acct-policy>cr>ref-queue>e-counters in-profile-packets-forwarded-count)

[Tree] (config>log>acct-policy>cr>policer>e-counters in-profile-packets-forwarded-count)

[Tree] (config>log>acct-policy>cr>queue>e-counters in-profile-packets-forwarded-count)

Full Context

configure log accounting-policy custom-record ref-policer e-counters in-profile-packets-forwarded-count

configure log accounting-policy custom-record ref-queue e-counters in-profile-packets-forwarded-count

configure log accounting-policy custom-record policer e-counters in-profile-packets-forwarded-count

configure log accounting-policy custom-record queue e-counters in-profile-packets-forwarded-count

Description

This command includes the in-profile packets forwarded count.

The no form of this command excludes the in-profile packets forwarded count.

Default

no in-profile-packets-forwarded-count

Platforms

All

in-profile-packets-forwarded-count

Syntax

[no] in-profile-packets-forwarded-count

Context

[Tree] (config>log>acct-policy>cr>ref-policer>i-counters in-profile-packets-forwarded-count)

[Tree] (config>log>acct-policy>cr>queue>i-counters in-profile-packets-forwarded-count)

[Tree] (config>log>acct-policy>cr>ref-queue>i-counters in-profile-packets-forwarded-count)

[Tree] (config>log>acct-policy>cr>policer>i-counters in-profile-packets-forwarded-count)

Full Context

configure log accounting-policy custom-record ref-policer i-counters in-profile-packets-forwarded-count

configure log accounting-policy custom-record queue i-counters in-profile-packets-forwarded-count

configure log accounting-policy custom-record ref-queue i-counters in-profile-packets-forwarded-count

configure log accounting-policy custom-record policer i-counters in-profile-packets-forwarded-count

Description

This command includes the in profile packets forwarded count.

The no form of this command excludes the in profile packets forwarded count.

Default

no in-profile-packets-forwarded-count

Platforms

All

in-profile-packets-offered-count

in-profile-packets-offered-count

Syntax

[no] in-profile-packets-offered-count

Context

[Tree] (config>log>acct-policy>cr>policer>e-counters in-profile-packets-offered-count)

[Tree] (config>log>acct-policy>cr>ref-policer>e-counters in-profile-packets-offered-count)

Full Context

configure log accounting-policy custom-record policer e-counters in-profile-packets-offered-count

configure log accounting-policy custom-record ref-policer e-counters in-profile-packets-offered-count

Description

This command includes the in profile packets offered count.

The no form of this command excludes the in profile packets offered count.

Default

no in-profile-packets-offered-count

Platforms

All

in-profile-packets-offered-count

Syntax

[no] in-profile-packets-offered-count

Context

[Tree] (config>log>acct-policy>cr>policer>i-counters in-profile-packets-offered-count)

[Tree] (config>log>acct-policy>cr>ref-policer>i-counters in-profile-packets-offered-count)

Full Context

configure log accounting-policy custom-record policer i-counters in-profile-packets-offered-count

configure log accounting-policy custom-record ref-policer i-counters in-profile-packets-offered-count

Description

This command includes the in-profile packets offered count.

The no form of this command excludes the in-profile packets offered count.

Default

no in-profile-packets-offered-count

Platforms

All

in-remark

in-remark

Syntax

in-remark {dscp dscp-name | prec ip-prec-value}

no in-remark

Context

[Tree] (config>qos>sap-ingress>fc in-remark)

Full Context

configure qos sap-ingress fc in-remark

Description

This command is used in a SAP ingress QoS policy to define an explicit in-profile remark action for a forwarding class or subclass. While the SAP ingress QoS policy may be applied to any SAP, the remarking functions are only enforced when the SAP is associated with an IP or subscriber interface (in an IES or VPRN). When the policy is applied to a Layer 2 SAP (i.e., Epipe or VPLS), the remarking definitions are silently ignored.

In the case where the policy is applied to a Layer 3 SAP, the in-profile remarking definition will be applied to packets that have been classified to the forwarding class or subclass. It is possible for a packet to match a classification command that maps the packet to a particular forwarding class or subclass, only to have a more explicit (higher priority match) override the association. Only the highest priority match forwarding class or subclass association will drive the in-profile marking.

The in-remark command is only applicable to ingress IP routed packets that are considered in-profile. The profile of a SAP ingress packet is affected by either the explicit in-profile/out-of-profile definitions or the ingress policing function applied to the packet. Effect of In-Remark Command on Received SAP Ingress Packets shows the effect of the in-remark command on received SAP ingress packets. Within the in-profile IP packet’s ToS field, either the six DSCP bits or the three precedence bits are remarked.

Table 1. Effect of In-Remark Command on Received SAP Ingress Packets

SAP Ingress Packet State

in-remark Command Effect

Non-Routed, Policed In-Profile

No Effect (non-routed packet)

Non-Routed, Policed Out-of-Profile

No Effect (non-routed packet)

Non-Routed, Explicit In-Profile

No Effect (non-routed packet)

Non-Routed, Explicit Out-of-Profile

No Effect (non-routed packet)

IP Routed, Policed In-Profile

in-remark value applied to IP header ToS field

IP Routed, Policed Out-of-Profile

No Effect (out-of-profile packet)

IP Routed, Explicit In-Profile

in-remark value applied to IP header ToS field

IP Routed, Explicit Out-of-Profile

No Effect (out-of-profile packet)

The no form of this command disables ingress remarking of in-profile packets classified to the forwarding class or subclass.

Parameters

dscp dscp-name

Specifies that the matching packet’s DSCP bits should be overridden with the value represented by dscp-name.

The dscp-name parameter is a 6-bit value. It must be one of the predefined DSCP names defined on the system.

Values

be, cp1, cp2, cp3, cp4, cp5, cp6, cp7, cs1, cp9, af11, cp11, af12, cp13, af13, cp15, cs2, cp17, af21, cp19, af22, cp21, af23, cp23, cs3, cp25, af31, cp27, af32, cp29, af33, cp31, cs4, cp33, af41, c p35, af42, cp37, af43, cp39, cs5, cp41, cp42, cp43, cp44, cp45, ef, cp47, nc1, cp49, cp50, cp51, cp52, cp53, cp54, cp55, nc2, cp57, cp58, cp59, cp60, cp61, cp62, cp63

prec ip-prec-value

Specifies that the matching packet’s precedence bits should be overridden with the value represented by ip-prec-value.

Values

0 to 7

Platforms

All

inactive-flow-timeout

inactive-flow-timeout

Syntax

inactive-flow-timeout seconds

no inactive-flow-timeout

Context

[Tree] (config>cflowd inactive-flow-timeout)

Full Context

configure cflowd inactive-flow-timeout

Description

This command specifies the length of time, in seconds, that must elapse without a packet matching a flow before the flow is considered inactive.

The no form of this command resets the inactive flow timeout back to the default of 15 seconds.

Existing flows do not inherit the new inactive-flow-timeout value if this parameter is changed while cflowd is active. The inactive-flow-timeout value for a flow is set when the flow is first created in the active cache table and does not change dynamically.

Default

inactive-flow-timeout 15

Parameters

seconds

Specifies the length of time, in seconds, without a packet matching a flow before the flow is considered inactive.

Values

10 to 600

Platforms

All

inactivity-mon

inactivity-mon

Syntax

[no] inactivity-mon

Context

[Tree] (config>app-assure>group>transit-ip-policy>transit-auto-create inactivity-mon)

Full Context

configure application-assurance group transit-ip-policy transit-auto-create inactivity-mon

Description

This command enables auto removal of inactive transit subscribers. Periodically AA removes any inactive auto-created subscriber where an inactive sub is defined as having no active flows in the last period.

The no form of this command disables the auto removal of inactive transit subscribers.

Platforms

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

inactivity-timeout

inactivity-timeout

Syntax

inactivity-timeout seconds

no inactivity-timeout

Context

[Tree] (config>test-oam>twamp>server inactivity-timeout)

Full Context

configure test-oam twamp server inactivity-timeout

Description

This command configures the inactivity time out for all TWAMP-control connections. If no TWAMP control message is exchanged over the TCP connection for this duration of time the connection is closed and all in-progress tests are terminated.

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

Default

inactivity-timeout 900

Parameters

seconds

Specifies the duration of the inactivity time out.

Values

60 to 3600

Default

900

Platforms

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

inactivity-timeout

Syntax

inactivity-timeout seconds

no inactivity-timeout

Context

[Tree] (config>test-oam>twamp>twamp-light inactivity-timeout)

Full Context

configure test-oam twamp twamp-light inactivity-timeout

Description

This command configures the length of time to maintain stale state on the session reflector. Stale state is test data that has not been refreshed or updated by newly arriving probes for that specific test in a predetermined length of time. Any single reflector can maintain up state for a maximum of 12000 tests. If the maximum value is exceeded, the session reflector lacks memory to allocate to new tests.

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

Default

inactivity-timeout 100

Parameters

seconds

Specifies the value in seconds for maintaining stale state.

Values

10 to 100

Default

100

Platforms

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

inactivity-timer

inactivity-timer

Syntax

inactivity-timer [days days] [hrs hours] [min minutes] [sec seconds]

no inactivity-timer

Context

[Tree] (config>service>ies>sub-if>grp-if>ipv6>rtr-sol inactivity-timer)

[Tree] (config>service>ies>sub-if>ipv6>rtr-sol inactivity-timer)

[Tree] (config>service>vprn>sub-if>ipv6>rtr-sol inactivity-timer)

Full Context

configure service ies subscriber-interface group-interface ipv6 router-solicit inactivity-timer

configure service ies subscriber-interface ipv6 router-solicit inactivity-timer

configure service vprn subscriber-interface ipv6 router-solicit inactivity-timer

Description

This command specifies the time before an inactive host is removed.

The no form of this command reverts to the default.

Parameters

infinite

Specifies that the idle host is never removed.

days

Specifies that the idle host is removed if idle within the number of specified days.

hours

Specifies that the idle host is removed if idle within the number of specified hours.

minutes

Specifies that the idle host is removed if idle within the number of specified minutes.

seconds

Specifies that the idle host is removed if idle within the number of specified seconds.

Platforms

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

inactivity-timer

Syntax

inactivity-timer timer

no inactivity-timer

Context

[Tree] (config>eth-cfm>slm inactivity-timer)

Full Context

configure eth-cfm slm inactivity-timer

Description

The time the responder keeps a test active. Should the time between packets exceed this values within a test the responder will mark the previous test as complete. It will treat any new packets from a peer with the same test-id, source-mac and MEP-ID as a new test responding with the sequence number one.

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

Default

inactivity-timer 100

Parameters

timer

Specifies the amount of time in seconds.

Values

10 100

Platforms

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

inband

inband

Syntax

inband service-id

no inband

Context

[Tree] (config>system>security>vprn-aaa-server inband)

Full Context

configure system security vprn-aaa-server inband

Description

This command configures TACACS+ or RADIUS servers in a VPRN to be used for AAA by that VPRN and by sessions in the Base routing instance.

The no form of this command disables the use of servers for in-band management.

Default

no inband

Parameters

service-id

Specifies the VPRN server for AAA to use for in-band sessions.

Values

service-id: 1 to 2147483648

svc-name: 64 characters maximum

Platforms

All

inband-collector-export-only

inband-collector-export-only

Syntax

[no] inband-collector-export-only

Context

[Tree] (config>cflowd inband-collector-export-only)

Full Context

configure cflowd inband-collector-export-only

Description

This command, when the inband-collector-export-only command is enabled, allows only collectors that are reachable through inband interfaces and enables a higher flow export rate.

The no form of this command, the default, re-enables the use of the out-of-band management Ethernet port.

Platforms

All

inbound-max-sessions

inbound-max-sessions

Syntax

inbound-max-sessions number-of-sessions

no inbound-max-sessions

Context

[Tree] (config>system>login-control>ftp inbound-max-sessions)

Full Context

configure system login-control ftp inbound-max-sessions

Description

This command configures the maximum number of concurrent inbound FTP sessions.

This value is the combined total of inbound and outbound sessions.

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

Default

inbound-max-sessions 3

Parameters

value

Specifies the maximum number of concurrent FTP sessions on the node.

Values

0 to 5

Platforms

All

inbound-max-sessions

Syntax

inbound-max-sessions number-of-sessions

no inbound-max-sessions

Context

[Tree] (config>system>login-control>telnet inbound-max-sessions)

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

Full Context

configure system login-control telnet inbound-max-sessions

configure system login-control ssh inbound-max-sessions

Description

This parameter limits the number of inbound Telnet and SSH sessions. A maximum of 30 telnet and ssh connections can be established to the router. The local serial port cannot be disabled.

Telnet and SSH maximum sessions can also use the combined total of both inbound sessions (SSH+Telnet). While it is acceptable to continue to internally limit the combined total of SSH and Telnet sessions to N, either SSH or Telnet sessions can use the inbound maximum sessions, if so required by the Operator.

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

Default

inbound-max-sessions 5

Parameters

number-of-sessions

The maximum number of concurrent inbound Telnet sessions, expressed as an integer.

Values

0 to 50 (default = 5) or 0 to N where N is the new total number of SSH+Telnet sessions if they are scaled

Platforms

All

incl-mcast-l2-attributes-advertisement

incl-mcast-l2-attributes-advertisement

Syntax

[no] incl-mcast-l2-attributes-advertisement

Context

[Tree] (config>service>vpls>bgp-evpn incl-mcast-l2-attributes-advertisement)

Full Context

configure service vpls bgp-evpn incl-mcast-l2-attributes-advertisement

Description

This command triggers the advertisement of the Layer-2 Attributes extended community including:

  • Service-MTU in the layer-2 MTU field
  • C bit, which is set based on the configuration of the control-word command (when enabled, sets the C bit, otherwise it is unset)

Upon reception, the Layer-2 MTU for a peer is compared with the local service MTU. If there is a mismatch, the EVPN destination is operational state is down, unless the bgp-evpn ignore-mtu-mismatch command is enabled.

The received C bit from a peer is compared with the local control-word setting. In case of a mismatch the EVPN destination becomes operationally down.

The no form of this command prevents the router from advertising the Layer-2 Attributes extended community along with the Inclusive Multicast Ethernet Tag route for the service.

Default

no incl-mcast-l2-attributes-advertisement

Platforms

All

incl-mcast-orig-ip

incl-mcast-orig-ip

Syntax

incl-mcast-orig-ip ip-address

no incl-mcast-orig-ip

Context

[Tree] (config>service>vpls>bgp-evpn>mpls incl-mcast-orig-ip)

Full Context

configure service vpls bgp-evpn mpls incl-mcast-orig-ip

Description

The IP address configured by the user in the incl-mcast-orig-ip command is encoded in the originating-ip field of EVPN Inclusive Multicast Routes with tunnel type Ingress Replication (value 6), mLDP (2), and Composite IR and mLDP (130).

The configured address does not need to be reachable in the base router or have an interface in the base router. The originating-ip address is used solely for BGP route-key selection.

The originating-ip is never changed for Inclusive Multicast Routes with tunnel type AR (Assisted Replication, value 10).

The no version of the command withdraws the affected Inclusive Multicast Routes and re-advertises it with the default system-ip address in the originating-ip field.

Default

incl-mcast-orig-ip 1

Parameters

ip-address

Specifies the IPv4 address value.

Values

a.b.c.d

Platforms

All

include

include

Syntax

include group-name [group-name]

no include [group-name [group-name]]

Context

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

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

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

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

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

Full Context

configure router mpls lsp include

configure router mpls lsp secondary include

configure router mpls lsp primary include

configure router mpls lsp primary-p2mp-instance include

configure router mpls lsp-template include

Description

This command specifies the admin groups to be included when an LSP is set up. Up to five groups per operation can be specified, up to 32 maximum. The include statement instructs the CSPF algorithm to pick TE links among the links which belong to one or more of the specified admin groups. A link that does not belong to at least one of the specified admin groups is excluded and thus pruned from the TE database before the CSPF computation. However, a link can still be selected if it belongs to one of the groups in a include statement but also belongs to other groups which are not part of any include statement in the LSP or primary/secondary path configuration. In other words, the include statements implements the "include-any” behavior.

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

The no form of this command deletes the specified groups in the specified context.

Default

no include

Parameters

group-name

Specifies admin groups to be included when an LSP is set up.

Platforms

All

include

Syntax

[no] include

Context

[Tree] (config>service>nat>syslog>syslog-export-policy include)

Full Context

configure service nat syslog syslog-export-policy include

Description

Commands in this context specify the optional fields to include in the NAT syslog messages.

Platforms

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

include

Syntax

[no] include tag

Context

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

Full Context

configure router admin-tags route-admin-tag-policy include

Description

This configures an admin tag to be included when matching a route against an LSP.

Up to eight inclusion statements are supported per policy.

The no form of this command removes the admin tag from the include statement.

Parameters

tag

Specifies the value of the admin tag, up to 32 characters.

Platforms

All

include-all

include-all

Syntax

include-all

Context

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

Full Context

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

Description

Commands in this context configure administrative groups to include in the flexible algorithm topology graph. Administrative groups are attributes associated with a link and are generally referred to as link colors.

Flexible algorithms provide the possibility to restrict inclusion into the topology graph to links that have a pre-defined combination of associated administrative groups. The include-all command requires that all configured administrative groups must be present in a link before the link can be included in the topology graph.

Platforms

All

include-any

include-any

Syntax

include-any

Context

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

Full Context

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

Description

Commands in this context configure administrative groups to include in the flexible algorithm topology graph. Administrative groups are attributes associated with a link and are generally referred to as link colors.

Flexible algorithms provide the possibility to restrict inclusion into the topology graph to links that have a pre-defined combination of associated administrative groups. The include-any command requires that one of the configured administrative groups must be present on a link before the link can be included in the topology graph.

Platforms

All

include-avp

include-avp

Syntax

[no] include-avp

Context

[Tree] (config>subscr-mgmt>diam-appl-plcy>gx include-avp)

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

[Tree] (config>subscr-mgmt>diam-appl-plcy>nasreq include-avp)

Full Context

configure subscriber-mgmt diameter-application-policy gx include-avp

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

configure subscriber-mgmt diameter-application-policy nasreq include-avp

Description

Commands in this context configure AVPs and their format to be included in Diameter Gx, Gy, or NASREQ application messages. For full description each AVP, refer to the 7750 SR and VSR RADIUS Attributes Reference Guide.

AVP name:

  • an-gw-address

  • apn-ambr

  • called-station-id

  • calling-station-id

  • charging-characteristics

  • dynamic-address-flag

  • ip-can-type

  • logical-access-id

  • nas-port

  • nas-port-id

  • nas-port-type

  • pdn-connection-id

  • physical-access-id

  • rai

  • rat-type

  • selection-mode

  • sgsn-mcc-mnc

  • supported-features

  • user-equipment-info

  • user-location-info

Platforms

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

include-dns

include-dns

Syntax

[no] include-dns

Context

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

[Tree] (config>service>ies>sub-if>ipv6>rtr-adv include-dns)

[Tree] (config>service>vprn>sub-if>ipv6>rtr-adv include-dns)

[Tree] (config>subscr-mgmt>rtr-adv-plcy>dns-opt include-dns)

[Tree] (config>service>ies>sub-if>grp-if>ipv6 include-dns)

Full Context

configure service vprn subscriber-interface group-interface ipv6 include-dns

configure service ies subscriber-interface ipv6 rtr-adv include-dns

configure service vprn subscriber-interface ipv6 rtr-adv include-dns

configure subscriber-mgmt router-advertisement-policy dns-options include-dns

configure service ies subscriber-interface group-interface ipv6 include-dns

Description

This command specifies to include the Recursive DNS Server (RDNSS) Option as defined in RFC 6106 in IPv6 router advertisements for DNS name resolution of IPv6 SLAAC hosts.

The no form of this command returns the command to the default setting.

Platforms

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

include-dns

Syntax

[no] include-dns

Context

[Tree] (config>service>ies>sub-if>ipv6>rtr-adv>dns-opt include-dns)

[Tree] (config>service>vprn>sub-if>grp-if>ipv6>rtr-adv>dns-opt include-dns)

[Tree] (config>service>vprn>sub-if>ipv6>rtr-adv>dns-opt include-dns)

[Tree] (config>service>ies>sub-if>grp-if>ipv6>rtr-adv>dns-opt include-dns)

Full Context

configure service ies subscriber-interface ipv6 router-advertisements dns-options include-dns

configure service vprn subscriber-interface group-interface ipv6 router-advertisements dns-options include-dns

configure service vprn subscriber-interface ipv6 router-advertisements dns-options include-dns

configure service ies subscriber-interface group-interface ipv6 router-advertisements dns-options include-dns

Description

This command specifies to include the Recursive DNS Server (RDNSS) Option as defined in RFC 6106 in IPv6 Router Advertisements for DNS name resolution of IPv6 SLAAC hosts.

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

include-dns

Syntax

[no] include-dns

Context

[Tree] (config>service>vprn>router-advert>if>dns-options include-dns)

Full Context

configure service vprn router-advertisement interface dns-options include-dns

Description

This command enables the Recursive DNS Server (RDNSS) Option in router advertisements. This must be enabled for each interface on which the RDNSS option is required in router advertisement messages.

The no form of this command disables the RDNSS option in router advertisements.

Default

include-dns

Platforms

All

include-dns

Syntax

[no] include-dns

Context

[Tree] (config>router>router-advert>if>dns-opt include-dns)

Full Context

configure router router-advertisement interface dns-options include-dns

Description

This command enables the Recursive DNS Server (RDNSS) Option in router advertisements. This must be enabled for each interface on which the RDNSS option is required in router advertisement messages.

The no form of this command disables the RDNSS option in router advertisements.

Default

include-dns

Platforms

All

include-group

include-group

Syntax

include-group ip-admin-group-name [pref preference]

no include-group ip-admin-group-name

Context

[Tree] (config>router>route-next-hop-policy>template include-group)

Full Context

configure router route-next-hop-policy template include-group

Description

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

Each group is entered individually. The include-group statement instructs the LFA SPF selection algorithm to pick up a subset of LFA next-hops among the links which belong to one or more of the specified admin groups. A link which does not belong to at least one of the admin-groups is excluded. However, a link can still be selected if it belongs to one of the groups in a include-group statement but also belongs to other groups which are not part of any include-group statement in the route next-hop policy.

The pref option is used to provide a relative preference for the admin group to select. A lower preference value means that LFA SPF will first attempt to select a LFA backup next-hop which is a member of the corresponding admin group. If none is found, then the admin group with the next higher preference value is evaluated. If no preference is configured for a given admin group name, then it is supposed to be the least preferred, that is, numerically the highest preference value.

When evaluating multiple include-group statements within the same preference, any link which belongs to one or more of the included admin groups can be selected as an LFA next-hop. There is no relative preference based on how many of those included admin groups the link is a member of.

The exclude-group statement simply prunes all links belonging to the specified admin group before making the LFA backup next-hop selection for a prefix.

If the same group name is part of both include and exclude statements, the exclude statement will win. It other words, the exclude statement can be viewed as having an implicit preference value of 0.

The admin-group criteria are applied before running the LFA next-hop selection algorithm.

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

Parameters

ip-admin-group-name

Specifies the name of the group, up to 32 characters.

preference

An integer specifying the relative preference of a group.

Values

1 to 255

Default

255

Platforms

All

include-radius-attribute

include-radius-attribute

Syntax

[no] include-radius-attribute

Context

[Tree] (config>aaa>l2tp-acct-plcy include-radius-attribute)

Full Context

configure aaa l2tp-accounting-policy include-radius-attribute

Description

Commands in this context specify the RADIUS attributes that the system should include into RADIUS Access-Request (for authentication) and Accounting-Request (for accounting) messages.

The no form of this command disables the RADIUS attributes to be included.

Platforms

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

include-radius-attribute

Syntax

[no] include-radius-attribute

Context

[Tree] (config>subscr-mgmt>auth-plcy include-radius-attribute)

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

Full Context

configure subscriber-mgmt authentication-policy include-radius-attribute

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

Description

Commands in this context specify the RADIUS attributes that the system should include in RADIUS Access-Request (for authentication) and Accounting-Request (for accounting) 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, VSR

include-radius-attribute

Syntax

[no] include-radius-attribute

Context

[Tree] (config>ipsec>rad-acct-plcy include-radius-attribute)

[Tree] (config>ipsec>rad-auth-plcy include-radius-attribute)

Full Context

configure ipsec radius-accounting-policy include-radius-attribute

configure ipsec radius-authentication-policy include-radius-attribute

Description

Commands in this context specify the RADIUS attributes that the system should include into RADIUS Access-Request (for authentication) and Accounting-Request (for accounting) messages.

Platforms

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

include-system-info

include-system-info

Syntax

[no] include-system-info

Context

[Tree] (config>log>accounting-policy include-system-info)

Full Context

configure log accounting-policy include-system-info

Description

This command allows the operator to optionally include router information at the top of each accounting file generated for a given accounting policy.

The no form of this command configures the router to not include optional router information at the top of the file.

Default

no include-system-info

Platforms

All

included-protocols

included-protocols

Syntax

included-protocols

Context

[Tree] (config>sys>security>cpu-protection>ip included-protocols)

Full Context

configure system security cpu-protection ip-src-monitoring included-protocols

Description

This context allows configuration of which protocols are included for ip-src-monitoring. This is system-wide configuration that applies to cpu protection globally.

Platforms

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

inclusive

inclusive

Syntax

inclusive

Context

[Tree] (config>service>vpls>provider-tunnel inclusive)

Full Context

configure service vpls provider-tunnel inclusive

Description

Commands in this context configure the use of a P2MP LSP as the default tree for forwarding Broadcast, Unknown unicast, and Multicast (BUM) packets of a VPLS or B-VPLS instance. The P2MP LSP is referred to, in this case, as the Inclusive Provider Multicast Service Interface (I-PMSI).

When enabled, this feature relies on BGP Auto-Discovery (BGP-AD), BGP-VPLS or BGP-EVPN to discover the PE nodes participating in a specified VPLS/B-VPLS instance. In the case of BGP-AD or BGP-VPLS, the BGP route contains the information required to signal both point-to-point (P2P) PWs used to forward unicast known Ethernet frames, and the RSVP or mLDP P2MP LSP used to forward the BUM frames. In the case of BGP-EVPN, the EVPN IMET route contains the information to set up the mLDP P2MP LSP and may also contain the information that enables the remote leaf-only nodes to setup an EVPN destination to the sending PE.

Note:

The provider-tunnel for a specified service must be configured with an owner protocol (BGP-AD, BGP-VPLS or BGP-EVPN); only one owner must be configured. Use the owner {bgp-ad|bgp-vpls|bgp-evpn-mpls} command to configure an owner.

With an mLDP I-PMSI, each leaf node will initiate the signaling of the mLDP P2MP LSP upstream using the P2MP FEC information in the I-PMSI tunnel information discovered through the BGP.

If IGMP or PIM snooping are configured on the VPLS/B-VPLS instance, multicast packets matching an L2 multicast Forwarding Information Base (FIB) record will also be forwarded over the P2MP LSP.

Use the mldp command to enable the use of an LDP P2MP LSP as the I-PMSI for forwarding Ethernet BUM and IP multicast packets in a VPLS instance:

config>service>vpls [b-vpls]>provider-tunnel>inclusive>mldp

When a no shutdown is performed under the context of the inclusive node and the expiration of a delay timer, BUM packets will be forwarded over an automatically signaled mLDP P2MP LSP.

Use the root-and-leaf command to configure the node to operate as both root and leaf in the VPLS instance:

config>service>vpls [b-vpls]>provider-tunnel>inclusive>root-and-leaf

The node behaves as a leaf-only node by default. For the I-PMSI of type mLDP, the leaf-only node will join I-PMSI rooted at other nodes it discovered but will not include a PMSI Tunnel Attribute in BGP route update messages. This way a leaf-only node will forward packets to other nodes in the VPLS/B-VPLS using the point-to-point spoke-SDPs in the case of BGP-AD or BGP-VPLS, or using EVPN destinations in the case of BGP-EVPN.

Note:

Either BGP-AD/VPLS or BGP-EVPN must be enabled in the VPLS/B-VPLS instance otherwise the execution of the no shutdown command under the context of the inclusive node will fail and the I-PMSI will not come up.

If the P2MP LSP instance goes down, the VPLS/B-VPLS immediately reverts the forwarding of BUM packets to the P2P PWs or EVPN destinations (in the case of BGP-EVPN). Performing a shutdown under the context of the inclusive node will allow the user to restore BUM packet forwarding over the P2P PWs or EVPN destinations.

This feature is supported with VPLS and B-VPLS; it is not supported with I-VPLS. Although Routed VPLS is supported, routed traffic cannot be sent over the I-PMSI tree.

Platforms

All

inclusive

Syntax

inclusive

Context

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

Full Context

configure service vprn mvpn provider-tunnel inclusive

Description

Commands in this context specify inclusive provider tunnels.

Platforms

All

inclusive

Syntax

inclusive

Context

[Tree] (config>router>gtm>provider-tunnel inclusive)

Full Context

configure router gtm provider-tunnel inclusive

Description

Commands in this context configure inclusive provider tunnels parameters.

Platforms

All

incoming-sid

incoming-sid

Syntax

incoming-sid static label

no incoming-sid

Context

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

Full Context

configure router p2mp-sr-tree replication-segment incoming-sid

Description

This command configures the incoming replication SID for this P2MP SR tree replication segment entry.

The no form of this command removes the incoming replication SID.

Parameters

static label

Specifies the incoming replication SID label.

Values

0 to 4294967295

Platforms

All

incremental-spf-wait

incremental-spf-wait

Syntax

incremental-spf-wait incremental-spf-wait

no incremental-spf-wait

Context

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

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

Full Context

configure router ospf timers incremental-spf-wait

configure router ospf3 timers incremental-spf-wait

Description

This command sets the delay before an incremental SPF calculation is performed when LSA types 3, 4, 5, or 7 are received. This allows multiple updates to be processed in the same SPF calculation. Type 1 or type 2 LSAs are considered a topology change and will always trigger a full SPF calculation.

The no form of this command resets the timer value back to the default value.

Note:

The timer granularity is 10 ms if the value is less than 500 ms, and 100 ms if the value is ≥ 500 ms. Timer values are rounded down to the nearest granularity, for example a configured value of 550 ms is internally rounded down to 500 ms.

Default

incremental-spf-wait 1000

Parameters

incremental-spf-wait

Specifies the OSPF incremental SPF calculation delay, in milliseconds.

Values

0 to 1000

Platforms

All

index

index

Syntax

index index [create]

no index index

Context

[Tree] (config>service>dynsvc>ladb>user index)

Full Context

configure service dynamic-services local-auth-db user-name index

Description

This command creates an index entry containing authentication data for a dynamic service SAP. Up to 32 indexes can be created per user name entry, representing up to 32 dynamic service SAPs that can be instantiated with a single dynamic service data trigger. One of the dynamic service SAPs must be the data trigger SAP.

The no form of this command removes the index entry from the user name entry in the local authentication database configuration.

Parameters

index

Specifies the index entry identifier.

Values

1 to 32

Platforms

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

indirect

indirect

Syntax

[no] indirect ip-address

Context

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

Full Context

configure service vprn static-route-entry indirect

Description

This command specifies that the route is indirect and specifies the next hop IP address used to reach the destination.

The configured ip-address is not directly connected to a network configured on this node. The destination can be reached via multiple paths. The indirect address can only be resolved from dynamic routing protocol. Another static route cannot be used to resolve the indirect address.

The ip-address configured here can be either on the network side or the access side and is typically at least one hop away from this node.

Default

no indirect

Parameters

ip-address

The IP address of the IP interface.

Values

ipv4-address

a.b.c.d

ipv6-address

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

Platforms

All

indirect

Syntax

[no] indirect ip-address

Context

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

Full Context

configure router static-route-entry indirect

Description

This command specifies that the route is indirect and specifies the next hop IP address used to reach the destination.

The configured ip-address is not directly connected to a network configured on this node. The destination can be reached via multiple paths. The indirect address can only be resolved from dynamic routing protocol. Another static route cannot be used to resolve the indirect address.

The ip-address configured here can be either on the network side or the access side and is typically at least one hop away from this node.

Default

no indirect

Parameters

ip-address

Specifies the IP address of the IP interface.

Values

ipv4-address

a.b.c.d

ipv6-address

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

Platforms

All

ine-identifier

ine-identifier

Syntax

ine-identifier identifier

no ine-identifier

Context

[Tree] (config>li>x-interfaces ine-identifier)

Full Context

configure li x-interfaces ine-identifier

Description

This command configures the Intercepting Network Element (INE).

The no form of this command reverts to the default.

Parameters

identifier

Specifies the INE name, up to 32 characters.

Platforms

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

info

info

Syntax

info [detail] [objective]

info [detail] [objective] operational

Context

[Tree] (info)

Full Context

info

Description

This command displays the running configuration for the configuration context where it is entered and all branches below that context level. It can be used in any branch under configure, but not with configure itself.

By default, the command only enters the configuration parameters that vary from the default values.

The detail keyword causes all configuration parameters to be displayed. The include-dynamic objective keyword includes configuration parameters from dynamic sources such as dynamic data services Python scripts. These dynamic configuration parameters are not saved in the configuration file.

The operational keyword is available in edit-cfg mode only, in which case the keyword is mandatory when using the info command.

Example:

A:ALA-48>config>router>if-attr# info
------------------------------------
            admin-group "green" value 15
            admin-group "red" value 25
            admin-group "yellow" value 20
A:ALA-48>config>router>mpls# info
------------------------------------
            interface "system"
            exit
            interface "to-104"
                admin-group "green"
                admin-group "red"
                admin-group "yellow"
                label-map 35
                    swap 36 nexthop 10.10.10.91
                    no shutdown
                exit
            exit
            path "secondary-path"
                hop 1 10.10.0.111  strict
                hop 2 10.10.0.222  strict
                hop 3 10.10.0.123  strict
                no shutdown
            exit
            path "to-NYC"
                hop 1 10.10.10.104  strict
                hop 2 10.10.0.210  strict
                no shutdown
            exit
            path "to-104"
                no shutdown
            exit
            lsp "to-104"
                to 10.10.10.104
                from 10.10.10.103
                rsvp-resv-style ff
                cspf
...
----------------------------------------------
A:ALA-48>config>router>mpls#
A:ALA-48>config>router>mpls# info detail
----------------------------------------------
            frr-object
            no resignal-timer
            interface "system"
                no admin-group
                no shutdown
            exit
            interface "to-104"
                admin-group "green"
                admin-group "red"
                admin-group "yellow"
                label-map 35
                    swap 36 nexthop 10.10.10.91
                    no shutdown
                exit
                no shutdown
            exit
            path "secondary-path"
                hop 1 10.10.0.111  strict
                hop 2 10.10.0.222  strict
                hop 3 10.10.0.123  strict
                no shutdown
            exit
            path "to-NYC"
                hop 1 10.10.10.104  strict
                hop 2 10.10.0.210  strict
                no shutdown
            exit
            path "to-104"
                no shutdown
            exit
            lsp "to-104"
                to 10.10.10.104
                from 10.10.10.103
                rsvp-resv-style ff
                adaptive
                cspf
                include "red"
                exclude "green"
                adspec
                fast-reroute one-to-one
                    no bandwidth
                    no hop-limit
                    node-protect
                exit
                hop-limit 10
                retry-limit 0
                retry-timer 30
                secondary "secondary-path"
                    no standby
                    no hop-limit
                    adaptive
                    no include
                    no exclude
                    record
                    record-label
                    bandwidth 50000
                    no shutdown
                exit
                primary "to-NYC"
                    hop-limit 50
                    adaptive
                    no include
                    no exclude
                    record
                    record-label
                    no bandwidth
                    no shutdown
                exit
                no shutdown
            exit
...
----------------------------------------------
A:ALA-48>config>router>mpls#

Parameters

detail

Displays all configuration parameters including parameters at their default values.

objective

Provides an output objective that controls the configuration parameters to be displayed.

Values

include-dynamic: includes configuration parameters from dynamic sources such as dynamic data services Python scripts.

info

Syntax

info

Context

[Tree] (debug>system>netconf info)

Full Context

debug system netconf info

Description

This command displays debug information for NETCONF sessions.

Platforms

All

Output

The following is an example of debug information for NETCONF sessions.

Sample Output
17 2018/03/17 12:29:54.785 UTC minor: DEBUG #2001 Base NETCONF
"NETCONF: INFO user: ncuser session 36: 
session started”

"18 2018/03/17 12:29:54.785 UTC minor: DEBUG #2001 Base NETCONF
NETCONF: INFO user: ncuser session 36: 
received <hello>”

19 2018/03/17 12:29:54.785 UTC minor: DEBUG #2001 Base NETCONF
"NETCONF: INFO user: ncuser session 36: setting 1.1 capability, chunk framing mode enabled”

20 2018/03/17 12:29:54.785 UTC minor: DEBUG #2001 Base NETCONF
"NETCONF: INFO user: ncuser session 36: 
successfully processed <hello> message”

21 2018/03/17 12:29:54.844 UTC minor: DEBUG #2001 Base NETCONF
"NETCONF: INFO user: ncuser session 36: 
received <edit-config>”

22 2018/03/17 12:29:54.848 UTC minor: DEBUG #2001 Base NETCONF
"NETCONF: INFO user: ncuser session 36: 
error occurred while processing <edit-config> RPC”

23 2018/03/17 12:29:54.892 UTC minor: DEBUG #2001 Base NETCONF
"NETCONF: INFO user: ncuser session 36: 
successfully processed <edit-config> RPC”

24 2018/03/17 12:29:54.893 UTC minor: DEBUG #2001 Base NETCONF
"NETCONF: INFO user: ncuser session 36: 
session terminated”

info-notification

info-notification

Syntax

info-notification

Context

[Tree] (config>port>ethernet>efm-oam>link-mon>local-sf-action info-notification)

Full Context

configure port ethernet efm-oam link-monitoring local-sf-action info-notification

Description

The context allows the operator to set different flags in the Information OAM PDU. The flags can be used to notify the peer that a local signal failure threshold has been exceeded within the configured window. This is useful when the local node supports the link monitoring function, but the remote peer does not support this capability. Information OAM PDUs are sent on the interval where the Event Notification OAM PDU is typically only sent on the initial sf-threshold crossing event. It is strongly suggested one of the Information OAM PDU Flag fields used to continually communicate current monitor state to the peer.

Interactions: The signal failure threshold will trigger these actions.

Platforms

All

ing-percentage-of-rate

ing-percentage-of-rate

Syntax

ing-percentage-of-rate ing-rate-percentage

no ing-percentage-of-rate

Context

[Tree] (config>port>modify-buffer-allocation-rate ing-percentage-of-rate)

Full Context

configure port modify-buffer-allocation-rate ing-percentage-of-rate

Description

This command increases or decreases the active bandwidth associated with the ingress port that affects the amount of ingress buffer space managed by the port. Changing a port’s active bandwidth using the ing-percentage-of-rate command is an effective means of artificially lowering the buffers managed by one ingress port and giving them to other ingress ports on the same MDA.

The ing-percentage-of-rate command accepts a percentage value that increases or decreases the active bandwidth based on the defined percentage. A value of 50% causes the active bandwidth to be reduced by 50%. A value of 150% causes the active bandwidth to be increased by 50%. Values from 1 to 1000 percent are supported.

A value of 100 (the default value) is equivalent to executing the no ing-percentage-of-rate command and restores the ingress active rate to the normal value.

The no form of this command removes any artificial increase or decrease of the ingress active bandwidth used for ingress buffer space allocation to the port. The no ing-percentage-of-rate command sets the ingress rate percentage to 100%.

Parameters

ing-rate-percentage

The ing-rate-percentage parameter is required and specifies the percentage value used to modify the current ingress active bandwidth of the port. This does not actually change the bandwidth available on the port in any way. The defined ing-rate-percentage parameter is multiplied by the ingress active bandwidth of the port. A value of 150 results in an increase of 50% (1.5 x Rate).

Values

1 to 1000

Default

100 (no change to active rate)

Platforms

All

ing-weight

ing-weight

Syntax

ing-weight access access-weight network network-weight

no ing-weight

Context

[Tree] (config>port>hybrid-buffer-allocation ing-weight)

Full Context

configure port hybrid-buffer-allocation ing-weight

Description

This command configures the sharing of the ingress buffers allocated to a hybrid port among the access and network contexts. By default, it is split equally between network and access.

The no form of this command reverts to the default values for the ingress access and network weights.

Parameters

access-weight

Specifies the access weight as an integer.

Values

0 to 100

Default

50

network-weight

Specifies the network weight as an integer.

Values

0 to 100

Default

50

Platforms

All

ingress

ingress

Syntax

ingress

Context

[Tree] (config>card>fp ingress)

Full Context

configure card fp ingress

Description

This command enables access to the ingress fp CLI context.

Platforms

All

ingress

Syntax

ingress

Context

[Tree] (config>subscr-mgmt>ancp>ancp-policy ingress)

Full Context

configure subscriber-mgmt ancp ancp-policy ingress

Description

Commands in this context configure ingress ANCP policy parameters.

Platforms

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

ingress

Syntax

ingress

Context

[Tree] (config>subscr-mgmt>msap-policy>ies-vprn ingress)

[Tree] (config>subscr-mgmt>msap-policy>vpls-only ingress)

Full Context

configure subscriber-mgmt msap-policy ies-vprn-only-sap-parameters ingress

configure subscriber-mgmt msap-policy vpls-only-sap-parameters ingress

Description

Commands in this context configure ingress policies for Managed SAPs (MSAPs).

Platforms

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

ingress

Syntax

ingress

Context

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

Full Context

configure subscriber-mgmt sla-profile ingress

Description

Commands in this context configure ingress parameters for the SLA profile.

Platforms

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

ingress

Syntax

ingress

Context

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

Full Context

configure service vprn subscriber-interface group-interface ingress

Description

Commands in this context configure ingress network filter parameters for the interface.

Platforms

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

ingress

Syntax

ingress

Context

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

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

Full Context

configure service vprn subscriber-interface group-interface sap ingress

configure service ies subscriber-interface group-interface sap ingress

Description

Commands in this context configure ingress SAP Quality of Service (QoS) policies and filter policies.

If no SAP ingress QoS policy is defined, the system default sap-ingress QoS policy is used for ingress processing. If no ingress filter is defined, no filtering is performed.

Platforms

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

ingress

Syntax

ingress

Context

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

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

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

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

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

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

Full Context

configure service ies interface spoke-sdp ingress

configure service vpls sap ingress

configure service ies interface sap ingress

configure service ies red-if spoke-sdp egress ingress

configure service vpls spoke-sdp ingress

configure service vpls mesh-sdp ingress

Description

Commands in this context configure ingress Quality of Service (QoS) policies and filter policies.

If no QoS policy is defined, the system default sap-ingress QoS policy is used for ingress processing. If no ingress filter is defined, no filtering is performed.

Platforms

All

ingress

Syntax

ingress

Context

[Tree] (config>port>access ingress)

[Tree] (config>card>mda>access ingress)

Full Context

configure port access ingress

configure card mda access ingress

Description

Commands in this context configure ingress buffer pool parameters which define the percentage of the pool buffers that are used for CBS calculations and specify the slope policy that is configured in the config>qos>slope-policy context.

On the MDA level, access ingress pools are only allocated on channelized MDAs.

Platforms

All

ingress

Syntax

ingress

Context

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

Full Context

configure port ethernet access ingress

Description

This command configures Ethernet access ingress port parameters.

Platforms

All

ingress

Syntax

ingress

Context

[Tree] (config>service>cpipe>sap ingress)

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

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

Full Context

configure service cpipe sap ingress

configure service ipipe sap ingress

configure service epipe sap ingress

Description

Commands in this context configure ingress SAP Quality of Service (QoS) policies.

If no sap-ingress QoS policy is defined, the system default sap-ingress QoS policy is used for ingress processing.

Platforms

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

  • configure service cpipe sap ingress

All

  • configure service ipipe sap ingress
  • configure service epipe sap ingress

ingress

Syntax

ingress

Context

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

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

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

Full Context

configure service cpipe spoke-sdp ingress

configure service ipipe spoke-sdp ingress

configure service epipe spoke-sdp ingress

Description

This command configures the ingress SDP context.

Platforms

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

  • configure service cpipe spoke-sdp ingress

All

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

ingress

Syntax

ingress

Context

[Tree] (config>service>template>epipe-sap-template ingress)

Full Context

configure service template epipe-sap-template ingress

Description

Commands in this context configure ingress SAP Quality of Service (QoS) policies and filter policies.

Platforms

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

ingress

Syntax

ingress

Context