- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Virtual Connect Network Access Groups (NAGs)
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-07-2012 06:25 AM
12-07-2012 06:25 AM
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?