| Merlin,
The latest release of the VBAM was updated for Vitalink by one of Digital's
engineering groups in Annecy, France. Since I believe that they are
currently the only group who's seen the source code for this version of
VBAM, I would assume that they are the best support channel to work
through.
The Digital contact for VBAM distribution and support issues is Bruno
LeFevre.
From ELF:
Common Name: BRUNO LEFEVRE
Search Surname: LEFEVRE Search Given Name: BRUNO DTN: 887-4234
Telephone: [33]50094111 Intrnl Mail Addr: AEO Location: AEO
Having said all that, let's try to narrow down some of the variables...
>Vitalink bridges, mostly TL III, with a handful of TL 350s. However, after
>registering the 30 bridges there are approx 6 that I cannot access when I
>try any operation on the respective bridge (i.e., SHOW CHARACTERISTICS).
>I get the following MCC error message:
>
> %MCC-E-ILVING, specified tag not found within current constructor
>
>I've not been able to find this error message in the MCC doc set for any
>clarification. Could someone please clarify the meaning of the message
>and give me some indication of what might be wrong?
This message means that when the AM was trying to decode the return packet
from the bridge (ILV-decoding), the packet didn't 'un-fold' like the ILV
rules said it was supposed to. I.e. The AM can't decode it. This
*usually* points to some sort of bug in the agent software or just a
version skew... It may be a bug in that *particular* version of the
TransLAN bridge software. Worse yet, it may be a bug in the bridge
software that only surfaces under certain configurations (i.e. traffic
load, number of circuits, etc).
Since this only seems to happen on a subset of the bridges and this problem
was not detected during any of the regression tests, it'll be much easier
to find/fix this problem if you can help find something that the 'problem
bridges' have in common that sets them apart from the bridges that *aren't*
having the problem? I.e.:
- Does this only happen on those 6 particular TLIII's ?
- Are there any other TLIIIs running the exact same vesion of
TransLAN software that *aren't* experiencing that problem?
- Does it *always* happen on those bridges? Even after a reboot (of
the bridge) ?
- Do you have the ability to *upgrade* the TransLAN software on one
of the complaining TLIIIs and see if that changes anything ?
Regards,
/doug
|