The historical data records are the Comma separated files generated by Oracle Session border controller to maintain traffic statistics.This also include performance statistics like CPU utilization , Memory Consumption etc.
These historical data records (commonly known as HDRs) are pushed out of the hardware for performance reporting. In order to get nicely presentable graphical reports you should have Net-Net Central in your network.
The Net-Net Central (commonly known as NNC) is a elemantery managment system for Oracle Session border controllers.
It includes Device Manager, Configuration Manager , Report Manager , Security Manager and Fault Manager.
The HDRs are push to NNC every 15minutes(this is a default value can be changed to accommodate your needs) however the records are collected and written to a CSV every 5mins (default values).
In order to configure session border control a.k.a SBC to generate HDRs , collection group need to configured i.e
Following details are mandatory to configure push-receiver from SBC CLI.
In case if configuration has been done using NNC ,you will require additional password i.e acmepacket
It is also recommended to restart collection service , you can use following command
request collect restart
At this stage you have configured HDRs correctly however I am sure it will not work until you configure server public key in SBC.
Please note SBC use SSH2 however most of the linux servers use OpenSSH, this will cause incompatiabilty as both have different key format.
The best way is to convert your server public key to SSh2 using following , excute command where OpenSSH is installed otherwise it will fail.
ssh-keygen -e -f /etc/ssh/id_rsa.pub
Now copy the output of this command and import this key in using following command
ssh-public-key import known-hosts <any-name-to-identify>
Oracle recommends to import both RSA and DSA keys in SBC.
To verify if HDRs are pushed correctly execute following command
show logfile log.collect
To verify NNC has received CSV files , look for the files at data-store location (mention above while configuring collection service)