5.10. System Command Reference

This command administratively disables the entity. When disabled, an entity does not change, reset, or remove any configuration settings or statistics.

The operational state of the entity is disabled as well as the operational state of any entities contained within. Many objects must be shut down before they may be deleted.

The no form of this command places the entity into an administratively enabled state.

This command creates a text description stored in the configuration file for a configuration context.

The description command associates a text string with a configuration context to help identify the content in the configuration file.

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

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.

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.

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 certain functional categories of equipment unique to the telecommunications industry.

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

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

The no form of this command removes the CLLI code.

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.

This command enables the context to configure console as an alarm-input-pin.

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.

This command creates a text string that identifies the contact name for the device.

Only one contact can be configured, if multiple contacts are configured the last one entered will overwrite the previous entry.

The no form of this command reverts to the default.

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.

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.

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.

This command enables the context to configure login control.

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.

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.

This command enables the context to configure hold time information.

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.

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.

This command enables the context to configure a power-supply.

On the 7210 SAS-D ETR and 7210 SAS-Dxp ETR, by default, the software does not generate any traps or alarms for PS2, when the external power- supply failure has been detected. The user is provided with an option to configure the external backup power-supply 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.

Note: 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. This CLI command does not affect generation of trap or alarm for the integrated power supply. Traps or alarms are always generated on detection of failure of the integrated power supply, when an external power supply is in use. The 7210 SAS-D ETR and 7210 SAS-Dxp ETR do 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. The power-supply command is only supported on the 7210 SAS-D ETR and 7210 SAS-Dxp ETR. If the power-supply command is used on the 7210 SAS-D or 7210 SAS-Dxp, the software returns an error message. 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.

This command enables the context to configure the external power-supply type and also provide 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.

Note: 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.

Note: 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.

This command configures an entry in the RMON-MIB alarm Table. The alarm command controls the monitoring and triggering of threshold crossing events. In order for notification or logging of a threshold crossing event to occur there must be at least one associated rmon>event configured.

The agent periodically takes statistical sample values from the MIB variable specified for monitoring and compares them to thresholds that have been configured with the alarm command. This command configures the MIB variable to be monitored, the polling period (interval), sampling type (absolute or delta value), and rising and falling threshold parameters. If a sample has crossed a threshold value, the associated event is generated.

The no form of this command removes an rmon-alarm-id from the configuration.

This command configures memory use, in kilobytes, alarm thresholds.

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

This command configures memory usage, in kilobytes, for warning thresholds

This command enables capacity monitoring of the compact flash specified in this command. The severity level is alarm. Both a rising and falling threshold can be specified.

The no form of this command removes the configured compact flash threshold alarm.

This command enables capacity monitoring of the compact flash specified in this command. The severity level is warning. Both a rising and falling threshold can be specified. The no form of this command removes the configured compact flash threshold warning.

This command configures an entry in the RMON-MIB event table. The event command controls the generation and notification of threshold crossing events configured with the alarm command. When a threshold crossing event is triggered, the rmon>event configuration optionally specifies if an entry in the RMON-MIB log table should be created to record the occurrence of the event. It may also specify that an SNMP notification (trap) should be generated for the event. The RMON-MIB defines two notifications for threshold crossing events: Rising Alarm and Falling Alarm.

Creating an event entry in the RMON-MIB log table does not create a corresponding entry in the TiMOS event logs. However, when the event-type is set to trap, the generation of a Rising Alarm or Falling Alarm notification creates an entry in the TiMOS event logs and that is distributed to whatever TiMOS log destinations are configured: CONSOLE, session, memory, file, syslog, or SNMP trap destination.

The TiMOS logger message includes a rising or falling threshold crossing event indicator, the sample type (absolute or delta), the sampled value, the threshold value, the RMON-alarm-id, the associated RMON-event-id and the sampled SNMP object identifier.

The no form of this command removes an rmon-event-id from the configuration.

The memory thresholds are based on monitoring the TIMETRA-SYSTEM-MIB sgiMemoryUsed object. This object contains the amount of memory currently used by the system. The severity level is Alarm.

The no form of this command removes the configured memory threshold warning.

The memory thresholds are based on monitoring MemoryUsed object. This object contains the amount of memory currently used by the system. The severity level is Alarm.

The absolute sample type method is used.

The no form of this command removes the configured compact flash threshold warning.

This command enables 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.

This command enables the context to configure monitoring thresholds.

This command enables the context to configure parameters for IEEE 1588-2008, Precision Time Protocol.

This command configures the PTP Announce Receipt Timeout count in the Announce message.

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

This command enables the context to configure the source of frequency reference for PTP.

This command provides a stable frequency reference obtained through one of the line references (SyncE) for the PTP clock. This is achieved by specifying the frequency source for PTP to be ssu. This mode of operation where PTP is used only for time recovery and SyncE is used for frequency recovery is known as PTP hybrid mode.

If set to ssu, PTP is running in hybrid mode (if PTP is also in a no shutdown state), using the recovered frequency provided by the central clock through the configured reference (SyncE). When this parameter is set to ssu, PTP cannot be configured as a reference in the ref-order. The CLI will block this configuration. The reverse is also true; that is, if PTP is configured under ref-order, this parameter cannot be set to ssu.

If set to ptp, PTP is running in pure mode, potentially being configured as a frequency reference in ref-order.

Note: If the freq-source value is changed, the system must be rebooted after the configuration changes are saved in order for the new value to take effect.

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

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

This command configures the PTP domain.

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

Note: Some profiles may require a domain number in a restricted range. It is up to the operator to ensure that the value aligns with what is expected within the profile.

The domain can be changed only if PTP is shut down.

If the PTP profile is changed, the domain is changed to the default domain for the new PTP profile.

This command configures the local priority used to choose between PTP masters in the best master clock algorithm (BMCA). This setting is relevant when the profile is set to g8265dot1-2010 or g8275dot1-2014. The parameter is ignored when the profile is set to ieee1588-2008.

The value 1 is the highest priority and 255 is the lowest priority.

For g8265dot1-2010, this command sets the priority to use to select between master clocks with the same quality.

For g8275dot1-2014, this command sets the value of the local priority associated with the Announce messages received from the external clocks (ptp>peer or ptp>port), or the local clock (PTP).

This command configures the PTP Announce interval.

The no form of this command sets it to the default value.

This command configures the PTP Sync and PTP Delay-Req message rate that a PTP slave requests of a PTP master. The value specified is used as the rate for both PTP Sync and Delay-Req messages. The user can set a lower packet rate, typically when using SyncE for frequency and PTP, for time only.

This command applies only if the profile is set to ieee1588-2008 or g8265dot1-2010. It does not apply when g8275dot1-2014 is configured. When the profile is set to g8275dot1-2014, the value is set to –4 (16 packets/s) and cannot be changed.

For multicast messages used on PTP Ethernet ports, this command configures the message interval used for synchronization messages transmitted by the local node when the port is in the master state.

The no form of this command reverts to the default value for the profile. For the 7210 SAS-D ETR, it is recommended that the packet rate be set to either –4 or –3.

This command configures the codeset to be used for the encoding of QL values into PTP clockClass values when the profile is configured for G.8265.1. The codeset is defined in G.8265.1, Table 1.

This setting only applies to the range of values observed in the clockClass values transmitted out of the node in Announce messages. The 7210 SAS supports the reception of any valid value in G.8265.1, Table 1.

This command enables the context to configure parameters associated with remote PTP peers.

Up to 20 remote PTP peers can be configured.

The no form of this command deletes the specified peer.

If the clock-type is ordinary slave or boundary, and PTP is not shut down, the last peer cannot be deleted. This prevents the user from having PTP enabled without any peer configured and enabled.

