Managing Your Infrastructure

1. In the My Infrastructure panel, click Add System/Network Device.

2. Enter a descriptive name for the server in the Display name in up.time field.
   This name will appear in the up.time interface. A system can have a different display name than the hostname. For example, you can assign the display name Toronto Mail Server to a system with the host name 10.1.1.6. This way, IP addresses are stored in up.time, but a more descriptive or meaningful name is displayed in the up.time Web interface.
3. Optionally, enter a description of the system in the Description field.
4. Select the Type of System/Device from the list:
   
   • Agent
   • Net-SNMP v2
   • Net-SNMP v3
   • Network Device
   • Novell NRM
   • pSeries LPAR Server (HMC)
   • pSeries LPAR Server (VIO)
   • Virtual Node
   • VMware ESX
   • VMware vCenter Server
   • WMI Agentless (only present on Monitoring Stations running on Windows)
5. Enter the host name of the system in the Host Name field.
   The host name can be the actual name of the machine that up.time will be monitoring. You can also enter an IP address in this field.
6. Configure the system- or device-specific settings. The options depends on the system or device type you selected in step 4:
   

   • Agent
     Configure the following:

     
     
     • Port
       The port on which the up.time Agent is listening.
     • Use SSL
       Select this check box if you want to securely communicate with the up.time Agent. 

     The up.time Agent’s information can be globally configured in the Global Element Settings page on the Config tab. If this has been done, and the Use up.time Agent Global Configuration check box is selected, the agent port and SSL options will not appear.

   • Net-SNMP v2
     Enter information in the following fields:
     
     • SNMP Port
       The port on which the Net-SNMP instance is listening.
     • Read Community
       A string that acts like a user ID or password, giving you access to the Net-SNMP instance.
       Common read communities are public (enables you to retrieve read-only information from the device) and private (enables you to access all information on the device).
   • Net-SNMP v3
     Enter information in the following fields:
     
     • SNMP Port
       The port on which the Net-SNMP instance is listening.
     • Username
       The name that is required to connect to the Net-SNMP instance.
     • Authentication Password
       The password that is required to connect to the Net-SNMP instance.
     • Authentication Method (optional)
       From the list, select one of the following options, which will determine how encrypted information travelling between the Net-SNMP instance and up.time will be authenticated:
       
       • MD5: A widely-used method for creating digital signatures used to authenticate and verify the integrity of data.
       • SHA: A secure method of creating digital signatures. SHA is considered the successor of MD5 and is widely used with network and Internet data transfer protocols.
     • Privacy Password
       The password that will be used to encrypt information travelling between the Net-SNMP instance and up.time.
     • Privacy Type (optional)
       From the list, select one of the following options, that determine how information travelling between the Net-SNMP instance and up.time will be encrypted:
       
       • DES: An older method used to encrypt information.
       • AES: The successor to DES, which is used with a variety of software that require encryption including SSL servers.

       You can set both an authentication and password type, only one of them, or neither.

   • Network Device (using version 2 of the SNMP protocol)
     By default, the network device's SNMP Version is set to v2; complete the following fields:
     
     • SNMP Port
       The port on which the network device is listening.
     • Read Community
       A string that acts like a user ID or password, giving you access to the network device instance.
       Common read communities are public (enabling you to retrieve read-only information from the device) and private (enabling you to access all information on the device).
     • Is Device Pingable?
       This options specifies whether up.time can contact the network device using the ping utility.
       There are scenarios in which you might not want the network device to be pingable (e.g., you have a firewall in place). Before selecting this check box, you should try to contact the network device using the ping utility. If you cannot ping it, ensure the check box is left cleared. Then, change the default host check for the network device. See Changing Host Checks for more information.
     • Exports NetFlow Data to Scrutinizer?
       If Scrutinizer has been integrated with up.time, and is also receiving NetFlow data from the network device, select this check box. You will then be able to call a Scrutinizer instance directly from the network device’s Graphing tab in up.time.

     SNMP details can be globally configured in the Global Element Settings page on the Config tab. If these have been done, and the Use Global SNMP Connnection Configuration check box is selected, none of these options will appear, or need to be configured.

   • Network Device (using version 3 of the SNMP protocol)
     If your network device uses version 3 of the SNMP protocol, complete the following fields:
     
     • SNMP Version
       Change this to v3 to reveal configuration options relevant to version 3 of the SNMP protocol.
     • SNMP Port
       The port on which the network device is listening.
     • Username
       The name that is required to connect to the network device.
     • Authentication Password
       The password that is required to connect to the network device.
     • Authentication Method (optional)
       From the list, select an option that will determine how encrypted information travelling between the network device and up.time will be authenticated:
       
       • MD5: A widely-used method for creating digital signatures used to authenticate and verify the integrity of data.
       • SHA: A secure method of creating digital signatures. SHA is considered the successor of MD5 and is widely used with network and Internet data transfer protocols.
     • Privacy Password
       The password that will be used to encrypt information travelling between the network device and up.time.
     • Privacy Type (optional)
       From the list, select an option that will determine how information travelling between the network device and up.time will be encrypted:
       
       • DES: An older method used to encrypt information.
       • AES: The successor to DES, which is used with a variety of software that require encryption including SSL servers.

       You can set both an authentication and password type, only one of them, or neither.

     • Is Node Pingable?
       This option specifies whether up.time can contact the network device using the ping utility.
       There are scenarios in which you might not want the network device to be pingable (e.g., you have a firewall in place). Before selecting this check box, you should try to contact the network device using the ping utility. If you cannot ping it, ensure the check box is left cleared. Then, change the default host check for the network device. See Changing Host Checks for more information.

     • Exports NetFlow Data to Scrutinizer?
       If Scrutinizer has been integrated with up.time, and is also receiving NetFlow data from the network device, select this check box. You will then be able to call a Scrutinizer instance directly from the network device's Graphing tab in up.time.

     SNMP details can be globally configured in the Global Element Settings page on the Config tab. If these have been done, and the Use Global SNMP Connnection Configuration check box is selected, none of these options will appear, or need to be configured.

   • Novell NRM
     Complete the following fields:
     
     • Port
       The port on which the NRM is listening. By default, the non-SSL port is 8008, and when SSL is used, the port is 8009.
     • Use SSL
       Select this check box if you want to securely communicate with the NRM.
     • Username
       The user name that is required to access the Novell NRM Web interface.
     • Password
       The password that is required to access the Novell Web interface.

   • pSeries LPAR Server (HMC)
     If you are adding a pSeries server that is managed by a Hardware Management Console, complete the following fields:

     Although you can manually add HMC-managed pSeries servers, we recommend using the Auto Discovery process as this will add all the pSeries servers managed by the HMC, and automatically populate their respective managed server names. See Auto Discovery for HMC-Managed pSeries Servers for more information.

      

     
     
     • HMC Host Name
       The host name of the Hardware Management Console that is managing the pSeries server.

     • Managed Server
       The HMC's unique identifier for the pSeries server. This information can be retrieved from the HMC itself (e.g., by running lssyscfg -r sys -F name).

       For HMC-managed pSeries servers, the above two fields are used in conjunction with the Host Name field. The pSeries Host Name and Managed Server name identify the p frame on the network, and within the HMC cluster, respectively. The HMC Host Name is required to identify the Hardware Management Console in order to retrieve some configuration and workload information about the pSeries server.

     • Username
       The username required to log in to the HMC.
     • Password
       The password used to access the HMC.
   • pSeries LPAR Server (VIO)
     If you are adding a pSeries server that is not managed by an HMC, but instead communicates with the up.time Agent on a Virtual I/O server that's using IVM (Integrated Virtual Manager), configure the following:
     
     • Port
       The port on which the up.time Agent is listening.
     • Use SSL
       Select this check box if you want to securely communicate with the up.time Agent.

     Information for the up.time Agent on the Virtual I/O server can be globally configured in the Global Element Settings page on the Config tab. If this has been done, and the Use up.time Agent Global Configuration check box is selected, the agent port and SSL options will not appear.

   • VMware ESX
     Complete the following fields:
     
     • Username
       The user name required to log into the VMware ESX server.
     • Password
       The password required to log into the VMware ESX server.
   • VMware vCenter Server
     Complete the following fields:
     
     • Web Services Port
       The port that the VMware vCenter Web Service uses to communicate with up.time.
     • Username
       The name of the VMware vCenter administrator account.
     • Password
       The password for the VMware vCenter account.
     • In the vSync Settings - Virtual Machines section, indicate whether you would like up.time to Collect Virtual Machine data.
       If you choose to ignore VMs in the VMware vCenter inventory by deselecting this check box, skip to the next configuration point; otherwise, configure how up.time's vSync will work with a vCenter's inventory of VMs.
       
       • Select the Collect up.time Agent data or Collect WMI Agentless data (if you are using data collection via WMI) to enable additional monitoring for VMs that are using the up.time Agent or WMI. (See Standalone Monitoring for vCenter VMs for more information.) If you have defined global Agent or WMI settings in the up.time Config panel, you can select the Use up.time Agent Global Configuration or Use WMI Global Configuration check box accordingly; otherwise, configure the appropriate fields: 
         
         • For the up.time Agent, indicate the Port on which it is listening, and whether it will Use SSL to communicate securely with up.time.
         • For data collection via WMI, indicate the Window Domain on which WMI has been implemented, and the Username and Password required for access.
       • Indicate whether up.time should Notify on newly discovered VMs, then select the desired Alert Profile and Action Profile.
         If enabled, up.time can send notifications about, or perform scripted actions in response to, new VMs discovered in the VMware vCenter inventory during a vSync operation. (For more information, see Managing vSync.)
     • vSync Settings - vSphere ESX Hosts section, indicate whether up.time should Notify on new discovered hosts, then select the desired Alert Profile and Action Profile.
       If enabled, up.time can send notifications about, or perform scripted actions in response to, new ESX hosts discovered in the VMware vCenter inventory during a vSync operation. (For more information, see Managing vSync.)
   • WMI Agentless
     Complete the following fields:
     
     • Windows Domain
       The Windows domain in which WMI has been implemented.
     • Username
       The name of the account with access to WMI on the Windows domain.

     • Password
       The password for the account with access to WMI on the windows domain.

     WMI information can be globally configured in the Global Element Settings page on the Config tab. If these have been done, and the Use WMI Global Credentials check box is selected, none of these options will appear, or need to be configured.

7. If you want to associate this system with a group, select the name of the group from the Group dropdown list.
   See Working with Groups for more information on defining groups.
8. If you want to associate this system with a service group, select the name of the group from the Service Group dropdown list.
   See Service Groups for more information.
9. Click Save.
   A window listing general information about the system you have added appears.
10. If you want to add another system or network device, click Add Another. Then, repeat the previous steps in this section. Otherwise, click Close.
11. Click Save.

Net-SNMP

The up.time SNMP monitor also supports Net-SNMP, which is a suite of command line and graphical applications that do the following:

• request information from SNMP agents
• set information on SNMP agents
• generate and handle SNMP traps

To take advantage of the Net-SNMP features, you must:

• Install and configure the Net-SNMP application suite on your server. Visit http://net-snmp.sourceforge.net for more information:
• Have a Net-SNMP agent already installed on the host or hosts that you want to monitor. The Net-SNMP HOST-RESOURCES-MIB (used to gather performance statistics from a host) must also be enabled. See the Net-SNMP documentation for details.
• Add a Net-SNMP Element to up.time . For more information, see Adding Systems or Network Devices.

Supported Versions of SNMP

The up.time SNMP monitor works with the following versions of SNMP:

• v2

The second implementation of the SNMP protocol, which contains additional protocol operations as well as improved security and data authentication.

• v3

The latest implementation of the SNMP protocol, which adds security and privacy features that are missing in versions 1 and 2 of the protocol.

See SNMP Poller and Network Device Port Monitor for more information.

WMI Requirements

In order to monitor agentless systems through WMI in a secure environment (e.g., through a firewall), you need to create an exception for WMI on the host end. Consult the Microsoft documentation or developer resources for information on connecting to WMI on a remote computer.

Adding a WMI System to up.time

To add an agentless WMI system to up.time , do the following:

1. On the up.time tool bar, click My Infrastructure , then click Add System/Network Device .
2. Complete the Display name in up.time and Description fields.
   See Adding Systems or Network Devices for more information.
3. Select WMI Agentless from the Type of System/Device dropdown list.
4. In the Host Name field, enter the actual name or IP address of the machine that up.time will be monitoring.
5. Select the Use WMI Global Credentials check box if they have been configured, and you would like to use them (see Configuring Global WMI Credentials for more information); otherwise complete the following fields:
   
   • Windows Domain
     The Windows domain in which WMI has been implemented.
   • Username
     The name of the account with access to WMI on the Windows domain.
   • Password
     The password for the account with access to WMI on the windows domain.
6. If you want to associate this system with a group, select its name from the Group dropdown list.
7. If you want to associate this system with a Service Group, select its name Service Group dropdown list.
8. Click Save .

Switching an Element to WMI Data Collection

To change the data collection source for an individual Windows Element from the up.time Agent to WMI, do the following:

Switching an Element to Agent-Based Data Collection

To change the data collection source for an individual Windows Element from WMI to the up.time Agent, do the following:

Converting Multiple Elements to WMI Data Collection

To change multiple agent-based Elements to use WMI for data collection, do the following

Converting Multiple Elements to Agent-Based Data Collection

To change multiple WMI Elements to use the up.time Agent for data collection, do the following

1. Ensure a global up.time Agent configuration exists (see Configuring Global WMI Credentials for more information).
2. On the up.time tool bar, click Config .
3. In the tree panel, click Bulk Element Conversion .
4. In the WMI Elements section, select the check boxes that correspond to the WMI Elements whose data collection method is to be changed to the up.time Agent.
5. Click Convert to Agent.
   When the conversion is complete, the lists of agent-based and WMI Elements will be refreshed to reflect the changes.

Adding a Novell NRM System to up.time

To add a Novell NRM version 6.5 system to up.time , do the following:

1. On the up.time tool bar, click My Infrastructure and then click the Add System/Network Device tab.
2. Complete the Display name in up.time and Description fields.
   See Adding Systems or Network Devices. for more information.
3. Select Novell NRM from the Type of System/Device dropdown list.
4. Complete the following fields:
   
   • Host name
     The actual name of the machine that up.time will be monitoring, or the IP address of the machine.
   • Port
     The port on which the NRM is listening. The default is 8008 for a port that is not using SSL. The default for a port that is using SSL is 8009 .
   • Username
     The NRM administrator account name. This field is mandatory.

   • Password
     The NRM administrator password. This field is mandatory.

     The password is encrypted and stored in the up.time DataStore.

5. If you want to associate this system with a group, select its name from the Group dropdown list.
6. If you want to associate this system with a Service Group, select its name Service Group dropdown list.
7. Click Save .

NRM Statistics Captured by up.time

up.time captures the following Novell NRM system (version 6.5) statistics:

Each statistic returns one of the following statuses:

• Good

The statistic is well within the threshold suspect value.

• Suspect

The statistic is between the threshold good and critical values.

• Bad

The statistic is greater than the threshold critical value.

Hosts File Name-Value Pairs

The following table explains the properties you can include in a hosts file to describe Elements. The properties required to add a system or network device depends on the type of Element it will be. For example, to add an Agent-based system, you only need to provide information for Host Name, Type, and Port. (For more information, see Working with Elements for a summary of Element types, and Adding Systems or Network Devices for configuration information by Element type.)

Adding Multiple Systems to up.time

To add multiple systems to up.time, do the following:

1. Copy the hosts file to the directory in which you installed the up.time Monitoring Station.
2. At the command line, navigate to the scripts folder.
   For example, if you installed the Monitoring Station in the default location on a Windows system, navigate to the following folder:
   C:\Program Files\uptime software\uptime\scripts\
3. Enter the following command:
   addsystem <path_and_filename>
   Where <path_and_filename> is the name of, and full path to, the text file that contains the list of systems that you want to add to up.time.
   The systems listed in the file are added to up.time, unless one of the following occurs:
   
   • up.time cannot connect to the system
   • the system does not exist in your environment
   • the system has already been added to up.time

   If you have deployed up.time UI instances, ensure you always run command-line scripts such as addsystem on the primary Monitoring Station that is actually performing data collection.

1. In the My Infrastructure panel, click Add Application .
2. In the Add Application window, enter a descriptive name for the Application in the Name of Application field.
   This name will appear in both the My Infrastructure panel and Global Scan dashboard.
3. Optionally, enter a description for the Application in Description of Application field.
4. Optionally, select the group of systems in your up.time environment with which this system will be associated from the Parent Group dropdown list.
   By default, the Application is added to the My Infrastructure group.
   For more information on groups, see Working with Groups.
5. In the Application Status section, define how many master service monitors must be in a warning- or critical-level state to affect the Application as a whole.
   You can include a defined number, a percentage or all master service monitors in this condition.
6. Select one of the following options from the dropdown list above the Available Master Service Monitors list:
   
   • the name of a specific system, which displays all its service monitors
   • All , which displays all service monitors for every system in your environment
7. Select one or more of the service monitors from the Available Master Service Monitors list, and then click Add .
8. Select one of the following options from the dropdown list above the Available Regular Service Monitors list:
   
   • the name of a specific system, which displays all its service monitors
   • All , which displays all service monitors for every system in your environment
9. Select one or more of the service monitors from the Available Regular Service Monitors list and then click Add .
10. Click Save .
    After closing the Add Application window, the name of the newly created Application appears in the My Infrastructure panel as a link that can be clicked to view the Application’s details.
11. If required, associate Alert Profiles with the Application by clicking Edit Alert Profiles when viewing the Application’s details.
12. In the Alert Profile Selector pop-up window, select one or more of the Available Alert Profiles from the list, then click Save .
13. If required, associate Action Profiles with the Application by clicking Edit Action Profiles when viewing the Application’s details.
14. In the Action Profile Selector pop-up window, select one or more of the Available Action Profiles from the list, then click Save .

To add a nested group, do the following:

1. In the My Infrastructure panel, click Add Group .
2. Enter a descriptive name for the group in the Group Name field.
3. Optionally, enter a description of the group in the Group Description field.
4. Select the group with which the new one will be associated from the Parent Group dropdown list.
5. To give this nested group its own subgroups, select one or more entries from the Available Groups list, then click Add .
6. Select the Elements that you want to add to this group from the Available Elements list, and then click Add .
7. Select one or more sets of users who can view this group from the Available User Groups list, and then click Add .
8. Click Save .

Adding a Nested View

To add a nested view, do the following:

1. In the Infrastructure panel, click Add View .
2. In the Add View window, enter a descriptive name in the View Name field.
   This name will appear when listing views in the Infrastructure panel.
3. Optionally, enter a description in View Description field.
4. In the Parent View dropdown list, select the view to which this nested view will be subordinate.
5. To give this nested view its own child views, select one or more entries from the Available Element Views list, then click Add .
6. Select one or more users who can view this group from the Available Users list, then click Add .
7. To add previously defined groups of users, select one or more entries from the Available User Groups list, then click Add .
8. Click Save .