System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

Upgrade to HP11.23 (from HP11.11)

SOLVED
Go to solution
Mark Parsons
Valued Contributor

Upgrade to HP11.23 (from HP11.11)

Hi,

I have recently upgraded my RP5470 from HP11.11 to HP11.23 but I'm having trouble being able to connect to and from the box via the network.
If I do a nslookup of another box I am getting the following error:

"# nslookup 10.129.48.10
*** Can't find server name for address 10.129.48.10: No response from server
*** Can't find server name for address 132.220.120.20: No response from server
*** Can't find server name for address 10.64.135.16: No response from server
*** Default servers are not available
Using /etc/hosts on: dcbk1"

A telnet comes back with the following:

"# telnet 10.129.48.10
Trying...
telnet: Unable to connect to remote host: Network is unreachable"

I've missed something really obvious. I didn't have this trouble when I upgraded another box a few weeks before.

All the networking details were supplied as per when the box was HP11.11

1) This is a copy of netconf

# more netconf
# cd rc.config.d
# netconf: configuration values for core networking subsystems
#
# @(#) $Revision: 1.6.119.6 $ $Date: 97/09/10 15:56:01 $
#
# HOSTNAME: Name of your system for uname -S and hostname
#
# OPERATING_SYSTEM: Name of operating system returned by uname -s
# ---- DO NOT CHANGE THIS VALUE ----
#
# LOOPBACK_ADDRESS: Loopback address
# ---- DO NOT CHANGE THIS VALUE ----
#
# IMPORTANT: for 9.x-to-10.0 transition, do not put blank lines between
# the next set of statements

HOSTNAME="dcbk1"
OPERATING_SYSTEM=HP-UX
LOOPBACK_ADDRESS=127.0.0.1

# Internet configuration parameters. See ifconfig(1m), autopush(1m)
#
# INTERFACE_NAME: Network interface name (see lanscan(1m))
# cat netconf
# netconf: configuration values for core networking subsystems
#
# @(#) $Revision: 1.6.119.6 $ $Date: 97/09/10 15:56:01 $
#
# HOSTNAME: Name of your system for uname -S and hostname
#
# OPERATING_SYSTEM: Name of operating system returned by uname -s
# ---- DO NOT CHANGE THIS VALUE ----
#
# LOOPBACK_ADDRESS: Loopback address
# ---- DO NOT CHANGE THIS VALUE ----
#
# IMPORTANT: for 9.x-to-10.0 transition, do not put blank lines between
# the next set of statements

HOSTNAME="dcbk1"
OPERATING_SYSTEM=HP-UX
LOOPBACK_ADDRESS=127.0.0.1

# Internet configuration parameters. See ifconfig(1m), autopush(1m)
#
# INTERFACE_NAME: Network interface name (see lanscan(1m))
#
# IP_ADDRESS: Hostname (in /etc/hosts) or IP address in decimal-dot
# notation (e.g., 192.1.2.3)
#
# SUBNET_MASK: Subnetwork mask in decimal-dot notation, if different
# from default
#
# BROADCAST_ADDRESS: Broadcast address in decimal-dot notation, if
# different from default
#
# INTERFACE_STATE: Desired interface state at boot time.
# either up or down, default is up.
#
# DHCP_ENABLE Determines whether or not DHCP client functionality
# will be enabled on the network interface (see
# auto_parms(1M), dhcpclient(1M)). DHCP clients get
# their IP address assignments from DHCP servers.
# 1 enables DHCP client functionality; 0 disables it.
#
# INTERFACE_MODULES: A list of modules to be pushed on a stream
# associated with an interface. For example,
# INTERFACE_MODULES[0]="mod1 mod2 ... modN-1 modN"
# pushes modN on top of modN-1.
#
# For each additional network interfaces, 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

INTERFACE_NAME[1]="lan1"
IP_ADDRESS[1]="10.64.69.20"
SUBNET_MASK[1]="255.255.255.0"
BROADCAST_ADDRESS[1]="10.64.69.255"
INTERFACE_STATE[1]="up"
DHCP_ENABLE[1]=0
INTERFACE_MODULES[1]=""
#
# 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[1]=default
# ROUTE_MASK[1]=""
# ROUTE_GATEWAY[1]="10.64.69.1"
# ROUTE_COUNT[1]=""
# ROUTE_ARGS[1]=""

# 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

