Replacing Compact Flash on a 7x50 v09

Technical Expertise Center

Replacing a Compact flash on a 7x50

Version 0.9, Jan 24, 2011

7x50 Technical Expertise Center


Purpose and Scope The purpose of this document is to describe the procedure of replacing compact flash card on a 7x50 in case such action is required due to a fault compact flash disk or an upgrade to a higher capacity compact flash disk. This includes the procedure for the replacement of cf1, cf2 and cf3 slots. The assumption in this document is that all logs are destined to either cf1 or cf2 as recommended by Alcatel-Lucent. Also, if running DHCP persistency, ensure that the correct size of compact flash is being used by consulting with the Release Notes.

Preparation Equipment FTP server reachable by the 7x50 with software image files PC with a card reader (to format the new compact flash device if necessary) 7x50 console cable Keep in mind It is advised to format the new compact flash cards in a PC card reader before going to site to switch the compact flash cards. Perform this procedure in a maintenance window. Important Note Always make sure the compact flash slot is shutdown before removing the flash card from the 7x50 CPM card. Steps – Replacing CF3 (if CF1 and CF2 slots are full, proceed to step 16)

1. Format new CF cards either on a PC with a card reader or on the 7x50 based on the guidelines below:

NOTE: Skip this step if already done OR if the CF cards are shipped directly from ALU Manufacturing which are all pre-formatted to FAT32 file system; they are ready to use on a 7x50 system

7.0R2 & Above

7.0R1 6.1R7 & Above

6.1R6 & below

6.0R12 & Above

6.0R11 & below

5.0R23 & Above

5.0R22 & below

Part No. Part Description

3HE00265AA CF - 256M COMPACT FLASH

PC or TiMOS

PC or TiMOS

PC or TiMOS

PC or TiMOS

PC or TiMOS

PC or TiMOS

PC or TiMOS

PC or TiMOS

3HE01619AA CF - 2 GB COMPACT FLASH

PC or TiMOS

PC only * PC or TiMOS



PC only *


PC or TiMOS




PC only *


PC or TiMOS




PC only *

* Check the release notes. DTS 74239 may occur if formatting a compact flash on the 7x50 with these releases. For this reason, a compact flash must be formatted using a PC when running these releases.


You can check the format type of a compact flash by running the ‘dir’ command: *B:node130>file cf3:\ # dir

Volume in drive cf3 on slot A has no label.

Volume in drive cf3 on slot A is formatted as FAT32.

…

CF3 is always FAT32 format. CF1 or CF2 can be either FAT32 or Reliable format.

2. Place the formatted compact flash in an empty cf1 or cf2 slot if not already done. Before

proceeding to the next step, make sure the slot is in operational ‘up’ state. Run ‘show card detail’ to check.

3. Backup DHCP persistency files If there is DHCP persistency configured on the system, point the location to the new compact flash card location. The system will write DHCP persistency files to this location when it sees that there is no DHCP persistency file present. After the file is created, remove the location.

First check the dhcp persistency and note the number of clients: B:node130# tools dump persistence summary

Keep note of the number of clients to compare after the compact flash has been replaced in step 12. Then remove the current location: B:node130# configure system persistence subscriber-mgmt no location

Then add the new location (make sure this matches the slot that the new CF is in): B:node130# configure system persistence subscriber-mgmt location cf1:

B:node130# config>system>persistence# info ---------------------------------------------- subscriber-mgmt description "SubMgmt-Test" location cf1: exit

Check the dhcp persistency and note the number of clients, should be close to previous before changing location (may take a few minutes): B:node130# tools dump persistence summary

Remove the location(Location will be added again after the compact flash is placed in the cf3 location): *B:node130>config>system>persistence>sub-mgmt# no location

4. Save bof to new compact flash ex: *B:node130# bof save cf1:


Writing BOF to cf1:/bof.cfg Saving BOF .... Completed.

5. Save SNMP persistency info and current configuration to the new compact flash To check if snmp persistency is on, see below: show bof: *B:node130# show bof ============================================================================ BOF (Memory) ============================================================================ ... duplex full speed 100 wait 3 persist on

no li-local-save no li-separate console-speed 115200 ============================================================================

Save both config and index file, can do this even if persistency is off B:node130# admin save cf1:/config.cfg detail index Writing file to cf1:\config.cfg Saving configuration .... Completed.

