1-- ***************************************************************** 2-- CISCO-OPTICAL-IF-CROSS-CONNECT-MIB.my: Cisco optical interface 3-- cross-connect MIB file 4-- 5-- April 2001, Suresh Basavarajappa, Mickey Spiegel and Sameer Merchant 6-- 7-- Copyright (c) 2001, 2002 by cisco Systems, Inc. 8-- All rights reserved. 9-- 10-- ***************************************************************** 11 12CISCO-OPTICAL-IF-CROSS-CONNECT-MIB DEFINITIONS ::= BEGIN 13 14 15IMPORTS 16 MODULE-IDENTITY, OBJECT-TYPE, Integer32 FROM SNMPv2-SMI 17 RowStatus, TimeStamp, TEXTUAL-CONVENTION FROM SNMPv2-TC 18 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 19 ciscoExperiment FROM CISCO-SMI 20 InterfaceIndex, ifIndex FROM IF-MIB; 21 22 23ciscoOpticalIfCrossConnectMIB MODULE-IDENTITY 24 LAST-UPDATED "200203130000Z" -- 03/13/2002 25 ORGANIZATION "Cisco Systems, Inc." 26 CONTACT-INFO "Cisco Systems 27 Customer Service 28 29 Postal: 170 W Tasman Drive 30 San Jose, CA 95134 31 32 Tel: +1 800 553-NETS 33 34 E-mail: cs-dwdm@cisco.com" 35 DESCRIPTION 36 "This MIB module is used to create and monitor cross-connects 37 (horizontal relationships) between peer interfaces on the same 38 network element. Vertical relationships (e.g. between lambdas 39 and the optical fiber in which the lambdas are carried) are 40 represented in the ifStackTable from the IF-MIB. 41 42 This MIB can be used to model various types of cross-connects 43 between peer interfaces, including time-division (e.g. 44 SDH/SONET, PDH), wavelength (lambda), and spatial switching 45 (e.g. incoming port or fiber to outgoing port or fiber). 46 47 This MIB does not apply to cross-connects between packet flows 48 (e.g. packets in the same forwarding equivalence class at a 49 MPLS-capable switch or router) or cell flows (e.g. ATM Virtual 50 Path connections or ATM Virtual Channel connections), since 51 there are scalability issues in modeling each packet flow or 52 cell flow as a logical interface. 53 54 The switching element performing the cross-connect function can 55 be electrical (e.g. SDH/SONET switch) or optical (e.g. passive 56 optical add/drop multiplexer) 57 58 Cross-connects can be created through provisioning, 59 automatically by the network element, or dynamically by using 60 control protocols (e.g. GMPLS). 61 62 The cross-connect model includes support for pairs of 63 interfaces used to protect each other (e.g. SONET 1+1 64 Automatic Protection Switching). Cross-connects to protection 65 interfaces may be shown in this MIB module." 66 REVISION "200203130000Z" -- 03/13/2002 67 DESCRIPTION 68 "Added two objects, coifccCcL2HAttenuation and 69 coifccCcH2LAttenuation to coifccCrossConnectTable. These 70 new objects indicate signal attenuation on a given 71 cross-connect. 72 Changed coifccCcKind in coifccCrossConnectTable from 73 read-only to read-create." 74 REVISION "200104200000Z" -- 04/20/2001 75 DESCRIPTION 76 "Initial version of this MIB module." 77 ::= { ciscoExperiment 68 } 78 79 80coifccMIBObjects OBJECT IDENTIFIER ::= { 81 ciscoOpticalIfCrossConnectMIB 1 } 82coifccMIBConformance OBJECT IDENTIFIER ::= { 83 ciscoOpticalIfCrossConnectMIB 2 } 84 85 86-- Textual Conventions 87 88CoifccCrossConnectOperStatus ::= TEXTUAL-CONVENTION 89 STATUS current 90 DESCRIPTION 91 "The operational status in one direction of a cross-connect 92 between two interfaces. 93 94 The 'up' state indicates that the traffic flow is enabled on 95 the cross-connect. 96 97 The 'down' state indicates that the traffic flow is disabled 98 on the cross-connect, since it is either administratively 99 down or there is a fault that prevents it from going to the 100 'up' state. 101 102 The 'dormant' state indicates that the traffic flow is 103 disabled, but it is administratively up and there is no fault 104 that prevents it from going to the 'up' state. The 'dormant' 105 state is used when the interface from which the traffic flows 106 across the cross-connect is the standby interface of a 107 protected pair. The 'dormant' state may also apply when the 108 protection mode is other than 1+1 and the high interface is the 109 standby interface of a protected pair. 110 111 The 'unknown' state indicates that the state of the 112 cross-connect cannot be determined. 113 114 The state will be 'down' or 'unknown' if one or both of the 115 interfaces are 'down' or 'unknown', respectively." 116 SYNTAX INTEGER { 117 up(1), 118 down(2), 119 dormant(3), 120 unknown(4) 121 } 122 123 124-- MIB Object Definitions 125 126coifccInterface OBJECT IDENTIFIER ::= { coifccMIBObjects 1 } 127coifccCrossConnect OBJECT IDENTIFIER ::= { coifccMIBObjects 2 } 128 129 130-- coifcc Interface Group 131 132coifccInterfaceTable OBJECT-TYPE 133 SYNTAX SEQUENCE OF CoifccInterfaceEntry 134 MAX-ACCESS not-accessible 135 STATUS current 136 DESCRIPTION 137 "This table lists all interfaces that are cross-connected 138 to one or more other interfaces. The table is used to find 139 cross-connects that include a particular interface." 140 ::= { coifccInterface 1 } 141 142coifccInterfaceEntry OBJECT-TYPE 143 SYNTAX CoifccInterfaceEntry 144 MAX-ACCESS not-accessible 145 STATUS current 146 DESCRIPTION 147 "An entry is created only when an interface is cross-connected 148 to one or more other interfaces (i.e. when the associated 149 entries in the coifccCrossConnectTable have been created). 150 151 An entry is deleted when an interface is removed from a 152 cross-connect, or when the cross-connect that includes the 153 interface is deleted from the coifccCrossConnectTable." 154 INDEX { ifIndex } 155 ::= { coifccInterfaceTable 1 } 156 157CoifccInterfaceEntry ::= 158 SEQUENCE { 159 coifccIfCrossConnectIdentifier Integer32 160 } 161 162coifccIfCrossConnectIdentifier OBJECT-TYPE 163 SYNTAX Integer32 (1..2147483547) 164 MAX-ACCESS read-only 165 STATUS current 166 DESCRIPTION 167 "The value of coifccCcIndex used in the coifccCrossConnectTable 168 to identify a cross-connect that includes this interface. Each 169 interface included in that cross-connect has an entry in this 170 table with the same value of this object, in addition to the 171 entries in the coifccCrossConnectTable with this value of 172 coifccCcIndex." 173 ::= { coifccInterfaceEntry 1 } 174 175 176-- coifcc Cross-Connect Group 177 178 179coifccCcIndexNext OBJECT-TYPE 180 SYNTAX Integer32 (0..2147483647) 181 MAX-ACCESS read-only 182 STATUS current 183 DESCRIPTION 184 "This object contains an appropriate value to be used for 185 coifccCcIndex when creating entries in the 186 coifccCrossConnectTable. The value 0 indicates that no 187 unassigned entries are available. To obtain the coifccCcIndex 188 value for a new entry, the manager issues a management protocol 189 retrieval operation to obtain the current value of this object. 190 The agent will modify the value to the next unassigned index, 191 when a new row is created in coifccCrossConnectTable with 192 coifccCcIndex value equal to the current value of this object. 193 After deletion of a row in coifccCrossConnectTable the agent 194 will determine through its local policy when its index value 195 will be made available for reuse." 196 ::= { coifccCrossConnect 1 } 197 198coifccCcLastChange OBJECT-TYPE 199 SYNTAX TimeStamp 200 MAX-ACCESS read-only 201 STATUS current 202 DESCRIPTION 203 "The value of sysUpTime at the time of the last 204 creation, deletion or modification of an entry 205 in the coifccCrossConnectTable. 206 If the coifccCrossConnectTable entries has been unchanged 207 since the last re-initialization of the local network 208 management subsystem, then this object contains a zero value." 209 ::= { coifccCrossConnect 2 } 210 211coifccCrossConnectTable OBJECT-TYPE 212 SYNTAX SEQUENCE OF CoifccCrossConnectEntry 213 MAX-ACCESS not-accessible 214 STATUS current 215 DESCRIPTION 216 "This table contains configuration and state information of 217 point-to-point and point-to-multipoint interface 218 cross-connects. 219 220 Each entry in the table models two bi-directional interfaces on 221 opposite sides of a bi-directional cross-connect. 222 223 For a point-to-point cross-connect, there can be up to four 224 entries in the table with the same value of coifccCcIndex, due 225 to the presence of protection interfaces. 226 All four entries are associated with each other due to 227 APS configuration (for now, this would be done through 228 the CISCO-APS-MIB). If both sides A and B are configured 229 for 1+1 APS protection, and a cross-connect between 230 interfaces A and B is created, then the following 231 cross-connect entries will be present: 232 233 The cross-connect with coifccCcKind value 'provisioned' is the 234 one that is created through cross-connect configuration and the 235 cross-connects with coifccCcKind value 'protection' are those 236 that are created automatically due to APS configuration. 237 238 Low interface High interface coifccCcKind 239 240 A B provisioned 241 A B' protection 242 A' B protection 243 A' B' protection 244 245 When the cross-connect between A and B is deleted, all four 246 cross-connect entries will disappear. 247 248 Each side of the point-to-point cross-connect can have up to 249 two interfaces, for example when SONET 1+1 Automatic 250 Protection Switching (APS) is used. Any one of the four 251 entries of a point-to-point cross-connect can be created, 252 and the remaining three entries will be created 253 automatically. However only the 'provisioned' entry can be 254 explicitly deleted, which also causes the corresponding 255 'protection' entries to be deleted. Note that use of the 256 word 'protection' is different from its usage in SONET 1+1 APS. 257 In particular, there is no requirement that the 'provisioned' 258 cross-connect must be between the SONET 'working' interfaces. 259 260 261 A point-to-multipoint connection consists of one root and 262 many leaves. Copies of the traffic received at the root 263 interface are transmitted out each of the leaf interfaces. 264 265 For a point-to-multipoint cross-connect with N leafs, 266 the manager creates N 'provisioned' entries in this table. 267 Where N is determined by the manager based on some application. 268 In the presence of APS configuration, the same 269 point-to-multipoint (N leafs) cross-connect, in addition 270 to having N 'provisioned' entries in this table, can have upto 271 an additional 3N 'protection' entries automatically configured. 272 273 The terms low and high are chosen to represent numerical 274 ordering of the two interfaces associated with a cross-connect. 275 That is, the interface with the lower value of ifIndex is 276 termed 'low', while the other interface associated with the 277 cross-connect is termed 'high'. This terminology is used to 278 provide directional information; for example, the 279 coifccCcL2HOperStatus applies to the low->high direction, and 280 coifccCcH2LOperStatus applies to the high->low direction." 281 ::= { coifccCrossConnect 3 } 282 283coifccCrossConnectEntry OBJECT-TYPE 284 SYNTAX CoifccCrossConnectEntry 285 MAX-ACCESS not-accessible 286 STATUS current 287 DESCRIPTION 288 "This entry is used to model two bi-directional cross-connected 289 interfaces. 290 291 Cross-connects can be created through provisioning, 292 automatically by the network element, dynamically by using 293 control protocols (e.g. GMPLS), or due to the presence of 294 protection interfaces. 295 296 When creating an entry through provisioning, the following 297 procedures are used to cross-connect two interfaces: 298 (1) The manager obtains a unique coifccCcIndex by reading the 299 coifccCcIndexNext object. 300 (2) Next, the manager creates a set of one or more rows in the 301 Cross Connect Table. For a point-to-point connection, one 302 row is created by the manager. For a point-to-multipoint 303 connection, one row is created for each leaf to an 304 unprotected interface, or one row is created for each leaf 305 to a pair of protected interfaces. Additional rows for 306 protection interfaces are created automatically by the 307 agent. Each row is indexed by the ifIndex values of the 308 two interfaces at the ends of that cross-connection. This 309 set of rows is identified by a single value of 310 coifccCcIndex. As each row is created, the agent checks if 311 the requested topology is supported and also checks for 312 internal errors in building the cross-connect. The 313 coifccIfCrossConnectIdentifier values in the corresponding 314 coifccInterfaceTable rows are filled in by the agent at 315 this point. The traffic flow is turned on when the manager 316 sets coifccCcRowStatus to active(1) or createAndGo(4). 317 318 A cross-connect identified by a particular value of 319 coifccCcIndex is released by setting coifccCcRowStatus of all 320 rows identified by this value of coifccCcIndex, other than the 321 rows with a coifccCcKind value of 'protection', to destroy(6). 322 The agent may release associated resources, and the 323 coifccIfCrossConnectIdentifier values in the corresponding 324 coifccInterfaceTable are removed. Note that a situation when 325 only a subset of the associated rows are deleted corresponds to 326 a topology change. 327 328 At the discretion of the agent, a cross-connect may be 329 reconfigured by adding and/or deleting leafs to/from the 330 topology as per the cross-connect establishment/retirement 331 guidelines described below. 332 333 Each leaf is added by creating a row with the same value of 334 coifccCcIndex in this table. Each leaf is deleted by deleting 335 a row with the same value of coifccCcIndex in the table. To 336 delete an entire point-to-multipoint connection, all entries 337 with the same coifccCcIndex value must be deleted." 338 INDEX { coifccCcIndex, 339 coifccCcLowIfIndex, 340 coifccCcHighIfIndex } 341 ::= { coifccCrossConnectTable 1 } 342 343CoifccCrossConnectEntry ::= 344 SEQUENCE { 345 coifccCcIndex Integer32, 346 coifccCcLowIfIndex InterfaceIndex, 347 coifccCcHighIfIndex InterfaceIndex, 348 coifccCcSwitchType INTEGER, 349 coifccCcKind INTEGER, 350 coifccCcCreationTime TimeStamp, 351 coifccCcL2HOperStatus CoifccCrossConnectOperStatus, 352 coifccCcH2LOperStatus CoifccCrossConnectOperStatus, 353 coifccCcL2HLastChange TimeStamp, 354 coifccCcH2LLastChange TimeStamp, 355 coifccCcRowStatus RowStatus, 356 coifccCcL2HAttenuation Integer32, 357 coifccCcH2LAttenuation Integer32 358 } 359 360coifccCcIndex OBJECT-TYPE 361 SYNTAX Integer32 (1..2147483647) 362 MAX-ACCESS not-accessible 363 STATUS current 364 DESCRIPTION 365 "A unique value used to identify this cross-connect. For each 366 interface associated with this cross-connect, the agent reports 367 this cross-connect index value in the 368 coifccIfCrossConnectIdentifier object of the corresponding 369 coifccInterfaceTable entry. 370 When the value of this index is equal to the current value 371 of coifccCcIndexNext, the agent will modify the value of 372 coifccCcIndexNext to the next unassigned index." 373 ::= { coifccCrossConnectEntry 1 } 374 375coifccCcLowIfIndex OBJECT-TYPE 376 SYNTAX InterfaceIndex 377 MAX-ACCESS not-accessible 378 STATUS current 379 DESCRIPTION 380 "The value of this object is equal to MIB II's ifIndex value of 381 the interface for this cross-connect. The term low implies 382 that this interface has the numerically lower ifIndex value 383 than the other interface identified in the same 384 coifccCrossConnectEntry." 385 ::= { coifccCrossConnectEntry 2 } 386 387coifccCcHighIfIndex OBJECT-TYPE 388 SYNTAX InterfaceIndex 389 MAX-ACCESS not-accessible 390 STATUS current 391 DESCRIPTION 392 "The value of this object is equal to MIB II's ifIndex value of 393 the interface for this cross-connect. The term high implies 394 that this interface has the numerically higher ifIndex value 395 than the other interface identified in the same 396 coifccCrossConnectEntry." 397 ::= { coifccCrossConnectEntry 3 } 398 399coifccCcSwitchType OBJECT-TYPE 400 SYNTAX INTEGER { 401 unknown(1), 402 electricalCrossConnect(2), 403 opticalCrossConnect(3), 404 autoSelect(4) 405 } 406 MAX-ACCESS read-create 407 STATUS current 408 DESCRIPTION 409 "This object specifies the type of switching element used to 410 implement this cross-connect. 411 412 The value 'opticalCrossConnect' applies only when there is no 413 optical-to-electrical conversion performed to implement the 414 cross-connect. 415 416 The value 'autoSelect' indicates the agent should figure out 417 the switch type to use. The value 'autoSelect' is a write-only 418 value and should never be returned when this object is read. 419 420 If the manager activates the row before setting this object, 421 the value may be chosen by the agent." 422 DEFVAL { autoSelect } 423 ::= { coifccCrossConnectEntry 4 } 424 425coifccCcKind OBJECT-TYPE 426 SYNTAX INTEGER { 427 provisioned(1), 428 automatic(2), 429 dynamic(3), 430 protection(4), 431 other(5) 432 } 433 MAX-ACCESS read-create 434 STATUS current 435 DESCRIPTION 436 "The type of call control used to establish a cross-connect. 437 438 If no value of this object is provided when a row is activated 439 through SNMP, then the value 'provisioned' is assigned by the 440 agent. 441 442 For point-to-point cross-connects, the only sets allowed on 443 this object are during initial row creation, and to change the 444 value of this object from 'protection' to 'provisioned', which 445 automatically changes the coifccCcKind value of the 446 'provisioned' cross-connect with the same coifccCcIndex value 447 to 'protection'. A change from 'protection' to 'provisioned' 448 is allowed when coifccCcRowStatus is 'active'. 449 450 The use is as follows: 451 provisioned(1) 452 Provisioned by the user or by a management system 453 using the Command Line Interface, SNMP, or other 454 means of management access to the network element. 455 automatic(2) 456 Created automatically by the network element, without 457 user, management, or control plane intervention. In 458 particular, this is used to represent fixed interface 459 cross-connects due to the presence of entities such as 460 optical add/drop multiplexers. 461 dynamic(3) 462 Created by request from a control plane (e.g. from 463 GMPLS signalling). 464 protection(4) 465 Created to include the second of a pair of protected 466 interfaces in a cross-connect, when a cross-connect 467 entry for the first interface in the pair is being 468 created. Such an entry cannot be deleted directly. 469 It is deleted when the cross-connect entry containing 470 the other interface(s) of the protected pair(s) is 471 deleted." 472 ::= { coifccCrossConnectEntry 5 } 473 474coifccCcCreationTime OBJECT-TYPE 475 SYNTAX TimeStamp 476 MAX-ACCESS read-only 477 STATUS current 478 DESCRIPTION 479 "The value of MIB II's sysUpTime object at the time this 480 bi-directional cross-connect was created. If the current state 481 was entered prior to the last re-initialization of the agent 482 then this object contains a zero value." 483 ::= { coifccCrossConnectEntry 6 } 484 485coifccCcL2HOperStatus OBJECT-TYPE 486 SYNTAX CoifccCrossConnectOperStatus 487 MAX-ACCESS read-only 488 STATUS current 489 DESCRIPTION 490 "The operational status of the cross-connect in the direction 491 from the interface that has the numerically lower ifIndex 492 value, to the interface that has the numerically higher ifIndex 493 value." 494 ::= { coifccCrossConnectEntry 7 } 495 496coifccCcH2LOperStatus OBJECT-TYPE 497 SYNTAX CoifccCrossConnectOperStatus 498 MAX-ACCESS read-only 499 STATUS current 500 DESCRIPTION 501 "The operational status of the cross-connect in the direction 502 from the interface that has the numerically higher ifIndex 503 value, to the interface that has the numerically lower ifIndex 504 value." 505 ::= { coifccCrossConnectEntry 8 } 506 507coifccCcL2HLastChange OBJECT-TYPE 508 SYNTAX TimeStamp 509 MAX-ACCESS read-only 510 STATUS current 511 DESCRIPTION 512 "The value of MIB II's sysUpTime at the time this cross-connect 513 entered its current operational state in the low to high 514 direction. If the current state was entered prior to the last 515 re-initialization of the agent then this object contains a zero 516 value." 517 ::= { coifccCrossConnectEntry 9 } 518 519coifccCcH2LLastChange OBJECT-TYPE 520 SYNTAX TimeStamp 521 MAX-ACCESS read-only 522 STATUS current 523 DESCRIPTION 524 "The value of MIB II's sysUpTime at the time this cross-connect 525 entered its current operational state in the high to low 526 direction. If the current state was entered prior to the last 527 re-initialization of the agent then this object contains a zero 528 value." 529 ::= { coifccCrossConnectEntry 10 } 530 531coifccCcRowStatus OBJECT-TYPE 532 SYNTAX RowStatus 533 MAX-ACCESS read-create 534 STATUS current 535 DESCRIPTION 536 "The status of this entry in the coifccCrossConnectTable. This 537 object is used to create a cross-connect or to modify or delete 538 an existing cross-connect. 539 540 Write access does not apply to entries with coifccCcKind values 541 of 'automatic' or 'protection'. 542 543 Entries with a coifccCcKind value of 'protection' cannot be 544 deleted using this object. Such an entry is deleted when the 545 cross-connect entry containing the other interface(s) of the 546 protected pair(s) is deleted. 547 548 For entries with coifccCcKind value of 'dynamic', the only 549 value that can be set is 'destroy'." 550 ::= { coifccCrossConnectEntry 11 } 551 552coifccCcL2HAttenuation OBJECT-TYPE 553 SYNTAX Integer32 (-400..0) 554 UNITS "1/10ths of dB" 555 MAX-ACCESS read-create 556 STATUS current 557 DESCRIPTION 558 "The value of this object indicates optical signal attenuation 559 due to connectors, optical wavelength filters, optical 560 switches, and other optical components, in the direction from 561 the interface that has the numerically lower ifIndex value, to 562 the interface that has the numerically higher ifIndex value. 563 564 Example: The value -25 represents an attenuation of -2.5 dB. 565 566 This object applies only if the value of coifccCcSwitchType is 567 'opticalCrossConnect'. For other values of coifccCcSwitchType, 568 this object will return a value of '0'." 569 ::= { coifccCrossConnectEntry 12 } 570 571coifccCcH2LAttenuation OBJECT-TYPE 572 SYNTAX Integer32 (-400..0) 573 UNITS "1/10ths of dB" 574 MAX-ACCESS read-create 575 STATUS current 576 DESCRIPTION 577 "The value of this object indicates optical signal attenuation 578 due to connectors, optical wavelength filters, optical 579 switches, and other optical components, in the direction from 580 the interface that has the numerically higher ifIndex value, to 581 the interface that has the numerically lower ifIndex value. 582 583 Example: The value -25 represents an attenuation of -2.5 dB. 584 585 This object applies only if the value of coifccCcSwitchType is 586 'opticalCrossConnect'. For other values of coifccCcSwitchType, 587 this object will return a value of '0'." 588 ::= { coifccCrossConnectEntry 13 } 589 590 591-- Cross-Connect Conformance 592 593coifccMIBCompliances OBJECT IDENTIFIER ::= { coifccMIBConformance 1 } 594coifccMIBGroups OBJECT IDENTIFIER ::= { coifccMIBConformance 2 } 595 596 597-- Compliance 598 599coifccMIBCompliance MODULE-COMPLIANCE 600 STATUS deprecated 601 DESCRIPTION 602 "The compliance statement for entities which implement 603 the Cisco Interface Cross-connect MIB" 604 MODULE -- this module 605 MANDATORY-GROUPS { coifccInterfaceGroup, 606 coifccCrossConnectGroup } 607 608 OBJECT coifccCcSwitchType 609 MIN-ACCESS read-only 610 DESCRIPTION 611 "Write access is not required." 612 613 ::= { coifccMIBCompliances 1 } 614 615coifccMIBComplianceRev1 MODULE-COMPLIANCE 616 STATUS current 617 DESCRIPTION 618 "The compliance statement for entities which implement 619 the Cisco Interface Cross-connect MIB" 620 MODULE -- this module 621 MANDATORY-GROUPS { coifccInterfaceGroup, 622 coifccCrossConnectGroup } 623 624 OBJECT coifccCcSwitchType 625 MIN-ACCESS read-only 626 DESCRIPTION 627 "Write access is not required." 628 629 OBJECT coifccCcKind 630 MIN-ACCESS read-only 631 DESCRIPTION 632 "Write access is not required." 633 634 OBJECT coifccCcRowStatus 635 MIN-ACCESS read-only 636 DESCRIPTION 637 "Write access does not apply when the only supported value 638 of coifccCcKind is 'automatic', or when the only two 639 supported values are 'automatic' and 'protection'." 640 641 GROUP coifccAttenuationGroup 642 DESCRIPTION 643 "May be implemented by elements providing optical 644 cross-connects." 645 646 OBJECT coifccCcL2HAttenuation 647 MIN-ACCESS read-only 648 DESCRIPTION 649 "Write access is not required." 650 651 OBJECT coifccCcH2LAttenuation 652 MIN-ACCESS read-only 653 DESCRIPTION 654 "Write access is not required." 655 656 ::= { coifccMIBCompliances 2 } 657 658-- Units of Conformance 659 660coifccInterfaceGroup OBJECT-GROUP 661 OBJECTS { coifccIfCrossConnectIdentifier 662 } 663 STATUS current 664 DESCRIPTION 665 "Object needed to implement Interfaces with 666 Cross-connects." 667 ::= { coifccMIBGroups 1 } 668 669coifccCrossConnectGroup OBJECT-GROUP 670 OBJECTS { coifccCcIndexNext, 671 coifccCcLastChange, 672 coifccCcSwitchType, 673 coifccCcKind, 674 coifccCcCreationTime, 675 coifccCcL2HOperStatus, 676 coifccCcH2LOperStatus, 677 coifccCcL2HLastChange, 678 coifccCcH2LLastChange, 679 coifccCcRowStatus 680 } 681 STATUS current 682 DESCRIPTION 683 "Collection of objects needed to implement 684 interface Cross-connects." 685 ::= { coifccMIBGroups 2 } 686 687coifccAttenuationGroup OBJECT-GROUP 688 OBJECTS { coifccCcL2HAttenuation, 689 coifccCcH2LAttenuation 690 } 691 STATUS current 692 DESCRIPTION 693 "Collection of objects used to indicate attenuation 694 across optical cross-connects." 695 ::= { coifccMIBGroups 3 } 696 697-- End of CISCO-OPTICAL-IF-CROSS-CONNECT-MIB 698 699END 700