This command disables or enables a specific PTP peer. Shutting down a peer sends cancel unicast negotiation messages on any established unicast sessions. When shut down, all received packets from the peer are ignored.

If the clock-type is ordinary slave or boundary, and PTP is not shut down, the last enabled peer cannot be shut down. This prevents the user from having PTP enabled without any peer configured and enabled.

This command configures PTP over Ethernet on the physical port. The PTP process transmits and receives PTP messages through the port using Ethernet encapsulation (as opposed to UDP/IPv4 encapsulation).

The frames are transmitted with no VLAN tags even if the port is configured for dot1q or qinq modes for encap-type. In addition, the received frames from the external PTP clock must also be untagged.

There are two reserved multicast addresses allocated for PTP messages. See Annex F IEEE Std 1588-2008 and the address command for more information. Either address can be configured for the PTP messages sent through this port.

This command applies only if the PTP profile is set to g8275dot1-2014.

Changing the encapsulation or the port type of the Ethernet port is not permitted when PTP Ethernet multicast operation is configured on the port. To change the encapsulation or port type, the physical port must be shut down.

The no form of this command deletes the specified port.

This command configures the MAC address to be used as the multicast destination address for transmitted PTP messages.

This command applies only if profile is set to g8275dot1-2014.

The IEEE Std 1588-2008 Annex F defines two reserved addresses for PTP messages, as follows:

The system will accept PTP messages received using either destination MAC address, regardless of the address configured by this command.

This command prevents the local port from ever entering the slave state. This can be used to ensure that the 7210 SAS never draws synchronization from the attached external device.

This command applies only if profile is set to g8275dot1-2014.

This command disables or enables a specific PTP port. When shut down, all PTP Ethernet messages are dropped on the IOM. They are not counted in the PTP message statistics. No PTP packets are transmitted by the node toward this port.

If the clock-type is ordinary slave or boundary, and PTP is not shut down, the last enabled port cannot be shut down. This prevents the user from having PTP enabled without any means to synchronize the local clock to a parent clock.

This command applies only if profile is set to g8275dot1-2014.

This command configures the priority1 value of the local clock. This command applies only if the profile is set to ieee1588-2008. This value is used by the BMCA to determine which clock should provide timing for the network. It is also used as the advertised value in Announce messages and as the local clock value in data set comparisons.

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

This command configures the priority2 value of the local clock. This parameter is only used when the profile is set to ieee1588-2008 or g8275dot1-2014.

This value is used by the BMCA to determine which clock should provide timing for the network. It is also used as the advertised value in Announce messages and as the local clock value in data set comparisons.

The no form of this command reverts to the default.

This command configures the profile to be used for the internal PTP clock. This principally defines the BMCA behavior.

The profile cannot be changed unless PTP is shut down.

When the profile is changed, the domain is changed to the default value for the new profile.

Layer 3 PTP commands apply if the profile is set to either ieee1588-2008 or g8265dot1-2010. Layer 2 PTP commands apply if the profile is set to g8275dot1-2014. The command descriptions indicate whether the command is applicable for a specific profile.

This command configures the local system time.

The time entered should be accurate for the time zone configured for the system. The system will convert the local time to UTC before saving to the system clock which is always set to UTC. This command does not take into account any daylight saving offset if defined.

This command enables the context to configure the system time zone and time synchronization parameters.

This command enables the context to create or modify timing reference parameters. The ref-order must be specified in order for this command to be enabled.

This command discards changes that have been made to the synchronous interface timing configuration during a session.

This command enables the context to create or edit the system synchronous interface timing configuration.

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

This command enables the context to configure parameters for system timing via IEEE 1588-2008, Precision Time Protocol (PTP). PTP is not supported on 7210 SAS-Dxp.

This command configures the reference selection based on the quality level (QL) value. This value overrides any value received by that reference's SSM process.

