netcool configuration manager version 6 release 4 · pdf filehuawei cir1uen dslam smartax...

Netcool Configuration ManagerVersion 6 Release 4

Drivers 18 Release NotesR2E1

��

NoteBefore using this information and the product it supports, read the information in “Notices” on page 21.

This edition applies to version 6, release 4 of IBM Tivoli Netcool Configuration Manager (5725-F56) and to allsubsequent releases and modifications until otherwise indicated in new editions.

© Copyright IBM Corporation 2010, 2013.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Chapter 1. What's new in Drivers 18 . . 1

Chapter 2. Drivers 18 installation . . . . 5

Chapter 3. Known issues andworkarounds . . . . . . . . . . . . 9

Notices . . . . . . . . . . . . . . 21Trademarks . . . . . . . . . . . . . . 23

© Copyright IBM Corp. 2010, 2013 iii

iv IBM Tivoli Netcool Configuration Manager: Drivers 18 Release Notes

Chapter 1. What's new in Drivers 18

Use this information to review the new and updated drivers in the Drivers 18release.

Drivers 18 upgrade paths

When upgrading to Drivers 18 from a previous drivers version, follow the upgradepaths listed in the following table, depending on your system configuration:

Table 1. Drivers 18 upgrade paths

Netcool Configuration Manager version Driver upgrade path

Netcool Configuration Manager 6.2 or 6.3 Install Drivers 18 as described in Chapter 2,“Drivers 18 installation,” on page 5 of theserelease notes.Note: This includes the installation of theseparate compliance definitions using thenew individual compliance installers foreach SmartModel package.

Netcool Configuration Manager 6.4 Install Drivers 18 as described in Chapter 2,“Drivers 18 installation,” on page 5 of theserelease notes.Note: This excludes the installation of theseparate compliance definitions.

Installation changes from Drivers 16 to Drivers 17 and 18

The following list summarizes the installation changes from Drivers 16 to Drivers17 and 18:

Netcool Configuration Manager Standard Device and Standard Basic Devicepackages

For Netcool Configuration Manager Standard Device and Standard BasicDevice packages the associated installers have been greatly reduced in sizeand time to install.

Netcool Configuration Manager SmartModel Basic Device, SmartModel Device,and SmartModel Complex Device packages

For Netcool Configuration Manager SmartModel Basic Device, SmartModelDevice, and SmartModel Complex Device packages:v All drivers are made available through individual installers for each

driver to minimize the download footprint.v The full installers are still available and now contain only the drivers

classified as belonging to the relevant package.v The SmartModelTier0Upgrade.bin, SmartModelTier2Upgrade.bin, and

SmartModelTier3Upgrade.bin installers are no longer needed.v The SmartModelTier0Upgrade.sh, SmartModelTier2Upgrade.sh, and

SmartModelTier3Upgrade.sh upgrade scripts from previous driverreleases are deprecated and have been replaced by theSmartModelUpgrade.sh, SmartModelBasicUpgrade.sh, andSmartModelComplexUpgrade.sh upgrade scripts. These new upgradescripts are installed when you install the SmartModel Basic Device,

© Copyright IBM Corp. 2010, 2013 1

SmartModel Device, and SmartModel Complex Device packages. Forexample, installing the SmartModel Complex Device package causesonly the SmartModelComplexUpgrade.sh upgrade script to be installed.The new upgrade scripts also get installed with any of the individualinstallers from the SmartModel Basic Device, SmartModel Device, andSmartModel Complex Device packages.

Compliance installation changes from Drivers 16 to Drivers 17 and 18 – NetcoolConfiguration Manager 6.4

The ITNCMComplianceDefinitions.bin separate installer is no longerrequired as the Compliance functionality now uses the driver metadatainstalled by the SmartModel Basic Device, SmartModel Device, andSmartModel Complex Device packages or any of the individual installersfrom these packages.

Compliance installation changes from Drivers 16 to Drivers 17 and 18 – NetcoolConfiguration Manager 6.2 and 6.3

The single ITNCMComplianceDefinitions.bin installer is replaced by newindividual installers for each SmartModel package, which need to bedownloaded and installed separately.

See Chapter 2, “Drivers 18 installation,” on page 5 of these release notes forinstructions on how to install the compliance definitions on NetcoolConfiguration Manager 6.2 and 6.3.

New and updated drivers

The Drivers 18 release contains the new and updated drivers listed in thefollowing table. The table provides the vendor, part number, device type,supported models, supported operating systems, and driver types associated withthe new drivers, as well as notes with further information.

Note: APAR fixes and other maintenance for other Drivers that is not included inthe list below will be included in a separate Drivers Fixpack that will be releasedat a later date. Please contact IBM support for further information.

Table 2. New and updated drivers

Vendor Part No TypeSupportedmodels

Supportedoperatingsystems

Driver name / driver filename Package Notes

Alcatel-Lucent

CIS3GEN PON 7342 GPONOLTS-L

OS 4.8 alcatel_pon_7342_4.8.x /AlcatelPON734248x.bin

