LVA Syllabus Part 1

Transcription

1 LVA Syllabus Part 1 Written by: Heimo Zeilinger Network Simulation and Configuration The aim of the laboratory course Part 1 is to get an overview on the configuration of network components (switches, routers, network interface cards) as well as the configuration of a Layer-2 network protocol (RSTP) on a predefined network structure see Figure 1. The course is evaluated by the completion of the tasks as well as a documentation of the work. Traffic sink Manage-PC Domain: ict.tuwien.ac.at PC eth2 MAC: 00:1B:11:19:B2:17 IP: t.b.d. : management-pc (Ubuntu 7.04) MAC: 00:18:4D:D3:97:9D IP: IP: MAC: 00:18:4D:D3:97:9D IP: Netgear GSM7312 Virtual Router / VRRP Netgear GSM7312 MAC: 00:18:4D:D3:97:9D IP: MAC: 00:18:4D:D3:96:1D IP: : RTR1 managed Layer 3 switch IP: : RTR2 managed Layer 3 switch L5 L7 L8 L6 Dell PowerConnect 3424 MAC: 00:19:B9:AD:0C:6A IP: Dell PowerConnect 3424 MAC: 00:19:B9:AC:FD:1F IP: : managed switch SWI3 : managed switch SWI4 L1 L3 Netgear FS105 : non-managed switch SWI1 Hostname: PC-s0 Domain: ict.tuwien.ac.at PC eth1 MAC: 00:14:6C:76:53:80 IP: : test-pc (Ubuntu 7.04) VCX-i Traffic generator Figure 1 Proposed network structure Fehler! Verweisquelle konnte nicht gefunden werden. shows the test network which consists of the host systems (PC-S0, MANAGE-PC) and the network nodes (SWI1, SWI2, SWI3, SWI4, RTR1, RTR2).The MANAGE-PC represents the traffic sink and simulates the Seite 1 von 9 Druckdatum:

2 backbone network. The host PC-S0 represents the traffic generators. The host and node configuration is listed in the Appendix A. One Layer-2 switch (SWI1), two managed Layer-2 switches (SWI3, SWI4), and two Layer-3 switches (RTR1, RTR2) complete the network. PC- S0 and the MANAGE-PC run Linux Ubuntu SWI1 and SWI2 are unmanaged switches. Network configuration Prepare the redundant network structure proposed in Figure 1 (Subnet addresses are optional use addresses regarding the private IP address space) Configure the network nodes as well as the end-systems Establish a connection between PC-s0 and Manage-PC (proof by ping each network node as well as end system) Observe the network behavior in case of shutting down the root node. Additional exercise: Configure the Virtual Router Redundancy Protocol (VRRP) for RTR1 and RTR2. Configure the network the way that RTR1 and RTR2 seem to be a virtual router for the Manage-PC. Test the failover behavior by transmitting a UDP stream through the network and shutting down the root node as well as one link of the main path. The host PC-S0 is used as traffic source which sends a continuous traffic stream to the Manage-PC the appropriate scripts are already written and will be explained on site. Failover times and packets are analyzed by the use of the packet sniffer Wireshark. Proposed procedure 1. Start the engines ;-) 2. Connect the network nodes to the network structure proposed in Figure Login to the Manage-PC, the PC-S0 as well as the managed network nodes. PC-S0 and managed network nodes are reachable from the Manage-PC (The tool Minicom is used for this task) user and pw are provided on site. 4. Look at the IP-settings. Ensure that nodes and end-systems are in the same sub-net. 5. Configure RSTP for all manageable nodes 6. Set the appropriate routes at the end-systems 7. Test the connection between Manage-PC and PC-S0 8. Shut down the root node the root node can be determined by a look at the configuration table. Evaluate the network behavior. Additional tasks 1. Put the Manage-PC to a different sub-network 2. Configure VRRP on both Layer-3 switches (RTR1, RTR2) 3. Check the connection between PC-S0 and Manage-PC 4. Measure the convergence time of the network due to shutting down the root node as well as the links which form the used transmission route In Appendix C, required Linux commands are listed. Examples for a network node configuration is listed in Appendix D. Good Luck! Seite 2 von 9 Druckdatum:

