- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Itanium bootp/tftp boot error
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-23-2009 06:51 AM
тАО01-23-2009 06:51 AM
Itanium bootp/tftp boot error
Please select a boot option
Boot from Bootp
Use ^ and v to change option(s). Use Enter to select an option
Loading.: Bootp
Running LoadFile()
CLIENT MAC ADDR: 00 30 6E 38 19 68
CLIENT IP: 192.168.1.72 MASK: 255.255.255.0 DHCP IP: 0.240.0.0
Running LoadFile()
Starting: Bootp
7 0 0x00006B 0x000000000000000B unexpected trap
7 0 0x000066 0x000000000000000B trap taken, number in ext PE
7 0 0x00003C 0x0000000000002C00 trap taken, offset in ext PE
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-23-2009 07:35 AM
тАО01-23-2009 07:35 AM
Re: Itanium bootp/tftp boot error
logical name or two, say,
"TCPIP$TFTP_TRACE" = "1"
and, perhaps:
"TCPIP$TFTP_EXTLOG" = "1"
then you might learn something from
SYS$SYSDEVICE:[TCPIP$TFTP]TCPIP$TFTP_RUN.LOG
(or somewhere).
> [...] the correct files [...]
Which are? UNIX-compatible format (Stream_LF
or fixed-512)?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-23-2009 08:10 AM
тАО01-23-2009 08:10 AM
Re: Itanium bootp/tftp boot error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-23-2009 08:54 AM
тАО01-23-2009 08:54 AM
Re: Itanium bootp/tftp boot error
The DHCP IP of 0.240.0.0 looks completely bogus. That's potentially a busted DHCP client, or a busted EFI display. There's an IANA reserved range for DHCP client IP activity, 169.254.0.0/16. While not all DHCP clients play well (do any?), I'd not expect to get to get 0.240.0.0 either from a local DHCP server, or as an address if I wasn't able to get an address from the DHCP server.
If the traps are a result of no DHCP client address and if these traps comprise the sole error message(s) for no DHCP address, then the EFI firmware is busted.
If you're not using DHCP and have a static IP enabled (which the 192.168.1.72 address listed could imply), then I'd a: move out of the 192.168.0.0/16 subnet for the sake of the VPNs, and would ignore the above DHCP details. I'd b: ensure there is connectivity within the subnet, as vLANs and LAN-level configurations can potentially derail communications among "new" host addresses. And I'd poke around in the logs.
Do also ensure the EFI firmware is reasonably current. The older firmware for the rx2600 series did have its share of issues and limits. If this is one of the recent crop of US$200 boxes, those definitely had seriously down-revision EFI firmware.
If you're in a hurry, I'd tend to use the EFI path, or a local DVD. If you have access to shared SCSI storage between these two boxes, you can transfer the kit over that way.
If your firmware is down-revision, I'd use the DVD or the EFI-level ftp stuff to transfer over the firmware images and then fix that issue first, and then move along to an InfoServer installation of OpenVMS I64 and such or the SCSI-based transfer of the bits over; the stuff up above.
And even though HP says you can operate without one, it's just a whole lot easier to have a DVD in these boxes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-23-2009 09:11 AM
тАО01-23-2009 09:11 AM
Re: Itanium bootp/tftp boot error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-23-2009 10:33 PM
тАО01-23-2009 10:33 PM
Re: Itanium bootp/tftp boot error
$ set nover
$ on sever then cont
$ @sys$STARTUP:ESS$LAD_STARTUP.COM
$ set ver
$ delete TCPIP$TFTP_ROOT:[V831H1]*.*;*
$ delete TCPIP$TFTP_ROOT:[000000]V831H1.dir;*
$
$ creat/dir TCPIP$TFTP_ROOT:[V831H1]
$
$ dismount dka500:/nounload
$ mount/system dka500: I640831H1
$ COPY dka500:[SYS0.SYSCOMMON.SYSEXE]VMS_LOADER.EFI -
TCPIP$TFTP_ROOT:[V831H1]VMS_LOADER.EFI
$ COPY Dka500:[SYS0.SYSCOMMON.SYSEXE]IPB.EXE -
TCPIP$TFTP_ROOT:[V831H1]IPB.EXE
$
$ infoserver:==$ess$infoserver
$ INFOSERVER delete SERVICE I640831H1
$ INFOSERVER CREATE SERVICE I640831H1 Dka500:
$
$ TCPIP SET noHOST node12
$ TCPIP SET noHOST node12a
$ TCPIP SET nobootp node12
$ TCPIP SET nobootp node12a
$
$ TCPIP SET HOST node12/ADDRESS=192.168.1.69
$ TCPIP SET HOST node12a/ADDRESS=192.168.1.70
$
$ TCPIP SET BOOTP node12 /HARDWARE=ADDRESS=00-30-6e-38-19-68 -
/FILE=[V831H1]VMS_LOADER.EFI
$ TCPIP SET BOOTP node12a /HARDWARE=ADDRESS=00-30-6e-38-99-42 -
/FILE=[V831H1]VMS_LOADER.EFI
$
How bad is that(edited)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-23-2009 11:05 PM
тАО01-23-2009 11:05 PM
Re: Itanium bootp/tftp boot error
> problems. [...]
Well?
Aside from the actual TFTP log file, I
noticed this when I used a loose TFTP client
to fetch a file:
%%%%%%%%%%% OPCOM 23-JAN-2009 09:24:57.00 %%%%%%%%%%%
Message from user INTERnet on ALP
INTERnet ACP TFTP Accept Request from Host: 10.0.0.9 Port: 51283
I haven't tried actually booting anything
this way, however.
> I must be stupid still.
Could be. Not enough evidence yet.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-08-2009 04:48 PM
тАО02-08-2009 04:48 PM
Re: Itanium bootp/tftp boot error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-08-2009 04:53 PM
тАО02-08-2009 04:53 PM