|
|
This chapter describes how to set up general switch features that apply to multiple switch interfaces. This chapter starts with a configuration quickstart procedure, which introduces the configuration tasks. The following sections provided detailed information on how to complete the configuration tasks.
The quickstart procedure in this section provides a summary of the tasks required to configure the
SES. This procedure is provided as an overview and as a quick reference for those who have already configured the SES.
| Command | Purpose | |
|---|---|---|
Step 1 | username password | Start a configuration session. (See "Establishing and Ending a CLI Management Session, page 7-2.) |
Step 2 | adduser <username> <accessLevel> cnfpasswd <username> deluser <username> | Configure administrator access. (See Configuring Administrator Access, page 7-10.) |
Step 3 | cnfname <node name> | Configure the switch name. (See Setting and Viewing the Switch Name, page 7-14.) |
Step 4 | dspdate cnfdate <mm:dd:yyyy> cnftmzn <timezone> cnftmzngmt <timeoffsetGMT> cnftime <hh:mm:ss> | Configure the switch time. (See Viewing and Setting the Switch Date and Time, page 7-14.) |
Step 5 | dspcds dspcd cc <slotnumber> | Verify the hardware configuration. (See Verifying the Hardware Configuration, page 7-15.) |
Step 6 | dspred | Verify PXM1 card redundancy configuration, if two cards are installed. (See Managing Redundant Cards, page 7-18.) |
Step 7 | dspcds setrev <slot> <version> | Verify firmware versions installed and configure version to use for each card. (See Managing Firmware Version Levels for Cards, page 7-19.) |
Step 8 | No CLI commands needed to configure Clocksource | No clocking configuration is required for the SES. Clock Source is pre-set to use the uplink for the in-band clock source. (See Managing Network Clock Sources, page 7-23.) |
Step 9 | No CLI commands needed to configure the PNNI controller on the SES. | No PNNI controller configuration is required for the SES. Controller configuration is done through a BPX 8600 switch.(See Configuring the PNNI Controller, page 7-24.) For more information, refer to Chapter 11, "Configuring ATM SVCs, PNNI Routing, and SPVCs". |
Step 10 | cnfsnmp community [string] cnfsnmp contact [string] cnfsnmp location [string] dspsnmp | Configure SNMP management. (See Configuring for Network Management, page 7-24.) |
Step 11 | saveallcnf | Save the switch configuration. (See Saving a Configuration, page 7-25.) |
The Command Line Interface (CLI) management tool allows you to configure the SES and display the switch status. All the configuration and monitoring procedures described in this book use the CLI tool.
While the switch does support management from Cisco WAN Manager (CWM) or an SNMP manager, you must begin your configuration using the CLI. Before other tools can connect the switch, you must use the CLI to configure the switch to support those tools.
To configure the switch using the CLI, you can use either of the following:
You must begin the configuration with a directly attached terminal. To enable Telnet client management, you must configure the appropriate IP interfaces on the switch.
The following sections describe how to establish CLI management sessions using a directly-attached terminal, how to configure the switch to support CLI sessions over IP, and how to establish CLI sessions over IP.
For instructions on physically connecting a terminal directly to the switch, refer to the instructions in the Cisco Service Expansion Shelf Hardware Installation Guide, Release 1.0.
To begin configuration, use the following procedure.
For instructions on operating the terminal or terminal emulation program, refer to the documentation for that product.
Step 2 If the Login prompt does not appear, press Enter. The Login prompt comes from the switch and indicates that the terminal has successfully connected to the switch.
Step 3 When the Login prompt appears, enter the user name provided with your switch and press Enter.
Step 4 When the password prompt appears, enter the password provided with your switch and press Enter.
After you successfully log in, a prompt appears that is similar to the following:
spirit.1.PXM.a >
The CLI prompt uses the following format:
nodename.slot.cardtype.state>
nodename | The nodename is the name of the node. To change the name, see "Setting and Viewing the Switch Name," which appears later in this chapter. |
slot | The slot number indicates the slot number of the card you are connected to. |
cardtype | The cardtype identifies the model of the card: PXM. |
The card state is active (a), standby (s), or initialized (i). Cards are labeled as initialized during switch startup. |
Once you have completed the procedure above, you have established a configuration session and you are ready to begin configuration. The next two sections describe how to enable a configuration for Ethernet and dial-up connections.
The SES supports IP communications over the following interface types:
The following sections describe how to configure the switch to support IP communications through the Ethernet and dial-up ports on the PXM1.
Before you can manage the switch through the PXM1 LAN port, you must first assign an IP address to the LAN port. This Ethernet LAN port is located on the PXM1 back card. For instructions on physically connecting a terminal or workstation to this port, refer to the Cisco Service Expansion Shelf Hardware Installation Guide, Release 1.0.
To configure an IP address for the PXM1 LAN port, use the following procedure.
Step 2 Verify that the IP address is not already configured by entering the dspipif command:
spirita.1.PXM.a> dspipif lnPci0
 |
Note If you omit the lnPci0 option, the switch displays the configuration for all switch IP interfaces: the ATM interface (atm0), the PXM1 LAN port interface (lnPci0), and the PXM1 maintenance port interface (sl0). |
In the IP Interface Configuration Table, look for an Internet address entry under the lnPci entry. If an IP address is configured, you can use that address and skip the rest of this procedure. However, if the address has not been entered or is incompatible with your network, you must configure a valid IP address as described in the next step.
Step 3 To set the IP address for the LAN port, enter the ipifconfig command using the following format:
spirita.1.PXM.a> ipifconfig lnPci0 <IP_Addr> <netmask Mask>
Replace IP_Addr with the IP address you want this port to use, and replace Mask with the network mask used on this network.
 |
Tips Cisco recommends that you use the same subnet for all IP addresses defined on all SESs. This simplifies router configuration. |
|
Note There are other options for the ipifconfig command, and you can set one or more options simultaneously. Any options you don't define in a command remain unchanged. |
After you complete this procedure, the switch is ready for management through the PXM1 Ethernet port.
Before you can manage the switch using the dial-up interface, you must first assign an IP address to the maintenance port on the switch. This maintenance port is located on the PXM1 back card. For instructions on physically connecting a modem to this maintenance port, refer to the Cisco Service Expansion Shelf Hardware Installation Guide, Release 1.0.
To configure an IP address on the switch maintenance port, use the following procedure.
Step 2 Verify that the IP address is not already configured by entering the following command:
spirita.1.PXM.a> dspipif sl0
|
Note If you omit the sl0 option, the switch displays the configuration for all switch IP interfaces: the ATM interface (atm0), the PXM1 LAN port interface (lnPci0), and the PXM1 maintenance port interface (sl0). |
In the IP Interface Configuration Table, look for an Internet address entry under the sl0 entry. (You may need to press Enter to see this.) If an IP address is configured, you can use that address and skip the rest of this procedure. However, if the address has not been entered or is incompatible with your network, you must configure a valid IP address as described in the next step.
Step 3 To set the IP address for the maintenance port, enter the ipifconfig command using the following format:
spirita.1.PXM.a> ipifconfig sl0 <IP_Addr> <netmask Mask>
Replace IP_Addr with the IP address you want this port to use, and replace Mask with the network mask used on this network.
|
Tips Cisco recommends that you use the same subnet for all IP addresses defined on all SESs. This simplifies router configuration. |
|
Note There are other options for the ipifconfig command, and you can set one or more options simultaneously. Any options you don't define in a command remain unchanged. |
After you complete this procedure, the switch is ready for configuration through the maintenance port.
Before you can establish a CLI Telnet session from a LAN workstation, you must configure one of the following switch interfaces to support IP connectivity:
The procedure for configuring the PXM1 LAN port is described in the previous section. The procedure for configuring the ATM interface is described in Appendix B, "Preparing for IP Communications over an ATM Interface."
After the appropriate interface is configured and a physical path is established to the SES, you can start a CLI session using a workstation with a Telnet program and the switch's IP address. To establish a CLI management session, use the following procedure.
C:>telnet ipaddress
Replace ipaddress with the IP address assigned to the switch.
|
Note Note that the Telnet program on your workstation may require a different start up and connection procedure. For instructions on operating your Telnet program, refer to the documentation for that product. |
Step 2 If the Login prompt does not appear, press Enter.
The Login prompt comes from the switch and indicates that the terminal has successfully connected to the switch.
Step 3 When the Login prompt appears, enter the user name provided with your switch and press Enter.
Step 4 When the password prompt appears, enter the password provided with your switch and press Enter.
After you successfully log in, a prompt appears that is similar to the following:
spirita.1.PXM.a >
The CLI prompt uses the following format:
nodename.slot.cardtype.state>
nodename | The nodename is the name of the node. To change the name, see "Setting and Viewing the Switch Name," which appears later in this chapter. |
slot | The slot number indicates which card you are configuring. For most general switch configuration procedures, you need to configure the switch using the PXM1 cards in slots 1 or 2. For many trunk configuration procedures, you need to modify a PXM card. |
cardtype | The cardtype identifies the model of the card: PXM. |
state | The card state is active (a), standby (s), or initialized (i). Card is labeled initialized during switch startup. |
Once you have completed the procedure above, you have established a CLI session and you are ready to begin switch configuration and monitoring.
Before you can establish a dial-up CLI Telnet session from a workstation, you must configure an IP address for the maintenance port as described in "Preparing for IP Communications through the Dial-Up Interface." You must also install the correct hardware to support dial-up communications. For instructions on preparing the switch for dial-up communications through the maintenance port, refer to the instructions in the Cisco Service Expansion Shelf Hardware Installation Guide, Release 1.0.
After the maintenance port interface is configured and a physical path is established to the SES, you can start a CLI session by establishing a dial-up connection from the workstation to the switch and directing a Telnet session to the switch's IP address. To establish a CLI management session, use the following procedure.
You will need the telephone number for the line connected to the modem at the switch. For instructions on establishing the connection to the switch, refer to the documentation for the workstation and the attached modem.
Step 2 After the dial-up connection is established, start the Telnet program with a command similar to the following:
C:>telnet ipaddress
Replace ipaddress with the IP address assigned to the switch.
|
Note Note that the Telnet program on your workstation may require a different start up and connection procedure. For instructions on operating your Telnet program, refer to the documentation for that product. |
Step 3 If the Login prompt does not appear, press Enter.
The Login prompt comes from the switch and indicates that the terminal has successfully connected to the switch.
Step 4 When the Login prompt appears, enter the user name provided with your switch and press Enter.
Step 5 When the password prompt appears, enter the password provided with your switch and press Enter.
After you successfully log in, a prompt appears that is similar to the following:
spirita.1.PXM.a >
The CLI prompt uses the following format:
nodename.slot.cardtype.state>
nodename | The nodename is the name of the node. To change the name, see "Setting and Viewing the Switch Name," which appears later in this chapter. |
slot | The slot number indicates the slot number of the card you are configuring: 1 or 2. |
cardtype | The cardtype identifies the model of the card: PXM. |
state | The card state is active (a), standby (s), or initialized (i). Cards are labeled as initialized during switch startup. |
Once you have completed the procedure above, you have established a CLI management session and you are ready to begin configuration.
To end a CLI management session, enter the bye command.
|
Note This command ends the CLI session. It does not terminate the phone call when you are using a dial-up connection. |
To restart the session after entering the bye command, just press Return and the switch will prompt you for a username and password.
The commands in the switch operating system are associated with the cards that are installed in the switch. Before you execute a command, you must select a card that supports the command. The switch displays the currently selected card in the switch prompt. For example, the following switch prompt shows that the PXM1 card in slot 1 is selected:
spirita.1.PXM.a >
To select another card in the switch, enter the following command:
spirita.1.PXM.a > cc <slotnumber>
Replace slotnumber with the number of the slot in which the card you want to manage is installed Valid slot numbers for PXM cards are 1 and 2.
spirita.2.PXM.a >
If you have trouble executing a command, look at the switch prompt to see if you have selected the correct card and type for the command. The following example shows the response to an unrecognized command:
spirita.1.PXM.a > dspport ERR: unknown command: "dspport"
|
Tips The command examples in this book include the switch prompt so that you can verify which card type supports a command. Also, commands can be entered without options. When a command is entered without an option, the last value defined for that option is maintained. |
The following example demonstrates that the switch recognizes partial commands and displays long reports one page at a time.
spirita.1.PXM.a > he
Available commands
------------------
?
abortofflinediag
abortrev
addaddr
addapsln
addchan
addcon
addfltset
addlmiloop
addmaster
addpnni-node
addpnni-summary-addr
addpnport
addprfx
addserialif
addslave
addtrapmgr
adduser
Type <CR> to continue, Q<CR> to stop:
Because the help command is the only command that begins with he, you can use the abbreviated he command to display help. Because the help report is too long to appear on one screen, it is displayed in pages. Press Return to display the next page, or type q and press Return to cancel the report display.
The following example demonstrates what can happen when a command is entered at the wrong card prompt.
spirita.2.PXM.s > ipifconfig ERR: command unavailable in current card state This command is available only on the active card and not on the standby card.
The switch operating system provides two ways to display information on commands. To display a list of all the commands available, enter the following command:
spirita.1.PXM.a > help
To display the syntax of a command, enter the command without any parameters. The following example shows the syntax report provided by the switch using the addport command.
spirita.1.PXM.a > addpnport
ERR: incorrect number of parameters: (not enough)
Syntax: addpnport <portid>
shelf.slot:subslot.port:subport -- [shelf.]slot[:subslot].port[:subport]default=Mandatory Parameter
possible errors are:
NULL
|
Note Some commands, such as dspcd and saveallcnf, do not require parameters, so entering the command without parameters executes the command.When you enter the saveallcnf command, which saves the current switch configuration to a file, the switch prompts you to confirm the save before execution begins. Whenever the switch prompts you to confirm a command, the command you are confirming is likely to change the switch configuration or reduce switch performance. |
The username and password supplied with your switch provides access to all customer accessible features within the switch, and it allows you to add and delete users and change user passwords.
When configuring administrator access for the switch, consider the following recommendations:
The following sections describe how to add users, change passwords for existing users, and delete users.
When you add users to the switch, you must specify the following for each user:
The user name and password identify the user when the user wants to manage the switch. The access level you specify determines which commands the user can use and at which levels the user can add users or modify user configurations.
To add a user to the switch, use the following procedure.
Step 2 Enter the following command after the switch prompt:
spirita.1.PXM.a >adduser <username> <accessLevel>
Enter the username using 1-12 alphanumeric characters. Specify the access level by entering one of the levels defined in Table 2-1.
|
Note The access level keywords are case-sensitive and must be entered as shown. Also, you cannot add users at access levels that are equal to or above your own access level. |
| Access Level Keyword | Descriptions |
|---|---|
Users at the Cisco access level can add users, delete users, change passwords, and change access levels for users at the following levels: SERVICE_GP, SUPERUSER_GP, GROUP1 to GROUP5, and ANYUSER. | |
Users at the service access level can add users, delete users, change passwords, and change access levels for users at the following levels: SUPERUSER_GP, GROUP1 to GROUP5, and ANYUSER. | |
Users at the superuser access level can add users, delete users, change passwords, and change access levels for users at the following levels: GROUP1 to GROUP5 and ANYUSER. | |
Users at the GROUP1 access level can add users, delete users, change passwords, and change access levels for users at the following levels: GROUP2 to GROUP5 and ANYUSER. | |
Users at the GROUP2 access level can add users, delete users, change passwords, and change access levels for users at the following levels: GROUP3 to GROUP5 and ANYUSER. | |
Users at the GROUP3 access level can add users, delete users, change passwords, and change access levels for users at the following levels: GROUP4 to GROUP5 and ANYUSER. | |
Users at the GROUP4 access level can add users, delete users, change passwords, and change access levels for users at the following levels: GROUP5 and ANYUSER. | |
Users at the GROUP5 access level can add users, delete users, change passwords, and change access levels for users at the ANYUSER level. | |
Users at the ANYUSER level cannot add users, delete users, change passwords or change access levels for other users. |
|
Tips To determine which commands are available at a particular access level, log into the switch as a user at that access level, then enter the help command. |
If you enter the command correctly, the switch prompts you for a password.
Step 3 Enter a password using 5 to 15 characters. If you press Return without entering a password, the system assigns the default password "newuser."
Step 4 When prompted, enter the password a second time to validate the previous entry.
This completes the addition of the new user.
Step 5 To display the new user in a list of all users, enter the command dspusers.
Step 6 To test the username, enter the bye command, then log in as the new user.
|
Tips If you forget which username you used to log in, enter the whoami command. This command displays the username, access level, and access method (for example, Telnet) for the current session. |
The Cisco SES provides two commands that you can use to changer administrator passwords: cnfpasswd and cnfuser. The next section describes how to use the cnfuser command. This section describes how to change passwords with the cnfpasswd command.
To change the password of a switch administrator with the cnfpasswd command, use the following procedure.
Step 2 Enter the following command after the switch prompt:
spirita.1.PXM.a >cnfpasswd <username>
Replace username with the name of the user whose password you are changing. If you want to change the password of the username you used to log in, you can omit the username. You can only change passwords for users that have privileges lower than the username you used to log in.
Step 3 Enter a password using 5 to 15 characters.
Step 4 When prompted, enter the password a second time to validate the correct entry.
This completes the change of password.
Step 5 To test the new password, enter the bye command, then log in using the new password.
After you create an administrator user, you can change that user's access level or password using the cnfuser command.
|
Note You can also change the user password with the cnfpasswd command as described in the preceding section. |
To change the user level or password of a switch administrator, use the following procedure.
Step 2 Enter the following command after the switch prompt:
spirita.1.PXM.a >cnfuser -u <username> [-p <password>] [-l <accessLevel>
Replace username with the name of the user for whom you are making the change.
If you are changing the password, specify the -p option and enter a password containing 5-15 characters. If you are changing the user access level, specify the -l (lowercase L) option and enter the appropriate access level as shown in Table 2-1.
|
Note You can only change passwords and access levels for users that have privileges lower than the username you used to log in. |
Step 3 To test a new password, enter the bye command, then log in using the new password.
Step 4 To verify a user access level change, enter the dspusers command.
The dspusers command displays all the usernames and the access level for each user as shown in the following example:
p2_203.7.PXM.a > dspusers
UserId AccessLevel
-------------------------
cisco CISCO_GP
service SERVICE_GP
superuser SUPER_GP
jbowman GROUP1
To delete a user, use the following procedure.
Step 2 Enter the following command after the switch prompt:
spirita.1.PXM.a >deluser <username>
Enter the username using 1 to 12 alphanumeric characters.
This completes the deletion of a user.
Step 3 To verify the user has been deleted, enter the command dspusers.
The switch name identifies the switch you are working on, which is important when you are managing multiple switches. The current switch name appears in the CLI prompt when you are managing a switch. To change the switch name, use the following procedure.
Step 2 Enter the following command after the switch prompt:
spirita.1.PXM.a > cnfname <node name>
Enter up to 32 characters for the new node name, and since the node name is case-sensitive, be sure to use the correct case. For example:
spirita.1.PXM.a > cnfname spiritb
The new name appears immediately in the next CLI prompt.
spiritb.1.PXM.a >
The switch date and time is appended to event messages and logs. To assure that events are properly time stamped, use the following procedure to view and change the date and time.
Step 2 To view the current switch date and time, enter the following command after the switch prompt:
spirita.1.PXM.a > dspdate
Step 3 To change the switch date, enter the following command:
spirita.1.PXM.a > cnfdate <mm/dd/yyyy>
Step 4 To change the time zone, enter the following command:
spirita.1.PXM.a > cnftmzn <timezone>
Replace timezone with GMT for Greenwich Mean Time, EST for Eastern Standard Time, CST for Central Standard Time, MST for Mountain Standard Time, PST for Pacific Standard Time. Options 2 through 5 are for switches located in the Western Hemisphere. If your switch is located outside the Western Hemisphere, select GMT and use the next step to specify an offset from GMT.
Step 5 To configure an offset from GMT, enter the following command:
spirita.1.PXM.a > cnftmzngmt <timeoffsetGMT>
Replace timeoffsetGMT with the offset in hours from GMT. Enter a number in the range of -12 to +12.
Step 6 To change the switch time, enter the following command:
spirita.1.PXM.a > cnftime <hh:mm:ss>
Replace hh with the hour of the day (0-23), mm with the minute of the hour (0-59), and ss with the number of seconds in the minute (0-60).
Step 7 To verify the new date and time settings, enter the dspdate command.
Before you can configure your switch, you need to collect information about the cards and software installed on the switch. You need to enter this information during the various configuration tasks. Table 2-2 shows the information you need and serves as a worksheet where you can enter this information.
| Card | Front Card Type | Upper Back Card | Lower Back Card | Primary Software Version | Boot Firmware Version | Redundant Slot | Redundancy Type |
|---|---|---|---|---|---|---|---|
1 |
|
|
|
|
|
|
|
2 |
|
|
|
|
|
|
|
The following procedure describes how to display the configuration information you need to enter in this table. It also describes how to verify that the correct upper and lower back cards are installed for each front card.
Step 2 To display a list of all the cards installed in the switch, enter the dspcds command after the switch prompt:
spirita.1.PXM.a > dspcds
dspcds
spirita System Rev: 01.00 May. 21, 2000 03:48:51 PST
Backplane Serial No: 12345 Bp HW Rev: 00.00 GMT Offset: -8
Node Alarm: NONE
Card Front/Back Card Alarm Redundant Redundancy
Slot Card State Type Status Slot Type
--- ---------- -------- -------- ------- -----
01 Active/Active PXM1_OC3 NONE 02 PRIMARY SLOT
02 Standby/Active PXM1_OC3 NONE 01 SECONDARY SLOT
03 Empty --- --- --- ---
04 Empty --- --- --- ---
05 Empty --- --- --- ---
06 Empty --- --- --- ---
07 Empty --- --- --- ---
Step 3 In the worksheet in Table 2-2, write down the following information for each card:
Step 4 To display additional information on the PXM1 card, enter the dspcd command:
spirita.1.PXM.a > dspcd
|
Note The dspcd and dspcds commands are very similar, but they produce different reports. The dspcd command displays information about a specific card and can be entered at the prompt for PXM cards. The dspcds command displays summary information for all cards in the switch and can only run at the PXM card prompt. |
The dspcd command displays information that is unique to a particular card. The switch displays a report similar to the following:
spirita.1.PXM.a > dspcd
spirita System Rev: 02.00 May. 22, 2000 10:51:08 GMT
SES-CNTL Node Alarm: NONE
Slot Number 1 Redundant Slot: 2
Front Card Upper Card
---------- ----------
Reserved Card: PXM1_OC3 UIA BackCard
Inserted Card:
State: Active Active
Serial Number: SBK0306004A SAK02350011
Prim SW Rev: 2.0(1)D ---
Sec SW Rev: 2.0(1)D ---
Boot FW Rev: 1.0(39)B1 ---
HW Ver: 69.5248.54
Orderable Part#: 800-03669-02 800-03688-01 800-05053-01
CLEI Code: 0 123456
Reset Reason: On Reset From Shell
Card Alarm: NONE
Failed Reason: None
Miscellaneous Information:
Type <CR> to continue, Q<CR> to stop:
spirita System Rev: 02.00 May. 22, 2000 10:51:08 GMT
SES-CNTL Node Alarm: NONE
Crossbar Slot Status: No Crossbar
Alarm Causes
------------
NO ALARMS
Step 5 In the worksheet in Table 2-2, write down the following information for each card:
Step 6 To collect card specific information for another card, enter the cc and dspcd commands:
spirita.1.PXM.a > cc number spirita.1.PXM.a > dspcd
Replace number with the slot number for the card for which you want information. When the report appears for the card, write down the card information in the worksheet in Table 2-2. The following example shows the report for an PXM card:
spirita.1.PXM.a > cc 2
(session redirected)
spirita.2.PXM.s > dspcd
spirita System Rev: 02.00 May. 22, 2000 10:54:30 GMT
SES-CNTL Node Alarm: UNKNOWN
Slot Number 2 Redundant Slot: 1
Front Card Upper Card
---------- ----------
Reserved Card: PXM1_OC3 UIA BackCard
Inserted Card:
State: Standby Active
Serial Number: SAK023800HV SBK03050077
Prim SW Rev: 2.0(1)D ---
Sec SW Rev: 2.0(1)D ---
Boot FW Rev: 1.0(39)B1 ---
HW Ver: 69.5248.57
Orderable Part#: 800-04001-02 800-03688-01 800-03061-02
CLEI Code: 0 BAI9Y00AAA
Reset Reason: On Reset From Shell
Card Alarm: UNKNOWN
Failed Reason: None
Miscellaneous Information:
spirita System Rev: 02.00 May. 22, 2000 10:54:30 GMT
SES-CNTL Node Alarm: UNKNOWN
Crossbar Slot Status: No Crossbar
Alarm Causes
------------
Reserved Front Card Role Not Assigned : ALARM
Reserved Back Card Missing : ALARM
Step 7 After you have entered the required information for all cards in Table 2-2, use Table 2-3 to verify the following:
If any of the cards are installed incorrectly, refer to the Cisco ServiceExpansion Shelf Hardware Installation Guide for instructions on installing the cards correctly.
|
Note The locations where the upper and lower back cards are installed are also called bays. Each slot has an upper and a lower bay for back cards. |
| Front Card Type | Description | Back Card Types | Back Card Locations | Valid Slot Numbers |
|---|---|---|---|---|
PXM-OC3 | Processor Switch Module | UI Stratum 3 | Upper | 1 and 2 1 and 2 1 and 2 |
MMF-4-155 SMF-4-155 | Lower Lower | |||
PXM-T3E3 | Processor Switch Module | UI Stratum 3 | Upper | 1 and 2 1 and 2 1 and 2 |
PSM-DC-T3 PSM-DC-E3 | Lower Lower |
The Cisco SES supports redundancy between two PXM1 cards. This redundancy is preconfigured on the switch. The following sections describe how to display the redundancy configuration and how to switch operation from one card to the other.
To display the redundancy configuration for the switch, use the following procedure.
Step 2 To view the redundancy status, enter the following command after the switch prompt:
spirita.1.PXM.a > dspred
After you enter the command, the switch displays a report similar to the following:
spirita.1.PXM.a > dspred spirita System Rev: 02.00 May. 22, 2000 11:25:02 GMT SES-CNTL Node Alarm: NONE Primary Primary Primary Secondary Secondary Secondary Redundancy SlotNum Type State SlotNum Type State Type ------- ------- ------- --------- --------- --------- ---------- 1 PXM1 Active 2 PXM1 Standby 1-1
To switch operation from one redundant PXM card to another, use the following procedure.
Step 2 To switch cards, enter the following command after the switch prompt:
spirita.1.PXM.a > switchcc
Cards within the SES switch can run two types of firmware: boot firmware and runtime firmware. The boot firmware provides the basic information the card needs to start up. The runtime firmware controls the operation of the card after startup.
Before a switch can begin using a card, it must have the correct firmware installed and a version number must be specified for the firmware. When you receive a new switch from Cisco, it is a good idea to verify that the switch has been configured to use the proper firmware for each card. The following sections explain how to
If you have just received a new switch from Cisco, you should perform the procedure in the next section to verify that the firmware version is set correctly for all the cards. If the version levels are set correctly, you can skip the other procedures. The remaining procedures describe how to collect the information you need to change the firmware version levels and how to change the firmware version levels.
To determine if any cards need to have the firmware version set, use the following procedure.
Step 2 To display a list of all the cards in the switch, enter the dspcds command:
spirita.1.PXM.a > dspcds
Example 7-1 shows the display for this command. If the firmware version for a card has not been set it will appear as either failed or empty and the card state will be unknown.
spirita.1.PXM.a > dspcds
dspcds
spirita System Rev: 01.00 May. 21, 2000 03:48:51 PST
Backplane Serial No: 12345 Bp HW Rev: 00.00 GMT Offset: -8
Node Alarm: NONE
Card Front/Back Card Alarm Redundant Redundancy
Slot Card State Type Status Slot Type
--- ---------- -------- -------- ------- -----
01 Active/Active PXM1_OC3 NONE 02 PRIMARY SLOT
02 Standby/Active PXM1_OC3 NONE 01 SECONDARY SLOT
03 Empty --- --- --- ---
04 Empty --- --- --- ---
05 Empty --- --- --- ---
06 Empty --- --- --- ---
07 Empty --- --- --- ---
Note the slot number, card type, and redundancy type for each card that needs to have the firmware version set. You will need this information to activate these cards as described in "Setting the Firmware Version for a Card."
|
Note If none of the cards display the Failed/Empty card state, you do not have to set firmware versions. However, you might want to update firmware if newer versions are released. The next section describes how to verify software version levels. |
When you are having problems with your switch, or when you've taken delivery of a new switch and it has not been installed immediately, it is wise to verify the firmware versions installed on the switch. If newer versions of this firmware are available, installing the updated firmware can eliminate or prevent switch problems.
To verify the firmware versions in use on your switch, use the following procedure.
Step 2 Compare the versions you noted in Table 2-2 with the latest versions listed in the Release Notes for the SES PNNI Controller.
|
Note For instructions on download and installing new firmware versions, see Appendix A, "Downloading and Installing Firmware Updates." |
To set the firmware version number for an inactive card or for an updated firmware version, you must know the version number and be able to enter it in the correct format. In most cases, you will find the correct firmware version numbers in the Release Notes for the SES PNNI Controller . If the release notes are not available and you've downloaded the firmware file, you can use the firmware filename to determine the version number as described in the following procedure.
Step 2 To view the files on the switch hard drive, you can enter standard UNIX commands at the switch prompt. To change directories to the firmware directory, FW, enter the cd C:/FW command:
spirita.1.PXM.a > cd C:/FW
|
Note Remember that UNIX directory and filenames are case sensitive. |
Step 3 To list the contents of the directory, enter the ll command:
spirita.1.PXM.a > ll
The display shows:
spirita.1.PXM.a > ll
size date time name
-------- ------ ------ --------
512 MAR-25-2000 00:02:56 . <DIR>
512 MAR-25-2000 00:02:56 .. <DIR>
2910432 MAR-24-2000 16:07:16 pxm1_002.000.126-A1_ses.fw
690984 MAR-24-2000 16:09:12 pxm1_002.000.126-A1_bt.fw
2958240 MAY-18-2000 05:40:48 pxm1_002.000.001-D_ses.fw
696752 APR-10-2000 09:47:40 pxm1_002.000.133-A1_bt.fw
2934904 APR-10-2000 09:23:30 pxm1_002.000.139-A1_ses.fw
2927944 APR-10-2000 09:47:58 pxm1_002.000.133-A1_ses.fw
697320 APR-10-2000 09:28:14 pxm1_002.000.139-A1_bt.fw
698136 MAY-11-2000 12:50:06 pxm1_001.000.039-B1_bt.fw
2972320 MAY-11-2000 12:50:30 pxm1_001.000.039-B1_ses.fw
2957760 MAY-12-2000 06:47:06 pxm1_001.000.001-D_ses.fw
2972176 MAY-13-2000 05:53:06 pxm1_002.000.039-B1_ses.fw
In the file system :
total space : 819200 K bytes
free space : 783016 K bytes
Filenames that include "_ses" are for runtime firmware, and filenames that include "_bt" are for boot image. When you first receive the switch from Cisco, there will be single versions of each file. If you download updates to any files, there will be multiple versions of those files.
The last step in discovering the firmware version number is to write it down in the format required by the command that activates the firmware, setrev. The following example shows the format required by the setrev command. You can display this by entering the setrev command without any parameters.
moshea#20.7.PXM.a > setrev
ERR: Syntax: setrev <slot> <new revision>
revision - revision number. E.g.,
2.0(1)
2.0(1.248)
2.0(0)B1 or 2.0(0)B2
2.0(0)A1 or 2.0(0)A2
2.0(0)I1 or 2.0(0)I2
2.0(0)D
NOTE: use the same revision for both primary
and secondary to start new revision
Step 4 Translate the filenames to version numbers and write this down so you can set the revision levels for the software.
Table 2-4 shows some example filenames and the correct version numbers. The next section describes how to set the firmware version number for a card.
| Filename | Description | Setrev Command |
|---|---|---|
pxm1_001.000.000.000_ses.fw | run time firmware image | set rev 1.0(0) 0 |
pxm1_001.006.000.000_ses.fw | run time firmware image | set rev 1.6(0) 0 |
pxm1_001.006.007.000_ses.fw | run time firmware image | set rev 1.6(7) 0 |
pxm1_001.006.007.002_ses.fw | run time firmware image | set rev 1.6(7) 2 |
pxm1_002.000.014-A1_bt.fw | boot image | not applicable |
To set the firmware version of the card, use the following procedure.
Step 2 Establish a configuration session as described in "Establishing and Ending a CLI Management Session," earlier in this chapter.
Step 3 If you haven't already done so, complete the hardware and software configuration worksheet in Table 2-2 as described earlier in "Verifying the Hardware Configuration." You need information from this worksheet to complete the next step.
Step 4 To set the firmware revision level for a card, enter the setrev command:
spirita.1.PXM.a > setrev <slot> <version>
Replace slot with the card slot number and replace both primary_revision and secondary_revision with the software version number.
Step 5 To verify the activation of a card for which the status was previously listed as Failed/Empty, enter the dspcds command.
Step 6 To verify that an updated version of the software has been successfully activated, use the cc and dspcd commands to display the software versions as described in "Verifying the Hardware Configuration."
The clock source is automatically configured on the SES. You do not need to run any clock source configuration commands.
There are no PNNI controller commands for the SES. All controller configuration is done on a BPX 8600 series switch.
The Cisco SES includes a Simple Network Management Protocol (SNMP) agent that you can configure for communications with a network management station such as Cisco WAN Manager (CWM) or a third-party SNMP manager. When configured for SNMP management, the switch accepts configuration commands from management stations and sends status and error messages to the management station.
To configure the SNMP agent, use the following procedure.
Step 2 To define the SNMP password for network management, enter the following command:
spirita.1.PXM.a > cnfsnmp community [password]
If the password parameter is not specified, the password becomes "private."
Step 3 To define a text string that identifies the location of the switch to the management station, enter the following command:
cnfsnmp location [location]
If the location parameter is not specified, the location is set to null (no text). The location value is sent to SNMP managers when information is requested about the sysLocation MIB object.
Step 4 To define a text string that identifies a person to contact regarding issues with this switch, enter the following command:
cnfsnmp contact [contact]
If the contact parameter is not specified, the location is set to null (no text). The contact value is sent to SNMP managers when information is requested about the sysContact MIB object.
Step 5 To display the SNMP agent configuration, enter the dspsnmp command. The command display appears similar to the following:
spirita.1.PXM.a > dspsnmp spirita System Rev: 02.00 Feb. 17, 2000 09:18:04 PST spirit Shelf Alarm: NONE Community: password rw System Location: Lab System Contact Jack, 555-555-1212
After configuring your switch or after making configuration updates, it is wise to save the configuration. Restoring a saved configuration is much easier than reentering all the commands used to configure the switch.
The configuration is saved to a file in the C:/CNF directory. The file is named using the switch name and the current date as follows:
Name_01_DateTime.zip.
The date appears in YYYYMMDD (year, month, day) format, and the time appears in HHMM (hour, minute) format. For example, if the configuration for a switch named "spirita" were saved on February 29th, 2000 at 2:31pm, the file would be named C:/CNF/spiritspirita_01_200002291431.zip.
You can perform a configuration save if both of the following are true:
To save the current switch configuration, use the following procedure.
Step 2 To save the configuration, enter the saveallcnf command:
spirita.1.PXM.a > saveallcnf
Step 3 Read the prompt that appears, press Y if you want to continue, and press Enter.
When the save is complete, the switch prompt reappears and the new file is stored in the C:/CNF directory.
You can perform a configuration restore if all of the following are true:
 |
Caution The restoreallcnf command resets all cards in the switch and terminates all calls passing through the switch. |
To restore a saved switch configuration, use the following procedure.
Step 2 Verify that the file from which you want to restore configuration data is located in the C:/CNF directory.
|
Note The C:/CNF directory is the only location from which you can restore a configuration file. If the file has been moved to another directory or stored on another system, the file must be returned to this directory before the data can be restored. |
Step 3 To restore a saved configuration file, enter the restoreallcnf command:
spirita.1.PXM.a > restoreallcnf -f filename
Replace filename with the name of the saved configuration file.You do not have to enter the path to the file or the extension. For information on the location and name of the file, see "Saving a Configuration."
Posted: Thu Jul 27 19:49:09 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.