“Lightning Bolt” Trap Multiplexor DSM Example

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

2. Overview • 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 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. Site DSM pings Nodes Small Site Structure Site TNG box with DSM Unix Win 95 USD NT F/P NT

5. Large 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 operations and support

6. Site DSMs ping Nodes Large Site Structure Site TNG boxes with DSMs Site TNG box with DSM Unix 600* Win95 USD NT F/P NT USD NT F/P NT

7. Central 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 operations and support

8. USD NT F/P NT Site DSMs ping Nodes USD NT USD NT Central Site Structure Site TNG boxes with DSMs Site TNG boxes with DSMs Site TNG boxes with DSMs Site TNG boxes with DSMs Site TNG box with DSM Unix 600* Win95 USD NT F/P NT USD NT F/P NT F/P NT F/P NT

9. Central Monitoring Facility • Customer required NetView and TNG to be able to simultaneously utilise site information. • ROC may need a subset view of local information NetView Unicenter TNG Trap Multiplexor

10. The 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 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. Heart beating Problems Site DSM pings Nodes TNG Solution - At the Sites... To Trap Multiplexor DSM at Center or ROC Site DSM Unix Win 95 Win NT Win NT

13. TNG 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 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. Traps sent to Multiplexor DSM Multiplexing Traps with Unicenter Central Facility NetView Central DSM TNG ROC DSM Trap Multiplexor DSM Store Store Store Store

16. Trap 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 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 - TRAP_CONFIG TRAP:192.29.*.*:*:*:*:* LISTEN TRAP_CONFIG TRAP:192.30.*.*:*:*:*:* LISTEN TRAP_CONFIG TRAP:192.31.*.*:*:*:*:* LISTEN TRAP_CONFIG TRAP:192.29.*.*:*:*:*:* FORWARD:Y:192.30.145.245:162 TRAP_CONFIG TRAP:192.30.*.*:*:*:*:* FORWARD:Y:192.30.145.245:162 TRAP_CONFIG TRAP:192.31.*.*:*:*:*:* FORWARD:Y:192.30.145.245:162

18. Central 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 Facility Unicenter TNG Trap Multiplexor DSM

19. Central TNG Configuration • Central TNG DSM has standard Agent Management Policy • No direct heartbeating, failure indicated by site DSM traps instead Traps forwarded to other SNMP Managers Central TNG DSM Trap Multiplexor DSM Traps from Stores (Agent Traps & Hearbeat Failures)

20. Summary • 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