MALC Release Notes

Transcription

1 For software version Document Part Number: April 20, 2007 MALC Release Notes This document describes the MALC release and includes the following information: General information, page 1 New features, page 2 Upgrading or downgrading software, page 16 Problems fixed, page 9 Known issues, page 9 Contacting Global Service and Support, page 19 General information New upgrade procedure This document describes the new features, known issues, upgrading procedures and other aspects of the MALC release. Changes in this release include: After downloading the image files, running image flash, and performing file backups, use the systemreboot command to reboot the system with the upgraded software. This new upgrade process reduces the overall outage time when upgrading the MALC 100. See Upgrading system software higher than on page 17 for upgrade procedures. Note: When upgrading systems to or higher, the dump and restore method should not be used. The swupgrade command is supported when upgrading software from to or higher. Zhone Way 7001 Oakport Street Oakland, CA USA Copyright 2007 Zhone Technologies, Inc. 1

2 MALC Release Notes MALC 100 Web User Interface For release , the MALC 100 provides a MALC 100 Web User Interface that can be used to configure, test, and administer the MALC 100. The default login is admin and the default password is zhone. The default IP address for the MALC 100 Web User Interface is This release note provides a summary of the new MALC 100 features using the feature default settings and related information for this release. For more detailed information and procedures, see the MALC 100 Hardware Installation and Configuration Guide at: 100/ NEW FEATURES New features in The following new features and commands are included in the release. Only summary descriptions for each feature or command are provided. For more details on each feature and command, see the MALC 100 Hardware Installation and Configuration Guide. System features 2 MALC Release Notes

3 New features in GigE/media features Bridging features IP features Voice features System features Annex B MALC 100 supports the Annex standard, Annex B (ADSL over ISDN). The supported line rate for ADSL2+ Annex B is: 20 Mbps downstream 1 Mbps upstream onreboot restore not required on or higher Systems running version or higher no longer require the set2default command to build the restore file when performing software upgrades. After downloading the image files and running image flush, use the systemreboot command to reboot the system with the upgraded software. See Upgrading or downgrading software on page 16 for the latest upgrade procedures. onreboot directory The onreboot directory is now available by default and does not need to be created manually. restore file validation The restore command now supports an option to validate a restore file. It parses through the file and provides indications of whether the restore file is syntactically valid. zsh> restore validate <filename> systemreboot verification When the systemreboot command is issued, the MALC 100 checks for the existence of the onreboot/restore file. If the is file is located, a warning message displays on the console to confirm that you want to install the restore database file. zsh> systemreboot A restore file (/onreboot/restore) is present. MALC Release Notes 3

4 MALC Release Notes A system reboot will result in a database restore. Continue? (yes or no) [no]: yes set2default validation When the set2default command is issued, the MALC 100 checks for the existence of the onreboot/restore file. If the file does not exist a warning message will is displayed on the console to confirm that you really want to set the system to default with the restore file. zsh> set2default No restore file (/onreboot/restore) found. Setting to default will result in an empty database. Continue? (yes or no) [no]: yes del command Deletes a file from the flash card file system as well as directories and multiple files. Note: This command can be used to delete all the Web User Interface files if needed. zsh> del -rv filename directoryname * -rv: Recursively deletes files and subdirectories. The v is optionally used for verbose mode so the names of the files being deleted are printed out. This option is not allowed from the root directory. Note: This option is not allowed from the root directory. GigE/media features filename: Full path name of the file to delete. directoryname: Full path name of the file to delete. *: Specifies a wildcard so all files in the current or specified directory are deleted. This option is not allowed from the root directory p priority queuing The MALC 100 supports 802.1p priority queuing on the MALC-UPLINK-GE uplink and on unicast connections on the ADSL-48 downlink. 4 MALC Release Notes

