r Commands – Part III

Context

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

Full Context

configure aaa l2tp-accounting-policy radius-accounting-server retry

Description

This command configures the number of times the router attempts to contact the RADIUS server for authentication.

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

Default

retry 3 (the initial attempt as well as two retried attempts)

Parameters

count

Specifies the retry count.

Values

1 to 10

Platforms

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

Context

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

Full Context

configure application-assurance radius-accounting-policy radius-accounting-server retry

Description

This command configures the number of times the router attempts to contact the RADIUS accounting server if a response to the initial message is not received.

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

Default

retry 3

Parameters

count

Specifies the retry count.

Values

1 to 10

Platforms

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

Context

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

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

Full Context

configure subscriber-mgmt authentication-policy radius-authentication-server retry

configure subscriber-mgmt radius-accounting-policy radius-accounting-server retry

Description

This command configures the number of times the router attempts to contact the RADIUS server for authentication or accounting, if not successful the first time.

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

Default

retry 3

Parameters

count

Specifies the retry count.

Values

1 to 10

Platforms

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

Context

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

Full Context

configure aaa radius-server-policy servers retry

Description

This command configures the number of times the router attempts to contact the RADIUS server, if not successful the first time.

The no form of this command reverts to the default.

Default

retry 3

Parameters

count

Specifies the number of times a signaling request message is transmitted towards the same peer.

Values

1 to 256

Platforms

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

Context

[Tree] (config>service>vpls>bgp-evpn>mac-duplication retry)

Full Context

configure service vpls bgp-evpn mac-duplication retry

Description

Specifies the timer after which the MAC in hold-down state is automatically flushed and the mac-duplication process starts again. This value is expected to be equal to two times or more than that of window.

If no retry is configured, this implies that, when mac-duplication is detected, MAC updates for that MAC will be held down till the user intervenes or a network event (that flushes the MAC) occurs.

Default

retry 9

Parameters

minutes

Specifies the BGP EVPN MAC duplication retry in minutes.

Values

2 to 60

Platforms

All

Context

[Tree] (config>system>security>radius retry)

[Tree] (config>service>vprn>aaa>rmt-srv>radius retry)

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

Full Context

configure system security radius retry

configure service vprn aaa remote-servers radius retry

configure system security dot1x radius-plcy retry

Description

This command configures the number of times the router attempts to contact the RADIUS server for authentication if there are problems communicating with the server.

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

Default

retry 3

Parameters

count

Specifies the retry count.

Values

1 to 10

Platforms

All

Context

[Tree] (config>system>file-trans-prof retry)

Full Context

configure system file-transmission-profile retry

Description

This command specifies the number of retries on transport protocol level.

When the virtual router does not receive any data from a server (e.g., FTP or HTTP server) after the configured timeout seconds, the router may repeat the request to the server. The number of retries specifies the maximum number of repeated requests.

The no form of this command disables the retry.

Default

no retry

Parameters

count

Specifies the number of retries.

Values

1 to 256

Platforms

All

Context

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

Full Context

configure aaa isa-radius-policy servers retry

Description

This command configures the number of times the router attempts to contact the RADIUS server for authentication, if not successful the first time.

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

Default

retry 3

Parameters

count

Specifies the retry count.

Values

1 to 10

Platforms

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

Context

[Tree] (config>system>security>ldap retry)

Full Context

configure system security ldap retry

Description

This command configures the number of retries for the SR OS in its attempt to reach the current LDAP server before attempting the next server.

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

Default

retry 3

Parameters

count

Specifies the number of retransmissions.

Values

1 to 10

Default

3

Platforms

All

Context

[Tree] (config>subscr-mgmt>shcv-policy>periodic retry-count)

Full Context

configure subscriber-mgmt shcv-policy periodic retry-count

Description

This command configures the number of retransmissions.

The no form of this command reverts to the default.

Default

retry-count 1 — For trigger-type ip-conflict, host-limit-exceeded and mobility

retry-count 10 — For trigger-type inactivity and MAC learning

Parameters

count

Specifies the number of retransmissions in periodic connectivity verification.

Values

2 to 29

Platforms

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

Context

[Tree] (config>subscr-mgmt>shcv-policy>trigger retry-count)

Full Context

configure subscriber-mgmt shcv-policy trigger retry-count

Description

This command configures the number of retransmissions in periodic connectivity verification.

The no form of this command reverts to the default.

Default

retry-count 1

Parameters

count

Specifies the number of retransmissions in periodic connectivity verification.

Values

1 to 29

Platforms

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

Context

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

Full Context

configure service epipe spoke-sdp-fec retry-count

Description

This optional command specifies the number of attempts software should make to reestablish the spoke SDP after it has failed. After each successful attempt, the counter is reset to zero.

When the specified number is reached, no more attempts are made and the spoke-sdp is put into the shutdown state.

Use the no shutdown command to bring up the path after the retry limit is exceeded.

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

Default

retry-count 30

Parameters

retry-count

The maximum number of retries before putting the spoke-sdp into the shutdown state.

Values

10 to 10000

Platforms

All

Context

[Tree] (config>test-oam>ldp-treetrace>path-discovery retry-count)

[Tree] (config>test-oam>ldp-treetrace>path-probing retry-count)

Full Context

configure test-oam ldp-treetrace path-discovery retry-count

configure test-oam ldp-treetrace path-probing retry-count

Description

In the path discovery phase of the LDP tree trace feature, this command configures the number of retransmissions of an LSP trace message to discover the path of an LDP FEC when no response is received within the timeout parameter.

In the path-probing phase of the LDP tree trace, this command configures the number of retransmissions of an LSP ping message to probe the path of an LDP FEC when no response is received within the timeout parameter.

The no form of this command resets the retry count to its default value.

Default

no retry-count

Parameters

retry-count

Specifies the maximum number of consecutive time outs allowed before failing a path probe (ping).

Platforms

All

Context

[Tree] (config>service>pw-routing retry-count)

Full Context

configure service pw-routing retry-count

Description

This optional command specifies the number of attempts software should make to re-establish the spoke SDP after it has failed. After each successful attempt, the counter is reset to zero.

When the specified number is reached, no more attempts are made and the spoke SDP is put into the shutdown state.

Use the no shutdown command to bring up the path after the retry limit is exceeded.

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

Default

no retry-count

Parameters

count

Specifies the maximum number of retries before putting the spoke SDP into the shutdown state.

Values

10 to 10000

Platforms

All

Context

[Tree] (config>aaa>route-downloader retry-interval)

Full Context

configure aaa route-downloader retry-interval

Description

This command sets the duration, in minutes, of the retry interval. The retry interval is the interval meant for the system to retry sending an Access Request message after the previous one was unanswered (not with an access reject but rather just a RADIUS failure or ICMP port unreachable). This timer is actually an exponential backoff timer that starts at min and is capped at max minutes.

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

Default

retry-interval min 10 max 20

Parameters

min minimum

Specifies the duration, in minutes, of the retry interval. This duration grows exponentially after each sequential failure.

Values

1 to 1440

max maximum

Specifies the maximum duration, in minutes, of the retry interval.

Values

1 to 1440

Platforms

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

Context

[Tree] (config>router>wpp>portals>portal retry-interval)

[Tree] (config>service>vprn>wpp>portals>portal retry-interval)

Full Context

configure router wpp portals portal retry-interval

configure service vprn wpp portals portal retry-interval

Description

This command configures the time interval between two consecutive retransmissions

The no form of this command reverts to the default.

Default

retry-interval 2000

Parameters

milliseconds

Specifies the time interval between two consecutive retransmissions.

Values

10 to 2000

Platforms

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

Context

[Tree] (config>system>security>pki>ca-prof>auto-crl-update retry-interval)

Full Context

configure system security pki ca-profile auto-crl-update retry-interval

Description

This command specifies the interval, in seconds, that the system waits before retrying the configured url-entry list when schedule-type is next-update-based and none of the URLs return a qualified CRL.

The no form of this command causes the system to retry immediately without waiting.

Default

retry-interval 3600

Parameters

seconds

Specifies an interval, in seconds, before retrying to update the CRL.

Values

1 to 31622400

Platforms

All

Context

[Tree] (config>system>security>pki>cert-upd-prof retry-interval)

Full Context

configure system security pki certificate-update-profile retry-interval

Description

This command configures the retry interval after the update fails.

Default

retry-interval 3600

Parameters

seconds

Specifies a retry interval, in seconds, after a failed update.

Values

60 to 36000

Platforms

All

Context

[Tree] (config>router>mpls>lsp retry-limit)

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

Full Context

configure router mpls lsp retry-limit

configure router mpls lsp-template retry-limit

Description

This optional command specifies the number of attempts software should make to re-establish the LSP after it has failed LSP. After each successful attempt, the counter is reset to zero.

When the specified number is reached, no more attempts are made and the LSP path is put into the shutdown state.

Use the config router mpls lsp lsp-name no shutdown command to bring up the path after the retry-limit is exceeded.

For P2MP LSP that are created based on the LSP template, all S2Ls must attempt to retry-limit before the client application is informed of failure.

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

Default

retry-limit 0 (no limit, retries forever)

Parameters

number

Specifies the number of times software will attempt to re-establish the LSP after it has failed. Allowed values are integers in the range of 0 to 10000.

Values

0 to 10000

Platforms

All

Context

[Tree] (config>router>mpls retry-on-igp-overload)

Full Context

configure router mpls retry-on-igp-overload

Description

This command allows for the global configuration of the handling in the ingress LER of the LSP paths which transit an LSR that advertised the IS-IS overload bit.

By default, MPLS re-optimizes using make-before-break (MBB) the transit paths away from the node in an IS-IS overload state only at the time a manual or timer-based re-signal is performed for the LSP paths. MPLS will not act immediately on the receipt of the IS-IS overload bit.

When this command is enabled, MPLS in the ingress LER immediately tears down and re-signals all LSP paths away from a transit LSR node which advertised the IS-IS overload bit.

LSP paths that terminate on the node that advertised the IS-IS overload bit are not acted on whether this command is enabled or disabled.

The no form of this command returns to the default behavior.

Platforms

All

Context

[Tree] (config>port>ethernet>dwl retry-timeout)

Full Context

configure port ethernet down-when-looped retry-timeout

Description

This command configures the minimum wait time before re-enabling port after loop detection.

Default

no retry-timeout

Parameters

timer

Specifies the minimum wait time before re-enabling port after loop detection.

Values

0, 10 to 160

Platforms

All

Context

[Tree] (config>service>vpls>mac-move retry-timeout)

[Tree] (config>service>template>vpls-template>mac-move retry-timeout)

Full Context

configure service vpls mac-move retry-timeout

configure service template vpls-template mac-move retry-timeout

Description

This indicates the time in seconds to wait before a SAP that has been disabled after exceeding the maximum relearn rate is re-enabled.

It is recommended that the retry-timeout value is larger or equal to 5s * cumulative factor of the highest priority port so that the sequential order of port blocking will not be disturbed by re-initializing lower priority ports.

A zero value indicates that the SAP will not be automatically re-enabled after being disabled. If, after the SAP is re-enabled it is disabled again, the retry timeout is increased with the provisioned retry timeout in order to avoid thrashing. For example, when retry-timeout is set to 15, it increments (15,30,45,60...).

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

Default

retry-timeout 10 (when mac-move is enabled)

Parameters

timeout

Specifies the time, in seconds, to wait before a SAP that has been disabled after exceeding the maximum relearn rate is re-enabled.

Values

0 to 120

Platforms

All

Context

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

Full Context

configure service epipe spoke-sdp-fec retry-timer

Description

This command specifies a retry-timer for the spoke SDP. This is a configurable exponential back-off timer that determines the interval between retries to reestablish a spoke SDP if it fails and a label withdraw message is received with the status code "AII unreachable”.

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

Default

retry-timer 30

Parameters

retry-timer

The initial retry-timer value in seconds.

Values

10 to 480

Platforms

All

Context

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

[Tree] (config>router>mpls>lsp retry-timer)

Full Context

configure router mpls lsp-template retry-timer

configure router mpls lsp retry-timer

Description

This command configures the time (in s), for LSP re-establishment attempts after it has failed. The retry time is jittered to +/- 25% of its nominal value.

For P2MP LSP created based on LSP template, all S2Ls must attempt to retry-limit before client application is informed of failure.

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

Default

retry-timer 30

Parameters

seconds

Specifies the amount of time (in s), between attempts to re-establish the LSP after it has failed. Allowed values are integers in the range of 1 to 600.

Values

1 to 600

Platforms

All

Context

[Tree] (config>service>pw-routing retry-timer)

Full Context

configure service pw-routing retry-timer

Description

This command configures a retry-timer for the spoke-SDP. This is a configurable exponential back-off timer that determines the interval between retries to re-establish a spoke-SDP if it fails and a label withdraw message is received with the status code "AII unreachable”.

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

Default

no retry-timer

Parameters

secs

Specifies initial retry-timer value in seconds.

Values

10 to 480

Platforms

All

Context

[Tree] (config>test-oam>link-meas>template>twl return-path)

Full Context

