cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
536
Views
0
Helpful
1
Replies

Nexus 3550-F Module X

war202994
Level 1
Level 1

Good day

I have a quick question well maybe not so quick but I have a layer 1 switch, a Nexus 3550-F this morning it was unreachable

but the odd thing is I was able to ssh to the switch.  When I logged onto the switch we see the following error message:

 

*Error Message from CLI*

{noformat}WARNING: Mux object "corvil-a" disabled: Switch, mux or fastmux module function required
WARNING: Mux object "corvil-b" disabled: Switch, mux or fastmux module function required
WARNING: Mux object "corvil-c" disabled: Switch, mux or fastmux module function required
WARNING: Mux object "corvil-d" disabled: Switch, mux or fastmux module function required{noformat}

 

show module x
Error: Invalid module

 

*Error Message from Log*

{noformat}2022-01-18 10:10:39.669 [exalinkd,error] gps_ubxm8: Received NMEA message with invalid checksum: [$GPGSV
2022-01-18 10:10:55.501 [exalinkd,error] gps_ubxm8: Received NMEA message with invalid checksum: [$GNRMC,,V,,,,022-01-18 10:11:19.512 [exalinkd,error] gps_ubxm8: Received NMEA message with invalid checksum: [$GNRMC,,V,,,,
2022-01-18 10:11:20.471 [exalinkd,error] gps_ubxm8: Received NMEA message with invalid checksum: [$GNGLLGNRMC,,V,,,,,,,,,,N*4D]
2022-01-18 10:11:21.471 [exalinkd,error] gps_ubxm8: Received NMEA message with invalid checksum: [$GNGLL,,,,,,V,N*7RMC,,V,,,,,,,,,,N*4D]
2022-01-18 10:14:47.703 [exalinkd,error] gps_ubxm8: Received NMEA message with invalid checksum: [$GLGSV,1,1,0SH{noformat}

 

After power cycling it and rebooting via the CLI it appears to be ok now.  Before we did all that noticed the following

Does this mean that the Module is flakily or about to  die?

 

Jan 18 07:50:25 localhost kernel: RPC: Registered named UNIX socket transport module.
Jan 18 07:50:25 localhost kernel: RPC: Registered udp transport module.
Jan 18 07:50:25 localhost kernel: RPC: Registered tcp transport module.
Jan 18 07:50:25 localhost kernel: RPC: Registered tcp NFSv4.1 backchannel transport module.
Jan 18 07:50:25 localhost kernel: brd: module loaded
Jan 18 07:50:25 localhost kernel: loop: module loaded
Jan 18 07:50:25 localhost kernel: ExaLINK Fusion kernel module loaded
Jan 18 07:50:25 localhost systemd-modules-load[81]: Inserted module 'exalink_fusion'
Jan 18 07:50:25 localhost systemd-modules-load[81]: Inserted module 'mdio'
Jan 18 07:50:25 localhost kernel: MDIO userspace module loaded
Jan 18 07:50:33 localhost exalinkd[382]: module: Initializing module X
Jan 18 07:50:33 localhost exalinkd[382]: module: Module temperature: 33 C 35 C
Jan 18 07:50:33 localhost exalinkd[382]: module: Module X serial number is UNKNOWN, build date 20160815
Jan 18 07:50:33 localhost exalinkd[382]: module: Enabling module X power
Jan 18 07:50:43 localhost exalinkd[382]: module: Timeout waiting for module serial device
Jan 18 07:50:43 localhost exalinkd[382]: exalink: Restarting hardware init because module init failed
Jan 18 07:50:45 localhost exalinkd[382]: module: Initializing module X
Jan 18 07:50:45 localhost exalinkd[382]: module: Module temperature: 33 C 36 C
Jan 18 07:50:45 localhost exalinkd[382]: module: Module X serial number is UNKNOWN, build date 20160815
Jan 18 07:50:45 localhost exalinkd[382]: module: Enabling module X power
Jan 18 07:50:55 localhost exalinkd[382]: module: Timeout waiting for module serial device
Jan 18 07:50:55 localhost exalinkd[382]: exalink: Restarting hardware init because module init failed
Jan 18 07:50:58 localhost exalinkd[382]: module: Initializing module X
Jan 18 07:50:58 localhost exalinkd[382]: module: Module temperature: 33 C 36 C
Jan 18 07:50:58 localhost exalinkd[382]: module: Module X serial number is UNKNOWN, build date 20160815
Jan 18 07:50:58 localhost exalinkd[382]: module: Enabling module X power
Jan 18 07:51:08 localhost exalinkd[382]: module: Timeout waiting for module serial device
Jan 18 07:51:10 mw9tagswa341 exalinkd[382]: module_manager: Startup module config loaded from /media/userfs/module.conf
Jan 18 07:51:10 mw9tagswa341 exalinkd[382]: object_manager: Mux object "corvil-a" disabled: Switch, mux or fastmux module function required
Jan 18 07:51:10 mw9tagswa341 exalinkd[382]: object_manager: Mux object "corvil-b" disabled: Switch, mux or fastmux module function required
Jan 18 07:51:10 mw9tagswa341 exalinkd[382]: object_manager: Mux object "corvil-c" disabled: Switch, mux or fastmux module function required
Jan 18 07:51:10 mw9tagswa341 exalinkd[382]: object_manager: Mux object "corvil-d" disabled: Switch, mux or fastmux module function required

 

1 Reply 1

Reza Sharifi
Hall of Fame
Hall of Fame

Hi,

Based on these messages, it appears that the module has failed. If you have a support contract on the switch, open a ticket with TAC.

 

Jan 18 07:50:58 localhost exalinkd[382]: module: Initializing module X
Jan 18 07:50:58 localhost exalinkd[382]: module: Module temperature: 33 C 36 C
Jan 18 07:50:58 localhost exalinkd[382]: module: Module X serial number is UNKNOWN, build date 20160815
Jan 18 07:50:58 localhost exalinkd[382]: module: Enabling module X power
Jan 18 07:51:08 localhost exalinkd[382]: module: Timeout waiting for module serial device

 

HTH

Review Cisco Networking for a $25 gift card