4019 - FC Module State is NO_COMM

Severity: MAJOR

Description: The Virtual Connect Manager is unable to communicate with the FC module.

Possible causes:

• The VC-FC module is rebooting after a FW panic and is not responding to VCM commands.
• The VC-FC module is not responding to ISMIC commands due to a FW defect.
• The VC-FC module fails to start the DHCP client due to a FW defect and therefore does not respond to commands from VCM to provide the switch configuration, including the FW revision number.
• The VC-FC module never obtains an IP address through DHCP and therefore does not respond to VCM commands.
• The VC-FC module never sends a COMM_OK OA event after a FW reboot due to a FW defect or hardware problem.

Action: Make sure that the DHCP server is running and correctly assigning addresses. In case of a transient error, power cycle the module to see if communication is restored. A support dump of the VC-FC module needs to be analyzed to determine the basic cause of the problem. The module might need to be replaced.