topic Cannot boot from the Ignite server while on an isolated vlan. in Operating System - HP-UX

Cannot boot from the Ignite server while on an isolated vlan.

Horia Barbul_2 — Thu, 09 Sep 2010 08:18:21 GMT

Greetings.

Please give me some suggestions about what goes wrong with the following setup.
I installed an Ignite server ( named IgniteDR ) and made Golden Images ( make_sys_image )
of vg00 from two production servers ( iasdb1 and iasdb2 both rx7640). Now I intend to test
the images by building two test systems ( generically named iasdb1drc and iasdb2drc - BL870c).
For that I isolated in a separate VLAN the Ignite server and the two BL870c servers.
IgniteDR takes a long time to boot - it cannot communicate with other servers towards who some
directories were NFS exported and there are no NDS servers available.
On ignitedr /etc/inetd.conf contains the line
bootps dgram udp wait root /usr/lbin/bootpd bootpd -d 3
and inetd -l was used in order to start logging.
/etc/bootptab contains the following stanza:
IADEF:\
ht=ethernet:\
hn:\
bf=/opt/ignite/boot/nbp.efi:\
bs=48:\
bp=172.16.1.69:\
sm=255.255.255.0:\
gw=172.16.1.1:\
ds=172.16.1.18
testsrvdrc:tc=IADEF:ip=172.16.1.65:ha=001E0B5C05EC
alfa01:tc=IADEF:ip=172.16.1.70:ha=0017A477006C
iasdb1drc:tc=IADEF:ip=172.16.1.66:ha=002264027A4C
iasdb2drc:tc=IADEF:ip=172.16.1.67:ha=002264029A80
The first issue is that bootpd does not start "by itself" and needs to be started manually:
-----------------------------------------------------------------------
# /usr/sbin/bootpquery 002264029A80 -s ignitedr -f
bootpquery: Bootp servers not responding!
# ps -e | grep bootpd
# /usr/lbin/bootpd -P -a
rm: /tmp/dhcpfifo.root non-existent
rm: /tmp/dhcpfifo.any non-existent
# ps -e | grep bootpd
29878 ? 0:00 bootpd
-------------------------------------------------------------------------
After bootpd is started bootpquery works fine on IgniteDR
-------------------------------------------------------------------------
# /usr/sbin/bootpquery 002264029A80 -s ignitedr -f
Received BOOTREPLY from IgniteDR (172.16.1.69)
Hardware Address: 00:22:64:02:9a:80
Hardware Type: ethernet
IP Address: 172.16.1.67
Boot file: /opt/ignite/boot/nbp.efi
RFC 1048 Vendor Information:
Subnet Mask: 255.255.255.0
Gateway: 172.16.1.1
Boofile Size: 24576 512 byte blocks
Domain Name Server: 172.16.1.18
Host Name: iasdb2drc
# tail -10 /var/adm/syslog/syslog.log
Sep 9 10:34:29 IgniteDR bootpd[29878]: group count: 0
Sep 9 10:34:29 IgniteDR bootpd[29878]: reading "/etc/bootptab"
Sep 9 10:34:29 IgniteDR bootpd[29878]: read 8 entries from "/etc/bootptab"
Sep 9 10:34:29 IgniteDR bootpd[29878]: reading "/etc/dhcpdeny"
Sep 9 10:34:29 IgniteDR bootpd[29878]: error opening "/etc/dhcpdeny": No such file or directory
Sep 9 10:34:29 IgniteDR bootpd[29878]: rif collection for token ring turned on
Sep 9 10:34:29 IgniteDR bootpd[29878]: found 172.16.1.67 iasdb2drc
Sep 9 10:34:29 IgniteDR bootpd[29878]: sending RFC1048-style reply
Sep 9 10:34:29 IgniteDR bootpd[29878]: sending reply on 172.16.1.67
Sep 9 10:34:29 IgniteDR bootpd[29878]: sending reply on 255.255.255.255
However, If I try to boot from "iasdb1drc" it fails with absolutely no entry
in /var/adm/syslog/syslog.log:
Shell> dbprofile
Profile List
Profile Name: iasdb2drc
Network Type: IPv4
Client IP address: 172.16.1.67
Gateway IP address: 172.16.1.1
Subnet Mask: 255.255.255.0
Server IP address: 172.16.1.69
Boot File: /opt/ignite/boot/nbp.efi
Optional Data:
Shell> lanboot select -dn iasdb2drc
01 Acpi(HWP0002,PNP0A03,100)/Pci(1|0)/Mac(002264029A80)
02 Acpi(HWP0002,PNP0A03,100)/Pci(1|1)/Mac(002264029A81)
03 Acpi(HWP0002,PNP0A03,200)/Pci(2|0)/Mac(002264029A82)
04 Acpi(HWP0002,PNP0A03,200)/Pci(2|1)/Mac(002264029A83)
Select Desired LAN: 1
Selected Acpi(HWP0002,PNP0A03,100)/Pci(1|0)/Mac(002264029A80)

