Octapid Error

[gilbb9]

8616SX Ports 4/7 and 4/8 brought down administratively due to excessive OPID resets. Can anyone explain what this error means also see exctract from log

CPU5 [09/29/09 13:41:11] HW WARNING opCheckGigOctaPid: Octapid Reset OpId = 27
CPU5 [09/29/09 13:41:11] SNMP INFO Link Down(4/7)
CPU5 [09/29/09 13:41:11] SNMP INFO Port 4/7 is a trunk port
CPU5 [09/29/09 13:41:11] SNMP INFO Link Down(4/8)
CPU5 [09/29/09 13:41:11] SNMP INFO Port 4/8 is a trunk port

These ports were down for about 30min but back up. These ports have not been down since then any ideas?

 

[anthonyanderberg]

I think we've all seen the occasional OctaPid or tmux reset, but I don't recall anyone that has had ports going down and recover later. If this an 8616 module? I think they have one OctaPid controlling two Gig ports, and it would be ports 7 and 8 so an OctaPid failure would cause what you saw.

I guess my advice would be to see what Nortel says and push for them to replace the module if anything similar happens again. Nortel also has 'backdoor' commands that can uncover more debugging information, you might see ask if that can uncover anything more.

Here's some of our previous threads that might be helpful in your understanding:

http://www.tek-tips.com/viewthread.cfm?qid=1451513

http://www.tek-tips.com/viewthread.cfm?qid=1362222

http://www.tek-tips.com/viewthread.cfm?qid=1422932

http://www.tek-tips.com/viewthread.cfm?qid=855239

http://www.tek-tips.com/viewthread.cfm?qid=1132884

Good luck,
anthony

 

[gilbb9]

Thanks for the info, yes the module is an 8618sx im just a little confused about something what is an OctaPid?

 

[andy88]

There are eight OctaPid's per slot. So if it's a 16 port card there is one OctaPid per 2 ports. If it's a 48 port card then one OctaPid per 6 ports. Octapid's are basically an asic.

Opid=27 would refer to slot4

slot1 0-7
slot2 8-15
slot3 16-23
slot4 24-31
5 & 6 no Opid
slot7 32-39
slot8 40-47
slot9 48-55
slot10 56-63

The switch monitors read/writes of records and traffic if it sees an inconsistency it can reset an Octapid to try and lear the problem.

A single reset shouldn't be much to worry about. If you start to see alot, try re-seating the card. If that doesn't work it may be a hardware issue and need the card swapping.