Académique Documents
Professionnel Documents
Culture Documents
DISCLAIMER
ALCATEL makes no representation or warranties with respect to the contents hereof and specifically
disclaims any implied warranties or merchantability or fitness for any particular purpose. Further, ALCATEL
reserves the right to revise this publication and to make changes from time to time in the content hereof
without obligation of ALCATEL to notify any person of such revision or changes.
ii
Table of Contents
Compatibility ..................................................................................................................................................................6
9500 MXC Hardware Supported.........................................................................................................................6
iii
Software Release Notes, Version 4.0
• Alcatel Customers
• Alcatel Value Added Resellers
• Alcatel Value Added Service Providers
• Alcatel Product Support staff
• Alcatel Field Service staff
Software Introduction
This software has been made available for customer release. In addition to previously supported
hardware and functionality it now provides additional support for:
The following table lists the software details for this release.
Supported Functionality
The following headings list functionality that is currently supported by version 4.0 embedded and CT
software. New functionality is highlighted in bold italics.
Configuration
Populate information fields such as terminal name, site name, etc
View expected plug-in layout
Configure frequency, power, modulation and capacity
Configure tributary interface parameters
Configure DAC ES ports
Configure circuits
Configure IP routing
Set radio date and time
Manage software versions and download
View active license and download license
Configure ring protection
Configure dynamic routing
View equipment part numbers and serial numbers
Configure custom T/R splits
Configure trap destinations
Configure XP4 compatibility mode
Configure ring wrap and unwrap criteria
Configure system function names
Configure ring unwrap time
Configuration backup & restore
Link aggregation for DAC GE
RWPR for DAC GE
• Layer 1 link aggregation with redundancy
E1/DS1 backplane for DAC GE
Status forwarding for DAC GE
DAC GE - Generic L2 Link Aggregation and Enhanced VLAN usability
E1 performance monitor
Diagnostics
Activate tributary/AUX line facing loop back
Activate tributary/AUX radio facing loop back
3DB 23102 AEAA, 15 September 2007 Page 3
Software Release Notes, Version 4.0
Protection Support
Equipment protection supported
Hitless path protection supported
Unidirectional ring protection supported
Optical tributary protection supported
IDU 300 20x v2 Hot Standby Non-Protected Tributary
Miscellaneous Features
Manufacturing details supported
Watch dog supported
ATPC supported
CT auto-version supported (upload CT from radio)
Soft reset without interrupting traffic
As-built report supported
Data file to send to Help Desk
Launch new CT session for remote terminal
Alarms
Alarm hierarchy supported
User configurable alarm thresholds
Alarm I/O supported
Logs
Event log operational
Informational event log entries
Event log notes
Security
Features controlled by license key
CT user security
Software Loading
Software loading – internal users only
Software loading – customer usable
CT Help
Customer support details
About CT
CT integration with alarm troubleshooting entries
Compatibility
It is important to note that while the hardware is supported by the software the hardware option may
not exist at this time.
3DB23026AAAA
3DB23026ABAA
3DB23026ACAA
3DB23026ADAA
3DB23026AEAA
3DB23026AFAA
3DB23027AAAA
3DB23027ABAA
3DB23028AAAA
3DB23028ABAA
3DB23028ACAA
3DB23028ADAA
3DB23028AEAA
3DB23028AFAA
3DB23028AGAA
3DB23028AHAA
3DB23028AIAA
3DB23028AJAA
3DB23028AKAA
3DB23028ALAA
3DB23028AMAA
3DB23028ANAA
3DB23028AOAA
3DB23028APAA
3DB23028AQAA
3DB23028ARAA
3DB23028ASAA
3DB23028ATAA
3DB23184AAAA
3DB23185AAAA
3DB23186AAAA
3DB23186ABAA
3DB23186ACAA
3DB23186ADAA
3DB23188AAAA
3DB23188ABAA
3DB23188ACAA
3DB23188ADAA
3DB23189AAAA
3DB23189ABAA
3DB23189ACAA
3DB23189ADAA
3DB23189AEAA
3DB23189AFAA
3DB23029AAAA
3DB23029ABAA
3DB23029ACAA
3DB23029ADAA
3DB23029AEAA
3DB23029AFAA
3DB23030AAAA
3DB23030ABAA
3DB23030ACAA
3DB23030ADAA
3DB23031AAAA
3DB 23102 AEAA, 15 September 2007 Page 8
Software Release Notes, Version 4.0
3DB23031ABAA
3DB23031ACAA
3DB23031ADAA
3DB23031AEAA
3DB23031AFAA
3DB23032AAAA
3DB23032ABAA
3DB23032ACAA
3DB23032ADAA
3DB23033AAAA
3DB23033ABAA
3DB23033ACAA
3DB23033ADAA
3DB23034AAAA
3DB23034ABAA
3DB23034ACAA
3DB23034ADAA
3DB23255AAAA
3DB23255ABAA
3DB23255ACAA
3DB23255ADAA
3DB23255AEAA
3DB23255AFAA
3DB23255AGAA
3DB23255AHAA
3DB23255AIAA
3DB23255ALAA
3DB23255AMAA
3DB23255ANAA
3DB23261AAAA
3DB23261ABAA
3DB23261ACAA
3DB23261ADAA
3DB23035AAAA
3DB23035ABAA
3DB23035ACAA
3DB23035ADAA
3DB23035AEAA
3DB23035AFAA
3DB23035AGAA
3DB23035AHAA
3DB23036AAAA
3DB23036ABAA
3DB23036ACAA
3DB23036ADAA
3DB23036AEAA
3DB23036AFAA
3DB23036AGAA
3DB23036AHAA
3DB23037AAAA
3DB23037ABAA
3DB23037ACAA
3DB23037ADAA
3DB23038AAAA
3DB23038ABAA
3DB23038ACAA
3DB 23102 AEAA, 15 September 2007 Page 9
Software Release Notes, Version 4.0
3DB23038ADAA
3DB23038AEAA
3DB23038AFAA
3DB23039AAAA
3DB23039ABAA
3DB23039ACAA
3DB23039ADAA
3DB23039AEAA
3DB23039AFAA
3DB23040AAAA
3DB23040ABAA
3DB23041AAAA
3DB23041ABAA
3DB23041ACAA
3DB23041ADAA
3DB23041AEAA
3DB23041AFAA
3DB23042AAAA
3DB23042ABAA
3DB23042ACAA
3DB23042ADAA
3DB23042AEAA
3DB23042AFAA
3DB23042AGAA
3DB23042AHAA
3DB23062ACAA
3DB23062ADAA
3DB23043AAAA
3DB23043ABAA
3DB23044AAAA
3DB23044ABAA
3DB23044ACAA
3DB23044ADAA
3DB23044AEAA
3DB23044AFAA
3DB23045AAAA
3DB23045ABAA
3DB23045ACAA
3DB23045ADAA
3DB23045AEAA
3DB23045AFAA
3DB23045AGAA
3DB23045AHAA
3DB23259AAAA
3DB23259ABAA
3DB23259ACAA
3DB23259ADAA
3DB23259AEAA
3DB23259AFAA
3DB23213AAAA
3DB23213ABAA
3DB23213ACAA
3DB23213ADAA
3DB23213AEAA
3DB23213AFAA
3DB23258AAAA
3DB 23102 AEAA, 15 September 2007 Page 10
Software Release Notes, Version 4.0
3DB23258ABAA
3DB23258ACAA
3DB23258ADAA
3DB23258AEAA
3DB23258AFAA
3DB23258AGAA
3DB23258AHAA
3DB23258AIAA
3DB23258ALAA
3DB23258AMAA
3DB23258ANAA
The following table details the minimum hardware specifications required to operate CT.
Note: ATI video cards installed with a ‘Catalyst driver’ set earlier than 4.9 will cause the CT
performance page to stop working if the screen-saver activates. The workaround is to install the
latest video drivers from the video card manufacturer.
Albanian, Belarusian, Bulgarian, Catalan, Croatian, Czech, Danish, Dutch, English, Estonian,
Finnish, French, German, Greek, Hebrew, Hungarian, Icelandic, Italian, Japanese, Korean, Latvian,
Lithuanian, Macedonian, Norwegian, Polish, Portuguese, Romanian, Russian, Serbian, Serbo-
Croatian, Slovak, Slovenian, Spanish, Ukrainian.
Arabic The calendar does not display the day of the week correctly
Chinese The date format is not consistent in event browser, the calendar does not
display the day of the week correctly, and the alarms page is larger than 800 x
600 resolution
Hindi The alarms page is larger than 800 x 600 resolution
Swedish Commas are displayed instead of decimal points when entering the TR/RX
spacing and TX/RX frequency. CT will accept commas when the user enters
TX/RX frequency, however it will not accept commas for the TX/RX spacing.
The workaround is to use decimal points.
Thai Alarms page is larger than 800 x 600 resolution
Turkish Some event log entries in the event browser and link history pages may not be
displayed
9500 MXC software has been successfully tested with the following NTP time servers.
• NetTime
722 G.826 performance statistics were previously not available for a 1+1
protected link. The statistics now record the performance of the protected
link and not the performance of the individual receivers. Further refinement
of this feature is expected in a later software release.
1829 The DAC ES experienced frame check sequence errors for large packets
when configured for 48xE1 operation.
722 G.826 performance statistics are now available for the combined link and the
off line receiver in a 1+1 protected link.
2402 In a ring, when there is a protected radio or tributary connection to the ring,
this connection would fail to carry traffic.
1738 In an IDU protected system, transmit switching on LOS is now blocked if both
IDUs simultaneously get LOS. This means that a LOS fault on the other side
of a tributary Y cable will no longer cause a transmit switch.
2140 If an IDU 300 ES is connected in a link to an INU, and the INU routes C1 and
C2 to different paths so that they have different end points, then the IDU 300
ES would receive incoming Ethernet errors.
2154 Link status propagation was not working for Layer 2 Aggregation.
1805 Using a DAC 4x it is now possible again to pass a E1 from a DAC 4x across
the backplane and then onto a DAC155oM.
1964 ODU 300 HP 28 GHz exhibited output power transients at low power and low
temperatures.
2134 The DAC E3 / DS3M card occasionally had dribbling errors due to marginal
clock timing.
2808 Unwrap time in a twice wrapped ring has been improved from 3-10 seconds
down to 50-200 ms.
Embedded The traffic outage for a 1+1 ODU 500 configuration could exceed 200ms (max
598ms) if the TX power was set to maximum.
Embedded Excessive STM-1 traffic disturbances no longer occur when the TDM clock is
switched between NCC and NPC Cards or vice versa.
Embedded In an error free link the “BER threshold exceeded” warning would occasionally
be raised for no reason. This has now been resolved.
Embedded In an IDU protected system, when the offline IDU is power cycled and the on
line IDU has LOS there was a significant traffic hit as the off line IDU powered
up. This has now been resolved.
Embedded In an IDU protected system, an alarm has been added to indicate when the
partner IDU has been powered off.
Important Notes
1. Traffic may be affected when upgrading software between two specific versions of software.
Contact an Alcatel Lucent Technical Help Desk for details, contact details are on page ii of
these release notes.
2. When upgrading software ensure the remote end of a link is upgraded before the local end.
This is particularly important where the RAC 40 is involved.
3. A license upgrade requires a power cycle if the backplane type changes.
4. A power cycle or a RAC reinsertion is required if a capacity change exceeds the license
capacity size.
5. Care should be taken not to run OSPF and Static routing within the same internal OSPF routing
domain.
6. If Craft terminal loses communication with an IDU 300 SP radio when changing the IP address,
restart Portal to restore communication.
7. Disable any PC firewalls before performing a software download.
8. The channel authentication feature introduced in release v4.0 may cause a possible problem
when upgrade the software. This incompatibility happens only with current DAC-GE customers
that are using:
- Transport Channel Mode sets in “Rapid Failure Detection” or “Rapid Failure Detection and
Protection”,
- Two ends of DAC-GE link have different versions (one end with v4.0 and other end with
previous version v3.7 or lower).
The following steps or procedure for upgrading software are recommended in order to minimize user
traffic impact on DAC-GE:
Step 1: Before downloading new software v4.0 to both ends, change Transport Channel
Mode in both ends to “No Failure Detection - ES Compatibility” in Portal
Step 2: Download both ends with new software v4.0. After activated both ends with new
version, change Transport Channel Mode in both ends back to the original one (“Rapid
Failure Detection” or “Rapid Failure Detection and Protection”).
ALCATEL encourages its customers to report problems so we can resolve them as quickly as possible.
If you encounter a technical issue please contact us