boot-bad-exec file-url
no boot-bad-exec
config>system
Supported on all 7210 SAS platforms as described in this document
This command configures a URL for a CLI script to exec 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 reboots and are included in the configuration saves (admin save).
See the exec command for related commands. This command executes the contents of a text file as if they were commands entered at the console.
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.
boot-good-exec file-url
no boot-good-exec
config>system
Supported on all 7210 SAS platforms as described in this document
This command configures a URL for a CLI script to exec following the success of a boot-up configuration.
The exec command executes the contents of a text file as if they were CLI commands entered at the console.
no boot-good-exec
Specifies the location and name of the file executed following successful completion of the boot-up configuration file execution. When this parameter is not specified, no CLI script file is executed.
clli-code clli-code
no clli-code
config>system
Supported on all 7210 SASplatforms as described in this document
This command creates a Common Language Location Identifier (CLLI) code string for the router. A CLLI code is an 11-character standardized geographic identifier that uniquely identifies geographic locations and specific functional categories of equipment unique to the telecommunications industry.
No CLLI validity checks other than truncating or padding the string to eleven characters are performed.
Only one CLLI code can be configured, if multiple CLLI codes are configured the last one entered overwrites the previous entry.
The no form of this command removes the CLLI code.
Specifies the 11 character string CLLI code. Any printable, seven bit ASCII characters can be used within the string. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes. If more than 11 characters are entered, the string is truncated. If less than 11 characters are entered the string is padded with spaces.
config-backup count
no config-backup
config>system
Supported on all 7210 SAS platforms as described in this document
This command configures the maximum number of backup versions maintained for configuration files and BOF.
For example, assume the config-backup count is set to 5 and the configuration file is called xyz.cfg. When a save command is executed, the file xyz.cfg is saved with a .1 extension. 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 is performed for all configurations and their associated persistent index files.
The no form of this command reverts to the default value.
5
Specifies the maximum number of backup revisions.
console
config>system
Supported on all 7210 SAS platforms as described in this document
Commands in this context configure console as an alarm-input-pin.
[no] use-console-alarm-input
config>system>console
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C
This command provides an option to the user to use the console port on the 7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, or 7210 SAS-K 3SFP+ 8C as an alarm-input pin. When this command is executed, the console port can be used as an alarm input pin. A single alarm-input pin can be enabled for use with the console port, allowing operators to monitor external events and alert the operator. For this command to take effect, the console must be enabled in the BOF.
The RXD and TXD pins of the console input is used to provide a single alarm input pin functionality and is used by the software to detect external events. The operating system detects an open or a close circuit which triggers an alarm and logs it when an event is detected.
After this command is executed, the console port can no longer be used as a console port, and the system generates a log message to convey this restriction. Additionally, the user needs to configure the alarm-contact-input parameter for console by using the config system alarm-contact-input console-1 command (the console alarm-contact-input is identified with the ID = console-1).
The no form of this command disables use of console port as alarm-input interface.
no use-console-alarm-input
contact contact-name
no contact
config>system
Supported on all 7210 SAS platforms as described in this document
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 this command reverts to the default.
Specifies the contact name character string. The string can be up to 80 characters. Any printable, seven-bit ASCII characters can be used within the string. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.
coordinates coordinates
no coordinates
config>system
Supported on all 7210 SAS platforms as described in this document
This command creates a text string that identifies the system coordinates for the device location. The coordinates ‟37.390 -122.0550" command 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 this command reverts to the default value.
Specifies the coordinates describing the device location character string. The string may be up to 80 characters. Any printable, seven-bit ASCII characters can be used within the string. If the string contains special characters (#, $, spaces, and so on), 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.
lacp-system-priority lacp-system-priority
no lacp-system-priority
config>system
Supported on all 7210 SAS platforms as described in this document
This command configures the Link Aggregation Control Protocol (LACP) system priority on aggregated Ethernet interfaces. LACP allows the operator to aggregate multiple physical interfaces to form one logical interface.
32768
Specifies the LACP system priority
location location
no location
config>system
Supported on all 7210 SAS platforms as described in this document
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 this command reverts to the default value.
Specifies the location as a character string. The string may be up to 80 characters. Any printable, seven-bit ASCII characters can be used within the string. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.
login-control
config>system
Supported on all 7210 SAS platforms as described in this document
Commands in this context configure login control.
name system-name
no name
config>system
Supported on all 7210 SAS platforms as described in this document
This command creates a system name string for the device.
For example, system-name parameter ALA-1 for the name command configures the device name as ALA-1.
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 this command reverts to the default value.
The default system name is set to the chassis serial number which is read from the backplane EEPROM.
Specifies the system name as a character string. The string may be up to 32 characters. Any printable, seven-bit ASCII characters can be used within the string. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.
oper-group name [create]
no oper-group
config>system
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C
This command creates a system-wide group name which can be used to associate a number of service objects; for example, ports. The status of the group is derived from the status of its members. The status of the group can then be used to influence the status of non-member objects. For example, when a group status is marked as down, the objects that monitor the group change their status accordingly.
The no form of this command removes the group. All the object associations need to be removed before the no command can be executed.
no oper-group
Specifies the operational group identifier, up to 32 characters.
Keyword to create the configuration context. After the context is created, it is possible to navigate into the context without the create keyword.
hold-time
config>system>oper-group
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C
Commands in this context configure hold time information.
[no] group-down time in seconds
config>system>oper-group>hold-time
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C
This command configures the number of seconds to wait before notifying clients monitoring this group when its operational status transitions from down to up. A value of zero indicates that transitions are reported immediately to monitoring clients.
The no form reverts the value to the default.
0
Specifies the wait time, in seconds.
[no] group-up time in seconds
config>system>oper-group>hold-time
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C
This command configures the number of seconds to wait before notifying clients monitoring this group when its operational status transitions from up to down.
The no form reverts the value to the default.
4
Specifies the wait time, in seconds.
poe
config>system
7210 SAS-Dxp 16p and 7210 SAS-Dxp 24p
Commands in this context configure power over Ethernet (PoE) power budget information.
max-poe-power-budget value
no max-poe-power-budget
config>system>poe
7210 SAS-Dxp 16p and 7210 SAS-Dxp 24p
This command configures the maximum PoE budget that the software uses to allocate PoE power to connected PoE devices (PDs).
When configuring the value parameter, the user must consider the PD power requirements at a site and the available power based on the power supply, operating temperature, and operating altitude. See the 7210 SAS-Dxp 16p/24p Chassis Installation Guide for more information about the formula to calculate the maximum PoE budget based on the operating altitude and temperature range for specific PoE power modules.
The software accounts for power requirements based on the PD type and does not consider the PoE class within a type. The following table lists the power requirements per PD type.
PD |
Power requirement |
|---|---|
PoE |
15 W |
PoE+ |
30 W |
PoE++ |
60 W |
HPoE |
90 W |
For example, if the user configures one PoE port, the software deducts 15 W from the configured max-poe-power-budget. If the user configures two PoE ports and two PoE + ports, the software deducts 90 W from the configured max-poe-power-budget (assuming the configured value is greater than or equal to 90 W). If the user configures a value of 100 W and attempts to configure four PoE+ ports, the software deducts 30 W from the configured max-poe-power-budget for the first three configured PoE+ ports using a total of 90 W (10 W are remaining). When the user configures the fourth port, the configuration fails because only 10 W are available, which does not meet the power requirement for the fourth PoE+ port.
The following configuration guidelines apply for this command.
If power module redundancy is configured, use the lowest common denominator PoE power budget of the two available power modules to determine the available PoE power.
If no max-poe-power-budget is configured, no PoE devices can be connected to the node.
To modify the module-type, configure no max-poe-power-budget, change the module-type, and configure the correct max-poe-power-budget for the new module-type.
The user cannot execute the no max-poe-power-budget command when PoE ports are enabled. Before configuring no max-poe-power-budget, the user must either shut down all PoE ports or remove the PoE configuration on all ports.
The no form of this command allocates 0 W for the PoE power budget.
no max-poe-power-budget
Specifies the maximum PoE power budget.
The MIB uses a common maximum value of 720 W for the 7210 SAS-Dxp 16p and 7210 SAS-Dxp 24p, but the system displays an error message for the 7210 SAS-Dxp 16p when the value exceeds 540 W.
power-supply [power-supply-id] type power-module-type module-type
config>system
7210 SAS-D ETR, 7210 SAS-Dxp 12p ETR, 7210 SAS-Dxp 16p, and 7210 SAS-Dxp 24p
This command configures a power supply.
By default, the software does not generate any traps or alarms for PS1 or PS2 when external power supply failure is detected. The user is provided with an option to configure the external backup power supply type on the 7210 SAS-Dxp 12p ETR and external power supply type on the 7210 SAS-Dxp 16p and 7210 SAS-Dxp 24p. The system generates an alarm or trap on a power supply failure only when the user configures the power supply type as ac or dc. The user can disable alarms or traps by setting the type value to none.
On the 7210 SAS-Dxp 16p and 7210 SAS-Dxp 24p, the power-module-type parameter identifies the specific power supply module in use among the various modules supported on the 7210 SAS-Dxp 16p and 7210 SAS-Dxp 24p.
If the value is none, the software does not send a trap to the management station to clear any pending alarms. Traps are only cleared locally and the LED color is reset if no major or critical alarms are pending. The management station is expected to take appropriate action upon receiving the configuration change event or trap.
On the 7210 SAS-Dxp 12p ETR, this command does not affect any traps or alarms generated for the integrated power supply, which continue to be generated on detection of integrated power supply failure when an external power supply is in use.
The 7210 SAS-D ETR, 7210 SAS-Dxp 12p ETR, 7210 SAS-Dxp 16p, and 7210 SAS-Dxp 24p do not have the capability to detect whether the external power supply type is an AC or DC version. Consequently, the user-configured value is not validated by the software. The user is responsible for ensuring that the value is correct and it corresponds to the type of power supply (AC or DC) in use. If an incorrect value is configured, the software continues to display the configured value and generate traps or alarms.
This command is only supported on the 7210 SAS-D ETR and 7210 SAS-Dxp 12p ETR. attempts to configure this command on the standard 7210 SAS-D and 7210 SAS-Dxp 12p causes the software to return an error message.
On the standard 7210 SAS-Dxp 12p and 7210 SAS-Dxp 12p ETR variant, when a single power supply is used, failure of that power supply brings the node down. On loss of power, the user can configure EFM OAM dying gasp or SNMP IP-based dying gasp to send a power loss notification.
Specifies the power supply ID for which the type is to be applied.
Specifies the type of power supply.
Specifies the power module type. This parameter is supported only on the 7210 SAS-Dxp 16p and 7210 SAS-Dxp 24p.
power-supply [power-supply-id] type
config>system
7210 SAS-K 2F1C2T ETR
This command configures the external power-supply type and also provides an option to the user to enable or disable notifications related to power supply. This command is recommended to be used when redundant power supplies are used with the 7210 SAS-K 2F1C2T ETR.
When a single power supply is used, failure of that power supply brings the node down and user has an option to use EFM OAM dying gasp or SNMP IP based dying gasp for sending out power loss notification.
On the 7210 SAS-K 2F1C2T ETR, by default, the software does not generate any traps or alarms when the external power-supply failure has been detected. The user is provided with an option to configure the external power-supply and its type. Only if the user configures the power-supply type as 'ac' or 'dc' the system generates alarm or trap on a power-supply failure. The user can disable generation of alarms or traps by setting the value to none.
By setting the value to none, the software does not send out a trap to the management station to clear the alarm, if there was one pending. The none value only clears the trap locally and resets the LED color, if there are no other major or critical alarms pending. It is expected that the management station takes appropriate action on receiving the configuration change event or trap.
The 7210 SAS-K 2F1C2T ETR does not have the capability to detect whether the external power-supply type is an AC or DC version. Therefore, the user-configured value is not validated by the software. The user is responsible for ensuring whether the value is correct and corresponds to what they are using. If users provide an incorrect value, the software continues to display the configured value and generate traps or alarms on detection of the power supply failure.
The power-supply command is only supported on the 7210 SAS-K 2F1C2T ETR. If the power-supply command is used on the 7210 SAS-K 2F1C2T, the software returns an error message.
Specifies the power-supply for which the type is to be applied.
Specifies the type of power-supply.