- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- VLAN CHANGE / MOVE Best Practices
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
10-13-2010 07:28 AM
10-13-2010 07:28 AM
VLAN CHANGE / MOVE Best Practices
Todd had a customer question regarding movement of VLANs.
*************************
A customer has two VC SUS configured in his domain. He wants to migrate several VLANS from one SUS to the other SUS. The VLAN's are currently assigned to Blade Profiles.
We are trying to minimize downtime, so the thought is to ADD the VLANS to the other SUS instead of MOVING the VLANS. Then modifying the server profiles to add the other SUS?. I checked the VC User guide and I see we can modify VLAN ID's in Flex10..but it doesn't mention one way or another for the non Fle-10 which is what we have in our environment.
*******************
Chris had some advice:
**********************
Well, you can modify the assigned VID (VLAN ID) within the SUS, or simply add the new VIDs to the SUS. This behavior and operation is regardless of the Virtual Connect model.
However, that doesn't mean that the customer does not need to make any changes on their OS's or even the Server Profiles. If they are not using any Server-side VLAN trunking/tagging, then life is easy; just update the server profile with the newer vNets.
If they are using Server-side VLAN trunking/tagging, then that will certainly make life a bit harder. If they are also defining new subnets, then they can also pre-stage the new networking on their hosts to minimize impact. If they are not migrating to another L3 subnet, then that will make their life more difficult, as they would need to update the networking stack or NIC team configuration to take into account for any changes.
************************
Other comments or best practices?