VLAN and IP Address Management

IPAM (IP Address Management) centralizes network addressing management.

Why use IPAM?

• Complete visibility: All VLANs and IPs in one place
• Error prevention: Automatic conflict detection
• Capacity planning: Utilization rate monitoring
• Audit: Traceability of IP assignments

Scope

KaliaOps IPAM manages:

• VLANs: Network segments with configuration
• IP addresses: Assigned to assets
• IP history: Assignment timeline

Access

Menu CMDB → VLANs for VLAN list and management.

Addressing types

Environments

Categorize VLANs by environment:

Impact on organization

Filtering by environment allows:

• Finding all production VLANs
• Isolating test environments
• Security analysis by zone

The IPAM dashboard provides a global view of your network addressing.

Key metrics

• Total VLANs: Count of configured VLANs
• Total addresses: Sum of available IPs
• Assigned addresses: IPs assigned to assets
• Overall utilization: Usage percentage

Utilization per VLAN

For each VLAN, the dashboard shows:

• Progress bar with usage percentage
• Number of assigned/available addresses
• Color indicator (green/orange/red)

Thresholds

Subnet grid

The visual grid displays the IP address space:

• Occupied cells: Assigned addresses (with asset name)
• Free cells: Available addresses
• Reserved cells: Gateway, broadcast, DHCP

Navigation

• Click on an IP to see the assigned asset
• Use filters to show/hide reserved ranges
• Zoom on specific ranges for large networks

Information on hover

Hovering over an IP shows:

• Assigned asset name
• Assignment date
• Asset type

Free address search

The interface identifies:

• Next available IP
• Contiguous free ranges
• Gaps in addressing

KaliaOps automatically detects IP address conflicts.

Conflict types

• Duplicate IP: Same IP assigned to multiple assets
• Out of range: IP outside the VLAN network
• Reserved IP: Use of gateway or broadcast

Detection on creation

When assigning an IP to an asset:

• KaliaOps checks existing assignments
• Warning displayed if conflict detected
• Assignment blocked if duplicate

CMDB health rules

Predefined rules monitor conflicts:

• duplicate-ip-addresses: Detects duplicate IPs
• network-asset-without-vlan: Network assets without VLAN

Conflict resolution

If a conflict is detected:

1. Identify conflicting assets
2. Verify the correct assignment
3. Update or remove duplicate
4. Document the resolution

KaliaOps maintains a complete IP assignment history.

Recorded information

For each assignment:

• IP address: Assigned address
• Asset: Equipment that held this IP
• Assigned at: Start date
• Released at: End date (if applicable)
• Source: Manual, DHCP, Import, API
• User: Person who made the assignment

Use cases

• Security audit: Who had which IP on a given date?
• Forensics: Post-incident investigation
• Compliance: Proof of IP control

Access

1. Open the VLAN detail page
2. Click the "IP History" tab
3. Filter by period, asset, or IP

Permission

IP history access requires the ipam.history permission.

Global VLANs span multiple sites.

Use case

VLANs routed between sites:

• Stretched VLANs (VXLAN, EVPN)
• Shared management VLANs
• Multi-site disaster recovery

Configuration

1. When creating the VLAN, check "Global VLAN"
2. Don't assign a specific site
3. The VLAN is visible from all sites

Specifics

• Addresses can be assigned to assets from different sites
• Conflict detection works across all sites
• The dashboard aggregates global statistics

Good practices

• Use global VLANs sparingly
• Document the architecture justifying the choice
• Monitor latency for stretched VLANs