Hi Rakesh,The config-register

nijacob · ‎03-30-2015

Hi,

I have a Cisco CAT6K switch (WS-C6506-E) and a SUP 720 engine installed on the slot 5.

I would like to know whether this Supervisor Engine 720, currently on slot 5 be changed to slot 6 and if so, does it require any configuration change?

Regards,
Nithin.

Jon Marshall · ‎04-01-2015

I would like to know whether this Supervisor Engine 720, currently on slot 5 be changed to slot 6 and if so, does it require any configuration change?

Why do you want to do that ?

Jon

nijacob · ‎04-02-2015

Hi Jon,

The CAT6K frequently goes into the ROMMON mode and as per the recommendation from the Cisco TAC, they asked to change the SUP Engine from slot 5 to slot 6, due to some Fabric Interconnect errors. So wanted to try this.

Regards,
Nithin.

Jon Marshall · ‎04-02-2015

Nithin

Okay, that makes sense.

You should be fine to move it and it shouldn't require any additional configuration.

Jon

nijacob · ‎04-02-2015

Thanks a lot Jon for your reply.

Do you have any idea of, why the switch is going to the ROMMON mode automatically.
Is it because of the hardware problem or due to the software crashes..?

CAT6K-SW01#sh rom-monitor slot 6 rp
Region F1: INVALID
Region F2: INVALID
Currently running ROMMON from S (Gold) region

CAT6K-SW01#sh rom-monitor slot 6 sp
Region F1: INVALID
Region F2: INVALID
Currently running ROMMON from S (Gold) region

Please do share your thoughts.

Regards,
Nithin

Jon Marshall · ‎04-02-2015

Nithin

Depends what you mean by automatically.

If the switch is dropping into ROMMON when it is up and running then you have a problem.

If when you boot it up it goes to ROMMON it could just be that you haven't told it which IOS image to boot.

That would depend on two things -

1) the configuration register

and

2) the "boot system ..." command

Jon

nijacob · ‎04-02-2015

Jon,

Automatic in the sense, the switch would be running fine for some days and when we get a message that the network is down and when the switch is checked it will be in the ROMMON mode.
CAT6K-SW01#sh bootvar
BOOT variable = sup-bootdisk:,1;
CONFIG_FILE variable does not exist
BOOTLDR variable =
Configuration register is 0x2102

SPP-CAT6K-SW01#sh sup-bootdisk:
-#- --length-- -----date/time------ path
1 33554432 Apr 11 2011 09:03:30 +00:00 sea_console.dat
2 71094564 Apr 11 2011 09:06:34 +00:00 s72033-ipservicesk9-mz.122-33.SXI5.bin

Doubt, the RP is crashing and causing the switch to be in ROMMON mode.

Regards,
Nithin.

Jon Marshall · ‎04-02-2015

Nithin

If the switch is dropping into ROMMON while up and running then yes it may well be worth trying the other slot to see if that fixes it.

Is that the main issue ie. you are not trying to get it simply to automatically reboot ?

Jon

Madhukrishnan Gopinathan Nair · ‎04-03-2015

I agree with Jon. I see an earlier note that you saw fabric errors, it would be worth to check in slot6.

If you can share the recent crashinfo file i can take a look at it.

Also as a best practice set the boot variable(you dont have at the moment.)

Further to that you may please check SP config reg value too ensure that it is 2102.(if it is not, everytime it crashes, switch may go to rommon)

remote command switch sh ver

HTH,

Thanks,

Madhu.

rakeshvelagala · ‎04-02-2015

Hi,

we had same issue on sup 720. We did the following which resolved the issue.

once in rommon, set the config register and reset it.

rommon 1 >confreg 0x2102

nijacob · ‎04-02-2015

Hi Rakesh,

The config-register is already set to 0x2102.

Nithin.

rakeshvelagala · ‎04-02-2015

Hi Yes

Though it is already set, we need to manually do the command in the rommon.

rakeshvelagala · ‎04-02-2015

Oh ok. Sorry understood you question wrongly.

