HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
BladeSystem Virtual Connect
cancel
Showing results for 
Search instead for 
Did you mean: 

Virtual Connect Network Access Groups (NAGs)

 
chuckk281
Trusted Contributor

Virtual Connect Network Access Groups (NAGs)

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?