|
|
In the GUI application developed by Cisco, network elements and the domains to which they belong are managed through the Element Manager window. To open this window, start the GUI application and click on the Element Manager button on the Main Window (or Element Manager on the Tools menu). The window displays all of the elements, domains, and subdomains to which you have access (as determined by the permissions group to which you belong). There are two kinds of elements:
From this window, you can create, modify, or delete domains and network elements; check the status of elements; upload configurations from the devices to your database; download configurations from your database to devices; and initiate checks on configurations (check the validity of connections, for example).
You can also import network elements into domains from a text file, using a command line script.
Cisco IP Manager manages elements, domains, and composite elements. A composite element is a physical entity in the management network that contains interconnected network elements, and it has a unique name, just as does any element.
The Element Manager window displays devices and domains in an expandable tree structure. The root entry under the heading Domains is reserved for system use. Only the system administrator (login admin) can add to the root level; all that user can add at the root level are subdomains. Elements and composite elements can be added only to subdomains beneath the root level.
The top level in the data tree is the highest-level domain that you have permission to view. When you log in and look at the Element Manager or Template Manager window, you see only as much of the data tree as the system administrator gave you permissions for. See "System Administration and Log Management," for more information about permission groups.
The Element Manager window contains four menus and five buttons.
The Element Manager window contains the following menus:
The File menu contains the following commands:
The Edit menu contains the following commands:
The View menu contains the following commands:
The Help menu contains the following command:
Every domain you create is a child of some other domain. To be able to create a domain, you must belong to a permissions group that has been granted create permission in the parent domain.
To create a new domain, right-click on the parent domain and choose the New option from the floating menu that opens, then choose the SubDomain command from the submenu. Enter a domain name in the dialog that opens and click the OK button (or click the Cancel button to close the dialog without adding a new subdomain).
When you click New and then SubDomain on the floating options menu for a selected domain, and enter a new domain name, the Domain Properties dialog opens.
The Domain Name field displays the name you gave the domain in the previous dialog. This is a read-only field. Once a domain has been created, you cannot change its name, except by deleting the domain from the Element Manager window and creating a new one.
The tab also contains fields for primary and secondary NEMServers. The NEM Server and NEM Backup Server group Name fields are both drop-down lists containing the names of all NEM Servers currently registered with the Orbix Naming Service (launched as NS when the Cisco IP Manager servers were started). For information about NEM Servers, see the section "NEMServer" in "Advanced Usage."
If you have multiple NEMServers running and you want to select a backup that is automatically put into service if the primary server becomes unavailable, select a second server from the NEM Backup Server Name list. Choose In Use from its Status list.
Click the Apply button at the bottom of the window. The status fields are adjusted to reflect the actual status of the two servers. If both are up and available, the primary server's status remains set to In Use and the backup server's status is changed to Standby. If one of the servers is not up at the time, its status is changed to Down and the other server becomes the In Use server.
Once you have set the status and clicked the Apply button, you cannot manually change the status of a server. The only way to force a change in status is to shut one of the servers down and restart it.
Whenever a server that has been designated either the primary or backup NEMServer goes down, its status is changed to Down. When the server becomes available again and there is another NEMServer in use, the status of the newly available server is set to Standby.
For example, assume you have designated the server hostOne to be your primary NEMServer and the server hostTwo to be the backup. If hostOne goes down, hostTwo automatically becomes the primary server (even though it continues to be shown in the NEM Backup Server field in the properties window). The server hostTwo remains the primary NEMServer until it is brought down.
This change in status is not known to the GUI application until you close and reopen the Domain Properties window.
NetworkAdministration.getDomainAtributes() to ADM. Since the GUI timeout is long, this can take over 24 minutes. ADM makes the switchover and sends out a domain modification event. The GUI can then make subsequent calls to NetworkAdministration.getDomainAtributes(). Every call to NetworkAdministration.getDomainAtributes() with a down NEMServer can take up to a minute. Removing the down NEM from the domain property will clear up this delay.
After selecting a server from the NEM Server Name drop-down list, select either Telnet Gateway or SNMP Gateway to configure the appropriate gateway. Similarly, later selecting a server from the NEM Backup Server Name drop-down list, again select either Telnet Gateway or SNMP Gateway to configure the appropriate gateway.
admin and apply to all domains associated with the selected NEMServer. A NEMServer and its associated TGServer and SGServer can have only one set of Telnet/SNMP properties, regardless of which Domain Properties dialog is open when the changes are made.
The page show the server's name, the TFTP server name and path (relative to /tftpboot---if /tftpboot is designated as your TFTP subdirectory, this field is empty), communication attributes, and customized element login prompts.
The Server Name field is for information only. You cannot change this value.
Values for the Operation Timeout, Prompt Timeout, and Socket Base Port fields were set by server flags when the TGServers were launched. You can change these values.
Values for the User Prompt 1, Password 1, User Prompt 2, and Password 2 fields were set by the TGServer, with the default values of Username: and Password:. You can change these values also.
You can set the TFTP server name and path (relative to /tftpboot---if /tftpboot is designated as your TFTP subdirectory, leave this field empty) here.
For information on how to change any of these values at launch time, see the section "Changing Environment Variables and Server Launch Flags" in "Installation and Configuration."
The page show the server's name, the TFTP server name and path (relative to /tftpboot---if /tftpboot is designated as your TFTP subdirectory, this field is empty), operation timeout value, and several SNMP attributes.
The Server Name field is for information only. You cannot change this value.
Values for the Operation Timeout and SNMP attributes fields were set by the SGServer properties file (install_dir/sgs/bin/sgs.properties) when the SGServers were launched. You can change these values.
For information on how to change any of these values at launch time, see the section "Changing Environment Variables and Server Launch Flags" in "Installation and Configuration."
When you have selected the desired servers and configured their associated gateways, click the Apply button to apply the properties to the domain and leave the Domain Properties window open, or click the OK button to apply the properties and close the window.
To create a network element, you must belong to a permissions group that has been assigned create permissions for elements for the domain, on the Domain Permissions tab in the Permission Manager window. You can create a network element or a composite element.
Right-click the mouse on a domain name in the data tree and select the New command, then select the Element command on the submenu that opens. Enter a name in the dialog that opens and click the OK button (or click the Cancel button to close the dialog without creating an element). When the Enter Element Name dialog appears, the name NewElement0 appears and is highlighted. You can replace this name just by starting to type a new name.
See the section "Name Restrictions" elsewhere in this chapter for limitations on characters in names.
The device is added to the data tree displayed in the Element Manager window. If it does not appear, you may have to choose the Refresh command on the View menu.
If the Element Manager window fails to display previously created elements in the data tree, right-click on the domain, click on the Properties command in the floating menu that opens, and click the Apply or OK button in the Domain Properties window. (If the NEMServer status has changed to Down and then back to In Use, the GUI application code can sometimes fall out of synchronization with the actual state of the server as shown in the Domain Properties window. The GUI can take over 24 minutes to time out before initiating the NEM switchover.)
Right-click the mouse on a domain name in the data tree and select the New command, then select the Composite Element command on the submenu that opens.
Enter a name in the dialog that opens and click the OK button (or click the Cancel button to close the dialog without creating an element). When the Enter Element Name dialog appears, the name NewElement0 appears and is highlighted. You can replace this name just by starting to type a new name.
When you click the OK button, a dialog appears requesting the number of slots. Enter the number of slots associated with the composite element, up to a maximum of 100.
This creates a new composite element. You can then create module elements beneath this composite element, in the same manner as described under "Creating a Network Element."
The number of module elements that you can create under a composite element is limited by the number of slots you specify when creating a composite element.
You create a module element beneath a module element. Do this by right-clicking on a composite element, and choosing the New Element dialog. Specify the slot number, and the new module element name, and the Element Manager creates a new module element.
To specify or edit the properties of a network element, right-click on the newly added device in the data tree and select the Properties command from the floating menu that opens. The Device Properties dialog is displayed, with the General tab selected.
This dialog tells the Cisco IP Manager software what property values---IP addresses, user names, passwords, and port numbers (depending on what is selected in the Connect Method list)---should be used when communicating with the selected device.
The Device Properties dialog has seven tabs. You can supply values on any or all of the tabs, depending on which are applicable. When you have filled in values on all the tabs, click the Apply button to apply the properties to the device and leave the Device Properties window open, or click the OK button to apply the properties and close the window. You do not need to click the Apply button before switching to another tab; clicking Apply at any time applies the values you have filled in on all the tabs. Or, click the Cancel button to close the window without saving the changes you have made anywhere in the dialog.
You enter information into the appropriate tab for the connect type. You can accept the defaults on some of the tabs, but some fields must be filled in. These are validated when that connect method is selected. For example, if you select SNMP as the connect method for a device, and have not entered a value in the Device IP Address field, Cisco IP Manager issues an error. The dialog offers multiple tabs to fill out because elements can support multiple connect methods.
The General tab has three sections; two are for informational purposes only.
In the NETWORK_ELEMENT section, the Device Model field holds a value you enter for the name of the device. This field is functions as a reminder or comment, and is not validated. You can enter up to 16 characters in this field.
Similarly, the Device Description field is for informational purposes only. You can enter up to 30 characters in this field.
The remaining fields, in the Device Preferences section have effect.
Select one of the following choices from the Connect Method drop-down list:
Elements beneath a composite element in the tree have an additional connect method available:
Currently Cisco IP Manager supports only TFTP for SNMP devices. TFTP is used only for configuration upload and download operations; all other communications between the Cisco IP Manager and a router are Telnet or SNMP.
Select one of the following choices from the Storage Device drop-down list:
These devices are described in the element documentation.
If the selected device is a composite element, the appearance of the General tab is slightly different:
There are two extra fields:
This displays the number of slots you specified as described under "Creating a Composite Element."
Select one of the following choices from the Composite Type drop-down list:
If the selected device is a module element, the appearance of the General tab is again slightly different:
This is the slot number being displayed.
Same as described for "General Tab."
Same as described for "General Tab."
Same as described for "General Tab."
The Using Telnet-VTY to Access Device control group contains a single field:
The Timeouts/Retries control group contains two fields.
Both of these fields initially contain the value <default>. To see what the default values are, click on Configure TG in the Domain Properties dialog to see the TGS Server Properties dialog (as described under "Configure Telnet Gateway"). You can change these values here. If your entry is outside the permitted values, Cisco IP Manager issues an error message when you click Apply.
The Login Security control group specifies the level of authentication you wish.
Select one of the following choices from the Authentication drop-down list:
If you choose either Element Auth or CIPM then Element Auth, then the following fields appear for you to fill in:
Figure 5-13 shows the appearance of the dialog with Element Auth selected; Figure 5-14 shows the appearance of the dialog with CIPM Auth selected.
The Console tab displays the following control groups and fields:
The Using Communications Server control group contains the following fields:
The Timeout control group contains the following fields:
Both of these fields initially contain the value <default>. To see what the default values are, click on Telnet Gateway in the Domain Properties dialog to see the TGS Server Properties dialog (as described under "Configure Telnet Gateway"). You can change these values here. If your entry exceeds the permitted values, Cisco IP Manager issues an error message when you click Apply. If your entry is outside the permitted range, Cisco IP Manager issues an error message.
The Login Security control group contains the following fields:
Except for Device IP Address, the SNMP tab uses default values for its fields.
The SNMP tab has three sections.
The Using SNMP-VTY to Access Device control group contains a single field:
The Timeouts/Retries control group contains three fields.
The Security control group contains two fields.
All of these fields initially contain the value <default>. To see what the default values are, click on SNMP Gateway in the Domain Properties dialog to see the SGS Server Properties dialog (as described under "Configure SNMP Gateway"). You can change these values here. If a numeric entry exceeds the permitted values, Cisco IP Manager issues an error message when you click Apply. If your entry is less than the permitted values, Cisco IP Manager substitutes the minimum permitted value.
The SNMP Trap tab has three sections. Figure 5-17 shows the tab after one address has been moved from the Enter Trap Source IP Address field to the Trap Source IP Addresses List.
The SNMP Trap control group contains two buttons and two fields.
public.
loopback0.
The Trap Source IP Addresses List control group contains two fields and two buttons. To add addresses to the Trap Source IP Addresses List, enter them in the Enter Trap Source IP Address field, and then click the Add button. To remove addresses from the Trap Source IP Addresses List, highlight them and then click the Remove button.
The Advanced tab provides information only. Check boxes indicate whether the following properties are set:
In addition, if the element is locked, the tab shows what user locked it.
To actually make these changes, you right-click on the element (in the Element Manager window) and specify Lock State or Commission State.
Click the Verify button to initiate a connection with the device.
The results are displayed in the Response window. Use the Clear button to clear text from this window.
If the connection cannot be established (incorrect console password or IP address, for example), you receive a general error message.
If the connection can be established but there is an error in the device properties, you receive a more specific error message.
When you have set the properties, click the Apply button to save the data to the database but keep the Device Properties dialog open. Click the OK button to save the data to the database and close the window. Or, click the Cancel button to close the window without saving the changes you have made in the dialog.
importElement username password filename
All parameters are required
Identify elements by entering the device's properties into the text file in the following order:
If a required property is omitted, the element is skipped.
Use commas to separate variables, and new-line characters to separate elements. You can leave fields empty, but there must be a comma for each. Empty lines and lines beginning with the # character are ignored.
The following text file would add a virtual device called element_1, another device called element_2, which lists VTY as the connect method, and a device called element_3, which lists console as the connect method, to the domain myDomain:
element_1,myDomain,,Virtual Device,,,,,,,,,,, element_2,myDomain,,VTY, 1.2.3.4, cisco, sesame,,,,,,,,element_2.cfg element_3,myDomain,,Console,,,,,1.2.3.4,comm_srvr_user_id,comm_srvr_password,1,port_password,consol_password,/tmp/element_3.cfg
The importElement utility takes a Cisco IP Manager user name, password, and the name of the import file as arguments. If the user's login name is ipmgr_user, the password ipmgr_password, and the elements are listed in a text file called elements that is in the same directory as the importElement utility, then launch the script by entering the following on the command line:
./importElement ipmgr_user ipmgr_password elements
The domain myDomain must already exist in the Cisco IP Manager database, and the person launching the script (the user identified by ipmgr_user) must be a valid Cisco IP Manager user with permission to create elements in the domain myDomain.
If you are importing a large number of devices with this script, you should close all instances of the GUI application. As each device is added, the Cisco IP Manager servers attempt to update any GUI application that is open. This can consume significant resources and, if the number of devices is very large, the GUI could experience a significant event interruption.
To view the device's working config, right-click on the device name and select the Working Config command from the menu that appears. For a description of a working config, see the section "Working Config versus Running Config" in "Running the GUI."
The Working Config window opens, with the text of the working config displayed.
Working configs can be created or modified in any of three ways:
If you choose the Import button at the bottom of configuration File window, an Import Config window opens.
Once a network element exists in a domain and you have created a working config, you can use the floating options menu that opens when you right-click the mouse to manage the uploading and downloading of configurations. This can be done either from or to an individual device or from or to multiple devices.
The Download Options window opens.
Choose the destination of the download operation by clicking the Running Config, Startup Config, or Storage Device button in the Download To control group. Other options on the dialog are enabled or disabled according to your Download To selection.
If you are configuring a new router for the first time, select the Initialize checkbox. (To perform this operation, you must previously have selected the Console connect method in the General tab of the Element Properties dialog.) You can initialize a device only when the Running Config download option is selected; the checkbox is disabled if you are downloading to the Startup Config. If you check the Initialize option, the Use "configure terminal" Mode option is automatically checked (and that mode used) and the option grayed out. You then cannot uncheck this option if you are initializing a device.
Select any combination of the following checkboxes in the Options group:
When you are downloading to the startup configuration, only the following option is available:
When you have made your selections, click the OK button to download the working configuration to the device. The Download Status window opens.
Click the Show Errors button to filter out positive responses from the messages displayed. This allows you to focus on problems that need to be resolved. (Not everything is filtered out of the response window; start, stop, and summary messages about the download operation still appear.)
The Show All button reverts to the full display.
In the first part of the status report, the Cisco IP Manager GUI application reports that the NEMServer has successfully issued the Cisco IOS command Reload. This is followed by the subsequent information that the router has returned the message "The date and time must be set first." This is a fatal error, and the Cisco IP Manager adds the information that, though the command was successfully issued, the operation failed.
pslab-2505: Reload successful. pslab-2505: Additional IOS message after reload: -------------------------------------------------- IOS Reload command succeeded, but reload operation failed: "The date and time must be set first" -------------------------------------------------- Reload finished.
The message concludes with the information from the NEMServer that the Reload attempt is finished.
You should read all messages carefully to determine whether an operation was successfully completed.
You can download a configuration file to a storage device associated with an element by clicking the Storage Device button. When you select this option, the To Storage Device File and From Local Config File in Directory fields are enabled. Specify a file name in the To Storage Device File field; the configuration file is then downloaded to the specified storage device in the element. (You specified this storage device in the General tab of the Element Properties dialog, as shown earlier under "General Tab.") You can use any convenient name here, such as test.
The From Local Config File in Directory field specifies the source file name entry for the configuration file to be downloaded to the storage device. You can specify directly the file name to be downloaded or leave this field blank. If you leave this field blank, Cisco IP Manager selects the configuration file from the default directory or the selected directory, and appends the element name with .cfg (elementname.cfg). The specific name usually gets generated at the time of upload (if you enabled the option in the dialog to store the configuration file). You can use this procedure for group operations.
.cfg) in the selected directory.
Select the Download to Elements command. The Download Options window described previously opens. When you click the OK button, the working configurations for the selected devices download, with the results of each download operation recorded in the Download Status window.
You can halt the download process at any time, by choosing the Abort button at the bottom of this window. This terminates the download after completing the operation in progress. You cannot stop a download operation for a single element.
The messages in the window tell you whether the download operation succeeded or failed for each device.
cfg.
# or > (which are used by Cisco IOS as part of a prompt), an upload using non-TFTP transfer mode may result in only a partial configuration being uploaded. We recommend that you use the TFTP transfer mode in this case.
If you click the Storage Device button, the Storage Device File field is enabled; you can choose the name of a file stored in the storage device of the element. That could be the element's flash memory, or whatever other device you specified in the General tab of the Element Properties dialog, as shown earlier under "General Tab." You can use a name that you specified in "Download to Storage Device."
When you have set the options as desired, click the OK button to upload the configuration.
If you want to update the device's startup configuration from the working configuration, click the Update Startup Config before Reload checkbox before forcing the reload operation.
You can choose to reload after a specified interval of time (using the format specified in the dialog), at a specified time of the current day (using 24-hour notation in the hour field), or immediately, by choosing one of the following buttons:
Or, you can click the Cancel Reload button to cancel a previously set reload request.
Click the OK button to implement your selections.
A confirmation message appears. Click Yes to complete the operation.
Choose the Show tab on the Element Status window to execute a Cisco IOS Show command.
Select either Enable Mode or Normal Mode from the drop-down list, then click the Show button. The response is displayed in the Response window. For example, Figure 5-23 shows the results of the Show interfaces command.
trace [protocol] [destination]
where protocol is one of appletalk, clns, ip (the default), or vines, and destination is a destination (IP) address.
Enter a command into the field to the right of the Execute button, and then click the Execute button. The results of the command appear in the Response window. For example, Figure 5-25 shows the results of the dir flash: command (which shows all the files under flash).
To close the Element Status Window, click the OK button.
To view archive information about an element and to perform operations on stored configurations, right-click on the element and select the Archive Viewer option. For more about the operations you can perform, refer to "Archive Administration."
When you download a configuration, the Element Manager creates a new version to store in the archive; you can view each version, compare versions, and so on, as also described in "Archive Administration."
To delete a domain or an element, right-click on its name in the data tree and choose the Delete command from the floating menu that opens. Or, select multiple domains and devices then right-click on any one of the selected names and choose the Delete command. When deleting multiple items, a confirmation dialog is displayed; click the OK button to confirm. If the deleted items remain in the Element Manager window's data tree, choose the Refresh All command (or select the parent node and choose the Refresh Selection command) from the View menu.
A domain must be empty before you can delete it.
Posted: Mon Feb 14 13:44:14 PST 2000
Copyright 1989 - 2000©Cisco Systems Inc.