Configuring the Nokia Solutions and Networks NetViewer collector

To use data from the Nokia Solutions and Networks (NSN) NetViewer collector in a network discovery, you must configure the connection details between the NSN NetViewer EMS and Network Manager.

About this task

You can also configure additional information to be collected from the EMS. To configure the NSN NetViewer collector, complete the following steps:

Procedure

  1. Change to the NSN NetViewer collector directory.
    cd $NCHOME/precision/collectors/javaCollectors/NetViewer/
  2. Within this directory, find the sample configuration file for the NSN NetViewer collector and copy it to the working configuration file.
    cp NetViewerCollector.properties.sample NetViewerCollector.properties
  3. Edit the collector configuration file:
    $NCHOME/precision/collectors/javaCollectors/NetViewer/NetViewerCollector.properties.
  4. Configure the following collector properties:
    port
    Port on which to run the embedded collector server. The port must match the port configured in the insert into the collectorFinder.collectorRules table in the DiscoCollectorFinderSeeds.cfg file. The default value is 8080.
    log.filename
    Filename for the NSN NetViewer collector log file. The default value is NetViewerCollector.log.
    log.level
    Level of logging for the collector framework. The default value is INFO.
    trace.filename
    Filename for the NSN NetViewer collector trace file. The default value is NetViewerCollector-trace.log.
    trace.level
    Level of trace for the collector framework. The default value is INFO.
  5. Configure data acquisition parameters for the collector:
    collectData
    Takes one of the following values. The default value is True.
    True
    Enables the collector. The collector collects data from the EMS.
    False
    Disables the collector. The collector does not collect data from the EMS.
    DataAcquisition.GetEntities
    Takes one of the following values. The default value is 0.
    1: Enable
    Enables download of physical entity data from the EMS.
    0: Disable
    Disables download of physical entity data from the EMS.
    DataAcquisition.GetLayer2Connections
    Takes one of the following values. The default value is 0.
    1: Enable
    Enables download of layer 2 connectivity data from the EMS.
    0: Disable
    Disables download of layer 2 connectivity data from the EMS.
  6. You can optionally configure details about the source element management system (EMS) in the Data Source properties section by configuring the following generic fields. Data from these fields is used by Network Manager to model the EMS.
    DataSource.id
    Unique identifier for the datasource, in the form of an integer. This field takes the value 1, indicating that this is the primary data source.
    DataSource.descr
    Description of the EMS.
    DataSource.emsHost
    Hostname of the EMS.
    DataSource.emsName
    Name of the EMS.
    DataSource.emsPort
    Port of the EMS.
    DataSource.emsVersion
    Version of the EMS.
    DataSource.emsIdentifier
    Identifier for the EMS and key to integrate the Network Manager collector with the Netcool Configuration Manager driver.
    DataSource.emsRole
    Role of the EMS. This parameter can take one of the following values:
    • unknown
    • primary
    • backup
    • other
    DataSource.emsStatus
    Status of the EMS. This parameter can take one of the following values:
    • unknown
    • up
    • down
    • other
    DataSource.emsUserName
    Username of the EMS.
    DataSource.emsPassword
    Password of the EMS.
    DataSource.SecondaryEmsHost
    Host address of the Secondary EMS.
    DataSource.SecondaryEmsPort
    Port of the Secondary EMS.
    Datasource.switchEms
    You can use this parameter to switch between the primary and secondary EMS.
  7. Do not modify the following ORB initialization properties unless directed by IBM® Support:
    These properties are codified as name-value pair parameters.
    orbProp.1.name=org.omg.CORBA.ORBClass
    orbProp.1.value=com.ibm.CORBA.iiop.ORB
    Specifies the IBM ORB implementation to be activated.
    orbProp.2.name=org.omg.CORBA.ORBSingletonClass
    orbProp.2.value=com.ibm.rmi.corba.ORBSingleton
    Specifies the IBM ORB implementation to be activated.
    orbProp.3.name=com.ibm.CORBA.Debug.Output
    orbProp.3.value=../log/orbtrc.log
    Specifies the log file to which to write ORB error messages when the collector fails to connect to the CORBA service on the EMS.
    orbProp.4.name=com.ibm.CORBA.ORBWCharDefault
    orbProp.4.value=UTF16
    Indicates that character encoding set UTF16 is to be used for integration with the NSN NetViewer EMS.
    orbProp.5.name=com.ibm.CORBA.ListenerPort
    orbProp.5.value=10005
    Integration with the NSN NetViewer EMS uses a Corba Interoperable Object Reference (IOR) file. Interfacing using an IOR file requires bidirectional communication. To facilitate this, the ListenerPort parameter is set to port 10005, and this is the port to be used for communication from the NSN NetViewer EMS to the collector. This parameter setting is especially important if you want to integrate the collector to the NSN NetViewer EMS in a NAT or firewall environment.
  8. Configure the naming service properties:
    nameService.useNameService
    Takes one of the following values. Default value is True.
    True
    Collector obtains the root naming context reference by accessing the naming service using a corbaloc URL
    False
    Collector obtains the root naming context reference from the specified IOR file and bypasses the naming service.
    nameService.iorFile
    The full filepath to the IOR file containing the NameService reference. Supports local filepath and remote filepath; for example, HTTP, and FTP.
    nameService.nameServiceName
    Service name for the naming service.
  9. Configure the EmsSessionFactory properties:
    emsSessionFactory.useNameService
    Takes one of the following values. Default value is True.
    True
    Collector obtains the EmsSessionFactory_I reference by using the naming service and by resolving the specified naming context properties.
    False
    Collector obtains the EmsSessionFactory_I reference from the specified IOR file and bypasses the naming service.
    emsSessionFactory.iorFile
    Full filepath to the IOR file containing the EmsSessionFactory reference. Supports local filepath and remote filepath; for example, HTTP, FTP.
  10. Configure the manager properties:
    manager.emsMgr
    Name for the EMSMgr interface. The default value is EMS.
    manager.equipmentInventoryMgr
    Name for the EquipmentInventoryMgr interface. The default value is EquipmentInventory.
    manager.managedElementMgr
    Name for the ManagedElementMgr interface. The default value is ManagedElement.
    manager.multiLayerSubnetworkMgr
    Name for the MultiLayerSubnetworkMgr interface. The default value is MultiLayerSubnetwork.
  11. In the Iterator properties section, configure the CORBA iterator properties:
    iterator.resultSize
    Specifies the maximum number of results returned for each set by the CORBA Iterator. The default value is 20. Increase this value if you want to decrease the number of iterations and increase the size of the data response from the EMS.
    iterator.destroyIterator
    Set to true if you want the CORBA Iterator to destroy the corresponding iterator object on the EMS side. The default value is false. Enable this property only if the EMS does not automatically perform memory garbage collection.
  12. Configure the extraInfo mappings properties:
    These properties map the values of the provided fields into the respective tables in the NCIM database. Multiple values can be specified, but must be differentiated by a numeral in the properties; for example, chassisData.2.extraInfo , shelfData.3.extraInfo , and so on.
    • chassisData.1.extraInfo
    • shelfData.1.extraInfo
    • slotData.1.extraInfo
    • moduleData.1.extraInfo
    • ptpData.1.extraInfo
    • ctpData.1.extraInfo
    • topologyData.1.extraInfo
  13. Save the collector configuration file.