|
|
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
MGX 8850. This procedure is provided as an overview and as a quick reference for those who have already configured the MGX 8850.
Command | Purpose | |
|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The Command Line Interface (CLI) management tool allows you to configure the MGX 8850 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 MGX 8850 Hardware Installation Guide, Release 2.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:
mgx8850a.7.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 PXM45 cards in slots 7 or 8. For many trunk configuration procedures, you need to modify an AXSM card in slots 1-6 and 9-14. |
cardtype | The cardtype identifies the model of the card: PXM or AXSM. |
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 MGX 8850 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 PXM45. The configuration required for the ATM interface is more complicated and is described in "Preparing for IP Communications over an ATM Interface."
Before you can manage the switch through the PXM45 LAN port, you must first assign an IP address to the LAN port. This Ethernet LAN port is located on the PXM45 back card. For instructions on physically connecting a terminal or workstation to this port, refer to the Cisco MGX 8850 Hardware Installation Guide, Release 2.0.
To configure an IP address for the PXM45 LAN port, use the following procedure.
Step 2 Verify that the IP address is not already configured by entering the dspipif command:
mgx8850a.7.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 PXM45 LAN port interface (lnPci0), and the PXM45 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:
mgx8850a.7.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 MGX 8850s. 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. For more information on this command, refer to Cisco MGX 8850 Routing Switch Command Reference, Release 2.0. |
After you complete this procedure, the switch is ready for management through the PXM45 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 PXM45 back card. For instructions on physically connecting a modem to this maintenance port, refer to the Cisco MGX 8850 Hardware Installation Guide, Release 2.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:
mgx8850a.7.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 PXM45 LAN port interface (lnPci0), and the PXM45 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:
mgx8850a.7.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 MGX 8850s. 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. For more information on this command, refer to Cisco MGX 8850 Routing Switch Command Reference, Release 2.0. |
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 PXM45 LAN port is described in the previous section. The procedure for configuring the ATM interface is described in "Preparing for IP Communications over an ATM Interface."
After the appropriate interface is configured and a physical path is established to the MGX 8850, 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:
mgx8850a.7.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 PXM45 cards in slots 7 or 8. For many trunk configuration procedures, you need to modify an AXSM card in slots 1-6 and 9-14. |
cardtype | The cardtype identifies the model of the card: PXM or AXSM. |
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 MGX 8850 Hardware Installation Guide, Release 2.0.
After the maintenance port interface is configured and a physical path is established to the MGX 8850, 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:
mgx8850a.7.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 PXM45 cards in slots 7 or 8. For many trunk configuration procedures, you need to modify an AXSM card in slots 1-6 and 9-14. |
cardtype | The cardtype identifies the model of the card: PXM or AXSM. |
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 PXM45 card in slot 7 is selected:
mgx8850a.7.PXM.a >
To select another card in the switch, enter the following command:
mgx8850a.7.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 7 and 8. Valid slot numbers for AXSM cards are 1-6 and 9-14. After you change cards, verify your card selection by viewing the switch prompt. The following example shows the prompt for an AXSM card in slot 9:
mgx8850a.9.AXSM.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:
mgx8850a.9.AXSM.a > dspdate ERR: unknown command: "dspdate"
The dspdate command must be run on a PXM45 card and is not recognized by an AXSM card.
|
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.
p2_203.7.PXM.a > he
Available commands
------------------
?
abortofflinediag
abortrev
addaddr
addcontroller
addfltset
addpnni-node
addpnni-summary-addr
addpnport
addprfx
addred
addserialif
addtrapmgr
adduser
aesa_ping
arpAdd
arpDelete
arpFlush
arpShow
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.
mgx8850a.9.AXSM.a > dspcds
ERR: incorrect number of parameters: (not enough)
Syntax: dspcdsct <bw|gen|cosb|vcThr|cosThr>
bw|gen|cosb|vcThr|cosThr -- bw: Bandwidth parameters
gen: policing and CAC parameters
cosb: cosb parameters
vcThr: vc threshold parameters
cosThr: cosb threshold parameters
In the example above, the dspcds command is entered at the AXSM card prompt, but this command is not supported on the AXSM card (although the dspcd command is). Because the command isn't recognized, the switch matches it up to a command that is supported, which is the dspcdsct command. Because the command was entered without parameters, the switch displays an error message and the correct format for entering the dspcdsct command.
Whenever the switch displays an error message, be sure to check the spelling of the command, the parameters entered with the command, and the prompt at which the command was entered.
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:
mgx8850a.7.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.
mgx8850a.9.AXSM.a > addport
ERR: incorrect number of parameters: (not enough)
Syntax: addport "<ifNum> <bay.line> <guaranteedRate> <maxRate> <sctID> <ifType>
[vpi]"
If Number -- number between 1 and 60
Line Number -- format bay.line
Guaranteed virtual int. Rate -- rates in cells/sec:
Max virtual int. Rate -- for OC48:between 50 and 5651328
for OC12:between 50 and 1412832
for OC3:between 50 and 353208
for T3:between 50 and 96000(PLCP),104268(ADM)
for E3:between 50 and 80000
SctID -- SCT file ID between 0 and 255, for default file use 0
IfType -- 1: uni 2: nni 3: vnni
vpiNum -- vpi between 1 and 4095:
used for configuring interface as virtual trunk
|
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:
mgx8850a.7.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 MGX 8850 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:
mgx8850a.7.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:
mgx8850a.7.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:
mgx8850a.7.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:
mgx8850a.7.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:
mgx8850a.7.PXM.a > cnfname mgx8850b
The new name appears immediately in the next CLI prompt.
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:
mgx8850a.7.PXM.a > dspdate
Step 3 To change the switch date, enter the following command:
mgx8850a.7.PXM.a > cnfdate <mm/dd/yyyy>
Step 4 To change the time zone, enter the following command:
mgx8850a.7.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:
mgx8850a.7.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:
mgx8850a.7.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 |
|
|
|
|
|
|
|
3 |
|
|
|
|
|
|
|
4 |
|
|
|
|
|
|
|
5 |
|
|
|
|
|
|
|
6 |
|
|
|
|
|
|
|
7 |
|
|
|
|
|
|
|
8 |
|
|
|
|
|
|
|
9 |
|
|
|
|
|
|
|
10 |
|
|
|
|
|
|
|
11 |
|
|
|
|
|
|
|
12 |
|
|
|
|
|
|
|
13 |
|
|
|
|
|
|
|
14 |
|
|
|
|
|
|
|
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:
mgx8850a.7.PXM.a > dspcds
The switch displays a report similar to the following:
p2_203.7.PXM.a > dspcds p2_203 System Rev: 02.00 Apr. 09, 2000 07:18:49 GMT Backplane Serial No: SBK03060003 Backplane HW Rev: 00.00 GMT Offset 0 Statistics Master IP Address: 0.0.0.0 Shelf Alarm: NONE Card Front/Back Card Alarm Redundant Redundancy Slot Card State Type Status Slot Type --- ---------- -------- -------- ------- ----- 01 Empty --- --- --- --- 02 Empty --- --- --- --- 03 Empty --- --- --- --- 04 Empty --- --- --- --- 05 Empty --- --- --- --- 06 Empty --- --- --- --- 07 Active/Active PXM45 NONE 08 PRIMARY SLOT 08 Empty Resvd/Emp UNKNOWN_FC MAJOR 07 SECONDARY SLOT 09 Active/Active AXSM_16OC3 NONE NA NO REDUNDANCY 10 Empty --- --- --- --- 11 Empty --- --- --- --- 12 Empty --- --- --- --- 13 Empty --- --- --- --- 14 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 PXM45 card, enter the dspcd command:
mgx8850a.7.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 and AXSM 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:
p2_203.7.PXM.a > dspcd
p2_203 System Rev: 02.00 Apr. 09, 2000 07:12:32 GMT
MGX8850 Shelf Alarm: NONE
Slot Number 7 Redundant Slot: 8
Front Card Upper Card Lower Card
---------- ---------- -----------
Inserted Card: PXM45 UI Stratum3 PXM HardDiskDrive
Reserved Card: PXM45 UI Stratum3 PXM HardDiskDrive
State: Active Active Active
Serial Number: * ,'ô SAK03300045 SAK03250064
Prim SW Rev: 2.0(128)A1 --- ---
Sec SW Rev: 2.0(128)A1 --- ---
Cur SW Rev: 2.0(128)A1 --- ---
Boot FW Rev: 2.0(128)A1 --- ---
Type <CR> to continue, Q<CR> to stop:
p2_203 System Rev: 02.00 Apr. 09, 2000 07:12:32 GMT
MGX8850 Shelf Alarm: NONE
HW Rev: 00.00 48.50 48.51
Orderable Part#: 0-0-0 800-5787-1 800-5052-2
PCA Part#: 0-0-0 73-4210-1 73-3947-2
Reset Reason: On Reset From Shell
Card Alarm: NONE
Failed Reason: None
Miscellaneous Information:
Crossbar Slot Status: EMPTY
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:
mgx8850a.7.PXM.a > cc number mgx8850a.7.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 AXSM card:
pop2one.7.PXM.a > cc 9
(session redirected)
p2_203.9.AXSM.a > dspcd
Front Card Upper Card Lower Card
---------- ---------- ------------
Card Type: AXSM-16-155 SMFIR-8-155-LC ---
State: Active Present Absent
Serial Number: SAK0350008F SAK0345004Y ---
Boot FW Rev: 2.0.128.252 --- ---
SW Rev: 2.0(128)A1 --- ---
HW Rev: 0.0 0.0 ---
Orderable Part#: 800-5776-3 800-5342-1 ---
PCA Part#: 73-4504-2 73-4026-1 ---
Reset Reason:On Power up
Card SCT Id: 6
Type <CR> to continue, Q<CR> to stop:
#Lines #Ports #Partitions #SPVC #SPVP #SVC
------ ------ ----------- ------- ------- -------
5 5 5 0 0 4
Port Group[1]:
#Chans supported:32512 Lines:1.1 1.2 1.3 1.4
Port Group[2]:
#Chans supported:32512 Lines:1.5 1.6 1.7 1.8
Port Group[3]:
#Chans supported:32512 Lines:2.1 2.2 2.3 2.4
Port Group[4]:
#Chans supported:32512 Lines:2.5 2.6 2.7 2.8
Step 7 Repeat Step 6 until you have entered information for all the cards in the switch.
Step 8 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 MGX 8850 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 |
|---|---|---|---|---|
PXM45 | Processor Switch Module | UI Stratum 3 | Upper | 7 and 8 |
PXM Hard Disk Drive | Lower | |||
AXSM-1-2488 | 1 port OC-48-STM-16 Note: no traffic shaping
| SMFSR-1-2488 | Upper | 1-6, 9-14 |
AXSM-16-155 | 16 port OC-3/ STM-1 | MMF-8-155-MT | Upper and lower | 1-6, 9-14 |
AXSM-8-155 | 8 port OC-3/STM-1 | SMB-4-155 | Upper and lower | 1-6, 9-14 |
AXSM-4-622 | 4 port OC-12/STM-4 | SMFIR-2-622 | Upper and lower | 1-6, 9-14 |
AXSM-16-T3E3 | 16 port T3/E3 | SMB-8-T3 | Upper and lower | 1-6, 9-14 |
The Cisco MGX 8850 supports redundancy between two PXM45 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:
mgx8850a.7.PXM.a > dspred
After you enter the command, the switch displays a report similar to the following:
pop2one.7.PXM.a > dspred pop2one System Rev: 02.00 Feb. 23, 2000 10:59:10 PST MGX8850 Shelf Alarm: NONE Primary Primary Primary Secondary Secondary Secondary Redundancy SlotNum Type State SlotNum Type State Type ------- ------- ------- --------- --------- --------- ---------- 7 PXM45 Active 8 PXM45 Empty Resvd 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:
mgx8850a.7.PXM.a > switchcc
Replace fromSlot with the card number that is active and replace toSlot with the card number to which you want to switch control.
Cards within the MGX 8850 V2 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:
mgx8850a.7.PXM.a > dspcds
Example 2-1 shows the display for this command. The card in slot 9 appears as either failed or empty and the card type is unknown. This is how a card appears when the firmware version has not been selected.
p2_203.7.PXM.a > dspcds p2_203 System Rev: 02.00 Apr. 09, 2000 07:18:49 GMT Backplane Serial No: SBK03060003 Backplane HW Rev: 00.00 GMT Offset 0 Statistics Master IP Address: 0.0.0.0 Shelf Alarm: NONE Card Front/Back Card Alarm Redundant Redundancy Slot Card State Type Status Slot Type --- ---------- -------- -------- ------- ----- 01 Empty --- --- --- --- 02 Empty --- --- --- --- 03 Empty --- --- --- --- 04 Empty --- --- --- --- 05 Empty --- --- --- --- 06 Empty --- --- --- --- 07 Active/Active PXM45 NONE 08 PRIMARY SLOT 08 Empty Resvd/Emp UNKNOWN_FC MAJOR 07 SECONDARY SLOT 09 Active/Active UNKNOWN_FC NONE NA NO REDUNDANCY 10 Empty --- --- --- --- 11 Empty --- --- --- --- 12 Empty --- --- --- --- 13 Empty --- --- --- --- 14 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 Cisco MGX 8850, Release 2.0.
|
Note For instructions on download and installing new firmware versions, see "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 Cisco MGX 8850, Release 2.0. 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:
mgx8850a.7.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:
mgx8850a.7.PXM.a > ll
The display shows:
p2_203.7.PXM.a > ll
size date time name
-------- ------ ------ --------
512 JAN-01-2098 00:00:00 . <DIR>
512 JAN-01-2098 00:00:00 .. <DIR>
2224872 FEB-05-2106 22:30:50 axsm_002.000.117-A1.fw
583856 FEB-05-2106 22:30:52 axsm_002.000.117-A1_bt.fw
831952 FEB-05-2106 22:30:56 pxm45_002.000.117-A1_bt.fw
3396744 FEB-05-2106 22:31:02 pxm45_002.000.117-A1_mgx.fw
2242312 JAN-01-2098 00:03:42 axsm_002.000.128-A1.fw
591072 JAN-01-2098 00:03:58 axsm_002.000.128-A1_bt.fw
839408 JAN-01-2098 00:04:08 pxm45_002.000.128-A1_bt.fw
3429272 MAR-31-2000 20:33:02 pxm45_002.000.128-A1_mgx.fw
In the file system :
total space : 819200 K bytes
free space : 799825 K bytes
Filenames that include "_mgx" are for runtime firmware, and filenames that include "_bt" are for runtime firmware. 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 | Version Number for setrev Command |
|---|---|
pxm45_002.000.001-D_mgx.fw | 2.0(1)D |
pxm45_002.000.014-A1_bt.fw | 2.0(14)A1 |
axsm_002.000.016-D.fw | 2.0(16)D |
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:
mgx8850a.7.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."
All communications between the switch and other devices are synchronized with the network clock, unless it is overridden by a line level clock. The Cisco MGX 8850, Release 2 can synchronize with the following network clock sources:
When the switch first powers up, it automatically starts using the internally-generated clock on the PXM45 as the network clock source. You can let the switch use this clock source, or you can specify primary and secondary clock sources for the switch. When primary and secondary clock sources are defined, the switch uses the primary clock source and switches over to the secondary clock source if the primary source fails. If both primary and secondary clock sources fail, the switch uses the internally-generated clock source. A revertive option allows you to configure the switch to change back to the primary clock source if it recovers (this applies only to external clock sources that are connected to the PXM45 UI back card).
In a typical network, you will configure one switch or node as the network clock source for all nodes, and you'll configure the other nodes to use that clock source as the primary clock source. You can also define a second node to serve as the secondary or backup clock source. At each node that uses remote clock sources, you configure external primary and secondary clock sources. If both external clock sources fail, the internal clock source within the switch is used.
If your switch is to be the master clock source, you might want to connect an external clock source to one or both of the two Building Integrated Timing System (BITS) ports on the PXM45 card. The clock source should be stratum 3 or higher, and it can be distributed to other nodes through lines connected to the AXSM cards.
If your switch is to receive the master clock source from another node, you can connect the line with the clock source to an AXSM card and then define that line as the clock source for the node. You can also configure a secondary AXSM line to serve as a backup clock, and the internal clock will take over if both external clocks fail.
The following sections describe how to do the following:
One command allows you to view the configured clock sources and determine which clock source is active. To view the configured clock sources, use the following procedure.
Step 2 To view the configured clock sources, enter the dspclksrcs command:
mgx8850a.7.PXM.a > dspclksrcs
|
Note The dspclksrcs command must be issued to the PXM45 card. If the switch prompt indicates that you are configuring another card, enter the cc 7 command to change to the PXM card. (Enter cc 8 if the PXM card in slot 8 is the active card.) |
The following example shows a display with neither primary nor secondary clocks configured. This is the default configuration of a switch, which is using the internal clock as the network clock source. Whenever the active clock is listed as null, the switch is using the internal clock.
popeye2.PXM.a > dspclksrcs Primary clock type: null Primary clock source: 0.0 Primary clock status: null Secondary clock type: null Secondary clock source:0.0 Secondary clock status: null Active clock: null source switchover mode:non-revertive
In the following example, the display shows that both the primary and secondary clocks are configured for network clock sources. The primary clock source is coming from port 2 on the AXSM card in slot 6. The primary clock source is active and configured for revertive operation. The secondary clock source is coming from port 3 on the AXSM card in slot 6.
POPEYE2.PXM.a> dspclksrcs Primary clock type: generic Primary clock source: 6.2 Primary clock status: good Secondary clock type: generic Secondary clock source: 6.3 Secondary clock status: good Active clock: primary source switchover mode: revertive
You can configure the switch to receive external clock sources on the PXM45 or AXSM cards. When configuring external clock sources, consider the following:
The following sections describe how to configure the switch to receive clock sources on PXM45 and AXSM cards.
The PXM45-UI-S3 back card has two connectors for receiving highly stable clocks from a dedicated, external devices. The card can support stratum levels 1-3. If primary and secondary clocks are both externally-sourced, they must be received at the same rate. For example, you cannot specify a T1 primary source and an E1 secondary source.
The PXM45 provides a revertive function that can apply when the primary clock source fails. A failure is either a loss of the signal or a clock that has drifted out of spec for its stratum. If a primary clock recovers from a failure and revertive mode is enabled, the node automatically reverts to the primary source. The restored primary clock must be available for 12 seconds before it again becomes the functioning clock source.
The following procedure describes how to configure an external clock source that is connected to the PXM45 card.
Step 2 To set a primary or secondary external clock source, enter the cnfclksrc command:
mgx8850a.7.PXM.a > cnfclksrc <priority> [shelf.]slot.port -bits {e1|t1} [-revertive {enable|disable}]
|
Note This command must be issued to the PXM45 card. If the switch prompt indicates that you are configuring another card, enter the cc 7 command to change to the PXM card. (Enter cc 8 if the PXM card in slot 8 is the active card.) |
Table 2-5 describes how to enter the parameters for this command.
| Parameter | Values | Descriptions |
|---|---|---|
priority | primary or secondary | Replace priority with the type of clock source, which is either primary or secondary. The default is primary. |
shelf | 1 | The shelf value is always 1 and is optional. |
slot | 7 | The slot number is 7 when the external clock is connected to the PXM45-UI-S3 (regardless of whether the active PXM45 is in slot 7 or 8). |
port | 35 or 36 | The port number identifies the port on the PXM45-UI-S3 to which the external clock is connected. The port number for the upper connector is 35. The port number for the lower connector is 36. |
-bits | e1 or t1 | When defining an external clock source that connects to the PXM45, you must include the bits keyword and specify whether the clock source trunk is an E1 or T1. |
-revertive | enable or disable | When defining an external clock source that connects to the PXM45 as a primary clock source, you can optionally define the clock source as revertive (enable) or nonrevertive (disable). The default is disable. |
Step 3 To configure an additional clock source, repeat Step 2 using the correct parameters for the additional source.
The following command example shows how to configure a primary E1 external clock source at the upper connector of the PXM45-UI-S3. Note the command punctuation.
mgx8850a.7.PXM.a > cnfclksrc primary 7.35 -bits e1
The next example configures a primary network clock source to revert back to the highest priority E1 clock source after the highest priority port recovers from failure.
mgx8850a.7.PXM.a > cnfclksrc primary 7.36 -bits e1 -revertive enable
The last example disables the revertive function for an E1 BITS clock.
mgx8850a.7.PXM.a > cnfclksrc primary 7.36 -bits e1 -revertive disable
To receive a clock source on an AXSM card, you must first connect a line between the AXSM and the node with the clock source, and then you must do the following:
These procedures are described in "Configuring ATM Lines and Trunks." The following procedure describes how to configure an external clock source on an AXSM card after the card has been correctly configured.
Step 2 To set a primary or secondary external clock source, enter the following command:
mgx8850a.7.PXM.a > cnfclksrc <priority> [shelf.]slot:subslot.port:subport
|
Note Although this command relates to an AXSM card, it must be issued to the PXM45 card. If the switch prompt indicates that you are configuring another card, enter the cc 7 command to change to the PXM card. (Enter cc 8 if the PXM card in slot 8 is the active card.) |
Table 2-6 describes how to enter the parameters for this command.
|
Tips To get the correct slot:subslot.port:subport specification, use the Port ID displayed by the dsppnports command. |
| Parameter | Values | Descriptions |
|---|---|---|
priority | primary or secondary | Replace priority with the type of clock source, which is either primary or secondary. The default is primary. |
shelf | 1 | The shelf value is always 1 and is optional. |
slot | 1-6, 8-14 | Enter the slot number of the AXSM card to which the external clock source is connected. |
subslot | 1 or 2 | The subslot identifies the bay in which the back card is installed. If the clock source line is connected to upper card, enter 1. If it is connected to the lower card, enter 2. The default is 1. |
port | 1-8 | The port number corresponds to the port number on the back card to which the clock source line is connected. The line connected to this port must already be active (through upln). |
subport | 1-60 | The subport number corresponds to the logical port number, which is between 1 and 60. The subport is also called an interface and must have been previously defined using the addport command. |
Step 3 To configure an additional clock source, repeat Step 2 using the correct parameters for the additional source.
The following command example shows how to configure a secondary clock source for subport (logical port) 10 on line 1 of the AXSM card in the upper bay of slot 3. Note the placement of the periods and colons.
mgx8850a.7.PXM.a > cnfclksrc secondary 3:1.1:10
Deleting a clock source deletes the definition of the clock source, not the clock source itself. You might want to delete a primary or secondary clock source definition so that you can reassign the clock source to another line.
To delete a clock source, use the following procedure.
Step 2 Display the clock source information by entering the dspclksrcs command.
You will need the information in this display to delete the clock source.
|
Note The commands in this procedure must be issued to the PXM45 card. If the switch prompt indicates that you are configuring another card, enter the cc 7 command to change to the PXM card. (Enter cc 8 if the PXM card in slot 8 is the active card.) |
Step 3 To delete an external clock source connected to a PXM45, enter the delclksrc command:
mgx8850a.7.PXM.a > delclksrc <priority> [shelf.]slot.port [bits {e1|t1}] [revertive {enable|disable}]
The parameters for this command are described in Table 2-6. The following is an example command:
mgx8850a.7.PXM.a > delclksrc primary 7.36 -bits e1 -revertive disable
Step 4 To delete an external clock source connected to a AXSM card, enter the following command:
mgx8850a.7.PXM.a > delclksrc <priority> [shelf.]slot:subslot.port:subport
The parameters for this command are described in Table 2-6. The following is an example command:
mgx8850a.7.PXM.a > delclksrc secondary 10:2.1:2
Step 5 To verify that a clock source has been deleted, enter the delclksrcs command. When the primary or secondary clock source is deleted, the clock type is set to null.
The switch monitors the clock sources and generates alarms when a clock source fails or strays out of tolerance. You can view the status of the clock sources by entering the dspclksrcs command. To display the clock source alarms, enter the dspclkalarms command. The following example shows the display that appears when both primary and secondary clock sources have failed.
mgx8850a.7.PXM.a > dspclkalarms pop2one System Rev: 02.00 Feb. 16, 2000 15:00:48 PST MGX8850 Shelf Alarm: NONE Clock Manager Alarm Summary ---------------------------- NETWORK CLOCK ALARM : LOST ALL CLOCK SOURCES - IN FREERUN MODE : MAJOR NETWORK CLOCK ALARM : LOST PRIMARY REFERENCE : MINOR Critical Major Minor 000 001 001
Each external clock source is either a primary or a secondary clock source. When you change clock sources from one line to another without changing the primary or secondary status, just enter a new cnfclksrc command as described in "Configuring External Clock Sources." The switch automatically deletes the former configuration and replaces it with the new configuration.
When changing a clock source from primary to secondary or from secondary to primary, the switch will not allow you to create two primary or two secondary clock sources. For example, if the switch is configured for both primary and secondary clock sources, you cannot change the primary clock source to secondary until you delete the existing secondary clock source.
To change the clock source on a line from primary to secondary or from secondary to primary (without changing lines), you must delete all clock sources. The switch will not allow you to configure the same line as both primary and secondary clock sources.
To delete a clock source, use the delclksrc command as described in "Deleting Clock Sources."
The revertive option for clock sources connected to the PXM45 allows a primary clock source to resume operation as the primary clock source after a failure and restoration of the signal. However, if you have this option disabled or if your primary clock source is connected to an AXSM card, you will have to redefine the primary clock source after it is restored. To redefine the clock source as a primary clock source, use the cnfclksrc command as described in "Configuring External Clock Sources."
|
Tips Use the dspclksrcs command to display the current configuration settings for the primary clock source. Having this information available makes it easier to re-enter the cnfclksrc command. |
|
Note To change a clock source on the PXM45 from non-revertive to revertive, enter the cnfclksrc with the option -revertive enable. |
When the primary clock source is restored on the master clock node, you may have to reconfigure the primary clock source at each remote node where the node has switched from the primary source to the secondary source due to a master node clock switchover. This reconfiguration is necessary only if the local node has detected a change in the master clock source.
To determine if you need to re-specify the primary clock at a non-master node, enter the dspclksrcs command. If the source has changed to either secondary or null, you must use the cnfclksrc command to redefine the primary clock source for that node.
The PNNI controller simplifies switch configuration by using the PNNI protocol to discover call routes in an ATM network. Without the PNNI controller, each route through the network would have to be defined manually. "Address Selection, Call Routing, and WAN Switching Using the PNNI Protocol," provides more information on PNNI. This section describes how to enable and configure the PNNI controller for the switch.
To enable and configure the PNNI controller, enter the following command:
mgx8850a.7.PXM.a > addcontroller <cntrlrId> i <cntrlrType> <lslot> [cntrlrName]
Table 2-7 describes the parameters for the addcontroller command.
| Parameter | Values | Descriptions |
|---|---|---|
cntrlrId | 1 to 20 | This number uniquely identifies this controller to the switch. |
cntrlrType | 2 | Enter 2 to specify a PNNI controller. |
lslot | 7 | Enter 7 to specify the PXM45 as the PNNI controller host. |
cntrlrName | text | The cntrlrName is optional.You can enter a text name to identify the PNNI controller. |
To display the PNNI controller configuration, enter the dspcontrollers command:
mgx8850a.7.PXM.a > dspcontrollers
The Cisco MGX 8850 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:
mgx8850a.7.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:
mgx8850a.7.PXM.a > dspsnmp mgx8850a System Rev: 02.00 Feb. 17, 2000 09:18:04 PST MGX8850 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 "mgx8850a" were saved on February 29th, 2000 at 2:31pm, the file would be named C:/CNF/mgx8850a_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:
mgx8850a.7.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:
mgx8850a.7.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: Mon Aug 7 08:39:32 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.