ip configuration problem!!

[Ionut Grigorescu_2]

Hello,

I have a K class box with HPUX 11.00 and 3 NIC's:
lan0 - driver btlan1
lan1 - driver lan2
lan2 - driver btlan1

I have changed the ip configuration in the netconf (see below) and rebooted the box. Before changing lan0 was 10.1.32.12 and lan1 was 10.80.241.12, the problem was that lan1 is built-in lan and the NIC can only 10M and on the box is running an apache server which is listening on 10.80.241.12 so I wanted to change to 100M FullDuplex. But after the reboot the lan0 is again 10.1.32.12 and lan1 10.80.241.12 - where is the problem????



INTERFACE_NAME[0]=lan0
IP_ADDRESS[0]=10.80.241.12
SUBNET_MASK[0]=255.255.255.240
BROADCAST_ADDRESS[0]=10.80.241.15
INTERFACE_STATE[0]=up
DHCP_ENABLE[0]=0

INTERFACE_NAME[1]=lan1
IP_ADDRESS[1]=10.1.32.12
SUBNET_MASK[1]=255.255.255.224
BROADCAST_ADDRESS[1]=10.1.32.31
INTERFACE_STATE[1]=up
DHCP_ENABLE[1]=0

INTERFACE_NAME[2]=lan2
IP_ADDRESS[2]=62.180.105.41
SUBNET_MASK[2]=255.255.255.240
BROADCAST_ADDRESS[2]=62.180.105.47
INTERFACE_STATE[2]=up
DHCP_ENABLE[2]=0

# Internet routing configuration. See route(1m), routing(7)
#
# ROUTE_DESTINATION: Destination hostname (in /etc/hosts) or host or network
# IP address in decimal-dot notation, preceded by the word
# "host" or "net"; or simply the word "default".
#
# ROUTE_MASK: Subnetwork mask in decimal-dot notation, or C language
# hexadecimal notation. This is an optional field.
# A IP address, subnet mask pair uniquely identifies
# a subnet to be reached. If a subnet mask is not given,
# then the system will assign the longest subnet mask
# of the configured network interfaces to this route.
# If there is no matching subnet mask, then the system
# will assign the default network mask as the route's
# subnet mask.
#
# ROUTE_GATEWAY: Gateway hostname (in /etc/hosts) or IP address in
# decimal-dot notation. If local interface, must use the
# same form as used for IP_ADDRESS above (hostname or
# decimal-dot notation). If loopback interface, i.e.,
# 127.0.0.1, the ROUTE_COUNT must be set to zero.
#
# ROUTE_COUNT: An integer that indicates whether the gateway is a
# remote interface (one) or the local interface (zero)
# or loopback interface (e.g., 127.*).
#
# ROUTE_ARGS: Route command arguments and options. This variable
# may contain a combination of the following arguments:
# "-f", "-n" and "-p pmtu".
#
# For each additional route, add a set of variable assignments like the ones
# below, changing the index to "[1]", "[2]" et cetera.
#
# IMPORTANT: for 9.x-to-10.0 transition, do not put blank lines between
# the next set of statements

# ROUTE_DESTINATION[0]=default
# ROUTE_MASK[0]=""
# ROUTE_GATEWAY[0]=""
# ROUTE_COUNT[0]=""
# ROUTE_ARGS[0]=""

# Dynamic routing daemon configuration. See gated(1m)
#
# GATED: Set to 1 to start gated daemon.
# GATED_ARGS: Arguments to the gated daemon.

GATED=0
GATED_ARGS=""

#
# Router Discover Protocol daemon configuration. See rdpd(1m)
#
# RDPD: Set to 1 to start rdpd daemon
#

RDPD=0

#
# Reverse ARP daemon configuration. See rarpd(1m)
#
# RARP: Set to 1 to start rarpd daemon
#

RARP=0

ROUTE_GATEWAY[0]=10.1.32.1
ROUTE_COUNT[0]=1
ROUTE_DESTINATION[0]="net 10.1.60.0"
IP_ADDRESS[0]=10.1.32.12
SUBNET_MASK[0]=255.255.255.240

ROUTE_GATEWAY[1]=10.80.241.3
ROUTE_COUNT[1]=1
ROUTE_DESTINATION[1]=default
IP_ADDRESS[1]=10.80.241.12
SUBNET_MASK[1]=255.255.255.224

ROUTE_GATEWAY[2]=10.1.32.1
ROUTE_COUNT[2]=1
ROUTE_DESTINATION[2]="host 172.16.1.2"

[Orhan Biyiklioglu]

You have IP_ADDRESS[?] lines on the bottom lines of the file near the routing definitions delete these lines or change them accordingly.

ROUTE_GATEWAY[0]=10.1.32.1
ROUTE_COUNT[0]=1
ROUTE_DESTINATION[0]="net 10.1.60.0"
>>>IP_ADDRESS[0]=10.1.32.12
SUBNET_MASK[0]=255.255.255.240

ROUTE_GATEWAY[1]=10.80.241.3
ROUTE_COUNT[1]=1
ROUTE_DESTINATION[1]=default
>>>>IP_ADDRESS[1]=10.80.241.12
SUBNET_MASK[1]=255.255.255.224

Since these lines comes after the previous lines they are accepted.

hth

[melvyn burnard]

Did you perhaps make a backup of th enetconf file prior to making these changes?
e.g. netconf.old

If so, this may be causing the problem.
ALL files in the rc.config.d get sourced at start time, and as netconf.old appears after netconf, it may be that it is reading in the old values.
If so, it is not recommended to do this, rather create a backup directory in rc.config.d and create backup copies in there.

Having said that, I notice at the bottome of your netconf file you have:
ROUTE_GATEWAY[0]=10.1.32.1
ROUTE_COUNT[0]=1
ROUTE_DESTINATION[0]="net 10.1.60.0"
IP_ADDRESS[0]=10.1.32.12 <<<<< BAD
SUBNET_MASK[0]=255.255.255.240 <<<<< BAD

ROUTE_GATEWAY[1]=10.80.241.3
ROUTE_COUNT[1]=1
ROUTE_DESTINATION[1]=default
IP_ADDRESS[1]=10.80.241.12 <<<<< BAD
SUBNET_MASK[1]=255.255.255.224 <<<<< BAD

ROUTE_GATEWAY[2]=10.1.32.1
ROUTE_COUNT[2]=1
ROUTE_DESTINATION[2]="host 172.16.1.2"

Comment out or remove the above matrked 4 lines

[Ionut Grigorescu_2]

thank you Melvin,

the fact is I have a lot of netconf.xxxx in /etc/rc.config.d directory and never had a problem until now. I thought is maybe a problem that the system IP address (set_parms) is set to 10.80.241.12 and the lan1 being the built-in lan - so the default - this lan1 will get the system ip address. Is that?

[AwadheshPandey]

configure ur netconf file in proper sequence and check ur /etc/hosts file for previous entries.

Awadhesh

[Orhan Biyiklioglu]

Removing the following lines

SUBNET_MASK[0]=255.255.255.240
BROADCAST_ADDRESS[0]=10.80.241.15

SUBNET_MASK[1]=255.255.255.224
BROADCAST_ADDRESS[1]=10.1.32.31

and running /sbin/init.d/net start should resolve your problem.