📄 isl.htm
字号:
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
<meta name="ProgId" content="FrontPage.Editor.Document">
<title>Show Lab</title>
<style>
<!--
li.MsoNormal
{mso-style-parent:"";
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";
margin-left:0in; margin-right:0in; margin-top:0in}
-->
</style>
</head>
<body>
<script language="Javascript">
<!--
function printpage() {
if (window.print)
window.print()
else
alert("Sorry, your browser doesn't support this feature.");
}
//-->
</script>
<FORM>
<INPUT TYPE="button" VALUE="Print this page" onClick="printpage()">
</FORM>
<p><font face="Arial, Arial, Helvetica" color="#008000" size="4"><b>Lab:
Introduction to Inter-Switch Link routing</b></font></p>
<p><font face="Arial, Arial, Helvetica"><i>Objective</i>: This lab will teach you how to configure your router with sub interfaces and
route between VLANs on a switch. <br>
<i>Lab Equipment</i>: You will be using eRouter 1, Switch 1, PC
1 and PC 2</font></p>
<p><font face="Arial, Arial, Helvetica"><b><font color="#FF0000">IMPORTANT</font></b>! You will need to load a new
topology file to complete this lab. To do this you must exit the program, open
it up again and on the "Choose your Topology" screen select the third option,
"Load Simulator using saved Topology." When the open screen comes up select the VLANs.top file inside of your Boson
NetSim directory.</font></p>
<p> </p>
<p class="MsoPlainText" align="center">
<img border="0" src="vlans.jpg" width="490" height="457"></p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Our goal is to configure separate VLANs on switch 1 for ePC1
and ePC2. We will then make sure these VLANs do not work by trying to ping from
ePC 1 to ePC2. After we verify that our pings can not go anywhere we will setup ISL encapsulation on our router and enable trunking on the Switch so that our
PC's
can communicate again.</p>
<p><font color="#FF00FF"><b>1. </b> </font>The first thing we
must do is assign ip addresses to all the interfaces. We will be using
subinterfaces on eRouter 1. Connect to eRouter 1 and enable FastEthernet 0/0
interface. Then create two subinterfaces .1 and .2 with IP addresses <b>1.1.1.1 255.255.255.0</b>
and <b>1.1.2.1 255.255.255.0</b>.<br>
<br>
<select size="1" name="D1">
<option selected>- Click here to View Answer -</option>
<option>Router>en</option>
<option>Router#conf t</option>
<option>Router(config)#hostname eRouter1</option>
<option>eRouter1(config)#interface Fast0/0</option>
<option>eRouter1(config-if)#no shut</option>
<option>eRouter1(config-if)#exit</option>
<option>eRouter1(config)#int fast 0/0.1</option>
<option>eRouter1(config-if)#ip add 1.1.1.1 255.255.255.0</option>
<option>eRouter1(config-if)#exit</option>
<option>eRouter1(config)#int fast 0/0.2</option>
<option>eRouter1(config-if)#ip add 1.1.2.1 255.255.255.0</option>
<option>eRouter1(config-if)#end</option>
</select> </p>
<p><font color="#FF00FF"><b>2.</b></font> Next connect to ePC1 and assign an IP of 1.1.1.2 255.255.255.0 with default
gateway of 1.1.1.1. <br>
<br>
<select size="1" name="D1">
<option selected>- Click here to View Answer -</option>
<option>C:>winipcfg</option>
</select><br>
<br>
<font color="#FF00FF"><b>3.</b></font> Connect to ePC2 and assign an IP of 1.1.2.2 255.255.255.0 with default gateway
of 1.1.2.1. </p>
<p>
<select size="1" name="D1">
<option selected>- Click here to View Answer -</option>
<option>C:>winipcfg</option>
</select></p>
<p><font color="#FF00FF"><b>4. </b></font>Now that we have all IP addresses setup lets try and see where we can
ping. From ePC1 we should be able to ping ePC2 and eRouter1. From ePC2 we should be
able to ping ePC1 and eRouter1. From eRouter1 we should be able to ping ePC1 or
ePC2. <br>
<br>
ePC1<br>
<select size="1" name="D1">
<option selected>- Click here to View Answer -</option>
<option>C:>ping 1.1.1.1</option>
<option>C:>ping 1.1.2.2</option>
</select></p>
<p>ePC2<br>
<select size="1" name="D1">
<option selected>- Click here to View Answer -</option>
<option>C:>ping 1.1.2.1</option>
<option>C:>ping 1.1.1.2</option>
</select></p>
<p>eRouter1<br>
<select size="1" name="D1">
<option selected>- Click here to View Answer -</option>
<option>C:>ping 1.1.1.2</option>
<option>C:>ping 1.1.2.2</option>
</select></p>
<p class="MsoNormal"><font color="#FF00FF"><b> 5.</b></font> Connect to Switch1 and create the
VLANs that we will be using. We need to have two VLANs, one for ePC1 and one for ePC2. <br>
<br>
<select size="1" name="D1">
<option selected>- Click here to View Answer -</option>
<option>>en</option>
<option>#config t</option>
<option>(config)#vlan 2 name VLAN2</option>
<option>(config)#Vlan 3 name VLAN3</option>
</select></p>
<font color="#FF00FF"><b>6. </b></font>After we have created the VLANs we need to assign the
VLANs to the ports the pc抯 are connected to. Port 1 will be vlan 2 and port
2 will be vlan 3.
<p>
<select size="1" name="D1">
<option selected>- Click here to View Answer -</option>
<option>(config)#int e0/1</option>
<option>(config-if)#vlan-membership static 2</option>
<option>(config-if)#exit</option>
<option>(config)#int e0/2</option>
<option>(config-if)#vlan-membership static 3</option>
<option>(config-if)#exit</option>
</select></p>
<p><font color="#FF00FF"><b>7.</b></font> To test and see if the VLANs are working try connecting
back to ePC1 and see if you can ping ePC2 now. You should not be able to because
they are on separate VLANs. </p>
<select size="1" name="D1">
<option selected>- Click here to View Answer -</option>
<option>C:>ping 1.1.2.2</option>
</select><br>
<p><font color="#FF00FF"><b>8.</b></font> Now that we have setup our VLANs we need to turn on
trunking for our Fast Ethernet port that is connected to eRouter1. Trunking
allows a single port to carry multiple VLANs. Trunk links are used to
transport multiple VLANs between devices on your network. Trunking is only
supported on Fast Ethernet interfaces. Trunking has two different
encapsulation methods, ISL and 802.1q. For more information on trunking
and isl visit:
<a style="color: blue; text-decoration: underline; text-underline: single" target="_blank" href="http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/sw_5_5/cnfg_gd/e_trunk.htm">http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/sw_5_5/cnfg_gd/e_trunk.htm</a>
</p>
<select size="1" name="D1">
<option selected>- Click here to View Answer -</option>
<option>(config)#interface Fast 0/26</option>
<option>(config)#Trunk on</option>
</select><p><b><font color="#FF00FF">9.</font></b> Now we should have our switch configured. Even though
the switch is transporting the packets for both VLANs to the Router we need to
tell the router how to accept the packets. Connect to eRouter 1 and set
interface FastEthernet 0/0.1 encapsulation to ISL with vlan1. FastEthernet
0/0.2 needs to also have ISL encapsulation with vlan2. </p>
<p>
<select size="1" name="D1">
<option selected>- Click here to View Answer -</option>
<option>Router#conf t</option>
<option>Router(config)#hostname eRouter1</option>
<option>eRouter1(config)#interface Fast0/0.1</option>
<option>eRouter1(config-if)#encap isl 2</option>
<option>eRouter1(config-if)#exit</option>
<option>eRouter1(config)#interface Fast0/0.2</option>
<option>eRouter1(config-if)#encap isl 3</option>
</select></p>
<b><font color="#FF00FF">10.</font></b> You have completed the entire configuration needed for
the lab. Now let抯 test and see if we can ping everyone again. From ePC1
<p>
<select size="1" name="D1">
<option selected>- Click here to View Answer -</option>
<option>C:>ping 1.1.1.1</option>
<option>C:>ping 1.1.2.1</option>
<option>C:>ping 1.1.2.2</option>
</select></p>
<font color="#FF00FF"><b>11. </b></font> From ePC2 ping ePC1 and eRouter1<p>
<select size="1" name="D1">
<option selected>- Click here to View Answer -</option>
<option>C:>ping 1.1.1.2</option>
<option>C:>ping 1.1.2.1</option>
<option>C:>ping 1.1.1.1</option>
</select></p>
<p><b><font color="#FF00FF">12. </font></b>Connect back to the switch and lets
view our vlan assignments using some new show commands.
<font face="Terminal" size="2">Show vlan</font> and
<font face="Terminal" size="2">show vlan-membership</font><b>
</b>are two different ways to view the VLAN port assignments for the switch.</p>
<p><select size="1" name="D1">
<option selected>- Click here to View Answer -</option>
<option>(config-if)#end</option>
<option>#show vlan</option>
<option>#show vlan-membership</option>
</select></p>
<p><b><font color="#FF00FF">13.</font></b> If all your pings were successful,
congratulations you have finished the lab.</p>
<p class="MsoNormal">Let抯 take a minute to go over what we actually did. In
our network we have a lot of internal traffic. Some traffic is concentrated in
the software department and some is concentrated in the accounting department.
We have decided to create separate VLANs to help manage that traffic. (Remember
VLANs break up broadcast domains on the layer 2 switches.) That way the traffic
for the software department does not have to be heard by the accounting
department. The only problem we encountered is when we want to talk to the
Accounting department from the software department. To do this we had to get a
router involved. On the router we created subinterfaces (one for each subnet/vlan)
and told the router to encapsulate the packets with ISL (this allowed us to
communicate with the fast Ethernet port on the switch that is trunking). Now we
have the switches breaking up our broadcast domains and the router is helping
the VLANs communicate between each other.</p>
<p> </p>
<p><font face="Arial" size="2"><span class="724482219-24092001">Copyright (c)
1998-2003 Boson Software, Inc. All Rights Reserved.</span></font></p>
</body>
</html>⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -