6.9 Traffic Analysis Agent for NetWare Error Messages

After the Traffic Analysis Agent for NetWare is installed, the NE2-32.LAN driver cannot be loaded

Source: ZENworks Server Management; Management and Monitoring Services; Traffic Analysis Agent for NetWare
Explanation: When you installed the Traffic Analysis Agent for NetWare, the NE2-32.LAN driver was updated with a driver named NE2_32.LAN. Because the driver name was changed, you need to update the files that load drivers.
Action: Modify the files that load the adapter drivers to call the NE2-32.LAN driver, then load the NE2_32.LAN driver.

After the Traffic Analysis Agent for NetWare is installed, the NE3200.LAN driver cannot be loaded

Source: ZENworks Server Management; Management and Monitoring Services; Traffic Analysis Agent for NetWare
Explanation: When you installed the Traffic Analysis Agent for NetWare, the NE3200.LAN driver was updated with a driver named NE3200P.LAN. Because the driver name was changed, you need to update the files that load drivers.
Action: Modify the files that load the adapter drivers to load the NE3200P.LAN driver.

After the Traffic Analysis Agent for NetWare is installed, the SMART386.LAN driver cannot be loaded

Source: ZENworks Server Management; Management and Monitoring Services; Traffic Analysis Agent for NetWare
Explanation: When you installed the Traffic Analysis Agent for NetWare, the SMART386.LAN driver was updated with a driver named MADGEODI.LAN. Because the driver name was changed, you need to update the files that load drivers.
Action: Modify the files that load the adapter drivers to load the MADGEODI.LAN driver.

LANZCON does not load

Source: ZENworks Server Management; Management and Monitoring Services; Traffic Analysis Agent for NetWare
Explanation: This message is displayed because of a change in the community string parameter of SNMP.
Action: Enter the control community string as a command line parameter at the NetWare console prompt while loading LANZCON. 
LOAD LANZCON ControlCommunity = control community string

If LANZCON is launched without any command line argument, then the default control community string is PUBLIC.

The LANalyzer - Adapter [MAC address] is not monitored because it is not a supported media type

Source: ZENworks Server Management; Management and Monitoring Services; Traffic Analysis Agent for NetWare
Explanation: The Traffic Analysis Agent for NetWare supports Ethernet, token ring. FDDI, and 100BaseT and 100VG-AnyLAN are considered Ethernet media types. Any other adapter media types are not supported.
Action: Use an Ethernet, token ring, or FDDI adapter for the Traffic Analysis Agent for NetWare operations.

The LANalyzer - Adapter [MAC address] is not monitored because the driver’s promiscuous mode cannot be turned on

Source: ZENworks Server Management; Management and Monitoring Services; Traffic Analysis Agent for NetWare
Explanation: The driver is corrupted or the adapter is damaged.
Action: Replace the adapter. If the problem persists, call your Novell Authorized ResellerSM.

The LANalyzer - Adapter [MAC address] is not monitored because the Traffic Analysis Agent for NetWare cannot allocate memory

Source: ZENworks Server Management; Management and Monitoring Services; Traffic Analysis Agent for NetWare
Explanation: The Traffic Analysis Agent for NetWare does not have adequate RAM available for it to build the internal data structures required to monitor the adapter.
Action: Do one or both of the following:

  • Unload any unnecessary NLM files.

  • Add additional memory to your server.

The LANalyzer - Ethernet adapter [MAC address] is not monitored because it is a pipelined adapter

Source: ZENworks Server Management; Management and Monitoring Services; Traffic Analysis Agent for NetWare
Explanation: A pipelined adapter is one that begins to send received data to the driver before the entire packet has been received. The Traffic Analysis for NetWare cannot support this method of data reception because it must tally all the information in a packet before the information is sent to its destination.
Action: If the adapter lets you switch from pipelined mode to non-pipelined mode, do so. If the adapter cannot switch modes, use a non-pipelined adapter for Traffic Analysis for NetWare transactions. Check the Novell Support Web Site for information regarding availability of the recommended adapters. You might need to contact your adapter vendor for the appropriate adapter.

The LANalyzer - Ethernet adapter [MAC address] is not monitored because the driver does not support promiscuous mode

Source: ZENworks Server Management; Management and Monitoring Services; Traffic Analysis Agent for NetWare
Explanation: A promiscuous mode driver receives all the packets and errors on the network it is attached to. The Traffic Analysis Agent for NetWare requires promiscuous mode to function properly, and does not support non-promiscuous mode Ethernet or token ring adapters.
Action: Install a promiscuous mode driver on the server. Check the Novell Support Web Site for information regarding availability of the latest promiscuous mode drivers. You might need to contact your adapter vendor for the appropriate driver.

The LANalyzer - Token Ring adapter [MAC address] is not monitored because it is a pipelined adapter

Source: ZENworks Server Management; Management and Monitoring Services; Traffic Analysis Agent for NetWare
Explanation: A pipelined adapter begins to send received data to the driver before the entire packet has been received. The Traffic Analysis Agent for NetWare cannot support this method of data reception because it must tally all the information in a packet before the information is sent to its destination.
Action: If the adapter lets you switch from pipelined mode to non-pipelined mode, do so. If the adapter cannot switch modes, use a non-pipelined adapter for Traffic Analysis Agent for NetWare transactions. Check the Novell Support Web Site for information regarding availability of the recommended adapters. You might need to contact your adapter vendor for the appropriate adapter.

The LANalyzer - Token Ring adapter [MAC address] is not monitored because the driver does not support raw send

Source: ZENworks Server Management; Management and Monitoring Services; Traffic Analysis Agent for NetWare
Explanation: The Traffic Analysis Agent for NetWare requires an adapter driver that supports the raw send feature. An adapter driver that supports raw send allows applications to build both the header and data components of a frame. The driver then receives the packet and sends it to its destination.
Action: Install an adapter driver on the server that supports raw send. Check the Novell Support Web Site for information regarding availability of the recommended drivers. You might need to contact your adapter vendor for the appropriate driver.

The LANalyzer - Token Ring/FDDI adapter [MAC address] is not monitored because the driver does not support promiscuous mode

Source: ZENworks Server Management; Management and Monitoring Services; Traffic Analysis Agent for NetWare
Explanation: A promiscuous mode driver receives all the packets and errors on the network it is attached to. The Traffic Analysis Agent for NetWare requires promiscuous mode to function properly, and does not support non-promiscuous mode Ethernet, token ring, or FDDI adapters.
Action: Install a promiscuous mode driver on the server. Check the Novell Support Web Site for information regarding availability of the latest promiscuous mode drivers. You might need to contact your adapter vendor for the appropriate driver.

Your server abended when you backed it up after installing the Traffic Analysis Agent for NetWare

Source: ZENworks Server Management; Management and Monitoring Services; Traffic Analysis Agent for NetWare
Explanation: This problem is not related to the installation process. However, some Traffic Analysis Agent for NetWare files were loaded and probably were open when you backed up the server. Depending on the backup software you use, backing up the lanz.cfg file when it is open can abend the server.
Action: Do not back up the lanz.cfg file when you back up the server.