03267-02 ATCA Command Line Interface Reference

www.radisys.com

PROMENTUMCOMMAND LINE INTERFACE REFERENCE

FOR MANAGEMENT PROCESSORSATCA-1200 QUAD AMC CARRIERATCA-2210 SWITCH AND CONTROL MODULEATCA-7220 PACKET PROCESSING MODULEATCA-9100 MODULE RESOURCE MODULE

FOR GENERAL PURPOSE COMPUTING PROCESSORSATCA-4300 COMPUTE PROCESSING MODULEATCA-4310 COMPUTE PROCESSING MODULECE3100 COM EXPRESS MODULE

SOFTWARE VERSION 3.3.0

007-03267-0002 September 2008

2Release history

Release Date Description-0000 May 2008 First release.-0001 June 2008 Added information for ATCA-9100 F-DSP farms.-0002 September 2008 Updated to include the ATCA-7220, 3.3.0 software features, and other

corrections and clarifications.

Copyright 2008 by RadiSys Corporation. All rights reserved. RadiSys is a registered trademark and Promentum is a trademark of RadiSys Corporation. AdvancedTCA, ATCA, and PIGMG are registered trademarks of PCI Industrial Computer Manufacturers Group. Linux is a registered trademark of Linus Torvalds. All other trademarks, registered trademarks, service marks, and trade names are the property of their respective owners.

3TABLE OF CONTENTS

Preface .......................................................................................................................................... 7About this manual ................................................................................................................................................................. 7Notational conventions ........................................................................................................................................................ 7Related Promentum manuals............................................................................................................................................. 8Where to get more product information ......................................................................................................................... 8

CLI Basics ...................................................................................................................................... 9Chapter 1: Command Line Interface Overview....................................................................................................................11

Layout of command descriptions .....................................................................................................................................11Accessing the master CLI ................................................................................................................................................... 12Displaying available commands and options ............................................................................................................... 12no commands................................................................................................................................................................... 13show commands.............................................................................................................................................................. 13Command line completion ............................................................................................................................................... 13Editing and history keys ..................................................................................................................................................... 13Error messages..................................................................................................................................................................... 13Idle timeout............................................................................................................................................................................14exit and logout commands .........................................................................................................................................14Saving configurations to flash............................................................................................................................................14

Chapter 2: Command Modes .................................................................................................................................................. 15Master CLI ............................................................................................................................................................................. 15Blade management command modes........................................................................................................................... 15Platform management command modes ......................................................................................................................16Ethernet command modes ................................................................................................................................................19Blade diagnostic command mode .................................................................................................................................. 23

Chapter 3: Master CLI Commands ......................................................................................................................................... 25

4Table of Contents

Blade Management ...................................................................................................................35Chapter 4: CLI Logging Commands ....................................................................................................................................... 37Chapter 5: NTP Server Control Commands.......................................................................................................................... 39Chapter 6: Management Interface Commands ................................................................................................................... 41Chapter 7: Operational State Commands ............................................................................................................................. 55Chapter 8: Network Timing Subsystem Commands .......................................................................................................... 61Chapter 9: RADIUS Authentication Commands .................................................................................................................. 95Chapter 10: SSH Management Commands.........................................................................................................................101Chapter 11: SNMP Agent Control Commands................................................................................................................... 103Chapter 12: SNMP Trap Generation Commands ...............................................................................................................113Chapter 13: Syslog Commands ............................................................................................................................................. 137Chapter 14: Telnet Server Commands ..................................................................................................................................141Chapter 15: TFTP Management Commands ...................................................................................................................... 143Chapter 16: Watchdog Commands....................................................................................................................................... 145Chapter 17: sRIO Switch Commands ................................................................................................................................... 149Chapter 18: DSP Commands ................................................................................................................................................. 155

Platform Management ............................................................................................................181Chapter 19: Master Platform Management Commands .................................................................................................. 183Chapter 20: Shelf Management Commands.......................................................................................................................191Chapter 21: Alarm Commands ..............................................................................................................................................205Chapter 22: Control Commands ........................................................................................................................................... 213Chapter 23: Sensor Commands ............................................................................................................................................ 221Chapter 24: Slot Type and FRU Commands.......................................................................................................................223

Table of Contents

5

Ethernet Switching...................................................................................................................233Chapter 25: Port Configuration Commands.......................................................................................................................235Chapter 26: Spanning Tree Commands ..............................................................................................................................245Chapter 27: Priority Provisioning Commands .................................................................................................................... 271Chapter 28: VLAN Commands ..............................................................................................................................................273Chapter 29: Double VLAN Commands ...............................................................................................................................303Chapter 30: Class of Service (CoS) Commands ................................................................................................................309Chapter 31: GARP Commands ..............................................................................................................................................327Chapter 32: GMRP Commands............................................................................................................................................. 331Chapter 33: GVRP Commands ..............................................................................................................................................335Chapter 34: Storm Control Commands...............................................................................................................................339Chapter 35: Denial of Service Commands..........................................................................................................................355Chapter 36: DiffServ Commands ..........................................................................................................................................363Chapter 37: Link Aggregation Commands...........................................................................................................................419Chapter 38: Port Mirroring Commands............................................................................................................................... 431Chapter 39: Port Security Commands..................................................................................................................................435Chapter 40: Port Filtering Commands .................................................................................................................................445Chapter 41: MAC Filtering Commands ................................................................................................................................ 451Chapter 42: MAC Database Commands .............................................................................................................................459Chapter 43: IGMP Snooping Commands ...........................................................................................................................463Chapter 44: Link Layer Discovery Protocol Commands ..................................................................................................465Chapter 45: Network Interface Commands........................................................................................................................473Chapter 46: Switch Information Commands......................................................................................................................475Chapter 47: Logging Commands ..........................................................................................................................................495Chapter 48: Clear and Exit Commands ...............................................................................................................................499Chapter 49: Configuration Scripting Commands ..............................................................................................................509

IP Routing..................................................................................................................................515Chapter 50: Routing Setup Commands................................................................................................................................517Chapter 51: ARP Commands..................................................................................................................................................539Chapter 52: VRRP Commands............................................................................................................................................... 551Chapter 53: RIP Commands...................................................................................................................................................563Chapter 54: Loopback Interface Commands .....................................................................................................................583Chapter 55: Multicast Routing Commands.........................................................................................................................585Chapter 56: IGMP Commands ..............................................................................................................................................605Chapter 57: DVMRP Commands........................................................................................................................................... 621

6Table of Contents

Blade Diagnostics ....................................................................................................................629Chapter 59: LMP-Controlled Diagnostic Commands ....................................................................................................... 631Chapter 59: sRIO Switch Diagnostic Commands ..............................................................................................................643Chapter 59: DSP Diagnostic Commands ............................................................................................................................649

Appendices ...............................................................................................................................659Appendix A: Slot and Port Identifiers....................................................................................................................................661

IPMB addresses of module and FRU slots ..................................................................................................................661Slot/port number combination used in Ethernet CLI ...............................................................................................662

Appendix B: Index of Commands .........................................................................................................................................669

7PREFACE

About this manualThe manual describes the command line interface (CLI), which lets you interactively configure and monitor a wide range of services on these Promentum AdvancedTCA (ATCA) modules:

ATCA-1200 Quad AMC Carrier ATCA-2210 Switch and Control Module (SCM) ATCA-2210 SCM with CE3100 COM Express Module ATCA-4300 Compute Processing Module (CPM) ATCA-4310 Compute Processing Module ATCA-7220 Packet Processing Module (PPM) ATCA-9100 Module Resource Module (MRM)

Differences in the way individual commands support the modules are noted for each command. Where differences exist, the relevant modules are identified by their model number.

Notational conventionsThis manual uses the following conventions:

BoldText A keyword.

ItalicText Directory, file, function, and utility names.

MonoText Screen text and syntax strings.BoldMonoText A command to enter.ItalicMonoText Variable parameters.

Angle brackets < > A symbolic name that represents a command-line argument or variable parameter to be replaced by an actual value.

Brackets [ ] Command options.

Curly braces { } A grouped list of parameters.

Vertical line | An OR in the syntax. Indicates a choice of parameters.

All numbers are decimal unless otherwise stated.

Preface

8

Related Promentum manualsThe following software and hardware information is available for Promentum front modules:

Front module installation and initial setup instructions. The installation guide for each front module provides the steps for installing the module into a shelf and completing the initial configuration.

Front module hardware and troubleshooting information. The reference manual for each front module describes the modules hardware features and operation. The reference manuals also contain information on Intelligent Platform Management Interface (IPMI) commands, diagnostic tests, and troubleshooting.

Software information. The Software Guide for Management Processors and General Purpose Computing Processors describes the software concepts, configuration procedures, and usage. Overviews of the software interfaces, the preinstalled software, and the supplied Linux packages are also included.

Shelf Manager information. The Shelf Management Software Reference describes the architecture and operation of the Shelf Manager. The Shelf Manager runs on the Promentum SCM and controls and monitors operations on the shelf. This manual includes information on using, configuring, and troubleshooting the Shelf Manager.

Where to get more product informationPlease visit the RadiSys Web site at www.radisys.com for product information and other resources. Downloads (manuals, release notes, software, etc.) are available via the Technical Support Library product links at www.radisys.com/support or the product pages at www.radisys.com/products.

CLI BASICS

COMMAND LINE INTERFACE OVERVIEWCOMMAND MODESMASTER CLI

CLI Basics: Command Line Interface Overview 11

1COMMAND LINE INTERFACE OVERVIEW

The command line interface (CLI) is an interface you can use to configure and monitor a wide range of services on Promentum AdvancedTCA (ATCA) front modules. The CLI lets you:

Perform management tasks interactively. Repeat a large number of steps easily by running batch files of commands. Create multiple, related configurations by writing a script (in a language such as Perl) that

runs on an external processor and generates related batch files.

The material presented here is not introductory; it assumes you have some experience using Linux and are already familiar with the intended use of the Promentum front modules installed in your system.

Layout of command descriptionsThe command descriptions are grouped by the command type in this manual. If a command is an IP routing command, it is grouped with the other IP routing commands. The commands are further divided by their specific function. For example, the ARP commands are all grouped together in an ARP commands section.

The command descriptions contain the following types of information:

Supported on specifies the modules from which the command is available. Mode specifies the command mode from which to access the command. In addition, this

information is linked to the description of the mode in the Chapter 2, Command Modes on page 15.

Syntax shows the syntax format for the command and includes any parameters or variables needed or available for the command.

Options describes any options that are available. Output (if applicable) describes any resulting output after the command is issued. This

field only appears in the command description when it is applicable.

Examples (if applicable) shows examples of how to use the command. This field only appears in the command description when an example is given.

Default lists the default state for the command. See also lists any related commands. no form (if applicable) describes the no form of the command. This field only

appears in the command description when a no form of the command exists.

1 Command Line Interface Overview

12 CLI Basics: Command Line Interface Overview

Accessing the master CLIThe master CLI is the top level of the Promentum CLI. Once you have accessed the master CLI, you can access other command modes to issue specific commands. To access the master CLI:

1. Connect to the module.

2. Log in to the CLI.

The way you connect or log in may vary for each module. Refer to a modules installation guide or reference for the module-specific instructions.

Once you are logged in to the master CLI, you have access to different command modes, which group similar subsets of commands together. For more information on the command modes and how they are used to access commands, see Chapter 2, Command Modes on page 15.

Displaying available commands and optionsTo access online help while typing commands, enter a question mark (?). The CLI returns a list of the commands or options available in your current mode. This example shows the master command CLI list on the ATCA-1200.

ATCA-1200# ?ethernet : Start ethernet CLIcopy : Copy information to and from the bladeerase : Erase startup configurationboot-flash : Select which flash part is to be used to boot the LMPblade-mgmt : Blade management configuration and statuslinux-shell : Start the Linux shellshow : Show configuration and statusexit : Logout from CLI sessionlogout : Logout from CLI sessionhelp : Operation instructions

For help on a specific command, type as much as you know of the command and follow it with a question mark. Many commands require multiple arguments (often file or directory names for input or output), each one shown as the next option when you type a question mark. After entering an option, type a question mark again to see if there are more options.

The notation indicates the carriage return as an option. Press Enter to execute the command.

1no commands

CLI Basics: Command Line Interface Overview 13

no commandsMany configuration commands have a no form that is used to disable, to delete, or to reset a configuration back to the factory defaults.

For example, the following command administratively disables a port:

shutdown

The no form of this command administratively enables a port:

no shutdown

show commandsA show command displays information about resources. The show commands are executed outside of the standard configuration modes; they are executed directly within a main command mode, such as the Ethernet mode.

For example, the current hardware configuration loaded on a module is displayed when you enter the following command from the master CLI:

show hardware

Command line completionPressing the tab key completes a partially typed command keyword. For example, typing a partial command, con, and pressing the tab key completes the keyword configure.Typing a question mark (?) lists valid entries after a command keyword. For example, typing the keyword configure and then a question mark brings up a list of valid options that follow configure.

Editing and history keysThe editing key sequences are similar to those used by EMACS text editors. Any character typed is inserted into the command line at the current cursor position, and all characters to the right of the typed character shift to the right.

The history key sequence is similar to that used by the UNIX C shell.

You can obtain a list of key sequences by entering help at the main CLI prompt.

Error messagesIf you make a mistake entering a command, the system responds with an error message that may help you correct the problem. The system may display the correct syntax or indicate that an invalid interface was selected. In the following case, the system marks where it detected invalid input and shows this message.

% Invalid input detected at ^ marker.

1 Command Line Interface Overview

14 CLI Basics: Command Line Interface Overview

Idle timeoutAn Idle Timeout message displays when you not enter a command within the specified timeout threshold while in an Ethernet mode. When this occurs, the system returns you to the master CLI, but does not log you off the module.

Use the telnetcon timeout command on page 474 to change the timeout length.

exit and logout commandsThe CLI uses both exit and logout commands. The exit command is available from any location in the CLI hierarchy, but the result of issuing the command varies depending on the location. The logout command is only available from the master CLI. To exit the current command mode and return to the previous command mode in the CLI hierarchy, enter:

exit

To exit from the master CLI and log off the module from the session, you have the choice of entering:

exitor

logout

Saving configurations to flashSome CLI configuration changes are kept within the application until you save them to flash on a module or on another system. If a save is not performed, your unsaved changes will remain in effect until the module is rebooted. At reboot, the startup configuration will be restored.

For example, to save configuration changes in Ethernet switching and blade management command modes, enter:

copy system:running-config nvram:startup-configYou may also save changes when exiting the current mode. Enter y as prompted.

CLI Basics: Command Modes 15

2COMMAND MODES

The CLI is divided into several command modes that give access to different subsets of commands. The top level of the CLI is called the master CLI. From the master CLI you can access the other command modes.

The primary command modes are:

Master CLI Blade management Platform management Ethernet Blade diagnostics

Master CLI A limited number of commands can be executed directly from the master CLI, but most of the commands are tied to a particular command mode. See Master CLI Commands on page 25 for a list of the master CLI commands.

Blade management command modesThe blade management command modes, blade-mgmt and config, contain commands for configuring the various services provided by the modules, including Linux services, SNMP, and network timing.

The instructions on how to access the command modes are included below. The blade management commands start on page 35.

blade-mgmt Supported on: All modules

