total access 5000_5006 upgrade mop - system release 6.0.2

upgr

ade

guid

e

Document Number: 65K602XUG-48BFebruary 2012

Total Access 5000/5006Upgrade MOPSystem Release 6.0.2

Total Access 5000/5006 Upgrade MOP System Manual

Front Matter

TrademarksAny brand names and product names included in this document are trademarks, registered trademarks, or trade names of their respective holders.

To the Holder of this DocumentThe contents of this document are current as of the date of publication. ADTRAN® reserves the right to change the contents without prior notice.

In no event will ADTRAN be liable for any special, incidental, or consequential damages or for commercial losses even if ADTRAN has been advised thereof as a result of issue of this document.

About this DocumentThis document supports Total Access 5000/5006 System Release 6.0.2.

Upgrade Guides provide detailed procedures on how to upgrade the system firmware or hardware.

901 Explorer BoulevardP.O. Box 140000

Huntsville, AL 35814-4000United States(256) 963-8000

©2012 ADTRAN, Inc.All Rights Reserved.

®

ii 65K602XUG-48B

Revision History

Revision History

Revision Functional DescriptionThis document has been updated to reflect the functionality of Total Access 5000/5006 Upgrade MOP System Release 6.0.2. System Release 6.0.2 includes a new appendix for T1 EFM updates.

ConventionsThe following typographical conventions are used in this document:

This font indicates a cross-reference link.

This font indicates screen menus, fields, and parameters.

THIS FONT indicates keyboard keys (ENTER, ESC, ALT). Keys that are to be pressed simulta-neously are shown with a plus sign (ALT+X indicates that the ALT key and X key should be pressed at the same time).

This font indicates references to other documentation and is also used for emphasis.

This font indicates on-screen messages and prompts.

This font indicates text to be typed exactly as shown.

THIS FONT indicates silk-screen labels or other system label items.

This font is used for strong emphasis.

Revision Date Description

A February 2012 Initial release. This document supports Total Access 5000/5006 System Release 6.0.2.

B February 2012 Initial release. This document supports Total Access 5000/5006 System Release 6.0.2.

65K602XUG-48B iii


Hazard ClassificationsThe following hazard classifications are used in this document:

DANGER!DANGER indicates a hazard with a high level of risk which, if not avoided,will result in death or serious injury.

WARNING!WARNING indicates a hazard with a medium level of risk which, if notavoided, could result in death or serious injury.

CAUTION!CAUTION indicates a hazard with a low level of risk which, if not avoided,could result in minor or moderate injury. CAUTION can also be used to alertagainst unsafe practices associated with events that could lead to personalinjury.

NOTICENotice call-outs indicate a potentially hazardous situation not related topersonal injury, such as messages related to property damage only.

NOTENotes inform the user of additional, but essential, information or features.

iv 65K602XUG-48B

Icons

IconsThe following icons are used throughout the ADTRAN document suite:

deployment guide

installation guide

jobAid

reference guide

diagnostic guide

compliance

engineering guide

application guide

release notes

upgrade guide

user guide

65K602XUG-48B v


TrainingADTRAN offers training courses on our products. These courses include overviews on product features and functions while covering applications of ADTRAN product lines. ADTRAN provides a variety of training options, including customized training and courses taught at our facilities or at customer sites.

For inquiries concerning training, contact ADTRAN:

Training Phone: 800-615-1176

Training Fax: 256-963-6217

Training Email:[email protected]

vi 65K602XUG-48B

Contents

Scope of this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

In this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Suggested Prerequisite Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Required Prerequisite Procedures and Checklist . . . . . . . . . . . . . . . . . . . . . . 7All Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Systems Containing ATM Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Run SCAMP Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Perform System Release 6.0.x Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Prepare System to Upload the New SCA File . . . . . . . . . . . . . . . . . . . . . . . . . . 10Restore Converted SCA File to Upgraded Total Access 5000/5006 . . . . . . . . 10

Systems Containing RPR Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Systems Containing 8 Port T1/HDSL4 EFM Modules . . . . . . . . . . . . . . . . . . . . . . . 10

