Host-Based InfoServer error

I am trying to setup the Host-Based InfoServer on my AlphaServer ES40 running OpenVMS V8.3 (Fully patched as of 01-OCT-2000) so that I can network boot an RX2600 using the recently released OpenVMS 8.4FT DVD ISO image file.. The LAD and LAST startup on the ES40 proceed without incident as does the LD connect and mount commands. The problem arises when I attempt to use the Infoserver control program to make the DVD ROM ISO image available via the LD device to which the ISO image file is connected. Here is the output from the terminal session in which I attempted to configure the InfoServer Service: $ show device LA Device Device Error Name Status Count LAST0: Online 0 LAD0: Online 0 $ LD CONNECT DISK_USERS:[usr.robertson.OpenVMS84FT]I64E84.ISO LDA100: $ MOUNT/SYSTEM/NOWRITE LDA100: I64084 %MOUNT-I-MOUNTED, I64084 mounted on _SRVR1$LDA100: $ dir LDA100:[000000] Directory LDA100:[000000] 000000.DIR;1 AVAIL_MAN_BASE.DIR;1 BACKUP.SYS; 1 BADBLK.SYS;1 BADLOG.SYS;1 BITMAP.SYS;1 CLEAN_SDA_HELP.COM;1 CONTIN.SYS;1 CORIMG.SYS;1 DECNET_PHASE_IV_I64084.DIR;1 DWMOTIF_SUPPORT_I64084.DIR;1 GPT.SYS;1 INDEXF.SYS; 1 KITS.DIR;1 SECURITY.SYS;1 SYS0.DIR;1 SYS1.DIR;1 SYS10.DIR;1 SYS11.DIR;1 SYS12.DIR;1 SYS13.DIR; 1 SYS14.DIR;1 SYS15.DIR;1 SYS16.DIR;1 SYS17.DIR; 1 SYS18.DIR;1 SYS19.DIR;1 SYS1A.DIR;1 SYS1B.DIR; 1 SYS1C.DIR;1 SYS1D.DIR;1 SYS1E.DIR;1 SYS1F.DIR; 1 SYS2.DIR;1 SYS20.DIR;1 SYS21.DIR;1 SYS22.DIR; 1 SYS23.DIR;1 SYS24.DIR;1 SYS25.DIR;1 SYS26.DIR; 1 SYS27.DIR;1 SYS28.DIR;1 SYS29.DIR;1 SYS2A.DIR; 1 SYS2B.DIR;1 SYS2C.DIR;1 SYS2D.DIR;1 SYS2E.DIR; 1 SYS2F.DIR;1 SYS3.DIR;1 SYS30.DIR;1 SYS31.DIR; 1 SYS32.DIR;1 SYS33.DIR;1 SYS34.DIR;1 SYS35.DIR; 1 SYS36.DIR;1 SYS37.DIR;1 SYS38.DIR;1 SYS39.DIR; 1 SYS3A.DIR;1 SYS3B.DIR;1 SYS3C.DIR;1 SYS3D.DIR; 1 SYS3E.DIR;1 SYS3F.DIR;1 SYS4.DIR;1 SYS40.DIR; 1 SYS41.DIR;1 SYS42.DIR;1 SYS43.DIR;1 SYS44.DIR; 1 SYS45.DIR;1 SYS46.DIR;1 SYS47.DIR;1 SYS48.DIR; 1 SYS49.DIR;1 SYS4A.DIR;1 SYS4B.DIR;1 SYS4C.DIR; 1 SYS4D.DIR;1 SYS4E.DIR;1 SYS4F.DIR;1 SYS5.DIR;1 SYS50.DIR;1 SYS51.DIR;1 SYS52.DIR;1 SYS53.DIR; 1 SYS54.DIR;1 SYS55.DIR;1 SYS56.DIR;1 SYS57.DIR; 1 SYS58.DIR;1 SYS59.DIR;1 SYS5A.DIR;1 SYS5B.DIR; 1 SYS5C.DIR;1 SYS5D.DIR;1 SYS5E.DIR;1 SYS5F.DIR; 1 SYS6.DIR;1 SYS60.DIR;1 SYS61.DIR;1 SYS62.DIR; 1 SYS63.DIR;1 SYS64.DIR;1 SYS65.DIR;1 SYS66.DIR; 1 SYS67.DIR;1 SYS68.DIR;1 SYS69.DIR;1 SYS6A.DIR; 1 SYS6B.DIR;1 SYS6C.DIR;1 SYS6D.DIR;1 SYS6E.DIR; 1 SYS6F.DIR;1 SYS7.DIR;1 SYS70.DIR;1 SYS71.DIR; 1 SYS72.DIR;1 SYS73.DIR;1 SYS74.DIR;1 SYS75.DIR; 1 SYS76.DIR;1 SYS77.DIR;1 SYS78.DIR;1 SYS79.DIR; 1 SYS7A.DIR;1 SYS7B.DIR;1 SYS7C.DIR;1 SYS7D.DIR; 1 SYS7E.DIR;1 SYS7F.DIR;1 SYS8.DIR;1 SYS80.DIR; 1 SYS81.DIR;1 SYS82.DIR;1 SYS83.DIR;1 SYS84.DIR; 1 SYS85.DIR;1 SYS86.DIR;1 SYS87.DIR;1 SYS88.DIR; 1 SYS89.DIR;1 SYS8A.DIR;1 SYS8B.DIR;1 SYS8C.DIR; 1 SYS8D.DIR;1 SYS8E.DIR;1 SYS8F.DIR;1 SYS9.DIR;1 SYS90.DIR;1 SYS91.DIR;1 SYS92.DIR;1 SYS93.DIR; 1 SYS94.DIR;1 SYS95.DIR;1 SYS96.DIR;1 SYS97.DIR; 1 SYS98.DIR;1 SYS99.DIR;1 SYS9A.DIR;1 SYS9B.DIR; 1 SYS9C.DIR;1 SYS9D.DIR;1 SYS9E.DIR;1 SYS9F.DIR; 1 SYSA.DIR;1 SYSA0.DIR;1 SYSA1.DIR;1 SYSA2.DIR; 1 SYSA3.DIR;1 SYSA4.DIR;1 SYSA5.DIR;1 SYSA6.DIR; 1 SYSA7.DIR;1 SYSA8.DIR;1 SYSA9.DIR;1 SYSAA.DIR; 1 SYSAB.DIR;1 SYSAC.DIR;1 SYSAD.DIR;1 SYSAE.DIR; 1 SYSAF.DIR;1 SYSB.DIR;1 SYSB0.DIR;1 SYSB1.DIR; 1 SYSB2.DIR;1 SYSB3.DIR;1 SYSB4.DIR;1 SYSB5.DIR; 1 SYSB6.DIR;1 SYSB7.DIR;1 SYSB8.DIR;1 SYSB9.DIR; 1 SYSBA.DIR;1 SYSBB.DIR;1 SYSBC.DIR;1 SYSBD.DIR; 1 SYSBE.DIR;1 SYSBF.DIR;1 SYSC.DIR;1 SYSC0.DIR; 1 SYSC1.DIR;1 SYSC2.DIR;1 SYSC3.DIR;1 SYSC4.DIR; 1 SYSC5.DIR;1 SYSC6.DIR;1 SYSC7.DIR;1 SYSC8.DIR; 1 SYSC9.DIR;1 SYSCA.DIR;1 SYSCB.DIR;1 SYSCC.DIR; 1 SYSCD.DIR;1 SYSCE.DIR;1 SYSCF.DIR;1 SYSD0.DIR; 1 SYSD1.DIR;1 SYSD2.DIR;1 SYSD3.DIR;1 SYSD4.DIR; 1 SYSD5.DIR;1 SYSD6.DIR;1 SYSD7.DIR;1 SYSD8.DIR; 1 SYSD9.DIR;1 SYSDA.DIR;1 SYSDB.DIR;1 SYSDC.DIR; 1 SYSDD.DIR;1 SYSDE.DIR;1 SYSDF.DIR;1 SYSE.DIR;1 SYSE0.DIR;1 SYSE1.DIR;1 SYSE2.DIR;1 SYSE3.DIR; 1 SYSE4.DIR;1 SYSE5.DIR;1 SYSE6.DIR;1 SYSE7.DIR; 1 SYSE8.DIR;1 SYSE9.DIR;1 SYSEA.DIR;1 SYSEB.DIR; 1 SYSEC.DIR;1 SYSED.DIR;1 SYSEE.DIR;1 SYSEF.DIR; 1 SYSF.DIR;1 SYSF0.DIR;1 SYSF1.DIR;1 SYSF2.DIR; 1 SYSF3.DIR;1 SYSF4.DIR;1 SYSF5.DIR;1 SYSF6.DIR; 1 SYSF7.DIR;1 SYSF8.DIR;1 SYSF9.DIR;1 SYSFA.DIR; 1 SYSFB.DIR;1 SYSFC.DIR;1 SYSFD.DIR;1 SYSFE.DIR; 1 SYSFF.DIR;1 VMS$COMMON.DIR;1 VOLSET.SYS;1 Total of 272 files. $ RUN SYS$SYSTEM:ESS$INFOSERVER InfoServer> CREATE SERVICE I64084 LDA100: %SYSTEM-F-DEVINACT, device inactive I am not sure how to interpret this error message. The LDA100: device is apparently active because it responds as expected to a directory command. Which leaves me wondering which device it is trying to use that it believes is inactive. Unfortunately, it is not nice enough to display the device name of the supposedly inactive device along with the error message. Has anybody else experienced this problem or a similar one? Any wisdom is greatly appreciated. Just in case it matters, here are the contents of the SYS$STARTUP:ESS$LAD_STARTUP.DAT and SYS$STARTUP:ESS$LAST_STARTUP.DAT files: SYS$STARTUP:ESS$LAD_STARTUP.DAT: !++ ! ESS$LAD_STARTUP.DAT ! ! Copy this file to SYS$STARTUP:ESS$LAD_STARTUP.DAT and edit it ! to suit your local situation. ! ! This file is used by SYS$STARTUP:ESS$LAD_STARTUP.COM to set up ! the parameters for the InfoServer Application on OpenVMS ! LASTport/Disk (LAD) server. ! ! Note: ! The LAD disk block cache is structured as a number of fixed-size ! buckets. You must specify both the bucket size and the number of ! buckets for the cache. ! ! The LAD cache is allocated from non-paged pool and is in no way ! associated with the XFC cache. The total LAD cache size in bytes ! may be determined by the formula: ! ! cache-bytes = bucket-size-in-blocks * number-of-buckets * 512 ! ! Be sure the SYSGEN parameters NPAGDYN/NPAGEVIR are sized appropriately. ! ! The following keywords with values are accepted by this procedure: ! ! BUFFER_SIZE - A number between 3 and 8 denoting the ! bucket size in blocks as follows: ! 3 - 8 blocks ! 4 - 16 blocks ! 5 - 32 blocks ! 6 - 64 blocks ! 7 - 128 blocks ! 8 - 256 blocks ! CACHE_BUCKETS - Number of buckets ! MAXIMUM_SERVICES - Maximum number of services (max=1024) ! WRITE_LIMIT - Server wide count of asynchronous writes !-- DEVICE = EIA BUFFER_SIZE = 3 ! default (8 block buckets) CACHE_BUCKETS = 512 ! Default setting WRITE_LIMIT = 0 ! No async writes MAXIMUM_SERVICES = 256 ! default (typically more than enough) SYS$STARTUP:ESS$LAST_STARTUP.DAT: !++ ! This file will be used to set the appropriate LASTCP qualifiers. The following ! LASTCP qualifiers: ALL_CONTROLLERS, CHECKSUM, TRANSMIT_QUOTA, or SLOW_MODE ! can be set by using the following statement format: ! LASTCP qualifier = 1 to enable e.g. SLOW_MODE = 1 enables SLOW_MODE ! LASTCP qualifier = 0 to disable e.g. SLOW_MODE = 0 disables SLOW_MODE ! The remaining LASTCP qualifiers will require the appropriate value settings. DEVICE = (EIA) ! TIMEOUT = n minimum interval in seconds ! CIRCUIT_MAXIMUM = n maximum number of nodes ! GROUP = n Group number ! NODE_NAME = name Node name ! CONTROLLERS = ([{controller letter,}...]) Controller list ! TRANSMIT_QUOTA = n Number of transmit buffers !-- ALL_CONTROLLERS = ON

