c Commands – Part II

Context

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

Full Context

configure system security tls client-group-list

Description

This command configures a list of group suite codes that the client sends in a client Hello message.

The no form of this command removes the client group list.

Parameters

name

Specifies the name of the client group list, up to 32 characters.

create

Keyword used to create the client group list.

Platforms

All

Context

[Tree] (config>system>security>ssh client-host-key-list)

Full Context

configure system security ssh client-host-key-list

Description

Commands in this context configure the list of host key algorithms negotiated by the SR OS acting as the SSH client.

Platforms

All

Context

[Tree] (config>service>vprn>sub-if>grp-if>pppoe>dhcp-client client-id)

[Tree] (config>service>ies>sub-if>grp-if>pppoe>dhcp-client client-id)

Full Context

configure service vprn subscriber-interface group-interface pppoe dhcp-client client-id

configure service ies subscriber-interface group-interface pppoe dhcp-client client-id

Description

This command inserts a DHCP client identifier option 61 in DHCP client messages for PPPoE sessions that obtain IPv4 addresses from a third party DHCP server. By default, a DHCP client identifier option 61 is not included.

The no form of this command reverts to the default.

Default

no client-id

Parameters

mac-pppoe-session-id

Specifies that the DHCP client identifier option 61 contains a type value with type set to zero (1 octet) and value set to the PPPoE client MAC address (6 octets) and the PPPoE session ID (2 octets). For example:

Opt 61 (hex) = 00 00 10 94 A0 45 E5 00 01

where:

00 = type

00 10 94 A0 45 E5 = PPPoE client MAC address

00 01 = PPPoE session ID

Platforms

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

Context

[Tree] (config>ipsec>client-db>client client-identification)

Full Context

configure ipsec client-db client client-identification

Description

Commands in this context configure client ID information of this IPsec client.

If there are multiple match input are configured in the match-list of the client-db, then all corresponding match criteria must be configured for the client-entry.

Platforms

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

Context

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

Full Context

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

Description

This command configures debugging of a client IP.

Platforms

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

Context

[Tree] (config>system>security>ssh client-kex-list)

Full Context

configure system security ssh client-kex-list

Description

Commands in this context configure SSH KEX algorithms for SR OS as a client.

An empty list is the default list that the SSH KEX advertises. The default list contains the following:

ecdh-sha2-nistp512

ecdh-sha2-nistp384

ecdh-sha2-nistp256

diffie-hellman-group16-sha512

diffie-hellman-group14-sha256

diffie-hellman-group14-sha1

diffie-hellman-group-exchange-sha1

diffie-hellman-group1-sha1

Platforms

All

Context

[Tree] (config>service>vprn>sub-if>grp-if>dhcp>osel client-mac)

[Tree] (config>service>vprn>sub-if>dhcp>osel client-mac)

[Tree] (config>service>ies>sub-if>grp-if>dhcp>osel client-mac)

Full Context

configure service vprn subscriber-interface group-interface dhcp offer-selection client-mac

configure service vprn subscriber-interface dhcp offer-selection client-mac

configure service ies subscriber-interface group-interface dhcp offer-selection client-mac

Description

Commands in this context configure a delay for the Discover message from the designated client MAC addresses.

The no form of this command removes the client MAC configuration.

Parameters

odd

Specifies to use the odd client MAC address.

even

Specifies to use the even client MAC address.

Platforms

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

Context

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

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

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

Full Context

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

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

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

Description

Commands in this context configure a solicit delay or preference option value in function of the source MAC address of the solicit message.

The no form of this command removes the client MAC configuration.

Parameters

odd

Specifies to use the odd client MAC address.

even

Specifies to use the even client MAC address.

Platforms

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

Context

[Tree] (config>service>vprn>sub-if>grp-if>dhcp>option>vendor client-mac-address)

[Tree] (config>service>ies>if>dhcp>option>vendor client-mac-address)

[Tree] (config>service>vprn>if>dhcp>option>vendor client-mac-address)

[Tree] (config>service>ies>sub-if>grp-if>dhcp>option>vendor client-mac-address)

[Tree] (config>service>ies>sub-if>dhcp>option client-mac-address)

[Tree] (config>service>vpls>sap>dhcp>option>vendor client-mac-address)

[Tree] (config>subscr-mgmt>msap-policy>vpls-only>dhcp>option>vendor client-mac-address)

Full Context

configure service vprn subscriber-interface group-interface dhcp option vendor-specific-option client-mac-address

configure service ies interface dhcp option vendor-specific-option client-mac-address

configure service vprn interface dhcp option vendor-specific-option client-mac-address

configure service ies subscriber-interface group-interface dhcp option vendor-specific-option client-mac-address

configure service ies subscriber-interface dhcp option client-mac-address

configure service vpls sap dhcp option vendor-specific-option client-mac-address

configure subscriber-mgmt msap-policy vpls-only-sap-parameters dhcp option vendor-specific-option client-mac-address

Description

This command enables the sending of the MAC address in the Nokia vendor-specific sub-option of the DHCP relay packet.

The no form of this command disables the sending of the MAC address in the Nokia vendor-specific sub-option of the DHCP relay packet.

Platforms

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

• configure service ies subscriber-interface group-interface dhcp option vendor-specific-option client-mac-address
• configure service vprn subscriber-interface group-interface dhcp option vendor-specific-option client-mac-address
• configure subscriber-mgmt msap-policy vpls-only-sap-parameters dhcp option vendor-specific-option client-mac-address

All

• configure service vpls sap dhcp option vendor-specific-option client-mac-address
• configure service vprn interface dhcp option vendor-specific-option client-mac-address
• configure service ies interface dhcp option vendor-specific-option client-mac-address

Context

[Tree] (config>router>if>dhcp>option client-mac-address)

Full Context

configure router interface dhcp option client-mac-address

Description

This command enables the sending of the MAC address in the Nokia vendor specific suboption of the DHCP relay packet.

The no form of this command disables the sending of the MAC address in the Nokia vendor specific suboption of the DHCP relay packet.

Default

no client-mac-address

Platforms

All

Context

[Tree] (config>system>security>ssh client-mac-list)

Full Context

configure system security ssh client-mac-list

Description

Commands in this context configure SSH MAC algorithms for SR OS as a client.

Platforms

All

Context

[Tree] (config>port>ethernet>eth-cfm>mep>ais-enable client-meg-level)

[Tree] (config>lag>eth-cfm>mep>ais-enable client-meg-level)

Full Context

configure port ethernet eth-cfm mep ais-enable client-meg-level

configure lag eth-cfm mep ais-enable client-meg-level

Description

This command configures the client maintenance entity group (MEG) level(s) to use for AIS message generation. Up to 7 levels can be provisioned with the restriction that the client MEG level must be higher than the local MEG level. Only the lowest client MEG level will be used for facility MEPs.

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

Parameters

level

Specifies the client MEG level.

Values

1 to 7

Default

1

Platforms

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

Context

[Tree] (config>service>epipe>spoke-sdp>eth-cfm>ais-enable client-meg-level)

[Tree] (config>service>epipe>sap>eth-cfm>mep client-meg-level)

Full Context

configure service epipe spoke-sdp eth-cfm ais-enable client-meg-level

configure service epipe sap eth-cfm mep client-meg-level

Description

This command configures the client maintenance entity group (MEG) level or levels to use for AIS message generation. Up to 7 levels can be provisioned with the restriction that the client MEG level must be higher than the local MEG level.

Parameters

level

Specifies the client MEG level.

Values

1 to 7

Default

1

Platforms

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

Context

[Tree] (config>service>vpls>spoke-sdp>eth-cfm>mep>ais-enable client-meg-level)

[Tree] (config>service>vpls>mesh-sdp>eth-cfm>mep>ais-enable client-meg-level)

Full Context

configure service vpls spoke-sdp eth-cfm mep ais-enable client-meg-level

configure service vpls mesh-sdp eth-cfm mep ais-enable client-meg-level

Description

This command configures the client maintenance entity group (MEG) level(s) to use for AIS message generation. Up to 7 levels can be provisioned with the restriction that the client MEG level must be higher than the local MEG level.

Parameters

level

Specifies the client MEG level

Values

1 to 7

Default

1

Platforms

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

Context

[Tree] (config>ipsec>client-db>client client-name)

Full Context

configure ipsec client-db client client-name

Description

This command specifies the name of the client entry. The client name can be used in CLI navigation or in show commands.

Default

no client-name

Parameters

name

Specifies the name of the client.

Platforms

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

Context

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

Full Context

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

Description

This command configures debugging of a client port.

Platforms

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

Context

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

Full Context

configure system security tls client-signature-list

Description

This command configures a list of TLS 1.3-supported signature suite codes that the client sends in a client Hello message.

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

Parameters

name

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

create

Keyword used to create the client signature list.

Platforms

All

Context

[Tree] (config>system>security>pki>est-profile client-tls-profile)

Full Context

configure system security pki est-profile client-tls-profile

Description

This command configures the TLS client profile to be assigned to applications for encryption. The profile creates the TLS connection to the EST server.

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

Default

no client-tls-profile

Parameters

name

Specifies the name of the client TLS profile, up to 32 characters

Platforms

All

Context

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

Full Context

configure system security tls client-tls-profile

Description

This command configures the TLS client profile to be assigned to applications for encryption.

Parameters

name

Specifies the name of the client TLS profile, up to 32 characters in length.

create

Keyword used to create the client TLS profile.

Platforms

All

Context

[Tree] (config>system>management-interface>remote-management client-tls-profile)

Full Context

configure system management-interface remote-management client-tls-profile

Description

This command configures the TLS client profile used for encryption by all remote managers. This command and allow-unsecure-connection are mutually exclusive.

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

The no form of this command causes the profile configuration not to be used.

Parameters

name

Specifies the name of the client TLS profile, up to 32 characters.

Platforms

All

Context

[Tree] (config>system>management-interface>remote-management>manager client-tls-profile)

Full Context

configure system management-interface remote-management manager client-tls-profile

Description

This command configures the TLS client profile used for encryption by this remote manager. This command and allow-unsecure-connection are mutually exclusive.

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

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

Parameters

name

Specifies the name of the client TLS profile, up to 32 characters.

Platforms

All

Context

[Tree] (config>system clli-code)

Full Context

configure system clli-code

Description

This command creates a Common Language Location Identifier (CLLI) code string for the 7450 ESS, 7750 SR, 7950 XRS, and VSR router. A CLLI code is an 11-character standardized geographic identifier that uniquely identifies geographic locations and certain functional categories of equipment unique to the telecommunications industry.

No CLLI validity checks other than truncating or padding the string to eleven characters are performed.

Only one CLLI code can be configured, if multiple CLLI codes are configured the last one entered overwrites the previous entry.

The no form of the command removes the CLLI code.

Default

no clli-code

Parameters

clli-code

