Log messages for the Chassis Management microservice
LogID | Level | Message | Cause | Remedy | Impact |
---|---|---|---|---|---|
5001 | Fatal | Unable to connect to Operational Database | Database is down | Check Database status | Service not operational |
5002 | Info | Service started | Service is starting up | NA | Chassis services becoming available |
5003 | Error | I2C timeout, please power-cycle chassis, waited for: %v | Service is starting up | Restart the chassis | Chassis unavailable until restarted |
5004 | Fatal | Unable to connect to gRPC server, Error: %v | The gRPC server could not be found and a connection could not be established | The service will restart automatically | The chassis service will not be available until the service is restarted |
5005 | Error | gRPC failed with error: %v | A gRPC message failed, the service may be down | The service will restart automatically | The chassis service will not be available until the service is restarted |
5006 | Fatal | Failed to initialize microservice | One of components needed to start the chassis service is not available | The service will automatically restart | The chassis service is not available until it is restarted |
5007 | Error | Error getting system uptime %d | Unknown | Try again later, if the problem persists, contact support | System uptime cannot be determined |
5008 | Error | Error processing event [%s], error [%d] | An unknown event was received | Report the issue to Extreme Networks support | Chassis Manager may not be fully functional |
5009 | Error | Received empty request | A request with no contents was received | Report the issue to Extreme Networks support | None |
5010 | Error | Error unmarshalling received request %v | Incompatible message was received | Report the issue to Extreme Networks support | Some Chassis manager functionality may not be available |
5011 | Error | Unknown message type %v | Chassis manager is not compatible with this message type | Report the issue to Extreme Networks support | Some Chassis manager functionality may not be available |
5012 | Error | Failed to Unmarshal message as JSON, error = %v | Chassis manager is not compatible with this message type | Report the issue to Extreme Networks support | Some Chassis manager functionality may not be available |
5013 | Warning | ActivateResponse returned Failure. Time: %v | Timeout occured during communication | Retry the command | Chassis Activate command failed |
5014 | Error | Failed converting value %v to scalar, continuing with next update | Incorrect value received in message | Retry the command or configuration, contact support if persistent | Command or config failed to apply and was ignored |
5015 | Info | Shutdown processing: %s | Chassis Service is going down | The chassis is rebooting or being shutdown, or the service is being upgraded | Chassis services will not be available until the service is restarted |
5016 | Info | System initialization in complete. All services are UP | System Initialization is complete | NA | System is up and running |
5017 | Error | Firmware update to %s failed. Rolling back to previous firmware | The new firmware did not come up completely | Contact Customer Support | Firmware update failed |
5018 | Error | Sofware Rollback failed. msg: %s, err: %v | Firmware Rollback Failed | Contact Customer Support | Rollback due to failed firmware update failed |
5019 | Error | System initialization failed. Firmware %s, last reboot reason %v | TBD | Contact Customer Support | System Initialization Failed |
5020 | Error | Services %s are not up after %v | System Initialization failed | Contact Customer Support | System Initialization failed |
5021 | Info | Firmware change successful. Current Firmware version is %s | Firmware change successful | NA | Firmware changed |
5022 | Error | Sensor %s Current Value %d Crossed Warning Threshold %d | Thermal Monitoring | NA | Fan Speed might Increase |
5023 | Error | Sensor %s Current Value %d Crossed Warning Threshold %d | Thermal Monitoring | NA | Fan Speed might Increase |
5024 | Error | File %s Read Error %v | OS File Operation Read Error | NA | Value is NULL |
5100 | Fatal | Unable to Detect the Programming Device, Error: %v | Device in Unhealthy state | The system needs to be powered down | The slots and chassis service will not be available until the device is detected |
5201 | Info | Slot %v Inserted | Bootup or Insertion of the Linecard | NA | Slot becomes available |
5202 | Info | Slot %v Extracted | Extraction of the Linecard | NA | Slot becomes unavailable |
5203 | Info | Slot %v Powered Down | Linecard has been powered down | Check ConfigDB For SlotOff | Slot Ports/Interface services are unavailable |
5204 | Info | Slot %v Powered UP | Linecard has been powered up after removal or using Config | NA | Slot Ports/Interface services are available |
5205 | Error | Slot %v Failed | Linecard Entered an faulty State | TroubleShoot the LC using Poweroff/On , else replace if needed | Slot Ports/Interface services are rendered DOWN |