6PE和6VPE的区别

C H A P T E R4-1MPLS User Guide, 5.2OL-19035-014IPv6 and 6VPE Support in MPLS VPNThis chapter provides an overview of IPv6 and 6VPE support in MPLS VPN. It contains the following sections:•Overview of IPv6 and 6VPE, page 4-1•Comparison of IOS and IOS XR, page 4-3•ISC and MPLS VPN Updates to Support IPv6 and 6VPE, page 4-7•IPv6 and 6VPE Features Not Supported in ISC 5.2, page 4-11NoteFor information on how MPLS VPN features are implemented and supported in the ISC GUI, see the appropriate sections of this guide, as indicated by the references provided.Overview of IPv6 and 6VPEThe ISC MPLS VPN management application supports the configuration and management of Cisco’s 12000 router running IOS XR for provisioning of IPv6 VPNs and 6VPEs for ISC Layer 3 VPN services. This section provides an overview of IPv6 and 6VPE technologies. For a comparison of IOS and IOS XR, see Comparison of IOS and IOS XR, page 4-3.NoteFor a list of IOS XR versions supported in ISC 5.2, see Release Notes for Cisco IP Solution Center, 5.2.Internet Protocol Version 6 (IPv6)IPv6 is an IP protocol designed to replace IPv4, the Internet protocol that is predominantly deployed and extensively used throughout the world. IPv6 quadruples the number of network address bits from 32 bits (in IPv4) to 128 bits, or approximately 3.4 x 1038 addressable nodes. This provides more than enough globally unique IP addresses for every network device on the planet. Cisco Systems has added IPv6 to its Cisco IOS Software. This means that current Cisco Systems-based networks are IPv6-capable,enabling coexistence and parallel operation between IPv4 and IPv6, thereby allowing network managers to configure IPv6 when it is required. While many see IPv6 as a way to build a larger global Internet, it does not eliminate the need to create VPNs for Intranets and other similar applications.A variety of deployment strategies are available for deploying IPv6 over MPLS backbones. Currently, service providers have two approaches to support IPv6 without making any changes to the current IPv4 MPLS backbones:4-2MPLS User Guide, 5.2OL-19035-01Chapter 4 IPv6 and 6VPE Support in MPLS VPNOverview of IPv6 and 6VPE4-3MPLS User Guide, 5.2OL-19035-01Chapter 4 IPv6 and 6VPE Support in MPLS VPNComparison of IOS and IOS XR•Site of Origin (SOO)•Extended community •MP-BGPThe 6VPE router exchanges either IPv4 or IPv6 routing information through any of the supported routing protocols, and switches IPv4 and IPv6 traffic using the respective fast switching CEF or distributed CEF path over the native IPv4 and IPv6 VRF interfaces. The 6VPE router exchanges reachability information with the other 6VPE routers in the MPLS domain using Multiprotocol BGP, and shares a common IPv4 routing protocol (such as OSPF or IS-IS) with the other P and PE devices in the domain. Separate routing tables are maintained for the IPv4 and IPv6 stacks. A hierarchy of MPLS labels is imposed on an incoming customer IPv6 packet at the edge LSR:•Outer label (IGP Label) for iBGP next-hop, distributed by LDP.•Inner label (VPN Label) for the IPv6 prefix, distributed by MP-BGP.Incoming customer IPv6 packets at the 6VPE VRF interface are transparently forwarded inside the service provider’s IPv4 core, based on MPLS labels. This eliminates the need to tunnel IPv6 packets. P routers inside the MPLS core are unaware that they are switching IPv6 labelled packets.Comparison of IOS and IOS XRThis section provides a comparison between IOS and IOS XR, showing various configuration scenarios. It contains the following sections:•General Comparison of IOS and IOS XR Device Configlets, page 4-3•Using OSPF as the PE-CE Routing Protocol, page 4-4•Using EIGRP as the PE-CE Routing Protocol, page 4-5•Using Static as the PE-CE Routing Protocol, page 4-5•Multicast Routing on IOS XR Devices, page 4-6•Multicast Support for IPv6, page 4-7Note For a list of IOS XR versions supported in ISC 5.2, see Release Notes for Cisco IP Solution Center, 5.2.General Comparison of IOS and IOS XR Device ConfigletsThis section provides examples of VRF-related and interface-related configlets for IOS an IOS XR.VRF-Related ConfigletsIOSIn IOS, RD and RT configlets have to be specified in IP VRF configuration mode:ip vrf vrfname rd ASN:uniquenoroute-target export ASN:uniqueno route-target import ASN:uniqueno route-target import ASN:uniqueno !Chapter4 IPv6 and 6VPE Support in MPLS VPN Comparison of IOS and IOS XRIOS XRIn IOS XR, RT values are configured in VRF configuration mode and the RD value has to be specifiedunder BGP configuration mode:vrf vrfnameaddress-family ipv4 unicastimport route-targetASN:uniquenoASN:uniqueno!export route-targetASN:uniqueno!Router BGP mode:vrf vrfnamerd AS:uniquenoaddress-family ipv4 unicastredistribute connectedredistribute staticInterface-Related ConfigletsIOSinterface interfacenameip address ipaddress subnetmaskip vrf forwarding vrfnameIOS XRinterface interfacenameipv4 address ipaddress subnetmaskvrf vrfnameUsing OSPF as the PE-CE Routing ProtocolNote In ISC 5.2, ISC provisions OSPF-based service requests in the same way, irrespective of whether IOS or IOS XR is used.The following examples highlight differences between IOS and IOS XR when using OSPF as the PE-CErouting protocol.IOS•IOS supports the network command:router ospf processid vrf vrfnamelog-adjacency-changesredistribute bgp AS subnetsnetwork networkipadress wildcardmask area areanumber•IOS supports only one VRF per OSPF process ID.MPLS User Guide, 5.2OL-19035-01Chapter4 IPv6 and 6VPE Support in MPLS VPNComparison of IOS and IOS XRIOS XR•In IOS XR, there is no network command support under the ospf process id command.In place of the network command, it uses interface interfacename.router ospf processidvrf vrfnameredistribute bgp ASarea areanointerface interface interfacename•IOS XR supports multiple VRFs per ospf process id command.router ospf process idvrf vpnnewredistribute bgp ASarea areanointerface interface interfacename!vrf V12:vrfnameredistribute bgp ASarea areanointerface interface interfacename!Using EIGRP as the PE-CE Routing ProtocolThe following examples highlight differences between IOS and IOS XR when using EIGRP as thePE-CE routing protocol.IOSIOS supports multiple EIGRP process IDs per device.IOS XRIOS XR supports a single EIGRP process ID per device.Using Static as the PE-CE Routing ProtocolThe following examples highlight differences between IOS and IOS XR when using Static at the PE-CErouting protocol.IOSConfiglets for creating a static route in IOS.•When using nexthopip for the static route:ip route vrf acme destination network subnetmask nexthopip•When using outgoing interface for the static routeip route vrf acme destination network subnetmask outgoing interfaceMPLS User Guide, 5.2 OL-19035-01Chapter4 IPv6 and 6VPE Support in MPLS VPN Comparison of IOS and IOS XRIOS XRConfiglets for creating a static route in IOS XR:•Using outgoing interface for the static route:router static!vrf vrfnameaddress-family ipv4 unicastdestinationnetwork/prefixlength outgoinginterface nexthopip!•Using nexthopip for the static route:router static!vrf vrfnameaddress-family ipv4 unicastdestinationnetwork/prefixlength nexthopip!Multicast Routing on IOS XR DevicesMulticast VRF deployments for IOS XR devices are supported for IPv4, IPv6, IPv4+IPv6 services.Currently, multicast on IOS XR is supported only for IOS XR versions 3.5.2, 3.6, and 3.7.0.This section describes how ISC supports multicast routing on IOS XR devices. There are no changes inthe GUI (Create VPN window) to support this feature. To enable support, the IOS multicast commandsare mapped to equivalent IOS XR commands. Because there are no XML configurations to supportmulticast routing on IOS XR devices, ISC supports the XR CLIs to enable multicast routing on IOS XRdevices.The following sections shows an example of the relevant IOS commands and the corresponding IOS XRcommands to enable multicast routing.IOS CommandsThe following is a sample IOS configuration:ip vrf V27:MulticastCERC3rd 100:124route-target import 100:406route-target import 100:407route-target export 100:406mdt default 226.2.3.4mdt data 226.5.6.7 0.0.0.15 2000mdt mtu 2000ip multicast-routing vrf V27:MulticastCERC3ip pim vrf V28:VPN13 ssm defaultip pim vrf V27:MulticastCERC3 rp-address 10.20.1.1ip pim vrf V27:MulticastCERC3 rp-address 10.20.3.1 test2ip pim vrf V27:MulticastCERC3 rp-address 10.20.2.1 test1 overrideIOS XR CommandsThe following IOS commands are not supported on the IOS XR devices, because the correspondingcommands do not exist in IOS XR.•ip multicast vrf <vrfName> route-limit. The reason for not supporting this is that the command to set the route limit per VRF is not available on IOS XR devices.•ip pim vrf <vrfName> sparse-dense-mode. Sparse-dense mode is not supported by IOS XR. Only sparse mode and bidirectional modes are supported.MPLS User Guide, 5.2OL-19035-01Chapter4 IPv6 and 6VPE Support in MPLS VPNISC and MPLS VPN Updates to Support IPv6 and 6VPE The following IOS commands are enabled on the IOS XR device by default when the multicast routingis enabled. They cannot be disabled.•ip pim vrf <vrfName> sparse-mode•ip pim vrf <vrfName> ssm default•ip pim vrf <vrfName> autorp listenerMulticast Support for IPv6ISC allows the following on IOS XR PE devices running release 3.7.0 or later:• A multicast VPN to be deployed on an IPv6 PE-CE link.•Multicast to be enabled during the creation of the VRF object.When creating a VPN or a VRF object, you can enable multicast for IPv4, IPv6, or both. You can enterIPv6 addresses as static Rendezvous Point (RP) addresses if IPv6 multicast is enabled during the creationof a VPN or VRF object.You can also modify an existing VPN or VRF object to enable multicast for IPv4, IPv6, or both. WhenIPv4 multicast is enabled, all deployed service requests containing IPv4 links of the same VPN or VRFare moved into Requested state.In addition, you can specify within the MPLS service request whether you want to enable multicast forIPv4, IPv6, or both on a given MPLS link.When IPv6 multicast is enabled, all deployed service requests containing IPv6 links of the same VPN orVRF are moved into Requested state. If IPv4 is previously configured and only IPv6 multicast is enabledin a VPN, only the service requests with IPv6 links are moved into Requested state.You can modify an existing VPN or VRF object and add IPv6 static RP addresses when IPv6 multicastis enabled. Any service requests already in Deployed state are then moved to the Requested state.You can create a service policy or an MPLS VPN link in the service request with IPv6 Numbered orIPv4+IPv6 Numbered as the IP addressing scheme and a multicast VPN or a VRF with multicastenabled.ISC and MPLS VPN Updates to Support IPv6 and 6VPEThis section summarizes how ISC and the MPLS VPN management application support IPv6 and 6VPEin ISC 5.2. It contains the following subsections:•Inventory and Device Management, page4-8•MPLS VPN Service Provisioning, page4-9•MPLS Reports, page4-11See Chapter2, “Setting Up the ISC Services” for information setting up ISC services mentioned in thissection. For additional information on setting up basic ISC services, see the Cisco IP Solution CenterInfrastructure Reference, 5.2.MPLS User Guide, 5.2 OL-19035-01Chapter4 IPv6 and 6VPE Support in MPLS VPN ISC and MPLS VPN Updates to Support IPv6 and 6VPEInventory and Device ManagementTo activate MPLS VPN services, you must configure ISC so it “knows” about the preconfigurationinformation, such as devices, providers, customers, and so on, that ISC is going to manage. Changes inthis release of ISC to support inventory and device management for IPv6 and 6VPE include:Discovery features for supporting IPv6/6VPE:•ISC Inventory Manager supports bulk-import of 6VPE devices into the ISC repository.Collect Config task features for supporting IPv6/6VPE:•The Collect Config task collects device information and interface information. It has been updated to collect IPv6 addresses of interfaces. When interfaces contain both IPv4 and IPv6 addresses, bothwill be collected and stored in the ISC repository.•The Collect Config task retrieves the OS type and the version information. If the device is a Cisco 12000 series router or a Cisco CRS-1 Carrier Routing System and is running IOS XR, the devicewill be marked as 6VPE supported.Device configuration features for supporting IPv6/6VPE:•6VPE devices with IPv6 addressing can be created and managed in the ISC GUI.– A “6VPE” check box has been added to the Create PE Device window to designate an N-PEdevice as a 6VPE.– A new column has been added to the Interface Attributes window to show IPv6 addresses. It is not possible to bulk change the IPv6 addresses by selecting multiple interfaces. The IPv6Address column is noneditable.–The Edit Device Interface window has also been updated to show IPv6 addresses on interfaces.In case of dual-stack interfaces containing both IPv4 and IPv6 addresses, both addresses aredisplayed.–ISC supports multiple IPv6 addresses on the PE interface for IOS XR PE devices.–The Create CPE Device window has been updated to display IPv6 addresses on interfaces. Incase of dual-stack interfaces containing both IPv4 and IPv6 addresses, both addresses aredisplayed.–You cannot create an IPv6 interface using the existing Create Interface feature. This screencurrently lets you create interfaces in the repository only, with the device configurationremaining unchanged. This feature does not support IPv6 addresses. The IPv6 interface creationin the device is supported through the MPLS VPN service deployment.General features for supporting IPv6/6VPE:•Windows within the Inventory and Connection Manager GUI have been updated in several areas to support IPv6 addressing for a 6VPE device.•The ISC GUI provides messages to the user that IPv6 addressing scheme is only applicable to IOS XR devices.VPN Creation and ConfigurationThere are no changes in the ISC VPN workflow for IPv6 and 6VPE. However, a new feature called VRFobject management was added in ISC 5.0.1. See the next section, VRF Object Support, page4-9, formore information.MPLS User Guide, 5.2OL-19035-01Chapter4 IPv6 and 6VPE Support in MPLS VPNISC and MPLS VPN Updates to Support IPv6 and 6VPEVRF Object SupportStarting in ISC 5.0.1, ISC allows you to specify VPN and VRF information in an independent VRFobject, which is subsequently deployed to a PE device and then associated with an MPLS VPN link viaan MPLS VPN service request. For details on using this feature, see Chapter3, “Independent VRFManagement.”Resource PoolsISC uses resource pools to automatically assign critical parameters like VLAN, VCID, and IP Addressesduring the service provisioning. IPv6 address pools are not supported in this release.MPLS VPN Service ProvisioningISC MPLS VPN management application supports the provisioning of IPv6 Layer 3 VPNs on an IPv6Provider Edge router (6VPE), starting with the IOS XR 3.5 release. ISC 5.2 provides the ability toconfigure the following on the 6VPE:•IPv6 addressing on 6VPE (optionally, IPv4 or both IPv6+IPv4 addresses)•Assign a static route to the 6VPE facing interface on a CE device.•Enable MP-BGP peering with target 6VPE.•Redistribute connected (if needed).The following sections describe changes to MPLS VPN service policy definition, service requestcreation, and service request auditing to support IPv6 and 6VPE in ISC 5.2.MPLS VPN Service PoliciesChanges in this release of ISC to support MPLS VPN service policy creation for IPv6 and 6VPE include:•The ISC MPLS VPN service policy design has been extended to support the configuration of IPv6 on a 6VPE router for the following policy types:–Regular: PE-CE (with unmanaged CE)•Both Unmanaged CE and No CE scenarios are supported for IPv6.•The service policies support the following addressing schemes:–IPv4–IPv6–Both IPv4 and IPv6•The IP Numbering Scheme field in the MPLS Policy Editor - IP Address Scheme window has been updated with option to specify each of the supported address schemes.•The IPv4 routing and IPv6 routing are independent. The ISC GUI allows you to input the same or different routing protocols for IPv4 and IPv6.MPLS User Guide, 5.2 OL-19035-01Chapter4 IPv6 and 6VPE Support in MPLS VPN ISC and MPLS VPN Updates to Support IPv6 and 6VPE•When setting up the policy, the following PE-CE routing protocols are supported for the IPv6 addressing scheme:–Static–BGP–EIGRP–None•IPv6 validity checks. The following checks will be performed on addresses entered in the IPv6 address fields:–The address can be specified eight consecutive blocks of 16-bit each separated by the “:” (colon) character. Each 16-bit block can be specified as 4-digit hexadecimal number. Example:21DA:00D3:0000:2F3B:02AA:00FF:FE28:9C5A.–The leading zeros can be skipped in each hexadecimal block. Here is the modified valid address from the previous example: 21DA:D3:0:2F3B:2AA:FF:FE28:9C5A.–Where there are consecutive “0:” blocks, they can be replaced with “::”. Example:21DA:D3:0:0:0:FF:FE28:9C5A can be represented as 21DA:D3::FF:FE28:9C5A.–The string “::” cannot appear more than once in the address. Example:21DA:0000:0000:2F3B:0000:0000:0000:9C5A can be represented as21DA::2F3B:0000:0000:0000:9C5A or 21DA:0000:0000:2F3B::9C5A, but not as21DA::2F3B::9C5A.See Chapter5, “MPLS VPN Service Policies” for information on defining MPLS VPN service policies. MPLS VPN Service RequestsChanges for MPLS VPN policy creation to support IPv6 and 6VPE are carried over to the correspondingwindows in the service request creation workflow. If the options were set as editable during policycreation, they can be modified when the service request is created.•The IP Numbering Scheme field in the MPLS Link Attribute Editor - IP Address Scheme window has been updated with options to specify each of the supported address schemes.•The IPv4 and IPv6 Unnumbered schemes are not supported on IOS XR devices.When you select an IOS XR device and go the to IP Addressing Scheme window, only the following options aredisplayed:–IPv4 Numbered–IPV6 Numbered–IPV4+IPV6 Numbered•As part of the regular PE-CE MPLS service, the required VRF will be configured on the PE device.The CE-facing interface will be configured with the IPv6 address and the interface will be assignedto the VRF. The IPv6 address-family configuration in BGP along with the PE-CE routinginformation will be configured. The PE-CE Routing protocols supported are Static, BGP andEIGRP.•If the PE Interface is dual-stacked and contains both IPv4 and IPv6 addresses, you can enter the routing information for both IPv4 and IPv6 independently. The GUI provides steps to enter the IPv6routing information in addition to the existing IPv4 routing information.•This release supports the scenario of the CE device not present in the service request. This release also supports the Unmanaged CE devices being present in the service request. In the later case, theconfiglets for service provisioning will be generated but not rolled onto the CE device.MPLS User Guide, 5.2OL-19035-01Chapter4 IPv6 and 6VPE Support in MPLS VPNIPv6 and 6VPE Features Not Supported in ISC 5.2•It is possible to modify a 6VPE service request.•If the PE device is an IOS XR device, all of the configuration operations will be performed using the IOS XR interface.•All configlets generated for 6VPE devices are IOS XR configlets and are in XML format. Different versions of IOS XR will generate different XML configlets. However, the configurations will bealmost identical, except for changes in the XML schema.See Chapter6, “MPLS VPN Service Requests” and subsequent chapters in this guide for information oncreating MPLS VPN service requests.MPLS Service Request AuditsL3 VPN functional audit has been enhanced to support IPv6 VPNs (IPv6 addresses and 6VPE devices).The current capabilities include checking the routes to remote CEs in the VRF route tables on the PEdevices. See Auditing Service Requests, page6-34 for information on auditing service requests.MPLS ReportsThe MPLS VPN reports support has been extended to support IPv6 addresses and 6VPE devices. SeeChapter14, “Generating MPLS Reports” for information on generating MPLS VPN reports for IPv6 and6VPE.IPv6 and 6VPE Features Not Supported in ISC 5.2The following features are not currently supported for IPv6 and/or 6VPEs:•Discovery of existing IPv6 VPN services on the device.•Support of IPv6 addressing for IOS-based routers.•IPv6 addressing as part of a CPE device definition and configuration.•IPv6 address pools.•IPv6 multicast address pools.•The IPv4 and IPv6 Unnumbered address schemes are not supported for IOS XR.•Grey management VPN support for 6VPE and IOS XR.•Staging service request deployment to support eBGP route maps on IOS XR devices.•Support for BGP maximum prefix configuration on IOS XR devices.•Managed CE services.•Multi-VRF CE (MVRFCE) support.•One-time setup operations on the 6VPE device like enabling IPv6 routing, BGP VPNv6configuration.•RIP and OSPF as the PE-CE routing protocol.•Tunnel interface. An IPv6 address cannot be specified as the Tunnel Source Address value.•Template Manager support for IPv6 features.MPLS User Guide, 5.2 OL-19035-01Chapter4 IPv6 and 6VPE Support in MPLS VPN IPv6 and 6VPE Features Not Supported in ISC 5.2MPLS User Guide, 5.2OL-19035-01。

