[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | LAT notes conference |
| Notice: | To reset your notebook -> SET SEEN/BEFORE=13-OCT-1992:01:00 |
| Moderator: | STAR::KOJNOK |
|
| Created: | Mon Mar 10 1986 |
| Last Modified: | Fri May 23 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4961 |
| Total number of notes: | 19526 |
4953.0. "V7.0 LAT problem ?" by CSC32::MAULUCCI () Fri Mar 28 1997 17:27
A customer I am working with has the following topology:
Thinwire
+-------+---------+--------+--------+---------------+
SNOOPY---------HP HUB HP HUB HP HUB HP HUB HP HUB DECbridge
90
10BT |
thickwire
--------------------------------------------------|
| | | |
| Node Chip DECserver Dale
DR90FA
|
| fiber
|
DECbridge90fl
|
| thinwire
|
|
HP HUB
| (10bt)
| \
opus \blondi
All of the nodes shown are running v7.0 AXP OVMS. Customer also has
3 nodes running v6.2 VAX OVMS. ALL of the nodes are cluster members.
The table below shows which nodes can connect to one another, and which
can not connect without getting a "%LAT-F-PROTERR, communication
protocol error" message.
All of the nodes can connect via LAT to / from the V6.2 nodes. The
below table shows which V7.0 nodes can connect and which can not:
chip snoopy opus blondie dale
snoopy ok - ok ok ok
chip - no no ok ok
opus ok no - ok ok
blondie no no no - ok
dale no no no ok -
All of the counters look real clean, is there a known problem with the
LAT driver in VMS 7.0?
Regards,
Gene
I have added a trace below:
- - - - - - - - - - - - - - - - Frame 46 - - - - - - - - - - - - - - -
- -<CR>
<CR>
SUMMARY Delta T Destination Source Summary<CR>
46 2.4177 SNOOPY OPUS LAT C Connect D=0000
S=8002
<CR>
LAT: ----- Local Area Transport -----<CR>
LAT: <CR>
LAT: Message type / flags = 06<CR>
LAT: 0000 01.. = Connect<CR>
LAT: .... ..1. = To host<CR>
LAT: .... ...0 = No response requested<CR>
LAT: Number of slots = 0<CR>
LAT: Destination circuit ID = 0000<CR>
LAT: Source circuit ID = 8002<CR>
LAT: Sequence number = 00<CR>
LAT: Acknowlegement number = FF<CR>
LAT: Maximum receive datagram size = 1500 bytes<CR>
LAT: Version number = 5<CR>
LAT: ECO level = 3<CR>
LAT: Maximum simultaneous sessions = 16<CR>
LAT: Extra data link buffers queued = 9<CR>
LAT: Server circuit timer = 8 x 10msec<CR>
LAT: Server keep alive timer = 20 seconds<CR>
LAT: Facility number = 0<CR>
LAT: Product type = 3<CR>
LAT: Product version number = 3<CR>
LAT: Node name = "SNOOPY"<CR>
LAT: Master node name = "OPUS"<CR>
LAT: Location = "DEC 3000/300 AXP"<CR>
LAT: Parameter 0:<CR>
LAT: Parameter code = 1 (Flags)<CR>
LAT: Parameter length = 2 bytes<CR>
LAT: Flag word = 64<CR>
LAT: .... ...0 = Line is local<CR>
LAT: .... ..0. = Logins allowed on this line<CR>
LAT: Parameter 1:<CR>
LAT: Parameter code = 2 (Queue identifier)<CR>
LAT: Parameter length = 16 bytes<CR>
LAT: Queue identifier = 14848<CR>
LAT: Parameter 2:<CR>
LAT: Parameter code = 232 (Unknown)<CR>
LAT: Parameter length = 0 bytes<CR>
LAT: Unknown parameter = <CR>
LAT: Parameter 3:<CR>
LAT: Parameter code = 214 (Unknown)<CR>
LAT: Parameter length = 1 bytes<CR>
<FF>Sniffer Network Analyzer data from 26-Mar-97 at 13:27:52, file
C:\ENCAP\SNO
<CR>
<CR>
LAT: Unknown parameter = 9B<CR>
LAT: <CR>
LAT: [9 padding byte(s)] <CR>
LAT: <CR>
<CR>
<CR>
- - - - - - - - - - - - - - - - Frame 47 - - - - - - - - - - - - - - -
- -<CR>
<CR>
SUMMARY Delta T Destination Source Summary<CR>
47 0.0006 OPUS SNOOPY LAT R Connect D=8002
S=8001
<CR>
LAT: ----- Local Area Transport -----<CR>
LAT: <CR>
LAT: Message type / flags = 04<CR>
LAT: 0000 01.. = Connect<CR>
LAT: .... ..0. = From host<CR>
LAT: .... ...0 = No response requested<CR>
LAT: Number of slots = 0<CR>
LAT: Destination circuit ID = 8002<CR>
LAT: Source circuit ID = 8001<CR>
LAT: Sequence number = 00<CR>
LAT: Acknowlegement number = 00<CR>
LAT: Maximum receive datagram size = 1500 bytes<CR>
LAT: Version number = 5<CR>
LAT: ECO level = 3<CR>
LAT: Maximum simultaneous sessions = 16<CR>
LAT: Extra data link buffers queued = 9<CR>
LAT: Server circuit timer = 8 x 10msec<CR>
LAT: Server keep alive timer = 20 seconds<CR>
LAT: Facility number = 0<CR>
LAT: Product type = 3<CR>
LAT: Product version number = 3<CR>
LAT: Node name = "SNOOPY"<CR>
LAT: Master node name = "OPUS"<CR>
LAT: Location = "DEC 3000/300 AXP"<CR>
LAT: Parameter 0:<CR>
LAT: Parameter code = 1 (Flags)<CR>
LAT: Parameter length = 2 bytes<CR>
LAT: Flag word = 0A<CR>
LAT: .... ...0 = Line is local<CR>
LAT: .... ..1. = No logins allowed on this line<CR>
LAT: Parameter 1:<CR>
LAT: Parameter code = 2 (Queue identifier)<CR>
LAT: Parameter length = 16 bytes<CR>
LAT: Queue identifier = 43008<CR>
<CR>
<CR>
- - - - - - - - - - - - - - - - Frame 48 - - - - - - - - - - - - - - - - -<CR>
<CR>
SUMMARY Delta T Destination Source Summary<CR>
48 0.0012 SNOOPY OPUS LAT Disconnect D=8001 S=0000
<FF>Sniffer Network Analyzer data from 26-Mar-97 at 13:27:52, file C:\ENCAP\SNO
<CR>
<CR>
<CR>
LAT: ----- Local Area Transport -----<CR>
LAT: <CR>
LAT: Message type / flags = 0A<CR>
LAT: 0000 10.. = Disconnect<CR>
LAT: .... ..1. = To host<CR>
LAT: .... ...0 = No response requested<CR>
LAT: Number of slots = 0<CR>
LAT: Destination circuit ID = 8001<CR>
LAT: Source circuit ID = 0000<CR>
LAT: Sequence number = 01<CR>
LAT: Acknowlegement number = 00<CR>
LAT: Disconnect reason = 2 (Illegal format)<CR>
LAT: Disconnect reason text = ""<CR>
LAT: <CR>
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 4953.1 | send it on up | CSC32::B_HORNE | | Tue Apr 22 1997 19:46 | 4 |
| frame #46 appears to contain unknown parameters which may be the cause
of the subsequent illegal format disconnect. seems to me v7.0 should
be able to talk with another v7.0 OpenVMS Alpha system using set
host/lat. I would recommend escalating this call...
|