HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- network probing.
Operating System - HP-UX
1833758
Members
2721
Online
110063
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
Forums
Discussions
Discussions
Discussions
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
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
05-02-2006 02:46 AM
05-02-2006 02:46 AM
I was working on service guard and i halted a node. When i restarted it using service guard manager it asked if i started it by cmrunnode command i will be prbing the network. What does that mean ?
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-02-2006 02:53 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-02-2006 02:54 AM
05-02-2006 02:54 AM
Re: network probing.
Shalom,
Serviceguard and most packages include network informaiton. Floating IP address, and such.
Probing the network is not nefarious, its necessary part of SG starting up the node.
Its not a security problem, nor does it threaten other hosts.
SEP
Serviceguard and most packages include network informaiton. Floating IP address, and such.
Probing the network is not nefarious, its necessary part of SG starting up the node.
Its not a security problem, nor does it threaten other hosts.
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-02-2006 10:13 PM
05-02-2006 10:13 PM
Re: network probing.
At some point in the past, Serviceguard was enhanced to do network probing at startup to ensure that the physical network matches that defined in the Serviceguard configuration. This is purely for your benefit and Serviceguard will start after issuing a warning if an anomoly is detected.
This is the message you will see from the command line:
cmruncl: Validating network configuration...
This option is on by default when cmruncl and cmrunnode are used and can be disabled with the -w none option:
-w none By default network probing is performed to check that
the network connectivity is the same as when the
cluster was configured. Any anomalies are reported
before the cluster daemons are started. The -w none
option disables this probing. The option should only be
used if this network configuration is known to be
correct from a recent check.
Serviceguard Manager also gives you the option to probe or not probe and passes this onto the command run when the cluster is started.
Probing normally takes little time and allows you to see any possible configuration or network problems in advance of any failures which may rely on network consistency.
This is the message you will see from the command line:
cmruncl: Validating network configuration...
This option is on by default when cmruncl and cmrunnode are used and can be disabled with the -w none option:
-w none By default network probing is performed to check that
the network connectivity is the same as when the
cluster was configured. Any anomalies are reported
before the cluster daemons are started. The -w none
option disables this probing. The option should only be
used if this network configuration is known to be
correct from a recent check.
Serviceguard Manager also gives you the option to probe or not probe and passes this onto the command run when the cluster is started.
Probing normally takes little time and allows you to see any possible configuration or network problems in advance of any failures which may rely on network consistency.
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 2025 Hewlett Packard Enterprise Development LP