11.

3 How to Replace an FLC Board (FLCSERVICE, FLCCONGI)

All rights reserved. Passing on and copying of this
document, use and communication of its contents

This procedure describes the replacement procedure of a defective FLC board or the extention of a single
not permitted without written authorization.

to a redundant FLC system.

11.3.1 Preconditions

– The FLC Replacement procedure should be executed within a time frame where high CPU
availability is not required on the active FLC, preferrably in a maintenance window. However, the
1678 will remain maintainable over the the entire FLC Replacement time.

– The FLC which is serving the FLC Replacement (server FLC) must be and must remain in active
state during FLC Replacement.

– If the 1678MCC NE is configured as L1 gateway for multiple OSI–Areas as described in chapter

“Example 2: 1678MCC as L1 Gateway NE for multiple areas” of the “CT Operator’s Handbook”,
you will have to connect the external LAN of the new FLC to a port of your DCN equipment terminating
the VLAN of the 1678MCC NE default communication protocol stack. The VLAN id of the default
VLAN can be found in the Local Ethernet Configuration Dialog using NM/CT:

Equipment View –> Comm/Routing Dialogs –> Ethernet...

Select “1” to view the settings of the default communication protocol stack.

11.3.2 Replace the defective FLC board

(1) Shut down the defective FLC board using the EP dialog via CT if the FLC board is
still operable

~ Edit –> Set out of service –> Standby FLC

~ Edit –> Shutdown –> ’Out of Service’ FLC

If the FLC is blocking (even not operable via debugger session), you have to continue with step
(2)).
1AA 00014 0004 (9007) A4

ED 03

3AG 24323 BEAA PCZZA 37/163

 (2) Plug out the defective FLC board

~ After ~1 min. plug out the defective FLC.

All rights reserved. Passing on and copying of this
document, use and communication of its contents

Only one EP dialog is working at the same time. Do not try to open a new EP dialog if
not permitted without written authorization.

another one is already open!

The new FLC (client FLC) is not yet plugged in.

(3) Check the DHCP service

~ Check that no DHCP service is active in the external LAN where the 1678MCC is connected
to.

(4) Connect the necessary Cables

~ Provide the normal cabling needed for the 1678MCC: LAN cabling to the customers LAN,
Cabling to an 1670 OED, if required.

~ If the 1678MCC is not connected to an external LAN, connect the LAN ports of the two FLCs
directly with a LAN cable.

~ Connect the debug port of the new FLC (client) to a PC or laptop with a debug cable, as
described in Installation and Start–Up Handbook FLC Software.

~ Start a terminal program on COM1/9600bd to connect to the EM of the client. For diagnostic
purposes it is useful to enable logging of the terminal output into a log file.

(5) Plug in the Client FLC

~ Plug in the new FLC board. Instantly interrupt the EM boot sequence by pressing <ESC> on
the serial terminal.

~ Force MENMON to boot from network by typing:

ee–def
rst

Refer to Installation and Start–Up Handbook FLC Software, chapter ”FLC installation”.

~ Check that the NBOOT is executed. The console output must end with the next line,
continuously adding dots:

Searching for server (BOOTP) ...........

1AA 00014 0004 (9007) A4

ED 03

3AG 24323 BEAA PCZZA 38/163

 ~ Note the MAC address shown in the boot sequence. The line indicating the MAC address looks
like (example):

Probing...[EEPRO100] 00:c0:3a:2d:00:dd at membase...

All rights reserved. Passing on and copying of this
document, use and communication of its contents

The MAC address in this example is 00:c0:3a:2d:00:dd.

not permitted without written authorization.

11.3.3 Installation and Configuration of the new FLC Board

(6) Download of the FLC Software

~ Log in on the active server FLC as user install.

ssh maint@<IP–address active FLC EM board>

~ On the active server FLC, enter the FLCReplacement command to start the download of the
client FLC:

cd ~install
./bin/FLCReplacement –v <client MAC addr>

The client will now start to download from the active server FLC. The rest of the FLC
Replacement procedure will run automatically. Depending on the disk occupancy of the active
server FLC and the network speed the time needed will vary. In case of a standard installation
with no extra data stored on the disk and a 100 MBit/s LAN the time needed is about 1 hour.

Caution: If additional data is stored on the disk partitions, the time needed for file
system transfer will increase correspondigly. As a rough estimate a transfer speed of 2
MByte/s can be asssumed.

The FLC Replacement will be executed in four phases:

• Clone phase: A ramdisk system is downloaded from the server. This system prepares the
harddisk of the new FLC and downloads the harddisk contents from the server to the client.
Afterwards the cloned system will be prepared for the first boot of the runtime system from
disk.

• Postinstallation: The new runtime system boots the first time from disk. CSServer data
is synchronized with the server FLC and the network configuration is updated.

• Save current installation: The now valid system installation and configuration is saved for
recovery.

• Final startup of the runtime system. The new FLC will start up into maintenance state.
1AA 00014 0004 (9007) A4

ED 03

3AG 24323 BEAA PCZZA 39/163

 (7) DCN Configuration

~ If the 1678MCC NE is configured as L1 gateway for multiple OSI–Areas (see chapter 11.3.1
Preconditions, step 3) you will have to connect the external LAN cable of the new FLC to the
All rights reserved. Passing on and copying of this
document, use and communication of its contents

original FLC’s port of your DCN equipment or roll back the changes to your DCN equipment
not permitted without written authorization.

configuration you made to meet the Preconditions (see chapter 11.3.1 Preconditions).

(8) Activate the new FLC

~ After the FLC has rebooted from save current installation, FLC Replacement is finished. This
can be checked by the FLCs console output.

~ Log in on the new FLC. The messages shown at log in should be as shown below. Be sure that
the login message is not indicating that clone, postinstall or save current installation is still
running. See chapter Troubleshooting below if in doubt.

~ Login at the finished FLC Replacement client:

ssh install@<IP–address of new installed FLC EM board>

~ Check the file /var/flcreplacement/FLCReplacement.state for successful completion of FLC

Relpacement. It should contain the state FLCReplacementFinished .

cat /var/flcreplacement/FLCReplacement.state

The log–file must end with following line:

FLCReplacementFinished

~ Check the file /var/flcreplacement/FLCReplacement.trace. The status report at the end of

the file should show no errors, see below. Warnings are considered harmless.

Status report in FLCReplacement.trace after successful FLC Replacement:

––––––––––––––––––––––––––––––––––––––––––––––––––
FLC Replacement status report
TIMESTAMP (Wed May 31 15:36:19 UTC 2006)

0 errors
0 warnings
For details see /var/flcreplacement

FLC Replacement was SUCCESSFUL

––––––––––––––––––––––––––––––––––––––––––––––––––
Current FLC Replacement state is ’FLCReplacementFinished’
––––––––––––––––––––––––––––––––––––––––––––––––––

~ Before you start the application, confirm that the server FLC is still in active state. This is
necessary for correct synchronization of the persistency data.
1AA 00014 0004 (9007) A4

ED 03

3AG 24323 BEAA PCZZA 40/163

 ~ Start the SSU and Application of the new installed FLC EM board.

pbin
SSUDiag –c startAppl
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization.

The new installed FLC board must be in state passive.

~ Check if the persistency of both FLCs are synchronized.

PersSync

All patches installed before replacing the FLC must be added manually after the FLC
replacement.

The replacement procedure is now completed!

1AA 00014 0004 (9007) A4

ED 03

3AG 24323 BEAA PCZZA 41/163