Overview  Containers  Contained  Inheritance  Events  Faults  FSMs  Properties Summary  Properties Detail  Naming 

Class fc:StatsHist (CONCRETE)

Class ID:155
Encrypted: false - Exportable: false - Persistent: false
Privileges: [read-only]
SNMP OID: .1.3.6.1.4.1.9.9.719.1.49.6

NO COMMENTS

Naming Rules 
RN FORMAT: [id]

    [1] PREFIX= PROPERTY = id




DN FORMAT: 

[0] fabric/san/[id]/pc-[portId]/stats/[id]

[1] sys/chassis-[id]/slot-[id]/[type]/port-[portId]/stats/[id]

[2] sys/fex-[id]/slot-[id]/[type]/port-[portId]/stats/[id]

[3] sys/chassis-[id]/shared-io-module/[type]/port-[portId]/stats/[id]

[4] sys/chassis-[id]/slot-[id]/shared-io-module/[type]/port-[portId]/stats/[id]

[5] sys/switch-[id]/slot-[id]/[type]/port-[portId]/stats/[id]

[6] sys/chassis-[id]/sw-slot-[id]/[type]/port-[portId]/stats/[id]

[7] sys/chassis-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]/stats/[id]

[8] sys/fex-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]/stats/[id]

[9] sys/chassis-[id]/shared-io-module/[type]/aggr-port-[aggrPortId]/port-[portId]/stats/[id]

[10] sys/chassis-[id]/slot-[id]/shared-io-module/[type]/aggr-port-[aggrPortId]/port-[portId]/stats/[id]

[11] sys/switch-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]/stats/[id]

[12] sys/chassis-[id]/sw-slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]/stats/[id]


Containers Hierarchies
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
 		fabric:Ep The root container of all fabric configuration objects.
 
 		 ├
 		fabric:SanCloud A container for logical Fibre Channel configuration Objects that span across the Fabric Interconnects. The contained configuration objects specify the logical Fibre Channel configuration, including fabric A and B, VSANs, pin groups, and threshold policy.
 
 		 
 		 ├
 		fabric:FcSan Represents a SAN fabric, which contains the user-configured VSANs, Fibre Channel (FC) interfaces and FC port channel interfaces. In a UCS HA configuration, there are two SAN Fabrics, A and B. Each fabric can contain a distinct set of configured VSANs, FC interfaces and port channel interfaces. The VSAN may be configured per SAN fabric (i.e. fabric A or fabric B) or per San Cloud, in which case the VSAN will be configure...
 
 		 
 		 
 		 ├
 		fabric:FcSanPc A Fibre Channel (FB) Port Channel Interface, which aggregate multiple FB ports to increase the link throughput and increase redundancy for higher availability. This is configured by the API user.
 
 		 
 		 
 		 
 		 ├
 		fc:Stats
 
 		 
 		 
 		 
 		 
 		 ├
 		fc:StatsHist
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
 		top:System Provides general information about this system, such as the name, IP address and current time.
 
 		 ├
 		equipment:Chassis A physical unit that can accomodate multiple blade servers. For example, the Cisco UCS 5108 Blade Server Chassis is six rack units (6RU) high, can mount in an industry-standard 19-inch rack and uses front-to-back cooling.
 
 		 
 		 ├
 		equipment:IOCard Represents an inventoried IO Card on a device, such as an IO module on a UCS chassis or FEX. This object is created implicitly when an IO Card is detected during hardware discovery.
 
 		 
 		 
 		 ├
 		port:Group A collection of physical ports on a device. A port group is created implicitly during device discovery of IO devices such as IO cards on a Fabric Interconnect, or IO modules on a UCS chassis. All the ports in a portGroup have the same type (i.e. FC, Ethernet).
 
 		 
 		 
 		 
 		 ├
 		fc:PIo An inventoried Physical Fibre Channel port on a physical device, such as a Fabric Interconnect or FEX.
 
 		 
 		 
 		 
 		 
 		 ├
 		fc:Stats
 
 		 
 		 
 		 
 		 
 		 
 		 ├
 		fc:StatsHist
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
 		top:System Provides general information about this system, such as the name, IP address and current time.
 
 		 ├
 		equipment:Chassis A physical unit that can accomodate multiple blade servers. For example, the Cisco UCS 5108 Blade Server Chassis is six rack units (6RU) high, can mount in an industry-standard 19-inch rack and uses front-to-back cooling.
 
 		 
 		 ├
 		equipment:IOCard Represents an inventoried IO Card on a device, such as an IO module on a UCS chassis or FEX. This object is created implicitly when an IO Card is detected during hardware discovery.
 
 		 
 		 
 		 ├
 		port:Group A collection of physical ports on a device. A port group is created implicitly during device discovery of IO devices such as IO cards on a Fabric Interconnect, or IO modules on a UCS chassis. All the ports in a portGroup have the same type (i.e. FC, Ethernet).
 
 		 
 		 
 		 
 		 ├
 		port:SubGroup A SubGroup contains ports which are made availabe by connecting a break-out cable to an aggregated port. Example in UCS-Mini a 40GB Scalability port is connected to a 4x10GB breakout cable to get 4 10GB ports.
 
 		 
 		 
 		 
 		 
 		 ├
 		fc:PIo An inventoried Physical Fibre Channel port on a physical device, such as a Fabric Interconnect or FEX.
 
 		 
 		 
 		 
 		 
 		 
 		 ├
 		fc:Stats
 
 		 
 		 
 		 
 		 
 		 
 		 
 		 ├
 		fc:StatsHist
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
 		top:System Provides general information about this system, such as the name, IP address and current time.
 
 		 ├
 		equipment:Chassis A physical unit that can accomodate multiple blade servers. For example, the Cisco UCS 5108 Blade Server Chassis is six rack units (6RU) high, can mount in an industry-standard 19-inch rack and uses front-to-back cooling.
 
 		 
 		 ├
 		equipment:SharedIOModule Represents an inventoried Shared IO Module on a device
 
 		 
 		 
 		 ├
 		port:Group A collection of physical ports on a device. A port group is created implicitly during device discovery of IO devices such as IO cards on a Fabric Interconnect, or IO modules on a UCS chassis. All the ports in a portGroup have the same type (i.e. FC, Ethernet).
 
 		 
 		 
 		 
 		 ├
 		fc:PIo An inventoried Physical Fibre Channel port on a physical device, such as a Fabric Interconnect or FEX.
 
 		 
 		 
 		 
 		 
 		 ├
 		fc:Stats
 
 		 
 		 
 		 
 		 
 		 
 		 ├
 		fc:StatsHist
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
 		top:System Provides general information about this system, such as the name, IP address and current time.
 
 		 ├
 		equipment:Chassis A physical unit that can accomodate multiple blade servers. For example, the Cisco UCS 5108 Blade Server Chassis is six rack units (6RU) high, can mount in an industry-standard 19-inch rack and uses front-to-back cooling.
 
 		 
 		 ├
 		equipment:SharedIOModule Represents an inventoried Shared IO Module on a device
 
 		 
 		 
 		 ├
 		port:Group A collection of physical ports on a device. A port group is created implicitly during device discovery of IO devices such as IO cards on a Fabric Interconnect, or IO modules on a UCS chassis. All the ports in a portGroup have the same type (i.e. FC, Ethernet).
 
 		 
 		 
 		 
 		 ├
 		port:SubGroup A SubGroup contains ports which are made availabe by connecting a break-out cable to an aggregated port. Example in UCS-Mini a 40GB Scalability port is connected to a 4x10GB breakout cable to get 4 10GB ports.
 
 		 
 		 
 		 
 		 
 		 ├
 		fc:PIo An inventoried Physical Fibre Channel port on a physical device, such as a Fabric Interconnect or FEX.
 
 		 
 		 
 		 
 		 
 		 
 		 ├
 		fc:Stats
 
 		 
 		 
 		 
 		 
 		 
 		 
 		 ├
 		fc:StatsHist
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
 		top:System Provides general information about this system, such as the name, IP address and current time.
 
 		 ├
 		equipment:Chassis A physical unit that can accomodate multiple blade servers. For example, the Cisco UCS 5108 Blade Server Chassis is six rack units (6RU) high, can mount in an industry-standard 19-inch rack and uses front-to-back cooling.
 
 		 
 		 ├
 		equipment:SwitchIOCard Represents an inventoried FI-IOM Card on a UCS-Mini Chassis This object is created implicitly when an FI-IOM Card is detected during hardware discovery. TODO: This is model similar to IOCard currently however this does not behave like a IOCard (IOM) and some of the properties will be removed if not needed.
 
 		 
 		 
 		 ├
 		port:Group A collection of physical ports on a device. A port group is created implicitly during device discovery of IO devices such as IO cards on a Fabric Interconnect, or IO modules on a UCS chassis. All the ports in a portGroup have the same type (i.e. FC, Ethernet).
 
 		 
 		 
 		 
 		 ├
 		fc:PIo An inventoried Physical Fibre Channel port on a physical device, such as a Fabric Interconnect or FEX.
 
 		 
 		 
 		 
 		 
 		 ├
 		fc:Stats
 
 		 
 		 
 		 
 		 
 		 
 		 ├
 		fc:StatsHist
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
 		top:System Provides general information about this system, such as the name, IP address and current time.
 
 		 ├
 		equipment:Chassis A physical unit that can accomodate multiple blade servers. For example, the Cisco UCS 5108 Blade Server Chassis is six rack units (6RU) high, can mount in an industry-standard 19-inch rack and uses front-to-back cooling.
 
 		 
 		 ├
 		equipment:SwitchIOCard Represents an inventoried FI-IOM Card on a UCS-Mini Chassis This object is created implicitly when an FI-IOM Card is detected during hardware discovery. TODO: This is model similar to IOCard currently however this does not behave like a IOCard (IOM) and some of the properties will be removed if not needed.
 
 		 
 		 
 		 ├
 		port:Group A collection of physical ports on a device. A port group is created implicitly during device discovery of IO devices such as IO cards on a Fabric Interconnect, or IO modules on a UCS chassis. All the ports in a portGroup have the same type (i.e. FC, Ethernet).
 
 		 
 		 
 		 
 		 ├
 		port:SubGroup A SubGroup contains ports which are made availabe by connecting a break-out cable to an aggregated port. Example in UCS-Mini a 40GB Scalability port is connected to a 4x10GB breakout cable to get 4 10GB ports.
 
 		 
 		 
 		 
 		 
 		 ├
 		fc:PIo An inventoried Physical Fibre Channel port on a physical device, such as a Fabric Interconnect or FEX.
 
 		 
 		 
 		 
 		 
 		 
 		 ├
 		fc:Stats
 
 		 
 		 
 		 
 		 
 		 
 		 
 		 ├
 		fc:StatsHist
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
 		top:System Provides general information about this system, such as the name, IP address and current time.
 
 		 ├
 		equipment:Chassis A physical unit that can accomodate multiple blade servers. For example, the Cisco UCS 5108 Blade Server Chassis is six rack units (6RU) high, can mount in an industry-standard 19-inch rack and uses front-to-back cooling.
 
 		 
 		 ├
 		equipment:SystemIOController Represents a SIOC on a Colusa 2 chassis
 
 		 
 		 
 		 ├
 		equipment:SharedIOModule Represents an inventoried Shared IO Module on a device
 
 		 
 		 
 		 
 		 ├
 		port:Group A collection of physical ports on a device. A port group is created implicitly during device discovery of IO devices such as IO cards on a Fabric Interconnect, or IO modules on a UCS chassis. All the ports in a portGroup have the same type (i.e. FC, Ethernet).
 
 		 
 		 
 		 
 		 
 		 ├
 		fc:PIo An inventoried Physical Fibre Channel port on a physical device, such as a Fabric Interconnect or FEX.
 
 		 
 		 
 		 
 		 
 		 
 		 ├
 		fc:Stats
 
 		 
 		 
 		 
 		 
 		 
 		 
 		 ├
 		fc:StatsHist
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
 		top:System Provides general information about this system, such as the name, IP address and current time.
 
 		 ├
 		equipment:Chassis A physical unit that can accomodate multiple blade servers. For example, the Cisco UCS 5108 Blade Server Chassis is six rack units (6RU) high, can mount in an industry-standard 19-inch rack and uses front-to-back cooling.
 
 		 
 		 ├
 		equipment:SystemIOController Represents a SIOC on a Colusa 2 chassis
 
 		 
 		 
 		 ├
 		equipment:SharedIOModule Represents an inventoried Shared IO Module on a device
 
 		 
 		 
 		 
 		 ├
 		port:Group A collection of physical ports on a device. A port group is created implicitly during device discovery of IO devices such as IO cards on a Fabric Interconnect, or IO modules on a UCS chassis. All the ports in a portGroup have the same type (i.e. FC, Ethernet).
 
 		 
 		 
 		 
 		 
 		 ├
 		port:SubGroup A SubGroup contains ports which are made availabe by connecting a break-out cable to an aggregated port. Example in UCS-Mini a 40GB Scalability port is connected to a 4x10GB breakout cable to get 4 10GB ports.
 
 		 
 		 
 		 
 		 
 		 
 		 ├
 		fc:PIo An inventoried Physical Fibre Channel port on a physical device, such as a Fabric Interconnect or FEX.
 
 		 
 		 
 		 
 		 
 		 
 		 
 		 ├
 		fc:Stats
 
 		 
 		 
 		 
 		 
 		 
 		 
 		 
 		 ├
 		fc:StatsHist
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
 		top:System Provides general information about this system, such as the name, IP address and current time.
 
 		 ├
 		equipment:Fex
 
 		 
 		 ├
 		equipment:IOCard Represents an inventoried IO Card on a device, such as an IO module on a UCS chassis or FEX. This object is created implicitly when an IO Card is detected during hardware discovery.
 
 		 
 		 
 		 ├
 		port:Group A collection of physical ports on a device. A port group is created implicitly during device discovery of IO devices such as IO cards on a Fabric Interconnect, or IO modules on a UCS chassis. All the ports in a portGroup have the same type (i.e. FC, Ethernet).
 
 		 
 		 
 		 
 		 ├
 		fc:PIo An inventoried Physical Fibre Channel port on a physical device, such as a Fabric Interconnect or FEX.
 
 		 
 		 
 		 
 		 
 		 ├
 		fc:Stats
 
 		 
 		 
 		 
 		 
 		 
 		 ├
 		fc:StatsHist
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
 		top:System Provides general information about this system, such as the name, IP address and current time.
 
 		 ├
 		equipment:Fex
 
 		 
 		 ├
 		equipment:IOCard Represents an inventoried IO Card on a device, such as an IO module on a UCS chassis or FEX. This object is created implicitly when an IO Card is detected during hardware discovery.
 
 		 
 		 
 		 ├
 		port:Group A collection of physical ports on a device. A port group is created implicitly during device discovery of IO devices such as IO cards on a Fabric Interconnect, or IO modules on a UCS chassis. All the ports in a portGroup have the same type (i.e. FC, Ethernet).
 
 		 
 		 
 		 
 		 ├
 		port:SubGroup A SubGroup contains ports which are made availabe by connecting a break-out cable to an aggregated port. Example in UCS-Mini a 40GB Scalability port is connected to a 4x10GB breakout cable to get 4 10GB ports.
 
 		 
 		 
 		 
 		 
 		 ├
 		fc:PIo An inventoried Physical Fibre Channel port on a physical device, such as a Fabric Interconnect or FEX.
 
 		 
 		 
 		 
 		 
 		 
 		 ├
 		fc:Stats
 
 		 
 		 
 		 
 		 
 		 
 		 
 		 ├
 		fc:StatsHist
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
 		top:System Provides general information about this system, such as the name, IP address and current time.
 
 		 ├
 		network:Element Represents a physical network element, such as a Fabric Interconnect.
 
 		 
 		 ├
 		equipment:SwitchCard Represents a physical switch card, such as a fixed module on a Fabric Interconnect or an extension module. This object is automatically created through hardware discovery.
 
 		 
 		 
 		 ├
 		port:Group A collection of physical ports on a device. A port group is created implicitly during device discovery of IO devices such as IO cards on a Fabric Interconnect, or IO modules on a UCS chassis. All the ports in a portGroup have the same type (i.e. FC, Ethernet).
 
 		 
 		 
 		 
 		 ├
 		fc:PIo An inventoried Physical Fibre Channel port on a physical device, such as a Fabric Interconnect or FEX.
 
 		 
 		 
 		 
 		 
 		 ├
 		fc:Stats
 
 		 
 		 
 		 
 		 
 		 
 		 ├
 		fc:StatsHist
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
 		top:System Provides general information about this system, such as the name, IP address and current time.
 
 		 ├
 		network:Element Represents a physical network element, such as a Fabric Interconnect.
 
 		 
 		 ├
 		equipment:SwitchCard Represents a physical switch card, such as a fixed module on a Fabric Interconnect or an extension module. This object is automatically created through hardware discovery.
 
 		 
 		 
 		 ├
 		port:Group A collection of physical ports on a device. A port group is created implicitly during device discovery of IO devices such as IO cards on a Fabric Interconnect, or IO modules on a UCS chassis. All the ports in a portGroup have the same type (i.e. FC, Ethernet).
 
 		 
 		 
 		 
 		 ├
 		port:SubGroup A SubGroup contains ports which are made availabe by connecting a break-out cable to an aggregated port. Example in UCS-Mini a 40GB Scalability port is connected to a 4x10GB breakout cable to get 4 10GB ports.
 
 		 
 		 
 		 
 		 
 		 ├
 		fc:PIo An inventoried Physical Fibre Channel port on a physical device, such as a Fabric Interconnect or FEX.
 
 		 
 		 
 		 
 		 
 		 
 		 ├
 		fc:Stats
 
 		 
 		 
 		 
 		 
 		 
 		 
 		 ├
 		fc:StatsHist


Contained Hierarchy
fc:StatsHist
Inheritance
stats:Item
 ├
 		stats:Hist
 
 		 ├
 		fc:StatsHist
Events


Faults


Fsms


Properties Summary
Defined in: fc:StatsHist
stats:Counter64
          scalar:Uint64 		bytesRx  (fc:StatsHist:bytesRx)
           NO COMMENTS
stats:Counter64
          scalar:Uint64 		bytesRxDelta  (fc:StatsHist:bytesRxDelta)
           NO COMMENTS
stats:Counter64
          scalar:Uint64 		bytesRxDeltaAvg  (fc:StatsHist:bytesRxDeltaAvg)
           NO COMMENTS
stats:Counter64
          scalar:Uint64 		bytesRxDeltaMax  (fc:StatsHist:bytesRxDeltaMax)
           NO COMMENTS
stats:Counter64
          scalar:Uint64 		bytesRxDeltaMin  (fc:StatsHist:bytesRxDeltaMin)
           NO COMMENTS
stats:Counter64
          scalar:Uint64 		bytesTx  (fc:StatsHist:bytesTx)
           NO COMMENTS
stats:Counter64
          scalar:Uint64 		bytesTxDelta  (fc:StatsHist:bytesTxDelta)
           NO COMMENTS
stats:Counter64
          scalar:Uint64 		bytesTxDeltaAvg  (fc:StatsHist:bytesTxDeltaAvg)
           NO COMMENTS
stats:Counter64
          scalar:Uint64 		bytesTxDeltaMax  (fc:StatsHist:bytesTxDeltaMax)
           NO COMMENTS
stats:Counter64
          scalar:Uint64 		bytesTxDeltaMin  (fc:StatsHist:bytesTxDeltaMin)
           NO COMMENTS
naming:Id
          scalar:Uint64 		id  (fc:StatsHist:id)
           Overrides:stats:Hist:id
           NO COMMENTS
stats:Counter64
          scalar:Uint64 		packetsRx  (fc:StatsHist:packetsRx)
           NO COMMENTS
stats:Counter64
          scalar:Uint64 		packetsRxDelta  (fc:StatsHist:packetsRxDelta)
           NO COMMENTS
stats:Counter64
          scalar:Uint64 		packetsRxDeltaAvg  (fc:StatsHist:packetsRxDeltaAvg)
           NO COMMENTS
stats:Counter64
          scalar:Uint64 		packetsRxDeltaMax  (fc:StatsHist:packetsRxDeltaMax)
           NO COMMENTS
stats:Counter64
          scalar:Uint64 		packetsRxDeltaMin  (fc:StatsHist:packetsRxDeltaMin)
           NO COMMENTS
stats:Counter64
          scalar:Uint64 		packetsTx  (fc:StatsHist:packetsTx)
           NO COMMENTS
stats:Counter64
          scalar:Uint64 		packetsTxDelta  (fc:StatsHist:packetsTxDelta)
           NO COMMENTS
stats:Counter64
          scalar:Uint64 		packetsTxDeltaAvg  (fc:StatsHist:packetsTxDeltaAvg)
           NO COMMENTS
stats:Counter64
          scalar:Uint64 		packetsTxDeltaMax  (fc:StatsHist:packetsTxDeltaMax)
           NO COMMENTS
stats:Counter64
          scalar:Uint64 		packetsTxDeltaMin  (fc:StatsHist:packetsTxDeltaMin)
           NO COMMENTS
scalar:Bitmask64 thresholded  (fc:StatsHist:thresholded)
           Overrides:stats:Item:thresholded
           NO COMMENTS
Defined in: stats:Hist
scalar:Bool mostRecent  (stats:Hist:mostRecent)
           override name="type">
Defined in: stats:Item
scalar:Bool suspect  (stats:Item:suspect)
           NO COMMENTS
scalar:Date timeCollected  (stats:Item:timeCollected)
           property name="type" type="Type" owner="management" mod="implicit" /
Defined in: mo:TopProps
mo:ModificationChildAction
          scalar:Bitmask32 		childAction  (mo:TopProps:childAction)
          
reference:Object dn  (mo:TopProps:dn)
           The Distinguished Name (dn) unambiguously identifies an object in the system.
The dn provides a fully qualified path from the top of the object tree, all the way to the object. It is built as a sequence of relative names separated by the "/" character.
For example:
< ... dn = "sys/chassis-5/blade-2/adaptor-1" />
reference:RN rn  (mo:TopProps:rn)
           The Relative Name (rn) uniquely identifies an object within a given context.
Note that a dn is comprised of a sequence of relative names. For example, the context "sys/chassis-1/blade-1/adaptor-1/host-eth-2" can be thought of as the following expression:
dn = <root object>/{rn}/{rn}/{rn}/{rn}/{rn}.
The rn can then be used to identify the object (for instance, "adaptor-1") within the context:
<... rn ="../" />
mo:InstSaclType
          scalar:Bitmask8 		sacl  (mo:TopProps:sacl)
           The system acl property for each Managed Object. br/> This property is a 8 bit mask and supports the following values :-
a: del
b: mod
c: addchild
d: cascade

By default all Managed Objects have the following permissions
a: del
b: mod
c: addchild
This property is persisted in the db. If this property has a value none
it means, the user has read only permissions on this object.
mo:ModificationStatus
          scalar:Bitmask32 		status  (mo:TopProps:status)
           This property controls the life cycle of a managed object
Properties Detail

bytesRx

Type: stats:Counter64
Primitive Type: scalar:Uint64
Units: bytes
Encrypted: false
Access: implicit
Category: StatsHistory
Property Validators:

Comments:
NO COMMENTS

bytesRxDelta

Type: stats:Counter64
Primitive Type: scalar:Uint64
Units: bytes
Encrypted: false
Access: implicit
Category: TopLevelRegular
Property Validators:

Comments:
NO COMMENTS

bytesRxDeltaAvg

Type: stats:Counter64
Primitive Type: scalar:Uint64
Units: bytes
Encrypted: false
Access: oper
Category: TopLevelRegular
Property Validators:

Comments:
NO COMMENTS

bytesRxDeltaMax

Type: stats:Counter64
Primitive Type: scalar:Uint64
Units: bytes
Encrypted: false
Access: oper
Category: TopLevelRegular
Property Validators:

Comments:
NO COMMENTS

bytesRxDeltaMin

Type: stats:Counter64
Primitive Type: scalar:Uint64
Units: bytes
Encrypted: false
Access: oper
Category: TopLevelRegular
Property Validators:

