Sponsored Content
Full Discussion: veritas and nic cards
Special Forums UNIX and Linux Applications High Performance Computing veritas and nic cards Post 302200164 by hercu on Wednesday 28th of May 2008 03:47:44 PM
Old 05-28-2008
Since you are mentioning heartbeat, looks as if you are installing VCS... You can use any NIC and a Virtual IP will be assigned over that NIC. You can also select two NIC's for primary and secondary heartbeat links - They will both be virtual IP's.

Continue with the installation and output of ifconfig -a will show you the change later on.... keep asking but giving more details is always better.

Cheers
 

10 More Discussions You Might Find Interesting

1. Solaris

NIC cards for sunblade 100

I need to add a PCI NIC to a sunblade 100 running solaris 8. Im new to this and was hoping someone could give me some card names and models which will work for this system and has a driver for this sparc system. thanks (3 Replies)
Discussion started by: meyersp
3 Replies

2. IP Networking

Setup 2 NIC cards in one UNIX system

Hi; I have a UNIX box (SCO 5.0.2) with two (2) NIC cards. One card (NIC1) talks to a network 57.14.65.x/27. The other card NIC2) talks to users on 57.14.103.x and 57.14.105.x with subnet mask of 255.255.0.0. If I set NIC2 to this subnet mask (255.255.0.0) it seems like the NIC traffic is now... (2 Replies)
Discussion started by: texaspanama
2 Replies

3. HP-UX

routing issues with multiple NIC cards

I am running HP_UX 11.23 with 4 NIC cards (this is our TSM server) I have 4 subnets we are backing across. trying to keep traffic on their subnets. I only have one route statment should I add more. route add net 123.99.8.0 netmask 255.255.255.0 123.99.8.254 route add net 123.99.67.0 netmask... (2 Replies)
Discussion started by: myork
2 Replies

4. Red Hat

External NIC cards not pinging with each other in RHEL 5.1

We have a setup of two nodes which has two NIC cards in each. One is built in and another is D-Link (external NIC card). We are unable to ping to the external NIC cards in both. Eg: Node A has two IPs 192.168.1.10 (eth0) and 192.168.2.10 (eth1) and Node B has two IPs 192.168.1.20 (eth0) and... (3 Replies)
Discussion started by: durgaprasadr13
3 Replies

5. HP-UX

HP UX 9000 NIC CARDS

Hello, I am trying to move an HP UX from one locaion to another. The new location don't have any Fiber switches. On the back of my server I see 2 RJ 45 for console management the other for networking , the server also has a fiber NIC card. When I disconnec the fiber and want to user regular... (1 Reply)
Discussion started by: ldaliosmane
1 Replies

6. IP Networking

Best reference for understanding low level info on nic cards drivers and functionality

Hi, What is the best reference that gives in detail on nic cards configuration , assigning multiple ip addresses to a single interface, netlink library etc and all basic stuff at this level..? Thanks (2 Replies)
Discussion started by: Gopi Krishna P
2 Replies

7. Ubuntu

Help asap squid with 2 nic cards setup

I found an old post that talks about 2 nice cards and it is driven by the IP address .... but I didn't understand it because the 2 people skipped information for me the newbie.. Can someone help me... I have the proxy server setup and I believe I have enabled the 2nd nic card, I just need one... (1 Reply)
Discussion started by: trilju2005
1 Replies

8. Ubuntu

How do you setup 2 nic cards for squid Ubuntu server?

I have a made my squid proxy, I now have add another nic card to an old CPU using Ubuntu server 12.04. I have seen another post similar however I am new and did not understand some of it. Something about redirecting IP address and IP table? I don't know how to do this.:confused: (9 Replies)
Discussion started by: trilju2005
9 Replies

9. Linux

Add two different subnet public IPs to single NIC or two different NIC on same box

Hello Admins, My ask is how can I add two different subnet IPs to same box with two different gateways? The issue is I can connect to the box when I am on ethernet LAN, but I am not able to connect to the same IP when I am on wifi. The server is RHEL 7 VM on vmware. How can I get connected... (4 Replies)
Discussion started by: snchaudhari2
4 Replies