On Tue, 1 Dec 2009 07:16:37 -0800 (PST), RobertsonEricW <robertsonericw@netzero.net> wrote: >$ LD CONNECT DISK_USERS:[usr.robertson.OpenVMS84FT]I64E84.ISO LDA100: >$ MOUNT/SYSTEM/NOWRITE LDA100: I64084 >%MOUNT-I-MOUNTED, I64084 mounted on _SRVR1$LDA100: >$ dir LDA100:[000000] > ...etc.. >Total of 272 files. >$ RUN SYS$SYSTEM:ESS$INFOSERVER >InfoServer> CREATE SERVICE I64084 LDA100: >%SYSTEM-F-DEVINACT, device inactive First guess: try a service name not equal to the disk label. (i think you're getting snake-bit by the disk logical created by $MOUNT)

I'd guess that the %SYSTEM-F-DEVINACT is referring to either the LAD0: or LAST0: template devices. Has the Infoserver server been started up properly? I've seen cases where it appears that the startup ran successfully but the server wasn't quite operational. Can you do a "SHOW SERVER" [from the Infoserver>" prompt] (I think that's the command). Does it show that the server is running okay? In my previous job I had a pretty sophisticated Infoserver server setup. I had implement wrappers around the various startup procedures (LD, ESS, LAD, etc.) that were involved in getting everything setup and running. fwiw, bw

