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:

Uploaded from the startup configuration of a device.
Imported from a UNIX file system.
Generated from the default template.

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.

State Changes in Supported Devices

This table indicates if a state change results from configuration actions available for Cisco UGM-managed devices.

Table 3-1: State Changes Associated with Configuration Actions

Configuration Action	State Change
Generate configuration file from a template	No
Get Startup Configuration	No
Associate a configuration file with a device	No
Associate a configlet with a device	No
Send Configuration to Startup	Yes (only if followed by a reload)
Send Configlet to Running	No
Copy Running to Startup	No

Note You cannot schedule file operations, and they do not change the state of the managed device.

Task 1: Authenticating the Device Object

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

Step 1 From a container or device object to be configured, select Configure Device > Open Device Authentication Information.

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:

IOSConfigCtrlUserData.ini
attrValueOpTimeout=n

Step 7 Enter the Prompt Timeout value in seconds. The default value is 10 seconds.

You can change this value located at:

IOSConfigCtrlUserData.ini
attrValuePromptTimeout=n

Note Enter values in all the fields in this dialog box. If you do not enter these values, the following operations will fail:
Show CLI
Configure Administrative State
All actions on the IOS Operations dialog box.

Step 8 Click Save.

Task 2: Selecting a Reload Option After a Configuration Download

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

Step 2 Under Options, select an option for Reload After Config Download.

Yes—The managed device reboots after the Send Configuration to Startup operation.
No— The managed device does not reboot immediately after the Send Configuration to Startup operation, and you can schedule the device reload operation.

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.

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

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.

Selecting Access Parameters (General Tab)

Step 1 From the Map Viewer window, select the device object for which you will build a configuration file.

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.

(Optional) Selecting Split-Mode Parameters for the Cisco AS5850 Device (Redundancy Tab)

Step 1 From the Map Viewer window, select the Cisco AS5850 device object for which you wish to build a configuration file.

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.

Classic-split—In this mode, the configuration file you are building configures cards controlled by the Router Shelf Controller (RSC) that you select in Step 5.
Handover-split—In this mode, the configuration file you are building configures all cards installed in all slots in this device.

Step 5 Select a Router Shelf Controller (RSC) for the device:

RSC6—Specifies that the RSC is installed in slot 6 of the parent device. The Ethernet information in slot 7 is ignored. (This configuration file configures Ethernet ports in slot 6 only.)

If you selected the Classic-split mode in Step 4, this configuration file configures cards installed in slots 0 through 5 only.
If you selected the Handover-split mode in Step 4, this configuration file configures all the cards installed in all the slots on the device.

RSC7—Specifies that the RSC is installed in slot 7 of the parent device. The Ethernet information in slot 6 is ignored. (This configuration file configures Ethernet ports in slot 7 only.)

If you selected the Classic-split mode in Step 4, this configuration file configures cards installed in slots 8 through 13 only.
If you selected the Handover-split mode in Step 4, this configuration file configures all the cards installed in all the slots on the device.

Step 6 Repeat this procedure for the next Cisco AS5850 managed device.

Step 7 Click Save (under the General tab).

Selecting Card Parameters (Slots Tab)

Step 1 From the Map Viewer window, select the device object for which you will build a configuration file.

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).

(Optional) Selecting Card Parameters for the Cisco AS5850 Device (Slots 0-5 Tab; Slots 8-13 Tab)

Step 1 From the Map Viewer window, select the device object for which you will build a configuration file.

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).

Selecting Interface Parameters (Interface Tab)

Note Cisco UGM default configuration templates support IP connectivity over Ethernet or Loopback interfaces only.

Step 1 From the Map Viewer window, select the device object for which you will build a configuration file.

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).

Entering SNMP Information for a Trap (SNMP Tab)

Step 1 From the Map Viewer window, select the device object for which you will build a configuration file.

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).

Selecting Cisco IOS Core Dump, Logging, and Time Parameters (Management Tab)

Step 1 From the Map Viewer window, select the device object for which you will build a configuration file.

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:

Yes
No

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

ftp
tftp

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:

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 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).

Entering Modem and SPE Parameters (SPE and Modem Tabs)

Step 1 From the Map Viewer window, select the device object for which you will build a configuration file.

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:

busyout (Graceful)—Prevents idle modems from accepting calls, but allows completion of any calls in progress. When the call is complete, the modem moves to the busyout state and does not accept any new calls. When all the modems on a card are in the busyout state, the firmware is upgraded on the card, and the card (and modems) move to the normal state.

: 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.

reboot (Forceful)—Upgrades the modem or SPE image during the next device reboot.
recovery—The firmware upgrade is delayed until recovery maintenance time.
download-maintenance—The firmware image is upgraded only when the managed device is taken offline for maintenance purposes.

: 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).

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).

Entering Network Communication Parameters (Other Tab)

