| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3493.1 | Questions 3 & 5 | SLINK::HOOD | Your bad news bear | Mon Apr 29 1996 15:08 | 11 |
| > 3. The above is the same for every platform HubWatch has been
> ported to.
GIGAswitch/FDDI is supported equally on all HUBwatch platforms.
> 5. clearVISN Resilience does not support the GIGAswitch
Version 2.0 of the clearVISN Recovery Manager supports GIGAswitch/FDDI.
Version 1.0 and 1.1 of clearVISN Resilience does not.
Tom Hood
|
| 3493.2 | | NETCAD::DRAGON | | Tue Apr 30 1996 20:12 | 25 |
| Carlos,
1. I believe that FW V2.2 has Dual Homing Support, but could
someone confirm this? As for M-port, you'll need MCM V5.0.
I would recommend using FW V3.0 with MCM V5.0.
2. You can use GIGAswitch/FDDI FW 3.0 with MCM V5.0.
3. See #2.
4. Correct.
5. Current version does not support GIGAswitch (/FDDI or /ATM).
6. MCM V5.0 supports:
a) Hunt Groups
b) Not sure what you mean here but M-port enable/disable
supported and A/B/M ports recognized
c) Full Duplex FDDI (can enable/disable Full Duplex (FFDT))
d) DOES NOT support ARP Server
e) Supports some additional STP parameters, but DOES NOT
currently allow enable/disable of STP on ports.
Regards,
Bob
|
| 3493.3 | | NPSS::MDLYONS | Michael D. Lyons DTN 226-6943 | Tue Apr 30 1996 20:38 | 34 |
| <<< SCHOOL::CLUSTERFILES:[NOTES$LIBRARY]GIGASWITCH.NOTE;1 >>>
-< GIGAswitch >-
================================================================================
Note 707.1 GIGAswitch/FW/hubWatch/clearVISN 1 of 1
NPSS::MDLYONS "Michael D. Lyons DTN 226-6943" 28 lines 29-APR-1996 09:40
--------------------------------------------------------------------------------
> 1. To demonstrate Dual Homing in the GIGAswitch, I need FW 2.2
> or later. This is for being able to configure M-ports.
No, M ports predated BL2.2 except for the FGL-4 line card. However,
BL2.2 is already one revision behind, anything earlier should not be
used.
> 2. To demonstrate HubWatch administering filters, I can only
> use FW 2.1, since HubWatch does not support later versions.
? What "FW 2.1" firmware are you talking about? Hubwatch for xxx
works perfectly well with BL2.2 firmare. Hubwatch for Windows has
problems with BL3.0.
> 3. The above is the same for every platform HubWatch has been
> ported to.
...I cannot speak for the Hubwatch group, but there's no reason that
BL2.2 wouldn't be supported that I can think of.
> 4. To use hunt groups need version FW 3.0.
This is correct.
...I will leave the other questions to the appropriate groups to answer...
MDL
|
| 3493.4 | Thanks! | MXOC00::CSILVA | Carlos@MXO 7296514 Free but focused | Wed May 01 1996 23:46 | 24 |
|
re
.2
Yeah!, I have FW 2.0 and I've been doing some testing with
dual homing with both FGL-2 and FGL-4 cards.
Great, but there are two problems:
1. BLD 3.0 of GIGAswitch firmware is temporarily
unavailable because some bugs and compatibility
problems with CISCO.
2. When MCM 5.0 will be available?, is there a
field test version or something?, definitively
no plans to integrate with Spectrum?
At this moment I'm configuring M ports from Netview,
my question was if MCM 5.0 will allow me to do that
graphically.
|
| 3493.5 | But...! | MXOC00::CSILVA | Carlos@MXO 7296514 Free but focused | Wed May 01 1996 23:48 | 4 |
|
Ah!, but I installed FW 2.0 because 2.2 does not allow me to
configure filters from HubWatch
|
| 3493.6 | | NETCAD::DRAGON | | Thu May 02 1996 12:28 | 6 |
|
re:.4
MCM V5.0 will allow you to set m-ports graphically.
Bob
|
| 3493.7 | | NPSS::MDLYONS | Michael D. Lyons DTN 226-6943 | Thu May 02 1996 15:25 | 17 |
| Re: .5 ...you're saying that you installed GIGAswitch/FDDI BL2.0
firmware instead of GIGAswitch/FDDI BL2.2 firmware because of a
perceived problem setting filters? Please tell me I'm wrong! No one
should be running anything older than BL2.2. Please explain what
filter problems you have observed which have led you to install this
obsolete firmware.
To the best of my knowledge, many GIGAswitch/FDDI customers are
currently using the most recently released version of Hubwatch on
various platforms to successfully manage GIGAswitch/FDDI BL2.2
including filters. BL3.0 and Hubwatch have a problem. BL2.2 and
Hubwatch do not.
BL2.0 should absolutely not be installed at any customer site.
Michael D. Lyons
GIGAswitch/FDDI product support
|
| 3493.8 | | NPSS::MDLYONS | Michael D. Lyons DTN 226-6943 | Thu May 02 1996 15:35 | 35 |
| P.S. Perhaps I am assuming that when you say FW 2.0, you mean
GIGAswitch/FDDI system BL2.0
Note that until BL3.0, there has been no connection between FGL
firmware levels and the official release level. Indeed, FGL-2 and
FGL-4 firmware versions are different for the same levels of code. If
you mean BL2.0 of FGL-4 firmware, then my histrionics have been
unnecessary. Every GIGAswitch/FDDI customer should be running BL2.2 at
a minimum.
GIGAswitch/FDDI BL2.2 includes:
SCP operational code: 2.20
SCP boot block code: 2.00
SCP downline load code: 1.00
FGL-2 operational code: 2.20
FGL-4 operational code: 2.00
AGL-2 operational code: 2.00
CLK operational code: 2.10
PSC operational code: 2.0
GIGAswitch/FDDI BL3.0 versions have been made more rational:
SCP operational code: 3.00
SCP boot block code: 2.00
SCP downline load code: 1.00
FGL-2 operational code: 3.00
FGL-4 operational code: 3.00
AGL-2 operational code: 3.00
CLK operational code: 3.00
PSC operational code: 2.0
I.E. the only ones which are not 3.00 are those which weren't changed
from earlier releases
|
| 3493.9 | SCHOOL::GIGASWITCH note 695.0 for firmware locations | NPSS::RLEBLANC | | Fri May 10 1996 14:59 | 13 |
|
re: .4
>>> 1. BLD 3.0 of GIGAswitch firmware is temporarily
>>> unavailable because some bugs and compatibility
>>> problems with CISCO.
Just for the record, this has been resolved with BL3.01 of FGL2
and FGL4 linecard firmware.
Check out notesfile SCHOOL::GIGASWITCH and note 695.0 for gory
details where to get latest firmware.
|