Interesting idea Scott. This calls for SNMP standards...
Now that opens up a whole other can of worms :)
>From the Web Console Users Guide v 7, on pg 49:
> A scope is defined by a set of top level locations and networks.
> Scope is used by the Submap Explorer as follows:
> - The only map enabled for viewing is the Default map.
> - The Root submap contains only those networks and locations that are within
> scope. This submap uses a row and column layout style, which means that
> SmartSet submaps cannot be displayed.
I think I am missing the point somewhere along the line. Are you saying, that
when
"small network group" want to see their stuff, they open the default map as
normal,
but they only see the stuff that belongs to them? Will they see it in the main
map,
or everything collected in one smart-set? Are you basing their scope on the
smartset?
-----Original Message-----
From: Barr, Scott [mailto:Scott_Barr@csgsystems.com]
Sent: Wednesday, September 04, 2002 3:04 PM
To: Gow Kevin (KTSO 4); nv-l@lists.tivoli.com
Subject: RE: [nv-l] Multiple Map Madness
The web client *IS* the way to go and the use of Scope is the best way to do
it. You have to have some way of recognizing devices they want to see - we use
the snmp contact/location field of the devices to set up smartsets that
segregate resources the way we want. Having the devices with an snmp contact
name of "Network Team" or similar would allow you to build a smartset called
"Network Team Stuff" and then the web client would allow you to display it
based on scope. Maybe this would work for you.
|