| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 914.1 | bug Free ? | CLPR01::PEYRACHE | Jean-Yves Peyrache Country Support Group France | Mon Jan 27 1997 08:11 | 5 |
|
Are the V3.1 include all fixes of V3.0 ?
JYP
|
| 914.2 | | NPSS::MDLYONS | Michael D. Lyons DTN 226-6943 | Mon Jan 27 1997 10:00 | 13 |
| We decided to add some new bugs, but the old bugs are fixed.
Seriously, this is covered in the release notes. In general, the
major releases of the GIGAswitch/FDDI System represent the current
level of firmware at the time of the release, including bug fixes.
Known problems which aren't fixed are discussed in the release notes.
Any problems which are discovered after the release are naturally
enough not in the release notes.
To my knowledge, the only expected change which is not in the BL3.1
release is non-zero vpi support in AGLs.
MDL
|
| 914.3 | debugger tools | PRSSOS::PEYRACHE | Jean-Yves Peyrache Country Support Group France | Tue Jan 28 1997 07:22 | 4 |
|
>> We Decided To add some new bugs
don't worry customers generally find them rapidly...
|
| 914.4 | Bug fixes and known problems with BL3.1 | NPSS::MDLYONS | Michael D. Lyons DTN 226-6943 | Fri Feb 21 1997 11:28 | 50 |
| This is a list of the bugs fixed since the GIGAswitch/FDDI BL3.1 release.
Each new release also contains the fixes in the prior bug fix releases. In
general, the bug fix releases are not put in the general distribution areas,
but are given out to those customers which encounter the bugs. For bugs which
have significant impact, the releases are placed in the general distribution
areas on gatekeeper and the web site.
SCP op BL 3.11
Observed symptom: management access to the GIGAswitch/FDDI system sometimes
ceases on particular ports after some length of time. Actually, it is just
broadcast ARP requests directed to the GIGAswitch/FDDI system which do not get
a response.
This was caused by buffers being lost after reception of certain frames.
FGL-2 and FGL-4 BL 3.??
ifInUcastPkts is sometimes invalid for second port (icc port) on a linecard
MIB counters on port 2 are sometimes invalid due to confusion with the way
the ICC port is treated. (References notes 231.* and 792.*)
Originally fixed in BL3.09, but the fix was inadvertantly left out of the
BL3.1 build for FGLs.
GIGAswitch MIB
Fix typos in MIB object names:
xacInDiscardUnkownDAUCast --> xacInDiscardUnknownDAUCast
xacInDiscardIPForwading --> xacInDiscardIPForwarding
Known verified problems for which fixes do not yet exist:
---------------------------------------------------------
OBM set for eauthTrapUserAddr doesn't work
Known unverified problems:
--------------------------
Multiple IP addresses for a single MAC address confuses the GIGAswitch/FDDI
system (Reference notes 544.* and 265.*)
lineCardFailureTrap doesn't work with Polycenter Netview
Suspected problem with AGLs hanging (Reference notes 924.*)
|
| 914.4 | Bug fixes and known problems with BL3.1 | NPSS::MDLYONS | Michael D. Lyons DTN 226-6943 | Wed Feb 26 1997 10:55 | 50 |
| This is a list of the bugs fixed since the GIGAswitch/FDDI BL3.1 release.
Each new release also contains the fixes in the prior bug fix releases. In
general, the bug fix releases are not put in the general distribution areas,
but are given out to those customers which encounter the bugs. For bugs which
have significant impact, the releases are placed in the general distribution
areas on gatekeeper and the web site.
SCP op BL 3.11
Observed symptom: management access to the GIGAswitch/FDDI system sometimes
ceases on particular ports after some length of time. Actually, it is just
broadcast ARP requests directed to the GIGAswitch/FDDI system which do not get
a response.
This was caused by buffers being lost after reception of certain frames.
AGL-2 and AGL-2+ BL 3.??
ifInUcastPkts is sometimes invalid for second port (icc port) on a linecard
MIB counters on port 2 are sometimes invalid due to confusion with the way
the ICC port is treated. (References GIGAswitch notes 231.* and 792.*)
Originally fixed in BL3.09, but the fix was inadvertantly left out of the
BL3.1 build for AGLs.
GIGAswitch MIB
Fix typos in MIB object names:
xacInDiscardUnkownDAUCast --> xacInDiscardUnknownDAUCast
xacInDiscardIPForwading --> xacInDiscardIPForwarding
Known verified problems for which fixes do not yet exist:
---------------------------------------------------------
OBM set for eauthTrapUserAddr doesn't work
Known unverified problems:
--------------------------
Multiple IP addresses for a single MAC address confuses the GIGAswitch/FDDI
system (Reference GIGAswitch notes 544.* and 265.*)
lineCardFailureTrap doesn't work with Polycenter Netview
Suspected problem with AGLs hanging (Reference GIGAswitch notes 924.*)
|
| 914.4 | Bug fixes for BL3.1 | NPSS::MDLYONS | Michael D. Lyons DTN 226-6943 | Thu Apr 10 1997 12:23 | 60 |
| This is a list of the bugs fixed since the GIGAswitch/FDDI BL3.1 release.
Each new release also contains the fixes in the prior bug fix releases. In
general, the bug fix releases are not put in the general distribution areas,
but are given out to those customers which encounter the bugs. For bugs which
have significant impact, the releases are placed in the general distribution
areas on gatekeeper and the web site.
SCP op BL 3.11
Observed symptom: management access to the GIGAswitch/FDDI system sometimes
ceases on particular ports after some length of time. Actually, it is just
broadcast ARP requests directed to the GIGAswitch/FDDI system which do not get
a response.
This was caused by buffers being lost after reception of certain frames.
SCP op BL3.12
SNMP requests for ports with E3 PMDs did not work due to improper testing for
the type of PMD.
AGL-2 and AGL-2+ BL 3.??
ifInUcastPkts is sometimes invalid for second port (icc port) on a linecard
MIB counters on port 2 are sometimes invalid due to confusion with the way
the ICC port is treated. (References GIGAswitch notes 231.* and 792.*)
Originally fixed in BL3.09, but the fix was inadvertantly left out of the
BL3.1 build for AGLs.
GIGAswitch MIB
Fix typos in MIB object names:
xacInDiscardUnkownDAUCast --> xacInDiscardUnknownDAUCast
xacInDiscardIPForwading --> xacInDiscardIPForwarding
The instance name of "clear_and_lock" in the mgmtMemoryAction MIB object
was changed to be "clearAndLock" to avoid problems with some MIB compilers.
Known verified problems for which fixes do not yet exist:
---------------------------------------------------------
OBM set for eauthTrapUserAddr doesn't work
Known unverified problems:
--------------------------
Multiple IP addresses for a single MAC address confuses the GIGAswitch/FDDI
system (Reference GIGAswitch notes 544.* and 265.*)
lineCardFailureTrap doesn't work with Polycenter Netview
Suspected problem with AGLs hanging (Reference GIGAswitch notes 924.* and
customer MFS Datanet problem)
|
| 914.4 | Bug fix list | NPSS::MDLYONS | Michael D. Lyons DTN 226-6943 | Thu Jun 05 1997 15:09 | 95 |
| This is a list of the bugs fixed since the GIGAswitch/FDDI BL3.1 release.
Each new release also contains the fixes in the prior bug fix releases. In
general, the bug fix releases are not put in the general distribution areas,
but are given out to those customers which encounter the bugs. For bugs which
have significant impact, the releases are placed in the general distribution
areas on gatekeeper and the web site.
SCP op V3.11
Observed symptom: management access to the GIGAswitch/FDDI system sometimes
ceases on particular ports after some length of time. Actually, it is just
broadcast ARP requests directed to the GIGAswitch/FDDI system which do not get
a response.
This was caused by buffers being lost after reception of certain frames.
SCP op V3.12
SNMP requests for ports with E3 PMDs did not work due to improper testing for
the type of PMD.
SCP op V3.13
Add workaround for management memory problem with duplicate filter records.
SCP op Vf.09
Fix "icc: invalid gigaport" SCP panic caused by SNMP GETs during AGL
initialization.
Linecards do not initialize properly sometimes, leaving the ports
inoperative, although no external failures are visible. FGLs in this state all
have their ports in the Off Ring Run state, and the MLA is set to zeroes in DVT
test 23. The Station ID in DVT test 2 shows the correct MAC address.
SCP op (no release yet)
OBM and SNMP hang caused by apparent lost resource lock between OBM Mib
viewer and SNMP.
AGL-2+ BL 3.15
Various problems associated with error recovery and error logging were
fixed.
AGL-2 and AGL-2+ (no release yet)
ifInUcastPkts is sometimes invalid for second port (icc port) on a linecard
MIB counters on port 2 are sometimes invalid due to confusion with the way
the ICC port is treated. (References GIGAswitch notes 231.* and 792.*)
Originally fixed in BL3.09, but the fix was inadvertantly left out of the
BL3.1 build for AGLs.
GIGAswitch MIB
Fix typos in MIB object names:
xacInDiscardUnkownDAUCast --> xacInDiscardUnknownDAUCast
xacInDiscardIPForwading --> xacInDiscardIPForwarding
The instance name of "clear_and_lock" in the mgmtMemoryAction MIB object
was changed to be "clearAndLock" to avoid problems with some MIB compilers.
Known verified problems for which fixes do not yet exist:
---------------------------------------------------------
OBM set for eauthTrapUserAddr doesn't work
Known unverified problems:
--------------------------
Multiple IP addresses for a single MAC address confuses the GIGAswitch/FDDI
system (Reference GIGAswitch notes 544.* and 265.*)
lineCardFailureTrap doesn't work with Polycenter Netview
Suspected problem with AGLs hanging (Reference GIGAswitch notes 924.* and
a separate customer problem)
ifOutOctets clipping on FGL-2s/FGL-4s
|