IP LAB: Current Architecture

Transcription

1 Section 1 Lab Architecture & Equipment IP LAB: Current Architecture Aalborg S1/1 Ethernet Istanbul Shanghai Vlan S0/2 S0/0 S0/1 Tokyo S0/ S1/ S0/3 San Francisco Frankfurt S1/1 Delft Shanghai Vlan 2 Toronto Vlan Sydney Dhaka Bluetooth X X Figur 1 The architecture shown above is the current state of the network setup in the lab, but changes rapidly according to the needed scenarios in the different student projects. In general the setup is as shown with additional connections between every router, not configured though. The equipment shown is as follows: Equipment: Version Software Names Cisco Routers 3620 c3620-i-mz.122-5d.bin Aalborg, Frankfurt and Delft 3631 c3631-telco-mz t5.bin Tokyo and San Francisco Cisco Switches 2950 c2950-i6q4l2-mz ea1.bin Toronto and Shanghai Cisco APís 350 Istanbul and Dhaka 1200 Sydney Bluetooth AP Ericsson BlipNode L1

2 Computers: 1 Pentium 4, Windows 2000 server and Linux Red Hat 9.0 platform ( ). 3 Pentium pro 166 MHz, 64 MB RAM, 2GB hard disk, Linux Red Hat 7.3 platform. Additional equipment, not shown in Figure 1, available: Cisco 1100 WLAN AP and PDA, see Section 2.

3 Section 2 Wireless Access Technologies BT, a/b and GPRS (Sonofon subscription) 2.1 Bluetooth 1 Ericsson BlipNode L1, Access Point (Computer is needed acting as server) 8 Belkin USB adapter, F8T003yy, 10 meter 2 Belkin USB adapter, F8T001yy, 100 meter 2 Belkin USB adapter, F8T003uk, 100 meter (Do not support PAN) The F8T003uk is version 1 followed by the F8T001yy version 2, where the main different is that version 1 does not support PAN. In general the Bluetooth protocol stack is a cut through all the layers depending on the specific profile. If something specific can be said about the Bluetooth protocol stack it would be that the stack can be simplified to a kernel protocol stack, which upon different protocols can be adapted. The kernel protocol stack is shown in the following figure. - Radio: Modulation FHSS, GFSK - Baseband: Link control, time synchronizing, SCO time critical data sent directly up and down. - LMP: Link Management Protocol - HCI: Host Controller Interface - L2CAP: Logical Link Control and Adaptation Protocol, packet segmenting and reassembling and QoS, max packet size 64KB. Currently IP transport is used in the Lab, which is the PAN profile. Supported profiles for the adapters: - Generic access - Service discovery - Serial port - PAN (IP transport) - LAN access - Dial-Up networking - Generic object exchange - Object push - File transfer - Synchronization - FAX Bluetooth Specification v1.1 Operating frequency 2.4 to GHz Data rate 723/57.6Kbps Network topology Point-to-Multipoint Packet support 1/3/5 slots packet Operation Master/Slave Supply voltage 5.0VDC Nominal current 100mA

4 2.2 IEEE Cisco access points Cisco aironet WLAN cards 350, b 2 Cisco access points Cisco aironet WLAN card 5GHz, 802,11a 1 Cisco access point Nokia access point A032 3 Nokia WLAN cards DTN-11 Standard Operating frequency Data rate Modulation Techniques Distance Coverage a to 5.350GHz and to 5.825GHz 54 Mbps OFDM 20 meters - speed goes down with increased distance b to GHz 11 Mbps FHSS Up to 100 meters The ANSI/IEEE standard only describes the 1Ω lowest layers of the OSI-model. This means: - The physical layer. o a uses OFDM with BPSK/QPSK or 16/64-QAM o b uses DSSS (which is most used) with BPSK/QPSK or it uses FHSS with 2/4 level GFSK - The MAC layer part of the data link layer. Specified by the 802 family on top of the standard you will find the bridging and on top again the logical link control. Then on top again you will find TCP/IP aso. 2.3 GPRS The GPRS equipment consist of a SIM-card (Sonofon subscription), which can be used in: - 1 Nokia GPRS/WLAN, D211, PCMCIA card (Can be used for in laptop) - HP PDA with GPRS jacket and integrated WLAN The GPRS protocol stack is as shown in the figure:

5 Application IP/X.25 SNDCP LLC RLC MAC GSM/RF Details about the GPRS subscription (private address, etc) need to be investigated.

6 Section 3 Mobility support Mobile IP software has been retrieved from Helsinki University: Where the installed software is the source code: dynamics tar.gz Mobile IP is implemented on the (from Section 1): - 3 Pentium pro 166 MHz, 64 MB RAM, 2GB hard disk, Linux Red Hat 7.3 platform. - 1 Pentium 4, Linux Red Hat 9.0 platform ( ). The most frequently used computers are the 3 Pentium pro computers, where the (see Figure 1): acts as the home-agent and acts as the foreign-agent The mobile IP software is developed to/on Linux Red Hat, where 7.X should as default have all the needed requirements fulfilled. A complete set-up of the Mobile IP can be found at: Client software - The dynamics source code also contains the client part. As tested so far, the data transport freezes when/after making a handover from one agent to another. - Birdstep Mobile IP client is implemented in windows ( This client supports handover and vertical handover, tested for BT and WLAN.