- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- 2 Node Cluster 1 node is dominant & 1 node is dorm...
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-26-2008 05:26 AM
тАО03-26-2008 05:26 AM
2 Node Cluster 1 node is dominant & 1 node is dormant to tcpip activities
for all TCPIP activities to where you can ping
out and other outside cluster nodes can ping
it while the other node in the same cluster
becomes dormant to TCPIP activities to where you cannot ping out nor any node can ping to
it. If you boot the dormant node, then the
dormant node becomes dominant while dominant
node becomes dormant. I did notice that the change occurs during the boot.
Any ideas on why this is occurring?
Hardware is ES40 system.
Software is OpenVMS 7.3-2
TCPIP Version is TCPIP_ECO V5.4-156
Both nodes do show up on show cluster command
and are booting from correct boot disk.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-26-2008 06:08 AM
тАО03-26-2008 06:08 AM
Re: 2 Node Cluster 1 node is dominant & 1 node is dormant to tcpip activities
regards Kalle
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-26-2008 10:37 AM
тАО03-26-2008 10:37 AM
Re: 2 Node Cluster 1 node is dominant & 1 node is dormant to tcpip activities
DNS Clustering via Load Broker or Metric Server?
Is FailSAFE or LAN Failover in use?
IP clustering and IP itself doesn't necessarily do what you might expect from experience with DECnet and the DECnet cluster alias, because (in simplest terms) IP isn't DECnet.
IP can easily be configured with wonky routing or wonky DNS. And sometimes simply getting IP configured can be interesting, too.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-26-2008 12:16 PM
тАО03-26-2008 12:16 PM
Re: 2 Node Cluster 1 node is dominant & 1 node is dormant to tcpip activities
anything unusual in comparison to other clusters. Sorry I'm not able show the
display results for security reasons.
By saying ping out is to ping other IP
addresses outside the node via TCPIP> PING
command. No failover or failsafe is in use.
Decnet is setup on it's own nic card and
is functioning.
No to DNS and Alias cluster questions.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-26-2008 12:49 PM
тАО03-26-2008 12:49 PM
Re: 2 Node Cluster 1 node is dominant & 1 node is dormant to tcpip activities
The local IP network configuration is almost certainly incorrect.
Somewhere.
Either with TCP/IP Services, within a firewall that might be lurking, or with a router or subnet or VLAN configuration setting. The cabling and the NICs are probably OK, given you indicate the active host is moving around.
The possibilities for a trigger here are, well, endless. This is IP, after all.
Start by segmenting the networks, and by researching the switches and firewalls that might be (or are) present here. Running both in-bound and out-bound ping tests for each network segment and each host.
Do trust what the local network team tells you, but also remain skeptical and do ensure you specifically verify all of you are told by your networking team.
Do have another set of eyeballs verify the IP network configuration of each of the cluster hosts.
Do verify the TCP/IP database files are in the expected directories.
Make sure that full privileges are enabled when working with ping. (There have been a few weird errors and silent failures here over the years.)
Do check that any managed switch firmware is current too, as down-revision firmware has led to many weird errors over the years.
If local policy precludes showing the details here and only permits descriptions of the configuration in general details, then -- if running the usual debugging by division and if a second review of the configuration fails to isolate a trigger -- you're likely going to have to call in somebody in possession of whatever appropriate security ratings or approvals are needed to take a look at this. We need details beyond what are posted here, and probably beyond what you're permitted to post.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-09-2008 06:41 AM
тАО04-09-2008 06:41 AM