[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
|
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
5846.0. "Bridge in Indeterminate State problems !!!" by SMAC10::STEPHENSON () Thu Jan 27 1994 05:51
I get the an "indeterminate" severity message using the following alarm
on a DECbridge 510 (10/100 bridge)
(CHANGE_OF (BRIDGE bribr2 DEVICE STATE, *,*), AT EVERY=00:01:00.00)
Event Type QualityofServiceAlarm
Significance True
Information The requested operation cannot be
completed<EOS>%MCC-W-ILVINVVAL, ILV
detected invalid value
Significance True
Information (CHANGE_OF (BRIDGE bribr2 DEVICE
STATE, *,*), AT EVERY=00:01:00.00)
Managed Object Bridge LOCAL_NS:.bribr2
Percieved Severity Indeterminate
Additional Text Bridge has changed state
When I use DECmcc to interrogate the bridge a SHOW STATUS reveals the
same problem....
Any ideas what is wrong with the bridge ?
SHOW CHARACTERISTICS reveals
ID %X08002B29955E
H/W type DEFEB DECbridge 510
S/w version V1.1
ROM Version V2.9.0
Port Count 2
Root Priority 128
Bad Hello Limit 15
Bad Hello Reset Interval 5
Port Test Passed Threshold 10
Port Test Interval 60
No Frame Interval 300
Hello Interval 1
Listen Time 15
Forwarding Delay 30
Reset Defaults Switch False
LB100 Spanning Tree Compatibility Auto-Select
LB100 Spanning Tree Version V0.2.0
LB100 Poll Time 300
LB100 Response Time 15
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 5846.1 | | NPSS::WADE | Network Systems Support | Fri Jan 28 1994 08:49 | 4 |
| I'm pretty sure that this was a problem that was fixed in 1.3 of the
DECbridge firmware.
|
| 5846.2 | Upgrade to V1.3 | BIKINI::KRAUSE | European NewProductEngineer for MCC | Fri Jan 28 1994 09:51 | 7 |
| >S/w version V1.1
I think it's about time to upgrade the bridge to V1.3. I don't have any
more V1.1 hanging around to check, but V1.3 seems to work quite well
with MCC.
*Robert
|