10. UNIX for Beginners Questions & Answers

How to extend a disk in veritas volume manager in veritas cluster?

Hi Experts, I wanted to extend a veritas file system which is running on veritas cluster and mounted on node2 system. #hastatus -sum -- System State Frozen A node1 running 0 A node2 running 0 -- Group State -- Group System Probed ... (1 Reply)
Discussion started by: Skmanojkum
1 Replies
in.mpathd(1M)															     in.mpathd(1M)

NAME
in.mpathd - daemon for network adapter (NIC) failure detection, recovery, automatic failover and failback SYNOPSIS
/usr/lib/inet/in.mpathd The in.mpathd daemon performs Network Interface Card (NIC) failure and repair detection. In the event of a NIC failure, it causes IP net- work access from the failed NIC to failover to a standby NIC, if available, or to any another operational NIC that has been configured as part of the same network multipathing group. Once the failed NIC is repaired, all network access is restored to the repaired NIC. The in.mpathd daemon can detect NIC failure and repair through two methods: by monitoring the IFF_RUNNING flag for each NIC (link-based failure detection), and by sending and receiving ICMP echo requests and replies on each NIC (probe-based failure detection). Link-based failure detection requires no explicit configuration and thus is always enabled (provided the NIC driver supports the feature); probe-based failure detection must be enabled through the configuration of one or more test addresses (described below), but has the benefit of testing the entire NIC send and receive path. If only link-based failure detection is enabled, then the health of the interface is determined solely from the state of the IFF_RUNNING flag. Otherwise, the interface is considered failed if either of the two methods indicate a failure, and repaired once both methods indi- cate the failure has been corrected. Not all interfaces in a group need to be configured with the same failure detection methods. As mentioned above, in order to perform probe-based failure detection in.mpathd needs a special test address on each NIC for the purpose of sending and receiving probes on the NIC. Use the ifconfig command -failover option to configure these test addresses. See ifconfig(1M). The test address must belong to a subnet that is known to the hosts and routers on the link. The in.mpathd daemon can detect NIC failure and repair by two methods, by sending and receiving ICMP echo requests and replies on each NIC, and by monitoring the IFF_RUNNING flag for each NIC. The link state on some models of NIC is indicated by the IFF_RUNNING flag, allowing for faster failure detection when the link goes down. The in.mpathd daemon considers a NIC to have failed if either of the above two meth- ods indicates failure. A NIC is considered to be repaired only if both methods indicate the NIC is repaired. The in.mpathd daemon sends the ICMP echo request probes to on-link routers. If no routers are available, it sends the probes to neighboring hosts. Thus, for network failure detection and repair, there must be at least one neighbor on each link that responds to ICMP echo request probes. in.mpathd works on both IPv4 and IPv6. If IPv4 is plumbed on a NIC, an IPv4 test address is configured on theNIC, and the NIC is configured as part of a network multipathing group, then in.mpathd will start sending ICMP probes on the NIC using IPv4. In the case of IPv6, the link-local address must be configured as the test address. The in.mpathd daemon will not accept a non-link-local address as a test address. If the NIC is part of a multipathing group, and the test address has been configured, then in.mpathd will probe the NIC for failures using IPv6. Even if both the IPv4 and IPv6 protocol streams are plumbed, it is sufficient to configure only one of the two, that is, either an IPv4 test address or an IPv6 test address on a NIC. If only an IPv4 test address is configured, it probes using only ICMPv4. If only an IPv6 test address is configured, it probes using only ICMPv6. If both type test addresses are configured, it probes using both ICMPv4 and ICMPv6. The in.mpathd daemon accesses three variable values in /etc/default/mpathd: FAILURE_DETECTION_TIME, FAILBACK and TRACK_INTER- FACES_ONLY_WITH_GROUPS. The FAILURE_DETECTION_TIME variable specifies the NIC failure detection time for the ICMP echo request probe method of detecting NIC fail- ure. The shorter the failure detection time, the greater the volume of probe traffic. The default value of FAILURE_DETECTION_TIME is 10 seconds. This means that NIC failure will be detected by in.mpathd within 10 seconds. NIC failures detected by the IFF_RUNNING flag being cleared are acted on as soon as the in.mpathd daemon notices the change in the flag. The NIC repair detection time cannot be configured; however, it is defined as double the value of FAILURE_DETECTION_TIME. By default, in.mpathd does failure detection only on NICs that are configured as part of a multipathing group. You can set TRACK_INTER- FACES_ONLY_WITH_GROUPS to no to enable failure detection by in.mpathd on all NICs, even if they are not part of a multipathing group. How- ever, in.mpathd cannot do failover from a failed NIC if it is not part of a multipathing group. The in.mpathd daemon will restore network traffic back to the previously failed NIC, after it has detected a NIC repair. To disable this, set the value of FAILBACK to no in /etc/default/mpathd. /etc/default/mpathd Contains default values used by the in.mpathd daemon. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsr | +-----------------------------+-----------------------------+ ifconfig(1M), attributes(5), icmp(7P), icmp6(7P), Test address address is not unique; disabling probe based failure detection In order for in.mpathd to perform probe-based failure detection, each configured test address on the system must be unique. Since the IPv6 test address is a link-local address derived from the ethernet address, each NIC must have a unique MAC address. NIC interface_name of group group_name is not plumbed for IPv[4|6] and may affect failover capability All NICs in a multipathing group must be homogeneously plumbed. For example, if a NIC is plumbed for IPv4, then all NICs in the group must be plumbed for IPv4. The streams modules pushed on all NICs must be identical. No test address configured on interface interface_name disabling probe-based failure detection on it In order for in.mpathd to perform probe-based failure detection on a NIC, it must be configured with a test address: IPv4, IPv6, or both. The link has come up on interface_name more than 2 times in the last minute; disabling failback until it stabilizes. In order to prevent interfaces with intermittent hardware, such as a bad cable, from causing repeated failovers and failbacks, in.mpathd does not failback to interfaces with frequently fluctuating link states. Invalid failure detection time assuming default 10000 An invalid value was encountered for FAILURE_DETECTION_TIME in the /etc/default/mpathd file. Too small failure detection time of time assuming minimum 100 The minimum value that can be specified for FAILURE_DETECTION_TIME is currently 100 milliseconds. Invalid value for FAILBACK value Valid values for the boolean variable FAILBACK are yes or no. Invalid value for TRACK_INTERFACES_ONLY_WITH_GROUPS value Valid values for the boolean variable TRACK_INTERFACES_ONLY_WITH_GROUPS are yes or no. Cannot meet requested failure detection time of time ms on (inet[6] interface_name) new failure detection is time ms The round trip time for ICMP probes is higher than necessary to maintain the current failure detection time. The network is probably con- gested or the probe targets are loaded. in.mpathd automatically increases the failure detection time to whatever it can achieve under these conditions. Improved failure detection time time ms on (inet[6] interface_name) The round trip time for ICMP probes has now decreased and in.mpathd has lowered the failure detection time correspondingly. NIC failure detected on interface_name in.mpathd has detected NIC failure on interface_name, and has set the IFF_FAILED flag on NIC interface_name. Successfully failed over from NIC interface_name1 to NIC interface_name2 in.mpathd has caused the network traffic to failover from NIC interface_name1 to NIC interface_name2, which is part of the multipathing group. NIC repair detected on interface_name in.mpathd has detected that NIC interface_name is repaired and operational. If the IFF_FAILED flag on the NIC was previously set, it will be reset. Successfully failed back to NIC interface_name in.mpathd has restored network traffic back to NIC interface_name, which is now repaired and operational. The link has gone down on interface_name in.mpathd has detected that the IFF_RUNNING flag for NIC interface_name has been cleared, indicating the link has gone down. The link has come up on interface_name in.mpathd has detected that the IFF_RUNNING flag for NIC interface_name has been set, indicating the link has come up. 4 May 2004 in.mpathd(1M)
All times are GMT -4. The time now is 08:41 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy