1-- ***************************************************************** 2-- CISCO-WIRELESS-DOCS-EXT-MIB.my: 3-- Cisco Wireless DOCS extension MIB file 4-- 5-- January 2000, Saradha Srinivasan 6-- 7-- Copyright (c) 2000 by Cisco Systems, Inc. 8-- All rights reserved. 9-- ***************************************************************** 10 11CISCO-WIRELESS-DOCS-EXT-MIB DEFINITIONS ::= BEGIN 12 13IMPORTS 14 MODULE-IDENTITY, 15 OBJECT-TYPE, 16 NOTIFICATION-TYPE, 17 Integer32, 18 Counter32, 19 IpAddress 20 FROM SNMPv2-SMI 21 TruthValue, 22 DisplayString, 23 MacAddress, 24 TimeStamp, 25 RowStatus, 26 TimeInterval 27 FROM SNMPv2-TC 28 OBJECT-GROUP, 29 MODULE-COMPLIANCE 30 FROM SNMPv2-CONF 31 ifIndex 32 FROM IF-MIB 33 cwdIfHeServiceEntry, 34 cwdIfHeSuStatusEntry, 35 cwdIfHeSuStatusIndex, 36 cwdIfHeMacEntry, 37 cwdIfHeSuStatusMacAddress, 38 cwdIfHeSuStatusIpAddress, 39 cwdIfHeSuStatusDownChanIfIndex, 40 cwdIfHeSuStatusUpChanIfIndex, 41 cwdIfHeSuStatusServiceId, 42 cwdIfQosProfileEntry, 43 cwdIfQosProfIndex 44 FROM CISCO-WIRELESS-DOCS-IF-MIB 45 ciscoMgmt 46 FROM CISCO-SMI; 47 48ciscoWirelessDocsExtMIB MODULE-IDENTITY 49 LAST-UPDATED "200007171003Z" 50 ORGANIZATION "Cisco Systems, Inc." 51 CONTACT-INFO 52 "Cisco Systems 53 Customer Service 54 55 Postal: Cisco Systems 56 170 West Tasman Drive 57 San Jose, CA 95134 58 U.S.A. 59 Phone: +1 800 553-NETS 60 E-mail: wireless-nms@cisco.com" 61 DESCRIPTION 62 "This MIB module defines Cisco-specific objects that 63 add to the functionality defined in 64 CISCO-WIRELESS-DOCS-IF-MIB. 65 These objects configure the scheduler that supports 66 Quality of Service (QoS) of MCNS/DOCSIS compliant 67 Radio Frequency (RF) interfaces in Wireless 68 Headends (HE)." 69 REVISION "200007171003Z" 70 DESCRIPTION 71 "Initial version" 72 ::= { ciscoMgmt 169 } 73 74ciscoWirelessDocsExtMIBObjects OBJECT IDENTIFIER ::= 75 { ciscoWirelessDocsExtMIB 1 } 76 77cwdxQosCtrlObjects OBJECT IDENTIFIER ::= { ciscoWirelessDocsExtMIBObjects 1 } 78cwdxQosQueueObjects OBJECT IDENTIFIER ::= { ciscoWirelessDocsExtMIBObjects 2 } 79cwdxHeSuCpeObjects OBJECT IDENTIFIER ::= { ciscoWirelessDocsExtMIBObjects 3 } 80cwdxQosProfileExtObjects OBJECT IDENTIFIER ::= 81 { ciscoWirelessDocsExtMIBObjects 4 } 82 83 84-- 85-- Scheduler QoS Control Group 86-- 87-- This group contains objects that configure how the scheduler 88-- controls traffic. In addition, it contains objects to monitor 89-- the scheduler's admission and rate control. 90-- 91-- For each Service ID, there is one Quality of Service profile 92-- associated with it. The QoS profile limits the request (upstream)/ 93-- packet (downstream) size for the Service ID and also defines the 94-- minimum guaranteed upstream bandwidth. Each SU's request 95-- associated with a Service ID needs to follow the Quality of 96-- Service profile constraints. 97-- 98 99-- 100-- Quality of Service control upstream table 101-- 102-- Quality of Service control objects for the upstream interface 103-- 104-- This table contains objects to configure upstream admission control 105-- based on available upstream bandwidth. This table also contains 106-- objects that show the status of the scheduler. 107 108 109cwdxQosCtrlUpTable OBJECT-TYPE 110 SYNTAX SEQUENCE OF CwdxQosCtrlUpEntry 111 MAX-ACCESS not-accessible 112 STATUS current 113 DESCRIPTION 114 "For each upstream interface, this table maintains a number 115 of objects related to Quality of Service scheduler. 116 These objects are used to control SU registration." 117 ::= { cwdxQosCtrlObjects 1 } 118 119cwdxQosCtrlUpEntry OBJECT-TYPE 120 SYNTAX CwdxQosCtrlUpEntry 121 MAX-ACCESS not-accessible 122 STATUS current 123 DESCRIPTION 124 "A list of attributes for each upstream MAC scheduler 125 that supports Quality of Service. Entries in this table 126 exist for each ifEntry with ifType of 127 propDocsWirelessUpstream(nnn)." 128 REFERENCE 129 "Data-Over-Cable Service Interface Specifications (DOCSIS) 130 Radio Frequency Interface Specification (SP-RFI-I04-980724), 131 section 6.4 and appendix C. 132 133 cwdIfQosProfileTable and cwdIfHeServiceTable in 134 CISCO-WIRELESS-DOCS-IF-MIB.my." 135 INDEX { ifIndex } 136 ::= { cwdxQosCtrlUpTable 1 } 137 138CwdxQosCtrlUpEntry ::= SEQUENCE { 139 cwdxQosCtrlUpAdmissionCtrl TruthValue, 140 cwdxQosCtrlUpMaxRsvdBWPercent Integer32, 141 cwdxQosCtrlUpAdmissionRejects Counter32, 142 cwdxQosCtrlUpReservedBW Integer32, 143 cwdxQosCtrlUpMaxVirtualBW Integer32 144 } 145 146cwdxQosCtrlUpAdmissionCtrl OBJECT-TYPE 147 SYNTAX TruthValue 148 MAX-ACCESS read-write 149 STATUS current 150 DESCRIPTION 151 "The admission control status for this upstream entry. 152 153 When this object is set to 'true', the upstream scheduler 154 will check the virtual reserved bandwidth remaining 155 before giving admission to this new SU. If there 156 is not enough reserved bandwidth to serve the SU's minimum 157 guaranteed bandwidth, the registration request will be 158 rejected. 159 160 This object is set to 'false' to disable admission control. 161 That is, there will be no checking for bandwidth capacity and 162 the upstream interface scheduler just admits SU registration 163 requests." 164 ::= { cwdxQosCtrlUpEntry 1 } 165 166cwdxQosCtrlUpMaxRsvdBWPercent OBJECT-TYPE 167 SYNTAX Integer32 (10..1000) 168 UNITS "percent" 169 MAX-ACCESS read-write 170 STATUS current 171 DESCRIPTION 172 "The percentage of upstream maximum reserved bandwidth to the 173 raw bandwidth if the admission control is enabled on this 174 upstream. 175 176 For example, if the upstream interface has raw bandwidth 177 1,600,000 bits/second and cwdxQosCtrlUpMaxRsvdBWPercent is 200 178 percent, then this upstream scheduler will set the maximum of 179 virtual reserved bandwidth capacity to 3,200,000 bits/second 180 (1,600,000 * 2) to serve Subscriber-units with minimum guaranteed 181 upstream bandwidth. 182 183 The default value is 100 percent (that is, maximum reserved 184 bandwidth is the raw bandwidth.) Whenever the admission control 185 is changed (on to off, off to on), this value will be reset to 186 the default value 100. 187 188 If the admission control is disabled, the value will be reset 189 to 100 (the default value)." 190 REFERENCE 191 "Data-Over-Cable Service Interface Specifications (DOCSIS) 192 Radio Frequency Interface Specification 193 (SP-RFI-I04-980724). section 6.4 and appendix C." 194 ::= { cwdxQosCtrlUpEntry 2 } 195 196cwdxQosCtrlUpAdmissionRejects OBJECT-TYPE 197 SYNTAX Counter32 198 MAX-ACCESS read-only 199 STATUS current 200 DESCRIPTION 201 "The count of SU registration requests rejected on this 202 upstream interface. The rejection is due to insufficient 203 available bandwidth for this SU. The requests are rejected 204 only when cwdxQosCtrlUpAdmissionCtrl is 'true' on this 205 upstream interface." 206 ::= { cwdxQosCtrlUpEntry 3 } 207 208cwdxQosCtrlUpReservedBW OBJECT-TYPE 209 SYNTAX Integer32 (0..102400000) 210 UNITS "bits/second" 211 MAX-ACCESS read-only 212 STATUS current 213 DESCRIPTION 214 "The current total reserved bandwidth in bits per second of this 215 upstream interface. It is the sum of all SUs' minimum 216 guaranteed bandwidth in bits per second currently supported 217 on this upstream." 218 ::= { cwdxQosCtrlUpEntry 4 } 219 220cwdxQosCtrlUpMaxVirtualBW OBJECT-TYPE 221 SYNTAX Integer32 (0..102400000) 222 UNITS "bits/second" 223 MAX-ACCESS read-only 224 STATUS current 225 DESCRIPTION 226 "The maximum virtual bandwidth capacity of this upstream interface 227 if the admission control is enabled. It is the raw bandwidth 228 in bits per second times the percentage. If the admission 229 control is disabled, then this object will contain the value 230 zero." 231 ::= { cwdxQosCtrlUpEntry 5 } 232 233-- 234-- Rate Limiting table 235-- 236-- After a SU is registered, upstream and downstream schedulers 237-- will control the bandwidth request/packet size to ensure the Quality of 238-- Service and fairness by a rate limiting algorithm. This table 239-- contains attributes related to the rate limiting algorithms. 240-- 241 242cwdxQosIfRateLimitTable OBJECT-TYPE 243 SYNTAX SEQUENCE OF CwdxQosIfRateLimitEntry 244 MAX-ACCESS not-accessible 245 STATUS current 246 DESCRIPTION 247 "This table describes the attributes of rate limiting for 248 schedulers in upstream and downstream interfaces that 249 support Quality of Service. The rate limiting process is 250 to ensure the Quality of Service and fairness." 251 ::= { cwdxQosCtrlObjects 2 } 252 253cwdxQosIfRateLimitEntry OBJECT-TYPE 254 SYNTAX CwdxQosIfRateLimitEntry 255 MAX-ACCESS not-accessible 256 STATUS current 257 DESCRIPTION 258 "List of the rate limiting attributes for upstream and 259 downstream interfaces schedulers that support Quality of 260 Service. Entries in this table exist for each ifEntry with 261 ifType of propDocsWirelessUpstream(nnn) and 262 propDocsWirelessDownstream(nnn)." 263 REFERENCE 264 "Data-Over-Cable Service Interface Specifications (DOCSIS) 265 Radio Frequency Interface Specification (SP-RFI-I04-980724), 266 section 6.4 and appendix C. 267 268 cwdIfQosProfileTable and cwdIfHeServiceTable in 269 CISCO-DOCS-WIRELESS-IF-MIB.my." 270 INDEX { ifIndex } 271 ::= { cwdxQosIfRateLimitTable 1 } 272 273CwdxQosIfRateLimitEntry ::= SEQUENCE { 274 cwdxQosIfRateLimitAlgo INTEGER, 275 cwdxQosIfRateLimitExpWgt Integer32, 276 cwdxQosIfRateLimitShpMaxDelay INTEGER, 277 cwdxQosIfRateLimitShpGranularity INTEGER 278 } 279 280cwdxQosIfRateLimitAlgo OBJECT-TYPE 281 SYNTAX INTEGER { 282 noRateLimit(1), -- rate limiting process is disabled 283 oneSecBurst(2), -- Bursty 1 second token bucket algorithm 284 carLike(3), -- Average token usage algorithm (CAR-like) 285 wgtExPacketDiscard(4), -- Weighted excess packet discard 286 -- algorithm 287 shaping(5) -- token bucket algorithm with shaping 288 } 289 MAX-ACCESS read-write 290 STATUS current 291 DESCRIPTION 292 "To ensure fairness, at the upstream, the HE will throttle 293 the rate of bandwidth grants, such that the flow never 294 gets more than its provisioned peak rate in bps. 295 Similarly at the downstream, HE controls the packets 296 sent such that flow never gets more than its provisioned 297 peak rate in bps. 298 299 There are two directions for every Service Id (Sid) traffic: 300 downstream and upstream. Each direction is called a service 301 flow here and is assigned one token bucket with chosen 302 algorithm. 303 304 The enumerations for the rate limiting algorithm are: 305 noRateLimit(1): The rate limiting is disabled. No rate 306 limiting. 307 oneSecBurst(2): Bursty 1 second token bucket algorithm. 308 carLike(3) : Average token usage (CAR-like) algorithm 309 wgtExPacketDiscard(4) : Weighted excess packet discard 310 algorithm. 311 shaping(5): token bucket algorithm with shaping 312 313 Upstream supports all the above except 314 wgtExtPacketDiscard(4). 315 316 Downstream supports all the above rate-limiting algorithms. 317 318 Token bucket algorithm with shaping is the 319 default algorithm for upstream. 320 321 Bursty 1 second token bucket algorithm is the 322 default algorithm for downstream. 323 324 Each algorithm is described as below: 325 No rate limiting: 326 The rate limiting process is disabled and no checking 327 against the maximum bandwidth allowed. 328 329 Bursty 1 second token bucket rate limiting algorithm: 330 In this algorithm, at the start of every 1 second interval, 331 a service flow's token usage is reset to 0, and every time 332 the modem for that service flow sends a request (upstream) / 333 packet (downstream) the upstream/downstream bandwidth 334 token usage is incremented by the size of the 335 request/packet sent. As long as the service flow's bandwidth 336 token usage is less than the maximum bandwidth in bits 337 per second (peak rate limit) its QoS service class 338 allows, the request/packets will not be restricted. 339 Once the service flow has sent more than its peak rate in the 340 one second interval, it is prevented from sending more 341 data by rejecting request (upstream) or dropping 342 packets (downstream). This is expected to slow down 343 the higher layer sources. The token usage counter gets 344 reset to 0 after the 1 second interval has elapsed. The 345 modem for that service flow is free to send more data up to the 346 peak rate limit in the new 1 second interval that follows. 347 348 Average token usage (Cisco CAR like) algorithm: 349 This algorithm maintains a continuous average of the 350 burst token usage of a service flow. There is no sudden 351 refilling of tokens every 1 second interval. Every time a 352 request/packet is to be handled, the scheduler tries to see 353 how much time has elapsed since last transmission, and 354 computes the number of tokens accumulated by this service flow 355 at its QoS class peak rate. If burst usage of the service flow 356 is less than tokens accumulated, the burst usage is reset to 0 357 and request/packet is forwarded. If the service flow has 358 accumulated fewer tokens than its burst usage, the burst usage 359 shows an outstanding balance usage after decrementing by the 360 tokens accumulated. In such cases, the request/packet is still 361 forwarded, provided the service flow's outstanding usage does 362 not exceed peak rate limit of its QoS class. If outstanding 363 burst usage exceeds the peak rate of the class, the service 364 flow is given some token credit up to a certain maximum credit 365 limit and the request/packet is forwarded. The request/packet 366 is dropped when outstanding usage exceeds peak rate and maximum 367 credit has been used up by this service flow. This algorithm 368 tracks long term average bandwidth usage of the service flow 369 and controls this average usage at the peak rate limit. 370 371 Weighted excess packet discard algorithm: 372 This rate limiting algorithm is only available as an option 373 for downstream rate limiting. The algorithm is to maintain an 374 weighted exponential moving average of the loss rate of a 375 service flow over time. The loss rate, expressed in packets, 376 represents the number of packets that can be sent from this 377 service flow in a one second interval before a packet will 378 be dropped. At every one second interval, the loss rate gets 379 updated using the ratio between the flow peak rate (in bps) 380 in its QoS profile and the service flow actual usage (in bps). 381 If the service flow begins to send more than its peak rate 382 continuously, the number of packets it can send in an one 383 second interval before experiencing a drop will slowly keep 384 reducing until SU for that service flow slows down 385 as indicated by actual usage less or equal to the peak rate. 386 387 Token bucket algorithm with shaping: 388 If there is no QoS class peak rate limit, forward the 389 request/packet without delay. If there is a QoS peak rate 390 limit, every time a request/packet is to be handled, the 391 scheduler determines the number of bandwidth tokens that this 392 service flow has accumulated over the elapsed time at its 393 QoS class peak rate and increments the tokens counter of the 394 service flow accordingly. The scheduler limits the token 395 count to the maximum transmit burst (token bucket depth). 396 If token count is greater than the number of tokens required 397 to handle current request/packet, decrement token count by 398 size of request/packet and forwards the request/packet 399 without delay. If token count is less than the size of 400 request/packet, compute the shaping delay time after 401 which the deficit number of tokens would be available. If 402 shaping delay time is less than the maximum shaping delay, 403 decrement tokens count by size of request/packet and 404 forward this request/packet with the shaping delay in the 405 shaping delay queue. When the delay time expires, the 406 request/packet is forwarded. If shaping delay time is 407 greater than the maximum shaping delay that the subsequent 408 shaper can handle, the request/packet is dropped. Users can 409 use cwdxQosIfRateLimitShpMaxDelay to configure the maximum 410 shaping delay and cwdxQosIfRateLimitShpGranularity to 411 configure the shaping granularity." 412 ::= { cwdxQosIfRateLimitEntry 1 } 413 414cwdxQosIfRateLimitExpWgt OBJECT-TYPE 415 SYNTAX Integer32 (1..4) 416 MAX-ACCESS read-write 417 STATUS current 418 DESCRIPTION 419 "Weight for exponential moving average of loss rate, 420 when using weighted excess packet discard algorithm. 421 The higher values of the weight make the algorithm 422 more sensitive to the recent bandwidth usage by the Sid. 423 424 The default value is 1. Whenever the rate limiting 425 algorithm is changed to weighted excess packet discard 426 algorithm, this value will be reset to the default 1. 427 428 If the rate limiting algorithm is not weighted excess 429 packet discard algorithm, the value will be always the 430 default value 1. You will not be able to set it to 431 anything other than 1 when it is not weighted excess 432 packet discard algorithm." 433 ::= { cwdxQosIfRateLimitEntry 2 } 434 435cwdxQosIfRateLimitShpMaxDelay OBJECT-TYPE 436 SYNTAX INTEGER { 437 na(1), 438 msec128(2), 439 msec256(3), 440 msec512(4), 441 msec1024(5) 442 } 443 MAX-ACCESS read-write 444 STATUS current 445 DESCRIPTION 446 "The maximum shaping delay in milliseconds. That is, the maximum 447 amount of time for which the HE will allow buffering of any 448 rate exceeded flow. If the max buffering delay is large, 449 then grants/packets of the flow will be buffered for a 450 longer period of time even though the flow is rate exceeded. 451 This means fewer chances of drops for such rate exceeded 452 flow. However, too large a max shaping delay can result in 453 quick drainage of packet buffers at the HE, since several 454 packets will be in the shaping (delay) queue waiting for 455 their proper transmission time. Another important point to 456 note is that delaying a flow's packets (especially TCP 457 flows) for extended periods of time may be counter- 458 productive, since the higher protocol layers may assume 459 a packet loss after a certain amount of time. 460 461 The maximum shaping delay is only applied to rate limit 462 algorithm: Token bucket algorithm with shaping. If the rate 463 limit algorithm is not Token bucket algorithm with shaping, 464 the value is always na(1) which is not applicable. In this 465 case, you will be allowed to set the value to na(1) only. 466 467 If the token count is less than the size of request/packet, HE 468 computes the shaping delay time after which the deficit number of 469 tokens would be available. If the shaping delay time is greater 470 than the maximum shaping delay, the request/packet will be 471 dropped. 472 473 The enumerations for cwdxQosIfRateLimitShpMaxDelay are: 474 na(1): maximum shaping delay is not applied to the current 475 rate limit algorithm 476 msec128(2): maximum shaping delay is 128 milliseconds 477 msec256(3): maximum shaping delay is 256 milliseconds 478 msec512(4): maximum shaping delay is 512 milliseconds 479 msec1024(5): maximum shaping delay is 1024 milliseconds 480 481 At the downstream, cwdxQosIfRateLimitShpMaxDelay 482 is configurable and the default value is msec128(2). 483 Whenever the downstream rate limit algorithm is changed 484 to Token bucket algorithm with shaping from other rate 485 limit algorithm, the value will be reset to the default 486 value. 487 488 At the upstream, cwdxQosIfRateLimitShpMaxDelay is not 489 configurable and it is read-only value." 490 ::= { cwdxQosIfRateLimitEntry 3 } 491 492cwdxQosIfRateLimitShpGranularity OBJECT-TYPE 493 SYNTAX INTEGER { 494 na(1), 495 msec1(2), 496 msec2(3), 497 msec4(4), 498 msec8(5), 499 msec16(6) 500 } 501 MAX-ACCESS read-write 502 STATUS current 503 DESCRIPTION 504 "The width in milliseconds of each element in shaping 505 delay queue, that is, the shaping granularity. 506 507 The shaping granularity is only applied to rate limit 508 algorithm: Token bucket algorithm with shaping. It 509 controls how accurately the algorithm quantizes the shaping 510 delay for a rate exceeded flow. If granularity is large, several 511 shaping delay values will all be quantized to the same element 512 in the queue resulting in less accurate rate shaping for the flows 513 in bits/sec. On the other hand, choosing too small granularity 514 causes more memory to be used for the shaper block, and also 515 can cost a bit more in runtime overhead. 516 517 If the rate limit algorithm is not Token bucket algorithm with 518 shaping, the value is always na(1) which is not applicable. 519 Setting to any thing other than na(1) will be rejected. 520 521 The enumerations for shaping granularity are: 522 na(1): shaping granularity is not applied to the current 523 rate limit algorithm 524 msec1(2): shaping granularity in 1 milliseconds 525 msec2(3): shaping granularity in 2 milliseconds 526 msec4(4): shaping granularity in 4 milliseconds 527 msec8(5): shaping granularity in 8 milliseconds 528 msec16(6): shaping granularity in 16 milliseconds 529 530 At the downstream, this object is configurable and the 531 default value is msec4(4). Whenever the downstream rate limit 532 algorithm is changed to Token bucket algorithm with shaping 533 from other rate limit algorithm, the value will be reset to the 534 default value. When the algorithm is Token bucket algorithm 535 with shaping and set to same algorithm again the value will 536 not be reset to default value. 537 538 At the upstream, this object is not configurable and 539 it is read-only value." 540 ::= { cwdxQosIfRateLimitEntry 4 } 541 542-- 543-- He Service Extension Table 544-- 545-- This table extends the information about a Service ID in 546-- cwdIfHeServiceTable. 547-- 548-- For each Service ID, there is one Quality of Service profile 549-- associated with it and the profile limitsthe request/packet size 550-- ratio for the Service ID. This table shows downstream traffic 551-- statistics. It also counts requests and packets that exceeded 552-- the limits set in the QOS profile for each SID. 553-- 554 555cwdxHeServiceExtTable OBJECT-TYPE 556 SYNTAX SEQUENCE OF CwdxHeServiceExtEntry 557 MAX-ACCESS not-accessible 558 STATUS current 559 DESCRIPTION 560 "The list contains the additional attributes of a single Service 561 ID that provided by cwdIfHeServiceEntry." 562 ::= { cwdxQosCtrlObjects 3 } 563 564cwdxHeServiceExtEntry OBJECT-TYPE 565 SYNTAX CwdxHeServiceExtEntry 566 MAX-ACCESS not-accessible 567 STATUS current 568 DESCRIPTION 569 "Additional objects for cwdIfHeServiceTable entry including 570 downstream traffic statistics and excess counts against the 571 Quality of Service limits for each Service ID." 572 REFERENCE 573 "Data-Over-Cable Service Interface Specifications (DOCSIS) 574 Radio Frequency Interface Specification (SP-RFI-I04-980724), 575 section 6.4 and appendix C. 576 577 cwdIfQosProfileTable and cwdIfHeServiceTable in 578 CISCO-WIRELESS-DOCS-IF-MIB.my." 579 AUGMENTS { cwdIfHeServiceEntry } 580 ::= { cwdxHeServiceExtTable 1 } 581 582CwdxHeServiceExtEntry ::= SEQUENCE { 583 cwdxIfHeServiceOutOctets Counter32, 584 cwdxIfHeServiceOutPackets Counter32, 585 cwdxQosMaxUpBWExcessRequests Counter32, 586 cwdxQosMaxDownBWExcessPackets Counter32 587 } 588 589cwdxIfHeServiceOutOctets OBJECT-TYPE 590 SYNTAX Counter32 591 MAX-ACCESS read-only 592 STATUS current 593 DESCRIPTION 594 "The cumulative number of Packet Data octets sent for this 595 Service ID." 596 ::= { cwdxHeServiceExtEntry 1 } 597 598cwdxIfHeServiceOutPackets OBJECT-TYPE 599 SYNTAX Counter32 600 MAX-ACCESS read-only 601 STATUS current 602 DESCRIPTION 603 "The cumulative number of Packet data packets sent for this 604 Service ID." 605 ::= { cwdxHeServiceExtEntry 2 } 606 607 608cwdxQosMaxUpBWExcessRequests OBJECT-TYPE 609 SYNTAX Counter32 610 MAX-ACCESS read-only 611 STATUS current 612 DESCRIPTION 613 "The number of upstream bandwidth requests which exceeds the 614 maximum upstream bandwidth allowed for a service defined 615 in the Quality of Service profile associated with this Sid. 616 The request which exceeds the maximum upstream bandwidth 617 allowed will be rejected by the upstream's rate limiting 618 process using one of the rate limiting algorithm. 619 620 Note that the value of this counter cannot be directly used 621 to know the number of upstream packets that got dropped at 622 the SU. A single upstream packet drop of a SU 623 can result in up to 16 increments in this counter, since the 624 SU keeps retrying and keeps getting bandwidth request 625 drops at HE if it has consumed its peak rate." 626 REFERENCE 627 "cwdIfQosProfMaxUpBandwidth object in 628 CISCO-WIRELESS-DOCS-IF-MIB.my." 629 ::= { cwdxHeServiceExtEntry 3 } 630 631cwdxQosMaxDownBWExcessPackets OBJECT-TYPE 632 SYNTAX Counter32 633 MAX-ACCESS read-only 634 STATUS current 635 DESCRIPTION 636 "The number of downstream bandwidth packets which exceeds the 637 maximum downstream bandwidth allowed for a service defined 638 in the Quality of Service profile associated with this Sid. 639 The packet which exceeds the maximum downstream bandwidth 640 allowed will be dropped by the downstream's rate limiting 641 process using one of the rate limiting algorithm." 642 REFERENCE 643 "cwdIfQosProfMaxDownBandwidth object in 644 CISCO-WIRELESS-DOCS-IF-MIB.my." 645 ::= { cwdxHeServiceExtEntry 4 } 646 647 648-- 649-- Scheduler QoS Queue Group 650-- 651-- To ensure Quality of Service and fairness, the scheduler 652-- maintains a set of queues for different services and puts 653-- SU requests/packets for that Sid in a different 654-- queue according to the Quality of Service profile of the 655-- Sid. Each queue has a name and order within the queue set. 656-- The scheduler will serve the requests/packets in higher 657-- order queue before serving the requests/packets in lower 658-- order queue. 659-- 660 661-- 662-- Scheduler bandwidth request queues table 663-- 664-- This table displays the attributes for these queues in a 665-- interface scheduler that supports Quality of Service. 666-- 667 668cwdxBWQueueTable OBJECT-TYPE 669 SYNTAX SEQUENCE OF CwdxBWQueueEntry 670 MAX-ACCESS not-accessible 671 STATUS current 672 DESCRIPTION 673 "This table describes the attributes of queues 674 in wireless interfaces schedulers that support 675 Quality of Service." 676 ::= { cwdxQosQueueObjects 1 } 677 678cwdxBWQueueEntry OBJECT-TYPE 679 SYNTAX CwdxBWQueueEntry 680 MAX-ACCESS not-accessible 681 STATUS current 682 DESCRIPTION 683 "The list of queue attributes in upstream and downstream 684 interfaces schedulers that supports Quality of Service. 685 Entries in this table exist for each ifEntry with ifType of 686 propDocsWirelessUpstream(nnn) and 687 propDocsWirelessDownstream(nnn)." 688 REFERENCE 689 "Data-Over-Cable Service Interface Specifications (DOCSIS) 690 Radio Frequency Interface Specification (SP-RFI-I04-980724), 691 section 6.4 and appendix C." 692 INDEX { ifIndex,cwdxBWQueueNameCode } 693 ::= { cwdxBWQueueTable 1 } 694 695CwdxBWQueueEntry ::= SEQUENCE { 696 cwdxBWQueueNameCode INTEGER, 697 cwdxBWQueueOrder Integer32, 698 cwdxBWQueueNumServedBeforeYield Integer32, 699 cwdxBWQueueType INTEGER, 700 cwdxBWQueueMaxDepth Integer32, 701 cwdxBWQueueDepth Integer32, 702 cwdxBWQueueDiscards Counter32 703 } 704 705cwdxBWQueueNameCode OBJECT-TYPE 706 SYNTAX INTEGER { 707 cirQ(1), -- Committed Information Rate queue 708 tbeQ(2) -- TIERED BEST EFFORT queue 709 } 710 MAX-ACCESS not-accessible 711 STATUS current 712 DESCRIPTION 713 "The name code for the queue. 714 cirQ: CIR queue. The queue is for Committed Information Rate 715 (CIR) type of service which serves Service IDs which have 716 minimum guaranteed rate in its QoS profile. 717 tbeQ: TBE queue. The queue is for TIERED BEST EFFORT type 718 service which serves Service IDs which does not have 719 minimum guaranteed rate in its QoS profile." 720 REFERENCE 721 "Data-Over-Cable Service Interface Specifications (DOCSIS) 722 Radio Frequency Interface Specification (SP-RFI-I04-980724), 723 section 6.4 and appendix C." 724 ::= { cwdxBWQueueEntry 1 } 725 726cwdxBWQueueOrder OBJECT-TYPE 727 SYNTAX Integer32 (0..10) 728 MAX-ACCESS read-only 729 STATUS current 730 DESCRIPTION 731 "The relative order of this queue to the other queues within the 732 wireless interface. The smaller number has higher order. That is, 733 0 is the highest order and 10 is the lowest order. The 734 scheduler will serve the requests in higher order queue up to 735 the number of requests defined in cwdxBWQueueNumServedBeforeYield 736 before serving requests in the next higher order queue. 737 The queues with higher priority will not be serviced 738 (once the QueueNumServedBeforeYield number has been hit) 739 until all remaining queues are processed. 740 741 If there are n queues on this interface, the queue order will 742 be 0 to n-1 and maximum number of requests defined as 743 cwdxBWQueueNumServedBeforeYield in order 0 queue will be served 744 before the requests in order 1 queue to be served." 745 ::= { cwdxBWQueueEntry 2 } 746 747cwdxBWQueueNumServedBeforeYield OBJECT-TYPE 748 SYNTAX Integer32 (0..50) 749 MAX-ACCESS read-only 750 STATUS current 751 DESCRIPTION 752 "The maximum number of requests/packets the scheduler can serve 753 before yielding to another queue. The value 0 means all requests 754 must be served before yielding to another queue." 755 ::= { cwdxBWQueueEntry 3 } 756 757 758cwdxBWQueueType OBJECT-TYPE 759 SYNTAX INTEGER { 760 unknown(1), 761 other(2), 762 fifo(3), 763 priority(4) 764 } 765 MAX-ACCESS read-only 766 STATUS current 767 DESCRIPTION 768 "The queuing type which decides the position of a request/packet 769 within the queue. 770 unknown : queue type unknown. 771 other : not fifo, and not priority. 772 fifo : first in first out. 773 priority: each bandwidth request has a priority and the 774 position of the request within the queue depends 775 on its priority." 776 ::= { cwdxBWQueueEntry 4 } 777 778 779cwdxBWQueueMaxDepth OBJECT-TYPE 780 SYNTAX Integer32 781 MAX-ACCESS read-only 782 STATUS current 783 DESCRIPTION 784 "The maximum number of requests/packets which the queue can 785 support." 786 ::= { cwdxBWQueueEntry 5 } 787 788 789cwdxBWQueueDepth OBJECT-TYPE 790 SYNTAX Integer32 791 MAX-ACCESS read-only 792 STATUS current 793 DESCRIPTION 794 "The current number of requests/packets in the queue." 795 ::= { cwdxBWQueueEntry 6 } 796 797 798cwdxBWQueueDiscards OBJECT-TYPE 799 SYNTAX Counter32 800 MAX-ACCESS read-only 801 STATUS current 802 DESCRIPTION 803 "The number of requests/packets discarded because of queue 804 overflow (queue depth > queue maximum depth)." 805 ::= { cwdxBWQueueEntry 7 } 806 807 808-- 809-- HE Customer Premises Equipments (CPE) Group 810-- 811-- This group contains tables in HE for information about 812-- Customer Premises Equipment (CPE) that connect to SUs. 813-- 814 815-- 816-- Customer Premises Equipments (CPE) Table 817-- 818-- For the information of CPE maintained in HE. 819-- 820 821cwdxCpeTable OBJECT-TYPE 822 SYNTAX SEQUENCE OF CwdxCpeEntry 823 MAX-ACCESS not-accessible 824 STATUS current 825 DESCRIPTION 826 "This table contains information about 827 Customer Premises Equipments (CPE)." 828 ::= { cwdxHeSuCpeObjects 1 } 829 830cwdxCpeEntry OBJECT-TYPE 831 SYNTAX CwdxCpeEntry 832 MAX-ACCESS not-accessible 833 STATUS current 834 DESCRIPTION 835 "The list contains information for a Customer Premises 836 Equipment (CPE) connected to SUs. An entry exists for 837 each Customer Premises Equipment connected to a 838 subscriber-unit supported by HE." 839 REFERENCE 840 "Data-Over-Cable Service Interface Specifications (DOCSIS) 841 Radio Frequency Interface Specification (SP-RFI-I04-980724.) 842 cwdIfHeSuStatusTable, cwdIfHeServiceTable in 843 CISCO-DOCS-WIRELESS-IF-MIB.my." 844 INDEX { cwdxCpeStatusIndex, cwdxCpeMacAddress } 845 ::= { cwdxCpeTable 1 } 846 847CwdxCpeEntry ::= SEQUENCE { 848 cwdxCpeStatusIndex INTEGER, 849 cwdxCpeMacAddress MacAddress, 850 cwdxCpeIpAddress IpAddress, 851 cwdxCpeAccessGroup DisplayString 852 } 853 854cwdxCpeStatusIndex OBJECT-TYPE 855 SYNTAX INTEGER(1..2147483647) 856 MAX-ACCESS not-accessible 857 STATUS current 858 DESCRIPTION 859 "Index to an entry in cwdIfHeSuStatusTable identifying 860 status of the SU (which the CPE connects to.)" 861 ::= { cwdxCpeEntry 1 } 862 863cwdxCpeMacAddress OBJECT-TYPE 864 SYNTAX MacAddress 865 MAX-ACCESS not-accessible 866 STATUS current 867 DESCRIPTION 868 "The Mac address to identify a Customer Premises Equipment." 869 ::= { cwdxCpeEntry 2 } 870 871cwdxCpeIpAddress OBJECT-TYPE 872 SYNTAX IpAddress 873 MAX-ACCESS read-only 874 STATUS current 875 DESCRIPTION 876 "Ip address of the Customer Premises Equipment." 877 ::= { cwdxCpeEntry 3 } 878 879 880cwdxCpeAccessGroup OBJECT-TYPE 881 SYNTAX DisplayString 882 MAX-ACCESS read-write 883 STATUS current 884 DESCRIPTION 885 "ASCII text to identify the Access Group for a CPE. 886 Access Group is to filter the upstream traffic for that 887 CPE." 888 ::= { cwdxCpeEntry 4 } 889 890-- 891cwdxSuMappingTable OBJECT-TYPE 892 SYNTAX SEQUENCE OF CwdxSuMappingEntry 893 MAX-ACCESS not-accessible 894 STATUS current 895 DESCRIPTION 896 "This table contains a mapping between the SU Mac Address 897 and the cwdIfHeSuStatusIndex which identifies a row 898 in cwdIfHeSuStatusTable which lists the attributes of 899 an SU." 900 ::= { cwdxHeSuCpeObjects 2 } 901 902cwdxSuMappingEntry OBJECT-TYPE 903 SYNTAX CwdxSuMappingEntry 904 MAX-ACCESS not-accessible 905 STATUS current 906 DESCRIPTION 907 "There exists an entry in this table for every SU 908 connected to the HE. Each entry contains a mapping 909 from the SU's mac address to the cwdIfHeSuStatusIndex." 910 REFERENCE 911 "Data-Over-Cable Service Interface Specifications (DOCSIS) 912 Radio Frequency Interface Specification (SP-RFI-I04-980724.) 913 cwdIfHeSuStatusTable, cwdIfHeServiceTable in 914 CISCO-DOCS-WIRELESS-IF-MIB.my." 915 INDEX { cwdxSuMappingMacAddress } 916 ::= { cwdxSuMappingTable 1 } 917 918CwdxSuMappingEntry ::= SEQUENCE { 919 cwdxSuMappingMacAddress MacAddress, 920 cwdxSuMappingStatusIndex INTEGER 921 } 922 923cwdxSuMappingMacAddress OBJECT-TYPE 924 SYNTAX MacAddress 925 MAX-ACCESS not-accessible 926 STATUS current 927 DESCRIPTION 928 "The Mac address to identify a Subscriber-unit." 929 ::= { cwdxSuMappingEntry 2 } 930 931cwdxSuMappingStatusIndex OBJECT-TYPE 932 SYNTAX INTEGER(1..2147483647) 933 MAX-ACCESS read-only 934 STATUS current 935 DESCRIPTION 936 "Index to an entry in cwdIfHeSuStatusTable identifying 937 status of the SU." 938 ::= { cwdxSuMappingEntry 1 } 939 940 941-- HE SU status extension table 942-- 943-- This table extends the SU status information in cwdIfHeSuStatusTable 944-- 945 946cwdxHeSuStatusExtTable OBJECT-TYPE 947 SYNTAX SEQUENCE OF CwdxHeSuStatusExtEntry 948 MAX-ACCESS not-accessible 949 STATUS current 950 DESCRIPTION 951 "The list contains the additional SU status information." 952 ::= { cwdxHeSuCpeObjects 3 } 953 954cwdxHeSuStatusExtEntry OBJECT-TYPE 955 SYNTAX CwdxHeSuStatusExtEntry 956 MAX-ACCESS not-accessible 957 STATUS current 958 DESCRIPTION 959 "Additional objects for cwdIfHeSuStatusTable entry." 960 REFERENCE 961 "Data-Over-Cable Service Interface Specifications (DOCSIS) 962 Radio Frequency Interface Specification (SP-RFI-I04-980724.) 963 cwdIfHeSuStatusTable in DOCS-IF-MIB.my." 964 AUGMENTS { cwdIfHeSuStatusEntry } 965 ::= { cwdxHeSuStatusExtTable 1 } 966 967CwdxHeSuStatusExtEntry ::= SEQUENCE { 968 cwdxHeSuStatusValue INTEGER, 969 cwdxIfHeSuStatusOnlineTimes Counter32, 970 cwdxIfHeSuStatusPercentOnline Integer32, 971 cwdxIfHeSuStatusMinOnlineTime TimeInterval, 972 cwdxIfHeSuStatusAvgOnlineTime TimeInterval, 973 cwdxIfHeSuStatusMaxOnlineTime TimeInterval, 974 cwdxIfHeSuStatusMinOfflineTime TimeInterval, 975 cwdxIfHeSuStatusAvgOfflineTime TimeInterval, 976 cwdxIfHeSuStatusMaxOfflineTime TimeInterval, 977 cwdxIfHeSuStatusDynSidCount INTEGER 978 } 979 980cwdxHeSuStatusValue OBJECT-TYPE 981 SYNTAX INTEGER { 982 offline(1), 983 others(2), 984 initRangingRcvd(3), 985 initDhcpReqRcvd(4), 986 onlineNetAccessDisabled(5), 987 onlineKekAssigned(6), 988 onlineTekAssigned(7), 989 rejectBadMic(8), 990 rejectBadCos(9), 991 kekRejected(10), 992 tekRejected(11), 993 online(12), 994 initTftpPacketRcvd(13), 995 initTodRequestRcvd(14) 996 } 997 MAX-ACCESS read-only 998 STATUS current 999 DESCRIPTION 1000 "Current Subscriber-unit connectivity state. The object extends 1001 states in cwdIfHeSuStatusValue in more detail. 1002 1003 The enumerations are: 1004 offline(1) : SU considered offline. 1005 others(2) : states is in cwdIfHeSuStatusValue. 1006 initRangingRcvd(3) : SU sent initial ranging. 1007 initDhcpReqRcvd(4) : dhcp request received. 1008 onlineNetAccessDisabled(5): SU registered, but network 1009 access for the SU is disabled. 1010 onlineKekAssigned(6) : SU registered, BPI enabled and KEK 1011 assigned. 1012 onlineTekAssigned(7) : SU registered, BPI enabled and TEK 1013 assigned. 1014 rejectBadMic(8) : SU did attempt to register but 1015 registration was refused due to bad mic. 1016 rejectBadCos(9) : SU did attempt to register but 1017 registration was refused due to bad COS. 1018 kekRejected(10) : KEK SU key assignment rejected. 1019 tekRejected(11) : TEK SU key assignment rejected. 1020 online(12) : SU registered, enabled for data. 1021 initTftpPacketRcvd(13): tftp packet received and option file 1022 transfer started. 1023 initTodRquestRcvd(14): Time of the Day (TOD) request received. 1024 1025 The ranging, rangingAborted, rangingComplete, and ipComplete 1026 states in cwdIfHeSuStatusValue are all represented 1027 by the 'others' value in this object. 1028 1029 The registrationComplete state in cwdIfHeSuStatusValue 1030 could be online, onlineNetAccessDisabled, onlineKekAssigned, or 1031 onlineTekAssigned in this object. 1032 1033 The accessDenied state in cwdIfHeSuStatusValue could be 1034 rejectBadMic, rejectBadCos in this object for the possible 1035 reasons of Subscriber-unit registration abort. 1036 1037 The HE only reports states it is able to detect." 1038 ::= { cwdxHeSuStatusExtEntry 1 } 1039 1040cwdxIfHeSuStatusOnlineTimes OBJECT-TYPE 1041 SYNTAX Counter32 1042 MAX-ACCESS read-only 1043 STATUS current 1044 DESCRIPTION 1045 "The number of times that the SU changes the connectivity 1046 state from 'offline' to 'online' over the time period from 1047 the SU's first ranging message received by HE until now. 1048 1049 The SU is considered as 'online' when the value for 1050 cwdxHeSuStatusValue is any of the values: online(5), 1051 onlineNetAccessDisabled(6), onlineKekAssigned(7), and 1052 onlineTekAssigned(8), and the SU is considered as 'offline' 1053 for other values for cwdxHeSuStatusValue." 1054 REFERENCE 1055 "cwdxHeSuStatusValue object." 1056 ::= { cwdxHeSuStatusExtEntry 2 } 1057 1058cwdxIfHeSuStatusPercentOnline OBJECT-TYPE 1059 SYNTAX Integer32 (0..10000) 1060 MAX-ACCESS read-only 1061 STATUS current 1062 DESCRIPTION 1063 "The percentage of time that the SU stays 'online' over 1064 the time period from the SU's first ranging message 1065 received by HE until now. 1066 1067 The value for this object is 100 times bigger than the real 1068 percentage value. For example, 32.15% will be value 3215. 1069 1070 The SU is considered as 'online' when the value for 1071 cwdxHeSuStatusValue is any of the values: online(5), 1072 onlineNetAccessDisabled(6), onlineKekAssigned(7), and 1073 onlineTekAssigned(8), and the SU is considered as 1074 'offline' for other values for cwdxHeSuStatusValue." 1075 REFERENCE 1076 "cwdxHeSuStatusValue object." 1077 ::= { cwdxHeSuStatusExtEntry 3 } 1078 1079cwdxIfHeSuStatusMinOnlineTime OBJECT-TYPE 1080 SYNTAX TimeInterval 1081 MAX-ACCESS read-only 1082 STATUS current 1083 DESCRIPTION 1084 "The minimum period of time the SU stayed 'online' over 1085 the time period from the SU's first ranging message 1086 received by HE until now. 1087 1088 The SU is considered as 'online' when the value for 1089 cwdxHeSuStatusValue is any of the values: online(5), 1090 onlineNetAccessDisabled(6), onlineKekAssigned(7), and 1091 onlineTekAssigned(8), and the SU is considered as 1092 'offline' for other values for cwdxHeSuStatusValue." 1093 REFERENCE 1094 "cwdxHeSuStatusValue object." 1095 ::= { cwdxHeSuStatusExtEntry 4 } 1096 1097 1098cwdxIfHeSuStatusAvgOnlineTime OBJECT-TYPE 1099 SYNTAX TimeInterval 1100 MAX-ACCESS read-only 1101 STATUS current 1102 DESCRIPTION 1103 "The average period of time the SU stayed 'online' over 1104 the time period from the SU's first ranging message 1105 received by HE until now. 1106 1107 The SU is considered as 'online' when the value for 1108 cwdxHeSuStatusValue is any of the values: online(5), 1109 onlineNetAccessDisabled(6), onlineKekAssigned(7), and 1110 onlineTekAssigned(8), and the SU is considered as 1111 'offline' for other values for cwdxHeSuStatusValue." 1112 REFERENCE 1113 "cwdxHeSuStatusValue object." 1114 ::= { cwdxHeSuStatusExtEntry 5 } 1115 1116cwdxIfHeSuStatusMaxOnlineTime OBJECT-TYPE 1117 SYNTAX TimeInterval 1118 MAX-ACCESS read-only 1119 STATUS current 1120 DESCRIPTION 1121 "The maximum period of time the SU stayed 'online' over 1122 the time period from the SU's first ranging message 1123 received by HE until now. 1124 1125 The SU is considered as 'online' when the value for 1126 cwdxHeSuStatusValue is any of the values: online(5), 1127 onlineNetAccessDisabled(6), onlineKekAssigned(7), and 1128 onlineTekAssigned(8), and the SU is considered as 1129 'offline' for other values for cwdxHeSuStatusValue." 1130 REFERENCE 1131 "cwdxHeSuStatusValue object." 1132 ::= { cwdxHeSuStatusExtEntry 6 } 1133 1134cwdxIfHeSuStatusMinOfflineTime OBJECT-TYPE 1135 SYNTAX TimeInterval 1136 MAX-ACCESS read-only 1137 STATUS current 1138 DESCRIPTION 1139 "The minimum period of time SU stayed 'offline' over 1140 the time period from the SU's first ranging message 1141 received by HE until now. 1142 1143 The SU is considered as 'online' when the value for 1144 cwdxHeSuStatusValue is any of the values: online(5), 1145 onlineNetAccessDisabled(6), onlineKekAssigned(7), and 1146 onlineTekAssigned(8), and the SU is considered as 1147 'offline' for other values for cwdxHeSuStatusValue." 1148 REFERENCE 1149 "cwdxHeSuStatusValue object." 1150 ::= { cwdxHeSuStatusExtEntry 7 } 1151 1152 1153cwdxIfHeSuStatusAvgOfflineTime OBJECT-TYPE 1154 SYNTAX TimeInterval 1155 MAX-ACCESS read-only 1156 STATUS current 1157 DESCRIPTION 1158 "The average period of time the SU stayed 'offline' over 1159 the time period from the SU's first ranging message 1160 received by HE until now. 1161 1162 The SU is considered as 'online' when the value for 1163 cwdxHeSuStatusValue is any of the values: online(5), 1164 onlineNetAccessDisabled(6), onlineKekAssigned(7), and 1165 onlineTekAssigned(8), and the SU is considered as 1166 'offline' for other values for cwdxHeSuStatusValue." 1167 REFERENCE 1168 "cwdxHeSuStatusValue object." 1169 ::= { cwdxHeSuStatusExtEntry 8 } 1170 1171cwdxIfHeSuStatusMaxOfflineTime OBJECT-TYPE 1172 SYNTAX TimeInterval 1173 MAX-ACCESS read-only 1174 STATUS current 1175 DESCRIPTION 1176 "The maximum period of time the SU stayed 'offline' over 1177 the time period from the SU's first ranging message 1178 received by HE until now. 1179 1180 The SU is considered as 'online' when the value for 1181 cwdxHeSuStatusValue is any of the values: online(5), 1182 onlineNetAccessDisabled(6), onlineKekAssigned(7), and 1183 onlineTekAssigned(8), and the SU is considered as 1184 'offline' for other values for cwdxHeSuStatusValue." 1185 REFERENCE 1186 "cwdxHeSuStatusValue object." 1187 ::= { cwdxHeSuStatusExtEntry 9 } 1188 1189cwdxIfHeSuStatusDynSidCount OBJECT-TYPE 1190 SYNTAX INTEGER(0..16383) 1191 MAX-ACCESS read-only 1192 STATUS current 1193 DESCRIPTION 1194 "The number of active dynamic sids on this SU." 1195 ::= { cwdxHeSuStatusExtEntry 10 } 1196-- 1197-- HE MAC extension Table 1198-- 1199-- This table extends the attributes for HE MAC interface. 1200-- 1201-- This table includes attributes of the Subscriber-unit notification 1202-- enabling/disabling and the interval of Subscriber-unit notification sent 1203-- by the HE for a Subscriber-unit that the Mac interface supports. 1204-- 1205 1206cwdxHeMacExtTable OBJECT-TYPE 1207 SYNTAX SEQUENCE OF CwdxHeMacExtEntry 1208 MAX-ACCESS not-accessible 1209 STATUS current 1210 DESCRIPTION 1211 "This table contains the additions attributes of a HE MAC 1212 interface that provided by cwdIfHeMacTable." 1213 ::= { cwdxHeSuCpeObjects 4 } 1214 1215cwdxHeMacExtEntry OBJECT-TYPE 1216 SYNTAX CwdxHeMacExtEntry 1217 MAX-ACCESS not-accessible 1218 STATUS current 1219 DESCRIPTION 1220 "Additional objects for cwdIfHeMacTable entry including 1221 the Subscriber-unit notification enable/disable and the 1222 interval of Subscriber-unit notification sent by the HE 1223 for a Subscriber-unit that the Mac interface supports. 1224 An entry in this table exists for each ifEntry with an 1225 ifType of propDocsWirelessMacLayer(nnn)." 1226 REFERENCE 1227 "cwdIfHeMacTable in CISCO-WIRELESS-DOCS-IF-MIB.my." 1228 AUGMENTS { cwdIfHeMacEntry } 1229 ::= { cwdxHeMacExtTable 1 } 1230 1231CwdxHeMacExtEntry ::= SEQUENCE { 1232 cwdxHeSuOnOffTrapEnable TruthValue, 1233 cwdxHeSuOnOffTrapInterval Integer32, 1234 cwdxHeSuDefaultMaxCpes Integer32, 1235 cwdxHeTotalSusRegistered Integer32, 1236 cwdxHeTotalSusOffline Integer32 1237 1238 } 1239 1240cwdxHeSuOnOffTrapEnable OBJECT-TYPE 1241 SYNTAX TruthValue 1242 MAX-ACCESS read-write 1243 STATUS current 1244 DESCRIPTION 1245 "An indication of whether the cwdxHeSuOnOffNotification 1246 is enabled. The default value is false(2)." 1247 ::= { cwdxHeMacExtEntry 1 } 1248 1249cwdxHeSuOnOffTrapInterval OBJECT-TYPE 1250 SYNTAX Integer32 (0..86400) 1251 UNITS "seconds" 1252 MAX-ACCESS read-write 1253 STATUS current 1254 DESCRIPTION 1255 "The interval for cwdxHeSuOnOffNotification sent by HE for 1256 one online/offline state change if cwdxHeSuOnOffTrapEnable 1257 is true. 1258 1259 If there are more than one state changes to online/offline 1260 for a Subscriber-unit during this interval, only one 1261 cwdxHeSuOnOffNotification is sent by HE for the first 1262 state change to online and one cwdxHeSuOnOffNotification 1263 for the first state changing to offline if 1264 cwdxHeSuOnOffTrapEnable is true. 1265 1266 This is to avoid too many notifications sent for a 1267 SU online/offline state changes during a short period 1268 of time. 1269 1270 If the value is 0, then cwdxHeSuOnOffNotification will be 1271 sent for every state change to online/offline for a 1272 SU if cwdxHeSuOnOffTrapEnable is true. 1273 1274 This object's value will be retained even if the 1275 cwdxHeSuOnOffTrapEnable value changes. Thus disabling 1276 notifications will not result in this object's value 1277 being reset tot he default value. 1278 1279 The default value is 600 seconds." 1280 ::= { cwdxHeMacExtEntry 2 } 1281 1282cwdxHeSuDefaultMaxCpes OBJECT-TYPE 1283 SYNTAX Integer32 (0..255) 1284 MAX-ACCESS read-write 1285 STATUS current 1286 DESCRIPTION 1287 "The default maximum number of permitted CPEs per SU 1288 in this wireless interface. A SU can override this 1289 value by setting the object cwdxHeSuMaxCpeNumber 1290 in the cwdxHeSuTable. 1291 1292 The value 0 means no maximum limit. 1293 1294 The default value for this object is 0. 1295 1296 Setting the value will not affect the already connected 1297 CPEs to the SUs in this wireless interface." 1298 ::= { cwdxHeMacExtEntry 3 } 1299 1300cwdxHeTotalSusRegistered OBJECT-TYPE 1301 SYNTAX Integer32 (0..2147483647) 1302 MAX-ACCESS read-only 1303 STATUS current 1304 DESCRIPTION 1305 "Total number of SUs that successfully registered at 1306 least once with this HE. This count will be decremented 1307 whenever the SUs are aged out at the HE." 1308 ::= { cwdxHeMacExtEntry 4 } 1309 1310cwdxHeTotalSusOffline OBJECT-TYPE 1311 SYNTAX Integer32 (0..2147483647) 1312 MAX-ACCESS read-only 1313 STATUS current 1314 DESCRIPTION 1315 "Total number of SU's that are offline at this time. 1316 The SU is considered as 'online' when the value for 1317 cwdxHeSuStatusValue is any of the values: online(5), 1318 onlineNetAccessDisabled(6), onlineKekAssigned(7), and 1319 onlineTekAssigned(8), and the SU is considered as 1320 'offline' for other values for cwdxHeSuStatusValue." 1321 ::= { cwdxHeMacExtEntry 5 } 1322 1323 1324-- 1325-- HE SU channel override operation table and the related 1326-- objects 1327-- 1328-- An HE operator may perform downstream/upstream load balancing 1329-- or failure recovery using cwdxHeSuChOverTable. An entry 1330-- in this table is an operation from HE to generate downstream 1331-- frequency and upstream channel override fields in the RNG-RSP message 1332-- sent to a Subscriber-unit. A RNG-RSP message is sent to a Subscriber-unit 1333-- during initial maintenance opportunity. 1334-- 1335-- This operation causes the HE to place an entry for the 1336-- SU specified into the override request queue. The link is 1337-- then broken by deleting the SU from its polling list. When 1338-- the SU attempts initial ranging, the override request 1339-- causes downstream frequency and upstream channel override 1340-- fields to be inserted into the RNG-RSP message. 1341-- 1342 1343cwdxHeSuChOverTimeExpiration OBJECT-TYPE 1344 SYNTAX Integer32 (1..86400) 1345 UNITS "minutes" 1346 MAX-ACCESS read-write 1347 STATUS current 1348 DESCRIPTION 1349 "The time period to expire a HE channel override operation. 1350 Within the time period, if the HE cannot send out a 1351 RNG-RSP message with channel override fields to a 1352 SU specified in the operation, the HE will abort 1353 the operation. The possible reason is that the 1354 SU does not repeat the initial ranging. 1355 1356 The change to this object will not affect the already active 1357 operations in this cwdxHeSuChOverTable. 1358 1359 Once the operation completes, the management station should 1360 retrieve the values of the cwdxHeSuChOverState 1361 object of interest, and should then delete the entry 1362 from cwdxHeSuChOverTable. In order to prevent old 1363 entries from clogging the table, entries will be aged out, 1364 but an entry will never be deleted within 15 minutes of 1365 completing." 1366 REFERENCE 1367 "Data-Over-Cable Service Interface Specifications (DOCSIS) 1368 Radio Frequency Interface Specification (SP-RFI-I04-980724), 1369 6.3.2.5.3 Overriding Channels." 1370 ::= { cwdxHeSuCpeObjects 5 } 1371 1372 1373cwdxHeSuChOverTable OBJECT-TYPE 1374 SYNTAX SEQUENCE OF CwdxHeSuChOverEntry 1375 MAX-ACCESS not-accessible 1376 STATUS current 1377 DESCRIPTION 1378 "A table of HE operation entries to instruct Subscriber-units 1379 to move to a new downstream and/or upstream channel. 1380 1381 An entry in this table is an operation that has been 1382 initiated from HE to generates downstream frequency and/or 1383 upstream channel override fields in the RNG-RSP message sent 1384 to a Subscriber-unit. A RNG-RSP message is sent to a 1385 SU during initial maintenance opportunity. 1386 1387 This operation causes the HE to place an entry for the 1388 SU specified into the override request queue. The link is 1389 then broken by deleting the SU from its polling list. When 1390 the SU attempts initial ranging, the override request 1391 causes downstream frequency and upstream channel override 1392 fields to be inserted into the RNG-RSP message." 1393 ::= { cwdxHeSuCpeObjects 6 } 1394 1395cwdxHeSuChOverEntry OBJECT-TYPE 1396 SYNTAX CwdxHeSuChOverEntry 1397 MAX-ACCESS not-accessible 1398 STATUS current 1399 DESCRIPTION 1400 "An HE operation entry to instruct a Subscriber-unit to move 1401 to a new downstream and/or upstream channel. 1402 1403 There can be more than one entry per Subscriber-unit, 1404 so there is a time stamp for each entry to show the time 1405 when this operation is initiated. 1406 1407 A management station wishing to create an entry should 1408 first generate a pseudo-random serial number to be used 1409 as the index to this sparse table. The station should 1410 then create the associated instance of the row status 1411 object. It must also, either in the same or in successive 1412 PDUs, create the associated instance of the command and 1413 parameter objects. It should also modify the default values 1414 for any of the parameter objects if the defaults are not 1415 appropriate. 1416 1417 Once the appropriate instances of all the command 1418 objects have been created, either by an explicit SNMP 1419 set request or by default, the row status should be set 1420 to active to initiate the operation. Note that this entire 1421 procedure may be initiated via a single set request which 1422 specifies a row status of createAndGo as well as specifies 1423 valid values for the non-defaulted parameter objects. 1424 1425 Once an operation has been activated, it cannot be stopped. 1426 That is, it will run until either the HE has generated 1427 downstream frequency and/or upstream channel override fields 1428 in the RNG-RSP message sent to a Subscriber-unit or time out. 1429 In either case, the operation is completed. During this 1430 time the row cannot be destroyed. 1431 1432 Once the operation is completed, the real result of the 1433 operation to the Subscriber-unit cannot be known from this table. 1434 The result of the Subscriber-unit's downstream frequency and the 1435 upstream channel id can be checked from other MIB tables. 1436 For example, cwdIfHeServiceTable from 1437 CISCO-WIRELESS-DOCS-IF-MIB can be used to check 1438 whether the Subscriber-unit's downstream frequency 1439 and upstream channel id are changed. Please note that even 1440 though HE has generated downstream frequency and/or 1441 upstream channel override fields in the RNG-RSP message sent 1442 to a SUs if the SU cannot lock at the instructed downstream 1443 frequency or no upstream channel id could be used, it may 1444 reconnect back to the original downstream frequency and 1445 upstream channel id. 1446 1447 Once the operation completes, the management station should 1448 retrieve the values of the cwdxHeSuChOverState 1449 objects of interest, and should then delete the entry. 1450 In order to prevent old entries from clogging the table, 1451 entries will be aged out, but an entry will never be deleted 1452 within 15 minutes of completing." 1453 REFERENCE 1454 "Data-Over-Cable Service Interface Specifications (DOCSIS) 1455 Radio Frequency Interface Specification (SP-RFI-I04-980724), 1456 6.3.2.5.3 Overriding Channels." 1457 INDEX { cwdxHeSuChOverSerialNumber } 1458 ::= { cwdxHeSuChOverTable 1 } 1459 1460CwdxHeSuChOverEntry ::= SEQUENCE { 1461 -- index 1462 cwdxHeSuChOverSerialNumber Integer32, 1463 -- operation items 1464 cwdxHeSuChOverMacAddress MacAddress, 1465 cwdxHeSuChOverDownFrequency Integer32, 1466 cwdxHeSuChOverUpChannelId Integer32, 1467 cwdxHeSuChOverTrapOnCompletion TruthValue, 1468 -- status items 1469 cwdxHeSuChOverOpInitiatedTime TimeStamp, 1470 cwdxHeSuChOverState INTEGER, 1471 cwdxHeSuChOverRowStatus RowStatus 1472 } 1473 1474cwdxHeSuChOverSerialNumber OBJECT-TYPE 1475 SYNTAX Integer32 (1..2147483647) 1476 MAX-ACCESS not-accessible 1477 STATUS current 1478 DESCRIPTION 1479 "Object which specifies a unique entry in the 1480 table. A management station wishing to initiate a 1481 channel override operation should use a pseudo-random 1482 value for this object when creating or modifying an 1483 instance of a cwdxHeSuChOverEntry." 1484 ::= { cwdxHeSuChOverEntry 1 } 1485 1486cwdxHeSuChOverMacAddress OBJECT-TYPE 1487 SYNTAX MacAddress 1488 MAX-ACCESS read-create 1489 STATUS current 1490 DESCRIPTION 1491 "The mac address of the Subscriber-unit that the HE instructs to 1492 move to a new downstream and/or upstream channel. 1493 1494 This column must be set to a valid Mac address currently in 1495 the HE in order for this entry's row status to be set to 1496 active successfully." 1497 ::= { cwdxHeSuChOverEntry 2 } 1498 1499cwdxHeSuChOverDownFrequency OBJECT-TYPE 1500 SYNTAX Integer32 (0..1000000000) 1501 UNITS "hertz" 1502 MAX-ACCESS read-create 1503 STATUS current 1504 DESCRIPTION 1505 "The new downstream frequency which the Subscriber-unit is 1506 instructed to move to. The value 0 is to ask the HE not to 1507 override the downstream frequency." 1508 DEFVAL { 0 } 1509 ::= { cwdxHeSuChOverEntry 3 } 1510 1511cwdxHeSuChOverUpChannelId OBJECT-TYPE 1512 SYNTAX Integer32 (-1..255) 1513 MAX-ACCESS read-create 1514 STATUS current 1515 DESCRIPTION 1516 "The new channel Id which the Subscriber-unit is instructed to 1517 move to. The value -1 is to ask the HE not to override 1518 the upstream channel Id." 1519 DEFVAL { -1 } 1520 ::= { cwdxHeSuChOverEntry 4 } 1521 1522cwdxHeSuChOverTrapOnCompletion OBJECT-TYPE 1523 SYNTAX TruthValue 1524 MAX-ACCESS read-create 1525 STATUS current 1526 DESCRIPTION 1527 "Specifies whether or not a cwdxHeSuChOverNotification 1528 should be issued on completion of the operation. If such a 1529 notification is desired, it is the responsibility of the 1530 management entity to ensure that the SNMP administrative model 1531 is configured in such a way as to allow the notification to be 1532 delivered." 1533 DEFVAL { false } 1534 ::= { cwdxHeSuChOverEntry 5 } 1535 1536cwdxHeSuChOverOpInitiatedTime OBJECT-TYPE 1537 SYNTAX TimeStamp 1538 MAX-ACCESS read-only 1539 STATUS current 1540 DESCRIPTION 1541 "The value of sysUpTime at which the operation was initiated. 1542 Since it is possible to have more than one entry in this 1543 table for a Subscriber-unit, this object can help to distinguish 1544 the entries for the same Subscriber-unit." 1545 ::= { cwdxHeSuChOverEntry 6 } 1546 1547cwdxHeSuChOverState OBJECT-TYPE 1548 SYNTAX INTEGER { 1549 messageSent(1), 1550 commandNotActive(2), 1551 noOpNeeded(3), 1552 suNotFound(4), 1553 waitToSendMessage(5), 1554 timeOut(6) 1555 } 1556 MAX-ACCESS read-only 1557 STATUS current 1558 DESCRIPTION 1559 "The status of the specified channel override operation. 1560 The enumerations are: 1561 messageSent(1): the HE has sent a RNG-RSP message 1562 with channel override to the Subscriber-unit. 1563 commandNotActive(2): the command is not in active mode 1564 due to this entry's row status is not 1565 in active yet. 1566 noOpNeeded(3): The downstream frequency and the upstream 1567 channel Id in this entry are the same as 1568 original ones when this entry's row status 1569 is set to active, so HE does not need to 1570 do any operation. 1571 SuNotFound(4): The SU is not found in the HE 1572 at the time when the command becomes 1573 active. 1574 waitToSendMessage(5): specified the operation is active 1575 and HE is waiting to send 1576 a RNG-RSP message with channel 1577 override to the Subscriber-unit. 1578 timeOut(6): specified the operation is timed out. 1579 That is, the HE cannot send a RNG-RSP message 1580 with channel override to the Subscriber-unit within 1581 the time specified in the object of 1582 cwdxHeSuChOverTimeExpiration. 1583 The possible reason is that the Subscriber-unit 1584 does not repeat the initial ranging. 1585 1586 The possible state change diagram is as below: 1587 [commandNotActive ->] waitToSendMessage -> 1588 messageSent or timeOut. 1589 [commandNotActive ->] noOpNeeded or SuNotFound." 1590 REFERENCE 1591 "Data-Over-Cable Service Interface Specifications (DOCSIS) 1592 Radio Frequency Interface Specification (SP-RFI-I04-980724), 1593 6.3.2.5.3 Overriding Channels." 1594 ::= { cwdxHeSuChOverEntry 7 } 1595 1596cwdxHeSuChOverRowStatus OBJECT-TYPE 1597 SYNTAX RowStatus 1598 MAX-ACCESS read-create 1599 STATUS current 1600 DESCRIPTION 1601 "The status of this table entry. 1602 1603 This value for cwdxHeSuChOverMacAddress must be valid Mac 1604 address currently in the HE in order for the row 1605 status to be set to active successfully. 1606 1607 Once the row status becomes active and state becomes 1608 waitToSendMessage, the entry cannot not be changed except 1609 to delete the entry by setting the row status to destroy(6) 1610 and since the operation cannot be stopped, the destroy(6) 1611 will just cause the SNMP agent to hide the entry from 1612 application and the SNMP agent will delete the entry 1613 right after the operation is completed." 1614 ::= { cwdxHeSuChOverEntry 8 } 1615 1616-- 1617-- HE Subscriber-unit (SU) Table 1618-- 1619-- This table contains attributes or configurable parameters 1620-- for Subscriber-units from a HE. 1621-- 1622-- An HE operator can use this table to report a Subscriber-unit's 1623-- attributes or configure a Subscriber-unit by a Subscriber-unit's 1624-- MAC address. 1625-- 1626 1627cwdxHeSuTable OBJECT-TYPE 1628 SYNTAX SEQUENCE OF CwdxHeSuEntry 1629 MAX-ACCESS not-accessible 1630 STATUS current 1631 DESCRIPTION 1632 "This table contains attributes or configurable parameters 1633 for Subscriber-units from a HE." 1634 ::= { cwdxHeSuCpeObjects 7 } 1635 1636cwdxHeSuEntry OBJECT-TYPE 1637 SYNTAX CwdxHeSuEntry 1638 MAX-ACCESS not-accessible 1639 STATUS current 1640 DESCRIPTION 1641 "The list contains a SU's attributes or 1642 configurable parameters from a HE." 1643 INDEX { cwdIfHeSuStatusIndex } 1644 ::= { cwdxHeSuTable 1 } 1645 1646CwdxHeSuEntry ::= SEQUENCE { 1647 cwdxHeSuMaxCpeNumber Integer32 1648 } 1649 1650cwdxHeSuMaxCpeNumber OBJECT-TYPE 1651 SYNTAX Integer32 (-1..255) 1652 MAX-ACCESS read-write 1653 STATUS current 1654 DESCRIPTION 1655 "The maximum number of permitted CPEs connecting to the 1656 SU. 1657 1658 The value -1 means to use the default value of maximum 1659 hosts per SU in the HE wireless interface which the SU 1660 connects to and the value is defined in 1661 cwdxHeSuDefaultMaxCpes in the cwdxHeMacExtTable. 1662 1663 The value 0 means no maximum limit. 1664 1665 The default value is -1. 1666 1667 Setting the value will not affect the already connected 1668 CPEs to the SU." 1669 ::= { cwdxHeSuEntry 1 } 1670 1671-- 1672-- Quality of Service Extension table 1673-- 1674 1675cwdxQosProfileExtTable OBJECT-TYPE 1676 SYNTAX SEQUENCE OF CwdxQosProfileExtEntry 1677 MAX-ACCESS not-accessible 1678 STATUS current 1679 DESCRIPTION 1680 "This table contains additional attributes to the Qos 1681 profiles that exists in cwdIfQosProfileTable in 1682 CISCO-WIRELESS-DOCS-IF-MIB." 1683 ::= { cwdxQosProfileExtObjects 1 } 1684 1685cwdxQosProfileExtEntry OBJECT-TYPE 1686 SYNTAX CwdxQosProfileExtEntry 1687 MAX-ACCESS not-accessible 1688 STATUS current 1689 DESCRIPTION 1690 "Each row extends the existing row in the 1691 cwdIfQosProfileTable with additional QOS parameters." 1692 AUGMENTS { cwdIfQosProfileEntry } 1693 ::= { cwdxQosProfileExtTable 1 } 1694 1695CwdxQosProfileExtEntry ::= SEQUENCE { 1696 cwdxQosProfGrantInterval INTEGER, 1697 cwdxQosProfGrantSize INTEGER, 1698 cwdxQosProfName DisplayString, 1699 cwdxQosProfTosOverwriteMask INTEGER, 1700 cwdxQosProfTosOverwriteValue INTEGER 1701 } 1702 1703cwdxQosProfGrantInterval OBJECT-TYPE 1704 SYNTAX INTEGER (0..65535) 1705 UNITS "milliseconds" 1706 MAX-ACCESS read-create 1707 STATUS current 1708 DESCRIPTION 1709 "The value of this parameter specifies the interval 1710 between successive data grant opportunities for a 1711 service flow. This object is required for 1712 Unsolicited Grant and Unsolicited Grant with 1713 Activity Detection Service Flows. This object is 1714 optional for Real-Time Polling Service Flows." 1715 REFERENCE 1716 "Data over Cable Radio Frequency Interface Specification, 1717 SP-RFIv1.1-I02-990731 Appendix M.1.2" 1718 DEFVAL{ 20 } 1719 ::= { cwdxQosProfileExtEntry 1 } 1720 1721cwdxQosProfGrantSize OBJECT-TYPE 1722 SYNTAX INTEGER (0..65535) 1723 UNITS "bytes" 1724 MAX-ACCESS read-create 1725 STATUS current 1726 DESCRIPTION 1727 "This parameter specifies the unsolicited grant size." 1728 REFERENCE 1729 "Data over Cable Radio Frequency Interface Specification, 1730 SP-RFIv1.1-I02-990731 Appendix M.1.2" 1731 DEFVAL{ 229 } 1732 ::= { cwdxQosProfileExtEntry 2 } 1733 1734cwdxQosProfName OBJECT-TYPE 1735 SYNTAX DisplayString(SIZE(0..64)) 1736 MAX-ACCESS read-create 1737 STATUS current 1738 DESCRIPTION 1739 "This object is a string used to describe this Qos 1740 Profile. It has informational significance only." 1741 DEFVAL{ "" } 1742 ::= { cwdxQosProfileExtEntry 3 } 1743 1744cwdxQosProfTosOverwriteMask OBJECT-TYPE 1745 SYNTAX INTEGER (0..255) 1746 MAX-ACCESS read-create 1747 STATUS current 1748 DESCRIPTION 1749 "This object is the bit mask (8 bit wide) for 1750 tos-overwrite feature. The 1751 cwdxQosProfTosOverwriteValue is written where the 1752 mark bits are set to 1. 1753 Tos-overwrite allows the HE to mark egress IP packets 1754 (from the HE) with a specific TOS value. This relieves 1755 the subscriber unit from marking upstream packets with 1756 a specific TOS and is most useful when a subscriber 1757 unit is supplied by a third party vendor who may not 1758 have the option of applying a TOS to an IP packet. 1759 Each packet received from an SU that matches this QoS 1760 profile will be tagged with the TOS-overwrite value 1761 at the cwdxQosProfTosOverwriteMask and sent to the 1762 network." 1763 DEFVAL { 0 } 1764 ::= { cwdxQosProfileExtEntry 4 } 1765 1766cwdxQosProfTosOverwriteValue OBJECT-TYPE 1767 SYNTAX INTEGER (0..255) 1768 MAX-ACCESS read-create 1769 STATUS current 1770 DESCRIPTION 1771 "This object is the byte value for tos-overwrite. The 1772 cwdxQosProfTosOverwriteValue is written where the mark 1773 bits are set to 1. 1774 Each packet received from an SU that matches this QoS 1775 profile will be tagged with the 1776 cwdxQosProfTosOverwriteValue value at the 1777 cwdxQosProfTosOverwriteMask and sent to the 1778 network." 1779 DEFVAL { 0 } 1780 ::= { cwdxQosProfileExtEntry 5 } 1781 1782 1783cwdxQosIpTosRatelimitTable OBJECT-TYPE 1784 SYNTAX SEQUENCE OF CwdxQosIpTosRatelimitEntry 1785 MAX-ACCESS not-accessible 1786 STATUS current 1787 DESCRIPTION 1788 "Describes the Ip-precedence attached to every 1789 Qos Profile identified by a row in 1790 cwdIfQosProfileTable in CISCO-WIRELESS-DOCS-IF-MIB." 1791 ::= { cwdxQosProfileExtObjects 2 } 1792 1793cwdxQosIpTosRatelimitEntry OBJECT-TYPE 1794 SYNTAX CwdxQosIpTosRatelimitEntry 1795 MAX-ACCESS not-accessible 1796 STATUS current 1797 DESCRIPTION 1798 "Describes the Ip Precedence parameters. For every 1799 QOS profile entry in the cwdIfQosProfileTable, 1800 there will be seven corresponding rows in this 1801 cwdxQosIpTosRatelimitTable. 1802 1803 The default value of 0 will be assigned to 1804 cwdxQosIpTosRatelimitMaxDownRate for all the 1805 rows." 1806 INDEX {cwdIfQosProfIndex, cwdxQosIpTosRatelimitIndex } 1807 ::= { cwdxQosIpTosRatelimitTable 1 } 1808 1809CwdxQosIpTosRatelimitEntry ::= SEQUENCE { 1810 cwdxQosIpTosRatelimitIndex INTEGER, 1811 cwdxQosIpTosRatelimitMaxDownRate INTEGER 1812 } 1813 1814cwdxQosIpTosRatelimitIndex OBJECT-TYPE 1815 SYNTAX INTEGER (1..8) 1816 MAX-ACCESS not-accessible 1817 STATUS current 1818 DESCRIPTION 1819 "The index value along with the primary index of 1820 cwdIfQosProfIndex which uniquely identifies an entry 1821 in the cwdxQosIpTosRatelimitEntry." 1822 ::= { cwdxQosIpTosRatelimitEntry 1 } 1823 1824cwdxQosIpTosRatelimitMaxDownRate OBJECT-TYPE 1825 SYNTAX INTEGER (0..100000000) 1826 UNITS "bps" 1827 MAX-ACCESS read-write 1828 STATUS current 1829 DESCRIPTION 1830 "Maximum downstream rate that can be allowed with 1831 this IP precedence." 1832 ::= { cwdxQosIpTosRatelimitEntry 2 } 1833 1834-- 1835-- The Cisco DOCS Extension MIB Notifications 1836-- 1837 1838ciscoWirelessDocsExtNotificationsPrefix OBJECT IDENTIFIER 1839 ::= { ciscoWirelessDocsExtMIB 2 } 1840ciscoWirelessDocsExtNotifications OBJECT IDENTIFIER 1841 ::= { ciscoWirelessDocsExtNotificationsPrefix 0 } 1842 1843 1844cwdxHeSuOnOffNotification NOTIFICATION-TYPE 1845 OBJECTS { cwdIfHeSuStatusMacAddress, 1846 cwdIfHeSuStatusIpAddress, 1847 cwdIfHeSuStatusDownChanIfIndex, 1848 cwdIfHeSuStatusUpChanIfIndex, 1849 cwdIfHeSuStatusServiceId, 1850 cwdxHeSuStatusValue 1851 } 1852 STATUS current 1853 DESCRIPTION 1854 "This notification indicates that the SU coming online 1855 and going offline. A notification will be sent from HE for 1856 a SU status changing to online or offline 1857 within the interval specified in cwdxHeSuOnOffTrapInterval." 1858 ::= { ciscoWirelessDocsExtNotifications 1 } 1859 1860 1861cwdxHeSuChOverNotification NOTIFICATION-TYPE 1862 OBJECTS { cwdxHeSuChOverMacAddress, 1863 cwdxHeSuChOverDownFrequency, 1864 cwdxHeSuChOverUpChannelId, 1865 cwdxHeSuChOverOpInitiatedTime, 1866 cwdxHeSuChOverState 1867 } 1868 STATUS current 1869 DESCRIPTION 1870 "This notification is sent at the completion of a HE 1871 channel override operation if 1872 cwdxHeSuChOverTrapOnCompletion is true in the 1873 original entry. 1874 1875 Once a channel override operation has been activated, it 1876 cannot be stopped. That is, it will run until either the 1877 HE has generated downstream frequency and/or upstream 1878 channel override fields in the RNG-RSP message sent to a 1879 HE or cwdxHeSuChOverTimeExpiration time expired. 1880 In either case, the operation is completed. State in the 1881 cwdxHeSuChOverState object will tell in which 1882 condition the operation is completed." 1883 ::= { ciscoWirelessDocsExtNotifications 2 } 1884 1885 1886 1887 1888-- 1889-- The Cisco DOCS Extension MIB Conformance Statements 1890-- 1891 1892-- 1893-- Conformance statement 1894-- 1895 1896ciscoWirelessDocsExtConformance OBJECT IDENTIFIER 1897 ::= { ciscoWirelessDocsExtMIB 3 } 1898cwdxDocsExtCompliances OBJECT IDENTIFIER 1899 ::= { ciscoWirelessDocsExtConformance 1 } 1900cwdxDocsExtGroups OBJECT IDENTIFIER 1901 ::= { ciscoWirelessDocsExtConformance 2 } 1902 1903 1904-- compliance statements 1905 1906cwdxDocsExtCompliance MODULE-COMPLIANCE 1907 STATUS current 1908 DESCRIPTION 1909 "The compliance statement for devices that implement MCNS 1910 compliant Radio Frequency Interfaces and DOCSIS features." 1911 MODULE -- this module 1912 MANDATORY-GROUPS { 1913 cwdxQosCtrlGroup, 1914 cwdxQosQueueGroup, 1915 cwdxHeSuCpeGroup 1916 } 1917 1918 OBJECT cwdxHeSuChOverTimeExpiration 1919 MIN-ACCESS read-only 1920 DESCRIPTION 1921 "Write access is not required." 1922 ::= { cwdxDocsExtCompliances 1 } 1923 1924 1925-- MIB groupings 1926 1927cwdxQosCtrlGroup OBJECT-GROUP 1928 OBJECTS { 1929 cwdxQosCtrlUpAdmissionCtrl, 1930 cwdxQosCtrlUpMaxRsvdBWPercent, 1931 cwdxQosCtrlUpAdmissionRejects, 1932 cwdxQosCtrlUpReservedBW, 1933 cwdxQosCtrlUpMaxVirtualBW, 1934 cwdxQosIfRateLimitAlgo, 1935 cwdxQosIfRateLimitExpWgt, 1936 cwdxQosIfRateLimitShpMaxDelay, 1937 cwdxQosIfRateLimitShpGranularity, 1938 cwdxIfHeServiceOutOctets, 1939 cwdxIfHeServiceOutPackets, 1940 cwdxQosMaxUpBWExcessRequests, 1941 cwdxQosMaxDownBWExcessPackets, 1942 cwdxQosProfGrantInterval, 1943 cwdxQosProfGrantSize, 1944 cwdxQosProfName, 1945 cwdxQosProfTosOverwriteMask, 1946 cwdxQosProfTosOverwriteValue, 1947 cwdxQosIpTosRatelimitMaxDownRate 1948 } 1949 STATUS current 1950 DESCRIPTION 1951 "Group of objects implemented in HE wireless 1952 interfaces for states of the scheduler supporting 1953 Data-Over-Cable Service Interface Specifications (DOCSIS) 1954 1.0 Quality of Service (QoS)." 1955 ::= { cwdxDocsExtGroups 1 } 1956 1957cwdxQosQueueGroup OBJECT-GROUP 1958 OBJECTS { 1959 cwdxBWQueueOrder, 1960 cwdxBWQueueNumServedBeforeYield, 1961 cwdxBWQueueType, 1962 cwdxBWQueueMaxDepth, 1963 cwdxBWQueueDepth, 1964 cwdxBWQueueDiscards 1965 } 1966 STATUS current 1967 DESCRIPTION 1968 "Group of objects implemented in HE wireless interfaces 1969 for the queuing states of the scheduler supporting 1970 Data-Over-Cable Service Interface Specifications 1971 (DOCSIS) 1.0 Quality of Service (QoS). Each upstream scheduler 1972 maintains a queue set, but the downstream schedulers does not 1973 in DOCSIS 1.0 QoS. So only each upstream has an entry for 1974 DOCSIS 1.0 QoS support." 1975 ::= { cwdxDocsExtGroups 2 } 1976 1977cwdxHeSuCpeGroup OBJECT-GROUP 1978 OBJECTS { 1979 cwdxCpeIpAddress, 1980 cwdxCpeAccessGroup, 1981 cwdxSuMappingStatusIndex, 1982 cwdxHeSuStatusValue, 1983 cwdxIfHeSuStatusOnlineTimes, 1984 cwdxIfHeSuStatusPercentOnline, 1985 cwdxIfHeSuStatusMinOnlineTime, 1986 cwdxIfHeSuStatusAvgOnlineTime, 1987 cwdxIfHeSuStatusMaxOnlineTime, 1988 cwdxIfHeSuStatusMinOfflineTime, 1989 cwdxIfHeSuStatusAvgOfflineTime, 1990 cwdxIfHeSuStatusMaxOfflineTime, 1991 cwdxIfHeSuStatusDynSidCount, 1992 cwdxHeSuOnOffTrapEnable, 1993 cwdxHeSuOnOffTrapInterval, 1994 cwdxHeSuDefaultMaxCpes, 1995 cwdxHeTotalSusRegistered, 1996 cwdxHeTotalSusOffline, 1997 cwdxHeSuChOverTimeExpiration, 1998 cwdxHeSuChOverMacAddress, 1999 cwdxHeSuChOverDownFrequency, 2000 cwdxHeSuChOverUpChannelId, 2001 cwdxHeSuChOverTrapOnCompletion, 2002 cwdxHeSuChOverOpInitiatedTime, 2003 cwdxHeSuChOverState, 2004 cwdxHeSuChOverRowStatus, 2005 cwdxHeSuMaxCpeNumber 2006 } 2007 STATUS current 2008 DESCRIPTION 2009 "Group of objects implemented in HE for managing and 2010 monitoring Customer Premises Equipments." 2011 ::= { cwdxDocsExtGroups 3 } 2012 2013 2014END 2015