SmartModel

Cisco CIR1QEN Router ASR900/1000Series

IOS-XE 2 cisco_router_asr1k_2.4.x /CiscoRouterASR1k24x.bin

SmartModel

Refresh of Drivers 17 partwith new VTMOS nameand updated description.Note: Replacescisco_router_asr_2.4.xdriver.

Cisco CIR1REN Router ASR900/1000Series

IOS-XE 3 cisco_router_asr1k_3.x /CiscoRouterASR1k3x.bin

SmartModel

New Drivers 18 driverseparated out of Drivers17 offerings

Cisco CIR1SEN Router ASR 9000Series

IOS-XR 3and 4

cisco_router_asr9k_4.x /CiscoRouterASR9k4x.bin

SmartModel

Refresh of Drivers 17 partwith new VTMOS nameand updated description.Note: Replacescisco_router_asr_4.xdriver.

Extreme CIR1TEN Switch Summit andBlackdiamondSeries

OS 15 extreme_switch_summit-48xx_15.x / ExtremeSwitchSummit48xx15x.bin

SmartModel

New with Drivers 18

Huawei CIR1UEN DSLAM SmartAXDSLAM andOLT MA5600 Series

OS 8 huawei_dslam_56xx_8.x /HuaweiDSLAM56xx8x.bin

SmartModel

Updated supportedmodels to include 5600T,and added newdescription.

IBM-BNT

CIR1VEN Switch 80xx/81xxSeries

OS 7 ibm-bnt_switch_8xxx_7.x /IBMBNTSwitch8xxx7x.bin

SmartModel

New with Drivers 18

2 IBM Tivoli Netcool Configuration Manager: Drivers 18 Release Notes

Table 2. New and updated drivers (continued)

Vendor Part No TypeSupportedmodels

Supportedoperatingsystems

Driver name / driver filename Package Notes

Juniper CIR1WEN Router M, MX, andJCS Series

JUNOS 11.3- 12.3

juniper_router_mxxx_12.0/JuniperRouterMxxx120.bin

SmartModel

Updated for Drivers 18 tosupport up to 12.3

Juniper CIR1ZEN Router T and TXSeries

JUNOS 11.3- 12.3

juniper_router_mxxx_12.0/JuniperRouterMxxx120.bin

SmartModelComplex

Chapter 1. What's new in Drivers 18 3

Chapter 2. Drivers 18 installation

Use this information to understand Netcool Configuration Manager Drivers 18installation, specifically the file name, download location, part number, and whereto go for detailed driver installation instructions.

Downloading the drivers

Download ITNCM Device Support - Drivers 18 from IBM Passport Advantage. Youcan log into your Passport Advantage (PPA) account at the following URL:

http://www.ibm.com/software/passportadvantage

The following tables provide the media available with the Drivers 18 release. Oncelogged into your PPA account search for the appropriate part number.

Note: These packages contain all device drivers from the Drivers 17 release, aswell as all new and enhanced drivers released specifically for Drivers 18.

Table 3. Drivers 18 installation files

Package file name Part number Details

ITNCMStandard.tar CIR1JEN IBM Netcool Configuration Manager Drivers18 Standard Device Full Installer v6.4multiplatform English

ITNCMStandardBasic.tar CIR1LEN IBM Netcool Configuration Manager Drivers18 Standard Basic Device Full Installer v6.4multiplatform English

ITNCMSmartModelBasic.tar CIR1MEN IBM Netcool Configuration Manager Drivers18 SmartModel Basic Device Full Installerv6.4 multiplatform English

ITNCMSmartModel.tar CIR1NEN IBM Netcool Configuration Manager Drivers18 SmartModel Device v6.4 Full Installermultiplatform English

ITNCMSmartModelComplex.tar

CIR1XEN IBM Netcool Configuration Manager Drivers18 SmartModel Complex Device v6.4 FullInstaller multiplatform English

ITNCMSmartModelDefinitions.bin

CIR1PEN ITNCM Compliance Definitions forSmartModel Devices for 6.2/6.3

ITNCMSmartModelComplexDefinitions.bin

CIR1YEN ITNCM Compliance Definitions forSmartModel Complex Devices for 6.2/6.3

ITNCM_Autodiscovery.tar CIR1KEN Autodiscovery Driver

Installing the drivers

For information on installing drivers, refer to one of the following resourceslocated on the Information Center:v See the 'Installing drivers' section in 'Chapter 2. Installing' of the IBM Tivoli

Netcool Configuration Manager Installation and Configuration Guide:http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_configurationmgr.doc_6.4.0/ncm_pdf_ins_master_64.pdf


http://www.ibm.com/software/passportadvantage

http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_configurationmgr.doc_6.4.0/ncm_pdf_ins_master_64.pdf


v See the 'Installing drivers' section in the Netcool Configuration Managerinformation center:http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_configurationmgr.doc_6.4.0/ncm/wip/install/concept/ncm_ins_driverinstalloverview.html

Attention: To prevent corrupt driver installation in the case of NetcoolConfiguration Manager not having been stopped before starting driver installation,do not attempt to restart or stop Netcool Configuration Manager until the driversinstallation has completed.

Installing the auto-discovery driver

For information on installing the auto-discovery feature, refer to one of thefollowing resources located on the Information Center:v See the 'Installing auto-discovery' section in 'Chapter 2. Installing' of the IBM

Tivoli Netcool Configuration Manager Installation and Configuration Guide:http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_configurationmgr.doc_6.4.0/ncm_pdf_ins_master_64.pdf

v See the 'Installing auto-discovery' section in the Netcool Configuration Managerinformation center:http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_configurationmgr.doc_6.4.0/ncm/wip/install/concept/ncm_ins_installingautodisco.html

UOWs may fail due to out of memory errors on Juniper devices

Due to the large size of the Juniper drivers, device imports and other UOWs mayfail due to out of memory errors, which can be seen in the UOW logs. It isrecommended that customers using Juniper drivers increase their client and servermemory settings. The following list identifies the settings to specify for the systemproperties associated with client memory, driver memory, and schema scale factor.

Note: The descriptions for the Memory Manager - Memory Reserved For Driversand Memory Manager - Schema Scale Factor system properties inhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_configurationmgr.doc_6.4.0/ncm/wip/adm/reference/ncm_adm_sys_properties.html indicate that these properties are for IBM Tivoli UseOnly. However, to avoid the out of memory errors on Juniper devices it isnecessary to supply the values in the following list for these system properties.

Minimum Client MemorySet this system property to the value 512m (512 MB)

Maximum Client MemorySet this system property to the value 1024m (1024 MB)

Memory Manager - Memory Reserved For DriversSet this system property to 1024m (1024 MB)

Memory Manager - Schema Scale FactorSet this system property to the value 2.8 (2.8 MB)

For more information on Minimum Client Memory, Maximum Client Memory, andother system properties, as well as for instructions on modifying them, see


http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_configurationmgr.doc_6.4.0/ncm/wip/install/concept/ncm_ins_driverinstalloverview.html





http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_configurationmgr.doc_6.4.0/ncm/wip/install/concept/ncm_ins_installingautodisco.html



http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_configurationmgr.doc_6.4.0/ncm/wip/adm/reference/ncm_adm_sys_properties.html



http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_configurationmgr.doc_6.4.0/ncm/wip/adm/reference/ncm_adm_sys_properties.html.

Note: After modifying the previously listed system properties, exit the SystemProperties window and exit the GUI. Then, reopen the GUI and reopen the SystemProperties window. The modified values should now be available.

To modify the settings for the server memory parameters, follow these steps:

Note: If you have a distributed setup, you will need to modify the server memorysettings on each server.1. Stop Netcool Configuration Manager by running the itncm.sh script as follows:

a. Access the directory containing the installer. The default location is/opt/IBM/tivoli/netcool/ncm/bin.

b. Within this directory, execute the itncm.sh script and specify the stopoption as follows:./itncm.sh stop

2. Locate the setEnv.sh script in the following directory on each server:/opt/IBM/tivoli/netcool/ncm/bin/utils/support

3. Create a backup copy of the setEnv.sh script. For example:cp setEnv.sh setEnv.sh.backup

4. Using your favorite text editor, open the setEnv.sh script for editing. Forexample:vi setEnv.sh

5. Modify the server memory parameters in setEnv.sh to match the following:#!/bin/sh

WEBSPHERE_INITIALHEAP_SIZE=256export WEBSPHERE_INITIALHEAP_SIZE

WEBSPHERE_MAXIMUMHEAP_SIZE=2036export WEBSPHERE_MAXIMUMHEAP_SIZE

WEBSPHERE_MAXPERM_SIZE=256mexport WEBSPHERE_MAXPERM_SIZE

WORKER_MEM_ARGS="-Xms512m -Xmx2036m -XX:MaxPermSize=128m"export WORKER_MEM_ARGS

IDT_MEM_ARGS="-Xms512m -Xmx1024m -XX:MaxPermSize=128m"export IDT_MEM_ARGS

LANG=en_US.UTF-8export LANG#LD_LIBRARY_PATH=#export LD_LIBRARY_PATH

Note: The LD_LIBRARY_PATH parameter should be set and uncommentedonly when using the Oracle Instant Client with Netcool Configuration Manager.

6. Save your edits and then exit the editor.7. Run the setWSMem.sh script from the same directory: /opt/IBM/tivoli/netcool/

ncm/bin/utils/support.8. Restart Netcool Configuration Manager by running the itncm.sh script as

follows:

Chapter 2. Drivers installation 7




a. Access the directory containing the installer. The default location is/opt/IBM/tivoli/netcool/ncm/bin.

b. Within this directory, execute the itncm.sh script and specify the startoption as follows:./itncm.sh start


Chapter 3. Known issues and workarounds

Use this information to understand the known issues and workarounds for NetcoolConfiguration Manager Drivers 18.

