ABB IET800 can have a healthy CH0 Ethernet path while its NIS21 pairing, INFI-Net node mapping or client database is incomplete; check the control-network side separately from IP reachability.

For ABB IET800, record the current address, switch port, subnet, routes and every dependent client before changing CH0, then test engineering and operations connections one by one.

ABB IET800 publishes CH0 as the 10/100 Mbps RJ45 connection and identifies CH1 as reserved, so CH1 should not be designed as an active redundant Ethernet interface.

For ABB IET800, stale values can follow source-node loss, exception-report interruption, overloaded client polling or incorrect point mapping; compare live INFI-Net status with client timestamps.

Before replacing ABB IET800, preserve the module and NIS21 identities, IP settings, security mode, database configuration, supported host versions and switch-port details.

For ABB IET800, inventory the intended Composer and server connections, point count and update demand, then validate them against the published 30,000-tag and up-to-10-Composer-client limits.