| 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 |
A customer of ours had an SCP module ver. 2.2 go bad so we replaced it
with a new module. The module we put in was ver 3.1. When this new SCP
module was placed in the GIGAswitch it refused to recognize the ver 2.x
line cards. Since it refused to recognize the line cards we were unable
to update/downgrade the firmware to 2.2 as their was no inline path to
the SCP.
We were left with a nonfunctional GIGAswitch. This switch has been down
for three days.
This GIGAswitch only has one SCP so we could not put it in as a backup
SCP and then load the firmware. So, we thought we would be tricky and
put a new version line card in...the version we got in was version 1.0!
Suffice it to say, we are now well and truly screwed.
This one situation has brought to light a number of issues.
1) There is a definite and very nasty compatibility issue between
modules in the GIGAswitch. Anyone else run into this? Anyone know a way
around this?
2) Because of 1 above, we have a stocking issue. What version of
GIGAswitch modules do we need to keep in stock? How do we tell the
firmware version of the modules that we are ordering in? Do we need to
purge our local stock rooms of older revision modules?
3) With the DECHUB 900 modules, you can upgrade firmware through the
OBM...what about the GIGAswitch?
Any light that you can shed on this issue would be appreciated.
Regards,
Ron Ryan
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 974.1 | NPSS::MDLYONS | Michael D. Lyons DTN 226-6943 | Thu Apr 24 1997 13:58 | 7 | |
The firmware mismatch issue is documented in the release notes.
The work around is to temporarily turn off hunt group support in
OBM, upgrade the line cards to the proper revision and then reenable
hunt group support.
MDL
| |||||
| 974.2 | How to disable hunt group support in OBM (3.1) | NPSS::MDLYONS | Michael D. Lyons DTN 226-6943 | Thu Apr 24 1997 14:05 | 45 |
Main Menu
System 1. Show box configuration
2. Show/set slot configuration
3. Show/set system time
4. Clear management memory
5. Reboot menu
Port 6. Show LAN address assignments
7. Show/set privileged and bootserver ports
8. Show/set delayed ports
9. IP Menu
Bridge 10. Bridge menu
MIBs 11. MIB viewer menu
Extensions 12. Extended options menu
OBM 13. OBM menu
14. End OBM session
Choice: 12
Extended Options Menu 1. Statistics and counters menu
2. Debug options menu
3. Hunt group menu
4. Management memory deletions
5. SCP revision history
6. Return to main menu
Choice: 3
Hunt Group Menu 1. Hunt group configuration menu
2. Set/disable hunt group support
3. Return to previous menu
Choice: 2
Hunt groups are currently supported
Do you want to change the configuration to disable hunt groups ?
WARNING: If you answer yes, the switch will REBOOT.
Do you want to do this? (yes/no): yes
| |||||
| 974.3 | Will 3.1 SCP run with ver. 2 FGL? | KAOFS::R_RYAN | I used to be a coyote but Im ok nowoooo! | Thu Apr 24 1997 16:18 | 9 |
Mike,
My apologies for missing the entry on hunt groups in the release notes.
I have passed the information on to the customer. Though it is not
recommended that a version 3.1 SCP run with the version 2 line cards,
can this be done for a week or so?
The customer would like to get the GIGAswitch up and running ASAP and
schedule the downtime for the upgrades for next week.
Thanks,
Ron Ryan
| |||||
| 974.4 | NPSS::MDLYONS | Michael D. Lyons DTN 226-6943 | Thu Apr 24 1997 17:38 | 7 | |
It may run OK. It's probably even likely that it'll run OK. We
don't know of any reason why it wouldn't run OK, but no testing has
been done.
...good luck
MDL
| |||||