1)So say if you reload the switch manually, will it come back up normally?

2)Can you please post # dir all file-systems (Cannot remember the exact command).

to check if there is any crashinfo file in others.

Thanks

nijacob · ‎04-02-2015

Hi Rakesh,

Yes, if I reload the switch, it comes up normally.

CAT6K-SW01#dir all-filesystems

Directory of system:/

2 -r-- 0 <no date> default-running-config
3 dr-x 0 <no date> memory
1 -rw- 20812 <no date> running-config
13 dr-x 0 <no date> vfiles

No space information available
Directory of tmpsys:/

6 drw- 0 <no date> eem_lib_system
5 drw- 0 <no date> eem_lib_user
37 -rw- 0 <no date> eem_pnt_0
39 -rw- 0 <no date> eem_pnt_1
57 -rw- 0 <no date> eem_pnt_10
59 -rw- 0 <no date> eem_pnt_11
61 -rw- 0 <no date> eem_pnt_12
63 -rw- 0 <no date> eem_pnt_13
65 -rw- 0 <no date> eem_pnt_14
67 -rw- 0 <no date> eem_pnt_15
41 -rw- 0 <no date> eem_pnt_2
43 -rw- 0 <no date> eem_pnt_3
45 -rw- 0 <no date> eem_pnt_4
47 -rw- 0 <no date> eem_pnt_5
49 -rw- 0 <no date> eem_pnt_6
51 -rw- 0 <no date> eem_pnt_7
53 -rw- 0 <no date> eem_pnt_8
55 -rw- 0 <no date> eem_pnt_9
4 drw- 0 <no date> eem_policy
8 drw- 0 <no date> eem_pub
36 -rw- 0 <no date> eem_rpc_0
38 -rw- 0 <no date> eem_rpc_1
56 -rw- 0 <no date> eem_rpc_10
58 -rw- 0 <no date> eem_rpc_11
60 -rw- 0 <no date> eem_rpc_12
62 -rw- 0 <no date> eem_rpc_13
64 -rw- 0 <no date> eem_rpc_14
66 -rw- 0 <no date> eem_rpc_15
40 -rw- 0 <no date> eem_rpc_2
42 -rw- 0 <no date> eem_rpc_3
44 -rw- 0 <no date> eem_rpc_4
46 -rw- 0 <no date> eem_rpc_5
48 -rw- 0 <no date> eem_rpc_6
50 -rw- 0 <no date> eem_rpc_7
52 -rw- 0 <no date> eem_rpc_8
54 -rw- 0 <no date> eem_rpc_9
7 drw- 0 <no date> eem_temp
1 dr-x 0 <no date> lib

No space information available
Directory of flexwan-fpd:/

0 dr-- <no size> <no date>

No space information available
Directory of bootflash:/

1 -rw- 16083 Dec 6 2013 10:32:23 +00:00 cat6k-sw01-confg
2 -rw- 357579 Feb 6 2014 12:11:09 +00:00 crashinfo_20140206-121109-GMT
3 -rw- 302748 Feb 6 2014 11:56:20 +00:00 crashinfo_20140206-115620-GMT
6 -rw- 1210 Apr 3 2014 12:57:27 +00:00 bootup.cfg
7 -rw- 327751 Jan 24 2015 05:41:35 +00:00 crashinfo_20150124-054135-GMT
8 -rw- 311305 Jan 24 2015 05:21:12 +00:00 crashinfo_20150124-052112-GMT
9 -rw- 344631 Feb 17 2015 13:16:53 +00:00 crashinfo_20150217-131653-GMT
10 -rw- 320713 Feb 17 2015 13:20:00 +00:00 crashinfo_20150217-132000-GMT
11 -rw- 359965 Mar 3 2015 15:38:46 +00:00 crashinfo_20150303-153846-GMT
12 -rw- 306904 Mar 3 2015 15:42:01 +00:00 crashinfo_20150303-154201-GMT
13 -rw- 401966 Mar 19 2015 00:24:25 +00:00 crashinfo_20150319-002425-GMT
14 -rw- 316930 Mar 19 2015 00:27:37 +00:00 crashinfo_20150319-002737-GMT

