This document summarizes the functions of the Integrated Management Controller (IMC) software Release 2.2.0.17. The document also provides a list of known problems. The document provides IMC first day of service (FDOS) procedure, and the procedures to upgrade or downgrade from Common Interface Module (CIM) to or from IMC module.

This document is intended for customer functional and operational groups and Cisco System Engineers responsible for installing/provisioning the Cisco MGX 8240 switch.

Upgrading to a New Software Release

This section describes the steps needed to upgrade an MGX 8240 chassis running with a CIM module to a chassis running IMC cards. The steps described minimize the impact to PSM cards running in the chassis. When these steps are followed, user traffic is not affected by the upgrade. Also described is the procedure for downgrading from IMC cards to a CIM module. This procedure applies to PSM version 1.1.2.10.

Note Although the upgrade will work with VCLI version 0.38, it recommended that the VCLI is upgraded to version 2.2.X before performing the upgrade.

This procedure does NOT describe the procedure for upgrading the switch software. See Appendix D of the Cisco MGX 8240 Hardware Installation Guide for details regarding upgrading switch software.

Upgrading from the CIM to the IMC

Upgrading from the CIM to the IMC requires a maintenance window. The upgrade requires from 1-2 hours per chassis to perform. During this time, the PSM cards may not be reachable via the out-of-band interface (ethernet). It is recommended that no configuration changes (other than those required by this procedure) be performed on the PSM cards while the upgrade is in progress.

For a chassis configured with redundancy, special steps are taken to ensure that the backup cards in a redundancy group do not perform an unwanted switch in. This is accomplished by setting the redundancy role of the backup card to none. Because the role of the backup will be set to none, it will not protect the primaries in its group during the IMC upgrade.

Warning Before the role of the backup is changed to none, its state must be standby. Failure to heed this warning will result in user traffic loss.

Step 1 Check to make sure the backup PSMs are in standby state.

Phys Slot	1	2	3	4	5	6	7	8	9	10	11	12	13	14	15	16
Group	-	-	-	-	-	7	7	7	7	7	-	-	-	-	-	-
Role	-	-	-	-	-	B	P	P	P	P	-	-	-	-	-	-
State	-	-	-	-	-	SB-	IS*	IS*	IS*	IS*	-	-	-	-	-	-
Log Slot	-	-	-	-	-	0	0	0	0	0					-	-

sw1[..] - VCLI>> show switch red -sname SwitchName

Switch Name: sw1

Phys Slot 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

Group

-

-

-

-

-

7

7

7

7

7

-

-

-

-

-

-

Role

-

-

-

-

-

B

P

P

P

P

-

-

-

-

-

-

State

-

-

-

-

-

SB-

IS*

IS*

IS*

IS*

-

-

-

-

-

-

Log

Slot

-

-

-

-

-

0

0

0

0

0

-

-

Note * For switch release 2.x, IS is replaced by PRO state.

Step 2 Change the role of the backup PSMs from standby to none.

sw1[..] - VCLI>> ch ces red -role n -card BackupCard -override 1

Repeat this command for all backup cards in the chassis. When the role of a backup card is changed to none, the card will reset. When all the backup cards have reset and are ready (approximately 5 minutes), verify that their roles are now none.

Step 1 Check that all the PSMs that were backups now have role none.

Phys Slot 1	2	3	4	5	6	7	8	9	10	11	12	13	14	15	16
Group	-	-	-	-	-	-	7	7	7	7	7	-	-	-	-
Role	-	-	-	-	-	-	N	P	P	P	P	-	-	-	-
State	-	-	-	-	-	-	NR	IS*	IS*	IS*	IS*	-	-	-	-
Log Slot	-	-	-	-	-	-	0	0	0	0	0	-	-	-	-

sw1[..] - VCLI>> show switch red -sname SwitchName

Switch Name: sw1

Phys Slot 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

Group

-

-

-

-

-

-

7

7

7

7

7

-

-

-

-

Role

-

-

-

-

-

-

N

P

P

P

P

-

-

-

-

State

-

-

-

-

-

-

NR

IS*

IS*

IS*

IS*

-

-

-

-

Log Slot

-

-

-

-

-

-

0

0

0

0

0

-

-

-

-

* For switch release 2.x, IS is replaced by PRO state.

Step 2 Change the primary clock source from BITS A or B to OC31 on all the primaries. Verify that the timing status of OC3-1 is good before changing the timing source. If the timing source has an error, correct the error or choose a different timing source.

sw1[..] - VCLI>> sho ces ref stat

CurrRefClk: BITS-A

BITS-A-Sts: Good BITS-B-Sts: Good OC3-1-Sts: Good OC3-2-Sts: LOS

sw1[..] - VCLI>> sho ces ref con -card CardNum

PriRef: BITS-A SecRef: BITS-B RevSwitch: Disabled ForceFreeRun: Off

sw1[..] - VCLI>> ch ces ref -prim oc31 -card CardNum

sw1[..] - VCLI>> sho ces ref con -card CardNum

PriRef: OC3-1 SecRef: BITS-B RevSwitch: Disabled ForceFreeRun: Off

Repeat this command for all of the primaries in the chassis.

Step 3 Disconnect the cables connected to CIO card. The cables are the CIM cable and BITS clock cable.

Step 4 Remove the CIO card from the rear of the chassis.

Step 5 Install the IMC IO card. Use care when installing the card so that midplane pins are not bent during the installation. If you need more information, please refer to Chapter 1 of the Cisco MGX 8240 Hardware Installation Guide.

Step 6 Install the first IMC card in the front of the chassis in slot 1A (top slot). If you need more information, please refer to Chapter 1 of the Cisco MGX 8240 Hardware Installation Guide.

Step 7 Connect a dumb terminal to the IMC IO card. The serial port is located on the rear of the chassis on the IMC IO card and is the second RJ-45 port from the top of the card.

Step 8 Perform first-day-of-service (FDOS) for the IMC card. The external IP address of the IMC card will usually be the IP address of CIM. For more information, please refer to the Cisco MGX 8240 Hardware Installation Guide.

Step 9 Move the RJ-45 ethernet connection from the CIM to the IMC IO card. The location of the ethernet port is the first port from the top on the IMC IO card.

Step 10 Install the second IMC card in the front of the chassis in slot 1B (bottom slot). There is no need to perform FDOS on the second IMC card in the chassis since it automatically derives FDOS configuration from the first card.

Step 11 Connect the BITS clock source to the IMC IO card.

Note The BITS connector pinout on the IMC card is different from the pinout on the CIO module.

Step 12 Using the VCLI, verify that the workstation can communicate with the PSM cards in the chassis. It may take up to 5 minutes before the VCLI can communicate with the PSM cards.

Phys Slot 1	2	3	4	5	6	7	8	9	10	11	12	13	14	15	16
Group	-	-	-	-	-	-	7	7	7	7	7	-	-	-	-
Role	-	-	-	-	-	-	N	P	P	P	P	-	-	-	-
State	-	-	-	-	-	-	NR	IS*	IS*	IS*	IS*	-	-	-	-
Log Slot	-	-	-	-	-	-	0	0	0	0	0	-	-	-	-

* For switch release 2.x, IS is replaced by PRO state.

Step 13 Verify that the BITS A and B clock sources are functioning properly. If there are any errors with the BITS source, correct the problem before proceeding.

sw1[..] - VCLI>> sho ces ref stat

CurrRefClk: OC3-1

BITS-A-Sts: Good BITS-B-Sts: Good OC3-1-Sts: Good OC3-2-Sts: LOS

Step 14 Change the configuration of the primary clock source for each of the primaries in the chassis back to the BITS A clock source.

sw1[..] - VCLI>> sho ces ref con -card CardNum

PriRef: OC3-1 SecRef: BITS-B RevSwitch: Disabled ForceFreeRun: Off

sw1[..] - VCLI>> ch ces ref -prim bitsa -card CardNum

sw1[..] - VCLI>> sho ces ref con -card CardNum

PriRef: BITS-A SecRef: BITS-B RevSwitch: Disabled ForceFreeRun: Off

Step 15 Change the role of the cards that were backups to role backup. When the role of a card is changed from none to backup, the card will reset.

sw1[..] - VCLI>> ch ces red -role b -card BackupCard -override 1

Repeat this command for all backup cards in the chassis. Once all backups have had their roles set to backup, wait 15 minutes (or four minutes times the number of primaries in the largest redundancy group) for all the configurations to be transferred from the primaries to the backup.

