1-- ***************************************************************** 2-- CISCO-RF-MIB.my: 3-- Descriptions of managed objects for the Redundancy Framework 4-- (RF) subsystem. 5-- 6-- August 2000, Timothy Kurnik and Bo Berry 7-- December 2001, Liwei Wang 8-- 9-- Copyright (c) 2000-2006 by Cisco Systems Inc. 10-- All rights reserved. 11-- **************************************************************** 12 13CISCO-RF-MIB DEFINITIONS ::= BEGIN 14 15IMPORTS 16 MODULE-IDENTITY, 17 OBJECT-TYPE, 18 NOTIFICATION-TYPE, 19 Counter32, 20 Integer32, 21 Unsigned32 22 FROM SNMPv2-SMI 23 MODULE-COMPLIANCE, 24 NOTIFICATION-GROUP, 25 OBJECT-GROUP 26 FROM SNMPv2-CONF 27 TEXTUAL-CONVENTION, 28 TruthValue, 29 DateAndTime, 30 TimeStamp, 31 TimeInterval 32 FROM SNMPv2-TC 33 sysUpTime 34 FROM SNMPv2-MIB 35 SnmpAdminString 36 FROM SNMP-FRAMEWORK-MIB 37 ciscoMgmt 38 FROM CISCO-SMI; 39 40 41ciscoRFMIB MODULE-IDENTITY 42 LAST-UPDATED "200509010000Z" 43 ORGANIZATION "Cisco Systems, Inc." 44 CONTACT-INFO 45 "Cisco Systems Customer Service 46 Postal: 170 West Tasman Drive 47 San Jose, CA 95134 48 USA 49 Tel: +1 800 553-NETS 50 51 E-mail: cs-rf-mib@cisco.com" 52 DESCRIPTION 53 "This MIB provides configuration control and status for the 54 Redundancy Framework (RF) subsystem. RF provides a mechanism 55 for logical redundancy of software functionality and is 56 designed to support 1:1 redundancy on processor cards. RF is 57 not intended to solve all redundancy schemes. Nor is RF 58 designed to support redundant hardware, such as power 59 supplies. 60 61 Redundancy is concerned with the duplication of data elements 62 and software functions to provide an alternative in case of 63 failure. It is a key component to meeting 99.999% availability 64 requirements for Class 5 carrier solutions. 65 66 In the scope of this MIB definition, peer software elements 67 are redundant and redundant software elements are peers." 68 REVISION "200509010000Z" 69 DESCRIPTION 70 "Added a new textual convention : RFClientStatus. 71 72 Added the cRFStatusRFClientTable which contains information 73 about all the clients registered with the Redundancy 74 Facility (RF). " 75 REVISION "200404010000Z" 76 DESCRIPTION 77 "Added the new states, systemReset, loadVersionSwitchover 78 and runVersionSwitchover. The unset state has been removed 79 and the init state will represent the absense of the ISSU 80 process. Updated the object cRFStatusIssuState to 81 cRFStatusIssuStateRev1 as the ISSU states have been revised. 82 Added new object, cRFStatusIssuFromVersion and 83 cRFStatusIssuToVersion which represent the from and the to 84 versions of IOS that are involved in the upgrade process. 85 The object ciscoRFIssuStateObjGroup was changed to 86 ciscoRFIssuStateObjGroupRev1 to accomodate these new 87 objects." 88 REVISION "200402040000Z" 89 DESCRIPTION 90 "Added ciscoRFIssuStateNotifGroup and ciscoRFIssuStateObjGroup 91 that represent the notification group and the object group 92 that represents the ISSU state of the system." 93 REVISION "200310020000Z" 94 DESCRIPTION 95 "Changed the description for ciscoRFProgressionNotif" 96 REVISION "200201070000Z" 97 DESCRIPTION 98 "Added the following object in cRFStatus: 99 cRFStatusRFModeCapsTable 100 Added the following object in cRFCfg: 101 cRFCfgRedundancyOperMode 102 Updated description of following object in cRFCfg: 103 cRFCfgRedundancyMode" 104 REVISION "200107200000Z" 105 DESCRIPTION 106 "Added new sub-group 107 cRFHistory 108 Added new table cRFHistorySwitchOverTable 109 which maintains the history of switchovers. 110 Also added objects: 111 cRFStatusFailoverTime 112 cRFStatusPeerStandByEntryTime 113 cRFHistoryTableMaxLength 114 cRFHistoryColdStarts 115 cRFHistoryStandByAvailTime 116 Added textual convention: 117 RFUnitIdentifier." 118 REVISION "200106260000Z" 119 DESCRIPTION 120 "Changed terminology: 121 'split-mode' is now 'maintenance-mode' 122 Added textual convention: 123 RFMode 124 Deprecated object: 125 cRFCfgSplitMode 126 Added objects: 127 cRFCfgMaintenanceMode 128 cRFCfgRedundancyMode 129 cRFCfgRedundancyModeDescr 130 Added enumeration values: 131 noAction(0) to RFAction 132 activeExtraload(15) to RFState 133 activeHandback(16) to RFState 134 Added new transition state to ciscoRFProgressionNotif: 135 activeExtraload 136 Update compliance and conformance statements" 137 REVISION "200104030945Z" 138 DESCRIPTION 139 "The initial revision of this MIB." 140 ::= { ciscoMgmt 176 } 141 142 143-- Glossary 144-- 145 146-- Active Unit - The CPU on which calls are being processed. 147-- 148-- Availability - Availability is measured as a percentage of 149-- uptime. Based on continuous system operation which is typically 150-- 24 hours per day, 7 days per week, 365 days a year. 151-- 152-- Bulk Sync - The process of updating the standby unit to the current 153-- context of the active unit. Once the Bulk sync is complete the 154-- standby unit is considered 'hot' and able to become the active unit. 155-- 156-- Clients - Applications that have registered with the Redundancy 157-- Facility (RF) to receive RF events and notifications. These are 158-- considered redundancy aware applications. 159-- 160-- Cold Redundancy - A redundancy scheme that is not able to instantly 161-- retain established calls and immediately able to handle new 162-- calls. The standby unit in a cold redundancy system is not fully 163-- initialized and is not able to retain established calls. 164-- 165-- Configuration Data - Data that the user configures for the 166-- application and networking requirements. PVCs would fall into this 167-- category. 168-- 169-- Cutover - A canonical term referring to either a switch-over or a 170-- fail-over. 171-- 172-- Data Events - Messages, such as ATM SVC events, sent from active 173-- unit clients to the standby clients. Data Events are used to keep a 174-- standby-hot unit up-to-date with dynamic data changes on the active 175-- unit. 176-- 177-- Drop Activity - The process by which the currently active unit 178-- relinquishes activity to the standby unit. The active unit can only 179-- drop activity to a standby-cold or standby-hot unit. This can be 180-- for one of two reasons: 181-- 182-- - the currently active unit has determined that it is unhealthy 183-- and needs to release activity to the standby, or 184-- 185-- - the user issues a command to drop activity. This is typically 186-- done for maintenance purposes such as upgrading to a new 187-- image in the standby. 188-- 189-- Duplex Mode - The mode of operation when both control processors, 190-- one active and one standby, are present in the system. As opposed 191-- to simplex mode. 192-- 193-- Dynamic Data - Dynamic Data is data that changes in real time. It 194-- is this data that is synced from the active to the standby unit. 195-- The type and frequency of dynamic data syncs is client 196-- specific. ATM SVCs fall into this category. Once the SVC is 197-- established on the active unit, ATM sends SVC Data Events to the 198-- standby unit. 199-- 200-- Gain Activity - The process by which the standby unit becomes the 201-- active unit. 202-- 203-- Hot Redundancy - A redundancy scheme that is able to instantly 204-- retain established calls and immediately able to handle new calls. 205-- 206-- Load Sharing - A high availability scheme whereby a portion of the 207-- system load is statically assigned to each processor/resource. The 208-- assignment of resources may be decided based on ingress interface, 209-- line card, etc. No dynamic decisions are made as to the load 210-- distribution in the system; it is pre-determined. 211-- 212-- Negotiation Clash - The situation when two loosely coupled units 213-- think both have the same negotiation status. In this case, the 214-- primary unit should over ride the secondary unit. 215-- 216-- Peer Unit - The Secondary Unit is the peer to the Primary Unit, 217-- and the Primary Unit is the peer to the Secondary Unit. 218-- 219-- Primary Unit - This is the unit that wins in the unlikely event of 220-- a negotiation clash between two loosely coupled units. For example, 221-- if both units think they are active, the Primary unit is designed 222-- to remain active while the Secondary Unit backs down to standby. If 223-- both units think they are standby, the Primary unit is designed to 224-- gain activity while the Secondary Unit remains the standby. 225-- 226-- Progression - The process of making redundancy state of the standby 227-- unit equivalent to that of the active unit. This includes 228-- transitioning the RF state machine through several states which in 229-- turn drives the RF clients on the active unit to synchronize any 230-- relevant data with their peer on the standby unit. 231-- 232-- Secondary Unit - This is the unit that backs-down in the unlikely 233-- event of a negotiation clash between two loosely coupled units. For 234-- example, if both units think they are active, the Secondary unit is 235-- designed to back down while the Primary unit remains active. If 236-- both units think they are standby, the Secondary unit is designed to 237-- remain standby while the Primary unit gains activity. 238-- 239-- Simplex Mode - The mode of operation when only a single control 240-- processor is present in the system. As opposed to duplex mode. 241-- 242-- Maintenance Mode - A mode in redundancy where the standby unit is 243-- present (duplex) but logically disconnected from the active 244-- unit. Clients do not send data syncs to the standby unit. This mode 245-- is useful for software upgrades and other maintenance procedures. 246-- 247-- Standby Unit - The unit which is backing-up the currently Active 248-- unit. The Standby unit has several substates that are specific to 249-- becoming standby-hot. Once the standby unit progresses to 250-- standby-hot, it is able to instantly become the active unit while 251-- retaining calls. 252-- 253-- Switch of Activity (SWACT) - Either a forced or automatic switch 254-- of active status from the active unit to the standby unit. The 255-- former standby unit is now referred to as the active unit. 256-- 257-- Take Activity - The process by which the standby unit becomes the 258-- active unit. This can be for one of two reasons: 259-- 260-- - the standby unit has determined that the currently active unit 261-- is unhealthy and takes activity, or 262-- 263-- - the user issues a command to switch activity from the currently 264-- active unit. This is typically done for maintenance purposes 265-- such as upgrading the standby unit. 266-- 267-- ISSU - In Service Software Upgrade 268-- IOS Software upgrades between different images will be 269-- possible using the new infrastructure that has been developed 270-- as a part of SSO. It will allow for Stateful Switchovers, 271-- and hence hitless upgrades between different image versions. 272-- 273 274-- 275-- Textual conventions 276 277RFState ::= TEXTUAL-CONVENTION 278 STATUS current 279 DESCRIPTION 280 "The current state of the RF subsystem. 281 282 notKnown 283 - state is unknown 284 disabled 285 - RF is not operational on this unit 286 initialization 287 - establish necessary system services 288 negotiation 289 - peer unit discovery and negotiation 290 standbyCold 291 - client notification on standby unit 292 *standbyColdConfig 293 - standby configuration is updated from active configuration 294 *standbyColdFileSys 295 - standby file system (FS) is updated from the active FS 296 *standbyColdBulk 297 - clients sync data from active to standby 298 standbyHot 299 - incremental client data sync continues. This unit is 300 ready to take over activity. 301 activeFast 302 - call maintenance efforts during a SWACT 303 activeDrain 304 - client clean-up phase 305 activePreconfig 306 - unit is active but has not read its configuration 307 activePostconfig 308 - unit is active and is post-processing its configuration 309 active 310 - unit is active and processing calls 311 activeExtraload 312 - unit is active and processing calls for all feature 313 boards in the system 314 activeHandback 315 - unit is active, processing calls and is in the process 316 of handing some resources to the other unit in the system 317 318 * Sub-state of 'standbyCold'" 319 SYNTAX INTEGER { 320 notKnown(1), 321 disabled(2), 322 initialization(3), 323 negotiation(4), 324 standbyCold(5), 325 standbyColdConfig(6), 326 standbyColdFileSys(7), 327 standbyColdBulk(8), 328 standbyHot(9), 329 activeFast(10), 330 activeDrain(11), 331 activePreconfig(12), 332 activePostconfig(13), 333 active(14), 334 activeExtraload(15), 335 activeHandback(16) 336 } 337 338RFMode ::= TEXTUAL-CONVENTION 339 STATUS current 340 DESCRIPTION 341 "The characterization of the redundancy subsystem. 342 343 nonRedundant 344 - the system is not redundant. 345 staticLoadShareNonRedundant 346 - the system is *not* redundant but is load sharing. 347 The load sharing is *not* based on operational load 348 (i.e. number of calls, etc). 349 dynamicLoadShareNonRedundant 350 - the system is *not* redundant but is load sharing. 351 Load sharing is based on operational load. 352 staticLoadShareRedundant 353 - the system is redundant and is load sharing. The 354 load sharing is *not* based on operational load. 355 dynamicLoadShareRedundant 356 - the system is redundant and is load sharing. Load 357 sharing is based on operational load. 358 coldStandbyRedundant 359 - the system is redundant but the redundant peer unit is 360 not fully initialized and is not able to retain 361 established calls. 362 warmStandbyRedundant 363 - the system is redundant and the redundant peer unit is 364 immediately able to handle new calls. The redundant 365 unit is unable to retain established calls. 366 hotStandbyRedundant 367 - the system is redundant and the redundant peer unit is 368 able to 'instantaneously' retain established calls and 369 immediately able to handle new calls." 370 SYNTAX INTEGER { 371 nonRedundant(1), 372 staticLoadShareNonRedundant(2), 373 dynamicLoadShareNonRedundant(3), 374 staticLoadShareRedundant(4), 375 dynamicLoadShareRedundant(5), 376 coldStandbyRedundant(6), 377 warmStandbyRedundant(7), 378 hotStandbyRedundant(8) 379 } 380 381RFAction ::= TEXTUAL-CONVENTION 382 STATUS current 383 DESCRIPTION 384 "Administrative commands to invoke in the RF subsystem. 385 386 noAction 387 - no action (do nothing) 388 reloadPeer 389 - reset the redundant peer unit 390 reloadShelf 391 - reset the entire shelf 392 switchActivity 393 - safely SWACT to peer unit and go standby 394 forceSwitchActivity 395 - switch activity; ignoring pre-conditions, system 396 warnings and safety checks. 397 398 When the value is set to 'noAction' no operation is performed. 399 When read, the value 'noAction' is always returned." 400 SYNTAX INTEGER { 401 noAction(0), 402 reloadPeer(1), 403 reloadShelf(2), 404 switchActivity(3), 405 forceSwitchActivity(4) 406 } 407 408RFSwactReasonType ::= TEXTUAL-CONVENTION 409 STATUS current 410 DESCRIPTION 411 "Reason codes for the switch of activity from an active 412 redundant unit to its standby peer unit. 413 414 unsupported 415 - the 'reason code' is an unsupported feature 416 none 417 - no SWACT has occurred 418 notKnown 419 - reason is unknown 420 userInitiated 421 - a safe, manual SWACT was initiated by user 422 userForced 423 - a manual SWACT was forced by user; ignoring 424 pre-conditions, warnings and safety checks 425 activeUnitFailed 426 - active unit failure caused an auto SWACT 427 activeUnitRemoved 428 - active unit removal caused an auto SWACT" 429 SYNTAX INTEGER { 430 unsupported(1), 431 none(2), 432 notKnown(3), 433 userInitiated(4), 434 userForced(5), 435 activeUnitFailed(6), 436 activeUnitRemoved(7) 437 } 438 439RFUnitIdentifier ::= TEXTUAL-CONVENTION 440 STATUS current 441 DESCRIPTION "A unique identifier for Active/Standby unit." 442 SYNTAX Integer32 (0..2147483647 ) 443 444RFIssuState ::= TEXTUAL-CONVENTION 445 STATUS deprecated 446 DESCRIPTION 447 "ISSU state represents the current system state. 448 449 unset 450 - unset state; if the system is booted from tftp or from 451 ROMMON such that the image is not the first in BOOT 452 init 453 - init state; the first ISSU state that the system will 454 move to after the unset state, when the ISSU process 455 has just been kicked off. The first CLI that is executed 456 to make this happen is the loadversion CLI. 457 loadVersion 458 - Once the loadversion CLI has been executed, the state 459 of the system is changed to reflect this, and this state 460 is called the loadVersion state. The boot variable on 461 the Standby is updated to point to the new image that the 462 Standby needs to load and then it is reset. 463 runVersion 464 - runVersion state; When the system is in the loadversion 465 state, the Active is running the old image and the 466 Standby is running the new image. When the runversion 467 CLI is executed, a switchover occurs, and the Standby 468 running the new image takes over as the Active. The 469 state of the system at this stage is updated to 470 runversion. 471 commitVersion 472 - in the runversion state, the Active is running the 473 new image, and the Standby is running the old image. 474 When the user is satisfied with the functioning of 475 the system, they execute the commitversion CLI, which 476 will prepend the boot variable on the Standby with 477 the new image, and then the Standby is reset. After 478 this, the Standby comes up with the new image, and 479 the state of the system is updated to reflect the 480 commitVersion state." 481 SYNTAX INTEGER { 482 unset(0), 483 init(1), 484 loadVersion(2), 485 runVersion(3), 486 commitVersion(4) 487 } 488 489RFIssuStateRev1 ::= TEXTUAL-CONVENTION 490 STATUS current 491 DESCRIPTION 492 "ISSU state represents the current system state. 493 494 init 495 - This state represents the initial state of the system. 496 The ISSU process is not running at this stage. The only 497 CLI for ISSU process that can be executed in this state 498 is the loadversion CLI. 499 systemReset 500 - If a system reset occurs, or the abortversion CLI is 501 executed, the state of the system is pushed to this state. 502 loadVersion 503 - When the Standby signs in after the loadversion CLI 504 is executed, the state of the system is changed to 505 loadVersion. 506 loadVersionSwitchover 507 - If a switchover occurs in the loadVersion state, by 508 the user, or because the Active crashes, the new 509 state of the system will be loadVersionSwitchover. 510 It is analogous to the runVersion state, except that 511 the runversion CLI was not executed. 512 runVersion 513 - When the Standby signs in after executing the 514 runversion CLI, the state of the system is changed 515 to runVersion. 516 runVersionSwitchover 517 - if a switchover occurs while the system is in the 518 runVersion state, the new state will be called 519 runVersionSwitchover. It is analogous to the 520 loadVersion state. 521 commitVersion 522 - When the Standby signs in after the commitversion CLI 523 is executed, the state of the system is changed to 524 commitVersion." 525 SYNTAX INTEGER { 526 init(0), 527 systemReset(1), 528 loadVersion(3), 529 loadVersionSwitchover(4), 530 runVersion(6), 531 runVersionSwitchover(7), 532 commitVersion(9) 533 } 534 535RFClientStatus ::= TEXTUAL-CONVENTION 536 STATUS current 537 DESCRIPTION 538 "The status of a RF client before, during and after 539 switchover. 540 541 noStatus 542 - No status information is available for this client. 543 clientNotRedundant 544 - Client is active. But there is no redundancy to this 545 client. This could be because there is no standby or 546 the client cannot claim that the standby client can 547 take over without losing data or traffic during a 548 switchover. 549 clientRedundancyInProgress 550 - The client is trying to sync all data to standby and 551 achieve redundancy. 552 clientRedundant 553 - The client is redundant and ready for switchover. The 554 client can safely claim that there is no data or traffic 555 loss if there is a switchover." 556 SYNTAX INTEGER { 557 noStatus(1), 558 clientNotRedundant(2), 559 clientRedundancyInProgress(3), 560 clientRedundant(4) 561 } 562-- OBJECT IDENTIFIER assignments for various groups 563ciscoRFMIBObjects OBJECT IDENTIFIER 564 ::= { ciscoRFMIB 1 } 565 566-- sub-groups 567cRFStatus OBJECT IDENTIFIER 568 ::= { ciscoRFMIBObjects 1 } 569 570cRFCfg OBJECT IDENTIFIER 571 ::= { ciscoRFMIBObjects 2 } 572 573cRFHistory OBJECT IDENTIFIER 574 ::= { ciscoRFMIBObjects 3 } 575 576cRFClient OBJECT IDENTIFIER 577 ::= { ciscoRFMIBObjects 4 } 578 579 580-- Status sub-group definitions 581cRFStatusUnitId OBJECT-TYPE 582 SYNTAX RFUnitIdentifier 583 MAX-ACCESS read-only 584 STATUS current 585 DESCRIPTION 586 "A unique identifier for this redundant unit. This identifier 587 is implementation-specific but the method for selecting the id 588 must remain consistent throughout the redundant system. 589 590 Some example identifiers include: slot id, physical or logical 591 entity id, or a unique id assigned internally by the RF 592 subsystem." 593 ::= { cRFStatus 1 } 594 595cRFStatusUnitState OBJECT-TYPE 596 SYNTAX RFState 597 MAX-ACCESS read-only 598 STATUS current 599 DESCRIPTION "The current state of RF on this unit." 600 ::= { cRFStatus 2 } 601 602cRFStatusPeerUnitId OBJECT-TYPE 603 SYNTAX RFUnitIdentifier 604 MAX-ACCESS read-only 605 STATUS current 606 DESCRIPTION 607 "A unique identifier for the redundant peer unit. This 608 identifier is implementation-specific but the method for 609 selecting the id must remain consistent throughout the 610 redundant system. 611 612 Some example identifiers include: slot id, physical or logical 613 entity id, or a unique id assigned internally by the RF 614 subsystem." 615 ::= { cRFStatus 3 } 616 617cRFStatusPeerUnitState OBJECT-TYPE 618 SYNTAX RFState 619 MAX-ACCESS read-only 620 STATUS current 621 DESCRIPTION "The current state of RF on the peer unit." 622 ::= { cRFStatus 4 } 623 624cRFStatusPrimaryMode OBJECT-TYPE 625 SYNTAX TruthValue 626 MAX-ACCESS read-only 627 STATUS current 628 DESCRIPTION 629 "Indicates whether this is the primary redundant unit or 630 not. If this unit is the primary unit, this object is true. If 631 this unit is the secondary unit, this object is false. 632 633 Note that the terms 'primary/secondary' are not synonymous 634 with the terms 'active/standby'. At any given time, the 635 primary unit may be the active unit, or the primary unit may 636 be the standby unit. Likewise, the secondary unit, at any 637 given time, may be the active unit, or the secondary unit may 638 be the standby unit. 639 640 The primary unit is given a higher priority or precedence over 641 the secondary unit. In a race condition (usually at 642 initialization time) or any situation where the redundant 643 units are unable to successfully negotiate activity between 644 themselves, the primary unit will always become the active 645 unit and the secondary unit will fall back to standby. Only 646 one redundant unit can be the primary unit at any given time. 647 648 The algorithm for determining the primary unit is system 649 dependent, such as 'the redundant unit with the lower numeric 650 unit id is always the primary unit.'" 651 ::= { cRFStatus 5 } 652 653cRFStatusDuplexMode OBJECT-TYPE 654 SYNTAX TruthValue 655 MAX-ACCESS read-only 656 STATUS current 657 DESCRIPTION 658 "Indicates whether the redundant peer unit has been detected 659 or not. If the redundant peer unit is detected, this object is 660 true. If the redundant peer unit is not detected, this object 661 is false." 662 ::= { cRFStatus 6 } 663 664cRFStatusManualSwactInhibit OBJECT-TYPE 665 SYNTAX TruthValue 666 MAX-ACCESS read-only 667 STATUS current 668 DESCRIPTION 669 "Indicates whether a manual switch of activity is 670 permitted. If a manual switch of activity is allowed, this 671 object is false. If a manual switch of activity is not 672 allowed, this object is true. Note that the value of this 673 object is the inverse of the status of manual SWACTs. 674 675 This object does not indicate whether a switch of activity is 676 or has occurred. This object only indicates if the 677 user-controllable capability is enabled or not. 678 679 A switch of activity is the event in which the standby 680 redundant unit becomes active and the previously active unit 681 becomes standby." 682 ::= { cRFStatus 7 } 683 684cRFStatusLastSwactReasonCode OBJECT-TYPE 685 SYNTAX RFSwactReasonType 686 MAX-ACCESS read-only 687 STATUS current 688 DESCRIPTION "The reason for the last switch of activity." 689 ::= { cRFStatus 8 } 690 691cRFStatusFailoverTime OBJECT-TYPE 692 SYNTAX TimeStamp 693 MAX-ACCESS read-only 694 STATUS current 695 DESCRIPTION 696 "The value of sysUpTime when the primary redundant unit took over 697 as active. The value of this object will be 0 till the first 698 switchover." 699 ::= { cRFStatus 9 } 700 701cRFStatusPeerStandByEntryTime OBJECT-TYPE 702 SYNTAX TimeStamp 703 MAX-ACCESS read-only 704 STATUS current 705 DESCRIPTION 706 "The value of sysUpTime when the peer redundant unit entered the 707 standbyHot state. The value will be 0 on system initialization." 708 ::= { cRFStatus 10 } 709-- Redundancy mode capability table 710 711cRFStatusRFModeCapsTable OBJECT-TYPE 712 SYNTAX SEQUENCE OF CRFStatusRFModeCapsEntry 713 MAX-ACCESS not-accessible 714 STATUS current 715 DESCRIPTION 716 "This table containing a list of redundancy modes that can be 717 supported on the device." 718 ::= { cRFStatus 11 } 719 720cRFStatusRFModeCapsEntry OBJECT-TYPE 721 SYNTAX CRFStatusRFModeCapsEntry 722 MAX-ACCESS not-accessible 723 STATUS current 724 DESCRIPTION 725 "An entry containing the device implementation specific 726 terminology associated with the redundancy mode that can be 727 supported on the device." 728 INDEX { cRFStatusRFModeCapsMode } 729 ::= { cRFStatusRFModeCapsTable 1 } 730 731CRFStatusRFModeCapsEntry ::= SEQUENCE { 732 cRFStatusRFModeCapsMode RFMode, 733 cRFStatusRFModeCapsModeDescr SnmpAdminString 734} 735 736cRFStatusRFModeCapsMode OBJECT-TYPE 737 SYNTAX RFMode 738 MAX-ACCESS not-accessible 739 STATUS current 740 DESCRIPTION 741 "The redundancy mode that can be supported on the device." 742 ::= { cRFStatusRFModeCapsEntry 1 } 743 744cRFStatusRFModeCapsModeDescr OBJECT-TYPE 745 SYNTAX SnmpAdminString 746 MAX-ACCESS read-only 747 STATUS current 748 DESCRIPTION 749 "The description of the device implementation specific 750 terminology associated with its supported redundancy mode." 751 ::= { cRFStatusRFModeCapsEntry 2 } 752 753 754 755cRFStatusIssuState OBJECT-TYPE 756 SYNTAX RFIssuState 757 MAX-ACCESS read-only 758 STATUS deprecated 759 DESCRIPTION "The current ISSU state of the system." 760 ::= { cRFStatus 12 } 761 762cRFStatusIssuStateRev1 OBJECT-TYPE 763 SYNTAX RFIssuStateRev1 764 MAX-ACCESS read-only 765 STATUS current 766 DESCRIPTION "The current ISSU state of the system." 767 ::= { cRFStatus 13 } 768 769cRFStatusIssuFromVersion OBJECT-TYPE 770 SYNTAX SnmpAdminString 771 MAX-ACCESS read-only 772 STATUS current 773 DESCRIPTION "The IOS version from with the user is upgrading" 774 ::= { cRFStatus 14 } 775 776cRFStatusIssuToVersion OBJECT-TYPE 777 SYNTAX SnmpAdminString 778 MAX-ACCESS read-only 779 STATUS current 780 DESCRIPTION "The IOS version to with the user is upgrading" 781 ::= { cRFStatus 15 } 782-- Redundancy Facility (RF) Client Table 783 784cRFStatusRFClientTable OBJECT-TYPE 785 SYNTAX SEQUENCE OF CRFStatusRFClientEntry 786 MAX-ACCESS not-accessible 787 STATUS current 788 DESCRIPTION 789 "This table contains a list of RF clients that are 790 registered on the device. 791 792 RF clients are applications that have registered with 793 the Redundancy Facility (RF) to receive RF events and 794 notifications. The purpose of RF clients is to synchronize 795 any relevant data with the standby unit." 796 ::= { cRFClient 1 } 797 798cRFStatusRFClientEntry OBJECT-TYPE 799 SYNTAX CRFStatusRFClientEntry 800 MAX-ACCESS not-accessible 801 STATUS current 802 DESCRIPTION 803 "An entry containing information on various clients 804 registered with the Redundancy Facility (RF). Entries in 805 this table are always created by the system. 806 807 An entry is created in this table when a redundancy aware 808 application registers with the Redundancy Facility. The entry 809 is destroyed when that application deregisters from the 810 Redundancy Facility." 811 INDEX { cRFStatusRFClientID } 812 ::= { cRFStatusRFClientTable 1 } 813 814CRFStatusRFClientEntry ::= SEQUENCE { 815 cRFStatusRFClientID Unsigned32, 816 cRFStatusRFClientDescr SnmpAdminString, 817 cRFStatusRFClientSeq Unsigned32, 818 cRFStatusRFClientRedTime Unsigned32, 819 cRFStatusRFClientStatus RFClientStatus 820} 821 822cRFStatusRFClientID OBJECT-TYPE 823 SYNTAX Unsigned32 (1..4294967295 ) 824 MAX-ACCESS not-accessible 825 STATUS current 826 DESCRIPTION 827 "A unique identifier for the client which registered with the 828 Redundancy Facility." 829 ::= { cRFStatusRFClientEntry 1 } 830 831cRFStatusRFClientDescr OBJECT-TYPE 832 SYNTAX SnmpAdminString 833 MAX-ACCESS read-only 834 STATUS current 835 DESCRIPTION 836 "The description of the client which has registered with the 837 Redundancy Facility." 838 ::= { cRFStatusRFClientEntry 2 } 839 840cRFStatusRFClientSeq OBJECT-TYPE 841 SYNTAX Unsigned32 842 MAX-ACCESS read-only 843 STATUS current 844 DESCRIPTION 845 "The sequence number of the client. The system assigns the 846 sequence numbers based on the order of registration of 847 the Redundancy Facility clients. 848 This is used for deciding order of RF events sent to clients." 849 ::= { cRFStatusRFClientEntry 3 } 850 851cRFStatusRFClientRedTime OBJECT-TYPE 852 SYNTAX Unsigned32 853 UNITS "milliseconds" 854 MAX-ACCESS read-only 855 STATUS current 856 DESCRIPTION 857 "Time taken for this client to become Redundant. This value 858 is meaningful when the value of cRFStatusRFClientStatus is 859 not 'noStatus'." 860 ::= { cRFStatusRFClientEntry 4 } 861 862cRFStatusRFClientStatus OBJECT-TYPE 863 SYNTAX RFClientStatus 864 MAX-ACCESS read-only 865 STATUS current 866 DESCRIPTION 867 "This object provides the status of the Redundancy Facility 868 client." 869 ::= { cRFStatusRFClientEntry 5 } 870 871 872 873-- Configuration sub-group definitions 874cRFCfgSplitMode OBJECT-TYPE 875 SYNTAX TruthValue 876 MAX-ACCESS read-write 877 STATUS deprecated 878 DESCRIPTION 879 "Indicates whether redundant units may communicate 880 synchronization messages with each other. If communication is 881 not permitted, this object is set to true. If communication is 882 permitted, this object is set to false. 883 884 In split mode (true), the active unit will not communicate 885 with the standby unit. The standby unit progression will not 886 occur. When split mode is disabled (false), the standby unit 887 is reset to recover. 888 889 Split mode (true) is useful for maintenance operations. 890 " 891 ::= { cRFCfg 1 } 892 893cRFCfgKeepaliveThresh OBJECT-TYPE 894 SYNTAX Unsigned32 895 MAX-ACCESS read-write 896 STATUS current 897 DESCRIPTION 898 "On platforms that support keep-alives, the keep-alive 899 threshold value designates the number of lost keep-alives 900 tolerated before a failure condition is declared. If this 901 occurs, a SWACT notification is sent. 902 903 On platforms that do not support keep-alives, this object has 904 no purpose or effect." 905 ::= { cRFCfg 2 } 906 907cRFCfgKeepaliveThreshMin OBJECT-TYPE 908 SYNTAX Unsigned32 909 MAX-ACCESS read-only 910 STATUS current 911 DESCRIPTION 912 "The minimum acceptable value for the cRFCfgKeepaliveThresh 913 object." 914 ::= { cRFCfg 3 } 915 916cRFCfgKeepaliveThreshMax OBJECT-TYPE 917 SYNTAX Unsigned32 918 MAX-ACCESS read-only 919 STATUS current 920 DESCRIPTION 921 "The maximum acceptable value for the cRFCfgKeepaliveThresh 922 object." 923 ::= { cRFCfg 4 } 924 925cRFCfgKeepaliveTimer OBJECT-TYPE 926 SYNTAX Unsigned32 927 UNITS "milliseconds" 928 MAX-ACCESS read-write 929 STATUS current 930 DESCRIPTION 931 "On platforms that support keep-alives, the keep-alive timer 932 value is used to guard against lost keep-alives. The RF 933 subsystem expects to receive a keep-alive within this period. 934 If a keep-alive is not received within this time period, a 935 SWACT notification is sent. 936 937 On platforms that do not support keep-alives, this object has 938 no purpose or effect." 939 ::= { cRFCfg 5 } 940 941cRFCfgKeepaliveTimerMin OBJECT-TYPE 942 SYNTAX Unsigned32 943 UNITS "milliseconds" 944 MAX-ACCESS read-only 945 STATUS current 946 DESCRIPTION 947 "The minimum acceptable value for the cRFCfgKeepaliveTimer 948 object." 949 ::= { cRFCfg 6 } 950 951cRFCfgKeepaliveTimerMax OBJECT-TYPE 952 SYNTAX Unsigned32 953 UNITS "milliseconds" 954 MAX-ACCESS read-only 955 STATUS current 956 DESCRIPTION 957 "The maximum acceptable value for the cRFCfgKeepaliveTimer 958 object." 959 ::= { cRFCfg 7 } 960 961cRFCfgNotifTimer OBJECT-TYPE 962 SYNTAX Unsigned32 963 UNITS "milliseconds" 964 MAX-ACCESS read-write 965 STATUS current 966 DESCRIPTION 967 "Note that the term 'notification' here refers to an RF 968 notification and not an SNMP notification. 969 970 As the standby unit progresses to the 'standbyHot' state, 971 asynchronous messages are sent from the active unit to the 972 standby unit which must then be acknowledged by the standby 973 unit. If the active unit receives the acknowledgement during 974 the time period specified by this object, progression proceeds 975 as normal. If the timer expires and an acknowledgement was not 976 received by the active unit, a switch of activity occurs." 977 ::= { cRFCfg 8 } 978 979cRFCfgNotifTimerMin OBJECT-TYPE 980 SYNTAX Unsigned32 981 UNITS "milliseconds" 982 MAX-ACCESS read-only 983 STATUS current 984 DESCRIPTION 985 "The minimum acceptable value for the cRFCfgNotifTimer 986 object." 987 ::= { cRFCfg 9 } 988 989cRFCfgNotifTimerMax OBJECT-TYPE 990 SYNTAX Unsigned32 991 UNITS "milliseconds" 992 MAX-ACCESS read-only 993 STATUS current 994 DESCRIPTION 995 "The maximum acceptable value for the cRFCfgNotifTimer 996 object." 997 ::= { cRFCfg 10 } 998 999cRFCfgAdminAction OBJECT-TYPE 1000 SYNTAX RFAction 1001 MAX-ACCESS read-write 1002 STATUS current 1003 DESCRIPTION 1004 "This variable is set to invoke RF subsystem action commands. 1005 The commands are useful for maintenance and software upgrade 1006 activities." 1007 ::= { cRFCfg 11 } 1008 1009cRFCfgNotifsEnabled OBJECT-TYPE 1010 SYNTAX TruthValue 1011 MAX-ACCESS read-write 1012 STATUS current 1013 DESCRIPTION 1014 "Allows enabling/disabling of RF subsystem notifications." 1015 DEFVAL { false } 1016 ::= { cRFCfg 12 } 1017 1018cRFCfgMaintenanceMode OBJECT-TYPE 1019 SYNTAX TruthValue 1020 MAX-ACCESS read-write 1021 STATUS current 1022 DESCRIPTION 1023 "Indicates whether redundant units may communicate 1024 synchronization messages with each other. If communication is 1025 not permitted, this object is set to 'true'. If communication 1026 is permitted, this object is set to 'false'. 1027 1028 If the value of this object is 'true', the redundant system is 1029 considered to be in a maintenance mode of operation. If the 1030 value of this object is 'false', the redundant system is 1031 considered to be in a normal (non-maintenance) mode of 1032 operation. 1033 1034 In maintenance mode (true), the active unit will not 1035 communicate with the standby unit. The standby unit 1036 progression will not occur. When maintenance mode is disabled 1037 (false), the standby unit is reset to recover. 1038 1039 Maintenance mode (true) is useful for maintenance-type 1040 operations." 1041 ::= { cRFCfg 13 } 1042 1043cRFCfgRedundancyMode OBJECT-TYPE 1044 SYNTAX RFMode 1045 MAX-ACCESS read-write 1046 STATUS current 1047 DESCRIPTION 1048 "Indicates the redundancy mode configured on the device." 1049 ::= { cRFCfg 14 } 1050 1051cRFCfgRedundancyModeDescr OBJECT-TYPE 1052 SYNTAX SnmpAdminString 1053 MAX-ACCESS read-only 1054 STATUS current 1055 DESCRIPTION 1056 "Further clarifies or describes the redundancy mode indicated 1057 by cRFCfgRedundancyMode. Implementation-specific terminology 1058 associated with the current redundancy mode may be presented 1059 here." 1060 ::= { cRFCfg 15 } 1061 1062cRFCfgRedundancyOperMode OBJECT-TYPE 1063 SYNTAX RFMode 1064 MAX-ACCESS read-only 1065 STATUS current 1066 DESCRIPTION 1067 "Indicate the operational redundancy mode of the device." 1068 ::= { cRFCfg 16 } 1069 1070-- History sub-group definitions 1071cRFHistoryTableMaxLength OBJECT-TYPE 1072 SYNTAX Unsigned32 (0..50 ) 1073 MAX-ACCESS read-write 1074 STATUS current 1075 DESCRIPTION 1076 "Maximum number of entries permissible in the history 1077 table. A value of 0 will result in no history being 1078 maintained." 1079 DEFVAL { 10 } 1080 ::= { cRFHistory 1 } 1081 1082cRFHistorySwitchOverTable OBJECT-TYPE 1083 SYNTAX SEQUENCE OF CRFHistorySwitchOverEntry 1084 MAX-ACCESS not-accessible 1085 STATUS current 1086 DESCRIPTION 1087 "A table that tracks the history of all switchovers that 1088 have occurred since system initialization. The maximum 1089 number of entries permissible in this table is defined by 1090 cRFHistoryTableMaxLength. When the number of entries in 1091 the table reaches the maximum limit, the next entry 1092 would replace the oldest existing entry in the table." 1093 ::= { cRFHistory 2 } 1094 1095cRFHistorySwitchOverEntry OBJECT-TYPE 1096 SYNTAX CRFHistorySwitchOverEntry 1097 MAX-ACCESS not-accessible 1098 STATUS current 1099 DESCRIPTION 1100 "The entries in this table contain the switchover 1101 information. Each entry in the table is indexed by 1102 cRFHistorySwitchOverIndex. The index wraps around to 1 1103 after reaching the maximum value." 1104 INDEX { cRFHistorySwitchOverIndex } 1105 ::= { cRFHistorySwitchOverTable 1 } 1106 1107CRFHistorySwitchOverEntry ::= SEQUENCE { 1108 cRFHistorySwitchOverIndex Unsigned32, 1109 cRFHistoryPrevActiveUnitId RFUnitIdentifier, 1110 cRFHistoryCurrActiveUnitId RFUnitIdentifier, 1111 cRFHistorySwitchOverReason RFSwactReasonType, 1112 cRFHistorySwactTime DateAndTime 1113} 1114 1115cRFHistorySwitchOverIndex OBJECT-TYPE 1116 SYNTAX Unsigned32 (1..4294967295 ) 1117 MAX-ACCESS not-accessible 1118 STATUS current 1119 DESCRIPTION 1120 "A monotonically increasing integer for the purpose of 1121 indexing history table. After reaching maximum value, 1122 it wraps around to 1." 1123 ::= { cRFHistorySwitchOverEntry 1 } 1124 1125cRFHistoryPrevActiveUnitId OBJECT-TYPE 1126 SYNTAX RFUnitIdentifier 1127 MAX-ACCESS read-only 1128 STATUS current 1129 DESCRIPTION 1130 "Indicates the primary redundant unit that went down." 1131 ::= { cRFHistorySwitchOverEntry 2 } 1132 1133cRFHistoryCurrActiveUnitId OBJECT-TYPE 1134 SYNTAX RFUnitIdentifier 1135 MAX-ACCESS read-only 1136 STATUS current 1137 DESCRIPTION 1138 "Indicates the secondary redundant unit that took 1139 over as active." 1140 ::= { cRFHistorySwitchOverEntry 3 } 1141 1142cRFHistorySwitchOverReason OBJECT-TYPE 1143 SYNTAX RFSwactReasonType 1144 MAX-ACCESS read-only 1145 STATUS current 1146 DESCRIPTION "Indicates the reason for the switchover." 1147 ::= { cRFHistorySwitchOverEntry 4 } 1148 1149cRFHistorySwactTime OBJECT-TYPE 1150 SYNTAX DateAndTime 1151 MAX-ACCESS read-only 1152 STATUS current 1153 DESCRIPTION 1154 "Indicates the Date & Time when switchover occurred." 1155 ::= { cRFHistorySwitchOverEntry 5 } 1156 1157 1158 1159cRFHistoryColdStarts OBJECT-TYPE 1160 SYNTAX Counter32 1161 MAX-ACCESS read-only 1162 STATUS current 1163 DESCRIPTION 1164 "Indicates the number of system cold starts. This includes 1165 the number of system cold starts due to switchover failure 1166 and the number of manual restarts." 1167 ::= { cRFHistory 3 } 1168 1169cRFHistoryStandByAvailTime OBJECT-TYPE 1170 SYNTAX TimeInterval 1171 MAX-ACCESS read-only 1172 STATUS current 1173 DESCRIPTION 1174 "Indicates the cumulative time that a standby redundant 1175 unit has been available since last system initialization." 1176 ::= { cRFHistory 4 } 1177-- MIB Notification definitions 1178ciscoRFMIBNotificationsPrefix OBJECT IDENTIFIER 1179 ::= { ciscoRFMIB 2 } 1180 1181ciscoRFMIBNotifications OBJECT IDENTIFIER 1182 ::= { ciscoRFMIBNotificationsPrefix 0 } 1183 1184 1185 1186ciscoRFSwactNotif NOTIFICATION-TYPE 1187 OBJECTS { 1188 cRFStatusUnitId, 1189 sysUpTime, 1190 cRFStatusLastSwactReasonCode 1191 } 1192 STATUS current 1193 DESCRIPTION 1194 "A SWACT notification is sent by the newly active redundant 1195 unit whenever a switch of activity occurs. In the case where a 1196 SWACT event may be indistinguishable from a reset event, a 1197 network management station should use this notification to 1198 differentiate the activity. 1199 1200 sysUpTime is the same sysUpTime defined in the RFC-1213 MIB." 1201 ::= { ciscoRFMIBNotifications 1 } 1202 1203 1204ciscoRFProgressionNotif NOTIFICATION-TYPE 1205 OBJECTS { 1206 cRFStatusUnitId, 1207 cRFStatusUnitState, 1208 cRFStatusPeerUnitId, 1209 cRFStatusPeerUnitState 1210 } 1211 STATUS current 1212 DESCRIPTION 1213 "A progression notification is sent by the active redundant 1214 unit whenever its RF state changes or the RF state of the peer 1215 unit changes. 1216 1217 To avoid a flurry of notifications for all state transitions, 1218 notifications will only be sent for transitions to the 1219 following RF states: 1220 disabled (for the peer state) 1221 standbyCold 1222 standbyHot 1223 active 1224 activeExtraload" 1225 ::= { ciscoRFMIBNotifications 2 } 1226 1227 1228ciscoRFIssuStateNotif NOTIFICATION-TYPE 1229 OBJECTS { 1230 cRFStatusUnitId, 1231 cRFStatusUnitState, 1232 cRFStatusIssuState 1233 } 1234 STATUS deprecated 1235 DESCRIPTION 1236 "An ISSU notification to indicate the new state of 1237 the system." 1238 ::= { ciscoRFMIBNotifications 3 } 1239 1240 1241ciscoRFIssuStateNotifRev1 NOTIFICATION-TYPE 1242 OBJECTS { 1243 cRFStatusIssuStateRev1, 1244 cRFStatusIssuFromVersion, 1245 cRFStatusIssuToVersion, 1246 cRFStatusLastSwactReasonCode 1247 } 1248 STATUS current 1249 DESCRIPTION 1250 "An ISSU notification to indicate the new state of 1251 the system." 1252 ::= { ciscoRFMIBNotifications 4 } 1253-- Conformance 1254ciscoRFMIBConformance OBJECT IDENTIFIER 1255 ::= { ciscoRFMIB 3 } 1256 1257ciscoRFMIBCompliances OBJECT IDENTIFIER 1258 ::= { ciscoRFMIBConformance 1 } 1259 1260ciscoRFMIBGroups OBJECT IDENTIFIER 1261 ::= { ciscoRFMIBConformance 2 } 1262 1263 1264-- compliance statements 1265ciscoRFMIBCompliance MODULE-COMPLIANCE 1266 STATUS deprecated 1267 DESCRIPTION 1268 "The compliance statement for entities which implement the 1269 Cisco RF MIB." 1270 MODULE -- this module 1271 MANDATORY-GROUPS { 1272 ciscoRFStatusGroup, 1273 ciscoRFConfigGroup, 1274 ciscoRFNotifGroup 1275 } 1276 ::= { ciscoRFMIBCompliances 1 } 1277 1278ciscoRFMIBComplianceRev1 MODULE-COMPLIANCE 1279 STATUS deprecated 1280 DESCRIPTION 1281 "The compliance statement for entities which implement the 1282 Cisco RF MIB" 1283 MODULE -- this module 1284 MANDATORY-GROUPS { 1285 ciscoRFStatusGroup, 1286 ciscoRFConfigGroupRev1, 1287 ciscoRFNotifGroup 1288 } 1289 ::= { ciscoRFMIBCompliances 2 } 1290 1291ciscoRFMIBComplianceRev2 MODULE-COMPLIANCE 1292 STATUS deprecated 1293 DESCRIPTION 1294 "The compliance statement for entities which implement the 1295 Cisco RF MIB." 1296 MODULE -- this module 1297 MANDATORY-GROUPS { 1298 ciscoRFStatusGroupRev1, 1299 ciscoRFConfigGroupRev1, 1300 ciscoRFNotifGroup, 1301 ciscoRFHistoryGroup 1302 } 1303 ::= { ciscoRFMIBCompliances 3 } 1304 1305ciscoRFMIBComplianceRev3 MODULE-COMPLIANCE 1306 STATUS deprecated 1307 DESCRIPTION 1308 "The compliance statement for entities which implement the 1309 Cisco RF MIB." 1310 MODULE -- this module 1311 MANDATORY-GROUPS { 1312 ciscoRFStatusGroupRev1, 1313 ciscoRFConfigGroupRev1, 1314 ciscoRFNotifGroup, 1315 ciscoRFHistoryGroup, 1316 ciscoRFConfigRFOperModeGroup, 1317 ciscoRFStatusRFModeCapsGroup, 1318 ciscoRFIssuStateNotifGroup, 1319 ciscoRFIssuStateObjGroup 1320 } 1321 ::= { ciscoRFMIBCompliances 4 } 1322 1323ciscoRFMIBComplianceRev4 MODULE-COMPLIANCE 1324 STATUS deprecated 1325 DESCRIPTION 1326 "The compliance statement for entities which implement the 1327 Cisco RF MIB." 1328 MODULE -- this module 1329 MANDATORY-GROUPS { 1330 ciscoRFStatusGroupRev1, 1331 ciscoRFConfigGroupRev1, 1332 ciscoRFNotifGroup, 1333 ciscoRFHistoryGroup, 1334 ciscoRFConfigRFOperModeGroup, 1335 ciscoRFStatusRFModeCapsGroup, 1336 ciscoRFIssuStateNotifGroupRev1, 1337 ciscoRFIssuStateObjGroupRev1 1338 } 1339 ::= { ciscoRFMIBCompliances 5 } 1340 1341ciscoRFMIBComplianceRev5 MODULE-COMPLIANCE 1342 STATUS current 1343 DESCRIPTION 1344 "The compliance statement for entities which implement the 1345 Cisco RF MIB." 1346 MODULE -- this module 1347 MANDATORY-GROUPS { 1348 ciscoRFStatusGroupRev1, 1349 ciscoRFConfigGroupRev1, 1350 ciscoRFNotifGroup, 1351 ciscoRFHistoryGroup, 1352 ciscoRFConfigRFOperModeGroup, 1353 ciscoRFStatusRFModeCapsGroup, 1354 ciscoRFIssuStateNotifGroupRev1, 1355 ciscoRFIssuStateObjGroupRev1, 1356 ciscoRFStatusClientGroup 1357 } 1358 ::= { ciscoRFMIBCompliances 6 } 1359 1360-- Units of conformance 1361ciscoRFStatusGroup OBJECT-GROUP 1362 OBJECTS { 1363 cRFStatusUnitId, 1364 cRFStatusUnitState, 1365 cRFStatusPeerUnitId, 1366 cRFStatusPeerUnitState, 1367 cRFStatusPrimaryMode, 1368 cRFStatusDuplexMode, 1369 cRFStatusManualSwactInhibit, 1370 cRFStatusLastSwactReasonCode 1371 } 1372 STATUS deprecated 1373 DESCRIPTION "The collection of global RF status objects." 1374 ::= { ciscoRFMIBGroups 1 } 1375 1376ciscoRFConfigGroup OBJECT-GROUP 1377 OBJECTS { 1378 cRFCfgSplitMode, 1379 cRFCfgKeepaliveThresh, 1380 cRFCfgKeepaliveThreshMin, 1381 cRFCfgKeepaliveThreshMax, 1382 cRFCfgKeepaliveTimer, 1383 cRFCfgKeepaliveTimerMin, 1384 cRFCfgKeepaliveTimerMax, 1385 cRFCfgNotifTimer, 1386 cRFCfgNotifTimerMin, 1387 cRFCfgNotifTimerMax, 1388 cRFCfgAdminAction, 1389 cRFCfgNotifsEnabled, 1390 cRFCfgRedundancyMode, 1391 cRFCfgRedundancyModeDescr 1392 } 1393 STATUS deprecated 1394 DESCRIPTION "The collection of RF configuration objects." 1395 ::= { ciscoRFMIBGroups 2 } 1396 1397ciscoRFNotifGroup NOTIFICATION-GROUP 1398 NOTIFICATIONS { 1399 ciscoRFSwactNotif, 1400 ciscoRFProgressionNotif 1401 } 1402 STATUS current 1403 DESCRIPTION 1404 "The collection of notifications used to indicate RF state 1405 information." 1406 ::= { ciscoRFMIBGroups 3 } 1407 1408ciscoRFConfigGroupRev1 OBJECT-GROUP 1409 OBJECTS { 1410 cRFCfgKeepaliveThresh, 1411 cRFCfgKeepaliveThreshMin, 1412 cRFCfgKeepaliveThreshMax, 1413 cRFCfgKeepaliveTimer, 1414 cRFCfgKeepaliveTimerMin, 1415 cRFCfgKeepaliveTimerMax, 1416 cRFCfgNotifTimer, 1417 cRFCfgNotifTimerMin, 1418 cRFCfgNotifTimerMax, 1419 cRFCfgAdminAction, 1420 cRFCfgNotifsEnabled, 1421 cRFCfgMaintenanceMode, 1422 cRFCfgRedundancyMode, 1423 cRFCfgRedundancyModeDescr 1424 } 1425 STATUS current 1426 DESCRIPTION "The collection of RF configuration objects." 1427 ::= { ciscoRFMIBGroups 4 } 1428 1429ciscoRFStatusGroupRev1 OBJECT-GROUP 1430 OBJECTS { 1431 cRFStatusUnitId, 1432 cRFStatusUnitState, 1433 cRFStatusPeerUnitId, 1434 cRFStatusPeerUnitState, 1435 cRFStatusPrimaryMode, 1436 cRFStatusDuplexMode, 1437 cRFStatusManualSwactInhibit, 1438 cRFStatusLastSwactReasonCode, 1439 cRFStatusFailoverTime, 1440 cRFStatusPeerStandByEntryTime 1441 } 1442 STATUS current 1443 DESCRIPTION "The collection of global RF Status objects." 1444 ::= { ciscoRFMIBGroups 5 } 1445 1446ciscoRFHistoryGroup OBJECT-GROUP 1447 OBJECTS { 1448 cRFHistoryPrevActiveUnitId, 1449 cRFHistoryCurrActiveUnitId, 1450 cRFHistorySwitchOverReason, 1451 cRFHistorySwactTime, 1452 cRFHistoryColdStarts, 1453 cRFHistoryStandByAvailTime, 1454 cRFHistoryTableMaxLength 1455 } 1456 STATUS current 1457 DESCRIPTION "The collection of RF History objects." 1458 ::= { ciscoRFMIBGroups 6 } 1459 1460ciscoRFConfigRFOperModeGroup OBJECT-GROUP 1461 OBJECTS { cRFCfgRedundancyOperMode } 1462 STATUS current 1463 DESCRIPTION 1464 "An optional group with a collection of objects providing 1465 the information of the operational redundancy mode on the 1466 device." 1467 ::= { ciscoRFMIBGroups 7 } 1468 1469ciscoRFStatusRFModeCapsGroup OBJECT-GROUP 1470 OBJECTS { cRFStatusRFModeCapsModeDescr } 1471 STATUS current 1472 DESCRIPTION 1473 "An optional group with a collection of objects 1474 providing the information of redundancy mode capability 1475 on the device." 1476 ::= { ciscoRFMIBGroups 8 } 1477 1478ciscoRFIssuStateNotifGroup NOTIFICATION-GROUP 1479 NOTIFICATIONS { ciscoRFIssuStateNotif } 1480 STATUS deprecated 1481 DESCRIPTION 1482 "The collection of notifications used to indicate 1483 ISSU state of the system." 1484 ::= { ciscoRFMIBGroups 9 } 1485 1486ciscoRFIssuStateNotifGroupRev1 NOTIFICATION-GROUP 1487 NOTIFICATIONS { ciscoRFIssuStateNotifRev1 } 1488 STATUS current 1489 DESCRIPTION 1490 "The collection of notifications used to indicate 1491 ISSU state of the system." 1492 ::= { ciscoRFMIBGroups 10 } 1493 1494ciscoRFIssuStateObjGroup OBJECT-GROUP 1495 OBJECTS { cRFStatusIssuState } 1496 STATUS deprecated 1497 DESCRIPTION 1498 "An optional group with a collection of objects providing 1499 the information on the current ISSU state of the system." 1500 ::= { ciscoRFMIBGroups 11 } 1501 1502ciscoRFIssuStateObjGroupRev1 OBJECT-GROUP 1503 OBJECTS { 1504 cRFStatusIssuStateRev1, 1505 cRFStatusIssuFromVersion, 1506 cRFStatusIssuToVersion 1507 } 1508 STATUS current 1509 DESCRIPTION 1510 "An optional group with a collection of objects providing 1511 the information on the current ISSU state of the system." 1512 ::= { ciscoRFMIBGroups 12 } 1513 1514ciscoRFStatusClientGroup OBJECT-GROUP 1515 OBJECTS { 1516 cRFStatusRFClientDescr, 1517 cRFStatusRFClientSeq, 1518 cRFStatusRFClientRedTime, 1519 cRFStatusRFClientStatus 1520 } 1521 STATUS current 1522 DESCRIPTION 1523 "A group of objects providing information regarding the 1524 various clients registered with the RF." 1525 ::= { ciscoRFMIBGroups 13 } 1526 1527END 1528