Comments:
NO COMMENTS

bytesTx

Type: stats:Counter64
Primitive Type: scalar:Uint64
Units: bytes
Encrypted: false
Access: implicit
Category: StatsHistory
Property Validators:

Comments:
NO COMMENTS

bytesTxDelta

Type: stats:Counter64
Primitive Type: scalar:Uint64
Units: bytes
Encrypted: false
Access: implicit
Category: TopLevelRegular
Property Validators:

Comments:
NO COMMENTS

bytesTxDeltaAvg

Type: stats:Counter64
Primitive Type: scalar:Uint64
Units: bytes
Encrypted: false
Access: oper
Category: TopLevelRegular
Property Validators:

Comments:
NO COMMENTS

bytesTxDeltaMax

Type: stats:Counter64
Primitive Type: scalar:Uint64
Units: bytes
Encrypted: false
Access: oper
Category: TopLevelRegular
Property Validators:

Comments:
NO COMMENTS

bytesTxDeltaMin

Type: stats:Counter64
Primitive Type: scalar:Uint64
Units: bytes
Encrypted: false
Access: oper
Category: TopLevelRegular
Property Validators:

Comments:
NO COMMENTS

childAction

Type: mo:ModificationChildAction
Primitive Type: scalar:Bitmask32
Units: null
Encrypted: false
Access: implicit
Category: TopLevelChildAction
Property Validators:

Comments:
Constants
deleteAll 16384u NO COMMENTS
ignore 4096u NO COMMENTS
deleteNonPresent 8192u NO COMMENTS
DEFAULT 0 This type is used to

dn

Type: reference:Object
Units: null
Encrypted: false
Access: implicit
Category: TopLevelDn
Property Validators:

Comments:
The Distinguished Name (dn) unambiguously identifies an object in the system.
The dn provides a fully qualified path from the top of the object tree, all the way to the object. It is built as a sequence of relative names separated by the "/" character.
For example:
< ... dn = "sys/chassis-5/blade-2/adaptor-1" />

id

Type: naming:Id
Primitive Type: scalar:Uint64
Overrides:stats:Hist:id
Units: null
Encrypted: false
Naming Property -- [NAMING RULES]
Access: naming
Category: TopLevelRegular
Property Validators:

Comments:
NO COMMENTS

mostRecent

Type: scalar:Bool
Units: null
Encrypted: false
Access: implicit
Category: TopLevelRegular
Property Validators:

Comments:
override name="type">
Constants
yes true NO COMMENTS
no false NO COMMENTS

packetsRx

Type: stats:Counter64
Primitive Type: scalar:Uint64
Units: packets
Encrypted: false
Access: implicit
Category: StatsHistory
Property Validators:

Comments:
NO COMMENTS

packetsRxDelta

Type: stats:Counter64
Primitive Type: scalar:Uint64
Units: packets
Encrypted: false
Access: implicit
Category: TopLevelRegular
Property Validators:

Comments:
NO COMMENTS

packetsRxDeltaAvg

Type: stats:Counter64
Primitive Type: scalar:Uint64
Units: packets
Encrypted: false
Access: oper
Category: TopLevelRegular
Property Validators:

Comments:
NO COMMENTS

packetsRxDeltaMax

Type: stats:Counter64
Primitive Type: scalar:Uint64
Units: packets
Encrypted: false
Access: oper
Category: TopLevelRegular
Property Validators:

Comments:
NO COMMENTS

packetsRxDeltaMin

Type: stats:Counter64
Primitive Type: scalar:Uint64
Units: packets
Encrypted: false
Access: oper
Category: TopLevelRegular
Property Validators:

Comments:
NO COMMENTS

packetsTx

Type: stats:Counter64
Primitive Type: scalar:Uint64
Units: packets
Encrypted: false
Access: implicit
Category: StatsHistory
Property Validators:

Comments:
NO COMMENTS

packetsTxDelta

Type: stats:Counter64
Primitive Type: scalar:Uint64
Units: packets
Encrypted: false
Access: implicit
Category: TopLevelRegular
Property Validators:

Comments:
NO COMMENTS

packetsTxDeltaAvg

Type: stats:Counter64
Primitive Type: scalar:Uint64
Units: packets
Encrypted: false
Access: oper
Category: TopLevelRegular
Property Validators:

Comments:
NO COMMENTS

packetsTxDeltaMax

Type: stats:Counter64
Primitive Type: scalar:Uint64
Units: packets
Encrypted: false
Access: oper
Category: TopLevelRegular
Property Validators:

Comments:
NO COMMENTS

packetsTxDeltaMin

Type: stats:Counter64
Primitive Type: scalar:Uint64
Units: packets
Encrypted: false
Access: oper
Category: TopLevelRegular
Property Validators:

Comments:
NO COMMENTS

rn

Type: reference:RN
Units: null
Encrypted: false
Access: implicit
Category: TopLevelRn
Property Validators:

Comments:
The Relative Name (rn) uniquely identifies an object within a given context.
Note that a dn is comprised of a sequence of relative names. For example, the context "sys/chassis-1/blade-1/adaptor-1/host-eth-2" can be thought of as the following expression:
dn = <root object>/{rn}/{rn}/{rn}/{rn}/{rn}.
The rn can then be used to identify the object (for instance, "adaptor-1") within the context:
<... rn ="../" />

sacl

Type: mo:InstSaclType
Primitive Type: scalar:Bitmask8
Units: null
Encrypted: false
Access: implicit
Category: TopLevelSacl
Property Validators:

Comments:
The system acl property for each Managed Object. br/> This property is a 8 bit mask and supports the following values :-
a: del
b: mod
c: addchild
d: cascade

By default all Managed Objects have the following permissions
a: del
b: mod
c: addchild
This property is persisted in the db. If this property has a value none
it means, the user has read only permissions on this object.
Constants
none 0 NO COMMENTS
del 1 NO COMMENTS
mod 2 NO COMMENTS
addchild 4 NO COMMENTS
cascade 8 NO COMMENTS
DEFAULT 0 NO COMMENTS

status

Type: mo:ModificationStatus
Primitive Type: scalar:Bitmask32
Units: null
Encrypted: false
Access: implicit
Category: TopLevelStatus
Property Validators:

Comments:
This property controls the life cycle of a managed object
Constants
removed 16u In a setter method: specifies that an object should be removed.
In the return value of a setter method: indicates that an object has been removed.
created 2u 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 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 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.

suspect

Type: scalar:Bool
Units: null
Encrypted: false
Access: implicit
Category: TopLevelRegular
Property Validators:

Comments:
NO COMMENTS
Constants
yes true NO COMMENTS
no false NO COMMENTS

thresholded

Type: scalar:Bitmask64
Overrides:stats:Item:thresholded
Units: null
Encrypted: false
Access: implicit
Category: TopLevelRegular
Property Validators:

Comments:
NO COMMENTS
Constants
packetsRxDeltaMax 1024ull NO COMMENTS
bytesTxDeltaMin 128ull NO COMMENTS
packetsTxDeltaMax 16384ull NO COMMENTS
bytesTxDelta 16ull NO COMMENTS
bytesRxDelta 1ull NO COMMENTS
packetsRxDeltaMin 2048ull NO COMMENTS
packetsRxDelta 256ull NO COMMENTS
bytesRxDeltaAvg 2ull NO COMMENTS
packetsTxDeltaMin 32768ull NO COMMENTS
bytesTxDeltaAvg 32ull NO COMMENTS
packetsTxDelta 4096ull NO COMMENTS
bytesRxDeltaMax 4ull NO COMMENTS
packetsRxDeltaAvg 512ull NO COMMENTS
bytesTxDeltaMax 64ull NO COMMENTS
packetsTxDeltaAvg 8192ull NO COMMENTS
bytesRxDeltaMin 8ull NO COMMENTS
DEFAULT 0 NO COMMENTS

timeCollected

Type: scalar:Date
Units: null
Encrypted: false
Access: implicit
Category: TopLevelRegular
Property Validators:

Comments:
property name="type" type="Type" owner="management" mod="implicit" /
Overview  Containers  Contained  Inheritance  Events  Faults  FSMs  Properties Summary  Properties Detail  Naming