数据通信网设备（路由器、交换机及台式电脑）
1 标准技术参数表
投标人应认真逐项填写技术参数表（见表1）中投标人保证值，不能空格，也不能以“响应”两字代替，不允许改动招标人要求值。

如有差异，请填写表10：投标人技术偏差表。

1.1 设备功能范围及性能指标
表1 技术参数表
（1）生产MIS三层交换机技术参数表
注1：附表及正文中带“★”的项目为重要指标，应答人必须满足。

（2）汇聚层—PE路由器2（千兆）
注1：附表及正文中带“★”的项目为重要指标，应答人必须满足。

（3）汇聚层—MCE路由器2（千兆）
注1：附表及正文中带“★”的项目为重要指标，应答人必须满足。

注1：附表及正文中带“★”的项目为重要指标，应答人必须满足。

2 项目需求部分
2.1 货物需求及供货范围
入现有网络及网管）。

注2：设备以电源、配线设备为界，设备缆线由设备厂家提供并负责连接。

注3：机柜前后门的规格型号按照工程项目单位的实际需求供货。

投标人应认真逐项填写投标人响应部分，不能空格，也不能以“响应”两字代替，不允许改动招标人要求值。

如有差异，请填写技术差异表。

注：打“*”的项目，如不满足要求，将被视为实质性不符合招标文件要求。

2.2 必备的备品备件、专用工具和仪器仪表。

随着IPv4地址日益耗尽，中兴通讯积极谋划IPv6，根据IPv4网络特征提出下一代互联网过渡方案。

骨干网从边缘到核心逐步升级，并根据网络特征（IP骨干网和MPLS骨干网）执行不同的升级策略。

IP骨干网根据IPv6互联需求进行升级，将IPv6流量所经路径的设备升级双栈，或者部署IPv6 over IPv4 隧道，随着IPv6规模扩大最终升级全网设备支持双栈；MPLS骨干网根据IPv6互联需求，升级业务接入层设备PE支持双栈，部署6PE和6vPE以提供IPv6公众互联和IPv6 VPN业务，最终完成全网PE升级，而P设备不做升级，保持IPv4单栈。

城域网从核心到边缘逐步升级，核心出口路由器升级双栈以支持IPv6转发。

BRAS升级双栈，部署PPPoEv6和IPoEv6以实现纯IPv6用户接入；部署PPPv6 over L2TP以实现远端纯IPv6用户接入；部署PPPoE/ IPoE+DS-Lite，为用户配置私有IPv4地址和公有IPv6地址，节省IPv4公有地址，并实现双栈用户接入；部署NAT64/DNS64，实现纯IPv6用户访问IPv4业务。