6. Copy images from FTP server to the new compact flash Files needed are: boot.ldr and .tim files Make sure that the boot.ldr is in the root directory. Also make sure that the image file location are in the correct path that is configured in the bof file.

7. Verify all files in the compact flash cards First run ‘show bof’ to see where the config files and image files are expected to be found Checklist – VERY Important or else system will not boot up next time!!!

File Location

boot.ldr Root directory

bof.cfg Root directory

configuration file Path specified in bof

SNMP persistency file (.ndx file) Root directory

Image files – cpm.tim, iom.tim, both.tim Path specified in bof

Ex: *B:node130# show bof ============================================================================BOF (Memory) ============================================================================ primary-image cf3:\7.0R4 primary-config cf3:\config.cfg address 138.120.189.130/24 active primary-dns 138.120.252.56 dns-domain ca.alcatel.com static-route 138.120.0.0/16 next-hop 138.120.189.1 static-route 172.0.0.0/8 next-hop 138.120.189.1 autonegotiate


duplex full speed 100 wait 3 persist on no li-local-save no li-separate console-speed 115200 ============================================================================

B:node130>file cf1:\ # dir

Volume in drive cf1 on slot B has no label. Volume in drive cf1 on slot B is formatted as FAT32. Directory of cf1:\ 12/03/2009 07:48p 286506 config.cfg 12/03/2009 07:43p 732 bof.cfg 12/03/2009 07:48p 2614 config.ndx 12/03/2009 07:57p <DIR> 7.0.R4 12/03/2009 07:56p 1405072 boot.ldr 4 File(s) 1694924 bytes. 1 Dir(s) 2040135680 bytes free. B:node130>file cf1:\ # cd 7.0.R4 B:node130>file cf1:\7.0.R4\ # dir

Volume in drive cf1 on slot B has no label. Volume in drive cf1 on slot B is formatted as FAT32. Directory of cf1:\7.0.R4\ 12/03/2009 07:57p <DIR> . 12/03/2009 07:56p <DIR> .. 12/03/2009 07:56p 23355505 cpm.tim 12/03/2009 07:57p 31404911 iom.tim 12/03/2009 07:57p 1405072 boot.ldr 3 File(s) 56165488 bytes. 2 Dir(s) 2040135680 bytes free.

8. If the active and standby cf3 both need to be replaced copy all the files to another compact

flash. Plug in another new compact flash which had been formatted in step 1 into the remaining empty cf1: or cf2: slot. Make sure the slot is no shut and up first before proceeding. Ex: B:node130>file cf1:\ # copy * cf2: Copying file cf1:\config.cfg....done Copying file cf1:\bof.cfg....done Copying file cf1:\config.ndx....done Skipping directory cf1:\7.0R4 Copying file cf1:\boot.ldr.....done Copying file cf1:\bof.cfg.1....done 5 file(s) copied. B:node130>file cf1:\ # cd cf2: B:node130>file cf2:\ # md 7.0R4 <-make directory 7.0R4 B:node130>file cf2:\ # cd cf1:


B:node130>file cf1:\ # cd 7.0R4 B:node130>file cf1:\7.0R4\ # copy * B:node130>file cf1:\7.0R4\ # copy * cf2:/7.0R4

Copying file cf1:\7.0R4\cpm.tim....done Copying file cf1:\7.0R4\iom.tim.....done Copying file cf1:\7.0R4\boot.ldr......done 3 file(s) copied.

9. Verify all files are compact flash cards B:node130>file cf2:\ # dir

Volume in drive cf2 on slot B has no label. Volume in drive cf2 on slot B is formatted as FAT32. Directory of cf2:\ 12/03/2009 08:04p 286506 config.cfg 12/03/2009 08:04p 726 bof.cfg 12/03/2009 08:04p 2614 config.ndx 12/03/2009 08:04p 1405072 boot.ldr 12/03/2009 08:04p 732 bof.cfg.1 12/03/2009 08:06p <DIR> 7.0R4 5 File(s) 1695650 bytes. 1 Dir(s) 202391552 bytes free. B:node130>file cf2:\ # cd 7.0R4 B:node130>file cf2:\7.0R4\ # dir

Volume in drive cf2 on slot B has no label. Volume in drive cf2 on slot B is formatted as FAT32. Directory of cf2:\7.0R4\ 12/03/2009 08:06p <DIR> . 12/03/2009 08:04p <DIR> .. 12/03/2009 08:05p 23355505 cpm.tim 12/03/2009 08:06p 31404911 iom.tim 12/03/2009 08:06p 1405072 boot.ldr 3 File(s) 56165488 bytes. 2 Dir(s) 202391552 bytes free.