This command enables the selection of the system timing reference to take into account the quality level. This command turns SSM encoding on or off as a means of timing reference selection.

The synchronous equipment timing subsystem can lock to different timing reference inputs, those specified in the ref1, ref2 and ptp command configuration. This command organizes the priority order of the timing references.

If a reference source is disabled, then the clock from the next reference source as defined by ref-order is used. If all reference sources are disabled, then clocking is derived from a local oscillator.

If a sync-if-timing reference is linked to a source port that is operationally down, the port is no longer qualified as a valid reference. Depending on the platform used, either SFP or Fixed copper ports can be used as a reference.

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

Note: On the 7210 SAS-D ETR, ref1 must be configured to use one of ports 1/1/1 to 1/1/4 and ref2 must be configured to use either port 1/1/5 or 1/1/6. The software enforces this check. Ports 1/1/7 to 1/1/10 can be configured as either ref1 or ref2.

This command enables the context to configure parameters for the first timing reference.

This command enables the context to configure parameters for the second timing reference.

This command enables the clock to revert to a higher priority reference if the current reference goes offline or becomes unstable.

If revertive switching is enabled, the highest-priority valid timing reference will be used. If a reference with a higher priority becomes valid, a reference switch over to that reference will be initiated. If a failure on the current reference occurs, the next highest reference takes over.

If non-revertive switching is enabled, the valid active reference always remains selected, even if a higher-priority reference becomes available. If this reference becomes invalid, a reference switch over to a valid reference with the highest priority will be initiated. When the failed reference becomes operational, it is eligible for selection.

This command configures the source port for timing reference ref1 or ref2. If the port is unavailable or the link is down, then the reference sources are re-evaluated according to the reference order configured in the ref-order command.

The no form of this command deletes the source port from the reference.

This command enables new MAC address assignments to avoid an overlap between port MAC addresses and LAG MAC addresses.

In the current default assignments of MAC addresses to ports and LAGs, the MAC addresses that are allocated to the LAGs overlap with the MAC addresses of the physical ports; for example, the MAC address assigned by the system to LAG 1 is the same as the MAC address of port 27.

Use this command to change the MAC address assignment scheme to ensure that the LAG MAC addresses are not the same as the MAC addresses of the physical ports. The new scheme is referred to in the system as “v1.”

A reboot is required for this command to take effect.

Warning: The MAC address for some ports will change after this command is run. Ensure required changes are made to other service objects (for example, CFM up MEPs, and so on) that reference local MAC addresses, and to MAC addresses that reference remote peer devices, if required. Failure to make such changes could result in unpredictable behavior.

The no form of this command reverts to the default MAC address assignment scheme for ports and LAGs. The use of the default configuration is not recommended; it is available only to maintain the current mode of operation, if absolutely necessary.

This command enables the context to configure administrative system commands. Only authorized users can execute the commands in the admin context.

This command validates the current golden bootstrap image, and displays its version, if found to be valid. If the golden bootstrap image is not found to be a valid, an error message is displayed to that effect.

This command can potentially use the TiMOS images available on the local flash to boot up and provide a user login prompt when the system boots up for the first-time. With this command, the user is provided with an option to stop the auto-init process and complete successful boot. After executing this command, the system saves the BOF with the BOF parameter primary-image pointing to the both.tim on the local flash.

If the user does not use this command to stop the auto-init process, the system reboots and attempts to find the BOF again using DHCP.

This command saves existing debug configuration. Debug configurations are not preserved in configuration saves.

This command disconnects a user from a console, Telnet, FTP, or SSH session.

If any of the console, Telnet, FTP, or SSH options are specified, then only the respective console, Telnet, FTP, or SSH sessions are affected.

If no console, Telnet, FTP, or SSH options are specified, then all sessions from the IP address or from the specified user are disconnected.

Any task that the user is executing is terminated. FTP files accessed by the user will not be removed.

