|
|
The "Configuration Synchronization" chapter explains how ViewRunner synchronizes its cache, stored in the Oracle database, with the actual Cisco 6100 element database. This chapter also explains auto-discovery which is the process of capturing inventory and configuration information about Cisco 6100 chassis and modules through an automated procedure.
Synchronizations are the methods by which ViewRunner is kept current with what is actually happening in the network. There are two basic types of synchronization done by ViewRunner:
Configuration, alarm, View Map, and OpenView Map synchronization algorithms are used to keep ViewRunner current with the node/network state.
This chapter concentrates on the ViewRunner configuration synchronization with Cisco 6100 nodes. See "ViewRunner Maps and Views" for information on View Map synchronizations, and see "Events and Alarms Management" for information on alarm synchronizations.
When windows are first opened in ViewRunner, certain information about the network and its components is displayed. The following lists some of this information and the source of that information:
Client windows are updated dynamically in real time while they are open. Error/event traps are propagated to all clients, updating alarm colors and the Event Categories window. Recovery from traps that are lost is done by an automatic polling of the Cisco 6100 alarm state and then propagated to clients. Other changes detected by ViewRunner servers are propagated to clients when one or more of the following conditions exist:
Configuration synchronization is the process of bringing the ViewRunner cache up-to-date with the actual Cisco 6100 element database. The process is either a manual or a scheduled event that synchronizes the ViewRunner OpenView Oracle database with the configuration stored in the Cisco 6100. It is important for ViewRunner to maintain this cache of Cisco 6100 information to facilitate more rapid display of dialogs (especially summary list dialogs for a node, subnetwork, or network) and to facilitate the service-oriented EMS API.
ViewRunner can get out of sync with a Cisco 6100's configuration when another management system issues SNMP sets to a Cisco 6100. The following are examples of other element management systems (EMS) which could change the configuration data for a network:
ViewRunner gets out of sync with a Cisco 6100's alarm state when traps are not received. This can happen when UDP is unreliable, so traps can be lost, reordered, or duplicated. It also happens when the trap destination is not set correctly in the Cisco 6100.
Configuration synchronization accomplishes the following:
ViewRunner uses an optimized algorithm to determine the minimum synchronization that needs to take place to assure Oracle database integrity. The algorithm compares the Cisco 6100 SNMP set counts and ViewRunner cache and trap sequence numbers to determine the level of synchronization needed.
The configuration synchronization algorithm retrieves the minimum amount of Cisco 6100 data to get ViewRunner totally in sync with the Cisco 6100 configuration. This reduces the network and CPU demands to accomplish synchronization substantially. The system supports manual override to force a full configuration synchronization if necessary.
The configuration synchronization algorithm uses three synchronization levels to maintain data integrity between the Cisco 6100 and the Oracle database:
There are a variety of conditions that cause a configuration synchronization to occur automatically (or as scheduled). Some of these conditions are set/controlled by configuration variables. See the ViewRunner for HP OpenView Set Up and Installation Guide for a listing of all configuration variables.
Automatic intelligent synchronizations occur when:
There are four ways to start an intelligent sychronization manually:
Step 1 Click on the Synchronize 6100 Configuration icon on the toolbar icon (the far left icon as shown below)
Step 2 Select Synchronize 6100 Configuration from the ViewRunner Discover menu
Step 3 Right click on the chassis part (rather than on a module or slot) of the 6100 Chassis View and select the Synchronize 6100 Configuration pop-up menu item.
Step 4 Command line invocation (vrPerformConfigSync) supports specifying individual Cisco 6100s, a list of Cisco 6100s, or all Cisco 6100s (sequentially) for configuration synchronization
Partial synchronizations occur when the Module Property dialogs are opened.
During a configuration synchronization, user requests (mouse clicks) within ViewRunner are queued, effectively "locking out" management of the Cisco 6100. This lockout is typically a minor inconvenience.
The lockout duration depends on how fully configured the Cisco 6100s are and how out of sync the ViewRunner is with the Cisco 6100s. For example, a system with 64 ATU-Cs, 64 LIM ports and subscribers, and 64 PVCs (a Direct Connect configuration) takes approximately 45 seconds to complete a full configuration synchronization. Whereas, a system with 64 ATU-Cs, 400 LIM ports and subscribers, and 1600 PVCs takes approximately 4 to 5 minutes to complete a full configuration synchronization.
If you use a cron job to synchronize the Cisco 6100s, we recommend that you use a "low usage time" to run the job. This will minimize the user lockout frequency during heavier management periods.
The following is an example of a cron job that will perform a configuration synchronization on a Cisco 6100 named "lr01" every night at 3:00 am using a script called "config_sync". To synchronize all Cisco 6100s, substitute the keyword "all" for "lr01" in the last line.
#ident `'@(#)root 1.12 94/03/24 SMI'' /* SVr4.0.1.1.3.1 */
#crontab
#
0 3 * * * sh /opt/VR4HPOVS/config_sync lr01
The following is an example of the config_sync script used in the cron job. The script assumes that the ViewRunner servers were installed in /opt/VR4HPOVS.
#!/bin/ksh
. /opt/VR4HPOVS/env/vrs.kshrc
/opt/VR4HPOVS/bin/vrPerformConfigSync -n $1
When Cisco 6100s or Cisco 6100 components are added to the network, their presence is automatically detected and propagated to ViewRunner clients to maintain synchronization. In addition, HP OpenView uses a discovery algorithm which detects all IP addressable network devices, such as the Cisco 6100. This detection process is called discovery. For Cisco 6100s to be automatically discovered, IP Discovery must be enabled in HP OpenView. To enable IP Discovery, use the following steps:
Step 1 Select Options > Network Polling Configuration: IP
Step 2 Check the Discover New Nodes box
Step 3 Set the discovery interval to one of the following
(a) Auto Adjust
(b) Fixed
The Auto Adjust discovery interval polls the existing SNMP nodes at a variable interval to determine if new nodes exist. As fewer nodes are found per polling cycle, the frequency of the polling interval decreases allowing traffic to decrease as more of the network is discovered. The Auto Adjust option is the better choice for networks where all Cisco 6100s have trap recipient addresses set correctly. In this case, a cold start trap will be received when a Cisco 6100 is added to the network, and it will be discovered automatically then. To determine the current auto adjusting interval, use the Fault > Network Connectivity > Poll Node operation.
During auto-discovery, the following steps take place within the Cisco 6100:
Step 1 Each inserted module conducts a self test to check for hardware malfunctions.
Step 2 The module then notifies the SC that it is present by passing relevant inventory attributes to the SC.
Step 3 Once the SC gets inventory information, it creates a system configuration and stores auto-discovered attributes and other default configuration details within the SNMP agent.
Step 4 If a module is faulty, the module does not send a message to the SC. The SC is therefore not able to auto-discover the module. Faulty modules are recognizable by certain LED conditions on the module faceplate. For more information on LED indicators, see the Cisco 6100 Set Up and Installation Guide.
Step 5 The SNMP agent issues a module insertion trap for the newly discovered module.
Step 6 Once the SNMP agent issues the module insertion trap, the information is immediately propagated to the all the ViewRunner clients.
Each module and chassis is equipped with a flash EPROM programmed at the factory with the following read-only attributes. These attributes are sent to the System Controller (SC) during the auto-discovery process performed by the Cisco 6100 software.
ATU-C modules also return the following transceiver information:
Multiplexer Chassis (MC) presence is inferred if an SC is present. Line Concentration Chassis (LCC) presence is inferred if a LIM Controller module is present (DOH configurations only). The LIM Controller forwards all LIM notifications to the SC.
Upon detection of a chassis or module by the Cisco 6100 software, if a configuration does not exist for the chassis or the slot, the Cisco 6100 SNMP agent automatically creates one using default configuration data. The Administrative State for the chassis or module defaults to locked.
A Cisco 6100 chassis or module configuration gets created whenever the following conditions occur:
The following Cisco 6100 components are auto-discovered in this release.
If a module is removed and its slot is left empty (or if a module is removed and another module is inserted) the originally auto-discovered module and its default configuration settings will remain in the system configuration.
As another example, if a chassis ID dip switch setting is modified, only the original dip switch settings are stored by the Cisco 6100 SNMP agent. A slot configuration must be deleted by an operator in order for the newly detected module to be correctly discovered with its default configuration settings.
For instructions on adding and deleting modules, see "Adding and Deleting System Components".
When ViewRunner is used to display the Chassis View for a Cisco 6100 for the first time, ViewRunner for HP OpenView queries the Cisco 6100 SNMP Agent for the modules that have been auto-discovered. Once ViewRunner for HP OpenView gets this information from the agent, it displays the front chassis and module faceplates of the Cisco 6100 in its graphical user interface. ViewRunner for HP OpenView displays each of the chassis/module attributes described above.
ViewRunner for HP OpenView also supports querying the agent for auto-discovered chassis/modules after the application has started. This is done by selecting the Synchronize 6100 Configuration option on the Discover menu of the 6100 Chassis View.
Posted: Fri Oct 8 12:51:25 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.