Table Of Contents
Managing Device and Credentials
Using the Device and Credential Admin
Importing Devices and Credentials
Exporting Devices and Credentials
Administering Device and Credential Repository
Master-Slave Configuration Prerequisites
Changing the Mode to Standalone
Sample CSV 3.0 File for Auto Update Server Managed Devices
Sample CSV 3.0 File for Cluster Managed Devices
Mapping CSV 2.0 to CSV 3.0 Fields
Sample XML File for Auto Update Server Managed Devices
Sample XML File for Cluster Managed Devices
Using DCR Features Through CLI
Viewing the Current DCR Mode Using dcrcli
Changing DCR Mode Using dcrcli
Implications of ACS Login Module on DCR
Managing Device and Credentials
The Device and Credential Repository (DCR) is a common repository of devices, their attributes, and credentials, meant to be used by various network management applications. The Device and Credential Admin (DCA) provides an interface to administer DCR.
DCR helps multiple applications share device lists and credentials using a client-server mechanism, with secured storage and communications. The applications can read or retrieve the information. The applications can also update the information in DCR so that the updated information could be shared with other applications.
DCR provides:
•
A central place where you can add or import new devices.
•
•
•
•
DCR also:
•
•
•
•
•
•
Credentials are values that are used by applications to access and operate on devices. It is typically an SNMP community string or a user ID and password pair. A device credential is used to access a managed device such as a switch or router
Device attributes are unique to each device and they identify a device. The following attributes are stored in the repository:
The mandatory attributes are:
•
•
Individual applications interact with the repository to get the device list, device attributes, and device credentials.
The following credentials can be associated with a device in DCR:
DCR supports Cisco Cluster Management Suites, Auto Update Servers and the managed devices using a mix of standard and additional attributes and credentials.
•
•
–
–
•
–
–
–
•
–
–
DCR Architecture
The sharing of device list and credentials among various network management products is achieved through a Client-Server mechanism. The clients are network management applications that use DCR. The server is called the DCR Server.
DCR works based on a Master-Slave model. DCR Server can also be in Standalone mode.
Master DCR
The Master DCR server refers to the master repository of device list and credential data. The Master hosts the authoritative, or a master-list of all devices and their credentials. All other DCRs in the same management domain which are running in Slave mode normally shares this list.
There is only one Master repository for each management domain, and it contains the most up-to-date device list and credentials.
Slave DCR
The Slave DCR refers to a repository that is an exact replica of the Master.
DCR Slaves are slave instance of DCR in other servers and provide transparent access to applications installed in those servers.
Any change to the repository data occurs first in the Master, and those changes are propagated to multiple Slaves. There can be more than one Slave in a management domain.
The Slave:
•
•
•
Standalone DCR
In Standalone mode, DCR maintains an independent repository of device list and credential data. It does not participate in a management domain and its data is not shared with any other DCR. It does not communicate with or contain registration information about any other Master, Slave, or Standalone DCR.
DCR running in Master or Slave mode always has an associated DCR Group ID that indicates the Server's management domain. This Group ID is generated when a DCR is set to Master mode, and communicated to all Slaves later assigned to that Master.
Using the Device and Credential Admin
Device and Credential Admin (DCA) helps you in:
•
Managing Devices
The Device Management option in DCA helps you manage the list of devices and their credentials. Device Management helps you in:
•
•
To perform any of these management functions, select:
Common Services > Device and Credentials > Device Management.
Adding Devices
You can use this feature to add devices, device properties or attributes, and device credentials to the DCA.
To add devices to the device list:
Step 1
The Device Management page appears.
The Device Management UI helps you perform operations on Standard Devices, Cluster Managed devices and Auto Update devices. Operations on Auto Update Servers can be performed only at the Auto Update Server Management UI.
The Device Summary window displays the devices and groups in DCA.
Step 2
The Device Properties page appears. The Device Information dialog box provides three device management types:
Standard Type
You can add Routers, Switches, Hubs, and other devices using the Standard management type.
To add devices and credentials using Standard type:
Step 1
Step 2
To select the Domain Name and the DeviceType, click Select and choose from the list.
DCR uses a device record to represent a Cluster. A Cluster can be added in the Standard Management option by selecting the Device Type field as Cisco Cluster Management Suite.
DSBU Clusters added this way, can then be selected in Cluster Managed Type, for the field Cluster.
Step 3
The device is added to the Added Device List in the window.
To remove the device from the Device List, select the device and click Remove from List.
Step 4
The Standard Credentials page appears.
Step 5
•
•
•
•
Step 6
The Standard UDF dialog box appears.
Step 7
DCA provides the option to define four attribute fields for a device. These fields are used to store additional user-defined data for the device.
The attribute fields that appear here can be changed at Device and Credentials > Admin > User Defined Fields.
Auto Update Type
You can use this feature to add, edit, and delete devices managed using Auto Update Server. The CiscoWorks Auto Update Server is a web-based interface for upgrading device configuration files and software images on firewalls that use the auto update feature.
The Auto Update Server managed device has its own attributes and credentials just like normal devices in DCR. In addition, it will have the following attributes:
•
•
To add devices and credentials using Auto Update type:
Step 1
Step 2
To select Auto Update Server, Domain Name, and the Device Type click Select and select from the resulting popup windows. For Auto Update Server managed devices, Display Name and Device-Identity are enough for identity.
DCR uses a device record to represent an Auto Update Server. An Auto Update Server can be added in the Auto Update Server Management UI. Auto Update Server added this way can then be selected for the field Auto Update Server.
Step 3
The device gets added to the Added Device List in the window.
To remove the device from the Device List, select the device and click Remove from List.
Step 4
The Credential Template dialog box appears.
Step 5
The User Defined Fields dialog box appears.
Step 6
You can define four attribute fields for a device. These fields are used to store additional user-defined data for a device.
The attribute fields that appear here can be changed at Device and Credentials > Admin> User Defined Fields.
Cluster Managed Type
DCR supports Cisco Clusters and their member devices using a mix of standard and additional attributes and credentials.
To add devices and credentials using Cluster Managed type:
Step 1
Step 2
The Member Number field is mandatory. The Member Number is the number of the Cluster member. This number represents the order in which the device is added into the cluster.
Also, Cluster needs to be added before a Cluster Managed device.
For example, if a device X belongs to cluster Y, first add the Cluster Y, and then add the Cluster Managed device X.
Step 3
The device is added to the Added Device List in the window.
To remove a device from the Device List select the device and click Remove from List.
Step 4
The Cluster Manager credentials dialog box appears.
Step 5
The User Defined Field dialog box appears.
Step 6
You can define four attribute fields for a device. These fields are used to store additional user-defined data for the device.
The attribute fields that appear here can be changed at Device and Credentials > Admin > User Defined Fields.
Deleting Devices
You can delete device information from DCR using this feature.
When a device is deleted, it will also get deleted in all the applications that use DCR.
To delete devices:
Step 1
The Device Management page appears.
Step 2
The device is removed from the device list. Also, all information about the selected device will be removed from DCR.
Editing Device Credentials
You can edit device information using this feature.
To edit device information:
Step 1
The Device Management page appears.
Step 2
The Device Properties page displays the Devices Information dialog box.
You can edit the attributes of individual devices here. The Devices column lists all the selected devices.
From the Devices column, you should separately select each device that needs to be edited, and make the required changes.
Step 3
The current attributes are automatically populated in the device information fields.
Step 4
If you are done with your editing and do not want to proceed, click Finish.
Step 5
The Credential Template dialog box appears. According to your requirement, you can edit:
•
•
•
•
•
Any changes made here will apply to all devices selected in Step 2. This has one exception.
If in Step 2, devices belonging to different device management types are selected, the changes made will apply only to devices of the appropriate type. That is, if a standard-device credential is changed, only the standard devices selected in Step 2 are affected.
If you have completed editing, and do not want to proceed, click Finish.
Step 6
The User Defined Fields dialog box appears. Make the required changes in the user-defined fields, and click Finish.
The changes made here will apply to all devices selected in Step 2 (irrespective of the device management type).
Auto Update Servers cannot be edited here. Even if they are selected in Step 2, they will not be affected. See "Editing Auto Update Server" section for details on editing Auto Update Server information.
Also, you cannot change the device management type using the edit flow. That is, a standard device cannot be changed to a Cluster device.
Importing Devices and Credentials
You can import device lists, device properties or attributes and device credentials to the DCR and populate DCR using this feature.You can:
or
Import Using DCA Interface
To import devices using DCA Interface:
Step 1
The Device Management page appears.
Step 2
The Import Devices popup window appears. You can import from any of the following:
•
•
•
Importing From a File
To import from a file:
Step 1
Or,
Browse the file system and select the file using the Browse tab.
Step 2
Only CSV2.0 and CSV3.0 file formats are supported.
Step 3
•
•
Step 4
a.
You can schedule importing the devices immediately or schedule the import for a later time. The scheduling can be periodic (daily, weekly, or monthly) or for a single instance.
b.
Step 5
Step 6
Importing From Local NMS
To import from Local NMS:
Step 1
HPOV6.x and Netview7.x are supported.
Step 2
Step 3
Step 4
a.
You can schedule importing the devices immediately or schedule the import for a later time. The scheduling can be periodic (daily, weekly, or monthly) or for a single instance.
b.
Step 5
Step 6
Importing From Remote NMS
You should have permissions to log into the remote network management system (NMS), without a password. Common Services uses remote login to log into the Server and get device details.
The rhosts file should be modified to enable you to login without a password.
To import from a remote NMS:
Step 1
If you select ACS, enter:
•
•
•
•
Step 2
Step 3
Step 4
Step 5
a.
You can schedule importing the devices immediately or schedule the import for a later time. The scheduling can be periodic (daily, weekly, or monthly) or for a single instance.
b.
Step 6
Step 7
Exporting Devices and Credentials
You can use this feature to export a list of device and their credentials into a file. The device list can be obtained from the device selector, or from a CSV file.
You can edit the Export Format file located at NMSROOT\objects\dcrimpexp\conf\Export_Format_CSV.xml or Export_Format_XML.xml to specify the credentials you need to export.
To see the list of attributes that can be exported:
Step 1
Step 2
Step 3
The list of attributes and their description is displayed. You can include the attributes you need to export, in the Export Format file.
You can:
or
Export Using DCA Interface
To export device credentials using DCA Interface:
Step 1
The Device Management page appears.
Step 2
The Device Export dialog box appears.
You can use either of the following device selection methods:
•
Select this option if you want to export devices from DCR to the file you specify in the Output File Information field. You can select the required devices from the Device Selector pane of the Device Export dialog box.
•
Select this option if you want to export devices from a CSV file that is already present in the server, to the file you specify in the Output File Information field.
You can use this option when the CSV file contains only partial device credentials, and you want to get the full list of credentials. The input CSV file checks for data in DCR, and exports the data to the output file.
We recommend that you use this option to export upto a maximum of 1000 devices.
Selecting From Device Selector
To select from device selector:
Step 1
Or
Browse the file system and select the file using the Browse tab.
Step 2
Step 3
Step 4
a.
You can schedule export immediately or schedule the export for a later time. The scheduling can be periodic (daily, weekly, or monthly) or for a single instance.
b.
Step 5
Step 6
Getting Device List From File
To get device list from file:
Step 1
Step 2
Step 3
Step 4
a.
You can schedule export immediately or schedule the export for a later time. The scheduling can be periodic (daily, weekly, or monthly) or for a single instance.
b.
Step 5
Step 6
You must populate DCR with devices before you export credentials from DCR selecting devices from a file.
Excluding Devices
This feature allows you to specify a file that contains the list of the devices that should not be added to DCR using the Add or Import operations.
During Add or Import operations, DCR makes sure that the device being added or imported is not listed in the Exclude Device List.
A device can be excluded based on it's hostname+domainname, IP address and device-identity fields.
To exclude devices from Add or Import operations:
Step 1
The Device Management page appears.
Step 2
The Upload Exclude Devices File dialog box appears.
Step 3
The file that needs to be uploaded must be in CSV format.
Step 4
A Sample CSV Exclude File
; This file is generated by DCR Export utilityCisco Systems NM Data import, Source=DCR Export; Type=DCRCSV; Version=3.0;;Start of section 0 - Basic Credentials;;HEADER: management_ip_address,host_name,domain_name,device_identity,display_na me,sysObjectID,dcr_device_type,mdf_type,snmp_v2_ro_comm_string,snmp_v2 _rw_comm_string,snmp_v3_user_id,snmp_v3_password,snmp_v3_engine_id,snm p_v3_auth_algorithm,primary_username,primary_password,primary_enable_p assword;,Dev1Hostname,,10.1.0.60,,,,,,AUSID1,Dev2Hostname,cisco.com,;;Start of section 2 - AUS managed;;HEADER: aus_device_identity,parent_aus_id;,;End of CSV fileViewing Devices List
You can view the devices in the Device List Report using this feature.
To view devices in the Device List Report:
Step 1
The Device Management page appears.
Step 2
The Device List Report dialog box appears.
Step 3
Step 4
Generating Reports in DCA
You can use this feature to generate and view Device and Credential Admin reports.
To generate reports:
Step 1
The Report Generator page appears.
Step 2
You can select any of the following reports:
•
•
•
•
•
Step 3
You can export the report, or print the report.
To export the report:
Step 1
Step 2
Step 3
Managing Auto Update Servers
Auto Update Servers have the following credentials:
•
•
•
Auto Update Server management feature helps you in:
Adding Auto Update Server
To add Auto Update Server:
Step 1
The Auto Update Server Management page appears.
Step 2
The Auto Update Server dialog box appears.
Step 3
DCR uses a device record to represent a Auto Update Server.
An Auto Update Server added in the Auto Update Server Management UI can be selected for the field Auto Update Server when you add devices using the Auto Update management type.
Step 4
Editing Auto Update Server
To edit Auto Update Server:
Step 1
The Auto Update Server Management page appears.
Step 2
The Auto Update Server dialog box appears.
Step 3
Step 4
Deleting Auto Update Server
To delete Auto Update Servers:
Step 1
The Auto Update Server Management page appears.
Step 2
Step 3
Administering Device and Credential Repository
The DCA Admin feature allows you to do the following tasks:
To perform these tasks, select CiscoWorks Homepage > Device and Credentials > Admin. The Admin page appears with the current DCA settings.
You can change the Mode Settings or modify User Defined fields.
Changing DCR Mode
To change Mode Settings:
Step 1
The Admin page appears with the current DCA settings.
Step 2
The Mode Settings window appears.
Step 3
The DCR Mode dialog box appears. You can select the required mode from this dialog box.
•
Master-Slave Configuration Prerequisites
Before you set up the Master and Slave, you have to perform certain tasks to ensure that secure communication takes place between the Master and Slave.
If machine M is to be the Master and S is to be the Slave:
Step 1
See "Setting up Peer Server Account" section for details.
Step 2
See "Setting up System Identity Account" section, for details.
Step 3
See "Creating Self Signed Certificate" section, for details on creating Self-Signed Certificate.
See "Setting up Peer Server Certificate" section, for details on copying Peer Certificate.
Step 4
Changing the Mode to Standalone
Step 1
Step 2
The default DCR mode is Standalone.
Changing the Mode to Master
Before you change the mode to Slave, ensure that Master-Slave Configuration Prerequisites are in place.
Step 1
Step 2
Changing the Mode to Slave
Before you change the mode to Slave, ensure that Master-Slave Configuration Prerequisites are in place.
You need to perform the following tasks:
Step 1
Step 2
Note
Step 3
•
If you select this check box, all the slaves of the Master (whose mode you currently changed to Slave) will be informed of the new master hostname. That is, they will become the slaves of the new Master.
•
Step 4
Changing the hostname of a Master
Changing the hostname of a Master is equivalent to pointing Slaves to a new Master.
When you point a Slave/Standalone to a new Master, DCR checks whether the new Master has the same Domain ID as the current machine.
If Domain ID is the same, DCR displays an error message saying that Master cannot be configured since the new Master has the same Domain ID.
In this case, you need to convert the Slave to Standalone, and then register the machine with the new Master.
On re-registration, the applications on Slave will clean up the device list.
When you change the host name of the current Master, you need to change the Slave's mode to Standalone, and then re-register the machine as a Slave by providing the new Master hostname. However, when the machine is re-configured as Slave, the applications will clean up the device list.
Let us say we have a Master M and Slave S. If M's hostname is changed, the Slave S has to be made standalone. Then it has to be re-configured as Slave of M. But when S is re-configured as Slave, the applications on S will clean up their device lists.
Therefore, you have to be aware of the fact that while changing the hostname of a Master, an application data is cleaned up on all Slaves.
Adding User-defined Fields
To add a user defined field:
Step 1
The Admin page appears with the current settings.
Step 2
The User-defined Fields page appears.
Step 3
Step 4
Step 5
Renaming User-defined Fields
To rename a user-defined field:
Step 1
The Admin page appears with the current DCA settings.
Step 2
The User-defined Field dialog box appears
Step 3
Step 4
The User-defined Field dialog box appears.
Step 5
Step 6
Deleting User-defined Fields
To delete a user-defined field:
Step 1
The Admin page appears with the current DCA settings.
Step 2
The User-defined Fields dialog box appears.
Step 3
Sample CSV File
CSV 2.0 or CSV 3.0 file formats are supported for import.
A Sample CSV 2.0 File
;; This file is generated by the export utility; If you edit this file, be sure you know what you are doing;Cisco Systems NM data import, source = export utility; Version = 2.0; Type = Csv;; Here are the columns of the table.; Columns 1 and 2 are required.; Columns 3 through 19 are optional.; Col# = 1: Name (including domain or simply an IP); Col# = 2: RO community string; Col# = 3: RW community string; Col# = 4: Serial Number; Col# = 5: User Field 1; Col# = 6: User Field 2; Col# = 7: User Field 3; Col# = 8: User Field 4; Col# = 9; Name = Telnet password; Col# = 10; Name = Enable password; Col# = 11; Name = Enable secret; Col# = 12; Name = Tacacs user; Col# = 13; Name = Tacacs password; Col# = 14; Name = Tacacs enable user; Col# = 15; Name = Tacacs enable password; Col# = 16; Name = Local user; Col# = 17; Name = Local password; Col# = 18; Name = Rcp user; Col# = 19; Name = Rcp password;; Here are the rows of data.;172.20.118.156,public,,FHH080600dg,,,,,,,,,,,,,,,172.20.118.150,public,,FHH0743W022,,,,,,,,,,,,,,,A Sample CSV 3.0 File
; This file is generated by DCR Export utilityCisco Systems NM Data import, Source=DCR Export; Type=DCRCSV; Version=3.0;;Start of section 0 - Basic Credentials;;HEADER: management_ip_address,host_name,domain_name,device_identity,display_na me,sysObjectID,dcr_device_type,mdf_type,snmp_v2_ro_comm_string,snmp_v2 _rw_comm_string,user_defined_field_0,user_defined_field_1;10.77.202.40,Switch6009,cisco.com,,Switch2,1.3.6.1.4.1.9.1.281,0,26843 8100,public,private,field0,field110.77.202.10,Router7000,cisco.com,,Router1,1.3.6.1.4.1.9.1.8,0,2784644 93,public,private,field0,field110.77.202.30,Switch4006,cisco.com,,Switch1,1.3.6.1.4.1.9.5.46,0,268438 086,public,private,field0,field110.77.202.20,Router6400,cisco.com,,Router2,1.3.6.1.4.1.9.1.180,0,26921 4543,public,private,field0,field1;End of CSV file
Note
Sample CSV 3.0 File for Auto Update Server Managed Devices
; This file is generated by DCR Export utilityCisco Systems NM Data import, Source=DCR Export; Type=DCRCSV; Version=3.0;;Start of section 0 - Basic Credentials;;HEADER: management_ip_address,host_name,domain_name,device_identity,display_na me,sysObjectID,dcr_device_type,mdf_type,snmp_v2_ro_comm_string,snmp_v2_rw _comm_string,snmp_v3_user_id,snmp_v3_password,snmp_v3_engine_id,snmp_v3_auth_algorithm,primary_username,primary_password,primary_enabl e_password;1.1.1.1,ons_host1,cisco.com,AUS_ID,ONS1,1.3.6.1.4.1.9.1.406,0,27361289 2,,,,,,,,,10.10.10.1,aus_server,cisco.com,,AUS_SERV1,UNKNOWN,3,UNKNOWN,,,,,,,,,;;Start of section 1 - AUS proxy;;HEADER: management_ip_address,host_name,domain_name,device_identity,display_na me,aus_username,aus_password,aus_url;1.1.1.1,ons_host1,cisco.com,AUS_ID,ONS1,admin,admin,10.10.10.1,aus_server,cisco.com,,AUS_SERV1,admin,admin,autoupdate/Auto UpdateServlet;;Start of section 2 - AUS managed;;HEADER: management_ip_address,host_name,domain_name,device_identity,display_na me,parent_aus_id;1.1.1.1,ons_host1,cisco.com,AUS_ID,ONS1,display_name=AUS_SERV1;End of CSV fileSample CSV 3.0 File for Cluster Managed Devices
; This file is generated by DCR Export utilityCisco Systems NM Data import, Source=DCR Export; Type=DCRCSV; Version=3.0;;Start of section 0 - Basic Credentials;;HEADER: management_ip_address,host_name,domain_name,device_identity,display_na me,sysObjectID,dcr_device_type,mdf_type,snmp_v2_ro_comm_string,snmp_v2_rw _comm_string,snmp_v3_user_id,snmp_v3_password,snmp_v3_engine_id,snmp_v3_auth_algori thm,primary_username,primary_password,primary_enable_password;1.1.1.1,ons_dev_1,cisco.com,,ONS1,1.3.6.1.4.1.9.1.406,0,273612892,,,,, ,,,,10.10.10.1,host1,cisco.com,,cluster1,Unknown,1,278283831,,,,,,,,,;;Start of section 3 - DSBU managed;;HEADER: management_ip_address,host_name,domain_name,device_identity,display_na me,dsbu_member_number,parent_dsbu_id;1.1.1.1,ons_dev_1,cisco.com,,ONS1,1,display_name=cluster;End of CSV fileMapping CSV 2.0 to CSV 3.0 Fields
The following table provides a mapping between the fields in CSV 2.0 and CSV 3.0:
Telnet password, Tacacs password, and Local password are matched to primary_password.
The Enable password, Enable secret, and Tacacs enable password are matched to primary_enable_password.
The Tacacs user and Local user are matched to primary_username.
The order of preference used to set these values in CSV 3.0:
•
•
•
Sample XML File
Sample XML File (Standard)
<?xml version="1.0"?><DEVICES><DEVICE><SET Name="Basic Credentials"><DEVATTRIB Name="management_ip_address">10.77.202.40</DEVATTRIB><DEVATTRIB Name="host_name">Switch6009</DEVATTRIB><DEVATTRIB Name="domain_name">cisco.com</DEVATTRIB><DEVATTRIB Name="display_name">Switch2</DEVATTRIB><DEVATTRIB Name="sysObjectID">1.3.6.1.4.1.9.1.281</DEVATTRIB><DEVATTRIB Name="dcr_device_type">0</DEVATTRIB><DEVATTRIB Name="mdf_type">268438100</DEVATTRIB><DEVATTRIB Name="snmp_v2_ro_comm_string">public</DEVATTRIB><DEVATTRIB Name="snmp_v2_rw_comm_string">private</DEVATTRIB><DEVATTRIB Name="primary_username">lab</DEVATTRIB><DEVATTRIB Name="primary_password">lab</DEVATTRIB><DEVATTRIB Name="primary_enable_password">lab</DEVATTRIB></SET></DEVICE></DEVICES>
Note
Sample XML File for Auto Update Server Managed Devices
<?xml version="1.0"?><DEVICES><DEVICE><SET Name="Basic Credentials"><DEVATTRIB Name="management_ip_address">1.1.1.1</DEVATTRIB><DEVATTRIB Name="host_name">ons_host1</DEVATTRIB><DEVATTRIB Name="domain_name">cisco.com</DEVATTRIB><DEVATTRIB Name="device_identity">AUS_ID</DEVATTRIB><DEVATTRIB Name="display_name">ONS1</DEVATTRIB><DEVATTRIB Name="sysObjectID">1.3.6.1.4.1.9.1.406</DEVATTRIB><DEVATTRIB Name="dcr_device_type">0</DEVATTRIB><DEVATTRIB Name="mdf_type">273612892</DEVATTRIB></SET><SET Name="AUS proxy"><DEVATTRIB Name="aus_username">admin</DEVATTRIB><DEVATTRIB Name="aus_password">admin</DEVATTRIB></SET><SET Name="AUS managed"><DEVATTRIB Name="device_identity">AUS_ID</DEVATTRIB><DEVATTRIB Name="parent_aus_id">display_name=AUS_SERV1</DEVATTRIB></SET></DEVICE><DEVICE><SET Name="Basic Credentials"><DEVATTRIB Name="management_ip_address">10.10.10.1</DEVATTRIB><DEVATTRIB Name="host_name">aus_server</DEVATTRIB><DEVATTRIB Name="domain_name">cisco.com</DEVATTRIB><DEVATTRIB Name="display_name">AUS_SERV1</DEVATTRIB><DEVATTRIB Name="sysObjectID">UNKNOWN</DEVATTRIB><DEVATTRIB Name="dcr_device_type">3</DEVATTRIB><DEVATTRIB Name="mdf_type">UNKNOWN</DEVATTRIB></SET><SET Name="AUS proxy"><DEVATTRIB Name="aus_username">admin</DEVATTRIB><DEVATTRIB Name="aus_password">admin</DEVATTRIB><DEVATTRIB Name="aus_url">autoupdate/AutoUpdateServlet</DEVATTRIB></SET></DEVICE></DEVICES>Sample XML File for Cluster Managed Devices
<?xml version="1.0"?><DEVICES><DEVICE><SET Name="Basic Credentials"><DEVATTRIB Name="management_ip_address">1.1.1.1</DEVATTRIB><DEVATTRIB Name="host_name">ons_dev_1</DEVATTRIB><DEVATTRIB Name="domain_name">cisco.com</DEVATTRIB><DEVATTRIB Name="display_name">ONS1</DEVATTRIB><DEVATTRIB Name="sysObjectID">1.3.6.1.4.1.9.1.406</DEVATTRIB><DEVATTRIB Name="dcr_device_type">0</DEVATTRIB><DEVATTRIB Name="mdf_type">273612892</DEVATTRIB></SET><SET Name="DSBU managed"><DEVATTRIB Name="dsbu_member_number">1</DEVATTRIB><DEVATTRIB Name="parent_dsbu_id">display_name=cluster1</DEVATTRIB></SET></DEVICE><DEVICE><SET Name="Basic Credentials"><DEVATTRIB Name="management_ip_address">10.10.10.1</DEVATTRIB><DEVATTRIB Name="host_name">host1</DEVATTRIB><DEVATTRIB Name="domain_name">cisco.com</DEVATTRIB><DEVATTRIB Name="display_name">cluster1</DEVATTRIB><DEVATTRIB Name="sysObjectID">Unknown</DEVATTRIB><DEVATTRIB Name="dcr_device_type">1</DEVATTRIB><DEVATTRIB Name="mdf_type">278283831</DEVATTRIB></SET></DEVICE></DEVICES>Using DCR Features Through CLI
Using Command Line Interface, you can add, delete, and modify devices, and change the DCR modes. You can also view the list of attributes that can be stored in DCR, and view the current DCR mode. The dcrcli utility provided with Common Services helps you perform these tasks using CLI.
Adding Devices Using dcrcli
To add devices using dcrcli:
Step 1
Step 2
Step 3
Enter either the IP address (ip), Hostname (hn), or Device Identity (di).
Enter the Display Name (dn) and the Attribute name (-a attname). The attribute sysObjectID is mandatory. You can add multiple attributes. For example,
add ip=1.1.1.1 hn=device1 dn=cisco.com -a sysObjectID=1.3.6.1.4.1.9.1.6
Deleting Devices Using dcrcli
To delete device using dcrcli:
Step 1
Step 2
Step 3
id is the Device ID. For example,
del id=54340
Editing Devices Using dcrcli
To modify devices using dcrcli
Step 1
Step 2
Step 3
Enter the Device ID (id).
Enter either the IP Address (ip), Hostname (hn), or Device Identity (di).
Enter the Display Name (dn) and the Attribute name (-a attname). You can add multiple attributes. For example,
mod id=54341 ip=2.2.2.2 dn=cisco.com -a display_name=new_name
Listing the Attributes
To view the list of all attributes:
Step 1
Step 2
Step 3
This lists Attribute Name, Attribute Description, and Attribute Type.
Attribute Type is a constant that identifies an Attribute Name.
Example:
Attribute Type 1072 identifies the attribute name display_name
Viewing the Current DCR Mode Using dcrcli
To view the current DCR mode:
Step 1
Step 2
Step 3
It lists the DCR ID, the DCR Group ID, the current DCR mode, and the associated Master/Slaves.
Viewing Device Details
To view device details using dcrcli:
Step 1
Step 2
Step 3
This lists all the details about the device with the ID you have specified. For example,
detail id=54341 lists the details for the device with device ID 54341.
Changing DCR Mode Using dcrcli
To change mode to Master:
Step 1
Step 2
Step 3
The DCR mode gets changed to Master.
To change mode to Standalone:
Step 1
Step 2
Step 3
The DCR mode gets changed to Standalone.
To change mode to Slave:
Step 1
Step 2
Step 3
You have to specify the Master for this slave.
The DCR mode gets changed to Slave. For example,
setslave master=1.2.1.3 port=443
Import Using CLI
You can import using the Command Line Interface.
Step 1
Step 2
•
Enter impFile fn=file name ft=file type
fn—the file name
ft—the file type; CSV and XML are the valid values.
Example:
impFile fn=/opt/CSCOpx/test.csv ft=csv•
Enter impNms nt=NMS type il=Installation location
nt—NMS type. Valid values are HPOV6.x and Netview7.x
il—Installation location of the NMS
Example:
impNms nt=HPOV6.x il=/opt/OV•
Enter ImpRNms nt=NMS type hn=hostname un=Remote User Name il=Installation location ot=OS Type
nt — NMS type. Valid values are HPOV6.x and Netview7.x
hn — Remote Host Name or IP address
un — Remote User Name
il — Installation location of the NMS
ot— OS Type; Valid values are HPUX, AIX, or SOL
Example:
impRNms nt=HPOV6.x hn=1.2.3.4 un=root il=/opt/OV ot=SOL•
Enter ImpACS ot=OS Type hn=ACS Server Name or IP address un=ACS admin user name pwd=ACS admin password prt=port number
ot— Operating System Type
hn — ACS Server Name or IP address
un — ACS admin user name
pwd— ACS admin password
prt — port number. Default is 2002.
Example:
impAcs ot=WIN2K hn=1.2.3.4 un=acsadmin pwd=acspwd prt=2002
Export Using CLI
You have the option to export using Command Line Interface.
Step 1
Step 2
Step 3
For filetype, CSV or XML are valid values. You can edit the Export Format file located at NMSROOT\objects\dcrimpexp\conf\Export_Format_CSV.xml.
Or,
Export_Format_XML.xml to specify the credentials. For example,exp fn=/opt/CSCOpx/test.csv ft=csv
Note
Implications of ACS Login Module on DCR
When Common Services is in ACS mode, you can perform operations in Device and Credential Repository (DCR) based on role assignment in ACS.
See Setting the Login Module to ACS for details on ACS login module.
Note
In DCR, you can see the buttons enabled or disabled, based on the role assigned to you.
For example, if a user U1 is assigned Approver role in ACS, he can see only the View button enabled in DCR. Further a user can see only those devices in DCR 's device-selector for which he has View Devices task assigned in ACS.
When performing operations in DCR, eventhough you select some devices and click the appropriate button, the operation will not be performed on all selected devices (unlike in CiscoWorks local mode). This is because the operation will be done only on those devices for which the you have the required privileges.
For example, a user U2 is assigned Helpdesk role for device D1 and System Administrator role for device D2 in ACS. Now U2 is able to select both D1 and D2 in DCR. But when the user clicks on Delete, only device D2 will be deleted.
This is because U2 has Helpdesk role for D1. Helpdesk role does not allow you to perform the Delete task.
Custom Roles and DCR
You can create new roles in ACS and assign a new combination of tasks to that role. In ACS, if a Custom role is created, a few points should be considered for DCR related tasks because certain DCR tasks have interdependencies. If certain tasks are included in the custom role, there will be other tasks which must also be assigned to the role to help you carry out the operations successfully.
The following table gives the details.
