Concord systemEDGE Agent (5012) - CA...

Concord systemEDGE Agent

Device Management

Supports Management Module SM-EMP1000

D e v i c e M a n a g e m e n t Page 2 C o n c o r d s y s t e m E D G E A g e n t

Copyright NoticeDocument 5021. Copyright © 2002-present by Aprisma Management Technologies, Inc. All rights reserved worldwide. Use, duplication, or disclosure by the United States government is subject to the restrictions set forth in DFARS 252.227-7013(c)(1)(ii) and FAR 52.227-19.Liability DisclaimerAprisma Management Technologies, Inc. (“Aprisma”) reserves the right to make changes in specifications and other information contained in this document without prior notice. In all cases, the reader should contact Aprisma to inquire if any changes have been made.

The hardware, firmware, or software described in this manual is subject to change without notice.

IN NO EVENT SHALL APRISMA, ITS EMPLOYEES, OFFICERS, DIRECTORS, AGENTS, OR AFFILIATES BE LIABLE FOR ANY INCIDENTAL, INDIRECT, SPECIAL, OR CONSEQUENTIAL DAMAGES WHATSOEVER (INCLUDING BUT NOT LIMITED TO LOST PROFITS) ARISING OUT OF OR RELATED TO THIS MANUAL OR THE INFORMATION CONTAINED IN IT, EVEN IF APRISMA HAS BEEN ADVISED OF, HAS KNOWN, OR SHOULD HAVE KNOWN, THE POSSIBILITY OF SUCH DAMAGES.

Trademark, Service Mark, and Logo InformationSPECTRUM, IMT, and the SPECTRUM IMT/VNM logo are registered trademarks of Aprisma Management Technologies, Inc., or its affiliates. APRISMA, APRISMA MANAGEMENT TECHNOLOGIES, the APRISMA MANAGEMENT TECHNOLOGIES logo, MANAGE WHAT MATTERS, DCM, VNM, SpectroGRAPH, SpectroSERVER, Inductive Modeling Technology, Device Communications Manager, SPECTRUM Security Manager, and Virtual Network Machine are unregistered trademarks of Aprisma Management Technologies, Inc., or its affiliates. For a complete list of Aprisma trademarks, service marks, and trade names, go tohttp://www.aprisma.com/manuals/trademark-list.htm.

All referenced trademarks, service marks, and trade names identified in this document, whether registered or unregistered, are the intellectual property of their respective owners. No rights are granted by Aprisma Management Technologies, Inc., to use such marks, whether by implication, estoppel, or otherwise. If you have comments or concerns

about trademark or copyright references, please send an e-mail to [email protected]; we will do our best to help.

Restricted Rights Notice(Applicable to licenses to the United States government only.)This software and/or user documentation is/are provided with RESTRICTED AND LIMITED RIGHTS. Use, duplication, or disclosure by the government is subject to restrictions as set forth in FAR 52.227-14 (June 1987) Alternate III(g)(3) (June 1987), FAR 52.227-19 (June 1987), or DFARS 52.227-7013(c)(1)(ii) (June 1988), and/or in similar or successor clauses in the FAR or DFARS, or in the DOD or NASA FAR Supplement, as applicable. Contractor/manufacturer is Aprisma Management Technologies, Inc. In the event the government seeks to obtain the software pursuant to standard commercial practice, this software agreement, instead of the noted regulatory clauses, shall control the terms of the government's license.Virus DisclaimerAprisma makes no representations or warranties to the effect that the licensed software is virus-free.

Aprisma has tested its software with current virus-checking technologies. However, because no antivirus system is 100 percent effective, we strongly recommend that you write-protect the licensed software and verify (with an antivirus system in which you have confidence) that the licensed software, prior to installation, is virus-free.

Contact InformationAprisma Management Technologies, Inc.273 Corporate DrivePortsmouth, NH 03801Phone: 603-334-2100U.S. toll-free: 877-468-1448Web site: http://www.aprisma.com

http://www.aprisma.com/manuals/trademark-list.htm

http://www.aprisma.com


ContentsINTRODUCTION 5

Purpose and Scope ........................................................5Required Reading ...........................................................5Supported Devices..........................................................6The SPECTRUM Model ..................................................6

TASKS 8

DEVICE VIEW 9

Interface Icons ..............................................................10Interface Icon Subviews Menu......................................11Interface Status View ....................................................12Secondary Address Panel ............................................12

DEVICE TOPOLOGY VIEW 13

APPLICATION VIEWS 14

Main Application View...................................................14Supported Applications .................................................15

Common Applications................................................15Device-Specific Applications .....................................16

RFC 2790 Application ...................................................16

PERFORMANCE VIEWS 18

CONFIGURATION VIEWS 19

Device Configuration View............................................ 19

HOST SYSTEM HEALTH 21

CPU Health Information View ....................................... 21CPU Statistics Table.............................................. 22

OS Information View..................................................... 23Boot Information View ............................................... 24Group Table .............................................................. 24History Table ............................................................. 25Kernel Information View ............................................ 25Log Monitor Table View............................................. 27Monitor Table View.................................................... 28NT Event Monitor View.............................................. 31Process Monitor Table .............................................. 32Process Table ........................................................... 34User Table................................................................. 36Who Table ................................................................. 37

Host Memory Information View..................................... 37Shared Memory Table............................................... 37I/O Buffer Information View ....................................... 38Directory Name Lookup Cache Group View ............. 39NT Information View.................................................. 39

FileSystem Information View ........................................ 41Disk Statistics Table .............................................. 41

Client NFS Information View ..................................... 42


Server NFS Information.............................................44RPC Information ........................................................46

Client Information Calls ......................................47Server Information Calls .....................................47

Top Process View......................................................48Queue Messages View..............................................49NT Thread Table View...............................................49NT Service Table View..............................................50

Host Performance View ................................................51System Performance View ........................................51

Total Time (in centiseconds) ..............................51Read...................................................................51Write ...................................................................52File Information...................................................52

Cache Performance View..........................................53Asynchronous.....................................................53Data....................................................................53Synchronous ......................................................53Fast Read...........................................................54Lazy Write ..........................................................54MDL Read ..........................................................55Copy Read .........................................................55Pin Read.............................................................55

Memory Performance View .......................................55Page ...................................................................56Pool ....................................................................56System ...............................................................57

Unix Kernal View .......................................................57CPU....................................................................57Load ...................................................................58

SWAP ................................................................ 58Memory.............................................................. 59Page Info ........................................................... 60Process.............................................................. 61

Page File Performance View .................................... 62

MODEL INFORMATION VIEW 63

TRAPS, EVENTS, AND ALARMS 64

Standard Trap Support ................................................. 64Device-Specific Trap Support....................................... 64

INDEX 70


Introduction

This section introduces the SPECTRUM Device Management documentation for Concord systemEDGE Agent.

This introduction contains the following topics:

• Purpose and Scope

• Required Reading

• Supported Devices (Page 6)

• The SPECTRUM Model (Page 6)

Purpose and ScopeUse this document as a guide for managing the Concord systemEDGE (formerly Empire) devices described on Page 6 with SPECTRUM management module SM-EMP1000. This document describes the icons, menus, and views that enable you to remotely monitor, configure, and troubleshoot Concord systemEDGE Agent devices through software models in your SPECTRUM database.

Information specific to SM-EMP1000 is what is primarily included in this document. For general information about device management using SPECTRUM and explanations of SPECTRUM

functionality and navigation techniques, refer to the topics listed under Required Reading.

Required ReadingTo use this documentation effectively, you must be familiar with the information covered by the other SPECTRUM online documents listed below.

• Getting Started with SPECTRUM for Operators

• Getting Started with SPECTRUM for Administrators

• How to Manage Your Network with SPECTRUM

• SPECTRUM Views

• SPECTRUM Menus

• SPECTRUM Icons

• SPECTRUM Software Release Notice


Supported DevicesSPECTRUM management module SM-EMP1000 currently lets you model the Concord systemEDGE Agent (formerly the Empire Agent)that runs on NT or Unix systems. Concord systemEDGE Agent provides application-specific information for NT and Unix Concord systemEDGE Agents.

The SPECTRUM ModelThe model types for the Concord systemEDGE Agent devices are Host_systemEDGE (formerly Host_Empire).

Modeling results in the creation of Device icons that represent the Concord systemEDGE Agent and Application icons that represent their supported applications.

The Device icons contain double-click zones and provide access to Icon Subviews menus that let you perform device management activities such as those listed in Tasks on Page 8.

Figure 1 shows a sample Concord systemEDGE Agent device icon.

Figure 1: Device Icon


The device-specific Icon Subviews menu options available from the Device icon are listed below.

The rest of this document covering the Concord systemEDGE Agent management module is organized as follows.

• Tasks (Page 8)

• Device View (Page 9)

• Device Topology View (Page 13)

• Application Views (Page 14)

• Performance Views (Page 18)

• Configuration Views (Page 19)

• Host System Health (Page 21)

• Model Information View (Page 63)

• Traps, Events, and Alarms (Page 64)

Option Accesses the...

Device Device View (Page 9)

DevTop Device Topology View (Page 13)

Application Application Views (Page 14)

Configuration Configuration Views (Page 19)

Fault Management

For further information refer to the How to Manage Your Network with SPECTRUM documentation.

Host System Health

Host System Health (Page 21)

Model Information

Model Information View (Page 63)

Primary Application

Menu options that let you select either Gen Bridge App or MIB-II as the primary application.


Tasks

This section contains an alphabetical list of device management tasks, with each task providing one or more links to views that let you perform the task.

Administrative Information (check)• Model Information View (Page 63)

Alarm Thresholds (set)• Interface Icon Subviews Menu (Page 11)

CPU Statistics (check)• CPU Statistics Table (Page 22)

Configuration Information (check)• Configuration Views (Page 19)

IP Address (find/change)• Device View (Page 9)• Secondary Address Panel (Page 12)

Memory Information (check)• Host Memory Information View (Page 37)

NT Information (check)• NT Event Monitor View (Page 31)

• NT Information View (Page 39)• NT Thread Table View (Page 49)• NT Service Table View (Page 50)

Network Type (check)• Network Type Label (Page 11)

Operating System Information (check/change)

• Host System Health (Page 21)• OS Information View (Page 23)

Performance (check)• Device View (Page 9)• Interface Icons (Page 10)• Performance Views (Page 18)• Host Performance View (Page 51)

Topology (check)• Device Topology View (Page 13)


Device View

This section describes the Device view and subviews available for models of Concord systemEDGE Agent devices in SPECTRUM.

Access: From the Icon Subviews menu for the Device icon, select Device.

This view (Figure 2) uses icons and labels to represent the device and its components, such as modules, ports, and applications. The view provides dynamic configuration and performance information for each of the device’s serial and network I/O ports, which are represented by Interface icons in the bottom panel of the view. The middle panel of the view displays a Device icon, which lets you monitor the device operation and access other device-specific views.