10. Replace standby cf3 card with newly configured cf3 card (skip this step if running a single

CPM environment)

Distinguish active and standby CPMs by issuing the ‘show card’ command: B:node130# show card

============================================================================ Card Summary ============================================================================ Slot Provisioned Equipped Admin Operational Card-type Card-type State State ----------------------------------------------------------------------------


… A sfm-200g sfm-200g up up/active B sfm-200g sfm-200g up up/standby ============================================================================

Shut down standby cf3 slot B:node130>file cf3:\ # shutdown cf3-A:

Replace the old cf3 with the new cf3 No shut the standby cf3 slot B:node130>file cf3:\ # no shutdown cf3-A:

‘show card detail’ to make sure the new compact flash cards are up

11. Replace active cf3 card with newly configured cf3 card

shutdown primacry cf3 slot B:node130>file cf3:\ # shutdown cf3:

replace the old cf3 with the new cf3: no shut primary cf3: B:node130>file cf3:\ # no shutdown cf3:

‘show card detail’ to make sure the new compact flash cards are up

12. Add location for DHCP persistency if DHCP persistency was previously used

*B:node130>config>system>persistence# info ---------------------------------------------- subscriber-mgmt description "Test" location cf3: exit

Use tools command to verify that the DHCP persistency status: B:node130# tools dump persistence summary

The number of clients displayed should be close to the number as previously checked in step 3.

13. Save the configuration, if there are redundant CPMs, make sure they are synched

*B:node130# admin save Writing file to cf3:\config.cfg Saving configuration .... Completed. Syncing .... Completed.

14. Check both the active and backup CPMs cf3 filesystem to verify that the correct files are there

Look at the bof to check if the files are in the correct location.

Checklist – VERY Important or else system will not boot up next time!!!

File Location


boot.ldr Root directory

bof.cfg Root directory

configuration file Path specified in bof

SNMP persistency file (.ndx file) Root directory

Image files – cpm.tim, iom.tim, both.tim Path specified in bof

Ex: *B:node130# show bof

============================================================================ BOF (Memory) ============================================================================ primary-image cf3:\7.0R4 primary-config cf3:\config.cfg address 138.120.189.130/24 active primary-dns 138.120.252.56 dns-domain ca.alcatel.com static-route 138.120.0.0/16 next-hop 138.120.189.1 static-route 172.0.0.0/8 next-hop 138.120.189.1 autonegotiate duplex full speed 100 wait 3 persist on no li-local-save no li-separate console-speed 115200

*B:node130# file dir cf3:

Volume in drive cf3 on slot B has no label.

Volume in drive cf3 on slot B is formatted as FAT32. Directory of cf3:\ 12/03/2009 10:21p 9233 config.cfg <-config file used 12/03/2009 08:01p 726 bof.cfg <-bof file 12/03/2009 10:21p 2606 config.ndx <-SAM persistency file 12/03/2009 08:02p <DIR> 7.0R4 <-.tim files in directory 12/03/2009 07:56p 1405072 boot.ldr <-bootloader 12/03/2009 07:43p 732 bof.cfg.1 12/03/2009 10:21p 9036 config.cfg.1 12/03/2009 10:21p 2606 config.ndx.1 12/03/2009 07:48p 2614 config.ndx.2 12/03/2009 07:48p 286506 config.cfg.2 10 File(s) 538590555 bytes. 1 Dir(s) 1503068160 bytes free. *B:node130# file dir cf3-a: Volume in drive cf3 on slot A has no label. Volume in drive cf3 on slot A is formatted as FAT32. Directory of cf3:\ 12/03/2009 10:21p 9233 config.cfg <-config file used 12/03/2009 10:21p 726 bof.cfg <-bof file 12/03/2009 10:21p 2606 config.ndx <-SAM persistency file 12/03/2009 10:21p 1405072 boot.ldr <-bootloader 12/03/2009 08:04p 732 bof.cfg.1


12/03/2009 08:06p <DIR> 7.0R4 <-.tim files in directory 12/03/2009 08:33p 3113 bootlog.txt 12/03/2009 08:14p 3164 bootlog_prev.txt 12/03/2009 10:21p 726 bof.cfg.bak 12/03/2009 10:21p 1405072 boot.ldr.bak 10 File(s) 2830444 bytes. 1 Dir(s) 201244672 bytes free.

