[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | DECmcc user notes file. Does not replace IPMT. |
Notice: | Use IPMT for problems. Newsletter location in note 6187 |
Moderator: | TAEC::BEROUD |
|
Created: | Mon Aug 21 1989 |
Last Modified: | Wed Jun 04 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 6497 |
Total number of notes: | 27359 |
2452.0. "PhaseV NET's not displayed correctly" by RDGENG::PRATT () Fri Feb 28 1992 08:40
Running Ultrix T1.2.4 MCC
If I look at the adjacencies on a routing circuit with NCL then the NET's are
dsiplayed correctly...
ncl> show node .reo.msrv23 routing circuit hdlc-0 adjacency * all status
Node .reo.msrv23 Routing Circuit hdlc-0 Adjacency RTG$0C78
AT 1992-02-28-13:37:54.920+00:00Iinf
Status
State = Up
Neighbor Node Type = Phase V L2 Router
Level = Level 2
Holding Timer = 30
Neighbor Node ID = 08-00-2b-0b-05-41
Neighbor Areas =
{
49::00-41 ,
49::00-42 ,
49::00-01
}
Router NETs =
{
49::00-01:AA-00-04-00-5B-06:00 ,
49::00-41:08-00-2B-0B-05-41:00 ,
49::00-42:08-00-2B-0B-05-41:00
}
_______
ncl>
If I then execute the same command from MCC, the NET's are not displayed
correctly...
MCC> show node .reo.msrv23 routing circuit hdlc-0 adjacency * all status
Node LOCAL_NS:.reo.msrv23 Routing Circuit hdlc-0 Adjacency RTG$0C78
AT 1992-02-28-13:40:38.437+00:00Iinf Status
Examination of attributes shows:
State = Up
Neighbor Node Type = Phase V L2 Router
Level = Level 2
Holding Timer = 30
Neighbor Node ID = 08-00-2b-0b-05-41
Neighbor Areas = { 49::00-41,
49::00-42,
49::00-01 }
Router NETs = { 49::00-01-AA:00-04-00-5B-06-00,
49::00-41-08:00-2B-0B-05-41-00,
49::00-42-08:00-2B-0B-05-41-00 }
MCC>
Regards
Ian Pratt
T.R | Title | User | Personal Name | Date | Lines |
---|
2452.1 | QAR 2399 | TOOK::MINTZ | Erik Mintz, DECmcc Development, dtn 226-5033 | Fri Feb 28 1992 09:59 | 2 |
| Entered as QAR 2399 in mcc_internal
|
2452.2 | fix coming | TOOK::CALLANDER | MCC = My Constant Companion | Wed Apr 08 1992 16:27 | 3 |
| These should be fixed for the EFT update we are planning. Sorry about
that, the datatype conversion routine was doing the wrong thing.
|