Suggested Upgrade Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Total Access 5000/5006 Auto Upgrade Procedure . . . . . . . . . . . . . . . . . . . . 12EMS Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Launch a Total Access EMS GUI Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Launch the Auto Upgrade Utility (SCM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Launch the Auto Upgrade Utility (AUTO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Enable a System Controlled Reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Verify Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Saving the SCA File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Close the Total Access EMS GUI Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

CLI Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Total Access 5000 Log On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29System Controlled Reboot (SCR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Auto Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Initiate System Controlled Reboot (SCR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Scheduled SCR Initiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Manual SCR Initiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Verify Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

65K602XUG-48B vii


Saving the SCA File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Menu Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Log On to the Total Access 5000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Total Access 5000 System Menu Remote File Server . . . . . . . . . . . . . . . . . . . 34Total Access 5000 System Menu SCR and Auto-Upgrade . . . . . . . . . . . . . . . . 37

Software Fallback Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Lacking Features or Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41TFTP Interruption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Flash Interruption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Fatal Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Total Access 5000/5006 Fallback Procedure . . . . . . . . . . . . . . . . . . . . . . . . . 42Launching the Auto Upgrade Utility for Fallback (Total Access 5000/5006 Shelf) . 42

Engineering Notes (Total Access 5000/5006 System) . . . . . . . . . . . . . . . . . 47System Controller Module (SCM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Remote File Transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Load Interruptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Switch Module 2GE (SM 2GE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Remote File Transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Flash Transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Remote File Transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Flash Transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Appendix ASystem Configuration Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Scope of this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

In this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Saving an SCA File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

Configure the SCA (Menu) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7

Configure the SCA (CLI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9Log On to the Total Access 5000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9Configure the SCA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-10

Appendix BMonitoring an Auto Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Scope of this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

In this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Monitor an Auto Upgrade Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2

Alternative Large-Scale Upgrade/Downgrade Monitor Procedure . . . . . . . . . . . . . B-3Description of the adTAeScuAutoUpgradeStatus OID . . . . . . . . . . . . . . . . . . . . . B-3

viii 65K602XUG-48B

Contents

Appendix CViewing SCA Restoration Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Scope of this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

In this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

View SCA Restoration Status (CLI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2

View SCA Restoration Status (Menu) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2

Appendix DFirmware Upgrade Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1

Scope of this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1

In this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1

Verify Firmware Upgrade (EMS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2

Alternative Large-Scale Total Access 5000/5006 Firmware Version Verification Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-4

Verify Firmware Upgrade (CLI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-4

Appendix ESystem Provisioning Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1

Scope of this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1

In this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1

Restore System Provisioning (EMS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-2

Restore System Provisioning (CLI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-10

Restore System Provisioning (Menu) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-11

Appendix FT1 EFM Upgrades. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-1

Scope of this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-1

In this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-2

Release Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-2

65K602XUG-48B ix


Appendix GWarranty and Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-1

Warranty. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-1

ADTRAN Customer Care . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-1

ADTRAN Sales. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-1

ADTRAN Technical Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-1

ADTRAN Repair/CAPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-1Repair and Return Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-1

x 65K602XUG-48B

Figures

Figures

Figure 1. EMS Logon Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Figure 2. EMS Launch Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Figure 3. Service Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Figure 4. Auto Upgrade Based on System Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Figure 5. Auto Upgrade on System Release - Step 1 (Location) . . . . . . . . . . . . . . . . . . . 15Figure 6. Auto Upgrade on System Release - Step 2 (Search Result) . . . . . . . . . . . . . . 16Figure 7. Auto Upgrade on System Release - Step 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Figure 8. Auto Upgrade on System Release - Step 4 (Summary) . . . . . . . . . . . . . . . . . . 18Figure 9. Service Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Figure 10. Auto Upgrade Based on System Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Figure 11. Auto Upgrade on System Release - Step 1 (Location) . . . . . . . . . . . . . . . . . . . 20Figure 12. Auto Upgrade on System Release - Step 2 (Search Result) . . . . . . . . . . . . . . 21Figure 13. Auto Upgrade on System Release - Step 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Figure 14. Auto Upgrade on System Release - Step 4 (Summary) . . . . . . . . . . . . . . . . . . 23Figure 15. Service Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Figure 16. SCR Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Figure 17. SCR Scheduler - Step 1 (Location) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Figure 18. SCR Scheduler - Step 2 (Search Result) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Figure 19. SCR Scheduler - Step 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Figure 20. Total Access 5000/5006 System Logon Screen . . . . . . . . . . . . . . . . . . . . . . . . 34Figure 21. Remote File I/O Method Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Figure 22. Remote File Host Provisioning Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Figure 23. Upgrade in Progress (AUTO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Figure 24. Upgrade in Progress (SCM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Figure 25. Concurrent Auto Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Figure 26. Service Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Figure 27. Auto Upgrade Based on System Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Figure 28. Auto Downgrade on System Release - Step 1 (Location) . . . . . . . . . . . . . . . . . 43Figure 29. Auto Downgrade on System Release - Step 2 (Search Result) . . . . . . . . . . . . 44Figure 30. Auto Downgrade on System Release - Step 3 . . . . . . . . . . . . . . . . . . . . . . . . . 45Figure 31. Auto Upgrade on System Release - Step 4 (Summary) . . . . . . . . . . . . . . . . . . 46Figure A-1. System Configuration Archive Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-2Figure A-2. SCA Operation Choice Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-2Figure A-3. System Configuration Archive - Step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-3Figure A-4. System Configuration Archive - Step 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-4Figure A-5. System Configuration Archive - Step 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-5Figure A-6. System Configuration Archive - Step 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-6Figure A-7. System Configuration Archive (SCA) Menu . . . . . . . . . . . . . . . . . . . . . . . . . . .A-7Figure D-1. Select Total Access 5000/5006 from Managed Object Manager List . . . . . . . .D-2Figure D-2. Total Access 5000/5006 Slot Type List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D-3Figure E-1. System Configuration Archive Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .E-2

65K602XUG-48B xi

Total Access 5000/5006 Upgrade MOP

Figure E-2. SCA Operation Choice Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .E-2Figure E-3. System Configuration Archive - Step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .E-3Figure E-4. System Configuration Archive - Step 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .E-4Figure E-5. SCA Restore Operation - Step 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .E-5Figure E-6. SCA Restore Operation - Step 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .E-6Figure E-7. SCA Restore Operation - Step 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .E-7Figure E-8. SCA Restore Operation - Step 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .E-8Figure E-9. Verification Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .E-8Figure E-10.SCA Transfer Status Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .E-9

xii 65K602XUG-48B

Tables

Tables

Table 1. Topic List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Table 2. Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Table 3. Example Total Access 5000 Firmware and Auto Upgrade

Configuration Files for System Release 6.0.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Table 4. Suggested Upgrade Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Table 5. Remote File I/O Method Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Table 6. Remote File Host Provisioning Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . 36Table 7. System Controlled Reboot (SCR) Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Table 8. Auto Upgrade Status Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Table A-1. Appendix A Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-1Table A-2. SCA Autosave Provisioning Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-8Table B-1. Appendix B Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-1Table B-2. Shelf State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-3Table C-1. Appendix C Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-1Table D-1. Appendix D Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D-1Table E-1. Appendix E Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .E-1Table E-2. SCA Module Restore Provisioning Menu Options . . . . . . . . . . . . . . . . . . . . .E-11Table F-1. Appendix F Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .F-1

65K602XUG-48B xiii


xiv 65K602XUG-48B

Total Access 5000/5006

System Release 6.0.2 Upgrade MOP

Scope of this GuideThis guide supports Total Access 5000/5006 System Release 6.0.2.

This guide provides step-by-step instructions for using the ADTRAN Total Access® Element Management System (EMS) to upgrade a Total Access 5000/5006 System to Total Access 5000/5006 System Release 6.0.2. It includes a complete listing of the Total Access 5000 and NetVanta firmware and upgrade configuration files for this release.

In this GuideThis guide contains the following topics:

Table 1. Topic List

Topic See Page

Related Documentation 2

Suggested Prerequisite Procedures 6

Required Prerequisite Procedures and Checklist 7

Suggested Upgrade Schedule 11

Launch a Total Access EMS GUI Session 12

Software Fallback Guidelines 41

Total Access 5000/5006 Fallback Procedure 42

Engineering Notes (Total Access 5000/5006 System) 47

65K602XUG-48B 1


Related DocumentationRefer to Table 2 for additional, detailed information concerning the Total Access 5000 EMS/AOE system.

Table 2. Related Documentation

Title Part Number

Total Access EMS User Guide 64150EMSB08-31

Total Access EMS Installation Guide 64150EMSB08-19

Total Access EMS Administrative Guide 64150EMSB08-30

OSS Gateway Installation and Administrative Guide 64150ANGB08-30

OSS Gateway Command Reference Guide 64150ANGB08-35

2 65K602XUG-48B

IntroductionThe Total Access 5000/5006 System Release 6.0.2 should be upgraded using the Auto Upgrade feature initiated through Total Access EMS.

Once initiated, the Auto Upgrade procedure uses a pre-defined Auto Upgrade Configuration (.auc) file to control the system upgrade. The EMS server must have the files listed in Table 3 in the following directories before the Auto Upgrade procedure can be initiated:

• <EMS installation directory>/owareapps/ems_support/TFTPTransferFiles/

• <EMS installation directory>/owareapps/ems_support/TFTPTransferFiles/system_releases/

Table 3. Example Total Access 5000 Firmware and Auto Upgrade Configuration Files for System Release 6.0.2

Part Number Description Firmware Filename

N/A Auto Upgrade Configuration File (AUTO)

N/A TA5000-06-00-02_AUTO.auc

N/A Auto Upgrade Configuration File (MANUAL)

N/A TA5000-06-00-02_MAN.auc

N/A Auto Upgrade Configuration File (SCM)

N/A TA5000-06-00-02_SCM.auc

System Controller Modules (SCM)

1187010L1 SCM F03.044 1187010L1_f03_044.bin

1187010G2 SCM G2 F03.044 1187010G2_f03_044.bin

1188010E1 SCM International F03.044 1187010L1_f03_044.bin

1188010G2 SCM G2 International F03.044 1187010L1_f03_044.bin

1188010G3 SCM G3 International F03.044 1187010L1_f03_044.bin

1187011G1 SCM Bridging F03.044 1187011G1_f03_044.bin

1888011G1 SCM Bridging International F03.044 1187011G1_f03_044.bin

Switch Modules (SM)

1187020L1 SM 2GE F02.071 1187020L1-060002071.glb

1187020E1 SM 2GE F02.071 1187020E1-060002071.glb

1187020G1 SM 2GE G2 No RG F02.071 1187020G1-060002071.glb

1187020G2 SM 2GE G2 RG F02.071 1187020G2-060002071.glb

1187025G1 SM 2.5 10GE NR F02.071 1187025G1-060002071.glb

1187025G2 SM 2.5 10GE RG F02.071 1187025G2-060002071.glb

1187030G1 SM 5-10GE NR F02.071 1187030G1-060002071.glb

1187030G2 SM 5-10GE RG F02.071 1187030G2-060002071.glb

1187030G3 SM 5 2-10G/2-1 Gigabit F02.071 1187030G3-060002071.glb

65K602XUG-48B 3


BBDLC

1187100L1 COMBO A2+ 24-Port AM F02.071 1187100L1-060002071.glb

1187100L2 COMBO A2+ 24-Port AM F02.071 1187100L2-060002071.glb

1187120L1 COMBO V2 24-Port AM F02.071 1187120L1-060002071.glb

1187150L1 RPOTS 24-Port AM F02.071 1187150L1-060002071.glb

1187160F1 CPOTS 24-Port LM F02.071 1187160F1-060002071.glb

1187520E1 RPR 2.5G LM F02.071 1187520E1-060002071.glb

1187550E1 Quad GigE LM F02.071 1187550E1-060002071.glb

1187550G2 Quad GigE G2 LM F02.071 1187550G2-060002071.glb

1187552G1 Octal GigE LM F02.071 1187552G1-060002071.glb

1187800L1 Voice Gateway DS1 32-Port LM F02.071 1187800L1-060002071.glb

1187801L1 Pseudowire T1 32-Port LM F02.071 1187801L1-060002071.glb

IP DSLAM

1187101E1 ADSL2+ 32-Port AM F02.071 1187101E1-060002071.glb

1188101E1 ADSL2+ 32-Port AM F02.071 1188101E1-060002071.glb

1187102G1 ADSL2+ 32-Port CAT 5 AM F02.071 1187102G1-060002071.glb

1187121L1 VDSL2 32-Port AM F02.071 1187121L1-060002071.glb

1187122G1 VDSL2 32-Port EFM DMT AM F02.071 1187122G1-060002071.glb

ATM Aggregation and Interworking

1187200L1 ATM DS3 LM F02.071 1187200L1-060002071.glb

1187201L1 ATM DS3 4-Port LM F02.071 1187201L1-060002071.glb

1187210E1 ATM OC3-1 LM F02.071 1187210E1-060002071.glb

1187211E1 ATM OC3-4 LM F02.071 1187211E1-060002071.glb

Business Services

1187220G1 CH DS3 PPP 3-Port LM F02.071 1187220G1-060002071.glb

1187220G3 CH DS3 FR 3-Port LM F02.071 1187220G3-060002071.glb

1188801G1 E1 CEM/PWE 32-Port LM F02.071 1188801G1-060002071.glb

1187803G1 DS1 IMA 32-Port LM F02.071 1187803G1-060002071.glb

1187803G2 DS1 PPP 32-Port LM F02.071 1187803G2-060002071.glb

1187803G3 DS1 FR 32-Port LM F02.071 1187803G3-060002071.glb

1188803G2 E1 PPP/MLPPP 32-Port LM F02.071 1188803G3-060002071.glb

Table 3. Example Total Access 5000 Firmware and Auto Upgrade Configuration Files for System Release 6.0.2 (Continued)


4 65K602XUG-48B

Fiber to the Premises/GPON

1187500E1 GPON OLT 2-Port AM F02.071 1187500E1-060002071.glb

1187501G1 GPON OLT 2x SFP AM F02.071 1187501G1-060000266.glb

1187502F1 GPON OLT 4X SFP AM F02.071 1187502F1-060002071.glb

1187560F1 Active Ethernet 24-Port, Dual AM F02.071 1187560F1-060002071.glb

EoX

1187180L1 EFM SHDSL 32-Port AM F02.071 1187180L1-060002071.glb

1188180E1 EFM SHDSL 32-Port AM F02.071 1188180E1-060002071.glb

1187180G1 EFM SHDSL 32-Port AM F02.071 1187180G1-060002071.glb

1187181G1 EFM SHDSL 24-Port AM F02.071 1187180G1-060002071.glb

1187250G1 EFM Bonding Protection Module F02.071 1187250G1-060002071.glb

1187260G1 EFM DS3 Unchannelized 4-Port LM F02.071 1187260G1-060002071.glb

1187300L1 EFM T1 8-Port LM F02.071 1187300L1-060002071.glb

1187310L1 EFM HDSL4 8-Port LM F02.071 1187310L1-060002071.glb

1187802L1 EFM DS1 32-Port LM F02.071 1187802L1-060002071.glb

1187810G1 EFM DS3 Channelized 3-Port LM F02.071 1187810G1-060002071.glb

1188802G1 EFM E1 32-Port LM F02.071 1188802G1-060002071.glb

Table 3. Example Total Access 5000 Firmware and Auto Upgrade Configuration Files for System Release 6.0.2 (Continued)


65K602XUG-48B 5


Suggested Prerequisite ProceduresThe following procedure provides tools to make the upgrade process complete without affecting other systems that may be associated with the Total Access 5000/5006 System. These procedures are not necessary to complete the system upgrade.

1. Disable any flow-through provisioning that may affect the Total Access 5000/5006 Sys-tem during the upgrade. If a shelf loses communication due to a card reset after upgrade, auto provisioning may fail. This can cause confusion for the OSS. To prevent this type of failure, the TL1 Gateway may be shutdown for the duration of the upgrade, or if a single shelf is to be upgraded that shelf may be removed from the TL1 Gateway before the upgrade and added to the TL1 Gateway after the upgrade.

NOTEIf no flow-through updates are scheduled during the upgrade, this step canbe skipped.

2. Disable any statistics gathering to shelves that are to be upgraded for the duration of the upgrade.

3. Make sure there are no trap storms from other devices that have the EMS server set as trap host.

4. Perform a trial upgrade on a Total Access 5000 lab system to verify that all correct files are in the correct directories and that manipulating those files has not caused any file corruption.

6 65K602XUG-48B

Required Prerequisite Procedures and ChecklistThis section includes procedures and setting checks that must be completed before completing the system upgrade. The following sections include instruction for systems containing the listed modules.

• All Systems

• Systems Containing ATM Modules

• Systems Containing RPR Modules

• Systems Containing 8 Port T1/HDSL4 EFM Modules

All SystemsComplete the following procedure for a successful upgrade of the Total Access 5000/5006 System.

1. Upgrade the Total Access EMS to System Release B07 or later EMS release.

This action will support the use of the system-controlled reboot (SCR) during the upgrade of the Total Access 5000/5006 modules.

2. Archive the current system configuration to an SCA file before performing the prerequisite procedures.

For detailed procedures, refer to “Appendix A, System Configuration Archive”.

3. Obtain the Total Access 5000/5006 System Release 6.0.2 zip file from the ADTRAN ftp site.

4. Extract the TA5000-06-00-xx.zip file into the following directories on the EMS server:

NOTEThe Total Access 5000 zip file (TA5000-06-00-xx) references the appropriate6.0 system release.

• <EMS installation directory>/owareapps/ems_support/TFTPTransferFiles/

• <EMS installation directory>/owareapps/ems_support/TFTPTransferFiles/system_releases/

CAUTION!Once the entire network upgrades to Total Access 5000/5006 System Release6.0.2, remove and save the unique files associated with previous Total Access5000/5006 System Release. Do not remove files associated with the currentsystem release until the SCM that is connected to the network has been giventhe TA5000-06-00-xx_AUTO.auc. Removing a required auc file from theRemote File server causes the EMS to be flooded with traps from the existingSCM because the auc file that the SCM is requesting is not available.

5. Verify connectivity to shelves to be upgraded.

6. Verify that the Auto Upgrade Mode is either Manual or Auto on the shelf to be upgraded during the Maintenance Window. If not, change Auto Upgrade Mode to either Manual or Auto.

65K602XUG-48B 7


7. Disable SCA retrieval for period of upgrade.

8. Verify that no SCA restorations are in progress on the shelf to be upgraded (Refer to “Appendix C, Viewing SCA Restoration Status”). If any SCA restorations are in progress, wait for the restoration to fully complete.

9. Disable device re-syncs for period of upgrade.

Systems Containing ATM ModulesPreviously, ATM provisioning resided on both the Access Module and Switch Module. With System Release 6.0, provisioning is "pushed-down" from the Switch Module to the ATM Modules, similar to other modules within the system. This centralization structure; however, requires that certain steps be taken to ensure a smooth transition when upgrading to System Release 6.0, especially for customers with DS3 or OC3 default network interfaces.

This conversion process has no bearing on the Default Network Interface, whether the DNI is an ATM interface or otherwise. The conversion process is only necessary for Total Access 5000/5006 systems in which there is the Inband Management of systems or units subtended by an ATM interface (DS3, OC3/STM-1, IMA) from that Total Access 5000/5006 system. If this conversion process is neglected for a Total Access 5000/5006 system, the customer may lose management of subtended ATM devices. Subscriber traffic should be unaffected, as should Inband Management of the Total Access 5000/5006 system itself.

• This process and operation is a one-time occurrence such that once you enter 6.X firmware, this process is not required again for the ATM Modules.

• It is ABSOLUTELY Critical to perform and save-off an SCA file for the Total Access 5000/5006 5.X release prior to upgrade to Total Access 5000/5006 6.0 in order for this process to work properly.

• The post upgrade SCA File can ONLY be restored to a system running Total Access 5000/5006 6.0 release.

• Upgrade items covered herein are specific to our ATM Module set.

Prior to firmware upgrade, run the SCAMP process on the System Release 5.x.x SCA file that was retreived prior to attempting the upgrade. This will ensure the SCA conversion process properly happens. Once completed, operators should continue forward with the System Upgrade to System Release 6.0.x.

NOTEThe conversion process is only necessary for Total Access 5000/5006 systemsin which there is the Inband Management of systems or units subtended byan ATM interface (DS3, OC3/STM-1, IMA) from that Total Access 5000/5006system.

Overview of Upgrade Path Process:

1. Create an SCA file for the Total Access 5000/5006 system to be upgraded from System Release 5.x.x to System Release 6.0.x by performing a SCA save.

2. Run SCAMP tool on SCA file retrieved from Total Access 5000/5006 system.

3. Perform System Release 6.0.x upgrade to the Total Access 5000/5006 system.

4. Prepare for SCA upload (restore) by enabling SCA restore for the ATM line module slots affected.

5. Perform SCA restore.

8 65K602XUG-48B

SetupListed below are the recommended steps that should be followed prior to performing the System Upgrade. The programs and files listed below will be posted to the TA5000 FTP Site for download at this link: SCAMP-Package

1. Before running the tool and before upgrading ANY firmware on the Total Access 5000/5006 system you must create an SCA file from the current 5.x.x system. For detailed pro-cedures, refer to “Appendix A, System Configuration Archive”.

NOTEFor the purposes of this guide, the SCA file will be named "scabackup.sca".

2. Prior to firmware upgrade, run the SCAMP process on the SR 5.x.x SCA file prior to attempting the upgrade. This will ensure the SCA conversion process properly happens. Once completed, operators should continue forward with the System Upgrade to SR 6.0.

3. In order to run the tool you must first have the following files all located in the same directory.

• SCAMP.exe

• dumpta3k.exe

• SCAConvert.bat

• scabackup.sca, (The SCA file which you are trying to convert)

4. It is now time to upgrade the code on the shelf from 5.x.x to 6.0.x.

CAUTION!Before running the SCAMP tool ensure an SCA file was created. If not, pleasego back to Step 1.

Run SCAMP ToolThis section details the required steps to upgrade the SCA file with the SCAMP tool. The SCA file must be converted before upgrading the system to System Release 6.0.x.

Complete the following procedure to run the SCAMP tool:

1. Open a command prompt window in the directory where you have placed all of the files needed by the tool. (TIP: This is easily done in Windows by holding shift while right mouse clicking in the window. In the menu that appears, there will be an option "open command window here" to open a terminal window in the current directory.)

2. Once the terminal window is open, run the batch file using the following command: (once again noting that you will replace "scabackup.sca" with the filename of your SCA file)

SCAConvert.bat scabackup.sca <ENTER>

3. The program will begin to run. This could take a few minutes depending on the size of your SCA file. Wait until the command prompt returns.

65K602XUG-48B 9

ftp://ta5kuser:[email protected]/outgoing/PM/ATM-SCAMP_Package.zip


4. If everything was completed successfully, there will be two new files in the working directory, "Converted_scabackup.sca" and "ChangeLog.txt".

• "Converted_scabackup.sca" is the new SCA file.

• "ChangeLog.txt" will have a list of the slots that have changes and need to be re-provisioned. The contents of the file are commands that need to be run from the root terminal of the shelf BEFORE restoring the new SCA file.

Perform System Release 6.0.x UpgradePerform System Release 6.0.x upgrade to the Total Access 5000/5006 system. Refer to “Suggested Upgrade Schedule” on page 11 to begin the upgrade process.

Prepare System to Upload the New SCA FileBefore attempting to upload the new SCA file, modules must be updated with the "ChangeLog.txt" file.

1. Open a terminal connection to the shelf that is to be upgraded to System Release 6.0.x and Log in..

2. Enter the enable mode.

ChassisId>enable

3. Copy and paste the contents of the "ChangeLog.txt" file into the window and press ENTER. This will enable SCA restore for the needed slots.

Restore Converted SCA File to Upgraded Total Access 5000/5006After completing the System Release 6.0.2 upgrade, upload the converted SCA file to the upgraded Total Access 5000/5006 system and perform an SCA restore to the upgraded Total Access 5000/5006 system. For detailed procedures, refer to “Appendix E, System Provisioning Restore”.

Systems Containing RPR ModulesIf the system uplink (on the Switch Module) and hub/spoke mode (on the RPR LM) have been configured via Menus in a release prior to any CLI support, there may be a problem when upgrading to System Release 6.0.2.

If the "show running-config system" command shows "ethernet default interface backplane 1/A/x" or something similar, it should be reprovisioned to "ethernet default interface rpr" before the upgrade to System Release 6.0.2.

Systems Containing 8 Port T1/HDSL4 EFM ModulesIf the system uplink has been configured via Menus in a release prior to any CLI support, there may be a problem when upgrading to System Release 6.0.2.

If the "show running-config system" command shows "ethernet default interface backplane 1/A/x" or something similar, it should be reprovisioned to "ethernet default interface efm-group shelf/slot/group" before the upgrade to System Release 6.0.2.

10 65K602XUG-48B

Suggested Upgrade ScheduleADTRAN suggests the following upgrade schedule for the System Upgrade from System Release 5.1.x , 5.5.x, or 5.7.x to System Release 6.0.2. The SCMs can be optionally upgraded prior to the upgrade of the system, but this is not required. Refer to Table 4 for more infor-mation. If moving directly from System Release 5.x to 6.0.x simply follow the Day 2 scenario detailed in Table 4.

NOTEBefore proceeding, ensure the shelves scheduled to be upgraded during thisprocess are responding to the network.

Table 4. Suggested Upgrade Schedule

Day Action Expected Traffic Downtime

Day 1 (Optional) Upgrade all SCMs first using the TA5000-06-00-xx_SCM.auc file.

None

Day 2 Enable System Controlled Reboot (SCR) for the Total Access 5000/5006 shelves. Set the SCR option to Manual.Apply TA5000-06-00-xx-AUTO.auc to the COT and RT nodes to download the software to all the modules in the nodes. The software only downloads at this point and no reboots will occur. Units will continue to operate on the previous code release. Once all of the Total Access 5000/5006 systems have been verified to have successfully upgraded using the monitor procedure, schedule a time to manually perform a System Controlled Reboot (SCR), to reboot all SCM modules to the new firmware.ADTRAN recommends that the SCR scheduled time occur during the maintenance window.

None

65K602XUG-48B 11


Total Access 5000/5006 Auto Upgrade ProcedureOnce the prerequisite procedures are complete, use one of the following procedures to upgrade the Total Access 5000/5006 System.

• “EMS Upgrade” on page 1-12

• “CLI Upgrade” on page 1-29

• “Menu Upgrade” on page 1-33

CAUTION!Upgrade all connected ONTs to version A3.10.00 and all connected NetVantaproducts to Carrier Ethernet Release 4.1 before completing the SystemRelease 6.0.2 upgrade. Failure to upgrade connected devices before thesystem upgrade can cause a loss of connection or functionality.

• Refer to the Carrier Ethernet Upgrade MOP (P/N 6CETHSR41-48) forNetVanta upgrade instructions.

• Refer to the FTTP ONT Release Notes - AOS Release A3.10.00 for ONTupgrade instructions.

EMS UpgradeThis subsection covers the following:

• Auto Upgrade

• SCA Save

Launch a Total Access EMS GUI SessionA Total Access EMS GUI session is required to perform a remote firmware download using the Auto Upgrade function. Launch the GUI by following the instructions provided by the system administrator.

1. Enter the designated User Name and Password in the Total Access EMS Logon screen (refer to Figure 1).

Figure 1. EMS Logon Screen

12 65K602XUG-48B

2. Click Logon in the Total Access EMS Logon screen. This launches the EMS Launch Console (refer to Figure 2).

Figure 2. EMS Launch Console

3. Proceed to the applicable section to complete the upgrade.

• Proceed to “Software Fallback Guidelines” on page 41 to downgrade a system back to a previous firmware revision.

• Proceed to “Launch the Auto Upgrade Utility (SCM)” to upgrade a system from a System Release prior to System Release 5.0.

• Proceed to “Launch the Auto Upgrade Utility (AUTO)” on page 19 to upgrade a system from System Release 5.0 or newer.

Launch the Auto Upgrade Utility (SCM)

NOTEUpgrading the SCM is only required when upgrading from a System Releaseprior to System Release 5.0. If upgrading from System Release 5.0 to 5.7.x,refer to “Launch the Auto Upgrade Utility (AUTO)” on page 19.

The Auto Upgrade Utility operation is as follows:

• The Auto Upgrade utility checks each of the system modules for the proper SCM firmware revision.

• Once the check is complete, the SCM initiates a request for the proper firmware file for the first type of module that is found not to have the correct firmware.

• The firmware is then loaded into the SCM cache and distributed to each module of that type, one module at a time, until each module of that type contains the proper firmware.

• The SCM then initiates a request for the proper firmware file for the second type of module that is found not to have the correct firmware.


• This process continues until all the modules in the system have been updated to the proper firmware.

NOTESince System Controlled Reboot is being used for this upgrade, there will beno reboot of modules in this step of the upgrade.

65K602XUG-48B 13


The time required to retrieve a firmware file depends on the file size and the speed of the management link.

1. From the EMS Launch Console, select Auto TFTP/Auto Upgrade/SCR from the Service Menu (refer to Figure 3).

This launches the Auto TFTP/Auto Upgrade/SCR dialog box (refer to Figure 4).

Figure 3. Service Menu

Figure 4. Auto Upgrade Based on System Release

2. From the Auto TFTP Auto Upgrade/SCR dialog box, select the Auto Upgrade based on System Release radio button, then click OK.

This launches the Auto Upgrade Scheduler, beginning with the Auto Upgrade on System Release - Step 1 (Location) screen (refer to Figure 5).

14 65K602XUG-48B

Figure 5. Auto Upgrade on System Release - Step 1 (Location)

3. Select (highlight) the appropriate Total Access 5000/5006 Central Office Terminal (COT) location from the location tree on the left of the Auto Upgrade on System Release - Step 1 (Location) screen. All locations subordinate to the selection, display in the location frame.

4. Check the box next to the location housing the Total Access 5000/5006 System to be updated.

5. Select the Chassis Type from the drop-down menu to designate the type of system to be upgraded.

(Select Total Access 5000/5006 to upgrade a Total Access 5000/5006 System.)

6. Click Next to continue.

This launches the Auto Upgrade on System Release - Step 2 (Search Result) screen (refer to Figure 6).

65K602XUG-48B 15


Figure 6. Auto Upgrade on System Release - Step 2 (Search Result)

7. Select the Total Access 5000/5006 from the search results by selecting the corresponding check boxes in the Auto Upgrade on System Release - Step 2 (Search Result) screen. The search results provide information about the Total Access 5000/5006: IP Address, System Name, and System Description.


This launches the Auto Upgrade on System Release - Step 3 screen (refer to Figure 7).

16 65K602XUG-48B

Figure 7. Auto Upgrade on System Release - Step 3

9. Click the Config File Name ellipsis (...) button on the Auto Upgrade on System Release - Step 3 screen to select the Auto Upgrade Configuration File. The selected file name is displayed. The configuration file name is designated in Table 3 on page 3.

10. Select the time and date to perform the file transfer.

• Choose Update Now, or

• Choose Update in 2 minutes.

NOTE• ADTRAN recommends using the Update Now or Update in 2 minutes

options to conserve time during this upgrade.• Real-time status information is not available on the Scheduled Operations

screen when Update Now is selected.

11. Ensure that the Use SCR (defer reset) is checked. If not, the modules will be upgraded and rebooted one at a time starting from slot 1 through slot 22, standby SM, active SM, and SCM if required. Not using SCR will likely cause extra data outage time compared to the SCR approach which waits until all modules have successfully accepted the new application code and then are all rebooted together.

65K602XUG-48B 17


12. Click Next to execute the request.

This launches the Auto Upgrade on System Release - Step 4 (Summary) screen (refer to Figure 8). This screen displays a summary of the scheduled items.

Figure 8. Auto Upgrade on System Release - Step 4 (Summary)

13. Click Next to continue to the final screen.

14. Click Start Over to schedule another Auto Upgrade occurrence or Close Wizard to exit.

15. Monitor the Total Access 5000/5006 Auto Upgrade until it is complete. For detailed procedures, refer to “Appendix B, Monitoring an Auto Upgrade”.

16. Once all of the Total Access 5000/5006 systems have been verified to have successfully upgraded using the monitor procedure, schedule a System Controlled Reboot (SCR) for the Total Access 5000/5006 shelf to reboot all SCM modules to the new firmware.

ADTRAN recommends that the SCR time be scheduled to occur during the maintenance window.

NOTE• EMS will temporarily lose communication with the Total Access 5000 for

approximately two minutes while the SCM reboots to activate the newsoftware.

• After completing the upgrade, the SCM firmware associated with SystemRelease 6.0.x automatically ensures the COMBO A2+ cards are upgraded tofirmware version C19.32 before attempting to upgrade to System Release6.0.x.

18 65K602XUG-48B

Launch the Auto Upgrade Utility (AUTO)The Auto Upgrade Utility operation is as follows:

• The Auto Upgrade utility checks each of the system modules for the proper SCM firmware revision.

• Once the check is complete, the SCM initiates a request for the proper firmware file for the first type of module that is found not to have the correct firmware.


• The SCM then initiates a request for the proper firmware file for the second type of module that is found not to have the correct firmware.


• This process continues until all the modules in the system have been updated to the proper firmware.

The time required to retrieve a firmware file depends on the file size and the speed of the management link.




65K602XUG-48B 19



2. From the Auto TFTP Auto Upgrade/SCR dialog box, select the Auto Upgrade based on System Release radio button, then click OK.


Figure 11. Auto Upgrade on System Release - Step 1 (Location)

3. Select (highlight) the appropriate Total Access 5000/5006 Central Office Terminal (COT) location from the location tree on the left of the Auto Upgrade on System Release - Step 1 (Location) screen). All locations subordinate to the selection, display in the location frame.

20 65K602XUG-48B



(Select Total Access 5000/5006 to upgrade a Total Access 5000/5006 System.)



Figure 12. Auto Upgrade on System Release - Step 2 (Search Result)




65K602XUG-48B 21


Figure 13. Auto Upgrade on System Release - Step 3

9. Click the Config File Name ellipsis (...) button on the Auto Upgrade on System Release - Step 3 screen to select the Auto Upgrade Configuration File. The selected file name is displayed. The configuration file name is designated in Table 3 on page 3.

10. Select the time and date to perform the file transfer.


• Choose Update in 2 minutes

NOTE• ADTRAN recommends using the Update Now or Update in 2 minutes

options to conserve time during this upgrade.• Real-time status information is not available on the Scheduled Operations

screen when Update Now is selected.

11. Ensure that the Use SCR (defer reset) is checked. If not, the modules will be upgraded and rebooted one at a time starting from slot 1 through slot 22, standby SM, active SM, and SCM if required. Not using SCR will likely cause extra data outage time compared to the SCR approach which waits until all modules have successfully accepted the new application code and then are all rebooted together.

22 65K602XUG-48B


This launches the Auto Upgrade on System Release - Step 4 (Summary) screen (refer to Figure 14).

This screen displays a summary of the scheduled items.



14. Click Start Over to schedule another Auto Upgrade occurrence or Close Wizard to exit.


16. Once all of the scheduled Total Access 5000 systems have been verified to have successfully upgraded using the monitor procedure, schedule a system controlled reboot for the Total Access 5000/5006 shelf to reboot all modules into the new firmware.

ADTRAN recommends that the SCR time be scheduled to occur during the maintenance window.

65K602XUG-48B 23


NOTEEMS will temporarily lose communication with the Total Access 5000 forapproximately two minutes while the SCM reboots to activate the newsoftware

Enable a System Controlled RebootAfter the Auto Upgrade is performed, the System Controlled Reboot option must be enabled in the Total Access 5000/5006 shelf. To do this, complete the following procedure.




Figure 16. SCR Wizard

2. From the Auto TFTP/Auto Upgrade/SCR dialog box, select the SCR Wizard radio button, then click OK.

This launches the SCR Scheduler, beginning with the SCR Scheduler - Step 1 (Location) screen (refer to Figure 17).

24 65K602XUG-48B

Figure 17. SCR Scheduler - Step 1 (Location)

3. Select (highlight) the appropriate Total Access 5000/5006 location from the location tree on the left of the SCR Scheduler - Step 1 (Location) screen. All locations subordinate to the selection, display in the location frame.



(Select Total Access 5000/5006 to schedule a reboot for a Total Access 5000/5006 System.)


This launches the SCR Scheduler - Step 2 (Search Result) screen (refer to Figure 18).

65K602XUG-48B 25


Figure 18. SCR Scheduler - Step 2 (Search Result)

7. Select the Total Access 5000/5006 from the search results by selecting the corresponding check boxes. The search results provide information about the Total Access 5000/5006: IP Address, System Name, and System Description.


This launches the SCR Scheduler - Step 3 screen (refer to Figure 19).

26 65K602XUG-48B

Figure 19. SCR Scheduler - Step 3

NOTEAt this point, all Total Access 5000/5006 shelves should indicate Ready in theStatus column (Figure 19). If not, the Auto Upgrade did not completeproperly. Connect to the Total Access 5000/5006 to determine why the AutoUpgrade did not complete.

9. Select the Total Access 5000/5006 from the search results by selecting the corresponding check boxes. The search results provide information about the Total Access 5000/5006: IP Address, System Name, and Status.

10. Select Enable SCR to enable SCR for the Total Access 5000 shelves selected.

11. Select Cancel to close the SCR Scheduler - Step 3 screen. The SCR is now enabled, and the auto upgrade can now proceed.

NOTEThe Total Access 5000 shelf will not reboot until the SCR is scheduled later.

65K602XUG-48B 27


12. Use the EMS GUI to verify the SCR setting. The SCR Mode must be set to Manual. Set the SCR Mode by completing the following procedure:

a. Verify the SCR is enabled.

b. Select Managed Objects from the Config menu.

c. Select the Total Access 5000 System to be verified.

d. Select Shelf-1/SCM.

e. Click Edit.

f. Select Provisioning/SCR Settings.

g. Verify the Use SCR is set to Yes and the SCR Mode is set to Manual.

h. Select Auto Upgrade Settings.

i. Select Auto in the Auto Upgrade Mode field.

j. Select Apply.

k. Select Close.


14. Select the time and date to perform the SCR reboot, choose the designated date and time for the maintenance window, or choose Reboot Now or Reboot in 2 minutes.


16. Click Close Wizard to exit.

Verify FunctionalityOnce the upgrade is completed, verify the system and all installed modules are functioning properly. If not, restore the previously working provisioning profile by performing an SCA Restore, refer to “Appendix E, System Provisioning Restore” for detailed insructions.

Saving the SCA FileADTRAN recommends saving the new system configuration. Save the current system config-uration to an SCA file. SCA files are tied to software releases, so a new SCA file is needed for the system configuration with the new software release. For detailed procedures, refer to “Appendix A, System Configuration Archive”.

Close the Total Access EMS GUI SessionOnce the system release upgrade is complete, the Total Access EMS GUI session can be closed.

To log off and exit the application, select Log Off and Exit from the Control menu.

The Total Access 5000/5006 System release upgrade is complete.

28 65K602XUG-48B

CLI UpgradeThis subsection covers the following:

• Auto Upgrade

• System Controlled Reboot (SCR)

Total Access 5000 Log OnFor initial deployment, only craft access is available. A serial cable with a male DB-9 connector on the Total Access 5000/5006 end is required.

To log on to the Total Access 5000/5006 command line interface, complete the following:

1. Set the parameters of the VT100 terminal to the following settings:

• 9600 baud rate

• 8-data bits

• No parity

• 1-stop bit

• No flow control

2. Plug the male end of the data cable into the Total Access 5000/5006. Make a connection to the VT100 terminal or a PC running emulation software as appropriate for the equipment.

3. After completing the prerequisite procedures above, pressing any key displays the logon Command Set.

The Total Access 5000 System Logon prompt displays the following information:

User Access Verification

Username:

NOTEThe account name and password are case sensitive.Default accounts are ADMIN, READONLY, READWRITE, and TEST. Thedefault password for each of these accounts is PASSWORD. The privilege tochange passwords, account names, and privileges are included in theADMIN account.At the Username field, input the Username (ADMIN), andpress ENTER.

4. At the Password field, input the Password (PASSWORD), and press ENTER.

65K602XUG-48B 29


5. Upon entering the correct password, the Total Access 5000 CLI introduction banner displays the following information:


Username:ADMIN

Password:********

Last Login Date : Nov 10 2008 10:19:17Last Login Type : IP Session(CLI) ‐ 192.168.1.3Login Failures : 0 (Since Last Login) : 14 (Total for Account)

ChassisID>

6. Access the Enable Command Set.

ChassisID>enableChassisID#

7. Access the Global Configuration Command Set.

ChassisID#configure terminal

NOTEThe privileged commands (Enable prompt) are designated by the #Command Set.

System Controlled Reboot (SCR)The System Controlled Reboot (SCR) mitigates release version interoperability problems by synchronizing module reboots after new system release software is written to the modules’ backup FLASH images. SCRs can be scheduled to take place on a specific date and at a specific time (such as during off-peak hours that are less likely to interrupt service.)

To enable System Controlled Reboot, from the Global Configuration prompt complete the following:

1. Access the Auto Upgrade Configuration prompt.ChassisId(config)#auto‐upgrade

2. Set the Auto Upgrade Mode.ChassisId(config‐auto‐upgrade)#mode [auto|disabled|manaul]

3. Enable SCR.ChassisId(config‐auto‐upgrade)#scr

4. Exit to the Global Configuration prompt.ChassisId(config‐auto‐upgrade)#exit

30 65K602XUG-48B

Auto UpgradeThe Total Access 5000/5006 Auto Upgrade system provides methods to manually or automat-ically upgrade the flash firmware for the Total Access 5000/5006. When the Auto Upgrade system is enabled, either manually or automatically, the Total Access 5000/5006 will compare the current product revision and firmware revision information against what has been specified in a retrieved Auto Upgrade Configure File (auc). Modules that are not currently running the firmware revision specified in the auc File will be marked as “needing upgrade.” If the operating mode is set to Auto, the module will be immediately upgraded or scheduled for future upgrade if another module upgrade is already in progress.

To configure the Auto Upgrade System, complete the following:

1. Configure the auto upgrade default transfer protocol.

ChassisId(config)#ip file‐server default protocol [file‐transfer‐over‐tl1|ftp|sftp|tftp]

2. Configure the auto upgrade host IP address.

ChassisId(config)#ip file‐server default host A.B.C.D

3. Configure the auto upgrade path.

ChassisId(config)#ip file‐server auto‐upgrade path WORD

4. Access the Auto Upgrade Configuration prompt.

ChassisId(config)#auto‐upgrade

5. Configure the auto upgrade mode.

NOTEThe Auto Upgrade Mode is automatically over-written based upon thespecific AUC file that is used for the upgrade unless the mode is set to"disabled" in which Auto Upgrade will perform no actions.

ChassisId(config‐auto‐upgrade)#mode [auto|disabled|manual]

6. Return to the Global Configuration prompt.

ChassisId(config)#exit

7. Configure the auto upgrade filename.

ChassisId(config)#ip file‐server auto‐upgrade filename WORD

8. Return to the Enable prompt.

ChassisId(config)#exit

9. Use the force auto-upgrade [abort|reset-config-cache|start] command to manually control the following auto upgrade operations:

ChassisId#force auto‐upgrade abort – Abort auto-upgrade of the system

ChassisId#force auto‐upgrade reset‐config‐cache – Reset auto-upgrade config (AUC) cache

ChassisId#force auto‐upgrade start – Start auto-upgrade of the system

10. Display the Auto Upgrade Configuration status.ChassisId#show auto‐upgrade module‐status <shelf/slot> realtimeorChassisId#show auto‐upgrade shelf‐status <shelf> realtime

65K602XUG-48B 31


Initiate System Controlled Reboot (SCR)After the Auto Upgrade is performed, the System Controlled Reboot must be initiated in the Total Access 5000/5006 shelf.

To do this, complete the following procedure.

Scheduled SCR Initiation1. To schedule the SCR for a later time, complete the following steps.

ChassisId(config)#scr mode scheduled

2. Schedule the SCR.ChassisId(config)#scr schedule <HH:MM> <1‐31> MONTH <2000‐2099>

3. Exit to the Enable prompt.ChassisId(config)#exit

Manual SCR Initiation1. To manually initiate the SCR, complete the following steps.

ChassisId(config)#scr mode manual

2. If SCR mode is set to manual and auto-upgrade has completed, use one of the following commands to reboot upgraded modules into the new firmware.

ChassisId#force scr modules

or

ChassisId#force scr all

3. Exit to the Enable prompt.ChassisId(config)#exit

Verify FunctionalityOnce the upgrade is completed, verify the system and all installed modules are functioning properly. If not, restore the previously working provisioning profile by performing an SCA Restore, refer to “Appendix E, System Provisioning Restore” for detailed insructions.

Saving the SCA FileADTRAN recommends saving the new system configuration. Save the current system config-uration to an SCA file. SCA files are tied to software releases, so a new SCA file is needed for the system configuration with the new software release. For detailed procedures, refer to “Appendix A, System Configuration Archive”.

32 65K602XUG-48B

Menu UpgradeThis subsection covers the following:

• Remote File Server Setup

• Auto Upgrade

• SCR

Log On to the Total Access 5000For initial deployment, only craft access is available. A straight-through serial cable with a male DB-9 connector on the Total Access 5000/5006 end is required.

To log on to the Total Access 5000/5006 menu structure, complete the following:


• 9600 baud rate

• 8-data bits

• No parity

• 1-stop bit

• No flow control


3. After completing the prerequisite procedures above, pressing any key displays the logon screen. The logon screen displays with the cursor in the Account Name field.

NOTEThe account name and password are case sensitive.Default accounts are ADMIN, READONLY, READWRITE, and TEST. Thedefault password for each of these accounts is PASSWORD. The privilege tochange passwords, account names, privileges, and perform system upgradesare included in the ADMIN account.

65K602XUG-48B 33


The Total Access 5000/5006 System Logon screen is shown in Figure 20.

Figure 20. Total Access 5000/5006 System Logon Screen

4. At the Account Name field, input the Account Name (ADMIN), and press Enter.


Total Access 5000 System Menu Remote File ServerTo provision auto upgrade to use a remote file server, complete the following procedure:

1. From the Total Access 5000 Main menu, select System Controller, and press ENTER.

2. From the System Controller menu, select Provisioning, and press ENTER.

3. From the Provisioning menu, select System Administration, and press ENTER.

4. From the System Administration menu, select Auto Upgrade Status, and press ENTER.

5. From the Auto Upgrade Status menu, select Remote File Host Provisioning, and press ENTER.

TID: HSV00001 Total Access 5000/5006 System MM/DD/YY

HH:MM

Unacknowledged Alarms: None Node: 1

Total Access 5000/5006 System

Account Name :

Password :

'?' - System Help Screen

34 65K602XUG-48B

6. From the Remote File Update menu, select Remote File I/O Method, and press ENTER.

Figure 21 displays the Remote File I/O Method menu.

Figure 21. Remote File I/O Method Menu

7. From the Remote File I/O Method, use Table 8 to select the method of remote file transfer.

8. From the Provisioning menu, select Network Management, and press ENTER.

9. From the Network Management menu, select IP Network Provisioning, and press ENTER.

10. From the IP Network Provisioning menu, select IP Services And Ports, and press ENTER.

Table 5. Remote File I/O Method Options

Option Function

TFTP (UDP/IP) This option selects a file transfer method that uses UDP packets over IP and requires a remote TFTP server.

FTOT (File transfer Over TL1) This option selects an ADTRAN-proprietary file transfer method that transfers files over TL1.

FTP (TCP/IP) This option selects a file transfer method that uses TCP packets over IP.

SFTP (TCP/IP) This option selects a file transfer protocol that performs all oper-ations over an encrypted SSHv2 transport.

TID: TA5000 Total Access 5000 MM/DD/YY hh:mm


Remote File I/O Method : TFTP <UDP/IP>

1. TFTP <UDP/IP>

2. FTOT <File Transfer Over TL1>

3. FTP <TCP/IP>

4. SFTP <TCP/IP>

Selection :

‘?’ - System Help Screen

65K602XUG-48B 35


11. From the IP Services And Ports menu, select Remote File Host Provisioning, and press ENTER.

Figure 21 displays the Remote File Host Provisioning menu.

Figure 22. Remote File Host Provisioning Menu

* - This option is displayed if the Remote File I/O Method option is set to FTP.

Table 6. Remote File Host Provisioning Menu Options

Description Function

Remote Firmware Host This option sets the IP address for the Remote Firmware Host. The default is set to 0.0.0.0.

Remote SCA Host This option sets the IP address for the Remote SCA Host. The default is set to 0.0.0.0.

Remote Host User ID* This option provides a text entry field for the Remote Host User ID. The default is set to “guest.”

Remote Host Password* This option provides a text entry field for the Remote Host pass-word. The default is set to “password.”

Remote Firmware Host Path This option provides a text entry field for the Remote Firmware Host path.

Event Log Export Host This option sets the IP address for the Event Log Export Host. The default is set to 0.0.0.0.

Event Log Export Path This option provides a text entry field for the Event Log Export path.



Remote File Host Provisioning

1. Remote Firmware Host : 0.0.0.0

2. Remote SCA Host : 0.0.0.0

3. Remote Host UserID : 0.0.0.0

4. Remote Host Password : 0.0.0.0

5. Remote Firmware Host Path : 0.0.0.0

6. Event Log Export Host : 0.0.0.0

7. Event Log Export Path :

8. General File Export Host : 0.0.0.0

9. General File Export Path :

Selection :


36 65K602XUG-48B

Total Access 5000 System Menu SCR and Auto-UpgradeTo provision for SCR and Auto-Upgrade, complete the following procedure:

NOTEUpgrading the SCM is only required when upgrading from a System Releaseprior to System Release 5.0. If upgrading from System Release 5.0 to 5.7.x,follow the normal upgrade procedure.




4. From the System Administration menu, select System Controlled Reboot (SCR), and press ENTER.

5. From the System Controlled Reboot menu, use Table 7 to complete the SCR.

Table 7. System Controlled Reboot (SCR) Options

Option Function

Operating Mode This option is used to set the SCR mode of operation. • Auto – SCR occurs only after Auto Upgrade has been

completed (i.e., after all modules have been updated). Auto Upgrade must be provisioned to use SCR.

• Manual – Allows the user to manually perform the SCR after all modules upgrades have completed.

• Scheduled – SCR will be executed at the time specified using the Scheduled Date/Time option (see below). This date and time must be after module upgrades are completed.

Scheduled Date/Time This option is used to set the date and time at which a scheduled SCR will occur. Date and time are set in the format MM/DD/YY HH:MM; the established value must be greater than one minute—but no more than 90 days—from the current time.

SCR Status This field shows the current status of the System Controlled Reboot function, including whether Auto Upgrade is set to use SCR.

65K602XUG-48B 37



7. From the Auto Upgrade Status menu, use Table 8 to complete the Auto Upgrade.

Table 8. Auto Upgrade Status Options

Option Function

Local File Cache Expire (Min) This option is used to specify how many minutes (0 to 1440) a flash file can be retained on the system before it is retrieved from the TFTP server. If a subsequent request for the same file is made within the Cache Expire time, the local, cached copy of the file is used, thus reducing upgrade time and network traffic. A value of zero disables TFTP flash file caching.The local cache is used during all TFTP “gets,” such as firmware upgrades, and .auc file and Total Access 5000 operations. The default is 480.

Auto Upgrade Config Basepath This option is used to set the BasePath prefix that precedes all Auto Upgrade configuration and module firmware files, indicat-ing where they are located in the same directory. This field applies to all Auto Upgrade module-specification entries.The Basepath argument should not contain spaces, commas, quotes, or other unusual characters that would generally be con-sidered invalid in a path specification. Although the system does not interpret the contents of this string, different operating systems have different rules concerning what constitutes valid characters and path/file separators.

Auto Upgrade Config Filename This option is used to set the Auto Upgrade configuration file-name that is to be retrieved from the firmware TFTP server. The Auto Upgrade configuration filename is supplied by ADTRAN. The file that is provided by ADTRAN typically has an .auc extension.

Auto Upgrade Mode This option is used to set the Auto Upgrade system operating mode:• Auto: Modules are automatically checked and upgraded after

power-up of the Total Access 5000 or on module insertion into the chassis. Actions controlled by the Config File Refresh Interval are also enabled.

• When this option is set to Auto and an upgrade is performed manually using the standard YModem or TFTP upgrade procedure, the module is immediately up/downgraded to the firmware version associated with the Auto Upgrade Config file.

• Manual: Modules are checked and upgraded only when instructed via SNMP or menus. Actions controlled by Refresh Interval are disabled.

• The manual setting should be used when it is necessary to deviate from the firmware versions that are associated with the Auto Upgrade Config file.

• Disabled: Auto Upgrade is disabled.The default Auto Upgrade Mode is Manual. To remove the Auto Upgrade Config filename, select Auto Upgrade Config Filename and press ENTER without typing in a new value.

38 65K602XUG-48B

8. From the Auto Upgrade Status menu, press S to start the upgrade.

Figure 23 displays an Auto upgrade in progress.

Figure 23. Upgrade in Progress (AUTO)


Config File Refresh Interval This option is used to set the Auto Upgrade refresh interval (0 to 744 hours), which controls how often the Auto Upgrades config-uration file should be retrieved from the TFTP server. When in Auto mode, this setting also controls how often Auto Upgrade evaluation operations are automatically performed. A value of zero (default) disables Auto Upgrade operations.

Auto Upgrade Retries This option is used to set the number of attempts (0 to 2) to retrieve the Auto Upgrade Config file if there are errors contact-ing the TFTP server or if an error occurs during the upgrade pro-cess. A value of zero (default) disables all retries.

Use SCR (defer reset) This option is used to enable or disable the use of a System Con-trolled Reboot (SCR) during the execution of an Auto Upgrade procedure. By enabling this feature (YES), a reset of the upgraded modules will be deferred to a scheduled time prede-termined by the system administrator using the System Con-trolled Reboot Menu, helping to mitigate release version interoperability problems. The default value is NO.

Table 8. Auto Upgrade Status Options (Continued)

Option Function



Auto Upgrade Status

1. Local File Cache Expire (Min) : 480 minutes

2. Auto Upgrade Config Basepath : \05.01.xx\

3. Auto Upgrade Config Filename : TA5000-05-01-xx_AUTO.auc

4. Auto Upgrade Mode : Manual

5. Config File Refresh Interval : 48 hours

6. Auto Upgrade Retries : 0

7. Use SCR (defer reset) : NO

8. Remote File Host Provisioning

System Release : TA5000-05-00-xx_AUTO.auc

Upgrades: 5/5, Errors: 0/0, Found: 13, Deferred: 0, Needed: 7, Active: 1

System( 00:31:33): Busy, upgrading slot 1/9 (1187250G1)

Slot (9 , 00:00:19): Busy, Ymodem send 10.7% (1187250G1, E01.013->E00.xx)

Slot (1 , 00:03:03): Complete, upgrade successful (1187180L1, E00.xx)

(F)irst Slot, (L)ast Selection : (P)rev Slot, (N)ext

(C)lear File Cache (R)eset Config File Cache

(A)bort, (S)tart, (D)etails

65K602XUG-48B 39


10. From the Auto Upgrade Status menu, press S to start the upgrade.

Figure 24 displays a SCM upgrade in progress.

Figure 24. Upgrade in Progress (SCM)

11. From the Auto Upgrade Status menu, press D to view detailed progress of the auto upgrade.

Figure 25 displays a concurrent auto upgrade.

Figure 25. Concurrent Auto Upgrade



Auto Upgrade Status

1. Local File Cache Expire (Min) : 480 minutes

2. Auto Upgrade Config Basepath : \05.07.xx\

3. Auto Upgrade Config Filename : TA5000-06-00-xx_SCM.auc

4. Auto Upgrade Mode : Manual

5. Config File Refresh Interval : 48 hours

6. Auto Upgrade Retries : 0

7. Use SCR (defer reset) : NO

8. Remote File Host Provisioning

System Release : TA5000-06-00-xx_SCM.auc


System( 00:32:22): Busy, upgrading slot 1/9 (1187250G1)

Slot (9 , 00:00:25): Busy, Ymodem send 11.3% (1187250G1, E01.013->E00.xx)

Slot (1 , 00:04:03): Complete, upgrade successful (1187180L1, E00.xx)

(F)irst Slot, (L)ast Selection : (P)rev Slot, (N)ext

(C)lear File Cache (R)eset Config File Cache

(A)bort, (S)tart, (D)etails



Concurrent Auto Upgrade Status


System( hh:mm:ss): Busy, retrieve file, 70.8%,

(A)bort, (S)tart

40 65K602XUG-48B

Software Fallback GuidelinesAlthough rare, it may be necessary to downgrade a system back to a previous firmware revision. Use the following guidelines for determining if fallback is required.

Lacking Features or FunctionalityIf the software loaded on a module loads correctly but does not contain the features or functionality required or the module appears to malfunction, the previous version software may be loaded on the module. Use the procedures outlined in the previous pages. Verify that the appropriate firmware files are available in the <EMS installation directory>/owareapps/ems_support/TFTPTransferFiles/ directory (for Auto TFTP upgrades) before initiating any software downloads.

Verify that the appropriate firmware files are available in the <EMS installation directory>/owareapps/ems_support/TFTPTransferFiles/system_releases/ directory (for Auto Upgrade utility) before initiating any software downloads.

TFTP InterruptionInterruption of the TFTP transfer from the EMS to the Total Access 5000/5006 System should not adversely affect the Total Access 5000/5006 System. In some cases, however, the module may remain busy and uncommunicative until the upgrade sequence times out.

Flash InterruptionIn the event that the transfer from the SCM to the access module is interrupted due to a reset or other abnormalities and the firmware file is not correctly or completely transmitted, the module times out, resets, and resumes operation with the previous version of software.

Fatal ErrorIf the module does not allow communications with the EMS after 15 minutes and appears permanently busy then a fatal error could have occurred. The module may have an incompat-ibility between the boot-loader firmware resident on the card and the software version that has been flashed.

ADTRAN endeavors to vigorously check firmware within the Product Quality group before releasing any new code in order to avoid such failures. In the event of an unresponsive module following an upgrade, contact Technical Support at (800) 726-8663 for further instruc-tions.

65K602XUG-48B 41


Total Access 5000/5006 Fallback ProcedureIf necessary, use the following procedure to rollback the software to a previous release.

Launching the Auto Upgrade Utility for Fallback (Total Access 5000/5006 Shelf)

To downgrade to the previous Total Access 5000 System Release, perform the following procedure:

NOTE• The Total Access 5000 System Release 3.1.xx designation is meant to be

generic and is used to indicate the downgrade to a previous release.• The time required to retrieve a firmware file depends on the file size and

the speed of the management link.





42 65K602XUG-48B

2. Select the Auto Upgrade based on System Release radio button, then click OK. The Auto Upgrade Wizard launches in a new window.


Figure 28. Auto Downgrade on System Release - Step 1 (Location)

3. Select (highlight) the appropriate Total Access 5000/5006 location from the location tree on the left of the Auto Upgrade on System Release - Step 1 (Location) screen. All locations subordinate to the selection display in the location frame.

4. Check the Select box next to the Location housing the Total Access 5000/5006 System to be downgraded.

5. Select the Chassis Type from the drop-down menu to designate the type of system to be downgraded.

(Select Total Access 5000 to downgrade a Total Access 5000 System.)

6. Click Next to execute.


65K602XUG-48B 43


Figure 29. Auto Downgrade on System Release - Step 2 (Search Result)




44 65K602XUG-48B

Figure 30. Auto Downgrade on System Release - Step 3

9. From the Auto Upgrade on System Release - Step 3 screen, click the Config File Name field Browse button (...) to select the Auto Upgrade Configuration File to be used for the fallback. The selected file name is displayed.

10. Select the time and date to perform the file transfer, or


• Choose Update in 2 minutes

NOTEReal-time status information is not available on the Scheduled Operationsscreen when Update Now is selected.

11. Ensure that the Use SCR (defer reset) is checked. If not, the modules reboot immediately after being upgraded.


This launches the Auto Upgrade on System Release - Step 4 (Summary) screen (refer to Figure 31).

This screen displays a summary of the scheduled items.

65K602XUG-48B 45



13. From the Auto Upgrade on System Release - Step 4 (Summary) screen, click Next to continue to the final screen.

14. Click Start Over to schedule another downgrade occurrence or Close Wizard to exit.


16. Schedule a System Controlled Reboot for the Total Access 5000/5006 shelf to reboot all modules into the new firmware. For detailed procedures, refer to “Software Fallback Guidelines” on page 41.

17. Verify the proper software revision for all Total Access 5000/5006 modules. For detailed procedures, refer to “Appendix D, Firmware Upgrade Verification”.

18. Restore the System SCA file archived before the system upgrade. For detailed procedures, refer to “Appendix E, System Provisioning Restore”.

46 65K602XUG-48B

Engineering Notes (Total Access 5000/5006 System)This section provides technical information on failure modes that could potentially occur during the upgrade process of a Total Access 5000/5006 System.

System Controller Module (SCM)

Remote File TransfersIncomplete or aborted firmware Remote File downloads destined for the SCM do not result in any system problems. The new code image is held in internal RAM space before programming the flash so a special boot mode is not required. The flash is programmed only after the complete file has been received and validated.

Load InterruptionsAfter an Network failure, card failure, or power failure, the SCM recovers from the Remote File session. The SCM does not have to be reseated, recovered manually through the Restart option, or repaired. In this situation the Remote File transfer must be rescheduled using the EMS.

Switch Module 2GE (SM 2GE)

Remote File TransfersIn the event of a Network or a power failure, the SCM sends an abort command to the SM 2GE immediately. The SM 2GE recovers without reseating, terminal actions, or repair. If the abort message is not sent from the SCM, the SM 2GE times out in ten (10) minutes and resumes normal operation.

Flash TransfersIn the event of a SM 2GE link failure, SCM link failure, or power failure during the flash transfer from the SCM to the SM 2GE, the SM 2GE recovers without reseating, resetting, or repairing. After approximately 30 seconds of not receiving firmware from the SCM, the SM 2GE aborts the download and returns to normal operation.

65K602XUG-48B 47


Modules

Remote File TransfersIn the event of a Network or a power failure, the SCM sends an abort command to a module immediately. The module recovers without reseating, terminal actions, or repair. If the abort message is not sent from the SCM, the module times out in 10 minutes and resumes normal operation.

Flash TransfersIn the event of a module link failure, SCM link failure, or power failure during the flash transfer from the SCM to the module, the module recovers without reseating, resetting, or repairing. After approximately 30 seconds of not receiving firmware from the SCM, the module aborts the download and returns to normal operation.

48 65K602XUG-48B

Appendix ASystem Configuration Archive

Scope of this AppendixThis appendix details the minimum steps needed to complete a System Configuration Archive (SCA).

In this AppendixThis appendix contains the following topics:

Table A-1. Appendix A Topics

Topic See Page

Saving an SCA File A-2

Configure the SCA (Menu) A-7

Configure the SCA (CLI) A-9

65K602XUG-48B A-1


Saving an SCA FileTo save the current system configuration to a System Configuration Archive file, complete the following steps:

1. From the EMS Launch Console, select System Configuration Archive from the Service menu (refer to Figure A-1).

This launches the SCA Operation Choice dialog box (refer to Figure A-2).

Figure A-1. System Configuration Archive Menu

Figure A-2. SCA Operation Choice Window

2. Select the Schedule radio button shown in Figure A-2, then click OK.

This launches the System Configuration Archive Wizard, beginning with the System Configuration Archive - Step 1 screen (refer to Figure A-3).

A-2 65K602XUG-48B

Appendix A, System Configuration Archive - Saving an SCA File

Figure A-3. System Configuration Archive - Step 1

3. Select the appropriate Total Access 5000/5006 location from the location tree on the left of the System Configuration Archive - Step 1 screen. All locations subordinate to the selection display in the location frame.

4. Check the Select box next to the Location housing the Total Access 5000/5006 System to be archived.

5. Select the Chassis Type from the drop-down menu to designate the type of system to be archived.

(Select Total Access 5000 to upgrade a Total Access 5000/5006 System.)


This launches the System Configuration Archive - Step 2 screen (refer to Figure A-4).

65K602XUG-48B A-3



7. Select the Total Access 5000/5006 from the search results by selecting the corresponding check boxes shown on the System Configuration Archive - Step 2 screen. The search results provide information about the Total Access 5000/5006: IP Address, System Name, and System Description.



A-4 65K602XUG-48B

Appendix A, System Configuration Archive - Saving an SCA File


9. From the System Configuration Archive - Step 3 screen, select the Start Date & Time to perform the System Configuration Archive or choose Collect Now .



65K602XUG-48B A-5



11. Verify that the System Configuration Archive -Step 4 screen indicates that the SCA collection request is submitted to the server.

12. To verify that the SCA retrieval was successful, explore the following directory to check that the new SCA file is present.

<EMS installation directory>/owareapps/ems_support/TFTPTransferFiles/

The format for the SCA file is:

<TA5000 IP Address>_YYYYMMDD_##_TA5000

Where:

YYYY = Year

MM = Month

DD = Date

## = A count of SCA completed on the given day; starting with 01.

For example: “192.168.1.5_20080416_01_TA5000”


14. Click Start Over to schedule another SCA or Close Wizard to exit.

A-6 65K602XUG-48B

Appendix A, System Configuration Archive - Configure the SCA (Menu)

Configure the SCA (Menu)To configure the SCA, complete the following:




4. From the System Administration menu, select System Configuration Archive (SCA), and press ENTER.

Figure A-7 displays the SCA menu.

Figure A-7. System Configuration Archive (SCA) Menu

5. From the System Configuration Archive (SCA) menu, select SCA Autosave Provisioning, and press ENTER.

6. From the SCA Autosave Provisioning menu, use the following to provision the SCA:

TID: HSV00001 Total Access 5000/5006 System MM/DD/YY

HH:MM


System Configuration Archive (SCA)

1. SCA Autosave Provisioning

2. SCA Controller Restore Provisioning

3. SCA Restore Provisioning

4. SCA Operations

Selection :


65K602XUG-48B A-7


Table A-2. SCA Autosave Provisioning Options

Option Function

Autosave System Use this option to enable or disable the Autosave system. There is a five-minute delay after initial power-up of the SCM before an Autosave operation is performed. This allows sufficient time for the shelf and provision settings on the SCM and modules to stabilize. The default is Disable.

Autosave Only if Prov Changes Use this option to allow the administrator to reduce the number of redundant Autosave operations and SCA files on the TFTP server. This is accomplished by instructing the SCM to perform Autosave operations only if provisions have been changed on the SCM or an installed MUX or access module. The default is Enable.

Autosave Filename Prefix The Autosave Filename Prefix is a 0 to 30-character string that is used to construct the first part of the SCA filename.

Autosave Filename Suffix The Autosave Filename Suffix is a 0 to 8-character string that is used to construct the trailing type, or extent portion, of the SCA filename.

Max Autosave File Instances The Max Autosave File Instances field determines the maxi-mum number of SCA filenames to save to the TFTP server. This is often called a backup file rotation scheme, where the last “n” files are always maintained on the backup medium. The valid values are 1 to 7. The default is 1.

Autosave Time (Hour) Use this option in conjunction with the Autosave Time (Minute) option to set the time of day, after which the Autosave SCA file can be written to the remote TFTP server. These fields allow the administrator to configure the Total Access 5000/5006 shelves on the customer network to write their Autosave SCA files at different times. This prevents the network conges-tion that might occur if all the shelves attempt to simulta-neously save their SCA files. The valid values are 0 to 23. The default is 0.

Autosave Time (Minute) Refer to the Autosave Time (Hour) option description above for information. The valid values are 0 to 59. The default is 0.

Autosave Retries Use this option to set the number of times the system re-attempts an Autosave operation in the event of a failure. The valid values are 0 to 99. The default is 5.

A-8 65K602XUG-48B

Appendix A, System Configuration Archive - Configure the SCA (CLI)

Configure the SCA (CLI)This section contains procedures on how to complete the following:

• Log-on to the Total Access 5000

• Configure the SCA

Log On to the Total Access 5000For initial deployment, only craft access is available. A serial cable with a male DB-9 connector on the Total Access 5000/5006 end is required.

To log on to the Total Access 5000/5006 command line interface, complete the following:


• 9600 baud rate

• 8-data bits

• No parity

• 1-stop bit

• No flow control


3. After completing the prerequisite procedures above, pressing any key displays the logon prompt.

The Total Access 5000 System Logon prompt displays the following information:


Username:

NOTEThe account name and password are case sensitive.Default accounts are ADMIN, READONLY, READWRITE, and TEST. Thedefault password for each of these accounts is PASSWORD. The privilege tochange passwords, account names, and privileges are included in theADMIN account.At the Username field, input the Username (ADMIN), andpress ENTER.


5. Upon entering the correct password, the Total Access 5000 CLI introduction banner displays the following information:


Username:ADMIN

Password:********

Last Login Date : Nov 10 2008 10:19:17

Last Login Type : IP Session(CLI) ‐ 192.168.1.3

Login Failures : 0 (Since Last Login)

65K602XUG-48B A-9


: 14 (Total for Account)

TA5000>

6. Type enable, and press ENTER to enable the privileged commands.

The Total Access 5000 system displays the following information:

TA5000>enable

TA5000#

NOTEThe privileged commands (Enable prompt) are designated by the # prompt.

Configure the SCATo configure the SCA, complete the following:

1. From the Enable prompt, type config term, and press ENTER to access the Global Con-figuration prompt.

2. From the Global Configuration prompt, type sca, and press ENTER.

3. From the SCA Configuration prompt, type autosave, and press ENTER.

The autosave command enables the SCA autosave feature.

4. From the SCA Configuration prompt, type max‐instances <1‐7>, and press ENTER.

The max-instances <1-7> command sets the maximum number of autosave file instances.

5. From the SCA Configuration prompt, type permit‐restore [controller|modules], and press ENTER.

The permit-restore [controller|modules] command enables SCA restores.

6. From the SCA Configuration prompt, type permit‐restore controller [sca|security|snmp], and press ENTER.

The permit-restore controller [sca|security|snmp] command enables the type of provisioning items to restore to the controller using SCA.

7. From the SCA Configuration prompt, type permit‐restore controller network [general|interface], and press ENTER.

The permit-restore controller network [general|interface] command enables the restoration of network provisioning settings to the controller using SCA.

8. From the SCA Configuration prompt, type permit‐restore modules [<shelf/slot>|empty‐slots|in‐service], and press ENTER.

The permit-restore modules [<shelf/slot>|empty-slots|in-service] command selects the modules to restore using SCA.

9. From the SCA Configuration prompt, type prefix word, and press ENTER.

The prefix WORD command selects the file prefix of the SCA auto-save file name.

10. From the SCA Configuration prompt, type suffix word, and press ENTER.

The prefix WORD command selects the file extension of the SCA auto-save file name.

11. From the SCA Configuration prompt, type retries <0‐99>, and press ENTER.

The retries <0-99> command selects the number of autosave retries.

A-10 65K602XUG-48B

Appendix A, System Configuration Archive - Configure the SCA (CLI)

12. From the SCA Configuration prompt, type schedule <hh:mm>, and press ENTER.

The schedule <HH:MM> command sets the hour and minute of the scheduled SCA autosave.

13. From the SCA Configuration prompt, type update‐only, and press ENTER.

The update-only command enables autosave updates to the SCA autosave file only if there are provisioning changes.

65K602XUG-48B A-11


A-12 65K602XUG-48B

Appendix BMonitoring an Auto Upgrade

Scope of this AppendixThis appendix details the minimum steps needed to monitor an auto upgrade.


Table B-1. Appendix B Topics

Topic See Page

Monitor an Auto Upgrade Session B-2

Alternative Large-Scale Upgrade/Downgrade Monitor Procedure B-3

65K602XUG-48B B-1


Monitor an Auto Upgrade SessionEach Total Access 5000/5006 System can be monitored from the scheduled operations window. To monitor a particular auto upgrade session, use the following procedure:

1. Select Scheduled Operations from the Control button (EMS Launch Console)

2. Select Auto Upgrade Scheduled Items from the drop-down list at the top of the window, and press Query.

3. Double-click on the line that contains the scheduled item to be monitored. A new window will open.

4. Click the Update Status checkbox to get an automatic update every 10 seconds.

5. Repeat steps 3 and 4 for each Auto Upgrade to be monitored.

6. The Auto Upgrade Process will proceed as follows:

a. Initially, the status will be “Idle” or some other status depending on results of the last upgrade.

b. Once the upgrade begins, the SCM proceeds to download the files from the EMS server, transfers the files to the appropriate modules, and prompts each module to reboot.

c. The Total Access 5000/5006 upgrade is complete when the upgrade status indicates Complete or Idle.

7. Select Close to close the monitor window.

NOTEWithin the Scheduled Item Details monitor windows, the Switch Module andshelf controller operations use the following “slot numbers”: • slot 252 = SM A• slot 253 = SM B• slot 254 = SCM

B-2 65K602XUG-48B

Appendix B, Monitoring an Auto Upgrade - Alternative Large-Scale Upgrade/Downgrade Monitor Procedure

Alternative Large-Scale Upgrade/Downgrade Monitor Procedure

As an alternative to the EMS monitoring feature, the SNMP OID adTAeScuAutoUpgradeStatus (1.3.6.1.4.1.664.2.241.11.10.1.1.254) can be used to retrieve the status of each Total Access 5000/5006 chassis.

NOTEThe OID value above is using the slot index 254, which is the index of theSCM. Since the SCM is always installed in any chassis, it can be used to checkthe shelf Auto Upgrade status as described below.

Description of the adTAeScuAutoUpgradeStatus OIDThe UpgradeStatus query is always directed to one of the slots in the Total Access shelf. For example, to get the Auto Upgrade status of the module in slot 3, perform an SNMP 'get' on the following OID:

adTAeScuAutoUpgradeStatus.3

The response from this 'get' is a single string describing the state of both the Auto Upgrade system (shelf state) and the upgrade state of the module in the specified slot (slot state).

The adTAeScuAutoUpgradeStatus response string will always be of the following form:

Shelf:<shelf_state>(hh:mm:ss, a,b,c,d,e,f,g), Slot:<slot_number>:<slot_status_string>

Table B-2 displays the shelf state.

Use the shelf status to determine if the upgrade has completed.

Table B-2. Shelf State

State Definition

Busy The shelf is currently performing an Auto Upgrade operation.

Idle The shelf has not performed an Auto Upgrade operation. Or, if an SCM upgrade was part of the Auto Upgrade, the upgrade could be complete. Check firmware revisions to verify upgrade was completed.

Complete The most recent Auto Upgrade is complete and the shelf is Idle.

Cancelled An Auto Upgrade operation has been cancelled, the shelf is Idle.

Error (<shelf_error_description>)

65K602XUG-48B B-3


B-4 65K602XUG-48B

Appendix CViewing SCA Restoration Status

Scope of this AppendixThis appendix details the steps for viewing the SCA restoration status by either using the Total Access 5000 Command Line Interface (CLI) or the Total Access 5000 Menus.


Table C-1. Appendix C Topics

Topic See Page

View SCA Restoration Status (CLI) C-2

View SCA Restoration Status (Menu) C-2

65K602XUG-48B C-1


View SCA Restoration Status (CLI)To check or monitor the SCA Restoration Status, perform the following steps:

1. Perform a Telnet cut-through to the Total Access 5000/5006.

2. Log on to the Total Access 5000 CLI and type show sca restore‐status.

Refer to the Total Access 5000 CLI Dictionary, P/N 65K60CLI-35, for command listings.

3. The SCA restore status will indicate Idle if no SCA restoration is in progress; otherwise, it will indicate the progress of the active SCA restoration.

View SCA Restoration Status (Menu)To check or monitor the SCA Restoration Status, perform the following steps:





5. From the System Configuration Archive (SCA) menu, select SCA Operations, and press ENTER.

6. From the SCA Operations menu, select SCA Restore Status, and press ENTER.

7. The SCA restore status will indicate “Idle” if no SCA restoration is in progress; otherwise, it will indicate the progress of the active SCA restoration.

C-2 65K602XUG-48B

Appendix DFirmware Upgrade Verification

Scope of this AppendixThis appendix details the steps to verify the Total Access 5000 System firmware revisions.


Table D-1. Appendix D Topics

Topic See Page

Verify Firmware Upgrade (EMS) D-2

Alternative Large-Scale Total Access 5000/5006 Firmware Version Verification Pro-cedure

D-4

Verify Firmware Upgrade (CLI) D-4

Verify Firmware Upgrade (CLI) D-4

65K602XUG-48B D-1


Verify Firmware Upgrade (EMS)This subsection describes how to verify that the Total Access 5000/5006 System reflects the new firmware revisions.

1. Select Managed Objects from the Config menu.

2. Use the product selection pull-down to select Total Access 5000/5006 System.

3. Select the Total Access 5000/5006 System to be verified (Figure D-1).

Figure D-1. Select Total Access 5000/5006 from Managed Object Manager List

4. Click Edit.

5. Click Slot Type List (Figure D-2) to view a list of the Total Access 5000/5006 System modules and their current firmware revision. Verify that the modules have been upgraded to the correct revision. Shelf 1 is displayed. Use the arrow at the base of the vertical window adjust bar to view subsequent shelves.

D-2 65K602XUG-48B

Appendix D, Firmware Upgrade Verification - Verify Firmware Upgrade (EMS)

Figure D-2. Total Access 5000/5006 Slot Type List

6. Click Close to exit the 3-panel GUI.

65K602XUG-48B D-3


Alternative Large-Scale Total Access 5000/5006 Firmware Version Verification Procedure

As an alternative to the EMS GUI, the SNMP OID adGenSlotProdSwVersion (1.3.6.1.4.1.664.5.13.2.4.1.6) can be used to retrieve the firmware version of each Total Access 5000/5006 module. The slot of the module to be retrieved should be appended to the OID. For example, to retrieve the firmware version of the module in slot 7, perform a 'get' on the OID 1.3.6.1.4.1.664.5.13.2.4.1.6.7.

The index values of the slots in the Total Access 5000/5006 are as follows:

• Slots 1-22:Index = 1-22

• SM A:Index = 252

• SM B:Index = 253

• SCM:Index = 254

If a 'get' is done on an empty slot number, the response will be the error code “No such name”.

Verify Firmware Upgrade (CLI)This subsection describes how to verify that the Total Access 5000/5006 System reflects the new firmware revisions.

1. From the Enable menu, type show system inventory, and press ENTER.

2. Verify that the modules have been upgraded to the correct revision.

D-4 65K602XUG-48B

Appendix ESystem Provisioning Restore

Scope of this AppendixThis appendix details the steps needed to restore the Total Access 5000 System provisioning.


Table E-1. Appendix E Topics

Topic See Page

Restore System Provisioning (EMS) E-2

Restore System Provisioning (CLI) E-10

Restore System Provisioning (Menu) E-11

65K602XUG-48B E-1


Restore System Provisioning (EMS)

NOTEAll modules in the shelf must be in Out of Service - Maintenance or Out ofService - Unassigned for the SCA restoration.

To restore a system provisioning using a System Configuration Archive file, complete the following steps:

1. From the EMS Launch Console, select System Configuration Archive from the Service Menu (refer to Figure E-1).

This launches the SCA Operation Choice dialog box (refer to Figure E-2).

Figure E-1. System Configuration Archive Menu

Figure E-2. SCA Operation Choice Window

2. Select the Restore radio button (refer to Figure E-2), then click OK.

This launches the System Configuration Archive Wizard, beginning with the System Configuration Archive - Step 1 screen (refer to Figure E-3).

E-2 65K602XUG-48B

Appendix E, System Provisioning Restore - Restore System Provisioning (EMS)

Figure E-3. System Configuration Archive - Step 1

3. Select (highlight) the appropriate Total Access 5000/5006 location from the location tree on the left of the System Configuration Archive - Step 1 screen. All locations subordinate to the selection display in the location frame.

4. Check the Select box next to the Location housing the Total Access 5000/5006 System to be restored.

5. Select the Chassis Type from the drop-down menu to designate the type of system to be restored.

(Select Total Access 5000 to upgrade a Total Access 5000/5006 System.)

6. Click Next to execute.

This launches the System Configuration Archive - Step 2 screen (refer to Figure E-4).

65K602XUG-48B E-3


Figure E-4. System Configuration Archive - Step 2

7. Select the Total Access 5000 from the search results on the System Configuration Archive - Step 2 screen by selecting the corresponding check boxes. The search results provide information about the Total Access 5000/5006: IP Address, System Name, and System Description.


This launches the SCA Restore Operation - Step 3 screen (refer to Figure E-5).

E-4 65K602XUG-48B


Figure E-5. SCA Restore Operation - Step 3

9. From the SCA Restore Operation - Step 3 screen, select the SCA Restore File to be used.


This launches the SCA Restore Operation- Step 4 screen (refer to Figure E-6).

65K602XUG-48B E-5



11. From the SCA Restore Operation - Step 4 screen, select the SCM provisioning to be restored.



The SCA Restore Operation - Step 5 screen displays the SCA Module Restore Provisioning options.

E-6 65K602XUG-48B



NOTETo ensure that all modules are restored, click the Select All button, and checkthe Restore In-Service Module Provisions box.

13. Select the modules to be restored.


65K602XUG-48B E-7



14. The SCA Restore Operation - Step 6 screen displays an SCA restore verification window. To verify the SCA restoration, click Next.

This launches a configuration dialog box (refer to Figure E-9).

Figure E-9. Verification Dialog Box

15. To continue, click Yes.

This launches an SCA Transfer Status screen (refer to Figure E-10).

E-8 65K602XUG-48B


Figure E-10. SCA Transfer Status Window

16. The SCA information is transferred to the Total Access 5000/5006 shelf, and the SCA restore is complete.

NOTEA Switch Module reset and subsequent SHDSL link retrains are normal.


18. Click Close Wizard to close the window.

19. Verify that the SCA restoration completes. For detailed procedures, refer to “Appendix C, Viewing SCA Restoration Status”.

The fallback procedure is now complete.

65K602XUG-48B E-9


Restore System Provisioning (CLI)To restore a Total Access 5000/5006 to the provisioning settings saved in an SCA file, complete the following:

1. Access the Global Configuration prompt.ChassisId#configure terminal

2. Configure the remote SCA Host IP address.ChassisId(config)#ip file‐server sca host A.B.C.D

3. Configure the remote SCA filename.

ChassisId(config)#ip file‐server sca filename WORD

4. Configure the SCA options.ChassisId(config)#sca

5. Use the following versions of the permit restore command to enable the restoration of provisioning settings of the required modules and controllers. Use the no form of each to disable the restoration of provisioning settings of the required modules and controllers.

• Restore the provisioning settings of the specified slot,

ChassisId(config‐sca)#permit‐restore modules <shelf/slot>

• To restore the provisioning settings of all module slots, type

ChassisId(config‐sca)#permit‐restore modules

• To restore the provisioning settings of all in-service slots, type

• ChassisId(config‐sca)#permit‐restore modules in‐service

• To restore the provisioning settings of all empty slots, type permit‐restore modules empty‐slots, and press ENTER.

• To restore the controller SCA provisioning settings, type permit‐restore controller sca, and press ENTER.

• To restore the controller SNMP provisioning settings, type permit‐restore controller snmp, and press ENTER.

• To restore the controller network general provisioning settings, type permit‐restore controller network general, and press ENTER.

• To restore the controller network interface provisioning settings, type permit‐restore controller network interface, and press ENTER.

• To restore the controller network interface provisioning settings, type permit‐restore controller security, and press ENTER.

• To restore the controller network interface provisioning settings, type permit‐restore controller, and press ENTER.

6. Return to the Enable prompt.

ChassisId(config‐sca)#end

7. Initiate the SCA restore.

ChassisId#copy tftp sca

8. Verify the SCA restore.

ChassisId#show sca restore‐status

E-10 65K602XUG-48B

Appendix E, System Provisioning Restore - Restore System Provisioning (Menu)

Restore System Provisioning (Menu)

NOTEAll modules in the shelf must be in Out of Service - Maintenance or Out ofService - Unassigned for the SCA restoration.

To restore system provisioning using a System Configuration Archive file, complete the following steps:





5. From the SCA Module Restore Provisioning menu, use the following to provision the SCA restore:

Table E-2. SCA Module Restore Provisioning Menu Options

Option Function

Restore These columns represent whether SCA restore to the corre-sponding slot has been enabled by the administrator. If the field is displayed in inverse video, some condition (such as an empty slot, user disable, or exclusion due to the card being in-service) exists that prevents SCA restore to this slot. The default value is NO. Selection of an individual slot number will toggle the restore state of the slot.

Restore Provisions To Modules This option acts as a global override to disable the restore of all access and switch module provisioning, and is useful in pro-tecting the current access and switch module settings during SCA restore operations to the SCM.If this field is set to Disable, no access or switch module provi-sions are altered during an SCA restore regardless of the other settings on this screen. The default is Disable.

Restore In-Service Module Provi-sions

This option controls whether SCA restore operations should affect in-service access and switch modules. Setting this field to Disable prevents in-service modules from being affected by an SCA restore. The default is Disable.

Restore to Empty Slot(Pre-Provision)

This option controls whether SCA restore operations should attempt to pre-provision empty slots. If an empty slot is pre-provisioned, inserting a line card match-ing the type of card present in the SCA file for that slot results in automatic reprovisioning of the card to the settings present in the SCA file. The default is Disable.

65K602XUG-48B E-11


E-12 65K602XUG-48B

Appendix FT1 EFM Upgrades

Scope of this AppendixThis appendix summarizes the upgrade process for the Total Access 5000 T1 8-Port Line Module (P/N 1187300L1).


Table F-1. Appendix F Topics

Topic See Page

Introduction F-2

Release Details F-2

65K602XUG-48B F-1


IntroductionIn Total Access 5000 System Release 6.0, the T1 8-Port changes to a new internal provisioning model. This means the T1 8-Port now handles certain provisioning, such as EFM groups, system uplinks, and timing information the same way as every other Total Access 5000 module. This ensures uniform CLI usage and card functionality across the system.

However, as the provisioning model changes, the upgrade process has automatically been incorporated through Sequential Auto Upgrade for this module. This results in the T1 8-Port upgrading to an intermediate build and then to the final 6.0.X release version.

NOTEThe auto-upgrade mode must be set to automatic in order for the T1 8-Port tocomplete the upgrade successfully.

Release DetailsThe intermediate build is only required if upgrading from specific releases. A two-step upgrade, which will be handled by Auto Upgrade automatically when using AUTO mode, to Total Access 5000 System Release 6.0 is required if using these releases with the T1 8-Port. The releases are as follows:

• Total Access 5000 System Release 5.0.X

• Total Access 5000 System Release 5.1.0, 5.1.1, and 5.1.2

• Total Access 5000 System Release 5.5.0 through 5.5.3

• Total Access 5000 System Release 5.7.0

The following releases are not impacted:



• Total Access 5000 System Release 5.5.6, 5.5.6.1, and anything out of 5.5.X forward


• Total Access 5000 System Release 5.7.2 and anything out of 5.7.X forward

F-2 65K602XUG-48B

65K602XUG-48B G-1

Appendix G, Warranty and Customer Support

Appendix GWarranty and Customer Support

WarrantyADTRAN will replace or repair our products within the warranty period if they do not meet their published specifications or fail while in service. Warranty information can be found at www.adtran.com/warranty.

ADTRAN Customer CareFrom within the U.S.: 1.800.726.8663

From outside the U.S.: +1 256.963.8716

ADTRAN SalesPricing/Availability: 1.800.827.0807

ADTRAN Technical SupportADTRAN offers Technical Support Engineering services for all of our products. These services are provided at no charge during the product warranty period.

Pre-Sales Applications/Post-Sales Technical Assistance: 1.800.726.8663

Standard hours: Monday - Friday, 7 a.m. - 7 p.m. CSTEmergency hours: 7 days/week, 24 hours/day

Email: [email protected]: http://www.adtran.com/getsupport

ADTRAN Repair/CAPSReturn for Repair/Upgrade: 1.256.963.8722

Repair and Return AddressContact CAPS prior to returning equipment to ADTRAN.

ADTRAN, Inc.CAPS Department901 Explorer BoulevardHuntsville, Alabama 35806-2807

http://www.adtran.com/warranty

Carrier Networks Division901 Explorer Blvd.

Huntsville, AL 35806U.S.A.

http://www.adtran.com

ADTRAN CUSTOMER CAREFrom within the U.S. 1.800.726.8663

From outside the U.S. +1 256.963.8716

PRICING AND AVAILABILITY1.800.827.0807

upgr

ade

guid

e

total access 5000_5006 upgrade mop - system release 6.0.2

Documents