Leslie,
Thank you for the response. I have not specifically added the OID
information to the files which I will. I don't think this is the whole
problem however. NetView will discover the VLAN segments ( made up by the
50 or so 5500s), but treats them as if they were just hubs. Other virtual
interfaces cannot be mapped to anything and are placed off to the side.
Is this normal? Will placing the OID information in NetView correct this?
If more detail is needed I can attempt to draw a diagram of the network and
also how NetView presents it. I will be on-site on Thursday to work on the
problem.
Ken
Maryville Data Systems
One Pierce Place Suite 475W
Itasca, IL 60143
(630) 285-9597 ext. 5105
> -----Original Message-----
> From: Leslie Clark [SMTP:lclark AT US.IBM DOT COM]
> Sent: Saturday, October 24, 1998 2:31 PM
> To: NV-L AT UCSBVM.ucsb DOT edu
> Subject: Re: Cisco Catalyst 5500 Switches and NetView V4.1
>
> >I have a customer with NetView v4.12 who has several Cisco 5500 switches
> in
> >a VLAN configuration. NetView
> >is not handling the discovery and mapping of this environment well at
> all,
> >Is this an unsupported environment with
> >NetView V4? Is it fixed in NetView v5? Any one with this environment
> have
> >comments on using NetView to manage the
> >5500s?
>
> You don't say how it is handling it, or what you expected it to do.
>
> All you should expect Netview to do with this is draw it, preferably at
> the
> Network submap level, in the
> subnet appropriate for the ip address and mask of its interface card.
> There
> should be no difference
> between Netview versions, I think, in the handling of this. I suspect
> that
> they are being discovered as
> unknown snmp Object IDs and placed (as generic boxes) in the segment level
> submap, as if they were
> PCs or something.
>
> In all cases I expect that you will have to add the agent to the agents
> list in
> /usr/OV/fields/C/snmp_fields
> and run ovw -fields, then update the oid_to_type file using 'smit nv6000
> ..
> configure', enterng the oid,
> selecting the vendor (cisco) and agent (you just defined it) and setting
> the
> type to H or B. (There is no
> special entry for Switch, I just pick H or B and that gets it promoted
> from the
> Segment submap to the
> Network submap, the same way G promotes things to the Internet submap).
> Once
> you call it a H or B,
> Netview will automatically assign an approprate symbol for it. If you load
> CiscoWorks, it provides its
> own bitmaps, but some of the later devices, or later releases of Cisco os
> have
> different OIDs that even
> Cisco does not provide bitmaps for. Anyway. But if you want a different
> symbol
> than Netview assigns,
> configure oid_to_sym to assign it a different one. (Look at Help...Legends
> on
> the top toolbar to see what
> is available). To get these changes applied, it is usually quickest to
> just
> delete and rediscover the device.
>
> Now, all of this is really just cosmetic. Netview handles all such devices
> in
> the same way, and does not
> provide any special topology handling for switches, bridges, or hubs that
> would, for instance, divide
> IP subnets and associate end nodes with such devices. So there is nothing
> to
> 'not support', as long
> as the device provides an entry in the MIB II interface table for the
> address
> you know it by.
>
> Cordially,
>
> Leslie Clark
> IBM Global Services - Network & Systems Management - Detroit
|