SR升级双栈，部署6vPE为大客户提供IPv6 VPN业务。

宽带接入网交换机/xPON/DSLAM二层透传IPv6流量，后续根据业务需求新建或者升级现有设备，部署IPv6 组播/安全等功能。

中兴通讯IPv6升级方案，不影响现网业务，并充分利用现有设备，实现了网络平滑演进。

∙清晰的网络架构IP/MPLS骨干网采用扁平化分层网络结构，当前分为核心层和汇聚层。

骨干核心P路由器采用全网状连接，汇聚PE路由器采用双节点双链路结构，避免单点故障从而网络健壮性。

根据带宽需求，可采用10G/40G/100G链路互联。

∙简明的路由规划IP/MPLS骨干网IGP采用IS-IS路由协议，基于管理方便性、路由收敛速度、后续扩展以及对TE Tunnel特性支持等方面的考虑，所有节点不分层，所有路由器置于Level 2中。

Science and Technology & Innovation｜科技与创新2024年第08期DOI：10.15913/ki.kjycx.2024.08.026电力通信网IPv6过渡技术研究李玉芬，张永安（国网张掖供电公司数字化通信部，甘肃张掖734000）摘要：IPv6作为下一代网络技术，可以有效解决IPv4网络中地址不足、协议缺陷、不安全等一系列问题。

目前，各个国家都在加快IPv6网络的部署建设，中国也通过CNGI工程积极参与IPv6的研究建设。

但是，直接跳过IPv4建设IPv6网络，并不是一件现实的事，因此，在IPv4向IPv6网络过渡的过程中，提出了双栈技术、隧道技术、NAT-PT（Network Address Translation - Protocol Translation，附带协议转换的网络地址端口转换）技术和6PE（IPv6 Provider Edge）技术与6VPE（IPv6 VPN Provider Edge）技术等多种过渡技术。

在这些过渡技术的基础上，提出了一种电力通信网由IPv4向IPv6网络过渡的实施方案和技术策略，并对过渡的前期、中期和后期网络特点及采用的技术和过渡策略进行了分析。

关键词：IPV4；IPv6；过渡技术；智能电网中图分类号：TP393.4 文献标志码：A 文章编号：2095-6835（2024）08-0095-03随着智能电网的发展部署，尤其是电力物联网的建设，各类传感器、终端设备等大量设备设施的数据都需要电力通信网进行传输，对电力通信网的承载力、可靠性都有了更高的需求。

电网中智能调度、在线输变电监测、电能质量监测、智能电表抄表、推广安装、各类新应用系统数据及信息的收集传输等新老应用系统都需要依靠电力通信网传输。

因此，随着智能电网的建设，电力通信网对IP地址的需求呈几何级增长。

传统的网络地址转换技术虽然能够解决部分IP地址不足的问题，但是不能解决根本问题。

深圳某电信运营商城域网IPv6部署方案作者：深圳xx分公司曹剑锋2010年9月20日目录一、前言 (3)二、IPv6技术简介 (4)(一) IPv6优势 (4)(二) 相关协议 (4)(三) 过渡技术 (6)三、深圳城域网现状分析 (9)(一) 网络情况 (9)(二) 业务情况 (11)(三) 设备对IPv6的支持情况 (11)四、IPv6业务实现方案 (13)(一) MPLS VPN实现 (13)(二) 宽带业务实现 (14)(三) WLAN业务的实现 (16)(四) 其他业务实现说明 (18)五、IPv6网络互联方案 (19)(一) IPv6网络互联 (19)(二) IPv6和IPv4网络互通 (21)六、IPv6网络实施方案 (25)(一) 试商用阶段 (25)(二) 规模商用阶段 (26)(三) 全面商用阶段 (27)七、总结 (28)一、前言今天互联网取得了巨大的成功，完全出乎网络创造者和IPv4设计者的预料。

29年前，当IPv4 RFC诞生时，尚没有真正意义上的互联网，网络如私有网络，主要供教育和科研使用。