From the master CLI, enter the following syntax to access the blade-mgmt mode:

blade-mgmt

configSupported on: All modules

Enter the configuration mode from the blade-mgmt mode:

config

2 Command Modes

16 CLI Basics: Command Modes

Platform management command modesThe platform-management command modes are available on the ATCA-2210 Switch and Control Module (SCM) when the Shelf Manager is running. The commands should be performed from the SCM hosting the active Shelf Manager.These command modes contain commands for configuring the Shelf Manager, controlling the Shelf Manager service, viewing and acknowledging all alarms in the shelf, and viewing information about the field replaceable units (FRUs) installed in the shelf.

The instructions on how to access the command modes are included below. The platform management commands start on page 181.

platform-mgmtSupported on: ATCA-2210

This is the top level of the platform management command mode hierarchy. From this command mode, you can perform a discovery of all shelf resources and view summary information about alarms, sensors, and FRUs.

From the master CLI, enter:

platform-mgmt

alarmsSupported on: ATCA-2210

The alarms mode is where you view, acknowledge, and add alarms.

From the platform-mgmt mode, enter:

alarms

controlsSupported on: ATCA-2210

The controls mode is where you set the HPI controls, configure items such as the shelf address, Shelf Manager IP address, and FRU power-on sequences.

From the platform-mgmt mode, enter:

controls

2Platform management command modes


frontSupported on: ATCA-2210

The front command mode is where you access the installed front modules to initiate FRU hot-swap events, reset FRUs, or view FRU-specific information such as sensor data.

For example, to configure a module installed in a front slot, enter the following from the platform-mgmt mode:

front

The possible values for the front modules in RadiSys shelves are shown below.

fanSupported on: ATCA-2210

The fan command mode is where you access the installed fans to initiate FRU hot-swap events, reset FRUs, or view FRU-specific information such as sensor data.

For example, to configure a fan, you enter the following from the platform-mgmt mode:

fan

The possible values for the fans in RadiSys shelves are shown below.

Table 1. Front values

slot_type valueslot_num values

ATCA-6000 ATCA-6006 ATCA-6014 ATCA-6016front 1-14 1-6 1-14 1-16

Table 2. Fan values


ATCA-6000 ATCA-6006 ATCA-6014 ATCA-6016fan 1-4 1-2 1-3 1-3

2 Command Modes


pemSupported on: ATCA-2210

The pem command mode is where you access the installed PEMs to initiate a FRU hot-swap event, reset the FRU, or view information such as slot or FRU sensor data.

To configure a PEM, you enter the following from the platform-mgmt mode:

pem

The possible values for RadiSys shelves are shown below.

peripheralSupported on: ATCA-2210

The peripheral command mode is where you access the RadiSys Chassis Managers (RCMs), which are installed in ATCA-6014 and ATCA-6016 shelves, to initiate a FRU hot-swap event, reset the FRU, or view FRU-specific information such as sensor data.

For example, to configure an RCM, you enter the following from the platform-mgmt mode:

peripheral

The possible values for the RadiSys shelves are shown below.

Note: If two RCMs are installed, RCM 1 is located on the left and RCM 2 is on the right. If only one RCM is installed, it is assigned the value of 1 regardless of its location.

sensorsSupported on: ATCA-2210

The sensors command mode is where you can view information on the shelf sensors, including the aggregate thermal, power, and operational sensors.

From platform-mgmt mode, enter:

sensors

Table 3. PEM values


ATCA-6000 ATCA-6006 ATCA-6014 ATCA-6016pem 1-2 1-2 1-2 1-2

Table 4. Peripheral values


ATCA-6014 ATCA-6016 peripheral 1-2 1-2

2Ethernet command modes


shelf-mgmtSupported on: ATCA-2210

The shelf management command mode is where you view or change Shelf Manager-specific status and role. This mode also is where you can stop and restart the Shelf Manager and cause a failover to the peer Shelf Manager.

From platform-mgmt, enter:

shelf-mgmt

Ethernet command modesThe Ethernet command mode is available on the modules with Ethernet switches: ATCA-1200, ATCA-2210, ATCA-7220, and ATCA-9100. From this command mode, you can view and change the Ethernet switch settings and, if enabled as a build option, the IP routing settings on the Ethernet switch.

Privileged EXEC Supported on: ATCA-1200, ATCA-2210, ATCA-7220, ATCA-9100

This is the first level command mode of the switching CLI. From this mode, you can view and change settings for a switch, and access other Ethernet switching command modes.

ATCA-1200From the master CLI, enter:

ethernet

ATCA-2210 and ATCA-9100To access the Base Ethernet CLI, enter the following from the master CLI:

base-ethernet

To access the fabric interface, enter the following from the master CLI:

fabric-ethernet

Global Config Supported on: ATCA-1200, ATCA-2210, ATCA-7220, ATCA-9100

This command mode is where general Ethernet switching setup commands are grouped and and is where you can make modifications to the running configuration.

From the Privileged EXEC mode, enter:

configure

2 Command Modes


Interface Config Supported on: ATCA-1200, ATCA-2210, ATCA-7220, ATCA-9100

This command mode is where you set up or modify the operation of a single interface port.

From the Global Config mode, enter:

interface

VLAN ConfigSupported on: ATCA-1200, ATCA-2210, ATCA-7220, ATCA-9100

This command mode is where you configure VLAN settings.

From the Privileged EXEC mode, enter:

vlan database

Class-Map ConfigSupported on: ATCA-1200, ATCA-2210, ATCA-7220, ATCA-9100

This command mode is where you configure or create quality of service (QoS) class maps for diffserv.

What you enter to access this command mode depends on whether you are configuring an existing diffserv class or creating a new diffserv class.

To configure an existing diffserv classFrom the Ethernet-specific Global Config mode, enter:

class-map

To create a new diffserv class From the Global Config mode, enter:

class-map match-all

The match-all indicates all of the individual match conditions must be true for a packet to be considered a member of the class. Once a class-map is created, you can then change the configuration settings.

Policy-Map ConfigSupported on: ATCA-1200, ATCA-2210, ATCA-7220, ATCA-9100

This command mode is where you configure QoS policy map settings for diffserv.

What you enter to access this command mode depends on whether you are configuring an existing diffserv policy or creating a new diffserv policy.

2Ethernet command modes


To configure an existing diffserv policyFrom the Global Config mode, enter:

policy-map

To create a new diffserv policy From the Global Config mode, enter:

policy-map in

Policy-Class-Map Config Supported on: ATCA-1200, ATCA-2210, ATCA-7220, ATCA-9100

This command mode is where you create, delete, and match policies for existing diffserv classes.

From the Policy-Map Config mode, enter:

class

Fields-Template Config Supported on: ATCA-1200, ATCA-2210, ATCA-7220, ATCA-9100

This command mode is where you create or configure the template that defines the fields to match to packet headers.

To create and configure a new template From the Global Config mode, enter:

fields-template create

To configure an existing templateFrom the Global Config mode, enter:

fields-template

2 Command Modes


Fields-Instance Config Supported on: ATCA-1200, ATCA-2210, ATCA-7220, ATCA-9100

This command mode is where you define the values to match to packet headers when using a user-defined template.

To configure an existing instanceFrom the Global Config mode, enter:

fields-instance

To create and configure a new instance From the Global Config mode, enter:

fields-instance create

Once a template is created, you can then change the configuration settings.

Router OSPF Config Supported on: ATCA-2210

This command mode is where you configure Open Shortest Path First (OSPF) settings. This command mode is available when IP routing software is an enabled on the ATCA-2210.


router ospf

Router RIP Config Supported on: ATCA-2210

This command mode is where you configure the routing information protocol (RIP) settings. This command mode is available when IP routing software is enabled on the ATCA-2210.


router rip

