error message ssa_get_reg: ssa=0: reg=0x2C rc=0x80

[jackson.ku]

Hi,

My Catalyat 6509 have the following error message :

21:11:50.878 FW[Mod 01]: ssa_get_reg: ssa=0: reg=0x2C rc=0x80

21:27:12.443 FW[Mod 01]: ssa_get_reg: ssa=0: reg=0x2C rc=0x80

22:13:37.275 FW[Mod 01]: ssa_get_reg: ssa=0: reg=0x2C rc=0x80

22:16:58.100 FW[Mod 01]: ssa_get_reg: ssa=0: reg=0x2C rc=0x80

Please help to mention me what this message mean?

Best Regards,

Jackson

[Reza Sharifi]

Hi,

What type of line card is in slot 1?

Can you reset line card 1 and test again.

HTH

[jackson.ku]

Hi,

This line card is WiSM. We need to arrange off-hour to reset this line card.

What is this error mean?

Best Regards,

Jackson

[InayathUlla Sharieff · Accepted solution]

RegHi Jackson,

Please find the details of the error which you are seeing :

21:11:50.878 FW[Mod 01]: ssa_get_reg: ssa=0: reg=0x2C rc=0x80

21:27:12.443 FW[Mod 01]: ssa_get_reg: ssa=0: reg=0x2C rc=0x80

Details:-

SSA (Super Santa Ana) is a name of the ASIC to provide for the transfer of   parallel data in both direction between the line card and fabric.

Card running at 4 or 8Gbps speed. The above message occurs when firmware initializes the SSA but some of the registers are not accessible or the access times out.

If you'll see the message continuously, I'd recommend to reseat first to resync fabric connection.

However, the same message will be displayed after resetting then the module needs to be replaced.

HTH

Regards

Inayath

*Plz rate the helpfull posts.

[jackson.ku]

Hi Inayath,

Thanks for your kindly help.

Best Regards,

Jackson

[blackmichael]

Could it be an issue with the 6509 chassis it self?

[InayathUlla Sharieff]

No its not as of now.

HTH

[jackson.ku]

Hi,

Today this message occur again :

14:43:41.378 FW[Mod 01]: ssa_get_reg: ssa=0: reg=0x2C rc=0x80

We have reseat this module 3 months ago. Is it a critical error? Can the module recover this error automatically and we can ignore this error or we should replace this module?

Best Regards,

Jackson

[InayathUlla Sharieff]

HI Jackson,

AS suggested earlier that if we see this happens again we have to replace the module.

Please go ahead and raise the RMA for the same.

Regards

Inayath