Custom driver capabilities

Custom drivers (and standard drivers) differ in functionality from SmartModel drivers, which is described here.

Table 1. Custom driver capabilities. The 'Custom driver capabilities' table lists the differences between custom drivers (and standard drivers), and SmartModel drivers.
SmartModel drivers functionality Supported in Standard/Custom Mode?
AutoDiscovery Yes, however the AutoDiscovery XML files will need to be customized. See Discovering network devices for further information.
Command Set UOWs No
Create or Edit Command Sets No
Driver Update Yes
File-based Access Yes
Golden Configurations No
Import Configuration Yes
Native Command Sets Yes
OS Upgrade Yes
Sync from Device to Netcool Configuration Manager Yes, however the RAD must have Native Differences enabled. See Resource access documents (RADs) for further information.
Sync from Netcool Configuration Manager to Device No
Report Only Sync Yes, however the RAD must have Native Differences enabled. See Resource access documents (RADs) for further information.
Search Sets No
Security Sets No
Submit Configuration, 'Disaster Recovery' and 'Use Raw CLI' options not selected No
Submit Current Configuration, 'Disaster Recovery' and 'Use Raw CLI' selected No, but you can achieve the same functionality by importing the device again to cause the Current configuration to become a Versioned Configuration, and then submitting it.
Submit Draft Configuration, 'Disaster Recovery' and 'Use Raw CLI' selected No, but you can achieve the same functionality by copying the configuration into a Native Command Set and submitting the Native Command Set.
Submit Stale Configuration, 'Disaster Recovery' and 'Use Raw CLI' selected Yes
Submit Versioned Configuration, 'Disaster Recovery' and 'Use Raw CLI' selected Yes
View Modelled Configuration No
View Modelled Differences No
View Native Configuration Yes
View Native Differences Yes
Note: The Netcool Configuration Manager UI may not block end-users from attempting to access the function even though it is not supported by the Standard/Custom driver.
Netcool Configuration Manager - Compliance does not make direct use of drivers but is indirectly affected by the use of Standard mode:
  • When in Standard mode, only native policies will give valid results. Modelled policies can be run but will all fail as there is no modelled configuration.
  • Since modelled command sets are not supported in Standard mode, compliance cannot execute them as the result of a policy evaluation.