Specifies the 11 character string CLLI code. Any printable, seven bit ASCII characters can be used within the string. If the string contains special characters (#, ?, space), the entire string must be enclosed within double quotes. If more than 11 characters are entered, the string is truncated. If less than 11 characters are entered the string is padded with spaces.

Platforms

All

Context

[Tree] (config>oam-pm>session>meas-interval clock-offset)

Full Context

configure oam-pm session meas-interval clock-offset

Description

This command allows measurement intervals with a boundary-type of clock aligned to be offset from the default time of day clock. The configured offset must be smaller than the size of the measurement interval. As an example, an offset of 120 (seconds) shifts the start times of the measurement intervals by two minutes from their default alignments with respect to the time of day clock.

The no form of this command sets the offset to 0.

Default

clock-offset 0

Parameters

seconds

Specifies the number of seconds to offset a clock-alignment measurement interval from its default.

Values

0 to 86399

Default

0

Platforms

All

Context

[Tree] (config>port>sonet-sdh clock-source)

Full Context

configure port sonet-sdh clock-source

Description

This command configures the clock to be used for transmission of data out towards the line. The options are to use the locally recovered clock from the line's receive data stream or the node central reference.

When changing the clock source for a port on an OC-48 MDA, a brief transmit interruption can occur on all ports of that MDA. Note that all SONET/SDH MDAs support loop timing.

The node-timed parameter in this command is supported by TDM satellite.

Parameters

loop-timed

The link recovers the clock from the received data stream.

node-timed

The link uses the internal clock when transmitting data.

Platforms

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

Context

[Tree] (config>port>tdm>ds1 clock-source)

[Tree] (config>port>tdm>e1 clock-source)

[Tree] (config>port>tdm>e3 clock-source)

[Tree] (config>port>tdm>ds3 clock-source)

Full Context

configure port tdm ds1 clock-source

configure port tdm e1 clock-source

configure port tdm e3 clock-source

configure port tdm ds3 clock-source

Description

This command configures the clock to be used for transmission of data out towards the line. The options are to use the locally recovered clock from the line's receive data stream, the node central reference, or an adaptively recovered clock using the received packets.

The following table shows MDAs that support loop timing at DS3/E3 channelization options.

The following table shows MDAs that support loop timing at DS1/E1 channelization options.

Parameters

loop-timed

The link recovers the clock from the received data stream.

node-timed

The link uses the internal clock when transmitting data.

adaptive

The clock is adaptively recovered from the rate at which data is received and not from the physical layer. Adaptive timing is only supported on ds1 and e1 channels.

differential

The clock is recovered from differential RTP timestamp header. Differential timing is only supported on ds1 and e1 channels.

Platforms

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

Context

[Tree] (config>system>ptp clock-type)

Full Context

configure system ptp clock-type

Description

This command configures the type of clock. The clock type can only be changed when PTP is shutdown.

The clock type cannot be changed to ordinary timeTransmitter if the PTP reference is no shutdown. In addition, the clock type cannot be changed to ordinary timeTransmitter if there are peers configured. The clock type is restricted based on the profile. See the profile command description for the details of the restrictions.

When enabling a PTP with clock-type boundary, at least one reference into the central frequency clock must be enabled using the configure system sync-if-timing [bits |ref1 |ref2 | ptp| synce] command.

Default

clock-type ordinary slave

Parameters

boundary

Specifies that the system is a boundary clock, which may be anywhere in the PTP clock hierarchy. It can obtain timing from a timeTransmitter clock, and provide timing to multiple timeReceiver clocks concurrently.

ordinary master

Specifies that the system is a grandmaster clock in the PTP hierarchy. The system provides timing to multiple timeReceiver clocks in the network.

ordinary slave

Specifies that the system is always a timeReceiver clock in the PTP hierarchy. The system derives its timing from one or more timeTransmitter clocks in the network.

Platforms

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

Context

[Tree] (configure>system>security>profile>netconf>base-op-authorization close-session)

Full Context

configure system security profile netconf base-op-authorization close-session

Description

This command enables the NETCONF <close-session> RPC.

The no form of this command disables the RPC.

Default

no close-session

Platforms

All

Context

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

Full Context

configure subscriber-mgmt bgp-peering-policy cluster

Description

This command configures the cluster ID for a route reflector server.

Route reflectors are used to reduce the number of IBGP sessions required within an AS. Normally, all BGP speakers within an AS must have a BGP peering with every other BGP speaker in an AS. A route reflector and its clients form a cluster. Peers that are not part of the cluster are considered to be non-clients.

When a route reflector receives a route, first it must select the best path from all the paths received. If the route was received from a non-client peer, then the route reflector sends the route to all clients in the cluster. If the route came from a client peer, the route reflector sends the route to all non-client peers and to all client peers except the originator.

For redundancy, a cluster can have multiple route reflectors.

Confederations can also be used to remove the full IBGP mesh requirement within an AS.

The no form of this command deletes the cluster ID and effectively disables the Route Reflection for the given group.

Parameters

cluster-id

Specifies the route reflector cluster ID is expressed in dot decimal notation.

Values

Any 32 bit number in dot decimal notation. (0.0.0.1 to 255.255.255.255)

Platforms

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

Context

[Tree] (config>service>vprn>bgp>group cluster)

[Tree] (config>service>vprn>bgp>group>neighbor cluster)

[Tree] (config>service>vprn>bgp cluster)

Full Context

configure service vprn bgp group cluster

configure service vprn bgp group neighbor cluster

configure service vprn bgp cluster

Description

This command configures the cluster ID for a route reflector server.

Route reflectors are used to reduce the number of IBGP sessions required within an AS. Normally, all BGP speakers within an AS must have a BGP peering with every other BGP speaker in an AS. A route reflector and its clients form a cluster. Peers that are not part of the cluster are considered to be non-clients.

When a route reflector receives a route, first it must select the best path from all the paths received. If the route was received from a non-client peer, then the route reflector sends the route to all clients in the cluster. If the route came from a client peer, the route reflector sends the route to all non-client peers and to all client peers except the originator.

For redundancy, a cluster can have multiple route reflectors.

Confederations can also be used to remove the full IBGP mesh requirement within an AS.

The no form of this command deletes the cluster ID and effectively disables the Route Reflection for the given group.

Default

no cluster — No cluster ID is defined.

Parameters

cluster-id

The route reflector cluster ID is expressed in dot decimal notation.

Values

Any 32 bit number in dot decimal notation. (0.0.0.1 to 255.255.255.255)

Platforms

All

Context

[Tree] (config>router>bgp cluster)

Full Context

configure router bgp cluster

Description

This command configures the cluster ID for a route reflector server ID and implicitly configures the associated BGP sessions as route reflector clients of the BGP instance. If an ORR location ID is specified with the cluster ID, the clients in that cluster receive routes optimal for that specific location; refer to draft-ietf-idr-bgp-optimal-route-reflection for more information.

Route reflectors are used to reduce the number of IBGP sessions required within an AS. Normally, all BGP speakers within an AS must have a BGP peering with every other BGP speaker in an AS. A route reflector and its clients form a cluster. Peers that are not part of the cluster are considered to be non-clients.

When a route reflector receives best path from a non-client peer, it sends the route to all clients. When the route reflector receives a best path from a client peer it sends the route to all non-client and all client peers except the originator.

With optimal route reflection, the best path advertised to a client takes location ID into account, which means that if the tie-break for best path (or Add-Paths) comes down to next-hop IGP cost, the IGP costs will be calculated relative to the specified location. In the SR OS implementation, the IGP costs from arbitrary ORR locations are calculated using OSPF/OSPFv3, IS-IS, or BGP-LS information in the TE DB.

Default

no cluster

Parameters

ip-address

Specifies the route reflector cluster ID is expressed in dot decimal notation.

Values

Any 32 bit number in dot decimal notation. (0.0.0.1 to 255.255.255.255)

orr-location location-id

Specifies the optimal route reflection location index for this set of route reflector clients.

Values

1 to 255

allow-local-fallback

Controls the behavior when there are no BGP routes to advertise to the RR clients that are reachable from the perspective of their ORR location. If this option is configured, the RR is allowed (in this circumstance only), to advertise the best reachable BGP path from its own topology location. If this option is not configured and this situation applies, then no route is advertised to the clients.

Platforms

All

Context

[Tree] (config>router>bgp>group>neighbor cluster)

[Tree] (config>router>bgp>group cluster)

Full Context

configure router bgp group neighbor cluster

configure router bgp group cluster

Description

This command configures the cluster ID for a route reflector server ID and implicitly configures the associated BGP sessions as route reflector clients of the BGP instance. If an ORR location ID is specified with the cluster ID, the clients in that cluster receive routes optimal for that specific location; see draft-ietf-idr-bgp-optimal-route-reflection for more information.

Route reflectors are used to reduce the number of IBGP sessions required within an AS. Normally, all BGP speakers within an AS must have a BGP peering with every other BGP speaker in an AS. A route reflector and its clients form a cluster. Peers that are not part of the cluster are considered to be non-clients.

When a route reflector receives best path from a non-client peer, it sends the route to all clients. When the route reflector receives a best path from a client peer it sends the route to all non-client and all client peers except the originator.

With optimal route reflection, the best path advertised to a client takes location ID into account, which means that if the tie-break for best path (or Add-Paths) comes down to next-hop IGP cost, the IGP costs will be calculated relative to the specified location. In the SR OS implementation, the IGP costs from arbitrary ORR locations are calculated using OSPF/OSPFv3, IS-IS, or BGP-LS information in the TE DB.

The no form of this command deletes the cluster ID and effectively disables route reflection for the group.

Default

no cluster

Parameters

ip-address

Specifies the route reflector cluster ID is expressed in dot decimal notation.

Values

Any 32 bit number in dot decimal notation. (0.0.0.1 to 255.255.255.255)

orr-location location-id

Specifies the optimal route reflection location index for this set of route reflector clients.

Values

1 to 255

allow-local-fallback

Controls the behavior when there are no BGP routes to advertise to the RR clients that are reachable from the perspective of their ORR location. If this option is configured, the RR is allowed (in this circumstance only), to advertise the best reachable BGP path from its own topology location. If this option is not configured and this situation applies, then no route is advertised to the clients.

Platforms

All

Context

[Tree] (config>router>policy-options>policy-statement>entry>from cluster-id)

Full Context

configure router policy-options policy-statement entry from cluster-id

Description

This command enables BGP routes to be matched based on the IP addresses encoded in the CLUSTER_LIST attribute.

The first ip-address/mask pair is matched against the most recently added cluster ID. Each subsequent ip-address/mask pair is tested against the next most recent cluster ID.

For example, to match all routes reflected by the RR with cluster ID 1.1.1.1 and then any other RR before reaching the router where the policy is applied, use the command cluster-id 0.0.0.0/0 1.1.1.1/32.

The cluster-id none form of this command only matches BGP routes without any CLUSTER_LIST attribute.

A non-BGP route does not match a policy entry if it contains the cluster-id command.

Default

no cluster-id

Parameters

ip-address

Specifies the 32-bit cluster ID in dotted decimal notation.

Values

a.b.c.d

mask

Specifies a bit mask to apply to the ip-address parameter.

Values

0 to 32 (0 is only allowed if the ip-address is 0.0.0.0)

none

Specifies that only BGP routes without a CLUSTER_LIST attribute should be matched.

Platforms

All

Context

[Tree] (admin>certificate cmpv2)

Full Context

admin certificate cmpv2

Description

Commands in this context configure CMPv2 operations.

Platforms

All

Context

[Tree] (config>system>security>pki>ca-profile cmpv2)

Full Context

configure system security pki ca-profile cmpv2

Description

Commands in this context configure CMPv2 parameters.

Platforms

All

Context

[Tree] (debug>certificate cmpv2)

Full Context

debug certificate cmpv2

Description

This command enables debugging of CMPv2 operations.

Platforms

All

Context

[Tree] (config>system>security>pki>common-name-list cn)

Full Context

configure system security pki common-name-list cn

Description

This command creates a CN list entry in text or regexp format.

The no form of this command removes the specified entry.

Parameters

index

Specifies the index number of the entry.

type

Specifies the type of the entry.

Values

ip-address, domain-name

common-name-value

Specifies the IP address or domain name value, up to 255 characters maximum.

Platforms

All

Context

[Tree] (config>aaa>isa-radius-plcy>servers>server coa)

Full Context

configure aaa isa-radius-policy servers server coa

Description

This command configures Change of Authorization (CoA) messages.

Default

no coa

Parameters

udp-port

Specifies the UDP port number on which to contact the RADIUS server for authentication.

Values

1 to 65535

Platforms

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

Context

[Tree] (config>subscr-mgmt>auth-plcy coa-script-policy)

Full Context

configure subscriber-mgmt authentication-policy coa-script-policy

Description

This command configures the RADIUS script policy used to change the RADIUS attributes of the Change-of-Authorization messages.

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

Parameters

policy-name

Specifies the Python script policy to modify the Change-of-Authorization messages.

Platforms

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

Context

[Tree] (config>service>vprn>radius-server>server coa-script-policy)

[Tree] (config>router>radius-server>server coa-script-policy)

Full Context

configure service vprn radius-server server coa-script-policy

configure router radius-server server coa-script-policy

Description

This command specifies the RADIUS script policy to modify the Change-of-Authorization messages sent from this RADIUS server.

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

Parameters

policy-name

Specifies the name of radius-script-policy up to 80 characters.

Platforms

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

Context

[Tree] (config>port>ethernet>ssm code-type)

Full Context

configure port ethernet ssm code-type

Description

This command configures the encoding of synchronization status messages. For example, whether to use an SDH or SONET set of values. Configuring the network-type is only applicable to SyncE ports. It is not configurable on SONET/SDH ports. For the network-type, sdh refers to ITU-T G.781 Option I, while sonet refers to G.781 Option II (equivalent to Telcordia GR-253-CORE).

Default

code-type sdh

Parameters

sdh

Specifies the values used on a G.781 Option 1 compliant network.

sonet

Specifies the values used on a G.781 Option 2 compliant network.

Platforms

All

Context

[Tree] (config>port>dwdm coherent)

Full Context

configure port dwdm coherent

Description

This command configures the coherent optical module parameters.

Platforms

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

Context

[Tree] (config>log>app-route-notifications cold-start-wait)

Full Context

configure log app-route-notifications cold-start-wait

Description

The time delay that must pass before notifying specific CPM applications that a route is available after a cold reboot.

Default

no cold-start-wait

Parameters

seconds

Time delay in seconds.

Values

1 to 300

Platforms

All

Context

[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw>ranges>range>dsm collect-aa-acct-stats)

[Tree] (config>service>ies>sub-if>grp-if>wlan-gw>ranges>range>dsm collect-aa-acct-stats)

Full Context

configure service vprn subscriber-interface group-interface wlan-gw vlan-tag-ranges range distributed-sub-mgmt collect-aa-acct-stats

configure service ies subscriber-interface group-interface wlan-gw vlan-tag-ranges range distributed-sub-mgmt collect-aa-acct-stats

Description

This command enables Application Assurance account statistics collection.

Platforms

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

Context

[Tree] (config>service>epipe>sap>eth-cfm collect-lmm-fc-stats)

[Tree] (config>service>epipe>spoke-sdp>eth-cfm collect-lmm-fc-stats)

[Tree] (config>service>ipipe>sap>eth-cfm collect-lmm-fc-stats)

Full Context

configure service epipe sap eth-cfm collect-lmm-fc-stats

configure service epipe spoke-sdp eth-cfm collect-lmm-fc-stats

configure service ipipe sap eth-cfm collect-lmm-fc-stats

Description

Commands in this context configure per-forwarding class (FC) LMM information collection.

This command is mutually exclusive with the collect-lmm-stats command when there is entity resource contention.

Platforms

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

Context

[Tree] (config>service>vpls>sap>eth-cfm collect-lmm-fc-stats)

[Tree] (config>service>vpls>spoke-sdp>eth-cfm collect-lmm-fc-stats)

[Tree] (config>service>vpls>mesh-sdp>eth-cfm collect-lmm-fc-stats)

Full Context

configure service vpls sap eth-cfm collect-lmm-fc-stats

configure service vpls spoke-sdp eth-cfm collect-lmm-fc-stats

configure service vpls mesh-sdp eth-cfm collect-lmm-fc-stats

Description

Commands in this context configure per-forwarding class (FC) LMM information collection.

This command is mutually exclusive with the collect-lmm-stats command when there is entity resource contention.

Platforms

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

Context

[Tree] (config>service>ies>if>spoke-sdp>eth-cfm collect-lmm-fc-stats)

[Tree] (config>service>ies>sub-if>grp-if>sap>eth-cfm collect-lmm-fc-stats)

[Tree] (config>service>ies>if>sap>eth-cfm collect-lmm-fc-stats)

Full Context

configure service ies interface spoke-sdp eth-cfm collect-lmm-fc-stats

configure service ies subscriber-interface group-interface sap eth-cfm collect-lmm-fc-stats

configure service ies interface sap eth-cfm collect-lmm-fc-stats

Description

Commands in this context configure per-forwarding class (FC) LMM information collection.

This command is mutually exclusive with the collect-lmm-stats command when there is entity resource contention.

Platforms

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

• configure service ies interface sap eth-cfm collect-lmm-fc-stats
• configure service ies interface spoke-sdp eth-cfm collect-lmm-fc-stats

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

• configure service ies subscriber-interface group-interface sap eth-cfm collect-lmm-fc-stats

Context

[Tree] (config>service>vprn>if>sap>eth-cfm collect-lmm-fc-stats)

[Tree] (config>service>vprn>if>spoke-sdp>eth-cfm collect-lmm-fc-stats)

[Tree] (config>service>vprn>sub-if>grp-if>sap>eth-cfm collect-lmm-fc-stats)

Full Context

configure service vprn interface sap eth-cfm collect-lmm-fc-stats

configure service vprn interface spoke-sdp eth-cfm collect-lmm-fc-stats

configure service vprn subscriber-interface group-interface sap eth-cfm collect-lmm-fc-stats

Description

Commands in this context configure per-forwarding class (FC) LMM information collection.

This command is mutually exclusive with the collect-lmm-stats command when there is entity resource contention.

Platforms

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

• configure service vprn interface spoke-sdp eth-cfm collect-lmm-fc-stats
• configure service vprn interface sap eth-cfm collect-lmm-fc-stats

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

• configure service vprn subscriber-interface group-interface sap eth-cfm collect-lmm-fc-stats

Context

[Tree] (config>router>if>eth-cfm>mep collect-lmm-fc-stats)

Full Context

configure router interface eth-cfm mep collect-lmm-fc-stats

Description

This command enables the collection of per-forwarding class LMM statistics.

The collect-lmm-fc-stats and collect-lmm-stats commands are mutually exclusive when there is entity resource contention.

Platforms

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

Context

[Tree] (config>port>ethernet>eth-cfm>mep collect-lmm-stats)

[Tree] (config>router>if>eth-cfm>mep collect-lmm-stats)

[Tree] (config>lag>eth-cfm>mep collect-lmm-stats)

Full Context

configure port ethernet eth-cfm mep collect-lmm-stats

configure router interface eth-cfm mep collect-lmm-stats

configure lag eth-cfm mep collect-lmm-stats

Description

This command enables the collection of statistics on the facility MEPs. This command is an object under the Facility MEP. This is at a different level of the hierarchy than collection of lmm statistics for service SAPs and MPLS SDP Bindings. The show mep command can be used to determine is the Facility MEP is collecting stats.

The no form of this command disables and deletes the counters for this SAP, Binding or facility.

Default

no collect-lmm-stats

Platforms

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

Context

[Tree] (config>service>epipe>spoke-sdp>eth-cfm collect-lmm-stats)

[Tree] (config>service>epipe>sap>eth-cfm collect-lmm-stats)

[Tree] (config>service>ipipe>sap>eth-cfm collect-lmm-stats)

[Tree] (config>service>vpls>spoke-sdp>eth-cfm collect-lmm-stats)

[Tree] (config>service>vpls>sap>eth-cfm collect-lmm-stats)

[Tree] (config>service>vpls>mesh-sdp>eth-cfm collect-lmm-stats)

Full Context

configure service epipe spoke-sdp eth-cfm collect-lmm-stats

configure service epipe sap eth-cfm collect-lmm-stats

configure service ipipe sap eth-cfm collect-lmm-stats

configure service vpls spoke-sdp eth-cfm collect-lmm-stats

configure service vpls sap eth-cfm collect-lmm-stats

configure service vpls mesh-sdp eth-cfm collect-lmm-stats

Description

This command enables the collection of statistics on the SAP or MPLS SDP binding on which the ETH- LMM test is configured. The collection of LMM statistics must be enabled if a MEP is launching or responding to ETH-LMM packets. If LMM statistics collection is not enabled, the counters in the LMM and LMR PDU do not represent accurate measurements and all measurements should be ignored. The show sap-using eth-cfm collect-lmm-stats command and the show sdp-using eth-cfm collect-lmm-stats command can be used to display entities that are collecting stats.

The no form of this command disables and deletes the counters for this SAP or MPLS SDP binding.

Default

no collect-lmm-stats

Platforms

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

Context

[Tree] (config>service>ies>sub-if>grp-if>sap>eth-cfm collect-lmm-stats)

[Tree] (config>service>ies>if>sap>eth-cfm collect-lmm-stats)

[Tree] (config>service>ies>if>spoke-sdp>eth-cfm collect-lmm-stats)

Full Context

configure service ies subscriber-interface group-interface sap eth-cfm collect-lmm-stats

configure service ies interface sap eth-cfm collect-lmm-stats

configure service ies interface spoke-sdp eth-cfm collect-lmm-stats

Description

This command enables the collection of statistics on the SAP or MPLS SDP binding on which the ETH- LMM test is configured. The collection of LMM statistics must be enabled if a MEP is launching or responding to ETH-LMM packets. If LMM statistics collection is not enabled, the counters in the LMM and LMR PDU do not represent accurate measurements and all measurements should be ignored. The show sap-using eth-cfm collect-lmm-stats command and the show sdp-using eth-cfm collect-lmm-stats command can be used to display which entities are collecting stats.

The no form of this command disables and deletes the counters for this SAP or MPLS SDP binding.

Default

no collect-lmm-stats

Platforms

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

• configure service ies subscriber-interface group-interface sap eth-cfm collect-lmm-stats

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

• configure service ies interface spoke-sdp eth-cfm collect-lmm-stats
• configure service ies interface sap eth-cfm collect-lmm-stats

Context

[Tree] (config>service>vprn>sub-if>grp-if>sap>eth-cfm collect-lmm-stats)

[Tree] (config>service>vprn>if>sap>eth-cfm collect-lmm-stats)

[Tree] (config>service>vprn>if>spoke-sdp>eth-cfm collect-lmm-stats)

Full Context

configure service vprn subscriber-interface group-interface sap eth-cfm collect-lmm-stats

configure service vprn interface sap eth-cfm collect-lmm-stats

configure service vprn interface spoke-sdp eth-cfm collect-lmm-stats

Description

This command enables the collection of statistics on the SAP or MPLS SDP binding on which the ETH- LMM test is configured. The collection of LMM statistics must be enabled if a MEP is launching or responding to ETH-LMM packets. If LMM statistics collection is not enabled, the counters in the LMM and LMR PDU do not represent accurate measurements and all measurements should be ignored. The show>service>sap-using>eth-cfm>collect-lmm-stats command and the show>service>sdp-using>eth-cfm>collect-lmm-stats command can be used to display which entities are collecting stats.

The no form of this command disables and deletes the counters for this SAP or MPLS SDP binding.

Default

no collect-lmm-stats

Platforms

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

• configure service vprn subscriber-interface group-interface sap eth-cfm collect-lmm-stats

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

• configure service vprn interface spoke-sdp eth-cfm collect-lmm-stats
• configure service vprn interface sap eth-cfm collect-lmm-stats

Context

[Tree] (config>subscr-mgmt>sub-prof collect-stats)

Full Context

configure subscriber-mgmt sub-profile collect-stats

Description

When enabled, the agent collects non-RADIUS accounting statistics.

When the no collect-stats command is issued the statistics are still accumulated by the IOM cards. However, the CPU will not obtain the results and write them to the billing file. If a subsequent collect-stats command is issued then the counters written to the billing file include all the traffic while the no collect-stats command was in effect.

Default

collect-stats

Platforms

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

Context

[Tree] (config>service>vprn>sub-if>grp-if>sap collect-stats)

[Tree] (config>service>ies>sub-if>grp-if>sap collect-stats)

Full Context

configure service vprn subscriber-interface group-interface sap collect-stats

configure service ies subscriber-interface group-interface sap collect-stats

Description

When enabled, the agent collects non-RADIUS accounting statistics on a subscriber profile.

When the no collect-stats command is issued the statistics are still accumulated by the IOM cards. However, the CPU does not obtain the results and write them to the billing file. If a subsequent collect-stats command is issued then the counters written to the billing file include all the traffic.

Default

collect-stats

Platforms

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

Context

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

[Tree] (config>service>ies>if>sap collect-stats)

[Tree] (config>service>vpls>sap collect-stats)

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

Full Context

configure service vpls spoke-sdp collect-stats

configure service ies interface sap collect-stats

configure service vpls sap collect-stats

configure service vpls mesh-sdp collect-stats

Description

This command enables accounting and statistical data collection for either the SAP or SDP, network port, or IP interface. When applying accounting policies the data, by default, is collected in the appropriate records and written to the designated billing file.

When the no collect-stats command is issued the statistics are still accumulated by the IOM cards. However, the CPU does not obtain the results and write them to the billing file. If a subsequent collect-stats command is issued then the counters written to the billing file include all the traffic while the no collect-stats command was in effect.

Default

collect-stats

Platforms

All

Context

[Tree] (config>card>fp>ingress>access>queue-group collect-stats)

[Tree] (config>card>fp>ingress>network>queue-group collect-stats)

Full Context

configure card fp ingress access queue-group collect-stats

configure card fp ingress network queue-group collect-stats

Description

This command enables the collection of accounting and statistical data for the queue group on the forwarding plane. When applying accounting policies, the data, by default, is collected in the appropriate records and written to the designated billing file.

When the no collect-stats command is issued, the statistics are still accumulated, however, the CPU does not obtain the results and write them to the billing file. If the collect-stats command is issued again (enabled), then the counters written to the billing file will include the traffic collected while the no collect-stats command was in effect.

Default

no collect-stats

Platforms

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

Context

[Tree] (config>port>tdm>e3>network collect-stats)

[Tree] (config>port>tdm>e1>channel-group>network collect-stats)

[Tree] (config>port>sonet-sdh>path>network collect-stats)

[Tree] (config>port>tdm>ds1>channel-group>network collect-stats)

[Tree] (config>port>ethernet>access>ing>qgrp collect-stats)

[Tree] (config>port>ethernet>network collect-stats)

[Tree] (config>port>ethernet>network>egr>qgrp collect-stats)

[Tree] (config>port>tdm>ds3>network collect-stats)

[Tree] (config>port>ethernet>access>egr>qgrp collect-stats)

[Tree] (config>port>ethernet collect-stats)

Full Context

configure port tdm e3 network collect-stats

configure port tdm e1 channel-group network collect-stats

configure port sonet-sdh path network collect-stats

configure port tdm ds1 channel-group network collect-stats

configure port ethernet access ingress queue-group collect-stats

configure port ethernet network collect-stats

configure port ethernet network egress queue-group collect-stats

configure port tdm ds3 network collect-stats

configure port ethernet access egress queue-group collect-stats

configure port ethernet collect-stats

Description

This command enables the collection of accounting and statistical data for the network interface. When applying accounting policies, the data, by default, is collected in the appropriate records and written to the designated billing file.

When the no collect-stats command is issued, the statistics are still accumulated by the XCM/IOM cards, however, the CPU does not obtain the results and write them to the billing file. If the collect-stats command is issued again (enabled), then the counters written to the billing file will include the traffic collected while the no collect-stats command was in effect.

Default

no collect-stats

Platforms

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

• configure port tdm ds1 channel-group network collect-stats
• configure port tdm e3 network collect-stats
• configure port tdm ds3 network collect-stats
• configure port tdm e1 channel-group network collect-stats

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

• configure port sonet-sdh path network collect-stats

All

• configure port ethernet network egress queue-group collect-stats
• configure port ethernet access ingress queue-group collect-stats
• configure port ethernet access egress queue-group collect-stats
• configure port ethernet collect-stats
• configure port ethernet network collect-stats

Context

[Tree] (config>service>epipe>sap collect-stats)

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

[Tree] (config>service>ipipe>sap collect-stats)

[Tree] (config>service>cpipe>sap collect-stats)

Full Context

configure service epipe sap collect-stats

configure service epipe spoke-sdp collect-stats

configure service ipipe sap collect-stats

configure service cpipe sap collect-stats

Description

This command enables accounting and statistical data collection for either the SAP, network port, or IP interface. When applying accounting policies the data, by default, is collected in the appropriate records and written to the designated billing file.

When the no collect-stats command is issued the statistics are still accumulated by the cards. However, the CPU will not obtain the results and write them to the billing file. If a subsequent collect-stats command is issued, then the counters written to the billing file include all the traffic while the no collect-stats command was in effect.

Default

no collect-stats

Platforms

All

• configure service epipe spoke-sdp collect-stats
• configure service epipe sap collect-stats
• configure service ipipe sap collect-stats

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

• configure service cpipe sap collect-stats

Context

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

Full Context

configure service ies interface spoke-sdp collect-stats

Description

This command enables statistics collection.

Platforms

All

Context

[Tree] (config>service>vprn>if>sap collect-stats)

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

Full Context

configure service vprn interface sap collect-stats

configure service vprn interface spoke-sdp collect-stats

Description

This command enables accounting and statistical data collection for either an interface SAP or interface SAP spoke SDP, or network port. When applying accounting policies the data, by default, is collected in the appropriate records and written to the designated billing file.

When the no collect-stats command is issued the statistics are still accumulated by the IOM cards. However, the CPU will not obtain the results and write them to the billing file. If a subsequent collect-stats command is issued then the counters written to the billing file include all the traffic while the no collect-stats command was in effect.

Default

no collect-stats

Platforms

All

Context

[Tree] (config>router>ldp>egr-stats>fec-pfx collect-stats)

Full Context

configure router ldp egress-statistics fec-prefix collect-stats

Description

This command enables accounting and statistical data collection. When applying accounting policies the data, by default, is collected in the appropriate records and written to the designated billing file.

When the no collect-stats command is issued the statistics are still accumulated by the forwarding engine. However, the CPU does not obtain the results and write them to the billing file. If a subsequent collect-stats command is issued, the counters written to the billing file include all the traffic while the no collect-stats command was in effect.

Default

collect-stats

Platforms

All

Context

[Tree] (config>router>mpls>ingr-stats>p2mp-template-lsp collect-stats)

[Tree] (config>router>mpls>ingr-stats>lsp collect-stats)

[Tree] (config>router>mpls>lsp>ingr-stats collect-stats)

[Tree] (config>router>mpls>ingr-stats>p2p-template-lsp collect-stats)

[Tree] (config>router>mpls>lsp-template>egr-stats collect-stats)

[Tree] (config>router>mpls>lsp>egr-stats collect-stats)

Full Context

configure router mpls ingress-statistics p2mp-template-lsp collect-stats

configure router mpls ingress-statistics lsp collect-stats

configure router mpls lsp ingress-statistics collect-stats

configure router mpls ingress-statistics p2p-template-lsp collect-stats

configure router mpls lsp-template egress-statistics collect-stats

configure router mpls lsp egress-statistics collect-stats

Description

This command enables accounting and statistical data collection. When applying accounting policies the data, by default, is collected in the appropriate records and written to the designated billing file.

The config>router>mpls>ingr-stats>p2mp-template-lsp>collect-stats command is supported on the 7750 SR, 7950 XRS, and with VPLS only on the 7450 ESS.

When the no collect-stats command is issued, the statistics are still accumulated by the forwarding engine. However, the CPU does not write the results to the billing file. If a subsequent collect-stats command is issued, the counters written to the billing file include all the traffic collected while the no collect-stats command was in effect.

Default

collect-stats

Platforms

All

• configure router mpls ingress-statistics p2mp-template-lsp collect-stats
• configure router mpls lsp egress-statistics collect-stats
• configure router mpls lsp-template egress-statistics collect-stats
• configure router mpls ingress-statistics p2p-template-lsp collect-stats
• configure router mpls ingress-statistics lsp collect-stats

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

• configure router mpls lsp ingress-statistics collect-stats

Context

[Tree] (config>app-assure>group>statistics>aa-part collect-stats)

[Tree] (config>app-assure>group>statistics>app-grp collect-stats)

[Tree] (config>app-assure>group>statistics>aa-admit-deny collect-stats)

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

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

[Tree] (config>app-assure>group>statistics>app collect-stats)

[Tree] (config>app-assure>group>statistics>protocol collect-stats)

[Tree] (config>isa>aa-grp>statistics>perform collect-stats)

Full Context

configure application-assurance group statistics aa-partition collect-stats

configure application-assurance group statistics app-group collect-stats

configure application-assurance group statistics aa-admit-deny collect-stats

configure application-assurance group statistics aa-sub-study collect-stats

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

configure application-assurance group statistics application collect-stats

configure application-assurance group statistics protocol collect-stats

configure isa application-assurance-group statistics performance collect-stats

Description

This command enables statistic collection within the applicable context.

Default

no collect-stats

Platforms

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

Context

[Tree] (config>service>pw-template collect-stats)

[Tree] (config>service>sdp collect-stats)

Full Context

configure service pw-template collect-stats

configure service sdp collect-stats

Description

This command enables accounting and statistical data collection for either the SDP. When applying accounting policies the data, by default, is collected in the appropriate records and written to the designated billing file.

When the no collect-stats command is issued the statistics are still accumulated by the IOM or XCM cards. However, the CPU will not obtain the results and write them to the billing file. If a subsequent collect-stats command is issued then the counters written to the billing file include all the traffic while the no collect-stats command was in effect.

Default

no collect-stats

Platforms

All

Context

[Tree] (conf>router>segment-routing>sr-policies>egress-stats collect-stats)

Full Context

configure router segment-routing sr-policies egress-statistics collect-stats

Description

This command enables statistics collection via the accounting policy.

The no form of this command disables the collection of statistics via the accounting policy.

Default

no collect-stats

Platforms

All

Context

[Tree] (config>log>acct-policy collection-interval)

Full Context

configure log accounting-policy collection-interval

Description

This command configures the accounting collection interval.

Parameters

minutes

Specifies the interval between collections, in minutes.

Values

1 to 120 A range of 1 to 4 is only allowed when the record type is set to SAA.

Platforms

All

Context

[Tree] (config>app-assure>group>cflowd collector)

Full Context

configure application-assurance group cflowd collector

Description

This command defines a flow data collector for cflowd data. The IP address of the flow collector must be specified. The UDP port number is an optional parameter. If it is not set, the default of 2055 is used.

Parameters

ip-address

Specifies the IP address of the flow data collector in dotted decimal notation.

port

Specifies the UDP port of flow data collector.

Values

1 to 65535

Default

2055

create

Keyword used to create the flow data collector.

Platforms

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

Context

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

Full Context

configure service ipfix ipfix-export-policy collector

Description

This command defines an external collector node that will collect IPFIX records sent by 7750 SR node. The IPFIX records will be streamed to the collector node using UDP transport. Traffic is originated from a random ephemeral UDP port to the destination port 4739. Up to two collector nodes can be defined for redundancy purposes.

UDP streams are stateless due to the significant volume of transactions. However they do contain 32bit sequence numbers such that packet loss can be identified.

Multiple IPFIX records are sent in a single UDP packet. UDP packet transmission is triggered when the packet size containing IPFIX records exceeds the configured MTU value or the internal timer which is set to 250ms, whichever occurs first.

Parameters

router router-instance

Router instance from which the collector node is reachable.

Values

<router-name> | <service-id>
router-name:	"Base"
service-id:	1 to 2147483647

ip ip-address

IPv4 address of the external collector node to which IPFIX records will be sent.

create

Keyword used to create the collector instance.

Platforms

All

Context

[Tree] (config>service>nat>syslog>syslog-export-policy collector)

Full Context

configure service nat syslog syslog-export-policy collector

Description

This command defines an external collector node that collects syslog records. The syslog records are streamed to the collector node using UDP transport. Traffic is originated from a random ephemeral UDP port to the destination port 514. Up to two collector nodes can be defined for redundancy purposes.

Stateless UDP streams are used as transport due to the significant volume of transactions. However, they do contain 32-bit sequence numbers so packet loss can be identified. The sequence numbers are generated per BB-ISA per collector, and within each stream they are monotonically increased by 1. Overlapping sequence numbers between BB-ISAs can be differentiated by the MDA ID field carried in the syslog message.

Multiple syslog records are sent in a single UDP packet. UDP packet transmission is triggered when the packet size containing syslog records exceeds the configured MTU value or the configurable timer, whichever occurs first.

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

Parameters

router-name

Specifies the router instances from which the collector node is reachable.

ip-address

Specifies the IPv4 address of the external collector node to which the syslog records are sent.

service-name

Specifies the service name from which the collector node is reachable.

create

Keyword used to create the collector instance.

Platforms

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

Context

[Tree] (config>cflowd collector)

Full Context

configure cflowd collector

Description

This command defines a flow data collector for cflowd data. The IP address and version of the flow collector must be specified. The UDP port number is an optional parameter. If it is not set, the default of 2055 is used for all collector versions. To connect to an IPFIX (version 10) collector using the IPFIX default port, specify port 4739 when defining the collector. A maximum of eight collectors can be configured.

The no form of this command removes the flow collector definition from the config and stops the export of data to the collector. The collector needs to be shut down to be deleted.

Parameters

ip-address

Specifies the address of a remote cflowd collector host to receive the exported cflowd data.

Values

ipv4-address	a.b.c.d
ipv6-address	x:x:x:x:x:x:x:x-[interface]

port

Specifies the UDP port number on the remote cflowd collector host to receive the exported cflowd data.

Values

1 to 65535

Default

2055

version

Specifies the version of the flow data collector.

Values

5, 8, 9, 10

Default

5

Platforms

All

Context

[Tree] (config>app-assure>group>cflowd>direct-export collector)

Full Context

configure application-assurance group cflowd direct-export collector

Description

This command configures the Cflowd direct export collector.

The system uses the collectors when the Cflowd admin state shuts down and then re-enabled (no shutdown state). The system re-assigns the collectors to the groups or AA-ISAs or when a Cflowd collector ID is created. The collector IDs are used when a new group is added later.

When a collector ID is removed, the groups (AA-ISAs) that are assigned to this collector are removed and assigned to another available collector. The affected ISAs reset their collector statistics as they change to the new collector.

In addition, a Cflowd collector assignment to a group or AA-ISA is done only in the following conditions:

• the admin state is in a no shutdown state for the AA group or the AA group Cflowd

• a collector is available under the AA group with at least one address in a no shutdown admin state

If an AA group or AA-ISA is assigned a collector, shutting down, or the group unassigns the group from the cflowd collector.

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

Parameters

collector-id

Specifies the Cflowd direct export collector ID.

Values

1 to 65535

Platforms

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

Context

[Tree] (conf>router>segment-routing>sr-policies>policy color)

Full Context

configure router segment-routing sr-policies static-policy color

Description

This command associates a color value with a statically defined segment routing policy. This is a mandatory parameter and configuration command to enable the segment routing policy; if the color parameter value is not configured, the execution of the no shutdown command on the static segment routing policy fails.

The no form of this command removes the color association.

Default

no color

Parameters

color

Specifies the color ID.

Values

0 to 4294967295

Platforms

All

Context

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

Full Context

configure router policy-options policy-statement entry from color

Description

This command configures an SR Policy color ID as a route policy match criterion.

This match criterion is only used in import policies.

The no form of this command removes the configuration.

Parameters

color-id

Specifies the SR policy color ID.

Values

0 to 4294967295

Platforms

All

Context

[Tree] (config>oam-pm>session>ip>tunnel>mpls>sr-policy color)

Full Context

configure oam-pm session ip tunnel mpls sr-policy color

Description

This command configures the color for associating the SR policy with an objective.

Default

color 0

Parameters

color-id

Specifies the color ID.

Values

0 to 4294967295

Default

0

Platforms

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

Context

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

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

Full Context

configure system security profile combined-max-sessions

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

Description

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

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

Default

no combined-max-sessions

Parameters

number-of-sessions

Specifies the maximum number of allowed combined SSH/TELNET based sessions.

Values

0 to 50

Platforms

All

Context

[Tree] (config>system>security>management-interface>md-cli command-accounting-during-load)

Full Context

configure system security management-interface md-cli command-accounting-during-load

Description

This command controls command accounting performed on the contents of a file loaded using the MD-CLI load or rollback command.

When enabled, all commands in the loaded file are logged, which may decrease the system response time with large files.

When disabled, command accounting is not performed during a load or rollback operation, which may increase the system response time by reducing the number of command accounting messages, especially when remote AAA servers are used.

The load or rollback command itself is always logged.

The no form of this command disables command accounting during a load or rollback operation.

Default

command-accounting-during-load

Platforms

All

Context

[Tree] (config>system>management-interface>cli>md-cli>environment command-completion)

Full Context

configure system management-interface cli md-cli environment command-completion

Description

This command configures keystrokes to trigger command completion.

Platforms

All

Context

[Tree] (config>app-assure>group>ip-id-asst>pdns>trst-srv comment)

Full Context

configure application-assurance group ip-identification-assist passive-dns trusted-server comment

Description

This command specifies a name or description to associate with the DNS server.

The no form of this command removes the name or description given to the DNS server.

Parameters

comment-string

Specifies a name or description, up to 32 characters.

Platforms

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

Context

[Tree] (config>system>management-interface>cli>md-cli>environment>commit-options comment)

Full Context

configure system management-interface cli md-cli environment commit-options comment

Description

This command configures the requirement for a commit comment when committing configuration.

The no form of this command does not require a commit comment when committing configuration

Default

no comment

Platforms

All

Context

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

Full Context

configure application-assurance group policy commit

Description

This command commits changes made during the current editing session. None of the policy changes done will take effect until commit command is issued. If the changes can be successfully committed, no errors detected during the commit during cross-reference verification against exiting application assurance configuration, the editing session will also be closed.

The newly committed policy takes effect immediately for all new flows, existing flows will transition onto the new policy shortly after the commit.

Platforms

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

Context

[Tree] (config>router>bfd commit)

Full Context

configure router bfd commit

Description

This command saves the changes made to a BFD template during an active session and makes the changes active.

Platforms

All

Context

[Tree] (config>router>route-next-hop-policy commit)

Full Context

configure router route-next-hop-policy commit

Description

This command saves the changes made to route next-hop templates during an active session.

Default

commit

Platforms

All

Context

[Tree] (candidate commit)

Full Context

candidate commit

Description

This command applies the changes in the candidate configuration to the active running configuration. The candidate changes will take operational effect.

If a commit operation is successful then all of the candidate changes will take operational effect and the candidate is cleared. If there is an error in the processing of the commit, or a 'commit confirmed’ is not confirmed and an auto-revert occurs, then the router will return to a configuration state with none of the candidate changes applied. The operator can then continue editing the candidate and try a commit later.

By default, the SR OS will automatically create a new rollback checkpoint after a commit operation. The rollback checkpoint will contain the new configuration changes made by the commit. An optional no-checkpoint keyword can be used to avoid the auto-creation of a rollback checkpoint after a commit.

A commit operation is blocked if a rollback revert is currently being processed.

Parameters

confirmed

specifies that the commit operation (if successful) should be automatically reverted (undone) at the end of the timeout period unless the operator issues the confirm command before the timeout period expires. A rollback checkpoint is created after the commit operation (if successful) and will remain available whether the commit is auto-reverted or not. The contents of the candidate will remain visible (candidate view) and changes to the candidate are blocked until the timeout is completed or the candidate confirm command is executed. If the timeout expires and an auto-revert occurs, then the original candidate config will be available in edit-cfg mode.

Standard line-by-line non-transactional configuration commands (including via SNMP) are not blocked during the countdown period and any changes made to the configuration during the countdown period will be rolled back if the timeout expires. The confirmed option is useful when changes are being made that could impact management reachability to the router.

A rollback revert is blocked during the countdown period until the commit has been confirmed.

timeout

Specifies the auto-revert timeout period, in minutes.

Values

1 to 168

no-checkpoint

Specifies to avoid the automatic creation of a rollback checkpoint for a successful commit.

comment comment

Adds a comment up to 255 characters to the automatic rollback checkpoint.

Platforms

All

Context

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

Full Context

configure system sync-if-timing commit

Description

This command saves changes made to the system synchronous interface timing configuration.

Platforms

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

Context

[Tree] (config>router>policy-options commit)

Full Context

configure router policy-options commit

Description

This command is required to save changes made to a route policy.

Platforms

All

Context

[Tree] (configure>system>security>profile>netconf>base-op-authorization commit)

Full Context

configure system security profile netconf base-op-authorization commit

Description

This command enables the NETCONF <commit> RPC.

The no form of this command disables the RPC.

Default

no commit

Platforms

All

Context

[Tree] (config>system>management-interface>cli>md-cli>environment commit-options)

Full Context

configure system management-interface cli md-cli environment commit-options

Description

Commands in this context configure commit options.

Platforms

All

Context

[Tree] (config>system>security>pki common-name-list)

Full Context

configure system security pki common-name-list

Description

This command configures a list of common names (CNs) that will be used to authenticate X.509.3 certificates. If the CN field of the X.509.3 certificate matches any of the CNs in the list, then the certificate can be used.

Parameters

name

Specifies the name of the CN list, up to 32 characters maximum.

Platforms

All

Context

[Tree] (config>service>vprn>snmp community)

Full Context

configure service vprn snmp community

Description

This command sets the SNMP community name(s) to be used with the associated VPRN instance. These VPRN community names are used to associate SNMP v1/v2c requests with a particular vprn context and to return a reply that contains VPRN-specific data or limit SNMP access to data in a specific VPRN instance.

VPRN snmp communities configured with an access permission of 'r' are automatically associated with the default access group "snmp-vprn-ro” and the "vprn-view” view (read only). VPRN snmp communities configured with an access permission of 'rw' are automatically associated with the default access group "snmp-vprn” and the "vprn-view” view (read/write).

The community in an SNMP v1/v2 request determines the SNMP context (i.e., the vprn# for accessing SNMP tables) and not the VPRN of the incoming interface on which the request was received. When an SNMP request arrives on VPRN 5 interface "ringo” with a destination IP address equal to the "ringo” interface, but the community in the SNMP request is the community configured against VPRN 101, then the SNMP request will be processed using the VPRN 101 context. (the response will contain information about VPRN 101). It is recommended to avoid using a simple series of vprn snmp-community values that are similar to each other (for example, avoid my-vprncomm-1, my-vprn-comm-2, etc).

The no form of this command removes the SNMP community name from the given VPRN context.

Parameters

community-name

Specifies the SNMP v1/v2c community name. This is a secret/confidential key used to access SNMP and specify a context (base vs vprn1 vs vprn2).

hash

Specifies the key is entered in an encrypted form. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.

hash2

Specifies the key is entered in a more complex encrypted form that involves more variables than the key value alone, meaning that the hash2 encrypted variable cannot be copied and pasted. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.

custom

Specifies the custom encryption to management interface.

version SNMP-version

Specifies the SNMP version.

Values

v1, v2c, both

access-permissions

Specifies the access rights to MIB objects.

Values

r — Grants only read access to MIB objects. Creates an association of the community-name with the snmp-vprn-ro access group.rw — Grants read and write access to MIB objects. Creates an association of the community-name with the snmp-vprn access group.

list-name

Configures the community to reference a specific src-access-list (created under configure system security snmp), which will be used to validate the source IP address of all received SNMP requests that use this community. Multiple community (vprn or base router) and usm-community instances can reference the same src-access-list.

Platforms

All

Context

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

Full Context

configure service vprn static-route-entry community

Description

This command associates a list of up to 12 BGP communities (any mix of standard, extended, and large communities) with the static route. These communities can be matched in route policies and are automatically added to BGP routes that are created from the static route.

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

The no form of this command removes the association.

Default

no community

Parameters

comm-id

Specifies a BGP community value, up to 72 characters.

Values

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

where:

• as-num — 0 to 65535

• comm-val — 0 to 65535

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

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

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

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

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

  • bandwidth:asnum:val-in-mbps

  • ext:4300:ovstate

  • ext:value1:value2

  • color:co-bits:color-value

  where:

  • target — route target

  • origin — route origin

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

  • ext-comm-val — 0 to 4294967295

  • ext-asnum — 0 to 4294967295

  • val-in-mbps — 0 to 16777215

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

  • value1 — 0000 to FFFF

  • value2 — 0 to FFFFFFFFFFFF

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

  • color-value — 0 to 4294967295

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

Platforms

All

Context

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

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

[Tree] (config>service>vprn>static-route-entry>black-hole community)

Full Context

configure service vprn static-route-entry indirect community

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

configure service vprn static-route-entry black-hole community

Description

This command associates one BGP community (standard, extended or large) with a next-hop of the static route. This community can be matched in route policies and automatically added to BGP routes that are created from the static route.

Any community specified in one of these contexts is overridden by any communities specified at the prefix level of the static route entry.

The no form of this command removes the association.

Default

no community

Parameters

comm-id

Specifies a BGP community value, up to 72 characters.

Values

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

where:

• as-num — 0 to 65535

• comm-val — 0 to 65535

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

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

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

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

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

  • bandwidth:asnum:val-in-mbps

  • ext:4300:ovstate

  • ext:value1:value2

  • color:co-bits:color-value

  where:

  • target — route target

  • origin — route origin

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

  • ext-comm-val — 0 to 4294967295

  • ext-asnum — 0 to 4294967295

  • val-in-mbps — 0 to 16777215

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

  • value1 — 0000 to FFFF

  • value2 — 0 to FFFFFFFFFFFF

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

  • color-value — 0 to 4294967295

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

Platforms

All

Context

[Tree] (config>service>vprn>static-route-entry>ipsec-tunnel community)

Full Context

configure service vprn static-route-entry ipsec-tunnel community

Description

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

The no form of this command removes the community association.

Default

no community

Parameters

comm-id

Specifies community IDs, up to 72 characters.

Values

[2 byte asnumber:comm-val | well-known-comm]

where:

• 2 byte as-number — 0 to 65535

• comm-val — 0 to 65535

• well-known-comm — no-export | no-export-subconfed | no-advertise

Platforms

All

Context

[Tree] (config>router>ldp>targeted-session>peer-template community)

[Tree] (config>router>ldp>session-params>peer community)

Full Context

configure router ldp targeted-session peer-template community

configure router ldp session-parameters peer community

Description

This command configures a community name associated with a targeted session to a specified peer. The community is a local configuration for a targeted session. FECs received over a session of a given community are taken to belong to that community, and are redistributed over sessions of the same community.

The SR OS router uses the following rules for community:

• If both the session parameters for a specified peer and targeted peer template that is applied to session have the default configuration then no community applies.

• If the session parameters for a peer have the default configuration, but targeted session peer template has an explicit configuration for community, then the targeted peer template configuration will be used.

• If the session parameters have an explicit configuration for community, and the targeted session peer template has the default configuration, then the session parameter configuration applies.

• If both session parameters and targeted peer template have an explicit configuration for community, then the session parameter configuration is used.

The no form of this command removes the community from the session to the peer. FEC subsequently received over the session are treated as having no community.

Default

no community

Parameters

community-name

Specifies the string defining the LDP community assigned to the session. 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.

Platforms

All

Context

[Tree] (config>router>static-route-entry>black-hole community)

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

[Tree] (config>router>static-route-entry>indirect community)

Full Context

configure router static-route-entry black-hole community

configure router static-route-entry next-hop community

configure router static-route-entry indirect community

Description

This command associates one BGP community (standard, extended or large) with a next-hop of the static route. This community can be matched in route policies and automatically added to BGP routes that are created from the static route.

Any community specified in one of these contexts is overridden by any communities specified at the prefix level of the static route entry.

The no form of this command removes the association.

Default

no community

Parameters

comm-id

Specifies a BGP community value, up to 72 characters.

Values

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

where:

• as-num — 0 to 65535

• comm-val — 0 to 65535

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

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

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

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

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

  • bandwidth:asnum:val-in-mbps

  • ext:4300:ovstate

  • ext:value1:value2

  • color:co-bits:color-value

  where:

  • target — route target

  • origin — route origin

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

  • ext-comm-val — 0 to 4294967295

  • ext-asnum — 0 to 4294967295

  • val-in-mbps — 0 to 16777215

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

  • value1 — 0000 to FFFF

  • value2 — 0 to FFFFFFFFFFFF

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

  • color-value — 0 to 4294967295

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

Platforms

All

Context

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

Full Context

configure router static-route-entry community

Description

This command associates a list of up to 12 BGP communities (any mix of standard, extended, and large communities) with the static route. These communities can be matched in route policies and are automatically added to BGP routes that are created from the static route.

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

The no form of this command removes the association.

Default

no community

Parameters

comm-id

Specifies a BGP community value, up to 72 characters.

Values

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

where:

• as-num — 0 to 65535

• comm-val — 0 to 65535

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

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

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

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

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

  • bandwidth:asnum:val-in-mbps

  • ext:4300:ovstate

  • ext:value1:value2

  • color:co-bits:color-value

  where:

  • target — route target

  • origin — route origin

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

  • ext-comm-val — 0 to 4294967295

  • ext-asnum — 0 to 4294967295

  • val-in-mbps — 0 to 16777215

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

  • value1 — 0000 to FFFF

  • value2 — 0 to FFFFFFFFFFFF

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

  • color-value — 0 to 4294967295

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

Platforms

All

Context

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

Full Context

configure system security snmp community

Description

This command creates SNMP community strings for SNMPv1 and SNMPv2c access. This command is used in combination with the predefined access groups and views. To create custom access groups and views and associate them with SNMPv1 or SNMPv2c access use the usm-community command.

When configured, community implies a security model for SNMPv1 and SNMPv2c only.

For SNMPv3 security, the access group command must be configured.

The no form of the command removes the specified community string.

Parameters

community-string

Configures the SNMPv1 and/or SNMPv2c community string.

Values

community-string — Specifies the community string. Allowed values are any string up to 32 characters, composed of printable, 7-bit ASCII characters. If the string contains special characters (for example, #, $, spaces), the entire string must be enclosed within double quotes.

hash-key — Up to 33 characters

hash2-key — Up to 96 characters

hash

Specifies the key is entered in an encrypted form. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.

hash2

Specifies the key is entered in a more complex encrypted form that involves more variables than the key value alone, meaning that the hash2 encrypted variable cannot be copied and pasted. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.

custom

Specifies the custom encryption to management interface.

access-permissions

Configures the access permissions for objects in the MIB.

r — Grants only read access to objects in the MIB, except security objects, using the internal "snmp-ro" access group and the "no-security" snmp view.

rw — Grants read and write access to all objects in the MIB, using the internal "snmp-rw" access group and the "no-security" snmp view.

rwa — Grants read and write access to all objects in the MIB, including security, using the internal snmp-rwa access group and the iso snmp view.

mgmt — Assigns a unique SNMP community string for SNMP access via the management router instance. This community uses the internal snmp-mgmt access group and the mgmt snmp view.

vpls-mgmt — Assigns a unique SNMP community string for SNMP access via the vpls-management router instance. This community uses the internal snmp-vpls-mgmt access group and mgmt-view snmp view.

version {v1 | v2c | both}

Configures the scope of the community string to be for SNMPv1, SNMPv2c, or both SNMPv1 and SNMPv2c access.

Default

both

list-name

Configures the community to reference a specific src-access-list, which will be used to validate the source IP address of all received SNMP requests that use this community. Multiple community, usm-community, or VPRN SNMP community instances can reference the same src-access-list.

Platforms

All

Context

[Tree] (config>router>policy-options community)

Full Context

configure router policy-options community

Description

This command creates a route policy community list or expression to use in route policy entries. A community list is an unordered set of community values (members). In general a route matches a community list if it has any of the member values. A community expression is a set of community values that are arranged in a logical expression using operators such as AND, OR, and NOT. A route matches a community expression if it satisfies the logic of the expression.

For additional information, see the expression and members commands in the config> router>policy-options>community context.

The no form of this command deletes the community list or the provided community ID.

Default

no community

Parameters

name

Specifies the community list name. Allowed values are any string up to 64 characters, composed of printable, 7-bit ASCII characters. If the string contains special characters (for example, #, $, spaces), the entire string must be enclosed within double quotes.

Platforms

All

Context

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

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

Full Context

configure router policy-options policy-statement default-action community

configure router policy-options policy-statement entry action community

Description

This command adds or removes a BGP community list to or from routes matching the route policy statement entry.

If no community list is specified, the community path attribute is not changed.

The community list changes the community path attribute according to the add and remove keywords.

The no form of this command disables the action to edit the community path attribute for the route policy entry.

Default

no community

Parameters

name

Specifies up to 28 names.

add

The specified community list is added to any existing list of communities.

remove

The specified community list is removed from the existing list of communities.

replace

The specified community list replaces any existing community attribute. name — The community list name. Allowed values are any string up to 64 characters, composed of printable, 7-bit ASCII characters. If the string contains special characters (#, ?, space), the entire string must be enclosed within double quotes. Policy parameters must be enclosed by at-signs (@) and may be midstring; for example, "@variable@," "start@variable@end"," @variable@end", or "start@variable@".

Platforms

All

Context

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

Full Context

configure router policy-options policy-statement entry from community

Description

This command configures a community list as a match criterion for the route policy entry.

If no community list is specified, any community is considered a match.

The no form of this command removes the community list match criterion.

Default

no community

Parameters

comm-name

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

expression

Specifies that the parameters are applied to routes matching the entry.

Values

expression is one of the following, up to 900 characters:

<expression> {AND| OR} <expression>

[NOT] ( <expression> )

[NOT] "["<comm-name> "]

The following are examples of valid logical expressions:

• "[community_list_A] OR ([community_list_B] AND [community_list_C])"
• "NOT [community_list_A]”
• "[community_list_A] AND [community_list_B] OR [community_list_C]”
• "NOT ([community_list_A] OR [community_list_B] OR [community_list_C])”

Platforms

All

Context

[Tree] (config>router>policy-options>policy-statement>entry>from community-count)

Full Context

configure router policy-options policy-statement entry from community-count

Description

This command matches BGP routes based on community length (that is, the number of community members in the COMMUNITY, EXTENDED_COMMUNITY, or LARGE_COMMUNITY the attributes).

If no comparison qualifiers are present (equal, or-higher, or-lower), then equal is the implied default.

Without the optional standard, extended, or large keyword, the community length applies to the total number of communities, of all types. If some keywords are present, then only the types specified are counted against the limit.

A non-BGP route does not match a policy entry if it contains the community-count command.

Default

no community-count

Parameters

count

Specifies the number of community members.

Values

0 to 1024, or a parameter, up to 32 characters, name delimited by a starting and ending at-sign (@) character

equal

Specifies that matched routes should have the same number of AS path elements as the value specified.

or-higher

Specifies that matched routes should have the same or a greater number of community members as the value specified.

or-lower

Specifies that matched routes should have the same or a lower number of community members as the value specified.

standard

Specifies that only communities in the COMMUNITY attribute should be counted.

extended

Specifies that only communities in the EXTENDED_COMMUNITY attribute should be counted.

large

Specifies that only communities in the LARGE_COMMUNITY attribute should be counted.

Platforms

All

Context

[Tree] (admin compare)

Full Context

admin compare

Description

This command displays the differences between rollback checkpoints and the active operational configuration, with source1 as the base/first file to which source2 is compared.

A compare operation does not check authorization of each line of output. Permission to execute the compare operation from the admin branch of CLI (authorization for the admin rollback compare or admin compare command itself) should only be given to users who are allowed to view the entire configuration, similar to permissions for admin display-config.

Default

The defaults for source1 and source2 are context aware and differ based on the branch in which the command is executed. In general, the default for source1 matches the context from which the command is issued.

• In the admin node: No defaults. source1 and source2 must be specified.

• In the admin>rollback node:

  source1 default = active-cfg, source2 default = latest-rb

  compare: equivalent to "compare active-cfg to latest-rb”

  compare to source2: equivalent to "compare active-cfg to source2”

• In a config>xx node:

  compare to source2: equivalent to "compare active-cfg to source2”

Parameters

source1, source2

Specifies comparison information.

Values

active-cfg — The current operational configuration that is active in the node.

latest-rb — The most recent rollback checkpoint (the checkpoint file at the configured rollback-location with "*.rb” as the suffix).

rescue — The rescue configuration (at the configured rescue-location).

checkpoint-id — An ID indicating a specific rollback checkpoint. A checkpoint-id of 1 indicates the rollback checkpoint file (at the configured rollback-location) with "*.rb.1” as the suffix, 2 for file "*.rb.2”, and so on.

Platforms

All

Context

[Tree] (admin>rollback compare)

Full Context

admin rollback compare

Description

This command can be used in any branch under configure, but not with configure itself. The command syntax, parameter names, and default values are context aware and will differ based on the branch in which the command is executed.

This command displays the differences between rollback checkpoints and the active operational configuration, with checkpoint1 as the base/first file to which checkpoint2 is compared. This command displays the comparison for the configuration context where it is entered and all branches below that context level.

A compare operation does not check authorization of each line of output. Permission to execute the compare operation from the admin branch of CLI (authorization for the admin rollback compare or admin compare command itself) should only be given to users who are allowed to view the entire configuration, similar to permissions for admin display-config.

Default

The defaults for checkpoint1 and checkpoint2 are context-aware and differ based on the branch in which the command is executed. In general, the default for checkpoint1 matches the context from which the command is issued.

• In the admin node: No defaults. checkpoint1 and checkpoint2 must be specified.

• In the admin>rollback node:

  checkpoint1 default = active-cfg, checkpoint2 default = latest-rb

  compare: equivalent to "compare active-cfg to latest-rb”

  compare to checkpoint2: equivalent to "compare active-cfg to checkpoint2”

• In a config>xx node:

  compare to checkpoint2: equivalent to "compare active-cfg to checkpoint2”

Parameters

checkpoint1, checkpoint2

Specifies comparison information.

Values

active-cfg — The current operational configuration that is active in the node.

latest-rb — The most recent rollback checkpoint (the checkpoint file at the configured rollback-location with "*.rb” as the suffix).

rescue — The rescue configuration (at the configured rescue-location).

checkpoint-id — An ID indicating a specific rollback checkpoint. A checkpoint-id of 1 indicates the rollback checkpoint file (at the configured rollback-location) with "*.rb.1” as the suffix, 2 for file "*.rb.2”, and so on.

Platforms

All

Context

[Tree] (config>ipsec>cert-profile>entry compare-chain-include)

Full Context

configure ipsec cert-profile entry compare-chain-include

Description

This command configures the Certificate Authority (CA) profile that needs to be included in the compare-chain for the entry. This configuration is required in instances where there are multiple overlapping compare-chains, for example, the configured root CA is cross-signed by another CA.

Default

no compare-chain-include

Parameters

ca-profile-name

Specifies the name of the CA profile.

Platforms

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

Context

[Tree] (config>service>vprn>bgp>best-path-selection compare-origin-validation-state)

Full Context

configure service vprn bgp best-path-selection compare-origin-validation-state

Description

This command enables the comparison of origin validation states during the BGP decision process. When this command is configured, a new step is inserted in the BGP decision process after the removal of invalid routes and before the comparison of Local Preference. This step compares the origin validation state so a BGP route with a "Valid” state is preferred over a BGP route with a "Not-Found” state. A BGP route with a "Not-Found” state is preferred over a BGP route with an "Invalid” state assuming that these routes are considered "usable”.

This comparison only applies to BGP routes learned from VPRN BGP peers. It does not apply to any comparison involving BGP-VPN routes that have been imported into the VPRN.

The no form of this command causes the new step to be skipped during the BGP decision process.

Default

no compare-origin-validation-state

Platforms

All

Context

[Tree] (config>router>bgp>best-path-selection compare-origin-validation-state)

Full Context

configure router bgp best-path-selection compare-origin-validation-state

Description

When this command is configured, a new step is inserted in the BGP decision process after removal of invalid routes and before the comparison of Local Preference. The new step compares the RPKI origin validation state so that a BGP route with a 'Valid’ state is preferred over a BGP route with a 'Not-Found’ state, and a BGP route with a 'Not-Found’ state is preferred over a BGP route with an 'Invalid’ state assuming that these routes are considered 'usable’.

The new step is skipped when no compare-origin-validation-state is configured.

Default

no compare-origin-validation-state

Platforms

All

Context

[Tree] (config>port>dwdm>coherent compatibility)

Full Context

configure port dwdm coherent compatibility

Description

This command configures the optical mode and rate of operation.

Parameters

mode

Specifies the optical mode.

Values

long-haul - The port operates in the native long-haul mode.

long-haul-non-diff - The port operates in the native long-haul mode using non-differential encoding.

metro - The port operates in the native metro regional mode.

access - The port operates in the native access mode (80km reach).

interop - The port operates in the third party interop mode.

interop2 - The port operates in the third party interop mode with alternate differential encoding.

interop3 - The port operates in the CFP2-DCO Rev A0 Staircase FEC interop mode.

oif-400g-zr - The port operates in compliance with the OIF 400G ZR implementation agreement (IA). This parameter is only supported for use with 400G ZR and 400G ZR+ pluggable transceiver modules.

open-zrp-ofec1 - The port operates in compliance with the OpenZR+ multi-source agreement (MSA) (100GHz spacing). This parameter is only supported for use with 400G ZR and 400G ZR+ pluggable transceiver modules.

open-zrp-ofec2 - The port operates in compliance with the OpenZR+ MSA (75 GHz spacing). This parameter is only supported for use with 400G ZR and 400G ZR+ pluggable transceiver modules.

Default

long-haul

Platforms

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

Context

[Tree] (config>service>vprn>ospf compatible-rfc1583)

Full Context

configure service vprn ospf compatible-rfc1583

Description

This command enables OSPF summary and external route calculations in compliance with RFC 1583 and earlier RFCs.

RFC 1583 and earlier RFCs use a different method to calculate summary and external route costs. To avoid routing loops, all routers in an OSPF domain should perform the same calculation method.

Although it would be favorable to require all routers to run a more current compliance level, this command allows the router to use obsolete methods of calculation.

This command is not supported in OSPF3.

The no form of this command enables the post-RFC 1583 method of summary and external route calculation.

Default

compatible-rfc1583 — RFC 1583 compliance is enabled.

Platforms

All

Context

[Tree] (config>router>ospf compatible-rfc1583)

Full Context

configure router ospf compatible-rfc1583

Description

This command enables OSPF summary and external route calculations in compliance with RFC 1583 and earlier RFCs.

RFC 1583 and earlier RFCs use a different method to calculate summary and external route costs. To avoid routing loops, all routers in an OSPF domain should perform the same calculation method.

Although it would be favorable to require all routers to run a more current compliance level, this command allows the router to use obsolete methods of calculation.

The no form of this command enables the post-RFC 1583 method of summary and external route calculation.

Default

compatible-rfc1583

Platforms

All

Context

[Tree] (config>eth-ring compatible-version)

Full Context

configure eth-ring compatible-version

Description

This command configures eth-ring compatibility version for the G.8032 state machine and messages. The default is version 2 and all router switches use this version. If there is a need to interwork with third party devices that only support version 1 this can be set to version 1.

The no form of this command set the compatibility version to 2.

Default

compatible-version 2

Parameters

version

Specifies the version of the G.8032 state machine.

Values

1, 2

Platforms

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

Context

[Tree] (config>system>security>password complexity-rules)

Full Context

configure system security password complexity-rules

Description

This command defines a list of rules for configurable password options.

Platforms

All

Context

[Tree] (config>app-assure>group>cflowd comprehensive)

Full Context

configure application-assurance group cflowd comprehensive

Description

Commands in this context configure cflowd comprehensive statistics output parameters.

Platforms

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

Context

[Tree] (config>router>policy-options>policy-statement>entry conditional-expression)

Full Context

configure router policy-options policy-statement entry conditional-expression

Description

This command creates the context to configure a route existence expression.

Platforms

All

Context

[Tree] (config>service>vprn confederation)

Full Context

configure service vprn confederation

Description

This command configures the VPRN BGP instance to participate in a BGP confederation. BGP confederations can be used to reduce the number of IBGP sessions required within an AS.

When a VPRN BGP instance is part of a confederation, it can form confederation-EBGP sessions with CE router peers in a different sub-autonomous systems of the same confederation as well as regular EBGP sessions with CE router peers outside the confederation. A VPRN BGP instance that is part of a confederation cannot import or export its routes to the base router instance (as VPN-IP routes).

The no form of this command deletes the specified member AS from the confederation. When members are not specified in the no statement, the entire list is removed and confederations is disabled. When the last member of the list is removed, confederations is disabled.

Default

no confederation

Parameters

confed-as-num

The confederation AS number defined as a decimal value.

Values

1 to 4294967295

members as-number

The AS number(s) that are members of the confederation, each expressed as a decimal integer. Configure up to 15 members per confed-as-num.

Values

1 to 4294967295

Platforms

All

Context

[Tree] (config>router confederation)

Full Context

configure router confederation

Description

This command creates confederation autonomous systems within an AS.

This technique is used to reduce the number of IBGP sessions required within an AS. Route reflection is another technique that is commonly deployed to reduce the number of IBGP sessions.

The no form of this command deletes the specified member AS from the confederation.

When no members are specified in the no statement, the entire list is removed and confederation is disabled.

When the last member of the list is removed, confederation is disabled.

Default

no confederation - no confederations are defined.

Parameters

confed-as-num

Specifies the confederation AS number expressed as a decimal integer.

Values

1 to 65535

as-number

Specifies the AS number of members that are part of the confederation, expressed as a decimal integer. Up to 15 members per confed-as-num can be configured.

Values

1 to 65535

Platforms

All

Context

[Tree] (config>app-assure>group>policy>charging-filter>entry>match>flow-attribute confidence)

[Tree] (config>app-assure>group>policy>aqp>entry>match>flow-attribute confidence)

Full Context

configure application-assurance group policy charging-filter entry match flow-attribute confidence

configure application-assurance group policy app-qos-policy entry match flow-attribute confidence

Description

This command configures the confidence level of the flow attribute for use as match criteria.

Parameters

eq equal-value

Specifies that a successful match occurs when the flow attribute confidence level is equal to the specified value.

Values

0 to 100

gte greater-than-or-equal-value

Specifies that a successful match occurs when the flow attribute confidence level is greater than or equal to the specified value.

Values

0 to 100

lt less-than-value

Specifies that a successful match occurs when the flow attribute confidence level is less than the specified value.

Values

1 to 100

Platforms

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

Context

[Tree] (config>system config-backup)

Full Context

configure system config-backup

Description

This command configures the maximum number of backup versions maintained for configuration files and BOF.

For example, assume the config-backup count is set to 5 and the configuration file is called xyz.cfg. When the configuration is saved, the file xyz.cfg is saved with a 1 extension. Each configuration save increments the numeric extension until the maximum count is reached.

xyz.cfg xyz.cfg.1 xyz.cfg.2 xyz.cfg.3 xyz.cfg.4 xyz.cfg.5

Each classic CLI persistent index file is updated at the same time as the associated configuration file. When the index file is updated, then the save is performed to xyz.cfg and the index file is created as xyz.ndx. Synchronization between the active and standby CPM is performed for all configurations and their associated persistent index files.

The no form of the command returns the configuration to the default value.

Default

config-backup 50

Parameters

count

Specifies the maximum number of backup revisions.

Values

1 to 200

Platforms

All

Context

[Tree] (config>system>management-interface configuration-mode)

Full Context

configure system management-interface configuration-mode

Description

This command controls which management interfaces are used for editing and changing the configuration of the router.

Any management interface can be used in any configuration mode (to gather state information or perform operations, for example), but only specific management interfaces (CLI, NETCONF, and so on) are allowed to edit the configuration of the router in different modes. For example, only classic CLI and SNMP can be used to edit the configuration when in classic mode.

Default

configuration-mode model-driven

Parameters

classic

Enables editing of router configuration via classic CLI and SNMP management interfaces, but not using model-driven interfaces.

model-driven

Enables editing of router configuration via model-driven management interfaces (NETCONF with 'Nokia' YANG models, MD-CLI or gRPC), but not using classic interfaces.

mixed

Enables editing of router configuration using a mix of classic CLI and/or model-driven management interfaces (with some restrictions and limitations).

Platforms

All

Context

[Tree] (configure)

Full Context

configure

Description

Commands in this context edit the system configuration.

Platforms

All

Context

[Tree] (candidate confirm)

Full Context

candidate confirm

Description

This command is used to stop an automatic reversion to the previous configuration after the candidate commit confirmed command was used. If the confirm command is not executed before the commit confirmed timeout period expires then the previous commit changes will be undone and the previous candidate configuration will be available for editing and a subsequent commit.

During the countdown the contents of the candidate will remain visible (candidate view) and changes to the candidate are blocked until the timeout is completed or the candidate confirm command is executed. Executing the confirm command clears the contents of the candidate and allows editing of the candidate.

Platforms

All

Context

[Tree] (config>system>management-interface>cli>md-cli>environment>commit-options confirm)

Full Context

configure system management-interface cli md-cli environment commit-options confirm

Description

This command configures the requirement for a confirmed commit when committing configuration.

The no form of this command does not require a confirmed commit when committing configuration

Default

no confirm

Platforms

All

Context

[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle cong-priority-threshold)

Full Context

configure mcast-management multicast-info-policy bundle cong-priority-threshold

Description

This command defines the preference level threshold where records change from low congestion priority to high congestion priority. Congestion priority is used by the ingress multicast path queues to map packets entering the queue to either the low drop-tail or the MBS drop-tail threshold. If congestion occurs on the queue, the queue depth increases. As the queue depth increases beyond the low drop-tail, packets with low priority congestion priority are discarded. This leaves room in the queue for packets with high congestion priority until the queue reaches the MBS threshold.

The default congestion priority threshold is 4. This means that multicast channels with a preference level of 0 to 3 are treated as having low congestion priority and channels with preference level of 4 to 7 are treated as having a high congestion priority. The cong-priority-threshold command can be used to change the default threshold. Any multicast channel with a preference equal to or higher than the configured threshold is treated with high congestion priority.

The cong-priority-threshold value is also used by the multicast CAC manager to derive the class of a channel matched by the multicast information policy. Channels with a preference less than the configured threshold are treated as low class and channels with a preference equal to or greater than the threshold is treated as high class.

Changing the cong-priority-threshold value causes all channels congestion priority to be reevaluated. Both the ingress multicast path managers and multicast CAC managers must be updated.

The no form of this command restores the default congestion priority preference threshold value.

Default

cong-priority-threshold 4

Parameters

preference-level

Specifies the cong-priority-threshold where records change from low congestion priority to high congestion priority.

Values

0 to 7

Platforms

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

Context

[Tree] (config>app-assure>group>policer congestion-override)

Full Context

configure application-assurance group policer congestion-override

Description

Commands in this context configure per subscriber congestion bandwidth policer override rates.

Platforms

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

Context

[Tree] (config>app-assure>group>policer congestion-override-stage2)

Full Context

configure application-assurance group policer congestion-override-stage2

Description

Commands in this context configure per-subscriber stage 2 congestion bandwidth policer override rates.

Platforms

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

Context

[Tree] (config>qos>hw-agg-shap-sched-plcy congestion-threshold)

Full Context

configure qos hw-agg-shaper-scheduler-policy congestion-threshold

Description

This command configures the congestion threshold for the hardware aggregate shaper scheduler policy, which, if exceeded, triggers the hardware aggregate scheduler algorithm.

Default

congestion-threshold 90

Parameters

percent

Specifies the congestion threshold as a percentage of the scheduler rate.

Values

0 to 100

Platforms

7750 SR-1, 7750 SR-s

Context

[Tree] (config>subscr-mgmt>bgp-prng-plcy connect-retry)

Full Context

configure subscriber-mgmt bgp-peering-policy connect-retry

Description

This command configures the BGP connect retry timer value in seconds.

When this timer expires, BGP tries to reconnect to the configured peer.

The no form of this command used at the global level reverts to the default value.

Default

connect-retry 120

Parameters

seconds

The BGP Connect Retry timer value in seconds, expressed as a decimal integer.

Values

1 to 65535

Platforms

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

Context

[Tree] (config>service>vprn>bgp>group>neighbor connect-retry)

[Tree] (config>service>vprn>bgp connect-retry)

[Tree] (config>service>vprn>bgp>group connect-retry)

Full Context

configure service vprn bgp group neighbor connect-retry

configure service vprn bgp connect-retry

configure service vprn bgp group connect-retry

Description

This command configures the BGP connect retry timer value in seconds.

When this timer expires, BGP tries to reconnect to the configured peer. This configuration parameter can be set at three levels: global level (applies to all peers), peer-group level (applies to all peers in group) or neighbor level (only applies to specified peer). The most specific value is used.

The no form of this command used at the global level reverts to the default value.

The no form of this command used at the group level reverts to the value defined at the global level.

The no form of this command used at the neighbor level reverts to the value defined at the group level.

Default

120 seconds

Parameters

seconds

Specifies the BGP connect retry timer value in seconds, expressed as a decimal integer.

Values

1 to 65535

Platforms

All

Context

[Tree] (config>router>origin-validation>rpki-session connect-retry)

Full Context

configure router origin-validation rpki-session connect-retry

Description

This command configures the time in seconds to wait between one TCP connection attempt that fails and the next attempt. The default (with no connect-retry) is 120 seconds.

Default

no connect-retry

Parameters

seconds

Specifies time in seconds.

Values

1 to 65535

Platforms

All

Context

[Tree] (config>router>bgp>group connect-retry)

[Tree] (config>router>bgp connect-retry)

[Tree] (config>router>bgp>group>neighbor connect-retry)

Full Context

configure router bgp group connect-retry

configure router bgp connect-retry

configure router bgp group neighbor connect-retry

Description

This command configures the BGP connect retry timer value in seconds.

When this timer expires, BGP tries to reconnect to the configured peer. This configuration parameter can be set at three levels: global level (applies to all peers), peer-group level (applies to all peers in group) or neighbor level (only applies to specified peer). The most specific value is used.

The no form of this command used at the global level reverts to the default value.

The no form of this command used at the group level reverts to the value defined at the global level.

The no form of this command used at the neighbor level reverts to the value defined at the group level.

Default

connect-retry 120

Parameters

seconds

The BGP Connect Retry timer value in seconds expressed as a decimal integer.

Values

1 to 65535

Platforms

All

Context

[Tree] (config>bmp>station>connection connect-retry)

Full Context

configure bmp station connection connect-retry

Description

This command configures the BMP connect retry timer value. When this timer expires, BMP tries to reconnect to the configured monitoring station. This timer is applicable when the connection to the monitoring station is not yet established.

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

Default

connect-retry 120

Parameters

seconds

Specifies the BMP connect retry timer in seconds.

Values

1 to 65535

Platforms

All

Context

[Tree] (config>bmp>station connection)

Full Context

configure bmp station connection

Description

Commands in this context configure connection parameters for the BMP monitoring station.

Platforms

All

Context

[Tree] (debug>router>pcep>pcc connection)

Full Context

debug router pcep pcc connection

Description

This command debugs PCC connection events.

The no form of this command disables debugging.

Parameters

ip-address

Specifies the IP address.

Values

ipv4-prefix: a.b.c.d

ipv6-prefix:

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

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

• x: [0 to FFFF] H

• d: [0 to 255] D

Platforms

All

Context

[Tree] (debug>router>pcep>pce connection)

Full Context

debug router pcep pce connection

Description

This command debugs PCE connection events.

The no form of this command disables debugging.

Parameters

ip-address

Specifies the IP address.

Values

ipv4-prefix: a.b.c.d

ipv6-prefix:

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

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

• x: [0 to FFFF] H

• d: [0 to 255] D

Platforms

VSR-NRC

Context

[Tree] (config connection-profile-vlan)

Full Context

configure connection-profile-vlan

Description

Commands in this context configure the VLAN ranges that will be associated with a service SAP.

Each connection-profile-vlan must be explicitly configured.

Parameters

conn-prof-id

Specifies the connection-profile identifier. This value will be configured in the service along with the SAP when the user associates a VLAN bundle to a single SAP. For example, a SAP defined in a dot1q port 1/1/1 that matches all the VLANs defined in the connection-profile-vlan 1 will be created as 'sap 1/1/1:cp-1 create'.

Values

1 to 8000

Platforms

All

Context

[Tree] (config>system>management-interface>remote-management connection-timeout)

Full Context

configure system management-interface remote-management connection-timeout

Description

This command configures the amount of time that all remote managers cannot be reached before they are considered to be down.

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

The no form of this command reverts to the default.

Default

connection-timeout 60

Parameters

seconds

Specifies the connection timeout in seconds.

Values

1 to 3600

Platforms

All

Context

[Tree] (config>system>management-interface>remote-management>manager connection-timeout)

Full Context

configure system management-interface remote-management manager connection-timeout

Description

This command configures the amount of time that this remote manager cannot be reached before it is considered to be down.

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

The no form of this command reverts to the default.

Default

connection-timeout 60

Parameters

seconds

Specifies the connection timeout in seconds.

Values

1 to 3600

Platforms

All

Context

[Tree] (config>aaa>diam>node>peer connection-timer)

[Tree] (config>aaa>diam>node connection-timer)

Full Context

configure aaa diameter node peer connection-timer

configure aaa diameter node connection-timer

Description

This command configures the Diameter node connection timer that defines the time the systems waits before attempting to reconnect to a peer after the connection was lost.

The no form of this command reverts to the default.

Default

connection-timer 30

Parameters

seconds

Specifies the Diameter node connection timer.

Values

1 to 1000

Platforms

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

Context

[Tree] (config>macsec connectivity-association)

Full Context

configure macsec connectivity-association

Description

This command configures a connectivity association. MACsec connectivity associations are applied to a port dot1x configuration to enable MACsec on that port.

The no form of this command removes the connectivity association.

Parameters

ca-name

The name of the connectivity association, a string up to 32 characters long.

create

Mandatory while creating an entry.

Platforms

All

Context

[Tree] (config>subscr-mgmt>vrgw>brg>brg-profile connectivity-verification)

Full Context

configure subscriber-mgmt vrgw brg brg-profile connectivity-verification

Description

This command configures the BRG connectivity verification. The system uses ICMP Echo request messages for connectivity verification.

When the last host associated with a BRG is removed, a ping mechanism is used to verify if the BRG is still active. This command specifies the parameters used in this mechanism.

The no form of this command disables the BRG ping mechanism and removes the BRG without verification. Any configured hold time still applies.

Default

connectivity-verification count 3 timeout 30 retry-time 900

Parameters

nr-of-attempts

Specifies the number of connectivity verification attempts this system makes before a BRG is considered down.

Values

1 to 5

timeout-seconds

Specifies the time, in seconds, after which an unanswered ping is considered failed.

Values

5 to 60

retry-seconds

Specifies the time, in seconds, that the system waits while it considers a BRG down before it starts a new connectivity verification cycle. If a ping succeeds, the mechanism will be retried after this time.

Values

300 to 3600

Platforms

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

Context

[Tree] (config>redundancy>mc>peer>mcr>l3ring>node connectivity-verify)

[Tree] (config>redundancy>mc>peer>mcr>ring connectivity-verify)

Full Context

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

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

Description

Commands in this context configure a node connectivity check.

Platforms

All

Context

[Tree] (config>port connector)

Full Context

configure port connector

Description

Commands in this context configure connector parameters.

Platforms

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

Context

[Tree] (config>router>ldp consider-system-ip-in-gep)

Full Context

configure router ldp consider-system-ip-in-gep

Description

When this command is enabled, the system interprets the presence or absence of the system IP and its associated action in the applied Global Export Policies in the same way as for other interfaces' IP addresses. In that case:

• if the system IP is not present, its FEC will not be exported or it will be withdrawn if it has been exported

• if the system IP is present with "accept", its FEC will be exported

• if the system IP is present with "deny", its FEC will not be exported or it will be withdrawn if it had been exported

Enabling or disabling this command leads to the applied Global Export Policies being reevaluated.

The no form of this command causes the system to not interpret the presence or absence of the system IP in applied Global Export Policies, and the FEC for the system IP is exported (default behavior).

Default

no consider-system-ip-in-gep

Platforms

All

Context

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

Full Context

configure system management-interface cli md-cli environment console

Description

Commands in this context configure console parameters.

Platforms

All

Context

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

[Tree] (config>system>security>user-template console)

Full Context

configure system security user console

configure system security user-template console

Description

This command creates the context to configure user profile membership for the console (either Telnet or CPM serial port user).

Platforms

All

Context

[Tree] (bof console-speed)

Full Context

bof console-speed

Description

This command configures the console port baud rate.

When this command is issued while editing the BOF file used for the most recent boot, both the BOF file and the active configuration are changed immediately.

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

Default

console-speed 115200

Parameters

baud-rate

Specifies the console port baud rate, expressed as a decimal integer.

Values

9600, 19200, 38400, 57600, 115200

Platforms

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

Context

[Tree] (config>port>gnss constellation)

Full Context

configure port gnss constellation

Description

This command configures the GNSS systems used by the GNSS receiver on platforms containing one or more embedded GNSS receivers.

The GNSS receiver uses GPS by default. GPS must always be enabled when the GNSS receiver is used, and the GNSS receiver can be configured to use additional GNSS systems simultaneously.

Default

gps

Parameters

gps

Enables the use of the American GPS GNSS system. This keyword is always required when using the GNSS receiver.

galileo

Enables the use of the European Galileo GNSS system. This keyword is only supported on 7750 SR FP5 GNSS platforms.

Platforms

7750 SR-1-24D, 7750 SR-1-46S, 7750 SR-1-48D, 7750 SR-1-92S, 7750 SR-1x-48D, 7750 SR-1x-92S, 7750 SR-1se, 7750 SR-2se

Context

[Tree] (config>service>cust contact)

Full Context

configure service customer contact

Description

This command configures contact information for a customer.

Include any customer-related contact information such as a technician’s name or account contract name.

The no form of this command removes the contact information from the customer ID.

Default

no contact

Parameters

contact-information

Specifies customer contact information entered as an ASCII character string up to 80 characters in length. If the string contains special characters (#, ?, space), the entire string must be enclosed within double quotes. Any printable, seven bit ASCII characters may be used within the string.

Platforms

All

Context

[Tree] (config>system contact)

Full Context

configure system contact

Description

This command creates a text string that identifies the contact name for the device.

Only one contact can be configured, if multiple contacts are configured the last one entered will overwrite the previous entry.

The no form of the command reverts to default.

Default

no contact

Parameters

contact-name

Specifies the contact name character string. The string can be up to 80 characters long. Any printable, seven-bit ASCII characters can be used within the string. If the string contains special characters (#, ?, space), the entire string must be enclosed within double quotes.

Platforms

All

Context

[Tree] (config>system>management-interface>cli>md-cli>environment>prompt context)

Full Context

configure system management-interface cli md-cli environment prompt context

Description

This command displays the current command context in the prompt.

The no form of this command suppresses the current command context in the prompt.

Default

context

Platforms

All

Context

[Tree] (config>saa>test continuous)

Full Context

configure saa test continuous

Description

This command specifies whether the SAA test is continuous. Once a test is configured as continuous, it cannot be started or stopped with the oam saa test-name {start | stop} command.

This option is not applicable to all SAA test types. Support is included for the following types:

• cpe-ping

• dns

• eth-cfm-loopback

• eth-cfm-two-way-delay

• eth-cfm-two-way-slm

• icmp-ping (not applicable to rapid type)

• lsp-ping

• mac-ping

• sdp-ping

• vccv-ping

• vprn-ping

The no form of this command disables the continuous execution of the test.

Platforms

All

Context

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

Full Context

configure subscriber-mgmt sla-profile control

Description

This command specifies whether this SLA profile can be used by a session that is set up by a specific control plane.

Platforms

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

Context

[Tree] (config>subscr-mgmt>sub-profile control)

Full Context

configure subscriber-mgmt sub-profile control

Description

Commands in this context configure the subscriber profile to be used by a session that is set up by a specific control plane.

Platforms

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

Context

[Tree] (config>service>epipe>spoke-sdp control-channel-status)

[Tree] (config>service>cpipe>spoke-sdp control-channel-status)

[Tree] (config>service>vpls>spoke-sdp control-channel-status)

Full Context

configure service epipe spoke-sdp control-channel-status

configure service cpipe spoke-sdp control-channel-status

configure service vpls spoke-sdp control-channel-status

Description

This command enables the configuration of static pseudowire status signaling on a spoke SDP for which signaling for its SDP is set to OFF.

A control-channel-status no shutdown is allowed only if all of the following are true:

• SDP signaling is off.

• The control-word is enabled (the control-word is disabled by default)

• The service type is Epipe, Apipe, VPLS, Cpipe, or IES/VPRN

• Mate SDP signaling is off (in vc-switched services)

• The pw-path-id is configured for this spoke SDP.

The no form of this command removes control channel status signaling from a spoke SDP. It can only be removed if control channel status is shut down.

Default

no control-channel-status

Platforms

All

• configure service epipe spoke-sdp control-channel-status
• configure service vpls spoke-sdp control-channel-status

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

• configure service cpipe spoke-sdp control-channel-status

Context

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

Full Context

configure service ies interface spoke-sdp control-channel-status

Description

This command enables the configuration of static pseudowire status signaling on a spoke-SDP for which signaling for its SDP is set to OFF.

A control-channel-status no shutdown is allowed only if all of the following are true:

• SDP signaling is off.

• The control-word is enabled (the control-word is disabled by default)

• The service type is Epipe, Apipe, VPLS, Cpipe, or IES/VPRN

• Mate SDP signaling is off (in vc-switched services)

• The pw-path-id is configured for this spoke-SDP.

The no form of this command removes control channel status signaling from a spoke-SDP. It can only be removed if control channel status is shut down.

Default

no control-channel-status

Platforms

All

Context

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

[Tree] (config>service>vprn>if>spoke-sdp control-channel-status)

Full Context

configure service vprn redundant-interface spoke-sdp control-channel-status

configure service vprn interface spoke-sdp control-channel-status

Description

This command enables the configuration of static pseudowire status signaling on a spoke SDP for which signaling for its SDP is set to OFF.

A control-channel-status no shutdown is allowed only if all of the following are true:

• SDP signaling is off.

• The control-word is enabled (the control-word is disabled by default)

• The service type is Epipe, Apipe, VPLS, Cpipe, or IES/VPRN

• Mate SDP signaling is off (in vc-switched services)

• The pw-path-id is configured for this spoke SDP.

The no form of this command removes control channel status signaling from a spoke SDP. It can only be removed if control channel status is shut down.

Default

no control-channel-status

Platforms

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

• configure service vprn redundant-interface spoke-sdp control-channel-status

All

• configure service vprn interface spoke-sdp control-channel-status

Context

[Tree] (config>mirror>mirror-dest>remote-src>spoke-sdp control-channel-status)

[Tree] (config>mirror>mirror-dest>spoke-sdp control-channel-status)

Full Context

configure mirror mirror-dest remote-source spoke-sdp control-channel-status

configure mirror mirror-dest spoke-sdp control-channel-status

Description

Commands in this context configure static pseudowire status signaling on a spoke SDP for which signaling for its SDP is set to OFF. For more information about control channel status configuration for the spoke SDP, see the 7450 ESS, 7750 SR, 7950 XRS, and VSR Layer 2 Services and EVPN Guide: VLL, VPLS, PBB, and EVPN Services Guide.

Platforms

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

Context

[Tree] (config>eth-tunnel>path>eth-cfm>mep control-mep)

Full Context

configure eth-tunnel path eth-cfm mep control-mep

Description

This command enables the Ethernet tunnel control on the MEP. The use of control-mep command is mandatory for an Ethernet tunnel. MEP detection of failure using CCM may be enabled or disabled independently of the control mep.

The no form of this command disables Ethernet ring control.

Default

no control-mep

Platforms

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

Context

[Tree] (config>eth-ring>path>eth-cfm>mep control-mep)

Full Context

configure eth-ring path eth-cfm mep control-mep

Description

This command enables the Ethernet ring control on the MEP. The use of control-mep command is mandatory for a ring. MEP detection of failure using CCM may be enabled or disabled independently of the control mep.

The no form of this command disables Ethernet ring control.

Default

no control-mep

Platforms

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

Context

[Tree] (config>eth-tunnel>path control-tag)

Full Context

configure eth-tunnel path control-tag

Description

This command specifies the VLAN-ID to be used for Ethernet CFM and G.8031 control plane exchanges. If the operator wants to replace an existing control-tag, the parent path needs to be in shutdown state, then deleted and recreated before a new control-tag can be specified.

The no form of this command is used just to indicate that a control-tag is not configured. The procedure described above, based on 'no path’ command must be used to un-configure/change the control-tag assigned to the path.

Default

no control-tag

Parameters

qtag[.qtag]

Specifies the value of the VLAN ID to be used for the control tag.

Values

0 to 4094, untagged option is not supported, *

Platforms

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

Context

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

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

Full Context

configure service epipe bgp-evpn mpls control-word

configure service vpls bgp-evpn mpls control-word

Description

This command enables the transmission and reception of the control-word. As defined in RFC 7432, the use of the control-word helps avoid frame disordering.

It is enabled or disabled for all EVPN-MPLS destinations at the same time.

Default

no control-word

Platforms

All

Context

[Tree] (config>service>sdp>binding>pw-port control-word)

Full Context

configure service sdp binding pw-port control-word

Description

This command enables the setting of the control word bit in the label message. Control words are used to distinguish a PW payload (Ethernet) from an IP payload (identified by the first nibble past the bottom MPLS label, either 4 or 6) carried over an MPLS network.

Based on the payload type, the transit MPLS node can make an appropriate load balancing decision. Load balancing can rely on the MPLS labels, or rely on additional fields that are available only in IP header (source and destination IP addresses and ports).

The presence of a control word indicates that the header following the last MPLS label in the frame is not an IP header.

The no form of this command disables setting the control word bit in the label message.

Default

no control-word

Platforms

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

Context

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

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

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

Full Context

configure service epipe spoke-sdp control-word

configure service cpipe spoke-sdp control-word

configure service ipipe spoke-sdp control-word

Description

The control word command provides the option to add a control word as part of the packet encapsulation for pseudowire types for which the control word is optional. These are Ethernet pseudowires (Epipe). For the 7750 SR only, ATM N:1 cell mode pseudowires (apipe vc-types atm-vcc and atm-vpc) and VT pseudowire (apipe vc-type atm-cell).

The configuration for the two directions of the pseudowire must match because the control word negotiation procedures described in Section 6.2 of RFC 4447 are not supported. The C-bit in the pseudowire FEC sent in the label mapping message is set to 1 when the control word is enabled. Otherwise, it is set to 0.

The service will only come up if the same C-bit value is signaled in both directions. If a spoke-sdp is configured to use the control word but the node receives a label mapping message with a C-bit clear, the node releases the label with the an "Illegal C-bit” status code as per Section 6.1 of RFC 4447. As soon as the user also enabled the control the remote peer, the remote peer will withdraw its original label and will send a label mapping with the C-bit set to 1 and the VLL service will be up in both nodes. The control word must be enabled to allow MPLS-TP OAM to be used on a static spoke-sdp in a Apipe, Epipe and Cpipe service.

Platforms

All

• configure service ipipe spoke-sdp control-word
• configure service epipe spoke-sdp control-word

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

• configure service cpipe spoke-sdp control-word

Context

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

Full Context

configure service vpls spoke-sdp control-word

Description

The control word command provides the option to add a control word as part of the packet encapsulation for pseudowire types for which the control word is optional. These are Ethernet pseudowires (Epipe). For the 7750 SR only, ATM N:1 cell mode pseudowires (apipe vc-types atm-vcc and atm-vpc) and VT pseudowire (apipe vc-type atm-cell).

The configuration for the two directions of the pseudowire must match because the control word negotiation procedures described in Section 6.2 of RFC 4447 are not supported. The C-bit in the pseudowire FEC sent in the label mapping message is set to 1 when the control word is enabled. Otherwise, it is set to 0.

The service will only come up if the same C-bit value is signaled in both directions. If a spoke-sdp is configured to use the control word but the node receives a label mapping message with a C-bit clear, the node releases the label with the an "Illegal C-bit” status code as per Section 6.1 of RFC 4447. As soon as the user also enabled the control the remote peer, the remote peer will withdraw its original label and will send a label mapping with the C-bit set to 1 and the VLL service will be up in both nodes. The control word must be enabled to allow MPLS-TP OAM to be used on a static spoke-sdp in a Apipe, Epipe and Cpipe service.

Platforms

All

Context

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

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

Full Context

configure service vpls mesh-sdp control-word

configure service vpls spoke-sdp control-word

Description

This command enables the use of the control word on pseudowire packets in VPLS and enables the use of the control word individually on each mesh SDP or spoke-SDP. By default, the control word is disabled. When the control word is enabled, all VPLS packets, including the BPDU frames, are encapsulated with the control word when sent over the pseudowire. The T-LDP control plane behavior is the same as in the implementation of control word for VLL services. The configuration for the two directions of the Ethernet pseudowire should match. The no form of this command reverts the mesh SDP or spoke-SDP to the default behavior of not using the control word. The control word must be enabled to use MPLS-TP OAM on a static spoke-sdp terminating in a VPLS.

Default

no control word

Platforms

All

Context

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

Full Context

configure service ies interface spoke-sdp control-word

Description

This command enables the PW control word on spoke-SDPs terminated on an IES or VPRN interface. The control word must be enabled to allow MPLS-TP OAM on the spoke-sdp

It is only valid for MPLS-TP spoke-SDPs when used with IES and VPRN services.

Default

no control-word

Platforms

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

Context

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

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

Full Context

configure service vprn interface spoke-sdp control-word

configure service vprn redundant-interface spoke-sdp control-word

Description

This command enables the PW control word on spoke SDPs terminated on an IES or VPRN interface. The control word must be enabled to allow MPLS-TP OAM on the spoke SDP

It is only valid for MPLS-TP spoke SDPs when used with IES and VPRN services.

The no form of this command disables the control work on spoke SDPs.

Default

no control-word

Platforms

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

• configure service vprn interface spoke-sdp control-word

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

• configure service vprn redundant-interface spoke-sdp control-word

Context

[Tree] (config>mirror>mirror-dest>remote-src>spoke-sdp control-word)

[Tree] (config>mirror>mirror-dest>spoke-sdp control-word)

Full Context

configure mirror mirror-dest remote-source spoke-sdp control-word

configure mirror mirror-dest spoke-sdp control-word

Description

This command enables the PW control word on spoke SDPs that are part of a mirror-destination.

The control word must be enabled to allow MPLS-TP OAM on a spoke SDP.

It is only valid for spoke SDPs that are part of a mirror service of type ether.

The no form of this command disables the control word.

Platforms

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

• configure mirror mirror-dest remote-source spoke-sdp control-word

All

• configure mirror mirror-dest spoke-sdp control-word

Context

[Tree] (config>test-oam>build-packet>header control-word)

Full Context

configure test-oam build-packet header control-word

Description

This command creates a control-word header for inclusion in a build packet instance.

Platforms

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

Context

[Tree] (config>service>pw-template controlword)

Full Context

configure service pw-template controlword

Description

This command enables the use of the control word on pseudowire packets in VPLS and VPWS and enables the use of the control word individually on each mesh-sdp or spoke-sdp. By default, the control word is disabled. When the control word is enabled, all VPLS/VPWS packets, including the BPDU frames, are encapsulated with the control word when sent over the pseudowire. The T-LDP control plane behavior is the same as in the implementation of control word for VLL services. The configuration for the two directions of the Ethernet pseudowire should match.

The no form of the command reverts the mesh SDP or spoke-sdp to the default behavior of not using the control word.

Default

no controlword

Platforms

All

Context

[Tree] (config>service>vprn>bgp convergence)

Full Context

configure service vprn bgp convergence

Description

Commands in this context configure route convergence delay.

Platforms

All

Context

[Tree] (config>router>bgp convergence)

Full Context

configure router bgp convergence

Description

Commands in this context configure route convergence delay.

Platforms

All

Context

[Tree] (admin>certificate convert-file)

Full Context

admin certificate convert-file

Description

This command converts imported certificates and keys in the cf3:/system-pki directory between secure and legacy format.

Parameters

filename

Specifies an existing filename, up to 95 characters.

output-file-name

Specifies the output file name, up to 95 characters. If the output filename already exists, and the force keyword is not selected, the system prompts to proceed or abort.

format

Specifies the target format.

Values

secure — Specifies the enhanced secure format

legacy — Specifies the legacy format

force

Forces the conversion even if there is an existing file with the same output filename.

Platforms

All

Context

[Tree] (config>service>epipe>spoke-sdp>ingress>l2tpv3 cookie)

[Tree] (config>service>epipe>spoke-sdp>egress>l2tpv3 cookie)

Full Context

configure service epipe spoke-sdp ingress l2tpv3 cookie

configure service epipe spoke-sdp egress l2tpv3 cookie

Description

This command configures the RX/TX cookie for L2TPv3 spoke SDPs for Epipe services. The RX cookie must match the configured TX cookie on a far-end node, while the TX cookie must match the configured RX cookie on a far-end node. If a mismatch is detected between the configured (far-end binding cookie) to what is received by the local IP address of the SDP a flag is set and must be manually cleared by an operator.

The purpose of the cookie is to provide validation against misconfiguration of service endpoints, and to ensure that the right service egress is being used.

One egress cookie and up to two ingress cookies may be configured per spoke SDP binding. One or two cookies can be configured for matching ingress packets from the far-end node, in order to support cookie rollover without dropping packets. When a cookie is not configured, SR OS assumes a value of 00:00:00:00:00:00:00:00.

A cookie is not mandatory. An operator may delete an egress cookie or either or both ingress cookies.

Default

no cookie1 cookie2

Parameters

cookie1

Specifies the first cookie, in the form of a 64-bit colon-separated hex value.

cookie2

Specifies the second cookie, in the form of a 64-bit colon-separated hex value.

Platforms

All

Context

[Tree] (config>mirror>mirror-dest>spoke-sdp>egress>l2tpv3 cookie)

[Tree] (config>mirror>mirror-dest>remote-src>spoke-sdp>ingress>l2tpv3 cookie)

Full Context

configure mirror mirror-dest spoke-sdp egress l2tpv3 cookie

configure mirror mirror-dest remote-source spoke-sdp ingress l2tpv3 cookie

Description

This command configures the RX/TX cookie for L2TPv3 spoke SDPs for the mirror destination. The command can configure L2TPv3 a single cookie for the egress spoke SDP or one or two cookies for the remote source ingress spoke SDP.

The purpose of the cookie is to provide validation against misconfiguration of service endpoints, and to ensure that the right service egress is being used.

When a cookie is not configured, SR OS assumes a value of 00:00:00:00:00:00:00:00. A cookie is not mandatory. An operator may delete the egress cookie or either or both ingress cookies.

Parameters

cookie1-value

Specifies a 64-bit colon separated hex value.

Values

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

cookie2-value

Specifies a second 64-bit colon separated hex value.

Values

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

Platforms

All

Context

[Tree] (config>service>vprn>l2tp>l2tpv3 cookie-length)

[Tree] (config>router>l2tp>l2tpv3 cookie-length)

[Tree] (config>service>vprn>l2tp>group>l2tpv3 cookie-length)

Full Context

configure service vprn l2tp l2tpv3 cookie-length

configure router l2tp l2tpv3 cookie-length

configure service vprn l2tp group l2tpv3 cookie-length

Description

This command configures the length of the optional cookie field.

The no form of this command returns the cookie-length to a default of none.

Default

no cookie-length

Parameters

4

Specifies the cookie length as 4 bytes.

8

Specifies the cookie length as 8 bytes.

default

When specified within the config>service>vprn>l2tp>group>l2tpv3 context, this is referencing to the cookie-length configuration within the config>service>vprn>l2tp>l2tpv3 context.

Platforms

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

Context

[Tree] (config>system>fan-control cooling-profile)

Full Context

configure system fan-control cooling-profile

Description

This command configures the cooling profile used to determine the fan speed.

Nokia recommends that the default setting be used unless aggressive cooling is explicitly required.

The no form of this command sets the cooling profile back to the default value.

Default

no cooling-profile

Parameters

default

Specifies the fan speed operates at its default speed.

aggressive

Sets the control point optics temperature to 65 C, which requires a higher fan speed.

Platforms

7750 SR-1-24D, 7750 SR-1-46S, 7750 SR-1-48D, 7750 SR-1-92S, 7750 SR-1x-48D, 7750 SR-1x-92S, 7750 SR-1se

Context

[Tree] (config>system coordinates)

Full Context

configure system coordinates

Description

This command creates a text string that identifies the system coordinates for the device location. For example, the command coordinates "37.390 -122.0550" is read as latitude 37.390 north and longitude 122.0550 west.

Only one set of coordinates can be configured. If multiple coordinates are configured, the last one entered overwrites the previous entry.

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

Parameters

coordinates

Specifies the coordinates describing the device location character string. The string may be up to 80 characters long. Any printable, seven-bit ASCII characters can be used within the string. If the string contains special characters (#, ?, space), the entire string must be enclosed within double quotes. If the coordinates are subsequently used by an algorithm that locates the exact position of this node then the string must match the requirements of the algorithm.

Platforms

All

Context

[Tree] (config>service>mrp copy)

Full Context

configure service mrp copy

Description

This command copies existing MRP policy list entries for a specific policy name to another policy name. The copy command is a configuration level maintenance tool used to create a new MRP policy using an existing MRP policy.

An error will occur if the destination policy name exists.

Parameters

source-name

Identifies the source MRP policy from which the copy command will attempt to copy. The MRP policy with this name must exist for the command to be successful.

dest-name

Identifies the destination MRP policy to which the copy command will attempt to copy. If the MRP policy with dest-name exist within the system an error message is generated.

Platforms

All

Context

[Tree] (config>qos copy)

Full Context

configure qos copy

Description

Commands in this context copy existing QoS policy entries for a QoS policy-id to another QoS policy-id.

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

Platforms

All

Context

[Tree] (config>filter copy)

Full Context

configure filter copy

Description

This command copies existing filter list entries for a specific filter ID to another filter ID. The copy command is a configuration level maintenance tool used to create new filters using existing filters. It also allows bulk modifications to an existing policy with the use of the overwrite keyword. If overwrite is not specified, an error will occur if the destination policy ID exists.

Platforms

All

Context

[Tree] (file copy)

Full Context

file copy

Description

This command copies a file or all files in a directory from a source URL to a destination URL. At least one of the specified URLs should be a local URL. The optional wildcard (*) can be used to copy multiple files that share a common (partial) prefix and/or (partial) suffix.

When a file is copied to a destination with the same file name, the original file is overwritten by the new file specified in the operation. The following prompt appears if the destination file already exists:

"Overwrite destination file (y/n)?”

For example:

To copy a file named srcfile in a directory called test on cf2 in slot B to a file called destfile in a directory called production on cf1 in slot A, the syntax is:

sr1>file cf2:\ # copy cf2-B/test/srcfile cf1-A/production/destfile

To FTP a file named 121201.cfg in directory mydir stored on cf1 in slot A to a network FTP server with IP address 192.0.2.79 in a directory called backup with a destination file name of 121201.cfg, the FTP syntax is:

copy cf1-A/mydir/121201.cfg 192.0.2.79/backup/121201.cfg

Parameters

source-file-url

Specifies the location of the source file or directory to be copied.

Values

local-url	[cflash-id/][file-path] up to 200 characters, including cflash-id directory length 99 chars max each
remote-url	[{ftp:// | tftp:// | http:// | https://}login:pswd@remote-locn/][file-path]
	up to 247 characters
	directory length up to 199 characters
remote-locn	[hostname | ipv4-address | [ipv6-address]]
ipv4-address	a.b.c.d
ipv6-address	x:x:x:x:x:x:x:x[-interface]
	x:x:x:x:x:x:d.d.d.d[-interface]
	x - [0 to FFFF]H
	d - [0 to 255]D
	interface - up to 32 characters, for link local addresses 255
cflash-id	cf1:, cf1-A:, cf1-B:, cf2:, cf2-A:, cf2-B:, cf3:, cf3-A:, cf3-B: