4.5 Defining and adding objects
4.5.1.2 Defining objects via the browser The browser consists of two parts:The browser consists of two parts:
– The left section of the window shows the network entities that serve as starting points for a search operation.
– The right section of the window shows the objects of the selected network entity. The name of the server with a prefix consisting of two status icons, the network address, the type description and a comment are output. The network address, type description and comment are only output if ServerView Operations Manager is able to identify them.
I
If a BMC has not been assigned a server name, the IP address is shown here.In the lower left-hand area of the window enter
1. which subnet or domain is to be searched for objects.
I
Domains can only be searched under Windows. Under Linux you can only search subnets.I
When searching a domain, please bear the following in mind:– Searching a domain can take some time. The time required for a search can differ depending on the attempt.
– The results list can differ depending on the Windows Application Programming Interface (WinAPI).
2. which community is to be used. This is the community that was specified during SNMP configuration on the managed server.
I
You can specify several communities, one after the other, separated by commas. If the community string already contains a comma, the comma must be masked with a backslash ’\’ beforehand (e.g.commwith\,string). Bear in mind that specifying a large number of communities slows down the search process. Equally, any access with an incorrect community can cause an Authentication failure alarm.
By default your own subnet and the community public are entered.
Starting the search
You start the search by clicking the Start Browsing button. You can also use this button to cancel the search procedure (Stop Browsing) while it is in progress. At the end of the search the objects found are displayed in order of ascending IP address. The icons in front of the names show the object type. An icon in the first column identifies the objects already present in the server list.
I
● ServerView also identifies VMware ESX servers V3.x, provided that the service ServerView Services (Windows) or SV Services (Linux) can establish a connection to the VMware server based on a valid user/password combination. To do this, the service ServerView Services (Windows) or SV Services (Linux) searches the user/password list created under ServerView Operations Manager (see chapter "Creating a user/password list" on page 331).● ServerView will only identify a BMC if the service ServerView Services (Windows) or SV Services (Linux) can establish a connection to the BMC based on a valid user/password combination.
To do this, the service ServerView Services (Windows) or SV Services (Linux) searches the user/password list created under ServerView Operations Manager (see chapter "Creating a user/password list" on page 331).
● The browser only displays BMCs from Fujitsu in the list. An icon in the first column in front of a BMC indicates that either the BMC or the associated server is already entered in the server list.
● The browser recognizes Citrix XenServer servers / Xen servers and KVM servers and marks them with the corresponding icon in the second column. The associated virtual servers are indicated by PRIMERGY XEN VM or PRIMERGY XEN VK.
Citrix XenServer servers / Xen servers and KVM servers do not always provide IP addresses for the associated virtual servers. But the IP address is required in order to find out the agent status of the
the KVM group automatically on the basis of the UUID or MAC address. The virtual servers in the group therefore get an IP address and their status can be determined.
● ServerView identifies Hyper-V servers, provided that the service ServerView Services (Windows) or SV Services (Linux) can establish a connection to the Hyper-V server based on a valid user/password combination. To do this, the service ServerView Services (Windows) or SV Services (Linux) searches the user/password list created under ServerView Operations Manager (see chapter "Creating a user/password list" on page 331).
If the browser recognizes Hyper-V servers, it marks them with the corresponding icon in the second column. The associated virtual servers are marked as PRIMERGY HYPER-V.
The IP address is required in order to find out the agent status of the virtual servers. So that Hyper-V Server provides IP addresses of the virtual servers the following conditions must be met:
– The VM guest must be running. This requires that in WMI in the class Msvm_ComputerSystem the property EnabledState is set to Enabled.
– The VM guest must have current integration modules installed.
– VM guests running Windows Server 2008 R2 or higher already have appropriate versions of integration modules. For Windows Server 2008 VM guests and earlier, the integration modules must be upgraded.
If these conditions are not made, Hyper-V servers will not provide the IP addresses for the associated virtual servers. Then, the IP address can be assigned to a virtual server in the following ways:
– You can define the IP address later via the Server Properties window.
– You can insert the systems marked PRIMERGY HYPER-V into the server list. ServerView Operations Manager can then assign the servers to the Hyper-V group automatically on the basis of the UUID or MAC address. The virtual servers in the group therefore get an IP address and their status can be determined.
● The browser recognizes servers with Agentless Service based on the IPMI or SNMP protocols and stores this information in the ServerView database. The protocols provided by the servers with Agentless Service are added to the server list.
Network instances which have been successfully searched are displayed in a small window next to the list of located objects.
Assigning a server type
If you select the option Automatic in the selection list in the top right, each of the selected objects will be assigned the server type that has been
automatically determined by the browser.
I
Storage subsystems are recognized as follows:You can also define the server type yourself (e.g. server, blade server, cluster, PRIMEPOWER, storage). Select Other for other TCP/IP devices such as printers.
I
If you want to add hosts with virtualization software (e.g. VMware, Hyper-V, Xen) as normal server without virtual features, you must select type Server in the selection list or disable VM Host Discovery in the VM Discovery step of the Base Configuration Wizard.Storage subsystem Recognized server type
CentricStor FS CentricStor FS
ETERNUS DX60/ DX80/ DX90 ETERNUS DX60/80/90 ETERNUS DX400/ DX8000 ETERNUS DX400/8000
Table 57: Server types of the storage subsystems
Possible sources of error during searches
Under certain circumstances, errors may occur during browser operation. There are many possible reasons for this:
● ServerView Operations Manager can only find computers that are powered up.
● Some items of network information are sometimes not recognized when the Microsoft Windows Network is searched. This depends on the method used by Microsoft Windows to obtain network information (i.e. on the broadcast method).
● A subsystem may not be accessible due to security measures. In addition, a subsystem may not be available because the subsystem server cannot be accessed. In such cases, the search operation is terminated when the time limit is exceeded. However, this may take several minutes.
● Other network systems may not be available for similar reasons.
● If a server is labelled as unknown even though its IP address is known, then the computer is inactive or a network error has occurred.
● If it takes a long time to resolve the computer name into the IP address, then it is possible that WINS or DNS is not properly configured on the login computer. It is possible that the addresses of the primary or secondary WINS servers or the addresses of the DNS servers are invalid. If the WINS protocol has not been activated correctly, then IP address resolution is performed using the very slow broadcast name query procedure. You can configure WINS and DNS using the TCP/IP parameters in the network settings.
● There may be a variety of reasons why it was not possible to find any IP addresses:
– TCP/IP is not installed on the remote computer.
– WINS has not been activated on the computer at which you have logged
– If the address could not be resolved by WINS, DNS or via LMHOSTS files, then a broadcast name query is performed. Such queries may fail due to the network topology or because of performance problems if, for example, the routers in a subsystem do not forward the broadcast name queries.
● If virtual systems are not recognized, either the user/password combination could be wrong or the virtual system might not have some of the conditions ServerView needs in order to recognize and query it.