Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

NAM module on 6509 doesn't ping via MANAGEMENT PORT

Hello,

I need some help. I have a cisco 6509 configured with a cisco NAM module. I have reset the config of the NAM module by the config clear command. Since this moment I can't no more ping the NAM module via the management port:  OK via the 127.0.0.91 address and log in ok via the ios cli session command.

I tried to ping the NAM module from the switch and vice-versa and nothing happens. the gateway is well configured on the NAM:

root@NAM-6500-R2.localdomain#  show ip
IP address:             172.31.51.11
Subnet mask:            255.255.255.0
IP Broadcast:           172.31.51.255
DNS Name:               NAM-6500-R2.localdomain
Default Gateway:        172.31.51.254
Nameserver(s):         
HTTP server:            Enabled
HTTP secure server:     Disabled
HTTP port:              80
HTTP secure port:       443
TACACS+ configured:     No
Telnet:                 Disabled
SSH:                    Disabled
root@NAM-6500-R2.localdomain# ping 172.31.51.254
PING 172.31.51.254 (172.31.51.254) 56(84) bytes of data.
From 172.31.51.11 icmp_seq=2 Destination Host Unreachable
From 172.31.51.11 icmp_seq=3 Destination Host Unreachable
From 172.31.51.11 icmp_seq=4 Destination Host Unreachable
From 172.31.51.11 icmp_seq=5 Destination Host Unreachable

--- 172.31.51.254 ping statistics ---
5 packets transmitted, 0 received, +4 errors, 100% packet loss, time 3999ms
, pipe 3
Invalid parameter!

I have already tried to reboot the module via the ios cli hw module command and nothing better.

Do you have any ideas?

Thanks by advance for any help,

best regards

1 ACCEPTED SOLUTION

Accepted Solutions

Re: NAM module on 6509 doesn't ping via MANAGEMENT PORT

Yes!

Let me know how it goes,

Merci

12 REPLIES
Community Member

Re: NAM module on 6509 doesn't ping via MANAGEMENT PORT

I have done some additional tests

on the other 6509 router with another nam module I have the following

SVT-RG1-B7-6509-R1#sh int gi 9/2 counters

Port                InOctets   InUcastPkts   InMcastPkts   InBcastPkts
Gi9/2               16173989         18170             0            58

Port               OutOctets  OutUcastPkts  OutMcastPkts  OutBcastPkts
Gi9/2               51807522         97651        444484          1530
SVT-RG1-B7-6509-R1#sh vlan id 981      

VLAN Name                             Status    Ports
---- -------------------------------- --------- -------------------------------
981  NAM                              active    Te1/2, Gi2/25, Gi2/31, Gi5/1
                                                Gi5/2, Gi9/2, Po1, Po1A

VLAN Type  SAID       MTU   Parent RingNo BridgeNo Stp  BrdgMode Trans1 Trans2
---- ----- ---------- ----- ------ ------ -------- ---- -------- ------ ------
981  enet  100981     1500  -      -      -        -    -        0      0 

Remote SPAN VLAN
----------------
Disabled

Primary Secondary Type              Ports
------- --------- ----------------- ------------------------------------------

SVT-RG1-B7-6509-R1#sh mac-address-table interface gigabitEthernet 9/2
Legend: * - primary entry
        age - seconds since last seen
        n/a - not available

  vlan   mac address     type    learn     age              ports
------+----------------+--------+-----+----------+--------------------------
Active Supervisor:
*  981  001f.ca7b.c41e   dynamic  Yes          5   Gi9/2

but on the one that doesn't works I have the following

SVT-RG1-B7-6509-R2#sh mac-address-table interface gigabitEthernet 9/2
Legend: * - primary entry
        age - seconds since last seen
        n/a - not available

  vlan   mac address     type    learn     age              ports
------+----------------+--------+-----+----------+--------------------------
No entries present.

SVT-RG1-B7-6509-R2#sh int gi 9/2 counters                          

Port                InOctets   InUcastPkts   InMcastPkts   InBcastPkts
Gi9/2                      0             0             0             0

Port               OutOctets  OutUcastPkts  OutMcastPkts  OutBcastPkts
Gi9/2                      0             0             0             0
SVT-RG1-B7-6509-R2#ping 172.31.51.111                              

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.31.51.111, timeout is 2 seconds:
...
Success rate is 0 percent (0/3)
SVT-RG1-B7-6509-R2#sh int gi 9/2 counters

Port                InOctets   InUcastPkts   InMcastPkts   InBcastPkts
Gi9/2                      0             0             0             0

Port               OutOctets  OutUcastPkts  OutMcastPkts  OutBcastPkts
Gi9/2                      0             0             0             0

I also upload the sh tech of the 6509 router that doesn't works because we have tracebacks logs and I'm afraid that it can have some interference.

thank you very much

Re: NAM module on 6509 doesn't ping via MANAGEMENT PORT

What happens when you set the default gateway to 172.31.51.253  on the NAM ?

Community Member

