Performance Counters - · PDF fileCisco RAN Management System Administration Guide, ... Performance Counters Performance Periodic Statistics. ... Performance Counters RMS KPIs and

Performance Counters

The RMS has a variety of PMG performance counters and upload server (ULS) counters that are displayedin the log files. These logs are located in the /rms/log/ directory. The various statistics that are calculated aredescribed here.

• PMG Counters, page 1

• Upload Server Counters, page 8

• RMS KPIs and Counters, page 11

PMG CountersPerformance counts are calculated for each PMG message type. The performance log files are located inrms/log/pmg and the following files are available:

• pmg-msg-perf.csv—PMG Performance Messages

• pmg-perf-periodic.csv—PMG Performance Periodic Messages

• rms-perf-gateway-periodic.csv—Performance Periodic Gateway Statistics

This table lists the various PMG messages for which statistics are calculated. All counts are integer. Thepolling interval is by default once per hour, but can be configured and is shown in the log as summary periodsec.

Table 1: Performance Message Types

DescriptionCounters

Inbound request to Activate a deviceActivate

Inbound request to Block a deviceBlock

Inbound connected eventConnected

Inbound request for connection request for a deviceConnectionRequest

Cisco RAN Management System Administration Guide, Release 5.1 MR 1

DescriptionCounters

Inbound request to create a FRM groupCreateGroup

Inbound request to create a FRM grouptypeCreateGroupType

Inbound request to create a FRM poolCreatePool

Inbound request to create a FRM pooltypeCreatePoolType

Inbound request to Deactivate a deviceDeactivate

Inbound request to Delete a deviceDelete

Inbound request to delete FRM GroupTypesDeleteFRMGroupType

Inbound request to delete FRM GroupsDeleteFRMGroups

Inbound request to delete FRM pool typeDeleteFRMPoolType

Inbound request to delete FRM poolsDeleteFRMPools

Inbound request to delete a FRM groupDeleteGroup

Inbound request to delete a FRM grouptypeDeleteGroupType

Inbound request to delete a FRM poolDeletePool

Inbound request to delete a FRM pooltypeDeletePoolType

Inbound Firmware upgrade eventFirmwareUpgraded

Inbound Firmware verified eventFirmwareVerified

Inbound request to get all FRM GroupTypesGetAllFRMGroupTypes

Inbound request to get all FRM Groups with details of a typeGetAllFRMGroups

Inbound request to get all FRM pool typesGetAllFRMPoolTypes

Inbound request to get all FRM pools with details of a typeGetAllFRMPools

Inbound request to get devie assignment infromation for a groupGetDeviceAssignmentByGroups

Inbound request to get FRM GroupTypeGetFRMGroupType

Inbound request to get details of FRM groupsGetFRMGroups

Inbound request to get pool type detailsGetFRMPoolType

Cisco RAN Management System Administration Guide, Release 5.1 MR2

Performance CountersPMG Counters

DescriptionCounters

Inbound request to get FRM pool detailsGetFRMPools

Inbound request to get names of all FRM groups of a typeGetGroupNames

Inbound request to get all FRM Group type namesGetGroupTypeNames

Inbound request to get GroupType detailsGetGroupTypesDetails

Inbound request to get details of FRM groupGetGroupsDetails

Inbound request to get group usage informationGetIDPoolsByGroups

Inbound request to get pool usage informationGetIDPoolsByTypes

Inbound request for getting device IDs belongs samegroup/subscriber

GetIDs

Inbound request to get live data for a deviceGetLiveData

Inbound request to get all FRM pool names of a typeGetPoolNames

Inbound request to get all FRM pool type namesGetPoolTypeNames

Inbound request to get PoolType detailsGetPoolTypesDetails

Inbound request to get details of FRM PoolGetPoolsDetails

Inbound request to stored data for a deviceGetStoredData

Inbound Location eventLocation

Notification that the CPE’s location status has changedLocationStatus

PMG collects and logs these counters in CSV file.

These counters are collected every 5 minutes.

Number of “group” update message

Number of device registration message

Number of GetLiveData issued

Number of SetLiveData issued

Inbound Online eventOnline

Inbound request to reassign a deviceReassignDevice

Inbound request to reboot a deviceRebootCPE

Inbound request to register a deviceRegister



DescriptionCounters

Inbound request to replace an existing device id with a new deviceid

Replace

Inbound request to reset a device to factory defautsResetCPEToFactoryDefaults

Inbound service eventService

Notification that there has been an error enabling serviceServiceError

Notification that service is now operational on the CPE after itenabled

ServiceOperational

Inbound request to set FRM GroupTypeSetFRMGroupType

Inbound request to create/update FRM GroupsSetFRMGroups

Inbound request to create/update FRM PoolsSetFRMPools

Inbound request to set live data for a deviceSetLiveData

Inbound request to shutdown a deviceShutdown

Inbound request to subscribe for eventsSubscribe

Inbound tampered eventTampered

Inbound request to un-subscribe for eventsUnSubscribe

Inbound request to Unblock a deviceUnblock

Inbound request to update a deviceUpdate

Inbound request to update a FRM groupUpdateGroup

Inbound request to update a FRM grouptypeUpdateGroupType

Inbound request to update IMSIs for a deviceUpdateIMSI

Inbound request to update a FRM poolUpdatePool

Inbound request to update a FRM pooltypeUpdatePoolType

For each message type, the following information is displayed in addition to the counts and statistics:DescriptionPerformance Counter

The timestamp of the event (in UMT format).timestamp



DescriptionPerformance Counter

The duration of the event (in seconds).summary period sec

The length of time the Upload Server is operational at the time of theassociated timestamp (in milliseconds).

uptime ms

The following example illustrates the Performance counter data captured for PMG, for a period of one hour.period end, summary period sec, msg name, avg response time ms,max response time ms, min response time ms, num msgs, num errors

2013-05-16T00:00:00.538Z,3600,Connected,0,0,0,151,02013-05-16T00:00:00.538Z,3600,Location,0,0,0,142,02013-05-16T00:00:00.538Z,3600,Register,250457,410637,102898,8,02013-05-16T00:00:00.538Z,3600,ServiceOperational,230348,240386,220310,2,0

No of ErrorsNo ofMessages

Minresponsetime (ms)

Maxresponsetime (ms)

AvgResponsetime (ms)

MessageName

SummaryPeriod (sec)

Period End

0151000Connected36002013-05-16T00:00:00.538Z

0142000Location36002013-05-16T00:00:00.538Z

08102898410637250457Register36002013-05-16T00:00:00.538Z

02220310240386230348ServiceOperational

36002013-05-16T00:00:00.538Z

Performance Periodic StatisticsThe performance periodic statistics file (pmg-perf-periodic.csv) lists the following statistics for each messagetype received within a specified period of time:

Table 2: Performance Period Statistics

DescriptionStatistic

The average response time in milliseconds for the message within thesummary period given by summary period sec.

avg response time ms


Performance CountersPerformance Periodic Statistics


The maximum response time in milliseconds for the message withinthe summary period given by summary period sec.

max response time ms

The minimum response time in milliseconds for the message within thesummary period given by summary period sec.

min response time ms

Total number of messages received during the summary period.num msgs

Number of errors occurred during the summary period for the message.num errors

Total bytes received for the message within the summary period givenby summary period sec.

total bytes received

Total bytes sent for the message within the summary period given bysummary period sec.

total bytes sent

Total bytes received per second for the message within the summaryperiod given by summary period sec.

bytes received per second

Total bytes sent per second for the message within the summary periodgiven by summary period sec.

bytes sent per second

Here is an example of the performance period log:

period end,summary period sec,msg name,avg response time ms,max response time ms,min response

