iMonitor Frames
Novell iMonitor provides cross-platform monitoring and diagnostic capability to all servers in your eDirectory tree. This utility lets you monitor your servers from any location on your network where a Web browser is available.
iMonitor lets you look at the eDirectory environment in depth on a partition, replica, or server basis. You can also examine what tasks are taking place, when they are happening, what their results are, and how long they are taking.
iMonitor provides a Web-based alternative or replacement for many of Novell's traditional server-based eDirectory tools such as DSBROWSE, DSTRACE, DSDIAG, and the diagnostic features available in DSREPAIR. Because of this, iMonitor's features are primarily server-focused, meaning that they focus on the health of individual eDirectory agents (running instances of the directory service) rather than the entire eDirectory tree.
iMonitor 1.5 provides the following features:
The information you can view in iMonitor is based the following factors:
Your identity's eDirectory rights are applied to every request you make in iMonitor. For example, you must log in as the Administrator of the server or a console operator on the server where you are trying to access the DS Repair page.
Newer versions of NDS and eDirectory will have features and options that older versions do not.
The information you view in iMonitor immediately shows what is happening on your server.
To use iMonitor 1.5, you need:
The iMonitor 1.5 utility runs on the following platforms:
Novell iMonitor is placed in AUTOEXEC.NCF.
For Windows NT/2000, Linux, and Solaris, iMonitor loads automatically when eDirectory runs.
You can use iMonitor to monitor the following versions of NDS and eDirectory:
To access iMonitor:
Ensure that the iMonitor executable is running on the eDirectory server.
Open your Web browser.
In the address (URL) field, enter:
http://server's_TCPIP_address:httpstack_port/nds
for example:
http://137.65.135.150:8008/nds
DNS names can be used anywhere a server's IP or IPXTM address or distinguished name could be used in iMonitor. For example, when you have configured DNS, then:
http://prv-gromit.provo.novell.com/nds?server=prv-igloo.provo.novell.com
is equivalent to
http://prv-gromit.provo.novell.com/nds?server=IP_or_IPX address
or
http://prv-gromit.provo.novell.com/nds?server=/cn=prv-igloo,ou=ds,ou=dev,o=novell,t=novell_inc
To have access to all of the features, click Login.
Log in as Administrator with the fully distinguished name or administrator equivalent.
This section contains information about the following:
Each iMonitor page is divided into four frames or sections: the Navigator frame, the Assistant frame, the Data frame, and the Replica frame.
Figure 26
iMonitor Frames
Navigator Frame: The Navigator frame is located across the top of the page. This frame shows the server name where the data is being read from, your identity, and the icons you can click to link to other screens, including online help, login, server portal, and other iMonitor pages.
Assistant Frame: The Assistant frame is located at the left side of the page. This frame contains additional navigational aids, such as links to other pages, items that help you navigate data in the Data frame, or other items to assist you with obtaining or interpreting the data on a given page.
Data Frame: The Data frame shows the detailed information about your servers that you request by clicking one of the links listed above. This is the only page you will see if your Web browser does not support frames.
Replica Frame: The Replica frame lets you determine which replica you are currently viewing, and provides links to view the same information from another replica or server's point of view. This frame only appears when you view pages where another replica of the requested data exists or where another replica may have a different view of the information being presented in the Data frame.
Novell iMonitor can be used in two different modes of operation: Direct mode and Proxy mode. No configuration changes are necessary to move between these modes. Novell iMonitor will move between these modes automatically, but you should understand them in order to successfully and easily navigate the eDirectory tree.
Figure 27
Modes of Operation
Direct Mode: Use Direct mode when your Web browser is pointed directly at an address or DNS name on a machine running the iMonitor executable and reading information only on that machine's local eDirectory DIB.
Some iMonitor features are server-centric; that is, they are only available to the iMonitor running on that machine. These features use local API sets that cannot be accessed remotely. Server-centric features in iMonitor include the DS Trace, DS Repair, and Background Process Schedule pages. When using direct mode, all iMonitor features will be available on that machine.
Key features of direct mode:
Proxy Mode: Use Proxy mode when your Web browser is pointed at an iMonitor running on one machine, but is gathering information from another machine. Because iMonitor uses traditional eDirectory non-server-centric protocols for non-server-centric features, all previous versions of eDirectory beginning with NDS 6.x can be monitored and diagnosed. However, server-centric features use APIs that cannot be accessed remotely.
While in proxy mode, if you wish to switch to Direct mode for a different server, you can do so as long as it is a version of eDirectory in which iMonitor has shipped. If the server you are gathering information on by proxy has iMonitor running, you will see an additional icon button in the Navigator frame. When you mouse over the icon, you will see a link to the remote iMonitor on the remote server. If the server you are gathering information on by proxy is an earlier version of eDirectory, no additional icon will be shown and you will always have to gather information on that server by proxy until it is upgraded to a version of eDirectory that includes iMonitor.
Key features of proxy mode:
You can link to the Agent Summary, Agent Information, Agent Configuration, Trace Configuration, DS Repair, Reports, and Search pages from any iMonitor page by using the icons in the Navigator frame. You can also log in or link to the Novell Support ConnectionTM Web page from any iMonitor page.
Login/Logout: The Login button is available if you are not logged in. A Logout button, which closes your browser window, is displayed if you are logged in. Unless all browser windows are closed, your iMonitor session remains open, and you will not need to log in again. You can see your login status on any page by looking at Identity in the Navigator frame.
Support Connection Link: The Novell logo in the upper-right corner is a link to the Novell Support Connection® Web page. This provides a direct link to the Novell Web site for current server patch kits, updates, and product-specific support.
On NetWare 5.x and later servers, a link to NetWare Remote Manager is available to provide you with Web-based monitoring, diagnosis, and troubleshooting information for NetWare servers.
iMonitor is integrated with NetWare Remote Manager in the following ways:
These links can be found under the Manage eDirectory section in the Remote Manager interface. Links to eDirectory agent health information can also be found in the Diagnose Server section under Health Monitor in the eDirectory-related categories.
NetWare Remote Manager also registers with eDirectory, which allows iMonitor and NetWare Remote Manager to cross-reference each other for a more seamless movement between each tool.
A configuration file is included with iMonitor to allow you to change or set default behavior or values in the utility.
The configuration file is a text file containing configuration parameter tags together with their desired values. This file is located in the same directory as the iMonitor executable (which is usually in the same location as the Novell eDirectory executables).
Table 47. iMonitor Configuration Files
| Server | Configuration File |
|---|---|
NetWare, Windows NT, and Windows 2000 |
NDSIMON.INI |
Solaris and Linux |
ndsimon.conf |
There are two groups of parameters that you can set in iMonitor's configuration file.
Except on NetWare, when the iMonitor executable loads, it will attempt to listen on the traditional HTTP port 80. If that port is in use, it will back off to port 8008. If that port is in use, iMonitor will then back off, increasing the desired port by 2 (8010, 8012, and so on) until 8078.
Where SSL is configured and available, a similar bind pattern is attempted. First, port 81 is tried, and then 8009, 8011, 8013, and so on.
This allows iMonitor to coexist with a Web server running on the same server. However, on some platforms, iMonitor may load before the installed Web server does, or you might want iMonitor to bind to a port of your choice. Both regular and SSL ports can be configured using the HttpPort and the HttpsPort parameters respectively. Commented out examples exist in the shipping configuration file. By default, iMonitor binds to all NIC addresses on the server where it loads. However, there is an Address parameter which you can use to specify a list of addresses, in comma delimited format, to bind to.
On NetWare, similar port selection rules are used, but they are controlled by the NetWare Remote Manager HTTP stack (HTTPSTK.NLM) and work as specified in the NetWare Remote Manager documentation.
The configuration file that ships with iMonitor contains samples of the parameters that can be modified. These parameters are preceded by a # character. This indicates that they are commented out or not used when iMonitor parses the configuration file. For the shipping configuration file, iMonitor uses all internally bound default values for these parameters. To enable any of these parameters or to add any parameters, simply omit the # character from the beginning of the line.
This section provides a brief description of iMonitor features.
Online help is provided in each section of iMonitor for more detailed information about each feature and function.
From the Agent Summary page you can view the health of your eDirectory servers, including synchronization information, agent process status, and the total servers known to your database.
In iMonitor, click Agent Summary 
.
Choose from the following options:
Agent Synchronization Summary: You can view the number and types of replicas you have and the length of time since they have been successfully synchronized. You can also view the number of errors for each replica type. If there is only one replica or partition to view, the heading is Partition Synchronization Status.
If the Agent Synchronization Summary doesn't appear, there are no replicas you can view based on your identity.
Servers Known to Database Totals: You can view the type and count of servers known to your database, and whether they are up or down.
Agent Process Status Totals: You can view the status of processes without the administrator's intervention that run on an agent. When there is a problem or piece of information, a status is recorded. The table increases or decreases, depending on the number of recorded statuses.
From the Agent Synchronization page you can view the synchronization status of your partitions. You can filter the information by selecting from the options listed in the Assistant frame on the left side of the page.
In iMonitor, click Agent Synchronization in the Assistant frame.
Choose from the following options:
Partition Synchronization Status: You can view the partition, number of errors, last successful synchronization, and maximum ring delta.
Partition: For each partition, you can view the links to that partition's Replica Synchronization page.
Last Successful Sync: You can view the amount of time since all replicas of an individual partition were successfully able to synchronize from the server.
Maximum Ring Delta: The maximum ring delta shows the amount of data which might not be successfully synchronized to all the replicas in the ring. For example, if a user has changed his login script within the past 30 minutes, and the maximum ring delta has a 45-minute allocation, the user's login might not be successfully synchronized, and he might get the previous login script when he attempts to log in. If, however, the user changed his login script more than 45 minutes ago, he should get the new login script consistently from all replicas.
If Unknown is listed under Maximum Ring Delta, it means the transitive synchronized vector is inconsistent and the maximum ring delta cannot be calculated due to replica/partition operations occurring, or some other problem.
From the Agent Information page you can view the connection information for your server.
In iMonitor, click Agent Information in the Assistant frame.
Choose from the following options:
Ping Info: Depending on the transport, configuration, and platform you are running on, you might not see ping information. The information, if listed, shows that iMonitor has attempted an IP ping to the set of addresses being advertised for the server. Success is as indicated.
DNS Name: Depending on the transport, configuration, and platform you are running on, you might not see this information. The information, if listed, shows that iMonitor has attempted to do an address reversal on IP addresses supported by the server and is indicating the associated DNS name.
Connection Information: You can view connection information for the server, including the server referral, time delta, Root Most Master, and replica depth.
Server Referral: You can view the set of addresses by which your server can be reached.
Time Synchronized: eDirectory believes time is synchronized well enough to issue time stamps based on the server's current time. The time synchronization protocol might or might not currently be in a synchronized state. Time Synchronized indicates that synthetic or future time is not being used unless a replica's last-issued time stamp is greater than the current time.
Time Delta: You can view the difference in time between iMonitor and the remote server in seconds. A negative integer indicates that iMonitor's time is ahead of the server's time; a positive integer indicates that iMonitor's time is slower than the server.
Root Most Master: Root Most Master specifies that the replica that is highest or closest to the root of the naming tree is a master replica.
Replica Depth: You can view the depth of the Root Most Replica (the number of levels between the Root Most Replica and the root of the tree).
From the Known Servers List, you can view the list of servers known to the database of the source server. You can filter the list to show all servers known to the database or to show all servers in the replica ring. If a server has an icon next to it, the server participates in a replica ring.
In iMonitor, click Known Servers in the Assistant frame.
Choose from the following options:
Entry ID: The Entry ID column lists the identifier on the local server for an object. Entry IDs cannot be used across servers.
NDS Revision: The NDS Revision column lists the eDirectory build number or version being cached or stored on the server with which you're communicating.
Status: The Status column shows whether the server is up, down, or unknown. If the status shows as unknown, this means the server has never needed to communicate with the server being shown as unknown.
Last Updated: The Last Updated column shows the last time this server attempted to communicate with the server and found out it was down. If this column is not showing, all servers are currently up.
From the Partitions page you can view information about the replicas on the server you are communicating with. You can filter the page by selecting from the options in the Assistant frame on the left side of the page.
Server Partition Information: You can view information about the server's partition, including the entry ID, replica state, purge time, and last modification time.
Partition: You can view information about the partition Tree object on the server.
Purge Time: Data that has been deleted before the listed purge time can be removed from the database because all replicas have seen the deletion.
Last Modification Time: You can view the last-issued time stamp of data written to the database for the replica. This lets you see if time is in the future and if synthetic time is being used.
Replica Synchronization: You can click the Replica Synchronization link to view the Replica Synchronization Summary page that refers to the partition. The Replica Synchronization page shows information about the partition synchronization status and replica status. You can also view lists of partitions and replicas.
From the Agent Configuration page you can control and configure the DS Agent. The functionality you have on this page will depend on the rights of the current identity and the version of eDirectory you are looking at.
In iMonitor, click Agent Configuration 
.
Choose from the following options:
Agent Triggers: You can use agent triggers to initiate certain background processes. These triggers are equivalent to using the SET DSTRACE=*option command.
Background Process Settings: You can use background process settings to modify the interval at which certain background processes run. These settings are equivalent to the SET DSTRACE=!option command.
Agent Synchronization: You can use agent synchronization settings to disable or enable inbound or outbound synchronization. You can specify in hours the amount of time you want synchronization disabled.
Database Cache: You can configure the amount of database cache used by the DS database engine. Various cache statistics are also provided to assist you in determining whether you have an appropriate amount of cache available. Having an inadequate amount of cache may severely impact your system's performance.
Use the Trace Configuration page to set trace settings. Novell iMonitor's DS Trace is a server-centric feature. That is, it can only be initiated on a server where iMonitor is running. If you need to access this feature on another server, you must switch to the iMonitor running on that server.
To access information on the Trace Configuration page you must be the equivalent of Administrator of the server or a console operator. You are prompted to enter your username and password so your credentials can be verified before you can access information on this page.
In iMonitor, click Trace Configuration 
.
Choose from the following options:
Submit: You can submit changes to Trace Options and Trace Line Prefixes. If DS Trace is off, click Submit to turn it on. If DS Trace is already on, click Submit to submit changes to the current trace.
Trace On/Off: You can turn DS Trace on or off by using this button. The button text will change based on the current DS Trace state. If DS Trace is on, the button text will say Trace Off. Clicking it turns DS Trace off and vice versa. When DS Trace is off, clicking Trace On is equivalent to clicking Submit.
DS Trace Options: These options apply to the events on the local DS Agent where the trace is initiated. The options show errors, potential problems, and other information about eDirectory on your local server. Turning on DS Trace options can increase CPU utilization and might reduce your system's performance; therefore, DS Trace should generally be used for diagnostic purposes, not as a standard practice. These options are a more convenient equivalent of the SET DSTRACE=+option command.
Trace Line Prefixes: You can choose which pieces of data are added to the beginning of any trace line. All trace line prefixes are selected by default.
Trace History: You can view a list of previous trace runs. Each previous trace log is identified by the period of time during which the trace data was being gathered.
Trace Triggers: You can use trace triggers to show the trace flags that must be set in order to display the specified DS Agent information in DS Trace. These triggers might write large quantities of information to trace. Generally, we recommend that these triggers be enabled only when instructed by Novell Technical Support.
Click Submit to submit any changes.
Click Trace On to turn DS Trace on > click 
to view DS Trace in iMonitor.
From the Agent Process Status page you can view background process status errors and more information about each error that occurred. You can filter the information on this page by selecting from the options listed in the Assistant frame on the left side of the page.
In iMonitor, click Agent Process Status in the Assistant frame.
Background process statuses that are currently reported include:
From the Agent Activity page you can determine traffic patterns and potential system bottlenecks. You can use this page to view the verbs and requests that are currently being handled by eDirectory. You can also see which of those requests are attempting to obtain DIB locks in order to write to the database and how many of those requests are waiting to obtain a DIB lock.
If you are viewing a server running Novell eDirectory 8.6, you will also see a list of partitions and the servers that participate in the replica ring with the server specified in the Navigator frame. With the introduction of Novell eDirectory 8.6, synchronization is no longer single threaded. Any 8.6 server might outbound multiple partitions simultaneously to one or more replication partners. For this reason, the synchronization activity page was created so you can more easily monitor this parallel synchronization strategy.
In iMonitor, click Agent Activity in the Assistant frame.
Choose from the following options:
Verb Statistics: Lets you view a running count of all verbs called and requests made since NDS was last initialized. This page also shows how many of those requests are currently active and the minimum, maximum, and average times (shown in milliseconds) that it takes to process those requests.
Background Process Schedule: Lets you view the background processes that are scheduled, what their current state is, and when they are scheduled to run again.
Synchronization Activity: Displays a list of different times that inbound and outbound synchronization occurred. If inbound or outbound synchronization is currently taking place, you will see an icon indicating that the process is active, when that cycle was started, and with which server it is occurring.
If inbound and outbound synchronization is disabled, you will see an icon indicating that fact and when it is scheduled to be reenabled. For outbound synchronization, the next scheduled time is also shown.
From the Verb Statistics page you can determine traffic patterns and potential system bottlenecks. You can use this page to view a running count of all verbs called and requests made since eDirectory was last initialized. This page also shows how many of those requests are currently active and the minimum, maximum, and average times (shown in milliseconds) it takes to process those requests. Background process, bindery, and standard eDirectory requests are tracked.
If you view this page on an older version of eDirectory, you might not see as much information as you would if you were running on DS build number 8500 or later.
From the Background Process Schedule page you can view the background processes that are scheduled, what their current state is, and when they are scheduled to run again. Novell iMonitor's Background Process Schedule is a server-centric feature. That is, it can only be viewed on a server where iMonitor is running. If you need to access the background process schedule on another server, you must switch to the iMonitor running on that server. As you upgrade more servers to eDirectory 8.5, iMonitor's server-centric features will be more available to you. Other server-centric features include the DS Trace and DS Repair pages.
To access information on the Background Process Schedule page, you must be the equivalent of Administrator of the server or a console operator. You are prompted to log in so your credentials can be verified before you can access information on this page.
From the Error Index page you can view information about the errors found on your eDirectory servers. The errors are separated into two fields: eDirectory-specific errors and other errors that might be of interest. Each error listed is hyperlinked to a description that contains an explanation, possible cause, and troubleshooting actions.
In iMonitor, click Error Index in the Assistant frame.
From the Error Index page you can link to the latest Novell documentation on errors, technical information, and white papers.
From the DS Repair page you can view problems and back up or clean up your DIB sets. Novell iMonitor's DS Repair is a server-centric feature. That is, it can only be initiated on a server where iMonitor is running. If you need to access the DS Repair information on another server, you must switch to the iMonitor running on that server. As you upgrade more servers to later versions of eDirectory, iMonitor's server-centric features will be more available to you. Other server-centric features include the DS Trace and Background Process Schedule pages.
To access information on this page, you must be the equivalent of Administrator of the server or a console operator. You are prompted to log in so your credentials can be verified before you can access information on this page.
In iMonitor, click DS Repair 
.
Choose from the following options:
Downloads: Retrieve repair-related files from the file server. You will not be able to access DSREPAIR.LOG if the DSREPAIR utility is running or you have initiated a repair from the DS Repair page in iMonitor until the operation is finished.
Delete Old DIB Sets: Click the red X to delete an old DIB set.
WARNING: This action is irreversible. When you select this option, the old DIB set will be purged from the file system.
DS Repair Advanced Switches: Use the advanced switches to fix problems, check for problems, or create a backup of your database. You will not need to enter information in the Support Options field unless you are directed to do so by Novell Technical Support.
Click Start Repair to run DS Repair on this server.
Use the Agent Health page to view health information about the specified eDirectory agent and the partitions and replica rings it participates in.
In iMonitor, click Agent Health in the Assistant frame.
Click the links to view detailed information.
The Browse page let you browse any object in your tree. The Navigation bar at the top of the page lets you know what server the object you are viewing is on, and the path to the object. The Replica frame on the left of the page lets you view or access the same object on any real partition. Click any underlined object on the page to view more information about an object. You can also click any portion of the name in the Navigator frame to browse up the tree.
The information displayed on this page depends on the eDirectory rights you are logged in with, the type of object you are browsing, and the version of NDS or eDirectory you are running. This page displays XRef objects if you are logged in with supervisor rights. You can use the replica list to jump to a real copy of the replica.
Replica Synchronization: Displays the synchronization status of the replica that contains this object.
Entry Synchronization: Shows which attributes need to be synchronized from this server's point of view.
Connection Information: Lets you know where iMonitor got the information for this object.
Entry Information: Displays the names, flags, base class, modification time stamp, and summary of connection information for the object.
Send Entry to all Replicas: Resends this entry's attributes to all other replicas. This process could take some time if the object has many attribute values. This does not make all other copies of the object identical. It simply allows the other replicas to reconsider each attribute.
The Change Cache page lets you view a list of entries that this server needs to consider for synchronization or purging. This option is available only if the server you are accessing is running eDirectory 8.6 or later and the object you are viewing is a partition root. You must have supervisor rights to the NCP server to view this page.
Entry Synchronization: Use this option to determine why an entry needs to be synchronized.
Use the DirXML Summary page to view a list of any DirXML drivers running on your server, the status of each driver, any pending associations, and driver details.
In iMonitor, click DirXML Summary 
.
Choose from the following options:
Status: Displays the current state of the specified driver. Possible states include: stopped, starting, running, shut down, pending, and getting schema.
Start Option: Displays the current startup option specified for the selected driver.
Pending: Displays the number of associations that have not yet been made.
Driver Details Icon: Displays subscriber and publisher details, XML rules, filters, and pending association lists for DirXML drivers running on your server. Details on the first 50 pending objects are also displayed on this page. The XML rule details provided on this page can be used to determine what to look for in the pending objects to allow their creation to proceed for the specified DirXML driver.
The Replica Synchronization page lets you view the synchronization status of a replica.
In iMonitor, click Agent Synchronization in the Assistant frame.
Click Replica Synchronization for the partition you want to view.
Use the links on this page and in the navigation bar on the left to access other partitions and jump through your replica ring.
Use the Reports page to view and delete reports run directly on this server. Some reports might take a long time to run and can be resource intensive.
Scheduled reports run without authenticating as a user (that is, as [Public]). Any reports you run directly are run as your identity. All report data is stored on the server from which the report was run.
The Report Config page lets you view a list of preconfigured, custom, and scheduled reports. Use this page to modify and run reports, and to create custom reports for iMonitor pages.
In iMonitor, click Reports 
.
Click 
to delete a report and 
to view a report.
In iMonitor, click Reports > Report Config.
Click 
to run a report.
In iMonitor, click Reports > Report Config.
Click 
to configure and schedule a report.
Select any options you want.
(Optional) Configure the report to run on either a periodic basis or at a later time.
Custom reports let you launch any iMonitor page as a report.
In iMonitor, click Reports > Report Config.
Click on the Custom Reports line in the Runable Report list.
Enter a name for the report > Enter the URL to the iMonitor page you want to launch as a report.
Specify the number of versions of the report you want to keep.
(Optional) Click Save to save the report.
Click Run Report to start the report.
(Optional) Configure the report to run on either a periodic basis or at a later time.
Use the Schema page to view your schema, class, and attribute definitions.
In iMonitor, click Schema in the Assistant frame.
Choose from the following options:
Synchronization List: Lists the servers that this server will synchronize with. This option is available only for servers running NDS eDirectory 8.5 or later. You must have supervisor rights on the server to view this information.
Attribute Definitions: The attribute definition page lists the name of each attribute, the syntax that the attribute value will be in, and the constraints that the attribute operates under. Use the navigation frame on the left to browse for and access individual attributes.
Class Definitions: Lists the name of each class, its rules, and its attributes. Use the navigation frame on the left to browse for and access individual attributes.
Use the Search page to search objects based on a variety of query options and filters. The search query options and filters are grouped in two levels of search request forms: basic and advanced. The basic search request form is designed for average users of eDirectory and simple searches. The advanced search request form is designed for advanced users and complicated searches. Currently, only server level search is supported.
All the search options and filters in the four sections are conjunctive. Blank fields (except the Relative Distinguished Name) will be ignored. Use the Ctrl key to deselect an item or select more than one item on the multi-lists. Deselected multi-lists will also be ignored.
In iMonitor, click Search 
.
Click the Help button at the bottom of the search request form to see brief help information added to the form itself.
Click Reload or Refresh to clear the help information.
Use the Stream Viewer page to view the current stream in any of the following formats:
If you have stream attributes that you consistently want to view in a particular format, you can use the Stream Viewer to choose default display settings.
NDS Stream Attribute Setup: Changes the default display format for streams in your browser. It is up to your browser to display the stream correctly, so it might not always apply the settings you have selected.
You must be authenticated to the server to apply any changes you have made to the default settings. Your changes are stored in STREAMS.INI (for NetWare and Windows NT/2000 servers) or STREAMS.CONF (for Solaris and Linux servers), so you can also manually edit the default settings.
iMonitor uses HTTPS for secure iMonitor operations. If the default HTTP port on which iMonitor is listening is 80, the HTTPS port will be 81. If the default HTTP port on which iMonitor is listening is 8008, the HTTPS port is 8009.
For secure ndsimonitor operations on Linux and Solaris systems, you must create a Key Material object (KMO) in the server context. For more information, see Creating a Key Material Object. After creating the KMO, add it to the ndsimonitor configuration file. To do so, add the following line to the /usr/share/ndsimon/ndsimon.conf file, then run the ndsimonitor utility:
SSLKey: KMO_name
Ensure that there is a space character after the colon character and before the KMO name.