Conference azur::mcc

2556.0. "navigate across" by ICS::WOODCOCK () Thu Mar 12 1992 16:51

Hi there,

Will MCC every navigate across instead of down???

With global wildcards coming into play in V1.2 we will now only have an
entity within ONE given domain thru the entire hierarchy. This allows for
wildcarding the alarms without receiving notifies in too many domains for the
same entity. With this change we have also represented what used to be an 
entity with the domain by which that entity is contained. When navigating MCC 
keeps going down rather than across. 

Ex. domain structure:

                           .bb
                            |
           -----------------------------------------
           |    |    |    |    |    |    |    |    |
          .lkg       (other domains)             .pko
           |                                       |
          .pko                                    .lkg


In the above example .bb only contains the other domains and basically no
global entities. There is a link between a node in .lkg and a node in .pko.
Therefore .pko is also placed within .lkg and vice versa to represent the link.
From .bb I click into .lkg. If I am working the lkg_pko circuit problem I will
want to flip back and forth between the two site domains. If I now click into
.pko from .lkg I have gone down again. To get back to .bb I have to look-up
(back to .lkg), then look-up again to get to .bb. The more times you look-into
between these sites the further down you go. I realize I could simply look-up
to .bb then down again to .pko but I'm a typical impatient net mngr with a 
problem to be fixed :-).

The suggestion is to be able to navigate *across* from .lkg to .pko and
back again. Considering domains are unique objects you might be able to
navigate the user to the domain clicked upon by sending them to the highest
point that domain resides within the hierarchy. Make sense???

just a thought,
brad..

If you're in that much of a hurry, just go to the Map window menu bar and pull
down "Open Domain", then you can go directly to that domain.

Downside is that you lose 'parent' context if you've gotten into your current
domain via a 'look into' operation (double click) and the new domain now looks
like the 'root' of your view....

/doug

    This is a very much requested feature. We would like to support it
    in the future. One of the issues is that to do this in a generic way
    you need topology context which unfortunately we do not have as yet.
    
    For example. If you have a relationship attribute for Node4.circuit
    that points to the remote Node4.circuit at the other end of a 
    point to point DECnet4 circuit, then the IMPM could easily implement
    the "navigate to the other end of the circuit" function. 
    
    Yes, there is enough raw information today to do this. The problem
    is that it is very specific to Node4, or to Bridge, or to Terminal
    Server, or to whatever it is. What is missing is a special relationship
    attribute that the IMPM can use to guide it so that it doesn't have
    to hard code a lot of knowledge about specific objects. We have it
    in our plans. Maybe we will be funded to do it before I am qualified
    for early retirement ::-)
    
    wally

re: .2

Glad to see the understanding of the need. Rather than getting into the
entity specifics maybe you could look to implement something just for
domains which is a generic use within MCC. Have you seen the eligibility
within the new retirement package? You may be ready to go already :-).

re: .1

Pull down and opening a new domain typically takes longer (maybe because
it has to reset NOTIFIES???).

thanks for the ear,
brad...