2Blade diagnostic command mode


Blade diagnostic command modeDiagnostic tests and commands can be run from the CLI for the ATCA-7220 and ATCA-9100. For information on how to run diagnostic tests on the other modules, see their module-specific reference manuals.

blade-diagsSupported on: ATCA-7220, ATCA-9100

This command mode is where you execute field diagnostics. From the master CLI, enter:

blade-diags

You can cancel tests that are invoked from the CLI while they are running by pressing Ctrl-c. For details on running multiple iterations and stopping tests when errors occur, see the command descriptions for each blade diagnostic.

2 Command Modes


CLI Basics: Master CLI Commands 25

3MASTER CLI COMMANDS

copy Depending on which options you select, this command: saves and then uploads the specified configuration file to the designated URL or reloads the specified configuration file so it becomes the running configuration.

Supported on: All modules

Mode: Master CLI

Syntax: copy Options: The original file location from which to copy.

Specifies where to copy the file.

Possible values for and are:nvram:startup-config

Reloads the configuration to RAM, making that configuration the current configuration. Saves the current running configuration to permanent storage on the module or to another system. If saved to permanent storage, the saved configuration is reloaded when the module is rebooted.

system:running-configLoads the configuration to RAM, making it the current running configuration.

tftp: A valid path reachable on the network using tftp.sftp: A valid path reachable on the network using sftp.

Examples:

To copy the configuration file to a specified URL:copy nvram:startup-config {tftp: | system:running-config}To copy the configuration file from a specified URL:copy {tftp: | system:running-config} nvram:startup-configTo copy the currently running configuration file to another system: copy system:running-config {tftp: | nvram:startup-config}

3 copy

26 CLI Basics: Master CLI Commands

Default: n/a

See also:

3erase nvram:startup-config


erase nvram:startup-configDeletes the saved CLI configuration files from the startup. Upon restart, the modules components will use the factory default configuration.

Note: This command currently only affects the blade-management mode configuration.


Mode: Master CLI

Syntax: erase nvram:startup-configOptions:

Default:

See also:

3 exit


exitLeaves the current CLI command mode and returns to the preceding command level.

For example, if you are in the configuration mode (config) under the blade-management mode (blade-mgmt) and enter exit, you will be returned to the blade-management mode level. If you are already in the master CLI (at the top level), this commands behaves as the logout command. The command exits the CLI and logs out from the module if you logged on using the admin login or returns you to Linux if you logged on using the root login.


Mode: All modes

Syntax: exitOptions: none

Default: n/a

See also: logout

3help


helpShows the editing and the history keys.


Mode: All modes

Syntax: helpOptions: none

Default: n/a

See also: Editing and history keys on page 13

3 logout


logoutThis command works only from the master CLI (top level). The command exits the master CLI and logs out from the module if you logged on using the admin login or returns you to Linux if you logged on using the root login.


Mode: Master CLI

Syntax: logoutOptions: none

Default: n/a

See also: exit

3show hardware


show hardwareDisplays the current hardware configuration loaded on the module. This includes information such as the processor type and the chipset type. The flash partition from which the LMP was booted is also identified.


Mode: Master CLI

Syntax: show hardwareOptions: none

Default: n/a

See also: show version

3 show mcli-version


show mcli-versionDisplays the version of the mcli loaded on the module.


Mode: Master CLI

Syntax: show mcli-versionOptions: none

Default: n/a

See also: show version

3show running-config


show running-configDisplays the currently running configuration.


Mode: Master CLI

Syntax: show running-configOptions: none

Default:

See also:

3 show version


show versionShows the version number for the LMP software and other programmable components on the blade like the IPMC, the FPGA, and the CPLD.


Mode: Master CLI

Syntax: show versionOptions: none

Default:

See also:

BLADE MANAGEMENT

CLI LOGGINGNTP SERVER CONTROL MANAGEMENT INTERFACEOPERATIONAL STATENETWORK TIMING SUBSYSTEMRADIUS AUTHENTICATIONSSH MANAGEMENTSNMP AGENT CONTROL SNMP TRAP GENERATIONSYSLOGTELNET SERVERTFTP MANAGEMENTWATCHDOGsRIO SWITCHDSP

Blade Management: CLI Logging Commands 37

4CLI LOGGING COMMANDS

service cli-loggingStarts or restarts the cli-logging service.


Mode: config

Syntax: service cli-logging Options: Restarts the cli-logging service.

Reads the current configuration file and applies it without shutting down and restarting the service.

Default: n/a

See also:

no service cli-loggingTurns off the cli-logging service.

4 show service cli-logging

38 Blade Management: CLI Logging Commands

show service cli-loggingDisplays the state of CLI command logging service (enabled or disabled) and the location of the initialization (init) file.


Mode: blade-mgmt

Syntax: show service cli-loggingOptions: none

Default:

See also: service cli-logging

Blade Management: NTP Server Control Commands 39

5NTP SERVER CONTROL COMMANDS

service ntpd Starts, restarts, or reconfigures the NTP service.

Supported on: ATCA-1200, ATCA-2210, ATCA-7220, ATCA-9100

Mode: config

Syntax: service ntpd [ restart | reconfigure ]

Options:restart Starts or restarts the NTP service.

reconfigure Reads and applies the current configuration file without shutting down and restarting the service.

Default:

See also:

no service ntpdStops the NTP service.

Syntax: no service ntpd

5 show service ntpd

40 Blade Management: NTP Server Control Commands

show service ntpd

Displays the administrative state of the NTP server (enabled or disabled) and the location of the initialization (init) file.


Mode: blade-mgmt

Syntax: show service ntpd

Options: none

Default:

See also:

Blade Management: Management Interface Commands 41

6MANAGEMENT INTERFACE COMMANDS

interface network dhcp renewRenews the IP address for the dynamic management interface on either the Base or the Fabric interface, depending on your designation.


Mode: config

Syntax: interface network { base | fabric } dhcp renewOptions:base Renews the management interface associated with the Base Ethernet

interface.

fabric Renews the management interface associated with the Fabric Ethernet interface.

Default: n/a

See also:

6 interface network ip

42 Blade Management: Management Interface Commands

interface network ipConfigures an alternate static IP address and subnet mask for the static management interface on either the Base or the Fabric interface, depending on your designation. This command can also configure an optional gateway.

A subinterface for the Base or Fabric management interface is created the first time you execute this command. You can use the command again to change the IP address and subnet mask for the subinterface. See the Software Guide for information on the subinterfaces created for each module.

Note: The specified IP address and gateway must be on the same subnet.


Mode: config

Syntax: interface network { base | fabric } ip [ ]

Options:base Creates a subinterface associated with the Base Ethernet interface.

fabric Creates a subinterface associated with the Fabric Ethernet interface.

Configures an alternate static IP address.

Configures an alternate subnet mask.

Configures an alternate gateway. This an optional parameter.

Default: the subinterface does not exist

See also: show interface network

6interface network shutdown


interface network shutdownDisables the management interfaces on either the Base or the Fabric Ethernet interface, depending on your designation.


Mode: config

Syntax: interface network { base | fabric } shutdownOptions:base Disables the management interface associated with the Base Ethernet

interface.

fabric Disables the management interface associated with the Fabric Ethernet interface.

Default: n/a

See also: show interface network

no interface network shutdownEnables the management interface on either the Base or the Fabric interface, depending on your designation.

Syntax: no interface network { base | fabric } shutdown

6 interface serviceport ip


interface serviceport ipConfigures an alternate static IP address, subnet mask, and gateway for the Ethernet maintenance port. For the ATCA-1200 and ATCA-9100, the Ethernet maintenance port and subinterface are available only when an optional RTM is installed.

The created subinterface is eth0:1. The specified IP address and gateway must be on the same subnet.


Mode: config

