| Title: | FDDI - The Next Generation |
| Moderator: | NETCAD::STEFANI |
| Created: | Thu Apr 27 1989 |
| Last Modified: | Thu Jun 05 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2259 |
| Total number of notes: | 8590 |
Is Fragmentation Error Checking a settable parameter/attribute in the
DECbridge 620? POLYcenter 300 1.2 ELMS shows this as Disabled in the
bridge characteristics display.
The only reference to this I've seen is in an old DECelms Use
manual from 1990 where it states that it only applies to DECbridge
500s. The description disappeared from subsequent versions of the
DECelms Use manual...
Since the DECbridge 6x0 did not exist at the time thae Use manual
included text on the subject, what's the deal? Is this permanently
disabled in the 6x0?
Phil
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1100.1 | KONING::KONING | Paul Koning, A-13683 | Wed Sep 29 1993 15:16 | 5 | |
I don't know any such parameter; do you mean whether fragmentation can be enabled and disabled? The answer to that is yes... and it's enabled by default. (I know of no reason ever to disable it, by the way...) paul | |||||
| 1100.2 | some speculation | ASDS::LEVY | Wed Sep 29 1993 15:28 | 14 | |
From your entry, Phil, I infer that trying to enable this parameter
fails. I suspect it was never implemented. (In any case, it's not clear
what function it performs.)
>The only reference to this I've seen is in an old DECelms Use
>manual from 1990 where it states that it only applies to DECbridge
>500s. The description disappeared from subsequent versions of the
>DECelms Use manual...
Assuming it does something useful, it should apply to all DECbridge 5xx
and 6xx variants (except the 600). The reference in the DECelms manual
was there to indicate that it didn't apply to LAN Bridges.
Jon
| |||||
| 1100.3 | The "rest of the story". | PFSVAX::MCELWEE | Opponent of Oppression | Thu Sep 30 1993 01:27 | 34 |
Re: .1-
Paul,
It was/is(?) an additional parameter to Fragmentation Enable/Disable,
labeled as desribed in the Note title.
Re: .2-
Jon,
The desription is that it controls whether or not an IP checksum
comparison is done on received messages requiring fragmentation.
I'm curious as it appears in the MSU/ELMS characteristics display,
and also because of possible relationship to the bug fix in DEFCN 3.3
related to unsolicited resets involving large PINGs as mentioned in
another Note.
I've not tried enabling it yet.
We are seeing Unsol. resets on DEFCN 3.1 and 620 bridges 1.2 which
are connected to and/or adjacent to a SUN server. We've already
verified that the SUN O/S 4.1.3 patch mentioned in this conference has
been installed to no avail. The DEFCN and DEFEB show only Ring Inits.
Rcvd.- no traces nor beaconing. I'm also having trouble reading M PHYPORTs
on the DEFCN with MSU/ELMS. All I can access are the A&B ports. I'm
beginning to think we need an analyzer to confirm my suspicion that the
SUN is sending a trace or ? causing the resets.
Sorry to ramble on so much, but I could use some advice. We will be
updating the units to 3.3 and 1.3 soon, but what then if no solution?
Phil
| |||||
| 1100.4 | One item sloved. | PFSVAX::MCELWEE | Opponent of Oppression | Mon Oct 04 1993 12:17 | 9 |
Re: .3 (mine):
> I'm also having trouble reading M PHYPORTs
> on the DEFCN with MSU/ELMS. All I can access are the A&B ports.
This turned out to be incompatible F/W. DEFCN V3.3 was installed
and these ports can now be managed.
Phil
| |||||
| 1100.5 | One item solved. | PFSVAX::MCELWEE | Opponent of Oppression | Mon Oct 04 1993 12:18 | 9 |
Re: .3 (mine):
> I'm also having trouble reading M PHYPORTs
> on the DEFCN with MSU/ELMS. All I can access are the A&B ports.
This turned out to be incompatible F/W. DEFCN V3.3 was installed
and these ports can now be managed.
Phil
| |||||