time ms,num msgs,num errors,total bytes received,total bytes sent,bytes received per second,bytes sent per second2014-09-01T11:00:00.469Z,2589,Connected,0,0,0,24,0,0,0,0,02014-09-01T11:00:00.469Z,2589,Location,0,0,0,24,0,0,0,0,02014-09-01T11:00:00.470Z,2589,ServiceOperational,490,490,490,1,0,0,0,0,02014-09-01T11:00:00.471Z,2589,GetAllFRMGroupTypes,135,161,114,14,0,2996,30226,1,82014-09-01T11:00:00.471Z,2589,SetFRMGroups,143,176,134,6,0,10251,1693,3,02014-09-01T11:00:00.472Z,2589,GetAllFRMPoolTypes,74,86,70,5,0,1060,2990,0,12014-09-01T11:00:00.472Z,2589,GetLiveData,142,234,121,6,0,3024,1698,1,02014-09-01T11:00:00.473Z,2589,GetFRMGroupType,73,85,63,7,0,1585,4516,0,1

This example displays as follows when imported into Excel (partial output):

num errorsnum msgsminresponsetime ms

maxresponsetime ms

avgresponsetime ms

msg namesummaryperiod sec

period end

024000Connected25892014-09-01T11:00:00.469Z

0142000Location25892014-09-01T11:00:00.469Z


Performance CountersPerformance Periodic Statistics

num errorsnum msgsminresponsetime ms

maxresponsetime ms

avgresponsetime ms

msg namesummaryperiod sec

period end

01490490490ServiceOperational

25892014-09-01T11:00:00.470Z

014114161135GetAllFRMGrouptypes

25892014-09-01T11:00:00.471Z

Performance Message StatisticsThe performance message statistics file (pmg-msg-perf.csv) lists each message received and the followingtimes taken by the BAC PMG for processing:

Table 3: Performance Message Statistics


The processing time in milliseconds for the message with BACprocessing time removed.

msg process time ms

The BAC processing time in milliseconds for the message.bac process time ms

Total message processing time in milliseconds including un-marshallingthe message, message processing time, BAC processing time andresponse message marshalling.

total msg process time ms

Example of performance message log:

timestamp,msg name,trans id,eid,msg process time ms,bac process time ms,total msg processtime ms2014-09-01T08:27:12.607Z,GetAllFRMGroupTypes,DCCdccadminf6c25bb6-fbd1-4e2e-a4aa-dfa9e762d25c,null,119,0,257,214,1966,0,12014-09-01T08:27:13.951Z,GetAllFRMPoolTypes,DCCdccadmin8fb9ffae-accb-442c-995d-eec6ce6a4c46,null,38,0,169,212,598,0,02014-09-01T08:27:14.765Z,GetAllFRMPools,DCCdccadmin4163d646-d277-4661-af83-97669b2d6bb3,null,24,0,116,241,605,0,02014-09-01T08:27:58.807Z,GetAllFRMPoolTypes,DCCdccadmin73b1f28f-68ea-40eb-ab3c-b4c8bf558531,null,31,0,120,212,598,0,02014-09-01T08:27:59.044Z,GetAllFRMGroups,DCCdccadmin1d74ccd2-e4d4-48e6-9839-3f5217b4ce66,null,30,0,132,241,3205,0,1

Performance Group Periodic CountersThe performance group periodic counters file (rms-perf-group-periodic.csv) lists for each specified periodthe following counters. The period is set by the property "registration.metrics.time.interval.in.milli.seconds"defined in dcc.properties, and the default value is 3600000. The polling interval is by default one hour or asdefined in the dcc.proeprties file: "registration.metrics.time.interval.in.milli.seconds." All counts are integer.


Performance CountersPerformance Message Statistics

Table 4: Performance Group Periodic Counters

DescriptionCounter

Total number of FemtoGateways.NumberOf FemtoGateway

Number of devices at each FemtoGateway.NumberOfDevicesInFemtoGateway

Number of HeNB gateways.NumberOf HeNBGW

Number of devices in each HeNB gateway.NumberOfDevicesIn HeNBGW

Number of Enterprises created.NumberOf Enterprise

Number of devices in each enterprise.NumberOfDevicesIn Enterprise

Number of sites created.NumberOf Site

Number of devices in each site.NumberOfDevicesIn Site

Here is an example of the performance gateway periodic counters log:[blrrms-central-22] /rms/log/pmg $ cat rms-perf-group-periodic.csvperiod end,NumberOf FemtoGateway,NumberOfDevicesIn FemtoGateway,NumberOfHeNBGW,NumberOfDevicesInHeNBGW,NumberOf Enterprise,NumberOfDevicesIn Enterprise,NumberOf Site,NumberOfDevicesInSite2015-06-18T00:22:12.996Z,1,DefaultFGW=0,1,DefaultHeNBGW=0,1,DefaultEnterprise=0,1,DefaultSite=02015-06-18T01:22:12.996Z,1,DefaultFGW=0,1,DefaultHeNBGW=0,1,DefaultEnterprise=0,1,DefaultSite=02015-06-18T09:22:12.998Z,3,DefaultFGW=0;FGWLTE=0;FGW-1=1,4,HeNBGW_Ad=0;HENBGW-1=0;DefaultHeNBGW=0;HeNBGW_Ad=0,1,DefaultEnterprise=0,1,DefaultSite=02015-06-18T10:22:12.998Z,3,DefaultFGW=0;FGWLTE=0;FGW-1=1,4,HeNBGW_Ad=0;HENBGW-1=0;DefaultHeNBGW=0;HeNBGW_Ad=0,1,DefaultEnterprise=0,1,DefaultSite=0

Upload Server CountersThe Upload Server periodic counters files (upload-perf-periodic.csv and weekly-perf-summaries.csv) list foreach specified period the following counters. The upload-perf-periodic.csv file maintains counter data for thecurrent day (daily) and the weekly-perf-summaries.csv file contains the same data maintained weekly (sevendays).

The period is set by the property "perf.summary.intervalMS" defined in the UploadServer.properties, and thedefault value is 300000. The polling interval is 5 minutes by default or as defined in the UploadServer.proeprtiesfile: "perf.summary.intervalMS".

All counters are integer.

Trigger PointDescriptionField

Southbound Statistics Counters

Set to current maximum concurrent uploadsif it is greater than the previous maximumconcurrent uploads.

The maximum number of concurrentuploads during the interval

max concurrent uploads


Performance CountersUpload Server Counters


Incremented if upload request issuccessfully handled by the ULS.

The number of southbound uploadscompleted in the interval ending withthe associated timestamp

SB uploads completed

Incremented if:

• Southbound connection is rejectedbecause the maximum connectionlimit is reached.Maximumconnectionlimit is defined by theUploadServer.sb.connection.limit.maxproperty.

• Upload URI references the parentdirectory, for example, HTTP uploadrequest has ../../../../tmp/test.txt asURI.

• ULS internal buffer is filled and nomore Upload requests can beaccepted.

• HTTP request has method other thanPUT, POST or GET.

• Bad HTTP request, for example,initial line of HTTP request is oflength greater than 4096.

• Internal server error.

The number of southbound uploadsfailed in the interval ending with theassociated timestamp

SB uploads failed

Incremented with size of request once it isreceived over southbound interface.

The number of southbound bytesreceived in the interval ending withthe associated timestamp

SB bytes rcvd

Incremented with the size of the responseonce it is sent over southbound interface.

The number of southbound bytes sentin the interval ending with theassociated timestamp

SB bytes count

Incremented if the southbound connectionpersists for more than the period definedby theUploadServer.sb.channel.maxsessmsproperty. Default is 20 mins.

The number of southbound sessiontimeouts in the interval ending withthe associated timestamp

SB session timeout

Incremented after sending 200OK responseto HTTP GET request for a file defined by/opt/CSCOuls/files/conf/index.html or anyother file defined byUploadServer.probeFileLocation andUploadServer.probeFilename properties.

Number of SB requestsserved/responded

SB status sent




Incremented if failed to send the abovestatus.

Number of SB requests for whichULS failed to respond

SB status failure

Northbound Statistics Counters

Incremented when the HTTP downloadrequest is successfully served by ULS.

The number of northbound uploadscompleted in the interval ending withthe associated timestamp

NB downloadscompleted

Incremented when the HTTP downloadrequest is successfully served by the ULS.

The number of northbound uploadsfailed in the interval ending with theassociated timestamp

NB downloads failed

Incremented with size of request once it isreceived over the northbound interface.

The number of northbound bytesreceived in the interval ending withthe associated timestamp

NB bytes rcvd

Incremented with the size of the responseonce it is sent over northbound interface.

The number of northbound bytes sentin the interval ending with theassociated timestamp

NB bytes sent

Incremented after sending 200OK responseto HTTP GET request for a file defined by/opt/CSCOuls/files/conf/index.html or anyother file defined byUploadServer.probeFileLocation andUploadServer.probeFilename properties.

The number of NB requests served /responded.

NB session count

Incremented when the northboundconnection persists for more than the perioddefined by theUploadServer.nb.channel.maxsessmsproperty. Default is 20 minutes.

The number of northbound sessiontimeouts in the interval ending withthe associated timestamp

NB session timeout

Set to current maximum concurrentdownloads if it is greater than the previousmaximum concurrent downloads.

Maximum number of concurrentdownloads during the interval

max concurrentdownloads

File counters

Incremented before compressing a file.The total bytes of log files prior tocompressing them during the interval

Bytes beforecompression

Incremented after file is successfullycompressed.

The total bytes of log files aftercompressing them during the interval

Bytes after compression

Incremented with the size of the file onceit is deleted.

The total number of bytes deletedduring the interval

Bytes deleted




Incremented after file is successfullyarchived.

The total number of bytes archivedduring the interval

Bytes archived

Incremented once a file is listed down.The total number of files listed duringthe interval

Number of files listed

Incremented once a file is deletedsuccessfully.

The total number of files deletedduring the interval

Number of files deleted

Incremented once a file isarchived/compressed.

The total number of files archivedduring the interval

Number of filesarchived

Incremented with the time taken forcompression of a file once it is completed.

The total time spent compressing thelog files during the interval

Total time compressing

Incremented with the time taken forarchival of a file once it is completed.

The total time spent archiving logfiles during the interval

Total time archiving

Incremented with time taken for deletion afile once the delete operation is complete.

The total time spent deleting log filesduring the interval

Total time deleting

Incremented with time taken once all thefiles are listed for directory maintenancepurpose (for example, deletion).

The total time spent listing the logfiles during the interval

Total time listing

Incremented once a new archive file iscreated.

The total number of archives createdduring the interval

Number of archives

Incremented after uploaded file is writtento disk.

Includes the total number of files foreach file type during the interval

Separate counters are present for eachfile type supported. For example, totalstat files, total stat bytes, total demandfiles, and so on.

Total number of filesfor each file type

File Types supported:stat files, demand files,cmas files, andunknown files

Incremented after uploaded file is writtento disk.

Includes the total number of bytes foreach file type during the interval

Total number of bytesfor each file type

RMS KPIs and CountersThe RMS KPIs and Counters feature enables RMS to collect and report KPIs in .CSV file format. it alsoprovides the functionality to upload these counters to Prime Performance Manager (PPM). In addition to thePMG and Upload server counters detailed above, the following counters are supported:

DescriptionCounters


Performance CountersRMS KPIs and Counters