5 New features in Table 1: COS/TOS mapping COS TOS Zhone 802.1p Priority QoS Description Default - best effort background, routine spare, immediate excellent effort controlled load video (<100ms) voice (<10ms) network control Bridging features PPPoA - PPPoE interworking Upon detecting PPPoA traffic, the MALC 100 initiates a PPPoE session with the Broadband Remote Access Server (BRAS). PPP traffic between the CPE and the BRAS is tunneled over this PPPoE session. The MALC 100 autosenses the type of PPPoA encapsulation as either VCMUX or LLC. bridge add /adsl vc 0/35 td downlink vlan 500 pppoa zsh> get bridge-interface-record adsl-0-35/bridge ispppoa: > {true}: (enables the PPPoA session) Note: The following message may appear if the CPE device is not properly configured for PPPoA connections. FEB 01 15:59:22: error : 1/1/9 : bridge: _afsmchkrcvencaps(): l=1811: tnettask: AFSM-6313: port adsl-0-35 misconfigured for PPPoA Display the bridge data. The new states available for PPPoA interworking are: READY-Waiting for PPPoA packet to initiate PPPoE discovery and DISCVRY -PPPoE discovery initiated. Waiting for session ID to be obtained. The A indicates a PPPoA port. When the PPPoA port status is UP, the BRAS MAC address and PPPoE session ID are also displayed. zsh> bridge show VLAN Bridge State Table Data Tagged ethernet2/bridge UP S Global default [U: 3600 sec, M: 120 sec, I: 60 sec] adsl-0-35/bridge UP A 00:19:aa:3b:83: MALC Release Notes 5

6 MALC Release Notes adsl-0-35/bridge PENDING adsl-0-35/bridge READY A zsh>bridgeshow ports ispppoa Yes, ahdl 0x6e6ac90, encapllc No The bridgeshow ports command displays the following new fields: is PPPoA- indicates if interface is PPPoA or not, ahdl- for PPPoA interfaces, displays the handle address to PPPoA (otherwise, 0x0), encapllc-shows Yes if PPPoA encapsulation is LLC or No for VCMU encapsulation. PPPoE intermediate agent The MALC 100 supports inserting port information into PPPoE packets that transit a MALC 100 bridge interface. When the MALC 100 receives a PPPoE Active Discovery Initiation (PADI) packet or a PPPoE Active Discovery Request (PADR) packet, the MALC 100 can be configured to insert a customized string along with default port/slot identification into the vendor-specific portion of the PPPoE packet. The customized identification string can be 0 to 48 characters. The inserted information is formatted as: <customstring> eth slot/port[[:stagid]:vlan-tag] The slot/port values identify the ingress slot/port on the MALC 100 where the packet was received. If the packet is tagged with a VLAN tag, the VLAN tag is also added to the packet on ingress. If the packet is tagged with a SLAN tag, the SLAN tag is also added to the packet on ingress. Untagged packet no customized string from slot 5 port 2: eth 5/2 VLAN 500 tagged packet no customized string from slot 5 port 2: eth 5/2 :500 VLAN 500 tagged, SLAN 4 tagged packet no customized string from slot 5 port 2: eth 5/2 :4 :500 VLAN 500 tagged, SLAN 4 tagged packet with customized string of from slot 5 port 2: eth 5/2 :4 :500 Note: For configurations with bridge intralinks or subtended MALC/ Raptor 100 devices, ensure that the PPPoE intermediate agent feature is enabled on only the subtended devices. Bridge configuration records for the intermediate agent options are assigned to bridge configuration groups on downlink bridge interfaces. Each bridge configuration record contains settings for type and value. The bridgeconfigtype parameter specifies the bridgeinsertpppoevendortag option to enable the intermediate agent feature. The bridgeconfigvalue parameter specifies the 0 to 48 character customized string to insert into PADI and PADR packets. Configure a new bridge-config-record for group1/instance1 and specifies the option to insert a PPPoE vendor tag with a customized prefix of Malc MALC Release Notes

7 New features in zsh> new bridge-config-record 1/1 bridgeconfigtype: --> {bridgeinsertoption82}: bridgeinsertpppoevendortag bridgeconfigvalue: -> {}: Malc123 zsh>bridgeshow ports... pppoetransitaddfail 0 zsh>bridge add /adsl vc 0/35 td 1 config 1/1 Use the config parameter of the bridge add command to create a bridge with the assigned bridge-config-record of group 1 instance 1. The bridgeshow ports command displays a new field for pppoetransitaddfail to help track the data insertion failures. bridge flush all command The bridge flush command now supports the all option. Caution: This will cause service interruption and cause all MALC 100 addresses to be relearned. IP features customdhcp setting By default, for uplink bridges the customdhcp setting is true. This enables broadcast DHCP broadcast packets to be switched from uplinks to downlinks by default for uplink bridge interfaces. dhcp-relay command zsh> dhcp-relay add ptm2/ip Created DHCP Relay Agent number 7 The dhcp-relay command creates, modifies, and deletes the dhcp-server-subnet profile for quick access to setting relay agent and external server settings. dhcp-relay add [<subnetgroup>] <ip-address> [<interface>/<type> NULL] zsh> dhcp-relay show subnetgroup external-server network address/mask / / / / MALC Release Notes 7