sw1[..] - VCLI>> show switch red -sname SwitchName

Switch Name: sw1

Phys Slot 1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

Group

-

-

-

-

-

-

7

7

7

7

7

-

-

-

-

Role

-

-

-

-

-

-

B

P

P

P

P

-

-

-

-

State

-

-

-

-

-

-

SB

IS*

IS*

IS*

IS*

-

-

-

-

Log Slot

-

-

-

-

-

-

0

0

0

0

0

-

-

-

-

* For switch release 2.x, IS is replaced by PRO state.

The upgrade to the IMC cards is complete.

Downgrading from the IMC to the CIM

Step 1 Check to make sure the backup PSMs are in standby state.

* For switch release 2.x, IS is replaced by PRO state.

Step 2 Change the role of the backup PSMs from standby to none

sw1[..] - VCLI>> ch ces red -role n -card BackupCard -override 1

Please ignore if an error 'SNMP Set error for Save Cfg file = -3' or 'Unable to communicate with switch (-3)' comes up from VCLI for this command as card may be already rebooting.

Step 3 Check that all the PSMs that were backups now have role none.

sw1[..] - VCLI>> show switch red -sname SwitchName

Switch Name: sw1

Phys Slot 1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

Group

-

-

-

-

-

-

7

7

7

7

7

-

-

-

-

Role

-

-

-

-

-

-

N

P

P

P

P

-

-

-

-

State

-

-

-

-

-

-

NR

IS*

IS*

IS*

IS*

-

-

-

-

Log Slot

-

-

-

-

-

-

0

0

0

0

0

-

-

-

-

* For switch release 2.x, IS is replaced by PRO state.

Step 4 Change the primary clock source from BITS A or B to OC31 on all the primaries. Verify that the timing status of OC3-1 is good before changing the timing source. If the timing source has an error, correct the error or choose a different timing source.

Repeat this command for all of the primaries in the chassis.

Step 5 Disconnect the cables connected to IMC IO card. The cables are the ethernet cable and the BITS clock cable.

Step 6 Remove the IMC IO card from the rear of the chassis.

Step 7 Remove both IMC cards (slot 1A and 1B) from the front of the chassis.

Step 8 Install the CIO card. Use care when installing the card so that midplane pins are not bent during the installation.

Step 9 If needed, perform first-day-of-service (FDOS) for the CIM module. The external IP address of the CIM module will usually be the IP address of IMC.

Step 10 Connect the RJ-45 ethernet connection in the CIM module. Connect CIM cable to the CIO card.

Step 11 Connect the BITS clock source to the CIO card. Note that the BITS connector pinout on the IMC card is different from the pinout on the CIO module.

Step 12 Using the VCLI, verify that the workstation can communicate with the PSM cards in the chassis. It may take up to 5 minutes before the VCLI can communicate with the PSM cards.

: * For switch release 2.x, IS is replaced by PRO state.

Step 13 Verify that the BITS A and B clock sources are functioning properly. If there are any errors with the BITS source, correct the problem before proceeding.

sw1[..] - VCLI>> sho ces ref stat

CurrRefClk: OC3-1

BITS-A-Sts: Good BITS-B-Sts: Good OC3-1-Sts: Good OC3-2-Sts: LOS

Step 14 Change the configuration of the primary clock source for each of the primaries in the chassis back to the BITS A clock source.

Step 15 Change the role of the cards that were backups to backup. When the role of a card is changed from none to backup, the card will reset.

sw1[..] - VCLI>> ch ces red -role b -card BackupCard -override 1

Please ignore if an error 'SNMP Set error for Save Cfg file = -3' or 'Unable to communicate with switch (-3)' comes up from VCLI for this command as card may be already rebooting.

* For switch release 2.x, IS is replaced by PRO state.

Step 16 The downgrade to the CIM module is complete.

New and Changed Information

This release provides a central management interface to the Cisco MGX 8240 product. The central management interface function was provided by the CIM before. The following functions are supported in release 2.2.0.17:

First day of service provisioning capability

Terminal server to connect to PSM CMDR

Network address translation

Temperature monitoring

Fan Status monitoring

Power Input monitoring

Alarm relay control monitoring

Management of IMC configuration

Inter-IMC health monitoring

1:1 IMC redundancy

Installation Notes

IMC First Day of Service (FDOS)

Perform First Day of Service (FDOS) on the primary IMC card via the craft port interface (serial port) to verify that the switch is ready to be managed by the Network Management System.

Before starting FDOS, you need the following:

A VT-100 terminal or PC equipped with terminal emulator software.
Standard (straight) RS232 cable with RJ45 connector (supplied).
The IP addresses of the NMS stations that need to receive traps.
Time of day.
Time zone the switch will be set to (including whether or not the switch will be on Daylight Savings Time).
Chassis IP address.
IP address of gateway router.
Netmask for IP address of switch.

Installing IMC

Install the front IMC card in slot 1A (top shelf). Leave the second IMC card on slot 1B uninstalled while FDOS is performed on the primary IMC card.

Making an RS232 Terminal Connection

Step 1 Use the RS232 DCE RJ45 Connector to connect the cable between the VT-100 terminal and IMC's Craft Interface (serial port on the IMC IO back card, second from the top).

Step 2 Configure the terminal device for VT-100 with a baud rate of 9600 (8,N,1).

Craft Interface

The Craft Interface/Console Management Diagnostic Resource (CMDR or Commander) is the menu-based tool available to set up FDOS. The menu-based tool is easily invoked when a user logs in through the serial port into the IMC. CMDR is menu based and several menus are available.

To set up the Craft Interface/CMDR, connect your VT-100 terminal (or laptop) via the RS-232c cable to the serial port on the module.

To begin FDOS, perform the following steps:

Step 1 Enter CMDR and press <Enter>.

Step 2 Enter your username and password on the Login menu (Default is sysadmin/sysadmin).

Step 3 To display the menu mode, enter menu.

Node Configuration

This first screen will have four options (Node Setup, Administration, Help, Exit). Node Setup will be highlighted. Press <Enter>.

Under Node Setup you will have two options: Node Config and SNMP Configuration. Node Config will be highlighted. Press Enter.

You will get a Node Configuration screen that requires you to fill in information on the following:

system location
system name
IP address
ethernet subnet mask
ethernet default gateway.

When those are set, press shift + F1 to enter data.

You will get a Node Configuration screen that asks if you want to update the parameters now. Use the arrow key to highlight Yes. Press <Enter>.

You will get a screen that asks if you want to reboot now. Highlight Yes and press <Enter> to Reboot the IMC card.

Manager/Trap Reporting

Step 1 Enter login name and password to login to the commander. Type menu to get

to the menu mode.

Step 2 You will see two options: Manager/Trap Reporting and Community Information. Manager/Trap Reporting will be highlighted. Press Enter.

Step 3 In the NMS Trap Report Screen, New will be highlighted. Press <Enter>.

You will get the New Manager screen, which asks for the IP address of the chassis

that will receive traps. Enter IP address.

Step 4 You will get a screen which asks if you want to send the traps to the address.

Select Yes.

Step 5 Enter the port number to which traps are sent (default is 162).

Indicate whether the trap community is private or public. Press <shift + F1>.

Step 6 You will see the SNMP Config screen again. Use the arrow key to highlight

Community Information. Press <Enter>.

Step 7 You will get the "Community String Access" screen. New will be highlighted. Press <Enter>. You will get the "New Community String" screen. Fill in the name of the community string

(such as public or private). Press <Shift + F1>.

Step 8 You will get a screen that asks if you want to allow GETs, SETs, and TRAPs. The default answers are

all yes. Select Yes or No, and press <Shift + F1>.

Step 9 Press <Esc> to return to the main menu window. With the arrow keys, highlight Administration. Press <Enter>.

Step 10 You will get a screen with two options: Set System Time and Operator Access. Set System Time will be highlighted. Press <Enter>.

Step 11 You will get a screen that asks for information on the system date, time, and time zone. Set them, and press <Shift + F1>.

Step 12 To reboot, use the <Esc> key to get back to the main menu. Use the arrow key to highlight the Exit option, and press <Enter>.

Step 13 IMCCMDR> oper reboot

After FDOS is performed on the primary IMC, installing the secondary IMC automatically derives FDOS configuration from the primary. The user does not have to perform FDOS on the secondary card.

Caveats

The following known problems have been fixed and/or verified in the IMC Release 2.2.0.17:

DDTS Number	Severity	Affects	Caveat
CSCdr15813	severe	Network Address Translation	NAT dynamic port numbers could use predefined port numbers.
CSCdr20266	severe	Network Address Translation	NAT did not create multiple entries for multiple trap receivers.

Open Caveats - Release 2.2.0.17 IMC Software

Cisco MGX 8240 IMC software (Release 2.2.0.17) has some known problems. Every attempt has been made to address and resolve the problems of high severity. Below are the lists of known bugs that exist in the IMC. This list includes all outstanding problems related to the IMC modules and associated I/O ports.

DDTS Number	Severity	Affects	Caveat	Workaround
CSCdp03325	cosmetic	FDOS	When the time or timezone is changed on FDOS menu, asking the user to reboot IMC is unnecessary.
CSCdp14532	moderate	SNMP agent	IMC software displays the LED status of the front card when NMS/VCLI queries the LED status of the IMC IO backcard. The software should not display any LED status since there is no LED on the IMC IO backcard.
CSCdp01746	severe	CMDR	Changing IP address followed by adding a community string on the commander via craft port can cause the IMC card to hang.	Change IP and reboot IMC right away.
CSCdm95292	minor	VxWorks socket	ftp sessions will fail if switchover to standby IMC occurs.	Restart the ftp session.

Cisco Connection Online

Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.

Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.

CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.

You can access CCO in the following ways:

WWW: http://www.cisco.com
WWW: http://www-europe.cisco.com
WWW: http://www-china.cisco.com
Telnet: cco.cisco.com
Modem: From North America, 408 526-8070; from Europe, 33 1 64 46 40 82. Use the following terminal settings: VT100 emulation; databits: 8; parity: none; stop bits: 1; and connection rates up to 28.8 kbps.

For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.

Note If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or cs-rep@cisco.com.

Documentation CD-ROM

Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.

If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.

This document is to be used in conjunction with the documents listed in the "Related Documentation" section.

Access Registrar, AccessPath, Any to Any, AtmDirector, Browse with Me, CCDA, CCDE, CCDP, CCIE, CCNA, CCNP, CCSI, CD-PAC, the Cisco logo, Cisco Certified Internetwork Expert logo, CiscoLink, the Cisco Management Connection logo, the Cisco NetWorks logo, the Cisco Powered Network logo, Cisco Systems Capital, the Cisco Systems Capital logo, Cisco Systems Networking Academy, the Cisco Systems Networking Academy logo, the Cisco Technologies logo, ConnectWay, Fast Step, FireRunner, Follow Me Browsing, FormShare, GigaStack, IGX, Intelligence in the Optical Core, Internet Quotient, IP/VC, Kernel Proxy, MGX, Natural Network Viewer, NetSonar, Network Registrar, the Networkers logo, Packet, PIX, Point and Click Internetworking, Policy Builder, Precept, RateMUX, ScriptShare, Secure Script, ServiceWay, Shop with Me, SlideCast, SMARTnet, SVX, The Cell, TrafficDirector, TransPath, ViewRunner, Virtual Loop Carrier System, Virtual Voice Line, VlanDirector, Voice LAN, Wavelength Router, Workgroup Director, and Workgroup Stack are trademarks; Changing the Way We Work, Live, Play, and Learn, Empowering the Internet Generation, The Internet Economy, and The New Internet Economy are service marks; and Aironet, ASIST, BPX, Catalyst, Cisco, Cisco IOS, the Cisco IOS logo, Cisco Systems, the Cisco Systems logo, the Cisco Systems Cisco Press logo, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub, FastLink, FastPAD, FastSwitch, GeoTel, IOS, IP/TV, IPX, LightStream, LightSwitch, MICA, NetRanger, Post-Routing, Pre-Routing, Registrar, StrataView Plus, Stratm, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. or its affiliates in the U.S. and certain other countries. All other trademarks mentioned in this document are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any of its resellers. (0004R)

Phys Slot 1	2	3	4	5	6	7	8	9	10	11	12	13	14	15	16
Group	-	-	-	-	-	-	7	7	7	7	7	-	-	-	-
Role	-	-	-	-	-	-	B	P	P	P	P	-	-	-	-
State	-	-	-	-	-	-	SB	IS*	IS*	IS*	IS*	-	-	-	-
Log Slot	-	-	-	-	-	-	0	0	0	0	0	-	-	-	-

Table of Contents