[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 |
4335.0. "Enabling Traps and counter problems." by BIGUN::WULFF () Tue Jan 05 1993 01:37
I need some help please to fix these problems thanks.
1. I don't seem to be able configure the trap address table using SNMP. How do
I do it?
2. When is trap support going to be available for the bridges for link down/up?
We have been short listed for a tender worth anything from $A2M to $A4M and
they would like to trap on link down/up messages.
2. As can be seen, from the text below, when accessing a Decbridge 520 there
are problems with getting the bridge status information and some of the
counters are incorrect eg
Device Frames Lost = 7730954240 Frames
Device Frames Lost = 7730954240 Frames
Frame Status Error = 4294967296 = ( 2 to the power 32 )
Frame Alignment Error = 4294967296 Send Failure = 0
IP Datagrams Fragmented = 4294967296 Datagrams
IP Datagrams Discarded No Fragment = 4294967296 Datagrams
IP Datagrams Discarded Illegal Header Length = 4294967296 Datagrams
IP Datagrams Discarded Illegal Size = 4294967296 Datagrams
from other notes I noticed that other people have had problems but have not
been able to find the solution.
Bridge LOCAL_NS:.521
AT 31-DEC-1992 12:42:03 All Attributes
Name = LOCAL_NS:.521
Address = { 08-00-2B-28-D3-84,
08-00-2B-68-D3-84 }
The requested operation cannot be completed
MCC Routine Error = %MCC-W-ILVINVVAL, ILV detected
invalid value
Counter Creation Time = 31-DEC-1992 12:39:12.79
Seconds Operating = 172 Seconds
Management Resets = 0
Powerups = 4
Device Frames Lost = 7730954240 Frames
Spanning Tree Mode Changes = 1
Invalid Passwords = 0
Unsolicited Resets = 0
ID = %X08002B28D384
Hardware Type = DEFEB DECbridge 520
Software Version = "V1.2B"
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 Seconds
No Frame Interval = 300 Seconds
Hello Interval = 1 Seconds
Listen Time = 15 Seconds
Forwarding Delay = 30 Seconds
Last Load Host = AA-00-04-00-0B-ED
Reset Defaults Switch = False
LB100 Spanning Tree Compatibility = Auto-Select
LB100 Spanning Tree Version = V0.2.0
LB100 Poll Time = 300 Seconds
LB100 Response Timeout = 15 Seconds
IEEE802 Spanning Tree Version = V0.0.0
Update Switch = False
IP Fragmentation Switch = True
NTP Table = { 80-F3 }
IP Address = 140.230.2.3
Trap Address Table = { 204.204.240.240,
240.240.170.170,
170.170.204.204,
204.204.240.240,
240.240.170.170 }
Device Configuration = ( (
FRU Type = AP Card,
FRU State = Working,
FRU ID = N/A,
FRU Revision = Revision 8 ),
(
FRU Type = Single NI Card,
FRU State = Working,
FRU ID = N/A,
FRU Revision = Revision 0 ),
(
FRU Type = FI Card,
FRU State = Working,
FRU ID = N/A,
FRU Revision = Revision 8 ),
(
FRU Type = QM Card,
FRU State = Working,
FRU ID = N/A,
FRU Revision = Revision 0 ),
(
FRU Type = Fan,
FRU State = Working,
FRU ID = N/A,
FRU Revision = Revision 0 ) )
Device Configuration Error Condition = False
Location = -- Attribute Not Available
Implementation Desc = -- Attribute Not Available
Responsible Person = -- Attribute Not Available
Phone Number = -- Attribute Not Available
MAIL Account = -- Attribute Not Available
Remarks = -- Attribute Not Available
Text File = -- Attribute Not Available
Bridge LOCAL_NS:.521 LINE 1
AT 31-DEC-1992 12:43:04 All Attributes
Port Number = 1
Port Module State = Forwarding
Port Broken Reason = None
Designated Bridge ID = 08-00-2B-28-69-72
Designated Bridge Priority = 128
Designated Port Number = 1
Designated Root ID = 08-00-2B-0F-35-61
Designated Root Priority = 110
Designated Root Age = 0 Seconds
Root Path Cost = 2125
Bad Hellos = 0
Forward Delay Timer = 240 Seconds
Possible Loop Flag = False
Topology Change Acknowledge Flag = False
Negotiated TRT = 7.9872 ms
Upstream Neighbor Address = 08-00-2B-28-69-72
UNA Timed Out = False
Link State = On Ring Running
Duplicate Address Condition = Absent
Ring Purger State = Non-purger
Claim Token Yield = False
Ring Error Reason = No Reason
Old Upstream Neighbor Address = 00-00-00-00-00-00
Downstream Neighbor Address = 08-00-2B-25-CC-49
Old Downstream Neighbor Address = 00-00-00-00-00-00
Counter Creation Time = 31-DEC-1992 12:39:12.89
Port Restarts = 0
Total Frames Received = 11200631710 Frames
Total Frames Sent = 109 Frames
Device Frames Received = 150 Frames
Device Bytes Received = 10181 Bytes
Device Frames Sent = 79 Frames
Device Bytes Sent = 34122 Bytes
Invalid Device Messages = 0 Frames
Invalid Device Bytes = 0 Bytes
Device Frames Lost = 7730954240 Frames
Multicast Frames Received = 0 Frames
Multicast Frames Sent = 28 Frames
Multicast Bytes Sent = 2108 Bytes
Multicast Device Frames Received = 0 Frames
Multicast Device Frames Sent = 28 Frames
Multicast Device Bytes Received = 0 Bytes
Multicast Device Bytes Sent = 2108 Bytes
Multicast Frames Filtered = 0 Frames
Multicast Source Frames Received = 0 Frames
Bad Frames Received = 23479189504 Frames
Transmit Frames Lost = 4294967296 Frames
Receive Frames Lost = 2863333376 Frames
Lifetime Exceeded Frames = 4294967296 Frames
Frames Filtered = 4042326022 Frames
Frames Addressed Filtered = 4042326022 Frames
Bytes Addressed Filtered = 0 Bytes
Receive Overruns = 0 Frames
Oversize Frames = 7730954240 Frames
Bad Hellos Limit Exceeded = 0
Unknown Destination Addresses Received = 0
Transmit Error Frames = 0 Frames
Forwarding State Entered = 1
Frame Count = 44079620 Frames
Error Count = 0
Lost Count = 0
Ring Initialization Received = 0
Ring Initialization Initiated = 0
Ring Beaconing Initiated = 0
Duplicate Address Test Failed = 0
Duplicate Token Detected = 0
Traces Initiated = 0
Traces Received = 0
Frame Status Error = 4294967296
Frame Alignment Error = 4294967296
Ring Purger Error = 0
Unprocessed Error Packets = 2863333376
Bridge Strip Error = 0
Send Failure = 0
IP Datagrams Fragmented = 4294967296 Datagrams
IP Datagrams Discarded No Fragment = 4294967296 Datagrams
IP Datagrams Discarded Illegal Header Length = 4294967296 Datagrams
IP Datagrams Discarded Illegal Size = 4294967296 Datagrams
Line Speed = 100000000 bps
Port Address = 08-00-2B-28-D3-84
Port ID = "1�"
Port Cost = 10
Datalink Type = FDDI Ring
Disable Switch = False
Management Sets Allowed Switch = True
Maximum TRT = 173.015 ms
Requested TRT = 7.9872 ms
Valid Transmission Time = 2.62144 ms
Station Type = Dual Attachment Station
Frame Strip Mode = Frame Content Independent
SMT Version ID = 1
SMT Resource Index = 3
SMT Station ID = %X000008002B28D384
Datalink Version = V1.0.0
SMT Maximum Version ID = 1
SMT Minimum Version ID = 1
Ring Purger Enable Flag = True
Optical Bypass Present = No
I-Max Expiration = 40 ms
Optical Bypass Insert Policy = True
Entity Coordination Management State = In
Bridge LOCAL_NS:.521 LINE 2
AT 31-DEC-1992 12:43:48 All Attributes
Port Number = 2
Port Module State = Forwarding
Port Broken Reason = None
Physical Medium Type = Standard AUI interface
Designated Bridge ID = 08-00-2B-28-D3-84
Designated Bridge Priority = 128
Designated Port Number = 2
Designated Root ID = 08-00-2B-0F-35-61
Designated Root Priority = 110
Designated Root Age = 0 Seconds
Root Path Cost = 2135
Bad Hellos = 0
Forward Delay Timer = 240 Seconds
Possible Loop Flag = False
Topology Change Acknowledge Flag = False
Counter Creation Time = 31-DEC-1992 12:39:12.66
Port Restarts = 1
Total Frames Received = 0 Frames
Total Bytes Received = 0 Bytes
Total Frames Sent = 6178 Frames
Total Bytes Sent = 853834 Bytes
Device Frames Received = 0 Frames
Device Bytes Received = 0 Bytes
Device Frames Sent = 0 Frames
Device Bytes Sent = 0 Bytes
Invalid Device Messages = 0 Frames
Invalid Device Bytes = 0 Bytes
Device Frames Lost = 0 Frames
Multicast Frames Received = 0 Frames
Multicast Bytes Received = 0 Bytes
Multicast Frames Sent = 5904 Frames
Multicast Bytes Sent = 832832 Bytes
Multicast Device Frames Received = 0 Frames
Multicast Device Frames Sent = 219 Frames
Multicast Device Bytes Received = 0 Bytes
Multicast Device Bytes Sent = 14049 Bytes
Multicast Frames Filtered = 0 Frames
Multicast Source Frames Received = 0 Frames
Bad Frames Received = 0 Frames
Bad Bytes Received = 0 Bytes
Transmit Frames Lost = 2863333376 Frames
Receive Frames Lost = 0 Frames
Lifetime Exceeded Frames = 4294967296 Frames
Frames Filtered = 0 Frames
Bytes Filtered = 187650557136076 Bytes
Frames Addressed Filtered = 0 Frames
Bytes Addressed Filtered = 0 Bytes
Receive Overruns = 0 Frames
Oversize Frames = 0 Frames
Bad Hellos Limit Exceeded = 0
Collision Presence Test Failed = 2863320793
Transmit Multiple Collisions = 0
Collision Limit Exceeded = 0
Unknown Destination Addresses Received = 0
Transmit Error Frames = 0 Frames
Transmit Error Bytes = 0 Bytes
Framing Errors = 0
Carrier Lost = 0
Forwarding State Entered = 1
Length Error = 4294967296
Line Speed = 10000000 bps
Port Address = 08-00-2B-68-D3-84
Port ID = "2�"
Port Cost = 10
Datalink Type = IEEE 802.3 CSMA/CD
Disable Switch = False
Management Sets Allowed Switch = True
Collision Presence Test Switch = False
Datalink Version = V1.0.0
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 4335.1 | Some answers to your problems | QUIVER::HAROKOPUS | | Wed Jan 06 1993 16:33 | 146 |
| From: QUIVER::WALTER "Dave Walter TAY2-2/B4 227-3809"
To: TOOK::S_KO, BIGUN::WULFF
CC: WALTER,HAROKOPUS,MIKE
Subj: RE: More DECbridge questions involving trap adresses and
counters.
I am commenting on the note written by BIGUN::WULFF in the MCC notes
conference. I can provide answers for some questions, and others need
more
investigation.
> <<< NOTED::DISK$NOTES4:[NOTES$LIBRARY_4OF5]MCC.NOTE;3 >>>
> -< DECmcc Developers Conference - DIGITAL Internal Use Only
>-
>
==============================================================================
==
> Note 4335.0 Enabling Traps and counter problems.
No
> replies
> BIGUN::WULFF 286 lines
5-JAN-1993
> 01:37
>
------------------------------------------------------------------------------
--
> I need some help please to fix these problems thanks.
>
> 1. I don't seem to be able configure the trap address table using
SNMP. How do
> I do it?
I have appended to this note a description of how to manage trap
addresses
using DECmcc SNMP. Please note that you must have the DEC vendor mib
loaded
into mcc or else it won't recognize the objects.
> 2. When is trap support going to be available for the bridges for
link down/up
?
> We have been short listed for a tender worth anything from $A2M to
$A4M and
> they would like to trap on link down/up messages.
There are no plans to implement link up/down traps on the DECbridge
5xx/6xx.
The only traps currently supported are cold start and authentication
failure.
> 2. As can be seen, from the text below, when accessing a Decbridge
520 there
> are problems with getting the bridge status information and some
of the
> counters are incorrect eg
>
> Device Frames Lost = 7730954240 Frames
> Device Frames Lost = 7730954240 Frames
> Frame Status Error = 4294967296 = ( 2 to
the power 3
2
> )
> Frame Alignment Error = 4294967296
> Send Failure = 0
> IP Datagrams Fragmented = 4294967296 Datagrams
> IP Datagrams Discarded No Fragment = 4294967296 Datagrams
> IP Datagrams Discarded Illegal Header Length = 4294967296 Datagrams
> IP Datagrams Discarded Illegal Size = 4294967296 Datagrams
[... more data not copied here...]
I don't know what the cause of this behavior is. I will try to
reproduce it
in the lab by this Friday. If it can't be reproduced, I will need more
information from the customer site in order to diagnose the problem.
Regards,
Dave Walter
PROCEDURE FOR MANAGING TRAP ADDRESSES ON BRIDGE USING MCC
---------------------------------------------------------
The following commands and responses from MCC illustrate the method to
manage Trap Addresses on the bridge. The IP Address of the test bridge
is 16.21.16.128, and it's Read/Write Community string is it's hardware
address. It is assumed that the SNMP AM module and the DEC vendor mib
have been loaded in MCC.
**************************************************
** Add new address 1.2.3.4 to Trap Table **
**************************************************
MCC> set snmp 16.21.16.128 dec ema eauth1 eauthtrapusertable 1.2.3.4 -
_MCC> eauthtrapuseraddr 1.2.3.4, by password "08002b2ffd7d"
SNMP 16.21.16.128 dec ema eauth1 eauthTrapUserTable 1.2.3.4
AT 5-JAN-1993 16:12:29 Identifiers
Examination of Attributes Shows
eauthTrapUserAddr = 1.2.3.4
**************************************************
** Show all addresses in Trap Table **
**************************************************
MCC> show snmp 16.21.16.128 dec ema eauth1 eauthtrapusertable * -
_MCC> eauthtrapuseraddr
SNMP 16.21.16.128 dec ema eauth1 eauthTrapUserTable 1.2.3.4
AT 5-JAN-1993 16:53:48 Identifiers
eauthTrapUserAddr = 1.2.3.4
SNMP 16.21.16.128 dec ema eauth1 eauthTrapUserTable 16.21.16.116
AT 5-JAN-1993 16:53:49 Identifiers
eauthTrapUserAddr = 16.21.16.116
**************************************************
** Delete address 1.2.3.4 from Trap Table **
**************************************************
MCC> set snmp 16.21.16.128 dec ema eauth1 eauthtrapusertable 1.2.3.4 -
_MCC> eauthtrapuserstatus invalid, by password "08002b2ffd7d"
SNMP 16.21.16.128 dec ema eauth1 eauthTrapUserTable 1.2.3.4
AT 5-JAN-1993 17:03:52 Characteristics
Examination of Attributes Shows
eauthTrapUserStatus = invalid
**************************************************
** Show all addresses in Trap Table **
**************************************************
MCC> show snmp 16.21.16.128 dec ema eauth1 eauthtrapusertable * -
_MCC> eauthtrapuseraddr
SNMP 16.21.16.128 dec ema eauth1 eauthTrapUserTable 16.21.16.116
AT 5-JAN-1993 17:04:24 Identifiers
eauthTrapUserAddr = 16.21.16.116
|
| 4335.2 | Counter problems fixed | QUIVER::WALTER | | Wed Jan 20 1993 17:20 | 7 |
| Re: Counter problems on DECbridge 500 series
Ken Rauhala found some initialization errors in the 500 code that
caused incorrect counter values. He has fixed those errors, and we
are now verifying the fix in the V1.3 Field Test code.
|
| 4335.3 | software and firmware available?? | GIDDAY::DRANSFIELD | Mike Dransfield, Sydney RSSG | Tue Jan 26 1993 22:45 | 7 |
| Can we get hold of the bridge AM for T1.3 MCC and firmware 1.3 for the
DECbridge 5xx?
We have a couple of DECbridges next week that we would like to make
sure do the things that didn't work last week at the customer test....
Thanks,
Mike
|
| 4335.4 | Not yet ready | TOOK::MINTZ | Erik Mintz | Tue Jan 26 1993 23:06 | 4 |
| The bridge AM for T1.3 is not yet available.
For firmware, you probably need to talk to the bridge developers.
-- Erik
|
| 4335.5 | Field Test version can be arranged | QUIVER::WALTER | | Wed Jan 27 1993 12:40 | 7 |
| V1.3 of the DECbridge firmware is currently in field test. It should
be released in the March timeframe. If you would like to use the field
test version internally, or are trying to solve a customer problem,
contact me through mail.
Dave Walter
|