65536000 bytes total (62163980 bytes free)
Directory of disk1:/

1 -rw- 9269 Oct 5 2012 10:06:18 +00:00 05-Oct-2012.cfg
2 -rw- 0 Mar 18 2013 07:23:52 +00:00 ace-180313
3 -rw- 916 Aug 14 2013 08:14:44 +00:00 sre-v-k9.smv.1.0.2.key
4 -rw- 7 Aug 14 2013 08:49:46 +00:00 test.txt

512098304 bytes total (512065536 bytes free)
Directory of sup-bootdisk:/

1 -rw- 33554432 Apr 11 2011 09:03:30 +00:00 sea_console.dat
2 -rw- 71094564 Apr 11 2011 09:06:34 +00:00 s72033-ipservicesk9-mz.122-33.SXI5.bin
3 -rw- 33554432 Apr 11 2011 16:28:22 +00:00 sea_log.dat
4 -rw- 5610 Jun 1 2011 11:42:16 +00:00 01jun2011.cfg
5 -rw- 200465 Jun 29 2011 14:32:16 +00:00 debuginfo_20110629-143214-UTC
6 -rw- 381102 Feb 6 2014 12:11:08 +00:00 crashinfo_20140206-121109-GMT
7 -rw- 408951 Jan 24 2015 05:41:34 +00:00 crashinfo_20150124-054135-GMT
8 -rw- 377856 Feb 17 2015 13:16:52 +00:00 crashinfo_20150217-131653-GMT
9 -rw- 371842 Mar 3 2015 15:38:46 +00:00 crashinfo_20150303-153847-GMT
10 -rw- 392284 Mar 19 2015 00:24:24 +00:00 crashinfo_20150319-002425-GMT

1024557056 bytes total (884146176 bytes free)
Directory of sup-microcode:/

0 dr-- <no size> <no date>
1 -r-- 23852114 <no date> DRACO2_MP
2 -r-- 9331982 <no date> CHEVYS-LC
3 -r-- 11309986 <no date> C2LC
4 -r-- 10805714 <no date> SPLC
5 -r-- 333568 <no date> LCP_LX10100
6 -r-- 303500 <no date> LCP_LX1000
7 -r-- 325646 <no date> LCP_AX1000
8 -r-- 376656 <no date> LCP_AX10100
9 -r-- 366718 <no date> LCP_CPFAB
10 -r-- 747470 <no date> LCP_CPGBIT
11 -r-- 483470 <no date> LCP_CP10G
12 -r-- 809230 <no date> LCP_CPMBIT2
13 -r-- 896238 <no date> LCP_CPMBIT
14 -r-- 1274158 <no date> LCP_CPXBIT
15 -r-- 65318 <no date> LCP_ABOOT
16 -r-- 60490 <no date> LCP_BOOT

61342258 bytes total (0 bytes free)
Directory of const_nvram:/

1 -rw- 2716 <no date> vlan.dat

129004 bytes total (126288 bytes free)
Directory of nvram:/

1918 -rw- 20812 <no date> startup-config
1919 ---- 1964 <no date> private-config
1920 -rw- 20812 <no date> underlying-config
1 ---- 141 <no date> persistent-data
2 ---- 0 <no date> rf_cold_starts
3 -rw- 4545 <no date> ifIndex-table

1964024 bytes total (1934028 bytes free)
Directory of dfc#2-bootflash:/

No files in directory

15990784 bytes total (15990784 bytes free)
Directory of dfc#3-bootflash:/

1 -rw- 256881 Apr 1 2015 19:02:10 +00:00 crashinfo_20150401-190210-GMT

15990784 bytes total (15733772 bytes free)

rakeshvelagala · ‎04-02-2015

There are crashinfo files generated. Extract them and send them to TAC. They will be able to help you to check if hardware or software caused the crash.

Changing the SUP720 on WS-C6506-E from slot 5 to slot 6