| The first step in making the most out of ZENworks for Servers 3 reports is understanding what types of reports are available and what information can be obtained from them. ZENworks for Servers 3 provides inventory reports that enable you to create lists of hardware and services available on your network to use for tracking and planning your network resources. You can use topology reports, generated by ZENworks, to understand the layout and design of your network, enabling you to plan for future growth. ZENworks for Servers 3 also includes health reports that you can use to understand your network's overall health and quickly diagnose issues. Reports on TED distribution are also provided to enable you to understand the current status of your distribution to determine progress and any errors that might have occurred. Understanding Server Inventory Reports ZENworks for Servers 3 enables you to create inventory reports of hardware and software that are located on your managed servers. These reports can be very useful to you if you need to know what hardware or software is on a particular machine. Suppose you want to install new server software that requires a server with a minimum of 256MB of RAM and a processor speed of at least 500MHz. You can use ZENworks for Servers 3 to generate a report of all NetWare Servers that are possible candidates for the software. ZENworks for Servers 3 can generate two different types of inventory reports: simple inventory lists and comprehensive inventory lists. Simple Inventory List Report The report you are likely to use most often is the simple inventory list report. The simple inventory list report enables you to selectively create reports on every aspect of your server by selecting specific criteria that must be matched. Simple inventory list reports are usually generated quickly, so the information you need will be almost instantaneously available. You may want to run several different inventory list reports, shown in Table 13.1, depending on what information you need. Table 13.1. Available Server Inventory List ReportsREPORT NAME | INFORMATION PROVIDED |
|---|
Server Scan Time Listing | Date and time of the last inventory scan on each server. Useful to know how up to date the report is. | Server Operating System Listing | List of all servers with the specified OS version and OS. Essential if you plan to upgrade your servers. | Server BIOS Listing | List of all servers with BIOS release date and the total number of such servers. Essential if your manufacturer releases a BIOS update. | Server Processor Family Listing | List of all servers with a specific processor family. Useful for software upgrades. | Server Processor Current Speed Listing | List of all servers' processor speed. | Server Processor Maximum Clock Speed Listing | List of all servers within a range of processor speed. | Server Video Adapter Listing | List of all servers with a specific video adapter. | Server Network Adapter Listing | List of all servers with a specific network interface card. | Server Software Listing | List of all servers with software installed on them. Listed in order by software. | Software Summary Listing | List of the number of servers with a particular software and version installed on them. | Storage Devices Listings | Lists all fixed and moveable storage devices, floppy disks, and CD-ROMs. | System Information Listing | Generates a list of all machines with system information for each machine. | Device Listing Report | Generates a list of all devices including pointing device, keyboard, bus, display adapter, network adapter, sound adapter, modem, battery, and power supply. | Memory Listing Report | Generates a list of all machines within the specified range of memory and the total number of such machines. |
Comprehensive Inventory Report The other type of inventory report that you will use is the comprehensive inventory report. The comprehensive inventory report combines several aspects of server inventory into each report. Each report takes considerably longer to generate; however, they are more specific and inclusive. You will typically use one of the comprehensive inventory reports listed in Table 13.2 to help you with business and network planning. Table 13.2. Available Comprehensive Inventory ReportsREPORT NAME | INFORMATION PROVIDED |
|---|
Application Software Inventory Report | Includes information on software with product name, version, vendor, product ID, and product location for each inventoried server. | Systems Software Inventory Report | Includes information on the operating system, drivers, and NetWare client for each inventoried server | Storage Devices Inventory Report | Includes hard drive, CD-ROM, floppy disk, removable disk, and logical disk drive details for each server. | Peripherals Inventory Report | Includes system description, OS description, BIOS, video type, video display details, network interface card type, and recent information for each server. | Hardware Inventory Report | Includes conventional memory, extended memory size, processor type and speed, hard drive information, video type, and modem information for each server. | Asset Management Report | Includes computer description, OS description, and BIOS information for each server, including memory, processor, display adapter, keyboard, pointing device, fixed and removable disk, floppy, CD-ROM, and network adapter details. | Networking Information Report | Includes OS description, network interface card type, IP address, MAC address, and network drive mappings for each server. | System Internal Hardware Report | Generates a report providing the system internal hardware information for the selected machines. Includes System IRQ, system cache, system DMA, system slot, and motherboard. | Hardware Summary Report | Generates a report providing hardware summary information of the selected machines. This includes OS type, OS version, processor family, processor maximum clock speed, memory, and hard disk sizes. |
Analyzing Topology Reports ZENworks for Servers 3 can also deliver reports on your network topology. These topology reports provide information about the specific topology of selected ZENworks for Servers 3 management sites or segments. ZENworks for Servers 3 can generate two basic types of topology reports. The first is a site-level report, which provides details about the discovered devices on each segment included in the ZENworks for Servers 3 management site. The second type of report is the segment-level topology report, which enables you to narrow the report down to a specific segment in the ZENworks for Servers 3 management site. NOTE Whenever possible, generate a segment-level topology report rather than a site-level topology report. A site-level report takes considerably longer to generate.
The five predefined topology reports that can be generated by ZENworks for Servers 3 are discussed in the following sections. Computer Systems by Segment Report The Computer Systems by Segment report can be done at a segment level to get only the systems in that segment; however, it is typically used as a comprehensive report to obtain a list of systems at the management site level. The Computer Systems by Segment report lists the following information about each node and groups them by segment: System name. Node name. Use descriptive names for your systems to make these reports more useful. MAC address. Physical address. IP address. IP address of node. Useful to match to captured packets and trend data. IPX address. IPX address of node. Useful to match to captured packets and trend data. Services. Network services running on the node. Manageable services for the computer system. MIB services. MIB services running on the node. Manageable MIB services for the device. Community string. Community string defined for SNMP services. SNMP community names associated with this computer system.
NCP Servers Report When running the NCP Servers report, ZENworks for Servers 3 queries the management site or segment (depending on from where the report was run) and returns the following information for each NetWare Server: Server name. Use descriptive names for your servers to make these reports more useful. MAC address. Physical address. IP address. Useful to match to captured packets and trend data. IPX address. Useful to match to captured packets and trend data. Labels. Other names by which the server is known. MIB services. Manageable MIB services for the device. Services. Manageable services for the computer system. Community strings. SNMP community names associated with reads and writes to the server. report, ZENworks for Servers 3 queries the management
Router Report When running the Router report, ZENworks for Servers 3 queries the management site or segment (depending on from where the report was run) and report, ZENworks for Servers 3 queries the management returns the following information for each router discovered: IPX address. Useful to match to captured packets and trend data. IP address. Useful to match to captured packets and trend data. MAC address. Physical address. Labels. Other names by which the server is known. MIB servers. Manageable MIB services for the device. Services. Manageable services for the computer system. Bound segments. Segments currently bound to the router.
Segment Report When running the Segment report on a management site, ZENworks for Servers 3 queries the management site and lists the number of computer systems on all segments. If this report is run at the segment level, it lists only the systems on the selected segment. The following information is shown for each computer system listed: IPX address. Useful to match to captured packets and trend data. IP address. Useful to match to captured packets and trend data. Segment type. Whether the segment is IP or IPX.
Segment Topology Report The Segment Topology report provides network information about routers and bridges in a ZENworks for Servers 3 management or segment (depending on where the report is run from). The following information is shown for each router listed in the report: Router name. Use descriptive names for your routers to make these reports more useful. MAC address. Physical address. IP address. Useful to match to captured packets and trend data. IPX address. Useful to match to captured packets and trend data. MIB services. Manageable MIB services for the device. Community strings. SNMP community names associated with the router.
The following information is shown for each bridge listed in the report: Bridge name. Use descriptive names for your bridges to make these reports more useful. Bridge type. Type of bridge device. IP address. Useful to match to captured packets and trend data. Number of ports. Number of ports on bridge. This is useful when planning for network growth. Port number (attached address). Useful when troubleshooting software and network problems.
Understanding Network Health Reports Network health reports provide information about the overall health of a specified ZENworks for Servers 3 management site or managed network segment. ZENworks for Servers 3 uses a predefined health profile to generate health reports. These health profiles define the trend parameters, shown in the following tables, that are used to calculate the overall health of the segment or site. Table 13.3 lists trend parameters that are used to calculate the health of managed servers. Table 13.3. Trend Parameters for Managed ServersTREND PARAMETER | AVAILABLE PROFILES |
|---|
AVERAGE_CONNECTIONS | NetWare Server, Windows Server | AVERAGE_DISK_TRANSFER | Windows Server | AVERAGE_FAILED_LOGONS | Windows Server | AVERAGE_LOGGED_IN_USERS | NetWare Server, Windows Server | FILE_READ_KBYTES | NetWare Server, Windows Server | FILE_READS | NetWare Server, Windows Server | FILE_WRITE_KBYTES | NetWare Server, Windows Server | FILE_WRITES | NetWare Server, Windows Server | LSL_IN_PACKETS | NetWare Server | LSL_OUT_PACKETS | NetWare Server | NETWORK_IN_KBYTES | Windows Server | NETWORK_OUT_KBYTES | Windows Server | NETWORK_TOTAL_KBYTES | Windows Server | NCP_REQUESTS | NetWare Server | NO_ECB_COUNT | NetWare Server | OS_PACKETS_RECEIVE_BUFFER | NetWare Server | PERCENT_ALLOCATED_MEMORY | NetWare Server | PERCENT_CACHE_BUFFERS | NetWare Server | PERCENT_CACHE_HIT_RATE | NetWare Server, Windows Server | PERCENT_CODE_AND_DATA_MEMORY | NetWare Server | PERCENT_CPU_UTILIZATION | NetWare Server, Windows Server | PERCENT_DIRTY_PACKET_RECEIVE_BUFFERS | NetWare Server | PERCENT_DISK_FREE_REDIRECTION_AREA | NetWare Server | PERCENT_LOGICAL_DISK_FREE_SPACE | Windows Server | PERCENT_MEMORY_AVAILABLE | Windows Server | PERCENT_VOLUME_FREE_SPACE | NetWare Server | PHYSICAL_INTERFACE_IN_KBYTE | NetWare Server, Windows Server | PHYSICAL_INTERFACE_IN_PACKETS | NetWare Server, Windows Server | PHYSICAL_INTERFACE_OUT_KBYTE | NetWare Server, Windows Server | PHYSICAL_INTERFACE_OUT_PACKETS | NetWare Server, Windows Server | QUEUE_AVERAGE_LENGTH | Windows Server | QUEUE_AVERAGE_NEXT_JOB_WAIT_TIME | NetWare Server | QUEUE_AVERAGE_NUMBER_READY_ITEMS | Windows Server | QUEUE_AVERAGE_NUMBER_READY_JOBS | NetWare Server | QUEUE_AVERAGE_NUMBER_READY_KBYTES | NetWare Server, Windows Server | SERVER_PROCESSES | NetWare Server |
Table 13.4 lists trend parameters that are used to calculate the health of managed networks. Table 13.4. Trend Parameters for Managed NetworksTREND PARAMETER | AVAILABLE PROFILES |
|---|
ABORT_DELIMETERS | Token ring | AC_ERRORS | Token ring | BEACONS | FDDI | BEACON_EVENTS | Token ring | BROADCASTS | Ethernet, token ring, FDDI | BURST_ERRORS | Token ting | CLAIM_TOKENS | Token ring, FDDI | CRC_ERRORS | Ethernet, FDDI | DATA_OCTETS | Token ring | DATA_PACKETS | Token ring | ECHO_PACKETS | FDDI | ELASTICITY_BUFFER_ERRORS | FDDI | ERROR_PACKETS | Ethernet, FDDI | FRAGMENTS | Ethernet | FRAME_COPIED_ERRORS | Token ring | FRAME_NOT_COPIED_COUNT | FDDI | FREQUENCY_ERRORS | Token ring | GOOD_PACKETS | Ethernet | INTERNAL_ERRORS | Token ring | JABBERS | Ethernet | LINE_ERRORS | Token ring | LOST_FRAME_ERRORS | Token ring, FDDI | MAC_OCTETS | Token ring, FDDI | MAC_PACKETS | Token ring, FDDI | MULTICASTS | Ethernet, token ring, FDDI | OVERSIZED_ERRORS | Ethernet, FDDI | PERCENT_UTILIZATION | Ethernet, token ring, FDDI | RECEIVE_CONGESTIONS | Token ring | RING_POLL_FAILURES | Token ring | RING_PURGES | Token ring | RING_WRAPS | FDDI | SMT_OCTETS | FDDI | SMT_PACKETS | Ethernet | TOKEN_ERRORS | Token ring | TOTAL_ERRORS | Token ring | TOTAL_OCTETS | Ethernet, FDDI | TOTAL_PACKETS | Ethernet, FDDI | UNDERSIZED_ERRORS | Ethernet, FDDI | UNICASTS | Ethernet, token ring, FDDI |
The following sections describe the five predefined health profiles provided with ZENworks for Servers 3. NetWare Server Profile The NetWare Server profile is used to monitor and understand the basic health of your NetWare Servers. It provides graphs and data about the following types of trend parameters, listed in Table 13.3, which are used to calculate the overall health of NetWare Servers on the managed site or segment: Cache buffers. Enables you to see the amount of free memory on the server. Low memory is one of the most common symptoms of a sick server. Cache hits. Enables you to see memory usage to troubleshoot overaggressive applications. CPU utilization. Enables you to see how hard the server processor is being worked. High utilization for extended periods can lead to server health problems. Watching the server's utilization can help you strategically plan for network growth in overused areas. Volume free space. Enables you to monitor available disk space on each volume. Low disk space, especially on the SYS volume, often causes server and application problems.
Microsoft Windows Profile ZENworks for Servers 3 uses the Microsoft Windows profile to generate reports that monitor the basic health of your Microsoft Windows servers. It provides graphs and data about the following types of trend parameters, listed in Table 13.3, which are used to calculate the overall health of Microsoft Windows servers on the managed site or segment: Available memory. Enables you to see the amount of free memory on the Windows Server. Low memory is one of the most common symptoms of a sick server. Cache hits. Enables you to see memory usage to troubleshoot overaggressive Windows applications. CPU utilization. Enables you to see how hard the Windows Server processor is being worked. High utilization for extended periods can lead to server health problems. Watching the Microsoft Windows Server's utilization can help you strategically plan for network growth in overused areas. Disk free space. Enables you to monitor available disk space on each disk. Low disk space, especially on the Windows drive, often causes Windows Server and application problems. A health report is generated for this parameter, but no trend graph.
Ethernet Network Profile The Ethernet network profile is used to monitor and understand the basic health of your network. It provides graphs and data about the following types of trend parameters, listed earlier in Table 13.4, which are used to calculate the overall health of your ethernet network on the managed site or segment: Total errors. Enables you to see the number of network errors occurring on your managed site or segment. This helps you troubleshoot problem networks. Network utilization. Enables you to see the current usage of your ethernet networks. This can help you understand which segments are being overused and help you plan for future expansion. Total packets. Enables you to monitor the packets being sent on your managed ethernet networks. A health report is generated for this parameter, but no trend graph. Good packets. Enables you to see the good packets that are being sent on your managed ethernet networks. Combined with the total packets, this can help you troubleshoot network problems and overuse. A health report is generated for this parameter, but no trend graph.
Token Ring Network Profile The token ring network profile is used to monitor and understand the basic health of your token ring network. It provides graphs and data about the following types of trend parameters, listed earlier in Table 13.4, which are used to calculate the overall health of your token ring network on the managed site or segment: Total errors. Enables you to see the number of token ring network errors occurring on your managed site or segment. This helps you troubleshoot problems on your token ring networks. Network utilization. Enables you to see the current usage of your token ring networks. This can help you understand which segments are being overused and help you plan for future expansion.
FDDI Network Profile Lastly, the FDDI network profile is used to monitor and understand the basic health of your FDDI network. It provides graphs and data about the following types of trend parameters, listed earlier in Table 13.4, which are used to calculate the overall health of your FDDI network on the managed site or segment: Total errors. Enables you to see the number of FDDI network errors occurring on your managed site or segment. This helps you troubleshoot problems on your FDDI networks. Network utilization. Enables you to see the current usage of your FDDI networks. This can help you understand which segments are being overused and help you plan for future expansion. Total packets. Enables you to monitor the total packets being sent on your managed FDDI networks. A health report is generated for this parameter, but no trend graph.
Appreciating Tiered Electronic Distribution Reports Tiered Electronic Distribution (TED) is an extremely valuable tool for delivering data from server to server across the network. For this reason, ZENworks for Servers 3 includes several reports, discussed in the following sections, that enable you to view the status and history of data distribution through the TED system. Detailed Reports ZENworks for Servers 3 enables you to create Detailed reports for data distribution at both the distribution and subscriber levels. These reports can be used to understand distribution processes that have occurred and that are occurring on your network. The Detailed reports contain the following statistical information about data distributions on the TED distributors and subscribers: Stage. The current stage of the distribution, which will be either the extract or receive stage. Status. Successful or not successful on the receiving of or extraction of the distribution. Date/time. The date and time the distribution was received on the subscriber. Acting process. The agent that is to extract the distribution. Channel. The name of the channel that contained the distribution. Error description. Description of the error associated with the distribution, traditionally at the subscriber side.
History Reports ZENworks for Servers 3 also creates Revision History reports. These reports help you understand the revisions of data distributions that have occurred on your network. For example, each time you use TED to distribute a new version of software on your network, it would have a new revision. Therefore, you can track successful and unsuccessful software distributions. There are two Revision History reports. The first report is for normal distribution. The second report is for failed distributions. The Revision History reports contain the following statistical information about data distributions on the TED distributors: Version. Revision number of the distribution package. Creation date/time. The date and time that the distributor created the distribution package. Size of distribution. The size of the distribution file that contains the compressed combination of files for the particular revision (only on regular report). Distribution error. Description of the error that the distribution experienced (only on failure report).
|
