Microsoft KB Archive/883335

= Event IDs 21249 and 21248 are logged in the application event log on a computer that is running Microsoft Operations Manager =

Article ID: 883335

Article Last Modified on 10/27/2006

-

APPLIES TO


 * Microsoft Operations Manager (MOM) 2005
 * Microsoft Operations Manager 2000 Service Pack 1

-





SYMPTOMS
When you view the application event log on a computer that is running Microsoft Operations Manager (MOM) 2000 or MOM 2005, two events that describe the same problem but that have different event IDs are logged in the application event log:

Type: Warning

Time: 10/26/2003 9:55:26 PM

Computer:

Source: Microsoft Operations Manager

Event Id: 21249

Category:

Provider Type: Event Log

Provider Name: Application

Domain:

Logged On Name:

Logged On Domain:

User: SYSTEM

Description:

The Agent was unable to contact the Consolidator on

Details: Sending management data

IsConsolidated:

False IsAlerted: False

Note Event ID 21249 is generated when the MOM primary consolidator cannot be contacted.

Type: Warning

Time: 10/26/2003 9:55:26 PM

Computer:

Source: Microsoft Operations Manager

Event Id: 21248

Category:

Provider Type: Event Log

Provider Name: Application

Domain:

Logged On Name:

Logged On Domain:

User: SYSTEM

Description: The Agent was unable to contact any Consolidator. The last attempt to connect to  failed.

Details: Sending management data

IsConsolidated: False

IsAlerted: False

Note Event ID 21248 is generated when the MOM secondary consolidators that are listed in the MOM agent registry cannot be contacted.



CAUSE
This problem occurs when the MOM 2000 or MOM 2005 agent cannot communicate with the MOM 2000 Data Access Server/Consolidator-Agent Manager (DCAM) server or the MOM 2005 Management Server. This typically occurs because of network problems.



RESOLUTION
To resolve this problem, use the ping command to try to ping the MOM consolidator by name. If this does not work, use the ping command with the -a switch. This resolves the IP address of the MOM DCAM server or the MOM 2005 Management Server to its host name. To do this, follow these steps:  On the computer that has the MOM 2005 agent installed, click Start, click Run, type cmd, and then click OK At the command prompt, type ping, where   is the name of the computer that is the listed in the Computer: field in the event warning message that is described in the &quot;Symptoms&quot; section. Note the IP address that is returned. If the ping response is successful, you must now verify that the IP address that is returned is the actual IP address of the MOM server by using the ping command with the -a switch. To do this, follow these steps:  At the command prompt, type ping -a, where   is the IP address from step 2. An example is ping -a 10.10.1.10 . The output of ping -a  must match the MOM server name. If the IP address matches the MOM server name, go to step 8. If the output does not match the MOM server name, go to the next step. </li> If the output of the ping -a command does not match the name of the MOM server, the MOM agent cannot resolve the MOM server name to the correct IP address. This problem may for any one of the following reasons: <ul> The local DNS client cache has stale DNS entries for the IP address. For example, the IP of the MOM server changes, but the MOM agent still has a cached name resolution entry for the old IP. This old IP is now used by another computer. Because of this, the ping –a IP address resolves to a computer name other than the MOM server.</li> The MOM agent computer contains a Hosts file in the %Windir%\System32\Drivers\Etc folder that contains an entry that adjusts the name resolution table for the IP address to the wrong computer name.</li> The DNS or WINS server that the MOM agent computer uses for name resolution contains a stale or incorrect entry.</li></ul>

The remaining steps can help determine whether the name resolution problem is local to the MOM agent computer or if it exists in the name resolution service, and may affect other MOM agent computers.

Note Two examples of such name resolution services are DNS and WINS.</li> Determine whether the name resolution problem is local to the MOM agent computer or if there is a problem with the name resolution service that the MOM agent computer uses. To do this, follow these steps:  On the computer that is running the MOM agent, click Start, click Run, type cmd, and then click OK.</li> At the command prompt, type the following commands. Press enter after you type each command. <ul>  Nbtstat -RR </li>  Ipconfig /flushdns </li></ul> </li> Remove any static entries for MOM server IP Address or MOM server name in the Hosts file that is contained in the \System32\Drivers\Etc folder on the MOM agent computer. You can change the Hosts file with Notepad.</li> Repeat step 3. The ping -a command is successful if the output matches the MOM server name. If it is successful, the local DNS cache on the MOM agent computer was at fault. Go to step 8. If the ping -a is unsuccessful, the MOM agent is still receiving incorrect name resolution information and you must go to step 6.</li></ol> </li> If the MOM agent computer still cannot resolve the correct IP address to the MOM server computer name, you must verify the name resolution services. To do this, follow these steps.

Note You must have access to the name resolution server to perform all the following steps.  On the MOM agent computer, click Start, click Run, type cmd, and then click OK.</li> At the command prompt, type the following to see a list of Primary and Secondary DNS servers and primary and secondary WINS servers:

ipconfig /all

</li> <li>If you are using WINS for name resolution log on to the WINS server, follow these steps: <ol style="list-style-type: lower-alpha;"> <li>Click Start, point Programs, point to Administrative Tools, and then click WINS.</li> <li>In the WINS snap-in, expand the WINS server name, right-click Active Registrations, and then click Find by Name.</li> <li>In the Find by name dialog box, type the name of the MOM server, and then click Find Now.</li> <li>Verify that the WINS entry for the MOM server points to the correct IP address. If the WINS record is incorrect, you can use WINS Help to resolve the problem. To access WINS Help, click the Help icon on the WINS menu bar.</li> <li>When you have resolved the name resolution, you must force WINS replication, and then repeat step 5.</li></ol> </li></ol> </li> <li>If you are using DNS for name resolution, log on to the DNS server, and then follow these steps: <ol style="list-style-type: lower-alpha;"> <li>Click Start, point to Programs, point to Administrative Tools, and then click DNS.</li> <li>In the DNS snap-in, expand the DNS server name, expand Forward Lookup Zones, and then click the zone name that contains the DNS entry for the MOM server.</li> <li>In the right pane of the DNS snap-in, make sure that the MOM server name points to the correct IP address. If the DNS record is incorrect, you can use DNS Help to resolve the problem. To access DNS Help, click the Help icon on the DNS menu bar.</li> <li>When you have resolved the name resolution problem, repeat step 5.</li></ol> </li> <li>If you have confirmed that the MOM agent can resolve the IP address and the MOM server name correctly, and the problem still exists, you must verify that the MOM agent service is communicating correctly with the MOM server by using telnet to connect to port 1270 on the MOM server. To do this, follow these steps.

Note The TCP port can be configured by using the MOM Administrative console. The value for the port can be found in Global Settings, under Communications. <ol style="list-style-type: lower-alpha;"> <li>On the MOM agent computer, click Start, click Run, type cmd, and then click OK.</li> <li>At the command prompt, type the following: telnet  1270, where   is the IP address of the computer that is running MOM.</li> <li>If the connection is successful, a blank command line window appears. This shows that the port that the MOM agent requires is open and listening on the computer that is running MOM.</li> <li>If the telnet command fails, the following response is returned:

Connecting To ...Could not open connection to the host on port 1270: Connect failed.

In this case, you must verify the following: <ul> <li>That there are no IPSec policies that prevent communication.</li> <li>That there are no local IPSec filters configured on any network adapters that prevent communication on port 1270 UDP and TCP.</li> <li>There are no Access Control List (ACL) entries on the firewall, on the router, or on the Switch that prevent communication between the MOM agent and the MOM server.

To find which ports must be opened for communication between the MOM agent and the MOM server, see the Microsoft Operations Manager 2005 Security Guide. To view the Microsoft Operations Manager 2005 Security Guide, visit the following Microsoft Web site:

http://www.microsoft.com/technet/prodtechnol/mom/MOM2005/Library/3e039637-4639-46f7-9f5f-518e0c04795e.mspx

</li></ul> </li></ol> </li> <li>If you have confirmed that the MOM agent can resolve the name of the MOM server and that the MOM server that is listening on port 1270, but the problem still exists, contact Microsoft Product Support (PSS).</li></ol>

<div class="status_section">

STATUS
This behavior is by design.

Keywords: kbtshoot kbprb KB883335

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.