ZyXEL

WiMAX IEEE802.16e MIMO CPE Support Node

Version 3.1

Revision History Date: 2008-11-13 2009-02-13 2009-03-30

Version and description: Support Node for MIMO CPE Support Node for MIMO CPE Support Node for MIMO CPE 1/80

Author: Justin Lin Patrick Lin Poyi Yu

Contents
1. Introduction ........................................................................................................................ 4
1.1 1.2 Key Benefits of ZyXEL WiMAX CPE Products ............................... 4 Hardware Brief of Simple CPE ........................................... 4 NAT and Router Features ................................................ 6 Firewall Features ...................................................... 6 Network Management ..................................................... 7 Pre-Provisioning ....................................................... 7 Local Provisioning ..................................................... 7 Remote Provisioning .................................................... 8
Web Interface ....................................................................................................................................8 Telnet Interface ..................................................................................................................................8 SNMP .................................................................................................................................................9 TR-069 ...............................................................................................................................................9

2.

Networking Features ......................................................................................................... 5

2.1 2.2 2.3

3.

CPE Provisioning Mechanism ......................................................................................... 7

3.1 3.2 3.3

3.3.1 3.3.2 3.3.3 3.3.4

4.

User Authentication......................................................................................................... 11
4.1 4.2 EAP-TTLS .............................................................. 11 EAP-TLS ............................................................... 12

5. 6.

VoIP Features ................................................................................................................... 13 Maintenance Guide.......................................................................................................... 14

6.1 Connection and Setup .................................................. 14
Start the Connection Manager ........................................................................................................14 Start Network Entry ........................................................................................................................17 6.1.1 6.1.2

6.2 6.3 6.4 6.5 6.6 6.7 6.8

Check Device Status ................................................... 19 Useful System CLI command ............................................. 22 Useful WiMAX CLI command .............................................. 24 Useful WiMAX Debug command ............................................ 26 Useful VoIP Debug command ............................................. 27 Useful TR069 Debug command ............................................ 27 Useful VPNT Command ................................................... 30
Use of Untagged Customer Interface in Bridge Mode .................................................................30 Use of Untagged & Tagged Customer Interface in Bridge Mode................................................32 Use of Untagged Customer Interface in Routing/NAT Mode......................................................37 GRE Tunnel via LAN Port to Bypass Radio Link Uncertainty ...................................................38 2/80

6.8.1 6.8.2 6.8.3 6.8.4

6.9

Software Upgrade ...................................................... 44

Download Files ................................................................................................................................44 Unzip the files..................................................................................................................................44 Upgrade Notification.......................................................................................................................44 Upgrade SYSTEM BOARD ...........................................................................................................44 Reset to DEFAULT ROM ..............................................................................................................45 Upgrade WiMAX CARD ...............................................................................................................46 ONE STEP FW/SW Upgrade .........................................................................................................47

6.9.1 6.9.2 6.9.3 6.9.4 6.9.5 6.9.6 6.9.7

6.10 Hardware Reset Mechanism .............................................. 48

6.10.1 6.10.2 6.10.3 Normal reboot..................................................................................................................................48 Level 1 Reset ...................................................................................................................................48 Level 2 Reset ...................................................................................................................................49

7.

Troubleshooting ............................................................................................................... 50
7.1 7.2 7.3 7.4 7.5 7.6 What can I do when struggling in the DL_SYN and Ranging process? ...... 50 What can I do when struggling in the Authentication process? .......... 53 What can I initiate the IDLE process? ................................. 56 What can I do the IDLE troubleshooting? ............................... 56 What can I do the handover troubleshooting? ........................... 57 What can I do the VOIP troubleshooting? ............................... 58
Use WireShark software to catch the VOIP trace log...................................................................58 Use ZyXEL console line to catch the VOIP trace log. .................................................................59

7.6.1 7.6.2

8.

Appendix ........................................................................................................................... 65
8.1 8.2 FAQ ................................................................... 65 TR-069 Parameters ..................................................... 65
WiMAX Specific TR-069 parameters ...........................................................................................65 InternetGatewayDevice parameter: ................................................................................................65 InternetGatewayDevice.Service.VoiceService parameters: .........................................................73 Vendor-Specific Parameter:............................................................................................................78 InternetGatewayDevice.X_WIMAXFORUM_OperatorProfile Parameter: ............................78

8.2.1 8.2.2 8.2.3 8.2.4 8.2.5

3/80

1. Introduction
This document is written for system operator to properly install the WiMAX MIMO CPE.

1.1 Key Benefits of ZyXEL WiMAX CPE Products

WiMAX 802.16e enables mobility ZyXEL MIMO CPE is compliant to WiMAX 802.16e specifications which provides mobility SIP Based VoIP Communication VoIP signaling supports standard SIP (RFC3261), suitable for IP telephony service deployment. Sophisticated voice compression provides toll quality voice communication. Effective QoS Control ZyXEL MIMO CPE fully utilizes the WiMAX QoS features and provides different service level based on the upper layer applications. Built-in radio antenna The antennas are built in with the enclosure which provides flexibility. Easy to Deploy ZyXEL MIMO CPE is designed to be self-installable by end user without operators truck roll-out. LED bars which show the WiMAX radio signal strength can used to adjust the direction and position of WM100 in order to get better connection. Software upgrade over the air ZyXEL MIMO CPE is fully software upgradeable over the WiMAX radio interface and can be triggered by operator. Robust, State-of-the-Art Firewall Security The ICSA certified ZyNOS operating system ensures state-of-the-art Firewall performance and robust security from the WM100. Based on Stateful Packet Inspection (SPI) and Denial of Service (DoS), it provides the first line of defense against hackers, network intruders, and other hazardous threats.

1.2 Hardware Brief of Simple CPE

Interface Status ON Power input low (Battery) Power Modem Error OFF Not connected 10 or 100 Mbps (Ethernet) Activity 4/80 LED Color Solid Green Yellow Red (WiMAX card N/A or uncontrollable ) OFF (No Light) OFF (No Light) Solid Green Stay Solid Green

LAN

VoIP 1 & VoIP 2 *

When the phone ports defined, SIP account for Solid Green outgoing call is registered. when voice port is off hooked Flashing Green (Slowly) When the phone ports defined SIP account for Solid Yellow outgoing call is registered. And there is voice message in the corresponding SIP account. When voice port is off hooked, and there is Flashing Yellow voice message in the corresponding SIP account. No Registered SIP accounts to this line, or OFF device power off. Both VoIP1/2 LED Solid Yellow WiMAX card in MFG mode (You can type wimax debug to see what mode is now.) Signal Strength: Green on: Show each of signal 3 LED bar : 0~3 indicates RSSI (Power level strength level reception) R < -90dBm = Level 0 (No LEDs ON) -90 < = R < -80dBm = Level 1 (One LED ON) -80 < = R < -70dBm = Level 2 (Two LEDs ON) -70 < = R = Level 3 (Three LEDs ON) LINK: Indication of connection status at WiMAX air interface level (network entry) - Searching for a channel - WiMAX network Entry in progress OFF: WiMAX card not ready Green slow blink (one second) Green fast blink (0.5 second) Solid Green: connected

WAN

* There is only one physical phone jack (PHONE 1) on the MAX-216M1 CPE and (SIP1 and SIP2) can be associated to (PHONE 1) for Incoming and Outgoing calls.

2. Networking Features
This chapter describes the networking features.

5/80

2.1 NAT and Router Features

Features IP Routing NAT Description IP (RFC 791) routing is supported UDP, TCP, ICMP, ARP, RIP and IGMP Static routes can be programmed NAT (RFC1631) supported. Up to 2048 NAT sessions Multiple NAT support Many-to-One, Many-to-Many etc. Port forwarding user configurable Port Triggering user configurable Multimedia applications support: NetMeeting, CuSeeMe, ICQ, etc. ALG support: SIP, FTP, H.323 Ethernet and PPPoE encapsulation IPSec/PPTP/L2TP Pass Through DHCP Server on LAN DHCP Client on WAN Static DHCP table Auto configuration, User define or DNS Relay RIP1 and RIP2 support IGMP v1 and v2 IP Alias UPnP support Redirect the traffic to backup gateway Support Any IP. End users PC can be set to any IP address.

IP Management VPN Pass through DHCP DNS RIP IP Multicast IP Alias UPnP Traffic Redirect Any IP

2.2 Firewall Features

ICSA certified firewall with Stateful Packet Inspection Features Description DoS DoS attack detection and prevention: Ping to Death, SYN flood, LAND, Smurf, SMTP attack Stateful Packet Inspection IP Application Inspected: FTP, SMTP, HTTP, Telnet, SSL, DNS, etc Service Blocking User selectable blocking of common TCP/IP applications, like FTP, Telnet etc. User configurable TCP/UDP port (range) blocking Alert and logging Real time attack alert and logging Logging schedule control Content Filtering Restriction of ActiveX, Java, Cookies and Web Proxy URL keyword blocking Blocking schedule control Trusted computer (bypassing blocking) Packet Filtering IP & Generic Packet Filtering 6/80

2.3 Network Management

Features SNMP Firmware upgrade Telnet Remote Management Control Description SNMP v1 & v2c with MIB II Embedded FTP/TFTP Server for f/w upgrade and configuration backup and restore Telnet for remote management Telnet, FTP and Web interface can be enabled or disabled respectively

3. CPE Provisioning Mechanism

Content provisioning mechanism can be split into 4 categories that do have different impact on the deployment and operation of the end-user device.

3.1 Pre-Provisioning
Pre-provisioning is done at factory according to operator instructions. On fixed CPEs, all parameters are stored into the product HW. Provisioning consists then in loading during production process a configuration file defined with the operator. The usual way to build this configuration file is that the operator sets all parameters using Local Provisioning mechanisms (see below), and backup this configuration into a configuration file. Some specific parameters can also be applied during this phase. The usual way is to define, for each product, identified by its MAC address, the specific settings to be applied. The process of backup and restore configuration file All configurations in CPE are stored in a single file, called ROM file. You can use FTP to get this file, rom-0, from Simple CPE. This file can also be restored back to the CPE or duplicated to hundreds of Simple CPE and make their configuration all the same. ZyXEL can load specific ROM file during the factory process. ISP or operator can pre-configure the Simple CPE and retrieve the ROM file to ZyXEL. Comments: Process to be further confirmed & described. How do we manage the parameters that are not accessible to the end-user, but which are operator controlled only? How do we exactly manage the specific parameters, hiw are they agreed with the operator, is there a database with a specific format.

3.2 Local Provisioning

Local provisioning is performed by the operator, the distribution channel or the end-user, using only local physical resources. It does not request a WiMAX connection. Several possibilities are offered. GUI of the CPE, i.e. the PC application running on the PC for the web server embedded in the Fixed CPE accessed from a PC. This is documented in the User Manual. 7/80

The user or operator can use FTP, Telnet and Web GUI to access the CPE for configuration. The activities can be done are listed as below. Activities FTP configuration file backup/restore FTP software upgrade Telnet and CLI command Interface LAN LAN LAN Limitations Password protected Password protected Password protected Can use hidden commands to configure parameters which you dont want end-user to change. The details of CLI commands are described in user manual. The Web GUI is designed for end users. Most configurable parameters are user specific. The operator doesnt need to control this. The Web GUI is described in users manual. Need a TFTP server running on PC Need some configuration and procedures to upgrade the 802.16e MAC firmware. The details are described in chapter 6. Need Sequans software running on PC. Need some configuration and procedures to configure the 802.16e parameters. The details are described in chapter 6.

Web GUI

LAN

802.16e MAC firmware upgrade

LAN

802.16e MAC configuration

LAN

Comments: what about operator specific parameters that the user has no right to change Admin password? In general, how to configure data so that they are read only for the end user but can be changed by the operator Telnet: Is there a manual? It consists in setting parameters using some telnet commands to be entered from a console. Local and/or remote use of telnet can be restricted by configuration. Command Line Interface (CLI): Is there a manual? Local and/or remote use of CLI can be restricted by configuration.

3.3 Remote Provisioning

Remote provisioning consists in having the provisioning managed from the network. This requires WiMAX connection to be active, and the end-user device to be addressable by the network. Several standard mechanisms are support by ZyXEL end-user device.

3.3.1 Web Interface

The Web GUI interface is normally used by end users to configure the networking features like NAT, firewall and DHCP. For WiMAX related setting, end user can configure the user name and password of EAP-TTLS through Web GUI. This can be customized by request.

3.3.2 Telnet Interface

The end-user device can be provisioned by Telnet from the network, as soon as the IP address of the end-user device is known, and the feature has been enabled on the device. 8/80

Note that activation of remote Telnet creates a security hole, as incoming UDP port 23 remains always open. Remote Telnet can be de-activated.

3.3.3 SNMP
The end-user device can be controlled by SNMP from the network, as soon as the IP address of the end-user device is known, and the feature has been enabled on the device. ZyXEL Fixed CPE support SNMPv1 and SNMPv2c with MIB II. WiMAX MIB (16d/16e) is not supported in current ZyXEL end-user device release. Note that in current WiMAX MIB definition, the most useful parameters on end-user device side are not settable through SNMP. Note that activation of SNMP creates a security hole, as incoming UDP port 61 remains always open. SNMP can be de-activated.

3.3.4 TR-069
ZyXEL Fixed CPE supports TR-069 protocol for CPE management. This feature is not available on PCMCIA. TR-069 allows Dynamic Services Provisioning, configuration file download / upload, firmware version identification, firmware download initiation and notification. The firmware upload itself is done through TFTP or HTTP(s). TR-069 relies on an Auto Configuration Server (ACS) implementation in the network. In the simplest case, ACS server address can simply be pre-configured in the CPE, together with ACS user credentials. The CPE is master, and establish first the contact with the TR-069 server. TR-069 is based on TCP/IP. ZyXEL supports SSL3.0 and TLS1.0 for confidentiality, data integrity, and certificate based authentication. End-user device certifies ACS by RSA certification whereas ACS certifies CPE by its username and password. The architecture is as following diagram. ZyXEL WiMAX CPE supports TR-069 protocol for CPE management. The architecture is as following diagram.

Service Configuration Manager

Scope of ACS Northbound CPE WAN Management Protocol: Interface ACS Southbound Interface

ACS
BRAS

Regional Broadband Network DSLAM

LAN

Managed CPE (B-NT) Managed CPE (LAN Device)

ACS = Auto Configuration Server ZyXEL TR-069 feature is under IOP testing with Alcatel HDM5580. Other IOP test report will be available soon. Current support TR-069 features are as below. Features Description Auto Configuration Configuration file download / upload Dynamic Services Provisioning ACS Discovery Manual setting of ACS URL 9/80

Firmware Management SSL3.0 / TLS1.0

Version identification File download initiation and notification Confidentiality, Data Integrity and Certificate based authentication

Protocol Layer Summary

CPE/ACS Management Application RPC Methods SOAP HTTP SSL/TLS TCP/IP

Following is brief description of each layer Layer RPC Methods Description The specific RPC methods that are defined by the CPE WAN Management Protocol. This includes the definition of the CPE Parameters accessible by an ACS via the Parameter-related RPC Methods. A standard XML-based syntax used here to encode remote procedure calls. HTTP 1.1 The standard Internet transport layer security protocols. Specifically, either SSL 3.0 (Secure Socket Layer), or TLS 1.0 (Transport Layer Security). Use of SSL/TLS is RECOMMENDED. Standard TCP/IP.

SOAP HTTP SSL/TLS

TCP/IP

Mutual Authentications CPE certifies ACS by RSA certification ACS certifies CPE by username and password

10/80

4. User Authentication
4.1 EAP-TTLS
The User can set the TTLS mode for Authentication.

11/80

4.2 EAP-TLS
The User can set the TLS mode for Authentication.

12/80

5. VoIP Features
This feature is only for Simple CPE and Multi-user CPE. Features SIP Protocol Standards Description SIP (RFC 3261) version 2 SDP (RFC 2327) RTP (RFC 1889) RTCP (RFC 1890) Echo Cancellation: G.168 VAD (Voice activity detection) Silence suppression CNG (Comfort noise generation) G.711 (PCM A-law or -law selectable), G.729a/b, G.723 SIP (RFC 3261) version 2 SDP (RFC 2327) RTP (RFC 1889) RTCP (RFC 1890) Echo Cancellation: G.168 VAD (Voice activity detection) Silence suppression CNG (Comfort noise generation) QoS Supports TOS or Diffserv Compression: G.711 (PCM A-law or -law selectable), G.729a/b, G.723 Loop Start and Ground Start Signaling Support DTMF Detection

Echo Cancellation Phone Features Codec VoIP Features

13/80

6. Maintenance Guide
There are two kinds of software inside Simple CPE: 1. Software for Simple CPE itself, with Router, firewall, VoIP and Web GUI etc. During the early stage of WiMAX, there are many chances to upgrade the 802.16e MAC software and/or change the configuration. These are performed locally through Ethernet connection and some special tools running on PC are required. Section 6.1 will describe how to setup the Simple CPE, MAX-206M2/MAX216M1 and how to connect them. Section 6.2 will describe the procedures of configuration/provisioning. Section 6.3 will describe the procedures of software download of the built-in WiMAX MAC/BB/RF card (called WiMAX card in this document). For the remote software upgrade and configuration, they are described in other sections. Following table shows the difference of the WiMAX card built-in in ZyXEL MIMO CPE. Card Type Description WiMAX card 1. WiMAX MAC, Baseband and RF 2. Built-in in Simple CPE, MAX-206M2/MAX216M1 3. Maximum Tx Power 27 dBm

6.1 Connection and Setup

Since WiMAX Card is connected with the WAN port of ZyXEL MIMO CPE itself is not a PC, some settings are required to re-connect to the PC. This setup procedure is as below. Connect your notebook or desktop PC to the ZyXEL MIMO CPE by Ethernet (LAN). Follow the procedures to configure the ZyXEL MIMO CPE:

6.1.1 Start the Connection Manager

ZyXEL MIMO CPE supports DHCP server function on LAN port. Thus, you just need to plug the Ethernet cable to connect ZyXEL MIMO CPE and PC, and then PC will get the IP address from ZyXEL MIMO CPE automatically. You can run a Window command terminal and perform the command ipconfig to check the IP address got from ZyXEL MIMO CPE. The default gateway IP address is the address for ZyXEL MIMO CPE.

14/80

Step.1

Launch your web browser and connect to URL http://192.168.1.1. For first time, you can use the default User name (admin) and Password (1234) to login.

The following page displays if you have not yet changed your password. Clink Clear to keep using default one; alternatively enter a new password and click Apply to change it.

15/80

Click Apply in the next screen to create a certificate using MAX-2X6s MAC address that will be specific to this device. This certificate is used for authentication when using a secure HTTPS connection over the Internet.

16/80

6.1.2
Step.2

Start Network Entry Import Certificate for both device own and server side. Click TOOLS > Certificates > My Certificates in the navigation panel for import device own certificate.

Click TOOLS > Certificates > Trusted CAs in the navigation panel for import server side certificate.

17/80

Step.3

Configure the Username, Password, and authentication method by click ADVANCED > WAN Configuration > Internet Connection in navigation panel.

Step.4

Configure the frequency and channel bandwidth by click ADVANCED > WAN Configuration > WiMAX Frequency in navigation panel. Current setting is

Step.5

After configure ZyXEL MIMO CPE ready, please request AAA server
18/80

engineer to add the device MAC address into the list.

6.2 Check Device Status

Check Device Status sys atsh

ZyNOS Firmware Version

Device MAC Address

