Re: Tracking Vitrual Servers in Remedy AM 5.6

[Lammey, Peter A.]

Title: Tracking Vitrual Servers in Remedy AM 5.6

**

We were also thinking that is the best short term solution to track them as Assets but what Asset ID do you set for a VM server?

They are not really servers.  They are essentially just files that you setup and can copy and move to one physical server to another but its not a machine with a Serial or some other identification tag.

Not sure if there is something glaring with a Virtual server (some number perhaps) that you could use to uniquely identify it?  The only way we reference a VM server is by its name but that does seem like a good candidate for the Asset ID.

 

Thanks
Peter Lammey
ESPN MIT Technical Services & Applications Management
860-766-4761

 

---

From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Luebbe, Tom
Sent: Wednesday, November 08, 2006 1:36 PM
To: arslist@ARSLIST.ORG
Subject: Re: Tracking Vitrual Servers in Remedy AM 5.6

**

Are you using Topology to track the relationships?  I know it is very lacking in 5.6.  We have the virtual devices in as "Main Assets", since we treat them as such.  They all have the same life cycle that physical assets have.  Also, we can relate our Patrol monitoring to assets, but not Components. 

 

Tom Luebbe

 

---

From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Lammey, Peter A.
Sent: Wednesday, November 08, 2006 10:50 AM
To: arslist@ARSLIST.ORG
Subject: [ARSLIST] Tracking Vitrual Servers in Remedy AM 5.6

**

A Sever support person asked our Remedy team a good question about handling Virtual servers in regards to Asset Management tracking and Change ticket relationship.

Our infrastructure teams want to be able to track changes to Virtual servers and track that they have been moved from one server to another and essentially been relocated.

Virtual servers are not basically a physical object but merely a file system on a server so there does not seem to be a way to set a good unique ID for these.

The VMs sound like they would fit as a Asset Component to an Asset but Asset Components in the world of ITSM 5.6 cannot be related to Change tickets or Help Desk tickets but can only be related to an Asset record and the Asset record would be related to a Change.

The problem also seems to be that if you move a Virtual server from one location to another location to another server, if the Virtual server was tracked as a component then the component's Main Asset relationship would have to change.  This seems to be somewhat tedious.

Have any others determined the best way to handle this in Asset Management 5.6?
I figure that this is better handled in Atrium CMDB 2.0 but we will not be getting that for some time.

Thanks
Peter Lammey
ESPN MIT Technical Services & Applications Management
860-766-4761

__20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___