Integration scenarios

In this scenario, notifications of configuration changes are sent to OMNIbus, which are correlated to network faults and performance indicators to identify the root cause of a network outage. This integration scenario consists of the following steps:

1. A change is made, such as shutting down an interface from Tivoli Netcool Configuration Manager.
2. An event shows up on the Tivoli Netcool OMNIbus Active Event List (AEL).
   • The operator launches the Tivoli Netcool Configuration Manager Activity Viewer in context from the AEL to investigate.
   • The operator drills down further into various integrated interfaces to investigate, such as the Tivoli Common Reporting 'Configuration and OS Change Summary' report and the Network Manager Network Views.
3. The operator corrects the problem by restarting the interface from the Tivoli Netcool Configuration Manager Submit Configuration Change wizard, by applying a previous configuration.
   • The operator launches various integrated interfaces to validate the configuration change, such as Network Manager Network Views and the Tivoli Netcool Configuration Manager Queue Manager.
   • Events are cleared on the Tivoli Netcool OMNIbus AEL.

This integration scenario provides a launch-in-context from a network problem to restore network service. This scenario consists of the following steps:

1. A device goes red.
2. The operator is watching the network map and notices the problem.
3. The operator launches a report in context from the device.
4. The operator launches the Tivoli Netcool Configuration Manager Activity Viewer in context from the device.
5. The operator identifies the configuration that needs to be rolled back.
6. The operator applies the rollback in context from Tivoli Netcool Configuration Manager's Submit Configuration Change wizard.
7. The device goes green in the network map.

This scenario uses Tivoli Netcool Configuration Manager's configuration command sets to implement configuration standards across all network devices. The following steps describe the data flow:

1. The administrator has installed the mttrapd probe.
2. The administrator wants to enable the network SNMP traps.
3. The administrator launches Tivoli Netcool Configuration Manager.
4. The administrator creates multiple command sets for different devices (such as CISCO IOS, CISCO CATOS, or Juniper JUNOS).
5. The administrator applies the command sets for selected devices.
6. The administrator verifies that mttrapd events appear on Netcool OMNIbus.

This scenario uses Tivoli Network Manager's view of network services to apply a compliance policy across a set of network resources to support the network service. The data flow is described as follows:

1. A service provider receives an order to create a new VPN for a new client ZYX, with several branches.
2. Service provider wants to verify that VPN configuration is compliant across all client ZYX facing routers.
3. Tivoli Netcool Configuration Manager administrator creates a MPLS VPN policy for client ZYX.
4. The Tivoli Network Manager administrator launches Tivoli Network Manager and MPLS views.
5. In the Tivoli Network Manager and MPLS view, suitable routers are identified.
6. The Tivoli Netcool Configuration Manager administrator launches the Tivoli Netcool Configuration Manager Applying policies wizard.
7. The Tivoli Netcool Configuration Manager administrator executes the policy against the selected devices. After the policy runs, the Tivoli Network Manager administrator launches in-context compliance reports and sees if the identified devices support the new network service.