BAC Counters

When BAC receives the incoming boot inform fromthe device, the counter is incremented.

Number of incoming boot inform

Number of incoming bootstrap inform

When a device boots and administration state issuccessful, the counter is incremented. Theoperational state is not considered as admin up.

Number of successful admin up

When a device boots and administration state is failed,the counter is incremented.

Number of failed admin up

When a device location fails, the counter isincremented.

Number of location check failure

When BAC receives the periodic inform from thedevice, the counter is incremented.

Number of incoming periodic inform

When BAC receives alarms from the devices, thecounter is incremented.

Number of incoming alarm

When the NWL scan is performed for the connecteddevice, the counter is incremented.

Number of NWL scan

When BAC performs NWL tolerance check andreported failure, the counter is incremented.

Number of NWL tolerance failure

When the Detected Neighbor Benchmark is updated,the counter is incremented.

Number of benchmark update

When the device GPS scan is performed, the counteris incremented.

Number of GPS scan

When the GPS tolerance is failed for the device, thecounter is incremented.

Number of GPS tolerance failure

When SetParameterValue is successful, the counteris incremented. The SetParameterValue isincremented when GA flow level and server level isinvoked.

Number of SetParameterValue

When SPV fails and if BAC receives a failureresponse, the counter is incremented. The errorSetParameterValue is incremented when GA flowlevel and server level is invoked.

Number of erroneous SetParameterValue



When GetParameterValue is successful, the counteris incremented. The GetParameterValue isincremented when GA flow level and server level isinvoked.

Number of GetParameterValue

When GetParameterValue fails and if BAC receivesa failure response, the counter is incremented. Theerror GetParameterValue is incremented when GAflow level and server level is invoked.

Number of erroneous GetParameterValue

When firmware upgrade is performed on a device andDPE, the counter is incremented.

Number of Firmware upgrade

When firmware upgrade is invoked and it fails, thecounter is incremented.

Number of erroneous Firmware upgrade

When reboot is performed for the device using AdminUI or API, the counter is incremented.

Number of reboot

Average activation time taken for the number ofdevices booted at specific interval

Device Activation Time = Device Admin Up time- Device Boot time

Total Activation Time = Sum of devices activationtime

Average Activation time = Total Activation Time/ Number of devices activated

The server property/server/metrics/inactive/device/size that holdsthe inactive devices based on the value defined. Theolder inactive device is removed from the list. Thedefault value is 100000. This value can bereconfigured if required.

Average activation time

When the device initiates a TR-069 session withanother device, the counter is incremented.

Number of TR-069 session

When the device lease query is performed, the counteris incremented.

Number of DHCP Lease query

When the configuration synchronization betweenRDU and DPE is done, the counter is incremented.

Number of config synch between RDU and DPE

When DPE is initialized and registered with RDU,the counter is incremented.

Number of DPE registration with RDU

When PNR is initialized and registered with RDU,the counter is incremented.

Number of PNR registration with RDU



When the BAC alarm is raised such as license alert,server status, and incoming events, the counter isincremented.

Number of BAC alarm raised

BAC counters are available in the following files:Note

• /rms/data/CSCObac/metrics/logs/dpeDPERMSKPI.csv on Servingnode

• /rms/data/CSCObac/metrics/logs/ rduRDURMSKPI.csv onCentralnode

DCC UI Counters

DCC UI collects and logs these counters in a CSVfile.

These counters are collected every 5 minutes.

Number of user logged-in using DCC UI

Number of UI session

Average UI response time

Sample CSVs of PMG, Upload, and KPI counters

• pmg-prov-stats-periodic.csv## SULEKH Version 5.0

# Time Stamp, period(ms),Incoming IP stats, Outgoing IP stats, Number of Register,Number of updateGroup,Number of GLD, Number of SLV2015-06-22T00:03:24.995Z,300000,,,0,0,0,02015-06-22T00:08:24.992Z,300000,,,0,0,0,0

