17
1 Client X Client X Management over Management over ISDN link ISDN link Client X

Client X Management over ISDN link

  • Upload
    shaw

  • View
    33

  • Download
    0

Embed Size (px)

DESCRIPTION

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 - PowerPoint PPT Presentation

Citation preview

Page 1: Client X  Management over  ISDN link

1

Client X Client X Management over Management over

ISDN linkISDN link

Client X

Page 2: Client X  Management over  ISDN link

2

Key RequirementsKey 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

Page 3: Client X  Management over  ISDN link

3

ISDNISDN

Minimal ISDN up-time– 30 seconds minimum ISDN billing– ISDN costs $$$!!– ISDN connection open for management

considered as overhead PiggyBack

Page 4: Client X  Management over  ISDN link

4

ScalabilityScalability

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

Page 5: Client X  Management over  ISDN link

5

Hardware ArchitectureHardware Architecture

Head Office

100Mb LAN

TNG Server

ISDN Routers

Shop Server

Tills

Applicaation

2 tier Model

x1950

Page 6: Client X  Management over  ISDN link

6

TNG ComponentsTNG Components TNG

– WorldView– Enterprise Management

Event , Workload

– Agent Technology DSM, Agents

Software Delivery AMO RCO AntiVirus

Page 7: Client X  Management over  ISDN link

7

Standard TNG SolutionStandard 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

Page 8: Client X  Management over  ISDN link

8

ISDN RoutersISDN 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.

Page 9: Client X  Management over  ISDN link

9

Client X ArchitectureClient X Architecture

Event Console

W orkstation 1NT

W orkstation 4NT

W orkstation 3W 95

W orkstation 2W 95STORE SERVER

S% ShopNo%

STORE HUB

LRL_UNISQL_01

LRL_UNISRV_01

ISDN 64K ROUTER

HQ Server

SHOP STORE

Unicenter TNG Components & CommunicationsTraffic Flow

CENTRALW V CORE

Rem oteW V CORE

Event Console

Page 10: Client X  Management over  ISDN link

10

Client X ArchitectureClient X Architecture

W orkstation 4NT

W orkstation 3W 95

STORE SERVERS%ShopNo%

STORE HUB

LRL_UNISQL_01

LRL_UNISRV_01

LRL_BS2KSDO_02

10.192.1.97

ISDN 64KROUTER

SHOP STORE

Unicenter TNG Options Components &Communications Traffic Flow

HQ Central Server

USD LIBRARY

RPO

RPO

RPO

AVO

AVO

AVO

AVO

AVO

AVO

Page 11: Client X  Management over  ISDN link

11

Power Off Status TransitionPower 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

Page 12: Client X  Management over  ISDN link

12

BridgeBridge 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

Page 13: Client X  Management over  ISDN link

13

Bridge RulesBridge Rules

Page 14: Client X  Management over  ISDN link

14

Event PolicyEvent Policy

Page 15: Client X  Management over  ISDN link

15

ISDN UsageISDN Usage

Component ISDN Line Usage

Unicenter TNG – WorldView Only objects which pass through a Critical state,will be synchronised. Objects are now managedremotely and only these pertinent events will bethen centrally managed.

Unicenter TNG – Event Management Each store has a defined set of Message actionsbased on normal Shop Server activity and whatoccurs in the NT Event Log. Based on this onlyCritical events will be deemed pertinent forforwarding to the central EM ConsoleLRL_UNISRV_01 thus keeping ISDN traffic at adesired minimum.

Software Delivery Option Delivery of software packages to shop servers(ONLY). The agent is switched off but willpiggyback on the overxfer.bat scheduled job andcheck with the central LRL_BS2KSDO_02Server if there is anything to be delivered e.g.Maintenance etc.

Anti Virus Option Dependent on virus activity alerts will be trappedand centrally reported via EM.

Remote Control Option Any remote takeover will bring up the line but isan understood action by Client.

Asset Management Option Propagating data back to head office (this mayalso be “piggy backed” on to the nightly call

Page 16: Client X  Management over  ISDN link

16

ConclusionConclusion 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

Page 17: Client X  Management over  ISDN link

17