Driver Support Document
| SYSOID Mapping | ||
| SYSOID | MODEL | OS VERSION |
| 1.3.6.1.4.1.9.1.2238 | APIC controller | 1.x |
The configuration of APIC fabrics are coordinated throuh the controller nodes. Leaf and spline switches are managed by this driver, but should not be directly imported as devices. To manage an APIC fabric, add the primary controller as a device. After the Module Status diagnostic is run, the child switches will be discovered and assigned as devices that will also be managed by this driver. Most tasks on the child devices will be run on the devices directly, though some are implemented by connecting to the controller.
By default, this driver manages the parent APIC and child Nexus devices separately, including the configuration for each using separate virtual devices. Specifically, the APIC parent only contains the configuration for itself and none of the children. If the device access variable "get_all" is set to "true", the parent APIC will collect the configuration for all child nodes in with its own configuration.
Scripting on the Cisco APIC and its member switches is implemented by three scripting modes.
Script Mode Subject Device Result Cisco APIC enable APIC (parent) Commands are run in the APIC's enable mode Nexus (child) Commands are executed on the APIC parent, and the value "fabric <node>" is prepended to all commands. Cisco APIC config APIC (parent) Commands are run in the APIC's configuration mode Nexus (child) Script will fail (unsupported) Cisco APIC Linux APIC (parent) Script will fail (unsupported) Nexus (child) Command will be run directly on the Nexus member switch, from a bash prompt
Discovery tasks for Javascript drivers handle More prompts by using timeouts, which can cause problems with the third-party SSH client code, which interprets the timeout as a disconnection. There are two options to work around the problem. Setting the RCX option [<option name="Driver/Discovery/UsePollRead">true</option>] in site_options.rcx will effect the workaround for all affected devices. Alternatively, it could be applied to a single device by setting the device access variable "PollRead" to "true".
Discovery tasks for Javascript drivers use wakeup characters are sent during device connection, to ensure that the device is responding. Normally, these characters do not echo to the console, but some devices may echo them. In this case, this causes the prompt detection phase to fail, which in turn can cause More prompts to not be handled properly, and discovery may fail. If these characters are echoed from the device [check the session log to see this], then set the device access variable "skip_ctrl_u" to skip the sending of the wakeup characters. Note that setting this option on a previously working device could cause discovery tasks to fail, but it only affects CLI discovery. SNMP discovery is unaffected.