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 |
Problems with an EA and EF talking over the VN bus. MCM shows both connected but LED on the EF shows that's not the case. The DVT command doesn't work with the V1.5 firmware. MCM shows the EF VNbus port as red and open. You can't click it closed. MCM shows the EA VNbus and closed and green, however when you try to click it open you get a "no such MIB" error message. EA and EF running V1.5 HUB running V5.0 MCM V1.1 Suggestions? dave
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
4352.1 | NPSS::WADE | Network Systems Support | Mon Apr 14 1997 09:40 | 12 | |
DEChub Multiswitch 900 MAM V5.1 has some fixes for VNbus and LAN interconnect. The LAN interconnect fixes are related to VNSwitch connections. The DVNEF V1.5.1 firmware also has fixes in this area. Suggestions: upgrade the DVNEF to V1.5.1 upgrade MAM to V5.1 make sure that auto VNbus is disabled on MAM Bill | |||||
4352.2 | NETCAD::FLOWERS | High Performance Networking; Dan | Mon Apr 14 1997 11:08 | 18 | |
Hi Dave, I don't know if this is your problem... but here's a clip from the VNswitch v1.5 release notes: >Upgrading from V1.1 to V1.5 > >Note that in V1.5, the VNbus is enabled by default. If you are >upgrading from V1.1 to V1.5, the VNbus must be manually enabled by >entering the following: > >config>enable int 0 Or... you can reset the module to it's factory defaults. See note 4348 in here. Dan |