Hochschule Bremen Networking Lab User Manual Welcome to the Hochschule Bremen networking lab. This manual will give you a brief introduction on how to use the PCs and networking hardware in the lab. The lab features the following hardware: - 15 Intel Quad Core PCs (14 student PCs, 1 instructor PC) - 21 Cisco Routers (2600 and 2800 models) - 7 Cisco Switches (2650 models) - 7 D-Link 100 Mbit/s Hubs Typically, most lab exercises are designed to use a standard topology, each consisting of 3 Routers, 1 Hub, 1 Switch and 2 PCs. Of course this setup may be changed at any time according to the exercise. Each student PC is running VMWare Server 2 virtualization software. This solution allows for operating system flexibility and gives the students full administration permissions on the virtual machines while maintaining stability and reducing administrative work.
Each physical student PC is able to run various Windows oder Linux virtual Machines (VMs). While students have limited user permissions on the physical Host PC, full administrative permissions are available on the virtual machines. Each PC has three important cable connections: - an ethernet fiber cable connection for access of the internet and the campus network. Used for downloading manuals, software or mailing lab reports. - an ethernet twisted pair copper cable connection for the lab internal LAN. Used for connecting the PCs to the Lab Routers, Switches and Hubs or the PCs back to back. - a console connection which is used only to configure the routers and switches. It uses the serial (com 1) port of your PC. All of these 3 connections are virtualized by VMWare which means that they are not only available on the host PC but also on the virtual machines, where you are able to change the settings of the Network Interface Cards (NICs). To get started, boot your PC and log in with the user account. User: vm Password: vm You are now logged on to the Windows XP host system. From the host desktop you are able to start your desired virtual machines by the corresponding desktop icons. After starting a virtual machine you need to enter the correct username and password for the vm:
Please log in using: User: vm Password: vm When your selected VM has finished loading you are able to start your lab exercise. In this manual we will use the windows XP Lab Desktop Virtual Machine. Please keep in mind that your VM has two network adapters, but only 1 should be active at any time. If both NICs should be active at the same time you may experience severe network problems up to total disfunction!!! Before starting your exercise,check your network properties: As you can see the Internet connection is enabled by default. At this moment you are able to access the internet. If you need to use the internal Lab LAN for connecting the PCs to the lab Routers and Switches, please deactivate the Internet Fiber NIC, and then activate the Twisted Pair Lab LAN Nic. Keep in mind that you still may need to modify your TCP/IP Settings for the Lab LAN NIC for setting the correct IP address, subnet mask and gateway.
d Cabling and using the lab hardware When starting your lab exercise you might receive a topology map which might look similar to this: With the help of this map you should be able to identify the correct cables and ports needed for your exercise. Like stated before, many lab exercises are designed to use a standard setup which consists of one hub, one switch, and three routers, which make up a lab hardware group. Seven hardware groups are available in the networking lab. As you can see in the picture above, the serial connections (blue cables) between the routers, which simulate Wide Area Network (WAN) connections, are already patched and should not be removed since the plugs of the serial cables are fragile and can easily be broken.
To connect your pc to your hardware group, please refer to the standup info sign on your pc: It will provide you with the necessary information to patch your ethernet connection (the twisted pair based internal lab LAN NIC) and the console connection. Please keep in mind, that the console connection is used ONLY to configure the routers and switches by exchanging text based commands with the command line interface (CLI) of the hardware. This port is not used for routing data. If you have gathered the information concerning the correct hardware rack, patch field and port you are able to install the cables on the patch field: When connecting to a router please be careful to use the correct ports:
This Router has two ethernet ports (yellow), named FastEthernet 0/0 and FastEthernet 0/1. If only one ethernet port is needed in your exercise, FastEthernet 0/0 should be used. Some routers only have one FastEthernet port. The console port (light blue) is used to access the CLI of the router for any configuration task. The AUX port is used for access via modem and not used in the exercises. Router Configuration Unlike Home DSL Routers, professional Cisco routers are not configured via a web browser, since in the factory setting, no IP Address is configured for any interface. Instead, a terminal software is used to access the CLI of the router through the console port, which is connected to the serial com port of the pc with a console or rollover cable. These cables have e special pin layout and should already be connected to the com1 port of your pc. Please connect a standard patch cable from the patch panel in the hardware racks to the console port of the router. To access the CLI of the router, please start the terminal software Hyper Terminal. Please choose a name for the session and then specify the correct serial port. Afterwards you need to configure the
communication settings for this session: Please configure the session for 9600 bps and no flow control. After starting the session and hitting the enter key you should receive the first output of the router CLI. If the router has a blank configuration you will be asked if you want to use configuration assistant: Would you like to enter the initial configuration dialog? [yes/no]: Please terminate the assistant by entering no or using the <ctrl+c> keys. When the router has finished initializing you should receive a prompt like this: Router> This is the first operating mode of a router, called user exec mode. This mode has a reduced set of available commands and is used for basic troubleshooting mainly. Please type? in any mode to view a list of available commands, command options or parameters. Please type enable. Your prompt should change like this: Router# This is the privileged exec mode which will give access to the full command set of the router. This mode is used for displaying the configuration, debugging, management of configuration files and troubleshooting. You cannot make any configuration changes in this mode. To change the configuration of the router, enter the command configure terminal. Your prompt should like this: Router(config)# This is the global configuration mode. Any settings that affect the router as a whole are made here. There a number of sub modes of the config mode which will configure specific interfaces or routing protocols.
Useful IOS Commands enable - get to privileged mode disable - get to user mode enable secret <password_here> - set encrypted password for privileged access Set password for console access: (config)#line console 0 (config-line)#login (config-line)#password <password_here> Set password for virtual terminal (telnet) access (password must be set to access router through telnet): (config)#line vty 0 4 (config-line)#login (config-line)#password <password_here> show running-config - details the running configuration file (RAM) show startup-config - displays the configuration stored in NVRAM configure terminal - use to execute configuration commands from the terminal copy running-config startup-config - copies config in RAM to NVRAM no shutdown - (enables the interface) reload - restarts the router no debug all - turns off all debugging banner motd # Your_message # - Set/change banner hostname <router_name_here> - use to configure the hostname of the router
show cdp neighbor - shows directly connected neighbors no cdp run - turns off CDP for entire router (global config) Configure IP on an interface (config mode): int serial 0/0 ip address 157.89.1.3 255.255.0.0 no shutdown (config-if)#clock rate 56000 - set clock on DCE (bits per second) sh ip route - view ip routing table ip route <remote_network> <mask> <default_gateway> [administrative_distance] - configure a static IP route ip route 0.0.0.0 0.0.0.0 <gateway_of_last_resort> - sets default gateway Configure RIP: router rip network 157.89.0.0 network 208.1.1.0 Other RIP Commands: debug ip rip - view RIP debugging info View access lists: sh access-lists Apply standard IP access list to FastEthernet0/0: access-list 1 deny 200.1.1.0 0.0.0.255 access-list 1 permit any int FastEthernet0/0
ip access-group 1 in Apply Extended IP access list to int FastEthernet0/0: access-list 100 deny tcp host 1.1.1.1 host 2.2.2.2 eq 23 access-list 100 deny tcp 3.3.3.0 0.0.0.255 any eq 80 int FastEthernet0/0 ip access-group 100 out