Overall Specification

Project Objectives

//Explain the detailed purpose of implementation project from the perspective of customer.

For example

The general objective is to replace 2 Pala Alto firewalls, which currently are deployed in the Internet egress of enterprise network for staff access Internet and communication with branches. The working modules can be analyzed as below.

• Make sure the replacement process is smoothly, and cannot bear more than 2 hours' time window; If fails in expected time period, network should be recovery as soon as possible.

• Except current the configuration in Pala Alto should be translated and configured to Sangfor Network Secure, there will add one more IPSec VPN site with other office site;

• Downlink and Uplink devices, will not change a lot of configuration for this implementation process.

• Perform other necessary configuration to optimize it.

 

Team Member Contact

No	Organization	Engineer Name	Telephone N
1	Customer	XXX	XXX
2	Sangfor	XXX(On-site)	XXX
3	Sangfor	XXX(Remote Standby)	XXX
4	Third-party Vendor	XXX(On-site)	XXX

 

Duty and Preparation

Sangfor Preparation

Device and Accessories

Device, power cable, Console line, RJ-45 cable, optical module, and screwdriver...etc

Upgrade Packet

The expected software version and service packets should be prepared in advance.

License Assistance

Sangfor engineer ought to assist customer to download the official license from Sangfor Platform-X to activate device.https://x.sangfor.com/#/index

Overall Check

• License Status: Check the expired data and authorization module are as expected.

• System Logs: Check the system logs and make sure there is no error or warning logs.

• System time: Modify the system time.

• Workload: Check and confirm CPU, memory and disk workload are normal.

• Light: After device is power on, make sure the lights in front-panel are all normal.

Implementation Plan Confirmation

The project implementation plan has to be confirmed with customer before Sangfor engineer began to implement.

Schedule Specialist for Standby

If the implementation project is complex, Sangfor engineer can schedule a TAC case in advance for remote assistance in case there occurs some unexpected issues.

Customer Preparation

License Preparation

Customer needs to register an account and apply for license in Sangfor Platform-X. During the process, Sangfor engineer can provide necessary assistance.https://x.sangfor.com/#/index

Permission to Computer Room

Customer oughts to prepare the permission for implementation device in the computer room, which should contain Sangfor side engineers, and possibly other third-party vendors' engineer if necessary.

Switch Configuration

Customer may prepare the switch configuration for change into a txt file, as well as the rollback configuration.

Integrated Wiring

Customer needs to prepare the integrated wiring well before the implementation begins.

Project Timetable

//Explain the detailed time planning with each implementation phase, by the way you are able to set timetable in

For example

No	Phase	Timetable	Key Work	Output	Person in Charge
1	Implementation Preparation	2023/10/10---2023/10/13	1. Figure out detailed network topology and physical links. 2. Finish the basic network plan, including IP addresses, routes, and deployment. 3. Sort out all internal network segments. 4. Collect WAN links information, including static public address, or ADSL account and password. 5. Sort out cabinet planning and interface links table. 6. Confirm the main product functions to be configured. 7. Confirm the devices list and software packet. 8. Complete Overall Implementation.	Research output: lCabinet planning lIP address planning lInterface links table lExpected topology after implementation lWAN links information; lInternal network segments or range lOverall Implementation Plan-v0.1	Sangfor engineer leads, and customer engineer cooperate
		2023/10/14---2023/10/15	1. Plan review with customer (perhaps including third-party vendor). 2. Agreement with all relevant roles in customer side.	lOfficial Implementation Planv1.0	Both Sangfor and customer sides all roles.
		2023/10/16--- 2023/10/16	1. Apply offline license and activate it; 2. Upgraded to expected implementation version. 3. Patch necessary service packets.		Sangfor engineer
		2023/10/17--- 2023/10/18	Finish offline configuration		Sangfor engineer leads, and customer engineer cooperate
		2023/10/17--- 2023/10/17	Prepare change as well as rollback configuration of switches or routers into .txt file. Finish the procedure for Sangfor as well as third-party vendor to computer room.	lChange configuration txt; lRollback configuration txt;	Customer engineer
2	Implementation	2023/10/20--- 2023/10/20	1. Reconfirm and record original interface links; 2. Install devices to expected cabinet position; 3. Connect cable or optical link as planned		Sangfor engineer
3	Verification	2023/10/20--- 2023/10/20	1. Connectivity section 2. Business section 3. Security policy section 4. Health check 5. Put on label to new links	lVerification record sheet. lAbnormality record.	Customer engineer leads, Sangfor engineer cooperates.
4	Trial Running	2023/10/21--- 2023/11/20	1. Record the abnormality and solve in time. 2. Weekly Check	Trial running report	Sangfor engineer

 

Implementation Design

 

Topology

Current Topology

//Before you start implementation, you need to confirm with customer about topology to figure out some details, including change position, downlink/uplink devices, port links, and address table.

For example

Topology After Implementation

For example

This project focuses on replacing original Broder Router into 2 Sangfor NSF. The expected topology after implementation is as follows.

Traffic Specification

Current Traffic

For Example

This diagram is simple, since the traffic is clear.

1. Terminals ---> Internet

2. Internet ---> Data Center Server

Traffic After Implementation

For Example

Essentially, the traffic does not change in this topology.

1. Terminals ---> Internet

2. Internet ---> Data Center Server

• Restore the network cable connections related to changes involved in this implementation to the state before the change.

• Flush the prepared rollback configuration back to switches or routers connecting with Network Secure, either downlink or uplink devices.

• Make sure all network comes to normal after rollback actions have been executed.

• Check the device network connection information and confirm whether there are any wrong links.

• Reorganize the customer's existing network environment and troubleshoot the root cause.