| Title: | GIGAswitch |
| Notice: | GIGAswitch/FDDI Jan 97 BL3.1 914.0 documentation 412.1 ion 412.1 |
| Moderator: | NPSS::MDLYONS |
| Created: | Wed Jul 29 1992 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 995 |
| Total number of notes: | 4519 |
At a big site (big in amounts of data) a couple of FGL-4 cards will reset intermittent. The results can be imagined..... I know they are running a bit (?) behind in firmware (2.0 and 2.2) but it all worked for 6 - 9 months without (serious) problems. The switch has about 20 ports in total. Most FGL-4's and some FGL-2's. FGL-4's are mainly used to connect high-performance systems ala Sun's. Customer claims that these systems are able to really load their 'ring'. All in all the switch is heavy loaded. Now the big question is: under what conditions will the card reset? How can we check on what happened after the reset? Can IP packet reassembly be a cause? Customer did change MTU sizes on some systems from 1500 to 4500 lately. Any help would be appriciated, Ton. [Posted by WWW Notes gateway]
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 946.1 | NPSS::MDLYONS | Michael D. Lyons DTN 226-6943 | Mon Mar 10 1997 12:09 | 9 | |
We can't "guess" your problem without information.
The release notes for the (at least two) upgrades which they lack
describe which problems the releases fix.
...but, do the smart thing and upgrade the firmware first.
MDL
| |||||
| 946.2 | NPSS::MDLYONS | Michael D. Lyons DTN 226-6943 | Mon Mar 10 1997 12:13 | 10 | |
P.S. IP packet reassembly does not happen on the GIGAswitch/FDDI system
today except for those frames directed at the GIGAswitch/FDDI system itself
which require reassembly. Frames directed to other systems are not
reassembled on the GIGAswitch/FDDI system.
There have been problems (IN THE PAST - read the release notes) which
involved sending frames requiring reassembly to the GIGAswitch/FDDI
system itself. As I've said many times before - upgrade the firmware
to current levels first. I don't care how well the firmware ran in the
past.
| |||||