| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 187.1 | | PROXY::HUTCHESON | the revolution will not be televised | Tue May 27 1997 17:00 | 8 |
| There are no SPDs for DECVET. A description, if that is what you are after,
can be found in the users guide which is on the firmware CD, the vet$public
area or ftp://imzppy.eng.pko.dec.com/decvet.
If DNSES plugs directly into a system bus I expect it would be sized by
DECVET. What kind of device is it?
Susan
|
| 187.2 | | PROXY::HUTCHESON | the revolution will not be televised | Tue May 27 1997 17:06 | 6 |
| Jean-Luc,
Do you have an available configuration where you could install DECVET and
see how it handles the DNSES?
Susan
|
| 187.3 | OK for testing DNSES | ANNECY::lacerta.aeo.dec.com::bonnier | Jean-Luc CSS Annecy France DTN 887-4055 | Wed May 28 1997 08:59 | 10 |
| Thanks for your replies Susan.
If there is no SDP for DECvet, I am wondering what could be given to a customer for a first approach. I'll have a look at the
user's guide.
For the DNSES support, we will install DECvet on the appropriate AlphaServer running DNSES hardware. I'll give you the status
in the foolowing days.
Regards
JLuc
|
| 187.4 | DNSES not seen by DECvet | ANNECY::lacerta.aeo.dec.com::bonnier | Jean-Luc ... CSS Annecy France DTN 887-4055 | Fri May 30 1997 05:49 | 13 |
| Susan,
We installed DECvet on one of our machine running DNSES HW and
Digital UNIX V3.2C.
The result is that this board is not seen by the DECvet SW.
It's a pity !
Another question : which version of DECvet is supported on
VMS AXP V7.1 ?
Thanks again for your support.
Jean-Luc
|
| 187.5 | | PROXY::HUTCHESON | the revolution will not be televised | Mon Jun 02 1997 17:39 | 9 |
| If the DNSES is being used to implement DECNET or tcp/ip, it should at least be
sized by DECVET. This should probably be fixed. I'll contact you offline about
DECVET support.
The most recent DECVET OVMS release supports OVMS V7.0. I am currently testing
the build for OVMS V7.1. I expect to make it available soon, possibly later
this week.
Susan
|
| 187.6 | HW config and VET perception | ANNECY::BONNIER | Jean-Luc ... CSS Annecy France | Tue Jun 03 1997 05:48 | 136 |
| Susan
Thanks again for your reply and the future VMS 7.1 support.
When starting DECvet (either cli or window), we have the message :
"sizer was unable to get information from all devices"
Here is an extract of the HW config from the uerf tool:
SYSTEM STARTUP: Fri May 30 10:27:24 1997
MESSAGE PCXAL keyboard, language English (American)
Alpha boot: available memory from 0xb66000 to 0xffee000
Digital UNIX V3.2G (Rev. 62); Fri Apr 11 15:43:15 WET
_DST 1997
physical memory = 256.00 megabytes.
available memory = 244.53 megabytes.
using 975 buffers containing 7.61 megabytes of memory
Firmware revision: 4.7
PALcode: OSF version 1.45
ibus0 at nexus
AlphaServer 2100 4/200
cpu 0 EV-4s 1mb b-cache
gpc0 at ibus0
pci0 at ibus0 slot 0
tu0: DECchip 21040-AA: Revision: 2.3
tu0 at pci0 slot 0
tu0: DEC TULIP Ethernet Interface, hardware address:
_08-00-2B-E7-36-BD
tu0: console mode: selecting 10Base5 (AUI) port
psiop0 at pci0 slot 1
Loading SIOP: script 1001000, reg 81000000, data
_406a0f80
scsi0 at psiop0 slot 0
rz0 at scsi0 bus 0 target 0 lun 0 (DEC RZ25L (C)
_DEC 0006)
rz1 at scsi0 bus 0 target 1 lun 0 (DEC RZ26L (C)
_DEC 440C)
rz2 at scsi0 bus 0 target 2 lun 0 (DEC RZ28 (C)
_DEC T436)
rz6 at scsi0 bus 0 target 6 lun 0 (DEC RRD43 (C)
_DEC 0064)
tz4 at scsi0 bus 0 target 4 lun 0 (DEC TLZ06
_(C)DEC 0491)
tz5 at scsi0 bus 0 target 5 lun 0 (DEC TZK11 (C)
_DEC 00A1)
eisa0 at pci0
ace0 at eisa0
ace1 at eisa0
lp0 at eisa0
fdi0 at eisa0
fd0 at fdi0 unit 0
vga0 at eisa0
1024x768 (QVision )
dns0 at eisa0
dns0: Digital WAN Device Driver Interface
dns1: Digital WAN Device Driver Interface
dns2: Digital WAN Device Driver Interface
dns3: Digital WAN Device Driver Interface
dns2 at eisa0
dns4: Digital WAN Device Driver Interface
dns5: Digital WAN Device Driver Interface
lvm0: configured.
lvm1: configured.
cam_logger: CAM_ERROR packet
cam_logger: bus 0 target 5 lun 0
ss_device_reset_done
Bus device reset has been performed
dli: configured
SuperLAT. Copyright 1993 Meridian Technology Corp. All
_rights reserved.
wandd_base: configured
wan_utilities: configured
ctf_base: configured
Node ID is 08-00-2b-e7-36-bd (from device tu0)
dna_netman: configured
dna_dli: configured
Here is the display of the DECvet "show devices all" command:
VET_setup>
SYSTEM/DEVICE TYPE SUBTYPE SIZE STATUS
------------- ---- ------- ---- ------
teleco
memory V_MEM 134217728
file FILE_DATA
cpu CPU alpha
network NETWORK tcpip
/dev/rrz1a DISK rz26l 67108864 LOCAL_RW
/dev/rz1a DISK rz26l 67108864 LOCAL_RW
/dev/rrz1b DISK rz26l 134217728 LOCAL_RW
/dev/rz1b DISK rz26l 134217728 LOCAL_RW
/dev/rrz1c DISK rz26l 1050040320 LOCAL_RW
/dev/rz1c DISK rz26l 1050040320 LOCAL_RW
/dev/rrz1d DISK rz26l LOCAL_RW
/dev/rz1d DISK rz26l LOCAL_RW
/dev/rrz1e DISK rz26l LOCAL_RW
/dev/rz1e DISK rz26l LOCAL_RW
/dev/rrz1f DISK rz26l LOCAL_RW
.
.
.
.
/dev/nrmt0a TAPE tlz06 LOCAL_RW
/dev/nrmt0h TAPE tlz06 LOCAL_RW
/dev/nrmt0l TAPE tlz06 LOCAL_RW
/dev/nrmt0m TAPE tlz06 LOCAL_RW
/dev/rmt0a TAPE tlz06 LOCAL_RW
/dev/rmt0h TAPE tlz06 LOCAL_RW
/dev/rmt0l TAPE tlz06 LOCAL_RW
/dev/rmt0m TAPE tlz06 LOCAL_RW
/dev/nrmt1a TAPE tzk11 LOCAL_RW
/dev/nrmt1h TAPE tzk11 LOCAL_RW
/dev/nrmt1l TAPE tzk11 LOCAL_RW
/dev/nrmt1m TAPE tzk11 LOCAL_RW
/dev/rmt1a TAPE tzk11 LOCAL_RW
/dev/rmt1h TAPE tzk11 LOCAL_RW
/dev/rmt1l TAPE tzk11 LOCAL_RW
/dev/rmt1m TAPE tzk11 LOCAL_RW
terminal TERMINAL
printer PRINTER
video VIDEO
The DNSES are standard synchronous EISA boards used by the standard DECss7
software developed in Valbonne (France) and aimed at managing signalisation
networks for telecom operators all over the world.
(part number = 00-DNSES-AA)
The DNSES boards are running DECss7 firmware and require WANDD subsets installed
There is only DNANETMAN (a subset of DECnet/OSI) installed.
I hope this helps.
Regards
JLuc
|
| 187.7 | on recognizing devices | DECWET::DADDAMIO | Design Twice, Code Once | Tue Jun 03 1997 16:54 | 11 |
| If the DNSES are used to implement the tcp/ip connection then they will
be exercised as the NETWORK device that is listed in the VET output.
VET does not automatically understand and recognize new devices. Code
needs to be added to VET to recognize a new device and an exerciser
written if it can't be exercised using one of the standard exercisers
provided with VET (example of this is the Denali graphics board for
which Kubota wrote an exerciser). There is a development kit with
library calls so it's easy to build an exerciser, but whoever does it
really needs to know the hardware and the best way to test it.
Jan
|
| 187.8 | DECVET does not recognize DNSES | PROXY::HUTCHESON | the revolution will not be televised | Tue Jun 03 1997 17:57 | 18 |
| Thanks, Jan.
Jean-Luc,
I have been talking to the hardware engineer who supports DNSES, John Perry.
He has been aware for some time that DECVET does not test this device.
DECVET is sizing the tu0 as the NETWORK device. DECVET does not see DNSES as a
NETWORK or any other testable device. Furthermore, DECVET only sizes devices for
which there is an exer and there is none for this device. John Perry asserts
that DECVET should size and test the DNSES as well as it's follow-on product,
which he says is coming down the pike.
I'll bring this up with my manager and it will probably get put in the queue. As
Jan pointed out, the developer's kit can be used to implement a home-grown
exerciser.
Susan
|