This command moves the context back one level of the command hierarchy. For example, if the current level is the config router ospf context, the back command moves the cursor to the config router context level.
This command echoes arguments on the command line. The primary use of this command is to allow messages to be displayed to the screen in files executed with the exec command.
See the description for the admin-password command. If the admin-password is configured in the config>system>security>password context, then any user can enter a special administrative mode by entering the enable-admin command.
enable-admin is in the default profile. By default, all users are given access to this command.
Once the enable-admin command is entered, the user is prompted for a password. If the password matches, the user is given unrestricted access to all the commands.
The minimum length of the password is determined by the minimum-length command. The complexity requirements for the password are determined by the complexity command.
The following shows a password configuration example:
There are two ways to verify that a user is in the enable-admin mode:
This command executes the contents of a text file as if they were CLI commands entered at the console.
exec commands do not have no versions.
Related Commands:
boot-bad-exec: Use this command to configure a URL for a CLI script to exec following a failed configuration boot.
boot-good-exec: Use this command to configure a URL for a CLI script to exec following a successful configuration boot.
<<: Stdin can be used as the source of commands for the exec command. When stdin is used as the exec command input, the command list is terminated with <Ctrl-C>, “EOF<Return>” or “eof_string<Return>”.
If an error occurs entering an exec file sourced from stdin, all commands after the command returning the error will be silently ignored. The exec command will indicate the command error line number when the stdin input is terminated with an end-of-file input.
This command returns to the context from which the current level was entered. For example, to navigate to the current level on a context by context basis, then the exit command only moves the cursor back one level.
When navigating to the current level by entering a command string, the exit command returns the cursor to the context in which the command was initially entered.
The exit all command moves the cursor all the way back to the root level.
This command provides a brief description of the help system. The following information is shown:
Available editing keystrokes:
Available global commands:
Use the following CLI commands to display more information about commands and command syntax:
This command lists the last 30 commands entered in this session.
Re-execute a command in the history with the !n command, where n is the line number associated with the command in the history output.
Example:
This command displays the running configuration for the configuration context.
The output of this command is similar to the output of the admin display-config command. This command, however, lists the configuration of the context where it is entered and all branches below that context level.
By default, the command only enters the configuration parameters that vary from the default values. The detail keyword causes all configuration parameters to be displayed. The “include-dynamic” objective keyword includes configuration parameters from dynamic sources such as VSD or dynamic data service Python scripts. These dynamic configuration parameters are not saved in the configuration file.
Example:
This command logs out of the router session.
When the logout command is issued from the console, the login prompt is displayed, and any log IDs directed to the console are discarded. When the console session resumes (regardless of the user), the log output to the console resumes.
When a Telnet session is terminated from a logout command, all log IDs directed to the session are removed. When a user logs back in, the log IDs must be re-created.
This command changes a user’s CLI login password.
When a user logs in after the administrator forces a new-password-at-login, or the password has expired (aging), then this command is automatically invoked.
When invoked, the user is prompted to enter the old password, the new password, and then the new password again to verify the correct input.
If a user fails to create a new password after the administrator forces a new-password-at-login or after the password has expired, the user is not allowed to access the CLI.
A user cannot configure a non-conformant password for themselves using the global password command. A password value that does not conform to the minimum-length or other password complexity rules can be configured using the config>system>security>user>password command (for example, by an administrator), but a warning is provided in the CLI. This allows, for example, an administrator to configure a non-conformant password for a user.
This command is the TCP/IP utility that is used to verify IP reachability.
The detail parameter includes in the output the interface on which the ping reply was received.
Example output:
router-instance: router name or service-id | ||
router-name | “Base” | “management” | cpm-vr-name | “vpls-management” | |
cpm-vr-name | [32 characters maximum] | |
vprn-service-id | 1 to 2147483647 |
This command displays the present or previous working context of the CLI session. The pwc command provides a user who is in the process of dynamically configuring a chassis a way to display the current or previous working context of the CLI session. The pwc command displays a list of the CLI nodes that hierarchically define the current context of the CLI instance of the user.
The following example is from a 7750 SR:
When the previous keyword is specified, the previous context displays. This is the context entered by the CLI parser upon execution of the exit command. The current context of the CLI is not affected by the pwc command.
The following example is from a 7450 ESS:
This command causes the console session to pause operation (sleep) for 1 second (default) or for the specified number of seconds.
sleep 1
This command initiates a client SSH session with the remote host and is independent from the administrative or operational state of the SSH server. However, to be the target of an SSH session, the SSH server must be operational. This command also allows the user to initiate a SSH session, with a key re-exchange, based on maximum megabytes or minutes, whichever occurs first. If the re-exchange options are not set, the default behavior will not perform a key re-exchange.
Quitting SSH while in the process of authentication is accomplished by either executing a ctrl-c or "~." (tilde and dot), assuming the “~” is the default escape character for SSH session.
host: user@hostname - [255 chars max] | |
user | 32 chars max |
hostname | [dns-name | ipv4-address | ipv6-address] |
ipv4-address | a.b.c.d |
ipv6-address | x:x:x:x:x:x:x:x[-interface] |
x:x:x:x:x:x:d.d.d.d[-interface] | |
x - [0 to FFFF]H | |
d - [0 to 255]D | |
interface - 32 chars max, mandatory for link local addresses | |
dns-name | 128 chars max |
router-instance: router-name or vprn-svc-id | ||
router-name | “Base”, “management”, “vpls-management” | |
vprn-svc-id | 1 to 2147483647 |
This command opens a Telnet session to a remote host. Telnet servers in SR-series networks limit Telnet clients to three attempts to login; this number is not user configurable. The Telnet server disconnects the Telnet client session after three attempts.
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 ipv6-address interface: 32 chars max, mandatory for link local addresses |
dns-name | 128 chars max |
Note: IPv6 applies to the 7750 SR and 7950 XRS. |
router-instance : router-name or vprn-svc-id | ||
router-name | “Base”, “management”, vpls-management” | |
vprn-svc-id | 1 to 2147483647 |
The TCP/IP traceroute utility determines the route to a destination address. Note that aborting a traceroute with the <Ctrl-C> command could require issuing a second <Ctrl-C> command before the prompt is returned.
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 |
dns-name | 63 characters maximum |
Note: IPv6 applies to the 7750 SR and 7950 XRS. |
ipv4-address | a.b.c.d | |
ipv6-address | x:x:x:x:x:x:x:x (eight 16-bit pieces) x:x:x:x:x:x:d.d.d.d | x: [0 to FFFF]H d: [0 to 255]D |
router-instance : router-name or service-id | ||
router-name | Base, management, cpm-vr-name, vpls-management | |
cpm-vr-name | [32 characters maximum] | |
vprn-service-id | 1 to 2147483647 |
This command displays the command hierarchy structure of the current working context.
This command sends a console message to a specific user or to all users with active console sessions.
This command monitors policer statistics in an ingress FP queue group.
Displays monitor command output of traffic statistics for Cross Connect Aggregation Groups (CCAGs) ports.
This command displays monitor command output for CPM filters.
This command displays monitor command statistics for IP filter entries.
This command displays monitor command statistics for IPv6 filter entries.
This command displays monitor command statistics for MAC filter entries.
This command enables the context to configure criteria to monitor IP and MAC filter statistics.
This command enables IP filter monitoring. The statistical information for the specified IP filter entry displays at the configured interval until the configured count is reached.
The first screen displays the current statistics related to the specified IP filter. The subsequent statistical information listed for each interval is displayed as a delta to the previous display.
When the keyword rate is specified, the rate-per-second for each statistic is displayed instead of the delta.
Monitor commands are similar to show commands but only statistical information displays. Monitor commands display the selected statistics according to the configured number of times at the interval specified.
The following output is an example of filter IP information.
This command enables IPv6 filter monitoring. The statistical information for the specified IPv6 filter entry displays at the configured interval until the configured count is reached.
The first screen displays the current statistics related to the specified IPv6 filter. The subsequent statistical information listed for each interval is displayed as a delta to the previous display.
When the keyword rate is specified, the rate-per-second for each statistic is displayed instead of the delta.
Monitor commands are similar to show commands but only statistical information displays. Monitor commands display the selected statistics according to the configured number of times at the interval specified.
The following output is an example of filter IPv6 information.
This command enables MAC filter monitoring. The statistical information for the specified MAC filter entry displays at the configured interval until the configured count is reached.
The first screen displays the current statistics related to the specified MAC filter. The subsequent statistical information listed for each interval is displayed as a delta to the previous display. When the keyword rate is specified, the rate-per-second for each statistic is displayed instead of the delta.
Monitor commands are similar to show commands but only statistical information displays. Monitor commands display the selected statistics according to the configured number of times at the interval specified.
The following output is an example of filter mac information.
This command monitors traffic statistics for Link Aggregation Group (LAG) ports. Statistical information for the specified LAG ID(s) displays at the configured interval until the configured count is reached.
The first screen displays the current statistics related to the specified LAG ID. The subsequent statistical information listed for each interval is displayed as a delta to the previous display. When the keyword rate is specified, the rate-per-second for each statistic is displayed instead of the delta.
Monitor commands are similar to show commands but only statistical information displays. Monitor commands display the selected statistics according to the configured number of times at the interval specified.
The following output is an example of monitor lag command information.
This command enables the context to monitor management-access filters. These filters are configured in the config>system>security>mgmt-access-filter context.
This command monitors statistics for the MAF IP filter entry.
This command monitors statistics for the MAF IPv6 filter entry.
This command monitors statistics for the MAF MAC filter entry.
This command enables port traffic monitoring. The specified port(s) statistical information displays at the configured interval until the configured count is reached.
The first screen displays the current statistics related to the specified port(s). The subsequent statistical information listed for each interval is displayed as a delta to the previous display.
When the rate is specified, the rate-per-second for each statistic is displayed instead of the delta.
Monitor commands are similar to show commands but only statistical information displays. Monitor commands display the selected statistics according to the configured number of times at the interval specified.
port-id | slot/mda/port [.channel] | ||
eth-sat-id | esat-id/slot/port | ||
esat | keyword | ||
id | 1 to 20 | ||
pxc-id | pxc-id.sub-port | ||
pxc | keyword | ||
id | 1 to 64 | ||
sub-port | a, b | ||
aps-id | aps-group-id[.channel] | ||
aps | keyword | ||
group-id | 1 to 64 (16 for 7750 SR-c12 and 7750 SR-c4) | ||
bundle-id | bundle-type-slot/mda.bundle-num | ||
bundle | keyword | ||
type | ima, ppp | ||
bundle-num | 1 to 128 (16 for 7750 SR-c12 and 7750 SR-c4) |
The following output is an example of monitor port information.
This command enables the context to configure criteria to monitor QoS scheduler statistics for specific customers and SAPs.
This command enables the context to configure monitor commands for arbiter statistics.
This command monitors arbiter statistics in an ingress FP queue group.
This command monitors arbiter statistics for a customer site.
This command monitors arbiter statistics for a customer site.
This command monitors arbiter statistics for a SAP.
This command monitors arbiter statistics for a subscriber.
This command monitors expanded secondary shaper statistics.
This command enables the context to configure monitor commands for scheduler statistics.
This command monitors scheduler statistics per customer multi-service-site. The first screen displays the current statistics related to the specified customer ID and customer site name. The subsequent statistical information listed for each interval is displayed as a delta to the previous display. When the keyword rate is specified, the rate-per-second for each statistic is displayed instead of the delta. Monitor commands are similar to show commands but only statistical information displays. These commands display selected statistics per the configured number of times at the interval specified.
This command monitors scheduler statistics in a port queue group or a VPORT.
Use this command to monitor scheduler statistics for a SAP at the configured interval until the configured count is reached.
The first screen displays the current statistics related to the specified SAP. The subsequent statistical information listed for each interval is displayed as a delta to the previous display.
When the keyword rate is specified, the rate-per-second for each statistic is displayed instead of the delta.
Monitor commands are similar to show commands but only statistical information displays. Monitor commands display the selected statistics according to the configured number of times at the interval specified.
This command monitors scheduler statistics for a SAP encap-group.
This command monitors scheduler statistics for a subscriber.
This command enables the context to configure criteria to monitor statistical information for a variety of routing protocols.
router-name: | Base, management, cpm-vr-name, vpls-management |
vprn-service-id: | 1 to 2147483647 |
cpm-vr-name | 32 chars max |
This command monitors commands for the BGP instance.
This command displays statistical BGP neighbor information at the configured interval until the configured count is reached.
The first screen displays the current statistics related to the specified neighbor(s). The subsequent statistical information listed for each interval is displayed as a delta to the previous display.
When the keyword rate is specified, the rate-per-second for each statistic is displayed instead of the delta.
Monitor commands are similar to show commands but only statistical information displays. Monitor commands display the selected statistics according to the configured number of times at the interval specified.
The following output is an example of BGP neighbor information.
This command monitors commands for the ISIS instance.
This command displays statistical IS-IS traffic information at the configured interval until the configured count is reached.
The first screen displays the current statistics related to the specified router statistics. The subsequent statistical information listed for each interval is displayed as a delta to the previous display. When the keyword rate is specified, the rate-per-second for each statistic is displayed instead of the delta.
Monitor commands are similar to show commands but only statistical information displays. Monitor commands display the selected statistics according to the configured number of times at the interval specified.
The following output is an example of ISIS statistics.
This command monitors commands for the LDP instance.
This command monitors egress statistics for LDP FEC prefixes.
ipv4-prefix | a.b.c.d |
ipv4-prefix-le | 0 to 32 |
ipv6-prefix | x:x:x:x:x:x:x:x (eight 16-bit pieces) |
x:x:x:x:x:x:d.d.d.d | |
x: [0 to FFFF] H | |
d: [0 to 255] D | |
ipv6-prefix-le | 0 to 128 |
This command displays statistical information for LDP sessions at the configured interval until the configured count is reached.
The first screen displays the current statistics related to the specified LDP session(s). The subsequent statistical information listed for each interval is displayed as a delta to the previous display.
When the keyword rate is specified, the rate-per-second for each statistic is displayed instead of the delta.
Monitor commands are similar to show commands but only statistical information displays. Monitor commands display the selected statistics according to the configured number of times at the interval specified.
ipv4-address | label-space | |
ipv6-address | [label-space] | |
label-space | 0 to 65535 | |
ipv4-address | a.b.c.d | |
ipv6-address | x:x:x:x:x:x:x:x (16 eight-bit pieces) | |
x:x:x:x:x:x:d.d.d.d | ||
x: [0 to FFFF] H | ||
d: [0 to 255] D |
The following output is an example of LDP session information.
Monitor statistics for LDP instance at the configured interval until the configured count is reached.
The first screen displays the current statistics related to the LDP statistics. The subsequent statistical information listed for each interval is displayed as a delta to the previous display. When the keyword rate is specified, the rate-per-second for each statistic is displayed instead of the delta.
Monitor commands are similar to show commands but only statistical information displays. Monitor commands display the selected statistics according to the configured number of times at the interval specified.
The following output is an example of LDP statistics information.
This commands monitors commands for the MPLS instance.
This command displays statistics for MPLS interfaces at the configured interval until the configured count is reached.
The first screen displays the current statistics related to the MPLS interface(s). The subsequent statistical information listed for each interval is displayed as a delta to the previous display. When the keyword rate is specified, the rate-per-second for each statistic is displayed instead of the delta.
Monitor commands are similar to show commands but only statistical information displays. Monitor commands display the selected statistics according to the configured number of times at the interval specified.
The following output is an example of MPLS interface information.
This command displays egress statistics for LSP interfaces at the configured interval until the configured count is reached.
no lsp-egress-stats
The following output is an example of LSP egress statistics information.
This command displays ingress statistics for LSP interfaces at the configured interval until the configured count is reached.
The following output is an example of LSP ingress statistics information.
This command monitors MPLS TP LSP egress statistics.
This command monitors MPLS TP LSP ingress statistics.
This command enables the context to configure monitor commands for the OSPF instance.
This command enables the context to configure monitor commands for the OSPF3 instance.
ospf-instance | 0 to 31, 64 to 95 | |
0 to 31 | ipv6-unicast address-family | |
64 to 95 | ipv4-unicast address-family |
This command displays statistics for OSPF interfaces at the configured interval until the configured count is reached.
The first screen displays the current statistics related to the OSPF interface(s). The subsequent statistical information listed for each interval is displayed as a delta to the previous display.
When the keyword rate is specified, the rate-per-second for each statistic is displayed instead of the delta.
Monitor commands are similar to show commands but only statistical information displays. Monitor commands display the selected statistics according to the configured number of times at the interval specified.
The following output is an example of OSPF interface information.
This command displays statistical OSPF neighbor information at the configured interval until the configured count is reached.
The first screen displays the current statistics related to the specified OSPF neighbors. The subsequent statistical information listed for each interval is displayed as a delta to the previous display.
When the keyword rate is specified, the rate-per-second for each statistic is displayed instead of the delta.
Monitor commands are similar to show commands but only statistical information displays. Monitor commands display the selected statistics according to the configured number of times at the interval specified.
The following output is an example of OSPF neighbor information.
This command displays statistical OSPF3 neighbor information at the configured interval until the configured count is reached.
The first screen displays the current statistics related to the specified OSPF3 neighbor(s). The subsequent statistical information listed for each interval is displayed as a delta to the previous display.
When the keyword rate is specified, the rate-per-second for each statistic is displayed instead of the delta.
Monitor commands are similar to show commands but only statistical information displays. Monitor commands display the selected statistics according to the configured number of times at the interval specified.
This command displays statistical OSPF virtual link information at the configured interval until the configured count is reached.
The first screen displays the current statistics related to the specified neighbor(s). The subsequent statistical information listed for each interval is displayed as a delta to the previous display.
When the keyword rate is specified, the rate-per-second for each statistic is displayed instead of the delta.
Monitor commands are similar to show commands but only statistical information displays. Monitor commands display the selected statistics according to the configured number of times at the interval specified.
This command displays statistical OSPF virtual neighbor information at the configured interval until the configured count is reached.
The first screen displays the current statistics related to the specified OSPF virtual neighbor router. The subsequent statistical information listed for each interval is displayed as a delta to the previous display.
When the keyword rate is specified, the rate-per-second for each statistic is displayed instead of the delta.
Monitor commands are similar to show commands but only statistical information displays. Monitor commands display the selected statistics according to the configured number of times at the interval specified.
This command monitors commands for the PIM instance.
This command monitors statistics for a PIM source group.
This command monitors commands for the RIP instance.
This command displays statistical RIP neighbor information at the configured interval until the configured count is reached.
The first screen displays the current statistics related to the specified RIP neighbor(s). The subsequent statistical information listed for each interval is displayed as a delta to the previous display. When the keyword rate is specified, the rate-per-second for each statistic is displayed instead of the delta.
Monitor commands are similar to show commands but only statistical information displays. Monitor commands display the selected statistics according to the configured number of times at the interval specified.
This command monitors commands for the RSVP instance.
This command displays statistics for RSVP interfaces at the configured interval until the configured count is reached.
The first screen displays the current statistics related to the RSVP interface(s). The subsequent statistical information listed for each interval is displayed as a delta to the previous display. When the keyword rate is specified, the rate-per-second for each statistic is displayed instead of the delta.
Monitor commands are similar to show commands but only statistical information displays. Monitor commands display the selected statistics according to the configured number of times at the interval specified.
This command enables the context to configure criteria to monitor VRRP statistical information for a VRRP enabled on a specific interface.
This command monitors statistics for a VRRP instance.
This command enables the context to configure criteria to monitor specific service SAP criteria.
This command displays statistics for a specific service, specified by the service-id, at the configured interval until the configured count is reached.
The first screen displays the current statistics related to the service-id. The subsequent statistical information listed for each interval is displayed as a delta to the previous display. When the keyword rate is specified, the rate-per-second for each statistic is displayed instead of the delta.
Monitor commands are similar to show commands but only statistical information displays. Monitor commands display the selected statistics according to the configured number of times at the interval specified.
This command monitors statistics for a SAP associated with this service.
This command displays statistics for a specific SAP, identified by the port-id and encapsulation value, at the configured interval until the configured count is reached.
The first screen displays the current statistics related to the SAP. The subsequent statistical information listed for each interval is displayed as a delta to the previous display. When the keyword rate is specified, the rate-per-second for each statistic is displayed instead of the delta.
Monitor commands are similar to show commands but only statistical information displays. Monitor commands display the selected statistics according to the configured number of times at the interval specified.
:null | port-id | bundle-id | bpgrp-id | lag-id | aps-id | ||
dot1q | port-id | bundle-id | bpgrp-id | lag-id | aps-id | pw-id:[qtag1|cp-conn-prof-id] | ||
qinq | port-id | bundle-id | bpgrp-id | lag-id | pw-id:[qtag1 cp-conn-prof-id].[qtag2 | cp-conn-prof-id] | ||
cp | keyword | ||
conn-prof-id | 1 to 8000 | ||
atm | port-id | aps-id [:vpi/vci | vpi | vpi1.vpi2 | cp.conn-prof-id] | ||
cp | keyword | ||
conn-prof-id | 1 to 8000 | ||
frame | port-id | aps-id:dlci | ||
cisco-hdlc | slot/mda/port.channel | ||
cem | slot/mda/port.channel | ||
ima-grp | bundle-id [:vpi/vci | vpi | vpi1.vpi2 | cp.conn-prof-id] | ||
cp | keyword | ||
conn-prof-id | 1 to 8000 | ||
port-id | slot/mda/port[.channel] esat-id/slot/port pxc-id.sub-port | ||
bundle-id | bundle-type-slot/mda.-bundle-nu | ||
bundle | keyword | ||
type | ima | fr | ppp | ||
bundle-num | 1 to 336 | ||
bpgrp-id | bpgrp-type-bpgrp-num | ||
bgrp | keyword | ||
type | ima | ppp | ||
bgrp-num | 1 to 2000 | ||
aps-id | aps-group-id[.channel] | ||
aps | keyword | ||
group-id | 1 to 128 | ||
ccag-id | ccag-id.path-id[cc-type]:cc-id | ||
ccag | keyword | ||
id | 1 to 8 | ||
path-id | a | b | ||
cc-type | .sap-net | .net-sap | ||
cc-id | 1 to 4094 | ||
eth-tunnel | eth-tunnel-id[:eth-tun-sap-id] | ||
id | 1 to 1024 | ||
eth-tun-sap-id | 0 to 4094 | ||
lag-id | lag-id | ||
lag | keyword | ||
id | 1 to 800 | ||
pw-id | pw-id | ||
pw | keyword | ||
id | 1 to 10239 | ||
qtag1 | * | 0 to 4094 | ||
qtag2 | * | null | 0 to 4094 | ||
vpi | 0 to 4095 (NNI) | ||
0 to 255 (UNI) | |||
vci | 1 | 2 | 5 to 65535 | ||
dlci | 16 to 1022 | ||
tunnel-id | tunnel-id.private | public:tag | ||
tunnel | keyword | ||
id | 1 to 16 | ||
tag | 0 to 4094 |
If the card in the slot has XMAs/MDAs installed, the port-id must be in the slot_number/MDA_number/port_number format. For example, 6/2/3 specifies port 3 on XMA/MDA 2 in slot 6.
The port-id must reference a valid port type. When the port-id parameter represents SONET/SDH and TDM channels, the port ID must include the channel ID. A period “.” separates the physical port from the channel-id. The port must be configured as an access port. Channels are supported on the 7750 SR.
If the SONET/SDH port is configured as clear-channel then only the port is specified.
The command syntax must be configured as follows:
bundle-id: bundle-type-slot-id/mda-slot.bundle-num
bundle-id value range: 1 to 128
For example:
The command syntax must be configured as follows:
bpgrp-id: | bpgrp-type-bpgrp-num |
type: | ima |
bpgrp-num value range: | 1 to 1280 |
Example:
qtag1: | 0 to 4094 |
qtag2 : | * | 0 to 4094 |
Port Type | Encap-Type | Allowed Values | Comments |
Ethernet | Null | 0 | The SAP is identified by the port. |
Ethernet | Dot1q | 0 to 4094 | The SAP is identified by the 802.1Q tag on the port. Note that a 0 qtag1 value also accepts untagged packets on the dot1q port. |
Ethernet | QinQ | qtag1: 0 to 4094 qtag2: 0 to 4094 | The SAP is identified by two 802.1Q tags on the port. Note that a 0 qtag1 value also accepts untagged packets on the dot1q port. |
SONET/SDH | IPCP | — | The SAP is identified by the channel. No BCP is deployed and all traffic is IP. |
SONET/SDH TDM | BCP-Null | 0 | The SAP is identified with a single service on the channel. Tags are assumed to be part of the customer packet and not a service delimiter. |
SONET/SDH TDM | BCP-Dot1q | 0 to 4094 | The SAP is identified by the 802.1Q tag on the channel. |
SONET/SDH TDM | Frame Relay | 16 to 991 | The SAP is identified by the data link connection identifier (DLCI). |
SONET/SDH ATM | ATM | vpi (NNI) 0 to 4095 vpi (UNI) 0 to 255 vci 1, 2, 5 to 65535 | The SAP is identified by port or by PVPC or PVCC identifier (vpi, vpi/vci, or vpi range) |
The following output is an example of SAP information.
This command monitors statistics for an SDP binding associated with this service.
The following output is an example of SDP information.
This command monitors statistics for a subscriber.
:null | port-id | bundle-id | bpgrp-id | lag-id | aps-id | ||
dot1q | port-id | bundle-id | bpgrp-id | lag-id | aps-id | pw-id:[qtag1|cp-conn-prof-id] | ||
qinq | port-id | bundle-id | bpgrp-id | lag-id | pw-id:[qtag1 cp-conn-prof-id].[qtag2 | cp-conn-prof-id] | ||
cp | keyword | ||
conn-prof-id | 1 to 8000 | ||
atm | port-id | aps-id [:vpi/vci | vpi | vpi1.vpi2 | cp.conn-prof-id] | ||
cp | keyword | ||
conn-prof-id | 1 to 8000 | ||
frame | port-id | aps-id:dlci | ||
cisco-hdlc | slot/mda/port.channel | ||
cem | slot/mda/port.channel | ||
ima-grp | bundle-id [:vpi/vci | vpi | vpi1.vpi2 | cp.conn-prof-id] | ||
cp | keyword | ||
conn-prof-id | 1 to 8000 | ||
port-id | slot/mda/port[.channel] esat-id/slot/port pxc-id.sub-port | ||
bundle-id | bundle-type-slot/mda.-bundle-nu | ||
bundle | keyword | ||
type | ima | fr | ppp | ||
bundle-num | 1 to 336 | ||
bpgrp-id | bpgrp-type-bpgrp-num | ||
bgrp | keyword | ||
type | ima | ppp | ||
bgrp-num | 1 to 2000 | ||
aps-id | aps-group-id[.channel] | ||
aps | keyword | ||
group-id | 1 to 128 | ||
ccag-id | ccag-id.path-id[cc-type]:cc-id | ||
ccag | keyword | ||
id | 1 to 8 | ||
path-id | a | b | ||
cc-type | .sap-net | .net-sap | ||
cc-id | 1 to 4094 | ||
eth-tunnel | eth-tunnel-id[:eth-tun-sap-id] | ||
id | 1 to 1024 | ||
eth-tun-sap-id | 0 to 4094 | ||
lag-id | lag-id | ||
lag | keyword | ||
id | 1 to 800 | ||
pw-id | pw-id | ||
pw | keyword | ||
id | 1 to 10239 | ||
qtag1 | * | 0 to 4094 | ||
qtag2 | * | null | 0 to 4094 | ||
vpi | 0 to 4095 (NNI) | ||
0 to 255 (UNI) | |||
vci | 1 | 2 | 5 to 65535 | ||
dlci | 16 to 1022 | ||
tunnel-id | tunnel-id.private | public:tag | ||
tunnel | keyword | ||
id | 1 to 16 | ||
tag | 0 to 4094 |
The following output is an example of subscriber-information.
This command enables the substitution of a command line (or part of a command line) by an alias. Use the alias command to create alternative or easier to remember/understand names for an entity or command string. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes. The special characters “/” and “\” cannot be used as the first character inside an alias string. An alias can contain a double quote character by preceding the quote with a “\” character (for example, alias my-alias "| match \"string\""). Only a single command can be present in the command string (the command can be long with many parameters but there is no support for aliases that include multiple CLI commands/lines). The alias command can be entered in any context but must be created in the root>environment context.
For example, to create an alias named soi to display OSPF interfaces, enter:
alias soi “show router ospf interface”
Complex aliases can be created to have shortcuts for customized show routine output:
environment alias my-summary "| match expression \"----|Description|Interface|Admin State|Oper State|Transceiver Type|Optical Compliance|Link Length\" | match invert-match expression \"Ethernet Interface|OTU Interface\" | match invert-match expression \"----\" post-lines 1"
and then used like this:
show port detail my-summary
By default, the create command is required to create a new OS entity.
The no form of the command disables requiring the create keyword.
create
This command enables and disables the kernel.
This command enables per-screen CLI output, meaning that the output is displayed on a screen-by- screen basis. The terminal screen length can be modified with the terminal command.
The following prompt appears at the end of each screen of paginated output:
The no form of the command displays the output all at once. If the output length is longer than one screen, the entire output will be displayed, which may scroll the screen.
more
This command configures the maximum number of higher CLI context levels to display in the CLI prompt for the current CLI session. This command is useful when configuring features that are several node levels deep, causing the CLI prompt to become too long. By default, the CLI prompt displays the system name and the complete context in the CLI.
The number of nodes specified indicates the number of higher-level contexts that can be displayed in the prompt. For example, if reduced prompt is set to 2, the two highest contexts from the present working context are displayed by name with the hidden (reduced) contexts compressed into a ellipsis (“…”).
The setting is not saved in the configuration. It must be reset for each CLI session or stored in an exec script file.
The no form of the command reverts to the default.
no reduced-prompt
This command enables saved indicator in the prompt. When changes are made to the configuration file a “*” appears in the prompt string indicating that the changes have not been saved. When an admin save command is executed the “*” disappears.
This command enables and disables the shell.
This command enables suggesting of internally created objects while auto completing.
The no form of the command disables the command.
This command enables the context to configure the terminal screen length for the current CLI session.
This command sets the number of lines on a screen.
This command determines display terminal width.
width 80
This command displays time stamps in the CLI session based on local time or Coordinated Universal Time (UTC).
The system keeps time internally in UTC and is capable of displaying the time in either UTC or local time based on the time zone configured.
This configuration command is only valid for times displayed in the current CLI session. This includes displays of event logs, traps and all other places where a time stamp is displayed.
In general all time stamps are shown in the time selected. This includes log entries destined for console/session, memory, or SNMP logs. Log files on compact flash are maintained and displayed in UTC format.
local
This command specifies whether the time-stamp should be displayed before the prompt.
This command enables the context to edit candidate configurations.
Commands in the candidate CLI branch, except candidate edit, are available only when in edit-cfg mode.
This command enables the edit-cfg mode where changes can be made to the candidate configuration and sets the edit-point to the end of the candidate. In edit-cfg mode the CLI prompt contains edit-cfg near the root of the prompt. Commands in the candidate CLI branch, except candidate edit, are available only when in edit-cfg mode.
This command applies the changes in the candidate configuration to the active running configuration. The candidate changes will take operational effect.
If a commit operation is successful then all of the candidate changes will take operational effect and the candidate is cleared. If there is an error in the processing of the commit, or a ‘commit confirmed’ is not confirmed and an auto-revert occurs, then the router will return to a configuration state with none of the candidate changes applied. The operator can then continue editing the candidate and try a commit later.
By default, the SR OS will automatically create a new rollback checkpoint after a commit operation. The rollback checkpoint will contain the new configuration changes made by the commit. An optional no-checkpoint keyword can be used to avoid the auto-creation of a rollback checkpoint after a commit.
A commit operation is blocked if a rollback revert is currently being processed.
Standard line-by-line non-transactional configuration commands (including via SNMP) are not blocked during the countdown period and any changes made to the configuration during the countdown period will be rolled back if the timeout expires. The confirmed option is useful when changes are being made that could impact management reachability to the router.
A rollback revert is blocked during the countdown period until the commit has been confirmed.
This command is used to stop an automatic reversion to the previous configuration after the candidate commit confirmed command was used. If the confirm command is not executed before the commit confirmed timeout period expires then the previous commit changes will be undone and the previous candidate configuration will be available for editing and a subsequent commit.
During the countdown the contents of the candidate will remain visible (candidate view) and changes to the candidate are blocked until the timeout is completed or the candidate confirm command is executed. Executing the confirm command clears the contents of the candidate and allows editing of the candidate.
This command copies the selected CLI node (which includes all sub-branches) into a temporary buffer that can be used for a subsequent insert. The contents of the temporary buffer are deleted when the operator exits the candidate edit mode.
This command deletes the selected CLI node (which includes all sub-branches). The deleted lines are also copied into a temporary buffer that can be used for a subsequent insert.
line, offset, first, edit-point, last | ||
line | absolute line number | |
offset | relative line number to current edit point. Prefixed with '+' or '-' | |
first | keyword - first line | |
edit-point | keyword - current edit point | |
last | keyword - last line that is not 'exit' |
This command deletes the entire contents of the candidate configuration and exits the edit-cfg mode. Undo cannot be used to recover a candidate that has been discarded with candidate discard.
This command changes the edit point of the candidate configuration. The edit point is the point after which new commands are inserted into the candidate configuration as an operator navigates the CLI and issues commands in edit-cfg mode.
line, offset, first, edit-point, last | ||
line | absolute line number | |
offset | relative line number to current edit point. Prefixed with '+' or '-' | |
first | keyword - first line | |
edit-point | keyword - current edit point | |
last | keyword - last line that is not 'exit' |
This command inserts the contents of the temporary buffer (populated by a previous copy or delete command) into the candidate configuration. The contents are inserted by default after the current edit point. Optional parameters allow the insertion after some other point of the candidate. The contents of the temporary buffer are deleted when the operator exits candidate edit mode.
Insertions are context-aware. The temporary buffer always stores the CLI context (such as the current CLI branch) for each line deleted or copied. If the lines to be inserted are supported at the context of the insertion point then the lines are simply inserted into the configuration. If the lines to be inserted are not supported at the context of the insertion point, then the context at the insertion point is first closed using multiple exit statements, the context of the lines to be inserted is built (added) into the candidate at the insertion point, then the lines themselves are added, the context of the inserted lines is closed using exit statements and finally the context from the original insertion point is built again leaving the context at the same point as it was before the insertion.
line, offset, first, edit-point, last | ||
line | absolute line number | |
offset | relative line number to current edit point. Prefixed with '+' or '-' | |
first | keyword - first line | |
edit-point | keyword - current edit point | |
last | keyword - last line that is not 'exit' |
This command loads a previously saved candidate configuration into the current candidate. The edit point will be set to the end of the loaded configuration lines. The candidate configuration cannot be modified while a load is in progress.
If the candidate is empty then a load without any of the optional parameters (such as overwrite, etc) will simply load the file-url into the candidate. If the candidate is not empty then one of the options, such as overwrite, insert, and so on, must be specified.
This command exits the edit-cfg mode. The contents of the current candidate will not be deleted and the operator can continue editing the candidate later.
This command reapplies the changes to the candidate that were removed using a previous undo. All undo/redo history is lost when the operator exits edit-cfg mode.
A redo command is blocked if another user has made changes in the same CLI branches that would be impacted during the redo.
This command displays the specified line (a single line only) and allows it to be changed.
line, offset, first, edit-point, last | ||
line | absolute line number | |
offset | relative line number to current edit point. Prefixed with '+' or '-' | |
first | keyword - first line | |
edit-point | keyword - current edit point | |
last | keyword - last line that is not 'exit' |
This command saves the current candidate to a file.
This command removes the most recent change(s) done to the candidate. The changes can be reapplied using the redo command. All undo/redo history is lost when the operator exists edit-cfg mode. Undo can not be used to recover a candidate that has been discarded with candidate discard.
An undo command is blocked if another user has made changes in the same CLI branches that would be impacted during the undo.
This command displays the candidate configuration along with line numbers that can be used for editing the candidate configuration.
line, offset, first, edit-point, last | ||
line | absolute line number | |
offset | relative line number to current edit point. Prefixed with '+' or '-' | |
first | keyword - first line | |
edit-point | keyword - current edit point | |
last | keyword - last line that is not 'exit' |
This command displays the operational configuration of the context that the operator is currently in. In edit-cfg mode, the operational keyword is mandatory when using the info command.
This command shows candidate configuration information.
The following output is an example of candidate information, and Table 24 describes the output fields.
Label | Description |
Candidate configuration state | • empty — indicates there are no uncommitted changes in the candidate config • modified — indicates there are uncommitted changes in the candidate config • unconfirmed — indicates there are no uncommitted changes in the candidate config but the result of the last commit will be auto-reverted unless it is confirmed before the timeout expires |
Num editors/viewers | Displays the number of CLI sessions currently in edit-cfg mode |
Candidate cfg exclusive locked | Indicates if a user has exclusively locked the candidate using the candidate edit exclusive command |
Last commit state | • none — indicates there have been no commits since the last reboot of the node • in-progress — indicates the system is currently committing the candidate config • success — indicates the last commit finished successfully • revert-pending — indicates the last commit finished successfully but has not been confirmed yet, and will be auto-reverted if it is not confirmed before the timeout expires • failed — indicates the last commit failed and has been undone • revert-in-progress — indicates the last commit finished successfully but was not confirmed in time and is currently being reverted • reverted — indicates the last commit finished successfully but was not confirmed in time and has been reverted • revert-failed — indicates the last commit finished successfully but was not confirmed in time and the system attempted to revert it but failed |
Last commit time | Displays the time at which the last commit attempt was started |
Checkpoint created with last commit | Indicates if a rollback checkpoint was created after the previous commit completed |
Scheduled revert time | Indicates the currently scheduled auto-revert time based on the confirmed option being used with a candidate commit |
Last commit revert time | Displays the time the commit was last reverted |
Users in edit-cfg mode | Lists all the user sessions that are currently in edit-cfg mode |
Type (from) | Indicates the type of session (such as Console, Telnet, and so on) and also the source of the session (such as the source IP address of the remote host) |
This command displays the differences between rollback checkpoints and the active operational configuration, with source1 as the base/first file to which source2 is compared.
A compare operation does not check authorization of each line of output. Permission to execute the compare operation from the admin branch of CLI (authorization for the admin rollback compare or admin compare command itself) should only be given to users who are allowed to view the entire configuration, similar to permissions for admin display-config.
The defaults for source1 and source2 are context aware and differ based on the branch in which the command is executed. In general, the default for source1 matches the context from which the command is issued.
This command deletes a rollback checkpoint and causes the suffixes to be adjusted (decremented) for all checkpoints older that the one that was deleted (to close the hole in the list of checkpoint files and create room to create another checkpoint).
If config redundancy rollback-sync is enabled, a rollback delete will also delete the equivalent checkpoint on the standby CF and shuffle the suffixes on the standby CF.
It is not advised to manually delete a rollback checkpoint (for example, using a file delete command). If a rollback checkpoint file is manually deleted without using the admin rollback delete command then the suffixes of the checkpoint files are not shuffled, nor is the equivalent checkpoint file deleted from the standby CF. This manual deletion creates a hole in the checkpoint file list until enough new checkpoints have been created to roll the hole off the end of the list.
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).
If the optional rescue keyword is not used, this command saves a rollback checkpoint at the location and with the filename specified by the rollback-location with a suffix of .rb. The previously saved checkpoints will have their suffixes incremented by one (.rb.1 becomes .rb.2, etc). If there are already as many checkpoint files as the maximum number supported, then the last checkpoint file is deleted.
If the rescue keyword is used, then this command saves the current operational configuration as a rescue configuration at the location and with the filename specified by the rescue location. The filename will have the suffix .rc appended.
This command displays the checkpoint.
The context to configure administrative system viewing parameters. Only authorized users can execute the commands in the admin context.
Configures the maximum number of rollback checkpoint files when the rollback-location is on local compact flash.
no local-max-checkpoints
Configures the maximum number of rollback checkpoint files when the rollback-location is remote (for example, ftp).
no remote-max-checkpoints
The location and filename of the rescue configuration is configurable to be local (on compact flash) or remote. The suffix .rc will be automatically appended to the filename when a rescue configuration file is saved. Trivial FTP (TFTP) is not supported for remote locations.
no rescue location
local-url | remote-url | |
local-url | [cflash-id/][file-path] 200 chars max, including flash-id directory length 99 chars max each |
remote-url | [{ftp://}login:pswd@ remote-locn/][file-path] 255 chars max directory length 99 chars max each |
remote-locn | [hostname | ipv4-address | ipv6-address] |
ipv4-address | a.b.c.d |
ipv6-address | x:x:x:x:x:x:x:x[-interface] |
x:x:x:x:x:x:d.d.d.d[-interface] | |
x - [0 to FFFF]H | |
d - [0 to 255]D | |
interface - 32 chars max, for link local addresses | |
cflash-id | cf1:, cf1-A:, cf1-B:, cf2:, cf2-A:, cf2-B:, cf3:, cf3-A:, cf3-B: |
rescue filename | suffixed with rc during rescue file creation |
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.
no rollback-location
local-url | remote-url | |
local-url | [cflash-id/][file-path] 200 chars max, including flash-id directory length 99 chars max each |
remote-url | [{ftp://}login:pswd@ remote-locn/][file-path] 255 chars max directory length 99 chars max each |
remote-locn | [hostname | ipv4-address | ipv6-address] |
ipv4-address | a.b.c.d |
ipv6-address | x:x:x:x:x:x:x:x[-interface] |
x:x:x:x:x:x:d.d.d.d[-interface] | |
x - [0 to FFFF]H | |
d - [0 to 255]D | |
interface - 32 chars max, for link local addresses | |
cflash-id | cf1:, cf1-A:, cf1-B:, cf2:, cf2-A:, cf2-B:, cf3:, cf3-A:, cf3-B: |
The following command outputs are examples only; actual displays may differ depending on supported functionality and user configuration.
This command displays a list of existing aliases.
The following output is an example of alias information, and Table 25 describes the output fields.
Label | Description |
Alias-Name | Displays the name of the alias. |
Alias-command-name | The command and parameter syntax that define the alias. |
Number of aliases | The total number of aliases configured on the router. |