1 Client X Management over ISDN link Client X

2 Key Requirements m Manageability of remote store devices m Scalability (Distributed Management) m Multi tier Model – Central Management key requirement m Minimal cost of management m Management over ISDN m Zero Fault tolerance – No Technical Expertise at Stores m Ease of Install

3 ISDN m Minimal ISDN up-time – 30 seconds minimum ISDN billing – ISDN costs $$$!! – ISDN connection open for management considered as overhead m PiggyBack

4 Scalability m 1950 Remote Sites – 21 Sites Currently on BS2000 m 1950 NT Servers – Approx. 3 WIN95/NTWS per Shop m Challenges – Central Core Size – Number of ISDN Open Connections – No operator coverage

5 Hardware Architecture Head Office 100Mb LAN TNG Server ISDN Routers Shop Server Tills Applicaation 2 tier Model x1950

6 TNG Components m TNG – WorldView – Enterprise Management n Event, Workload – Agent Technology n DSM, Agents m Software Delivery m AMO m RCO m AntiVirus

7 Standard TNG Solution m One DSM per Store m Store Nodes monitored by local DSM m DSM connects to Local Repository m Multi tier model m Status Changes propagated to Central Server m Central CORE sizing – Include only needs attention objects m Bridge – Status Propagation and Replication

8 ISDN Routers m Stores ISDN Router Not Monitored When the ISDN router raises or drops the line, the DSM may see this as a state transition and notify the Object Repository at head office. Thus a transition from up to down on the ISDN line (when a call ends) may cause a raising of the line (an ISDN call) simply to notify the Object Repository that a call has ended. This is clearly an undesirable effect, which in its extreme form can cause a spurious ISDN call every 5 minutes.

9 Client X Architecture

10 Client X Architecture

11 Power Off Status Transition m Stores Workstations power off at night – Non Significant status changes everyday – Unknown->Up – Up->Down – Down->Up – ISDN Costs!!!!! m No benefit to Client in seeing this! – No status propagation with power on / off

12 Bridge m Function – Propagate severity levels 2 and 5 to Central CORE – Replicate Objects – Delete Objects when no longer conforms to severity levels m Not started at bootup m Startup triggered by status transition – Event Rule

13 Bridge Rules

14 Event Policy

15 ISDN Usage

16 Conclusion m Great Cost Justification m Reduced ISDN connection up time m Pro Active Management m Management of Pertinent resources m RCO really loved! m STORE Server up time improved – SQL Agent proactive notification m Virus detection and corrections m Ease of maintenance with USD

17