MAX204 Student Guide v4 (1) .0

MAX 204 - Network Configuration,
Operations, and Maintenance
Motorola, Inc. All Rights Reserved
MAX204 Network Configuration, Operations and Maintenance
MAX204SGV4.0
MAX 204 Network Configuration, Operations, and Maintenance
Course Information
Course Number: MAX204
Course Name: Network Configuration, Operations and Maintenance
Revision Date: July 16, 2007
Version Number: 4.0
Prerequisites
The following are prerequisites for this course:
MAX101 WiMAX Overview
MAX102 WiMAX Technical Overview
Disclaimer
While reasonable efforts have been made to assure the accuracy of this document, this document may
contain some technical or typographical errors or omissions. Motorola, Inc. and its subsidiaries and
affiliates disclaim responsibility for any labor, materials, or costs incurred by any person or party as a result
of using this document. Motorola, Inc., and any of its subsidiaries and affiliates shall not be liable for any
damages (including, but not limited to, consequential, indirect, incidental, or special damages or loss of
profits or data) even if they were foreseeable and Motorola has been informed of their potential occurrence,
arising out of in connection with this document or its use. Motorola, Inc. reserves the right to make changes
without notice to any products or services described herein and reserves the right to make changes from
time-to-time in content of this document and substitute the new document thereof, with no obligation to notify
any person or party of such changes or substitutions.
MOTOROLA and the Stylized M logo are registered in the U.S. Patent and Trademark Office. Sun, Solaris,
and Java are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and/or other
countries. Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation
in the United States and/or other countries. All other product or service names are the property of their
respective owners.
Copyright Motorola, Inc. 2004-2005
MAX204SGV4.0
Table of Contents
Table of Contents............................................................................................................................................................... 4
Course Introduction ......................................................................................................................................................... 14
Course Objectives ............................................................................................................................................................ 14
Lesson 1 ........................................................................................................................................................................... 16
WiMAX Network Overview............................................................................................................................................ 16
Networks...................................................................................................................................................................... 18
Network Types......................................................................................................................................................... 19
Wireless Networks ................................................................................................................................................... 21
WiMAX Defined ......................................................................................................................................................... 22
Standards Organizations .......................................................................................................................................... 24
WiMAX Defines PHY and MAC ................................................................................................................................ 26
WiMAX Specifics........................................................................................................................................................ 28
Network Characteristics............................................................................................................................................... 31
Radio Network............................................................................................................................................................. 32
WiMAX Physical Layer .............................................................................................................................................. 34
WiMAX MAC Layer................................................................................................................................................... 46
Network Entry and Connections .................................................................................................................................. 49
Mobile IP ..................................................................................................................................................................... 52
Lesson Summary.......................................................................................................................................................... 58
Lesson 2 ........................................................................................................................................................................... 61
WiMAX Networking ................................................................................................................................................... 61
Authentication.......................................................................................................................................................... 63
Authorization ........................................................................................................................................................... 64
Accounting............................................................................................................................................................... 66
Authorization Between ASNs.................................................................................................................................. 67
Element Management System (EMS)...................................................................................................................... 69
Access Point (AP) .................................................................................................................................................... 70
Carrier Access Point Controller (CAPC) ................................................................................................................. 71
Network Time Protocol (NTP) ................................................................................................................................ 73
WiMAX NTP........................................................................................................................................................... 73
Home Agent............................................................................................................................................................. 76
Foreign Agent .......................................................................................................................................................... 76
Agent Discovery Process ......................................................................................................................................... 76
Call Routing............................................................................................................................................................. 77
Voice Application Server......................................................................................................................................... 79
Asterisk Private Branch Exchange........................................................................................................................... 80
End of Lesson Exercise............................................................................................................................................ 82
Lesson 3 ........................................................................................................................................................................... 83
WiMAX Call Processes .............................................................................................................................................. 83
A General Overview of the End to End Call Setup.................................................................................................. 86
A General Overview of the End to End Call Setup continued. ............................................................................. 87
WiMAX Subscriber Terminal Network Entry Process............................................................................................ 88
WiMAX Subscriber Terminal Network Entry Process continued ........................................................................ 89
Scan and Synchronize to Downlink Channel........................................................................................................... 90
Scan and Synchronize to Downlink Channel continued ....................................................................................... 91
Initial Ranging ......................................................................................................................................................... 92
Initial Ranging Continued..................................................................................................................................... 93
Negotiate Basic Capabilities .................................................................................................................................... 94
Negotiate Basic Capabilities continued................................................................................................................. 95
Authorization and Key Exchange ............................................................................................................................ 96
Authorization and Key Exchange continued......................................................................................................... 97
Registration.............................................................................................................................................................. 98
Registration continued .......................................................................................................................................... 99
Connections and Addressing.................................................................................................................................. 100
CID Allocation....................................................................................................................................................... 100
Connections and Addressing.................................................................................................................................. 101
MAX204SGV4.0
Service Flows and Service Flow Identifiers........................................................................................................... 102

Service Flows and Service Flow Identifiers........................................................................................................... 103
Dynamic Service Flows ......................................................................................................................................... 104
Dynamic Service Flows continued...................................................................................................................... 105
ST Initiated Dynamic Service Flow Creation ........................................................................................................ 106
ST Initiated Dynamic Service Flow Creation continued..................................................................................... 107
AP Initiated Dynamic Service Flow Creation........................................................................................................ 108
AP Dynamic Service Flow Creation continued .................................................................................................. 109
Dynamic Service Change....................................................................................................................................... 110
ST Initiated Dynamic Service Change................................................................................................................... 110
ST Initiated Dynamic Service Change continued ............................................................................................... 111
AP Initiated Dynamic Service Change .................................................................................................................. 112
AP Initiated Dynamic Service Change continued............................................................................................... 113
IP Connectivity/Address Assignment .................................................................................................................... 114
DHCP Procedure for Fixed/Nomadic Clients ........................................................................................................ 114
DHCP Procedure for Fixed/Nomadic Clients continued .................................................................................... 115
Mobile IP Terminology Review............................................................................................................................. 116
Mobile IP Terminology Review continued......................................................................................................... 117
New Mobile IP Terminology ................................................................................................................................. 118
New Mobile IP Terminology continued ............................................................................................................. 119
DHCP Address Assignment and Proxy Mobile IP (PMIP).................................................................................... 120
DHCP Address Assignment and Proxy Mobile IP (PMIP) continued ................................................................ 121
WiMAX Mobility ...................................................................................................................................................... 124
WiMAX Mobility (Access) Modes........................................................................................................................ 124
WiMAX Mobility Modes continued................................................................................................................... 125
Active WiMAX Mobility ................................................................................................................................... 126
Active WiMAX Mobility continued................................................................................................................ 127
Idle WiMAX Mobility........................................................................................................................................ 128
Idle WiMAX Mobility continued...................................................................................................................... 129
WiMAX Lease Processes, Handoffs and Ownership............................................................................................. 130
WiMAX Leases continued.................................................................................................................................. 131
Side-haul traffic and QoS in Call Management ..................................................................................................... 132
Side-haul traffic and QOS in Call Management .................................................................................................... 133
Leases Idle Mode Entry ST Initiated .................................................................................................................. 134
Idle Mode Entry ST Initiated .............................................................................................................................. 135
Intra-CAPC, Intra-Router/FA Handover................................................................................................................ 136
Intra-CAPC, Intra-Router/FA Handover continued ............................................................................................ 140
Student Activity - Call Setup Processes................................................................................................................. 144
Student Activity Call Flow Processes Team 1 ................................................................................................. 145
Re-entry from Idle Mode - Outbound Data (serving AP holds lease).................................................................... 145
Re-entry from Idle Mode - Outbound Data (serving AP holds lease).................................................................... 146
Re-entry from Idle Mode - Outbound Data (non-serving AP holds lease) ............................................................ 147
Re-entry from Idle Mode - Outbound Data (non-serving AP holds lease) continued......................................... 148
Re-entry from Idle Mode - Outbound Data (PC holds lease)................................................................................. 149
Re-entry from Idle Mode - Outbound Data (PC holds lease) continued ............................................................. 150
Re-entry from Idle Mode - Outbound Data (PC holds lease) continued ............................................................. 151
Inter-CAPC, Inter-Router/FA Handover................................................................................................................ 152
Inter-CAPC, Inter-Router/FA Handover continued ............................................................................................ 153
MAX204SGV4.0

Inter-CAPC, Inter-Router/FA Handover continued ............................................................................................. 155
Re-entry from Idle Mode Inbound Data (Serving AP)........................................................................................ 158
Re-entry from Idle Mode Inbound Data (Serving AP) continued .................................................................... 159
Re-entry from Idle Mode Inbound Data (non-Serving AP) ................................................................................ 160
Re-entry from Idle Mode Inbound Data (non-Serving AP) continued............................................................. 161
Inter-Paging Group Mobility in Idle Mode ............................................................................................................ 162
Inter-Paging Group Mobility in Idle Mode continued ........................................................................................ 163
Trouble Shooting Considerations for Call Setup ................................................................................................... 164
Trouble Shooting Considerations continued ........................................................................................................ 165
Student Activity - Trouble Shooting Considerations ............................................................................................. 169
Student Activity - Trouble Shooting Considerations continued........................................................................... 170
Types of Mobility Review for Troubleshooting Considerations......................................................................... 171
Idle WiMAX Mobility........................................................................................................................................ 171
Active WiMAX Mobility ................................................................................................................................... 171
Types of Mobility Review for Troubleshooting Considerations......................................................................... 172
Mobility Trouble Shooting Considerations............................................................................................................ 173
Test Equipment for Trouble Shooting.................................................................................................................... 174
Test Equipment for Trouble Shooting continued ................................................................................................ 175
Analysing Protocol Traces ..................................................................................................................................... 176
Analysing Protocol Traces - continued .................................................................................................................. 177
Analysing Protocol Traces - continued .................................................................................................................. 178
Sample DNS Look-Up trace file ............................................................................................................................ 179
Sample DHCP Address Assignment trace file....................................................................................................... 180
User Registration Traces........................................................................................................................................ 181
Analysing Protocol Traces ..................................................................................................................................... 182
Student Activity - Call Process Troubleshooting................................................................................................... 183
Student Activity Troubleshooting scenarios Team 1 ....................................................................................... 184
MAX204SGV4.0

Lesson Summary.................................................................................................................................................... 205
Lesson 4 ......................................................................................................................................................................... 207
EMS Overview .............................................................................................................................................................. 207
FCAPS ................................................................................................................................................................... 210
Hardware Requirements......................................................................................................................................... 212
Software Requirements .......................................................................................................................................... 212
System Capabilities................................................................................................................................................ 213
EMS Platform Components ................................................................................................................................... 213
EMS Software Components................................................................................................................................... 215
Element Management System................................................................................................................................ 218
EMS Site Administration ....................................................................................................................................... 218
EMS Account Management ................................................................................................................................... 218
Site Administration Functions ............................................................................................................................... 220
EMS Operations Management ............................................................................................................................... 222
EMS Backup / Restore........................................................................................................................................... 224
Restore Backup ...................................................................................................................................................... 228
EMS HTTPS Management .................................................................................................................................... 230
High Level Configuration Steps ............................................................................................................................ 234
EMS Properties ...................................................................................................................................................... 244
Add WiMAX System Node ................................................................................................................................... 246
Configure Global WiMAX settings ....................................................................................................................... 248
EMS Node Properties & Node Configuration Rules........................................................................................... 250
WiMAX Network Element Configuration Dependencies...................................................................................... 253
CAPC Node Configuration .................................................................................................................................... 254
General Node Properties ........................................................................................................................................ 256
CAPC Bootstrapping ............................................................................................................................................. 258
Payload Set/Module - Node Properties .................................................................................................................. 260
Validation............................................................................................................................................................... 262
CAPC Download ................................................................................................................................................... 264
Access Point Configuration ................................................................................................................................... 266
AP Bootstrapping................................................................................................................................................... 268
AP Sector Configuration........................................................................................................................................ 268
AP Configuration Node Configuration ............................................................................................................... 272
AP Download......................................................................................................................................................... 274
Software Mismatch ................................................................................................................................................ 276
CPE Policy Configuration...................................................................................................................................... 280
CPE Auto Discovery.............................................................................................................................................. 282
Student Activity ............................................................................................................................................................. 299
EMS Operations and Maintenance ................................................................................................................................ 299
EMS Network Topology........................................................................................................................................ 302
Node Functions ...................................................................................................................................................... 304
Database Changes .................................................................................................................................................. 306
Performance Management ..................................................................................................................................... 310
Statistic Collection Configuration.......................................................................................................................... 310
Lesson 5 ......................................................................................................................................................................... 327
CAPC Hardware ............................................................................................................................................................ 327
Functions of the CAPC .......................................................................................................................................... 330
CAPC Hardware .................................................................................................................................................... 332
CAPC Chassis........................................................................................................................................................ 332
ATCA-F101 Blades (System Controller Blades)................................................................................................... 334
Shelf Management Alarm Module (SAM)............................................................................................................. 336
ATCA-7221 Blades (pCAPC Blades).................................................................................................................... 338
RTM-ACTA-F101 Rear Transition Modules (RTM) ............................................................................................ 340
ACC-ARTM-7221/SCSI Rear Transition Modules (RTM)................................................................................... 342
Power Entry Modules (PEM)................................................................................................................................. 344
Fan Tray Modules .................................................................................................................................................. 344
CAPC Hardware Redundancy ............................................................................................................................... 346
MAX204SGV4.0
Power Distribution Redundancy Model................................................................................................................. 348

CAPC Capacities ................................................................................................................................................... 349
Software Functions / Interfaces.............................................................................................................................. 350
CAPC Transport Communications ........................................................................................................................ 352
CAPC Transport Communications ........................................................................................................................ 353
CAPC Master Bootstrap Procedure ....................................................................................................................... 354
CAPC Software Download .................................................................................................................................... 354
Lesson 6 ......................................................................................................................................................................... 359
CAPC Commissioning, Bootstrapping, and Troubleshooting ....................................................................................... 359
Introduction............................................................................................................................................................ 362
CAPC Configurations ............................................................................................................................................ 363
Verifying the Front Blade Placement..................................................................................................................... 364
Verifying the Rear Transition Modules (RTM) placement.................................................................................... 366
Blade Insertion & Extraction ................................................................................................................................. 368
CAPC Power on Sequence..................................................................................................................................... 371
WiMAX Network Element Configuration Dependencies...................................................................................... 372
CAPC Commissioning and Bootstrapping............................................................................................................. 374
Assumptions and Dependencies............................................................................................................................. 374
Procedural Work Flow for Commissioning and Bootstrapping ............................................................................. 375
CAPC Bootstrapping Set Up.................................................................................................................................. 377
Adding the CAPC .................................................................................................................................................. 380
General Node Properties ........................................................................................................................................ 381
Verification of the Bootstrapping procedure.......................................................................................................... 388
CAPC Payload Card Discovery Procedure ............................................................................................................ 390
Payload Set Node Properties.................................................................................................................................. 392
Payload Set Node Configuration............................................................................................................................ 394
Payload Module Node Properties........................................................................................................................... 396
CAPC Paging Group Properties............................................................................................................................. 398
Paging Group Configuration.................................................................................................................................. 400
Payload Set Node and Payload Module Configuration Download ........................................................................ 402
CAPC Node Configuration .................................................................................................................................... 402
Validation............................................................................................................................................................... 402
CAPC Configuration Download ............................................................................................................................ 404
CAPC Software Location....................................................................................................................................... 406
CAPC Software Verification ................................................................................................................................. 406
CAPC Software Upgrade Procedure...................................................................................................................... 408
Download............................................................................................................................................................... 410
Prepare ................................................................................................................................................................... 411
Activate.................................................................................................................................................................. 412
Configuration Only download ............................................................................................................................... 415
Lesson 7 ......................................................................................................................................................................... 419
CAPC Local Maintenance Terminal.............................................................................................................................. 419
LMT User Accounts .............................................................................................................................................. 423
LMT Login ............................................................................................................................................................ 424
CAPC LMT Welcome Screen................................................................................................................................ 426
Activity Logging.................................................................................................................................................... 427
Alarm Logs ............................................................................................................................................................ 428
Configuration Tools ............................................................................................................................................... 430
Dynamic Logging .................................................................................................................................................. 434
Configuration Utilities ........................................................................................................................................... 436
Event Reports......................................................................................................................................................... 437
Health Check.......................................................................................................................................................... 438
IP Utility Tools ...................................................................................................................................................... 440
Link Management .................................................................................................................................................. 442
Message Tracing .................................................................................................................................................... 444
Security .................................................................................................................................................................. 446
Platform Logs ........................................................................................................................................................ 448
MAX204SGV4.0
Session Management ............................................................................................................................................. 450

Snap Tool............................................................................................................................................................... 452
State Management.................................................................................................................................................. 454
Statistics ................................................................................................................................................................. 456
User Management .................................................................................................................................................. 459
Lesson 8 ......................................................................................................................................................................... 463
Access Point Hardware .................................................................................................................................................. 463
Diversity Access Point (DAP) Hardware............................................................................................................... 466
DAP Hardware Interconnection............................................................................................................................. 468
RF Head ................................................................................................................................................................. 470
BCU Cabinet.......................................................................................................................................................... 472
BCU Alarm Card ................................................................................................................................................... 474
BCU Site Controller Card ...................................................................................................................................... 478
BCU Modem Card ................................................................................................................................................. 480
BCU Circuit Breaker Card..................................................................................................................................... 482
BCU Power Supply Unit........................................................................................................................................ 483
Global Positioning System (GPS).......................................................................................................................... 484
Ancillary units........................................................................................................................................................ 485
Power Distribution Module.................................................................................................................................... 486
Lesson 9 ......................................................................................................................................................................... 489
AP Commissioning, Bootstrapping and Software Upgrade .................................................................................................... 489
Objectives .................................................................................................................................................................. 491
Introduction............................................................................................................................................................ 492
Access Point Commissioning................................................................................................................................. 496
Access Point Commissioning Procedure ............................................................................................................... 496
Installing Site Controller Software......................................................................................................................... 497
Pre-Commissioning Tools...................................................................................................................................... 500
Access Point Site Calibration (apcalib).................................................................................................................. 500
Access Point Diagnostics (apdiag)......................................................................................................................... 506
Site Commissioning ............................................................................................................................................... 510
Installation and Network Connection Verification ................................................................................................ 513
Access Point Bootstrapping ................................................................................................................................... 516
Adding the Access Point / Sector........................................................................................................................... 518
Lesson Summary........................................................................................................................................................ 528
Hands-On Activity ..................................................................................................................................................... 530
Hands-On Activity ..................................................................................................................................................... 531
Lesson 10 ....................................................................................................................................................................... 533
AP Local Maintenance Terminal ................................................................................................................................... 533
Introduction............................................................................................................................................................ 535
Adding LMT Users ................................................................................................................................................ 536
Accessing the Access point LMT .......................................................................................................................... 538
Reset Box............................................................................................................................................................... 541
Reset Modem ......................................................................................................................................................... 542
View Running Configuration................................................................................................................................. 543
Deploy New Configuration.................................................................................................................................... 544
View IP Network Configuration ............................................................................................................................ 545
Modify IP Network Configuration......................................................................................................................... 546
View Ethernet Network Configuration .................................................................................................................. 547
Modify Ethernet Network Configuration............................................................................................................... 548
View Node and FRU States ................................................................................................................................... 549
View Active Interface Info .................................................................................................................................... 550
View Internal Device States................................................................................................................................... 551
View State of Links to Other NEs.......................................................................................................................... 552
View Connected MSs ............................................................................................................................................ 554
Run Ping Command............................................................................................................................................... 555
Run Traceroute Command ..................................................................................................................................... 556
Run Netstat Command ........................................................................................................................................... 557
Run Netstat Command ........................................................................................................................................... 558
View Test Mode Configuration ............................................................................................................................. 560
Modify Test Mode Configuration .......................................................................................................................... 561
MAX204SGV4.0
10
View Daily Log File .............................................................................................................................................. 562

View Current Security Configuration .................................................................................................................... 563
Deploy New Security Configuration...................................................................................................................... 564
Start Bootstrap Procedure ...................................................................................................................................... 565
Add a New LMT User ........................................................................................................................................... 566
Remove an LMT User Account ............................................................................................................................. 567
Lesson 11 ....................................................................................................................................................................... 571
AP Troubleshooting....................................................................................................................................................... 571
Objectives .............................................................................................................................................................. 571
Tasks ...................................................................................................................................................................... 571
Introduction............................................................................................................................................................ 571
Identifying AP Problems........................................................................................................................................ 572
On-site Observation ............................................................................................................................................... 572
Element Management System - EMS .................................................................................................................... 573
Local Maintenance Terminal LMT..................................................................................................................... 580
Correcting On-site Problems.................................................................................................................................. 581
Hardware Faults ..................................................................................................................................................... 581
BCU Cabinet.......................................................................................................................................................... 581
BCU Cabinet Cards................................................................................................................................................ 584
RF Head ................................................................................................................................................................. 586
Link Problems........................................................................................................................................................ 588
Other AP Alarms.................................................................................................................................................... 589
Customer Defined Alarms ..................................................................................................................................... 589
Ground-based Access Point (GAP)........................................................................................................................ 590
Lesson Summary.................................................................................................................................................... 592
Lesson 12 ....................................................................................................................................................................... 593
WiMAX Network .......................................................................................................................................................... 593
Troubleshooting ............................................................................................................................................................. 593
Appendix A.................................................................................................................................................................... 597
My Network Support ..................................................................................................................................................... 597
MAX204SGV4.0
11
MAX204SGV4.0
12
How to Use this Guide

This guide is intended to supplement instructor-led training for the WiMAX system. It
is meant for you to use as a learning guide during class.
About this Guide

Each module/lesson contains specific objectives that are accomplished through
lecture, activities, and hands-on laboratory exercises. The lessons are broken down
to specific topics and sub-topics.
Organization of this Guide

Each module includes an overview and the objective of the module. It also provides
a list of lessons incorporated in the module.
Each lesson includes a brief introduction to the lesson, along with the objectives of
that lesson. In addition, each lesson includes the following information, when
applicable:
Topics relating to each lesson objective
Step-by-step process explanations
Topic exercises
Lesson exercises
Lesson review
This guide also includes a final course exercise, course summary, and an appendix
with reference information.
Conventions Used in this Guide

Throughout this guide, you will find icons representing various types of information.
These icons serve as reminders of their associated text.
Indicates an Activity where
you can test your skills.
Indicates a Hint such as a

tip, shortcut, or additional
way to do something.
Indicates a Note or additional

information that might be
helpful to you.
Indicates a list of
References where you can
go for additional information
about a topic.
MAX204SGV4.0
13
Agenda
Agenda Item
Length
Day 1
Introductions
30 minutes
Lesson 1 WiMAX Overview
2 hours
Lesson 2 WiMAX Networking
1 hour
Lesson 3 WiMAX Call Processes
3 hours
Day 2
Lesson 4 EMS Overview
3 hours
Lesson 5 CAPC Hardware
1 hour
Lesson 6 CAPC Installation & Troubleshooting
3 hours
Day 3
Lesson 7 CAPC LMT
3 hours
Lesson 8 AP Hardware
1 hour
Lesson 9 AP Bootstrap, Commissioning and Software Upgrade
3 hours
Day 4
Lesson 10 AP LMT
3 hours
Lesson 11 AP Troubleshooting
3 hours
Day 5
Lesson 12 WiMAX Network Troubleshooting
4 hours
Final Test
1 hour
Course Wrap Up
30 minutes
TOTAL COURSE TIME IN DAYS
5 days
MAX204SGV4.0
14
Course Introduction
WiMAX Network Configuration, Operations and Maintenance is designed to provide
Central Office Technicians, Network Engineers and the Motorola Support Team with
the necessary knowledge and skills needed to install, operate, maintain and
troubleshoot a WiMAX system. This course includes hands-on labs to help students
to master course objectives.
Course Objectives
Upon completion of this course, you should be able to:
1. Define WiMAX
2. Explain the purpose of WiMAX Access Network Elements
3. Describe the function of the devices found in the WiMAX Core Network
4. Illustrate the WiMAX Network Entry process
5. Illustrate the WiMAX Handover process
6. Describe the function and makeup of the Carrier Access Point Controller
(CAPC)
7. State CAPC the commissioning, bootstrapping and software upgrade
procedures
8. Demonstrate proper CAPC troubleshooting procedures
9. Describe the function and makeup of the Access Point (AP)
10. State AP the commissioning, bootstrapping and software upgrade procedures
11. Demonstrate proper AP troubleshooting procedures
12. Use the CAPC and AP Local Management Terminal to maintain a WiMAX
system
13. Use the Element Management System to provision and maintain a WiMAX
system
MAX204SGV4.0
15
MAX204SGV4.0
16
Lesson 1
WiMAX Network Overview
MAX204SGV4.0
17
Objectives
At the completion of this lesson, you should be able to:
1. Define WiMAX
2. Explain what WiMAX offers
3. Identify the standards and groups Define the purpose of IEEE 802.X
Standards
4. Describe the purpose of the OSI Reference Model
5. Define LANs, MANs, PANs, and WANs
6. Explain WiMAX (IEEE 802.16) Physical (PHY) and MAC layers.
7. Explain IEEE 802.3 (Ethernet)
8. Define Ethernet networks
9. Explain the purpose of typical network elements
By the end of this lesson you will have gained the skills needed to perform the
following tasks:
1.
2.
3.
4.
5.
Understand the purpose of each WiMAX network element

Understand the relationships between WiMAX network elements
Understand general WiMAX parameters
Place a VoIP call
Establish a Data connection
MAX204SGV4.0
18
Networks
Networking has been around for a very long time. As technology advanced, so did
networking. In the 1800s data networking tied distant places together. Later as
computers began to emerge they were connected together to allow users to
communicate and to share data. In the 1970s local area networks began slowly
take shape. This allowed fixed locations to connect to a network. In the late 1990;
people began to look for ways to access data networks over a wireless carrier. The
IEEE standards organization took this opportunity to extend the 802 standard to
support wireless connectivity.
Data Networking
Peer-to-Peer
Really Old
802.3 Ethernet Network
Network
Network
802.X Ethernet Network
MAX204SGV4.0
19
Network Types
As networks began to expand and develop, they were classified by the type of area
for which they provided connectivity.
Network Types
Wide Area Network
Metropolitan Area Network
A network that covers great distances

Not part of IEEE 802 standard
A network that covers a large geographic area
Local Area Network
Personal Area Network
A network that covers a limited geographic area
A network that covers a very small area
Network Types
MAX204SGV4.0
20
Wide Area Network
Definition
Wide Area Network (WAN)
A computer network that spans a

relatively large geographic area.
Metropolitan Area Network (MAN)
A data network designed for a

town or city. Typically these are
larger that LANs but smaller than
WANs.
Local Area Network (LAN)
A computer network that covers

an immediate area. These may
include offices and homes.
Personal Area Network (PAN)
A very small computer network

designed for use by a single
person.
MAX204SGV4.0
21
Wireless Networks
An extension of computer networking was the addition of wireless connections.
Wireless networks allowed computers and peripherals to be connected using radio
frequencies. The IEEE organization is a standards-making body that added wireless
to the IEEE 802 standards. Working groups within IEEE focused on building
standards based on the LAN/MAN/Pan functionality.
And then there is Wireless

Standard
Type of Network
Industry Group
Wireless LAN
Wireless PAN
Wireless MAN
Wireless Networks
MAX204SGV4.0
22
WiMAX Defined
WiMAX is a Broadband Wireless Access wireless-MAN solution designed to provide a
high speed, high quality connection over a large area. With the introduction of IEEE
802.16e WiMAX will support full mobility enabling subscribers to move from one
coverage zone to another.
WiMAX is a Broadband Wireless Access
Wide Coverage
High Capacity
High Quality
High Speed
Reliability
WiMAX stands for the Worldwide Interoperability for Microwave Access. I guess
adding the x made it sound better than calling it WiMA. However, it is designed to
provide service for the last mile.
WiMAX
Worldwide Interoperability for Microwave Access
Provides the last mile or a Point-To-Point

Wireless Broadband (WiBB) access
MAX204SGV4.0
23
Using research and technologies previously developed, IEEE organized the 802.16
working group. This group defined the parameters (profiles) and combined a
multitude of existing technologies to develop WiMAX.
WiMAX and technology
Use a multitude of technologies

Different applications of the technology
WiMAX is IEEEs standard for its broadband wireless access network. A BWA
should have instantaneous bandwidth greater than 1 MHz and support data rates
faster than 1.5 mega-bits per second. A BWA is similar to broadband wired networks
such as cable modems, and DSL circuits.
WiMAX is a standards based interface that can support a multitude of user types.
What is WiMAX
State of the Art
Broadband Wireless Access network
802.16 defines IEEEs BWA standard
High-performing
standards based solution
Supporting
Fixed
Nomadic
mobile subscribers
Both licenses and unlicensed frequency
MAX204SGV4.0
24
Standards Organizations
WiMAX is a very versatile standard that can be configured in hundreds of different
ways, each following the standard to the letter. Problems could occur when different
companies wanted to use equipment from multiple manufacturers. Services
providers may not be able to ensure compatibility and interoperability of the
equipment. To solve this problem, manufacturers and service providers built an
organization to lead the deployment effort for WiMAX worldwide. This organization is
the WiMAX Forum. The WiMAX Forum certifies the compatibility and interoperability
of BWA products using the IEEE 802.16 standard. The Forum has developed
several profiles that define specific configurations and capabilities that equipment
manufacturers must meet in order to obtain WiMAX Forum Certification.
Standards and Organization

Develop standards for multiple technologies
Produced the 802 standards
Including the 802.16 (WiMAX) standard
Industry-led organization
Certifies compatibility and interoperability
Develops WiMAX profiles
Standards Based, State-of-the-art solution

Flexible Infrastructure
MAX204SGV4.0
25
Motorola is a member of both the IEEE standards committee and the WiMAX Forum.
As a member of these organizations, Motorola is able to work with service providers
and other companies to leverage the best possible solutions. In addition to acting as
a key member of these teams, we bring years of advanced experience in our
development and deployment of RF technologies.
Driving the standards
Motorola is an active member of

the standards specification
committee
Motorola is a key participant in

the WiMAX Forum
Leveraging our expertise in

multiple technologies
OFDMA (Advanced Modulation)

Smart Antennas
Mobility Management
IP Networking
MAX204SGV4.0
26
WiMAX Defines PHY and MAC

One of the key initiatives of the 802.16 working group was that WiMAX had to provide
interoperability without having to modify other networks and protocols. To do this,
WiMAX followed the International Organization for Standardizations Open System
Interconnect (OSI) reference model.
Using this model each layer has a specific functionality. When an application needs
to send or receive data, it processes the information and sends it down to the next
layer in the stack. The next layer adds to or manipulates the data and sends it down
to the next layer.
OSI Layers Stacks
7 Application
7 Application
6 Presentation
6 Presentation
5 Sessions
5 Sessions
4 Transport
4 Transport
3 Network
3 Network
2 Data Link
2 Data Link
1 Physical
1 Physical
Data networks communicate by stacking different

protocols on top of each other.
According to the standard, each layer is independent of the other layer and can be
interchanged with another protocols or applications designed to work at that layer of
the stack.
MAX204SGV4.0
27
WiMAX defines the two lowest layers of the OSI stack. These layers are the physical
PHY and the data link layer. Actually, the data link layer is divided into two
sub-layers; WiMAX uses one of these sub-layers. This layer is the Media Access
Control layer, MAC.
WiMAX defines
Layer two data layer is divided into two sub layers called MAC and LLC.
Layer 2 uses MAC addresses not IP addresses.
Application
Presentation
Sessions
Transport
Network
Data Link
Physical
IEEE 802.16 / WiMAX

Defined the PHY and MAC
layers for the air interface
MAX204SGV4.0
28
WiMAX Specifics
WiMAX was designed to be deployed as an overlay to existing networks or to operate
separately. Added to existing wireline networks, WiMAX adds full mobility. In areas
with no existing infrastructure, WiMAX is a low-cost solution to provide voice and DSL
quality data to the market. WiMAX is also designed to compliment existing wireless
systems.
Deployments
Wi-Fi Hot spots
DSL
Cable
WiMAX
Adds mobility
for Wireline networks
Cellular Network
WiMAX
New networks
Greenfield
WiMAX
Complements
existing networks
MAX204SGV4.0
29
WiMAX is an all-IP based architecture. This approach provides service providers to

use off the shelf equipment rather than a proprietary solution. It also provides
service providers a network that is easily scalable and is extremely flexible.
Motorolas WiMAX solution is also designed to meet very stringent availability criteria.
99.999% equates to 5 minutes and 15 seconds of downtime per year.
Carrier Class IP Core
IP Network
WiMAX uses an all IP based architecture

Scalable
Flexible
Designed to meet 99.999

availability requirements
WiMAX can support downlink data rates up to 75 Mbps on a single channel.
Network Speeds
Speeds up to 75*
Mbps
* DL data rate up to 75 Mbps is based Per sector with a

20 MHz channel and closer than4 miles from site
MAX204SGV4.0
30
WiMAX can support a number of different types of subscribers for the last-mile of
service. With the acceptance of the 802.16e amendment, WiMAX support full
mobility.
Types of Subscribers
Fixed
A subscriber that is connected to the
network from one physical location
Nomadic
User powers up and connects to network.
To move the subscriber has to reconnect
at new AP
Mobile
Network provides continuous coverage as
the subscriber moves from AP to AP
IEEE 802.16e is a standard and does not identify the types of services that it can
support. Services and data speeds are defined by the service provider. What
WiMAX does is provide the ability to seamlessly offer any type of service over a large
metropolitan area. Typically these services include voice over IP (VoIP), data, and
streaming video.
Types of Services
Network
Video
Voice
Streaming
Data
MAX204SGV4.0
31
Network Characteristics
WiMAX is capable of supporting Point-To-Point (PTP) and Point-to-Multi-Point (PMP)
services. PTP service is usually Line-of-sight (LOS) and PMP is usually
Non-line-of-sight (NLOS). The operating frequency must be considered when
deploying a PMP system.
Types of Systems
Point-To-Point
Point-To-Multipoint
(PTP)
(PMP)
* MESH networks are also defined as part of the IEEE 802.16 standard. (not shown)
IEEE defines two general frequency bands of operation for WiMAX. NLOS operates
from 2 to 11 GHz. Within this operating band, Countries may specifically identify
which portion of the band users occupy. Today, 3.5 GHZ is common in European
Countries, and 2.5/3.5 GHz is common in the United States.
Operating Frequency
RF characteristics play an important part of dividing WiMAX
into two distinct types of systems.
2.5*
3.5*
5.8*
2 11 GHz
Non Line of Sight (NLOS)
10 66 GHz
Line of Sight (LOS)
*Part of the WiMAX Forum Profiles
MAX204SGV4.0
32
Radio Network
WiMAX NLOS systems are deployed in a cellular configuration. Cells can be
Omni-directional or can be divided into sections called sectors. WiMAX supports up
to 4 sectors per site. Using a sectoring technique allows for a gradual growth of the
network as the demand for bandwidth increases.
In order to optimize the efficiency of the network, RF planners reuse the frequency
over and over again. Normally you will see WiMAX systems define their reuse
scheme as 3 numbers. The first number is the number of cells, the second is
number of sectors the cell is divided into, and the last number is the number of RF
carriers.
MAX204SGV4.0
33
Link Budget
Non-Line-of-Sight systems are typically organized into cells. The coverage area of a
cell is determined many factors including the height of the antenna, the terrain, and
radiation pattern. These factors along with transmit power, antenna gain, path loss,
and receiver gain make up the cells link budget.
Cell Site Organization

To support mobility, cells are further organized into paging groups. This allows the
network to efficiently track and page all of the subscribers in the system.
MAX204SGV4.0
34
WiMAX Physical Layer

IEEE 802.16 and WiMAX define the layer 1 and layer 2 air interfaces. The Layer 1
interface provides a high quality RF connection. This dynamic connection uses
multiple technologies to minimize the effects of interference.
MAX204SGV4.0
35
Channel Direction
Each WiMAX channel organizes traffic based on direction. Data traffic from the
access point to the subscriber is sent on the downlink, while traffic from the subscriber
to the access point is called the uplink.
Channel Types
To ensure that WiMAX provided the versatility needed by the service providers, the
system can support either frequency division duplexing or time division duplexing.
Duplexing
Frequency
Division
Duplex
Time
Division
Duplex
Freq 1
Freq 2
Freq 1
WiMAX supports FDD and TDD operations
MAX204SGV4.0
36
Time Division Duplexing

The WiMAX forum has determined that mobile WiMAX will use
time-division-duplexing. Using this scheme, the system will transmit and receive on
the same frequency. The channel will be used as the downlink, then switch to
accepting traffic for the uplink. To ensure uplink and downlink traffic does not
overlap, a small timeframe or gap is established to switch between the two.
DL/UL Percentages
System level provisioning is used to determine Down Link and Up Link allocation.
MAX204SGV4.0
37
Another important feature of WiMAX is its ability to work in different size channels. A
channel is defined by its center frequency along with the bandwidth it occupies.
WiMAX uses a very robust modulation scheme that allows it to effectively operate in
multiple bands. 3.5, 5.0, 7.0, and 10 MHz channels are accepted profiles from the
WiMAX Forum.
MAX204SGV4.0
38
To maximize throughput while minimizing data errors, WiMAX uses and Adaptive
Modulation and error coding scheme. Adaptive modulation and coding allows the
system to adjust the modulation scheme and error correction up or down depending
on the RF conditions being experienced by the subscriber. This technique allows
WiMAX to dynamically adapt to changing RF conditions.
Adaptive Modulation and Coding

FASTEST
64QAM*
FASTER
16QAM
FAST
QPSK
ity
ual
lQ
a
n
Sig
Note * UL - 64QAM is optional
The overall benefit to this approach is that as RF channel conditions improve, the
Modulation scheme can increase while the error correction decreases resulting in a
high data throughput.
MAX204SGV4.0
39
The adaptive modulation techniques use changes in amplitude and phase in order to
transmit multiple data bits. As the RF channel quality improves, WiMAX will adjust
the modulation and the error correction to ensure an error free message.
Modulation
1010
Group of data is multiplexed together

Data is transmitted by changing phase
amplitude or frequency
Data Point
0011
QPSK
16QAM
64QAM
MAX204SGV4.0
40
Modulation schemes are identified by listing the modulation type followed by the
amount of error correction added to the signal.
Modulation Schemes
2/3 of the bits are data

1/3 of the bits are error correction
64QAM 2/3
coding rate
modulation
3/4 of the bits are data

1/4 of the bits are error correction
64QAM 3/4
Error correction is added to ensure the data is recoverable
As the subscriber moves away from the access point, the channel quality will be
continually checked. When required, the system will adjust the modulation and error
correction.
Adaptive Modulation & Code Rate

The BS will adjust the modulation and code
rates based on the the RF channel
conditions
QPSK
16QAM
64QAM
MAX204SGV4.0
41
WiMAX uses OFDMA which is robust enough to minimize the effect of fast fading and
co-channel interference. Compared with similar cellular technologies in use today,
WiMAX can obtain a much larger coverage area while maximizing data throughput.
Orthogonal Frequency Division Multiple Access
OFDMA
Limited distance
Traditional narrowband cellular system
Improves radio link performance
Maximizes distance
resistant to interference
OFDMA system
MAX204SGV4.0
42
ODFMA
Orthogonal Frequency Division Multiplexing and Orthogonal Frequency Division
Multiple Access is a digital encoding technique used by WiMAX to transmit large
amounts of data while minimizing the effects of multipath interference. This
technology divides the data into multiple sub-channels and transmits the
sub-channels all at the same time.
To fit within the different channel sizes, WiMAX implemented a scalable version of
OFDMA.
MAX204SGV4.0
43
Antenna Systems
Another key innovation being deployed with WiMAX is smart antenna technology.
WiMAX uses technology called MIMO, multiple-in Multiple-out. Using advanced
microcontrollers and mathematical algorithms MIMO can improve the overall data
throughput by either improving coverage, capacity or both.
There are two main types of MIMO in use today, they are open-loop MIMO systems
and Closed-loop MIMO systems.
Motorolas WiMAX systems deploy MIMO A and MIMO B using our DAP and GAP
Access Points. Smart Antenna systems are supported with our Smart Antenna
Access Point.
MAX204SGV4.0
44
Open Loop MIMO

MIMO means multiple-input, multiple output. MIMO uses the radio phenomena of
multipath propagation to increase throughput. Peak throughput of a MIMO system
increases proportionally to the number of signal streams transmitted.
Open-loop MIMO systems can be divided into MIMO A and MIMO B systems.
MIMO A systems can improve system coverage, while MIMO B systems increase
system capacity
MAX204SGV4.0
45
Closed Loop MIMO

Closed Loop MIMO systems are usually called Adaptive Antenna Systems. Adaptive
Antenna Systems or Smart Antennas provide additional RF gain while minimizing the
effects of interference. Beam steering changes the radiation pattern of the antenna.
This improves the received signal strength allowing the subscriber to receive a signal
at higher throughput rates, while minimizing errors received.
Adaptive Antenna Systems

Smart Antenna
Uses beam steering

Adaptively steers the beam towards the SS
Minimizes
Bit Errors
Interference
Improves
RF gain
Data throughput
MAX204SGV4.0
46
WiMAX MAC Layer

The Function of the MAC layer is to control access to the Network. This includes
controlling radio resources and access. The MAC layer will also encapsulate and
fragment data to ensure it is delivered efficiently. Another important feature of the
MAC layer is its ability to manage the over the air quality of service. QoS ensures
that bandwidth is allocated to services that are susceptible to latency and jitter before
being allocated to services less susceptible to delay. The MAX Layer supports the
transport on multiple protocols such as ATM and IP. Layer two also has an elaborate
security mechanism in place to ensure services are authorized and protected.
MAX204SGV4.0
47
ODFMA Frame Structure

Shown below is the ODFMA frame structure comprised of a Preamble, and Down Link
and Uplink Sub-frames separated by a Transmit Time Gap.
MAX204SGV4.0
48
Burst Profile
The Downlink Sub-frame contains the Uplink and Downlink maps. During a downlink
sub-frame, every subscriber will listen to the uplink and downlink maps. These maps
identify which burst the subscriber should listen to for downlink data and which burst
the subscriber should operate in for uplink data. In addition to containing uplink and
downlink data assignments, the access point will also inform the subscriber of how
much bandwidth it may used during the uplink sub-frame.
During the initial ranging process subscribers are assigned a Burst Profile. The Burst
Profile defines the modulation scheme and Forward Error Correction to be used. The
Burst Profile assigned is based on QoS and channel conditions and profiles will
change as channel conditions change. Different Uplink and Downlink profiles may be
assigned. Multiple Burst Profiles are transmitted to support multiple subscribers.
MAX204SGV4.0
49
Network Entry and Connections
WiMAX is a connection based system, which means everything communicated

between the subscriber and access point occurs over a known connection. When a
subscriber is turned on, it will go through this process to gain service.
MAX204SGV4.0
50
A single subscriber may have multiple connections. Each connection has a

connection ID, CID. There are two basic categories for connections, they are
management and transport.
MAX204SGV4.0
51
Each connection will be associated with a quality of service (QoS) identifier. QOS
identifiers ensure that data is transmitted in a fashion to ensure real-time services are
transmitted in real-time while other services less susceptible to delay are transmitted
after. Service providers may also uses QOS tags as an additional method to sell
services.
QOS
Flexible resource mechanism

Flexible support of simultaneous IP services
QOS will set the priority of when the connection will be serviced.
rtPS
nrtPS
USG
BE
Real-Time Polling Services
Non-Real-Time Polling Services
Unsolicited Grant Service
Best Effort Service
MAX204SGV4.0
52
Mobile IP
With the addition of 802.16e WiMAX now supports Mobility. Mobility will allow a
subscriber to move between access points, and networks while maintaining its
connections.
A process MS seamlessly migrates from one AP to another

Supports Seamless mobility at vehicular speeds.
Mobility
This signal is
getting pretty bad.
Hey can you take

this guy?
I have resources,
Ill take him!
Serving Cell
Target Cell
MAX204SGV4.0
53
Mobile IP provides secure internet mobility using a connection between the home
agent router and the foreign agent router. This connection is called a tunnel.
AP
binding
Router/Home Agent
SS/MSS/CPE
Router/Foreign Agent
Visitors list
Contains information about the MSS
Tunnel
Mobility Binding Table

Links the home address with the
Temporary Care-of-address (FA)
DATA
MAX204SGV4.0
54
WiMAX Network
This section will introduce you to a generic WiMAX network. It is important to
remember that with the flexibility of WiMAX, this network may take on many different
configurations while still providing a high quality data network.
Access
Service Network
(ASN)
AP
Connectivity
Service Network
(CSN)
Router/FA
MSS/CPE
NTP
AP
EMS
DNS
DHCP
DNS
Server(s)
AP
MSS/CPE
Firewall
(Optional)
CAPC
AP
Router/HA
DHCP
AAA
AAA
VoIP
Server
MSS/CPE
Router/FA
AP
This diagram represents a

Generic WiMAX Network.
AP
MAX204SGV4.0
55
Network Element
(interface)
Name
Definition
ASN
Access Service Network
Provides access layer connectivity and QoS

between the subscribers and the AP.
CSN
Connectivity Service Network
Provides connectivity services. Includes

AAA, DHCP, Security, and Home Agent
routing.
MS/CPE/MSS/Subscriber
This is the customer access device.
IEEE 802.16e
WiMAX Air Interface
Responsible for the PHY and MAC access

over the RF interface to the network.
AP
Access Point
Provides wireless access to the network.

IEEE referrers to APs as Base Stations (BS)
CAPC
Cellular Access Point Controller
Provides management of security and

mobility.
Functionality includes:
Security / Local Key distribution
Paging controller
QoS Policy decision point
MS/CPE access control
Handover decision point
EMS
Element Management System
Provides network management functions for

the APs and CAPCs.
Includes:
Fault Management
Configuration Management
Performance Management
Security Management
MAX204SGV4.0
56
Network Element
Name
Definition
NTP
Network Time Protocol Server
Used to synchronize the time of computer

clients or servers.
DNS
Domain Name Service Server
Stores and associates domain names to IP

addresses.
DHCP
Dynamic Host Configuration

Protocol Server
Provides network computers with IP address

and other network parameters
AAA
Authentication, Authorization,
and Accounting Server
Provides security and provides capability

information to the MSS/CPE.
FA
Foreign Agent
A router that works with the home agent to

deliver IP services to a subscriber on its
network.
HA
Home Agent
A router that ensure connective of the

subscriber to the home network regardless of
the location
MAX204SGV4.0
57
MSS/CPE
MSS/CPE
MSS/CPE
AP
AP
AP
AP
AP
AP
NTP
AAA
DHCP
DHCP
AAA
Firewall Router/HA
(Optional)
DNS
DNS
VoIP
Server
Server(s)
Access
Connectivity
Service Network Service Network
(ASN)
(CSN)
Router/FA
EMS
CAPC
Router/FA
This diagram represents a

Generic WiMAX Network.
MAX204SGV4.0
58
Lesson Summary
In this lesson you learned to:
Define WiMAX
Explain what WiMAX offers
Identify the standards and groups Define the purpose of IEEE 802.X
Standards
Describe the purpose of the OSI Reference Model
Define LANs, MANs, PANs, and WANs
Explain WiMAX (IEEE 802.16) Physical (PHY) and MAC layers.
Explain IEEE 802.3 (Ethernet)
Define Ethernet networks
Explain the purpose of typical network elements
MAX204SGV4.0
59
End of Lesson Exercise

1. Match the terms.
a. WAN
b. MAN
c. LAN
d. PAN
__ A computer network that covers an immediate area. These may include
offices or homes.
__ A data network designed for a town or city.
__ A very small computer network designed for use by a single person
__ A computer network that spans a relatively large geographical area.
2. Match the standard with the network.
a. 802.11
b. 802.15
c. 802.16
__ WPAN
__ WLAM
__ WMAN
3. WiMAX operates in the licensed and unlicensed frequency bands
a. True
b. False.
4. WiMAX Non-line-of-sight systems operate in the ___ frequency band.
a. 800 MHz
b. 900 MHz
c. 2-11 GHz
d. 10-66 GHz
5. Which is not a channel bandwidth defined by the WiMAX Forum.
a. 3.5 MHZ
b. 5 MHz
c. 7 MHZ
d. 10 MHZ
e. All are defined
6. WiMAX supports up to a maximum of __ sectors per site.
a. 1
b. 2
c. 3
d. 4
7. Mobile IP provides secure internet mobility using a connection between the
home agent router and the foreign agent router. This connection is called a
___.
a. Trunk
b. Tunnel
c. Link
d. Gateway
MAX204SGV4.0
60

8. Provides management of security and mobility.
a. AP
b. CAPC
c. EMS
d. NTP
9. Provides network computers with IP address and other network parameters.
a. DNS
b. DHCP
c. FA
d. HA
10. Provides access layer connectivity and QoS between the subscribers and the
AP.
a. ASN
b. CSN
c. AAA
d. CAPC
MAX204SGV4.0
WiMAX Networking
61
Lesson 2
WiMAX Networking
Objectives:
1. Understand the function of the individual network elements found in the core
network
2. Understand the flow of data between the network elements in the core
network
By the end of this lesson you will have gained the skills needed to perform the
following tasks:
1. Understand the purpose of each WiMAX network element
2. Understand the relationships between WiMAX network elements
Introduction:
The core network is responsible for providing the path between the Access Point and
customers subscribed services. The core network is comprised of:
AAA
DHCP
DNS
NTP
Layer 2 Ethernet Switch
Layer 3 Router
Home Agent
Foreign Agent
Voice Gateway
Data Gateway
These elements may be found in the Access Service Network (ASN), Connectivity
Service Network (CSN), or both. Their operation is not dependant upon where they
reside in the network. In this lesson we will look at the part each of these devices
plays in the overall end-to-end WiMAX network.
MAX204SGV4.0
62
WiMAX Networking
MAX204SGV4.0
WiMAX Networking
63
AAA Server
Sometimes called the Triple A server, it provides Authentication, Authorization, and
Accounting services for the WiMAX network. The AAA server maintains information
related to subscriber accounts. The system uses Radius and EAP authentication
protocols, with the AAA acting as a Radius and EAP server. The CAPC acts as a
Radius client and EAP authenticator.
Authentication
Authentication begins after the Subscriber Station (SS) has completed its network
entry process with the Access Point (AP). The SS has a downlink and uplink
channel, MAC synchronization and is ranged.
The authentication process:
1. The AP sends a network entry request to the CAPC which is acting as an
EAP authenticator
2. The CAPC requests the SSs Network Access Identifier (NAI) which is in the
form of username@realm.com
3. The CAPC, now acting as an AAA client, forwards the EAP request to the
SSs home AAA (based on the NAI)
4. The ST and AAA now exchange multiple EAP messages
Authentication
EAP success or failure is passed from the AAA to the CAPC. This exchange is
discussed in more detail in the WiMAX Call Processes lesson.
Actually two forms of authenticating are taking place. SS authentication ensures the
device is compliant with the network, and is also helpful in denying access to stolen
SSs. User authentication ties the user to a billing account and identifies subscribed
services.
For more information on the RADIUS protocol

consult:
RFC2284, RFC2548, RFC2619, RFC 2621,
RFC2716, RFC2809, RFC2865 through
RFC2869, RFC3579, RFC3580, RFC3748
MAX204SGV4.0
64
WiMAX Networking
Authorization
The authorization step provides information needed for session access. At the
WiMAX system level the operator creates Service Classes which define parameters
for:
Traffic Priority
Maximum Sustained Rate
Maximum Traffic Burst
Minimum Reserved Rate
Jitter
Latency
And many others
Service classes are then assigned in the AAA at the user account level to provide
Quality of Service (QoS) for subscribed services. The system comes with default
Service Classes for VoIP, CBR, CIR, Video, and generic broadband. The operator
has the ability to build others.
The AAA server knows which services and networks the SS may access. Policy and
admission control is provided based on subscriber profiles. The profiles are used to
authorize service flows, which are closely related to Quality of Service (QoS). If a
user subscribes to Voice over IP (VoIP) for example, there will be an associated
service flow and QoS.
The chart below shows an example of the relationship between the Service Class
Name, AAA QoS Rule Index and User Priority.
Service Class Name
VoIP_1
VoIP_Signaling
AAA QoS Rule

user_priority
Application Description
Index
1
5
High priority Voice bearer (UL & DL)
2
4
SIP and other Signaling (UL & DL)
Low_VoIP
Low Priority Voice Bearer (UL & DL)
High_Data_UL
High Priority Data Service
Med_Data_UL
Medium Priority Data Service
Data_UL
Best Effort Data Service
MAX204SGV4.0
WiMAX Networking
65
Total_Max_Committed_UL
AAA User QoS Profile

QoS profile attribute 1
VoIP_1
BE_Data
BE_Signaling
Data_1M_UL
Data_1M_DL
0=Provisioned
1=Active
2=Default
3-7 =Reserved
Rate (in Kbits per second)
Total_Max_Committed_DL
Total_Max_Bandwidth_UL

Total_Max_Bandwidth_DL
User_Priority

1-8
Service_Class_Name
Initial_Service_Flow_State
Convergence_Sublayer

0=IPv4
1-7=Reserved
Must match Service

Classes created at the
system level
Indicates action BCU

should take upon network
entry.
Sum of all committed UL

service flows admitted for
user
Sum of all committed DL
service flows admitted for
user
Real-time sum of all UL
service flows ft the user
Real-time sum of all DL
service flows ft the user
This parameter is a
placeholder for TRD
requirement R6082
Convergence Sublayer
supported by the device.
Shown below is an example of a user profile:

USER_ID,Services{BE_data:2,VoIP_1:0,BE_sig:1}
Total_Max_Committed{128,512}
Total_Max_Bandwidth{140,525}
User_Priority{4}
Convergence_Sublayer{0}
Pre-provisioned service flows are activated when the SS is registered with the
system; dynamic service flows are assigned when requested.
MAX204SGV4.0
66
WiMAX Networking
Accounting
The AAA server uses RADIUS accounting messages to create a usage data record
for every packed data session. Information on the start and stop time and number of
packets sent and received is available to be used for customer billing.
Three forms of accounting are available, online for prepaid applications, offline for
post paid applications, and hot lining for denial of service applications.
In online prepaid accounts customers purchase packet data service in advance. It
could be sold to them on duration of connection with time of day and day of week
rates, or sold by number of packets transported. Since the AAA keeps information
on each session, billing rates can vary based in service flow.
Offline accounts are billed after service is delivered. Again it may be on time
duration, packets transported or service flow.
Hot lining allows a provider to deny access to customers who are no longer
authorized to use packet data services. Access may be denied because their
prepaid account has been depleted or possibly for non-payment. When a hot lined
customer attempts to access packet data services they are redirected to a hot line
application which describes the reason they are being denied service and offers a
way to resolve the problem.
Accounting
MAX204SGV4.0
WiMAX Networking
67
Authorization Between ASNs

A mobile subscriber must re-authenticate when it moves into another network
providers ASN. The CAPC in the visited network will request the SSs NAI, which is
in the form of username@realm.com. This NAI points toward the SSs home AAA.
In this case the visited AAA acts as an AAA proxy forwarding the authentication
request to the home AAA for processing. Authentication now follows the steps
previously described.
Authorization
MAX204SGV4.0
68
WiMAX Networking
Dynamic Host Configuration Protocol (DHCP) Server

The DHCP function provides for establishing Layer 3 connectivity by assigning IP
addresses to devices. One goal of a DHCP server is to ensure that no two devices
on a network concurrently have the same IP address. DHCP servers reside in the
Access Service Network (ASN) and the Connectivity Service Network (CSN).
Network devices containing a DHCP client can request an IP address of the DHCP
server. The DHCP server can assign addresses by one of three methods:
Manual Allocation (Static)

IP addresses are contained in a table where the system administrator has matched
them with device MAC addresses. The server will only assign an IP addresses to
device MAC addresses listed in the table.
Automatic Allocation (Static)

The system administrator defines in a table a range of IP addresses. A device
requesting an address is assigned, by the server, a permanent IP address from the
list.
Dynamic Allocation
As with automatic allocation, dynamic allocation assigns a device an address from a
preconfigured list. But with dynamic allocation the address is owned by the device
for a controlled period of time called a lease. Lease times can vary from one hour to
months or can be set to infinite which means they never expire. When the lease
expires the address is available for reassignment. This method automates the
assignment of IP addresses
A WiMAX network operator must decide if device IP addresses will be assigned
using DHCP, as described above, or statically. Statically means entering the IP
address manually during network element commissioning. Static assignment may
be suitable for a network with a small number of managed elements, but larger
networks may benefit from dynamic allocation.
For more information on DHCP consult

RFC1531, RFC1541
MAX204SGV4.0
WiMAX Networking
69
Element Management System (EMS)

The Element Management System (EMS) is a central point for configuration,
monitoring and management of the Motorola WiMAX Fixed Network Elements (FNE).
Specifically the EMS is responsible for managing the Subscriber Stations (SS),
Access Points (AP) and Carrier Access Point Controllers (CAPC).
The EMS provides basic FCAPS functionality, including:
Fault Management
Alarm and event handling
State management
Event logs
Diagnostics
Software and configuration distribution
Inventory Data
Entity browser
Motorola software server
Statistics collection and reports
Security Management
User accounts
Security logs
Control point for distribution of security keys
North Bound Interfaces to the EMS include:

SNMP event stream
XML configuration and inventory files
HP Open View integration support
EMS
MAX204SGV4.0
70
WiMAX Networking
Access Point (AP)
The pole Motorola Access Point is the interface between the air interface and the
backhaul network. It is made up of a Radio Frequency (RF) head and a Base
Control Unit (BCU). The RF head provides broadband wireless access in the 2.3,
2.5 and 3.5 GHz spectrum. Diverse antenna techniques with Multiple-Input,
Multiple-output (MIMO) capability results in enhanced coverage and strong indoor
penetration. Fiber and power cables connect the RF head to the BCU.
The BCU can be pole or floor mounted. The BCU cabinet contains slots for up to
two site controllers. IEEE 802.16e Physical and MAC layer functions are performed
by the BCU Modem card. The BCU contains slots for up to 4 modem blades, with
each typically supporting a sector. Interface to the backhaul network is through the
Ethernet connections on the Site Controller blade. Other BCU blades are
responsible for power, alarms and timing.
MAX204SGV4.0
WiMAX Networking
71
Carrier Access Point Controller (CAPC)
CAPC
The CAPC is responsible for managing WiMAX security and mobility functions.
The CAPC provides
Subscriber authentication
Subscriber authorization
Key distribution
Idle paging controller
Mobility decision point
Local maintenance
By serving as a RADIUS client for authentication and authorization, the CAPC
performs the ASN Gateway Decision Point (ASN-DP) function defined by the WiMAX
Forum.
The CAPC paging controller (location register) stores all information gained about a
subscribers equipment location. When a packet is received by the CAPC for an idle
subscriber, the CAPC buffers the packet, accesses the paging controller information, and
uses its paging function to locate the idle subscriber. Once the subscriber equipment item is
located and returns to an active state, the CAPC forwards all buffered packets to the AP
serving the subscriber.
The CAPC is built on the industry standards based Avantellis platform with a bladed
architecture that supports pay as you grow scalability and performance. Full
redundancy is provided at the System Controller, Payload and Shelf Management
blades. N + 1 power distribution redundancy is also available. Each CAPC shelf has
the capacity to manage up to 1 million end user devices and up to 1,000 Access
Points.
.
MAX204SGV4.0
72
WiMAX Networking
Domain Name Service (DNS)

The function of the DNS server is to convert Fully Qualified Domain Names (FQDN) to
an IP address. A domain name is comprised of two or more parts separated by dots,
for example motorola.com. The rightmost part contains the top-level domain. All
parts to the left are sub-domains.
The DNS server provides the IP address of the applicable network node when queried
by an ASN NE or subscriber equipment item with a FQDN. To allow the DNS server
to be reached by all NEs, the DNS server IP address must be provided to all NEs.
This is accomplished during the DHCP request/response process when the NEs are
obtaining their interface IP addresses. The DNS server IP address is included in the
DHCP server response to the requesting NE. The DHCP server must be provided
with the DNS server IP address when it is configured on the network. When a
subscriber equipment item obtains its IP address, the AP serving the subscriber item
checks the DHCP server response to verify that the DNS server IP address is
included in the appropriate response field. If it is not, the AP inserts a copy of its IP
address for the DNS server into the DHCP response to the subscriber item. All NEs
provide update information to the DNS server when they receive their IP addresses
from the DHCP server.
Domain Name Server
For more information on DNS consult

RFC1032 through RFC1035
MAX204SGV4.0
WiMAX Networking
73
Network Time Server

A Network Time Server is a device that takes a timing reference from a very accurate
timing source such as the GPS satellites. This timing reference is then distributed to
a computer network.
Network Time Protocol (NTP)

Network Time Servers run the Network Time Protocol (NTP). The Network Time
Protocol is available from the Network Time Protocol Project (http://www.ntp.org/).
The current version supported in WiMAX is NPTv4. SNTP v4 is compatible with
SNTP v3 clients and servers; however, SNTP v4 has added an authentication feature
which SNTP v3 does not have.
WiMAX NTP
The NTP server provides signals to the AP, CAPC and EMS which are used to
synchronize their timing clocks with network time. These NEs use SNTP clients to
query the server periodically and derive a time offset from the server reported time to
adjust their clocks. NTPv4 has a precision of about 200 picoseconds.
The NEs will be provided with the NTP server IP address by the DHCP server with the
response to their DHCP request. This requires that the DHCP server be provided the
NTP server IP address as part of its configuration process.
The function of the Network Time Server is to provide the EMS, CAPC, AP and CPE
the ability to assign time stamping events, alarms and statistics. The EMS, CAPC
and AP perform a conversion from Universal Coordinated Time (UTC) to local time.
Network Time Server
For more information on NTP consult

RFC1305, RFC2030
MAX204SGV4.0
74
WiMAX Networking
Layer 2 Ethernet Switch

In our WiMAX network the Ethernet output of the Access Points are connected to a
Layer 2 Aggregation switch. These devices support the Layer 2 switching network
transporting bearer and control traffic between the APs and other Access Service
Network (ASN) elements.
Updates are sent from the AP to the switch to enable proper Layer 2 packet switching.
Messages sent by the SSs and delivered by the AP to the Layer 2 switch network
contain the SSs 48-bit MAC address as the source address. Layer 2 switches
contain a database associating the MAC address with VLAN parameters. When a
frame is received, the Layer 2 switch looks in the database for the destination MAC
address. If an entry exists, the switch forwards the frame to the designated port. If
an entry does not exist, the switch forwards out the frame to every port associated
with the same VLAN. In this the switch is effectively acting like a hub. When the
switch receives a response it updates its filtering database.
The WiMAX operator has the option of provisioning multiple unique interfaces on the
MAN into a VLAN. VLAN tagging can be used to:
Manage physically different Ethernet segments connected/aggregated on the
same physical port on the router through interim Layer 2 bridged network and
logically extending a physical LAN.
Manage different devices belonging to same group connected on the same or
different Ethernet segments.
Isolate the control or bearer traffic and provide different priority or scheduling
or forwarding behavior.
The system supports VLAN tagging as defined by the IEEE802.1Q standard. VLAN
tagged packets specify the priority bits, which can be set to enable specific Layer 2
forwarding behavior. Layer 2 priority bits may be set to enable Layer 3 QoS
attributes. The user_priority field must be set to a value in order that all frames
receive the proper QoS treatment on the backhaul. Valid user_priority values range
from 0 to 63, with 0 being the lowest priority. Notice the relationship to the AAA
Server QoS Rule Index. The table below is an example.
Service Class Name
VoIP_1
VoIP_Signaling
AAA QoS Rule

user_priority
Index
1
5
High priority Voice bearer (UL & DL)
2
4
SIP and other Signaling (UL & DL)
Low_VoIP
Low Priority Voice Bearer (UL & DL)
High_Data_UL
Med_Data_UL
Medium Priority Data Service
Data_UL
Best Effort Data Service
The values entered in the Service Class Name field will reflect the WiMAX operators
service offerings.
MAX204SGV4.0
WiMAX Networking
75
Layer 3 Router
The Router routes bearer traffic between the ASN and other networks providing
connectivity and/or application services to WiMAX subscribers. All bearer traffic
within the Layer 2 network is sent via the router. This router forms the gateway
between the ASN Layer 2 switched network and the Layer 3 network or networks
where subscribers obtain services and operate applications. The CAPC is
connected to the router for handing control traffic. Control traffic is essentially
signaling traffic between the AP and CAPC.
The Router will map the VLAN user_priority bits to Layer 3 QoS bits before forwarding
the packets to other NEs within the ASN/CSN. The differing QoS requirements of
services on the WiMAX network are satisfied by assigning Differentiated Services
values to the packets. The network uses these values to classify, mark, shape,
police traffic, and perform intelligent queuing. The Differentiated Services Code
Point (DSCP) tag is a 6 bit field and valid values range from 0 to 63, with 0 being the
lowest priority. The table below is an example.
Service Class Name
VoIP_1
QoS DSCP
Map
46
High Priority Voice Bearer (UL &DL)
26
VoIP_Signalling
High_Data_UL
SIP and other signaling (UL &DL)

18
In WiMAX, to ensure support for both L2 and L3 backhaul networks, mapping of

DSCP markings will be supported for uplink IP packets leaving the AP. Mapping of
DL markings is also supported for additional flexibility but is expected to be configured
to be pass-through in most deployments
WiMAX Network
MAX204SGV4.0
76
WiMAX Networking
Mobile IP Routers
As mobile Subscriber Stations (SS) move across a WiMAX network they are
continually changing their Point of Attachment (PoA). Even while mobile, users have
the expectation of continuous Internet connectivity no matter where they are
physically in the network. This poses a problem in the fact that Internet Protocol
requires end point connections to have an IP address that is associated with a unique
PoA. In IP changing a PoA requires a change in IP address.
Mobile Internet Protocol allows for the routing of IP datagrams to mobile SSs at any
PoA in the network. This is accomplished by assigning the mobile SS a second IP
address, a Care of Address. The Care of Address provides information about the
mobile SSs current PoA to the Internet. A tunnel is created to transport IP
datagrams from the mobiles home PoA to the Care of Address. Two network
elements facilitate Mobile IP, the Home Agent and Foreign Agent.
Home Agent
The Home Agent is a router on a mobile SSs home network which tunnels datagrams
for delivery to the mobile SS when it is away from home. During registration the
mobile SS communicates its current reachability information. The Mobile IP
Registration procedure creates or updates a mobility binding at the Home Agent
associating the mobile SSs IP address with the Foreign Agents Care of Address.
The Home Agent is responsible for maintaining current location information for the
mobile SS.
Foreign Agent
Foreign Agent is a router on a mobile SSs visited network which provides routing
services to the mobile SS while it is registered and authorized to use the visited
network. The Foreign Agent detunnels and delivers datagrams to the mobile SS that
were tunneled by the mobile SSs Home Agent.
The Foreign Agent maintains a Visitor List of registered mobile SSs containing the
mobile SSs Destination Address.
Agent Discovery Process

So how does an SS know it is in its home or a foreign network? There are two
possible methods used in what is called the Agent Discovery Process. They are the
Foreign Agent Advertisement Procedure and the Foreign Agent Solicitation
Procedure.
Foreign Agent Advertisement Procedure
In this procedure the Foreign Agent advertises its services by periodically
broadcasting Agent Advertisement messages. The mobile SS uses these
advertisements to determine their current PoA.
Foreign Agent Solicitation Procedure
In the absence of Agent Advertisement messages the mobile SS will use this
procedure to solicit Agent Advertisement messages.
MAX204SGV4.0
WiMAX Networking
77
Call Routing
We will assume that the mobile SS has successfully registered with its Home Agent
and a Foreign Agent in a foreign network.
A datagram received on the home network is intercepted by the Home Agent. The
Home Agent encapsulates the datagram and tunnels it to the mobile SSs currently
registered Care of Address (COA). The Foreign Agent receives the encapsulated
datagram and compares the inner Destination Address (DA) to entries in its Visitor
List. If a Destination Address match is found, the Foreign Agent decapsulates the
datagram and forwards it to the mobile SS.
For datagrams sent to the Internet by a mobile SS the Foreign Agent serves as a
default router for registered SSs. It is also possible to have datagrams sent by the
SS to be encapsulated and tunneled from the Care of Address to the Home Agent for
delivery to the Internet. This is called reverse tunneling.
Home Agent / Foreign Agent
MAX204SGV4.0
78
WiMAX Networking
Media Gateway
The goal of a WiMAX network is to deliver packets of data between Subscriber
Stations (SS) and applications. Those packets of data may contain voice, data traffic
or video. A Media Gateway is a device that converts data from one format to another.
Media Gateways are required to convert the IP format of the WiMAX network to the
formats required by the application network.
For voice applications, the Media Gateway is responsible for converting the Real-time
Transfer Protocol (RTP) of the IP network to the Time Division Multiplexed (TDM)
protocol of the Public Switched Telephone Network (PSTN). Or we may say
conversion from a packet based network to a circuit based network.
Data and video applications will also make use of Media Gateways for protocol
conversion. In the case of video the conversion will be from streaming media to IP.
Data conversion may be from IP to ATM.
MAX204SGV4.0
WiMAX Networking
79
Voice Application Server

WiMAX networks will provide voice services using Voice over Internet Protocol (VoIP).
The most commonly used VoIP call management protocol in use today is Session
Initiation Protocol (SIP). SIP is a simple text based description protocol that uses
interactions similar to HTTP or SMTP in order for two systems to describe the media
stream needed to get between two points. Residing on the SS will be a SIP client.
At the edge of the network will be the VoIP Application Server, sometimes called a
Call Agent, which is responsible for call control. Call control includes signaling
functions such as on/off hook, dialed digits and others. The Call Agent is responsible
for converting SIP to a signaling protocol recognized by the PSTN, such as Signaling
System 7 (SS7).
VoIP Service
For more information on the SIP protocol

consult RFC2543, RFC3261, RFC3265
For more information on media gateways
consult ITU H.248, ITU H.323, RFC3435,
RFC2805
MAX204SGV4.0
80
WiMAX Networking
Asterisk Private Branch Exchange

Many software applications are available for business customer VoIP solutions. One
example is Asterisk. The Asterisk software is an open source IP Private Branch
Exchange (PBX) telephony platform that is designed to run on LINUX. Essentially
Asterisk is middleware connecting telephony technologies such as VoIP services like
SIP, T1, ISDN and PSTN to telephony applications like voice mail, call
conferencing/bridging, intercom and others. Asterisk interfaces with almost all
standards-based telephony equipment and supports a wide range of protocols and
codecs.
While feature additions to traditional PBXs may require hardware changes, feature
additions and system reconfigurations in Asterisk are a matter of table entries.
Operators have access to an Asterisk PBX through Command Line (CLI) or Graphical
User Interfaces (GUI). PBX extension features are defined in the Asterisk Dial Plan.
The Dial Plan, stored in a text file, defines the route and actions to take for each call in
the system from its source through various applications, to its final destination.
For more information on Asterisk consult

www.asterisk.org
www.digium.com
MAX204SGV4.0
WiMAX Networking
81
Lesson Summary
Understand the function of the individual network elements found in the core
network
Understand the flow of data between the network elements in the core
network
MAX204SGV4.0
82
WiMAX Networking
MAX204SGV4.0
WiMAX Call Processes
83
Lesson 3
MAX204SGV4.0
84
MAX204SGV4.0
85
Lesson Objectives
Upon completion of this lesson you will be able to:
1. List the WiMAX mobility modes
2. List the WiMAX handover modes
3. List the Network Elements involved in WiMAX mobility
4. Define the different WiMAX mobility architectures
5. Explain WiMAX lease operations
6. Explain WiMAX ST idle mode(s)
7. Illustrate the WiMAX Network Entry process
8. Understand Connections (CID)management, bearer, special.
9. Understand the concept of capabilities negotiations, service flow establishment/modification, and
end to end QOS.
10. Illustrate the WiMAX handover process
11. Understand the concept of side-haul traffic and mobility support in call management procedures.
12. Establish a logical approach to troubleshooting a call flow scenario.
By the end of this lesson you will have gained the skills needed to perform the following tasks:
1. Interpret system information
2. Interpret sniffer/traces
3. Isolate network failure
This lesson introduces call processing in Motorolas WiMAX system. It builds upon the Introduction to
TCP/IP and the Introduction to Mobile IP web-based courses that you have completed. The lesson is
broken in to three sections:
WiMAX Subscriber Terminal Network Entry Process
WiMAX Mobility Architecture
WiMAX Mobility / Call Processes
Trouble Shooting Considerations
MAX204SGV4.0
86
A General Overview of the End to End Call Setup

In this section, we will discuss the End To End Call Setup Process. As depicted on the facing page,
there are many steps that need to be accomplished in the process of establishing an end to end
connection for the purpose of transporting subscriber data.
It is important to understand the relationships and background information exchanges between
network nodes in the WiMAX network that are necessary to create and sustain a network pathway for
subscriber traffic.
As we will see, the process is initiated by a request from the subscriber to register with the network
followed by an authentication process and subsequent registration and connectivity. But during the
overall process, a series of exchanges are required between the supporting nodes in the Access
Service Network to support the establishment of service to the subscriber.
The Access Point must exchange user information with the CAPC. The CAPC must communicate
the information to other nodes such as the DNS and DHCP servers and Foreign Agent and also act as
an AAA proxy on behalf of the subscriber.
Connectivity out of the ASN may be required and therefore involve the exchange of messages with
the Connectivity Service Network to support the establishment of service for a subscriber who is
mobile.
In our illustration, we see the registration request from the SS/MSS to the AP, which is then forwarded
to the CAPC for assistance in registering the user on the network. The CAPC then will be required to
communicate with the local DNS server to resolve the user ID and subsequently with the AAA server
on the subscribers home network to assist in the authentication process.
After the user is authenticated, then they must be assigned an IP address for use on the network and
possibly a Care Of Address if they are mobile. This may involve obtaining an address assignment
from the DHCP server on the home network and mapping that to a Care Of Address for a local
Foreign Agent.
As we will see when we discuss Call Flow Processes later in the lesson, we will see that while the
subscriber is registered on the network, management of that subscribers lease will be under the
control of the CAPC node and will at times be transferred between the CAPC and the APs and may
even be transferred to another ASN if necessary.
MAX204SGV4.0
87
A General Overview of the End to End Call Setup continued.
Access
Service Network
(ASN)
1- Initial Ranging and Registration Request

2- Exchange of SS/MSS information
3- DNS lookup of USER@REALM
4- AAA proxy Radius exchange with Home AAA
5- FA to HA binding
6 SS/MSS lookup in Home AAA
7- IP address assignment from Home DHCP
Connectivity
Service Network
(CSN)
NTP
EMS
DNS
DHCP
DNS
Server(s)
L2/L3/FA
AP
MSS/CPE
192.168.2.x
Assigned IP for CPE
Held by AP or CAPC
Registration
CAPC
Transport
Between
ASN & CSN
64.150.2.x
Gateway
Router/HA 6
Foreign Agent 5
DHCP
AAA
192.168.2.x
AAA
VoIP
Server
This diagram represents

background interactions to
support CPE registration
MAX204SGV4.0
88

In this section, we will discuss the Network Entry Process. As depicted on the facing page, there are
seven (7) steps that need to be accomplished before a Subscriber Terminal (ST) is ready to send or
receive data.
The term data is not specific to the type of

traffic being passed to/from the ST.
Scanning for Channels

Ranging
The first two steps are to establish basic

synchronization with the physical and MAC
layers of the WiMAX air interface.
Capability Negotiation
The next step is to establish basic equipment

capabilities support between the subscriber
and the ASN.. Keep in mind that this is not
negotiation of subscriber services but rather
what the MSS equipment can do and what the
ASN network equipment they are connecting to
can support.
1. Authorization
The remaining steps are required to establish

connectivity through the ASN network on
behalf of the subscriber. And include steps for
authenticating the subscriber and assigning
them an address as well as negotiating access
to services subscribed to and actual call
establishment. This part of the process is
mostly carried out between the nodes in the
ASN and CSN networks.
2. Registration
3. IP Connectivity
4. Service Established
MAX204SGV4.0
89
WiMAX Subscriber Terminal Network Entry Process continued
MAX204SGV4.0
90
Scan and Synchronize to Downlink Channel
Scan and Synchronize to Downlink Channel

1
Scan for Channel

Upon power-up, ST begins scanning its frequency list to find a valid downlink (DL)
operating channel (may be preconfigured to a specific frequency and/or
frequency list, i.e. bandmap).
If this is after a signal loss, ST uses last operational parameters to acquire downlink
Achieves synchronization one it finds a valid downlink signal
Obtain Downlink Parameters

Downlink Channel Descriptor (DCD) and DL-MAP
DCD describes physical layer characteristics of downlink channel (i.e., modulation
type, forward error-correction type, preamble length, etc.)
DL-MAP contains info on how to interpret and use description in DCD
Considered MAC syncd if at least one DL-MAP has been received
Obtain Uplink Parameters

Uplink Channel Descriptor (UCD) and Uplink MAP (UL-MAP)
UCD describes transmit parameters, timing of the uplink initial ranging contention
slot, etc.
UL-MAP contains info on how to interpret and use description in UCD
Considered to have valid uplink parameters as long as it received UL-MAP and
UCD
MAX204SGV4.0
91
Scan and Synchronize to Downlink Channel continued
Scan and Sync to Downlink Channel
MAX204SGV4.0
92
Initial Ranging
Ranging is the process by which a ST tunes its timing, frequency offsets, and power so that the
transmissions from the ST are aligned with the APs receive frames and are received by the AP within
the appropriate limits.
Initial Ranging
1
AP sends initial ranging slots in UL-MAP
ST randomly chooses initial ranging slot/code and transmits CDMA code with its
parameters (timing, power, etc.)
If further adjustments are needed:
RNG-RSP from AP contains time and power corrections, ranging code
attributes (which code, where received), status = continue
ST identifies the RNG_RSP as being for itself and reads UL-MAP for
ranging slot/code
ST makes the requested adjustments and sends CDMA code again
If no further adjustments are needed:
RNG-RSP from AP contains time and power corrections, ranging code
attributes (which code, where received), status = success, and
allocates bandwidth for the ST to transmit the RNG_REQ
RNG-REQ from ST contains its MAC address, requested Downlink
Burst Profile
RNG-RSP from AP contains ST MAC Address and Basic and Primary
Management CIDs
MAX204SGV4.0
93
Initial Ranging Continued
Initial Ranging
MAX204SGV4.0
94
Negotiate Basic Capabilities

During this part of the network entry process, the ST and AP negotiate basic capabilities using the
SBC-REQ (SS basic capability request) and SBC-RSP (SS basic capability response) management
messages over the Basic connection.
The list of capabilities includes:
MAC capabilities
Maximum transmit power
Current transmit power
OFDMA modulator/demodulator
Authorization policy (EAP)
PKM version support (PKM, PKMv2)

1
ST send it capabilities to the AP (SBC-REQ)
AP replies back (SBC-RSP) with a list containing the capabilities it supports (on/off
derived from the list that the ST sent)
If the SBC-RSP IS NOT acceptable:
The ST will retry using SBC-REQ message.
If all retries are exhausted, the ST will reinitialize MAC.
If the SBC-RSP IS acceptable:
Go to next step in network entry processAuthorization
The SBC-REQ/RSP does not stop the ST from continuing with the
network entry procedures if the ST & AP capabilities dont match.
If the ST proceeds to Authorization, the AP will flag the ST and reject the
registration request (REG-REQ) forcing the ST to reinitialize MAC.
MAX204SGV4.0
95
Negotiate Basic Capabilities continued
MAX204SGV4.0
96
Authorization and Key Exchange

During this step of the network entry procedure, the ST and the network authenticate each other.
Authentication is initiated by the network side.
Authorization and key exchange portion of the network entry process uses several different
security/authorization methods. While it is beyond the scope of this training to go into the specifics,
we will define them below:
Extensible Authentication Protocol (EAP) - a universal authentication framework frequently used in
wireless networks and Point-to-Point connections. It is defined by RFC 3748.
Privacy Key Management Protocol (PKM) The PKM key management protocol facilitates mutual
authentication of the ST and AP, as well as distribution of traffic keying material from the AP to the ST.
It also supports periodic reauthentication/reauthorization and traffic key refresh.

1
Immediately after SBC-RSP, AP sends message to CAPC to start the EAP

authentication process.
CAPC requests ST identity thru AP (PKM-RSP)
PKM-REQ from ST to AP/CAPC/AAA

Use MAC address and ST@realm.com to point to and authenticate on correct AAA
server
Security associations (crypto keys, digital certs, etc)
Can use certificate (X.509)
AAA sends accept success (to CAPC) with

MSK (Master Secret/Session Key)
MIP info (HA address, HoA, MIP Key)
DHCP server address
Authorization profiles
CAPC stores information and also sends to AP/ST
AP starts three-way SA-TEK (security association traffic encryption key) exchange

with ST to verify both have correctly derived the keys
MAX204SGV4.0
97
Authorization and Key Exchange continued
MAX204SGV4.0
98
Registration
Registration occurs after the ST has successfully authenticated on the network. It is the process by
which an ST is allowed entry into the network to complete the network entry process (Mobile IP
registration, dynamic services, etc.). Also, managed STs receive their Secondary Management CID
(the secondary management CID is currently not supported).
Registration
1
REG-REQ to AP includes information such as IP version, vendor specific

information, number of UL CIDs support, ST management support, etc.
AP responds in REG-RSP ST management support and other relevant information

such as IP version.
Establish Initial Service flows (2) that will be used for all communication between ST
and AP until others are set-up (management, IP address assignment, etc.)
Uplink
Downlink
MAX204SGV4.0
99
Registration continued
Registration
MAX204SGV4.0
100
Connections and Addressing

In the WiMAX network the 48 bit MAC address is really only used to identify an SS/MSS before
successful ranging has been accomplished. After that, to identify data exchanges between the
SS/MSS and the network, Connection Identifiers are used.
For example: a Basic CID is assigned to each SS/MSS, after initial ranging, and is used to transport
basic MAC control/management messages and communicate information that is time critical.
Additional CIDs for transporting data and management traffic may be negotiated during initialization or
dynamically added during operation to identify user data traffic flows.
By definition, a WiMAX connection is unidirectional and therefore for most services a pair of
connections, one in each direction, will be required to support bi-directional exchanges. There are no
limits to the number of connections allowed between a subscriber and an access point except for
practical limitations imposed by implementation or design.
A separate Connection ID will be assigned for each connection in either direction with the exception of
Basic, Primary and Secondary management connections which will generally share the same CID in
both directions. And at least one Transport Connection in either direction will be assigned to identify
user data going to or from the SS/MSS.
CID Allocation
The following types of CIDs are defined for use:
Initial Ranging CID During the Initial Ranging process a CID is necessary to tag the data
for that purpose. Since an SS/MSS has no unique CID assigned at this point, a default CID (the
Initial Ranging CID), is used for this purpose.
Basic CID During the ranging process a Basic CID is assigned for the SS/MSS to use for
the exchange of delay-intolerant and time-critical MAC management messages with the AP. In this
case the CID assigned will be the same for both the UL and DL directions.
Primary Management CID Also during the ranging process, there is the assignment of a
Primary Management CID. Each SS/MSS is assigned a Primary Management CID for the transport
of more delay-tolerant MAC management messages between the subscriber and the access point.
Again, the same CID will be assigned for use in both directions.
Secondary Management CID The secondary management connection is used to transport
higher layer management messages (such as DHCP and SNMP) and is only assigned if the
subscriber is identified as a managed SS/MSS and is again assigned to both UL and DL
connections.
Transport CID At least one Transport CID is required to identify data traffic transported to or
from a SS/MSS and is assigned after the completion of ranging and authentication. This CID will be
assigned to carry user information in either direction and for bidirectional information exchange two
CIDs are required in this case.
MAX204SGV4.0
101
Connections and Addressing
Connection Identifiers
<-CID->
Basic
<-CID->
Primary Management
CID->
Transport
<-CID
CID->
Transport
<-CID
Initial Ranging CID

Basic CID
Primary Management CID
Transport CIDs
MAX204SGV4.0
102
Service Flows and Service Flow Identifiers

Service flows are used by the MAC layer to support services such as QOS which are implemented on
a per-connection basis. When an SS/MSS is added to a system, SFIDs for the subscriber, are
provisioned in the system, along with their associated QOS parameters. Upon registering these
SFIDs are mapped onto unique CIDs which are in turn mapped to transport connections.
Additional service flows may be defined in the system, and modified as needs change and depending
on activity. Not all connections (and their associated CIDs), such as those used for management and
control, have Service flows associated with them as the service requirements for that type of data is
always the same and does not require a separate definition.
MAX204SGV4.0
103
Service Flows and Service Flow Identifiers
Service Flow Identifiers

<-CID->
Basic
<-CID->
Primary Management
SFID CID->
Transport
<-CID SFID
SFID CID->
Transport
<-CID SFID
Established Connections with Service Flow Identifiers associated with CIDs
MAX204SGV4.0
104
Dynamic Service Flows

The WiMAX air interface is connection oriented and requires that each packet be carried on a service
flow between the Subscriber Terminal (ST) and Access Point (AP).
As you recall from the network entry process, two types of connections were used that allow the ST to
gain access to the system:
Basic Connection Used by ST and AP to exchange short, time-sensitive management messages.
Ranging
Primary Management Connection Used by ST and AP to exchange longer, more delay tolerant
management messages.
Registration, PKM, IP connectivity
Service flows are unidirectional and must be created separately for the uplink and downlink. Because
Quality of Service (QoS) parameters may be defined differently for each service flow (based on the
type of service being provided), the creation of multiple service flows allows differentiation of the QoS
being provided to each traffic flow.
A service flow is characterized by the following:
Service Flow ID - An SFID is assigned to each existing service flow. The SFID serves as the principal
identifier for the service flow in the network. A service flow has at least an SFID and an associated
direction.
Connection ID (CID) - Mapping to an SFID that exists only when the connection has an admitted or
active service flow.
ProvisionedQoSParamSet - A provisioned QoS parameter set (EMS, AAA server, etc.).
AdmittedQoSParamSet - Defines a set of QoS parameters for which the AP (and possibly the ST) is
reserving resources. The principal resource to be reserved is bandwidth, but this also includes any
other memory or time-based resource required to subsequently activate the flow.
ActiveQoSParamSet - Defines a set of QoS parameters defining the service actually being provided to
the service flow. Only an Active service flow may forward packets.
Authorization Module - A logical function within the AP that approves or denies every change to QoS
Parameters and Classifiers associated with a service flow. As such, it defines an envelope that limits
the possible values of the AdmittedQoSParamSet and ActiveQoSParamSet.
MAX204SGV4.0
105
Dynamic Service Flows continued
Dynamic Service Flows
MAX204SGV4.0
106
ST Initiated Dynamic Service Flow Creation

A ST wishing to establish either an uplink or a downlink dynamic service flow with an AP performs the
following:

1
ST sends a Service Flow creation request to the AP using a DSA-REQ message
AP sends a message received response to the ST (DSX-RVD) and checks the

integrity of the message
Check if ST is authorized service
Check if service flow QoS can be supported
Create SFID
If uplink AdmittedQoSParamSet is non-null, map service flow to CID
If uplink ActiveQoSParamSet is non-null, enable reception of data on
new uplink service flow
AP sends DSA-RSP (response) back to ST

Send SFID and CID
ST acknowledges response message (DSA-ACK)

From the ST perspective, if ActiveQoSParamSet is non-null, enable
transmission and/or reception of data on new service flow
From the ST perspective, if downlink ActiveQoSParamSet is non-null,
enable transmission of data on new downlink service flow
MAX204SGV4.0
107
ST Initiated Dynamic Service Flow Creation continued
MAX204SGV4.0
108
AP Initiated Dynamic Service Flow Creation

An AP wishing to establish either an uplink or a downlink dynamic service flow with a ST performs the
following:

1
A new service flow is required for the ST. After checking below, the AP sends a
DSA-REQ.
Check if ST is authorized service
Check if service flow QoS can be supported
Create SFID
If uplink AdmittedQoSParamSet is non-null, map service flow to CID
ST receives DSA-REQ and:
Confirms ST can support service flow
Adds downlink SFID
Enables reception of a new downlink service flow
ST sends DSA-RSP
If ActiveQoSParamSet is non-null, enable transmission and/or
reception of data on new service flow
If downlink ActiveQoSParamSet is non-null, enable transmission of
data on new downlink service flow
AP receives DSA-RSP
Enable transmission (downlink) or reception (uplink) of data on new
service flow
AP sends DSA-ACK
ST receives DSA-ACK and enables transmission on new uplink service
flow.
MAX204SGV4.0
109
AP Dynamic Service Flow Creation continued
MAX204SGV4.0
110
Dynamic Service Change

There may be times when bandwidth needs to be increased or decrease on an established service
flow. The Dynamic Service Change set of messages (DSC) is used to modify the parameters
associated with a service flow.
A single DSC message exchange can modify the parameters of either one downlink service flow or
one uplink service flow.
If an uplink service flows bandwidth is being reduced, the ST reduces its payload bandwidth first and
then the AP reduces the bandwidth scheduled for the service flow. If an uplink service flows
bandwidth is being increased, the AP increases the bandwidth scheduled for the service flow first and
then the ST increases its payload bandwidth.
Any service flow can be deactivated with a DSC command by sending a DSC-REQ message,
referencing the SFID, and including a null ActiveQoSParamSet. However, care should be taken before
deactivating service flows. If a Basic, Primary Management, or Secondary Management Connection of
an ST is deactivated, that ST is deregistered and must re-register.
ST Initiated Dynamic Service Change

A ST that needs to change a service flow performs the following:

1
ST sends a Dynamic Service Change request to the AP using a DSC-REQ message
AP sends a message received response to the ST (DSX-RVD) and checks the

integrity of the message
Validates request
Modify service flow
Increase channel bandwidth if required
AP sends DSC-RSP (response) back to ST

ST receives DSC-RSP
Modifies service flow
Adjust payload bandwidth

AP receives DSA-ACK and decreases channel bandwidth if required
MAX204SGV4.0
111
ST Initiated Dynamic Service Change continued
MAX204SGV4.0
112
AP Initiated Dynamic Service Change

An AP that needs to change a service flow performs the following:

1
AP sends a Dynamic Service Change request to the ST using a DSC-REQ message

AP receives DSC-REQ and
Validates request
Modify service flow
Decrease payload bandwidth if required
ST sends DSC-RSP (response) back to AP

AP receives DSC-RSP and
Modifies service flow
Adjust channel bandwidth

AP receives DSA-ACK and increases payload bandwidth if required.
MAX204SGV4.0
113
AP Initiated Dynamic Service Change continued
MAX204SGV4.0
114
IP Connectivity/Address Assignment
In this section, we will discuss three types of procedures that a ST uses to obtain an IP address:
Static IP address assignment (permanently assigned to ST)
DHCP address assignment for fixed/nomadic STs
DHCP address assignment for mobile STs (using Mobile IP)
DHCP Procedure for Fixed/Nomadic Clients

DHCP for Fixed/Nomadic Clients
1
The ST sends a DHCP Discover message to the AP.
The AP forwards the information to the local DHCP server.
DHCP server replies (DHCP Offer) with IP addressing information for the ST.
The AP relays the DHCP Offer with the IP addressing information.
The ST sends a DHCP Request (to request the offered parameter) that is forwarded
by the AP to the local DCHP server.
A DHCP Ack from the local DHCP server returns the IP configuration to the DHCP
Relay in the AP.
Once an IP address is allocated to the ST, the classification of the two default
service flows could be updated to reflect the ST IP address:
Uplink - source IP address equals to ST IP address
Downlink - destination IP address equals to the ST IP address
The AP delays sending the final DHCP Ack to the ST to avoid IP traffic being
generated by the ST prior to the completion of the end-to-end data path set up.
Before sending DHCP Ack to the STs, the AP updates the Address Resolution
Protocol (ARP) table in the STs default router and the forwarding tables on the L2
devices by sending an ARP Request message. The associated ARP Reply will be
used by the AP as an acknowledgement of end-to-end data path establishment.
The AP sends DHCP Ack to the ST. The ST receives IP address assignment.
MAX204SGV4.0
115
DHCP Procedure for Fixed/Nomadic Clients continued
DHCP Procedure for Fixed/Nomadic Clients
MAX204SGV4.0
116
Mobile IP Terminology Review

Mobile IP is a standard that allows users with mobile devices whose IP addresses are associated with
one network to stay connected when moving to a network with a different IP address.
Mobile Node - A Mobile Node is a host or router that changes its point of attachment from one
network or sub-network to another. A mobile node may change location and continue to
communicate with other nodes using its permanent IP address. For our purposes, this is the
Subscriber Terminal (ST).
Home Address (HoA) - An IP address that is assigned to a mobile node. The address remains
unchanged regardless of where the node is attached to the Internet.
Home Network - A network, possibly virtual, that has a network-prefix that matches the mobile nodes
home address.
Home Agent (HA) - A router on a mobile nodes home network that tunnels packets for delivery to the
mobile node when it is away from home and maintains current location information for the mobile
node.
Foreign Network - Any network whose network-prefix does not match the network-prefix of a mobile
nodes home address.
Foreign Agent (FA) - A router on a mobile nodes visited network that provides routing services to the
mobile node while registered. It de-tunnels and delivers packets to the mobile node that were
tunneled by the home agent of the mobile node. For packets sent by a mobile node, the foreign
agent may serve as the default router.
Care-of-Address (COA) - An IP address associated with a mobile node that is visiting a foreign link.
It is the IP address of the Foreign Agent.
Mobile IP Registration - When the mobile node is away from home, it registers its care-of-address
with its home agent. Depending on the method of attachment, the mobile node will register either
directly with its home agent or through another device, which forwards the registration to the home
agent.
Authentication, Authorization, and Accounting (AAA) Server - Provides network authentication
and authorization. May also be used for billing.
Tunnel - A tunnel is the path followed by a packet while it is encapsulated. While it is encapsulated,
a packet is routed to a knowledgeable decapsulating agent, which decapsulates the packet and then
correctly delivers it to its ultimate destination.
MAX204SGV4.0
117
Mobile IP Terminology Review continued
Mobile IP Terminology Review
MAX204SGV4.0
118
New Mobile IP Terminology

Mobile IP allows users with mobile devices whose IP addresses are associated with one network to
stay connected when moving to a network with a different IP address. The Mobile IP function (or
client) can be implemented in two ways:
Client Mobile IP (CMIP) - The Mobile IP Client is hosted on the Subscriber Terminal (Operating
System level). This is the generic Mobile IP call processing that you have already studied.
Proxy Mobile IP (PMIP) - The Mobile IP Client is hosted by the network.
From the Home Agents (HA) standpoint,

there is no difference between CMIP and
PMIP.
In the Motorola WiMAX infrastructure, the Subscriber Terminal (ST), Cellular Access Point Controller
(CAPC), the Access Point (AP), and Home Agent (HA) must all be PMIP enabled. The CAPC then
assumes the role of the Mobile Node (generic Mobile IP definition) for the ST and the AP provides the
relay function. The ST does not have to support the Mobile IP client.
Why would we use PMIP instead of CMIP?
Having the MIP client on the ST does not provide any advantage to manage mobility within the
WiMAX network. There is no requirement placed on the ST to provide the Mobile IP client
functionality plus, depending on the type of ST (PDA, laptop, etc.), it is not always possible to install
the MIP client on the device.
MAX204SGV4.0
119
New Mobile IP Terminology continued
New Mobile IP Terminology
MAX204SGV4.0
120
DHCP Address Assignment and Proxy Mobile IP (PMIP)

1
The ST sends a DHCP Discover message to the AP.
The AP sends Mobile IP Registration Request to the CAPC.

This is triggered by the DHCP Discover in Step #1.
CAPC returns Mobile IP Registration Reply to the AP.

Because the AP does not have the security information to generate
ST-HA and/or ST-AAA authentication extension (steps 2 & 3), the AP
has to request the CAPC to generate authentication extension for Mobile
IP Registration Request and to authenticate Mobile IP Registration
Reply.
AP sends Mobile IP Registration Request to the Foreign Agent. Included in this

message is:
Home Agent address
ST MAC address
Network Access Identifier (NAI). This is sent when the ST IP address is not know
(set to all 0s)
The Home Address (HoA). If this is present, this is the ST IP address.
This creates the ST-FA binding. For the rest of this process, we will
assume that the ST IP IS NOT known after the access authentication.
5
Foreign Agent forwards the Mobile IP Registration Request to the Home Agent.
ST IP address is allocated:
The Home Agent MAY have a pool of IP addresses.
The Home Agent MAY request the IP address from a DHCP server.
The Home Agent MAY request the IP address from the AAA server.
Home Agent sends Mobile IP Registration Reply to the Foreign Agent.
Foreign Agent sends Mobile IP Registration Reply to the AP.

Message contains Mobile IP registration lifetime, Home Address
(HoA), authentication extensions, and accept/deny with deny code if
denied.
MAX204SGV4.0
121
DHCP Address Assignment and Proxy Mobile IP (PMIP) continued
MAX204SGV4.0
122

8
9
AP sends a Mobile IP Registration Reply Validity Check Request to the CAPC.

CAPC returns Mobile IP Registration Reply Validity Check Response back to the
AP.
Steps 8 & 9 check the validity of the authentication extensions

generated in Step #3.
10
The AP sends a DHCP Offer message to the ST.

The DHCP Lease Time is derived from the negotiated Mobile IP
Registration Lifetime that was derived during the Mobile IP
Registration Request. The lease is shorter than the Mobile IP
Lifetime as when the lease expires, it will trigger a Mobile IP
registration renewal.
11
The ST sends a DHCP Request (to request the offered parameter) to the AP.
Once an IP address is allocated to the ST, the classification of the two default
service flows could be updated to reflect the ST IP address:
Uplink - source IP address equals to ST IP address
Downlink - destination IP address equals to the ST IP address
The AP delays sending the final DHCP Ack to the ST to avoid IP traffic being
generated by the ST prior to the completion of the end-to-end data path set up.
Before sending DHCP Ack to the ST, the AP updates the ARP table in the STs
default router and the forwarding tables on the L2 devices by sending an ARP
Request message. The associated ARP Reply will be used by the AP as an
acknowledgement of end-to-end data path establishment.
12
The AP sends DHCP Ack to the ST. The ST receives IP address assignment.
MAX204SGV4.0
123
MAX204SGV4.0
124
WiMAX Mobility
Up to now, we have concentrated on gaining entry to the WiMAX network and establishing service
flows. Now that we have established connections, we need to look at what happens when the
Subscriber Terminal (ST) moves about in the system.
Fixed and Nomadic mobility is defined below.
However, we will not discuss them later on in this
section as they do not have the capability to move in
the network.
While Nomadic Mobility does infer that the ST is able

to move, in reality, the ST performs the Network Entry
process we just discussed.
WiMAX Mobility (Access) Modes

This section defines the different WiMAX mobility modes. Generally, the mobility modes available are
dependant on the type of Subscriber Terminal (ST) employed (must be capable of moving) and
carrier provisioning.
Fixed
The Subscriber Terminal is fixed in a single geographic location for the duration of the network
subscription. Fixed access is similar to conventional DSL or cable broadband services that provide
always-on broadband connectivity.
Nomadic Mobility
The Subscriber Terminal is in a fixed geographic location for the duration of the connectivity session.
This allows the flexibility to connect to the network from different points within the network.
Connections are not retained between two network entries. Nomadic access does not require
handover support.
Portable Mobility
Portable Mobility access allows the user to maintain a network data session while the Subscriber
Terminal moves into a different cell and/or sector area, at pedestrian speeds. During the handover
process between cells/sectors, there may be data loss and possibly even more latency and data loss
during inter-subnet handovers. There are is no quality of service guarantees during the handover
process.
Simple Mobility
Simple Mobility access allows the user to maintain a network data session for non-real-time
applications while the Subscriber Terminal moves at mobility speeds of 5 km/h to 120 km/h within the
network coverage area. Handover between cells, sectors and Access Points (AP) provide service
continuity for all non real time applications. The quality of service would be maintained and re-instated
during inter-AP handovers.
Full Mobility
Full Mobility access allows the user to maintain a network data session while the Subscriber Terminal
moves at mobility speeds of 120 km/h speeds or higher within the network coverage area. Guaranteed
handover performance cells, sectors and Access Points (AP) provide service continuity for all
applications. The quality of service is maintained at provisioned levels at all the Access Points.
MAX204SGV4.0
125
WiMAX Mobility Modes continued
Handover Service Class

Fixed Mobility
Nomadic Mobility
Portable Mobility
Simple Mobility
Full Mobility
Mobility Characteristics
Idle Characteristics
Handovers prevented
Idle mode entry supported
Initial network entry and

reselection limited to
home APs neighbors
only.
Inter-PG mobility prevented
Handovers prevented

reselection permitted to
any AP in the Network
Access Providers
(NAP) system
Handovers supported
AP to AP downlink packet
forwarding is not
performed
Inter-PG mobility supported
Handovers supported
forwarding is performed
Handovers supported
Idle mode entry supported,
& ARQ Block
Network re-entry and

home paging groups
neighbors only.

home paging groups
neighbors only.

reselection allowed in
neighboring paging
groups.

neighboring paging
groups

neighboring paging
groups.
WiMAX Mobility Modes
MAX204SGV4.0
126
Active WiMAX Mobility

Below are the different types of handover modes available to an Active WiMAX Subscriber Terminal
(ST). That is, the Subscriber Terminal is in the process of sending and/or receiving data as opposed
to Idle Mode where the ST is listening to the downlink transmissions. Active mobility is known as a
handover while Idle mobility uses the reselection process (see next section).
Inter-sector Handover
An Inter-sector Handover is a handover from one sector to another sector at the same RF site staying
within the same Carrier Access Point Controller (CAPC).
Inter-Access Point (AP) Handover

An Inter-Access Point (AP) Handover crosses between CAPCs. If two sectors at a physical site have
different CAPCs, then a handover between the two sectors would be considered an Inter-AP
handover.
Intra-Foreign Agent (FA) Handover

An Intra-FA Handover is a handover from one CAPC, to another CAPC, belonging to the same
Foreign Agent domain. This type of handover requires only update to the Subscriber Terminals (ST)
Layer 2 (L2) forwarding information.
Inter- Foreign Agent (FA) Handover

An Inter-FA Handover is a handover from one CAPC, to another CAPC, belonging to the two different
Foreign Agent domains. This type of handover requires update to the STs Layer 3 (L3) routing
information in addition to the STs L2 forwarding information.
MAX204SGV4.0
127
Active WiMAX Mobility continued
MAX204SGV4.0
128
Idle WiMAX Mobility

Idle mode is the period of time in which the Subscriber Terminal (ST) receives only intermittent
downlink transmission from the system and yet retains its ability to move throughout the system while
retaining its IP address.
A ST may choose to enter idle mode during periods of data inactivity to conserve its battery resources.
Likewise, a serving AP may choose to move an inactive ST to idle mode in order to conserve its
air-interface resources.
A ST exits idle mode and returns to active mode upon either outbound or inbound data activity for the
ST or when it becomes necessary to reauthenticate.
While in idle mode, an ST is under the administration of a function in the CAPC called the Paging
Controller (PC). The PC, through the use of its Location Register database (LR), is responsible for
tracking the location of idle mode STs and for paging an ST when it is required to re-enter the system
and become active.
A PC controls idle mode STs while those STs reside in an area of coverage represented by a group of
APs the PC manages, called a Paging Group. The coverage of paging groups overlap such that some
APs function in more than a single paging group.
As an idle ST moves from a cell in one paging group to a non-overlapping cell in another paging
group, the PC will transfer its administration of the idle mode ST to the PC that manages the moved-to
paging group (if the PC doesnt manage both).
MAX204SGV4.0
129
Idle WiMAX Mobility continued
Idle WiMAX Mobility
MAX204SGV4.0
130
WiMAX Lease Processes, Handoffs and Ownership

To ensure the Subscriber Terminal (ST) is reachable throughout the WiMAX system, a Lease concept is
employed.
The lease owner is responsible for:
AP ensures the downlink traffic is correctly routed to the ST
CAPC queue traffic for delivery to ST
Leases are exclusive, there is no sharing. A lease can be owned by either an Access Point (AP) that is hosting a
ST while the subscriber is active (or a short time after) or by the lease manager function that resides within the
CAPC while the ST is inactive (idle mode).
A few more Lease definitions:
Paging Controller
Function within the CAPC
Coordinates downlink traffic and paging
Sends paging messages
Location updates
Paging Group
Multiple APs (geographical location)
Can be overlapping
Provisioned/fixed
ST performs location update when it detects it has entered a new Paging Group using information from the
Downlink Channel Descriptor (DCD), i.e. Paging Group ID (PGID).
Basic Lease process as follows:
1. Network Entry At network entry, the lease is conceptually owned by the ST. Once the ST is registered on
the network, the lease is held by the AP.
2. Network Exit Prior to performing an orderly network exit, the CAPC owns the lease (assuming ST is idle).
After power-down, the lease is conceptual owned by the ST.
3. Handover (HO) Completion - This represents the second half of the HO process beginning at the point where
the lease is requested by the target AP from a CAPC.
4. Handover (HO) Start - This represents the first half of the HO process up to the point where the lease is
relinquished by the AP to the CAPC.
5. Location Update - An idle ST moves between paging areas owned by different CAPCs, the ownership of the
lease will transfer from one CAPC to another.
6. Lease Hold Timer expiration - Once a mobile transitions to idle mode and after an additional Lease Hold
seconds, the lease is transferred from the AP to the CAPC.
7. Network Exit - Prior to performing an orderly network exit, the AP owns the lease (assuming ST is active).
After power-down, the lease is conceptual owned by the ST.
8. Active - The ST originates uplink or receives downlink data. Prior to sending/receiving data, the lease was
held by the CAPC. Once connections are set-up, the lease is owned by the AP.
MAX204SGV4.0
131
WiMAX Leases continued
WiMAX Leases
WiMAX Leases
MAX204SGV4.0
132
Side-haul traffic and QoS in Call Management

To ensure that the QoS requirements for the subscriber data are met and sustained within the ASN network the
concept of side-haul traffic has been implemented.
Side haul traffic is the user data which is stored for forwarding to the subscriber upon re-entry to the network from
an idle state or while transitioning from Access Point to Access Point during active mobility.
In order to maintain Class of Service handling of the data and ensure that real-time and non-real time data flows
are maintained without loss of data, user data will be buffered and forwarded from network element to network
element during reselection and handover processes. The resultant data forwarding will allow the user traffic to
be downloaded to the MSS in proper sequential order and in a timely enough fashion to meet the demands of
QoS parameters established within the system.
Both Service Flow Classification and QoS will determine whether the data is to be side-haul forwarded during
mobility or if the data should simply be discarded.
Under the requirements of Simple Mobility only non-real-time data can be stored and forwarded in a timely
enough manner to meet stated requirements for that service.
To support Full Mobility, real-time data as well as non-real-time data will be stored and side-haul forwarded in a
timely manner. The real-time data, however will be forwarded at a higher priority and therefore more quickly than
the non-real-time data. Neither of those data types will be discarded in the process.
During Portable, Nomadic, or Fixed Mobility, no data will be side-haul stored and forwarded during relocation from
place to place within the system.
MAX204SGV4.0
133
Side-haul traffic and QOS in Call Management
Access
Service Network
(ASN)
NTP
EMS
DNS
L2/L3/FA
Gateway
Foreign Agent
AP
Transport
Between
ASN & CSN
MSS/CPE
DHCP
CAPC
AP
AAA
Previous Bearer Traffic Path

Current Bearer Traffic Path
Sidehaul Traffic Path

Sidehaul Traffic Flows
MAX204SGV4.0
134
Leases Idle Mode Entry ST Initiated

Initial Conditions:
AP1 holds the lease for the ST
ST has been inactive and triggers an Idle Mode entry request
Idle Mode Entry ST Initiated

1
ST sends a de-registration request (DREG-REQ) to the AP.
AP receives DREG-REQ and forwards request to the Paging Controller (CAPC)

Message includes ST information from the AP which is stored at the
CAPC to shorten re-entry time.
Paging Controller (CAPC) sends a message back to AP granting Idle Mode entry.
AP sends de-registration command to ST.

Message includes Paging Group ID (PGID), Paging Controller ID
(PCID), paging offset and paging cycle.
At this point, the AP holds the lease for a configured period of time after
the ST goes into Idle Mode. This is to ensure that no traffic is destined
for the ST prior to it releasing the lease.
AP sends a Release Lease Request to Paging Controller (CAPC)
The CAPC updates its L2 switching routing tables and sends this information out the
network.
All routes are updated to point to the CAPC (paging controller) instead
of the AP for destination address for packets.
The Paging Controller sends the Release Lease Response to the AP which then
relinquishes the lease.
MAX204SGV4.0
135
MAX204SGV4.0
136
Intra-CAPC, Intra-Router/FA Handover

Initial conditions:
AP1A is the serving AP
AP1B is the target AP
AP1A holds the lease from CAPC1
AP1A provisioned with Router/FA1 address

1
ST receives a neighbor advertisement message.

Learn the triggers for the serving AP
Learn preamble and channel descriptions (DCD) of neighboring APs
1a/b
These steps are only performed if target APs are on different frequencies than
serving AP.
These messages allow the ST to scan the neighbors.
2/3
4
5/6
7
Sync and measure downlink characteristics of AP2 & 3.

ST requests to move to AP3.
AP1A triggers a refresh and acknowledgement of the L2 switch routing (resets timer).
AP1A sends a Handover prepare message to AP1B.
This message contains the STs information.
AP1B sends CAPC1 message requesting STs information.

In order to process the handover, AP1B must check the validity of the
request. In order to do that, it must have the STs security information.
It requests this information from the CAPC1.
CAPC sends ST information to AP3.

The AP will now validate the handover request using the security
information provided by the CAPC1.
10
AP1B sends a handover accept message to AP1A.

This message contains the handover ID (HO_ID) that accelerates the
re-entry process by providing a pre-specified slot at the target AP.
MAX204SGV4.0
137
Intra-CAPC, Intra-Router/FA Handover continued
MAX204SGV4.0
138
Intra-CAPC, Intra-Router/FA Handover - continued

11
AP1A sends a Handover Commit message, containing the STs ID to AP1B.
12
AP1A sends a move to AP1B message to the ST.
13
AP1A sends a HO advise message to AP1B containing the STs ID, Handover ID,
and the frame offset for the ST.
14
AP1A sends UL allocation information (where to look for target AP UL-MAP) to the
ST
15
ST sends Handover Indication message to AP1A containing target APs ID.
16
Fast ranging is a non-contention based Information Element that allows the ST to

send the required Registration Request (REG-REQ) in Step 17.
This message contains the STs information (context)
16a/b
Steps taken if ST aborts handover. MOB-HO-IND indicates that to AP

MOB-HO-IND informs AP1A that the ST no longer wishes to move to
AP1B
HO Commit (cancel) informs AP1B that the ST is no longer moving
and to cancel UL opportunity and unreserved resources allocated
to the ST.
MAX204SGV4.0
139
MAX204SGV4.0
140

17
ST sends ranging request to AP1B (normal ranging procedures)
18
AP1B requests the STs lease from CAPC1.
19
CAPC1 revokes the STs lease on AP1A.
20
AP1B send ranging response back to ST.
21
ST internal processing is complete. ST is ready to accept downlink data.
22
AP1B sends downlink data to ST.
23
ST sends uplink data to AP1B.
24
CAPC1 grants the STs lease to AP1B.

This is the response from Step 18.
25
AP1B updates its L2 switching/routing tables and sends this information out the
network (router/FA).
AP may need to buffer data until L2 bearer path is set-up.
MAX204SGV4.0
141
MAX204SGV4.0
142

26
AP1A acknowledges it no longer holds the lease for the ST.

This is the response from Step 19.
27
AP1B informs AP1A to release the STs resources
MAX204SGV4.0
143
MAX204SGV4.0
144
Student Activity - Call Setup Processes

At this point we should have a relatively good idea of what nodes will be involved in a normal
sequence of events for establishing and maintaining connectivity for a couple of different scenarios.
We have looked at the types of exchanges that have to take place during call setup and mobility.
Now we will take this a step further and explore other call process scenarios.
During this exercise, students will be given a series of different scenarios and will be asked to work
through and note the steps required to set up and support the call. This will include all of the
message exchanges between the network nodes as well as the MSS.
Students will need to break up into groups and work with 3-4 team members to accomplish this
activity.
Each team will be given task sheets with sets of initial assumptions related to their working
scenario(s) and blank ladder diagrams. From these opening assumptions, the teams each need to
work through and diagram the sequence of message exchanges representing the call flow process
for their given scenario start to finish, attempting to list out as many of the steps as they can think of.
At the end of this student activity, each team will be asked to present their findings to the class for
open discussion.
MAX204SGV4.0
145
Student Activity Call Flow Processes Team 1
Re-entry from Idle Mode - Outbound Data (serving AP holds lease)

Initial Conditions:
ST is in Idle Mode in fixed location (AP1)
AP1 holds the lease
Data originates from the CSN network and needs to go to the ST
AP1
AP2
AP3
L2
SWITCH
CAPC
PC1
CAPC
PC2
ROUTER
/FA1
ROUTER
/FA2
AAA
MAX204SGV4.0
HA
146
AP1
AP2
AP3
L2
SWITCH
CAPC
PC1
CAPC
PC2
ROUTER
/FA1
ROUTER
/FA2
AAA
MAX204SGV4.0
HA
147
Re-entry from Idle Mode - Outbound Data (non-serving AP holds lease)

Initial Conditions:
ST entered Idle Mode from AP1
AP1 still holds the lease
ST roamed to AP3 (AP3 is in same paging group)
AP1
AP2
AP3
L2
SWITCH
CAPC
PC1
CAPC
PC2
ROUTER
/FA1
ROUTER
/FA2
AAA
MAX204SGV4.0
HA
148

continued
AP1
AP2
AP3
L2
SWITCH
CAPC
PC1
CAPC
PC2
ROUTER
/FA1
ROUTER
/FA2
AAA
Re-entry from Idle Mode - Outbound Data (non-serving AP holds lease) continued
MAX204SGV4.0
HA
149
Re-entry from Idle Mode - Outbound Data (PC holds lease)

Initial Conditions:
ST is in Idle Mode
PC1 holds the lease
AP1
AP2
AP3
L2
SWITCH
CAPC
PC1
CAPC
PC2
ROUTER
/FA1
ROUTER
/FA2
AAA
MAX204SGV4.0
HA
150
Re-entry from Idle Mode - Outbound Data (PC holds lease) continued
AP1
AP2
AP3
L2
SWITCH
CAPC
PC1
CAPC
PC2
ROUTER
/FA1
ROUTER
/FA2
AAA
Re-entry from Idle Mode - Outbound Data (PC holds lease)
MAX204SGV4.0
HA
151
AP1
AP2
AP3
L2
SWITCH
CAPC
PC1
CAPC
PC2
ROUTER
/FA1
ROUTER
/FA2
AAA
MAX204SGV4.0
HA
152
Inter-CAPC, Inter-Router/FA Handover

Initial conditions:
Subscriber is active
AP1A is the serving AP and holds the lease from CAPC1
AP2A is the target AP
AP
1A
AP
2A
AP
1B
L2
SWITCH
ROUTER
/FA1
ROUTER
/FA2
CAPC1
CAPC2
MAX204SGV4.0
AAA
153
Inter-CAPC, Inter-Router/FA Handover continued
AP
1A
AP
2A
AP
1B
L2
SWITCH
ROUTER
/FA1
ROUTER
/FA2
CAPC1
CAPC2
MAX204SGV4.0
AAA
154
AP
1A
AP
2A
AP
1B
L2
SWITCH
ROUTER
/FA1
ROUTER
/FA2
CAPC1
CAPC2
MAX204SGV4.0
AAA
155
AP
1A
AP
2A
AP
1B
L2
SWITCH
ROUTER
/FA1
ROUTER
/FA2
CAPC1
CAPC2
MAX204SGV4.0
AAA
156
AP
1A
AP
2A
AP
1B
L2
SWITCH
ROUTER
/FA1
ROUTER
/FA2
CAPC1
CAPC2
MAX204SGV4.0
AAA
157
AP
1A
AP
2A
AP
1B
L2
SWITCH
ROUTER
/FA1
ROUTER
/FA2
CAPC1
CAPC2
MAX204SGV4.0
AAA
158
Re-entry from Idle Mode Inbound Data (Serving AP)

Initial Conditions:
Subscriber is in Idle mode.
Subscriber needs to become active and send data.
AP1 is the last known Serving AP and is closest but does not hold the lease when the inbound event
occurs.
AP1
AP2
AP3
L2
SWITCH
CAPC
PC1
CAPC
PC2
ROUTER
/FA1
ROUTER
/FA2
AAA
MAX204SGV4.0
HA
159
Re-entry from Idle Mode Inbound Data (Serving AP) continued
AP1
AP2
AP3
L2
SWITCH
CAPC
PC1
CAPC
PC2
ROUTER
/FA1
ROUTER
/FA2
AAA
Re-entry from Idle Mode Inbound Data
MAX204SGV4.0
HA
160
Re-entry from Idle Mode Inbound Data (non-Serving AP)

Initial Conditions:
Subscriber is in Idle mode.
Subscriber needs to become active and send data.
AP 3 is closest but is not the last known Serving AP. AP3 requires the lease when the inbound event
occurs.
AP1
AP2
AP3
L2
SWITCH
CAPC
PC1
CAPC
PC2
ROUTER
/FA1
ROUTER
/FA2
AAA
MAX204SGV4.0
HA
161
Re-entry from Idle Mode Inbound Data (non-Serving AP) continued
AP1
AP2
AP3
L2
SWITCH
CAPC
PC1
CAPC
PC2
ROUTER
/FA1
ROUTER
/FA2
AAA
Re-entry from Idle Mode Inbound Data
MAX204SGV4.0
HA
162
Inter-Paging Group Mobility in Idle Mode

Initial Conditions:
ST is in Idle Mode and CAPC1 owns the lease
ST moves to AP2
A MIP binding exists in CAPC1 (moved-from system)
Data flows from HA-FA1 to lease owner CAPC1
AP2 requires the lease and CAPC2 requires the MIP binding.
AP2, CAPC2 and FA2 are part of a different ASN network.
AP 1
CAPC2
ROUTER
/FA2
AP 2
CAPC1
ROUTER
/FA1
AAA
Different
L2 Networks
MAX204SGV4.0
HA
163
Inter-Paging Group Mobility in Idle Mode continued
AP 1
CAPC2
ROUTER
/FA2
AP 2
CAPC1
ROUTER
/FA1
AAA
Different
L2 Networks
Inter-Paging Group Mobility in Idle Mode
MAX204SGV4.0
HA
164
Trouble Shooting Considerations for Call Setup

At this point we should have a relatively good idea of what is a normal sequence of events for
establishing and maintaining connectivity for a variety of different scenarios.
Having discussed the seven steps involve in the Network Entry process and having walked through
the step by step process of call setup in the network let now consider the issue of troubleshooting
this environment.
Essentially, we have three different areas of the network environment to work with: the Air Interface
(WiMAX), the ASN network that we are trying to establish connectivity through, and the CSN
network that we are trying to obtain services from.
It is very important when troubleshooting, to be completely aware of what stage of connectivity we
are in, what the procedures are for each step, as well as which nodes are involved. This is why it
is important to be utterly familiar with the ladder diagrams we were discussing in the previous
section.
With that information, a list of symptoms, a good network baseline and an organized plan of
approach, trouble shooting should be a relatively straight forward process.
As for an organized plan of approach, the following steps are generally recommended:
1. Compile a list of all symptoms take stock of all alarms and indications.
2. Try to evaluate if the symptoms indicate that the system is actually broken compare the
symptoms gathered to your baseline
3. Try to determine whether the symptoms are isolated to a single user, set of users, or a given
area of the network.
4. Take time to consider the symptoms and (given your knowledge of the system at this point,)
create one or more working hypotheses of what could be causing the problem. Write these
down!
5. Create a plan for testing each hypothesis in order of likelihood. These plans should consist of
steps that will either confirm of negate the possibilities.
6. Test each hypothesis thoroughly and run each plan completely keeping a log of all steps
performed.
7. If a step performed seems to correct the problem, undo the step if possible and go back and
recreate the problem to make sure that what was done was the actual resolution and not merely
coincidence.
8. If the resolution has been found log the steps taken to correct the problem.
9. If all of the hypothesis have been thoroughly tested and proved incorrect start again at step
#1.
For an efficient approach to troubleshooting, various methods of have been proposed depending on
the nature of the symptoms seen. For example, if the problem seems to be isolated to a specific
user, the top-down approach often works best starting with factors involved in user login and
applications. If the symptoms point to a larger population of users and seems to perhaps be physical
media or network related then the bottom up approach of looking for media related issues may be the
best approach. The divide and conquer approach is often used in situations where it is unclear what
area of the process or network is breaking down and therefore needs a two-pronged attack approach.
Whatever the approach, it is first necessary to know what is normal and start from there by first
assessing the situation and determining if the system is indeed broken.
MAX204SGV4.0
165
Trouble Shooting Considerations continued
Troubleshooting Information Points

LMTs and
Discovered
Users
NTP
Access
Service Network
(ASN)
EMS
User
Interface and
commands
DNS
Gateway
Foreign Agent
L2/L3/FA
MSS/CPE
AP
Transport
Between
ASN & CSN
(CSN)
AP LMT and
CLI commands
CAPC LMT,
User Database
and Message
Traces

Information Sources for
testing and trouble shooting
Host Table
DHCP
CAPC
AAA
(CSN)
User Database
and Profiles on
support nodes:
AAA, DNS, DHCP
MAX204SGV4.0
166

When troubleshooting an environment it is important to keep in mind what types of indications are
available to show what has been successful versus unsuccessful and also to be aware of different
locations where information might be obtained regarding the status of the nodes and processes
involved.
On the following table are listed some basic parts of the Registration and Call Flow Process.
Included are some of the activities that should take place for each of these processes as well as a list
of indications and information that should show the status of each process.
Initial Ranging
CPE should see CIDs for

Basic and Management
Channels
AP should show a
connection and CIDs to
CPE in the LMT interface
Should see the start of the

Authorization process
A protocol trace of the

WiMAX interface would
show this activity.
These messages should be

seen in a protocol trace at
the core switch
AP sends message to CAPC to start

the EAP authentication process.
CAPC requests ST identity from AP
AAA sends accept success to CAPC
CAPC stores information and also

sends to AP/ST
AP starts three-way SA-TEK
exchange with ST
Subscriber registration
attempt should be seen at
the AAA server logs
during exchange
Trace at core switch, Port

Mirror on CAPC and filter
on MAC address, also Filter
on AP and CAPC IP address
and user FQDN
Click on Message Trace in
CAPC LMT
show this activity
RNG-RSP from AP contains time

and power corrections, ranging code
attributes (which code, where
received), status = success
RNG-RSP from AP contains ST
MAC Address and Basic and
Primary Management CIDs
User interface commands

should be used to verify
Click on View Connected
MSs
Print_MMS_STATS
command at AP CLI
Negotiation messages exchanged

between MSS and AP. Successful
negotiation = Go to next step in
network entry
processAuthorization
CAPC should show

subscriber in Contextual
Database
MAX204SGV4.0
167

Registration
REG-REQ to AP includes
information such as IP version,
vendor specific information, number
of UL CIDs support, ST
management support, etc.
Establish Initial Service flows (2)
that will be used UL and DL
Should see Service Flow

IDs associated with
Transport CIDs.

To connect to the Site
Controller via CLI
o /usr/app/bin/demon
command will
allow access
To Dump Flows belonging
to a particular subscriber
o Type sfm get
pending X Y
o Type sfm get
committed X Y
To Dump general subscriber
information
o Type sfm get
mob X Y
Note: in both sets of commands X=
SSID and Y= Sector ID
Should see Subscriber

MAC address in the
DHCP Host Table
Show hosts in DHCP server

will show MAC and
assigned IP address pair
DHCP Messages should

be see in protocol trace at
the Core Switch At the
AP the DHCP
Transaction Log will log
final status of last 100
DHCP messages sent
cat
/tmp/dhcp_transactions.tx
t command will show these
messages
LMT interface click on

Dump ARP Cache
Subscriber should see an

IP address assigned.
CPE interface commands to

check IP configuration
The IWF Interrupts at the

AP should be ARPing on
behalf of the CPE
The cat
/proc/interrupts command
should show and entry for:
Iwf_ext7
At the DHCP Server

DHCP messages are
logged
The /var/log/ directory can

be accessed for these
message logs
Failure of the DHCP

server will appear at the
EMS
Looking at Alarms at the

EMS will show this
DHCP for Fixed/Nomadic Clients
The AP forwards the DHCP

Discover message to the local DHCP
server.
The AP relays DHCP server reply
with the DHCP Offer containing the
IP addressing information.
The ST sends a DHCP Request
which is forwarded by the AP to the
local DCHP server.
An IP address is allocated to the ST,
and the classification of the two
default service flows is updated to
reflect the ST IP address
The ST receives IP address
assignment.
MAX204SGV4.0
168

DHCP Address Assignment and Proxy Mobile IP (PMIP
The AP forwards the Mobile IP

Registration Request initiated by a
DHCP Discover message to the CAPC
CAPC returns Mobile IP Registration
Reply to the AP.
AP sends Mobile IP Registration
Request to the Foreign Agent
This creates the ST-FA binding
Foreign Agent forwards the Mobile IP
Registration Request to the Home Agent.
Home Agent sends Mobile IP
Registration Reply (with ST IP address
allocation) to the Foreign Agent.
Foreign Agent sends Mobile IP
Registration Reply to the AP.
AP and CAPC exchange Mobile IP
Registration Reply Validity Check
messages
The AP sends a DHCP Offer message to
the ST
The ST receives IP address assignment.
Mobile IP Registration
messages between AP,
CAPC, and FA should be
seen in a protocol trace at
the core switch.
ST-FA binding should be
seen in the FA
Mirror CAPC attached port

and filter on AP IP and CAPC
IP
Clicking on Message Trace

in the CAPC LMT will show
these messages
Show and Debug Mobile IP

Commands can be used to
access this information
Mirror FA attached port and

filter on FA IP and AP IP
address.
HA-FA binding should be

seen n the FA
These message exchanges

should be seen in a protocol
trace at the core switch
Subscriber should see an IP

address assigned.
CPE interface commands to

check IP configuration
The IWF Interrupts at the

AP should be ARPing on
behalf of the CPE
The cat /proc/interrupts

command should show and
entry for: Iwf_ext7
At the DHCP Server DHCP

messages are logged
Failure of the DHCP server

will appear at the EMS
The /var/log/ directory can be

accessed for these message
logs
Looking at Alarms at the

EMS will show this
MAX204SGV4.0
169
Student Activity - Trouble Shooting Considerations

In this next activity, students will be asked to revisit the call setup scenarios presented earlier and
analyze them with an eye toward possible problems which might occur and their related symptoms.
Students will be asked to present possible ways in which they could gather symptoms as well as
different ways to approach troubleshooting the possible error situations given.
The object of this activity is to think of locations in the network where the Call Flow Process might
break down. You should also be looking at where information might be obtained as to the status of
the Call Flow Process at any given point in the scenario and what indicators would show success or
failure of that process.
Access
Service Network
(ASN)
1- Initial Ranging and Registration Request

2- Exchange of SS/MSS information
3- DNS lookup of USER@REALM
4- AAA proxy Radius exchange with Home AAA
5- FA to HA binding
6 SS/MSS lookup in Home AAA
7- IP address assignment from Home DHCP
Connectivity
Service Network
(CSN)
NTP
EMS
DNS
DHCP
DNS
Server(s)
L2/L3/FA
AP
MSS/CPE
192.168.2.x
Assigned IP for CPE
Held by AP or CAPC
Registration
CAPC
Transport
Between
ASN & CSN
64.150.2.x
Gateway
Router/HA 6
Foreign Agent 5
DHCP
AAA
192.168.2.x
AAA
VoIP
Server

background interactions to
support CPE registration
MAX204SGV4.0
170
Student Activity - Trouble Shooting Considerations continued

How do we know
when this is
successful?
What indicators
can we look for?
Where?
What nodes are

involved?
Scanning for
Channels
Ranging
Capability
Negotiation
Authorization
Registration
IP Connectivity
Service
Establishment
Re-entry from Idle

Mode
Intra ASN
Handover
MAX204SGV4.0
171
Types of Mobility Review for Troubleshooting Considerations
Idle WiMAX Mobility

As stated earlier in this chapter - Idle mode is the period of time in which the Subscriber Terminal (ST)
receives only intermittent downlink transmission from the system and yet retains its ability to move
throughout the system while retaining its IP address.
A ST or its AP may choose to have the MSS enter idle mode during periods of data inactivity to
conserve resources. A ST exits idle mode and returns to active mode upon either outbound or
inbound data activity for the ST or when it becomes necessary to reauthenticate.
While in idle mode, an ST is under the administration of a function in the CAPC called the Paging
Controller (PC). The PC, is responsible for tracking the location of idle mode STs and for paging an
ST when it is required to re-enter the system and become active.
As an idle ST moves from a cell in one paging group to a non-overlapping cell in another paging
group, the PC will transfer its administration of the idle mode ST to the PC that manages the moved-to
paging group (if the PC doesnt manage both).

Depending upon where the MSS is moving during the call process there are different types of
handover modes available to an Active WiMAX Subscriber Terminal (ST). That is, the Subscriber
Terminal is in the process of sending and/or receiving data as opposed to Idle Mode where the ST is
listening to the downlink transmissions. Active mobility is known as a handover while Idle mobility
uses the reselection process (see next section).
Inter-sector Handover
An Inter-sector Handover is a handover from one sector to another sector at the same RF site staying
within the same Carrier Access Point Controller (CAPC).
Inter-Access Point (AP) Handover

An Inter-Access Point (AP) Handover crosses between CAPCs. If two sectors at a physical site have
different CAPCs, then a handover between the two sectors would be considered an Inter-AP
handover.
Intra-Foreign Agent (FA) Handover

An Intra-FA Handover is a handover from one CAPC, to another CAPC, belonging to the same
Foreign Agent domain. This type of handover requires only update to the Subscriber Terminals (ST)
Layer 2 (L2) forwarding information.
Inter- Foreign Agent (FA) Handover

An Inter-FA Handover is a handover from one CAPC, to another CAPC, belonging to the two different
Foreign Agent domains. This type of handover requires update to the STs Layer 3 (L3) routing
information in addition to the STs L2 forwarding information.
MAX204SGV4.0
172
Types of Mobility Review for Troubleshooting Considerations

Other considerations of mobility which must be included in troubleshooting include the concept of the
different levels of mobility and what services are required to support successful data flows during
handovers or idle mode. Here again we see our chart of Mobility Types:
Handover Service Class

Fixed Mobility
Nomadic Mobility
Portable Mobility
Simple Mobility
Full Mobility
Mobility Characteristics
Idle Characteristics
Handovers prevented

reselection limited to home
APs neighbors only.
Handovers prevented

reselection permitted to any
AP in the Network Access
Providers (NAP) system
Handovers supported
forwarding is not performed
Handovers supported
Handovers supported
Idle mode entry supported,
AP to AP downlink packet &

ARQ Block forwarding is
performed

paging groups neighbors
only.

paging groups neighbors
only.

neighboring paging groups.

neighboring paging groups

neighboring paging groups.
MAX204SGV4.0
173
Mobility Trouble Shooting Considerations

In this area of troubleshooting it may be assumed that the subscriber has successfully registered on
the network and is either in process of a call and handing over from one AP to another, or attempting
to send or receive a new data after going idle for a period of time.
To perform successful troubleshooting at this point we must recall the message exchanges we
described earlier in the chapter when we studied, the call flow processes for a variety of scenarios.
Looking at those processes again, we need to consider how we would know that the steps performed
in support of the call were successful and where in the network environment we would check for
information regarding call flow status.
On the following table are listed some basic parts of the Call Flow and Handover Process. Included
are some of the activities that should take place for each of these processes as well as a list of
indications and information that should show the status of each process.
ST sends a de-registration request

(DREG-REQ) to the AP which is then
forwarded to the Paging Controller in the
CAPC.
Paging Controller (CAPC) sends a message
back to AP granting Idle Mode entry.
AP sends de-registration command to ST.
AP and Paging Controller (CAPC)
exchange Release Lease messages
Message exchanges
should be seen in
protocol trace at
Core Switch
CPE status should

be seen as Idle at
AP LMT interface
CPE should go into

Idle Mode

Mirror on CAPC
switchport and filter on
AP, CAPC and user IP
and MAC addresses.
Click on Message Trace

in CAPC LMT.

show this activity


Mirror on CAPC
switchport and filter on
AP, CAPC and user IP
and MAC addresses.
Click on Message Trace

in CAPC LMT.

handover and new AP ID
Click on View Connected

MSs
Print_MMS_STATS
command at AP CLI
show this activity
Intra ASN Handover
ST requests to move to AP3.

AP1A sends a Handover prepare message to
AP1B.
AP1B sends CAPC1 message requesting
STs information.
CAPC sends ST information to AP3.
AP1B sends a handover accept message to
AP1A.
AP1A sends a Handover Commit message,
containing the STs ID to AP1B.
AP1A sends a move to AP1B message to
the ST.
AP1A sends a HO advise message to AP1B
containing the STs ID, Handover ID, and
the frame offset for the ST.
AP1A sends UL allocation information
(where to look for target AP UL-MAP) to
the ST
ST sends Handover Indication message to
AP1A containing target APs ID.
Message
exchanges should
be seen in protocol
trace at Core
Switch
Should see AP1B

ID at CPE
Should see CPE ID

at AP1B LMT
interface
MAX204SGV4.0
174
Test Equipment for Trouble Shooting

A list of various test equipment has been recommended for troubleshooting in this environment.
This test equipment is in addition to any alarm and event information obtainable from system nodes
in the ASN or CSN networks. It is also in addition to any information obtainable directly from the
user interface of the MSS.
For our purposes here, the two types of test equipment that we would be using to troubleshoot
issues of call processes would be the LAN/WAN Analyzer and Ethereal. Both would be
implemented in this environment as a means of looking at the message exchanges required during
our Call Process.
AP LMT
Capture communications between the CPE and

DAP and view CPE connectivity status
CAPC LMT and Database
Look for subscriber entry in contextual

database
EMS
Look for Subscriber entry in topology tree
LAN/WAN Analyzer
Real time data collection and analysis of

messages between network nodes and between
networks.
Ethereal Analyzer
Network protocol analyzer. Real time data

collection and analysis. Capture message
exchanges between network nodes.
Note: Ethereal (now Wireshark) can be

found at www.wireshark.org
MAX204SGV4.0
175
Test Equipment for Trouble Shooting continued
Access
Service Network
(ASN)
LMTs and
Discovered
Users EMS
NTP
DNS
AP LMT
Ethereal
LAN/WAN Analyzer
Gateway
Foreign Agent
L2/L3/FA
MSS/CPE
User Interface
AP
CAPC LMT
and User
Database
Transport
Between
ASN & CSN
(CSN)
Host Table
DHCP
CAPC
AAA
(CSN)

test points and applicable tools for
testing and trouble shooting
User Database
and Profiles
MAX204SGV4.0
176
Analysing Protocol Traces

Although not a first method of attack when troubleshooting, protocol traces can be invaluable in determining
the true source of errors in a network environment. Using tools such as a Sniffer, Ethereal, Wireshark or even
equipment associated trace files and logs as well as de-bugging functions can provide access to message
exchanges between network nodes.
When using a de-bug function or a trace file, setting up a capture may be as simple as turning on that particular
function. Although these tools will not give the control and filtering options of a protocol analyzer they do
render access to the same types of message exchanges in most cases. The thing to keep in mind regarding
de-bug and trace functions performed by a network node, is that such activity may be resource intensive from the
perspective of the network node itself. Also be aware that those tools can only give access to information
going to and from that particular node.
When using a tool such as Protocol Analysis software, setting up the capture may require a little more
preparation (such as setting up port mirroring) but is only resource intensive to the analyzer and the switch port it
is attached to.
Generally speaking, protocol traces are gathered from a centralized point in the network, such as the core or
aggregate switches. Port Mirroring will be required in order to see the information going to or from the
nodes that are being analyzed. Port Mirroring tells the switch to echo to the Sniffer attached port any data
going to or from the node being monitored. Port Mirroring will have to be configured from the administrator
interface of the switch and should only be enabled long enough to gather the data needed due to the amount of
resource utilization required.
Taking what we know about the Registration and Call Flow Processes we now should have a very good idea of
the sequence and types of protocol messages being sent between the network nodes. By looking at the message
exchanges captured by the protocol analyzer and comparing what we know with what we see captured in our
trace files we can then try to determine if a protocol error may be the source of the problem we are
troubleshooting. The sequence of events seen in the trace should match precisely with the message exchanges
we have discussed, if they do not, that breakdown in the sequence of events should point to the problem at hand.
MAX204SGV4.0
177
Analysing Protocol Traces - continued
Wireshark User Interface

To capture data using a protocol analysis tool like Ethereal or Wireshark, the data must be accessible by the
analyzer. Therefore it is necessary to be physically attached to the same network as the node sending or
receiving data and configure the analyzer to capture data through the port attachment connected to that network.
As mentioned before, when attaching to a LAN switch, it will also be necessary to mirror the data to the
switch-port the analyzer is attached through given the fact that each switch-port is in effect a separate physical
LAN.
MAX204SGV4.0
178
Analysing Protocol Traces - continued
Here is an example of a Wireshark capture filter looking for MAC addresses, IP addresses or other specific
protocols.
To look for information relevant to the problem we are troubleshooting, it is usually necessary to filter on the
MAC layer or IP layer addresses of the nodes involved in the exchange. It is also a good idea to limit the
capture period to a short timeframe directly involved with the exchange that is being trapped in order to avoid
having to search through hundreds of frames of non-related information from the same nodes.
MAX204SGV4.0
179
Sample DNS Look-Up trace file

The following trace file has captured a DNS Look-up exchange.
In this example we see that the sequence of messages is to place a broadcast message onto the local network
looking for a DNS server address and then follow that protocol exchange with a sequence of messages intended
to query the discovered DNS server for the information required to be looked up.
In this particular exchange sequence, however, we see a functional error It this case, it is apparent from the
ICMP (Internet Control Message Protocol) error message sent, that the DNS service is not actually running on
the IP node which should be providing that service!
Such errors are common within the network environment we are troubleshooting and it is necessary to know
what to look for that is normal as well and indicators of a protocol failure such as the circumstance seen here.
MAX204SGV4.0
180
Sample DHCP Address Assignment trace file

The following is an example of the message exchange found in a DHCP Relay environment for an
address assignment of a subscriber.
This message exchange is fairly straightforward and follows much the same message exchange
sequence that we saw in our Call Flow Process ladder charts.
We see the DHCP address assignment request go out on the network, followed by responses from
the DHCP server containing the subscriber address assignment and lease information. This in turn is
followed by an acknowledgement from the subscriber accepting the assigned address and lease.
Recall that this type of message exchange sequence could also be viewed from other points in the
network It could, for example, be brought up in the transaction log of the DHCP server itself or
viewed in a message trace file of a supporting network node such as an AP or CAPC.
MAX204SGV4.0
181
User Registration Traces
MAX204SGV4.0
182
Analysing Protocol Traces
MAX204SGV4.0
183
Student Activity - Call Process Troubleshooting

At this point students should have a detailed knowledge of the normal sequence of events for
establishing and maintaining connectivity within the ASN for the different Call Process scenarios.
We have looked at the types of exchanges that have to take place during call setup and mobility.
Now we will take this a step further and work with our knowledge of troubleshooting considerations
for call processes.
Students will need to break up into groups and work with 3-4 team members to accomplish this
activity.
Each team will be given a series of different troubleshooting problems. On the task sheets for each
group will be initial network assumptions and symptoms related to their working scenario(s). From
the information given, the teams each need to determine the most efficient means by which to
approach the problem. In troubleshooting they will need to work through and list the test points and
tools they would use to troubleshoot the scenario(s) given, what they are looking for, what they
expect to see, and also how they would verify each item tested.
To successfully accomplish this they will have to have a thorough understanding of the steps
involved in the call setup process and how to tell if the step is successful or not. This will include all
of the message exchanges between the network nodes as well as the MSS.
At the end of this student activity, each team will be asked to present their findings to the class for
open discussion.
MAX204SGV4.0
184
Student Activity Troubleshooting scenarios Team 1

Instructions:
The following are the symptoms for the trouble scenarios for your group. Your teams task is to
review the information you have learned and try to deduce what the probable fault is and how you
would test for it within this system. The object of this task is to resolve the problem utilizing the most
efficient approach possible. Please include:
What node you would connect to or check from to gather information regarding the fault.
Where would you check first, next, etc. to troubleshoot in the most effective manner possible.
What would you check for in order of precedence First, next, etc.
How you would check what steps you would perform or commands you would use to gather
information.
And what you would expect to see, regarding errors, alarms, feedback, etc. at the location you
are accessing.
Once your group has defined a testing plan, check with the instructor for additional information and
potential test results.
Upon completion of each problem check with your instructor to verify your answers.
Your team will be given approximately 40 minutes to troubleshoot the assigned scenarios.
MAX204SGV4.0
185

Problems and Symptoms:
Problem 1
User calls with complaint that they are not able to access web browsing. Service worked before, they
are on a VoIP call currently, and they state that they have made no configuration changes since last
time they accessed the web.
Network Assumptions:
This is a not new installation
The Physical RF network is operating correctly
Symptoms:
1. VoIP calls work
2. User can not browse the Web
List where
you would
check for
this error
(in priority
order):
What are you

verifying?
What Commands or
Steps would you use
at this location?
What would you

expect to see as
information or
Feedback presented
for each of these
commands or steps?
Additional notes
or next steps:
MAX204SGV4.0
186

List where
you would
check for
this error
(in priority
order):
What are you

verifying?
What Commands or
Steps would you use
at this location?
What would you

expect to see as
information or
Feedback presented
for each of these
commands or steps?
Additional notes
or next steps:
Probable Fault:
MAX204SGV4.0
187

Problem 2
Some users are calling with complaints that they are not able to access the network to place calls or
send data. Service worked before and they state that they have made no configuration changes
since last time they accessed the network. Other users who have service from the same network and
are already connected do not seem to be affected.
Symptoms:
1. Affects only users connecting through the same network
2. Affects all new registrations and Multiple Subscribers
3. Mobility not affected
List where
you would
check for
this error
(in priority
order):
What are you

verifying?
What Commands or
Steps would you use
at this location?
What would you

expect to see as
information or
Feedback presented
for each of these
commands or steps?
Additional notes
or next steps:
MAX204SGV4.0
188

List where
you would
check for
this error
(in priority
order):
What are you

verifying?
What Commands or
Steps would you use
at this location?
What would you

expect to see as
information or
Feedback presented
for each of these
commands or steps?
Additional notes
or next steps:
Probable Fault:
MAX204SGV4.0
189

Problem 3 (Optional)
User calls with complaint that they are not able to access the network to place calls or send data.
Service worked before and they state that they have made no configuration changes since last time
they accessed the web.
Symptoms:
1. Fixed and Nomadic Subscribers are able to register, but not be able to obtain an IP Address
2. No Affect on Mobility
3. Affects Multiple Subscribers
List where
you would
check for
this error
(in priority
order):
What are you

verifying?
What Commands or
Steps would you use
at this location?
What would you

expect to see as
information or
Feedback presented
for each of these
commands or steps?
Additional notes
or next steps:
MAX204SGV4.0
190

List where
you would
check for
this error
(in priority
order):
What are you

verifying?
What Commands or
Steps would you use
at this location?
What would you

expect to see as
information or
Feedback presented
for each of these
commands or steps?
Additional notes
or next steps:
Probable Fault:
MAX204SGV4.0
191

Instructions:
information.
are accessing.
MAX204SGV4.0
192

Problem 1
User calls with complaint that they are not able to access the network to place calls or send data.
Symptoms:
1. Full Mobile subscribers will have trouble browsing the Web
2. Affects Multiple Subscribers from the same service provider
3. Not ASN specific
List where
you would
check for
this error
(in priority
order):
What are you

verifying?
What Commands or
Steps would you use
at this location?
What would you

expect to see as
information or
Feedback presented
for each of these
commands or steps?
Additional notes
or next steps:
MAX204SGV4.0
193

List where
you would
check for
this error
(in priority
order):
What are you

verifying?
What Commands or
Steps would you use
at this location?
What would you

expect to see as
information or
Feedback presented
for each of these
commands or steps?
Additional notes
or next steps:
Probable Fault:
MAX204SGV4.0
194

Problem 2
Users calls with complaints that they are not able to access the network to place calls or send data.
Symptoms:
1. Does not affect the Fixed and Nomadic Subscriber
2. New registrations of a Mobile subscriber may not be able to obtain an IP Address
3. Service provider specific not ASN specific
4. Affects Multiple Mobile Subscribers
List where
you would
check for
this error
(in priority
order):
What are you

verifying?
What Commands or
Steps would you use
at this location?
What would you

expect to see as
information or
Feedback presented
for each of these
commands or steps?
Additional notes
or next steps:
MAX204SGV4.0
195

List where
you would
check for
this error
(in priority
order):
What are you

verifying?
What Commands or
Steps would you use
at this location?
What would you

expect to see as
information or
Feedback presented
for each of these
commands or steps?
Additional notes
or next steps:
Probable Fault:
MAX204SGV4.0
196

Problem 3 (Optional)
Users calling in with complaints of dropped calls while mobile and loss of local service in a geographic
region. Service worked before and they state that they have made no configuration changes since
last time they accessed the network.
Symptoms:
1. Affects only Mobile and Nomadic subscribers
2. All Network initiated Calls fail for affected subscribers
3. Does not affect Fixed subscribers
List where
you would
check for
this error
(in priority
order):
What are you

verifying?
What Commands or
Steps would you use
at this location?
What would you

expect to see as
information or
Feedback presented
for each of these
commands or steps?
Additional notes
or next steps:
MAX204SGV4.0
197
List where
you would
check for
this error
(in priority
order):
What are you

verifying?
What Commands or
Steps would you use
at this location?
What would you

expect to see as
information or
Feedback presented
for each of these
commands or steps?
Additional notes
or next steps:
Probable Fault:
MAX204SGV4.0
198

Instructions:
information.
are accessing.
MAX204SGV4.0
199

Problem 1
Fixed and Nomadic users call with complaints that they are not able to access the network to place
calls or send data. Service worked before and they state that they have made no configuration
changes since last time they accessed the web.
Symptoms:
1. Affects Management of the EMS, CAPC, and AP no AAA authenticated access for
management users
2. Affects fixed or nomadic subscribers only
3. Does not affect sessions in progress
4. Does not affect calls in progress or registrations already active
List where
you would
check for
this error
(in priority
order):
What are you

verifying?
What Commands or
Steps would you use
at this location?
What would you

expect to see as
information or
Feedback presented
for each of these
commands or steps?
Additional notes
or next steps:
MAX204SGV4.0
200

List where
you would
check for
this error
(in priority
order):
What are you

verifying?
What Commands or
Steps would you use
at this location?
What would you

expect to see as
information or
Feedback presented
for each of these
commands or steps?
Additional notes
or next steps:
Probable Fault:
MAX204SGV4.0
201

Problem 2
Users call with complaints that they are not able to access the network to place calls or send data.
Symptoms:
1. No New registrations for Mobile subscribers
2. Does not affect calls in progress
3. Does not affect subscribers already registered
List where
you would
check for
this error
(in priority
order):
What are you

verifying?
What Commands or
Steps would you use
at this location?
What would you

expect to see as
information or
Feedback presented
for each of these
commands or steps?
Additional notes
or next steps:
MAX204SGV4.0
202

List where
you would
check for
this error
(in priority
order):
What are you

verifying?
What Commands or
Steps would you use
at this location?
What would you

expect to see as
information or
Feedback presented
for each of these
commands or steps?
Additional notes
or next steps:
Probable Fault:
MAX204SGV4.0
203

Problem 3(Optional)
Users call with complaints that they are not able establish service. Service worked before and they
state that they have made no configuration changes since last time they accessed the web.
Symptoms:
1. Affects only Mobile subscribers on the same Service Providers network
2. All Calls dropped for affected subscribers
3. Not ASN specific.
4. Affects subscribers in roaming networks
List where
you would
check for
this error
(in priority
order):
What are you

verifying?
What Commands or
Steps would you use
at this location?
What would you

expect to see as
information or
Feedback presented
for each of these
commands or steps?
Additional notes
or next steps:
MAX204SGV4.0
204

List where
you would
check for
this error
(in priority
order):
What are you

verifying?
What Commands or
Steps would you use
at this location?
What would you

expect to see as
information or
Feedback presented
for each of these
commands or steps?
Additional notes
or next steps:
Probable Fault:
MAX204SGV4.0
205
Lesson Summary
List the WiMAX mobility modes
List the WiMAX handover modes
List the network elements involved in WiMAX mobility
Define the different WiMAX mobility architectures
Explain WiMAX lease operations
Explain WiMAX SS idle mode(s)
Illustrate the WiMAX Network Entry process
Understand Connections (CID)management, bearer, special.
Understand the concept of capabilities negotiations, service flow establishment/modification,

and end to end QoS.
Illustrate the WiMAX handover process
Understand the concept of side-haul traffic and mobility support in call management
procedures.
Establish a logical approach to troubleshooting a call flow scenario.
MAX204SGV4.0
206
MAX204SGV4.0
EMS Overview
207
Lesson 4
EMS Overview
MAX204SGV4.0
208
EMS Overview
MAX204SGV4.0
EMS Overview
209
Objectives
1. Describe the Principle of Network Management.
2. State the hardware requirements of the EMS.
3. State the software requirements of the EMS.
4. State the daily operations of the EMS.
5. Describe the functions of EMS Site Administration.
6. Describe the Account Management Operations.
7. Describe the EMS & NE Configuration (MIB Creation)
1. Log on to the EMS
2. Create the WiMAX network record
3. Understand the EMS GUI
4. Use the EMS to determine managed services states
5. Backup/restore EMS data
6. Use the EMS to manage user accounts
7. Add AAA network element record to the EMS
8. Add CPS policy
9. Use Network Topology tree to determine node status
10. Interpret statistics
11. Interpret alarms
12. Filter alarms
13. Download node configuration
14. View node configurations
15. Change node configurations
16. Download node software
17. Delete a node
MAX204SGV4.0
210
EMS Overview
Network Management Overview

This section provides a short overview of Operations and Maintenance capabilities in the WiMAX system.
These capabilities primarily cover element management of Motorola supplied fixed network equipment
(FNE) by the Element Management System (EMS).
The Element Management System (EMS) provides a central point for configuring, monitoring, and managing a
Motorola WiMAX Access Services Network (ASN) via web-based and Java-based tools.
FCAPS
EMS network management includes the basic functions of Fault, Configuration, Accounting,
Performance, Security (FCAPS) management. The FCAPS descriptions and Benefits are
summarized below:
Fault Management Features

Graphical Event Viewer Display in tabular list format for easy navigation of stored event data
Uses secure SNMPv3 for reporting from NEs to EMS
Up to 32 days of normal events
1 year of availability data
Multiple severity levels (Critical, Major, Minor, Warning, Indeterminate, Cleared)
Fault information includes details on fault passed by NE, as well as possible root causes and
remedies
Filtering based upon severity, type, NE IP address, active/cleared state, and user
acknowledged state
E-mail notification to operators
SNMPv1 NBI forwarding to other network management systems
NE State shown graphically in Topology Manager
Access to NE Diagnostics via Topology Manager
Configuration Management Features
Full configuration, validation, and online help support

Uses secure SNMPv3 and SFTP for configuration support for all Motorola NEs in the system
Logging of all configuration changes
Download Manager allows configuration and upgrade of multiple NEs
Configuration reports on current and pending changes
Reports on NE configuration and inventory data
MAX204SGV4.0
EMS Overview
211
Network Management Overview

Performance Management Features
Graphical Statistics Viewer Display provides information graphically for easy
interpretation of statistical data
Uses secure SNMPv3 and SFTP for collection of statistical data
Historical statistics
Up 32 days of statistical data provides substantial baseline of activity for review
Global collection intervals may be set to 15, 30, or 60 minutes
Individual NEs may be set to different collection intervals
Data may be extracted in CSV or XML to obtain a larger baseline for additional
analysis or viewing in another tool
Security Management Features
Username/password protection for Motorola EMS access

Access classes (Operator, Administrator)
Security logs to track all logins and account changes
Configuration logs to map users to network configuration changes
Control point for distribution of security keys for all management interfaces
Automatic key rotation
SNMPv3, SFTP, and IPSec protocols for communicating with NEs
MAX204SGV4.0
212
EMS Overview
EMS Hardware and Software

This section covers the high level hardware and software requirements/functions of the EMS
Hardware Requirements
The EMS is a software-only product. It can be installed on a computer that has the
following hardware:
Hardware Requirements
System Type
Low End System
High End System
Requirements
2.8 GHz Pentium 4 CPU
160 Gb 7200 RPM hard drive
1 Gb RAM 10/100/1000 BaseT network

CD-ROM drive
SVGA video card
Dual 3.7 GHz dual core Xeon CPUs
500 Gb 7200 RPM hard drive

4 Gb RAM
10/100/1000 BaseT network card

CD-ROM drive
SVGA video card
Software Requirements
Required software for EMS includes:
Microsoft Windows XP Professional with service pack 2 with firewall off (or) Microsoft Windows
2003 Server with service pack 1 with firewall off (to not interfere with the EMS application).
Microsoft Internet Explorer, version 5.0 or greater
Apache Web Server, version 2.0.54
Adobe Acrobat Reader, version 5.0 or greater
MAX204SGV4.0
EMS Overview
213

System Capabilities
The following table shows the system capabilities of the EMS in both the low and high end
configurations.
System Capabilities
EMS
Platform Type
Maximum CAPCs
Maximum APs
Maximum CPEs
Low End System
High End System
PC OS Windows XP
Professional
PC OS Windows 2003
Server
500
1000
100,000
333,000
EMS Platform Components

The following table depicts the EMS platform in a layered view. The foundation is the PC hardware
followed by the Windows OS then the Java Runtime environment.
EMS Platform Components
EMS
Layer
Java Runtime Environment (1.5)
Platform
OS (Windows XP Professional or 2003 Server)

PC (Low End or High End Configuration)
MAX204SGV4.0
214
EMS Overview
MAX204SGV4.0
EMS Overview
215

EMS Software Components
The following table depicts the EMS software as it relates to the services and platform software.
Software Services
Software Components
GUI (Java Applets)
User Presentation
(Platform)
Web Browser (MS-Internet Explorer)

Topology Mgmt
User Services
(EMS)
Security Mgmt
Core Services
(Platform)
Message Bus (IPC)
Configuration
Management
User Management
Web Server
(Apache/Tomcat)
Fault Mgmt
FM NBI
HTTPS Management
DBMS
(Derby)
SNMPv3 Stack
The key concept to note with this software components layering is that the User (Administrator or
Operator) logs into the EMS application through a web browser regardless if it is a local or remote
login. The User Presentation is the Client to the User Services (Server) which is the EMS
application.
MAX204SGV4.0
216
EMS Overview
EMS Network Interface

The Network Interface Diagram above shows the protocols the EMS uses with the WiMAX Network
Elements. While there are multiple different protocols used in the ASN to provide a complete end to
end operation it is important to understand the protocol relationship between the EMS and other WiMAX
NEs for network maintenance.
High Level Operation Flow

The sequence of events listed below is from the EMS perspective and it is at a very
high level. It follows a network element hierarchical topology
1.
2.
An administrator starts a session via a web interface using the HTTP/HTTPS protocol
The CAPC is configured:
a. Bootstrap SNMPv3
b. SW & Configuration Download SFTP
3. The AP is configured
a. Bootstrap SNMPv3
b. SW & Configuration Download SFTP
4. The CPE registers with the EMS and gets its configuration policy SNMPv3
5.
6.
7.
Alarm events and statistics from each NE (CAPC, AP, CPE) sent to EMS SNMPv3
EMS sends the alarm events and statistics to the North Bound Interface (NBI) SNMP Trap
EMS downloads Software updates for the system from a Software Server, shown as the
Network Management System SFTP
MAX204SGV4.0
EMS Overview
217
Network Interface
MAX204SGV4.0
218
EMS Overview
EMS Operations Introduction

This section will cover logging into the EMS tools, high level tool functions and tool navigation Logging into the
EMS locally the user is presented with 3 application short cut icons:
EMS Site Administration
EMS Account Management

This function starts the Topology management and allows the administrator to perform:
Fault Management

This function allows the administrator to:
Backup/Restore the EMS database
Stop/Start EMS Operations
HTTPS Management
EMS Account Management

This function allows the administrator to:
add users to the system
edit user privileges on the system
delete users on the system
MAX204SGV4.0
EMS Overview
219
EMS Operations Introduction
EMS Operations
MAX204SGV4.0
220
EMS Overview
Site Administration
The EMS Site Administration tool is a EMS utility that is launched independently from the
EMS desktop.
Site Administration Functions

1. EMS operation management
2. EMS Backup / Restore - configuration data and logs
3. Security (HTTPS) Management
The Site Administration tool is launched from the icon on the desktop. To launch Site
Administration, log in with an Administrator or Operator user ID and password.
MAX204SGV4.0
EMS Overview
221
Site Administration
MAX204SGV4.0
222
EMS Overview
EMS Operations Management

This utility is available from the top right tab of the Site Administration tool.
The operational status of the EMS is shown under the Current System State section.
There are two types of services:
1. Managed EMS software components
2.
Non-Managed software components the EMS requires but is managed by the OS When
EMS application is successfully started, all Managed Services are displayed with a
green check mark vs. a red X.
[Stop EMS Operations] button will STOP ALL EMS MANAGED SERVICES. If any of the EMS
managed services are not running use this button to stop the remaining EMS managed services.
Start EMS Operations] button starts all managed services.
Stopping the EMS managed services will break the SNMPv3 links
to all Network Elements and the operator will be blind to ASN state
changes. **Note: At this time all NEs must be restarted after the EMS has
been restarted to restore the SNMPv3 links.
MAX204SGV4.0
EMS Overview
223
Site Administration
MAX204SGV4.0
224
EMS Overview
EMS Backup / Restore

The EMS Backup/Restore utility is selected by the top left tab of the Site Administration tool. The page is
separated in 3 sections:
1. Available Backups
a.
Path to the back up area - C:\MotoArchives
b.
List of available backups
c. Sort filter
2. Backup Summary
a.
Date Created
b. System Version
c.
d.
Creating Machine
Creating Operator
e. Archive Health
3. Backup Management buttons to select
a. Create New Backup
b.
c.
d.
e.
Backup
Restore Backup
Show Backup Details
Delete Backup
View Log
There are 2 methods of creating a backup of the configuration and data

1. Offline - the EMS application is shutdown. This is the DEFAULT Backup method.
2. Online the EMS services are temporarily suspended but never shutdown
MAX204SGV4.0
EMS Overview
225
EMS Backup
MAX204SGV4.0
226
EMS Overview
Backup Image Name

The backup images are stored in C:\MotoArchives and are shown in the Available Backups area of
the utility. A status box to the left of the file:
GREEN check if the Backup is GOOD.

RED X if the backup is NOT GOOD.
The combination of the backup timestamp and EMS version are:

yyyymmdd-hhmmss-nn.nn.nn.nn (YearMonthDay-HourMinSec-release.number)
The backup image may have a RED X if the image was created on a Portal
EMS release that is newer than the current EMS installed release. The Archive
Health field will state Future backup version is not restorable
The image on the facing page shows the results of an Offline Backup. The EMS Operations
Manager will be needed to restart the EMS application.
MAX204SGV4.0
EMS Overview
227
EMS Backup
MAX204SGV4.0
228
EMS Overview
Restore Backup
Restoring a backup is done for a couple of reasons:
1. Current configuration database is bad and restoration to a good known database is needed.
2. EMS release has been upgraded to a newer version and the good known
database is imported.
The Restore Backup will cause the EMS application to be shutdown.

Save all sessions before proceeding with the Restore Backup operation.
Highlight the backup image to be resorted and click on [Restore Backup] button.
Once the Backup has been restored the EMS application will need to be restarted using the
Operations Management utility as previously described.
Detailed information pertaining to a backup image can be examined by highlighting the backup
image and clicking on Show Backup Details icon.
MAX204SGV4.0
EMS Overview
229
Backup Restore
MAX204SGV4.0
230
EMS Overview
EMS HTTPS Management

EMS HTTPS Management provides the following functionalities:
1.
2.
3.
4.
5.
View Certificate Details

Generate certificate signing requests
Import Certificate Authority issued Certificates
Enable HTTPS
Export Selected Certificates.
MAX204SGV4.0
EMS Overview
231
HTTPS Management
MAX204SGV4.0
232
EMS Overview
Account Management
EMS user accounts are managed through EMS Account Management tool which is launched
independently from the EMS application.
User Account Management supports EMS user addition, modification and deletion.
There are 2 levels of access control for a user account:
1. Administrator - can perform all EMS supported operations
2. Operator - can perform all EMS supported operations except Security related
configurations and User Account management.
Double click on the Motorola EMS Account Management icon on the Windows desktop
to launch the tool.
Login as an administrator to perform account management or as an Operator to
change your current password.
Once logged into the Account Management tool as an Administrator a menu of operations
is shown under the Actions function.
Change Password user selection is made through a pull down selection
on the Change Password window.
Add a User Login ID, Name (comment field) & password is entered
Modify Users user name and admin function can be modified.
Delete Users deletes users from the system
MAX204SGV4.0
EMS Overview
233
Account Management
Account Management
MAX204SGV4.0
234
EMS Overview
EMS and NE Configuration

This module describes the use of the EMS to configure the WiMAX network elements. Database values
used in this module reference the current values used in the field.
Start Point of Reference

1.
2.
3.
All network connections from EMS to NEs have been established in advance;
The latest EMS has been successfully installed.
A WiMAX Network configuration has NOT been created; no backup file is available.
High Level Configuration Steps

1.
2.
Define / Configure WiMAX system

Define / Configure CAPC
a. Discover Payload
3.
Define / Configure AP
a. Define / Configure Sectors
4.
Define / Configure CPE Policy

a. CPE Auto Discovery (through Registration trap)
5. Download to NEs
a. Full (NECB) Configuration
b. Delta (BCC) Configuration
c.
Software Bundle (w/NECB)
d. IPsec Policy
MAX204SGV4.0
EMS Overview
235
MAX204SGV4.0
236
EMS Overview
Operational Flow
The operational flow diagram below depicts the high level functions of the EMS application. The
top half of the diagram represents the provisioning flow. The bottom half of the diagram identifies
ongoing operations of the EMS as applied to the WiMAX system. Also note that the operational flow
diagram show System Level functions, Network Element Level and Managed Network Element
functions.
WiMAX system must be first defined in the Network Topology.
WiMAX system global settings can be defined.

NE nodes, CAPC and AP, can be provisioned, i.e., added, bootstrapped.
IP security among NEs can be enforced.
SNMP v3, Secure FTP and HTTPS can be established between EMS and NEs.
Software and configuration can be downloaded to NEs.
CPE can be discovered.
CPEs are provisioned in AAA server, NOT in the EMS.
MAX204SGV4.0
EMS Overview
237
MAX204SGV4.0
238
EMS Overview
Building a WiMAX Network
Other Network Elements

AP
Router/FA
MSS/CPE
NTP
AP
EMS
DNS
DHCP
DNS
Server(s)
AP
MSS/CPE
Firewall
(Optional)
CAPC
AP
DHCP
AAA
Router/HA
AAA
VoIP
Server
MSS/CPE
Router/FA
AP
ASN and CSN Network Elements and EMS

Should be in place
Should be configured
Should have connectivity
AP
In preparation for building a WiMAX network some initial pre-work needs to have been accomplished. The
pre-work involved includes installation and configuration of other supporting Network Elements such as the
various network servers, the core routers and switches and the installation of the Portal EMS. All ASN
Network elements should be in place and should have connectivity between them as required.
As part of the configuration of these nodes, it is important that a network administrator plan all necessary
addressing and routing and VLAN associations for this part of the network and also for the WiMAX elements
to be added later.
It is important at this phase to provision the Portal EMS with necessary global settings for the EMS system
so that it can communicate with the other nodes in the core network and also perform the task of managing
and monitoring the network.
MAX204SGV4.0
EMS Overview
239
Building A WiMAX Network

1. Add WiMAX System
2. Add CAPC
3. Add AP
The build process for building a WiMAX network follows a relatively simple sequential order.
Step 1 is to add and define a WiMAX system in the Portal EMS.
Step 2 is to add and define a CAPC element in the portal EMS and establish communication between the
two nodes.
Step 3 is to add and define the Access Point elements associated with the CAPC along with their related
sectors and to establish communications between the Access Point and the EMS.
MAX204SGV4.0
240
EMS Overview
Add A WiMAX System
1 Add WiMAX Network at EMS
It is first necessary to define the WiMAX system in the Portal EMS so that the EMS is aware of and can
therefore build the required associations between files which will be generated in the process of adding
WiMAX network elements into the system defined.
MAX204SGV4.0
EMS Overview
241
Add A CAPC
1 Install Hardware
2 Configure at local terminal
3 Add CAPC to Network at EMS
4 Bootstrap CAPC at local terminal
5 Configure CAPC at EMS
6 Push Config. to CAPC from EMS
7 Physical
The next step required is to add and define a CAPC network element to the system so that the associations
between that node and the EMS can be built as well as the associations between this node and other nodes
such as the Access Point nodes can be established.
Again, this is a relatively simple sequential process:
Step 1 is to install all of the CAPC hardware and connectivity.
Step 2 is to configure the local software and communication setup at the CAPC so that it will be able to
communicate with the Portal EMS and other elements in the WiMAX network.
Step 3 is to add the CAPC definition at the Portal EMS so that the EMS is aware of the CAPC and will be
able to communicate with it.
Step 4 is to initiate the Bootstrap process at the local terminal of the CAPC to initiate communications with
the EMS.
Step 5 is to configure the newly added CAPC at the EMS with all of its necessary operating parameters.
Step 6 is the final step of pushing the configuration just defined in the EMS out to the CAPC so that it can be
up and running in the network.
MAX204SGV4.0
242
EMS Overview
MAX204SGV4.0
EMS Overview
243
Add An AP
1 Install Hardware
2 Configure at local terminal
3 Add AP to Network at EMS
4 Bootstrap AP at local terminal
5 Configure AP at EMS
6 Add Sectors at EMS
7 Push Config. to AP from EMS
8 Physical
The remaining step in the process is one which will be repeated as each AP element is deployed. This part
of the build process involves adding and defining each Access Point and its related RF sectors and will
include setting all necessary parameters for the Access Point.
Once again, the addition of this network element is a relatively simple sequential process:
Step 1 is to install all of the Access Point and RF components and their physical connectivity.
Step 2 is to configure the local software and communication setup at the Access Point so that it will be able
to communicate with the Portal EMS and other elements in the WiMAX network.
Step 3 is to add the definition of the Access Point and related RF sectors at the Portal EMS so that the EMS
is aware of those elements and will be able to communicate with and manage them.
Step 4 is to initiate the Bootstrap process at the local terminal of the Access Point to initiate communications
with the EMS.
Step 5 is to configure the newly added Access Point and RF sectors at the EMS with all necessary operating
parameters.
Step 6 is the final step of pushing the configuration just defined in the EMS out to the Access Point so that it
can be up and running in the network.
As stated before, each of these steps will be repeated with the deployment of additional Access Points in the
WiMAX network.
MAX204SGV4.0
244
EMS Overview
WiMAX System Configuration

Launch the EMS Network Topology from the Portal Element Management System home page
EMS Properties
This is where you define and commit Global WiMAX settings. This window is opened by:
1. Select File | Configuration
2. Left gear icon EMS configuration viewer
The window is defaulted in View mode. Click on the Pencil/Paper icon to transit to the Edit
mode. The Status area at the bottom of the window will show a lock in the right corner and the
message Obtain Lock and Allow Editing Successful!. The Save Configuration and Abort
Changes icons are enabled when in the Edit mode.
Tooltip will display when placing the mouse pointer on a parameter name, e.g. Global log level.
Tooltip will have a description of the parameter and if it is a required parameter and the Min and
Max value range when applicable.
Fault Management Parameters
Alarms and (non-management type) Events can be forwarded to up to 2 user specified external
platforms as they come into EMS from NEs. The forwarded hosts must be configured to process the
forwarded events. Note that EMS Engine ID field is ready-only parameter with a reading glass icon
shown in the left column.
Performance Management parameters
A historical statistics collection interval (in minutes) can be set for all APs or for all CAPCs. The raw statistics
data and parsed data will be retained by a user defined period (in days).
Resource Management parameters
EMS will be the NTP server for NEs (CAPC and AP). There can be up to 3 (stratum 1) NTP servers where EMS can
source from. EMS will use its internal (localhost) clock if no NTP server is available.
Bootstrap Accounts
Otherwise known as the SFTP accounts. This is needed for the CAPC and AP bootstrap operation. The user:
apftp with password: apftp is defined as a requirement in the bootstrapping procedures.
The lock on EMS configuration data is released after either a successful Save operation or Abort
Changes operation. The interface will be in View mode after either operation. EMS configuration
takes effect immediately after a successful Save.
MAX204SGV4.0
EMS Overview
245
MAX204SGV4.0
246
EMS Overview
Add WiMAX System Node

Before any NE Provision/Configuration can be performed to a WiMAX system, the WiMAX system level
Global Setting must first configured and committed. WiMAX Global Settings (common parameters) will
apply to NE only when any NE is configured next time, i.e. any Global settings change applies to an NE
configuration when that NE configuration data is edited and downloaded next time. Most of the WiMAX
Global Settings are NE impacted, i.e. will cause NE re-start (re-init). These Global settings should be done
at the initial system buildup stage and not be changed frequently. A few Global Settings parameters, e.g.
WiMAX Service Provider ID, DHCP Server IP Address, etc., require information in advance. Quality of
Service profiles must be defined for any subsequent referencing from AP configurations. A WiMAX
system node must first be added to the EMS Topology after EMS is initially installed. WiMAX Global
Settings can then be configured and committed through the WiMAX system node.
System Node
To add a WiMAX node to the EMS Topology, right click on the System icon in the Motorola EMS
Network Topology; select and click on Add WiMAX.
All WiMAX node property parameters are automatically generated by the EMS and only the Node
name parameter can be modified. Click on the Save Configuration icon will complete adding the
WiMAX system node to the Topology.
WiMAX System Node
WiMAX node properties can be modified if needed. Right click on the WiMAX node icon; select and
click on Node Properties to view or change WiMAX node properties. Node Properties is available
for almost all NE nodes in the WiMAX Topology
MAX204SGV4.0
EMS Overview
247
Node Properties
MAX204SGV4.0
248
EMS Overview
Configure Global WiMAX settings

Right Click on the WiMAX node icon; select and click on Configure Global WiMAX settings to
set up the WiMAX Global Settings.
Click on the Pencil/Paper icon to transit to the Edit mode to edit/configure the WiMAX Global Settings.
Once a WiMAX system has been configured, to change the Global WiMAX settings the data must be retrieved
from the database by clicking on the folder icon then the Edit mode can be used.
Service Provider
Service Provider ID (should be called Network Access Provider, NAP, ID instead) comes from the
system provider, e.g. Motorola, and needs to be first defined in the global settings. This value is
used for constructing NEs identifier (logical MAC address) to be used in the network as well as
defined in CPE configuration.
The up/down arrow next to the parameter name which means that change
made to the this parameter will impact NE (cause NE to re-init on all the
subsequent NE configuration downloads) and it is Required
DHCP Servers
More than one DHCP Server for device (e.g. CPE) registration can be defined for the WiMAX system.
At least one DHCP Server is required. Click on the Add icon to add a DHCP Server.
Quality of Service Classification
Defines the QoS profiles for NEs. Each WiMAX QoS profile is identified by the QoS Rule Index when
referenced by NE QoS definition. There can be up to 100 service classes configured in this table.
Security
Encryption/authentications can be enabled or disabled for Security. Disabled will allow the
CPE (MSS or SS) to enter the network without AAA verification.
This is a NE impacting and Required parameter.

Signaling Priority
Operation Administration Management (OAM) task priority can be defined to plan
the utilization of the system resources.
Click on the Save icon to save the WiMAX Global Settings. This only saves the settings to a
workspace. The previous settings can be restored by clicking the Restore icon. Click on Validate
Configuration Changes icon to validate all Global Settings before Commit. Valid data format and
range will be checked. Some parameters (e.g. in QoS) are also validated for any business rule
violations. Error message will show if any validation failure encountered. For the Global Settings to take
effect the settings must be committed. Click on Commit Configuration to the Network Element icon
to commit these settings. These settings will apply to any subsequent NE Configuration downloads.
Since most Global settings are NE impacting, it is very likely the warning message like this shows
up when WiMAX Global Settings are committed. Click on Yes to proceed. Commit Successful
status message indicates that the WiMAX Global Settings configuration is completed. The Global
Settings must be configured at least once before any NE is added to the Topology.
MAX204SGV4.0
EMS Overview
249
Configuration Interface
MAX204SGV4.0
250
EMS Overview
EMS Node Properties & Node Configuration Rules

The Topology is now ready for add/configure NEs. Before we begin there are some tool rules and configuration
dependencies that need to be understood and referenced during the system buildout.
Node Properties
[Node Properties] is available for all NE nodes in the WiMAX topology from the EMS Properties (described
previously) to the CPE Policy Properties. Editing the Node Properties is accomplished by:
1.
2.
Opened in an Edit mode when [Add Node] is selected from a parent Topology node. For
example right click on the WiMAX System Node to get: Add AAA, Add CAPC, Add CPE Policy
Right click on the topology node select [Node Properties] then click on the
Pencil/Paper icon to transit to the Edit mode. NO PARENT DEPENDENCIES
NEEDED TO EDIT NODE PROPERTIES.
Node Configuration
[Node Configuration] is available for most NE nodes in the WiMAX topology. Editing the node
configuration is highly dependent on a Parent Child topology LOCK State relationship
Children node configuration requires the parent node configuration to be locked first.
A parent (CAPC or AP) node configuration is locked when that configuration has been:
1.
2.
Opened for editing and not in the Download Manager queue

The node configuration has been placed in Download Manager queue
and is still pending for download.
A child (Payload Set or Sector) node must be in locked state for editing. A child node configuration is locked
when its parent node configuration is in locked state but not in Download Manger queue.
Therefore, to edit a Payload Set configuration data its parent CAPC node configuration must be opened for
editing but not been placed on the Download Manager queue.
MAX204SGV4.0
EMS Overview
251
Add CAPC
MAX204SGV4.0
252
EMS Overview
MAX204SGV4.0
EMS Overview
253
WiMAX Network Element Configuration Dependencies

A CAPC node must exist before any AP can be added to the Topology. Each AP is associated with a PayloadSet of a
CAPC and are added at the PayloadSet level of CAPC. PayloadSet may contain up to 2 Payload Modules.
PayloadSets and Payload Modules are discovered by the Inventory provided by CAPC. PayloadSets and Payload
Modules are established in the Topology by invoking the Discover Payload (via obtaining the CAPC FRU
inventory data) at CAPC level. Bootstrapping is required for any additions of CAPC and AP. SFTP is employed for
transferring bootstrap info between EMS and CAPC or AP. It is essential that the SFTP account id and password
are in sync among EMS and NEs
Due to the dependency of APs and CAPC/PayloadSet, the following order must be employed to
construct a WiMAX Topology with CAPCs and APs:
1.
2.
3.
4.
5.
6.
Add a CAPC
Bootstrap the CAPC
Discover the PayloadSets and Payload Module of the CAPC
Add an AP to a PayloadSet
Add AP Sectors
Bootstrap the AP
CAPC & AP Configuration Rules

There can be up to 10 PayloadSets per CAPC.
Each PayloadSet may contain one or two Payload Modules (an Active and Standby modules).
200 APs can be added to a PayloadSet (database capacity). However realized AP capacity is a
function of the offered MSS traffic profile and could be less than the maximum database capacity.
Up to four Sectors can be added to an AP.
APs can also be moved from one Payload set to another PayloadSet within a CAPC or to
a PayloadSet of a different CAPC. This is called AP Re-parenting.
CPE Policy Configuration
EMS manages CPE through a pseudo NE type, called CPE Policy. Each CPE Policy contains a CPE matching
criteria and the CPE configuration for all CPEs matching the criteria. CPE Policy pseudo nodes must be defined
prior to any CPE discovery. CPEs are provisioned in AAA server not in EMS. When a CPE registers to an AP, a
registration trap will be sent by CPE to EMS (for CPE auto discovery). EMS will validate the MAC address of the
CPE and either creates a data base entry for a new MAC address or updates the IP for an existing CPE with the
MAC address if the IP has been altered (by DHCP server). Each CPE is pre-installed with a certificate (by
manufacture) for bootstrapping (file transfer) with EMS through HTTPS (vs. SFTP is the case of bootstrapping
CAPC or AP). EMS will import the certificate via the Security Management in Site Administration tool.
CPEs are grouped under the CPE Policy pseudo node by the CPE Selection Criteria, Model number, Network
Address Identifier (NAI) or MAC address. No CPE entry will be shown in the WiMAX Topology. There is a CPE
allocation mechanism called Search CPE to find a particular CPE in the EMS database. The CPE configuration
defined in the pertaining CPE Policy can be downloaded to the CPE found.
MAX204SGV4.0
254
EMS Overview
CAPC Node Configuration

A CAPC node is added to the WiMAX Topology at the WiMAX level. Right click on the WiMAX System
Node to pull up the node menu and select Add CAPC
The Add Node (Node Properties) window for the CAPC is launched with the following tabs:
General Node Properties

CAPC General
Node Information
FRU
Interfaces
Local Admin Accounts
MAX204SGV4.0
EMS Overview
255
Add CAPC
MAX204SGV4.0
256
EMS Overview

The CAPC MAC Address is used to establish the SNMP Engine ID for secure SNMP
communication between EMS and the CAPC.
The MAC address of the CAPC must be known in advance and cannot be changed once the CAPC node is
added to the Topology. This information is obtained when commissioning the CAPC.
If a MAC address change is needed the CAPC node must

be deleted and re-added
IP address and Node name can be edited from this screen. General
Node Properties
CAPC General
CAPC LMT URL - is automatically populated after CAPC Bootstrapping. This will be the URL used to launch
the web based Local Maintenance Terminal from the CAPC Node menu selection.
SNMP Engine Id is automatically generated once the CAPC Node is added. This value will be
needed for the CAPC Bootstrapping operation.
More than one user account can be defined for the CAPC Local Maintenance Terminal (LMT).
Node Information, FRU, Interfaces information is updated from the inventory data obtained from the CAPC
after a CAPC bootstrap or later when EMS requests an Inventory Sync.
Once a CAPC node is added to the WiMAX Topology, an icon representing the CAPC is shown on the
Topology tree. The CAPC state management will not begin until after the CAPC has bootstrapped. The
icon is in grey color and no status info available yet.
A small down arrow marked on the CAPC icon means a configuration download is required.
MAX204SGV4.0
EMS Overview
257
MAX204SGV4.0
258
EMS Overview
CAPC Bootstrapping
The CAPC (with the same MAC address of the node added) can now exchange the bootstrap (xml)
file with EMS (using the authenticated SFTP account) and establishes the SNMP V3 communication
(with the authenticated SNMP Engine ID) to complete the initial bootstrap.
This process can take (5 or more) minutes to
complete Bootstrap xml file exchange
There is no status bar or similar types of indication of bootstrapping progression. One can observe
the bootstrap xml file exchange for the progression of the bootstrapping.
The bootstrap xml created by EMS for the CAPC bootstrapping looks like
800000A103212121210201.xml in which the file name is the same as the SNMP
Engine ID of the CAPC just added and the xml file is placed under:C:\Program
Files \Motorola\PortalEMS\s ftproot\ems _to_ne
When the CAPC starts the bootstrapping, a similar bootstrap xml created by the CAPC is uploaded
to EMS and placed under:C:\Program Files\Motorola\PortalEMS\sftproot\ne _to _ems
Both bootstrap xml files will be automatically deleted by EMS when the
bootstrapping is successfully completed.
The FRU related information will also be populated in the Node Properties after
the bootstrapping is successfully completed.
CAPC Bootstrapping will be accomplished during the CAPC course.
Payload Discovery
Payload Discovery can only be done when a CAPC has completed its bootstrapping. Right
click CAPC Node icon; select Discover Payload Sets and click.
Discover Payloads Summary displays the PayloadSets and Payload Modules
discovered for this CAPC. Click OK to acknowledge.
The WiMAX Topology tree now shows the hierarchical order of the newly discovered
PayloadSets and Payload Modules.
Children nodes can be collapsed or expanded under its parent node for
different views of the hierarchical depth.
MAX204SGV4.0
EMS Overview
259
Payload Discovery
MAX204SGV4.0
260
EMS Overview
Payload Set/Module - Node Properties

Payload properties configuration is at the Payload Set level. Each Payload Set may contain 1 2 Payload Modules, one Active and one Standby.
Payload set is the logical representative of Payload and is the node where APs are associated with.
Right click a Payload Module icon to select Node Properties to modify the properties of
the Payload Module.
The only editable parameter is the Payload Module Node Name. All other fields are either automatically
generated by EMS or populated from the CAPC Inventory data and are read-only. The Node Name
serves only as the identifier of the Payload Module on the Topology.
Payload Module Node Properties
At PayloadSet level, in addition to the Node Properties one can configure the PayloadSet, to launch
the Statistics Viewer, to delete this PayloadSet and to add APs.
Right click PayloadSet to select the operations.
Delete this Node is disabled. A parent node cannot be deleted until all children
nodes are deleted first. There are two Payload Modules under this PayloadSet.
PayloadSet Node Properties are similar to Payload Module Node Properties where only Node Name is editable
and all others are automatically generated by EMS or populated from CAPC Inventory data.
Payload Set Node Configuration

To configure a PayloadSet, one must open its parent CAPC node configuration for editing first.
The CAPC Node (parent) must be Locked for editing (NOT IN DOWNLOAD
MANAGER) before the Payload Set (child) can be Locked for editing.
Right click on CAPC node icon; select and click on Node Configuration then click on the
Pencil/Paper icon to transit to the Edit mode.
After the parent CAPC node configuration is in locked state, right click on the PayloadSet node icon; select and
click on Node Configuration then click on the Pencil/Paper icon to transit to the Edit mode.
Note that there is a small lock icon at the CAPC node icon and at all the children PayloadSet icons. Payload Set
Node Configuration
Child node configuration is a subset of the configuration data of the parent node. It cannot be
downloaded individually. The child configuration can only be saved for incorporating into the
parent node configuration data.
All children node configurations must be completed before the parent node configuration can be
downloaded, i.e. complete (save) all children PayloadSet configurations before downloading
a CAPC configuration.
MAX204SGV4.0
EMS Overview
261
Node Configuration
MAX204SGV4.0
262
EMS Overview
Validation
To validate if all required parameters are in place as well as if any parameter data are invalid, a
Validation (the light bulb icon) can be performed before or after the configuration is saved. If any
required field is missing or any field contains invalid data (out of range, incorrect format, etc.), the
Validation will fail. The failed field will be highlight in RED.
After all PayloadSets configurations are completed (saved), CAPC can then be configured.
Right click on the CAPC node icon in WiMAX Topology; select and click on Node
Configuration to launch the CAPC Node Configuration interface.
There are a few configuration parameters required. To validate if all required parameters are in place as well as
if any parameter data are invalid, a Validation (the light bulb icon) can be performed before or after the
configuration is saved. If any required field is missing or any field contains invalid data (out of range, incorrect
format, etc.), the Validation will fail. The failed field will be highlight in RED.
MAX204SGV4.0
EMS Overview
263
MAX204SGV4.0
264
EMS Overview
CAPC Download
When a validation is successful the configuration is ready for downloading to NE.
A Configuration Download can be executed on demand (by clicking the down arrow icon) or by
schedule via Download Manager (by clicking on the green plus icon).
Since this is the very first time Configuration Download to this CAPC, the NECB contains re-init type
parameters which will cause the CAPC to restart.
The warning message is issued after the automatic Validation. This message should also
be seen in the previous validations.
Click Yes to proceed the on-demand Configuration Download.
If this Configuration Download is not desired, one can undo all the changes and revert back to
the previous configuration by aborting this Configuration Download with a No and then click on
the Delete Workspace (the trash can icon).
Delete Workspace will also remove the lock from this CAPC and all children PayloadSets.
When a Configuration Download succeeds for the first time, the color of the NE icon will turn to green
with an Up status (from the previous Unknown state).
As this is a NECB download, the CAPC has restarted and sent an Availability event trap
to EMS after the restart.
MAX204SGV4.0
EMS Overview
265
Node Configuration
MAX204SGV4.0
266
EMS Overview
Access Point Configuration

Access Point (AP) nodes can only be added to the WiMAX Topology at a PayloadSet level. Therefore, a
CAPC must be added to the Topology and Payloads have been discovered before one can add an AP.
Right click on a PayloadSet; select and click on Add Access Point
Required Fields needed for Bootstrapping

IP Address
Node Name
MAC address
AP General
AP VLAN ID
These are the same values used in commissioning the Access Point and must be known
in advance to add an AP node to the WiMAX Topology.
Click Save Configuration (floppy diskette) icon after valid values are entered.
The parent CAPC node icon now shows with a down arrow which means a CAPC
Configuration Download is required as a new AP node is added to its PayloadSet.
An AP node icon appears on the WiMAX Topology under the PayloadSet level after an
AP has been successfully added. The AP node icon is in grey color with a down arrow
need a Bootstrap and an initial Configuration Download.
The SNMP Engine ID will be needed at the AP for the Bootstrapping procedure
MAX204SGV4.0
EMS Overview
267
AP Configuration
MAX204SGV4.0
268
EMS Overview
AP Bootstrapping
The AP Bootstrapping is similar to the CAPC bootstrapping.The AP (with the same MAC address of
the node added) can now exchange the bootstrap (xml) file with EMS (using the authenticated
SFTP account) and establishes the SNMP V3 communication (with the authenticated SNMP Engine
ID) to complete the initial bootstrap.
Bootstrap xml file exchange
There is no status bar or similar types of indication of bootstrapping progression. One can observe the
bootstrap xml file exchange for the progression of the bootstrapping. The bootstrap xml created by EMS for the
AP bootstrapping looks like 800000A1 03212121210201 .xml in which the file name is the same as the SNMP
Engine ID of the CAPC just added and the xml file is placed under
C: \Program Files\Motorola\PortalEMS\sftproot\ems _to_ne
When the AP starts the bootstrapping, a similar bootstrap xml created by the AP is uploaded to
EMS and placed underC:\Program Files\Motorola\PortalEMS\sftproot\ne _to _ems
Both bootstrap xml files will be automatically deleted by EMS when the bootstrapping is successfully
completed. The FRU related information will also be populated in the Node Properties after the
AP Sector Configuration
Sectors must be first defined (added and configured) for the newly added AP node. Right clicking the AP
icon; select and click on Add Sectors to add Sectors to this AP. The only field to be entered is the Sector
ID under Sector General. Sector IDs are constrained to 1,2,3 or 4. All fields in General Node Properties are
filled with default values and the Node Name is only changeable field.
Click Save Configuration to complete adding this Sector. A new Sector node icon appears on the WiMAX
Topology after a successful addition of a Sector. Up to 4 Sectors can be added to an AP node.
Similar to CAPC, all children nodes (Sectors) must be configured before the parent node (AP)
can be downloaded with the node configuration and the parent node must be in locked
state before children node can be configured.
Right click on AP node icon; select and click on Node Configuration then put AP
configuration in edit (locked) mode.
The CAPC of the associated PayloadSet must have at least one prior
successful Configuration Download as AP requires some
inherent parameters from CAPC.
AP Sector Node Configuration

Sectors need to be configured prior to AP is configured.
Right click on a Sector node icon; select and click on Node Configuration to configure a Sector. AP Sector
- Node Configuration
MAX204SGV4.0
EMS Overview
269
AP Configuration
MAX204SGV4.0
270
EMS Overview
Configuring a Sector requires a solid understanding of WiMAX 802.16e RF modulation,
management and protocol fundamentals.
Almost all parameters are re-init type parameter. Configuration changes made to Sectors is very likely to
cause AP restart when downloading configuration to the parent AP
AP 2nd Mgmt Channel
Timing parameters the AP sends to the CPE for network __________________
OFDMA Uplink Channel
Uplink timing and power control parameters.
OFDMA Downlink Channel
AP Transmitter/Receiver parameters
AP Uplink Range
MAP Rectangular Region parameters
AP Scheduler
Modulation coding parameters for call flow.
AP PH Y Layer
Average transmit power per antenna
RF Measurement
Receiver signal to noise measurement parameters for call flow.
Uplink Power Control C/N
CPE power control parameters based on modulation schemes
Validation
Click on Validate Configuration Changes after Save Configuration to validate all parameters. Validation
must be successful before leaving this configuration interface.
AP configuration validation checks all children configuration as well. Perform the same for all Sectors Validate
Configuration Change.
MAX204SGV4.0
EMS Overview
271
Configuration Validation
MAX204SGV4.0
272
EMS Overview
AP Configuration Node Configuration

After all children Sectors have been configured and validated, the parent AP can be configured. Right
click on the parent AP node and select [Node Configuration].
Quality of Service Classification
The Classifier Rule Index of each entry must have the same QoS Rule Index
value of one of previously defined and committed Quality of Service Classifications in
the WiMAX Global Settings.
The screen shot below shows the WiMAX System topology icons [Configure Global WiMAX Settings], the
equivalent of the Node Configuration setting, on the bottom half. The AP [Node Configuration] page is
shown on the top half. This shows that the QoS Rule Index on the AP Node equals the value of the
Classifier Rule Index of the WiMAX System node.
The buttons at the bottom of the Quality of Service Classification tabs are used to manage the QoS
records. There can a max of 100 entries per AP configured in this table.
Subscriber Restrictions
CPE authentication on/off and transition time gap parameters
Radius Authentication Server Table AAA
interface parameters
Radio Physical Layer
DL/UL ratios, radio bandwidth and frequency band parameters
Physical Components Backhaul
Type parameter
Recovery Timers
This is a timer that controls how long UL inactivity can occur for a CPE.
Statistics
Indicate statistic collection yes/no and collection interval.
Bandwidth Admission Control
DL/UL Admission Control (AC) parameters
Backhaul Bandwidth
Specifies total DL/UL backhaul bandwidth allocated. During AP commissioning it is recommended to set the
backhaul link bandwidth to Auto negotiate to allow the maximum throughput as provided by the network.
These parameters should be set to the maximum allowable bandwidth.
Security
AAA communication link timers
Validation
Click on Validate Configuration Changes after Save Configuration to validate all parameters. Validation
must be successful before leaving this configuration interface.
AP configuration validation checks all children configuration as well. Perform the same for all Sectors
MAX204SGV4.0
EMS Overview
273
AP Node Configuration
MAX204SGV4.0
274
EMS Overview
AP Download
A Configuration Download can be executed on demand (by clicking the down arrow icon) or by
schedule via Download Manager (by clicking on the green plus icon).
Since this is the very first time Configuration Download to this AP, the NECB contains re-init
type parameters which will cause the AP to restart.
Software mismatch is likely when an NE Configuration Download is performed for the first time. Software Bundle
Download may be required under the circumstance. Click on No to abort the download and then proceed to
AP Software Bundle Download or click on Yes to continue the download operation.
MAX204SGV4.0
EMS Overview
275
AP Download
MAX204SGV4.0
276
EMS Overview
Software Mismatch
Software mismatch is likely when an NE Configuration Download is performed for the first time. Software Bundle
Download may be required under the circumstance. Click on No to abort the download and then proceed to
AP Software Bundle Download or click on Yes to continue the download operation.
A successful AP Configuration Download will clear all locks from AP node as well as all children Sectors. Operation
will be similar to CAPC if AP Configuration Download is done through Download Manager.
MAX204SGV4.0
EMS Overview
277
MAX204SGV4.0
278
EMS Overview

CPEs are managed through CPE Policies. It is imperative to add CPE Policies to the WiMAX Topology
prior to any CPE registration so that CPE Configuration data can be configured. Right click on WiMAX
node; select and click on Add CPE Policy.
There is an Add CPE function, however, CPEs are supposed to be

auto-discovered through a CPE registration trap.
One for one or one for many, with use of model number, can be defined as CPE Selection
Criteria within a CPE Policy. Subsequent CPE registration will be validated with all CPE Policies
for a Selection Criteria match.
By default a CPE Policy is disabled when first added to WiMAX Topology. It must be
activated for the policy to take effect.
The CPE Policy icon is in red when save without activation

(Status would be Disabled).
Right click on CPE Policy node; select and click on Node Configuration to configure CPE. This configuration
can be downloaded to all CPEs that met the CPE Selection Criteria of this CPE Policy.
MAX204SGV4.0
EMS Overview
279
MAX204SGV4.0
280
EMS Overview

NAP ID is the Network Access Provider ID which should be the same as the Service Provider
ID in the WiMAX Global Settings.
They should be called the same, i.e. NAP ID, to avoid being confused with NSP the Service Provider,
e.g. Sprint, ID. The NSP Realm is the name of the NSP.
For now NAP and NSP is 1 to 1 mapping and this should be a single entry definition. WiMAX
Service Provider and CPE NAP Identifier Mapping
CPE Configuration Download can only be scheduled through Download manager from a
CPE Policy node and the Configuration Download will apply to all CPEs that met the CPE
Selection Criteria of the CPE Policy.
Click on Commit Configuration to the Network Element to apply this configuration to any
subsequent single CPE or group CPE Configuration Downloads.
Once the CPE configuration has been committed, it can be scheduled for download through Download
Manager to all CPEs governed by this CPE Policy.
Although CPEs are auto-discovered through CPE Registration Traps, EMS provides the ability to manually
add CPEs for technician convenience (e.g. during testing the system).
To add a CPE manually, right click on WiMAX node; select and click on Add CPE.
MAX204SGV4.0
EMS Overview
281
CPE Policy
MAX204SGV4.0
282
EMS Overview
CPE Auto Discovery

In CPE auto-discovery, the IP of a CPE is assigned by the DHCP Server.
In the real life scenario this function may not have much use as most of the CPE Properties (generated
by EMS and CPE bootstrap) and Config file Encoding parameters (obtained from an actual CPE) are
read-only and cannot be defined.
Most of parameters in Device Information (including a MAC address) are obtained
from an actual CPE as well.
To illustrate the association of a CPE and a CPE Policy, the Network Access Identifier (NAI) and Model Number (and
the MAC address) are used to match the CPE Selection Criteria with CPE Policies.
Normally, this occurs during a CPE registration.
MAX204SGV4.0
EMS Overview
283
CPE Auto Discovery

MAX204SGV4.0
284
EMS Overview
Lesson Summary
Describe the Principle of Network Management.
State the hardware requirements of the EMS.
State the software requirements of the EMS.
State the daily operations of the EMS.
Describe the Functions of EMS Site Administration
Describe the Account Management Operations
Describe the EMS & NE Configuration (MIB Creation)
MAX204SGV4.0
EMS Overview
285
EMS Activity
Purpose
This activity will give you practice in installing the WiMAX EMS, adding a WiMAX system to the EMS, and
commissioning the AP and CAPC in the EMS.
MAX204SGV4.0
286
EMS Overview
MAX204SGV4.0
EMS Overview
287
MAX204SGV4.0
288
EMS Overview
TITLE EMS Installation

Duration: 30 minutes
Purpose: to give you practice installing the WiMAX EMS
Directions: Prior to EMS installation you will need to gather system specific
information. For this lab, use the information listed below.
Your instructor will provide the required software.
Site Installation Related Parameters

These parameters are necessary for network and initial account setup for the
EMS.
Network Domain Name (FQDN): wimaxtraining.com
External VLAN ID (range = 1-2303, 2432-4094): 7
EMS IP Configuration Method (0 = Static, 1 = dynamic): 0
The following information will be required if you do not use a dynamic
configuration.
EMS IP Address (IPv4 Backhaul Interface IP address): 10.248.140.10
Subnet Mask (IPv4): 255.255.252.0
Default Gateway IP Address (IPv4): 10.248.140.1
Primary DNS Server IP Address (IPv4): 10.248.140.3
Secondary DNS Server IP Address (IPv4): 10.248.140.3
Primary NTP Server IP Address (IPv4): 10.248.140.34
EMS Address (IPv4): 10.248.129.5
Backhaul Auto negotiation (0 = disabled, speed, duplex and auto mdix are user
specified, 1 = enable auto negotiation): 1
The following information will be required if you do not use auto-negotiation.
Backhaul Duplex (0 = half duplex, 1 = full duplex):
Backhaul Link Speed (0 = 10 Mbit, 1 = 100 Mbit, 2 = 1000 Mbit):
Backhaul Auto MDI X (0 = disabled, 1 = enabled):
Enter the account name for the local admin account: Student
Enter the password for the local admin account: Student12
Enter the account name for the EMS FTP account: apftp
Enter the password for the EMS FTP account: apftp
MAX204SGV4.0
EMS Overview
289
LMT Security Certificate Related Parameters

These parameters will be used to generate the LMT Security certificate used to
provide the secure http connection between the access point LMT and a web
browser.
Country Name (2 letter code) (US is the default): US
Organization Name (eg company): Motorola
Organization Unit Name (eg section): WiMAX
Common Name (EMS Domain Name (FQDN)): wimaxtraining.com
MAC Address of the EMS backhaul interface (obtained from ifconfig a)
(example: 00:1A:66:FD:21:19):
_________________________________________
Your Observations/Notes
MAX204SGV4.0
290
EMS Overview
TITLE EMS WiMAX System Add

Purpose: to give you practice adding a WiMAX system to the EMS
Directions: Prior to adding a WiMAX system to the EMS you will need to
gather system specific information. For this lab, use the information listed
below.
Site Installation Related Parameters

These parameters are necessary for Adding a WiMAX network and Network
Elements to the EMS.
WiMAX Global Configuration Parameters
Network Access Provider ID (assigned by IEEE): 1
Quality of Service Classification (used across all access points): default,
priority = 0
Security (PKM used between CPE and access points): default values
Signaling Priority (priorities for network traffic): OAM = 0, HiPri = 6, LowPri = 4
WiMAX System Node Properties
General Node Properties.
NodeID(Given Node ID): 65536
Node name (Node name for Operator use): Training_Network
AAA Server Node Properties
AAA ID(Given Node ID): 65539
AAA name (Node name for Operator use): AAA_SERVER65539

configuration.
EMS IP Address (IPv4 Backhaul Interface IP address): 10.248.140.5
Subnet Mask (IPv4): 255.255.252.0
Primary DHCP Server IP Address (IPv4): 10.248.140.2
Primary NTP Server IP Address (IPv4): 10.248.140.6
AAA Server IP Address (IPv4): 10.248.140.4
AAA Server Port (UDP Port #): 1812
MAX204SGV4.0
EMS Overview
291
CAPC Node Properties

CAPC IP Address (IPv4 address or FQDN): 10.248.140.8
Node name (Node name for Operator use): TNGCAPC01
ID of Parent Node: 65536
MAC Address (MAC Address of the CAPC backhaul interface):
00:01:AF:16:F2:B5
CAPC Account User name (local login for diagnostics): capcuser
NAS ID (AAA client user login ID for CAPC at AAA):
Training_WiMAX_Network
AAA Authentication Key(Shared key for authentication of CAPC): TNGCAPC
AP Node Properties.
AP IP Address (IPv4 address or FQDN): 10.248.140.12
Node name (Node name for Operator use): TNG-AP12
00:E0:0C:FE:53:5F
AP Account User name (local login for diagnostics): apuser
AP Node Configuration
NAS ID (AAA client user login ID for CAPC at AAA):
Training_WiMAX_Network
AAA Authentication Key(Shared key for authentication of CAPC): TNGAP
DL/UL Bandwidth Allocation Ratio(Highest, High, Medium, Lowest): Highest
Channel Bandwidth (5Mhz, 7Mhz, or 10Mhz): 7Mhz
Base Radio Frequency: 3.5Ghz
Sector Properties
Sector ID(Given Node ID): 2
Node name (Node name for Operator use): S_0_2
00:E0:0C:FE:53:5F
AP Account User name (local login for diagnostics): apuser
Sector Configuration
Initial Ranging RSS(dBm): -85
Downlink Center Frequency (kHz): 3562500
Cell ID (Used in Downlink Preamble): 0
Permutation Base (Used for DL Zone): 0
Base Radio Frequency: 3.5Ghz
Tx Power Report Alpha P Average: 3
MAX204SGV4.0
292
EMS Overview
TITLE CAPC Site Commissioning

Purpose: To give you practice commissioning a CAPC
Directions: Prior to commissioning a CAPC you will need to gather site
specific information. For this lab, use the information listed below.
Site Commissioning Related Parameters
CAPC.
External VLAN ID (1-2303, 2432-4094): 3
CAPC IP Configuration Method (0 = Static, 1 = dynamic): 0
configuration.
CAPC IP Address (IPv4 Backhaul Interface IP address): 10.248.140.8
Subnet Mask (IPv4): 255.255.252.0
Enter the account name for the local admin account: capcadmin
Enter the password for the local admin account: capcadmin
Enter the password for the root account: root
MAX204SGV4.0
EMS Overview
293

browser.
Common Name (CAPC Domain Name (FQDN)): wimaxtraining.com
MAC Address of the CAPC backhaul interface (obtained from ifconfig
a)(example: 00:1A:66:FD:21:19): 00:01:AF:16:F2:B5
MAX204SGV4.0
294
EMS Overview
TITLE AP Site Commissioning

Purpose: To give you practice commissioning an AP
Directions: Prior to commissioning an AP you will need to gather site specific
information. For this lab, use the information listed below.
Site Commissioning Related Parameters

access point.
External Vlan ID (1-2303, 2432-4094): 7
AP IP Configuration Method (0 = Static, 1 = dynamic): 0
configuration.
AP IP Address (IPv4 Backhaul Interface IP address): 10.248.140.12
Subnet Mask (IPv4): 255.255.252.0
Enter the account name for the local admin account: apadmin
Enter the password for the local admin account: apadmin
Enter the password for the root account: root
MAX204SGV4.0
EMS Overview
295

browser.
Common Name (AP Domain Name (FQDN)): wimaxtraining.com
MAC Address of the AP backhaul interface (obtained from ifconfig
a)(example: 00:1A:66:FD:21:19): 00:E0:0C:FE:53:5F
MAX204SGV4.0
296
EMS Overview

EMS Administration
1.
When may a Backup Restore be required at the EMS?

a. EMS release has been upgraded to a newer version and the good
known database is imported
b. Current software is an older version
c. Current configuration database is bad and restoration to a good known database is needed
d. 1or2
e. 1or3
2.
It is possible to start or stop an individual EMS managed service without affecting other
managed services.
a. True
b. False
3.
The default EMS backup method is ____.

a. Offline
b. Online
c.
Current
d. Delayed
4.
Which is not a function of EMS HTTPS Management?

a. View Certificate Details
b. Generate certificate signing requests
c.
Import Certificate Authority issued Certificates
d. Enable HTTPS
e. Enable FTP
f.
5.
Export Selected Certificates

The EMS stays up during the Restore Backup process.
a. True
b. False
6.
Which is not an EMS control level for user account access?

a. Administrator
b. Operator
c.
Guest
d. All are EMS access control levels

7.
CPEs are provisioned in the AAA server, not in the EMS.

a. True
b. False
MAX204SGV4.0
EMS Overview
297
There are many WiMAX system level parameters that are defined in the Global WiMAX Settings
of the EMS. The following two questions address these system level parameters.
8.
Up to ____ WiMAX system QoS profiles may be defined in the EMS.

a. 100
b. 500
c.
1000
d. 1500
9.
If Encryption/Authentication is disabled, the CPE may enter the network without AAA server
verification
a. True
b. False
10. A CAPC node must exist before any AP can be added to the Network Topology.
a. True
b. False
11. There can be up to ___ Payload cards per CAPC.
a. 2
b. 4
c.
d. 8
e. 10
12. Each Access Point may have up to ____ sectors.

a. 2
b. 4
c.
d. 8
e. 10
13. If a CAPC MAC address change is needed the CAPC node must be deleted and re-added
a. True
b. False
14. For security reasons, only one user account can be defined for the CAPC Local Maintenance
Terminal.
a. True
b. False
15. Access Point sectors must be configured prior to configuring an Access Point.
a. True
b. False
MAX204SGV4.0
298
EMS Overview
16. To allow for maximum throughput, set the backhaul link to 10/1 00/1 000 during Access Point
a. True
b. False
17. During Auto Discovery, the IP of the CPE is assigned by the AAA server.
a. True
b. False
MAX204SGV4.0
Student Activity
299
Student Activity
EMS Operations and Maintenance
MAX204SGV4.0
300
Student Activity
MAX204SGV4.0
Student Activity
301
Objectives
At the end of this activity the student will be able to:
Describe the configuration management of global and NE parameters
Describe the system monitoring, alarm, recovery and troubleshooting operations
Describe the EMS Configuration Troubleshooting
Activity Instructions
This activity will give you the opportunity to explore the WiMAX Element
Management System. Use the following pages as a guide. Your instructor is
available to assist you.
MAX204SGV4.0
302
Student Activity
EMS Network Topology

The Portal Element Management System home page is used to start the Network Topology
management tool. The EMS Network Topology tool allows and administrator or operator to
perform the following functions:
1.
2.
3.
Fault Management
The focus of this section is look at each area of operation from the perspective that the WiMAX network is
established and in commercial operation. There will be similar tasks as described in the EMS Administration section
regarding configuration management. However in this section configuration management is performed when
network changes are needed to improve operational performance.
Network Topology Tree
The left pane of the topology manager shows a network tree structure. The parent-child relationship of each
network element node is show in a classical expanding tree format.
The node state is shown in 4 colors which are:
Green = Up
Blue = Unknown
Yellow = Impaired
Red = Down
Moving the mouse over the network element node will activate a pop up text (Tool Tip)
with the current nodes state.
The EMS reports the state information obtained from managed network elements. The
NEs that can have a state are:
CAPC & Payload Modules
AP & Sectors
The System & WiMAX Network nodes do not have node states.
MAX204SGV4.0
Student Activity
303
Network Topology
MAX204SGV4.0
304
Student Activity
Node Functions
The functions that can be performed on the node are selected by right clicking on the node.
The CAPC & AP nodes have the functions:
Node Configuration
Statistics Viewer
Event Viewer
Node Properties
Down Load Software
Launch ____ Local Maintenance Terminal
Delete this Node
Database changes are accomplished through the [Node Properties] and [Node Configuration] selections. Fault
information is view through [Event Viewer]
Performance Information is available through [Statistics Viewer]
The AP Node Functions are shown on the facing page
MAX204SGV4.0
Student Activity
305
Node Configuration
MAX204SGV4.0
306
Student Activity
Database Changes
Database changes are segmented into 3 major levels:
1. EMS
2. WiMAX Network
3. Network Element
EMS and WiMAX Network changes will have a global network

impact and will require all network elements to be
downloaded to implement the configuration changes.
EMS Properties
Fault Management tab configures the North Bound Interface and system event parameter
Performance Management tab configures collection intervals and archive durations Configuration
Management tab configures high level download management constraints.
WiMAX Network
QoS Classification configures the system QoS services which the AP
Node must match the Classifier Rule Index.
Network Element
See the EMS Administration section Node Properties and Node
Configuration for edit constraints.
Fault Management
Fault Management is supported by the Alarms and Events display window. The EMS supports a real time
status of all Network Elements (N Es). Up to 500 items (if available) can be displayed at a time on a page
(default is 50 per page). A complete listing may require multiple pages. Event collection times can be set
for 15, 30, or 60 minute intervals. The default is 30 minutes.
Alarms are assigned a severity level, and events are reported as "normal".
View Alarms
From the Launch Page select the Alarm Bell icon. A new window will display
in the right pane showing real time Events and Alarms.
MAX204SGV4.0
Student Activity
307
View Alarms
MAX204SGV4.0
308
Student Activity
View Alarms
Columns in this display are: Ack, Cleared, Severity, Date, Source, EMS Tag, and Details.
Each alarm can be selected and opened using a left mouse button "double-click". The desired alarm will
display additional information in regards details and suggested resolution(s).
Filters
Under the Action menu, filters can be selected for the display. Any of the above columns titles,
except Details, can be use for display filtering. Within the titles, there are finer filtering criteria.
For most filtering: Check the check boxes for the level of alarms you want to view. Uncheck the
boxes for those you do not want to view.
The Severity filter includes: Critical, Major, Minor, Warning, Normal, Acked, and Cleared. Note that
each of these is assigned a color on the display.
The Source filter uses the main display. The operator selects rows that match the
data in the source column.
The Date filter is simply setting a beginning and end time to view.
For both the Ack and Clear filters, selecting the option displays only those items with check
marks in the Ack or Cleared columns.
Ack and Clear
If an alarm or event is acknowledged, or "ack'd", the display row for that alarm or event will be greyed out and
the Ack column will have a check mark next to the alarm or event. This is not the same as being cleared. For
an alarm or event to be cleared, another event that is paired with the original should be present. (Some events
clear automatically due to the minor nature of the event.) The operator can "ack" an alarm or event, however
the EMS will clear the alarm or event.
At the bottom of the alarm display, there is a button to delete cleared alarms and events. Clicking on this
button will remove all the cleared alarms or events form the display.
Each event/alarm is displayed with Severity, Source, etc., info. Detailed information pertaining to the
event/alarm can be displayed by double clicking the event/alarm on the display.
Storage Log
Files are also maintained for the alarms and events display. These files are constructed as an event
database file. Alarms stored are 10K. Subsequent releases are planned for 100K storage. Up to
32 days of alarms and events can be saved.
MAX204SGV4.0
Student Activity
309
View Alarms
MAX204SGV4.0
310
Student Activity
Performance management is accomplished by reviewing the historical statistics of a managed network element and
making some decision with regards to the NEs configuration parameters.
Historical statistics are collections of selected events over a period of time. Statistics are displayed as quantity of
events in relation to a time period. Time periods are 15, 30, and 60 minutes.
Statistic Collection Configuration

Clicking on the chart icon with an NE node highlighted will launch the Statistics Viewer of that
NE. The stats upload (Polling) interval indicates the data collection points in time segments
which can be plotted in graphics.
MAX204SGV4.0
Student Activity
311
Statistics
MAX204SGV4.0
312
Student Activity
Statistics
Create
Upon first opening the statistics window, there is a left pane showing the various statistics. Directly underneath is a
smaller window. This is the "Queue to Plot" window. Up to five statistics can be selected, and each
selection will appear in the Queue to Plot window. Each statistic selected will be assigned a color
to be graphed. If the statistic is not desired, selecting the same statistic again will remove that statistic
from the Queue to Plot window.
View
After the desired statistics are selected, click the plot button. A new window with a graphical representation
of the selected statistics will be shown. The selection / queue / plot sequence may be repeated. Up to 20 graphs may
exist in the right pane window. A warning will appear after 10 plots are displayed. More than 10 plots is fairly hard to
analyze. To help the user analyze multiple statistics graphs, the standard cascade and tile windows function is
available from the View menu. Storage
Log files are also maintained for the statistics display
Up to 5 stats can be selected for a graphic plotting. Selected stats are plotted with different
colors. The graphic name can be defined by user.
Multiple graphics can be plotted and the displays can be tiled for comparison. The graphic definitions will be
able (in I3) to be saved per user and per NE type (AP or CAPC) for re-use.
MAX204SGV4.0
Student Activity
313
Statistics
MAX204SGV4.0
314
Student Activity
Download Software
There is a default location (directory) on EMS where NE software will be stored. Up to 5 versions
of software per NE type can be retained.
EMS will display a list of stored software of the NE type in
C:\Program Files\Motorola\PortalEMS\sftproot\softwareBundle
NE software can be imported by copying it from CD, other sources in the network Software
Download directory.
Downloading software to the CAPC or AP follow the same methods. An AP load will be
used in this example.
Two AP software versions are available to pick for AP Software Bundle Download. Select (click
on) the desired software version; click on Start Software Download (CD icon) to start the AP
Software Bundle Download.
MAX204SGV4.0
Student Activity
315
Software Download
MAX204SGV4.0
316
Student Activity
Software Bundle Download
Software Bundle Download always includes the NE Configuration Download (and it will be a NECB) so that the
NE will activate the downloaded software with a full configuration (and restart).
If no changes are required, click on Save Configuration Workspace for Software Bundle Download
As AP Configuration is mandatory as a part of AP Software Bundle Download, proceed with either Download
Configuration to Network Element or Add to Download Manager
MAX204SGV4.0
Student Activity
317
Software Download
MAX204SGV4.0
318
Student Activity
Software Download
Download Manager
NE Configuration Download can be scheduled through the Download Manager. The download
job will be pending for further instructions.
Click on the Add to Download Manager icon (the green cross) to queue the CAPC
Configuration Download.
All lock icons will stay until the download job is executed from the
Download
Manager or is aborted and deleted from the Download Manager job
queue.
Configuration Add to Download Manager

User is informed with a confirmation of the scheduling to the Download Manger. Click on
OK and then click on the Download Manger (LAN) icon to launch the Download Manger
interface to view the download jobs.
MAX204SGV4.0
Student Activity
319
MAX204SGV4.0
320
Student Activity
Configuration Downloads
All queued download jobs will be listed. They can be a mix of single NE Configuration Downloads,
Software Bundle Downloads and CPE Policy Downloads.
Click on Push Configuration/Software Download to the Network Element (green machine)
icon to initiate download for all queued jobs.
There may be dependencies among downloads where some downloads need to occur prior to
the others, e.g. parent CAPC goes prior to children APs. EMS will execute as many downloads
as it can in parallel otherwise.
The icon under the Status is automatically updated as downloads progress. The time it takes to complete a
Configuration Download varies. It can take many minutes for a Software Bundle Download.
Note that the CAPC Configuration Download job is in Pending state.
Download Pending
If a download job failed one can try to download again or cancel the download job. The NE node and all children
nodes are still in locked state until the download succeeds or is cancelled.
MAX204SGV4.0
Student Activity
321
Download Management
MAX204SGV4.0
322
Student Activity
Download Manager
Download job status will be updated as the jobs progress. User can get an immediate refresh of all job
status by clicking on the Refresh Download Manager icon (the double circular arrows).
Right clicking on a download job will allow user to either Clear Download Flag or Abort Changes. If user
wants to retain the configuration data (remain in the locked state) then select Clear Download Flag to just
remove the download job from the Download Manager. If the configuration data is to be discarded with the
cancellation of the Configuration Download then select the Abort Changes.
Download Actions
After a Configuration Download has succeeded the download job status can be removed from the list by
clicking on the Remove all Successful Downloads from Download Manger icon (the RED push button). All
pending download jobs, if any, will remain on the queue list.
All locks are removed from the NE topology icons after a successful Configuration Download.
MAX204SGV4.0
Student Activity
323
Download Actions
MAX204SGV4.0
324
Student Activity
Web LMT Configuration

The web Local Maintenance Terminal (LMT) is configured at the Network Element (NE) and the EMS. The
web LMT allows the operator to perform local management of the NE
High Level Configuration Steps
Before a user may access the LMT of the NEs a number of user names have to be added
to the system as shown below.
1.
2.
3.
4.
5.
6.
At the NE - add a Local Admin account during the commissioning of the NE

At the EMS under the CAPC [Node Properties] add the Local Admin Account user name
Bootstrapping the CAPC will populate the CAPC LMT URL under the CAPC
General tab in the CAPC [Node Properties] book
At the EMS under the AP [Node Properties] add the Local Admin Account user name
Bootstrapping the AP will populate the AP LMT URL under the AP General tab in the AP [Node
Properties] book. This will also populate the BTS Gateway field under the LMT Information tab
If the AAA server is used to authenticate the LMT user the respective CAPC and AP
Local Admin account must be configured in the AAA server
MAX204SGV4.0
Student Activity
325

MAX204SGV4.0
326
Student Activity
MAX204SGV4.0
CAPC Hardware
327
Lesson 5
CAPC Hardware
328
CAPC Hardware
MAX204SGV4.0
CAPC Hardware
329
Objectives
1. Describe the functions and makeup of the Motorola Carrier Access Point - Controller (CAPC).
2. Describe the software functions of the Motorola Carrier Access Point - Controller (CAPC).
MAX204SGV4.0
330
CAPC Hardware
Carrier Access Point - Controller (CAPC) Hardware

Functions of the CAPC
As the Motorola WiMAX solution is based upon a distributed network architecture, many of the local
management function are carried out by the DAP. However to allow for security related functions and
network mobility, Motorola has devolved this responsibility to the Carrier Access Point Controller
(CAPC). The CAPC performs the following functions:
ASN Gateway Decision Point
The CAPC performs the ASN Gateway Decision Point (ASNDP) function, by serving as a Remote
Authentication Dial-In User Service (RADIUS) client (AAA client) for authentication and authorization of
subscriber equipment requesting access to the network. As the AAA client, the CAPC is responsible
for passing subscriber information to designated RADIUS servers (AAA servers), and then acting on
the response which is returned.
Mobile IP Client
The CAPC performs the function of the Mobile IP Client on behalf of the subscriber. It uses the AAA
record information to formulate appropriate Mobile IP requests which are forwarded to the AP who
then relays these messages to the Foreign Agent on behalf of the subscriber.
Radio Resource Management
The CAPC provides a central point of management for handovers. It coordinates messaging and
lease management between access points and other CAPCs during handovers and location updates.
Paging controller and subscriber equipment location management
The CAPC owns the lease for subscribers in idle mode. This means the data path ends at the CAPC,
which is required to locate the subscriber who is in idle mode. To do this, the Paging controller function
tracks the paging region in which the subscriber currently is registered (location register).
When a packet is received by the CAPC for an idle subscriber, the CAPC buffers the packet, accesses the
paging controller information, and uses its paging function to locate the idle subscriber. To perform this function
it sends paging messages to each of the APs in the paging region. Once the subscriber equipment item is
located and returns to an active state, the CAPC forwards all buffered packets to the AP serving the subscriber.
As part of this process, the AP will obtain the data lease for the subscriber. Following downlink data path
capture by the AP, all packets will traverse the network directly to be delivered by the Access Point to the
subscriber.
MAX204SGV4.0
CAPC Hardware
331
CAPC Chassis
ASN Decision Point

P aging Controller and Location Management
MAX204SGV4.0
332
CAPC Hardware
CAPC Hardware
The CAPC is built upon the Motorola Embedded Communications Computing 1406 common platform
server and operates Monta Vista CGL (Carrier Grade Linux) OS. This product line encompasses the
hardware platform, hardware control software, middleware, and operating system environment. The CAPC is
made up of a number of sub units as listed below:
1406 CAPC Chassis.

ATCA-F101 Blades (System Controller Blades).
Shelf Management Alarm Modules (SAM).
ATCA-7221 blades (pCAPC blades).
RTM-ACTA-F101 Rear Transition Modules (RTM).
ACC-ARTM-7221/SCSI Rear Transition Modules (RTM).
Power Entry Modules (PEM).
Fan Tray Modules.
CAPC Chassis
The CAPC hardware is composed of the 1406 chassis and the items installed in the chassis, and has both
front and rear slots. There are 14 open slots in the front and 14 open slots in the rear. The front and rear
blades have to be paired correctly. Two of the 14 slots are populated with System Controller blades, while
the remaining 12 slots are populated with pCAPC blades based on the site characteristics and the operators
chosen configuration. The blades located in the rear of the chassis that are associated with the front
blades are called Rear Transition Modules (RTM) and typically they provide ports for cable connections. A
number of Power Entry Modules (PEMS) are also fitted along with Fan Tray Modules. In addition there is
space for Shelf Management Alarm Modules (SAM) at the bottom front, next to the air inlet.
MAX204SGV4.0
CAPC Hardware
333
MAX204SGV4.0
334
CAPC Hardware
ATCA-F101 Blades (System Controller Blades)

The Motorola ATCA-F101 system controller and switching blade is a key element within the Motorola
CAPC network element. This blade combines standard PICMG 3.0 base interface and PICMG 3.1 fabric
interface switching (hub functionality) with a PowerPC processor complex to support a wide variety of
applications, including shelf wide and/or frame-wide management. By combining these essential functions
on a single blade, the ATCAF101 can provide a completely redundant switching and system management
environment while consuming only two slots in the shelf, maximizing the number of slots available for
billable applications.
Features
The key features of the ATCA-F101 Blades are as follows:
MPC7447 microprocessor @ 1.0 GHz

PMC-based 40GB hard disk drive
Marvell Discovery II System Controller
512 MB ECC protected RAM
16KB NVRAM
16MB CPU reset-persistent memory
PICMG 3.0 base interface switching
PICMG 3.1 data interface switching
Front Panel LEDs

There are a number of LEDs on the front panel for use by local engineering staff as listed below:
Hard Disk Drive
green
Out of service (OOS)
red
Attention (ATTN)
amber (not used)
Hot Swap indicator (H/S)
blue
Management Ethernet
Green/Yellow (Link connectivity
= Green, Link activity = Yellow)
Front Panel Connectors

There are a number of connection ports on the front panel for use by local engineering
staff as listed below:
Mini DB-9 RS232 serial link connector console port
10/100 BaseT RJ45 Ethernet port used for management purposes
USB 2.0 port (not used)
MAX204SGV4.0
CAPC Hardware
335
CAPC F101 Blade
MAX204SGV4.0
336
CAPC Hardware
Shelf Management Alarm Module (SAM)

The purpose of shelf management, as defined by the PICMG 3.0 standard, is to assure proper operation
of 1406 blades and other shelf components within the shelf. The SAM continually monitors all low-level,
hardware functionality (inventory, sensor, status data, etc.) and reports status to the system manager.
It also provides control access to these attributes via local console and Ethernet interfaces. Each blade and
major shelf accessory has an Intelligent Platform Management Controller (IPMC) that is responsible for
providing this information to the SAM.
The 1406 shelf provides redundant shelf management functionality, utilizing an active/standby architecture. In
addition, the Telco Alarm functionality is integrated into the same module to maximize critical real estate within
the shelf, this functionality also being redundant. Visual indicators, as well as physical interfaces are
provided for direct, front panel access.
Front Panel LEDs
In Service
Critcal Telco indication
Major Telco indication
Minor Telco indication
SCSI ACT x 2
green
red
blue
On
On
On
On

Telco Alarm interface, dry relay contact, DB-15
10/100 BaseT RJ45 Ethernet port
RS-232 console
ACO (Alarm Cut Out) used to acknowledge alarms such as audible alarms
MAX204SGV4.0
CAPC Hardware
337
CAPC SAM
MAX204SGV4.0
338
CAPC Hardware
ATCA-7221 Blades (pCAPC Blades)

The purpose of the ATCA-7221 Blades is to run applications that are applicable
for data and billing services.
Features
The key features of the ATCA-7221 Blades are as follows:
Dual single core Intel Xeon LV 2.8 GHz processors running in two-way symmetric
multi-processing mode
8 GB ECC-enabled DDR2 RAM, which can be extended up to 16 GBs
72GB Serial Attached SCSI (SAS) hard drive used for storing local software and logging information
Front Panel LEDs

Hard Disk Drive
OK
ACK
User
green
red
On
On
blue
Front Panel Connectors / Switches

There are a number of connection ports and switches on the front panel for use by local
engineering staff as listed below:
Reset switch resets the payload card

10/100 BaseT RJ45 Ethernet port
2 x USB 2.0 ports not used
Serial Keyboard/Mouse port not used
RJ45 Com Port for console connection
Software Functions
The Payload card, also referred to as a pCAPC, provides the various functions such as
the paging controller, Mobile IP Function, and the Location Register functions.
MAX204SGV4.0
CAPC Hardware
339
ATCA-7221 Blades (pCAPC

Blades)
MAX204SGV4.0
340
CAPC Hardware
RTM-ACTA-F101 Rear Transition Modules (RTM)

The RTM-ACTA-F101 Rear Transition Modules (RTM) are used to transfer data to and from the
ATCA-F101 Blades (System Controller Blades) to the network.
Front Panel LEDs

Hard Disk Drive
green
red
In Service (IS)
green
Attention (ATTN)
amber (not used)
blue
Ethernet
Green/Yellow (Link connectivity
= Green, Link activity = Yellow)

8 x 10/100 BaseT RJ45 Ethernet port for Fabric Uplink connections
4 x 10/1 00 BaseT RJ45 Ethernet port for Base Link connections
10/100 BaseT Management RJ45 Ethernet port (console port)
MAX204SGV4.0
CAPC Hardware
341
F101 - RTM
MAX204SGV4.0
342
CAPC Hardware
ACC-ARTM-7221/SCSI Rear Transition Modules (RTM)

The ACC-ARTM-7221/SCSI Rear Transition Modules (RTM) are used to transfer data to and
from the ATCA-7221 Blades (pCAPC Blades) to the network.
Front Panel LEDs

There are a number of LEDs on the front panel for use by local engineering as listed below:
Hard Disk Drive
OK
ACK
Ethernet x 2
SCSI ACT x 2
green
red
On
On
blue
On
On
Front Panel Connectors / Switches

There are a number of connection ports and switches on the front panel for use by local
engineering as listed below:
USB 2.0 port

Serial Keyboard/Mouse port
2 x 10/100 BaseT RJ45 Ethernet port
2 X RJ45 Comm ports
4 X E1/T1 ports
Reset switch
SAS connector
2 x SCSI connectors
MAX204SGV4.0
CAPC Hardware
343
ACC-ARTM-7221/SCSI Rear Transition Modules (RTM)
7221 - RTM
MAX204SGV4.0
344
CAPC Hardware
Power Entry Modules (PEM)

Power conditioning for the 1406 shelf is provided by a pair of redundant PEMs. They provide wiring
studs for connection to redundant 40 VDC to 72 VDC (-48 VDC nominal) power sources and
provide power to the backplane on the redundant 48 VDC power rails for blades and other shelf
components. Operating with internal redundant fans they deliver 100 amp maximum capacity via five
(5) 25 amp circuit breakers.
The PEMs are hot-swappable and when using 200W per slot PEMs, two are required to support
N+1 redundancy. If the system is configured for redundant operation using two power supplies, they
operate in load sharing where the total load is equal to or less than what one power supply can
provide. The CAPC can operate at 200W per slot capacity with one PEM installed however this
would not be a redundant configuration.
Fan Tray Modules

The 1406 shelf provides fault-tolerant cooling to all front blades and RTM slots in an N+1 cooling architecture that
is implemented using eight hotswappable fan tray modules; six on the top (3 front and 3 rear) of the shelf
and two at the bottom front. Each fan tray module has redundant fans and a complete IPMC complex to
interface with the shelf management entity. The Front blade cooling capacity is 200 watts per blade while the
RTM blade cooling capacity is 25 watts per blade. The fan tray modules are fitted with an automatic fan speed
control and operate in the range of 0 C to 40 C.
Front Panel LEDs
There are a number of LEDs on the front panel for use by local engineering as listed below:
In Service
green
red
blue
MAX204SGV4.0
CAPC Hardware
345
Black
Red
PEM
MAX204SGV4.0
346
CAPC Hardware
CAPC Hardware Redundancy

The CAPC has been designed to be a High Availability platform with a performance better than 5-NINES
(99.9995%). Recovery from a failure is expected to be within 30 seconds. With no planned downtime, the
CAPC will continue to provide service during software upgrades with both the hardware and software
components designed for full redundancy.
Hardware Redundancy Model
The CAPC uses a 2N redundancy model, in that each System Controller, pCAPC and Shelf Manager has
a redundant peer. In fact the CAPC Standard configuration requires redundant peers. Devices will
continue to provide service after the failure of the primary device, but will not provide service after a
second fault of the same device pair. The pairing of the cards can be seen on the diagram on the
facing page. In the event that a CAPC FRU can no longer provide service, a failover will be initiated by
the CAPC application code or NCS middleware. On CAPC failover the external IP address is activated
on the redundant pCAPC allowing the AP to reinstate the connection on the provisioned IP address on
the standby card
Hardware Faults These faults are detected and managed by Shelf Controller module (fans,
PEM, temperature) and a hardware fault on a System Controller or pCAPC will cause a
failover to the redundant card.
Software Faults The NCS middleware will detect the failure of a CAPC software component via the use of
a heartbeat system and a software component can initiate a failover if it can no longer provide its intended
service. A critical software fault will cause the faulted board to reset. Reboot and recovery of the board will
be monitored by the EMS via State Change Events.
Fault Recovery In most circumstances a faulted boards will auto-recover from general software
faults and will on recovery insert itself in the Standby role. Hardware faults however, will cause the
faulted board to stay in a Down state if it can no longer go in-service. A faulted board can be hot
inserted with automatic recovery.
MAX204SGV4.0
CAPC Hardware
347
Hardware Redundancy Model
Logical
Slots
11
13
10
12
14
Payload 7221
Empty
Payload 7221
Payload 7221
Payload 7221
Payload 7221
Payload 7221
Empty
10
11
12
13
Active
Standby
F101
Payload 7221
Payload 7221
Payload 7221
Payload 7221
F101
Physical
Slots
14
pCAPC 1
pCAPC 2
App1
App2
Faiover Path
Checkpoint Data
IP A.B.C.D
IP A.B.C.D
Access Point
MAX204SGV4.0
348
CAPC Hardware
Power Distribution Redundancy Model

To protect against Power Entry Module (PEM) outages causing service interruptions, the PEMs are
configured in a load sharing arrangement, with each PEM capable of carrying the entire shelf power load.
A second level of power redundancy is provided by the way the PEM circuit breakers are assigned to the
blade slots and shelf modules. -48Vdc power is presented to both PEM-A and PEM-B. Each PEM has
four 25 amp circuit breakers (A1-4 and B1-4) delivering -48Vdc to blade slots 1 through 14 as shown in the
drawing below. A 15 amp breaker (A5 and B5) provides -48Vdc to the FTM modules. 12Vdc is provided
to the SAM, PEM and FTM modules. The fuses (C1 and D1) on the 12V sources are not field
replaceable.
Physical slot 1, where the System Controller blade is installed, receives power from the first breaker on
PEM-A, and the first breaker on PEM-B (shown on the drawing as A1 and B1). Notice that Physical slot
14, where the redundant System Controller blade would be installed, receives power from A4 and B4.
With this arrangement the loss of PEM-A or PEM-B will not interrupt the operation of the active or standby
System Controller. Likewise, the loss of breaker A1, A4, B1 or B4 will not interrupt the operation of either
System Controller. Obviously, multiple PEM or breaker failures may impact service.
FTM - 6
A5
Power
Segments
B5
C1
D1
A5
FTM - 1
A5
Power
Segments
C1
D1
A5
D1
A5
B5
C1
C1 D1
FTM - 3
FTM - 2
C1
B5
D1
A5
B5
C1
D1
2
3
3
5
4
7
5
9
6
11
7
13
8
15
9
4
10
6
11
8
12
10
13
12
14
14
15
16
16
2
A1
B1
A2
B1
A2
B2
A1
B2
A1
B3
A2
B3
A2
B4
A1
B4
A3
B4
A3
B1
A4
B1
A4
B2
A3
B2
A3
B3
A4
B3
A4
B4
HUB - B
ATCA
Blade
Slots
B5
B5
HUB - A
Physical
Logical
1
1
FTM - 4
FTM - 5
B1
Power
Supplies
B2
B3
B4
B5
A1
D1
A5
B5
C1
D1
C1
A4
A5
PEM - A
FTM - 8
SAM - A
FTM - 7
A3
C1
PEM - B
Lower
SAM- A, B
FTM - 7, 8, 9
A2
D1
A5
B5
C1
FTM - 9
SAM - B
D1
C1
D1
A5
B5
C1
D1
Power Distribution Redundancy Model
MAX204SGV4.0
CAPC Hardware
349
CAPC Capacities
The Motorola CAPC product also offers support for various market sizes and growth trends The
CAPC scales from its smallest to the largest configuration in 5 (20%) increments and CAPC
capacity increases are executed by inserting additional payload cards. The table below shows the
capacities for various CAPC configurations.
Smallest
CAPC
Configuration
Initial System Release
Deployment
Availability
(including scheduled
downtime)
Physical Payload cards
(deployed as 2N
availability)
Total Ethernet Ports
Maximum AP Database
Capacity
Maximum CPE Database
Capacity
WMX1.0
WMX2.0
Maximum
CAPC
Configuration
WMX1.0
WMX2.0
99.9995%
99.9995%
10
4 1.0
8 2.0
200
4 1.0
24 2.0
1,000
200,000
1,000,000
MAX204SGV4.0
350
CAPC Hardware
CAPC Software
Software Functions / Interfaces
The CAPC has a number of software functions, which use a variety of standard and propriety interfaces that allow it
to communicate with internal and external devices. These interfaces are listed below.
Portal-EMS This interface may be SSH or, SNMPv3 using CNEOMI-Lite agent
and provides for FCAPS capabilities.
LMT/CLI This interface is supported via a web server using HTTPS and is used
for basic configuration and troubleshooting.
CPE This interface provides an IPSec transport service and is used for CPE
authentication mobility functions.
DHCP/DNS This interface is used during start-up to determine the CAPC IP
addresses and to resolve AP names to IP addresses.
AAA This Optional IPSec transport/tunnel is used for CPE validation and user
validation for LMT/CLI interfaces. The AAA server can provide CPE/user authentication
functionality, proxy to another AAA or support both functions.
All cards within the CAPC chassis come complete with software package. This package
contains two software forms:
MontaVista CGL 4.0This is a standard Carrier Grade Linux (CGL) distribution
and includes all required Linux Support Packages (LSPs) to support the blades,
as well as an assortment of user applications.
Basic Blade Services This software is provided to enable a set of ATCA hardware
and software components to exist as a fully integrated and verified telecom
platform. The services it will provide are as follows:
Hardware Platform Management including local IPMC, LED,

EKeying and blade extraction software.
Firmware upgrade utility
Local management access (SNMP, CLI)
Open HPI support Centralized access to blade specific HPI information from the
shelf manager and presentation to a higher level systems management
application.
Switch management software Includes hardened network drivers, default

network configuration scripts and network configuration tools.
MAX204SGV4.0
CAPC Hardware
351
CAPC Software
Software Functions / Interfaces

Portal
EMS
AP
LMT/CLI
CPE
DHCP/DNS
AAA
CAPC
MontaVista CGL 4.0
Basic Blade Services
Software Functions/Interfaces
MAX204SGV4.0
352
CAPC Hardware
CAPC Transport Communications

The CAPC transport communication is carried out by two switching fabrics.
Base Interface Switch This is a switching fabric that is used to allow control information
to be passed internally within the CAPC. It consists of a Gigabit Ethernet, Dual Star
Configuration system that is PICMG 3.0 compliant.
Internal Network Configuration

Internal Base Interface Switch A
F101
Empty
Payload 7221
Payload 7221
Payload 7221
Payload 7221
Payload 7221
Empty
Payload 7221
Payload 7221
Payload 7221
Payload 7221
Payload 7221
F101
Internal Base Interface Switch B
Internal Network Configuration
MAX204SGV4.0
CAPC Hardware
353
CAPC Transport Communications

Fabric Interface Switch This is a switching fabric that allows the CAPC to communicate
with external Network Elements via the payload cards. It consists of a Gigabit Ethernet,
Dual Star Configuration system that is PICMG 3.1 compliant.
External Network Configuration

External Switch A
F101
Empty
Payload 7221
Payload 7221
Payload 7221
Payload 7221
Payload 7221
Empty
Payload 7221
Payload 7221
Payload 7221
Payload 7221
Payload 7221
F101
External Switch B
External Network Configuration
MAX204SGV4.0
354
CAPC Hardware
CAPC Master Bootstrap Procedure

The purpose of the bootstrap procedure is to allow the CAPC to establish a secure SNMPv3 communication
link with the EMS and is carried out by an exchange of secure key information as part of the
commissioning procedure. When the CAPC is first installed and powered up, the local engineer should
login to the root account and run the master bootstrap script. Once this has executed the following
information is required:
Dynamic or Static transport configuration (note if static selected then more information is required)
New root password
New local admin account
Bootstrap account
Engine Id
When the bootstrap is complete and secure communication is established with the EMS, the
CAPC will reboot. When the CAPC has fully rebooted, the Operator may begin the software
download form the EMS.
CAPC Software Download

The actual software download for the CAPC is carried out by the network operator at the
EMS and consists of three stages
Download
The active CAPC System Controller will download a RedhatTM Package Manager (RPMTM) file from
the Motorola software server which is then stored in a temporary location on the active System
controller. The RPM file has the new software and other files in it.
Prepare
The active CAPC System Controller unpacks the RPM file, verifies the digital signatures of the RPM contents, and
audits the current CAPC configuration to determine if the installation can proceed.
Activate
The active System Controller performs a rolling upgrade procedure to install the new software on all the
blades in the CAPC. This rolling upgrade procedure will allow the CAPC to continuing functioning,
while the new software is being installed.
Successful Installation
The CAPC sends the procedure status to the EMS at various times during the software installation. The
software installation is considered successful when the new software has been installed on both System
Controllers and on at least one ATCA-7221 blade from each mated pair.
MAX204SGV4.0
CAPC Hardware
355
CAPC Software
Install & Power On
CAPC
Commission CAPC
Bootstrap CAPC
Bootstrap successful
Install
Software
Download
Prepare
Activate
MAX204SGV4.0
356
CAPC Hardware
Lesson Summary
Describe the functions and makeup of the Motorola Carrier Access Point Controller (CAPC)
Describe the software functions of the Motorola Carrier Access Point Controller (CAPC)
MAX204SGV4.0
CAPC Hardware
357

1. The CAPC is designed to support up to _____ APs on a single chassis.
a. 100
b. 256
c. 1000
d. 1024
2. The purpose of the CAPC Master Bootstrap procedure is to allow the CAPC to establish a
secure SNMPv3 communication link with the EMS.
a. True
b. False
3. Which switching fabric is used to pass control information internally within the CAPC?
a. Base Fabric Switch
b. Internal Fabric Switch
c. Data Fabric Switch
d. Ethernet Fabric Switch
4. One logical IP address is assigned to the active and standby system controller pair.
a. True
b. False
5. In the event of a failover of the System Controller card, a new IP external address is assigned to
the new active System Controller card.
a. True
b. False
6. Applications for data and billing services run on the _____.
a. SAM
b. pCAPC
c. System Controller
d. RTM
7. The CAPC uses a 2N redundancy model; each System Controller, pCAPC and SAM has a
redundant pair.
a. True
b. False
MAX204SGV4.0
358
CAPC Hardware
MAX204SGV4.0
CAPC Commissioning, Bootstrapping, and Troubleshooting
359
Lesson 6
CAPC Commissioning,
Bootstrapping, and
Troubleshooting
MAX204SGV4.0
360
CAPC Commissioning, Bootstrapping, and

Troubleshooting
MAX204SGV4.0
361
Objectives
1.
2.
3.
4.
5.
State the pre-site commissioning procedures to be used to install the CAPC in a chosen location.
State and demonstrate the Field Commissioning procedures of the CAPC.
State and demonstrate the configuration procedures for the CAPC
State and demonstrate the software upgrade procedures of the CAPC.
State and demonstrate the methods to be used when troubleshooting the commissioning of the
CAPC.
1. Verify proper installation of CAPC hardware
2. Verify proper installation of CAPC software and NCS middleware
3. Perform the proper CAPC power on procedure
4. Observe CAPC LEDs to determine equipment status
5. Bootstrap the CAPC
6. Discover CAPC payload sets
7. Discover CAPC payload modules
8. Download CAPC configuration
9. Download CAPC software
MAX204SGV4.0
362

Troubleshooting
Introduction
The initialization of the CAPC node is performed in four specific steps:
Commissioning
Bootstrapping
Payload Discovery
Software and Configuration Download
Before attempting these steps, verify that the CAPC hardware, software and middleware have
been installed correctly and that the node is powered up. The CAPC must be provisioned in the
EMS for the bootstrapping and download phases to be completed.
Commissioning
The purpose of the commissioning procedure is to set up the CAPC so that is may communicate
with the EMS. Basic communication variables must be established so that the CAPC can
establish contact with the EMS and the bootstrap process can proceed.
Bootstrapping
Once commissioning has been completed and network connectivity has been verified,
communication with the EMS can be established. During the bootstrap process the EMS and the
CAPC exchange security key information. Only when this step is successful may the payload
discovery process take place and the configuration be pushed to the CAPC.
Payload Discovery
Once secure communication has been established through the bootstrap process, the EMS may
then discover the installed CAPC payload sets and add them to the topology database. At that
point, the CAPC configuration may be defined and pushed to the CAPC and if necessary a
software download may take place.
Downloading
Once commissioning, bootstrapping, and payload discovery are complete, the operator may push
down and configuration load from the EMS, and if required a software upgrade to the CAPC.
MAX204SGV4.0
363
CAPC Installation Verification

The CAPC should arrive on site with all units and component parts fitted (apart from the cables). It
is generally a good practice to carry out an inventory check to ensure that the hardware
installation and software installation have been carried out correctly. Verify that the correct
items have been supplied, they are installed in the correct slots and that they are undamaged. In
addition the basic operating system, application software and middleware should have also been
installed before shipping and should be verified for correct version and revision number.
CAPC Configurations
The CAPC may be installed in a number of different configurations dependent upon the operators
requirements, however it generally consists of a basic configuration plus a number of additional
payload cards. In all cases it requires a 48VDC input
Power
48VDC power
Basic Configuration
CAPC chassis
Two ATCA-F101 blades also called System Controller blades
Two Shelf Management Alarm Modules (SAM)
Two ATCA-7221 blades also called pCAPC blades
Two RTM-ATCA-F101 Rear Transition Modules (RTM) associated with the ATCA-F101 blades
Two ACC-ARTM-7221/SCSI Rear Transition Modules (RTM) associated with the ATCA-7221 blades
Two Power Entry Modules (PEM)
Eight Fan Tray modules
AXP-F-PANEL
AXP-R-PANEL
Ground cable
2 black power cables
2 red power cables
8 RJ 45 Ethernet cables
Options
Up to ten ATCA-7221 blades also called pCAPC blades

Up to ten ACC-ARTM-7221/SCSI Rear Transition Modules (RTM)
associated with the ATCA-7221 blades
8 wire cable with RJ45 fitment at one end (number is site dependent)
A number of mini 9 pin D type connectors and cables for terminal use
For a list of tools and

procedures that required for
the installation, please refer
to the CAPC Hardware
Installation Manual
68P09277A58-4.
MAX204SGV4.0
364

Troubleshooting
Verifying the Front Blade Placement

The object of this procedure is to verify that the front blades of the CAPC chassis are in the correct slot.
Blades to Verify
The following blades are to be verified:

ATCA-F101
Shelf Management Alarm Module
ATCA-7221
The following tables show the slot-to-blade association for the front blades which are
installed in the front of the CAPC chassis based on the Physical Slot number. The 7221
blades must be installed in pairs starting at slot 2 and going to the right. The location
of the mated blade is based on the logical slot number.
Blade Type
Physical
Slot
1
F101
Blade Type
Logical Physical
Slot
Slot Pairs
1
14
F101
Logical
Slots
2
2
3
7221
7221 or Filler Panel
3
5
8
9
7221
7221
4
6
10
7221
11
7221
10
11
12
7221
12
7
8

7221
13
4
13
2
7221
7221
14
3
9
10

6
8
3
4
7221
7221
5
7
11
10
7221
12
12
7221
11
13
14
7221
13
14
F101
F101
MAX204SGV4.0
365
CAPC Hardware Verification Procedure
O O
S
S
H
S
S
4
K
ME
F1 01
Slot 14
F1 01
Slot 1
7221
Slot 2
7221
Slot 8
CR
CR I
MAJ
MAJ
MIN
MIN
OOS
OOS
IS
IS
H/S
SAM 1
H/S
SAM 2
MAX204SGV4.0
366

Troubleshooting
Verifying the Rear Transition Modules (RTM) placement

The object of this procedure is to verify that the RTMs of the CAPC chassis are in the correct slots.
Blades to Verify
RTM-ACTA-F101
ACC-ARTM-7221 /SCSI
The front blade and the RTM are a mated pair. The blade installed in the front determines the type of
RTM installed in the back and they must be installed in the same physical slot number.
Physical
Slot
1
2
3
RTM Blade
RTM-ACTA-F101
ACC-ARTM-7221/SCSI
ACC-ARTM-7221 /SCSI
or Filler Panel
Physical
Slot Pairs
14
RTM
RTM-ACTA-F101
Logical
Slots
1
8
9
ACC-ARTM-7221/SCSI
ACC-ARTM-7221/SCSI
3
5
ACC-ARTM-7221 /SCSI
or Filler Panel
10
ACC-ARTM-7221/SCSI
ACC-ARTM-7221 /SCSI
or Filler Panel
11
ACC-ARTM-7221/SCSI
ACC-ARTM-7221 /SCSI
or Filler Panel
12
ACC-ARTM-7221/SCSI
11
ACC-ARTM-7221 /SCSI
or Filler Panel
13
ACC-ARTM-7221/SCSI
13
8
9
ACC-ARTM-7221/SCSI
2
3
ACC-ARTM-7221/SCSI
ACC-ARTM-7221/SCSI
4
6
ACC-ARTM-7221 /SCSI
or Filler Panel
10
ACC-ARTM-722 1/SCSI
or Filler Panel
ACC-ARTM-7221/SCSI
11
ACC-ARTM-722 1/SCSI
or Filler Panel
ACC-ARTM-7221/SCSI
10
12
ACC-ARTM-722 1/SCSI
or Filler Panel
ACC-ARTM-7221/SCSI
12
13
ACC-ARTM-722 1/SCSI
or Filler Panel
ACC-ARTM-7221/SCSI
14
14
RTM-ACTA-F101
RTM-ACTA-F101
MAX204SGV4.0
367
F101 RTM
F101 RTM
Slot 14
Slot 1
7221 RTM
Slots 2 and 8
MAX204SGV4.0
368

Troubleshooting
Blade Insertion & Extraction

During the commissioning of the CAPC, the operator may be required to remove the blades in
the front and rear of the CAPC chassis and then reinsert them.
If the system is powered up and running, blades must be deactivated from the SAM module
interface or via the NCS command line at the system controller interface, before physically
removing them from the CAPC chassis. The procedure for carrying this out is stated below:
Deactivating CAPC Blades
When Payload or Standby System Controller needs to be deactivated. The following
commands should be used to deactivate the cards from the active F101 ncscli:
root@CAPC1004-F101:~# ncscli
NCS> en
NCS# conf t
NCS-config# avsv
NCS-config -avsv# admreq 2/<payload 1 slot number> operation shutdown
NCS-config -avsv# admreq 2/<payload 2 slot number> operation shutdown
NCS-config -avsv# admreq 2/<standby SCXB slot number> operation shutdown
After issuing these commands the operator should see the cards requested transition to an
inactive state and the Hotswap indication light should turn on indicating that the cards are ready
to be extracted.
MAX204SGV4.0
369
Blade Extraction
When removing blades from the chassis for any reason, Motorola strongly recommends that you
use an antistatic wrist strap and a conductive foam pad when installing or upgrading a system.
The procedure for removing and inserting blades is stated below:
1.
Using the torque wrench and appropriate bit, loosen the faceplate screws
that secure the blade to the chassis.
2.
Compress the handles and move them to the outward position.
3.
Carefully pull the handles to extract the blade.
Blade Insertion
1.
2.
Determine which blades go in which slots.

Ensure that the top and bottom injector handles are in the outward position.
3. Insert the blade into the chassis by placing the top and bottom edges of the blade
in the blade guides of the chassis. Align the edges of the blade with the blade
chassis rail guides in the appropriate slot. Hold the blade by the handles and do
not exert unnecessary pressure on the faceplate.
4. Grasping the handles, apply equal and steady pressure as necessary to carefully slide the
module into the blade chassis rail guides. Continue to gently push until the blade connectors
engage with the backplane connector. Do not force the blade into the backplane slot.
5. Hook the lower and the upper handle into the shelf rail recesses.
6. Fully insert the blade and lock it to the shelf by pressing the two components of the lower
and upper handles together and moving the handles towards the faceplate.
7.
8.
To fully seat the handle, hold the front part of the handle and gently move it
towards the faceplate until a click is heard.
Using the torque wrench and appropriate bit, tighten the faceplate screws to secure the
blade to the shelf.
MAX204SGV4.0
370

Troubleshooting
Blade Extraction and Insertion
MAX204SGV4.0
371
CAPC Power on Sequence

The power on sequence for the CAPC is as follows:
Ensure all cards and units are correctly fitted to the CAPC chassis.
Physically check all power and grounding cables connected to the CAPC for
serviceability.
Ensure the 48V dc supply is set to on at the customer premise power
equipment.
Select to on all circuit breakers on Power Entry Module A.
Select to on all circuit breakers on Power Entry Module B.
Ensure all fans, Power Entry Modules and cards operate normally.
All cards and units correctly fitted

Check power and grounding cables
48V dc supply is set to on at CPE power equipment
Power Entry Module A circuit breakers on
Power Entry Module B circuit breakers on
Fans, Power Entry Modules and cards operating normally
MAX204SGV4.0
372

Troubleshooting
WiMAX Network Element Configuration Dependencies

The WiMAX system must be defined before system nodes may be added. A CAPC node must exist in the
topology and Payload Sets discovered before the bootstrap process for the CAPC can happen or any APs
can be added to the Topology.
APs are associated with a Payload Set of a CAPC and are added at the Payload Set level of CAPC. A
Payload Set may contain up to 2 Payload Modules. Payload Sets and Payload Modules are discovered
by the Inventory function provided by CAPC.
Payload Sets and Payload Modules are established in the Topology by invoking the Discover
Payload (via obtaining the CAPC FRU inventory data) at CAPC level. Bootstrapping is required for any
additions of CAPC and AP. SFTP is employed for transferring bootstrap info between EMS and CAPC or
AP. It is essential that the SFTP account id and password are in sync among EMS and NEs
Due to the dependency of APs and CAPC/Payload Set, the following order must be employed
to construct a WiMAX Topology with CAPCs and APs:
7.
8.
9.
10.
11.
12.
13.
14.
Add a CAPC
Bootstrap the CAPC
Discover the Payload Sets and Payload Modules of the CAPC
Configure the CAPC and Payload Modules
Push the configuration
Add an AP to a Payload Set
Add AP Sectors
Bootstrap the AP
15. Configure and push the configuration

CAPC & AP Configuration Rules
There can be up to 5 Payload Sets per CAPC.
Each Payload Set may contain one or two Payload Modules (Active and Standby modules).
200 APs can be added to a Payload Set (database capacity). However realized AP capacity is a
function of the offered MSS traffic profile and could be less than the maximum database capacity.
Up to four Sectors can be added to an AP.
APs can also be moved from one Payload Set to another Payload Set within a CAPC or
to a Payload Set of a different CAPC. This is called AP Re-parenting.
MAX204SGV4.0
373
WiMAX Network Element Configuration

Dependencies
Define WiMAX system
Add a CAPC
Bootstrap the CAPC
Discover the Payload Sets and Payload Modules of the CAPC
Configure the CAPC and Payload Modules
Push the CAPC configuration
Add an AP to a Payload Set
Add AP Sectors
Bootstrap the AP
Configure and push the AP configuration
MAX204SGV4.0
374

Troubleshooting
CAPC Commissioning and Bootstrapping

Assumptions and Dependencies
General Assumptions
When Beginning the CAPC commissioning and bootstrapping procedure, a number of initial assumptions
must be made. For example:
I is assumed that the CAPC hardware has been properly installed per the expected configuration.
It is assumed that the CAPC has been installed with the current Trial Pack or Deployment SW.
It is assumed that the PortalEMS software has been installed with the latest version of
SoftWare, but has not had the CAPC added or configured.
It is assumed that the software bundles necessary to upgrade the CAPC are
readily available.
It is assumed that Network connectivity is available for all devices and each device is
pingable from the Portal EMS.
It is assumed that the Operator has access to all of the requisite information to carry out the bootstrap
function to include all necessary addresses and required parameter settings.
MAX204SGV4.0
375
Procedural Work Flow for Commissioning and Bootstrapping
MAX204SGV4.0
376

Troubleshooting
MAX204SGV4.0
377
CAPC Bootstrapping Set Up

For bootstrapping to successfully occur, the CAPC must first have the NCS middleware correctly
installed. The CAPC when delivered to the customer should already be configured with this
middleware, however the customer should verify that this is correct.
Prerequisites
The following list states the prerequisites for the bootstrapping procedure:
Hardware installation procedure is complete.
All necessary cabling has been completed for the backhaul.
Required Equipment
The following list states the required equipment for the bootstrapping procedures:
Laptop with a DB9 serial port installed running Terminal Emulation Software.
Serial Cable DB9 Male to DB9 female cable
Category 5 or greater Ethernet cable.
Required Software
The following list states the required software for both procedures:
Microsoft Internet Explorer version 6 or later or equivalent Java enabled web browser.
Terminal emulator software such as Hyperterminal or Procomm.
PC Terminal Configuration
The terminal software being used should be configured as follows for use on comm. port 1 for
interfacing with SAM Module interface:
115200 baud
8 bit data
no parity
1 stop bit
no flow control
Please note that the terminal software being used will be configured for a slightly different port
speed for use on comm. port 1 for interfacing with all other serial interfaces and should be
configured as follows:
9600 baud
8 bit data
no parity
1 stop bit
no flow control
MAX204SGV4.0
378

Troubleshooting
CAPC Bootstrapping
The purpose of the bootstrapping procedure is to allow the CAPC and the EMS to exchange secure key
information. This will then allow the EMS to download software and configuration files to the CAPC.
Usually the network operator will carry out the bootstrap procedure from the EMS, however for the
purpose of understanding; the procedure will be explained in this courseware. There are a number of
steps involved with this process, which are listed below:
Pre Bootstrapping steps
Adding the CAPC
Verification of the Bootstrapping procedure
Discovering the CAPC Payload cards

To ensure that the CAPC is capable of carrying out the bootstrapping procedure, a number
of steps have to be achieved. These are as follows:
The EMS Operator has the ability to access the CAPC as root via a remote terminal using
Secure Shell (login as root is not allowed using this method).
The CAPC has the NCS middleware installed.
The operator is able to successfully ping the EMS from the CAPC.
NCS Middleware Verification
The bootstrapping procedure can only be executed if the NCS middleware has been installed on
the CAPC. To verify this, the operator should carry out the following procedure:
Connect a serial cable from the laptop to the active F101 card front panel serial port.
Run the command rpm -qa I grep ncs to check the NCS version.
Run the command ps -e I grep ncs I wc to check that all NCS processes are running.
Run the command rpm -qa I grep wimax to check the CAPC software version
Determining IP and Mac Address configuration

From the CAPC Controller, determine the IP and MAC Address for the EMS-CAPC
Configuration and make note of configured addresses for use at the EMS.
Run the command ifconfig bond1
This document assumes access to the Network Elements is readily available as

no instruction to that end is given.
MAX204SGV4.0
379
CAPC Field Commissioning and Bootstrapping
MAX204SGV4.0
380

Troubleshooting
Adding the CAPC

Before the operator can continue with the bootstrapping procedure, a CAPC must first be added at
the EMS. A CAPC node is added to the WiMAX Topology at the WiMAX level.
Using the EMS Topology Manager, right click on the WiMAX System icon and choose Add CAPC.
The Add Node (Node Properties) window for the CAPC is launched with the following tabs:

CAPC General
Node Information
FRU
Interfaces
CAPC IPSec Policy Data
Internal Devices
Primary Device Information
General AP Configuration
MAX204SGV4.0
381

General Node Properties tab
When the add CAPC window launches it will bring up the General Node Properties tab first. The
operator will need to enter the following information:
IP address of the CAPC
Node name
MAC address of the Active F101 System card
CAPC IP Address will need to be entered at this screen and specifies the address
of the fully qualified domain name of this node.
CAPC Node Name can be edited from this screen a mnemonic name for this
node which is for operator use (minimum name length is 7 digits maximum
length is 65 digits).
The CAPC MAC Address is used to establish the SNMP Engine ID for secure
SNMP communication between EMS and the CAPC. The MAC address of the
CAPC must be known in advance and cannot be changed once the CAPC node
is added to the Topology. This information is obtained when commissioning the
CAPC.
Warning
If a MAC address change is needed the CAPC node must

be deleted and re-added
MAX204SGV4.0
382

Troubleshooting
CAPC General tab

CAPC LMT URL - is automatically populated after CAPC Bootstrapping. This will be the URL used
to launch the web based Local Maintenance Terminal from the CAPC Node menu selection.
SNMP Engine Id is automatically generated once the CAPC Node is added. This value
will be needed for the CAPC Bootstrapping operation.
Node Information tab Contains information about CAPC physical components.
FRU tab - Contains CAPC physical FRU information.
Interfaces tab This is a list of interface entries.
CAPC IPSec Policy Data tab This table is supported for System Controllers and
Payload Cards
Internal Devices tab This table is for non-EMS state managed devices managed by
the CAPC
Primary Device Information tab This table contains device information for the AP.
Each of these tabs is of the read-Only group and is updated from the inventory data obtained from the
CAPC after a CAPC bootstrap or later when EMS requests an Inventory Sync.. The information in
these fields is and is present for management purposes and will be populated automatically upon
Bootstrap.
MAX204SGV4.0
383
CAPC Properties at the EMS
MAX204SGV4.0
384

Troubleshooting
Local Admin Accounts tab

Account username
Role
These are the account names used to log in to the CAPC and specify user access level and
permissions. The CAPC will ask the AAA Server to authenticate these login accounts. More than
one user account can be defined for the CAPC Local Maintenance Terminal (LMT).
AP General Configuration tab
Lease Retain Time(s)
These parameters specify attributes for services provided by the AP and specify the length of
time an AP will retain the lease for an MSS who has gone idle before relinquishing that lease
control to the CAPC.
When all of the required data for each of these tabs has been added, the data should be saved
by selecting the save icon. If the information has been saved correctly, the operator should
then be able to select the CAPC General tab and obtain the SNMP engine id. It should be noted
that this information is derived from the MAC address of the Active F101 Card.
Once a CAPC node is added to the WiMAX Topology, an icon representing the CAPC is shown
on the Topology tree. The CAPC state management will not begin until after the CAPC has
bootstrapped. The icon is in grey color and no status info available yet.
A small down arrow marked on the CAPC icon means a configuration download is required.
MAX204SGV4.0
385
CAPC Properties at the EMS
MAX204SGV4.0
386

Troubleshooting
CAPC Bootstrapping
To carry out the bootstrap procedure, the operator will require the following information:
The SNMP engine ID from the EMS.

The bootstrap ftp user name for the EMS.
The bootstrap ftp password for the EMS.
The EMS IP address
The active F101 card IP address
When the above information has been obtained, the operator should login to the
CAPC at the system controller card and run the following command:
/usr/app/capc/app/script/nm_bootstrap_info.sh. When prompted enter the
information obtained in the above list.
Enter
Enter
Enter
Enter
Enter
user name(ex. root ):apftp

passwd for apftp (ex. root ):apftp
EMS ip addr (ex. 10.19.175.130 ):10.19.183.38
key (ex. 800000A10300E00CF9F214 ):800000a1030001af16f2b5
the NE IP addr(IP for this SCXB) (ex. 10.19.175.xxx ):10.19.183.98
Having run this command, the operator is to wait five minutes and then follow the validation
steps below to confirm bootstrapping is complete on both the CAPC and the EMS before
proceeding with the software and configuration downloads
Note - After the following validation, the controller card should be reset via the shelf manager not the reboot
command.
Verify success by running the cat command on the snmpd.conf file:
root@CAPCWPI1-F101-7:#cd /usr/app/repl_capc/cl_agent/Wimax/agent/data/
root@CAPCWPI1-F101-7:#cat snmpd.conf
# net-snmp (or ucd-snmp) persistent data file.
#
##############################################################
# STOP STOP STOP STOP STOP STOP STOP STOP STOP
#
# **** DO NOT EDIT THIS FILE ****
#
# STOP STOP STOP STOP STOP STOP STOP STOP STOP
#############################################################
#
# DO NOT STORE CONFIGURATION ENTRIES HERE.
# Please save normal configuration tokens for snmpd in SNMPCONFPATH/snmpd.conf.
# Only "createUser" tokens should be placed here by snmpd administrators.
# (Did I mention: do not edit this file?)
#
usmUser 1 3 0x800000a1030001af16f2b5 0x61646d696e00 0x61646d696e00
NULL .1.3.6.1.6.3.10.1.1.3
0x6088ea52a3e2b92ad276a8a41113a0506aa1712b .1.3.6.1.6.3.10.1.2.4
0xa3e2b92ad276a8a41113a0506aa1712b 0x00
usmUser 1 3 0x800000a1030001af16f2b5 0x677565737400 0x677565737400
NULL .1.3.6.1.6.3.10.1.1.3
0x8435926266b17c41704b455f328216dcd9dc2264 .1.3.6.1.6.3.10.1.2.4
0x66b17c41704b455f328216dcd9dc2264 0x00
usmUser 1 3 0x800000a1030001af16f2b5 0x6f70657261746f7200 0x6f70657261746f7200
NULL .1.3.6.1.6.3.10.1.1.3
0x69bb38686426d91e2254d0bb500b78ff837d1a7b .1.3.6.1.6.3.10.1.2.4
0x6426d91e2254d0bb500b78ff837d1a7b 0x00
setserialno 1241250569
engineBoots 2
oldEngineID 0x800000a1030001af16f2b5
MAX204SGV4.0
387
Note: If the snmpd.conf file has the correct engineID and three usmUsers were added or if this file is not
readable, bootstrapping was successfully completed. If not, the file will have a default EngineID that will
not match the system EngineID. In this case delete the CAPC from the EMSand re-run the bootstrapping
procedure.
CAPC Bootstrapping
MAX204SGV4.0
388

Troubleshooting
CAPC Bootstrapping
The CAPC (with the same MAC address of the node added) can now exchange the bootstrap (xml) file with
EMS (using the authenticated SFTP account) and establishes the SNMP V3 communication (with the
authenticated SNMP Engine ID) to complete the initial bootstrap. This process can take (5 or more) minutes
to complete Bootstrap xml file exchange
There is no status bar or similar types of indication of bootstrapping progression. One can observe the
bootstrap xml file exchange for the progression of the bootstrapping.
The bootstrap xml created by EMS for the CAPC bootstrapping looks like
800000A103212121210201.xml in which the file name is the same as the SNMP Engine ID
of the CAPC just added and the xml file is placed under:
C:\Program Files\Motorola\PortalEMS\sftproot\ems_to_ne
When the CAPC starts the bootstrapping, a similar bootstrap xml created by the CAPC is uploaded
to EMS and placed under:
C:\Program Files\Motorola\PortalEMS\sftproot\ne_to_ems
Both bootstrap xml files will be automatically deleted by EMS when the
The FRU related information will also be populated in the Node Properties after the
NOTE CAPC Configuration at EMS cannot be done until after the payload discovery process has been
successfully accomplished.

There are two ways of knowing when the bootstrapping procedure is complete on both
the CAPC and EMS.
1. The CAPC keys have been successfully uploaded to the EMS and processed by the EMS. Generally
checking that the EMS has cleaned up the bootstrapping configuration files is a good indication.
2. The CAPC LMT URL has been populated on the EMS in the CAPC general screen.
After bootstrapping is complete on both the EMS and the CAPC and has been verified by the operator, the CAPC
should be rebooted by use of the command reboot. It should be noted that if the operator reboots the CAPC
before the EMS has processed the bootstrapping configuration, that the CAPC sends up, the entire process will
have to be repeated.
MAX204SGV4.0
389
CAPC Bootstrapping
Note that the files have

disappeared after transfer
MAX204SGV4.0
390

Troubleshooting
CAPC Payload Card Discovery Procedure

With only the Primary System Controller active, payload discovery can take place. The procedure to
discover the payload cards of the CAPC is carried out at the EMS and can only be achieved when a CAPC has
completed its bootstrapping procedure.
Using the EMS Topology Manager, the operator should select the CAPC by right clicking on the CAPC icon
and when the pop up window appears, the operator should select Discover Payload Sets.
A Discover Payloads Summary popup window will display the Payload Sets and Payload Modules discovered for
the chosen CAPC. At this point, the operator should click OK to acknowledge.
The WiMAX Topology tree now shows the hierarchical order of the newly discovered Payload
Sets and Payload Modules. Children nodes can be collapsed or expanded under its parent
node for different views of the hierarchical depth.
Once the discovery procedure has been successfully completed, the operator may configure the
Payload Sets and the CAPC node itself. Only after the Payload Sets are configured will the operator
be able to configure the parent CAPC node and then push the configuration files out to the CAPC.
MAX204SGV4.0
391
CAPC Payload Discover Process
MAX204SGV4.0
392

Troubleshooting
Payload Set Node Properties

Payload properties configuration is at the Payload Set level. Each Payload Set may
contain 1 - 2 Payload Modules, one Active and one Standby.
Payload set is the logical representation of Payload Cards (Modules) and is the node level where the
APs are associated.
Payload Set Node Properties

Right click a Payload Set icon to select Node Properties to modify the
properties of the Payload Set. The tabs presented under Payload Set
Properties are as follows:
FRU Information
Paging Controller Configuration
The only editable parameters under these tabs are the Payload Set Node Name and Paging
Controller ID. All other fields are either automatically generated by EMS or populated from the
CAPC Inventory data and are read-only. The Node Name serves only as the mnemonic
identifier of the Payload Set on the Topology.
MAX204SGV4.0
393
CAPC Payload Set Properties
MAX204SGV4.0
394

Troubleshooting
Payload Set Node Configuration

To configure a Payload Set, one must open its parent CAPC node configuration for editing first.
Right click on CAPC node icon; select and click on Node Configuration then click on
the Pencil/Paper icon to transit to the Edit mode.
After the parent CAPC node configuration is in locked state, right click on the Payload Set node icon;
select and click on Node Configuration then click on the Pencil/Paper icon to transit to the Edit mode.
Note that there is a small lock icon at the CAPC node icon and at all the children Payload Set icons.
NOTE
The CAPC Node (parent) must be Locked for editing (NOT IN DOWNLOAD
MANAGER) before the Payload Set (child) can be Locked for editing.
At Payload Set level, in addition to the Node Properties option the operator is given options to
launch the Statistics Viewer, delete the Payload Set and add APs.
Right click Payload Set to select the additional operations.
.NOTE
Delete this Node is disabled. A parent node cannot be deleted until all children
nodes are deleted first. There are two Payload Modules under this Payload Set.
MAX204SGV4.0
395
CAPC Payload Set Configuration
MAX204SGV4.0
396

Troubleshooting
Payload Module Node Properties
Node Name
Right click a Payload Module icon to select Node Properties to modify the
properties of the Payload Module. Payload Module Properties are similar to
Payload Set Node Node Properties where only Node Name is editable and all
others are automatically generated by EMS or populated from CAPC Inventory
data The Node Name serves only as the mnemonic identifier of the Payload
Set on the Topology.
MAX204SGV4.0
397
CAPC Payload Module Properties
MAX204SGV4.0
398

Troubleshooting
CAPC Paging Group Properties
Right click a Payload Module icon to select Paging Group Properties to modify the properties of the
Paging Group.
Paging Group Name

Under General Node Properties, the Node Name is editable and all other
fields are automatically generated by EMS or populated from CAPC Inventory
data The Paging Group Name serves only as the mnemonic identifier of
the Paging Group on the Topology.
Paging Group Information
Paging Group ID
Paging Cycle
Paging Offset
Paging Retry Count
Paging Group ID The Paging Group ID is the Globally unique ID of the Paging
Group. Since the EMS only validates and enforces uniqueness within this EMS,
It is the responsibility of the operator to enforce global uniqueness.
Paging Cycle The Paging Cyle parameter is given as a count of the number of
frames between the beginning of MSS listening intervals. This determines the
frame into which the paging message is transmitted to a specific paging group.
This parameter does not apply to this CAPC but apply to all the AP members in
this paging group. The service impact indicates the impact to the AP's not this
CAPC. Change to this parameter, all the AP members in this paging group must
be pushed.
Paging Offset This parameter specifies the frame within the cycle in which the
listening interval begins and paging message is transmitted. Must be smaller
than wmanPagingCycle value.
Paging Retry Count The paging offset specifies how many pages to send to
an unresponsive MSS. This parameter does not apply to this CAPC but apply to
all the AP members in this paging group. The service impact indicates the impact
to the AP's not this CAPC. Change to this parameter, all the AP members in this
paging group must be pushed.
MAX204SGV4.0
399
CAPC Paging Group Properties
MAX204SGV4.0
400

Troubleshooting
Paging Group Configuration

Right click a Payload Module icon to select Paging Group Configuration to modify the configuration of
the Paging Group.
Paging Group Information
Broadcast Paging Retry Count

Under Paging Group Information, the Broadcast Paging Retry Count is the
only parameter listed and is editable. Broadcast Paging Retry Count serves
as a parameter to delimit the maximum number of broadcast pages sent
to all MSSs in a paging area.
Member List
Index
Index The Index is the only editable parameter and is a unique Identifier of
each record listing the APs which are members of the Paging Group. The
Sector Node ID field will be populated by the EMS system inventory.
MAX204SGV4.0
401
CAPC Paging Group Configuration
MAX204SGV4.0
402

Troubleshooting
Payload Set Node and Payload Module Configuration Download

Child node configuration is a subset of the configuration data of the parent node. It
cannot be downloaded individually. The child configuration can only be saved for
incorporating into the parent node configuration data and all children node
configurations must be completed before the parent node configuration can be
complete , i.e. (saved) or downloaded. Therefore, all children Payload Set
and Payload Module configurations must be complete and saved before editing,
saving and downloading a CAPC configuration.

After all Payload Set configurations are completed (saved), the CAPC node itself can then be
configured.
Right click on the CAPC node icon in WiMAX Topology; select and click on Node
Configuration to launch the CAPC Node Configuration interface.
There are a few configuration parameters required to include:
AAA Client NAS Identifier
AAA Servers
Security options
Etc.
Validation
To validate if all required parameters are in place as well as if any parameter data are invalid,
a Validation function (the light bulb icon) can be performed before or when the configuration
is saved. If any required field is missing or any field contains invalid data (out of range,
incorrect format, etc.), the Validation will fail. The failed field will be highlight in RED.
MAX204SGV4.0
403
CAPC Node Configuration at the EMS
MAX204SGV4.0
404

Troubleshooting
CAPC Configuration Download

A Configuration Download can be executed on demand (by clicking the down arrow icon) or
by schedule via Download Manager (by clicking on the green plus icon).
Since this is the very first time Configuration Download to this CAPC, the NECB contains
re-init type parameters which will cause the CAPC to restart.
The warning message is issued after the automatic Validation. This message
should also be seen in the previous validations.
Click Yes to proceed the on-demand Configuration Download.
If this Configuration Download is not desired, one can undo all the changes and revert
back to the previous configuration by aborting this Configuration Download with a No
and then click on the Delete Workspace (the trash can icon).
Delete Workspace will also remove the lock from this CAPC and all children Payload Sets.
When a Configuration Download succeeds for the first time, the color of the NE icon will turn
to green with an Up status (from the previous Unknown state).
As this is a NECB download, the CAPC has restarted and sent an Availability
event trap to EMS after the restart.
MAX204SGV4.0
405
CAPC Software & Configuration Upgrade
MAX204SGV4.0
406

Troubleshooting
CAPC Software Location

The software to be used by the CAPC is stored in an RPM format in the designated location on
the EMS, to enable the software upgrade procedure to be carried out.
CAPC Software Verification

Before attempting to carry out the CAPC software upgrade procedure, the operator should check that
the software is located on the EMS in the correct directory and the correct format.
EMS location
The software for the CAPC is stored on the EMS in the following directory: C:\Program
Files\Mot\PortalEMS\sftproot\softwarebundles
CAPC Software Format
The CAPC software is placed on the EMS in the RedhatTM Package Manager (RPMTM) format,
which is a LinuxTM based software management system. The RPM file contains all the binary files
for all the applications, in addition to RPM component files a System Controller RPM and an
ATCA-7221 blade RPM. It also contains some configuration data and installation scripts. The
RPM file for a CAPC software release has a specific naming format. The following example file
name and table show this format and the meaning of each field.
wimax_capc-WMX010CAPC101 REL1 .rpm
Field
Example
Description
Software Name
wimax_capc
The name of the software to be downloaded.
Software Version
WMX01 0CAPC1 01 REL1 Identifies the unique software version for that software
name.
System Name
WMX
Indicates the specific system based on technology,
WMX=WiMAX.
System Version
Product Name
010
CAPC
The version of the system the software applies to.

The name of the product the software was built for.
For a CAPC the name is CAPC.
Product Version
Build Type
101
REL
Build Version
The version of the product the software applies to.

The type of software a Software Release or a
Software Patch.
The specific version of the build. There can be
multiple builds for a specific software release. This
number increments with each additional build.
MAX204SGV4.0
407
MAX204SGV4.0
408

Troubleshooting
CAPC Software Upgrade Procedure

The CAPC software upgrade procedure is carried out in 3 stages, with each stage
(listed below) being initiated by the EMS operator.
TM
DownloadThe active CAPC System Controller will download a Redhat Package Manager
TM
(RPM ) file from the EMS. The RPM file is stored in a temporary location on the active
System controller. The RPM file has the new software and other files in it.
PrepareThe active System Controller unpacks the RPM file, verifies the digital signatures of the RPM
contents, and audits the current CAPC configuration to determine if the installation can proceed.
ActivateThe active System Controller performs a rolling upgrade procedure to install the
new software on all the blades in the CAPC. The rolling upgrade will allow the CAPC to
continuing functioning while the new software is being installed.
Prerequisites
The following prerequisites must be met before installing the new software:
The active System Controller must have a designated standby card that is in the standby state.
Each ATCA-7221 blade must have a designated standby card that is in the standby state.
There are no faulty blades in the chassis.
No blades are reporting errors.
The CAPC has the configuration data for each installed blade.
MAX204SGV4.0
409
MAX204SGV4.0
410

Troubleshooting
Download
The Download procedure is the first of the three procedures required to carry out an upgrade of
the new software. The download procedure falls into 4 main steps as listed below:
Initiate the download
Verify the software version
Download the software
Generate status
Initiate the download
The CAPC Download command is initiated by the operator using the EMS.
Using the topology manager, locate the CAPC node that the Software download to be performed on.
Right click on the CAPC node and select Download Software.
Select the software load from the pop-up window and click on Start Download. A configuration
window will now be launched.
The operator should verify the configuration, make any necessary changes and then save the
configurations
Select Add to Download Manager or Push Configuration to NE. If Add to Download Manager is
selected, the configuration will be downloaded as part of the Software Download.
The operator should then initiate the Software download by selecting the Green Icon on the
Download Manager
The Software download status (Download, Prepare, Active) will be displayed in the Download
Manager window
The RPM file (software name and software version) and the IP address of the Motorola software
server have to be specified by the operator. The command and information is sent to the
specified CAPC, who will then perform software version verification.
Software version verification
Once the operator has initiated the download the CAPC will first perform the software version
verification. If the given software version is different from the one that is currently running on the CAPC,
the download process will continue. If the given software version is the same as the one that is currently
running on the CAPC, the CAPC will not download the software and will notify the EMS to this fact.
The operator can if so desired; force a download of the same version of software but this is usually
only carried out as part of a fault recovery procedure.
Download the software
After the CAPC performs the software version verification and establishes communication with the
EMS, the new software is downloaded to the CAPC who will notify the EMS that the download
has been successful. The CAPC then waits for the EMS to give it the next instruction (typically
to prepare the software).
Status
The software download status can be monitored at the EMS. If the download fails, the EMS is notified
and the operator can take actions to correct the problem. If the download is successful, the EMS
is notified and the operator can initiate the Prepare procedure.
MAX204SGV4.0
411
Prepare
The Prepare procedure is the second of the three procedures required for an upgrade of
new software and consists of a number of steps as shown below:
Initiate the Prepare
Unpack the software package
Perform a health check
Perform a system verification
Generate status
Initiate the Prepare The CAPC Prepare command is initiated by the operator using
the EMS, which executes the Prepare procedure.
Unpack the software package The CAPC will unpack the RPM file into individual RPM
files for the System Controller and the ATCA-7221 blades.
Perform a health check The health check determines if there are any error conditions
being reported by any of the active or standby blades.
Perform a system verification The CAPC verifies that the following conditions are met. In
order to activate the software, these conditions must be met.
Each active System Controller and active ACTA-7221 blade has a mated
blade that is in the standby state.
There are no faulty blades in the chassis.
There are no blades reporting errors.
The CAPC has configuration data for each installed blade.
Generate status The Prepare status can be monitored at the EMS. If the Prepare fails, the EMS is
notified and the operator can take actions to correct the problem. If the Prepare is successful, the
EMS is notified and the operator can initiate the Activate procedure.
MAX204SGV4.0
412

Troubleshooting
Activate
The Activate procedure is the third of the three procedures required for an upgrade of new
software and consists of a number of steps as shown below:
Initiate the Activate
Perform a rolling upgrade
Generate status
Initiate the Activate The CAPC Activate command is initiated by the operator using the EMS
and causes the CAPC to execute the Activate procedure.
Perform a rolling upgrade The CAPC performs a rolling upgrade to avoid any system downtime
while the new software is being loaded. The rolling upgrade sequence is:
Upgrade and then reboot the standby System Controller
Initiate the failover of the currently active System Controller
Upgrade and reboot the now standby (previously the active) System Controller
Upgrade and reboot all standby ATCA-7221 blades simultaneously
Initiate the failover of all the active ATCA-7221 blades
Upgrade and reboot all the now standby ATCA-7221 blades
Generate status The Activate status can be monitored at the EMS. If the Activate fails, the EMS is
notified and the operator can take actions to correct the problem. When the new software has been
installed on all the blades, the CAPC reports a successful activation to the EMS.
MAX204SGV4.0
413
MAX204SGV4.0
414

Troubleshooting
MAX204SGV4.0
415
Configuration Only download

The CAPC configuration can be downloaded independently of the software upgrade. In
this case, the configuration will be verified and saved. The operator can choose to push
the configuration to be downloaded to the NE and then there is no reboot required at the
CAPC in order for the new configuration to take effect.
Two types of configuration download can be performed for a CAPC Node.
BCC (Bulk Configuration Change) Download - Only the changed configuration will be downloaded
NECB (Network Element Configuration Baseline) Download - The entire configuration file
will be downloaded to the NE
In addition there are two more configuration file types that may be used by the CAPC as shown below:
FTP (Factory Tunable Parameters) can only be changed via a software upgrade
Internal Data can only be viewed or changed via the LMT
MAX204SGV4.0
416

Troubleshooting
Lesson Summary
Verify the component parts of the CAPC to be used in the installation.
Verify proper installation of CAPC hardware
Verify proper installation of CAPC software and NCS middleware
State the pre-site commissioning procedures to be used to install the CAPC in a chosen
location.
State the Field Commissioning procedures of the CAPC.
Perform the proper CAPC power on procedure
Observe CAPC LEDs to determine equipment status
Bootstrap the CAPC
Discover CAPC payload sets
Discover CAPC payload modules
Download CAPC configuration
Download CAPC software
State the software upgrade procedures of the CAPC.
State the methods to be used when troubleshooting the commissioning of the CAPC.
MAX204SGV4.0
417

CAPC Installation and Troubleshooting
1. The two methods available for mounting the CAPC chassis in a rack are, front and rear
mount.
a. True
b. False
2. The 7221 blades may be placed in physical slots ____ in the CAPC chassis.
a.
b.
c.
d.
1 through 14
2 through 14
1 through 13
2 through 13
3. Physical slot 1 on the front of the CAPC chassis is associated with physical slot ____ on the
rear of the CAPC chassis.
a. 1
b. 14
c.
d. 13
4. The CAPC chassis ground should be connected to the -48 vdc return line.
a. True
b. False
5. The Ethernet cables used to connect the CAPC to the rest of the providers system are
installed on the _____.
a. F101 Blade
b. F101 RTM
c.
F7221 Blade
d. F7221 RTM
6. Place the following CAPC power on steps in order.
Procedure
Procedure Number
Physically check all power and grounding cables connected to the CAPC
for serviceability.
Ensure the 48V dc supply is set to on at the customer premise power
equipment.
Select to on all circuit breakers on Power Entry Module B.
Ensure all fans, Power Entry Modules and cards operate normally.
Select to on all circuit breakers on Power Entry Module A.
Ensure all cards and units are correctly fitted to the CAPC chassis.
MAX204SGV4.0
418

Troubleshooting

7. The purpose of the bootstrapping procedure is to allow the CAPC and the EMS to exchange
secure key information.
a. True
b. False
8. The procedure to discover the payload cards of the CAPC, is carried out at the EMS and
must be completed prior to the bootstrapping procedure.
a.
True
b.
False
9. Which is not one of the steps in the CAPC software upgrade procedure?
a. Download
b. Prepare
c. Verify
d. Activate
10. The types of configuration download that can be performed on a CAPC Node are ____.
a. BCC
b. BCU
c. NECB
d. FTP
e. a&c
f.
b&c
g. b&d
MAX204SGV4.0
CAPC LMT
419
Lesson 7
CAPC Local Maintenance Terminal
MAX204SGV4.0
CAPC LMT
420
MAX204SGV4.0
CAPC LMT
421
Objectives
1. Describe the functions of the CAPC Local Maintenance Terminal
1. Log on to the CAPC LMT
2. Interpret Active log file
3. Interpret Alarm log files
4. Interpret Platform logs
5. Interpret IPSec configuration
6. Modify IPSec configuration
7. Schedule Health Check
8. Download Health Check report
9. Verify IP connectivity
10. Trace messages between subcomponents
11. Interpret OS security/authority logs
12. Interpret Node and FUR states
13. Take and download Snap reports
14. Interpret and graph statistics
Student Activity
This lesson will include an instructor guided simulation of the CAPC LMT.
MAX204SGV4.0
422
CAPC LMT
Introduction
The Local management Terminal (LMT) of the CAPC is a Web based interface that may be used for
maintenance purposes. The actual software function resides on the CAPC system controller cards,
and requires the user to login to gain access. The LMT user accounts should already have been
set when commissioning the CAPC. The LMT is launched using a standard PC web browser and
displays as a series of tabs which contain a number of features listed below, to assist the operator
in management of the CAPC:
Activity Logging
Alarm Logs
Dynamic Logging
Configuration Tools
Configuration Utility
Event Reports
Health Check
IP Utility
Link Management
Message Tracing
Security
Platform Logs
Session Management
Snap tool
State Management
Statistics
User Management
MAX204SGV4.0
CAPC LMT
423
LMT User Accounts

Before the LMT is accessed, the LMT user account must be set up at the EMS. In the case of the CAPC,
this is carried out when the CAPC is defined on the EMS. Under the CAPC General Tab [Node Properties],
the Local Admin account User name should be added. Once bootstrapping of the CAPC has taken place,
the CAPC LMT URL field will be populated.
If the AAA server is to be used to authenticate the CAPC LMT user, this Local Admin account
must also be configured at that Node.
There are four types of users who have access to the CAC LMT as stated below.
Administrator
Configuration Manager
Troubleshooter
Tools
Each will have different levels of access as stated in the table
Activity Logging
Administrator Configuration
Manager
X
X
Alarm Logs
Dynamic Logging
Configuration Tools
Configuration Utilities
Troubleshooter
Tools
X
X
X
Event Reports
Health Check
IP Utility Tools
Link Management
Message Tracing
Security
X
X
X
X
Platform Logs
Session Management
SNAP Tool
State Management
Statistics
User Management
X
X
MAX204SGV4.0
424
CAPC LMT
LMT Login
There are two basic methods for accessing the CAPC LMT as stated below:
LMT launch via EMS
LMT launch via secure Web connection
LMT launch via EMS
When launching the CAPC LMT from the EMS, the following steps are to be followed:
1. Right click on the CAPC node in the EMS Topology Tree.
2. Left click on the [Launch CAPC Local Maintenance Terminal] menu selection.
3. When the CAPC LMT login screen appears, enter the Local Administration account user
name and password.
LMT launch via secure Web connection
Before the user attempts this procedure they should ensure that a web browser such as Internet explorer is
installed on the PC to be used. To log into the LMT, the user should carry out the following procedure:
1.
2.
3.
Open up the PC web browser.

On the navigation bar, type in the IP address of the CAPC system controller. This
should be in the following formathttps://x.x.x.x
When the CAPC LMT login screen appears, enter the Local Administration
account user name and password.
MAX204SGV4.0
CAPC LMT
425
CAPC Local Management Terminal
CAPC LMT Login
MAX204SGV4.0
426
CAPC LMT
CAPC LMT Welcome Screen

When the user has logged into the CAPC LMT (by either of the two methods stated previously) they will be
presented with a CAPC LMT Welcome Screen. The left hand pane of this screen shows the option available to
the user, while the main viewing pane shows a brief description of each option. The user may choose one of
these options by selecting with the mouse, an option in the left hand pane.
In addition the screen will also show the current software version of the CAPC.
CAPC LMT Welcome Screen
MAX204SGV4.0
CAPC LMT
427
Activity Logging
The Activity Logging section allows the user to view and download the LMT activity logs. There are
4 sub menus in this section which are as follows:
Backup Logs
Delete Logs
View Download Logs
View Log Size
Backup Logs
There are 3 items under this option which allow the operator to select the directory of the logs to be backed up.
The user may back up the current logs files, the backed up log files or both.
Delete Logs
This option allows the operator to specify from which directory the logs files are to be deleted, current
and backup and also which day over a 7 day period is be selected.
View Download Logs
This option allows the operator to specify from which directory the logs files are to be viewed or
downloaded, current and backup and also which day over a 7 day period is be selected.
View Log Size
This option allows the operator to view the log size of all logs held in the backup directory.
Activity Logging
MAX204SGV4.0
428
CAPC LMT
Alarm Logs
The Alarm Logs section allows the user to list and view the alarm logs as well as the file size. There
are 5 sub menus in this section which are as follows:
Backup Alarm Logs

Delete Alarm logs
Backup Download Logs
View Backup Logs
View Log Size
Backup Alarm Logs

This option allows the operator to backup the alarm logs on a per card basis for
system cards and payload cards.
Delete Alarm logs
This option allows the operator to delete the alarm logs on a per card basis for system
cards and payload cards.
Backup Download Logs
This option allows the operator to backup the downloaded alarm logs on a per card
basis for system cards and payload cards.
View Backup Logs
This option allows the operator to view the backed up alarm logs on a per card basis for
View Log Size
This option allows the operator to view the size of the alarm logs on a per card basis for
Alarm Logs
MAX204SGV4.0
CAPC LMT
429
MAX204SGV4.0
430
CAPC LMT
Configuration Tools
There are 11 sub menus in this section as shown below:
Ethernet Configuration
ICMP Echo Request
IP Sec Utility
View Running IP Sec Policy
View IKE Security Associations
View IP Security Associations
View Pending Policy Store
View Source XML with PDB
IP Parameter Configuration
View the Running NECB File
Software Upgrade Type
Ethernet Configuration
This option allows the operator to configure the Ethernet settings on a per card basis for
system cards and payload cards. This includes:
Ethernet link speed
Ethernet Duplex
Ethernet Auto Negotiate
Ethernet Auto Mdix
MTU size
In addition it will also display the FRU type and slot number.
ICMP Echo Request
This option allows the operator to enable or disable the ICMP echo Request settings on a per
card basis for system cards and payload cards.
IP Sec Utility
This option allows the operator to configure the location of the CAPC IP Sec configuration
file that will be used.
View Running IP Sec Policy
This option allows the operator to view the running IP Sec policy on a on a per card basis
for payload cards only.
View IKE Security Associations
This option allows the operator to view the IKE Security associations on a per card basis
MAX204SGV4.0
CAPC LMT
431
Configuration Tools
MAX204SGV4.0
432
CAPC LMT
Configuration Tools
View IP Security Associations
This option allows the operator to view the IP Security associations on a per card basis
View Pending Policy Store
This option allows the operator to view the pending policy store on a per card basis for payload cards only. View
Source XML with PDB
This option allows the operator to view the source XML with PDB on a per card basis
IP Parameter Configuration
This option allows the operator to view and configure the external IP addresses that will be used by the
CAPC to communicate with other network devices. In addition the operator will have a choice to set
these IP address manually or automatically visa DHCP.
View the Running NECB File
This option allows the operator to view the running NECB file Software
Upgrade Type
This option allows the operator to configure the type of software upgrade to be used on the
CAPC. The two types available are rolling or fast.
MAX204SGV4.0
CAPC LMT
433
Configuration Tools
MAX204SGV4.0
434
CAPC LMT
Dynamic Logging
The Dynamic Logging section allows the user to carry out a multitude of tasks. There are 5
sub menus in this section as shown below:
Set Log Level
View Log level
View Download Logs
Configure Log Size
High Water Mark for Log Space
Set Log Level
This option allows the operator to set the dynamic log level on a per card basis for system cards and payload
cards. The filter may be set to capture logs in all boards or individual boards, while selecting all or one of
fourteen sub component tasks per card. The operator may further still configure the level at which he
wants logs collected, by customizing the log level. The choice available is:
Log all
Log off
Log information messages
Log debug statements
Log errors
log warnings
View Log level
This option allows the operator to view the configuration set by the dynamic log level option on a
per card basis for system cards and payload cards.
View Download Logs
This option allows the operator to view or download the dynamic logs on a per card basis for system
cards and payload cards and by subcomponent (application id). When displayed the operator has the choice
to refresh the information manually or have it in real time.
Configure Log Size
This option allows the operator to configure the size of the logs in Mb High
Water Mark for Log Space
This option allows the operator to configure the high water marks for logs as a percentage value of disk space.
When this level is reached, the operator will be required to take some remedial action.
MAX204SGV4.0
CAPC LMT
435
Dynamic Logging
MAX204SGV4.0
436
CAPC LMT
Configuration Utilities
The Configuration Utility section allows the user to configure the system using the IPSec utility.
MAX204SGV4.0
CAPC LMT
437
Event Reports
The Events reports section allows the user to view the dynamic log event reports. There is only
one sub menu in this section as shown below:
View Event Reports
View Event Reports

This option allows the operator to view event reports on a per card basis for both
system and payload cards.
Event Reports
MAX204SGV4.0
438
CAPC LMT
Health Check
The Health Check tool allows you to schedule a health check. The reports may then be
downloaded. There are 2 sub menus in this section as shown below:
Schedule Health Check
View Downloaded HC Report
Schedule Health Check
This option allows the operator to schedule a health check on a per card basis for both system and
payload cards. Once the health check has been executed by the CAPC, the operator will be informed
and may then download the report via the next option
View Downloaded HC Report
This option allows the operator to download and view a previously schedule health check for all
cards including system card and payload cards. Once the card has been chosen the operator may
select one of three different formats. These are:
hc_detailed.txt
hc_summary.txt
hc.log
MAX204SGV4.0
CAPC LMT
439
Health Check
MAX204SGV4.0
440
CAPC LMT
IP Utility Tools
The IP utilities tools section allows the operator to perform a number of basic IP tool operations.
Arp
Ifconfig
Netstat
Ping
Traceroute
Arp
This option allows the operator to view the arp results for all cards including system card and payload
cards. In addition the operator may specifically search for one IP address
Ifconfig
This option allows the operator to view the IF for all cards including system card and payload cards. Netstat
This option allows the operator to view the netstat information for all cards including system
card and payload cards. The operator may also search by IP or port number and may display
the information in two formats as shown:
Display all connections and listening ports in numerical form (-an)
Display routing table and listening ports in numerical form (-rn)
Ping
This option allows the operator to carry out a ping from all cards including system card and payload
cards. The operator may use an IP address or a FQDN.
Traceroute
This option allows the operator to carry out a traceroute from all cards including system card and
payload cards. The operator may use an IP address or a FQDN.
MAX204SGV4.0
CAPC LMT
441
IP Utilities
MAX204SGV4.0
442
CAPC LMT
Link Management
The Link Management section allows the operator to check the Access Point distribution and view the status of the
Access Point links. There are 2 sub menus in this section as shown below:
AP Distribution
AP Link Status
AP Distribution
This option allows the operator to view the distribution of Access Points amongst the configured payload cards
of the CAPC. By selecting the radio button more details can be obtained as stated below:
Payload Index
AP Id
AP Address Type
AP Address
AP VLAN ID
AP Row Status
AP Link Status
This option allows the operator to view the status of the Access Points per configured payload cards.
MAX204SGV4.0
CAPC LMT
443
Link Management
MAX204SGV4.0
444
CAPC LMT
Message Tracing
The Message Tracing section allows the user to trace the message between any two
subcomponents. There are 4 sub menus in this section as shown below:
Schedule Trace
List Trace
Delete Trace
View Trace Report
Schedule Trace
This option allows the operator to schedule a trace between two component per card basis on
system cards and payload cards. In scheduling the trace, the operator may chose a
number of options as listed below:
Sub components
Start time
Duration of Trace
Message type
Message name
Includes/excludes
List Trace
This option allows the operator to list completed traces per card basis on system cards and payload cards. Delete
Trace
This option allows the operator to delete completed traces per card basis on system
View Trace Report
This option allows the operator to view or download completed traces per card basis on
MAX204SGV4.0
CAPC LMT
445
Message Tracing
MAX204SGV4.0
446
CAPC LMT
Security
The Security section allows you to view the OS security authorization logs, user login attempts.
View user Login Attempts
View OS Security Log
View user Login Attempts
This option allows the operator to list the number of successful and unsuccessful login attempts
per card basis on system cards and payload cards.
View OS Security Log
This option allows the operator to view the security logs per card basis on system
MAX204SGV4.0
CAPC LMT
447
Security
MAX204SGV4.0
448
CAPC LMT
Platform Logs
The Platform/OS logs allow you to manage the platform/OS logs. There are 3 sub menus
in this section as shown below:
View/Download Platform Logs
Configure Log Size
Delete Logs
View/Download Platform Logs
This option allows the operator to view or download platform logs per card basis on system cards and
payload cards. Once the card is selected the user is presented with a list of available logs. By selecting
the radio button these may then be viewed or downloaded.
Configure Log Size
This option allows the operator to configure the platform log size in Mb, per card basis on
Delete Logs
This option allows the operator to delete platform logs per card basis on system cards and payload cards.
MAX204SGV4.0
CAPC LMT
449
Platform Logs
MAX204SGV4.0
450
CAPC LMT
Session Management
The Session Management section allows the user to carry a myriad of functions that directly relate to the
use of the CAPC LMT. There are 2 sub menus in this section as shown below:
Set Inactivity Timer
View and Terminate Sessions
Set Inactivity Timer
This option allows the operator to set an inactivity timer in minutes at which point the
CAPC LMT session will automatically close.
View and Terminate Sessions
This option allows the operator to view all current CAPC LMT sessions and terminate
any of these by manual operation.
MAX204SGV4.0
CAPC LMT
451
Session Management
MAX204SGV4.0
452
CAPC LMT
Snap Tool
The Snap tool allows the operator to take snap reports of the CAPC. There are 2 sub
menus in this section as shown below:
Schedule Snap
Download Snap Report
Schedule Snap
This option allows the operator to schedule a snap shot of the state of the cards within the CAPC. This is
carried out on a per card basis for system cards and payload cards.
Download Snap Report
This option allows the operator to view and download a scheduled snapshot and is carried out on a
per card basis for system cards and payload cards.
MAX204SGV4.0
CAPC LMT
453
SNAP Tool
MAX204SGV4.0
454
CAPC LMT
State Management
The State Management section allows the operator to view the CAPC Node State and FRU State.
CAPC Node State
FRU State
CAPC Node State
This option displays the current operational and administrative state of the CAPC node and in addition it
will also enable the operator to set the current CAPC node state to testing or down. However, selection
of these node states will cause a loss of service of the CAPC and result in the CAPC LMT failing to
respond (a warning is presented to this fact).
FRU State
This option displays the current operational and administrative state of the CAPC FRUs. By selecting
the radio button associated with each FRU, the operator may display more information on the selected
FRU and in addition the operator may set the state of the FRU to testing or down. However, selection of
these FRU states will cause a loss of service of that FRU and result in the CAPC LMT failing to respond
(a warning is presented to this fact).
MAX204SGV4.0
CAPC LMT
455
State Management
MAX204SGV4.0
456
CAPC LMT
Statistics
The Statistics Section allows the operator to view various CAPC statistics. There are 8 sub
CPU Node Utilization Statistics

Disk Utilization Statistics
IO Utilization Statistics
Key Statistics
Memory Utilization Statistics
Network Utilization Statistics
Temperature Monitoring Statistics
Timer Utilization Statistics
CPU Node Utilization Statistics

This option allows the operator to view the CPU Node Utilization Statistics on a per card basis for system cards and
payload cards. The results may be displayed either as a table, bar graph or line graph.
Disk Utilization Statistics
This option allows the operator to view the Disk Utilization Statistics on a per card basis for system cards
and payload cards. The results may be displayed either as a table, bar graph or line graph.
IO Utilization Statistics
This option allows the operator to view the IO Utilization Statistics on a per card basis for system cards and
payload cards. The results may be displayed either as a table, bar graph or line graph.
Key Statistics
This option allows the operator to view Key Statistics within the CAPC. The options available are
1. CAPC Payload Measurement
2. CAPC Measurement
3. CAPC Internal LM Payload Measurement
If option 2 is selected, the operator will not be able to specify a particular system card or payload
card. The results may be displayed either as a table, bar graph or line graph. The operator may
also display information from an active or historical source. The results may be displayed either as
a table, bar graph or line graph.
Memory Utilization Statistics
This option allows the operator to view the Memory Utilization Statistics on a per card basis for system
cards and payload cards while also selecting the type as Node Stats or Component MW. The results
may be displayed either as a table, bar graph or line graph.
MAX204SGV4.0
CAPC LMT
457
Statistics
MAX204SGV4.0
458
CAPC LMT
Network Utilization Statistics

This option allows the operator to view the Network Utilization Statistics on a per card basis for system
cards and payload cards. The display options per cards are:
Ethernet Stats
ICMP Stats
IP Stats
TCP Stats
UDP Stats
The results may be displayed either as a table, bar graph or line graph.
Temperature Monitoring Statistics
This option displays in table format the temperature of each fitted system card and
payload card in the CAPC
Timer Utilization Statistics
This option displays, in table format, information regarding all timers running on a per card basis
for system cards and payload cards.
Statistics
MAX204SGV4.0
CAPC LMT
459
User Management
The User Management section allows the operator to manage CAPC LMT users. There are 3 sub
Add User
Delete User
View / Modify User
Add User
This option allows for users to be added to one of the four CAPC LMT groups.
Delete User
This option allows for users to be deleted from the CAPC LMT.
View / Modify User
This option allows for user detailed to be modified.
User Management
MAX204SGV4.0
460
CAPC LMT
Lesson Summary
Describe the functions of the CAPC Local Management Terminal
MAX204SGV4.0
CAPC LMT
461
Hands-On Activity
The purpose of this activity is allow the student to navigate around the CAPC
LMT and retrieve information as directed.
Student Brief
For the purposes of the activity you are about to undertake, the following points are to be noted.
1. The CAPC you will connect to is in a serviceable condition.
2. You are to use the PCs provided which have the correct version Internet explorer loaded on them.
3. All documentation and passwords will be provided by the instructor.
Task Details
1. From the web browser on the PC login to the CAPC.
2. View a downloaded log from the active system card
3. View a downloaded backup alarm log from one of the configured payload cards.
4. Ensure that the ICMP echo request is enabled on the system card.
5. What is the IP address of the Primary DNS server?
6. What is the IP address of the EMS?
7. View a downloaded platform log for a system card with application id of LMT proxy task.
8. What is the maximum size of the dynamic log files set to?
9. Schedule a health check for the system card.
10. View the result of the health check in summary format.
11. Perform a Ping and traceroute between the system card and the EMS.
12. What VLAN is the Access Point configured on?
13. What is the current operational and administrative state of the CAPC node?
14. Which of the System cards is active?
15. Display the TCP stats for the system card.
MAX204SGV4.0
462
CAPC LMT
MAX204SGV4.0
AP Hardware
463
Lesson 8
Access Point Hardware
MAX204SGV4.0
464
AP Hardware
MAX204SGV4.0
AP Hardware
465
Objectives
1. State the physical makeup and functions of the Access Point
MAX204SGV4.0
466
AP Hardware
Access Point Hardware

Compliant to 802.16 standards, WiMAX Access Points provide high-performance
broadband wireless access in a number of spectrums.
Diversity Access Point (DAP) Hardware

The DAP provides high-performance broadband wireless access in the 2.3, 2.5
and 3.5 GHz spectrum. By utilizing diversity antenna and Multiple-Input,
Multiple-Output (MIMO) antenna techniques, WiMAX system capacity and
coverage are enhanced. These antenna techniques also result in strong indoor
penetration.
The Diversity Access Point consists of two major subsystems: the Diversity RF Head and the
Base Control Unit (BCU) as shown in the diagram on the facing page. By integrating the RF
processing at the tower-top, the need for heavy RF coaxial cable is eliminated. Instead,
the Diversity RF Head utilizes simple fiber and a power cables to connect to the BCU.
The BCU can pole, floor, wall or rack mounted.
The BCU contains a number of hot-pluggable slots for up to two site controllers and up
to four modem boards to support a four sector site configuration. Additionally, the BCU
contains an Alarm Input/Output board, fans and heating, and the power distribution system
for the entire site.
The Diversity Access Point consists of a number of units, some of which are
Field Replaceable Units (FRUs):
RF Head (FRU)
BCU Cabinet
BCU Alarms Card (FRU)
BCU Site Controller Card (FRU)
BCU Modem Card (FRU)
BCU Circuit Breaker Card (FRU)
BCU Power Supply Unit (FRU)
GPS system (including Maximum Stability Oscillator (MSO) FRU)
Ancillary Units
MAX204SGV4.0
AP Hardware
467
Diversity Access Point
MAX204SGV4.0
468
AP Hardware
DAP Hardware Interconnection

The diagram on the facing page shows the interconnections between the sub
units of the DAP system.
Power
The AC or DC input is routed via the Power Distribution Module to the DC
power Supplies before being routed via the BCU Circuit Breaker Card to the
other BCU cards. Power cables (which should be color coded per sector) are
routed to from the Power Distribution Unit to each RF Head.
Data
Data to and from the backhaul network is routed via two Ethernet cables which terminate
on the BCU Input / Output unit. The data is then switched on the backplane and routed to the
correct Modem Card. Once processed by the Modem Card the data is routed over the
sector color coded fiber optic cables to the RF Head. The data once received by the
RF head is processed in terms of modulation etc. before being transmitted.
Management
Management of the DAP is carried out by the Site Controller card and the Alarm Card.
These cards connect to the backplane for communication with the other cards
located with the BCU and via the Site Input / Output card for communication to the
Network. The site Input / Output card also provides connections for Customer external
alarms. The GPS antenna cable also connects to the Input / Output module.
MAX204SGV4.0
AP Hardware
469
DAP Hardware Interconnections
MAX204SGV4.0
470
AP Hardware
RF Head
The Diversity RF Head contains a two antenna RF section that performs all RF
transmit and receive processing required to deliver baseband signaling to the BCU.
The Diversity RF Head is a self-contained unit consisting of the following elements:
Two transmitter lineups

Two receiver lineups
Two duplexer filters
Two antenna elements
Redundant fiber optic interfaces
DC power conversion
The Diversity RF Head has a built in surge suppressor to protect the incoming power
feed from the BCU Power Distribution Unit. The Diversity RF Head produces a power
output one watt power per each of the two antenna elements. For severe interference
environments, optional filters can be introduced to the Diversity RF Head to improve
interference mitigation.
The two transceivers (XCVR) line-ups contained within each Diversity RF Head are
implemented in a soft-fail fashion. In the event that one of the transceivers should fail,
the Diversity RF Head will continue to operate utilizing a single transceiver chain. Each
user will effectively operate at a lower modulation and coding rate to compensate for the
reduction in diversity gain. Redundancy also extends to the fiber link between the BCU and
the RF Head
The RF head is fitted to a pole by means of an RF Head Mounting bracket which allows the
angle of elevation to be set. The fiber optic cables which connect the RF head to the Modem
Cards within the BCU cabinet are color coded per sector as are the power cables. This is
shown below:
RFU 1 = RED
RFU 2 = BLUE
RFU 3 = YELLOW
RFU 4 = GREEN
MAX204SGV4.0
AP Hardware
471
RF Head and Color Code
MAX204SGV4.0
472
AP Hardware
BCU Cabinet
The Base Control Unit (BCU) performs baseband processing, site synchronization, power
distribution, and network interfacing. Additionally, the unit hosts site level software and provides
interfaces for site backhaul. The BCU Cabinet is a weatherized outdoor unit which may be pole,
floor, wall or rack mounted. The BCU components are accessed from the front and rear of the
cabinet. The BCU Backplane allows for interconnectivity of the Site Controller Cards, Modem
Card, and the Alarm Card. All cables to and from the DAP are routed via cable inlets in the
bottom of the BCU cabinet
MAX204SGV4.0
AP Hardware
473
BCU Cabinet
MAX204SGV4.0
474
AP Hardware
BCU Alarm Card

The Alarm Card provides for the functions listed below:
Customer alarm inputs.
4 customer defined relay control outputs.
Cabinet alarm inputs.
Power supply ID information.
Layer 1 switching for Ethernet backhaul.
Power and interface signals to a GPS receiver.
Power and interface signals to an optional Maximum Stability Oscillator (MSO)
reference.
The Alarm card presents information in a series of LEDs on its front panel. They can be
subdivided into four groupings:
Alarm Card BCU LEDs

Alarm Card GPS LEDs
Alarm Card RFU 1-4 LEDs
Alarm Card Status Indicator
Under normal operation the Alarm Card LEDs will display:

LED
SYS FAN
LOW TEMP
High Temp
SURGE
REF FAULT
RFU 1-4
STATUS
State
Unlit
Unlit
Unlit
Unlit
Unlit
Green
Green
MAX204SGV4.0
AP Hardware
475
Alarm Card BCU LEDs
BCU LEDs
SYS FAN
This LED monitors the operation of the fan units.
When it is RED, a BCU fan unit has failed.
LOW TEMP
This LED monitors the BCU internal temperature. When it is RED, the BCU temperature has
fallen below 0 degrees centigrade.
HIGH TEMP
This LED monitors the BCU internal temperature. When it is RED, the BCU temperature has
risen above 70 degrees centigrade.
SURGE
This LED monitors the surge suppressor. When it is RED, the suppressor has failed.
REF FAULT
This LED monitors the Maximum Stability Oscillator (MSO). When it is RED, the MSO has
failed.
MAX204SGV4.0
476
AP Hardware
Alarm Card GPS LEDs

As the table below shows, two LEDs (RED and GREEN) are used to indicate the GPS input
state.
GPS LEDs
Alarm Card RFU 1-4 LEDs

As the table below shows, two LEDs (RED and GREEN) are used to indicate the RF Unit
(RFU) states.
RFU LEDs
MAX204SGV4.0
AP Hardware
477
Alarm Card Status LED
The STATUS LEDs monitor the state of the Alarm card circuitry controlling customer
alarms and providing power to the GPS module. A RED LED indicates a fault,
GREEN indicates normal operation.
Status LED
MAX204SGV4.0
478
AP Hardware
BCU Site Controller Card

The BCU Site Controller Card is a digital processing card containing:
Microprocessor platform for the site level software
Frequency/timing reference circuit
Ethernet switch
Interfaces for backhaul and site alarms
The BCU cabinet contains slots for two Site Controller Cards. LEDS on the front of the
BCU Site Controller will indicate if it is the main or standby card along with status
indications. There are three connection ports for direct access.
The BCU Site Controller Cards are accessed from the front of the BCU Cabinet.
BCU Site Controller Card
Site Controller Card - Front Panel Connections

TTY
RJ45 allows connection of a PC to the card via an Ethernet connection.
9 Pin console port
MAX204SGV4.0
AP Hardware
479
Site Controller Card - LEDs
Three LEDs are used to display Site Controller operation.

Under normal operation the Active Site Controller card will display the following LEDs:
LED
Active
Status
State
GREEN
GREEN - Lit
RED - Unlit
Site Controller LEDs

Active LED
A GREEN Active LED indicates that the card is the active Site Controller. If two Site
Controller cards are installed, an unlit Active LED indicates the standby Site Controller.
Status LED
The Status LED indicates the software state of the System Controller card. Upon power up
the hardware sets the Status LEDs to GREEN off and RED on, which indicates the card is
un-initialized. This LED condition remains if the software boot was unsuccessful. During
initialization the GREEN and RED LEDs will be on, and after successful initialization the RED
will go off.
Site Controller LEDs
MAX204SGV4.0
480
AP Hardware
BCU Modem Card

The Modem Card is a digital baseband card, performing 802.16e MAC and PHY
processing. The Modem Card allows for software upgrades for PHY and MAC layer
modifications.
The BCU includes slots for up to four Modem Cards, with a typical configuration requiring
one Modem Card per sector. Using a trunked configuration, one Modem Card can be
configured to support two sectors.
There are a number of LEDs and connectors on the front of the Modem Card each is described
below. The Modem Cards are accessed from the front of the BCU Cabinet.
BCU Modem Card
Front Panel Connections
RJ45 allows connection of a PC to the card via an Ethernet connection.

9 Pin console port
MAX204SGV4.0
AP Hardware
481
Modem Card LEDs

The operation of the Modem card is displayed on 8 LEDs.
Under normal operation the Active Site Controller card will display the following LEDs:
LED
SYNC (A-C)
RX (A-C)
STATUS
State
GREEN
GREEN
GREEN - Lit
RED - Unlit
SYNC (A-C) LEDs

The Modem Card controls three fiber connection ports designated as A, B, and C. The
three SYNC LEDs provide information on the state of frame synchronization on the fiber
optic link to the RF heads. SYCN LEDs will be GREEN when frame synchronization is
detected with the RF head. A loss of frame synchronization will cause the SYNC LED to
turn RED.
RX (A-C) LEDs
The three RX LEDs provide information on the state of RX power. If power is detected
from the RF head, the RX LED will be GREEN. Loss of power, or low power, will cause
the RX LED to turn RED.
STATUS LEDs
The Status LED indicates the software state of the Modem card. Upon power up the
hardware sets the Status LEDs to GREEN off and RED on, which indicates the card is
un-initialized. This LED condition remains if the software boot was unsuccessful. During
initialization the GREEN and RED LEDs will be on, and after successful initialization the RED
will go off.
Modem Card LEDs
MAX204SGV4.0
482
AP Hardware
BCU Circuit Breaker Card

The Circuit Breaker card, containing 7 circuit breakers, is housed in the BCU Cabinet. The
circuit breakers control the following sub units:
BCU 1 (10A)
BCU 2 (10A)
Heater/DACS (15A)
RFU1 (10A) RF Head
RFU2 (10A) RF Head
RUF3 (10A) RF Head
RFU4 (10A) RF Head
This card is accessed from the front of the BCU Cabinet.
Circuit Breaker
BCU1
BCU2
Heater/DACS
RUF1
RUF2
RUF3
RUF4
Description
Controls power to SC1 and Modem 1&2
Controls power to SC2 and Modem 3&4
Controls power to Heater (if used) and Direct Air Cooling
System (DACS)
Controls power to RF Head 1
BCU Circuit Breaker Card

MAX204SGV4.0
AP Hardware
483
BCU Power Supply Unit

The BCU contains slots for three DC Power Supply units. Two DC Power Supplies are
required to support a fully populated site, with an optional third unit to allow for N+1
redundancy.
There
are three different models of Power Supply Units (PSU) available.

100/240 VAC (88 to 300 VRMS at 45-66 Hz)
+27 VDC (+21 to + 30 VDC)
-48 VDC (-60 to -40 VDC)
The Power Supply units provide +27 VDC for the BCU backplane and +54VDC for the
RF Heads (routed via the Circuit Breaker card). The Power Supply Units are housed at
the top of the BCU cabinet and are accessed from the front for insertion and removal.
Each Power Supply has a front panel On/Off Switch and a GREEN Active LED and
RED Alarm LED.
BCU Power Supply
MAX204SGV4.0
484
AP Hardware
Global Positioning System (GPS)

The GPS system, whose purpose is to provide an accurate timing reference for the TCXO
on the DAP Site Controller Card, is available in two variants together with an optional unit.
RF (Local) GPS
In this option, the GPS RF signal is passed from the head unit to the GPS RF unit located
within the BCU for processing. From here it is passed to the Site Controller card.
Remote GPS
In this option, the GPS RF signal is processed at the head unit with the resultant signal then
being passed to the GPS RF unit, before being routed to Site Controller card.
Maximum Stability Oscillator (MSO)
This is an optional module residing within the BCU cabinet. The MSO plugs directly into the
BCU Backplane and provides a highly stable 1 pulse per second signal which the Alarm
Card distributes to the Site Controller Cards for use as a frequency reference in the event
of GPS failure. The MSO can provide up to 24 hours of holdover.
GPS
MAX204SGV4.0
AP Hardware
485
Ancillary units
Input / Output Unit
This unit, which is accessed from the rear of the BCU Cabinet, houses all
input/output cables, 2 redundant Gb Ethernet ports (auto sensing connections), and
the GPS RF unit. In addition there are 6 connection outputs for customer use
and also a connection to the Alarm Board. The GPS unit has a connection for
RF input and a Power LED.
Fan
The BCU is cooled by forced air via the air plenum. The BCU utilizes a fan enclosed within
a fan tray which has a tachometer output that will provide alarm triggering approximately one
week prior to fan failure. The unit is physically housed in the top of the BCU Cabinet and can
be accessed from the front.
Heater & Direct Air Cooling (DAC) Filter
A heater module is included within the BCU cabinet for operations in cold
environments, and consists of a two-stage heater controlled by a thermistor and
control circuitry. During cold startup, both elements operate to quickly raise the internal
temperatures to 0C. During cold day operation only one heater element is used.
The heat from that element, plus heat dissipation within the BCU can maintain the
internal temperatures above 0C.
The DAC filter is an element that restricts movement of moisture and particulate
matter. The DAC filter will require periodic replacement due to particulate
clogging or filter aging. The life of the filter element is dependent upon local site
conditions. The Heater and DAC filter are housed in the bottom of the BCU Cabinet
and can be accessed from the front.
Surge Protection
The BCU has two surge elements. One surge card protects the main power input while a
second surge card protects the backhaul, GPS, customer Input / Output, and power feeds
to the RF heads. This unit may be accessed through the rear of the BCU Cabinet.
Ancillary Units
MAX204SGV4.0
486
AP Hardware
Power Distribution Module

The DAP may be powered off a -48 VDC, +27 VDC, or 100-240 VAC input directly connected
to the BCU Power Distribution Module. The Power Distribution unit has two ganged circuit
breakers for AC power input and one breaker if using a DC power input supply.
The module, which is accessed from the rear of the BCU Cabinet, has terminal strips for
connecting the DC power cables to the RF Heads. It is of great importance that these DC
power cables be connected using the correct sector color codes. These color codes match
those used on the fiber optics cables.
MAX204SGV4.0
AP Hardware
487
Lesson Summary
State the physical makeup and functions of the Access Point
MAX204SGV4.0
488
AP Hardware
1. Which is not part of the Access Points BCU?

a. Duplex Filter
b. Alarm Card
c. Heater
d. Medium Stability Oscillator
2. Which is not part of the Access Points RF Head?
a. Antenna Element
b. Duplex Filter
c. Medium Stability Oscillator
d. Transmit Lineups
3. When installing the RF heads, color coded cable ties are used to identify the four sectors.
Match the color to the proper sector.
1. Red = Sector ____
2. Yellow = Sector ____
3. Green = Sector ____
4. Blue = Sector ____
4. The DAP operates in the ____GHz, _____GHz, and ____GHz spectrum.
a. 2.3, 2.5, 3.0
b. 2.3, 2.5, 5.8
c. 2.3, 2.5, 3.5
d. 2.3, 3.5, 11
5. A BCU Alarm card flashing GPS LED indicates:

a. GPS Alarmed, site unsynchronized
b. GPS locked, Site locked to GPS
c. GPS unlocked, Site in free-run
d. none of the above
6. A BCU Alarm card with a RU4 Green LED on and Red LED off indicates:
a. Sector 4 Un-powered
b. Sector 4 RF Head Alarmed
c. Sector 4 RF Head Operational
d. Sector 4 RF Head Initializing
7. A Modem card with a flashing Green Status LED indicates:
a. Alarmed or Un-initialized
b. Initialized and no alarms
c. Standby waiting for sector assignment
d. Power-on LED test
8. The Modem card Sync LEDs indicate the state of:
a. Optical power level
b. Frame sync of TX/RX fibers
c. GPS signal
d. NPT server connection
MAX204SGV4.0
AP Commissioning
489
Lesson 9
AP Commissioning, Bootstrapping and

Software Upgrade
MAX204SGV4.0
490
AP Commissioning
MAX204SGV4.0
AP Commissioning
491
Objectives
1. Perform the procedure to carry out Access Point Commissioning and Bootstrapping
2. Perform the software upgrade procedures of the Access Point
1. Obtain required site commissioning data
2. Verify AP software version
3. Enter AP site commissioning data
4. Create LMT users account
5. Log on to AP LMT
6. Ping EMS from AP
7. Bootstrap the AP
8. Add AP sectors
9. Configure AP sectors
10. Download AP configuration
11. Download AP software on site
12. Download AP software from the EMS
13. Use AP Diagnostics tool to determine AP status
MAX204SGV4.0
492
AP Commissioning
Introduction
The initialization of the Access Point contains five distinct steps:
Site Calibration
Site Diagnostics
Commissioning
Bootstrapping
Download
Before attempting these steps, ensure that the Access Point is installed correctly
and powered up. The Access Point must be provisioned in the EMS for the
bootstrapping and download phases to be completed.
Site Calibration
The site calibration tool is used to calibrate the different RF link elements that exist
on the Access Point.
Site Diagnostics
The site diagnostics tool is used to determine the status of Access Point Field
Replaceable (Units FRU).
Commissioning
The purpose of commissioning procedure is to set up the Access Point in order that it may
communicate with the EMS. The Access Point does not need to be connected to the
backhaul network during the commissioning procedure.
Bootstrapping
Once commissioning is complete, and the Access Point is connected to the backhaul network,
communication with the EMS can be established. During bootstrapping the EMS and
Access Point exchange security key information. Only when this is successful may the
EMS push a software download to the Access Point
Downloading
Once commissioning and bootstrapping are complete, the operator may push down a software
load from the EMS, and, if required, the configuration file to the Access Point.
MAX204SGV4.0
AP Commissioning
493
Prerequisite Conditions
The following list states the prerequisites for both the Commissioning and Bootstrapping
procedures:
Hardware installation procedure is complete.
All necessary cabling has been completed for the backhaul.
The RF head(s) have been installed, are powered, and have been connected to the
Access Point.
Required Equipment
The following list states the required equipment both the Commissioning and Bootstrapping
procedures:
Laptop with a DB9 serial port installed running Microsoft Windows XP operating system.
Serial Cable DB9 Male to DB9 female cable
Category 5 or greater Ethernet cable.
Required Software
The following list states the required software both the Commissioning and Bootstrapping
procedures:
Tera Term Pro version 2.3 or greater
(http://hp.vector.co.jp/authors/VA002416/teraterm.html) or equivalent terminal emulator.
freeFTPd version 1.0.1.1 or later (http://www.freeftpd.com/?ctt=download) or equivalent
ftp server.
WinZip version 7.0 or later.
Official Access Point Software Distribution (dapsc_factory.tgz and dapsc_full.tgz).
MAX204SGV4.0
494
AP Commissioning
Access Point Initialization

The facing diagram shows the initialization process of the Access Point. Once the Access Point has
been powered up, the system will first negotiate which of the two System Controller cards is to
be active and which is to be standby. The next phase checks to see if the Access Point has valid
Commissioning data available. If it does not have valid data available it will have to be provided.
Once the Access Point has been successfully commissioned, various applications will begin to
initialize, which will bring up the physical link back to the network, and in particular the link to EMS. Once
the link to the EMS is established, the operator will then be able to perform the bootstrap procedure.
Providing the bootstrap procedure has been completed successfully the Access Point will check to
see if the software load is valid. If the software load is not valid, it may be pushed by the EMS. Once
completed, the Access Point will reset. If however the software load was valid, the Access Point
will continue to boot up and then report its state to the EMS.
MAX204SGV4.0
AP Commissioning
495
MAX204SGV4.0
496
AP Commissioning
Access Point Commissioning

Before the actual commissioning can begin, the equipment needed has to be configured. In
addition, the information to be entered during the commissioning process has to be acquired.
PC Terminal Software Configuration
The Terminal software being used should be configured as follows for use on comm port 1:
9600 baud
8 bit data
no parity
1 stop bit
no flow control
Laptop and Network Configuration

The laptop network connection that will interface with the BCU Site Controller is to
have the IP address configured statically to 144.190.240.2. (This should match the
subnet of the eth0 port on the System Controller Card) and the subnet mask
configured to 255.255.240.0. In addition the PC should not use a proxy server.
Access Point Commissioning Procedure

The Access Point Commissioning procedure falls into five steps
Software Version Verification

Site Calibration
Site Diagnostics
Site Commissioning
Installation and Network Connectivity Verification
Software Version Verification

The following list details the procedure to carry out software verification:
Connect a serial cable from the laptop to the Site Controllers front panel serial port.
Connect Crossover Ethernet cable between the Site Controller front Ethernet port and
the laptop Ethernet adapter.
Start up the terminal on the Laptop with settings as already defined for the comm port.
Power up the Site Controller- reset of the BSU site controller may be required if the
bootloader prompt does not appear.
Check that the software version is the latest version available.
If required, install the correct version of the Site Controller software (procedure follows).
MAX204SGV4.0
AP Commissioning
497
Installing Site Controller Software

This procedure involves booting the Site Controller off of the network using FTP and then transferring
the file system to the TFFS partitions.
Installation
Two steps are required:
Configuring The Host Machine

Flashing the File System onto the Site Controller
Configuring the host machine

1.
Set up an FTP server on the host machine if there isnt one on there already. The host
machine must be networked with the Site Controller use the front panel Ethernet port on the Site
Controller.
2.
All firewalls need to be disabled on the FTP host machine. Usually this is BlackICE firewall.
3.
You should have 2 files (2.16.03 files) in your FTP root home directory: zImage_codeload.elf
and dapsc.tgz.
4.
Connect a serial cable from your laptop to the Site Controllers front panel serial port
5.
Connect Crossover Ethernet cable between the Site Controller front Ethernet port (debug port)
and the laptop Ethernet adapter.
6.
Start Tera Term Pro (or some other terminal emulator) on the laptop.
Select serial connection and the appropriate Com port on the window that will open in Tera
Term.
Select the Setup drop down menu and select Serial port. Use serial settings 9600 baud, 8
bit data, no parity, 1 stop bit, no flow control.
7.
Configure the Ethernet interface on the laptop that will be networked with the Site Controller. It
must have a static IP 144.190.240.2 with a subnet mask of 255.255.240.0.
Flashing the File System onto the Site Controller

1.
Power down the Site Controller and remove any jumpers
2.
Connect a serial cable from your laptop to the Site Controllers front panel serial port
3.
Connect Crossover Ethernet cable between the Site Controller front Ethernet port (debug port)
and the laptop Ethernet adapter.
4.
Start Tera Term Pro on the laptop.

Select serial connection and the appropriate Com port on the window that will open in Tera
Term (This will most likely be Com 1).
Select the Setup drop down menu and select Serial port. Use serial settings 9600 baud, 8
bit data, no parity, 1 stop bit, no flow control
MAX204SGV4.0
498
AP Commissioning
5.
Power up the Site Controller. You should see the bootloader appear in your terminal
application. If it doesnt appear try to reset the Site Controller. Press (ENTER) and hold any key to
stop the autoboot and release when the [SC Boot]: prompt appears.
CPU: MPC8548E - Security Engine Rev 2
Version: VxWorks 6.2
BL version: BL02.02.02
BSP version: BS02.02.02
Creation date: Aug 11 2006, 10:25:37
******************
MOTOROLA WIMAX
******************
Pilot or later Site Controller
Attaching to TFFS...
6.
Use the c command to change the boot parameters. Configure them as follows you can
also type h to get a help menu. The ones underlined and in bold should be updated for this
procedure. All other parameters should be left as is by pressing the Enter key. Note error erasing
address. messages are normal and can be ignored during this procedure if using pilot hardware.
[SC Boot]: c
'.' = clear field; '-' = go to previous field; ^D = quit
boot device : tffs0 mottsec1
processor number : 0
host name : host
file name : /usr/app/scimg/zImage_911.elf zImage_codeload.elf
inet on ethernet (e) : 144.190.240.1:fffff000
inet on backplane (b):
host inet (h) : 144.190.16.1 144.190.240.2
gateway inet (g) :
user (u) : apftp
ftp password (pw) (blank = use rsh): apftp
flags (f) : 0x0
target name (tn) :
startup script (s) :
other (o) :
error writing address 0xffff8000
.
.
.
Site Controller Linux cmd string params
'.' = clear field; '-' = go to previous field; ^D = quit
AutoIP base ipAddr : 144.190.15.0:fffff000
root : docroot=tffsb1
nfs root : 144.190.0.1
gateIpAddr : FF.FF.FF.FF
console dev : ttyS0
Console baud : 9600
misc. : FF.FF.FF.FF
error writing address 0xffff8000
.
.
MAX204SGV4.0
AP Commissioning
499
.
7.
At the prompt -Boot using the @ command. The Linux Codeload kernel should boot and you
should see the Site Controller Codeload banner. Follow the prompts to enter things such as your FTP
server IP, username/password. Once youve entered these parameters, the script will run on its own
until codeload is complete. Here is sample output the items in red and underlined are the
parameters that should be entered. Note: If an error is made while entering the FTP server IP, the
username, or the password, <ctrl>u may clear the field. If not, please start over from the beginning of
this procedure.
********************************************************
********************************************************
** SITE CONTROLLER CODELOAD KERNEL **
********************************************************
********************************************************
Version: LSP02.01.02
Enter one of the following codeload options. You should use [u] ONLY if you've
codeloaded this Site Controller with the [n] option previously using the version of the
APSW Site Controller Codeload Kernel specified above.
[n] new (use this option if unsure)
[u] upgrade (faster)
n
********************************************************
** THE FOLLOWING FILE MUST BE ON THE FTP SERVER: **
** dapsc.tgz **
** **
** NOTE: The Wind River FTP Server will not work with **
** this script. **
********************************************************
FTP Server IP --> 144.190.240.2
FTP Username --> apftp
FTP Password --> apftp
***************************************************
** Retrieving filesystem package from FTP server...
***************************************************
.
.
.
******************************************************************************
******************************************************************************
** SITE CONTROLLER FILESYSTEM CODELOAD COMPLETED **
** Log File: /codeload.log
**
******************************************************************************
******************************************************************************
8.
After the software has updated, reboot the Site Controller using the reboot command.
After the AP has been bootstrapped, software updates may also be pushed from the EMS. That will
be discussed later in this lesson.
MAX204SGV4.0
500
AP Commissioning
Pre-Commissioning Tools
Prior to site commissioning the Access Point Calibration and Site Diagnostic tools should be run.
Access Point Site Calibration (apcalib)

AP calibration is a tool used to calibrate the appropriate gain and loss values of different RF link
elements that exist on the AP. Site calibration is performed by the site installer as the first step during
site installation. AP calibration tool runs on the active site controller (SC) and does not require
SC-Modem connections. All calibration data entered will be stored locally on the site controller, until
ready to be used by modem applications during normal AP initialization.
Prior to running Site Calibration collect the following data:
AP platform type (DAP, GAP, SAAP)

Antenna Gain (0-25 dBi)
Feeder cable length (1-100 m)
Feeder loss (0-16 dB)
TTLNA type (no TTLNA, AISG, Current-Sensing)
TTLNA Unique ID (up to 19 characters)
TTLNA low frequency (2.495-2.690 GHz)
TTLNA high frequency (2.495-2.690 GHz)
TTLNA normal RX gain (10-14 Db)
TTLNA bypass RX gain (0-1 dB)
TTLNA TX loss (0-1 dB)
Note TTLNA stands for Tower Top Low Noise

Amplifier (used on GAP installations only).
MAX204SGV4.0
AP Commissioning
AP Calibration
501
1. To start AP Site Calibration, open a terminal connection to the active Site Controller and type:
root@unknown:/root>run/usr/app/bin/apcalib
The following screen appears:
2. Clicking ENTER brings up the following screen.
MAX204SGV4.0
502
AP Commissioning
3. Once the selection for Platform type has been made, it could be changed by hitting RESET at
the bottom of the screen.
4. Select Next to enter General Calibration Data (required for all RFH types).
5. If displayed values are ok and match the values you recorded and do not require changes, hit
Enter key until the field that requires change is selected for editing (blinking cursor).
If an invalid value is entered for a field, a message pops up to display the permissible range for that
field.
MAX204SGV4.0
AP Commissioning
AP Calibration
503
While filling in data for any field the SPACE BAR can be hit to find out the currently stored value and
the default value for that field.
6. RESET at the bottom of the screen could be hit to discard the changes and to revert back to
values currently stored in the memory.
7. Hit Next at the bottom of screen after the data for general calibration parameters has been
entered. If the platform was selected to be of a type other than GAP, then jump to Step 10.
8. By clicking Next, GAP specific TTLNA Type Selection Menu is displayed. This is displayed
only if the installer selected GAP as the platform type. Select the type of TTLNA installed per
sector. If there is no TTLNA present then select "Not Present".
TTLNA selection, once made for any sector, can not be changed without hitting the RESET option at
the bottom of the screen.
MAX204SGV4.0
504
AP Commissioning
AP Calibration
9. Once the TTLNA Type is selected (AISG or Current-Sensing), enter the calibration values for
the selected TTLNA Type per sector (only required if TTLNA is present).
10. Once all the data required for the different RF elements are entered or defaults are accepted,
hit Save to store the data.
11. After data has been saved, hit Exit to exit the tool.
MAX204SGV4.0
AP Commissioning
AP Calibration
505
If at a later date you wish to see the currently stored calibrated values, run:
root@unknown:/root>/usr/app/bin/apcalib print
MAX204SGV4.0
506
AP Commissioning
Access Point Diagnostics (apdiag)

After Access Point Calibration is completed the AP Diagnostics procedure should be performed. AP
Diagnostics provides information on the state of the BCU. Information presented includes:
FRU State
Alarm State
GPSR Self Test Results
Satellite Status
TCXO Status
Modem Information
RF Head Connection Status
The BCU will be taken out of service to run AP
Diagnostics. When AP Diagnostics is completed,
the controllers must be rebooted to bring the site
back to active.
Perform the following to run AP Diagnostics application:
1. Connect to the serial port of the ACTIVE controller
2. Verify all boards (redundant SC, Alarm card, Modem(s), Power Supplies) are installed in the
BCU cage.
3. Log in as root
4. Start the AP Diagnostics application apdiag in the /usr/app/bin directory.
root@unknown:/root> /usr/app/bin/apdiag
5.
The BCU must be in Test mode to run AP Diagnostics. If it is not, apdiag will prompt the user
to place the BCU in Test mode. To insure a site is not inadvertently taken out of service,
apdiag will ask the user to enter 1 twice before starting Test mode.
Motorola WiMAX AP Diagnostic Tool
Copyright (C) 2006-2007 Motorola, Inc.
Warning: BCU is not in Test Mode!
Enter 1 to place BCU in Test mode,
Or any other key to exit: 1
This will take the BCU out of service!
If you are sure you want to continue, enter 1
or any other key to exit 1
Please wait
6. Once the BCU is in test mode, the Main Menu will appear. At this point, please allow the
modems to finish booting (may take up to three minutes if the site was not previously
commissioned). To enter the BCU diagnostics submenu, choose option 1.
Motorola WiMAX AP Diagnostic Tool
Copyright (C) 2006-2007 Motorola, Inc.
****** Main Menu ******
Choose from the following options:
1) BCU Diagnostics
2) Site Controller Diagnostics
3) Modem Diagnostics
?) Help
E) Exit
>1
MAX204SGV4.0
AP Commissioning
AP Diagnostics
507
****** BCU Diagnostics Sub-menu ******

Choose from the following tests:
1) BCU Information
2) Site Initialization Procedure
?) Help
E) Exit to Main Menu
7. Type 2 to begin the Site Installation Procedure.

>2
Running test, please wait
During this procedure, verify the following:

A. Verify all installed boards are listed as PRESENT:
FRU Status:
---------Alarm Card:
Controller 1 (slot 2):
Controller 2 (slot 3):
Modem 1 (slot 4):
Modem 2 (slot 5):
Modem 3 (slot 6):
Modem 4 (slot 7):
Power Supply 1:
Power Supply 2:
Power Supply 3:
MSO:
PRESENT
PRESENT
NOT Present
PRESENT
NOT Present
NOT Present
NOT Present
PRESENT
PRESENT
PRESENT
PRESENT
B. Verify none of the BCU alarms are ALARMED. If an alarm is triggered, resolve the condition
(usually by replacing the applicable FRU). A Door Alarm can be expected if a BCU door is open.
BCU Alarms Status:

----------------Power Supply 1 Voltage Alarm:
Power Supply 1 Temperature Alarm:
Power Supply 1 Input Alarm:
Power Supply 1 Output Alarm:
Power Supply 2 Voltage Alarm:
Power Supply 3 Voltage Alarm:
Customer Power Alarm:
GPS Power Alarm:
MSO Fault Alarm:
Relay 1 Alarm:
Relay 2 Alarm:
Cabinet Under-Temperature Alarm:
Cabinet Over-Temperature Alarm:
surge Alarm:
Door 1 Alarm:
Door 2 Alarm:
Not Alarmed
Not Alarmed
Not Alarmed
Not Alarmed
Not Alarmed
Not Alarmed
Not Alarmed
Not Alarmed
Not Alarmed
Not Alarmed
Not Alarmed
Not Alarmed
Not Alarmed
Not Alarmed
Not Alarmed
Not Alarmed
Not Alarmed
Not Alarmed
Not Alarmed
Not Alarmed
Not Alarmed
Not Alarmed
MAX204SGV4.0
508
AP Commissioning
AP Diagnostics
C. Verify all GPSR self tests have Passed. If any of these test fail, replace the GPSR and re-run the
test.
GPSR Self Test Results:
---------------------Channel 1 Correlation:
Channel 2 Correlation:
Passed
Passed
Passed
Passed
Passed
Passed
Passed
Passed
Passed
Passed
Passed
Passed
Manuf. Data Checksum Status:

Oscillator Checksum Status:
Temp Sensor Checksum Status:
ROM Status:
RAM Status:
Temperature Sensor Status:
RTC Status:
Passed
Passed
Passed
Passed
Passed
Passed
Passed
Antenna Status:
Passed
D. Verify satellite status.

Satellite Status:
-------------------Maximum visible satellites: 12
Channel
Sat. ID Mode
------------------ ------1
21
0
2
26
5
3
18
8
4
29
8
5
7
8
6
6
5
7
9
8
8
22
8
9
3
0
10
0
0
11
0
0
12
0
0
Signal
--------0
52
54
48
45
45
49
51
0
0
0
0
IODE
------100
11
8
211
2
48
197
195
0
0
0
0
E. Verify the TCXO in each Site Controller is Good. If the TCXO has failed, the associated
Site Controller will need to be replaced.
TCXO Status:
-----------------Controller
------------SC1
SC2
Slot
-----2
3
TCXO Status
-----------------Good
Good
MAX204SGV4.0
AP Commissioning
AP Diagnostics
509
F. For each modem, verify the FRU Part Number and Serial Number match the numbers that are
located on the 2 tabs that lock the modems into the BCU. Then verify the correct RF
Heads are listed as Connected: Perform this step for each modem.
Information for Modem 1:

----------------------EID Information:
--------------Board Type:
FRU Part Number:
FRU Serial Number:
Description:
HAL Compatibility:
MAC Address:
MAC Mask:
Kit Number:
Kit Serial Number:
User Defined Field:
0x0013, 0x0003
STLN6398GA
170G6T04W0
WiMax Modem
{0x01, 0x01, 0x00}
00:E0:0C:F9:EB:58
0x0003 (4 addresses)
STLN6398GA
170G6T04W0
Running test, please wait...
RF Head Connection Status:

------------------------RF Head 1 (Fiber Port A): Connected, Sector ID = 255, RF Head Type = Small (DAP)
RF Head 2 (Fiber Port B): NOT connected
RF Head 3 (Fiber Port C): NOT connected
G. Finally, for each connected RF Head, verify the communication connection has been established,
and enter the correct sector ID (0-based) for the RF Head:
Connection to RF Head 1 on modem in slot 5 established!

Changing Sector ID for RF Head 1, Modem 1
Enter Sector ID (0 to 3), or 'E' to leave unchanged: 2
Running test, please wait...
RF Head successfully set to sector 2
8. If any test fails, re-run the test when the problem is fixed. Note that each test can be run
individually. For example, to set a sector ID from the Main Menu, choose 3 for the Modem menu,
enter the modem number, choose 2 for the RF Head Menu, enter 1 when prompted for an RF
head number, then enter the sector ID as above.
At any time, entering ? will display a help screen.
9. Reboot the controllers when finished.
MAX204SGV4.0
510
AP Commissioning
Site Commissioning
Site Commissioning Information
Now that AP Calibration and AP Diagnostics have been run we can proceed to site commissioning.
The list below indicates the information that has to be acquired before commissioning takes place:
AP Domain Name:
External VLAN ID: (1-2303, 2432-4094)
Dynamic IP configuration: (0 = No, 1 = Yes)
The parameters marked with a * are required if Dynamic IP config IS NOT used (option 0 above)
Primary NTP Server Address*
Secondary NTP Server Address*
AP IP Address (Backhaul IP address)*

Subnet Mask*
Default Gateway IP Address*
Auto Negotiate link speed (1 = Yes)
Preferred DNS Server IP Address (Primary DNS)*

Alternate DNS Server IP Address (Secondary DNS)*
Network Maintenance Address (EMS Address)*
Number of Modems that should be present in the BCU

Number of Site Controllers that should be present in the BCU
Modem Trunking support (0 = No, 1 = yes)
TRX Power Source (0 = BCU, 1 = BBU, 2 = External Source)
Local Admin User Name

Local Admin User Password
Unix Root Account Password
Country Name
Organization Name
Common Name
MAX204SGV4.0
AP Commissioning
511
Site Commissioning
The following list details the procedure to carry out site commissioning:
1. Install all Modems and the Site Controller if they are not already installed.
2. Connect a serial cable from your laptop to the Site Controllers front panel serial port
3. Connect Crossover Ethernet cable between the Site Controller front Ethernet port (debug port) and
the laptop Ethernet adapter.
4. Start a Tera Term Pro on the laptop.
5. Select serial connection and the appropriate Com port on the window that will open in Tera Term.
6. Select the Setup drop down menu and select Serial port.
9600 baud
8 bit data, no parity
1 stop bit
no flow control
7. Boot the Site Controller
8. A message will appear on the console indicating that site commissioning data is not valid. Site
Commissioning must be performed if there is no site commissioning data. If site commissioning data
exists and is valid, the application will start up and run.
9. When the AP completes initialization or when a login prompt appears.
Login as root
User: root
password: root
10. Run the site commissioning application using the command:

/usr/app/bin/apcommission
11. Enter the appropriate data from the information collected during the pre-commissioning steps
when prompted.
Note, during the creation of the local admin account, the default user name is apadmin
MAX204SGV4.0
512
AP Commissioning
12. Enter 1 to commit commissioning data (site controller will continue to boot at this point).
13. Enter the appropriate LMT Certificate information collected during the pre-commissioning steps
from the LMT Security Certificate Related Parameters section when prompted.
14. Reboot the site controller.
15. If you wish to archive the site commissioning data, perform the following procedure:
When the AP completes initialization or when a login prompt appears.

o
Login as root
User: root
password: The password entered during the site commissioning procedure above
Run the following command:

/usr/app/bin/apcommission print > /data/site_commissioning_data.txt
Transfer the file /data/site_commissioning_data.txt to an appropriate host in the network via

sftp.
This may be the EMS or another host running a sftp server.
16. At this point the modems will begin the software loading process. Wait for the modems to come
up (they should reboot twice). Note the modem will not reach mac_state=2 and RF head code load
will not happen. This is expected behavior.
17. Install (push in) all modems and site controllers at this time.
18. Reboot the site controller.
19. Ping the EMS address provided during the Site Commissioning steps.
MAX204SGV4.0
AP Commissioning
513
Installation and Network Connection Verification

The following list details the procedure to carry out Installation and Network Connection Verification:
1. Connect an Ethernet cable between the Site Controller Debug port and the laptop
Ethernet adapter.
2. Ping the EMS address provided during the Site Commissioning steps if backhaul
connected.
3. Log in to the LMT by opening an internet browser, the address should be
https://144.190.240.1 (which is the IP address of eth0 port on the System
Controller Card and check the state of the Access Point FRUs via the LMT).
AP LMT View Node and FRU states
The next step in AP Installation is to bootstrap the AP.
That procedure is covered later in this
lesson.
MAX204SGV4.0
514
AP Commissioning
Hands-On Activity
Objective
The purpose of this activity is to give you practice in commissioning a WiMAX Access Point.
Student Brief
For the purposes of the activity you are about to undertake, the following points are to be noted.
1. The Access Point has been installed correctly and powered up.
2. At least one Ethernet connection from the Access Point to the
backhaul network has been provided.
3. Tools, ESSD wrist straps, test equipment and documentation will be provided by the
instructor.
Task Details
At all times when handling the Site Controller Cards, the Alarm Card, or the Modem Cards
of the Access Point, an ESSD wrist strap is to be worn. If the Optical fibers between the RF
Head and the BCU are removed, all relevant safety precautions are to be followed.
1. Ensure all equipment to be used in the commissioning procedure is
available and in a serviceable condition.
2. Configure as required the settings of the terminal emulator program on
the PC that is to be used in the commissioning procedure.
3. Ensure that the PC to be used in the commissioning procedure is loaded
with a web browser suitable for the commissioning procedure.
4. Ensure that the PC network connections (IP address & Proxy server setting)
are configured as per the commissioning procedure.
5. Using the form provided on the next page, obtain all the information required for
commissioning the Access Point (some of this information may be provided by the
instructor, while some may have to be obtained by the student by interrogating the network
as required).
6. Verify the current software version running on the Access Point.
7. Perform the Site commissioning procedure.
8. Perform Installation and Network Connectivity Verification.
MAX204SGV4.0
AP Commissioning
515
Field
AP Domain Name
External VLAN ID
Dynamic IP configuration
Primary NTP Server Address
Secondary NTP Server Address
AP IP Address (Backhaul IP address)
Subnet Mask
Default Gateway IP Address
Preferred NS Server IP Address (Primary DNS)
Alternative NS Server IP Address (Secondary
DNS)
Network Maintenance Address (EMS Address)
Auto Negotiate link speed
Number of Modems that should be present in the
BCU
Modem Trunking support
Local Admin User Name
Local Admin User Password
Unix Root Account Password
TRX Power Source
Country Name (LMT security Parameter)
Organization Name (LMT security Parameter)
Common Name (LMT security Parameter)
MAX204SGV4.0
516
AP Commissioning
Access Point Bootstrapping

The purpose of the bootstrapping procedure is to allow the Access Point and the EMS
to exchange secure key information. This will then allow the EMS to download software
and configuration files to the Access Point. The AP can be bootstrapped locally at the AP or
remotely from the EMS.
There are a number of steps involved with this process listed below:

Adding the Access Point / Sector
Bootstrapping procedure

To ensure that the Access Point is capable of carrying out the bootstrapping procedure, a
number of steps have to be achieved. These are as follows:
The AP has an initial software load installed and site commissioning has been
performed successfully.
The operator is able to successfully ping the EMS from the AP.
The AP and Sectors have been created in the EMS.
MAX204SGV4.0
AP Commissioning
517
MAX204SGV4.0
518
AP Commissioning
Adding the Access Point / Sector

Before the operator can continue with the bootstrapping procedure they must first add an
Access Point and sector at the EMS.
Adding the Access Point
Using the EMS Topology Manager, right click on the chosen CAPC payload set and
choose Add Access Point. When the add Access Point window launches. Enter the
following information
General Node Properties tab
IP address
Node name
MAC address (this is the MAC address of the Site Controller card obtained by
logging into the Access point site controller and entering ifconfig).
AP General tab
AP VLAN ID
Account username
When this data has been added, the data should be saved by selecting the save icon. If the
information has been saved correctly, the operator should then be able to select the AP
General tab and obtain the SNMP engine id. It should be noted that this information is
derived from the MAC address of the Site Controller Card.
MAX204SGV4.0
AP Commissioning
519
Add AP and Sector
MAX204SGV4.0
520
AP Commissioning
Bootstrapping Procedure
To carry out the bootstrap procedure the operator will require the following information:
The bootstrap ftp user name for the EMS.
The bootstrap ftp password for the EMS.
The SNMP engine ID from the EMS (the last 12 digits are the eth2.ext MAC address)
Use the following command to obtain the eth2.ext interface MAC address:
root@unknown:/root> ifconfig eth2.ext
When the above information has been obtained, the operator (on site using the
AP LMT, or from the EMS) should login to the Access Point and run the following
command:
/usr/app/bin/bootstrap <ftpUsername> <ftpPassword> <SNMP EngineID>
Having run this command the operator is to wait five minutes and then follow the validation
steps below to confirm bootstrapping is complete on both the Access Point and EMS before
proceeding with the software and configuration downloads.
There are two ways of knowing when the bootstrapping procedure is complete
on both the Access Point and EMS.
1. Verify user can see events appearing on the EMS in the event viewer for that particular AP.
This can be accomplished by right clicking on the AP in question and selecting "Event Viewer".
Verify timestamps for events that appear are recent.
2. Verify an invenotry refresh can successfully be performed by going to the AP node properties
window and selecting "Refresh Inventory Data" from the Tools menu.
If at this point the user can see events on the EMS via the event viewer, then no reboot of the AP is
necessary. If no events appear on the EMS after about 5-10 minutes, reboot the AP either via LMT or
a remote terminal to the APs SC. Rebooting generally takes a few minutes to complete.
Once the EMS shows a gold or green status, communication between the AP and EMS has been
initialized.
MAX204SGV4.0
AP Commissioning
521
Access Point Bootstrap
MAX204SGV4.0
522
AP Commissioning
EMS AP Configuration
Now that bootstrapping is complete the EMS can download Access Point configuration files. If the
Access Point has just been commissioned and successfully bootstrapped, the Access Point icon on
the EMS Topology Manger will be grey in color, and will show an arrow that indicates a
Configuration Download is required. The Access Point must be in locked state (prevents more
than one operator making changes) before the Sectors can be configured. All Access Point
Sectors must be configured before the Access Point itself can be downloaded with the node
configuration.
Configuration of the Access Point and its sectors is carried out using the configuration interface of
the EMS. The CAPC of the associated Payload Set must have had at least one prior successful
Configuration Download, as the Access Point requires some inherent parameters from the CAPC.
To build sector configuration, right click on a sector icon. This opens a drop down window. Select
Node Configuration to open the configuration window. On the graphic on the facing page the
ODFMA Downlink Channel is displayed. Data input items needed to configuring a sector require
detailed RF engineering knowledge. Tool tips for each item gives a brief explanation, valid data
range, and sometimes a critical business rule which must be complied with.
The configuration can be downloaded to the Access Point in full configuration (Network Element
Configuration Base, NECB), which contains the complete configuration for the Access Point or delta
configuration (Bulk Configuration Change, BCC), which contains only the changes since the last
configuration was loaded. A configuration download can be executed on-demand (only with a
single NE) or scheduled through the Download Manager for a later time. To use the Download
Manager, select the Add icon.
The EMS will use the BCC download method when downloading to an Access Point
except under the following conditions:
After an Access Point bootstrap

When executing Software Bundle Download;
Following a configuration version mismatch when attempting BCC download
After a Payload Set has been deleted from a CAPC
EMS operator demands an NECB download by setting the force NECB flag
A configuration download
will cause the Access Point
to reboot.
A successful Access Point Configuration Download will clear all locks from the Access Point
node as well as all Sectors. In addition, the down arrow (Configuration Download required)
symbol is removed from the Access Point icon on the EMS Topology Manger.
MAX204SGV4.0
AP Commissioning
523
MAX204SGV4.0
524
AP Commissioning
EMS AP Software Download

Earlier in this lesson we saw that software can be locally loaded on the AP. After bootstrapping is
complete, it is also possible to push software from the EMS to the AP.
A Software download to the Access Point may be required for one of two reasons.
The current Software is of an older version.
There is a mismatch error message generated during a configuration download.
While the software may be downloaded to the Access Point, separately from the configuration, they
will be downloaded together if the software download bundle is used. If an Access Point is running
an outdated software version, the user will receive a warning message about the mismatched
software version during configuration download. The operator can then determine if a software bundle
download is desired.
There is a default location (directory) on Portal EMS where up to 5 versions of software per NE
type can be retained NE software. Portal EMS will display a list of stored software of the NE type
in:
C:\Program Files\Motorola\PortalEMS\sftproot\softwareBundle
NE software can be imported by copying it from CD, other sources in the network or Motorola
Portal.
The naming convention and the format of AP and CAP-C downloadable software are:
[NE type]_WiMAX.[nn].[nn].[nn].tar.gz
To download software, right click on the AP icon. On the drop down menu, select Download
Software Then select from the available versions of software that has been previously loaded on the
EMS. To start the download, click on Start Software Download (the CD icon).
The Download Type of Software (FULL) indicated this is a bundled AP Configuration and Software
download.
Access Point Software Download

MAX204SGV4.0
AP Commissioning
525
Access Point Software Upgrade
MAX204SGV4.0
526
AP Commissioning
Software Download at the Access Point

The download process at the Access Point is carried out in three stages as listed below:
Download
Prepare
Activate
Download. The CNEOMI Lite Agent will automatically download the Access Point software bundle
from the EMS to the active Site Controller card. This bundle contains the Software, Operating System
and configuration for the for the Site Controller and Modem cards.
Prepare. The active Site Controller will now send a message to its peers (standby Site
Controller and Modems) telling them to pull the new software bundle from the active Site
Controller. All FRUs will now untar the bundle into an inactive partition. The active Site
Controller will send progress indications to the EMS throughout this prepare process.
Activate. The active Site Controller will notify its peers to reset onto the new
load but will not wait itself for a reply.
Once the download has taken place, the Access Point will reboot. To confirm that the software
download has been successful, the operator will see a green checkmark in the download manager or a
Push Successful message depending on how the push was initiated. The push will only come back as
successful on the EMS once the Access Point has rebooted in either an active or impaired state.
A software download will

cause the Access Point to
reboot.
MAX204SGV4.0
AP Commissioning
527
: EMS
: CLA
: 'SCMT-SC'
: 'SCMT-Modem'
// DOWNLOAD
// sftp bundle
Download
// send DOWNLOAD response

// PREPARE
// NEM I-PREPARE
// "start prepare"
// ftp bundle
Prepare
// return from "start prepare"

// return from NEMI-PREPARE
// send PREPARE response
// ACTIVATE
// NEMI-ACTIVATE
// "start activate"
Activate
// return from NEMI-ACTIVATE
// No reply for activate
// send ACTIVATE response
MAX204SGV4.0
528
AP Commissioning
Lesson Summary
Perform the procedure to carry out Access Point Commissioning and Bootstrapping
Perform the software upgrade procedures of the Access Point
MAX204SGV4.0
AP Commissioning
529

Access Point Commissioning, Bootstrapping and Software Upgrade
1.
The steps to complete Access Point initialization are _____.

a. Commissioning, Authentication, Authorization
b. Conditioning, Linkup, Bootstrap
c.
Commissioning, Bootstrap, Download
d. Negotiation, Bootstrap, Synch up

2.
When carrying out the bootstrap procedure, the Access Point must be connected to
the backhaul network.

a. True
b. False
3.
Which information is not needed for Access Point commissioning?

a. AP Domain Name
b. Primary NTP server address
c.
Number of sectors present
d. Number of modems present

4.
The purpose of the bootstrap procedure is to allow the Access Point and the CAPC
to exchange secure key information.

a. True
b. False
5.
The ____ is required to carry out the bootstrap procedure.

a. SNMP engine ID for the EMS B. C. D.
b. Bootstrap ftp user name for the EMS
c.
Bootstrap ftp password for the EMS
d. All of the above
MAX204SGV4.0
530
AP Commissioning
Hands-On Activity
Access Point Bootstrapping
Objective
The purpose of this activity is to give you practice in bootstrapping a WiMAX Access Point.
Student Brief
For the purposes of the activity you are about to undertake, the following points are to be
noted.
1.
The Access Point has been installed correctly, with power applied.
2.
Tools, ESSD wrist straps, test equipment and documentation will be provided by the
instructor.
Task Details
At all times when handling the Site Controller Cards, the Alarm Card, or the
Modem Cards of the Access Point, an ESSD wrist strap is to be worn. If the Optical
fibers between the RF Head and the BCU are removed, all relevant safety
precautions are to be followed.
1. Perform the pre-bootstrapping steps:
a.
Login to the Access Point from the PC using a remote terminal.
b.
Verify the Access Point has an initial software load
installed. c. Verify that the Access point is able to ping

the EMS.
2. Login to the EMS and verify that the Access Point has been
added to a CAPC payload card set.
3. Using the EMS, obtain the following information relevant to the
Access Point:
a. IP address
b.
Node name ______________________________
c.
MAC address _____________________________
d.
AP Vlan ID ______________________________
e.
Local Admin Account user name _________________
f.
SNMP engine ID __________________________
4. Perform the Access Point bootstrap procedure.

5. Verify the bootstrap procedure has functioned correctly.
MAX204SGV4.0
AP Commissioning
531
Hands-On Activity
Access Point Software / Configuration Download
The purpose of this activity is to give you practice performing a software and configuration
download to a WiMAX Access Point.
Student Brief
For the purposes of the activity you are about to undertake, the following points are to be
noted.
1.
The Access Point you are to use has been correctly installed and has power applied.
2.
The Access Point you are to use has been correctly commissioned.
3.
The Access Point you are to use has been correctly bootstrapped.
4.
Tools, ESSD wrist straps, test equipment and documentation will be provided by the
instructor.
Task Details
At all times when handling the Site Controller Cards, the Alarm Card, or the
Modem Cards of the Access Point, an ESSD wrist strap is to be worn. If the Optical
fibers between the RF Head and the BCU are removed, all relevant safety
precautions are to be followed.
1.
Verify that the Access Point has at least one sector that has been configured.
2.
Perform the pre-download procedure as set out below.

a.
Ping the Access point form the EMS to check connectivity.
b.
Verify that the current version of the software to be downloaded is held on the EMS.
c. Verify that the configuration of the Access point has been saved and added to the
download manager of the EMS.
3.
From the EMS Download Manager, perform a software /

configuration download to the Access Point.
4.
Verify that the download was successful.

a.
Ensure that the Access Point reboots correctly.
b.
Check that the green checkmark is displayed against the Access point on the
EMS.
c.
Verify that there are no outstanding alarms against the Access Point.
MAX204SGV4.0
532
AP Commissioning
MAX204SGV4.0
AP LMT
533
Lesson 10
AP Local Maintenance Terminal
MAX204SGV4.0
534
AP LMT
MAX204SGV4.0
AP LMT
535
Objectives
1. Describe the functions of the AP Local Maintenance Terminal
1. Log on to the AP LMT
2. Reset AP
3. Reset Modem
4. Interpret AP configuration
5. Modify AP configuration
6. Interpret Node and FRU states
7. Interpret Node Alarms
8. Interpret Node Statistics
9. Interpret daily log file
Student Activity
This lesson will include an instructor guided simulation of the AP LMT.
Introduction
The Access Point Local Maintenance Terminal (LMT) is a web-based application which provides an
interface for a user to perform a set of configuration, management, and debugging activities on the
Access Point. It is designed to augment (not duplicate) the functionality of the EMS.
MAX204SGV4.0
536
AP LMT
Adding LMT Users

The default admin user account will be set to apadmin. This user is in the administrator class and is
authenticated locally. Since not all operations can be performed with this user, it is required that more
users will be added to the system. Additional users can be added by logging into the site controller
command line as the root user and following the steps detailed below.
A locally authenticated user can be created with the following commands:
useradd -m -g <wadm|wcfgmgr|wtrouble|wtools> -s /bin/sh <username>
passwd <username>
An AAA-authenticated user can be created with the following command, but there will also be
additional steps required to provision this account on the AAA itself:
useradd -m -g <wadm|wcfgmgr|wtrouble|wtools> -s /bin/false <username>
Accounts and Authentication

LMT access requires a user account and password, which are managed centrally by the AAA server. However,
local accounts are required on the Access Point to maintain a user to class mapping. Every LMT user
account must fall into one of three user classes depending on the type of access they require. Only
those commands applicable to the class of the currently logged in user will be displayed in the LMT
menu. LMT users may be authenticated in one of two ways.
AAA Authentication. This is the default and is recommended due to its
central and more secure storage of passwords
Local Authentication. This allows users to access the LMT when an
AAA is not installed or out of service.
MAX204SGV4.0
AP LMT
537
Local authenticated user

useradd -m -g <wadm|wcfgmgr|wtrouble|wtools> -s /bin/sh <username>
passwd <username>
AAA authenticated user

useradd -m -g <wadm|wcfgmgr|wtrouble|wtools> -s /bin/false <;username>
Class
Linux Group(s)
Description
Administrator
wadm
Responsible for security task, tracing (debug) and

clearing of event logs. Not involved with
day-to-day operations
Operator
wcgfmgr
Responsible for NE software and patch upgrades

and configuration, real-time system monitoring,
troubleshooting and FRU restart. An operator
has full access to all management information
base on all managed NEs except the security
related information.
wtrouble
Guest
wtools
Performs operations requiring only non-invasive

access.
MAX204SGV4.0
538
AP LMT
Accessing the Access point LMT

The Access Point LMT functionality is accessed via an HTML browser such as Internet Explorer or
equivalent. There are two methods of accessing the LMT:
By logging in to the IP address of the Access Point
By logging in to the IP address of the Access Point Site Controller card

In both cases https:// should be used. All LMT HTML content is protected via HTTP Basic
Authentication and a user must first log in with a valid username and password in order to
execute LMT operations. Once a user has successfully logged in, they will remain logged in
until their web browser application is closed.
AP LMT Logon
MAX204SGV4.0
AP LMT
539
AP LMT Main Menu

The screens authorized for the Operator login are listed in the table below, but it should also be noted that
the availability of a command will also depend upon the software load.
AP LMT Main Menu
MAX204SGV4.0
540
AP LMT
AP LMT User Permissions

Screen permissions are linked to the User Login and Password.
Command/Menu item
Administrator
Operator
Reset Box
Reset Modem
X
X
View Running Configuration
Deploy New Configuration
View IP Network Configuration
Modify IP Network Configuration
View Ethernet Network Configuration
X
X
Modify Ethernet Network Configuration
Guest
X
X
View Active Interface Info
X
X
View Internal Device States
View State of Links to Other NEs
View Node and FRU States
View Active Alarms
View Connected MSs
Run Ping Command
Run Traceroute Command
X
X
X
X
Run Netstat Command
Dump ARP Cache
X
X
X
X
View Test Mode Configuration

Modify Test Mode Configuration
View Daily Log File
View Current Security Configuration
Deploy New Security Configuration

Start Bootstrap Procedure
X
X
Add a New LMT User
Remove an LMT User Account
MAX204SGV4.0
AP LMT
541
Reset Box
This command performs a graceful reset of the Access Point.
Reset Box
MAX204SGV4.0
542
AP LMT
Reset Modem
This command will perform a rest of one of the Modem Cards within the access point. The user can chose the
Modem card to be reset (14) and type of reset (hard or soft).
Reset Modem
MAX204SGV4.0
AP LMT
543

This command will retrieve and present to the user the contents of the current configuration (i.e.
Network Element Configuration Baseline) file.
MAX204SGV4.0
544
AP LMT

This command will accept a file containing Network Element Configuration Baseline data from the web
clients file system, place it on the Access Point, and make its contents active.
MAX204SGV4.0
AP LMT
545
View IP Network Configuration

This command will retrieve and present to the user a variety of information related to the IP network this
Access Point is connected to. Information such as Access Point IP address, subnet, gateway, DNS
servers, VLAN ID, EMS IP, and node name is presented. This command also displays if the Access
Point is configured to use DHCP to get its IP configuration.
View IP Configuration
MAX204SGV4.0
546
AP LMT
Modify IP Network Configuration

This command will accept a variety of configuration data related to the IP network the AP is operating
on from the web client user via an HTML form. The data entered by the user will be sent to and
made active at the Access Point. Configuration associated with fields which are left unmodified or
blank will remain unchanged. Via this option, a user can instruct the Access Point whether or not to
use DHCP to get its IP configuration. If DHCP is not being used, the user can also use this
command to modify information such as the assigned Access Point address, subnet, gateway, DNS
servers, VLAN ID, EMS IP, and node name.
Modify Network Configuration
MAX204SGV4.0
AP LMT
547
View Ethernet Network Configuration

This command will retrieve and present to the user a variety of information related to the Ethernet
network this Access Point is connected to. Information such as link speed, duplex setting, and auto
midi-X is presented. This command also displays if the Access Point is configured to auto-negotiate
the Ethernet configuration parameters.
View Ethernet Configuration
MAX204SGV4.0
548
AP LMT
Modify Ethernet Network Configuration

This command will accept a variety of configuration data related to the Ethernet network the
Access Point is operating on from the web client user via an HTML form. The data entered by the
user will be sent to and made active at the Access Point. Access Point configuration associated
with fields which are left unmodified or blank will remain unchanged. Via this option, a user can
instruct the Access Point whether or not to auto negotiate its Ethernet configuration parameters. If auto
negotiate is disabled, the user can then use this command to modify information such as Ethernet
link speed, duplex setting, and auto midi-X.
Modify Ethernet Configuration
MAX204SGV4.0
AP LMT
549
View Node and FRU States

This command will retrieve and present to the user the current operational state of the Access Point
as a whole as well as the slot, type, administrative state, and operational state of each individual field
replaceable unit (SC, modem card, alarm card, etc.).
View Node FRU States
MAX204SGV4.0
550
AP LMT

This command will retrieve and display a variety of information about the Access Points
interfaces. First, it displays a list of every active sector, modem, RF Head, and backhaul as
well as its corresponding administrative and operational states. It also displays a table
detailing all sectors to modem to RF Head mappings.
MAX204SGV4.0
AP LMT
551

This command will retrieve and present to the user the slot, type, administrative state, and
operational state of each individual internal device (GPS, Ethernet port, etc.) within the
Access Point View LMT - Configurable Parameters.
MAX204SGV4.0
552
AP LMT

This command will retrieve and display the type, number, administrative state, and operational state
of links from the Access Point to other network elements.
MAX204SGV4.0
AP LMT
553
View Active Alarms

This command will retrieve and present to the user a list of alarms which are currently active
on the Access Point as well as details about each.
MAX204SGV4.0
554
AP LMT
View Connected MSs

This command will retrieve and display the MAC addresses of all MSs which are
currently associated with the current Access Point.
MAX204SGV4.0
AP LMT
555
Run Ping Command

This command will accept a network address from the web client user via an HTML form, run a
ping on this address from the active site controller board within the Access Point, and present
the resulting data to the web client user as plain text.
MAX204SGV4.0
556
AP LMT
Run Traceroute Command

This command will accept a network address from the web client user via an HTML form, run a
traceroute on this address from the active site controller board within the Access Point, and
present the resulting data to the web client user as plain text.
Run Tracerout Command
MAX204SGV4.0
AP LMT
557
Run Netstat Command

This command will run a netstat command on the active site controller board within the Access
Point and present the resulting data to the web client user as plain text. The web client user can
choose via an HTML form, either netstat data on connected sockets, the state of interfaces being
used for IP traffic or the kernal routing tables.
MAX204SGV4.0
558
AP LMT
Run Netstat Command
MAX204SGV4.0
AP LMT
559
Dump ARP Cache

This command will retrieve and present to the user a dump of the active site
controllers Linux kernel ARP cache as plain text.
MAX204SGV4.0
560
AP LMT
View Test Mode Configuration

This command will retrieve and present to the user a report of the current values of several
configuration parameters used to enable special testing modes of the Access Point. The
parameters which are visible are as follows:
Uplink Modulation Coding Schemes

Downlink Modulation Coding Schemes
MAP message types
Generic parameters 1 5
MAX204SGV4.0
AP LMT
561
Modify Test Mode Configuration

This command allows the user to set the values of several configuration parameters used to enable special
testing modes of the Access Point. The parameters which can be modified are as follows:
Uplink Modulation Coding Schemes

Downlink Modulation Coding Schemes
MAP message types
Generic parameters 1 5
MAX204SGV4.0
562
AP LMT
View Daily Log File

This command will retrieve and present to the user as plain text the current contents of a daily log file.
This file is currently the syslog messages file and contains important system messages as well as
what LMT actions have been requested recently and the requesting user.
View Daily Log File
MAX204SGV4.0
AP LMT
563
Administrator Screens
The following screens are available only to users with an Administrator login and password.
View Current Security Configuration

This command will retrieve and present to the user the contents of the current security configuration files.
This currently includes files used to configure the APs IPsec policy.
MAX204SGV4.0
564
AP LMT

This command will accept a file containing IP sec configuration data from the web clients file system,
place it on the Access Point, and make its contents active.
MAX204SGV4.0
AP LMT
565

This command will initiate bootstrapping.
MAX204SGV4.0
566
AP LMT
Add a New LMT User

This command will add a new AAA-authenticated LMT user to the Access Point. The operator must choose
one of three classes for the new user at the time of creation. It is important to note that the new user
must also exist at the AAA before it can be used to access LMT.
Add New User
MAX204SGV4.0
AP LMT
567
Remove an LMT User Account

This command will remove an LMT user from the Access Point. Users deleted in this
manner will continue to exist in the AAA and should also be deleted from there as well to
avoid filling the AAA with unnecessary accounts.
Remove User
MAX204SGV4.0
568
AP LMT
Lesson Summary
Describe the functions of the AP Local Maintenance Terminal
MAX204SGV4.0
AP LMT
569
MAX204SGV4.0
570
AP LMT
MAX204SGV4.0
AP Troubleshooting
571
Lesson 11
AP Troubleshooting
Objectives
At the end of this lesson you will be able to:
1. Use on-site observation, the Element Management System (EMS) and the Local Maintenance
Terminal (LMT) to identify Access Point problems
2. Restore the Access Point to full operation
Tasks
1. Use the EMS network topology tree to determine AP node state
2. Use the LMT to manage AP operation
3. Graph AP statistics
4. Interpret AP statistics
5. Interpret AP Alarms and Events
6. Filter AP Alarms
7. Isolate AP failure
8. Determine root cause of AP problems
9. Restore AP performance
Introduction
There are many tools available to the used to assist in identifying AP trouble. This lesson will provide
information on the use of these tools in the identifying of trouble and restoring service at the AP.
MAX204SGV4.0
572
AP Troubleshooting
Identifying AP Problems
Trouble conditions can be identified:
On-site observation of conditions at the AP BCU

By monitoring alarm conditions at the EMS
By monitoring alarm and log information at the LMT
On-site Observation
The place to start onsite troubleshooting is at the BCU Alarm card. The BCU Alarm card faceplate LEDs
present information concerning basic BCU conditions such as:
The operation of the fan unit
High/Low temperature conditions
Status of the GPS and MSO units
Operational state of the RF Units
Status of the Alarm card itself
BCU Alarm Card
The other BCU cards also contain faceplate LEDs for use in identifying AP operational states.
See the AP Hardware lesson for additional BCU card LED details. There are no LEDs on the RF Head.
MAX204SGV4.0
AP Troubleshooting
573
Element Management System - EMS

The EMS receives stores and displays events and alarms generated by the AP. A color code is used to
indicate NE state. Notice the AP selected is shown in GREEN. This indicates that it is UP and operational.
Dark BLUE indicates a NE is Down, a Not Present NE is shown as GREY and Unknown is displayed as Light
BLUE. This gives us a quick snapshot of NE health.
Events and alarms are viewed using the EMS GUI Event Viewer. The Event Viewer is launched by selecting
the Alarm Bell icon.
Alarm Bell icon
MAX204SGV4.0
574
AP Troubleshooting
Event Viewer
There are over 80 possible alarm conditions that may be reported on the AP.
defined.
Sixteen of them are customer
AP Alarms and Events are collected at preset intervals of either 15, 30 or 60 minutes. This interval is
determined during AP configuration.
Events and alarms are displayed on the Event Viewer screen as shown below. The columns in this display
are:
Acknowledged
Cleared
Severity
Date Source
EMS Tag
Details
A check mark in the ACK field indicates the alarm has been acknowledged and is being worked on. A check
mark in the Cleared field indicates the alarm condition has cleared.
Users may order the display by severity or date. Notice that the alarm severity is color coded. Events are
reported with a normal severity
Event Viewer
MAX204SGV4.0
AP Troubleshooting
575
Alarm Selection
Alarms are selected and acknowledged by double clicking the event or alarm on the display.
Once an alarm is selected, detailed information pertaining to the event or alarm is displayed.
A possible resolution is also offered.
Detailed Information
MAX204SGV4.0
576
AP Troubleshooting
Filters
By default, all alarms and events are available to be displayed. Up to 500 items can be displayed at a time
on one page. Users may wish to make use of filters and page size (default is 50 items per page) to limit the
amount of information displayed.
Filters are available for all columns except Details.
Severity filter options include Critical, Major, Minor, Warning, Acknowledged and Cleared. To use the
Severity filter simply check the boxed for the alarm levels you wish to see.
The Source filter uses the main display. The operator selects rows that match the data in the source column.
The Date filter sets the beginning and end time to view.
Severity Filter
MAX204SGV4.0
AP Troubleshooting
577
Statistics
AP performance statistics are collected at preset intervals of either 15, 30 or 60 minutes. This interval is
determined during AP configuration.
Statistics collection interval
MAX204SGV4.0
578
AP Troubleshooting
Historical Statistics
Historical statistics are displayed by selecting an AP and clicking on the chart icon. The left pane of the
statistic window contains a list of the various statistics collected. The user may select up to five statistics to
plot. Each statistic selected is assigned a color to be graphed. After all selections have been made, click
the Plot or graph button. A new window with the graphical representation of the selected statistics is
displayed.
MAX204SGV4.0
AP Troubleshooting
579
Historical Statistics Graph

Up to 5 stats can be selected for graphic plotting. Selected stats are plotted in different colors. The graphic
name can be defined by user. Up to 20 graphs can be plotted and the displays can be cascaded or tiled for
comparison. A warning will appear after 10 plots are displayed.
MAX204SGV4.0
580
AP Troubleshooting
Local Maintenance Terminal LMT

Many of the LMT screens covered in the AP LMT lesson may be of use during troubleshooting. The most
obvious would be the View Active Alarms screen. All alarms available at the EMS may also be viewed
using the AP LMT. We will see later in this lesson how to use other LMT screens to identify faults and
restore service.
AP LMT View Active Alarms screen
MAX204SGV4.0
AP Troubleshooting
581
Correcting On-site Problems

Some reported alarm conditions will require an on-site visit to restore operation. These conditions will likely be
a result of a hardware fault in a Field Replaceable Unit (FRU). In many cases replacement of the faulty
equipment clears the alarm. The material that follows is a look at some of the alarm reports these failures
will generate. This is not intended to be a complete listing of all AP Alarms.
For detailed information on AP Alarms and troubleshooting please consult the following Motorola documents
which are available at My Network Support:
WiMAX System Alarms
Performance Statistics and Analysis
EMS Parameters
WiMAX LMT Reference Guide
WiMAX System Troubleshooting Guide
Hardware Faults
Access Point
BCU Cabinet
These alarm conditions reflect the state of the BCU support equipment.
Alarm
Surge Protector Failed
Cold Start Heater Relay 1, 2,
both Failed
Under Temperature
BCU Cage Fan Failed
BCU Air Flow Fault
BCU Cabinet Door Open
FRU Missing
GPS/MSO Hardware Failed
GPS free-run time expired
BCU Power Insufficient
Power Supply Fault
Power Supply Mismatch
Input Power System Failure
Operator Action
Replace surge suppressor
Replace cold start heater relay
Replace BCU heater assembly
Replace BCU cage fan
Service air filter
Close and lock cabinet door
Insert FRU if needed
Replace GPS receiver/antenna or replace MSO
Check for GPS and MSO faults
Install appropriate additional power supply
Replace Power Supply Unit
Replace mismatched Power Supply Unit
Troubleshoot power system
MAX204SGV4.0
582
AP Troubleshooting
BCU Cabinet Trouble Identification and Resolution

We will use the GPS Hardware Failed Alarm to provide an example of troubleshooting.
The GPS Hardware Failed alarm may be caused by a failure of the GPS Head, the GPS Surge Protect
Module, the RF GPS Module, or the cables connecting them.
The steps described are adapted from the WiMAX System Troubleshooting Guide.
GPS Components
MAX204SGV4.0
AP Troubleshooting
583
BCU Cabinet Trouble Identification and Resolution

The table below provides the steps needed to determine which component has caused the alarm. Following
this procedure will restore the GPS system to service.
Step
1
2
6
7
8
9
10
11
12
Action
GPS Hardware Alarm is received
Perform a visual inspection to verify that all the cables are correctly connected.
Verify that there are no obstructions blocking the GPS head.
Verify that there is power applied to the GPS head.
The system requires three minutes to recognize the GPS head. The
GPS requires up to 20 minutes to lock onto a minimum of four
GPS satellites
Connect a spectrum analyzer to the Surge Protect Module end of the antenna cable,
and verify there is a signal present.
If there is a signal, reconnect antenna cable to Surge Protect Module, proceed to step 4.
If not, replace this cable or the GPS Head.
Disconnect cable from RF GPS Module to Surge Protect Module.
Connect spectrum analyzer to output of Surge Protect Module.
Verify that a signal is present. If so reconnect cable to Surge Protect Module.
Verify that after a short time, the Alarms card GPS GREEN LED is lit.
Proceed to step 11
If not, proceed to step 5
Leave RF GPS Module to Surge Protect Module cable disconnected.
Disconnect cable from Surge Protect Module to antenna.
Disconnect ground cable, if in use.
Remove nut and washer securing Surge Protect Module to BCU.
Remove Surge Protect Module.
Replace Surge Protect Module.
Secure Surge Protect Module to BCU with nut and washer supplied with replacement.
Connect cable from RF GPS Module to Surge Protect Module.
Connect cable from Surge Protect Module to antenna.
Connect ground cable, if it was used.
Verify that after a short while, the Alarms card GPS GREEN LED is lit.
Proceed to step 14
Connect spectrum analyzer to RF GPS Module end of cable, and verify signal is
present.
If so, reconnect cable to RF GPS Module, and proceed to step 12.
If not proceed, replace this cable.
The RF GPS Module is the last remaining item. If there is a signal at all of the cables
and still no timing, then this module needs replacement.
13
Remove the four screws securing the module to the Customer Interface I/O.
Replace RF GPS Module.
14
Alarm card GPS GREEN LED is lit.
MAX204SGV4.0
584
AP Troubleshooting
BCU Cabinet Cards

These alarm conditions reflect the state of the BCU plug-in cards.
Alarm
Alarm Card Fault
Mate Controller Failed
Site Controller Warning
Site Controller Failure
SC A frame synch alarm
PHY Overload Alarm

PHY Failure
Modem HW Failure
BHP Lost Communication with
OHP
Frame Failure
EncDec Failure
Modem Communication Failed
Operator Action
Replace Alarm card
Replace Site Controller card if condition persists
Replace Site Controller card
Replace Site Controller card
If all Modems are reporting this alarm then it is probably a
Site Controller problem, otherwise it is probably a Modem
problem
Replace Modem card if alarm persists
Reset Modem card (replace if condition persists)
MAX204SGV4.0
AP Troubleshooting
585
BCU Cabinet Cards Trouble Identification and Resolution

We will use the procedures laid out in the WiMAX Troubleshooting Guide to resolve a Modem Hardware
Failure alarm.
Step
1
Action
Modem HW Failed Alarm is received
The normal state for the Modem Status LEDs is Green On / Red Off.
Verify that the Modem card is in the correct slot and properly seated.
Pull card and inspect for damage to components or connectors.
Verify that Modem circuit breaker is pushed in on Circuit Breaker card.
Verify that the code load is the latest revision.

If Modem card is still under alarm, replace the Modem card.
Replacement Modem card: STLN6398.
Disconnect all cables from Modem card.

Install new Modem card.
New Modem card will boot, if new software upgrade is required it will reboot to load
software, and reboot before going active.
6
Connect all cables disconnected in step 5.
MAX204SGV4.0
586
AP Troubleshooting
RF Head
These alarm conditions reflect the state of the RF Heads and Antennas.
Alarm
Antenna Failure (RF Head 1:4)
DAP Q-BBB TRX#1 Link
Failure (RF Head 1:4)
DAP Q-BBB TRX#2 Link
Failure (RF Head 1:4)
DAP Q-BBB Link#1
Temperature (RF Head 1:4)
DAP Q-BBB Link#2
DAP Q-BBB Link#3
DAP TRX#1 Alarm (RF Head
1:4)
DAP TRX#2 Alarm (RF Head
1:4)
DIV RF Head#1 SIB Alarm (RF
Head 1:4)
Head 1:4)
Head 1:4)
Operator Action
Service Antenna
Replace RF Head
Replace RF Head
Replace RF Head (if multiple RF Heads have this problem it
is probably an environmental condition)
Replace RF Head
Replace RF Head
Replace RF Head
Replace RF Head
Replace RF Head
MAX204SGV4.0
AP Troubleshooting
587
RF Head Trouble Identification and Resolution

For this example we will assume that a DAP TRX Alarm has been received.
Step
1
Action
At the EMS:
Check the Managed Object name to identify the RF Head under alarm.
At the site:
Check the Alarm card to verify that the RF Head under alarm (RFU 1 through RFU 4) is
the same one noted at the EMS. The RF Head under alarm will have the Red LED lit.
Inspect the Fiber Optic cable. Verify that the cable is undamaged. Disconnect it from the
BCU and verify that no pins are damaged. If no damage, reconnect it.
Disconnect the Fiber Optic cable from the RF Head and verify that no pins are
damaged. If no damage, leave it disconnected.
If an optional filter is in use, proceed to before doing anything further.
Replace RF Head.
At the BCU Circuit Breaker card, pull the appropriate RF Head circuit breaker
(RF1, RF2, RF3, or RF4) to disconnect DC power.
Disconnect DC power and ground cables from RF Head.

Record the direction and azimuth of the RF Head
Loosen or remove all connecting hardware on bracket.
Remove RF Head.
Install new RF Head along with connecting hardware.

Ensure that the RF Head is properly aligned according to direction and azimuth values
recorded in step 5.
Ensure that screws securing RF Head to bracket are torqued to 45 in-lbs
(5.0 N-m).
Attach ground, DC power, and Fiber Optic cables.

Ensure that Fiber Optic cable is properly connected
and nut is torqued to 38 in-lbs (4.3 N-m).
Ensure that ground cable is connected to RF
Head. Torque screw to 45 in-lbs (5.0 N-m)
Ensure that DC power cable is properly connected and coupling nut is torqued to 38
in-lbs (4.3 N-m).
At the BCU Circuit Breaker card, push in the circuit breaker for the new RF
Head. On the Alarms card, the RF Head Green LED should be lit.
If the new RF Head is part of a non-trunked configuration, reboot only the Modem
configured for that RF Head. If it is part of a
trunked configuration, all the Modems must be rebooted.
MAX204SGV4.0
588
AP Troubleshooting
Link Problems
These alarms reflect the state of the internal AP links, backhaul links and other AP links.
Alarm
Backhaul Ethernet port #1
failure
Backhaul Ethernet port #2
failure
Backhaul Ethernet Link failure
AP-CAPC Link Failure
SC-Modem (1:4) Ethernet Link
Failure
BBB Link # (1:3) Alarm
Operator Action
Troubleshoot Backhaul Link #1
Troubleshoot Backhaul Link #2
Attempt to restore backhaul
Possible site visit to replace faulty Physical Link
Troubleshoot and replace either Site Controller or Modem
Faulty Link requires on-site debug to determine faulty FRU
RF Head or Modem
Link Trouble Identification and Resolution

For this example we will assume a BBB Link alarm has been received. This alarm may be caused by a
defective fiber cable between the RF Head and the BCU, Modem card transceiver, the Modem card or the RF
head. The following procedure will help determine the root cause of the problem.
Step
1
Action
Locate the indicated fiber optic interface on the front panel of the Modem under alarm
and disconnect the fiber optic connector.
Check for visible light being emitted from the transmit side of the fiber optic transceiver.
If there is visible light from the fiber optic transceiver, proceed to step 3.
If there is no visible light, replace the fiber optic transceiver (they are
hot-swappable). If light is now visible from the fiber optic transceiver, reconnect the fiber
optic cable and check if the alarm condition clears.
If light is still not visible from the fiber optic transceiver, proceed to step 4.
Check for visible light being emitted from the receive fiber (transmitted by the RF Head).
If there is visible light in the fiber continue to step 4.
If there is no visible light, proceed to step 5.
Replace the Modem (hot-swappable) and look for the alarm condition to clear. If the
alarm condition clears, return the Modem for repair; otherwise, proceed to step 5.
If the customer has equipment that allows them to independently test the integrity of the
fiber cables they should do so at this time.
If the fiber cables test OK or the customer does not have the equipment to test them,
proceed to step 6.
If the fiber cables test bad, replace them. If the alarm condition still does not clear,
proceed to step 6.
Replace the RF Head at the other end of the alarmed fiber optic link. If the alarm clears,
return the RF Head for repair. If the alarm does not clear, proceed to step 7.
Replace the fiber optic cable between the Modem and RF Head (if it has not been
tested independently).
MAX204SGV4.0
AP Troubleshooting
589
Other AP Alarms
Troubleshooting and problem resolution of the following alarms may be done on-site with the LMT or remotely
at the EMS.
Alarm
Sector Improperly Configured
Operator Action
If an RF Head is improperly programmed, the operator must
reprogram the Sector ID in the RF Head. If the NECB's
sector configuration does not reflect the AP's physical
configuration, it should be updated. If sector initialization is
in progress, the alarm will automatically clear on completion.
SW Failure
Device Restarts automatically. May cause site outage if SC

reset or dropped calls if Modem
Critical MIB Failure
Problem exists in the MIB. Update the MIB to resolve the

issue.
DHCPR Failure
Verify DHCP Server Address and AP DNS Server are valid.
Data Loss
Modem Capacity Reached
VLAN Packet Dropping
Exceeded High Threshold
None
None
Check BRAS configuration for VLAN tag NSP <-> NAP
translation.
Check AP configuration in EMS of NSP domain to VLAN
mapping.
Check NSP domain and VLAN provision in AAA user profile.
Customer Defined Alarms

There are 16 customer defined alarms that can be triggered by either a contact opening or contact closure.
These alarm points may be assigned to things such as intrusion detection, smoke/fire alarm or to indicate the
status of ancillary equipment. Connection to these alarm points is on the Input/Output unit, accessed via the
BCU back door.
MAX204SGV4.0
590
AP Troubleshooting
Ground-based Access Point (GAP)

The GAP is a 3 sector Tower-Bottom WiMAX Access Point which can be installed in indoor or outdoor
cabinets or in an indoor rack arrangement. Most GAP alarms are identical to those of the DAP. Exceptions
include:
GAP TRX Fan Alarms
Tower Top Low Noise Amplifiers (TTLNA) Alarms

o
Communication
Configuration
General Failure
Battery Backup Unit (BBU) Alarms
MAX204SGV4.0
AP Troubleshooting
591
Ground-based Access Point BBU Alarms

The outdoor Ground-based Access Point (GAP) may be installed with Battery Backup Units (BBU) to provide
power during power outages. When a GAP BBU is present, the GAP BBU Alarms make use of a subset of
the Customer Alarm inputs. During the system installation procedure, the installer is prompted to enter
whether a BBU is present or not. If the installer enters that it is, then the BBU Alarms will be mapped to the
Customer Alarm inputs per the table below. If a BBU is not present, then the associated Customer Alarm
Inputs are available for other use.
Alarm
GAP_BBU-Door
Intrusion
GAP_BBU-Customer
Alarm
GAP_BBU-Surge
Protect Fail
GAP_BBU-AC Fail
GAP_BBU Minor
GAP_BBU-Major
GAP_BBU-Battery
Over-temp
GAP_BBU-Rect Fail
Reason for Alarm

Allows Customer to know if an intruder opens any
BBU door at a remote Site.
Allows the customer an alarm for internal optional
equipment, such as Hydrogen monitoring.
If an AC surge event occurs that destroys the
surge protector, allows the Customer to know that
it needs to be replaced prior to the next event.
Allows Customer to know that the Site has lost AC
power and has started battery backup. It also
allows immediate power savings measures to be
taken.
Indicates a minor internal Rectifier System alarm.
Refer to the appropriate Rectifier Shelf Manual for
conditions which would create such an alarm.
Indicates a major internal Rectifier System alarm.
Refer to the appropriate Rectifier Shelf Manual for
conditions which would create such an alarm.
Indicates that the Batteries exceed temperature
thresholds.
Indicates one or more Rectifiers have failed.
Customer
Alarm
Input
9
Alarmed State
Open Circuit
10
Open Circuit
11
Open Circuit
12
Open Circuit
13
Open Circuit
14
Open Circuit
15
Open Circuit
16
Open Circuit
Note: If 2 or more Rectifiers have failed, the

GAP_BBU-Major Alarm will also be enabled.
MAX204SGV4.0
592
AP Troubleshooting
Lesson Summary
Use on-site observation, the Element Management System (EMS) and the Local Maintenance
Terminal (LMT) to identify Access Point problems
Restore the Access Point to full operation
MAX204SGV4.0
WiMAX Network Troubleshooting
593
Lesson 12
WiMAX Network
Troubleshooting
MAX204SGV4.0
594
Troubleshooting
MAX204SGV4.0
WiMAX Network Troubleshooting
595
Objectives
1. Describe the 6 step network troubleshooting approach for the ASN.
2. Describe the use of network tools to determine extent of fault.
3. Describe the functions needed to correct the fault.
1. Interpret system information
2. Interpret sniffer/traces
3. Interpret WiMAX statistics
4. Isolate network failure
5. Isolate problem to box or network
6. Isolate problem to board, component or software
7. Isolate configuration problems
8. Troubleshoot VoIP call
9. Troubleshoot data
10. Verify CPE/SS connection
11. Use EMS/LMT/LEDs to identify network outages
12. Use statistics logs to analyze network performance
13. Use test equipment to analyze network performance
14. Determine the root cause of a problem
15. Restore network operation
16. Test network performance
MAX204SGV4.0
596
Troubleshooting
MAX204SGV4.0
Appendix A My Network Support
597
Appendix A
My Network Support
MAX204SGV4.0
598
Window to Products & Services

MyNetworkSupport provides information on the products and services that
support Motorolas Network Solutions.
Here you can find useful documentation and support materials such as:
Documentation - View the following product documentation quickly and easily using MyQuickLinks:
Bulletins, MOPs, White Papers, Health Checks, and Product Manuals.
Technical Support - Use the on-line support tool to create service requests, check on or add notes to
existing requests, as well as notify us if you would like us to close a service request.
Board Repair / Hardware Support - Use on-line support to create and check the status of your RMAs.
Training - View a comprehensive description of available courses, registration instructions, class
schedules and locations available to our infrastructure customers worldwide.
MyAccount - Manage your MyNetworkSupport account profile, notifications, and module access.
MyNetworkSupport Intro
Inside MyNetworkSupport
Quick Links and the Navigation bar provide easy access to what you need.
Using Quick Links to find specific
documentation:
9
9
9
Select a category or product from the first

pull-down menu on the bulletin or
document side.
Then select an option or release from the
second menu.
The search will launch immediately after the
second selection.
Use the Navigation Bar on the left hand

side to gain access to more site
products and services.
Navigation Bar
Quick Links
MAX204SGV4.0
599
MyAccount
Customize your MyNetworkSupport profile by clicking on the MyAccount link in
the top navigation bar.
MyAccount Link
Here you can:
Modify your account details and
password
Modify your subscriptions for bulletins,
documentation, training, and more
Manage Your Account
Enable Auto-Notifications
MyAccount (continued)
Request access to service modules on
the site.
Request Access to Modules
MAX204SGV4.0
600
WiMAX Technology
WiMAX Bulletins
MAX204SGV4.0
601
WiMAX Documentation
WiMAX Training
MAX204SGV4.0
602
MAX204SGV4.0

MAX204 Student Guide v4 (1) .0

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MAX204 Student Guide v4 (1) .0

Uploaded by

Copyright:

Available Formats

MAX 204 - Network Configuration,

Operations, and Maintenance

Motorola, Inc. All Rights Reserved

MAX204 Network Configuration, Operations and Maintenance

Motorola, Inc. All Rights Reserved

MAX 204 Network Configuration, Operations, and Maintenance

Motorola, Inc. All Rights Reserved

MAX204 Network Configuration, Operations and Maintenance

MAX 204 Network Configuration, Operations, and Maintenance

Service Flows and Service Flow Identifiers........................................................................................................... 102

MAX204 Network Configuration, Operations and Maintenance

Student Activity Call Flow Processes Team 2 ................................................................................................. 154

MAX 204 Network Configuration, Operations, and Maintenance

Student Activity Troubleshooting scenarios Team 3 ....................................................................................... 202

MAX204 Network Configuration, Operations and Maintenance

Power Distribution Redundancy Model................................................................................................................. 348

MAX 204 Network Configuration, Operations, and Maintenance

Session Management ............................................................................................................................................. 450

MAX204 Network Configuration, Operations and Maintenance

View Daily Log File .............................................................................................................................................. 562

Motorola, Inc. All Rights Reserved

MAX 204 Network Configuration, Operations, and Maintenance

Motorola, Inc. All Rights Reserved

MAX204 Network Configuration, Operations and Maintenance

How to Use this Guide

About this Guide

Organization of this Guide

Conventions Used in this Guide

Indicates a Hint such as a

Indicates a Note or additional

Motorola, Inc. All Rights Reserved

MAX204 Network Configuration, Operations and Maintenance

Lesson 1 WiMAX Overview

Lesson 2 WiMAX Networking

Lesson 3 WiMAX Call Processes

Lesson 5 CAPC Hardware

Lesson 6 CAPC Installation & Troubleshooting

Lesson 9 AP Bootstrap, Commissioning and Software Upgrade

TOTAL COURSE TIME IN DAYS

Motorola, Inc. All Rights Reserved

MAX204 Network Configuration, Operations and Maintenance

Motorola, Inc. All Rights Reserved

MAX204 Network Configuration, Operations and Maintenance

Motorola, Inc. All Rights Reserved

MAX204 Network Configuration, Operations and Maintenance

WiMAX Network Overview

Motorola, Inc. All Rights Reserved

WiMAX Network Overview

Understand the purpose of each WiMAX network element

Motorola, Inc. All Rights Reserved

WiMAX Network Overview

802.3 Ethernet Network

802.X Ethernet Network

Motorola, Inc. All Rights Reserved

WiMAX Network Overview

Metropolitan Area Network

A network that covers great distances

A network that covers a large geographic area

Local Area Network

Personal Area Network

A network that covers a limited geographic area

A network that covers a very small area

Motorola, Inc. All Rights Reserved