Ok - then when the status is Down - I read in the BMC documentation is
defined as the CI is down, but not yet in maintenance. Down is not a
location that describes where the asset is at. It's a little confusing.
So the user is marking any server that is not pingable as down. But the
Maybe I am getting confused with the pingable statement.
CMDB is not pinging anything, Configuration Discovery does not ping anything
Foundation discovery will ping something, but I have never seen an asset in
the down status due to the FD not reaching a host that it previously created
a CI for.
: public.remedy.arsystem.general
To: arslist@ARSLIST.ORG
Sent: Wednesday, February 03, 2010 4:10 PM
Subject: Re: Discovery and CMDB
**
Maybe I am getting confused with the pingable statement.
CMDB is not pinging anything, Configuration Discovery does not ping anything
Foundation
If a server was discovered and marked as deployed and then later is not
pingable - what status would you give this server?
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum
the cmdb assets are based on where they are at, not whether they are up?
monitoring is one side (Patrol, Ca-unicenter, Whatever) up / down and
overall status uptime etc.
Asset is different: ordered, recieved, being assembled, deployed, in-repair,
down, endof life, transferred, delete, in
to do. please provide the results as soon as possible.
--
View this message in context:
http://www.nabble.com/syncronising-topology-discovery-with-CMDB.-tf4935674.html#a14127490
Sent from the ARS (Action Request System) mailing list archive at Nabble.com
discovery with CMDB.
From: anuar [EMAIL PROTECTED]
Date: Mon, December 03, 2007 6:02 am
To: arslist@ARSLIST.ORG
we have installed topology discovery discovered CI's and followed the
syncronising steps to synchronise with CMDB. but we are unable to see any
results in the CMDB console of user tool
7 matches
Mail list logo
