- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Re: VC Ethernet
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
тАО03-02-2011 11:08 AM
тАО03-02-2011 11:08 AM
VC Ethernet
I tried to reset them, but still failed, but stop to tried to connect to 49.48.46.49.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-03-2011 03:52 AM
тАО03-03-2011 03:52 AM
Re: VC Ethernet
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-03-2011 06:02 AM
тАО03-03-2011 06:02 AM
Re: VC Ethernet
just curious if the advice in that document (disabling DNS) helped...
Unix operates with beer.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-03-2011 06:06 AM
тАО03-03-2011 06:06 AM
Re: VC Ethernet
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-03-2011 06:09 AM
тАО03-03-2011 06:09 AM
Re: VC Ethernet
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-03-2011 08:24 AM
тАО03-03-2011 08:24 AM
Re: VC Ethernet
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-03-2011 08:28 AM
тАО03-03-2011 08:28 AM
Re: VC Ethernet
dns gives mx-ll-49.48.46-49.dynamic.3bb.co.th
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-07-2011 05:51 AM
тАО03-07-2011 05:51 AM
Re: VC Ethernet
While I'm glad to see that someone else has observed the 49.48.46.49 ssh connection, I'm still quite concerned.
I also had to run the same fix, disabling DNS via the internconnect IP config interface, however I had a nasty surprise after committing the change. Rather than having the interfaces refresh their config automagically after 2-5 minutes (as they had done in the past), my Flex-10 modules all spontaneously rebooted.
Very nasty surprise.
I've got a case open with HP for both the spontaneous reboot and the 49.48.x.x SSH connection - please post if you find anything out.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-07-2011 06:40 AM
тАО03-07-2011 06:40 AM
Re: VC Ethernet
The issue I noted, where the domain essentially reboots, is mentioned in the latest version of the DNS issue advisory, which was updated today.
I spoke with a VC engineer about the 49.48.x.x ssh issue, and here's what he told me:
- The "DNS bug" has existed since v1.8* of the VC firmware, but has not manifested itself until now.
- The "DNS bug" is not a virus.
- Some old section of code relied on the 49.48.x.x IP block not existing, and this code is somehow related to the VC's internal domain communication.
- The 49.48.x.x IP block was allocated in February (the WHOIS record and admin info was updated 14 February 2011), and reverse resolution began sometime thereafter.
- When it started to reverse resolve, the SSH connections also started.
- This reverse resolution actually _working_ is at the heart of the DNS issue.
- It will be fixed in firmware 3.17.
That's a summary of what I heard and I hope it helps. From my end it is technically feasible, as the SSH connections started at the exact moment my VC domain started to report an inability to connect to or manage the interconnects, and both issues cleared after removing the DNS server entries.
The BIG issue, in my mind, is that removing the DNS servers in the list can cause a full VC domain reboot, which is what I experienced. The engineer noted that there is no rhyme or reason to why this happens, but in a NO_COMM error status it is "very likely".
So watch out and don't update that DNS until you can secure an outage window, as we were completely down for around 5-8 minutes.
Dave
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-08-2011 06:43 AM
тАО03-08-2011 06:43 AM
Re: VC Ethernet
Customer Advisory Document ID: c02720395, March 7, 2011 is available now at the url below to resolve this issue. If you have questions or need assistance, contact HP Support in your home country. HP is committed to minimizing any impact on customer environments and to resolving the issue as quickly as possible.
Download Customer Advisory Document ID: c02720395, March 7, 2011:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02720395тМй=en&cc=us&taskId=101&prodSeriesId=3540808&prodTypeId=329290
Visit the HP Support worldwide contact list:
http://welcome.hp.com/country/us/en/wwcontact_us.html