Figure 2: Device View

SpectroGRAPH: Router Device: Model Name

File View HelpTools

Model NameContactDescriptionLocation

Sys Up TimeManufacturerDevice TypeSerial Number

Network Address

Interface Description

Filter Physical

Interface Options PanelDevice Icon

Model Name

1Ethernet

0:0:1D:F:FD:B6

ei0

0.0.0.0

ON

5SFTWARLPBK

0:0:1D:F:FD:B6

lo0

0.0.0.0

ON

9ATM8023

0:0:1D:F:FD:B6

zn1

0.0.0.0

ON

512AAL5

UAAL5

0.0.0.0

ON

2ATMCPU

0.0.0.0

ON

6ATM portCPU.1

0.0.0.0

ON

ATM7A1

0.0.0.0

ON

ATM7B1

0.0.0.0

ON

ATM7B2

0.0.0.0

ON

ATM7B3

0.0.0.0

ON

ATM8B1

0.0.0.0

ON

ATM8B2

0.0.0.0

ON

ATM8B3

0.0.0.0

ON

ATM8B4

0.0.0.0

ON

10

2783905 2783909

11

7

3 4

8

Interface Icons

Bookmarks

Primary Application Gen Bridge App


Interface IconsFigure 3 shows a close-up of an Interface icon from the Device view. Most of the informational labels on the icon also provide double-click access to other views, as explained in the following label descriptions.

Figure 3: Interface Icon

Interface Number LabelThis label displays the interface (port) number.

IF Status LabelThis label displays the current status of the interface for the primary application selected, e.g., Gen Rtr App or MIB-II App. Table 1 lists the possible label color representations. Note that the color of the label also depends on the interface’s current Administrative Status, which you set in the (Page 11). This view can be accessed by double-clicking the label.

Interface Type LabelThis label identifies the interface type (Ethernet, ATM, etc.). Double-click this label to access the Interface Configuration view. See the SPECTRUM Views documentation.

c

f

b

1ethernet

0:0:1D:F:FD:B6

a

a Interface Number Label

b IF Status Label

c Interface Type Label

d Network Type Label

e Physical Address Label

f IP Address Label

fxp0

0.0.0.0

d

e

ON Table 1: Interface Status Label Colors

Color OperationalStatus

AdministrativeStatus

LabelText

Green up up ON

Blue down down OFF

Yellow down up OFF

Red testing testing TEST


Network Type LabelThis label identifies the type of network to which the interface is connected. Double-click the label to open the Model Information view for the interface.

Physical Address LabelThis label displays the physical (MAC) address of the interface. Double-click this label to open the Address Translation Table (AT).

IP Address LabelThis label displays the IP address for the interface. Double-click this label to open the Secondary Address Panel (Page 12), which lets you change the address and mask for the interface.

Interface Icon Subviews MenuTable 2 lists the device-specific interface Icon Subviews menu options and the views to which they provide access.

Table 2: Interface Icon Subviews Menu

Option Accesses the...

Detail Interface Detail view, which displays packet, error, and discard breakdown statistics for the interface.

IF Status Interface Status View (Page 12).

IF Configuration Interface Configuration view (see SPECTRUM Views).

Address Translation Table

Address Translation Table (AT) (see SPECTRUM Views).

Secondary Address Panel

Secondary Address Panel (Page 12).

Thresholds Interface Threshold view, which lets you set the on/off alarm thresholds for load, packet rate, error rate, and % discarded for the interface.

Model Information

Model Information View (Page 63).


Interface Status ViewAccess: From the Icon Subviews menu for the Interface icon in the Device view, select IF Status.

This view provides information on the operational status of the interface and allows you to enable or disable the port.

Operational StatusThe current state of the interface (Up, Down, Unknown, Dormant, Not Present, Lower Layer Down, or Testing).

This button allows you to select the desired administrative state of the interface (On, Off, or Testing).

Secondary Address PanelAccess: From the Icon Subviews menu for the Interface icon in the Device view, select Secondary Address Panel.

This panel provides a table of IP addresses and masks obtained from the Address Translation table within the device’s firmware. You can change the current address displayed in the IP Address field by selecting an entry from the table in this panel and clicking the Update button.

Administrative Status


Device Topology View

This section describes the Device Topology view available for models of the Concord systemEDGE Agent devices.

Access: From the Icon Subviews menu for the Device icon, select Device Topology.

The Device Topology view (Figure 4) shows the connections between a modeled device and other network entities. The lower panel of the view uses Interface icons to represent the device’s serial, network, and I/O ports. These icons provide the same information and menu options as those in the Device View (Page 9). If a device is connected to a particular interface, a Device icon appears on the vertical bar above the Interface icon along with an icon representing the network group that contains the device.

Refer to the SPECTRUM Views documentation for details on Device Topology view.

Figure 4: Device Topology View

File View HelpTools

1Ethernet

0:0:1D:F:FD:B6ei0

0.0.0.0

ON 2ATM

0:0:1D:F:FD:B6A2

0.0.0.0

ON 3ATM

0:0:1D:F:FD:B6CPU

0.0.0.0

ON

Model Name

Bookmarks

SpectroGRAPH: Device Topology: Model Name


Application Views

This section describes the main Application view and the associated application-specific subviews available for models of Concord systemEDGE Agent devices in SPECTRUM.

Access: From the Icon Subviews menu for the Device icon, select Application.

Main Application ViewWhen a device model is created, SPECTRUM automatically creates models for each of the major and minor applications supported by the device. The main Application view identifies all of these application models, shows their current condition status, and provides access to application-specific subviews. Figure 5 shows this view in the Icon mode. If you prefer the List mode, which displays applications as text labels, select View > Mode > List.

For more information on this view, refer to the MIBs and the Application View documentation.

Figure 5: Main Application View

Model Name

Contact

Description

Location

Network Address System Up Time

Manufacturer

Device Type

Serial Number

Model Name

6E132_25

Model Name

Empire_UnixAp

File View Tools Bookmarks Help


Supported ApplicationsSPECTRUM’s applications can be grouped within two general categories as follows:

• Common Applications, below• Device-Specific Applications (Page 16)

Common ApplicationsFor the most part, these applications represent the non proprietary MIBs supported by your device. Listed below (beneath the title of the document that describes them) are some of the common applications currently supported by SPECTRUM.

• Routing Applications- Generic Routing- Repeater- AppleTalk- DECnet- OSPF- OSPF2

- BGP4- VRRP

- RFC 2932

• Bridging Applications- Ethernet Special Database- Spanning Tree- Static- Transparent- PPP Bridging- Source Routing- Translation- QBridge

• MIB II Applications- SNMP- IP- ICMP- TCP- System2- UDP

• Transmission Applications- FDDI- Point to Point- DS1- DS2- RS-232

Note:Note:

The documents listed are available for viewing at:

www.aprisma.com/manuals

http://www.aprisma.com/manuals


- WAN- Frame Relay- DS3- Token Ring- Ethernet- Fast Ethernet- RFC 1317App- RFC 285App- RFC 1315App- 802.11App- SONET

• Technology Applications- APPN- ATM Client- DHCP- DLSw- PNNI- RFC 1316App- RFC 1514- RFC 2287- RFC 2790- RFC 2925

• DOCSIS Applications- DOCSISCblDvApp - DOCSISQOSApp- DOCSISBPI2App - DOCSISBPIApp

- DOCSISIFApp

• Digital Subscriber Line (DSL) Applications- ADSL

Device-Specific ApplicationsSPECTRUM imports the following device-level proprietary MIBs into its database:

• empire.asni1• hostMIB.asni1

These MIBs can be used in conjunction with SPECTRUM’s optional customization products (referred to as the Level I Tool Kits) to create application models and views that display the condition of selected MIB fields.

RFC 2790 Application This application allows you to manage host systems and obsoletes the RFC1514 Application. For further information on this improved Host

Note:Note:

Aprisma Management Technologies can provide training, technical assistance, and custom engineering support services for creating application models and their associated views.


application, see the Technology Applications documentation.


Performance Views

This section introduces the Performance view. For details concerning this view, refer to the SPECTRUM Views documentation.

Performance views display performance statistics in terms of a set of transmission attributes, e.g., cell rates, frame rates, % error, etc. A typical view is shown in Figure 6. The instantaneous condition of each transmission attribute is recorded in a graph. The statistical information for each attribute is presented in the adjacent table.

Generally, you determine performance at the device level through Performance views accessed from the Device and Application icons. You determine performance at the port/interface level through Performance views accessed from Interface icons.

Figure 6: Performance View

Model Name

Contact

Description

Location

Network Address System Up Time

Manufacturer

Device Type

Serial Number

Log

100.0

10.00

1.00

0.10

0.01

000:40:0 0:30:0 0:20:0

Value Average Peak Value

* Frame Rate

% Delivered

% Forwarded

% Transmit

% Error

DetailGraph Properties Scroll to Date-Time

File View Tools Bookmarks

% Discarded*Frames per second

type routing of type IP Routing of Landscape node: Primary

Primary Application


Configuration Views

This section describes the Configuration views available for models of the Concord systemEDGE Agent devices in SPECTRUM.

Configuration views let you see and modify current settings for the modeled device and its interfaces, ports, and applications. The following Configuration views are available for models of Concord systemEDGEdevices:

• Device Configuration View (Page 19)

Device Configuration ViewAccess: From the Icon Subviews menu for the Device icon, select Configuration.

A typical Device Configuration view is shown in Figure 7. Generally, this view includes a few fields that display device information as well as an Interface Configuration Table that lists interface parameters, some of which can be changed (see SPECTRUM Views). Some Device Configuration views include one or more buttons that provide access to device-specific configuration information. These are described below.

Figure 7: Device Configuration View

SpectroGRAPH: Model Name

Model Name


DescriptionLocation

ContactManufacturerSys Up Time

Net Address

Device Type

Serial Number

Configuration View

Contact Status Number of Interfaces

Interface Address Table

Sort Interface Configuration Table

Index Description Type Bandwidth Physical Addre

IP Address of type Model of Landsape: Primary

Find Update


Refer to the SPECTRUM Views documentation.

IF Address Translation


Host System Health

This view provides details about the Operating System on which devices of Concord systemEDGEHost are running.

Host System Health views let you see and modify OS specific information that pertains to Concord systemEDGEHost Devices. Each view also provides button access to either NT or Unix specific views. The following Host System Health views are available:

• CPU Health Information View (Page 21).• OS Information View (Page 23)• Host Memory Information View (Page 37)• FileSystem Information View (Page 41)• Host Performance View (Page 51)

CPU Health Information ViewAccess: From the Icon Subviews menu for the Device icon, select Host System Health > CPU.

The following information is available.

Times IdleThe total number of ticks spent by this CPU in Idle mode.

Times Idle %The percentage of time (over the sample period) that the system's CPU was idle.

System ModeThe total number of ticks spent by this CPU in Kernel or system mode. This value may wrap a 32-bit counter.

System User %The percentage of time (over the sample period) that the system's CPU was executing in user mode.

Note:Note:

Plugins such as Top Processes are not loaded by the agent by default. The user will need to configure the agent appropriately to enable the SystemEDGE Agent to load the plugins. Refer to the SystemEDGE Agent User Guide for information on how to configure the agent.


User ModeThe total number of ticks spent by this User on this OS.

User Mode %The percentage of time this User has spent in this mode.

Time of Last Update The time (based on sysUpTime) that the log file was last modified by the system or application(s) writing to this file. Monitoring this value can indicate if the system or application(s) that log to this file are active.

CPU Statistics TableThis view also provides you with the CPU Statistics Table that provides per-cpu statistics and counters; the agent periodically (approximately every 60 seconds) updates data contained in this table. By periodically sampling entries in this table, one can determine the percentage of time spent by each CPU in their respective modes. This percentage can be calculated by summing the total ticks spent in each mode and then dividing the ticks spent in each mode by the total. Ticks is a system-dependent quantity whose unit is not necessary when calculating the percentage of time spent in each CPU mode.

This table contains the following information:

IndexAn index that uniquely identifies an entry in the counter.

DescriptionThe type of CPU for which statistics are reported. On Solaris 2.x, this description also includes the CPU's clock speed.

IdleThe total number of ticks spent by this CPU in Idle mode. This value may wrap 32-bit counter.

UserThe total number of ticks spent by this CPU in Idle mode. This value may wrap 32-bit counter.

Last UpdateThe last time this table was updated.

Idle %The percentage of ticks spent by this CPU in idle time.

User %The percentage of total ticks spent by this CPU under the current user.

System %The percentage of total ticks spent running by this system.


OS Information ViewAccess: From the Icon Subviews menu for the Device icon, select Host System Health > System.

This view provides general system and network configuration information. This view also provides you with button access to certain Unix or NT specific information. Only the buttons available for your system will be available in this view.

This view provides the following information.

Node The name of the system that the agent is running on as given by the login prompt.

MemoryThe amount of memory in 1024 byte units contained in the system.

CPUThe CPU type of the system that the agent is running on (e.g., sun4c, sun4m).

OS ReleaseThe operating system release of the system that the agent resides (e.g., 4.1.3).

Agent VersionThe version type of the Concord systemEDGE Agent.

OS VersionThe operating system version of the system that the agent resides (e.g., 7). Each time a new kernel is re-linked for a given kernel configuration file, this number is incremented.

System TypeThe type of system currently used to view the Concord systemEDGE Agent.

System Edge TimeThe total number of tick this CPU has spent in edge mode.

System Edge ModeDisplays whether this system is running in edge mode or not.

License StringThe License string operating on this device.

The following views are accessed with buttons:

• Boot Information View (Page 24)• Group Table (Page 24)• History Table (Page 25)• Kernel Information View (Page 25)• Log Monitor Table View (Page 27)• Monitor Table View (Page 28)• NT Event Monitor View (Page 31)• Process Monitor Table (Page 32)


• Process Table (Page 34)• User Table (Page 36)• Who Table (Page 37)

Boot Information ViewAccess: From the OS Information view click on the Boot Information button.

This view identifies Sun device and partition information on the root, dump, and swap file systems.

This view provides the following information:

Root NameThe name of the device and partition on which the root file system is mounted.

Root FS TypeThe root file system type (for example, 4.2).

# Block/Root FSThe total number of blocks contained in the root file system. A value of zero is returned if the number is unknown.

Dump NameThe name of the device and partition that the dump file system is mounted from. Dump is an

area of secondary storage reserved by the operating system so that it may write diagnostic information in the event of a kernel crash.

Dump FS TypeThe dump file system type (for example, spec).

# Blocks/Dump FSThe total number of blocks contained in the dump file system.

Swap NameThe name of the device and partition that serves as swap space for the running kernel.

Swap FS TypeThe swap file system type (for example, spec).

Swap SizeThe total number of blocks contained in the kernel’s swap area.

Group TableAccess: From the OS Information view click the Group Table button.

This table lists the following information about groups of users who can log on to the workstation.


IndexThe instance of this entry derived from its index in the groups file.

NameThe name of the group (e.g., Marketing).

PasswordThe encrypted password for the group. Groups without passwords have an “*” in this field.

GIDThe group ID.

History TableAccess: From the OS Information view click on the History Table button.

This view provides the following historical data.

Index The history of which this entry is a part. This value identifies a row in the History Control Table of which this sample is a part.

Sample IndexAn index that uniquely identifies the particular sample this entry represents among all samples associated with the same history control entry. This index starts at 1 and increases by one as each new sample is taken.

Start TimeThe value of sysUpTime at which the first sample was taken.

Sample TimeThe value of sysUpTime at which this particular sample was taken.

ValueThe value of this sample.

Kernel Information ViewAccess: From the OS Information view click on the Kernal Information button.

This view provides the following kernel configuration and identification information.

Serial NumberThe serial number of the system the agent is running on as given by the login prompt.

Number CPUsThe number of CPUs contained in this host.

Clock Rate (Hz)The system’s clock or tick rate in Hertz, which is used by the operating system in handling I/O, process scheduling, etc.


Posix VersionThe POSIX version number supported by the host operating system. It is important to monitor which host supports which version of the POSIX standard when new POSIX versions are released.

Posix Job ControlA boolean variable that indicates whether the system supports POSIX-style job control.

Total Swap SpaceThe total system swap space in KBytes.

Virtual MemoryThe amount of virtual memory in 1024-byte units (KBytes).

Kernel VersionThe kernel version; this description string is compiled into the kernel at kernel build time and is generally used to convey information about its functionality, patch level, or administrative domain.

Rom VersionThe system’s ROM version number. Different versions of ROM often support different commands and options. Knowing the system’s ROM version is helpful in debugging system problems.

Page SizeThe number of bytes in a page. A “page” is the fixed size unit of measurement associated to virtual and physical memory; however, it may not correspond to the underlying hardware page size.

Max InodesThe maximum number of in-core file Inodes allocated by this host. An Inode is a data structure used by a file system to describe a file. Part of it is cached in memory (in core) while the other is stored on disk. The kernel allocates a fixed amount of these structures at kernel boot time for use with file I/O.

Max ProcessesThe maximum number of processes that may run at any one time on the system.

Max FilesThe maximum number of open files the system can support at any one time. The kernel pre-allocates a table of structures for file I/O at kernel boot time.

Max Open Files/ProcessThe maximum number of open files per process. Each process is generally given a limit on the maximum number of files it may have open at any time. If the operating system does not set such limits, the value of zero is returned.


Max Memory/ProcessThe maximum memory per process in KBytes. Operating systems often set an upper limit on the amount of memory a process may use. If the operating system does not set such a limit, the value of zero is returned.

Max C ListThe maximum number of clist structures allocated by the kernel. Line disciplines, like terminals, manipulate data on clists which are essentially linked-lists of data heading to and from terminal or serial devices. If the underlying operating system does not utilize clists, then 0 is returned.

Log Monitor Table ViewAccess: From the OS Information view click on the Log Monitor Button.

This table contains log monitor entries; each entry specifies a log file and regular expression. The agent periodically stats the log files to see if they have been updated. If updated, the agent scans the new entries for the regular expression. When that regular expression is found (or matched) in the new entries, a trap PDU is sent to appropriate managers.


IndexAn index that uniquely identifies an entry in the Log Monitor Table.

LogFileThe name of the log file to scan for pattern matches. This variable must name a valid log filename.

RegularExpressionThe display string representation of the regular expression to match in the corresponding log file.

NumTrapsThe number of traps sent by the agent on behalf of this entry. One trap PDU message is sent for each match the agent detects in the corresponding log file.

LastTrapThe time (based on sysUpTime) at which the agent last sent a trap for this entry. Alternatively, it is the time at which the last pattern match occurred.

LastMatchThe last log file entry that matched the Log Monitor RegularExpression field. Each time a match occurs, this variable is updated.


StatusThe status of this entry. This variable is equivalent in semantics to the V2 SMI RowStatus textual-convention (see RFC 1443). A value of active indicates that the agent is currently monitoring and evaluating the current row. A value of notInService indicates that the agent has suspended evaluation of the row. Setting this field to destroy causes the agent to suspend evaluation of its row and free its resources. For row creation to occur, the manager must supply active, createAndGo, createAndWait, or notInService as the value of this object. If an error occurs at any time during the processing of a particular Monitor Table entry, its Status column will be set to notReady.

LogFileSizeThe size in bytes of the log file at time of last sample. By querying this value, one can tell if the log file is growing.

LogFileLastUpdateThe time (based on sysUpTime) that the log file was last modifed by the system or application(s) writing to this file. Monitoring this value can indicate if the system or application(s) that log to this file are active.

DescriptionA textual description of this entry possibly identifying the purpose of this entry and who created it.

ActionsA textual string specifying the command to be executed upon finding a match.

FlagsThe flags field dictates the behavior of each logMonitorEntry. Each bit in the integer represents the toggling of an option. The flags field of 0x00 is enables default behavior. Logical ordering together of different bits allows one to combine different options.

Monitor Table ViewAccess: From the OS Information view click the Monitor Table View.

Each entry in the Monitor table represents a single variable or function that the agent is monitoring. Variables are those field in the MIB for which the agent is tracking. Likewise, functions that the agent are calling periodically as part of its internal implementation are available for manipulation via this table.



IndexA unique value for entry in the Monitor table. The index values in the Monitor table may not necessarily be contiguous, but are unique.


IntervalThe interval, in seconds, between successive samples by the agent. It must be a multiple of 30 seconds. For example, if a manager wanted to sample the value of a particular variable every 30 seconds, then setting monInterval to 30 would instruct the agent to sample once very 30 seconds. The sampling period is not exact but represents a best-effort by the agent.

SampleTypeThe type of sampling performed on the field represented by this entry. For example, for sampling and monitoring fields of type Counter, setting the appropriate SampleType to deltaValue causes the agent to measure/sample the rate of change in the variable rather than the absolute value. For gauge and gauge-like variables, absoluteValue makes more sense. The agent does not perform sanity checks on this variable against the type of field being monitoring

because there may exist some case where a manage may actually wish to monitor the absolute value of a counter or the delta value of a gauge.

OIDThe object identifier (including properly formed instance) of the variable being monitoring by this entry. For example, if a manager wanted to monitor the number of packets received on a particular network interface, that manager would write the field identifier corresponding to the appropriate counter. During row creation, the agent ensures that the field identifier is valid. If invalid, the agent returns BadValue. This variable can represent both scalar and tabular objects as well. If, at any point during the row's lifetime, the variable no longer exists in the agent's MIB, the row's status is set to notInService.

CurrvalThis variable represents the current value of the object being monitored as last sampled by the agent. If the SampleType is deltaValue, then this value represents the difference between two successive samples. If monSampleType is absoluteValue, then this value represents the actual sampled value.


OperatorThe boolean operator performed in the expression: CurrVal, Operator Value. For example, to monitor a value so that an alarm is generated when its value rises about 100, the expression: currValue gt 100 could be used. Likewise, currValue ge 101 could also be used. The value of nop causes the agent to perform no boolean comparison; it is useful when a manager wishes that an agent track the value of some field but not perform any evaluation of its value.

ValueThe value against which the agent compares the current value. This value represents a threshold. Its semantics are not interpreted by the agent; therefore, the manager is responsible for determining if this value 'makes sense'.

LastCallThe time (based on sysUpTime) at which the agent last called or sampled the field being monitored. If the field has not yet been sampled, 0 is returned.

NumTrapsThe number of traps sent for this particular monitor entry. This value indicates how many times the agent has evaluated this entry's expression as true. Because this value depends on the semantics of the variable, the entry's

sampling interval (monInterval), and the interval at which the monitoring table is evaluated, it represents a lower bound on the number of times the threshold has actually been crossed.

RowStatusThe status of this entry. This variable is equivalent in semantics to the V2 SMI RowStatus textual-convention (see RFC 1443). A value of active indicates that the agent is currently monitoring and evaluating the current row. A Value of notInService indicates that the agent has suspended evaluation of the row. Setting this object to destroy causes the agent to suspend evaluation of its row and free its resources. For row creation to occur, the manager must supply active, createAndGo, createAndWait, or notInService as the value of this. If an error occurs at any time during the processing of a particular Monitor table entry, its Row Status column will be set to notReady.

MinValueThe minimum sampled value or 0 upon initialization.

MaxValueThe maximum sampled value or 0 upon initialization.


ActionA string specifying the command to be executed upon finding a match.

FlagsThe flags field dictates the behavior of each Monitor Entry. Each bit in the integer represents the toggling of an option. The flags field of 0x00 is enables default behavior. Logical ordering together of different bits allows one to combine different options.

NT Event Monitor ViewAccess: From the OS Information view click the NT Event Monitor button.

The table containing NT Event Log monitor entries; each entry specifies an Event Log and regular expression. The agent periodically stats the event logs to see if they have been updated. If updated, the agent scans the new entries for the regular expressions. When an entry is found that matches the regular expressions, a trap PDU is sent to appropriate managers.

This table provides the following information:

IndexAn index that identifies an entry in the Event Monitor table.

LogThe number identifying the NT event log to scan for pattern matches. Possible values are: Application, Security, and System.

TimeThe time (based on sysUpTime) at which the event occurred.

MatchesThe number of traps sent by the agent on behalf of this entry. One trap PDU message is sent for each match the agent detects in the corresponding event log.

Last Type MatchThe number identifying the event type of the last event that matched the search criteria. Types 1 through 5 are defined by Windows NT. Type 6 indicates that there has not yet been a matching event for this monitoring entry.

Type FilterThe number identifying the event type to match. Types 1 through 5 are defined by Windows NT. Type all indicates that all event types will match.

Source Last MatchThe source name of the last event log entry that matched this monitor entry. Each time a match occurs, this variable is updated.


Source FilterThe display string representation of the regular expression to match the source name in the event log.

Description Last MatchA textual description of this entry possibly identifying the purpose of this entry and who created it.

Description FilterThe display string representation of the regular expression to match the description in the event log.

StatusThe status of this entry. This variable is equivalent in semantics to the V2 SMI RowStatus textual-convention (see RFC 1443).


ActionA string specifying the command to be executed upon finding a match.combine different options.

Process Monitor TableAccess: From the OS Information view click the Process Monitor button.


IndexA unique value for an entry in the Monitor table.


IntervalThe interval, in seconds, between successive samples by the agent. It must be a multiple of 30 seconds. For example, if a manager wanted to sample the value of a particular variable every 30 seconds, then setting Interval to 30 would instruct the agent to sample once very 30 seconds. The sampling period is not exact but represents a best-effort by the agent.

SampleTypeThe type of sampling performed on the object represented by this entry. For example, for sampling and monitoring objects of type Counter, setting the field SampleType to deltaValue causes the agent to measure/sample the rate of change in the variable rather than the absolute


value. For gauge and gauge-like variables, absoluteValue makes more sense. The agent does not perform sanity checks on this variable against the type of object being monitoring because there may exist some case where a manage may actually wish to monitor the absolute value of a counter or the delta value of a gauge.

AttributeA string specifying the command to be executed upon finding a match.

Current ValueThis variable represents the current value of the object being monitored as last sampled by the agent. If the SampleType is deltaValue, then this value represents the difference between two successive samples. If SampleType is absoluteValue, then this value represents the actual sampled value.

OperatorThe value against which the agent compares the current value. This value represents a threshold. Its semantics are not interpreted by the agent; therefore, the manager is responsible for determining if this value makes sense.

ValueThe time (based on sysUpTime) at which the agent last called or sampled the field being monitored. If the field has not yet been sampled, 0 is returned.

LastCallThe time (based on sysUpTime) at which the agent last called or sampled the field being monitored. If the field has not yet been sampled 0 is returned.

NumTrapsThe number of traps sent for this particular monitor entry. This value indicates how many times the agent has evaluated this entry's expression as true. Recall, the expression takes the form of: 'pmonCurrVal pmonOperator pmonValue'. Because this value depends on the semantics of the variable, the entry's sampling interval, and the interval at

which the monitoring table is evaluated, it represents a lower bound on the number of times the threshold has actually been crossed.

LastTrapThe time (based on sysUpTime) at which the agent last sent a trap for this Monitor Table entry. If no traps have been sent, the value is 0.


Flags

The flags field dictates the behavior of each Moni-tor table entry. Each bit in the integer represents the toggling of an option. The flags field of 0x00 is enables default behavior.

Action A string specifying the command to be executed upon finding a match.

Regular ExpressionThe expression of this field.

MinValueThe minimum sampled value or 0 upon initialization.

MaxValueThe maximum sampled value or 0 upon initialization.

Current PIDThe PID of the process being monitored.

RowStatusThe status of this entry. This variable is equivalent in semantics to the V2 SMI RowStatus textual-convention (see RFC 1443). A value of active indicates that the agent is currently monitoring and evaluating the current row. A value of notInService indicates that the agent has suspended evaluation of the row. Setting this

field to destroy causes the agent to suspend evaluation of its row and free its resources. For row creation to occur, the manager must supply active, createAndGo, createAndWait, or notInService as the value of this field. If an error occurs at any time during the processing of a particular processMonTable entry, its RowStatus column will be set to notReady.

Process Table Access: From the OS Information view click the Process Table button.

This table lets you access the kernel’s process table, which can be queried to find out information on processes currently running on this host. NT only displays a certain number of the fields listed below.

The following information is available from this table:

IDThe unique process identification number, which also serves as the instance of this process.

NameThe name of the process that is running (for example, swapper).


StateThe process state that is dependent on the operating system. The possible states include Sleeping, Waiting, Running, Idle, Zombie, and Stopped.

NiceA value, which can be set, that reflects the level of priority that the running process has when compared to other processes. The higher the value, the lower the priority of the running process.

UIDThe process owner’s user ID (for example, 0 for root).

GIDThe process owner’s group ID.

SizeThe combined size of the data and stack segments, in kilobytes. Processes are normally broken into segments, including those for text (or program), data, and stack. This variable indicates how large the variable size portion of a process is. Monitoring this value can help determine the health of a process.

FlagsThe process flags; flags are operating system dependent and are generally documented in system header files.

MemoryThe percentage (0-100) of real memory used by this process.

RSSReal memory (resident set) size of the process in kilobytes. This value indicates how many bytes are held by a process.

TimeThis process' accumulated CPU time in seconds.

Parent IDThis process' parent process ID (PID).

Thread CountThe number of threads executing within this process. Note, on some systems, the operating system may be un-aware of user-level threads executing within the process. This field reflects the number of threads executing within the process that the operating system is aware of.

In BlocksThe number of blocks of data input by the process.


Out BlocksThe number of blocks of data output by the process.

Message SentThe number of messages sent by the process.

Messages ReceivedThe number of messages received by the process.

System CallsThe number of system calls invoked by this process.

Minor Page FaultsThe number of minor page faults incurred by this process. Minor faults do not require I/O to retrieve the page.

Major Page FaultsThe number of major page faults incurred by this process. Major faults require I/O to retrieve the page.

Process SwapsThe number of times this process has been swapped.

Voluntary SwitchesThe number of voluntary context switches incurred by this process. Voluntary context switches occur when the processor 'voluntary' gives up the CPU (e.g., waiting on I/O.)

Involuntary SwitchesThe number of involuntary context switches incurred by this process. An involuntary context switch occurs when the process has executed for the duration of its time quantum and is switched out by the process scheduler.

User TableAccess: From the OS Information view click on the User Table button.

This table lists the following information about all users who are permitted to log on to the workstation.

IndexA number derived from its entry in the file.

Login IDThe user’s login ID, which is normally given to the system’s login prompt (for example, root).

PasswordThe user’s encrypted password. Users without passwords have an “*” in this field.

UIDThe user’s ID (for example, 0).

GIDThe user’s group ID (for example, 1).


Who TableAccess: From the OS Information view click on the Who Table button.

This table shows who is logged onto the system.

The following information is available from this table:

IndexThe instance of this entry.

NameThe user name of a user logged into the node on which this agent resides (for example, root).

DeviceThe device the user is using to log into the node on which the agent resides.

TimeThe time when the user first logged in.

WhereThe location the user logged in from (for example,:0.0 if local or host name if logged in from a remote system).

Process IDThe number of the process currently operating on this system.

Host Memory Information ViewAccess: From the Icon Subviews menu or the Device icon, select Host System Health > Memory.

This view displays buttons for OS specific information. Only buttons that apply to your OS will be active. The following views are available:

• Shared Memory Table (Page 37)• I/O Buffer Information View (Page 38)• Directory Name Lookup Cache Group View

(Page 39)• NT Information View (Page 39)

Shared Memory TableAccess: From the Host Memory Information view click on the Shared Memory button.

This table contains an entry for each system shared memory segment currently in use.

This view contains the following information:

IDThe unique shared memory segment ID. The value of this field also represents the instance of the shmemEntry field.

Key The shared memory segment key. Each shared memory segment is assigned a key value by the


creating user. Its value is only significant to the creating process.

ModeThe shared memory segment permissions mode. The mode defines access permissions for the message queue as well as status information.