A major severity security log event is created specifying what was terminated and by whom.

This command displays the system’s running configuration.

By default, only non-default settings are displayed.

This command reboots the system or initiates an upgrade of the firmware along with a reboot of the node or initiate an auto-init boot procedure along with a reboot of the node.

If no options are specified, the user is prompted to confirm the reboot operation.

If the now option is specified, boot confirmation messages appear.

This command saves the running configuration to a configuration file.

By default, the running configuration is saved to the primary configuration file.

This command enables the shell and kernel commands.

Note: This command should only be used with authorized direction from the Nokia Technical Assistance Center (TAC).

This command creates a system core dump.

Note: This command should only be used with authorized direction from the Nokia Technical Assistance Center (TAC).

This command updates the golden bootstrap image with the file-url, after validating it as a bootstrap image for the 7210 SAS platforms. Only on newer 7210 SAS-D platforms, the admin>update-golden-bootstrap CLI command does not update the golden-bootstrap image with the boot.tim specified in the parameter value, if the boot.tim is not a newer image.

This command enables the context to configure one of four available alarm contact input pins.

This command enables the context to relay alarms from the alarm-contact input to the alarm-contact output by associating an appropriate alarm-contact output with the alarm-contact input. The system generates or clears the alarm-contact output when it triggers or clears the alarm for the associated alarm-contact input.

If multiple alarm-contact input pins share an alarm-contact output, the system generates the alarm-contact output even if any one of the alarm-contact input is triggered and the system clears alarm-contact output only when all the alarm-contact input pins are cleared.

The severity parameter tser determines the appropriate alarm-contact output to be used for generation and clearing the alarm.

Note: The system relays the alarm-contact input to the appropriate alarm-contact output only if the alarm-contact output is available on the platform

This command enables the context to configure a text message for use along with SNMP trap and Log message that are sent when the system clears an alarm. The system generates a default message if the message is not configured. The system does not generate a trap or log if no form of this command is enabled.

This command describes an alarm contact input pin. The description provides an indication of the usage or attribute of the pin. It is stored in the CLI configuration file and helps the user in identifying the purpose of the pin.

This command configures the normal state to be associated with the alarm-contact input. When the system detects a transition from the normal state, an alarm is generated. The alarm is cleared when the system detects a transition is back to the normal state.

This command stops tracking the state changes associated with the alarm contact input. The system does not generate or clear the alarms for the alarm-contact input, but if an alarm is generated for the alarm-contact-input, the system clears the alarm when the shutdown command is executed.

The no form of this command starts tracking the state changes associated with the alarm contact input.

This command enables the context to configure a text message for use along with SNMP trap and Log message that are sent when the system generates an alarm. The system generates a default message if the message is not configured. The system does not generate a trap or log if no form of this command is enabled.

This command enables the context to configure system-wide Link Layer Discovery Protocol parameters.

This command configures the duration of the fast transmission period.

This command configures the number of LLDPDUs to send during the fast transmission period.

This command configures the minimum time between change notifications.

This command configures the time before reinitializing LLDP on a port.

This command configures the maximum consecutive LLDPDUs transmitted.

This command configures the multiplier of the tx-interval.

This command configures the LLDP transmit interval time.

This command enables the context to configure Link Layer Discovery Protocol (LLDP) parameters on the specified port.

This command configures destination MAC address parameters.

This command configures the administratively desired status of the local LLDP agent.

This command enables LLDP notifications.

The no form of this command disables LLDP notifications.

This command configures which management address to transmit.

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

This command specifies which LLDP TLVs to transmit.

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

This command enables the context to configure resource-profile parameters on the system.

This command provides the context to decommission a port. Ports which are decommissioned using this command are not available for provisioning services. The packet buffers are taken away from the decommissioned port and allocated to port(s) as specified by the entries configured under the decommission command. This command allows the user to allocate more packet buffers to certain port or a group of ports and enables those ports to absorb larger bursts.