在这种情况下，32位的地址空间看起来是绰绰有余的。

但随着互联网应用的日益广泛，网络规模的快速增长，IPv4地址空间迅速耗尽。

尽管NAT（Network Address Translation，网络地址转换）技术一定程度上减缓了IPv4地址空间耗尽的速度，但未从根本上解决问题。

因此为了互联网的可持续发展，人们决定开发新的技术取代IPv4，这就是IPv6。

1992年IETF（Internet Engineering Task Force，因特网工程任务组）成立了IPNG工作组，并于1994年推出IPv6推荐版本。

但至今IPv6并没有得到大规模的应用，一方面由于IPv6和相关技术标准完善需要时间，另外一方面，由于NAT技术的出现，IPv4由死刑改判了死缓，尚存残延的时间。

但现在，IPv4地址空间的耗尽已经迫在眉睫。

IPv6 6PE和6VPE的实现和配置Cao Jianfeng China Telecom Shenzhen Branch目录一、应用场景 (2)二、6PE/6VPE的实现 (2)三、6PE/6VPE详细配置 (3)1.拓朴图 (3)2.IP/IPv6地址分配 (3)3.6PE配置 (3)4.6VPE配置 (10)一、应用场景在IPv4向IPv6过渡初期，IPv6网络规模较小，且分布零散。

