- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- VC-enet modules will not "take" IP addresses
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
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
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
тАО03-28-2011 10:18 AM
тАО03-28-2011 10:18 AM
I started down this rabbit hole when I got the dreaded "Error Active Virtual Connect Manager Not at this IP Address" when trying to connect to VCM. One of the modules had an IP, the other didn't. I tried the instructions at http://bizsupport1.austin.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c01051495 and now both modules are IP-less.
One of the modules is @ f/w 3.10; I updated the f/w in the other one (before I lost the IP) to 3.15 OA f/w is @ 3.21 I even tried resetting the OA to no avail.
Help!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-28-2011 07:29 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-29-2011 05:23 AM
тАО03-29-2011 05:23 AM
Re: VC-enet modules will not "take" IP addresses
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-29-2011 01:33 PM
тАО03-29-2011 01:33 PM
Re: VC-enet modules will not "take" IP addresses
I handily stumped the first two levels of support. The workaround (I hesitate to call it a 'fix') was to remove both VC-Enet modules, and then remove the OA module(s), then re-install the OA, wait until it's all booted and settled in, and then install the VC-Enet modules. A bit disruptive, to say the least. Also, she had me clear the DNS server info from the EBIPA setup - she said there's been problems with that.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-29-2011 03:00 PM
тАО03-29-2011 03:00 PM