SIP User's Manual 102 Document #: LTRT-83310
Mediant 600 & Mediant 1000
10.2 Ethernet Interface Redundancy
The device supports Ethernet redundancy by providing two Ethernet ports, located on the
CPU module. The Ethernet port redundancy feature is enabled using the ini file parameter
MIIRedundancyEnable. By default, this feature is disabled.
When Ethernet redundancy is implemented, the two Ethernet ports can be connected to
the same switch (segment / hub). In this setup, one Ethernet port is active and the other is
redundant. If an Ethernet connection failure is detected, the CPU module switches over to
the redundant Ethernet port. The CPU issues a Major alarm notifying of the failed physical
port. If the first Ethernet port connection is restored, the Major alarm is cleared. The first
physical port now becomes the redundant Ethernet port in case of failure with the active
physical port (which is currently the second physical port).
When the CPU module loses all Ethernet connectivity, a Critical alarm is generated:
When MIIRedundancyEnable is disabled: the alarm is generated when the single
physical connection is lost. The alarm is cleared when the single physical connection
is restored.
When MIIRedundancyEnable is enabled: the alarm is generated when both physical
connections are lost. The alarm is cleared when one or both of the physical
connections are restored.
10.3 Configuring IP Interface Settings
The Multiple Interface Table page allows you to configure logical VoIP network interfaces.
Each interface can be defined with the following:
Application type allowed on the interface:
• Control - call control signaling traffic (i.e., SIP)
• Media - RTP traffic
• Operations, Administration, Maintenance and Provisioning (OAMP) -
management (such as Web- and SNMP-based management)
IP address and subnet
VLAN ID
Default Gateway
Primary and secondary DNS IP address
You can configure up to 16 interfaces - up to 15 Control and/or Media interfaces, and 1
OAMP interface.
This page also provides VLAN-related parameters for enabling VLANs and defining the
Native VLAN ID. This is the VLAN ID to which incoming, untagged packets are assigned.
For assigning VLAN priorities and Differentiated Services (DiffServ) for the supported Class
of Service (CoS), see Configuring the QoS Settings on page 122.