8 MALC Release Notes / zsh> dhcp-relay modify Updated DHCP Relay Agent number 6 zsh> dhcp-relay delete 5 Deleted DHCP Relay Agent number 5 Voice features T.38 fax T.38 fax service is supported between two MALC 100 devices configured for SIP VoIP. If one side is not configured for T.38, the fax call reverts to g.711 pass through when this option is configured.otherwise, the fax may not go through. By default, T.38 fax service is disabled. T.38 service options are either t38udptl or t38none. t38udptl enables T.38 service using UDP IP packets. t38none disables the service. t38rtp option is currently not supported. Configure the T.38 option with the voice add command. The subscriber-voice-voip profile settings are updated based on the command options. voice add pots /voicefxs voip 1/6 ethernet1/ip dn name codec g729a t38fax t38updtl reg 1 voice show command A new option for verbose (-v) output has been added. The Voice Prof Id has been removed from non-verbose output. A new option is available to show voice connection data for a single connection. zsh> voice show -l /voicefxs Subscriber end-point Remote end-point STA /voicefxs uplink4-0-32/ip DN ENA voice add command The voice add command supports the framesperpkt parameter to specify the number of frames per packet for a voice connection. The valid range is 1 to 7 packets. voice add pots /voicefxs voip ethernet2-200/ip dn name pw password plar framesperpkt 1 Created subscriber-voice 1/4/48 Created subscriber-voice-pots 95 Created subscriber-voice-voip 96 8 MALC Release Notes

9 Problems fixed Problems fixed Problems fixed in Bridge video shows the downlink in PENDING instead of the DOWN state. When changing ADSL mode from fastonly to interleavedonly, traffic is no longer able to pass. Modem MAX rate is 9600 Baud Rate with SIP-PLAR on MALC 100. Modem MAX rate is 9600 Baud Rate with MGCP on MALC 100. When bridging high-throughput data traffic, a linear topology should be used and not RPR. Routed data can be used on RPR topology without limitations. It is recommended that bridged video be used in a linear uplink configuration and not in RPR. Routed video can be done with RPR configuration. MALC 100 and MALC devices should not be used as ring nodes in the same RPR ring.it is recommended that MALC 100 devices be subtended. Ringback does not play to the transferring party on a blind transfer. When calling your own number, there is no busy tone indicator heard. Metaswitch MGCP: A blind transfer gets disconnected. Metaswitch MGCP: There are no continuous rings while blind transfer is in progress. Tekelec T6000 MGCP: There is no busy tone heard when calling yourself. Known issues General Known Issues with an asterisk (*) are new to this release. *An inforserv error message is created after set to default. *SELT/DELT results are not accurate. MALC Release Notes 9

10 MALC Release Notes Bridging *When using Coppercom, a non-t.38 to T.38 fax does not work. *When using the WebUI, are unable to modify voice connections after they are added. TR *The MALC-100 fails to SIP-register with the Nortel PGI softswitch. PVC statistics incorrectly reporting that traffic is inactive. No Ethernet status lights appear lit in RPR mode. You can only perform a lookout operation when running a metallic line test. The line test function does not support the lookin feature. When you modify the ADSL alarm profile in ZMS, the ASDL connection goes down for 30 seconds. The OAM F5 segment ATM Ping function is not supported. DSL *MALC 100 does not prevent the user from creating VLAN 4095 even though it is an internal reserved VLAN. *The MALC 100 can only support 128 downlink bridges. * For bridged video, bridge statistics are not available via SNMP. * Bridged video does not work when using a default vlan bridge-path. MALC 100 only supports 1024 bridges. TR * On Canadian 911 Calls MALC 100 has to play on the RTP port back to the operator. watchdog wrong error appears on CPE when trying to train on longer loop. CPE must be reset or restarted, broken data path of ZOI may be an indication a CPE has encountered this error. SELT tests incorrectly run to completion with the CPE connected, and DELT tests incorrectly run to completion without the CPE connected. 10 MALC Release Notes