There are two MAC address on MAX-2X6; one is for LAN interface (on system board), the other is for WAN (on WiMAX card) Here the address shows on sys atsh page is the LAN interface MAC. LAN MAC + 1 is the WAN MAC address. Take an instance, this devices LAN MAC is 00:19:CB:46:10:FB; WAN MAC is 00:19:CB:46:10:FC.

19/80

Check WiMAX Card Status wimax iot wcstatus

WiMAX Card Status

WiMAX Card Firmware Version

Check IP Status ip ifconfig

enif0 is the LAN interface

enif1 is the WAN (WiMAX) interface

20/80

Show device Status wimax cli show [parameter]

21/80

6.3

Useful System CLI command

Set MAC address sys atwz [MAC address]

Release and renew DHCP IP address ip dhcp enif1 client release ip dhcp enif1 client renew

Enable/Disable the Menu Configuration sys smt on/sys smt off

After perform the command, you need to exit and re-login again. And then you will get the menu configuration page. Exit menu configuration page by select 24 -> 8 -> type sys smt off, then exit and re-login.

22/80

IPref test You need to set the NAT Setup by using Menu configuration. Use Menu 15 and Port Forwarding Setup to configure. Ipref command for example: Server: ipref u s t 9999 Client: ipref u c 10.10.10.1 l 1370 b 10m t 9999

Sometimes different H/W version will cause the LED behavior abnormal. When encounter this problem, you can perform this command to sync the boot code. sys atmb 1

23/80

6.4 Useful WiMAX CLI command

Enable/Disable WiMAX Card wimax start/wimax stop

Hardware reset WiMAX Card wimax iot resetwc Without reboot the system board, we can use this to reboot the WiMAX CARD.

Capture the Air packet wimax iot setaircopy2LAN [turn on/off] After use this command, you can use the ethereal tools to capture the packets which sent to WiMAX interface.

Show all wimax iot commands wimax iot

24/80

Query current Frequency setting wimax net setFre 0

Configure Frequency setting wimax net setFre [0/1: show/clean and set] [DL frequency value] [bandwidth value]

Add Frequency setting wimax net setFre 2 2677000

25/80

Get current scan Frequency setting in the WiMAX Card wimax cli showscanner

6.5 Useful WiMAX Debug command

Enable/Disable the debug log wimax log [type] [turn on/off] [target]

Enable/Disable EAP debug log wimax eap debug <log (0:off, 1:on)> <level (0-4)>

Currently, the only way to disable the log is wimax eap debug 0 4.
[SOP for testing EAP module]: 1. wimax stop 2. wimax log 0 1 3. wimax eap debug 0 1 4. wimax iot setaircopy2LAN on 5. wimax cli enablelog PKMS 6. execute Wireshark on host system 7. wimax start 8. Collect logs from console and sniff packet using Wireshark. 26/80

6.6 Useful VoIP Debug command

[Caller ID]: CPE supports caller ID payload format in MDMF, SDMF and DTMF. You can perform "voice config fxs display 1" to check the current setting. Or perform voice config fxs cidpayload to configure the format you want to adopt. Here is an example to show you how to change the format to MDMF.

"voice config fxs index 1" "voice config fxs cidpayload 1 0" "voice config fxs save 1"
[DNS SRV]:

You can use "voice config signal display 1" to see the setting of the DNS SRV (default is redundancy). If you want change it, use "voice config signal index 1" "voice config signal srvServerType 1 <0 or 1>" "voice config signal save 1"

6.7 Useful TR069 Debug command

>#############################> TR-069 DEBUG COMMAND <#################< TR069 Related Command Command Description Ether TR069 0/1 Usage: [0:no/1:yes] active Enable the function of Tr069 The operation of load needs to be done before load you set any parameters. clear Clear any settings you have set. e.g. Current Auto-Configuration Server URL = Current http://81.246.42.74:7003/cwmpWeb/NACPEMgt acsUrl Auto-Configuration Server URL save Save the settings you have set. display Display the current settings of Tr069 0/1 Usage: [0:Disable/1:Enable] periodicEnable Enable the function of periodic interval. PeriodicInformInterval Usage: PeriodicInformInterval xxx [sec] informInterval Set the time of periodic inform interval 27/80

yyyy-mm-ddThh:mm:ss Usage: An absolute PeriodicInformTime [yyyy-mm-ddThh:mm:ss] reset Trigger the inform to be sent getRPC Get the RPC methods of the ACS server [off:Disable/on:Enable] Usage: [off:Disable/on:Enable] [number: Level] debug Enable the function of debug mode [number: Level] [maxlength:15] Usage: username:xxx [maxlength:15] username The username and password used for connecting to the ACS. [maxlength:15] Usage: password:xxx [maxlength:15] password The username and password used for connecting to the ACS. [maxlength:15] Usage: username:xxx [maxlength:15] Username of the connection request requsername (The username and password used for authenticating ACS during a connection request.) [maxlength:15] Usage: username:xxx [maxlength:15] Password of the connection request reqpassword (The username and password used for authenticating ACS during a connection request.) Show the notification list saved in the flash (max. notification 64) informTime

For example ======================= Copyright (c) 1994 - 2008 ZyXEL Communications Corp. MAX-216M1> et tr di TR069 Active: No Auto-Configuration Server URL: PeriodicInformEnable: Disable PeriodicInformInterval: 0 PeriodicInformTime: 0000-00-00T00:00:00 Username: Password: ConnectionRequestUsername: ConnectionRequestPassword: TR069 Debug: Disable MAX-216M1> ether tr load MAX-216M1> ether tr active 1 MAX-216M1> ether tr acsUrl http://172.23.40.16/TR069 Auto-Configuration Server URL: http://172.23.40.16/TR069
28/80

MAX-216M1> ether tr periodicEnable 1 MAX-216M1> ether tr informInterval 30 TR069 Informinterval 30 MAX-216M1> ether tr informTime 2008-09-08T12:00:00 New InformTime: 2008-09-08T12:00:00 MAX-216M1> ether tr username wimax Username: wimax MAX-216M1> ether tr password wimax Password: wimax MAX-216M1> ether tr requsername wimax ConnectionRequestUserName: wimax MAX-216M1> ether tr reqpassword wimax ConnectionRequestPassword: wimax MAX-216M1> ether tr save MAX-216M1> et tr di TR069 Active: Yes Auto-Configuration URL: http://172.23.40.16/TR069 PeriodicInformEnable: Enabled PeriodicInformInterval: 30 PeriodicInformTime: 2008-09-08T12:00:00 Username: wimax Password: wimax ConnectionRequestUsername: wimax ConnectionRequestPassword: wimax TR069 Debug: Disable Server

29/80

6.8 Useful VPNT Command

6.8.1 Use of Untagged Customer Interface in Bridge Mode

In this test case, we bridge the untagged customer interface of ZyXEL MIMO CPE (A) with the untagged customer interface of ZyXEL MIMO CPE (B) by setting up an Ethernet pseudowire between the WAN ports of both MAX-206M2/MAX216M1s. The combination of the two MAX-206M2/MAX216M1s is equivalent to a two-port bridge.

The use of untagged customer interface in bridge mode

Please follow the steps below to carry out this test. Prepare the network elements as depicted above. Make sure that the WAN links of both MAX-206M2/MAX216M1 A and MAX-206M2/MAX216M1 B are up and that each of the WAN interfaces acquires an IP address. Check the WAN status of a ZyXEL MIMO CPE. Log on to the ZyXEL MIMO CPE and go to Web > Status > Device Information . Turn off the firewall on each ZyXEL MIMO CPE before performing ping check to see if ZyXEL MIMO CPE A and ZyXEL MIMO CPE B can reach each other. By default the firewall blocks incoming ICMP packets. To turn off the
30/80

firewall, go to Web > Security > Firewall > General. Go to ZyXEL MIMO CPE As Command Interpreter, and execute the following CLI command to ping ZyXEL MIMO CPE Bs WAN IP address. MAX-216M1> ip ping < ZyXEL MIMO CPE Bs WAN IP address> If ZyXEL MIMO CPE A can reach ZyXEL MIMO CPE B, the console will display information such as follows; otherwise it means ZyXEL MIMO CPE B is unreachable. sent 1 2 3 rcvd rate 1 100 2 100 3 100 rtt 50 70 30 avg 50 53 50 mdev 0 5 10 max 50 70 70 min 50 50 30

Perform the same check on ZyXEL MIMO CPE B. If the results show that ZyXEL MIMO CPE A and ZyXEL MIMO CPE B can reach each other, continue to Step 6.1.5; otherwise go back to Step 6.1.2. You may turn on the Firewall now. To turn on the firewall, go to Web>Security>Firewall>General . Go to ZyXEL MIMO CPE As Command Interpreter and execute the following CLI command to set up the L2/L3 VPN Transport feature configuration necessary. MAX-216M1> vpnt load MAX-216M1> vpnt active on MAX-216M1> vpnt gre <MAX-206M2/MAX216M1 Bs IP address> MAX-216M1> vpnt pw config 0 on 100 5100 "Pseudowire X" MAX-216M1> vpnt cif config 0 on -1 B 0 000000 "Customer X" MAX-216M1> vpnt save To view and double-check the latest configuration, execute the following CLI commands. MAX-216M1> vpnt load MAX-216M1> vpnt gre MAX-216M1> vpnt pw list MAX-216M1> vpnt cif list Go to ZyXEL MIMO CPE Bs Command Interpreter and execute the following CLI command to set up the L2/L3 VPN Transport feature configuration necessary. MAX-216M1> vpnt load
31/80

MAX-216M1> vpnt active on MAX-216M1> vpnt gre <MAX-206M2/MAX216M1 As IP address> MAX-216M1> vpnt pw config 0 on 5100 100 "Pseudowire X" MAX-216M1> vpnt cif config 0 on -1 B 0 000000 "Customer X" MAX-216M1> vpnt save To view and double-check the latest configuration, execute the following CLI commands. MAX-216M1> vpnt load MAX-216M1> vpnt gre MAX-216M1> vpnt pw list MAX-216M1> vpnt cif list Check if the PC behind ZyXEL MIMO CPE A can acquire an IP address from the DHCP server behind ZyXEL MIMO CPE B. After the PC has acquired an IP address, check if the PC can access the Internet without any problem. Check out the traffic counters of each ZyXEL MIMO CPE by executing the following CLI commands. MAX-216M1> vpnt pw cnt display all MAX-216M1> vpnt cif cnt display all

6.8.2 Use of Untagged & Tagged Customer Interface in Bridge Mode

In this test case, we bridge each of the sixteen customer interfaces of ZyXEL MIMO CPE A with one of the customer interfaces of ZyXEL MIMO CPE by setting up an Ethernet pseudowire between the WAN ports of both ZyXEL MIMO CPEs. The combination of the two ZyXEL MIMO CPEs and the two VLAN switches is equivalent to sixteen two-port bridges.

32/80

The use of tagged and untagged customer interfaces in bridge mode

Please follow the steps below to carry out this test. Prepare the network elements as depicted above. Make sure that the WAN links of both ZyXEL MIMO CPE A and ZyXEL MIMO CPE B are up and that each of the WAN interfaces acquires an IP address. To check the WAN status of a ZyXEL MIMO CPE, log on to the ZyXEL MIMO CPE and go to Web>Status>Device Information. Turn off the firewall on each ZyXEL MIMO CPE before performing ping check to see if ZyXEL MIMO CPE A and ZyXEL MIMO CPE B can reach each other. By default the firewall blocks incoming ICMP packets. To turn off the firewall, go to Web>Security>Firewall>General. Go to ZyXEL MIMO CPE As Command Interpreter and execute the following CLI command to ping ZyXEL MIMO CPE Bs WAN IP address. MAX-216M1> ip ping < ZyXEL MIMO CPE Bs WAN IP address> If ZyXEL MIMO CPE A can reach ZyXEL MIMO CPE B, the console will display information such as follows; otherwise it means ZyXEL MIMO CPE B is unreachable. sent 1 2 rcvd rate 1 100 2 100 rtt 50 70
33/80

avg 50 53

mdev 0 5

max 50 70

min 50 50

3 100

30

50

10

70

30

Perform the same check from ZyXEL MIMO CPE B. If the results show that ZyXEL MIMO CPE A and ZyXEL MIMO CPE B can reach each other, continue to Step 6.2.5; otherwise go back to Step 6.2.2. You may turn on the Firewall now. To turn on the firewall, go to Web>Security>Firewall>General . Go to ZyXEL MIMO CPE As Command Interpreter Mode and execute the following CLI command to set up the L2/L3 VPNT feature configuration necessary. MAX-216M1> vpnt load MAX-216M1> vpnt active on MAX-216M1> vpnt gre <MAX-206M2/MAX216M1 Bs IP address> MAX-216M1> vpnt pw config 0 on 100 5100 "Pseudowirw 0" MAX-216M1> vpnt pw config 1 on 101 5101 "Pseudowirw 1" MAX-216M1> vpnt pw config 2 on 102 5102 "Pseudowirw 2" MAX-216M1> vpnt pw config 3 on 103 5103 "Pseudowirw 3" MAX-216M1> vpnt pw config 4 on 104 5104 "Pseudowirw 4" MAX-216M1> vpnt pw config 5 on 105 5105 "Pseudowirw 5" MAX-216M1> vpnt pw config 6 on 106 5106 "Pseudowirw 6" MAX-216M1> vpnt pw config 7 on 107 5107 "Pseudowirw 7" MAX-216M1> vpnt pw config 8 on 108 5108 "Pseudowirw 8" MAX-216M1> vpnt pw config 9 on 109 5109 "Pseudowirw 9" MAX-216M1> vpnt pw config 10 on 110 5110 "Pseudowirw 10" MAX-216M1> vpnt pw config 11 on 111 5111 "Pseudowirw 11" MAX-216M1> vpnt pw config 12 on 112 5112 "Pseudowirw 12" MAX-216M1> vpnt pw config 13 on 113 5113 "Pseudowirw 13" MAX-216M1> vpnt pw config 14 on 114 5114 "Pseudowirw 14" MAX-216M1> vpnt pw config 15 on 115 5115 "Pseudowirw 15" MAX-216M1> vpnt cif config 0 on -1 B 0 000000 "Customer 0" MAX-216M1vpnt cif config 1 on 2391 B 1 000000 "Customer 1" MAX-216M1> vpnt cif config 2 on 2392 B 2 001000 "Customer 2" MAX-216M1> vpnt cif config 3 on 2393 B 3 001010 "Customer 3" MAX-216M1> vpnt cif config 4 on 2394 B 4 001100 "Customer 4" MAX-216M1> vpnt cif config 5 on 2395 B 5 001110 "Customer 5" MAX-216M1> vpnt cif config 6 on 2396 B 6 010000 "Customer 6"
34/80

MAX-216M1> vpnt cif config 7 on 2397 B 7 010010 "Customer 7" MAX-216M1> vpnt cif config 8 on 2398 B 8 010100 "Customer 8" MAX-216M1> vpnt cif config 9 on 2399 B 9 010110 "Customer 9" MAX-216M1> vpnt cif config 10 on 2400 B 10 011000 "Customer 10" MAX-216M1> vpnt cif config 11 on 2401 B 11 011010 "Customer 11" MAX-216M1> vpnt cif config 12 on 2402 B 12 011110 "Customer 12" MAX-216M1> vpnt cif config 13 on 2403 B 13 100000 "Customer 13" MAX-216M1> vpnt cif config 14 on 2404 B 14 100010 "Customer 14" MAX-216M1> vpnt cif config 15 on 2405 B 15 100100 "Customer 15" MAX-216M1> vpnt save To view and double-check the latest configuration, execute the following CLI commands. MAX-216M1> vpnt load MAX-216M1> vpnt gre MAX-216M1> vpnt pw list MAX-216M1> vpnt cif list Go to ZyXEL MIMO CPE Bs Command Interpreter and execute the following CLI command to set up the L2/L3 VPNT feature configuration. MAX-216M1> vpnt load MAX-216M1> vpnt active on MAX-216M1> vpnt gre <ZyXEL MIMO CPE A's IP address> MAX-216M1> vpnt pw config 0 on 5100 100 "Pseudowirw 0" MAX-216M1> vpnt pw config 1 on 5101 101 "Pseudowirw 1" MAX-216M1> vpnt pw config 2 on 5102 102 "Pseudowirw 2" MAX-216M1> vpnt pw config 3 on 5103 103 "Pseudowirw 3" MAX-216M1> vpnt pw config 4 on 5104 104 "Pseudowirw 4" MAX-216M1> vpnt pw config 5 on 5105 105 "Pseudowirw 5" MAX-216M1> vpnt pw config 6 on 5106 106 "Pseudowirw 6" MAX-216M1> vpnt pw config 7 on 5107 107 "Pseudowirw 7" MAX-216M1> vpnt pw config 8 on 5108 108 "Pseudowirw 8" MAX-216M1> vpnt pw config 9 on 5109 109 "Pseudowirw 9" MAX-216M1> vpnt pw config 10 on 5110 110 "Pseudowirw 10" MAX-216M1> vpnt pw config 11 on 5111 111 "Pseudowirw 11" MAX-216M1> vpnt pw config 12 on 5112 112 "Pseudowirw 12" MAX-216M1> vpnt pw config 13 on 5113 113 "Pseudowirw 13"
35/80

MAX-216M1> vpnt pw config 14 on 5114 114 "Pseudowirw 14" MAX-216M1> vpnt pw config 15 on 5115 115 "Pseudowirw 15" MAX-216M1> vpnt cif config 0 on -1 B 0 000000 "Customer 0" MAX-216M1> vpnt cif config 1 on 2391 B 1 000000 "Customer 1" MAX-216M1> vpnt cif config 2 on 2392 B 2 001000 "Customer 2" MAX-216M1> vpnt cif config 3 on 2393 B 3 001010 "Customer 3" MAX-216M1> vpnt cif config 4 on 2394 B 4 001100 "Customer 4" MAX-216M1> vpnt cif config 5 on 2395 B 5 001110 "Customer 5" MAX-216M1> vpnt cif config 6 on 2396 B 6 010000 "Customer 6" MAX-216M1> vpnt cif config 7 on 2397 B 7 010010 "Customer 7" MAX-216M1> vpnt cif config 8 on 2398 B 8 010100 "Customer 8" MAX-216M1> vpnt cif config 9 on 2399 B 9 010110 "Customer 9" MAX-216M1> vpnt cif config 10 on 2400 B 10 011000 "Customer 10" MAX-216M1> vpnt cif config 11 on 2401 B 11 011010 "Customer 11" MAX-216M1> vpnt cif config 12 on 2402 B 12 011110 "Customer 12" MAX-216M1> vpnt cif config 13 on 2403 B 13 100000 "Customer 13" MAX-216M1> vpnt cif config 14 on 2404 B 14 100010 "Customer 14" MAX-216M1> vpnt cif config 15 on 2405 B 15 100100 "Customer 15" MAX-216M1> vpnt save To view and double-check the latest configuration, execute the following CLI commands. MAX-216M1> vpnt load MAX-216M1> vpnt gre MAX-216M1> vpnt pw list MAX-216M1> vpnt cif list Properly configure sixteen virtual LANs (including one untagged LAN) on each VLAN switch, and aggregate the traffic to a port connected to each ZyXEL MIMO CPEs LAN port. Check if the PC in each VLAN behind ZyXEL MIMO CPE A can acquire an IP address from the DHCP server in the corresponding VLAN behind ZyXEL MIMO CPE B. When the PC in each VLAN behind ZyXEL MIMO CPE A are acquiring an IP address from the DHCP server, the DSCP of each VLAN can be checked by monitoring the packets over the air. After the PC in each VLAN has acquired an IP address, check if the PC can
36/80

