Documents NETW240 Wk4 Lab
NETW240 Week 4 Lab: TCP/IP LAN Networking
Lab Scenario
Assignment
Configure static networking on a Linux PC (host11) so that it can communicate with the other server (host12) in your lab environment.
Story
You will configure the second interface (eth1) with static networking so that it can communicate with host12.
Conditions
You have remote access to host11. You will not have remote access to host12 because it is already configured and there is nothing for you to do to with it. Both host11 and host12 use DHCP on their first interface (eth0). This interface is used by the lab environment and should not be modified. Both host11 and host12 are unable to communicate over this interface.
Virtual Machine Login Information
Username: vlab
Password: password
Lab Diagram
During your session you will have access to the following lab configuration.
Connecting to your lab
In this module you will be working on the following equipment to carry out the steps defined in each exercise.
WINCONSOLE (Management Server)
HOST11 (Linux Server)
HOST12 (Linux Server)
Each exercise will detail which console you are required to work on to carry out the steps.
To start simply click on the named Server from the device list (located on the left hand side of the screen) and click the Power on from the in tools bar. In some cases the devices may power on automatically.
During the boot up process an activity indicator will be displayed in the name tab:
Black - Powered Off
Orange - Working on your request
Green - Ready to access
If the remote console is not displayed automatically in the main window (or popup) click the Connect icon located in the tools bar to start your session.
If the remote console does not appear please try the following option:
Switch between the HTML 5 and Java client versions in the tools bar.
In the event this does not resolve your connectivity problems please visit our Help / Support pages for additional resolution options.
Suggested Approach
The
Lab Scenario
Assignment
Configure static networking on a Linux PC (host11) so that it can communicate with the other server (host12) in your lab environment.
Story
You will configure the second interface (eth1) with static networking so that it can communicate with host12.
Conditions
You have remote access to host11. You will not have remote access to host12 because it is already configured and there is nothing for you to do to with it. Both host11 and host12 use DHCP on their first interface (eth0). This interface is used by the lab environment and should not be modified. Both host11 and host12 are unable to communicate over this interface.
Virtual Machine Login Information
Username: vlab
Password: password
Lab Diagram
During your session you will have access to the following lab configuration.
Connecting to your lab
In this module you will be working on the following equipment to carry out the steps defined in each exercise.
WINCONSOLE (Management Server)
HOST11 (Linux Server)
HOST12 (Linux Server)
Each exercise will detail which console you are required to work on to carry out the steps.
To start simply click on the named Server from the device list (located on the left hand side of the screen) and click the Power on from the in tools bar. In some cases the devices may power on automatically.
During the boot up process an activity indicator will be displayed in the name tab:
Black - Powered Off
Orange - Working on your request
Green - Ready to access
If the remote console is not displayed automatically in the main window (or popup) click the Connect icon located in the tools bar to start your session.
If the remote console does not appear please try the following option:
Switch between the HTML 5 and Java client versions in the tools bar.
In the event this does not resolve your connectivity problems please visit our Help / Support pages for additional resolution options.
Suggested Approach
The