User's Manual

Configuration

5 Configuration

The equipment activation process has a distributed set of procedures that allow the connection of an

inactive equipment to a PON network. This configuration is done following the procedure described in

the OMCI protocol.

5.1 Costumization

For customization process, the requirements specified in the G.984.4, G.984.5 and ‘Implementer’s

Guide’ in the G.984.4 v1 are taken into account.

5.2 Software download from the OLT

The software download is made following the OMCI-based procedure included in the ‘Implementer’s

Guide’ of the G.984.4 Recommendation.

The Managed Entity (ME) in charge of managing the software download is named Software Image. Per

each ME containing independently-manageable software, the FiberGateway creates two software

images. Each image will have three attributes:

• Valid - if it has been verified that it’s content is an image with executable code;

• Committed - if once the FiberGateway is rebooted, it is loaded and executed;

• Active - if it is loaded and it is being executed in the FiberGateway.

There can be only one active image and only one committed image at a given moment. The

FiberGateway goes through a series of states in order to download and activate a software image. Each

state is defined according to the states of the variables of both images. The OLT controls the

FiberGateway state through a series of commands:

• Start download

o It starts the software download sequence. This action is only valid for inactive

and non-committed software images;

• Download section

o It downloads a section of a software image. This action is only valid for an image

that is being downloaded;

• End download

o It indicates the end of a download sequence, providing the CRC and

information about version for the final verification of the downloaded software

image. This action is only valid for a software image that is being downloaded;

• Activate image

o It loads/executes a valid software image. When this action is applied to an

inactive software image, the execution of the current code image is suspended,

the associated software image is loaded from the non-volatile memory and the

execution of the new code image is started. When this action is applied over a

software image that is active, a reboot is executed;

• Commit image

o It selects a valid SW image to be loaded and executed by default when the

FiberGateway is restarted;

• Composition of the Software Image