3 Appendix A Network components All nodes are listed in context to their notation in Fehler! Verweisquelle konnte nicht gefunden werden.. For the manuals, please look at the LVA homepage - Node Configuration RTR1 Serial Number MAC-Address (burned in) Software Bootcode GSM7312 L3 Managed Gigabit Switch GSM7312 1C22725B :18:4D:D3:97:9D RTR2 Serial Number MAC-Address (burned in) Software GSM7312 L3 Managed Gigabit Switch Netgear GSM7312 1C22725B :18:4D:D3:96:1D SWI4 Managed Layer-2 Switch Dell PowerConnect 3424 Serial Number MAC-Address (burned in) Software SWI3 00:19:b9:ad:0c:6a Managed Layer-2 Switch Dell PowerConnect 3424 Serial Number MAC-Address (burned in) Software SWI2 00:19:b9:ac:fd:1f Serial Number Ethernet Switch Netgear ProSafe 5 Port 10/100 Fs105 v2 1D51763R03567 Seite 3 von 9 Druckdatum:

4 SWI1 Serial Number Ethernet Switch Netgear ProSafe 5 Port 10/100 Fs105 v2 1D51763R03595 Host Configuration PC-S0 Ubuntu 7.04 Operating system Debian version 4.0 Kernel generic GCC version (Ubuntu ubuntu4) CPUs Processor 0 Vendor GenuineIntel CPU family 6 name Genuine Intel(R) CPU 1.66GHz CPU MHz Cache size 2048 KB Processor 1 Vendor GenuineIntel CPU family 6 14 name Genuine Intel(R) CPU 1.66GHz CPU MHz Hardware FSB Cache size 2048 KB RAM 1 GB Network interfaces eth0 AOPEN Inc. Intel Corporation 82573L Gigabit Ethernet Controller IP address MAC address Hostname 00:01:80:63:FD:CF volare-s0.ict.tuwien.ac.at eth1 D-Link System Inc DFE-530TX rev A VIA Technologies, Inc. VT6102 [Rhine-II] (rev 43) IP address MAC address 00:1B:11:19:B0:42 Seite 4 von 9 Druckdatum:

5 eth2 D-Link System Inc DFE-530TX rev C VIA Technologies, Inc. VT6105 [Rhine-III] (rev 86) IP address t. b. d. MAC address 00:50:BA:FA:C8:C1 Manage-PC Ubuntu 7.04 Operating system Debian version 4.0 Kernel generic GCC version (Ubuntu ubuntu4) CPU Vendor AuthenticAMD CPU family 6 8 name AMD Athlon(TM) XP CPU MHz Cache size 256 KB FSB RAM Network interfaces 512MB eth0 ASUSTeK Computer Inc. VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74) Hardware IP address MAC address 00:0E:A6:92:61:16 Hostname volare-pc.ict.tuwien.ac.at eth1 D-Link System Inc DFE-530TX rev C VIA Technologies, Inc. VT6105 [Rhine-III] (rev 86) IP address - MAC address 00:05:5D:7B:4D:AB eth2 D-Link System Inc DFE-530TX rev C VIA Technologies, Inc. VT6105 [Rhine-III] (rev 86) IP address MAC address 00:1B:11:19:B2:17 Seite 5 von 9 Druckdatum:

6 Appendix B Protocols Rapid Spanning Tree Protocol The Spanning Tree Protocol ensures a loop-free topology for a bridged Local Area Network and works on the base of OSI layer-2. STP allows including redundant links in order to provide automatic backup paths in case of link failures. Bridge loops are avoided. It is defined in the IEEE Standard 802.1D. The Rapid Spanning Tree Protocol (RSTP) IEEE standard 802.1w represents an evolution of STP and provides faster spanning tree convergence. For more information on RSTP please look at Virtual Router Redundancy Protocol The Virtual Router Redundancy Protocol (VRRP) is a non-proprietary redundancy protocol described in RFC 3768, designed to deal with the single hop problem. Like it is explained above, in order to achieve higher network availability, the network structure shows a redundant design. However, the network gateway forms a single point of failure. Hence the VRRP is designed for combining n routers to a virtual router (formed out of master and backup routers) the network gateway is formed by n routers, which seems to be one single router to the provider network as well as the end system. A short introduction to VRRP can be found on the CISCO homepage shtml Seite 6 von 9 Druckdatum:

7 Appendix C Basic Linux Commands A lot of lists on basic Linux commands are placed in the www. One example is the list on If you do not have any experience in Linux you may consider working through such a page. As a start the basic commands should suffice. Network configuration commands The basic commands for network configuration are listed below. For specific information, please look at man XY ping traceroute ip ip route show shows the manual page of any command XY sends echo requests to the host you specify on the command line, and lists the responses received their round trip time. shows the route of a packet. It attempts to list the series of hosts through which your packets travel on their way to a given destination. used to assign IP addresses to interfaces (eth0, lo, ), setting up and displaying the TCP/IP configuration. It replaces the commands ifconfig and route in newer Linux distributions shows all specified routes ip addr add <ip-addr>/24 dev eth0 ip addr del <ip-addr> dev eth0 ip route add /24 dev eth0 ip route add default via ip route delete /24 dev eth0 adds an ip-address to the interface eth0. /24 shows specifies the subnet prefix. /24 accords to the subnet deletes an ip-address sets a route to the Locally Connected Network eth0 sets a default route deletes route from table ifconfig optional command to ip to show the network interface configuration and to configure them Examples: ifconfig ethxy down ifconfig ethxy up deactivates the interface XY activates the interface XY ifconfig ethxy a.b.c.d netmask assigns the IP address a.b.c.d to the network interface ethxy and specifies the sub-netmask route configures the routing information for the kernel this is needed if the sink is not placed in the same sub-net as any interface. It allows to manually set network table entries Examples: route add default gw xy route add -net x netmask eth0 route del x netmask eth0 route -n sets the default gateway adds a route to the network x via "eth0". deletes the specified route lists all routes with numerical addresses Seite 7 von 9 Druckdatum:

8 Appendix D Node Configuration This part gives a short introduction on the configuration of a network node. As example the configuration of RSTP on the managed Layer-2 Switch Dell PowerConnect 3424 is given. Even the user interface of the managed Layer-2 and the Layer-3 switches differs, it is similar to handle. Please, look at the manuals for the commands see On the command line of the Manage-PC type minicom ttyusb1 Minicom is a text-based modem control and terminal emulation program for Unix-like perating systems. The serial port of the managed switch is assigned to ttyusb1. Below, the assignment of all network nodes is listed Network Node SWI3 SWI4 RTR1 RTR2 Name ttyusb1 ttyusb2 ttyusb3 ttyusb4 After connecting to the switch, the switch s user interface appears. Username and password will be given on site. Type (SWI3) >enable to reach the administration mode. With the command? all possible commands, which can be invoked from the current mode, are listed. With the command SWI3# show running-config you can have a look at the current system settings; IP settings included. SWI3# show? shows all possible commands and configuration settings for the command show. The same applies for all commands. With the command SWI3# configure the global configuration mode is reached. With the command exit you can return to the previous configuration mode. To change the nodes IP-address SWI3 (config-if)# ip address To enable spanning-tree functionality, type SWI3 (config) # spanning-tree With the command no spanning-tree, the spanning-tree functionality is turned off. The spanning- tree mode RSTP is chosen by SWI3 (config) # spanning-tree mode rstp Make sure that the different protocol timers for RSTP (hello-time, forward-time, max-age) are set to the same value on each network node. Set the timers to the minimum. SWI3 (config)# spanning-tree forward-time 25 SWI3 (config)# spanning-tree hello-time 5 SWI3 (config)# spanning-tree max-age 10 Seite 8 von 9 Druckdatum:

9 Set the priority for all nodes to the same value. SWI3 (config)# spanning-tree priority 4096 After returning to the admin mode, you are able to verify spanning-tree settings with SWI3 # show spanning-tree or SWI3 # show spanning-tree detail Restarting the devices is executed through the following command: SWI3# reload Seite 9 von 9 Druckdatum: