Support Guide: SACM / Service Asset & Configuration Guide (Server)

Objective

  • Guide the development and implementation of robust Software Asset Management specifically tailored to server environments, helping to optimize software investments while ensuring compliance and reducing risks

Scope 

  • The scope of SACM for Servers is focused on infrastructure server assets
    • Server Inventory Management: Maintain an accurate and up-to-date inventory of server software assets 

Environment

  • 10374: TeamDynamix (CMDB) 
  • 12568: Service Asset & Configuration Management (SACM)

Automation

  • Puppet/Foreman is used for Linux and others are entered manually

Reviews/Audit 

  • Are completed at the discretion of the Linux and Windows Administration group 

User

  • IT Services

Environment

  • TeamDynamix (CMDB) Server Equipment

Server Device Attributes 

Below are key attribute names with their descriptions along with guidance and information about server assets.

 

Must

Crucial to the integrity of most or all CIs will be regularly audited for accuracy and completeness by the Practice Owner, Virtual Machines uses Name as the key field, where physical machines use Serial Number.

  • Form: Provides a template of fields to complete — Form Name: Server Cable
  • Name: The name of the asset as it appears on the Network
  • Status: Status of the asset — Key status are highlighted in BLUE
    • Inventory: Not actively in use but available for deployment 
    • Build Phase: Is in build process — ie. Network components that are in the process of build configuration phase and have not been implemented
    • In-Use: Active
    • Retired: No longer in use but not disposed
    • Disposed: No longer under control of Miami and removed from the environment 
    • Donated: No longer under the control of Miami and ownership transferred to another party
    • RMA: Device returned to vendor for replacement
    • Missing: The device is missing
  • Owner: The owner of the asset 
  • Owning Acct/Dept: Department responsible for the support of the asset
  • Product Model: Server (Set to Server with the form)
  • Serial Number
  • External ID:  Foreman path of the server as a location — external source path of the server

 

Should

  • Description: Description of the asset
  • Serial Number: Serial Number of the asset 
  • Location: Actual/physical location of the asset
  • Location Room: Define Space (such as a room number) where the asset is located
  • Maintenance Window: Used to determine when activities concerning the asset can be performed
  • Service Tag: Organization-defined tag for the asset
  • Attachment: Attachments associated with the asset
  • Server Environment: 
    • Development
    • Early-life Support
    • Pre-production
    • Production
    • Test
  • Server — Service Description Code: All codes should be three characters long

 

Could

  • Operating System
  • RAM: Amount of RAM present in the device
  • mu.server.numberCPU 
  • mu.server.disks 
  • mu.server.location.rack  
  • IP Address
  • VLAN
  • mu.server.FQDN
  • mu.server.IsVirtual
  • mu.server.ForemanLink
  • mu.server.Model
  • Health Status
    • Green
    • Yellow
    • Red

 

Print Article