Ethernet operation, Configuration restrictions, Ethernet operation -4 – Clear-Com Eclipse-Omega User Manual
Page 24: Configuration restrictions -4
Clear-Com
Eclipse Omega Instruction Manual
2 - 4
• Replace the master CPU card.
ETHERNET OPERATION
The CPU card ethernet ports are normally connected to a LAN and
used to communicate with clients such as ECS and Production
Maestro. The ethernet port functionality depends on the IP address
setup.
If an IP address of 0.0.0.0 is configured on the second ethernet port, it
will not be used for Tx or Rx. This is the default setup if the default IP
address is set as described above.
All matrix to matrix traffic is sent out on both ethernet ports. This
applies to both directed and broadcast packets. All matrix to matrix
traffic is also received on both ethernet ports. If the traffic is transaction
related, the second (duplicate) message received is not consumed, but
simply dropped.
The matrices listen for client connections on both ethernet ports. Once
the connection is made it is added to the list of connections to service.
Broadcast type Tx data is duplicated out on each connection e.g. HCI
connection to the matrix from 3rd party applications.
The ECS Server makes a connection on either the main or backup
ethernet port of each system in the linked set. If both are up, this will
default to the primary port. In the event that connection is lost to the
currently active port on a matrix the ECS server will swap over to using
the other ethernet port. If this connection is lost only on one matrix in a
linked set, the others will not be affected.
Configuration Restrictions
The network ID on the first ethernet port must be different to that of the
second port. The network ID is defined by the IP address and the
network mask for the port. For example a network address of
172.16.2.1 and a mask of 255.255.0.0 gives a network ID of 172.16.
Therefore in this scheme the second port could not have an IP address
starting with 172.16. If the network mask is extended to 255.255.255.0
the network ID becomes 172.16.2 so the second port could have an
address of 172.16.3.1 and a mask of 255.255.255.0 giving a network
ID of 172.16.3 for the second port.
If both ethernet ports are set up with the same network ID this
condition results in data loss on one or both of the ethernet ports.
Ethernet redundancy and the use of a default gateway is not
recommended. An IP address and gateway combination on an
ethernet port means that all Tx traffic to any address is possible on the
port. Traffic that actually matches the other ethernet port can therefore
be sent out on the wrong port.