Conference help::decnet-osi_for_vms

3960.0. "%NCL-E-CMLRCVFAILED, -using WITH-clause" by ZUR01::SCHNEIDER (Kurt Schneider, SW-Support Zurich) Tue May 13 1997 04:20

    Hello,
    		The following command would be very useful to display
    the router's L1 and L2 adjacenceies. Would this be implemented in
    a future version. I tried V6 and V7. At least Unix does display the
    desired output among the failing replies.
    
    On VMS,
    
    NCL>sho node rlert1 rout cir rle_lan_1 adj * all, with Level = Level 2
    %NCL-E-CMLRCVFAILED, error receiving command request
    -CML-E-CMIPPROB, CMIP error -- Bug in CMIP encoding/decoding routines
    -CML-E-INVALID_PDU, invalid PDU
    
    Node rlert1 Routing Circuit rle_lan_1 Adjacency *
     with Level = Level 2
    
    command failed due to:
     Unknown response failure code
    
    On Unix,
    
    ncl> sho node rlert1 rout cir rle_lan_1 adj * all, with Level = Level 2
    
    Node rlert1 Routing Circuit rle_lan_1 Adjacency RTG$08D5
    AT 1997-05-13-09:54:49.335+02:00I-----
    
    FAILED IN DIRECTIVE: Show
    DUE TO: The Entity Filter attribute is not valid
    
    _______
    
    ... repeated for all endnode-adjacencies ...
    
    
    Node rlert1 Routing Circuit rle_lan_1 Adjacency RTG$0041
    AT 1997-05-13-09:54:51.055+02:00I-----
    
    Identifiers
    
        Name                              = RTG$0041
    
    Status
    
        Type                              = Autoconfigured
        State                             = Up
        LAN Address                       = aa-00-04-00-01-fc (63.1)
        Neighbor Node Type                = Phase IV L2 Router
        Level                             = Level 2
        LAN Priority                      = 32
        Holding Timer                     = 45
        Neighbor Node ID                  = aa-00-04-00-01-fc (63.1)
        Neighbor Areas                    =
            {
                49::00-3F
            }
        Router NETs                       =
            {
                49::00-3F:AA-00-04-00-01-FC:00
            }
    
    ncl>
    
    Thanks for a reply,
    
    Regards
    Kurt

    This has been fixed in the next release of DECnet-Plus and in future
    ECO kits.  (See Note 3243.)  If you need to obtain the fix before then, 
    please log an IPMT.
    
                                     - LL

    thanks Lindaleigh,
    
    I will open an IPMT if the customer insists to have it sooner.
    
    Regards
    Kurt