HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- VCEM 1.30 - VC 2.10 - Multiple Networks with 1 nat...
BladeSystem - General
1833275
Members
2931
Online
110051
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
06-23-2009 09:22 AM
06-23-2009 09:22 AM
VCEM 1.30 - VC 2.10 - Multiple Networks with 1 native - Odd behaviour
Hi all, may need to log a call for this but just in case anyone has seen it before. Chassis#1 not managed by VCEM. Shared Uplink set. Mapped. I can go in to the server profile, choose multiple networks and set one to untagged. Once I've clicked apply everything is green, all connections work as expected down to the ESX hosts. I then have a production group imported in to VCEM (same hardware, firmware, networks as the unmanaged one above). When I follow the same process as Chassis#1 (but through VCEM this time) I can apply the profile but the network is dropped. Looking in the server profile it now reads as unassigned. Removing the untagged VLAN flag results in it taking correctly and being assigned. So it seems that for some reason I can't apply a native VLAN on a multiple network using VCEM 1.30 but I can on a standalone chassis with the same config. Any ideas? Cheers [Updated on 6/23/2009 11:38 AM]
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP