SR-ES R10. IOM-IOM3 Migration Via 205620SAM Procedure

7750 SR & 7450 ESS R10.
0
IOM1/2-IOM3 Migration via 5620 SAM
Procedure
IP-GPEC TEAM
3FQ 24026 70XF PGZZA

Table of Contents
Introduction .............................................................................................................. 4
General ............................................................................................................ 4
Purpose ........................................................................................................... 4
Restrictions ...................................................................................................... 5
Intended Audience ............................................................................................. 5
Document Conventions ........................................................................................ 5
Document Revision History .................................................................................... 5
Web Site .......................................................................................................... 6
IP-GPEC Announcements ...................................................................................... 6
Feedback ......................................................................................................... 6
Document Issues ................................................................................................ 6
Timeline .......................................................................................................... 6
References ........................................................................................................ 7
Reference List ................................................................................................... 7
Requirements ..................................................................................................... 8
Pre-requisites ................................................................................................... 8
Engineering Skills ............................................................................................... 8
Required Materials ............................................................................................. 8
Pre-Migration ............................................................................................................ 9
Pre-Migration Tasks.............................................................................................. 9
Configuring the Chassis Mode ................................................................................. 9
Backup NE configuration on SAM ............................................................................. 9
Tech-support File ............................................................................................... 9
Saving Log File ................................................................................................. 10
Required Outputs .............................................................................................. 11
Migration ................................................................................................................ 12
Migration Tasks .................................................................................................. 12
Card Migration Management Procedures .................................................................. 12
Post-Migration .......................................................................................................... 19
Post-Migration Tasks ........................................................................................... 19
Information ..................................................................................................... 19
Required Outputs .............................................................................................. 19
Tech-support File .............................................................................................. 20
Back out ................................................................................................................. 21
Back out Tasks................................................................................................... 21
Introduction .................................................................................................... 21
Issue 1 ........................................................................................................... 21
Issue 2 ........................................................................................................... 21
APPENDIX-A: Additional Information ............................................................................... 24
Swapping the IOM Cards ....................................................................................... 24
Tasks ............................................................................................................. 24
7750 SR & 7450 ESS R10.0 IOM1/2-IOM3 Migration via 5620 SAM Procedure 3FQ 24026 70XF PGZZA
Introduction
General
Purpose The purpose of this document is to provide the migration procedure of the existing IOM1/2s to
IOM3s modules with 5620 SAM Application. The detailed procedure includes highlight service
impact and back out scenarios.
CAUTION: This Procedure is 100% Service Impacting.

You can use a 5620 SAM GUI utility called the „Card Migration Event Manager’ to facilitate
the transition to an IOM3 on one or more 7450 ESS or 7750 SR NEs. The Card Migration
Event Manager transfers the existing IOM and MDA configurations to new modules with
service interruption.
The 5620 SAM Card Migration Event Manager can do the following:
Upgrade from an IOM1/2 to an IOM3 while retaining the same MDAs.
Upgrade from one MDA type to a newer MDA type that has compatible features.
Upgrade an IOM and the associated MDAs in one operation.
WARNING:
The software version of the products used in this procedure are:
o 10.0 R5 on 7750 SR
o 10.0R3 on 5620 SAM
An IOM downgrade, for example, a migration from an IOM3 to an IOM2, is not
supported.
Continued on next page
Copyright © Alcatel-Lucent GPEC TEAM Page 4 of 25

General, Continued
Restrictions Below are restrictions for IOM1/2-IOM3 migration with SAM from Reference [1].
General
Only the 5620 SAM admin user, or a user with an assigned administrator scope of
command role, can create, modify, or execute a migration event.
The migration functions are not available to 5620 SAM OSS clients.
You may need to re-enable SNMP on an NE after the NE reboots following a
migration event.
You can only perform a card migration if the description associated with the cards
being migrated does not contain any numerical values.
IOM-specific
An IOM downgrade, for example, a migration from an IOM 3 to an IOM 2, is not
supported.
MDA-specific:
You cannot migrate an empty MDA slot to an MDA.
MDA migration is limited to MDAs of the same physical transmission type; for
example, migration from a SONET MDA to an Ethernet MDA is not supported.
You cannot upgrade an MDA that is integrated with an IOM, for example, an IMM.
For MDAs, you can migrate only to an MDA of similar capacity that has the same or a
greater number of ports.
Intended This document is intended for internal use only and shall be distributed among the people
Audience listed below.
Integration Engineers
Field Engineers
Technical Project Managers
Project Managers
Document Yellow highlighted text depends on the network configuration and can be different in your
Conventions setup.
Document The below table shows the revision history of this document.
Revision History
Date Author Revision Change
14.08.2012 Ozan GONULTAS 1.0 Document Creation
16.08.2012 Cihan TOKA 1.1 Document Review
20.09.2012 IP-GPEC Team 1.2 Document Review
27.09.2012 Ozan GONULTAS 1.3 10.0 R5 Updates
NOTE: Please check IP-GPEC Homepage for the most recent version of this document.

General, Continued
Web Site You can visit the following page for other IPD product documents.
https://all1.na.alcatel-lucent.com/Teams/GCDNetworks/IPGPEC/default.aspx
IP-GPEC In order to be kept updated with the most recent news from IP GPEC Team, please join the
Announcements engage group using the link below.
https://engage.alcatel-lucent.com/groups/ipd-gpec
Feedback For any feedback on this document, please contact to @DL_TR_PUB_GPEC_TR_IPD
Document If you find any issues about this document, please raise a ticket for NPIf-IPD-TR Workgroup.
Issues Simply, send email to support@alcatel-lucent.com including:
Cares Workgroup
Your contact information
Document Name
Issue Description
Timeline
CAUTION: The installation takes around 20-30 minutes depending on the

configuration. Validated timeline for this procedure is below:
Operation Expected Time

Pre-Migration Tasks 5 minutes
Migration 15 minutes
Post-Migration Tasks 5 minutes
TOTAL 25 minutes

References
Reference List You can find the list of references referred in this document in the table below:
No Title
1 Alcatel-Lucent 5620
SERVICE AWARE MANAGER | RELEASE 10.0 R5 USER GUIDE
3HE 06993 AAAA TQZZA Edition 01
3 7750 SR
Basic System Configuration Guide
93-0070-09-02

Requirements
Pre-requisites
CAUTION: Use an ESD-preventive wrist or ankle strap and always connect an

ESD strap to the grounding plug on the front of the chassis and ensure that the device
components is placed on an anti-static surface.
Engineering Person who is in charge of performing procedures explained in this document should be
Skills capable of;
7750 SR software boot process and cards:
- IOM, IMM, MDA, CPM, Compact Flash
Experience of 7750 SR hardware and software installation:
- Knowledge of card installation, checking 7750 SR logs
Required Before swapping out, the following items will be required.

Materials
Required Action / Information
Terminal Emulation Software HyperTerminal, SecureCRT, Putty etc.
Cross-head Screwdriver -
Antistatic Wrist Strap Always use the antistatic wrist strap before you touch
the hardware
Admin User Login 5620 SAM admin user, or a user with an assigned
administrator scope of command role, can create,
modify, or execute a migration event.

Pre-Migration
Pre-Migration Tasks
Configuring the Depending on the chassis and IOM type, the following modes can be configured;
Chassis Mode Make sure that the chassis-mode is compatible with existing and migrated IOMs on the node.
To check the chassis mode of the system, simply run the command below:
A:IP-GPEC# show chassis
========================================================================
Chassis Information
========================================================================
Name : SR12-1
Type : 7750 SR-12
. . . >>>Output Omitted
Admin chassis mode : b
Oper chassis mode : b
. . . >>>Output Omitted
Chassis Mode Corresponds to … Backwards compatible for …

A iom-20g iom-20g-b, iom2-20g, iom3-xp
B iom-20g-b iom2-20g, iom3-xp
C iom2-20g iom3-xp
D iom3-xp
For more information refer to Reference [2].
Backup NE Use the 5620 SAM to back up the device configuration of each target NE. This Backup is used
configuration to back out the system to initial configuration if a problem occurs during the migration.
on SAM
CAUTION: When you attempt a migration on a NE that does not have a recent
configuration backup in the 5620 SAM database, the 5620 SAM raises an alarm and the
migration fails.
See chapter 23 in Reference [1] for information about performing NE backups.
Tech-support Generate an admin tech-support file:

File
A:SR12-1 # admin tech-support cf3:\pre_migration
Processing CPM...
Second Pass
Processing CPM...
Processing CPM in Slot B...
Processing IOM in Slot 2...
Processing MDA in 2/1...
Done...

Pre-Migration Tasks, Continued
Saving Log File Connect to NE by Terminal Emulation Software.

The output of the following each command should be taken in a log file in order to refer back to
the status of the device before it was rebooted.
For example, If you use SecureCRT, Click Options->SessionOptions->Log File;

Pre-Migration Tasks, Continued
Required Execute below commands and save the outputs:

Outputs NOTE: To disable pagination on command output; execute „environment no more‟ command.
 show version
 show chassis
 show system memory-pools
 show bof
 show card
 show card detail
 show mda
 show mda detail
 show port
 show port description
 show router interface
 show router route-table
 show router route-table summary
 show router ospf interface
 show router ospf neighbor
 show router ldp discovery
 show router ldp session
 show router isis interface
 show router isis adjacency
 show router bgp summary
 show router mpls lsp
 show service service-using
 show service sap-using
 show service sdp-using
 show service sdp
 show lag detail
 monitor lag <lag-id> rate interval 3
 monitor port (monitor all the ports are preferred but uplink ports are required)
 show log log-id 100
 show system cpu
Run below commands only if ESM is configured;

 show service subscriber-using
 show service active-subscribers

Migration
Migration Tasks
Card Migration Use the following procedures to perform migration tasks.

Management
Procedures Step Action
1 Choose „Tools→Card Migration Event Manager‟ from the 5620 SAM main menu.
The Card Migration Event Manager form opens.
2 Click on the Create button. The „Card Migration Event (Create)’ window opens
with the General tab displayed.
3 Configure the parameters:
ID or Auto-Assign ID
Description
Additional Information
Auto Reboot
4 Switch to the NE Migration Candidates tab and click on the Add button.
The „Select Network Elements / Card Migration Event‟ window opens.

Migration Tasks, Continued
Card Migration
Management Step Action
Procedures
5 Select one or more NEs in the list on which card migration operation will be
(continued)
performed and click on the „OK’ button.
6 Select one or more NEs in the list and click on the Properties button. The „Network
Element Migration Candidates’ form opens.
7 Configure the Auto Reboot parameter as needed. Then click on the „OK’ button.
CAUTION: If auto-reboot option remains checked, the system will automatically

reboot as soon as the migration operation initiates.
8 Click on the „Apply’ button and switch to „Card Migration Candidates’ tab.
9 Click on the „Add’ button. The „Select Cards - Card Migration Event’ form opens.

Card Migration
Procedures
10 Select one or more cards in the list and click on the „OK’ button.
(continued)
11 Select one or more cards in the list and click on the Properties button. The
‘Migration Details (Create)’ form opens.

Card Migration
Procedures
12 Configure the New Type parameter in the IOM panel, MDA1 panel, MDA2 panel as
(continued)
required.
13 Click on the „OK’ button

14 Click on the „Apply’ button. The 5620 SAM saves the card migration event
configuration.
15 Replace IOMs or IOM2s with IOM3s. Please follow APPENDIX-A for appropriate
operation.
16 Login to the node.

Card Migration
Procedures
17 Run „show card ‟command and wait until the equipped card-type is the same as
(continued)
newly replaced card-type.
*A:SR12-1# show card
==================================================================
Card Summary
==================================================================
Slot Provisioned Type Admin Operational
Equipped Type (if different) State State
------------------------------------------------------------------
1 iom3-xp up up
8 iom-20g-b up failed
iom3-xp
A sfm4-12 up up/active
B sfm4-12 up down/standby
(not equipped)
==================================================================
18 Click on the General tab on „Card Migration Event’ form to display the Status
indicator.
19 Click on the „Initiate Migration’ button. A dialog box appears.
CAUTION: If auto-reboot option was checked during the configuration,

