Known issues in previous versions

SmartModelUpgrade.sh -all script upgrading both Standard and Custom drivers along with SmartModel drivers

Issue: Release drivers missing SmartModelUpgrade.sh, SmartModelUpgrade.jar and drivers_bulk_install.sh files

Harmless "Undetermined error" in drivers_bulk_install.sh

When using the drivers bulk installer utility drivers_bulk_install.sh, the script output shows that the result has one undetermined error: Unable to locate log file for analysis. This error can safely be ignored.

Issue: [IBMBNT Switch compass 7.5.x] Missing README for config changes only support via streaming during driver installation

Cause: The version of IBM-BNT device used in testing did not support FTP, so the only way to perform tasks was to set the streaming flags to true for both put and get.
Workaround: Set the streaming flags in the RAD to both true if not set already.

Issue: [Standard model drivers] Standard only driver not working after run SmartModelUpgrade with smart model driver installed in same server

Cause

After running the smartModelUpgrade script the smart model flag in the database is set. This lets the system know that there is a schema model for the device. In this case there is not schema model because the device is only a standard model device but the script set the flag anyway.

Workaround

When running the Smartmodels, specify the driver that needs to have the smart model flag set. If the script was already run, to fix the issue go into the database and change the flag. Obtain the unique ID for the correct driver, then go to the drivers table and change the SmartModel field to false.

Example SQL for generic device:

UPDATE "ICOSUSER"."DRIVER" SET SMARTMODELENABLED = 'true' 
WHERE DISPLAYVENDOR!='Unknown';
commit;

Issue: [error in logs] Error Invalid classpath entry "/opt/IBM/tivoli/netcool/ncm/drivers/lib_legacy/aspn-client-v1.jar" in classpath

Cause: On some releases the invalid classpath error shows up after startup. This is before any work is done. This error does not affect any drivers that are executed afterwards. Each driver will now load the needed classes from individual classpath files before running.
Workaround: No workaround is needed.

Issue: [Huawei DSLAM 56xx 8.x] Using streaming to fetch native configurations for the Huawei DSLAM 56xx 8.x device prevents configuration data from modeling

Cause: Line wrap occurs when the native configuration is streamed and wrapping lines do not model in XML correctly
Workaround: File transfer should be used to fetch the native configuration for the Huawei DSLAM device instead of streaming. This is configured in the default resource access document for the Huawei DSLAM driver. Streaming is configured as the default method to send changes to the device as it does not support file transfer as a mechanism to do so.

Issue: [Cisco ASR 1K] Search set can be created and applied to the device with standard driver in 6.3.0.6

Cause: Netcool Configuration Manager Version 6.3 fix pack 6 (or earlier) does not prevent search set from being created and applied to Cisco ASR devices with standard drivers.
Workaround: When using Netcool Configuration Manager Version 6.3 fix pack 6 (or earlier), do not create and apply search sets to Cisco ASR devices with standard drivers.

Issue: [Cisco ASR 1K] The user is not blocked from importing standard config into config editor in 6.3.0.6

Cause: Netcool Configuration Manager Version 6.3 fix pack 6 (or earlier) does not prevent the (ineffective) importation of standard configurations for Cisco ASR devices via the Configuration Editor.
Workaround: When using Netcool Configuration Manager Version 6.3 fix pack 6 (or earlier), do not import standard configurations for Cisco ASR devices via the Configuration Editor, as this will have no effect on the device configuration.

Issue: [Extreme Switch 48xx 15.x] Disaster Recovery

Issue: When a versioned configuration is submitted to an Extreme Switch 48xx 15.x via the Disaster Recovery functionality, the associated UOW is marked as successful, even though the configuration is not sent to the device.

Cause: Zero length binary data file is being transferred to the device
Workaround: Do not use Disaster Recovery to apply configurations to an Extreme Switch 48xx 15.x if there is a "Warning: No Binary data to apply" message in the UOW log.

Issue: [Extreme Switch 48xx 15.x] Native Diff displays incorrect changes

Cause: Performing diffing on two imported configurations through the Native Show Differences feature displays false output.
Workaround: Use the modeled difference feature instead.

Issue: [Extreme Switch 48xx 15.x] Multiple Config Compare

Cause: The stored configurations and running configurations for Extreme 48xx 15.x switches are in different formats, and therefore the 'show configuration' command can not be used to interpret these configurations.
Workaround: None; The comparing of running and stored configurations in Extreme 48xx 15.x switches is not supported by Netcool Configuration Manager.

Issue: [IBM-BNT Switch VFab 7.x] Custom Resource Icons

Cause: When an IBM-BNT VFab 7.x switch is imported, the icon displayed in Netcool Configuration Manager the network resource icon instead of the IBM-BNT icon
Workaround: None

Issue [IBM-BNT Switch VFab 7.x] Native Compare exception in Standard Mode

