idnits 2.17.1 draft-baill-netmod-yang-ip-stats-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 14 instances of lines with control characters in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (April 27, 2015) is 3287 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) == Missing Reference: 'RFC2119' is mentioned on line 84, but not defined == Missing Reference: 'RFC 3810' is mentioned on line 146, but not defined == Missing Reference: 'RFC 7277' is mentioned on line 208, but not defined ** Obsolete undefined reference: RFC 7277 (Obsoleted by RFC 8344) == Missing Reference: 'RFC 7224' is mentioned on line 215, but not defined == Missing Reference: 'RFC0826' is mentioned on line 420, but not defined == Missing Reference: 'RFC4862' is mentioned on line 421, but not defined == Missing Reference: 'RFC4941' is mentioned on line 421, but not defined ** Obsolete undefined reference: RFC 4941 (Obsoleted by RFC 8981) == Missing Reference: 'RFC7217' is mentioned on line 421, but not defined == Missing Reference: 'RFC6536' is mentioned on line 1584, but not defined ** Obsolete undefined reference: RFC 6536 (Obsoleted by RFC 8341) == Unused Reference: 'RFC3810' is defined on line 1640, but no explicit reference was found in the text == Unused Reference: 'RFC7277' is defined on line 1657, but no explicit reference was found in the text == Unused Reference: 'XML' is defined on line 1660, but no explicit reference was found in the text == Unused Reference: 'RFC7224' is defined on line 1667, but no explicit reference was found in the text == Unused Reference: 'RFC4293' is defined on line 1670, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2460 (Obsoleted by RFC 8200) ** Obsolete normative reference: RFC 7223 (Obsoleted by RFC 8343) ** Obsolete normative reference: RFC 7277 (Obsoleted by RFC 8344) -- Possible downref: Non-RFC (?) normative reference: ref. 'XML' Summary: 7 errors (**), 0 flaws (~~), 15 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET-DRAFT S.Baillargeon 3 Intended Status: Standards Track Ericsson 4 Expires: October 29, 2015 April 27, 2015 6 A YANG Data Model for basic IP and ICMP Statistics 7 draft-baill-netmod-yang-ip-stats-01 9 Abstract 11 This document defines a YANG data model for basic IP and ICMP 12 statistics for monitoring IPv4 and IPv6 implementations. 14 Status of this Memo 16 This Internet-Draft is submitted to IETF in full conformance with the 17 provisions of BCP 78 and BCP 79. 19 Internet-Drafts are working documents of the Internet Engineering 20 Task Force (IETF), its areas, and its working groups. Note that 21 other groups may also distribute working documents as 22 Internet-Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet-Drafts as reference 27 material or to cite them other than as "work in progress." 29 The list of current Internet-Drafts can be accessed at 30 http://www.ietf.org/1id-abstracts.html 32 The list of Internet-Draft Shadow Directories can be accessed at 33 http://www.ietf.org/shadow.html 35 Copyright and License Notice 37 Copyright (c) 2015 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (http://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 53 1.1 Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3 54 1.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 3 55 2 IP Stats Model . . . . . . . . . . . . . . . . . . . . . . . . 4 56 3 Relationship to IP-MIB . . . . . . . . . . . . . . . . . . . . 8 57 4 IP Statistics YANG Module . . . . . . . . . . . . . . . . . . . 11 58 5 Security Considerations . . . . . . . . . . . . . . . . . . . . 35 59 6 IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 35 60 7 References . . . . . . . . . . . . . . . . . . . . . . . . . . 36 61 7.1 Normative References . . . . . . . . . . . . . . . . . . . 36 62 7.2 Informative References . . . . . . . . . . . . . . . . . . 37 63 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 37 65 1 Introduction 67 This document defines a YANG [RFC6020] data model for collecting 68 basic IP and ICMP statistics for monitoring IPv4 and IPv6 69 implementations. 71 The data model defines the following IP layer statistics: 73 o ICMPv4 system statistics 75 o ICMPv6 system statistics 77 o IP interface statistics 79 1.1 Terminology 81 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 82 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 83 document are to be interpreted as described in RFC 2119 [RFC2119]. 85 The following terms are defined in [RFC6241] and are not redefined 86 here: 88 o client 90 o configuration data 92 o server 94 o state data 96 o statistics 98 The following terms are defined in [RFC6020] and are not redefined 99 here: 101 o augment 103 o data model 105 o data node 107 o presence container 109 1.2. Tree Diagrams 110 A simplified graphical representation of the data model is used in 111 this document. The meaning of the symbols in these diagrams is as 112 follows: 114 o Brackets "[" and "]" enclose list keys. 116 o Abbreviations before data node names: "rw" means configuration 117 data (read-write), and "ro" means state data (read-only). 119 o Symbols after data node names: "?" means an optional node, "!" 120 means a presence container, and "*" denotes a list and leaf-list. 122 o Parentheses enclose choice and case nodes, and case nodes are also 123 marked with a colon (":"). 125 o Ellipsis ("...") stands for contents of subtrees that are not 126 shown. 128 2 IP Stats Model 130 This document defines the YANG module "ietf-ip-stats" which provides 131 the following IP layer statistics: 133 o ICMPv4 system statistics 135 o ICMPv6 system statistics 137 o IP interface statistics 139 The ICMPv4 system statistics are defined in the "icmpv4" container. 140 It provides a small set of statistics about ICMPv4 traffic processed 141 by the entire system. It is an optional node and it MAY be present 142 only if IPv4 is enabled on the system. 144 The ICMPv6 system statistics are defined in the "icmpv6" container. 145 It provides a small set of statistics about ICMPv6 traffic (including 146 MLDv2 [RFC 3810]) processed by the entire system. It is an optional 147 node and it MAY be present only if IPv6 is enabled on the system. 149 Both the "icmpv4" and "icmpv6" containers are child nodes of the top- 150 level "system-stats" container that is intended to hold any system 151 wide statistics. The "system-stats" container has the following tree 152 structure: 154 +--ro system-stats 155 +--ro icmpv4! 156 | +--ro in-msgs? yang:counter32 157 | +--ro in-errors? yang:counter32 158 | +--ro in-echo-requests? yang:counter32 159 | +--ro in-echo-replies? yang:counter32 160 | +--ro in-dest-unreachs? yang:counter32 161 | +--ro in-param-problems? yang:counter32 162 | +--ro in-time-exceeds? yang:counter32 163 | +--ro in-others? yang:counter32 164 | +--ro out-msgs? yang:counter32 165 | +--ro out-errors? yang:counter32 166 | +--ro out-echo-requests? yang:counter32 167 | +--ro out-echo-replies? yang:counter32 168 | +--ro out-dest-unreachs? yang:counter32 169 | +--ro out-param-problems? yang:counter32 170 | +--ro out-time-exceeds? yang:counter32 171 | +--ro out-others? yang:counter32 172 +--ro icmpv6! 173 +--ro in-msgs? yang:counter32 174 +--ro in-errors? yang:counter32 175 +--ro in-echo-requests? yang:counter32 176 +--ro in-echo-replies? yang:counter32 177 +--ro in-dest-unreachs? yang:counter32 178 +--ro in-param-problems? yang:counter32 179 +--ro in-time-exceeds? yang:counter32 180 +--ro in-redirects? yang:counter32 181 +--ro in-pkt-too-bigs? yang:counter32 182 +--ro in-router-solicits? yang:counter32 183 +--ro in-router-adverts? yang:counter32 184 +--ro in-neighbor-solicits? yang:counter32 185 +--ro in-neighbor-adverts? yang:counter32 186 +--ro in-MLDv2-queries? yang:counter32 187 +--ro in-MLDv2-reports? yang:counter32 188 +--ro in-others? yang:counter32 189 +--ro out-msgs? yang:counter32 190 +--ro out-errors? yang:counter32 191 +--ro out-echo-requests? yang:counter32 192 +--ro out-echo-replies? yang:counter32 193 +--ro out-dest-unreachs? yang:counter32 194 +--ro out-param-problems? yang:counter32 195 +--ro out-time-exceeds? yang:counter32 196 +--ro out-redirects? yang:counter32 197 +--ro out-pkt-too-bigs? yang:counter32 198 +--ro out-router-solicits? yang:counter32 199 +--ro out-router-adverts? yang:counter32 200 +--ro out-neighbor-solicits? yang:counter32 201 +--ro out-neighbor-adverts? yang:counter32 202 +--ro out-MLDv2-queries? yang:counter32 203 +--ro out-MLDv2-reports? yang:counter32 204 +--ro out-others? yang:counter32 206 The IP interface statistics are defined in the "stats" containers 207 belongs to a reusable "ip-if-stats" group. Such containers augment 208 the YANG IP Management module [RFC 7277] and provide a basic set of 209 statistics about IPv4 and IPv6 traffic received on and transmitted by 210 an interface. The statistics are for a specific IP address family. Up 211 to two separate set of IP statistics are supported per interface, one 212 for each IP version. The IP implementation MAY also decides to 213 support a single IP version per interface. The interface can be any 214 IP capable interface defined in the IANA Interface Type YANG module 215 [RFC 7224]. For instance, it can be: 217 o an Ethernet interface (if:type = 'ianaift:ethernetCsmacd') 219 o a link aggregate interface (if:type = 'ianaift:ieee8023adLag') 221 o a L3 IP VLAN interface (if:type = 'ianaift:l3ipvlan') 223 o a loopback interface (if:type = 'ianaift:softwareLoopback') 225 The "stats" container is an optional node and it MAY be present only 226 if IPv4 and/or IPv6 is enabled on the system. The "stats" containers 227 has the following tree structure: 229 augment /if:interfaces-state/if:interface/ip:ipv4: 230 +--ro stats 231 +--ro in-receives? yang:counter64 232 +--ro in-octets? yang:counter64 233 +--ro in-hdr-errors? yang:counter32 234 +--ro in-mcast-pkts? yang:counter64 235 +--ro in-mcast-octets? yang:counter64 236 +--ro in-bcast-pkts? yang:counter64 237 +--ro in-truncates? yang:counter32 238 +--ro in-dest-addr-errors? yang:counter32 239 +--ro in-scr-addr-errors? yang:counter32 240 +--ro in-forwards? yang:counter64 241 +--ro in-no-routes? yang:counter32 242 +--ro in-reasm-requires? yang:counter64 243 +--ro in-reasm-fails? yang:counter32 244 +--ro in-reasm-OKs? yang:counter64 245 +--ro in-unknown-protos? yang:counter32 246 +--ro in-discards? yang:counter32 247 +--ro in-delivers? yang:counter64 248 +--ro out-requests? yang:counter64 249 +--ro out-no-routes? yang:counter32 250 +--ro out-forwards? yang:counter64 251 +--ro out-frag-requires? yang:counter64 252 +--ro out-frag-fails? yang:counter32 253 +--ro out-frag-OKs? yang:counter64 254 +--ro out-frag-creates? yang:counter64 255 +--ro out-mcast-pkts? yang:counter64 256 +--ro out-mcast-octets? yang:counter64 257 +--ro out-bcast-pkts? yang:counter64 258 +--ro out-discards? yang:counter32 259 +--ro out-transmits? yang:counter64 260 +--ro out-octets? yang:counter64 261 augment /if:interfaces-state/if:interface/ip:ipv6: 262 +--ro stats 263 +--ro in-receives? yang:counter64 264 +--ro in-octets? yang:counter64 265 +--ro in-hdr-errors? yang:counter32 266 +--ro in-mcast-pkts? yang:counter64 267 +--ro in-mcast-octets? yang:counter64 268 +--ro in-bcast-pkts? yang:counter64 269 +--ro in-truncates? yang:counter32 270 +--ro in-dest-addr-errors? yang:counter32 271 +--ro in-scr-addr-errors? yang:counter32 272 +--ro in-forwards? yang:counter64 273 +--ro in-no-routes? yang:counter32 274 +--ro in-reasm-requires? yang:counter64 275 +--ro in-reasm-fails? yang:counter32 276 +--ro in-reasm-OKs? yang:counter64 277 +--ro in-unknown-protos? yang:counter32 278 +--ro in-discards? yang:counter32 279 +--ro in-delivers? yang:counter64 280 +--ro out-requests? yang:counter64 281 +--ro out-no-routes? yang:counter32 282 +--ro out-forwards? yang:counter64 283 +--ro out-frag-requires? yang:counter64 284 +--ro out-frag-fails? yang:counter32 285 +--ro out-frag-OKs? yang:counter64 286 +--ro out-frag-creates? yang:counter64 287 +--ro out-mcast-pkts? yang:counter64 288 +--ro out-mcast-octets? yang:counter64 289 +--ro out-bcast-pkts? yang:counter64 290 +--ro out-discards? yang:counter32 291 +--ro out-transmits? yang:counter64 292 +--ro out-octets? yang:counter64 294 3 Relationship to IP-MIB 296 The IP-MIB defines two ICMP statistic tables: icmpStatsTable and 297 icmpMsgStatsTable. The icmpStatsTable contains generic system-wide 298 ICMP counters for each IP version. The icmpMsgStatsTable contains 299 system-wide per-version, per-message type ICMP counters. The YANG IP 300 statistics module aggregates all ICMP statistics into one container 301 for each IP version. This module does not individually track all 302 possible ICMP type values. It only tracks the most common ICMP types 303 for each IP version and aggregate all other ICMP types into a single 304 counter. 306 The IP-MIB defines two IP statistics tables: ipSystemStatsTable and 307 ipIfStatsTable). The ipSystemStatsTable contain objects to count the 308 number of packets, fragments, datagrams and octets that a given 309 system has processed for each IP version. The ipIfStatsTable contain 310 objects to count the number of packets, fragments, datagrams and 311 octets that a given interface has received or transmitted for each IP 312 version. The data nodes defined in the "ip-if-stats" group 313 corresponds to the counters defined in ipIfStatsTable. The system 314 wide table ipSystemStatsTable is not defined in this data model. 316 The following tables list the YANG data nodes with corresponding 317 objects in the IP-MIB. 319 +--------------------------------+----------------------------------+ 320 |YANG data node in |IP-MIB Object | 321 |/ip-stats:system-stats | | 322 +--------------------------------+----------------------------------+ 323 |icmpv4/in-msgs |icmpStatsInMsgs | 324 |icmpv4/in-errors |icmpStatsInErrors | 325 |icmpv4/in-echo-requests | | 326 |icmpv4/in-echo-replies | | 327 |icmpv4/in-dest-unreachs | | 328 |icmpv4/in-param-problems | | 329 |icmpv4/in-time-exceeds | | 330 |icmpv4/in-others | | 331 |icmpv4/out-msgs |icmpStatsOutMsgs | 332 |icmpv4/out-errors |icmpStatsOutErrors | 333 |icmpv4/out-echo-requests | | 334 |icmpv4/out-echo-replies | | 335 |icmpv4/out-dest-unreachs | | 336 |icmpv4/out-param-problems | | 337 |icmpv4/out-time-exceeds | | 338 |icmpv4/out-others | | 339 +--------------------------------+----------------------------------+ 340 Table 1: YANG ICMPv4 Stats Nodes to IP-MIB Objects 342 +--------------------------------+----------------------------------+ 343 |YANG data node in |IP-MIB Object | 344 |/ip-stats:system-stats | | 345 +--------------------------------+----------------------------------+ 346 |icmpv6/in-msgs |icmpStatsInMsgs | 347 |icmpv6/in-errors |icmpStatsInErrors | 348 |icmpv6/in-echo-requests | | 349 |icmpv6/in-echo-replies | | 350 |icmpv6/in-dest-unreachs | | 351 |icmpv6/in-param-problems | | 352 |icmpv6/in-time-exceeds | | 353 |icmpv6/in-redirects | | 354 |icmpv6/in-pkt-too-bigs | | 355 |icmpv6/in-router-solicits | | 356 |icmpv6/in-router-adverts | | 357 |icmpv6/in-neighbor-solicits | | 358 |icmpv6/in-neighbor-adverts | | 359 |icmpv6/in-MLDv2-queries | | 360 |icmpv6/in-MLDv2-reports | | 361 |icmpv6/in-others | | 362 |icmpv6/out-msgs |icmpStatsInMsgs | 363 |icmpv6/out-errors |icmpStatsInErrors | 364 |icmpv6/out-echo-requests | | 365 |icmpv6/out-echo-replies | | 366 |icmpv6/out-dest-unreachs | | 367 |icmpv6/out-param-problems | | 368 |icmpv6/out-time-exceeds | | 369 |icmpv6/out-redirects | | 370 |icmpv6/out-pkt-too-bigs | | 371 |icmpv6/out-router-solicits | | 372 |icmpv6/out-router-adverts | | 373 |icmpv6/out-neighbor-solicits | | 374 |icmpv6/out-neighbor-adverts | | 375 |icmpv6/out-MLDv2-queries | | 376 |icmpv6/out-MLDv2-reports | | 377 +--------------------------------+----------------------------------+ 378 Table 2: YANG ICMPv6 Stats Nodes to IP-MIB Objects 380 +-------------------------------------+-----------------------------+ 381 |YANG data node in |IP-MIB Object | 382 |/if:interface-state/if:interface | | 383 +-------------------------------------+-----------------------------+ 384 |{ipv4,ipv6}/stats/in-receives |ipIfStatsHCInReceives | 385 |{ipv4,ipv6}/stats/in-octets |ipIfStatsHCInOctets | 386 |{ipv4,ipv6}/stats/in-hdr-errors |ipIfStatsInHdrErrors | 387 |{ipv4,ipv6}/stats/in-mcast-pkts |ipIfStatsHCInMcastPkts | 388 |{ipv4,ipv6}/stats/in-mcast-octets |ipIfStatsHCInMcastOctets | 389 |{ipv4,ipv6}/stats/in-bcast-pkts |ipIfStatsHCInBcastPkts | 390 |{ipv4,ipv6}/stats/in-truncates |ipIfStatsInTruncatedPkts | 391 |{ipv4,ipv6}/stats/in-dest-addr-errors|ipIfStatsInAddrErrors | 392 |{ipv4,ipv6}/stats/in-scr-addr-errors | | 393 |{ipv4,ipv6}/stats/in-forwards |ipIfStatsHCInForwDatagrams | 394 |{ipv4,ipv6}/stats/in-no-routes |ipIfStatsInNoRoutes | 395 |{ipv4,ipv6}/stats/in-reasm-requires |ipIfStatsReasmReqds | 396 |{ipv4,ipv6}/stats/in-reasm-fails |ipIfStatsReasmFails | 397 |{ipv4,ipv6}/stats/in-reasm-OKs |ipIfStatsReasmOKs | 398 |{ipv4,ipv6}/stats/in-unknown-protos |ipIfStatsInUnknownProtos | 399 |{ipv4,ipv6}/stats/in-discards |ipIfStatsInDiscards | 400 |{ipv4,ipv6}/stats/in-delivers |ipIfStatsHCInDelivers | 401 |{ipv4,ipv6}/stats/out-requests |ipIfStatsHCOutRequests | 402 |{ipv4,ipv6}/stats/out-no-routes | | 403 |{ipv4,ipv6}/stats/out-forwards |ipIfStatsHCOutForwDatagrams | 404 |{ipv4,ipv6}/stats/out-frag-requires |ipIfStatsOutFragReqds | 405 |{ipv4,ipv6}/stats/out-frag-fails |ipIfStatsOutFragFails | 406 |{ipv4,ipv6}/stats/out-frag-OKs |ipIfStatsOutFragOKs | 407 |{ipv4,ipv6}/stats/out-frag-creates |ipIfStatsOutFragCreates | 408 |{ipv4,ipv6}/stats/out-mcast-pkts |ipIfStatsHCOutMcastPkts | 409 |{ipv4,ipv6}/stats/out-mcast-octets |ipIfStatsHCOutMcastOctets | 410 |{ipv4,ipv6}/stats/out-bcast-pkts |ipIfStatsHCOutBcastPkts | 411 |{ipv4,ipv6}/stats/out-discards |ipIfStatsOutDiscards | 412 |{ipv4,ipv6}/stats/out-transmits |ipIfStatsHCOutTransmits | 413 |{ipv4,ipv6}/stats/out-octets |ipIfStatsHCOutOctets | 414 +-------------------------------------+-----------------------------+ 415 Table 3: YANG IP Stats Nodes to IP-MIB Objects 417 4 IP Statistics YANG Module 419 This module imports typedefs from [RFC6991] and [RFC7223], and it 420 references [RFC0791], [RFC0826], [RFC2460], [RFC4861], 421 [RFC4862],[RFC4941], and [RFC7217]. 423 file "ietf-ip-stats@2015-04-27.yang" 425 module ietf-ip-stats { 427 namespace "urn:ietf:params:xml:ns:yang:ietf-ip-stats"; 428 prefix ip-stats; 430 import ietf-ip { 431 prefix ip; 432 } 433 import ietf-interfaces { 434 prefix if; 435 } 436 import ietf-yang-types { 437 prefix yang; 438 } 440 organization 441 "IETF NETMOD (NETCONF Data Modeling Language) Working Group"; 443 contact 444 "WG Web: 445 WG List: 447 WG Chair: Thomas Nadeau 448 450 WG Chair: Juergen Schoenwaelder 451 453 Editor: Steve Baillargeon 454 "; 456 description 457 "This YANG module contains a collection of IP and ICMP statistics 458 for monitoring IPv4 and IPv6 implementations. 460 Copyright (c) 2015 IETF Trust and the persons identified as 461 authors of the code. All rights reserved. 463 Redistribution and use in source and binary forms, with or 464 without modification, is permitted pursuant to, and subject 465 to the license terms contained in, the Simplified BSD License 466 set forth in Section 4.c of the IETF Trust's Legal Provisions 467 Relating to IETF Documents 468 (http://trustee.ietf.org/license-info). 470 This version of this YANG module is part of TBD; see 471 the RFC itself for full legal notices."; 473 revision 2015-04-27 { 474 description 475 "Initial revision."; 476 reference 477 "TBD"; 478 } 480 /* 481 * Groupings 482 */ 484 grouping ip-if-stats { 485 description 486 "A group of IP layer statistics for IP traffic 487 received and transmitted by an interface."; 489 container stats { 490 config false; 491 description 492 "A collection of IP layer statistics for IP traffic 493 received and transmitted by an interface."; 495 leaf in-receives { 496 type yang:counter64; 497 units packets; 498 description 499 "The number of input IP packets received on the 500 interface, including those received in error. 502 Discontinuities in the value of this counter can occur 503 at re-initialization of the management system, and at 504 other times as indicated by the value of 505 'discontinuity-time'."; 506 reference 507 "RFC 4293: The IP MIB - ipIfStatsHCInReceives"; 508 } 510 leaf in-octets { 511 type yang:counter64; 512 units octets; 513 description 514 "The number of octets received in IP packets, 515 including those received in error. Octets from packets 516 counted in in-receives MUST be counted. 518 Discontinuities in the value of this counter can occur 519 at re-initialization of the management system, and at 520 other times as indicated by the value of 521 'discontinuity-time'."; 522 reference 523 "RFC 4293: The IP MIB - ipIfStatsHCInOctets"; 524 } 526 leaf in-hdr-errors { 527 type yang:counter32; 528 units packets; 529 description 530 "The number of input IP packets discarded due to errors 531 in their IP headers, including version number mismatch, 532 other format errors, hop count exceeded, errors 533 discovered in processing their IP options, etc. 535 Discontinuities in the value of this counter can occur 536 at re-initialization of the management system, and at 537 other times as indicated by the value of 538 'discontinuity-time'."; 539 reference 540 "RFC 4293: The IP MIB - ipIfStatsInHdrErrors"; 541 } 543 leaf in-mcast-pkts { 544 type yang:counter64; 545 units packets; 546 description 547 "The number of input IP multicast packets received on 548 the interface. 550 Discontinuities in the value of this counter can occur 551 at re-initialization of the management system, and at 552 other times as indicated by the value of 553 'discontinuity-time'."; 554 reference 555 "RFC 4293: The IP MIB - ipIfStatsHCInMcastPkts"; 556 } 558 leaf in-mcast-octets { 559 type yang:counter64; 560 units octets; 561 description 562 "The number of octets received in IP multicast 563 packets. Octets from packets counted in 564 /ipv4/in-mcast-pkts MUST be counted. 566 Discontinuities in the value of this counter can occur 567 at re-initialization of the management system, and at 568 other times as indicated by the value of 569 'discontinuity-time'."; 570 reference 571 "RFC 4293: The IP MIB - ipIfStatsHCInMcastOctets"; 572 } 574 leaf in-bcast-pkts { 575 type yang:counter64; 576 units packets; 577 description 578 "The number of input IP broadcast packets received on 579 the interface. 581 Discontinuities in the value of this counter can occur 582 at re-initialization of the management system, and at 583 other times as indicated by the value of 584 'discontinuity-time'."; 585 reference 586 "RFC 4293: The IP MIB - ipIfStatsHCInBcastPkts"; 587 } 589 leaf in-truncates { 590 type yang:counter32; 591 units packets; 592 description 593 "The number of input IP packets discarded because the 594 packet didn't carry enough data. 596 Discontinuities in the value of this counter can occur 597 at re-initialization of the management system, and at 598 other times as indicated by the value of 599 'discontinuity-time'."; 600 reference 601 "RFC 4293: The IP MIB - ipIfStatsInTruncatedPkts"; 602 } 604 leaf in-dest-addr-errors { 605 type yang:counter32; 606 units packets; 607 description 608 "The number of input IP packets discarded because the IP 609 address in their IP header's destination field was not a 610 valid address to be received at this system. For systems 611 that are not IP routers and therefore do not forward packets, 612 this counter includes packets that are discarded because 613 the destination address was not a local address. 615 Discontinuities in the value of this counter can occur 616 at re-initialization of the management system, and at 617 other times as indicated by the value of 618 'discontinuity-time'."; 619 reference 620 "RFC 4293: The IP MIB - ipIfStatsInAddrErrors"; 621 } 623 leaf in-scr-addr-errors { 624 type yang:counter32; 625 units packets; 626 description 627 "The number of input IP packets discarded because the IP 628 address in their IP header's source field was not a 629 valid address to be received at this system. This count 630 includes source filtering on multicast packets. 632 Discontinuities in the value of this counter can occur 633 at re-initialization of the management system, and at 634 other times as indicated by the value of 635 'discontinuity-time'."; 636 reference 637 "RFC 4293: The IP MIB - ipIfStatsInAddrErrors"; 638 } 640 leaf in-forwards { 641 type yang:counter64; 642 units packets; 643 description 644 "The number of input IP packets for which this system 645 was not their final IP destination and for which this 646 system attempted to find a route to forward them to that 647 final destination. 649 Discontinuities in the value of this counter can occur 650 at re-initialization of the management system, and at 651 other times as indicated by the value of 652 'discontinuity-time'."; 653 reference 654 "RFC 4293: The IP MIB - ipIfStatsHCInForwDatagrams"; 655 } 656 leaf in-no-routes { 657 type yang:counter32; 658 units packets; 659 description 660 "The number of input IP packets for which this system was 661 not their final IP destination and for which this system 662 attempted to find a route to forward them to that final 663 destination. 665 Discontinuities in the value of this counter can occur 666 at re-initialization of the management system, and at 667 other times as indicated by the value of 668 'discontinuity-time'."; 669 reference 670 "RFC 4293: The IP MIB - ipIfStatsInNoRoutes"; 671 } 673 leaf in-reasm-requires { 674 type yang:counter64; 675 units fragments; 676 description 677 "The number of input IP fragments received that needed 678 to be reassembled at this interface. 680 When tracking interface statistics, the counter of the 681 interface to which these fragments were addressed is 682 incremented. This interface might not be the same as the 683 input interface for some of the fragments. 685 Discontinuities in the value of this counter can occur 686 at re-initialization of the management system, and at 687 other times as indicated by the value of 688 'discontinuity-time'."; 689 reference 690 "RFC 4293: The IP MIB - ipIfStatsReasmReqds"; 691 } 693 leaf in-reasm-fails { 694 type yang:counter32; 695 units failures; 696 description 697 "The number of failures detected by the IP re-assembly 698 algorithm (for whatever reason: timed out, errors, etc.). 699 Note that this is not necessarily a count of discarded IP 700 fragments since some algorithms can lose track of the 701 number of fragments by combining them as they are 702 received. 704 When tracking interface statistics, the counter of the 705 interface to which these fragments were addressed is 706 incremented. This interface might not be the same as the 707 input interface for some of the fragments. 709 Discontinuities in the value of this counter can occur 710 at re-initialization of the management system, and at 711 other times as indicated by the value of 712 'discontinuity-time'."; 713 reference 714 "RFC 4293: The IP MIB - ipIfStatsReasmFails"; 715 } 717 leaf in-reasm-OKs { 718 type yang:counter64; 719 units datagrams; 720 description 721 "The number of input IP datagrams successfully 722 reassembled. 724 When tracking interface statistics, the counter of the 725 interface to which these datagrams were addressed is 726 incremented. This interface might not be the same as the 727 input interface for some of the datagrams. 729 Discontinuities in the value of this counter can occur 730 at re-initialization of the management system, and at 731 other times as indicated by the value of 732 'discontinuity-time'."; 733 reference 734 "RFC 4293: The IP MIB - ipIfStatsReasmOKs"; 735 } 737 leaf in-unknown-protos { 738 type yang:counter32; 739 units datagrams; 740 description 741 "The number of locally-addressed input IP datagrams 742 received successfully but discarded because of an unknown 743 or unsupported protocol. 745 When tracking interface statistics, the counter of the 746 interface to which these datagrams were addressed is 747 incremented. This interface might not be the same as the 748 input interface for some of the datagrams. 750 Discontinuities in the value of this counter can occur 751 at re-initialization of the management system, and at 752 other times as indicated by the value of 753 'discontinuity-time'."; 754 reference 755 "RFC 4293: The IP MIB - ipIfStatsInUnknownProtos"; 756 } 758 leaf in-discards { 759 type yang:counter32; 760 units datagrams; 761 description 762 "The number of input IP datagrams for which no problems 763 were encountered to prevent their continued processing, 764 but were discarded (e.g., for lack of buffer space). 765 Note that this counter does not include any datagrams 766 discarded while awaiting re-assembly. 768 Discontinuities in the value of this counter can occur 769 at re-initialization of the management system, and at 770 other times as indicated by the value of 771 'discontinuity-time'."; 772 reference 773 "RFC 4293: The IP MIB - ipIfStatsInDiscards"; 774 } 776 leaf in-delivers { 777 type yang:counter64; 778 units datagrams; 779 description 780 "The number of input IP datagrams successfully 781 delivered to IP user protocols (including ICMP). 783 When tracking interface statistics, the counter of the 784 interface to which these datagrams were addressed is 785 incremented. This interface might not be the same as the 786 input interface for some of the datagrams. 788 Discontinuities in the value of this counter can occur 789 at re-initialization of the management system, and at 790 other times as indicated by the value of 791 'discontinuity-time'."; 792 reference 793 "RFC 4293: The IP MIB - ipIfStatsHCInDelivers"; 794 } 796 leaf out-requests { 797 type yang:counter64; 798 units datagrams; 799 description 800 "The number of output IP datagrams that local IP user 801 protocols (including ICMP) supplied to IP in requests for 802 transmission. Note that this counter does not include any 803 datagrams counted out-forwards. 805 Discontinuities in the value of this counter can occur 806 at re-initialization of the management system, and at 807 other times as indicated by the value of 808 'discontinuity-time'."; 809 reference 810 "RFC 4293: The IP MIB - ipIfStatsHCOutRequests"; 811 } 813 leaf out-no-routes { 814 type yang:counter32; 815 units datagrams; 816 description 817 "The number of locally generated output IP datagrams 818 discarded because no route could be found to transmit 819 them to their destination. 821 Discontinuities in the value of this counter can occur 822 at re-initialization of the management system, and at 823 other times as indicated by the value of 824 'discontinuity-time'."; 825 reference 826 "RFC 4293: The IP MIB"; 827 } 829 leaf out-forwards { 830 type yang:counter64; 831 units packets; 832 description 833 "The number of output IP packets for which this system 834 was not their final IP destination and for which it was 835 successful in finding a path to their final destination. 837 When tracking interface statistics, the counter of the 838 outgoing interface is incremented for a successfully 839 forwarded packet. 841 Discontinuities in the value of this counter can occur 842 at re-initialization of the management system, and at 843 other times as indicated by the value of 844 'discontinuity-time'."; 845 reference 846 "RFC 4293: The IP MIB - ipIfStatsHCOutForwDatagrams"; 847 } 848 leaf out-frag-requires { 849 type yang:counter64; 850 units datagrams; 851 description 852 "The number of output IP datagrams that would require 853 fragmentation in order to be transmitted. 855 When tracking interface statistics, the counter of the 856 outgoing interface is incremented for a successfully 857 fragmented datagram. 859 Discontinuities in the value of this counter can occur 860 at re-initialization of the management system, and at 861 other times as indicated by the value of 862 'discontinuity-time'."; 863 reference 864 "RFC 4293: The IP MIB - ipIfStatsOutFragReqds"; 865 } 867 leaf out-frag-fails { 868 type yang:counter32; 869 units datagrams; 870 description 871 "The number of output IP datagrams that have been 872 discarded because they needed to be fragmented but 873 could not be. This includes IPv4 packets that have 874 the DF bit set or IPv6 packets that are being 875 forwarded and exceed the outgoing link MTU. 877 When tracking interface statistics, the counter of the 878 outgoing interface is incremented for a successfully 879 fragmented datagram. 881 Discontinuities in the value of this counter can occur 882 at re-initialization of the management system, and at 883 other times as indicated by the value of 884 'discontinuity-time'."; 885 reference 886 "RFC 4293: The IP MIB - ipIfStatsOutFragFails"; 887 } 889 leaf out-frag-OKs { 890 type yang:counter64; 891 units datagrams; 892 description 893 "The number of output IP datagrams that have been 894 successfully fragmented. 896 When tracking interface statistics, the counter of the 897 outgoing interface is incremented for a successfully 898 fragmented datagram. 900 Discontinuities in the value of this counter can occur 901 at re-initialization of the management system, and at 902 other times as indicated by the value of 903 'discontinuity-time'."; 904 reference 905 "RFC 4293: The IP MIB - ipIfStatsOutFragOKs"; 906 } 908 leaf out-frag-creates { 909 type yang:counter64; 910 units fragments; 911 description 912 "The number of output IP fragments that have been 913 generated as a result of IP fragmentation. 915 When tracking interface statistics, the counter of the 916 outgoing interface is incremented for a successfully 917 fragmented datagram. 919 Discontinuities in the value of this counter can occur 920 at re-initialization of the management system, and at 921 other times as indicated by the value of 922 'discontinuity-time'."; 923 reference 924 "RFC 4293: The IP MIB - ipIfStatsOutFragCreates"; 925 } 927 leaf out-mcast-pkts { 928 type yang:counter64; 929 units packets; 930 description 931 "The number of output IP multicast packets transmitted 932 on the interface. 934 Discontinuities in the value of this counter can occur 935 at re-initialization of the management system, and at 936 other times as indicated by the value of 937 'discontinuity-time'."; 938 reference 939 "RFC 4293: The IP MIB - ipIfStatsHCOutMcastPkts"; 940 } 942 leaf out-mcast-octets { 943 type yang:counter64; 944 units octets; 945 description 946 "The number of octets transmitted in IP 947 multicast packets. Octets from packets 948 counted in /ipv4/out-mcast-pkts MUST be counted. 950 Discontinuities in the value of this counter can occur 951 at re-initialization of the management system, and at 952 other times as indicated by the value of 953 'discontinuity-time'."; 954 reference 955 "RFC 4293: The IP MIB - ipIfStatsHCOutMcastOctets"; 956 } 958 leaf out-bcast-pkts { 959 type yang:counter64; 960 units packets; 961 description 962 "The number of output IP broadcast packets transmitted 963 on the interface. 965 Discontinuities in the value of this counter can occur 966 at re-initialization of the management system, and at 967 other times as indicated by the value of 968 'discontinuity-time'."; 969 reference 970 "RFC 4293: The IP MIB - ipIfStatsHCOutBcastPkts"; 971 } 973 leaf out-discards { 974 type yang:counter32; 975 units packets; 976 description 977 "The number of output IP packets for which no problem was 978 encountered to prevent their transmission to their 979 destination, but were discarded (e.g., for lack of 980 buffer space). Note that this counter would include 981 datagrams counted in out-forwards if any such 982 packets met this (discretionary) discard criterion. 984 Discontinuities in the value of this counter can occur 985 at re-initialization of the management system, and at 986 other times as indicated by the value of 987 'discontinuity-time'."; 988 reference 989 "RFC 4293: The IP MIB - ipIfStatsOutDiscards"; 990 } 991 leaf out-transmits { 992 type yang:counter64; 993 units packets; 994 description 995 "The number of output IP packets that this system 996 supplied to the lower layers for transmission. 998 Discontinuities in the value of this counter can occur 999 at re-initialization of the management system, and at 1000 other times as indicated by the value of 1001 'discontinuity-time'."; 1002 reference 1003 "RFC 4293: The IP MIB - ipIfStatsHCOutTransmits"; 1004 } 1006 leaf out-octets { 1007 type yang:counter64; 1008 units octets; 1009 description 1010 "The number of octets in output IP packets delivered 1011 to the lower layers for transmission. Octets from packets 1012 counted in out-transmits MUST be counted. 1014 Discontinuities in the value of this counter can occur 1015 at re-initialization of the management system, and at 1016 other times as indicated by the value of 1017 'discontinuity-time'."; 1018 reference 1019 "RFC 4293: The IP MIB - ipIfStatsHCOutOctets"; 1020 } 1021 } 1022 } 1024 /* 1025 * Data nodes for ICMP statistics for IP-capable system 1026 */ 1028 container system-stats { 1029 config false; 1030 description 1031 "A collection of system wide statistics"; 1033 container icmpv4 { 1034 presence 1035 "Present if IPv4 is enabled on this system"; 1036 description 1037 "A collection of ICMPv4 layer statistics processed by 1038 this system."; 1039 leaf in-msgs { 1040 type yang:counter32; 1041 units messages; 1042 description 1043 "The number of ICMPv4 messages received by this system. 1044 Note that this counter includes all those counted by 1045 /icmpv4/in-errors."; 1046 reference 1047 "RFC 4293: The IP MIB - icmpStatsInMsgs"; 1048 } 1050 leaf in-errors { 1051 type yang:counter32; 1052 units messages; 1053 description 1054 "The number of ICMPv4 messages that this system received 1055 but determined as having ICMP-specific errors (bad ICMP 1056 checksums, bad length, etc)."; 1057 reference 1058 "RFC 4293: The IP MIB - icmpStatsInErrors"; 1059 } 1061 leaf in-echo-requests { 1062 type yang:counter32; 1063 units messages; 1064 description 1065 "The number of ICMPv4 Echo Request messages 1066 (type 8) received by this system."; 1067 reference 1068 "RFC 4293: The IP MIB"; 1069 } 1071 leaf in-echo-replies { 1072 type yang:counter32; 1073 units messages; 1074 description 1075 "The number of ICMPv4 Echo Reply messages 1076 (type 0) received by this system."; 1077 reference 1078 "RFC 4293: The IP MIB"; 1079 } 1081 leaf in-dest-unreachs { 1082 type yang:counter32; 1083 units messages; 1084 description 1085 "The number of ICMPv4 Destination Unreachable messages 1086 (type 3) received by this system."; 1088 reference 1089 "RFC 4293: The IP MIB"; 1090 } 1092 leaf in-param-problems { 1093 type yang:counter32; 1094 units messages; 1095 description 1096 "The number of ICMPv4 Parameter Problem messages 1097 (type 12) received by this system."; 1098 reference 1099 "RFC 4293: The IP MIB"; 1100 } 1102 leaf in-time-exceeds { 1103 type yang:counter32; 1104 units messages; 1105 description 1106 "The number of ICMPv4 Time Exceeded messages 1107 (type 11) received by this system."; 1108 reference 1109 "RFC 4293: The IP MIB"; 1110 } 1112 leaf in-others { 1113 type yang:counter32; 1114 units messages; 1115 description 1116 "The number of any other ICMPv4 message types 1117 received by this system."; 1118 reference 1119 "RFC 4293: The IP MIB"; 1120 } 1122 leaf out-msgs { 1123 type yang:counter32; 1124 units messages; 1125 description 1126 "The number of ICMPv4 messages this system attempted to 1127 send. Note that this counter includes all those counted 1128 by /icmpv4/out-errors."; 1129 reference 1130 "RFC 4293: The IP MIB - icmpStatsOutMsgs"; 1131 } 1133 leaf out-errors { 1134 type yang:counter32; 1135 units messages; 1136 description 1137 "The number of ICMPv4 messages this system did not send 1138 due to problems discovered within ICMP, such as a lack of 1139 buffers. This value should not include errors discovered 1140 outside the ICMP layer, such as the inability of IP to 1141 route the resultant datagram."; 1142 reference 1143 "RFC 4293: The IP MIB - icmpStatsOutErrors"; 1144 } 1146 leaf out-echo-requests { 1147 type yang:counter32; 1148 units messages; 1149 description 1150 "The number of ICMPv4 Echo Request messages 1151 (type 8) this system attempted to send."; 1152 reference 1153 "RFC 4293: The IP MIB"; 1154 } 1156 leaf out-echo-replies { 1157 type yang:counter32; 1158 units messages; 1159 description 1160 "The number of ICMPv4 Echo Reply messages 1161 (type 0) this system attempted to send."; 1162 reference 1163 "RFC 4293: The IP MIB"; 1164 } 1166 leaf out-dest-unreachs { 1167 type yang:counter32; 1168 units messages; 1169 description 1170 "The number of ICMPv4 Destination Unreachable messages 1171 (type 3) this system attempted to send."; 1172 reference 1173 "RFC 4293: The IP MIB"; 1174 } 1176 leaf out-param-problems { 1177 type yang:counter32; 1178 units messages; 1179 description 1180 "The number of ICMPv4 Parameter Problem messages 1181 (type 12) this system attempted to send."; 1182 reference 1183 "RFC 4293: The IP MIB"; 1185 } 1187 leaf out-time-exceeds { 1188 type yang:counter32; 1189 units messages; 1190 description 1191 "The number of ICMPv4 Time Exceeded messages 1192 (type 11) this system attempted to send."; 1193 reference 1194 "RFC 4293: The IP MIB"; 1195 } 1197 leaf out-others { 1198 type yang:counter32; 1199 units messages; 1200 description 1201 "The number of any other ICMPv4 message types this 1202 system attempted to send."; 1203 reference 1204 "RFC 4293: The IP MIB"; 1205 } 1206 } 1208 container icmpv6 { 1209 presence 1210 "Present if IPv6 is enabled on this system"; 1211 description 1212 "A collection of ICMPv6 layer statistics for ICMPv6 traffic 1213 processed by this system."; 1215 leaf in-msgs { 1216 type yang:counter32; 1217 units messages; 1218 description 1219 "The number of ICMPv6 messages received by this system. 1220 Note that this counter includes all those counted by 1221 icmpv6/in-errors."; 1222 reference 1223 "RFC 4293: The IP MIB - icmpStatsInMsgs"; 1224 } 1226 leaf in-errors { 1227 type yang:counter32; 1228 units messages; 1229 description 1230 "The number of ICMPv6 messages that this system received 1231 but determined as having ICMP-specific errors (bad ICMP 1232 checksums, bad length, etc)."; 1234 reference 1235 "RFC 4293: The IP MIB - icmpStatsInErrors"; 1236 } 1238 leaf in-echo-requests { 1239 type yang:counter32; 1240 units messages; 1241 description 1242 "The number of ICMPv6 Echo Request messages 1243 (type 128) received by this system."; 1244 reference 1245 "RFC 4293: The IP MIB"; 1246 } 1248 leaf in-echo-replies { 1249 type yang:counter32; 1250 units messages; 1251 description 1252 "The number of ICMPv6 Echo Reply messages 1253 (type 129) received by this system."; 1254 reference 1255 "RFC 4293: The IP MIB"; 1256 } 1258 leaf in-dest-unreachs { 1259 type yang:counter32; 1260 units messages; 1261 description 1262 "The number of ICMPv6 Destination Unreachable messages 1263 (type 1) received by this system."; 1264 reference 1265 "RFC 4293: The IP MIB"; 1266 } 1268 leaf in-param-problems { 1269 type yang:counter32; 1270 units messages; 1271 description 1272 "The number of ICMPv6 Parameter Problem messages 1273 (type 4) received by this system."; 1274 reference 1275 "RFC 4293: The IP MIB"; 1276 } 1278 leaf in-time-exceeds { 1279 type yang:counter32; 1280 units messages; 1281 description 1282 "The number of ICMPv6 Time Exceeded messages 1283 (type 3) received by this system."; 1284 reference 1285 "RFC 4293: The IP MIB"; 1286 } 1288 leaf in-redirects { 1289 type yang:counter32; 1290 units messages; 1291 description 1292 "The number of ICMPv6 Redirect messages 1293 (type 137) received by this system."; 1294 reference 1295 "RFC 4293: The IP MIB"; 1296 } 1298 leaf in-pkt-too-bigs { 1299 type yang:counter32; 1300 units messages; 1301 description 1302 "The number of ICMPv6 Packet Too Big messages 1303 (type 2) received by this system."; 1304 reference 1305 "RFC 4293: The IP MIB"; 1306 } 1308 leaf in-router-solicits { 1309 type yang:counter32; 1310 units messages; 1311 description 1312 "The number of ICMPv4 Router Solicit messages 1313 (type 133) received by this system."; 1314 reference 1315 "RFC 4293: The IP MIB"; 1316 } 1318 leaf in-router-adverts { 1319 type yang:counter32; 1320 units messages; 1321 description 1322 "The number of ICMPv4 Router Advertisement messages 1323 (type 134) received by this system."; 1324 reference 1325 "RFC 4293: The IP MIB"; 1326 } 1328 leaf in-neighbor-solicits { 1329 type yang:counter32; 1330 units messages; 1331 description 1332 "The number of ICMPv6 Neighbor Solicit messages 1333 (type 135) received by this system."; 1334 reference 1335 "RFC 4293: The IP MIB"; 1336 } 1338 leaf in-neighbor-adverts { 1339 type yang:counter32; 1340 units messages; 1341 description 1342 "The number of ICMPv6 Neighbor Advertisement messages 1343 (type 136) received by this system."; 1344 reference 1345 "RFC 4293: The IP MIB"; 1346 } 1348 leaf in-MLDv2-queries { 1349 type yang:counter32; 1350 units messages; 1351 description 1352 "The number of Multicast Listener Discovery version 2 1353 Query messages(type 130 with length equal or greater 1354 than 28 bytes) received by this system."; 1355 reference 1356 "RFC 3810: MLDv2 for IPv6"; 1357 } 1359 leaf in-MLDv2-reports { 1360 type yang:counter32; 1361 units messages; 1362 description 1363 "The number of Multicast Listener Discovery version 2 1364 Report messages(type 143) received by this system."; 1365 reference 1366 "RFC 3810: MLDv2 for IPv6"; 1367 } 1369 leaf in-others { 1370 type yang:counter32; 1371 units messages; 1372 description 1373 "The number of any other ICMPv6 message types received 1374 by this system."; 1375 reference 1376 "RFC 4293: The IP MIB"; 1377 } 1378 leaf out-msgs { 1379 type yang:counter32; 1380 units messages; 1381 description 1382 "The number of ICMPv6 messages this system attempted to 1383 send. Note that this counter includes all those counted 1384 by /icmpv6/out-errors."; 1385 reference 1386 "RFC 4293: The IP MIB - icmpStatsInMsgs"; 1387 } 1389 leaf out-errors { 1390 type yang:counter32; 1391 units messages; 1392 description 1393 "The number of ICMPv6 messages that this system received 1394 but determined as having ICMP-specific errors (bad ICMP 1395 checksums, bad length, etc)."; 1396 reference 1397 "RFC 4293: The IP MIB - icmpStatsInErrors"; 1398 } 1400 leaf out-echo-requests { 1401 type yang:counter32; 1402 units messages; 1403 description 1404 "The number of ICMPv6 Echo Request messages 1405 (type 128) this system attempted to send."; 1406 reference 1407 "RFC 4293: The IP MIB"; 1408 } 1410 leaf out-echo-replies { 1411 type yang:counter32; 1412 units messages; 1413 description 1414 "The number of ICMPv6 Echo Reply messages 1415 (type 129) this system attempted to send."; 1416 reference 1417 "RFC 4293: The IP MIB"; 1418 } 1420 leaf out-dest-unreachs { 1421 type yang:counter32; 1422 units messages; 1423 description 1424 "The number of ICMPv6 Destination Unreachable messages 1425 (type 1) this system attempted to send."; 1427 reference 1428 "RFC 4293: The IP MIB"; 1429 } 1431 leaf out-param-problems { 1432 type yang:counter32; 1433 units messages; 1434 description 1435 "The number of ICMPv6 Parameter Problem messages 1436 (type 4) this system attempted to send."; 1437 reference 1438 "RFC 4293: The IP MIB"; 1439 } 1441 leaf out-time-exceeds { 1442 type yang:counter32; 1443 units messages; 1444 description 1445 "The number of ICMPv6 Time Exceeded messages 1446 (type 3) this system attempted to send."; 1447 reference 1448 "RFC 4293: The IP MIB"; 1449 } 1451 leaf out-redirects { 1452 type yang:counter32; 1453 units messages; 1454 description 1455 "The number of ICMPv6 Redirect messages 1456 (type 137) this system attempted to send."; 1457 reference 1458 "RFC 4293: The IP MIB"; 1459 } 1461 leaf out-pkt-too-bigs { 1462 type yang:counter32; 1463 units messages; 1464 description 1465 "The number of ICMPv6 Packet Too Big messages 1466 (type 2) this system attempted to send."; 1467 reference 1468 "RFC 4293: The IP MIB"; 1469 } 1471 leaf out-router-solicits { 1472 type yang:counter32; 1473 units messages; 1474 description 1475 "The number of ICMPv6 Router Solicit messages 1476 (type 133) this system attempted to send."; 1477 reference 1478 "RFC 4293: The IP MIB"; 1479 } 1481 leaf out-router-adverts { 1482 type yang:counter32; 1483 units messages; 1484 description 1485 "The number of ICMPv6 Router Advertisement messages 1486 (type 134) this system attempted to send."; 1487 reference 1488 "RFC 4293: The IP MIB"; 1489 } 1491 leaf out-neighbor-solicits { 1492 type yang:counter32; 1493 units messages; 1494 description 1495 "The number of ICMPv6 Neighbor Solicit messages 1496 (type 135) this system attempted to send."; 1497 reference 1498 "RFC 4293: The IP MIB"; 1499 } 1501 leaf out-neighbor-adverts { 1502 type yang:counter32; 1503 units messages; 1504 description 1505 "The number of ICMPv6 Neighbor Advertisement messages 1506 (type 136) this system attempted to send."; 1507 reference 1508 "RFC 4293: The IP MIB"; 1509 } 1511 leaf out-MLDv2-queries { 1512 type yang:counter32; 1513 units messages; 1514 description 1515 "The number of Multicast Listener Discovery version 2 1516 Query messages(type 130 with length equal or greater 1517 than 28 bytes) this system attempted to send."; 1518 reference 1519 "RFC 3810: MLDv2 for IPv6"; 1520 } 1522 leaf out-MLDv2-reports { 1523 type yang:counter32; 1524 units messages; 1525 description 1526 "The number of Multicast Listener Discovery version 2 1527 Report messages(type 143) this system attempted to send."; 1528 reference 1529 "RFC 3810: MLDv2 for IPv6"; 1530 } 1532 leaf out-others { 1533 type yang:counter32; 1534 units messages; 1535 description 1536 "The number of any other ICMPv6 message types 1537 this system attempted to send."; 1538 reference 1539 "RFC 4293: The IP MIB"; 1540 } 1541 } 1542 } 1543 /* 1544 * Data nodes for IP statistics for IPv4-capable interface 1545 */ 1547 augment "/if:interfaces-state/if:interface/ip:ipv4" { 1548 description 1549 "Data nodes for statistics about IPv4 traffic on an 1550 interface when IPv4 is enabled on that interface. 1552 The interface can be any IPv4-capable interface including 1553 an Ethernet interface, a link aggregate (LAG) interface, 1554 a L3 IP VLAN interface and a loopback interface."; 1556 uses ip-if-stats; 1557 } 1559 /* 1560 * Data nodes for IP statistics for IPv6-capable interface 1561 */ 1563 augment "/if:interfaces-state/if:interface/ip:ipv6" { 1564 description 1565 "Data nodes for statistics about IPv6 traffic on an 1566 interface when IPv6 is enabled on that interface. 1568 The interface can be any IPv6-capable interface including 1569 an Ethernet interface, a link aggregate (LAG) interface, 1570 a L3 IP VLAN interface and a loopback interface."; 1572 uses ip-if-stats; 1573 } 1574 } 1576 1578 5 Security Considerations 1580 The YANG module defined in this memo is designed to be accessed via 1581 the NETCONF protocol [RFC6241]. The lowest NETCONF layer is the 1582 secure transport layer and the mandatory-to-implement secure 1583 transport is SSH [RFC6242]. The NETCONF access control model 1584 [RFC6536] provides the means to restrict access for particular 1585 NETCONF users to a pre-configured subset of all available NETCONF 1586 protocol operations and content. 1588 There are a number of data nodes defined in the YANG module which are 1589 readable IP statistics (read-only counters) with config false 1590 statement. Even though these data nodes are generally not considered 1591 sensitive or vulnerable, it may be desirable to limit the number of 1592 interfaces with IP statistic collection in some network environments. 1593 These are the subtrees and data nodes and their 1594 sensitivity/vulnerability: 1596 {ipv4|ipv6}/stats: These leafs are used to collect IP statistics 1597 about a specific interface. Enabling or collecting IP statistics on 1598 all IP capable interfaces on an system may have a negative impact on 1599 its performance or data storage capacity. The IP statistics may also 1600 contain sensitive operational information about the usage of the 1601 network. 1603 6 IANA Considerations 1605 This document registers a URI in the "IETF XML Registry" [RFC3688]. 1606 Following the format in RFC 3688, the following registration has been 1607 made. 1609 URI: urn:ietf:params:xml:ns:yang:ietf-ip-stats 1611 Registrant Contact: The NETMOD WG of the IETF. 1613 XML: N/A; the requested URI is an XML namespace. 1615 This document registers a YANG module in the "YANG Module Names" 1616 registry [RFC6020]. 1618 Name: ietf-ip-stats 1619 Namespace: urn:ietf:params:xml:ns:yang:ietf-ip-stats 1620 Prefix: ip-stats 1621 Reference: RFC XXXX 1623 7 References 1625 7.1 Normative References 1627 [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, September 1628 1981. 1630 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 1631 (IPv6) Specification", RFC 2460, December 1998. 1633 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 1634 January 2004. 1636 [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, 1637 "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, 1638 September 2007. 1640 [RFC3810] Vida, R., Costa, L., "Multicast Listener Discovery 1641 Version 2 (MLDv2) for IPv6", RFC 3810, June 2004. 1643 [RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the 1644 Network Configuration Protocol (NETCONF)", RFC 6020, 1645 October 2010. 1647 [RFC6241] Enns, R., Bjorklund, M., Schoenwaelder, J., and A. 1648 Bierman, "Network Configuration Protocol (NETCONF)", RFC 1649 6241, June 2011. 1651 [RFC6991] Schoenwaelder, J., "Common YANG Data Types", RFC 6991, 1652 July 2013. 1654 [RFC7223] Bjorklund, M., "A YANG Data Model for Interface 1655 Management", RFC 7223, May 2014. 1657 [RFC7277] Bjorklund, M., "A YANG Data Model for IP Management", RFC 1658 7277, June 2014. 1660 [XML] Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and 1661 F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fifth 1662 Edition)", W3C Recommendation, November 2008, 1663 . 1665 7.2 Informative References 1667 [RFC7224] Bjorklund, M., "IANA Interface Type YANG Module", RFC 1668 7224, May 2014. 1670 [RFC4293] Routhier, S., "Management Information Base for the 1671 Protocol (IP)", RFC 4293, April 2006. 1673 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 1674 Shell (SSH)", RFC 6242, June 2011. 1676 Authors' Addresses 1678 Steve Baillargeon 1679 349 Terry Fox Drive 1680 Kanata, Ontario, K2K 2V6 1681 Canada 1683 EMail: steve.baillargeon@ericsson.com