|
|
This chapter contains the following sections. Complete the tasks in this order:
Overview of Configuring Managed Devices .
Selecting Access Parameters (General Tab).
(Optional) Selecting Split-Mode Parameters for the Cisco AS5850 Device (Redundancy Tab)
Selecting Card Parameters (Slots Tab).
(Optional) Selecting Card Parameters for the Cisco AS5850 Device (Slots 0-5 Tab; Slots 8-13 Tab)
Selecting Interface Parameters (Interface Tab).
Entering SNMP Information for a Trap (SNMP Tab).
Selecting Cisco IOS Core Dump, Logging, and Time Parameters (Management Tab).
Entering Modem and SPE Parameters (SPE and Modem Tabs).
Entering Network Communication Parameters (Other Tab).
Building the Configuration File.
Many users can access Cisco UGM—like all Element Management Systems—on the Cisco EMF platform. You must take precautions to avoid simultaneously accessing and modifying the same network object or any of its components. Establish access schedules for all your users.
Cisco UGM performs all Cisco IOS operations through the Ethernet interface used to discover the device.
 |
Tip Before testing Cisco IOS commands on your Cisco UGM system, save the original configuration file from the device. |
Device configuration files are stored in the corresponding ConfigurationFiles folder under each device. Configuration files used by Cisco UGM are:
 |
