[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference netcad::hub_mgnt

Title:DEChub/HUBwatch/PROBEwatch CONFERENCE
Notice:Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7
Moderator:NETCAD::COLELLADT
Created:Wed Nov 13 1991
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:4455
Total number of notes:16761

4336.0. "traps on FDDI link failure" by NETRIX::"[email protected]" (Brendan Docherty) Fri Apr 04 1997 12:11

Hi,

I have a customer who is requesting information regarding SNMP traps when his
FFDI liks fail.

The set-up is a GIGAswitch/FDDI with Full duplex connections to 900EF in
900Multichassis. 
The 900EFs are dual-homed to seperate line cards in the GIGAswitch.

When an switched Ethernet connection link fails, a trap is sent to the NMS. 
But not if either of the FDDI connections are broken.

Presumably the back-up link takes over when the Active link fails - and
therefore no linkdown trap is sent.
(Until the back-up link also fails !!!)

The customer is clearly concerned - as he'd like a trap telling him that his
first link had failed.

Any suggestions how this could be done (RMON ?)

The NMS is running HPopenview.

Thanks in advance

Brendan Docherty
NSIS Livingston

GIGAswitch v3.1
900EF v1.7
[Posted by WWW Notes gateway]
T.RTitleUserPersonal
Name		DateLines
4336.1Try alarming on "fddimibPORTConnectState".NETCAD::GALLAGHERFri Apr 04 1997 15:4072
|Any suggestions how this could be done (RMON ?)

I might be able to get you part of the way there.

The DECconcentrator 900 series products support a "port trap" whereby
an SNMP trap is sent whenever the value of the FDDI MIB (rfc1512)
object "fddimibPORTConnectState" changes.  (Definition attached.)
Port traps are sent when a dual-homed port failover happens, but I
don't recall the state transitions that occur.

Since the DECswitch 900EFs support RMON Alarms and Events, you could
set an alarm on "fddimibPORTConnectState" in order to get rising
and falling events.  By playing with it a little bit you can probably
differentiate rising and falling events into something meaningful - 
for example, maybe a rising event means that the connectState went to
'standby'.

Good luck.  Please post the results if you get this to work.
 
					-Shawn
------------
rfc1512:
          fddimibPORTConnectState OBJECT-TYPE
              SYNTAX  INTEGER {
                          disabled(1),
                          connecting(2),
                          standby(3),
                          active(4)
                      }
              ACCESS  read-only
              STATUS  mandatory
              DESCRIPTION
                      "An indication of the connect state of this PORT
                      and is equal to the value of Connect_State (refer
                      to ANSI 9.4.1)"
              REFERENCE
                      "ANSI { fddiPORT 61 }"
              ::= { fddimibPORTEntry 20 }

 
rfc1285:
          snmpFddiPORTConnectState OBJECT-TYPE
              SYNTAX  INTEGER {
                          disabled(1),
                          connecting(2),
                          standby(3),
                          active(4)
                      }
              ACCESS  read-only
              STATUS  mandatory
              DESCRIPTION
                      "An indication of the connect state of this PORT.
                      Basically, this gives a higher level view of the
                      state of the connection by grouping PCM states and
                      the PC-Withhold flag state.  The supported values
                      and their corresponding PCM states and PC-Withhold
                      condition, when relevant, are:

                        disabled: (PC0:Off, PC9:Maint)

                      connecting: (PC1(Break) || PC3 (Connect) || PC4
                      (Next)                 || PC5 (Signal) || PC6
                      (Join) || PC7 (Verify))             &&
                      (PC_Withhold = None)

                         standby: (NOT PC_Withhold == None)

                          active: (PC2:Trace || PC8:Active) "
              REFERENCE
                      "ANSI { fddiPORT 61 }"
              ::= { snmpFddiPORTEntry 20 }