-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathCISCO-RF-MIB
1527 lines (1381 loc) · 55.4 KB
/
CISCO-RF-MIB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
-- *****************************************************************
-- CISCO-RF-MIB.my:
-- Descriptions of managed objects for the Redundancy Framework
-- (RF) subsystem.
--
-- August 2000, Timothy Kurnik and Bo Berry
-- December 2001, Liwei Wang
--
-- Copyright (c) 2000-2006 by Cisco Systems Inc.
-- All rights reserved.
-- ****************************************************************
CISCO-RF-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY,
OBJECT-TYPE,
NOTIFICATION-TYPE,
Counter32,
Integer32,
Unsigned32
FROM SNMPv2-SMI
MODULE-COMPLIANCE,
NOTIFICATION-GROUP,
OBJECT-GROUP
FROM SNMPv2-CONF
TEXTUAL-CONVENTION,
TruthValue,
DateAndTime,
TimeStamp,
TimeInterval
FROM SNMPv2-TC
sysUpTime
FROM SNMPv2-MIB
SnmpAdminString
FROM SNMP-FRAMEWORK-MIB
ciscoMgmt
FROM CISCO-SMI;
ciscoRFMIB MODULE-IDENTITY
LAST-UPDATED "200509010000Z"
ORGANIZATION "Cisco Systems, Inc."
CONTACT-INFO
"Cisco Systems Customer Service
Postal: 170 West Tasman Drive
San Jose, CA 95134
USA
Tel: +1 800 553-NETS
E-mail: [email protected]"
DESCRIPTION
"This MIB provides configuration control and status for the
Redundancy Framework (RF) subsystem. RF provides a mechanism
for logical redundancy of software functionality and is
designed to support 1:1 redundancy on processor cards. RF is
not intended to solve all redundancy schemes. Nor is RF
designed to support redundant hardware, such as power
supplies.
Redundancy is concerned with the duplication of data elements
and software functions to provide an alternative in case of
failure. It is a key component to meeting 99.999% availability
requirements for Class 5 carrier solutions.
In the scope of this MIB definition, peer software elements
are redundant and redundant software elements are peers."
REVISION "200509010000Z"
DESCRIPTION
"Added a new textual convention : RFClientStatus.
Added the cRFStatusRFClientTable which contains information
about all the clients registered with the Redundancy
Facility (RF). "
REVISION "200404010000Z"
DESCRIPTION
"Added the new states, systemReset, loadVersionSwitchover
and runVersionSwitchover. The unset state has been removed
and the init state will represent the absense of the ISSU
process. Updated the object cRFStatusIssuState to
cRFStatusIssuStateRev1 as the ISSU states have been revised.
Added new object, cRFStatusIssuFromVersion and
cRFStatusIssuToVersion which represent the from and the to
versions of IOS that are involved in the upgrade process.
The object ciscoRFIssuStateObjGroup was changed to
ciscoRFIssuStateObjGroupRev1 to accomodate these new
objects."
REVISION "200402040000Z"
DESCRIPTION
"Added ciscoRFIssuStateNotifGroup and ciscoRFIssuStateObjGroup
that represent the notification group and the object group
that represents the ISSU state of the system."
REVISION "200310020000Z"
DESCRIPTION
"Changed the description for ciscoRFProgressionNotif"
REVISION "200201070000Z"
DESCRIPTION
"Added the following object in cRFStatus:
cRFStatusRFModeCapsTable
Added the following object in cRFCfg:
cRFCfgRedundancyOperMode
Updated description of following object in cRFCfg:
cRFCfgRedundancyMode"
REVISION "200107200000Z"
DESCRIPTION
"Added new sub-group
cRFHistory
Added new table cRFHistorySwitchOverTable
which maintains the history of switchovers.
Also added objects:
cRFStatusFailoverTime
cRFStatusPeerStandByEntryTime
cRFHistoryTableMaxLength
cRFHistoryColdStarts
cRFHistoryStandByAvailTime
Added textual convention:
RFUnitIdentifier."
REVISION "200106260000Z"
DESCRIPTION
"Changed terminology:
'split-mode' is now 'maintenance-mode'
Added textual convention:
RFMode
Deprecated object:
cRFCfgSplitMode
Added objects:
cRFCfgMaintenanceMode
cRFCfgRedundancyMode
cRFCfgRedundancyModeDescr
Added enumeration values:
noAction(0) to RFAction
activeExtraload(15) to RFState
activeHandback(16) to RFState
Added new transition state to ciscoRFProgressionNotif:
activeExtraload
Update compliance and conformance statements"
REVISION "200104030945Z"
DESCRIPTION
"The initial revision of this MIB."
::= { ciscoMgmt 176 }
-- Glossary
--
-- Active Unit - The CPU on which calls are being processed.
--
-- Availability - Availability is measured as a percentage of
-- uptime. Based on continuous system operation which is typically
-- 24 hours per day, 7 days per week, 365 days a year.
--
-- Bulk Sync - The process of updating the standby unit to the current
-- context of the active unit. Once the Bulk sync is complete the
-- standby unit is considered 'hot' and able to become the active unit.
--
-- Clients - Applications that have registered with the Redundancy
-- Facility (RF) to receive RF events and notifications. These are
-- considered redundancy aware applications.
--
-- Cold Redundancy - A redundancy scheme that is not able to instantly
-- retain established calls and immediately able to handle new
-- calls. The standby unit in a cold redundancy system is not fully
-- initialized and is not able to retain established calls.
--
-- Configuration Data - Data that the user configures for the
-- application and networking requirements. PVCs would fall into this
-- category.
--
-- Cutover - A canonical term referring to either a switch-over or a
-- fail-over.
--
-- Data Events - Messages, such as ATM SVC events, sent from active
-- unit clients to the standby clients. Data Events are used to keep a
-- standby-hot unit up-to-date with dynamic data changes on the active
-- unit.
--
-- Drop Activity - The process by which the currently active unit
-- relinquishes activity to the standby unit. The active unit can only
-- drop activity to a standby-cold or standby-hot unit. This can be
-- for one of two reasons:
--
-- - the currently active unit has determined that it is unhealthy
-- and needs to release activity to the standby, or
--
-- - the user issues a command to drop activity. This is typically
-- done for maintenance purposes such as upgrading to a new
-- image in the standby.
--
-- Duplex Mode - The mode of operation when both control processors,
-- one active and one standby, are present in the system. As opposed
-- to simplex mode.
--
-- Dynamic Data - Dynamic Data is data that changes in real time. It
-- is this data that is synced from the active to the standby unit.
-- The type and frequency of dynamic data syncs is client
-- specific. ATM SVCs fall into this category. Once the SVC is
-- established on the active unit, ATM sends SVC Data Events to the
-- standby unit.
--
-- Gain Activity - The process by which the standby unit becomes the
-- active unit.
--
-- Hot Redundancy - A redundancy scheme that is able to instantly
-- retain established calls and immediately able to handle new calls.
--
-- Load Sharing - A high availability scheme whereby a portion of the
-- system load is statically assigned to each processor/resource. The
-- assignment of resources may be decided based on ingress interface,
-- line card, etc. No dynamic decisions are made as to the load
-- distribution in the system; it is pre-determined.
--
-- Negotiation Clash - The situation when two loosely coupled units
-- think both have the same negotiation status. In this case, the
-- primary unit should over ride the secondary unit.
--
-- Peer Unit - The Secondary Unit is the peer to the Primary Unit,
-- and the Primary Unit is the peer to the Secondary Unit.
--
-- Primary Unit - This is the unit that wins in the unlikely event of
-- a negotiation clash between two loosely coupled units. For example,
-- if both units think they are active, the Primary unit is designed
-- to remain active while the Secondary Unit backs down to standby. If
-- both units think they are standby, the Primary unit is designed to
-- gain activity while the Secondary Unit remains the standby.
--
-- Progression - The process of making redundancy state of the standby
-- unit equivalent to that of the active unit. This includes
-- transitioning the RF state machine through several states which in
-- turn drives the RF clients on the active unit to synchronize any
-- relevant data with their peer on the standby unit.
--
-- Secondary Unit - This is the unit that backs-down in the unlikely
-- event of a negotiation clash between two loosely coupled units. For
-- example, if both units think they are active, the Secondary unit is
-- designed to back down while the Primary unit remains active. If
-- both units think they are standby, the Secondary unit is designed to
-- remain standby while the Primary unit gains activity.
--
-- Simplex Mode - The mode of operation when only a single control
-- processor is present in the system. As opposed to duplex mode.
--
-- Maintenance Mode - A mode in redundancy where the standby unit is
-- present (duplex) but logically disconnected from the active
-- unit. Clients do not send data syncs to the standby unit. This mode
-- is useful for software upgrades and other maintenance procedures.
--
-- Standby Unit - The unit which is backing-up the currently Active
-- unit. The Standby unit has several substates that are specific to
-- becoming standby-hot. Once the standby unit progresses to
-- standby-hot, it is able to instantly become the active unit while
-- retaining calls.
--
-- Switch of Activity (SWACT) - Either a forced or automatic switch
-- of active status from the active unit to the standby unit. The
-- former standby unit is now referred to as the active unit.
--
-- Take Activity - The process by which the standby unit becomes the
-- active unit. This can be for one of two reasons:
--
-- - the standby unit has determined that the currently active unit
-- is unhealthy and takes activity, or
--
-- - the user issues a command to switch activity from the currently
-- active unit. This is typically done for maintenance purposes
-- such as upgrading the standby unit.
--
-- ISSU - In Service Software Upgrade
-- IOS Software upgrades between different images will be
-- possible using the new infrastructure that has been developed
-- as a part of SSO. It will allow for Stateful Switchovers,
-- and hence hitless upgrades between different image versions.
--
--
-- Textual conventions
RFState ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The current state of the RF subsystem.
notKnown
- state is unknown
disabled
- RF is not operational on this unit
initialization
- establish necessary system services
negotiation
- peer unit discovery and negotiation
standbyCold
- client notification on standby unit
*standbyColdConfig
- standby configuration is updated from active configuration
*standbyColdFileSys
- standby file system (FS) is updated from the active FS
*standbyColdBulk
- clients sync data from active to standby
standbyHot
- incremental client data sync continues. This unit is
ready to take over activity.
activeFast
- call maintenance efforts during a SWACT
activeDrain
- client clean-up phase
activePreconfig
- unit is active but has not read its configuration
activePostconfig
- unit is active and is post-processing its configuration
active
- unit is active and processing calls
activeExtraload
- unit is active and processing calls for all feature
boards in the system
activeHandback
- unit is active, processing calls and is in the process
of handing some resources to the other unit in the system
* Sub-state of 'standbyCold'"
SYNTAX INTEGER {
notKnown(1),
disabled(2),
initialization(3),
negotiation(4),
standbyCold(5),
standbyColdConfig(6),
standbyColdFileSys(7),
standbyColdBulk(8),
standbyHot(9),
activeFast(10),
activeDrain(11),
activePreconfig(12),
activePostconfig(13),
active(14),
activeExtraload(15),
activeHandback(16)
}
RFMode ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The characterization of the redundancy subsystem.
nonRedundant
- the system is not redundant.
staticLoadShareNonRedundant
- the system is *not* redundant but is load sharing.
The load sharing is *not* based on operational load
(i.e. number of calls, etc).
dynamicLoadShareNonRedundant
- the system is *not* redundant but is load sharing.
Load sharing is based on operational load.
staticLoadShareRedundant
- the system is redundant and is load sharing. The
load sharing is *not* based on operational load.
dynamicLoadShareRedundant
- the system is redundant and is load sharing. Load
sharing is based on operational load.
coldStandbyRedundant
- the system is redundant but the redundant peer unit is
not fully initialized and is not able to retain
established calls.
warmStandbyRedundant
- the system is redundant and the redundant peer unit is
immediately able to handle new calls. The redundant
unit is unable to retain established calls.
hotStandbyRedundant
- the system is redundant and the redundant peer unit is
able to 'instantaneously' retain established calls and
immediately able to handle new calls."
SYNTAX INTEGER {
nonRedundant(1),
staticLoadShareNonRedundant(2),
dynamicLoadShareNonRedundant(3),
staticLoadShareRedundant(4),
dynamicLoadShareRedundant(5),
coldStandbyRedundant(6),
warmStandbyRedundant(7),
hotStandbyRedundant(8)
}
RFAction ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Administrative commands to invoke in the RF subsystem.
noAction
- no action (do nothing)
reloadPeer
- reset the redundant peer unit
reloadShelf
- reset the entire shelf
switchActivity
- safely SWACT to peer unit and go standby
forceSwitchActivity
- switch activity; ignoring pre-conditions, system
warnings and safety checks.
When the value is set to 'noAction' no operation is performed.
When read, the value 'noAction' is always returned."
SYNTAX INTEGER {
noAction(0),
reloadPeer(1),
reloadShelf(2),
switchActivity(3),
forceSwitchActivity(4)
}
RFSwactReasonType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Reason codes for the switch of activity from an active
redundant unit to its standby peer unit.
unsupported
- the 'reason code' is an unsupported feature
none
- no SWACT has occurred
notKnown
- reason is unknown
userInitiated
- a safe, manual SWACT was initiated by user
userForced
- a manual SWACT was forced by user; ignoring
pre-conditions, warnings and safety checks
activeUnitFailed
- active unit failure caused an auto SWACT
activeUnitRemoved
- active unit removal caused an auto SWACT"
SYNTAX INTEGER {
unsupported(1),
none(2),
notKnown(3),
userInitiated(4),
userForced(5),
activeUnitFailed(6),
activeUnitRemoved(7)
}
RFUnitIdentifier ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "A unique identifier for Active/Standby unit."
SYNTAX Integer32 (0..2147483647 )
RFIssuState ::= TEXTUAL-CONVENTION
STATUS deprecated
DESCRIPTION
"ISSU state represents the current system state.
unset
- unset state; if the system is booted from tftp or from
ROMMON such that the image is not the first in BOOT
init
- init state; the first ISSU state that the system will
move to after the unset state, when the ISSU process
has just been kicked off. The first CLI that is executed
to make this happen is the loadversion CLI.
loadVersion
- Once the loadversion CLI has been executed, the state
of the system is changed to reflect this, and this state
is called the loadVersion state. The boot variable on
the Standby is updated to point to the new image that the
Standby needs to load and then it is reset.
runVersion
- runVersion state; When the system is in the loadversion
state, the Active is running the old image and the
Standby is running the new image. When the runversion
CLI is executed, a switchover occurs, and the Standby
running the new image takes over as the Active. The
state of the system at this stage is updated to
runversion.
commitVersion
- in the runversion state, the Active is running the
new image, and the Standby is running the old image.
When the user is satisfied with the functioning of
the system, they execute the commitversion CLI, which
will prepend the boot variable on the Standby with
the new image, and then the Standby is reset. After
this, the Standby comes up with the new image, and
the state of the system is updated to reflect the
commitVersion state."
SYNTAX INTEGER {
unset(0),
init(1),
loadVersion(2),
runVersion(3),
commitVersion(4)
}
RFIssuStateRev1 ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"ISSU state represents the current system state.
init
- This state represents the initial state of the system.
The ISSU process is not running at this stage. The only
CLI for ISSU process that can be executed in this state
is the loadversion CLI.
systemReset
- If a system reset occurs, or the abortversion CLI is
executed, the state of the system is pushed to this state.
loadVersion
- When the Standby signs in after the loadversion CLI
is executed, the state of the system is changed to
loadVersion.
loadVersionSwitchover
- If a switchover occurs in the loadVersion state, by
the user, or because the Active crashes, the new
state of the system will be loadVersionSwitchover.
It is analogous to the runVersion state, except that
the runversion CLI was not executed.
runVersion
- When the Standby signs in after executing the
runversion CLI, the state of the system is changed
to runVersion.
runVersionSwitchover
- if a switchover occurs while the system is in the
runVersion state, the new state will be called
runVersionSwitchover. It is analogous to the
loadVersion state.
commitVersion
- When the Standby signs in after the commitversion CLI
is executed, the state of the system is changed to
commitVersion."
SYNTAX INTEGER {
init(0),
systemReset(1),
loadVersion(3),
loadVersionSwitchover(4),
runVersion(6),
runVersionSwitchover(7),
commitVersion(9)
}
RFClientStatus ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The status of a RF client before, during and after
switchover.
noStatus
- No status information is available for this client.
clientNotRedundant
- Client is active. But there is no redundancy to this
client. This could be because there is no standby or
the client cannot claim that the standby client can
take over without losing data or traffic during a
switchover.
clientRedundancyInProgress
- The client is trying to sync all data to standby and
achieve redundancy.
clientRedundant
- The client is redundant and ready for switchover. The
client can safely claim that there is no data or traffic
loss if there is a switchover."
SYNTAX INTEGER {
noStatus(1),
clientNotRedundant(2),
clientRedundancyInProgress(3),
clientRedundant(4)
}
-- OBJECT IDENTIFIER assignments for various groups
ciscoRFMIBObjects OBJECT IDENTIFIER
::= { ciscoRFMIB 1 }
-- sub-groups
cRFStatus OBJECT IDENTIFIER
::= { ciscoRFMIBObjects 1 }
cRFCfg OBJECT IDENTIFIER
::= { ciscoRFMIBObjects 2 }
cRFHistory OBJECT IDENTIFIER
::= { ciscoRFMIBObjects 3 }
cRFClient OBJECT IDENTIFIER
::= { ciscoRFMIBObjects 4 }
-- Status sub-group definitions
cRFStatusUnitId OBJECT-TYPE
SYNTAX RFUnitIdentifier
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A unique identifier for this redundant unit. This identifier
is implementation-specific but the method for selecting the id
must remain consistent throughout the redundant system.
Some example identifiers include: slot id, physical or logical
entity id, or a unique id assigned internally by the RF
subsystem."
::= { cRFStatus 1 }
cRFStatusUnitState OBJECT-TYPE
SYNTAX RFState
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The current state of RF on this unit."
::= { cRFStatus 2 }
cRFStatusPeerUnitId OBJECT-TYPE
SYNTAX RFUnitIdentifier
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A unique identifier for the redundant peer unit. This
identifier is implementation-specific but the method for
selecting the id must remain consistent throughout the
redundant system.
Some example identifiers include: slot id, physical or logical
entity id, or a unique id assigned internally by the RF
subsystem."
::= { cRFStatus 3 }
cRFStatusPeerUnitState OBJECT-TYPE
SYNTAX RFState
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The current state of RF on the peer unit."
::= { cRFStatus 4 }
cRFStatusPrimaryMode OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates whether this is the primary redundant unit or
not. If this unit is the primary unit, this object is true. If
this unit is the secondary unit, this object is false.
Note that the terms 'primary/secondary' are not synonymous
with the terms 'active/standby'. At any given time, the
primary unit may be the active unit, or the primary unit may
be the standby unit. Likewise, the secondary unit, at any
given time, may be the active unit, or the secondary unit may
be the standby unit.
The primary unit is given a higher priority or precedence over
the secondary unit. In a race condition (usually at
initialization time) or any situation where the redundant
units are unable to successfully negotiate activity between
themselves, the primary unit will always become the active
unit and the secondary unit will fall back to standby. Only
one redundant unit can be the primary unit at any given time.
The algorithm for determining the primary unit is system
dependent, such as 'the redundant unit with the lower numeric
unit id is always the primary unit.'"
::= { cRFStatus 5 }
cRFStatusDuplexMode OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates whether the redundant peer unit has been detected
or not. If the redundant peer unit is detected, this object is
true. If the redundant peer unit is not detected, this object
is false."
::= { cRFStatus 6 }
cRFStatusManualSwactInhibit OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates whether a manual switch of activity is
permitted. If a manual switch of activity is allowed, this
object is false. If a manual switch of activity is not
allowed, this object is true. Note that the value of this
object is the inverse of the status of manual SWACTs.
This object does not indicate whether a switch of activity is
or has occurred. This object only indicates if the
user-controllable capability is enabled or not.
A switch of activity is the event in which the standby
redundant unit becomes active and the previously active unit
becomes standby."
::= { cRFStatus 7 }
cRFStatusLastSwactReasonCode OBJECT-TYPE
SYNTAX RFSwactReasonType
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The reason for the last switch of activity."
::= { cRFStatus 8 }
cRFStatusFailoverTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime when the primary redundant unit took over
as active. The value of this object will be 0 till the first
switchover."
::= { cRFStatus 9 }
cRFStatusPeerStandByEntryTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime when the peer redundant unit entered the
standbyHot state. The value will be 0 on system initialization."
::= { cRFStatus 10 }
-- Redundancy mode capability table
cRFStatusRFModeCapsTable OBJECT-TYPE
SYNTAX SEQUENCE OF CRFStatusRFModeCapsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table containing a list of redundancy modes that can be
supported on the device."
::= { cRFStatus 11 }
cRFStatusRFModeCapsEntry OBJECT-TYPE
SYNTAX CRFStatusRFModeCapsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry containing the device implementation specific
terminology associated with the redundancy mode that can be
supported on the device."
INDEX { cRFStatusRFModeCapsMode }
::= { cRFStatusRFModeCapsTable 1 }
CRFStatusRFModeCapsEntry ::= SEQUENCE {
cRFStatusRFModeCapsMode RFMode,
cRFStatusRFModeCapsModeDescr SnmpAdminString
}
cRFStatusRFModeCapsMode OBJECT-TYPE
SYNTAX RFMode
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The redundancy mode that can be supported on the device."
::= { cRFStatusRFModeCapsEntry 1 }
cRFStatusRFModeCapsModeDescr OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The description of the device implementation specific
terminology associated with its supported redundancy mode."
::= { cRFStatusRFModeCapsEntry 2 }
cRFStatusIssuState OBJECT-TYPE
SYNTAX RFIssuState
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION "The current ISSU state of the system."
::= { cRFStatus 12 }
cRFStatusIssuStateRev1 OBJECT-TYPE
SYNTAX RFIssuStateRev1
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The current ISSU state of the system."
::= { cRFStatus 13 }
cRFStatusIssuFromVersion OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The IOS version from with the user is upgrading"
::= { cRFStatus 14 }
cRFStatusIssuToVersion OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The IOS version to with the user is upgrading"
::= { cRFStatus 15 }
-- Redundancy Facility (RF) Client Table
cRFStatusRFClientTable OBJECT-TYPE
SYNTAX SEQUENCE OF CRFStatusRFClientEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains a list of RF clients that are
registered on the device.
RF clients are applications that have registered with
the Redundancy Facility (RF) to receive RF events and
notifications. The purpose of RF clients is to synchronize
any relevant data with the standby unit."
::= { cRFClient 1 }
cRFStatusRFClientEntry OBJECT-TYPE
SYNTAX CRFStatusRFClientEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry containing information on various clients
registered with the Redundancy Facility (RF). Entries in
this table are always created by the system.
An entry is created in this table when a redundancy aware
application registers with the Redundancy Facility. The entry
is destroyed when that application deregisters from the
Redundancy Facility."
INDEX { cRFStatusRFClientID }
::= { cRFStatusRFClientTable 1 }
CRFStatusRFClientEntry ::= SEQUENCE {
cRFStatusRFClientID Unsigned32,
cRFStatusRFClientDescr SnmpAdminString,
cRFStatusRFClientSeq Unsigned32,
cRFStatusRFClientRedTime Unsigned32,
cRFStatusRFClientStatus RFClientStatus
}
cRFStatusRFClientID OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295 )
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A unique identifier for the client which registered with the
Redundancy Facility."
::= { cRFStatusRFClientEntry 1 }
cRFStatusRFClientDescr OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The description of the client which has registered with the
Redundancy Facility."
::= { cRFStatusRFClientEntry 2 }
cRFStatusRFClientSeq OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The sequence number of the client. The system assigns the
sequence numbers based on the order of registration of
the Redundancy Facility clients.
This is used for deciding order of RF events sent to clients."
::= { cRFStatusRFClientEntry 3 }
cRFStatusRFClientRedTime OBJECT-TYPE
SYNTAX Unsigned32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Time taken for this client to become Redundant. This value
is meaningful when the value of cRFStatusRFClientStatus is
not 'noStatus'."
::= { cRFStatusRFClientEntry 4 }
cRFStatusRFClientStatus OBJECT-TYPE
SYNTAX RFClientStatus
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object provides the status of the Redundancy Facility
client."
::= { cRFStatusRFClientEntry 5 }
-- Configuration sub-group definitions
cRFCfgSplitMode OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS deprecated
DESCRIPTION
"Indicates whether redundant units may communicate
synchronization messages with each other. If communication is
not permitted, this object is set to true. If communication is
permitted, this object is set to false.
In split mode (true), the active unit will not communicate
with the standby unit. The standby unit progression will not
occur. When split mode is disabled (false), the standby unit
is reset to recover.
Split mode (true) is useful for maintenance operations.
"
::= { cRFCfg 1 }
cRFCfgKeepaliveThresh OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"On platforms that support keep-alives, the keep-alive
threshold value designates the number of lost keep-alives
tolerated before a failure condition is declared. If this
occurs, a SWACT notification is sent.
On platforms that do not support keep-alives, this object has
no purpose or effect."
::= { cRFCfg 2 }
cRFCfgKeepaliveThreshMin OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The minimum acceptable value for the cRFCfgKeepaliveThresh
object."
::= { cRFCfg 3 }
cRFCfgKeepaliveThreshMax OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum acceptable value for the cRFCfgKeepaliveThresh
object."
::= { cRFCfg 4 }
cRFCfgKeepaliveTimer OBJECT-TYPE
SYNTAX Unsigned32
UNITS "milliseconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"On platforms that support keep-alives, the keep-alive timer
value is used to guard against lost keep-alives. The RF
subsystem expects to receive a keep-alive within this period.
If a keep-alive is not received within this time period, a
SWACT notification is sent.
On platforms that do not support keep-alives, this object has
no purpose or effect."
::= { cRFCfg 5 }
cRFCfgKeepaliveTimerMin OBJECT-TYPE
SYNTAX Unsigned32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The minimum acceptable value for the cRFCfgKeepaliveTimer
object."
::= { cRFCfg 6 }
cRFCfgKeepaliveTimerMax OBJECT-TYPE
SYNTAX Unsigned32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum acceptable value for the cRFCfgKeepaliveTimer
object."
::= { cRFCfg 7 }
cRFCfgNotifTimer OBJECT-TYPE
SYNTAX Unsigned32
UNITS "milliseconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Note that the term 'notification' here refers to an RF
notification and not an SNMP notification.
As the standby unit progresses to the 'standbyHot' state,
asynchronous messages are sent from the active unit to the
standby unit which must then be acknowledged by the standby
unit. If the active unit receives the acknowledgement during
the time period specified by this object, progression proceeds
as normal. If the timer expires and an acknowledgement was not
received by the active unit, a switch of activity occurs."
::= { cRFCfg 8 }
cRFCfgNotifTimerMin OBJECT-TYPE
SYNTAX Unsigned32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The minimum acceptable value for the cRFCfgNotifTimer
object."
::= { cRFCfg 9 }
cRFCfgNotifTimerMax OBJECT-TYPE
SYNTAX Unsigned32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum acceptable value for the cRFCfgNotifTimer
object."
::= { cRFCfg 10 }
cRFCfgAdminAction OBJECT-TYPE
SYNTAX RFAction