- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- After OA upgrade to 4.50, some of my VC's can no l...
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
06-01-2016 09:46 AM
06-01-2016 09:46 AM
After OA upgrade to 4.50, some of my VC's can no longer communicate with the OA
Hey all,
Seeing if anyone else has had this problem and/or found the solution- after the latest upgrade of OA firmware 4.50(completed last week), it seems some(not all) of my VC's can no longer communicate with their enclosure's OA's. This results in the status on the VC's going Orange, and I am no longer able to assign server profiles to slots. So far this has not caused any interruption. The very maddening part of this is that there is a button to re-enter the OA credentials into the VC. It asks for the OA IP, user name and pw- pretty standard. I can see in the logs on the OA that the login takes place from the VC. However, the VC still remains clueless. Anyone else run across this?
So my OA's are running 4.50(successful upgrades to both OA's), and my VC's are running 4.31.