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

SIP – DECT OM System Manual Release 2.1 7 Configuration und Administration Aspects
depl-1230/1.3 Page: 144 (196)
# DO load the individual file for the RFP with mac 003042FFF0D0
# no matter what OM_PersonalConfigAll says
OM_PersonalConfig_003042FFF0D0=y
# DO NOT load the individual file for the RFP with mac 003042ABCDEF
# no matter what OM_PersonalConfigAll says
OM_PersonalConfig_003042ABCDEF=n # BOOL
##############################################################################
# OpenMobility system
# the OpenMobilityManager IP addresses
OM_ManagerIpAddress1=172.30.205.17
OM_ManagerIpAddress2=172.30.205.18
OM_ManagerRestoreDbUrl=ftp://172.30.207.21/pub/backup.txt
OM_ManagerCountry=2
##############################################################################
# SYSLOG
OM_SyslogIpAddress=172.30.207.20
OM_SyslogPort=10115
##############################################################################
# NTP
OM_NtpServerName=de.pool.ntp.org
OM_NtpServerIPAddress=131.188.3.220 130.149.17.21
##############################################################################
# MISC
# transfer core files to the following url location
OM_CoreFileTransfer=ftp://172.30.206.21/pub # currently not
implemented
##############################################################################
7.8 802.1Q Support
The IP RFPs support VLANs according to IEEE 802.1Q. VLAN can be administered
• on a per port basis of the LAN switch assuming that the IP RFPs are connected to a
single port of a switched Ethernet environment, or
• by advising a VLAN ID to the IP RFP matching the VLAN they should operate in.
VLAN tagging has only to be set to IP RFPs’ in the last case. The whole section refers to that
case. With this, also 802.1p priority within Ethernet frames is enabled.
The scope of the following description is only the VLAN tagging and obtaining the VLAN ID.
Quality of Service mechanisms like 802.1p priority and DiffServ are not in the scope of this
section.
VLAN implementation notes referring to IP RFPs:
• IP RFPs are not able to support VLAN ID 0 as described later in this section. Any other
valid VLAN ID can be configured.
• If a VLAN ID is configured all traffic from an IP RFP will be tagged with this VLAN ID.
• The VLAN ID configured for a IP RFP is also used for the OMM running on this IP RFP.
• Once a VLAN ID is set to the IP RFP, incoming frames are only accepted if they are
tagged as well. Therefore the switch port has to be configured as a tagged trunk for this
VLAN.
• The VLAN configurations can be done using DHCP or the interface for the local static
configuration, the OM Configurator.
• The usage of VLAN does influence the boot up process of the IP RFP because the VLAN
configuration takes place during the boot up phase.