| Author |
Message |
slim
Guest
|
 Posted:
Wed Oct 26, 2005 12:51 am Post subject:
Computer discovery/monitoring only by Netbios name or DNS na |
|
|
I have a little weird question. I have several servers running Windows
Server 2003, and they are clustered using Veritas clustering server.
When a veritas virtual group (virtual server) is online and running on
one of the machines, it will change the NetBios name of the server to
the name of the virtual server, and this is giving me troubles.
For instance, lets say that the DNS name of the server is US-SERVERX-1.
And that the Veritas virtual server name is US-VIRTUAL-1. When the
US-VIRTUAL-1 is not enabled and running, everything is fine. I have
installed the agent on US-SERVERX-1, and monitoring it fine and dandy.
However, when the US-VIRTUAL-1 comes online on US-SERVERX-1, it will
change the NetBios name of US-SERVERX-1 to US-VIRTUAL-1. ( The
computer name still shows US-SERVERX-1.domain.com, but lets say I click
on the Device Manager, and the System name at top will be changed to
US-VIRTUAL-1).
Since the netbios name changed, MOM thinks that the server is down, and
no monitoring is done from this point on. The bigger trouble is, I
cannot discover and install agents on the machine, since the names do
not match. Bottom line, I need to monitor both US-SERVERX-1 and
US-VIRTUAL-1 when it is online. Is there any way this can be
accomplished?
Thank you, and please let me know if you need me to provide more
details or if anything does not make sense... |
|
| Back to top |
|
 |
