GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers - Netservers
- >
- Re: HP BLADE SERVER CLUSTER PROBLEM gbe2c
ProLiant Servers - Netservers
1851363
Members
3926
Online
104058
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Knowledge Base
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Forums
Discussions
back
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
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
11-07-2007 11:31 PM
11-07-2007 11:31 PM
HP BLADE SERVER CLUSTER PROBLEM gbe2c
Hi,
We have a blade chasis connected via ethernet (gbe2c) to a cisco 3750 and the problem I am having is that when the (Microsoft windows 2003 r2) Cluster has initiated failover then we cannot contact the virtual clustered resource for a long time via dns or ip address?? does anyone have any ideas how we can fix this ,,, i have a feeling it is the arp cache on the gbe2c do you have any suggestions on how to resolve / troubleshoot this . I am a windows server techie so my networking knowledge is limited.
Thanks
We have a blade chasis connected via ethernet (gbe2c) to a cisco 3750 and the problem I am having is that when the (Microsoft windows 2003 r2) Cluster has initiated failover then we cannot contact the virtual clustered resource for a long time via dns or ip address?? does anyone have any ideas how we can fix this ,,, i have a feeling it is the arp cache on the gbe2c do you have any suggestions on how to resolve / troubleshoot this . I am a windows server techie so my networking knowledge is limited.
Thanks
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-09-2007 11:16 AM
11-09-2007 11:16 AM
Re: HP BLADE SERVER CLUSTER PROBLEM gbe2c
What makes you think it's related to arp cache?
gbe2c is Cisco isn't it? Do you have redundant path setup? Are you running C-Class or P-Class blades?
If you think it's arp cache related then you could add static arp entries to the switches to fix it, but that depends on how your environment is setup.
If it's DNS related, you could make that server a caching only DNS server. I've had problems with DNS timeout's before and this solved it. You don't need to manage the DNS on that server if it's caching only, and you only need to get it to cache the domain that you need for the application.
gbe2c is Cisco isn't it? Do you have redundant path setup? Are you running C-Class or P-Class blades?
If you think it's arp cache related then you could add static arp entries to the switches to fix it, but that depends on how your environment is setup.
If it's DNS related, you could make that server a caching only DNS server. I've had problems with DNS timeout's before and this solved it. You don't need to manage the DNS on that server if it's caching only, and you only need to get it to cache the domain that you need for the application.
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.
Company
Events and news
Customer resources
© Copyright 2026 Hewlett Packard Enterprise Development LP