You did not say how the traffic is being routed/switched from one VLAN to
another, so this "solution" may not apply to your environment. We also are
using Cat5000/5500 switches to implement our VLANs. We are using Cisco
routers to route between the VLANs. The routers have a logical subinterface
configured in each VLAN, so on our NetView map there is a router interface
in every network icon corresponding to a VLAN.
If this doesn't work for your network, then another approach would be to
utilize more of the Cisco-specific information and tools, like the log
messages from the Catalysts, and/or CiscoWorks 2000 (Campus topology map,
User Tracking, VLAN Director).
Joel Gerber - I/T Networking Professional - USAA Information Technology Co.
- San Antonio, TX
* (210)456-4231 * mailto:Joel.Gerber@USAA.com "
http://www.usaa.com
-----Original Message-----
From: Brad Martin [SMTP:bmartin@METLIFE.COM]
Sent: Tuesday, January 11, 2000 16:11
To: NV-L@UCSBVM.UCSB.EDU
Subject: Virtual LANs
We are beginning to implement several VLAN's within our environment
using
Cisco's 5000, 5500, and 6500 switches. It appears that NetView
creates a network
icon for every VLAN, but a switch that participates in multiple
VLANs will only
appears in one of them. Since we are primarily using VLAN's to
segment our user
population, it would be nice to have the network (VLAN) icon turn
yellow if the
switch was unavailable.
Prior to implementing VLAN's, the switch was the only icon in the
user's network
segement because desktops are not included in our maps. In the new
environment,
we have multiple network icons for the user population, but all the
switches are
in one network and the other network icons are empty. Thus, it is
difficult to
understand which users are impacted if the switch becomes
unavailable.
Can anyone give recommendation on how to manage the VLAN's?
Brad Martin
MetLife.
|