Справочник Пользователя для SonicWALL 5.8.1

The requested data will be presented to the client as a .cap file, and can be saved or viewed 
on the local machine.

The client and NPCS must be able to reach one another. Usually, this means the client and the 
NPCS will be in the same physical location, both connected to the SonicWALL appliance. In 
any case, the client will be able to directly reach the NPCS, or will be able to reach the NPCS 
through the SonicWALL. Administrators in a remote location will require some method of VPN 
connectivity to the internal network. Access from a centralized GMS console will have similar 
requirements.

SonicOS currently allocates 32K to a rolling log buffer. When the log becomes full, it can be 
emailed to a defined recipient and flushed, or it can simply be flushed. Emailing provides a 
simple version of logging persistence, while GMS provides a more reliable and scalable 
method.

By offering the administrator the option to deliver logs as either plain-text or HTML, the 
administrator has an easy method to review and replay events logged.

To provide the ability to identify and view events across an entire enterprise, a GMS update will 
be required. Device-specific interesting-content events at the GMS console appear in Reports 
> Log Viewer Search page, but are also found throughout the various reports, such as Top 
Intrusions Over Time.