Syntax: interface serviceport ip [ ]

Options:: Configures an alternate static IP address.

Configures an alternate subnet mask.

Configures an alternate gateway. This an optional parameter.

Default: the subinterface does not exist

See also: show interface serviceport

6service amc


service amcStarts, restarts, or reloads the specified AMC.

Supported on: ATCA-1200

Mode: config

Syntax: service amc Example: service amc1Options: The service stops, any log files are deleted, and the services restarts using

the current configuration file.

Reads the current configuration file and applies the configuration without shutting down and restarting the service.

Default:

See also: show service amc

no service amcDisables the AMC service.

Syntax: no service amc

6 service dhcpd


service dhcpdEnables the DHCP server.


Mode: config

Syntax: service dhcpd [restart]Options:restart Restarts the DHCP server.

Default: disabled

See also:

no service dhcpdDisables the DHCP server.

Syntax: no service dhcpd

6service rtm


service rtmStarts, restarts, or reloads the RTM service. During a reload, the service continues running, but loads the current configuration file.

Supported on: ATCA-1200, ATCA-7220, ATCA-9100

Exceptions: When no RTM is present, this command is unavailable.

Mode: config

Syntax: service rtm [restart | reconfigure]Options:restart Restarts the RTM service.

reconfigure Loads the current configuration file.

Default: disabled

See also: show service rtm

no service rtmDisables the RTM service.

Syntax: no service rtm

6 show interface network


show interface networkDisplays configuration settings associated with the management interfaces on either the Base or the Fabric interface, depending on your designation.


Mode: blade-mgmt

Syntax: show interface network [ base | fabric ]Options:base Shows the management interface configuration associated with the Base

Ethernet interface.

fabric Disables the management interface configuration associated with the Fabric Ethernet interface.

Output:Name The name of the IP interface in Linux.

Status Whether the interface is up or down.

HW Address The MAC address of the interface.

Sub IF The IP subinterface name in Linux.

IP Address The IP address of the interface. There is no default address.

Netmask The IP subnet mask for this interface.

Broadcast The broadcast address for this interface.

Gateway The default gateway for this interface.

Default: n/a

See also: interface network ip

6show interface serviceport


show interface serviceportDisplays configuration settings associated with an Ethernet maintenance port when an optional RTM is installed.


Mode: blade-mgmt

Syntax: show interface serviceportOptions: none

Output:

Name The name of the IP interface in Linux.

Status Whether the interface is up or down.

HW Address The MAC address of the interface.

Sub IF The IP subinterface name in Linux.

IP Address The IP address of the interface. There is no default address.

Netmask The IP subnet mask for this interface.

Broadcast The broadcast address for this interface.

Gateway The default gateway for this interface.

Default: n/a

See also: interface serviceport ip

6 show service amc


show service amcShows the administrative state of the ATM and the location of the initialization (init) file.


Mode: blade-mgmt

Syntax: show service amcOutput: Enabled or disabled. Also shows the location of the init file.

Default:

See also: service amc

6show service dhcpd


show service dhcpd

Displays the administrative state of the DHCP server (enabled or disabled) and the location of the initialization (init) file.


Mode: blade-mgmt

Syntax: show service dhcpd

Output: Enabled or disabled. Also shows the location of the init file.

Default:

See also: service dhcpd

6 show service rtm


show service rtmShows the administrative state of the RTM service and the location of the initialization (init) file.


Exceptions: When no RTM is present, this command is unavailable.

Mode: blade-mgmt

Syntax: show service rtmOutput: Enabled or disabled. Also shows the location of the init file.

Default: n/a

See also: service rtm

6show sel


show selShows the contents of the modules local system event log (SEL).

Notes: The time it takes for the SEL to display may vary depending on how much information has

been gathered. When run from an ATCA-2210, this command shows the SEL for the entire shelf. For information on the show sel command that displays the global SEL, see page 201.


Mode: blade-mgmt

Syntax: show selOptions: none

Output: Displays the IDs, the date, and the timestamp for each logged event and provides a description of the sensor or the post event. For example, a sensor-specific event would include the sensors logged threshold value.

Default: n/a

See also:

6 show sel


Blade Management: Operational State Commands 55

7OPERATIONAL STATE COMMANDS

boot-flashSelects the flash partition from which to boot the LMP. This setting takes effect the next time the LMP is reset.


Mode: config

Syntax: boot-flash [ primary | secondary ]

Options:primary Loads the software from the primary flash partition on the next reboot.secondary Loads the software from the secondary flash partition on the next reboot.

Default: Primary flash partition

See also: show boot-flash

7 powerdown

56 Blade Management: Operational State Commands

powerdownThis commands powers down the module.


Mode: blade-mgmt

Syntax: powerdownOptions: none

Default:

See also:

no powerdownThis command powers up the module.

Syntax: no powerdown

7reset cold


reset coldPerforms a cold reset of the module. A cold reset is performed by the IPMC on the module and it causes all memory to be cleared. If enabled, the appropriate SNMP trap will be generated as part of the reset operation.


Mode: blade-mgmt

Syntax: reset coldOptions: none

Default:

See also: snmp-trap coldstart

7 reset warm


reset warmPerforms a warm reset of the module. A warm reset is performed by the LMP on the module and only a portion of the memory is cleared. If enabled, the appropriate SNMP trap will be generated as part of the reset operation.


Mode: blade-mgmt

Syntax: reset warmOptions: none

Default:

See also:

7show boot-flash


show boot-flashShows which boot-flash will be used on the next reboot.


Mode: blade-mgmt

Syntax: show boot-flashOptions: none

Default:

See also: boot-flash

7 show service


show serviceLists the administrative states of all the Linux services (enabled or disabled).


Mode: blade-mgmt

Syntax: show serviceOptions:

Example:Services Status Service Enabled Status ------------------- ----------- dhcpd enabled mmsdmgr disabled ntpd disabled snmpd enabled sshd disabled syslog disabled tftp enabled watchdog enabled

Default:

See also:

Blade Management: Network Timing Subsystem Commands 61

8NETWORK TIMING SUBSYSTEM COMMANDS

network-clock-selectConfigures and assigns a unique priority for each clock input. If clocks are set to the same priority, the last clock configured retains that priority, while the others are set to zero (ignored).


Mode: config

Syntax: ATCA-1200, ATCA-4300/4310, ATCA-7220, ATCA-9100network-clock-select { clk2a | clk2b }ATCA-2210network-clock-select { xlink1 | clk3a | clk3b | extclk1 | extclk2 | extclk3 | extclk4 }

Options: All modules

Assigns a priority to the specified clock input. The available priority choices for the different module types are listed below:

ATCA-1200, ATCA-4300/4310, ATCA-7220, ATCA-9100clk2a Sets the priority for the a half of the clk2 bused signal, which is received

from an ATCA-2210 installed in the hub slot.

clk2b Sets the priority for the b half of the clk2 bused signal.

Module PriorityATCA-1200, ATCA-4300/4310, ATCA-7220, ATCA-9100

0 (ignore) and 2-3.

ATCA-2210 0 (ignore) and 2-7. Priority 1 (the highest priority) is reserved for the update channel clock (xlink1) from the ATCA-2210 in the network timing subsystem (NTS) master role and used as the input by the slave ATCA-2210.

8 network-clock-select

62 Blade Management: Network Timing Subsystem Commands

ATCA-2210xlink1 Sets the priority for the first update channel clock received from the

partner ATCA-2210. Update channel signals between partner ATCA-2210s maintain synchronization by providing phase alignment and allows redundancy by providing quick detection of peer loss.

xlink2 Sets the priority for the second update channel clock received from the partner ATCA-2210.

clk3a Sets the priority for the a half of the clk3 bus, which is a backplane bus that is part of the PICMG-defined synchronization clock interface.

clk3b Sets the priority for the b half of the clk3 bus.

extclk1 Sets the priority for the first input from the optional rear transition module (RTM).

extclk2 Sets the priority for the second input from the optional RTM.

extclk3 Sets the priority for the third input from the optional RTM.

extclk4 Sets the priority for the fourth input from the optional RTM.

Defaults:ATCA-1200, ATCA-4300/4310, ATCA-7220, ATCA-9100

ATCA-2210

See also: network-clock-select modeshow network-clocks source priority

Source Priorityclk2a 2clk2b 3

Source Priorityxlink1 0 (ignore) when the ATCA-2210 is acting as the master ATCA-2210

1 when the ATCA-2210 is acting as the redundant (slave) ATCA-2210 clk3a 2clk3b 3extclk1 4extclk2 5extclk3 6extclk4 7

8network-clock-select clock-source-mode


network-clock-select clock-source-modeEnables the CLK1 only mode, which implements the optional sync input CLK1 as the frequency input. In this mode, the default input frequency of CLK2 is not used.

Supported on: ATCA-1200, ATCA-4300/4310, ATCA-7220, ATCA-9100

Mode: config

Syntax: network-clock-select clock-source-mode [ clk2-normal | clk1-only ]

Options:clk2-normal Resets the frequency input to the normal CLK2 input.

clk1-only Sets the frequency input to the optional sync CLK1 input.

Default: clk2-normal

See also: show network-clocks configuration

no network-clock-select clock-source-modeResets the frequency input to the normal CLK2 input.

Syntax: no network-clock-source-mode

8 network-clock-select framer


network-clock-select framerSets the expected framing format of the signal received from the RTM framer clock. The format also affects the CLK3 input frequency and the sysclk1 output frequency.


Mode: config

Syntax: network-clock-select framer [ e1 | t1 | j1 ]Options:e1 Sets the framing format to e1 mode. In this mode, 2.048 MHz is the

expected RTM and clk3 input frequency and sysclk1 output frequency.

t1 Sets the framing format to t1 mode. In this mode, 1.544 MHz is the expected frequency.

j1 Sets the framing format to j1 mode. In this mode, 1.544 MHz is the expected frequency.

Default: e1


no network-clock-select framerResets the framing format expected from the framer clock to the default.

Syntax: no network-clock-select framer

8network-clock-select frequency


network-clock-select frequencyAssigns a source frequency to the specified CLK3 input clock.


Mode: config

Syntax: network-clock-select frequency { clk3a | clk3b } [ 8-kHz | 1544-kHz | 2048-kHz | 19.44-MHz ]

Options:clk3a Specifies the clk3a input clock as the clock to configure. This clock is the

a half of the clk3 bus, which is a backplane bus and is part of the synchronization clock interface.

clk3b Specifies the clk3b input clock as the clock to configure. This clock is the b half of the clk3 bus.

8-kHz Sets the source frequency to 8-kHz on the specified input clock.

1544-kHz Sets the source frequency to 1544-kHz on the specified input clock. This option is available only when the framing format is set to t1 or j1.

2048-kHz Sets the source frequency to 2048-kHz on the specified input clock. This option is available only when the framing format is set to e1.

19.44-MHz Sets the source frequency to19.44-MHz on the specified input clock.

Default: 19.44-MHz

See also: network-clock-select framershow network-clocks source status

no network-clock-select frequencySets the selected input clock back to the default frequency.

Syntax: no network-clock-select frequency { clk3a | clk3b }

8 network-clock-select manage-bused-resource


network-clock-select manage-bused-resourceEnables E-Key management of the clock bus resources (CLK1 and CLK2). In this state, the Shelf Manager on the ATCA-2210 tracks token ownership and responds to CLI or NTS API requests to drive a particular clock bus by granting or denying a token. If neither the ATCA-2210 acting as the NTS master nor its redundant partner own a token, they cannot enable output on a bus.

When an ATCA-2210 acting as the NTS master fails over to the partner ATCA-2210, the Shelf Manager is notified that a new token owner is driving the bus, and the configuration value is automatically changed.


Mode: config

Syntax: network-clock-select manage-bused-resourceOptions: none

Default: Disabled

See also: network-clock-select request-bused-resourceshow network-clocks bused-resource

no network-clock-select manage-bused-resourceDisables E-Key management of the clock bus resources. With management disabled, the ATCA-2210 can drive output to a clock bus without requesting a token.

Syntax: no network-clock-select manage-bused-resource

8network-clock-select mode


network-clock-select modeSelects the reference clock source.


Mode: config

Syntax: ATCA-1200, ATCA-4300/4310, ATCA-7220, ATCA-9100network-clock-select mode [ automatic | force { clk2a | clk2b } ]

ATCA-2210network-clock-select mode [ automatic | force { clk3a | clk3b | extclk1 | extclk2 | extclk3 | extclk4 } ]

Options:

All modulesautomatic Selects the highest priority, validated clock and designates it as the

reference clock source.

force Designates the selected clock as the reference clock source. If a clock source specified in the force mode is not valid, the module will go into digital holdover mode.

ATCA-1200, ATCA-4300/4310, ATCA-7220, ATCA-9100clk3a Specifies clk3a as the reference clock source.

clk3b Specifies clk3b as the reference clock source.

ATCA-2210clk2a Specifies clk2a as the reference clock source.

clk2b Specifies clk2b as the reference clock source.

extclk1 Specifies extclk1 as the reference clock source.




Default: automatic

See also: show network-clocks brief

no network-clock-select modeSets the reference clock source to automatic, which selects the highest priority, validated clock.

Syntax: no network-clock-select mode

8 network-clock-select output


network-clock-select outputSpecifies which half of the selected clock signals are driven by the module. On the ATCA-2210, you can specify the halves for the clk1 and clk2 signals. On the ATCA-1200 and the ATCA-4300/ATCA-4310 modules, you can specify the halves for the clk3 signal.

Note: When the management of bused resources is enabled on the ATCA-2210 (see network-clock-select manage-bused-resource), the output selection is limited to buses whose tokens are owned by the ATCA-2210 or its partner. The management of bused resources does not affect the outputs to the RTM or the update channel between the redundant ATCA-2210s, since these outputs are always enabled.

Supported on: ATCA-1200, ATCA-2210, ATCA-4300/4310

Mode: config

Syntax: ATCA-1200, ATCA-4300/4310network-clock-select output clk3 [ a | b ]

ATCA-2210network-clock-select output { clk1 | clk2 } [ a | b ]

Options:ATCA-1200, ATCA-2210, ATCA-4300/4310

a Configures the ATCA to drive signals from the a half of the specified clock bus.

b Configures the ATCA-2210 to drive signals from the b half of the specified clock bus.

ATCA-2210clk1 Selects the clk1 bus as the clock signal driven by the module.

clk2 Selects the clk1 bus as the clock signal driven by the module.

Example:ATCA-1200, ATCA-4300/4310network-clock-select output clk3aATCA-2210To configure partner ATCA-2210s so they provide redundancy, use this setup:

On the ATCA-2210 acting as the master: network-clock-select output clk1anetwork-clock-select output clk2a

8network-clock-select output


On the ATCA-2210 acting as the slave: network-clock-select output clk1bnetwork-clock-select output clk2b

Default: No output selected

See also: network-clock-select manage-bused-resource

no network-clock-select outputRemoves the specified half of the selected clock bus as the signal driven by the module.

Syntax: ATCA-1200, ATCA-4300/4310no network-clock-select output clk3 [ a | b ]

ATCA-2210no network-clock-select output { clk1 | clk2 } [ a | b ]

8 network-clock-select output-module


network-clock-select output-moduleConfigures which AMC bay drives the CLK3 output to the backplane.

