atn 905 v200r002c01 configuration guide 03(cli)

ATN 905 Multi-Service Access EquipmentV200R002C01

Configuration Guide (CLI)

Issue 03Date 2013-11-22

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2013. All rights reserved.No part of this document may be reproduced or transmitted in any form or by any means without prior writtenconsent of Huawei Technologies Co., Ltd. Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.All other trademarks and trade names mentioned in this document are the property of their respective holders. NoticeThe purchased products, services and features are stipulated by the contract made between Huawei and thecustomer. All or part of the products, services and features described in this document may not be within thepurchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,and recommendations in this document are provided "AS IS" without warranties, guarantees or representationsof any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but all statements, information, andrecommendations in this document do not constitute a warranty of any kind, express or implied. Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.comEmail: [email protected]

Issue 03 (2013-11-22) Huawei Proprietary and ConfidentialCopyright Huawei Technologies Co., Ltd.

i

About This Document

PurposeThis document provides the basic concepts, configuration procedures, and configurationexamples in different application scenarios of the Lan features supported by the ATN 905 device.The usage precautions are as follows:l A device can store keys in plaintext, reversible algorithm encryption, or irreversible

algorithm encryption mode. The plaintext mode has the low security level, and theirreversible algorithm encryption mode has the highest security level. Use different storagemodes for different scenarios. Exercise caution when using an insecure storage mode. Thesystem automatically selects the irreversible algorithm encryption mode to store local userkeys. Generally, the reversible algorithm encryption mode is used to store protocol keys tomeet interworking requirements.

l If the plaintext mode is used, a password is stored in plaintext in the configuration file. Thisresults in high security risks. The plaintext mode applies only to scenarios with specialrequirements, such as compatibility and interworking requirements.

Related VersionThe following table lists the product version related to this document.

Product Name VersionATN 905 V200R002C01

Intended AudienceThis document is intended for:l Commissioning Engineerl Data Configuration Engineerl Network Monitoring Engineerl System Maintenance Engineer

ATN 905 Multi-Service Access EquipmentConfiguration Guide (CLI) About This Document


ii

Symbol ConventionsSymbol Description

DANGERIndicates a hazard with a high level of risk, which if notavoided, will result in death or serious injury.

WARNINGIndicates a hazard with a medium or low level of risk, whichif not avoided, could result in minor or moderate injury.

CAUTIONIndicates a potentially hazardous situation, which if notavoided, could result in equipment damage, data loss,performance degradation, or unexpected results.

TIP Indicates a tip that may help you solve a problem or savetime.

NOTE Provides additional information to emphasize or supplementimportant points of the main text.

Command ConventionsConvention DescriptionBoldface The keywords of a command line are in boldface.Italic Command arguments are in italics.[ ] Items (keywords or arguments) in brackets [ ] are optional.{ x | y | ... } Optional items are grouped in braces and separated by

vertical bars. One item is selected.[ x | y | ... ] Optional items are grouped in brackets and separated by

vertical bars. One item is selected or no item is selected.{ x | y | ... }* Optional items are grouped in braces and separated by

vertical bars. A minimum of one item or a maximum of allitems can be selected.

[ x | y | ... ]* Optional items are grouped in brackets and separated byvertical bars. Several items or no item can be selected.



iii

GUI ConventionsConvention DescriptionBoldface Buttons, menus, parameters, tabs, window, and dialog titles

are in boldface. For example, click OK.> Multi-level menus are in boldface and separated by the ">"

signs. For example, choose File > Create > Folder.

Change HistoryUpdates between document issues are cumulative. Therefore, the latest document issue containsall updates made in previous issues.

Changes in Issue 03 (2013-11-22)This document has the following updates:Known bugs are fixed.

Changes in Issue 02 (2013-08-15)This document has the following updates:Known bugs are fixed.

Changes in Issue 01 (2013-05-30)This document is the first release of the V200R002C01 version.



iv

Contents

About This Document.....................................................................................................................ii1 Application Scenario Overview..................................................................................................11.1 Small-cell Base Station Bearer Scenario........................................................................................................................21.2 EDD Scenario.................................................................................................................................................................22 Configuration Overview..............................................................................................................52.1 Networking Models........................................................................................................................................................62.2 Configuration Overview.................................................................................................................................................72.2.1 Select Overall Solution..............................................................................................................................................132.2.2 Select Management Plane Configuration Solution....................................................................................................142.2.3 Select Service Solution..............................................................................................................................................162.3 Recommended Solutions..............................................................................................................................................193 Solution 1: Native IP VRF Static Route Access......................................................................233.1 Scenario Introduction...................................................................................................................................................253.2 Logging In to the ATN 905..........................................................................................................................................283.2.1 Logging In to the ATN 905 by Using SSH...............................................................................................................283.2.2 Logging In to the ATN 905 by Using the Console Interface....................................................................................303.3 Configuring Basic Information.....................................................................................................................................333.3.1 Configuring an NE Name..........................................................................................................................................343.3.2 Configuring the VTY User Interface.........................................................................................................................353.3.3 Configuring AAA Users............................................................................................................................................363.3.4 Configuring the SNMP..............................................................................................................................................373.4 Deploying the Management Plane................................................................................................................................393.4.1 Configuration Roadmap............................................................................................................................................403.4.2 Data Planning............................................................................................................................................................403.4.3 Configuring the Management Plane..........................................................................................................................413.5 Deploying VRF Lite Services.......................................................................................................................................413.5.1 Configuration Roadmap............................................................................................................................................423.5.2 Data Planning............................................................................................................................................................433.5.3 Configuring VRF Lite Services.................................................................................................................................463.6 Deploying Static Routes...............................................................................................................................................483.6.1 Configuration Roadmap............................................................................................................................................48

ATN 905 Multi-Service Access EquipmentConfiguration Guide (CLI) Contents


v

3.6.2 Data Planning............................................................................................................................................................493.6.3 Configuring Static Routes.........................................................................................................................................523.6.4 Checking Static Route Configurations......................................................................................................................533.7 Deploying QoS.............................................................................................................................................................543.7.1 Configuring QoS........................................................................................................................................................543.8 Deploying the Clock.....................................................................................................................................................553.8.1 Configuration Roadmap............................................................................................................................................553.8.2 Data Planning............................................................................................................................................................563.8.3 Configuring Synchronous Ethernet to Achieve Frequency Synchronization............................................................573.8.4 Configuring IEEE 1588v2 to Achieve Time Synchronization..................................................................................584 Solution 2: Native IP VRF Dynamic Route Access...............................................................604.1 Scenario Introduction...................................................................................................................................................624.2 Logging In to the ATN 905..........................................................................................................................................654.2.1 Logging In to the ATN by Using SSH......................................................................................................................654.2.2 Logging In to the ATN by Using the Console Interface...........................................................................................674.3 Configuring Basic Information.....................................................................................................................................704.3.1 Configuring NE Information.....................................................................................................................................714.3.2 Configuring the VTY User Interface.........................................................................................................................724.3.3 Configuring AAA Users............................................................................................................................................734.3.4 Configuring the SNMP..............................................................................................................................................744.4 Configuring the Management Plane.............................................................................................................................764.4.1 Configuring the Management Plane..........................................................................................................................764.5 Deploying VRF Lite Services.......................................................................................................................................784.5.1 Configuration Roadmap............................................................................................................................................784.5.2 Data Planning............................................................................................................................................................794.5.3 Configuring VRF Lite Services.................................................................................................................................834.6 Deploying the IGP........................................................................................................................................................854.6.1 Configuring the IS-IS................................................................................................................................................854.6.2 Deploying the OSPF..................................................................................................................................................904.7 Deploying QoS.............................................................................................................................................................944.7.1 Configuring QoS........................................................................................................................................................944.8 Deploying the Clock.....................................................................................................................................................954.8.1 Configuration Roadmap............................................................................................................................................954.8.2 Data Planning............................................................................................................................................................964.8.3 Configuring Synchronous Ethernet to Achieve Frequency Synchronization............................................................974.8.4 Configuring IEEE 1588v2 to Achieve Time Synchronization..................................................................................985 Solution 3: Native Ethernet Access........................................................................................1005.1 Scenario Introduction.................................................................................................................................................1015.2 Logging In to the ATN 905........................................................................................................................................1035.2.1 Logging In to the ATN by Using SSH....................................................................................................................1035.2.2 Logging In to the ATN by Using the Console Interface.........................................................................................105



vi

5.3 Configuring Basic Information...................................................................................................................................1085.3.1 Configuring NE Information...................................................................................................................................1095.3.2 Configuring the VTY User Interface.......................................................................................................................1105.3.3 Configuring AAA Users..........................................................................................................................................1115.3.4 Configuring the SNMP............................................................................................................................................1125.4 Configuring the Management Plane...........................................................................................................................1145.4.1 Configuration Roadmap..........................................................................................................................................1145.4.2 Data Planning..........................................................................................................................................................1155.4.3 Configuring the Management Plane........................................................................................................................1165.5 Deploying the serive...................................................................................................................................................1175.5.1 Configuration Roadmap..........................................................................................................................................1175.5.2 Data Planning..........................................................................................................................................................1185.5.3 Configuring Ethernet Services.................................................................................................................................1195.6 Deploying QoS...........................................................................................................................................................1215.6.1 Configuring QoS......................................................................................................................................................1215.7 Deploying the Clock...................................................................................................................................................1225.7.1 Configuration Roadmap..........................................................................................................................................1225.7.2 Data Planning..........................................................................................................................................................1235.7.3 Configuring Synchronous Ethernet to Achieve Frequency Synchronization..........................................................1245.7.4 Configuring IEEE 1588v2 to Achieve Time Synchronization................................................................................125



vii

1 Application Scenario OverviewAbout This Chapter

ATN 905 is small-sized, light-weighted, and low power-consuming case-shaped equipment. Theapplication scenarios of ATN 905 are divided into the small-cell base station bearer scenarioand the Ethernet demarcation device (EDD) scenario.

1.1 Small-cell Base Station Bearer Scenario1.2 EDD Scenario

ATN 905 Multi-Service Access EquipmentConfiguration Guide (CLI) 1 Application Scenario Overview


1

1.1 Small-cell Base Station Bearer ScenarioApplication Scenarios

1. Small-cell base station bearer scenarioMobile networks are transforming from dominant macro base stations to co-existing macroand small-cell base stations. In addition, small-cell base stations, with characteristics suchas low cost, wide coverage, and easy installation, will play a more and more important rolein future network construction.In Huawei's mobile bearer solution, ATN 905 devices are used as small-cell base stationbearer NEs and connected to the access device (the CSG in the figure) at the macro basestation in chain networking mode. As an extension of the IPRAN mobile bearer solutionbased on the macro base station, Huawei's mobile bearer solution integrates mobile bearerclock and maintenance solutions in an end-to-end manner, and features low cost, easydeployment, and easy O&M. Figure 1 shows the networking diagram of the solution usingthe ATN 905 as the bearer device at the small-cell base station.

Figure 1-1 Networking diagram of the small-cell base station bearer solution

CSG ASG RSG

IPRANSmall-cell Base Station Access

MME/SGW

RNC

BSC

Micro/Pico Macro CellMicro/Pico

Micro/PicoMicro/Pico

ATN 905ATN 905

NOTE

The mobile bearer device at the macro base station may be a third-party device. In this topic, Huawei'sIPRAN solution (ATN + CX networking) on the macro base station side is used as an example to illustratethe deployment configuration.

1.2 EDD ScenarioApplication Scenario Overview

A provider network is large-scale and complex, making management and fault locating difficult.The Ethernet demarcation device (EDD) is a key element in provider-level Ethernet services,leased network services, and applications of mobile backhaul networks. By deploying an EDD



2

on the user side and connecting it to the CPE, the provider separates the customer network fromthe provider network. As an EDD, Huawei's ATN 905 provides strong link OAM functions,performs end-to-end fault monitoring and diagnosis, and automatically verifies the service levelagreement (SLA).1. Dividing Maintenance Responsibilities for the Provider's Departments

As shown in Figure 1, the provider network is divided into different maintenance domainsbased on maintenance responsibilities. These maintenance domains are independent fromeach other and do not need to perceive each other. There are boundaries between differentmaintenance domains, and the boundaries need to be clearly demarcated to facilitatemaintenance. For example, how to divide maintenance responsibilities for the provider'swireless and network departments in the case of an argument? An EDD can be deployedat each base station to obtain information such as the throughput, packet loss rate, latency,and jitter.

Figure 1-2 Dividing Maintenance Responsibilities for the Provider's Departments

RNC

CSGASG RSG

BSC

EDD

ATN 905

MBH maintenance territory

Wireless maintenance territory

2. Demarcating the Provider Network and Enterprise Network

As shown in Figure 2, on an enterprise private line network, the enterprise user's CPEconnects to the provider's PE using an optical fiber. However, the CPE is usually far fromthe PE, so maintenance responsibilities are difficult to divide in the case of a fault.

Figure 1-3 Enterprise private line network with the EDD

CPE EDD PE EDDPE CPE

Provider Network User NetworkUser Network

ATN 905 ATN 905



3

As shown in Figure 3, an enterprise rents a 100M private line from a provider. However,the enterprise user considers the bandwidth as lower than 100 M. In the case of a fault onthe enterprise user network, the enterprise user tends to call the provider and complain.How can the provider divide the maintenance responsibilities? The provider can deploy anEDD near the CPE and test the throughput using RFC 2544 before the deployment so asto prove that the bandwidth meets the requirements. After services are provisioned, theEDD monitors service packets in real time using IP FPM, obtains information such as thethroughput, packet loss rate, latency, and jitter, and periodically provides an SLA to theenterprise user so as to prove the provider's network quality.

Figure 1-4 Enterprise private line network without the EDD

CPE PE PE CPE

Provider Network User NetworkUser Network

3. Demarcating the Provider Network and Leased Network

As shown in Figure 4, provider B rents a network from provider A. However, faults cannotbe clearly demarcated, so arguments always occur between providers A and B. To resolvethis problem, an EDD can be deployed on provider A's side and deploy OAM functionssuch as RFC 2544 and IP FPM based on live network requirements to monitor and measureinformation such as the throughput, packet loss rate, latency, and jitter. In this manner,maintenance responsibilities can be divided.

Figure 1-5 Demarcating the Provider Network and Leased Network

EDD PE PE

Provider NetworkWholesale Network

ATN 905

AB

NOTE

For easy description, the upstream network of the EDD is called aggregation network.



4

2 Configuration OverviewAbout This Chapter

2.1 Networking Models2.2 Configuration Overview2.3 Recommended Solutions

ATN 905 Multi-Service Access EquipmentConfiguration Guide (CLI) 2 Configuration Overview


5

2.1 Networking ModelsNetworking Model for the Configuration Example

The application scenarios of the ATN 905 are small-base station bearer and enterprise privateline EDD. From the deployment point of view, the solutions can be classified into the followingtypes by access technology.l Native IP access solutionl Native Ethernet access solutionIn both solutions, the ATN 905 is connected to the nearby network of the operator. If theoperator's network is regarded as an abstract "cloud", only the deployment and configuration ofthe part (marked by the dotted rectangle on the left) on the access network need to be considered.For the marked part of the access network, the configuration roadmaps and procedures in bothsolutions are basically the same. Therefore, this topic only provides detailed configurationdescription from the angle of the access technology. That is, scenarios are not differentiatedwhile only solutions are differentiated. The following typical networking models are providedfor the configuration example.l Native IP scenario: Layer 3 IP packets are forwarded between the ATN 905 and CSG.

CSG

Micro/Pico

Micro/Pico

Macro Cell

RNC/SGW

IPRAN

Native IPTraffic flow

ATN 905ATN 905

l Native Ethernet scenario: Layer 2 Ethernet packets are forwarded between the ATN 905

and CSG.



6

CSG

Micro/Pico

Micro/Pico

Macro Cell

RNC/SGW

IPRAN

Native EthTraffic flow

ATN 905ATN 905

2.2 Configuration OverviewOverall Configuration Roadmap

1. Overall solution selection: Determine the small-cell base station bearer solution or EDDbearer solution based on the macro base station mobile bearer solution or aggregationnetwork bearer solution.

NOTETypical networking models are used in the following schematic diagrams, regardless of the small-cell basestation bearer solution or EDD bearer solution. For details, see Networking Models.

Scenario OverallSolution

Diagram

l If a Layer 3 access solution(such as HVPN) is used onthe macro base station side,you are advised to deploythe native IP solutionbetween the ATN 905 andcell site gateway (CSG) toforward services.

l If a Layer 3 access solution(such as MPLS/IP) is usedon the aggregation network,you are advised to deploythe native IP solutionbetween the ATN 905 andPE to forward services.

This solution facilitates end-to-end IP-based continuity check(CC) and performancemonitoring.

Native IPsolution

CSG

Micro/Pico Macro Cell

RNCIPRAN

Native IP

ATN 905

Micro/Pico

ATN 905



7


Diagram

l If a Layer 2 or Layer 2 +Layer 3 access solution(such as mixed VPN) is usedon the macro base stationside, you are advised todeploy the native Ethernetsolution between the ATN905 and CSG totransparently transmitpackets from the small-cellbase station.

l If a Layer 2 access solution(such as metro Ethernet) isused on the aggregationnetwork, you are advised todeploy the native Ethernetsolution between the ATN905 and PE to forwardservices.

In this solution, the VLANinformation of the small-cellbase station or enterpriseprivate line user is notmodified. Instead, packets ofthe small-cell base station orenterprise private line user aretransparently transmitted.

NativeEthernetsolution

CSG


RNCIPRAN

Native Eth

ATN 905

Micro/Pico

ATN 905

2. Service solution selection: During actual service deployment, multiple feature solutions

are available. The following describes the applicable scenarios of these feature solutions.You can choose an appropriate solution based on the actual networking requirements.a. Select a management plane configuration solution based on the overall solution

selected in step 1 and the actual networking requirements.Prerequisite

Scenario Management Plane Mode

Advantage Disadvantage

Native IP/NativeEthernetsolution

The networkscale is small.

Public networkstatic route

The reliability and stabilityare high.

The scalability is poor. Whenthe network topologychanges, static routes need tobe manually configured again.



8

Prerequisite



1. Thenetworkscale islarge.

2. Upstreamdevicesaremanagedusing thepublicnetworkIGP.

Public networkIGP

1. The scalability is high androutes are automaticallyadjusted when the networktopology changes.

2. The management modecan be the same as that ofthe upstream IPRAN oraggregation network.

IGP configurations need to beplanned and maintained.

The ATN 905is networkedwith Huaweiproducts.

Privatenetwork DCN

1. The configuration issimple and managementroutes do not need to beconfigured by NE.

2. The scalability is high.When devices are added tothe network, themanagement planeconfiguration of otherdevices does not need to bemodified.


The CSG (or PE) must be aHuawei product.

Figure 2-1 Management plane configuration diagram

CSG

Macro Cell

RNC

IPRANATN 905ATN 905

Micro/Pico

Micro/Pico

Micro/Pico

Micro/PicoPublic network static route/

Public network IGP/Private network DCN

management flow

b. Select a service plane access mode based on the overall solution selected in step 1and the actual networking requirements.



9

a. If the native IP solution is selected in step 1:Prerequisite Scenario Access Mode Advantage DisadvantageNative IPsolution

Users orservices needto beseparated.

VRF access This solution can separateservices.l This solution can separate

different wirelessoperators accessed to anetwork using the ATN905 as the backhauldevice for the small-cellbase station.

l This solution can separatedifferent enterprise usersaccessed to a networkusing the ATN 905 as theEDD.

Configurations for thissolution is complex because aunique IP route and InteriorGateway Protocol (IGP)process need to be plannedand configured for eachvirtual routing andforwarding (VRF) instance asrequired.

Users orservices donot need to beseparated.

Entire publicnetworkaccess

The planning andconfiguration is simple. Aunique IP route and IGPprocess for each VRFinstance can be resolved onlyby making public networkchannels available.

This solution cannot separateusers or separate servicesfrom the management plane.IP addresses need to beplanned in a centralizedmanner.

Figure 2-2 Native IP service access (VRF access) configuration diagram

VRF2

VRF2

CSG

Macro Cell

RNC

IPRANATN 905ATN 905

VRF1

VRF1

main interface

VRF1 service flowVRF2 service flowDot1q sub-interface



10

Figure 2-3 Native IP service access (public network access) configurationdiagram

VRF2

VRF2

CSG

Macro Cell

RNC

IPRANATN 905

ATN 905

Main interfaceService flow

VRF1

VRF1

b. If the native Ethernet solution is selected in step 1:Prerequisite Scenario Access Mode Advantage DisadvantageNativeEthernetsolution


Hybridinterfaceaccess

Extra encapsulation costs aresaved.

VLANs for customers andoperators need to be plannedin a centralized manner.

Figure 2-4 Native Ethernet service access (hybrid interface access) configurationdiagram

CSG

Macro Cell

RNC

IPRANATN 905

ATN 905

Hybrid interface

VLAN10

port trunk allow-pass vlan 10 to 20

VLAN10VLAN20

VLAN20

Service flow

c. If the native IP solution is selected in step 1, select a service plane routing modebased on the actual networking requirements. If the native Ethernet solution is selectedin step 1, skip this step.



11

Prerequisite

Scenario Service planerouting mode


Native IPsolution


Static Route 1. The configuration issimple.

2. The reliability andstability are high, andnetwork flapping causedby a network topologychange is prevented.

The scalability is poor.l When a small-cell base

station is added to thenetwork, static routesneed to be added by hopfor the network segmentfrom the small-cell basestation to thecorresponding macrobase station.

l When a PE is added to thenetwork, static routesneed to be added by hopfor the network segmentfrom the PE to the EDD.

The networkscale is large.

IGP route 1. The scalability is high.When a device is added tothe network, only theinterface configurationson its adjacent devicesneed to be adjusted.Configurations on otherdevices do not need to bemodified.

1. IGP configurations needto be planned andmaintained.

2. Network flapping mayoccur when the networktopology changes.

Figure 2-5 Service plane route configuration diagram

CSG

Macro Cell

RNC

IPRANATN 905

ATN 905

Service flowStatic route / IGPd. Select the QoS deployment mode based on the actual networking requirements.

