[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
Moderator: | NETCAD::COLELLA DT |
|
Created: | Wed Nov 13 1991 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 4455 |
Total number of notes: | 16761 |
4424.0. "VN management gotcha" by PTOJJD::DANZAK (Pittsburgher �) Tue May 20 1997 10:18
Create the following scenario with FOUR VNswitches....
1.) In slots 1/2 put two VNswitches, preferably an EA in one
2.) In slots 7/8 put two VNswitches, preferaboy an EA in one
3.) Connect your management station to a VNswitch
4.) Assign all the IP addresses to the switches, hub etc.
5.) Use MCM to manage the hub
6.) create a VNbus for the entities in slot 1/2
7.) Create a VNbus for the entities in slot 7/8
8.) Drag the 1/2 VN switches to the first VNbus
9.) Drag the 7/8 VNswitches to the second VNbus
10.) Refresh your hub display, note that the VN switches
which are NOT connected to the bus that your management
station is plugged into are now NO LONGER manageable because
you don't have TCP/IP connectivity to 'em.
Any questions why we need that management bus support in the
VNswitches? (so we don't need a funky Ethernet connection to 'em to
manage the @*$()@*()@ things!)
I was demo-ing the VN stuff at interop and this little 'gotcha' caught
me - I broke my IP/LAN connectivity to the VN and could NOT manage it -
where "manage" means muck with the VSDs etc....nasty!)
Hope that we fix this - soon! It's a PAIN to explain to customers!
REgards,
j
(cross posted in common-brouters)
T.R | Title | User | Personal Name | Date | Lines
|
---|