GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Stand-by lan card in Service Guard and traffic
Operating System - HP-UX
1848097
Members
5354
Online
104022
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
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
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
04-08-2003 06:10 AM
04-08-2003 06:10 AM
Hello,
my environnment is a 2 nodes cluster (srervice Guard); each node has two lan cards.
Lan1 is the production lan, lan5 is the stan-by lan. In GPM i see all the traffic going through lan1, but there are few packets per seconds (inbount but also outbound!) from lan5: i did'nt expected this.
Ifconfig lan5 gives me 0.0.0.0.
is it correct?
Thanks in advance
Roberto
my environnment is a 2 nodes cluster (srervice Guard); each node has two lan cards.
Lan1 is the production lan, lan5 is the stan-by lan. In GPM i see all the traffic going through lan1, but there are few packets per seconds (inbount but also outbound!) from lan5: i did'nt expected this.
Ifconfig lan5 gives me 0.0.0.0.
is it correct?
Thanks in advance
Roberto
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2003 07:16 AM
04-08-2003 07:16 AM
Solution
Roberto,
I expect this is ServiceGuard ensuring that the interface can be accessed at the data link level.
This is from Chapter 4 of the 'Managing ServiceGuard' manual:
Network Polling Interval
The frequency at which the networks configured for MC/ServiceGuard are checked. In the ASCII cluster configuration file, this parameter is NETWORK_POLLING_INTERVAL.
Default is 2,000,000 microseconds in the ASCII file (2 seconds in SAM). Thus every 2 seconds, the network manager polls each network interface to make sure it can still send and receive information. Changing this value can affect how quickly a network failure is detected.
The minimum value is 1,000,000 (1 second). The maximum value recommended is 15 seconds, and the maximum value supported is 30 seconds.
HTH
Duncan
I am an HPE Employee
I expect this is ServiceGuard ensuring that the interface can be accessed at the data link level.
This is from Chapter 4 of the 'Managing ServiceGuard' manual:
Network Polling Interval
The frequency at which the networks configured for MC/ServiceGuard are checked. In the ASCII cluster configuration file, this parameter is NETWORK_POLLING_INTERVAL.
Default is 2,000,000 microseconds in the ASCII file (2 seconds in SAM). Thus every 2 seconds, the network manager polls each network interface to make sure it can still send and receive information. Changing this value can affect how quickly a network failure is detected.
The minimum value is 1,000,000 (1 second). The maximum value recommended is 15 seconds, and the maximum value supported is 30 seconds.
HTH
Duncan
I am an HPE Employee
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2003 08:23 AM
04-08-2003 08:23 AM
Re: Stand-by lan card in Service Guard and traffic
Yes this is correct.
Your cmcld process is ensuring that the networks are healthy by polling out and in on all the networks on both nodes, so you will see small amounts of traffic appearing. This is one of hte ways cmcld detects an issue with the network if it sees no incoming traffic over a period of time.
As for the ip address, that is standrad for an unconfigured lan used as a standby.
If you do netstat -in you will see it is marked wiht an * showing it is unconfigured.
Also if you halt the cluster and this is HP-UX 11.x, you will find netstat -in will no longer show that lan!
HTH
Your cmcld process is ensuring that the networks are healthy by polling out and in on all the networks on both nodes, so you will see small amounts of traffic appearing. This is one of hte ways cmcld detects an issue with the network if it sees no incoming traffic over a period of time.
As for the ip address, that is standrad for an unconfigured lan used as a standby.
If you do netstat -in you will see it is marked wiht an * showing it is unconfigured.
Also if you halt the cluster and this is HP-UX 11.x, you will find netstat -in will no longer show that lan!
HTH
My house is the bank's, my money the wife's, But my opinions belong to me, not HP!
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