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.

Tip Before testing IOS operations on your Cisco UGM system, save the original configuration file from the device, so that you can retrieve it if necessary.

This table shows configuration actions available for Cisco UGM-managed devices: Cisco AS5350, AS5400, AS5800, and AS5850.

Table 4-1: Configuration Actions and the Devices on Which They Are Supported

	AS5350	AS5400	AS5800	AS5800 with 324 Universal Port Card	AS5850	State Change	Can Be Scheduled
Get Configuration	Yes	Yes	Yes	Yes	Yes	No	No
Send Configuration	Yes	Yes	Yes	Yes	Yes	Yes	No

Task 1: Preparing the Device for Configuration

Changes that you make in the Device Readiness Configuration dialog box are applied only to the selected device object.

Step 1 In Map View > Physical, right-click the device object to be configured, and select Device Readiness Configuration.

Step 2 Click the Login tab. Select an authentication method:

Group—(Default) The device uses the values defined in the Group Authentication method and the Group Authentication Object Name.

: These values are defined in the System Object Settings dialog box (Map View > Physical > AS5xxxx > Device Readiness Configuration).

Local—If you select this value, the authentication values that you enter in the following steps are applied to the device.

Step 3 (Optional) Enter the name of the Group Authentication object used by this device.

This field is used only if you selected the Group authentication method.

Step 4 Enter a password for administrators to access the system.

Step 5 Enter the username as configured on the device.

This entry must match a username that you selected when building the device configuration file. See the "Task 3: Option 1: Building a Configuration File from a Template" section.

Step 6 Enter a password corresponding to the User ID, followed by the login password.

This entry must match a password that you selected when building the device configuration file. See the "Task 3: Option 1: Building a Configuration File from a Template" section.

Step 7 Click OK.

Step 8 Click the Trap tab. Select the interface where SNMP traps currently originate.

Step 9 Select if the traps should be saved to NV Ram.

Step 10 Click Set Trap Source and Trap Receiver.

This starts Cisco IOS commands that enable trap forwarding by using the specified input as the source interface and the Cisco UGM server host as the trap destination.

Task 2: Entering IOS Access Parameters

Step 1 In the Physical tree, locate and right-click the device object for which you want to enter access parameters.

Step 2 Select Configure Device > Perform IOS Operations.

Step 3 Select the interface through which Cisco IOS commands can access the selected devices.

Console—Enables you to access and configure the selected devices through a connected console even, if the Ethernet address for the selected device is inaccessible.

Ethernet—Enables you to directly access the selected devices through the IP addresses by which the device was discovered during deployment.

: If you selected the Ethernet configuration interface, the IP address of the target device (discovered when the device was deployed) appears.

Step 4 If you selected the Console configuration interface to configure the device, enter the IP address and the port number of the connected console.

Step 5 Select the firmware upgrade method:

busyout (Graceful)—The modem/SPE image is upgraded immediately on idle modem ports. The modem ports with calls are upgraded after the calls are completed.

reboot (Forceful)—The modem/SPE image is upgraded when the device is rebooted.

download-maintenance

Step 6 After you enter the IOS access parameters, save them:

If you want to apply all the displayed IOS access parameters to your selected devices, click Save.

Note If you enter IOS Access Information for multiple devices and click Save, Cisco UGM saves only the Configuration Interface, Console Address, and Firmware Upgrade Option.

Cisco UGM does not save the Ethernet Address and Console Port Number because these attributes are unique for each device.

If you want to apply only the IOS access parameters that you changed to your selected devices, click Save File in the icon bar.
If you specify IOS access parameters for multiple devices, but other individual devices have unique IOS access parameter values (such as login name or password), select that device only, modify the parameter, and click Save.

Task 3: Option 1: Building a Configuration File from a Template

To build a configuration file from a template, complete the following procedures in this order:

1. Selecting Access Parameters (General Tab)

2. Selecting Card Parameters (Slots Tab)

3. Selecting Interface Parameters (Interface Tab)

4. Entering SNMP Information for Traps (SNMP Tab)

5. Selecting IOS Core Dump and Logging Parameters (Management Tab)

6. Entering Modem and SPE Parameters (Modem/SPE Tab)

7. Entering Network Communication Parameters (Other Tab)

8. Building and Viewing the Configuration

However, if you wish to use an existing configuration file, see the "Task 3: Option 2: Using an Existing Configuration File" section.

Selecting Access Parameters (General Tab)

Step 1 From the Map Viewer window, select NAS-File-Repository > AS5xxxChassis > Template > Def5xxx TemplateFile > Build Config File from Default AS5xxx Template.

Step 2 Click the General tab.

Step 3 Enter the host name of the device.

Step 4 Select the authentication method for users, accounting, administrative users, the network, and Point-to-Point Protocol (PPP) users if necessary.

Step 5 Enter the authentication key to use with Radius or Terminal Access Controller Access Control System (TACACS) servers.

Step 6 Select the list of Radius or TACACS servers to use for authentication.

Step 7 Enter local user names and passwords.

Selecting Card Parameters (Slots Tab)

Step 1 From the Map Viewer window, select NAS-File-Repository > AS5xxxChassis > Template > Def5xxx TemplateFile > Build Config File from Default AS5xxx Template.

Step 2 Click the Slots tab.

Step 3 Select the type of card installed in each slot.

Step 4 (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 5 (Optional) Select the controller line code for this slot.

This field is applicable only if a trunk card occupies the slot.

Step 6 (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).

Selecting Interface Parameters (Interface Tab)

Step 1 From the Map Viewer window, select NAS-File-Repository > AS5xxxChassis > Template > Def5xxxTemplateFile > Build Config File from Default AS5xxx Template.

Step 2 Click the Interface tab.

Step 3 Select the ISDN switch type.

Step 4 Enter port IP addresses and masks.

Step 5 Enter loopback IP addresses and masks.

Entering SNMP Information for Traps (SNMP Tab)

Step 1 From the Map Viewer window, select NAS-File-Repository > AS5xxxChassis > Template > Def5xxxTemplateFile > Build Config File from Default AS5xxx Template.

Step 2 Click the SNMP tab.

Step 3 Enter the location and owner of this stack.

Step 4 Enter the SNMP read and write community strings.

Step 5 Enter IP addresses of hosts where traps will be sent.

Selecting IOS Core Dump and Logging Parameters (Management Tab)

Step 1 From the Map Viewer window, select NAS-File-Repository > AS5xxxChassis > Template > Def5xxxTemplateFile > Build Config File from Default AS5xxx Template.

Step 2 Click the Management tab.

Step 3 To enable an IOS core dump to all the hosts on the core dump list, select:

Yes
No

Step 4 (Optional) Select a transfer method to use when sending the IOS core dump file to its destinations:

ftp
tftp

This field is applicable only if you enabled IOS core dump transfer.

Step 5 (Optional) Enter the name of the FTP user that will send the IOS core dump file.

This field is applicable only if you enabled IOS core dump transfer and selected the FTP transfer method.

Step 6 (Optional) Enter a filename for the IOS core dump file being transferred.

The default for this field is hostname-core. This field is applicable only if you enabled IOS core dump transfer.

Step 7 (Optional) Enter a password to use when sending the IOS core dump file through FTP.

This field is applicable only if you enabled IOS core dump transfer and selected the FTP transfer method.

Step 8 (Optional) Enter a list of hosts or IP addresses that will receive the IOS core dump file.

This field is applicable only if you enabled IOS core dump transfer.

Step 9 To enable logging hosts, select:

Yes to enable the device to send syslog to the logging hosts. (This is the default.)
No to disable the transfer of syslog to the logging hosts.

Step 10 Select a logging facility.

Step 11 Select a level of traps to be sent to the logging server.

Step 12 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 13 Select the time zone in which this device is located.

Step 14 Specify if this device uses daylight savings time.

Step 15 Enter the IP addresses of Network Time Protocol (NTP) servers.

Entering Modem and SPE Parameters (Modem/SPE Tab)

Step 1 From the Map Viewer window, select NAS-File-Repository > AS5xxxChassis > Template > Def5xxxTemplateFile > Build Config File from Default AS5xxx Template.

Step 2 Select if you want to enable the modem or SPE firmware upgrade in the configuration file.

Step 3 (Optional) Select the modem/SPE firmware upgrade method:

busyout (Graceful)—Upgrades the modem/SPE image immediately on idle modem ports. The modem ports with calls are upgraded after the calls are completed.

reboot (Forceful)—Upgrades the modem/SPE image during the next device reboot.

download-maintenance

This field applies only if you enabled modem or SPE upgrade.

Step 4 Enter the SPE firmware file name that is stored in Flash memory.

Entering Network Communication Parameters (Other Tab)

Step 1 From the Map Viewer window, select NAS-File-Repository > AS5xxxChassis > Template > Def5xxxTemplateFile > Build Config File from Default AS5xxx Template.

Step 2 Enter the beginning and ending IP addresses of the local IP address pool.

Step 3 Enter the Enhanced Interior Gateway Routing Protocol (EIGRP ) autonomous system number.

Step 4 Enter a list of EIGRP network IP addresses.

Step 5 Enter the Challenge Handshake Authentication Protocol (CHAP) host name for this device.

Step 6 Select if Virtual Private Dialing Network (VPDN ) support is enabled for this device.

Step 7 Enter a list of DNS server IP addresses.

Step 8 Enter a list of NetBIOS Name Service (NBNS ) server IP addresses.

Step 9 Enter a list of default route IP addresses.

Step 10 Enter a list of IP addresses for name servers.

Building and Viewing the Configuration

Step 1 From the Map Viewer window, select NAS-File-Repository > AS5xxxChassis > Template > Def5xxxTemplateFile > Build Config File from Default AS5xxx Template.

Step 2 Click the General tab.

Step 3 Click Build and View Configuration.

Cisco UGM saves the new configuration file with a unique file name that includes a randomly generated number.

For example, the new file name is similar to 5400.config-16838 and is automatically imported into the NAS-File-Repository. You can now associate the file with a device as described in the "Task 5: Option 1: Associating a Configuration File with a Device Object" section.

Task 3: Option 2: Using an Existing Configuration File

To build a new configuration file, see the "Task 3: Option 1: Building a Configuration File from a Template" section.

When you click Get Configuration in the Performing IOS Operations dialog box, you upload the configuration file from a device to the Cisco UGM server. This is a real time operation that cannot be scheduled to later.

Note The Get Configuration operation retrieves the startup IOS configuration on the target device—not the running IOS configuration on that device.

Cisco UGM does not retrieve configuration statements input to the target device after startup. If the running configuration on the target device is different from its startup configuration and you want to retrieve the running configuration, you must manually save the running configuration as the startup IOS configuration on the target device before following this procedure.

Step 1 From the Map Viewer, select the chassis object whose configuration file you want to upload to the server.

Step 2 Choose AS5xxx > Configure Device > Perform IOS Operations.

Step 3 Select the device from the list, and click Get Configuration.

An Action Report window displays the contents of the configuration file that you uploaded.

Step 4 In the Action Report window, click Save.

Step 5 Enter a location to store the file.

Step 6 By using a UNIX editor, make changes to the configuration file that you uploaded.

Step 7 Complete the procedure in "Task 4: Importing a Configuration File into the NAS-File-Repository" section.

Task 4: Importing a Configuration File into the NAS-File-Repository

Step 1 Copy the file that you want to import to a directory on the Cisco EMF server where Cisco UGM is installed.

Step 2 Select NAS-File-Repository > AS5xxxchassis > Import Files/Images.

The Deployment Wizard appears.

Step 3 In the Template Choices window, select the Configuration option and click Forward.

Note Select the choice that applies to the file you want to import.

Step 4 In the first Object Parameters window, note or enter the name of the configuration file object as it will appear in the Map Viewer.

Step 5 Enter the path, filename, and description of the IOS configuration file to be imported into the NAS-File-Repository.

Step 6 View the summary dialog box. If this information is correct, click Finish.

Step 7 When you receive a message indicating that the file was stored successfully, click Dismiss.

The user-supplied IOS configuration file is now stored in the appropriate category under the NAS-File-Repository view. Now you can associate the file with a specific device in the network.

Task 5: Option 1: Associating a Configuration File with a Device Object

You must associate a configuration file with a device before you can download it to the device.

If you have already associated the configuration file with a device, see "Task 5: Option 2: Re-associating a Configuration File with a NAS-File-Repository Object" section.

Step 1 In the Cisco UGM tree, locate and right-click the device object with which you want to associate the configuration file.

AS5350
AS5400
AS5800
AS5850

Step 2 Choose Configure Device > Associate File Repository Object with Device.

Step 3 Select one or more of these device objects:

AS5350
AS5400
AS5800
AS5850

Note If you select multiple device objects, make sure that they are all of the same type: all Cisco AS5350, AS5400, AS5800, or AS5850 devices.

Step 4 Select one of these device objects:

AS5350Chassis
AS5400Chassis
AS5800Chassis
AS5850Chassis

Step 5 Select Configuration as the type of file to download to the selected device. This is an IOS configuration file with prespecified parameters.

Note You cannot associate the same configuration file with multiple devices in the same operation.

Step 6 View the downloaded file objects and select the version of the configuration file that you want to apply.

When you select the imported file version, the Selected File Repository Object, Description, and Original File Path fields are updated to show the attributes of the selected file.

Step 7 Click Save Association.

The corresponding field in the Device Associated With panel is updated to reflect the new configuration file association.

Task 5: Option 2: Re-associating a Configuration File with a NAS-File-Repository Object

By re-associating an existing file repository object with a new file, you can download the new configuration to many devices without associating the file with each device.

"Task 5: Option 1: Associating a Configuration File with a Device Object" section shows you how to associate a configuration file with a device.

Step 1 In the Cisco UGM tree under the NAS-File-Repository node, locate and right-click the IOS configuration file object that you want to associate with a new configuration file.

Step 2 Select Re-associate File Repository Object with New File.

Existing NAS-File-Repository objects are listed in the left-hand list box.

Step 3 Select the name of the existing NAS-File-Repository object that you want to associate with a new file.

Step 4 Enter a description for the new file.

The original filename and path associated with the selected repository object appears.

Step 5 Enter the path and filename of the new configuration file that you want to store as the NAS-File-Repository object that you selected in Step 3.

Step 6 Click Save Association.

The NAS-File-Repository object points to the new or modified file, and the association with the device is updated.

Task 6: Downloading a Configuration File from the Cisco UGM Server to a Device Object

You can download a configuration file from the Cisco UGM server to a managed device by clicking Send Configuration in the Performing IOS Operations dialog box.

This is a real time operation that cannot be scheduled to run at a future time.
The target devices must be in the normal state before you can start downloading a file.
Clicking Send Configuration changes the device state from normal to softwaredownload, and back to normal when the download is complete.
Clicking Send Configuration reboots the target devices.
The Send Configuration operation on multiple devices is performed sequentially.

: You can install a configuration file on several managed devices. In order to do this, you must first check that all selected devices are of the same type, and then associate the configuration file with each individual device.

Step 1 From the Map Viewer, select the device object which will receive the new configuration file.

Step 2 Choose AS5xxx > Configure Device > Perform IOS Operations.

Step 3 Select the devices from the left-side list and click Send Configuration.

(Optional) Task 7: Viewing Configuration Files

You can view the text commands in a configuration file that has been stored as an object in the NAS-File-Repository.

Note You cannot view Cisco IOS, SPE, or modem images.

Step 1 Under the NAS-File-Repository node in the Cisco UGM tree, locate and right-click the IOS configuration file object that you want to view.

Step 2 Select View Configuration File.

Step 3 Select the name of the existing configuration file object that you want to view.

Step 4 To see the text in the file, Click View.

The contents of the configuration file object appear in the Action Result window.

Step 5 After you finish viewing the file, click Close.

(Optional) Task 8: Editing Configuration Files

Step 1 Complete the procedure through Step 4 in the "(Optional) Task 7: Viewing Configuration Files" section.

Step 2 By using a UNIX file editor, make any necessary changes to the file you just saved.

Step 3 After viewing the file, click Save.

Step 4 Click Close.

Step 5 Complete the procedure in the "Task 5: Option 2: Re-associating a Configuration File with a NAS-File-Repository Object" section.

Table of Contents