Sponsored Content
Homework and Emergencies Emergency UNIX and Linux Support HP-UX: Help to Change network configuration from APA manual mode (2Gbps) to simple fail over (1Gbps) Post 302906000 by prvnrk on Monday 16th of June 2014 02:33:54 PM
Old 06-16-2014
HP-UX: Help to Change network configuration from APA manual mode (2Gbps) to simple fail over (1Gbps)

Hello HP-UX experts,

Server = rx8640 Node partition
OS = HP-UX 11.23
arch = IA64
Network switch = Foundry 16 port switch (1Gbps)

Existing configuration: Tough to explain as it is very messy (see below for the link of zip of network related fles). 2 x 2Gbps aggregates configured some time ago. But suddenly faced some packet loss issue and it was solved by disabling one of the ports (of aggregate) on one of the switch. There were two interfaces which formed lan900 however one cable was going to one switch and another to another switch. Networks team confirmed that both switches were seeing same MAC address and both were receiving packets at the same time hence disabling on of the network port on one of the switch resolved the packet loss issue. however now the server doesn't have any resilience and its running only on one network interface with 1gbps bandwidth. server also has a service guard package name dbXY0.

As it is noticed that 1Gbps throughput would be enough for the server, its decided NOT to use any aggregate instead a simple failover (2 NICs - 1Gbps each active/passive LAN_MONITOR mode). Could anyone please suggest me how to remove existing APA config and configure simple fail over (1Gbps throughput) using LAN_Monitor mode? I'm not entirely sure which Interfaces I need to deconfigure and which interfaces to configure for new setup as service guard config should not get affected.

Pl let me know if any more info needed from my end. Appreciate any professional help!

Thanks a lot.

Note: I'm unable to attach zip of various network commands' output - getting "invalid thread contact admin" error. So uploaded to dropbox, here is the link
 

9 More Discussions You Might Find Interesting

1. HP-UX

HP-UX Network Configuration

Hi, I have installed a HP-UX B.11.00 U 9000/800 Server in one of the domain. And I'm also able to telnet/ping into this server from systems in the same domain. But I'm not able to telnet/ping into this server from a different domain. So, what shoud need to do to achieve this... (6 Replies)
Discussion started by: S.Vishwanath
6 Replies

2. Solaris

network configuration

