Overview
The transcript explains common types of network documentation, their purposes, and tools/processes for mapping, asset tracking, IP address management, SLAs, and wireless site surveys.
Network Maps: Physical vs. Logical
- Physical network maps show equipment layout, cabling, and exact device locations and interfaces.
- Example: Internet cable to internet router at 10.1.1.1, then to firewall, then core router at 10.1.1.101.
- Useful for tracing cables in rooms to specific equipment during troubleshooting and installs.
- Logical network maps show high-level connectivity without per-interface detail.
- Example: Central cloud with multiple headquarters connected from different locations to one cloud.
- Logical maps help plan new locations by viewing existing WAN layout and connectivity.
Tools for Creating Maps
- Third-party software can create physical and logical maps.
- Examples mentioned: Visio, OmniGraffle, Gliffy, Draw.io, and others.
Rack Diagrams
- Provide a front-of-rack view as if standing in the data center looking at the rack.
- Useful when data center access is restricted; guide remote hands precisely.
- Documentation can specify row and rack (e.g., row 3, rack W) and unit positions.
- Enables precise instructions, e.g., go to unit 15 and reboot that server.
Cable Maps (Office Wiring)
- Show office layout and exact wire runs under floors or above ceilings.
- Typically posted in IDF/MDF closets to correlate desk drops with patch panels.
- Each drop is numbered to match patch panel ports for quick identification.
- Supports installation verification and troubleshooting by tracing wire paths and drops.
Layer 1/2/3 Combined Diagrams
- Layer 1: Physical layer showing interfaces, cables, and physical connectivity.
- Layer 2: Data link layer overlay including MAC addresses of devices and links.
- Layer 3: Network layer overlay with IP addresses mapped to MAC and physical ports.
- Combined view links physical, MAC, and IP addressing for end-to-end clarity.
Asset Tracking and Asset Database
- Tag/label all assets: laptops, desktops, routers, firewalls, switches, and more.
- Tags support troubleshooting, inventory, depreciation tracking, and warranty checks.
- Tags may include barcodes/RFID and ownership info for third-party identification.
- Centralized asset database links asset tag, device components, and assigned user.
- Database used by support, accounting, finance, and others needing asset data.
- Knowing assigned user allows determining device physical location.
- Track purchase dates and warranty status; monitor software installed for licensing.
Asset Tracking: Structured Details
| Aspect | Purpose | Details |
|---|
| Asset Tags | Identification and reference | Visible labels; may include barcode/RFID; ownership info |
| Troubleshooting | Device-specific issues | Refer to tag (e.g., router #42) in tickets |
| Financial Tracking | Depreciation and warranty | Purchase date, warranty status stored in database |
| Location Mapping | Find device location | Link asset to user; user location implies device location |
| Software Tracking | Licensing compliance | Count installations to determine licenses needed |
| Central Database | Cross-department access | Used by support, accounting, finance, others |
IP Address Management (IPAM)
- IPAM plans, tracks, and configures DHCP and IP addressing across the organization.
- Maps users to IPs at specific dates/times despite dynamic addressing.
- Identifies IP shortages or configuration issues; guides subnet/range changes.
- Manages IPv4 and IPv6 addressing from a central console.
- Typical console shows subnets, usage statistics, change logs, warnings, and errors.
IPAM: Structured Details
| Function | Description | Outcomes |
|---|
| Planning | Design DHCP scopes and IP schemes | Prevent shortages; allocate ranges effectively |
| Tracking | Map users to IPs over time | Support audits and incident investigations |
| Configuration | Centralized DHCP/IP adjustments | Rapid updates to scopes and reservations |
| Monitoring | View stats, logs, warnings/errors | Early detection of address exhaustion |
| Protocol Scope | IPv4 and IPv6 management | Unified handling of dual-stack networks |
Service Level Agreements (SLAs)
- Contractual definition of minimum service levels with third-party providers.
- Example target: 99.99% uptime or no more than 4 hours unscheduled downtime.
- Providers must have processes for rapid restoration, dispatch, or on-site spare gear.
- SLAs apply to WAN and internet services and other outsourced services.
SLA Examples
| Metric | Target | Provider Expectation |
|---|
| Availability | 99.99% uptime | Monitoring, redundancy, rapid incident response |
| Unscheduled Downtime | ≤ 4 hours | Dispatch technicians or deploy on-site spare equipment |
Wireless Site Surveys and Heat Maps
- Document all visible access points and frequencies, including those not under control.
- Configure channels to minimize interference based on observed frequency use.
- Perform frequent surveys in multi-tenant buildings or large multi-organization campuses.
- Heat maps capture signal propagation while walking with a mobile device.
- Use findings to optimize AP placement, channels, and power levels.
Key Terms & Definitions
- Physical Network Map: Diagram of equipment, cabling, and physical connections and locations.
- Logical Network Map: High-level connectivity view without per-interface detail.
- Rack Diagram: Visual layout of devices by rack units for precise physical tasks.
- Cable Map: Office wiring diagram showing numbered drops and cable paths.
- Layer 1/2/3: Physical, data link (MAC), and network (IP) layers in the OSI model.
- Asset Tag: Label identifying a device for tracking, support, and financial purposes.
- IPAM: System for planning, tracking, and configuring IP addresses and DHCP.
- SLA: Contract specifying minimum service levels and uptime/downtime guarantees.
- Site Survey: Assessment of wireless environment to document APs and frequencies.
- Heat Map: Visual representation of wireless signal strength across physical space.
Action Items / Next Steps
- Create or update physical, logical, and combined L1/L2/L3 network diagrams.
- Build rack diagrams with row, rack, and unit details for all data center racks.
- Produce cable maps with numbered drops and patch panel correlations for each site.
- Implement standardized asset tagging and populate a centralized asset database.
- Deploy IPAM to manage IPv4/IPv6, DHCP scopes, and maintain audit logs and alerts.
- Define and negotiate SLAs with providers; include uptime and recovery procedures.
- Conduct regular wireless site surveys; generate heat maps and optimize channels.