access the Internet without any problem. Check out the traffic counters of each ZyXEL MIMO CPE by executing the following CLI commands. MAX-216M1> vpnt pw cnt display all MAX-216M1> vpnt cif cnt display all

6.8.3 Use of Untagged Customer Interface in Routing/NAT Mode

In this test case, we configure one of ZyXEL MIMO CPEs customer interfaces for Routing/NAT. The PC behind this customer interface can acquire an IP address from the ZyXEL MIMO CPEs DHCP server and then access the Internet.

The use of untagged customer interface in routing/NAT mode

Please follow the steps below to carry out this test. Prepare the network elements as depicted above. Make sure that the WAN link of ZyXEL MIMO CPE is up and its WAN interface has acquired an IP address. To check the WAN status of ZyXEL MIMO CPE, log on to ZyXEL MIMO CPE and go to Web>Status>Device Information . Go to ZyXEL MIMO CPEs Command Interpreter and execute the following CLI command to check its connectivity to the Internet. MAX-216M1> ip ping www.google.com If ZyXEL MIMO CPE can reach www.google.com, the console will display information such as follows; otherwise it means ZyXEL MIMO CPE has no
37/80

Internet connectivity. sent 1 2 3 rcvd rate 1 100 2 100 3 100 rtt 70 70 70 avg 70 70 70 mdev 0 0 0 max 70 70 70 min 70 70 70

If ZyXEL MIMO CPE has Internet connectivity, continue to Step 6.3.4; otherwise go back to Step 6.3.2. Go to ZyXEL MIMO CPEs Command Interpreter and execute the following CLI command to set up an untagged customer interface for Routing/NAT. MAX-216M1> vpnt load MAX-216M1> vpnt active on MAX-216M1> vpnt cif config 0 on -1 R "" "" "Customer X" MAX-216M1> vpnt save To view and double-check the latest configuration, execute the following CLI commands. MAX-216M1> vpnt load MAX-216M1> vpnt cif list Go to ZyXEL MIMO CPEs Web>Network>LAN>DHCP Setup and properly configure ZyXEL MIMO CPEs DHCP server. Connect a PC to the LAN port of ZyXEL MIMO CPE. Check if the PC can acquire an IP address from ZyXEL MIMO CPEs DHCP server. After the PC has acquired an IP address, check if the PC can access the Internet without any problem. Check out the traffic counters of ZyXEL MIMO CPE by executing the following CLI commands. MAX-216M1> vpnt cif cnt display all

6.8.4 GRE Tunnel via LAN Port to Bypass Radio Link Uncertainty

This test case is similar to Case 2, except that the GRE tunnel is established between the LAN ports of both ZyXEL MIMO CPEs, in order to bypass the uncertainty of radio link. Before a GRE tunnel can be established between the LAN ports of both ZyXEL MIMO CPE s, a customer interface on each ZyXEL MIMO CPE must first be configured for routing.

38/80

The establishment of a GRE tunnel between the LAN ports of two MAX-206M2/MAX216M1s

Please follow the steps below to carry out this test. Prepare the network elements as depicted above. Go to ZyXEL MIMO CPE As Web>Network>LAN>IP to configure its LAN interface IP address as 192.168.1.10. Go to ZyXEL MIMO CPE Bs Web>Network>LAN>IP to configure its LAN interface IP address as 192.168.1.11. Now ZyXEL MIMO CPE As LAN interface is on the same subnet as ZyXEL MIMO CPE Bs LAN interface. Go to ZyXEL MIMO CPE As Command Interpreter and execute the following CLI command to set up one untagged customer interface for routing/NAT. MAX-216M1> vpnt load MAX-216M1> vpnt active on MAX-216M1> vpnt cif config 0 on -1 R "" "" "for routing/NAT" MAX-216M1> vpnt save Go to ZyXEL MIMO CPE Bs Command Interpreter and execute the following CLI command to also set up one untagged customer interface for routing/NAT. MAX-216M1> vpnt load
39/80

MAX-216M1> vpnt active on MAX-216M1> vpnt cif config 0 on -1 R "" "" "for routing/NAT" MAX-216M1> vpnt save Properly configure one untagged virtual LAN on each VLAN switch, and forward the traffic to a port connected to each ZyXEL MIMO CPEs LAN port. Go to ZyXEL MIMO CPE As Command Interpreter and execute the following CLI command to ping ZyXEL MIMO CPE Bs LAN IP address. MAX-216M1> ip ping 192.168.1.11 If ZyXEL MIMO CPE A can reach ZyXEL MIMO CPE B, the console will display information such as follows; otherwise it means ZyXEL MIMO CPE B is unreachable. sent 1 2 3 rcvd rate 1 100 2 100 3 100 rtt 50 70 30 avg 50 53 50 mdev 0 5 10 max 50 70 70 min 50 50 30

Perform the same check from ZyXEL MIMO CPE B. If the results show that ZyXEL MIMO CPE A and ZyXEL MIMO CPE B can reach each. Go to ZyXEL MIMO CPE As Command Interpreter and execute the following CLI command to set up the L2/L3 VPNT feature configuration necessary. MAX-216M1> vpnt load MAX-216M1> vpnt active on MAX-216M1> vpnt gre 192.168.1.11 MAX-216M1> vpnt pw config 1 on 101 5101 "Pseudowirw 1" MAX-216M1> vpnt pw config 2 on 102 5102 "Pseudowirw 2" MAX-216M1> vpnt pw config 3 on 103 5103 "Pseudowirw 3" MAX-216M1> vpnt pw config 4 on 104 5104 "Pseudowirw 4" MAX-216M1> vpnt pw config 5 on 105 5105 "Pseudowirw 5" MAX-216M1> vpnt pw config 6 on 106 5106 "Pseudowirw 6" MAX-216M1> vpnt pw config 7 on 107 5107 "Pseudowirw 7" MAX-216M1> vpnt pw config 8 on 108 5108 "Pseudowirw 8" MAX-216M1> vpnt pw config 9 on 109 5109 "Pseudowirw 9" MAX-216M1> vpnt pw config 10 on 110 5110 "Pseudowirw 10" MAX-216M1> vpnt pw config 11 on 111 5111 "Pseudowirw 11"
40/80

MAX-216M1> vpnt pw config 12 on 112 5112 "Pseudowirw 12" MAX-216M1> vpnt pw config 13 on 113 5113 "Pseudowirw 13" MAX-216M1> vpnt pw config 14 on 114 5114 "Pseudowirw 14" MAX-216M1> vpnt pw config 15 on 115 5115 "Pseudowirw 15" MAX-216M1> vpnt cif config 1 on 2391 B 1 000000 "Customer 1" MAX-216M1> vpnt cif config 2 on 2392 B 2 001000 "Customer 2" MAX-216M1> vpnt cif config 3 on 2393 B 3 001010 "Customer 3" MAX-216M1> vpnt cif config 4 on 2394 B 4 001100 "Customer 4" MAX-216M1> vpnt cif config 5 on 2395 B 5 001110 "Customer 5" MAX-216M1> vpnt cif config 6 on 2396 B 6 010000 "Customer 6" MAX-216M1> vpnt cif config 7 on 2397 B 7 010010 "Customer 7" MAX-216M1> vpnt cif config 8 on 2398 B 8 010100 "Customer 8" MAX-216M1> vpnt cif config 9 on 2399 B 9 010110 "Customer 9" MAX-216M1> vpnt cif config 10 on 2400 B 10 011000 "Customer 10" MAX-216M1> vpnt cif config 11 on 2401 B 11 011010 "Customer 11" MAX-216M1> vpnt cif config 12 on 2402 B 12 011110 "Customer 12" MAX-216M1> vpnt cif config 13 on 2403 B 13 100000 "Customer 13" MAX-216M1> vpnt cif config 14 on 2404 B 14 100010 "Customer 14" MAX-216M1> vpnt cif config 15 on 2405 B 15 100100 "Customer 15" MAX-216M1> vpnt save To view and double-check the latest configuration, execute the following CLI commands. MAX-216M1> vpnt load MAX-216M1> vpnt gre MAX-216M1> vpnt pw list MAX-216M1> vpnt cif list Go to MAX-206M2/MAX216M1 Bs Command Interpreter and execute the following CLI command to set up the L2/L3 VPNT feature configuration. MAX216M1> vpnt load MAX216M1> vpnt active on MAX216M1> vpnt gre 192.168.1.10 MAX216M1> vpnt pw config 1 on 5101 101 "Pseudowirw 1" MAX216M1> vpnt pw config 2 on 5102 102 "Pseudowirw 2" MAX216M1> vpnt pw config 3 on 5103 103 "Pseudowirw 3" MAX216M1> vpnt pw config 4 on 5104 104 "Pseudowirw 4"
41/80