On Dec 2, 1:12 am, JBloggs <JBlo...@acme.com> wrote: > On Tue, 1 Dec 2009 07:16:37 -0800 (PST), RobertsonEricW > > <robertsoner...@netzero.net> wrote: > >$ LD CONNECT DISK_USERS:[usr.robertson.OpenVMS84FT]I64E84.ISO LDA100: > >$ MOUNT/SYSTEM/NOWRITE LDA100: I64084 > >%MOUNT-I-MOUNTED, I64084 mounted on _SRVR1$LDA100: > >$ dir LDA100:[000000] > > ...etc.. > >Total of 272 files. > >$ RUN SYS$SYSTEM:ESS$INFOSERVER > >InfoServer> CREATE SERVICE I64084 LDA100: > >%SYSTEM-F-DEVINACT, device inactive > > First guess: try a service name not equal to the disk label. > > (i think you're getting snake-bit by the disk logical created by > $MOUNT) Thanks JBloggs. Unfortunately, choosing a different service name gives the same error message as before.

On Dec 2, 9:30 am, bw <bwan...@gmail.com> wrote: > I'd guess that the %SYSTEM-F-DEVINACT is referring to either the LAD0: > or LAST0: template devices. > > Has the Infoserver server been started up properly? I've seen cases > where it appears that the startup ran successfully but the server > wasn't quite operational. > > Can you do a "SHOW SERVER" [from the Infoserver>" prompt] (I think > that's the command). Does it show that the server is running okay? > > In my previous job I had a pretty sophisticated Infoserver server > setup. I had implement wrappers around the various startup procedures > (LD, ESS, LAD, etc.) that were involved in getting everything setup > and running. > > fwiw, > bw Thanks bw. I am not sure what to make of the show server output. But it does not seem write that cache buckets is reported as zero when SYS $STARTUP:ESS$LAD_STARTUP.DAT specifies that CACHE_BUCKETS = 512. Also the SHOW MEMORY/POOL seems to indicate plenty of available space in non-paged pool. I am just trying a very basic InfoServer setup at this point. This is the first and only configuration of an InfoServer service that has been attempted on this system. Is there any other configuration setup required for this most basic of setups for the InfoServer software? $ LD CONNECT DISK_USERS:[usr.robertson.OpenVMS84FT]I64E84.ISO LDA100: $ MOUNT/SYSTEM/NOWRITE LDA100: I64084 %MOUNT-I-MOUNTED, I64084 mounted on _SRVR1$LDA100: $ RUN SYS$SYSTEM:ESS$INFOSERVER InfoServer> show server Node SRVR1 [AlphaServer ES40] running OpenVMS V8.3 LASTport/Disk Server Version 1.2 Max Services: 256 Write Quota: 30 Cache Buckets: 0 Cache Bucket Size: 8 blocks Cache Size: 0 bytes Hits: 0 Hit Percentage: 0% Misses: 0 Current Sessions: 0 Peak Sessions: 0 Read Write Requests: 0 0 Blocks: 0 0 Errors: 0 0 Aborted: 0 0 Conflicts: 0 0 InfoServer> CREATE SERVICE VMS84FTIA64 LDA100: %SYSTEM-F-DEVINACT, device inactive $ show memory/pool System Memory Resources on 2-DEC-2009 22:39:47.35 Dynamic Memory Usage: Total Free In Use Largest Nonpaged Dynamic Memory (MB) 10.63 6.86 3.77 4.69 Paged Dynamic Memory (MB) 6.32 3.01 3.30 3.01 Lock Manager Dyn Memory (MB) 1.98 0.42 1.55