the system will automatically reboot as soon as the migration operation initiates.
This will result in 100% service impact.

Card Migration
Procedures
20 Click on the „Yes‟ button. The 5620 SAM starts to migrate the specified cards.
(continued)
21 Monitor the card migration as it progresses by viewing the Status indicator on the
form. If Auto Reboot is unchecked, the following status will be seen as below.
22 If Auto Reboot checkbox was not selected during the configuration, reboot the
device. Otherwise skip to next step.
CAUTION: This will result in 100% service impact.

Card Migration
Procedures
23
(continued)
WARNING: Re-enable the SNMP if needed after reboot.
A:SR12-1>config>system>snmp# info
----------------------------------------------
shutdown
packet-size 9216
----------------------------------------------
A:SR12-1>config>system>snmp# no shutdown
24 Check if migration status is completed.

Post-Migration
Post-Migration Tasks
Information Saved logs during the Pre-Migration step indicate the status of the services before migration. In
order to validate the status of the services after migration and verify stability of same services,
before and after Post-Migration tasks should be performed.
Required Execute below command and save output:

Outputs
NOTE: To disable pagination on command output; execute “environment no more”
command.
 show version
 show chassis
 show system memory-pools
 show bof
 show card
 show card detail
 show mda
 show mda detail
 show port
 show port description
 show router interface
 show router route-table
 show router route-table summary
 show router ospf interface
 show router ospf neighbor
 show router ldp discovery
 show router ldp session
 show router isis interface
 show router isis adjacency
 show router bgp summary
 show router mpls lsp
 show service service-using
 show service sap-using
 show service sdp-using
 show service sdp
 show lag detail
 monitor lag <lag-id> rate interval 3
 monitor port (monitor all the ports are preferred but uplink ports are required)
 show system cpu
Run below commands only if ESM is configured;

 show service subscriber-using
 show service active-subscribers

Post-Migration Tasks, Continued
Tech-support Generate a post migration tech-support file:

File
A:SR12-1 # admin tech-support cf3:\post_migration
Processing CPM...
Second Pass
Processing CPM...
Processing CPM in Slot B...
Done...

Back out
Back out Tasks
Introduction In order to back out the system to initial status, back out operation must be performed.
IMPORTANT: These actions must be determined with the customer in mutual

agreement before swap out.
Issue 1
If ... Then ...
the IOM3 fails remove and re-insert the card and check the status of the
card.
the IOM3 fails again after re- replace the card with a new IOM3 and check the status of
insert the card.
the second spare IOM3 fails perform the Issue-2.

again after re-insert
Issue 2 The backup which is taken in „Pre-Migration Tasks‟ section will be applied to the failed node to
back out the system to initial status.
Step Action
1 Choose „Administration→NE Maintenance→Backup/Restore’ from the
5620 SAM main menu. The „Backup/Restore form‟ opens.

Back out Tasks, Continued
Issue 2
(continued)
Step Action
3 From „Backup/Restore Policy’ tab, select the SR Based policy and click on
„Properties’ button.
4 Check „Auto Reboot After Successful Restore‟ button and click on „OK’.
5 Click on the „Backup/Restore Status‟ tab.

6 Select the related node to back out and click on „Restore’ button.
CAUTION: This will result in 100% service impact.

Back out Tasks, Continued
Issue 2
(continued)
Step Action
7 A dialog box appears. Click on the „Yes’ button.
8 Confirm the restore is successful on the „Backup/Restore Status‟ window.

APPENDIX-A: Additional Information
Swapping the IOM Cards
Tasks Follow the steps below for IOM cards swapping.
Step Action
1 Remove existing IOM or IOM2 cards.
2 Remove the IOM3s from the packaging. Do not touch the printed circuit board
and connector pins.
3 If the Impedance panel is covering the chassis slot, remove the panel by
loosening the panel‟s captive screws.
4 Holding the IOM3 by the edges, rotate the ejector levers inward. The ejector
levers must be in this position to release the locking mechanism.
5 Align the IOM3 in the slot guide and slide the IOM inward until the connectors
are seated with the backplane.
6 Rotate the ejector levers outward to lock the IOM3 in place.

