CMDB Creation
DOCUMENT CATEGORY: Runbook SCOPE: CMDB registration PURPOSE: Register assets in ServiceNow CMDB MASTER REFERENCE: ServiceNow Documentation
Overview
This section covers the creation of CMDB (Configuration Management Database) entries in ServiceNow for Azure Local implementations. Proper CMDB registration ensures accurate asset tracking and change management throughout the solution lifecycle.
ServiceNow (SNOW) Registration
Customer Solution Registration
Register the complete Azure Local solution in ServiceNow with the following information categories:
Solution Information
| Field | Description | Example |
|---|---|---|
| Customer CRM ID | Unique customer identifier | CRM-12345 |
| Solution Name | Azure Local solution name | AZLA-CustomerName-Site1 |
| Implementation Date | Go-live date | 2026-01-15 |
| Primary Contact | Customer technical contact | Name, email, phone |
| Azure Local Cloud Account Manager | Assigned account manager | Name, email |
Hardware Components
Register all physical hardware assets:
| Component | Required Fields |
|---|---|
| Dell AX Nodes | Serial numbers, model, firmware version |
| TOR Switches | Serial numbers, model, firmware version, management IPs |
| Management Switch | Serial number, model, management IP |
| Firewall (FortiGate) | Serial numbers (primary/secondary), firmware version |
| Console Server (OpenGear) | Serial number, management IP |
Software Components
Document all software versions:
| Component | Version Field |
|---|---|
| Azure Local Build | e.g., 2506 |
| Windows Server OS | e.g., 26100.4349 |
| Dell SBE Version | e.g., 4.2.2506.1600 |
| Arc Resource Bridge | Current version |
| Management Tools | WAC, PowerShell modules |
Configuration Details
Record deployment configuration:
- Network Configurations: VLANs, IP ranges, DNS, VPN settings
- Storage Configurations: Storage pool capacity, volume layout, encryption status
- Clustering Settings: Cluster name, node count, quorum configuration
- Azure Integration: Subscription IDs, resource group names, region
CMDB Best Practices
Ensure all configuration items (CIs) are properly linked and relationships are established between hardware, software, and service components for complete visibility and change tracking.
Relationship Mapping
Create CI relationships in ServiceNow:
Azure Local Solution (Parent)
├── Dell AX Nodes (Hardware CIs)
│ ├── Node 1 → connects to → TOR Switch 1, TOR Switch 2
│ ├── Node 2 → connects to → TOR Switch 1, TOR Switch 2
│ └── ... (all nodes)
├── Network Infrastructure (Hardware CIs)
│ ├── TOR Switch 1 → connects to → Firewall Primary
│ ├── TOR Switch 2 → connects to → Firewall Secondary
│ └── Management Switch → connects to → All management ports
├── Azure Subscription (Cloud CI)
│ ├── Azure Local Cluster Resource
│ ├── Arc Resource Bridge
│ └── Recovery Services Vault
└── Services (Service CIs)
├── Azure Site Recovery
├── Azure Backup
└── Azure Arc Management
Maintenance Schedule
| Activity | Frequency | Owner |
|---|---|---|
| CI Verification | Quarterly | Implementation Team |
| Firmware Version Updates | After each update | Operations Team |
| Relationship Validation | Semi-annually | CMDB Administrator |
| Full CMDB Audit | Annually | Compliance Team |
Related Documentation
Navigation
| Previous | Up | Next |
|---|---|---|
| ← Client Training & Handover | Lifecycle Operations | Deprovision Steps → |
Version Control
| Version | Date | Author | Changes |
|---|---|---|---|
| 1.0.0 | 2026-03-24 | Azure Local Cloudnology Team | Initial release |