AASTRA SIP-DECT (Release 2.1)- OM System Manual - Installation, Administration and Maintenance EN - Manual (Page 145)

SIP – DECT OM System Manual Release 2.1 7 Configuration und Administration Aspects
depl-1230/1.3 Page: 145 (196)
• The default setting is not to tag the traffic. 802.1Q tagging is enabled if the VLAN ID is set.
If no VLAN ID is set 802.1Q is disabled.
Why not VLAN ID 0 ?
VLAN ID 0 means that the IP RFP’s traffic belongs to the port/native VLAN. The Ethernet
switch port to which the IP RFP is connected must be configured to accept 802.1Q tagging
for this to work and the switch must interpret VLAN ID 0 as the port/native VLAN ID per the
IEEE 802.1Q standard.
The packets from the IP RFP are tagged with VLAN ID 0 and the packets send to the IP RFP
are tagged with the port/native VLAN ID. This scenario does not work, because the IP RFP
supports only one VLAN ID in both directions. That means the VLAN ID in receive direction
has to be the same as in send direction.
7.8.1 Boot Phase of IP RFPs (DHCP)
Because the IP RFP does not know about VLAN during the beginning of the start up, two
DHCP scopes are required. This applies regardless of the Ethernet switch being used. The
following scenario with arbitrary VLAN Ids’ details the steps an IP RFP would go through in a
typical dual-VLAN implementation.
Step A. DHCP scope within the native VLAN:
1 IP RFP boots up and obtains an address on the native VLAN.
2 The data VLAN DHCP option 132 directs the IP RFP to go to voice VLAN.
Step B. DHCP scope within the voice VLAN:
1 IP RFP releases the data VLAN address and obtains an address on the voice VLAN and
all other parameters.
The voice VLAN does not have the DHCP option 132, because a IP RFP already on the
voice VLAN does not need to be directed to go there.
2 IP RFP is operational on the voice VLAN.
If a reboot or power cycle occurs, the IP RFP returns to step A.
If an IP RFP cannot obtain an address on the voice VLAN, due to network or DHCP
problems then the IP RFP falls back automatically to untagged frames (native VLAN).
To avoid the DHCP scope within the native VLAN the VLAN ID to be used can be set
permanently via OMC without losing the ability to provide other parameter via DHCP, please
see section 0 Static Local Configuration Of An RFP.
7.8.2 Boot Phase of IP RFPs (Local Configuration)
The PC running the OM Configurator has to be a member of the native VLAN for the 1st
configuration, later on within the voice VLAN set.
If a wrong or unknown VLAN ID is set, you can overwrite or read the configuration using no
VLAN tag on the switch port in the first 6 seconds after the RFP is connected to a power
supply / PoE. After 6 seconds the RFP apply the local configurations and start using the
parameters.