Enterasys Educational Services
Enterasys Educational Services
Enterasys Networks reserves all rights to its materials and the content of the
materials. No material provided by Enterasys Networks to a Partner (or Customer, etc.)
may be reproduced or transmitted in any form or by any means, electronic or
mechanical, including photocopying and recording, or by any information storage or
retrieval system, or incorporated into any other published work, except for internal use
by the Partner and except as may be expressly permitted in writing by Enterasys
Networks.
This document and the information contained herein are intended solely for
informational use. Enterasys Networks makes no representations or warranties of
any kind, whether expressed or implied, with respect to this information and
assumes no responsibility for its accuracy or completeness. Enterasys Networks,
hereby disclaims all liability and warranty for any information contained herein and
all the material and information herein exists to be used only on an "as is" basis.
More specific information may be available on request. By your review and/or use of
the information contained herein, you expressly release Enterasys from any and all
liability related in any way to this information. A copy of the text of this section is
an uncontrolled copy, and may lack important information or contain factual errors.
All information herein is Copyright Enterasys Networks. All rights reserved. All
information contain in this document is subject to change without notice.
http://www.enterasys.com/constants/terms-of-use.aspx
Routing and Wireless Boot Camp Local Lab Guide
Contents
Lab 1: Basic Routing Configuration ............................................................................... 1
Section A: Start of Lab: Initial Connection ...................................................................... 2
Section B: Prepare the Switch/Router for the Lab .......................................................... 3
Section C: Create VLANs ................................................................................................ 3
Section D: Configure Router VLAN Interfaces with IP Addresses ................................. 4
Section E: Test Network Connectivity ............................................................................. 6
Section F: Static Route Network Setup ........................................................................... 7
Section G: Configure Router VLAN Interfaces with IP Addresses ................................. 9
Section H: Test Network Connectivity ............................................................................. 9
Section I: Defining Static Routes ..................................................................................... 9
Section J: Test Network Connectivity............................................................................ 10
Section K: Remove Static Route Setup ........................................................................ 10
Section L: Test Network Connectivity ........................................................................... 10
Section M: RIP Route Setup.......................................................................................... 10
Section N: Test Network Connectivity ........................................................................... 12
Section O: DHCP Relay (IP helper-address) ................................................................ 13
Section P: Test PC-Connectivity ................................................................................... 15
Lab 2: OSPF Routing Configuration ............................................................................. 16
Section A: New Configuration Setup ............................................................................. 19
Section B: Create a Router ID ....................................................................................... 21
Section C: Create an OSPF instance............................................................................ 22
Section D: Add Networks ............................................................................................... 23
Section E: Test Network Connectivity ........................................................................... 24
Section F: Set the Designated Router........................................................................... 24
Section G: OSPF show commands (Router A,B and C) .............................................. 25
Section H: Redistribution of Static Routes .................................................................... 26
Section I: Setting Secondary Addresses ....................................................................... 28
Section J: Summarization .............................................................................................. 29
Section K: Define Stub Area .......................................................................................... 30
Section L: Authentication- Simple ................................................................................. 33
Section M: Authentication- MD5 .................................................................................... 34
Section N: Verify Configuration ..................................................................................... 34
Equipment
For this lab you will need:
Two Enterasys routers (this lab was written with a C5 and an SSA
Three PCs
Objectives
When you finish this lab you will be able to:
NOTE: All screen shots included in this lab exercise are for illustrative purposes only
and may not accurately reflect the actual settings on your switch. Please follow the
procedural explanations in the text when you perform configurations in this lab.
NOTE: The CLI structure differs slightly between the S/K series and the Stackable
Switches. Not all CLI Commands in these labs work on all switches. Use the ?
command from the CLI to determine which specific command will work on the switch
you are configuring.
As you proceed through this section of the lab, you will configure your network
according to the table and diagram below.
PC-A
VLAN 10
172.16.1x1.11/24
172.16.1x1.101/24
GW 172.16.1x1.101
ge.1.2
Port 2
Router A
Port 4
PC-B
172.16.1x3.11/24 VLAN 3
172.16.1x3.101/24
GW 172.16.1x3.101
ge.1.4
Enter Y.
5. Set a prompt for your Router.
> set prompt Router A
6. Disable spanning tree, LACP, and GVRP globally.
> set gvrp disable
> set lacp disable
> set spantree stpmode none
VLAN: 10 NAME:
VLAN Type: Permanent
Egress Ports
ge.1.2
Forbidden Egress Ports
None.
Untagged ports
ge.1.2
RouterA(su)->
Note: show vlan will show the ports that are configured and active;
show vlan static will show the configured ports even if they are not
currently active.
In these labs you will use an IP addressing scheme based upon your Student
Group number, as in the table below.
1. Enter router mode (Not required on S and K Series firmware 7.0 and higher. For
these routers, enter configuration mode directly from the Layer 2 prompt by
typing configure.)
Router A> router
2. Enter privileged mode (not required S and K 7.0 and higher. For these routers,
enter configuration mode directly from the Layer 2 prompt by typing
configure.)
Router A> enable
3. For the S and K7.0+ set the interface IP addresses and IP forwarding.
Router A(su)->config
Router A(su-config)->set ip address 172.16.1x1.101 mask
255.255.255.0 interface vlan.0.10
Router A(su-config)-> interface vlan.0.10
Router A(su-config-intf-vlan.0.2)->ip forwarding
For all other devices including the C-series, enter config mode and add an IP
address to the VLAN interface.
RouterA> router# configure
RouterA> router(Config)# interface vlan 10
RouterA> router(Config-if(Vlan-vid))# ip address
172.16.1X1.101 255.255.255.0
4. Enter no shutdown to enable the interface.
RouterA> router(Config-if(Vlan-vid))# no shutdown
5. Type exit to return to router mode.
PC-A PC-B
172.16.1x1.11/24 172.16.1X3.11/24
172.16.1x1.101 GW 172.16.1X3.101 GW
3. Ping the directly connected default Gateway router to test the local connectivity.
4. Ping your neighbor's PC to check route connectivity.
5. From Router A router mode enter the following command:
RouterA>router# show ip route
In this portion of the lab you will set up static routes between two routers: Router
A and Router C. This lab was written using two SSAs; you may need to modify
your CLI commands if you are using a stackable switch as one or both of your
routers.
PC-A
VLAN 10
172.16.1x1.11/24
172.16.1x1.101/24
GW
ge.1.2
172.16.1x1.101
Port 2
Router A
VLAN 3
172.16.1x3.103/24
Port ge.1.5 ge.1.5
Router C
Port 4
PC-D
VLAN 4
172.16.1x4.22/24
172.16.1x4.103/24
GW
ge.1.4
172.16.1x4.103
Router A config
1. Add port ge.1.5 to VLAN 3.
set port vlan ge.1.5 3 modify-egress
Router C configuration
1. Set the Prompt to Router C
set prompt Router C
2. Disable Spanning Tree and GVRP globally.
S/K-Series > set gvrp disable
> set spantree stpmode none
All others
> set spantree disable
3. Create VLAN 3 and VLAN 4 on Router C.
set vlan create 3
set vlan create 4
4. Assign port 4 to VLAN 4.
On Router C:
1. Enter router mode. (Not required for S & K-7.0+)
2. Enter enable mode. (Not required for S & K-7.0+)
3. Enter configuration mode.
4. From config mode enter the VLAN interface 3 to add an IP address.
Router C(su-config)interface vlan.0.3
5. From the VLAN interface enter the IP address with a 24 bit mask.
ip address 172.16.1X3.103 255.255.255.0
6. Enter ip forwarding to enable IP forwarding on the interface.
7. Enter no shutdown to enable the interface.
8. Type exit to return to router mode
9. Configure VLAN interface 4 with IP address 172.16.1X4.103/24 using the same
process.
A static route will allow the system to send traffic destined for a specific network out
a specific interface that is manually defined.
1. Add the static routes. From Router A, access config mode and enter the
following command:
1. Remove the static routes. From Router A, access config mode and enter the
following command:
no ip route 172.16.1X4.0 255.255.255.0 172.16.1X3.103
2. From Router C, access config mode and enter the following command:
no ip route 172.16.1X1.0 255.255.255.0 172.16.1X3.101
1. Verify that PC-A and PC-D do not have ping connectivity at this time.
You will be using the same network setup used for static routes. Using the IP
addresses that have been assigned to the VLAN interfaces; you will enable RIP, and
then identify the networks that will use RIP.
2. Enable RIP globally from config mode using the router rip command.
On the C5
RouterA/C> router
RouterA/C>router>enable
RouterA/C>router#config
RouterA/C> router(Config) # router rip
On the S/K-Series:
RouterA/C(su)->configure
RouterA/C(su-config)->router rip
For S/K Switch/Routers set the networks to be advertised by RIP from config mode.
PC-A
VLAN 10
172.16.1x1.11/24
172.16.1x1.101/24
GW
ge.1.2
172.16.1x1.101
Port 2
Router A
VLAN 3
172.16.1x3.103/24
Port ge.1.5 ge.1.5
Router C
Port 4
PC-D
VLAN 4
DHCP Enabled
172.16.1x4.103/24
ge.1.4
1. Using your previously configured network topology (as shown above), set an IP
helper-address (172.16.1x1.11), on Router C, VLAN 4. At the interface level,
issue the command:
Router C(su-config-intf-vlan.0.4)->ip helper-address
172.16.1x1.11
In Windows XP:
c. Highlight and right click My Network Places icon.
d. Select Properties. The Network Connections window opens.
e. From the network connections window, open Local Area Connection.
f. From Local Area Connection Status window, click the Properties tab.
g. From Local Area Connection Properties window, scroll down to Internet
Protocol (TCP/IP) and open Internet Protocol (TCP/IP).
h. From Internet Protocol (TCP/IP) Properties window select Obtain an IP
address automatically, click OK.
In Windows 7:
a. Open Network Connections by clicking the Start button , and then clicking
Control Panel. In the search box, type adapter, and then, under Network and
Sharing Center, click View network connections.
b. Right-click the connection that you want to change, and then click Properties.
If you're prompted for an administrator password or confirmation, type the
password or provide confirmation.
c. Click the Networking tab. Under This connection uses the following items,
click Internet Protocol Version 4 (TCP/IPv4), and then click Properties.
d. Click Obtain an IP address automatically, and then click OK.
6. Verify PC-D has received an IP address in the 172.16.1X4.0/24 range, with a
default gateway address of 172.16.1X4.103.
e. From your Windows desktop, select StartRun, and enter cmd, click OK.
f. At command prompt window, enter ipconfig /all.
1. From PC-D, ping the directly connected default Gateway router (172.16.1X4.103)
to test your local connectivity.
2. Ping PC-A (172.16.1X1.11) to check route connectivity.
End of Lab 1
Resources/Tools
For this lab you will need:
Three Enterasys routers (this lab was written with two SSAs and one C5)
Two PCs
Objectives
At the end of this lab you will be able to:
Lab Setup
At the end of this lab you will have set up your network according to the table and
diagram below.
Router A, VLAN
172.16.1x1.101/24
Interface 10
Router A, VLAN
172.16.2x.101/24
Interface 2x
Router A, port ge.1.2 PC-A
Router C, Interface
172.16.3x.103/24
VLAN 3x
Router C, Interface
172.16.1x4.103/24
VLAN 4
Router C, port ge.1.4 PC-D
PC-A
172.16.1x1.11/24
GW 172.16.1x1.101
Area 1
VLAN 10
172.16.1x1.101/24
Port ge.1.2
Router A
Port ge.1.3 VLAN 2x
172.16.2x.101/24
Backbone Area 0
VLAN 2x
Port ge.1.3 172.16.2x.102/24
Router B
Port ge.1.6 VLAN 3x
172.16.3x.102/24
VLAN 3x
Area 2
172.16.3x.103/24
Port ge.1.6
Port ge.1.4
Router C
VLAN 4
172.16.1x4.103/24
PC-D
172.16.1x4.22/24
GW 172.16.1x4.103
The steps to route using OSPF between the IP VLANs are as follows:
Define two VLANs on each Switch.
Add IP addresses to each VLAN.
Create OSPF Instances.
Add OSPF Networks and Areas.
Enter Y.
2. Cable the network as shown in the table and diagram above.
3. Set your prompts on all three switches.
4. Disable Spanning Tree on all three switches.
5. Create VLANs on your routers according to the table below, where X is your
Student Group number.
Router B 2x 3x
Router C 3x 4
6. Configure the router ports to attach to the correct VLANs according to the table
below, where X is your Student Group number.
10. From the VLAN interface enter the IP address with a 24 bit mask
11. Enter no shutdown to enable the interface.
12. Enter the IP Forwarding command for S/K-Series routers to enable IP
Forwarding for interface. (Not required on the C-Series.)
13. Type exit to return to configuration mode.
14. Configure all of the VLAN interfaces using the same process.
15. Configure your loopback address to advertise into OSPF using the same
process. This will allow you to reach the switchs loopback address via OSPF for
management purposes.
Router B 2 2.2.2.2/32
Router C 3 3.3.3.3/32
Note: For the S/K-Series router, you do not need to enter router mode. Simply
enter config mode, and issue same sequence of commands shown above to
create your loopback address. Be sure to include the ip forwarding command.
2. On the S-series:
Router A(su-config)->interface loop.0.1
Router A(su-config-intf-loop.0.1)->ip address 1.1.1.1
255.255.255.255
Router A(su-config-intf-loop.0.1)->ip forwarding
Router A(su-config-intf-loop.0.1)->no shut
Note: For S/K-Series routers using firmware 7.0+ the router-id is configured under
the OSPF instance. Therefore, you must create the OSPF instance first, and then
enter the router-id.
For C-Series routers, you should create your router id before you create your OSPF
instance.
3. Create an OSPF instance on each router, and add the router-id for the S/K-
Series platform:
On C5:
Router>router(Config)# router id 2.2.2.2
Router>router(Config)# router ospf 10
On S/K-Series:
Router(su-config)->router ospf 10
Router(su-config-ospf-10)->router-id 1.1.1.1
Router(su-config-ospf-10)->
Example of a C5 (Router B)
RouterB> router(config)# interface vlan 2X
RouterB> router(config-if(Vlan 2X))# ip ospf enable
RouterB> router(config-if(Vlan 2X))# ip ospf areaid
0.0.0.0
RouterB> router(config-if(Vlan 2X))# exit
1. Attach the PCs as shown in the diagram at the beginning of the lab. Use the IP
addresses in the table and diagram.
2. From PC-A and PC-D.
a. Ping the directly connected default Gateway router to test your local
connectivity.
b. Ping your neighbor's PC to check route connectivity.
3. Troubleshoot any connectivity issues that arise.
4. If OSPF has learned the wrong routes you can clear the OSPF processes.
C5:
RouterA/B/C>router# clear ip ospf process {process-number}
S/K:
RouterA(su)->clear ip ospf process pid {process-number}
1. Check to see who is the Designated Router for area 0.0.0.2 by using the show
ip ospf interface command on Router B and Router C.
1) For VLAN 3X, which router is the DR?_______________
2) For VLAN 3X, which router is the BDR?______________
2. Change the router priority value to affect the Designated Router (DR) and Back-
up Designated Router (BDR) values. The router with the highest value will
become the DR.
RouterA> router(config-if(Vlan 2X) # ip ospf priority 50
RouterB> router(config-if(Vlan 3X) # ip ospf priority 255
RouterC> router(config-if(Vlan 3X) # ip ospf priority 0
3. Enter the show ip ospf interface command to view results of setting
OSPF interface priority.
show ip ospf interface
PC-A
172.16.1x1.11/24
GW 172.16.1x1.101
Area 1
VLAN 10
172.16.1x1.101/24
Port ge.1.2
Router A
Port ge.1.3 VLAN 2x
172.16.2x.101/24
Backbone Area 0
VLAN 2x
Port ge.1.3 172.16.2x.102/24
Router B
Port ge.1.6 VLAN 3x
172.16.3x.102/24
VLAN 3x Area 2
172.16.3x.103/24
Port ge.1.6
Port ge.1.4
Router C
VLAN 4 Static Routes
172.16.1x4.103/24 112.x.1.0/24
112.x.2.0/24
PC-D 112.x.3.0/24
172.16.1x4.22/24
GW 172.16.x4.103
Add the static routes shown in the diagram to your network. Once you have
created static IP addresses, redistribute the routes. Redistribution allows your
router to send the static routes to the remote routing tables.
1. Create static routes from router config mode on Router C. Add static routes as
shown below, where X is your student group number:
2. Verify that Router B does not know about the static routes from Router C by
using:
show ip route
3. To redistribute static routes into OSPF, enter router ospf 10 mode on Router C.
Use the redistribute static command.
Use the redistribute static subnets command for the C-Series
Use the redistribute static command for the S/K-Series
Example for C-Series
Router C<su>->router<Config-router># redistribute static subnets
Example for S/K-Series:
RouterC(su-config-ospf-10)->redistribute static
4. Check that the static routes from Router C have been redistributed to Router B.
Verify this by issuing the show ip route command on Router B.
PC-A
172.16.1x1.11/24
GW 172.16.1x1.101
Area 1
VLAN 10
172.16.1x1.101/24
Secondary Port ge.1.2
Addresses Router A
20.x.1.0/24 Port ge.1.3 VLAN 2x
20.x.2.0/24 172.16.2x.101/24
20.x.3.0/24
Backbone Area 0
VLAN 2x
Port ge.1.3 172.16.2x.102/24
Router B
Port ge.1.6 VLAN 3x
172.16.3x.102/24
VLAN 3x Area 2
172.16.3x.103/24
Port ge.1.6
Port ge.1.4
Router C
VLAN 4 Static Routes
172.16.1x4.103/24 112.x.1.0/24
112.x.2.0/24
PC-D 112.x.3.0/24
172.16.1x4.22/24
GW 172.16.x4.103
1. Set multiple secondary addresses that will be used for route summarization.
Configure these secondary addresses on Router A.
Router A(su-config)->interface vlan.0.10
Router A(su-config-intf-vlan.0.10)->ip address 20.X.1.1
255.255.255.0 secondary
Router A(su-config-intf-vlan.0.10)->ip address 20.X.2.1
255.255.255.0 secondary
Section J: Summarization
Summarization is used to reduce size of your LS database and Route tables. This is
performed on the Area Border Router. You will examine Router Bs OSPF
database, then implement route summarization on Router A, and then recheck
Router Bs database.
1. Examine the OSPF database on Router B.
Router B>router(config-)# show ip ospf database
5) How many entries start with
20.X.x.x?_________________________________
2. Implement route summarization on Router A.
Router A(su-config)->router ospf 10
Router A(su-config-ospf-10)->area 0.0.0.1 range 20.X.0.0
255.255.0.0
Router A(su-config-ospf-10)->exit
3. Recheck the OSPF database on Router B.
Router B(su)->router#show ip ospf database
6) How many entries start with
20.X.x.x?_________________________________
2. Make note of the route table and OSPF database on Router C prior to converting
area 2 to a stub. Issue the commands show below:
RouterC(su)->router#show ip route
Number of routes = 10
Router C(su-config)->
Note that specific routes exist to 172.16.1x1.0/24, 172.16.2x.0/24 & 20.x.0.0/16 all
your interarea routes.
OSPF Process Id 10
OSPF Process Id 10
Note that summary LSAs (LS Type 3 Advertisements) are present for
172.16.1x1.0/24, 172.16.2x.0/24 & 20.x.0.0/16.
Router B(su)->router#config
Enter configuration commands:
Router B(su)->router(Config)#router ospf 10
Router B(su)->router(Config-router)#area 2 stub no-summary
Router B(su)->router(Config-router)#
(Note: Pings will fail momentarily while you configure your stub area.)
4. Verify area 2 has been set to stub area by issuing the show ip ospf
command on Router B and Router C.
5. Clear IP OSPF process on Router C
Router C(su-config)->clear ip ospf process
6. Re-issue the show ip route, and show ip ospf database commands.
Routes to 172.16.1x1.0/24, 172.16.2x.0/24 & 20.x.0.0/16 should no longer be
present in the route table. Only a single OSPF default route 0.0.0.0/0 will be
visible as shown below:
Number of routes = 8
Router C(su-config)->
OSPF Process Id 10
Note Once your stub area is up, pings will succeed based on the OSPF injected default
route.
End of Lab 2
Resources/Tools
For this lab you will need:
One Enterasys router (this lab was written with an SSA)
Two PCs
Objectives
When you complete this lab you will be able to:
Create an ACL via the Router CLI
Test your ACL
Create an ACL via NetSight ACL Manager
Test your ACL
Network
IP Address/Mask Connection
Component
Router A port
PC-A 172.16.1x1.11/24
ge.1.2
Router A port
PC-B 172.16.1x3.11/24
ge.1.4
Router A Interface
172.16.1x1.101/24
VLAN 2
Router A Interface
172.16.1x3.101/24
VLAN 3
PC-A
VLAN 10
172.16.1x1.11/24
172.16.1x1.101/24
GW
ge.1.2
172.16.1x1.101
Port 2 Router A
Port 4 S/K Series
PC-B
VLAN 3
172.16.1x3.11/24
172.16.1x3.101/24
GW
ge.1.4
172.16.1x3.101
Network
Port VLAN
Component
Router A Port ge.1.2 VLAN 10
Network
VLAN IP Address
Component
Router A VLAN 10 172.16.1x1.101/24
RouterA(su-config)->interface vlan 10
RouterA(su-config-intf-vlan.0.10)->ip access-group denyPCA
in
RouterA(su-config-intf-vlan.0.10)->exit
3. Start continuous Pings between PC-A and PC-B, (pings should be failing).
4. Ensure that PC-A cannot ping to the router.
5. Show the access list.
RouterA(su-config)->show access-lists
1. Add an extended numbered ACL to stop ICMP from any source on VLAN 3.
2. Check the continuous Pings between PCs on VLAN 10 and VLAN 3. (They
should fail).
3. Ensure that you can telnet from PC-B on VLAN 3 to the router.
4. Show the access list:
show access-lists 100
PC-A
VLAN 10
172.16.1x1.11/24
172.16.1x1.101/24
GW
ge.1.2
172.16.1x1.101
Port 2 Router A
Port 4 S/K Series
PC-B
VLAN 3
172.16.1x3.11/24
172.16.1x3.101/24
GW
ge.1.4
172.16.1x3.101
7. ACL Manager functionality is available from the ACL Manager Tab in the main
NetSight Console window.
8. Select the ACL Manger tab. From ACL Manager, you can access the ACL Editor
to create a new ACL or to modify an existing ACL.
9. If you do not see your device in the ACL Manager view, right click on your router
in the device tree and click Refresh Device Data.
10. To open the ACL Editor, click the ACL Editor Button located on upper right side
of ACL Manager Screen.
1. From the ACL Editor window: in the leftpanel tree, highlight the cataloged folder,
right click and select Create S/K/N 7.x+.
Note: Do NOT choose an N-Series ACL, even if you are working on an N-Series
switch. Beginning with version 7.0, the Enterasys N-Series switch uses S-Series
ACLs.
2. Type the name for your new ACL (use ACL5) and click OK. (ACL names must
be alphanumeric characters only.)
3. In the leftpanel tree, select/highlight ACL5.
4. In the rightpanel Editor tab, click the New button.
5. Set the parameters for your rule:
a. Action: Deny
b. Rule Type: TCP
c. Source Address:172.16.1x3.0/24
d. Destination Address: Any
e. Source Port: Any
f. Destination Port: = (21) FTP
6. Click OK. The window closes and the rule appears in the leftpanel tree and
right-panel display of the Editor.
7. Using the previous steps, create a rule for an explicit permit all for ACL5. Once
you have created the rule, click save and close the editor.
1. From the ACL Manager window: right-click the device in the Console leftpanel
tree that the ACL will be written to (in this case, 172.16.1X1.101) and click
Import ACL Data.
2. Select the Interface Assignment view using the radio button at the top of the tab.
3. Select the device interface where you want to assign your ACL. (Interface VLAN
3). Note you may need to refresh the view to see your router interfaces.
4. Click on the Show Table Editor Button to display the table editor row. (The button
is located on upper right side of ACL Manager Window.)
5. In the Table Editor Row (displayed at the bottom of the ACL Manager Window)
click on the Inbound ACL column to display the ACL Selection window. Expand
the folders to select the desired ACL.
8. Click on the Enforce button to write your changes to the device's active
configuration.
1. Using continuous pings from PC-A, check route connectivity. Should the pings
succeed?
2. Initiate an ftp session from PC-B to PC-A (172.16.1X1.11), username: training,
password: training. Ensure that you cannot ftp to PC-A from PC-B.
Note: FileZilla is running on PC-A.
End of Lab 3
Resources/Tools
For this lab you will need:
Two Enterasys S/K-series routers
Two PCs
Objectives
After you complete this lab, you will be able to:
Create a Policy Based Route (PBR)
Test your PBR
At the end of the lab you will have set up your network according to the table and
diagram below.
Network
IP Address/Mask Connection
Component
172.16.1x1.11/24 Router A
PC-A
GW 172.16.1x1.101 Port ge.1.2
172.16.x4.22/24 Router C
PC-D
GW 172.16.x4.103 Port ge.1.4
Router A
172.16.x5.101/24
VLAN 5
Router A
172.16.1x1.101
VLAN 10
Router A Router C
Port ge.1.5 Port ge.1.5
Router C
172.16.1x4.103/24
VLAN 4
Router C
172.16.x5.103/24
VLAN 5
Router C Router C
Port ge.1.5 Port ge.1.5
PC-A
172.16.1X1.11/24
VLAN 10
172.16.1X1.101/24
Port 2
Router A
Port 5
.101
VLAN 5
172.16.X5.0/24
Port 5
.103
Router C
Port 4
PC-D
172.16.1X4.22/24
VLAN 4
172.16.1X4.103/24
1. Ping between PC-A and PC-D to check route connectivity. You should not be
able to ping between the PCs at this time.
2. Create a route map entry give the route map a number of 101.
Router C(su-config)->route-map policy 101
3. Check to see if the ACL has any matches.
Router C(su-config-route-map-pbr)->match ip address 101
4. Set the route for the match
Router C(su-config-route-map-pbr)->set next-hop
172.16.X5.101
Router C(su-config-route-map-pbr)->exit
5. Select the VLAN to attach the route using the policy command
Router C(su-config)->interface vlan 4
Router C(su-config-intf-vlan.0.4)->ip policy route-map 101
1. Check connectivity between VLAN 2 and VLAN 4, pings should now succeed
between PC-A and PC-D.
2. Show the access list.
3. Show the route map.
4. Show ip policy.
End of Lab 4
Resources/Tools
For this lab you will need:
Two Enterasys routers (this lab was written with two SSAs)
Three PCs
Objectives
At the end of this lab you will be able to:
Configure PIM-SM
Verify your configuration with VLC Multicast movies
Network
IP Address/Mask Connection
Component
172.16.1x1.11/24 Router A
PC-A
GW 172.16.x2.101 Port ge.1.2
172.16.x4.22/24 Router C
PC-D
GW 172.16.1x4.103 Port ge.1.4
Router A
172.16.1x1.101/24
VLAN 10
Router A
172.16.x3.101/24
VLAN 3
Router A
172.16.x5.101/24
VLAN 5
Router A
PC-A
Port ge.1.2
Router A Router B
Port ge.1.3 Port ge.1.3
Router A Router C
Port ge.1.5 Port ge.1.5
Router B
172.16.x3.102/24
VLAN 3
Router B
172.16.x6.102/24.
VLAN 6
Router B Router A
Port ge.1.3 Port ge.1.3
Router B Router C
Port ge.1.6 Port ge.1.6
Router C
172.16.1x4.103/24
VLAN 4
Router C
172.16.x5.103/24
VLAN 5
Router C
172.16.x6.103/24
VLAN 6
Router C
PC-D
Port ge.1.4
Router C Router A
Port ge.1.5 Port ge.1.5
Router C Router B
Port ge.1.6 Port ge.1.6
PIM-SM Network
VLAN 3 VLAN 6
172.16.X3.x/2 Router B 172.16.X6.x/24 Router C
Router A
Leaf- 4 RP ge.1.6 ge.1.6 First Hop
ge.1.3 ge.1.3
RTR
.101 .102 .103
.102
Area 0 Multicast
Server
As you cable your network for this lab, you must configure your S/K-series
router to function as Router B. We recommend that if you have a second
S/K series router you configure it as Router C.
We have changed the labeling on your routers in this lab to reflect this
change in the physical topology of your network.
5. Cable the network as shown in the diagram above and as outlined in the
previous table.
6. Set the switch back to factory defaults (clear config all).
7. Attach the PCs as shown in the diagram at the beginning of the lab, using the IP
addresses in the table and diagram.
8. Set your Prompts to Router A, Router B, and Router C, respectively.
9. Globally disable GVRP, LACP, and Spanning Tree.
10. Create VLANs on your Switches.
On the C5:
Router A(su)->router(Config)#interface vlan 10
Router A(su)->router(Config-if(Vlan 10))#ip ospf enable
Router A(su)->router(Config-if(Vlan 10))#ip ospf areaid
0.0.0.0
Router A(su)->router(Config-if(Vlan 10))#exit
Repeat for each interface.
On the S/K:
Router B(su-config-ospf-10)->network 172.16.x3.0 0.0.0.255
area 0.0.0.0
Repeat for each interface.
1. From your PCs, ping your directly connected default Gateway routers to test your
local connectivity.
2. Ping your neighbor's PC to check route connectivity.
3. Troubleshoot any connectivity issues that arise.
1. Enable IGMP globally. On your C-Series switches, also issue ip igmp enable
on each VLAN.
On the S/K:
Router B/Cset igmp enable <vids>
Router B/C> set igmp query-enable <vids>
1. Enable PIM-SM globally and at each VLAN interface level for the C-series
platforms.
On the C5:
Router A> router(config) # ip pimsm
Router A> router(config) # ip pimsm staticrp 172.16.X3.102
224.4.4.4 255.255.255.255
Router A> router(config(Vlan#) # ip pimsm enable
Router A> router(config(Vlan#) # ip pimsm enable
Router A> router(config(Vlan#) # ip pimsm enable
2. Issue the show ip interface command. Verify that PIM-SM is enabled on all
VLAN interfaces.
RouterX> router# show ip interface
3. Use the following commands where possible.
RouterX> router# show ip pim neighbors
In this section you will use the VLC video player to generate multicast traffic over
the network. Prior to setup, insure VLC software is installed on your Server (PC-
D, attached to Router C) and your clients (PC-A attached to Router A). If you do
not have the VLC application, contact your instructor.
1. Set up PC-D as the Video server. Double click on the VLC icon to start the
application.
2. Click on Media and select Open (advanced). The Open Media window appears.
5. From Stream Output window, Destinations Setup, select Display Locally. From
the New destinations pull down choose UDP, then click the add button. A new
UDP tab will be created, enter in multicast address 224.4.4.4
8. To set up your video client, Open VLC on PC-A. Click on Media and Select Open
Network Steam. Enter the Multicast address you used when you set up your
server (224.4.4.4). Then Click Play.
9. If everything has been configured properly, you should see the video on client
PC-A. If not, troubleshoot PIM environment using recommended show
commands.
End of Lab 5
Resources/Tools
For this lab you will need:
Three Enterasys routers (this lab was written with two SSAs and a C5)
Two PCs
Objectives
At the end of this lab you will be able to:
Configure VRRP
Configure a VRRP IP address owner
Configure a VRRP Critical IP interface
Configure an Enterasys router for VRRP priority
At the end of the lab, you will have configured your devices according to the table
and diagram below.
VLAN VRID=1X1
1X1 IP=172.16.1X1.103/24
Switch/Router A
ge.1.2
ge.1.3 ge.1.5
172.16.1X1.102/24 172.16.1X1.103/24
VLAN 1X1 VLAN 1X1
ge.1.3 ge.1.5
ge.1.7 ge.1.8
172.16.1X4.102/24 172.16.1X4.103/24
VLAN 1X1 VLAN 1X1
ge.1.7 ge.1.8
ge.1.4
VRID=1X4
VLAN IP=172.16.1X4.50/24
1X4
1. Cable the network as shown in the diagram above and previous table.
2. Set the switches back to factory defaults (clear config all).
It may be necessary to re-enter the advanced routing licenses on platforms once
they have been defaulted.
3. Set equipment prompts to Switch A, Router B, and Router C.
Note: an S/K-Series platform must be used for Router C in this lab setup.
4. Set Spanning Tree disabled globally on all devices.
5. Set GVRP disabled globally on all devices.
6. Set LACP disabled globally on all devices.
(Note: LACP is fully supported with VRRP, but for this lab it is necessary to
disable it to prevent routers from forming a LAG with Switch A.)
Network
VLANs
Component
1x1
Switch A
1x4
1x1
Router B
1x4
1x1
Router C
1x4
Network
Port VLAN
Component
Switch A Ge.1.2,3,5 VLAN 1x1
9. Create Layer 3 VLAN/routing interfaces on your two routers. From the VLAN
interfaces enter the IP addresses shown in table, with 24 bit masks.
Network
VLAN IP Address/Mask
Component
Router B VLAN 1x1 172.16.1x1.102/24
Network
VLAN IP Address/Mask
Component
Router C VLAN 1x4 172.16.1x4.103/24
1. From router config mode set up VRRP instance 1X1, for VLAN 1X1, on Router B.
On your C5 in router mode:
RouterB> router(config)# router vrrp
RouterB> router(config-router)# create vlan 1X1 1X1
RouterB> router(config-router)# address vlan 1X1 1X1 1 Indicates IP
172.16.1X1.102 1 address owner.
RouterB> router(config-router)# enable vlan 1X1 1X1
RouterB> router(config-router)# exit
2. From config mode setup, configure VRRP instance 1X1, for VLAN 1X1, on
Router C at the interface level.
On your S/K in config mode:
RouterC(su-config)->interface vlan 1X1
RouterC(su-config-intf-vlan.0.1X1)->vrrp create 1X1 v2-IPv4
RouterC(su-config-intf-vlan.0.1X1)->vrrp address 1X1
172.16. 1X1.102
RouterC(su-config-intf-vlan.0.1X1)->vrrp enable 1X1
1. From router config mode setup VRRP instance 1X4 for VLAN 1X4 on Router B.
Note: critical-ip address support is platform specific. Therefore, Router C
configuration must be performed on the S/K-Series platform for critical-ip to
function.
On your C5 in router mode:
RouterB>router(config)# router vrrp
RouterB>router(config-router)# create vlan 1X4 1X4
RouterB>router(config-router)# address vlan 1X4 1X4
172.16.1X4.50 0
RouterB>router(config-router)# priority vlan 1X4 1X4 100
RouterB>router(config-router)# enable vlan 1X4 1X4
RouterB>router(config-router)# exit
2. From config mode setup configure VRRP instance 1X4, for VLAN 1X4, on Router
C at the interface level.
On your S/K in config mode:
RouterC(su-config)->interface vlan 1X4
RouterC(su-config-intf-vlan.0.1X4)-> vrrp create 1X4 v2-
IPv4
RouterC(su-config-intf-vlan.0.1X4)->vrrp address 1X4
172.16.1X4.50
RouterC(su-config-intf-vlan.0.1X4)->vrrp priority 1X4 125
RouterC(su-config-intf-vlan.0.1X4)->vrrp critical-ip 1X4
172.16.1X1.103 50 (Configures critical-ip on RouterC)
RouterC(su-config-intf-vlan.0.1X4)->vrrp accept-mode 1X4
(Configure Router C to accept pings for VIP)
RouterC(su-config-intf-vlan.0.1X4)->vrrp enable 1X4
1. Start a continuous ping between PC-A and PC-B in VLAN 1X1 and VLAN 1X4.
Confirm the pings are successful.
ping 172.16.1X#.11 t
2. Display VRRP setup information to determine the master router in the VRRP
pair. Router B should be VRRP Master for VLAN 1X1 based on IP address
ownership, Router C should be VRRP Master for VLAN 1X4 based on VRRP
priority.
show ip vrrp
show ip vrrp verbose (S-Series)
3. Display the VRRP instances
show ip vrrp 1X1
show ip vrrp 1X4
4. Disable the port on the master router for VLAN 1X1 (ge.1.3 on Router B) to
cause the backup router to take over the VRRP instance. Verify that ping traffic
remains successful between your VLANs.
5. Re-enable the port on the master router for VLAN 1X1. Verify that the original
master router resumes supporting the VRRP instance. Verify that ping traffic
remains successful between your VLANs.
6. Repeat the above steps for VLAN 1X4. Be sure to disable/enable the master
port on the correct router.
7. Use show commands above to ensure switchover has occurred.
1. Verify that your S/K Series router is the master VRRP router in VLAN 1X4.
RouterC> show ip vrrp vlan.0.1X4
2. Start a continuous ping between PC-B, VLAN 1X4 and PC-A, VLAN 1X1.
Confirm the pings are successful.
3. Cause a failure of the critical-ip address on Router C. Disable the interface for
VLAN 1X1 on Router C (ge.1.5).
4. Verify that master VRRP router (S/K Series) for VLAN 4has now switched to
backup role. Router B should now be the master VRRP router for VLAN 1X4 as a
result of the critical-ip interface failure on Router C.
5. Verify that ping traffic remains successful between VLANs.
End of Lab 6
Group IP Address
Group1 10.170.110.10
Group2 10.170.120.10
Group3 10.170.130.10
Group4 10.170.140.10
Group5 10.170.150.10
Group6 10.170.160.10
Group7 10.170.170.10
Group8 10.170.180.10
2. Login to the Enterasys WC (EWC) using the following username and password.
a. Username: admin
b. Password: training
3. Select Wireless Controller from the top toolbar.
4. Select Software Maintenance from the left column and then select the Restore
tab.
5. Select the available backup to restore from the pull down that contains your
controller name WC#BACKUP.zip, e.g. WC1, and then select Restore Now.
6. A Window will open and the restore process will start. After a while the controller
will reboot. This will remove the pre-configured VNS configurations.
End of Lab 7
These components will be utilized in future labs, such as Integration with NetSight,
Guest Portal, Availability and Mobility.
10.170.1.15/32
DHCP, RADIUS
Server
L3 Switch
10.170.1x1.50
PC (VNC/ WLAN
10.170.1x0.0/24 Client)
Controller L2 Switch
PC w/ VMWare
10.170.1x0.10
AP1
AP2
1. Open your Web Browser and connect to the Wireless Controller ip address
https://10.170.1x0.10:5825.
2. Login to the WC using the Username: admin and Password: training
3. Examine the dashboard page. The tool bar at the bottom of the page displays
the name of the Enterasys Wireless Controller, User, Port status and Software
Release.
4. Click the Green Up arrow for Local APs this will produce a pop-up window of
the active APs.
Click on some of the other areas, such as: Admin Session, Security, Health and
Licensing. Each of these items on the dashboard will re-direct to the
configuration or reporting information for each of these items.
1. Select Wireless Controller from the toolbar, the System Maintenance screen
will appear.
2. Click on the Logs tab in the left-hand panel.
3. Configure the System Log Levels and then click Apply.
a. Wireless Controller Log Level: Information
b. Wireless AP Log Level: Information
The first setting specifies the level at which events should be logged; Information is
the lowest level and Critical is the highest level. The second setting tells the
Enterasys Wireless Controller the IP address and port to which syslog messages
should be sent. The syslog messages will be sent to the lab SIEM and to your
NetSight Server (messages can be viewed by clicking on the Syslog tab in the
Console View).
Changes to the NTP screen may cause the controller to reboot, therefore you may
need to login again after this section.
4. Select New, add the Interface to the OSPF configuration. and then Save.
Enabling OSPF will propagate all new Routed networks created on the
Controller to the neighboring router.
3. At any time during the labs you can select Reports tab to see other reports such
as:
Forwarding Table
OSPF Neighbor
OSPF Link state
AP Inventory
End of Lab 8
End of Lab 9
The admin account is what NetSight will use to config some components on the
Controller.
1. Launch the Console Client from your browser http://<ip address of your
PC>:8080 or select the NetSight Launch Page on the Desktop.
1. Before you configure anything you will have to import the Default Database. Go
to Tools > Server Information.
2. From the Database tab click the Restore button.
3. Select the Restore Initial Database radio button from the Restore Database
window.
4. Click the Restore button.
5. After the Database is cleared, the NetSight Server has to be restarted; the
system will do this for you when you click on the OK then the YES button.
6. The Server will restart and the connection will be restored, the status on the
bottom of the NetSight Console window will show the status. When the NetSight
Server taskbar arrow icon goes green the server has been restarted successfully
and you can continue.
1. Create SNMP and CLI Authentication credentials for the Enterasys Wireless
Controller, from the Console Tools Menu select Authorization/Device Access.
6. Create the Device Access Profile (Add Profile), by combining the SNMP and CLI
Credentials, when finished, click Apply and then Close.
a. Profile Name: WC
b. SNMP version: SNMPv3
c. Read/Write/Max Access : WC (Security Level: AuthPriv)
d. CLI Credential: WC_Access
NetSight should contact the Controller and will display the Controller and the alarm
icon will be green indicating that that the SNMPv3 contact was successful.
End of Lab 10
The Enterasys Wireless Controller requires an FTP Server on the network. The FTP
server (filezilla) has been installed on the same PC-As the NetSight Suite Software.
2. Right-click on the controller and set the File Transfer Method to FTP.
The Controller Configuration will be archived nightly; if problems arise in class the
configuration can be easily be restored.
1. Select the Controller, right click and select the Wizards > Archive Wizard.
4. Verify the Device Selection (should match the starting point of the wizard) and
click Next.
5. Select to archive the configuration on a daily basis Schedule and then click
Finish.
a. Frequency: Daily
b. Starting Day: Today
c. Time: 10:00 PM EST
End of Lab 11
1. By default, OneView polls the devices every 15 minutes for statistics. To change
that polling interval for purposes of this class, from Netsight Console click
Tools>Options.
End of Lab 12
OneView Device and Interface Statistics Collection can be easily enabled from the
NetSight Console Window. Once statistic collection is enabled you will see any
results in the OneView Reports.
3. Click OK.
1. You must also enable statistics collection on your interfaces. In the NetSight
Console window, select the Wireless Controller.
End of Lab 13
The Controller client statistics collection is enabled within the OneView window.
1. You must enable statistics collection in OneView for your controller before you
will see any results in your reports. To do so, click on the Devices tab.
The Reports that use these collections will be view in a later lab.
End of Lab 14
1. Select the Wireless APs tab and then select AP Registration from the left hand
column.
2. Change the Security mode to: Allow only approved Wireless APs to connect and
then click Save.
Section C: AP Properties
4. If you have an Access Point with External Antennas (3620/2620), verify that
under the AP properties tab, that the Antennas are set to the Factory default
Antenna, i.e. choose the Left , Middle and Right Antenna to 4dBi Omni
Factory.
NOTE: Even if you assign WLAN service to that AP, there will be no radio service
available on any AP radio till the proper antenna is selected.
1. Select All.
2. Select the AP, and Select the Reset to Defaults button (the AP will obtain the
new default settings that were created.
3. Click OK to accept the warning message.
6. Click Save.
End of Lab 15
Check the Logs on the Controller; these will include the discovery of the AP to the
controller.
Section B: AP Reports
1. Click on Reports.
2. Select AP Inventory.
End of Lab 16
Each group is assigned a WLAN Client that is accessible via VNC from your Glance
session. This will be the Wireless Client that will be used to connect to the
Broadcasting SSID of the APs.
1. To access the WLAN client, open the VNC Viewer Icon on the Desktop
2. Enter the Server IP Address listed above for your Group, and then click OK.
End of Lab 17
Bridge Locally at AP (tagged) Traffic will be tagged by the Access Point before
entering the network.
Rate Limiting is typically configured in order to give priority to Enterprise traffic and
applications.
1. Select the Classes of Service component from the left hand menu.
2. Select the Critical Data Class of Service.
5. Select Outbound Rate Limit: select Student from the pull down menu, and then
click Save.
Create a Policy that will provide access to the network will some restrictions.
Create Filter rules that will not allow the end-system to act as any type of Server on
the Network (DNS, FTP and DHCP Server) and allow all other traffic.
3. Repeat this process for the following ports: FTP & Bootp.
Note: This filter will allow all traffic from the network (scr), but will not
allow the end system be to an FTP, DNS or BOOTP Server.
Section G: AP Reports
1. Confirm that your APs are transmitting on just the b/g/n (depending on your AP)
by selecting Reports.
1. Using your Wireless Client connect to the SSID broadcasted by your Access
Point BR_Group#, i.e. BR_Group1.
2. Using the WLAN client connect to the SSID broadcasted by the AP(s) i.e.
BR_Group#, enter the pre-shared Key.
4. Execute ipconfig at the command prompt to check for the IP- address for the
Wireless adapter.
1. Active WLAN Clients are displayed in the EWC reports by selecting Clients from
the left hand pane. Client reports include Clients by AP, Clients by VNS and All
Active Clients.
ICMP and HTTP traffic is controlled by the Filters that are applied
to the Authenticated Client.
3. Using the scroll bar find the Avg. Rate (Mbps) Sent / Recd. Note that the Avg.
Rate is not the highest Data Rate but is the Class of Service applied to the SSID/
End-System. Using the Refresh button this value will change.
What is the Avg. Rate Sent / Recd? ___ / ___
Note: If the IP Client IP address is N/A either the WLAN Client is still in the
Authentication process or there may be a problem with the DHCP server.
The Client that associated and Authenticated with the AP should be displayed. A Pre-
Shared WPA key was used for authentication therefore Identity information such as
User Name and Host Name are not displayed.
When a new VNS is added to the controller, a new interface is created. To monitor
traffic and collect historical information using OneView this interface MUST have
interface collection enabled. This can be performed in the OneView screen or in the
Netsight Console window.
End of Lab 18
Did the filter work dynamically or did you have to disassociate the client from
the AP and connect again?
6. Select the Student Policy; Delete the ICMP rules previously created in Step 4
and then click Save.
Are the pings (ICMP Reply packets) working again?
End of Lab 19
10.170.1.15/32
DHCP, RADIUS
Server
Controller 10.170.1#0.0/24
WLAN Client
AP1 AP2
Maintain client session in event of poll failure is default behavior for the Enterasys
APs. This is an Advanced Setting for the APs.
Are the ICMP Replay packets still being displayed in the command window on
the Windows Client?
Check the controller logs after you log back into the controller to confirm the
reboot, you can see it under the severity of Major.
End of Lab 20
Section B: Wireshark
4. Enter the IP address of the Wireless Access Point, i.e. 10.170.1x0.102, where x
is the Group Number you have been assigned.
5. Enter port 2002, this is port that will be used on collect the packets.
6. Click OK.
7. Once the Remote Host is configured the Interface pull-down is populated. Select
the rcap entry for the node; e.g., rpcap://[10.170.110.102]:2002/wifi1.
8. Click Start.
Note: If you receive the following message, this is an indication that the trace is not
running at this time.
End of Lab 21
10.170.1.15/32
DHCP, RADIUS
Server
Controller 10.170.1#0.0/24
WLAN Client
AP1 AP2
In the classroom training there is a Radius Server configured using the following
settings:
IP-Address: 10.170.1.15
Authentication: EAP, PEAP, MS-CHAP2, PAP
User: Student / Password: training
3. Define a New Radius Server using the following settings, and then Save.
a. Server Alias: Radius
b. Server Address: 10.170.1.15
c. Shared Secret: training
d. Default Protocol: MS-CHAP2
Note: If you want to monitor this newly created interface (VNS), repeat the
process defined earlier to enable interface collection on the OneView Screen.
Note: You will have to make some changes on your WLAN Client (Windows 7) to
make the connection.
1. Click on the Wireless icon and then Open Network and Sharing Center (Window
7).
3. Select Add.
10. Select Specify Authentication mode and select User authentication from the
pull down menu, and then click OK.
11. From the Security Tab, click on Settings next to the network authentication
method.
12. In the Protected EAP Properties window uncheck Validate Certificate Server
and Enable Fast Reconnect.
1. Connect to the Group# SSID and authenticate using the username = training /
Password = training.
If the SSID is not listed as an available Wireless Connection check that the
VNS and WLAN Services configuration for this SSID on the controller are
enabled.
Note that the Auth/Priv will be EAP/ WPA and that the Avg. Rate Sent/Recd is
within the full rate of 54Mbps. Because the back-end Radius Server was used for
Authentication, identity information, such as Username is displayed.
End of Lab 22
When authenticating via 802.1x or Captive Portal the Radius Filter-ID attribute can be
used to assign both the policy and topology for an end-system. By default, when the
controller receives a RADIUS ACCESS-ACCEPT packet, it will use the RADIUS Filter-
ID to assign the Policy and the Tunnel-Private-Group-ID to assign the topology.
5. Click Save.
Create a Policy named Employees. This Policy will match the Filter-ID defined on the
RADIUS Server. The Filter-ID is case sensitive; therefore the policy created on the
Controller must exactly match the Filter-ID name specified in the RADIUS Accept
Message.
3. Select the Filter Rules Tab and select the Default Filter to Allow all Traffic and
then click Save.
The End-System will authenticate using 802.1.x; the Radius Server will return the
Filter-ID attribute.
2. Connect to the Group# SSID and authenticate using the username = Trainer /
Password = training.
The Topology and the IP address which is tied to the topology and Filter will
change because a different Filter-ID was returned by the RADIUS server.
When authenticating an end-user with the RADIUS Server, if the Radius or Network
Access Policy has a Filter-ID defined and returned in the Radius Accept Message, the
policy that matches the Filter-ID will be used to assign the topology, class of service
and filters. The User Trainer returns a Filter-ID of Employees, therefore the
Employees Policy will be applied.
End of Lab 23
3. If the WLAN is not connected to the Group# SSID, reconnect and login using the
Username: Trainer and Password: training.
End of Lab 24
Bridged Locally at HWC or Routed Traffic is tunneled to the Controller, this can be
used in a Guest Network Environment where Wireless End-System traffic enters the
Enterprise Network into the DMZ, by-passing the core network.
Guest Access is typically Rate Limited and traffic is given a lower priority in order to
give priority to Enterprise traffic and applications.
Note: The DSCP bit is being used due the Routed Topology.
6. Select Outbound Rate Limit: select Guest on the pull down menu.
7. Click Save.
Non-Authenticated Policy This policy will be used for features such as Captive Portal
or Guest Portal, traffic will be re-directed to the Controller for Authentication.
c. Allow HTTP to an External HTTP link (used in the Captive Portal Web Page).
d. Edit the last two rules to Deny all other traffic and then Save.
Once Authenticated onto the Network, users that do not have a Filter-ID or
Role/Policy assigned to their Radius account will get the default Guest Policy (limited
access and Routed topology).
c. Edit the last two rules to Deny all other traffic and then Save.
17. Create a new WLAN Service for the Captive Portal with the following settings and
then Save:
a. WLAN Service Name: Portal_Group# (# = Group)
b. SSID: Portal_Groupx
c. Service Type: Standard
18. Select APs: radio 2, which will apply the WLAN service to all Radio 2s.
26. Enter a creative message to be displayed to users that fail authentication and
then click Close.
27. Select Launch Captive Portal Editor for the Captive Portal Configuration Editor.
29. In the Property Editor window, Browse for the enterasys.jpg file to upload from
the Training Share and then click Open.
31. Click on the Text button in the Add Widget To Panel section.
32. Set the display option to Only prior to authentication. Enter the message to
display to user, i.e. Welcome to the Enterasys Training Guest Network. pPease
enter your credentials.
34. The Message box will be display in the Login Page screen, select the Text Box
and move it slightly above the Login Prompt.
The Error message label indicates where the error messages will be displayed. During
the testing phase of creating the Captive Portal Web page, you may have to adjust the
text box so that it doesnt overwrite the Error message.
36. In the Property Editor Window and then set the Width, Height, Left values.
a. Width: 210 Height: 75
b. Left: 295 Top: 10
37. Select the image that was recently uploaded and then click Apply.
39. Enter the URL for the External HTML link, http://10.170.1.15/footer.htm in the
Property Editor.
40. Select the Width, Height and Top equal to what is displayed below. This will set
the location of where the contents of the External HTML file will be displayed.
43. Click the Preview to see the sample page, make adjustments if needed.
This is the screen that will be displayed if the topology changes during the
authentication process, i.e. Non-Authenticated = Bridged Locally at HWC.
Once authenticated, the end-users topology is changed to Bridge Locally at
AP based on a Dynamic Policy Assignment.
47. In the Configure window select to redirect the end-user once authenticated to
the original destination that was required, i.e. 10.170.1.1. Click Close.
48. Select the Save button to save your Captive Portal configuration.
1. Select Virtual Networks, and then create a New Portal Virtual Network.
a. VNS Name: Portal_VNS
b. WLAN Service: Portal_Group#
c. Non-Authenticated = Non-Authenticated
d. Authenticated: Guest
e. Select Enable and then click Save.
1. Connect to the Captive Portal SSID that is being broadcasted from your AP, i.e.
Portal_Group#.
2. Open your web browser on the WLAN Client. (If there isnt a DNS Server on the
Network, enter the following URL, http://10.170.1.1, to be redirected to the
Captive Portal Page). You should be redirected to the controller displaying the
previously configured Captive Portal login page.
Note: 10.170.1.1 is the log-in screen for the switch in the network.
Check your filter settings first if you cannot reach the Captive Portal Web Page.
3. Go to Reports on the GUI then click on Active Clients by VNS or All Active
Clients notice that the Filter for the connection is the non-authenticated policy or
Non-Authenticated.
If a Filter-ID or VLAN-id is not returned in the Authentication Packet received from the
Radius Server, the default Authenticated Policy (Filters/Cos/Topology) will be
assigned to the end-system.
1. Open your web browser on the WLAN Client. (If there isnt a DNS Server on the
Network, enter the following URL, http://10.170.1.1, to be redirected to the
Captive Portal Page).
2. Login as user: Trainer password: training.
3. On the Wireless Controller GUI refresh the All Active Clients Report.
4. Select Logs.
5. Examine the Controller Events, HWC: Events > All. A log message is created
during the authentication process recording the Radius Server interaction,
showing the VNS the WLAN client connect to as well as the username and policy
that was applied to the user.
What filter, topology and IP address was assigned to the Wireless Client?
Why?
In this example when the user training was authenticated by the Radius Server,
there was NO filter-id was returned to the Controller. Therefore the controller
assigned the default policy or Guest.
End of Lab 25
Create a GuestPortal Manager account that will be used to Register Users that will
access the Guest Network.
5. Select Configure, to open the window for the Internal Guest Portal Settings.
7. Configure your own personal Guest Portal web page. Type in the following:
a. Send Successful Login To: custom specific URL
b. Enter the URL: http://10.170.1.1
c. Communication Options: Use Zip File
d. Upload Zip file: enterasys.zip ( Found on the Training Share Drive)
e. Click Upload. Accept the warning by clicking OK.
f. Click Close.
Once the .zip file has been uploaded, via the Close button you can click on
Configure and then again on View Sample Login Page or View Sample Index Page.
2. Login Again in to the Wireless Assistant using the Guest Manager account
created in the previous lab, i.e. User Name: GuestManager, Password: training.
Note: The Guest Manager account is only active once Guest Manager is selected
as an Active VNS.
Note: If the Portal_Group# ssid is not displayed, check to make sure that the
WLAN Service is enabled.
4. Open the web browser on the WLAN Client. (If there isnt a DNS Server on the
Network, enter the following URL, http://10.170.1.15, to be redirected to the
Captive Portal Page). You should be redirected to an internal site displayed the
previously configured Guest Portal login page.
5. Log in as using the guest access credentials created earlier.
End of Lab 26
Note: This Lab requires the use of a second controller or 2 groups working together.
DHCP, RADIUS
Server
1. Open your Web Browser and connect to your second Wireless Controller (PC.1)
at IP address https://10.170.1#0.11:5825.
Group IP Address
Group1 10.170.110.11
Group2 10.170.120.11
Group3 10.170.130.11
Group4 10.170.140.11
Group5 10.170.150.11
Group6 10.170.160.11
Group7 10.170.170.11
Group8 10.170.180.11
2. Login to the Secondary Controller using the Username: admin and Password:
training.
3. Select the Bulk Configuration> Access Approval window; the AP should be
Approved and Active.
4. Examine the Mobility Tunnel Matrix on the Mobility Manager. (Should see one
controller report home =1, current = 1).
6. Examine the Report on the primary controller, the WLAN client should have
roamed to the other AP on the other Controller, however because the primary
controller is configured for the Remoteable WLAN Server the client will be
displayed on the primary controller the Roamed status of Yes.
The controller is not managing the AP that the client is now connected to.
Therefore the information such as Radio/Protocol/RSS information is not displayed.
7. Examine the Mobility Tunnel Matrix report, the report should indicate that the one
Controller with home =1 and the other controller should have current =1).
Does the WLAN Client retain its IP address? Why or why not?
How have the Mobility Tunnel Reports changed?
End of Lab 28
DHCP, RADIUS
Server
Secondary/ Foreign
Controller
10.170.1#0.10/24
10.170.1#0.11/24
Home Controller
AP1 AP2
1. On the Primary Controller, i.e. 10.170.1#0.10, select the Wireless Controller tab
and select the Availability component from the left hand column of the Wireless
Controller>Administration window.
2. Start the Availability Wizard.
3. Enter the Connection Details (Primary Controller will use this information to
communicate to its peer Controller and configure Availability).
a. Select the Port/IP that will communicate to the other Controller i.e. (esa0)
10.170.1#0.10
b. Set the Peer Controller IP, i.e. 10.170.1#0.11
c. Set the Peer Controller Login: admin / training
d. Enable Fast Failover
4. Enter the Synchronization Options.
a. Enable Synchronize System Configuration
b. Enable Synchronize Guest Portal Accounts
5. Click Next.
6. The Topology Definitions will be displayed for all Routed and Bridged Locally at
Controller topologies. Interface IP and Mask values are displayed with
placeholders as 0.0.0.0. For real Gateway and Mask information enter the Peers
Gateway IP address that matches your VNS, e.g. 10.170.113., would match
10.170.114.1. Give the gateway a 24-bit mask.
1. Select Reports and open the AP Availability report. The Availability tunnel
should be up. (The number of APs on display should be equal to the number of
APs configured on each Controller.)
5. On the Controller that the Client is connected to, select the Wireless Controller
tab and Shutdown the controller by initiating a reboot.
6. Monitor the Active Clients by Wireless AP report on the Controller that did not
reboot and the continuous pings on the Wireless Client.
Note: If the Controller is displaying the Client IP as N/A, the Client IP address can
be obtained by using the ipconfig/all command on the WLAN client.
7. Monitor the Wireless AP Availability report by refreshing the Report until the
availability status is reported as UP, i.e. Availability Link is UP.
8. Bring the foreign AP(s) back to its home controller by selecting Wireless APs >
Access Approval and Releasing the Foreign AP.
End of Lab 29
1. Associate the WLAN Client to SSID, BR_Group# SSID and log in as Student /
training.
2. Start a continuous ping to 10.170.1.1, i.e. ping t 10.170.1.1.
3. To discover the MAC address of your client, go to Console, click the All Devices
group, and click the Interface Summary tab.
5. In the Enterasys Wireless folder, click the Wireless Clients.tpl Flexview and
click Open. If you cannot find the Enterasys Wireless folder, browse to
Win7OS(C:)/Users/training/Application Data/NetSight/System/Flexviews/ to
locate it.
9. Move to the Search tab, and paste the MAC address of your client into the
search field.
10. Click Search . The Search Overview information appears on your screen.
11. Select the Wireless Details tab. Inormation about the Client, Controller and AP
that the Client is associated to is displayed.
1. Explore the information available to you under the Wireless tab. Click the
Wireless tab, and click the Details sub tab. Click the Wireless Network icon
and answer the questions below.
2. Click the Virtual Networks icon, and answer the questions below.
3. Click Close.
6. The Options field provides you with five drop-down windows that allow you to
tailor your report. In the Data Options>Category drop-down window, select
Raw Data.
8. In the Targets field, select Group#-AP1 Interface (the Ethernet interface of the
AP, since the connection we are using for the Wireless client is Bridged at AP
tagged).
11. Click Submit. You will see one value at the far right-hand side of your chart. If
you re-click Submit after 15 minutes, a second value will appear.
12. OneView provides you the information in graph form. To see the same
information in table form, under Display Options check the Render As drop down
box. Choose Table and click Submit.
End of Lab 30