CR-2538 - RFC 1918 Routing Update on the EGRs
Implementation Plan
CHANGE REQUEST TYPE:
NETWORK: X
REMEDY:
INFRASTRUCTURE:
SUBMITTER CONTACT INFORMATION:
Request Date: March 30, 2011
Requested By: LCM Engineering
Organization: AT&T LCM Team
Contact Information during AT&T GCSC for General Monitoring Information 800 222 8926 pin 78283
Implementation:
Jenny Notestein, AT&T PM, for Change Information 201-360-9208
Escalation Contact Jenny Notestein, AT&T PM 201-360-9208
Information:
CHANGE REQUEST INFORMATION:
General: X
Critical:
Emergency:
SUPPORTING CHANGE DOCUMENTATION:
Request for Change Description: This change request is being submitted for approval to perform the
following configuration changes:
- Apply null routes for RFC 1918 IP address space for each VRF on
the NetTN Network on the Nashville and Knoxville EGRs.
Risk category assigned: 14 - Critical
Benefit/Reason for Change: This change will prevent IP packets from looping between the EGRs and the firewalls for RFC
1918 IP address space.
Requested Implementation Date / Time: Sunday, April 10, 2011 12:00 AM Central to 6:00 AM Central
Justification for work outside maintenance window: An extended window is required to complete this work.
Corresponding Change Ticket or RFS ID assigned: Business Direct ticket 136579097
TECHNICAL INFORMATION:
Work products affected: N/A
Network Components affected: Please see the Affected Sites & Devices Tab
Additional work/rework required: None. Standalone change.
SUPPORTING DOCUMENTATION:
Back-out/recovery Plan: Y - See Backout Plan
Test Plan completed (y/n): Y - See Implementation & Test Plan
Monitoring Plan: Y - AT&T Engineers will monitor the routers as changes occur. GCSC will continue to monitor network
following standard GCSC processes and procedures.
END-SITE(s) IMPACT:
No end site impact is anticipated during this work.
Mark "X" for Affected Groups in yellow and corresponding comments in white section:
STATE: X
PROVISIONING:
ENGINEERING: X
MSS:
REMEDY:
MRS GCSC: X
OTHER: X Freeze any VRF builds 3 days prior to CR execution
CHANGE PLANNING:
Engineering Peer Review Required? (y/n) Y
Engineering Peer Review Date Tuesday, January 25, 2011
Completed by Change Manager
APPROVED:
9e19bf54-39f3-4e31-9170-aca8fff6b30a.xlsx
CHANGE FORM
NETWORK CHANGE RISK EVALUATION FORM
** One form must be filled out for each Request for Change submitted **
RISK EVALUATION MATRIX CR-2538 - RFC 1918 Routing Update on the EGRs
RISK EVALUATION TOTAL:
Weighted *Change Requester *Post Implementation
Change Attributes Impact Assessment Assessment
Impact of the change to the Network:
Major impact ( > 3 hours ) 3
Significant impact ( between 1 and 3 hours) 2 2
Minimal impact 1
No impact 0
Exposure:
Back out possible, though not easily executed 3
Back out easily executed (1 hour or more) 2 2
Back out easily executed (less than 1 hour) 1
No back out required 0
Activities required to prepare for implementation:
3 or more affected groups 3 3
2 affected groups 2
Multiple activities - one affected group 1
One activity - one affected group 0
End-Site Impact
All below 4
Core 3 3
NAP/POP/VIP Sites 2
Multiple End-Sites 1
Single End-Site 0
Preparation effort (all affected groups):
More than 2 months 3 3
2 weeks to 2 months 2
2 days to 2 weeks 1
2 days or less 0
Supporting Documentation:
Considerable amount 3
Moderate amount 2
Minimum 1 1
None required 0
Sum Categories Total 14
Risk Category Assigned:
10 - 13 = (Critical), 5 - 9 = (Major),1 - 4 = (Minor), 0 = ( No Impact)
Enter comments below:
9e19bf54-39f3-4e31-9170-aca8fff6b30a.xlsx
RISK EVAL (NETWORK)
CR-2538 - RFC 1918 Routing Update on the EGRs
List all affected sites that could be impacted by the change
Core Devices Affected Remote Sites Affected
(Check Appropriate Boxes Below) (Check Appropriate Boxes Below)
Nashville (Y/N) Knoxville (Y/N) Memphis (Y/N) Chattanooga (Y/N) Johnson City (Y/N) Node Name Description
nshpe1 knxpe1 mempe2 chtpe2 jhnpe1 Please See Note Below
nshpe2 knxpe2 mempe3 chtpe3 jhnoob
nshpe6 knxpe3 memi2br chtgsr1
nshpe4 knxpe4 memgsr1 chtgsr2
nshpe5 knxpe5 memgsr2 chtoob
nshpe6 knxrr memoob1
nshcspe1 knxgsr1
nshrr knxgsr2
nshgsr1 knxegr1 Y
nshgsr2 knxegr2 Y
nshcat1 knxibr1
nshcat2 knxibr2
nshegr1 Y knxmgmt1
nshegr2 Y knxoob
nshibr1
nshibr2
nshmgmt1
nshmgmt2
nshoob
nshoob1
No end site impact is anticipated during this work.