Events

FieldData
Categorygiid
Severityinfo
MessageDHCP address for interface [<interface-name>] has successfully been resolved/renewed
CauseTroubleshooting Step
The DHCP address lease for the interface has been successfully resolved or renewed.None.

FieldData
Categorygiid
Severityminor
MessageDHCP address for interface [<interface-name>] has changed
NotesIssued when the DHCP address changes during a renewal.
CauseTroubleshooting Step
Occurs when the DHCP address changes during a renewal.This is just for information purposes and no action is normally needed.

FieldData
Categoryplatform
Severitymajor
MessageOffline file <file-name> was never completed
NotesIssued when an offline audit file was not closed correctly by the audit log subsystem. This could indicate lost audit logs.
CauseTroubleshooting Step
Occurs when an offline audit file was not closed correctly by the auto log subsystem.
Note: This may indicate lost audit logs.
This event could indicate a disk write failure or a previous improper shutdown of the system. Check the integrity of the system disks using the linux command fsck. Ensure that the system is powered down correctly whenever possible.

FieldData
Categoryplatform
Severitymajor
MessageExternal modification of /etc/resolv.conf detected.
NotesIssued when the file /etc/resolve.conf is modified by user or code.
CauseTroubleshooting Step
/etc/resolv.conf is editedThis file is managed by the 128T platform and should not be edited by hand or by an external script or processes.

FieldData
Categoryplatform
Severitymajor
MessageApplication script on interface <interface-name> exited unexpectedly.
NotesIssued when the interface plugin script hits an unhandled exception in code.
CauseTroubleshooting Step
Application script faults.If this happens, check the status of the interface on which the script is running. If the interface is operational and the problem persists, contact customer support.

FieldData
Categoryplatform
Severitymajor
MessageApplication script on interface <interface-name> was restarted after unexpected exit.
NotesApplication script on interface was restarted.
CauseTroubleshooting Step
Application script on interface restarted unexpectedly.If this happens, check the status of the interface on which the script is running. If the interface is operational and the problem persists, contact customer support.

FieldData
Categoryredundancy
Severitymajor
MessageProcess RedisServer on node <node-name> is now active.
NotesIssued when the redis process on node assumes leadership
CauseTroubleshooting Step
Leadership for redis process has changedThis may happen if the HA link between nodes has gone down. Check the availability of both nodes and their respective HA interface status. If one of the nodes is offline, start the 128T process. If the node is online, check the interface status.

FieldData
Categoryredundancy
Severitymajor
MessageProcess RoutingEngine on node <node-name> is now active.
NotesIssued when the routing engine process on node assumes leadership
CauseTroubleshooting Step
Leadership for routing engine process has changedThis may happen if the HA link between nodes has gone down. Check the availability of both nodes and their respective HA interface status. If one of the nodes is offline, start the 128T process. If the node is online, check the interface status.

FieldData
Categoryredundancy
Severitymajor
MessageProcess SecurityLeader on node <node-name> is now active.
NotesIssued when the security leader process on node assumes leadership
CauseTroubleshooting Step
Leadership for security leader process has changedThis may happen if the HA link between nodes has gone down. Check the availability of both nodes and their respective HA interface status. If one of the nodes is offline, start the 128T process. If the node is online, check the interface status.

FieldData
Categoryredundancy
Severitymajor
MessageProcess AutomatedProvisioner on node <node-name> is now active.
NotesIssued when the automated provisioner process on node assumes leadership
CauseTroubleshooting Step
Leadership for automated provisioner process has changedThis may happen if the HA link between nodes has gone down. Check the availability of both nodes and their respective HA interface status. If one of the nodes is offline, start the 128T process. If the node is online, check the interface status.

FieldData
Categoryredundancy
Severitymajor
MessageNode <node-name> is now active for shared interface
NotesIssued when a redundant interface assumes a leadership change.
CauseTroubleshooting Step
Application script on interface was restartedThis event does not necessarily indicate a system error and can occur occasionally due to HA failover events, for example when an interface is taken down for maintenance. This can be reported as a system is started and assumes leadership. If it occurs during runtime, see the sections on related interface alarms (eg: “interface operational down”) for more detailed causes and troubleshooting steps.
Last updated on