
Phoenix G2 IDU Quick Start Guide
SAF Tehnika JSC
26
All Ethernet LAN, WAN and MNG ports can be separated by 3 groups. By default LAN3
port and MNG CPU port are interconnected into the same one group (Group 3); LAN2
port and WANb port are interconnected into Group2; LAN1 port and WANa port are
interconnected into the Group1. As LAN3 and MNG CPU port group is not connected
to any of WAN ports, the management channel over the RF is disabled to avoid of
possible Ethernet loop when interconnecting the IDUs/link to external equipment.
6.6.1
Out-band management
In order to have an out-band management access (management port is separated
from the user traffic), MNG CPU port should be in the same group with only one of
LAN ports and with one of WAN ports. In this case user traffic should not be passed
through the LAN port which is in the same group with MNG CPU port. The example is
given below:
Figure 21:
Phoenix G2 IDU out-band MNG configuration
The example in
Figure 21
shows one of grouping configuration options for out-band
management. In the example the management is accessible only via LAN3 port and
management channel over RF is enabled via WANb port ( MNG CPU, LAN3 and WANb
ports are grouped in Group 3). The user traffic will be passed through LAN1 and LAN2
port, and it will be passed through the RF over WANa port (LAN1, LAN2 and WANa
ports are grouped in Group 1)
6.6.2
In-band management
In order to have an in-band management access (management port is available
through the same LAN ports where user traffic is passed through), the MNG CPU port
should be in the same group with other LAN ports and with one of WAN ports. The
example is given below: