Oracle® Communications Network Integrity

Discovering MIB II SNMP Action Changes

As part of this feature implementation, Discover MIB II SNMP action is added with following two new discovery processors:

• Device Interface Name Remodel Initializer Processor

• Device Interface Name Remodeler Processor

Device Interface Name Remodel Initializer Processor

This discovery processor initializes the ”remodelerProperties” based on following MBean properties:

Discover MIB II SNMP:DI Name Remodel Initializer:DeviceInterfaceNameModeling:PerformRemodeling

Discover MIB II SNMP:DI Name Remodel Initializer:DeviceInterfaceNameModeling:LocationOfAutoDiscoverycfg

Device Interface Name Remodeler Processor

This discovery processor performs the remodeling of Logical Device hierarchy based on configuration information provided in AutoDiscover.cfg file. Table 2 provides the variable information for the processors.

These new processor changes on the ”Discover MIB II SNMP” action are also available in all the extended out-of-the-box actions, for example ”Discover Generic Cisco SNMP” and ”Discover Enhanced Cisco SNMP” to utilize this feature.

Enabling the Device Interface Name Remodeler

By default an SNMP scan does not run with the Device Interface Name Remodeler. To enable Device Interface Name Remodeler, you must set the ”PerformRemodeling” property to true and provide the AutoDiscovery.cfg file location to ”LocationOfAutoDiscoverycfg” for their specific SNMP scan. You do this using ”System MBean Browser” in Oracle Weblogic Enterprise Manager.

Figure 2 shows the ”System MBean Browser” in Oracle WebLogic Enterprise Manager for the Discover MIB II SNMP action.

Figure 2 Action Properties List in the Oracle Enterprise Manager

Description of ''Figure 2 Action Properties List in the Oracle Enterprise Manager''

Customize Device Interface Name Modeling

To enhance or customize the Device Interface name modeling, perform the following:

• You must create a new Cartridge with a new Discovery Action extending MIB II / Cisco SNMP actions. This is because both the OOB MIB II and the Cisco cartridges are sealed and you do not modify them directly.

• Add all required dependencies cartridges to the new cartridge. For example, Address_Handler and MIB_II_SNMP_Cartridge and select ”IPAddressHandler” as an Address Handler for a new discovery action.

• Create a CustomDINameRemodeler class by extending the DefaultDINameRemodeler class in the package:

  oracle.communications.integrity.mibiisnmpcartridge.discoveryprocessors

  In the CustomDINameRemodeler class override the performDINameRemodeler() method or any specific function of DefaultDINameRemodeler based on your new requirement.

  The following is an example of a CustomDINameRemodeler class:

  public class CustomDINameRemodeler extends DefaultDINameRemodeler {
      @Override
      public void performDINameRemodeler(LogicalDevice logicalDevice,
                                         DINameRemodelerProperties properties)
                                         throws ProcessorException {
         // Custom Remodeling goes here.
      }
  }
  

• Create a new discovery processor ”DI Name Remodeler Customizer” and move it above the ”DI Name Remodeler” processor in processor list and select ”remodelerProperties” as the input parameter.

  Figure 3 shows the result after you move the ”DI Name Remodeler Customizer” above the ”DI Name Remodeler” processor. Figure 4 shows the selection of the ”remodelerProperties” as the input parameter for the ”DI Name Remodeler Customizer”.

  Figure 3 Processors Related to this Action

  
  Description of ''Figure 3 Processors Related to this Action''
  
  

  Figure 4 Discovery Processor Properties

  
  Description of ''Figure 4 Discovery Processor Properties''
  
  

• Create an implementation class for a new ”DI Name Remodeler Customizer” processor. For example, create the following class:

  DINameRemodelerCustomizerProcessorImpl

  You set the instance of CustomDINameRemodeler to ”remodelerProperties” using the setNameRemodeler() method.

• Set the implementation class for the ”DI Name Remodeler Customizer” with the package and implementation class name.

Example 1 provides code for a sample implementation class DINameRemodelerCustomizerProcessorImpl.

public class DINameRemodelerCustomizerProcessorImpl implements
             DINameRemodelerCustomizerProcessorInterface {
   @Override
   public void invoke(DiscoveryProcessorContext context,
                      DINameRemodelerCustomizerProcessorRequest request)
                          throws ProcessorException {
     DINameRemodelerProperties remodelerProperties =
           request.getRemodelerProperties();
     if(remodelerProperties.isPerformRemodeling()){
         CustomDINameRemodeler customRemodeler = new CustomDINameRemodeler();
         remodelerProperties.setNameRemodeler(customRemodeler);
      }
   }
}

Support for Single Sign-On Authentication

Network Integrity now includes support for single sign-on (SSO) authentication. Network Integrity implements the SSO authentication solution using Oracle Access Manager, which enables you to seamlessly access multiple applications without being prompted to authenticate for each application separately. The main advantage of SSO is that you are authenticated only once, which is when you log in to the first application; you are not required to authenticate again when you subsequently access different applications within the same web browser session.

Network Integrity also supports single logout (SLO). If you access multiple applications using SSO within the same web browser session, and then if you log out of any one of the applications, you are logged out of all the applications.

See "Setting Up Network Integrity for Single Sign-On Authentication" in Network Integrity Installation Guide for more information.

Support for CPU Utilization-enabled Discovery

The Cisco Router and Switch SNMP cartridge and Cisco Router and Switch UIM Integration cartridge have been enhanced to support CPU utilization-enabled discovery. These cartridges now enable you to discover devices based on their CPU utilization by setting a threshold value (in percentage) in the discovery scan.

See Network Integrity Cisco Router and Switch SNMP Cartridge Guide and Network Integrity Cisco Router and Switch UIM Integration Cartridge Guide for more information.

If the CPU utilization value of a device exceeds the user-specified threshold value, the scan for that device is skipped. The discovery scans are run only for those devices whose CPU utilization value is less than the user-specified threshold value.

To support the discovery of devices based on CPU utilization, a new scan parameter group, CPU Utilization Parameters, has been added in the NetworkIntegritySDK cartridge. This scan parameter group adds the CPU Utilization % field to the Network Integrity UI Scan Configuration screen. The CPU Utilization % field accepts a value between 1 to 99.

See Network Integrity Developer's Guide for more information.

New CLI Cartridge Introduced

The Command Line Interface (CLI) cartridge allows you to build deployable cartridges that connect to devices and retrieve information using CLI commands over Telnet or Secure Shell (SSH) protocol.

The CLI cartridge provides the following key features:

• Telnet protocol and SSH communication with CLI devices

• Record and playback of CLI communication

The CLI cartridge is an abstract cartridge, meaning that Design Studio is used to configure and assemble the run time cartridge against devices before deploying it into Network Integrity.

The CLI cartridge ZIP file contains a reference implementation cartridge for discovering Cisco devices running the IOS XR operating system and retrieves information about virtual private LAN services (VPLSs) on the Cisco IOS XR devices.

See Network Integrity CLI Cartridge Guide for more information.

Extended Oracle Communications Information Model Support

Network Integrity now enables you to model packet connectivity entities in Design Studio to enhance the integration with Oracle Communications Unified Inventory Management (UIM).

To support packet connectivity, Network Integrity adds support to additional Oracle Communications Information Model (OCIM) entities in the following entity categories:

• Connectivity Entities

• Logical Device Entities

• Signal Structure Entities

• Capacity Consumption Pattern Entities

Network Integrity CLI Cartridge Guide Introduced

The Network Integrity 7.3.2 documentation set includes a new guide entitled Network Integrity CLI Cartridge Guide. This guide explains the functionality and design of the Oracle Communications Network Integrity CLI cartridge.