Problem reset Nexus 5596

Answered Question
Jan 9th, 2013

Hello,

Some equipments Nexus 5596 from a customer have reinitiated and it seems to have been provoked by an OSPF problem although I am not sure.

The logs from the equipment show:

2013 Jan  9 07:29:42 ROISBPRE2CN %BTCM-5-BTCM_LOG_L3_READY: system becomes L3 Ready

2013 Jan  9 07:29:44 ROISBPRE2CN %VSHD-5-VSHD_SYSLOG_CONFIG_I: Configured from vty by  on ppm.3726

2013 Jan  9 07:29:45 ROISBPRE2CN %OSPF-5-ADJCHANGE:  ospf-1 [3236]  Nbr 180.101.250.26 on Vlan902 went TWOWAY

2013 Jan  9 07:29:48 ROISBPRE2CN %OSPF-5-ADJCHANGE:  ospf-1 [3236]  Nbr 180.101.250.29 on Vlan902 went TWOWAY

2013 Jan  9 07:29:49 ROISBPRE2CN %OSPF-5-ADJCHANGE:  ospf-1 [3236]  Nbr 180.101.250.28 on Vlan902 went TWOWAY

2013 Jan  9 07:29:52 ROISBPRE2CN %OSPF-5-ADJCHANGE:  ospf-1 [3236]  Nbr 180.101.250.17 on Vlan902 went TWOWAY

2013 Jan  9 07:29:52 ROISBPRE2CN %OSPF-5-ADJCHANGE:  ospf-1 [3236]  Nbr 180.101.250.29 on Vlan902 went FULL

2013 Jan  9 07:29:52 ROISBPRE2CN %OSPF-5-ADJCHANGE:  ospf-1 [3236]  Nbr 180.101.250.26 on Vlan902 went FULL

2013 Jan  9 07:30:41 ROISBPRE2CN %ETHPORT-5-IF_DOWN_INITIALIZING: Interface port-channel902 is down (Initializing)

2013 Jan  9 07:30:41 ROISBPRE2CN %ETHPORT-5-IF_DOWN_INITIALIZING: Interface port-channel100 is down (Initializing)

2013 Jan  9 07:30:41 ROISBPRE2CN %ETHPORT-5-IF_DOWN_INITIALIZING: Interface Ethernet1/31 is down (Initializing)

2013 Jan  9 07:30:41 ROISBPRE2CN %ETHPORT-5-IF_DOWN_INITIALIZING: Interface Ethernet1/32 is down (Initializing)

2013 Jan  9 07:30:41 ROISBPRE2CN %ETHPORT-5-IF_DOWN_PORT_CHANNEL_MEMBERS_DOWN: Interface port-channel112 is down (No operational mem

bers)

2013 Jan  9 07:30:41 ROISBPRE2CN %ETHPORT-5-IF_DOWN_PORT_CHANNEL_MEMBERS_DOWN: Interface port-channel111 is down (No operational mem

bers)

I wanted to know if you know something about a problem with OSPF in next version:

  cisco Nexus5596 Chassis ("O2 48X10GE/Modular Supervisor")
  Intel(R) Xeon(R) CPU         with 8263880 kB of memory.
   bootflash:    2007040 kB

Kernel uptime is 0 day(s), 2 hour(s), 25 minute(s), 35 second(s)

      

System version: 5.1(3)N1(1a)

Thank you very much.

I have this problem too.
0 votes
Correct Answer by Andras Dosztal about 1 year 3 months ago
  • OSPF logs say that your switch is fully adjacent with 180.101.250.26 and .29, this means normal operation.
  • Bi-directional communication has been established between the Nexus and 180.101.250.17 and .28. They are in the middle of the OSPF neighboring process.
  • Some interfaces are initializing, and Po111 and 112 have no member ports (the channel-group <111|112> command hasn't been issued on any physical interfaces).

More information about OSPF neighbor states can be found here.

  • 1
  • 2
  • 3
  • 4
  • 5
Average Rating: 5 (1 ratings)
Correct Answer
Andras Dosztal Wed, 01/09/2013 - 04:55
  • OSPF logs say that your switch is fully adjacent with 180.101.250.26 and .29, this means normal operation.
  • Bi-directional communication has been established between the Nexus and 180.101.250.17 and .28. They are in the middle of the OSPF neighboring process.
  • Some interfaces are initializing, and Po111 and 112 have no member ports (the channel-group <111|112> command hasn't been issued on any physical interfaces).

More information about OSPF neighbor states can be found here.

stelefonico Thu, 01/10/2013 - 06:19

Hello,

Thank you very much a_dosztal. As you have said, this is normal behaviour and anything about this log should have provoked the reset of the equipment. I have looked the status of the modules and I have seen a power supply is failed, maybe this has been the origin of the problem although this shouldn't be a problem. There are redundant power supplies.

Well, thank you very much!!!! Best regards. And thank you for being so quick answering me.

Actions

Login or Register to take actions

This Discussion

Posted January 9, 2013 at 2:26 AM
Stats:
Replies:2 Avg. Rating:5
Views:825 Votes:0
Shares:0
Tags: No tags.

Discussions Leaderboard