configure test-oam link-measurement measurement-template twamp-light return-path

Description

Commands in this context configure the return-path TLV for the test packet.

Platforms

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

Context

[Tree] (conf>router>segment-routing>sr-policies>policy>srv6 return-path-bfd-sid)

Full Context

configure router segment-routing sr-policies static-policy segment-routing-v6 return-path-bfd-sid

Description

This command configures the Seamless Bidirectional Forwarding Detection (S-BFD) session to echo mode and pushes an additional SRv6 SID in the SRH on S-BFD packets only.

The command applies to the initiator of the S-BFD sessions. The return path SID refers to a binding SID on a SRv6 policy configured on the far-end router. Instead of being routed through the IGP path, the S-BFD packet returns to the initiator through this SRv6 return path.

The no form of this command disables the controlled return-path SID and echo mode for S-BFD. If the command is deleted, the S-BFD session returns to asynchronous mode and the initiator node does not push a return-path SID. Any S-BFD packets for this SRv6 policy that the terminating router receives are sent back using a routed return path.

Parameters

ipv6-address

Specifies the IPv6 address.

Values

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

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

• x: [0 to FFFF]H

• d: [0 to 255]D

Platforms

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

Context

[Tree] (config>router>mpls>lsp>bfd return-path-label)

[Tree] (config>router>segment-routing>main-plcy return-path-label)

[Tree] (config>router>mpls>lsp>sec>bfd return-path-label)

[Tree] (config>router>mpls>lsp>primary>bfd return-path-label)

[Tree] (config>router>mpls>lsp-template>bfd return-path-label)

Full Context

configure router mpls lsp bfd return-path-label

configure router segment-routing maintenance-policy return-path-label

configure router mpls lsp secondary bfd return-path-label

configure router mpls lsp primary bfd return-path-label

configure router mpls lsp-template bfd return-path-label

Description

This command configures the Seamless Bidirectional Forwarding Detection (S-BFD) session to echo mode and adds an additional MPLS label, referring to an MPLS-labeled reply path for the S-BFD packet, to the bottom of the label stack for the S-BFD packet.

The command applies to the initiator of the S-BFD sessions. The return-path label may be a binding SID for an SR policy or other MPLS path configured on the reflector router. Instead of being routed through the IGP path, the S-BFD packet returns to the initiator through this MPLS return path.

The no form of this command disables the controlled return-path label and echo mode for S-BFD. S-BFD returns to asynchronous mode and the initiator node does not push a return-path label. Any S-BFD packets for this LSP or path that the reflector receives are sent back using a routed return path.

Default

no return-path-label

Parameters

label-value

Specifies the label value.

Values

32 to 1048575

Platforms

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

• configure router mpls lsp-template bfd return-path-label
• configure router mpls lsp bfd return-path-label
• configure router mpls lsp primary bfd return-path-label
• configure router mpls lsp secondary bfd return-path-label

All

• configure router segment-routing maintenance-policy return-path-label

Context

[Tree] (config>router>policy-options>damping reuse)

Full Context

configure router policy-options damping reuse

Description

This command configures the reuse parameter for the route damping profile.

When the Figure of Merit (FoM) value falls below the reuse threshold, the route is once again considered valid and can be reused or included in route advertisements.

The no form of this command removes the reuse parameter from the damping profile.

Default

no reuse

Parameters

integer

Specifies the reuse value expressed as a decimal integer.

Values

1 to 20000

Platforms

All

Context

[Tree] (config>service>nat>pcp-server-policy reuse-ext-ip)

Full Context

configure service nat pcp-server-policy reuse-ext-ip

Description

This command enables the system to reuse the external IP address assigned to a subscriber when the requested well-known port or external IP mapping is not available.

The no form of this command causes a request for a well-known port to be allocated exactly as requested but on a different external IP address from the one that the subscriber is already using. This occurs if the requested well-known port is already allocated to another subscriber which is sharing the same external IP address. The existing external IP address is initially allocated to the subscriber by the virtue of initial traffic flow.

Default

no reuse-ext-ip

Platforms

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

Context

[Tree] (config>router>mpls>mpls-tp>transit-path reverse-path)

Full Context

configure router mpls mpls-tp transit-path reverse-path

Description

This command enables the reverse path of an MPLS-TP reverse path to be created or edited.

The reverse path must be created after the forward path.

The no form of this command removes the reverse path. The reverse path must be removed before the forward path.

Default

no reverse-path

Platforms

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

Context

[Tree] (config>ipsec>tnl-temp reverse-route)

Full Context

configure ipsec tunnel-template reverse-route

Description

Commands in this context configure the dynamic LAN-to-LAN (DL2L) tunnel reverse-route options for the tunnel template.

Platforms

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

Context

[Tree] (admin>rollback revert)

Full Context

admin rollback revert

Description

This command initiates a configuration rollback revert operation that will return the configuration state of the node to a previously saved checkpoint. The rollback revert minimizes impacts to running services. There are no impacts in areas of configuration that did not change since the checkpoint. Configuration parameters that changed (or items on which changed configuration have dependencies) are first removed (revert to default) and the previous values are then restored (can be briefly service impacting in changed areas).

Parameters

latest-rb

Specifies the most recently created rollback checkpoint (corresponds to the file-url.rb rollback checkpoint file).

checkpoint-id

Specifies the configuration to return to (which rollback checkpoint file to use). Checkpoint-id of 1 corresponds to the file-url.rb.1 rollback checkpoint file. The higher the id, the older the checkpoint. Max is the highest rollback checkpoint supported or configured.

Values

1 to 9

rescue

Specifies to revert to the rescue checkpoint.

now

