ZfS is made up of several components, some of which require certain setup tasks before you can use them, and others that do not.
The following components do not require any specific setup tasks:
The following sections describe the setup tasks that are required to get the following components up and running:
If you need to install other software or perform other maintenance functions on your server, you can stop Management and Monitoring Services and down the server. After performing the maintenance, you must reboot the server and restart the services in order for the server to resume its Management and Monitoring Services.
To stop and restart Management and Monitoring Services and down the server, complete the following steps at the management server console prompt:
To stop and unload ZfS Management and Monitoring Services, enter unmw.
To stop all JAVA processes, enter java -killall.
To exit JAVA, enter java -exit.
To down the server and restart, enter restart server.
To down the server, enter down server. You need to start the server again.
Because the appropriate commands to start the back-end and discovery processes (SLOADER and NETEXPLOR) were inserted in the AUTOEXEC.NCF file when you installed Management and Monitoring Services, restarting the server will start these processes. If you modified the AUTOEXEC.NCF file and need to manually start these processes, see Manually Starting Discovery and Back-End Processes.
The discovery software on the management server automatically discovers the nodes on your network. Network nodes include servers, desktops, routers, switches, and any other network devices. Discovery starts automatically when the ZfS software is loaded on the management server and runs continually, 24 hours a day. The amount of time to build a complete database depends on the size of your network. Very small networks might take one or two hours; very large networks (several thousand nodes) might require several days.
It is recommended that you run Network discovery on a standalone as the discovery process consumes a longer duration if you use the system.
After installation, your servers are in one of the following states:
If you selected Yes to start the autodiscovery process and back-end services during installation, discovery is running on your ZfS server and your network is continually being discovered. You do not need to do anything further with regards to configuring discovery unless you want to modify your discovery parameters after you check the results of the initial discovery. For instructions on checking the results of discovery and modifying your discovery parameters, see Understanding Network Discovery and Atlas Management.
IMPORTANT: After modifying any discovery parameters, you must restart the server as described in Stopping and Starting Management and Monitoring Services.
If you selected No, and did not start the autodiscovery process and back-end services during installation, you must start discovery after you modify the default discovery parameters. For specific instructions on modifying discovery parameters, see Understanding Network Discovery and Atlas Management.
Before discovering your network, you can modify the following discovery parameters:
IMPORTANT: After modifying any discovery parameters, you must restart the services as described in Stopping and Starting Management and Monitoring Services. If you never started discovery or the back-end services, you can manually start the services as described in Manually Starting Discovery and Back-End Processes.
The commands to start autodiscovery and load the back-end services are inserted into the AUTOEXEC.NCF file by the installation program. Restarting the server will automatically start these processes. However, if you remove these commands you will need to manually start autodiscovery and load the back-end services (management site services).
During installation, a search path is added to the AUTOEXEC.NCF file to the management server program file path --- ZENWorks\MMS\MWSERVER\BIN
Type the following in order at the management server console prompt, to manually start discovery and the back-end processes:
The server will accept requests from ConsoleOne only after the SLOADER.NCF is completely loaded.
The ZfS Alarm Management System (AMS) can receive SNMP traps from any SNMP-enabled device or computer hosting a proxy SNMP agent. If your network device is using Management Agent for NetWare, Management Agent for Windows NT, NetWare LANalyzer® AgentTM, or LANalyzer Agent for Windows NT software, the device is discovered automatically for you. No setup is needed after installing the software.
Third-party SNMP agents require some setup before traps can be received. For information on setting up third-party SNMP agents, see SNMP Configuration.
Because the Management Agent for NetWare and the ManageWise® Agent for Windows NT are based on SNMP, all actions that are directed from network management console to a server involve SNMP SET and GET requests from the manager to the agent. Any ConsoleOne requesting data from a managed server does so by issuing an SNMP GET request. An SNMP SET command is required to set server alarm thresholds or configuration parameters. Conducting these management operations from ConsoleOne such as ConsoleOne, raises the issue of ensuring security. In particular, unauthorized users setting configuration parameters on a server could cause severe performance problems or even sabotage network operations.
For these reasons, you should secure communication between the management system and your SNMP agents. For further information on SNMP security, SNMP Configuration.
The Traffic Analysis Agent for NetWare is a distributed network analyzer that complements ZfS. While other ZfS agents collect data about specific network nodes, such as servers, the Traffic Analysis Agent for NetWare observes the interaction among these nodes on a specific LAN segment. The agent is installed on a NetWare 4.x or NetWare 5.x server. To set up Traffic Analysis Agent for NetWare, see Starting the Traffic Analysis Agent for NetWare.
The Traffic Analysis Agent for Windows NT/2000 uses SNMP to communicate with the management server. After installation, in order for the Traffic Analysis Agent for Windows NT/2000 to operate, you must start the SNMP services. To start SNMP services, complete Starting the SNMP Service for the Traffic Analysis Agent for Windows NT/2000.
After the agents are set up, you must restart the Windows NT/2000 server on which the agent resides.
The installation program for the Traffic Analysis Agent for NetWare modifies the AUTOEXEC.NCF file so that the agent starts automatically. Therefore, you do not need any further configuration. If, however, you are upgrading from a previous version of the Traffic Analysis Agent (referred to as the LANalyzer agent), and did not uninstall the previous version, you must ensure that each server on which you upgraded the agent will run the new Traffic Analysis Agent.
To ensure that the upgraded NetWare servers run the new Traffic Analysis Agent:
On each NetWare server where you upgraded the ZfS Traffic Analysis Agent, open the AUTOEXEC.NCF file located in SYS:\SYSTEM.
Comment out the following lines by placing a # character at the beginning of the line as follows:
#Search add lanzdir
#LANZ.NCF
The first statement defines the search path where lanzdir is the directory in which the older agent is installed. The second statement loads the older agent.
Save the file and restart the server.
The new agent will load and run automatically. The LANZ.NCF file in the agentinstallfolder\LANZ will start the Traffic Analysis agent. The ULANZ.NCF in the same folder will stop the Traffic Analysis agent.
If you have configured Windows NT/2000 to start the SNMP service automatically, the agent installed on Windows NT/2000 starts with the SNMP service when you start Windows NT/2000.
If you have not configured Windows NT/2000 to start the SNMP service automatically, do either of the following:
When the SNMP service is started, the traffic analysis agent for Windows NT/2000 will also start.