- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
08-19-2023 06:40 PM
The customer found that some traffic logs have extremely large bytes, reaching 281.5T,
Looking at the log details, it was found that:
Question 1:
Details:
Type end
Bytes 281474976579754 ---- I think this is an incorrect display?
Bytes Received 2147483647
Bytes Sent 170
Repeat CountPackets1
Packets Sent 2
Bytes= Bytes sent + Bytes Received
=2147483647+170
=2147483817 This is the correct value
Question 2:
Generated Time 2023/08/17 15.07:55
start Time 2023/08/17 15:07:20
Receive Time 2023/08/17 15:07:55
The session lasts for 35 seconds and transmits 281.5T Bytes, which is too exaggerated.
The device is vm-300, version 10.2.4-h3
Do you have any suggestions? Can you determine the bugs in the version
08-23-2023 02:53 AM - edited 08-23-2023 02:54 AM
Hello Felixcao,
The issue is currently under investigation.
You can open a case to TAC for an updated status.
Olivier
PCSNE - CISSP
Best Effort contributor
Check out our PANCast Channel
Disclaimer : All messages are my personal ones and do not represent my company's view in any way.
01-20-2024 01:12 AM
on which version are you running?
Maybe time to upgrade.
PCSNE - CISSP
Best Effort contributor
Check out our PANCast Channel
Disclaimer : All messages are my personal ones and do not represent my company's view in any way.
01-23-2024 02:18 AM
HI @ozheng ,
I just encountered this issue with lots of GBs and Tb's in the traffic logs. I just want to ask if you have any idea whether this issue is confirmed to be a bug?
I am running PANOS 10.1.8
Regards,
Renz
01-24-2024 12:27 AM
Hi,
Anyone has resolution for this issue?
Regards,
Renz
01-24-2024 07:26 PM
Hello Renzanjo11,
Please open a case to TAC to get formal confirmation.
Thank you.
Olivier
PCSNE - CISSP
Best Effort contributor
Check out our PANCast Channel
Disclaimer : All messages are my personal ones and do not represent my company's view in any way.
02-18-2024 08:44 PM
I opened a case before and TAC confirmed that it was a bug, but at that time, there was no plan to fix it, so I am not sure which version to fix,
1: This does not affect usage and can be ignored.
2: Try updating to the latest recommended version.
3: Open a case and confirm the fixed version with TAC.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!