Supported on: ATCA-1200, ATCA-4300/4310

Mode: config

Syntax: network-clock-select output-module Options: Configures the source clock in the selected bay. Bays are numbered

1 to 4 on the ATCA-1200 and 1 to 2 on the ATCA-4300/4310.

Default: n/a

See also: network-clock-select output

no network-clock-select output-module Resets the default AMC bay as the bay to drive the CLK3 output to the backplane.

Syntax: no network-clock-select output-module

8network-clock-select phase-buildout


network-clock-select phase-buildoutEnables phase-buildout, which implements a phase offset (the difference between the input and the output phase) on a module. This lets the module maintain a hitless failover (i.e., seamless transition) to a secondary clock source upon failure of the primary clock source.


Mode: config

Syntax: network-clock-select phase-buildoutOptions: none

Default: n/a

See also:

no network-clock-select phase-buildout Disables phase-buildout on the module.

Syntax: no network-clock-select output-module

8 network-clock-select revertive


network-clock-select revertiveEnables revertive mode, which does the following.


Mode: config

Syntax: network-clock-select revertiveOptions: none

Default: Does not revert, stays with the current source.


no network-clock-select revertiveDisables revertive mode, which does the following.

Syntax: network-clock-select revertive

Module Revertive mode enabledATCA-1200, ATCA-4300/4310, ATCA-7220, ATCA-9100

Configures NTS to revert to the primary clock if there is a temporary disruption of its signal.

ATCA-2210 Sets the reference clock to revert to the original source if the signal is lost. When this occurs, the ATCA fails over to another source and the signal is restored. For example, if a newly validated (or revalidated) source has a higher priority than the current reference source, the ATCA-2210 transitions to the higher priority source.

Module Revertive mode disabledATCA-1200, ATCA-4300/4310, ATCA-7220, ATCA-9100

Configures NTS to stay with the current clock source, rather than revert to the primary clock if there is a temporary disruption of the signal.

ATCA-2210 Sets the reference clock to stay with current clock source, even when the original source is restored after a failover or when a newly validated (or revalidated) source has a higher priority than the current reference source.

8network-clock-select request-bused-resource


network-clock-select request-bused-resourceRequests permission to drive a clock bus pair. The Shelf Manager on the ATCA-2210 provides a token to the entity authorized to drive the clock.

A result message indicates whether the token was granted. If E-Key management of clock bus resources is enabled, token ownership is enforced when allowing output to be enabled, and ownership is reflected in the running configuration, allowing it to be saved permanently to the startup configuration.

Even though one ATCA-2210 requests permission to drive both halves of the bus, either ATCA-2210 can drive the halves. Output can be enabled if the ATCA-2210 or its partner ATCA-2210 owns the token. See the example in network-clock-select output.


Mode: config

Syntax: network-clock-select request-bused-resource {clk1 | clk2 | clk3}

Options:clk1 Requests access to clk1.

clk2 Requests access to clk2.

clk3 Requests access to clk3.

Default: n/a

See also: network-clock-select manage-bused-resourceshow network-clocks bused-resource

no network-clock-select request-bused-resourceReleases the token previously granted to the ATCA-2210 and allows it to drive a clock bus pair. This frees the bus resource for use by another entity.

Syntax: no network-clock-select request-bused-resource { clk1 | clk2 | clk3 }

8 network-clock-select role


network-clock-select roleConfigures an ATCA-2210 to act as the master NTS, the slave NTS, or to be in an autonomous NTS relationship with the other ATCA-2210 installed in the shelf.


Mode: config

Syntax: network-clock-select role [ master | slave | autonomous ]

Options:master Sets an ATCA-2210 to act as the master NTS, which provides the system

clocks.

slave Sets an ATCA-2210 to act as the slave NTS, which stays synchronized with the master and outputs the same system clocks. If configured as a slave, the module provides a seamless failover source.

autonomous Sets an ATCA-2210 to an autonomous role. The two ATCA-2210s do not communicate their timing or configuration information with each other and may be under manual control of a management application such as a system manager.

Default: The ATCA-2210 in lower-numbered slot is the master and the other ATCA-2210 is the slave.

See also: show network-clocks brief

no network-clock-select roleSets the ATCA-2210s to their default roles, making the ATCA-2210 in the lower-numbered slot the master and the other the slave.

Syntax: no network-clock-select role

8network-clock-select sabit


network-clock-select sabitSpecifies which Sa Bit the framer uses to receive and transmit Synchronization Status Messages (SSMs). The Sa Bits (sa4 to sa8) are the additional spare bits in the frame that do not contain the frame alignment signal (Table 5A/G.704). Any of these spare bits can be used in a synchronization interface to convey SSMs.

This command is available when the framer is in E1 mode and an RTM is installed.


Mode: blade-mgmt

Syntax: network-clock-select sabit [ sa4 | sa5 | sa6 | sa7 | sa8 ]

Options:sa4 Sets the framer to receive and transmit the SSMs on Sa Bit 4.

sa5 Sets the framer to receive and transmit the SSM on Sa Bit 5.




Default: sa4

See also: network-clock-select

no network-clock-select sabitResets the configured Sa Bit value to the default of sa4 for the SSM.

Syntax: no network-clock-select sabit

8 network-clock-select source-module


network-clock-select source-module Configures the reference clock source and clock speed for the specified bay or DSP farm.


Mode: config

Syntax: network-clock-select source-module [ tclk-a | tclk-c ] [ 8-kHz | 1544-kHz | 2048-kHz | 19.44-MHz | none ]

Options: Configures the reference source clock for the bay, DSP farm, or data

processing block (DPB) number specified.

none Disables the source clock to the bay, DSP farm, or DPB.

8-kHz Sets the speed of the specified reference source clock to 8-kHz.

1544-kHz Sets the speed of the tlck-a clock to 1544-kHz.

2048-kHz Sets the speed of the tlck-a clock to 2048-kHz.

19.44-MHz Sets the speed of the tlck-a clock to 19.44-MHz.

Default: n/a

See also: network-clock-selectshow network-clocks

no network-clock-select source-moduleDisables the selected reference clock source for the bay or the DSP farm number specified.

Syntax: no network-clock-select source-module [ tclk-a | tclk-c ]

8network-clock-select ssm


network-clock-select ssm Sets the output stratum level of the Synchronization Status Message (SSM) for all framer output ports. The configured output stratum level should match the SSM inputs being received by the input ports. If the framer input ports are receiving different SSM inputs, match the SSM input on the input port to which the PLL is locked and using as its current SSM source.

The NTS framing format (E1, T1, or J1) determines which output stratum levels are available for selection. See network-clock-select framer on page 64 for more information on the configuring the framing format. The differences between the framing formats for this command are described in the Syntax and the Options sections below.

Important: This command is only available when an RTM is installed.


Mode: config

Syntax: E1 modenetwork-clock-select ssm [ prs | stu | g812t | g812l | sets | dus ]

T1 and J1 modesnetwork-clock-select ssm [ prs | stu | st2 | st3 | smc | st4 | dus | none ]

Options:All modes

prs Sets the SSM output to the primary reference source.

stu Sets the SSM output to synchronized traceability unknown

dus Configures the output port so it does not use the reference source.

E1 modeg812t Sets the transit node clock so it is traceable to SSU type A, G.812.

g812l Sets the local node clock so it is traceable to SSU type B, G.812.

sets Configures the Synchronous Equipment Timing Source (SETS).

T1 and J1 modesst2 Sets the SSM output to the Stratum 2 reference source.

st3 Sets the SSM output to the Stratum 2 reference source.

smc Sets the SSM output to SONET minimum clock (self-timing) source

st4 Sets the SSM output to the Stratum 4 reference source (free run).

none none

Default: n/a

8 network-clock-select ssm



no network-clock-select source-moduleRemoves the assigned SSM from the framer. The framer then transmits without an SSM.

Syntax: no network-clock-select ssm

8show network-clocks


show network-clocksShows the frequency and current status of each clock that a module may output.


Mode: blade-mgmt

Syntax: show network-clocks Options: This command can be issued by itself or appended with optional

parameters that describe specific aspects of the network clocks. The varying versions of this command are described separately in this manual. See the See also: section for a list of the related commands.

Output:Output Lists the clocks that a module may output.

Frequency Shows the configured frequency for the output clock.

Enabled Shows whether a clock is enabled or not as an output clock for the module. If a clock is enabled, the status is listed as true.

EKey Status Specifies whether managed bused resources are enabled for the clocks.

Examples:

ATCA-1200show network-clocksNetwork Clock Output Status Output Frequency Enabled EKey Status --------- ----------- --------- ------------ clk3a N/A false enabled clk3b N/A true enabled tclka-1 19.44 MHz false enabled tclkc-1 8 kHz false enabled tclka-2 8 kHz true enabled tclkc-2 8 kHz false enabled tclka-3 8 kHz false enabled tclkc-3 8 kHz true enabled tclka-4 19.44 MHz true enabled tclkc-4 8 kHz false enabled sysclk1 19.44 MHz true not required

8 show network-clocks


ATCA-2210show network-clocksNetwork Clock Output Status Output Frequency Enabled EKey Status --------- ----------- --------- ------------ clk1a 8 kHz false unknown clk1b 8 kHz false unknown clk2a 19.44 MHz false unknown clk2b 19.44 MHz false unknown sysclk1 2048 kHz true not required sysclk2 8 kHz true not required sysclk3 19.44 MHz true not required xlink1 6.48 MHz true enabled xlink2 2 kHz true enabled

Default: n/a

See also: network-clock-selectnetwork-clock-select outputnetwork-clock-select manage-bused-resourceshow network-clocks briefshow network-clocks configurationshow network-clocks priorityshow network-clocks source alarms

8show network-clocks brief


show network-clocks brief Displays the runtime status of the NTS subsystem.


Mode: blade-mgmt

Syntax: show network-clocks briefOptions: none

Output:All modules

Mode Indicates what NTS is using to select an input clock. The possible values are:

Selected The source clock currently being used as a network timing reference. For information on the network clocks see network-clock-select source-module on page 76

Operating Mode The mode of the internal digital phase-lock loop (PLL) on the reference clock. The possible modes are:

Selection method Description

automatic NTS is using the defined priorities automatically selecting the highest priority, valid input clock.

force NTS is using an input clock selected by a user. The selected input clock is also shown. See network-clock-select mode on page 67 for information on the possible modes.

PLL mode Descriptionlocked The PLL is locked to a valid source.holdover The PLL is operating based on stored phase information from a

previous source to maintain clock stability until it locks to another source.

freerun The PLL phase is independent of any source.locked The PLL is locked to a valid source.pre-locked After being in free-run mode, the module has selected a reference

source and the PLL is attempting to lock to it. If the source is of good quality, the PLL enters locked state within 100 seconds. Otherwise, it reverts to free-run mode and the module selects another reference source.

pre-locked2 After being in holdover mode, the module has selected a reference source and the PLL is attempting to lock to it. The PLL also enters this mode if the module is in revertive mode and is transitioning to a higher priority source that has been restored.

8 show network-clocks brief


Operating State Shows the current alarms for the PLL. The possible values are:

RTM present Shows whether a rear transition module has registered its presence with the NTS API.

ATCA-2210Role The current NTS role of the ATCA-2210: master, slave, or autonomous.

The displayed role may differ from what was actually configured for NTS. This may occur in situations where NTS was configured as a master or a slave and an automatic failover took place, causing the NTS role to change. See network-clock-select role on page 74 for more information.

Partner Visible Shows whether the master or the slave partner of this ATCA-2210 is visible.

Examples:ATCA-1200show network-clocks brief Network Clock Information Mode : automatic Selected : clk3b Operating Mode : holdover Operating State : sync-alarm

ATCA-2210show network-clocks brief Network Clock Information Mode : automatic Role : master Selected : clk2a Operating Mode : holdover Operating State : RTM Present : true Partner Visible : false

phase-lost The PLL has lost phase lock and is attempting to lock to the input reference clock, if it exists. If the anomaly causing the loss of lock is serious, the module disqualifies the reference clock. The clock is automatically disqualified and generates an alarm if the PLL remains in phase-lost mode for more than 100 seconds. When the reference clock is disqualified, the PLL proceeds to pre-locked2 mode if a valid reference clock is available. Otherwise, it goes into holdover mode.

Possible alarms Descriptiondpll-soft-alarm The PLL is tracking its input reference clock beyond the 11.43

ppm drift limit that generates a soft alarm.sync-alarm The xlink2 input has a problem.

PLL mode Description

8show network-clocks brief


Default: n/a


8 show network-clocks bused-resource


show network-clocks bused-resourceShows the E-Key token ownership of the clock buses and summarizes the token-specific communications between this ATCA-2210 and the Shelf Manager.


Mode: blade-mgmt

Syntax: show network-clocks bused-resourceOptions: none

Output:Bused Resource Shows which backplane clock bus is specified as the bused resource.

Token Owner Shows the current entity authorized by the Shelf Manager to drive signals on the clock bus. The possible values are:

Board2Shelf Shows the last token-specific communication this ATCA-2210 sent to the Shelf Manager.

Shelf Reply Shows the last token-specific reply received from the Shelf Manager. The reply is displays in standard IPMI return code.

Shelf2Board Shows the last communication received from the Shelf Manager.

Board Reply Shows the last token-specific communication sent to the Shelf Manager.

Default: n/a

See also: network-clock-select manage-bused-resourceshow network-clocks

Entity DescriptionLocal This ATCA-2210 holds the E-Key token.Partner The other ATCA-2210 in this master/slave pair holds the token.Unknown An unknown entity or no one holds the token.

8show network-clocks configuration


show network-clocks configuration Displays the configuration for the module.


Mode: blade-mgmt

Syntax: show network-clocks configurationOptions: none

Output:All modules

Mode Indicates what NTS is using to select an input clock. The possible values are:

Revertive Indicates whether revertive mode is enabled. See network-clock-select revertive on page 72 for information on this mode.

ATCA-1200, ATCA-4300/4310, ATCA-7220, ATCA-9100Clock Source Mode

Shows which clock source mode is enabled: clk1 or clk2. See network-clock-select clock-source-mode on page 63 for information on configuring the clock source modes.

Role ATCA-2210The current NTS role of the ATCA-2210: master, slave, or autonomous. The displayed role may differ from what was actually configured for NTS. This may occur in situations where NTS was configured as a master or a slave and an automatic failover took place, causing the NTS role to change. See network-clock-select role on page 74 for more information.

Phase buildout Shows the phase-buildout status. When phase-buildout is enabled, on is displayed. When disabled, off is displayed. See network-clock-select phase-buildout on page 71 for more information on phase-buildout.

Output Shows which clock is being used to drive clock timing as an output to the backplane.

Selection method Description

automatic NTS is using the defined priorities automatically selecting the highest priority, valid input clock.

force NTS is using an input clock selected by a user. The selected input clock is also shown. See network-clock-select mode on page 67 for information on the possible modes.

8 show network-clocks configuration


Framer Shows the expected framing format of the signal received from the RTM framer clock. The format also affects the CLK3 input frequency and the sysclk1 output frequency. See network-clock-select framer on page 64 for information on the framing formats.

Sa Bit Shows which Sa Bit the framer is using to receive and tra

03267-02 ATCA Command Line Interface Reference

Documents

Transcript of 03267-02 ATCA Command Line Interface Reference