1 / 17

Client X Management over ISDN link

Client X Management over ISDN link. Client X. Key Requirements. Manageability of remote store devices Scalability (Distributed Management) Multi tier Model Central Management key requirement Minimal cost of management Management over ISDN Zero Fault tolerance

shaw
Download Presentation

Client X Management over ISDN link

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Client X Management over ISDN link Client X

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

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

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

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

  6. TNG Components • TNG • WorldView • Enterprise Management • Event , Workload • Agent Technology • DSM, Agents • Software Delivery • AMO • RCO • AntiVirus

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

  8. ISDN Routers • 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 • Stores Workstations power off at night • Non Significant status changes everyday • Unknown->Up • Up->Down • Down->Up • ISDN Costs!!!!! • No benefit to Client in seeing this! • No status propagation with power on / off

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

  13. Bridge Rules

  14. Event Policy

  15. ISDN Usage

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

More Related