RadioFrame Networks Inc DH2 User Manual

Page of 164
Method of Procedure 
System Description 
18 
RFN_3.1 Beta
 
unauthorized access to the customer LAN. In addition, while a router between 
the RFS and the customer LAN is not required, it is highly recommended that a 
combination router and security gateway be used. 
The RFN implementation of 802.11b provides a transparent MAC layer bridging 
function between the RFS and the customer’s LAN. No layer 3 (IP) protocol 
routing is required for operation. 
The NCU contains a card that is assigned a fixed address during installation. 
Once the NCU has been configured, the NCU will automatically assign IP 
addresses to each network element in the RFS. 
2.2 Physical 
Relationships 
The RadioFrame System is laid out as follows: 
• 
Main rack:  Located in a Telco closet, the main rack houses the entire iDEN 
Interface and Power Plant, along with the NCU and one ACU of the 
RadioFrame System. 
• 
Remote ACUs:  Up to seven additional ACUs can be connected to the NCU. 
The remote ACUs are installed in closets or Telco rooms throughout the 
building to support additional RFUs. 
• 
RFUs:  Up to 8 RFUs per ACU are installed on walls or on or above ceilings 
throughout the building to provide coverage for the iDEN/802.11b RFS; RFUs 
house the iDEN RadioBlades RAPs. 
• 
LAN:  Customer equipment located in a customer-defined area. 
The following illustration depicts a typical RadioFrame Networks iDEN/802.11 
solution. The main rack is located on Floor 4 housing the iDEN Interface, Power 
Plant, and the NCU and one ACU of the RFS. The Customer LAN equipment is 
also located on Floor 4.  
Remote ACUs are located on Floors 1 and 2, with each ACU supporting up to 
eight RFUs. The ACU located on Floor 1 also supports RFUs in the parking level. 
RFUs on each floor of the building, 1, 2, 3, 4 and the parking level, support one 
of three sectors. RFUs on Floors 1 and 4 support sector 1. RFUs in the parking 
level and on floor 3 support sector 2. RFUs on Floor 2 support sector 3.