- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Re: VC Module reboot after minor OA config change
BladeSystem - General
1753761
Members
4841
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
тАО10-04-2010 01:55 AM
тАО10-04-2010 01:55 AM
VC Module reboot after minor OA config change
Hi There,
We noticed recently that the redundant OA in one of our c7000 chassis had lost it's IP address, but when we manually re-entered it from the active OA interface, it caused a reboot of all 4 (2 eth, 2 FC) Virtual Connect modules in the enclosure - causing a loss of ethernet connectivity, but more importantly a fairly catastrophic loss of SAN connectivity.
Has anyone seen this before, or have any info or advice? I appreciate we are not on the latest fware, but I'm pretty sure this shouldn't happen on any fware level, so I'm hoping for more than a 'upgrade fware' answer if possible. We have trouble getting downtime for fware upgrades owing to VC fware upgrades being so disruptive in the past (despite being advertised as non-disruptive in HP literature).
Thanks in advance and points will be awarded to any useful advice.
Fware levels below and logs attached;
Fware;
c7000 enclosure
Redundant OA's 2.51
1/10Gb VC Eth 2.00
4Gb VC FC 1.30
Thanks,
Brett
We noticed recently that the redundant OA in one of our c7000 chassis had lost it's IP address, but when we manually re-entered it from the active OA interface, it caused a reboot of all 4 (2 eth, 2 FC) Virtual Connect modules in the enclosure - causing a loss of ethernet connectivity, but more importantly a fairly catastrophic loss of SAN connectivity.
Has anyone seen this before, or have any info or advice? I appreciate we are not on the latest fware, but I'm pretty sure this shouldn't happen on any fware level, so I'm hoping for more than a 'upgrade fware' answer if possible. We have trouble getting downtime for fware upgrades owing to VC fware upgrades being so disruptive in the past (despite being advertised as non-disruptive in HP literature).
Thanks in advance and points will be awarded to any useful advice.
Fware levels below and logs attached;
Fware;
c7000 enclosure
Redundant OA's 2.51
1/10Gb VC Eth 2.00
4Gb VC FC 1.30
Thanks,
Brett
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-04-2010 04:44 AM
тАО10-04-2010 04:44 AM
Re: VC Module reboot after minor OA config change
Sorry ...this problem is fixed by FW update (as several others too).
And updating VC was very troublesome, but current VCSU update will go pretty smoothly.
And updating VC was very troublesome, but current VCSU update will go pretty smoothly.
Remember to give Kudos to answers! (click the KUDOS star)
You can find me from Twitter @JKytsi
You can find me from Twitter @JKytsi
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-04-2010 07:53 AM
тАО10-04-2010 07:53 AM
Re: VC Module reboot after minor OA config change
Thanks for the reply Jarkko.
Do you have a link or any info about the firmware upgrade that specifically deals with virtual connect issues resulting from resetting the IP of the passive OA?
Thanks,
Brett
Do you have a link or any info about the firmware upgrade that specifically deals with virtual connect issues resulting from resetting the IP of the passive OA?
Thanks,
Brett
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-04-2010 09:36 AM
тАО10-04-2010 09:36 AM
Re: VC Module reboot after minor OA config change
Can't remember exact advisory (could have been OA fw advisory too).
But this looks like something for example
Version: 2.10 (14 May 2009)
Fixes
The following issues have been resolved in Virtual Connect v2.10:
Resolved a potential VC GUI hang if Internet browser is being used, and an uplink port cable is pulled from a VC Ethernet module.
Resolved a few unexpected pop-up error messages which might appear on VC GUI when the VC GUI browser was open on the Profile page and a server was powered on.
Resolved an issue that caused servers using FC to lose SAN connectivity when the primary Onboard Administrator (OA) module is reset.
Resolved a memory leak in VC Manager daemon that was triggered when both Onboard Administrator (OA) modules were absent.
Resolved issue that caused CLI to terminate the ssh sessions and logout the user when CTRL-C was entered in the middle of CLI command execution.
But this looks like something for example
Version: 2.10 (14 May 2009)
Fixes
The following issues have been resolved in Virtual Connect v2.10:
Resolved a potential VC GUI hang if Internet browser is being used, and an uplink port cable is pulled from a VC Ethernet module.
Resolved a few unexpected pop-up error messages which might appear on VC GUI when the VC GUI browser was open on the Profile page and a server was powered on.
Resolved an issue that caused servers using FC to lose SAN connectivity when the primary Onboard Administrator (OA) module is reset.
Resolved a memory leak in VC Manager daemon that was triggered when both Onboard Administrator (OA) modules were absent.
Resolved issue that caused CLI to terminate the ssh sessions and logout the user when CTRL-C was entered in the middle of CLI command execution.
Remember to give Kudos to answers! (click the KUDOS star)
You can find me from Twitter @JKytsi
You can find me from Twitter @JKytsi
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