We're running AsyncOS 7.7.0 for Web build 725. When I try to grep the accesslog to follow a stream for troubleshooting, often I see nothing for about 10 seconds, then only
Binary file (standard input) matches
and then I get dropped back to the command prompt within the device. We have no custom fields configured on this device, (TAC originally told me during a call on a separate problem that there was a QA issue with this build and that some of the custom fields for logging didn't work correctly) so I'm curious what's causing this and how to fix it.
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...