RE: [nv-l] Poor switch navigation
2006-04-26 15:40:53
Leslie,
That
is exactly what I was looking for. I am just going to create additional location
objects to avoid clutter.
Thank
you!
-
Rob
Hi, Rob. I'm
way behind. I'm not sure I understand what you are trying to do here. I assume
you mean layer2 switches, so they don't show up at the IP Internet level of
the map. They should be flagged in oid_to_type as H or B so they show up in
the Network level submaps, right? And you are looking for a way to identify,
preferably from the top level, where these things are?
One thing you could do is to promote them to the IP
Internet level of the map by adding a G in the oid_to_type file. I don't think
that would hurt anything. Depending on how many of them you have, it would add
clutter to the map. If they are cut and pasted into location submaps, that
should be fine, thought. To see the full effect of this, for each oid you
change, you need to do an ovtopofix -u <oid> and then probably
close and open the map.
If I have
not understood the question, ask again...
Cordially,
Leslie A. Clark IT Services Specialist,
Network Mgmt Information Technology Services Americas IBM Global
Services (248) 552-4968 Voicemail, Fax, Pager
"Shipley, Rob"
<rshipley AT mt DOT gov> Sent
by: owner-nv-l AT lists.us.ibm DOT com
04/14/2006 01:13 PM
Please respond
to nv-l AT lists.us.ibm DOT com |
|
To
| <nv-l AT lists.us.ibm DOT com>
|
cc
|
|
Subject
| [nv-l] Poor switch
navigation |
|
I am looking for an efficient method to navigate to switches on the IP
map. It is hard to determine which network the switches are in. Have toyed
with the idea of changing the network symbols if a switch is in the
submap.
We have smartsets for each switch type, but this is
hard too since it is not based on location. Any suggestions?
|
|
|