hi again... i configured my network settings sometiime ago using the sys-unconfig command.the active link was rtls0. there was some problem with the network so i changed the ISP. now when im trying to reconfigure the system wit sys-unconfig, it tries to configure the network on rtls1 (and shows... (1 Reply)
Discussion started by: strider
1 Replies

3. SCO

Network Configuration

I have a SCO 5.07 Server and I am trying to get it on my network. I have edited the /etc/hosts file and /etc/rc2.d/s99route . I has connectivity on the NIC card but not sure if I am forgetting another file. Thanks! (2 Replies)
Discussion started by: andrewd
2 Replies

4. UNIX for Dummies Questions & Answers

network configuration

I am using solaris 10, my internet works alright but each time i reboot i keep loosing my connection. I will have to use the ifconfig iprb0 192.168.1.xx netmask 255.255.255.0 up and Route add default 192.168.1.xxx command to gain back my internet. I know there is a better way of addressing... (1 Reply)
Discussion started by: seyiisq
1 Replies

5. Solaris

Network configuration

Hi I have installed Solaris 5.10 on Intel x86 machine (standalone). I want to access internet through solaris. How should I configure the network? Is static IP or DHCP advisable? (5 Replies)
Discussion started by: johnl
5 Replies

6. Solaris

Fail to up network interface after system boot

Hi! I have Sun SPARC Enterprise T5140 with Solaris 10 and it unable to up network interface after boot, but after issuing ifconfig interface begins to work... svcs -xv says that service svc:/network/physical:default is failed to start and service log stores something like "service method... (5 Replies)
Discussion started by: Sapfeer
5 Replies

7. Solaris

SC3.2 issue - cluster transport configuration not right - resulting fail

I am trying to set up a two host cluster. trouble is with the cluster transport configuration. i'm using e1000g2 and g3 for the cluster transport. global0 and global1 are my two nodes, and I am running the scinstall from global1. i think i should be expecting, is this: The following... (19 Replies)
Discussion started by: frustin
19 Replies

8. Shell Programming and Scripting

A simple script fail

Hi, I am a programming newbie, I have started learning C++ a couple of months ago. Unfortunately I don't have too much time in my hands to learn it properly. I need to write a simple script for a project I am doing but I am failing quite hard :mad: (the fact that I am learning C++ is completely... (3 Replies)
Discussion started by: Akhlore
3 Replies

9. UNIX for Dummies Questions & Answers

Ubuntu Server - simple network and users configuration

Hello, I am new to Ubuntu Server. Can you please suggest very simple configuration to network. Need: 1. Ubuntu Server (already installed) 2. Connect to it 1 Linux Mint computer (already installed) + 1 computer with Windows 7 (already installed). Need to create 3 groups with... (2 Replies)
Discussion started by: ABQw
2 Replies
lanqueryconf(1M)														  lanqueryconf(1M)

NAME
lanqueryconf - query LAN interface configuration information for LAN_MONITOR mode link aggregates, also called failover groups SYNOPSIS
ascii_file] ascii_file] DESCRIPTION
The command discovers the set of LAN interfaces that can form a failover group and then maps that information to the ASCII configuration file. Options supports the following options: Find existing LAN Monitor failover group configuration from the kernel, and write it to the ASCII configuration file. Specifies the name of the ASCII configuration file into which configuration information is written. See the "ASCII Configuration File" section for information about the file parameters and syn- tax. By default, information is written to the file. Queries the system for the potential failover group configuration, and write it to the ASCII configuration file. Displays verbose output. ASCII Configuration File The default ASCII configuration file is It is similar to the Serviceguard file. This file contains the fields below. Note: the term is used for a physical link or a link aggregate with or mode. o The aggregate name for a LAN Monitor failover group, where XX is a decimal number, starting with 00 (lan900). may generate failover group name where X is the PPA of the physical link. Such failover group will be ignored unless it is modified manually. Each can have the following keywords: o This field can be used to specify the preconfigured IP address on the primary port. o Each failover group must have one primary port. The primary port is usually assigned the highest priority or lowest cost value, so it will be the port that carries traffic initially. The primary port is also the port that may have IP addresses configured. After lanapplyconf creates the failover group, the IP addresses on the primary port (if any is present) are moved to the failover group. Prior versions of APA maintains that the primary port must have IP address configured and must be the highest priority/lowest cost. APA 11i v3 observes neither of these rules: the primary port may be assigned any priority/cost values and it may not have IP addresses configured. Port that carries traffic depends on the priority/cost. HP recommends that the primary port always be assigned the highest priority or the lowest cost in a failover group. o Specifies a standby port for the A standby port is a port that replaces the primary port when the primary is incapable of carrying traffic. Both the and keywords have the following fields: o The LAN interface name (for example, lan0 and lan1). o The port priority that will be assigned to the port. o A cost value for the LAN interface preceded by a colon (:) and a space. This is an optional field. A port with the lowest normalized cost (cost divided by port's speed) will carry traffic. When ports have the same normalized cost, the one with the higher priority is preferred. For each failover group, either all or none of the ports should have the cost values assigned. If none of the ports has cost value assigned, then the failover group uses the default failover behavior based on priority. See the "Proactive Failover" section and the for more information. o The number of microseconds between polling messages. Polling messages are sent between ports in the specified interval for monitoring the health of all the ports in the failover group. The default is 10000000 (10 seconds). This keyword can be specified multiple times in the configuration file. A failover group's polling interval is set to the last specified interval. o The number of polling packets that are missed before deciding to send a log message to the user that indicates the port might have prob- lems and the network should be checked. The default is 3. o Enables (on) or disables (off) the ability to transmit gratuitous ARP messages at intervals shorter than 5 seconds. By default, is on. When the MAC address of a failover group changes, a gratuitous ARP packet is transmitted. To ensure that other clients and servers receive the new IP-MAC address mapping, APA/LAN Monitor transmits more gratuitous ARP packets for 1 minute. When this option is enabled, LAN Monitor will transmit gratuitous ARP at every for a total of times immediately after the MAC address changes. After completing the process, gratuitous ARP packets will be transmitted every 5 seconds until one minute has elapsed since the first gratuitous ARP was transmitted. When this option is disabled, LAN Monitor will transmit gratuitous ARP at every 5 seconds for 1 minute. o Number of microseconds between rapid gratuitous ARP messages. The range of valid values is 1000000-4000000, inclusive (1 second to 4 seconds). The default value is 1000000 (1 second). Specify a whole number of seconds as the value you specify is automatically rounded up to the next whole number of seconds. The value must be a valid integer. If the value is not in the valid range and is on, the interval value last processed with the command is used. If is off, this value is ignored for the corresponding failover group. o Number of gratuitous ARP packets sent rapidly. The valid range is 5-60, inclusive. The default value is 10. The value must be a valid integer. If the value is not in the valid range and is on, the count value last processed with the command is used. If is off, this value is ignored for the corresponding failover group. Proactive Failover By default, the port in a failover group with the highest priority is the active port. With proactive failover, the port that is the most efficient at carrying traffic is the active port. Efficiency is determined by assigning a cost to each port in a failover group. This cost is divided by the port's current speed to yield a normalized port cost; port speed is the number of links in a link aggregate multi- plied by the link speed, or in the case of a physical port, only the link speed. The lower the normalized port cost, the higher the port's efficiency. During certain LAN Monitor events, the normalized port cost might change on the active or standby ports. When these events occur, the nor- malized port cost of the active port and the standby ports are compared. If a standby port has a lower normalized port cost than the active port, the standby port becomes the active port. Sample File The file specifies failover groups and with total number of 2, 4, 2, 2, and 1 ports in each, respectively. The first network interface listed is the primary and the subsequent ones are the standby interfaces. Failover groups and have polling interval of 5 seconds and dead count of 2; and have polling interval of 10 seconds and dead count of 3. is enabled (on). There are IP addresses preconfigured on the primary ports of lan900 and lan905. There are no IP address preconfigured on the primary ports of lan901 and lan902. is a cost-based failover group. The cost values are preceded by a colon and a space. The primary port has the lowest cost. is also a cost-based failover group. The primary port and the standby port have the same cost, but the primary port has higher priority. When the failover group is created, the normalized cost determines which port will be the active port; it might not be the one designated as in the ASCII configuration file. When the failover group is cleared, the IP address switches back to the port specified as in the ASCII file if the primary port preconfigured IP address when creating the failover group. is a single-port failover group, no aggregate is allocated for it. POLLING_INTERVAL 10000000 DEAD_COUNT 3 LM_RAPID_ARP on LM_RAPID_ARP_INTERVAL 1000000 LM_RAPID_ARP_COUNT 10 FAILOVER_GROUP lan1 STATIONARY_IP 193.12.14.54 FAILOVER_GROUP lan900 STATIONARY_IP 194.12.14.55 PRIMARY lan2 5 STANDBY lan3 3 FAILOVER_GROUP lan901 PRIMARY lan4 5 STANDBY lan5 4 STANDBY lan7 3 STANDBY lan6 3 POLLING_INTERVAL 5000000 DEAD_COUNT 2 FAILOVER_GROUP lan902 PRIMARY lan903 5 : 2 STANDBY lan904 3 : 3 FAILOVER_GROUP lan905 STATIONARY_IP 192.12.14.56 PRIMARY lan907 9 : 3 STANDBY lan908 7 : 3 AUTHOR
was developed by HP. SEE ALSO
lanapplyconf(1M), lancheckconf(1M), landeleteconf(1M), lanscan(1M), netstat(1M). User manuals at lanqueryconf(1M)
All times are GMT -4. The time now is 01:36 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy