Table of Contents

Overview of Deploying Devices into the Network

Deploying a Region Object
Deploying a Site Object

Overview of Discovery

About SNMP Tables
Discovering Objects Automatically

Overview of Deploying Device Objects Manually

Deploying Device Objects Manually

Overview of Exporting Inventory Data

Scheduling Inventory Data Export
Updating Inventory Data
Exporting Inventory Data Immediately
Exporting a File

Example of an Inventory Export File
Format of Exported Data

Deploying, Discovering, and Exporting Inventory Data with Cisco UGM

With Cisco UGM, you can query the network for managed devices. Each device is then queried for subcomponents. When you remove or insert cards that support Online Insertion/Removal (OIR), an OIR trap is sent from the device which then causes Cisco UGM to automatically rediscover device subcomponents.

• Overview of Deploying Devices into the Network
  
  
• Deploying a Region Object
  
  
• Deploying a Site Object
  
  
• Overview of Discovery
  
  
• About SNMP Tables
  
  
• Discovering Objects Automatically
  
  
• Overview of Deploying Device Objects Manually
  
  
• Deploying Device Objects Manually
  
  
• Overview of Exporting Inventory Data
  
  
• Scheduling Inventory Data Export
  
  
• Updating Inventory Data
  
  
• Exporting a File
  
  

Overview of Deploying Devices into the Network

In order to set up Cisco UGM to manage network devices, you must first deploy the devices into the network. An object for each device is created automatically when the device is deployed by Cisco UGM. This created object represents a real object in the network and is stored under the Network, Physical, and device-specific (AS5350, AS5400, AS5800, AS5850) views. You can access the device object through the Map Viewer.

Deploying a Region Object

Step 1   Right-click the physical node and select Deployment > Deploy generic objects.

Step 2   In the Deployment Wizard dialog box, select the Region option and click Next.

Step 3   Enter responses to the Deployment Selector Screen and click Next.

Step 4   In the Object Details screen, specify a site name.

Step 5   In the Deployment Summary screen, click Finish and wait until the deployment process is completed.

For details on creating site objects, refer to the Cisco Element Management Framework User Guide.

Deploying a Site Object

Step 1   Right-click the physical node, or, if you created a region object and want your site object to be located under it, right-click that region and select Deployment > Deploy generic objects.

Step 2   In the Deployment Wizard dialog box, select the Site option and click Next.

Step 3   Enter responses to the Deployment Selector Screen and click Next.

Step 4   In the Object Details screen, specify a site name.

Step 5   In the Deployment Summary screen, click Finish and wait until the deployment process is completed.

For details on creating site objects, refer to the Cisco Element Management Framework User Guide.

Overview of Discovery

You can start this application by using one of these methods:

• Click the Discovery icon in the Cisco EMF Launchpad.
  
  
• Right-click a selected container object like Site or Region, and select the Deployment > Auto Discovery option from the menu.
  
  

Device objects are discovered first, followed by the subcomponent objects. When the subcomponent discovery is in progress, the device object is in the discovering state.

For details on icons, refer to the Cisco Element Management Framework User Guide.

The device and subcomponent objects are discovered and located in the region or site from where you initiate discovery.

---

Caution   Do not attempt to discover all network objects in bulk mode. Discover objects by specifying a range of (approximately 30) IP addresses.

---

If objects are not discovered during the first discovery, the next discovery finds these undiscovered objects. The database retains information about previously discovered objects.

For example, if you specified the IP address range (of devices to be discovered) to be from 171.22.41.65 to 171.22.41.95, and Cisco UGM did not discover devices in the 171.22.41.83 to 88 range, you can initiate discovery to find these devices.

After the initial discovery of devices, discovery is triggered again when:

• Cisco UGM receives an Online Insertion and Deletion (OIR) trap (from a device that supports OIR).
  
  
• You start discovery by first decommissioning and then commissioning the device as described in the "Overview of the Commission/Decommission Function for a Chassis" section.
  
  

If the underlying device subcomponents have changed, corresponding changes are made during rediscovery leading to deletion or creation of Cisco EMF objects (representing cards and ports).

About SNMP Tables

Cisco UGM discovers device subcomponents by getting the following SNMP tables:

• ENTITY-MIB.entPhysicalTable
  
  
• OLD-CISCO-CHASSIS-MIB.cardTable
  
  
• IF-MIB.ifTable
  
  
• RFC1407-MIB.dsx3ConfigTable
  
  
• RFC1406-MIB.dsx1ConfigTable
  
  
• CISCO-POP-MGMT-MIB.cpmDS0UsageTable
  
  
• CISCO-MODEM-MGMET-MIB.cmLineStatusTable
  
  

Discovering Objects Automatically

Caution   Do not attempt to discover all network objects in bulk mode. Discover objects by specifying a range of (approximately 30) IP addresses.

Step 1   From the Map Viewer, select the object (region, site, or device) that you want to discover.

Step 2   To open the Discover Network Devices window, right-click the device and select Discovery > Auto discovery.

Step 3   Select the drop down list next to Discovery Method and select SNMP or IP and SNMP.

Step 4   Set the Hop Count to the number of subsequent levels of subnets that you want to discover.

Note   The maximum number of subnets that you can discover is 16.

Step 5   For IP devices in the Ping Retries data entry box, specify the number of times the system should try Internet Control Message Protocol (ICMP) ping to identify whether an active machine is connected to a specified address.

The maximum number of ping retries is 10.

Step 6   Enter a community name in the New Community data entry box; then, click Add.

Step 7   In the data entry box next to SNMP Retries, enter the number of times the system should try to get the RFC1213-MIB.system attribute from a device without receiving a reply before the device is discarded as not being an SNMP device.

The maximum number is 10.

Step 8   In the Physical Location panel, click Use Physical Path. If required, select Get Path for the correct physical view.

Step 9   In the data entry box next to SNMP Timeout, enter the required time. The default is set to 10 seconds.

Step 10   (Optional) You can restrict the IP address range that the system interrogates by double-clicking Device Interface.

The Discovery Interface window appears.

Step 11   (Optional) Specify a range of IP addresses (or even a single address) by entering a start address and a stop address. Only IP addresses within the specified address range are discovered.

Step 12   To start the discovery process, select the device from the Device Interfaces list.

Step 13   Click Start.

Note   You can stop creating and deploying device objects by clicking Stop.

When the Network Access Server (NAS) object is discovered, the process is immediately followed by the automatic discovery of NAS components, such as cards and ports. This subcomponent discovery leads to the creation (under the NAS object) of the hierarchy of subcomponent objects.

Overview of Deploying Device Objects Manually

You can deploy Cisco UGM device objects manually by using templates. In addition, you can discover device subcomponents automatically by getting a number of SNMP tables from the NAS. (There is no manual deployment for device subcomponents.)

You can use either of the following templates for each type of managed device in your network:

• Template for AS5xxx as Decommissioned—Use this template to deploy a device only; not to discover any of its subcomponents.
  
  

---

Tip This template creates an object in a decommissioned state; Cisco UGM does not process its traps, and performance data is not collected.

---

• Template for AS5xxx with Sub-Chassis Discovery—Use this template to deploy and commission the device and automatically initiate subcomponent discovery.
  
  

In the manual deployment mode, you can assign NAS device object names, whereas in auto-discovery mode, Cisco EMF assigns device object names based on the IP address of the device.

The device objects are discovered and located in the region or site from where you manually initiated the deployment.

Deploying Device Objects Manually

Caution   When you manually deploy device objects: Check that the IP address or device name that you specify is not already used in the network of Cisco UGM-managed devices. If a conflict is detected, the manual deployment fails. Verify that the type of NAS device matches the template that you specify. If you use an AS5xxx template to deploy an AS5yyy device type, Cisco UGM detects a conflict, and creates the device object in the errored state with no subcomponents. Delete the object and deploy a device object that matches the template.

Step 1   Click a site or region in the left pane until you access the device to be deployed.

Step 2   Right click the device and select: Deployment > Deploy Access Servers> Deployment Wizard—Templates. Select the template that you want.

Step 3   Enter the number of objects. If you enter a number greater than 1, repeat Step 4 for each object.

Step 4   Enter the IP address of the device that you want to deploy and click Forward.

See the "Overview of Deploying Device Objects Manually" section.

Overview of Exporting Inventory Data

With Cisco UGM, you can export your system inventory data into a flat text file. By using report-generating software, you can format this data into a report. Exporting files allows you to export data from the database to a UNIX directory; then, you can send the file to an external system through File Transfer Protocol (FTP).

• Schedule only one file (at a time) for inventory data export. If multiple files are scheduled for export at different intervals (hourly, daily, weekly, or monthly) only the last scheduled export saved is active. Any previously specified inventory data exports are ignored.
  
  
• Exporting inventory files enables you to get a snapshot of the managed devices' physical view in a flat file. Data output consists of device names and associated attributes.
  
  
• Schedule inventory export to occur automatically on an hourly, daily, weekly, or monthly basis. Or you can trigger it immediately.
  
  
• Specify the aging time (number of days) and action (delete, move, compress) for the inventory output files.
  
  
• Exported inventory objects consist of site, region, device, and subcomponent objects.
  
  
• Exported attributes include IP address, shelf, slot, and port numbers for subcomponent objects.
  
  

Scheduling Inventory Data Export

By default the inventory data export feature is disabled. Follow these steps to enable this feature:

Step 1   In the Map Viewer, choose Physical > ASEMSConfig > File Export > File Export Properties.

Step 2   In the File Export Properties dialog box, click the Inventory tab.

Step 3   Select Scheduled Export.

Step 4   Enter the location where the exported file will be stored and the delimiter that you want to use.

Step 5   Select the file aging action, duration, and directory where the aged file will be stored.

Step 6   Select the time interval when you want the inventory text file to be created. The export takes place at the beginning of the hour. For example, if the interval is set to hourly, the export takes place at 1:00, 2:00... every day.

Step 7   Click Save.

Updating Inventory Data

Inventory data is retrieved during the discovery of network objects. You can update the inventory data by forcing rediscovery of any number of network objects.

Step 1   In the Map Viewer, right-click the device, region, or site where you want to initiate rediscovery.

Step 2   For a site or region, select ASMainEM > Chassis Commissioning.

Or

For a single device object, select Chassis > Chassis Commissioning.

Step 3   From the object list, select the device or multiple devices that you want to rediscover.

Step 4   Click Decommission and wait for the object to transition to the Decommissioned state.

Step 5   Click Commission to discover network objects. Wait until the objects transition to the Normal state.

Inventory data has been updated for the selected objects. To export the inventory data, complete the "Exporting Inventory Data Immediately" section.

Exporting Inventory Data Immediately

Step 1   In the Map Viewer choose Physical > ASEMSConfig > File Export > File Export Properties.

Step 2   In the File Export Properties dialog box, click the Inventory tab.

Step 3   Enter the location where the exported file will be stored, and the delimiter that you want to use.

Step 4   Click Save.

Step 5   Click Export Now.

Exporting a File

Step 1   In the Physical view, select the object for which you want to export inventory data. Right click the object and choose ASEMSConfig > File Export > Open File Export Properties > Inventory.

Step 2   In the Export Type field, enter:

• Scheduled—Enables scheduled inventory export.
  
  
• None—Disables scheduled inventory export. Select this option if you plan to immediately export data (see Step 12 in this procedure).
  
  

If you followed this step, skip Step 8 through Step 11.

Step 3   Enter a storage path for the inventory data file.

Step 4   Enter a delimiter to use between fields of data in the report.

The default value of the delimiter is the "|" string.

Step 5   Select an action to be performed when file aging occurs:

• none—Disables aging; File Age and Aging Directory fields are ignored.
  
  
• delete—Deletes the aged file from the disk.
  
  
• move—Moves the aged file into the aging directory.
  
  
• moveTarCompress—Compresses the aged file; then, adds it to the FileExport.tar file which, if it does not already exist, is created in the Aging Directory.
  
  

Step 6   Enter the maximum size (in KBytes) of a file before the selected aging action is performed. Export then continues in the newly created file.

Step 7   Enter a location where the file is moved to (or moveTarCompressed to) when aging occurs.

• If you enter a non-existent directory path, the directory path is automatically created.
  
  
• This location field does not apply to the delete aging action.
  
  
• The directory string that you enter must end with a trailing / (forward slash).
  
  
• If the Action field is set to moveTarCompress, a tar file named FileExport.tar is created in the Aging Directory to contain aged files.
  
  

Step 8   Select the frequency of data export:

Step 11   Select the scheduled day of the month for the export:

Step 12   Click Export Now.

See the "Format of Exported Data" section.

Example of an Inventory Export File

See the "Format of Exported Data" section for a description of fields in this file.

Format of Exported Data

Inventory export data is formatted as follows:

<Device pathName>|<Device Type>|<attribute1>|<attribute2>....

where attributes (if any) are specific to the device or subcomponent.

Note   If a device or subcomponent is not listed in this table, no attribute information is generated for it; just the pathname and device type appear. Any unrecognized devices appear as "Unknown" for the device type.

Posted: Sat Sep 28 16:55:25 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.