Step 1 From the Map Viewer window, select the device object for which you will build a configuration file.

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).

Building the Configuration File

Note Before you start building the configuration file, save all parameters that you entered by selecting the General tab and then clicking Save.

Step 1 From the Map Viewer window, select the device object for which you will build a configuration file.

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.

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 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 1 From the Map Viewer, select the device 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 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.

Task 3: Option 3: Importing a Configuration File

Before importing a configuration file, you must deploy a managed device.

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

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.

d. Click Forward.

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.

d. Click Forward.

e. Click Select Relationships.

f. Expand the Physical tree until the ConfigFiles folder is visible.

g. Select the folder and click Apply.

h. Click Forward.

i. Proceed to Step 5.

Step 5 Click Finish.

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.

(Optional) Task 4: Importing a Configlet

Step 1 Copy the configlet that you want to import to a directory accessible from the Cisco EMF server where Cisco UGM is installed.

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.

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

Cisco UGM Predefined Configlets

Note The predefined configlets listed in Table 3-2 are examples. Modify them as necessary to work in your network environment.

Table 3-2: Predefined Configlets

Configlet Object Name	Configlet Content
AAA	aaa new-model
	aaa authentication login default none
	aaa authentication login h323 group radius
	aaa authentication login NONE none
	aaa authorization exec h323 group radius
	aaa accounting connection h323 start-stop group radius
	enable password test
BusyoutDS0	controller t1 <num>
BusyoutDS0	busyout ds0 <range>
CodecClass	voice class codec 88
	codec preference 1 g729br8 bytes 50
	codec preference 3 g729r8 bytes 50
	codec preference 5 g723ar53
	codec preference 6 g723ar63 bytes 144
	codec preference 7 g723r53
	codec preference 8 g723r63 bytes 120
	dial-peer voice 1000 voip
DTMFRelay	dial-peer voice 1000 voip
DTMFRelay	dtmf-relay h245-alphanumeric h245-signal cisco-rtp
EnableT38	dial-peer voice 1000 voip
EnableT38	fax protocol t38 ls-redundancy 5 hs-redundancy 0
E1PRI	controller E1 1/0
	framing NO-CRC4
	pri-group timeslots 1-31 service mgcp
	controller E1 1/1
	framing NO-CRC4
	ds0-group 0 timeslots 1-15, 17-31 type none service mgcp
IVR	call application voice debit tftp://ivrserver/tcl/ debitcard.tcl
	call application voice debit warning-time 30
	call application voice debit language 1 en
	call application voice debit language 2 ch
	call application voice debit set-location en 0 tftp://ivrserver/au/en/
	call application voice debit set-location ch 0 tftp://ivrserver/au/ch
MGCP	mgcp
	mgcp call-agent <CallAgent> 2427 service-type mgcp version 0.1
	mgcp max-waiting-delay 1000
	mgcp restart-delay 2
	mgcp codec g711alaw packetiaztion-period 10
	mgcp ip qos dscp cs4 media
	mgcp package-capability dtmf-package
	mgcp default-package dtmf-package
	mgcp timer receive-rtcp 100
	mgcp profile default
NTP	ntp clock-period 17178985
	ntp server 10.19.29.100
	ntp update-calendar
PRIBackhaul	backhaul-session-manager
	set spnas_set client ft
	group master set spnas_set
	group slave set spnas_set
	session group master <CallAgentMaster> 1803 <GatewayAddress> 1803 1
	session group slave <CallAgentSlave> 1803 <GatewayAddress> 1803 1
	isdn switch-type primary-net5
	isdn voice-call-failure 0
RadiusAccounting	radius-server host 2.10.6.26 auth-port 1645 acct-port 1646
	radius-server retransmit 3
	radius-server timeout 4
	radius-server deadtime 5
	radius-server key cisco
	radius-server vsa send accounting
	radius-server vsa send authentication
RadiusWithAAA	radius-server host 156.151.37.252 auth-port 1812 acct-port 1813
	radius-server retransmit 0
	radius-server key testing123
	radius-server vsa send accounting
	radius-server vsa send authentication
SNMP	snmp-server community <communityStringForRO> RO
	snmp-server community <communityStringForRW> RW
	snmp-server enable traps snmp authentication linkdown linkup coldstart warmstart
	snmp-server enable traps entity
	snmp-server enable traps envmon
	snmp-server trap-source <InterfaceName>
	snmp-server host <UGMServerIPAddress> public
	snmp-server location <SystemLocation>
	snmp-server contact <SystemContact>
	snmp-server system-shutdown
SS7ForIntegratedSLT	interface Serial3/3:15
	no ip address
	encapsulation ss7
	channel-id 0
	!
	interface Serial3/4:15
	no ip address
	encapsulation ss7
	channel-id 1
	!
	ss7 session 1 address <GatewayIPAddress> 7000 <MGCHostIPAddress> 7000
	ss7 mtp2-variant itu 0
	ss7 mtp2-variant itu 1
	ss7 mtp2-variant itu 2
	ss7 mtp2-variant itu 3
