dtc 16rx mGR SOFTWARE QUESTION

[mike worrell]

I am running product J2496B DTC16RX MGR
software on a 10.2 HPUX box that is about to crash. The J2496B product is version A143C000.

Can someone tell me the easiest way to move this over to a hpux server running 11.0.
Here is what I have so far:

Have an old HPUX 10.2 app cd, I can see the product on the CD but when I go to swinstall it doesn't show. Can't find the cust id and password anywhere for the cd's

I have a hp-ux 11.0 app cd in which I do see J2496b on it but it is version A143J000. Used Swinstall to try and install and it says it's missing some pieces of the bundle
Internet SRVCS.INETSVCS-Boot.. Any idea what product I need to load to get that.

What is my easiest route to get this installed?

Thanks,
MIke

[TTr · Accepted solution]

The InternetSrvcs.INETSVCS-BOOT is a default fileset on any server unless you totally did not install any networking on your server.
Is it possible this was not really an error but a warning early in the software selection? And was there a message saying somethin like this dependancy would be checked further during the analysis phase?
Run "swinstall -l fileset" and look in the listing to see if you have the INETSVCS-BOOT fileset.
Post the exact swinstall error.

[mike worrell]

Here is the info showing in swinstall.
(Also i did the swlist -l fileset and that item is there.)
The software item "J2496B,r=A143J000,a=HP-UX_B.11.00_32/64,v=HP" is a
Ta bundle (or a product, subproduct or fileset contained within a
bundle). This item was successfully marked, but difficulties were
On encountered while marking some items that it depends on. The messages
-- below show which software items encountered difficulties and exactly ---
To what these difficulties were: ted
-- The software "RDTCMGR,r=A143J000,a=HP-UX_B.11.00_32/64,v=HP" was ---
successfully marked, but it depends on the following software items
/- which could not be found in the source. However, these items may -\
| already be in the target. This will be checked during the Analysis ^
| Phase: |
| InternetSrvcs.INETSVCS-BOOT,r>=B.11.00.%,a=HP-UX_B.11.00_32/64,v=HP
| InternetSrvcs.INETSVCS-BOOT,r>=B.11.00.%,a=HP-UX_B.11.00_32/64,v=HP
| InternetSrvcs.INETSVCS-BOOT,r>=B.11.00.%,a=HP-UX_B.11.00_32/64,v=HP
| TextFormatters.TEXT-FMT,r>=B.11.00.%,a=HP-UX_B.11.00_32/64,v=HP
| InternetSrvcs.INETSVCS-BOOT,r>=B.11.00.%,a=HP-UX_B.11.00_32/64,v=HP |
| InternetSrvcs.INETSVCS-BOOT,r>=B.11.00.%,a=HP-UX_B.11.00_32/64,v=HP


Reason I thought this was a problem is I loaded earlier. Set up the configuration like on old box. Had Network folks go into dtc and change server location from the one that is about to croak to this new server. He powercycled dtc and it wouldn't get configuration.. led on back went from 0 to 2 which is a failure. He logged back into dtc and put in the old server name, rebooted dtc and it worked fine according to the led on the back.

Any ideas?

[TTr]

Note this text in the log. This is what I was referring to

> successfully marked, but it depends on the following software items which could not be found in the source. However, these items may already be in the target. This will be checked during the Analysis Phase:

This is not an error, it is a warning of a possible dependancy and it is telling you that that this dependancy will be checked later on during the analysis phase. Continue the installation in swinstall and watch the analysis and install log for any errors. These are the errors if any that really count. If you don't get any errors in the analysis and install phases the software should be ok.
Based on what I read in here

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&objectID=c01526037&jumpid=reg_R1002_USEN

this looks like a tftp boot setup and additional configuration needs to be done in tftp and config files need to be copied from the old server so that the device can boot from the new server.

[TTr]

When your network folks changed the "server location" in the dtc box, it tried to connect to your new server using tftp connection. Was tftp enabled on the new server?
After the tftp connection, the dtc box tries to download its boot configuration. This is what you need to copy from the old server. Check out the URL I mentioned above

[mike worrell]

Yes tftp is enabled in /etc/inetd.conf and /etc/ passwd. They are identical.

Regarding the document in the url, i haven't copied anything from live box to the new box. Only have 2 dtc's so I set up manually just like on the live box. The live box now is hpux 10.2 using dtc 16 rx version A143C000. Box I'm trying to get this up and running on is hp ux 11.0 using dtc 16 rx version A143J000.

Any thing else I can try that you can think of. You would think this would be a cut and dry task. When I configured everything on the current live box about 8 years ago it was simple as could be and worked first time.

[TTr]

> i haven't copied anything from live box to the new box

The DTC box setup is a two-part process. Part 1 is the dtc software installation that you have done already on the 11.0 server and tha's good.
Part 2 to to setup the configuration files that are specific for your DTC box and your local environment. These files are NOT part of the software installation. Look in /home/tftpdir/rdtcmgr and /var/opt/rdtcmgr/mapip of the live (10.20) and new (11.00) servers and compare the two. These are the files that you need to copy over. Read steps 3 and 5 of the URL. Step #6 is the step that your network folks perform when the switch over the DTC to boot from the new 11.00 server. In this step, bootp is not mentioned and it does not appear that it is required by the dtc box. But check the old server to see if bootp is enabled and if there is a /etc/bootptab file with dtc related entries in it.

Also check the syslog for any tftp errors ot tftp connection activity from the dtc box.

[mike worrell]

the old server has bootp uncommented in inetd file and was commented out on new, so i uncommented and restarted inetd.. no entries for dtc in old bootptab

[mike worrell]

setting bootp service to work got us going...thanks for sticking with me on this.

[TTr]

Hmm, If there are no /etc/bootptab entries maybe bootp is not really needed. Or is it using /etc/dhcptab instead? Maybe restarting inetd is what did it and by restarting inetd you activated tftp?

Are there any bootp entries in the syslog related to the dtc box? Any tftp entries?

[mike worrell]

We had rebooted the new server a few times thurs and friday and that would have restarted the inetd and it still didn't work. The bootptab entries on that old server were from stuff years ago that is no longer here. Looks like that enabling of bootps in inetd got us going. That is the only change I made today. I'm glad we got it working. Now we can configure the 2 live dtc's on this new box and be in good shape. Thanks for all your help.