Virtual Connect Network Access Groups (NAGs)

chuckk281 — Fri, 07 Dec 2012 14:25:05 GMT

Glen needed some clarification regarding how Virtual Connect uses NAGs:

**************

I am playing around with NAGs to advise a customer on their use and it appears to me that a server role user can still create a server profile connecting to any combination of networks by having the server profile in the default NAG. If the idea of NAGs is to prevent the server user circumventing a network policy (administered by the network role), doesn’t this defeat the purpose? Or am I missing something?

************

Input from Vincent:

**************

You can remove networks from the Default NAG, then server profiles in the Default NAG will not be able to connect to these networks

************

And from Steve:

************

Vincent is right and you can share networks, such as vmotion, management etc. in all NAGs that require them.

Server only admins won't be able to edit the NAGs.

**************

Comments or questions?

topic Virtual Connect Network Access Groups (NAGs) in BladeSystem - General

Virtual Connect Network Access Groups (NAGs)