RAD access order

Edit online

Use the access order section of a RAD to specify the names of and the order in which Netcool Configuration Manager should access specific network protocols. Access order is not called out explicitly in the GUI as it is defined in the XML document; however, it is represented in the GUI by the list of enabled access types.

XML tags example

The XML document explicitly calls out the access order, and declares which access types will be used.

The following example shows the XML tags used in the access order section of a RAD:

<access-order>
	<name>ssh</name>
	<name>telnet</name>
	<name>alt-telnet</name>
</access-order>

Table 1. XML tags description
The following table describes each of the XML tags used in the access order section of a RAD:
XML tag	Description
`<access-order>`	Specifies the access order section of a RAD. The `<access-order>` XML tag is typically followed by one or more `<name>` XML tags. The order in which access types are attempted is specified in a RAD file. So, in this example Netcool Configuration Manager would start with SSH, then TELNET, and so forth. As soon as a successful connection is made, the access type listed next in line is not required and therefore not attempted.
`<name>`	Specifies the name of an access type, or network protocol. Valid values are as follows: `ssh` — Specifies the Secure Shell (SSH) protocol. `TELNET` — Specifies the TELNET protocol.

Tip: GUI access order: Access types are displayed by right clicking on the RAD in the Resource Browser, and selecting Edit. The access types displayed in the GUI need to be enabled in the RAD for them to be used. Access types can be enabled by ensuring that the enabled checkbox against the access type is selected. An access type that is italicized in the GUI is not enabled in the RAD. The order in which they are listed reflects the order in which the access types are used to access the device. For example, if the access type of 'ssh' is listed before 'telnet', the 'ssh' access type will be used to attempt to connect to the device first. If a successful connection is made to the device using 'ssh', then the 'telnet' access type will be ignored. If the connection is not successful using 'ssh', 'telnet' is then used to attempt connection to the device.

Remember: At this point, the name of the access type should not necessarily reflect the protocol used to connect to the device.