HP 3PAR StoreServ 7400 4-node HP 3PAR Policy Server Administrator's G - Page 50

Association between an Agent Gateway and Managed Assets

Get HP 3PAR StoreServ 7400 4-node PDF manuals and user guides View all HP 3PAR StoreServ 7400 4-node manuals
Add to My Manuals
Save this manual to your list of manuals

Page 50 highlights

When it receives a request to execute an action whose access right is "Ask for Approval," an Agent gateway or Policy Agent sends a permission request message to the Policy Server. When a Policy Server user acts on a previously submitted permission request, the Policy Server delivers a permission response message back to the Agent. Since a permission response contains an action, it needs to be delivered to the target asset only once. For stateless actions such as Set Data Item, permission responses are delivered to the redundant Agent gateway that contacts the Policy Server first. However, if a permission response for a Software Management (SM) package deployment were not sent to the redundant gateway that originally sent the request, the package would not be processed properly. Therefore, "stickiness" has been introduced for permission requests for SM package deployments. For "sticky" permission requests, the permission response is sent only to the Agent gateway that sent the permission request. Association between an Agent Gateway and Managed Assets For HP 3PAR Policy Server to keep track of policy deliveries, and also to optimize communications between Policy Server and Agent gateways, Policy Server maintains associations between Agent gateways and managed assets. An Agent gateway generates the association information and sends it to the Policy Server. In addition, an Agent gateway updates the association information every time managed assets are added or removed. HP 3PAR Policy Server 5-6

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
HP 3PAR Policy Server
5-6
When it receives a request to execute an action whose access right is “Ask for Approval," an Agent gateway
or Policy Agent sends a permission request message to the Policy Server. When a Policy Server user acts on
a previously submitted permission request, the Policy Server delivers a permission response message back to
the Agent. Since a permission response contains an action, it needs to be delivered to the target asset only
once. For stateless actions such as Set Data Item, permission responses are delivered to the redundant Agent
gateway that contacts the Policy Server first. However, if a permission response for a Software Management
(SM) package deployment were not sent to the redundant gateway that originally sent the request, the
package would not be processed properly. Therefore, "stickiness" has been introduced for permission
requests for SM package deployments. For "sticky" permission requests, the permission response is sent
only to the Agent gateway that sent the permission request.
Association between an Agent Gateway and Managed Assets
For HP 3PAR Policy Server to keep track of policy deliveries, and also to optimize communications
between Policy Server and Agent gateways, Policy Server maintains associations between Agent gateways
and managed assets. An Agent gateway generates the association information and sends it to the Policy
Server. In addition, an Agent gateway updates the association information every time managed assets are
added or removed.