11 Known issues As shaping rate approaches train rate, a reduction in throughput occurs on a per port basis: MALC 100-ADSL-24 MALC 100-ADSL-32A MALC 100-DS3/E3-4 MALC 100-G.SHDSL MALC 100-SHDSL-48 MALC 100-G.SHDSL-4W-12 MALC 100-ReachDSL-24 MALC 100-T1/E1-ATM-32 Ethernet * Traffic routed through an interface with TOS/COS/SCOS defined do not tagged. * COS/TOS: COS/TOS is not supported on PPPOA/PPPOE connections. * COS/TOS: Bridge egress packets are not tagged with cos/scos when it is configured. * Unable to delete an ip interface configured for QinQ. * COS/TOS does not work with video running on same connection as data. Multiple intralink bridges are not supported. Data traffic works only if one intralink is configured. GigE: Mcast control list with connections is referencing it can be deleted. IP * Numerically named ip-interface-records are not recognized by the delete command. MALC 100 does not respond to DHCPINFORM. Video Bridged Video: Multicast counters are incorrect on GigE/RPR physicals. MALC 100 does not support multiple PVCs with bridged video. Bridged video does not work when using a default VLAN bridge-path. MALC Release Notes 11

12 MALC Release Notes Voice *When using Annex A and Annex B, the SIP server and Broadsoft call waiting caller ID tone heard in the voice path. *When using Annex A and Annex B the disconnect and reconnect uplink does not recover voice path between two MALC 100 s. *When using Coppercom SIP, Annex A and Annex B will get a fast busy when call waiting caller hangs up. *When using Sylantro 3-way conference calls do not end with the originator (Cisco SIP phone) hangs up. *IP TOS values in voip-server-entry is inconsistent with the ip-interface-record. *RTP picks up TOS from voip-server-entry and COS/SCOS from source ip-interface-record. *Annex A SIP PLAR V52, are unable to disconnect calls ccrp terms are NULL. *G3 fax machines are not supported with T.38 protocol. *For metaswitch SIP 4.2 M100, there is no ringback on a blind transfer Release.Tekelec T9000 MGCP: There is a combination of a voice path and a ringback heard while a call transfer is in progress Release. Tekelec T9000 MGCP: Ringback continues to sound after three-way call conferencing is initiated. If you want to use the call park (*98) feature on a Sylantro softswitch, you must create a custom dial plan. Contact Zhone GSS for information on setting up custom dial plans. The ring generator feature does not support all countries displayed in the country list in the system 0 profile. Continuous ringback is heard during the setup of a call transfer and a three way call. IP logical statistics are incorrect on interfaces with active traffic. Unable to transfer calls using Comm Pilot Manager. 12 MALC Release Notes

13 Known issues MALC 100 does not support SCA (Shared Call Appearance) features. Voice path interrupted while RPR GigE SWACT is processing. Existing V52 user ports and existing GR303 CRVs are not appearing in ZMS. Ringback does not play to the transferring party on a blind transfer. MALC 100 does not talk to MetaSwitch when voice connections are provisioned against RPR interface on the head-end node. Proper cadence is not always heard on first ring. Voice add voip command fails with floating IP interface causing no dial tone on these lines. Enabling local call conferencing results in incorrect flashing to 3-way conferencing and not between conversations. Speed Dial 100 is not working correctly. The MALC 100 treats the default prefix of '#' as the end of the dial string. Workaround: Change the prefix to a digit or an asterisk (*) and Speed Dial works. There is a two-second delay on dial tone with the Voice Gateway ESA cluster. Every time a ground start telephone goes into an off-hook state, an error message is generated even though operations work properly. A sample view of the error message is JUL 25 15:07:20: error : 1/2/1077: rp303: Unexpected CAS event from ZCCAPI 6 in ACTIVE JUL 25 15:07:20: error : 1/2/1077: rp303: State machine error. State:0 ig:0 crv:2001 JUL 25 15:07:20: error : 1/2/1077: rp303: q3stateredupdatetorpevent() failed Ground Start: In a far end disconnect to the local line, it may take as long as 3 seconds for dial tone. Voice-Megaco MEGACO: Telephone keeps ringing if made Admin Down while it is ringing. Voice-MGCP * MetaSwitch MGCP 4.2: Screeching noise during first ringback. MALC Release Notes 13