Re: NAM module on 6509 doesn't ping via MANAGEMENT PORT

Hello Nael Mohammad,

thanks for your response, I've tried what you've proposed but it doesn't work :

root@NAM-6500-R2.localdomain# show ip
IP address:             172.31.51.111
Subnet mask:            255.255.255.0
IP Broadcast:           172.31.51.255
DNS Name:               NAM-6500-R2.localdomain
Default Gateway:        172.31.51.254
Nameserver(s):         
HTTP server:            Enabled
HTTP secure server:     Disabled
HTTP port:              80
HTTP secure port:       443
TACACS+ configured:     No
Telnet:                 Disabled
SSH:                    Disabled
root@NAM-6500-R2.localdomain# ping 172.31.51.111
PING 172.31.51.111 (172.31.51.111) 56(84) bytes of data.
64 bytes from 172.31.51.111: icmp_seq=1 ttl=64 time=0.088 ms
64 bytes from 172.31.51.111: icmp_seq=2 ttl=64 time=0.066 ms
64 bytes from 172.31.51.111: icmp_seq=3 ttl=64 time=0.051 ms
64 bytes from 172.31.51.111: icmp_seq=4 ttl=64 time=0.066 ms
64 bytes from 172.31.51.111: icmp_seq=5 ttl=64 time=0.049 ms

--- 172.31.51.111 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4015ms
rtt min/avg/max/mdev = 0.049/0.064/0.088/0.014 ms
root@NAM-6500-R2.localdomain# ping 172.31.51.254
PING 172.31.51.254 (172.31.51.254) 56(84) bytes of data.
From 172.31.51.111 icmp_seq=1 Destination Host Unreachable
From 172.31.51.111 icmp_seq=2 Destination Host Unreachable
From 172.31.51.111 icmp_seq=3 Destination Host Unreachable
From 172.31.51.111 icmp_seq=4 Destination Host Unreachable
From 172.31.51.111 icmp_seq=5 Destination Host Unreachable

--- 172.31.51.254 ping statistics ---
5 packets transmitted, 0 received, +5 errors, 100% packet loss, time 4012ms
, pipe 3
Invalid parameter!
root@NAM-6500-R2.localdomain# ip gateway
                 - default gateway network address
root@NAM-6500-R2.localdomain# ip gateway 172.31.51.253
root@NAM-6500-R2.localdomain# show ip
IP address:             172.31.51.111
Subnet mask:            255.255.255.0
IP Broadcast:           172.31.51.255
DNS Name:               NAM-6500-R2.localdomain
Default Gateway:        172.31.51.253
Nameserver(s):         
HTTP server:            Enabled
HTTP secure server:     Disabled
HTTP port:              80
HTTP secure port:       443
TACACS+ configured:     No
Telnet:                 Disabled
SSH:                    Disabled
root@NAM-6500-R2.localdomain# ping 172.31.51.253
PING 172.31.51.253 (172.31.51.253) 56(84) bytes of data.
From 172.31.51.111 icmp_seq=1 Destination Host Unreachable
From 172.31.51.111 icmp_seq=2 Destination Host Unreachable
From 172.31.51.111 icmp_seq=3 Destination Host Unreachable
From 172.31.51.111 icmp_seq=4 Destination Host Unreachable
From 172.31.51.111 icmp_seq=5 Destination Host Unreachable

--- 172.31.51.253 ping statistics ---
5 packets transmitted, 0 received, +5 errors, 100% packet loss, time 4012ms
, pipe 3
Invalid parameter!

Do you have any other idea?

Best regards,

Community Member

Re: NAM module on 6509 doesn't ping via MANAGEMENT PORT

I discover a new thing for this problem, I think the interface between the NAM and the chassis is the 9/1 and this port is in the "not connect" status:

SVT-RG1-B7-6509-R2#sh interfaces Gi9/2 status

Port         Name               Status       Vlan       Duplex  Speed Type
Gi9/2                           notconnect   981          full   1000 NetworkAnalysis

Does this help anyone to propose me an answer?

Best regards,

Re: NAM module on 6509 doesn't ping via MANAGEMENT PORT

You might be hitting this bug and the work around is provided in the release notes . From looking at the config, all seems ok.

You can also try using a different default gateway from a different switch or vlan.

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCee10005

Community Member

Re: NAM module on 6509 doesn't ping via MANAGEMENT PORT

Hello Nael,

Thank you very much for your help. I have read the release notes and the work-around section but I didn't understand the whole thing. In my config, where is the etherchannel ? Is it the channel-group 1 Po that can causes the NAM not to communicate with the chassis?

I've tried to set up the gateway on the NAM to the IP of the other equipment in the HSRP group of the vlan 981 (172.31.21.252) but nothing has changed. I expect that changing the switching fabric mode can have a major impact on the behavio of the router?

Here are the results of the commands specified in the bug description:

SVT-RG1-B7-6509-R2#sh module
Mod Ports Card Type                              Model              Serial No.
--- ----- -------------------------------------- ------------------ -----------
  1    8  CEF720 8 port 10GE with DFC            WS-X6708-10GE      SAL1201C618
  2   48  CEF720 48 port 10/100/1000mb Ethernet  WS-X6748-GE-TX     SAL1204E9R1
  5    2  Supervisor Engine 720 (Active)         WS-SUP720-3B       SAL1202CSDK
  9    8  Network Analysis Module                WS-SVC-NAM-2       SAD132501DX

Mod MAC addresses                       Hw    Fw           Sw           Status
--- ---------------------------------- ------ ------------ ------------ -------
  1  001a.6c9f.1278 to 001a.6c9f.127f   1.3   12.2(18r)S1  12.2(33)SXH  Ok
  2  001e.1323.7c78 to 001e.1323.7ca7   2.7   12.2(14r)S5  12.2(33)SXH  Ok
  5  0019.e7d4.4348 to 0019.e7d4.434b   5.6   8.5(2)       12.2(33)SXH  Ok
  9  001f.ca7b.c37e to 001f.ca7b.c385   4.5   7.2(1)       4.0(1)       Ok

Mod  Sub-Module                  Model              Serial       Hw     Status
---- --------------------------- ------------------ ----------- ------- -------
  1  Distributed Forwarding Card WS-F6700-DFC3C     SAL1204E79M  1.0    Ok
  2  Centralized Forwarding Card WS-F6700-CFC       SAL1204DXSZ  4.0    Ok
  5  Policy Feature Card 3       WS-F6K-PFC3B       SAL1202CP2C  2.3    Ok
  5  MSFC3 Daughterboard         WS-SUP720          SAL1202CPYT  3.1    Ok

Mod  Online Diag Status
---- -------------------
  1  Pass
  2  Pass
  5  Pass
  9  Pass
SVT-RG1-B7-6509-R2# sh etherchannel summary ?
  |  Output modifiers
 

SVT-RG1-B7-6509-R2# sh etherchannel summary
Flags:  D - down        P - bundled in port-channel
        I - stand-alone s - suspended
        H - Hot-standby (LACP only)
        R - Layer3      S - Layer2
        U - in use      N - not in use, no aggregation
        f - failed to allocate aggregator

        M - not in use, no aggregation due to minimum links not met
        m - not in use, port not aggregated due to minimum links not met
        u - unsuitable for bundling
        d - default port

        w - waiting to be aggregated
Number of channel-groups in use: 1
Number of aggregators:           2

Group  Port-channel  Protocol    Ports
------+-------------+-----------+-----------------------------------------------
1      Po1(SU)         LACP      Gi2/47(P)      Gi2/48(P)     
1      Po1A(SU)        LACP      Te1/1(P)     

SVT-RG1-B7-6509-R2#sh fabric switching-mode ?
  module  switching mode of linecard modules
  |       Output modifiers
 

SVT-RG1-B7-6509-R2#sh fabric switching-mode module 9
Module Slot     Switching Mode
    9                 Crossbar

Best regards,

Re: NAM module on 6509 doesn't ping via MANAGEMENT PORT

This field notice will clear things up and explain in more detail and includes some workarounds . The data
provided indicates that crossbar mode is enabled.

http://www.cisco.com/en/US/ts/fn/610/fn61935.html

As outlined in the Field Notice, you can issue this CLI command if its supported in the IOS code listed
above:

"fabric switching-mode force busmode" and this should resolve the connectivity issue.

Re: NAM module on 6509 doesn't ping via MANAGEMENT PORT

Salut Jean-Claude,

You do have cross modules etherchannel on Ten GIG card and GI card (PO1).

Can you either remove one line card from the trunk for testing of the NAM or change the busmode and see if that helps.

Community Member

Re: NAM module on 6509 doesn't ping via MANAGEMENT PORT

Hello Lucien,

do you mean remove the Te interface from the channel group?

this way for example:

interface TenGigabitEthernet1/1
no channel-group 1 mode active

thank you,

best regards

Re: NAM module on 6509 doesn't ping via MANAGEMENT PORT

Yes!

Let me know how it goes,

Merci

Community Member

Re: NAM module on 6509 doesn't ping via MANAGEMENT PORT

Hello Lucien,

We have firstly rebooted the 6509. The IP connection with the NAM is now OK. But we have seen this log at the boot sequence:

May  5 07:49:01: %EC-SP-5-CANNOT_BUNDLE_LACP: Te1/1 is not compatible with aggregators in channel 1 and cannot attach to them (qos-card types of Te1/1 do not match Gi2/48)

So, in addition to your advices, we will remove remove the Te1/1 interface from the channel-group.

Thank you very much,

Best regards,

Jean-Christophe

Community Member

NAM module on 6509 doesn't ping via MANAGEMENT PORT

Cisco 6509:

config t:

analysis module management-port <1 or 2> access-vlan

analysis module   data-port 1 capture allowed-vlan 1-4094

analysis module   data-port 2 capture allowed-vlan 1-4094

1988
Views
0
Helpful
12
Replies
CreatePlease to create content