Slave Device Events In The Log - LEGRAND Raritan PX3TS User Manual

Appendix J: Additional PX3TS Information
848
Tip: To determine which PX3TS may be the failure point of network, you may
ping each PX3TS in the cascading chain, or check the slave-related events in the
event log of each PX3TS. See
Events in the Log (on page 848).
For a cascading chain comprising only products with "dual" Ethernet
ports, also check the following:
•
Whether the Ethernet interface (ETH1 or ETH2) where the network or
cascading cable is connected is disabled on the cascaded device in
question or any upstream device.
•
Whether the connection complies with the cascading guidelines, when set
to the Port Forwarding mode. See
Connections (on page 34).
•
Whether a newer product model, if involved in the chain, runs the
appropriate minimum firmware version or later.

Slave Device Events in the Log

The log messages for connection/disconnection of a cascaded device are
different for USB-cascading and Ethernet-cascading chains.
Messages for the Ethernet-cascading chain:
Whenever the connection or disconnection of a master/slave device is
detected, both PX3TS devices connected via that network cable record this
event in their internal logs.
There are two slave-related events:
Event
The ETH1/2 network interface
link is now up.
The ETH1/2 network interface
link is now down.
The Ping Tool (on page 849) and
Restrictions of Port-Forwarding
Description
This log entry is generated when the PX3TS
detects the connection of the upstream or
downstream cascaded device on one of its
Ethernet ports.
This log entry is generated when the PX3TS
detects the disconnection of the upstream
or downstream cascaded device on one of
its Ethernet ports.
Slave Device