If an IOM3 lever does not shift to the locked position, the IOM3 is not properly
seated. Rotate the levers inward and pull the IOM3 out halfway and then try to
reinsert it. Try again to shift the levers outward to the locked position.
7 Secure the IOM3 into place by tightening the captive screws.

- End Of Document –
www.alcatel-lucent.com
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of
Alcatel-Lucent. All other trademarks are the property of their respective owners.
The information presented is subject to change without notice. Alcatel-Lucent
assumes no responsibility for inaccuracies contained herein. Copyright © 2012
Alcatel-Lucent.
All rights reserved.

SR-ES R10. IOM-IOM3 Migration Via 205620SAM Procedure

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SR-ES R10. IOM-IOM3 Migration Via 205620SAM Procedure

Uploaded by

Copyright:

Available Formats

7750 SR & 7450 ESS R10.

3FQ 24026 70XF PGZZA

CAUTION: This Procedure is 100% Service Impacting.

Continued on next page

Copyright © Alcatel-Lucent GPEC TEAM Page 4 of 25

Continued on next page

Copyright © Alcatel-Lucent GPEC TEAM Page 5 of 25

Feedback For any feedback on this document, please contact to @DL_TR_PUB_GPEC_TR_IPD

CAUTION: The installation takes around 20-30 minutes depending on the

Operation Expected Time

Copyright © Alcatel-Lucent GPEC TEAM Page 6 of 25

Copyright © Alcatel-Lucent GPEC TEAM Page 7 of 25

CAUTION: Use an ESD-preventive wrist or ankle strap and always connect an

Required Before swapping out, the following items will be required.

Copyright © Alcatel-Lucent GPEC TEAM Page 8 of 25

Chassis Mode Corresponds to … Backwards compatible for …

Tech-support Generate an admin tech-support file:

Continued on next page

Copyright © Alcatel-Lucent GPEC TEAM Page 9 of 25

Pre-Migration Tasks, Continued

Saving Log File Connect to NE by Terminal Emulation Software.

Continued on next page

Copyright © Alcatel-Lucent GPEC TEAM Page 10 of 25

Pre-Migration Tasks, Continued

Required Execute below commands and save the outputs:

Run below commands only if ESM is configured;

Copyright © Alcatel-Lucent GPEC TEAM Page 11 of 25

Card Migration Use the following procedures to perform migration tasks.

Continued on next page

Copyright © Alcatel-Lucent GPEC TEAM Page 12 of 25

Migration Tasks, Continued

CAUTION: If auto-reboot option remains checked, the system will automatically

Continued on next page

Copyright © Alcatel-Lucent GPEC TEAM Page 13 of 25

Migration Tasks, Continued

Continued on next page

Copyright © Alcatel-Lucent GPEC TEAM Page 14 of 25

Migration Tasks, Continued

13 Click on the „OK’ button

Continued on next page

Copyright © Alcatel-Lucent GPEC TEAM Page 15 of 25

Migration Tasks, Continued

*A:SR12-1# show card

19 Click on the „Initiate Migration’ button. A dialog box appears.

CAUTION: If auto-reboot option was checked during the configuration,

Continued on next page

Copyright © Alcatel-Lucent GPEC TEAM Page 16 of 25

Migration Tasks, Continued

CAUTION: This will result in 100% service impact.

Continued on next page

Copyright © Alcatel-Lucent GPEC TEAM Page 17 of 25

Migration Tasks, Continued

24 Check if migration status is completed.

Copyright © Alcatel-Lucent GPEC TEAM Page 18 of 25

Required Execute below command and save output:

Run below commands only if ESM is configured;

Continued on next page

Copyright © Alcatel-Lucent GPEC TEAM Page 19 of 25

Post-Migration Tasks, Continued

Tech-support Generate a post migration tech-support file:

Copyright © Alcatel-Lucent GPEC TEAM Page 20 of 25

Back out Tasks

IMPORTANT: These actions must be determined with the customer in mutual