- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Adding VirtualConnect Enet modules to existing dom...
BladeSystem - General
1752777
Members
6165
Online
108789
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
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
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
05-22-2009 03:06 PM
05-22-2009 03:06 PM
Adding VirtualConnect Enet modules to existing domain
I'm planning to add two VC 1/10 Enet modules to an existing VC domain in a C7000 chassi. The exising VC Enet modules is placed in slot 1/2 and have the latest 2.10 firmware. The "new" modules will be placed in slot 3/4 and probably have a lower firmware revision. I also plan to use 1 GB TP connection to link the modules (1/3 and 2/4).
My question is if this operation can be performed "online" without interrupting the traffic in the existing modules or do I have to plan for downtime? I'm not so familiar with VC domains and what will happen if I get a firmware mismatch.
I read an similar thread started by CarlosG 17th Jun 2008 but the question at the end wasn´t answered.
My question is if this operation can be performed "online" without interrupting the traffic in the existing modules or do I have to plan for downtime? I'm not so familiar with VC domains and what will happen if I get a firmware mismatch.
I read an similar thread started by CarlosG 17th Jun 2008 but the question at the end wasn´t answered.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-23-2009 10:51 PM
05-23-2009 10:51 PM
Re: Adding VirtualConnect Enet modules to existing domain
Per,
The interconnect modules are designed to be hot swap/plug(able) so installing the additional VC modules should not cause any problems.
Once installed, and before opening any of the uplink ports to the outside world, or connecting them to the modules in IC Bays 1 & 2, consider bringing the firmware up tho the same level as your existing VC ENet modules. At least, ensure that both of the new ethernet modules have the same firmware rev, even if it is different to your existing modules.
Because VC failover is L <--> R, it is important that the Modules on any given shelf are at the same firmware level. (Less important vertically)
HTH
Dave.
The interconnect modules are designed to be hot swap/plug(able) so installing the additional VC modules should not cause any problems.
Once installed, and before opening any of the uplink ports to the outside world, or connecting them to the modules in IC Bays 1 & 2, consider bringing the firmware up tho the same level as your existing VC ENet modules. At least, ensure that both of the new ethernet modules have the same firmware rev, even if it is different to your existing modules.
Because VC failover is L <--> R, it is important that the Modules on any given shelf are at the same firmware level. (Less important vertically)
HTH
Dave.
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP