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