X

An Oracle blog about Ops Center

What's In Your Datacenter

Guest Author

Starting
in 12.3.1, Ops Center keeps count of your assets. Despite the name, the
numbers are not a physical inventory of assets; they are the number
of access points to the assets. An access point is the connection
between the Enterprise Controller and an asset. Often, it's a 1-to-1
relationship, but it is common to have multiple connections between
an asset and the Enterprise Controller. For example, a server will
have an access point for its service processor and one for its
operating system. A logical domain will have an access point for its
control domain and one for its operating system. So what the asset
counter really shows you is how many connections the Enterprise
Controller is handling by type and how many connections each Proxy
Controller is handling by type.

If you are only
interested in a particular type of asset, use the Asset Counter tab
in the Enterprise Controller's dashboard. Go to the Administration section of the navigation pane, then click the Asset Counter tab in the center pane. Let's say you are running a
job that creates logical domains and you only need to check progress.
You could always check the Jobs pane to see to see the job complete, but to
see only each logical domain complete, refresh the Asset Counter tab
and watch the count in the Ldoms column increase.

To
investigate the access points, or if you wonder whether it's time to
rebalance your Proxy Controllers, call the OCDoctor. Two of the
OCDoctor's options now show the number of access points on the
Enterprise Controller and on each Proxy Controller: the
--troubleshoot
option and the
--collectlogs
option. A new script in OCDoctor,
AssetCount.sh,
when you run it with its
standard
parameter, gives you the same information as you see in UI's Asset
Counter tab.

#
/var/opt/sun/xvm/OCDoctor/toolbox/AssetCount.sh standard

To drill
down into the count, run the script with each of its other
parameters:

machine
,
agent,
and
all.

To see each
Proxy Controller:

    #/var/opt/sun/xvm/OCDoctor/toolbox/AssetCount.sh
machine

To see
each Proxy Controller by type of access
:

#
/var/opt/sun/xvm/OCDoctor/toolbox/AssetCount.sh agent

To put the output
together in one long listing,use the all
parameter:

   #
/var/opt/sun/xvm/OCDoctor/toolbox/AssetCount.sh all

The resulting output for a smallish datacenter, just 72 access points, looks like this: 


EC 72
Proxy Assets Zones Ldoms OVMGuests Servers Storages Switches ExadataCells MSeriesChassis MSeriesD
-------------------------------------------------------------------------------------------------
pc4 32 5 25 0 2 0 0 0 0 0
pc1 28 0 26 0 2 0 0 0 0 0
pc0 12 2 4 0 6 0 0 0 0 0
Proxy Agents Agentless SPs
--------------------------
pc4 25 2 0
pc1 1 1 0
pc0 5 5 5
Proxy 32 pc4
Zones 5 S11zone101 S11zone102 S11zone100 S11zone103 S11zone104
Ldoms 25 stdldom21 stdldom34 stdldom36 stdldom22 stdldom45 stdldom47 ...
OVMGuests 0
Servers 2 10.187.70.169 pc4
...
Proxy 28 pc1
Zones 0
Ldoms 26 stdldom21 stdldom34 stdldom36 stdldom22 stdldom45 stdldom47 ...
OVMGuests 0
Servers 2 10.187.70.171 pc1


By the way, if
you're wondering at what point the number of assets affects
performance, don't worry – Ops Center tells you if it's feeling
the strain. When the Enterprise Controller exceeds 2700 access
points, you'll get a Warning incident. At 3000 access points,
you'll get a Critical incident. For a Proxy Controller, you'll get a
Warning when it exceeds 450 access points and a Critical incident
at 500 access points. So there's time and some headroom to make
adjustments.

The Sizing and Performance Guide has more information, and if you want to adjust the number of access points each Proxy Controller is handling, see Rebalancing Assets.

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.Captcha