Larry,

If you're out there - and I hope you still are - hope this information is
helpful.  James I hope you're out there too.    I agree with many of the
views already expressed....I too want to feel free to ask questions, we all
make mistakes and learn, and I appreciate the tremendous knowledge that
everyone, and James in particular, has generously shared.

I do not consider myself a Cisco expert, but will try to offer some
additional information.

The frame relay DLCI status change trap is part of rfc1315-FRAME MIB.  This
is a branch under mib2 (mib-2.transmission.frame-relay); it is not a Cisco
private mib.  My limited hands-on experience with this trap is on Cisco
equipment and Netview for AIX .

The trap is reporting a changes in the status of a single frame relay
virtual circuit identified by the DLCI, not the physical interface on the
router itself.  In a multi-point configuration, there will be multiple
virtual circuits defined for a particular serial interface.  The serial
interface may be fine, but a single (or multiple) virtual circuit may be
inactive or invalid.

The Index and State variables are defined in the mib.  I'm not sure what is
included in the NT distribution.  From the mib distributed with the AIX
version:

frCircuitState OBJECT-TYPE
             SYNTAX   INTEGER {
                         invalid (1),
                         active (2),
                         inactive (3)
                      }
             ACCESS   read-write
             STATUS   mandatory
             DESCRIPTION
                "Indicates whether the particular virtual  cir-
                cuit  is operational.  In the absence of a Data
                Link Connection Management  Interface,  virtual
                circuit  entries  (rows) may be created by set-
                ting virtual  circuit  state  to  'active',  or
                deleted by changing Circuit state to 'invalid'.
                Whether or not the row actually  disappears  is
                left  to the implementation, so this object may
                actually read as 'invalid' for  some  arbitrary
                length  of  time.   It is also legal to set the
                state of a virtual  circuit  to  'inactive'  to
                temporarily disable a given circuit."
            DEFVAL { active }

frCircuitIfIndex OBJECT-TYPE
             SYNTAX   Index
             ACCESS   read-only
             STATUS   mandatory
             DESCRIPTION
                "The ifIndex Value of the ifEntry this  virtual
                circuit is layered onto."
            ::= { frCircuitEntry 1 }

The index value isn't too meaningful in raw form.  For example index 5 may
refer to interface "serial 1" or "serial 2" depending on the order cards
have been installed in the router.  You can do an snmp query to the device
using this index value to obtain the  interface name, which is much more
meaningful to someone reading an error message.  For example on router
RTR1.xxx.com, index 3:

snmpget RTR1.xxx.com interfaces.ifTable.ifEntry.ifDescr.3

Hope this helps,
Karin

-----Original Message-----
From: Leslie Clark <lclark AT US.IBM DOT COM>
To: NV-L AT UCSBVM.UCSB DOT EDU <NV-L AT UCSBVM.UCSB DOT EDU>
Date: Monday, November 08, 1999 9:13 PM
Subject: Re: Netview for NT (meaning of trap)


>Come now, boys, shake and make up.
>
>A cisco expert might chime in here, but in the meantime....
>
>Larry, where I look when I want to try to figure out what these traps mean
>(guessing is often faster than finding the appropriate vendor
>documentation)
>is the MIB Browser. Those mib variables will be found under the Private
>branch somewhere, and when you get down to the MIB variables mentioned,
>the descriptions will probably help. Certainly the enumeration of the
>states
>will be defined. Since the names of the variables show up in the traps,
>then
>I believe you will find that the mibs have already been loaded. On Unix I
>would go to the mibs directory (/usr/OV/snmp-mibs) and grep on the variable
>name in all files, and see which file it is in, and just edit the file and
>read it.
>I don't know how to do that on NT, though.
>
>Cordially,
>
>Leslie A. Clark
>IBM Global Services - Systems Mgmt & Networking
>
>---------------------------------------------------------------------------
---------------------------------------------------------------
>
>NetView for NT
>
>Would this trap indicate a physical problem on the serial interface of the
>router
>or is it an LMI status request from the router to the DLCI?
>It makes me think it is the router serial interface since it's DTE.
>Where can I reference the meanings of the Index and State?
>
>TRAP:
>frDLCIStatusChange:trap received from enterprise frame-relay-dte
>with 3 arguments:  frCircuitIfIndex=3;  frCircuitDlci=100;
>frCircuitState=3
>
>Thanks,
>
>Larry
>