Issue: D18 [Huawei DSLAM 56xx 8.x] Using streaming to fetchnative configurations for the Huawei DSLAM 56xx 8.x deviceprevents configuration data from modelling

Cause Line wrap occurs when the native configuration is streamed and wrappinglines do not model in XML correctly

WorkaroundFile transfer should be used to fetch the native configuration for theHuawei DSLAM device instead of streaming. This is configured in thedefault resource access document for the Huawei DSLAM driver.Streaming is configured as the default method to send changes to thedevice as it does not support file transfer as a mechanism to do so.

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

Cause Netcool Configuration Manager Version 6.3 fix pack 6 (or earlier) does notprevent search set from being created and applied to Cisco ASR deviceswith standard drivers.

WorkaroundWhen using Netcool Configuration Manager Version 6.3 fix pack 6 (orearlier), do not create and apply search sets to Cisco ASR devices withstandard drivers.

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

Cause Netcool Configuration Manager Version 6.3 fix pack 6 (or earlier) does notprevent the (ineffective) importation of standard configurations for CiscoASR devices via the Configuration Editor.

WorkaroundWhen using Netcool Configuration Manager Version 6.3 fix pack 6 (orearlier), do not import standard configurations for Cisco ASR devices viathe Configuration Editor, as this will have no effect on the deviceconfiguration.

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

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

Cause Zero length binary data file is being transferred to the device

WorkaroundDo not use Disaster Recovery to apply configurations to an Extreme Switch48xx 15.x if there is a "Warning: No Binary data to apply" message in theUOW log.


Issue: D18 [Extreme Switch 48xx 15.x] Native Diff displaysincorrect changes

Cause Performing diffing on two imported configurations through the NativeShow Differences feature displays false output.

WorkaroundUse the modeled difference feature instead.

Issue: D18 [Huawei DSLAM *MA56* 8*] DSLAM resource icon notbeing displayed

Cause When a Huawei DSLAM device is imported, the icon displayed in NetcoolConfiguration Manager the network resource icon instead of the DSLAMicon

WorkaroundNone

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

Cause The stored configurations and running configurations for Extreme 48xx15.x switches are in different formats, and therefore the 'showconfiguration' command can not be used to interpret these configurations.

WorkaroundNone

The comparing of running and stored configurations in Extreme 48xx 15.xswitches is not supported by Netcool Configuration Manager.

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

Cause When an IBM-BNT VFab 7.x switch is imported, the icon displayed inNetcool Configuration Manager the network resource icon instead of theIBM-BNT icon

WorkaroundNone

Issue D18 [IBM-BNT Switch VFab 7.x] Native Compare exceptionin 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' hasbeen set to TRUE.

WorkaroundDeselect the check box for Native Compare on the configuration tab of theresource access document (RAD). This will prevent a native comparisonfrom being carried out during a apply native commands set unit of work.

To see the changes applied to the native device configuration, select bothconfigs in the Resource Browser's configuration tab, and choose ShowDifferences Native View from the right-click menu.

Issue: D18 ITNCM 6.4.0.2 [Search Set] Applied to NetworkResource with Standard Support

Cause A search set can be erroneously applied to a standard network resource ifthe values of 'Network Resources in a Realm' or 'Network Resourcesretrieved from a Realm' have been selected in the Apply Search Set wizard.


WorkaroundDo not select the values of 'Network Resources in a Realm' or 'NetworkResources retrieved from a Realm' in the Apply Search Set wizard whenapplying search sets to standard network resources.

Issue: D17 [Core] InvocationTargetException on saving a draftconfig

Cause For devices with very large configurations the user may encounter anInvocationTargetException on attempting to save a new configuration draftdue to WebSphere running out of memory.

WorkaroundIncrease the maximum heap size for the embedded WebSphere Applicationserver to a sufficient size or perform housekeeping on the versionedconfigurations to reduce their number.

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

Cause If you want to add, remove, or modify a list of VLANs on a trunk, youhave to issue 'add' or 'remove' commands. However these commands arenot being substituted correctly when submitted to the device via a configchange or restore operation.

WorkaroundUse native commands for configuring VLANs on a trunk.

Issue: D17 Deletion of undocumented command fails formodeled config changes and restore operations

Issue Deletion of undocumented command fails for modeled config changes andrestore operations.

Cause For Junoscript based devices there is an issue with the XML generatedwhen the user deletes srlg configuration data contained within theundocumented section of the routing-options config, and causes modeledconfig operation and restores to fail. This issue could occur with otherundocumented commands also.

WorkaroundRemove the undocumented command with correct Junoscript using anative command set.

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

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

The new configuration will be saved into the device running-configurationand 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.

WorkaroundYou can address this issue in two steps:1. First, ensure that the config is kept in good condition, and turn on

rollback when making config changes.

Chapter 3. Known issues and workarounds 11

2. Secondly, do not pick DR when submitting a versioned config.

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

Issue: D17 [Juniper QFabric] Modeled command setsunsuccessful on Juniper QFabric

Issue Modeled command sets and configuration changes do not completesuccessfully on the Juniper QFabric.

Cause Juniper identified an issue with Junoscript configuration change processingand a fix will be in an upcoming JUNOS software release.

WorkaroundUse native command sets.

Issue: IDT ssh is not working for F5 devices

Cause Currently there is an issue with compatibility with ssh key exchange withthe F5 device.

WorkaroundContact IBM support.

Issue: D17 [Schema] Juniper ERX Config Submit Failureconfiguration||ip||vrf

Issue The ip vrf commands are not completely supported by the translator. Anyconfiguration with ip vrf commands will have issues with any changesmade to these commands and they will not be correctly displayed in theconfig editor interface.

WorkaroundNone

Issue: D17 [Release Notes] driverTools.sh memory requirement

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

WorkaroundModify the default max heap size (-Xmx512m) in the script file to increasethe memory for driverTools.sh. Testing has indicated setting this to 1536mresolves 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: D16 [Nexus 1k] Native Command Set Line By Line Failure

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

WorkaroundTo prevent these failures, the following new inline commands for nativecommand sets are provided. The following commands apply only if Allow


Line by Line for Native Command Set mode is true. If the Allow Line byLine for Native Command Set mode is not true, then NetcoolConfiguration Manager removes the commands.

Table 4. New inline commands for native command sets

Inline command Description

ITNCM-Sleep Allows Netcool Configuration Manager to sleep for thespecified seconds before executing the next command in thelist of native command sets. The following example specifiesa value of 2000 Milliseconds, which means that NetcoolConfiguration Manager sleeps for two milliseconds beforeexecuting the next command in the list.

ITNCM-Sleep=2000

ITNCM-NoPrompt Sets it so that Netcool Configuration Manager waits for noprompt. You can specify one of the following values:

v ITNCM-NoPrompt=true — Netcool Configuration Managerwaits for no prompt when executing commands in nativecommand sets.

v ITNCM-NoPrompt=false — Netcool Configuration Managerwaits for a prompt when executing commands in nativecommand sets.

ITNCM-ChangePrompt Changes the prompt that ITNCM is waiting for whenexecuting commands in NCS. The following examplechanges the default prompt to > (right angle bracket).

ITNCM-ChangePrompt=>

ITNCM-ResetPrompt Resets the prompt to its default value. The default prompt isset in the device script using the default.prompt= prompt.For example, default.prompt=# specifies that the defaultprompt is # (pound sign). You can specify one of thefollowing values:

v ITNCM-ResetPrompt=true — Netcool ConfigurationManager resets the prompt to the default value specifiedin the device script.

v ITNCM-ResetPrompt=false — Netcool ConfigurationManager does not reset the prompt to the default valuespecified 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. Thedefault value is \n. You can specify one of the followingvalues:

v ITNCM-ResetEndOfLine=true — Netcool ConfigurationManager resets the end of line value to the default value.

v ITNCM-ResetEndOfLine=false — Netcool ConfigurationManager does not reset the end of line value to the defaultvalue.

Related informationFor information on command sets, see http://publib.boulder.ibm.com/


http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_configurationmgr.doc_6.4.0/ncm/wip/condev/task/ncm_idt_idtcommandsets.html

infocenter/tivihelp/v8r1/topic/com.ibm.netcool_configurationmgr.doc_6.4.0/ncm/wip/condev/task/ncm_idt_idtcommandsets.html.

For information on the Allow Line by Line for Native Command Setmode, see http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_configurationmgr.doc_6.4.0/ncm/wip/adm/task/ncm_adm_devcom_editingradguiconfig.html

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

Cause When attempting to apply a multi-line MOTD Banner via FTP, only thefirst line will be applied to the configuration.

WorkaroundThis issue is similar to the one described in “Issue: D16 [Nexus 1k] NativeCommand Set Line By Line Failure” on page 12. However, in this case thisis expected behavior and is a limitation of the NX OS on this device.

Issue: Disaster Recovery is not supported on CISCO Nexus1000v

Cause The Disaster Recovery feature is not supported on the CISCO Nexus 1000vdevice.

WorkaroundFollow 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 devicesrunning Netcool Configuration Manager 6.3.0.2 and earlier.

Workaround

1. 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 doneimport the device again.

2. Deselect the Streaming Put check box in the RAD.3. In the device script, comment out the Ftp file section.4. In the Submit Configuration Change window, submit the Versioned

Config and select the Disaster Recovery; Use Raw CLI checkbox.5. Select the Streaming Put check box in the RAD.

Issue: D16 [Avaya 8xxx 7.x] Import of Versioned Config intoEditor

Cause The driver for Avaya Switch 8xxx 7.x does not properly import a versionedconfiguration into the GUI editor window by selecting file > import.

WorkaroundTo import a versioned configuration, select the device from the realmdirectory then select the Configurations tab. Choose the Versionedconfiguration 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 onlyreport against startup vs running configurations. If diffs are needed againsta versioned configuration then use the work around.


http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_configurationmgr.doc_6.4.0/ncm/wip/condev/task/ncm_idt_idtcommandsets.html

http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_configurationmgr.doc_6.4.0/ncm/wip/adm/task/ncm_adm_devcom_editingradguiconfig.html



WorkaroundIf diffs are needed against a versioned configuration then the work aroundis to use the Synchronize option in the Resource Browser after the initialimports to synchronize the configurations.

Related informationFor information on Synchronizing configurations, see http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_configurationmgr.doc_6.4.0/ncm/wip/condev/task/ncm_condev_synchronizingconfigurations.html.

Issue: D17 [Juniper routers and switches] Rollback should notbe selected in UOWs

Issue Rollback options should not be selected in Juniper router and switchUOWs, rollback is done automatically if UOW fails.

Cause Juniper device scripts are setup to automatically rollback if UOW fails toavoid leaving the device in a bad state.

WorkaroundDo not select rollback in UOWs for Juniper devices.

Issue: OS UPGRADES NOT USING THE OS UPGRADE SCRIPTSDEFINED (APAR=IV20852)

Cause When the device script is set in the Resource Access Document (RAD) boththe communications handler and the operating system (OS) upgrade willuse that device script for processing operations. Thus, the OS upgrade willnot use any OS upgrade device script that is defined.

WorkaroundThe user must validate that the correct copy down (copyDown) sections andany other changes that were made to the OS Upgrade device script areincluded in the device script to which the RAD is pointing.

Related informationFor information on device scripts, see http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_configurationmgr.doc_6.4.0/ncm/wip/adm/concept/ncm_adm_devcom_devscriptsover.html.

For information on the copyDown and other device script sections, seehttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_configurationmgr.doc_6.4.0/ncm/wip/adm/reference/ncm_adm_devcom_devscriptssections.html.

For information on creating an OS Upgrade device script, seehttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_configurationmgr.doc_6.4.0/ncm/wip/adm/task/ncm_adm_osman_creatingosupgradescript.html.

Issue: Can't copy more than one image file at a time(APAR=IV20852)

Cause Only one image file can be copied to the server at a time.

WorkaroundIf the device requires two image files, the user must modify the devicescript (or the OS Upgrade device script if there is no device script in theRAD) to copy the extra image file over to the server. The user will have to


http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_configurationmgr.doc_6.4.0/ncm/wip/condev/task/ncm_condev_synchronizingconfigurations.html




http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_configurationmgr.doc_6.4.0/ncm/wip/adm/concept/ncm_adm_devcom_devscriptsover.html




http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_configurationmgr.doc_6.4.0/ncm/wip/adm/reference/ncm_adm_devcom_devscriptssections.html



http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_configurationmgr.doc_6.4.0/ncm/wip/adm/task/ncm_adm_osman_creatingosupgradescript.html



validate that the image files are present on the FTP/TFTP server asNetcool Configuration Manager will not know about them.

Note: The copy commands for the extra image file or files should bespecified in the copyDown section of the device script (or the OS Upgradedevice script if there is no device script in the RAD).

Related informationFor information on device scripts, see http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_configurationmgr.doc_6.4.0/ncm/wip/adm/concept/ncm_adm_devcom_devscriptsover.html.


For information on the copyDown and other device script sections, seehttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_configurationmgr.doc_6.4.0/ncm/wip/adm/reference/ncm_adm_devcom_devscriptssections.html.

Issue: Can't modify fqpath from the gui (APAR=IV20852)

Cause It is not possible to create or modify the <fqpath> element from theResource Browser. The following example shows the fields that theResource Browser displays for an FTP resource called altFtp:Name: altFtpInfoHost: 9.42.13.84Username: icosftpPassword: passwordPath: /

WorkaroundThe user must switch to XML mode (the XML editor) to modify the<fqpath> element in the File Transfer resource.

The Resource Browser displays the following XML file for the altFtp FTPresource. To edit the xml right click on the resource and select edit. Oncethe resource comes up select XML on the top right side of the File Transferresource. Note that the example XML file contains two entries: one for aresource called ftpInfo and one for a resource called altFtpInfo:<?xml version="1.0" encoding="UTF-8"?><ftp encrypted="false"><entry><name>ftpInfo</name><host>9.42.13.166</host><username>icosftp</username><password> value="current">password</password><path>/tftpboot</path><mode>active</mode></entry><entry><name>altftpInfo</name><host>9.42.13.184</host><username>icosftp</username><password> value="current">password</password><fqpath>/tftpboot</fqpath><path>/</path>












<type>ftp</type><mode>active</mode></entry></ftp>

Users must consider the following XML elements associated with the FTPresource:v <path> — In the case of an OS upgrade, Netcool Configuration Manager

uses the value specified in <path> to get the image file from the TFTPserver onto the device. The value specified in <path> is also used whenyou request an FTP/TFTP connection to the server from the device.What this means is that when logging into the FTP server, you willinitially be placed in a home directory as defined by the FTPconfiguration files. This home directory may or may not be where theimage file resides. If the image file does not reside in this location, thenyou will need to navigate up or down the directory structure to accessthe directory in which the images are located. For example, logging intoa server as icosftp/password places you in a directory /, which couldphysically be /home/icosftp/ftpfiles, but that is hidden from the FTPserver. To get to the directory where the image files reside (for example,/opt/cisco/images) would require a <path> value of../../../opt/cisco/images.

v <fqpath> — Netcool Configuration Manager uses the value specified in<fqpath> to check that the OS image file is indeed located on the fileserver. Specifically, the worker server that processes the UOW logs intothe remote server using the credentials specified in the <username> (inthe example, icosftp) and <password> (in the example, password)elements and navigates to the <fqpath> element to check the directory(in the example, /tftpboot) in which the image file is located on the fileserver.The path specified in the <fqpath> element usually differs from the pathspecified in the <path> element for the reasons specified in thedescription of the <path> XML element.

Related informationFor information on managing resources, see http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_configurationmgr.doc_6.4.0/ncm/wip/condev/task/ncm_condev_resources.html.

Issue: Integrating a command set into an OS specification(APAR=IV20852)

Cause It is possible to create an optional command set to modify theconfiguration of a device so that it points to the new operating system (OS)image that is being downloaded to the device. This optional command setintegrates into the OS specification so that the OS upgrade changes thedevice's configuration after the OS image is downloaded to the device andbefore the device is rebooted. This command set can take advantage of theparameterization that is available inside command sets so long as theparameter names are correctly defined.

WorkaroundIntegrating a command set into an OS specification requires you to do thefollowing:v Use a parameterized command setv Test the behavior of the FULL_IMAGE PATH calculation logic


http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_configurationmgr.doc_6.4.0/ncm/wip/condev/task/ncm_condev_resources.html




Use a parameterized command setThe integration of the command set into the OS specification relies on thedata that is contained in the OS registry. More specifically, you define aparameterized command set in the OS registry so that the configuration ofa device points to the new OS image that is being downloaded to thedevice. For each OS image that you want to associate with a specificdevice, you define a parameterized command set using the following XMLelements:v <os name>, </os name> — Specify the OS node to contain the

parameterized command set. Set this name to the name of the OS image.v <image>, </image> — Specify the OS image to be associated with a

specific device.v <commandset>, </commandset> and <param name>, </paramname> —

Specify a parameterized command. You can specify one or more of thesecommands. With one exception, any parameter name and values definedwill be passed directly to the parameter substitution logic used whenpreparing the command set at run time. The exception is theFULL_IMAGE_PATH parameter.

v <commandset>, </commandset> and <paramname="FULL_IMAGE_PATH">,fullImagePath </paramname> — Specify aspecial command that makes use of the FULL_IMAGE_PATH value. ThefullImagePath specifies empty, NULL, or the name of the OS image. Youcan specify only one FULL_IMAGE_PATH parameter for each OS node.The value of the FULL_IMAGE_PATH parameter can be modified by internalOS Upgrade logic at runtime. This OS Upgrade logic can use otherparameters including FILE_SYSTEM, SEPARATOR, and IMAGE_PATH.

The following example shows the definition of one OS node in an OSregistry, using the previous XML elements that are necessary to integratethe command set into the OS specification:<os name="c2800nm-adventerprisek9-mz.124-1a.bin"> 1

<image>c2800nm-adventerprisek9-mz.124-1a.bin

</image> 2...

<commandset> 3<param name="some parameter name">

somevalue</param>

.

.

.</commandset><commandset> 4

<param name="FULL_IMAGE_PATH">c2800nm-adventerprisek9-mz.124-1a.bin

</param></commandset>

.

.

.</os>

The following list describes each of the numbered items in the previousexample:


1. Specify an OS node, which is the OS image file name, includingextension type. In the example, the OS image is calledc2800nm-adventerprisek9-mz.124-1a.bin.

2. Specify the file name, including extension type, of the OS image, whichin the example is c2800nm-adventerprisek9-mz.124-1a.bin.

Note: You use the <image>, </image> XML elements to bypass theconnection to the FTP server to retrieve a list of images.

3. Specify a parameterized command set. The optional command set usesthis parameterized command set to perform some action. Anyparameter name and values can be defined.

Note: The vertical ellipses indicate for each OS node any number of<commandset>, </commandset>, <param name>, </paramname> XMLelements can be specified.

4. Specify the FULL_IMAGE_PATH parameter. Note that the OS image file(c2800nm-adventerprisek9-mz.124-1a.bin) is also specified. Theoptional command set uses the FULL_IMAGE_PATH parameter to set theboot parameters.

The following provides a textual description of the OS Upgrade logic atruntime:1. Set a temporary string named fullImagePath to the value of the

FULL_IMAGE_PATH parameter.2. If fullImagePath is empty or NULL, simply pass the defined parameter

name-value pairs to the parameter substitution logic.a. Else if fullImagePath is the same as the image name (the value

specified for the <image> XML element) proceed with the followinglogic:

v If the parameter FILE_SYSTEM is defined and not null or empty thenreplace the value of fullImagePath with the value of the FILE_SYSTEMparameter.Else, replace the value of fullImagePath with the value of the filesystem from that selected in the Upgrade Specification.

v If the parameter SEPARATOR is defined and not null or empty thenappend the value of the SEPARATOR parameter to fullImagePath.Else, append the “ “ (a space character) to fullImagePath.

v If the parameter IMAGE_PATH is defined and not null or empty thenappend the value of the IMAGE_PATH parameter to fullImagePath.

v If the parameter IMAGE_NAME is defined and not null or empty thenappend the value of the IMAGE_NAME parameter to fullImagePath.Else, append the value of the image name (the value specified for the<image> XML element) to fullImagePath.

3. Finally, set the value of the FULL_IMAGE_PATH parameter to the value offullImagePath and pass the defined parameter name-value pairs to theparameter substitution logic.

Test the behavior of the FULL_IMAGE PATH calculation logicSince the internal logic used to calculate the effective value ofFULL_IMAGE_PATH may change in future releases, it is recommended you testthe actual parameter value calculations by executing an OS Upgrade devicescript using the intended parameters in report-only mode. The CLI thatwould be sent to the device can be seen in the resulting UOW log. Note


that the target device will need to be on line even for report-only testingsince the OS Upgrade device script workflow still contacts the device tovalidate RAM and file system availability.

To generically test the behavior of the FULL_IMAGE_PATH calculation logic forplanning or informational purposes, you can simply copy one of the <os>nodes in an OS Registry XML, paste it back into the XML doc, change the<os name> parameter value of the new <os> node, and change the<commandset> node to look like the following:<commandset>

<param name="FULL_IMAGE_PATH"> </param><param name="SEPARATOR"></param><param name="FILE_SYSTEM"> </param><param name="IMAGE_PATH"> </param>

</commandset>

Then you can add values based on the logic described earlier, submit anOS Upgrade device script using the new test image data in report-onlymode, and check the resulting command set UOW log to see what CLIwould have been sent to the device.

Note: Note that it is currently necessary to include the FULL_IMAGE_PATHparameter in the XML (even if the value is empty) to avoid XML parsingerrors. Also note that if the command set includes any parameter namesthat are not defined in the XML, the command set processing will fail.Having extra parameters defined in the XML (such as those that may beused for internal processing of the FULL_IMAGE_PATH parameter) but are notreferenced in the command set will not cause any errors; they will simplybe ignored during command set parameter substitution.

Related informationFor information on an OS specification, see http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_configurationmgr.doc_6.4.0/ncm/wip/adm/concept/ncm_adm_osman_osspecification.html.

For information on an OS registry, see http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_configurationmgr.doc_6.4.0/ncm/wip/adm/concept/ncm_adm_osman_osregistry.html.



http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_configurationmgr.doc_6.4.0/ncm/wip/adm/concept/ncm_adm_osman_osspecification.html




http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_configurationmgr.doc_6.4.0/ncm/wip/adm/concept/ncm_adm_osman_osregistry.html







Notices

This information was developed for products and services offered in the U.S.A.

IBM® may not offer the products, services, or features discussed in this documentin other countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not grant youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle Drive Armonk, NY10504-1785U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan, Ltd.19-21, Nihonbashi-Hakozakicho, Chuo-kuTokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law: INTERNATIONALBUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFNON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULARPURPOSE. Some states do not allow disclaimer of express or implied warranties incertain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.


IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM Corporation958/NH04IBM Centre, St Leonards601 Pacific HwySt Leonards, NSW, 2069Australia

IBM Corporation896471/H128B76 Upper GroundLondon SE1 9PZUnited Kingdom

IBM CorporationJBF1/SOM1294 Route 100Somers, NY, 10589-0100United States of America

Such information may be available, subject to appropriate terms and conditions,including in some cases, payment of a fee.

The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurements may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

All statements regarding IBM's future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include the


names of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. You may copy,modify, and distribute these sample programs in any form without payment toIBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operatingplatform for which the sample programs are written. These examples have notbeen thoroughly tested under all conditions. IBM, therefore, cannot guarantee orimply reliability, serviceability, or function of these programs.

If you are viewing this information softcopy, the photographs and colorillustrations may not appear.

TrademarksIBM, the IBM logo, ibm.com®, AIX®, Tivoli®, Tivoli Enterprise Console, andNetcool® are trademarks or registered trademarks of International BusinessMachines Corporation in the United States, other countries, or both.

Adobe, Acrobat, Portable Document Format (PDF), PostScript, and all Adobe-basedtrademarks are either registered trademarks or trademarks of Adobe SystemsIncorporated in the United States, other countries, or both.

Java™ and all Java-based trademarks and logos are trademarks orregistered trademarks of Sun Microsystems, Inc. in the United States,other countries, or both.

Linux is a registered trademark of Linus Torvalds in the United States, othercountries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks ofMicrosoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Notices 23

��

Printed in the Republic of Ireland

netcool configuration manager version 6 release 4 · pdf filehuawei cir1uen dslam smartax...

Documents