Hi Jan-Erik,

Those are valid and loaded questions.  As far as the Entity MIB, I assume you 
are talk about the Cisco devices.
See the attachment below.

Thanks.

Charles



CISCO-ZS-MIB  DEFINITIONS ::= BEGIN

IMPORTS
    MODULE-IDENTITY,
    OBJECT-TYPE, 
    NOTIFICATION-TYPE, 
    Integer32
        FROM SNMPv2-SMI
    MODULE-COMPLIANCE, 
    OBJECT-GROUP
        FROM SNMPv2-CONF
    TEXTUAL-CONVENTION, 
    TimeStamp,
    TruthValue
        FROM SNMPv2-TC
    entPhysicalIndex
        FROM ENTITY-MIB
    ciscoMgmt
        FROM CISCO-SMI;


entitySensorMIB MODULE-IDENTITY
        LAST-UPDATED "9812102112Z"
        ORGANIZATION "Cisco Systems, Inc."
        CONTACT-INFO
         "Postal: Cisco Systems, Inc.
             170 West Tasman Drive
             San Jose, CA 95134-1706
             USA

             Tel: +1 408 526 4000

             E-mail: [email protected]"
        DESCRIPTION
            "The CISCO-ENTITY-SENSOR-MIB is used to monitor 
            the values of sensors in the Entity-MIB (RFC 2037) 
            entPhysicalTable."
        ::= { ciscoMgmt 91 }

entitySensorMIBNotifications
        OBJECT IDENTIFIER ::= { entitySensorMIBNotificationPrefix 0 }

entitySensorMIBObjects
        OBJECT IDENTIFIER ::= { entitySensorMIB 1 }

entitySensorMIBNotificationPrefix
        OBJECT IDENTIFIER ::= { entitySensorMIB 2 }

entitySensorMIBConformance
        OBJECT IDENTIFIER ::= { entitySensorMIB 3 }

entSensorThresholdNotification NOTIFICATION-TYPE
    OBJECTS { entSensorThresholdValue, entSensorValue }
    STATUS current
    DESCRIPTION
        "The sensor value crossed the threshold 
        listed in entSensorThresholdTable.

        This notification is generated once each time
        the sensor value crosses the threshold.
        
        The agent implementation guarantees prompt, timely
        evaluation of threshold and generation of this
        notification.
        "
        --#TYPE "Threshold"
        --#SUMMARY "Entity exceeded the threshold value %d.  Current Value is 
%d."
        --#ARGUMENTS {0,1}
        --#SEVERITY WARNING
        --#GENERIC 6
        --#CATEGORY "Error Events"            
        
        ::= { entitySensorMIBNotifications 1 }


END


________________________________________
From: [email protected] [mailto:[email protected]] 
Sent: Thursday, February 26, 2009 7:00 AM
To: spectrum
Subject: [spectrum] Traps for l2tp tunnel sessions and SNMP trap config.

Hi, 
Is there a way to get a trap for a l2tp tunnel session, not the tunnel itself 
but the ppp session. 
Anyone knowing the specific behaviour of the entity trap, one differens from 
the envmon trap is that the entity discover problems with power supply fan, and 
the envmon discovers problem with the chassie fan.
I have searched all the doc. I could find, but there is no detailed 
description. 
Do you have any suggestions about logging and buffered logging and the size of 
the buffer. 
Regards 
Jan-Erik Frilén

Vattenfall Eldistribution AB
Communication Network 
Distribution Nordic
SE-971 77 Luleå
Visit: Timmermansgatan 25

Phone +46 920 77221
Mobile +46 70 3677221

[email protected] 
www.vattenfall.se

Pleace consider the environment before printing this e-mail 

* --To unsubscribe from spectrum, send email to [email protected] with the body: 
unsubscribe spectrum [email protected] 
<html>
<body>
<p>***********************************************************************</p>
<p>The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else is
unauthorized. If you are not the intended recipient, any disclosure, copying,
distribution or any action taken or omitted to be taken in reliance on it, is
prohibited and may be unlawful. When addressed to our clients any opinions or
advice contained in this email are subject to the terms and conditions
expressed in the governing KPMG client engagement letter.</p>
<p>***********************************************************************</p>
</body>
</html>


---
To unsubscribe from spectrum, send email to [email protected] with the body: 
unsubscribe spectrum [email protected]

Reply via email to