Forces a rollback revert without any interactive confirmations (assumes 'y’ for any confirmations that would have occurred).

Platforms

All

Context

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

Full Context

configure system sync-if-timing revert

Description

This command allows the clock to revert to a higher priority reference if the current reference goes offline or becomes unstable. When the failed reference becomes operational, it is eligible for selection. When the mode is non-revertive, a failed clock source is not selected again.

Default

no revert

Platforms

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

Context

[Tree] (config>service>vprn>isis>link-group>level revert-members)

Full Context

configure service vprn isis link-group level revert-members

Description

This command sets the threshold for the minimum number of operational links to return the associated link group to its normal operating state and remove the associated offsets to the IS-IS metrics. If the number of operational links is equal to or greater than the configured revert-members threshold, the configured offsets are removed.

The no form of this command reverts the threshold back to the default, which is equal to the oper-members threshold value.

Default

no revert-members oper-members

Parameters

1..8

Specifies the number of revert members.

Values

1 to 8

Platforms

All

Context

[Tree] (config>router>isis>link-group>level revert-members)

Full Context

configure router isis link-group level revert-members

Description

This command sets the threshold for the minimum number of operational links to return the associated link group to its normal operating state and remove the associated offsets to the IS-IS metrics. If the number of operational links is equal to or greater than the configured revert-member threshold then the configured offsets are removed.

The no form of this command reverts the threshold back to the default which is equal to the oper-member threshold value.

Default

no revert-members oper-members

Parameters

1..8

Specifies the threshold for revertive members.

Values

1 to 8

Platforms

All

Context

[Tree] (config>port>aps revert-time)

Full Context

configure port aps revert-time

Description

This command configures the revert-time timer to determine how long to wait before switching back to the working circuit after that circuit has been restored into service.

A change in the minutes value takes effect upon the next initiation of the wait to restore (WTR) timer. It does not modify the length of a WTR timer that has already been started. The WTR timer of a non-revertive switch can be assumed to be infinite.

The no form of this command restores the default (non-revertive mode).

Default

The default is to not revert back unless the protect circuit fails or there is an operator intervention.

Parameters

minutes

Specifies the time, in minutes, to wait before reverting back to the original working circuit after it has been restored into service.

Values

0 to 60 minutes

Default

5

Platforms

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

Context

[Tree] (config>eth-tunnel revert-time)

Full Context

configure eth-tunnel revert-time

Description

This command configure how long to wait before switching back to the primary path after it has been restored to Ethernet tunnel.

The no form of this command disables the revert behavior, effectively setting the revert time to zero.

Default

no revert-time

Parameters

time

Specifies the re-activation delay, in seconds, for the primary path.

Values

1 to 720

Platforms

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

Context

[Tree] (config>service>cpipe>endpoint revert-time)

[Tree] (config>service>epipe>endpoint revert-time)

[Tree] (config>service>ipipe>endpoint revert-time)

Full Context

configure service cpipe endpoint revert-time

configure service epipe endpoint revert-time

configure service ipipe endpoint revert-time

Description

This command configures the time to wait before reverting back to the primary spoke SDP defined on this service endpoint, after having failed over to a backup spoke SDP.

Parameters

revert-time

Specifies the time, in seconds, to wait before reverting to the primary SDP.

Values

0 to 600

Default

0

infinite

Causes the endpoint to be non-revertive.

Platforms

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

• configure service cpipe endpoint revert-time

All

• configure service ipipe endpoint revert-time
• configure service epipe endpoint revert-time

Context

[Tree] (config>service>vpls>endpoint revert-time)

Full Context

configure service vpls endpoint revert-time

Description

This command configures the time to wait before reverting to primary spoke-SDP.

In a regular endpoint the revert-time setting affects just the pseudowire defined as primary (precedence 0). For a failure of the primary pseudowire followed by restoration the revert-timer is started. After it expires the primary pseudowire takes the active role in the endpoint. This behavior does not apply for the case when both pseudowires are defined as secondary. For example, if the active secondary pseudowire fails and is restored it will stay in standby until a configuration change or a force command occurs.

Parameters

revert-time

Specifies the time to wait, in seconds, before reverting back to the primary spoke-SDP defined on this service endpoint, after having failed over to a backup spoke-SDP

Values

0 to 600

infinite

Specifying this keyword makes endpoint non-revertive

Platforms

All

Context

[Tree] (config>mirror>mirror-dest>endpoint revert-time)

Full Context

configure mirror mirror-dest endpoint revert-time

Description

This command configures the time to wait before reverting to the primary spoke SDP. This command has an effect only when used in conjunction with an endpoint which contains a SDP of type 'primary’. It is ignored and has no effect in all other cases. The revert-timer is the delay in seconds the system waits before it switches the path of the mirror service from an active secondary SDP in the endpoint into the endpoint primary SDP after the latter comes back up.

The no form of this command resets the timer to the default value of 0. This means that the mirror-service path is switched back to the endpoint primary sdp immediately after it comes back up.

Parameters

revert-time

Specifies a delay, in seconds, the system waits before it switches the path of the mirror service from an active secondary SDP in the endpoint into the endpoint primary SDP after the latter comes back up.

Values

0 to 600

infinite

Forces the mirror or LI service path to never revert to the primary SDP as long as the currently active secondary SDP is UP.

Platforms

All

Context

[Tree] (config>service>sdp>mixed-lsp-mode revert-time)

Full Context

configure service sdp mixed-lsp-mode revert-time

Description

This command configures the delay period the SDP must wait before it reverts to a higher priority LSP type when one becomes available.

The no form of the command resets the timer to the default value of 0. This means the SDP reverts immediately to a higher priority LSP type when one becomes available.

Default

no revert-time

Parameters

revert-time

Specifies the delay period, in seconds, that the SDP must wait before it reverts to a higher priority LSP type when one becomes available. A value of zero means the SDP reverts immediately to a higher priority LSP type when one becomes available.

Values

0 to 600

infinite

This keyword forces the SDP to never revert to another higher priority LSP type unless the currently active LSP type is down.

Platforms

All

Context

[Tree] (config>eth-ring revert-time)

Full Context

configure eth-ring revert-time

Description

This command configures the revert time for an Eth-Ring. It ranges from 60 seconds to 720 second by 1 second intervals.

The no form of this command means non-revertive mode and revert time is essentially 0, and the revert timers are not set.

Default

revert-time 300

Parameters

time

Specifies the guard-time, in seconds.

Values

60 to 720

Platforms

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

Context

[Tree] (config>router>mpls>lsp revert-timer)

Full Context

configure router mpls lsp revert-timer

Description

This command configures a revert timer on an LSP. The timer starts when the LSP primary path recovers from a failure. The LSP reverts from a secondary path to the primary path when the timer expires, or when the secondary path fails.

The no form of this command cancels any currently outstanding revert timer. If the LSP is up when a no revert-timer is issued, the LSP will revert to the primary path. Otherwise the LSP reverts when the primary path is restored.

Default

no revert-timer

Parameters

timer-value

Specifies the amount of time, in one minute increments, between attempts to re-establish the LSP after it has failed.

Values

1 to 4320

Platforms

All

Context

[Tree] (config>router>mpls>fwd-policies>fwd-policy revert-timer)

Full Context

configure router mpls forwarding-policies forwarding-policy revert-timer

Description

This command configures the revert timer in an MPLS forwarding policy.

When the primary direct or indirect next hop is restored and is added back into the routing table, CPM waits for an amount of time equal to the user-programmed revert timer before activating it and updating the data path. However, if the backup direct or indirect next hop fails while the timer is running, CPM activates it and updates the data path immediately.

A value of 0 disables the revert timer; meaning the policy reverts immediately.

The no form of this command removes the revert timer from the MPLS forwarding policy.

Default

revert-timer 0

Parameters

seconds

Specifies the revert-timer value, in number of seconds.

Values

1 to 600

Platforms

All

Context

[Tree] (config>router>segment-routing>maintenance-policy revert-timer)

Full Context

configure router segment-routing maintenance-policy revert-timer

Description

This command configures the revert timer for SR Policy candidate paths.

The revert timer is started when the primary path (for example, the best preference programmed candidate path) recovers (for example, after the number of S-BFD sessions that are up is ≥ threshold and the hold-down-timer has expired) and switches back when the timer expires.

The no form of this command removes the revert timer from the SR policy.

Default

no revert-timer

Parameters

revert-timer

Specifies the revert timer, in minutes.

Values

1 to 4320

Platforms

All

Context

[Tree] (config>router>mpls>mpls-tp>protection-template revertive)

Full Context

configure router mpls mpls-tp protection-template revertive

Description

This command configured revertive behavior for MPLS-TP linear protection. The protect-tp-path MEP must be in the shutdown state for of the MPLS-TP LSPs referencing this protection template in order to change the revertive parameter.

Default

revertive

Platforms

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

Context

[Tree] (config>redundancy>multi-chassis>ipsec-domain revertive)

Full Context

configure redundancy multi-chassis ipsec-domain revertive

Description

This command configures whether to allow a revertive activity state after a designated active state recovers from an ineligibility event. The revertive function allows a router in an N:M domain to automatically take over as the active router in the domain, when it becomes eligible to do so.

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

Default

no revertive

Platforms

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

Context

[Tree] (config>service>vprn>mvpn>pt>inclusive>umh-rm revertive-timer)

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

Full Context

configure service vprn mvpn provider-tunnel inclusive umh-rate-monitoring revertive-timer

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

Description

This command configures the timer value (in seconds) after which to revert to the primary UMH after traffic is restored. This value must account for the traffic flapping from the primary UMH. If there is traffic flapping, the timer resets and starts over.

The no form of the command means that there is no revertive behavior.

Default

no revertive-timer

Parameters

sec

Specifies the timer value (in seconds).

Values

1 to 3600

Platforms

All

Context

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

Full Context

configure system security pki ca-profile revocation-check

Description

This command specifies the revocation method the system uses to check the revocation status of certificate issued by the CA. If the crl-optional option is configured, when the user disables the ca-profile, the system tries to load the configured CRL (specified by the crl-file command). However, if the system fails to load the configured CRL for the following reasons, the system still brings the ca-profile operationally up, but leaves the CRL configured as non-existent:

• CRL file does not exist

• CRL is not properly encoded - maybe due to interrupted file transfer

• CRL does not match cert

• Wrong CRL version

• CRL expired

If the system needs to use the CRL of a specific CA profile to check the revocation status of an end-entity certificate, and the CRL is non-existent due to the preceding reasons, the system treats a case like this as being unable to get an answer from CRL and falls back to the next status verify method or default result.

If the system needs to check the revocation of a CA certificate in a certificate chain, and if the CRL is non-existent due to the preceding reasons, the system skips checking the revocation status of the CA certificate. For example, if CA1 is issued by CA2, if the revocation-check for CA2 is crl-optional and the CRL for CA2 is non-existent, the system does not check the certificate revocation status of CA1 and it is considered as "good”.

Default

revocation-check crl

Parameters

crl

Specifies to use the configured CRL.

crl-optional

Specifies that the CRL is optional.

Platforms

All

Context

[Tree] (admin>system>security>secure-boot revoke-key)

Full Context

admin system security secure-boot revoke-key

Description

This command revokes secure boot keys.

Parameters

cpm-slot

Specifies the CPM slot.

Values

A,B

cpm-serial-number

Specifies the CPM serial number, up to 256 characters.

code

Specifies the signed software confirmation code, up to 32 characters.

Platforms

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

Context

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

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

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

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

Full Context

configure service vprn bgp-evpn mpls auto-bind-tunnel resolution-filter rib-api

configure service vprn bgp-ipvpn mpls auto-bind-tunnel resolution-filter rib-api

configure service vpls bgp-evpn mpls auto-bind-tunnel resolution-filter rib-api

configure service epipe bgp-evpn mpls auto-bind-tunnel resolution-filter rib-api

Description

This command selects the RIB-API tunnel type.

This command enables tunnels programmed using the RibApi gRPC service to be used in resolving the next hops of routes imported into the EVPN service.

The no form of this command disables tunnels programmed using the RibApi gRPC service from being used in resolving the next hops.

Default

no rib-api

Platforms

All

Context

[Tree] (config>router rib-api)

Full Context

configure router rib-api

Description

Commands in this context configure parameters related to the RIB-API gRPC service.

Platforms

All

Context

[Tree] (config>router>static-route-entry>indirect>tunnel-next-hop>resolution-filter rib-api)

Full Context

configure router static-route-entry indirect tunnel-next-hop resolution-filter rib-api

Description

This command enables tunnels programmed using the RibApi gRPC service for use in resolving the indirect next hops of statically-configured IPv4 and IPv6 routes.

Platforms

All

Context

[Tree] (debug>router rib-api)

Full Context

debug router rib-api

Description

This command enables debugging for RIB-API protocol entities.

Platforms

All

Context

[Tree] (config>system>grpc rib-api)

Full Context

configure system grpc rib-api

Description

Commands in this context control the RibAPI gRPC service.

Platforms

All

Context

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

[Tree] (config>router>bgp>next-hop-resolution>labeled-routes>transport-tunnel>family>resolution-filter rib-api)

Full Context

configure router bgp next-hop-resolution shortcut-tunnel family resolution-filter rib-api

configure router bgp next-hop-resolution labeled-routes transport-tunnel family resolution-filter rib-api

Description

This command enables tunnels programmed using the RibApi gRPC service for use in resolving the next hops of label-IPv4 or label-IPv6 routes.

Platforms

All

Context

[Tree] (config>service>vprn>auto-bind-tunnel>res-filter rib-api)

Full Context

configure service vprn auto-bind-tunnel resolution-filter rib-api

Description

Platforms

All

Context

[Tree] (config>system>security>profile>grpc>rpc-authorization rib-api-getversion)

Full Context

configure system security profile grpc rpc-authorization rib-api-getversion

Description

This command permits the use of GetVersion RPC provided by the RibApi service.

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

Default

rib-api-getversion permit

Parameters

permit

Specifies that the use of the GetVersion RPC is permitted.

deny

Specifies that the use of the GetVersion RPC is denied.

Platforms

All

Context

[Tree] (config>system>security>profile>grpc>rpc-authorization rib-api-modify)

Full Context

configure system security profile grpc rpc-authorization rib-api-modify

Description

This command permits the use of Modify RPC provided by the RibApi service.

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

Default

rib-api-modify permit

Parameters

permit

Specifies that the use of the Modify RPC is permitted.

deny

Specifies that the use of the Modify RPC is denied.

Platforms

All

Context

[Tree] (config>service>vprn>bgp rib-management)

Full Context

configure service vprn bgp rib-management

Description

Commands in this context configure RIB management parameters.

Platforms

All

Context

[Tree] (config>router>bgp rib-management)

Full Context

configure router bgp rib-management

Description

Commands in this context configure RIB management parameters.

Platforms

All

Context

[Tree] (config>service>vprn>isis rib-priority)

Full Context

configure service vprn isis rib-priority

Description

This command enabled RIB prioritization for the IS-IS protocol and specifies the prefix list or IS-IS tag value that will be used to select the specific routes that should be processed through the IS-IS route calculation process at a higher priority.

The no form of this command disables RIB prioritization.

Default

no rib-priority

Parameters

prefix-list-name

Specifies the prefix list which is used to select the routes that are processed at a higher priority through the route calculation process.

tag tag-value

Specifies the tag value that is used to match IS-IS routes that are to be processed at a higher priority through the route calculation process.

Values

1 to 4294967295

Platforms

All

Context

[Tree] (config>service>vprn>ospf3>area>if rib-priority)

[Tree] (config>service>vprn>ospf>area>if rib-priority)

Full Context

configure service vprn ospf3 area interface rib-priority

configure service vprn ospf area interface rib-priority

Description

This command enables RIB prioritization for the OSPF/OSPFv3 protocol. When enabled at the OSPF interface level, all routes learned through the associated OSPF interface will be processed through the OSPF route calculation process at a higher priority.

The no form of rib-priority command disables RIB prioritization at the associated level.

Default

no rib-priority

Platforms

All

Context

[Tree] (config>service>vprn>ospf3 rib-priority)

[Tree] (config>service>vprn>ospf rib-priority)

Full Context

configure service vprn ospf3 rib-priority

configure service vprn ospf rib-priority

Description

This command enabled RIB prioritization for the OSPF protocol and specifies the prefix list that will be used to select the specific routes that should be processed through the OSPF route calculation process at a higher priority.

The no form of rib-priority command disables RIB prioritization at the associated level.

Default

no rib-priority

Parameters

prefix-list-name

Specifies the prefix list which is used to select the routes that are processed at a higher priority through the route calculation process.

Platforms

All

Context

[Tree] (config>router>isis rib-priority)

Full Context

configure router isis rib-priority

Description

This command enabled RIB prioritization for the IS-IS protocol and specifies the prefix list or IS-IS tag value that will be used to select the specific routes that should be processed through the IS-IS route calculation process at a higher priority.

The no rib-priority form of command disables RIB prioritization.

Default

no rib-priority high

Parameters

prefix-list-name

Specifies the prefix list which is used to select the routes that are processed at a higher priority through the route calculation process.

tag tag-value

Specifies the tag value that is used to match IS-IS routes that are to be processed at a higher priority through the route calculation process.

Values

1 to 4294967295

Platforms

All

Context

[Tree] (config>router>ospf3 rib-priority)

[Tree] (config>router>ospf rib-priority)

Full Context

configure router ospf3 rib-priority

configure router ospf rib-priority

Description

This command enables RIB prioritization for the OSPF protocol and specifies the prefix list used to select the specific routes that should be processed through the OSPF route calculation process at a higher priority.

The no form of this command disables RIB prioritization at the associated level.

Default

no rib-priority high

Parameters

prefix-list-name

Specifies the prefix list, up to 32 characters, which is used to select the routes that are processed at a higher priority through the route calculation process.

Platforms

All

Context

[Tree] (config>router>ospf>area>interface rib-priority)

[Tree] (config>router>ospf3>area>interface rib-priority)

Full Context

configure router ospf area interface rib-priority

configure router ospf3 area interface rib-priority

Description

This command enables RIB prioritization for the OSPF/OSPFv3 protocol. When enabled at the OSPF interface level, all routes learned through the associated OSPF interface are processed through the OSPF route calculation process at a higher priority.

The no form of this command disables RIB prioritization at the associated level.

Default

no rib-priority

Parameters

high

Specifies that the name of the prefix list which contains prefixes get high priority for RIB-download. The high priority prefixes are downloaded first to the RIB. In doing so, the convergence time for these prefixes is better.

Platforms

All

Context

[Tree] (config>redundancy>mc>peer>mcr ring)

Full Context

configure redundancy multi-chassis peer mc-ring ring

Description

This command configures a multi-chassis ring.

The no form of this command removes the sync-tag from the configuration.

Parameters

sync-tag

Specifies a synchronization tag, up to 32 characters, to be used while synchronizing this port with the multi-chassis peer.

create

Creates he multi-chassis peer ring instance. The create keyword requirement can be enabled or disabled in the environment>create context.

Platforms

All

Context

[Tree] (config>redundancy>mc>peer>mcr>ring ring-node)

Full Context

configure redundancy multi-chassis peer mc-ring ring ring-node

Description

This command specifies the unique name of a multi-chassis ring access node.

Parameters

ring-node-name

Specifies the unique name of a multi-chassis ring access node. The name can be up to 32 characters.

create

Keyword used to create the ring node instance. The create keyword requirement can be enabled or disabled in the environment>create context.

Platforms

All

Context

[Tree] (config>service>epipe>sap ring-node)

Full Context

configure service epipe sap ring-node

Description

This command configures a multi-chassis ring-node for this SAP.

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

Platforms

All

Context

[Tree] (config>service>ies rip)

[Tree] (config>service>vprn rip)

Full Context

configure service ies rip

configure service vprn rip

Description

This command enables the RIP protocol on the given VPRN IP interface.

The no form of this command disables the RIP protocol from the given VPRN IP interface.

Default

no rip

Platforms

All

Context

[Tree] (config>router rip)

Full Context

configure router rip

Description

This command creates the context to configure the RIP protocol instance.

When a RIP instance is created, the protocol is enabled by default. To start or suspend execution of the RIP protocol without affecting the configuration, use the [no] shutdown command.

The no form of the command deletes the RIP protocol instance removing all associated configuration parameters.

Default

no rip

Platforms

All

Context

[Tree] (config>subscr-mgmt>loc-user-db>ppp>host rip-policy)

[Tree] (config>subscr-mgmt>loc-user-db>ipoe>host rip-policy)

Full Context

configure subscriber-mgmt local-user-db ppp host rip-policy

configure subscriber-mgmt local-user-db ipoe host rip-policy

Description

This command configures the RIP policy name. This policy is applied to a subscriber IPv4 host to enable the BNG to learn RIP routes from the host. RIP routes are never sent to the hosts.

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

Parameters

policy-name

Specifies the RIP policy name, up to 32 characters.

Platforms

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

Context

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

Full Context

configure subscriber-mgmt rip-policy

Description

This command creates a RIP policy. This policy is applied to a subscriber IPv4 host to enable the BNG to learn RIP routes from the host. RIP routes are never sent to the hosts.

Parameters

policy-name

Specifies the RIP policy name up to 32 characters.

create

Keyword required to create the configuration context.

Platforms

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

Context

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

Full Context

configure service ies subscriber-interface group-interface sap static-host rip-policy

Description

This command specifies the name of the RIP policy up to 32 characters.

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

Platforms

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

Context

[Tree] (config>router ripng)

Full Context

configure router ripng

Description

This command creates the context to configure the RIPng protocol instance.

When a RIPng instance is created, the protocol is enabled by default. To start or suspend execution of the RIP protocol without affecting the configuration, use the [no] shutdown command.

The no form of this command deletes the RIP protocol instance removing all associated configuration parameters.

Default

no ripng

Platforms

All

Context

[Tree] (config>system>thresholds rmon)

Full Context

configure system thresholds rmon

Description

This command creates the context to configure generic RMON alarms and events.

Generic RMON alarms can be created on any SNMP object-ID that is valid for RMON monitoring (for example, an integer-based datatype).

The configuration of an event controls the generation and notification of threshold crossing events configured with the alarm command.

Platforms

All

Context

[Tree] (config>subscr-mgmt>gtp>peer-profile>charging roaming)

Full Context

configure subscriber-mgmt gtp peer-profile charging-characteristics roaming

Description

This command configures the charging characteristics for roaming UE.

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

Default

no roaming

Parameters

bit

Specifies up to 16 bits to set in the Charging Characteristics Information Element (IE) for roaming UE, if not known by other means such as RADIUS.

Values

bit0, bit1, bit2, bit3, bit4, bit5, bit6, bit7, bit8, bit9, bit10, bit11, bit12, bit13, bit14, bit15

Platforms

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

Context

[Tree] (config>service>vpls>spoke-sdp>mld-snooping robust-count)

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

[Tree] (config>service>vpls>mesh-sdp>mld-snooping robust-count)

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

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

[Tree] (config>service>vpls>sap>mld-snooping robust-count)

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

Full Context

configure service vpls spoke-sdp mld-snooping robust-count

configure service vpls igmp-snooping robust-count

configure service vpls mesh-sdp mld-snooping robust-count

configure service vpls mesh-sdp igmp-snooping robust-count

configure service vpls spoke-sdp igmp-snooping robust-count

configure service vpls sap mld-snooping robust-count

configure service vpls sap igmp-snooping robust-count

Description

If the send-queries command is enabled, this parameter allows tuning for the expected packet loss on a SAP or SDP. The robust-count variable allows tuning for the expected packet loss on a subnet and is comparable to a retry count. If this SAP or SDP is expected to be 'lossy', this parameter may be increased. IGMP snooping on this SAP or SDP is robust to (robust-count-1) packet losses.

If send-queries is not enabled, this parameter will be ignored.

Default

robust-count 2

Parameters

robust-count

Specifies the robust count for the SAP or SDP

Values

2 to 7 (for config>service>vpls>sap>igmp-snooping) 1 to 255 (for config>service>vpls>igmp-snooping)

Platforms

All

Context

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

Full Context

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

Description

This command configures the IGMP robustness variable. If the send-queries command is enabled, this parameter allows tuning for the expected packet loss on a SAP or SDP. The robust-count variable allows tuning for the expected packet loss on a subnet and is comparable to a retry count. If an MSAP or SDP is expected to be "lossy”, this parameter may be increased. IGMP snooping on an MSAP or SDP is robust to (robust-count-1) packet losses.

If send-queries is not enabled, this parameter is ignored.

The no form of this command reverts to the default.

Default

robust-count 2

Parameters

robust-count

Specifies the robust count for the SAP or SDP.

Values

2 to 7

Platforms

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

Context

[Tree] (config>service>vprn>mld robust-count)

[Tree] (config>service>vprn>igmp robust-count)

Full Context

configure service vprn mld robust-count

configure service vprn igmp robust-count

Description

This command configures the robust count. The robust-count variable allows tuning for the expected packet loss on a subnet. If a subnet anticipates losses, the robust-count variable can be increased.

Default

robust-count 2

Parameters

robust-count

Specifies the robust count value.

Values

2 to 10

Platforms

All

Context

[Tree] (config>router>igmp robust-count)

Full Context

configure router igmp robust-count

Description

This command configures the robust count. The robust-count variable allows tuning for the expected packet loss on a subnet. If a subnet anticipates losses, the robust-count variable can be increased.

Default

robust-count 2

Parameters

robust-count

Specify the robust count value.

Values

2 to 10

Platforms

All

Context

[Tree] (config>router>mld robust-count)

Full Context

configure router mld robust-count

Description

This command configures the robust count. The robust-count variable allows tuning for the expected packet loss on a subnet. If a subnet anticipates losses, the robust-count variable can be increased.

Default

robust-count 2

Parameters

robust-count

Specify the robust count value.

Values

2 to 10

Platforms

All

Context

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

Full Context

configure service pw-template igmp-snooping robust-count

Description

If the send-queries command is enabled, this parameter allows tuning for the expected packet loss. The robust-count variable allows tuning for the expected packet loss on a subnet and is comparable to a retry count.

If send-queries is not enabled, this parameter will be ignored.

Default

robust-count 2

Parameters

robust-count

Specifies the robust count for the SAP or SDP.

Values

2 to 7

Platforms

All

Context

[Tree] (config>system>satellite>port-template>port role)

Full Context

configure system satellite port-template port role

Description

This command configures the role that the associated port is to take on.

Parameters

none

Clears the role association for the associated port.

uplink

Specifies that the associated satellite port is assigned the role of an uplink port.

client

Specifies that the associated satellite port is assigned the role of a satellite client port.

system-default

Specifies that the associated satellite port is returned to the system default.

Platforms

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

Context

[Tree] (config>system rollback)

Full Context

configure system rollback

Description

Configure parameters of the classic CLI configuration rollback functionality. Configuration rollback provides the ability to undo configuration and revert back to previous router configuration states.

Platforms

All

Context

[Tree] (admin rollback)

Full Context

admin rollback

Description

Commands in this context configure rollback operations.

Platforms

All

Context

[Tree] (config>system>rollback rollback-location)

Full Context

configure system rollback rollback-location

Description

The location and name of the rollback checkpoint files is configurable to be local (on compact flash) or remote. The file-url must not contain a suffix (just a path/directory + filename). The suffixes for rollback checkpoint files are ".rb”, ".rb.1", ..., ".rb.9" and are automatically appended to rollback checkpoint files.

Default

no rollback-location

Parameters

file-url

Specifies the URL or rollback filename.

Values

local-url | remote-url
local-url	[cflash-id/][file-path] up to 200 characters, including cflash-id directory length of up to 99 characters each
remote-url	[{ftp://}login:pswd@ remote-locn/][file-path] up to 255 characters, directory length of up to 99 characters each
remote-locn	[hostname | ipv4-address | ipv6-address]
ipv4-address	a.b.c.d
ipv6-address	x:x:x:x:x:x:x:x[-interface]
	x:x:x:x:x:x:d.d.d.d[-interface]
	x - [0 to FFFF]H
	d - [0 to 255]D
	interface - up to 32 characters each, for link local addresses
cflash-id	cf1:, cf1-A:, cf1-B:, cf2:, cf2-A:, cf2-B:, cf3:, cf3-A:, cf3-B:

rollback-filename

Specifies the rollback file name.

Values

suffixed with .rb, .rb.1 up to .9 during rollback checkpoint creation

Platforms

All

Context

[Tree] (admin>redundancy rollback-sync)

Full Context

admin redundancy rollback-sync

Description

This command copies the entire set of rollback checkpoint files from the active CPM CF to the standby CPM CF.

Platforms

All

Context

[Tree] (config>redundancy rollback-sync)

Full Context

configure redundancy rollback-sync

Description

The operator can enable automatic synchronization of classic CLI rollback checkpoint files between the active CPM and standby CPM. When this automatic synchronization is enabled, a classic CLI rollback save causes the new classic CLI checkpoint file to be saved on both the active and standby CPMs. The suffixes of the old checkpoint files on both active and standby CPMs are incremented. Note that automatic sync only causes the one new checkpoint file to be copied to both CFs (the other checkpoint files are not automatically copied from active to standby but that can be done manually with admin redundancy rollback-sync).

Automatic synchronization of classic CLI rollback checkpoint files across CPMs is only performed if the rollback-location is configured as a local file-url (for example, "cf3:/rollback-files/rollback). Synchronization is not done if the rollback-location is remote.

The config redundancy synchronize {boot-env | config} and admin redundancy synchronize {boot-env | config} do not apply to classic CLI rollback checkpoint files. These commands do not manually or automatically sync classic CLI rollback checkpoint files. The dedicated rollback-sync command must be used to sync classic CLI rollback checkpoint files.

Default

no rollback-sync

Platforms

All

Context

[Tree] (config>log>file-id rollover)

Full Context

configure log file-id rollover

Description

This command configures how often an event or accounting log is rolled over or partitioned into a new file.

An event or accounting log is actually composed of multiple, individual files. The system creates a new file for the log based on the rollover time, expressed in minutes.

The retention option, expressed in hours, allows you to modify the default time to keep the file in the system. The retention time is based on the rollover time of the file.

If logs are needed to be retained for more than 16 days, use a CRON job to move the logs to a different location, either on a local drive or a remote server. For more information, contact Nokia support.

When multiple rollover commands for a file-id are entered, the last command overwrites the previous command.

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

Default

rollover 1440 retention 12

Parameters

minutes

Specifies the rollover time, in minutes.

Values

5 to 10080

retention hours

Specifies the retention period in hours, expressed as a decimal integer. The retention time is based on the time creation time of the file. The file becomes a candidate for removal once the creation datestamp + rollover time + retention time is less than the current timestamp.

Default

12

Values

1 to 500

Platforms

All

Context

[Tree] (config>qos>policer-control-policy root)

Full Context

configure qos policer-control-policy root

Description

The root node contains the policer control policies configuration parameters for the root arbiter. Within the node, the parent policer’s maximum rate limit can be set, the strict priority level, and fair threshold portions may be defined per priority level.

The root node always exists and does not need to be created.

Platforms

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

Context

[Tree] (config>router>p2mp-sr-tree>p2mp-policy root-address)

Full Context

configure router p2mp-sr-tree p2mp-policy root-address

Description

This command configures the IP address of the P2MP SR tree root node of the P2MP policy. The root tree ID and the root address uniquely identify the P2MP policy on the root node.

The no form of this command removes the root address entry.

Parameters

ip-address

Specifies the IPv4 address of the root node.

Values

a.b.c.d

Platforms

All

Context

[Tree] (config>router>p2mp-sr-tree>replication-segment root-address)

Full Context

configure router p2mp-sr-tree replication-segment root-address

Description

This command configures the replication segment with the IP address of the root node of the P2MP SR tree replication segment.

The no form of this command removes the root node address.

Parameters

ip-address

Specifies the IPv4 address.

Values

a.b.c.d

Platforms

All

Context

[Tree] (config>service>vpls>provider-tunnel>inclusive root-and-leaf)

Full Context

configure service vpls provider-tunnel inclusive root-and-leaf

Description

This command configures the node to operate as both root and leaf of the I-PMSI in a specified VPLS/B-VPLS instance.

By default, a node will behave as a leaf-only node. When the node is leaf only for the I-PMSI of type P2MP RSVP LSP, no PMSI Tunnel Attribute is included in BGP-AD route update messages and therefore no RSVP P2MP LSP is signaled but the node can join RSVP P2MP LSP rooted at other PE nodes participating in this VPLS/B-VPLS service. The user must still configure a LSP template even if the node is a leaf only.

For the I-PMSI of type mLDP, the leaf-only node will join I-PMSI rooted at other nodes it discovered but will not include a PMSI Tunnel Attribute in BGP-AD route update messages. This way a leaf-only node will forward packets to other nodes in the VPLS/B-VPLS using the point-to-point spoke-SDPs.

The no version of this command re-instates the default value.

Platforms

All

Context

[Tree] (config>service>template>vpls-sap-template>stp root-guard)

[Tree] (config>service>vpls>spoke-sdp>stp root-guard)

[Tree] (config>service>vpls>sap>stp root-guard)

Full Context

configure service template vpls-sap-template stp root-guard

configure service vpls spoke-sdp stp root-guard

configure service vpls sap stp root-guard

Description

This command specifies whether this port is allowed to become an STP root port. It corresponds to the restrictedRole parameter in 802.1Q. If set, it can cause lack of spanning tree connectivity.

Default

no root-guard

Platforms

All

Context

[Tree] (config>service>pw-template>stp root-guard)

Full Context

configure service pw-template stp root-guard

Description

This command specifies whether this port is allowed to become an STP root port. It corresponds to the restrictedRole parameter in 802.1Q. If set, it can cause lack of spanning tree connectivity.

Default

no root-guard

Platforms

All

Context

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

Full Context

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

Description

Commands in this context configure root tier parameters. Within the root-tier context, root pools can be sized using the allocation-weight command or a slope policy can be associated with a root pool.

The no form of the command restores the default allocation-weight value and default slope policy to the specified root pool. Root pool 1 has a different default weight than root pools 2 through 16. The no root-pool command fails for root pools 2 through 16 if the root pool is currently the parent of a mid-tier pool.

Parameters

root-pool-id

Specifies the root pool ID. This is a required parameter when executing the root-pool command and specifies which root pool context is being entered.

Values

1 to 16

Platforms

7750 SR-7/12/12e

Context

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

Full Context

configure qos hs-pool-policy root-tier

Description

Commands in this context configure root pool parameters. Within the root-tier context, root pools can be sized using the allocation-weight command or a slope policy can be associated with a root pool.

Platforms

7750 SR-7/12/12e

Context

[Tree] (config>mcast-mgmt>chassis-level round-robin-inactive-records)

Full Context

configure mcast-management chassis-level round-robin-inactive-records

Description

This command specifies whether initially inactive multicast records use the IOM default secondary multicast path or not. When enabled, the system redistributes newly populated inactive records among all available IOM multicast paths and multicast switch fabric planes. When disabled, the system continues to set all initially inactive multicast records to use the IOM default secondary multicast path.

The no form of this command reverts to the default.

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>aaa>diam>node>peer route)

Full Context

configure aaa diameter node peer route

Description

This command configures the index of the static route within the Diameter peer used to reach remote realms that are not directly connected to the origin realm, or to override the route preference (peer preference) of the directly-connected realms.

The no form of this command removes the route index information from the configuration.

Parameters

index

Specifies the index of the static route within the Diameter peer.

Values

1 to 15

realm-string

Specifies the destination realm reachable through this static route, up to 80 characters.

application

Specifies the ID of the Diameter application of the static route.

Values

nasreq, gy, gx

create

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

Platforms

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

Context

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

Full Context

configure router admin-tags route-admin-tag-policy

Description

This command configures a route admin tag policy.

Up to 2,000 policies can be configured per system.

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

Parameters

policy-name

The name of the route admin tag policy, up to 32 characters.

Platforms

All

Context

[Tree] (config>router>bgp>group>srv6 route-advertisement)

[Tree] (config>router>bgp>group>neighbor>srv6 route-advertisement)

Full Context

configure router bgp group segment-routing-v6 route-advertisement

configure router bgp group neighbor segment-routing-v6 route-advertisement

Description

Commands in this context configure the route advertisement options.

The no form of this command deletes the context.

Default

no route-advertisement

Platforms

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

Context

[Tree] (config>subscr-mgmt>isa-svc-chain>evpn>bgp route-distinguisher)

Full Context

configure subscriber-mgmt isa-service-chaining evpn bgp route-distinguisher

Description

This command configures the Route Distinguisher (RD) field that is signaled in NLRI in EVPN routes.

The no form of this command reverts to the default.

Parameters

auto-rd

Specifies that the system automatically generates an RD.

rd

Specifies the RD.

Values

rd: ip-addr:comm-val | 2byte-asnumber:ext-comm-val | 4byte-asnumber:comm-val

ip-addr: a.b.c.d

comm-val: [0 to 65535]

2byte-asnumber: [1 to 65535]

ext-comm-val: [0 to 4294967295]

4byte-asnumber: [1 to 4294967295]

Platforms

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

Context

[Tree] (config>service>vpls>bgp route-distinguisher)

[Tree] (config>service>epipe>bgp route-distinguisher)

Full Context

configure service vpls bgp route-distinguisher

configure service epipe bgp route-distinguisher

Description

This command configures the Route Distinguisher (RD) component that will be signaled in the MP-BGP NLRI for L2VPN and EVPN families. This value will be used for BGP-AD, BGP VPLS and BGP multi-homing NLRI if these features are configured.

If this command is not configured, the RD is automatically built using the BGP-AD VPLS ID. The following rules apply:

• if BGP AD VPLS-id is configured and no RD is configured under BGP node - RD=VPLS-ID

• if BGP AD VPLS-id is not configured then an RD value must be configured under BGP node (this is the case when only BGP VPLS is configured)

• if BGP AD VPLS-id is configured and an RD value is also configured under BGP node, the configured RD value prevails

Values and format (6 bytes, other 2 bytes of type will be automatically generated)

Alternatively, the auto-rd option allows the system to automatically generate an RD based on the bgp-auto-rd-range command configured at the service level. For BGP-EVPN enabled VPLS and Epipe services, the route-distinguisher value can also be auto-derived from the evi value (config>service>vpls>bgp-evpn>evi or config>service>epipe>bgp-evpn>evi) if this command is not configured. See the config>service>system>bgp-evpn>eth-seg>service-carving>manual evi command description for more information.

Parameters

ip-addr:comm-val

Specifies the IP address.

Values

ip-addr: a.b.c.d

comm-val: 0 to 65535

as-number:ext-comm-val

Specifies the AS number.

Values

as-number: 1 to 65535

ext-comm-val: 0 to 4294967295

auto-rd

The system will generate an RD for the service according to the IP address and range configured in the bgp-auto-rd-range command.

Platforms

All

Context

[Tree] (config>service>system>bgp-evpn route-distinguisher)

Full Context

configure service system bgp-evpn route-distinguisher

Description

This command configures the Route Distinguisher (RD) component that will be signaled in the MP-BGP NLRI for EVPN corresponding to the base EVPN instance (Ethernet Segment routes). If the route-distinguisher component is not configured, the system will use system:ip-address as the default route-distinguisher

Default

no route-distinguisher

Parameters

ip-addr:comm-val

Specifies the IP address.

Values

ip-addr: a.b.c.d

comm-val: 0 to 65535

as-number:ext-comm-val

Specifies the AS number.

Values

as-number: 1 to 65535

ext-comm-val: 0 to 4294967295

Platforms

All

Context

[Tree] (config>service>vprn>bgp-evpn>vxlan route-distinguisher)

[Tree] (config>service>vprn>bgp-evpn>mpls route-distinguisher)

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

[Tree] (config>service>vprn>bgp-ipvpn>mpls route-distinguisher)

Full Context

configure service vprn bgp-evpn vxlan route-distinguisher

configure service vprn bgp-evpn mpls route-distinguisher

configure service vprn bgp-ipvpn segment-routing-v6 route-distinguisher

configure service vprn bgp-ipvpn mpls route-distinguisher

Description

This command specifies an identifier attached to a route, which enables the user to identify the VPN to which the route belongs. Each routing instance must have a unique (within the carrier’s domain) route distinguisher (RD) associated with it.

Alternatively, the auto-rd option allows the system to automatically generate an RD based on the configure service system bgp-auto-rd-range command.

The no form of this command removes the RD configuration.

Default

no route-distinguisher

Parameters

auto-rd

Keyword that allows the system to generate an RD for the service according to the IP address and range configured in the bgp-auto-rd-range command.

rd

Specifies the route distinguisher.

Values

rd: ip-addr:comm-val | 2byte-asnumber:ext-comm-val | 4byte-asnumber:comm-val

ip-addr: a.b.c.d

comm-val: [0 to 65535]

2byte-asnumber: [1 to 65535]

ext-comm-val: [0 to 4294967295]

4byte-asnumber: [1 to 4294967295]

Platforms

7750 SR-1, 7750 SR-s

• configure service vprn bgp-evpn vxlan route-distinguisher

All

• configure service vprn bgp-ipvpn mpls route-distinguisher
• configure service vprn bgp-evpn mpls route-distinguisher

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

• configure service vprn bgp-ipvpn segment-routing-v6 route-distinguisher

Context

[Tree] (config>service>vprn route-distinguisher)

Full Context

configure service vprn route-distinguisher

Description

Platforms

All

Context

[Tree] (config>router>policy-options route-distinguisher-list)

Full Context

configure router policy-options route-distinguisher-list

Description

This command creates a list of entries used to match the RD in BGP routes of specific address families.

Parameters

name

Specifies the name of the RD list, up to 64 characters.

Platforms

All

Context

[Tree] (config>router>policy-options>policy-statement>entry>from route-distinguisher-list)

Full Context

configure router policy-options policy-statement entry from route-distinguisher-list

Description

This command configures a route distinguisher (RD) list as a match criterion for the policy statement entry.

This match condition is supported by policies applied as VRF import or BGP peer import policies. A BGP route can match a policy entry with this match criterion if the NLRI field contains an RD that is matched by at least one of the entries in the route-distinguisher-list.

BGP routes belonging to address families other than VPN-IPv4, VPN-IPv6, MCAST-VPN-IPv4, MCAST-VPN-IPv6, EVPN, FlowSpec-VPN IPv4, FlowSpec-VPN IPv6, MVPN-IPv4 or MVPN-IPv6 routes do not match policy entries with this match criterion.

Parameters

name

Specifies the (possibly parameterized) name of an RD list.

Platforms

All

Context

[Tree] (config>aaa route-downloader)

Full Context

configure aaa route-downloader

Description

Commands in this context configure a route-downloader instance. The route-downloader is a process that uses radius access-request messages to a particular server. The server returns either an access-accept or access-deny message. Access-accept messages also contain the prefixes (in the form of static blackhole routes in various formats). Only a single route-downloader object can be created.

The no form of this command removes the name from the configuration. The object must be shutdown prior to deletion. No prefix is needed to delete an existing route-download object.

Parameters

name

Specifies the name of this RADIUS route downloader.

create

This keyword is mandatory while creating an instance of the route-download object.

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>static-host>managed-routes route-entry)

[Tree] (config>service>ies>sub-if>grp-if>sap>static-host>managed-routes route-entry)

Full Context

configure service vprn subscriber-interface group-interface sap static-host managed-routes route-entry

configure service ies subscriber-interface group-interface sap static-host managed-routes route-entry

Description

This command assigns a managed route to a specified subscriber host. As a consequence, a static route pointing subscriber-host IP address as a next hop is installed in the FIB.

The no form of this command removes the respective route. By default, there are no managed routes configured.

Parameters

ip-prefix/length

Specifies the IP prefix and length.

Syntax:

ip-prefix/length:	ip-prefix	a.b.c.d
	ip-prefix-length	1 to 32

netmask

Specifies the subnet mask in dotted decimal notation.

Values

a.b.c.d (0.0.0.0 not allowed)

ipv6-prefix/prefix-length

Specifies the IPv6 prefix and prefix length.

Values

ipv6-prefix	x:x:x:x:x:x:x:x (eight 16-bit pieces)
	x:x:x:x:x:x:d.d.d.d
	x: [0 to FFFF]H
	d: [0 to 255]D
ipv6-prefix-length	1 to 128

Platforms

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

Context

[Tree] (config>router>policy-options>policy-statement>entry>cond-expr route-exists)

Full Context

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

Description

This command is used to specify a route existence expression to control evaluation of the policy entry. If the route existence expression evaluates to 'true’ the matching and action commands of the policy entry are applied as normal. If the route existence expression evaluates to 'false’ the entire policy entry is skipped and processing continues with the next entry; however, conditional expressions are only parsed when the route policy is used as a BGP export policy or VRF export policy.

Default

no route-exists

Parameters

expression

"["<pfx-list-name>”]” [all | none]

If neither the all nor the none keyword are used the match logic is 'any’ – that is, the route expression evaluates as 'true’ if any exact match entry in the referenced prefix-list has an active route in the route table associated with the policy.

all – the route expression evaluates as 'true’ only if all the exact match entries in the referenced prefix-list have an active route in the route table associated with the policy.

none – the route expression evaluates as 'true’ only if none of the exact match entries in the referenced prefix-list have an active route in the route table associated with the policy.

Platforms

All

Context

[Tree] (config>service>vprn>nat>outside>dnat-only route-limit)

[Tree] (config>router>nat>outside>dnat-only route-limit)

Full Context

configure service vprn nat outside dnat-only route-limit

configure router nat outside dnat-only route-limit

Description

This command limits the number of source routes (inside routes) that are installed on the outside in dnat-only case. In case that the number of actual routes is larger than the number of configured routes, the excess of the routes will not be installed in the routing table and a log will be raised.

The source IP addresses on the inside must be known in advance in a dnat-only instance. This is required so that the corresponding routes can be installed in the routing table and thus the downstream traffic is properly routed towards the MS-ISAs where the original translation was performed (and state is kept).

In the dnat-only case, it is mandatory that the inside (private side) and the outside (public side) are in separated VPRNs.

Default

route-limit 32768

Parameters

[1..131072]

Specifies the maximum number of source routes installed on the outside the dnat-only scenario.

Platforms

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

Context

[Tree] (config>router>bgp>group>neighbor>monitor route-monitoring)

[Tree] (config>router>bgp>group>monitor route-monitoring)

[Tree] (config>router>bgp>monitor route-monitoring)

[Tree] (config>service>vprn>bgp>monitor route-monitoring)

[Tree] (config>service>vprn>bgp>group>monitor route-monitoring)

Full Context

configure router bgp group neighbor monitor route-monitoring

configure router bgp group monitor route-monitoring

configure router bgp monitor route-monitoring

configure service vprn bgp monitor route-monitoring

configure service vprn bgp group monitor route-monitoring

Description

This command specifies if BMP sends pre-policy route monitoring messages, post-policy route monitoring messages, both types of messages, or none.

The no form of this command disables sending of route-monitoring messages.

Parameters

pre-policy

Enables sending pre-policy route monitoring messages using the pre-policy path attribute values, if available.

post-policy

Enables sending post-policy route monitoring messages using the post-policy path attribute values, if available.

Platforms

All

Context

[Tree] (config>service>vpls>bgp-evpn>mpls route-next-hop)

[Tree] (config>service>epipe>bgp-evpn>mpls route-next-hop)

[Tree] (config>service>epipe>bgp-evpn>srv6 route-next-hop)

[Tree] (config>service>vpls>bgp-evpn>srv6 route-next-hop)

Full Context

configure service vpls bgp-evpn mpls route-next-hop

configure service epipe bgp-evpn mpls route-next-hop

configure service epipe bgp-evpn segment-routing-v6 route-next-hop

configure service vpls bgp-evpn segment-routing-v6 route-next-hop

Description

This command configures the next hop of the EVPN routes.

Default

route-next-hop system-ipv4

Parameters

system-ipv4

Specifies the system IPv4 address as the next hop for the service EVPN routes.

system-ipv6

Specifies the system IPv6 address as the next hop for the service EVPN routes.

ip-address

Specifies the IPv4 address value as the next hop for the service EVPN.

Values

a.b.c.d

Platforms

All

• configure service epipe bgp-evpn mpls route-next-hop
• configure service vpls bgp-evpn mpls route-next-hop

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

• configure service epipe bgp-evpn segment-routing-v6 route-next-hop
• configure service vpls bgp-evpn segment-routing-v6 route-next-hop

Context

[Tree] (config>service>system>bgp-evpn>eth-seg route-next-hop)

Full Context

configure service system bgp-evpn ethernet-segment route-next-hop

Description

This command modifies the next hop to the configured IP address value, for the following routes:

• ES

• AD per-ES (irrespective of the evi-rt-set or evi-rt configuration mode)

The no form of the command changes the originating IP address back to the system-ip.

Default

no route-next-hop

Parameters

ip-address

Specifies an IPv4 or IPv6 address.

Values

ip-address | ipv6-address

Platforms

All

Context

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

Full Context

configure router route-next-hop-policy

Description

This command creates the context to configure route next-hop policies.

Platforms

All

Context

[Tree] (config>log route-preference)

Full Context

configure log route-preference

Description

This command specifies the primary and secondary routing preference for traffic generated for SNMP notifications and syslog messages. If the remote destination is not reachable through the routing context specified by primary route preference then the secondary routing preference will be attempted.

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

Default

no route-preference

Parameters

primary

Specifies the primary routing preference for traffic generated for SNMP notifications and syslog messages.

Default

outband

secondary

Specifies the secondary routing preference for traffic generated for SNMP notifications and syslog messages. The routing context specified by the secondary route preference will be attempted if the remote destination was not reachable by the primary routing preference, specified by primary route preference. The value specified for the secondary routing preference must be distinct from the value for primary route preference.

Default

inband

inband

Specifies that the logging utility will attempt to use the base routing context to send SNMP notifications and syslog messages to remote destinations.

outband

Specifies that the logging utility will attempt to use the management routing context to send SNMP notifications and syslog messages to remote destinations.

none

Specifies that no attempt will be made to send SNMP notifications and syslog messages to remote destinations.

Platforms

All

Context

[Tree] (config>system>security>radius route-preference)

[Tree] (config>system>security>tacplus route-preference)

[Tree] (config>system>security>ldap route-preference)

Full Context

configure system security radius route-preference

configure system security tacplus route-preference

configure system security ldap route-preference

Description

This command specifies the routing preference to reach the AAA server. If the configured option is to use both in-band and out-of-band routes, the out-of-band routes in the management routing instance are used to reach the server before the in-band routes in the Base routing instance.

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

Default

route-preference both

Parameters

both

Specifies the use of out-of-band routes before in-band routes.

inband

Specifies the use of in-band routes only.

outband

Specifies the use of out-of-band routes only.

Platforms

All

Context

[Tree] (config>router>pcep>pcc>peer route-preference)

Full Context

configure router pcep pcc peer route-preference

Description

This command specifies the routing preference to reach the PCE server. If the configured option is to use both in-band and out-of-band routes, the out-of-band routes in the management routing instance are used to reach the server before the in-band routes in the Base routing instance.

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

Default

route-preference both

Parameters

both

Specifies the use of out-of-band routes before in-band routes.

inband

Specifies the use of in-band routes only.

outband

Specifies the use of out-of-band routes only.

Platforms

All

Context

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

Full Context

configure log app-route-notifications route-recovery-wait

Description

The time delay that must pass before notifying specific CPM applications after the recovery or change of a route during normal operation.

The no form of this command disables the time-delay configuration.

Default

no route-recovery-wait

Parameters

seconds

Time delay in seconds.

Values

1 to 100

Platforms

All

Context

[Tree] (debug>router>bgp route-refresh)

Full Context

debug router bgp route-refresh

Description

This command enables debugging for BGP route-refresh.

The no form of this command disables debugging.

Parameters

neighbor ip-address

Debugs only events affecting the specified BGP neighbor.

Values

ipv4-address:

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

ipv6-address:

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

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

• x: [0 to FFFF]H

• d: [0 to 255]D

• interface: up to 32 characters for link local addresses

group name

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

Platforms

All

Context

[Tree] (debug>router>ip route-table)

Full Context

debug router ip route-table

Description

This command configures route table debugging.

Parameters

ip-prefix/prefix-length

The IP prefix for prefix list entry in dotted decimal notation.

Values

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

ipv4-prefix	a.b.c.d (host bits must be 0)
ipv4-prefix-length	0 to 32
ipv6-prefix	x:x:x:x:x:x:x:x (eight 16-bit pieces)
	x:x:x:x:x:x:d.d.d.d
	x:	[0 to FFFF]H
	d:	[0 to 255]D
ipv6-prefix-length	0 to 128

Values

The following values apply to the 7450 ESS:

ipv4-prefix	a.b.c.d (host bits must be 0)
ipv4-prefix-length	0 to 32

longer

Specifies the prefix list entry matches any route that matches the specified ip-prefix and prefix mask length values greater than the specified mask.

Platforms

All

Context

[Tree] (config>service>vprn>bgp>rib-management>ipv6 route-table-import)

[Tree] (config>service>vprn>bgp>rib-management>ipv4 route-table-import)

[Tree] (config>service>vprn>bgp>rib-management>label-ipv4 route-table-import)

Full Context

configure service vprn bgp rib-management ipv6 route-table-import

configure service vprn bgp rib-management ipv4 route-table-import

configure service vprn bgp rib-management label-ipv4 route-table-import

Description

This command specifies the name of a route policy to control the importation of active routes from the IP route table into one of the BGP RIBs.

If the route-table-import command is not configured, or if the command refers to an empty policy, all non-BGP routes from the IP route table are imported into the applicable RIB.

If the route-table-import command is configured, then routes dropped or rejected by the configured policy are not installed in the associated RIB. Rejected routes cannot be advertised to BGP peers associated with the RIB, but they can still be used to resolve BGP next-hops of routes in that RIB. If the active route for a prefix is rejected by the route-table-import policy, then the best BGP route for that prefix in the BGP RIB can be advertised to peers as though it is used.

Aggregate routes are always imported into each RIB, independent of the route-table-import policy.

Route modifications specified in the actions of a route-table-import policy are ignored and have no effect on the imported routes.

Default

no route-table-import

Parameters

policy-name

Specifies the name of a policy-statement (up to 64 characters).

Platforms

All

Context

[Tree] (config>router>bgp>rib-management>label-ipv6 route-table-import)

[Tree] (config>router>bgp>rib-management>label-ipv4 route-table-import)

[Tree] (config>router>bgp>rib-management>ipv6 route-table-import)

[Tree] (config>router>bgp>rib-management>ipv4 route-table-import)

Full Context

configure router bgp rib-management label-ipv6 route-table-import

configure router bgp rib-management label-ipv4 route-table-import

configure router bgp rib-management ipv6 route-table-import

configure router bgp rib-management ipv4 route-table-import

Description

This command specifies the name of a policy to control the importation of active routes from the IP route table into one of the BGP RIBs.

If the route-table-import command is not configured, or if the command refers to an empty policy, all non-BGP routes from the IP route table are imported into the applicable RIB.

If the route-table-import command is configured, then routes dropped or rejected by the configured policy are not installed in the associated RIB. Rejected routes cannot be advertised to BGP peers associated with the RIB, but they can still be used to resolve BGP next-hops of routes in that RIB. If the active route for a prefix is rejected by the route-table-import policy, then the best BGP route for that prefix in the BGP RIB can be advertised to peers as though it is used.

Aggregate routes are always imported into each RIB, independent of the route-table-import policy.

Route modifications specified in the actions of a route-table-import policy are ignored and have no effect on the imported routes.

Default

no route-table-import

Parameters

policy-name

Specifies the name of a policy-statement (up to 64 characters).

Platforms

All

Context

[Tree] (config>subscr-mgmt>isa-svc-chain>evpn>bgp route-target)

Full Context

configure subscriber-mgmt isa-service-chaining evpn bgp route-target

Description

This command configures route target attributes to be signaled in EVPN routes used for service chaining.

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

Parameters

export

Specifies the route target to be used by BGP in this EVPN service when exporting EVPN routes.

import

Specifies the route target to be used by BGP in this EVPN service when importing EVPN routes.

ext-community

Specifies the extended community.

Values

rd: ip-addr:comm-val | 2byte-asnumber:ext-comm-val | 4byte-asnumber:comm-val

ip-addr: a.b.c.d

comm-val: [0 to 65535]

2byte-asnumber: [1 to 65535]

ext-comm-val: [0 to 4294967295]

4byte-asnumber: [1 to 4294967295]

Platforms

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

Context

[Tree] (config>service>epipe>bgp route-target)

[Tree] (config>service>vpls>bgp-ad route-target)

[Tree] (config>service>vpls>bgp route-target)

Full Context

configure service epipe bgp route-target

configure service vpls bgp-ad route-target

configure service vpls bgp route-target

Description

This command configures the route target (RT) component that will be signaled in the related MP- BGP attribute to be used for BGP auto-discovery, BGP VPLS, BGP multi-homing and EVPN if these features are configured in this VPLS service, or for BGP multi-homing, BGP-VPWS and EVPN in case of Epipe services.

If this command is not used in VPLS services, the RT is built automatically using the VPLS ID. The extended community can have the same two formats as the VPLS ID, a two-octet AS-specific extended community, IPv4 specific extended community. For BGP EVPN enabled VPLS and Epipe services, the route target can also be auto-derived from the evi value (config>service>vpls>bgp-evpn>evi or config>service>epipe>bgp-evpn>evi) if this command is not configured.

Parameters

export ext-community

Specifies communities allowed to be sent to remote PE neighbors.

import ext-community

Specifies communities allowed to be accepted from remote PE neighbors.

Platforms

All

Context

[Tree] (config>router>bgp route-target-list)

Full Context

configure router bgp route-target-list

Description

This command specifies the route target(s) to be accepted from or advertised to peers. If the route-target-list is a non-null list, only routes with one or more of the given route targets are accepted from or advertised to peers.

The route-target-list is assigned at the global level and applies to all peers connected to the system.

This command is only applicable if the router is a route-reflector server.

The no form of this command with a specified route target community removes the specified community from the route-target-list. The no form of this command entered without a route target community removes all communities from the list.

Default

no route-target-list

Parameters

comm-id

Specifies up to 15 route target communities.

Values

[target: {ip-address:comm-val | 2byte-asnumber:ext-comm-val | 4byte-asnumber:comm-val}

where:

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

• comm-val — 0 to 65535

• 2byte-asnumber — 0 to 65535

• ext-comm-val — 0 to 4294967295

• 4byte-asnumber — 0 to 4294967295

Platforms

All

Context

[Tree] (config>vrrp>policy>priority-event route-unknown)

Full Context

configure vrrp policy priority-event route-unknown

Description

This command creates a context to configure a route unknown priority control event that monitors the existence of a specific active IP route prefix within the routing table.

The route-unknown command configures a priority control event that defines a link between the VRRP priority control policy and the Route Table Manager (RTM). The RTM registers the specified route prefix as monitored by the policy. If any change (add, delete, new next hop) occurs relative to the prefix, the policy is notified and takes correct action according to the priority event definition. If the route prefix exists and is active in the routing table according to the conditions defined, the event is in the cleared state. If the route prefix is removed, becomes inactive or fails to meet the event criteria, the event is in the set state.

The command creates a route-unknown node identified by prefix/mask-length and containing event control commands.

Multiple unique (different prefix/mask-length) route-unknown event nodes can be configured within the priority-event node up to the maximum limit of 32 events.

The route-unknown command can reference any valid IP address mask-length pair. The IP address and associated mask length define a unique IP router prefix. The dynamic monitoring of the route prefix results in one of the event operational states listed in Route-unknown Operational States.

An existing route prefix in the RTM must be active (used by the IP forwarding engine) to clear the event operational state. It may be less specific (the defined prefix may be contained in a larger prefix according to Classless Inter-Domain Routing (CIDR) techniques) if the event has the less-specific statement defined. The less specific route that incorporates the router prefix may be the default route (0.0.0.0) if the less-specific allow-default statement is defined. The matching prefix may be required to have a specific next hop IP address if defined by the event next-hop command. Finally, the source of the RTM prefix may be required to be one of the dynamic routing protocols or be statically defined if defined by the event protocol command. If an RTM prefix is not found that matches all the above criteria (if defined in the event control commands), the event is considered to be set. If a matching prefix is found in the RTM, the event is considered to be cleared.

When an event transitions from clear to set, the set is processed immediately and must be reflected in the associated virtual router instances in-use priority value. As the event transitions from clear to set, a hold-set timer is loaded with the value configured by the events hold-set command. This timer prevents the event from clearing until it expires, damping the effect of event flapping. If the event clears and becomes set again before the hold-set timer expires, the timer is reset to the hold-set value, extending the time before another clear can take effect.

The no form of the command is used to remove the specific prefix/mask-length monitoring event. The event can be removed at anytime. When the event is removed, the in-use priority of all associated virtual router instances must be reevaluated. The events hold-set timer has no effect on the removal procedure.

Default

no route-unknown — No route unknown priority control events are defined for the priority control event policy.

Parameters

ip-prefix/mask

The IP prefix address in dotted decimal notation and the subnet mask length expressed as a decimal integer associated with the IP prefix defining the route prefix to be monitored by the route unknown priority control event.

Values

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

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

ipv6-address/prefix-length

The IPv6 address of the host for which the specific event will monitor connectivity. The ipv6-address can only be monitored by a single event in this policy. The IPv6 address can be monitored by multiple VRRP priority control policies. The IPv6 address can be used in one or multiple ping requests. Each VRRP priority control host-unreachable and ping destined to the same ipv6-address is uniquely identified on a per message basis. Each session originates a unique identifier value for the ICMP echo request messages it generates. This allows received ICMP echo reply messages to be directed to the appropriate sending application.

Values

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

ipv6-address x:x:x:x:x:x:x:x (eight 16-bit pieces)
	x:x:x:x:x:x:d.d.d.d
	x:	[0..FFFF]H
prefix-length	0 to 128

Platforms

All

Context

[Tree] (config>service>vprn>subscriber-mgmt>dhcpv4 routed-subnet-transparent-forward)

[Tree] (config>router>subscriber-mgmt>dhcpv4 routed-subnet-transparent-forward)

Full Context

configure service vprn subscriber-mgmt dhcpv4 routed-subnet-transparent-forward

configure router subscriber-mgmt dhcpv4 routed-subnet-transparent-forward

Description

This command configures the transparent forwarding of DHCPv4 packets that are received on a subscriber interface with a source IP in a routed subnet that is associated with a routed IPoE session or host. Supported routed subnets are RADIUS and NASREQ framed routes or routes learned via an ESM dynamic BGP peer and managed routes associated with a static IPv4 host.

The no form of this command disables transparent forwarding of DHCPv4 packets.

Default

no routed-subnet-transparent-forward

Platforms

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

Context

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

Full Context

configure aaa l2tp-accounting-policy radius-accounting-server router

Description

This command configures the virtual router instance applicable for the set of configured RADIUS servers. This value cannot be changed once a RADIUS server is configured for this policy.

The no form of this command reverts to the default.

Default

no router

Parameters

router-instance

Specifies the router instance.

Values

router-name | vprn-svc-id
router-name	Base, management Default - Base
vprn-svc-id	1 to 2147483647

service-name

Specifies the service name, up to 64 characters.

Platforms

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

Context

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

Full Context

configure application-assurance radius-accounting-policy radius-accounting-server router

Description

This command configures the virtual router instance applicable for the set of configured RADIUS servers. This value cannot be changed once a RADIUS server is configured for this policy.

The no form of this command reverts to the default.

Default

no router

Parameters

router-instance

Specifies the router name or service ID used to specify the router instance.

service-name

Specifies the service name to identify the service, up to 64 characters.

Platforms

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

Context

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

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

Full Context

configure subscriber-mgmt radius-accounting-policy radius-accounting-server router

configure subscriber-mgmt authentication-policy radius-authentication-server router

Description

This command specifies the virtual router instance applicable for the set of configured RADIUS servers. This value cannot be changed once a RADIUS server is configured for this policy. When the value is zero, both base and management router instances are matched.

The no form of this command reverts to the default.

Parameters

router-instance

Specifies the virtual router instance

Values

router-name:	Base, management
service-id:	1 to 2147483647

service-name

Specifies the service name, up to 64 characters..

Platforms

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

Context

[Tree] (config>aaa>diam>node router)

Full Context

configure aaa diameter node router

Description

This command references the routing-instance from which diameter peering connection is initiated.

The no form of this command reverts to the default.

Default

router "Base”

Parameters

router-instance

Specifies the router instance.

Values

router-name | vprn-svc-id

router-name: Base, management Default - Base

vprn-svc-id: 1 to 2147483647

service-name

Specifies the service name, up to 64 characters.

Platforms

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

Context

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

Full Context

configure subscriber-mgmt wlan-gw tunnel-query router

Description

This command enables matching only on tunnels that are terminated in the specified routing instance.

The no form of this command disables matching on a routing instance.

Default

no router

Parameters

router-instance

Specifies the routing instance in the form of router-name or vprn-svc-id.

Values

router-name — Base

vprn-svc-id — 1 to 2147483647

Platforms

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

Context

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

Full Context

configure aaa radius-server-policy servers router

Description

This command specifies the virtual router instance applicable for the set of configured RADIUS servers. This value cannot be changed once a RADIUS server is configured for this policy.

The no form of this command reverts to the default.

Parameters

router-instance

Specifies the router instance.

Values

service-name	Service name, up to 64 characters.
	router-instance:	router-name, service-id
	router-name:	Base, management
	service-id:	1 to 2147483647

service-name

Specifies the router name service-id up to 64 characters.

Platforms

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

Context

[Tree] (config>service>ies>sub-if>grp-if>wlan-gw router)

[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw router)

Full Context

configure service ies subscriber-interface group-interface wlan-gw router

configure service vprn subscriber-interface group-interface wlan-gw router

Description

This command specifies the routing instance that wlan-gw gateway endpoint resides in.

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

Default

router

Parameters

router-instance

Specifies the identifier of the virtual router instance where the tunneled UE traffic is routed.

Platforms

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

Context

[Tree] (config router)

Full Context

configure router

Description

Commands in this context configure router parameters including interfaces, route policies and protocols. This command is also used to create CPM router instances.

For CPM router instances, this command enters or creates a user-created CPM router instance. A CPM router instance is a not a VPRN router instance. VPRN router instances are configured under configure service vprn. CPM router instances are the only type of non-VPRN router instances that can be created by a user, and they have a user-defined name. CPM router instances only use CPM/CCM ethernet ports as interfaces.

Parameters

router-instance

Specifies the router name or CPM router instance.

Values

router-instance : router name
	router-name	Base | management | cpm-vr-name
	cpm-vr-name	[32 characters maximum]

Default

Base

create

Mandatory keyword when creating a router instance. The create keyword requirement can be enabled or disabled in the environment>create context.

Platforms

All

Context

[Tree] (config>service>epipe>sap>l2tpv3-session router)

[Tree] (config>service>vpls>sap>l2tpv3-session router)

Full Context

configure service epipe sap l2tpv3-session router

configure service vpls sap l2tpv3-session router

Description

This command configures the service and L2TPv3 group to which this L2TPv3 session should be associated. The associated services are used to provide transport for the L2TPv3 tunnel. The service can be specified with either the service-name or router ID. The group name specifies the L2TPv3 group parameters that should be associated with the session.

The no form of this command deletes the router configuration.

Parameters

router-instance

Specifies the router name or service ID used to identify the router instance.

Values

router-instance: router-name or vprn-svc-id
	router-name	"Base”
	vprn-svc-id	1 to 2147483647

Default

Base

tunnel-group-name

Specifies the tunnel group name, up to 32 characters.

service-name

Specifies the service name, up to 64 characters.

Platforms

All

Context

[Tree] (debug router)

Full Context

debug router

Description

Commands in this context enable debugging of various protocols and areas of a router-instance.

Parameters

router-instance

Specifies the router name, CPM router instance, or service ID.

Values

router-name or service-id

router-instance : router-name
	router-name	Base | management | cpm-vr-name
	cpm-vr-name	[32 characters maximum]

service-id: 1 to 2147483647

Default

Base

service-name

Specifies the service name, up to 64 characters.

Platforms

All

Context

[Tree] (config>system>file-trans-prof router)

Full Context

configure system file-transmission-profile router

Description

This command specifies the routing instance that the transport protocol uses.

Default

router Base

Parameters

router-instance

Specifies the router instance on which the file transmission connection will be established.

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

Values

{router-name | vprn-svc-id}

router-name:	Base, management router-name is an alias for input only. The router-name gets replaced with an id automatically by SR OS in the configuration).
vprn-svc-id:	1 to 2147483647

Default

Base

service vprn-service-name

Identifies the service, up to 64 characters.

Platforms

All

Context

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

Full Context

configure system management-interface remote-management router

Description

This command defines the router instance in which all remote managers are reachable.

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 configures management as the router (default).

Default

router management

Parameters

router-instance

Specifies a router instance on which the remote management connection is established, up to 32 characters.

service vprn-service-instance

Specifies a VPRN service instance, up to 64 characters.

Platforms

All

Context

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

Full Context

configure system management-interface remote-management manager router

Description

This command defines the router instance in which this manager is reachable.

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 router to be inherited from the global context (config>system>management-interface>remote-management).

Default

management

Parameters

router-instance

Specifies the router instance on which the remote management connection is established for this manager, up to 32 characters.

service vprn-service-instance

Specifies a VPRN service instance, up to 64 characters.

Platforms

All

Context

[Tree] (config>isa>nat-group>inter-chassis-redundancy router)

Full Context

configure isa nat-group inter-chassis-redundancy router

Description

This command configures routing instance through which ISAs communicate between redundant nodes and synchronize their flow state.

The no form of this command removes the router instance from the configuration.

Default

no router

Parameters

router-instance

Specifies the router name or service ID for the router instance.

Values

<router-name>| <vprn-svc-id>

router-name: "Base"

vprn-svc-id: 1 to 2147483647

Platforms

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

Context

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

Full Context

configure aaa isa-radius-policy servers router

Description

This command specifies the number of times the router attempts to contact the RADIUS server for authentication, if not successful the first time.

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

Default

no router

Platforms

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

Context

[Tree] (config>mirror>mirror-dest>encap>layer-3-encap router)

Full Context

configure mirror mirror-dest encap layer-3-encap router

Description

This command specifies the routing instance into which to inject the mirrored packets. The packets are forwarded in the routing instance based on the configurable destination IP address in the inserted IP header. If a mirror-dest is configured to inject into a VPRN service, then that VPRN service cannot be deleted. A mirror-dest with layer-3-encap is set to operationally down if the configured destination IP address is not reachable via an interface in the routing instance or service configured for the mirror-dest. No changes are allowed to the router configuration once a gateway is configured. A service must already exist before it is specified as a router-instance. VPRN and IES services share the same number space for the service-id, but IES services cannot be specified as the router-instance for routable LI encap.

Forwarding of routable encapsulated LI packets out an R-VPLS interface is not supported. A mirror-dest configured with routable encapsulation can be bound to a routing instance that also has an R-VPLS bound to it but the operator must ensure that the destination of the LI packets is not reachable via any R-VPLS interfaces. Any routable encapsulated LI packets that arrive at the egress of an R-VPLS interface are discarded. Parallel use of routable LI encapsulation and R-VPLS in the same routing instance is supported as long as the mirrored packets do not egress out the R-VPLS interface.

Default

router Base

Parameters

router-instance

Specifies the router instance.

Values

<router-name> | <service-id>

router-name	"Base”, name
service-id	1 to 2147483647

service-name

Specifies the service name, up to 64 characters.

Platforms

All

Context

[Tree] (config>li>mirror-dest-template>layer-3-encap router)

Full Context

configure li mirror-dest-template layer-3-encap router

Description

This command specifies the routing instance into which to inject the mirrored packets. The packets will be forwarded in the routing instance based on the configurable destination IP address in the inserted IP header. This parameter can be overridden by RADIUS.

If a mirror destination is configured to inject into a VPRN service, that VPRN service cannot be deleted. A mirror destination with Layer 3 encapsulation will be set to operationally down if the configured destination IP address is not reachable via an interface in the routing instance or service configured for the mirror destination. A service must exist before it is specified as a router instance. VPRN and IES services share the same number space for the service ID; however, IES services cannot be specified as the router instance for routable LI encapsulation.

Default

router "Base”

Parameters

router-instance

Specifies the router instance using the router name or service ID.

Values

router-instance	router-name | vprn-svc-id
	router-name	"Base”
	vprn-svc-id	1 to 2147483647

Platforms

All

Context

[Tree] (config>li>x-interfaces>lics>lic router)

Full Context

configure li x-interfaces lics lic router

Description

This command configures the router instance that the X-interfaces must use for communication.

The no form of this command reverts to the default.

Parameters

router-name

Specifies the router name or VPRN service ID.

Values

<router-name>, <vprn-svc-id>

router-name	Base
vprn-svc-id	1 to 2147483647

Platforms

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

Context

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

Full Context

configure oam-pm session ip router

Description

This command numerically references the source context from which the TWAMP Light packet is launched. The router-instance router-instance configuration, under the same context as the router command, is the preferred method for referencing. This method references the launch context by name, and not number, or alias that converts service-name to a number.

The no form of this command restores the default value.

Parameters

router-or-service

Specifies the numerical reference to the router instance or service. Well known router-name "Base" is allowed for convenience, but mapped numerically.

Values

{router-name | vprn-svc-id}

router-name:	Base
vprn-svc-id:	1 to 2147483647

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

service-name

Specifies the alias function that allows the service-name to be used converted and stored as service ID, up to 64 characters. The parameter router-instance is preferred for specifying the router or service.

Platforms

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

Context

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

Full Context

configure cflowd collector export-filter interface-list router

Description

This command configures the interface flow data sent to this collector.

The no form of this command removes the specified interface from the interface-list filter.

Parameters

router-instance

Specifies the router instance ID associated with the interface name

Values

router-name | vprn-svc-id

router-name: Base, management Default - Base

vprn-svc-id: 1 to 2147483647

interface-name

Specifies the interface name, up to 32 characters and must start with a letter, for the router to the service interface or SAP.

ingress

Keyword to specify that ingress flows are sent to the associated Cflowd Collector.

Default

both

egress

Keyword to specify that egress flows are sent to the associated Cflowd Collector.

Default

both

both

Keyword to specify that both ingress and egress flows are sent to the associated Cflowd Collector.

Default

both

Platforms

All

Context

[Tree] (config>cflowd>collector>export-filter router)

Full Context

configure cflowd collector export-filter router

Description

This command allows the flow data from only specific router instances to be sent to the associated collector.

Multiple router instances can be configured by issuing the command multiple times with the different router-instances.

The no form of this command removes the specified router-instance restriction, which means flows from that router-instance will no longer be exported. If all router-instances are removed, then flows from all router instances are sent to the associated collector.

Default

no router

Parameters

router-instances

Specifies the router name or router instance VPRN service ID. Only "Base” is supported.

Values

router-name: Base, management Default - management

vprn-svc-id: 1 to 2147483647

Platforms

All

Context

[Tree] (config>cflowd>collector router)

Full Context

configure cflowd collector router

Description

This command configures the flow data sent to the associated collector to be sent within the specified router context. If this parameter is not specified, flow data is exported using the management routing context.

Default

router management

Parameters

router-name

Specifies the router name.

Values

Base, management

Default

management

vprn-svc-id

Specifies the router instance VPRN service ID.

Values

1 to 2147483647

Platforms

All

Context

[Tree] (config>filter>redirect-policy router)

Full Context

configure filter redirect-policy router

Description

This command enhances VRF support in redirect policies. When a router instance is specified, the configured destination tests are run in the specified router instance, and the PBR action is executed in the specified router instance. If no destination is active or if the hardware does not support PBR action "next-hop router”, action forward will be executed (i.e. routing will be performed in the context of the incoming interface routing instance).

The no form of the command preserves backward-compatibility. Tests always run in the "Base” routing instance context, and the PBR action executes in the routing context of the ingress interface that the filter using this redirect policy is deployed on.

Default

no router

Parameters

router-instance

Specifies a router instance in the form of router-name or service-id.

Values

router-name — Base

service-id — Specifies an existing Layer 3 service [1 to 2147483647]

service-name

Specifies the name of a configured Layer 3 service.

Platforms

All

Context

[Tree] (config>log>filter>entry>match router)

Full Context

configure log filter entry match router

Description

This command specifies the log event matches for the router instance using a special vrtr-name format used by the logging system.

The no form of this command removes the log event matches.

Parameters

eq

Determines if the matching criteria should be equal to the specified value.

neq

Determines if the matching criteria should not be equal to the specified value.

router-instance

Specifies a router name, up to 32 characters, to be used in the match criteria. The router-instance in this command is a name for a router instance in a special format used in the logging system (called the vrtr-name). Examples of vrtr-names include Base and vprn101 (where 101 is the service-id of the VPRN service). It represents the router instance that generated the log event.

regexp

Specifies the type of string comparison to use to determine if the log event matches the value of the specified router instance. When the regexp keyword is specified, the string in the router command is a regular expression string that is matched against the vrtr-name string in the log event being filtered.

Platforms

All

Context

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

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

Full Context

configure system security management-access-filter ipv6-filter entry router

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

Description

This command configures a router name or service ID to be used as a management access filter match criterion.

The no form the command removes the router name or service ID from the match criteria.

Parameters

router-instance

Specifies one of the following parameters for the router instance:

router-name — Specifies a router name or CPM router instance, up to 32 characters to be used in the match criteria.

Values	"Base” | "management” | "vpls-management”
Default	Base

vprn-svc-id — Specifies a CPM router instance to be used in the match criteria.

Values

1 to 2147483647

service name

Specifies an existing service name, up to 64 characters.

Platforms

All

Context

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

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

Full Context

configure system security cpm-filter ipv6-filter entry match router

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

Description

This command specifies a router name or a service-id to be used in the match criteria.

Default

no router

Parameters

router-instance

Specifies one of the following parameters for the router instance:

router-name — Specifies a router name up to 32 characters to be used in the match criteria.

service-id — Specifies an existing service ID to be used in the match criteria.

Values

1 to 2147483647

service-name

Specifies an existing service name, up to 64 characters.

Platforms

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

Context

[Tree] (config>bmp>station>connection router)

Full Context

configure bmp station connection router

Description

This command configures the router instance to be used to connect to the associate BMP monitoring station.

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

Parameters

service-name

Specifies the name associated with the VPRN service through which the BMP monitoring station connection should traverse.

router-instance

Specifies the routing instance where the lead pool resides.

Values

router-name | vprn-service-id

router-name: "Base" Default - Base

vprn-svc-id: 1 to 2147483647

service-name: The service name up to 64 characters in length.

Platforms

All

Context

[Tree] (config>mirror>mirror-dest>pcap router)

Full Context

configure mirror mirror-dest pcap router

Description

This command configures the destination router name for the FTP transmission of the PCAP file.

The no form of this command configures the router name to management, which is the default.

Default

router management

Parameters

router-name

Specifies the router name.

Values

Base, management

Platforms

All

Context

[Tree] (config>service>vprn router-advertisement)

Full Context

configure service vprn router-advertisement

Description

This command configures router advertisement properties. By default, it is disabled for all IPv6 enabled interfaces.

The no form of this command disables all IPv6 interface. However, the no interface interface-name command disables a specific interface.

Default

no router-advertisement

Platforms

All

Context

[Tree] (config>router router-advertisement)

Full Context

configure router router-advertisement

Description

This command configures router advertisement properties. By default, it is disabled for all IPv6 enabled interfaces.

The no form of this command disables all IPv6 interface. However, the no interface interface-name command disables a specific interface.

Default

disabled

Platforms

All

Context

[Tree] (config>subscr-mgmt>loc-user-db>ipoe>host router-advertisement-policy)

[Tree] (config>subscr-mgmt>loc-user-db>ppp>host router-advertisement-policy)

Full Context

configure subscriber-mgmt local-user-db ipoe host router-advertisement-policy

configure subscriber-mgmt local-user-db ppp host router-advertisement-policy

Description

This command applies an RA policy to the host.

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

Parameters

policy

Specifies the policy name, up to 32 characters.

Platforms

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

Context

[Tree] (config>subscr-mgmt router-advertisement-policy)

Full Context

configure subscriber-mgmt router-advertisement-policy

Description

This command creates a router advertisement policy or enters the context to configure a router advertisement policy. The keyword create is mandatory when creating a router advertisement policy the first time.

The no form of this command deletes the specified router advertisement policy.

Parameters

name

Specifies the router advertisement policy name 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.

create

Specifies the keyword used to create the router advertisement policy. The create keyword requirement can be enabled or disabled in the environment>create context.

Platforms

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

Context

[Tree] (config>service>vprn>sub-if>grp-if>ipv6 router-advertisements)

[Tree] (config>service>vprn>sub-if>ipv6 router-advertisements)

[Tree] (config>service>ies>sub-if>ipv6 router-advertisements)

[Tree] (config>service>ies>sub-if>grp-if>ipv6 router-advertisements)

Full Context

configure service vprn subscriber-interface group-interface ipv6 router-advertisements

configure service vprn subscriber-interface ipv6 router-advertisements

configure service ies subscriber-interface ipv6 router-advertisements

configure service ies subscriber-interface group-interface ipv6 router-advertisements

Description

This command enables IPv6 router advertisements for this interface.

The no form of this command disables the router advertisements.

Default

router-advertisements

Platforms

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

Context

[Tree] (config>service>vprn>bgp router-id)

[Tree] (config>service>vprn router-id)

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

Full Context

configure service vprn bgp router-id

configure service vprn router-id

configure service vprn ospf router-id

Description

This command sets the router ID for a specific VPRN context.

When configuring the router ID in the base instance of OSPF it overrides the router ID configured in the config>router context. The default value for the base instance is inherited from the configuration in the config>router context. If the router ID in the config>router context is not configured, the following applies:

• The system uses the system interface address (which is also the loopback address).

• If a system interface address is not configured, use the last 32 bits of the chassis MAC address.

If neither the router ID nor system interface are defined, the router ID from the base router context is inherited.

This is a required command when configuring multiple instances and the instance being configured is not the base instance.

When configuring a new router ID, the instance is not automatically restarted with the new router ID. The next time the instance is initialized, the new router ID is used.

To force the new router ID to be used, issue the shutdown and no shutdown commands for the instance, or reboot the entire router.

It is possible to configure an SR OS to operate with an IPv6 only BOF and no IPv4 system interface address. When configured in this manner, the operator must explicitly define IPv4 router IDs for protocols such as OSPF and BGP as there is no mechanism to derive the router ID from an IPv6 system interface address.

The no form of this command removes the router ID definition from the given VPRN context.

Default

no router-id

Parameters

ip-address

The IP address must be given in dotted decimal notation.

Platforms

All

Context

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

Full Context

configure service vprn isis router-id

Description

This command sets the router ID for a specific VPRN context.

If neither the router ID nor system interface are defined, the router ID from the base router context is inherited.

The no form of this command removes the router ID definition from the given VPRN context.

Default

no router-id

Parameters

ip-address

The IP address must be given in dotted decimal notation.

Platforms

All

Context

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

Full Context

configure router mpls srlg-database router-id

Description

Commands in this context configure the link members of SRLG groups for a specific router in the network. The user must also use this command to enter the local interface SRLG membership into the user SRLG database. Use by CSPF of all interface SRLG membership information of a specific router ID may be temporarily disabled by shutting down the node. If this occurs, CSPF assumes these interfaces have no SRLG membership association.

The no form of this command will delete all interface entries under the router ID.

Parameters

ip-address

Specifies the router ID for this system. This must be the router ID configured under the base router instance, the base OSPF instance or the base IS-IS instance.

Platforms

All

Context

[Tree] (config>router router-id)

Full Context

configure router router-id

Description

This command configures the router ID for the router instance.

The router ID is used by both OSPF and BGP routing protocols in this instance of the routing table manager. IS-IS uses the router ID value as its system ID.

When configuring a new router ID, protocols are not automatically restarted with the new router ID. The next time a protocol is initialized, the new router ID is used. This can result in an interim period of time when different protocols use different router IDs.

It is possible to configure SR OS to operate with an IPv6 only BOF and no IPv4 system interface address. When configured in this manner, the operator must explicitly define IPv4 router IDs for protocols such as OSPF and BGP as there is no mechanism to derive the router ID from an IPv6 system interface address.

To force the new router ID to be used, issue the shutdown and no shutdown commands for each protocol that uses the router ID, or restart the entire router.