Академический Документы
Профессиональный Документы
Культура Документы
Page 2 of 102
Contents
1.
INTRODUCTION ...................................................................................................................................................... 8
2.
APPLICABILITY ...................................................................................................................................................... 8
2.1.
3.
4.
5.12.5.
IGMP ....................................................................................................................................................... 93
5.12.6.
VoIP MGCP ............................................................................................................................................. 94
5.12.7.
VoIP SIP .................................................................................................................................................. 94
5.12.8.
VoIP Endpoint ......................................................................................................................................... 95
5.13. ISSUES RESOLVED ON RELEASE 4.1.1 (INTERNALLY 4.1.1_50) .......................................................................... 96
5.13.1.
SYSTEM ................................................................................................................................................... 96
5.13.2.
SNTP ........................................................................................................................................................ 96
5.13.3.
QoS .......................................................................................................................................................... 97
5.13.4.
Switch & vlan ........................................................................................................................................... 97
5.13.5.
IP ............................................................................................................................................................. 97
5.13.6.
SwUpdate ................................................................................................................................................. 98
5.13.7.
VoIP ......................................................................................................................................................... 99
5.14. ISSUES RESOLVED ON RELEASE 4.1 (INTERNALLY 4.1_69) ............................................................................. 101
5.14.1.
SYSTEM ................................................................................................................................................. 101
5.14.2.
SWITCH ................................................................................................................................................. 101
5.14.3.
IGMP ..................................................................................................................................................... 101
5.14.4.
DHCP Server ......................................................................................................................................... 101
Page 7 of 102
1.
INTRODUCTION
This document lists new features, solved issues and known issues in AT-iMG1400, AT-iMG1500, AT-iMG2400 and ATiMG2500 Next Generation gateway Series version 4.4.3
The document consists in the following sections:
New features
Known Issues
2.
2.1.
APPLICABILITY
Supported models
Model Name
AT-iMG1405
AT-iMG1425
AT-iMG1425RF
AT-iMG1405W
AT-iMG1425W
Model Name
AT-iMG1505
AT-iMG1525
AT-iMG1525RF
Model Name
AT-iMG2504
AT-iMG2524
AT-iMG2522
AT-iMG2524F
AT-iMG2524H
Model Name
AT-iMG2426F
Page 9 of 102
3.
SOFTWARE PACKAGES
3.1.
Software Update package: its the set of files that includes the main application code plus mandatory support
files (if any) that can be downloaded on the CPE via SwUpdate module.
Web Update package: its one file with embedded 4.4.2 main application code. The Web Update package can
be installed through web page access on the CPE.
plus
3.1.1.
The following table details the Main Application Code version released through the Software Update package for each
iMG model:
software version
Package name
MD5SUM
iMG1405
iMG1425
iMG1425RF
4.4.3
iMG1400-4.4.3.zip
AT-iMG1400-4.4.3
18a85db28b5f72f202cb663d9063d586
4.4.3
iMG1500-4.4.3.zip
AT-iMG1500-4.4.3
bbbe597a4fe92bd3e9cd3504bfd83958
4.4.3
iMG2400-4.4.3.zip
AT-iMG2400-4.4.3
4.4.3
iMG2500-4.4.3.zip
AT-iMG2500-4.4.3
iMG1405W
iMG1425W
iMG1505
iMG1525
iMG1525RF
iMG2426F
48276ad066bfdae909a7fe11a452cf1a
iMG2504
iMG2524
iMG2522
d944dabda00d1fbe597c79ecd8949756
iMG2524F
iMG2524H
Page 10 of 102
3.1.2.
The following table details the Main Application Code version released through the Web Update package for each iMG
model:
software
version
Package name
MD5SUM
iMG1405
iMG1425
iMG1425RF
4.4.3
iMG1400-4.4.3_WEB.zip
AT-iMG1400-4.4.3
18a85db28b5f72f202cb663d9063d586
4.4.3
iMG1500-4.4.3_WEB.zip
AT-iMG1500-4.4.3
bbbe597a4fe92bd3e9cd3504bfd83958
4.4.3
iMG2400-4.4.3_WEB.zip
AT-iMG2400-4.4.3
48276ad066bfdae909a7fe11a452cf1a
4.4.3
iMG2500-4.4.3_WEB.zip
AT-iMG2500-4.4.3
d944dabda00d1fbe597c79ecd8949756
iMG1405W
iMG1425W
iMG1505
iMG1525
iMG1525RF
iMG2426F
iMG2504
iMG2524
iMG2522
iMG2524F
iMG2524H
Table 6. Main Application Code binary packages via WEB Update.
Page 11 of 102
3.1.3.
Embedded subsystems
Version
ATI_INTERNAL_VERSION
AtiBcm-4.4.3_01
GWA_CODE_VERSION
AtiVoip-2.4_20
UBOOT_CODE_VERSION
See Table 9
3.2.
For manufacturing purposes and for special field recovery operations, the Main Application Code is released also in an
additional format: the whole flash image.
The flash image includes the UBOOT startup code plus default configuration scripts plus one copy of the Main
Application Code installed in the main partition
Note that special engineering loads are released in ZIP format file, they MUST be unzipped first.
3.2.1.
software
version
Filename
Md5sum
iMG1405
iMG1425
iMG1425RF
4.4.3
AT-iMG1400-4.4.3.image.full
96505ea0d531a6a4062a6e03cb573edd
4.4.3
AT-iMG1500-4.4.3.image.full
b474ad071cb94013767a74bb8fbe98ee
iMG1405W
iMG1425W
iMG1505
iMG1525
iMG1525RF
Page 12 of 102
4.4.3
AT-iMG2400-4.4.3.image.full
09f4413b453ef1cca04dd76ea883ec69
4.4.3
AT-iMG2500-4.4.3.image.full
b23ebdb630ae62fc037c5f3bdf7ba1ab
iMG2504
iMG2524
iMG2522
iMG2524F
iMG2524H
Table 8. Whole flash images.
Note that special engineering loads cannot be loaded in a production environment. A local serial
connection to the unit is required and the operations can be executed only by qualified personnel.
3.2.2.
UBOOT code
UBOOT
software
version
UBOOT
script
version
UBOOT
Config
Filename
Md5sum
Version
iMG1405
iMG1425
iMG1425RF
1.0.32
1.0.8
1.8
AtiUBoot6828-iMG1400-1.0_32.bin 76DC63CCC2EBF763BB4609559464553A
1.0.23
1.0.8
1.1
AtiUboot636x-1.0_23.bin
1.0.26
1.0.8
1.2
AtiUBoot6818-iMG2400-1.0_26.bin 2B939E396F69F98B930A3C9644E76B30
1.0.07
1.0.8
1.2
AtiUboot681x-1.0_07.bin
iMG1405W
iMG1425W
iMG1505
iMG1525
9F674E235F2E3920AD3E18DB5CB86D0F
iMG1525RF
iMG2426F
iMG2504
iMG2524
iMG2522
FEEE36705EDA49517AB57A98F76DAD15
iMG2524F
iMG2524H
Page 13 of 102
Note that special engineering loads cannot be loaded in a production environment. A local serial
connection to the unit is required and the operations can be executed only by qualified personnel.
Page 14 of 102
4.
4.1.
4.1.1.
Software Release 4.4.2 introduced the router acceleration feature (SMP) on iMG1500 models, performances of
routing/natting have been improved to reach same results of all AT-iMG models
References: CR5676, CR5866
4.1.2.
With Software Release 4.4.2 has been introduced the possibility to redirect accesses for public services to internal IP
natted locations. An action of postrouting has been added via port mapping setting.
References: CR7440
4.1.3.
Support for Sip Registration timeout parameter into Sip Register message
To better respond the requests coming from VOIP world with Software Release 4.4.2 it has been improved SIP
module to be able to manage timeout parameter of SIP registration dialogue.
References: CR7624
4.2.
4.2.1.
Software Release 4.4 supports now Host Resource MIB for monitoring CPU & memory usage.
References: CR7488
4.2.1.
Software Release 4.4 supports now ifXTable MIB for monitoring wan fiber and lan Ethernet port packet statistics.
References: CR6850
Page 15 of 102
4.2.2.
Support for snmp traps of link UP and DOWN for switchport interfaces
Software Release 4.4 supports now the possibility to enable traps for link up and link down of switchport interfaces.
CLI new command allows to globally enable or disable the feature.
The following CLI commands have been introduced:
awplus(config)# snmp-server enable traps link-status
awplus(config)# no snmp-server enable traps link-status
References: CR4545
4.2.3.
Software Release 4.4 introduces a new behavior for the media gateway. A Non Intelligent device requires the iMG to
respond to and send flash-hook events using SIP INFO messages instead of SIP INVITE messages. This affects call
handling for call-waiting, 3waycall and call transfers.
The following CLI commands have been introduced:
awplus(config-sip-ua)# behavior hook-flash ext-in-call
awplus(config-sip-ua)#no behavior hook-flash ext-in-call
References: CR7496
4.2.4.
Software Release 4.4 adds the possibility to see in log file IP addresses of users connected via telnet or via ssh or via
http.
References: CR7344
4.2.5.
Software Release 4.4 adds the possibility to load a configuration file entirely written in CLI mode, allowing a better
management of configuration files.
References: CR7386
Page 16 of 102
4.2.6.
New CLI commands for support of port range during settings of portmap
Software Release 4.4 extends CLI commands to allow filtering out unknown multicast/unicast traffic originating from
CPE. The set of commands allow blocking the flooding of multicast/unicast traffic for each interface.
The following CLI commands have been introduced:
awplus(config-if)# ip nat portmap <name> protocol <prot> remote-host <IP address> external-port
<port> to <port> local-host <IP address> internal-port <port> to <port>
References: CR7345
4.2.7.
Software Release 4.4 extends CLI commands to allow filtering out unknown multicast/unicast traffic originating from
CPE. The set of commands allow blocking the flooding of multicast/unicast traffic for each interface.
The following CLI commands have been introduced:
awplus(config-if)# switchport block unicast
awplus(config-if)# no switchport block unicast
awplus(config-if)# switchport block multicast
awplus(config-if)# no switchport block multicast
References: CR7460
4.2.8.
Software Release 4.4 extends CLI commands to allow enabling/disabling of broadcast flag into dhcpclient request
message.
The following CLI commands have been introduced:
awplus(config)# interface vlan1
awplus(config-if)# ip dhcp client broadcast-flag
awplus(config-if)# no ip dhcp client broadcast-flag
References: CR5882
4.2.9.
Software Release 4.4 includes NEW SFPs plugins for long distance connections to its list of managed SFPs (see also
chap. 4.3.1 for previous list).
For iMG2426F:
AT-SPFXBD-LC-13,
AT-SPTX,
Page 17 of 102
AT-SPBD10-13,
AT-SPBD20-13/I,
AT-TN-P015-A,
AT-SPBD20EPON-13
AT-SPFX/2
AT-SPFX/15
AT-SPBD40-15/I,
AT-SPBD40-13/I,
AT-SPBD40-1270LU,
AT-SPBD40-1290LU,
AT-SPBD40-1310LU,
AT-SPBD40-1330LU,
AT-SPBD40-1350LU,
AT-SPBD40-1370LU,
AT-SPBD40-1390LU,
AT-SPBD40-1410LU,
AT-SPBD40-1430LU,
AT-SPBD40-1450LU,
AT-SPBD40-1470LU,
AT-SPBD40-1490LU,
AT-SPBD40-1510LU,
AT-SPBD40-1530LU,
AT-SPBD40-1550LU,
AT-SPBD40-1570LU,
AT-SPBD40-1590LU,
AT-SPBD40-1610LU,
AT-SPBD40-1270HU,
AT-SPBD40-1290HU,
AT-SPBD40-1310HU,
AT-SPBD40-1330HU,
AT-SPBD40-1350HU,
AT-SPBD40-1370HU,
AT-SPBD40-1390HU,
AT-SPBD40-1410HU,
AT-SPBD40-1430HU,
AT-SPBD40-1450HU,
AT-SPBD40-1470HU,
AT-SPBD40-1490HU,
AT-SPBD40-1510HU,
AT-SPBD40-1530HU,
AT-SPBD40-1550HU,
AT-SPBD40-1570HU,
AT-SPBD40-1590HU,
AT-SPBD40-1610HU
AT-SPFXBD-LC-13,
AT-SPTX,
AT-SPBD10-13,
AT-SPBD20-13/I,
AT-TN-P015-A,
Page 18 of 102
AT-SPFX/2,
AT-SPFX/15,
AT-SPBD40-15/I ,
AT-SPBD40-13/I
4.3.
There are no new features on Software Release 4.3.3.1 but only fixes of field issues.
4.4.
4.4.1.
Software Release 4.3.3 changes the way SFP compatibility control works:
SFP models that belong to the list of well-known and approved SFPs are put in service without any warning to the
user.
SFP models that belong to the list of well-known incompatible SFPs are never put in service and a warning message
is raised to the user and logged in the system log.
SFP models that are unknown are put in service but a warning message is raised to the user and logged in the
system log.
AT-SPFXBD-LC-13,
AT-SPTX,
AT-SPBD10-13,
AT-SPBD20-13/I,
AT-TN-P015-A,
AT-SPBD20EPON-13
AT-SPFX/2
AT-SPFX/15
AT-SPFXBD-LC-13,
AT-SPTX,
AT-SPBD10-13,
AT-SPBD20-13/I,
AT-TN-P015-A,
AT-SPFX/2
Page 19 of 102
AT-SPFX/15
Note that the usage of a SFP not approved by ATI can damage seriously the unit or even cause
personnel injury.
4.4.2.
Software Release 4.3.3 introduces the possibility to control the way the iMG is restarted when a critical problem
happens on the VoIP stack.
Before release 4.3.3, a critical VoIP problem would cause the entire iMG to restart in order to recover from the VoIP
issue.
Starting from release 4.3.3 a configuration parameter has been introduced to instruct the system to perform a specific
action when VoIP crashes:
The new attribute can be manipulated only via debug commands by setting the following data model object:
InternetGatewayDevice.VoiceProfile.1.X_ALLIEDTELESIS_COM_FailureAction
The values acceptable by this attribute are:
4.4.3.
Software Release 4.3.3 enhances the control of software upgrade when triggered via DHCP options.
Its now possible to disable TFTP software upgrade by setting statically the ACS URL address or by setting in the data
model the attribute:
InternetGatewayDevice.X_BROADCOM_COM_AppCfg.X_ALLIEDTELESIS_COM_SwupdateCfg.DhcpTriggerEnable
to be 0 (default is 1)
A dhcp initiated download only occurs if:
1.
2.
3.
4.
4.4.4.
Software Release 4.3.3 introduces the control of system restart via SNMP interface.
Its now possible to allow a remote SNMP management system to force a system restart by setting to true the
following SNMP object:
.enterprises.alliedTelesyn.residentialGateway.iMG1000.sys.sysAdmin.sysRestart
For security reasons, by default this attribute cannot be set.
To enable the sysRestart SNMP object, the following CLI command has been introduced:
awplus(config)# snmp-server system-shutdown
References: CR7137
4.4.5.
4.4.6.
Software Release 4.3.3 extends CLI file management commands and make possible to override the default_button.cfg
file by using one existing configuration file or the running configuration.
Its therefore possible to create default_button.cfg files that are customized per user and that can contains an operative
configuration suitable for the customer.
For example a customized user default_button.cfg could contain wireless configuration parameters at their defaults
with a well know public SSID and password while all the remaining iMG configuration is fully operative for all the other
services.
So all the following CLI commands now work:
awplus# copy test.cfg default_button.cfg
awplus# copy default_button.cfg test.cfg
Page 21 of 102
4.4.7.
Software Release 4.3.3 extends CLI commands to support the description field on switch interfaces.
The following new CLI command has been introduced:
awplus(config-if)# description <port-description>
References: CR5560
4.4.8.
Software Release 4.3.3 extends CLI commands to fully configure wireless interface without requiring access to the
WEB interface or TR69 data model.
The extended set of commands is useful when provisioning of iMG1400W models is mainly operated via CLI scripts.
The following command is used to specify the Wi-Fi country, i.e. the range of allowed frequencies for Wi-Fi interface:
awplus(config)# interface dot11radio1.0.1
awplus(config-if-dot11radio)# world-mode dot11d country-code <countryID>
The following command is used to change the network name on the selected SSID:
awplus(config)# dot11 ssid <old_SSID>
awplus(config-if-ssid)# ssid-name <new_SSID>
The following command is used to change the host authentication/encryption protocol on the selected SSID:
awplus(config)# dot11 ssid <SSID>
awplus(config-if-ssid)# wpa-psk ascii <wpa_passphrase>
awplus(config-if-ssid)# authentication key-management wpa2-psk
The following command is used to hide/unhide the broadcast of the network SSID:
awplus(config)# dot11 ssid <SSID>
awplus(config-if-ssid)# no guest-mode
Page 22 of 102
The following command is used to create and enable a white list of MAC addresses allowed to connect:
awplus(config)# dot11 ssid <SSID>
awplus(config-if-ssid)# permit 00:22:FB:07:CC:5A
awplus(config-if-ssid)# permit
The following command is used to create and enable a black list of MAC addresses not allowed to connect:
awplus(config)# dot11 ssid <SSID>
awplus(config-if-ssid)# deny 00:22:FB:07:CC:5A
awplus(config-if-ssid)# deny
The following command is used to change the channel used by the Wi-Fi radio:
awplus(config)# interface dot11radio1.0.1
awplus(config-if-dot11radio)# channel {number of channel| MHz | least-congested}
The following command is used to change the 802.11 protocol family:
awplus(config)# interface dot11radio1.0.1
awplus(config-if-dot11radio)# protocol-family <protocol>
The following command is used to enable client isolation on the selected SSID:
awplus(config)# dot11 ssid <SSID>
awplus(config-if-ssid)# client-isolation
References: CR6468
4.4.9.
In Software Release 4.3.3 color and font schemas for WEB pages are changed accordingly to new MarCom
recommendations.
References: CR6981
4.4.10.
TM
The USB universal driver configuration file already release in 4.3.2 is also valid for Windows 8.
References: CR6992
Page 23 of 102
4.5.
4.5.1.
Software Release 4.3.2 introduces the lock of Wi-Fi frequencies depending on the country where the unit is used.
The frequency lock is done at production level, therefore is not possible to remove the lock without RMA the unit.
For the countries where lock is active, the WEB interface does not allow to change the Wi-Fi country (and therefore
the frequencies channels range); for all the other cases the Wi-Fi country can be changed via WEB or via CLI.
References: CR6919, CR6920, CR6932
Page 24 of 102
4.5.2.
Software Release 4.3.2 introduces the support to log wireless button activity when it is pushed to turn on/off wireless
radio.
References: CR6895
4.5.3.
4.5.4.
Software Release 4.3.2 introduces the support to manage GEPON SFP on iMG2426 product.
No special CLI commands are needed to enable the feature. The GEPON SFP module is automatically detected and
the interface is referred by CLI commands as port1.0.7 like any other SFP type.
References: CR6928, CR6929
4.5.5.
Software Release 4.3.2 introduces the support to manage only ATI Certified SFP's.
Units produced after release 4.3.2 will have an hard coded configuration flag that prevents SFPs that are not Allied
Telesis to operate. In this case the WAN connection will remain always down and a warning message is prompted any
time a user logins into the system.
Units produced before release 4.3.2 do not have such hard coded configuration flag. Therefore in this case SFPs that
are not Allied Telesis will still work. Also in this case a warning message is prompted any time a user logins into the
system to inform that the SFP is not Allied Telesis certified.
The following is the list of SFPs supported on release 4.3.2:
AT-SPFXBD-LC-13,
AT-SPTX,
AT-SPBD10-13,
AT-SPBD20-13/I,
AT-TN-P015-A,
AT-SPBD20EPON-13
References: CR6970
Page 25 of 102
4.5.6.
Software Release 4.3.2 introduces the support to manage AT-SPTX on iMG2426F product.
No special CLI commands are needed to enable the feature. AT-SPTX SFP module is automatically detected and the
interface is referred by CLI commands as port1.0.7 like any other SFP type.
References: CR6927, CR6380
4.5.7.
Software Release 4.3.2 introduces the support to manage Terminal Length via AW+ CLI:
For example:
awplus# terminal length 0 (for no pausing)
or
awplus# terminal length 80
References: CR6938
4.5.8.
Software Release 4.3.2 introduces the support to manage session logout via AW+ CLI:
For example:
awplus(config-line)# exec-timeout 0 (for no timeout)
or
awplus(config-line)# exec-timeout {<minutes>} [<seconds>]
References: CR6940
4.5.9.
Software Release 4.3.2 introduces the possibility to disable/enable the Default button functionality.
For example:
awplus(config)# no boot default-button
or
awplus(config)# boot default-button
Page 26 of 102
When default button is disabled, its not possible to force the system to restart executing the configuration associated
to the default button. As consequence the system will boot running a factory (default) configuration.
References: CR6945
4.5.10.
Software Release 4.3.2 introduces the support for a default WEB user that can access only to split management WEB
pages.
The username/password of the default WEB user is: admin/admin.
References: CR6893
4.5.11.
Software Release 4.3.2 introduces the support to detect voice stuck situations and force a system restart to recover
the system.
References: CR6950
4.5.12.
Software Release 4.3.2 introduces the support for OSGI, DLNA, NAS storage service on iMG1600 products.
This is a feature not supported for the field but only for internal development purposes.
References: CR6923
4.5.13.
Software Release 4.3.2 introduces the support of the new model named AT-iMG2726:
Model Name
WAN Interface
LAN Interface(s)
POTS
Wireless
AT-iMG2726
SFP 1000/GPON
10/100/1000Tx (6)
None
Page 27 of 102
AT-iMG2726 is not in production yet. GPON SFPs are still under analysis at the time this software
release note is written. Currently AT-iMG2726 can run only active-fiber SFPs at 1000 Mbps.
4.5.14.
Software Release 4.3.2 introduces the support of the new models named AT-iMG1605, AT-iMG1625, AT-iMG1625RF:
Model Name
WAN Interface
LAN Interface(s)
POTS
Wireless
CATV
AT-iMG1605
1000/GPON
10/100/1000Tx (5)
None
None
None
AT-iMG1625
1000/GPON
10/100/1000Tx (5)
None
None
AT-iMG1625RF
1000/GPON
10/100/1000Tx (5)
None
AT-iMG1600 family is not in production yet. GPON SFPs are still under analysis at the time this
software release note is written. Currently AT-iMG1625 can run only active-fiber SFPs at 1000
Mbps.
References: CR6923
4.6.
4.6.1.
Software Release 4.3.1 introduces the support for multiple SSID (max 4) on the wireless interface.
Each SSID can be associated to a different vlan allowing the deployment of multiservice applications over multiple
wireless networks.
Configuration of multiple SSIDs is a two stage process:
First, each SSID is associated to the proper vlan via CLI commands
For example:
awplus(config)# dot11 ssid iMG1425W_00_01_71
awplus(config-if-ssid)# vlan 204
awplus(config)# dot11 ssid Guest1
awplus(config-if-ssid)# vlan 202
awplus(config)# dot11 ssid Guest2
awplus(config-if-ssid)# vlan 203
awplus(config)# dot11 ssid Guest3
awplus(config-if-ssid)# vlan 205
At this point, via WEB interface, the user can enable or disable secondary SSIDs, change the descriptions and also
specify the type of security separately for each SSID.
Note that Wi-Fi standard and channel frequencies are common to all the SSIDs and cannot be
configured separately for each network.
4.6.2.
Software Release 4.3.1 extends the support for iMG configuration via WEB pages.
In order to display the proper WEB contents, a WEB user with privileges between 9 to 14 must be created:
awplus# configure
awplus(config)# username home-user privilege 9 password my-home-pwd
At this point the following contents are available through WEB GUI:
Summary
WAN Statistics
Password configuration
References: CR6457, CR6711, CR6712, CR6713, CR6714, CR6715, CR6716, CR6717, CR6718, CR6760, CR6751
4.6.3.
Software Release 4.3.1 introduces the possibility to use any LAN interface as uplink WAN interface.
Configuration of the LAN interface follows the same rules as for any trunk interface. The standard WAN interface
(SFP or Fiber based) will be left unconfigured and unplugged.
For what concern the management of IGMP messages for video service, i.e. the detection of the multicast router
interface, the software is able to automatically identify the uplink interface by receiving IGMP queries from the access
network.
Note that only for iMG2426F, LAN5 and LAN6 interfaces cannot be used as uplink WAN
interfaces due to limitations on IGMP. Only LAN1 to LAN4 are allowed to be used for uplink
copper links.
4.6.4.
Software Release 4.3.1 introduces full UPnP support when the iMG is used as router with NAT functionality.
In this case the iMG advertises its capability as an Internet Access Device for any UPnP aware client connected to the
local area network.
UPnP protocol allows internal clients like some Windows applications to configure automatically reserved map rules
on the iMG NAT module accordingly to the service that the application needs to enable.
The NAT reserved map rules configured via UPnP become visible both on the CLI and on the WEB interface but are
not saved in the datamodel.
Page 30 of 102
To enable UPnP support its necessary to specify the outer VLAN where NAT is enabled (this is necessary for multi
homed solutions where more than one IP interface could have NAT configured) and the internal VLAN where UPnP
SSDP messages need to be advertised.
awplus#(config)# interface vlan<public-VID>
awplus#(config-if)# ip upnp network enable
awplus#(config-if)# exit
awplus#(config)# interface vlan<local-VID>
awplus#(config-if)# ip upnp local enable
awplus#(config-if)# end
References: CR6456
4.6.5.
The CLI show file command now accepts also *.txt files generated by the show tech and show tech all CLI
commands.
References: CR6674
4.6.6.
Software Release 4.3.1 extends the SIP stack functionalities by adding the support for SIP pseudonyms.
Its now possible to associate to each dial peer pots a strings (alphanumeric) that is used during the registration phase
as local URI. The same string can also be used as termination identifier for incoming calls.
For example:
awplus#(config)# dial-peer voice 1 pots
awplus(config-dial-peer)# destination-pattern 201723239873
awplus(config-dial-peer)# registration-name MrBobBrown-Line1
References: CR6763
Page 31 of 102
4.6.7.
Starting from Software Release 4.3.1 its possible to enable/disable via CLI command the monitoring of Battery Back UP
alarm lines. Previously the feature was configurable only via TR69 interface.
The new command is:
awplus#(config)# psu-management
References: CR5129
4.6.8.
Starting from Software Release 4.3.1 its possible to read interface packets statistics via SNMP as defined by ifTable in
RFC2863.
There is no specific settings for this feature. SNMP ifTable is immediately available as soon SNMP agent is enabled.
References: CR4505
4.6.9.
The technical support file contents (see show tech CL:I command) has been extended to include information also for
the following modules:
recovery
loop protection
voice translation
port counters
UPnP configuration
4.6.10.
Software Release 4.3.1 introduces the support of the new model named AT-eDM1405:
Model Name
WAN Interface
LAN Interface(s)
POTS
Wireless
AT-eDM1405
SFP 100/1000
10/100Tx (2)
10/100/1000Tx (3)
None
Page 32 of 102
4.7.
4.7.1.
Software Release 4.3 introduces the support of the new models named AT-iMG1405W and AT-iMG1425W belonging
to the iMG1400 families:
The iMG1405W has the same characteristics as iMG1405 plus wireless interface.
The iMG1425W has the same characteristics as iMG1425W plus wireless interface.
Model Name
WAN Interface
LAN Interface(s)
POTS
Wireless
AT-iMG1405W
SFP 100/1000
10/100Tx (2)
10/100/1000Tx (3)
None
AT-iMG1425W
SFP 100/1000
10/100Tx (2)
10/100/1000Tx (3)
FXS (2)
Both the two new models adopt a Wireless radio card that supports b/g/n modes Single Band at 2.4 GHz.
Software Release 4.3 supports only one SSID (that can be associated to just one vlan to transport untagged ethernet
frames). Support for multiple SSID is for future.
Configuration of the wireless interface is mainly performed via WEB interface. CLI commands are needed to assign the
wireless network SSID to a specific vlan.
iMG1405W and iMG1425W have also a wireless button accessible on the left side of the unit that allows the user to
disable/enable the wireless interface (without the need to use WEB interface or CLI commands).
References: CR5855, CR 3986, CR4349, CR4522, CR6177, CR6580, CR6514, CR6483, CR4347 ,CR4269, CR6519, CR6531,
CR6624, CR6169
4.7.2.
Software Release 4.3 introduces the support of the new model named AT-iMG2426F. AT-iMG1405W has the same
characteristics of AT-iMG2524F but it offers 6 LAN interfaces instead of four.
Model Name
WAN Interface
LAN Interface(s)
POTS
AT-iMG2426F
SFP 100/1000
10/100/1000Tx (6)
FXS (2)
4.7.3.
Only for SIP protocol, starting from Software Release 4.3 its possible to automatically add a prefix or replace the first
part of a dialed number.
The administrator can create a set of rules (a translation set) that look for specific patterns in the dialed number and
then perform an action like replace the matching number with another one or add a prefix in front of the dialed
number.
To create a new translation set and assigns an identifier #3 to it:
awplus#(config)# voice translation-rule 3
To create a rule #6 that replaces the prefix 011 with 00:
awplus(config-voi-trans-rule)# rule 6 011 00 replace
To assign a translation set #3 to a POTS interface:
awplus(config)# dial-peer voice 1 pots
awplus(config-dial-peer)# translate-outgoing 3
References: CR4438, CR6629, CR6413
4.7.4.
Software Release 4.3 introduces the Loop Protection feature to protect the iMG from accidental network loops on the
LAN side.
When loop protection is activated, LAN interfaces send periodically special loop protection MAC frames (ldif) to pool
the user side network.
If one of the loop protection frames is received back, this is detected as a loop condition and then the sending interface
is automatically disabled.
Periodically the system will attempt to re-enable the locked interface to check if the loop condition still exists, and in
case no loop frames are received, i.e. there is no more loop, the interface is re-enabled.
To enable loop protection a system level:
awplus(config)# loop-protection loop-detect
To activate loop protection on LAN interfaces:
awplus(config)# interface port1.0.1-port1.0.4
awplus(config-if)# loop-protection
SNMP Private TRAPS are also generated when loop-protection detects a loop on one or more LAN interfaces or
when loop is completely removed.
Page 34 of 102
A new iMG1000 MIB file containing the loop protection objects and TRAPs definition is released.
References: CR4455, CR6644, CR6521, CR6523, CR6510, CR6477, CR6481
4.7.5.
Software Release 4.3 extends IGMP statistics information by adding the following new CLI commands:
awplus# show ip igmp groups
IGMP IGMP Connected Group Membership
Group Address
Interface
Uptime
Expires
Last Reporter
239.255.255.254
port1.0.5
00:21:30
00:03:57
10.17.90.1
224.0.1.60
port1.0.5
00:21:24
00:03:54
10.17.90.31
239.255.255.100
port1.0.5
00:19:52
00:02:38
10.17.90.78
224.2.2.52
dot11radio1.0.1
00:02:56
00:02:30
10.17.90.131
4.7.6.
Software Release 4.3 introduces GR909 testing suite for POTS lines
To start GR909 tests, use the following CLI commands:
awplus(config)# test voice-port tel1
then to review the test results use the following command:
awplus# show test voice-port tel1
References: CR3997, CR6352, CR6335
4.8.
Software Release 4.2.3 is mainly designed to fix issues coming from the field and only few features have been added to
improve interoperability and usability.
4.8.1.
Software Release 4.2.3 releases a new USB .inf file for Windows that instructs Windows 7 how use its own Universal
USB driver when AT-iMG is connected to a USB interface.
Page 35 of 102
This new USB driver makes USB connection much more reliable under Windows 7. In addition a fix on the USB iMG
DHCP server has improved to USB connection resolution reducing the time when USB interface is disconnected and
then reconnected to the same iMG.
References: CR 6390,CR6404
4.8.2.
Software Release 4.2.3 has extended the support by CLI for MIB-II interface statistics.
The following new CLI commands have been introduced:
awplus# show platform port port1.0.x counters
For Example:
awplus# show platform port port1.0.6 counters
Switch Port Counters
-------------------------------------------------------------------------------Port 1.0.6
128 - 255
256 - 511
1036
0
0
General counters:
Receive
Octets
Pkts
CRCErrors
UnicastPkts
Transmit
514454 Octets
3122 Pkts
730458
1458
0
1219 UnicastPkts
1377
MulticastPkts
8 MulticastPkts
BroadcastPkts
1895 BroadcastPkts
81
FlowCtrlFrms
0 FlowCtrlFrms
OversizePkts
Fragments
Jabbers
UpsupportOpcode
UndersizePkts
0
Collisions
0
Page 36 of 102
LateCollisions
ExcessivCollsns
Miscellaneous counters:
MAC TxErr
MAC RxErr
Drop Events
-------------------------------------------------------------------------------References: CR 6286
4.9.
Software Release 4.2.1 is mainly designed to fix issues coming from the field after Software Release 4.2 was released.
The following is the only enhancement added in this release:
4.9.1.
Software Release 4.2.1 adds the support for SNMP traps (private) when restarting in recovery mode in order to inform
a remote management system that the unit needs to be software upgraded.
A new MIB private file is released to export the OIDs of the new added SNMP traps objects.
References: CR 6085
4.10.
4.10.1.
Software Release 4.2 introduces the support of the new model named iMG2524H belonging to the iMG2500 families.
The iMG2524H has the same characteristics as the iMG2524F model but it has HPNA interfaces on the use side.
References: CR 5440
4.10.2.
Software Release 4.2 introduces the support of the new models named iMG1405 and iMG1425 belonging to the
iMG1400 families.
The iMG1405 has the same characteristics as the iMG1505
Page 37 of 102
4.10.3.
Protected Mode is a technique to avoid broadcast traffic to flow between two or more interface belonging to the same
vlan.
Protected mode is also referred on iMAP system as UFO (Uplink Forwarding Only) mode to highlight the fact that this
feature is typically used to force communication between hosts to happen only through the uplink network.
To enable Protected mode on an interface:
configure
interface port1.0.3,port1.0.4
protected
end
References: CR 5477
4.10.4.
Dynamic DNS (ddns) is a feature that allows the IMG to register its own IP address and hostname to a remote ddns
providers (tzo and dyndds).
The iMG can then be reachable via its hostname given the fact the DDNS provider will resolve the iMG ip address for
the rest of the world.
References: CR 5566
4.10.5.
Multicast Routing Acceleration is a technique to allow multicast stream received on a vlan network faced to be
forwarded to a different vlan customer faced.
The cross of vlan boundaries is performed at fabric switch level allowing wire speed performances. It is not a pure
routing in strict sense because TTL is not decreased and multicast frames are not modified.
Page 38 of 102
To enable Multicast Routing Acceleration its necessary to enable igmp snooping and proxy on the outer vlan by
entering:
configure
interface vlan205 (vlan 205 is the vlan video facing the network access)
ip igmp proxy-service
ip igmp snooping
exit
interface vlan100 (vlan 100 is the vlan video facing the customer/local network)
ip igmp snooping
end
References: CR 4462
4.10.6.
SIP Forwarding is an extension of the existing dial peer concept that allows the iMG to talk directly to a remote peer
without having to go through a proxy server.
To configure a FDB peer:
dial-peer voice 4 voip
destination-pattern 215xxxx
session target 172.32.3.121
end
References: CR 4509
4.10.7.
Option 43 - vendor-specific-info
Option 72 - www-server
References: CR 4468
4.10.8.
Software Release 4.2 has introduced the support for Secondary IP Interface over vlan.
Secondary IP interfaces share the same physical media (vlan) of the primary IP interface to which they are attached.
Secondary IP interfaces do not need to be configured on the same subnet as they primary IP interfaces. They can be
static or dynamic via DHCP client with proper dhcp client configuration options.
They participate also to the routing decision process.
To create a secondary ip interface on top of vlan 100:
vlan database
vlan 100 name vlan_data
interface vlan100
ip address dhcp
exit
interface vlan100.1
ip address dhcp
exit
References: CR 5675
4.10.9.
IPV6 Support
IPv6 is a new layer 3 protocol which will supersede IPv4. Major changes in IPv6 are the redesign of the header,
including the increase of address size from 32 bits to 128 bits.
IPv6 has been developed to work in Dual Stack mode with IPv4.
On iMG (all the iMG1400, iMG1500 and iMG2500 families) IPv6 addresses can be configured via stateless
autoconfiguration method (SLAAC), or stateful (DHCPv6) method or both stateless and DHCPv6.
4.10.9.1.
Stateless Autoconfiguration
IPv6 stateless autoconfiguration is a fairly simple protocol. The iMG creates an interface identifier, then obtains a
network prefix that is pre-pended to the interface identifier to configure a global valid IPv6 address
The interface identifier can be used for any link-local or global addresses. This interface identifier, called EUI-64, is 64
bits that are adapted from the device's layer two address, typically MAC-48 in LANs. The interface identifier is then
appended to the prefix fe80::/10, which is reserved for link-local addresses.
Page 40 of 102
The IPv6 router in the access network sends a router advertisement to the all-nodes multicast address with a network
prefix, preferred and valid lifetimes, and a MTU for the link. The prefix is prepended to the interface identifier and a
new, often globally routable, IPv6 address is added to the iMG interface.
To enable IPv6 SLAAC autoconfiguration:
configure
vlan database
vlan 1666 name vlan_ipv6
interface port1.0.6
switchport access vlan 1666
interface vlan1666
ipv6 address autoconfig default
end
4.10.9.2.
DHCPv6 is called ``stateful'' since there is bidirectional communication between the dhcpv6 client and dhcpv6 server.
DHCPv6 stateful IPv6 configuration method allows to obtain options DNS servers or NTP servers) and addresses, in
particular the IPv6 prefix for the prefix delegation feature.
To enable IPv6 DHCPv6 stateful configuration method:
configure
vlan database
vlan 1666 name vlan_ipv6
interface port1.0.6
switchport access vlan 1666
interface vlan1666
ipv6 address dhcp
end
4.10.9.3.
DHCPv6 is capable of being used in communion with IPv6 stateless autoconfiguration method (SLAAC), A DHCPv6
client can be used to just obtain DHCPv6 options only, such as DNS and NTP servers or a prefix-delegation prefix.
To enable IPv6 SLAAC autoconfiguration method with DHCPv6 option:
configure
vlan database
vlan 1666 name vlan_ipv6
Page 41 of 102
interface port1.0.6
switchport access vlan 1666
interface vlan1666
ipv6 address autoconfig default
ipv6 dhcp client pd MyPrefixDel
end
4.10.9.4.
In conjunction with DHCPv6 client, iMG can provide a Router Advertisement Daemon (RADVD) allowing the
possibility to manage an independent internal IPv6 network SLAAC based.
DHCPv6 client will obtain a prefix for prefix-delegation from the external network and will use it on the Router
Advertisement Daemon for the devices connected to its internal network, with the opportunity to provide also
DHCPv6 options to hosts locally connected.
To enable IPv6 SLAAC autoconfiguration method with DHCPv6 prefix-delegation option:
configure
vlan database
vlan 1666 name vlan_ipv6
interface port1.0.6
switchport access vlan 1666
interface vlan1666
ipv6 address autoconfig default
ipv6 dhcp client pd MyPrefixDel
end
To enable Router Advertisement Daemon on internal network and Prefix-delegation application:
configure
vlan database
vlan 3030 name internal_IPv6_network
exit
interface vlan3030
ipv6 address MyPrefixDel 0:0:0:1::/64
ipv6 nd other-config-flag
ipv6 nd ra-interval 60
no ipv6 nd suppress-ra
Page 42 of 102
end
Adding DHCPv6 options for clients connected internally:
configure
interface vlan3030
ipv6 dhcp pool
dns-server
2012:900:1666:1:211:50ff:fe9b:703e
domain-name service.stre.ipv6
ipv6 dhcp server
end
4.10.10.
HPNA Support
HomePNA (HPNA) is a technology used to transport IP data services over coaxial cable.
It is suited for scenarios where the users house is already cabled with coaxial cable for TV service and the service
provider want to add also IP services on the same media
HPNA interface is managed like the other Ethernet interfaces even if some features (rate limiting, port protection and
ipv6 support) are not supported.
HPNA interface is referred in the CLI configuration as hpna1.0.1 interface.
References: CR 5440
Page 43 of 102
4.11.
4.11.1.
Software Release 4.1.2 introduces the support of the new model named iMG2522 belonging to the iMG2500 families.
The iMG2522 has the same characteristics as the iMG2524 model but is has only 2 LAN 10/100/1000Mbps interfaces.
The WAN interface (fiber) supports only 1000Mbps operations (1000BX).
References: CR 5252, CR 5259
4.11.2.
Software Release 4.1.2 introduces the logging of CLI commands history (up to 32 entries) and the possibility to recall
them using the UP/Down arrow keys.
All the CLI commands are now logged into the system log file.
awplus# show history
Also, the system log file can now be cleared by CLI command:
awplus# clear log
References: CR 4895, CR 5100, CR 5313, CR4898
4.11.3.
Software Release 4.1.2 introduces the following supplementary services for SIP protocol:
In the Attended Call Transfer, User A and User B are in a call, then:
1.
User A press the flash-hook button and a dial tone is heard (user B is put on-hold)
2.
User A dial the Attended Call Transfer prefix, a special tone is heard, and User A continues to dial the User C
address,
3.
User C is called,
4.
5.
6.
7.
8.
User A on-hook.
To configure the Attended Call Transfer prefix the following CLI commands are used (example):
User A press the flash-hook button and a dial tone is heard (user B is put on-hold)
2.
User A dial the Blind Call Transfer prefix, a special tone is heard, and User A continues to dial the User C address,
3.
User C is called,
4.
5.
6.
User A on-hook.
To configure the Blind Call Transfer prefix the following CLI commands are used (example):
awplus(config)# voipapp feature access-code
awplus(config-voipapp-fac)# transfer blind *33
To add the Blind Call Transfer service on the POTS interface the following CLI commands are used:
awplus(config)# voipapp supplementary-services
awplus(config-voipapp-suppl-serv)# port tel1
awplus(config-voipapp-suppl-serv-port)# transfer-mode blind
User A press the flash-hook button and a dial tone is heard (user B is put on-hold)
2.
User A dial the 3 Way Call prefix, a special tone is heard, and User A continues to dial the User C address,
3.
User C is called,
Page 45 of 102
4.
5.
6.
7.
8.
To configure the 3 Way Call prefix the following CLI commands are used (example):
awplus(config)# voipapp feature access-code
awplus(config-voipapp-fac)# conference *35
To add the 3 Way Call service on the POTS interface the following CLI commands are used:
awplus(config)# voipapp supplementary-services
awplus(config-voipapp-suppl-serv)# port tel1
awplus(config-voipapp-suppl-serv-port)# conference
References: CR 4437
4.11.4.
Software Release 4.1.2 introduces the following supplementary services for SIP protocol:
Warm Line
Hot Line
To configure the Warm Line prefixes the following CLI commands are used (example):
awplus(config)# voipapp feature access-code
awplus(config-voipapp-fac)# warmline *51
awplus(config-voipapp-fac)# warmline cancel *52
awplus(config-voipapp-fac)# warmline reactivate *53
To add the Warm Line service on the POTS interface the following CLI commands are used:
awplus(config-voipapp-suppl-serv)# port tel1
awplus(config-voipapp-suppl-serv-port)# warmline
To configure the Hot Line its not necessary to specify any Warm Line feature access codes but its necessary to
change the Warm Line timeout to be 0 secs and to specify the hotline number.
For example:
awplus(config)# voipapp supplementary-services
awplus(config-voipapp-suppl-serv)# port tel1
Page 46 of 102
awplus(config-voipapp-suppl-serv-port)# warmline
awplus(config-voipapp-suppl-serv-port)# warmline timeout 0
awplus(config-voipapp-suppl-serv-port)# warmline digits 201723231211
4.11.5.
Software Release 4.1.2 introduces the support for a secondary SIP registrar server and a secondary SIP proxy server:
To configure the Backup servers the following CLI commands are used:
awplus(config-sip-ua)sip-server <SipServerIpaddr> secondary
awplus(config-sip-ua)# registrar <RegistrarIpaddr> secondary
References: CR 5269
4.11.6.
Software Release 4.1.2 introduces the possibility to map the SIP alerting-info attribute to a specific ring pattern
(depending on the selected country).
To configure the SIP alerting-info attribute the following CLI commands are used:
awplus(config)# sip-ua
awplus(config-sip-ua)# map alertinfo <Pattern #> <alert-info string>
Where:
Pattern1 is distinctive-ring-1 (cai)
Pattern2 is distinctive-ring-2 (cai0)
Pattern3 is distinctive-ring-3 (cai1)
Pattern4 is distinctive-ring-4 (cai2)
Pattern5 is distinctive-ring-5 (pingring)
Pattern6 is distinctive-ring-6 (cai4)
Pattern7 is distinctive-ring-7 (cai5)
Pattern8 is distinctive-ring-8 (cai6)
Pattern9 is distinctive-ring-9 (cai7)
Pattern 10 is distinctive-ring-10 (cai8)
References: CR 4440
Page 47 of 102
4.11.7.
Software Release 4.1.2 introduces the possibility to configure via CLI the type of disconnect procedure for POTS
interfaces: Immediate or Timed.
The following CLI command has been introduced to set the disconnect procedure to be Immediate (FXS-DEL):
awplus(config)# voice-port tel1
awplus(config-voiceport)# no disconnect-supervision
The following CLI command has been introduced to set the disconnect procedure to be Timed (FXS-LCFO):
awplus(config)# voice-port tel1
awplus(config-voiceport)# disconnect-supervision
References: CR 5704
4.11.8.
4.11.9.
Q-in-Q Support
Software Release 4.1.2 introduces the support for Q-in-Q and for jumbo frames.
Its possible to configure WAN and/or LAN interfaces to work in provider or customer mode.
Its possible to customize the ethernet TPID value added to the outer VLAN-tag header and to enable/disable jumbo
frame support.
Page 48 of 102
4.11.10.
Software Release 4.1.2 introduces the support for IPv6 transparent bridging mode.
IPv6 frames are now bridged transparently between interfaces belonging to the same vlan.
There is no CLI to enable/disable this feature. This is always enabled.
References: CR 5338
4.11.11.
4.11.12.
Software Release 4.1.2 introduces new CLI commands to manage the switch FDB entries.
The following CLI commands have been introduced:
awplus# show mac address-table
awplus# show mac address-table dynamic
awplus# show mac address-table static
awplus# show mac address-table interface <interface>
awplus# show mac address-table vlan <vlanid>
Page 49 of 102
4.11.13.
Software Release 4.1.2 introduces new CLI commands to manage Firewall and Access-Lists.
The following CLI commands have been introduced:
awplus(config)# firewall enable <VLAN id>
awplus(config)#
<service name>
access-list
<acl-id>
<action>
<IP
address/bits
of
netmask>
4.11.14.
Software Release 4.1.2 introduces a new CLI command to display the lease time of the local hosts served by CPE
DHCP server:
4.12.
4.12.1.
Software Release 4.1.1 introduces the support of the new model named iMG1525RF belonging to the iMG1500
families.
The iMG1525RF has the same characteristics as the iMG1525 model plus a Fiber-to-RF interface for CATV
applications.
The Fiber-to-RF interface acts as an additional pair of interfaces:
RF signal over fiber is received on the CATV fiber port located close to the WAN interface. Fiber connector is
SC/PC.
Page 50 of 102
Internally the optical signal is converted in RF analogue signals and transmitted to the RF interface (F connector)
located on the front of the unit.
AW+ CLI has also been extended to support the Enable/Disable of the RF interface. E.g.:
awplus(config)# interface catv
awplus(config-if-catv)# shutdown
or
awplus(config-if-catv)# no shutdown
awplus # show catv
References: CR 5437, CR 5203, CR 5313
4.12.2.
Software Release 4.1.1 introduces the support of the new model named iMG2524F belonging to the iMG2500 families.
The iMG2524F has the same characteristics as the iMG2524 model plus the capability to negotiate 100/1000Mbos on
the WAN (fiber) interface.
References: CR 5437, CR 5224
4.12.3.
Software Release 4.1.1 implements additional robustness checks on the configuration files:
during the download of a configuration file from a remote system (via TFTP, FTP or TR69), the iMG checks the
content of the file to search for the type of model. If the model type does not match the current iMG model type,
the configuration file is discharged in order to prevent wrong configuration file to be installed.
For debugging purposes, its possible to download any configuration file on the iMG adopting the
following criteria:
References: CR 5309
datamodel objects or attributes that are not recognized by the running iMG software version (for example
because generated by newer iMG software versions), are now skipped during the datamodel loading process
without causing a fallback into default_button.cfg or default.cfg configuration files.
Page 51 of 102
downgrades/upgrades software are now forbidden if the loaded image contains a software version that is older
than the minimum supported software version stored in the iMG personalization database. This feature avoids that
accidental software upgrades could load a software version not able to recognize the iMG model and therefore
making the system unusable.
References: CR 5303
UBOOT scripts are now versioned and visible in the configuration file under
InternetGatewayDevice.X_ALLIEDTELESIS_COM_SmokingGun.NvramParams and reported as :
the
object
4.12.4.
Software Release 4.1.1 extends the flexibility on dhcp client to handle different option-61 (dhcp client identifier) values.
When a dynamic (dhcp client) interface is configured on a vlan, by default, the dhcp client notifies as option-61 the
VLANID where the DHCP client is running followed by the iMG MAC address.
The DHCP client identifier option is the sequence of the following fields:
IAID (Identity Association Identifier RFC 4361 ) = VLANID
DUID (DHCP Unique Identifier RFC 3315)
o
DUID Type = Vendor-assigned unique ID based on Enterprise Number (fixed value)
o
Enterprise Number (IANA Assigned) = Allied Telesis, Inc (fixed value)
o
Identifier = iMG MAC Address
For backward compatibility with legacy iMG models, the DHCP client identifier can also be set to any custom
hexadecimal string.
4.12.5.
Software Release 4.1.1 extends the availability of the AW+ do command for all the sub-modes below the
Priviledged Exec mode.
Its therefore possible for example to execute any type of show commands from any sub-mode, especially useful
during configuration process to check the system status.
Also, the end command is now available for all the sub-modes below the Priviledged Exec mode.
References: CR 5060, CR 5191, CR 5311
Page 52 of 102
4.12.6.
Software Release 4.1.1 implements AW+ CLI for creating log files useful for technical support.
The technical support log file includes basic system information, the running and bootstrap configurations, a dump of
the persistent log and additional runtime information.
awplus(config)# show tech-support
awplus(config)# show tech-support all
The output of these commands is stored in a local TXT file that can be listed using the dir command and that can
be exported to a remote TFTP server via the copy command.
Also, from Software Release 4.1.1 its possible to display the content of the persistent log as messages are logged at
run time:
awplus# terminal [no] monitor
The content of the persistent log can also be displayed on the current CLI session by entering one of the following new
CLI commands:
awplus# show log
awplus# show log tail <number-of-tail-rows>
4.12.7.
Software Release 4.1.1 introduces AW+ CLI for software update module.
Its now possible to specify the IP address of the FTP server (and FTP credentials) and the FTP path where the
MD5SUM file is located.
Depending on the content of the MD5SUM file, its possible to download of a new software image and/or the
download of new configuration files(s).
awplus(config)# swupdate server <FTP_IP_Address>
awplus(config)# swupdate server-path <FTP_Path>
awplus(config)# swupdate username <FTP_login>
awplus(config)# swupdate password <FTP_password>
awplus(config)# swupdate now
awplus# show swupdate
Page 53 of 102
References: CR 4500
4.12.8.
4.12.9.
Software Release 4.1.1 introduces AW+ CLI for Switch FDB table.
Its now possible to display the switch FDB table with the indication about the vlan where each MAC address has been
registered and if MAC entries are dynamic or static (multicast).
awplus(config)# show mac address-table
awplus(config)# show mac address-table interface port1.0.x
awplus(config)# show mac address-table vlan xxx
awplus(config)# show mac address-table dynamic
awplus(config)# show mac address-table static
On Software Release 4.1.1 is not possible to configure the switch aging time neither is possible to
clear the switch FDB.
Page 54 of 102
References: CR 5042
4.12.10.
4.12.11.
Software Release 4.1.1 extends the AW+ CLI support for VoIP SIP Protocol configuration.
Its now possible to configure via CLI the following parameters (see Software Reference Manual for a complete
commands description):
Subscribe
Digitmap
References: CR 5239
Interdigit timeout
Ringing timeout
Caller ID
Page 56 of 102
Transmitting gain
Receiving gain
Jitter buffer
Fax/Modem detection
DTMF Relay
o
Supplementary Services
o
Caller ID On-Hook
Caller-ID on Call-Waiting
Call-On-Hold
4.12.12.
Software Release 4.1.1 extends the AW+ CLI support for VoIP MGCP Protocol configuration.
Its now possible to configure via CLI the following parameters (see Software Reference Manual for a complete
commands description):
References: CR 5236
Heartbeat
Piggyback
Endpoint syntax
Interdigit timeout
Ringing timeout
Caller ID
Page 58 of 102
Transmitting gain
Receiving gain
Jitter buffer
Fax/Modem detection
DTMF Relay
o
RFC2833 or InBand
Page 59 of 102
4.13.
4.13.1.
Software Release 4.1 introduces the support of two new models named iMG1525 and iMG2524 belonging to the
iMG1500 and iMG2500 families respectively.
These two new models run the iMG6xx VoIP stack supporting SIP and MGCP protocols.
4.13.2.
With Software Release 4.1 is also available VoIP SIP protocol for the iMG models that have POTS interfaces.
The following features are available under SIP protocol:
Basic registration and Authenticated registration via Digest and WWW methods
The following supplementary services are available and managed under SIP protocol:
Call On Hold
The following supplementary services are available and managed under SIP protocol using prefixes (or star codes):
Call Waiting
Warm Line
Hot Line
Country Tones
Digitmap
Page 60 of 102
Echo Cancellation
4.13.3.
With Software Release 4.1 is also available VoIP MGCP protocol for the iMG models that have POTS interfaces.
Both standard MGCP and NCS signaling protocol are supported.
The following features are available under MGCP protocol:
Heartbeat
Ring Splash
Distinctive Ringing
Country Tones
Echo Cancellation
4.13.4.
IGMP Snooping
Software Release 4.1 introduces the support for IGMP snooping Version 2 and Version 3.
IGMP snooping can be enabled on one vlan (vlan video) only and can be configured to work in Proxy Mode or Snoop
Only mode.
Detection of the Multicast Querier works only for deployment scenario where the WAN interface uses the fiber port
(default). Configurations where a LAN copper interface is used as WAN interface are not allowed for IGMP to work
properly.
4.13.5.
Software Release 4.1 extends port statistic counters (via TR69 only) also on iMG1500 family (previously were available
only on iMG2500 family).
The following MIB-II counters are available:
snmpIfInOctets
snmpIfOutOctets
snmpEtherStatsMulticastPkts
snmpEtherStatsBroadcastPkts
snmpEtherStatsOctets
snmpEtherStatsPkts
snmpEtherStatsTXNoErrors
snmpEtherStatsRXNoErrors
snmpIfHCInOctets_HI
snmpIfHCInOctets_LOW
snmpIfHCInUcastPkts_HI
snmpIfHCInUcastPkts_LOW
snmpIfHCInMulticastPkts_HI
snmpIfHCInMulticastPkts_LOW
snmpIfHCInBroadcastPkts_HI
snmpIfHCInBroadcastPkts_LOW
Page 62 of 102
snmpIfHCOutOctets_HI
snmpIfHCOutOctets_LOW
snmpIfHCOutUcastPkts_HI
snmpIfHCOutUcastPkts_LOW
snmpIfHCOutMulticastPkts_HI
snmpIfHCOutMulticastPkts_LOW
snmpIfHCOutBroadcastPckts_HI
snmpIfHCOutBroadcastPckts_LOW
snmpEtherStatsPkts64Octets
snmpEtherStatsPkts65to127Octets
snmpEtherStatsPkts128to255Octets
snmpEtherStatsPkts256to511Octets
snmpEtherStatsPkts512to1023Octets
snmpEtherStatsPkts1024to1518Octets
snmpIfOutDiscards
snmpIfOutErrors
snmpIfOutQLen
snmpIfInUnknownProtos
snmpIfInDiscards
snmpIfInErrors
snmpEtherStatsDropEvents
snmpEtherStatsUndersizePkts
snmpEtherStatsFragments
snmpEtherStatsOversizePkts
snmpEtherStatsJabbers
snmpEtherStatsCollisions
snmpEtherStatsCRCAlignErrors
4.13.6.
Software Release 4.1 introduces the possibility to mirror an interface (WAN or LAN) toward a LAN interface.
4.13.7.
Only for iMG1500 family, software release 4.1 introduces the capability to have the fiber WAN interface able to autonegotiate the speed from 100Mbps to 1000Mbps without any manual operation.
4.14.
4.14.1.
All the software modules are configurable by mean of TR69 configuration methods.
Most part of the objects and attributes defined in TR98 are supported in release 4.0. In addition to objects defined in
TR98, there are objects not defined by any standard and that are ATI proprietary.
The following TR69 methods are supported.
GetRPCMethods
SetParameterValues
GetParameterValues
GetParameterNames
SetParameterAttributes
GetParameterAttributes
AddObject
DeleteObject
Reboot
Download (for Firmware Image and Vendor Configuration File)
Upload (for Vendor Configuration File)
Software Release 4.0 supports ACS URL static configuration or dynamic discover via DHCP option 43.
Configuration of the TR69 module is available only via DHCP options or by TR69 datamodel manipulation (via
ACS/NMS).
There is no configuration support via AW+ CLI commands.
TR69 support
ACS URL
Supported
Not Supported
ACS Authentication
Supported
Not Supported
Periodic INFORM
Supported
Not Supported
CPE Authentication
Supported
Not Supported
Page 64 of 102
4.14.2.
AW+ provisioning
TR69 support
User creation/deletion
Supported
Supported
User password
Supported
Supported
User privilege
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
4.14.3.
WEB provisioning
Software Release 4.0 supports WEB interface for a limited set of operations.
Two level of WEB users are supported: Administrator and User.
The Administrator level allows a WEB user to upgrade the iMG software, upload and select new bootstrap
configurations.
User level allows only access to System Information page and few other status pages.
WEB user level is mapped to AW+ CLI privilege: AW+ CLI users with privilege 0-14 are set to the WEB level User;
AW+ CLI users with privilege 15 are set to the WEB level Administrator.
TR69 support
Supported
Page 65 of 102
4.14.4.
SNMP provisioning
Software Release 4.0 supports a limited set of SNMP public objects via SNMP v1/v2c.
Restart TRAPs (v2) are supported and battery backup unit lines status TRAPs are supported too.
TR69 support
Supported
Supported
Write community
Supported
Supported
Read community
Supported
Supported
TRAP receiver
Supported
Supported
System name
Supported
Supported
System location
Supported
Supported
System Contact
Supported
Supported
4.14.5.
Software Release 4.0 supports local access to AW+ CLI through USB console.
Access to the system AW+ CLI is performed via Telnet or SSH session over the USB interface. The default IP address
for the USB interface is 192.168.200.1
If the system is disconnected from the access network (WAN interface is down), access to the system AW+ CLI can
also being operated via Telnet or SSH through any LAN interface. The default IP address for the LAN interfaces is
192.168.2.1
4.14.6.
Software Release 4.0 supports the provisioning of all the 4 status lines from an external battery backup unit.
The system can generate SNMP TRAPs to signal the rising of an alarms or the clear of an existing alarm.
TR69 support
Supported
Not Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Page 66 of 102
4.14.7.
Software Release 4.0 supports the configuration of an external Reset/Default Button to recover the system to a well
known boot configuration.
The configuration assigned to the Default Button can be customized to any custom configuration and/or uploaded from
a remote TFTP server.
TR69 support
Supported
Supported
Supported
Supported
Not Supported
4.14.8.
Software Release 4.0 supports two full Main images: the first is used as bootstrap image while the second is used as
backup image.
When a firmware upgrade takes place, the backup image is overwritten by the new image and if the process terminates
correctly the backup image will be nominated as bootstrap image (and vice versa the existing bootstrap image will be
marked as backup image).
If during the system startup phase, the bootstrap image is invalid, the system automatically will attempt to run the
backup image.
Its possible to force the system to boot from any of the two images and then to upgrade the backup image.
TR69 support
Supported
Supported
Supported
Supported
Supported
Supported
4.14.9.
Software Release 4.0 supports multiple configuration files that can be created locally or can be uploaded from a
remote server.
Page 67 of 102
TR69 support
Supported
Supported
Supported
Supported
Not Supported
Supported
Not Supported
Supported
Not Supported
Supported
Supported
Supported
4.14.10.
Software Release 4.0 supports software upgrade via WEB interface (requires administrative WEB access level) or via
TR69 Upgrade method.
Its also possible to perform software upgrade from the debug CLI (not AW+ CLI) from a remote FTP or TFTP server.
Software upgrade can be used to upload a new Main image on the system and or to upload custom configuration files.
TR69 support
WEB support
Supported (via HTTP client)
Debug CLI
Supported
Supported
Supported
Page 68 of 102
4.14.11.
Software Release 4.0 supports Ethernet interface configuration via TR69 objects and via AW+ commands.
Its possible administratively disable/enable WAN (fiber) interface and LAN (copper) interfaces.
Its possible to force the speed and duplex mode (only for LAN interfaces) from 1000Mbps to 100Mbps to 10Mbps,
Full or Half duplex.
Its possible to enable/disable the generation of flow control frames.
Its also possible to gather MIB-II packets statistics for incoming and outgoing frames (only iMG2500).
TR69 support
Supported
Supported
Port Speed
Supported
Supported
Port Duplex
Supported
Supported
Supported
Supported
Port Counters
Supported
Supported
Not Supported
Not Supported
Not Supported
Not Supported
Not Supported
Not Supported
Not Supported
4.14.12.
Software Release 4.0 supports VLAN configuration and management over WAN (fiber) uplink interface and over LAN
(copper) interfaces.
The system is able to support up to 32 vlans and for each vlan its possible to assign an IP address (static or dynamic
via DHCP client) that will participate to the routing/ip-forwarding process.
The system supports port based vlan, vlan tagging and mixed configurations with untagged and tagged vlans on the
same interface.
Page 69 of 102
TR69 support
Vlan creation/deletion
Supported
Supported
Supported
Supported
Vlan tagging
Supported
Supported
Supported
Not Supported
4.14.13.
Software Release 4.0 supports port based rate limiting on WAN and LAN interfaces.
TR69 support
Supported
Not Supported
Supported
Not Supported
Supported
Not Supported
Supported
Not Supported
Not Supported
Not Supported
Not Supported
Not Supported
4.14.14.
Software Release 4.0 support DSCP prioritization over four Tx Queues (in weight priority mode).
Its possible to configure a DSCP priority MAP assigning for each of the 64 possible DSCP values the Tx Priority Queue
ID.
Software Release 4.0 support 802.1P prioritization over four Tx Queues (in weight priority mode).
Its possible to configure a 802.1P priority MAP assigning for each of the 8 possible 802.1P values the Tx Priority
Queue ID.
Only one prioritization scheme, DSCP or 802.1P, can be enabled at the same time.
Page 70 of 102
TR69 support
Supported
Not Supported
Supported
Not Supported
Supported
Not Supported
4.14.15.
IP bridging
Software Release 4.0 supports bridging between interfaces belonging to the same vlan at wire speed.
Multicast traffic is forwarded to all the interfaces belonging to the same vlan video. Interfaces that do not participate to
the video vlan are protected from multicast traffic.
Vlan crossing is only supported by mean of IP routing.
4.14.16.
IP routing
TR69 support
Static IP address
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Static routes
Supported
Supported
Not Supported
Not Supported
Not Supported
Not Supported
4.14.17.
DHCP Server
Software Release 4.0 supports multiple DHCP servers on local LAN interfaces.
Page 71 of 102
TR69 support
Supported
Not Supported
Supported
Not Supported
Supported
Not Supported
Not Supported
Not Supported
Not Supported
Not Supported
Not Supported
Not Supported
Supported
Not Supported
4.14.18.
Software Release 4.0 supports DNS Client for local system applications.
The list of external DNS servers can be configured statically or can be assigned dynamically from DHCP client
interfaces.
Software Release 4.0 supports also DNS Proxy for local hosts served by the system DHCP server(s).
The list of external DNS servers used by the DNS proxy can be configured statically or can be assigned dynamically
from DHCP client interfaces.
TR69 support
Supported
Supported
Supported
Supported
Supported
Not Supported
Supported
Not Supported
4.14.19.
Syslog
Software Release 4.0 supports syslog facility for most of the running software modules.
Page 72 of 102
Syslog can be redirected to a local buffer or a local file or to a remote syslog server.
Software Release 4.0 also supports semi-permanent logging: the local syslog file can keep syslog information across
warm restarts triggered by software reboots or watchdog restarts.
TR69 support
Supported
Supported
Supported
Not Supported
Supported
Supported
Supported
Supported
N/A
Supported
4.14.20.
NAT
TR69 support
Supported
Not Supported
Virtual Server(s)
Supported
Not Supported
4.14.21.
Firewall
Software Release 4.0 supports Firewall to inhibit/allow incoming/outgoing sessions through IP forwarding process.
TR69 support
Supported
Not Supported
Firewall portfilters
Supported
Not Supported
Firewall exceptions
Supported
Not Supported
Page 73 of 102
4.14.22.
Supported
Not Supported
SNTP
Software Release 4.0 supports Network Time Protocol to synchronize the system clock to an external NTP server.
TR69 support
Supported
Not Supported
Supported
Not Supported
Page 74 of 102
5.
5.1.
5.1.1.
5.1.2.
7591
Title
Notes
VOIP
7648
IGMP
CR ID
7637
5.1.4.
Notes
7621
CR ID
5.1.3.
Title
Title
Notes
AW+ CLI
CR ID
Title
Notes
7534
7483
7593
7521
7525
5783
Page 75 of 102
5.2.
5.2.1.
7545
5.2.2.
7346
7393
Title
Notes
Title
Notes
AW+ CLI
CR ID
5320
5.2.5.
SWITCH
CR ID
5.2.4.
Notes
SYSTEM
CR ID
5.2.3.
Title
Title
Notes
VOIP
CR ID
Title
Notes
7019
[Asterisk] No Ringback
7560
7526
7067,
7076,
7097,
7108,
7114,
7116,
7119,
7129,
7133
Page 76 of 102
5.3.
5.3.1.
5.4.
5.4.1.
Title
Notes
7320
7301
TR69 crash
7247
7292,
6609
6877,
6934
7289,
7325,
7339
Title
Notes
7153
7100
7035
7250
5.4.2.
VOIP
CR ID
5.5.
5.5.1.
Title
Notes
6935,
7148
6954
Noise on line
7198,
6955
7011
7027
5.5.2.
Title
Notes
6951
6912
6844
6910
6846
6971
Now upgrading from 4.2.3 to 4.3.2 the IP Address will not change
IGMP
CR ID
Title
Description
Page 78 of 102
5.5.3.
6926
IGMP improvements
6914
6922
HPNA
CR ID
6917
5.5.4.
6848
6772
Title
Description
Title
Description
VOIP
CR ID
6941,
6949,
6953
5.5.7.
SWITCH
CR ID
5.5.6.
Description
IPv6
CR ID
5.5.5.
Title
Title
Description
AW+
CR ID
6896
Title
Description
Page 79 of 102
5.6.
5.6.1.
5.6.2.
Title
Notes
4765,
6535,
6767
6799
6828
6560,
6561
6696
SWITCH
CR ID
Title
Notes
6851,
6854
6559
6669,
6646,
6647,
6693,
6797,
6801,
6650
6632
6247
5.6.3.
Title
Notes
6084
6159,
6601
Given a config with two 2 IPv6 WANside vlans the CLI returns an error
when adding an IPv6 route via the nondefault IPv6 gateway.
6183
6137,
6324
SIP
CR ID
5.6.5.
IPv6
CR ID
5.6.4.
Title
Notes
6874
6697
6803
6689
POTS
CR ID
Title
Notes
Page 81 of 102
5.7.
5.7.1.
6890
6377
6706
6833
5.7.2.
Title
Notes
6489
6441
6389
6149
6604
6131
6168
WEB Interface
CR ID
6427
Title
Notes
5.7.3.
6437
6530
6652
SWITCH
CR ID
Title
Notes
6614
6538
6393
6451
6420
6387
6417
6605
Page 83 of 102
5.7.4.
VOIP
CR ID
5.8.
5.8.1.
Notes
6329
5450,
5674,
6394
6369
6554
5659
6631
6621
6362
5.8.2.
Title
Title
Notes
6425
6370
6425
Voip SIP
CR ID
Title
Notes
Page 84 of 102
5.8.3.
6430
6405
6351
6423
6432
6563
Title
Notes
SWITCH
CR ID
6434
6410
6141
6113
6421
Page 85 of 102
5.8.4.
SYSTEM
CR ID
5.9.
5.9.1.
Notes
6428
6404
6390
6370
5.9.2.
Title
Title
Notes
6179
6204
6225
6249
6182
Voip SIP
CR ID
Title
Notes
6210,
6211
5870
6205
5.9.3.
5.10.1.
Title
Notes
6206
6302
6266
6285
5.10.2.
SWITCH
CR ID
5.10.
Title
5836
6184
6195
Notes
SYSTEM
CR ID
Title
6085
6166
6197
iMG1500 DDR clock setting are not correct and cause instability
execution instability
Notes
Page 87 of 102
5.11.
5.11.1.
SYSTEM
CR ID
5.11.2.
(internally 4.2_112)
Title
Description
5747
4713
4864
5485
4955
5480
5898
5792
5907
5843
5944
6163
SWITCH
CR ID
5424
Title
Description
5.11.3.
on x900
4851,
4776
5760
IGMP
CR ID
6141
5.11.4.
Title
Description
4366
5996
4864
DHCP
CR ID
4468
5.11.6.
Description
IP
CR ID
5.11.5.
Title
Title
Description
VoIP SIP
CR ID
Title
Description
5124
Wrong management of
X_ALLIEDTELESIS_COM_CallerIDTiming
attribute
5772
5777
6105
5.11.7.
Voip MGCP
CR ID
5.11.8.
Title
Description
4831
6101
VoIP Endpoint
CR ID
Title
Description
4704
5711
5902
6003
6152
6156
Page 90 of 102
5.12.
5.12.1.
5.12.2.
Title
Description
5263
5265
5537
5746
5678,
5606
5461
4579
SYSTEM
CR ID
Title
Description
5445
5722
5612,
5392
5393
5364
5.12.3.
5487
5456
5498
5546
5474,
5608
5304
5706
5526
5683
4932
SWUPDATE
CR ID
Title
Description
5431
5505
5389
5708
Page 92 of 102
5.12.4.
SWITCH
CR ID
5.12.5.
Title
Description
5360
5439
4851
5605,
5541
5522
5581
4862
5510
IGMP
CR ID
Title
Description
5540
5510
5524
5.12.6.
VoIP MGCP
CR ID
5.12.7.
Title
Description
5449
5285
VoIP SIP
CR ID
Title
Description
5610
5462
5598
5404
5246,
5301
5053
5769
Page 94 of 102
5.12.8.
VoIP Endpoint
CR ID
Title
Description
5714
5201
5483
5713
5736
5295
5348
5453
5454
5459
Page 95 of 102
5.13.
5.13.1.
5.13.2.
Title
Description
5328
5241
5370
5242
5448
5279
5271,
5032
SNTP
CR ID
Title
Description
5080
5280
5367
5.13.3.
QoS
CR ID
5.13.4.
Description
5254
5253
5.13.5.
Title
Title
Description
4760
5360
5136
IP
CR ID
Title
Description
5070
4923
5291
5.13.6.
5444
5385
5335
5206
5219
5228,
5230,
5341,
5229
5276
4391
SwUpdate
CR ID
5475
Title
Description
Page 98 of 102
5.13.7.
VoIP
CR ID
Title
Description
5340
5221,
5465,
5310
5257
5282
5286
5210
5209
5177
5208
5375
5376
5215
5222
5226
5227
5296
5324
Page 99 of 102
5406
5.14.
5.14.1.
5.14.2.
Title
4302
SWITCH
Title
Description
4603
4700
4855
4881
IGMP
CR ID
4386,
4431
5.14.4.
Description
4920
CR ID
5.14.3.
(internally 4.1_69)
Title
IGMP support
Description
DHCP Server
CR ID
4975
Title
Description