TD060100-0MA
12
Even though the
JC-MER-CXB
looks like a data router to
the Metasys
Network, most communications experts would call it a
network
gateway. To the Ethernet network, the router looks like a
normal
IBM
PMI/OWS
workstation. Unlike typical network
gateways and
routers, the
JC-MER-CXB
does not process:
•
routing protocols used by standard network routers, except for
UDP/IP communications from other
JC-MER-CXB unit
s
•
messages not generated by Metasys
The
JC-MER-CXB
responds to TCP/IP “
p
ing” commands,
allowing
you to verify that the router is operational and
properly connected to
the Ethernet network. However, the ping could fail if a firewall
blocks it from reaching the intended target.
Subnet Communication Upon Network Failure
If the Ethernet network goes down, or the router disconnects or fails,
each Metasys subnet continues to function on a standalone basis. A
JC-MER-CXB:
failure looks like a general failure of the
Metasys N1
network. Devices on a subnet are still able to
communicate with
other
devices on that subnet, but devices on a
different subnet are offline.
Hardware Requirements
The following are
other
hardware requirements of the
JC-MER-CXB:
•
Metasys Network with NCM200 or NCM300
or NCM4500
at
any revision;
or, NCM101/NCM401at Revision K or later
•
10BASE-T
/100BASE-TX
Ethernet connection
•
ARCNET connection (i.e., Metasys N1 LAN)
•
10
–36 VDC
or 8–24
VAC power at each
JC-MER-CXB
location