idnits 2.17.1 draft-ietf-rmonmib-smon-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-25) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 1741 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 145 instances of too long lines in the document, the longest one being 8 characters in excess of 72. == There are 1 instance of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 223 has weird spacing: '...tecture or by...' == Line 313 has weird spacing: '...ty than copy ...' == Line 1378 has weird spacing: '...rce and desti...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: '2' is defined on line 1612, but no explicit reference was found in the text == Unused Reference: '7' is defined on line 1633, but no explicit reference was found in the text == Unused Reference: '8' is defined on line 1637, but no explicit reference was found in the text == Unused Reference: '9' is defined on line 1641, but no explicit reference was found in the text == Unused Reference: '10' is defined on line 1645, but no explicit reference was found in the text == Unused Reference: '16' is defined on line 1664, but no explicit reference was found in the text ** Obsolete normative reference: RFC 1902 (ref. '1') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1903 (ref. '2') (Obsoleted by RFC 2579) ** Obsolete normative reference: RFC 1905 (ref. '4') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 1573 (ref. '5') (Obsoleted by RFC 2233) -- Possible downref: Non-RFC (?) normative reference: ref. '6' ** Obsolete normative reference: RFC 1904 (ref. '7') (Obsoleted by RFC 2580) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '8') ** Obsolete normative reference: RFC 1906 (ref. '9') (Obsoleted by RFC 3417) ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. '10') ** Obsolete normative reference: RFC 2021 (ref. '11') (Obsoleted by RFC 4502) ** Obsolete normative reference: RFC 1757 (ref. '12') (Obsoleted by RFC 2819) ** Obsolete normative reference: RFC 2037 (ref. '13') (Obsoleted by RFC 2737) -- Possible downref: Non-RFC (?) normative reference: ref. '14' -- Possible downref: Non-RFC (?) normative reference: ref. '15' ** Obsolete normative reference: RFC 1493 (ref. '18') (Obsoleted by RFC 4188) Summary: 22 errors (**), 0 flaws (~~), 12 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Remote Network Monitoring MIB Extensions for Switched Networks 2 Version 1.0 4 | 6 Sept. 12, 1997 | 8 Richard Waterman 9 Allot Networks Inc. | 10 rwaterma@msn.com 12 Bill Lahaye 13 Cabletron Systems 14 lahaye@ctron.com 16 Dan Romascanu 17 Madge Networks 18 dromasca@madge.com 20 Steve Waldbusser 21 INS 22 waldbusser@ins.com 24 Status of this Memo 26 This document is an Internet-Draft. Internet-Drafts are working 27 documents of the Internet Engineering Task Force (IETF), its areas, 28 and its working groups. Note that other groups may also distribute 29 working documents as Internet-Drafts. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet- Drafts as reference 34 material or to cite them other than as ``work in progress.'' 36 To learn the current status of any Internet-Draft, please check the 37 ``1id-abstracts.txt'' listing contained in the Internet- Drafts 38 Shadow Directories on ds.internic.net (US East Coast), nic.nordu.net 39 (Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific 40 Rim). 42 Abstract 44 This memo defines a portion of the Management Information Base (MIB) 45 for use with network management protocols in TCP/IP-based internets. 46 In particular, it defines objects for managing remote network 47 monitoring devices in switched networks environments. 49 Table of Contents 51 Status of this Memo 1 52 Abstract 1 53 1. The Network Management Framework 2 54 2. Overview 3 55 2.1 Remote Network Management Goals 4 56 2.2 Switched Networks Monitoring 5 57 2.3 Mechanisms for Monitoring Switched Networks 6 58 2.3.1 DataSource Objects 6 59 2.3.2 Copy Port 7 60 2.3.3 Vlan Monitoring 8 61 2.4 Relationship to Other MIBs 8 62 2.4.1 The RMON and RMON2 MIBs 8 63 2.4.2 The Interfaces Group MIB 9 64 2.4.3 The Entity MIB 9 65 2.4.4 The Bridge MIB 10 66 2.5 Relationship with IEEE 802.1 Standards 10 67 3. SMON/RMON Groups 10 68 3.1 SMON ProbeCapabilities 10 | 69 3.2 smonVlanStats 11 70 3.3 smonPrioStats 11 71 3.4 dataSourceCaps 11 72 3.5 portCopyConfig 11 73 4. Control of Remote Network Monitoring Devices 12 74 5. Definitions 13 75 6. References 34 | 76 7. Security Considerations 36 | 77 8. Authors' Addresses 36 | 79 1. The Network Management Framework 81 The Internet-standard Network Management Framework consists of three 82 components. They are: 84 RFC 1902 [1] which defines the SMI, the mechanisms used for 85 describing and naming objects for the purpose of management. 87 RFC 1213, STD 17, [3] which defines MIB-II, the core set of managed 88 objects for the Internet suite of protocols. 90 RFC 1905 [4] which defines the SNMP, the protocol used for network 91 access to managed objects. 93 The Framework permits new objects to be defined for the purpose of 94 experimentation and evaluation. 96 Managed objects are accessed via a virtual information store, termed 97 the Management Information Base or MIB. Within a given MIB module, 98 objects are defined using the SMI's OBJECT-TYPE macro. At a minimum, 99 each object has a name, a syntax, an access-level, and an 100 implementation-status. 102 The name is an object identifier, an administratively assigned name, 103 which specifies an object type. The object type together with an 104 object instance serves to uniquely identify a specific instantiation 105 of the object. For human convenience, we often use a textual string, 106 termed the object descriptor, to also refer to the object type. 108 The syntax of an object type defines the abstract data structure 109 corresponding to that object type. The ASN.1 [6] language is used for 110 this purpose. However, RFC 1902 purposely restricts the ASN.1 111 constructs which may be used. These restrictions are explicitly made 112 for simplicity. 114 The access-level of an object type defines whether it makes "protocol 115 sense" to read and/or write the value of an instance of the object 116 type. (This access-level is independent of any administrative 117 authorization policy.) 119 The implementation-status of an object type indicates whether the 120 object is mandatory, optional, obsolete, or deprecated. 122 2. Overview 124 This document continues the architecture created in the RMON MIB [12] 125 by providing RMON analysis for switched networks(SMON). 127 Remote network monitoring devices, often called monitors or probes, 128 are instruments that exist for the purpose of managing a network. 129 Often these remote probes are stand-alone devices and devote 130 significant internal resources for the sole purpose of managing a 131 network. An organization may employ many of these devices, one per 132 network segment, to manage its internet. In addition, these devices 133 may be used for a network management service provider to access a 134 client network, often geographically remote. 136 The objects defined in this document are intended as an interface 137 between an RMON agent and an RMON management application and are not 138 intended for direct manipulation by humans. While some users may 139 tolerate the direct display of some of these objects, few will 140 tolerate the complexity of manually manipulating objects to 141 accomplish row creation. These functions should be handled by the 142 management application. 144 2.1 Remote Network Management Goals 146 o Offline Operation 148 There are sometimes conditions when a management 149 station will not be in constant contact with its 150 remote monitoring devices. This is sometimes by 151 design in an attempt to lower communications costs 152 (especially when communicating over a WAN or 153 dialup link), or by accident as network failures 154 affect the communications between the management 155 station and the probe. 157 For this reason, this MIB allows a probe to be 158 configured to perform diagnostics and to collect 159 statistics continuously, even when communication with 160 the management station may not be possible or 161 efficient. The probe may then attempt to notify 162 the management station when an exceptional condition 163 occurs. Thus, even in circumstances where 164 communication between management station and probe is 165 not continuous, fault, performance, and configuration 166 information may be continuously accumulated and 167 communicated to the management station conveniently 168 and efficiently. 170 o Proactive Monitoring 172 Given the resources available on the monitor, it 173 is potentially helpful for it continuously to run 174 diagnostics and to log network performance. The 175 monitor is always available at the onset of any 176 failure. It can notify the management station of the 177 failure and can store historical statistical 178 information about the failure. This historical 179 information can be played back by the management 180 station in an attempt to perform further diagnosis 181 into the cause of the problem. 183 o Problem Detection and Reporting 185 The monitor can be configured to recognize 186 conditions, most notably error conditions, and 187 continuously to check for them. When one of these 188 conditions occurs, the event may be logged, and 189 management stations may be notified in a number of 190 ways. 192 o Value Added Data 194 Because a remote monitoring device represents a 195 network resource dedicated exclusively to network 196 management functions, and because it is located 197 directly on the monitored portion of the network, the 198 remote network monitoring device has the opportunity 199 to add significant value to the data it collects. 200 For instance, by highlighting those hosts on the 201 network that generate the most traffic or errors, the 202 probe can give the management station precisely the 203 information it needs to solve a class of problems. 205 o Multiple Managers 207 An organization may have multiple management stations 208 for different units of the organization, for different 209 functions (e.g. engineering and operations), and in an 210 attempt to provide disaster recovery. Because 211 environments with multiple management stations are 212 common, the remote network monitoring device has to | 213 deal with more than one management station, 214 potentially using its resources concurrently. 216 2.2 Switched Networks Monitoring 218 This document addresses issues related to applying "Remote 219 Technology" to Switch Networks. Switches today differ from standard 220 shared media protocols: 222 Data is not, in general, broadcast. This may be caused by the switch 223 architecture or by the connection-oriented nature of the data. This 224 means, therefore, the monitoring non-broadcast traffic needs to be 225 considered. 227 Monitoring the multiple entry and exit points from a switching device 228 requires a vast amount of resources - memory and CPU, and aggregation 229 of the data in logical packets of information, determined by the 230 application needs. 232 Switching incorporates logical segmentation such as Virtual LANs 233 (vLANs). 235 Switching incorporates packet prioritization. 237 Data across the switch fabric can be in the form of cells. Like RMON, 238 SMON is only concerned with the monitoring of packets. 240 Differences such as these make monitoring difficult. The current 241 RMON-1 and RMON-2 standards do not provide for things that are unique 242 to switches or switched environments. 244 In order to overcome the limitations of the existing standards, new 245 monitoring mechanisms have been implemented by vendors of switching 246 equipment. All these monitoring strategies are currently proprietary 247 in nature. 249 This document attempts to provide the framework to include different 250 switching strategies and allow for monitoring operations consistent 251 with the RMON framework. This MIB is limited to monitoring, and 252 control operations aimed in providing monitoring data for RMON 253 probes. 255 2.3 Mechanisms for Monitoring Switched Networks 257 The following mechanisms are used by SMON devices, for the purpose of 258 monitoring switched networks. 260 2.3.1 DataSource Objects 262 The RMON MIB standard [12] defines data source objects which point to 263 MIB-II interfaces, identified by instances of ifIndex objects. 265 The SMON MIB extends this concept and allows for other types of 266 objects to be defined as data sources for RMON and/or SMON data. 267 Three forms of dataSources are described: 269 ifIndex. 271 Traditional RMON dataSources. Called 'port-based' 272 for ifType. not equal to 'propVirtual(53)'. 274 smonVlanDataSource. 276 A dataSource of this form refers to a 'Packet-based VLAN' and 277 is called a 'VLAN-based' dataSource. is the VLAN ID, as 278 defined by the IEEE 802.1Q standard [14]. 280 entPhysicalEntry. 282 A dataSource of this form refers to a physical entity within 283 the agent and is called an 'entity-based' dataSource. 285 In addition to these new dataSource types, SMON introduces a new 286 group called dataSourceCapsTable to aid an NMS to discover dataSource 287 identity and attributes. 289 The extended data source mechanism supported by the SMON MIB allows 290 for the use of external collection points, similar to the one defined 291 and supported by the RMON-1 and RMON-2 MIBs, as well as internal 292 collection points(e.g. propVirtual ifTable entry, entPhysicalEntry). 293 The latter reflects either data sources which may be the result of 294 aggregation(e.g.switch-wide) or internal channels of physical 295 entities, which have the capability of being monitored by an SMON 296 probe. 298 2.3.2 Copy Port 300 In order to make the switching devices support RMON statistics, many 301 vendors have implemented a port copy feature, allowing traffic to be 302 replicated from switch port to switch port. Several levels of 303 configuration are possible: 305 1) 1 src port to 1 dst port 306 2) N src ports to 1 dst port 307 3) N src ports to M dst ports 309 The SMON standard presents a standard MIB interface which allows for 310 the control of this function. 312 Note that this function can apply to devices that have no other SMON 313 or RMON functionality than copy port. The agent of such a device 314 would support only the portCopyCaps and the portCopyConfig MIB 315 groups, out of the whole SMON MIB. Switch vendors are encouraged to 316 implement this subset of the SMON MIB, as it would allow for standard 317 port copy configuration from the same NMS application that does RMON 318 or SMON. 320 Port copy may cause congestion problems on the SMON device. This 321 situation is more likely occur when copying from a port of higher 322 speed to a port of lower speed or copy from multiple port to a single 323 port. 325 Particular implementations may chose to build protection mechanisms 326 that would prevent creation of new port copy links, when the capacity 327 of the destination port is exceeded. The MIB allows for 328 implementations to (if supported) instrument a destination drop count 329 on port copy to provide NMS applications a sense of the quality of 330 data presented at the destination port. 332 2.3.3 Vlan Monitoring 334 Vlan monitoring can be accomplished by using a VLAN-based dataSource 335 and/or by configuring smonVlanIdStats and/or smonVlanPrioStats 336 collections. These functions allow VLAN-ID or user priority 337 distributions per dataSource. Vlan monitoring provides a high-level 338 view of total Vlan usages and relative non-unicast traffic usage as 339 well as a profile of Vlan priority as defined in the 3-bit 340 user_priority field. 342 NOTE: priority stats reflect what was parsed from the packet, not 343 what priority, if any, was necessarily granted by the switch. 345 2.4 Relationship to Other MIBs 347 2.4.1 The RMON and RMON2 MIBs 349 The Remote Monitoring MIB (RMON-1) [12] provides several management 350 functions that may be directly or indirectly applicable to switched 351 networks. 353 The port copy mechanisms defined by the RMON MIB allow for the 354 destination ports to become data source for any RMON-1 statistics. 355 However, an NMS application should check whether it is in the device 356 capability(portCopyCap) to filter errors from a source to a 357 destination port and whether this capability is enabled, in order to 358 provide a correct interpretation of the copied port traffic. 360 RMON I host and matrix group statistics entries may be aggregated by 361 use of the extended dataSource capability defined in SMON. RMON II 362 groups are similarly extended through the use of SMON's dataSource 363 definition. 365 RMON-1 also defines a simple thresholding monitoring mechanism, 366 event-logging and event-notification for any MIB instance; SMON 367 utilizes the alarms and events groups from RMON-1 without 368 modification. These groups should be implemented on SMON devices if a 369 simple thresholding mechanism is desired. 371 The RMON II usrHistory group (user-defined history collection) should 372 be implemented by an SMON device if a history collection mechanism is 373 desired for smonStats entries. 375 2.4.2 The Interfaces Group MIB 377 The Interfaces Group MIB [5], [17] extends aspects of MIB-II [3]. 378 This document discusses the 'interfaces' group of MIB-II, especially 379 the experience gained from the definition of numerous media- specific 380 MIB modules for use in conjunction with the 'interfaces' group for 381 managing various sub-layers beneath the internetwork- layer. It 382 specifies clarifications to, and extensions of, the architectural 383 issues within the previous model used for the 'interfaces' group. 385 The Interfaces Group MIB also includes a MIB module. As well as 386 including new MIB definitions to support the architectural 387 extensions, this MIB module also re-specifies the 'interfaces' group 388 of MIB-II in a manner that is both compliant to the SNMPv2 SMI and 389 semantically- identical to the existing SNMPv1-based definitions. 391 The SMON MIB utilizes the propVirtual(53) ifType defined in The 392 Interfaces Group MIB [17] to provide SMON and RMON with new 393 dataSources such as Vlans and internal monitoring points. NMS 394 applications should consult the SMON dataSource capabilities group 395 (dataSourceCap) for a description of these virtual interfaces. 397 2.4.3 The Entity MIB 399 The scope of the Entity MIB [13] is to allow an NMS to interrogate a 400 standard SNMP context and thereby discover what logical and physical 401 entities exist, how to access the MIB information of each logical 402 entity, and the relationships between the various entities. The MIB 403 should support both a single agent or multiple agents in one physical 404 entity. 406 A "physical entity" or "physical component" represents an 407 identifiable physical resource within a managed system. Zero or more 408 logical entities may utilize a physical resource at any given time. 409 It is an implementation-specific manner as to which physical | 410 components are represented by an agent in the entPhysicalTable. 411 Typically, physical resources (e.g. communications ports, backplanes, 412 sensors, daughter-cards, power supplies, the overall chassis, the 413 overall switch), which can be managed via functions associated with 414 one or more logical entities are included in the MIB. 416 The SMON MIB does not mandate Entity MIB support, but allows for 417 physical entities, as defined by this MIB to be defined as SMON data 418 sources. For such cases, the support for the entPhysicalTable is | 419 required. 421 2.4.4 The Bridge MIB 423 One of the important indicators for measuring the effectiveness of a 424 switching device is the ratio between the number of forwarded frames 425 and the number of dropped frames at the switch port. 427 It is out of the scope of this MIB to provide instrumentation 428 information relative to switching devices. However, such indication 429 may be part of other MIB modules. 431 For instance the Bridge MIB [18] provides such MIB objects, for the 432 802.1 bridges (dot1dTpPortInFrames, dot1dTpPortInDiscards) and 433 switches managed according to the 802.1 bridge model may provide this 434 information. 436 2.5 Relationship with IEEE 802.1 Standards 438 The SMON MIB provides simple statistics per vLAN and priority levels. 439 Those two categories of statistics are of higher importance for 440 switched networks managers. Interoperability for those features is 441 ensured by the use of the IEEE 802.1 p/Q standards ([14], [15]) 442 defined by the IEEE 802.1 WG. Interoperability from the SMON MIB 443 point of view is ensured by referencing the IEEE definition of vLANs 444 and priority levels, for the SMON statistics. 446 3. SMON Groups | 448 3.1 SMON ProbeCapabilities | 450 The SMON probeCapabilities BITS object covers the following four | 451 capabilities. 453 - smonVlanStats(1) | 454 The probe supports the smonVlanStats object group. 456 - smonPrioStats(2) | 457 The probe supports the smonPrioStats object group. 459 - dataSource(3) | 460 The probe supports the dataSource object group. 462 - portCopy(4) | 463 The probe supports the portCopy object group. 465 * 467 3.2 smonVlanStats 469 The smonVlanStats MIB group includes the control and statistics 470 objects related to 802.1q Vlans. Specific statistics per 802.1q 471 virtual LAN are supported. The group provides a high level view of 472 total Vlan usage, and relative non-unicast traffic usage. 474 It is an implementation-specific matter as to how the agent 475 determines the proper default-VLAN for untagged or priority-tagged 476 frames. 478 3.3 smonPrioStats 480 The smonPrioStatsTable provides a distribution based on the 481 user_priority field in the VLAN header. 483 Note that this table merely reports priority as encoded in VLAN 484 headers, not the priority (if any) given the frame for actual 485 switching purposes. 487 3.4 dataSourceCaps 489 The dataSourceCaps MIB group identifies all supported data sources on 490 an SMON device. An NMS may use this table to discover the RMON and 491 Copy Port attributes of each data source. 493 Upon restart of the agent, the dataSourceTable, ifTable and 494 entPhysicalTable are initialized for the available data sources. The 495 agent may modify these tables as data sources become known or are 496 removed(e.g. hot swap of interfaces, chassis cards or the discovery 497 of Vlan usage). It is understood that dataSources representing VLANs 498 may not always be instantiated immediately upon restart, but rather 499 as VLAN usage is detected by the agent. The agent should attempt to 500 create dataSource and interface entries for all dataSources as soon 501 as possible. 503 For each dataSourceCapsEntry representing a VLAN or entPhysicalEntry, 504 the agent must create an associated ifEntry with a ifType value of 505 'propVirtual(53)'. This ifEntry will be used as the actual value in 506 RMON control table dataSource objects. The assigned ifIndex value is 507 copied into the associated dataSourceCapsIfIndex object. 509 3.5 portCopyConfig 511 The portCopyConfig MIB group includes the objects defined for the 512 control of the port copy functionality in a device. 514 The standard does not place a limit on the mode by which this copy 515 function may be used: 517 Mode 1 -- 1:1 Copy 519 Single dataSource copied to a single destination dataSource. 520 Agent may limit configuration based on ifTypes, ifSpeeds, half- 521 duplex/full-duplex, or agent resources. In this mode the single 522 instance of the portCopyDestDropEvents object refers to dropped 523 frames on the portCopyDest interface. 525 Mode 2 -- N:1 Copy 527 Multiple dataSources copied to a single destination dataSource. 528 Agent may limit configuration based on ifTypes, ifSpeeds, half- 529 duplex/full-duplex, portCopyDest over-subscription, or agent 530 resources. In this mode all N instances of the 531 portCopyDestDropEvents object should contain the same value, and 532 refer to dropped frames on the portCopyDest interface. 534 Mode 3 -- N:M Copy 536 Multiple dataSources copied to multiple destination dataSources. 537 Agent may limit configuration based on ifTypes, ifSpeeds, half- 538 duplex/full-duplex, portCopyDest over-subscription, or agent 539 resources. Since portCopyDestDropEvents is kept per destination 540 port, all instances of the portCopyDestDropEvents object 541 associated with(indexed by) a given portCopyDest should have the 542 same value(i.e. replicated or aliased for each instance associated 543 with a given portCopyDest). 545 The rows do not have an OwnerString, since multiple rows may be part 546 of the same portCopy operation. The agent is expected to activate or 547 deactivate entries one at a time, based on the rowStatus for the 548 given row. This can lead to unpredictable results in Modes 2 and 3 549 in applications utilizing the portCopy target traffic, if multiple 550 PDUs are used to fully configure the operation. It is recommended 551 that an entire portCopy operation be configured in one SetRequest PDU 552 if possible. 554 The portCopyDest object may not reference an interface associated 555 with a packet-based VLAN (rmonVlanDataSource.V), but this dataSource 556 type may be used as a portCopySource. 558 4. Control of Remote Network Monitoring Devices 560 Due to the complex nature of the available functions in these 561 devices, the functions often need user configuration. In many cases, 562 the function requires parameters to be set up for a data collection 563 operation. The operation can proceed only after these parameters are 564 fully set up. 566 Many functional groups in this MIB have one or more tables in which 567 to set up control parameters, and one or more data tables in which to 568 place the results of the operation. The control tables are typically 569 read/write in nature, while the data tables are typically read/only. 570 Because the parameters in the control table often describe resulting 571 data in the data table, many of the parameters can be modified only 572 when the control entry is not active. Thus, the method for modifying 573 these parameters is to de-activate the entry, perform the SNMP Set 574 operations to modify the entry, and then re-activate the entry. 575 Deleting the control entry causes the deletion of any associated data 576 entries, which also gives a convenient method for reclaiming the 577 resources used by the associated data. 579 Some objects in this MIB provide a mechanism to execute an action on 580 the remote monitoring device. These objects may execute an action as 581 a result of a change in the state of the object. For those objects 582 in this MIB, a request to set an object to the same value as it 583 currently holds would thus cause no action to occur. 585 To facilitate control by multiple managers, resources have to be 586 shared among the managers. These resources are typically the memory 587 and computation resources that a function requires. 589 The control mechanisms defined and used in this MIB are the same as 590 those defined in the RMON MIB [11], for control functionality and 591 interaction with multiple managers. 593 5. Definitions 595 SMON-MIB DEFINITIONS ::= BEGIN 597 IMPORTS 598 MODULE-IDENTITY, OBJECT-TYPE, Counter32, 599 Integer32, Counter64, experimental | 600 FROM SNMPv2-SMI 601 mib-2, ifType 602 FROM RFC1213-MIB 603 RowStatus, TEXTUAL-CONVENTION 604 FROM SNMPv2-TC 605 OwnerString 606 FROM RMON-MIB 607 LastCreateTime, DataSource, rmonConformance 608 FROM RMON2-MIB 609 InterfaceIndex 610 FROM IF-MIB 611 probeConfig | 612 FROM RMON2-MIB | 613 MODULE-COMPLIANCE, OBJECT-GROUP 614 FROM SNMPv2-CONF; 616 switchRMON MODULE-IDENTITY 617 LAST-UPDATED "9707030000Z" 618 ORGANIZATION "IETF RMON MIB Working Group" 619 CONTACT-INFO 620 "IETF RMONMIB WG Mailing list: rmonmib@cisco.com 622 Rich Waterman 623 Allot Networks Inc. 624 Phone: +1 408 559 0253 625 Email: rwaterma@msn.com 627 Bill Lahaye 628 Cabletron Systems 629 Phone: +1 603 337 5211 630 Email: lahaye@ctron.com 632 Dan Romascanu 633 Madge Networks 634 Phone: +972 3 645 8414 635 Email: dromasca@madge.com 637 Steven Waldbusser 638 International Network Services 639 Phone: (415) 254-4251 640 EMail: waldbusser@ins.com" 642 DESCRIPTION 643 "The MIB module for managing remote monitoring device 644 implementations for Switched Networks" 645 ::= { experimental 1000 } 647 smonMIBObjects OBJECT IDENTIFIER ::= { switchRMON 1 } 649 dataSourceCaps OBJECT IDENTIFIER ::= {smonMIBObjects 1} 650 smonStats OBJECT IDENTIFIER ::= {smonMIBObjects 2} 651 portCopyConfig OBJECT IDENTIFIER ::= {smonMIBObjects 3} 652 smonRegistrationPoints OBJECT IDENTIFIER ::= {smonMIBObjects 4} 654 -- Textual Conventions 655 -- 656 SmonDataSource ::= TEXTUAL-CONVENTION 657 STATUS current 658 DESCRIPTION 659 "Identifies the source of the data that the associated function 660 is configured to analyse. This macro extends the DataSource 661 Textual Convention defined by RMON-2 [11] to the following data 662 source types: 664 - ifIndex. 665 DataSources of this traditional form are called 'port-based', 666 but only if ifType. is not equal to 'propVirtual(53)'. 668 - smonVlanDataSource. 669 A dataSource of this form refers to a 'Packet-based VLAN' and 670 is called a 'VLAN-based' dataSource. is the VLAN ID, as defined 671 by the IEEE 802.1Q standard [14]. 673 - entPhysicalEntry. 674 A dataSource of this form refers to a physical entity within 675 the agent (e.g. entPhysicalClass = backplane(4)) and is called 676 an 'entity-based' dataSource." 677 SYNTAX OBJECT IDENTIFIER 678 -- | 679 -- The smonCapabilities object describes SMON agent capabilites | 680 -- | 681 -- | 682 smonCapabilities OBJECT-TYPE | 683 SYNTAX BITS { | 684 smonVlanStats(1), | 685 smonPrioStats(2), | 686 dataSource(3), | 687 portCopy(4) | 688 } | 689 MAX-ACCESS read-only | 690 STATUS current | 691 DESCRIPTION | 692 "An indication of the SMON MIB groups supported | 693 by this agent." | 694 ::= { probeConfig 15 } | 696 -- dataSourceCaps MIB group - defines SMON data source and port copy | 697 -- capabilities for devices supporting SMON. 699 -- A NMS application will check this MIB group and retrieve information about 700 -- the SMON capabilities of the device before applying SMON control operations 701 -- to the device. 703 -- dataSourceCapsTable: defines capabilities of RMON data sources 705 dataSourceCapsTable OBJECT-TYPE 706 SYNTAX SEQUENCE OF DataSourceCapsEntry 707 MAX-ACCESS not-accessible 708 STATUS current 709 DESCRIPTION 710 "This table describes RMON data sources and port copy capabilities. 711 An NMS may use this table to discover the identity and attributes of 712 the data sources on a given agent implementation. Similar to the 713 probeCapabilities object, actual row-creation operations will succeed 714 or fail based on the resources available and parameter values used 715 in each row-creation operation. 717 Upon restart of the RMON agent, the dataSourceTable, ifTable, and 718 perhaps entPhysicalTable are initialized for the available dataSources. 720 For each dataSourceCapsEntry representing a VLAN or entPhysicalEntry 721 the agent must create an associated ifEntry with a ifType value of 722 'propVirtual(53)'. This ifEntry will be used as the actual value 723 in RMON control table dataSource objects. The assigned ifIndex value 724 is copied into the associated dataSourceCapsIfIndex object. 726 It is understood that dataSources representing VLANs may not always 727 be instantiated immediately upon restart, but rather as VLAN usage 728 is detected by the agent. The agent should attempt to create 729 dataSource and interface entries for all dataSources as soon as 730 possible." 731 ::= { dataSourceCaps 1 } 733 dataSourceCapsEntry OBJECT-TYPE 734 SYNTAX DataSourceCapsEntry 735 MAX-ACCESS not-accessible 736 STATUS current 737 DESCRIPTION 738 "Entries per data source containing descriptions of data source and 739 port copy capabilities. This table is populated by the RMON agent 740 with one entry for each supported data source." 741 INDEX { IMPLIED dataSourceCapsObject } 742 ::= { dataSourceCapsTable 1 } 744 DataSourceCapsEntry ::= SEQUENCE { 745 dataSourceCapsObject 746 SmonDataSource, 747 dataSourceRmonCaps 748 BITS, 749 dataSourceCopyCaps 750 BITS, 751 dataSourceCapsIfIndex 752 InterfaceIndex 753 } 755 dataSourceCapsObject OBJECT-TYPE 756 SYNTAX SmonDataSource 757 MAX-ACCESS not-accessible 758 STATUS current 759 DESCRIPTION 760 "Defines an object that can be a SMON data source or a 761 source or a destination for a port copy operation." 762 ::= { dataSourceCapsEntry 1 } 764 dataSourceRmonCaps OBJECT-TYPE 765 SYNTAX BITS { 766 countErrFrames(0), 767 countAllGoodFrames(1), 768 countAnyRmonTables(2), | 769 babyGiantsCountAsGood(3), | 770 countNUcastOctets(4) | 771 } 772 MAX-ACCESS read-only 773 STATUS current 774 DESCRIPTION 775 " General attributes of the specified dataSource. 776 Note that these are static attributes, which should not 777 be adjusted because of current resources or configuration. 779 - countErrFrames(0) 780 The agent sets this bit for the dataSource if errored frames 781 received on this dataSource can actually be monitored by the agent. 782 The agent clears this bit is any errored frames are not visible to 783 the RMON data collector. 785 - countAllGoodFrames(1) 786 The agent sets this bit for the dataSource if all good frames received 787 on this dataSource can actually be monitored by the agent. 788 The agent clears this bit if any good frames are not visible for RMON 789 collection, e.g., the dataSource is a non-promiscuous interface or an 790 internal switch interface which may not receive frames which were | 791 switched in hardware or dropped by the bridge forwarding function. 793 - countAnyRmonTables(2) 794 The agent sets this bit if this dataSource can actually be used in 795 any of the implemented RMON tables, resources notwithstanding. 796 The agent clears this bit if this dataSourceCapsEntry is present 797 simply to identify a dataSource that may only be used as 798 portCopySource and/or a portCopyDest, but not the source of an 799 actual RMON data collection. | 801 - babyGiantsCountAsGood(3) | 802 The agent sets this bit if it can distinguish, for counting purposes,| 803 between true giant frames and frames that are larger than the media's| 804 'normal' maximum frame size due to Vlan tagging('baby giants'). | 806 Agents not capable of detecting 'baby giants' will clear this bit | 807 and, for example on ethernet, will view all frames less than or equal| 808 to 1518 octets as 'good frames' and all frames larger than 1518 octets| 809 as 'bad frames' for the purpose of counting in the smonVlanIdStats and | 810 smonVlanPrioStats tables. | 812 Agents capable of detecting 'baby giants' shall consider them as | 813 'good frames' for the purpose of counting in the smonVlanIdStats | 814 and smonVlanPrioStats tables." | 815 | 816 - countNUcastOctets(4) | 817 The agent sets this bit if it is capable of counting non-unicast | 818 octets on this dataSource. Note that if this bit is set the | 819 smonVlanStatsExtGroup becomes mandatory | 821 ::= { dataSourceCapsEntry 2 } 823 dataSourceCopyCaps OBJECT-TYPE 824 SYNTAX BITS { 825 copySourcePort(0), 826 copyDestPort(1), 827 copySrcTxTraffic(2), 828 copySrcRxTraffic(3), 829 countDestDropEvents(4), 830 copyErrFrames(5), 831 copyUnalteredFrames(6), 832 copyAllGoodFrames(7) 833 } 834 MAX-ACCESS read-only 835 STATUS current 836 DESCRIPTION 837 " PortCopy function capabilities of the specified dataSource. 838 Note that these are static capabilities, which should not be adjusted 839 because of current resources or configuration. 841 - copySourcePort(0) 842 The agent sets this bit if this dataSource is capable of acting 843 as a source of a portCopy operation. The agent clears this bit 844 otherwise. 846 - copyDestPort(1) 847 The agent sets this bit if this dataSource is capable of acting as 848 a destination of a portCopy operation. The agent clears this bit 849 otherwise. 851 - copySrcTxTraffic(2) 852 If the copySourcePort bit is set: 853 The agent sets this bit if this dataSource is capable of 854 copying frames transmitted out this portCopy source. 855 The agent clears this bit otherwise. This function is 856 needed to support full-duplex ports. 857 Else this bit should be cleared. 859 - copySrcRxTraffic(3) 860 If the copySourcePort bit is set: 861 The agent sets this bit if this dataSource is capable of 862 copying frames received on this portCopy source. 863 The agent clears this bit otherwise. This function is 864 needed to support full-duplex ports. 865 Else this bit should be cleared. 867 - countDestDropEvents(4) 868 If the copyDestPort bit is set: 869 The agent sets this bit if it is capable of incrementing 870 portCopyDestDropEvents, when this dataSource is the target 871 of a portCopy operation and a frame destined to this dataSource is 872 dropped (for RMON counting purposes). 873 Else this BIT should be cleared. 875 - copyErrFrames(5) 876 If the copySourcePort bit is set: 877 The agent sets this bit if it is capable of copying all errored 878 frames from this portCopy source-port, for errored frames 879 received on this dataSource. 880 Else this BIT should be cleared. 882 - copyUnalteredFrames(6) 883 If the copySourcePort bit is set: 884 The agent sets this bit if it is capable of copying all frames 885 from this portCopy source-port without alteration in any way; 886 including, but not limited to: 887 - truncation (with or without CRC regeneration) 888 - proprietary header insertion 889 - MAC header rewrite 890 - VLAN retagging 891 Else this bit should be cleared. 893 - copyAllGoodFrames(7) 894 If the copySourcePort bit is set: 895 The agent sets this bit for the dataSource if all good frames 896 received on this dataSource are normally capable of being copied 897 by the agent. The agent clears this bit if any good frames are 898 not visible for the RMON portCopy operation, e.g., the dataSource 899 is a non-promiscuous interface or an internal switch interface 900 which may not receive frames which were switched in hardware or 901 dropped by the bridge forwarding function. 902 Else this bit should be cleared." 904 ::= { dataSourceCapsEntry 3 } | 906 dataSourceCapsIfIndex OBJECT-TYPE 907 SYNTAX InterfaceIndex 908 MAX-ACCESS read-only 909 STATUS current 910 DESCRIPTION 911 "This object contains the ifIndex value of the ifEntry associated 912 with this smonDataSource." 913 ::= { dataSourceCapsEntry 4 } 915 -- The SMON Statistics MIB Group 917 -- aggregated statistics for IEEE 802.1Q VLAN environments. 919 -- VLAN statistics can be gathered in two different ways; either by using a 920 -- dataSource referencing a VLAN (sec. 3.3.6) or by configuring 921 -- smonVlanIdStats and/or smonVlanPrioStats collections. These functions 922 -- allow a VLAN-ID or user priority distributions per dataSource, 923 -- auto-populated by the agent in a manner similar to the RMON1 hostTable. 925 -- Only good frames are counted in the tables described in this section. 927 -- VLAN ID Stats 929 -- smonVlanStatsControlTable allows configuration of VLAN-ID collections. 931 smonVlanStatsControlTable OBJECT-TYPE 932 SYNTAX SEQUENCE OF SmonVlanStatsControlEntry 933 MAX-ACCESS not-accessible 934 STATUS current 935 DESCRIPTION 936 "Controls the setup of vLAN statistics tables." 937 ::= { smonStats 1 } 939 smonVlanStatsControlEntry OBJECT-TYPE 940 SYNTAX SmonVlanStatsControlEntry 941 MAX-ACCESS not-accessible 942 STATUS current 943 DESCRIPTION 944 "A conceptual row in the smonVlanStatsControlTable. 945 An example of the indexing of this entry is 946 smonVlanStatsControlCreateTime.7" 947 INDEX { smonVlanStatsControlIndex } 948 ::= { smonVlanStatsControlTable 1 } 950 SmonVlanStatsControlEntry ::= SEQUENCE { 951 smonVlanStatsControlIndex Integer32, 952 smonVlanStatsControlDataSource SmonDataSource, 953 smonVlanStatsControlCreateTime LastCreateTime, 954 smonVlanStatsControlOwner OwnerString, 955 smonVlanStatsControlStatus RowStatus 956 } 958 smonVlanStatsControlIndex OBJECT-TYPE 959 SYNTAX Integer32 (1..65535) 960 MAX-ACCESS not-accessible 961 STATUS current 962 DESCRIPTION 963 "A unique arbitrary index for this smonVlanStatsControlEntry." 964 ::= { smonVlanStatsControlEntry 1 } 966 smonVlanStatsControlDataSource OBJECT-TYPE 967 SYNTAX SmonDataSource 968 MAX-ACCESS read-create 969 STATUS current 970 DESCRIPTION 971 "The source of data for this set of vLAN statistics. 973 This object may not be modified if the associated 974 smonVlanStatsControlStatus object is equal to active(1)." 975 ::= { smonVlanStatsControlEntry 2 } 977 smonVlanStatsControlCreateTime OBJECT-TYPE 978 SYNTAX LastCreateTime 979 MAX-ACCESS read-only 980 STATUS current 981 DESCRIPTION 982 "The value of sysUpTime when this control entry was last 983 activated. This can be used by the management station to 984 ensure that the table has not been deleted and recreated 985 between polls." 986 ::= { smonVlanStatsControlEntry 3 } 988 smonVlanStatsControlOwner OBJECT-TYPE 989 SYNTAX OwnerString 990 MAX-ACCESS read-create 991 STATUS current 992 DESCRIPTION 993 "The entity that configured this entry and is 994 therefore using the resources assigned to it." 995 ::= { smonVlanStatsControlEntry 4 } 997 smonVlanStatsControlStatus OBJECT-TYPE 998 SYNTAX RowStatus 999 MAX-ACCESS read-create 1000 STATUS current 1001 DESCRIPTION 1002 "The status of this row. 1004 An entry may not exist in the active state unless all 1005 objects in the entry have an appropriate value. 1007 If this object is not equal to active(1), all associated 1008 entries in the smonVlanIdStatsTable shall be deleted." 1009 ::= { smonVlanStatsControlEntry 5 } 1011 -- The VLAN Statistics Table 1012 -- The smonVlanIdStatsTable provides a distribution based on the IEEE 802.1Q 1013 -- VLAN-ID (VID), for each frame attributed to the data source for the 1014 -- collection. 1016 -- This function applies the same rules for attributing frames to VLAN-based 1017 -- collections. RMON VLAN statistics are collected after the Ingress Rules 1018 -- defined in section 3.13 of the VLAN Specification (P802.1Q/D4) 1019 -- are applied. 1021 -- It is possible that entries in this table will be garbage-collected, based 1022 -- on agent resources, and VLAN configuration. Agents are encouraged to 1023 -- support all 4096 index values and not garbage collect this table. 1025 smonVlanIdStatsTable OBJECT-TYPE 1026 SYNTAX SEQUENCE OF SmonVlanIdStatsEntry 1027 MAX-ACCESS not-accessible 1028 STATUS current 1029 DESCRIPTION 1030 "Contains the vLAN statistics data." 1031 ::= { smonStats 2 } 1033 smonVlanIdStatsEntry OBJECT-TYPE 1034 SYNTAX SmonVlanIdStatsEntry 1035 MAX-ACCESS not-accessible 1036 STATUS current 1037 DESCRIPTION 1038 "A conceptual row in smonVlanIdStatsTable." 1039 INDEX { smonVlanStatsControlIndex, smonVlanIdStatsId } 1040 ::= { smonVlanIdStatsTable 1 } 1042 SmonVlanIdStatsEntry ::= SEQUENCE { 1043 smonVlanIdStatsId Integer32, 1044 smonVlanIdStatsTotalPkts Counter32, 1045 smonVlanIdStatsTotalOverflowPkts Counter32, 1046 smonVlanIdStatsTotalHCPkts Counter64, 1047 smonVlanIdStatsTotalOctets Counter32, 1048 smonVlanIdStatsTotalOverflowOctets Counter32, 1049 smonVlanIdStatsTotalHCOctets Counter64, 1050 smonVlanIdStatsNUcastPkts Counter32, 1051 smonVlanIdStatsNUcastOverflowPkts Counter32, 1052 smonVlanIdStatsNUcastHCPkts Counter64, 1053 smonVlanIdStatsNUcastOctets Counter32, 1054 smonVlanIdStatsNUcastOverflowOctets Counter32, 1055 smonVlanIdStatsNUcastHCOctets Counter64, 1056 smonVlanIdStatsCreateTime LastCreateTime 1057 } 1059 smonVlanIdStatsId OBJECT-TYPE 1060 SYNTAX Integer32 (0..4095) 1061 MAX-ACCESS not-accessible 1062 STATUS current 1063 DESCRIPTION 1064 "The unique identifier of the vLAN monitored for 1065 this specific statistics collection. 1067 According to [14] tagged packets match the VID for the range between 1068 1 and 4095. An external RMON probe may detect VID=0 on a Inter Switch 1069 Link, in which case the packet belongs to a vLAN determined by the 1070 PVID of the ingress port. The vLAN belonging of such a packet can be 1071 determined only by a RMON probe internal to the switch." 1072 REFERENCE 1073 "Draft Standard for Virtual Bridged Local Area Networks, P802.1Q/D6, 1074 chapter 3.13" 1075 ::= { smonVlanIdStatsEntry 1 } 1077 smonVlanIdStatsTotalPkts OBJECT-TYPE 1078 SYNTAX Counter32 1079 MAX-ACCESS read-only 1080 STATUS current 1081 DESCRIPTION 1082 "The total number of packets counted on 1083 this vLAN." 1084 ::= { smonVlanIdStatsEntry 2 } 1086 smonVlanIdStatsTotalOverflowPkts OBJECT-TYPE 1087 SYNTAX Counter32 1088 MAX-ACCESS read-only 1089 STATUS current 1090 DESCRIPTION 1091 "The number of times the associated smonVlanIdStatsTotalPkts 1092 counter has overflowed." 1093 ::= { smonVlanIdStatsEntry 3 } 1095 smonVlanIdStatsTotalHCPkts OBJECT-TYPE 1096 SYNTAX Counter64 1097 MAX-ACCESS read-only 1098 STATUS current 1099 DESCRIPTION 1100 " The total number of packets counted on 1101 this vLAN." 1102 ::= { smonVlanIdStatsEntry 4 } 1104 smonVlanIdStatsTotalOctets OBJECT-TYPE 1105 SYNTAX Counter32 1106 MAX-ACCESS read-only 1107 STATUS current 1108 DESCRIPTION 1109 "The total number of octets counted on 1110 this vLAN." 1111 ::= { smonVlanIdStatsEntry 5 } 1113 smonVlanIdStatsTotalOverflowOctets OBJECT-TYPE 1114 SYNTAX Counter32 1115 MAX-ACCESS read-only 1116 STATUS current 1117 DESCRIPTION 1118 "The number of times the associated smonVlanIdStatsTotalOctets 1119 counter has overflowed." 1120 ::= { smonVlanIdStatsEntry 6 } 1122 smonVlanIdStatsTotalHCOctets OBJECT-TYPE 1123 SYNTAX Counter64 1124 MAX-ACCESS read-only 1125 STATUS current 1126 DESCRIPTION 1127 " The total number of octets counted on 1128 this vLAN." 1129 ::= { smonVlanIdStatsEntry 7 } 1131 smonVlanIdStatsNUcastPkts OBJECT-TYPE 1132 SYNTAX Counter32 1133 MAX-ACCESS read-only 1134 STATUS current 1135 DESCRIPTION 1136 "The total number of non-unicast packets counted on 1137 this vLAN." 1138 ::= { smonVlanIdStatsEntry 8 } 1140 smonVlanIdStatsNUcastOverflowPkts OBJECT-TYPE 1141 SYNTAX Counter32 1142 MAX-ACCESS read-only 1143 STATUS current 1144 DESCRIPTION 1145 "The number of times the associated smonVlanIdStatsNUcastPkts 1146 counter has overflowed." 1147 ::= { smonVlanIdStatsEntry 9 } 1149 smonVlanIdStatsNUcastHCPkts OBJECT-TYPE 1150 SYNTAX Counter64 1151 MAX-ACCESS read-only 1152 STATUS current 1153 DESCRIPTION 1154 " The total number of non-unicast packets counted on 1155 this vLAN." 1156 ::= { smonVlanIdStatsEntry 10 } 1158 smonVlanIdStatsNUcastOctets OBJECT-TYPE 1159 SYNTAX Counter32 1160 MAX-ACCESS read-only 1161 STATUS current 1162 DESCRIPTION 1163 "The total number of non-unicast octets counted on 1164 this vLAN." 1165 ::= { smonVlanIdStatsEntry 11 } 1167 smonVlanIdStatsNUcastOverflowOctets OBJECT-TYPE 1168 SYNTAX Counter32 1169 MAX-ACCESS read-only 1170 STATUS current 1171 DESCRIPTION 1172 "The number of times the associated smonVlanIdStatsNUcastOctets 1173 counter has overflowed." 1174 ::= { smonVlanIdStatsEntry 12 } 1176 smonVlanIdStatsNUcastHCOctets OBJECT-TYPE 1177 SYNTAX Counter64 1178 MAX-ACCESS read-only 1179 STATUS current 1180 DESCRIPTION 1181 " The total number of Non-unicast octets counted on 1182 this vLAN." 1183 ::= { smonVlanIdStatsEntry 13 } 1185 smonVlanIdStatsCreateTime OBJECT-TYPE 1186 SYNTAX LastCreateTime 1187 MAX-ACCESS read-only 1188 STATUS current 1189 DESCRIPTION 1190 "The value of sysUpTime when this entry was last activated. 1191 This can be used by the management station to ensure that the 1192 entry has not been deleted and recreated between polls." 1193 ::= { smonVlanIdStatsEntry 14 } 1195 -- smonPrioStatsControlTable allows configuration of collections based on the 1196 -- value of the 3-bit user priority field encoded in the TCI. Note that this 1197 -- table merely reports priority as encoded in the VLAN headers, not the 1198 -- priority (if any) given to the frame for the actual switching purposes. 1200 smonPrioStatsControlTable OBJECT-TYPE 1201 SYNTAX SEQUENCE OF SmonPrioStatsControlEntry 1202 MAX-ACCESS not-accessible 1203 STATUS current 1204 DESCRIPTION 1205 "Controls the setup of priority statistics tables." 1206 ::= { smonStats 3 } 1208 smonPrioStatsControlEntry OBJECT-TYPE 1209 SYNTAX SmonPrioStatsControlEntry 1210 MAX-ACCESS not-accessible 1211 STATUS current 1212 DESCRIPTION 1213 "A conceptual row in the smonPrioStatsControlTable. 1215 An example of the indexing of this entry is 1216 smonPrioStatsControlCreateTime.7" 1217 INDEX { smonPrioStatsControlIndex } 1218 ::= { smonPrioStatsControlTable 1 } 1220 SmonPrioStatsControlEntry ::= SEQUENCE { 1221 smonPrioStatsControlIndex Integer32, 1222 smonPrioStatsControlDataSource SmonDataSource, 1223 smonPrioStatsControlCreateTime LastCreateTime, 1224 smonPrioStatsControlOwner OwnerString, 1225 smonPrioStatsControlStatus RowStatus 1226 } 1228 smonPrioStatsControlIndex OBJECT-TYPE 1229 SYNTAX Integer32 (1..65535) 1230 MAX-ACCESS not-accessible 1231 STATUS current 1232 DESCRIPTION 1233 "A unique arbitrary index for this smonPrioStatsControlEntry." 1234 ::= { smonPrioStatsControlEntry 1 } 1236 smonPrioStatsControlDataSource OBJECT-TYPE 1237 SYNTAX SmonDataSource 1238 MAX-ACCESS read-create 1239 STATUS current 1240 DESCRIPTION 1241 "The source of data for this set of vLAN statistics. 1243 This object may not be modified if the associated 1244 smonPrioStatsControlStatus object is equal to active(1)." 1245 ::= { smonPrioStatsControlEntry 2 } 1247 smonPrioStatsControlCreateTime OBJECT-TYPE 1248 SYNTAX LastCreateTime 1249 MAX-ACCESS read-only 1250 STATUS current 1251 DESCRIPTION 1252 "The value of sysUpTime when this control entry was last 1253 activated. This can be used by the management station to 1254 ensure that the table has not been deleted and recreated 1255 between polls." 1256 ::= { smonPrioStatsControlEntry 3 } 1258 smonPrioStatsControlOwner OBJECT-TYPE 1259 SYNTAX OwnerString 1260 MAX-ACCESS read-create 1261 STATUS current 1262 DESCRIPTION 1263 "The entity that configured this entry and is 1264 therefore using the resources assigned to it." 1265 ::= { smonPrioStatsControlEntry 4 } 1267 smonPrioStatsControlStatus OBJECT-TYPE 1268 SYNTAX RowStatus 1269 MAX-ACCESS read-create 1270 STATUS current 1271 DESCRIPTION 1272 "The status of this row. 1274 An entry may not exist in the active state unless all 1275 objects in the entry have an appropriate value. 1277 If this object is not equal to active(1), all associated 1278 entries in the smonPrioStatsTable shall be deleted." 1279 ::= { smonPrioStatsControlEntry 5 } 1281 -- The Priority Statistics Table 1283 smonPrioStatsTable OBJECT-TYPE 1284 SYNTAX SEQUENCE OF SmonPrioStatsEntry 1285 MAX-ACCESS not-accessible 1286 STATUS current 1287 DESCRIPTION 1288 "Contains the priority statistics." 1289 ::= { smonStats 4 } 1291 smonPrioStatsEntry OBJECT-TYPE 1292 SYNTAX SmonPrioStatsEntry 1293 MAX-ACCESS not-accessible 1294 STATUS current 1295 DESCRIPTION 1296 "A conceptual row in smonPrioStatsTable." 1297 INDEX { smonPrioStatsControlIndex, smonPrioStatsId } 1298 ::= { smonPrioStatsTable 1 } 1300 SmonPrioStatsEntry ::= SEQUENCE { 1301 smonPrioStatsId Integer32, 1302 smonPrioStatsPkts Counter32, 1303 smonPrioStatsOverflowPkts Counter32, 1304 smonPrioStatsHCPkts Counter64, 1305 smonPrioStatsOctets Counter32, 1306 smonPrioStatsOverflowOctets Counter32, 1307 smonPrioStatsHCOctets Counter64 1308 } 1310 smonPrioStatsId OBJECT-TYPE 1311 SYNTAX Integer32 (0..7) 1312 MAX-ACCESS not-accessible 1313 STATUS current 1314 DESCRIPTION 1315 "The unique identifier of the priority level monitored for 1316 this specific statistics collection." 1317 REFERENCE 1318 " Draft Standard for Virtual Bridged Local Area Networks, P802.1Q/D6, 1319 chapter 4.3.2.1" 1320 ::= { smonPrioStatsEntry 1 } 1322 smonPrioStatsPkts OBJECT-TYPE 1323 SYNTAX Counter32 1324 MAX-ACCESS read-only 1325 STATUS current 1326 DESCRIPTION 1327 "The total number of packets counted on 1328 this priority level." 1329 ::= { smonPrioStatsEntry 2 } 1331 smonPrioStatsOverflowPkts OBJECT-TYPE 1332 SYNTAX Counter32 1333 MAX-ACCESS read-only 1334 STATUS current 1335 DESCRIPTION 1336 "The number of times the associated smonPrioStatsPkts 1337 counter has overflowed." 1338 ::= { smonPrioStatsEntry 3 } 1340 smonPrioStatsHCPkts OBJECT-TYPE 1341 SYNTAX Counter64 1342 MAX-ACCESS read-only 1343 STATUS current 1344 DESCRIPTION 1345 " The total number of packets counted on 1346 this priority level." 1347 ::= { smonPrioStatsEntry 4 } 1349 smonPrioStatsOctets OBJECT-TYPE 1350 SYNTAX Counter32 1351 MAX-ACCESS read-only 1352 STATUS current 1353 DESCRIPTION 1354 "The total number of octets counted on 1355 this priority level." 1356 ::= { smonPrioStatsEntry 5 } 1358 smonPrioStatsOverflowOctets OBJECT-TYPE 1359 SYNTAX Counter32 1360 MAX-ACCESS read-only 1361 STATUS current 1362 DESCRIPTION 1363 "The number of times the associated smonPrioStatsOctets 1364 counter has overflowed." 1365 ::= { smonPrioStatsEntry 6 } 1367 smonPrioStatsHCOctets OBJECT-TYPE 1368 SYNTAX Counter64 1369 MAX-ACCESS read-only 1370 STATUS current 1371 DESCRIPTION 1372 " The total number of octets counted on 1373 this priority level." 1374 ::= { smonPrioStatsEntry 7 } 1376 -- Port Copy provides the ability to copy all frames from a 1377 -- a specified source to specified destination within a switch. 1378 -- Source and destinations should be MIB-II interfaces 1379 -- One to one, one to many, many to one and many to many source 1380 -- to destination relationships may be configured. 1381 -- 1382 -- Applicable counters on the destination will increment for 1383 -- all packets transmitted, be it by normal bridging/switching 1384 -- or due to packet copy. 1385 -- Note that this table manages no RMON data collection by itself, | 1386 -- and an agent may possibly implement no other RMON objects except the 1387 -- probeCapabilities scalar, the dataSourceCapsTable, and this table. 1389 portCopyTable OBJECT-TYPE 1390 SYNTAX SEQUENCE OF PortCopyEntry 1391 MAX-ACCESS not-accessible 1392 STATUS current 1393 DESCRIPTION 1394 "This table provides the ability to configure the copy port 1395 functionality. Source and destinations should be MIB-II 1396 interfaces. 1397 One to one, many to one and one to many source to destination 1398 relationships may be configured. 1399 Each row that exists in this table defines such a 1400 relationship. By disabling a row in this table the port copy 1401 relationship no longer exists." 1402 ::= { portCopyConfig 1 } 1404 portCopyEntry OBJECT-TYPE 1405 SYNTAX PortCopyEntry 1406 MAX-ACCESS not-accessible 1407 STATUS current 1408 DESCRIPTION 1409 "Describes a particular port copy entry." 1410 INDEX { portCopySource, portCopyDest } 1411 ::= { portCopyTable 1 } 1413 PortCopyEntry ::= SEQUENCE { 1414 portCopySource 1415 InterfaceIndex, 1416 portCopyDest 1417 InterfaceIndex, 1418 portCopyDestDropEvents 1419 Counter32, 1420 portCopyStatus 1421 RowStatus 1422 } 1424 portCopySource OBJECT-TYPE 1425 SYNTAX InterfaceIndex (1..65535) 1426 MAX-ACCESS not-accessible 1427 STATUS current 1428 DESCRIPTION 1429 "The ifIndex of the source which will have all packets redirected to 1430 the destination as defined by portCopyDest." 1431 ::= { portCopyEntry 1 } 1433 portCopyDest OBJECT-TYPE 1434 SYNTAX InterfaceIndex (1..65535) 1435 MAX-ACCESS not-accessible 1436 STATUS current 1437 DESCRIPTION 1438 "Defines the ifIndex destination for the copy operation." 1439 ::= { portCopyEntry 2 } 1441 portCopyDestDropEvents OBJECT-TYPE 1442 SYNTAX Counter32 1443 MAX-ACCESS read-only 1444 STATUS current 1445 DESCRIPTION 1446 "The total number of events in which port copy packets 1447 were dropped by the switch at the destination port due to 1448 lack of resources. 1449 Note that this number is not necessarily the number of 1450 packets dropped; it is just the number of times this 1451 condition has been detected. 1452 A single dropped event counter is maintained for each 1453 portCopyDest. Thus all instances associated with a given 1454 portCopyDest will have the same portCopyDestDropEvents value " 1455 ::= { portCopyEntry 3 } 1457 portCopyStatus OBJECT-TYPE 1458 SYNTAX RowStatus 1459 MAX-ACCESS read-write 1460 STATUS current 1461 DESCRIPTION 1462 "Defines the status of the port copy entry." 1463 ::= { portCopyEntry 4 } 1465 -- smonRegistrationPoints 1466 -- defines a set of OIDs for registration purposes of entities 1467 -- supported by the SMON MIB. 1469 smonVlanDataSource OBJECT IDENTIFIER ::= { smonRegistrationPoints 1} 1471 -- Defined for uses as an SmonDataSource. A single integer parameter 1472 -- is appended to the end of this OID when actually encountered in 1473 -- the dataSourceCapsTable, which represents a positive, non-zero VLAN 1474 -- identifier value. 1476 -- Conformance Macros 1478 smonMIBCompliances OBJECT IDENTIFIER ::= { rmonConformance 3} 1479 smonMIBGroups OBJECT IDENTIFIER ::= { rmonConformance 4} 1481 smonMIBCompliance MODULE-COMPLIANCE 1482 STATUS current 1483 DESCRIPTION 1484 "Describes the requirements for full conformance with the SMON MIB" 1485 MODULE -- this module 1486 MANDATORY-GROUPS {dataSourceCapsGroup, 1487 smonVlanStatsGroup, 1488 smonPrioStatsGroup, 1489 portCopyConfigGroup | 1490 smonInformationGroup} | 1491 GROUP smonVlanStatsExtGroup | 1492 DESCRIPTION | 1493 "The smonVlanStatsExtGroup is mandatory for systems | 1494 which can count Non-unicast octets for a given dataSource."| 1495 ::= { smonMIBCompliances 1 } 1497 smonMIBVlanStatsCompliance MODULE-COMPLIANCE 1498 STATUS current 1499 DESCRIPTION 1500 "Describes the requirements for conformance with the SMON MIB 1501 with support for VLAN Statistics. Mandatory for a SMON probe in 1502 environment where IEEE 802.1Q bridging is implemented." 1503 MODULE -- this module 1504 MANDATORY-GROUPS {dataSourceCapsGroup, 1505 smonVlanStatsGroup} 1506 ::= { smonMIBCompliances 2 } 1508 smonMIBPrioStatsCompliance MODULE-COMPLIANCE 1509 STATUS current 1510 DESCRIPTION 1511 "Describes the requirements for conformance with the SMON MIB 1512 with support for priority level Statistics. Mandatory for a SMON 1513 probe in a environment where IEEE 802.1p priority-switching is 1514 implemented." 1515 MODULE -- this module 1516 MANDATORY-GROUPS {dataSourceCapsGroup, 1517 smonPrioStatsGroup} 1518 ::= { smonMIBCompliances 3 } 1520 portCopyCompliance MODULE-COMPLIANCE 1521 STATUS current 1522 DESCRIPTION 1523 "Describes the requirements for conformance with the port copy 1524 functionality defined by the SMON MIB" 1525 MODULE -- this module 1526 MANDATORY-GROUPS {dataSourceCapsGroup, 1527 portCopyConfigGroup} 1528 ::= { smonMIBCompliances 4} 1530 dataSourceCapsGroup OBJECT-GROUP 1531 OBJECTS { dataSourceRmonCaps, 1532 dataSourceCopyCaps, 1533 dataSourceCapsIfIndex} 1534 STATUS current 1535 DESCRIPTION 1536 "Defines the objects that describe the capabilities of RMON data 1537 sources." 1538 ::= {smonMIBGroups 1 } 1540 smonVlanStatsGroup OBJECT-GROUP 1541 OBJECTS { smonVlanStatsControlDataSource, 1542 smonVlanStatsControlCreateTime, 1543 smonVlanStatsControlOwner, 1544 smonVlanStatsControlStatus, 1545 smonVlanIdStatsTotalPkts, 1546 smonVlanIdStatsTotalOverflowPkts, 1547 smonVlanIdStatsTotalHCPkts, 1548 smonVlanIdStatsTotalOctets, 1549 smonVlanIdStatsTotalOverflowOctets, 1550 smonVlanIdStatsTotalHCOctets, 1551 smonVlanIdStatsNUcastPkts, 1552 smonVlanIdStatsNUcastOverflowPkts, 1553 smonVlanIdStatsNUcastHCPkts, 1554 smonVlanIdStatsCreateTime} * 1555 STATUS current 1556 DESCRIPTION 1557 "Defines the switch monitoring specific statistics - per vLAN Id." 1558 ::= { smonMIBGroups 2 } 1560 smonPrioStatsGroup OBJECT-GROUP 1561 OBJECTS { smonPrioStatsControlDataSource, 1562 smonPrioStatsControlCreateTime, 1563 smonPrioStatsControlOwner, 1564 smonPrioStatsControlStatus, 1565 smonPrioStatsPkts, 1566 smonPrioStatsOverflowPkts, 1567 smonPrioStatsHCPkts, 1568 smonPrioStatsOctets, 1569 smonPrioStatsOverflowOctets, 1570 smonPrioStatsHCOctets} 1571 STATUS current 1572 DESCRIPTION 1573 "Defines the switch monitoring specific statistics - per vLAN Id." 1574 ::= { smonMIBGroups 3 } 1576 smonVlanStatsExtGroup OBJECT-GROUP | 1577 OBJECTS {smonVlanIdStatsNUcastOctets, | 1578 smonVlanIdStatsNUcastOverflowOctets, | 1579 smonVlanIdStatsNUcastHCOctets} | 1580 STATUS current | 1581 DESCRIPTION | 1582 "Defines the switch monitoring specific statistics for systems capable| 1583 of counting non-unicast octets for a given dataSource(as described| 1584 in the dataSourceRmonCaps object." | 1585 ::= { smonMIBGroups 4 } | 1587 smonInformationGroup OBJECT-GROUP | 1588 OBJECTS { smonCapabilities } | 1589 STATUS current | 1590 DESCRIPTION | 1591 "An indication of the SMON capabilities support by this agent." | 1592 ::= { smonMIBGroups 5 } | 1594 portCopyConfigGroup OBJECT-GROUP 1595 OBJECTS { portCopyDestDropEvents, 1596 portCopyStatus 1597 } 1598 STATUS current 1599 DESCRIPTION 1600 "Defines the control objects for copy port operations" 1601 ::= { smonMIBGroups 6 } | 1603 END 1605 6. References 1607 [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 1608 S. Waldbusser, "Structure of Management Information for version 2 1609 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, 1610 January 1996. 1612 [2] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 1613 S. Waldbusser, "Textual Conventions for version 2 of the Simple 1614 Network Management Protocol (SNMPv2)", RFC 1903, January 1996. 1616 [3] McCloghrie, K., and M. Rose, Editors, "Management Information Base 1617 for Network Management of TCP/IP-based internets: MIB-II", STD 17, 1618 RFC 1213, Hughes LAN Systems, Performance Systems International, 1619 March 1991. 1621 [4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 1622 S. Waldbusser, "Protocol Operations for version 2 of the Simple 1623 Network Management Protocol (SNMPv2)", RFC 1905, January 1996. 1625 [5] McCloghrie, K., and Kastenholtz, F., "Interfaces Group Evolution", 1626 RFC 1573, Hughes LAN Systems, FTP Software, January 1994. 1628 [6] Information Processing Systems -- Open Systems Interconnection -- 1629 Specification of Abstract Syntax Notation One (ASN.1), International 1630 Organization for Standardization. International Standard 8824, 1631 (December, 1987) 1633 [7] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 1634 S. Waldbusser, "Conformance Statements for version 2 of the Simple 1635 Network Management Protocol (SNMPv2)", RFC 1904, January 1996. 1637 [8] Case, J., M. Fedor, M. Schoffstall, J. Davin, "Simple Network 1638 Management Protocol", RFC 1157, SNMP Research, Performance Systems 1639 International, MIT Laboratory for Computer Science, May 1990. 1641 [9] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 1642 S. Waldbusser, "Transport Mappings for version 2 of the Simple 1643 Network Management Protocol (SNMPv2)", RFC 1906, January 1996. 1645 [10] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 1646 S. Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, 1647 January 1996. 1649 [11] S. Waldbusser, "Remote Network Monitoring Management Information 1650 Base Version 2 using SMIv2", RFC 2021, January 1997. 1652 [12] S. Waldbusser, "Remote Network Monitoring Management 1653 Information Base", RFC 1757, February, 1995 1655 [13] K. McCloghrie, A. Bierman, "Entity MIB", RFC 2037, October1996 1657 [14] T. Jeffree, "Draft Standard for Virtual Bridged Local Area 1658 Networks", P802.1Q/D6, May 1997 1660 [15] T. Jeffree, "Standard for Local and Metropolitan Area Networks - 1661 Supplement to Media Access Control (MAC) Bridges: Traffic Class Expediting 1662 and Dynamic Multicast Filtering", P802.1p/D6, May 1997 1664 [16] K. De Graaf, D. Romascanu, D. McMaster, K. McCloghrie, "Definitions of 1665 Managed Objects for IEEE 802.3 Repeater Devices using SMIv2", RFC 2108, 1666 February 1997 1668 [17] K. McCloghrie, F. Kastenholz, "Interfaces Group MIB", 1669 draft-ietf-ifmib-mib-05.txt, November 1996 1671 [18] E.Decker, etc. - Definitions of Managed Objects for Bridges, 1672 RFC 1493, July 1993 1674 7. Security Considerations 1676 In order to implement this MIB, an agent must make certain management 1677 information available about various logical and physical entities 1678 within a managed system, which may be considered sensitive in some 1679 network environments. 1681 Therefore, a network administrator may wish to employ instance-level 1682 access control, and configure the Entity MIB access (i.e., community 1683 strings in SNMPv1 and SNMPv2C), such that certain instances within 1684 this MIB, are excluded from particular MIB views. 1686 8. Authors' Addresses 1687 Richard Waterman 1688 Allot Networks Inc. | 1689 Email: rwaterma@msn.com 1691 Bill Lahaye 1692 Cabletron Systems 1693 Email: lahaye@ctron.com 1695 Dan Romascanu 1696 Madge Networks 1697 Atidim Technology Park, Bldg. 3 1698 Tel Aviv 61131 1699 Israel 1701 Steven Waldbusser 1702 International Network Services 1703 Phone: (415) 254-4251 1704 EMail: waldbusser@ins.com