atm
config>system
This command enables the context to configure system-wide ATM parameters.
atm-location-id location-id
no atm-location-id
config>system>atm
This command indicates the location ID for ATM OAM.
See the 7705 SAR Quality of Service Guide, ‟ATM QoS Traffic Descriptor Profiles”, for information about ATM QoS policies and the 7705 SAR Services Guide, ‟VLL Services” for information about ATM-related service parameters.
no atm-location-id
specifies the 16 octets that identifies the system loopback location ID as required by the ATM OAM Loopback capability. This textual convention is defined in ITU-T standard I.610.
Invalid values include a location ID where the first octet is: 00, FF, 6A
Acceptable location-ids include values where the first octet is: 01, 03
Other values are not accepted.
boot-bad-exec file-url
no boot-bad-exec
config>system
Use this command to configure a URL for a CLI script to execute following a failure of a boot-up configuration. The command specifies a URL for the CLI scripts to be run following the completion of the boot-up configuration. A URL must be specified or no action is taken.
The commands are persistent between router (re)boots and are included in the configuration saves (admin>save).
Also see the related command exec.
no boot-bad-exec
specifies the location and name of the CLI script file executed following failure of the boot-up configuration file execution. When this parameter is not specified, no CLI script file is executed. (See Table: URL Types and Syntax for parameter descriptions.)
boot-good-exec file-url
no boot-good-exec
config>system
Use this command to configure a URL for a CLI script to execute following the success of a boot-up configuration.
Also refer to the related command exec.
no boot-good-exec
specifies the location and name of the CLI script file executed following successful completion of the boot-up configuration file execution. When this parameter is not specified, no CLI script file is executed. (See Table: URL Types and Syntax for parameter descriptions.)
clli-code clli-code
no clli-code
config>system
This command creates a Common Language Location Identifier (CLLI) code string for the 7705 SAR. A CLLI code is an 11-character standardized geographic identifier that uniquely identifies geographic locations and certain functional categories of equipment unique to the telecommunications industry.
No CLLI validity checks other than truncating or padding the string to 11 characters are performed.
Only one CLLI code can be configured. If multiple CLLI codes are configured, the last one entered overwrites the previous entry.
The no form of the command removes the CLLI code.
n/a — no CLLI codes are configured
the 11-character string CLLI code. Any printable, 7-bit ASCII characters can be used within the string. If the string contains spaces, the entire string must be enclosed within double quotes. If more than 11 characters are entered, the string is truncated. If fewer than 11 characters are entered, the string is padded with spaces.
config-backup count
no config-backup
config>system
This command configures the maximum number of backup versions maintained for configuration files and BOF.
For example, if the config-backup count is set to 5 and the configuration file is called xyz.cfg, the file xyz.cfg is saved with a .1 extension when the save command is executed. Each subsequent config-backup command increments the numeric extension until the maximum count is reached.
xyz.cfg
xyz.cfg.1
xyz.cfg.2
xyz.cfg.3
xyz.cfg.4
xyz.cfg.5
xyz.ndx
Each persistent index file is updated at the same time as the associated configuration file. When the index file is updated, then the save is performed to xyz.cfg and the index file is created as xyz.ndx. Synchronization between the active and standby CSM is performed for all configurations and their associated persistent index files.
The no form of the command returns the configuration to the default value.
5
the maximum number of backup revisions
contact contact-name
no contact
config>system
This command creates a text string that identifies the contact name for the device.
Only one contact can be configured. If multiple contacts are configured, the last one entered overwrites the previous entry.
The no form of the command reverts to the default.
n/a — no contact name is configured
the contact name character string. Allowed values are any string up to 80 characters long composed of printable, 7-bit ASCII characters. If the string contains spaces, the entire string must be enclosed within double quotes.
coordinates coordinates
no coordinates
config>system
This command creates a text string that identifies the system coordinates for the device location. For example, the command coordinates ‟37.390 -122.0550” is read as latitude 37.390 north and longitude 122.0550 west.
Only one set of coordinates can be configured. If multiple coordinates are configured, the last one entered overwrites the previous entry.
The no form of the command reverts to the default value.
n/a — no coordinates are configured
the coordinates describing the device location character string. Allowed values are any string up to 80 characters long composed of printable, 7-bit ASCII characters. If the string contains spaces, the entire string must be enclosed within double quotes. If the coordinates are subsequently used by an algorithm that locates the exact position of this node, then the string must match the requirements of the algorithm.
fp
config>system
This command enters the context to issue forwarding path commands.
n/a
options
config>system>fp
This command enters the context to configure forwarding path options.
n/a
vpls-high-scale
config>system>fp>options
This command enters the context to enable or disable VPLS scalability with the shutdown command.
VPLS scalability is only supported on the 7705 SAR-8 Shelf V2 and the 7705 SAR-18. VPLS scalability cannot be enabled if any of the following are configured in the system:
access or network IP interfaces (GRT/IES/VPRN) on a 16-port T1/E1 ASAP Adapter card, version 2, 32-port T1/E1 ASAP Adapter card, 4-port OC3/STM1 Clear Channel Adapter card, 2-port OC3/STM1 Channelized Adapter card, or 4-port DS3/E3 Adapter card.
VPLS residential ATM SAPs
VPLS high-scale limits are supported on access and network links on the following cards:
2-port 10GigE (Ethernet) Adapter card
8-port Gigabit Ethernet Adapter card
10-port 1GigE/1-port 10GigE X-Adapter card
Packet Microwave Adapter card
4-port OC3/STM1 / 1-port OC12/STM4 Adapter card
By default, VPLS scalability is disabled and the 7705 SAR-8 Shelf V2 and 7705 SAR-18 support only 64 VPLS instances. You can enable up to 255 VPLS instances by issuing the no shutdown command under this context.
After the no shutdown command is issued, the Admin state for vpls-high-scale is enabled but the Oper state remains disabled and you cannot create more than 64 VPLS instances. You must issue an admin save command and reboot the node for the configuration change to take effect.
To disable VPLS scalability, you must lower the number of VPLS services to 64 or fewer before issuing the shutdown command under this context. The VPLS service ID numbers are not relevant, as long as the maximum number of services is 64. You must issue an admin save command and reboot the node for the configuration change to take effect.
n/a
[no] identifier id
config>system
This command configures a static system identifier for the 7705 SAR. The system identifier can be used to uniquely identify the 7705 SAR in the network instead of the system IP address, as a system IP address can change dynamically using DHCP when the 7705 SAR is acting as a DHCP client and the DHCP server-facing interface is unnumbered. To prevent management systems (for example, the NSP NFM-P) from rediscovering a node based on a system IP address that has been changed via DHCP, and therefore losing historical data attributed to a specific system IP address, a static system identifier should be configured.
The system identifier takes the form of an IPv4 address. This address is not advertised in IGP or BGP and is used solely as a node identifier.
The no form of the command deletes the system identifier.
no identifier
configures an IPv4 address to be used as the system identifier
load-balancing
config>system
This command enables the context to configure load balancing parameters.
[no] l4-load-balancing
config>system>load-balancing
This command configures system-wide Layer 4 load balancing. The configuration at the system level can enable or disable load balancing across all IP interfaces. When enabled, Layer 4 source and destination port fields of incoming TCP/UDP packets are included in the hashing calculation to randomly determine the distribution of packets. Adding the Layer 4 source and destination port fields to the hashing algorithm generates a higher degree of randomness and a more even distribution of packets across the available ECMP paths or LAG ports.
no l4-load-balancing
lsr-load-balancing hashing-algorithm [bottom-of-stack hashing-treatment][use-ingress-port]
no lsr-load-balancing
config>system>load-balancing
This command configures system-wide LSR load balancing. Hashing can be enabled on the IP header at an LSR to send labeled packets over multiple equal-cost paths in an LDP LSP and/or over multiple links of a LAG group in all types of LSPs.
The bottom-of-stack option determines the significance of the bottom-of-stack label (VC label) based on which label stack profile option is specified.
When LSR load balancing is enabled, the default configuration for the hashing algorithm is label-only (lbl-only) hashing, and the default configuration for the bottom-of-stack hashing treatment is profile-1.
The use-ingress-port option, when enabled, specifies that the ingress port are used by the hashing algorithm at the LSR. This option should be enabled for ingress LAG ports because packets with the same label stack can arrive on all ports of a LAG interface. In this case, using the ingress port in the hashing algorithm results in better egress load balancing, especially for pseudowires.
The option should be disabled for LDP ECMP so that the ingress port is not used by the hashing algorithm. For ingress LDP ECMP, if the ingress port is used by the hashing algorithm, the hash distribution could be biased, especially for pseudowires.
LSR load-balancing configuration on an interface overrides the system-wide LSR load-balancing settings for the interface.
no lsr-load-balancing
specifies the hashing algorithm
specifies which label stack profile option to use; profiles determine the significance of the bottom-of-stack label (VC label)
when configured, specifies that the ingress port is used by the hashing algorithm at the LSR
[no] system-ip-load-balancing
config>system>load-balancing
This command enables the use of the system IP address in the hash algorithm to add a per-system variable. This can help to guard against cases where multiple routers, in series, ends up hashing traffic to the same ECMP or LAG path. The algorithm based on the system IP address is included by default.
system-ip-load-balancing
location location
no location
config>system
This command creates a text string that identifies the system location for the device.
Only one location can be configured. If multiple locations are configured, the last one entered overwrites the previous entry.
The no form of the command reverts to the default value.
n/a — no system location is configured
the location as a character string. Allowed values are any string up to 80 characters long composed of printable, 7-bit ASCII characters. If the string contains spaces, the entire string must be enclosed within double quotes.
name system-name
no name
config>system
This command creates a system name string for the device.
For example, system-name parameter ALU-1 for the name command configures the device name as ALU-1.
ABC>config>system# name ALU-1
ALU-1>config>system#
Only one system name can be configured. If multiple system names are configured, the last one encountered overwrites the previous entry.
The no form of the command reverts to the default value.
The default system name is set to the chassis serial number which is read from the backplane EEPROM.
the system name as a character string. Allowed values are any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains spaces, the entire string must be enclosed within double quotes.
[no] power-feed-monitoring {A | B | C}
config>system
This command suppresses power feed monitoring and alarms on the secondary input power feed of a chassis when that power feed is not in use. Use this command when monitoring and raising alarms on the unused power input is not required. Suppressing monitoring and alarms on an unused input power feed results in the following:
logging of input power feed failures is suppressed
any alarms that have been raised on an unused power feed are cleared when the no power-feed-monitoring command is applied to that power feed
in the Power Feed Information output of the show>chassis command, the status of the unused input power feed appears as ‟not monitored”
for chassis that use the Status LED to indicate alarms, the Status LED is lit green if no other alarm conditions exist; for chassis that have alarm LEDs, the critical alarm LED is unlit if no other critical alarm conditions exist. For the 7705 SAR-Hc, the alarm LED is unlit if no other alarm condition exists.
Power feed monitoring and alarming is enabled by default.
power-feed-monitoring