| 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 |
There are 3 (maybe more) ways to build redundant links between
G/S's.
a) Reliability groups - DAS to M ports
b) Hunt groups
c) Blocking STP path(s).
a) Will fail over in about 2 seconds, c) will take 45 secs default.
Can someone describe how and how long b) works/takes.
Observations:-
1. On G/S the red/green button reflects the eFDXEnable/eFDXOp
combination. If both are true OR both are false the butten is GREEN.
If they are differnet the butten is RED.
For more info use the console menus to check out eFDXState.n.n
(n=port number eg Card 3 port 1 = port 5).
1=idle (not fdx)
2=Requesting full duplex
3=fdx confirm
4=fdx Operating .
2. The Gigaswitch does not automatically adjust the STP line cost for
hunt groups. In redundant configurations you may find that the big
hunt group pipe is not being used. Manually adjust the cost to get
the hunt group into STP forwarding.
3. If, after enabling a hunt group, you lose IP connectivity. Go to the
console and enable an IP address on the new hunt group port (eg
99.37).
4. Current factory default on DEcswitch 900 is eFDXenable false. I
could find no button using MCM V5 or V6 to enable fdx on the 900.
Need to use MIB browser.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 932.1 | NPSS::MDLYONS | Michael D. Lyons DTN 226-6943 | Mon Feb 17 1997 20:57 | 59 | |
> There are 3 (maybe more) ways to build redundant links between
> G/S's.
> a) Reliability groups - DAS to M ports
> b) Hunt groups
> c) Blocking STP path(s).
>
> a) Will fail over in about 2 seconds, c) will take 45 secs default.
>
> Can someone describe how and how long b) works/takes.
See 527.7 and 527.8 (keyword hunt-group)
>
> Observations:-
>
> 1. On G/S the red/green button reflects the eFDXEnable/eFDXOp
> combination. If both are true OR both are false the butten is GREEN.
> If they are differnet the butten is RED.
>
> For more info use the console menus to check out eFDXState.n.n
> (n=port number eg Card 3 port 1 = port 5).
>
> 1=idle (not fdx)
> 2=Requesting full duplex
> 3=fdx confirm
> 4=fdx Operating .
The "red/green button"? Perhaps you mean the screen in Multichassis
Manager. MCM issues are typically covered in the KALI::HUB_MGNT notes
conference. c.f. note 4010.* where this topic is discussed.
>
> 2. The Gigaswitch does not automatically adjust the STP line cost for
> hunt groups. In redundant configurations you may find that the big
> hunt group pipe is not being used. Manually adjust the cost to get
> the hunt group into STP forwarding.
See note 820.*
>
> 3. If, after enabling a hunt group, you lose IP connectivity. Go to the
> console and enable an IP address on the new hunt group port (eg
> 99.37).
>
... 776.4 keyword can't-ping ...and yes, it would have been helpful to
have had this in the release notes.
> 4. Current factory default on DEcswitch 900 is eFDXenable false. I
> could find no button using MCM V5 or V6 to enable fdx on the 900.
> Need to use MIB browser.
>
...Perhaps this would get more attention in KALI::HUB_MGNT
MDL
| |||||