15. If there are redundant CPMs, synchronize CPMs both boot-env and config

*B:node130# admin redundancy synchronize boot-env Syncing boot environment: BOF.CFG : cf3:bof.cfg boot loader : cf3:boot.ldr primary config : cf3:/config.cfg primary config : cf3:/config.ndx primary image : cf3:/7.0.R4/cpm.tim primary image : cf3:/7.0.R4/iom.tim secondary image : cf3:/secondary/cpm.tim *B:node130# admin redundancy synchronize config Syncing configuration: BOF.CFG : cf3:/bof.cfg primary config : cf3:/config.cfg primary config : cf3:/config.ndx SSH key file : cf3:/ssh/sshV2SvrPubDSAkeyFile SSH key file : cf3:/ssh/sshV2SvrPrivDSAkeyFile SSH key file : cf3:/ssh/sshV2SvrPubRSAkeyFile SSH key file : cf3:/ssh/sshV2SvrPrivRSAkeyFile

Note: If SSH preserve-key feature is enabled and the compact flash in cf3 of the active CPM

does not contain the SSH directory and files, ‘synchronize config’ will not be successful. If SSH preserve-key feature is enabled, either copy the contents of the ‘ssh’ directory from the old compact flash or disable and re-enable SSH preserve-key: *B:node130# configure system security ssh *B:node130>config>system>security>ssh# no preserve-key *B:node130>config>system>security>ssh# preserve-key

Then, check that ssh directory and files are present on cf3. Finally, perform ‘admin redundancy synchronize config’.

Replace CF1 and CF2 Procedure 16. Make sure the new compact flash cards are properly formatted before proceeding.

See step 1 for details about formatting a compact flash. Check the current CF1 or CF2 compact flash format type by issuing ‘dir’. CF1 or CF2 can be either FAT32 or Reliable. Verify that the replacement compact flash format is the same unless you want to change it. *B:node130# file dir cf1:


Volume in drive cf3 on slot A has no label. Volume in drive cf3 on slot A is formatted as FAT32. …

17. shut down all logging in the system ex: *B:node130# configure log *B:node130>config>log# info

Check for logs that point to a file. If the log points to a file, shut down the log. *B:node130# configure log log-id 5 *B:node130>config>log>log-id# info ---------------------------------------------- from security to file 3 ---------------------------------------------- *B:node130>config>log>log-id# shutdown *B:node130>config>log>log-id# info ---------------------------------------------- shutdown from security to file 3 ----------------------------------------------

18. Copy log files that are in cf1 and cf2 onto an ftp server

ex:

B:node130>file cf1:\ #cd act B:node130>file cf1:\ #copy * ftp://admin:[email protected]/act B:node130>file cf1:\ #cd act-collect B:node130>file cf1:\ #copy * ftp://admin:[email protected]/act-collect

19. Shut down the compact flash cf1 and cf2

Ex:

*B:node130# file shutdown cf1: *B:node130# file shutdown cf2-B:

Verify that the compact flash slot is shut down

Card B =============================================================================== Slot Provisioned Equipped Admin Operational Card-type Card-type State State ------------------------------------------------------------------------------- B sfm2-400g sfm2-400g up up/active ... Flash - cf1: Administrative State : down Operational state : shutdown Serial number : Firmware revision : Model number : Size : 0 Bytes Free space : 0 Bytes


Flash - cf2: Administrative State : down Operational state : not equipped Flash - cf3: Administrative State : up Operational state : up Serial number : 038CTX7DSw703SC02590 Firmware revision : V2.23 Model number : SILICONSYSTEMS INC 256MB Size : 253,932 KB Free space : 52,420 KB ...

20. Remove cf1 or cf2

21. Replace cf1 or cf2 slot with new compact flash cards

22. No shut down the compact flash cf1 and cf2

Ex:

*B:node130# file no shutdown cf1: *B:node130# file no shutdown cf2-B:

23. Verify that the card is operationally up by running ‘show card detail’

24. Re-enable logging

Ex: *B:node130# configure log log-id 5 *B:node130>config>log>log-id# no shutdown *B:node130>config>log>log-id# info ---------------------------------------------- from security to file 3 ----------------------------------------------

Documents

Replacing Compact Flash on a 7x50 v09