idnits 2.17.1 draft-ietf-rmonmib-smon-01.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-19) 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 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 58 instances of too long lines in the document, the longest one being 7 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 224 has weird spacing: '...tecture or by...' == Line 305 has weird spacing: '...c ports to 1 ...' == Line 312 has weird spacing: '...ty than copy ...' == Line 1333 has weird spacing: '...rce and desti...' == Line 1403 has weird spacing: '... switch due t...' -- 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.) -- The document date (July 15, 1997) is 9775 days in the past. Is this intentional? 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 1550, but no explicit reference was found in the text == Unused Reference: '7' is defined on line 1571, but no explicit reference was found in the text == Unused Reference: '8' is defined on line 1575, but no explicit reference was found in the text == Unused Reference: '9' is defined on line 1579, but no explicit reference was found in the text == Unused Reference: '10' is defined on line 1583, but no explicit reference was found in the text == Unused Reference: '16' is defined on line 1602, 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 (~~), 13 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Remote Network Monitoring MIB Extensions for Switched Networks 3 Version 1.0 5 7 July 15, 1997 9 Richard Waterman 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. 47 In particular, it defines objects for managing remote network 48 monitoring devices in switched networks environments. 50 Table of Contents 52 Status of this Memo 1 53 Abstract 1 54 1. The Network Management Framework 3 55 2. Overview 3 56 2.1 Remote Network Management Goals 4 57 2.2 Switched Networks Monitoring 5 58 2.3 Mechanisms for Monitoring Switched Networks 6 59 2.3.1 DataSource Objects 6 60 2.3.2 Copy Port 7 61 2.3.3 Vlan Monitoring 8 62 2.4 Relationship to Other MIBs 9 63 2.4.1 The RMON and RMON2 MIBs 9 64 2.4.2 The Interfaces Group MIB 10 65 2.4.3 The Entity MIB 10 66 2.4.4 The Bridge MIB 11 67 2.5 Relationship with IEEE 802.1 Standards 11 68 3. SMON/RMON Groups 11 69 3.1 ProbeCapabilities Additions 11 70 3.2 smonVlanStats 12 71 3.3 smonPrioStats 12 72 3.4 dataSourceCaps 12 73 3.5 portCopyConfig 13 74 4. Control of Remote Network Monitoring Devices 14 75 5. Definitions 14 76 6. References 34 77 7. Security Considerations 36 78 8. Authors' Addresses 36 80 1. The Network Management Framework 82 The Internet-standard Network Management Framework consists of three 83 components. They are: 85 RFC 1902 [1] which defines the SMI, the mechanisms used for 86 describing and naming objects for the purpose of management. 88 RFC 1213, STD 17, [3] which defines MIB-II, the core set of managed 89 objects for the Internet suite of protocols. 91 RFC 1905 [4] which defines the SNMP, the protocol used for network 92 access to managed objects. 94 The Framework permits new objects to be defined for the purpose of 95 experimentation and evaluation. 97 Managed objects are accessed via a virtual information store, termed 98 the Management Information Base or MIB. Within a given MIB module, 99 objects are defined using the SMI's OBJECT-TYPE macro. At a minimum, 100 each object has a name, a syntax, an access-level, and an 101 implementation-status. 103 The name is an object identifier, an administratively assigned name, 104 which specifies an object type. The object type together with an 105 object instance serves to uniquely identify a specific instantiation 106 of the object. For human convenience, we often use a textual string, 107 termed the object descriptor, to also refer to the object type. 109 The syntax of an object type defines the abstract data structure 110 corresponding to that object type. The ASN.1 [6] language is used for 111 this purpose. However, RFC 1902 purposely restricts the ASN.1 112 constructs which may be used. These restrictions are explicitly made 113 for simplicity. 115 The access-level of an object type defines whether it makes "protocol 116 sense" to read and/or write the value of an instance of the object 117 type. (This access-level is independent of any administrative 118 authorization policy.) 120 The implementation-status of an object type indicates whether the 121 object is mandatory, optional, obsolete, or deprecated. 123 2. Overview 125 This document continues the architecture created in the RMON MIB [12] 126 by providing RMON analysis for switched networks(SMON). 128 Remote network monitoring devices, often called monitors or probes, 129 are instruments that exist for the purpose of managing a network. 130 Often these remote probes are stand-alone devices and devote 131 significant internal resources for the sole purpose of managing a 132 network. An organization may employ many of these devices, one per 133 network segment, to manage its internet. In addition, these devices 134 may be used for a network management service provider to access a 135 client network, often geographically remote. 137 The objects defined in this document are intended as an interface 138 between an RMON agent and an RMON management application and are not 139 intended for direct manipulation by humans. While some users may 140 tolerate the direct display of some of these objects, few will 141 tolerate the complexity of manually manipulating objects to 142 accomplish row creation. These functions should be handled by the 143 management application. 145 2.1 Remote Network Management Goals 147 o Offline Operation 149 There are sometimes conditions when a management 150 station will not be in constant contact with its 151 remote monitoring devices. This is sometimes by 152 design in an attempt to lower communications costs 153 (especially when communicating over a WAN or 154 dialup link), or by accident as network failures 155 affect the communications between the management 156 station and the probe. 158 For this reason, this MIB allows a probe to be 159 configured to perform diagnostics and to collect 160 statistics continuously, even when communication with 161 the management station may not be possible or 162 efficient. The probe may then attempt to notify 163 the management station when an exceptional condition 164 occurs. Thus, even in circumstances where 165 communication between management station and probe is 166 not continuous, fault, performance, and configuration 167 information may be continuously accumulated and 168 communicated to the management station conveniently 169 and efficiently. 171 o Proactive Monitoring 173 Given the resources available on the monitor, it 174 is potentially helpful for it continuously to run 175 diagnostics and to log network performance. The 176 monitor is always available at the onset of any 177 failure. It can notify the management station of the 178 failure and can store historical statistical 179 information about the failure. This historical 180 information can be played back by the management 181 station in an attempt to perform further diagnosis 182 into the cause of the problem. 184 o Problem Detection and Reporting 186 The monitor can be configured to recognize 187 conditions, most notably error conditions, and 188 continuously to check for them. When one of these 189 conditions occurs, the event may be logged, and 190 management stations may be notified in a number of 191 ways. 193 o Value Added Data 195 Because a remote monitoring device represents a 196 network resource dedicated exclusively to network 197 management functions, and because it is located 198 directly on the monitored portion of the network, the 199 remote network monitoring device has the opportunity 200 to add significant value to the data it collects. 201 For instance, by highlighting those hosts on the 202 network that generate the most traffic or errors, the 203 probe can give the management station precisely the 204 information it needs to solve a class of problems. 206 o Multiple Managers 208 An organization may have multiple management stations 209 for different units of the organization, for different 210 functions (e.g. engineering and operations), and in an 211 attempt to provide disaster recovery. Because 212 environments with multiple management stations are 213 common, the remote network monitoring device has to 214 deal with more than own management station, 215 potentially using its resources concurrently. 217 2.2 Switched Networks Monitoring 219 This document addresses issues related to applying "Remote 220 Technology" to Switch Networks. Switches today differ from standard 221 shared media protocols: 223 1) Data is not, in general, broadcast. This may be caused by the 224 switch architecture or by the connection-oriented nature of the 225 data. This means, therefore, the monitoring non-broadcast 226 traffic needs to be considered. 228 2) Monitoring the multiple entry and exit points from a switching 229 device requires a vast amount of resources - memory and CPU, and 230 aggregation of the data in logical packets of information, 231 determined by the application needs. 233 3) Switching incorporates logical segmentation such as Virtual LANs 234 (vLANs). 236 4) Switching incorporates packet prioritization. 238 5) Data across the switch fabric can be in the form of cells. Like 239 RMON, SMON is only concerned with the monitoring of packets. 241 Differences such as these make monitoring difficult. The current 242 RMON-1 and RMON-2 standards do not provide for things that are unique 243 to switches or switched environments. 245 In order to overcome the limitations of the existing standards, new 246 monitoring mechanisms have been implemented by vendors of switching 247 equipment. All these monitoring strategies are currently proprietary 248 in nature. 250 This document attempts to provide the framework to include different 251 switching strategies and allow for monitoring operations consistent 252 with the RMON framework. This MIB is limited to monitoring, and con- 253 trol operations aimed in providing monitoring data for RMON 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 col- 292 lection 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 enti- 295 ties, which have the capability of being monitored by an SMON probe. 297 2.3.2 Copy Port 299 In order to make the switching devices support RMON statistics, many 300 vendors have implemented a port copy feature, allowing traffic to be 301 replicated from switch port to switch port. Several levels of confi- 302 guration are possible: 304 1) 1 src port to 1 dst port 305 2) N src ports to 1 dst port 306 3) M src ports to N dst ports 308 The SMON standard presents a standard MIB interface which allows for 309 the control of this function. 311 Note that this function can apply to devices that have no other SMON 312 or RMON functionality than copy port. The agent of such a device 313 would support only the portCopyCaps and the portCopyConfig MIB 314 groups, out of the whole SMON MIB. Switch vendors are encouraged to 315 implement this subset of the SMON MIB, as it would allow for standard 316 port copy configuration from the same NMS application that does RMON 317 or SMON. 319 Port copy may cause congestion problems on the SMON device. This 320 situation is more likely occur when copying from a port of higher 321 speed to a port of lower speed or copy from multiple port to a single 322 port. 324 Particular implementations may chose to build protection mechanisms 325 that would prevent creation of new port copy links, when the capacity 326 of the destination port is exceeded. The MIB allows for implementa- 327 tions to (if supported) instrument a destination drop count on port 328 copy to provide NMS applications a sense of the quality of data 329 presented at the destination port. 331 2.3.3 Vlan Monitoring 333 Vlan monitoring can be accomplished by using a VLAN-based dataSource 334 and/or by configuring smonVlanIdStats and/or smonVlanPrioStats col- 335 lections. These functions allow VLAN-ID or user priority distribu- 336 tions per dataSource. Vlan monitoring provides a high-level view of 337 total Vlan usages and relative non-unicast traffic usage as well as a 338 profile of Vlan priority as defined in the 3-bit user_priority field. 340 NOTE: priority stats reflect what was parsed from the packet, not 341 what priority, if any, was necessarily granted by the switch. 343 2.4 Relationship to Other MIBs 345 2.4.1 The RMON and RMON2 MIBs 347 The Remote Monitoring MIB (RMON-1) [12] provides several management 348 functions that may be directly or indirectly applicable to switched 349 networks. 351 The port copy mechanisms defined by the RMON MIB allow for the desti- 352 nation ports to become data source for any RMON-1 statistics. How- 353 ever, an NMS application should check whether it is in the device 354 capability(portCopyCap) to filter errors from a source to a destina- 355 tion port and whether this capability is enabled, in order to provide 356 a correct interpretation of the copied port traffic. 358 RMON I host and matrix group statistics entries may be aggregated by 359 use of the extended dataSource capability defined in SMON. RMON II 360 groups are similarly extended through the use of SMON's dataSource 361 definition. 363 RMON-1 also defines a simple thresholding monitoring mechanism, 364 event-logging and event-notification for any MIB instance; SMON util- 365 izes the alarms and events groups from RMON-1 without modification. 366 These groups should be implemented on SMON devices if a simple thres- 367 holding mechanism is desired. 369 The RMON II usrHistory group (user-defined history collection) should 370 be implemented by an SMON device if a history collection mechanism is 371 desired for smonStats entries. 373 2.4.2 The Interfaces Group MIB 375 The Interfaces Group MIB [5], [17] extends aspects of MIB-II [3]. 376 This document discusses the 'interfaces' group of MIB-II, especially 377 the experience gained from the definition of numerous media- specific 378 MIB modules for use in conjunction with the 'interfaces' group for 379 managing various sub-layers beneath the internetwork- layer. It 380 specifies clarifications to, and extensions of, the architectural 381 issues within the previous model used for the 'interfaces' group. 383 The Interfaces Group MIB also includes a MIB module. As well as 384 including new MIB definitions to support the architectural exten- 385 sions, this MIB module also re-specifies the 'interfaces' group of 386 MIB-II in a manner that is both compliant to the SNMPv2 SMI and 387 semantically- identical to the existing SNMPv1-based definitions. 389 The SMON MIB utilizes the propVirtual(53) ifType defined in The 390 Interfaces Group MIB [17] to provide SMON and RMON with new 391 dataSources such as Vlans and internal monitoring points. NMS appli- 392 cations should consult the SMON dataSource capabilities group 393 (dataSourceCap) for a description of these virtual interfaces. 395 2.4.3 The Entity MIB 397 The scope of the Entity MIB [13] is to allow an NMS to interrogate a 398 standard SNMP context and thereby discover what logical and physical 399 entities exist, how to access the MIB information of each logical 400 entity, and the relationships between the various entities. The MIB 401 should support both a single agent or multiple agents in one physical 402 entity. 404 A "physical entity" or "physical component" represents an identifi- 405 able physical resource within a managed system. Zero or more logical 406 entities may utilize a physical resource at any given time. It is an 407 implementation-specific manner as to which physical components are 408 represented by an agent in the EntPhysicalTable. Typically, physical 409 resources (e.g. communications ports, backplanes, sensors, daughter- 410 cards, power supplies, the overall chassis, the overall switch), 411 which can be managed via functions associated with one or more logi- 412 cal entities are included in the MIB. 414 The SMON MIB does not mandate Entity MIB support, but allows for phy- 415 sical entities, as defined by this MIB to be defined as SMON data 416 sources. For such cases, the support for the EntPhysicalTable is 417 required. 419 2.4.4 The Bridge MIB 421 One of the important indicators for measuring the effectiveness of a 422 switching device is the ratio between the number of forwarded frames 423 and the number of dropped frames at the switch port. 425 It is out of the scope of this MIB to provide instrumentation infor- 426 mation relative to switching devices. However, such indication may be 427 part of other MIB modules. 429 For instance the Bridge MIB [18] provides such MIB objects, for the 430 802.1 bridges (dot1dTpPortInFrames, dot1dTpPortInDiscards) and 431 switches managed according to the 802.1 bridge model may provide this 432 information. 434 2.5 Relationship with IEEE 802.1 Standards 436 The SMON MIB provides simple statistics per vLAN and priority levels. 437 Those two categories of statistics are of higher importance for 438 switched networks managers. Interoperability for those features is 439 ensured by the use of the IEEE 802.1 p/Q standards ([14], [15]) 440 defined by the IEEE 802.1 WG. Interoperability from the SMON MIB 441 point of view is ensured by referencing the IEEE definition of vLANs 442 and priority levels, for the SMON statistics. 444 3. SMON/RMON Groups 446 3.1 ProbeCapabilities Additions 448 The RMON probeCapabilities bitmask needs to be republished with some 449 new BIT definitions for the SMON MIB: 451 - smonVlanStats(33) 452 The probe supports the smonVlanStats object group. 454 - smonPrioStats(34) 455 The probe supports the smonPrioStats object group. 457 - dataSource(35) 458 The probe supports the dataSource object group. 460 - portCopy(36) 461 The probe supports the portCopy object group. 463 NOTE: bits 27-32 are reserved for HC-RMON MIB groups. 465 3.2 smonVlanStats 467 The smonVlanStats MIB group includes the control and statistics 468 objects related to 802.1q Vlans. Specific statistics per 802.1q vir- 469 tual LAN are supported. The group provides a high level view of total 470 Vlan usage, and relative non-unicast traffic usage. 472 It is an implementation-specific matter as to how the agent deter- 473 mines the proper default-VLAN for untagged or priority-tagged frames. 475 3.3 smonPrioStats 477 The smonPrioStatsTable provides a distribution based on the 478 user_priority field in the VLAN header. 480 Note that this table merely reports priority as encoded in VLAN 481 headers, not the priority (if any) given the frame for actual switch- 482 ing purposes. 484 3.4 dataSourceCaps 486 The dataSourceCaps MIB group identifies all supported data sources on 487 an SMON device. An NMS may use this table to discover the RMON and 488 Copy Port attributes of each data source. 490 Upon restart of the agent, the dataSourceTable, ifTable and entPhysi- 491 calTable are initialized for the available data sources. The agent 492 may modify these tables as data sources become known or are 493 removed(e.g. hot swap of interfaces, chassis cards or the discovery 494 of Vlan usage). It is understood that dataSources representing VLANs 495 may not always be instantiated immediately upon restart, but rather 496 as VLAN usage is detected by the agent. The agent should attempt to 497 create dataSource and interface entries for all dataSources as soon 498 as possible. 500 For each dataSourceCapsEntry representing a VLAN or entPhysicalEntry, 501 the agent must create an associated ifEntry with a ifType value of 502 'propVirtual(53)'. This ifEntry will be used as the actual value in 503 RMON control table dataSource objects. The assigned ifIndex value is 504 copied into the associated dataSourceCapsIfIndex object. 506 3.5 portCopyConfig 508 The portCopyConfig MIB group includes the objects defined for the 509 control of the port copy functionality in a device. 511 The standard does not place a limit on the mode by which this copy 512 function may be used: 514 Mode 1 -- 1:1 Copy 516 Single dataSource copied to a single destination dataSource. 517 Agent may limit configuration based on ifTypes, ifSpeeds, half- 518 duplex/full-duplex, or agent resources. In this mode the single 519 instance of the portCopyDstDroppedFrames object refers to dropped 520 frames on the portCopyDest interface. 522 Mode 2 -- N:1 Copy 524 Multiple dataSources copied to a single destination dataSource. 525 Agent may limit configuration based on ifTypes, ifSpeeds, half- 526 duplex/full-duplex, portCopyDest over-subscription, or agent 527 resources. In this mode all N instances of the portCopyDstDrop- 528 pedFrames object should contain the same value, and refer to 529 dropped frames on the portCopyDest interface. 531 Mode 3 -- N:M Copy 533 Multiple dataSources copied to multiple destination dataSources. 534 Agent may limit configuration based on ifTypes, ifSpeeds, half- 535 duplex/full-duplex, portCopyDest over-subscription, or agent 536 resources. In this mode all N instances of the portCopyDstDrop- 537 pedFrames object should the droppedFrames counter associated with 538 the portCopyDest INDEX value for the specific entry, and refer to 539 the total dropped frames on that portCopyDest interface (i.e., a 540 single droppedFrames counter is maintained for each value of M). 542 The rows do not have an OwnerString, since multiple rows may be part 543 of the same portCopy operation. The agent is expected to activate or 544 deactivate entries one at a time, based on the rowStatus for the 545 given row. This can lead to unpredictable results in Modes 2 and 3 546 in applications utilizing the portCopy target traffic, if multiple 547 PDUs are used to fully configure the operation. It is recommended 548 that an entire portCopy operation be configured in one SetRequest PDU 549 if possible. 551 The portCopyDest object may not reference an interface associated 552 with a packet-based VLAN (rmonVlanDataSource.V), but this dataSource 553 type may be used as a portCopySource. 555 4. Control of Remote Network Monitoring Devices 557 Due to the complex nature of the available functions in these dev- 558 ices, the functions often need user configuration. In many cases, 559 the function requires parameters to be set up for a data collection 560 operation. The operation can proceed only after these parameters are 561 fully set up. 563 Many functional groups in this MIB have one or more tables in which 564 to set up control parameters, and one or more data tables in which to 565 place the results of the operation. The control tables are typically 566 read/write in nature, while the data tables are typically read/only. 567 Because the parameters in the control table often describe resulting 568 data in the data table, many of the parameters can be modified only 569 when the control entry is not active. Thus, the method for modifying 570 these parameters is to de-activate the entry, perform the SNMP Set 571 operations to modify the entry, and then re-activate the entry. 572 Deleting the control entry causes the deletion of any associated data 573 entries, which also gives a convenient method for reclaiming the 574 resources used by the associated data. 576 Some objects in this MIB provide a mechanism to execute an action on 577 the remote monitoring device. These objects may execute an action as 578 a result of a change in the state of the object. For those objects 579 in this MIB, a request to set an object to the same value as it 580 currently holds would thus cause no action to occur. 582 To facilitate control by multiple managers, resources have to be 583 shared among the managers. These resources are typically the memory 584 and computation resources that a function requires. 586 The control mechanisms defined and used in this MIB are the same as 587 those defined in the RMON MIB [11], for control functionality and 588 interaction with multiple managers. 590 5. Definitions 592 SMON-MIB DEFINITIONS ::= BEGIN 594 IMPORTS 595 MODULE-IDENTITY, OBJECT-TYPE, Counter32, 596 Integer32, Counter64, experimental 597 FROM SNMPv2-SMI 598 mib-2, ifType 599 FROM RFC1213-MIB 600 RowStatus, TEXTUAL-CONVENTION, RowPointer 601 FROM SNMPv2-TC 602 OwnerString 603 FROM RMON-MIB 604 LastCreateTime, DataSource, rmonConformance 605 FROM RMON2-MIB 606 InterfaceIndex 607 FROM IF-MIB 608 MODULE-COMPLIANCE, OBJECT-GROUP 609 FROM SNMPv2-CONF; 611 switchRMON MODULE-IDENTITY 612 LAST-UPDATED "9707030000Z" 613 ORGANIZATION "IETF RMON MIB Working Group" 614 CONTACT-INFO 615 "IETF RMONMIB WG Mailing list: rmonmib@cisco.com 617 Rich Waterman 618 Allot Networks Inc. 619 Phone: +1 408 559 0253 620 Email: rwaterma@msn.com 622 Bill Lahaye 623 Cabletron Systems 624 Phone: +1 603 337 5211 625 Email: lahaye@ctron.com 627 Dan Romascanu 628 Madge Networks 629 Phone: +972 3 645 8414 630 Email: dromasca@madge.com 632 Steven Waldbusser 633 International Network Services 634 Phone: (415) 254-4251 635 EMail: waldbusser@ins.com" 637 DESCRIPTION 638 "The MIB module for managing remote monitoring device 639 implementations for Switched Networks" 640 ::= { experimental 1000 } 642 smonMIBObjects OBJECT IDENTIFIER ::= { switchRMON 1 } 644 dataSourceCaps OBJECT IDENTIFIER ::= {smonMIBObjects 1} 645 smonStats OBJECT IDENTIFIER ::= {smonMIBObjects 2} 646 portCopyConfig OBJECT IDENTIFIER ::= {smonMIBObjects 3} 647 smonRegistrationPoints OBJECT IDENTIFIER ::= {smonMIBObjects 4} 649 -- Textual Conventions 650 -- 651 SmonDataSource ::= TEXTUAL-CONVENTION 652 STATUS current 653 DESCRIPTION 654 "Identifies the source of the data that the associated function 655 is configured to analyse. This macro extends the DataSource 656 Textual Convention defined by RMON-2 [11] to the following data 657 source types: 659 - ifIndex. 660 DataSources of this traditional form are called 'port-based', 661 but only if ifType. is not equal to 'propVirtual(53)'. 663 - smonVlanDataSource. 664 A dataSource of this form refers to a 'Packet-based VLAN' and 665 is called a 'VLAN-based' dataSource. is the VLAN ID, as defined 666 by the IEEE 802.1Q standard [14]. 668 - entPhysicalEntry. 669 A dataSource of this form refers to a physical entity within 670 the agent (e.g. entPhysicalClass = backplane(4)) and is called 671 an 'entity-based' dataSource." 672 SYNTAX OBJECT IDENTIFIER 674 -- dataSourceCaps MIB group - defines SMON data source and port copy 675 -- capabilities for devices supporting SMON. 677 -- A NMS application will check this MIB group and retrieve information about 678 -- the SMON capabilities of the device before applying SMON control operations 679 -- to the device. 681 -- dataSourceCapsTable: defines capabilities of RMON data sources 683 dataSourceCapsTable OBJECT-TYPE 684 SYNTAX SEQUENCE OF DataSourceCapsEntry 685 MAX-ACCESS not-accessible 686 STATUS current 687 DESCRIPTION 688 "This table describes RMON data sources and port copy capabilities. 689 An NMS may use this table to discover the identity and attributes of 690 the data sources on a given agent implementation. Similar to the 691 probeCapabilities object, actual row-creation operations will succeed 692 or fail based on the resources available ans parameter values used 693 in each row-creation operation. 695 Upon restart of the RMON agent, the dataSourceTable, ifTable, and 696 perhaps entPhysicalTable are initialized for the available dataSources. 698 For each dataSourceCapsEntry representing a VLAN or entPhysicalEntry 699 the agent must create an associated ifEntry with a ifType value of 700 'propVirtual(53)'. This ifEntry will be used as the actual value 701 in RMON control table dataSource objects. The assigned ifIndex value 702 is copied into the associated dataSourceCapsIfIndex object. 704 It is understood that dataSources representing VLANs may not always 705 be instantiated immediately upon restart, but rather as VLAN usage 706 is detected by the agent. The agent should attempt to create 707 dataSource and interface entries for all dataSources as soon as 708 possible." 709 ::= { dataSourceCaps 1 } 711 dataSourceCapsEntry OBJECT-TYPE 712 SYNTAX DataSourceCapsEntry 713 MAX-ACCESS not-accessible 714 STATUS current 715 DESCRIPTION 716 "Entries per data source containing descriptions of data source and 717 port copy capabilities. This table is populated by the RMON agent 718 with one entry for each supported data source." 719 INDEX { IMPLIED dataSourceCapsObject } 720 ::= { dataSourceCapsTable 1 } 722 DataSourceCapsEntry ::= SEQUENCE { 723 dataSourceCapsObject 724 SmonDataSource, 725 dataSourceRmonCaps 726 BITS, 727 dataSourceCopyCaps 728 BITS, 729 dataSourceCapsIfIndex 730 InterfaceIndex 731 } 733 dataSourceCapsObject OBJECT-TYPE 734 SYNTAX SmonDataSource 735 MAX-ACCESS not-accessible 736 STATUS current 737 DESCRIPTION 738 "Defines an object that can be a SMON data source or a 739 source or a destination for a port copy operation." 740 ::= { dataSourceCapsEntry 1 } 742 dataSourceRmonCaps OBJECT-TYPE 743 SYNTAX BITS { 744 countErrFrames(0), 745 countAllGoodFrames(1), 746 countAnyRmonTables(2) 747 } 748 MAX-ACCESS read-only 749 STATUS current 750 DESCRIPTION 751 " General attributes of the specified dataSource. 752 Note that these are static attributes, which should not 753 be adjusted because of current resources or configuration. 755 - countErrFrames(0) 756 The agent sets this bit for the dataSource if errored frames 757 received on this dataSource can actually be monitored by the agent. 758 The agent clears this bit is any errored frames are not visible to 759 the RMON data collector. 761 - countAllGoodFrames(1) 762 The agent sets this bit for the dataSource if all good frames received 763 on this dataSource can actually be monitored by the agent. 764 The agent clears this bit if any good frames are not visible for RMON 765 collection, e.g., the dataSource is a non-promiscuous interface or an 766 internal switch interface which may not receives frames which were 767 switched in hardware or dropped by the bridge forwarding function. 769 - countAnyRmonTables(2) 770 The agent sets this bit if this dataSource can actually be used in 771 any of the implemented RMON tables, resources notwithstanding. 772 The agent clears this bit if this dataSourceCapsEntry is present 773 simply to identify a dataSource that may only be used as 774 portCopySource and/or a portCopyDest, but not the source of an 775 actual RMON data collection." 776 ::= { dataSourceCapsEntry 2 } 778 dataSourceCopyCaps OBJECT-TYPE 779 SYNTAX BITS { 780 copySourcePort(0), 781 copyDestPort(1), 782 copySrcTxTraffic(2), 783 copySrcRxTraffic(3), 784 countDstDropEvents(4), 785 copyErrFrames(5), 786 copyUnalteredFrames(6), 787 copyAllGoodFrames(7) 788 } 789 MAX-ACCESS read-only 790 STATUS current 791 DESCRIPTION 792 " PortCopy function capabilities of the specified dataSource. 793 Note that these are static capabilities, which should not be adjusted 794 because of current resources or configuration. 796 - copySourcePort(0) 797 The agent sets this bit if this dataSource is capable of acting 798 as a source of a portCopy operation. The agent clears this bit 799 otherwise. 801 - copyDestPort(1) 802 The agent sets this bit if this dataSource is capable of acting as 803 a destination of a portCopy operation. The agent clears this bit 804 otherwise. 806 - copySrcTxTraffic(2) 807 If the copySourcePort bit is set: 808 The agent sets this bit if this dataSource is capable of 809 copying frames transmitted out this portCopy source. 810 The agent clears this bit otherwise. This function is 811 needed to support full-duplex ports. 812 Else this bit should be cleared. 814 - copySrcRxTraffic(3) 815 If the copySourcePort bit is set: 816 The agent sets this bit if this dataSource is capable of 817 copying frames received on this portCopy source. 818 The agent clears this bit otherwise. This function is 819 needed to support full-duplex ports. 820 Else this bit should be cleared. 822 - countDstDropEvents(4) 823 If the copyDestPort bit is set: 824 The agent sets this bit if it is capable of incrementing the 825 portCopyDstDroppedFrames, when thisdataSource is the target 826 of a portCopy operation and a frame destined to this dataSource is 827 dropped (for RMONcounting purposes). 828 Else this BIT should be cleared. 830 - copyErrFrames(5) 831 If the copySourcePort bit is set: 832 The agent sets this bit if it is capable of copying all errored 833 frames from this portCopy source-port, for errored frames 834 received on this dataSource. 835 Else this BIT should be cleared. 837 - copyUnalteredFrames(6) 838 If the copySourcePort bit is set: 839 The agent sets this bit if it is capable of copying all frames 840 from this portCopy source-port without alteration in any way; 841 including, but not limited to: 842 - truncation (with or without CRC regeneration) 843 - proprietary header insertion 844 - MAC header rewrite 845 - VLAN retagging 847 Else this bit should be cleared. 849 - copyAllGoodFrames(7) 850 If the copySourcePort bit is set: 851 The agent sets this bit for the dataSource if all good frames 852 received on this dataSource are normally capable of being copied 853 by the agent. The agent clears this bit if any good frames are 854 not visible for the RMON portCopy operation, e.g., the dataSource 855 is a non-promiscuous interface or an internal switch interface 856 which may not receive frames which were switched in hardware or 857 dropped by the bridge forwarding function. 858 Else this bit should be cleared." 859 ::= { dataSourceCapsEntry 3 } 861 dataSourceCapsIfIndex OBJECT-TYPE 862 SYNTAX InterfaceIndex 863 MAX-ACCESS read-only 864 STATUS current 865 DESCRIPTION 866 "This object contains the ifIndex value of the ifEntry associated 867 with this smonDataSource." 868 ::= { dataSourceCapsEntry 4 } 870 -- The SMON Statistics MIB Group 872 -- aggregated statistics for IEEE 802.1Q VLAN environments. 874 -- VLAN statistics can be gathered in two different ways; either by using a 875 -- dataSource referencing a VLAN (sec. 3.3.6) or by configuring 876 -- smonVlanIdStats and/or smonVlanPrioStats collections. These functions 877 -- allow a VLAN-ID or user priority distributions per dataSource, 878 -- auto-populated by the agent in a manner similar to the RMON1 hostTable. 880 -- Only good frames are counted in the tables described in this section. 882 -- VLAN ID Stats 884 -- smonVlanStatsControlTable allows configuration of VLAN-ID collections. 886 smonVlanStatsControlTable OBJECT-TYPE 887 SYNTAX SEQUENCE OF SmonVlanStatsControlEntry 888 MAX-ACCESS not-accessible 889 STATUS current 890 DESCRIPTION 891 "Controls the setup of vLAN statistics tables." 892 ::= { smonStats 1 } 894 smonVlanStatsControlEntry OBJECT-TYPE 895 SYNTAX SmonVlanStatsControlEntry 896 MAX-ACCESS not-accessible 897 STATUS current 898 DESCRIPTION 899 "A conceptual row in the smonVlanStatsControlTable. 900 An example of the indexing of this entry is 901 smonVlanStatsControlCreateTime.7" 902 INDEX { smonVlanStatsControlIndex } 903 ::= { smonVlanStatsControlTable 1 } 905 SmonVlanStatsControlEntry ::= SEQUENCE { 906 smonVlanStatsControlIndex Integer32, 907 smonVlanStatsControlDataSource SmonDataSource, 908 smonVlanStatsControlCreateTime LastCreateTime, 909 smonVlanStatsControlOwner OwnerString, 910 smonVlanStatsControlStatus RowStatus 911 } 913 smonVlanStatsControlIndex OBJECT-TYPE 914 SYNTAX Integer32 (1..65535) 915 MAX-ACCESS not-accessible 916 STATUS current 917 DESCRIPTION 918 "A unique arbitrary index for this smonVlanStatsControlEntry." 919 ::= { smonVlanStatsControlEntry 1 } 921 smonVlanStatsControlDataSource OBJECT-TYPE 922 SYNTAX SmonDataSource 923 MAX-ACCESS read-create 924 STATUS current 925 DESCRIPTION 926 "The source of data for this set of vLAN statistics. 928 This object may not be modified if the associated 929 smonVlanStatsControlStatus object is equal to active(1)." 930 ::= { smonVlanStatsControlEntry 2 } 932 smonVlanStatsControlCreateTime OBJECT-TYPE 933 SYNTAX LastCreateTime 934 MAX-ACCESS read-only 935 STATUS current 936 DESCRIPTION 937 "The value of sysUpTime when this control entry was last 938 activated. This can be used by the management station to 939 ensure that the table has not been deleted and recreated 940 between polls." 941 ::= { smonVlanStatsControlEntry 3 } 943 smonVlanStatsControlOwner OBJECT-TYPE 944 SYNTAX OwnerString 945 MAX-ACCESS read-create 946 STATUS current 947 DESCRIPTION 948 "The entity that configured this entry and is 949 therefore using the resources assigned to it." 950 ::= { smonVlanStatsControlEntry 4 } 952 smonVlanStatsControlStatus OBJECT-TYPE 953 SYNTAX RowStatus 954 MAX-ACCESS read-create 955 STATUS current 956 DESCRIPTION 957 "The status of this row. 959 An entry may not exist in the active state unless all 960 objects in the entry have an appropriate value. 962 If this object is not equal to active(1), all associated 963 entries in the smonVlanStatsStatsTable shall be deleted." 964 ::= { smonVlanStatsControlEntry 5 } 966 -- The VLAN Statistics Table 967 -- The smonVlanIdStatsTable provides a distribution based on the IEEE 802.1Q 968 -- VLAN-ID (VID), for each frame attributed to the data source for the 969 -- collection. 971 -- This function applies the same rules for attributing frames to VLAN-based 972 -- collections. RMON VLAN statistics are collected after the Ingress Rules 973 -- defined in section 3.13 of the VLAN Specification (P802.1Q/D4) 974 -- are applied. 976 -- It is possible that entries in this table will be garbage-collected, based 977 -- on agent resources, and VLAN configuration. Agents are encouraged to 978 -- support all 4096 index values and not garbage collect this table. 980 smonVlanIdStatsTable OBJECT-TYPE 981 SYNTAX SEQUENCE OF SmonVlanIdStatsEntry 982 MAX-ACCESS not-accessible 983 STATUS current 984 DESCRIPTION 985 "Contains the vLAN statistics data." 986 ::= { smonStats 2 } 988 smonVlanIdStatsEntry OBJECT-TYPE 989 SYNTAX SmonVlanIdStatsEntry 990 MAX-ACCESS not-accessible 991 STATUS current 992 DESCRIPTION 993 "A conceptual row in smonVlanIdStatsTable." 994 INDEX { smonVlanStatsControlIndex, smonVlanIdStatsId } 995 ::= { smonVlanIdStatsTable 1 } 997 SmonVlanIdStatsEntry ::= SEQUENCE { 998 smonVlanIdStatsId Integer32, 999 smonVlanIdStatsTotalPkts Counter32, 1000 smonVlanIdStatsTotalOverflowPkts Counter32, 1001 smonVlanIdStatsTotalHCPkts Counter64, 1002 smonVlanIdStatsTotalOctets Counter32, 1003 smonVlanIdStatsTotalOverflowOctets Counter32, 1004 smonVlanIdStatsTotalHCOctets Counter64, 1005 smonVlanIdStatsNUcastPkts Counter32, 1006 smonVlanIdStatsNUcastOverflowPkts Counter32, 1007 smonVlanIdStatsNUcastHCPkts Counter64, 1008 smonVlanIdStatsNUcastOctets Counter32, 1009 smonVlanIdStatsNUcastOverflowOctets Counter32, 1010 smonVlanIdStatsNUcastHCOctets Counter64, 1011 smonVlanIdStatsCreateTime LastCreateTime 1012 } 1014 smonVlanIdStatsId OBJECT-TYPE 1015 SYNTAX Integer32 (0..4095) 1016 MAX-ACCESS not-accessible 1017 STATUS current 1018 DESCRIPTION 1019 "The unique identifier of the vLAN monitored for 1020 this specific statistics collection. 1022 According to [14] tagged packets match the VID for the range between 1023 1 and 4095. An external RMON probe may detect VID=0 on a Inter Switch 1024 Link, in which case the packet belongs to a vLAN determined by the 1025 PVID of the ingress port. The vLAN belonging of such a packet can be 1026 determined only by a RMON probe internal to the switch." 1027 REFERENCE 1028 "Draft Standard for Virtual Bridged Local Area Networks, P802.1Q/D6, 1029 chapter 3.13" 1030 ::= { smonVlanIdStatsEntry 1 } 1032 smonVlanIdStatsTotalPkts OBJECT-TYPE 1033 SYNTAX Counter32 1034 MAX-ACCESS read-only 1035 STATUS current 1036 DESCRIPTION 1037 "The total number of packets counted on 1038 this vLAN." 1040 ::= { smonVlanIdStatsEntry 2 } 1042 smonVlanIdStatsTotalOverflowPkts OBJECT-TYPE 1043 SYNTAX Counter32 1044 MAX-ACCESS read-only 1045 STATUS current 1046 DESCRIPTION 1047 "The number of times the associated smonVlanIdStatsTotalPkts 1048 counter has overflowed." 1049 ::= { smonVlanIdStatsEntry 3 } 1051 smonVlanIdStatsTotalHCPkts OBJECT-TYPE 1052 SYNTAX Counter64 1053 MAX-ACCESS read-only 1054 STATUS current 1055 DESCRIPTION 1056 " The total number of packets counted on 1057 this vLAN." 1058 ::= { smonVlanIdStatsEntry 4 } 1060 smonVlanIdStatsTotalOctets OBJECT-TYPE 1061 SYNTAX Counter32 1062 MAX-ACCESS read-only 1063 STATUS current 1064 DESCRIPTION 1065 "The total number of octets counted on 1066 this vLAN." 1067 ::= { smonVlanIdStatsEntry 5 } 1069 smonVlanIdStatsTotalOverflowOctets OBJECT-TYPE 1070 SYNTAX Counter32 1071 MAX-ACCESS read-only 1072 STATUS current 1073 DESCRIPTION 1074 "The number of times the associated smonVlanIdStatsTotalOctets 1075 counter has overflowed." 1076 ::= { smonVlanIdStatsEntry 6 } 1078 smonVlanIdStatsTotalHCOctets OBJECT-TYPE 1079 SYNTAX Counter64 1080 MAX-ACCESS read-only 1081 STATUS current 1082 DESCRIPTION 1083 " The total number of octets counted on 1084 this vLAN." 1085 ::= { smonVlanIdStatsEntry 7 } 1087 smonVlanIdStatsNUcastPkts OBJECT-TYPE 1088 SYNTAX Counter32 1089 MAX-ACCESS read-only 1090 STATUS current 1091 DESCRIPTION 1092 "The total number of non-unicast packets counted on 1093 this vLAN." 1094 ::= { smonVlanIdStatsEntry 8 } 1096 smonVlanIdStatsNUcastOverflowPkts OBJECT-TYPE 1097 SYNTAX Counter32 1098 MAX-ACCESS read-only 1099 STATUS current 1100 DESCRIPTION 1101 "The number of times the associated smonVlanIdStatsNUcastPkts 1102 counter has overflowed." 1103 ::= { smonVlanIdStatsEntry 9 } 1105 smonVlanIdStatsNUcastHCPkts OBJECT-TYPE 1106 SYNTAX Counter64 1107 MAX-ACCESS read-only 1108 STATUS current 1109 DESCRIPTION 1110 " The total number of non-unicast packets counted on 1111 this vLAN." 1112 ::= { smonVlanIdStatsEntry 10 } 1114 smonVlanIdStatsNUcastOctets OBJECT-TYPE 1115 SYNTAX Counter32 1116 MAX-ACCESS read-only 1117 STATUS current 1118 DESCRIPTION 1119 "The total number of non-unicast octets counted on 1120 this vLAN." 1121 ::= { smonVlanIdStatsEntry 11 } 1123 smonVlanIdStatsNUcastOverflowOctets OBJECT-TYPE 1124 SYNTAX Counter32 1125 MAX-ACCESS read-only 1126 STATUS current 1127 DESCRIPTION 1128 "The number of times the associated smonVlanIdStatsNUcastOctets 1129 counter has overflowed." 1130 ::= { smonVlanIdStatsEntry 12 } 1132 smonVlanIdStatsNUcastHCOctets OBJECT-TYPE 1133 SYNTAX Counter64 1134 MAX-ACCESS read-only 1135 STATUS current 1136 DESCRIPTION 1137 " The total number of Non-unicast octets counted on 1138 this vLAN." 1139 ::= { smonVlanIdStatsEntry 13 } 1141 smonVlanIdStatsCreateTime OBJECT-TYPE 1142 SYNTAX LastCreateTime 1143 MAX-ACCESS read-only 1144 STATUS current 1145 DESCRIPTION 1146 "The value of sysUpTime when this entry was last activated. 1147 This can be used by the management station to ensure that the 1148 entry has not been deleted and recreated between polls." 1149 ::= { smonVlanIdStatsEntry 14 } 1151 -- smonPrioStatsControlTable allows configuration of collections based on the 1152 -- value of the 3-bit user priority field encoded in the TCI. Note that this 1153 -- table merely reports priority as encoded in the VLAN headers, not the 1154 -- priority (if any) given to the frame for the actual switching purposes. 1156 smonPrioStatsControlTable OBJECT-TYPE 1157 SYNTAX SEQUENCE OF SmonPrioStatsControlEntry 1158 MAX-ACCESS not-accessible 1159 STATUS current 1160 DESCRIPTION 1161 "Controls the setup of priority statistics tables." 1162 ::= { smonStats 3 } 1164 smonPrioStatsControlEntry OBJECT-TYPE 1165 SYNTAX SmonPrioStatsControlEntry 1166 MAX-ACCESS not-accessible 1167 STATUS current 1168 DESCRIPTION 1169 "A conceptual row in the smonPrioStatsControlTable. 1171 An example of the indexing of this entry is 1172 smonPrioStatsControlCreateTime.7" 1173 INDEX { smonPrioStatsControlIndex } 1174 ::= { smonPrioStatsControlTable 1 } 1176 SmonPrioStatsControlEntry ::= SEQUENCE { 1177 smonPrioStatsControlIndex Integer32, 1178 smonPrioStatsControlDataSource SmonDataSource, 1179 smonPrioStatsControlCreateTime LastCreateTime, 1180 smonPrioStatsControlOwner OwnerString, 1181 smonPrioStatsControlStatus RowStatus 1182 } 1183 smonPrioStatsControlIndex OBJECT-TYPE 1184 SYNTAX Integer32 (1..65535) 1185 MAX-ACCESS not-accessible 1186 STATUS current 1187 DESCRIPTION 1188 "A unique arbitrary index for this smonPrioStatsControlEntry." 1189 ::= { smonPrioStatsControlEntry 1 } 1191 smonPrioStatsControlDataSource OBJECT-TYPE 1192 SYNTAX SmonDataSource 1193 MAX-ACCESS read-create 1194 STATUS current 1195 DESCRIPTION 1196 "The source of data for this set of vLAN statistics. 1198 This object may not be modified if the associated 1199 smonPrioStatsControlStatus object is equal to active(1)." 1200 ::= { smonPrioStatsControlEntry 2 } 1202 smonPrioStatsControlCreateTime OBJECT-TYPE 1203 SYNTAX LastCreateTime 1204 MAX-ACCESS read-only 1205 STATUS current 1206 DESCRIPTION 1207 "The value of sysUpTime when this control entry was last 1208 activated. This can be used by the management station to 1209 ensure that the table has not been deleted and recreated 1210 between polls." 1211 ::= { smonPrioStatsControlEntry 3 } 1213 smonPrioStatsControlOwner OBJECT-TYPE 1214 SYNTAX OwnerString 1215 MAX-ACCESS read-create 1216 STATUS current 1217 DESCRIPTION 1218 "The entity that configured this entry and is 1219 therefore using the resources assigned to it." 1220 ::= { smonPrioStatsControlEntry 4 } 1222 smonPrioStatsControlStatus OBJECT-TYPE 1223 SYNTAX RowStatus 1224 MAX-ACCESS read-create 1225 STATUS current 1226 DESCRIPTION 1227 "The status of this row. 1229 An entry may not exist in the active state unless all 1230 objects in the entry have an appropriate value. 1232 If this object is not equal to active(1), all associated 1233 entries in the smonPrioStatsStatsTable shall be deleted." 1234 ::= { smonPrioStatsControlEntry 5 } 1236 -- The Priority Statistics Table 1238 smonPrioStatsTable OBJECT-TYPE 1239 SYNTAX SEQUENCE OF SmonPrioStatsEntry 1240 MAX-ACCESS not-accessible 1241 STATUS current 1242 DESCRIPTION 1243 "Contains the priority statistics." 1244 ::= { smonStats 4 } 1246 smonPrioStatsEntry OBJECT-TYPE 1247 SYNTAX SmonPrioStatsEntry 1248 MAX-ACCESS not-accessible 1249 STATUS current 1250 DESCRIPTION 1251 "A conceptual row in smonPrioStatsTable." 1252 INDEX { smonPrioStatsControlIndex, smonPrioStatsId } 1253 ::= { smonPrioStatsTable 1 } 1255 SmonPrioStatsEntry ::= SEQUENCE { 1256 smonPrioStatsId Integer32, 1257 smonPrioStatsPkts Counter32, 1258 smonPrioStatsOverflowPkts Counter32, 1259 smonPrioStatsHCPkts Counter64, 1260 smonPrioStatsOctets Counter32, 1261 smonPrioStatsOverflowOctets Counter32, 1262 smonPrioStatsHCOctets Counter64 1263 } 1265 smonPrioStatsId OBJECT-TYPE 1266 SYNTAX Integer32 (0..7) 1267 MAX-ACCESS not-accessible 1268 STATUS current 1269 DESCRIPTION 1270 "The unique identifier of the priority level monitored for 1271 this specific statistics collection." 1272 REFERENCE 1273 " Draft Standard for Virtual Bridged Local Area Networks, P802.1Q/D6, 1274 chapter 4.3.2.1" 1275 ::= { smonPrioStatsEntry 1 } 1277 smonPrioStatsPkts OBJECT-TYPE 1278 SYNTAX Counter32 1279 MAX-ACCESS read-only 1280 STATUS current 1281 DESCRIPTION 1282 "The total number of packets counted on 1283 this priority level." 1284 ::= { smonPrioStatsEntry 2 } 1286 smonPrioStatsOverflowPkts OBJECT-TYPE 1287 SYNTAX Counter32 1288 MAX-ACCESS read-only 1289 STATUS current 1290 DESCRIPTION 1291 "The number of times the associated smonPrioStatsPkts 1292 counter has overflowed." 1293 ::= { smonPrioStatsEntry 3 } 1295 smonPrioStatsHCPkts OBJECT-TYPE 1296 SYNTAX Counter64 1297 MAX-ACCESS read-only 1298 STATUS current 1299 DESCRIPTION 1300 " The total number of packets counted on 1301 this priority level." 1302 ::= { smonPrioStatsEntry 4 } 1304 smonPrioStatsOctets OBJECT-TYPE 1305 SYNTAX Counter32 1306 MAX-ACCESS read-only 1307 STATUS current 1308 DESCRIPTION 1309 "The total number of octets counted on 1310 this priority level." 1311 ::= { smonPrioStatsEntry 5 } 1313 smonPrioStatsOverflowOctets OBJECT-TYPE 1314 SYNTAX Counter32 1315 MAX-ACCESS read-only 1316 STATUS current 1317 DESCRIPTION 1318 "The number of times the associated smonPrioStatsOctets 1319 counter has overflowed." 1320 ::= { smonPrioStatsEntry 6 } 1322 smonPrioStatsHCOctets OBJECT-TYPE 1323 SYNTAX Counter64 1324 MAX-ACCESS read-only 1325 STATUS current 1326 DESCRIPTION 1327 " The total number of octets counted on 1328 this priority level." 1329 ::= { smonPrioStatsEntry 7 } 1331 -- Port Copy provides the ability to copy all frames from a 1332 -- a specified source to specified destination within a switch. 1333 -- Source and destinations should be MIB-II interfaces 1334 -- One to one, many to one and one to many source to destination 1335 -- relationships may be configured. 1336 -- 1337 -- Applicable counters on the destination will increment for 1338 -- all packets transmitted, be it by normal bridging/switching 1339 -- or due to packet copy. 1340 -- Note that this table manages no RMON data collection on itself, 1341 -- and an agent may possibly implement no other RMON objects except the 1342 -- probeCapabilities scalar, the dataSourceCapsTable, and this table. 1344 portCopyTable OBJECT-TYPE 1345 SYNTAX SEQUENCE OF PortCopyEntry 1346 MAX-ACCESS not-accessible 1347 STATUS current 1348 DESCRIPTION 1349 "This table provides the ability to configure the copy port 1350 functionality. Source and destinations should be MIB-II 1351 interfaces. 1352 One to one, many to one and one to many source to destination 1353 relationships may be configured. 1354 Each row that exists in this table defines such a 1355 relationship. By disabling a row in this table the port copy 1356 relationship no longer exists." 1357 ::= { portCopyConfig 1 } 1359 portCopyEntry OBJECT-TYPE 1360 SYNTAX PortCopyEntry 1361 MAX-ACCESS not-accessible 1362 STATUS current 1363 DESCRIPTION 1364 "Describes a particular port copy entry." 1365 INDEX { portCopySource, portCopyDest } 1366 ::= { portCopyTable 1 } 1368 PortCopyEntry ::= SEQUENCE { 1369 portCopySource 1370 InterfaceIndex, 1371 portCopyDest 1372 InterfaceIndex, 1373 portCopyDestDropEvents 1374 Counter32, 1376 portCopyStatus 1377 RowStatus 1378 } 1380 portCopySource OBJECT-TYPE 1381 SYNTAX InterfaceIndex 1382 MAX-ACCESS not-accessible 1383 STATUS current 1384 DESCRIPTION 1385 "The ifIndex of the source which will have all packets redirected to 1386 the destination as defined by portCopyDest." 1387 ::= { portCopyEntry 1 } 1389 portCopyDest OBJECT-TYPE 1390 SYNTAX InterfaceIndex 1391 MAX-ACCESS not-accessible 1392 STATUS current 1393 DESCRIPTION 1394 "Defines the ifIndex destination for the copy operation." 1395 ::= { portCopyEntry 2 } 1397 portCopyDropEvents OBJECT-TYPE 1398 SYNTAX Counter32 1399 MAX-ACCESS read-only 1400 STATUS current 1401 DESCRIPTION 1402 "The total number of events in which port copy packets 1403 were dropped by the switch due to lack of resources. 1404 Note that this number is not necessarily the number of 1405 packets dropped; it is just the number of times this 1406 condition has been detected." 1407 ::= { portCopyEntry 3 } 1409 portCopyStatus OBJECT-TYPE 1410 SYNTAX RowStatus 1411 MAX-ACCESS read-write 1412 STATUS current 1413 DESCRIPTION 1414 "Defines the status of the port copy entry." 1415 ::= { portCopyEntry 4 } 1417 -- smonRegistrationPoints 1418 -- defines a set of OIDs for registration purposes of entities 1419 -- supported by the SMON MIB. 1421 smonVlanDataSource OBJECT IDENTIFIER ::= { smonRegistrationPoints 1} 1422 -- Defined for uses as an SmonDataSource. A single integer parameter 1423 -- is appended to the end of this OID when actually encountered in 1424 -- the dataSourceCapsTable, which represents a positive, non-zero VLAN 1425 -- identifier value. 1427 -- Conformance Macros 1429 smonMIBCompliances OBJECT IDENTIFIER ::= { rmonConformance 3} 1430 smonMIBGroups OBJECT IDENTIFIER ::= { rmonConformance 4} 1432 smonMIBCompliance MODULE-COMPLIANCE 1433 STATUS current 1434 DESCRIPTION 1435 "Describes the requirements for full conformance with the SMON MIB" 1436 MODULE -- this module 1437 MANDATORY-GROUPS {dataSourceCapsGroup, 1438 smonVlanStatsGroup, 1439 smonPrioStatsGroup, 1440 portCopyConfigGroup} 1441 ::= { smonMIBCompliances 1 } 1443 smonMIBVlanStatsCompliance MODULE-COMPLIANCE 1444 STATUS current 1445 DESCRIPTION 1446 "Describes the requirements for conformance with the SMON MIB 1447 with support for VLAN Statistics. Mandatory for a SMON probe in 1448 environment where IEEE 802.1Q bridging is implemented." 1449 MODULE -- this module 1450 MANDATORY-GROUPS {dataSourceCapsGroup, 1451 smonVlanStatsGroup} 1452 ::= { smonMIBCompliances 2 } 1454 smonMIBPrioStatsCompliance MODULE-COMPLIANCE 1455 STATUS current 1456 DESCRIPTION 1457 "Describes the requirements for conformance with the SMON MIB 1458 with support for priority level Statistics. Mandatory for a SMON 1459 probe in a environment where IEEE 802.1p priority-switching is 1460 implemented." 1461 MODULE -- this module 1462 MANDATORY-GROUPS {dataSourceCapsGroup, 1463 smonPrioStatsGroup} 1464 ::= { smonMIBCompliances 3 } 1466 portCopyCompliance MODULE-COMPLIANCE 1467 STATUS current 1468 DESCRIPTION 1469 "Describes the requirements for conformance with the port copy 1470 fuctionality defined by the SMON MIB" 1471 MODULE -- this module 1472 MANDATORY-GROUPS {dataSourceCapsGroup, 1473 portCopyConfigGroup} 1474 ::= { smonMIBCompliances 4} 1476 dataSourceCapsGroup OBJECT-GROUP 1477 OBJECTS {dataSourceCapsObject, 1478 dataSourceRmonCaps, 1479 dataSourceCopyCaps, 1480 dataSourceCapsIfIndex} 1481 STATUS current 1482 DESCRIPTION 1483 "Defines the objects that describe the capabilities of RMON data 1484 sources." 1485 ::= {smonMIBGroups 1 } 1487 smonVlanStatsGroup OBJECT-GROUP 1488 OBJECTS { smonVlanStatsControlIndex, 1489 smonVlanStatsControlDataSource, 1490 smonVlanStatsControlCreateTime, 1491 smonVlanStatsControlOwner, 1492 smonVlanStatsControlStatus, 1493 smonVlanIdStatsId, 1494 smonVlanIdStatsTotalPkts, 1495 smonVlanIdStatsTotalOverflowPkts, 1496 smonVlanIdStatsTotalHCPkts, 1497 smonVlanIdStatsTotalOctets, 1498 smonVlanIdStatsTotalOverflowOctets, 1499 smonVlanIdStatsTotalHCOctets, 1500 smonVlanIdStatsNUcastPkts, 1501 smonVlanIdStatsNUcastOverflowPkts, 1502 smonVlanIdStatsNUcastHCPkts, 1503 smonVlanIdStatsNUcastOctets, 1504 smonVlanIdStatsNUcastOverflowOctets, 1505 smonVlanIdStatsNUcastHCOctets, 1506 smonVlanIdStatsCreateTime} 1507 STATUS current 1508 DESCRIPTION 1509 "Defines the switch monitoring specific statistics - per vLAN Id." 1510 ::= { smonMIBGroups 2 } 1512 smonPrioStatsGroup OBJECT-GROUP 1513 OBJECTS { smonPrioStatsControlIndex, 1514 smonPrioStatsControlDataSource, 1515 smonPrioStatsControlCreateTime, 1516 smonPrioStatsControlOwner, 1517 smonPrioStatsControlStatus, 1518 smonPrioStatsId, 1519 smonPrioStatsPkts, 1520 smonPrioStatsOverflowPkts, 1521 smonPrioStatsHCPkts, 1522 smonPrioStatsOctets, 1523 smonPrioStatsOverflowOctets, 1524 smonPrioStatsHCOctets} 1525 STATUS current 1526 DESCRIPTION 1527 "Defines the switch monitoring specific statistics - per vLAN Id." 1528 ::= { smonMIBGroups 3 } 1530 portCopyConfigGroup OBJECT-GROUP 1531 OBJECTS { portCopySource, 1532 portCopyDest, 1533 portCopyDestDropEvents, 1534 portCopyStatus 1535 } 1536 STATUS current 1537 DESCRIPTION 1538 "Defines the control objects for copy port operations" 1539 ::= { smonMIBGroups 4 } 1541 END 1543 6. References 1545 [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 1546 S. Waldbusser, "Structure of Management Information for version 2 1547 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, 1548 January 1996. 1550 [2] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 1551 S. Waldbusser, "Textual Conventions for version 2 of the Simple 1552 Network Management Protocol (SNMPv2)", RFC 1903, January 1996. 1554 [3] McCloghrie, K., and M. Rose, Editors, "Management Information Base 1555 for Network Management of TCP/IP-based internets: MIB-II", STD 17, 1556 RFC 1213, Hughes LAN Systems, Performance Systems International, 1557 March 1991. 1559 [4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 1560 S. Waldbusser, "Protocol Operations for version 2 of the Simple 1561 Network Management Protocol (SNMPv2)", RFC 1905, January 1996. 1563 [5] McCloghrie, K., and Kastenholtz, F., "Interfaces Group Evolution", 1564 RFC 1573, Hughes LAN Systems, FTP Software, January 1994. 1566 [6] Information Processing Systems -- Open Systems Interconnection -- 1567 Specification of Abstract Syntax Notation One (ASN.1), International 1568 Organization for Standardization. International Standard 8824, 1569 (December, 1987) 1571 [7] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 1572 S. Waldbusser, "Conformance Statements for version 2 of the Simple 1573 Network Management Protocol (SNMPv2)", RFC 1904, January 1996. 1575 [8] Case, J., M. Fedor, M. Schoffstall, J. Davin, "Simple Network 1576 Management Protocol", RFC 1157, SNMP Research, Performance Systems 1577 International, MIT Laboratory for Computer Science, May 1990. 1579 [9] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 1580 S. Waldbusser, "Transport Mappings for version 2 of the Simple 1581 Network Management Protocol (SNMPv2)", RFC 1906, January 1996. 1583 [10] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 1584 S. Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, 1585 January 1996. 1587 [11] S. Waldbusser, "Remote Network Monitoring Management Information 1588 Base Version 2 using SMIv2", RFC 2021, January 1997. 1590 [12] S. Waldbusser, "Remote Network Monitoring Management 1591 Information Base", RFC 1757, February, 1995 1593 [13] K. McCloghrie, A. Bierman, "Entity MIB", RFC 2037, October1996 1595 [14] T. Jeffree, "Draft Standard for Virtual Bridged Local Area 1596 Networks", P802.1Q/D6, May 1997 1598 [15] T. Jeffree, "Standard for Local and Metropolitan Area Networks - 1599 Supplement to Media Access Control (MAC) Bridges: Traffic Class Expediting 1600 and Dynamic Multicast Filtering", P802.1p/D6, May 1997 1602 [16] K. De Graaf, D. Romascanu, D. McMaster, K. McCloghrie, "Definitions of 1603 Managed Objects for IEEE 802.3 Repeater Devices using SMIv2", RFC 2108, 1604 February 1997 1606 [17] K. McCloghrie, F. Kastenholz, "Interfaces Group MIB", 1607 draft-ietf-ifmib-mib-05.txt, November 1996 1609 [18] E.Decker, etc. - Definitions of Managed Objects for Bridges, 1610 RFC 1493, July 1993 1612 7. Security Considerations 1614 In order to implement this MIB, an agent must make certain management 1615 information available about various logical and physical entities 1616 within a managed system, which may be considered sensitive in some 1617 network environments. 1619 Therefore, a network administrator may wish to employ instance-level 1620 access control, and configure the Entity MIB access (i.e., community 1621 strings in SNMPv1 and SNMPv2C), such that certain instances within 1622 this MIB, are excluded from particular MIB views. 1624 8. Authors' Addresses 1625 Richard Waterman 1626 Email: rwaterma@msn.com 1628 Bill Lahaye 1629 Cabletron Systems 1630 Email: lahaye@ctron.com 1632 Dan Romascanu 1633 Madge Networks 1634 Atidim Technology Park, Bldg. 3 1635 Tel Aviv 61131 1636 Israel 1638 Steven Waldbusser 1639 International Network Services 1640 Phone: (415) 254-4251 1641 EMail: waldbusser@ins.com