14 MALC Release Notes Voice-POTS * After swact on busy system, uplink card says redundancy ready, but not really ready for 5-10 minutes later. * NORTEL CS2K MGCP: No reminder ringing on hanging up after hookflash. * MGCP: There is an unusual noise heard when phone is going offhook after a reminder ring. * Metaswitch MGCP 4.2: DTMF does not work. * METASWITCH-MGCP: No voicepath after caller hold re-ring, For MGCP and MEGACO calls, the MALC 100 ignores the preferred-codec setting and selects the codec from a list provided by the MGCP server or media gateway controller. MGCP: No ringback tone is heard after MTAC ringer goes down. MGCP: POTS line permanently busy after MTAC ringer reboots. T9000 MGCP: Reminder ring does not work when a party hangs up and the call is already on a conference/hold state. T9000-MGCP: A DSP error message is generated and there is no call waiting indication when a second call-waiting call is made. On a T6000-MGCP softswitch there is no tone to indicate a call is on hold. Voice-SIP Auto attendant works intermittently in detecting DTMF with the MALC 100 is set to use RFC2833 with G.711. POTS reports incorrect endpoint statistics on POTS-VoIP voice connections. DTMF does not always work on voice mail. * Codec Negotiation issue between the MALC 100 and the Cisco ATA while fax is in progress. * Asterisk/Sylantro: Blind Transfer gets no RingBack. 14 MALC Release Notes

15 Known issues * Sylantro SIP: Call waiting call drops when a party on hold does a hookflash to take it. * SIP, SIPExpress: no reminder ring after call waiting. * Coppercom SIP: After blind transfer, ring back continues on the transfer. * Broadsoft/T38: SuperG/pc modem fax call uses G711 instead of T38 for fax * Broadsoft: DTMF tones are sometimes distorted on a local conference call. * Broadsoft /T38: SuperG/pc modem fax call uses G711 protocol instead of T38 for faxing. * Broadsoft / Local Conferencing: voicepaths dropped after RPR GigE SWACT. * SIP SER & Broadsoft: Excessive SIP 200 okay message being replied by MALC 100 during T.38 negotiation. * Local conferencing: no voicepath for remaining lines after first line is released. * SIP-PRI: Can not re-configure isdn-signaling. * SIP: Phones loose server on "update ip-interface-record". * Metaswitch SIP 4.2/Sylantro/SIPExpress/Asterisk: 3-way conf initiation at the third party ringing fails. *SIP PRI: subscriber terms get messed up after systemreboot on E1 type VG. * Coppercom SIP: Non T38 to T38 fax does not work. * T38 compatibility with CopperCom: Softswitch was unable to response to T38 request. SIPSTACK error message appears when changing from a primary application server to the Session Border Controller domain name. ESA information is inconsistent: When ESA is active, SIPSTACK ESA shows ESA ON. But, the voice status shows voice connections listed as ESA OFF. SIP: There is no Visual Message Waiting Indicator, but stutter dial tone is played when a voic is waiting. MALC Release Notes 15

16 MALC Release Notes Voice-SIP PLAR Voice SIP: Phones do not get registered after making a password change on the VoIP server. Three-way conferencing in SIP does not work if initiated at the time of the third-party ringing. ZMS * VG card doesn't support redundancy ready log message. SIP-PLAR: Dial-up modem does not connect reliably at some baud rates. Voice Gateway system statistics incorrectly reports calls running SIP-PLAR. TR ZMS reports the wrong optics information, LX instead of the correct SX, in the Media Type field. Limitations and features not supported in this release The following features are not currently supported: CLI-scripted provisioning. DS3 test patterns. G.726 voice compression codecs are not supported for VoIP. SNMP sets and walks from the CLI. Upgrading or downgrading software This section explains how to back up configurations, upgrade, and downgrade the MALC 100 software. Backing up the configuration Back up your configuration using the dump command. The command uses the following syntax: dump network [host filename] To back up the configuration to the network: 16 MALC Release Notes

