NetSight Boot Camp Lab Guide v1.30 (Ebook PDF
NetSight Boot Camp Lab Guide v1.30 (Ebook PDF
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
Extreme Networks NetSight Boot Camp Lab Guide
Extreme Networks reserves all rights to its materials and the content of the
materials. No material provided by Extreme 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 Extreme
Networks.
This document and the information contained herein are intended solely for
informational use. Extreme 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. Extreme 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
ok
information may be available on request. By your review and/or use of the
Bo
information contained herein, you expressly release Extreme from any and all
liability related in any way to this information. A copy of the text of this section is
-e
an uncontrolled copy, and may lack important information or contain factual errors.
All information herein is Copyright ©Extreme Networks. All rights reserved. All
information contain in this document is subject to change without notice.
ks
or
http://www.extremenetworks.com/company/legal
N
e
m
tre
Ex
Extreme Networks NetSight Boot Camp Lab Guide
Contents
LAB 1: Integration with NetSight ............................................................................. 1
Section A: Admin Account ......................................................................................... 1
Section B: SNMP V3 Configuration ........................................................................... 2
Section C: Configuring SNMPv3 on Switch-A (XOS) .............................................. 4
Section D: Configuring SNMPv3 on Switch-C (EOS) ............................................. 5
LAB 2: NetSight Server Administration ................................................................... 7
Section A: Console Preparation: Restore Initial Database ........................................ 7
Section B: Restoring the Database ............................................................................ 9
Section C: Automated NetSight Database Backup ............................................... 13
ok
Section D: Manually Backup the Database .......................................................... 14
Bo
Section E: Email setup ............................................................................................ 16
LAB 3: NetSight - Device Configuration ................................................................ 17
-e
Section A: NetSight Profile/Credentials ................................................................... 17
Section B: Discovery and Device Groups ................................................................ 22
ks
Section C: Unknown Devices or 3rd Party Device ................................................. 25
or
ok
Section B: Interface Statistics Collection ................................................................. 90
Bo
Section C: OneView Display ................................................................................. 93
-e
LAB 9: Console - Compass .................................................................................... 95
Section A: Compass Search – Determine Port on Device ....................................... 95
ks
Section B: Faster Searches ..................................................................................... 98
or
Section C: Add Port to Device Port ..................................................................... 102
LAB 10: Console - FlexViews ................................................................................. 103
w
ok
Section E: Rule Usage .......................................................................................... 154
Bo
Section F: Dynamic – Authenticate User ............................................................... 155
NAC – End System Management ............................................................. 158
-e
LAB 16:
Section A: Restore NAC Database ........................................................................ 158
ks
Section B: Executing Command Script to Configure NetLogin and UP Profiles .... 165
or
Section C: One View Client History Report ........................................................ 168
Section D: Modified End-System ........................................................................ 173
w
et
N
e
m
tre
Ex
NetSight uses a combination of CLI and SNMP MIBs to configure, monitor and
manage devices in NetSight.
ok
Bo
Section A: Admin Account
-e
1. Connect to the Wireless Controller. ks
https://<your Wireless Controller IP address>:5825.
or
2. From the top menu, click Wireless Controller.
w
4. Create a Full Administrator account; enter the following User ID, Password
and Confirm Password:
N
b. Password: training
m
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
i. Enabled
ii. User Name: <your SNMP username> (See Section D of
the Appendix)
iii. Security Level: authPriv
iv. Authentication Protocol: MD5
v. Authentication Password: training
vi. Privacy Protocol: DES
vii. Privacy Password: training
c. Click OK.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
5. Click Save.
ok
Bo
-e
ks
or
config snmpv3 add group <your SNMP group> user <your SNMP
username> sec-model usm
Ex
ok
Bo
-e
ks
or
w
et
Password changed.
5. Configure the switch for SNMPv3 using the following commands:
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
In this lab you will learn how Extreme NetSight can discover networking devices and
connect to them in order to manage them.
Objectives
ok
At the end of this lab you will be able to:
Bo
Restore the initial database in the NetSight server
Configure an automated Database backup. You will also manually back up
-e
the Database.
Configure an Email Server for Alarms and Events
ks
or
w
Note: There may a shortcut on the Desktop that can be used as well.
m
tre
Ex
ok
Bo
-e
ks
or
d. Username: training
et
e. Password: training
N
e
m
tre
Ex
4. Click OK.
ok
Bo
Section B: Restoring the Database
-e
1. On the main menu bar, go to Tools > Server Information.
ks
or
w
et
N
e
m
tre
Ex
ok
Bo
-e
ks
or
w
3. Click the Restore Initial Database radio button from the Restore Database
window.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
4. Click the Restore button. The “Restoring Initial Database, please wait.. message
should appear. This process can take several minutes.
ok
Bo
-e
ks
or
5. After the Database is cleared, the NetSight Server must be restarted. The system
w
will do this for you when you click on the OK in the Database Initialized
Successful window, then the YES button.
et
N
e
m
tre
Ex
This process can take up to five minutes. Console will reconnect. If not, restart
Console.
Backing up the Database backs up the Data for Console and all the Plug-in
Applications like Inventory Manager, Policy Manager and NAC Manager.
1. From the Tools>Options Menu select DatabaseBackup.
2. Configure the system to do a database All days of week at 10 pm.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
ok
Bo
-e
ks
or
w
et
N
5. Select the Restore button, in the Restore Database window the manual-backup
files will be listed.
ok
Bo
-e
ks
or
w
et
N
e
6. Click Cancel.
m
7. Optionally, you can SSH to the NetSight Virtual Appliance, login, change the
tre
Email can be used for several aspects of the NetSight function, i.e. Alarms and
OneView reports.
1. From Suite Options section select SMTP E-Mail Server and the email server
and the Sender’s Address and then click Apply and then OK.
a. Outgoing E-mail (SMTP) Server: training1.training.com
b. Sender’s Address: [email protected] (where X is your
Student /Group number)
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
Objectives
ok
At the end of this lab you will be able to:
Bo
Configure NetSight to connect to devices using SNMPv3
Discover Devices using the SNMPv3 configuration
-e
Discover the Active Directory Server using SNMPv1
Create Device and Port Groups ks
or
w
The SNMPv3 and CLI credentials have been created on each of the devices. The
N
devices need to be configured with the SNMPv3 credentials before being discovered
e
by NetSight.
m
tre
1. From the Toolbar click on the Authorization/Device Access icon and then
select the Profiles/Credentials tab.
Ex
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
4. Add the CLI Credentials for the Wireless Controller and XOS Switch, both of
these devices do not support all the MIBs that NetSight utilizes for configuration
and management.
5. Select the CLI Credentials tab.
6. Add the CLI Credentials, and then click on OK.
a. User Name = <your SNMP Username>
b. Description = Device_Access
c. Login & Configuration password = training
d. Type = SSH
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
7. Create the Device Access Profile (Add Profile), combining the SNMP and CLI
Credentials.
a. Profile Name: Mgmt_Class
b. SNMP version: SNMPv3
c. Read/Write/Max Access: training
d. Security Level: AuthPriv
8. Set the CLI Credential to Device_Access, Click OK.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
9. Change the Default Profile setting to your SNMPv3 profile, i.e. Mgmt_Class
ok
Bo
-e
Now that SNMPv3 is configured on the switches and in Console, we will have
Console use the SNMPv3 Device Access profile to communicate to the switches.
ks
or
w
et
N
e
m
tre
Ex
First you will discover your switches using SNMP. Several devices are located on the
Network:
- XOS Switch (Switch-A)
- EOS Switch (Switch-C)
- NAC Gateway
- Wireless Controller
1. From Console go to Tools > Discover to launch the Discover window.
2. From the IP Range tab, enter your IP range using the Start IP and End IP
columns. (Do a quick double click in the box to get the prompt to show.)
ok
a. Range : Your Device Discover IP Range(s) (See Appendix Section
C)
Bo
b. Profile: Mgmt_Class
c. Poll Type: SNMP
-e
3. Click the Discover Button.
ks
or
w
et
N
e
m
tre
You will notice that the “Progress” bar is updating based on the SNMP polling.
NetSight is reaching out to each device within the IP range for a successful contact.
Ex
4. The devices that match the Device Profile will be displayed in the Discovered
Device table. You should see 4 devices; Wireless APs are managed by the
Controller.
ok
Bo
-e
ks
or
w
et
N
7. Add the Active Directory Server (Windows 2008 Server) that is part of this
tre
network.
Ex
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
In this lab we will add a 3rd Party device to our network. The Device will vary
depending on the location of your Class.
1. Select My Networks, right-click and select Add Device from the drop-down
menu.
ok
Bo
-e
ks
or
2. Add Device. Enter the following variables: (See table in the Appendix Section C)
w
et
b. Profile: public_v1_profile
e
m
tre
Ex
3. You will notice that the device is added with the “?” icon, because the
sysObjectID does not match any property defined in the DeviceType.properties
or myDeviceTypes.properties files.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
5. In the MIB Tools window, make sure that the Device is your 3rd Party Device.
6. In the Find what: window, type sysObjectID and then click Find. Once the
Variable is displayed click on the Query button to display the value.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
7. Record the Raw Value (OID Value) and Formatted Value below.
Ex
8. Use Putty and SSH to your NetSight Server, login username: root, password:
training.
9. User VI edit the
/usr/local/Extreme_Networks/NetSight/appdata/System/deviceTypes/myDeviceT
ypes.properties file
vi usr/local/Extreme_Networks/NetSight/appdata/System/deviceTypes/myDeviceTypes.properties
Note: The file will show you examples and if you would like to add your own images
they will need to be placed in the specific directory listed in the file.
10. Add the appropriate information to the file. Do not include the “<>” symbol. Note:
This information may not match your environment, if you are unsure contact the
instructor.
ok
<sysObjectID raw value> = <sysObjectID formatted value>
Bo
<sysObjectID formatted value> = <sysObjectID raw value>
<sysObjectID formatted value>.family=<Family Name>
-e
<sysObjectID formatted value>.name=<Device Name>
<sysObjectID formatted value>.treeicon = 3
ks
<sysObjectID formatted value>.mapicon=switch.gif
or
w
et
N
e
m
tre
Ex
11. Once you are finished, save and close the file. <ESC> :wq!
ok
Bo
13. After 2 minutes, re-launch the NetSight Client page, select Console and login
-e
again (since the file is local, if the file was updated on the Server, restarting
NetSight would have been required). ks
14. In the Device list you should see the Device Listed with its icon.
or
w
et
N
e
m
tre
Ex
You can Create Device Groups for Organizational Purposes. You will create a Device
Group for the Devices that we will be managing in this Class.
1. Right click on My Network and select Add Device Group.
ok
Bo
-e
ks
or
w
3. The StudentX folder appears as a device group. Select the 3 devices (Switch-A,
N
Switch-C and Wireless Controller) and drag the devices to this new group. Now
you have a manually created device group that consists of your Devices. Click
e
4. You will notice that the 3 devices are now under the StudentX custom folder
(yellow folder).
ok
Section E: Add a Device Group - Ports
Bo
-e
1. Create a Device Group of Ports.
2. Select the Device and right-click Add Device Group.
ks
or
w
et
N
e
m
tre
Ex
In this section of the lab you will create an Uplink Ports group that contains the uplink
ok
ports on all switches. This will allow you to created policies that are different on these
Bo
ports vs end-system ports later in the lab.
-e
1. Right-click on My Network and select Add Device Group.
ks
or
w
et
N
e
m
tre
Ex
5. Sort the Interface by Current link, by selecting the Current link column header.
6. Right-Click on interface name esa0 (Wireless Controller) and select Add Port
ok
Elements to Group.
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
ok
Bo
-e
8. Select the highlight the XOS Switch.
9. Select the Interface Summary flexview tab and retrieve the port information.
ks
10. Select the port 23, right click and select Add Ports Elements to Group.
or
12. Select the Switch-C (EOS), select the ports that are the inter-switch links (uplink
ports, right click and select Add Ports Elements to Group.
ok
Bo
-e
13. Select the Uplink Ports Group and then the Interface Summary Flexview from
the dropdown menu.
ks
14. Click the Retrieve button to see the details of the Uplink Ports.
or
w
et
N
e
m
tre
Ex
ok
Section A: Device Groups/Using the Table Editor
Bo
1. In the My Network tree, select Grouped By > Location > Unknown. Three
devices should be displayed. In the right hand menu select Properties. These
-e
are the 3 devices that will be used during the lab.
ks
or
w
et
N
e
m
tre
Ex
2. Select the Device radio button in the Properties tab, and scroll to the right.
Notice that the Location and Contact groups are not fully configured (blank).
These groups are based on the sysLocation, sysContact and sysName object
name of the SNMP v2 MIB.
Note: If your Lab configuration has only a single Switch-C (SSA) do not
configure the Switch-C (SSA)
ok
Bo
-e
ks
or
w
5. Highlight each switch individually, at the bottom of the screen a box will be
displayed that will allow you to modify or set the MIB object. Enter the
following:
a. Contact = StudentX (where X is your student/group number)
b. Location = Your Location
ok
Bo
-e
ks
6. Notice, where you have made changes there is the ! sign. This informs you that
or
changes have been made in NetSight but not written to the switches.
w
7. Click the Apply icon to push/write your changes directly to the switches using
et
SNMP-sets.
N
e
m
tre
Ex
8. After Console is finished with the MIB sets, right click on the “My Network” and
select Refresh.
Notice what happens to the Contact and Location Group Groups. You
should see three groups.
9. Select the Console tab below; examine the Console Event Details on why the
Wireless Controller failed.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
1. Instead of using the Web Interface on the Controller to set the sysContact and
sysLocation variables we will use the scripting tool.
2. Select either Unknown Contact or Unknown Location and right-click to display
the drop down menu, select Execute Command Script.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
3. The Command Script Tools will open, the Device is listed as V2110. Enter the
following commands in the Commands window.
ok
Bo
-e
ks
or
w
4. The Execute Command Script Status Window opens; you will see the Status
et
5. Back at the Command Script Tool you can save the commands for future
controllers. Click on the Save Script File icon, the local directory will be display,
enter a File name and then click Save.
Note: If you want this script to be available to all NetSight Users you must
save it on the Server.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
6. After you save, select the Open Script file icon and select Open Local Script
File to view your script.
Ex
In this section of the lab you will view and configure various FlexViews.
1. From Console highlight your XOS Switch, select the Interface Summary tab
and click the Retrieve button .
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
2. Right click in any column in FlexView and select the Type column, right-click
and select Hide Column and repeat this with Speed column. Or you can select
what information is not important to you. These will be applied immediately. If
you need to add these back in select a cell in the table, right-click select Table
Tools > Settings.
ok
Bo
-e
ks
or
w
5. Name the file Modified Interface Summary and save it in the default My
e
Back in the FlexView screen you will have to do another Retrieve to re-populate the
new FlexView
If you want to display the devices by their names, select Options > Data Display
Format and select Use system name in the “How to display devices in the device tree”
option.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
ok
Bo
Section A: Create a Map
-e
1. From Console select All Devices, right click and select Create Topology Map.
ks
or
w
et
N
e
m
tre
Ex
2. Select the Attributes in the Map Creation Tool window, enable LLDP, and leave
all the options at default.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
3. Click Continue then Finish. Console will then poll the switches based on the
Polling options.
Ex
4. The All Devices icon will be displayed on the map. Once the Discovery is
completed the Discovery is completed the Discovery Results will be displayed.
6. Double click on the All Devices icon; All the devices it has learned will be
displayed. The Wireless Controller, AD Server and the 3rd party device will need
to be linked manually.
7. To link the devices, press Ctrl on the keyboard then select device 1 and device
ok
2 using the table below.
Bo
Please see the Appendix Section B for the Actual Ports numbers for the Map.
-e
Device 1 Port Device 2
ks Port
AD Server Core Router
3rd Party Device Core Router
or
Controller switch
et
N
e
m
tre
Ex
ok
Bo
-e
ks
or
w
et
9. In the Link Devices window, choose the ports which connect your Controller to
N
10. Repeat for all your devices. All devices should be linked based similar to the
configuration below.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
1. Double click on the XOS Switch to see its neighbours; this is similar to what
would show up in OneView Portview (which will be covered later).
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
2. Select the link between the EOS Switch and XOS Switch, double click to see
the Link Data.
ok
Bo
-e
ks
or
w
et
N
4. Select the tabs on the top to see Device A, Device B. In the Link Information
section select each tab to view the results of the discovery.
ok
Bo
-e
ks
or
1. From your MAP ROOT highlight the XOS Switch. Go to Edit > Group into New
Submap.
My F
ok
Bo
2. Right click on the New Submap icon.
-e
ks
or
w
et
N
e
m
tre
Ex
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
4. Select the EOS Switch and the Wireless Controller and then select Edit > Move
Devices to Submap..
ok
Bo
-e
ks
or
w
et
N
5. In the Move Devices to Submap window, open the tree and select My Virtual
e
7. Use Edit > Shapes and Text on the Submap to add a little flair if desired.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
ok
Bo
-e
ks
or
w
et
ok
Bo
-e
ks
or
w
et
N
e
m
5. Click OK.
tre
7. Use the left arrow key icon (shown below) to bring you back to the main map.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
Section E: Overlays
1. Go to View > Overlay, select the different Overlays to view how the data
changes. Select Link Source and Physical.
Note: If a device does not support the MIB the device will not change their
display.
.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
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.
ok
Bo
-e
Section A: Inventory Manager Overview
In this section of the lab you will become familiar with Inventory Manager.
ks
or
1. Launch Inventory Manager either from the NetSight Client Web Page or from
w
2. Take a few moments to explore the available drop-down menus and the options.
Notice the four main tabs:
a. Network Elements shows all Network Devices.
b. Firmware Mgmt provides a comprehensive listing of all the
firmware images that are available for use.
c. Archive Mgmt allows you to view the library of stored Device
Configurations that you’ve previously “backed-up”.
d. Configuration Templates allows you to view the various
configurations that you have available.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
1. You can check what firmware is running in the Network Elements General tab
for each Device, by selecting the device. In the General tab you will see the
Firmware Version.
ok
Bo
-e
ks
or
w
et
N
e
1. Select Tools > Push Local Firmware to Server. Push from the local
C:\tftboot directory to the to the /tftpboot/firmware/images directory on the
Ex
NetSight Server.
2. Each image individually. Place them into the TFTP Firmware Directory.
a. Copy over summitX-15.5.2.9.xos
b. Copy over summitX-15.5.2.9-ssh.xmod
c. Copy over S-822xx-xxxx
ok
Bo
-e
ks
or
w
et
N
e
m
4. Right click on Device Type and click Refresh to populate the images. (Note:
If the Images are not displayed check the Security Permission settings on the
Ex
tftpboot directory)
The ExtremeXOS device at this time does not support the CTdownload Mib, therefore a
script must be used to perform the download. This script has already been created in
NetSight. The script will allow you to download the Firmware and the SSH module at the
same time.
1. Right Click on the XOS switch and Select Wizards > Firmware Upgrade
Wizard.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
2. The Firmware Upgrade Wizard will start, click Next. At this point do not add the
other devices; each device must be upgraded separately due to difference in
hardware/software.
ok
Bo
2. Double click on the XOS software and click Next. (select the summitX-
15.X.X.X.xos)
-e
ks
or
w
et
N
e
m
tre
Ex
3. Pop-up window will allow you to select to also download the .ssh module at the
same time. MAKE SURE YOU SELECT TO DOWNLOAD THE SSH XMOD AT
THE SAME TIME AS THE FIRMWARE IMAGE.
4. In the Assignments window scroll over to the Image Name column and make
sure that both the .xos and .xmod images are listed, if not use the Previous
button to go back and repeat the above steps again.
ok
Bo
-e
ks
or
5. Click Next.
w
et
6. Schedule the download to occur in two minutes then select Finish. Note: The
Download will take several minutes to complete.
N
e
m
tre
Ex
ok
Bo
-e
ks
or
w
Note: The download of the firmware and installation will take a significant
amount of time. Close the Scheduled Events window and continue to the next
lab instead of waiting.
Note: If you only have a Single Switch-C in your lab environment skip this
section of the Lab.
1. Select the Switch-C (EOS) and launch the Firmware Upgrade Wizard.
ok
Bo
-e
2. The S-Series (EOS Switch) is added automatically.
ks
or
w
et
N
e
m
tre
Ex
3. Click Next.
4. If you want to see all the images click the Show All Images button.
ok
Bo
-e
ks
6. Double click the latest S-Series firmware and then click Next.
7. In the next window you can either start the down load or schedule one. Click
or
Start.
w
et
N
e
m
tre
Ex
ok
Bo
10. Once the EOS Switch is rebooted, you should see the Device Status go from
-e
Contact to No Contact back to Contact, click Finish.
11. At the bottom of the screen monitor the Active Status: Summary or Active
ks
Status Details Events log to monitor the TFTP firmware upgrade. Double
click on an entry to obtain more detail.
or
w
et
N
e
m
tre
Ex
ok
Switch primary Wed Oct 22 16:48:50 ___ 2014 15.4.1.3 summitX-15.4.1.3.xos v1541b3
Switch secondary Thu Aug 7 00:54:50 UTC 2014 15.5.2.9 summitX-15.5.2.9.xos v1533b5
Bo
Switch secondary Tue Oct 21 11:01:01 ___ 2014 15.5.2.9summitX-15.5.2.9-ssh.xmod v1533b5
-e
3. Select the XOS Switch from your Device Group. ks
or
w
et
N
e
m
tre
Ex
4. Launch the Reset Wizard from your button at the top of the screen.
5. In the Reset Device Wizard window, the XOS Switch will be displayed. Click
Next.
ok
Bo
-e
ks
6. Choose Cold boot and click Start.
or
w
et
N
e
m
tre
Ex
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
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.
ok
Bo
Section A: SCP Transfer Settings
-e
1. In Inventory Manager (IM) go to Tools > Options > File Transfer Settings >
ks
SCP Transfer Settings
or
2. Change the Login Information to Username: root, Password: training. Also
notice the Root and Firmware Direction section. This is where IM will look
w
for firmware.
et
N
e
m
tre
Ex
ok
Bo
-e
2. Select the Devices tab at the top.
3. Sort the Devices by Location.
ks
4. While holding the Ctrl button, select your Virtual Lab Devices (Not the Core
or
Network Devices).
w
5. After all 3 devices are highlighted, right-click and then select Configuration
Firmware > Backup Configuration.
et
N
e
m
tre
Ex
6. You will now be told to see the “Inventory Manager log for progress”.
7. The configs will be located in the following location if it is a windows based
server:
ok
Bo
-e
ks
or
w
et
9. Look at the Event log’s Active Status: Details to follow the progress of the
e
backup, you will see that it has finished and the OneView Archive is complete.
m
tre
Ex
10. Select the Archive Mgmt Tab. Open the OneView Archive tree. The results
will be displayed.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
1. In OneView, click on the XOS Device, the Interface Summary table will be
displayed.
2. Select the Port 7 Interface, right click and select Edit Selected Rows.
ok
Bo
-e
ks
or
w
3. In the Edit Selected Rows window, click Enable, change the Admin Link to
et
4. You will notice that the Table is refreshed and the Admin Link on Port 7 is down.
5. Open the Inventory Manager window again, select the Archive Mgmt tab.
Right-click on the OneView Archive folder and select Stamp New Version.
ok
This will run the Archive again.
Bo
-e
ks
or
w
et
N
e
m
tre
6. Now you have two configuration backups for all the switches in your lab for two
different time periods. Notice there is an alert on the Achieve to indicate a
Ex
configuration change.
7. Open the recent Date of the Backup and see that there have been changes.
Select the XOS Switch to view what has been changed.
8. Check for any differences in the two backups for the XOS Switch. Right click on
ok
the XOS Switch and select Compare Configuration Files.
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
9. Select the two different (time date) folders then Compare. By highlighting each
switch you can see that the configurations for both time periods are different.
ok
Bo
-e
ks
or
w
10. Scroll down the Configuration to view the differences, you will also notice some
of the commands that were created on the switch from when we used NetSight
to create sysContact and sysLocation.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
2. Select the first archive of the XOS switch (with port 7 disabled) and proceed to
download it to the switch.
ok
Bo
-e
3. Click Next, in the Restore Configurations window click Start. When the Restore
is completed. Click Finish.
ks
or
w
et
N
e
m
tre
Ex
4. The Switch will reboot and you will lose connection to the NetSight Server
because it is located off Port 5 of the XOS Switch.
5. After the switch resets, open OneView, select the Device Tab.
6. Select your XOS switch to view the Interface, verify that Port 7 is now enabled.
7. Using Inventory Manager, using the Archive Wizard create a scheduled archive
ok
that will backup all devices daily starting at 10:00pm. If possible check the
Bo
archives tomorrow to verify it ran. Now the configurations on all the devices on
your lab network will be backed up daily.
-e
ks
or
w
et
N
e
m
tre
Ex
Objective:
Enable statistic collection on the devices, clients and interfaces for up-to-date
statistics and trend reporting
In order to view Device and Interface reporting via OneView you must enable statistic
collection on your Devices.
ok
Bo
Section A: Device Statistics
-e
1. Launch OneView, select the Devices tab. Sort the Devices by Location, only
enable Device and Interface Collection on the Virtual Lab.
ks
2. Select each Device individually, right-click and select Collect Device Statistics.
or
(EOS switch)
w
et
N
e
m
tre
Ex
ok
Bo
-e
4. Repeat for the Wireless Controller, the Collect Controller Statistics window
opens. ks
or
w
et
N
e
m
5. Click OK.
6. Repeat on the XOS Device.
a. Select Historical.
ok
Bo
-e
ks
or
w
et
Note: Devices are different each device type must be performed separately.
tre
2. In the OneView Devices table, select the first device, i.e. EOS Switch, right-click
and select View Interfaces.
Ex
ok
Bo
-e
3. Sort the Interface by the Current Link Status, Enable interface statistic collection
ks
for all the interfaces on your controllers. Shift-click to select the ports and
right-click and select Collect Interface Statistics.
or
w
et
N
e
m
tre
Ex
4. In the Collect Interface Statistics window select the Historical radio button and
select OK.
ok
Bo
5. Repeat the process for the Switch-A (XOS) Switch.
-e
ks
or
w
et
N
e
m
tre
Ex
ok
Bo
-e
2. Select any of the Devices in the list, right click and select View Interfaces.
ks
or
w
et
N
e
m
tre
Ex
ok
Bo
-e
Overtime the Device Statistics will be collected from the Device and Reports to
OneView. When tools such as PortView and Reports are generated they will use the
information collected from these devices.
ks
or
w
et
N
e
m
tre
Ex
ok
Bo
In this example, an end-user has called the help desk communicating that he cannot
access some servers on the network, we will determine which port a particular end-
-e
system is plugged into a switch using Compass because at this time NAC has not
been implemented in the network. The end-user has told you the IP address his
device has received on the network.
ks
or
3. In the Search criteria, select your Device Group that you had created in the
previous lab from the Drop Down menu.
Notes: When using the Search tool, for optimal speed search as few devices as
ok
possible. This becomes important on a large network.
Bo
4. In the Search Type select IP Address and in the Address box enter IP address
of PC-B (See Appendix C for IP address).
-e
5. Click the Search icon. ks
or
w
et
N
6. The Results will be displayed; you will see that the IP address has been seen
from multiple Sources, the Address type displays where this information was
e
m
derived. The Compass Options on the right allows you to select which devices
options to check.
tre
7. Look at the results of your search. Determine which ports the PC was
Ex
discovered through and if it can still be discovered through those ports. (Active
would be selected). The Address Type of MAC would indicate the physical
Location of the device.
8. If you scroll across the window you can view the Source column, it lists the MIBs
used to obtain the information.
9. Using the Compass Option on the right, deselect the Layer 2 box. Notice what
information is lost.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
Overtime you may notice that there may be a consistent display of the small-set of
Sources that are providing the information that you require. If so, you may want to
narrow down the search list.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
2. Click on the Compass Options button; restore the variables to the default, by
selecting the Restore Defaults button.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
3. Open NetSight Console, select your Virtual Lab Location and then click the
Compass tab. Select the Search Type=All. Click Search.
ok
Bo
-e
4. Note how long it takes for Compass to return your search results and the
sources of the results. ks
or
w
et
N
e
m
tre
Ex
5. Open the Console Tools Options again and configure the searched MIBs as
shown below.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
1. Select the Interface Summary Flexview, retrieve the port information and select
port 7 from the XOS switch, right-click and select to Add Port Elements To
Group.
ok
Bo
-e
ks
or
w
3. Repeat the Process on Switch-C (EOS Switch) by selecting the port that PC-D
is connected. Please the Appendix for PC-D location.
1. In the NetSight Console Window, select All Devices and select the Interface
ok
Summary FlexView.
Bo
-e
ks
or
w
et
4. Browse and the Interface folder and select the Interface Statistics FlexView.
ok
Bo
-e
ks
or
w
et
N
5. Notice that the Interface Statistics tab is displayed at the top, click the Retrieve
button to obtain the information for the switches. You will notice that the Data is
e
6. Change how the data is displayed by selecting the Pie Graph view.
ok
Bo
-e
ks
7. Put your cursor on or near the word FlexView (shown below). Left click on the
or
mouse, and then drag the cursor in any direction.
w
et
N
e
m
tre
Ex
9. Change the Poll Frequency timer to 10 and click the Retrieve button.
ok
Bo
-e
ks
10. Remember to set the poll timer back to 0 later then click on the retrieve button.
or
11. Click the button on the floating FlexView in the top right. The FlexView
w
1. Click the FlexView menu icon and select Open. In the Flexview browser window,
click Export Catalog button and save the file to the C:\ drive (use any name).
ok
Bo
-e
ks
or
2. Open your newly created file. This is a nice reference sheet on the description of
w
the FlexView.
et
N
e
m
tre
Ex
Section C: Statistics
1. From the FlexView icon, click Open. Navigate to the Interface folder.
ok
Bo
-e
2. From the Interface folder, open the Interface Statistics FlexView. Choose your
ks
All Devices folder and click Retrieve. Right click on any line in the table and go
or
to Table Tools > Settings.
w
et
N
e
m
tre
Ex
3. Select Yes for Show the row count column? Then Apply and Close.
ok
Bo
-e
ks
or
w
et
N
4. Now you can see how many rows there are in the FlexView.
e
m
tre
Ex
Clicking on any column will give you the top talkers on your Network as far as Octets,
Packets, Unicast Packets, or any column listed.
1. Click twice on Total Octets.
2. Highlight the top 10.
3. Click on the Pie Graph view icon and do a Refresh. The Top 5 values are
automatically graphed.
4. Select the General Controls tab and set n to 10.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
5. In the Columns tab deselect total Octets and select Total In Packets, then
unselect everything else. Click Refresh to repopulate your graph.
ok
Bo
-e
ks
or
w
et
6. Click the Bar Graph view to see the same information in a bar graph format.
N
e
m
tre
Ex
ok
Bo
-e
ks
or
w
et
N
e
m
7. Now select a Graph Type of Rate. Rate takes two time frames compares the
tre
Total In Packets for the two time frames and displays the difference.
8. Go back the Absolute Data Graph Type, and in the Columns tabs have only
Ex
14. Go to the Pie Chart view and export the graph using the Save icon (Notice
you can only export data when in the Line Graph – real time). Find your graph
picture and open it.
1. Launch OneView.
2. Click Devices from the OneView in the top tool bar.
3. Select a Device.
4. From the top left drop down menu; select Choose FlexView.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
5. The Open FlexView window will be displayed; select the RMON Ethernet
Statistics FlexView.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
6. Once the table is displayed manipulate the columns and create filters. Note:
Only FlexViews stored on the Server will be listed, FlexViews created in “My
FlexViews” will not be available.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
You can configure SNMPv3 snmptrapd.conf file and set SNMP traps on a device that
ok
supports the appropriate MIB, like Extreme switches. Identifi Wireless Controller does
not support the MIBs that are used to write the SNMPtrap information; this device will
Bo
be configured manually.
-e
1. From Console highlight your StudentX devices.
2. Right click and select Trap Receiver Configuration.
ks
or
w
et
N
e
m
tre
Ex
3. Set up the Trap Receiver Configuration (this will be your NetSight Server) by
setting the Trap Credential to the SNMPv3 credential you configured earlier,
user:<your SNMP username>,group:<your SNMP group>.
4. A green ! mark next to the IP address in the lower portion of the window
indicates that the set will take place on the device, not the caution symbol next
to the Wireless Controller, this is not support.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
6. In the Trap Receivers on Devices section you should see the # of Receivers
increment to 1.
ok
Bo
-e
ks
or
w
7. Click on the snmptrapd tab. Ensure that the Trap Credentials Credential name
et
(training) is equal to what you created. Use the dropdown menu on the
N
require both the Security User credentials and the Engine ID of the sending
m
SNMP agent in order to process the packets sent from the devices.
tre
Ex
ok
Bo
-e
ks
or
10. Click on the Save button. Click OK to accept the Restart Service warning. Click
w
Close.
et
N
e
m
tre
Ex
Devices can generate traps based on a number of items; most common is when a port
transitions from an up state to a down state.
ok
1. Select the Server Ports Device Group and Retrieve the information on the ports.
Bo
2. Right-click on the Devices and select I/F Disable to disable the interface.
-e
ks
or
w
et
N
e
m
tre
Ex
3. Retrieve the Interface information again, you will notice the following:
a. The Admin status is “down” indicating that the port had been
disabled.
b. The alarm/device status beside Switches has turned orange to
indicate an error on the device or device group.
4. Verify the devices are sending traps. Click on the Traps tab at the bottom of
your NetSight screen.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
5. Double click on any single trap event to display additional information about the
trap.
ok
Bo
-e
ks
or
w
et
6. In the Traps tab, check the Acknowledge checkbox beside your Warning
N
7. Click the Alarms tab at the bottom of Console. Notice the details of the Alarm,
i.e. Port Disable is listed in the Alarm table.
ok
default is green. Retrieve the port information and noticed the Current Link
status is green.
Bo
The Alarms are cleared on NetSight because of the Alarm Options setting
determine when to clear the alarm.
-e
ks
or
w
et
N
e
m
tre
10. If you click on the Alarm History, it will display the alarms that were displayed
recently and alarms to indicate that they were cleared.
Ex
ok
1. From Console select Tools > Alarm/Event > Alarms Manager.
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
2. Click New Alarm and provide a name – “Link Trap Alarm” Click on OK.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
3. Click the Select Groups button and select the device group that can trigger this
alarm – select the Server Ports device group. Click on OK.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
4. Select the By Selected Trap radio button, and then click Edit Traps.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
5. Click on the Name column to sort your traps by name. Scroll and add the
snmpTraps linkUp and linkDown as shown. Hint: Sorting the Traps by
Enterprise makes them easier to find.
ok
Bo
-e
6. Be sure to hit the Apply button. Then click OK.
7. Click the Actions tab.
ks
8. Click Syslog Servers(s).
or
9. Enter your NetSight Server IP address. Note: In your environment this could be
w
10. In the Alarm Suppression section, select Enable Action Limit and set the Max
Count to 5. Set the Reset Interval to 1 Hour. This will keep you from being
inundated with alarms.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
11. Check the Enable Alarm checkbox. Alarms Manager should look like the below
screen shot.
ok
Bo
-e
ks
or
w
et
From either NetSight Console or OneView, disable port 7 on the XOS Switch. Then
enable port on the XOS Switch. Below shows the example with OneView.
1. Launch OneView, select the Devices Tab.
2. Select the XOS Switch, right-click and select View Interfaces from the drop-
down menu.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
3. Using the Interface Summary FlexView in Console, select port 7 and then right-
click. From the drop down menu select Edit Rows.
ok
Bo
-e
4. Select the Enable box and then select the Admin Link: Down. Click OK.
ks
or
w
et
N
e
m
tre
Ex
5. In NetSight Console select the Syslog tab in NetSight Console, you should see
the new Syslog Message, select the Traps tab, the trap should be displayed.
6. Enable Port 7 again.
Using the Topology Manager and OneView Map we will look at how these tools can
show status changes to the network.
ok
You will now simulate a failure by changing the SNMPv3 Profile in Console for the
Bo
Wireless Controller.
-e
1. In NetSight Console, open Tools > Topology Manager.
ks
or
w
et
N
e
m
tre
Ex
ok
Open the Wireless Controller from the Available Devices.
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
7. Open the table editor, change the profile from Mgmt_Class profile to
“snmp_v3_profile” and click the Apply button.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
ok
Bo
2. Drill down into the All Devices view and follow the path that will lead you to
-e
which device is unreachable. ks
or
w
et
N
e
m
tre
Ex
3. Select the Device to view additional tools that could be used to determine the
cause of the issue, i.e. Ping, Port View.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
4. Select the Ping tool, this will open a window to see the results.
If there are a large number of devices to view the Topology Manager Find Device
function can pinpoint the device.
1. In Topology Manager select Edit > Find Device and then enter the IP address
of the Device that is down via the indication of the “red” alarm.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
OneView Devices or the Console Device table will displayed and show the alarm.
1. On NetSight Console in the Alarms window you will see that an alarm was
generated because SNMP has lost contact.
ok
Bo
2. Select the Devices tab, you will see the Alarm icon next to the Device.
-e
ks
or
w
et
N
3. Launch OneView, select Alarms and Events > Alarms. It should display the
same information.
e
m
tre
Ex
5. Enter a Reason and click Submit. You will notice that the alarms have been
removed from the Table.
ok
Section E: Reset SNMP on the Wireless Controller
Bo
1. Go back to the Authorization/Device Access > Profile/Device Mapping and
-e
set the snmp profile back to Mgmt_Class for the Wireless Controller using the
table editor. Click Apply and close the window. After a while the device should
turn green again.
ks
or
w
et
N
e
m
tre
Ex
There is one Purview appliance in the network, the NetSight Server that is managing
the Purview will depend on your training environment/location.
ok
Bo
1. Contact the NetSight OneView Server, i.e. http://ext-training:8080.
-e
2. Login with the credentials username: readonly, password: readonly
3. Launch OneView. ks
or
w
et
N
e
m
tre
Ex
4. The OneView toolbar will show Reports and Applications. Select the
Applications tab.
5. Change the Dashboard drop-down menu and select Dashboard. Notice the
Client, Server, Bandwidth and Application.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
6. Select any Application and double click to drill down into the details.
ok
Bo
7. The clients that are using the application will be displayed along with the
Bandwidth. In a real environment you could ask yourself if this application
-e
complies with the company policy and/or is this normal bandwidth for this
application or is this client supposed to be using this application. If not, then
actions such as Policy Rules can be created to deny traffic or limit traffic on the
ks
network.
or
w
et
N
e
m
tre
Ex
8. Select one of the clients and view what other application this client is using on
the network.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
The Applications Browser allows you to generate reports in several different formats
using data based on selected options including a data target, statistic type, and other
search criteria.
1. From the Browser tab. Use the Options to select different aspects of the
Network, for example, Application Response time, Utilization and then click
Submit.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
Objectives
At the end of this lab you will be able to:
Access Policy Manager and Import a Policy Manager Domain file (.pmd)
Apply a Role to a Port
Enable Dynamic Authentication (MAC Authentication)
Use Monitoring tools such as Rule Usage and End-User sessions.
Note: This Lab is only supported on the ExtremeEOS switch at this time.
ok
Section A: Check network connectivity from PC-D
Bo
-e
1. Access your PC-D, all the following tasks in section A are carried out from
your PC-D. ks
a. Run a continual ping to its default gateway, at this moment it should
succeed.
or
succeed.
et
succeed.
d. Open up a HTTP session to the Radius Server, it should succeed.
e
m
succeed.
Ex
ok
Bo
2. Import the MGMT Policy Domain by selecting File > Import > Import From
-e
File…
ks
or
w
et
N
e
m
tre
Ex
Note: Please see Instructor for the location of the .pmd file if it cannot
be found in the default directory.
ok
Bo
-e
ks
or
w
et
4. Select All to Import all the Data Elements and overwrite existing elements.
N
5. Click OK.
e
m
tre
Ex
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
Adding a Policy Role to a device Port will provide a default Role to a port, for example in
a conference Room, if a guest or visitor not required to Authenticate connects into the
port they will obtain the default role.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
ok
Bo
-e
ks
or
w
et
N
Result
tre
Result
6. Any tasks carried out under the Network Elements / Ports Groups tab in
Policy Manager is real time unlike that under the Roles / Services tab that
required you to click on the Enforce.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
Enabling Authenticated can allow user to authenticate on the same port that we just
assigned a Default Role; these Dynamic Users will be assigned a Role based on Rules
on the backend Authentication Server, i.e. RADIUS Server. Note: The RADIUS Server
has been preconfigured on the Switch.
1. In the Policy Manager Application, select the Switch-C (EOS) from the Network
Elements/Port Group view.
2. Select the Details View tab and open the Chassis-1 slot tree.
3. Find the port the PC-D is connected to, right-click and select Properties.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
ok
Bo
-e
10. Check to see what network access PC-D has now, if you are unsure what
access it should have check the rules associated with Enterprise User.
ks
or
w
et
N
e
m
tre
Ex
ok
Section A: Restore NAC Database
Bo
NAC manager has been pre-configured the necessary information for End-System
authentication for visibility.
-e
1. Open the NAC Manager application. Select Applications > NAC Manager.
ks
or
w
et
N
e
m
tre
Ex
2. When the NAC Manager window displayed, restore the NAC database.
File > Database > Restore NAC Configuration
ok
Bo
-e
ks
or
w
et
7. Enter the IP address of your NAC Gateway, see Section C of the Appendix.
Click OK.
ok
8. Select the Switches tab; Add the Switch-A (XOS) to be managed by the NAC
Bo
Gateway.
a. Select the Switch-A to add to the appliance group.
-e
b. Set the Primary Gateway parameter to the IP address of the NAC
ks
Gateway. When the Add Switch screen is completed and the
configuration is written to the switch via SNMP, the switch will send
or
c. Set the Auth Access Type to Network Access to set the RADIUS
et
ok
Bo
-e
ks
Note: Before completing the addition of the switch, one other item may need to be
or
changed. If VLANs will not be used for registration or assessment capabilities, Port Link
w
Control should be disabled on the switch. By default, NAC will have Port Link Control
et
enabled since it will not know whether or not VLANs will be used.
N
e
m
ok
Bo
-e
ks
or
w
11. Deselect the Enable port link control. The Attribute Definitions are what will be
et
passed to the XOS switch when a Profile is assigned to an end-user during the
N
authentication process.
e
m
tre
Ex
c. Set the Auth Access Type to Network Access to set the RADIUS
configuration type directly to the switches.
ok
d. Assign the Enterasys (HiPath) Wireless. (Default)
Bo
e. Enable RADIUS Accounting.
-e
ks
or
w
et
N
e
m
tre
Ex
17. In the NAC Application Enforce window, select the NAC Appliance and select
Force Reconfiguration for All Switches.
18. Enforce the configuration on the Switches.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
NAC utilized the Universal Port Profile configuration to assign dynamic roles to end-
systems. These Profiles as well as the NetLogin configuration have been created by the
Instructor and will be written to the XOS switch via the Scripting capabilities in NetSight.
The script will also assign these dynamic profiles to the port that your PC-B is
connected to, Port 7.
1. In Console, right-click on the XOS switch. Scroll down and select Execute
Command Script.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
ok
Bo
-e
ks
or
w
3. If the Script file is not found locally, navigate to the Training share, NAC Folder
et
4. The script can be seen in the upper window. Select the NAC IP Address
variable, enter your NAC Gateway and then select Execute to run script.
ok
Bo
-e
ks
or
w
et
ok
2. Select the Identity and Access tab from the toolbar.
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
ok
Note: If the PC’s are not listed. You may have to reconnect the PC either physically or
by disabling and enabling the interface that the PC is connected to. For the wireless PC
Bo
ensure that the client is connected to the SSID broadcasted by the AP.
-e
ks
or
w
et
N
e
m
tre
Ex
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
6. The PortView will display the information about the Wired or Wireless
Configuration, Mobile IAM/NAC gateway, AP and the Wireless Client/End-
System view.
7. Selecting the other tabs will display information about the Wireless details
(Client and AP), Client History and NAC End-System Details. The
information will depend on the End-System selected.
ok
Bo
-e
ks
or
w
et
N
e
m
tre
Ex
ok
Bo
-e
ks
or
w
et
Note: Top Application Flow data will only be displayed if NetFlow is enabled on the
N
switch and collected by the NetSight Server. In this lab environment Flow information
will not be displayed.
e
m
tre
Ex
ok
Bo
-e
ks
or
w
et
N
e
m
tre
4. The End-System is now part of the BlackList group and will obtain the
Quarantine Role thereby limiting its access onto the network.
ok
6. Refresh the End-System table, the refresh button is located on the bottom left of
the screen. You will notice that the End-System Group information has changed
Bo
and a different policy has been applied.
-e
ks
or
w
et
N
e
m
tre
Ex