My first guess is that you specified the device as EIA in both SYS$STARTUP:ESS$LAST_STARTUP.DAT and SYS$STARTUP:ESS$LAD_STARTUP.DAT. I would either specify the full device name (EIA0 or EIA1 or whatever) or remove the device from both files. I took a look at the same files on my systems and none of them define a device. You might want to check to see if there are any errors in either SYS$STARTUP:ESS$LAST_STARTUP.LOG or SYS$STARTUP:ESS$LAD_STARTUP.LOG. =20 If those do not help then can you try creating a new container file and serving that? That would let you know if the problem is with InfoServer = or if there is something about your I64E84.ISO file. If you get the same = error with the new container then try serving a CDROM that will narrow it down = to either the InforServer setup or your LD setup.=20 The other thing I would try is using the command=20 CREATE SERVICE VMS84FTIA64 _SRVR1$LDA100: instead of CREATE SERVICE VMS84FTIA64 LDA100: but on my system I get a different error if I use LDA100: instead of the fully qualified name so I doubt this is your issue. Peter Weaver www.weaverconsulting.ca Winner of the OpenVMS.org Readers' Choice Award for System Management/Performance http://www.linkedin.com/in/peterweaver=A0=20

On Wed, 2 Dec 2009 19:25:05 -0800 (PST), RobertsonEricW <robertsonericw@netzero.net> wrote: >On Dec 2, 1:12 am, JBloggs <JBlo...@acme.com> wrote: >> On Tue, 1 Dec 2009 07:16:37 -0800 (PST), RobertsonEricW >> >> <robertsoner...@netzero.net> wrote: >> >$ LD CONNECT DISK_USERS:[usr.robertson.OpenVMS84FT]I64E84.ISO LDA100: >> >$ MOUNT/SYSTEM/NOWRITE LDA100: I64084 >> >%MOUNT-I-MOUNTED, I64084 mounted on _SRVR1$LDA100: >> >$ dir LDA100:[000000] >> > ...etc.. >> >Total of 272 files. >> >$ RUN SYS$SYSTEM:ESS$INFOSERVER >> >InfoServer> CREATE SERVICE I64084 LDA100: >> >%SYSTEM-F-DEVINACT, device inactive >> >> First guess: try a service name not equal to the disk label. >> >> (i think you're getting snake-bit by the disk logical created by >> $MOUNT) > >Thanks JBloggs. Unfortunately, choosing a different service name gives >the same error message as before. the service name issue, was something I got bit by long ago. here are notes (verbatim), I made the last time around I don't see that you're doing anything fundamentally different. (i adopted a cargo-cult belief inre the startup order of the various last/lad/infoserver startups. below, is what worked for me ...) Cloning the I64 8.3 dvd install disk: the *.bck from the *.bck-gz needs: $ set file/attrib=(rfm:fix,rat:none,lrl:32256,mrs:32256) $ ld connect/log DKA100:[000000]$$$I64SA.SYS LDA65: $ init/.../GPT LDA65: I64 $ set boot /blocksize=512 /I64 LDA65: $ mcr sys$setboot -s -f LDA65: $ back/image/noinit/... Similar for I64 sys$update:STABACKIT.com but note that WLKSYSDSK needs to be changed to 1 (write-locked) SYSGEN> USE LDA65:[SYSE.SYSEXE]IA64VMSSYS.PAR SYSGEN> SHOW WLKSYSDSK Parameter Name Current Default Min. Max. Unit Dynamic -------------- ------- ------- ------- ------- ---- ------- WLKSYSDSK 0 0 0 1 Boolean SYSGEN> SET WLKSYSDSK 1 SYSGEN> WRITE LDA65:[SYSE.SYSEXE]IA64VMSSYS.PAR 1. $ mount/system/noassist/foreign - .....LDA65: I64SA I64SA ! s/a needs write access 2. $ edit sys$startup:ess$last_startup.dat .......a. comment all_controllers = ON .......b. add DEVICE = (EIB) ! or EWA, etc 3. $ subm/noprint/user=SYSTEM/log=sys$manager- .....sys$startup:ess$last_startup.com 4. $ subm/noprint/user=SYSTEM/log=sys$manager- .....sys$startup:ess$lad_startup.com 5. $ subm/noprint/user=SYSTEM/log=sys$manager- ...../param=("DISK") sys$startup:ess$startup.com 6. $ mcr ess$infoserver create service IA64SA LDA65: 7. $ mcr ess$ladcp show service .....Interrogating network for Disk services, please wait... .....Disk services offered by node XX - .....(LAD V3.1, Address: 08-00-2B-86-86-3E) ..... Current Writes .....Service: Device: Rating: Connects: Allowed?: .....I64083 OpenVMS 65472 1 No and. then,. the network booting is another can of worms ... .... Please select a boot option OpenVMS 8.3, DKA0, flags: 0,0 OpenVMS 8.3, DKA100, flags: e,0 PKA0.1 EFI Shell [Built-in] NIC2 NIC1, 10/100 Boot Option Maintenance Menu System Configuration Menu Use ^ and v to change option(s). Use Enter to select an option Loading.: NIC1, 10/100 Running LoadFile() CLIENT MAC ADDR: 00 30 6E 39 E6 FE CLIENT IP: 10.0.0.2 MASK: 255.0.0.0 DHCP IP: 0.240.0.0 Running LoadFile() Starting: NIC1, 10/100 Loading file: TCPIP$TFTP_ROOT:[V83SA]IPB.EXE from IP 10. 0. 0. 1 %IPB-I-SUCCESS, HP OpenVMS IPB version V8.3 successfully loaded. %EIA-I-BOOTDRIVER, Starting auto-negotiation %EIA-I-BOOTDRIVER, Link partner not auto-negotiation capable, used parallel detection %EIA-I-BOOTDRIVER, Auto-negotiation selected 100BaseTX HDX Network Initial System Load Function Version 1.2 FUNCTION FUNCTION ID 1 - Display Menu 2 - Help 3 - Choose Service 4 - Select Options 5 - Stop Enter a function ID value: 3 OPTION OPTION ID 1 - Find Services 2 - Enter known Service Name Enter an Option ID value: 1 Working Servers found:: 1 Services offered by node XX, Address: 08-00-2B-86-86-3E # 1 IA64SA Enter a Service Number: 1 HP OpenVMS Industry Standard 64 Operating System, Version V8.3 � Copyright 1976-2007 Hewlett-Packard Development Company, L.P. %EIA-I-BOOTDRIVER, Starting auto-negotiation %EIA-I-BOOTDRIVER, Link partner not auto-negotiation capable, used parallel detection %EIA-I-BOOTDRIVER, Auto-negotiation selected 100BaseTX HDX %EIA0, Auto-negotiation mode assumed set by console %EIA0, Auto-negotiation started, advertising 100BaseTX Full Duplex, Flow Control %SMP-I-CPUTRN, CPU #01 has joined the active set. %EIA0, Link partner not auto-negotiation capable, using parallel detection %EIA0, Half Duplex 100BaseTX connection selected, TX flow control %SYSINIT-E- error reading TDF file, status = 00000910 %SYSINIT-I- run SYS$MANAGER:UTC$TIME_SETUP.COM to set time differential factor

On Dec 3, 9:48 am, "Peter Weaver" <info-...@weaverconsulting.ca> wrote: > My first guess is that you specified the device as EIA in both > SYS$STARTUP:ESS$LAST_STARTUP.DAT and SYS$STARTUP:ESS$LAD_STARTUP.DAT. I > would either specify the full device name (EIA0 or EIA1 or whatever) or > remove the device from both files. I took a look at the same files on my > systems and none of them define a device. > > You might want to check to see if there are any errors in either > SYS$STARTUP:ESS$LAST_STARTUP.LOG or SYS$STARTUP:ESS$LAD_STARTUP.LOG. > > If those do not help then can you try creating a new container file and > serving that? That would let you know if the problem is with InfoServer or > if there is something about your I64E84.ISO file. If you get the same error > with the new container then try serving a CDROM that will narrow it down to > either the InforServer setup or your LD setup. > > The other thing I would try is using the command > CREATE SERVICE VMS84FTIA64 _SRVR1$LDA100: > instead of > CREATE SERVICE VMS84FTIA64 LDA100: > but on my system I get a different error if I use LDA100: instead of the > fully qualified name so I doubt this is your issue. > > Peter Weaverwww.weaverconsulting.ca > Winner of the OpenVMS.org Readers' Choice Award for System > Management/Performancehttp://www.linkedin.com/in/peterweaver Thanks Peter Weaver. When I looked at the SYS$STARTUP:ESS $LAD_STARTUP.LOG file there was an error message regarding the DEVICE = EIA entry in the SYS$STARTUP:ESS$LAD_STARTUP.DAT file. After looking at the code in SYS$STARTUP:ESS$LAD_STARTUP.COM, it turns out that the DEVICE = EIA entry is not legal for the ESS$LAD_STARTUP.DAT file. So, I removed this entry from the SYS$STARTUP:ESS$LAD_STARTUP.DAT file. The DEVICE = (EIA) entry in the SYS$STARTUP:ESS$LAST_STARTUP.DAT file, however, is valid because the ALL_CONTROLLERS = ON line in the SYS $STARTUP:ESS$LAST_STARTUP.DAT is supposed to be commented out (there were issues reported with multiple Ethernet controllers being used for LAST services. Current documentation indicates that only one controller is supported) and the DEVICE = (EIA) configures the LAST services to use only the EIA Ethernet controller. I actually forgot to comment out the ALL_CONTROLLERS = ON entry originally. But, I have since corrected this omission. Now after restarting LAST and LAD the service creation command completes successfully. Thanks again, Eric

On Dec 3, 3:01 pm, JBloggs <JBlo...@acme.com> wrote: > On Wed, 2 Dec 2009 19:25:05 -0800 (PST), RobertsonEricW > > > > <robertsoner...@netzero.net> wrote: > >On Dec 2, 1:12 am, JBloggs <JBlo...@acme.com> wrote: > >> On Tue, 1 Dec 2009 07:16:37 -0800 (PST), RobertsonEricW > > >> <robertsoner...@netzero.net> wrote: > >> >$ LD CONNECT DISK_USERS:[usr.robertson.OpenVMS84FT]I64E84.ISO LDA100: > >> >$ MOUNT/SYSTEM/NOWRITE LDA100: I64084 > >> >%MOUNT-I-MOUNTED, I64084 mounted on _SRVR1$LDA100: > >> >$ dir LDA100:[000000] > >> > ...etc.. > >> >Total of 272 files. > >> >$ RUN SYS$SYSTEM:ESS$INFOSERVER > >> >InfoServer> CREATE SERVICE I64084 LDA100: > >> >%SYSTEM-F-DEVINACT, device inactive > > >> First guess: try a service name not equal to the disk label. > > >> (i think you're getting snake-bit by the disk logical created by > >> $MOUNT) > > >Thanks JBloggs. Unfortunately, choosing a different service name gives > >the same error message as before. > > the service name issue, was something I got bit by long ago. > > here are notes (verbatim), I made the last time around > I don't see that you're doing anything fundamentally different. > > (i adopted a cargo-cult belief inre the startup order of > the various last/lad/infoserver startups. below, is what > worked for me ...) > > Cloning the I64 8.3 dvd install disk: > > the *.bck from the *.bck-gz needs: > $ set file/attrib=3D(rfm:fix,rat:none,lrl:32256,mrs:32256) > > $ ld connect/log DKA100:[000000]$$$I64SA.SYS LDA65: > $ init/.../GPT LDA65: I64 > $ set boot /blocksize=3D512 /I64 LDA65: > $ mcr sys$setboot -s -f LDA65: > $ back/image/noinit/... > > Similar for I64 sys$update:STABACKIT.com > but note that WLKSYSDSK needs to be changed to 1 (write-locked) > > SYSGEN> USE LDA65:[SYSE.SYSEXE]IA64VMSSYS.PAR > SYSGEN> SHOW WLKSYSDSK > Parameter Name Current Default Min. Max. > Unit Dynamic > -------------- ------- ------- ------- ------- > ---- ------- > WLKSYSDSK 0 0 0 1 > Boolean > SYSGEN> SET WLKSYSDSK 1 > SYSGEN> WRITE LDA65:[SYSE.SYSEXE]IA64VMSSYS.PAR > > 1. $ mount/system/noassist/foreign - > ....LDA65: I64SA I64SA ! s/a needs write access > > 2. $ edit sys$startup:ess$last_startup.dat > ......a. comment all_controllers =3D ON > ......b. add DEVICE =3D (EIB) ! or EWA, etc > > 3. $ subm/noprint/user=3DSYSTEM/log=3Dsys$manager- > ....sys$startup:ess$last_startup.com > > 4. $ subm/noprint/user=3DSYSTEM/log=3Dsys$manager- > ....sys$startup:ess$lad_startup.com > > 5. $ subm/noprint/user=3DSYSTEM/log=3Dsys$manager- > ..../param=3D("DISK") sys$startup:ess$startup.com > > 6. $ mcr ess$infoserver create service IA64SA LDA65: > > 7. $ mcr ess$ladcp show service > ....Interrogating network for Disk services, please wait... > ....Disk services offered by node XX - > ....(LAD V3.1, Address: 08-00-2B-86-86-3E) > .... Current Writes > ....Service: Device: Rating: Connects: Allowed?: > ....I64083 OpenVMS 65472 1 No > > and. then,. the network booting is another can of worms ... > > ... > Please select a boot option > > OpenVMS 8.3, DKA0, flags: 0,0 > OpenVMS 8.3, DKA100, flags: e,0 PKA0.1 > EFI Shell [Built-in] > NIC2 > NIC1, 10/100 > Boot Option Maintenance Menu > System Configuration Menu > > Use ^ and v to change option(s). Use Enter to select an option > > Loading.: NIC1, 10/100 > Running LoadFile() > > CLIENT MAC ADDR: 00 30 6E 39 E6 FE > CLIENT IP: 10.0.0.2 MASK: 255.0.0.0 DHCP IP: 0.240.0.0 > Running LoadFile() > > Starting: NIC1, 10/100 > Loading file: TCPIP$TFTP_ROOT:[V83SA]IPB.EXE from IP 10. 0. 0. 1 > %IPB-I-SUCCESS, HP OpenVMS IPB version V8.3 successfully loaded. > %EIA-I-BOOTDRIVER, Starting auto-negotiation > %EIA-I-BOOTDRIVER, Link partner not auto-negotiation capable, used > parallel detection > %EIA-I-BOOTDRIVER, Auto-negotiation selected 100BaseTX HDX > > Network Initial System Load Function > Version 1.2 > > FUNCTION FUNCTION > ID > 1 - Display Menu > 2 - Help > 3 - Choose Service > 4 - Select Options > 5 - Stop > > Enter a function ID value: 3 > > OPTION OPTION > ID > 1 - Find Services > 2 - Enter known Service Name > > Enter an Option ID value: 1 > > Working > > Servers found:: 1 > > Services offered by node XX, Address: 08-00-2B-86-86-3E > # 1 IA64SA > > Enter a Service Number: 1 > > HP OpenVMS Industry Standard 64 Operating System, Version V8.3 > =A9 Copyright 1976-2007 Hewlett-Packard Development Company, L.P. > > %EIA-I-BOOTDRIVER, Starting auto-negotiation > %EIA-I-BOOTDRIVER, Link partner not auto-negotiation capable, used > parallel detection > %EIA-I-BOOTDRIVER, Auto-negotiation selected 100BaseTX HDX > > %EIA0, Auto-negotiation mode assumed set by console > %EIA0, Auto-negotiation started, advertising 100BaseTX Full Duplex, > Flow Control > %SMP-I-CPUTRN, CPU #01 has joined the active set. > %EIA0, Link partner not auto-negotiation capable, using parallel > detection > %EIA0, Half Duplex 100BaseTX connection selected, TX flow control > %SYSINIT-E- error reading TDF file, status =3D 00000910 > %SYSINIT-I- run SYS$MANAGER:UTC$TIME_SETUP.COM to set time > differential factor JBloggs, Thanks for all the information on setting up the network boot! I have no doubt this information will come in handy. Eric

On Thu, 3 Dec 2009 13:48:43 -0800 (PST), RobertsonEricW <robertsonericw@netzero.net> wrote: >Thanks for all the information on setting up the network boot! I have >no doubt this information will come in handy. > >Eric i did say the network booting was another can of worms; and the above just demonstrated/listed a itanium network boot but didn't offer much of a recipe/howto... the HPQ docs are pretty good, but googling didn't (iirc) pull up many examples. the following "notes" vis tftp/bootp, might help (or not), with the network boot (and others may chime in with better ways to do this ...) the ipb.exe, vms_loader.efi came from the i64 install disk and the tftp/boot server in the example below was a VMS alpha; and I had the infoserver running on the same server (iirc). I didn't capture very much (any) of how to add a network card boot to the Intanium's boot options (but iirc, it wasn't hard. either or my system had one already) TFTP/BOOTP: (enable both of these obviously) $ CREATE/DIRECTORY TCPIP$TFTP_ROOT:[V83] $ COPY LDA65:[VMS$COMMON.SYSEXE]IPB.EXE TCPIP$TFTP_ROOT:[V83SA] $ COPY LDA65:[VMS$COMMON.SYSEXE]VMS_LOADER.EFI TCPIP$TFTP_ROOT:[V83SA] $ DEFINE /SYSTEM TCPIP$TFTP_TRACE 1 $ DEFINE /SYSTEM TCPIP$TFTP_EXTLOG 1 $ DEFINE /SYSTEM TCPIP$BOOTP_TRACE 1 $ tcpip set host NODE1 /addr=10.0.0.2 $ tcpip set host NODE2 /addr=10.0.0.3 $ arp -s NODE1 00-30-6E-39-E6-FE $ arp -s NODE2 00-30-6E-39-66-DE $ tcpip set bootp NODE1 /HARDWARE=ADDRESS=00-30-6E-39-E6-FE /FILE=[V83SA]VMS_LOADER.EFI $ tcpip set bootp NODE2 /HARDWARE=ADDRESS=00-30-6E-39-66-DE /FILE=[V83SA]VMS_LOADER.EFI $ mcr ess$ladcp show service Interrogating network for Disk services, please wait... Disk services offered by node NODE1 (LAD V3.1, Address: 08-00-2B-86-86-3E) ......................Current Writes Service: Device: Rating: Connects: Allowed?: I64083 OpenVMS 65472 1 No TCPIP$TFTP_EXTLOG Enables logging of client read and write requests, as well as any error messages the server reports to the clients while processing those requests. By default, this logical name is set to 0, or OFF. TCPIP$TFTP_FASTCLOSE If set, the socket and file are closed immediately after the server receives the last block of a file, on client write operations. If the logical is set, the server's last acknowledgment message is lost and no retransmission is done. This may appear to the client to be a failure. By default, this logical is set to 0, or OFF. TCPIP$TFTP_ROOT Defines a concealed device that points to TFTP data storage. By default, the concealed device is SYS$SYSDEVICE:[TCPIP$TFTP_ROOT]. For more information, see Section 11.3. TCPIP$TFTP_TRACE Enables logging of detailed tracing information about server operation, including logging of blocks sent and received, as well as other useful trace information. By default, this logical name is set to 0, or OFF.

Similiar Articles:

V100 firmware password - comp.unix.solaris
... to boot from the network (dunno why, there is no server ... Based on how I've reset previous sun hardware, I think ... V100 firmware password - comp.unix.solaris Error ...

Microsoft Internet Information Server
Latest Unanswered Forum Posts . Error 404.2 ISAPI and CGI list settings restrictions... ... Windows Media Server or Web Server?

Windows Server | IIS | Web Development | Hosting
Internet Information Services (IIS) 7.5 is a technology included in Windows Server ... This enables organizations to deliver rich, web-based experiences.

7/29/2012 9:36:57 PM