1 / 9

Discovery Flow

Discovery Flow. 18 September 2014. Client Requests Discovery RPC or Notification. GUI <<client>>. Identification <<provider>>. Device Type A <<provider>>. RPC. Synchronization <<provider>>. Device Type B <<provider>>. Reconciliation <<provider>>. Credential Mgr <<provider>>.

maxine
Télécharger la présentation

Discovery Flow

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. Discovery Flow 18 September 2014

  2. Client Requests DiscoveryRPC or Notification GUI <<client>> Identification <<provider>> Device Type A <<provider>> RPC Synchronization <<provider>> Device Type B <<provider>> Reconciliation <<provider>> Credential Mgr <<provider>> POST: restconf/existance:discover-network-element 200 ok { “input” : { “network-element-ip” : “1.2.3.4” } } { “output”: { “transaction-id”: “2167e651-78cf-42e7-a9d5- 942d42753114”, “result”: true } }

  3. RPC Converted To Notification Notification GUI <<client>> Identification <<provider>> Device Type A <<provider>> Synchronization <<provider>> Device Type B <<provider>> Reconciliation <<provider>> Credential Mgr <<provider>> NewNetworkElement { “transaction-id” : “2167e651-78cf-42e7-a9d5- 942d42753114”, “network-element-ip” : “1.2.3.4”, “network-element-type” : null }

  4. Notification To Device Support ModulesBroadcast GUI <<client>> Identification <<provider>> Device Type A <<provider>> Notification Synchronization <<provider>> Device Type B <<provider>> Reconciliation <<provider>> Credential Mgr <<provider>> IdentifyNetworkElement { “transaction-id” : “2167e651-78cf-42e7-a9d5- 942d42753114”, “network-element-ip” : “1.2.3.4”, “network-element-type” : null }

  5. Device Support Modules Attempt To ConnectOr Otherwise Attempt To Identify Device GUI <<client>> Identification <<provider>> Device Type A <<provider>> Connect Query Credentials Synchronization <<provider>> Device Type B <<provider>> Connect Reconciliation <<provider>> Credential Mgr <<provider>>

  6. Successful Identification NotifiesNetwork Element Type Associated GUI <<client>> Identification <<provider>> Device Type A <<provider>> Notification Synchronization <<provider>> Device Type B <<provider>> Reconciliation <<provider>> Credential Mgr <<provider>> NetworkElementIdentified { “transaction-id” : “2167e651-78cf-42e7-a9d5- 942d42753114”, “network-element-ip” : “1.2.3.4”, “network-element-type” : “TYPE-A” }

  7. Synchronization Queues Up Routed RPCRouted on network-element-type GUI <<client>> Identification <<provider>> Device Type A <<provider>> Routed RPC Synchronization <<provider>> Device Type B <<provider>> Reconciliation <<provider>> Credential Mgr <<provider>> synchronizeNetworkElement Three possible results { “transaction-id” : “2167e651-78cf-42e7-a9d5- 942d42753114”, “network-element-ip” : “1.2.3.4”, “network-element-type” : “TYPE-A” } Success – NE has been synchronized Failure – Synchronization failed, NE has not been synchronized Pending – Device support module will publish success or failure notification at a later time

  8. Successful Synchronization NotificationCould come from synchronization provider or device module GUI <<client>> Identification <<provider>> Device Type A <<provider>> Synchronization <<provider>> Device Type B <<provider>> Notification Reconciliation <<provider>> Credential Mgr <<provider>> NetworkElementedSynchronized { “transaction-id” : “2167e651-78cf-42e7-a9d5- 942d42753114”, “network-element-ip” : “1.2.3.4”, “network-element-type” : “TYPE-A” }

  9. Additional Network Elements During SynchronizationFan-out discovery Notification GUI <<client>> Identification <<provider>> Device Type A <<provider>> Routed RPC Synchronization <<provider>> Device Type B <<provider>> Reconciliation <<provider>> Credential Mgr <<provider>> NewNetworkElement { “network-element-ip” : “1.2.3.42”, “network-element-type” : null }

More Related