This command allows the user to decommission a port or group of ports and allocate buffers to those ports which need more packet buffers for absorbing larger bursts. It allows user to configure the entries which list the ports to be decommissioned. Ports whose packet buffers are taken away are given on the left-hand of the to keyword, and ports to which buffers are allocated are given on the right-hand side.

This command allows users to specify either a port or a group of ports on the left-hand side of the to keyword, and a single port on the right-hand side of the to keyword. This allows the user to decommission up to two ports and allocate buffer to a single port.

Packet buffers taken away from a port or a group of ports specified on the left-hand side are distributed to the configured port on the right-hand side of the to keyword. Packet buffers are added to the MBS pool of the port (the MBS pool is shared by the 8 queues on the port) and the CBS portion of the queues is not modified.

The administrative state or the operational state of the port is not affected by configuring the port in a decommission entry.

Note: Any changes to the command, such as modifying the list of ports in existing entries or execution of no entry command or addition of new entries, takes effect only after a reboot of the node. The user is allowed to make change when the node is up, but the changes does not happen until a reboot of the system.

The software maintains two lists of entries, one which is in effect currently and one which has been modified by the user and takes effect during the next reboot. These lists can be displayed using the show command. The configuration file always stores the list of entries as configured by the user so that upon reboot, the modified entries and new entries (if any) take effect.

The following guidelines are to be adhered while configuring the entry command:

The no form of this command removes the entry from the list of decommissioned ports.

Note: The no form of this command requires a reboot to take effect.

The following examples show the list of ports, range of ports, and a combination of list of ports and range of ports that can be specified.

List of ports can be specified as:

Range of ports can be specified as:

This command enables the context to allocate resources from the egress internal TCAM pool.

The egress-internal-tcam resource pool is shared by multiple features. The resources are allocated in chunks of fixed sizes. The user is provided an option to allocate the available resources based on their scaling requirements for the features. The resource usage for different features is provided in the CLI description. It is not possible for a chunk to be shared by multiple features. Software allocates resources from the chunk to the feature to which it is allocated until it runs out of all resources in the chunk. If available, the user can allocate more chunks to the feature by taking away chunks of resources from other features that do not need to be enabled.

To free up the resources for use by other features, the users need to modify the configuration such that the chunks of resources in use by other features are freed. For example, to free up a chunk of resources allocated to egress ACLs mac-criteria and allocate it to ip-criteria, the user will need to remove the association of all the SAPs with egress ACLs that use a MAC criteria policy, then change the resource profile configuration to allocate the chunk to ip-criteria, and then create and associate the SAPs with ip-criteria. As another example, the user can free up a chunk of resources used by egress ACLs and allocate it towards a SAP egress aggregate meter (on platforms that support this feature). To do this, the user will need to remove the association of all the SAPs with egress ACLs, change the resource profile configuration to reduce the chunk of resources allocated to egress ACLs (and reduce the value of chunks in use by the egress ACLs match criteria), then allocate the chunk of resources to the SAP egress aggregate meter feature, and then configure the SAPs with the aggregate meter rate.

The egress-internal-tcam resource pool is shared among the following features on different platforms.

Note: When reassigning chunks of resources among features, a reboot of the node might be required. See the CLI description of the specific feature for information. The egress-internal-tcam pool of resources is allocated per node on the 7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C. The number of chunks and the number of resources per chunk varies among the different platforms. Contact your Nokia technical support representative for more information. For some features, a minimum number of chunks (greater than 1) must be allocated to enable the feature functionality. If this is not done, the software cannot allocate the required number of resources and it will fail the command associated with the feature.

This command enables the context to allocate maximum resources for use by egress filter policies using any of the supported match criteria. This command limits the total amount of chunks allocated for use by egress filter policies to the value specified by num-resources. In other words, the cumulative sum of chunks allocated to different match criteria supported by filter policies cannot exceed the value configured with num-resources.

