- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Re: Can changing OA IP can cause loss of server co...
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
тАО04-28-2010 07:35 AM
тАО04-28-2010 07:35 AM
Can changing OA IP can cause loss of server connectivity?
Raymond had a question regarding the changing of IP addresses used by the Onboard Admninistrator:
********************************************************************************************************************
My customer changed the IP address of their OAs to a different subnet without changing IP for iLO and VC modules. They said that once they changed the OA IPs they could not connect to the servers running in the enclosure. They had to reset the VC modules and then connection to servers when returned. In my mind, changing the OA IPs will only affect manageability of the iLOs and I/O modules but everything else should continue to run as normal. Can anyone provide feedback whether there are issues if the OA IPs are in a different subnet?
****************************************************************************************************************
Monty replied:
*************************************************************************************************************
Virtual Connect Manager requires connectivity to the OA in each enclosure in a VCM domain тАУ this includes all VC interconnect modules and OAs in the VCM domain be on the same subnet as the module running Virtual Connect Manager.
**************************************************************************************************************
To which Raymond responded:
********************************************************************************************************
Monty тАУ lacking that required connectivity, VC will shutdown server traffic thru the module?
*********************************************************************************************************
And Monty replied:
*********************************************************************************************************
I have only seen VCM register an enclosure status degraded based on loss of network connectivity to the OA. So just reconfiguring the OA IP address to a different subnet than the VCM will only prevent VCM from making any changes in that enclosure. It should maintain the previous connections until network connectivity to the OA is restored.
However, after changing the OA IP address to an inaccessible subnet, if the VCM is rebooted, there could be severe issues as VCM first attempts to establish communication with the OA to ensure that the VCM module is in the correct domain. Lack of VCM communication due to changing the subnet of the OA will result in VCM stopping at the point it needs the domain to be created or imported.
*******************************************************************************************************************
Any other comments or suggestions?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-01-2011 10:12 AM
тАО03-01-2011 10:12 AM
Re: Can changing OA IP can cause loss of server connectivity?
I have just had an issue too. The OA IPs were the wrong way around, so changed these (after a failover to get back to OA1 in bay 1). All was well and OA connectivity restored, except, the VC domain went degraded, all connectivity to servers lost, the VCs didn't log anything until they were manually reset.. We didn't move subnets, just simply switched the IPs over. (OA v3.21, VC 3.10). Even now the VCs are reporting some strange 'unknown' status on defined networks, trunks etc.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-05-2012 10:38 PM
тАО01-05-2012 10:38 PM
Re: Can changing OA IP can cause loss of server connectivity?
Will changing both the OA IP and VC IPs (interconnect bay IPs via EBIPA) via the service port using a laptop do the trick? This way we can make both OA and VCM in same subnet, but need confirmation if someone has tested this?