The MIB is used to manage and optimize power usage
in networks.
Cisco EnergyWise is a specification of data, discovery and
protocols for managing power on and between network devices.
An entity is Cisco EnergyWise compatible, if it complies with
Cisco EnergyWise specification.
A Cisco EnergyWise entity is characterized by the power related
attributes of a physical entity present in ENTITY-MIB.
Cisco EnergyWise solves the problem of Network Power
Management. One of goals of Cisco EnergyWise is to manage
power on network level. Some solutions in FCAPS have focused
on
managing a single element but Cisco EnergyWise provides the
capability to handle the management of a network of devices, as
well as a single device.
Concepts and Definitions:
=========================
Cisco EnergyWise Entity: A physical entity that is part of the
network that provides power or draws power from another
part of the network.
Cisco EnergyWise Level: A uniform way to classify power
settings on an EnergyWise entity. Levels are guidelines for
the manufacturers of entity (e.g., shut, hibernate, sleep,
standby).
Cisco EnergyWise Usage: The consumption of power by a Cisco
EnergyWise entity in watts.
Current The current power consumption by an
Cisco EnergyWise entity.
Provisioned The maximum power a Cisco EnergyWise
entity can draw in the current level.
Usage Vector A vector 0..10 representing the maximum
power a Cisco EnergyWise entity can draw at
each level.
Delta Vector This defines a vector 0..10 representing
the difference between the Current and
Usage Vector for each level.
Cisco EnergyWise Entity Power Unit: This is used to represent
smaller or larger quantities of Cisco EnergyWise usage and
conforms to the standard prefixes for the SI (System
International) units of measure. The value represents an
exponent of 10.
For example, if current usage of an EnergyWise entity is
3, it could be 3 W, 3 mW, 3 KW, 3 MW depending on the value
of Cisco EnergyWise power unit, i.e. 0, -3, 3, or 6
respectively.
Cisco EnergyWise Domain: A collection of entities that is
divided into manageable sets. Switch, IP phones, IP cameras,
lighting controllers can be Cisco EnergyWise entities, all part
of a domain. A domain can contain multiple devices.
Cisco EnergyWise Entity Importance: The importance attribute of
an entity enables the management station to differentiate other
Cisco EnergyWise entities in the domain with a different
business context. This also provides a choice to the
administrators to manage power in context of importance.
For example, assuming we have 2 phones deployed in a
enterprise. One phone is in a shared spare office and one
used by trader generating lot of money as part of core
business of enterprise.
This clearly demonstrates that the phone used by trader is
more important than the phone used in the spare office.
Nanny Vector: A vector of bits, representing different features
(E.g., sleep, wakeup, shutdown) supported on a Cisco
EnergyWise entity. Setting of some of the features on the
Cisco EnergyWise entity can be managed by itself, but for some
others, a parent has to nanny.
Nanny: An EnergyWise entity acts on behalf of another
another Cisco EnergyWise entity.
Cisco EnergyWise Parent: A Cisco EnergyWise entity that does
not have a nanny vector. This entity can manage all its power
setting for itself as well as for Cisco EnergyWise entities
contained in it. The contained in relationship is same as
defined in ENTITY-MIB.
Cisco EnergyWise Child: A Cisco EnergyWise entity that has a
nanny vector. It requires a Cisco EnergyWise parent to serve
as nanny. Depending on the nanny vector a Cisco EnergyWise
child can be fully or partially managed.
Cisco EnergyWise Neighbor: A Cisco EnergyWise entity to which
Cisco EnergyWise protocol events can be forwarded to. An
entity can either discover a neighbor using a discovery
protocol, or the neighbor can be configured as a static
neighbor
by the Management station. A Cisco EnergyWise parent may also
nanny a Cisco EnergyWise neighbor.
For example, A Cisco EnergyWise compatible entity like an
IP phone, connected to a port on the switch, can provide a
nanny vector to the switch to serve as a nanny.
Cisco EnergyWise Proxy: A device attached to a port that does
not understand the Cisco EnergyWise protocol, but has the
provision to manage power through network APIs or a proprietary
protocol.
A Proxy is always configured on a port. It allows the
Cisco EnergyWise protocol to be used with other non networking
devices that draw power indirectly.
For example, a Lutron controller (building lighting
controller) is a nonnetworking device which does not
understand Cisco EnergyWise protocol. However, it runs a
proprietary BACNET protocol.
The following diagram represents the relationship between
cewEntTable and cewNeighborTable,
cewEntTable and cewProxyTable.
Points to a
| EntPhyIdx | NbrId | which it does | NbrId | Name |
| 101 | 1 |
| 102 | 0 | | 2 | Switch1 |
| 103 | 3 |
| 104 | 0 |
| 105 | 0 |
| |
Points to proxy | |
entry configured | | | EntPhyIdx | PrxyId | Name |
on this port. | |
| |
|
| | | | |
|
| | | |
Cisco EnergyWise Event: It is a policy that can be either
configured on a Cisco EnergyWise entity or received from
other Cisco EnergyWise entities. Using this, a Cisco
EnergyWise entity can adjust its power settings according
to some criteria, typically time.
For example, a Management station can configure an
EnergyWise event on a switch to control devices in branch
offices, to go to power level standby at 8pm and power
level full at 7am.
Cisco Energywise Query: It is a Cisco Energywise CLI used to
get
power information from the entire Energywise Domain. Queries
are
delivered, hop by hop, through the Domain using the established
neighbor information. Authentication is by the domain's shared
secret, and only authenticated queries can be sent to
EndPoints. EnergyWise supports various kinds of queries,
including set, collect, sum and delta.
set: changes or turns off power usage levels
collect: retrieves power usage information (in watts) from
the cloud.
sum: aggregates power information across multiple Members
and Endpoints.
delta: runs what if calculations.
Cisco EnergyWise Neighbor Id : The Cisco EnergyWise Neighbor's
unique Id is made up of two parts:-
UDI: Unique Device Indentification of the Cisco EnergyWise
Neighbor.
EntPhysicalIndex: The Entity Physical Index of the Cisco
EnergyWise Neighbor.
A combination of these two values provide a unique Id for the
Cisco EnergyWise Neighbor.
Parsed from file CISCO-ENERGYWISE-MIB.mib
Module: CISCO-ENERGYWISE-MIB
The MIB is used to manage and optimize power usage
in networks.
Cisco EnergyWise is a specification of data, discovery and
protocols for managing power on and between network devices.
An entity is Cisco EnergyWise compatible, if it complies with
Cisco EnergyWise specification.
A Cisco EnergyWise entity is characterized by the power related
attributes of a physical entity present in ENTITY-MIB.
Cisco EnergyWise solves the problem of Network Power
Management. One of goals of Cisco EnergyWise is to manage
power on network level. Some solutions in FCAPS have focused
on
managing a single element but Cisco EnergyWise provides the
capability to handle the management of a network of devices, as
well as a single device.
Concepts and Definitions:
=========================
Cisco EnergyWise Entity: A physical entity that is part of the
network that provides power or draws power from another
part of the network.
Cisco EnergyWise Level: A uniform way to classify power
settings on an EnergyWise entity. Levels are guidelines for
the manufacturers of entity (e.g., shut, hibernate, sleep,
standby).
Cisco EnergyWise Usage: The consumption of power by a Cisco
EnergyWise entity in watts.
Current The current power consumption by an
Cisco EnergyWise entity.
Provisioned The maximum power a Cisco EnergyWise
entity can draw in the current level.
Usage Vector A vector 0..10 representing the maximum
power a Cisco EnergyWise entity can draw at
each level.
Delta Vector This defines a vector 0..10 representing
the difference between the Current and
Usage Vector for each level.
Cisco EnergyWise Entity Power Unit: This is used to represent
smaller or larger quantities of Cisco EnergyWise usage and
conforms to the standard prefixes for the SI (System
International) units of measure. The value represents an
exponent of 10.
For example, if current usage of an EnergyWise entity is
3, it could be 3 W, 3 mW, 3 KW, 3 MW depending on the value
of Cisco EnergyWise power unit, i.e. 0, -3, 3, or 6
respectively.
Cisco EnergyWise Domain: A collection of entities that is
divided into manageable sets. Switch, IP phones, IP cameras,
lighting controllers can be Cisco EnergyWise entities, all part
of a domain. A domain can contain multiple devices.
Cisco EnergyWise Entity Importance: The importance attribute of
an entity enables the management station to differentiate other
Cisco EnergyWise entities in the domain with a different
business context. This also provides a choice to the
administrators to manage power in context of importance.
For example, assuming we have 2 phones deployed in a
enterprise. One phone is in a shared spare office and one
used by trader generating lot of money as part of core
business of enterprise.
This clearly demonstrates that the phone used by trader is
more important than the phone used in the spare office.
Nanny Vector: A vector of bits, representing different features
(E.g., sleep, wakeup, shutdown) supported on a Cisco
EnergyWise entity. Setting of some of the features on the
Cisco EnergyWise entity can be managed by itself, but for some
others, a parent has to nanny.
Nanny: An EnergyWise entity acts on behalf of another
another Cisco EnergyWise entity.
Cisco EnergyWise Parent: A Cisco EnergyWise entity that does
not have a nanny vector. This entity can manage all its power
setting for itself as well as for Cisco EnergyWise entities
contained in it. The contained in relationship is same as
defined in ENTITY-MIB.
Cisco EnergyWise Child: A Cisco EnergyWise entity that has a
nanny vector. It requires a Cisco EnergyWise parent to serve
as nanny. Depending on the nanny vector a Cisco EnergyWise
child can be fully or partially managed.
Cisco EnergyWise Neighbor: A Cisco EnergyWise entity to which
Cisco EnergyWise protocol events can be forwarded to. An
entity can either discover a neighbor using a discovery
protocol, or the neighbor can be configured as a static
neighbor
by the Management station. A Cisco EnergyWise parent may also
nanny a Cisco EnergyWise neighbor.
For example, A Cisco EnergyWise compatible entity like an
IP phone, connected to a port on the switch, can provide a
nanny vector to the switch to serve as a nanny.
Cisco EnergyWise Proxy: A device attached to a port that does
not understand the Cisco EnergyWise protocol, but has the
provision to manage power through network APIs or a proprietary
protocol.
A Proxy is always configured on a port. It allows the
Cisco EnergyWise protocol to be used with other non networking
devices that draw power indirectly.
For example, a Lutron controller (building lighting
controller) is a nonnetworking device which does not
understand Cisco EnergyWise protocol. However, it runs a
proprietary BACNET protocol.
The following diagram represents the relationship between
cewEntTable and cewNeighborTable,
cewEntTable and cewProxyTable.
Points to a
| EntPhyIdx | NbrId | which it does | NbrId | Name |
| 101 | 1 |
| 102 | 0 | | 2 | Switch1 |
| 103 | 3 |
| 104 | 0 |
| 105 | 0 |
| |
Points to proxy | |
entry configured | | | EntPhyIdx | PrxyId | Name |
on this port. | |
| |
|
| | | | |
|
| | | |
Cisco EnergyWise Event: It is a policy that can be either
configured on a Cisco EnergyWise entity or received from
other Cisco EnergyWise entities. Using this, a Cisco
EnergyWise entity can adjust its power settings according
to some criteria, typically time.
For example, a Management station can configure an
EnergyWise event on a switch to control devices in branch
offices, to go to power level standby at 8pm and power
level full at 7am.
Cisco Energywise Query: It is a Cisco Energywise CLI used to
get
power information from the entire Energywise Domain. Queries
are
delivered, hop by hop, through the Domain using the established
neighbor information. Authentication is by the domain's shared
secret, and only authenticated queries can be sent to
EndPoints. EnergyWise supports various kinds of queries,
including set, collect, sum and delta.
set: changes or turns off power usage levels
collect: retrieves power usage information (in watts) from
the cloud.
sum: aggregates power information across multiple Members
and Endpoints.
delta: runs what if calculations.
Cisco EnergyWise Neighbor Id : The Cisco EnergyWise Neighbor's
unique Id is made up of two parts:-
UDI: Unique Device Indentification of the Cisco EnergyWise
Neighbor.
EntPhysicalIndex: The Entity Physical Index of the Cisco
EnergyWise Neighbor.
A combination of these two values provide a unique Id for the
Cisco EnergyWise Neighbor.
Parsed from file CISCO-ENERGYWISE-MIB.my.txt
Company: None
Module: CISCO-ENERGYWISE-MIB
The MIB is used to manage and optimize power usage
in networks.
Cisco EnergyWise is a specification of data, discovery and
protocols for managing power on and between network devices.
An entity is Cisco EnergyWise compatible, if it complies with
Cisco EnergyWise specification.
A Cisco EnergyWise entity is characterized by the power related
attributes of a physical entity present in ENTITY-MIB.
Cisco EnergyWise solves the problem of Network Power
Management. One of goals of Cisco EnergyWise is to manage
power on network level. Some solutions in FCAPS have focused
on
managing a single element but Cisco EnergyWise provides the
capability to handle the management of a network of devices, as
well as a single device.
Concepts and Definitions:
=========================
Cisco EnergyWise Entity: A physical entity that is part of the
network that provides power or draws power from another
part of the network.
Cisco EnergyWise Level: A uniform way to classify power
settings on an EnergyWise entity. Levels are guidelines for
the manufacturers of entity (e.g., shut, hibernate, sleep,
standby).
Cisco EnergyWise Usage: The consumption of power by a Cisco
EnergyWise entity in watts.
Current The current power consumption by an
Cisco EnergyWise entity.
Provisioned The maximum power a Cisco EnergyWise
entity can draw in the current level.
Usage Vector A vector 0..10 representing the maximum
power a Cisco EnergyWise entity can draw at
each level.
Delta Vector This defines a vector 0..10 representing
the difference between the Current and
Usage Vector for each level.
Cisco EnergyWise Entity Power Unit: This is used to represent
smaller or larger quantities of Cisco EnergyWise usage and
conforms to the standard prefixes for the SI (System
International) units of measure. The value represents an
exponent of 10.
For example, if current usage of an EnergyWise entity is
3, it could be 3 W, 3 mW, 3 KW, 3 MW depending on the value
of Cisco EnergyWise power unit, i.e. 0, -3, 3, or 6
respectively.
Cisco EnergyWise Domain: A collection of entities that is
divided into manageable sets. Switch, IP phones, IP cameras,
lighting controllers can be Cisco EnergyWise entities, all part
of a domain. A domain can contain multiple devices.
Cisco EnergyWise Entity Importance: The importance attribute of
an entity enables the management station to differentiate other
Cisco EnergyWise entities in the domain with a different
business context. This also provides a choice to the
administrators to manage power in context of importance.
For example, assuming we have 2 phones deployed in a
enterprise. One phone is in a shared spare office and one
used by trader generating lot of money as part of core
business of enterprise.
This clearly demonstrates that the phone used by trader is
more important than the phone used in the spare office.
Nanny Vector: A vector of bits, representing different features
(E.g., sleep, wakeup, shutdown) supported on a Cisco
EnergyWise entity. Setting of some of the features on the
Cisco EnergyWise entity can be managed by itself, but for some
others, a parent has to nanny.
Nanny: An EnergyWise entity acts on behalf of another
another Cisco EnergyWise entity.
Cisco EnergyWise Parent: A Cisco EnergyWise entity that does
not have a nanny vector. This entity can manage all its power
setting for itself as well as for Cisco EnergyWise entities
contained in it. The contained in relationship is same as
defined in ENTITY-MIB.
Cisco EnergyWise Child: A Cisco EnergyWise entity that has a
nanny vector. It requires a Cisco EnergyWise parent to serve
as nanny. Depending on the nanny vector a Cisco EnergyWise
child can be fully or partially managed.
Cisco EnergyWise Neighbor: A Cisco EnergyWise entity to which
Cisco EnergyWise protocol events can be forwarded to. An
entity can either discover a neighbor using a discovery
protocol, or the neighbor can be configured as a static
neighbor
by the Management station. A Cisco EnergyWise parent may also
nanny a Cisco EnergyWise neighbor.
For example, A Cisco EnergyWise compatible entity like an
IP phone, connected to a port on the switch, can provide a
nanny vector to the switch to serve as a nanny.
Cisco EnergyWise Proxy: A device attached to a port that does
not understand the Cisco EnergyWise protocol, but has the
provision to manage power through network APIs or a proprietary
protocol.
A Proxy is always configured on a port. It allows the
Cisco EnergyWise protocol to be used with other non networking
devices that draw power indirectly.
For example, a Lutron controller (building lighting
controller) is a nonnetworking device which does not
understand Cisco EnergyWise protocol. However, it runs a
proprietary BACNET protocol.
The following diagram represents the relationship between
cewEntTable and cewNeighborTable,
cewEntTable and cewProxyTable.
Points to a
| EntPhyIdx | NbrId | which it does | NbrId | Name |
| 101 | 1 |
| 102 | 0 | | 2 | Switch1 |
| 103 | 3 |
| 104 | 0 |
| 105 | 0 |
| |
Points to proxy | |
entry configured | | | EntPhyIdx | PrxyId | Name |
on this port. | |
| |
|
| | | | |
|
| | | |
Cisco EnergyWise Event: It is a policy that can be either
configured on a Cisco EnergyWise entity or received from
other Cisco EnergyWise entities. Using this, a Cisco
EnergyWise entity can adjust its power settings according
to some criteria, typically time.
For example, a Management station can configure an
EnergyWise event on a switch to control devices in branch
offices, to go to power level standby at 8pm and power
level full at 7am.
Cisco Energywise Query: It is a Cisco Energywise CLI used to
get
power information from the entire Energywise Domain. Queries
are
delivered, hop by hop, through the Domain using the established
neighbor information. Authentication is by the domain's shared
secret, and only authenticated queries can be sent to
EndPoints. EnergyWise supports various kinds of queries,
including set, collect, sum and delta.
set: changes or turns off power usage levels
collect: retrieves power usage information (in watts) from
the cloud.
sum: aggregates power information across multiple Members
and Endpoints.
delta: runs what if calculations.
Cisco EnergyWise Neighbor Id : The Cisco EnergyWise Neighbor's
unique Id is made up of two parts:-
UDI: Unique Device Indentification of the Cisco EnergyWise
Neighbor.
EntPhysicalIndex: The Entity Physical Index of the Cisco
EnergyWise Neighbor.
A combination of these two values provide a unique Id for the
Cisco EnergyWise Neighbor.
ciscoEnergywiseMIB MODULE-IDENTITY LAST-UPDATED "201007090000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO "Cisco Systems Customer Service Postal: 170 W Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: [email protected]" DESCRIPTION "The MIB is used to manage and optimize power usage in networks. Cisco EnergyWise is a specification of data, discovery and protocols for managing power on and between network devices. An entity is Cisco EnergyWise compatible, if it complies with Cisco EnergyWise specification. A Cisco EnergyWise entity is characterized by the power related attributes of a physical entity present in ENTITY-MIB. Cisco EnergyWise solves the problem of Network Power Management. One of goals of Cisco EnergyWise is to manage power on network level. Some solutions in FCAPS have focused on managing a single element but Cisco EnergyWise provides the capability to handle the management of a network of devices, as well as a single device. Concepts and Definitions: ========================= Cisco EnergyWise Entity: A physical entity that is part of the network that provides power or draws power from another part of the network. Cisco EnergyWise Level: A uniform way to classify power settings on an EnergyWise entity. Levels are guidelines for the manufacturers of entity (e.g., shut, hibernate, sleep, standby). Cisco EnergyWise Usage: The consumption of power by a Cisco EnergyWise entity in watts. Current The current power consumption by an Cisco EnergyWise entity. Provisioned The maximum power a Cisco EnergyWise entity can draw in the current level. Usage Vector A vector 0..10 representing the maximum power a Cisco EnergyWise entity can draw at each level. Delta Vector This defines a vector 0..10 representing the difference between the Current and Usage Vector for each level. Cisco EnergyWise Entity Power Unit: This is used to represent smaller or larger quantities of Cisco EnergyWise usage and conforms to the standard prefixes for the SI (System International) units of measure. The value represents an exponent of 10. For example, if current usage of an EnergyWise entity is 3, it could be 3 W, 3 mW, 3 KW, 3 MW depending on the value of Cisco EnergyWise power unit, i.e. 0, -3, 3, or 6 respectively. Cisco EnergyWise Domain: A collection of entities that is divided into manageable sets. Switch, IP phones, IP cameras, lighting controllers can be Cisco EnergyWise entities, all part of a domain. A domain can contain multiple devices. Cisco EnergyWise Entity Importance: The importance attribute of an entity enables the management station to differentiate other Cisco EnergyWise entities in the domain with a different business context. This also provides a choice to the administrators to manage power in context of importance. For example, assuming we have 2 phones deployed in a enterprise. One phone is in a shared spare office and one used by trader generating lot of money as part of core business of enterprise. This clearly demonstrates that the phone used by trader is more important than the phone used in the spare office. Nanny Vector: A vector of bits, representing different features (E.g., sleep, wakeup, shutdown) supported on a Cisco EnergyWise entity. Setting of some of the features on the Cisco EnergyWise entity can be managed by itself, but for some others, a parent has to nanny. Nanny: An EnergyWise entity acts on behalf of another another Cisco EnergyWise entity. Cisco EnergyWise Parent: A Cisco EnergyWise entity that does not have a nanny vector. This entity can manage all its power setting for itself as well as for Cisco EnergyWise entities contained in it. The contained in relationship is same as defined in ENTITY-MIB. Cisco EnergyWise Child: A Cisco EnergyWise entity that has a nanny vector. It requires a Cisco EnergyWise parent to serve as nanny. Depending on the nanny vector a Cisco EnergyWise child can be fully or partially managed. Cisco EnergyWise Neighbor: A Cisco EnergyWise entity to which Cisco EnergyWise protocol events can be forwarded to. An entity can either discover a neighbor using a discovery protocol, or the neighbor can be configured as a static neighbor by the Management station. A Cisco EnergyWise parent may also nanny a Cisco EnergyWise neighbor. For example, A Cisco EnergyWise compatible entity like an IP phone, connected to a port on the switch, can provide a nanny vector to the switch to serve as a nanny. Cisco EnergyWise Proxy: A device attached to a port that does not understand the Cisco EnergyWise protocol, but has the provision to manage power through network APIs or a proprietary protocol. A Proxy is always configured on a port. It allows the Cisco EnergyWise protocol to be used with other non networking devices that draw power indirectly. For example, a Lutron controller (building lighting controller) is a nonnetworking device which does not understand Cisco EnergyWise protocol. However, it runs a proprietary BACNET protocol. The following diagram represents the relationship between cewEntTable and cewNeighborTable, cewEntTable and cewProxyTable. Points to a | EntPhyIdx | NbrId | which it does | NbrId | Name | | 101 | 1 | | 102 | 0 | | 2 | Switch1 | | 103 | 3 | | 104 | 0 | | 105 | 0 | | | Points to proxy | | entry configured | | | EntPhyIdx | PrxyId | Name | on this port. | | | | | | | | | | | | | | | Cisco EnergyWise Event: It is a policy that can be either configured on a Cisco EnergyWise entity or received from other Cisco EnergyWise entities. Using this, a Cisco EnergyWise entity can adjust its power settings according to some criteria, typically time. For example, a Management station can configure an EnergyWise event on a switch to control devices in branch offices, to go to power level standby at 8pm and power level full at 7am. Cisco Energywise Query: It is a Cisco Energywise CLI used to get power information from the entire Energywise Domain. Queries are delivered, hop by hop, through the Domain using the established neighbor information. Authentication is by the domain's shared secret, and only authenticated queries can be sent to EndPoints. EnergyWise supports various kinds of queries, including set, collect, sum and delta. set: changes or turns off power usage levels collect: retrieves power usage information (in watts) from the cloud. sum: aggregates power information across multiple Members and Endpoints. delta: runs what if calculations. Cisco EnergyWise Neighbor Id : The Cisco EnergyWise Neighbor's unique Id is made up of two parts:- UDI: Unique Device Indentification of the Cisco EnergyWise Neighbor. EntPhysicalIndex: The Entity Physical Index of the Cisco EnergyWise Neighbor. A combination of these two values provide a unique Id for the Cisco EnergyWise Neighbor." REVISION "201007090000Z" DESCRIPTION "Swaped the order of objects in cewEntEnergyUsageDirection and cewNeighborUsageDirection" REVISION "201003260000Z" DESCRIPTION "The following MIB objects have been added :- cewNeighborMacAddress cewNeighborParentPortIndex cewNeighborEnergywiseIdIndex Changed MAX-ACCESS for cewEntEnergyLevel to read-only to correct error were MIB did not match design and implementation." REVISION "200911220000Z" DESCRIPTION "Two new mib objects have been added :- cewEntAllowSet and cewEntActivityCheck." REVISION "200910210000Z" DESCRIPTION "The following MIB objects have been added :- cewEntEnergyUsageCategory cewEntEnergyUsageDirection cewNeighborKeyword cewNeighborConfiguredKeyword cewNeighborName cewNeighborConfiguredName cewNeighborRoleDescription cewNeighborConfiguredRoleDescription cewNeighborEnergyLevel cewNeighborConfiguredLevel cewNeighborImportance cewNeighborConfiguredImportance cewNeighborEnergyUnits cewNeighborEnergyUsage cewNeighborEnergyUsageCategory cewNeighborEnergyUsageDirection cewNeighborLevelTable :- cewNeighborLevelEntry cewNeighborLevelIndex cewNeighborLevelMaxUsage cewNeighborLevelDeltaUsage cewNeighborLevelUnits" REVISION "200905200000Z" DESCRIPTION "Following object was added to the MIB. cewDeviceType Following modifications were made cewNeighborDeviceType was added cewNeighborTable" REVISION "200905080000Z" DESCRIPTION "Following objects were added to the MIB to provide support for activation of Cisco EnergyWise on a Cisco EnergyWise entity. cewManagementSecret cewEndPointSecret cewDomainSecret cewProtocol cewAddressType cewAddress cewPort cewEnable cewVersion cewDeviceTotalUsage cewDeviceTotalUsageUnits Following modifications were made cewEntConfiguredlevel added to cewEntTable. cewEventImportance added to cewEventTable." REVISION "200901080000Z" DESCRIPTION "Initial version of this MIB module." ::= { ciscoMgmt 683 }
ciscoEnergywiseMIB OBJECT IDENTIFIER ::= { ciscoMgmt 683 }
Vendor: Cisco
Module: CISCO-ENERGYWISE-MIB
[Automatically extracted from oidview.com]
ciscoEnergywiseMIB MODULE-IDENTITY LAST-UPDATED "201007090000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO "Cisco Systems Customer Service Postal: 170 W Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: [email protected]" DESCRIPTION "The MIB is used to manage and optimize power usage in networks. Cisco EnergyWise is a specification of data, discovery and protocols for managing power on and between network devices. An entity is Cisco EnergyWise compatible, if it complies with Cisco EnergyWise specification. A Cisco EnergyWise entity is characterized by the power related attributes of a physical entity present in ENTITY-MIB. Cisco EnergyWise solves the problem of Network Power Management. One of goals of Cisco EnergyWise is to manage power on network level. Some solutions in FCAPS have focused on managing a single element but Cisco EnergyWise provides the capability to handle the management of a network of devices, as well as a single device. Concepts and Definitions: ========================= Cisco EnergyWise Entity: A physical entity that is part of the network that provides power or draws power from another part of the network. Cisco EnergyWise Level: A uniform way to classify power settings on an EnergyWise entity. Levels are guidelines for the manufacturers of entity (e.g., shut, hibernate, sleep, standby). Cisco EnergyWise Usage: The consumption of power by a Cisco EnergyWise entity in watts. Current The current power consumption by an Cisco EnergyWise entity. Provisioned The maximum power a Cisco EnergyWise entity can draw in the current level. Usage Vector A vector 0..10 representing the maximum power a Cisco EnergyWise entity can draw at each level. Delta Vector This defines a vector 0..10 representing the difference between the Current and Usage Vector for each level. Cisco EnergyWise Entity Power Unit: This is used to represent smaller or larger quantities of Cisco EnergyWise usage and conforms to the standard prefixes for the SI (System International) units of measure. The value represents an exponent of 10. For example, if current usage of an EnergyWise entity is 3, it could be 3 W, 3 mW, 3 KW, 3 MW depending on the value of Cisco EnergyWise power unit, i.e. 0, -3, 3, or 6 respectively. Cisco EnergyWise Domain: A collection of entities that is divided into manageable sets. Switch, IP phones, IP cameras, lighting controllers can be Cisco EnergyWise entities, all part of a domain. A domain can contain multiple devices. Cisco EnergyWise Entity Importance: The importance attribute of an entity enables the management station to differentiate other Cisco EnergyWise entities in the domain with a different business context. This also provides a choice to the administrators to manage power in context of importance. For example, assuming we have 2 phones deployed in a enterprise. One phone is in a shared spare office and one used by trader generating lot of money as part of core business of enterprise. This clearly demonstrates that the phone used by trader is more important than the phone used in the spare office. Nanny Vector: A vector of bits, representing different features (E.g., sleep, wakeup, shutdown) supported on a Cisco EnergyWise entity. Setting of some of the features on the Cisco EnergyWise entity can be managed by itself, but for some others, a parent has to nanny. Nanny: An EnergyWise entity acts on behalf of another another Cisco EnergyWise entity. Cisco EnergyWise Parent: A Cisco EnergyWise entity that does not have a nanny vector. This entity can manage all its power setting for itself as well as for Cisco EnergyWise entities contained in it. The contained in relationship is same as defined in ENTITY-MIB. Cisco EnergyWise Child: A Cisco EnergyWise entity that has a nanny vector. It requires a Cisco EnergyWise parent to serve as nanny. Depending on the nanny vector a Cisco EnergyWise child can be fully or partially managed. Cisco EnergyWise Neighbor: A Cisco EnergyWise entity to which Cisco EnergyWise protocol events can be forwarded to. An entity can either discover a neighbor using a discovery protocol, or the neighbor can be configured as a static neighbor by the Management station. A Cisco EnergyWise parent may also nanny a Cisco EnergyWise neighbor. For example, A Cisco EnergyWise compatible entity like an IP phone, connected to a port on the switch, can provide a nanny vector to the switch to serve as a nanny. Cisco EnergyWise Proxy: A device attached to a port that does not understand the Cisco EnergyWise protocol, but has the provision to manage power through network APIs or a proprietary protocol. A Proxy is always configured on a port. It allows the Cisco EnergyWise protocol to be used with other non networking devices that draw power indirectly. For example, a Lutron controller (building lighting controller) is a nonnetworking device which does not understand Cisco EnergyWise protocol. However, it runs a proprietary BACNET protocol. The following diagram represents the relationship between cewEntTable and cewNeighborTable, cewEntTable and cewProxyTable. Points to a | EntPhyIdx | NbrId | which it does | NbrId | Name | | 101 | 1 | | 102 | 0 | | 2 | Switch1 | | 103 | 3 | | 104 | 0 | | 105 | 0 | | | Points to proxy | | entry configured | | | EntPhyIdx | PrxyId | Name | on this port. | | | | | | | | | | | | | | | Cisco EnergyWise Event: It is a policy that can be either configured on a Cisco EnergyWise entity or received from other Cisco EnergyWise entities. Using this, a Cisco EnergyWise entity can adjust its power settings according to some criteria, typically time. For example, a Management station can configure an EnergyWise event on a switch to control devices in branch offices, to go to power level standby at 8pm and power level full at 7am. Cisco Energywise Query: It is a Cisco Energywise CLI used to get power information from the entire Energywise Domain. Queries are delivered, hop by hop, through the Domain using the established neighbor information. Authentication is by the domain's shared secret, and only authenticated queries can be sent to EndPoints. EnergyWise supports various kinds of queries, including set, collect, sum and delta. set: changes or turns off power usage levels collect: retrieves power usage information (in watts) from the cloud. sum: aggregates power information across multiple Members and Endpoints. delta: runs what if calculations. Cisco EnergyWise Neighbor Id : The Cisco EnergyWise Neighbor's unique Id is made up of two parts:- UDI: Unique Device Indentification of the Cisco EnergyWise Neighbor. EntPhysicalIndex: The Entity Physical Index of the Cisco EnergyWise Neighbor. A combination of these two values provide a unique Id for the Cisco EnergyWise Neighbor." REVISION "201007090000Z" DESCRIPTION "Swaped the order of objects in cewEntEnergyUsageDirection and cewNeighborUsageDirection" REVISION "201003260000Z" DESCRIPTION "The following MIB objects have been added :- cewNeighborMacAddress cewNeighborParentPortIndex cewNeighborEnergywiseIdIndex Changed MAX-ACCESS for cewEntEnergyLevel to read-only to correct error were MIB did not match design and implementation." REVISION "200911220000Z" DESCRIPTION "Two new mib objects have been added :- cewEntAllowSet and cewEntActivityCheck." REVISION "200910210000Z" DESCRIPTION "The following MIB objects have been added :- cewEntEnergyUsageCategory cewEntEnergyUsageDirection cewNeighborKeyword cewNeighborConfiguredKeyword cewNeighborName cewNeighborConfiguredName cewNeighborRoleDescription cewNeighborConfiguredRoleDescription cewNeighborEnergyLevel cewNeighborConfiguredLevel cewNeighborImportance cewNeighborConfiguredImportance cewNeighborEnergyUnits cewNeighborEnergyUsage cewNeighborEnergyUsageCategory cewNeighborEnergyUsageDirection cewNeighborLevelTable :- cewNeighborLevelEntry cewNeighborLevelIndex cewNeighborLevelMaxUsage cewNeighborLevelDeltaUsage cewNeighborLevelUnits" REVISION "200905200000Z" DESCRIPTION "Following object was added to the MIB. cewDeviceType Following modifications were made cewNeighborDeviceType was added cewNeighborTable" REVISION "200905080000Z" DESCRIPTION "Following objects were added to the MIB to provide support for activation of Cisco EnergyWise on a Cisco EnergyWise entity. cewManagementSecret cewEndPointSecret cewDomainSecret cewProtocol cewAddressType cewAddress cewPort cewEnable cewVersion cewDeviceTotalUsage cewDeviceTotalUsageUnits Following modifications were made cewEntConfiguredlevel added to cewEntTable. cewEventImportance added to cewEventTable." REVISION "200901080000Z" DESCRIPTION "Initial version of this MIB module." ::= { ciscoMgmt 683 }
ciscoEnergywiseMIB MODULE-IDENTITY LAST-UPDATED "201007090000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO "Cisco Systems Customer Service Postal: 170 W Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: [email protected]" DESCRIPTION "The MIB is used to manage and optimize power usage in networks. Cisco EnergyWise is a specification of data, discovery and protocols for managing power on and between network devices. An entity is Cisco EnergyWise compatible, if it complies with Cisco EnergyWise specification. A Cisco EnergyWise entity is characterized by the power related attributes of a physical entity present in ENTITY-MIB. Cisco EnergyWise solves the problem of Network Power Management. One of goals of Cisco EnergyWise is to manage power on network level. Some solutions in FCAPS have focused on managing a single element but Cisco EnergyWise provides the capability to handle the management of a network of devices, as well as a single device. Concepts and Definitions: ========================= Cisco EnergyWise Entity: A physical entity that is part of the network that provides power or draws power from another part of the network. Cisco EnergyWise Level: A uniform way to classify power settings on an EnergyWise entity. Levels are guidelines for the manufacturers of entity (e.g., shut, hibernate, sleep, standby). Cisco EnergyWise Usage: The consumption of power by a Cisco EnergyWise entity in watts. Current The current power consumption by an Cisco EnergyWise entity. Provisioned The maximum power a Cisco EnergyWise entity can draw in the current level. Usage Vector A vector 0..10 representing the maximum power a Cisco EnergyWise entity can draw at each level. Delta Vector This defines a vector 0..10 representing the difference between the Current and Usage Vector for each level. Cisco EnergyWise Entity Power Unit: This is used to represent smaller or larger quantities of Cisco EnergyWise usage and conforms to the standard prefixes for the SI (System International) units of measure. The value represents an exponent of 10. For example, if current usage of an EnergyWise entity is 3, it could be 3 W, 3 mW, 3 KW, 3 MW depending on the value of Cisco EnergyWise power unit, i.e. 0, -3, 3, or 6 respectively. Cisco EnergyWise Domain: A collection of entities that is divided into manageable sets. Switch, IP phones, IP cameras, lighting controllers can be Cisco EnergyWise entities, all part of a domain. A domain can contain multiple devices. Cisco EnergyWise Entity Importance: The importance attribute of an entity enables the management station to differentiate other Cisco EnergyWise entities in the domain with a different business context. This also provides a choice to the administrators to manage power in context of importance. For example, assuming we have 2 phones deployed in a enterprise. One phone is in a shared spare office and one used by trader generating lot of money as part of core business of enterprise. This clearly demonstrates that the phone used by trader is more important than the phone used in the spare office. Nanny Vector: A vector of bits, representing different features (E.g., sleep, wakeup, shutdown) supported on a Cisco EnergyWise entity. Setting of some of the features on the Cisco EnergyWise entity can be managed by itself, but for some others, a parent has to nanny. Nanny: An EnergyWise entity acts on behalf of another another Cisco EnergyWise entity. Cisco EnergyWise Parent: A Cisco EnergyWise entity that does not have a nanny vector. This entity can manage all its power setting for itself as well as for Cisco EnergyWise entities contained in it. The contained in relationship is same as defined in ENTITY-MIB. Cisco EnergyWise Child: A Cisco EnergyWise entity that has a nanny vector. It requires a Cisco EnergyWise parent to serve as nanny. Depending on the nanny vector a Cisco EnergyWise child can be fully or partially managed. Cisco EnergyWise Neighbor: A Cisco EnergyWise entity to which Cisco EnergyWise protocol events can be forwarded to. An entity can either discover a neighbor using a discovery protocol, or the neighbor can be configured as a static neighbor by the Management station. A Cisco EnergyWise parent may also nanny a Cisco EnergyWise neighbor. For example, A Cisco EnergyWise compatible entity like an IP phone, connected to a port on the switch, can provide a nanny vector to the switch to serve as a nanny. Cisco EnergyWise Proxy: A device attached to a port that does not understand the Cisco EnergyWise protocol, but has the provision to manage power through network APIs or a proprietary protocol. A Proxy is always configured on a port. It allows the Cisco EnergyWise protocol to be used with other non networking devices that draw power indirectly. For example, a Lutron controller (building lighting controller) is a nonnetworking device which does not understand Cisco EnergyWise protocol. However, it runs a proprietary BACNET protocol. The following diagram represents the relationship between cewEntTable and cewNeighborTable, cewEntTable and cewProxyTable. Points to a | EntPhyIdx | NbrId | which it does | NbrId | Name | | 101 | 1 | | 102 | 0 | | 2 | Switch1 | | 103 | 3 | | 104 | 0 | | 105 | 0 | | | Points to proxy | | entry configured | | | EntPhyIdx | PrxyId | Name | on this port. | | | | | | | | | | | | | | | Cisco EnergyWise Event: It is a policy that can be either configured on a Cisco EnergyWise entity or received from other Cisco EnergyWise entities. Using this, a Cisco EnergyWise entity can adjust its power settings according to some criteria, typically time. For example, a Management station can configure an EnergyWise event on a switch to control devices in branch offices, to go to power level standby at 8pm and power level full at 7am. Cisco Energywise Query: It is a Cisco Energywise CLI used to get power information from the entire Energywise Domain. Queries are delivered, hop by hop, through the Domain using the established neighbor information. Authentication is by the domain's shared secret, and only authenticated queries can be sent to EndPoints. EnergyWise supports various kinds of queries, including set, collect, sum and delta. set: changes or turns off power usage levels collect: retrieves power usage information (in watts) from the cloud. sum: aggregates power information across multiple Members and Endpoints. delta: runs what if calculations. Cisco EnergyWise Neighbor Id : The Cisco EnergyWise Neighbor's unique Id is made up of two parts:- UDI: Unique Device Indentification of the Cisco EnergyWise Neighbor. EntPhysicalIndex: The Entity Physical Index of the Cisco EnergyWise Neighbor. A combination of these two values provide a unique Id for the Cisco EnergyWise Neighbor." REVISION "201007090000Z" DESCRIPTION "Swaped the order of objects in cewEntEnergyUsageDirection and cewNeighborUsageDirection" REVISION "201003260000Z" DESCRIPTION "The following MIB objects have been added :- cewNeighborMacAddress cewNeighborParentPortIndex cewNeighborEnergywiseIdIndex Changed MAX-ACCESS for cewEntEnergyLevel to read-only to correct error were MIB did not match design and implementation." REVISION "200911220000Z" DESCRIPTION "Two new mib objects have been added :- cewEntAllowSet and cewEntActivityCheck." REVISION "200910210000Z" DESCRIPTION "The following MIB objects have been added :- cewEntEnergyUsageCategory cewEntEnergyUsageDirection cewNeighborKeyword cewNeighborConfiguredKeyword cewNeighborName cewNeighborConfiguredName cewNeighborRoleDescription cewNeighborConfiguredRoleDescription cewNeighborEnergyLevel cewNeighborConfiguredLevel cewNeighborImportance cewNeighborConfiguredImportance cewNeighborEnergyUnits cewNeighborEnergyUsage cewNeighborEnergyUsageCategory cewNeighborEnergyUsageDirection cewNeighborLevelTable :- cewNeighborLevelEntry cewNeighborLevelIndex cewNeighborLevelMaxUsage cewNeighborLevelDeltaUsage cewNeighborLevelUnits" REVISION "200905200000Z" DESCRIPTION "Following object was added to the MIB. cewDeviceType Following modifications were made cewNeighborDeviceType was added cewNeighborTable" REVISION "200905080000Z" DESCRIPTION "Following objects were added to the MIB to provide support for activation of Cisco EnergyWise on a Cisco EnergyWise entity. cewManagementSecret cewEndPointSecret cewDomainSecret cewProtocol cewAddressType cewAddress cewPort cewEnable cewVersion cewDeviceTotalUsage cewDeviceTotalUsageUnits Following modifications were made cewEntConfiguredlevel added to cewEntTable. cewEventImportance added to cewEventTable." REVISION "200901080000Z" DESCRIPTION "Initial version of this MIB module." ::= { ciscoMgmt 683 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.683.0 | ciscoEnergywiseMIBNotifs | 5 | 5 | None |
| 1.3.6.1.4.1.9.9.683.1 | ciscoEnergywiseMIBObjects | 29 | 127 | None |
| 1.3.6.1.4.1.9.9.683.2 | ciscoEnergywiseMIBConform | 2 | 27 | None |
To many brothers! Only 100 nearest brothers are shown.
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| ... | ||||
| 1.3.6.1.4.1.9.9.633 | ciscoIpSlaAutoMIB | 3 | 57 | This module defines the MIB for IP SLA Automation. IP SLA Automation consists of the following: 1. Use of grouping - Group is an … |
| 1.3.6.1.4.1.9.9.634 | ciscoServiceControlTpStatsMIB | 3 | 39 | This MIB provides information and statistics on the traffic processor(s) of a service control entity, which is a network element … |
| 1.3.6.1.4.1.9.9.635 | ciscoIpSlaJitterMIB | 3 | 57 | This MIB module defines templates for IP SLA operations of UDP Jitter and ICMP Jitter. The UDP Jitter operation is designed to me… |
| 1.3.6.1.4.1.9.9.636 | ciscoIpSlaEchoMIB | 3 | 71 | This MIB module defines the templates for IP SLA operations of ICMP echo, UDP echo and TCP connect. The ICMP echo operation measu… |
| 1.3.6.1.4.1.9.9.637 | ciscoServiceControlRdrMIB | 3 | 56 | This MIB module defines objects describing statistics and configuration relating to the Raw Data Record Formatter running on a se… |
| 1.3.6.1.4.1.9.9.638 | ciscoAgwMIB | 3 | 324 | This module manages Cisco's WiMAX ASN Gateway (ASN-GW). A WiMAX network supports wireless data communication through WiMAX radio … |
| 1.3.6.1.4.1.9.9.639 | ciscoOtnIfMIB | 3 | 137 | This MIB module defines the managed objects for physical layer characteristics of DWDM optical channel interfaces and performanc… |
| 1.3.6.1.4.1.9.9.640 | ciscoImageLicenseMgmtMIB | 3 | 31 | The MIB module for managing the running image level of a Cisco device. Cisco's licensing mechanism provides flexibility to run a … |
| 1.3.6.1.4.1.9.9.642 | ciscoBridgeDomainMIB | 3 | 24 | A bridge domain is one of the means by which it is possible to define a broadcast domain on a bridging device. It is an alternati… |
| 1.3.6.1.4.1.9.9.643 | ciscoTelepresenceMIB | 3 | 119 | The MIB module defines the managed objects for a Telepresence system. Telepresence refers to a set of technologies which allow a p… |
| 1.3.6.1.4.1.9.9.644 | ciscoTelepresenceCallMIB | 3 | 178 | The MIB module defines the managed objects for Telepresence calls. Telepresence refers to a set of technologies which allow a pers… |
| 1.3.6.1.4.1.9.9.645 | ciscoEtherExtMIB | 3 | 18 | The MIB module to describe generic objects for ethernet-like network interfaces. This MIB provides ethernet-like network interfac… |
| 1.3.6.1.4.1.9.9.646 | ciscoAonStatusMIB | 3 | 80 | This MIB module defines managed objects that facilitate the management of AON node. The information available through this MIB in… |
| 1.3.6.1.4.1.9.9.647 | ciscoGgsnExtMIB | 3 | 212 | This MIB module extends the CISCO-GGSN-MIB. This MIB module manages the Gateway GPRS Support Node (GGSN) devices. A GGSN device pr… |
| 1.3.6.1.4.1.9.9.648 | ciscoVirtualInterfaceMIB | 2 | 32 | The MIB module for creation and deletion of Virtual Interfaces and Virtual Interface Groups. In addition to this MIB, interface … |
| 1.3.6.1.4.1.9.9.650 | ciscoL4L7moduleRedundancyMIB | 3 | 71 | The L4-7 SLB devices are used for scaling websites, building web enabled applications, and migrating to web services. The followin… |
| 1.3.6.1.4.1.9.9.651 | ciscoCommonRolesExtMIB | 3 | 37 | A MIB Module for managing the roles that are common between access methods like Command Line Interface (CLI), SNMP and XML interf… |
| 1.3.6.1.4.1.9.9.652 | ciscoSwitchStatsMIB | 3 | 106 | The MIB module provides management information for configuration and monitoring of traffic statistics on Cisco's switching device… |
| 1.3.6.1.4.1.9.9.653 | ciscoAdmissionPolicyMIB | 3 | 36 | This MIB module defines managed objects that facilitate the management of policies upon host(s) admission to a network. The inform… |
| 1.3.6.1.4.1.9.9.654 | ciscoMabMIB | 3 | 20 | MIB module for monitoring and configuring MAC Authentication Bypass (MAB) feature in the system. MAC Auth Bypass feature provides… |
| 1.3.6.1.4.1.9.9.655 | ciscoDigitalMediaSystemsMIB | 3 | 195 | Acronyms and Definitions The following acronyms and terms are used in this document: DMS: Digital Media Systems DAM: Digital As… |
| 1.3.6.1.4.1.9.9.656 | ciscoAuthFrameworkMIB | 3 | 117 | MIB module for Authentication Framework in the system. Authentication Framework provides generic configurations for authenticatio… |
| 1.3.6.1.4.1.9.9.657 | ciscoSbcCallStatsMIB | 3 | 201 | The main purpose of this MIB is to define the statistics information for Session Border Controller application. The statistics ar… |
| 1.3.6.1.4.1.9.9.658 | ciscoSessBorderCtrlrEventMIB | 3 | 208 | The main purpose of this MIB is to define the SNMP notifications and alarms generated by Session Border Controller application an… |
| 1.3.6.1.4.1.9.9.660 | ciscoNportVirtualizationMIB | 3 | 19 | The MIB module for the management of N_port Virtualization or NPV within the framework of Cisco's N_port virtualization (NPV) Arc… |
| 1.3.6.1.4.1.9.9.661 | ciscoWan3gMIB | 3 | 378 | This MIB module provides network management support for Cisco cellular 3G WAN products. *** ABBREVIATIONS, ACRONYMS, AND SYMBOLS … |
| 1.3.6.1.4.1.9.9.662 | ciscoCbpTcMIB | 0 | 0 | This MIB module defines textual conventions used by the CISCO-CBP-BASE-CFG-MIB, CISCO-CBP-BASE-MON-MIB, and any MIB modules exten… |
| 1.3.6.1.4.1.9.9.663 | ciscoSwitchHardwareCapacityMIB | 3 | 141 | This MIB module defines the managed objects for hardware capacity of Cisco switching devices. The hardware capacity information c… |
| 1.3.6.1.4.1.9.9.664 | ciscoMmodalContactAppsMIB | 3 | 359 | The Cisco Unified Multi-Modal Contact Applications (MMCA) platform is a highly scalable, modular, extensible, open and secure pl… |
| 1.3.6.1.4.1.9.9.667 | ciscoServiceControllerMIB | 2 | 31 | This MIB module defines objects describing traffic controllers used by a service control entity. A service control entity is a ne… |
| 1.3.6.1.4.1.9.9.668 | ciscoP2PIfMIB | 3 | 16 | The Point to Point Interface MIB module. This MIB manages the generic objects for Serial link or SONET/SDH like point to point ne… |
| 1.3.6.1.4.1.9.9.669 | ciscoCdmaPdsnExtMIB | 3 | 178 | This MIB is an extension to the CISCO-CDMA-PDSN-MIB. A CDMA network supports wireless data communication through 3G CDMA radio acc… |
| 1.3.6.1.4.1.9.9.670 | ciscoReportIntervalTcMIB | 0 | 0 | CISCO-REPORT-INTERVAL-TC-MIB |
| 1.3.6.1.4.1.9.9.672 | ciscoMobilityTapMIB | 3 | 24 | This module manages Cisco's intercept feature for Mobility Gateway Products. This MIB is used along with CISCO-TAP2-MIB MIB to int… |
| 1.3.6.1.4.1.9.9.673 | ciscoFCoEMIB | 2 | 45 | This MIB module is for configuring and monitoring Fibre Channel over Ethernet (FCoE) related entities. This MIB defines the Virtu… |
| 1.3.6.1.4.1.9.9.679 | ciscoIeee8021CfmExtMIB | 3 | 55 | A MIB module for extending the IEEE8021-CFM-MIB and IEEE8021-CFM-V2-MIB to add objects which provide additional information about… |
| 1.3.6.1.4.1.9.9.680 | ciscoNhrpExtMIB | 3 | 36 | This MIB module is an extension of the NHRP MIB module as defined in RFC 2677. It defines notifications associated with critical … |
| 1.3.6.1.4.1.9.9.686 | ciscoLwappInterfaceMIB | 3 | 27 | ciscoLwappInterfaceMIB MODULE-IDENTITY LAST-UPDATED "200901090000Z" ORGANIZATION "Cisco Systems Inc." CONTACT-INFO "Cisco Syste… |
| 1.3.6.1.4.1.9.9.688 | ciscoFlowMonitorTcMIB | 0 | 0 | This MIB module defines textual conventions used by the MIB modules defining objects describing flow monitoring. GLOSSARY ========… |
| 1.3.6.1.4.1.9.9.689 | ciscoSlbDfpMIB | 3 | 22 | This MIB reports the congestion status of the real server. A server can be in congested state due to high memory consumption, hig… |
| 1.3.6.1.4.1.9.9.690 | ciscoMobilePolicyChargingControlMIB | 3 | 143 | Mobile PCC Infrastructure built on top of Policy Shim Layer, is a common interface to send and receive PCC related messages for a… |
| 1.3.6.1.4.1.9.9.691 | ciscoEthernetFabricExtenderMIB | 3 | 23 | The MIB module for configuring one or more fabric extenders to connect into a core switch. Since fabric extenders might not be m… |
| 1.3.6.1.4.1.9.9.692 | ciscoFlowMonitorMIB | 4 | 195 | This MIB module defines objects that describe flow monitoring. A typical application of this MIB module will facilitate monitorin… |
| 1.3.6.1.4.1.9.9.693 | ciscoServiceControlAttackMIB | 3 | 55 | This MIB provides data related to different types of attacks detected by a service control entity. A service control entity is a … |
| 1.3.6.1.4.1.9.9.694 | ciscoCtsTcMIB | 0 | 0 | This module defines the textual conventions used within Cisco Trusted Security framework. |
| 1.3.6.1.4.1.9.9.695 | ciscoGtcapMIB | 3 | 194 | The MIB for Transaction Capabilities(TCAP) messages transported over Signalling System No. 7 (SS7) Network via Cisco IP Transfer P… |
| 1.3.6.1.4.1.9.9.696 | ciscoBootHwDiagsMIB | 3 | 22 | This MIB is used to configure those devices that support boot-time hardware diagnostics. It provides the reports about the respe… |
| 1.3.6.1.4.1.9.9.697 | ciscoIpCbrMetricsMIB | 4 | 42 | This MIB module defines objects that describe the a set of metrics used to measure the quality of a IP CBR traffic flow. An IP CB… |
| 1.3.6.1.4.1.9.9.698 | ciscoObmiMIB | 3 | 60 | The On-Board Management Interface (OBMI) provides an out-of-band communications channel (in Cisco terms: a console port), that is… |
| 1.3.6.1.4.1.9.9.699 | ciscoMdiMetricsMIB | 4 | 46 | This MIB module defines objects that describe the Media Delivery Index (MDI). The MDI [RFC4445] measurement describes the qualit… |
| 1.3.6.1.4.1.9.9.700 | ciscoCableL2vpnMIB | 3 | 28 | This MIB module defines managed objects that facilitate the management of Cisco devices complying to the DOCSIS L2VPN Feature for… |
| 1.3.6.1.4.1.9.9.701 | ciscoSeuMitigationMIB | 3 | 51 | This MIB reports the status of non-automatic and automatic, rate-adaptive Single Event Upset (SEU) mitigation algorithms and adju… |
| 1.3.6.1.4.1.9.9.702 | ciscoSanBaseSvcMIB | 3 | 57 | Common MIB module to manage services in Storage Area Network (SAN). Service is deployed on service nodes on multiple switches fo… |
| 1.3.6.1.4.1.9.9.703 | ciscoRtpMetricsMIB | 4 | 61 | This MIB module defines objects that describe the quality metrics of RTP streams, similar to those described by an RTCP Receiver … |
| 1.3.6.1.4.1.9.9.706 | ciscoInterfaceXcvrMonitorMIB | 3 | 33 | A MIB module that provides monitoring information about the transceivers plugged into interface on a system. |
| 1.3.6.1.4.1.9.9.708 | ciscoContentDeliveryStreamingMIB | 2 | 30 | This MIB instrumentation is for managing the Content Delivery and Streaming functionality on Cisco devices. Contents are ingested… |
| 1.3.6.1.4.1.9.9.709 | ciscoVlanGroupMIB | 3 | 18 | MIB module for monitoring and configuring VLAN Group Mapping information. |
| 1.3.6.1.4.1.9.9.710 | ciscoVirtualNicMIB | 3 | 36 | This MIB module defines MIB objects which provide mechanisms to manage the parameters used by or related to Virtual NIC. Virtual s… |
| 1.3.6.1.4.1.9.9.711 | ciscoVrfMIB | 3 | 48 | The MIB module for provisioning and managing network virtualization features. This module provides manageability for VRF, VRF-Lit… |
| 1.3.6.1.4.1.9.9.712 | ciscoWirelessNotificationMIB | 3 | 30 | This MIB is intended to be implemented on those Network Management applications that manage a network of wireless devices through… |
| 1.3.6.1.4.1.9.9.713 | ciscoTrustSecPolicyMIB | 3 | 204 | This MIB module defines managed objects that facilitate the management of various policies within the Cisco Trusted Security (Tru… |
| 1.3.6.1.4.1.9.9.714 | ciscoHwModuleControlMIB | 3 | 27 | The MIB module providing configuration and control information for management of hardware modules and components on Cisco devices… |
| 1.3.6.1.4.1.9.9.715 | ciscoEntityQfpMIB | 3 | 82 | This MIB module defines managed objects that facilitate the management of Quantum Flow Processors (QFP), which are listed in the … |
| 1.3.6.1.4.1.9.9.716 | ciscoVoIpTapMIB | 3 | 18 | This module manages Cisco's intercept feature for Voice over IP (VoIP). This MIB is used along with CISCO-TAP2-MIB to intercept V… |
| 1.3.6.1.4.1.9.9.718 | ciscoCuicappsMIB | 3 | 130 | The Cisco Unified Intelligence Center (CUIC) is a scalable robust and secure reporting solution for contact center applications. T… |
| 1.3.6.1.4.1.9.9.719 | ciscoUnifiedComputingMIB | 5 | 13463 | This MIB module defines the managed objects for Unified Computing System (UCS) Manager. Cisco UCS Manager provides centralized m… |
| 1.3.6.1.4.1.9.9.720 | ciscoTrustSecSxpMIB | 3 | 140 | This MIB module is for the configuration and status query of SGT Exchange Protocol over TCP (SXPoTCP) feature of the device on th… |
| 1.3.6.1.4.1.9.9.721 | ciscoMldSnoopingMIB | 3 | 215 | This MIB module defines objects that describe IGMP/MLD snooping. It provides remote network management system the ability to manag… |
| 1.3.6.1.4.1.9.9.724 | cggsnGeoMIB | 2 | 12 | This MIB provide additional information for passive interface configured for each OSPF process, independent of object creation in… |
| 1.3.6.1.4.1.9.9.725 | ciscoSmartInstallMIB | 3 | 101 | This MIB module defines managed objects that facilitate the management of Smart Install feature. Smart Install is a plug-and-pla… |
| 1.3.6.1.4.1.9.9.729 | ciscoCdstvServicesMIB | 3 | 21 | This MIB module defines service monitoring objects that faciliate the management of the Cisco Content Delivery System for TV (CDS… |
| 1.3.6.1.4.1.9.9.730 | ciscoTrustSecMIB | 3 | 128 | This MIB module is for the configuration of a network device on the Cisco Trusted Security (TrustSec) system. TrustSec secures a … |
| 1.3.6.1.4.1.9.9.731 | ciscoEpcGatewayMIB | 3 | 130 | This MIB module manages the features and configuration for PDN Gateway(PGW) and Serving Gateway(SGW) in Evolved Packet Core(EPC) … |
| 1.3.6.1.4.1.9.9.732 | ciscoDeviceLocationMIB | 3 | 49 | This MIB is used for managing location information of end point devices(Telepresence, IP Camera, Digital media player etc) connec… |
| 1.3.6.1.4.1.9.9.733 | ciscoMeetingPlaceMIB | 3 | 70 | This MIB allows management of Cisco Unified MeetingPlace (CUMP) features, CUMP is the key conferencing solution component for Cis… |
| ... | ||||