• rms-perf-group-periodic.csvperiod end,NumberOf FemtoGateway,NumberOfDevicesIn FemtoGateway,NumberOfHeNBGW,NumberOfDevicesInHeNBGW,NumberOf Enterprise,NumberOfDevicesIn Enterprise,NumberOf Site,NumberOfDevicesInSite2015-06-22T00:22:13.012Z,3,DefaultFGW=0;FGWLTE=0;FGW-1=1,4,HeNBGW_Aditi1=0;HENBGW-1=0;DefaultHeNBGW=0;HeNBGW_Aditi=0,1,DefaultEnterprise=0,1,DefaultSite=02015-06-22T01:22:13.012Z,3,DefaultFGW=0;FGWLTE=0;FGW-1=1,4,HeNBGW_Aditi1=0;HENBGW-1=0;DefaultHeNBGW=0;HeNBGW_Aditi=0,1,DefaultEnterprise=0,1,DefaultSite=02015-06-22T02:22:13.013Z,3,DefaultFGW=0;FGWLTE=0;FGW-1=1,4,HeNBGW_Aditi1=0;HENBGW-1=0;DefaultHeNBGW=0;HeNBGW_Aditi=0,1,DefaultEnterprise=0,1,DefaultSite=0

• upload-perf-periodic.csvperiod end,period duration (sec),uptime ms,SB uploads completed,SB uploads failed,SBstatus sent,SB status failure,SB bytes rcvd,SB bytes sent,SB session count,SB session timeout,NBdownloads completed,NB downloads failed,NB bytes rcvd,NB bytes sent,NB session count,NB session timeout,Bytesbefore compression,Bytes after compression,Bytes deleted,Bytes archived,Number of files listed,Number offiles deleted,Number of files archived,Total time compressing,Total time archiving,Total timedeleting,Total time listing,Number of archives,Total stat files,Total stat bytes,Total demand files,Total demandbytes,Total cmas files,Total cmas bytes,Total unknown files,Total unknown bytes,max concurrent uploads,maxconcurrent downloads2015-06-22T00:00:00.001,300,325316134,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0



2015-06-22T00:05:00.000,299,325616133,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,02015-06-22T00:10:00.000,300,325916133,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0

• rms-prov-stats-periodic.csv## Version 5.0

#Time, Interval, ActiveEntryAPcount,IdleAPcount,NoOfInnerAP,MulticellEnterpriseAPcount,StandaloneAPCount,residentialAPcount, UMTSAPcount, LTEAPcount2015-06-22T06:02:13.074Z,59999,0,0,0,0,0,1,1,0

BAC - RDUrduRDURMSKPI.csv

##Version 3.10

#period end, summary period sec,bacAlarmRaised,dpeRegistration,pnrRegistration,reboot2015-06-17T09:26:15.205Z,300,5,0,0,02015-06-17T09:31:15.198Z,300,0,2,2,0

BAC - DPEdpeDPERMSKPI.csv

##Version 3.10

#period end, summary periodsec,avgActivationTime,bacAlarmRaised,benchmarkUpdate,configSyncRduandDpe,dhcpLeaseQuery,erroneousFirmwareUpgrade,erroneousGetParamValue,erroneousSetParamValue,failedAdminUp,firmwareUpgrade,getParamValue,gpsScan,gpsToleranceFailure,incomingAlarm,incomingBootInform,incomingBootStrapInform,incomingPeriodicInform,locationCheckFailure,nwlScan,nwlToleranceFailure,setParamValue,successfulAdminUp,tr069Session2015-06-17T09:35:25.680Z,300,0,6,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,02015-06-17T09:40:25.677Z,300,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0





Documents

Performance Counters - · PDF fileCisco RAN Management System Administration Guide, ... Performance Counters Performance Periodic Statistics. ... Performance Counters RMS KPIs and