T.R | Title | User | Personal Name | Date | Lines |
---|
1807.1 | see 1797.1 | TOOK::MATTHEWS | | Wed Nov 13 1991 12:00 | 1 |
| Please check note 1797.1.
|
1807.2 | MCC-E-FULLNAME_ERROR | VF::LANGASQUE | | Thu Nov 14 1991 03:39 | 12 |
| >================================================================================
>Note 1807.1 MCC-E-FULLNAME_ERROR 1 of 1
>TOOK::MATTHEWS 1 line 13-NOV-1991 12:00
>--------------------------------------------------------------------------------
> -< see 1797.1 >-
>
> Please check note 1797.1.
>
Yes just read 1797 2 min ago, same question teh same day, sorry.
The rename solution works for me. Thanks.
Eric
|
1807.3 | Please read the release notes! | MARVIN::COBB | Graham R. Cobb (Wide Area Comms.), REO2-G/H9, 830-3917 | Fri Nov 15 1991 14:29 | 14 |
| Note that the requirement to issue a RENAME directive to the WANrouter after
configuring and loading is in the release notes. There is also other
important information in there so please make sure you read them.
Graham
P.S. It would be nice if the MCC group either put pressure on the DNS group
to fix DNS to correctly translate a null fullname to external form or
adopted Ben's ULTRIX NCL solution: special case the null fullname and don't
call DNS at all for it!
Technically, the MCC-E-FULLNAME_ERROR is an MCC bug and should be QAR'd --
the node has a legal name (the QAR can then be transferred to the DNS
group!).
|