Scenario QoS ModeTraffic management is required. Simple traffic classification



12

e. Select the clock deployment mode based on the actual networking requirements.

Scenario Clock ModeFrequency synchronization needs tobe achieved between NEs.

Synchronous Ethernet

Time synchronization needs to beachieved between NEs.

1588v2

2.2.1 Select Overall SolutionSolution Selection Principle

Determine the small-cell base station bearer solution or EDD bearer solution based on the macrobase station mobile bearer solution or aggregation network bearer solution.


Diagram

l If a Layer 3 access solution(such as HVPN) is used onthe macro base station side,you are advised to deploythe native IP solutionbetween the ATN 905 andcell site gateway (CSG) toforward services.

l If a Layer 3 access solution(such as MPLS/IP) is usedon the aggregation network,you are advised to deploythe native IP solutionbetween the ATN 905 andPE to forward services.

This solution facilitates end-to-end IP-based continuity check(CC) and performancemonitoring.

Native IPsolution

CSG


RNCIPRAN

Native IP

ATN 905

Micro/Pico

ATN 905



13


Diagram

l If a Layer 2 or Layer 2 +Layer 3 access solution(such as mixed VPN) is usedon the macro base stationside, you are required todeploy the native Ethernetsolution between the ATN905 and CSG totransparently transmitpackets from the small-cellbase station.

l If a Layer 2 access solution(such as metro Ethernet) isused on the aggregationnetwork, you are required todeploy the native Ethernetsolution between the ATN905 and PE to forwardservices.

In this solution, the VLANinformation of the small-cellbase station or enterpriseprivate line user is notmodified. Instead, packets ofthe small-cell base station orenterprise private line user aretransparently transmitted.

NativeEthernetsolution

CSG


RNCIPRAN

Native Eth

ATN 905

Micro/Pico

ATN 905

2.2.2 Select Management Plane Configuration SolutionSolution Selection Principle

Select a management plane configuration solution based on the overall solution selected instep 1 and the actual networking requirements.

Prerequisite



Native IP/NativeEthernetsolution


Public networkstatic route

The reliability and stabilityare high.

The scalability is poor. Whenthe network topologychanges, static routes need tobe manually configured again.



14

Prerequisite



1. Thenetworkscale islarge.

2. Upstreamdevicesaremanagedusing thepublicnetworkIGP.

Public networkIGP

1. The scalability is high androutes are automaticallyadjusted when the networktopology changes.


IGP configurations need to beplanned and maintained.

The ATN 905is networkedwith Huaweiproducts.

the VRF ofPrivatenetwork DCN

1. The configuration issimple and managementroutes do not need to beconfigured by NE.

2. The scalability is high.When devices are added tothe network, themanagement planeconfiguration of otherdevices does not need to bemodified.


The CSG (or PE) must be aHuawei product.


CSG

Macro Cell

RNC

IPRANATN 905ATN 905

Micro/Pico

Micro/Pico

Micro/Pico

Micro/PicoPublic network static route/

Public network IGP/Private network DCN

management flow



15

2.2.3 Select Service SolutionOverview

The service solution selection involves the following parts:1. Selecting the service plane access mode2. Selecting the service plane routing mode3. Selecting the QoS deployment mode4. Selecting the clock deployment mode

Solution Selection Principle1. Select a service plane access mode based on the overall solution selected in step 1 and the

actual networking requirements.a. If the native IP solution is selected in step 1:

Prerequisite Scenario Access Mode Advantage DisadvantageNative IPsolution

Users orservices needto beseparated.

VRF access This solution can separateservices.l This solution can separate

different wirelessoperators accessed to anetwork using the ATN905 as the backhauldevice for the small-cellbase station.

l This solution can separatedifferent enterprise usersaccessed to a networkusing the ATN 905 as theEDD.

Configurations for thissolution is complex because aunique IP route and InteriorGateway Protocol (IGP)process need to be plannedand configured for eachvirtual routing andforwarding (VRF) instance asrequired.


Entire publicnetworkaccess

The planning andconfiguration is simple. Aunique IP route and IGPprocess for each VRFinstance can be resolved onlyby making public networkchannels available.

This solution cannot separateusers or separate servicesfrom the management plane.IP addresses need to beplanned in a centralizedmanner.



16

Figure 2-7 Native IP service access (VRF access) configuration diagram

VRF2

VRF2

CSG

Macro Cell

RNC

IPRANATN 905ATN 905

VRF1

VRF1

main interface

VRF1 service flowVRF2 service flowDot1q sub-interface

Figure 2-8 Native IP service access (public network access) configuration diagram

VRF2

VRF2

CSG

Macro Cell

RNC

IPRANATN 905

ATN 905

Main interfaceService flow

VRF1

VRF1

b. If the native Ethernet solution is selected in step 1:Prerequisite Scenario Access Mode Advantage DisadvantageNativeEthernetsolution


Hybridinterfaceaccess

Extra encapsulation costs aresaved.

VLANs for customers andoperators need to be plannedin a centralized manner.



17

Figure 2-9 Native Ethernet service access (hybrid interface access) configurationdiagram

CSG

Macro Cell

RNC

IPRANATN 905

ATN 905

Hybrid interface

VLAN10

port trunk allow-pass vlan 10 to 20

VLAN10VLAN20

VLAN20

Service flow

2. If the native IP solution is selected in step 1, select a service plane routing mode basedon the actual networking requirements. If the native Ethernet solution is selected in step 1,skip this step.

Prerequisite

Scenario Service planerouting mode


Native IPsolution


Static Route 1. The configuration issimple.

2. The reliability andstability are high, andnetwork flapping causedby a network topologychange is prevented.

The scalability is poor.l When a small-cell base

station is added to thenetwork, static routesneed to be added by hopfor the network segmentfrom the small-cell basestation to thecorresponding macrobase station.

l When a PE is added to thenetwork, static routesneed to be added by hopfor the network segmentfrom the PE to the EDD.

The networkscale is large.

IGP route 1. The scalability is high.When a device is added tothe network, only theinterface configurationson its adjacent devicesneed to be adjusted.Configurations on otherdevices do not need to bemodified.





18

Figure 2-10 Service plane route configuration diagram

CSG

Macro Cell

RNC

IPRANATN 905

ATN 905

Service flowStatic route / IGP

3. Select the QoS deployment mode based on the actual networking requirements.Scenario QoS ModeTraffic management is required. Simple traffic classification

4. Select the clock deployment mode based on the actual networking requirements.

Scenario Clock ModeFrequency synchronization needs to beachieved between NEs.

Synchronous Ethernet

Time synchronization needs to beachieved between NEs.

1588v2

2.3 Recommended SolutionsIntroduction to the Recommended Solutions

Huawei recommends the following solutions based on the common networking modes:1. Solution 1: Native IP + public network static management plane + VRF access + static

route2. Solution 2: Native IP + DCN private network management plane + VRF access +

dynamic route3. Solution 3: Native Ethernet + public network IGP management plane + hybrid

interface accessNOTE

The preceding recommended solutions are only common ones and there are also other combination types.

l Solution 1: Native IP + public network static management plane + VRF access + staticroute



19

Application Scope Advantage ConstraintThis solution applies tosmall-scale networks thatuse a Layer 3 accesssolution as the macro basestation bearer solution (orthe aggregation networkbearer solution in theEDD scenario) in amobile bearer solution.

1. The configuration issimple. The basic nativeIP feature is used,dynamic protocols suchas the IGP are notinvolved, and the IGPdoes not need to beplanned.

2. Users are separatedusing the VRF.