17 Upgrading or downgrading software 1 Create the file in the destination location of the TFTP server and make it writable. 2 Save the configuration. The following example saves the configuration to a file named m100.cfg on the host : zsh> dump network m100.cfg Upgrading system software higher than Note: This procedure is only valid if you are upgrading from a release and before a release, or if you are upgrading with a non-redundant system. Note: If the database includes customer renamed profiles that include parentheses (), the parentheses will be replaced with a dash - when the device is upgraded to All other characters of the name are preserved. Note: If asymmetrical traffic descriptors were configured using ZMS, contact GSS for upgrade assistance before upgrading a MALC 100 from 1.12.x to 1.13.x or later. To upgrade the system software: 1 Create the onreboot directory if one does not already exist, and back up the current configuration file to the onreboot directory. Return to the root directory. zsh> mkdir onreboot zsh> cd onreboot zsh> dump file restore zsh> cd.. This file will be used to restore the system configuration or revert to a previous release, if desired. The restore file can be validated using the restore validate <filename> command. 2 Copy the new system boot image software to the flash memory using the image download command. zsh> image download m100adsl2pgige.bin where is the TFTP server, and r100adsl2pgige.bin is the name of the file of the earlier version of software. 3 Use the file upload command to copy the infotbl.v7 and infotbl.v7.old files to an external device. > SH> cd datastor > zsh> file upload infotbl.v7 infotbl.v7. > File upload successful MALC Release Notes 17

18 MALC Release Notes > zsh> file upload infotbl.v7.old infotbl.v7.old File upload successful 4 Use the systemreboot command to reboot the system with the new configuration: zsh> systemreboot The system reboots again with the new configuration. This may take several minutes to complete. 5 Restore the configuration that was backed up using the restore network command. For example: zsh> restore network m100.cfg Note: When upgrading systems to or higher, the dump and restore method should not be used. The swupgrade command is supported when upgrading software from to or higher. Note: After upgrading, if you are using ZMS, perform a full config sync to ZMS. Upgrading the system software lower than To upgrade the system software from a release lower than , first upgrade to See the MALC Release Notes for upgrade instructions. Downgrading the software For unplanned downgrades, contact Zhone GSS before preforming the downgrade procedures. The procedure to downgrade the software version is identical to the upgrading procedure, except the system boot image is the older release in the image download syntax: zsh> image download [old image] 1 Back up your configuration using the dump command. The command uses the following syntax: dump network [host filename] To back up the configuration to the network: a Create the file in the destination location of the TFTP server and make it writable. 18 MALC Release Notes

19 Contacting Global Service and Support b Save the configuration. The following example saves the configuration to a file named m100.cfg on the host : zsh> dump network m100.cfg 2 Download the earlier version of software to the flash memory using the image download command. For example: zsh> image download m100adsl2pgige.bin where is the TFTP server, and m100adsl2pgige.bin is the name of the file of the earlier version of software. 3 Use the file upload command to copy the infotbl.v7 and infotbl.v7.old files to an external device. > SH> cd datastor > zsh> file upload infotbl.v7 infotbl.v7. > File upload successful > zsh> file upload infotbl.v7.old infotbl.v7.old File upload successful 4 Erase the previous system configuration and restore the factory default settings of the newly downloaded software: zsh> set2default 5 Restore the configuration that was backed up using the restore network command. For example: zsh> restore network m100.cfg Note: After upgrading, if you are using ZMS, perform a full-config-sync to the ZMS. Contacting Global Service and Support Technical support Contact Global Service and Support (GSS) if you have any questions about this or other Zhone products. Before contacting GSS, make sure you have the following information: Zhone product you are using System configuration Software version running on the system Description of the issue If you require assistance with the installation or operation of your product, or if you want to return a product for repair under warranty, contact GSS. The contact information is as follows: MALC Release Notes 19

20 MALC Release Notes Service requirements Telephone (North America) 877-ZHONE20 Telephone (International) Internet If you purchased the product from an authorized dealer, distributor, Value Added Reseller (VAR), or third party, contact that supplier for technical assistance and warranty support. If the product malfunctions, all repairs must be performed by the manufacturer or a Zhone-authorized agent. It is the responsibility of users requiring service to report the need for service to GSS. 20 MALC Release Notes