Note: On the 7210 SAS-D and 7210 SAS-Dxp, the resources in the egress-internal-tcam resource pool are shared with other features (for example, SAP egress aggregate meter). To assign resources to this feature, resources may be reallocated from other features by disabling the policy association with a SAP. On the 7210 SAS-D and 7210 SAS-Dxp, some of the egress ACL match criteria require a minimum number of resources greater than 1 to be allocated before the match criteria can be used. Use of the SAP egress aggregate meter and the use of egress ACLs with the following match criteria: mac-ipv4 match, ipv6-128bit match, and mac-ipv6-64bit match, are mutually exclusive. All these match criteria require a minimum of two resources. SAP egress aggregate meter and egress ACLs MAC match criteria can be enabled simultaneously, with each feature sharing the available resources equally among them. On the 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C, when resources are allocated to egress ACLs from the egress internal TCAM pool, these resources can be used by MAC criteria entries, IPv4 entries, and entries that use only IPv6 64-bit addresses.

When the user allocates resources for use by SAP egress ACL policies using this command, the system allocates resources in chunks of 128 entries for the 7210 SAS-D and 7210 SAS-Dxp, 510 entries for the 7210 SAS-K 2F1C2T, and 7210 SAS-K 2F6C4T, and 180 entries for the 7210 SAS-K 3SFP+ 8C. The resources are used only for filter entries configured under IPv4 criteria or MAC criteria.

For the 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C, if the user needs to use IPv6 criteria, resources must be allocated using the mac-ipv4-ipv6-128-match-enable command under this command context. The resources allocated using this command are used for filter entries configured under IPv6 criteria, IPv4 criteria, or MAC criteria. Each IPv6, IPv4, or MAC filter entry consumes two resources from this pool, reducing the number of filter entries that can be accommodated in a single chunk to 255 entries for the 7210 SAS-K 2F1C2T and 7210 SAS-K 2F6C4T, and 108 entries for the 7210 SAS-K 3SFP+ 8C. The user can choose to allocate all the chunks allocated for SAP egress ACL policies for IPv6 criteria or allocate only a portion of it.

For information on resource allocation for the match criteria used in egress filter policies, refer to the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Router Configuration Guide.

The no form of this command is blocked by the CLI and cannot be used on the 7210 SAS-K 3SFP+ 8C.

The no form of this command specifies that the software does not allocate any resources for use by egress filter policies on the 7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F1C2T, and 7210 SAS-K 2F6C4T. If no resources are allocated for use, then the software fails all attempts to associate a service entity (for example, SAP, IP interface) with a filter policy using any of the match criteria.

This command enables the context to allocate resources for use by SAP egress aggregate policer from the egress-internal-tcam resource pool. This command limits the total amount of chunks allocated for use by SAP egress aggregate meter to the value specified by num-resources.

Note: The resources in the egress-internal-tcam resource pool are shared with other features; for example, SAP egress aggregate meter. To assign resources to this feature, resources may be reallocated from other features by disabling the policies association with a SAP, and others. On the 7210 SAS platforms, some of the Egress ACL match criteria require a minimum amount of resources greater than 1, to be allocated before the match criteria can be used. In other words, use of SAP egress aggregate meter is mutually exclusive to use of egress ACLs with the following match criteria - mac-ipv4 match, ipv6-128bit match, mac-ipv6-64bit match. All these match criteria require a minimum of 2 resources. SAP egress aggregate meter and egress ACLs MAC match criteria can be enabled simultaneously, with each feature sharing the available resources equally among them.

The no form of this command specifies that the software does not allocate any resources for use by SAP egress aggregate policer. If no resources are allocated for use, then the software fails all attempts to enable the configuration of the command for a SAP.

This command reserves a resource chunk for use by the MAC authentication feature.

The no form of this command releases any resource chunks that were previously reserved for use by the MAC authentication feature.