From: McDonald, Ira (imcdonald@sharplabs.com)
Date: Thu Nov 17 2005 - 17:27:07 EST
Hi folks, Thursday (17 November 2005)
Below is a second example sequence of operations diagram, as per my
working group last call comment on WIMS Abstract Protocol spec.
I propose:
(1) Rename existing section 4.3 from 'Sequence of Operations' to
'Example of Fleet Management' (because it contains ONLY an example
and does NOT normatively define any WIMS sequence of operations).
(2) Annotate the diagram in section 4.3 with numbered steps and append
numbered notes that are more complete (rather than most of the text
in section 4.3).
(3) Add a new section 4.4 'Example of Enterprise Management' containing
the (Visio version of the) diagram below and explanatory notes.
Comments?
Cheers,
- Ira
Ira McDonald (Musician / Software Architect)
Blue Roof Music / High North Inc
PO Box 221 Grand Marais, MI 49839
phone: +1-906-494-2434
email: imcdonald@sharplabs.com
------------------------------------------------------------------------
WIMS Manager WIMS Proxy SNMP Legacy Step In
(Enterprise) (Agent/Manager) Managed Entity Notes
------------ --------------- -------------- -------
Connect and authenticate (1)
------------------------>
|
Accept and authenticate (2)
<------------------------
|
|
BeginManagement (3)
------------------------>
(managerURI {W-Manager}, |
agentReference {W-Agent}, |
operations, actions, |
objects, |
schedule {w/ action |
SubscribeForAlerts}) |
|
BeginManagementResponse (4)
<------------------------
| (statusString,
| operations, actions,
| objects)
|
|
Disconnect Indication (5)
------------------------>
|
Disconnect OK (6)
<------------------------
{SubscribeForAlerts scheduled action} (7)
Create Subscription object and
Connect and authenticate
<------------------------
|
Accept and authenticate (8)
------------------------>
|
|
SendReports (9)
<------------------------
| (senderReference {W-Agent},
| managerURI {W-Manager},
| reports {list of events
| in Subscription}
|
SendReportsResponse (10)
------------------------>
(statusString,
unsupportedElements)
|
|
Disconnect Indication (11)
<------------------------
|
Disconnect OK (12)
------------------------>
Connect and authenticate (13)
------------------------>
|
Accept and authenticate (14)
<------------------------
|
|
ExecuteAction (15)
------------------------>
(managerURI {W-Manager}, |
agentReference {W-Agent}, |
action {GetElements of |
ManagerAgentSupported}) |
|
{GetElements immediate action} (16)
SendReports
<------------------------
| (senderReference {W-Agent},
| managerURI {W-Manager},
| reports {list of WIMS or
| legacy agents})
|
SendReportsResponse (17)
------------------------>
(statusString, |
unsupportedElements) |
|
ExecuteActionResponse (18)
<------------------------
(statusString,
unsupportedElements)
|
|
Disconnect Indication (19)
------------------------>
|
Disconnect OK (20)
<------------------------
Connect and authenticate (21)
------------------------>
|
Accept and authenticate (22)
<------------------------
|
|
ExecuteAction (23)
------------------------>
(managerURI {W-Manager}, |
agentReference {W-Agent}, |
action {GetElements of |
legacy AgentInfo}) |
|
{GetElements immediate action} (24)
SNMP Get
------------------------>
(SNMPv2-MIB.sysDescr) |
|
SNMP GetResponse (25)
<------------------------
| (SNMPv2-MIB.sysDescr)
|
SendReports (26)
<------------------------
| (senderReference {W-Agent},
| managerURI {W-Manager},
| reports {legacy AgentInfo})
|
SendReportsResponse (27)
------------------------>
(statusString, |
unsupportedElements) |
|
ExecuteActionResponse (28)
<------------------------
(statusString,
unsupportedElements)
|
|
Disconnect Indication (29)
------------------------>
|
Disconnect OK (30)
<------------------------
Notes:
(1) Top-level WIMS Manager (on left in diagram) starts downstream
connection to WIMS Proxy including mutual authentication.
(2) WIMS Proxy (in middle of diagram) accepts incoming connection
from WIMS Manager and completes mutual authentication.
(3) WIMS Manager proposes management association with WIMS Proxy by
sending BeginManagement request specifying its supported objects,
operations, and actions and Schedule object (w/ SubscribeForAlerts
action).
(4) WIMS Proxy (Agent) accepts management association with WIMS Manager
by replying with BeginManagement response, specifying its own
supported objects, operations, and actions and a PWG standard status
of "SuccessfulOk".
(5) WIMS Manager sends disconnect indication to WIMS Proxy.
(6) WIMS Proxy sends disconnect OK to WIMS Manager.
--------------------
(7) WIMS Proxy (Agent) processes SubscribeForAlerts action (in Schedule)
by creating Subscription object (for notifications) and
starting upstream connection to WIMS Manager.
(8) WIMS Manager accepts incoming connection from WIMS Proxy and
completes mutual authentication.
(9) WIMS Proxy sends SendReports request to WIMS Manager specifying
NotifyEvents element (list of events) from Subscription object.
(10) WIMS Manager replies with SendReports response specifying PWG
standard status of "SuccessfulOk".
(11) WIMS Proxy sends disconnect indication to WIMS Manager.
(12) WIMS Manager sends disconnect OK to WIMS Proxy.
--------------------
(13) WIMS Manager starts downstream connection to WIMS Proxy including
mutual authentication.
(14) WIMS Proxy accepts incoming connection from WIMS Manager and
completes mutual authentication.
(15) WIMS Manager reads list of supported WIMS or legacy agents by
sending ExecuteAction request specifying GetElements action for
ManagerAgentSupported element in Manager object.
(16) WIMS Proxy (Agent) processes GetElements action by sending
SendReports request specifying ManagerAgentSupported element from
Manager object.
(17) WIMS Manager replies with SendReports response specifying PWG
standard status of "SuccessfulOk".
(18) WIMS Proxy (Agent) completes ExecuteAction operation by sending
ExecuteAction response specifying PWG standard status of
"SuccessfulOk".
(19) WIMS Manager sends disconnect indication to WIMS Proxy.
(20) WIMS Proxy sends disconnect OK to WIMS Manager.
--------------------
(21) WIMS Manager starts downstream connection to WIMS Proxy including
mutual authentication.
(22) WIMS Proxy accepts incoming connection from WIMS Manager and
completes mutual authentication.
(23) WIMS Manager reads description of legacy agent by sending
ExecuteAction request specifying GetElements action for AgentInfo
element in (mapped) Agent object.
(24) WIMS Proxy processes GetElements action by sending SNMP Get request
for sysDescr element in SNMP Agent MIB (RFC 3418, updates RFC 1213)
SNMP Agent in legacy system (on right in diagram).
(25) SNMP Agent in legacy system replies with SNMP Get response
specifying sysDescr to WIMS Proxy.
(26) WIMS Proxy continues processing of GetElements action by sending
SendReports request specifying AgentInfo (mapped from sysDescr) to
WIMS Manager.
(27) WIMS Manager replies with SendReports response specifying PWG
standard status of "SuccessfulOk".
(28) WIMS Proxy (Agent) completes ExecuteAction operation by sending
ExecuteAction response specifying PWG standard status of
"SuccessfulOk".
(29) WIMS Proxy sends disconnect indication to WIMS Manager.
(30) WIMS Manager sends disconnect OK to WIMS Proxy.
--------------------
This archive was generated by hypermail 2.1.4 : Thu Nov 17 2005 - 17:25:14 EST