Snoops Not Archiving Correctly
(Doc ID 2309300.1)
Last updated on JUNE 30, 2023
Applies to:
Oracle Communications Network Charging and Control - Version 5.0.2 and laterInformation in this document applies to any platform.
Symptoms
The rolling snoops file are not being archived correctly in a directory per hour and not being zipped either. Below you can see snoops not zipped and not put into separate 1-hour directory:
The rolling snoop scripts run the Solaris 'snoop' command to capture network packets for a specific interface device. It runs in a continuous loop creating capture files that up to x network packets (configurable) in size.
These scripts can be found in the /IN/service_packages/SUPPORT/bin directory:
rolling-snoop.sh
start-rolling-snoop.sh
stop-rolling-snoop.sh
snoop_archiver.sh
Please have a look on the following article, to learn more about the rolling snoop stack scripts: "How to Use the Rolling Snoop Scripts to Create Hourly Archives Directories of Snoop Capture Files (Doc ID 1210585.1)".
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |