| Title: | VAXELN |
| Notice: | Support - 2.*; Kits - 3.* |
| Moderator: | HELIX::MIANO LO |
| Created: | Fri Feb 08 1991 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 770 |
| Total number of notes: | 2721 |
A machine running ELN has an image SYSBOOT.EXE on its system disk. Under phase IV DECNET, issuing a NCP TRIGGER nodename caused the system to boot SYSBOOT.EXE from its default boot device. This is the expected behaviour. Under phase V decnet, we expect issuing a NCL BOOT MOP CLIENT nodename to perform the same action. However, issuing this command leaves the target system at the console prompt. The only difference between the PhaseIV and DECnet/OSI inituiated boot is that the DEcnet/OSI system sends MOP V4 in IEEE802.3 format first before sending a MOP V3 Ethernet boot packet. Does anyone have a workaround for this problem ? Andrew/ Cross posted in HELP::DECNET-OSI_FOR_VMS ---------------------------------------------------------------------- Attached are the lan capture of the phaseIV and phaseV mop boot packes. >ETHERNET: Source address : AA0004000704 is a VMS 5.5-2 phase IV host >ETHERNET: Source address : AA0004005E05 is a VMS 7.1 phase V host >(decnet+ V7.1) > >Network Monitor trace Wed 02/12/97 14:32:31 MOP1.TXT > >************************************************************************** >************************************************************************** >******* >Frame Time Src MAC Addr Dst MAC Addr Protocol Description > Src Other Addr Dst >Other Addr Type Other Addr >2 11.687 AA0004000704 DEC 9E8C5E ETHERNET ETYPE = 0x6002 : >Protocol = MOP: DEC Maintenance Operation Protoc > > > >+ FRAME: Base frame properties > ETHERNET: ETYPE = 0x6002 : Protocol = MOP: DEC Maintenance Operation >Protocol > + ETHERNET: Destination address : 08002B9E8C5E > + ETHERNET: Source address : AA0004000704 > ETHERNET: Frame Length : 60 (0x003C) > ETHERNET: Ethernet Type : 0x6002 (MOP: DEC Maintenance Operation >Protocol) > ETHERNET: Ethernet Data: Number of data bytes remaining = 46 >(0x002E) > >00000: 08 00 2B 9E 8C 5E AA 00 04 00 07 04 60 02 0C 00 > ..+..^......`... >00010: 06 00 00 00 00 00 00 00 00 00 00 FF 00 00 00 00 > ................ >00020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > ................ >00030: 00 00 00 00 00 00 00 00 00 00 00 00 ............ > > > > > >Network Monitor trace Wed 02/12/97 14:32:59 MOP1a.TXT > >************************************************************************** >************************************************************************** >******* >Frame Time Src MAC Addr Dst MAC Addr Protocol Description > Src Other Addr Dst >Other Addr Type Other Addr >6 60.584 AA0004005E05 DEC 9E8C5E SNAP ETYPE = 0x6002 > > > > >+ FRAME: Base frame properties > ETHERNET: 802.3 Length = 60 > + ETHERNET: Destination address : 08002B9E8C5E > + ETHERNET: Source address : AA0004005E05 > ETHERNET: Frame Length : 60 (0x003C) > ETHERNET: Data Length : 0x0014 (20) > ETHERNET: Ethernet Data: Number of data bytes remaining = 46 >(0x002E) >+ LLC: UI DSAP=0xAA SSAP=0xAA C > SNAP: ETYPE = 0x6002 > SNAP: Snap Organization code = 08 00 2B > SNAP: Snap etype : 0x6002 > SNAP: Snap Data: Number of data bytes remaining = 38 (0x0026) > >00000: 08 00 2B 9E 8C 5E AA 00 04 00 5E 05 00 14 AA AA > ..+..^....^..... >00010: 03 08 00 2B 60 02 06 00 00 00 00 00 00 00 00 00 > ...+`........... >00020: 00 FF 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > ................ >00030: 00 00 00 00 00 00 00 00 00 00 00 00 ............ > > > >************************************************************************** >************************************************************************** >******* >Frame Time Src MAC Addr Dst MAC Addr Protocol Description > Src Other Addr Dst >Other Addr Type Other Addr >7 60.584 AA0004005E05 DEC 9E8C5E ETHERNET ETYPE = 0x6002 : >Protocol = MOP: DEC Maintenance Operation Protoc > > > >+ FRAME: Base frame properties > ETHERNET: ETYPE = 0x6002 : Protocol = MOP: DEC Maintenance Operation >Protocol > + ETHERNET: Destination address : 08002B9E8C5E > + ETHERNET: Source address : AA0004005E05 > ETHERNET: Frame Length : 60 (0x003C) > ETHERNET: Ethernet Type : 0x6002 (MOP: DEC Maintenance Operation >Protocol) > ETHERNET: Ethernet Data: Number of data bytes remaining = 46 >(0x002E) > >00000: 08 00 2B 9E 8C 5E AA 00 04 00 5E 05 60 02 0C 00 > ..+..^....^.`... >00010: 06 00 00 00 00 00 00 00 00 00 00 FF 00 00 00 00 > ................ >00020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > ................ >00030: 00 00 00 00 00 00 00 00 00 00 00 00 ............ > > > >************************************************************************** >************************** >
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 764.1 | what is the target? | ZYDECO::BODA | Realtime Expertise Center | Wed Feb 12 1997 10:13 | 10 |
Andrew - What is the target CPU? If it is a KAV30, there have been changes made to the KAV30 firmware so it will accomodate MOP V4 boot protocol. This was introduced for KAV30 Rev C02. If this is the case, please see the KAV30 notesfile note #137.4 (CSSVMS::KAV30) Regards, Alan | |||||
| 764.2 | KA55A | GIDDAY::CHONG | Andrew Chong - Sydney CSC | Sat Feb 15 1997 07:02 | 2 |
The target cpu is KA55-A at firmware level v2.6
| |||||
| 764.3 | VAXELN version? | ZYDECO::BODA | Realtime Expertise Center | Tue Feb 18 1997 13:56 | 14 |
Andrew, VAXELN V4.5 added support for MOP V4.0.0. Support for the KA55 in a 3100-85 was latent for V4.5 so I doubt you are using a VAXELN version prior to V4.5. VAXELN never introduced support for Phase V DECnet/OSI. But I agree it is a bit strange that it sees the trigger, but simply drops to the console prompt. I do not have a network with DECnet/OSI to test. Perhaps VAXELN engineering may have some additional thoughts. Regards, Alan | |||||