Owner The user login name (e.g., root) of the owner of the shared memory segment.

GroupThe group name (e.g., wheel) of the owner of the shared memory segment.

Segment SizeThe size in bytes of the shared memory segment.

Times LockedThe number of times the shared memory segment has been locked.

DeleteSetting this field to 1 causes the agent to remove this entry from the table. The shared memory identifier is removed from the system-wide table and the kernel shared memory segment and associated data structure are destroyed.

I/O Buffer Information ViewAccess: From the Host Memory Information view click the I/O Buffer button.


Call to Kernel’s Bread FunctionThe total number of calls to the kernel's bread function. This function is the primary read interface to the kernel's buffer pool used for file system I/O. On NT systems, this value is an aggregate of several read variables in the ntCachePerf group.

Kernel Buffer Cache hitsThe number of kernel buffer cache hits. The kernel caches previously used I/O buffers in an attempt to avoid excessive reading and writing to disk. A cache 'hit' indicates that this strategy has paid off because a process has requested a buffer that was in the buffer cache thereby avoiding a more expensive disk read. A high rate of cache hits indicates a relatively smooth running system. On NT systems, this value is an aggregate of several hit variables in the ntCachePerf group.

Time Kernel Slept For BufferThe total number of times the kernel had to sleep for a buffer. The kernel sleeps for a buffer when it fails to find it in the cache and must access the disk for it. Excessive buffer sleeps indicates that


the caching algorithm is not able to effectively predict and cache disk I/O patterns. Adding more memory for buffering may improve the cache hit ratio.

Hit RatePercentage of buffer cache lookups that result in a 'hit'. This value is derived from numBreadHits and numBreadRequests.

Directory Name Lookup Cache Group ViewAccess: From the Host Memory Information view click the DNLC button.

The efficiency and effectiveness of this caching can greatly effect I/O performance. This view contains performance statistics for that cache.


Cache HitsTotal number of DNLC cache hits.

Cache MissesTotal number of DNLC cache misses.

Enters DoneTotal number of DNLC enters done.

Enters Tried when Already CachedTotal number enters tried when already cached.

Long Names Tried to EnterTotal number of long names tried to enter.

Long Name Lookup AttemptsTotal number of long name lookup attempts.

Purges to the DNLC CacheTotal number of least-recently used list empty.

Percentage of Cache Lookups that HitPercentage of DNLC cache lookups that result in a hit. Hit rates less than 90% are considered poor and may require kernel tuning. This value is derived from dnlcHits /dnlcHits + dnlcMisses.

Cache SizeThe maximum number of possible entries in the DNLC cache. If there is no set upper bound, 0 is returned.

NT Information ViewAccess: From the Host Memory Information view click the NT Specific Info button.

This view displays information on the settings, and network abilities of the NT system. This information is NT Specific.



MS-DOS Memory Size (in Mbytes)Size in MBytes of memory to be given to each individual MS-DOS virtual DOS machine (VDM).

Window 3.1 Filing SytemDisplays whether the FAT will allow creation, enumeration, opening, or querying of long file names, and whether extended time stamp information is stored and reported. Setting to true reverts the system back to Win3x semantics.

Critical Section TimeoutThe deadlock time-out for critical sections.

Global FlagNT system global hexadecimal flag that controls various internal operations.

IO Page Lock Limit (in bytes)Specifies the limit of the number of bytes that can be locked for I/O operations.

Large System CacheA nonzero value indicates that the system favors the system-cache working set rather than the processes working set.

Paged Pool Size (in bytes)Size of paged pool in bytes.

Non Paged Pool Size (in bytes)Size of nonpaged pool in bytes.

Paging Files (in Mbytes)List of paging files and their sizes used by the system for paging. For each paging file the description includes the file pathname, current size in MB and maximum size in MB.

Wow Command LineThe number of system page table entries reserved for I/O buffers and other information.

Command Line OptionsCommand-line that runs when an MS-DOS application is launched under NT.

Number History BuffersThe number of history buffers associated with the console by default.

History Buffer CountThe number of commands stored in the history buffer by default.

WOW Size (in Mbytes)The command line that runs when a 16-bit Windows-based application is started. The switches instruct NT to start either an MS-DOS VDM or a WOW VDM.

Crash Dump EnabledWhether debugging information is to be written to a log file in the event of a system crash.


LPT Timeout (in seconds)How many seconds after the LPT port has been used that Windows NT waits before grabbing the port, closing it, and flushing the output. This value is only needed for MS-DOS based applications that use BIOS and do not close the port.

Disable 8dot3 Name CreationDisplays whether the underlying NT system has enabled or disabled the creation of short names to correspond with long filenames. For example, if enabled, then NT will create a short filename to correspond to a file created with a long filename. This feature is often enabled if backward compatibility with DOS based applications is desired.

Log EventDisplays whether NTAS logging is enabled or disabled. If disabled, NT workstation logging is used.

OverwriteIndicates whether an existing log file is to be overwritten by the new one. Enabled for NTAS, disabled for NT workstation.

Send AlertIndicates whether an administrative alert is sent; enabled for NTAS, disabled for NT workstation.

FileSystem Information ViewAccess: From the Icon Subviews menu for the Device icon, select Host System Health > File System.

This view provides you with the Disk Statistics table and button access to the following views:

• Client NFS Information View (Page 42)• Server NFS Information (Page 44)• RPC Information (Page 46)• Top Process View (Page 48)• Queue Messages View (Page 49)• NT Thread Table View (Page 49)• NT Service Table View (Page 50)

Disk Statistics TableThis view shows all of the mount points and local disks and the device addresses where these disks have been mounted.

The following information is available:

IndexA value that uniquely identifies an entry in this table.

DeviceThe device name corresponding to the mounted file system.


MountThe mount point or path name in the local file system where the device is mounted.

Total BlocksThe total number of blocks contained in the mounted device.

Free BlocksThe total number of free blocks or unallocated blocks in the mounted device.

TypeThe type of the mounted device. If this underlying device does not support feature, 0 is returned.

FsidThe (possibly unique) file system ID of the mounted device. V.4 systems support its uniqueness while SunOS does not. For devices or operating systems not supporting this field, the field instance identifier is returned instead.

DeviceThe device name (e.g., /dev/sd0a) corresponding to the mounted file system. For example, the '/' file system is commonly mounted from the device /dev/sd0a. For network file systems, the value corresponds to the remote host and remote file system name (e.g., emptech:/usr/local).

CapacityThe percentage of the device's total capacity in use.

Client NFS Information ViewAccess: From the FileSystem Information view click the Client NFS Information button.

This view provides statistics and counters relating to the use of the distributed file services utilizing the NFS protocol. Statistics and counters are divided according to their applicability towards client and server side protocol operations. For more information, please refer to the NFS protocol specification (RFC 1094).


Total CallsThe total number of NFS calls sent by the NFS client protocol software.

Root CallsThe total number of NFS Root procedure calls sent by the client NFS protocol software. This function has been declared obsolete.

Remove CallsThe total number of NFS Remove procedure calls sent by the client NFS protocol software. This


function is used to remove a file from a given directory.

Rename CallsThe total number of NFS Rename procedure calls sent by the client NFS protocol software. This function is used to rename a given file.

ReadLink CallsThe total number of NFS 'Read link' procedure calls sent by the client NFS protocol software. This function is used to read from a symbolic link.

Bad CallsThe total number of times an NFS call was rejected by the underlying client RPC protocol software.

Read CallsThe total number of NFS Read procedure calls sent by the client NFS protocol software. This function is used to read data (in units of bytes) from a give file.

Link CallsThe total number of NFS Create Link procedure calls sent by the client NFS protocol software. This function is used to create a link to a given file.

Received CallsThe total number of times a client NFS handle was received by the NFS client protocol software.

Write Cache CallsThe total number of NFS Write Cache procedure calls sent by the client NFS protocol software. This function is to be used in future versions of the NFS protocol.

Symbolic LinksThe total number of NFS Create Symbolic Link procedure calls sent by the client NFS protocol software. This function is used to create a symbolic link to a given file.

Write CallsThe total number of NFS Write procedure calls sent by the client NFS protocol software. This function is used to write data (in units of bytes) to a given file.

Make Directory CallsThe total number of NFS mkdir procedure calls sent by the client NFS protocol software. This function is used to create a directory within a given directory.

Null callsThe total number of NFS NULL procedure calls sent by the client NFS protocol software. The


'NULL' procedure is often used to allow server response testing and timing.

Create CallsThe total number of NFS Create procedure calls sent by the client NFS protocol software. This function is used to create a file in a given directory.

Remove Directory CallsThe total number of NFS rmdir procedure calls sent by the client NFS protocol software. This function is used to remove a given directory.

Get Attribute CallsThe total number of NFS GetAttr procedure calls sent by the client NFS protocol software. This function is used to obtain attributes for a given file.

Lookup CallsThe total number of NFS Lookup procedure calls sent by the client NFS protocol software. This function is used to retrieve a file's attributes and handle.

Read Directory CallsThe total number of NFS readdir procedure calls sent by the client NFS protocol software. This function is used to read a variable number of directory entries from the given directory.

Set Attribute CallsThe total number of NFS SetAttr procedure calls sent by the client NFS protocol software. This function is used to set a file's attributes.

Status CallsThe total number of NFS stat procedure calls sent by the client NFS protocol software. This function is used to retrieve file system statistics.

Server NFS InformationAccess: From the FileSystem Information view click the Server NFS Information button.

This view provides statistics and counters relating to the use of the distributed file services utilizing the NFS protocol. Statistics and counters are divided according to their applicability towards client and server side protocol operations. For more information, please refer to the NFS protocol specification (RFC 1094).


Total CallsThe total number of NFS calls received by the NFS server protocol software.


ReadLink CallsThe total number of NFS Read link procedure calls received by the server NFS protocol software. This function is used to read from a symbolic link.

Link CallsThe total number of NFS Create Link procedure calls received by the server NFS protocol software. This function is used to create a link to a given file.

Bad CallsThe total number of times an NFS call was rejected by the underlying server RPC protocol software.

Read CallsThe total number of NFS Read procedure calls received by the server NFS protocol software. This function is used to read data (in units of bytes) from a give file.

Symbolic LinksThe total number of NFS Create Symbolic Link procedure calls received by the server NFS protocol software. This function is used to create a symbolic link to a given file.

Null CallsThe total number of NFS NULL procedure calls received by the server NFS protocol software. The

'NULL' procedure is often used to allow server response testing and timing.

Write Cache CallsThe total number of NFS Write Cache procedure calls received by the server NFS protocol software. This function is to be used in future versions of the NFS protocol.

Make Directory CallsThe total number of NFS mkdir procedure calls received by the server NFS protocol software. This function is used to create a directory within a given directory.

Get Attribute CallsThe total number of NFS GetAttr procedure calls received by the server NFS protocol software. This function is used to obtain attributes for a given file.

Write CallsThe total number of NFS Write procedure calls received by the server NFS protocol software. This function is used to write data (in units of bytes) to a given file.

Remove Directory CallsThe total number of NFS rmdir procedure calls received by the server NFS protocol software. This function is used to remove a given directory.


Set Attribute CallsThe total number of NFS SetAttr procedure calls received by the server NFS protocol software. This function is used to set a file's attributes.

Create CallsThe total number of NFS Create procedure calls received by the server NFS protocol software. This function is used to create a file in a given directory.

Read Directory CallsThe total number of NFS readdir procedure calls received by the server NFS protocol software. This function is used to read a variable number of directory entries from the given directory.

Root CallsThe total number of NFS Root procedure calls received by the server NFS protocol software. This function has been declared obsolete.

Remove CallsThe total number of NFS Remove procedure calls received by the server NFS protocol software. This function is used to remove a file from a given directory.

Status CallsThe total number of NFS stat procedure calls sent by the server NFS protocol software. This function is used to retrieve file system statistics.

Lookup CallsThe total number of NFS Lookup procedure calls received by the server NFS protocol software. This function is used to retrieve a file's attributes and handle.

Rename CallsThe total number of NFS Rename procedure calls received by the server NFS protocol software. This function is used to rename a given file.

RPC InformationAccess: From the FileSystem Information view click the RPC Information button.

This view provides statistics and counters relating to the use of RPC facilities. While it should be independent of which RPC protocol is used, most often it represents counters and statistics for the usage of Sun RPC. Statistics and counters are divided according to their applicability towards client and server side protocol operations. Please refer to the SunRPC specification (RFC 1057) for more information.



Client Information Calls

Total CallsThe total number of RPC calls sent by the RPC client protocol software.

Bad CallsThe total number of RPC calls rejected by the RPC client protocol software.

Retransmit CallsThe total number of times an RPC call had to be retransmitted due to a timeout while waiting for an RPC server reply.

Bad Existing CallsThe total number of times a server RPC reply was received for which no outstanding call exists.

Timeout CallsThe total number times an RPC call timed out while waiting for a reply from the RPC server.

Wait CallsThe total number of times an RPC call has to wait because no client handle was available.

Newcred CallsThe total number of times an RPC call has to wait because no client handle was available.

Timer CallsThe total number of times the calculated time-out value was greater than or equal to the minimum specified time-out value for an RPC call.

Server Information Calls

Total CallsThe total number of RPC calls received by the RPC server protocol software.

Bad CallsThe total number of calls rejected by the RPC server protocol software; it is equivalent to the sum of the MIB fields serverRPCBadlen and serverRPCxdrcall.

Null CallsThe number of RPC requests not available when it was thought to be received.

Bad Length CallsThe number of RPC requests whose lengths were shorter than the minimum size RPC message.

XDR CallsThe number of RPC requests whose header could not be XDR decoded.


Top Process ViewAccess: From the FileSystem Information view click on the Top Process button.


IndexThe index in the topProcsTable starting at 1. Processes are sorted by percent CPU utilization with index 1 denoting the process currently using the greatest percentage of the CPU.

Procs IDThe unique process identifier (PID) for the process that this entry describes. You can use this value (plus 1) to index the process in the process table.

Procs UIDThe process owner's user ID (e.g., 0 for root).

PriorityThe nice value of the process which reflects the level of priority that the running process has.

SizeThe combined size of this process' text, data, and stack segments in KBytes.

MemoryThe real memory (resident set) size of the process in KBytes.

StatusThe operating system-dependent process state (e.g., sleeping, waiting, running, idle, zombie, stopped).

TimeThe CPU time, in seconds, accumulated by this process.

CPU Util.The percent CPU utilization, of this process, over the last sample interval. Although this value is highly system-dependent, it is usually determined by calculating the difference in the number of CPU ticks and dividing by the total possible CPU ticks. Since fractions are not supported by SNMP, the value reported is percentage multiplied by 100. For example, a CPU percentage of 1.37 would be returned as 137.

CommandThe name of the running process that this entry describes.

ArgumentsThe arguments (if any) to the running process that this entry describes.


Queue Messages ViewAccess: From the FileSystem Information view click the Queue Messages button.

This table contains an entry for each system message queue currently in use.

This views contains the following information:

IDThe unique queue ID. The value of this field also represents the instance for the queEntry field.

KeyThe message queue key. Each message queue has a key value chosen by the creating user. Its value is only significant to the creating process.

ModeThe message queue permissions mode. The mode defines access permissions for the message queue as well as status information.

OwnerThe login name (e.g., root) of the owner of the message queue.

GroupThe group name (e.g., wheel) of the owner of the message queue.

Byte CountThe number of bytes currently in the message queue.

Message CountThe number of messages currently in the message queue.

DeleteSetting this field to the value 1 causes this agent to remove the message queue from its table. The message queue identifier is removed from the system-wide table and the kernel message queue and associated data structure are destroyed.

NT Thread Table ViewAccess: From the FileSystem Information view click the NT Thread Table button.

This table provides historical information of NT threads.


Thread IDAn entry in the NT system thread table.

Process IDThe process ID with which this thread is contained and executing within.


Thread NumberThe thread number within a given process. Thread numbers are not unique across all threads in the system.

Privileged TimeThe total elapsed time (in centiseconds) that this thread has executed in Privileged Mode.

Processor TimeThe total elapsed time (in centiseconds) that this thread has used the processor to execute instructions.

User TimeTotal elapsed time (in centiseconds) that this thread has executed in User Mode.

Context SwitchesNumber of thread context switches.

Elapsed TimeThe total elapsed time (in seconds) this thread has been running.

Priority BaseThe current base priority of this thread. The system may alter the thread's dynamic priority above, below the base priority.

PriorityThe current dynamic priority of this thread.

Wait ReasonReason thread is waiting; valid only if Thread State is currently wait, otherwise undefined.

Start AddressThe starting virtual address of this thread.

StateThe current state of this thread.

NT Service Table ViewAccess: From the FileSystem Information view click the NT Service Table button.

This table provides a list of services currently running on the NT system.

This table contains the following information:

IndexIdentifier for the service running on this device.

NameThe system service name.

Path NameThe system service path.

Start TypeThe manner in which the service is started. Automatic implies that the system starts the service at boot time while Manual implies that the service must be started by hand by an


administrator. Disabled indicates that the service cannot be started.

ParametersThe parameters passed to this service when it is invoked.

StateThe current state of the system service.

Host Performance ViewAccess: From the Icon Subviews menu for the Device icon, select Host System Health > Performance.

This view provides you button access to the following views:

• System Performance View (Page 51)• Cache Performance View (Page 53)• Memory Performance View (Page 55)• Unix Kernal View (Page 57)• Page File Performance View (Page 62)

System Performance ViewAccess: From the Host Performance view click the System Performance view button.

Various NT-specific performance groups are located under this Performance view.


Total Time (in centiseconds)

PrivilegedRunning counter of centiseconds spent by the system processor(s) in Privileged mode.

Processor Running counter of centiseconds spent by the system processor(s) running Idle threads. Note that this is actually the inverse of the total processor time.

UserRunning counter of centiseconds spent by the system processor(s) running User mode.

Read

Kbytes TransferredThe number of KBytes transferred for all the file system read operations on this system since system initialization.


OperationsTotal number of all the file system read operations on this system since system initialization.

Write

KBytes TransferredThe number of Kbytes transferred for all the file system write operations on this system since system initialization.

OperationsThe number of all the file system write operations on this system since system initialization.

File Information

Control KiloBytesAn aggregate of KBytes transferred for all file system operations that are neither reads or writes (e.g., file system control requests or device control requests).

Control OperationsAggregate counter of all file system operations that are neither reads nor writes.

Data OperationsTotal number of read and write operations to file system devices issued by the system since system initialization.

Align FixupsThe number of alignment faults fixed by the system.

Context SwitchesThe total number of context switches that have occurred since the kernel was last initialized. A context switch occurs each time a thread gives up the CPU and another takes its place. This counter reflects the level of system activity; a high rate of context switching is indicative of the system load. This counter is equivalent (for NT systems) to the UNIX counter Number Switches (kernelperf.14)

Floating EmulationsThe Number of floating emulations performed by the system.

Queue LengthInstantaneous processor queue length in threads and is equivalent to runQLen (kernelperf.4)

System CallsThe number of calls to system service routines.

InterruptsThe number of hardware interrupts that have occurred.

Exception DispatchesThe total number of exceptions dispatched by the system since it was initialized.


Cache Performance ViewAccess: From the Host Performance view click on the Cache button.


Asynchronous

Copy ReadsThe number of async reads from Cache pages involving a memory copy of the data from the Cache to the application's buffer.

Data MapsNumber of async data maps of file pages into the Cache.

Fast ReadsThe number of direct-to-Cache async read operations.

MDL ReadsThe number of async memory descriptor list (MDL) reads from the Cache. The MDL contains the physical address of each page in the transfer thus permitting DMA of the pages.

Pin ReadsThe number of async reads from the Cache in preparation to writing the data back to disk. Pages read in this fashion are pinned in memory at the completion of the read.

Data

Flush PagesThe number of pages of the Cache flushed to disk as a result of a flush request or to satisfy a write-through request.

FlushesNumber of Cache data flush operations.

Map HitsThe number of data maps in the Cache that could be resolved without retrieval from disk.

Map PinsThe number of data maps in the Cache that resulted in pinning a page in main memory.

MapsThe number of times a file system such as NTFS or HPFS has mapped a page of a file into the Cache to read the page.

Synchronous

Copy ReadsThe number of reads from Cache pages that wait for the copy operation to complete before proceeding.


Data MapsThe number of times that a file system such as NTFS or HPFS maps a page of a file into the Cache to read the page.

Fast ReadsThe number of sync reads from Cache pages that bypass the installed file system and retrieve the data directly from the Cache.

MDL ReadsThe number of reads from Cache pages that use a Memory Descriptor List (MDL) to access the pages.

Pin ReadsThe number of page reads that have resulted in the page being pinned in memory.

Fast Read

Not PossibleThe number of times an API function call to bypass the file system to get at Cache data could not be honored without invoking the file system after all.

Resource MissesThe number of Cache misses necessitated by the lack of available resources to satisfy the request.

ReadsThe number of reads from Cache pages that bypass installed file systems and read from the Cache directly.

PagesThe number of pages the Cache's Lazy Write thread has written to disk. Lazy Writing is the process of updating the disk after the page has been changed in memory so the application making the change to the file does not have to wait for the disk write to complete before proceeding.

Lazy Write

FlushesThe number of times the Cache's Lazy Write thread has written to disk.

PagesThe number of pages the Cache's Lazy Write thread has written to disk. Lazy Writing is the process of updating the disk after the page has been changed in memory so the application making the change to the file does not have to wait for the disk write to complete before proceeding.


MDL Read

Hits The number of Cache Memory Descriptor List (MDL) read requests that hit the Cache.

ReadsNumber of MDL Cache reads.

Copy Read

HitsNumber of Cache Copy Read requests that hit the cache and did not require a disk read.

ReadsThe number of reads from Cache pages that involved a memory copy of data from the Cache to the application's buffer.

Pin Read

Hits The number Cache Pin Read requests that hit the Cache.

ReadsThe number of pages read from the Cache that have been pinned in memory.

Memory Performance ViewAccess: From the Host Performance view click on the Memory Performance button.


Available KBytesThe number of KBytes of virtual memory currently on the Zeroed, Free, and Standby lists. Zeroed and free memory is ready for use. Standby memory is memory removed from a process's working set but still available.

Cache KBytesThe number of KBytes currently in use by the system Cache.

Cache KBytes PeakThe maximum number of KBytes used by the system Cache.

Cache FaultsThe number of Cache faults whereby memory had to be located elsewhere.

Commit LimitThe size in KBytes of virtual memory that can be committed without having to expand the paging file(s).


Committed KBytesThe number of KBytes of virtual memory that have been committed.

Demand Zero FaultsThe number of page faults for pages that must be filled with zeros before fault is satisfied.

Page

FaultsThe number of page faults in the processor and is equivalent to Page Faults.

ReadsThe number of times the disk was read to retrieve pages of virtual memory.

WritesThe number of times pages have been written to disk.

Input The number of pages read from disk to resolve memory references.

OutputThe number of pages written to disk because the pages were modified.

CountThe number of pages read or written from and to disk is a sum of Pages Input and Pages Output.

Transition FaultsThe number of page faults resolved by recovering pages that were in transition to disk at time of page fault.

Write CopiesThe number of page faults that have been satisfied by making a copy of a page when an attempt to write the page was made while it was shared.

Free System Page Table EntriesThe number of Page table entries not currently in use by the system.

Pool

Non Paged AllocationsThe number of calls to allocate space in the system Nonpaged pool.

Non Paged KBytesThe number of KBytes in the Nonpaged pool which is a system memory area where space is acquired by operating systems facilities as they accomplish their tasks. These pages cannot be paged out to disk.

Paged AllocationsThe number of calls to allocate space in the system Paged Pool. Paged Pool is a system memory area where space is acquired by


operating systems facilities as they accomplish their tasks. Paged Pool bytes may be paged out to disk when not accessed by the system for sustained periods of time.

Paged KBytesThe number of KBytes in the Paged Pool.

Paged Resident KBytesThe size of paged Pool resident in core memory in KBytes.

System

Cache Resident KBytesThe number of KBytes currently resident in the global disk cache.

Code Resident KBytesThe number of KBytes of System Code Total Bytes currently resident in core memory. This is the code working set of the pagable executive.

Code Total KBytesTotal number of KBytes of pageable pages in ntoskrnl.exe, hal.dll, and the boot drivers and file systems loaded by ntldr/osloader.

Driver Resident KBytesThe number of KBytes of System Driver Total KBytes currently resident in core memory. The

number is the code working set of the pagable drivers.

Driver Total KBytesThe number of KBytes of pageable pages in all other loaded device drivers.

Unix Kernal ViewAccess: From the Host Performance view click on the Unix Kernal button.

This views provide specific performance information for Concord systemEDGE Unix Agents. This view contains the following performance information.

CPU

Percentage of CPU usage over 1 minuteThe percentage of time over the last one-minute sample period that the CPU was not idle. The agent samples the CPU very minute and calculates this variable. On multi-processor machines, this field represents the value for the first CPU only. The Host Resources MIB hrProcessorTable breaks out the cpu load on a per-processor basis. This value is meaningless until at least two samples have been taken. On NT systems, this value is the average over all the CPUs.


Percentage of CPU usage over 5 minutesThe percentage of time over the last 5-minute sample period that the CPU was not idle. The agent samples the CPU every 5 minutes and calculates this variable. On multi-processor machines, this field represents the value for the first CPU only. The Host Resources MIB hrProcessorTable breaks out the cpu load on a per-processor basis. This value is meaningless until at least two samples have been taken. On NT systems, this value is the average over all the CPUs.

Percentage of CPU usage over 15 minutesThe percentage of time over the last 15-minute sample period that the CPU was not idle. The agent samples the CPU every 15 minutes and calculates this variable. On multi-processor machines, this field represents the value for the first CPU only. The Host Resources MIB hrProcessorTable breaks out the cpu load on a per-processor basis. This value is meaningless until at least two samples have been taken. On NT systems, this value is the average over all the CPUs.

Load

Load Average Over the Last MinuteThe load average over the last minute. The load average represents the average number of jobs in

the run queue over the specified time range. The value reported is the load average multiplied by 100.

Load Average Over the last 5 minutesThe load average over the last 5 minutes. The load average represents the average number of jobs in the run queue over the specified time range. The value reported is the load average multiplied by 100.

Load Average Over the last 15 minutesThe load average over the last 15 minutes. The load average represents the average number of jobs in the run queue over the specified time range. The value reported is the load average multiplied by 100.

SWAP

