Rfp Configuration - Aastra NeXspan S Installation And Maintenance Manual

4.5.4 RFP CONFIGURATION

All configured RFPs are listed by cluster according to their topographic relations. The RFPs are
sorted by their Ethernet address.
To ensure correct handover of a PP during a call, all involved RFPs must deliver the same clock
signal to the PP. This is achieved by placing the RFPs so close to each other that every RFP
recognises at least one other RFP through its air interface.
There are conditions where this is not possible, for instance with RFPs at remote locations. In this
case, the RFPs must be grouped in clusters.
The OpenMobility Manager will not try to synchronize RFPs over cluster borders.
All non-empty clusters are displayed in the navigation bar on the left side and the OMM RFP is
marked with a bold font.
For easier administration, each RFP can be associated with a location string. The location string
can contain up to 20 characters
Each RFP is identified by its MAC address (6 bytes in hexadecimal format, separated by a colon).
The Ethernet address is unique and can be found on the back of the housing.
When the RFPs are connecting the OMM, they send their HW type characteristics. This type is
displayed on the RFP list web page.
When the RFPs connect to the OMM, they send their software release. If this release differs from
the OMM software release, the RFP connection attempt is rejected.
This could happen when if several DHCP servers with different OpenMobility software releases
are used. In this case, an error message is displayed. Moreover a global error message is
displayed on the RFP list web page if at least one version mismatch has been found.
New RFPs can be added to the system by pressing the 'New' button. A window opens providing
the configuration of this new RFP.
The same window can be opened for an existing RFP by pressing the tool icon
question.
Page 61 01/2007
of the RFP in
AMT/PTD/PBX/0062/1/2EN