Chapter 3 - section 3.1 - Explain the purpose of organizational processes and procedures.

0.0(0)
studied byStudied by 0 people
0.0(0)
full-widthCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/28

flashcard set

Earn XP

Description and Tags

section 3.1

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

29 Terms

1
New cards
Objective – Documentation, Lifecycle, Change, and Configuration Management
• Documentation
▸ Physical vs. logical diagrams
▸ Rack diagrams
▸ Cable maps and diagrams
▸ Network diagrams
▸ Layer 1
▸ Layer 2
▸ Layer 3
▸ Asset inventory
▸ Hardware
▸ Software
▸ Licensing
▸ Warranty support
▸ IP address management (IPAM)
▸ Service-level agreement (SLA)
▸ Wireless survey / heat map
• Life-cycle management
▸ End-of-life (EOL)
▸ End-of-support (EOS)
▸ Software management
▸ Patches and bug fixes
▸ Operating system (OS)
▸ Firmware
▸ Decommissioning
• Change management
▸ Request process tracking / service request
• Configuration management
▸ Production configuration
▸ Backup configuration
▸ Baseline / golden configuration
2
New cards
Documentation – Purpose
• Provides visibility into network design
• Supports troubleshooting and audits
• Required for change and lifecycle management
• Exam critical for N10-009
3
New cards
Diagrams – Physical vs. Logical
• Physical diagrams
▸ Show hardware placement and cabling
• Logical diagrams
▸ Show IPs, VLANs, routing, and traffic flow
• Both are required for full documentation
4
New cards
Documentation – Rack Diagrams
• Visual layout of rack-mounted equipment
• Shows device position and size (U)
• Helps with airflow and power planning
• Used during installation and upgrades
5
New cards
Documentation – Cable Maps and Diagrams
• Show cable paths and endpoints
• Identify port numbers and media types
• Reduce troubleshooting time
• Critical for large environments
6
New cards
Network Diagrams – Layer 1
• Physical layer view
• Cables, connectors, interfaces
• No IP or routing info
• Focus on connectivity
7
New cards
Network Diagrams – Layer 2
• Switching and VLAN topology
• MAC addressing and trunks
• Shows broadcast domains
• Important for troubleshooting loops
8
New cards
Network Diagrams – Layer 3
• IP addressing and routing
• Subnets and gateways
• Routing protocols and paths
• Used for traffic flow analysis
9
New cards
Asset Inventory – Overview
• Tracks network resources
• Supports budgeting and audits
• Required for lifecycle planning
10
New cards
Asset Inventory – Hardware
• Routers, switches, APs, firewalls
• Model, serial number, location
• Supports warranty and replacement
11
New cards
Asset Inventory – Software
• OS and application versions
• Patch levels
• Helps with vulnerability management
12
New cards
Asset Inventory – Licensing
• Tracks license type and expiration
• Prevents compliance violations
• Exam-relevant for enterprise networks
13
New cards
Asset Inventory – Warranty Support
• Vendor support contracts
• Replacement timelines
• Critical during outages
14
New cards
IP Address Management (IPAM)
• Centralized IP tracking system
• Prevents IP conflicts
• Tracks subnets and assignments
• Essential for IPv4/IPv6 networks
15
New cards
Service-Level Agreement (SLA)
• Defines expected service performance
• Uptime, latency, response time
• Used with ISPs and vendors
• Exam critical definition
16
New cards
Wireless Survey / Heat Map
• Visual RF coverage representation
• Identifies dead zones and interference
• Used during wireless planning
• Important for performance tuning
17
New cards
Lifecycle Management – Overview
• Manages devices from deployment to removal
• Reduces risk and downtime
• Supports budgeting and upgrades
18
New cards
Lifecycle – End-of-Life (EOL)
• Vendor stops selling product
• No new hardware availability
• Signals upcoming replacement need
19
New cards
Lifecycle – End-of-Support (EOS)
• Vendor stops updates and support
• No security patches
• High security risk
• Exam critical distinction from EOL
20
New cards
Software Management – Patches and Bug Fixes
• Fix security and performance issues
• Must be tested before deployment
• Reduces vulnerabilities
21
New cards
Software Management – Operating System (OS)
• Network device OS (IOS, JunOS, etc.)
• Must match hardware compatibility
• Updated during maintenance windows
22
New cards
Software Management – Firmware
• Low-level hardware control software
• Impacts performance and stability
• Often updated less frequently
23
New cards
Lifecycle – Decommissioning
• Secure removal of devices
• Data wiped or destroyed
• Licenses reclaimed
• Prevents security leaks
24
New cards
Change Management – Purpose
• Controls network changes
• Reduces unintended outages
• Required in enterprise environments
25
New cards
Change Management – Request Process Tracking
• Formal service request submission
• Approval and documentation
• Tracks impact and rollback plans
• Exam relevant process concept
26
New cards
Configuration Management – Overview
• Ensures consistent device settings
• Supports recovery and auditing
• Critical for stability
27
New cards
Configuration – Production Configuration
• Active running configuration
• Currently in use
• Must be documented and approved
28
New cards
Configuration – Backup Configuration
• Saved copy of device settings
• Used for recovery
• Stored securely and regularly updated
29
New cards
Configuration – Baseline / Golden Configuration
• Approved standard configuration
• Used for deployment and comparison
• Ensures consistency and compliance