Managing FireBreak
Most of the administrative tasks for FireBreak can be performed in the FireBreak object in the eDirectory (NDS), such as configuration of auto-updates, messaging and eDirectory options. Other tasks, like monitoring real-time actions can be done both at the server console and by browsing in log files.
FireBreak’s console menus follow the conventions for NetWare’s “look and feel", including implementation of “first letter" selection in the menus.
We have also developed a ConsoleOne snap-in module, as we believe that ConsoleOne represents a simplified and consequently more user-friendly approach for configuration and administration of the FireBreak installation.
Scanning
Norman FireBreak offers two types of scanning:
- On-access scanning is continuous scanning of files accessed on the server. So if a user tries to copy an infected file to or from your server, infect a file on the server, or run an infected file from the server, Norman FireBreak will detect the file and repair, quarantine, delete, or ignore it. These actions are all configurable. Both NSS and Classic NetWare volumes are supported. This can be done with or without Norman SandBox.
- On-demand scanning is used for scanning selected parts or the entire server for possible viruses at your request. This can be done with or without Norman SandBox.
Multi-CPU support
Many large companies use servers with multiple CPUs to increase performance. This has previously been a problem for many antivirus vendors. FireBreak can run perfectly well in a multi-CPU environment.
Clusters
Network servers are often connected to form one or more clusters, to ease administration, increase capacity, reduce load, etc. FireBreak is fully cluster compatible.
FireBreak NetWare WAN
Another strength of Norman FireBreak is Enterprise-wide functioning. If two or more NetWare servers are running Norman FireBreak, one of them can be configured to be a communications hub. The hub can then operate as a central monitoring station, enabling more efficient WAN administration.
For configuration purposes, a configuration object for Norman FireBreak is created in an eDirectory (NDS). From this configuration object all the Norman FireBreak objects can be configured from one central location, thus reducing the administrative burden for the administrator.
Messaging
The messaging module in FireBreak supports messages and alarms received from Norman Virus Control. All messages and alarms can be logged, printed, forwarded as SNMP traps, or broadcasted as NetWare alerts.
Sending messages over SMTP (email)
All messages and alarms can now be sent to selected recipients via email.
Protocol support
FireBreak automatically detects and fully supports the protocol used in its operating environment. It does not matter whether TCP/IP, IPX or both protocols are being used.
