Start-Up Of The Openmobility Manager; Booter; Dhcp Client; Dhcp Request - Aastra DECToverSIP Installation, Administration And Maintenance

Installation, Administration and Maintenance
On start-up each RFP tries to determine its own IP address and other
settings of the IP interface from the configuration settings in the internal flash
memory. If no settings are available or these settings are disabled, the RFP
tries to determine these settings via DHCP.
The RFP gets the application image file from the TFTP server.
Application
After starting the application image the RFP checks the local network settings
in its internal flash memory once again. If no settings are available or if they
are disabled it starts a DHCP client to determine the IP address of the OMM
and other start-up settings.
3.1.2

Start-up of the OpenMobility Manager

There is no difference in booting that RFP, which is chosen to be running in
OMM mode from those which are in the RFP only mode.
The decision is driven by the OMM IP address, which is read
• within the local network settings, if active.
• via DHCP request.
The RFP which has the same IP address as the dedicated OMM IP address,
will be the RFP which the OMM software runs on.
3.1.3

Booter

3.1.3.1 DHCP client

Within the initial boot process the DHCP client supports the following
parameters:
• IP address
• Net mask
• Gateway
• Boot file name
• TFTP server
• Public option 224: "OpenMobility"

3.1.3.1.1 DHCP request

3.1.3.1.1.1 Vendor class identifier (code 60)
The DHCP client sends the vendor class identifier "OpenMobility".
3.1.3.1.1.2 Parameter request list (code 55)
The DHCP client in the booter requests the following options in the
parameter request list:
• Subnet mask option (code 1)
• Router option (code 3)
• Public option 224 (code 224)
Aastra
mandatory
mandatory
mandatory
mandatory
mandatory
mandatory
depl-0900/0.4
Page: 20 (104)