- Community Home
- >
- Servers and Operating Systems
- >
- BladeSystem
- >
- BladeSystem Virtual Connect
- >
- Gen9 blades and VC Mgr Major error 6030 - Profile ...
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Latin America
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
- 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
- Email to a Friend
- Report Inappropriate Content
10-09-2017 01:34 PM
10-09-2017 01:34 PM
Gen9 blades and VC Mgr Major error 6030 - Profile Pending
Can anyone share knowledge of the root cause(s) of the VC Manager Major error 6030 - "Profile could not be assigned to powered up server". I got bit by this recently while doing Virtual Connect firmware upgrades (HP VC Flex-10/10D Module - firmware 4.45 to 4.50) and several servers dropped off the network after the interconnect modules reset. Reviewing the VC Manager system log shows 6030 Major error - while the VCSU log doesn't indicate any issues with the firmware upgrade itself. Power-cycling the affected servers brings them back on the network, but a firmware upgrade on the interconnect modules should be non-impacting to the servers if the server profiles provide redundant network ports and the server O/S properly handles the temporary link loss on each port.
-----------------------------------------------------------------------
Record : 3136
Date/Time : 2017-10-06 01:04:26-04:00
Info : PRO:ServerProfileBay10:6030:Major
Message : Profile could not be assigned to powered up server : Bay 10
-----------------------------------------------------------------------
Record : 3137
Date/Time : 2017-10-06 01:04:29-04:00
Info : PRO:ServerProfileBay11:6030:Major
Message : Profile could not be assigned to powered up server : Bay 11
-----------------------------------------------------------------------
Record : 3138
Date/Time : 2017-10-06 01:04:32-04:00
Info : PRO:ServerProfileBay12:6030:Major
Message : Profile could not be assigned to powered up server : Bay 12
-----------------------------------------------------------------------
Record : 3139
Date/Time : 2017-10-06 01:04:34-04:00
Info : PRO:ServerProfileBay15:6030:Major
Message : Profile could not be assigned to powered up server : Bay 15
-----------------------------------------------------------------------
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP