1 LLDP-MIB DEFINITIONS ::= BEGIN

     2 

     3 IMPORTS

     4     MODULE-IDENTITY, OBJECT-TYPE, Integer32, Counter32, NOTIFICATION-TYPE

     5         FROM SNMPv2-SMI

     6     TEXTUAL-CONVENTION, TimeStamp, TruthValue

     7         FROM SNMPv2-TC

     8     SnmpAdminString

     9         FROM SNMP-FRAMEWORK-MIB

    10     MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP

    11         FROM SNMPv2-CONF

    12     TimeFilter, ZeroBasedCounter32

    13         FROM RMON2-MIB

    14     AddressFamilyNumbers

    15         FROM IANA-ADDRESS-FAMILY-NUMBERS-MIB;

    16 

    17 lldpMIB MODULE-IDENTITY

    18     LAST-UPDATED "200505060000Z" -- May 06, 2005

    19     ORGANIZATION "IEEE 802.1 Working Group"

    20     CONTACT-INFO 

    21             "  WG-URL: http://grouper.ieee.org/groups/802/1/index.html

    22              WG-EMail: stds-802-1@ieee.org

    23 

    24               Contact: Paul Congdon

    25                Postal: Hewlett-Packard Company

    26                        8000 Foothills Blvd. 

    27                        Roseville, CA 95747

    28                        USA

    29                   Tel: +1-916-785-5753

    30                E-mail: paul_congdon@hp.com"

    31     DESCRIPTION

    32             "Management Information Base module for LLDP configuration,

    33             statistics, local system data and remote systems data

    34             components.

    35 

    36             Copyright (C) IEEE (2005).  This version of this MIB module

    37             is published as subclause 12.1 of IEEE Std 802.1AB-2005;

    38             see the standard itself for full legal notices."

    39     REVISION        "200505060000Z" -- May 06, 2005

    40     DESCRIPTION

    41             "Published as part of IEEE Std 802.1AB-2005 initial version."

    42    ::= { iso std(0) iso8802(8802) ieee802dot1(1) ieee802dot1mibs(1) 2 }

    43 

    44 lldpNotifications            OBJECT IDENTIFIER ::= { lldpMIB 0 }

    45 lldpObjects                  OBJECT IDENTIFIER ::= { lldpMIB 1 }

    46 lldpConformance              OBJECT IDENTIFIER ::= { lldpMIB 2 } 

    47 

    48 --

    49 -- LLDP MIB Objects

    50 --

    51 

    52 lldpConfiguration            OBJECT IDENTIFIER ::= { lldpObjects 1 }

    53 lldpStatistics               OBJECT IDENTIFIER ::= { lldpObjects 2 }

    54 lldpLocalSystemData          OBJECT IDENTIFIER ::= { lldpObjects 3 }

    55 lldpRemoteSystemsData        OBJECT IDENTIFIER ::= { lldpObjects 4 }

    56 lldpExtensions               OBJECT IDENTIFIER ::= { lldpObjects 5 }

    57 

    58 -- 

    59 -- ***********************************************************

    60 -- 

    61 -- Textual Conventions

    62 -- 

    63 -- ***********************************************************

    64 

    65 LldpChassisIdSubtype ::= TEXTUAL-CONVENTION

    66     STATUS      current

    67     DESCRIPTION

    68             "This TC describes the source of a chassis identifier.

    69 

    70             The enumeration 'chassisComponent(1)' represents a chassis

    71             identifier based on the value of entPhysicalAlias object

    72             (defined in IETF RFC 2737) for a chassis component (i.e.,

    73             an entPhysicalClass value of 'chassis(3)').

    74 

    75             The enumeration 'interfaceAlias(2)' represents a chassis

    76             identifier based on the value of ifAlias object (defined in

    77             IETF RFC 2863) for an interface on the containing chassis.

    78 

    79             The enumeration 'portComponent(3)' represents a chassis

    80             identifier based on the value of entPhysicalAlias object

    81             (defined in IETF RFC 2737) for a port or backplane

    82             component (i.e., entPhysicalClass value of 'port(10)' or

    83             'backplane(4)'), within the containing chassis.

    84 

    85             The enumeration 'macAddress(4)' represents a chassis

    86             identifier based on the value of a unicast source address

    87             (encoded in network byte order and IEEE 802.3 canonical bit

    88             order), of a port on the containing chassis as defined in

    89             IEEE Std 802-2001.

    90 

    91             The enumeration 'networkAddress(5)' represents a chassis

    92             identifier based on a network address, associated with

    93             a particular chassis.  The encoded address is actually

    94             composed of two fields.  The first field is a single octet,

    95             representing the IANA AddressFamilyNumbers value for the

    96             specific address type, and the second field is the network

    97             address value.

    98 

    99             The enumeration 'interfaceName(6)' represents a chassis

   100             identifier based on the value of ifName object (defined in

   101             IETF RFC 2863) for an interface on the containing chassis.

   102 

   103             The enumeration 'local(7)' represents a chassis identifier

   104             based on a locally defined value."

   105     SYNTAX  INTEGER {

   106             chassisComponent(1),

   107             interfaceAlias(2),

   108             portComponent(3),

   109             macAddress(4),

   110             networkAddress(5),

   111             interfaceName(6),

   112             local(7)

   113     }

   114 

   115 LldpChassisId ::= TEXTUAL-CONVENTION

   116     STATUS      current

   117     DESCRIPTION

   118             "This TC describes the format of a chassis identifier string.

   119             Objects of this type are always used with an associated

   120             LldpChassisIdSubtype object, which identifies the format of

   121             the particular LldpChassisId object instance.

   122 

   123             If the associated LldpChassisIdSubtype object has a value of

   124             'chassisComponent(1)', then the octet string identifies

   125             a particular instance of the entPhysicalAlias object

   126             (defined in IETF RFC 2737) for a chassis component (i.e.,

   127             an entPhysicalClass value of 'chassis(3)').

   128 

   129             If the associated LldpChassisIdSubtype object has a value

   130             of 'interfaceAlias(2)', then the octet string identifies

   131             a particular instance of the ifAlias object (defined in

   132             IETF RFC 2863) for an interface on the containing chassis.

   133             If the particular ifAlias object does not contain any values,

   134             another chassis identifier type should be used.

   135 

   136             If the associated LldpChassisIdSubtype object has a value

   137             of 'portComponent(3)', then the octet string identifies a

   138             particular instance of the entPhysicalAlias object (defined

   139             in IETF RFC 2737) for a port or backplane component within

   140             the containing chassis.

   141 

   142             If the associated LldpChassisIdSubtype object has a value of

   143             'macAddress(4)', then this string identifies a particular

   144             unicast source address (encoded in network byte order and

   145             IEEE 802.3 canonical bit order), of a port on the containing

   146             chassis as defined in IEEE Std 802-2001.

   147 

   148             If the associated LldpChassisIdSubtype object has a value of

   149             'networkAddress(5)', then this string identifies a particular

   150             network address, encoded in network byte order, associated

   151             with one or more ports on the containing chassis.  The first

   152             octet contains the IANA Address Family Numbers enumeration

   153             value for the specific address type, and octets 2 through

   154             N contain the network address value in network byte order.

   155 

   156             If the associated LldpChassisIdSubtype object has a value

   157             of 'interfaceName(6)', then the octet string identifies

   158             a particular instance of the ifName object (defined in

   159             IETF RFC 2863) for an interface on the containing chassis.

   160             If the particular ifName object does not contain any values,

   161             another chassis identifier type should be used.

   162 

   163             If the associated LldpChassisIdSubtype object has a value of

   164             'local(7)', then this string identifies a locally assigned

   165             Chassis ID."

   166     SYNTAX      OCTET STRING (SIZE (1..255))

   167 

   168 LldpPortIdSubtype ::= TEXTUAL-CONVENTION

   169     STATUS      current

   170     DESCRIPTION

   171             "This TC describes the source of a particular type of port

   172             identifier used in the LLDP MIB.

   173 

   174             The enumeration 'interfaceAlias(1)' represents a port

   175             identifier based on the ifAlias MIB object, defined in IETF

   176             RFC 2863.

   177 

   178             The enumeration 'portComponent(2)' represents a port

   179             identifier based on the value of entPhysicalAlias (defined in

   180             IETF RFC 2737) for a port component (i.e., entPhysicalClass

   181             value of 'port(10)'), within the containing chassis.

   182 

   183             The enumeration 'macAddress(3)' represents a port identifier

   184             based on a unicast source address (encoded in network

   185             byte order and IEEE 802.3 canonical bit order), which has

   186             been detected by the agent and associated with a particular

   187             port (IEEE Std 802-2001).

   188 

   189             The enumeration 'networkAddress(4)' represents a port

   190             identifier based on a network address, detected by the agent

   191             and associated with a particular port.

   192 

   193             The enumeration 'interfaceName(5)' represents a port

   194             identifier based on the ifName MIB object, defined in IETF

   195             RFC 2863.

   196 

   197             The enumeration 'agentCircuitId(6)' represents a port

   198             identifier based on the agent-local identifier of the circuit

   199             (defined in RFC 3046), detected by the agent and associated

   200             with a particular port.

   201 

   202             The enumeration 'local(7)' represents a port identifier

   203             based on a value locally assigned."

   204 

   205     SYNTAX  INTEGER {

   206             interfaceAlias(1),

   207             portComponent(2),

   208             macAddress(3),

   209             networkAddress(4),

   210             interfaceName(5),

   211             agentCircuitId(6),

   212             local(7)

   213     }

   214 

   215 LldpPortId ::= TEXTUAL-CONVENTION

   216     STATUS      current

   217     DESCRIPTION

   218             "This TC describes the format of a port identifier string.

   219             Objects of this type are always used with an associated

   220             LldpPortIdSubtype object, which identifies the format of the

   221             particular LldpPortId object instance.

   222 

   223             If the associated LldpPortIdSubtype object has a value of

   224             'interfaceAlias(1)', then the octet string identifies a

   225             particular instance of the ifAlias object (defined in IETF

   226             RFC 2863).  If the particular ifAlias object does not contain

   227             any values, another port identifier type should be used.

   228 

   229             If the associated LldpPortIdSubtype object has a value of

   230             'portComponent(2)', then the octet string identifies a

   231             particular instance of the entPhysicalAlias object (defined

   232             in IETF RFC 2737) for a port or backplane component.

   233 

   234             If the associated LldpPortIdSubtype object has a value of

   235             'macAddress(3)', then this string identifies a particular

   236             unicast source address (encoded in network byte order

   237             and IEEE 802.3 canonical bit order) associated with the port

   238             (IEEE Std 802-2001).

   239 

   240             If the associated LldpPortIdSubtype object has a value of

   241             'networkAddress(4)', then this string identifies a network

   242             address associated with the port.  The first octet contains

   243             the IANA AddressFamilyNumbers enumeration value for the

   244             specific address type, and octets 2 through N contain the

   245             networkAddress address value in network byte order.

   246 

   247             If the associated LldpPortIdSubtype object has a value of

   248             'interfaceName(5)', then the octet string identifies a

   249             particular instance of the ifName object (defined in IETF

   250             RFC 2863).  If the particular ifName object does not contain

   251             any values, another port identifier type should be used.

   252 

   253             If the associated LldpPortIdSubtype object has a value of

   254             'agentCircuitId(6)', then this string identifies a agent-local

   255             identifier of the circuit (defined in RFC 3046).

   256 

   257             If the associated LldpPortIdSubtype object has a value of

   258             'local(7)', then this string identifies a locally

   259             assigned port ID."

   260     SYNTAX      OCTET STRING (SIZE (1..255))

   261 

   262 LldpManAddrIfSubtype ::= TEXTUAL-CONVENTION

   263     STATUS      current

   264     DESCRIPTION

   265             "This TC describes the basis of a particular type of

   266             interface associated with the management address.

   267 

   268             The enumeration 'unknown(1)' represents the case where the

   269             interface is not known.

   270 

   271             The enumeration 'ifIndex(2)' represents interface identifier

   272             based on the ifIndex MIB object.

   273 

   274             The enumeration 'systemPortNumber(3)' represents interface

   275             identifier based on the system port numbering convention."

   276     REFERENCE 

   277             "IEEE 802.1AB-2005 9.5.9.5"

   278             

   279     SYNTAX  INTEGER {

   280             unknown(1),

   281             ifIndex(2),

   282             systemPortNumber(3)

   283     }

   284 

   285 LldpManAddress ::= TEXTUAL-CONVENTION

   286     STATUS      current

   287     DESCRIPTION

   288             "The value of a management address associated with the LLDP

   289             agent that may be used to reach higher layer entities to

   290             assist discovery by network management.

   291 

   292             It should be noted that appropriate security credentials,

   293             such as SNMP engineId, may be required to access the LLDP

   294             agent using a management address.  These necessary credentials

   295             should be known by the network management and the objects

   296             associated with the credentials are not included in the

   297             LLDP agent."

   298     SYNTAX      OCTET STRING (SIZE (1..31))

   299 

   300 LldpSystemCapabilitiesMap ::= TEXTUAL-CONVENTION

   301     STATUS      current

   302     DESCRIPTION

   303             "This TC describes the system capabilities.

   304 

   305             The bit 'other(0)' indicates that the system has capabilities

   306             other than those listed below.

   307 

   308             The bit 'repeater(1)' indicates that the system has repeater

   309             capability.

   310 

   311             The bit 'bridge(2)' indicates that the system has bridge

   312             capability.

   313 

   314             The bit 'wlanAccessPoint(3)' indicates that the system has 

   315             WLAN access point capability.

   316 

   317             The bit 'router(4)' indicates that the system has router

   318             capability.

   319 

   320             The bit 'telephone(5)' indicates that the system has telephone

   321             capability.

   322 

   323             The bit 'docsisCableDevice(6)' indicates that the system has

   324             DOCSIS Cable Device capability (IETF RFC 2669 & 2670).

   325 

   326             The bit 'stationOnly(7)' indicates that the system has only

   327             station capability and nothing else."

   328     SYNTAX  BITS {

   329             other(0),

   330             repeater(1),

   331             bridge(2),

   332             wlanAccessPoint(3),

   333             router(4),

   334             telephone(5),

   335             docsisCableDevice(6),

   336             stationOnly(7)

   337     }

   338 

   339 LldpPortNumber ::= TEXTUAL-CONVENTION

   340     DISPLAY-HINT "d"

   341     STATUS     current 

   342     DESCRIPTION

   343             "Each port contained in the chassis (that is known to the

   344             LLDP agent) is uniquely identified by a port number.

   345 

   346             A port number has no mandatory relationship to an

   347             InterfaceIndex object (of the interfaces MIB, IETF RFC 2863).

   348             If the LLDP agent is a IEEE 802.1D, IEEE 802.1Q bridge, the

   349             LldpPortNumber will have the same value as the dot1dBasePort

   350             object (defined in IETF RFC 1493) associated corresponding

   351             bridge port.  If the system hosting LLDP agent is not an

   352             IEEE 802.1D or an IEEE 802.1Q bridge, the LldpPortNumber

   353             will have the same value as the corresponding interface's

   354             InterfaceIndex object.

   355 

   356             Port numbers should be in the range of 1 and 4096 since a

   357             particular port is also represented by the corresponding

   358             port number bit in LldpPortList."

   359     SYNTAX 	Integer32(1..4096)

   360 

   361 LldpPortList ::= TEXTUAL-CONVENTION

   362     STATUS      current

   363     DESCRIPTION

   364             "Each octet within this value specifies a set of eight ports,

   365             with the first octet specifying ports 1 through 8, the second

   366             octet specifying ports 9 through 16, etc.  Within each octet,

   367             the most significant bit represents the lowest numbered port,

   368             and the least significant bit represents the highest numbered

   369             port.  Thus, each port of the system is represented by a

   370             single bit within the value of this object.  If that bit has

   371             a value of '1' then that port is included in the set of ports;

   372             the port is not included if its bit has a value of '0'."

   373     REFERENCE 

   374             "IETF RFC 2674 section 5"

   375     SYNTAX  OCTET STRING(SIZE(0..512))

   376 

   377 -- 

   378 -- ***********************************************************

   379 -- 

   380 --                  L L D P    C O N F I G 

   381 -- 

   382 -- *********************************************************** 

   383 --

   384 

   385 lldpMessageTxInterval OBJECT-TYPE

   386     SYNTAX      Integer32(5..32768)

   387     UNITS       "seconds"

   388     MAX-ACCESS  read-write

   389     STATUS      current

   390     DESCRIPTION

   391             "The interval at which LLDP frames are transmitted on

   392             behalf of this LLDP agent.

   393 

   394             The default value for lldpMessageTxInterval object is

   395             30 seconds.

   396 

   397             The value of this object must be restored from non-volatile

   398             storage after a re-initialization of the management system."

   399     REFERENCE 

   400             "IEEE 802.1AB-2005 10.5.3.3"

   401     DEFVAL     { 30 }

   402     ::= { lldpConfiguration 1 }

   403 

   404 lldpMessageTxHoldMultiplier OBJECT-TYPE

   405     SYNTAX      Integer32(2..10)

   406     MAX-ACCESS  read-write

   407     STATUS      current

   408     DESCRIPTION

   409             "The time-to-live value expressed as a multiple of the

   410             lldpMessageTxInterval object.  The actual time-to-live value

   411             used in LLDP frames, transmitted on behalf of this LLDP agent,

   412             can be expressed by the following formula: TTL = min(65535,

   413             (lldpMessageTxInterval * lldpMessageTxHoldMultiplier)) For

   414             example, if the value of lldpMessageTxInterval is '30', and

   415             the value of lldpMessageTxHoldMultiplier is '4', then the

   416             value '120' is encoded in the TTL field in the LLDP header.

   417 

   418             The default value for lldpMessageTxHoldMultiplier object is 4.

   419 

   420             The value of this object must be restored from non-volatile

   421             storage after a re-initialization of the management system."

   422     REFERENCE 

   423             "IEEE 802.1AB-2005 10.5.3.3"

   424     DEFVAL      { 4 }    

   425     ::= { lldpConfiguration 2 }

   426 

   427 lldpReinitDelay OBJECT-TYPE

   428     SYNTAX      Integer32(1..10)

   429     UNITS       "seconds"

   430     MAX-ACCESS  read-write

   431     STATUS      current

   432     DESCRIPTION

   433             "The lldpReinitDelay indicates the delay (in units of

   434             seconds) from when lldpPortConfigAdminStatus object of a

   435             particular port becomes 'disabled' until re-initialization

   436             will be attempted.

   437 

   438             The default value for lldpReintDelay object is two seconds.

   439 

   440             The value of this object must be restored from non-volatile

   441             storage after a re-initialization of the management system."

   442     REFERENCE 

   443             "IEEE 802.1AB-2005 10.5.3.3"

   444     DEFVAL      { 2 }    

   445     ::= { lldpConfiguration 3 }

   446 

   447 lldpTxDelay OBJECT-TYPE

   448     SYNTAX      Integer32(1..8192)

   449     UNITS       "seconds"

   450     MAX-ACCESS  read-write

   451     STATUS      current

   452     DESCRIPTION

   453             "The lldpTxDelay indicates the delay (in units

   454             of seconds) between successive LLDP frame transmissions 

   455             initiated by value/status changes in the LLDP local systems

   456             MIB.  The recommended value for the lldpTxDelay is set by the

   457             following  formula:

   458 

   459                1 <= lldpTxDelay <= (0.25 * lldpMessageTxInterval)

   460 

   461             The default value for lldpTxDelay object is two seconds.

   462 

   463             The value of this object must be restored from non-volatile

   464             storage after a re-initialization of the management system."

   465     REFERENCE 

   466             "IEEE 802.1AB-2005 10.5.3.3"

   467     DEFVAL      { 2 }    

   468     ::= { lldpConfiguration 4 }

   469 

   470 lldpNotificationInterval OBJECT-TYPE

   471     SYNTAX      Integer32(5..3600)

   472     UNITS       "seconds"

   473     MAX-ACCESS  read-write

   474     STATUS      current

   475     DESCRIPTION

   476             "This object controls the transmission of LLDP notifications.

   477 

   478             the agent must not generate more than one lldpRemTablesChange

   479             notification-event in the indicated period, where a

   480             'notification-event' is the transmission of a single

   481             notification PDU type to a list of notification destinations.

   482             If additional changes in lldpRemoteSystemsData object

   483             groups occur within the indicated throttling period,

   484             then these trap- events must be suppressed by the

   485             agent. An NMS should periodically check the value of

   486             lldpStatsRemTableLastChangeTime to detect any missed

   487             lldpRemTablesChange notification-events, e.g. due to

   488             throttling or transmission loss.

   489 

   490             If notification transmission is enabled for particular ports,

   491             the suggested default throttling period is 5 seconds.

   492 

   493             The value of this object must be restored from non-volatile

   494             storage after a re-initialization of the management system."

   495     DEFVAL { 5 }

   496     ::= { lldpConfiguration 5 }

   497 

   498 --

   499 -- lldpPortConfigTable: LLDP configuration on a per port basis

   500 --

   501 

   502 lldpPortConfigTable   OBJECT-TYPE

   503     SYNTAX      SEQUENCE OF LldpPortConfigEntry

   504     MAX-ACCESS  not-accessible

   505     STATUS      current

   506     DESCRIPTION

   507             "The table that controls LLDP frame transmission on individual

   508             ports."

   509     ::= { lldpConfiguration 6 }

   510 

   511 lldpPortConfigEntry   OBJECT-TYPE

   512     SYNTAX      LldpPortConfigEntry

   513     MAX-ACCESS  not-accessible

   514     STATUS      current

   515     DESCRIPTION

   516             "LLDP configuration information for a particular port.

   517             This configuration parameter controls the transmission and

   518             the reception of LLDP frames on those ports whose rows are

   519             created in this table."

   520      INDEX  { lldpPortConfigPortNum }

   521     ::= { lldpPortConfigTable 1 }

   522 

   523 LldpPortConfigEntry ::= SEQUENCE {

   524       lldpPortConfigPortNum            LldpPortNumber,

   525       lldpPortConfigAdminStatus        INTEGER,

   526       lldpPortConfigNotificationEnable TruthValue,

   527       lldpPortConfigTLVsTxEnable       BITS }

   528 

   529 lldpPortConfigPortNum   OBJECT-TYPE

   530     SYNTAX      LldpPortNumber 

   531     MAX-ACCESS  not-accessible

   532     STATUS      current

   533     DESCRIPTION

   534             "The index value used to identify the port component

   535             (contained in the local chassis with the LLDP agent)

   536             associated with this entry.

   537 

   538             The value of this object is used as a port index to the

   539             lldpPortConfigTable."

   540     ::= { lldpPortConfigEntry 1 }

   541 

   542 lldpPortConfigAdminStatus  OBJECT-TYPE 

   543     SYNTAX INTEGER { 

   544        txOnly(1), 

   545        rxOnly(2),

   546        txAndRx(3),

   547        disabled(4)

   548     }

   549     MAX-ACCESS read-write 

   550     STATUS     current 

   551     DESCRIPTION 

   552             "The administratively desired status of the local LLDP agent.

   553 

   554             If the associated lldpPortConfigAdminStatus object has a

   555             value of 'txOnly(1)', then LLDP agent will transmit LLDP

   556             frames on this port and it will not store any information

   557             about the remote systems connected.

   558          

   559             If the associated lldpPortConfigAdminStatus object has a

   560             value of 'rxOnly(2)', then the LLDP agent will receive,

   561             but it will not transmit LLDP frames on this port.

   562 

   563             If the associated lldpPortConfigAdminStatus object has a

   564             value of 'txAndRx(3)', then the LLDP agent will transmit

   565             and receive LLDP frames on this port.

   566 

   567             If the associated lldpPortConfigAdminStatus object has a

   568             value of 'disabled(4)', then LLDP agent will not transmit or

   569             receive LLDP frames on this port.  If there is remote systems

   570             information which is received on this port and stored in

   571             other tables, before the port's lldpPortConfigAdminStatus

   572             becomes disabled, then the information will naturally age out."

   573     REFERENCE 

   574             "IEEE 802.1AB-2005 10.5.1"

   575     DEFVAL  { txAndRx }    

   576    ::= { lldpPortConfigEntry 2 } 

   577 

   578 lldpPortConfigNotificationEnable OBJECT-TYPE 

   579     SYNTAX     TruthValue

   580     MAX-ACCESS read-write 

   581     STATUS     current 

   582     DESCRIPTION 

   583             "The lldpPortConfigNotificationEnable controls, on a per

   584             port basis,  whether or not notifications from the agent

   585             are enabled. The value true(1) means that notifications are

   586             enabled; the value false(2) means that they are not."

   587     DEFVAL  { false }    

   588    ::= { lldpPortConfigEntry 3 } 

   589 

   590 lldpPortConfigTLVsTxEnable OBJECT-TYPE

   591     SYNTAX      BITS {

   592             portDesc(0),

   593             sysName(1),

   594             sysDesc(2),

   595             sysCap(3)

   596     }

   597     MAX-ACCESS  read-write

   598     STATUS      current

   599     DESCRIPTION

   600             "The lldpPortConfigTLVsTxEnable, defined as a bitmap,

   601             includes the basic set of LLDP TLVs whose transmission is

   602             allowed on the local LLDP agent by the network management.

   603             Each bit in the bitmap corresponds to a TLV type associated

   604             with a specific optional TLV.

   605 

   606             It should be noted that the organizationally-specific TLVs

   607             are excluded from the lldpTLVsTxEnable bitmap.

   608             

   609             LLDP Organization Specific Information Extension MIBs should

   610             have similar configuration object to control transmission

   611             of their organizationally defined TLVs.

   612 

   613             The bit 'portDesc(0)' indicates that LLDP agent should

   614             transmit 'Port Description TLV'.

   615 

   616             The bit 'sysName(1)' indicates that LLDP agent should transmit

   617             'System Name TLV'.

   618 

   619             The bit 'sysDesc(2)' indicates that LLDP agent should transmit

   620             'System Description TLV'.

   621 

   622             The bit 'sysCap(3)' indicates that LLDP agent should transmit

   623             'System Capabilities TLV'.

   624 

   625             There is no bit reserved for the management address TLV type

   626             since transmission of management address TLVs are controlled

   627             by another object, lldpConfigManAddrTable.

   628 

   629             The default value for lldpPortConfigTLVsTxEnable object is

   630             empty set, which means no enumerated values are set.

   631 

   632             The value of this object must be restored from non-volatile

   633             storage after a re-initialization of the management system."

   634     REFERENCE 

   635             "IEEE 802.1AB-2005 10.2.1.1"

   636     DEFVAL  { { } }

   637     ::= { lldpPortConfigEntry 4 } 

   638 

   639 

   640 --

   641 -- lldpManAddrConfigTxPortsTable : selection of management addresses

   642 --                                 to be transmitted on a specified set

   643 --                                 of ports.

   644 -- 

   645 

   646 lldpConfigManAddrTable OBJECT-TYPE

   647     SYNTAX      SEQUENCE OF LldpConfigManAddrEntry

   648     MAX-ACCESS  not-accessible

   649     STATUS      current

   650     DESCRIPTION

   651             "The table that controls selection of LLDP management address

   652             TLV instances to be transmitted on individual ports."

   653     ::= { lldpConfiguration 7 }

   654 

   655 lldpConfigManAddrEntry  OBJECT-TYPE

   656     SYNTAX      LldpConfigManAddrEntry

   657     MAX-ACCESS  not-accessible

   658     STATUS      current

   659     DESCRIPTION

   660             "LLDP configuration information that specifies the set

   661             of ports (represented as a PortList) on which the local

   662             system management address instance will be transmitted.

   663 

   664             This configuration object augments the lldpLocManAddrEntry,

   665             therefore it is only present along with the management

   666             address instance contained in the associated

   667             lldpLocManAddrEntry entry.

   668 

   669             Each active lldpConfigManAddrEntry must be restored from

   670             non-volatile and re-created (along with the corresponding

   671             lldpLocManAddrEntry) after a re-initialization of the

   672             management system."

   673     AUGMENTS { lldpLocManAddrEntry }

   674     ::= { lldpConfigManAddrTable 1 }

   675 

   676 LldpConfigManAddrEntry  ::= SEQUENCE {

   677     lldpConfigManAddrPortsTxEnable LldpPortList

   678 }

   679 

   680 lldpConfigManAddrPortsTxEnable  OBJECT-TYPE

   681     SYNTAX        LldpPortList

   682     MAX-ACCESS    read-write

   683     STATUS        current

   684     DESCRIPTION

   685             "A set of ports that are identified by a PortList, in which

   686             each port is represented as a bit.  The corresponding local

   687             system management address instance will be transmitted on the

   688             member ports of the lldpManAddrPortsTxEnable.  

   689 

   690             The default value for lldpConfigManAddrPortsTxEnable object

   691             is empty binary string, which means no ports are specified

   692             for advertising indicated management address instance."

   693     REFERENCE 

   694             "IEEE 802.1AB-2005 10.2.1.1"

   695     DEFVAL  { ''H }     -- empty binary string

   696     ::= { lldpConfigManAddrEntry 1 }

   697 

   698 

   699 --

   700 --  *********************************************************** 

   701 --

   702 --                   L L D P    S T A T S 

   703 --

   704 --  *********************************************************** 

   705 --

   706 -- LLDP Stats Group

   707 

   708 lldpStatsRemTablesLastChangeTime OBJECT-TYPE

   709     SYNTAX      TimeStamp

   710     MAX-ACCESS  read-only

   711     STATUS      current

   712     DESCRIPTION

   713             "The value of sysUpTime object (defined in IETF RFC 3418)

   714             at the time an entry is created, modified, or deleted in the

   715             in tables associated with the lldpRemoteSystemsData objects

   716             and all LLDP extension objects associated with remote systems.

   717 

   718             An NMS can use this object to reduce polling of the

   719             lldpRemoteSystemsData objects."

   720     ::= { lldpStatistics 1 }

   721 

   722 lldpStatsRemTablesInserts OBJECT-TYPE

   723     SYNTAX      ZeroBasedCounter32

   724     UNITS       "table entries"

   725     MAX-ACCESS  read-only

   726     STATUS      current

   727     DESCRIPTION

   728             "The number of times the complete set of information

   729             advertised by a particular MSAP has been inserted into tables

   730             contained in lldpRemoteSystemsData and lldpExtensions objects.

   731 

   732             The complete set of information received from a particular

   733             MSAP should be inserted into related tables.  If partial

   734             information cannot be inserted for a reason such as lack

   735             of resources, all of the complete set of information should

   736             be removed.

   737 

   738             This counter should be incremented only once after the

   739             complete set of information is successfully recorded

   740             in all related tables.  Any failures during inserting

   741             information set which result in deletion of previously

   742             inserted information should not trigger any changes in

   743             lldpStatsRemTablesInserts since the insert is not completed

   744             yet or or in lldpStatsRemTablesDeletes, since the deletion

   745             would only be a partial deletion. If the failure was the

   746             result of lack of resources, the lldpStatsRemTablesDrops

   747             counter should be incremented once."

   748     ::= { lldpStatistics 2 }

   749 

   750 lldpStatsRemTablesDeletes   OBJECT-TYPE

   751     SYNTAX      ZeroBasedCounter32

   752     UNITS       "table entries"

   753     MAX-ACCESS  read-only

   754     STATUS      current

   755 

   756     DESCRIPTION

   757             "The number of times the complete set of information

   758             advertised by a particular MSAP has been deleted from

   759             tables contained in lldpRemoteSystemsData and lldpExtensions

   760             objects.

   761 

   762             This counter should be incremented only once when the

   763             complete set of information is completely deleted from all

   764             related tables.  Partial deletions, such as deletion of

   765             rows associated with a particular MSAP from some tables,

   766             but not from all tables are not allowed, thus should not

   767             change the value of this counter."

   768     ::= { lldpStatistics 3 }

   769 

   770 lldpStatsRemTablesDrops  OBJECT-TYPE

   771     SYNTAX      ZeroBasedCounter32

   772     UNITS       "table entries"

   773     MAX-ACCESS  read-only

   774 

   775     STATUS      current

   776     DESCRIPTION

   777             "The number of times the complete set of information

   778             advertised by a particular MSAP could not be entered into

   779             tables contained in lldpRemoteSystemsData and lldpExtensions

   780             objects because of insufficient resources."

   781     ::= { lldpStatistics 4 }

   782 

   783 lldpStatsRemTablesAgeouts   OBJECT-TYPE

   784     SYNTAX      ZeroBasedCounter32

   785     MAX-ACCESS  read-only

   786     STATUS      current

   787     DESCRIPTION

   788             "The number of times the complete set of information

   789             advertised by a particular MSAP has been deleted from tables

   790             contained in lldpRemoteSystemsData and lldpExtensions objects

   791             because the information timeliness interval has expired.

   792 

   793             This counter should be incremented only once when the complete

   794             set of information is completely invalidated (aged out)

   795             from all related tables.  Partial aging, similar to deletion

   796             case, is not allowed, and thus, should not change the value

   797             of this counter."

   798     ::= { lldpStatistics 5 }

   799 

   800 --

   801 -- TX statistics

   802 --

   803 

   804 lldpStatsTxPortTable  OBJECT-TYPE

   805     SYNTAX      SEQUENCE OF LldpStatsTxPortEntry

   806     MAX-ACCESS  not-accessible

   807     STATUS      current

   808     DESCRIPTION 

   809             "A table containing LLDP transmission statistics for

   810             individual ports.  Entries are not required to exist in

   811             this table while the lldpPortConfigEntry object is equal to

   812             'disabled(4)'."

   813     ::= { lldpStatistics 6 } 

   814 

   815 lldpStatsTxPortEntry   OBJECT-TYPE

   816      SYNTAX      LldpStatsTxPortEntry

   817      MAX-ACCESS  not-accessible

   818      STATUS      current

   819      DESCRIPTION

   820              "LLDP frame transmission statistics for a particular port.  

   821              The port must be contained in the same chassis as the

   822              LLDP agent.

   823             

   824              All counter values in a particular entry shall be

   825              maintained on a continuing basis and shall not be deleted

   826              upon expiration of rxInfoTTL timing counters in the LLDP

   827              remote systems MIB of the receipt of a shutdown frame from

   828              a remote LLDP agent.

   829 

   830              All statistical counters associated with a particular

   831              port on the local LLDP agent become frozen whenever the

   832              adminStatus is disabled for the same port."

   833      INDEX  { lldpStatsTxPortNum }

   834      ::= { lldpStatsTxPortTable 1 } 

   835 

   836 LldpStatsTxPortEntry ::= SEQUENCE {      

   837       lldpStatsTxPortNum                 LldpPortNumber,

   838       lldpStatsTxPortFramesTotal         Counter32

   839 }

   840 

   841 lldpStatsTxPortNum   OBJECT-TYPE

   842     SYNTAX      LldpPortNumber 

   843     MAX-ACCESS  not-accessible

   844     STATUS      current

   845     DESCRIPTION

   846             "The index value used to identify the port component

   847             (contained in the local chassis with the LLDP agent)

   848             associated with this entry.

   849 

   850             The value of this object is used as a port index to the

   851             lldpStatsTable."

   852     ::= { lldpStatsTxPortEntry 1 } 

   853 

   854 lldpStatsTxPortFramesTotal  OBJECT-TYPE

   855     SYNTAX        Counter32

   856     MAX-ACCESS    read-only

   857     STATUS        current

   858     DESCRIPTION

   859             "The number of LLDP frames transmitted by this LLDP agent

   860             on the indicated port."

   861     REFERENCE 

   862             "IEEE 802.1AB-2005 10.5.2.1"

   863     ::= { lldpStatsTxPortEntry 2 }

   864 

   865 --

   866 -- RX statistics

   867 --

   868 

   869 lldpStatsRxPortTable  OBJECT-TYPE

   870     SYNTAX      SEQUENCE OF LldpRxStatsPortEntry

   871     MAX-ACCESS  not-accessible

   872     STATUS      current

   873     DESCRIPTION 

   874             "A table containing LLDP reception statistics for individual

   875             ports.  Entries are not required to exist in this table while

   876             the lldpPortConfigEntry object is equal to 'disabled(4)'."

   877     ::= { lldpStatistics 7 } 

   878 

   879 lldpStatsRxPortEntry   OBJECT-TYPE

   880      SYNTAX      LldpRxStatsPortEntry

   881      MAX-ACCESS  not-accessible

   882      STATUS      current

   883      DESCRIPTION

   884              "LLDP frame reception statistics for a particular port.

   885              The port must be contained in the same chassis as the

   886              LLDP agent.

   887             

   888              All counter values in a particular entry shall be

   889              maintained on a continuing basis and shall not be deleted

   890              upon expiration of rxInfoTTL timing counters in the LLDP

   891              remote systems MIB of the receipt of a shutdown frame from

   892              a remote LLDP agent.

   893 

   894              All statistical counters associated with a particular

   895              port on the local LLDP agent become frozen whenever the

   896              adminStatus is disabled for the same port."

   897      INDEX  { lldpStatsRxPortNum }

   898      ::= { lldpStatsRxPortTable 1 } 

   899 

   900 LldpRxStatsPortEntry ::= SEQUENCE {      

   901       lldpStatsRxPortNum                   LldpPortNumber,

   902       lldpStatsRxPortFramesDiscardedTotal  Counter32,

   903       lldpStatsRxPortFramesErrors          Counter32,

   904       lldpStatsRxPortFramesTotal           Counter32,

   905       lldpStatsRxPortTLVsDiscardedTotal    Counter32,

   906       lldpStatsRxPortTLVsUnrecognizedTotal Counter32,

   907       lldpStatsRxPortAgeoutsTotal          ZeroBasedCounter32

   908 }

   909 

   910 lldpStatsRxPortNum   OBJECT-TYPE

   911     SYNTAX      LldpPortNumber 

   912     MAX-ACCESS  not-accessible

   913     STATUS      current

   914     DESCRIPTION

   915             "The index value used to identify the port component

   916             (contained in the local chassis with the LLDP agent)

   917             associated with this entry.

   918 

   919             The value of this object is used as a port index to the

   920             lldpStatsTable."

   921     ::= { lldpStatsRxPortEntry 1 } 

   922 

   923 lldpStatsRxPortFramesDiscardedTotal OBJECT-TYPE 

   924     SYNTAX        Counter32

   925     MAX-ACCESS read-only

   926     STATUS     current 

   927     DESCRIPTION 

   928             "The number of LLDP frames received by this LLDP agent on

   929             the indicated port, and then discarded for any reason.

   930             This counter can provide an indication that LLDP header

   931             formating problems may exist with the local LLDP agent in

   932             the sending system or that LLDPDU validation problems may

   933             exist with the local LLDP agent in the receiving system."

   934    REFERENCE 

   935             "IEEE 802.1AB-2005 10.5.2.2"

   936    ::= { lldpStatsRxPortEntry 2 } 

   937 

   938 lldpStatsRxPortFramesErrors  OBJECT-TYPE

   939     SYNTAX        Counter32

   940     MAX-ACCESS    read-only

   941     STATUS        current

   942     DESCRIPTION

   943             "The number of invalid LLDP frames received by this LLDP

   944             agent on the indicated port, while this LLDP agent is enabled."

   945     REFERENCE 

   946             "IEEE 802.1AB-2005 10.5.2.2"

   947     ::= { lldpStatsRxPortEntry 3 }

   948 

   949 lldpStatsRxPortFramesTotal OBJECT-TYPE

   950     SYNTAX        Counter32

   951     MAX-ACCESS    read-only

   952     STATUS        current

   953     DESCRIPTION

   954             "The number of valid LLDP frames received by this LLDP agent

   955             on the indicated port, while this LLDP agent is enabled."

   956     REFERENCE 

   957             "IEEE 802.1AB-2005 10.5.2.2"

   958     ::= { lldpStatsRxPortEntry 4 }

   959 

   960 lldpStatsRxPortTLVsDiscardedTotal OBJECT-TYPE

   961     SYNTAX        Counter32

   962     MAX-ACCESS    read-only

   963     STATUS        current

   964     DESCRIPTION

   965             "The number of LLDP TLVs discarded for any reason by this LLDP

   966             agent on the indicated port."

   967     REFERENCE 

   968             "IEEE 802.1AB-2005 10.5.2.2"

   969     ::= { lldpStatsRxPortEntry 5 }

   970 

   971 lldpStatsRxPortTLVsUnrecognizedTotal  OBJECT-TYPE

   972     SYNTAX        Counter32

   973     MAX-ACCESS    read-only

   974     STATUS        current

   975     DESCRIPTION

   976             "The number of LLDP TLVs received on the given port that

   977             are not recognized by this LLDP agent on the indicated port.

   978             

   979             An unrecognized TLV is referred to as the TLV whose type value

   980             is in the range of reserved TLV types (000 1001 - 111 1110)

   981             in Table 9.1 of IEEE Std 802.1AB-2005.  An unrecognized

   982             TLV may be a basic management TLV from a later LLDP version."

   983     REFERENCE 

   984             "IEEE 802.1AB-2005 10.5.2.2"

   985     ::= { lldpStatsRxPortEntry 6 }

   986 

   987 lldpStatsRxPortAgeoutsTotal   OBJECT-TYPE

   988     SYNTAX      ZeroBasedCounter32

   989     MAX-ACCESS  read-only

   990     STATUS      current

   991     DESCRIPTION

   992             "The counter that represents the number of age-outs that

   993             occurred on a given port.  An age-out is the number of

   994             times the complete set of information advertised by a

   995             particular MSAP has been deleted from tables contained in

   996             lldpRemoteSystemsData and lldpExtensions objects because

   997             the information timeliness interval has expired.

   998 

   999             This counter is similar to lldpStatsRemTablesAgeouts, except

  1000             that the counter is on a per port basis.  This enables NMS to

  1001             poll tables associated with the lldpRemoteSystemsData objects

  1002             and all LLDP extension objects associated with remote systems

  1003             on the indicated port only.

  1004 

  1005             This counter should be set to zero during agent initialization

  1006             and its value should not be saved in non-volatile storage.

  1007             When a port's admin status changes from 'disabled' to

  1008             'rxOnly', 'txOnly' or 'txAndRx', the counter associated with

  1009             the same port should reset to 0.  The agent should also flush

  1010             all remote system information associated with the same port.

  1011 

  1012             This counter should be incremented only once when the

  1013             complete set of information is invalidated (aged out) from

  1014             all related tables on a particular port.  Partial aging

  1015             is not allowed, and thus, should not change the value of

  1016             this counter."

  1017     REFERENCE 

  1018             "IEEE 802.1AB-2005 10.5.2.2"

  1019     ::= { lldpStatsRxPortEntry 7 }

  1020 

  1021 --  ***********************************************************

  1022 --

  1023 --          L O C A L    S Y S T E M    D A T A

  1024 --

  1025 --  ***********************************************************

  1026 

  1027 lldpLocChassisIdSubtype  OBJECT-TYPE

  1028     SYNTAX      LldpChassisIdSubtype

  1029     MAX-ACCESS  read-only

  1030     STATUS      current

  1031     DESCRIPTION

  1032             "The type of encoding used to identify the chassis

  1033             associated with the local system."

  1034     REFERENCE 

  1035             "IEEE 802.1AB-2005 9.5.2.2"

  1036     ::= { lldpLocalSystemData 1 }

  1037 

  1038 lldpLocChassisId  OBJECT-TYPE

  1039     SYNTAX      LldpChassisId

  1040     MAX-ACCESS  read-only

  1041     STATUS      current

  1042     DESCRIPTION

  1043             "The string value used to identify the chassis component

  1044             associated with the local system."

  1045     REFERENCE 

  1046             "IEEE 802.1AB-2005 9.5.2.3"

  1047     ::= { lldpLocalSystemData 2 }

  1048 

  1049 lldpLocSysName  OBJECT-TYPE

  1050     SYNTAX      SnmpAdminString (SIZE(0..255))

  1051     MAX-ACCESS  read-only

  1052     STATUS      current

  1053     DESCRIPTION

  1054             "The string value used to identify the system name of the

  1055             local system.  If the local agent supports IETF RFC 3418,

  1056             lldpLocSysName object should have the same value of sysName

  1057             object."

  1058     REFERENCE 

  1059             "IEEE 802.1AB-2005 9.5.6.2"

  1060     ::= { lldpLocalSystemData 3 }

  1061 

  1062 lldpLocSysDesc  OBJECT-TYPE

  1063     SYNTAX      SnmpAdminString (SIZE(0..255))

  1064     MAX-ACCESS  read-only

  1065     STATUS      current

  1066     DESCRIPTION

  1067             "The string value used to identify the system description

  1068             of the local system.  If the local agent supports IETF RFC 3418,

  1069             lldpLocSysDesc object should have the same value of sysDesc

  1070             object."

  1071     REFERENCE 

  1072             "IEEE 802.1AB-2005 9.5.7.2"

  1073     ::= { lldpLocalSystemData 4 }

  1074 

  1075 lldpLocSysCapSupported OBJECT-TYPE

  1076     SYNTAX      LldpSystemCapabilitiesMap

  1077     MAX-ACCESS  read-only

  1078     STATUS      current

  1079     DESCRIPTION

  1080             "The bitmap value used to identify which system capabilities

  1081             are supported on the local system."

  1082     REFERENCE 

  1083             "IEEE 802.1AB-2005 9.5.8.1"

  1084     ::= { lldpLocalSystemData 5 }

  1085 

  1086 lldpLocSysCapEnabled  OBJECT-TYPE

  1087     SYNTAX      LldpSystemCapabilitiesMap

  1088     MAX-ACCESS  read-only

  1089     STATUS      current

  1090     DESCRIPTION

  1091             "The bitmap value used to identify which system capabilities

  1092             are enabled on the local system."

  1093     REFERENCE 

  1094             "IEEE 802.1AB-2005 9.5.8.2"

  1095     ::= { lldpLocalSystemData 6 }

  1096 

  1097 

  1098 --

  1099 -- lldpLocPortTable : Port specific Local system data

  1100 --

  1101 

  1102 lldpLocPortTable OBJECT-TYPE

  1103     SYNTAX      SEQUENCE OF LldpLocPortEntry

  1104     MAX-ACCESS  not-accessible

  1105     STATUS      current

  1106     DESCRIPTION

  1107             "This table contains one or more rows per port information

  1108             associated with the local system known to this agent."

  1109     ::= { lldpLocalSystemData 7 }

  1110 

  1111 lldpLocPortEntry OBJECT-TYPE

  1112     SYNTAX      LldpLocPortEntry 

  1113     MAX-ACCESS  not-accessible

  1114     STATUS      current

  1115     DESCRIPTION

  1116             "Information about a particular port component.

  1117 

  1118             Entries may be created and deleted in this table by the

  1119             agent."

  1120     INDEX   { lldpLocPortNum }

  1121     ::= { lldpLocPortTable 1 }

  1122 

  1123 LldpLocPortEntry ::= SEQUENCE {

  1124       lldpLocPortNum                LldpPortNumber,

  1125       lldpLocPortIdSubtype          LldpPortIdSubtype,

  1126       lldpLocPortId                 LldpPortId,

  1127       lldpLocPortDesc               SnmpAdminString

  1128 }

  1129 

  1130 lldpLocPortNum  OBJECT-TYPE

  1131     SYNTAX      LldpPortNumber

  1132     MAX-ACCESS  not-accessible

  1133     STATUS      current

  1134     DESCRIPTION

  1135             "The index value used to identify the port component

  1136             (contained in the local chassis with the LLDP agent)