这些零散分布的IPv6网络称为IPv6孤岛。

如何在对现有骨干网络（IPv4网络）做最少的改动情况下，将这些IPv6孤岛连接起来，实现互联互通？目前相关的技术较多，如GRE、6to4、ISATAP、6PE、6VPE等，都可以实现IPv6网络跨越IPv4网络的连接。

对于已经部署MPLS的电信运营商来说，使用基于MPLS技术的6PE和6VPE，可以更方便、低成本地实现IPv6孤岛的连通，避免对现有骨干网络做大量的升级、改造工作。

6PE/6VPE在现有的MPLS网络中实现，只需在边缘路由器开启IPv6功能，而对骨干路由器无需做任何改动。

二、6PE/6VPE的实现6PE在MPLS网络使用两层标签。

外层标签由为IGP标签，由LDP发布，内层标签为IPv6标签，由MP-IBGP发布。

因此实现6PE,需要在PE路由器间配置MP-IBGP发布IPv6路由，发布路由的同时为IPv6前缀分配标签。

6PE需要两层标签的原因为：倒数第二跳弹出机制使得IGP标签在倒数第二条的P 路由器上弹出，如果只有一层标签，IPv6地址将会暴露出来，而P路由器没有开启IPv6功能，不能识别IPv6地址，会将数据报文丢弃，因此需要两层标签。

6VPE是IPv6的MPLS VPN，和IPv4的MPLS VPN相似，不同之处为6VPE 中的MP-IBGP发布的网络可达信息为VPNv6地址路由。

VPNv4地址由RD和IPv6地址组合而成。

6PE和6VPE都是使用二层标签承载，不同之处为6PE发布的网络可达信息为IPv6路由，而6VPE为VPNv6地址路由。

运营商IPv4至IPv6过渡技术方案探讨王明明【摘要】本文阐明了IPv4/v6过渡的必要性，对现有的基本过渡技术进行综述和比较。

根据运营商实际网络环境分析已有的双栈技术和NAT444技术相结合的过渡技术，并在此基础上根据不同的场景分析不同的过渡技术，最终根据运营商的案例分析了部署CGN的过渡技术方案。

%This paper summarizes the existing basic transition techniques, and clarifi es the need of the transition from IPv4 to IPv6. Then analyses the transition technology of the Dual IP Stack and NAT444 based on the operator’s actual network environment. According to the operators case and compare with other different transition technologies, the CGN deployment transition technology is discussed.【期刊名称】《电信工程技术与标准化》【年(卷),期】2016(029)011【总页数】6页(P65-70)【关键词】IPV4/IPV6;双栈技术;NAT444;CGN;地址空间【作者】王明明【作者单位】上海邮电设计咨询研究院有限公司，上海 200009【正文语种】中文【中图分类】TN914全球地址分配机构（IANA）于2011年2月3日正式宣布，将其最后的468万个IPv4地址平均分配到全球5个地区的互联网络信息中心，亚太互联网信息中心（APNIC）于2011年4月15日宣布，正常可分配的IPv4地址告罄[1～2]。

在当前IPv4地址逐渐枯竭的关键时期，IPv4向IPv6的全面过渡更加紧迫。