Class syshist:ExtChCardRstRec (CONCRETE)

Class ID:2988
Class Label: Extended Chassis Card Reset Record
Encrypted: false - Exportable: false - Persistent: true - Configurable: false - Subject to Quota: Disabled
Write Access: [NON CONFIGURABLE]
Read Access: [access-equipment, admin, fabric-equipment, ops]
Creatable/Deletable: yes (see Container Mos for details)
Semantic Scope: Fabric
Semantic Scope Evaluation Rule: Parent
Monitoring Policy Source: Parent
Monitoring Flags : [ IsObservable: false, HasStats: false, HasFaults: false, HasHealth: false, HasEventRules: false ]

The extended chassis card reset record.

Naming Rules
RN FORMAT: rstrec-{ts}

    [1] PREFIX=rstrec- PROPERTY = ts




DN FORMAT: 

[0] topology/pod-{id}/node-{id}/sys/extch-{id}/extchslot-{id}/rstrec-{ts}

[1] sys/extch-{id}/extchslot-{id}/rstrec-{ts}

                


Diagram

Super Mo: syshist:RstRec,
Container Mos: eqpt:ExtChCardSlot (deletable:yes),


Containers Hierarchies
[V] top:Root  This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
[V] fabric:Topology The root for IFC topology.
 
 ├
[V] fabric:Pod A pod.
 
 
 ├
[V] fabric:Node The root node for the APIC.
 
 
 
 ├
[V] top:System The APIC uses a policy model to combine data into a health score. Health scores can be aggregated for a variety of areas such as for the infrastructure, applications, or services. The category health score is calculated using a Lp -Norm formula. The health score penalty equals 100 minus the health score. The health score penalty represents the overall health score penalties of a set of MOs that belong to a given category and are children or direc...
 
 
 
 
 ├
[V] eqpt:ExtCh The fabric extended chassis.
 
 
 
 
 
 ├
[V] eqpt:ExtChCardSlot The extended chassis card slot.
 
 
 
 
 
 
 ├
[V] syshist:ExtChCardRstRec The extended chassis card reset record.
[V] top:Root  This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
[V] top:System The APIC uses a policy model to combine data into a health score. Health scores can be aggregated for a variety of areas such as for the infrastructure, applications, or services. The category health score is calculated using a Lp -Norm formula. The health score penalty equals 100 minus the health score. The health score penalty represents the overall health score penalties of a set of MOs that belong to a given category and are children or direc...
 
 ├
[V] eqpt:ExtCh The fabric extended chassis.
 
 
 ├
[V] eqpt:ExtChCardSlot The extended chassis card slot.
 
 
 
 ├
[V] syshist:ExtChCardRstRec The extended chassis card reset record.


Contained Hierarchy
[V] syshist:ExtChCardRstRec The extended chassis card reset record.


Inheritance
[V] syshist:RstRec The reset records.
 ├
[V] syshist:ExtChCardRstRec The extended chassis card reset record.


Events
                


Faults
                


Fsms
                


Properties Summary
Defined in: syshist:ExtChCardRstRec
scalar:Date ts  (syshist:ExtChCardRstRec:ts)
           Overrides:syshist:RstRec:ts
           The day and time of the task or update.
Defined in: syshist:RstRec
syshist:RstRsn
          scalar:Enum8
reason  (syshist:RstRec:reason)
          
syshist:RstRsnQual
          string:Basic
reasonQual  (syshist:RstRec:reasonQual)
          
cap:Version
          string:Basic
ver  (syshist:RstRec:ver)
           The CDP version supported by the device.
Defined in: mo:TopProps
mo:ModificationChildAction
          scalar:Bitmask32
childAction  (mo:TopProps:childAction)
           Delete or ignore. For internal use only.
reference:BinRef dn  (mo:TopProps:dn)
           A tag or metadata is a non-hierarchical keyword or term assigned to the fabric module.
reference:BinRN rn  (mo:TopProps:rn)
           Identifies an object from its siblings within the context of its parent object. The distinguished name contains a sequence of relative names.
mo:ModificationStatus
          scalar:Bitmask32
status  (mo:TopProps:status)
           The upgrade status. This property is for internal use only.
Defined in: mo:Modifiable
mo:TStamp
          scalar:Date
modTs  (mo:Modifiable:modTs)
           The time when this object was last modified.
Properties Detail

childAction

Type: mo:ModificationChildAction
Primitive Type: scalar:Bitmask32

Units: null
Encrypted: false
Access: implicit
Category: TopLevelChildAction
    Comments:
Delete or ignore. For internal use only.
Constants
deleteAll 16384u deleteAll NO COMMENTS
ignore 4096u ignore NO COMMENTS
deleteNonPresent 8192u deleteNonPresent NO COMMENTS
DEFAULT 0 --- This type is used to





dn

Type: reference:BinRef

Units: null
Encrypted: false
Access: implicit
Category: TopLevelDn
    Comments:
A tag or metadata is a non-hierarchical keyword or term assigned to the fabric module.



modTs

Type: mo:TStamp
Primitive Type: scalar:Date

Units: null
Encrypted: false
Access: implicit
Category: TopLevelRegular
    Comments:
The time when this object was last modified.
Constants
never 0ull never NO COMMENTS
DEFAULT never(0ull) never NO COMMENTS





reason

Type: syshist:RstRsn
Primitive Type: scalar:Enum8

Units: null
Encrypted: false
Access: oper
Category: TopLevelRegular
    Comments:
Constants
unknown 0 Unknown Unknown
reboot 1 Kernel Reboot Kernel Reboot
watchdog 2 Watchdog Timeout Watchdog
sysmgr 3 Reset Requested due to Fatal System Error Sysmgr reset
mod-err 4 Reset Requested due to Fatal Module Error NO COMMENTS
pwr-cfg 5 Configured Power down NO COMMENTS
temp-alaram 6 Power down due to temperature sensor policy trigger NO COMMENTS
user-switchover 7 Reset triggered due to Switchover Request by User NO COMMENTS
upg-err 8 Reset Requested due to Fatal Upgrade Error NO COMMENTS
reload 9 Reset Requested by CLI command reload NO COMMENTS
sprom-upd 10 Reset Requested due to SPROM update NO COMMENTS
sys-cfg-dwn 11 System Reset due to Element Manager NO COMMENTS
clock 12 System Reset due to Clock failure NO COMMENTS
halt 13 Kernel Halt NO COMMENTS
redundancy 14 Reset Requested by Redundancy NO COMMENTS
ha-switchover 15 Reset triggered due to HA policy of Switchover NO COMMENTS
ha-reset 16 Reset triggered due to HA policy of Reset NO COMMENTS
pfm-rtime 17 Power down triggered due to Platform manager runtime error NO COMMENTS
pfm-power-dwn 18 Power down triggered due to Platform manager event NO COMMENTS
panic 19 Kernel Panic NO COMMENTS
mgmt-app 20 Reset Requested by management application NO COMMENTS
hw 21 Reset triggered due to Hardware Error NO COMMENTS
asic 22 Reset performed due to component Error NO COMMENTS
redun-channel 23 Reset triggered due to bad redundancy channel NO COMMENTS
sys-health 24 Reset due to bad HW detected by System Health NO COMMENTS
eobc 25 Reset triggered due to bad backplane communication channel NO COMMENTS
boot-err 27 Reset (powered-down) because module does not boot NO COMMENTS
no-bootflash 28 Reset (powered-down) because there is no bootflash NO COMMENTS
netboot-err 29 Reset (powered-down) because netboot failed NO COMMENTS
bootflash-corrupt 30 Reset (powered-down) because bootflash access failed NO COMMENTS
installer 31 Reset by installer NO COMMENTS
epld 33 Power Down/UP epld upgrade process NO COMMENTS
sigkill-fail 34 Reset triggered due to failure to respond to SIGKILL NO COMMENTS
sys-gen-fail 35 Reset triggered by System Manager for generic failure NO COMMENTS
clock-switchover 37 VegasLC Reset due to Clock SwitchOver NO COMMENTS
insufficient-resource 38 Reset (powered-down) because of insufficient resources (DI) NO COMMENTS
incompat-config 43 Reset (powered-down) because of incompatible configuration NO COMMENTS
lcm-unknown 44 Unknown reason lcm reason codes
lcm-ha-restart 45 HA System restart NO COMMENTS
lcm-haswitchover-done 46 HA-Switchover done NO COMMENTS
lcm-boot-srg-timeout 47 SRG info response timeout NO COMMENTS
lcm-coredump 48 Core dump initiation NO COMMENTS
lcm-disruptive-upg 49 Disruptive upgrade NO COMMENTS
lcm-lc-fail 50 Line card failure NO COMMENTS
lcm-hitless-mod-rem 51 Hitless module removal NO COMMENTS
lcm-hitless-pwr-dwn 52 Hitless power down NO COMMENTS
lcm-hitless-proc-notice 53 Catastrophic error from LC NO COMMENTS
lcm-hitless-reg-fail 54 Hitless registration failed NO COMMENTS
lcm-hitless-timeout 55 Hitless upgrade timeout NO COMMENTS
lcm-img-upg-timeout 56 Line card image upgrade (failure) NO COMMENTS
lcm-img-upgsuccess 57 Line card image upgrade (success) NO COMMENTS
lcm-lc-ins-seq-fail 58 LC insertion sequence failure NO COMMENTS
lcm-hitless-upg-fail 59 Hitless upgrade failed NO COMMENTS
lcm-lc-no-resp 60 Line card not responding NO COMMENTS
lcm-lc-reg-more3 61 Line card 3+ registration NO COMMENTS
lcm-lc-reg-timeout 62 Line card registration timeout NO COMMENTS
lcm-runtime-diag-fail 63 Runtime diagnostic failure NO COMMENTS
lcm-runtime-diag-timeout 64 Runtime diagnostic timeout NO COMMENTS
lcm-seeprom-timeout 65 Line card SEEPROM contents response timeout NO COMMENTS
lcm-proc-notice 66 Line card catastrophic error NO COMMENTS
lcm-save-state-fail 67 Save state response (failure) NO COMMENTS
lcm-hitfull-img-check 68 Hitful image compatibility check NO COMMENTS
lcm-img-check-pwr-cycle 69 Image compatibility check (action:powercycle) NO COMMENTS
lcm-img-check-pwr-dwn 70 Image compatibility check (action:powerdown) NO COMMENTS
lcm-img-check-switch-over 71 Switchover : Image compatibility check NO COMMENTS
lcm-power-down 72 Module is powered down or power cycled NO COMMENTS
lcm-sup-rem 73 Supervisor card is removed or power cycled NO COMMENTS
lcm-lc-rem 74 Module is removed NO COMMENTS
lcm-unknown-mod 75 Unknown line card insertion NO COMMENTS
lcm-srg-timeout 76 SRG infor response timeout NO COMMENTS
lcm-async-notice-fail 77 Stop async notice failed NO COMMENTS
lcm-switchover-fail 78 Switchover failed NO COMMENTS
lcm-timeout 79 Addon image response timeout NO COMMENTS
lcm-srg-incompat 80 Upgraded SRG incompatible NO COMMENTS
outofservice 86 Out of service NO COMMENTS
sup-dev-err 87 Supervisor Device Error NO COMMENTS
issu-restart 88 Reset due to upgrade NO COMMENTS
ins-seq-fail-pwr-dwn 89 Reset (powered-down) due to insertion sequence failed NO COMMENTS
no-sup 92 Reset due to no sup NO COMMENTS
bad-volt 93 Reset due to Bad Voltage NO COMMENTS
bad-bus-volt 94 Reset due to bad system bus voltage NO COMMENTS
bad-intermediate-bus-volt 95 Reset due to bad intermediate bus voltage NO COMMENTS
psp 96 Reset due to CMP NO COMMENTS
eem-pwr-dwn 97 Powered-down due to EEM event policy trigger NO COMMENTS
usd-fail 98 Reset due to USD Failure NO COMMENTS
ejector 99 All the ejectors are OPEN NO COMMENTS
sys-rst 100 System reset by active sup (by writing to PMFPGA regs) NO COMMENTS
push-button 101 linecard reset by push button NO COMMENTS
policy-reset 103 Policy trigger initiated reset: NO COMMENTS
policy-fan 104 Powered-down due to fan policy trigger NO COMMENTS
chassis-rst 105 Chassis reset by Sup NO COMMENTS
max-switchover 107 Reset (powered-down) since maximum number of swovers were exceeded NO COMMENTS
switchover-timeout 108 Reset since switchover timeout NO COMMENTS
sysmgr-timeout 109 Reset of standby by active sup due to sysmgr timeout NO COMMENTS
unknown-mod 110 Unsupported/Unknown Module NO COMMENTS
mod-fail 111 Module Failed NO COMMENTS
mod-pwr-cycle 112 Module PowerCycled NO COMMENTS
card-incompat 113 Module not supported in this chassis NO COMMENTS
idprom-err 114 Bootup error accessing module IDPROM NO COMMENTS
unspecified 115 Non-specific deadend error, check platform int error NO COMMENTS
no-plugin 117 plugin absent/ not loaded NO COMMENTS
sw-card-id-unknown 118 Unknown card (Could not get software-card-id) NO COMMENTS
mod-fail-pwr-up 119 Unable to power up card (Power-OK not set) NO COMMENTS
max-bring-up-exceed 120 failure(powered-down) since maximum number of bringups were exceeded NO COMMENTS
epld-upg-nw-crd-mode 125 Power Down/UP epld upgrade process NO COMMENTS
deep-sleep 126 Preparing to enter deep sleep mode NO COMMENTS
epc-fail 130 EPC failure NO COMMENTS
klm-fail 131 KLM load failure NO COMMENTS
dme-clean-config-reset 132 Dme clean config reset NO COMMENTS
last-fc-down 133 Reloading linecard on removal of last fabric card NO COMMENTS
decommissioned 134 Decommissioned NO COMMENTS
last-sc-down 136 Reloading linecard and fabric card on removal of last SC NO COMMENTS
ssd-firmware-upgrade 139 System power-cycled due to SSD firmware upgrade NO COMMENTS
DEFAULT 0 --- Reset reason





reasonQual

Type: syshist:RstRsnQual
Primitive Type: string:Basic

Units: null
Encrypted: false
Access: oper
Category: TopLevelRegular
    Comments:



rn

Type: reference:BinRN

Units: null
Encrypted: false
Access: implicit
Category: TopLevelRn
    Comments:
Identifies an object from its siblings within the context of its parent object. The distinguished name contains a sequence of relative names.



status

Type: mo:ModificationStatus
Primitive Type: scalar:Bitmask32

Units: null
Encrypted: false
Access: implicit
Category: TopLevelStatus
    Comments:
The upgrade status. This property is for internal use only.
Constants
created 2u created In a setter method: specifies that an object should be created. An error is returned if the object already exists.
In the return value of a setter method: indicates that an object has been created.
modified 4u modified In a setter method: specifies that an object should be modified
In the return value of a setter method: indicates that an object has been modified.
deleted 8u deleted In a setter method: specifies that an object should be deleted.
In the return value of a setter method: indicates that an object has been deleted.
DEFAULT 0 --- This type controls the life cycle of objects passed in the XML API.

When used in a setter method (such as configConfMo), the ModificationStatus specifies whether an object should be created, modified, deleted or removed.
In the return value of a setter method, the ModificationStatus indicates the actual operation that was performed. For example, the ModificationStatus is set to "created" if the object was created. The ModificationStatus is not set if the object was neither created, modified, deleted or removed.

When invoking a setter method, the ModificationStatus is optional:
If a setter method such as configConfMo is invoked and the ModificationStatus is not set, the system automatically determines if the object should be created or modified.






ts

Type: scalar:Date

Overrides:syshist:RstRec:ts
Units: null Encrypted: false Naming Property -- [NAMING RULES] Access: naming Category: TopLevelRegular
    Comments:
The day and time of the task or update.



ver

Type: cap:Version
Primitive Type: string:Basic

Units: null
Encrypted: false
Access: oper
Category: TopLevelRegular
    Comments:
The CDP version supported by the device.