Note Redundancy and split mode functionality for the Cisco AS5800 and AS5850
devices are not configured by Cisco UGM. You can configure these features
by using Cisco IOS configlets. For information on configuring this functionality, check the Cisco IOS documents. |
This table indicates if a state change results from configuration actions available for Cisco UGM-managed devices.
Table 2-1 State Changes Associated with Configuration Actions
| Configuration Action | State Change |
|---|---|
| Generate configuration file from a template | |
| Get Startup Configuration | |
| Associate a configuration file with a device | |
| Associate a configlet with a device | |
| Send Configuration to Startup | |
| Send Configlet to Running | |
| Copy Running to Startup |
|
Note You cannot schedule file operations, and they do not change the state of the managed device. |
Changes that you make in the Device Authentication Information dialog box are applied only to the selected device object.
Step 2 If you opened this dialog box from a container, select a device object.
Step 3 Enter the Login User Name as configured on the device.
Step 4 Enter and verify a Login Password.
|
Note If the device has vty line password configured, enter the vty line password for the Login Password. |
Step 5 Enter and verify an Enable password.
Step 6 Enter the Operation Timeout value in seconds. The default value is 10 seconds.
You can change this value located at:
Step 7 Enter the Prompt Timeout value in seconds. The default value is 10 seconds.
You can change this value located at:
|
Note Enter values in all the fields in this dialog. If you do not enter these values, the
following operations will fail: Show CLI Configure Administrative State All actions on the IOS Operations dialog. |
Step 8 Click Save.
Step 2 Under Options, select an option for Reload After Config Download.
|
Note Even though you can perform the Reload operation on multiple
devices, do not reload more than three devices at a time. Since Reload is a scheduled operation, you can schedule up to three devices to be reloaded at time A then, schedule the next group (up to three devices) at time A+30 minutes, and follow the same sequence with the remaining devices. |
Step 3 Click Save.
Cisco UGM does not allow you to define your own configuration file template. You must use the templates provided.
|
Note When building a configuration file from template, do not enter values for the user name, user password, and enable password. These values are automatically retrieved from the Device Authentication Information dialog box. |
To build a configuration file from a template for Cisco AS5300, AS5350, AS5400, and AS5800 devices, complete the following procedures in this order:
1. Selecting Access Parameters (General Tab)
2. (Optional) Selecting Split-Mode Parameters for the Cisco AS5850 Device (Redundancy Tab)
3. (Optional) Selecting Card Parameters for the Cisco AS5850 Device (Slots 0-5 Tab; Slots 8-13 Tab)
4. Entering SNMP Information for a Trap (SNMP Tab)
5. Selecting Cisco IOS Core Dump, Logging, and Time Parameters (Management Tab)
6. Entering Modem and SPE Parameters (SPE and Modem Tabs)
7. Entering Network Communication Parameters (Other Tab)
8. Building the Configuration File
To build a configuration file from a template for a Cisco AS5850 device, complete the following procedures in this order:
1. Selecting Access Parameters (General Tab)
2. (Optional) Selecting Split-Mode Parameters for the Cisco AS5850 Device (Redundancy Tab)
3. (Optional) Selecting Card Parameters for the Cisco AS5850 Device (Slots 0-5 Tab; Slots 8-13 Tab)
4. (Optional) Selecting Card Parameters for the Cisco AS5850 Device (Slots 0-5 Tab; Slots 8-13 Tab)
5. Entering SNMP Information for a Trap (SNMP Tab)
6. Selecting Cisco IOS Core Dump, Logging, and Time Parameters (Management Tab)
7. Entering Modem and SPE Parameters (SPE and Modem Tabs)
8. Entering Network Communication Parameters (Other Tab)
9. Building the Configuration File
To use an existing configuration file, see the "Task 3: Option 2: Using an Existing Configuration File" section. To import a configuration file, see the "Task 3: Option 3: Importing a Configuration File" section.
|
Tip If you are building configuration files for several managed devices, first select each individual device and specify unique parameters, such as a hostname and an IP address. Then, select all the devices and specify common configuration parameters for them. |
Step 2 Select Configure Device > Build Config File from Default AS5xxx Template.
Step 3 Click the General tab.
Step 4 Enter the host name of the device.
Step 5 Select the authentication method for users, accounting, administration, the network, and Point-to-Point Protocol (PPP) users if necessary.
Step 6 Enter the authentication key to use with Radius or Terminal Access Controller Access Control System (TACACS) servers if necessary.
Step 7 Enter the list of Radius or TACACS servers to use for authentication.
|
Note Cisco UGM does not check these parameters for validity. Your entries are inserted into the configuration file. |
Step 8 Enter local user names and passwords for additional users.
|
Note Do not enter user names and user passwords entered previously in the Device Authentication Information dialog box. Values from that dialog box are automatically retrieved when building the configuration file. |
Step 9 Click Save.
Step 2 Select Configure Device > Build Config File from Default AS5850 Template.
Step 3 Click the Redundancy tab.
Step 4 Select a Redundancy Mode for the device:
|
Note Select the same split mode (Classic-split or Handover-split) for both devices in a split-mode configuration. |
Step 5 Select a Router Shelf Controller (RSC) for the device:
Step 6 Repeat this procedure for the next Cisco AS5850 managed device.
Step 7 Click Save (under the General tab).
Step 2 Select Configure Device > Build Config File from Default AS5xxx Template.
Step 3 Click the Slots tab.
Step 4 Select the type of card installed in each slot.
Step 5 (Optional) Select the framing type used by the controller in this slot.
This field is applicable only if a trunk card occupies the slot.
Step 6 (Optional) Select the controller line code for this slot.
This field is applicable only if a trunk card occupies the slot.
Step 7 (Optional) Select the type of signal used when a channel type is channelized.
This field is applicable only if a trunk card occupies the slot and is configured to be Primary Rate Interface (PRI).
Step 8 Select an ISDN switch for the D channel.
Step 9 Click Save (under the General tab).
Step 2 Select Configure Device > Build Config File from Default AS5xxx Template.
Step 3 If you selected RSC6 in "(Optional) Selecting Split-Mode Parameters for the Cisco AS5850 Device (Redundancy Tab)" section, click the Slots 0-5 tab.
If you selected RSC7 in "(Optional) Selecting Split-Mode Parameters for the Cisco AS5850 Device (Redundancy Tab)" section, click the Slots 8-13 tab.
Step 4 Select the type of card installed in each slot.
Step 5 (Optional) Select the framing type used by the controller in this slot.
This field is applicable only if a trunk card occupies the slot.
Step 6 (Optional) Select the controller line code for this slot.
This field is applicable only if a trunk card occupies the slot.
Step 7 (Optional) Select the type of signal used when a channel type is channelized.
This field is applicable only if a trunk card occupies the slot and is configured to be Primary Rate Interface (PRI).
Step 8 Select an ISDN switch for the D channel.
Step 9 Click Save (under the General tab).
|
Note Cisco UGM default configuration templates support IP connectivity over Ethernet or Loopback interfaces only. |
Step 2 Select Configure Device > Build Config File from Default AS5xxx Template.
Step 3 Click the Interface tab.
Step 4 Select the ISDN switch type.
Step 5 Enter Ethernet and Fast Ethernet IP addresses and masks.
Step 6 Enter loopback IP addresses and masks.
Step 7 Click Save (under the General tab).
Step 2 Select Configure Device > Build Config File from Default AS5xxx Template.
Step 3 Click the SNMP tab.
Step 4 Enter the location and owner of this system.
Step 5 Enter the SNMP read and write community strings.
Step 6 Enter the Cisco IOS Trap Source (name of the interface).
Step 7 Enter the IP addresses of hosts where the traps will be sent.
The Cisco UGM server IP address is automatically configured as a trap host.
Step 8 Click Save (under the General tab).
Step 2 Select Configure Device > Build Config File from Default AS5xxx Template.
Step 3 Click the Management tab.
Step 4 To enable a Cisco IOS core dump transfer to all the hosts on the core dump list, select:
Step 5 (Optional) Select a transfer method to use when sending the Cisco IOS core dump file to its destinations:
This field is applicable only if you enabled Cisco IOS core dump transfer.
Step 6 (Optional) Enter the FTP User Name.
This field is applicable only if you enabled Cisco IOS core dump transfer and selected the FTP transfer method.
Step 7 (Optional) Enter a password to use when sending the Cisco IOS core dump file through FTP.
This field is applicable only if you enabled Cisco IOS core dump transfer and selected the FTP transfer method.
Step 8 (Optional) Enter a filename for the Cisco IOS core dump file being transferred.
The default for this field is hostname-core. This field is applicable only if you enabled Cisco IOS core dump transfer.
This field is applicable only if you enabled Cisco IOS core dump transfer and selected the FTP transfer method.
Step 9 (Optional) Enter a list of hosts or IP addresses that will receive the Cisco IOS core dump file.
This field is applicable only if you enabled Cisco IOS core dump transfer.
Step 10 To enable logging hosts, select:
Step 11 Select a Logging Facility.
Step 12 Select a level of traps to be sent to the logging server.
Step 13 Enter the IP addresses where you want to send logging information.
If the logging hosts are enabled, Cisco UGM sets the Cisco EMF server address as a logging host.
Step 14 To set the time parameter, select the time zone in which this device is located.
Step 15 Specify if this device uses daylight savings time.
Step 16 Enter the IP addresses of Network Time Protocol (NTP) servers.
Step 17 Click Save (under the General tab).
Step 2 Select Configure Device > Build Config File from Default AS5xxx Template.
Step 3 Click the SPE/Modem tab.
Step 4 Specify if you want to enable the modem or SPE firmware upgrade in the configuration file.
Step 5 (Optional) Select the modem/SPE firmware upgrade method:
A card does not move to the busyout state if even one of its modems is processing a call. This can prevent the firmware upgrade. You can terminate calls by using the Cisco IOS clear command.
You can schedule download-maintenance windows by using Cisco IOS commands. When you select the download-maintenance option for firmware upgrade, the modems run the old firmware until Cisco UGM enters the scheduled maintenance window. During this scheduled maintenance, any calls in progress are dropped. When the firmware upgrade is complete, the modems resume call processing by using the new firmware.
This field applies only if you enabled modem or SPE upgrade.
|
Note You can select the firmware upgrade method either here or in the IOS
Operations dialog box (see the
"Task 2:
Selecting a Reload Option After a Configuration Download" section
2-5). You can select the firmware upgrade method from either location in order to set the same Cisco UGM variable. |
Step 6 Enter the SPE firmware file name that is stored in Flash memory.
Step 7 Click Save (under the General tab).
Step 2 Select Configure Device > Build Config File from Default AS5xxx Template.
Step 3 Click the Other tab.
Step 4 Enter the beginning and ending IP addresses of the local IP address pool.
Step 5 Specify if Enhanced Interior Gateway Routing Protocol (EIGRP) should be enabled by selecting Yes or No.
Step 6 Enter a list of EIGRP network IP addresses.
Step 7 Specify if Virtual Private Dialing Network (VPDN) support is enabled for this device.
Step 8 Enter the VPDN source IP address.
Step 9 Enter a list of DNS server IP addresses.
Step 10 Enter a list of NetBIOS Name Service (NBNS) server IP addresses.
Step 11 Enter a list of default route IP addresses.
Step 12 Enter a list of IP addresses for name servers.
Step 13 Click Save (under the General tab).
|
Note Before you start building the configuration file, save all parameters that you entered by selecting the General tab and then clicking Save. |
Step 2 Select Configure Device > Build Config File from Default AS5xxx Template.
Step 3 Click the General tab.
Step 4 Click Build Configuration.
Cisco UGM creates a configuration file object in the ConfigurationFiles folder under the device object in the Physical view.
Cisco UGM saves the new configuration file object under the following file name: autoGenerated_year_month_day_hour_minute_second.
For example, if the new file name is autoGenerated_2001_04_06_13_28_50, this indicates that the configuration file was created from the default template on April 6, 2001 at 13:28:50.
You can now associate the file with a device as described in the "Task 5: Associating a Configuration File with a Device Object" section.
To build a new configuration file, see the "Task 3: Option 1: Building a Configuration File from a Template" section.
When you click Get Startup Configuration in the IOS Operations Dialog box, you upload the configuration file from a device to the /tftpdir directory on the Cisco UGM server. This is a real-time operation that cannot be scheduled later.
|
Note The Get Startup Configuration operation retrieves the startup Cisco IOS
configuration on the target device—not the running Cisco IOS configuration
on that device. If the running configuration on the target device is different from its startup configuration and you want to retrieve the running configuration, first click Copy Running to Startup before following this procedure. |
Step 2 Choose AS5xxx > Configure Device > Perform IOS Operations.
Step 3 Select the device from the list, and click Get Startup Configuration.
An Action Report window appears with the contents of the configuration file that you uploaded.
Cisco UGM saves the new configuration file object under the following file name: startup_year_month_day_hour_minute_second.
For example, if the new file name is startup_2001_04_26_17_28_50, this indicates that the configuration file was created from the default template on April 26, 2001 at 17:28:50.
You can now associate the file with a device as described in the "Task 5: Associating a Configuration File with a Device Object" section.
To edit the configuration file, see the "(Optional) Task 11: Viewing and Editing Configuration Files and Configlets" section.
Before importing a configuration file, you must deploy a managed device.
Step 2 From a ConfigurationFiles object, a container object, or a device object, select Deployment > Import NAS File Object.
Step 3 If you launch the dialog box is from a ConfigurationFiles or container object, the Deployment Wizard appears:
a. In the Template Choices window, select the Store Configuration File option and click Forward.
b. In the first Object Parameters window, enter the name of the configuration file object as it will appear in the Map Viewer.
c. Enter the full-path filename and description of the Cisco IOS configuration file to be imported.
|
Note If you enter an invalid full-path filename (or no path) for the configuration file, the import operation fails. |
e. Proceed to Step 5.
Step 4 If you launch the dialog box from a device object, the Deployment Wizard appears:
a. In the Template Choices window, select the Store Configuration File option and click Forward.
b. In the first Object Parameters window, enter the name of the configuration file object as it will appear in the Map Viewer.
c. Enter the full-path filename and description of the Cisco IOS configuration file to be imported.
e. Click Select Relationships.
f. Expand the Physical tree until the ConfigFiles folder is visible.
g. Select the folder and click Apply.
i. Proceed to Step 5.
The user-supplied Cisco IOS configuration file is now stored in the ConfigurationFiles folder for the appropriate device object. Now, you can associate the file with a specific device in the network. See the "Task 5: Associating a Configuration File with a Device Object" section.
Step 2 From the Configlets folder in the NAS-File-Repository, select Deployment > Import NAS File Object.
The Deployment Wizard appears.
Step 3 In the Template Choices window, select Store Configlet and click Forward.
Step 4 In the first Object Parameters window, enter the name of the configlet object as it will appear in the Map Viewer.
Step 5 Enter the full path to the filename and a description of the configlet to be imported.
|
Note If you enter an incorrect path for the configlet, the import operation fails. If you leave the path field blank, an empty configlet is created. You can add content to the configlet by editing it later. See the "(Optional) Task 11: Viewing and Editing Configuration Files and Configlets" section 2-28. |
Step 6 Click Forward.
Step 7 Click Finish.
|
Note Configlet contents do not need begin and end statements. Cisco UGM does not check the contents of the configlet. |
The user-supplied configlet is now stored in the Configlets folder under the NAS-File-Repository. Now you can associate the configlet with one or more devices in the network. See the "(Optional) Task 6: Associating a Configlet with a Device Object" section
|
Note The predefined configlets listed in Table 2-2 are examples. Modify them as necessary to work in your network environment. |
Table 2-2 Predefined Configlets
You must associate a configuration file with a device object before you can download it to the device.
|
Note You cannot associate the same configuration file with multiple devices in the same operation. |
Step 2 From the Device list, select one of these device objects:
Step 3 From the Configuration File list, select the file (corresponding to your selected devices) to associate with the selected device. This is a Cisco IOS configuration file with prespecified parameters.
Step 4 Click Save Association.
The Associated with Config File field is updated to reflect the new configuration file association.
In the Map Viewer, the associated configuration file has _current added to the filename.
For example, if the filename (before association) was autoGenerated_2001_04_06_13_28_50, the same file (after association) appears in the Map Viewer as autoGenerated_2001_04_06_13_28_50_current.
A device can be associated with only one configuration file at a time. The current association always erases the previous association.
You must associate a configlet with a device object before you can download it to the device.
|
Note You can associate the same configlet with multiple devices in the same operation, however, a device can be associated with only one configlet at a time. |
Step 2 From the Device list, select one or more of these device objects:
Step 3 From the Configlet list, select the configlet to associate with the selected device. This is a file that consists of Cisco IOS CLI commands.
Step 4 Click Save Association.
The Associated with Configlet field is updated to reflect the new configlet association.
In the Map Viewer, configlet names do not change after association with a device object. To check a configlet association, access the Associate Configlet Object with Device dialog box.
You can now proceed to "(Optional) Task 8: Sending a Configlet to the Running Configuration File" section.
You can download a configuration file from the Cisco UGM server to a managed device by clicking Send Configuration to Startup in the IOS Operations dialog box.
If you are downloading a configuration file to several devices, first check that all the selected devices are of the same type, and then associate the configuration file with each individual device.
Step 2 Select Yes or No to specify if the device should be rebooted after a configuration is downloaded.
The default is No (no reload).
Step 3 Click Save.
Step 4 Select the devices from the list in the left panel and click Send Configuration to Startup.
The Action Result window shows the success of the operation.
If you selected the Reload After Config Download option, the device reboots. (See the "Task 2: Selecting a Reload Option After a Configuration Download" section.)
You can download a configlet from the Cisco UGM server to one or more managed devices by clicking Send Configlet to Running in the IOS Operations dialog box.
If you are installing a configlet on several managed devices, first check that all the selected devices are of the same type, and then associate the configlet with the devices.
Step 2 Select the devices from the list in the left panel and click Send Configlet to Running.
The Action Result window shows the success of the operation.
|
Note In order to save the configlets and current configuration, click Copy Running to Startup. See the "(Optional) Task 10: Copying the Running Configuration to the Startup Configuration File" section. |
You can upload a startup configuration file (from a managed device) to the
Cisco UGM server by clicking Get Startup Configuration in the IOS Operations dialog box.
year_month_day_hour_minute_second
Example: startup_2001_04_26_13_28_50
Step 2 Select the devices from the list in the left panel and click Get startup Configuration.
The Action Result window shows the success of the operation.
You can copy the running configuration file (from a managed device) to its startup configuration file by clicking Copy Running to Startup in the IOS Operations dialog box.
Step 2 Select the devices from the list in the left panel and click Copy Running to Startup.
The Action Result window shows the success of the operation.
You can use this procedure to create a configlet. If you imported an empty configlet earlier (see "(Optional) Task 4: Importing a Configlet" section), you can now view the empty configlet and create content for it.
Step 2 Choose Edit Configuration File or Edit Configlet.
The description and content of the file appears. The text can be edited directly in the dialog box.
Step 3 Click Save.
The revised configuration file or configlet is saved under the original filename.
Posted: Sat Apr 5 07:59:09 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.