Amount of Swap Space Currently in UseThe amount of swap space (KBytes) currently in use by the system. Swap space is used when memory is in short supply. Typically, entire processes are swapped out to secondary storage. Comparing this value to totalSwap (in Empire's kernelConfig group) can help indicate if additional swap space is needed.

Total System Swap Space (KBytes)The amount of swap space (KBytes) currently in use by the system. Swap space is used when


memory is in short supply. Typically, entire processes are swapped out to secondary storage. Comparing this value to totalSwap (in Empire's kernelConfig group) can help indicate if additional swap space is needed.

Percent of Total Swap Space UsedTotal system swap space in KBytes. This field is identical to the kernelConfig.totalSwap field and is repeated here for the convenience of management stations which cannot simultaneously poll groups of fields in different branches of the MIB.

Memory

Memory Usage in KBytesThe total real KBytes of memory in use sampled over a fixed period of time. The sampling interval is system dependent. In SunOS, the kernel updates this parameter once every 5 seconds. Comparing memInUse to memory (in the 'system' group) can help indicate if a system has sufficient memory for its current load.

Total Active Real in Memory KBytesThe total active real memory (KBytes) sampled over a fixed period of time. The sampling interval is system dependent. In SunOS, the kernel updates this parameter once every 5 seconds. Memory is active when it is actually being used by

a process running in memory. This value should be less than or equal to memInUse. A high value may indicate a system with insufficient memory.

Percent of Total Active Memory UsedThe percentage of the system's memory in use. The value of this field can be approximated by dividing memInUse by memory system and converting to a percentage. Because virtual memory allows systems to operate with a higher memCapacity value, this value alone should not be used to judge how loaded a system is. Managers should also monitor swapCapacity.

Percent of Total Memory UsedThe percentage of the system’s total memory that has been used.

Active Jobs Swapped Out of MemoryTotal number of jobs swapped out of active memory.

Scheduler’s Run Queue LengthThe percentage of time over the last 15-minute sample period that the CPU was not idle. The agent samples the CPU every 15 minutes and calculates this variable. On multi-processor machines, this field represents the value for the first CPU only. The Host Resources MIB hrProcessorTable breaks out the cpu load on a per-processor basis. This value is meaningless


until at least two samples have been taken. On NT systems, this value is the average over all the CPUs.

Context SwitchesThe total number of context switches that have occurred since the kernel was last initialized. A context switch occurs each time a process gives up the CPU and another takes its place. This counter reflects the level of system activity; a high rate of context switching is indicative of the system load.

Trap SwitchingsThe total number of traps switching a process from user to kernel mode that have occurred since the kernel was last initialized. Traps are hardware exceptions that occur and are usually caused by the currently running process. Example traps include those for incorrect arithmetic operations, segmentation violations or page faults. An excessive trap rate can indicate a faulty program, excessive system loading, or some other abnormality.

System CallsThe total number of system calls that have occurred since the kernel was last initialized. System calls occur when a process calls a function which must execute in kernel or privileged mode; it is a indicator of the system

load and may be higher on servers or machines shared by many users.

Device InterruptsThe total number of device interrupts that have occurred since the kernel was last initialized. The operating system is interrupted by devices and peripherals when they require the attention of the system. An excessive rate of interrupts can indicate a heavily loaded machine; servers and machines shared by many users will typically have a higher rate though.

Page Info

Pages Paged InThe total number of pages that have been paged in since the kernel was last initialized. Page-in is an operation performed by the virtual memory system in which the contents of a page are read from secondary storage. A high rate of change may indicate an overloaded system.

Pages Paged OutThe total number of pages that have been paged out since the kernel was last initialized. Page-out is an operation performed by the virtual memory system in which the contents of a page are written to secondary storage. A high rate of change may indicate an overloaded system.


Pages Reclaimed from FreelistThe total pages that have been reclaimed from the freelist since the kernel was last initialized. Memory pages are stored on a free-list when not in use. If a page has been acquired from the free-list, it has been reclaimed. A high rate of changed indicates an active system which is not generally considered to be overloaded.

Pages Swapped InThe total number of pages that have been swapped in since the kernel was last initialized. Page swapping occurs when a process is swapped to and from secondary storage. A high rate of page swap activity can indicate an overloaded system.

Pages Swapped OutThe total number of pages that have been swapped out since the kernel was last initialized. Page swapping occurs when a process is swapped to and from secondary storage. A high rate of page swap activity can indicate an overloaded system.

Pages Faults OccurredThe total number of page faults that have occurred since the kernel was last initialized. A page fault occurs when a running process attempts to access a virtual memory page that is not currently in physical memory resulting in a hardware page fault. A high rage of page faults

may indicate an overloaded system or one with insufficient memory.

Total No. of Open FilesThe system-wide total number of open files.

Process

Processes Swapped InThe total number of processes that have been swapped in since the kernel was last initialized. Processes are swapped to and from secondary storage when memory is in short supply. A high rate may indicate an overloaded system.

Processes Swapped OutThe total number of processes that have been swapped out since the kernel was last initialized. Processes are swapped to and from secondary storage when memory is in short supply. A high rate may indicate an overloaded system.

No. Proc Table Slots UsedThe number of processes table slots currently allocated and in use. On older BSD-based systems, this metric is important since it places an upper bound on the total number of processes that may run on the system at any one time.


Page File Performance ViewAccess: From the Host Performance view click on the Page File button.


Pages InputThe total number of pages that have been paged in since the kernel was last initialized. Page-in is an operation performed by the virtual memory system in which the contents of a page are read from secondary storage. A high rate of change may indicate an overloaded system.

Pages OutputThe total number of pages that have been paged out since the kernel was last initialized. Page-out is an operation performed by the virtual memory system in which the contents of a page are written to secondary storage. A high rate of change may indicate an overloaded system.

Total PagesNumber of pages read or written from/to disk and is a sum of Pages Input and Pages Output.

Page WritesNumber of times pages have been written to disk.

Page ReadNumber of pages read from disk to resolve memory references and is equivalent to numPageIns.

Page FaultsThe total number of page faults that have occurred since the kernel was last initialized. A page fault occurs when a running process attempts to access a virtual memory page that is not currently in physical memory resulting in a hardware page fault. A high rage of page faults may indicate an overloaded system or one with insufficient memory.

UsageThe current usage measured in bytes.

Peak UsageThe maximum usage allowed on this system.


Model Information View

This section provides a brief overview of the Model Information view.

This view displays administrative information about the device and its applications and lets you set thresholds and alarm severity for the device.

Figure 8 shows a sample Model Information view. The layout of this view is the same for all model types in SPECTRUM but some information will vary depending on the model it defines. Refer to the SPECTRUM Views documentation for a complete description of this view.

Figure 8: Model Information View

Model Name ContactDescriptionLocation

SpectroGRAPH: Model Name


IP Address of Model Type of Landscape: Primary

ManufacturerSysUpTime

Net AddressDevice TypeSerial Number

Model Information View

MM Name

MM Part Number

MM Version Type

Model Type

Model Creation Time

Model Created By

Model State

Security String

Communication Information

Poll / Log Information

Condition Value

Contact Status

DCM TimeOut

DCM Retry

Lost Child Count

Value When Yellow

Value When OrangeValue When Red

Community Name

Mgnmt Protocol

Poll Interval

Poll Status

Log Ratio

Last Successful Poll

Logged Polled

True

Condition Value


Traps, Events, and Alarms

This section describes trap, event, and alarm support.

This section describes any device-specific events and alarms supported by this management module.

• Standard Trap Support• Device-Specific Trap Support

Standard Trap SupportThe following standard traps are supported.

Device-Specific Trap SupportThe supported device-specific traps are listed in Table 4 (Page 65)

Table 3: Standard Trap Support

Standard Trap Name OID

coldStart 0.0

warmStart 1.0

linkDown 2.0

linkUp 3.0

authenticationFailure 4.0

egpNeighborLoss 5.0


Table 4: Device-Specific Traps

Trap Name OID Variable BindingsEvent

GeneratedAlarm

GeneratedAlarm

Severity

monitorTrap 1.3.6.1.4.1.546.1.1.6.1 1.3.6.1.4.1.546.6.1.1.2 1.3.6.1.4.1.546.6.1.1.5 1.3.6.1.4.1.546.6.1.1.6 1.3.6.1.4.1.546.6.1.1.8 1.3.6.1.4.1.546.6.1.1.12 1.3.6.1.4.1.546.6.1.1.7 1.3.6.1.4.1.546.6.1.1.1

0x1160028 NA NA

kernelErrorTrap 1.3.6.1.4.1.546.1.1.6.2 1.3.6.1.4.1.546.1.1.8.1.1 1.3.6.1.4.1.546.1.1.8.1.6 1.3.6.1.4.1.546.1.1.8.1.7 1.3.6.1.4.1.546.1.1.8.1.8

0x1168d1e NA NA

monitorEntryNotReadyTrap 1.3.6.1.4.1.546.1.1.6.3 1.3.6.1.4.1.546.6.1.1.2 1.3.6.1.4.1.546.6.1.1.5 1.3.6.1.4.1.546.6.1.1.6 1.3.6.1.4.1.546.6.1.1.8 1.3.6.1.4.1.546.6.1.1.12 1.3.6.1.4.1.546.6.1.1.7 1.3.6.1.4.1.546.6.1.1.1

0x116002a 0x116002a Yellow

logMonMatchTrap 1.3.6.1.4.1.546.1.1.6.4 1.3.6.1.4.1.546.11.1.1.2 1.3.6.1.4.1.546.11.1.1.3 1.3.6.1.4.1.546.11.1.1.51.3.6.1.4.1.546.11.1.1.6 1.3.6.1.4.1.546.11.1.1.10 1.3.6.1.4.1.546.11.1.1.1

0x116002f NA NA


logMonNotReadyTrap 1.3.6.1.4.1.546.1.1.6.5 1.3.6.1.4.1.546.11.1.1.2 1.3.6.1.4.1.546.11.1.1.3 1.3.6.1.4.1.546.11.1.1.5 1.3.6.1.4.1.546.11.1.1.6 1.3.6.1.4.1.546.11.1.1.10 1.3.6.1.4.1.546.11.1.1.1

0x1160030 0x1160030 Orange

nteventMonMatchTrap 1.3.6.1.4.1.546.1.1.6.7 1.3.6.1.4.1.546.5.6.4.1.1 1.3.6.1.4.1.546.5.6.4.1.2 1.3.6.1.4.1.546.5.6.4.1.3 1.3.6.1.4.1.546.5.6.4.1.5 1.3.6.1.4.1.546.5.6.4.1.7 1.3.6.1.4.1.546.5.6.4.1.9 1.3.6.1.4.1.546.5.6.4.1.12

0x1160031 0x1160031 Yellow

nteventMonNotReadyTrap 1.3.6.1.4.1.546.1.1.6.8 1.3.6.1.4.1.546.5.6.4.1.1 1.3.6.1.4.1.546.5.6.4.1.2 1.3.6.1.4.1.546.5.6.4.1.6 1.3.6.1.4.1.546.5.6.4.1.8 1.3.6.1.4.1.546.5.6.4.1.10 1.3.6.1.4.1.546.5.6.4.1.12

0x1160032 0x1160032 Yellow



GeneratedAlarm

GeneratedAlarm

Severity


monitorClearTrap 1.3.6.1.4.1.546.1.1.6.9 1.3.6.1.4.1.546.6.1.1.2 1.3.6.1.4.1.546.6.1.1.5 1.3.6.1.4.1.546.6.1.1.6 1.3.6.1.4.1.546.6.1.1.8 1.3.6.1.4.1.546.6.1.1.12 1.3.6.1.4.1.546.6.1.1.7 1.3.6.1.4.1.546.6.1.1.11.3.6.1.4.1.546.6.1.1.16

0x1160033 NA NA

processStopTrap 1.3.6.1.4.1.546.1.1.6.10 1.3.6.1.4.1.546.15.1.1.1 1.3.6.1.4.1.546.15.1.1.2 1.3.6.1.4.1.546.15.1.1.5 1.3.6.1.4.1.546.15.1.1.6 1.3.6.1.4.1.546.15.1.1.7 1.3.6.1.4.1.546.15.1.1.8 1.3.6.1.4.1.546.15.1.1.12( 1.3.6.1.4.1.546.15.1.1.14 1.3.6.1.4.1.546.15.1.1.17

0x1160034 0x1160034 Yellow

processStartTrap 1.3.6.1.4.1.546.1.1.6.11 1.3.6.1.4.1.546.15.1.1.1 1.3.6.1.4.1.546.15.1.1.2 1.3.6.1.4.1.546.15.1.1.5 1.3.6.1.4.1.546.15.1.1.6 1.3.6.1.4.1.546.15.1.1.7 1.3.6.1.4.1.546.15.1.1.81.3.6.1.4.1.546.15.1.1.12 1.3.6.1.4.1.546.15.1.1.14 1.3.6.1.4.1.546.15.1.1.17

0x1160035 NA NA



GeneratedAlarm

GeneratedAlarm

Severity


processThresholdTrap 1.3.6.1.4.1.546.1.1.6.12 1.3.6.1.4.1.546.15.1.1.1 1.3.6.1.4.1.546.15.1.1.2 1.3.6.1.4.1.546.15.1.1.5 1.3.6.1.4.1.546.15.1.1.6 1.3.6.1.4.1.546.15.1.1.7 1.3.6.1.4.1.546.15.1.1.8 1.3.6.1.4.1.546.15.1.1.12 1.3.6.1.4.1.546.15.1.1.14 1.3.6.1.4.1.546.15.1.1.17

0x1160036 0x1160036 Yellow

processClearTrap 1.3.6.1.4.1.546.1.1.6.13 1.3.6.1.4.1.546.15.1.1.1 1.3.6.1.4.1.546.15.1.1.2 1.3.6.1.4.1.546.15.1.1.5 1.3.6.1.4.1.546.15.1.1.6 1.3.6.1.4.1.546.15.1.1.7 1.3.6.1.4.1.546.15.1.1.8 1.3.6.1.4.1.546.15.1.1.12 1.3.6.1.4.1.546.15.1.1.14 1.3.6.1.4.1.546.15.1.1.17

0x1160037 NA NA

licenseTrap 1.3.6.1.4.1.546.1.1.6.16 1.3.6.1.4.1.546.1.1.1.14 0x1160038 0x1160038 Yellow

addrChangeTrap 1.3.6.1.4.1.546.1.1.6.18 1.3.6.1.4.1.546.1.1.1.11.3.6.1.4.1.546.1.1.1.19

0x1168d1f NA NA



GeneratedAlarm

GeneratedAlarm

Severity


procGroupChangeTrap 1.3.6.1.4.1.546.1.1.6.19 1.3.6.1.4.1.546.15.10.1.1 1.3.6.1.4.1.546.15.10.1.2 1.3.6.1.4.1.546.15.10.1.5 1.3.6.1.4.1.546.15.10.1.6 1.3.6.1.4.1.546.15.10.1.41.3.6.1.4.1.546.15.10.1.13 1.3.6.1.4.1.546.15.10.1.7 1.3.6.1.4.1.546.15.10.1.8

0x1168d20 NA NA



GeneratedAlarm

GeneratedAlarm

Severity


Index

AAddress

Interface IP 11Physical (MAC) 11Translation 12

Admin Status 10Alarm Generated 65Applications 14

CConfiguration

Device 19

DDevTop Views 13Documentation 5

EEvent Generated 65

HHardware 6

IIcons

Device 6Interface 10

InterfaceStatus 12Type, Device 10

JJob Control 26

KKernel Information (Unix) 25

MManagement Tasks 8

Mask 12Model

Information 63Types of 6

NNetwork I/O ports 13Network Type 11

OOID 65

PPerformance Statistics 18Port Number, Device 10POSIX Job Control 26

SSerial ports 13Statistics


Routing Frame Transmission 19Sun Device

Boot Information 24Diagnostic Information 24Files and Processes 26Kernel Information 24Login Information 37Memory 26POSIX Information 26Process Information 34Process Priority 35Swap Information 24Swap Space 26User Information 36

TThreshold Information 11Trap Name 65Trap Support 64Troubleshooting 8

Date post:	09-Sep-2018
Category:	Documents
Upload:	phamkhuong
View:	213 times
Download:	0 times

Concord systemEDGE Agent (5012) - CA...

Documents