Automatic Booter Update For Major Release Changes; Selecting The Right Dhcp Server; Rfp Led Status - Aastra SIP-DECT Installation And Administration Manual

Installation, Administration and Maintenance
Each application SW comes with the latest released booter SW. The
application SW will update the booter automatically as long as the major
release number of the booter SW has not changed, e.g booter SW 2.1.2 will
not be automatically updated by the booter SW 3.x.y, but the booter SW
3.0.0 will be automatically updated by the booter SW 3.1.0.

3.1.4.1.2 Automatic booter update for major release changes

The update of booters with a major release number change will be performed
automatically when the DHCP client in the application receives an DHCP
offer with the public option 254 with a value "UPDATE".

3.1.4.2 Selecting the right DHCP server

The DHCP client requests its own IP address using code 50. The DHCP
client will select the DHCP server that offers the currently used IP address.
Additionally the mandatory options must be offered otherwise the DHCP offer
is ignored by the DHCP client.
If no matching reply was received the DHCP client resends the request for 2
times after 1 second. Then the DHCP client will wait for 1 minute before
resending 3 requests again.
If the DHCP client cannot accept an DHCP offer within 3 minutes the RFP is
rebooted.
3.1.5

RFP LED status

The following diagram shows the LED status of a RFP according to the
different states during start up.
The RFP32 IP has three separate LEDs for red, orange and green to show
the different states during start up.
State
Booter (Start up)
Booter DHCP
Aastra Telecom
RFP32
Unused LED
LED green (Application)
LED orange (Application)
LED red (Booter)
Ethernet jack
Power supply in line with Power over LAN™
standard IEEE 802.3af
Power jack (120 V/230 V AC adapter)
LED state
Red on
Red flashing 0.5 Hz
Remarks
Waiting for link up
Launching a DHCP request and
waiting for an DHCP offer
Page: 21 (47)