| Sun Netra CT 900 Server Installation Guide |    
|
| C H A P T E R 5 |
|
Installing and Using the Software |
This chapter includes the following topics:
You can access the Sun Netra CT 900 server either remotely, by logging in to the Sun Netra CT 900 server as superuser through another server on the network, or directly, by connecting a terminal console directly to your Sun Netra CT 900 server. A terminal console can be an ASCII terminal, workstation, or PC laptop.
You can administer your Sun Netra CT 900 server or specific boards directly through the serial port on the following boards:
Refer to Chapter 4 for more information on the serial port for each of these boards.
1. Get the appropriate cables and adapters and make the necessary connections.
2. Access the Set Up Menu of the ASCII terminal and bring up the Serial Communications section.
3. Set up the serial port communications parameters.
The default settings should match the values reported on the host serial port.
Following are the default settings for the serial port on the shelf alarm panel:
Following are the default settings for the serial port on the switch:
Refer to the documentation that came with your node board for the default settings for the serial port on that board.
Any node boards installed in the Sun Netra CT 900 server require board-specific operating systems. Some versions of the Sun ATCA node boards might have a PCI Mezzanine card (PMC) disk pre-installed on the node board, and a version of the Solaris OS pre-installed on that PMC disk. Refer to the documentation that you received with your node board for more information. In addition, refer to the Sun Netra CT 900 Server Product Notes to determine if any patches must be installed for your operating system.
If your Sun ATCA node board has the Solaris OS pre-installed on the PMC disk, enter the following command to boot the node board from that operating system:
You might also be able to install a different version of the operating system onto the node board, if necessary, or you might boot the node board over the net or through the Compact Flash card on the node board. Refer to your node board documentation for more information.
The system management software is actually firmware that is pre-installed on the shelf management cards. No additional software installation is necessary for those cards. You access the system management software through the shelf alarm panel. Refer to Connecting the Cables to the Shelf Alarm Panel for information on connecting to the shelf alarm panel.
Following are some basic software commands for the system management software; for more detailed procedures and information, refer to the Sun Netra CT 900 Server Administration and Reference Manual.
The default TCP/IP for the primary shelf management card is 192.168.0.2.
To log in to the default user account for the first time, root is the login and there is no password:
To change the IP address of the primary shelf management card, enter:
To list the boards in the Sun Netra CT 900 server, enter:
To list the Intelligent Platform Management controllers (IPMCs) in the Sun Netra CT 900 server, enter:
To change the fan speed for a fan tray in the Sun Netra CT 900 server, enter:
Note that the value for the speed can go from 2 to 15. For example, to change the speed to 5 on a fan tray with an Intelligent Platform Management Interface (IPMI) address of 0x20 and a FRU ID of 3, enter:
To display the FRU information in a board, enter:
For example, to list the FRU information in a board with an IPMI address of 0x82 and a FRU ID of 0, enter:
To display the shelf manager firmware version, enter:
To display the contents of the System Event Log (SEL), enter:
To clear the System Event Log, enter:
To list the sensors on a board, enter:
For example, to list the sensors on a board with an IPMI address of 0x82, enter:
To get the data from a sensor on a board, enter:
For example, to get the data from sensor 4 on a board with an IPMI address of 0x82, enter:
The switch software is firmware that is pre-installed on the switches, so no additional software installation is necessary for those boards. You access the switch software through the switch. Refer to Connecting Cables to Switches for information on connecting to the switch.
Following are some basic software commands and information for the switch software; for more detailed procedures and information, refer to the Sun Netra CP3140 Switch Software Reference Manual (819-3774) or the Sun Netra CP3240 Switch Software Reference Manual (820-3253).
The switch software is built upon three main components:
The first two software components are covered in detail in this chapter. FASTPATH is touched upon, but refer to the Sun Netra CP3140 Switch Software Reference Manual (819-3774) or the Sun Netra CP3240 Switch Software Reference Manual (820-3253) for more details and a complete command list for each switch.
The uBoot software is the boot loader for the switch. Much like a BIOS, it brings the system to a usable state for the operating system to boot. It also performs a power-on self-test (POST) of the CPU subsystem. It can be used as a recovery console if the firmware image is corrupt or a firmware update fails. Several important environment variables are stored in uBoot, only some of which should ever be changed, namely noekey and baudrate.
To get to a uBoot console, you must prevent the switch from booting into Linux. Shown here is the start of the switch boot sequence.
You must press any key before Booting ... appears. There is only a one-second delay to press this key. Multiple key presses do not hurt.
You are presented with the uBoot prompt:
TABLE 5-1 shows the commands that you can execute at this point.
|
When followed by an environment variable, changes that environment variable. |
|
| Note - You must save if you want changes to persist through a reset. |
Refer to E-Keying for a description of E-Keying and how it is supported on the switch.
To disable E-Keying, the noekey environment variable is used. Simply list the ports to be disabled separated only by commas, or use the word all to disable E-Keying completely. For example:
To re-enable E-Keying, enter the following command to clear the variable.
After changing the environment variables, you must always save if you would like your change to persist though a reset.
The serial baud rate can be changed from within FASTPATH, on the boot menu, or in uBoot. Only changes made in uBoot will persist through a reset. To change the baud rate in uBoot, the baudrate variable must be changed. Only standard baud rates are accepted.
To change the baud rate in uBoot, enter:
After changing the environment variables, you must always save if you would like your change to persist though a reset.
The switch uses Linux as an operating system. The Monta Vista 3.1 Pro 2.4.20 kernel is used. This proven environment provides stability to the switch. There are no settings to change, and the OS is completely transparent to the end user.
E-Keying is implemented as a Linux driver on the switch. The CPUs for both Base and Fabric interfaces have a direct connection to the IPMI controller that is used to communicate E-Keying messages. The CPU is interrupted when an E-Keying event occurs. The driver handles these interrupts and disables ports based on the information it receives. It disables them by doing the equivalent of a shutdown command at the CLI. This disables the port at the PHY level. E-Keying can be ignored by creating a uBoot environment variable (see E-Keying Control in uBoot for more information).
The ATCA LEDs can be turned on from several sources, one of which is a Linux driver. Both the Base and Fabric interfaces drive these LEDs. The red OOS LED is driven until FASTPATH has loaded, at which point the green Healthy LED is driven. The OOS LED signals are ORed so that if one or more are active, then the LED is on. The Healthy LED signals are ANDed. The Base and Fabric interfaces must be booted into FASTPATH, in addition to several hardware conditions that must be met for this LED to be on.
The Linux ATCA LED driver provides control over the user-defined amber LED as well. The signals for this LED are ORed. This LED is currently driven under no circumstances.
Following is an example of the switch boot sequence.
The switch should take approximately 20 seconds to boot to a console and be fully functional.
There is a utility menu that can be used before FASTPATH boots. As seen in the preceding section, during boot, a two-option menu is displayed for five seconds. This menu enables you to access to the utility menu if you press 2 and Return.
The following screen is displayed once you enter the boot utility menu.
Most of the options are self-explanatory based on their names, but some deserve further discussion.
FASTPATH can be updated from within FASTPATH itself, but you can also update it from this menu. The update image must be on a TFTP server. Supply the IP address of the TFTP server, the desired IP address of the board being updated, the gateway (if needed) and the file name. To obtain an IP address for the switch during this update, enter dhcp as the IP address. This begins the update and provides status information as it is updating.
The Erase Current Configuration option is the same as clear config from within FASTPATH. This option can be used if the switch is in an unknown state and you want to restore the default settings.
|
Caution - You should never use this command. |
The Erase Permanent Storage command completely erases FASTPATH, any log files, and any configurations. It does not erase uBoot or Linux. Updates can safely be installed without running this option, and configurations and log files are preserved.
The switch supports three boot methods:
The default option is booting from the Compact Flash card. See Network Booting for more information on network booting.
| Note - This environment is provided as is, with no support. |
The BCM Debug Shell option boots the Broadcom diag shell, currently SDK version 5.2.1. Several commands provided in this shell are not supported on the switch and do not work. This shell is provided mainly for debug, testing, and diagnostics purposes. This shell has many low-level tests and low-level register access. It can be used to check the integrity of particular boards. Help is provided in the shell with ?? and commands followed by a single question mark. Some commands of interest are SystemSnake, dsanity, TestList, and TestRun.
Note that ports are not numbered in the same order here as in FASTPATH. In the BCM diag shell, the ports are the actual port numbers of the chips. In FASTPATH, the port numbers have been abstracted to represent the ATCA channel numbers. TABLE 5-2 maps the BCM diag shell numbers to the FASTPATH numbers.
Booting from the network can be a very useful feature. It can make firmware updates as simple and quick as rebooting the boards, and it can be used to test new firmware without losing the old firmware. As described in Boot Method, network boot can be enabled or disabled from the boot utility menu. To perform a network boot, you must have a TFTP server with the firmware image and you must use the out-of-band management port.
The network boot supports DHCP to obtain an IP address. Simply use dhcp as the IP address when configuring network boot. The network boot uses the out-of-band management port to download the firmware image, and then frees it to be used as normal once FASTPATH boots. This enables an NMS to control the firmware revision on the switch as well as manage and control the switch functions.
The switch uses FASTPATH software. FASTPATH is a software package providing the robust management needed to control a modern switch-router. FASTPATH is not covered in detail in this manual, but is covered in the Sun Netra CP3140 Switch Software Reference Manual (819-3774) or the Sun Netra CP3240 Switch Software Reference Manual (820-3253). This section serves as a quick primer on using FASTPATH on the switch.
FASTPATH supports multiple users with different security levels. By default, there is one user (admin), with no password. In the command-line interface (CLI), Privilege mode is password-protected separately from the Default mode, but also has a default of no password.
A CLI is provided on the serial console, Telnet console, and SSH console. The serial console is always enabled. The Telnet console is enabled by default. SSH is disabled by default.
The following screen shows how to switch from the Default mode to the Privilege mode. Note that by default, there is no password for the Default and Privilege modes.
The following screen is displayed; enter enable to go from Default mode to Privilege mode:
The prompts always show the current mode. TABLE 5-3 gives a few examples.
Simple Network Management Protocol (SNMP) is enabled by default. The default community string is “public”. Write access is disabled by default.
The switch supports SSH for a secure CLI console as well as SSL/TLS. However, the switch cannot generate its own keys. Keys must be generated on an external system and uploaded to the switch through TFTP. Once the keys are on the switch, SSH must be enabled before it can be used.
The switch can be controlled by a CLI or through SNMP. All management interfaces, other than serial, can be enabled or disabled, provided over both the out-of-band management port and any in-band ports, and can be limited to certain in-band ports.
The switch provides an industry-standard CLI. The CLI is provided over the serial port, Telnet, and SSH. This section describes some very basic commands. Refer to the Sun Netra CP3140 Switch Software Reference Manual (819-3774) or the Sun Netra CP3240 Switch Software Reference Manual (820-3253) for a detailed list of commands.
The CLI is mode-based. It works similarly to a console in Linux. Commands are grouped under modes, and those commands work only when the user is in the current mode. There are very few global commands. To return to one mode higher than the current mode, type exit. For example, to shut down port 17, you must switch to Enable mode, then Configure mode, then Interface 17 mode, and then issue the shutdown command. Type exit to return to Configure mode.
Many commands have a “no” form. The no form is used to disable the command. To re-enable port 17, once you are in the Interface 17 mode, issue the no shutdown command.
TABLE 5-4 gives a list of basic FASTPATH CLI commands.
The switch comes configured with a default configuration. This configuration boots the board to Layer 2 switching. This configuration is very basic and should be updated for your environment. The default settings are basically that every port is in VLAN 1, every port is configured in switching mode, management interfaces are enabled, and everything else is disabled.
The settings of the switch can be checked with the show running-config command. This command shows how the current configuration is different from the default configuration. This command can be very useful because the output is in script format. This output can be backed up or copied to another switch.
The ports are ordered the same way as the ATCA channels. In the Sun Netra CT 900 serverfrom Oracle, the logical slots and physical slots do not match. The switch supports an abstraction layer that allows the port order to be changed. This enables vendors to match logical slots and physical slots independent of routing.
TABLE 5-5 shows the port ordering.
The switch has two powerful CPU complexes to control and manage all the operations of the board. These complexes feature plenty of head room for custom software development and future upgrades.
FASTPATH and Linux use only approximately 56 Mbytes of the 128 Mbytes of memory. This memory is allocated at boot time and is independent of switch load. CPU usage is on the order of 1-15 percent, and is on the low end of that range most of the time. It is mostly management features that require the CPU cycles. All program files are stored compressed on the Compact Flash card and are decompressed into memory on boot. Only 12 Mbytes of the available 32 Mbytes are needed to store uBoot, Linux, and the current version of FASTPATH.
| Sun Netra CT 900 Server Installation Guide | 819-1175-14 |
|
Copyright © 2010, Oracle and/or its affiliates. All rights reserved.