MAX216M1> vpnt pw config 5 on 5105 105 "Pseudowirw 5" MAX216M1> vpnt pw config 6 on 5106 106 "Pseudowirw 6" MAX216M1> vpnt pw config 7 on 5107 107 "Pseudowirw 7" MAX216M1> vpnt pw config 8 on 5108 108 "Pseudowirw 8" MAX216M1> vpnt pw config 9 on 5109 109 "Pseudowirw 9" MAX216M1> vpnt pw config 10 on 5110 110 "Pseudowirw 10" MAX216M1> vpnt pw config 11 on 5111 111 "Pseudowirw 11" MAX216M1> vpnt pw config 12 on 5112 112 "Pseudowirw 12" MAX216M1> vpnt pw config 13 on 5113 113 "Pseudowirw 13" MAX216M1> vpnt pw config 14 on 5114 114 "Pseudowirw 14" MAX216M1> vpnt pw config 15 on 5115 115 "Pseudowirw 15" MAX216M1> vpnt cif config 1 on 2391 B 1 000000 "Customer 1" MAX216M1> vpnt cif config 2 on 2392 B 2 001000 "Customer 2" MAX216M1> vpnt cif config 3 on 2393 B 3 001010 "Customer 3" MAX216M1> vpnt cif config 4 on 2394 B 4 001100 "Customer 4" MAX216M1> vpnt cif config 5 on 2395 B 5 001110 "Customer 5" MAX216M1> vpnt cif config 6 on 2396 B 6 010000 "Customer 6" MAX216M1> vpnt cif config 7 on 2397 B 7 010010 "Customer 7" MAX216M1> vpnt cif config 8 on 2398 B 8 010100 "Customer 8" MAX216M1> vpnt cif config 9 on 2399 B 9 010110 "Customer 9" MAX216M1> vpnt cif config 10 on 2400 B 10 011000 "Customer 10" MAX216M1> vpnt cif config 11 on 2401 B 11 011010 "Customer 11" MAX216M1> vpnt cif config 12 on 2402 B 12 011110 "Customer 12" MAX216M1> vpnt cif config 13 on 2403 B 13 100000 "Customer 13" MAX216M1> vpnt cif config 14 on 2404 B 14 100010 "Customer 14" MAX216M1> vpnt cif config 15 on 2405 B 15 100100 "Customer 15" MAX216M1> vpnt save To view and double-check the latest configuration, execute the following CLI commands. MAX216M1> vpnt load MAX216M1> vpnt gre MAX216M1> vpnt pw list MAX216M1> vpnt cif list Properly configure fifteen more virtual LANs (all untagged) on each VLAN switch, and aggregate the traffic to the port connected to each ZyXEL
42/80

MIMO CPEs LAN port. Check if the PC in each VLAN behind ZyXEL MIMO CPE A can acquire an IP address from the DHCP server in the corresponding VLAN behind ZyXEL MIMO CPE B. When the PC in each VLAN behind ZyXEL MIMO CPE A are acquiring an IP address from the DHCP server, the DSCP of each VLAN can be checked by monitoring the packets in the established GRE tunnel). After the PC in each VLAN has acquired an IP address, check if the PC can access the Internet without any problem. Check out the traffic counters of each ZyXEL MIMO CPE by executing the following CLI commands. MAX216M1> vpnt pw cnt display all MAX216M1> vpnt cif cnt display all

43/80

6.9 Software Upgrade

6.9.1 Download Files
Please get the file from release FTP. There will be five files in the daily release folder MIMO CPE\MAX206M2\20080520

3.60BCC0b3_20080520.rtf is the release note. MAX206M2_readme.txt is the descript of the files. MAX206M2_b3_20080520(13506).zip is the major firmware which includes WiMAX CARD and SYSTEM BOARD firmware both. It is for the ONE STEP firmware upgrade and Web GUI firmware upgrade. This ONE STEP firmware upgrade only be supported after b4_20080724 version. MAX206M2_b3_20080520(13506)_SBFW.zip is the SYSTEM BOARD firmware only MAX206M2_b3_2008050(13506)_WCFW.zip is the WiMAX CARD firmware only.

6.9.2 Unzip the files

Unzip each file your will get the folder which contact the firmware inside.

In each folder there are three files.

6.9.3 Upgrade Notification

The One-Step Upgrade only can be supported after b4_20080724 version. The older version and other needs to do the TWO steps upgrade. Upgrade System Board first. Then Upgrade the WiMAX CARD.

6.9.4 Upgrade SYSTEM BOARD

Into the MAX206M2_b3_20080520(13506)_SBFW folder 44/80

Click the SYSTEM_BOARD_Upgrade.bat (If you change your CPE LAN IP and Admin Password, please edit the IP in the batch file to fit your option and fwupdate_max216m1.txt for the admin password. The firmware upgrade will start.

In the upgrading, all LED will flashing. After the flashing, the system will reboot and it means upgrade complete.

6.9.5 Reset to DEFAULT ROM

6.9.5.1 Reset by HW You can use the reset button to reset the default rom. Push the reset button keep 5 sec. It will start to reset default and reboot. MAX216M1 reset Button

MAX206M2 reset Button

45/80

6.9.5.2 Reset by command Telnet into CPE. Type the cli sys

rom and click Y.

It will start to reset default and reboot.

6.9.6 Upgrade WiMAX CARD

Click the WiMAXCARD_Upgrade.bat (If you change your CPE LAN IP and Admin Password, please edit the IP in the batch file to fit your option and wcfw.txt for the admin password. The firmware upgrade will start. Into the MAX206M2_b3_20080520(13506)_WCFW folder

46/80

In the upgrading, all LED will flashing. After the flashing, the system will reboot and it means upgrade complete.

6.9.7 ONE STEP FW/SW Upgrade

(ONLY SUPPORT AFTER b4_20080724 VERSION) 6.9.7.1 Upgrade by FTP Into the MAX206M2_b3_20080520(13506) folder

Click the MAX206M2_Upgrade.bat (If you change your CPE LAN IP and Admin Password, please edit the IP in the batch file to fit your option and wcfw.txt for the admin password. The firmware upgrade will start.

In the upgrading, all LED will flashing. After the flashing, the system will reboot and it means upgrade complete. 6.9.7.2 7.2 Upgrade by Web Login to Web. Into page Advance -> System configuration -> Firmware You can selection the file to upgrade the firmware.

Please select MAX206M2.wcwd During the FW/SW upgrading, the all LED will blinking until upgrade completed, system will reboot automatically after upgrade, just wait 4~5 minutes

47/80

6.10 Hardware Reset Mechanism

Here are the different mechanisms of reset button exist at the back of the CPE.
6.10.1 Normal reboot
Push the reset button for 1 second and release.

6.10.2 Level 1 Reset

When the power of the CPE has been turn on, and make sure the PWD LED is light on steadily. Push the reset button for more than 5 sec and release. After doing this action, the CPE will reset to the last customized parameters loaded by CROM tool or reset to ZyXEL factory default parameters if no customization ever done.

48/80

6.10.3 Level 2 Reset

Turn off the CPE first then push on the reset button before power on the CPE. While pushing the reset button, power on the CPE and continue push the reset button for more than 30 seconds and release. By doing this, the CPE will reset back to ZyXEL factory default parameters.

49/80

7. Troubleshooting
When you do the IOT test, you may encounter some unexpected conditions in the network entry process; this chapter is to provide the troubleshooting steps in order to help you run the IOT test smoothly.

7.1 What can I do when struggling in the DL_SYN and Ranging process?
When you encounter the conditions as diagram, you can follow the steps to solve that problem. 1. The WiMAX indicator is blinking or no blink. 2. The trace log displayed the DL_SYNCHRONIZATION or RANGING.

Step1: Check the WiMAX card status. If the Power led is red, it indicates the WiMAX card is damaged, not ready or has become unseated from the main board. You can also perform the CLI command wimax debug to check the card is alive or not. If you use the command wimax debug 18 trying to reboot the wimax card, but it still is failed, you may send the card back to ZyXEL.

50/80

Step2: Check scan frequency setting in the main board.

Step3: Check current frequency status in the WiMAX card. After you ran the step2, You have to check the frequency setting is using correctly in the wimax card.

51/80

Step4: Check signal quality in the WiMAX card. The ZyXEL MIMO CPE connection RSSI threshold value is about -90 dBi, if the RSSI value is less than -90, the ranging process might be failed.

Master stroke Send the trace log to ZyXEL After you followed the steps above, the CPE is still struggling in the DL_SYNCHRONIZATION or RANGING. Please follow the steps as diagram to send the trace log to ZyXEL.

52/80

7.2 What can I do when struggling in the Authentication process?

When you encounter the conditions as diagram, you can follow the steps to solve that problem. 1. The trace log displayed the AUTHORIZATION or EAP FAIL.

Step1: Check the RSSI strength. If the RSSI is less than -90, it might be caused the authentication process failure.

Step2: Check the setting of EAP. You could have to check some EAP settings like username, password, authentication mode, inner authentication, anonymous ID and verify server certificate demand.

53/80

Step3: Check the Trust CA certificate and date.

Step4: Check the Device certificate and date. If customer dont need this, we can skip this step.

Step5: Restart the network entry again.

54/80

Master stroke Send the trace log to ZyXEL After you followed the steps above, the CPE is still struggling in the Authentication process. Please follow the steps as diagram to send the trace log to ZyXEL.

PS: If you have console line, please also peform the command wimax eap debug 0 1 to dump more detail log.

55/80

7.3 What can I initiate the IDLE process?

Initiate IDLE mode and the IDLE period to enter IDLE mode

7.4 What can I do the IDLE troubleshooting?

If you encounter IDLE problem, please follow the steps below to send the trace log to ZyXEL. Step1: Enable the handover log function

Step2: Check the handover log is enabled

Step3: Enable the wimax log and catch the trace log.

56/80

7.5 What can I do the handover troubleshooting?

If you encounter handover problem, please follow the steps below to send the trace log to ZyXEL. Step1: Enable the handover log function

Step2: Check the handover log is enabled

Step3: Enable the wimax log and catch the trace log.

57/80

7.6 What can I do the VOIP troubleshooting?

7.6.1 Use WireShark software to catch the VOIP trace log.
Step1: Perform the command wimax iot setaircopy2LAN to dump the packet traffic from WAN to LAN.

Step2: Open the WireShark software to catch the VOIP trace log, type the filter rule sip to filter the VOIP packets.

58/80

7.6.2 Use ZyXEL console line to catch the VOIP trace log.
Step1: take off the device housing and plug in the console line to main board.

Step2: First make sure that the Internet is accessible from the device. Make a simple ping from CLI to do it. If the server address uses domain name, make sure the domain name can be properly resolved and SIP server is reachable.

Step3: To generate SIP signal trace log, please type voice sip tl (tl stands for trace log). 0 is default value and stands for none. 1 captures all logs (This mode is suggested to capture log for ZyXEL support.). 2 only capture the outgoing sip signaling. 3 only capture the incoming sip signaling. 4 only captures SIP TX and RX sip signaling. 5 only capture the state machines status. 6 only show error. 59/80

7 only show warning. If problem is encountered upon registration or signaling, we suggest to make a level 4 trace of SIP transmit and receive signal. This will make the log more readable due to its including only the TX and RX signal trace. Then access from console on the PCB, and in CLI mode. 1. Type voice sip tl h to show all the options. 2. Type voice sip tl<value> to set the trace log level. In this example, Option 4 is used. 3. Type exit to exit the CLI, but still with the console connected and terminal open.

Step4: For ZyXEL MIMO CPE ,if you want to do the test on CLI mode directly, please use CLI command voice sip sigreg <index> to enable the SIP1/SIP2 setting; voice sip sigunreg <index>to disable the SIP1/SIP2 setting.

60/80

Step5: After making a registration or call attempt, you should see the signal dump on the terminal. In it, you can check whether there are SIP error codes and check what the error is. You can have a configuration change to be on the error code which you received and try again.

Step6: In the above case, the registration failure is caused by failed authorization. Thus, error code 401 Unauthorized is received.

61/80

Step7: The registration is successful now. If a problem can not be resolved, capture the whole log dump from the starting of the registration or call until the problem was encountered and send it to the support for further analysis.

Step8: If all the attempts fail, use the this command voice fsm debug all 1 to capture a complete debug log. The procedure is as with the trace log command and dumps all the log from start until the problem occurred and sends it to us for analysis. Phone = fxs, fxo Debug Ccm = Call Control Management Sip = Sip Protocol Debug Ua = User Agent Debug Sip Tx = Sip Transition Debug Rtp = RTP Packet Debug

62/80

SIP response codes reference

63/80

64/80

8. Appendix
8.1 FAQ
How MAC address is managed in Simple CPE? There are two MAC addresses reserved for each Simple CPE. One for LAN, the other for WiMAX. They are consecutive numbers. When Simple CPE powers up, it will check and write the MAC address in to PCMCIA card. This address will also be saved in PCMCIA cards flash ROM. If you try to swap several PCMCIA cards in a single Simple CPE, it might cause all cards share same MAC addresses. Remember not to use these cards separately in notebook. What version of EAP-TTLS is supported? Only support v0

8.2 TR-069 Parameters

ZyXEL WiMAX CPE supports following parameters.

8.2.1 WiMAX Specific TR-069 parameters 8.2.2 InternetGatewayDevice parameter:

Support list of TR069 Objects and Parameters 1 Type 2 InternetGatewayDevice. DeviceSummary LANDeviceNumberOfEntries 65/80 object string uint Write 3 Description 4 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1

WANDeviceNumberOfEntries InternetGatewayDevice.DeviceInfo. Manufacturer ManufacturerOUI ModelName Description ProductClass SerialNumber HardwareVersion SoftwareVersion ModemFirmwareVersion SpecVersion ProvisioningCode UpTime FirstUseDate DeviceLog

uint object string string string string string string string string string string string uint

W -

dateTim e string -

As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1

InternetGatewayDevice.ManagementServer. URL Username Password PeriodicInformEnable PeriodicInformInterval PeriodicInformTime ParameterKey ConnectionRequestURL 66/80

object string string string

W W W

boolean W uint [1:] W dateTim W e string string -

ConnectionRequestUsername ConnectionRequestPassword UpgradesManaged InternetGatewayDevice.Time. NTPServer1 NTPServer2

string string

W W

boolean object string string W -

NTPServer3

string

NTPServer4

string

NTPServer5

string

CurrentLocalTime LocalTimeZone LocalTimeZoneName DaylightSavingsUsed DaylightSavingsStart DaylightSavingsEnd InternetGatewayDevice.Layer3Forwarding. DefaultConnectionService ForwardNumberOfEntries

dateTim W e string W string W

boolean W dateTim W e dateTim W e object string uint W

InternetGatewayDevice.Layer3Forwarding.Forw object arding.{i}. Enable 67/80

boolean W

As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 ps. only support 1 NTPserver As defined in TR-098 Amendment 1 ps. only support 1 NTPserver As defined in TR-098 Amendment 1 ps. only support 1 NTPserver As defined in TR-098 Amendment 1 ps. only support 1 NTPserver As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 ps. only one WAN interface. As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 ps. Max instance number = 8 As defined in TR-098 Amendment 1

Status Type DestIPAddress DestSubnetMask GatewayIPAddress Interface ForwardingMetric InternetGatewayDevice.LANConfigSecurity. ConfigPassword InternetGatewayDevice.IPPingDiagnostics DiagnosticsState

string string string string string string

W W W W -

int [-1:] W object string object string W W

Interface Host NumberOfRepetitions Timeout DataBlockSize

string string

W W

uint [1:] W uint [1:] W uint W [1:6553 5] uint [0:63] uint uint uint uint uint W -

DSCP SuccessCount FailureCount AverageResponseTime MinimumResponseTmie MaximumResponseTime

As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 ps. only support Default As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 ps. only one WAN interface. As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 ps. support Requested and Complete As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 ps. support value: 8 ~ 41836 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1

68/80

InternetGatewayDevice.LANDevice.{i} LANEthernetInterfaceNumberOfEntries LANUSBInterfaceNumberOfEntries LANWLANConfigurationNumberOfEntries

object uint uint uint

InternetGatewayDevice.LANDevice.{i}.LANHost object ConfigManagement. DHCPServerConfigurable boolean W DHCPServerEnable DHCPRelay MinAddress MaxAddress SubnetMask DNSServers DomainName IPRouters boolean W boolean string string string string string string W W W W W W

DHCPLeaseTime IPInterfaceNumberOfEntries

int [-1:] W uint W

InternetGatewayDevice.LANDevice.{i}.LANHost object ConfigManagement. IPInterface.{i}. Enable

boolean -

IPInterfaceIPAddress IPInterfaceSubnetMask IPInterfaceAddressingType

string string string

W W W

As defined in TR-098 Amendment 1 ps. instance number = 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 ps. only support one Router address. As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 ps. instance number = 1 As defined in TR-098 Amendment 1 ps. cant disable the only one LAN interface As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1

69/80

InternetGatewayDevice.LANDevice.{i}.LANEthe object rnetInterfaceConfig.{i}. Enable Status MACAddress MaxBitRate DuplexMode

boolean string string string string -

As defined in TR-098 Amendment 1 ps. LAN interface can not be disable As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 ps. instance number = 1. As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 ps. instance number = 1. As defined in TR-098 Amendment 1

InternetGatewayDevice.LANDevice.{i}.LANEthe object rnetInterfaceConfig.{i}.Stats. BytesSent uint BytesReceived PacketsSent PacketsReceived InternetGatewayDevice.LANDevice.{i}.Hosts. HostNumberOfEntries uint uint uint object uint

InternetGatewayDevice.LANDevice.{i}.Hosts.H object ost.{i}. IPAddress AddressSource LeaseTimeRemaining MACAddress HostName InterfaceType Active InternetGatewayDevice.WANDevice.{i}. WANConnectionNumberOfEntries 70/80 string string

int [-1:] string string string -

boolean object uint -

InternetGatewayDevice.WANDevice.{i}.WANCo object mmonInterfaceConfig. EnabledForInternet WANAccessType Layer1UpstreamMaxBitRate Layer1DownstreamMaxBitRate PhysicalLinkStatus TotalBytesSent TotalBytesReceived TotalPacketsSent TotalPacketsReceived MaximumActiveConnections NumberOfActiveConnections

As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 ps. instance number = 1. As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 ps. instance number = 1. As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 ps. support IP_Routed IP_Bridged As defined in TR-098 Amendment 1 ps. string length dont exceed 10 bytes As defined in TR-098 Amendment 1

boolean W string uint utin string uint uint uint uint uint uint -

InternetGatewayDevice.WANDevice.{i}.WANCo object nnectionDevice.{i}. WANIPConnectionNumberOfEntries WANPPPConnectionNumberOfEntries uint uint

InternetGatewayDevice.WANDevice.{i}.WANCo object nnectionDevice.{i}.WANIPConnection.{i}. Enable ConnectionStatus PossibleConnectionTypes ConnectionType

boolean string string string W

Name

string

Uptime 71/80

uint

LastConnectionError IdleDisconnectTime RSIPAvailable NATEnabled AddressingType ExternalIPAddress SubnetMask DefaultGateway DNSEnabled

string uint

boolean boolean W string string string string W W W W

boolean W

DNSOverrideAllowed DNSServers MACAddress ConnectionTrigger RouteProtocolRx

boolean string string string string W W W

PortMappingNumberOfEntries

uint

InternetGatewayDevice.WANDevice.{i}.WANCo object nnectionDevice.{i}.WANIPConnection.{i}.PortM apping.{i}. PortMappingEnabled PortMappingLeaseDuration RemoteHost ExternalPort InternalPort PortMappingProtocol 72/80

boolean W uint string string string string W W W W W

As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 ps. unable to disable DNS server As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 ps. only support AlwaysOn As defined in TR-098 Amendment 1 ps. support Off RIPv1 RIPv2 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 ps. max instance number = 11. As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1

InternalClient PortMappingDescription

string string

W W -

InternetGatewayDevice.WANDevice.{i}.WANCo object nnectionDevice.{i}.WANIPConnection.{i}.Stats. EthernetBytesSent uint EthernetBytesReceived EthernetPacketsSent EthernetPacketsReceived uint uint uint

As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1 As defined in TR-098 Amendment 1

8.2.3

InternetGatewayDevice.Service.VoiceService parameters:
Write 3 Description 4 As defined in TR-104 As defined in TR-104 As defined in TR-104 ps. instance number = 1. As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 ob uint object uint object uint uint uint uint string string

Support list of TR069 Objects and Parameters 1 Type 2 Services. VoiceServiceNumberOfEntries .VoiceService.{i}. VoiceProfileNumberOfEntries .VoiceService.{i}.Capabilities. MaxProfileCount MaxLineCount MaxSessionsPerLine MaxSessionCount SignalingProtocols Regions RTCP SRTP RTPRedundancy DSCPCoupled EthernetTaggingCoupled PSTNSoftSwitchOver FaxT38

boolean boolean boolean boolean boolean boolean boolean -

73/80

FaxPassThrough ModemPassThrough ToneGeneration RingGeneration NumberingPlan ButtonMap .VoiceService.{i}.Capabilities.SIP. Role Extensions Transports URISchemes EventSubscription ResponseMap .VoiceService.{i}.Capabilities.Codecs.{i}. EntryID Codec BitRate PacketizationPeriod SilenceSuppression .VoiceService.{i}.VoiceProfile.{i}. Enable Reset NumberOfLines Name SignalingProtocol MaxSessions DTMFMethod .VoiceService.{i}.VoiceProfile.{i}.ServiceProvid erInfo. 74/80

boolean boolean boolean boolean boolean boolean object string string string string -

As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 ps. instance number = 4 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 ps. instance number = 2. As defined in TR-104 ps. support Disable Enable As defined in TR-104 As defined in TR-104

boolean boolean object uint string uint string -

boolean object string W

boolean W uint string string uint string W W

As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104

Name URL ContactPhoneNumber EmailAddress .VoiceService.{i}.VoiceProfile.{i}.SIP. ProxyServer ProxyServerPort ProxyServerTransport RegistrarServer RegistrarServerPort RegistrarServerTransport UserAgentDomain UserAgentPort UserAgentTransport OutboundProxy OutboundProxyPort RegistrationPeriod RegisterExpires RegisterRetryInterval UseCodecPriorityInSDPResponse .VoiceService.{i}.VoiceProfile.{i}.RTP. LocalPortMin LocalPortMax DSCPMark TelephoneEventPayloadType 75/80

string string string string

W W W W

As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104

string

As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 ps. support value: 50000 ~ 65535 As defined in TR-104 ps. support value: 50000 ~ 65535 As defined in TR-104 As defined in TR-104

uint W [0:6553 5] string W string W

W uint [0:6553 5] string string W

uint W [0:6553 5] string string W

W uint [0:6553 5] uint [1:] W uint [1:] W uint [1:] W boolean object uint [0:6553 5] uint [0:6553 5] uint [0:63] uint W W W -

.VoiceService.{i}.VoiceProfile.{i}.Line.{i}. Enable DirectoryNumber Status CallState PhyReferenceList .VoiceService.{i}.VoiceProfile.{i}.Line.{i}.SIP. AuthUserName AuthPassword URI

object string string string string string object string string string

W W W W W W W W W

As defined in TR-104 ps. instance number = 1 As defined in TR-104 ps. support Disable Enable As defined in TR-104 ps. max string length = 127 As defined in TR-104 As defined in TR-104 As defined in TR-104 ps. the valid value: 0, 1, 2 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 ps. max string length = 127 As defined in TR-104 As defined in TR-104 ps. value range: [-13: 13] As defined in TR-104 ps. value range: [-13: 13] As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104

.VoiceService.{i}.VoiceProfile.{i}.Line.{i}.Callin object gFeatures. CallerIDName string .VoiceService.{i}.VoiceProfile.{i}.Line.{i}.Voice object Processing. TransmitGain int ReceiveGain EchoCancellationEnable EchoCancellationInUse EchoCancellationTail int

boolean W boolean uint -

.VoiceService.{i}.VoiceProfile.{i}.Line.{i}.Code object c. TransmitCodec string ReceiveCodec TransmitBitRate ReceiveBitRate TransmitSilenceSuppression string uint uint

boolean -

76/80

boolean Support list of TR069 Objects and Parameters 1 InternetGatewayDevice.X_ZYXEL-COM-TW_WiMAX. CINRMean CINRDeviation RSSI ULDataRate DLDataRate TxPower Type 2 object string string string string string string -

As defined in TR-104 Write 3 Description 4

The sub-root of vendor-specific parameters related to wimax. Mean CINR report (dB)

Standard deviation CINR report (dB) Mean RSSI report (dBm) Uplink Data Rate (bits/s) Downlink Data Rate (bits/s) Transmission Power (dBm)

InternetGatewayDevice.X_ZYXEL-COM-TW_WiMAX.Ea object p. Username string Password AuthenticationType InnerAuthenticationType string string string

W W W W

AuthMode

string

MyCertificate

string

AnonymousID Validcert

string string

W W W

InternetGatewayDevice.X_ZYXEL-COM-TW_WiMAX.Fre object quency. DLFrequency1 string

77/80 DLFrequency2 DLFrequenc3 string string W W

the authentication setting of the device Username of device EAP configuration. ps. max string length = 63 Password of device EAP configuration. ps. max string length = 47 The Authentication type of devi EAP configuration. ps. valid value: <md5 | tls | ttls The Inner Authentication type o device EAP configuration. ps. valid value: <chap | pap | mschap | mschap > The Authentication mode of dev EAP configuration. ps. valid value: <0 | 1 | 2 | 6 > (0:none; 1:user-only; 2:device-only with Cert; 6:Cert and User Auth.) The name of using certificate generated from device itself. ps. the valid value is the name the certificates of My Certificat Anonymous ID of device EAP configuration. Username of device EAP configuration. ps. valid value: <0 | 1> The scanning Frequency list stor in the device (unit: kHz). The 1st Frequency setting store in the device (unit: kHz). valid range: 2.3G [0, 2300000 ~ 2500000] k 2.5G [0, 2500000 ~ 2700000] k 3.5G [0, 3400000 ~ 3600000] k The 2ed Frequency setting store in the device (unit: kHz). valid range: the as DLFrequency The 3rd Frequency setting store

TransmitPacketizationPeriod

uint

As defined in TR-104 As defined in TR-104 ps. instance number = 4 As defined in TR-104 As defined in TR-104 As defined in TR-104

.VoiceService.{i}.VoiceProfile.{i}.Line.{i}.Code object c.List.{i}. EntryID uint [1:] Codec BitRate PacketizationPeriod string uint string W

SilenceSuppression Enable Priority

boolean W boolean W uint [1:] W

As defined in TR-104 ps. value range: for G.711: 10~30 for G.729 : 10~80 for G.723.1: only 30 As defined in TR-104 As defined in TR-104 As defined in TR-104 ps. value range: 1~3 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 As defined in TR-104 ps. instance number = 2 As defined in TR-104 As defined in TR-104 As defined in TR-104

.VoiceService.{i}.VoiceProfile.{i}.Line.{i}.Sessi object on.{i}. SessionStartTime dateTim e SessionDuration uint FarEndIPAddress FarEndUDPPort LocalUDPPort .VoiceService.{i}.PhyInterface.{i}. PhyPort InterfaceID Description string -

uint [0:6553 5] uint [0:6553 5] object string -

uint [1:] string -

8.2.4 Vendor-Specific Parameter: 8.2.5 InternetGatewayDevice.X_WIMAXFORUM_OperatorProfile Parameter:

Support list of TR069 Objects and Parameters 1 Type 2 Write 3 Description 4

78/80

InternetGatewayDevice.X_WIMAXFORUM_OperatorProfile.{i}. InternetGatewayDevice.X_WIMAXFORUM_OperatorProfile.{i}. WiMAXNetworkParameters. ChannelPlanNumberOfEntries

object object

As defined in NWG_Rel_1 5_OTA_Based_On_TR-069. doc As defined in NWG_Rel_1 5_OTA_Based_On_TR As defined in NWG_Rel_1 5_OTA_Based_On_TR As defined in NWG_Rel_1 5_OTA_Based_On_TR As defined in NWG_Rel_1 5_OTA_Based_On_TR valid range: 5000 (means 5M) 8750 (means 8.75M) 10000 (means 10M) or 3500, 4375, 7000. As defined in NWG_Rel_1 5_OTA_Based_On_TR ps. Valid according to Bandwidth As defined in NWG_Rel_1 5_OTA_Based_On_TR ps. Only support 1: TDD As defined in NWG_Rel_1 5_OTA_Based_On_TR As defined in NWG_Rel_1 5_OTA_Based_On_TR As defined in NWG_Rel_1 5_OTA_Based_On_TR valid range: 5000 (means 5M) 8750 (means 8.75M) 10000 (means 10M) or 3500, 4375, 7000. As defined in NWG_Rel_1 5_OTA_Based_On_TR As defined in NWG_Rel_1 5_OTA_Based_On_TR

InternetGatewayDevice.X_WIMAXFORUM_OperatorProfile.{i}. WiMAXNetworkParameters.DefaultChannelPlan. . Bandwidth int

unsigne d Int object -

FFTSize

int

DuplexMode

int

InternetGatewayDevice.X_WIMAXFORUM_Oper object atorProfile.{i}. WiMAXNetworkParameters.ChannelPlan.{i}. ChannelPlanIdentifier string(2 W 0) Bandwidth int W

FFTSize DuplexMode

int int

79/80

FirstFrequency

int

LastFrequency

int

NextFrequencyStep Preambles

int

string(2 W 9)

As defined in NWG_Rel_1 5_OTA_Based_On_TR valid range: 2.3G [0, 2300000 ~ 2500000] kHz 2.5G [0, 2500000 ~ 2700000] kHz 3.5G [0, 3400000 ~ 3600000] kHz As defined in NWG_Rel_1 5_OTA_Based_On_TR valid range: 2.3G [0, 2300000 ~ 2500000] kHz 2.5G [0, 2500000 ~ 2700000] kHz 3.5G [0, 3400000 ~ 3600000] kHz As defined in NWG_Rel_1 5_OTA_Based_On_TR As defined in NWG_Rel_1 5_OTA_Based_On_TR

80/80