-
Administration of Cisco Prime LAN Management Solution 4.1
-
Preface
-
Open Source License Acknowledgements
-
Chapter 1: Overview of Administration
-
Chapter 2: Setting up Security
-
Chapter 3: Administering LMS Server
-
Chapter 4: Administering Discovery Settings and Device and Credential Repository
-
Chapter 5: Managing Groups
-
Chapter 6: Administering Data Collection
-
Chapter 7: User Tracking and Dynamic Updates
-
Chapter 8: Administering Collection Settings
-
Chapter 9: Monitoring and Troubleshooting Settings
-
Chapter 10: Notification and Action Settings
-
Chapter 11: Administering Change Audit and Software Management
-
Chapter 12: Managing Jobs
-
Chapter 13: Working With Software Center
-
Chapter 14: Discrepancies and Best Practices Deviations
-
Chapter 15: Report Setting
-
Chapter 16: Purge Settings
-
Chapter 17: Debugging Options
-
Chapter 18: Understanding LMS Tasks
-
Appendix A: CLI Tools
-
Appendix B: Troubleshooting and FAQs
-
Appendix C: Data Extraction Engine
-
Appendix D: Understanding Cisco Prime Security
-
Appendix E:Commands to Enable Mac Notification Traps
-
Appendix F: Recommended Best Practices
-
Index
-
Feedback
Table Of Contents
Configuring Default Job Policies
Defining the Default Job Policies
Configuring NetShow Job Policies
Purging Configuration Management Jobs
Enabling Approval and Approving Jobs Using Job Approval
Creating and Editing Approver Lists
Device Attributes Export File Format
Managing Jobs
In LMS 4.1, there is a Job Browser which enables you to view the status of all the LMS admin-related Jobs.
LMS applications, such as NetConfig, Config Editor, Archive Management, and Software Management allow you to schedule jobs to perform their tasks. Job Approval allows you to require that one of a group of users designated as job Approvers approves each job before it can run.
This section contains the following:
•
Configuring Default Job Policies
•
•
Using Job Browser
In LMS 4.1, there is a Job Browser which enables you to view the status of all the LMS admin-related Jobs.
The job details that you can view here include the job ID, the job type, the job status, the job description, the job owner, the time the job is scheduled to run at, the time of job completion, and the schedule type.
To open the job browser, select Admin > Jobs > Browser.
The Job Browser appears.
Table 12-1 displays the fields in the LMS Job Browser.
Filtering Jobs
You can filter the jobs by any specified criteria using the Filter by drop-down list. Select your criteria, enter the corresponding value in the text box next to the drop-down list and click Filter. The jobs pertaining to that category are displayed.
Click the Refresh icon to refresh the job browser. Use the Stop and Delete buttons to stop or delete jobs:
•
•
Note
Configuring Default Job Policies
Each Configuration Management job has properties that define how the job will run. You can configure a default policy for these properties that applies to all future jobs. You can also specify for each property whether users can change the default when creating a job.
You have the option of entering a username and password for running a specific Archive Management, Config Editor, NetConfig, or NetShow job.
If you enter a username and password, Archive Management, Config Editor, or NetConfig applications use this username and password to connect to the device, instead of taking these credentials from the Device and Credential Repository.
While the job is running, the password is retrieved from the Device and Credential Repository for each of the selected devices.
For example, if the TACACS server is managing the devices, the passwords in the TACACS server and the passwords in the Device and Credential Repository should be synchronized (with every password change).
This option of entering the username and password for running a job is useful in high security installations where device passwords are changed at frequent intervals. In such instances, the passwords may be changed every 60-90 seconds.
To use this option of entering a username and password for running a specific job, you should enable the job password policy for Archive Management, Config Editor, NetConfig, or NetShow jobs.
You can do this by using the Enable Job Password option in the Config Job Policies window.
If you have enabled Enable Job Password option, you can enter these credentials while scheduling a job:
•
•
•
This section also explains about Defining the Default Job Policies.
Defining the Default Job Policies
The following is the workflow for defining the default job policies for Configuration Management applications like NetConfig, ArchiveMgmt, ConfigEditor, Netshow:
Note
Step 1
The Config Job Policies dialog box appears.
Step 2
•
•
•
•
Step 3
Failure Policy
Select what the job should do if it fails to run on the device. You can stop or continue the job, and roll back configuration changes to the failed device or to all devices configured by the job.
You can select one of the options:
•
•
•
•
•
Note
You can create rollback commands for a job in the following ways:
•
Rollback commands are created automatically by the template.
The Banner system-defined template does not support rollback. You cannot create rollback commands using this template.
•
Allows you to enter rollback commands into the template.
When you use the Adhoc and Telnet Password templates, you cannot create rollback commands.
E-mail Notification
Enter e-mail addresses to which the job sends messages at the beginning and at the end of the job.
You can enter multiple e-mail addresses separated by commas.
Configure the SMTP server to send e-mails in the View / Edit System Preferences dialog box (Admin > System > System Preferences).
We recommend that you configure the E-mail ID in the View / Edit System Preferences dialog box (Admin > System > System Preferences).
When the job starts or completes, an e-mail is sent with the E-mail ID as the sender's address.
Notification is sent when the job is started and completed.
Notification E-mails include a URL to enter to display job details. If you are not logged in, do so using log in panel.
Sync Archive before Job Execution
The job archives the running configuration before making configuration changes.
Note
None.
Copy Running Config to Startup
The job writes the running configuration to the startup configuration on each device after configuration changes are made successfully.
Note
Does not apply to Catalyst OS devices.
Enable Job Password
The Job Password Policy is enabled for all the jobs.
The Archive Management, Config Editor, and NetConfig jobs use this username and password to connect to the device, instead of taking these credentials from the Device and Credential Repository.
These device credentials are entered while scheduling a job.
None.
You can use this option even if you have configured only the Telnet password (without configuring username) on your device.
You must enter a string in the Login Username field. Do not leave the Login Username field blank.
The Login Username string will be ignored while connecting to the device since the device is configured only for the Telnet password.
See Usage Scenarios When Job Password is Configured on Devices.
Fail on Mismatch of Config Versions
The job is considered a failure when the most recent configuration version in the configuration archive is not identical to the most recent configuration version that was in the configuration archive when you created the job.
Note
None.
Delete Config after download
The configuration file is deleted after the download.
Note
Execution Policy
Allows you to configure the job to run on multiple devices at the same time (Parallel execution) or in sequence (Sequential Execution).
If you select sequential execution, you can select Device Order in the Job Schedule and Options dialog box to set the order of the device.
1.
2.
•
Or
•
You cannot alter the device sequence for Archive Management application jobs such as Sync Archive, Check Compliance and Deploy, etc.
Sequential Execution is not supported for the following jobs:
•
•
•
User Configurable
Select this check box next to any field to make corresponding policy user configurable.
You can configure a user-configurable policy while defining job. You cannot modify non-user-configurable policies.
Step 4
A message appears,
Policy values changed successfully.Step 5
Usage Scenarios When Job Password is Configured on Devices
The following tables list the usage scenarios and their implications for Configuration application when job password is configured on devices.
•
Configuring NetShow Job Policies
Each NetShow job has properties that define how the job runs. You can configure a default policy for these properties that apply to all future jobs. For each job property you can specify whether users can change the default property when creating a job.
NetShow supports the following Job Policies:
•
The default job policies that NetShow support are E-Mail Notification, Enable Job Password, and Execution Policy.
•
The Job Purge option provides a centralized location for you to schedule purge operations.
You can define the protocol order for NetShow through the Protocol Ordering option in the Config Management feature in LMS.
This section also gives details on Masking Credentials
Defining Default Job Policies
NetShow supports E-Mail Notification, Enable Job Password, and Execution Policy.
Note
To define these default Job Policies:
Step 1
The Job Policy dialog box appears.
Step 2
Step 3
Step 4
A message appears,
Policy values changed successfully.Step 5
Purging Configuration Management Jobs
The Job Purge option provides a centralized location for you to schedule purge operations for certain Configuration Management jobs including NetShow jobs.
Select Admin > Network > Purge Settings > Config Job Purge Settings to invoke the Job Purge option.
The Job Purge window contains the following information:
To purge Configuration Management Jobs:
Step 1
The Job Purge dialog box appears. You can perform the following tasks in the Job Purge window:
Defining Protocol Order
You can define the protocol order for NetConfig, Archive Mgmt, Config Editor, and NetShow through the Protocol Ordering option in the Config Management feature in LMS.
Note
To define the protocol order for NetShow:
Step 1
The Transport Settings dialog box appears.
Step 2
Step 3
NetShow supports only Telnet and SSH.
If you want to remove a protocol or change the protocol order, you can remove the protocol using the Remove button and then add it again.
The protocols that you have selected appear in the Selected Protocol Order pane.
Step 4
A message appears,
New settings saved successfully.Step 5
The protocol used for communicating with the device is based on the order in which the protocols are listed here.
Masking Credentials
You can mask the credentials shown in the output of show commands. If you want to mask the credentials of a particular command, you must specify the command in the NMSROOT\MDC\tomcat\webapps\rme\WEB-INF\classes\com\cisco\nm\rmeng\config\netshow\NSCredCmds.properties file.
In this file you can specify all the commands whose output should be processed to mask the credentials. We recommend that you enter the complete command in the file. For example, you must enter show running-config, not show run. This file contains some default commands like show running-config.
Enabling Approval and Approving Jobs Using Job Approval
LMS applications, such as NetConfig, Config Editor, Archive Management, and Software Management allow you to schedule jobs to perform their tasks. Job Approval allows you to require that one of a group of users designated as job Approvers approves each job before it can run.
See Job Approval Workflow for more information.
Job Approval sends job requests through e-mail to users on a job's Approver list. If none of the Approvers approve the job before its scheduled run time, or if an Approver rejects the job, the job is moved to the rejected state and will not run.
When Job Approval is enabled, applications that use it, require you to schedule the job to run in the future, rather than immediately. Job approval cannot be enabled for jobs that run immediately.
A user with the appropriate privileges uses a Cisco Prime application to schedule jobs.
When you use Job Approval, different people can perform different tasks:
Note
System Administrator
Creates and maintains the Approver lists
Approver
Approves/rejects a job, or changes the schedule for a job.
To select the log level settings for the Job Approval application, select Admin > System > Debug Settings > Config and Image Management Debugging settings.
Job Approval is also referred to as Maker Checker in a few places within LMS. For example, in Loglevel Settings and Permission Report (Reports > System > Users > Permission) it is mentioned as Maker Checker.
Job Approval Workflow
A typical job approval workflow may look like this:
A system administrator does the following:
1.
2.
3.
4.
The planner analyzes the network and prompts the network engineer to schedule a job to perform a needed network change.
The job creator uses a Cisco Prime application to create a job.The application must have an Approver list assigned to it before Job Approval is enabled. Also, it must be scheduled to run in the future (not immediately).
All Approvers on the Approver list receive an automatic email notification. The job Approvers approve or reject the job (see Approving and Rejecting Jobs) and give their comments.
The job creator and all Approvers on the Approver list receive an automatic e-mail notification.
A job that is not approved or rejected before its scheduled time is automatically moved to the Rejected state. E-mail notification is sent to all Approvers and the user who scheduled the job. If the job is approved, it runs as scheduled.
Specifying Approver Details
Use the option, Approver Details, to maintain information about users with Approver roles.
Note
To specify Approver details:
Step 1
The Approver Details dialog box appears.
Step 2
All the approvers in with valid E-mail IDs, will appear in theApprovers list. The E-mails of the approvers will be the same as that added in LMS.
(You can create a valid Cisco Prime user using the Local User Setup option under Admin > System > User Management > Local User Setup).
If you want to change the E-mail ID of any of the Approvers, select the Approver from the Approvers list, and change specifying the new e-mail ID in the E-mail Address field. You can add more than one e-mail, separated by commas
Step 3
All approvers, have to be manually added to LMS.
To do this, enter the name of the Approver that you want to add in the New Approver field, enter a valid e-mail ID for that user in the E-mail Address field, and click Save.
The Approver that you added, appears in the Approvers box.
Creating and Editing Approver Lists
You can use the option Create/Edit Approver Lists to create, edit, or delete Approver lists. Before you create an Approver list, ensure that users have been added, through the Approver Details option (see Specifying Approver Details).
Note
To create and edit Approvers lists:
Step 1
The Create/Edit Approver List dialog box appears.
Step 2
Step 3
A message appears:
ListListname has no users. To save the list successfully, add users and click Save.Step 4
The newly-created list appears in the lists box.
(If previously-created lists exist, you can highlight a list to see the List Members in the Users group of fields.)
Step 5
In the Users group of fields, the Available Users box lists users who have Approver permissions. Only these users can be added to Approver lists to approve jobs.
•
The name appears in the List Members list box.
•
The name is removed from the List Members list box.
Step 6
The Approver Lists box displays the name of the new Approver list and the users on this list appear in the box below Approver Lists.
To edit an Approver List:
a.
The approvers of the list appear in the List Members list box.
b.
To delete an Approver List:
a.
b.
A message appears:
Are you sure you wish to delete? Approval will be disabled for applications to which theListname is assigned!c.
Assigning Approver Lists
You can assign an Approver list to each of the LMS applications, from the available Approver lists.
Note
To assign an Approver list:
Step 1
The Assign Approver Lists dialog box appears.
Step 2
Step 3
The selected Approver lists are assigned to the applications.
Setting Up Job Approval
The Approval Policies dialog box allows you to set up Job Approval for all applications for which you can set up job approval. The applications are:
•
•
•
•
•
Prerequisite
Make sure the approver list is assigned to the application, before you enable approval for the application.
Note
To set up Job Approval:
Step 1
The Approval Policies dialog box appears. You can enable or disable Job Approval for the following applications:
•
•
•
•
•
Step 2
•
•
•
•
Step 3
After you enable Job Approval, two additional fields appear in the job schedule wizard of the applications. These are:
•
•
Using Job Approval for Archive Management
You can enable Job Approval for Archive Management tasks, (Admin > Network > Configuration Job Settings > Approval Policies). This means all jobs require approval before they can run.
Only users with Approver permissions can approve Archive Management jobs. Jobs must be approved before they can run if Job Approval is enabled on the system.
For more details on enabling job approval see Setting Up Job Approval.
The following Archive Management tasks require approval if you have enabled Job Approval:
Out-of-Sync (Configuration > Compliance > Out-of-Sync Summary)
Sync Archive jobs do not have Job Approval enabled because this job only archives the configuration from the device and there is no change to the device configuration.
If you have enabled Approval for Archive Management tasks, these options appear in the Job Schedule and Options dialog box:
•
•
Using Job Approval for Software Management
You can enable Job Approval for Software Management tasks, (Admin > Network > Configuration Job Settings > Approval Policies) which means all jobs require approval before they can run.
Only users with Approver permissions can approve Software Management jobs. Jobs must be approved before they can run if Job Approval is enabled on the system.
The following Software Management tasks require approval if you have enabled Job Approval:
•
–
–
–
–
•
–
–
–
–
If you have enabled Approval for Software Management tasks, then in the Job Schedule and Options dialog box, you get these two options:
•
•
Approving and Rejecting Jobs
Use the Approve or Reject Jobs option to approve or reject a job for which you are an Approver. The job will not run until you or another Approver approves it. If no Approver approves the job by its scheduled run time, or an Approver rejects it, the job is moved to the rejected state and will not run.
For periodic jobs, only one instance of the job needs to be approved. If one instance is approved all other instances are considered approved, and vice-versa.
When a job for which you are an Approver is created, you are notified by email.
An Approver can edit the job schedule at the time of approving the job.
The e-mail displays these details:
View the Permission Report (Reports > System > Users > Permission) to check whether you have the required privileges to perform this task. You need to be a user with an Approver role.
Note
To approve or reject jobs:
Step 1
The Jobs Pending Approval dialog box appears with the following information about the scheduled jobs on the system:
You can filter the pending jobs by any specified criteria using the Filter By drop-down list. Select your criteria and click Filter.
Step 2
•
The job is approved.
Or
•
The Job Details dialog box appears (For example, if the ID of the job awaiting approval is 1025, then the title of the dialog box appears as Job Details For Job 1025). You can view/ change the job details before approving or rejecting it.
Fields in the Job Details box are:
Step 3
The job is approved.
If you want to reject the job, enter comments in the Comments text box and then click Reject.
Using Device Selector
The Device Selector pane is used to select devices to perform LMS tasks. This pane lists all devices in a group. The devices are listed in the appropriate groups based on Device type groups and User-defined group rules.
The devices name that you see in this pane is the Display Name that you have entered at the time of adding the devices in Device and Credential Repository.
You can use the following search options to search for devices:
Note
The Device Selector pane contains the following field/buttons:
Search Input
Enter the search expression in this field.
You can enter single device names or multiple device names. If you are entering multiple device names, separate them with a comma. You can also enter the wildcard characters "*" amd "?".
For example: 192.168.10.1*, 192.168.20.*
Search
Use this icon to perform a simple search of devices based on the search criteria you have specified in the Search Input text field.
For information on Search, see Using Simple Search.
Advanced Search
Use this icon to perform an advanced search of devices based on the search criteria you have specified in the Search Input text field.
For information on Advanced Search, see Using Advanced Search.
All
Lists all User-defined and System-defined groups for all applications that are installed on LMS Server.
For more information, see Using the All Tab.
Search Results
Displays all the search results from Search or Advanced Search.
For more information, see Using the Search Results Tab.
Selection
Lists all the devices that you have selected in the Search Results or All tab.
Using this tab, you can deselect devices from the list.
For more information, see Using the Selection Tab.
Figure 12-1 shows the new device selector.
Figure 12-1 Device Selector
Tool-tips are provided for long device names so that you do not have to scroll to see the complete device name.
Using Simple Search
You can search for devices by entering the devices name (Display Name) in the Search Input field.
The search is based on the Display Name that you view in the Device Selector pane. This Display Name is entered when you add devices to Device and Credential Repository.
Usage Notes
The following are the usage notes for Simple Search:
•
For example:
You can enter device names in these many ways to select multiple devices:
–
–
–
You cannot enter multiple wildcard characters for selecting the devices
For example, 192.*.80.*. This is not allowed.
•
–
–
•
•
For example:
If you have these devices in All Devices and Normal devices nodes: 192.168.10.10, 192.168.10.20, 192.168.10.21, 192.168.10.30, and 192.168.10.31 then,
a.
b.
c.
•
Using Advanced Search
You can use the Advanced Search icon to specify a set of rules for advanced search. Advanced search is based on the Grouping Services attributes of Grouping Services Server. In the Advanced Search dialog box, you can create rules to search for devices.
Figure 12-2 shows the Advanced Search dialog box.
Figure 12-2 Device Selector Advanced Search
This dialog box contains the following fields and buttons (See Table 12-6):
Usage Notes
The following are the usage notes for Advanced Search:
•
•
Each rule expression contains the following:
object type.variable operator value
Object Type—The type of object (device) that is used to form a group. All rule expressions begin with the same Object Type, RME:INVENTORY:Device.
Variable—Device attributes, based on which you can define the group. See the Advanced Search Rule Attribute.
Operator—Operator to be used in the rule. The list of possible operators changes based on the Variable selected.
Value—Value of the rule expression. The possible values depend upon the variable and operator selected. Depending on the operator selected, the value may be free-form text or a list of values.
•
object type.variable operator value
•
You must use Check Syntax button only when you add a rule manually or when you modify a rule expressions in the Rule Text.
•
•
•
Advanced Search Rule Attribute
Table 12-7 lists the available device advanced search rule attributes that you can use for defining advanced search.
Using Advanced Search—An Example
The following example describes the procedure for selecting devices whose IP address starts with 192.168 or Network Mask is 255.255.255.0. Also, these devices are assumed to be in Normal state.
The devices in your network are:
•
•
•
•
•
Use the following procedure for advanced search:
Step 1
The Define Advanced Search Rule dialog box appears.
Step 2
a.
b.
c.
Step 3
The rule is added into the Rule Text.
Step 4
a.
b.
c.
d.
Step 5
The rule is added into the Rule Text.
Step 6
a.
b.
c.
d.
Step 7
The rule is added into the Rule Text.
Step 8
The Device Selection dialog box appears.
The devices that satisfied the search condition are selected. That is these two devices are selected.
•
•
•
Using the All Tab
The All tab lists all the devices that are available in the LMS. The list is based on the Display Name that you entered in the Device Properties dialog box when you added devices to Device and Credential Repository.
List of Device Folders
The following is the list of device folders under the All tab:
•
•
•
•
•
Only one Saved device list is created within the device selector. If concurrent users have created Saved device list, only the last created Saved device list appears in the Device Selector. The previous Saved device list is overwritten with the latest.
Note
•
•
For example: For Cisco Prime Common Services, you will see:
CS@CiscoWorks_ServerHostName.
In a stand-alone system, server name is not appended. For example, for Common Services, you will see CS.
•
•
For example: If you have devices, A, B, C and D in Cisco Prime Common Services and you have devices A, B, and C in LMS then in the Device Selector under Common Services device folder, you will view on device list, A, B, and C.
•
–
–
There are two types of device selectors in LMS:
Single Device Selector
In the single device selector, you can select a device only at the leaf-level (device-level). The radio buttons at the node-level (folder-level) are grayed out.
Multiple Device Selector
In the multiple device selector, you can select devices at both the node-level and leaf-level.
The following are the usage notes for the multiple device selector:
•
For example, if you select the All Devices node, all devices under this node are selected.
•
For example, if you expand the All Devices node, you cannot select devices at the All Devices node-level (the check-box is grayed out). You need to select devices individually under the All Devices node.
•
For example, if you select the Normal Devices node and expand the same, you can deselect the devices only at the leaf-level. You cannot deselect all the devices at the Normal Devices node-level (the check-box is grayed out), when it is expanded. However, you can use Clear All to deselect all the devices.
•
For example, you can select the Previous selection and the Saved device list nodes together to perform the tasks.
Using the Search Results Tab
The Search Results Tab lists all the results of Simple search or advanced search operations. It displays a flat list of devices and you can do a select all , clear all , or select a few devices from the list.
Using the Selection Tab
The Selection Tab serves as a repository of all the devices that you select from the Search Results tab or the All Tab.
There are three ways to select devices in the Device Selector:
•
Selection Using All Tab
You can select devices using the tree view in the All tab. This tab displays all devices that are available in LMS.
Selection Using Search
You can search devices using Search or Advanced Search. The list of devices matching the search criteria is shown under the Search Results tab. You can select the required devices from the Search Results tab. The Selection tab reflects whatever you selected from Search Results.
If you click the All tab now, the devices selected from Search Results will be shown in the All Devices group.
Selection Combining All and Search
After you select devices using the All tab, you can add a few more devices using Search. You can enter the search criteria and search using Search or Advanced Search and the Search Results tab displays the devices matching the criteria.
You can select the required devices from the Search Results tab. The Selection tab displays the accumulated list from both All and Search Results tabs. If you click the All tab, it displays the selected devices from Search Results under the All Devices group also.
You can enter another search criteria and select more devices. The selected devices are accumulated in the All tab from the Selection tab, as you select more devices.
Note
Editing Device Attributes
To edit the device attributes for a single device
Step 1
The Edit Devices dialog box appears.
Step 2
Step 3
The Device Attributes dialog box appears.
Step 4
The Device Attributes Information dialog box appears.
Step 5
Step 6
You can check the Apply to all Devices checkbox to apply the device attributes of one device to all other devices that are listed in the Devices pane.
Step 7
Step 8
To edit the device attributes for the bulk of devices
Step 1
The Devices dialog box appears.
Step 2
Step 3
The Device Attributes dialog box appears.
Step 4
The Export Device Attributes to File dialog box appears.
a.
or
–
The Server Side File Browser dialog box appears.
–
–
b.
The notification window displays
Data exported successfully.c.
Step 5
You can edit only the device attributes, Serial Number, SNMP Retry, SNMP Timeout, Telnet Timeout, and Natted IP Address. You cannot edit the Device Display Name (device_identity) and add new device entries.
See Device Attributes Export File Format for more information.
Step 6
The Import Device Attributes to File dialog box appears.
We recommend that you import the same file that you have exported after editing. If any new device entries are added, these device entries are ignored. Only device entries that match the existing device entries are imported.
a.
or
–
The Server Side File Browser dialog box appears.
–
–
b.
The notification window displays
Data imported successfully.c.
The Device Attributes window refreshes to display the updated device attributes.
While importing the edited device attributes file an error message may appear,
Attribute values for some selected devices are invalid. See Attribute Error Report for details.See Editing Device Attributes section to know the minimum and maximum values for the device attributes. Also see Attribute Error Report for more information.
Step 7
The Devices window appears.
The device attributes are:
•
Display name of the device.
•
Cisco manufacturing serial number from chassis. You can enter alphanumeric characters up to 255.
The default value is Default Not Defined.
This attribute is available when you either export or edit the device attributes from the Devices window.
•
Number of times that the system should try to access devices with SNMP options.
The default value is 2. The minimum value is zero.
•
Duration of time that the system should wait for a device to respond before it tries to access it again.
The default value is 2 seconds. The minimum value is zero seconds. There is no maximum value limit.
Changing the SNMP timeout value affects inventory collection.
•
Duration of time that the system should wait for a device to respond before it tries to access it again.
The default value is 36 seconds. The minimum value is zero seconds. There is no maximum value limit.
Note
•
The server ID. This is the translated address of server as seen from the network where the device resides.
This is used when LMS tries to contact devices outside the NAT boundary, you need to enable support for NAT.
The default value is Default Not Defined.
•
Duration of time that the system should wait for a device to respond before it tries to access it again.
The default value is 5 seconds and the minimum value is 0 seconds. There is no maximum value limit.
This attribute is available only when you edit the device attributes from the Device Attributes window.
Do any one of the following to edit the device attributes:
•
•
Note
Attribute Error Report
The Attribute Error report is generated when the attribute values imported for some selected devices are invalid. This error occurs when the device attributes that are imported as a CSV file contain invalid attributes.
You can click on the Attribute Error Report link that is displayed in the error message, to open the Attribute Error Report.
You can also view the Attribute Error Report by clicking on the Attribute Error Report button from: Admin > Collection Settings > Inventory > Edit the Inventory, Config Timeout, and Retry settings > Edit Device Attributes
Note
Device Attributes Export File Format
The device attributes are exported in CSV 3.0 format. The exported file format is:
; This file is generated by DM Export utility
Cisco Systems NM Data import, Source=DM Export; Type=DMCSV; Version=3.0
;
;Start of section 0 - DM Export
;
;HEADER: device_identity,serial_number,SNMPRetryCount,SNMPTimeout,TelnetTimeout,RMEId
;
192.168.8.4,Default Not Defined,2,2,36,Default Not Defined
;End of CSV fileWhere,
•
device_identity—Display name of the device as entered in Device and Credential Repository.•
serial_number—Cisco manufacturing serial number from chassis. You can enter 0 to 255 alphanumeric characters. The default value isDefault Not Defined.•
SNMPRetryCount—Number of times, system should try to access devices with SNMP options. The default value is 2. The minimum value is zero.•
SNMPTimeout—Duration of time the system should wait for a device to respond before it tries to access it again. The default value is 2 seconds. The minimum value is zero seconds. There is no maximum value limit.Changing the SNMP timeout value affects inventory collection.
•
TelnetTimeout—Duration of time the system should wait for a device to respond before it tries to access it again. The default value is 36 seconds. The minimum value is zero seconds. There is no maximum value limit.•
Natted IP Address—server ID. This is the translated address of server as seen from the network where the device resides. This is used when LMS tries to contact devices outside the NAT boundary. The default value isDefault Not Defined.
