- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Re: VC update failed
BladeSystem - General
1753717
Members
4704
Online
108799
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
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
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
тАО04-04-2011 07:19 PM
тАО04-04-2011 07:19 PM
VC update failed
We have a chassis where the OA's have been updated to v3.21 and we are in the process of updating the VC's one at a time to v3.15.
Bay 1 updated to vc3.15 as per the OA, but the VCM claims it is running v3.01 still. Bay 2 is the current primary VC and is still at v3.01. Bay 1 was reset from the OA - no difference.
Running upgrade again, healthcheck, supportdump and so on aborts with "Error: The operation failed". The VCSU log is attached.
Any ideas? This is a production environment.
Bays 1 & 2 1/10Gb VC-Enet
Bays 3 & 4 4Gb VC-FC v1.40
Bays 5 - 8 1GB Ethernet pass thru
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-05-2011 03:15 AM
тАО04-05-2011 03:15 AM
Re: VC update failed
Tony,
The problem is that your OA cannot talk to the Primary VC manager in Bay_1, (see your log).
"Could not get Primary VCM IP Address from Bay 1"
I would check that the IP addresses are correctly assigned in EBIPA.
Next, log in to the VC Manager and check the status of the Domain.
There was a recent advisory regarding communication between OA and VCM which might be contributing to your problem.
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02720395&dimid=1043192498&dicid=alr_feb11&jumpid=em_alerts/us/feb11/all/xbu/emailsubid/mrm/mcc/loc/rbu_category/alerts
Dave.
The problem is that your OA cannot talk to the Primary VC manager in Bay_1, (see your log).
"Could not get Primary VCM IP Address from Bay 1"
I would check that the IP addresses are correctly assigned in EBIPA.
Next, log in to the VC Manager and check the status of the Domain.
There was a recent advisory regarding communication between OA and VCM which might be contributing to your problem.
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02720395&dimid=1043192498&dicid=alr_feb11&jumpid=em_alerts/us/feb11/all/xbu/emailsubid/mrm/mcc/loc/rbu_category/alerts
Dave.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-12-2011 07:25 AM
тАО04-12-2011 07:25 AM
Re: VC update failed
Oh yes - go for firmware 3.17 now as it fixes lots of bugs.
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