Cause: When you apply a native command set to an IBM-BNT VFab 7.xs switch, the UOW fails with an exception when the RAD flag 'Native Compare' has been set to TRUE.
Workaround: Deselect the check box for Native Compare on the configuration tab of the resource access document (RAD). This will prevent a native comparison from being carried out during a apply native commands set unit of work.; To see the changes applied to the native device configuration, select both configs in the Resource Browser's configuration tab, and choose Show Differences Native View from the right-click menu.

Issue: ITNCM 6.4.0.2 [Search Set] Applied to Network Resource with Standard Support

Cause: A search set can be erroneously applied to a standard network resource if the values of 'Network Resources in a Realm' or 'Network Resources retrieved from a Realm' have been selected in the Apply Search Set wizard.
Workaround: Do not select the values of 'Network Resources in a Realm' or 'Network Resources retrieved from a Realm' in the Apply Search Set wizard when applying search sets to standard network resources.

Issue: [Core] InvocationTargetException on saving a draft config

Cause: For devices with very large configurations the user may encounter an InvocationTargetException on attempting to save a new configuration draft due to WebSphere running out of memory.
Workaround: Increase the maximum heap size for the embedded WebSphere Application server to a sufficient size or perform housekeeping on the versioned configurations to reduce their number.

Issue: [Cisco 76xx] Setting allowed VLANs on trunk failure

Cause: If you want to add, remove, or modify a list of VLANs on a trunk, you have to issue 'add' or 'remove' commands. However these commands are not being substituted correctly when submitted to the device via a config change or restore operation.
Workaround: Use native commands for configuring VLANs on a trunk.

Issue: Deletion of undocumented command fails for modeled config changes and restore operations

Issue: Deletion of undocumented command fails for modeled config changes and restore operations.
Cause: For Junoscript based devices there is an issue with the XML generated when the user deletes srlg configuration data contained within the undocumented section of the routing-options config, and causes modeled config operation and restores to fail. This issue could occur with other undocumented commands also.
Workaround: Remove the undocumented command with correct Junoscript using a native command set.

Issue: [Cisco ASR 9k] Rollback and commit operations

Issue

Some configuration changes sent to the device, for example 'interface ATM 0/0/0/1', will receive an error message after applying a commit command.

The new configuration will be saved into the device running-configuration and will cause Disaster Recovery to fail.

The following is an example of a device error message:
% Failed to commit one or more configuration items. Please issue 'show configuration failed' from this session to view the errors.

Cause

The device is processing the interface ATM0/0/0/2 type commands.

Workaround

You can address this issue in two steps:

First, ensure that the config is kept in good condition, and turn on rollback when making config changes.
Secondly, do not pick DR when submitting a versioned config.

This will allow Netcool Configuration Manager to calculate the differences and only send the commands needed to restore the device's config.

Issue: [Juniper QFabric] Modeled command sets unsuccessful on Juniper QFabric

Issue: Modeled command sets and configuration changes do not complete successfully on the Juniper QFabric.
Cause: Juniper identified an issue with Junoscript configuration change processing and a fix will be in an upcoming JUNOS software release.
Workaround: Use native command sets.

Issue: [Schema] Juniper ERX Config Submit Failure configuration||ip||vrf

Issue: The ip vrf commands are not completely supported by the translator. Any configuration with ip vrf commands will have issues with any changes made to these commands and they will not be correctly displayed in the config editor interface.
Workaround: None

Issue: [Release Notes] driverTools.sh memory requirement

Cause

For Netcool Configuration Manager versions 6.3 and earlier, the driverTools.sh script uses its own JVM. Therefore, users must specify a custom maximum heap size to prevent Out of Memory exceptions for larger schemas. For example, the Juniper SRX specifies a maximum heap size of 1536m.

Workaround

Modify the default max heap size (-Xmx512m) in the script file to increase the memory for driverTools.sh. Testing has indicated setting this to 1536m resolves the memory issue.

For example:

$JAVA_HOME/bin/java -Xmx1536m -Dinstall.dir=$INSTALL_DIR 
-Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl
-Dcom.ibm.CORBA.ConfigURL="file:$INSTALL_DIR/config/properties/sas.client.props"
-Djava.security.auth.login.config="file:$INSTALL_DIR/config/properties/wsjaas_client.conf"
-cp $CLASSPATH com.intelliden.drivers.DriverTools ${1+"$@"}

Issue: [Nexus 1k] Native Command Set Line By Line Failure

Cause

Failures occur when attempting to stream line by line a native command set that contains a command to apply a MOTD Banner with multiple lines.

Workaround

To prevent these failures, the following new inline commands for native command sets are provided. The following commands apply only if Allow Line by Line for Native Command Set mode is true. If the Allow Line by Line for Native Command Set mode is not true, then Netcool Configuration Manager removes the commands.

Table 1. New inline commands for native command sets
Inline command	Description
`ITNCM-Sleep`	Allows Netcool Configuration Manager to sleep for the specified seconds before executing the next command in the list of native command sets. The following example specifies a value of 2000 Milliseconds, which means that Netcool Configuration Manager sleeps for two milliseconds before executing the next command in the list. `ITNCM-Sleep=2000`
`ITNCM-NoPrompt`	Sets it so that Netcool Configuration Manager waits for no prompt. You can specify one of the following values: `ITNCM-NoPrompt=true` — Netcool Configuration Manager waits for no prompt when executing commands in native command sets. `ITNCM-NoPrompt=false` — Netcool Configuration Manager waits for a prompt when executing commands in native command sets.
`ITNCM-ChangePrompt`	Changes the prompt that ITNCM is waiting for when executing commands in NCS. The following example changes the default prompt to `>` (right angle bracket). `ITNCM-ChangePrompt=>`
`ITNCM-ResetPrompt`	Resets the prompt to its default value. The default prompt is set in the device script using the `default.prompt=` `prompt`. For example, `default.prompt=#` specifies that the default prompt is `#` (pound sign). You can specify one of the following values: `ITNCM-ResetPrompt=true` — Netcool Configuration Manager resets the prompt to the default value specified in the device script. `ITNCM-ResetPrompt=false` — Netcool Configuration Manager does not reset the prompt to the default value specified in the device script.
`ITNCM-ChangeEndOfLine`	Changes the end of line value that follows each command. For example: `ITNCM-ChangeEndOfLine=\r\n` Other values are: `\r,\n,\m`.
`ITNCM-ResetEndOfLine`	Resets the end of line value back to the default value. The default value is `\n`. You can specify one of the following values: `ITNCM-ResetEndOfLine=true` — Netcool Configuration Manager resets the end of line value to the default value. `ITNCM-ResetEndOfLine=false` — Netcool Configuration Manager does not reset the end of line value to the default value.

Related information

For information on command sets, see http://www.ibm.com/support/knowledgecenter/SS7UH9_6.4.2/ncm/wip/condev/task/ncm_idt_idtcommandsets.html.

For information on the Allow Line by Line for Native Command Set mode, see http://www.ibm.com/support/knowledgecenter/SS7UH9_6.4.2/ncm/wip/adm/task/ncm_adm_devcom_editingradguiconfig.html

http://www.ibm.com/support/knowledgecenter/SS7UH9_6.4.2/ncm/wip/adm/task/ncm_adm_devcom_editingradguiconfig.html

Issue: [Nexus 1k] Multi-line MOTD Banner via FTP

Cause: When attempting to apply a multi-line MOTD Banner via FTP, only the first line will be applied to the configuration.
Workaround: This issue is similar to the one described in Known issues in previous versions. However, in this case this is expected behavior and is a limitation of the NX OS on this device.

Issue: Disaster Recovery is not supported on CISCO Nexus 1000v

Cause: The Disaster Recovery feature is not supported on the CISCO Nexus 1000v device.
Workaround: Follow the disaster recovery procedure from your vendor.

Issue: Avaya Switch Disaster Recovery issues

Cause

The Disaster Recovery feature will not work on the 48xx and 55xx devices running Netcool Configuration Manager 6.3.0.2 and earlier.

Workaround

Change the Config Data Type field in the RAD to the value CLIandBIN, and deselect the Reboot on Config Load check box. Once this is done import the device again.
Deselect the Streaming Put check box in the RAD.
In the device script, comment out the Ftp file section.
In the Submit Configuration Change window, submit the Versioned Config and select the Disaster Recovery; Use Raw CLI checkbox.
Select the Streaming Put check box in the RAD.

Issue: [Avaya 8xxx 7.x] Import of Versioned Config into Editor

Cause: The driver for Avaya Switch 8xxx 7.x does not properly import a versioned configuration into the GUI editor window by selecting file > import.
Workaround: To import a versioned configuration, select the device from the realm directory then select the Configurations tab. Choose the Versioned configuration to be imported, right click, and select Submit.

Issue: UOW fails for Report diffs = true on Avaya device

Cause: The diffs reported on the Avaya device using Report Diffs = true will only report against startup vs running configurations. If diffs are needed against a versioned configuration then use the work around.
Workaround: If diffs are needed against a versioned configuration then the work around is to use the Synchronize option in the Resource Browser after the initial imports to synchronize the configurations.
Related information: For information on Synchronizing configurations, see http://www.ibm.com/support/knowledgecenter/SS7UH9_6.4.2/ncm/wip/condev/task/ncm_condev_synchronizingconfigurations.html.

Issue: [Juniper routers and switches] Rollback should not be selected in UOWs

Issue: Rollback options should not be selected in Juniper router and switch UOWs, rollback is done automatically if UOW fails.
Cause: Juniper device scripts are setup to automatically rollback if UOW fails to avoid leaving the device in a bad state.
Workaround: Do not select rollback in UOWs for Juniper devices.