Operating System - HP-UX
1833187 Members
2758 Online
110051 Solutions
New Discussion

Trying To Determine Which LAN is in use

 
SOLVED
Go to solution
B Wade Moll
Frequent Advisor

Trying To Determine Which LAN is in use

I have a server at a remote site that has one lan cable plugged into what is labeled on the server as SLOT 2 & the lan cable is connected to the bottom port. The server has 5 nic cards. three are dual port nics, followed by 2 nic's that have a fiber port & a rj-45 port.

ioscan shows the following:

root@visccov1:/root>ioscan -kfnC lan
Class I H/W Path Driver S/W State H/W Type Description
========================================================================
lan 4 0/2/1/0/6/0 igelan CLAIMED INTERFACE HP AB465-60001 PCI/PCI-X 1000Base-T 2-port 2Gb FC/2-port 1000B-T Combo Adapter
lan 5 0/2/1/0/6/1 igelan CLAIMED INTERFACE HP AB465-60001 PCI/PCI-X 1000Base-T 2-port 2Gb FC/2-port 1000B-T Combo Adapter
lan 0 0/3/1/0 iether CLAIMED INTERFACE HP A7012-60601 PCI/PCI-X 1000Base-T Dual-port Adapter
lan 1 0/3/1/1 iether CLAIMED INTERFACE HP A7012-60601 PCI/PCI-X 1000Base-T Dual-port Adapter
lan 2 0/4/2/0 iether CLAIMED INTERFACE HP AB352-60003 PCI/PCI-X 1000Base-T Dual-port Core
lan 3 0/4/2/1 iether CLAIMED INTERFACE HP AB352-60003 PCI/PCI-X 1000Base-T Dual-port Core
lan 6 0/6/1/0/6/0 igelan CLAIMED INTERFACE HP AB465-60001 PCI/PCI-X 1000Base-T 2-port 2Gb FC/2-port 1000B-T Combo Adapter
lan 7 0/6/1/0/6/1 igelan CLAIMED INTERFACE HP AB465-60001 PCI/PCI-X 1000Base-T 2-port 2Gb FC/2-port 1000B-T Combo Adapter
lan 8 0/7/1/0 iether CLAIMED INTERFACE HP A7012-60601 PCI/PCI-X 1000Base-T Dual-port Adapter
lan 9 0/7/1/1 iether CLAIMED INTERFACE HP A7012-60601 PCI/PCI-X 1000Base-T Dual-port Adapter
root@visccov1:/root>
root@visccov1:/root>lanscan
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
0/2/1/0/6/0 0x0017A4A48494 4 UP lan4 snap4 1 ETHER Yes 119
0/2/1/0/6/1 0x0017A4A48495 5 UP lan5 snap5 2 ETHER Yes 119
0/4/2/0 0x0017A451E592 2 UP lan2 snap2 3 ETHER Yes 119
0/6/1/0/6/0 0x0017A4A4840A 6 UP lan6 snap6 4 ETHER Yes 119
0/6/1/0/6/1 0x0017A4A4840B 7 UP lan7 snap7 5 ETHER Yes 119
0/3/1/0 0x001A4B061C52 0 UP lan0 snap0 6 ETHER Yes 119
0/3/1/1 0x001A4B061C53 1 UP lan1 snap1 7 ETHER Yes 119
0/4/2/1 0x0017A451E593 3 UP lan3 snap3 8 ETHER Yes 119
0/7/1/0 0x001A4B061DAC 8 UP lan8 snap8 9 ETHER Yes 119
0/7/1/1 0x001A4B061DAD 9 UP lan9 snap9 10 ETHER Yes 119
root@visccov1:/root>

I BELIEVE the connection is on lan4. Can someone look at this and possibly confirm that?

Thank you :)
13 REPLIES 13
Johnson Punniyalingam
Honored Contributor
Solution

Re: Trying To Determine Which LAN is in use

Hi ,

Can you Check with "linkloop"

Example:-

# linkloop 0x00306E461911
Link connectivity to LAN station: 0x00306E461911
error: get_msg2 getmsg failed, errno = 4
-- FAILED
frames sent : 1
frames received correctly : 0
reads that timed out : 1

or please check ,

more /etc/rc.config.d/netconf ,

Thanks,
Johnson
Problems are common to all, but attitude makes the difference
Ivan Krastev
Honored Contributor

Re: Trying To Determine Which LAN is in use

Check lanspeed, duplex mode with lanadmin -http://docs.hp.com/en/B2355-90691/lanadmin.1M.html

See also configured network interfaces - netstat -in

regards,
ivan
Johnson Punniyalingam
Honored Contributor

Re: Trying To Determine Which LAN is in use

HP-UX Lan admin manual which details what you want.
http://docs.hp.com/en/B2355-90796/ch03s04.html
Problems are common to all, but attitude makes the difference
B Wade Moll
Frequent Advisor