T1CAS	controller T1 0
	framing esf
	clock source line primary
	linecode b8zs
	ds0-group 0 timeslots 1-24 type e&m-immediate
T1PRI	isdn switch-type primary-5ess
	!
	controller T1 0
	framing esf
	clock source line primary
	linecode b8zs
	pri-group timeslots 1-24
	!
	interface Serial0:23
	description Abacus ORIGINATING PRI#1
	no ip address
	ip mroute-cache
	isdn switch-type primary-5ess
	isdn tei-negotiation first-call
	isdn incoming-voice modem
	fair-queue 64 256 0
	no cdp enable
VOIPGatewayWithGatekeeper	interface FastEthernet0
	description rack subnet
	ip address 10.10.2.1 255.255.255.0
	duplex auto
	speed auto
	h323-gateway-voip interface
	h323-gateway-voip id ogk-zone1 ipaddr 10.10.2.201 1719 priority 1
	h323-gateway-voip id ogk-zone1 ipaddr 10.10.2.203 1719 priority 10
	h323-gateway-voip h323-id orig-gw1
	h323-gateway-voip tech-prefix 21#

Task 5: Associating a Configuration File with a Device Object

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 1 In the Cisco UGM tree, from a container or device object choose Configure Device > Associate Configuration File Object with Device.

Step 2 From the Device list, select one of these device objects:

AS5300Chassis
AS5350Chassis
AS5400Chassis
AS5800Chassis
AS5850Chassis

Note If the selected device has a configuration file already associated with it, the name of the file appears in the Associated with Config File field.

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.

(Optional) Task 6: Associating a Configlet with a Device Object

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 1 In the Cisco UGM tree, from a container or device object choose Configure Device > Associate Configlet Object with Device.

Step 2 From the Device list, select one or more of these device objects:

AS5300Chassis
AS5350Chassis
AS5400Chassis
AS5800Chassis
AS5850Chassis

Note If the selected device has a configlet already associated with it, the name of the configlet appears in the Associated with Configlet field.

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.

Task 7: Sending a Configuration File from the Cisco UGM Server to the Startup File of a Device Object

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.

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.
With Send Configuration to Startup, you can download the same configuration file to multiple devices.

: 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 1 From a container or device object choose Configure Device > Perform IOS Operations.

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.)

(Optional) Task 8: Sending a Configlet to the Running Configuration File

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.

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 configlet.
The Send Configlet to Running operation can be performed on multiple devices.

: 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 1 From a container or device object, choose Configure Device > Perform IOS Operations.

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 on page 3-31.

(Optional) Task 9: Uploading the Device Startup Configuration File to the Cisco UGM Server

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.

This is a real time operation that cannot be scheduled to run at a future time.
The managed device must be in the normal state before you can start the uploading process.
The Get Startup Configuration operation can be performed on multiple devices.
The configuration file object is created in the ConfigurationFiles folder under the corresponding chassis in the Physical view.
The configuration file object name assigned is startup_timestamp where timestamp has the following format:

: year_month_day_hour_minute_second
: Example: startup_2001_04_26_13_28_50

Step 1 From a container or device object, choose Configure Device > Get startup Configuration.

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.

(Optional) Task 10: Copying the Running Configuration to the Startup Configuration File

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.

This is a real time operation that cannot be scheduled to run at a future time.
The managed device must be in the normal state before you can start the copy process.
The Copy Running to Startup operation can be performed on multiple devices.

Step 1 From a container or device object, choose Configure Device > Perform IOS Operations.

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.

(Optional) Task 11: Viewing and Editing Configuration Files and Configlets

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 1 From the Map Viewer, select a configuration file or configlet object to view or edit.

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.

Table of Contents

Configuring Devices with Cisco UGM

Overview of Configuring Managed Devices

State Changes in Supported Devices

Task 1: Authenticating the Device Object

Task 2: Selecting a Reload Option After a Configuration Download

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

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

Task 3: Option 2: Using an Existing Configuration File

Task 3: Option 3: Importing a Configuration File

(Optional) Task 4: Importing a Configlet

Cisco UGM Predefined Configlets

Task 5: Associating a Configuration File with a Device Object

(Optional) Task 6: Associating a Configlet with a Device Object

Task 7: Sending a Configuration File from the Cisco UGM Server to the Startup File of a Device Object

(Optional) Task 8: Sending a Configlet to the Running Configuration File

(Optional) Task 9: Uploading the Device Startup Configuration File to the Cisco UGM Server

(Optional) Task 10: Copying the Running Configuration to the Startup Configuration File

(Optional) Task 11: Viewing and Editing Configuration Files and Configlets