[Info-vax] LAT query

Volker Halle volker_halle at hotmail.com
Wed Jan 6 07:25:32 EST 2021


Rich,

this is an example from an IRIS trace of a LAT service announcement (advertisement) message (from 11-DEC-2000) :

** Summary for frame 13 **

   13     +1s LAT_Svc_Adv <-AA0004007FC9  LAT Adver  Node=TINTTI Srv=TINTTI
                                          DLL DIX PType=60-04

** Detail for frame 13 **LAT:
LAT: - - - - - Local Area Transport - - - - -
LAT:
LAT: Message type / flags           = 28
LAT:         001010.. = Adver
LAT:         ......0. = From host
LAT:         .......0 = No response requested
LAT: Server circuit timer (10ms)    = 8
LAT:       High protocol version    = 5
LAT:        Low protocol version    = 5
LAT:    Current protocol version    = 5
LAT:        Current protocol ECO    = 3
LAT:         Message incarnation    = 147
LAT:             Change flags       = 255
LAT:         .......1 = Node group codes have changed
LAT:         ......1. = Node descriptor has changed
LAT:         .....1.. = Service names and/or number of name has changed
LAT:         ....1... = Service ratings have changed
LAT:         ...1.... = Service descriptors have changed
LAT:         ..1..... = Service classes have changed
LAT:         1....... = Other parameters have changed
LAT:     Maximum message size       = 1500
LAT:          Multicast timer       = 60
LAT:             Node status        = 2
LAT:         .......0 = Node is accepting new sessions
LAT: Number of group code bytes     = 1
LAT:         0         1         2         3         4
LAT:         01234567890123456789012345678901234567890123456789
LAT:   0     X-------
LAT:        Node name = TINTTI
LAT: Node description = DEC 3000 VMS V7.1 (ALa)
LAT: Number of services             = 1
LAT:
LAT: - - - - Service 1 of 1 - - - -
LAT:      Service rating            = 63
LAT:        Service name = TINTTI
LAT: Service description = DEC 3000 VMS V7.1 (ALa)
LAT:
LAT: Number of service classes supp = 1
LAT: Supported service class        = 1


You see that the node name appears first in that protocol message and then the service name. So the DECserver will store the node name together with the src node mac address together with the service name. When asked to connect to that service, it will connect to the NODE, then ask for the SERVICE.

Problem explained ?

Volker.



More information about the Info-vax mailing list