VSP9K Datapath heartbeat failure on ports

[atascoman]

We have a new VSP9000 that out of the blue disabled several ports on a couple of the 9024XL cards. Most of the ports were connected to new Aruba wireless controllers and one of the ports is part of an MLT going over to their remaining 8600 chassis. When we tried to renable the ports they would not reset and then I tried it in the CLI and got a message saying the the ports would remain out of service due to a data path heartbeat failure.

I found a patch on the Avaya support site that pertained to this, applied it and follows the instructions explicitly. Still no change. Tried reseating the cards as well. The only way to clear it was to reboot the VSP9K. I am trying to get an SR opened with Avaya. I wanted to see if anyone else has seen this before and can help me figure out what could cause this and how to properly fix it without having to reset the whole VSP..

 

[atascoman]

This is a known issue. Avaya recommends upgrading to 3.3.3.0.

 

[atascoman]

FOllow up. 3.3.3.0 did not fix the issue. You have to perform a special procedure to reset the port. Avaya is still working on the issue at the design level. Since the procedure requires special passwords I probably shouldn't list them on here... sorry folks. I will ask Avaya TAC if there is an issue with posting those passwords. If not I will post them to this thread. You have to go into debug mode and then into the shell and then run a command to clear the error. Here is the basic process.

reset the slot
enter debug mode
enter the shell
run this command
-> smartioDpHeartbeatStatusUpdate(<index>, 4, 1)

( where, index is the port index num of the first port of the lane, which can be found in show tech. In your case it should be 340)
-> exit

Now bounce the port

# config t
(config)# interface gigabitEthernet slot/port
(config-if)# shut
(config-if)# no shut