- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- METRICVIEW
Operating System - OpenVMS
1753758
Members
4600
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
тАО12-29-2008 01:50 PM
тАО12-29-2008 01:50 PM
METRICVIEW
We have a 3 node cluster, all Itaniums running VMS version 8.3-1H1 ... TCPIP V5.6 ECO 2. The load broker and metric server are configured on all 3 systems. The load broker config file is exactly the same for all 3 systems.
When TCPIP was initially configured on one system, the host name was entered as a fully qualified name (host.domain.name). The other 2 were configured with just the host name without the domain suffix. Everything worked fine and when you did a METRICVIEW on any particular node it would display all 3 nodes.
The IP host name for the one system was redefined to follow the format of the other 2 (just host name without domain). Now when you do a METRICVIEW on the other 2 nodes, you don't see the system that had the name change. On the system that had the name change, you only see that node.
I have defined the DEBUG logicals for both the load broker and metric server and after reviewing the log file, I have confirmed that the load broker is working correctly as is the metric server. It appears that only the METRICVIEW is not displaying all the data.
From the system that had the name change:
$ METRICVIEW
Host Rating
----------- ------
164.58.46.6 px3.swosu.edu 136
From the other systems:
$ METRICVIEW
Host Rating
----------- ------
164.58.46.4 px1.swosu.edu 136
164.58.46.5 px2.swosu.edu 137
Any ideas what the name change messed up ?
When TCPIP was initially configured on one system, the host name was entered as a fully qualified name (host.domain.name). The other 2 were configured with just the host name without the domain suffix. Everything worked fine and when you did a METRICVIEW on any particular node it would display all 3 nodes.
The IP host name for the one system was redefined to follow the format of the other 2 (just host name without domain). Now when you do a METRICVIEW on the other 2 nodes, you don't see the system that had the name change. On the system that had the name change, you only see that node.
I have defined the DEBUG logicals for both the load broker and metric server and after reviewing the log file, I have confirmed that the load broker is working correctly as is the metric server. It appears that only the METRICVIEW is not displaying all the data.
From the system that had the name change:
$ METRICVIEW
Host Rating
----------- ------
164.58.46.6 px3.swosu.edu 136
From the other systems:
$ METRICVIEW
Host Rating
----------- ------
164.58.46.4 px1.swosu.edu 136
164.58.46.5 px2.swosu.edu 137
Any ideas what the name change messed up ?
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-30-2008 12:06 AM
тАО12-30-2008 12:06 AM
Re: METRICVIEW
I know nothing but could it be proxy related ? (full name used in proxy setup)
Wim
Wim
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-30-2008 07:41 AM
тАО12-30-2008 07:41 AM
Re: METRICVIEW
We found the problem .... the subnet mask was entered wrong.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-30-2008 07:43 AM
тАО12-30-2008 07:43 AM
Re: METRICVIEW
When IP was reconfigured, a typo in the subnet mask caused METRICVIEW to not see the other systems.
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