1 “Lightning Bolt” Trap Multiplexor DSM Example Revised Mar 26 2001

1

““Lightning Bolt”Lightning Bolt”Trap Multiplexor DSM ExampleTrap Multiplexor DSM Example

Revised Mar 26 2001

2

OverviewOverview Medium Sized Central plus ROC Central Facility to control ~50 sites Sites contain few to many Win95, NT, Unix

machines running mission-critical software Variable bandwidth from sites to central

facility Some sites are autonomous entities with

local management and operations. Most sites lack local intelligence

3

Typical (Small) Site ScenarioTypical (Small) Site Scenario

NT & perhaps Unix Servers, 10-50 Windows 95 client workstations

One dedicated Enterprise Management NT Hardware Monitoring Required Database monitoring on NT/Unix Servers Linked to an ROC and a central site for

operations and support

4

Small Site StructureSmall Site Structure

Site DSMpings Nodes

Site TNG box with DSM


Unix Unix

USD NT USD NT F/P NT F/P NT

Win 95 Win 95

5

Large Site ScenarioLarge Site Scenario

NT & Unix Servers, 600 Windows 95 client workstations

Two USD servers Two File/Print servers Two dedicated Enterprise Management NT Hardware Monitoring Required Database monitoring on NT/Unix Servers Linked to local ROC and central site for


6

Large Site StructureLarge Site Structure

Site DSMsping Nodes



Unix Unix


600*Win95

600*Win95

Site TNG boxes

with DSMs

Site TNG boxes

with DSMs


7

Central Site ScenarioCentral Site Scenario

NT & Unix Servers, 1500 Windows 95 client workstations

Five USD servers Five File/Print servers Five dedicated Enterprise Management NT Hardware Monitoring Required Database monitoring on NT/Unix Servers Linked to local ROC and central site for


8

Central Site StructureCentral Site Structure

Site DSMsping Nodes



Unix Unix


600*Win95

600*Win95

Site TNG boxes

with DSMs

Site TNG boxes

with DSMs


Site TNG boxes

with DSMs

Site TNG boxes

with DSMs

Site TNG boxes

with DSMs

Site TNG boxes

with DSMs

Site TNG boxes

with DSMs

Site TNG boxes

with DSMs

USD NT USD NT USD NT USD NT USD NT USD NT F/P NT F/P NT F/P NT F/P NT F/P NT F/P NT

9

Central Monitoring FacilityCentral Monitoring Facility

Customer required NetView and TNG to be able to simultaneously utilise site information.

ROC may need a subset view of local information

NetViewNetView

Unicenter TNG

Unicenter TNG

TrapMultiplexor

10

The TNG SolutionThe TNG Solution

Dedicated DSM or Domain Manager to provide Multiplexing of traps CA-Unicenter TNG WorldView and DSM act as one recipient of traps Agents and Lightweight DSM at each site issuing traps to Multiplexing DSM which feeds NetView and central TNG plus ROC TNG

Customization issues here are setting up the Multiplexing DSM & TNG DSM configuration

11

TNG Solution - At each siteTNG Solution - At each site

TNG Agents deployed on servers and some critical clients– HP-UX: Os, Log, Pro and Oracle Agents– NT & Win 95: Os Agent

One NT Server per site designated as a Site DSM

Site DSM heartbeats local nodes Nodes directly trap to Central DSM No need for site WVGateway

12

TNG Solution - At the Sites...TNG Solution - At the Sites...

Site DSMpings Nodes

Site DSMSite DSM

Unix Unix

Win NT Win NT Win NT Win NT

Win 95 Win 95

To Trap Multiplexor DSMat Center or ROC

Heart beating Problems

13

TNG Solution - Site DSMTNG Solution - Site DSM

Provides direct local heartbeating, raising traps on errors

No local WorldView Gateway needed Agents directly trap to Trap Multiplexor

DSM which uses TRAP_CONFIG TRAP FORWARD:Y to pass to TNG DSM

Only modified Ping Policy is employed at the Site DSM. No Agent Policy.

14

TNG Solution - Central FacilityTNG Solution - Central Facility

Require SNMP information from the sites not direct WorldView connection

DSM can act as a trap multiplexor For TNG WorldView traps are passed

through a modified DSM to provide WorldView class/status brokering

NetView receives traps from same trap multiplexor

15

Multiplexing Traps with UnicenterMultiplexing Traps with Unicenter

Central FacilityCentral Facility

StoreStore StoreStore StoreStore StoreStore

TrapMultiplexor

DSM

Traps sent to Multiplexor DSM

ROC DSMROC DSM

NetViewNetView CentralDSM TNG

CentralDSM TNG

16

Trap Multiplexor DSMTrap Multiplexor DSM

Utilizes Trap Forwarding capability Implemented using Policy Definitions Incoming traps can be ‘invisibly’ forwarded to

multiple destinations Only concern is LISTEN, FORWARD statements

use same syntax for mask of IP addresses

Only Policy employed is to Forward Traps. One line per destination - easy alteration.

17

Trap Multiplexor DSMTrap Multiplexor DSM# Example policy – only these lines in cnf file – no atp file allowed

# DSM-1

TRAP_CONFIG TRAP:192.2.*.*:*:*:*:* LISTEN

TRAP_CONFIG TRAP:192.2.*.*:*:*:*:* FORWARD:Y:192.2.4.6:162

# DSM-2 -







18

Central TNG ConfigurationCentral TNG Configuration

Receives Multiplexed traps Trap origin is as if the trap were

sent directly from the agent node (invisible)

No direct heartbeating Generates & Maintains

Object Store Connects to Repository

Central FacilityCentral Facility

TrapMultiplexor

DSM

Unicenter TNG

Unicenter TNG

19

Central TNG ConfigurationCentral TNG Configuration

Central TNGDSM

TrapMultiplexor

DSM

TrapMultiplexor

DSM

Traps from Stores(Agent Traps & Hearbeat Failures)

• Central TNG DSM has standard Agent Management Policy• No direct heartbeating, failure indicated by site DSM traps instead

Traps forwarded toother SNMP

Managers

20

SummarySummary DSM used for Trap Forwarding to provide

site traps to several SNMP Managers Site DSMs only heartbeat local nodes and

trap Central TNG DSMs on Agents directly trap to Central TNG DSM Central TNG DSM handles forwarded Agent

traps with standard policy, modified heartbeat (ping) policy using traps from site DSMs

Documents

1 “Lightning Bolt” Trap Multiplexor DSM Example Revised Mar 26 2001