Table Of Contents
Performing Administrative Tasks
Using Discovery and Managing Devices
Managing Devices
Manage Devices
View Device Management History
Specifying Device Credentials
Specify Community Strings
Community String Guidelines
Specify the HTTP Username and Password
Managing Device Discovery
Overview: Discovery
Set Up Devices
Enable Discovery Options
Set Up Discovery Filters
Schedule Discovery
Run Discovery Now
Running Inventories
Immediate Inventory of Selected Devices
Immediate Inventory of All Devices
Viewing Inventory and Discovery Task History
Importing Devices
Import Devices from a File
Import Devices from CiscoWorks2000
Exporting Devices
Adding, Modifying and Deleting AAA Servers
Manage LEAP Servers
Manage RADIUS Servers
Manage EAP-MD5 Servers
Managing Groups
Overview: Groups
Creating, Editing, and Deleting Groups
Add a Group
Edit a Group
Delete a Group
Managing the Appliance
Viewing WLSE Status
Viewing Log File Reports
Log Files Displayed
Restarting the Wireless LAN Solution Engine
Managing the Software
Viewing Software Status
Defining the Repository
Installing Software Updates
Browsing the Repository
Viewing Software Update History
Overview: Security
Managing Security
Overview: Authentication Modules
Managing SSL (HTTPS)
Disabling or Enabling Telnet and Selecting SSH
Viewing the Last 10 Logged-On Users
Backing Up and Restoring Data
Specifying the Backup Location
Configuring a Windows 2000 or Windows XP Server as a Backup Location
Backing Up Data
Restoring Data
Using Diagnostics
Viewing and Creating a Status Report
Viewing and Creating a Self-Test Report
Viewing Processes
Setting Up the Splash Screen Message
Setting the Current Time and Date on the WLSE
Specifying NTP Time Servers
Specifying Name Servers
Specifying an SMTP Mail Server
Using Connectivity Tools
Managing System Parameters
Administering Users
Managing Roles
Managing Users
Add Users
Modify Users
Delete Users
Modifying Your Profile
Linking to a CiscoWorks2000 Server
Performing Administrative Tasks
The Administration tab allows you to you perform administrative tasks.
Note 
Some of the subtabs may not be visible to some users; what you view under the Administration tab depends on your login.
The Administration subtabs have the following functions:
•Discover—Manage devices, configure and run discovery, specify device credentials, run inventory, view discovery and inventory history, import and export devices, and set up AAA servers (see Using Discovery and Managing Devices).
•Group Management—Create groups for efficient device management and place devices in them (see Managing Groups).
•Appliance—Manage the Wireless LAN Solution Engine server (see Managing the Appliance).
•System Parameters—Configure polling parameters for collecting data from devices (see Managing System Parameters).
•User Admin—Manage users and user roles (see Administering Users).
•My Profile—Change your password (see Modifying Your Profile).
•Links—Set up links to CiscoWorks2000 servers and display server desktops (see Linking to a CiscoWorks2000 Server).
Using Discovery and Managing Devices
When you select Administration > Discover, the following options appear in the left pane:
•Managed Devices—View newly discovered devices, change device status, and view device management history—see Managing Devices.
•Device Credentials—Specify community strings for all managed devices and specify the HTTP usernames and passwords for access points (see Specifying Device Credentials).
•Discover—Schedule discovery, perform an immediate discovery, set up discovery filters, and set discovery options (including auto-manage—see Managing Device Discovery.
•Inventory—Run a one-time, immediate inventory to collect information from managed devices before the next scheduled inventory (see Running Inventories)
•Task History—View details on discovery and inventory jobs (See Viewing Inventory and Discovery Task History).
•Import Devices—Import devices from a file or from a CiscoWorks2000 server (see Importing Devices).
•Export Devices—Export devices to a CiscoWorks2000 server (see Exporting Devices).
•LEAP Server—Add, modify, and delete LEAP servers (see Adding, Modifying and Deleting AAA Servers).
•RADIUS Server—Add, modify, and delete RADIUS servers (see Adding, Modifying and Deleting AAA Servers).
•EAP-MD5 Server—Add, modify, and delete EAP-MD5 servers (see Adding, Modifying and Deleting AAA Servers).
Managing Devices
Before you can view discovered devices or perform any operations on them, you must move the devices to the managed state. When you select Administration > Discover > Managed Devices, the following options are displayed:
•Manage/Unmanage—View newly discovered devices, change device management status, or delete devices (see Manage Devices).
•Device History—View the management history of each discovered device (see View Device Management History).
Manage Devices
You can use this option to change a device's management status or delete a device.
Note Your login determines whether you can use this option.
Procedure
Step 1 Select Administration > Discover > Managed Devices > Manage/Unmanage. The device selector is displayed, showing:
•Newly discovered devices (New folder). All new devices are also listed in the Unmanaged folder.
•Managed devices (Managed folder)
•Unmanaged devices (Unmanaged folder).
Step 2 To view the contents of a folder, expand the folder.
Step 3 To modify the status of the devices in a folder, click the folder name. The Group Status pane appears. Select one or more devices from the list and click Manage or Unmanage in the Group Change Status window. Devices are moved into the Managed or Unmanaged folders.
You must move newly discovered devices to the managed state. Only managed devices appear in WLSE displays.
Tip If you want all discovered devices to be automatically moved to the managed state, enable auto-manage in Administration > Discover > DISCOVER > Discovery Options. For more information, see Enable Discovery Options.
Note You can only manage a total of 525 access points and wireless bridges. After you have placed 500 of these devices into the Managed folder, warning messages are displayed each time you place more devices in the folder. After the 525 limit is reached, no more devices can be placed in the Managed folder, although discovery continues after the limit is reached.
Step 4 After you move devices to the managed state, inventory is run for those devices. This ensures that device attributes appear in displays, such as reports and system-defined groups without waiting for the next inventory cycle. For information about running an immediate inventory, see Running Inventories.
Note When auto-manage is enabled, after devices are discovered an inventory is run automatically for the auto-managed devices. For more information about auto-manage, see Enable Discovery Options.
Step 5 To view details about a device, select the device from the device selector. The Device Details pane appears. You can change the device's status by using the Manage and Unmanage buttons.
Note Some details may not be displayed if the corresponding parameters are not set on the device; for example, Location and Contact.
The details in the Device Details pane are as follows:
Table 6-1 Device Details Pane
Field
|
Description
|
Device Name
|
Hostname, IP address, or SNMP sysname.
|
Description
|
Detailed device description.
|
Version
|
Software version installed on the device.
|
Device Family
|
Device type.
|
SysName
|
The system name.
|
SysObjectId
|
Unique identifier that identifies the device type.
|
Location
|
Where the device is located.
|
IP Address
|
Device IP address.
|
Subnet
|
Subnet in which the device is located.
|
Network Segment
|
The network segment in which the device is located.
|
Contact
|
The person to contact for this device.
|
Step 6 To delete a device, select the device from the device selector or dialog box and click Delete.
The device will be removed from the device selector and from all tables (including trend tables).
Related Topics
Managing Device Discovery
Device Name and IP Address Display
View Device Management History
The Historical Operations table shows information on all changes in device state (from unmanaged to managed or vice versa).
Note Your login determines whether you can use this option.
Procedure
Step 1 To view the Historical Operations table, select Administration > Discover > Managed Devices > Device History. The following information is displayed:
Table 6-2 Managed Device History Information
Field
|
Description
|
Timestamp
|
Date and time when the state change occurred.
|
Device Name
|
The device's hostname.
|
IP Address
|
The device's IP address.
|
State
|
The device's state:
•New—Device was discovered but has not been moved to the managed or unmanaged state.
•Managed—Device has been moved to the managed state.
•Unmanaged—Device is unmanaged.
|
Step 2 To sort table data, click on the column heading by which you want to sort the data:
•A triangle indicates ascending order.
•An upside-down triangle indicates descending order.
•No triangle indicates that the data is not sorted.
Specifying Device Credentials
This option allows you specify device community strings and HTTP credentials.
•SNMP Communities—Specify community strings for managed devices. See Specify Community Strings.
•HTTP User/Password—Specify the HTTP usernames and passwords for configuring access points. See Specify the HTTP Username and Password.
Specify Community Strings
The Wireless LAN Solution Engine uses a device's read-only community string to discover the device and uses the read/write community string to configure the device. If community strings are not entered correctly, the Wireless LAN Solution Engine cannot communicate with the device. Both read-only and read/write community strings are required.
The default community string is public for both the read-only string and the read-write string. If the community strings on your devices differ from the defaults, you must specify the community strings before the discovery process can begin and before you can configure the devices.
Note Your login determines whether you can use this option.
Procedure
Step 1 Select Administration > Discover > Device Credentials > SNMP Communities. The SNMP Communities dialog box appears.
This dialog box contains a default entry that covers all devices, provided device community strings are set to the default (public).
Step 2 To add new entries, you can enter community strings by using either of the following methods:
•Use the individual text boxes and list for the variables: Hostname (IP address), Read Community, SNMP Timeout, SNMP Retries, and Write Community. Then click Add. The community string appears in the large textbox.
•Enter the data directly in the large text box using the following syntax:
target:read_community::timeout:retries:::write_community
Note You must enter the correct number of colons between variables. Otherwise, the community strings cannot be read.
Information about the variables follows. For more details, see Community String Guidelines.
Table 6-3 Community String Guidelines
Variable
|
Description
|
Notes
|
target
|
The IP address of a device or range of devices that use these community strings.
|
If you do not specify a target, the default community strings apply to all devices in the network.
|
read_community
|
A password allowing read-only access to the target devices.
|
You must specify the read community string. Otherwise, the default value of public is used.
|
timeout
|
The length of time (seconds) the server waits for a response from the device before performing the first retry.
|
The default is 10 seconds. If you increase the timeout period, discovery could take significantly longer to complete. The minimum value is one and the maximum value is 60.
|
retries
|
Number of attempts the server makes to communicate with the device before declaring that the device has timed out.
|
The default is one retry. If you increase the number of retries, discovery takes significantly longer to complete. The default retry policy doubles the previous timeout value for retry.
|
write_community
|
The password that allows write access to the target devices.
|
You must specify the write community string. Otherwise, the default value of public is used.
|
Step 3 To modify an entry, make your changes directly in the large textbox.
Step 4 Click Save to apply your changes.
Related Topic
Community String Guidelines
Community String Guidelines
Use these guidelines when adding or modifying community strings:
•You can assign community strings to any of the following:
–Complete IP address; for example, 172.20.4.9
–Any wild cards (based on IP addresses); for example:
*.*.*.*
172.*.*.*
–Address ranges, which can include wild cards; for example:
27.20.[4-55].*
172.[21-30].[44-88].*
172.*.*.[121-255]
•You can add a combination of general and specific entries, but the WLSE reads the community strings from most specific to least specific.
•If you enter duplicate community strings for a device, the most specific community string is used.
•A # sign as the first character on a line indicates a comment.
•All printable characters, except for colons (:), are allowed in community strings.
•Spaces are not allowed in community strings.
Specify the HTTP Username and Password
HTTP usernames and passwords are required for downloading configuration files to access points. The password must be set on each access point, and you can enter as many usernames and passwords as necessary on the WLSE. For more information about setting passwords on access points, see Set Up Devices.
Note Your login determines whether you can use this option.
Procedure
Step 1 Select Administration > Discover > Device Credentials > HTTP User/Password.
Step 2 To add a username and password:
a. Enter the access point IP address or range of IP addresses that will use this username and password.
b. Enter the username.
c. Enter the password.
d. Click Save. The IP address and username are added to the Current Entries textbox.
Step 3 To modify an entry:
a. Select the entry from the Current Entries text box.
b. Modify fields as needed and click Save.
Step 4 To delete an entry, select it from the Current Entries text box and click Delete.
Related Topic
"Configuring Devices"
Managing Device Discovery
When you select Administration > Discover > DISCOVER, the following options appear:
•Discovery Options—Enable or disable automatic management of discovered devices and enable or disable reverse DNS lookup (See Enable Discovery Options).
•Filter Rules—Limit discovery by setting up IP address filters (See Set Up Discovery Filters).
•Schedule Discovery—Set up scheduled discoveries (see Schedule Discovery).
•Run Discovery Now—Run a one-time, immediate discovery (see Run Discovery Now)
You can also view details on the last 15 discoveries—See Viewing Inventory and Discovery Task History.
Related Topics
•Overview: Discovery
•Set Up Devices
Overview: Discovery
You can set up regularly scheduled discoveries and run one-time discoveries.
Before the WLSE can discover devices:
•You must configure discovery on the WLSE. See Schedule Discovery.
As an alternative to using Cisco Discovery Protocol (CDP) to run discovery, you can import devices from a file or from CiscoWorks2000. See Importing Devices.
•Devices must be properly configured for access by the WLSE. See Set Up Devices.
•Community strings must be entered on the WLSE. See Specify Community Strings).
Note Routers and switches are only discovered if they have properly configured access points attached to them.
Discovery proceeds according to the seed devices and CDP distance that you specify. The CDP distance determines the depth of the discovery. With a CDP distance of 1, only the immediate neighbors of the seed device are discovered. With a CDP distance of 2, devices A and B that are directly connected to the seed device are discovered, and the immediate neighbors of A and B are also discovered. You should set the CDP distance so that your entire wireless network is discovered.
After devices are discovered, you must move them to the managed state. Unmanaged devices do not appear in WLSE displays.
Related Topic
Importing Devices
Managing Devices
Set Up Devices
You must set up devices so the WLSE can discover and manage them. This section describes both required and optional setup tasks for:
•Set Up Access Points and Bridges
•Set Up Routers and Switches
•Set Up AAA Servers
Set Up Access Points and Bridges
You can set up access points and bridges in two ways:
•By using the WLSE's automatic configuration option for first-time device configuration (select Configuration > Auto Update). For more information, see Automating Configurations.
•By opening a web browser session on each device and perform the tasks in the following table. To use this method, you must first configure each access point or bridge for web browsing.
Table 6-4 Set Up Procedures for Access Points and Bridges
Tasks
|
Procedure
|
Notes
|
1. Enable Cisco Discovery Protocol (CDP).
|
1. In the Summary Status page, click Setup. The Cisco Services Setup page appears.
2. Under Services: Cisco Services, click Cisco Discovery Protocol. The CDP Setup page appears.
3. Select Enabled. Click Apply or OK.
|
CDP is required for the WLSE to discover devices on the network.
|
2. Enable SNMP.
(Optional) Set the location.
(Optional) Set the system name and system contact.
|
1. In the Summary Status page, click Setup. The Cisco Services Setup page appears.
2. Under Services, click SNMP. The SNMP Setup page appears.
3. Select Enabled.
4. Enter a System Name, System Location, and System Contact.
5. Click Apply or OK.
|
SNMP is required for the WLSE to discover and manage the device.
Setting the location enables proper grouping of devices into the system-defined Location group. For more information, see Managing Groups.
Setting the system name and system location displays this information when you display device details.
|
3. Set the community string by creating a user with all privileges.
(If you already entered an SNMP Admin Community name, the user created has Write, SNMP, Firmware, and Admin privileges, and the User Manager is enabled, you do not need to create another user.)
|
1. In the Summary Status page, click Setup. The Cisco Services Setup page appears.
2. Under Services, click Security. The Security Setup page appears.
3. Click User Information; then click Add New User. The User Management window appears.
4. To create an user with SNMP read/write privileges, enter a username and password and select the Write, SNMP, Firmware, and Admin capabilities.
5. Click Apply or OK.
|
The username of the user with write and SNMP privileges is used as the SNMP read/write community string.
The Firmware privilege is required for configuring devices from the WLSE.
|
4. Add an HTTP user with the ability to modify firmware, and enable the User Manager.
You can use the same user that you created in Task 3, if the user has firmware privileges.
|
1. In the Summary Status page, click Setup. The Cisco Services Setup page appears.
2. Click Security. The Security Setup page appears.
3. Click User Information; then click Add New User. The User Management window appears.
4. Enter a username and password and select Firmware; then click Apply.
5. Navigate back to the Security Setup page and click User Manager. The User Manager Setup window appears.
6. Select Enabled; then click Apply or OK.
|
This allows configuration uploads from the WLSE to the access point.
You must also enter HTTP users and passwords on the WLSE (see Specify the HTTP Username and Password).
|
5. Set up TFTP as the transfer protocol between the WLSE and access points.
|
1. In the Summary Status page, click Setup. The Cisco Services Setup page appears.
2. Under Services, click FTP. The FTP Setup page appears.
3. Use the pulldown menu to select TFTP as the file transfer protocol.
4. In the Default File Server text box, enter the IP address of the WLSE.
5. Click Apply or OK.
|
TFTP is used for transferring configuration changes to access points.
|
Set Up Routers and Switches
Note Only routers and switches that have properly configured access points or bridges attached to them will be discovered.
On each router and switch, configure the following:
Table 6-5 Set Up Procedures for Routers and Switches
Task
|
Procedure
|
Notes
|
1. Enable CDP and verify that access points and bridges are visible from the router or switch.
|
1. Enter enable mode.
2. Verify that CDP is running on the switch or router:
On IOS-based devices, use the show cdp run command.
On Hybrid OS-based Catalyst switches, use the show cdp command
3. If CDP is not running, use the set cdp enable command to enable CDP.
4. To verify that access points or bridges are visible in the device's CDP table, use the show cdp neighbors command.
|
CDP is required for the WLSE to discover the device.
|
2. Enable SNMP and set up community strings.
|
On IOS-based devices, enter configuration mode and use the snmp community community_string ro command.
On Hybrid OS-based Catalyst devices, enter enable mode and use the set snmp community read-only community_string command.
|
SNMP is required for the WLSE to discover and manage the device.
|
3. (Optional) Set the system name, contact, and location variables.
|
On IOS-based devices, enter configuration mode and use the following commands.
•To set the system name, use the hostname name command.
•To set the system contact, use the snmp contact contact command.
•To set the location, use the snmp location location command.
On Hybrid OS-based Catalyst switches, enter enable mode and use the following commands:
•To set the system name, use the set system name name command.
•To set the system contact, use the set system contact contact command.
•To set the location, use the set system location location command.
|
These variables make the device more manageable. The location variable enables proper grouping of devices into the system-defined Location group. For more information about groups, see Managing Groups.
The system name, system contact, and location will appear in the device detail displays.
|
Set Up AAA Servers
The WLSE can monitor the performance of AAA (Authentication, Authorization, and Accounting) services provided by CiscoSecure ACS Server. To enable monitoring, you must:
•Configure CiscoSecure ACS server to recognize the WLSE as a client. Follow the procedure in this section on each server.
•Configure the WLSE to add information about the LEAP, RADIUS, and EAP-MD5 servers. For more information, see Adding, Modifying and Deleting AAA Servers.
Procedure
Step 1 Log into CiscoSecure ACS Server on a PC that will provide authentication services to the wireless network.
Note You will need the IP address or name of the PC when configuring the WLSE.
Step 2 Click User Setup on the left side of the initial page. The User Setup page appears.
Step 3 Enter a username for the user the WLSE will use for synthetic transactions and click Add/Edit.
Step 4 Enter a password in the first set of Password and Confirm Password textboxes. Click Submit.
Note You will need this name and password when configuring the WLSE.
Step 5 Click Network Configuration on the left side of the page. The Network Configuration screen appears.
Step 6 Click Add Entry. In the Add AAA Client area, enter the WLSE information in the following text boxes:
•Client Hostname—enter the WLSE hostname (or IP address)
•Client IP—enter the WLSE IP address
•Key—enter a secret key
Note You will need this key when configuring the WLSE.
Step 7 Select RADIUS (Cisco Aironet) from the Authenticate Using list.
Step 8 Click Submit or Submit+Restart. A restart is required for the changes to take effect.
Enable Discovery Options
You can modify the discovery process by specifying that all discovered devices be automatically managed and enabling reverse DNS lookup so that device names, instead of IP addresses, appear in WLSE displays.
Note Your login determines whether you can use this option.
Procedure
Step 1 Select Administration > Discover > DISCOVER > Discovery Options. The Discovery Options window appears.
Step 2 To enable automatic management for all discovered devices, select the Auto-Manage Devices checkbox.
All discovered devices will be automatically placed in the Managed folder.
Note If you are using the automatic configuration feature (Configuration > Auto Update), new access points and bridges added to the network will be automatically configured if Auto-Manage is enabled. For more information, see Automating Configurations.
Step 3 If DNS is configured on devices, you can enable reverse DNS lookup by selecting the Use reverse DNS lookup checkbox. Use of this feature affects device name display on the WLSE as follows:
Reverse DNS lookup enabled?
|
Affect on Display
|
Yes
|
If the lookup succeeds, the device name is displayed.
|
If the lookup fails, the device IP address is displayed.
|
No
|
If the device's SNMP sysName is set, the sysName is displayed.
|
If the sysName is not set, the device IP address is displayed.
|
Step 4 Click Save.
Related Topics
Manage Devices
Set Up Discovery Filters
You can limit discovery to certain devices by setting up filter rules to include or exclude devices. Filter rules consist of device IP addresses with optional wildcards and ranges.
Note Your login determines whether you can use this option.
Procedure
Step 1 Select Administration > Discover > DISCOVER > Filter Rules. The Filter Rules window opens.
Step 2 Add IP addresses to the Include Rules or Exclude Rules text boxes, one entry per line. Use standard IP address format (four octets separated by periods) in which any octet can be:
•A value between 0 and 255.
•An asterisk (*) wildcard, denoting any number from 0 to 255; for example, 10.20.*.*.
•A range in which the first number is less than the second; for example, 10.20.30[50-60].
Rules cause discovery to be limited as described in the following table.
Note Exclude rules take precedence over include rules.
Table 6-6 Effects of Include and Exclude Rules in Discovery Filters
Include Rules Defined?
|
Exclude Rules Defined?
|
Result
|
No
|
No
|
All devices are discovered.
|
No
|
Yes
|
All devices are discovered, but those that match the Exclude Rules are discarded.
|
Yes
|
No
|
Only devices that match the Include Rules are discovered.
|
Yes
|
Yes
|
Only devices that match the include rules are discovered. Devices that match the exclude rules are discarded.
|
For example, assume the IP addresses of the devices in a network are from 10.10.10.1 through 10.10.10.200:
•The include rule is 10.10.10.[40-80]
•The exclude rule is 10.10.10.[60-70]
All of the devices with the IP addresses 10.10.10.[40-80] are discovered, but those with IP addresses 10.10.10.[60-70] are discarded. Therefore, the devices discovered and retained have IP addresses 10.10.10.[40-59] and 10.10.10.[71-80].
Step 3 Click Save to save your Rules.
The Rules will take effect for all subsequent discoveries.
Schedule Discovery
This option allows you to schedule discovery. You can specify that scheduled discoveries be repeated at specified intervals. Before discovery can proceed, you must specify at least one seed device. Any supported device can function as a seed. Neighbors of seed devices are discovered by examining the contents of CDP tables.
You may want to specify multiple seed devices to:
•Shorten the discovery time.
•Discover "disconnected" networks; that is, discover devices across links on which CDP is disabled or discover devices outside the firewall.
Note Your login determines whether you can use this option.
Procedure
Step 1 Select Administration > Discover > DISCOVER > Schedule Discovery. The Discovery - Configuring Seeds dialog box appears.
Step 2 To add seed devices, enter their comma-separated IP addresses or device names in the Seed Values text box and click >>. Seed devices that you add in this dialog box will be retained so that you can use them for subsequent scheduled and immediate discoveries.
Device names must resolve to your local DNS in order to translate device names to IP addresses during discovery. The requirements for entering device names are:
•Blank spaces are not allowed.
•The first character in a name must be alphanumeric
•The only valid characters are the alphanumeric characters, the minus sign (-), and the period (.).
•The last character cannot be a minus or a period.
Tip You can add multiple seed devices at one time by copying and pasting seed device names or IP address from a file.
Note Before you can proceed to the next screen, Modify Discovery Schedule, you must have at least one seed device in the Seed Values list.
Step 3 To delete a seed device, select the IP address from the Seed Values list and click Delete.
Step 4 Select the CDP distance from the list. Set CDP distance appropriately to discover the entire wireless network; a CDP distance of 1 only discovers the immediate neighbors of the seed devices.
Note Routers and switches that do not have access points attached to them are used when computing CDP distance. However, such devices will not appear in the discovered devices list.
Step 5 If you have not entered community strings that allow the WLSE to access all devices to be discovered, click Enter community strings before running discovery. The SNMP Community dialog box appears. For more information about entering community strings, see Specifying Device Credentials.
Step 6 To schedule discovery, click Modify Schedule. The Modify Discovery Schedule dialog box appears.
•Select the State Date and Start Time from the pulldown lists.
•To repeat discovery at specified intervals, click Enable. Then enter a number in the Every textbox and select the interval from the list.
Step 7 Click Next. The CDP Discovery - Summary dialog box appears.
Step 8 Click Finish to submit your settings or Back to make changes in your settings.
Related Topic
Specifying Device Credentials
Run Discovery Now
This option allows you to run an immediate, one-time discovery.
Note Your login determines whether you can use this option.
Procedure
Step 1 Select Administration > Discover > DISCOVER > Run Discovery Now. The Run Discovery Now - Seeds dialog box appears.
Step 2 If necessary, add seed devices:
Note Any seed devices added here are used for this one-time discovery only.
a. Enter the seed device's IP address or device name in the Add Seed Value text box and click >>.
Device names must resolve to your local DNS in order to translate device names to IP addresses during discovery. The requirements for entering device names are:
–Blank spaces are not allowed.
–The first character in a name must be alphanumeric.
–The only valid characters are the alphanumeric characters, the minus sign (-), and the period (.).
–The last character cannot be a minus or a period.
b. Set the CDP by selecting a number from the list.
Step 3 If you have not added community strings that allow the WLSE to access all devices to be discovered, click Enter community strings before running discovery. The SNMP Community dialog appears. For more information about entering community strings, see Specify Community Strings.
Step 4 Click Run Now. The Discovery - Summary dialog box appears.
•Click Back if you want to make changes before running the discovery.
•Click Finish to run the discovery. The discovery will begin within 2 minutes.
Step 5 The Tasks History window appears. You can expand the Discovery folder to see the results of the discovery:
•Immediate discoveries are named CDPDiscovery_Run_Now_number. The number increments each time you run an immediate discovery.
•Click the discovery name. The Run Log appears, showing the start and end times of the discovery and information about the devices that were discovered.
Related Topics
•Specifying Device Credentials
•Viewing Inventory and Discovery Task History
Running Inventories
The WLSE automatically runs scheduled inventories (see About Scheduled Inventories), and you can run immediate inventories of all devices or of selected devices.
When you select Administration > Discover > Inventory, the following options for running immediate inventories appear:
•Run Inventory Now—Use this option to collect complete inventory data from selected devices (see Immediate Inventory of Selected Devices).
•Inventory All Devices—Use this option to collect inventory data from all devices—see Immediate Inventory of All Devices).
You can view details on the last 15 inventories—See Viewing Inventory and Discovery Task History.
About Scheduled Inventories
The WLSE runs 3 types of inventories on a regularly scheduled basis:
•Basic inventories that collect all the information required by the WLSE to populate displays, such as reports, and to place devices in system-defined groups. This inventory runs hourly by default.
In the inventory history listing, these inventories appear under the name Inventory.
•Client inventories that only collect information about associations of clients to access points. This inventory runs every 5 minutes by default.
In the inventory history listing, these inventories appear under the name ClientInventory.
•Performance inventories that only collect the performance attributes used in trend reports for access points, bridges, and AAA servers. This inventory runs every 15 minutes.
In the inventory history listing, these inventories appear under the name PerformanceInventory.
To change the scheduled inventory intervals, you can reset the inventory polling parameters. See Managing System Parameters.
Immediate Inventory of Selected Devices
Use this option to run an immediate inventory of selected devices.
Note Your login determines whether you can use this option.
Procedure
Step 1 Select Administration > Discover > Inventory > Run Inventory Now. The device selector shows all managed devices in group folders in the middle pane, and the Run Inventory Collection window appears.
Step 2 To search for devices:
a. From the list in the search area located in the middle pane, select the method for searching: by device name or IP address.
b. Enter the IP address or name. You can use asterisks (*) as wildcards. An asterisk denotes any number of characters in a name or an entire octet in an IP address; for example, *AP or 172.*.*.*.
c. Click Search. The matching devices appear in the Search Results folder in the device selector.
Step 3 To select devices for inventory:
a. Expand the folder that contains the devices you want to include.
b. Click the device group folder. All of the devices in the group are added to the list in the Run Inventory Collection window.
Note Each immediate inventory job for selected devices contains devices from only one group.
c. From the list of devices in the group, select the devices you want to inventory.
Step 4 Click Run Inventory for Selected Devices. The inventory job starts immediately. Managed devices are polled and information is collected. WLSE displays are updated accordingly.
Step 5 The Tasks History window appears. You can expand the Inventory folder to see the results of the inventory collection:
•Inventories of selected devices are named InventoryRunNow_number. The number increments each time you run an inventory.
•Click the inventory name. The Run Log appears, showing the start and end times of the inventory and the type of data that was collected for the devices you selected.
Immediate Inventory of All Devices
Use this option to run an immediate inventory of all devices. This inventory is the same as the scheduled basic inventory. Inventories that collect data for all devices are named Inventory, whether they are scheduled inventories or immediate inventories run by a user.
Note Your login determines whether you can use this option
Procedure
Step 1 Select Administration > Discover > Inventory > Inventory All Devices.
Step 2 Click Inventory All Devices. The inventory job starts immediately. Managed devices are polled and information is collected. WLSE displays are updated accordingly.
If an inventory is currently running, a message appears. You should wait for the running inventory to complete before starting the immediate inventory.
Step 3 The Tasks History window appears. You can expand the Inventory folder to see the results of the inventory collection.
•Inventories of all devices are named Inventory.
•Click the inventory name. The Run Log appears, showing the start and end times of the inventory and type of data that was collected.
Viewing Inventory and Discovery Task History
You can view the history of inventories and discoveries by using the Task History option. Details on the last 15 inventories and discoveries are accessible through this option.
Note Your login determines whether you can use this option.
Procedure
Step 1 Select Administration > Discover > Tasks History. The Tasks selector appears.
Step 2 To view a list of jobs, expand the Discoveries or Inventories folder. A list of the last 15 jobs appears with the latest job listed first and earliest listed last.
The names of the inventory and discovery jobs indicate the type of inventory or discovery as follows:
Table 6-7 Discovery Job Names
Name
|
Type of Job
|
CDPDiscovery
|
Scheduled discoveries.
|
CDPDiscovery_Run_Now_number
|
Immediate, one-time discoveries.
|
CDPDiscovery_Import_Devices
|
Devices were imported from a file or from a CiscoWorks2000 server.
|
Table 6-8 Inventory Job Names
Name
|
Type of Job
|
Inventory
|
Scheduled and immediate inventories of all devices.
|
ClientInventory
|
Scheduled inventories of client associations to access points.
|
PerformanceInventory
|
Scheduled inventories of performance attributes used in trend reports.
|
InventoryRunNow_number
|
Immediate inventories of selected devices, run by users.
|
Step 3 To view details about a job, select the job. The Run Log appears, showing the start and end times of the job and type of data that was collected.
Related Topics
•Running Inventories
•Immediate Inventory of Selected Devices
•Immediate Inventory of All Devices
Importing Devices
Instead of running discovery on the WLSE, you can import devices:
•From a file (see Import Devices from a File).
•From CiscoWorks2000 Resource Manager Essentials (see Import Devices from CiscoWorks2000).
A one-time discovery job starts immediately after you import devices. All WLSE-supported devices in the file are used as seed devices with a CDP of 1. These devices are not added to the list of available seed devices in the Discovery - Configuring Seeds dialog box, but they do appear in the Discovery Run Log. See Schedule Discovery and Viewing Inventory and Discovery Task History.
Devices not supported by the WLSE are ignored.
You can choose to discover some devices and import others.
The following information is imported:
•IP addresses are accepted, and hostnames are resolved to obtain the IP address. Hostnames that cannot be resolved are ignored.
•Read-only and read/write community strings are appended to the end of the Bulk SNMP Settings table (Administration > Discover > Device Credentials). See Specifying Device Credentials.
Note Imported credentials are not matched with existing entries that contain wildcards or ranges.
Import Devices from a File
You can import devices from a file that contains device information in the CSV format. You can create a CSV file by exporting devices from CiscoWorks2000 or by creating the file with a text editor. You can view a sample CSV file in the dialog box for importing files.
Note Your login determines whether you can use this option.
Procedure
Step 1 Select Administration > Discover > Import Devices > From File. The Import Devices from File dialog box appears.
To see a sample file, click See Sample CSV File.
Step 2 You can enter a pathname for the file in the Choose File dialog box or click Browse to find the file in the client directory structure.
Step 3 Click Import. Devices are imported and a one-time discovery begins within 2 minutes.
Step 4 To verify the discovery, see Viewing Inventory and Discovery Task History.
Related Topics
•Import Devices from CiscoWorks2000
•Schedule Discovery
•Specifying Device Credentials
•Viewing Inventory and Discovery Task History
Import Devices from CiscoWorks2000
You can import devices directly from CiscoWorks2000 by connecting to a CiscoWorks2000 server.
The time required to import devices depends on the response from the CiscoWorks2000 server and the number of devices imported. The following procedure explains how to check the status of the operation.
Note Your login determines whether you can use this option.
Procedure
Step 1 Select Administration > Discover > Import Devices > From CiscoWorks2000.
Step 2 Enter the following information. All fields are required; if any are left blank, the display will clear.
•The CiscoWorks2000 server IP address.
•The port number at which the CiscoWorks2000 server listens for HTTP requests. You may need to contact the administrator of the CiscoWorks2000 server to obtain this information.
•The username and password of any user who has the authority to export and import device credentials on the CiscoWorks2000 server.
Click Import. After devices are imported, a one-time discovery begins.
Step 3 To see the Import Status log, click Status. The CiscoWorks2000 Import Status window appears. To refresh the status display, click Refresh.
•If the Last Status button is displayed in place of the Status button, you can review the results of a previous import.
•If the import fails because you entered the wrong data in the Import dialog box, one of the following error messages is included in the Import Status log:
–The following message means that either the host or the port specified in the WLSE import dialog was wrong:
Error: Could not connect to CiscoWorks2000 server:ip_address on port:port_number.
–The following message means that either the user or password specified in the WLSE import dialog was wrong:
Error: Connected to CiscoWorks2000 server:ip_address on port:port_number successfully, but server returned error after connection.
•If the import succeeds, you can view detailed information in the Discovery Run Log. See Viewing Inventory and Discovery Task History.
Related Topics
</
