05-04-2017 03:08 AM
We have tried to run below mantioned Rest API call from DHCP Clint
o/p of the above comm. is blank :
is there other way to collect switch frame time series performance data.??
We have also tried with 14.2.0 REST API for txFrameRate and rxFrameRate but still no luck .
05-04-2017 11:11 PM
timeseriestxframerate applies to flow, so you need to have a flow defined.
Further, it only can applies to one switch (where you have your flow running).
To get performance data, historical or real time, which also assumes
that you have BNA setup to gather historical data already.
So, one test would to be see if you are able view the same data in
BNA client as you try to access via the REST API.
Notice that limit of number of ports is 100 in 14.0, and increased to 600 in 14.2.
For historical performance data - use timeseriestraffic from the Port-related performance data URIs,
see the part starting on page 68 in 14.2.0 REST API Guide:
Example URL for timeseriestraffic:
05-31-2017 06:18 AM
Thank you very much for replying and detailed explanation.
Can you please confirm that flow should be defined on BNA server or each switch which are monitored by BNA ?
05-31-2017 07:35 AM
you can define the flow (flow vision / monitor) using BNA for those switches where you have flows you want to monitor. Either one or several, all...
09-20-2018 06:49 AM
I'm working with NetApp OnCommand Insight (OCI) for a customer with a large fabric. We've been informed that OCI will only be able to retrieve performance data for up to 600 ports via the ReST API unless the ports are put into resource groups (<600 ports per group). Searches for this limitation eventually led me to this thread, and I'm hoping that you can enlighten me as whether this is true or not. And also some information on how these resource groups are created and populated, as this seems to be somewhat lacking in the BNA documentation.
09-20-2018 07:47 AM