#
# Network interface configuration. See ifconfig(1m)
#
# DEFAULT_INTERFACE_MODULES contains a default list of modules to be
# pushed on a stream associated with an interface. For example,
# INTERFACE_MODULES[0]="mod1 mod2 ... modN-1 modN" pushes modN on top
# of modN-1.
#
# Precedence rules:
# 1) The module names specified in INTERFACE_MODULES[] for the specified
# interface overrides the modules in DEFAULT_INTERFACE_MODULES. For
# example, INTERFACE_MODULES[0]="foo" and
# DEFAULT_INTERFACE_MODULES="m1 m2", then the module list applied
# will be "foo".
#
# 2) If INTERFACE_MODULES[] is set to null string, then the module
# names specified in DEFAULT_INTERFACE_MODULES will be used for the
# specified interface. For example, INTERFACE_MODULES[0]="" ( or
# INTERFACE_MODULES[0]= ) and DEFAULT_INTERFACE_MODULES="m1 m2",
# then the applied module list will be "m1,m2".
#
# 3) If INTERFACE_MODULES[] is explicitly set to "NONE", then no module
# list will be applied for the specified interface. For example, if
# INTERFACE_MODULES[0]="NONE" and DEFAULT_INTERFACE_MODULES="m1 m2",
# then there will be no -m option applied to the interface.
# Restriction: The module name can't be "NONE", and "NONE" is not
# case sensitive.

DEFAULT_INTERFACE_MODULES=""
#

2) This is a copy of /etc/hosts

# cat /etc/hosts
# @(#)B11.23_LRhosts $Revision: 1.9.214.1 $ $Date: 96/10/08 13:20:01 $
#
# The form for each entry is:
#
#
# For example:
# 192.1.2.34 hpfcrm loghost
#
# See the hosts(4) manual page for more information.
# Note: The entries cannot be preceded by a space.
# The format described in this file is the correct format.
# The original Berkeley manual page contains an error in
# the format description.
#

127.0.0.1 localhost loopback
10.64.69.20 dcbk1.uk.eurw.ey.net dcbk1
10.64.157.10 drbk1
10.64.191.6 ey_itt_time
132.220.120.16 uklondeylp.uk.eurw.ey.net uklondeylp
10.64.132.120 uk.ey.com

3) This is a copy of resolv.conf

# cat /etc/resolv.conf
domain uk.eurw.ey.net
nameserver 10.129.48.10
nameserver 132.220.120.20
nameserver 10.64.135.16
search uk.eurw.ey.net ernsty.co.uk
retry 1
retrans 500
#

Hope someone can help!

Kind Regards,

Mark Parsons.

5 REPLIES
Steven E. Protter
Exalted Contributor

Re: Upgrade to HP11.23 (from HP11.11)

Shalom,

Make sure any backup copies of netconf are not in /etc/rc.config.d . Duplicates will be read twice by network and that will result in no networking at all.

netstat -rn

Please post.

I suspect update-ux hosed something. update-ux should not be used for major version upgrades. I base that on experience. I'm just beginning this week to see how it does at updating the OE within a major version, using DRD, but have never had any consistent success with update-ux for major version upgrades.

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
Larry Klasmier
Honored Contributor

Re: Upgrade to HP11.23 (from HP11.11)

Can you ping the default gateway?
Mark Parsons
Valued Contributor

Re: Upgrade to HP11.23 (from HP11.11)

1) Just to let you know that I ran a cold install.

2) # netstat -rn
Routing tables
Destination Gateway Flags Refs Interface Pmtu
127.0.0.1 127.0.0.1 UH 0 lo0 4136
10.64.69.20 10.64.69.20 UH 0 lan1 4136
10.64.69.0 10.64.69.20 U 2 lan1 1500
127.0.0.0 127.0.0.1 U 0 lo0 0

3) Default gateway can be pinged

# ping 10.64.69.1
PING 10.64.69.1: 64 byte packets
64 bytes from 10.64.69.1: icmp_seq=0. time=1. ms
64 bytes from 10.64.69.1: icmp_seq=1. time=0. ms
64 bytes from 10.64.69.1: icmp_seq=2. time=0. ms
64 bytes from 10.64.69.1: icmp_seq=3. time=0. ms

----10.64.69.1 PING Statistics----
4 packets transmitted, 4 packets received, 0% packet loss
round-trip (ms) min/avg/max = 0/0/1

Thanks - Mark P.
Torsten.
Acclaimed Contributor
Solution

Re: Upgrade to HP11.23 (from HP11.11)

The route entries in netconf are commented (#). Check this.

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Mark Parsons
Valued Contributor

Re: Upgrade to HP11.23 (from HP11.11)

Torsten - you are a star! It was so obvious!