1-- ***************************************************************** 2-- DOCS-DRF-MIB.my: 3-- 4-- Nov 2007 Bo Wu 5-- 6-- Initial Version: Oct 2007: CableLabs ECN M-OSSI-N-07.0562-5 7-- 8-- Copyright (c) 2007-2008 by cisco Systems, Inc. 9-- All rights reserved. 10-- ***************************************************************** 11 12DOCS-DRF-MIB DEFINITIONS ::= BEGIN 13 14IMPORTS 15 MODULE-IDENTITY, 16 OBJECT-IDENTITY, 17 OBJECT-TYPE, 18 Unsigned32 19 FROM SNMPv2-SMI 20 TruthValue, 21 AutonomousType 22 FROM SNMPv2-TC 23 OBJECT-GROUP, 24 MODULE-COMPLIANCE 25 FROM SNMPv2-CONF 26 27 PhysicalIndexOrZero, 28 PhysicalIndex FROM ENTITY-MIB 29 ifIndex, 30 31 InterfaceIndexOrZero 32 FROM IF-MIB 33 docsIfDownstreamChannelEntry 34 FROM DOCS-IF-MIB 35 clabProjDocsis 36 FROM CLAB-DEF-MIB; 37 38docsDrfMib MODULE-IDENTITY 39 LAST-UPDATED "200712060000Z" -- December 6, 2007 40 ORGANIZATION "Cable Television Laboratories, Inc" 41 CONTACT-INFO 42 "Postal: Cable Television Laboratories, Inc. 43 858 Coal Creek Circle 44 Louisville, Colorado 80027-9750 45 U.S.A. 46 Phone: +1 303-661-9100 47 Fax: +1 303-661-9199 48 E-mail: mibs@cablelabs.com" 49 DESCRIPTION 50 "This MIB module contains the management objects for the 51 management of the Downstream RF Interface specification. 52 Copyright 1999-2007 Cable Television Laboratories, Inc. 53 All rights reserved." 54 REVISION "200712060000Z" -- December 6, 2007 55 DESCRIPTION 56 "Initial version, published as as part of the CableLabs 57 MOSSI specification CM-SP-M-OSSI-I07-YYMMDD via ECN 58 M-OSSI-R-07.0562-x" 59 ::= { clabProjDocsis 23 } 60 61-- --------------------------------------------------------- 62-- Textual Conventions 63-- --------------------------------------------------------- 64 65-- --------------------------------------------------------------------- 66-- Main Groups 67-- --------------------------------------------------------------------- 68 69docsDrfNotifications OBJECT IDENTIFIER ::= { docsDrfMib 0 } 70docsDrfObjects OBJECT IDENTIFIER ::= { docsDrfMib 1 } 71 72 73-- -------------------------------------------------------------------- 74-- DOCSIS DRF objects 75-- -------------------------------------------------------------------- 76 77-- -------------------------------------------------------------------- 78-- 79-- PHY Parameters dependencies OBJECT-IDENTITY definitions 80-- 81-- -------------------------------------------------------------------- 82 83docsDrfRegistry OBJECT-IDENTITY 84 STATUS current 85 DESCRIPTION 86 "Registration point for M-CMTS characterization of PHY 87 parameters dependencies." 88 ::= { docsDrfObjects 1 } 89 90docsDrfPhyParamFixValue OBJECT-IDENTITY 91 STATUS current 92 DESCRIPTION 93 "Indicates that this PHY parameter is fixed and cannot 94 be changed." 95 ::= { docsDrfRegistry 1 } 96 97docsDrfPhyParamSameValue OBJECT-IDENTITY 98 STATUS current 99 DESCRIPTION 100 "Indicates that the PHY parameter value is the same for 101 the elements in a dependency group; thus, a change in 102 the PHY parameter of an element in the group will change 103 the PHY parameter value in the other elements of the 104 dependency group." 105 ::= { docsDrfRegistry 2 } 106 107docsDrfPhyParamAdjacentValues OBJECT-IDENTITY 108 STATUS current 109 DESCRIPTION 110 "Indicates that the PHY parameter has an adjacency or 111 sequence pattern for the elements in a dependency group 112 e.g., A group of channels all using J.83 Annex A, may set 113 frequencies in the group by setting a 6 MHz spacing 114 between the channels in the group. Vendors may rather 115 use a more detailed vendor-specific OBJECT-IDENTITY or a 116 table pointer to describe this type of PHY parameter 117 dependency." 118 ::= { docsDrfRegistry 3 } 119 120docsDrfPhyParamFrequencyRange OBJECT-IDENTITY 121 STATUS current 122 DESCRIPTION 123 "This object indicates that the frequency in a TSID Group 124 is constrained to a frequency range. Vendors may extend 125 the MIB construct containing this reference to detail such 126 constraints or rather use a more detailed vendor-specific 127 OBJECT-IDENTITY or a table pointer to describe the 128 frequency range supported." 129 ::= { docsDrfRegistry 4 } 130 131-- --------------------------------------------------------------------- 132-- DOCSIS DRF Interface Extension objects 133-- --------------------------------------------------------------------- 134 135docsDrfDownstreamTable OBJECT-TYPE 136 SYNTAX SEQUENCE OF DocsDrfDownstreamEntry 137 MAX-ACCESS not-accessible 138 STATUS current 139 DESCRIPTION 140 "Extensions for the DOCSIS RFI Downstream 141 docsIfDownstreamChannelTable." 142 ::= { docsDrfObjects 2 } 143 144docsDrfDownstreamEntry OBJECT-TYPE 145 SYNTAX DocsDrfDownstreamEntry 146 MAX-ACCESS not-accessible 147 STATUS current 148 DESCRIPTION 149 "A conceptual row for this table. 150 There is a corresponding entry for each entry of 151 docsIfDownstreamChannelTable." 152 AUGMENTS { docsIfDownstreamChannelEntry } 153 ::= { docsDrfDownstreamTable 1 } 154 155DocsDrfDownstreamEntry ::= SEQUENCE 156 { 157 docsDrfDownstreamPhyDependencies BITS 158 } 159 160docsDrfDownstreamPhyDependencies OBJECT-TYPE 161 SYNTAX BITS { 162 frequency(0), 163 bandwidth(1), 164 power(2), 165 modulation(3), 166 interleaver(4), 167 j83Annex(5), 168 symbolRate(6), 169 mute(7) 170 } 171 MAX-ACCESS read-only 172 STATUS current 173 DESCRIPTION 174 "The summary of the Downstream Interface 175 dependencies based on the constraints of 176 docsDrfGroupDependencyEntry. 177 A BIT position set to '1' indicates the PHY parameter 178 belongs to a dependency group. 179 A BIT position set to '0', indicates the PHY parameter 180 does not belong to a dependency group. 181 182 For Interfaces configured via DEPI this information is 183 reflected in the DEPI session as DEPI TSID group 184 dependencies. 185 186 If this object value is the zero-length string, it indicates 187 this interface is configurable via DEPI but no session is 188 currently active." 189 ::= { docsDrfDownstreamEntry 1 } 190 191-- --------------------------------------------------------------------- 192-- DRF Downstream Interface Capabilities 193-- --------------------------------------------------------------------- 194 195docsDrfDownstreamCapabilitiesTable OBJECT-TYPE 196 SYNTAX SEQUENCE OF DocsDrfDownstreamCapabilitiesEntry 197 MAX-ACCESS not-accessible 198 STATUS current 199 DESCRIPTION 200 "This table contains the QAM channel capabilities 201 for the Downstream Interface PHY parameters." 202 ::= { docsDrfObjects 3 } 203 204docsDrfDownstreamCapabilitiesEntry OBJECT-TYPE 205 SYNTAX DocsDrfDownstreamCapabilitiesEntry 206 MAX-ACCESS not-accessible 207 STATUS current 208 DESCRIPTION 209 "A conceptual row for this table." 210 INDEX { ifIndex } 211 ::= { docsDrfDownstreamCapabilitiesTable 1 } 212 213DocsDrfDownstreamCapabilitiesEntry ::= SEQUENCE 214 { 215 docsDrfDownstreamCapabFrequency BITS, 216 docsDrfDownstreamCapabBandwidth BITS, 217 docsDrfDownstreamCapabPower BITS, 218 docsDrfDownstreamCapabModulation BITS, 219 docsDrfDownstreamCapabInterleaver BITS, 220 docsDrfDownstreamCapabJ83Annex BITS, 221 docsDrfDownstreamCapabConcurrentServices BITS, 222 docsDrfDownstreamCapabServicesTransport BITS, 223 docsDrfDownstreamCapabMuting BITS 224 } 225 226docsDrfDownstreamCapabFrequency OBJECT-TYPE 227 SYNTAX BITS { 228 qamDependency(0), 229 adjacentChannel(1), 230 adjacentChannelOrder(2) 231 } 232 MAX-ACCESS read-only 233 STATUS current 234 DESCRIPTION 235 "The QAM channel frequency capabilities. 236 'qamDependency' BIT set to '1' indicates the QAM channel 237 frequency value has dependencies with other QAM channels 238 and an entry that includes this QAM channel is in 239 in docsDrfGroupDependencyTable for the PHY 240 parameter 'frequency'. 241 242 'adjacentChannel' BIT set to '1' indicates the QAM channel 243 frequencies in the dependency group (DEPI TSID group) are 244 adjacent and constrained in a frequency range based on 245 the number of QAM channels in the dependency group. 246 247 'adjacentChannelOrder' BIT set to '1' indicates the QAM 248 channel frequency adjacency is based in the QAM channel 249 sequence like entPhysicalParentRelPos in EntPhysicalTable 250 or other vendor sequence. 251 252 e.g., a dependency group of four QAM channels 253 with 'adjacentChannelOrder' BIT set to '1': 254 The 4th QAM channel in the sequence gets a frequency 255 assignment f + 1*bandwidth when the frequency value of 256 the 3rd QAM channel in the sequence is set to f. 257 Similarly the 1st QAM channel in the sequence gets a 258 frequency assignment of f - 2*bandwidth and the 2nd QAM 259 channels gets a frequency of f -1*bandwidth. 260 261 'adjacentChannel' 'adjacentChannelOrder' BITs may be set to 262 '1' when a dependency group includes the QAM channel 263 of this M-CMTS Downstream interface and the value of the 264 object docsDrfGroupDependencyType is 265 docsDrfPhyParamAdjacentValues. 266 267 'adjacentChannel' BIT may be set to '1' if 268 'qamDependency' BIT is set to '1'. The same way, 269 'adjacentChannelOrder' BIT may be set to '1' and implies 270 'adjacentChannel' BIT is set to '1'." 271 ::= { docsDrfDownstreamCapabilitiesEntry 1 } 272 273docsDrfDownstreamCapabBandwidth OBJECT-TYPE 274 SYNTAX BITS { 275 qamDependency(0), 276 chan6Mhz(1), 277 chan8Mhz(2) 278 } 279 MAX-ACCESS read-only 280 STATUS current 281 DESCRIPTION 282 "The QAM channel Bandwidth capabilities. 283 'qamDependency' BIT set to '1' indicates the QAM channel 284 bandwidth value has dependencies with other QAM channels 285 as indicated in docsDrfGroupDependencyTable. 286 287 'chan6Mhz' set to '1' indicates 6 MHz channel width 288 support. 289 'chan8Mhz' set to '1' indicates 8 MHz channel width 290 support. 291 292 When 'qamDependency' BIT is set to '1', a set to the 293 channel bandwidth PHY parameter of a QAM channels in a 294 dependency group (with docsDrfGroupDependencyType 295 set to docsDrfPhyParamSameValue), sets the same channel 296 bandwidth value to all QAM channels in the dependency 297 group." 298 ::= { docsDrfDownstreamCapabilitiesEntry 2 } 299 300docsDrfDownstreamCapabPower OBJECT-TYPE 301 SYNTAX BITS { 302 qamDependency(0) 303 } 304 MAX-ACCESS read-only 305 STATUS current 306 DESCRIPTION 307 "The QAM channel Power capabilities. 308 'qamDependency' BIT set to '1' indicates the QAM channel 309 power value has dependencies with other QAM channels 310 as indicated in docsDrfGroupDependencyTable. 311 312 When 'qamDependency' BIT is set to '1', a set to the 313 power level PHY parameter of a QAM channels in a 314 dependency group (with docsDrfGroupDependencyType 315 set to docsDrfPhyParamSameValue), sets the same power 316 level to all QAM channels in the dependency group." 317 ::= { docsDrfDownstreamCapabilitiesEntry 3 } 318 319docsDrfDownstreamCapabModulation OBJECT-TYPE 320 SYNTAX BITS { 321 qamDependency(0), 322 qam64(1), 323 qam256(2) 324 } 325 MAX-ACCESS read-only 326 STATUS current 327 DESCRIPTION 328 "The QAM channel Modulation capabilities. 329 'qamDependency' BIT set to '1' indicates the QAM channel 330 modulation value has dependencies with other QAM channels 331 as indicated in docsDrfGroupDependencyTable. 332 333 'qam64' set to '1' indicates 64 QAM modulation support. 334 'qam256' set to '1' indicates 256 QAM modulation support. 335 336 When 'qamDependency' BIT is set to '1', a set to the 337 modulation PHY parameter of a QAM channels in a 338 dependency group (with docsDrfGroupDependencyType 339 set to docsDrfPhyParamSameValue), sets the same modulation 340 type to all QAM channels in the dependency group." 341 ::= { docsDrfDownstreamCapabilitiesEntry 4 } 342 343docsDrfDownstreamCapabInterleaver OBJECT-TYPE 344 SYNTAX BITS { 345 qamDependency(0), 346 taps8Increment16(1), 347 taps16Increment8(2), 348 taps32Increment4(3), 349 taps64Increment2(4), 350 taps128Increment1(5), 351 taps12increment17(6), 352 taps128increment2(7), 353 taps128increment3(8), 354 taps128increment4(9), 355 taps128increment5(10), 356 taps128increment6(11), 357 taps128increment7(12), 358 taps128increment8(13) 359 } 360 MAX-ACCESS read-only 361 STATUS current 362 DESCRIPTION 363 "The QAM channel Interleaver capabilities. 364 'qamDependency' BIT set to '1' indicates the QAM channel 365 interleave value has dependencies with other QAM channels 366 as indicated in docsDrfGroupDependencyTable. 367 368 'taps8Increment16' set to '1' indicates the support of 369 j = 8, i = 16 interleave. 370 371 'taps16Increment8' set to '1' indicates the support of 372 j = 16, i = 8 interleave. 373 374 'taps32Increment4' set to '1' indicates the support of 375 j = 32, i = 4 interleave. 376 377 'taps64Increment2' set to '1' indicates the support of 378 j = 64, i = 2 interleave. 379 380 'taps128Increment1' set to '1' indicates the support of 381 j = 128, i = 1 interleave. 382 383 'taps12increment17' set to '1' indicates the support of 384 j = 12, i = 17 interleave. 385 386 'taps128increment2' set to '1' indicates the support of 387 j = 128, i = 2 interleave. 388 389 'taps128increment3' set to '1' indicates the support of 390 j = 128, i = 3 interleave. 391 392 'taps128increment4' set to '1' indicates the support of 393 j = 128, i = 4 interleave. 394 395 'taps128increment5' set to '1' indicates the support of 396 j = 128, i = 5 interleave. 397 398 'taps128increment6' set to '1' indicates the support of 399 j = 128, i = 6 interleave. 400 401 'taps128increment7' set to '1' indicates the support of 402 j = 128, i = 7 interleave. 403 404 'taps128increment8' set to '1' indicates the support of 405 j = 128, i = 8 interleave. 406 407 When 'qamDependency' BIT is set to '1', a set to the 408 interleave PHY parameter of a QAM channels in a 409 dependency group (with docsDrfGroupDependencyType 410 set to docsDrfPhyParamSameValue), sets the same Interleave 411 value to all QAM channels in the dependency group." 412 ::= { docsDrfDownstreamCapabilitiesEntry 5 } 413 414docsDrfDownstreamCapabJ83Annex OBJECT-TYPE 415 SYNTAX BITS { 416 qamDependency(0), 417 annexA(1), 418 annexB(2), 419 annexC(3) 420 } 421 MAX-ACCESS read-only 422 STATUS current 423 DESCRIPTION 424 "The QAM channel J.83 Annex Capabilities. 425 'qamDependency' BIT set to '1' indicates the QAM channel 426 J.83 Annex value has dependencies with other QAM channels 427 as indicated in docsDrfGroupDependencyTable. 428 429 'annexA' set to '1' indicates J.83 Annex A support. 430 'annexB' set to '1' indicates J.83 Annex B support. 431 'annexC' set to '1' indicates J.83 Annex C support. 432 433 When 'qamDependency' BIT is set to '1', a set to the 434 J.83 Annex PHY parameter of a QAM channels in a 435 dependency group (with docsDrfGroupDependencyType 436 set to docsDrfPhyParamSameValue), sets the same J.83 Annex 437 value to all QAM channels in the dependency group." 438 ::= { docsDrfDownstreamCapabilitiesEntry 6 } 439 440docsDrfDownstreamCapabConcurrentServices OBJECT-TYPE 441 SYNTAX BITS { 442 qamDependency(0), 443 videoAndDocsis(1) 444 } 445 MAX-ACCESS read-only 446 STATUS current 447 DESCRIPTION 448 "The QAM channel Concurrent Services Capabilities. 449 'qamDependency' BIT set to '1' indicates the QAM channel 450 is part of a dependency group that supports concurrent 451 services mode as indicated in 452 docsDrfGroupDependencyTable. 453 454 'videoAndDocsis' BIT set to '1' indicates video transport 455 and DOCSIS transport can be supported simultaneously. 456 457 Video and DOCSIS transport service types are described in 458 docsDrfDownstreamCapabServicesTransport." 459 ::= { docsDrfDownstreamCapabilitiesEntry 7 } 460 461docsDrfDownstreamCapabServicesTransport OBJECT-TYPE 462 SYNTAX BITS { 463 qamDependency(0), 464 mpeg2OverIP(1), 465 dmpt(2), 466 psp(3) 467 } 468 MAX-ACCESS read-only 469 STATUS current 470 DESCRIPTION 471 "The QAM channel Services transports modes Capabilities. 472 473 'qamDependency' BIT set to '1' indicates the QAM channel 474 Service transport type has dependencies with other QAM 475 channels as indicated in 476 docsDrfGroupDependencyTable. 477 478 'mpeg2OverIP' set to '1' indicates video transports as 479 conventional VoD is supported (known as MPT mode, MPEG-2 480 transport). 481 'dmpt' set to 1 indicates DOCSIS MPT mode (D-MPT) support. 482 'psp' set to 1 indicates DOCSIS Packet Streaming Protocol 483 mode (PSP) support. 484 485 When 'qamDependency' BIT is set to '1', a request to set 486 a QAM channel to a service type in a dependency group 487 (with docsDrfGroupDependencyType set to 488 docsDrfPhyParamSameValue) may be rejected." 489 ::= { docsDrfDownstreamCapabilitiesEntry 8 } 490 491docsDrfDownstreamCapabMuting OBJECT-TYPE 492 SYNTAX BITS { 493 qamDependency(0) 494 } 495 MAX-ACCESS read-only 496 STATUS current 497 DESCRIPTION 498 "The QAM channel muting capabilities. 499 'qamDependency' BIT set to '1' indicates the QAM Mute 500 state has dependencies with other QAM channels as 501 indicated in docsDrfGroupDependencyTable. 502 503 When 'qamDependency' BIT is set to '1', a request to 504 mute a QAM channels in a dependency group (with 505 docsDrfGroupDependencyType set to 506 docsDrfPhyParamSameValue), sets all QAM channels in the 507 dependency group to mute." 508 ::= { docsDrfDownstreamCapabilitiesEntry 9 } 509 510-- --------------------------------------------------------------------- 511-- DRF Group Dependency of PHY parameters Definitions 512-- Defines the group of QAM channels that may be impacted for 513-- individual QAM channels PHY parameters changes. Extends ENTITY-MIB 514-- --------------------------------------------------------------------- 515 516docsDrfGroupDependencyTable OBJECT-TYPE 517 SYNTAX SEQUENCE OF DocsDrfGroupDependencyEntry 518 MAX-ACCESS not-accessible 519 STATUS current 520 DESCRIPTION 521 "This table describes the rules that identify groups of 522 QAM channels with PHY parameters dependencies. 523 A PHY parameter dependency group means that a set to 524 a QAM channel parameter may affect the value of 525 other QAM Channels in the group. 526 527 TSID is a broadcast term borrowed by the M-CMTS 528 architecture to represent a unique identifier of QAM 529 channels in the M-CMTS architecture. 530 531 TSID Group is the DEPI concept of a set of QAM channels 532 with a PHY parameter dependency. This module refers to 533 TSID group as a PHY dependency Group. 534 535 This table uses the ENTITY-MIB physical component structure 536 to allows the managed system to describe the QAM channels' 537 PHY parameters dependencies. A management entity can use 538 the information from this table to generate the DEPI TSID 539 Groups. 540 541 Examples of PHY dependencies could be usage of adjacent 542 frequencies, or QAM channels of RF ports restricted, or 543 same interleaver value, modulation and J.83 Annex value. 544 545 Additional details and rules to describe the PHY parameter 546 dependency is indicated in 547 docsDrfGroupDependencyType. 548 Vendors may extend via other MIB modules the usage of 549 docsDrfGroupDependencyType." 550 ::= { docsDrfObjects 4 } 551 552docsDrfGroupDependencyEntry OBJECT-TYPE 553 SYNTAX DocsDrfGroupDependencyEntry 554 MAX-ACCESS not-accessible 555 STATUS current 556 DESCRIPTION 557 "A conceptual row of this table. 558 559 QAM channels are modeled as PhysicalClass 'port' from 560 the ENTITY-MIB. 561 An QAM channel can be represented as part of an entity 562 MIB containment tree as follows: 563 chassis(device) 564 .container(Slot) 565 .module(field-replaceable-module) 566 .module ( Physical RF spigot) 567 . port (QAM channel) 568 569 PhysicalClass 'stack' is left optional and not included 570 as a reference or examples for this table. 571 572 Based on the hardware capabilities the Agent will create 573 entries in this table including the entPhysicalEntry of 574 the close element to the root (e.g., up to 'chassis' or 575 'stack') including the PHY parameter of the dependency 576 as part of the entry index 577 578 The Aggregation is then defined as all the QAM channels 579 (entity PhysicalClass = 'port') below the tree as 580 indicated in entyPhysicalContainsTable. 581 582 Logical or software dependencies of the QAM channels PHY 583 parameters in addition to the hardware dependency entries 584 can be present and MUST persist during system 585 re-initialization. The storage realization of hardware 586 dependent entries are 'permanent' or 'readOnly'. The 587 storage realization of logical dependency entries is 588 'nonVolatile'. 589 590 PHY parameter dependencies that are logically defined may 591 be present in this table but its configuration is outside 592 of the scope of this MIB Module, including the definition 593 of simulated Physical components such backplane types or 594 modules accomplish its logical grouping. 595 596 PHY parameters with no Physical entities associated in 597 this table indicate no PHY dependencies for certain groups 598 of QAM channels. 599 600 Administrative changes to the 601 docsDrfGroupDependencyPhyParamLock are preserved in 602 non-volatile memory upon system re-initialization. 603 604 Note that any change in the system due to the 605 insertion or removal or components will reset to factory 606 default the entries associated with those components. 607 608 An entry in this table is reflected in the MIB object 609 docsIfMExtDownstreamTSIDGroupPhyParamFlag for individual 610 QAM channels. 611 612 A recursive method to find the PHY dependency group of an 613 QAM channel A, PHY parameter X is as follows: 614 615 The parent tree of QAM channel A is recursively calculated 616 by navigating entyPhysicalContainsTable from bottom to top 617 Pi(P1..Pn) 618 619 The list Mj (M1..Mn) of 620 docsDrfGroupDependencyPhysicalIndex represents the 621 values from this table with PHY parameter 622 docsDrfGroupDependencyPhyParam X and/or 'all' 623 624 The list Qi (Q1..n) is the list of matches of Mi in Pi 625 626 Qi with the lower position in the entyPhysicalContainsTable 627 is selected Qy and My is the group criteria selected. 628 629 All QAM channels Bi below My are candidates for inclusion 630 in the dependency group. 631 632 Each Bi is verified as A for its own BPi parent tree to 633 verify that in effect My is the lowest denominator in Mi 634 BPi intersection to become part of the Dependency Group 635 of A." 636 INDEX { docsDrfGroupDependencyPhyParam, 637 docsDrfGroupDependencyPhysicalIndex } 638 ::= { docsDrfGroupDependencyTable 1 } 639 640DocsDrfGroupDependencyEntry ::= SEQUENCE 641 { 642 docsDrfGroupDependencyPhyParam INTEGER, 643 docsDrfGroupDependencyPhysicalIndex PhysicalIndexOrZero, 644 docsDrfGroupDependencyGroupID Unsigned32, 645 docsDrfGroupDependencyType AutonomousType 646 } 647 648docsDrfGroupDependencyPhyParam OBJECT-TYPE 649 SYNTAX INTEGER { 650 noDependencies(0), 651 all(1), 652 frequency(2), 653 bandwidth(3), 654 power(4), 655 modulation(5), 656 interleave(6), 657 annex(7), 658 symbolRate(8), 659 mute(9) 660 } 661 MAX-ACCESS not-accessible 662 STATUS current 663 DESCRIPTION 664 "This object represents the type of PHY parameter 665 that may have dependencies when setting an individual 666 object in the dependency group. 667 The value 'all' may be used as a wildcard to indicate 668 all PHY parameters have dependencies. The other 669 enumeration values are common QAM PHY parameters. 670 671 The opposite to 'all' is 'noDependencies', which indicates 672 no dependencies in PHY parameters, but is only used to 673 indicate no dependencies across all the device. Thus, 674 when used, 'noDependencies' is accompanied by 675 docsDrfGroupDependencyPhysicalIndex '0' as the only 676 entry in the table. 677 In this way it is clearly distinguished when a device 678 has dependencies instead of an empty table." 679 ::= { docsDrfGroupDependencyEntry 1 } 680 681docsDrfGroupDependencyPhysicalIndex OBJECT-TYPE 682 SYNTAX PhysicalIndexOrZero 683 MAX-ACCESS not-accessible 684 STATUS current 685 DESCRIPTION 686 "Indicates the physical element from where the PHY 687 parameter dependency for QAM channels is derived. 688 All the QAM channels elements under this Physical index 689 will belong to a dependency group of the specified PHY 690 parameter." 691 ::= { docsDrfGroupDependencyEntry 2 } 692 693docsDrfGroupDependencyGroupID OBJECT-TYPE 694 SYNTAX Unsigned32 (1..127) 695 MAX-ACCESS read-only 696 STATUS current 697 DESCRIPTION 698 "The internal ID assigned for the QAM channels in the 699 dependency group. 700 The value of this object is unique in the scope of the 701 PHY parameter being mapped." 702 ::= { docsDrfGroupDependencyEntry 3 } 703 704docsDrfGroupDependencyType OBJECT-TYPE 705 SYNTAX AutonomousType 706 MAX-ACCESS read-only 707 STATUS current 708 DESCRIPTION 709 "The description of the type of dependency associated 710 with this dependency group. 711 Basic type of dependencies are docsDrfPhyParamSameValue, 712 docsDrfPhyParamAdjacentValues, docsDrfPhyParamFrequencyRange. 713 Vendors may define their own rules and policies to describe 714 their implementation dependency definitions such as 715 RowPointers to table entries or OBJECT-IDENTITY clauses. 716 If the dependency is not described this object is set to 717 zeroDotZero, although the dependency does exist." 718 ::= { docsDrfGroupDependencyEntry 4 } 719 720-- --------------------------------------------------------------------- 721-- DRF Channel Block configuration 722-- Configuration and diagnostic of block Channels. 723-- This table is only for Channels Blocks Physical containments 724-- Other configuration parameters (PHY) applicable to all channes in a 725-- QAM Channel Block are set through the DS (QAM) channel interface and 726-- configuration objects 727-- --------------------------------------------------------------------- 728 729docsDrfChannelBlockTable OBJECT-TYPE 730 SYNTAX SEQUENCE OF DocsDrfChannelBlockEntry 731 MAX-ACCESS not-accessible 732 STATUS current 733 DESCRIPTION 734 "This table configure attributes of block channels and 735 Controls channel Block Tests. 736 A channel block is an ENTITY-MIB containment of 737 PhysicalClass 'module' that represent an RF connector." 738 ::= { docsDrfObjects 5 } 739 740docsDrfChannelBlockEntry OBJECT-TYPE 741 SYNTAX DocsDrfChannelBlockEntry 742 MAX-ACCESS not-accessible 743 STATUS current 744 DESCRIPTION 745 "The conceptual row of this table. 746 Entries in this table are created at system 747 Initialization for Block Channels compliant to DRFI 748 Specification. 749 Sets in entries of this table persist after system 750 initialization." 751 INDEX { docsDrfChannelBlockPhysicalIndex } 752 ::= { docsDrfChannelBlockTable 1 } 753 754DocsDrfChannelBlockEntry::= SEQUENCE 755 { 756 docsDrfChannelBlockPhysicalIndex PhysicalIndex, 757 docsDrfChannelBlockNumberChannels Unsigned32, 758 docsDrfChannelBlockCfgNumberChannels Unsigned32, 759 docsDrfChannelBlockMute TruthValue, 760 docsDrfChannelBlockTestType INTEGER, 761 docsDrfChannelBlockTestIfIndex InterfaceIndexOrZero 762 } 763 764docsDrfChannelBlockPhysicalIndex OBJECT-TYPE 765 SYNTAX PhysicalIndex 766 MAX-ACCESS not-accessible 767 STATUS current 768 DESCRIPTION 769 "The Physical Index of the QAM Channel Block." 770 ::= { docsDrfChannelBlockEntry 1 } 771 772docsDrfChannelBlockNumberChannels OBJECT-TYPE 773 SYNTAX Unsigned32 774 MAX-ACCESS read-only 775 STATUS current 776 DESCRIPTION 777 "The Number of QAM Channels N associated with this entry. 778 779 The value of this attribute corresponds to the number 780 of channels that can be transmitted from this block" 781 ::= { docsDrfChannelBlockEntry 2 } 782 783docsDrfChannelBlockCfgNumberChannels OBJECT-TYPE 784 SYNTAX Unsigned32 785 MAX-ACCESS read-write 786 STATUS current 787 DESCRIPTION 788 "The Number of QAM Channels N' to configure for the 789 QAM block. 790 791 This number corresponds to the number of channels that 792 are configured to be currently transmitted by the block. 793 794 The maximum number of channels per block follows the 795 consideration of maximum number of digital channels in 796 a headend described in the DRFI specification. 797 As a rule N' is valid if it is less than or equal to N. 798 In addition N minimal requirements consist of even 799 numbers and 1 (one QAM channel per Block Channel). Odd 800 number of QAM channels per Block Channel are optional 801 for implementation. 802 A Set to an invalid value or not supported value returns 803 Error 'wrongValue'." 804 ::= { docsDrfChannelBlockEntry 3 } 805 806 807docsDrfChannelBlockMute OBJECT-TYPE 808 SYNTAX TruthValue 809 MAX-ACCESS read-write 810 STATUS current 811 DESCRIPTION 812 "The Mute control object for the Block Channel 813 A set to this object to 'true' is reflected in 814 ifOperStatus set to 'down' of the QAM channels 815 associated to the block Channel. 816 The opposite, a set to this object to 'false', is not 817 necessarily reflected as ifOperStatus set to 'up' since 818 other interface conditions might prevent such status." 819 ::= { docsDrfChannelBlockEntry 4 } 820 821docsDrfChannelBlockTestType OBJECT-TYPE 822 SYNTAX INTEGER { 823 noTest(1), 824 offOthersNormal(2), 825 allOff(3), 826 onOthersOff(4), 827 cwOnOthersOff(5), 828 cwOnOthersNormal(6), 829 clockTest(7) 830 } 831 MAX-ACCESS read-only 832 STATUS current 833 DESCRIPTION 834 "A set of in-service and out-of-service test modes. 835 The value 'noTest'(1) is the normal condition after 836 reinitialization where the QAM channels are expected in 837 operation. 838 839 'noTest' 840 It is also used to take out of testing mode 841 a QAM channel within the block. 842 843 In-service tests modes: 844 'offOthersNormal' 845 It is the condition where the QAM Channel indicated in 846 docsDrfChannelBlockTestIfIndex has its carrier 847 suppressed and the other channels in the 848 Block Channel are operational. 849 'allOff' 850 All QAM channel carriers in the channel block are 851 Suppressed. 852 'onOthersOff' 853 It is the condition where the QAM channel indicated in 854 docsDrfChannelBlockTestIfIndex is in operation 855 and the other QAM channels in the channel Block have 856 their carriers suppressed. 857 858 Out-of-service test modes: 859 'cwOnOthersOff' 860 It is the condition where the QAM channel indicated in 861 docsDrfChannelBlockTestIfIndex transmits a 862 continuous wave (CW) while the other QAM 863 channels in the channel Block have their carriers 864 suppressed. 865 'cwOnOthersNormal' 866 It is the condition where the QAM channel indicated 867 in docsDrfChannelBlockTestIfIndex transmits a 868 continuous wave (CW) while the other QAM channels in 869 the channel Block are operational. 870 871 'clockTest' 872 It is the condition where the QAM channel indicated in 873 docsDrfChannelBlockTestIfIndex transmits a sequence 874 of alternating -1 and 1 symbols. 875 876 This object value does not persist after system 877 Reinitialization. 878 The value of this object is meaningless if 879 docsDrfChannelBlockTestIfIndex is set to zero." 880 ::= { docsDrfChannelBlockEntry 5 } 881 882docsDrfChannelBlockTestIfIndex OBJECT-TYPE 883 SYNTAX InterfaceIndexOrZero 884 MAX-ACCESS read-write 885 STATUS current 886 DESCRIPTION 887 "The ifIndex of the QAM channel to perform the QAM 888 channel test. 889 A Set to a value that does not correspond to a QAM 890 Channel within the Block channel returns error 891 'wrongValue'. 892 A set to zero stops a current test execution." 893 ::= { docsDrfChannelBlockEntry 6 } 894 895 896 897-- --------------------------------------------------------- 898-- Conformance definitions 899-- --------------------------------------------------------- 900 901docsDrfConformance OBJECT IDENTIFIER ::= { docsDrfMib 2 } 902docsDrfCompliances OBJECT IDENTIFIER ::= { docsDrfConformance 1 } 903docsDrfGroups OBJECT IDENTIFIER ::= { docsDrfConformance 2 } 904 905docsDrfDeviceCompliance MODULE-COMPLIANCE 906 STATUS current 907 DESCRIPTION 908 "The compliance statement DOCSIS DRFI compliant 909 devices." 910 911 MODULE -- this MODULE 912 913-- conditionally mandatory groups 914 915 MANDATORY-GROUPS { 916 docsDrfGroup 917 } 918::= { docsDrfCompliances 1} 919 920docsDrfCmtsCompliance MODULE-COMPLIANCE 921 STATUS current 922 DESCRIPTION 923 "The compliance statement for CMTS compliant 924 devices." 925 926MODULE -- this MODULE 927 928-- conditionally mandatory groups 929 930MANDATORY-GROUPS { 931 docsDrfGroup, 932 docsDrfCmtsGroup 933 } 934 935 ::= { docsDrfCompliances 2} 936 937docsDrfGroup OBJECT-GROUP 938 OBJECTS { 939 docsDrfDownstreamCapabFrequency, 940 docsDrfDownstreamCapabBandwidth, 941 docsDrfDownstreamCapabPower, 942 docsDrfDownstreamCapabModulation, 943 docsDrfDownstreamCapabInterleaver, 944 docsDrfDownstreamCapabJ83Annex, 945 docsDrfDownstreamCapabConcurrentServices, 946 docsDrfDownstreamCapabServicesTransport, 947 docsDrfDownstreamCapabMuting, 948 docsDrfGroupDependencyGroupID, 949 docsDrfGroupDependencyType, 950 docsDrfChannelBlockNumberChannels, 951 docsDrfChannelBlockCfgNumberChannels, 952 docsDrfChannelBlockMute, 953 docsDrfChannelBlockTestType, 954 docsDrfChannelBlockTestIfIndex 955 } 956 STATUS current 957 DESCRIPTION 958 "Group of objects implemented in M-CMTS compliant devices." 959 ::= { docsDrfGroups 1 } 960 961 962docsDrfCmtsGroup OBJECT-GROUP 963 OBJECTS { 964 docsDrfDownstreamPhyDependencies 965 } 966 STATUS current 967 DESCRIPTION 968 "Group of objects speficic for CMTS." 969 ::= { docsDrfGroups 2 } 970 971 972END 973 974 975