Client MAC Address: 00 22 64 02 9A 80
Client IP Address: 172.16.1.67
Subnet Mask: 255.255.255.0
BOOTP Server IP Address: 172.16.1.69
DHCP Server IP Address: 0.0.0.0
Boot file name: /opt/ignite/boot/nbp.efi
Retrieving File Size
PXE-E18: Timeout. Server did not respond.
Exit status code: Invalid Parameter
Periodically the following two entries appear in syslog.log:
Sep 9 10:58:29 IgniteDR inetd[230]: registrar/tcp: Connection
from localhost (127.0.0.1) at Thu Sep 9 10:58:29 2010
Sep 9 11:02:29 IgniteDR inetd[267]: registrar/tcp: Connection
from IgniteDR (172.16.1.69) at Thu Sep 9 11:02:29 2010
I suspected a name resolution issue so the /etc/hosts file on IgniteDR contains:
172.16.1.69 IgniteDR ignitedr ignitedr.cne.ro
172.16.1.66 iasdb1drc iasdbidrc.xxx.yy
172.16.1.67 iasdb2drc iasdb2drc.xxx.yy
172.16.1.nnn iasdb1 iasdb1.xxx.yy
172.16.1.mmm iasdb2 iasdb2.xxx.yy
127.0.0.1 localhost loopback
And /etc/nsswitch.conf contains
passwd: compat
group: compat
hosts: files [NOTFOUND=continue] dns [NOTFOUND=return] nis
ipnodes: dns [NOTFOUND=return] files
networks: nis [NOTFOUND=return] files
protocols: nis [NOTFOUND=return] files
rpc: nis [NOTFOUND=return] files
publickey: nis [NOTFOUND=return] files
netgroup: nis [NOTFOUND=return] files
automount: files nis
aliases: files nis
services: nis [NOTFOUND=return] files
I intend to install HP-UX on one of the two BL870c to see if it can ping IgniteDR
but I am having issues with mounting the virtual media...

Any advice would be appreciated.
Thank you

Re: Cannot boot from the Ignite server while on an isolated vlan.

likid0 — Thu, 09 Sep 2010 10:09:58 GMT

You should also have in /etc/inetd.conf , tftp active:

tftp dgram udp wait root /usr/lbin/tftpd tftpd\
/opt/ignite\
/var/opt/ignite

you can check network conectivity, the other way round, when you execute the lanboot from the client:

lanboot select -dn iasdb2drc

you can try with a linkloop from the ignite server, and check conectivity

Re: Cannot boot from the Ignite server while on an isolated vlan.

Horia Barbul_2 — Thu, 09 Sep 2010 11:14:39 GMT

Daniel, thanks for your answer

tftp is active:
---------------------------------------------------------------------------------------
# have one, please consult the tftpd(1M) manual entry for
# information about setting up this service.
tftp dgram udp wait root /usr/lbin/tftpd tftpd\
/opt/ignite\
/var/opt/ignite
bootps dgram udp wait root /usr/lbin/bootpd bootpd -d 3
#finger stream tcp nowait bin /usr/lbin/fingerd fingerd
login stream tcp6 nowait root /usr/lbin/rlogind rlogind
shell stream tcp6 nowait root /usr/lbin/remshd remshd
exec stream tcp6 nowait root /usr/lbin/rexecd rexecd
#uucp stream tcp nowait root /usr/sbin/uucpd uucpd
ntalk dgram udp wait root /usr/lbin/ntalkd ntalkd
auth stream tcp6 wait bin /usr/lbin/identd identd

And:

# cat /etc/services | grep tftp
tftp 69/udp # Trivial File Transfer Protocol
# cat /etc/services | grep boot
bootps 67/udp # Bootstrap Protocol Server
bootpc 68/udp # Bootstrap Protocol Client
instl_boots 1067/udp # installation bootstrap protocol server
instl_bootc 1068/udp # installation bootstrap protocol client
------------------------------------------------------------------------

However it seems that my VLAN is faulty:

linkloop issued on own MAC on IgniteDR fails on all 4 MACs:
# linkloop -i 0 0x2264369034
Link connectivity to LAN station: 0x2264369034
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

And lanadmin shows for all PPAs - 0, 1, 2 and 3:
PPA Number = 0
Description = lan0 HP PCI-X 1000Mbps Release B.11.23.0712.01
Type (value) = ethernet-csmacd(6)
MTU Size = 1500
Speed = 1000000000
Station Address = 0x2264369034
Administration Status (value) = up(1)
Operation Status (value) = down(2)

I probably must approach the netadmin ...

Re: Cannot boot from the Ignite server while on an isolated vlan.

likid0 — Thu, 09 Sep 2010 14:28:21 GMT

Yes, looks like you have a network problem, you should at least have one working nic

Re: Cannot boot from the Ignite server while on an isolated vlan.

Horia Barbul_2 — Wed, 15 Sep 2010 10:05:12 GMT

If anyone is interested: the issue was actually that the Catalyst 3020 switches were not "seeing" the LOMs of the BL860c as connected to the respective ports , hence the ports were kept down on the switch.

The "solution" was to reseat the BL860 IgniteDR server. After the shutown / power-off / take out / reinsert /power-on/boot the booting of the BL870c servers from the Ignite server worked.

Thank you