1-- ***************************************************************** 2-- CISCO-CIPCSNA-MIB - CIP Channel SNA MIB. 3-- 4-- April 1995, Mike Otto 5-- 6-- Copyright (c) 1995-1996, 1998 by cisco Systems, Inc. 7-- All rights reserved. 8-- ***************************************************************** 9-- 10 11CISCO-CIPCSNA-MIB DEFINITIONS ::= BEGIN 12 13IMPORTS 14 MODULE-IDENTITY, OBJECT-TYPE, 15 NOTIFICATION-TYPE, 16 Counter32, Counter64, Integer32, Gauge32 17 FROM SNMPv2-SMI 18 19 MODULE-COMPLIANCE, OBJECT-GROUP 20 FROM SNMPv2-CONF 21 22 RowStatus, TEXTUAL-CONVENTION 23 FROM SNMPv2-TC 24 25 ifIndex 26 FROM RFC1213-MIB 27 28 ciscoMgmt 29 FROM CISCO-SMI 30 31 cipCardEntryIndex, cipCardDtrBrdIndex, cipCardSubChannelIndex 32 FROM CISCO-CHANNEL-MIB 33 34 llcPortVirtualIndex, llcSapNumber 35 FROM CISCO-SNA-LLC-MIB; 36 37ciscoCipCsnaMIB MODULE-IDENTITY 38 LAST-UPDATED "9508210000Z" 39 ORGANIZATION "cisco IBM engineering Working Group" 40 CONTACT-INFO 41 " Cisco Systems 42 Customer Service 43 44 Postal: 170 W Tasman Drive 45 San Jose, CA 95134 46 USA 47 48 Tel: +1 800 553-NETS 49 50 E-mail: cs-snmp@cisco.com" 51 DESCRIPTION 52 "This is the Management Information Base (MIB) 53 module for objects used to manage the cisco Systems 54 Network Architecture (SNA) support on Cisco Mainframe 55 Channel Connection (CMCC) cards, also called the 56 CIP-SNA feature. 57 58 --------------------------------------------------- 59 | Acronym Definitions: | 60 | CMCC = Cisco Mainframe Channel Connection | 61 | CIP = Channel Interface Processor | 62 | CTA = Channel Transport Architecture | 63 | SNA = Systems Network Architecture | 64 | CIP-SNA = CNA = CSNA = SNA Support on | 65 | a CMCC card | 66 --------------------------------------------------- 67 68 69 This mib consists of the following tables: 70 1) CSNA Administration 71 2) CSNA Operational 72 3) CSNA Statistics 73 4) Max Sessions Administration 74 5) Max Sessions Operational 75 8) LLC2/CSNA Connection mapping 76 77The following is a set of IBM channel terminology: 78 1) The Channel Subsystem is the way a host performs 79 I/O. 80 2) A Channel Path is the path to the Channel Control 81 Unit. In the Cisco CMCC environment, this is the 82 path of the channel to the physical router, itself. 83 This path is needed because the physical channel may 84 be directed (switched) through a device called 85 an ESCON director. The path defined from the 86 host to the Control Unit can be different than 87 the path from the Control Unit to the host. 88 For an in-depth definition of how this number 89 is derived, see the cipCardCsnaAdminPath object. 90 3) A Sub-Channel and Device are exactly the same 91 thing. The term Sub-Channel was introduced 92 for ESCON (IBM's serial fiber optic) channel 93 interface. Previously the term Device was used, 94 and it mapped directly to hardware (in most 95 situations) via a Parallel Channel Adapter 96 (PCA). Another name for PCA is Bus & Tag. In 97 the Cisco CMCC environment, the Sub-Channel is 98 controlled by the Channel Systems Network 99 Architecture (CSNA) feature. For an 100 in-depth definition of how this number is 101 derived, see the cipCardCsnaAdminDevice object. 102 NOTE: The terminology of Sub-Channel and 103 Sub-Channel Index are two completely different 104 entities! See below for Sub-Channel Index. 105 4) An I/O Device is the entity that is addressed by 106 the combination of Sub-Channel and Device. This 107 directly maps to the cipCardCsnaAdminTable. 108 NOTE: The Channel Systems Network Architecture 109 (CSNA) feature may have multiple 110 sub-channels/devices defined for its control. 111 Also NOTE: That we have defined an object with 112 the name cipCardSubChannelIndex and this object 113 is the two hex octet Channel Path values concatenated 114 with the second hex (the first octet is not used) 115 octet Device value and then converted to an 116 INTEGER (Unsigned). 117 The exact description is taken from the 118 CISCO-CHANNEL-MIB 119 cipCardSubChannelIndex OBJECT-TYPE 120 SYNTAX INTEGER 121 MAX-ACCESS read-only 122 STATUS current 123 DESCRIPTION 124 This indicates which subchannel is being referenced 125 for a particular daughter board on a CMCC card. 126 This value is constructed as follows: 127 path * 256 + device 128 Path and device are the values in 129 CipCardClawConfigTable. 130 ::= { cipCardSubChannelEntry 1 } 131 In this mib, the last two lines change to 132 Path and device are the values in the 133 cipCardCsnaAdminTable. 134 5) XCA Major Nodes. The XCA major node binds the 135 Channel Path (from the hosts perspective)/Sub- 136 Channel number (i.e. I/O Device), to a CIP internal 137 LAN Adapter of a specific type with a unique SAP 138 Number. That same I/O Device can also be 139 bound to the same LAN Adapter of the same 140 type with a different SAP, and/or the same I/O 141 Device can be bound to any other Adapter and 142 any unique SAP on that Adapter. The binding 143 allows the I/O Device to talk to the Adapter. 144 The SAP allows multiple connections to the 145 same Adapter. 146 147The following is an example of the hardware with 148the above names showing there locations. 149 150 |----- Channel Path ------| 151 Eg. 150F and 190A ================= 152 ========== | Router A with | 153 | HOST 1 |--- ============ | Control Unit | 154 ========== |__15| ESCON |_____| & Virtual | 155 ____| Director | | I/O Devices | 156 ========== | 19============ | via the CSNA | 157 | HOST 2 |--- -----| feature. | 158 ========== | ================= 159 | 160 Eg. 0100, | 161 ========== Direct Connection | 162 | HOST 3 |--------------------- 163 ========== 164 165 166The following example configuration of a router that 167shows the entities managed by the CIPCSNA MIB. 168 169 ------------ ------------ 170 | HOST 1 | | HOST 3 | 171 | & HOST 2 | | | 172 ------------ ------------ 173 || || Router A 174 ----------------------------------------- 175 | ------------------------------------- | 176 | | ----------- --------- | | 177 | | | ESCON 0 | | PCA 1 | | | 178 | | ----------- --------- | | 179 | | | | 180 | | ---------------------- | | 181 | | | CSNA Feature | | | 182 | | | Control Unit F & A | | | 183 | | | for ESCON 0 | | | 184 | | ---------------------- | | 185 | | | | 186 | | CMCC CARD 6 | | 187 | ------------------------------------- | 188 | | 189 ----------------------------------------- 190 191The first table is the Cisco Mainframe Channel Connection 192 (CMCC) Channel Systems Network Architecture support (CSNA) 193 Administration table. Each entry created in this table 194 will create an I/O Device that can be attached to the 195 host (via a host VTAM XCA Major Node command). 196 The indices of the table are: 197 * The CMCC Card Slot Index 198 * The Daughter Board Index 199 * The Sub-Channel Index 200 NOTE: In the above discussion, this value is defined 201 to be a combination of the Channel Path and 202 Device (really the address of an I/O Device). 203 The fields included in this table represent: 204 * Channel Path 205 * Device 206 NOTE: The two fields above are the same values as 207 the above Sub-Channel Index. 208 * The configured maximum block delay time 209 * The configured suggested block delay length 210 * The configured maximum block length 211 NOTE: The channel uses data blocks that accumulate 212 data before it sends it to the host. 213 * The row control variable 214 In the example above, three entries would be 215 defined. 216 The first entry would be: 217 - CMCC Card Slot 0 218 - CMCC Daughter Board 0 219 - Sub-Channel Index of 0x150F00 or 1380096 220 - Channel Path of 0x150F or 5391 221 - Device of 00 222 - rest can be defaulted 223 The second entry would be: 224 - CMCC Card Slot 0 225 - CMCC Daughter Board 0 226 - Sub-Channel Index of 0x190A00 or 1640960 227 - Channel Path of 0x190A or 6410 228 - Device of 00 229 - rest can be defaulted 230 The third entry would be: 231 - CMCC Card Slot 0 232 - CMCC Daughter Board 1 233 - Sub-Channel Index of 0x010000 or 65536 234 - Channel Path of 0x0100 or 256 235 - Device of 00 236 - rest can be defaulted 237 238The next table is an augmented table to the first table. 239 It keeps the operational status of the first table. 240 The indices are the same as the first table. 241 The fields included in this table represent: 242 * The current operational state of a this table entry 243 * The current operational maximum block delay time 244 * The current operational suggested block delay length 245 * The current operational maximum block length 246 In the example above, three entries would be 247 defined. 248 The first entry would be: 249 - CMCCC Card Slot 0 250 - CMCC Daughter Board 0 251 - Sub-Channel Index of 0x150F00 or 1380096 252 - rest will be determined by the agent 253 The second entry would be: 254 - CMCC Card Slot 0 255 - CIP Daughter Board 0 256 - Sub-Channel Index of 0x190A00 or 1640960 257 - rest will be determined by the agent 258 The second entry would be: 259 - CMCC Card Slot 0 260 - CMCC Daughter Board 1 261 - Sub-Channel Index of 0x010000 or 65536 262 - rest will be determined by the agent 263 264The next table is an augmented table to the first table. 265 It keeps the statistics for the Channel Systems Network 266 Architecture (CSNA) counters. 267 The indices are the same as the first table. 268 The fields included in this table represent: 269 * Blocks transmitted 270 * Blocks received 271 * Bytes transmitted 272 * Bytes received 273 * Blocks transmitted by maximum block delay time 274 * Blocks transmitted by the suggested block delay length 275 * Blocks transmitted by maximum block length 276 In the example above, three entries would be 277 defined. 278 The first entry would be: 279 - CMCC Card Slot 0 280 - CMCC Daughter Board 0 281 - Sub-Channel Index of 0x150F00 or 1380096 282 - rest will be determined by the agent 283 The second entry would be: 284 - CMCC Card Slot 0 285 - CMCC Daughter Board 0 286 - Sub-Channel Index of 0x190A00 or 1640960 287 - rest will be determined by the agent 288 The second entry would be: 289 - CMCC Card Slot 0 290 - CMCC Daughter Board 1 291 - Sub-Channel Index of 0x010000 or 65536 292 - rest will be determined by the agent 293 294The next table is maximum sessions Admin table. 295 The one entry in this table defines the configured 296 maximum sessions supported on the whole CMCC card. 297 The one index is: 298 * The ifIndex addresses the virtual CMCC interface 299 The one field in this table represents: 300 * The maximum sessions for this card 301 In the example above, the one entry would be defined. 302 - ifIndex is created by the agent 303 - the maximum sessions would be within the 304 range 305 306The next table is the operational maximum sessions table. 307 This table is an augmented table to the maximum sessions 308 Admin table. The entries in this table display the 309 current maximum sessions supported on the whole CMCC card. 310 The indices are the same as the maximum sessions Admin 311 table. 312 The one field in this table represents: 313 * The current operational maximum sessions for 314 this card 315 In the example above, the one entry would be defined. 316 - ifIndex is created by the agent 317 - the maximum sessions would be within the 318 range 319 320The next table is the statistical maximum sessions table. 321 This table is an augmented table to the maximum sessions 322 Admin table. The entries in this table displays the 323 current high water maximum sessions supported on the 324 whole CMCC card and the number of allocation errors that 325 have occurred when attempting to increase the number of 326 sessions. The indices are the same as the maximum sessions 327 Admin table. 328 The one field in this table represents: 329 * The current operational maximum sessions for 330 this card 331 In the example above, the one entry would be defined. 332 - ifIndex is created by the agent 333 - the highest maximum sessions that has occurred since 334 the last re-boot. 335 - the number of allocation errors when extending the 336 number of sessions. 337 338The last table is the SNA Connection table. Each entry 339 in this table represents a connection from an I/O Device 340 (Channel Path/Device) address to a CMCC internal LAN Adapter 341 for a single SAP address. Multiple entries in this table 342 can represent the same LAN Adapter with the use 343 of a different SAP. The entries in this table are 344 created when VTAM on a host creates an XCA Major 345 Node definition. That definition will tell the router 346 what I/O Device address are to be bound to which 347 CMCC internal LAN Adapter (of a type) and which SAP will be 348 used to carry traffic. 349 The indices of the table are: 350 * The ifIndex that addresses the virtual 351 CMCC interface 352 * The virtual interface identifying a unique 353 CMCC internal MAC Adapter. This definition used is defined 354 in the CISCO-SNA-LLC-MIB as llcPortVirtualIndex. 355 * The SAP used by this connection. 356 NOTE: The SAP definition used is defined in 357 the CISCO-SNA-LLC-MIB. 358 The fields included in this table represent: 359 * The number of currently active sessions 360 over this connection 361 * The slot of the CMCC card. 362 * The port on the CMCC card that the Path/Device 363 (subchannel is configured. 364 * The Channel Path used by this connection 365 * The Device used by this connection 366 In the example above, the number entries would 367 depend upon the VTAM configuration. 368 Each entry would be: 369 - ifIndex is created by the agent 370 - one of the LAN identifiers from one of the entries 371 in the CMCC internal LAN table. 372 - one of the adapter identifiers from one the 373 entries in the CMCC internal LAN Adapter table. 374 - the SAP provided by the XCA Major Node command 375 - the number of currently active sessions 376 - the slot of the CMCC card. 377 - the port on the CMCC card. 378 - the Channel Path from one entry in the first table 379 - the Device from same entry as the Channel Path 380 in the first table 381 " 382 REVISION "9801060000Z" 383 DESCRIPTION 384 "With the addition of Cisco's new Channel Port 385 Adapter cards, all the references to CIP in the 386 MIB description and object descriptions are changed 387 to CMCC (Cisco Mainframe Channel Connection). The 388 object names in the form of cip... or cipCard... 389 will remain the same, but will be valid objects 390 for the Channel Port Adapter cards. 391 392 Change the maximum number of llc2 sessions 393 supported from 4000 to 6000." 394 395 REVISION "9508210000Z" 396 DESCRIPTION 397 "Minor cleanups to pacify mib compiler." 398 REVISION "9504280000Z" 399 DESCRIPTION 400 "Initial version of this MIB module." 401 ::= { ciscoMgmt 33 } 402 403ChannelPath ::= TEXTUAL-CONVENTION 404 DISPLAY-HINT "1x:" 405 STATUS current 406 DESCRIPTION 407 "This channel path is a two octet value made up of the 408 following values: 409 ------------------------------------------------------ 410 Path 01-FF 411 For a directly attached ESCON channel or 412 any parallel channel, this value is 01 413 unless the system administrator has 414 configured another value. 415 For a channel attached through an ESCON 416 director switch, this value will be the 417 path that, from the router point of view, 418 exits the switch and attaches to the 419 host. 420 ------------------------------------------------------ 421 Channel logical address 0-F 422 For a directly attached ESCON channel or 423 any parallel channel, this value is 0. 424 If the host is running in Logical 425 Partition (LPAR) mode, this is the 426 channel logical address associated with 427 the channel and defined in the IOCP 428 configuration file used by VTAM. 429 The default for this part of the path 430 argument is 0. 431 Otherwise, the channel logical address 432 associated with the channel is defined 433 in the IOCP configuration file used by 434 VTAM. 435 ------------------------------------------------------ 436 Control unit logical address 0-F 437 For a directly attached ESCON channel or 438 any parallel channel, this value 439 defaults to 0. If this value is 440 specified in the IOCP file, used by 441 VTAM, then match that value here. 442 Otherwise, the control unit logical 443 address is specified in the IOCP 444 configuration file's CNTLUNIT statement 445 for the host channel in the CUADD parameter. 446 ------------------------------------------------------ 447 For example, for path C7, channel logical address 9, control 448 unit logical address 4, the 2 octet value is C7:94. 449 450 NOTE: Knowledge of creating and using IOCP configuration 451 files for VTAM is a prerequisite." 452 SYNTAX OCTET STRING(SIZE (0..2)) 453 454ChannelDevice ::= TEXTUAL-CONVENTION 455 DISPLAY-HINT "1x:" 456 STATUS current 457 DESCRIPTION 458 "Two octet hex device address for the device the 459 Systems Network Architecture (SNA) host will use 460 to communicate with the Channel Systems Network 461 Architecture (CSNA) feature on the CMCC card. 462 463 The first octet will always be zero for 464 consistency with other CMCC MIBs. 465 466 For example, for device address 1C (decimal 28) the 467 2 octet value is 00:1C." 468 SYNTAX OCTET STRING(SIZE (0..2)) 469 470cipCsnaObjects OBJECT IDENTIFIER ::= { ciscoCipCsnaMIB 1 } 471 472cipCsnaChannel OBJECT IDENTIFIER ::= { cipCsnaObjects 1 } 473cipSession OBJECT IDENTIFIER ::= { cipCsnaObjects 2 } 474cipCsnaConnection OBJECT IDENTIFIER ::= { cipCsnaObjects 3 } 475 476-- ;;;;;;;;;;;;;;;;;;;;; cipCardCsnaAdminTable ;;;;;;;;;;;;;;;;;;;;;;;;;;; 477-- Variables stored in this table are: 478-- <path> <device> <Block Delay Time> <Block Delay Length> 479-- <Maximum Block Length> 480 481cipCardCsnaAdminTable OBJECT-TYPE 482 SYNTAX SEQUENCE OF CipCardCsnaAdminEntry 483 MAX-ACCESS not-accessible 484 STATUS current 485 DESCRIPTION 486 "This table contains configuration information for 487 the Channel Systems Network Architecture (CSNA) 488 feature on the CMCC card." 489 ::= { cipCsnaChannel 1 } 490 491cipCardCsnaAdminEntry OBJECT-TYPE 492 SYNTAX CipCardCsnaAdminEntry 493 MAX-ACCESS not-accessible 494 STATUS current 495 DESCRIPTION 496 "A list of CSNA configuration values." 497 INDEX { cipCardEntryIndex, 498 cipCardDtrBrdIndex, 499 cipCardSubChannelIndex 500 } 501 ::= { cipCardCsnaAdminTable 1 } 502 503CipCardCsnaAdminEntry ::= SEQUENCE 504{ 505 cipCardCsnaAdminPath ChannelPath, 506 cipCardCsnaAdminDevice ChannelDevice, 507 cipCardCsnaAdminBlockDelayTime INTEGER (0..100), 508 cipCardCsnaAdminBlockDelayLength INTEGER (0..65535), 509 cipCardCsnaAdminMaxBlockLength INTEGER (4096..65535), 510 cipCardCsnaAdminRowStatus RowStatus 511} 512 513cipCardCsnaAdminPath OBJECT-TYPE 514 SYNTAX ChannelPath 515 MAX-ACCESS read-create 516 STATUS current 517 DESCRIPTION 518 "The Channel Path for this Channel Systems 519 Network Architecture table entry. 520 521 For more information see the 522 textual convention ChannelPath." 523 ::= { cipCardCsnaAdminEntry 1 } 524 525cipCardCsnaAdminDevice OBJECT-TYPE 526 SYNTAX ChannelDevice 527 MAX-ACCESS read-create 528 STATUS current 529 DESCRIPTION 530 "Two octet hex device address for the device the 531 SNA host will use to communicate with the CSNA 532 feature on the CMCC card. 533 534 For more information see the 535 textual convention ChannelDevice." 536 ::= { cipCardCsnaAdminEntry 2 } 537 538cipCardCsnaAdminBlockDelayTime OBJECT-TYPE 539 SYNTAX INTEGER (0..100) 540 UNITS "milliseconds" 541 MAX-ACCESS read-create 542 STATUS current 543 DESCRIPTION 544 "The Block Delay Time is the maximum amount of time 545 the CSNA feature can hold a set of requests 546 before it must transmit the block to the host. 547 548 The Block must be sent when this time has expired, 549 even if the block has not reached the suggested 550 Block Delay Length." 551 DEFVAL { 10 } 552 ::= { cipCardCsnaAdminEntry 3 } 553 554cipCardCsnaAdminBlockDelayLength OBJECT-TYPE 555 SYNTAX INTEGER (0..65535) 556 UNITS "octets" 557 MAX-ACCESS read-create 558 STATUS current 559 DESCRIPTION 560 "The Block Delay Length is the suggested size of 561 a block before it is transmitted to the host. 562 563 The Block Delay Length is used to force a transmit of 564 a block when all information currently being processed 565 has been placed in the block and the real block size 566 exceeds this Block Delay Length size. The size of the 567 block can grow larger than the Block Delay Length size, 568 but must never exceed the Maximum Block Length before 569 being transmitted." 570 DEFVAL { 20470 } 571 ::= { cipCardCsnaAdminEntry 4 } 572 573cipCardCsnaAdminMaxBlockLength OBJECT-TYPE 574 SYNTAX INTEGER (4096..65535) 575 UNITS "octets" 576 MAX-ACCESS read-create 577 STATUS current 578 DESCRIPTION 579 "The Maximum block length is the maximum size 580 that an inbound channel I/O block my attain 581 before being sent to the host. The block must 582 be smaller or equal to this value." 583 DEFVAL { 20470 } 584 ::= { cipCardCsnaAdminEntry 5 } 585 586cipCardCsnaAdminRowStatus OBJECT-TYPE 587 SYNTAX RowStatus 588 MAX-ACCESS read-create 589 STATUS current 590 DESCRIPTION 591 "This object is used by a Management Station to create 592 or delete the row entry in the cipCardCsnaAdminTable 593 following the the RowStatus textual convention. 594 595 Upon successful creation of the row, an Agent 596 automatically creates a corresponding entry in 597 the cipCardCsnaOperTable with the cipCardCsnaOperState 598 equal to 'inactive (1)'. 599 600 The Management Station can initiate row deletion, by 601 setting this value to 'destroy (6)'. The Agent will 602 then delete the rows corresponding to this CSNA 603 instance from both the cipCardCsnaAdminTable and 604 cipCardCsnaOperTable." 605 ::= { cipCardCsnaAdminEntry 6 } 606 607-- ;;;;;;;;;;;;;;;;;;;;; cipCardCsnaOperTable ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; 608-- Variables stored in this table are: 609-- <status> <Block Delay Time> <Block Delay Length> 610-- <Maximum Block Delay Length> 611 612cipCardCsnaOperTable OBJECT-TYPE 613 SYNTAX SEQUENCE OF CipCardCsnaOperEntry 614 MAX-ACCESS not-accessible 615 STATUS current 616 DESCRIPTION 617 "This table contains operation values and status information for 618 the Channel Systems Network Architecture (CSNA) feature on the 619 CMCC card." 620 ::= { cipCsnaChannel 2 } 621 622cipCardCsnaOperEntry OBJECT-TYPE 623 SYNTAX CipCardCsnaOperEntry 624 MAX-ACCESS not-accessible 625 STATUS current 626 DESCRIPTION 627 "A list of CSNA operational and status values. The entries are 628 created by the Agent. They have read-only access." 629 INDEX { cipCardEntryIndex, 630 cipCardDtrBrdIndex, 631 cipCardSubChannelIndex 632 } 633-- AUGMENTS { cipCardCsnaAdminEntry } 634 ::= { cipCardCsnaOperTable 1 } 635 636CipCardCsnaOperEntry ::= SEQUENCE 637{ 638 cipCardCsnaOperState INTEGER, 639 cipCardCsnaOperSlowDownState INTEGER, 640 cipCardCsnaOperBlockDelayTime INTEGER (0..100), 641 cipCardCsnaOperBlockDelayLength INTEGER (0..65535), 642 cipCardCsnaOperMaxBlockLength INTEGER (4096..65535) 643} 644 645cipCardCsnaOperState OBJECT-TYPE 646 SYNTAX INTEGER { 647 closed (0), 648 pendingOpen (1), 649 open (2), 650 pendingSetup (3), 651 setupComplete (4), 652 pendingClose (5) 653 } 654 MAX-ACCESS read-only 655 STATUS current 656 DESCRIPTION 657 "The current state of the CSNA entry. 658 The values have the following meanings: 659 closed - Link is closed. 660 pendingOpen - An Open Subchannel command has 661 been received from the host. 662 open - Subchannel is open. 663 pendingSetup - Host has queried for LAN info. 664 setupComplete - LAN info has been sent to the host. 665 pendingClose - A Close Subchannel command has 666 been received from the host. 667 " 668 ::= { cipCardCsnaOperEntry 1 } 669 670cipCardCsnaOperSlowDownState OBJECT-TYPE 671 SYNTAX INTEGER { 672 normal (0), 673 slowDownSent (1), 674 slowDownReceived (2), 675 slowDownSentAndReceived (3) 676 } 677 MAX-ACCESS read-only 678 STATUS current 679 DESCRIPTION 680 "The current state of the CSNA slow down 681 condition. A channel device will turn on 682 the slow down bit whenever insufficient 683 buffering is available to receive data 684 from the adjacent channel device. 685 686 The values have the following meanings: 687 normal - Link is normal. 688 slowDownSent - The router has put VTAM into 689 a slow down state. 690 slowDownReceived - VTAM has put the router into 691 a slow down state. 692 slowDownSentReceived - Both VTAM and the router 693 are in a slow down state. 694 " 695 ::= { cipCardCsnaOperEntry 2 } 696 697cipCardCsnaOperBlockDelayTime OBJECT-TYPE 698 SYNTAX INTEGER (0..100) 699 UNITS "milliseconds" 700 MAX-ACCESS read-only 701 STATUS current 702 DESCRIPTION 703 "The current Block Delay Time value being 704 used by this instance of CSNA path/device 705 (subchannel)." 706 ::= { cipCardCsnaOperEntry 3 } 707 708cipCardCsnaOperBlockDelayLength OBJECT-TYPE 709 SYNTAX INTEGER (0..65535) 710 UNITS "octets" 711 MAX-ACCESS read-only 712 STATUS current 713 DESCRIPTION 714 "The current Block Delay Length being 715 used by this instance of CSNA path/device 716 (subchannel)." 717 ::= { cipCardCsnaOperEntry 4 } 718 719cipCardCsnaOperMaxBlockLength OBJECT-TYPE 720 SYNTAX INTEGER (4096..65535) 721 UNITS "octets" 722 MAX-ACCESS read-only 723 STATUS current 724 DESCRIPTION 725 "The current Maximum block length 726 being used by this instance of CSNA 727 path/device (subchannel)." 728 ::= { cipCardCsnaOperEntry 5 } 729 730-- ;;;;;;;;;;;;;;;;;;;;; cipCardCsnaStatsTable ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; 731-- Variables stored in this table are: 732-- <Blocks Transmitted> <Blocks Received> 733-- <Bytes Transmitted> <Bytes Received> 734-- <Blocks Transmitted by Block Delay Time expiration> 735-- <Bytes Transmitted by Block Delay Time expiration> 736-- <Blocks Transmitted by Block Delay Length exceeded> 737-- <Bytes Transmitted by Block Delay Length exceeded> 738-- <Blocks Transmitted by Maximum Block Length> 739-- <Bytes Transmitted by Maximum Block Length> 740-- <slow downs received> 741-- <slow downs transmitted> 742 743cipCardCsnaStatsTable OBJECT-TYPE 744 SYNTAX SEQUENCE OF CipCardCsnaStatsEntry 745 MAX-ACCESS not-accessible 746 STATUS current 747 DESCRIPTION 748 "This table contains statistics information for 749 the Channel Systems Network Architectures (CSNA) 750 feature on the CMCC card." 751 ::= { cipCsnaChannel 3 } 752 753cipCardCsnaStatsEntry OBJECT-TYPE 754 SYNTAX CipCardCsnaStatsEntry 755 MAX-ACCESS not-accessible 756 STATUS current 757 DESCRIPTION 758 "A list of CSNA statistics. The entries are 759 created by the Agent. They have read-only access." 760 INDEX { cipCardEntryIndex, 761 cipCardDtrBrdIndex, 762 cipCardSubChannelIndex 763 } 764-- AUGMENTS { cipCardCsnaAdminEntry } 765 ::= { cipCardCsnaStatsTable 1 } 766 767CipCardCsnaStatsEntry ::= SEQUENCE 768{ 769 cipCardCsnaStatsBlocksTxd Counter32, 770 cipCardCsnaStatsBlocksRxd Counter32, 771 cipCardCsnaStatsBytesTxd Counter32, 772 cipCardCsnaStatsHCBytesTxd Counter64, 773 cipCardCsnaStatsBytesRxd Counter32, 774 cipCardCsnaStatsHCBytesRxd Counter64, 775 cipCardCsnaStatsBlocksTxByBlockDelayTime Counter32, 776 cipCardCsnaStatsBytesTxByBlockDelayTime Counter32, 777 cipCardCsnaStatsHCBytesTxByBlockDelayTime Counter64, 778 cipCardCsnaStatsBlocksTxByBlockDelayLength Counter32, 779 cipCardCsnaStatsBytesTxByBlockDelayLength Counter32, 780 cipCardCsnaStatsHCBytesTxByBlockDelayLength Counter64, 781 cipCardCsnaStatsBlocksTxByMaxBlockLength Counter32, 782 cipCardCsnaStatsBytesTxByMaxBlockLength Counter32, 783 cipCardCsnaStatsHCBytesTxByMaxBlockLength Counter64, 784 cipCardCsnaStatsSlowDownsReceived Counter32, 785 cipCardCsnaStatsSlowDownsSent Counter32 786} 787 788cipCardCsnaStatsBlocksTxd OBJECT-TYPE 789 SYNTAX Counter32 790 MAX-ACCESS read-only 791 STATUS current 792 DESCRIPTION 793 "The number of Blocks Transmitted." 794 ::= { cipCardCsnaStatsEntry 1 } 795 796cipCardCsnaStatsBlocksRxd OBJECT-TYPE 797 SYNTAX Counter32 798 MAX-ACCESS read-only 799 STATUS current 800 DESCRIPTION 801 "The number of Blocks Received." 802 ::= { cipCardCsnaStatsEntry 2 } 803 804cipCardCsnaStatsBytesTxd OBJECT-TYPE 805 SYNTAX Counter32 806 UNITS "octets" 807 MAX-ACCESS read-only 808 STATUS current 809 DESCRIPTION 810 "The number of Bytes Transmitted. 811 812 NOTE: To support SNMP Version 1 813 Managers, this variable is 814 supplied as a 32 bit value 815 which can wrap very 816 frequently." 817 ::= { cipCardCsnaStatsEntry 3 } 818 819cipCardCsnaStatsHCBytesTxd OBJECT-TYPE 820 SYNTAX Counter64 821 UNITS "octets" 822 MAX-ACCESS read-only 823 STATUS current 824 DESCRIPTION 825 "The number of Bytes Transmitted. 826 827 NOTE: This is a 64 bit (High Capacity) 828 version of the cipCardCsnaStatsBytesTxd 829 counter for use with SNMP Version 2 830 Managers" 831 ::= { cipCardCsnaStatsEntry 4 } 832 833cipCardCsnaStatsBytesRxd OBJECT-TYPE 834 SYNTAX Counter32 835 UNITS "octets" 836 MAX-ACCESS read-only 837 STATUS current 838 DESCRIPTION 839 "The number of Bytes Received. 840 841 NOTE: To support SNMP Version 1 842 Managers, this variable is 843 supplied as a 32 bit value 844 which can wrap very 845 frequently." 846 ::= { cipCardCsnaStatsEntry 5 } 847 848cipCardCsnaStatsHCBytesRxd OBJECT-TYPE 849 SYNTAX Counter64 850 UNITS "octets" 851 MAX-ACCESS read-only 852 STATUS current 853 DESCRIPTION 854 "The number of Bytes Received. 855 856 NOTE: This is a 64 bit (High Capacity) 857 version of the cipCardCsnaStatsBytesRxd 858 counter for use with SNMP Version 2 859 Managers" 860 ::= { cipCardCsnaStatsEntry 6 } 861 862cipCardCsnaStatsBlocksTxByBlockDelayTime OBJECT-TYPE 863 SYNTAX Counter32 864 MAX-ACCESS read-only 865 STATUS current 866 DESCRIPTION 867 "The number of Blocks Transmitted when the 868 Block Delay Time has been exceeded." 869 ::= { cipCardCsnaStatsEntry 7 } 870 871cipCardCsnaStatsBytesTxByBlockDelayTime OBJECT-TYPE 872 SYNTAX Counter32 873 MAX-ACCESS read-only 874 STATUS current 875 DESCRIPTION 876 "The number of Bytes Transmitted when the 877 Block Delay Time has been exceeded." 878 ::= { cipCardCsnaStatsEntry 8 } 879 880cipCardCsnaStatsHCBytesTxByBlockDelayTime OBJECT-TYPE 881 SYNTAX Counter64 882 MAX-ACCESS read-only 883 STATUS current 884 DESCRIPTION 885 "The number of Bytes Transmitted when the 886 Block Delay Time has been exceeded. 887 888 NOTE: This is a 64 bit (High Capacity) 889 version of the cipCardCsnaStatsBytesTxByBlockDelayTime 890 counter for use with SNMP Version 2 891 Managers" 892 ::= { cipCardCsnaStatsEntry 9 } 893 894cipCardCsnaStatsBlocksTxByBlockDelayLength OBJECT-TYPE 895 SYNTAX Counter32 896 MAX-ACCESS read-only 897 STATUS current 898 DESCRIPTION 899 "The number of Blocks Transmitted when the 900 suggested Block Delay Length has been 901 exceeded." 902 ::= { cipCardCsnaStatsEntry 10 } 903 904cipCardCsnaStatsBytesTxByBlockDelayLength OBJECT-TYPE 905 SYNTAX Counter32 906 MAX-ACCESS read-only 907 STATUS current 908 DESCRIPTION 909 "The number of Bytes Transmitted when the 910 suggested Block Delay Length has been 911 exceeded." 912 ::= { cipCardCsnaStatsEntry 11 } 913 914cipCardCsnaStatsHCBytesTxByBlockDelayLength OBJECT-TYPE 915 SYNTAX Counter64 916 MAX-ACCESS read-only 917 STATUS current 918 DESCRIPTION 919 "The number of Bytes Transmitted when the 920 suggested Block Delay Length has been 921 exceeded. 922 923 NOTE: This is a 64 bit (High Capacity) 924 version of the cipCardCsnaStatsBytesTxByBlockDelayLength 925 counter for use with SNMP Version 2 926 Managers" 927 ::= { cipCardCsnaStatsEntry 12 } 928 929cipCardCsnaStatsBlocksTxByMaxBlockLength OBJECT-TYPE 930 SYNTAX Counter32 931 MAX-ACCESS read-only 932 STATUS current 933 DESCRIPTION 934 "The number of Blocks Transmitted when the 935 Maximum block length has been exceeded." 936 ::= { cipCardCsnaStatsEntry 13 } 937 938cipCardCsnaStatsBytesTxByMaxBlockLength OBJECT-TYPE 939 SYNTAX Counter32 940 MAX-ACCESS read-only 941 STATUS current 942 DESCRIPTION 943 "The number of Bytes Transmitted when the 944 Maximum block length has been exceeded." 945 ::= { cipCardCsnaStatsEntry 14 } 946 947cipCardCsnaStatsHCBytesTxByMaxBlockLength OBJECT-TYPE 948 SYNTAX Counter64 949 MAX-ACCESS read-only 950 STATUS current 951 DESCRIPTION 952 "The number of Bytes Transmitted when the 953 Maximum block length has been exceeded. 954 955 NOTE: This is a 64 bit (High Capacity) 956 version of the cipCardCsnaStatsBytesTxByBlockDelayLength 957 counter for use with SNMP Version 2 958 Managers" 959 ::= { cipCardCsnaStatsEntry 15 } 960 961cipCardCsnaStatsSlowDownsReceived OBJECT-TYPE 962 SYNTAX Counter32 963 MAX-ACCESS read-only 964 STATUS current 965 DESCRIPTION 966 "The number of times the slow down bit was 967 detected in a channel I/O block received from 968 VTAM. This condition causes the router to stop 969 transmitting data to VTAM over the channel until 970 the slow down condition has been cleared." 971 ::= { cipCardCsnaStatsEntry 16 } 972 973cipCardCsnaStatsSlowDownsSent OBJECT-TYPE 974 SYNTAX Counter32 975 MAX-ACCESS read-only 976 STATUS current 977 DESCRIPTION 978 "The number of times the slow down bit was 979 set by the router to stop VTAM from sending any 980 more channel I/O blocks. This condition stays in 981 effect until the router clears the slow down 982 condition." 983 ::= { cipCardCsnaStatsEntry 17 } 984 985-- ;;;;;;;;;;;;;;; cipCardSessionsAdminTable ;;;;;;;;;;;;;;;;;;;;; 986-- Variables stored in this table are: 987-- <Maximum Number of Sessions> 988 989cipCardSessionsAdminTable OBJECT-TYPE 990 SYNTAX SEQUENCE OF CipCardSessionsAdminEntry 991 MAX-ACCESS not-accessible 992 STATUS current 993 DESCRIPTION 994 "This table contains configured values for 995 CSNA sessions supported on the CMCC card." 996 ::= { cipSession 1 } 997 998cipCardSessionsAdminEntry OBJECT-TYPE 999 SYNTAX CipCardSessionsAdminEntry 1000 MAX-ACCESS not-accessible 1001 STATUS current 1002 DESCRIPTION 1003 "A list of CMCC specific Session configuration values." 1004 INDEX { cipCardEntryIndex } 1005 ::= { cipCardSessionsAdminTable 1 } 1006 1007CipCardSessionsAdminEntry ::= SEQUENCE 1008{ 1009 cipCardAdminMaxLlc2Sessions INTEGER (0..6000) 1010} 1011 1012cipCardAdminMaxLlc2Sessions OBJECT-TYPE 1013 SYNTAX INTEGER (0..6000) 1014 MAX-ACCESS read-write 1015 STATUS current 1016 DESCRIPTION 1017 "The configured maximum number of LLC2 sessions 1018 allowed on a CMCC card. A value of zero indicates 1019 that the maximum should only be limited by the 1020 amount of available memory on the CMCC. A value 1021 greater than zero indicates the maximum number 1022 of sessions the CMCC will support given 1023 there is enough memory available on the CMCC card. 1024 1025 This value can be set at any time, however 1026 it will only affect the Maximum number of LLC2 1027 sessions supported on a CIP the first time it 1028 is set and only if the value it is being set to 1029 is greater than the current value for 1030 cipCardStatsHiWaterLlc2Sessions." 1031 ::= { cipCardSessionsAdminEntry 1 } 1032 1033-- ;;;;;;;;;;;;;;; cipCardSessionsOperTable ;;;;;;;;;;;;;;;;;;;;; 1034-- Variables stored in this table are: 1035-- <Maximum Number of Active Sessions> 1036 1037cipCardSessionsOperTable OBJECT-TYPE 1038 SYNTAX SEQUENCE OF CipCardSessionsOperEntry 1039 MAX-ACCESS not-accessible 1040 STATUS current 1041 DESCRIPTION 1042 "This table contains the current value for 1043 the maximum number of sessions that can be 1044 supported on the CMCC card." 1045 ::= { cipSession 2 } 1046 1047cipCardSessionsOperEntry OBJECT-TYPE 1048 SYNTAX CipCardSessionsOperEntry 1049 MAX-ACCESS not-accessible 1050 STATUS current 1051 DESCRIPTION 1052 "A list of CMCC specific Session values." 1053 INDEX { cipCardEntryIndex } 1054-- AUGMENTS { cipCardSessionsAdminEntry } 1055 ::= { cipCardSessionsOperTable 1 } 1056 1057CipCardSessionsOperEntry ::= SEQUENCE 1058{ 1059 cipCardOperMaxLlc2Sessions INTEGER (0..6000) 1060} 1061 1062cipCardOperMaxLlc2Sessions OBJECT-TYPE 1063 SYNTAX INTEGER (0..6000) 1064 MAX-ACCESS read-only 1065 STATUS current 1066 DESCRIPTION 1067 "This value indicates the current number 1068 of LLC2 sessions that can be supported 1069 on this CMCC card. If this value is 1070 zero, then the limit of LLC2 sessions on 1071 the CMCC card is only limited by the amount of 1072 memory available." 1073 ::= { cipCardSessionsOperEntry 1 } 1074 1075-- ;;;;;;;;;;;;;;; cipCardSessionsStatsTable ;;;;;;;;;;;;;;;;;;;;; 1076-- Variables stored in this table are: 1077-- <High Water Mark of Active Sessions> 1078-- <Number of Allocation Errors> 1079 1080cipCardSessionsStatsTable OBJECT-TYPE 1081 SYNTAX SEQUENCE OF CipCardSessionsStatsEntry 1082 MAX-ACCESS not-accessible 1083 STATUS current 1084 DESCRIPTION 1085 "This table contains the statistic value(s) for 1086 the maximum number of sessions that can be 1087 supported on the CMCC card." 1088 ::= { cipSession 3 } 1089 1090cipCardSessionsStatsEntry OBJECT-TYPE 1091 SYNTAX CipCardSessionsStatsEntry 1092 MAX-ACCESS not-accessible 1093 STATUS current 1094 DESCRIPTION 1095 "A list of CMCC specific Session values." 1096 INDEX { cipCardEntryIndex } 1097-- AUGMENTS { cipCardSessionsAdminEntry } 1098 ::= { cipCardSessionsStatsTable 1 } 1099 1100CipCardSessionsStatsEntry ::= SEQUENCE 1101{ 1102 cipCardStatsHiWaterLlc2Sessions Gauge32, 1103 cipCardStatsLlc2SessionAllocationErrs Counter32 1104} 1105 1106cipCardStatsHiWaterLlc2Sessions OBJECT-TYPE 1107 SYNTAX Gauge32 1108 MAX-ACCESS read-only 1109 STATUS current 1110 DESCRIPTION 1111 "High water LLC2 sessions count per CMCC card. 1112 1113 If cipCardOperMaxLlc2Sessions is zero (0), 1114 then this value starts at 256 Llc2 sessions 1115 and will be incremented in values of 64 as 1116 more active concurrent LLC2 sessions are 1117 established. 1118 1119 If cipCardOperMaxLlc2Sessions is greater 1120 then zero (0), then this value will either 1121 be equal to the cipCardOperMaxLlc2Sessions 1122 given enough memory is available on the CMCC card 1123 to support that many LLC2 sessions or 1124 the the value will be less than 1125 cipCardOperMaxLlc2Sessions, reflecting the maximum 1126 number of LLC2 sessions the CMCC card can support." 1127 ::= { cipCardSessionsStatsEntry 1 } 1128 1129cipCardStatsLlc2SessionAllocationErrs OBJECT-TYPE 1130 SYNTAX Counter32 1131 MAX-ACCESS read-only 1132 STATUS current 1133 DESCRIPTION 1134 "This value represents the number of 1135 memory allocation errors that have 1136 occurred when attempting to create a 1137 new block of memory for the LLC2 session 1138 buffer pool." 1139 ::= { cipCardSessionsStatsEntry 2 } 1140 1141-- ;;;;;;;;;;;;;;;;;;;;; cipCardCsnaConnTable ;;;;;;;;;;;;;;;;;;;;;;;;;;; 1142-- Variables indexing and stored in this table are: 1143-- <interface index> <Virtual Index> <SAP number> 1144-- <Active Sessions> <slot> <port> <path> <device> 1145 1146cipCardCsnaConnTable OBJECT-TYPE 1147 SYNTAX SEQUENCE OF CipCardCsnaConnEntry 1148 MAX-ACCESS not-accessible 1149 STATUS current 1150 DESCRIPTION 1151 "This table contains the map between 1152 VTAM (the I/O Device Address) and the 1153 CMCC LAN Adapter/Mac 1154 Address/SAP. 1155 1156 For example: 1157 1158 Channel Path Channel Path 1159 & Device & Device 1160 | \ \ / / | 1161 | \ \ / / | 1162 SAPS 04 04 04 04 04 04 1163 08 \ \ / / 08 1164 | \ \/ / | 1165 | \ /\ / | 1166 | \ / \ / | 1167 | \ / \/ | 1168 | v /\ | 1169 | ______/ \ / \_____ | 1170 Adpt Adpt Adpt" 1171 ::= { cipCsnaConnection 1 } 1172 1173cipCardCsnaConnEntry OBJECT-TYPE 1174 SYNTAX CipCardCsnaConnEntry 1175 MAX-ACCESS not-accessible 1176 STATUS current 1177 DESCRIPTION 1178 "A list of CSNA internal LAN Adapter connection values. 1179 The first three indices allow the mapping to the 1180 LAN and Adapter. To obtain the 1181 mapping to the llc SAP table, use the ifIndex, 1182 llcSapNumber, and the MAC Address (from the 1183 CMCC internal LAN Adapter table)." 1184 INDEX { ifIndex, 1185 llcPortVirtualIndex, 1186 llcSapNumber 1187 } 1188 ::= { cipCardCsnaConnTable 1 } 1189 1190CipCardCsnaConnEntry ::= SEQUENCE 1191{ 1192 cipCardCsnaConnActiveSessions Gauge32, 1193 cipCardCsnaSlot Integer32, 1194 cipCardCsnaPort Integer32, 1195 cipCardCsnaConnPath ChannelPath, 1196 cipCardCsnaConnDevice ChannelDevice 1197} 1198 1199cipCardCsnaConnActiveSessions OBJECT-TYPE 1200 SYNTAX Gauge32 1201 MAX-ACCESS read-only 1202 STATUS current 1203 DESCRIPTION 1204 "The Active Sessions in this VTAM to CMCC 1205 LAN Adapter/Mac Address mapping." 1206 ::= { cipCardCsnaConnEntry 1 } 1207 1208cipCardCsnaSlot OBJECT-TYPE 1209 SYNTAX Integer32 1210 MAX-ACCESS read-only 1211 STATUS current 1212 DESCRIPTION 1213 "Slot number of the CMCC card that the 1214 Path and Device are configured." 1215 ::= { cipCardCsnaConnEntry 2 } 1216 1217cipCardCsnaPort OBJECT-TYPE 1218 SYNTAX Integer32 1219 MAX-ACCESS read-only 1220 STATUS current 1221 DESCRIPTION 1222 "Port number on the CMCC card that the 1223 Path and Device are configured." 1224 ::= { cipCardCsnaConnEntry 3 } 1225 1226cipCardCsnaConnPath OBJECT-TYPE 1227 SYNTAX ChannelPath 1228 MAX-ACCESS read-only 1229 STATUS current 1230 DESCRIPTION 1231 "Hex path identifier used by this instance 1232 of CMCC LAN adapter/SAP to connect 1233 SNA sessions to VTAM. 1234 1235 For more information see the 1236 textual convention ChannelPath." 1237 ::= { cipCardCsnaConnEntry 4 } 1238 1239cipCardCsnaConnDevice OBJECT-TYPE 1240 SYNTAX ChannelDevice 1241 MAX-ACCESS read-only 1242 STATUS current 1243 DESCRIPTION 1244 "Two digit hex device address used by this 1245 CMCC LAN adapter/SAP instance to connect 1246 SNA sessions to VTAM. 1247 1248 For more information see the 1249 textual convention ChannelDevice." 1250 ::= { cipCardCsnaConnEntry 5 } 1251 1252-- ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; 1253-- 1254-- Notifications 1255-- 1256 1257cipCsnaNotificationPrefix OBJECT IDENTIFIER ::= { ciscoCipCsnaMIB 2 } 1258cipCsnaNotifications OBJECT IDENTIFIER ::= { cipCsnaNotificationPrefix 0 } 1259 1260cipCsnaOpenDuplicateSapFailure NOTIFICATION-TYPE 1261 OBJECTS 1262 { 1263 cipCardCsnaSlot, 1264 cipCardCsnaPort, 1265 cipCardCsnaConnPath, 1266 cipCardCsnaConnDevice 1267 } 1268 STATUS current 1269 DESCRIPTION 1270 "This trap indicates that VTAM attempted 1271 to open a SAP that was already open via 1272 another Path/Device on this CMCC card." 1273 ::= { cipCsnaNotifications 1 } 1274 1275cipCsnaLlc2ConnectionLimitExceeded NOTIFICATION-TYPE 1276 OBJECTS 1277 { 1278 cipCardAdminMaxLlc2Sessions, 1279 cipCardOperMaxLlc2Sessions, 1280 cipCardStatsHiWaterLlc2Sessions, 1281 cipCardStatsLlc2SessionAllocationErrs 1282 } 1283 STATUS current 1284 DESCRIPTION 1285 "This trap indicates that a connection 1286 attempt was rejected due to a connection 1287 resource limitation" 1288 ::= { cipCsnaNotifications 2 } 1289 1290-- ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; 1291-- 1292-- Conformance Information 1293-- 1294 1295ciscoCipCsnaMibConformance OBJECT IDENTIFIER ::= { ciscoCipCsnaMIB 3 } 1296ciscoCipCsnaMibCompliances OBJECT IDENTIFIER 1297 ::= { ciscoCipCsnaMibConformance 1 } 1298ciscoCipCsnaMibGroups OBJECT IDENTIFIER 1299 ::= { ciscoCipCsnaMibConformance 2 } 1300 1301-- 1302-- Compliance Statements 1303-- 1304 1305ciscoCipCsnaMibCompliance MODULE-COMPLIANCE 1306 STATUS current 1307 DESCRIPTION 1308 "The compliance statement for the Channel Systems Network 1309 Architecture (CSNA) feature." 1310 MODULE 1311 MANDATORY-GROUPS { 1312 ciscoCsnaGroup, 1313 ciscoMaxSessionsGroup, 1314 ciscoCsnaConnGroup 1315 } 1316 ::= { ciscoCipCsnaMibCompliances 1 } 1317 1318ciscoCsnaGroup OBJECT-GROUP 1319 OBJECTS { 1320 -- Table Header 1321 -- cipCardCsnaAdminTable 1322 -- cipCardCsnaAdminEntry 1323 -- Table Header 1324 -- cipCardCsnaOperTable 1325 -- cipCardCsnaOperEntry 1326 -- Table Header 1327 -- cipCardCsnaStatsTable 1328 -- cipCardCsnaStatsEntry 1329 -- Table Indicies 1330 -- cipCardEntryIndex 1331 -- cipCardDtrBrdIndex 1332 -- cipCardSubChannelIndex 1333 1334 cipCardCsnaAdminPath, 1335 cipCardCsnaAdminDevice, 1336 cipCardCsnaAdminBlockDelayTime, 1337 cipCardCsnaAdminBlockDelayLength, 1338 cipCardCsnaAdminMaxBlockLength, 1339 cipCardCsnaAdminRowStatus, 1340 cipCardCsnaOperState, 1341 cipCardCsnaOperSlowDownState, 1342 cipCardCsnaOperBlockDelayTime, 1343 cipCardCsnaOperBlockDelayLength, 1344 cipCardCsnaOperMaxBlockLength, 1345 cipCardCsnaStatsBlocksTxd, 1346 cipCardCsnaStatsBlocksRxd, 1347 cipCardCsnaStatsBytesTxd, 1348 cipCardCsnaStatsHCBytesTxd, 1349 cipCardCsnaStatsBytesRxd, 1350 cipCardCsnaStatsHCBytesRxd, 1351 cipCardCsnaStatsBlocksTxByBlockDelayTime, 1352 cipCardCsnaStatsBytesTxByBlockDelayTime, 1353 cipCardCsnaStatsHCBytesTxByBlockDelayTime, 1354 cipCardCsnaStatsBlocksTxByBlockDelayLength, 1355 cipCardCsnaStatsBytesTxByBlockDelayLength, 1356 cipCardCsnaStatsHCBytesTxByBlockDelayLength, 1357 cipCardCsnaStatsBlocksTxByMaxBlockLength, 1358 cipCardCsnaStatsBytesTxByMaxBlockLength, 1359 cipCardCsnaStatsHCBytesTxByMaxBlockLength, 1360 cipCardCsnaStatsSlowDownsSent, 1361 cipCardCsnaStatsSlowDownsReceived 1362 } 1363 STATUS current 1364 DESCRIPTION 1365 "A collection of objects providing (Channel Systems Network 1366 Architecture (CSNA) Administration, Operational 1367 status and Statistics." 1368 ::= { ciscoCipCsnaMibGroups 1 } 1369 1370ciscoMaxSessionsGroup OBJECT-GROUP 1371 OBJECTS { 1372 -- Table Header 1373 -- cipCardSessionsAdminTable 1374 -- cipCardSessionsAdminEntry 1375 -- Table Header 1376 -- cipCardSessionsOperTable 1377 -- cipCardSessionsOperEntry 1378 -- Table Header 1379 -- cipCardSessionsStatsTable 1380 -- cipCardSessionsStatsEntry 1381 -- Table Indicies 1382 -- cipCardEntryIndex 1383 1384 cipCardAdminMaxLlc2Sessions, 1385 cipCardOperMaxLlc2Sessions, 1386 cipCardStatsHiWaterLlc2Sessions, 1387 cipCardStatsLlc2SessionAllocationErrs 1388 } 1389 STATUS current 1390 DESCRIPTION 1391 "A collection of objects providing the information 1392 on the maximum number of sessions supported 1393 on a CMCC card." 1394 ::= { ciscoCipCsnaMibGroups 2 } 1395 1396ciscoCsnaConnGroup OBJECT-GROUP 1397 OBJECTS { 1398 -- Table Header 1399 -- cipCardCsnaConnTable 1400 -- cipCardCsnaConnEntry 1401 -- Table Indicies 1402 -- ifIndex 1403 -- llcPortVirtualIndex 1404 -- llcSapNumber 1405 1406 cipCardCsnaConnActiveSessions, 1407 cipCardCsnaSlot, 1408 cipCardCsnaPort, 1409 cipCardCsnaConnPath, 1410 cipCardCsnaConnDevice 1411 } 1412 STATUS current 1413 DESCRIPTION 1414 "A collection of objects providing CMCC 1415 LAN adapter/SAP connection mapping to the 1416 Path/Device (subchannel)." 1417 ::= { ciscoCipCsnaMibGroups 3 } 1418 1419END 1420 1421 1422