1 2-- ***************************************************************** 3-- CISCO-VISM-CONN-MIB 4-- Connection MIB in VISM module. 5-- 6-- May 2004, Rashmi Purandare 7-- 8-- Copyright (c) 2003, 2004 by Cisco Systems, Inc. 9-- All rights reserved. 10-- ***************************************************************** 11 12CISCO-VISM-CONN-MIB DEFINITIONS ::= BEGIN 13IMPORTS 14 15 MODULE-IDENTITY, 16 OBJECT-TYPE, 17 Integer32, 18 Unsigned32 FROM SNMPv2-SMI 19 TruthValue, 20 DisplayString FROM SNMPv2-TC 21 MODULE-COMPLIANCE, 22 OBJECT-GROUP FROM SNMPv2-CONF 23 vismChanGrp, 24 vismChanCnfGrp FROM BASIS-MIB 25 ciscoWan FROM CISCOWAN-SMI; 26 27ciscoVismConnMIB MODULE-IDENTITY 28 LAST-UPDATED "200405030000Z" 29 ORGANIZATION "Cisco Systems, Inc." 30 CONTACT-INFO 31 " Cisco Systems 32 Customer Service 33 34 Postal: 170 W Tasman Drive 35 San Jose, CA 95134 36 USA 37 38 Tel: +1 800 553-NETS 39 40 E-mail: cs-wanatm@cisco.com" 41 DESCRIPTION 42 "The MIB module to contains configuration 43 and connection state information the VISM. 44 45 For VoIP(Voice over IP) support, VISM needs one 46 active AAL5 bearer PVC and one active AAL5 47 control PVC between the VISM card and the PXM. 48 The redundant PVC feature is supported for AAL5 49 PVCs. Each redundant PVC pair has one active 50 PVC and one standby PVC. There can be one AAL5 51 bearer redundant PVC pair and one AAL5 52 control redundant PVC pair. 53 54 All PVCs are added on the ATM virtual port=1. 55 56 For the AAL2 trunking application, there can 57 be multiple AAL2 bearer PVCs. Also, AAL2 bearer 58 PVC in this case, is between the two media 59 gateways, instead of just between the VISM and 60 the PXM. Up to 64 AAL2 bearer PVCs are supported 61 for this application. 62 63 Terminologies Used: 64 65 PVC - Permanent Virtual Circuit OR 66 Permanent Virtual Connection. 67 68 SPVC - Soft Permanent Virtual Circuits. 69 This is a PVC controlled by PNNI 70 Controller. 71 72 AAL - ATM Adaption Layer. 73 74 PXM - Processor Switch Module. 75 76 VC - Virtual Channel. 77 78 CAC - Connection Admission Control. 79 80 LCN - Logical Channel Number. 81 82 VCI - Virtual Channel Identifier. 83 " 84 85 REVISION "200405030000Z" 86 DESCRIPTION 87 " 88 Corrected UNITS clause for vismChanRTDResult 89 " 90 REVISION "200403090000Z" 91 DESCRIPTION 92 " 93 Added the following objects: 94 - vismChanPrefRouteId 95 - vismChanDirectRoute 96 - vismChanAisSuppression 97 - vismChanAisDelayTime 98 - vismChanUserMaxPCRBandwidth 99 - vismChanUserMaxScrIngress 100 - vismChanUserMaxMbsIngress 101 - vismChanUserMinPCRBandwidth 102 - vismChanUserPcrNumber 103 Added new enum oamFailure to vismChanRcvATMState. 104 " 105 REVISION "200402180000Z" 106 DESCRIPTION 107 "Initial version of the MIB. 108 109 The content of this MIB was originally 110 available in CISCO-WAN-AXIPOP-MIB defined 111 using SMIv1. The applicable objects from 112 CISCO-WAN-AXIPOP-MIB are defined using SMIv2 113 in this MIB. Also the descriptions of some 114 of the objects have been modified. 115 " 116 ::= { ciscoWan 86 } 117 118vismChanStateGrp OBJECT IDENTIFIER ::= { vismChanGrp 2 } 119 120vismChanCnfGrpTable OBJECT-TYPE 121 SYNTAX SEQUENCE OF VismChanCnfGrpEntry 122 MAX-ACCESS not-accessible 123 STATUS current 124 DESCRIPTION 125 "The channel configuration table for voice traffic." 126 ::= { vismChanCnfGrp 1 } 127 128vismChanCnfGrpEntry OBJECT-TYPE 129 SYNTAX VismChanCnfGrpEntry 130 MAX-ACCESS not-accessible 131 STATUS current 132 DESCRIPTION 133 "An entry for each voice channel. 134 An entry is created when the vismChanRowStatus is 135 set to 'add'. 136 An entry is deleted when the vismChanRowStatus is 137 set to 'del'. 138 " 139 INDEX { vismCnfChanNum } 140 ::= { vismChanCnfGrpTable 1 } 141 142VismChanCnfGrpEntry ::= 143 SEQUENCE { 144 vismCnfChanNum Integer32, 145 vismChanRowStatus INTEGER, 146 vismChanPortNum Integer32, 147 vismChanLocRmtLpbkState INTEGER, 148 vismChanTestType INTEGER, 149 vismChanTestState INTEGER, 150 vismChanRTDResult INTEGER, 151 vismChanPvcType INTEGER, 152 vismChanConnType INTEGER, 153 vismLocalVpi Integer32, 154 vismLocalVci Integer32, 155 vismLocalNSAP OCTET STRING, 156 vismRemoteVpi Integer32, 157 vismRemoteVci Integer32, 158 vismRemoteNSAP OCTET STRING, 159 vismMastership INTEGER, 160 vismVpcFlag INTEGER, 161 vismConnServiceType INTEGER, 162 vismRoutingPriority Integer32, 163 vismMaxCost Integer32, 164 vismRestrictTrunkType INTEGER, 165 vismConnPCR Integer32, 166 vismConnPercentUtil Integer32, 167 vismConnRemotePCR Integer32, 168 vismConnRemotePercentUtil Integer32, 169 vismChanProtection INTEGER, 170 vismChanPreference INTEGER, 171 vismChanActivityState INTEGER, 172 vismChanLockingState INTEGER, 173 vismChanScrIngress Integer32, 174 vismChanMbsIngress Integer32, 175 vismChanCdvt Integer32, 176 vismChanClrIngress Integer32, 177 vismConnPCREgress Integer32, 178 vismChanScrEgress Integer32, 179 vismChanMbsEgress Integer32, 180 vismChanClrEgress Integer32, 181 vismChanApplication INTEGER, 182 vismChanFallbackLcn Integer32, 183 vismChanReroute TruthValue, 184 vismFarEndAddressType INTEGER, 185 vismFarEndE164Address DisplayString, 186 vismFarEndGWIDAddress DisplayString, 187 vismFarEndNSAPAddress OCTET STRING, 188 vismVCCI Integer32, 189 vismConnAdminStatus INTEGER, 190 vismChanPrefRouteId Unsigned32, 191 vismChanDirectRoute TruthValue, 192 vismChanAisSuppression TruthValue, 193 vismChanAisDelayTime Unsigned32, 194 vismChanUserMaxPCRBandwidth Unsigned32, 195 vismChanUserMaxScrIngress Unsigned32, 196 vismChanUserMaxMbsIngress Unsigned32, 197 vismChanUserMinPCRBandwidth Unsigned32, 198 vismChanUserPcrNumber INTEGER 199} 200 201vismCnfChanNum OBJECT-TYPE 202 SYNTAX Integer32 (131..510) 203 MAX-ACCESS read-only 204 STATUS current 205 DESCRIPTION 206 "Logical Channel Number for the PVC." 207 ::= { vismChanCnfGrpEntry 1 } 208 209vismChanRowStatus OBJECT-TYPE 210 SYNTAX INTEGER { 211 add (1), 212 del (2), 213 mod (3), 214 outOfService (4) 215 } 216 MAX-ACCESS read-write 217 STATUS current 218 DESCRIPTION 219 "An entry is created by setting this object to 220 'add (1)' : Adds an entry to the table. 221 'mod (3)' : This is used to modify an existing 222 entry. 223 'del (2)' : This is used to delete an existing. 224 225 'outOfService (4)': Setting this object to this 226 value takes the channel out of service 227 or brings the channel 'down (2)'. The 228 channel can be brought 'up (1)' again by 229 setting the object to 'mod (3)'. 230 231 If there is redundant configuration for the 232 channel, an active channel can be deleted only 233 after locking the channel. 234 " 235 ::= { vismChanCnfGrpEntry 2 } 236 237vismChanPortNum OBJECT-TYPE 238 SYNTAX Integer32 (1..255) 239 MAX-ACCESS read-write 240 STATUS current 241 DESCRIPTION 242 "This refers to the virtual port between VISM and PXM. This 243 number is defaulted to the appropriate number for the 244 shelf, in PXM1 the value is 1 and 255 for PXM1E. 245 " 246 ::= { vismChanCnfGrpEntry 3 } 247 248vismChanLocRmtLpbkState OBJECT-TYPE 249 SYNTAX INTEGER { 250 enable (1), 251 disable (2) 252 } 253 MAX-ACCESS read-write 254 STATUS current 255 DESCRIPTION 256 "Loopback on cellbus in egress direction. 257 258 'enable (1)' : When you enable this option on a 259 connection (channel) then all the 260 cells that are coming from the network 261 side would be looped back toward the 262 network and all the frames coming from 263 the user side would be dropped. 264 265 'disable (2)': disables the remote loopback for a channel. 266 " 267 DEFVAL { disable } 268 ::= { vismChanCnfGrpEntry 4 } 269 270vismChanTestType OBJECT-TYPE 271 SYNTAX INTEGER { 272 testcon (1), 273 testdelay (2), 274 notest (3) 275 } 276 MAX-ACCESS read-write 277 STATUS current 278 DESCRIPTION 279 "This object specifies the channel test type on 280 a voice channel connection. 281 282 'testcon (1)' : Test Continuity. 283 'testdelay (2)' : Test Delay. 284 'notest (3)' : No test, meant for GET only. 285 " 286 ::= { vismChanCnfGrpEntry 5 } 287 288vismChanTestState OBJECT-TYPE 289 SYNTAX INTEGER { 290 passed (1), 291 failed (2), 292 inprogress (3), 293 notinprogress (4) 294 } 295 MAX-ACCESS read-only 296 STATUS current 297 DESCRIPTION 298 "This object identifies the state of the test 299 in the object vismChanTestType. 300 301 'passed (1)' : Test passed. 302 'failed (2)' : Test failed. 303 'inprogress (3)' : Test is in progress. 304 'notinprogress (4)' : No test in progress. 305 " 306 ::= { vismChanCnfGrpEntry 6 } 307 308vismChanRTDResult OBJECT-TYPE 309 SYNTAX INTEGER (1..65535) 310 UNITS "microseconds" 311 MAX-ACCESS read-only 312 STATUS current 313 DESCRIPTION 314 "This object identifies round trip delay. 315 " 316 ::= { vismChanCnfGrpEntry 7 } 317 318vismChanPvcType OBJECT-TYPE 319 SYNTAX INTEGER { 320 aal-5 (1), 321 aal-2 (2), 322 aal-1 (3) 323 } 324 MAX-ACCESS read-write 325 STATUS current 326 DESCRIPTION 327 "This object identifies the PVC type. 328 329 'aal-5 (1)' - Indicates the PVC type is AAL5. 330 'aal-2 (2)' - Indicates the PVC type is AAL2. 331 'aal-1 (3)' - Indicates the PVC type is AAL1. 332 " 333 DEFVAL { aal-5 } 334 ::= { vismChanCnfGrpEntry 8 } 335 336vismChanConnType OBJECT-TYPE 337 SYNTAX INTEGER { 338 pvc (1) 339 } 340 MAX-ACCESS read-write 341 STATUS current 342 DESCRIPTION 343 "This object identifies the connection type. 344 " 345 DEFVAL { pvc } 346 ::= { vismChanCnfGrpEntry 9 } 347 348vismLocalVpi OBJECT-TYPE 349 SYNTAX Integer32 (0..255) 350 MAX-ACCESS read-only 351 STATUS current 352 DESCRIPTION 353 "This object identifies local VPI, together 354 with the local VCI and NSAP represents the local 355 end point in this connection. 356 GET on this object returns value 0. 357 " 358 ::= { vismChanCnfGrpEntry 10 } 359 360vismLocalVci OBJECT-TYPE 361 SYNTAX Integer32 (0..65535) 362 MAX-ACCESS read-only 363 STATUS current 364 DESCRIPTION 365 "This object identifies local VCI, together 366 with the local VPI and NSAP represents the local 367 end point in this connection. 368 GET on this object returns the vismCnfChanNum or LCN. 369 " 370 ::= { vismChanCnfGrpEntry 11 } 371 372vismLocalNSAP OBJECT-TYPE 373 SYNTAX OCTET STRING (SIZE(20)) 374 MAX-ACCESS read-write 375 STATUS current 376 DESCRIPTION 377 "This object identifies the local NSAP address. 378 The NSAP is 20 bytes binary and is encoded as follows: 379 13 bytes : for prefix(node name) 380 2 bytes : for Cisco ID 381 1 byte : Reserved 382 3 bytes : for logical interface: 383 slot (1 byte) and port number (2 bytes), 384 1 byte : for SEL(Selector). 385 " 386 ::= { vismChanCnfGrpEntry 12 } 387 388vismRemoteVpi OBJECT-TYPE 389 SYNTAX Integer32 (0..65535) 390 MAX-ACCESS read-write 391 STATUS current 392 DESCRIPTION 393 "This object identifies the remote VPI, together 394 with the remote VCI and NSAP represents the remote 395 end point in this connection. This parameter is 396 required only if vismMastership is set to 'master (1)'. 397 " 398 ::= { vismChanCnfGrpEntry 13 } 399 400vismRemoteVci OBJECT-TYPE 401 SYNTAX Integer32 (0..65535) 402 MAX-ACCESS read-write 403 STATUS current 404 DESCRIPTION 405 "This object identifies the VCI, together with the 406 remote VPI and NSAP represents the remote end point 407 in this connection. This parameter is required only 408 if vismMastership is set to 'master (1)'. 409 " 410 ::= { vismChanCnfGrpEntry 14 } 411 412vismRemoteNSAP OBJECT-TYPE 413 SYNTAX OCTET STRING (SIZE(20)) 414 MAX-ACCESS read-write 415 STATUS current 416 DESCRIPTION 417 "This object identifies the remote NSAP address. 418 The NSAP is 20 bytes binary and is encoded as follows: 419 13 bytes : for prefix(node name) 420 2 bytes : for Cisco ID 421 1 byte : Reserved 422 3 bytes : for logical interface: 423 slot (1 byte) and port number (2 bytes), 424 1 byte : for SEL(Selector). 425 426 This parameter is required only if vismMastership is set 427 to 'master (1)'. This object contains the NSAP address 428 of the cross-connect (PXM/AUSM). 429 " 430 ::= { vismChanCnfGrpEntry 15 } 431 432vismMastership OBJECT-TYPE 433 SYNTAX INTEGER { 434 master (1), 435 slave (2), 436 unknown (3) 437 } 438 MAX-ACCESS read-write 439 STATUS current 440 DESCRIPTION 441 "'master (1)' : indicates the connection on the 442 channel is a master. 443 'slave (2)' : indicates the connection on the 444 channel is a slave. 445 'unknown (3)' : indicates the connection on the 446 channel is unknown. 447 " 448 DEFVAL { master } 449 ::= { vismChanCnfGrpEntry 16 } 450 451vismVpcFlag OBJECT-TYPE 452 SYNTAX INTEGER { 453 vcc (2) 454 } 455 MAX-ACCESS read-write 456 STATUS current 457 DESCRIPTION 458 "This object specifies the connection type which 459 is used by PXM to setup connection." 460 DEFVAL { vcc } 461 ::= { vismChanCnfGrpEntry 17 } 462 463vismConnServiceType OBJECT-TYPE 464 SYNTAX INTEGER { 465 cbr (1), 466 vbr-rt (2), 467 vbr-nrt (3), 468 vbr3-rt (4), 469 vbr2-rt (5), 470 vbr2-nrt (6), 471 vbr3-nrt (7) 472 } 473 MAX-ACCESS read-write 474 STATUS current 475 DESCRIPTION 476 "This specifies the class of service or service type 477 'cbr (1)' : Constant Bit Rate. 478 479 'vbr-rt (2)' : Variable Bit Rate 1 (Real Time) 480 although, VISM does not do any kind 481 of traffic shaping, the PVC has to be 482 specified as vbr-rt for PXM to treat 483 the connection as a VBR1 connection. 484 Variable Bit Rate is not currently 485 supported. 486 487 'vbr-nrt (3)' : Variable Bit Rate 1 (non real time) 488 the service type of the connection 489 cannot be modified once the PVC is 490 added. 491 492 'vbr3-rt (4)' : Variable Bit Rate 3 (Real Time) 493 although, VISM does not do any kind 494 of traffic shaping, the PVC has to be 495 specified as vbr3-rt for PXM to treat 496 the connection as a VBR3 connection. 497 Variable Bit Rate is not currently 498 supported. 499 500 'vbr2-rt (5)' : Variable Bit Rate 2 (Real Time) 501 although, VISM does not do any kind 502 of traffic shaping, the PVC has to be 503 specified as 'vbr2-rt' for PXM to treat 504 the connection as a VBR2 connection. 505 Variable Bit Rate is not currently 506 supported. 507 508 'vbr2-nrt (6)' : Variable Bit Rate 2 (non real time) 509 the service type of the connection 510 cannot be modified once the PVC 511 is added. 512 513 'vbr3-nrt (7)' : Variable Bit Rate 3 (non real time) 514 the service type of the connection 515 cannot be modified once the PVC 516 is added. 517 " 518 DEFVAL { cbr } 519 ::= { vismChanCnfGrpEntry 18 } 520 521 522vismRoutingPriority OBJECT-TYPE 523 SYNTAX Integer32 (1..15) 524 MAX-ACCESS read-write 525 STATUS current 526 DESCRIPTION 527 "This object is used by PXM to determine how 528 important this connection is when selecting 529 connections to route. 530 " 531 DEFVAL { 8 } 532 ::= { vismChanCnfGrpEntry 19 } 533 534vismMaxCost OBJECT-TYPE 535 SYNTAX Integer32 (1..2147483647) 536 MAX-ACCESS read-write 537 STATUS current 538 DESCRIPTION 539 "Maximum allowed cost. It is related to Cost Based 540 Routing. This is used by PXM so that it won't 541 choose a path with a cost greater than this 542 configured level. This is not necessary to be 543 provided in the connection setup request. 544 " 545 ::= { vismChanCnfGrpEntry 20 } 546 547vismRestrictTrunkType OBJECT-TYPE 548 SYNTAX INTEGER { 549 noresriction (1), 550 terrestrialTrunk (2), 551 sateliteTrunk (3) 552 } 553 MAX-ACCESS read-write 554 STATUS current 555 DESCRIPTION 556 "This object specifies trunk type for routing, 557 used by PXM. 558 559 'noresriction (1)' : No routing restriction, it can 560 be done on any trunk. 561 'terrestrialTrunk (2)' : It specifies the connection be 562 routed over terrestrial trunks. 563 'sateliteTrunk (3)' : It specifies the connection be routed 564 over satellite trunks. 565 " 566 DEFVAL { noresriction } 567 ::= { vismChanCnfGrpEntry 21 } 568 569vismConnPCR OBJECT-TYPE 570 SYNTAX Integer32 (1..100000) 571 UNITS "cells-per-second" 572 MAX-ACCESS read-write 573 STATUS current 574 DESCRIPTION 575 "This indicates bandwidth(Peak Cell Rate) in cells 576 per second from the local end i.e in the ingress 577 direction of the PVC. 578 579 For AAL2 PVCs, the PCR to be specified has to 580 be computed based on: 581 a) The no. of channels multiplexed on an AAL2 PVC 582 b) The Codec (Compression Algorithm) used. 583 c) The VAD factor 584 d) Partial fill factor. 585 586 For a AAL2 bearer PVC, the max value is 60,000 587 cps on E1 card and 50,000 cps on T1 card, and for 588 a signaling PVC, the max value is 400 cps. 589 590 This parameter can not be changed when there are 591 calls active on the PVC. 592 593 For variable bit rate connections the minimum 594 value of PCR is 15. 595 " 596 ::= { vismChanCnfGrpEntry 22 } 597 598vismConnPercentUtil OBJECT-TYPE 599 SYNTAX Integer32 (0..100) 600 UNITS "percentage" 601 MAX-ACCESS read-write 602 STATUS current 603 DESCRIPTION 604 "This is the expected long-term utilization 605 of the channel by this end-point. 606 " 607 DEFVAL { 100 } 608 ::= { vismChanCnfGrpEntry 23 } 609 610vismConnRemotePCR OBJECT-TYPE 611 SYNTAX Integer32 (1..100000) 612 UNITS "cells-per-second" 613 MAX-ACCESS read-write 614 STATUS current 615 DESCRIPTION 616 "This object indicates bandwidth(Peak Cell Rate) 617 from the other end i.e in the egress direction of 618 the PVC. 619 " 620 ::= { vismChanCnfGrpEntry 24 } 621 622vismConnRemotePercentUtil OBJECT-TYPE 623 SYNTAX Integer32 (0..100) 624 UNITS "percentage" 625 MAX-ACCESS read-write 626 STATUS current 627 DESCRIPTION 628 "This is the expected long-term utilization 629 of the channel by the other end-point. 630 " 631 DEFVAL { 100 } 632 ::= { vismChanCnfGrpEntry 25 } 633 634 635vismChanProtection OBJECT-TYPE 636 SYNTAX INTEGER { 637 protected (1), 638 unprotected (2) 639 } 640 MAX-ACCESS read-write 641 STATUS current 642 DESCRIPTION 643 "This object is used to configure a PVC protection 644 group (or redundant group) with the PVCs protecting 645 each other. Currently only two PVCs are supported 646 in a protection group. One of them is primary and 647 the other one is secondary. This is intended for 648 PVCs designated to carry control traffic and needs 649 to be protected. However the same PVC may also be 650 used to carry VoIP bearer traffic or other traffic. 651 652 Channels that are 'protected (1)' share the 653 following characteristics: 654 655 1. They are monitored for their health (including 656 emission of traps in case of state changes). 657 658 2. An active channel is protected by another 659 protected channel which is standby. This means 660 when an active channel fails, switchover to 661 another channel will happen if one is available. 662 663 3. It is also possible to do a forced switchover 664 (through locking). Even in the case of forced 665 switchover, switchover to another channel, which 666 is in standby, will happen. 667 668 4. Channels may be locked to force switchover and/or 669 to take the channel out of service in a graceful 670 fashion. 671 672 This object takes the default value of 'unprotected (2)' 673 during the creation of the table entry. Once the 674 primary and secondary channels have been created as 675 'unprotected (2)' channels, they can be 'protected (1)' 676 by doing a SET on the primary channel by specifying 677 the vismChanProtection as protected and by specifying 678 the vismChanFallbackLcn as the LCN number of the 679 secondary channel. 680 681 The sequence of operations for setting up the 682 'protection (1)' group is: 683 step 1: Add primary channel as unprotected 684 step 2: Add secondary channel as unprotected. 685 The PCR value for the secondary should be 686 the same as that of the primary. 687 step 3: Do a SET on the primary channel with 688 vismChanProtection set to 'protected (1)' 689 and vismChanFallbackLcn set to the 690 LCN number of the secondary channel. This 691 operation sets-up the protection group. The 692 primary channel becomes active and the 693 secondary channel becomes standby. 694 695 Please note that all the CAC related parameters 696 for the both the PVCs in the protecting group 697 should be same. In other words the vismChanCacMaster, 698 vismChanCarrierLossPolicy, vismChanCacRejectionPolicy, 699 VAD tolerance etc.. should have the same value 700 for the PVCs that are protecting each other, else 701 the set request to protect two channels will 702 be rejected. 703 704 Once the protection group is setup, if the active 705 channel fails, it automatically switches over to 706 the standby. The standby channel then becomes 707 active. 708 709 The channels can be removed from the protection 710 group by setting this object to unprotected. 711 712 Deletion of a 'protected (1)' channel is not 713 allowed. Channels have to be removed from 714 the protection group first before deleting. The 715 sequence of operations for deleting 'protected (1)' 716 channels are: 717 step 1: Remove the channels from the 718 protection group by setting 719 vismChanProtection to unprotected. 720 step 2: Delete secondary channel. 721 step 3: Delete primary channel. 722 " 723 DEFVAL { unprotected } 724 ::= { vismChanCnfGrpEntry 26 } 725 726vismChanPreference OBJECT-TYPE 727 SYNTAX INTEGER { 728 primary (1), 729 secondary (2) 730 } 731 MAX-ACCESS read-write 732 STATUS current 733 DESCRIPTION 734 "This object is used to identify a PVC as 735 primary or secondary. The primary PVC should 736 be added before the secondary. Similarly 737 secondary should be deleted before deleting 738 the primary. 739 740 When the protection group is setup, the primary 741 becomes active and secondary becomes standby. 742 The distinction of 'primary (1)' and 'secondary(2)' 743 is meaningful only if the PVC is 'protected (1)'. 744 " 745 DEFVAL { primary } 746 ::= { vismChanCnfGrpEntry 27 } 747 748vismChanActivityState OBJECT-TYPE 749 SYNTAX INTEGER { 750 active (1), 751 standby (2), 752 failed (3), 753 unknown (4) 754 } 755 MAX-ACCESS read-only 756 STATUS current 757 DESCRIPTION 758 "Indicates whether the PVC is currently used 759 to carry IP traffic or not, and whether it 760 has failed. 761 762 The possible states are: 763 764 'active (1)' : Channel is healthy and is currently 765 designated to carry IP traffic. A 766 channel can only be active if it is 767 also unlocked. 768 'standby (2)' : Channel is healthy but not designated 769 to carry IP traffic. 770 Switchover to this channel is allowed. 771 'failed (3)' : Channel is unable to carry any traffic. 772 'unknown (4)' : Channel is unprotected and hence 773 health of the channel is not monitored. 774 775 The default value upon creation of the row will be 776 'standby (2)' for a protected channel and 'unknown (4)' 777 for an unprotected channel. VISM may then transition 778 a 'protected (1)' channel to active if it determines 779 that this channel should be the one carrying the 780 traffic. 781 " 782 ::= { vismChanCnfGrpEntry 28 } 783 784vismChanLockingState OBJECT-TYPE 785 SYNTAX INTEGER { 786 unlock (1), 787 lock (2) 788 } 789 MAX-ACCESS read-write 790 STATUS current 791 DESCRIPTION 792 "This object is used to control the switchover 793 of protected channels. 794 795 'unlock (1)' : Transition state to unlock. A channel 796 which is in lock state has to be 797 brought to 'unlock (1)' state for it to 798 be available for switchover. 799 800 Whether a switchover to a channel is 801 allowed or not is dependent on both 802 vismChanActivityState and vismChanLockingState. 803 A switchover is allowed if its 804 vismChanActivityState is standby and its 805 vismChanLockingState is unlock. 806 807 Changing the vismChanLockingState to unlock does 808 not cause a change in the vismChanActivityState. 809 810 A channel which is in unlock state may carry 811 traffic depending on its activity state (active 812 or standby). 813 814 'lock (2)' : Transition state to 'lock (2)'. If the activity 815 state is active, it transitions to standby 816 and a switchover occurs to another channel 817 which is standby and 'unlocked (1)'. 818 819 When a channel is in 'lock (2)' state, 820 switchover to this channel is not allowed. 821 822 A channel which is in 'lock (2)' state, is 823 always in either standby or failed state. 824 Hence it will not carry any traffic. 825 826 Switchover to a channel which is in 827 'lock (2)' state is not allowed. 828 829 This object can be set to 'locked (2)' to force a 830 switchover and/or to perform maintenance operations 831 related to that channel. 832 833 A channel that is 'unprotected' will always be in 834 'unlock (1)' state. It can not be set to 'lock (2)' 835 state. 836 " 837 DEFVAL { unlock } 838 ::= { vismChanCnfGrpEntry 29 } 839 840-- The following three objects are defined for VBR 841-- type connections only. Even though no special 842-- processing is done for VBR connections on VISM, 843-- the following parameters are still required for 844-- making a PVC connection with the AUSM card, which 845-- is the other end of the PVC in the trunking application. 846 847vismChanScrIngress OBJECT-TYPE 848 SYNTAX Integer32 (1..100000) 849 UNITS "cells-per-second" 850 MAX-ACCESS read-write 851 STATUS current 852 DESCRIPTION 853 "This object identifies the SCR (Sustained Cell Rate) 854 for the PVC in the ingress direction. SCR is used 855 for vbr connection types only. Traffic shaping 856 is not done on the VISM card, this value is useful 857 for setting up the parameters for the end-to-end 858 PVC. This value is expressed in units of cells 859 per second. 860 861 If the user provides a value that is greater than 862 vismConnPCR then the SET request will be rejected. 863 864 For vbr connections the allowed range of values 865 of SCR is from 15 - PCR. 866 " 867 ::= { vismChanCnfGrpEntry 30 } 868 869vismChanMbsIngress OBJECT-TYPE 870 SYNTAX Integer32 (1..2147483647) 871 UNITS "cells-per-second" 872 MAX-ACCESS read-write 873 STATUS current 874 DESCRIPTION 875 "This object defines the MBS (Max. Burst Size). 876 This object is meaningful for VBR connections 877 only. 878 879 This object defines the MBS value for the ingress 880 direction of the PVC. The MBS value cannot 881 be greater than 10 times vismChanScrIngress value. 882 " 883 ::= { vismChanCnfGrpEntry 31 } 884 885vismChanClrIngress OBJECT-TYPE 886 SYNTAX Integer32 (1..2147483647) 887 MAX-ACCESS read-write 888 STATUS current 889 DESCRIPTION 890 "This object defines the CLR (Cell Loss Ratio) for 891 the PVC in ingress direction. This field is also 892 meaningful for VBR connections only. 893 " 894 ::= { vismChanCnfGrpEntry 32 } 895 896vismChanCdvt OBJECT-TYPE 897 SYNTAX Integer32 (1..30) 898 MAX-ACCESS read-write 899 STATUS current 900 DESCRIPTION 901 "This object defines the CDVT (Cell Delay Variation 902 Tolerance) for the connection. CDVT is useful for 903 determining the playout buffer size in the DSPs. 904 This object is applicable only in AAL1 adaptation. 905 For AAL2, the equivalent of this parameter, known 906 as PDVT (Packet Delay Variation Tolerance) is 907 internally derived. 908 " 909 DEFVAL { 2 } 910 ::= { vismChanCnfGrpEntry 33 } 911 912vismConnPCREgress OBJECT-TYPE 913 SYNTAX Integer32 (1..100000) 914 UNITS "cells-per-second" 915 MAX-ACCESS read-write 916 STATUS current 917 DESCRIPTION 918 "This object defines the PCR (Peak Cell Rate) for 919 the PVC in egress direction. PCR is applicable 920 to all connection service types ie. CBR, RT-VBR 921 and nRT-VBR. 922 " 923 ::= { vismChanCnfGrpEntry 34 } 924 925vismChanScrEgress OBJECT-TYPE 926 SYNTAX Integer32 (1..100000) 927 UNITS "cells-per-second" 928 MAX-ACCESS read-write 929 STATUS current 930 DESCRIPTION 931 "This object defines the SCR (Sustained Cell 932 Rate) for the PVC in the egress direction. 933 SCR is used for VBR connection types only. 934 No traffic shaping is done on the VISM card, 935 this value is useful for setting up the 936 parameters for the end-to-end PVC. 937 " 938 ::= { vismChanCnfGrpEntry 35 } 939 940vismChanMbsEgress OBJECT-TYPE 941 SYNTAX Integer32 (1..2147483647) 942 UNITS "cells-per-second" 943 MAX-ACCESS read-write 944 STATUS current 945 DESCRIPTION 946 "This object defines the MBS (Max. Burst Size) 947 for a PVC in egress direction. This object is 948 meaningful for VBR connections only. 949 " 950 ::= { vismChanCnfGrpEntry 36 } 951 952vismChanClrEgress OBJECT-TYPE 953 SYNTAX Integer32 (1..2147483647) 954 MAX-ACCESS read-write 955 STATUS current 956 DESCRIPTION 957 "This object defines the CLR (Cell Loss Ratio) 958 for the PVC in egress direction. This field 959 is also meaningful for VBR connections only. 960 " 961 ::= { vismChanCnfGrpEntry 37 } 962 963vismChanApplication OBJECT-TYPE 964 SYNTAX INTEGER { 965 control (1), 966 bearer (2), 967 signaling (3) 968 } 969 MAX-ACCESS read-write 970 STATUS current 971 DESCRIPTION 972 "This object defines the application that the 973 LCN is used for. There are 4 types of PVCs 974 known so far: 975 976 'control (1)' : Control PVC used for carrying 977 control traffic only (XGCP packets). 978 'bearer (2)' : Bearer PVC, used for carrying 979 voice payload traffic only. 980 'signaling(3)' : Signaling PVC, used for carrying 981 the signaling protocol messages. 982 " 983 DEFVAL { bearer } 984 ::= { vismChanCnfGrpEntry 38 } 985 986vismChanFallbackLcn OBJECT-TYPE 987 SYNTAX Integer32 (131..510) 988 MAX-ACCESS read-write 989 STATUS current 990 DESCRIPTION 991 "This object defines the LCN to be used as 992 a fallback mechanism, in case the primary 993 PVC fails. This is applicable if the PVC 994 is configured for redundancy. The redundancy 995 is applicable for both applications i.e 996 control PVC and bearer PVC. 997 998 This object is applicable only if the 999 vismChanProtection is set to 'protected'. 1000 It is mandatory if the PVC is protected. 1001 " 1002 ::= { vismChanCnfGrpEntry 39 } 1003 1004vismChanReroute OBJECT-TYPE 1005 SYNTAX TruthValue 1006 MAX-ACCESS read-write 1007 STATUS current 1008 DESCRIPTION 1009 "This is used by the administrator to 1010 trigger the re-routing of the connection. 1011 The re-routing takes effect, when this object 1012 is set to 'true (1)'. When set to 'false (2)', 1013 no action is taken. A get on this object always 1014 returns 'false (2)'. 1015 " 1016 DEFVAL { false } 1017 ::= { vismChanCnfGrpEntry 40 } 1018 1019vismFarEndAddressType OBJECT-TYPE 1020 SYNTAX INTEGER { 1021 notapplicable (1), 1022 nsap (2), 1023 e164 (3), 1024 gwid (4), 1025 unspecified (5) 1026 } 1027 MAX-ACCESS read-write 1028 STATUS current 1029 DESCRIPTION 1030 "The address type can be one of five types: 1031 NSAP, E164, GWID, notapplicable or unspecified. 1032 It determines which object contains the scope 1033 for the VCCI, i.e. whether the VCCI needs to 1034 be unique relative to NSAP, E164 address or GWID. 1035 'notApplicable (1)' : no valid addresses are 1036 required and no validation 1037 of VCCI uniqueness for a 1038 remote address is performed. 1039 'nsap (2)' : object vismFarEndNSAPAddress 1040 contains the address. 1041 'e164 (3)' : object vismFarEndE164Address 1042 contains the address. 1043 'gwid (4)' : object vismFarEndGWIDAddress 1044 contains the address. 1045 'unspecified (5)' : no valid addresses are required 1046 but VCCI needs to be unique. 1047 1048 While this object is writeable, it is recommended 1049 not to change the value of this object once it 1050 has been created. However, upon modification to 1051 any value other than notapplicable, it will be 1052 ensured that the resulting combination of VCCI 1053 and remote address is unique. Requests that would 1054 result in a non-unique combination will be rejected. 1055 1056 If the vismFarEndAddressType is one of 'nsap', 1057 'e164' or 'gwid', the far end address has to be 1058 specified. 1059 " 1060 DEFVAL { notapplicable } 1061 ::= { vismChanCnfGrpEntry 41 } 1062 1063vismFarEndE164Address OBJECT-TYPE 1064 SYNTAX DisplayString (SIZE(1..15)) 1065 MAX-ACCESS read-write 1066 STATUS current 1067 DESCRIPTION 1068 "The E.164 address of the far end peer. The 1069 address is expressed as decimal numbers with 1070 up to 15 digits. If the vismFarEndAddressType 1071 is different from e164, this object is not 1072 applicable and it should be ignored. 1073 1074 This object serves as the scope for VCCI 1075 identifiers (vismVCCI), if vismFarEndAddressType 1076 is equal to e164. In that case, the combination 1077 of (vismFarEndE164Address, vismVCCI) will always 1078 be unique for any given agent. It thus constitutes 1079 a label denoting the scope for a VCCI address 1080 space; it has no purpose otherwise. 1081 1082 While this object is writeable, it is recommended 1083 not to change the value of this object once it 1084 has been created. However, upon modification, it 1085 will be ensured that the resulting combination of 1086 VCCI and remote E164 address is unique (as long as 1087 the remote address type is E164). Requests that 1088 would result in a non-unique combination will be 1089 rejected. Beyond this, there are no other integrity 1090 constraints that will be enforced for this object. 1091 This includes network-level consistency with the 1092 actual address of the remote peer. 1093 1094 The value of this object cannot be modified when 1095 there are active calls on this PVC. The valid 1096 characters allowed are '0..9'. 1097 " 1098 ::= { vismChanCnfGrpEntry 42 } 1099 1100vismFarEndGWIDAddress OBJECT-TYPE 1101 SYNTAX DisplayString (SIZE(1..64)) 1102 MAX-ACCESS read-write 1103 STATUS current 1104 DESCRIPTION 1105 "The gateway ID of the far end peer. The address 1106 is expressed as ASCII characters. If the 1107 vismFarEndAddressType is different from gwid(4), 1108 this object is not applicable and it should 1109 be ignored. 1110 1111 This object serves as the scope for VCCI identifiers 1112 (vismVCCI) if vismFarEndAddressType is equal to 1113 gwid(4). In that case, the combination of 1114 (vismFarEndGWIDAddress, vismVCCI) will always be 1115 unique for any given agent. It thus constitutes 1116 a label denoting the scope for a VCCI address space; 1117 it has no purpose otherwise. 1118 1119 While this object is writeable, it is recommended 1120 not to change the value of this object once it 1121 has been created. However, upon modification, 1122 it will be ensured that the resulting combination 1123 of VCCI and far end GWID address is unique (as 1124 long as the vismFarEndAddress type is GWID). 1125 Requests that would result in a non-unique 1126 combination will be rejected. Beyond this, there 1127 are no other integrity constraints that will be 1128 enforced for this object. This includes 1129 network-level consistency with the actual address 1130 of the remote peer. 1131 1132 The value of this object cannot be modified 1133 when there are active calls on this PVC. All 1134 ASCII characters are allowed by this object. 1135 " 1136 ::= { vismChanCnfGrpEntry 43 } 1137 1138vismFarEndNSAPAddress OBJECT-TYPE 1139 SYNTAX OCTET STRING (SIZE(20)) 1140 MAX-ACCESS read-write 1141 STATUS current 1142 DESCRIPTION 1143 "This object contains the 20 byte NSAP address 1144 of the far end peer. If the vismFarEndAddressType 1145 is different from 'nsap', this object is not 1146 applicable and it should be ignored. 1147 1148 This object serves as the scope for VCCI 1149 identifiers (vismVCCI) if vismFarEndAddressType 1150 is equal to 'nsap'. In that case, the combination 1151 of (vismFarEndNSAPAddress, vismVCCI) will always 1152 be unique for any given agent. It thus constitutes 1153 a label denoting the scope for a VCCI address 1154 space; it has no purpose otherwise. 1155 1156 While this object is writeable, it is recommended 1157 not to change the value of this object once it has 1158 been created. However, upon modification, it will 1159 be ensured that the resulting combination of VCCI 1160 and far end NSAP address is unique (as long as 1161 the far end address type is GWID). Requests that 1162 would result in a non-unique combination will 1163 be rejected. Beyond this, there are no other 1164 integrity constraints that will be enforced for 1165 this object. This includes network-level 1166 consistency with the actual address of the remote 1167 peer. 1168 1169 The value of this object cannot be modified when 1170 there are active calls on this PVC. 1171 1172 When the user adds a connection, by default the 1173 value of this object will be set to 1174 vismRemoteNSAP, unless the user specifies a 1175 value for this object. This object is 1176 represented as hex (0 .. 9,A .. F). 1177 " 1178 ::= {vismChanCnfGrpEntry 44 } 1179 1180vismVCCI OBJECT-TYPE 1181 SYNTAX Integer32 (0..65535) 1182 MAX-ACCESS read-write 1183 STATUS current 1184 DESCRIPTION 1185 "The VCCI, or Virtual Circuit Connection 1186 Identifier, is a variable that identifies a 1187 virtual circuit connection between two nodes. 1188 A virtual circuit connection, or VCC, consists of 1189 one virtual circuit link or a series of concatenated 1190 virtual circuit links. In its most common usage, 1191 the value of the VCCI is unique between the nodes 1192 at the extremities of the virtual circuit 1193 connection, but not on a network-wide basis. Hence, 1194 its value needs to be qualified by the ATM 1195 addresses of these end nodes. At one of these 1196 end nodes, its value needs to be qualified by the 1197 ATM address of the far-end node. Some applications 1198 can extend this definition to make the VCCI value 1199 unique on a network-wide basis. This is specially 1200 possible when VCCIs are administered from a management 1201 system and not locally assigned by a node. 1202 1203 In this MIB, the VCCI serves as a label to be assigned 1204 by an external application. VCCIs need to be unique 1205 for a given remote peer, however, the same VCCI can 1206 be reused for different remote peers. Accordingly, 1207 the combination of (remote address, VCCI) will always 1208 be unique for any given agent. This allows a controller 1209 to refer to a VC by the VCCI and remote peer address, 1210 in contrast to VPI/VCI and port. It thus constitutes 1211 a convenience feature, providing an alternative 1212 identification scheme for a VC which is managed by 1213 an outside user, such as a management system. 1214 1215 The remote peer address can be specified in NSAP, 1216 E.164, or GWID format, as indicated by the address 1217 type (vismRemoteAddressType). Depending on the 1218 address type specified, uniqueness will be relative 1219 to NSAP, E.164 address, or GWID. 1220 1221 It is recommended not to change the value of this 1222 object once it has been created. However, 1223 upon modification, it will be ensured that the 1224 resulting combination of VCCI and remote address 1225 is unique. Requests that would result in a 1226 non-unique combination will be rejected. 1227 Beyond this, there are no other integrity constraints 1228 that will be enforced for this object. This includes 1229 network-level consistency whether the remote peer, 1230 or an external controller, use the same VCCI 1231 designation for the VC. 1232 " 1233 DEFVAL { 0 } 1234 ::= { vismChanCnfGrpEntry 45 } 1235 1236vismConnAdminStatus OBJECT-TYPE 1237 SYNTAX INTEGER { 1238 up (1), 1239 down (2) 1240 } 1241 MAX-ACCESS read-write 1242 STATUS current 1243 DESCRIPTION 1244 "This object specifies channel administration status. 1245 1246 'up (1)' : Indicates the status channel is up. 1247 'down (2)' : Indicates the channel is down or 1248 out of service. 1249 " 1250 DEFVAL { up } 1251 ::= { vismChanCnfGrpEntry 46 } 1252 1253vismChanPrefRouteId OBJECT-TYPE 1254 SYNTAX Unsigned32 (0..65535) 1255 MAX-ACCESS read-write 1256 STATUS current 1257 DESCRIPTION 1258 "This object serves to associate a preferred 1259 route with a connection. 1260 1261 The value of '0' means no preferred route is 1262 associated with this connection. 1263 1264 Usage: 1265 - If the value of this set to 0, the object 1266 vismChanDirectRoute is automatically set to FALSE by 1267 the agent. 1268 - The preferred route is defined in cwaPrefRouteConfTable 1269 object." 1270 REFERENCE 1271 "cwaPrefRouteConfTable from CISCO-WAN-ATM-PREF-ROUTE-MIB" 1272 DEFVAL { 0 } 1273 ::= { vismChanCnfGrpEntry 47 } 1274 1275vismChanDirectRoute OBJECT-TYPE 1276 SYNTAX TruthValue 1277 MAX-ACCESS read-write 1278 STATUS current 1279 DESCRIPTION 1280 "This object serves to associate a preferred 1281 route as directed route (corresponds to the preferred 1282 route object vismChanPrefRouteId). 1283 1284 A directed route specifies that the associated preferred 1285 route is the only permission route for the connection to 1286 take. Should the associated preferred route be unavailable, 1287 the connection is failed. 1288 1289 The object is not applicable if there is no associated 1290 preferred route with the connection or in other words if 1291 the object vismChanPrefRouteId has a value of 0." 1292 DEFVAL { false } 1293 ::= { vismChanCnfGrpEntry 48 } 1294 1295vismChanAisSuppression OBJECT-TYPE 1296 SYNTAX TruthValue 1297 MAX-ACCESS read-write 1298 STATUS current 1299 DESCRIPTION 1300 "AIS suppression can be enabled(true) or disabled(false). 1301 When AIS suppression is disabled on a PVC, ATM network 1302 alarms on that PVC will immediately propagate to the 1303 TDM side and cause T1/E1 line alarms. When AIS suppression 1304 is enabled on a PVC, ATM network alarms will not propagate 1305 to the TDM side and cause T1/E1 line alarms for the 1306 duration of the AIS delay time setting. However, if the 1307 ATM network alarms persist causing the AIS delay timer to 1308 expire, the ATM network alarms will be allowed to propagate 1309 onto the TDM side and cause T1/E1 line alarms." 1310 DEFVAL { false } 1311 ::= { vismChanCnfGrpEntry 49 } 1312 1313vismChanAisDelayTime OBJECT-TYPE 1314 SYNTAX Unsigned32(1..60) 1315 MAX-ACCESS read-write 1316 STATUS current 1317 DESCRIPTION 1318 "This object defines the duration for which ATM network 1319 alarms on this PVC will be prevented from propagating 1320 onto the TDM side when AIS suppression is enabled." 1321 DEFVAL { 30 } 1322 ::= { vismChanCnfGrpEntry 50 } 1323 1324vismChanUserMaxPCRBandwidth OBJECT-TYPE 1325 SYNTAX Unsigned32(1..100000) 1326 UNITS "cells-per-second" 1327 MAX-ACCESS read-write 1328 STATUS current 1329 DESCRIPTION 1330 "This indicates a user configured bandwidth 1331 (Peak Cell Rate) in cells per second from the local 1332 end i.e in the ingress direction of the PVC. 1333 For a VoIP bearer PVC, the max value is 75600 cps. 1334 For a VoIP control PVC, the max value is 24400 cps. 1335 For AAL2 PVCs, the PCR to be specified has to be computed 1336 based on: 1337 a) The no. of channels multiplexed on an AAL2 PVC 1338 b) The Codec (Compression Algorithm) used. 1339 c) The VAD factor 1340 d) Partial fill factor. 1341 1342 For a AAL2 bearer PVC, the max value is 60,000 cps on E1 1343 card and 50,000 cps on T1 card. For a signaling PVC, the 1344 max value is 400 cps. 1345 1346 This parameter can not be changed when there are calls 1347 active on the PVC. 1348 1349 For a VOIP bearer PVC the max allowed value is 80000. 1350 For a VOIP control PVC the max allowed value is 20000. 1351 increased as we will allow 248 endpoints. 1352 1353 For Aal2 the values remain the same 50000/60000. 1354 For vbr connections the minimum value of PCR is 15. 1355 " 1356::= { vismChanCnfGrpEntry 51 } 1357 1358vismChanUserMaxScrIngress OBJECT-TYPE 1359 SYNTAX Unsigned32(1..100000) 1360 UNITS "cells-per-second" 1361 MAX-ACCESS read-write 1362 STATUS current 1363 DESCRIPTION 1364 "This object defines a user configured SCR (Sustained 1365 Cell Rate) for the PVC. SCR is used for vbr connection 1366 types only. Although, based on the value of SCR, any kind 1367 of traffic shaping is not done on the VISM card, this value 1368 is useful for setting up the parameters for the end-to-end 1369 PVC. This value is expressed in units of cells per second. 1370 This object defines the SCR value for the ingress direction 1371 of the PVC. 1372 For a VOIP bearer PVC the max value is 80000. 1373 For a VOIP control PVC the max value is 20000 increased as 1374 we will allow 248 endpoints. 1375 For Aal2 the values remain the same (50000/60000). 1376 If the user provides a value that is greater than vismConnPCR 1377 then the SET request will be rejected. 1378 For vbr connections the allowed range of values of SCR is from 1379 15 - PCR." 1380::= { vismChanCnfGrpEntry 52 } 1381 1382vismChanUserMaxMbsIngress OBJECT-TYPE 1383 SYNTAX Unsigned32(1..2147483647) 1384 UNITS "cells-per-second" 1385 MAX-ACCESS read-write 1386 STATUS current 1387 DESCRIPTION 1388 "This object defines the user configured MBS (Maximum 1389 Burst Size). 1390 This object is meaningful for VBR connections only. 1391 This object defines the MBS value for the ingress direction 1392 of the PVC. 1393 The MBS value cannot be greater than 10 times 1394 vismChanScrIngress value." 1395::= { vismChanCnfGrpEntry 53 } 1396 1397vismChanUserMinPCRBandwidth OBJECT-TYPE 1398 SYNTAX Unsigned32(1..100000) 1399 UNITS "cells-per-second" 1400 MAX-ACCESS read-write 1401 STATUS current 1402 DESCRIPTION 1403 "This indicates a user configured minimum number of cells 1404 that will be required to keep the connection up." 1405::= { vismChanCnfGrpEntry 54 } 1406 1407vismChanUserPcrNumber OBJECT-TYPE 1408 SYNTAX INTEGER { 1409 userConfiguredMaxBandwidth (1), 1410 userConfiguredMinBandwidth (2) 1411 } 1412 MAX-ACCESS read-write 1413 STATUS current 1414 DESCRIPTION 1415 "This indicates which bandwidth value the user has chosen. 1416 This value cannot be specified when adding the connection. 1417 It can be modified once the connection has been added. 1418 If it has a value of userConfiguredMaxBandwidth, it 1419 indicates that the bandwidth configured at the time of 1420 adding the connection will be used. 1421 If it takes a value of userConfiguredMinBandwidth then 1422 the minimum bandwidth will be applied as the current PCR 1423 value. A derived minimum value, from this value, will be 1424 applied for SCR and MBS values." 1425DEFVAL { userConfiguredMaxBandwidth } 1426::= { vismChanCnfGrpEntry 55 } 1427 1428vismChanNumNextAvailable OBJECT-TYPE 1429 SYNTAX Integer32 (0..510) 1430 MAX-ACCESS read-only 1431 STATUS current 1432 DESCRIPTION 1433 "This object contains the next unused channel number. 1434 When channels are available the range is 32..510. 1435 This number can be used in channel config table. 1436 Value 0 for this object indicates that 1437 no more channels are available." 1438 ::= { vismChanCnfGrp 2 } 1439 1440 1441-- ------------------------------------------------------------------ 1442-- 1443-- VISM specific Channel State group 1444-- 1445-- ------------------------------------------------------------------ 1446 1447 1448-- ------------------------------------------------------------------ 1449-- For VoIP support we need only one PVC between the 1450-- VISM card and the PXM. 1451-- This PVC is added on the network port=255, which 1452-- has the portSpeed=192*64 kbps for VISM-8T1 and 1453-- 240 * 64 kbps for VISM-8E1. 1454-- Note that this network port is pre-configured on 1455-- the VISM card, and no need to configure it. 1456-- ------------------------------------------------------------------ 1457 1458vismChanStateGrpTable OBJECT-TYPE 1459 SYNTAX SEQUENCE OF VismChanStateGrpEntry 1460 MAX-ACCESS not-accessible 1461 STATUS current 1462 DESCRIPTION 1463 "voice connection state table." 1464 ::= { vismChanStateGrp 1 } 1465 1466vismChanStateGrpEntry OBJECT-TYPE 1467 SYNTAX VismChanStateGrpEntry 1468 MAX-ACCESS not-accessible 1469 STATUS current 1470 DESCRIPTION 1471 "An entry for each channel (PVC)." 1472 INDEX { vismStateChanNum } 1473 ::= { vismChanStateGrpTable 1 } 1474 1475VismChanStateGrpEntry ::= 1476 SEQUENCE { 1477 vismStateChanNum Integer32, 1478 vismChanState INTEGER, 1479 vismChanXmtATMState INTEGER, 1480 vismChanRcvATMState INTEGER, 1481 vismChanStatusBitMap Integer32 1482 } 1483 1484vismStateChanNum OBJECT-TYPE 1485 SYNTAX Integer32 (131..510) 1486 MAX-ACCESS read-only 1487 STATUS current 1488 DESCRIPTION 1489 "Refers to the channel Number LCN. 1490 " 1491 ::= { vismChanStateGrpEntry 1 } 1492 1493vismChanState OBJECT-TYPE 1494 SYNTAX INTEGER { 1495 notConfigured (1), 1496 okay (2), 1497 alarm (3) 1498 } 1499 MAX-ACCESS read-only 1500 STATUS current 1501 DESCRIPTION 1502 "This object indicates the channel status. 1503 1504 'notConfigured (1)' : Indicates the channel is not 1505 configured. 1506 'okay (2)' : Indicates the channel is healthy, 1507 i.e not 1508 experiencing error condition. 1509 'alarm (3)' : Indicates the channel is in alarm state. 1510 " 1511 ::= { vismChanStateGrpEntry 2 } 1512 1513vismChanXmtATMState OBJECT-TYPE 1514 SYNTAX INTEGER { 1515 other (1), 1516 normal (2), 1517 sendingAIS (3), 1518 sendingFERF (4) 1519 } 1520 MAX-ACCESS read-only 1521 STATUS current 1522 DESCRIPTION 1523 "This object indicates the transmit state of channel 1524 on the ATM side(towards the network). 1525 1526 'other (1)' : Indicates the transmit channel is in 1527 unknown state. 1528 'normal (2)' : Indicates the transmit channel is in a 1529 normal state. 1530 'sendingAIS (3)' : Indicates the transmit channel is sending 1531 AIS alarm toward the network side. 1532 'sendingFERF (4)' : Indicates the transmit channel is sending 1533 Far End Receive Failure alarm cells to 1534 the network side. 1535 " 1536 ::= { vismChanStateGrpEntry 3 } 1537 1538vismChanRcvATMState OBJECT-TYPE 1539 SYNTAX INTEGER { 1540 other (1), 1541 normal (2), 1542 receivingAIS (3), 1543 receivingFERF (4), 1544 oamFailure (5) 1545 } 1546 MAX-ACCESS read-only 1547 STATUS current 1548 DESCRIPTION 1549 "This object indicates the receive state of channel 1550 on the ATM side(from the network). 1551 1552 'other (1)' : Indicates the receive channel is 1553 in unknown state. 1554 'normal (2)' : Indicates the receive channel is 1555 in a normal state. 1556 'receivingAIS (3)' : Indicates the receive channel is 1557 receiving AIS alarm cells from the 1558 network side. 1559 'receivingFERF (4)' : Indicates the receive channel is 1560 receiving Far End Receive Failure 1561 alarm cells from the network side. 1562 'oamFailure (5)' : Indicates that the receive channel 1563 has failed OAM end-to-end loopback. 1564 " 1565 ::= { vismChanStateGrpEntry 4 } 1566 1567vismChanStatusBitMap OBJECT-TYPE 1568 SYNTAX Integer32 (0..255) 1569 MAX-ACCESS read-only 1570 STATUS current 1571 DESCRIPTION 1572 "This object indicates the consolidated bit map of 1573 the channel alarm state. 1574 1575 Individual bit positions are as defined below, all reserved 1576 bits will be set to zero. 1577 1578 Bit position Fail/Alarm Reason 1579 ------------ ---------- ------ 1580 0 Alarm Reserved 1581 1 Alarm n/w side CC failure/AIS/RDI Rx 1582 2 Fail Conditioned (Abit from n/w) 1583 3 Alarm Reserved 1584 4 Fail Reserved 1585 5 Fail Reserved 1586 6 Alarm Reserved 1587 7 Alarm Reserved 1588 1589 Fail bitmap mask : 0x34 1590 Alarm bitmap mask: 0xCB 1591 " 1592 1593 ::= { vismChanStateGrpEntry 5 } 1594 1595 1596-- conformance information 1597 1598ciscoVismConnMIBConformance OBJECT IDENTIFIER ::= 1599 { ciscoVismConnMIB 2 } 1600 1601ciscoVismConnMIBGroups OBJECT IDENTIFIER ::= 1602 { ciscoVismConnMIBConformance 1 } 1603ciscoVismConnMIBCompliances OBJECT IDENTIFIER ::= 1604 { ciscoVismConnMIBConformance 2 } 1605 1606 1607-- compliance statements 1608 1609ciscoVismConnCompliance MODULE-COMPLIANCE 1610 STATUS deprecated --Replaced by ciscoVismConnComplianceRev1 1611 DESCRIPTION 1612 "The compliance statement for SNMP entities 1613 which support Connections in VISM Module. 1614 " 1615 MODULE -- this module 1616 MANDATORY-GROUPS { 1617 ciscoVismConnGroup, 1618 ciscoVismConnStateGroup 1619 } 1620 ::= { ciscoVismConnMIBCompliances 1 } 1621 1622ciscoVismConnComplianceRev1 MODULE-COMPLIANCE 1623 STATUS current 1624 DESCRIPTION 1625 "The compliance statement for SNMP entities 1626 which support Connections in VISM Module." 1627 MODULE -- this module 1628 MANDATORY-GROUPS { 1629 ciscoVismConnGroupRev1, 1630 ciscoVismConnStateGroup 1631 } 1632 ::= { ciscoVismConnMIBCompliances 2 } 1633 1634ciscoVismConnGroup OBJECT-GROUP 1635 OBJECTS { 1636 vismChanNumNextAvailable, 1637 vismCnfChanNum, 1638 vismChanRowStatus, 1639 vismChanPortNum, 1640 vismChanLocRmtLpbkState, 1641 vismChanTestType, 1642 vismChanTestState, 1643 vismChanRTDResult, 1644 vismChanPvcType, 1645 vismChanConnType, 1646 vismLocalVpi, 1647 vismLocalVci, 1648 vismLocalNSAP, 1649 vismRemoteVpi, 1650 vismRemoteVci, 1651 vismRemoteNSAP, 1652 vismMastership, 1653 vismVpcFlag, 1654 vismConnServiceType, 1655 vismRoutingPriority, 1656 vismMaxCost, 1657 vismRestrictTrunkType, 1658 vismConnPCR, 1659 vismConnPercentUtil, 1660 vismConnRemotePCR, 1661 vismConnRemotePercentUtil, 1662 vismChanProtection, 1663 vismChanPreference, 1664 vismChanActivityState, 1665 vismChanLockingState, 1666 vismChanScrIngress, 1667 vismChanMbsIngress, 1668 vismChanCdvt , 1669 vismChanClrIngress, 1670 vismConnPCREgress , 1671 vismChanScrEgress, 1672 vismChanMbsEgress, 1673 vismChanClrEgress, 1674 vismChanApplication, 1675 vismChanFallbackLcn, 1676 vismChanReroute, 1677 vismFarEndAddressType, 1678 vismFarEndE164Address, 1679 vismFarEndGWIDAddress, 1680 vismFarEndNSAPAddress, 1681 vismVCCI, 1682 vismConnAdminStatus 1683 } 1684 STATUS deprecated --Replaced by ciscoVismConnGroupRev1 1685 DESCRIPTION 1686 "A collection of objects providing information 1687 applicable to connections in VISM Module. 1688 " 1689 ::= { ciscoVismConnMIBGroups 1 } 1690 1691ciscoVismConnStateGroup OBJECT-GROUP 1692 OBJECTS { 1693 vismStateChanNum, 1694 vismChanState, 1695 vismChanXmtATMState, 1696 vismChanRcvATMState, 1697 vismChanStatusBitMap 1698 } 1699 STATUS current 1700 DESCRIPTION 1701 "A collection of objects related to state 1702 of VISM connections. 1703 " 1704 ::= { ciscoVismConnMIBGroups 2 } 1705 1706ciscoVismConnGroupRev1 OBJECT-GROUP 1707 OBJECTS { 1708 vismChanNumNextAvailable, 1709 vismCnfChanNum, 1710 vismChanRowStatus, 1711 vismChanPortNum, 1712 vismChanLocRmtLpbkState, 1713 vismChanTestType, 1714 vismChanTestState, 1715 vismChanRTDResult, 1716 vismChanPvcType, 1717 vismChanConnType, 1718 vismLocalVpi, 1719 vismLocalVci, 1720 vismLocalNSAP, 1721 vismRemoteVpi, 1722 vismRemoteVci, 1723 vismRemoteNSAP, 1724 vismMastership, 1725 vismVpcFlag, 1726 vismConnServiceType, 1727 vismRoutingPriority, 1728 vismMaxCost, 1729 vismRestrictTrunkType, 1730 vismConnPCR, 1731 vismConnPercentUtil, 1732 vismConnRemotePCR, 1733 vismConnRemotePercentUtil, 1734 vismChanProtection, 1735 vismChanPreference, 1736 vismChanActivityState, 1737 vismChanLockingState, 1738 vismChanScrIngress, 1739 vismChanMbsIngress, 1740 vismChanCdvt , 1741 vismChanClrIngress, 1742 vismConnPCREgress , 1743 vismChanScrEgress, 1744 vismChanMbsEgress, 1745 vismChanClrEgress, 1746 vismChanApplication, 1747 vismChanFallbackLcn, 1748 vismChanReroute, 1749 vismFarEndAddressType, 1750 vismFarEndE164Address, 1751 vismFarEndGWIDAddress, 1752 vismFarEndNSAPAddress, 1753 vismVCCI, 1754 vismConnAdminStatus, 1755 vismChanPrefRouteId, 1756 vismChanDirectRoute, 1757 vismChanAisSuppression, 1758 vismChanAisDelayTime, 1759 vismChanUserMaxPCRBandwidth, 1760 vismChanUserMaxScrIngress, 1761 vismChanUserMaxMbsIngress, 1762 vismChanUserMinPCRBandwidth, 1763 vismChanUserPcrNumber 1764 } 1765 STATUS current 1766 DESCRIPTION 1767 "A collection of objects providing information 1768 applicable to connections in VISM Module." 1769 ::= { ciscoVismConnMIBGroups 3 } 1770 1771END 1772 1773 1774