NAM-1 login problem

[skiran]

Hi

Recently installed 2 6509 switches with native IOS running software version 12.1(13) E9 Early Deployment on both. Am using NAM-1 module with a software version 2.2(1a) on the 9th slot of both the switches. The problem is i cant login to these modules on both the switches..

6509-1#session slot 9 processor 1

The default escape character is Ctrl-^, then x.

You can also type 'exit' at the remote prompt to end the session

Trying 127.0.0.91 ...

% Connection timed out; remote host not responding

What could be the reason ? i checked the Cisco site ,checked the software says the 2.2(1a) can go with 12.1(13)E onwards... I even changed the slot but in vain..i gave a full memory reset (hw-module module 9 reset memory full-test) but in vain.Without the IP address i cant launch the NAM traffic analyzer...Can anyone help me on this...Cisco site does'nt have a answer for this on thier site..

Regards

Shashi

[scottmperry]

Shashi,

Can you do a "sho mod" to double check the status of the NAM? Just want to verify that before replying to your issue.

Thanks

[skiran]

Hi

Thanks for replying...The sh module recognisez the NAM module

eghq-dsw-1>sh module

Mod Ports Card Type Model Serial No.

--- ----- -------------------------------------- ------------------ -----------

1 2 Catalyst 6000 supervisor 2 (Active) WS-X6K-SUP2-2GE SAL0732J77G

3 16 SFM-capable 16 port 1000mb GBIC WS-X6516-GBIC SAL0733K108

4 16 SFM-capable 16 port 1000mb GBIC WS-X6516-GBIC SAL0733K2NY

5 16 SFM-capable 16 port 1000mb GBIC WS-X6516-GBIC SAL0733JMKF

6 48 48-port 10/100 mb RJ45 WS-X6148-RJ-45 SAL0732J18Q

7 16 SFM-capable 16 port 10/100/1000mb RJ45 WS-X6516-GE-TX SAL0728GK2P

9 3 Network Analysis Module WS-SVC-NAM-1 SAD0725037T

Mod MAC addresses Hw Fw Sw Status

--- ---------------------------------- ------ ------------ ------------ -------

1 0008.7dc9.dd60 to 0008.7dc9.dd61 4.3 6.1(3) 7.5(0.6)HUB1 Ok

3 000d.bd5a.6ae0 to 000d.bd5a.6aef 5.5 6.3(1) 7.5(0.6)HUB1 Ok

4 000d.bd5a.6af0 to 000d.bd5a.6aff 5.5 6.3(1) 7.5(0.6)HUB1 Ok

5 000d.bd5a.5cd0 to 000d.bd5a.5cdf 5.5 6.3(1) 7.5(0.6)HUB1 Ok

6 000d.bd0d.a884 to 000d.bd0d.a8b3 1.3 5.4(2) 7.5(0.6)HUB1 Ok

7 000d.6532.0690 to 000d.6532.069f 2.5 6.3(1) 7.5(0.6)HUB1 Ok

9 0003.feab.e6d8 to 0003.feab.e6df 2.0 7.2(1) 2.2(1a) Ok

Mod Sub-Module Model Serial Hw Status

--- --------------------------- --------------- --------------- ------- -------

1 Policy Feature Card 2 WS-F6K-PFC2 SAL0732J8UX 3.4 Ok

1 Cat6k MSFC 2 daughterboard WS-F6K-MSFC2 SAL0731HQ7D 2.5 Ok

Mod Online Diag Status

--- -------------------

1 Pass

3 Pass

4 Pass

5 Pass

6 Pass

7 Pass

9 Pass

Everything seems to be ok in the insertion of the module

Pleease throw some light on this

Regards

shashi

[jolmo]

Have you configured VLANs for Catalyst? Have you configured VLAN1? Maybe I'm wrong, but perhaps, configuring VLAN1 in Catalyst could solve your problem. (I think NAM belongs to VLAN1 by default).

HTH

[skiran]

Hi

thanks for ur reply...I cant create Vlan 1...its created by default...and i can see that the 2 ports of the NAM are in VLAN 1...and VLAN 1 is up...so it seems that even CISCO doenst have a answer for this

Regards

Shashi

[scottmperry]

Shashi,

Try resetting the nam and booting to the maintenance image.

switch# hw-module module 9 reset cf:1

You can boot the NAM to either the application image or the maintenance image by using "cf:1" (maint) or "hdd:1" (application).

Once it's back up, you can just try to ping 127.0.0.91 (the ip address the session command tries to telnet to). sometimes it's quicker than waiting for the session to time out.

[skiran]

Hi

Thanks once again for ur reply...I tried doin all these things before posting the message...I tried booting though maintainence image & application image..Even then i cant do anything...Though i can ping 127.0.0.91 from the switch CLI i cant telnet it also (telnet 127.0.0.91). ..So how to go abt it now ? Do u think the software inamge on the Switch & the NAM module is not compatible,should i upgrade the NAM module software to 3.1 ? Also how do i check whether the NAM module has booted into application or maintainence image ?

waiting for ur reply

Thanks

Shashi

[scottmperry]

So you can ping 127.0.0.91 but you can't telnet to it.

Do you have any ACL's that deny telnet??

In order to upgrade the software on the NAM, you have to telnet to it. I don't think there is any other way to upgrade it.

Based on the info you provided, all the software and hardware should work together. As a matter of fact all the versions you're running are the same as mine, except it looks like I have a NAM-1 and you have a NAM-2.

You can run the below command to check which image has been booted by the name.

switch# sho boot device module 9

[skiran]

Hi

There is no acl which is preventing telnet to go through...Even i have NAM-1 not NAM -2 & if i run that command i cant see anything

6509-1>sh boot device module 9

[mod:9 ]:

6509-1>

What could be the problem ??

waiting for ur reply

Sumeeth

[skiran]

Hi All

Can anybody from Cisco help me on this issue ? Or should i log a TAC case ?

Regards

Shashi

[skiran]

Hi

The maintainence image is 1.1(1)m & the application image is 2.2(1)a is this right ?

Waiting for ur reply

Nagu

[skiran]

Hi All

Any Updates on this issue ? All suggestions are welcome....Please update on this

regards

shashi

[scottmperry]

.