3. Interconnection withthird-party equipment issupported. That is, themobile bearer NE (orPE) on the macro basestation side can be athird-party NE.

1. This solution does notapply to large-scalenetworks.

2. The scalability is poor.l When a small-cell

base station is addedto the network, staticroutes need to beadded by hop for thenetwork segmentfrom the small-cellbase station to thecorresponding macrobase station.

l When a PE is addedto the network, staticroutes need to beadded by hop for thenetwork segmentfrom the PE to theEDD.

l Solution 2: Native IP + DCN private network management plane + VRF access +

dynamic routeApplication Scope Advantage ConstraintThis solution applies tonetworks of any scale thatuse a Layer 3 accesssolution as the macro basestation bearer solution (orthe aggregation networkbearer solution in theEDD scenario) in amobile bearer solution.NOTE

This solution applies tonetworks built with Huaweiequipment only. Equipmentcan be managed togetherwith the upstreamequipment using a DCNprivate network, which isconvenient and effective.

1. This solution isrecommended forrelatively largenetworks.

2. The scalability is high.When a small-cell basestation is added to thenetwork, only theinterface configurationson its adjacent devicesneed to be adjusted.Configurations on otherdevices do not need to bemodified.

3. Users are separatedusing the VRF.



l Solution 3: Native Ethernet + public network IGP management plane + hybrid

interface access



20

Application Scope Advantage ConstraintThis solution applies tonetworks of any scale thatuse a Layer 2 accesssolution as the macro basestation bearer solution (orthe aggregation networkbearer solution in theEDD scenario) in amobile bearer solution.

1. This solution isespecially applicable toscenarios in which theATN 905 is used as theEDD.

1. A protocol needs to beconfigured to preventloops and Layer 2broadcast storms.

2. VLANs for customersand operators do notneed to be separated.

Overall Configuration Roadmap of the Recommended SolutionsOption

Solution 1: Native IP+ Public NetworkStatic ManagementPlane + VRF Access +Static Route

Solution 2: Native IP +DCN Private NetworkManagement Plane +VRF Access + DynamicRoute

Solution 3: NativeEthernet + PublicNetwork IGPManagement Plane +Hybrid Interface Access

Managementplaneconfiguration

1. Use Layer 3subinterfacesbetween the ATN905 and backhauldevice at the macrobase station toestablish publicnetwork IPconnections.

2. On the ATN 905,create a loopbackinterface on the ATN905 and configure amanagement IPaddress for it.

3. Configure publicstatic routes leadingfrom the ATN 905 tothe NMS by hop forthe network segmentfrom the ATN 905 tothe CSG (or PE).

1. Plan and configure anNE IP address for eachNE.

2. Manage the ATN 905using the DCNmanagement plane.

1. Establish publicnetwork IPinterconnectionsbetween the ATN 905and the CSG (or PE)using Layer 3subinterfaces.



21

Option

Solution 1: Native IP+ Public NetworkStatic ManagementPlane + VRF Access +Static Route

Solution 2: Native IP +DCN Private NetworkManagement Plane +VRF Access + DynamicRoute

Solution 3: NativeEthernet + PublicNetwork IGPManagement Plane +Hybrid Interface Access

Serviceconfiguration

1. Establish VRF-instance-based IPconnections betweenthe ATN 905 and theCSG (or PE) usingLayer 3subinterfaces.

2. Bind the AC port ofthe ATN 905 to theVRF instance thatthe directly-connected small-cellbase station (or CPE)belongs to.

3. Configure staticroutes leading to thesmall-base stationand RNC by hop forthe network segmentfrom the ATN 905 tothe CSG (or PE).

1. Establish VRF-instance-based IPconnections betweenthe ATN 905 and theCSG (or PE) usingLayer 3 subinterfaces.

2. Bind the AC port of theATN 905 to the VRFinstance that thedirectly-connectedsmall-cell base station(or CPE) belongs to.

3. Configure anindependent IGPprocess for each VRFinstance between theATN 905 and the CSG(or PE) to learn theroutes leading to thesmall-cell base station(or CPE) and RNC (orPE) respectively.

1. Switch the AC port ofthe ATN 905 to a Layer2 switching port andconfigure a segment ofVLANs that the ACinterface allows to passthrough.

2. Switch the NNI of theATN 905 to a Layer 2switching port and add asegment of VLANs thateach AC interfaceallows to pass through.

3. On the access port of theCSG (or PE), configurea virtual leased line(VLL) for each serviceVLAN or terminate theVLAN for Layer 3forwarding.

QoSconfiguration

Enable simple traffic classification for each service interface.

Clockconfiguration

1. Enable synchronous Ethernet and IEEE 1588v2 for each interface.2. Configure the priority of imported clock sources for the NNI.



22

3 Solution 1: Native IP VRF Static RouteAccess

About This Chapter

Native IP VRF static route access is applicable to small-sized networks, and mainly adopts theNative IP service solution. In this solution, management plane packets are transmitted throughpublic network static routes, static routes are created between ATN 905 devices and accessdevices in a macro base station, and meanwhile, VRF instances are configured to isolate servicesof different carriers.

3.1 Scenario IntroductionThis section gives a brief introduction about scenarios, including overview, configurationroadmap, and data planning.3.2 Logging In to the ATN 905This chapter describes how to log in to the ATN 905 for later commissioning. Two login methods,login by using the console interface and SSH, are introduced.3.3 Configuring Basic InformationBefore configuring services, you need to perform basic configurations, including the devicename, user login parameter, authentication, authorization, and accounting (AAA), and SimpleNetwork Management Protocol (SNMP) configurations, for the devices.3.4 Deploying the Management PlaneThe management plane is an exclusive logical channel that is used to transmit managementpackets between NEs on an ATN network. Logical channels of the management plane and otherplanes, such as the service plane, are separated, so devices can still be managed when the otherplanes become abnormal.3.5 Deploying VRF Lite ServicesThis topic describes how to deploy VRF Lite services.3.6 Deploying Static RoutesStatic routes, instead of dynamic routes, are sufficient for a simple network to function.3.7 Deploying QoS

ATN 905 Multi-Service Access EquipmentConfiguration Guide (CLI) 3 Solution 1: Native IP VRF Static Route Access


23

You can deploy quality of service (QoS) on a carrier network to provide differentiated QoSassurance as required.3.8 Deploying the ClockYou are advised to use a clock synchronization solution based on actual clock synchronizationrequirements.



24

3.1 Scenario IntroductionThis section gives a brief introduction about scenarios, including overview, configurationroadmap, and data planning.

OverviewSolution 1: Native IP VRF static route access (native IP + public network staticmanagement plane + static route + VRF access)

Figure 3-1 Example network of Native IP VRF static route access

VRF2

VRF2

CSG

Macro Cell

RNC

IPRANATN 905ATN 905

VRF1

VRF1main interfaceDot1q sub-interfacepublic network management planeVRF1 service flowVRF2 service flow

Static route



25

Table 3-1 Solution informationSolution Feature Applicable

ScenarioSolutionAdvantage

SolutionConstraint

l Serviceconfigurationsfor small-cellbase stations:Native IP

l Managementplane:Public networkstatic routes

l IP route:Static routes

l Native IP access:VRF access

1. Scenario in whichthe carriersolution on themacro basestation sideadopts the Layer3 access solution

2. Small-sizednetwork

3. Small-cell basestation providingaccess formultiple wirelesscarriers (Servicesof differentwireless carriersare isolated fromeach other.)

4. Huawei IPRANproducts or thethird-party NEsdeployed in theupstreamdirection of themacro basestation

1. Theconfigurationsare very simpleand easy tounderstand. Basicfeatures areapplied to thissolution, anddynamic routingprotocols, forexample, theInterior GatewayProtocol (IGP),are not includedin this solution.

2. VRF instancesare created forservice isolation.Wireless devicesare insensible tothe VRFinstances. TheVRF instancesare created ontransmissionequipment toisolate services ofdifferent wirelessusers.

1. This solution isnot applicable tolarge-sizednetworks.

2. This solution is ofpoorexpansibility.Specifically, ifthe service IPaddress of thesmall-cell basestation changes,the static routesconfigured on thebackhaul devicesneed to bechangedaccordingly.

Configuration Roadmapl Configure a management plane (based on public network static routes) between the ATN

905 and the CSG in a macro base station.l Use dot1p sub-interfaces to create VRF-instance-based IP connections between the ATN

905 and the CSG in a macro base station.NOTE

1. When services need to be isolated at station access devices, create multiple VRFs on the ATN 905and CSG devices so that different services use their own VRFs. The VRFs must be the same as thoseconfigured on the macro base station.

2. When services do not need to be isolated at station access devices, create and configure only one VRFon the ATN 905 and CSG devices so that different services use the same VRF.

l Hop by hop configure static routes from the ATN 905 and the CSG in a macro base stationto the small-cell base station and the RNC. Configure static routes between ATN 905 and



26

small-cell base stations that are directly connected to it, between ATN 905 and itsdownstream ATN 905, and between ATN 905 and small-cell base stations that are directlyconnected to the downstream ATN 905.

l Deploy simple traffic classification (STC) on the ATN 905.l Deploy Synchronous Ethernet (SyncE) on the ATN 905 to implement frequency

synchronization; deploy IEEE 1588v2 to implement time synchronization.

Data PlanningItem Planning GuidelinesBasic configurationparameters:l NE namel User login parameterl SNMPl AAA

You are advised to configure the basic configuration parametersexcept NE name in the centralized manner based on the entirenetwork. In this way, these basic configuration parameters areplanned once for all.

Small-cell base stationdata:l Voice services IP

addressl Data services IP

addressl VRF

1. Different VRF instances need to be configured to isolateservices of different wireless carriers. VRF instances areplanned by wireless carriers.

2. A service IP address pool (32-bit mask) needs to be planned.3. A management IP address pool (32-bit mask) needs to be

planned.

ATN 905 data:l Management IP

addressl IP address of the link

that connects thesmall-cell base stationto the ATN 905

l VRF

1. A service IP address pool (32-bit mask) needs to be planned.2. An IP address pool of links that connect small-cell base

stations to the ATN 905 needs to be planned.3. Each AC port of the ATN 905 needs to be added into the

related VRF instance. The dot1q sub-interfaces between thebackhaul devices are bound to different VRF interfaces totransmit packets hop by hop.

Static route:l Destination IP

addressl Next-hop IP address

1. Static routes from the ATN 905 to the small-cell base stationneed to be configured.

2. Static routes from the ATN 905 to the downstream ATN 905and small-cell base station need to be configured.

3. The default route from the ATN 905 to the RNC needs to beconfigured.

4. Static routes are imported into the BGP area configured on thebackhaul device in a macro device.

QoS STC is deployed on each service interface of the ATN 905.



27

Item Planning GuidelinesClock SyncE and 1588v2 functions are enabled on the ATN 905 so that

the ATN 905 traces the clock and time of the upstream deviceand transmits the clock signals to base stations.

3.2 Logging In to the ATN 905This chapter describes how to log in to the ATN 905 for later commissioning. Two login methods,login by using the console interface and SSH, are introduced.

3.2.1 Logging In to the ATN 905 by Using SSHThis section describes how to log in to the ATN 905 by using SSH. SSH is a secure remote loginprotocol developed based on the traditional Telnet protocol. Compared with Telnet, SSH isgreatly improved in terms of the authentication mode and data transmission security.Figure 3-2 shows the networking diagram for logging in to the ATN 905 by using SSH.

Figure 3-2 Networking diagram for logging in to the ATN 905 by using SSH

SSH Client SSH Server

network

Prerequisitel The ATN 905 is running properly.l The ATN 905 has been logged in using the console interface and an IP address for each

interface has been configured on the ATN 905.l A direct or reachable route exists between the SSH client and the ATN 905.

NOTE

Perform the following configurations on the ATN 905 that serves as the SSH server. This section describes onlythe SSH login by using the PuTTY program.

ProcedureStep 1 As shown in the following figure, set the IP address of the ATN 905 to 192.168.1.1 and the login

protocol to SSH.



28

NOTE

After the ATN is powered on for the first time, you can log in to it in STelnet mode. The IP address of themanagement network interface Ethernet0/0/0 (the console interface) is 129.0.0.1. If the ATN has accessedthe network when it is powered on for the first time, its IP address 129.0.0.1 will be automatically changedto the IP address that DHCP obtains during the startup.

Figure 3-3 Login by using the PuTTY program

Step 2 Enter the user name root and the password Changeme_123.

NOTE

After the ATN is powered on for the first time, you can log in to it in STelnet mode. The user name andpassword are root and Changeme_123 respectively. After logging in to the ATN, change the defaultpassword in time.



29

Figure 3-4 Login using the PuTTY program

----End

3.2.2 Logging In to the ATN 905 by Using the Console InterfaceThis section describes how to use the HyperTerminal in Windows on the PC to log in to theATN 905 after setting up a local configuration environment with the console interface.

ContextFigure 3-5 shows the networking diagram for logging in to the NE80E/40E by using the consoleinterface.

Figure 3-5 Networking diagram for logging in to the ATN 905 by using the console interface

PC ATN

Prerequisitel The ATN 905 is running properly.l The PC is connected to the ATN 905 through an asynchronous interface.l Installing terminal emulation program on the PC (such as Windows XP HyperTerminal)

NOTE

Perform the following configurations on the HyperTerminal on the PC.The console port applies the non-standard serial port communication cable sequence. For more information, seeATN 905Multi-service Access Equipment Installation Guide.



30

ProcedureStep 1 Use a serial cable to connect the serial interface on the PC and the console interface on the ATN

905.For more information about the console interface, see the ATN 905Multi-service AccessEquipmentHardware Description.

Step 2 Start the HyperTerminal on the PC.Choose Start > Programs > Accessories > Communications to start the HyperTerminal inWindows.

Step 3 Set up a connection.As shown in Figure 3-6, enter the name of the new connection in the Name text box, and selectan icon. Then, click OK.

Figure 3-6 Setting up a connection

Step 4 Set a connection port.

In the Connect To dialog box shown in Figure 3-7, select a port from the drop-down list boxof Connect using according to the port actually used on the PC or terminal. Then, click OK.



31

Figure 3-7 Setting a connection port

Step 5 Set communication parameters.

When the COM1 Properties dialog box is displayed as shown in Figure 3-8, set the COM1properties according to the description in Figure 3-8 or by clicking Restore Defaults.

NOTE

l Setting the COM1 properties according to the description in Figure 3-8 and setting them by clickingRestore Defaults have the same effect. The default settings of the console interface will be used.

l When you log in to the ATN 905 by using the console interface, ensure that the COM1 properties onthe HyperTerminal are consistent with the interface attribute settings on the ATN 905. Otherwise, thelogin will fail. This means that if default settings are not used for the interface attributes on the ATN905, the COM1 properties on the HyperTerminal must be changed to be consistent with the interfaceattribute settings on the ATN 905.



32

Figure 3-8 Setting communication parameters

----End

Commissioning ResultAfter the preceding configurations are complete, press Enter. An initial password is requiredfor the first login. Set an authentication password. The system automatically saves the setpassword.An initial password is required for the first login via the console.Set a password and keep it safe! Otherwise you will not be able to login via the console. Please configure the login password (6-16)Enter Password: Confirm Password:

If the login fails, click Disconnect and then Call. If the login still fails, repeat Step 1 to checkwhether the parameters or physical connections are correct. If they are correct, log in to the ATN905 again.

3.3 Configuring Basic InformationBefore configuring services, you need to perform basic configurations, including the devicename, user login parameter, authentication, authorization, and accounting (AAA), and SimpleNetwork Management Protocol (SNMP) configurations, for the devices.



33

3.3.1 Configuring an NE NameIf multiple devices on a network need to be managed, set equipment names to identify eachdevice.

Data PlanningAn NE name consists of the site name, device model, and device number. Each NE is named inthe format of AA-BB-CC. The following provides the meaning of the letters.l AA: device model, for example, ATN 910 or ATN 905l BB: site name, for example, SmallCellSiteAl CC: device number, starting from 001For example, ATN905-SmallCellSiteA-001 refers to an ATN 905 numbered 001 at siteSmallCellSiteA.

Parameter Value Descriptionsysname ATN905-

SmallCellSiteA-001Indicates the NE name.

NOTEAll the NEs involved in this document are named as shown in the following figure.

Figure 3-9 NE names

ATN910-MacroCellSite-003

Micro/Pico

Micro/Pico

Macro Cell

RNC

IPRAN

Micro/Pico

Micro/Pico ATN905-SmallCellSiteB-002

ATN905-SmallCellSiteA-001

SmallCellSiteA1

SmallCellSiteA2

SmallCellSiteB1

SmallCellSiteB2

Configuration Processl Configure the name of the NE as ATN905-SmallCellSiteA-001.

sysname ATN905-SmallCellSiteA-001

l Configure the name of the NE as ATN905-SmallCellSiteB-002.sysname ATN905-SmallCellSiteB-002



34

l Configure the name of the NE as ATN910-MacroCellSite-003.sysname ATN910-MacroCellSite-003

3.3.2 Configuring the VTY User InterfaceTo log in to an ATN device remotely, you can configure the virtual type terminal (VTY) userinterface to ensure equipment security.

Data PlanningTo log in to an ATN device in telnet or Secure Shell (SSH) mode, you can configure the VTYuser interface to ensure equipment security. The following parameters are involved: themaximum number of VTY user interfaces, user authentication mode, user privilege, and VTYattributes.l By setting the maximum number of VTY user interfaces, you can limit the number of users

who can log in to the ATN device concurrently.l By setting the user authentication mode, you can enhance the equipment security. The user

authentication mode can be set to AAA authentication or password authentication.1. The AAA authentication mode is based on users, ensuring high security. To log in to

the ATN device, you need to enter the user name and password.2. The password authentication mode is based on VTY channels, requiring simple

configuration while ensuring high security. You only need to be create a loginpassword.

l By setting the user privilege, you can differentiate the access rights of different users onthe ATN device to enhance the management security. User privileges are divided into 16levels, which are numbered 0 to 15. A larger value indicates a higher user privilege.

l You can configure the VTY attributes of a VTY user interface, such as the timeout intervalof communication failure for login users. Each VTY attribute on the VTY user interfacehas a default value on the ATN device. You can re-configure the terminal attributes asrequired.

NOTESet these parameters based on the actual network conditions, such as network size and topology. Thefollowing recommended values in this example are only for reference.

Parameter Value Descriptionuser-interfacemaximum-vty

15 Sets the maximum number ofusers that are allowed to login to the NE to 15.NOTE

When the value of thisparameter is set to 0, no user(even the NMS user) can log into the ATN device through theVTY user interface.



35

Parameter Value Descriptionuser-interface vty 0 14 Indicates that the maximum

number of VTY userinterfaces is the total numberof users that have logged in tothe NE through Telnet orSTelnet.

authentication-mode aaa Sets the authentication modeto AAA authentication forusers that attempt to log in tothe NE.

protocol inbound ssh Specifies the login protocolsupported by the VTY userinterface to SSH.

user privilege level 3 Specifies the command levelto level 3.

idle-timeout 5 0 Sets the timeout interval ofcommunication failure forlogin users.

Configuration ProcessPerform the following configurations on all ATN devices:1. Set the maximum number of VTY user interfaces.

user-interface maximum-vty 15 //Set the maximum number of VTY user interfaces that are allowed to log in to the NE at the same time.

2. Configure VTY attributes.user-interface vty 0 14 //Perform configurations for VTY 0 to VTY 14. protocol inbound ssh authentication-mode aaa user privilege level 3 idle-timeout 5 0

3.3.3 Configuring AAA UsersIf the user authentication mode is set to AAA authentication on an ATN device, you need toconfigure user names and passwords on the ATN device to manage and authenticate users.

Data PlanningIf the user authentication mode is set to AAA authentication in an ATN device, a user needs tokeep the login user name and password properly, and uses them to log in to the ATN device.The levels of commands that can be used by users logging in to an ATN device concurrently aredetermined by the privileges of these users in the AAA configuration.



36


Parameter Value Descriptionaaa - Enters the AAA view to

create a user, set a user level,or configure anauthentication scheme, anauthorization scheme, anaccounting scheme, or adomain, so that the NEauthenticates users.

local-user XXXpassword cipher XXX

USER01Hello@*#123

Adds a local user USER01.

local-user level 3 Sets the user level for thelocal user. The systemmanages commands bycommand level. A user canuse only the commandswhose levels are lower thanor equal to the user level.

local-user xxxservice-type xxx

USER01ssh

Sets the access type of localusers to SSH.

Configuration ProcessPerform the following configurations on all ATN devices:aaa local-user USER01 password cipher Hello@*#123 //Add a local uer (USER01) and set the password. local-user USER01 level 3 //Set the user level of the local user. local-user USER01 service-type ssh //Set the access type for the user.

NOTERequirements on user names and passwords for ATN products are as follows:l A local user name contains 1 to 253 characters.l A password must contain eight characters at least.l A password must contain digits, upper-case and lower-case letters, and special characters, excluding

question marks (?) and spaces.l The password cannot be the same as the user name or the user name in reverse order.

3.3.4 Configuring the SNMPAfter the Simple Network Management Protocol (SNMP) is configured, the NMS can monitorand manage NEs.



37

Data PlanningThe SNMP is a standard network management protocol widely used on TCP/IP networks. TheNMS can manage NEs using the SNMP. Specifically, the SNMP defines several devicemanagement operations that can be performed by the NMS and alarms that can be automaticallysent to the NMS when the ATN equipment is faulty. The NMS uses the management informationbase (MIB) to identify and manage devices. The SNMP versions include SNMPv1, SNMPv2c,and SNMPv3, which are all supported by the ATN 905.The Link Layer Discovery Protocol (LLDP) is a Layer 2 discovery protocol defined in 802.1ab.When the ATN and its neighbors are all enabled with LLDP, the ATN notifies the neighbors ofits status and obtains the status of the neighbors through LLDP packets. The NMS then can getinformation about Layer 2 connection of the ATN. In this manner, the NMS can analyze thenetwork topology.


Table 3-2 SNMP parametersParameter Value Descriptionsnmp-agent - Enables the SNMP agent

function. By default, theSNMP agent function isdisabled.

snmp-agent sys-infoversion

all Configures the system toadopt all the SNMP versions,namely, SNMPv1,SNMPv2c, and SNMPv3.

snmp-agent mib-viewincluded iso-view

iso Includes the iso subtree in theSNMP MIB view.

snmp-agentcommunity readcipher

Huawei123!mib-view iso-view

Sets a read community name.The NMS can access a deviceonly when the communityname set on the NMS is thesame as that set on the device.

snmp-agentcommunity writecipher

Huawei@123mib-view iso-view

Sets a write communityname. The NMS can access adevice only when thecommunity name set on theNMS is the same as that seton the device.

snmp-agent trapenable

- Enables all traps on a device.



38

Parameter Value Descriptionsnmp-agent trapsource

LoopBack0 Configures the LoopBack0interface as the sourceinterface that sends trapmessages.

snmp-agent target-host trap

address udp-domain20.20.20.20params securitynameHuawei@123 v2c private-netmanager ext-vb

Allows the SNMP agent tosend SNMP trap messages tothe Huawei NMS at20.20.20.20.

snmp-agent trapenable feature-namelldp

- Enables the LLDP trapfunction.

snmp-agent extenderror-code

enable Enables the extended errorcode function.

lldp enable - Enables the LLDP function.

Application ProcessPerform the following configurations on all ATN devices:snmp-agentsnmp-agent sys-info version all //Enable SNMP of all versions for the system.snmp-agent mib-view included iso-view iso //Include the iso subtree SNMP MIB view.snmp-agent community read cipher Huawei123! mib-view iso-viewsnmp-agent community write cipher Huawei@123 mib-view iso-view //Set the read and write permissions for the write attributes. When the read entity name and write entity name are the same, the write attribute command will override the read attribute command.snmp-agent trap enablesnmp-agent target-host trap address udp-domain 20.20.20.20 params securityname Huawei@123 v2c private-netmanager ext-vb //When the management plane is deployed on public network routes, SNMP trap messages can be sent to the U2000 at management IP address 20.20.20.20 using entity name Huawei@123. If an NMS provided by Huawei is used, configure private-netmanager and ext-vb.snmp-agent trap source LoopBack0 //Set the source interface for trap messages.snmp-agent trap enable feature-name lldpsnmp-agent extend error-code enablelldp enable

3.4 Deploying the Management PlaneThe management plane is an exclusive logical channel that is used to transmit managementpackets between NEs on an ATN network. Logical channels of the management plane and otherplanes, such as the service plane, are separated, so devices can still be managed when the otherplanes become abnormal.



39

3.4.1 Configuration RoadmapThis topic describes the configuration roadmap for the management plane.Traditional management and service packets are closely coupled, making equipmentmanagement more and more complex and costly. Therefore, it is more and more important toseparate the management and service planes. A user operates and manages devices using themanagement plane and deploys services using other planes, such as the service plane. That is,the logical channels of the management plane and other planes are separated. When themanagement plane becomes abnormal, other planes can still be used; when other planes becomeabnormal, devices can still be managed.The configuration roadmap is as follows:l Establish a management plane between the ATN 905 and the CSG based on public network

static routes.

3.4.2 Data PlanningThis topic describes data planning for the management plane configuration.

Data PlanningNOTE

Set these parameters based on the actual network conditions, such as network size and topology. Thefollowing recommended values and precautions in this example are for reference only.


Macro Cell

RNC/SGW

IPRAN GE0/2/0

GE0/2/0GE0/2/1.1 dot1q 1192.168.1.9/30

GE0/2/1.1 dot1q 1 192.168.1.10/30

GE0/2/0.1 dot1q 1 192.168.1.21/30

GE0/2/0.1 dot1q 1 192.168.1.22/30

Loopback0128.4.11.11/32

Loopback0128.4.12.12/32 Loopback0

128.4.13.13/32

Table 3-3 Interface planning tableNE Name Interface IP Address VPNATN905-SmallCellSiteA-001

Loopback0 128.4.11.11 32 -GigabitEthernet0/2/1.1vlan-type dot1q 1

192.168.1.9 30 -



40

NE Name Interface IP Address VPNATN905-SmallCellSiteB-002


192.168.1.21 30 -

GigabitEthernet0/2/1.1vlan-type dot1q 1

192.168.1.10 30 -

ATN910-MacroCellSite-003


192.168.1.22 30 -

3.4.3 Configuring the Management PlaneThis topic describes how to configure the management plane.

Configuring ATN905-SmallCellSiteA-001interface GigabitEthernet0/2/1.1 description NNI vlan-type dot1q 1 ip address 192.168.1.9 30

Configuring ATN905-SmallCellSiteB-002interface GigabitEthernet0/2/0.1 description ToNext905 vlan-type dot1q 1 ip address 192.168.1.10 30interface GigabitEthernet0/2/1.1 description NNI vlan-type dot1q 1 ip address 192.168.1.21 30

Configuring ATN910-MacroCellSite-003interface GigabitEthernet0/2/0.1 description NNI vlan-type dot1q 1 ip address 192.168.1.22 30

3.5 Deploying VRF Lite ServicesThis topic describes how to deploy VRF Lite services.



41

3.5.1 Configuration RoadmapThis topic describes the configuration roadmap for local VPN routing and forwarding (VRF)instances.Usually multiple users share a device. When a user wants to keep the internal network topologyand address allocation plan from other users, network addresses and routing information ofdifferent users need to be separated to ensure security. Logically, each PE can be divided intomultiple virtual routers, that is, multiple VRF instances. Each VRF instance corresponds to aVPN and has its own routing table, forwarding table, and corresponding interfaces. In thismanner, a PE shared by multiple VPNs is simulated as multiple exclusive PEs and the routinginformation exchanged between the PE and CE is related to a specific VPN. In this manner,VPN routes are separated.Although VRF instances are usually used with Multiprotocol Label Switching (MPLS), VRFinstances can be used alone. VRF Lite is a typical example. VRF Lite indicates that VRFinstances are supported on the CE. The following provides an example:Three departments of an enterprise branch are required to be isolated from each other and eachdepartment is connected to the PE through a CE. That is, the enterprise branch requires 3 egressrouters and 3 links leading to the PE, and the PE needs to provide 3 interfaces for the enterprisebranch. In this case, port and link resources are wasted and costs increase. To resolve thisproblem, VRF Lite is introduced. That is, VRF instances are configured on the CE. The followingfigure shows the networking mode. The enterprise branch needs only 1 CE to connect to the PE,VRF instances are configured on the CE, and the CE interfaces for the 3 departments are boundto VRF instances. In addition, the CE connects to the PE through only 1 physical link andsubinterfaces of the CE interface are bound to VRF instances. In this manner, correspondingVRF instances are logically connected on the CE and PE, so the PE and CE can run a routingprotocol in each VRF instance to exchange VPN routes.

Figure 3-11 L3VPN configuration roadmap

VRF2

VRF2

CSG

Macro Cell

RNC

IPRANATN 905ATN 905

VRF1

VRF1

VRF1 service flowDot1q sub-interfaceMain interface

VRF2 service flow

The preceding figure shows how to configure VRF instances. The configuration roadmap is asfollows:l Use different VPNs to carry data flows of different users and bind AC interfaces on the

ATN 905 to VRF instances.



42

NOTE

1. When services need to be isolated at station access device

atn 905 v200r002c01 configuration guide 03(cli)

Documents

huawei trademarks

huawei proprietary

plaintext mode

documentpurposethis

huawei industrial basebantian

insecure storage mode

different scenarios

low security level