Conference azur::mcc

    You need to be more specific about which child entities of node that
    you are referring to. Although in general we like to stay as close
    to the NCL products as is feasible, we make no guarantees to track
    them exactly. If you supply me with a list of specific child entities
    and a description of the possible alternate identifiers that Ultrix
    NCL accepts, I will see what we have done for V1.2.
    
    wally matthews
    

Wally,

I would  guess that the author of .0 wants to use the NSAP as the identifier
for  the Node global class.  As mentioned in .0, ULTRIX NCL allows a variety
of  forms  for  the  node  identifier:  fullname  (and  any abbreviations or
defaulting  handled  by  DNS),  synonym  (Phase IV name), towerset, Phase IV
address (nn.mmmm), NSAP are the ones I know work (NET and VMS style Phase IV
address (nnnnn) may also be supported, I am not sure).

Note that  the  "NSAP"  form  doesn't  use  backtranslation:  it effectively
constructs a towerset containing the NSAP (with the other floors hardcoded).

Graham

    Based upon Graham's information, It is unlikely that for V1.2 DECmcc
    will support the wide range of node identification that Ultrix NCL
    supports. This was brought to our attention only recently and there
    isn't adequate time to resolve it, since our code has been essentially
    frozen for a few weeks. I will bring this to the UI teams attention
    for the next development cycle. 
    
    One of the reasons DECmcc has not been as attentive to this issue as
    NCL is that DECmcc is a wide spectrum management system which spans
    more than a single technology. NCL to do this, uses a lot of DNA5
    specific knowledge in its User Interface to fill in the blanks so
    to speak. This is divergent from the goal of DECmcc for its User
    Interface to generic and not have technology specific code built into
    it. This is another case in point where a point product can be more
    user friendly than a general product. To improve DECmcc we need to
    find some way for the various AMs to influence the user interface
    in doing just this sort of thing.
    
    wally

Hi, 

Thank you for the quick reply. My name is Jerry, I work with the author of 
.0. Our question is about using NSAP or NET as Identifier to make the AM call as
Graham has mentioned.

The problem we are having is when we are trying to access a Phase V node, of 
which the only information available to us at the point is NSAP. Right now, we
are writing the code to translation the NSAP to backtranslation and retrieve the
fullname and then issue the AM calls. Since there is no garantee the existence 
of the backtranslation of each NSAP or any of the NSAP, the chance of exception
is pretty big. When I tested it with WAVE1, the NCL didn't accept NSAP. However,
lately I tested on a Ultrix Phase V node, it did as the attatchment (well, it 
worked with 3 out of 4 NSAP at least, even thought I know there is no 
backtranslation for the NET: 41:45418715:00-41:08-00-2B-0D-A4-87.

So our question is whether MCC will be able to accept NET or NSAP as the NCL
command showing below:


ncl> sh node 41:45418715:00-41:08-00-2B-0D-A4-87

Node 41:45418715:00-41:08-00-2B-0D-A4-87
AT 1992-04-07-15:56:48.140-04:00I0.153

Identifiers

    Name                              = DEC:.lkg.shlump
    Address                           =
       {
          (
          [ DNA_CMIP-MICE ]  ,
          [ DNA_SessionControlV3 , number=19 ]  ,
          [ DNA_OSItransportV1 , 'DEC0'H ]  ,
          [ DNA_OSInetwork , 49::00-04:AA-00-04-00-35-11:21 (cte_ns:.lkg.shlump)
 ]
          ) ,
          (
          [ DNA_CMIP-MICE ]  ,
          [ DNA_SessionControlV3 , number=19 ]  ,
          [ DNA_NSP ]  ,
          [ DNA_OSInetwork , 49::00-04:AA-00-04-00-35-11:20 (cte_ns:.lkg.shlump)
 ]
          ) ,
          (
          [ DNA_CMIP-MICE ]  ,
          [ DNA_SessionControlV3 , number=19 ]  ,
          [ DNA_OSItransportV1 , 'DEC0'H ]  ,
          [ DNA_OSInetwork , 41:45418715:00-41:08-00-2B-0D-A4-87:21 ]
          ) ,
          (
          [ DNA_CMIP-MICE ]  ,
          [ DNA_SessionControlV3 , number=19 ]  ,
          [ DNA_NSP ]  ,
          [ DNA_OSInetwork , 41:45418715:00-41:08-00-2B-0D-A4-87:20 ]
          )
       }

and for other DNA5 routing AMs:

ncl> show node 41:45418715:00-41:08-00-2B-0F-31-8D:20 routing all char

Node 41:45418715:00-41:08-00-2B-0F-31-8D:20 Routing
AT 1992-04-07-11:19:03.290-04:00Iinf

Characteristics

    Version                           = T1.0.6
    Type                              = L2Router
    Maximum Path Splits               = 1
    Maximum Buffers                   = 100
    Redirect Holding Time             = 600
    Generate Checksums                = False
    Lifetime                          = 63
    Manual L1 Algorithm               = Link State
    Manual L2 Algorithm               = Routing Vector
    Manual Area Addresses             =
       {
          41:45418715:00-41
       }
    Segment Buffer Size               = 576
    PhaseIV Buffer Size               = 0
    PhaseIV Address                   = 12.5
    PhaseIV Prefix                    = 49::
    PhaseIV Maximum Address           = 1023
    PhaseIV Maximum Hops              = 30
    PhaseIV Maximum Cost              = 1022
    PhaseIV Maximum Area              = 63
    PhaseIV Broadcast Routing Timer   = 10
    PhaseIV Area Maximum Hops         = 30
    PhaseIV Area Maximum Cost         = 1022
    PhaseIV Maximum Visits            = 63
    Protocols                         =
       {
          ISO8473
       }


Thanks for the help,

Jerry Shiau