
Data Migration Manager
Document Status: Issue Business Communications Manager Revision: 01.00
Data Migration Manager 35 of 36
Appendix A - System Requirements and Compatibility
For each of the supported source systems that DMM supports there may be certain configuration requirements or
non-supported configuration aspects.
A.1 Minimum Software Versions
Table 4 - BCM 4.0 source System Minimum S/W+ Patch Version Requirements
Nortel SMB Platform S/W Version and Patch
BCM 200/400
BCM 4.0 GA
+
SU Oct 2009 - BCM.R400.SU.System.024-200910-1.0-1.0.zip
Table 5 - BCM 5.0 target System Minimum S/W+ Patch Version Requirements
Nortel SMB Platform S/W Version and Patch
BCM 450 (2 or 4 MBM chassis)
BCM 5.0 GA
+
SU Nov 2009 - BCM450.R500.SU.System-001.200911
A.2 BCM 4.0 to BCM 5.0 Hardware Configuration Compatibility
The following table highlights how particular configuration aspects of a BCM 4.0 system will impact migration to
a BCM 5.0 system.
Table 6 - BCM 4.0 to BCM 5.0 Hardware Configuration Considerations
BCM 4.0 Configured
Option
BCM 5.0 Compatibility Impact
FEM DMM does not support FEM migration to BCM 5.0. Using DMM on this source
system will result in the equivalent MBMs being declared on the target system.
Co-Existing (same bus)
BRI and Loop devices
Migration to BCM 5.0 will result in a requirement to split the BRI device(s) and
the Loop device(s) onto unique buses on the 5.0. MBM Hardware declaration
must declare the BRI and Loop devices to be destined for buses on the 5.0
system such that there are no BRI and Loop devices co-existing on the same
bus (regardless of slot offset).
5/3 Bus Split In this case the 7
th
bus on the BCM 4.0 system is “virtual” hardware declared for
additional IP Set DNs to exist.
Do NOT place a DSM32+ MBM hardware declaration on bus 7 in the MBM
Hardware window. This entry must be left blank (set to Empty) in order for the
associated IP Set DNs to be properly migrated to the target system.
Comentarios a estos manuales