Daniel Lai [MVP-Managemen
Guest
|
| Posted:
Wed Oct 26, 2005 12:51 am Post subject:
Re: Computer discovery/monitoring only by Netbios name or DN |
|
|
Hello,
Thank you for your posting!
After you install the agent on the physical cluster nodes, the virtual
cluster servers are added to the Administration\Computers\Windows Server
Cluster Computers node in the MOM 2005 Administrator Console. It can take
several minutes and possibly up to 30 minutes for the virtual servers to be
added to this node. After the virtual cluster servers are added, right-click
each server and then click Start Managing. In the MOM Operator Console, the
state for these virtual servers should change to success.
To fully monitor server clusters, install the Server Clusters Management
Pack for MOM 2005
If you have any questions, please feel to let me know. I am glad to be of
assistance.
--
Daniel Lai
Microsoft MVP Program Top Contributor
Windows Server-Management Infrastructure
Microsoft Management Solution Consultant
http://msmvps.com/daniel
"slim" <gte176f@gmail.com> wrote in message
news:1130274588.510064.172580@o13g2000cwo.googlegroups.com...
| Quote: | I have a little weird question. I have several servers running Windows
Server 2003, and they are clustered using Veritas clustering server.
When a veritas virtual group (virtual server) is online and running on
one of the machines, it will change the NetBios name of the server to
the name of the virtual server, and this is giving me troubles.
For instance, lets say that the DNS name of the server is US-SERVERX-1.
And that the Veritas virtual server name is US-VIRTUAL-1. When the
US-VIRTUAL-1 is not enabled and running, everything is fine. I have
installed the agent on US-SERVERX-1, and monitoring it fine and dandy.
However, when the US-VIRTUAL-1 comes online on US-SERVERX-1, it will
change the NetBios name of US-SERVERX-1 to US-VIRTUAL-1. ( The
computer name still shows US-SERVERX-1.domain.com, but lets say I click
on the Device Manager, and the System name at top will be changed to
US-VIRTUAL-1).
Since the netbios name changed, MOM thinks that the server is down, and
no monitoring is done from this point on. The bigger trouble is, I
cannot discover and install agents on the machine, since the names do
not match. Bottom line, I need to monitor both US-SERVERX-1 and
US-VIRTUAL-1 when it is online. Is there any way this can be
accomplished?
Thank you, and please let me know if you need me to provide more
details or if anything does not make sense...
|
|
|
| Back to top |
|
|
slim
Guest
|
| Posted:
Wed Oct 26, 2005 6:43 am Post subject:
Re: Computer discovery/monitoring only by Netbios name or DN |
|
|
Hi Daniel,
Thank you for your reply. However, the servers are clustered using
Veritas Cluster Server (Veritas Storage Foundation for Windows to be
exact) as mentioned in my post, and not using Microsoft Server
Clustering. I have looked at the Management Pack for Windows Server
Clusters, and have also installed it, but as expected, it does not do
anything for me... Does anyone have any experience with MOM and
Veritas Clusters?
Thank you,
Lim.
Daniel Lai [MVP-Management Infrastructure] wrote:
| Quote: | Hello,
Thank you for your posting!
After you install the agent on the physical cluster nodes, the virtual
cluster servers are added to the Administration\Computers\Windows Server
Cluster Computers node in the MOM 2005 Administrator Console. It can take
several minutes and possibly up to 30 minutes for the virtual servers to be
added to this node. After the virtual cluster servers are added, right-click
each server and then click Start Managing. In the MOM Operator Console, the
state for these virtual servers should change to success.
To fully monitor server clusters, install the Server Clusters Management
Pack for MOM 2005
If you have any questions, please feel to let me know. I am glad to be of
assistance.
--
Daniel Lai
Microsoft MVP Program Top Contributor
Windows Server-Management Infrastructure
Microsoft Management Solution Consultant
http://msmvps.com/daniel
"slim" <gte176f@gmail.com> wrote in message
news:1130274588.510064.172580@o13g2000cwo.googlegroups.com...
I have a little weird question. I have several servers running Windows
Server 2003, and they are clustered using Veritas clustering server.
When a veritas virtual group (virtual server) is online and running on
one of the machines, it will change the NetBios name of the server to
the name of the virtual server, and this is giving me troubles.
For instance, lets say that the DNS name of the server is US-SERVERX-1.
And that the Veritas virtual server name is US-VIRTUAL-1. When the
US-VIRTUAL-1 is not enabled and running, everything is fine. I have
installed the agent on US-SERVERX-1, and monitoring it fine and dandy.
However, when the US-VIRTUAL-1 comes online on US-SERVERX-1, it will
change the NetBios name of US-SERVERX-1 to US-VIRTUAL-1. ( The
computer name still shows US-SERVERX-1.domain.com, but lets say I click
on the Device Manager, and the System name at top will be changed to
US-VIRTUAL-1).
Since the netbios name changed, MOM thinks that the server is down, and
no monitoring is done from this point on. The bigger trouble is, I
cannot discover and install agents on the machine, since the names do
not match. Bottom line, I need to monitor both US-SERVERX-1 and
US-VIRTUAL-1 when it is online. Is there any way this can be
accomplished?
Thank you, and please let me know if you need me to provide more
details or if anything does not make sense...
|
|
|
| Back to top |
|
|
Daniel Lai [MVP-Managemen
Guest
|
| Posted:
Wed Oct 26, 2005 12:50 pm Post subject:
Re: Computer discovery/monitoring only by Netbios name or DN |
|
|
Hello,
Thank you for your posting!
As i know, Veritas Storage Foundation for Windows support SNMP, So, You can
forward the SNMP trap to the SNMP Receiver (MOM Agent Computer) to let MOM
to monitor the cluster.
For more inforamtion how to configure SNMP and MOM, Please refer to my Blog.
http://msmvps.com/daniel
If you have any questions, please feel to let me know. I am glad to be of
assistance.
--
Daniel Lai
Microsoft MVP Program Top Contributor
Windows Server-Management Infrastructure
Microsoft Management Solution Consultant
http://msmvps.com/daniel
"slim" <gte176f@gmail.com> wrote in message
news:1130291025.762138.236440@z14g2000cwz.googlegroups.com...
| Quote: | Hi Daniel,
Thank you for your reply. However, the servers are clustered using
Veritas Cluster Server (Veritas Storage Foundation for Windows to be
exact) as mentioned in my post, and not using Microsoft Server
Clustering. I have looked at the Management Pack for Windows Server
Clusters, and have also installed it, but as expected, it does not do
anything for me... Does anyone have any experience with MOM and
Veritas Clusters?
Thank you,
Lim.
Daniel Lai [MVP-Management Infrastructure] wrote:
Hello,
Thank you for your posting!
After you install the agent on the physical cluster nodes, the virtual
cluster servers are added to the Administration\Computers\Windows Server
Cluster Computers node in the MOM 2005 Administrator Console. It can take
several minutes and possibly up to 30 minutes for the virtual servers to
be
added to this node. After the virtual cluster servers are added,
right-click
each server and then click Start Managing. In the MOM Operator Console,
the
state for these virtual servers should change to success.
To fully monitor server clusters, install the Server Clusters Management
Pack for MOM 2005
If you have any questions, please feel to let me know. I am glad to be of
assistance.
--
Daniel Lai
Microsoft MVP Program Top Contributor
Windows Server-Management Infrastructure
Microsoft Management Solution Consultant
http://msmvps.com/daniel
"slim" <gte176f@gmail.com> wrote in message
news:1130274588.510064.172580@o13g2000cwo.googlegroups.com...
I have a little weird question. I have several servers running Windows
Server 2003, and they are clustered using Veritas clustering server.
When a veritas virtual group (virtual server) is online and running on
one of the machines, it will change the NetBios name of the server to
the name of the virtual server, and this is giving me troubles.
For instance, lets say that the DNS name of the server is US-SERVERX-1.
And that the Veritas virtual server name is US-VIRTUAL-1. When the
US-VIRTUAL-1 is not enabled and running, everything is fine. I have
installed the agent on US-SERVERX-1, and monitoring it fine and dandy.
However, when the US-VIRTUAL-1 comes online on US-SERVERX-1, it will
change the NetBios name of US-SERVERX-1 to US-VIRTUAL-1. ( The
computer name still shows US-SERVERX-1.domain.com, but lets say I click
on the Device Manager, and the System name at top will be changed to
US-VIRTUAL-1).
Since the netbios name changed, MOM thinks that the server is down, and
no monitoring is done from this point on. The bigger trouble is, I
cannot discover and install agents on the machine, since the names do
not match. Bottom line, I need to monitor both US-SERVERX-1 and
US-VIRTUAL-1 when it is online. Is there any way this can be
accomplished?
Thank you, and please let me know if you need me to provide more
details or if anything does not make sense...
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in