Prerequisites for IDC data center network cutover

Source: Internet
Author: User

As a network administrator or network engineer, you cannot avoid network cutover. Here we will summarize what needs to be prepared before network cutover In the IDC room and how to solve some problems encountered during cutover.

The Network cutover of the IDC room generally has the following situations: access layer: Switch replacement; core layer: Switch replacement, bandwidth expansion, including the replacement of M ports into M ports, or replace the M port with the M port ).

Preparations for cutover and switch replacement at the access layer: Prepare one vswitch. The access layer is generally a layer-2 switch. Before cutover, test whether the switch runs normally, whether the ports are normal, and configure network parameters in advance.

Preparations for cutover and switch replacement at the core layer: Prepare one vswitch to ensure that the switch runs normally. Configure the network parameters in advance to ensure that the Network is normal after the replacement of the device without any problems. Preparation for bandwidth expansion: Prepare the optical module. It is recommended that you prepare a backup module instead of a physical fault in the module during cutover. This is troublesome. How many times have I encountered it. Pigtails. If you do not know how long pigtails are to be prepared, you must call the IDC personnel on duty to determine the length of pigtails. We recommend that you write a script before cutover. We hope to solve the problem within a few minutes.

To put it more specifically, CISCO switches must be configured with Cisco original modules or compatible modules dedicated to Cisco switches. Modules of other vendors are not recognized.

The following are two failures I encountered during cutover:

Fault 1

Network Environment Description: the uplink traffic is expanded from 4G to 10G, and the switch model is Huawei 9303. the uplink traffic is ZTE 8906. The previous 4G network implemented 4-port aggregation, this aggregation vlan port is composed of three layers.

Requirement: Replace 4 M ports with 10 M ports, and the IP address remains unchanged.

Fault: After tens of thousands of M modules are inserted and pigtails are connected, the physical link cannot start.

Troubleshooting: first, we need to disable the backend fiber, the promise, or the failure. Then, we need to disable the self-negotiation between the ports at both ends to enable full duplex. It still cannot start. Check whether there is a problem with pigtails again. Because Pigtails are originally pigtails, they must be okay. They can only be a module problem. Replace the modules on 9303 and the physical links will work properly. Each cutover I have an additional module. This time, it will be useful. Otherwise, I will find the module on this evening.

Fault 2

Network Environment Description: The vswitch is Cisco 3560, and acts on Cisco 3570G, with a bandwidth of 2G.

Requirements: PORTS 26,27 of the vswitch and ports 26,27 of the uplink vswitch are aggregated. The ports are closed through negotiation, and the ports are L3.

Fault description: After the aggregation data is complete, only port 27 is connected. Only the upstream switch port is green on the physical link of port 26, and the switch port light is unavailable.

Troubleshooting: Because the configurations at both ends are the same and the configurations on the port are the same, the configuration should be fine. Save the configuration and restart the two switches. After the restart, the fault remains the same, and then re-delete the aggregation configuration and re-do it. If the fault is the same, switch the two modules of the vswitch. If the fault is the same, switch the pigtails of the 26 ports of the vswitch and the uplink switch. Then, the port of the vswitch is on, if the uplink switch port is not bright, it indicates that there is a problem with pigtails. After the pigtails are changed, the network is normal.

This article is from the "Yi Chai Ren" blog, please be sure to keep this source http://join12.blog.51cto.com/1194785/1197672

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.