Re: Trying To Determine Which LAN is in use

Ran linkloop on all the lan connections...


root@visccov1:/root>linkloop 0x0017A4A48494
Link connectivity to LAN station: 0x0017A4A48494
error: expected primitive 0x30, got DL_ERROR_ACK
dl_error_primitive = 0x2d
dl_errno = 0x04
dl_unix_errno = 57
error - did not receive data part of message
root@visccov1:/root>linkloop 0x0017A4A48495
Link connectivity to LAN station: 0x0017A4A48495
error: expected primitive 0x30, got DL_ERROR_ACK
dl_error_primitive = 0x2d
dl_errno = 0x04
dl_unix_errno = 57
error - did not receive data part of message
root@visccov1:/root>linkloop 0x0017A451E592
Link connectivity to LAN station: 0x0017A451E592
error: expected primitive 0x30, got DL_ERROR_ACK
dl_error_primitive = 0x2d
dl_errno = 0x04
dl_unix_errno = 57
error - did not receive data part of message
root@visccov1:/root>linkloop 0x0017A4A4840A
Link connectivity to LAN station: 0x0017A4A4840A
error: expected primitive 0x30, got DL_ERROR_ACK
dl_error_primitive = 0x2d
dl_errno = 0x04
dl_unix_errno = 57
error - did not receive data part of message
root@visccov1:/root>linkloop 0x0017A4A4840B
Link connectivity to LAN station: 0x0017A4A4840B
error: expected primitive 0x30, got DL_ERROR_ACK
dl_error_primitive = 0x2d
dl_errno = 0x04
dl_unix_errno = 57
error - did not receive data part of message
root@visccov1:/root>linkloop 0x001A4B061C52
Link connectivity to LAN station: 0x001A4B061C52
error: expected primitive 0x30, got DL_ERROR_ACK
dl_error_primitive = 0x2d
dl_errno = 0x04
dl_unix_errno = 57
error - did not receive data part of message
root@visccov1:/root>linkloop 0x001A4B061C53
Link connectivity to LAN station: 0x001A4B061C53
error: expected primitive 0x30, got DL_ERROR_ACK
dl_error_primitive = 0x2d
dl_errno = 0x04
dl_unix_errno = 57
error - did not receive data part of message
root@visccov1:/root>linkloop 0x0017A451E593
Link connectivity to LAN station: 0x0017A451E593
error: expected primitive 0x30, got DL_ERROR_ACK
dl_error_primitive = 0x2d
dl_errno = 0x04
dl_unix_errno = 57
error - did not receive data part of message
root@visccov1:/root>linko^?H^[[
root@visccov1:/root>linkloop 0x001A4B061DAC
Link connectivity to LAN station: 0x001A4B061DAC
error: expected primitive 0x30, got DL_ERROR_ACK
dl_error_primitive = 0x2d
dl_errno = 0x04
dl_unix_errno = 57
error - did not receive data part of message
root@visccov1:/root>linkloop 0x001A4B061DAD
Link connectivity to LAN station: 0x001A4B061DAD
error: expected primitive 0x30, got DL_ERROR_ACK
dl_error_primitive = 0x2d
dl_errno = 0x04
dl_unix_errno = 57
error - did not receive data part of message
root@visccov1:/root>
B Wade Moll
Frequent Advisor

Re: Trying To Determine Which LAN is in use

All interfaces are set at 100 FD

root@visccov1:/root>netstat -in
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
lo0 4136 127.0.0.0 127.0.0.1 19822 0 19822 0 0
lan4 1500 138.35.86.128 138.35.86.151 22886 0 22886 0 0
root@visccov1:/root>
Johnson Punniyalingam
Honored Contributor

Re: Trying To Determine Which LAN is in use

>> more /etc/rc.config.d/netconf ,<<

how does it says..?

hope you have fail-over lan Cards configured

Thanks,
Johnson
Problems are common to all, but attitude makes the difference
B Wade Moll
Frequent Advisor

Re: Trying To Determine Which LAN is in use

root@visccov1:/etc/rc.config.d>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="visccov1"
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[0]=
IP_ADDRESS[0]=
SUBNET_MASK[0]=
BROADCAST_ADDRESS[0]=
INTERFACE_STATE[0]=""
DHCP_ENABLE[0]=0
INTERFACE_MODULES[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_GATEWAY[0]="138.35.86.129"
ROUTE_COUNT[0]="1"
#ROUTE_MASK[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)
#
# RARPD: Set to 1 to start rarpd daemon
#

RARPD=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=""
IP_ADDRESS[4]=138.35.86.151
SUBNET_MASK[4]=255.255.255.192
INTERFACE_NAME[4]=lan4
BROADCAST_ADDRESS[4]=138.35.86.255
INTERFACE_STATE[4]=up
root@visccov1:/etc/rc.config.d>

There is only the one lan cable plugged in right now. Our networking team is still setting up a 2d switch. I just ignited the box yesterday and trying to get it up on the one lan.
Johnson Punniyalingam
Honored Contributor

Re: Trying To Determine Which LAN is in use

lan4 1500 138.35.86.128 138.35.86.151 22886 0 22886 0 0

Looks Lan4 --> is in Use, for more information , can you help to attahe /etc/rc.config.d/netconf file will exaplain you clearly,

Thanks,
Johnson
Problems are common to all, but attitude makes the difference
B Wade Moll
Frequent Advisor

Re: Trying To Determine Which LAN is in use

I agree and it's why I configured lan4. Darn thing doesn't want to ping the gateway though...

root@visccov1:/etc/rc.config.d>ifconfig lan4
lan4: flags=1843
inet 138.35.86.151 netmask ffffffc0 broadcast 138.35.86.191
root@visccov1:/etc/rc.config.d>netstat -rnv
Routing tables
Dest/Netmask Gateway Flags Refs Interface Pmtu
127.0.0.1/255.255.255.255 127.0.0.1 UH 0 lo0 4136
138.35.86.151/255.255.255.255 138.35.86.151 UH 0 lan4 4136
138.35.86.128/255.255.255.192 138.35.86.151 U 2 lan4 1500
127.0.0.0/255.0.0.0 127.0.0.1 U 0 lo0 4136
default/0.0.0.0 138.35.86.129 UG 0 lan4 1500
root@visccov1:/etc/rc.config.d>ping 138.35.86.129
PING 138.35.86.129: 64 byte packets

----138.35.86.129 PING Statistics----
10 packets transmitted, 0 packets received, 100% packet loss
root@visccov1:/etc/rc.config.d>
Johnson Punniyalingam
Honored Contributor

Re: Trying To Determine Which LAN is in use

>>Can someone look at this and possibly confirm that? <<

Yes

Its Confirmed that LAN4 is only configured, in your server

DEFAULT_INTERFACE_MODULES=""
IP_ADDRESS[4]=138.35.86.151
SUBNET_MASK[4]=255.255.255.192
INTERFACE_NAME[4]=lan4
BROADCAST_ADDRESS[4]=138.35.86.255
INTERFACE_STATE[4]=up

Thanks,
Johnson
Problems are common to all, but attitude makes the difference
B Wade Moll
Frequent Advisor

Re: Trying To Determine Which LAN is in use

Yes, I configured lan4 based on the description of the slot the cable was plugged into at the remtote site by a technician I asked to tell me where the cable was plugged into.

I'm trying to determine if that's the lan which it's plugged into based on the ioscan and lanscan hardware addresses
Johnson Punniyalingam
Honored Contributor

Re: Trying To Determine Which LAN is in use

>>>>I'm trying to determine if that's the lan which it's plugged into based on the ioscan and lanscan hardware addresses <<

ioscan --> will only show the device "claimed or not sorry not the connectivity. :(

lanscan --> Yes you can

For example if you have NO LINK on the lan4 probaly you "lanscan" --> output will show like below

lan4* 1500 138.35.86.128 138.35.86.151 22886 0 22886 0 0
(pls take note (*)--> means link down, or no link,

Thanks,
Johnson

Problems are common to all, but attitude makes the difference
B Wade Moll
Frequent Advisor

Re: Trying To Determine Which LAN is in use

It was on lan2

root@visccov1:/root>ifconfig lan2
lan2: flags=1843
inet 138.35.86.151 netmask ffffffc0 broadcast 138.35.86.191
root@visccov1:/root>netstat -rnv
Routing tables
Dest/Netmask Gateway Flags Refs Interface Pmtu
127.0.0.1/255.255.255.255 127.0.0.1 UH 0 lo0 4136
138.35.86.151/255.255.255.255 138.35.86.151 UH 0 lan2 4136
138.35.86.128/255.255.255.192 138.35.86.151 U 2 lan2 1500
127.0.0.0/255.0.0.0 127.0.0.1 U 0 lo0 4136
default/0.0.0.0 138.35.86.129 UG 0 lan2 1500
root@visccov1:/root>ping 138.35.86.129
PING 138.35.86.129: 64 byte packets
64 bytes from 138.35.86.129: icmp_seq=0. time=0. ms
64 bytes from 138.35.86.129: icmp_seq=1. time=0. ms
64 bytes from 138.35.86.129: icmp_seq=2. time=0. ms

----138.35.86.129 PING Statistics----
3 packets transmitted, 3 packets received, 0% packet loss
round-trip (ms) min/avg/max = 0/0/0
root@visccov1:/root>


Thank you everyone for your assistance and help !!