- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Re: IP config on GbE2c after upgrade to 2.0.50
BladeSystem - General
1753706
Members
4877
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-02-2008 02:32 AM
тАО10-02-2008 02:32 AM
Re: IP config on GbE2c after upgrade to 2.0.50
Thanks for that info. I have informed HP tech support and asked if there's any other workaround to get EBIPA to work again without resetting the OA config.
Will post result here.
Will post result here.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-02-2008 03:55 AM
тАО10-02-2008 03:55 AM
Re: IP config on GbE2c after upgrade to 2.0.50
you're not resetting the OA config (that is, you don't bring it to its factory default settings) - you're just rebooting the OA, it should be harmless unless you expect tons of events to happen in the enclosure during that minute that you absolutely need to be aware of :)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-02-2008 04:16 AM
тАО10-02-2008 04:16 AM
Re: IP config on GbE2c after upgrade to 2.0.50
Ah, I'll see. However, I think also removing the switch and putting it back also resolved the problem (note: not just powering off and off via the OA but physically removing and putting it back).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-26-2009 04:34 PM
тАО02-26-2009 04:34 PM
Re: IP config on GbE2c after upgrade to 2.0.50
Hello
I Can't tell if firmware 2.0.50 caused this situation for one of my customers. But for som reason the assigned a static IP via CLI.
I had some trouble reverting it to EBIPA assigned adress. After several reboots of both OA and Gbe2c switch, removing/reinserting switch etc. I firmware updated one switch to 2.0.60, this didn't solve my problem, but at least the eventlog now told me that EBIPA DHCP adress is recieved, but due to IP-conflict it can't be assigned to mgmt interface (256), also conflict on gateway to be assigned (4).
Via the WEB GUI i deleted both the L3 management IF (1) with static IP and deleted L3 Gateway (4)and hit the apply button. 30 milisecs later the switch was available at EBIPA assigned adress with link in OA GUI.
I guess the new 2.0.60 firmware isn't a part of the solution, but since it's so easy upgradeable I upgraded the 2. switch as well.
Hope this help you.
I Can't tell if firmware 2.0.50 caused this situation for one of my customers. But for som reason the assigned a static IP via CLI.
I had some trouble reverting it to EBIPA assigned adress. After several reboots of both OA and Gbe2c switch, removing/reinserting switch etc. I firmware updated one switch to 2.0.60, this didn't solve my problem, but at least the eventlog now told me that EBIPA DHCP adress is recieved, but due to IP-conflict it can't be assigned to mgmt interface (256), also conflict on gateway to be assigned (4).
Via the WEB GUI i deleted both the L3 management IF (1) with static IP and deleted L3 Gateway (4)and hit the apply button. 30 milisecs later the switch was available at EBIPA assigned adress with link in OA GUI.
I guess the new 2.0.60 firmware isn't a part of the solution, but since it's so easy upgradeable I upgraded the 2. switch as well.
Hope this help you.
- « Previous
-
- 1
- 2
- Next »
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