idnits 2.17.1 draft-ietf-rmonmib-smon-04.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-24) 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 39 longer pages, the longest (page 2) being 60 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 40 pages 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 44 instances of too long lines in the document, the longest one being 4 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 313 has weird spacing: '...ty than copy ...' == Line 1389 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 1765, but no explicit reference was found in the text == Unused Reference: '7' is defined on line 1786, but no explicit reference was found in the text == Unused Reference: '8' is defined on line 1790, but no explicit reference was found in the text == Unused Reference: '9' is defined on line 1794, but no explicit reference was found in the text == Unused Reference: '10' is defined on line 1798, but no explicit reference was found in the text == Unused Reference: '16' is defined on line 1817, 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 Oct. 22, 1997 9 Richard Waterman 10 Allot Networks Inc. 11 rwaterma@msn.com 13 Bill Lahaye 14 Cabletron Systems 15 lahaye@ctron.com 17 Dan Romascanu 18 Madge Networks 19 dromasca@madge.com 21 Steve Waldbusser 22 INS 23 waldbusser@ins.com 25 Status of this Memo 27 This document is an Internet-Draft. Internet-Drafts are working 28 documents of the Internet Engineering Task Force (IETF), its areas, 29 and its working groups. Note that other groups may also distribute 30 working documents as Internet-Drafts. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet- Drafts as reference 35 material or to cite them other than as ``work in progress.'' 37 To learn the current status of any Internet-Draft, please check the 38 ``1id-abstracts.txt'' listing contained in the Internet- Drafts 39 Shadow Directories on ds.internic.net (US East Coast), nic.nordu.net 40 (Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific 41 Rim). 43 Abstract 45 This memo defines a portion of the Management Information Base (MIB) 46 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 2 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 8 63 2.4.1 The RMON and RMON2 MIBs 8 64 2.4.2 The Interfaces Group MIB 9 65 2.4.3 The Entity MIB 9 66 2.4.4 The Bridge MIB 10 67 2.5 Relationship with IEEE 802.1 Standards 10 68 3. SMON/RMON Groups 10 69 3.1 SMON ProbeCapabilities 10 70 3.2 smonVlanStats 11 71 3.3 smonPrioStats 11 72 3.4 dataSourceCaps 11 73 3.5 portCopyConfig 11 74 4. Control of Remote Network Monitoring Devices 12 75 5. Definitions 13 76 6. References 38 77 7. Security Considerations 39 78 8. Authors' Addresses 40 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 one 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, that 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 at 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 draft standard 'Draft Standard for 279 Virtual Bridged Local Area Networks', P802.1Q/D6, May 1997 281 entPhysicalEntry. 283 A dataSource of this form refers to a physical entity within 284 the agent and is called an 'entity-based' dataSource. 286 In addition to these new dataSource types, SMON introduces a new 287 group called dataSourceCapsTable to aid an NMS in discovering 288 dataSource identity and attributes. 290 The extended data source mechanism supported by the SMON MIB allows 291 for the use of external collection points, similar to the one defined 292 and supported by the RMON-1 and RMON-2 MIBs, as well as internal col- 293 lection points(e.g. propVirtual ifTable entry, entPhysicalEntry). 294 The latter reflects either data sources which may be the result of 295 aggregation(e.g.switch-wide) or internal channels of physical enti- 296 ties, which have the capability of being monitored by an SMON 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 confi- 303 guration 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 implementa- 328 tions to (if supported) instrument a destination drop count on port 329 copy to provide NMS applications a sense of the quality of data 330 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 smonPrioStats collec- 336 tions. These functions allow VLAN-ID or user priority distributions 337 per dataSource. VLAN monitoring provides a high-level view of total 338 VLAN usages and relative non-unicast traffic usage as well as a pro- 339 file of VLAN priority as defined in the 3-bit user_priority field. 341 NOTE: priority stats reflect what was parsed from the packet, not 342 what priority, if any, was necessarily granted by the switch. 344 2.4 Relationship to Other MIBs 346 2.4.1 The RMON and RMON2 MIBs 348 The Remote Monitoring MIB (RMON-1) [12] provides several management 349 functions that may be directly or indirectly applicable to switched 350 networks. 352 The port copy mechanisms defined by the RMON MIB allow for the desti- 353 nation ports to become a data source for any RMON-1 statistics. How- 354 ever, an NMS application should check whether it is in the device 355 capability(portCopyCap) to filter errors from a source to a destina- 356 tion port and whether this capability is enabled, in order to provide 357 a correct interpretation of the copied port traffic. 359 RMON I host and matrix group statistics entries may be aggregated by 360 use of the extended dataSource capability defined in SMON. RMON II 361 groups are similarly extended through the use of SMON's dataSource 362 definition. 364 RMON-1 also defines a simple thresholding monitoring mechanism, 365 event-logging and event-notification for any MIB instance; SMON util- 366 izes the alarms and events groups from RMON-1 without modification. 367 These groups should be implemented on SMON devices if a simple 368 thresholding mechanism is desired. 370 The RMON II usrHistory group (user-defined history collection) should 371 be implemented by an SMON device if a history collection mechanism is 372 desired for smonStats entries. 374 2.4.2 The Interfaces Group MIB 376 The Interfaces Group MIB [5], [17] extends aspects of MIB-II [3]. 377 This document discusses the 'interfaces' group of MIB-II, especially 378 the experience gained from the definition of numerous media- specific 379 MIB modules for use in conjunction with the 'interfaces' group for 380 managing various sub-layers beneath the internetwork layer. It 381 specifies clarifications to, and extensions of, the architectural 382 issues within the previous model used for the 'interfaces' group. 384 The Interfaces Group MIB also includes a MIB module. As well as 385 including new MIB definitions to support the architectural exten- 386 sions, this MIB module also re-specifies the 'interfaces' group of 387 MIB-II in a manner that is both compliant to the SNMPv2 SMI and 388 semantically identical to the existing SNMPv1-based definitions. 390 The SMON MIB utilizes the propVirtual(53) ifType defined in the 391 Interfaces Group MIB [17] to provide SMON and RMON with new 392 dataSources such as VLANs and internal monitoring points. NMS appli- 393 cations should consult the SMON dataSource capabilities group 394 (dataSourceCap) for a description of these virtual interfaces. 396 2.4.3 The Entity MIB 398 The scope of the Entity MIB [13] is to allow an NMS to interrogate a 399 standard SNMP context and thereby discover what logical and physical 400 entities exist, how to access the MIB information of each logical 401 entity, and the relationships between the various entities. The MIB 402 should support both a single agent or multiple agents in one physical 403 entity. 405 A "physical entity" or "physical component" represents an identifi- 406 able physical resource within a managed system. Zero or more logical 407 entities may utilize a physical resource at any given time. It is an 408 implementation-specific matter as to which physical components are 409 represented by an agent in the entPhysicalTable. Typically, physical 410 resources (e.g. communications ports, backplanes, sensors, daughter- 411 cards, power supplies, the overall chassis, the overall switch), 412 which can be managed via functions associated with one or more logi- 413 cal entities are included in the MIB. 415 The SMON MIB does not mandate Entity MIB support, but allows for phy- 416 sical entities, as defined by this MIB to be defined as SMON data 417 sources. For such cases, the support for the entPhysicalTable is 418 required. 420 2.4.4 The Bridge MIB 422 One of the important indicators for measuring the effectiveness of a 423 switching device is the ratio between the number of forwarded frames 424 and the number of dropped frames at the switch port. 426 It is out of the scope of this MIB to provide instrumentation infor- 427 mation relative to switching devices. However, such indication may be 428 part of other MIB modules. 430 For instance the Bridge MIB [18] provides such MIB objects, for the 431 802.1 bridges (dot1dTpPortInFrames, dot1dTpPortInDiscards) and 432 switches managed according to the 802.1 bridge model may provide this 433 information. 435 2.5 Relationship with IEEE 802.1 Standards 437 The SMON MIB provides simple statistics per VLAN and priority levels. 438 Those two categories of statistics are important to managers of 439 switched networks. Interoperability for those features is ensured by 440 the use of the IEEE 802.1 p/Q standards ([14], [15]) defined by the 441 IEEE 802.1 WG. Interoperability from the SMON MIB point of view is 442 ensured by referencing the IEEE definition of VLANs and priority lev- 443 els, for the SMON statistics. 445 3. SMON Groups 447 3.1 SMON ProbeCapabilities 449 The SMON probeCapabilities BITS object covers the following four 450 capabilities. 452 - smonVlanStats(1) 453 The probe supports the smonVlanStats object group. 455 - smonPrioStats(2) 456 The probe supports the smonPrioStats object group. 458 - dataSource(3) 459 The probe supports the dataSource object group. 461 - portCopy(4) 462 The probe supports the portCopy object group. 464 3.2 smonVlanStats 466 The smonVlanStats MIB group includes the control and statistics 467 objects related to 802.1q VLANs. Specific statistics per 802.1q vir- 468 tual LAN are supported. The group provides a high level view of total 469 VLAN usage, and relative non-unicast traffic usage. 471 It is an implementation-specific matter as to how the agent deter- 472 mines the proper default-VLAN for untagged or priority-tagged frames. 474 3.3 smonPrioStats 476 The smonPrioStatsTable provides a distribution based on the 477 user_priority field in the VLAN header. 479 Note that this table merely reports priority as encoded in VLAN 480 headers, not the priority (if any) given the frame for actual switch- 481 ing purposes. 483 3.4 dataSourceCaps 485 The dataSourceCaps MIB group identifies all supported data sources on 486 an SMON device. An NMS may use this table to discover the RMON and 487 Copy Port attributes of each data source. 489 Upon restart of the agent, the dataSourceTable, ifTable and entPhysi- 490 calTable are initialized for the available data sources. The agent 491 may modify these tables as data sources become known or are 492 removed(e.g. hot swap of interfaces, chassis cards or the discovery 493 of VLAN usage). It is understood that dataSources representing VLANs 494 may not always be instantiated immediately upon restart, but rather 495 as VLAN usage is detected by the agent. The agent should attempt to 496 create dataSource and interface entries for all dataSources as soon 497 as possible. 499 For each dataSourceCapsEntry representing a VLAN or entPhysicalEntry, 500 the agent must create an associated ifEntry with a ifType value of 501 'propVirtual(53)'. This ifEntry will be used as the actual value in 502 RMON control table dataSource objects. The assigned ifIndex value is 503 copied into the associated dataSourceCapsIfIndex object. 505 3.5 portCopyConfig 506 The portCopyConfig MIB group includes the objects defined for the 507 control of the port copy functionality in a device. 509 The standard does not place a limit on the mode by which this copy 510 function may be used: 512 Mode 1 -- 1:1 Copy 514 Single dataSource copied to a single destination dataSource. 515 Agent may limit configuration based on ifTypes, ifSpeeds, half- 516 duplex/full-duplex, or agent resources. In this mode the single 517 instance of the portCopyDestDropEvents object refers to dropped 518 frames on the portCopyDest interface. 520 Mode 2 -- N:1 Copy 522 Multiple dataSources copied to a single destination dataSource. 523 Agent may limit configuration based on ifTypes, ifSpeeds, half- 524 duplex/full-duplex, portCopyDest over-subscription, or agent 525 resources. In this mode all N instances of the portCopyDestDro- 526 pEvents object should contain the same value, and refer to dropped 527 frames on the portCopyDest interface. 529 Mode 3 -- N:M Copy 531 Multiple dataSources copied to multiple destination dataSources. 532 Agent may limit configuration based on ifTypes, ifSpeeds, half- 533 duplex/full-duplex, portCopyDest over-subscription, or agent 534 resources. Since portCopyDestDropEvents is kept per destination 535 port, all instances of the portCopyDestDropEvents object associ- 536 ated with(indexed by) a given portCopyDest should have the same 537 value(i.e. replicated or aliased for each instance associated with 538 a given portCopyDest). 540 The rows do not have an OwnerString, since multiple rows may be part 541 of the same portCopy operation. The agent is expected to activate or 542 deactivate entries one at a time, based on the rowStatus for the 543 given row. This can lead to unpredictable results in Modes 2 and 3 544 in applications utilizing the portCopy target traffic, if multiple 545 PDUs are used to fully configure the operation. It is recommended 546 that an entire portCopy operation be configured in one SetRequest PDU 547 if possible. 549 The portCopyDest object may not reference an interface associated 550 with a packet-based VLAN (rmonVlanDataSource.V), but this dataSource 551 type may be used as a portCopySource. 553 4. Control of Remote Network Monitoring Devices 554 Due to the complex nature of the available functions in these dev- 555 ices, the functions often need user configuration. In many cases, 556 the function requires parameters to be set up for a data collection 557 operation. The operation can proceed only after these parameters are 558 fully set up. 560 Many functional groups in this MIB have one or more tables in which 561 to set up control parameters, and one or more data tables in which to 562 place the results of the operation. The control tables are typically 563 read/write in nature, while the data tables are typically read/only. 564 Because the parameters in the control table often describe resulting 565 data in the data table, many of the parameters can be modified only 566 when the control entry is not active. Thus, the method for modifying 567 these parameters is to de-activate the entry, perform the SNMP Set 568 operations to modify the entry, and then re-activate the entry. 569 Deleting the control entry causes the deletion of any associated data 570 entries, which also gives a convenient method for reclaiming the 571 resources used by the associated data. 573 Some objects in this MIB provide a mechanism to execute an action on 574 the remote monitoring device. These objects may execute an action as 575 a result of a change in the state of the object. For those objects 576 in this MIB, a request to set an object to the same value as it 577 currently holds would thus cause no action to occur. 579 To facilitate control by multiple managers, resources have to be 580 shared among the managers. These resources are typically the memory 581 and computation resources that a function requires. 583 The control mechanisms defined and used in this MIB are the same as 584 those defined in the RMON MIB [11], for control functionality and 585 interaction with multiple managers. 587 5. Definitions 589 SMON-MIB DEFINITIONS ::= BEGIN 591 IMPORTS 592 MODULE-IDENTITY, OBJECT-TYPE, Counter32, 593 Integer32, Counter64, experimental 594 FROM SNMPv2-SMI 595 RowStatus, TEXTUAL-CONVENTION 596 FROM SNMPv2-TC 597 OwnerString 598 FROM RMON-MIB 599 LastCreateTime, DataSource, rmonConformance, probeConfig 600 FROM RMON2-MIB 601 InterfaceIndex 602 FROM IF-MIB 603 MODULE-COMPLIANCE, OBJECT-GROUP 604 FROM SNMPv2-CONF; 606 switchRMON MODULE-IDENTITY 607 LAST-UPDATED "9709000000Z" 608 ORGANIZATION "IETF RMON MIB Working Group" 609 CONTACT-INFO 610 "IETF RMONMIB WG Mailing list: rmonmib@cisco.com 612 Rich Waterman 613 Allot Networks Inc. 614 Phone: +1 408 559 0253 615 Email: rwaterma@msn.com 617 Bill Lahaye 618 Cabletron Systems 619 Phone: +1 603 337 5211 620 Email: lahaye@ctron.com 622 Dan Romascanu 623 Madge Networks 624 Phone: +972 3 645 8414 625 Email: dromasca@madge.com 627 Steven Waldbusser 628 International Network Services 629 Phone: (415) 254-4251 630 Email: waldbusser@ins.com" 632 DESCRIPTION 633 "The MIB module for managing remote monitoring device 634 implementations for Switched Networks" 635 ::= { experimental 1000 } 637 smonMIBObjects OBJECT IDENTIFIER ::= { switchRMON 1 } 639 dataSourceCaps OBJECT IDENTIFIER ::= {smonMIBObjects 1} 640 smonStats OBJECT IDENTIFIER ::= {smonMIBObjects 2} 641 portCopyConfig OBJECT IDENTIFIER ::= {smonMIBObjects 3} 642 smonRegistrationPoints OBJECT IDENTIFIER ::= {smonMIBObjects 4} 644 -- Textual Conventions 645 -- 646 SmonDataSource ::= TEXTUAL-CONVENTION 647 STATUS current 648 DESCRIPTION 649 "Identifies the source of the data that the associated function 650 is configured to analyse. This macro extends the DataSource 651 Textual Convention defined by RMON-2 to the following data 652 source types: 654 - ifIndex. 655 DataSources of this traditional form are called 'port-based', 656 but only if ifType. is not equal to 'propVirtual(53)'. 658 - smonVlanDataSource. 659 A dataSource of this form refers to a 'Packet-based VLAN' and 660 is called a 'VLAN-based' dataSource. is the VLAN ID, as defined 661 by the IEEE 802.1Q standard. 663 - entPhysicalEntry. 664 A dataSource of this form refers to a physical entity within 665 the agent (e.g. entPhysicalClass = backplane(4)) and is called 666 an 'entity-based' dataSource." 667 SYNTAX OBJECT IDENTIFIER 668 -- 669 -- The smonCapabilities object describes SMON agent capabilites 670 -- 671 -- 672 smonCapabilities OBJECT-TYPE 673 SYNTAX BITS { 674 smonVlanStats(0), 675 smonPrioStats(1), 676 dataSource(2), 677 portCopy(4) 678 } 679 MAX-ACCESS read-only 680 STATUS current 681 DESCRIPTION 682 "An indication of the SMON MIB groups supported 683 by this agent." 684 ::= { probeConfig 15 } 686 -- dataSourceCaps MIB group - defines SMON data source and port copy 687 -- capabilities for devices supporting SMON. 689 -- A NMS application will check this MIB group and retrieve information 690 -- about the SMON capabilities of the device before applying SMON 691 -- control operations to the device. 693 -- dataSourceCapsTable: defines capabilities of RMON data sources 695 dataSourceCapsTable OBJECT-TYPE 696 SYNTAX SEQUENCE OF DataSourceCapsEntry 697 MAX-ACCESS not-accessible 698 STATUS current 699 DESCRIPTION 700 "This table describes RMON data sources and port copy capabilities. 701 An NMS may use this table to discover the identity and attributes of 702 the data sources on a given agent implementation. Similar to the 703 probeCapabilities object, actual row-creation operations will 704 succeed or fail based on the resources available and parameter 705 values used in each row-creation operation. 707 Upon restart of the RMON agent, the dataSourceTable, ifTable, and 708 perhaps entPhysicalTable are initialized for the available 709 dataSources. 711 For each dataSourceCapsEntry representing a VLAN or entPhysicalEntry 712 the agent must create an associated ifEntry with a ifType value of 713 'propVirtual(53)'. This ifEntry will be used as the actual value 714 in RMON control table dataSource objects. The assigned ifIndex 715 value is copied into the associated dataSourceCapsIfIndex object. 717 It is understood that dataSources representing VLANs may not always 718 be instantiated immediately upon restart, but rather as VLAN usage 719 is detected by the agent. The agent should attempt to create 720 dataSource and interface entries for all dataSources as soon as 721 possible." 722 ::= { dataSourceCaps 1 } 724 dataSourceCapsEntry OBJECT-TYPE 725 SYNTAX DataSourceCapsEntry 726 MAX-ACCESS not-accessible 727 STATUS current 728 DESCRIPTION 729 "Entries per data source containing descriptions of data source and 730 port copy capabilities. This table is populated by the RMON agent 731 with one entry for each supported data source." 732 INDEX { IMPLIED dataSourceCapsObject } 733 ::= { dataSourceCapsTable 1 } 735 DataSourceCapsEntry ::= SEQUENCE { 736 dataSourceCapsObject 737 SmonDataSource, 738 dataSourceRmonCaps 739 BITS, 740 dataSourceCopyCaps 741 BITS, 742 dataSourceCapsIfIndex 743 InterfaceIndex 745 } 747 dataSourceCapsObject OBJECT-TYPE 748 SYNTAX SmonDataSource 749 MAX-ACCESS not-accessible 750 STATUS current 751 DESCRIPTION 752 "Defines an object that can be a SMON data source or a 753 source or a destination for a port copy operation." 754 ::= { dataSourceCapsEntry 1 } 756 dataSourceRmonCaps OBJECT-TYPE 757 SYNTAX BITS { 758 countErrFrames(0), 759 countAllGoodFrames(1), 760 countAnyRmonTables(2), 761 babyGiantsCountAsGood(3) 762 } 763 MAX-ACCESS read-only 764 STATUS current 765 DESCRIPTION 766 " General attributes of the specified dataSource. 767 Note that these are static attributes, which should not 768 be adjusted because of current resources or configuration. 770 - countErrFrames(0) 771 The agent sets this bit for the dataSource if errored frames 772 received on this dataSource can actually be monitored by the agent. 773 The agent clears this bit is any errored frames are not visible to 774 the RMON data collector. 776 - countAllGoodFrames(1) 777 The agent sets this bit for the dataSource if all good frames 778 received on this dataSource can actually be monitored by the 779 agent. 780 The agent clears this bit if any good frames are not visible for 781 RMON collection, e.g., the dataSource is a non-promiscuous 782 interface or an internal switch interface which may not receive 783 frames which were switched in hardware or dropped by the bridge 784 forwarding function. 786 - countAnyRmonTables(2) 787 The agent sets this bit if this dataSource can actually be used in 788 any of the implemented RMON tables, resources notwithstanding. 789 The agent clears this bit if this dataSourceCapsEntry is present 790 simply to identify a dataSource that may only be used as 791 portCopySource and/or a portCopyDest, but not the source of an 792 actual RMON data collection. 794 - babyGiantsCountAsGood(3) 795 The agent sets this bit if it can distinguish, for counting 796 purposes, between true giant frames and frames that exceed 797 Ethernet maximum frame size 1518 due to VLAN tagging 798 ('baby giants'). Specifically, this BIT means that frames up 799 to 1522 octets are counted as good. 801 Agents not capable of detecting 'baby giants' will clear this bit 802 and will view all frames less than or equal to 1518 octets as 803 'good frames' and all frames larger than 1518 octets as 'bad 804 frames' for the purpose of counting in the smonVlanIdStats and 805 smonPrioStats tables. 807 Agents capable of detecting 'baby giants' shall consider them as 808 'good frames' for the purpose of counting in the smonVlanIdStats 809 and smonPrioStats tables." 811 ::= { dataSourceCapsEntry 2 } 813 dataSourceCopyCaps OBJECT-TYPE 814 SYNTAX BITS { 815 copySourcePort(0), 816 copyDestPort(1), 817 copySrcTxTraffic(2), 818 copySrcRxTraffic(3), 819 countDestDropEvents(4), 820 copyErrFrames(5), 821 copyUnalteredFrames(6), 822 copyAllGoodFrames(7) 823 } 824 MAX-ACCESS read-only 825 STATUS current 826 DESCRIPTION 827 " PortCopy function capabilities of the specified dataSource. 828 Note that these are static capabilities, which should not be adjusted 829 because of current resources or configuration. 831 - copySourcePort(0) 832 The agent sets this bit if this dataSource is capable of acting 833 as a source of a portCopy operation. The agent clears this bit 834 otherwise. 836 - copyDestPort(1) 837 The agent sets this bit if this dataSource is capable of acting as 838 a destination of a portCopy operation. The agent clears this bit 839 otherwise. 841 - copySrcTxTraffic(2) 842 If the copySourcePort bit is set: 843 The agent sets this bit if this dataSource is capable of 844 copying frames transmitted out this portCopy source. 845 The agent clears this bit otherwise. This function is 846 needed to support full-duplex ports. 847 Else this bit should be cleared. 849 - copySrcRxTraffic(3) 850 If the copySourcePort bit is set: 851 The agent sets this bit if this dataSource is capable of 852 copying frames received on this portCopy source. 853 The agent clears this bit otherwise. This function is 854 needed to support full-duplex ports. 855 Else this bit should be cleared. 857 - countDestDropEvents(4) 858 If the copyDestPort bit is set: 859 The agent sets this bit if it is capable of incrementing 860 portCopyDestDropEvents, when this dataSource is the target 861 of a portCopy operation and a frame destined to this dataSource is 862 dropped (for RMON counting purposes). 863 Else this BIT should be cleared. 865 - copyErrFrames(5) 866 If the copySourcePort bit is set: 867 The agent sets this bit if it is capable of copying all errored 868 frames from this portCopy source-port, for errored frames 869 received on this dataSource. 870 Else this BIT should be cleared. 872 - copyUnalteredFrames(6) 873 If the copySourcePort bit is set: 874 The agent sets this bit if it is capable of copying all frames 875 from this portCopy source-port without alteration in any way; 876 including, but not limited to: 877 - truncation (with or without CRC regeneration) 878 - proprietary header insertion 879 - MAC header rewrite 880 - VLAN retagging 881 Else this bit should be cleared. 883 - copyAllGoodFrames(7) 884 If the copySourcePort bit is set: 885 The agent sets this bit for the dataSource if all good frames 886 received on this dataSource are normally capable of being copied 887 by the agent. The agent clears this bit if any good frames are 888 not visible for the RMON portCopy operation, e.g., the dataSource 889 is a non-promiscuous interface or an internal switch interface 890 which may not receive frames which were switched in hardware or 891 dropped by the bridge forwarding function. 892 Else this bit should be cleared." 894 ::= { dataSourceCapsEntry 3 } 896 dataSourceCapsIfIndex OBJECT-TYPE 897 SYNTAX InterfaceIndex 898 MAX-ACCESS read-only 899 STATUS current 900 DESCRIPTION 901 "This object contains the ifIndex value of the ifEntry associated 902 with this smonDataSource. The agent must create 'propVirtual' 903 ifEntries for each dataSourceCapsEntry of type VLAN or 904 entPhysicalEntry." 905 ::= { dataSourceCapsEntry 4 } 907 -- The SMON Statistics MIB Group 909 -- aggregated statistics for IEEE 802.1Q VLAN environments. 911 -- VLAN statistics can be gathered by configuring 912 -- smonVlanIdStats and/or smonPrioStats collections. These functions 913 -- allow a VLAN-ID or user priority distributions per dataSource, 914 -- auto-populated by the agent in a manner similar to the RMON1 hostTable. 916 -- Only good frames are counted in the tables described in this section. 918 -- VLAN ID Stats 920 -- smonVlanStatsControlTable allows configuration of VLAN-ID collections. 922 smonVlanStatsControlTable OBJECT-TYPE 923 SYNTAX SEQUENCE OF SmonVlanStatsControlEntry 924 MAX-ACCESS not-accessible 925 STATUS current 926 DESCRIPTION 927 "Controls the setup of VLAN statistics tables. 929 The statistics collected represent a distribution based 930 on the IEEE 802.1Q VLAN-ID (VID), for each good frame 931 attributed to the data source for the collection." 932 ::= { smonStats 1 } 934 smonVlanStatsControlEntry OBJECT-TYPE 935 SYNTAX SmonVlanStatsControlEntry 936 MAX-ACCESS not-accessible 937 STATUS current 938 DESCRIPTION 939 "A conceptual row in the smonVlanStatsControlTable. 940 An example of the indexing of this entry is 941 smonVlanStatsControlCreateTime.7" 942 INDEX { smonVlanStatsControlIndex } 943 ::= { smonVlanStatsControlTable 1 } 945 SmonVlanStatsControlEntry ::= SEQUENCE { 946 smonVlanStatsControlIndex Integer32, 947 smonVlanStatsControlDataSource DataSource, 948 smonVlanStatsControlCreateTime LastCreateTime, 949 smonVlanStatsControlOwner OwnerString, 950 smonVlanStatsControlStatus RowStatus 951 } 953 smonVlanStatsControlIndex OBJECT-TYPE 954 SYNTAX Integer32 (1..65535) 955 MAX-ACCESS not-accessible 956 STATUS current 957 DESCRIPTION 958 "A unique arbitrary index for this smonVlanStatsControlEntry." 959 ::= { smonVlanStatsControlEntry 1 } 961 smonVlanStatsControlDataSource OBJECT-TYPE 962 SYNTAX DataSource 963 MAX-ACCESS read-create 964 STATUS current 965 DESCRIPTION 966 "The source of data for this set of VLAN statistics. 968 This object may not be modified if the associated 969 smonVlanStatsControlStatus object is equal to active(1)." 970 ::= { smonVlanStatsControlEntry 2 } 972 smonVlanStatsControlCreateTime OBJECT-TYPE 973 SYNTAX LastCreateTime 974 MAX-ACCESS read-only 975 STATUS current 976 DESCRIPTION 977 "The value of sysUpTime when this control entry was last 978 activated. This can be used by the management station to 979 ensure that the table has not been deleted and recreated 980 between polls." 981 ::= { smonVlanStatsControlEntry 3 } 983 smonVlanStatsControlOwner OBJECT-TYPE 984 SYNTAX OwnerString 985 MAX-ACCESS read-create 986 STATUS current 987 DESCRIPTION 988 "The entity that configured this entry and is 989 therefore using the resources assigned to it." 990 ::= { smonVlanStatsControlEntry 4 } 992 smonVlanStatsControlStatus OBJECT-TYPE 993 SYNTAX RowStatus 994 MAX-ACCESS read-create 995 STATUS current 996 DESCRIPTION 997 "The status of this row. 999 An entry may not exist in the active state unless all 1000 objects in the entry have an appropriate value. 1002 If this object is not equal to active(1), all associated 1003 entries in the smonVlanIdStatsTable shall be deleted." 1004 ::= { smonVlanStatsControlEntry 5 } 1006 -- The VLAN Statistics Table 1007 -- The smonVlanIdStatsTable provides a distribution based on the IEEE 802.1Q 1008 -- VLAN-ID (VID), for each frame attributed to the data source for the 1009 -- collection. 1011 -- This function applies the same rules for attributing frames to VLAN-based 1012 -- collections. RMON VLAN statistics are collected after the Ingress Rules 1013 -- defined in section 3.13 of the VLAN Specification (P802.1Q/D6) 1014 -- are applied. 1016 -- It is possible that entries in this table will be garbage-collected, 1017 -- based on agent resources, and VLAN configuration. Agents are encouraged 1018 -- to support all 4096 index values and not garbage collect this table. 1020 smonVlanIdStatsTable OBJECT-TYPE 1021 SYNTAX SEQUENCE OF SmonVlanIdStatsEntry 1022 MAX-ACCESS not-accessible 1023 STATUS current 1024 DESCRIPTION 1025 "Contains the VLAN statistics data. 1026 The statistics collected represent a distribution based 1027 on the IEEE 802.1Q VLAN-ID (VID), for each good frame 1028 attributed to the data source for the collection." 1030 ::= { smonStats 2 } 1032 smonVlanIdStatsEntry OBJECT-TYPE 1033 SYNTAX SmonVlanIdStatsEntry 1034 MAX-ACCESS not-accessible 1035 STATUS current 1036 DESCRIPTION 1037 "A conceptual row in smonVlanIdStatsTable." 1038 INDEX { smonVlanStatsControlIndex, smonVlanIdStatsId } 1039 ::= { smonVlanIdStatsTable 1 } 1041 SmonVlanIdStatsEntry ::= SEQUENCE { 1042 smonVlanIdStatsId Integer32, 1043 smonVlanIdStatsTotalPkts Counter32, 1044 smonVlanIdStatsTotalOverflowPkts Counter32, 1045 smonVlanIdStatsTotalHCPkts Counter64, 1046 smonVlanIdStatsTotalOctets Counter32, 1047 smonVlanIdStatsTotalOverflowOctets Counter32, 1048 smonVlanIdStatsTotalHCOctets Counter64, 1049 smonVlanIdStatsNUcastPkts Counter32, 1050 smonVlanIdStatsNUcastOverflowPkts Counter32, 1051 smonVlanIdStatsNUcastHCPkts Counter64, 1052 smonVlanIdStatsNUcastOctets Counter32, 1053 smonVlanIdStatsNUcastOverflowOctets Counter32, 1054 smonVlanIdStatsNUcastHCOctets Counter64, 1055 smonVlanIdStatsCreateTime LastCreateTime 1056 } 1058 smonVlanIdStatsId OBJECT-TYPE 1059 SYNTAX Integer32 (0..4095) 1060 MAX-ACCESS not-accessible 1061 STATUS current 1062 DESCRIPTION 1063 "The unique identifier of the VLAN monitored for 1064 this specific statistics collection. 1066 Tagged packets match the VID for the range between 1067 1 and 4095. An external RMON probe may detect VID=0 on a Inter 1068 Switch Link, in which case the packet belongs to a VLAN determined 1069 by the PVID of the ingress port. The VLAN belonging of such a packet 1070 can be determined only by a RMON probe internal to the switch." 1071 REFERENCE 1072 "Draft Standard for Virtual Bridged Local Area Networks, P802.1Q/D6, 1073 chapter 3.13" 1074 ::= { smonVlanIdStatsEntry 1 } 1076 smonVlanIdStatsTotalPkts OBJECT-TYPE 1077 SYNTAX Counter32 1078 MAX-ACCESS read-only 1079 STATUS current 1080 DESCRIPTION 1081 "The total number of packets counted on 1082 this VLAN." 1083 ::= { smonVlanIdStatsEntry 2 } 1085 smonVlanIdStatsTotalOverflowPkts OBJECT-TYPE 1086 SYNTAX Counter32 1087 MAX-ACCESS read-only 1088 STATUS current 1089 DESCRIPTION 1090 "The number of times the associated smonVlanIdStatsTotalPkts 1091 counter has overflowed." 1092 ::= { smonVlanIdStatsEntry 3 } 1094 smonVlanIdStatsTotalHCPkts OBJECT-TYPE 1095 SYNTAX Counter64 1096 MAX-ACCESS read-only 1097 STATUS current 1098 DESCRIPTION 1099 " The total number of packets counted on 1100 this VLAN." 1101 ::= { smonVlanIdStatsEntry 4 } 1103 smonVlanIdStatsTotalOctets OBJECT-TYPE 1104 SYNTAX Counter32 1105 MAX-ACCESS read-only 1106 STATUS current 1107 DESCRIPTION 1108 "The total number of octets counted on 1109 this VLAN." 1110 ::= { smonVlanIdStatsEntry 5 } 1112 smonVlanIdStatsTotalOverflowOctets OBJECT-TYPE 1113 SYNTAX Counter32 1114 MAX-ACCESS read-only 1115 STATUS current 1116 DESCRIPTION 1117 "The number of times the associated smonVlanIdStatsTotalOctets 1118 counter has overflowed." 1119 ::= { smonVlanIdStatsEntry 6 } 1121 smonVlanIdStatsTotalHCOctets OBJECT-TYPE 1122 SYNTAX Counter64 1123 MAX-ACCESS read-only 1124 STATUS current 1125 DESCRIPTION 1126 " The total number of octets counted on 1127 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 1196 -- on the value of the 3-bit user priority field encoded in the TCI. 1197 -- Note that this table merely reports priority as encoded in the VLAN 1198 -- headers, not the priority (if any) given to the frame for the actual 1199 -- switching purposes. 1201 smonPrioStatsControlTable OBJECT-TYPE 1202 SYNTAX SEQUENCE OF SmonPrioStatsControlEntry 1203 MAX-ACCESS not-accessible 1204 STATUS current 1205 DESCRIPTION 1206 "Controls the setup of priority statistics tables. 1208 smonPrioStatsControlTable allows configuration of 1209 collections based on the value of the 3-bit user 1210 priority field encoded in the TCI." 1212 ::= { smonStats 3 } 1214 smonPrioStatsControlEntry OBJECT-TYPE 1215 SYNTAX SmonPrioStatsControlEntry 1216 MAX-ACCESS not-accessible 1217 STATUS current 1218 DESCRIPTION 1219 "A conceptual row in the smonPrioStatsControlTable. 1221 An example of the indexing of this entry is 1222 smonPrioStatsControlCreateTime.7" 1223 INDEX { smonPrioStatsControlIndex } 1224 ::= { smonPrioStatsControlTable 1 } 1226 SmonPrioStatsControlEntry ::= SEQUENCE { 1227 smonPrioStatsControlIndex Integer32, 1228 smonPrioStatsControlDataSource DataSource, 1229 smonPrioStatsControlCreateTime LastCreateTime, 1230 smonPrioStatsControlOwner OwnerString, 1231 smonPrioStatsControlStatus RowStatus 1232 } 1234 smonPrioStatsControlIndex OBJECT-TYPE 1235 SYNTAX Integer32 (1..65535) 1236 MAX-ACCESS not-accessible 1237 STATUS current 1238 DESCRIPTION 1239 "A unique arbitrary index for this smonPrioStatsControlEntry." 1240 ::= { smonPrioStatsControlEntry 1 } 1242 smonPrioStatsControlDataSource OBJECT-TYPE 1243 SYNTAX DataSource 1244 MAX-ACCESS read-create 1245 STATUS current 1246 DESCRIPTION 1247 "The source of data for this set of VLAN statistics. 1249 This object may not be modified if the associated 1250 smonPrioStatsControlStatus object is equal to active(1)." 1251 ::= { smonPrioStatsControlEntry 2 } 1253 smonPrioStatsControlCreateTime OBJECT-TYPE 1254 SYNTAX LastCreateTime 1255 MAX-ACCESS read-only 1256 STATUS current 1257 DESCRIPTION 1258 "The value of sysUpTime when this control entry was last 1259 activated. This can be used by the management station to 1260 ensure that the table has not been deleted and recreated 1261 between polls." 1262 ::= { smonPrioStatsControlEntry 3 } 1264 smonPrioStatsControlOwner OBJECT-TYPE 1265 SYNTAX OwnerString 1266 MAX-ACCESS read-create 1267 STATUS current 1268 DESCRIPTION 1269 "The entity that configured this entry and is 1270 therefore using the resources assigned to it." 1271 ::= { smonPrioStatsControlEntry 4 } 1273 smonPrioStatsControlStatus OBJECT-TYPE 1274 SYNTAX RowStatus 1275 MAX-ACCESS read-create 1276 STATUS current 1277 DESCRIPTION 1278 "The status of this row. 1280 An entry may not exist in the active state unless all 1281 objects in the entry have an appropriate value. 1283 If this object is not equal to active(1), all associated 1284 entries in the smonPrioStatsTable shall be deleted." 1285 ::= { smonPrioStatsControlEntry 5 } 1287 -- The Priority Statistics Table 1289 smonPrioStatsTable OBJECT-TYPE 1290 SYNTAX SEQUENCE OF SmonPrioStatsEntry 1291 MAX-ACCESS not-accessible 1292 STATUS current 1293 DESCRIPTION 1294 "Contains the priority statistics. 1295 The collections are based on the value of the 3-bit user 1296 priority field encoded in the TCI. Note that this 1297 table merely reports priority as encoded in the VLAN 1298 headers, not the priority (if any) given to the frame 1299 for the actual switching purposes." 1300 ::= { smonStats 4 } 1302 smonPrioStatsEntry OBJECT-TYPE 1303 SYNTAX SmonPrioStatsEntry 1304 MAX-ACCESS not-accessible 1305 STATUS current 1306 DESCRIPTION 1307 "A conceptual row in smonPrioStatsTable." 1308 INDEX { smonPrioStatsControlIndex, smonPrioStatsId } 1309 ::= { smonPrioStatsTable 1 } 1311 SmonPrioStatsEntry ::= SEQUENCE { 1312 smonPrioStatsId Integer32, 1313 smonPrioStatsPkts Counter32, 1314 smonPrioStatsOverflowPkts Counter32, 1315 smonPrioStatsHCPkts Counter64, 1316 smonPrioStatsOctets Counter32, 1317 smonPrioStatsOverflowOctets Counter32, 1318 smonPrioStatsHCOctets Counter64 1319 } 1321 smonPrioStatsId OBJECT-TYPE 1322 SYNTAX Integer32 (0..7) 1323 MAX-ACCESS not-accessible 1324 STATUS current 1325 DESCRIPTION 1326 "The unique identifier of the priority level monitored for 1327 this specific statistics collection." 1328 REFERENCE 1329 " Draft Standard for Virtual Bridged Local Area Networks, 1330 P802.1Q/D6, chapter 4.3.2.1" 1331 ::= { smonPrioStatsEntry 1 } 1333 smonPrioStatsPkts OBJECT-TYPE 1334 SYNTAX Counter32 1335 MAX-ACCESS read-only 1336 STATUS current 1337 DESCRIPTION 1338 "The total number of packets counted on 1339 this priority level." 1340 ::= { smonPrioStatsEntry 2 } 1342 smonPrioStatsOverflowPkts OBJECT-TYPE 1343 SYNTAX Counter32 1344 MAX-ACCESS read-only 1345 STATUS current 1346 DESCRIPTION 1347 "The number of times the associated smonPrioStatsPkts 1348 counter has overflowed." 1349 ::= { smonPrioStatsEntry 3 } 1351 smonPrioStatsHCPkts OBJECT-TYPE 1352 SYNTAX Counter64 1353 MAX-ACCESS read-only 1354 STATUS current 1355 DESCRIPTION 1356 " The total number of packets counted on 1357 this priority level." 1358 ::= { smonPrioStatsEntry 4 } 1360 smonPrioStatsOctets OBJECT-TYPE 1361 SYNTAX Counter32 1362 MAX-ACCESS read-only 1363 STATUS current 1364 DESCRIPTION 1365 "The total number of octets counted on 1366 this priority level." 1367 ::= { smonPrioStatsEntry 5 } 1369 smonPrioStatsOverflowOctets OBJECT-TYPE 1370 SYNTAX Counter32 1371 MAX-ACCESS read-only 1372 STATUS current 1373 DESCRIPTION 1374 "The number of times the associated smonPrioStatsOctets 1375 counter has overflowed." 1376 ::= { smonPrioStatsEntry 6 } 1378 smonPrioStatsHCOctets OBJECT-TYPE 1379 SYNTAX Counter64 1380 MAX-ACCESS read-only 1381 STATUS current 1382 DESCRIPTION 1383 " The total number of octets counted on 1384 this priority level." 1385 ::= { smonPrioStatsEntry 7 } 1387 -- Port Copy provides the ability to copy all frames from a 1388 -- a specified source to specified destination within a switch. 1389 -- Source and destinations should be MIB-II ifEntries. 1390 -- One to one, one to many, many to one and many to many source 1391 -- to destination relationships may be configured. 1392 -- 1393 -- Applicable counters on the destination will increment for 1394 -- all packets transmitted, be it by normal bridging/switching 1395 -- or due to packet copy. 1396 -- Note that this table manages no RMON data collection by itself, 1397 -- and an agent may possibly implement no other RMON objects except the 1398 -- probeCapabilities scalar, the dataSourceCapsTable, and this table. 1400 portCopyTable OBJECT-TYPE 1401 SYNTAX SEQUENCE OF PortCopyEntry 1402 MAX-ACCESS not-accessible 1403 STATUS current 1404 DESCRIPTION 1405 "This table provides the ability to configure the copy port 1406 functionality. Source and destinations are MIB-II 1407 ifEntries. 1409 One to one, many to one and one to many source to destination 1410 relationships may be configured. 1412 Each row that exists in this table defines such a 1413 relationship. By disabling a row in this table the port copy 1414 relationship no longer exists. 1416 The number of entries and the types of port copies(1-1, many-1, 1417 1-many) are implementation specific and could possibly be dynamic 1418 due to changing resource availability. 1420 In order to configure a source to destination portCopy 1421 relationship, both source and destination interfaces must be 1422 present as an ifEntry in the ifTable and their respective 1423 ifAdminStatus and ifOperStatus values are equal to 'up(1)'. 1424 If the value of any of those two objects changes after the 1425 portCopyEntry is activated, portCopyStatus will transition to 1426 'notReady(3)'. 1428 The capability of a interface to be source or destination of 1429 a port copy operation is described by the 'copySourcePort(0)' 1430 and 'copyDestPort(1)' bits in dataSourceCopyCaps. Those bits 1431 should be respectively set, in order to allow for a portCopyEntry 1432 to be created. 1434 Applicable counters on the destination will increment for 1435 all packets transmitted, be it by normal bridging/switching 1436 or due to packet copy." 1438 ::= { portCopyConfig 1 } 1440 portCopyEntry OBJECT-TYPE 1441 SYNTAX PortCopyEntry 1442 MAX-ACCESS not-accessible 1443 STATUS current 1444 DESCRIPTION 1445 "Describes a particular port copy entry." 1446 INDEX { portCopySource, portCopyDest } 1447 ::= { portCopyTable 1 } 1449 PortCopyEntry ::= SEQUENCE { 1450 portCopySource 1451 InterfaceIndex, 1452 portCopyDest 1453 InterfaceIndex, 1454 portCopyDestDropEvents 1455 Counter32, 1456 portCopyStatus 1457 RowStatus 1458 } 1460 portCopySource OBJECT-TYPE 1461 SYNTAX InterfaceIndex (1..65535) 1462 MAX-ACCESS not-accessible 1463 STATUS current 1464 DESCRIPTION 1465 "The ifIndex of the source which will have all packets redirected to 1466 the destination as defined by portCopyDest." 1467 ::= { portCopyEntry 1 } 1469 portCopyDest OBJECT-TYPE 1470 SYNTAX InterfaceIndex (1..65535) 1471 MAX-ACCESS not-accessible 1472 STATUS current 1473 DESCRIPTION 1474 "Defines the ifIndex destination for the copy operation." 1475 ::= { portCopyEntry 2 } 1477 portCopyDestDropEvents OBJECT-TYPE 1478 SYNTAX Counter32 1479 MAX-ACCESS read-only 1480 STATUS current 1481 DESCRIPTION 1482 "The total number of events in which port copy packets 1483 were dropped by the switch at the destination port due to 1484 lack of resources. 1485 Note that this number is not necessarily the number of 1486 packets dropped; it is just the number of times this 1487 condition has been detected. 1488 A single dropped event counter is maintained for each 1489 portCopyDest. Thus all instances associated with a given 1490 portCopyDest will have the same portCopyDestDropEvents value." 1491 ::= { portCopyEntry 3 } 1493 portCopyStatus OBJECT-TYPE 1494 SYNTAX RowStatus 1495 MAX-ACCESS read-write 1496 STATUS current 1497 DESCRIPTION 1498 "Defines the status of the port copy entry." 1499 ::= { portCopyEntry 4 } 1501 -- smonRegistrationPoints 1502 -- defines a set of OIDs for registration purposes of entities 1503 -- supported by the SMON MIB. 1505 smonVlanDataSource OBJECT IDENTIFIER ::= { smonRegistrationPoints 1} 1507 -- Defined for use as an SmonDataSource. A single integer parameter 1508 -- is appended to the end of this OID when actually encountered in 1509 -- the dataSourceCapsTable, which represents a positive, non-zero VLAN 1510 -- identifier value. 1512 -- Conformance Macros 1514 smonMIBCompliances OBJECT IDENTIFIER ::= { rmonConformance 3} 1515 smonMIBGroups OBJECT IDENTIFIER ::= { rmonConformance 4} 1517 smonMIBCompliance MODULE-COMPLIANCE 1518 STATUS current 1519 DESCRIPTION 1520 "Describes the requirements for full conformance with the SMON MIB" 1521 MODULE -- this module 1522 MANDATORY-GROUPS {dataSourceCapsGroup, 1523 smonVlanStatsGroup, 1524 smonPrioStatsGroup, 1525 portCopyConfigGroup, 1526 smonInformationGroup} 1528 GROUP smonHcTo100mbGroup 1529 DESCRIPTION 1530 "This group of Vlan statistics counter are mandatory only 1531 for those network interfaces for which the corresponding 1532 ifSpeed can be greater than 10MB/sec and less than or equal 1533 to 100MB/sec." 1535 GROUP smonHc100mbPlusGroup 1536 DESCRIPTION 1537 "This group of Vlan statistics counters are mandatory only 1538 for those network interfaces for which the corresponding 1539 ifSpeed can be more than 100MB/sec. This group of Vlan 1540 statistics is also mandatory for smonDataSources of type 1541 VLAN or entPhysicalEntry." 1543 ::= { smonMIBCompliances 1 } 1545 smonMIBVlanStatsCompliance MODULE-COMPLIANCE 1546 STATUS current 1547 DESCRIPTION 1548 "Describes the requirements for conformance with the SMON MIB 1549 with support for VLAN Statistics. Mandatory for a SMON probe in 1550 environment where IEEE 802.1Q bridging is implemented." 1551 MODULE -- this module 1552 MANDATORY-GROUPS {dataSourceCapsGroup, 1553 smonVlanStatsGroup, 1554 smonInformationGroup} 1555 GROUP hcVlanTo100mbGroup 1556 DESCRIPTION 1557 "This group of VLAN statistics counter are mandatory only 1558 for those network interfaces for which the corresponding 1559 ifSpeed can be up to and including 100MB/sec." 1561 GROUP hcVlan100mbPlusGroup 1562 DESCRIPTION 1563 "This group of VLAN statistics counters are mandatory only 1564 for those network interfaces for which the corresponding 1565 ifSpeed is greater than 100MB/sec. This group of VLAN 1566 statistics is also mandatory for smonDataSources of type 1567 VLAN or entPhysicalEntry." 1569 ::= { smonMIBCompliances 2 } 1571 smonMIBPrioStatsCompliance MODULE-COMPLIANCE 1572 STATUS current 1573 DESCRIPTION 1574 "Describes the requirements for conformance with the SMON MIB 1575 with support for priority level Statistics. Mandatory for a SMON 1576 probe in a environment where IEEE 802.1p priority-switching is 1577 implemented." 1578 MODULE -- this module 1579 MANDATORY-GROUPS {dataSourceCapsGroup, 1580 smonPrioStatsGroup, 1581 smonInformationGroup} 1583 GROUP hcPrioTo100mbGroup 1584 DESCRIPTION 1585 "This group of VLAN priority statistics counters are 1586 mandatory only for those network interfaces for which 1587 the corresponding ifSpeed can be up to and including 100MB/sec." 1589 GROUP hcPrio100mbPlusGroup 1590 DESCRIPTION 1591 "This group is mandatory only for those network 1592 interfaces for which the corresponding ifSpeed is greater 1593 than 100MB/sec. This group of VLAN priority 1594 statistics is also mandatory for smonDataSources of type 1595 VLAN or entPhysicalEntry" 1597 ::= { smonMIBCompliances 3 } 1599 portCopyCompliance MODULE-COMPLIANCE 1600 STATUS current 1601 DESCRIPTION 1602 "Describes the requirements for conformance with the port copy 1603 functionality defined by the SMON MIB" 1605 MODULE -- this module 1606 MANDATORY-GROUPS {dataSourceCapsGroup, 1607 portCopyConfigGroup, 1608 smonInformationGroup} 1609 ::= { smonMIBCompliances 4} 1611 dataSourceCapsGroup OBJECT-GROUP 1612 OBJECTS { dataSourceRmonCaps, 1613 dataSourceCopyCaps, 1614 dataSourceCapsIfIndex} 1615 STATUS current 1616 DESCRIPTION 1617 "Defines the objects that describe the capabilities of RMON data 1618 sources." 1619 ::= {smonMIBGroups 1 } 1621 smonVlanStatsGroup OBJECT-GROUP 1622 OBJECTS { smonVlanStatsControlDataSource, 1623 smonVlanStatsControlCreateTime, 1624 smonVlanStatsControlOwner, 1625 smonVlanStatsControlStatus, 1626 smonVlanIdStatsTotalPkts, 1627 smonVlanIdStatsTotalOctets, 1628 smonVlanIdStatsNUcastPkts, 1629 smonVlanIdStatsCreateTime} 1630 STATUS current 1631 DESCRIPTION 1632 "Defines the switch monitoring specific statistics - per VLAN Id 1633 on interfaces of 10MB or less." 1634 ::= { smonMIBGroups 2 } 1636 smonPrioStatsGroup OBJECT-GROUP 1637 OBJECTS { smonPrioStatsControlDataSource, 1638 smonPrioStatsControlCreateTime, 1639 smonPrioStatsControlOwner, 1640 smonPrioStatsControlStatus, 1641 smonPrioStatsPkts, 1642 smonPrioStatsOctets} 1643 STATUS current 1644 DESCRIPTION 1645 "Defines the switch monitoring specific statistics - per VLAN Id 1646 on interface." 1647 ::= { smonMIBGroups 3 } 1649 smonHcTo100mbGroup OBJECT-GROUP 1650 OBJECTS { smonVlanIdStatsTotalOverflowOctets, 1651 smonVlanIdStatsTotalHCOctets, 1652 smonPrioStatsOverflowOctets, 1653 smonPrioStatsHCOctets} 1654 STATUS current 1655 DESCRIPTION 1656 "Defines the additional high capacity statistics needed to 1657 be kept on interfaces with ifSpeed greater than 10MB/sec and less 1658 than or equal to 100MB/sec." 1659 ::= { smonMIBGroups 4 } 1661 smonHc100mbPlusGroup OBJECT-GROUP 1662 OBJECTS { smonVlanIdStatsTotalOverflowPkts, 1663 smonVlanIdStatsTotalHCPkts, 1664 smonVlanIdStatsTotalOverflowOctets, 1665 smonVlanIdStatsTotalHCOctets, 1666 smonVlanIdStatsNUcastOverflowPkts, 1667 smonVlanIdStatsNUcastHCPkts, 1668 smonPrioStatsOverflowPkts, 1669 smonPrioStatsHCPkts, 1670 smonPrioStatsOverflowOctets, 1671 smonPrioStatsHCOctets} 1672 STATUS current 1673 DESCRIPTION 1674 "Defines the additional high capacity statistics needed to 1675 be kept on interfaces with ifSpeed of more than 100MB/sec. 1676 These statistics must also be kept on smonDataSources of 1677 type VLAN or entPhysicalEntry." 1678 ::= { smonMIBGroups 5 } 1680 hcVlanTo100mbGroup OBJECT-GROUP 1681 OBJECTS { smonVlanIdStatsTotalOverflowOctets, 1682 smonVlanIdStatsTotalHCOctets} 1683 STATUS current 1684 DESCRIPTION 1685 "Defines the additional high capacity VLAN statistics 1686 needed to be kept on interfaces with ifSpeed greater than 1687 10MB/sec and less than or equal to 100MB/sec." 1688 ::= { smonMIBGroups 6 } 1690 hcVlan100mbPlusGroup OBJECT-GROUP 1691 OBJECTS { smonVlanIdStatsTotalOverflowPkts, 1692 smonVlanIdStatsTotalHCPkts, 1693 smonVlanIdStatsTotalOverflowOctets, 1694 smonVlanIdStatsTotalHCOctets, 1695 smonVlanIdStatsNUcastOverflowPkts, 1696 smonVlanIdStatsNUcastHCPkts} 1697 STATUS current 1698 DESCRIPTION 1699 "Defines the additional high capacity VLAN statistics 1700 needed to be kept on interfaces with ifSpeed of more than 1701 100MB/sec. These statistics must also be kept on 1702 smonDataSources of type VLAN or entPhysicalEntry." 1703 ::= { smonMIBGroups 7 } 1705 hcPrioTo100mbGroup OBJECT-GROUP 1706 OBJECTS { smonPrioStatsOverflowOctets, 1707 smonPrioStatsHCOctets } 1708 STATUS current 1709 DESCRIPTION 1710 "Defines the additional high capacity VLAN priority 1711 statistics needed to be kept on interfaces with 1712 ifSpeed of greater than 10MB/sec and less than or equal 1713 to 100MB/sec." 1714 ::= { smonMIBGroups 8 } 1716 hcPrio100mbPlusGroup OBJECT-GROUP 1717 OBJECTS { smonPrioStatsOverflowPkts, 1718 smonPrioStatsHCPkts, 1719 smonPrioStatsOverflowOctets, 1720 smonPrioStatsHCOctets} 1721 STATUS current 1722 DESCRIPTION 1723 "Defines the additional high capacity VLAN priority 1724 statistics needed to be kept on interfaces with 1725 ifSpeed of greater than 100MB/sec. These statistics must 1726 also be kept on smonDataSources of type VLAN or 1727 entPhysicalEntry." 1728 ::= { smonMIBGroups 9 } 1730 smonVlanStatsExtGroup OBJECT-GROUP 1731 OBJECTS {smonVlanIdStatsNUcastOctets, 1732 smonVlanIdStatsNUcastOverflowOctets, 1733 smonVlanIdStatsNUcastHCOctets} 1734 STATUS current 1735 DESCRIPTION 1736 "Defines the switch monitoring specific statistics for systems 1737 capable of counting non-unicast octets for a given dataSource 1738 (as described in the dataSourceRmonCaps object)." 1739 ::= { smonMIBGroups 10 } 1741 smonInformationGroup OBJECT-GROUP 1742 OBJECTS { smonCapabilities } 1743 STATUS current 1744 DESCRIPTION 1745 "An indication of the SMON capabilities supported by this agent." 1746 ::= { smonMIBGroups 11 } 1747 portCopyConfigGroup OBJECT-GROUP 1748 OBJECTS { portCopyDestDropEvents, 1749 portCopyStatus 1750 } 1751 STATUS current 1752 DESCRIPTION 1753 "Defines the control objects for copy port operations." 1754 ::= { smonMIBGroups 12 } 1756 END 1758 6. References 1760 [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 1761 S. Waldbusser, "Structure of Management Information for version 2 1762 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, 1763 January 1996. 1765 [2] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 1766 S. Waldbusser, "Textual Conventions for version 2 of the Simple 1767 Network Management Protocol (SNMPv2)", RFC 1903, January 1996. 1769 [3] McCloghrie, K., and M. Rose, Editors, "Management Information Base 1770 for Network Management of TCP/IP-based internets: MIB-II", STD 17, 1771 RFC 1213, Hughes LAN Systems, Performance Systems International, 1772 March 1991. 1774 [4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 1775 S. Waldbusser, "Protocol Operations for version 2 of the Simple 1776 Network Management Protocol (SNMPv2)", RFC 1905, January 1996. 1778 [5] McCloghrie, K., and Kastenholtz, F., "Interfaces Group Evolution", 1779 RFC 1573, Hughes LAN Systems, FTP Software, January 1994. 1781 [6] Information Processing Systems -- Open Systems Interconnection -- 1782 Specification of Abstract Syntax Notation One (ASN.1), International 1783 Organization for Standardization. International Standard 8824, 1784 (December, 1987) 1786 [7] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 1787 S. Waldbusser, "Conformance Statements for version 2 of the Simple 1788 Network Management Protocol (SNMPv2)", RFC 1904, January 1996. 1790 [8] Case, J., M. Fedor, M. Schoffstall, J. Davin, "Simple Network 1791 Management Protocol", RFC 1157, SNMP Research, Performance Systems 1792 International, MIT Laboratory for Computer Science, May 1990. 1794 [9] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 1795 S. Waldbusser, "Transport Mappings for version 2 of the Simple 1796 Network Management Protocol (SNMPv2)", RFC 1906, January 1996. 1798 [10] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 1799 S. Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, 1800 January 1996. 1802 [11] S. Waldbusser, "Remote Network Monitoring Management Information 1803 Base Version 2 using SMIv2", RFC 2021, January 1997. 1805 [12] S. Waldbusser, "Remote Network Monitoring Management 1806 Information Base", RFC 1757, February, 1995 1808 [13] K. McCloghrie, A. Bierman, "Entity MIB", RFC 2037, October1996 1810 [14] T. Jeffree, "Draft Standard for Virtual Bridged Local Area 1811 Networks", P802.1Q/D6, May 1997 1813 [15] T. Jeffree, "Standard for Local and Metropolitan Area Networks - 1814 Supplement to Media Access Control (MAC) Bridges: Traffic Class 1815 Expediting and Dynamic Multicast Filtering", P802.1p/D6, May 1997 1817 [16] K. De Graaf, D. Romascanu, D. McMaster, K. McCloghrie, "Definitions of 1818 Managed Objects for IEEE 802.3 Repeater Devices using SMIv2", RFC 2108, 1819 February 1997 1821 [17] K. McCloghrie, F. Kastenholz, "Interfaces Group MIB", 1822 draft-ietf-ifmib-mib-05.txt, November 1996 1824 [18] E.Decker, etc. - Definitions of Managed Objects for Bridges, 1825 RFC 1493, July 1993 1827 7. Security Considerations 1829 In order to implement this MIB, an agent must make certain management 1830 information available about various logical and physical entities 1831 within a managed system, which may be considered sensitive in some 1832 network environments. 1834 Therefore, a network administrator may wish to employ instance-level 1835 access control, and configure the Entity MIB access (i.e., community 1836 strings in SNMPv1 and SNMPv2C), such that certain instances within 1837 this MIB, are excluded from particular MIB views. 1839 8. Authors' Addresses 1841 Richard Waterman 1842 Allot Networks Inc. 1843 Email: rwaterma@msn.com 1845 Bill Lahaye 1846 Cabletron Systems 1847 Email: lahaye@ctron.com 1849 Dan Romascanu 1850 Madge Networks 1851 Atidim Technology Park, Bldg. 3 1852 Tel Aviv 61131 1853 Israel 1855 Steven Waldbusser 1856 International Network Services 1857 Phone: (415) 254-4251 1858 EMail: waldbusser@ins.com