06.08.2013 Views

Test Plan for Optical Grooming Switches - Light Reading

Test Plan for Optical Grooming Switches - Light Reading

Test Plan for Optical Grooming Switches - Light Reading

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Test</strong> <strong>Plan</strong> <strong>for</strong> <strong>Optical</strong> <strong>Grooming</strong> <strong>Switches</strong><br />

TCB018: In-service Software upgrades.<br />

Purpose:<br />

To confirm that upon an in service software upgrade to the node, no traffic affect conditions<br />

will occur.<br />

<strong>Test</strong> method:<br />

1. Configure and monitor an STS-1 trail from Paris to LA<br />

2. Per<strong>for</strong>m supplier process <strong>for</strong> In-service Software upgrades <strong>for</strong> individual interface card<br />

PAR#1<br />

3. Attempt to access resource during operation and note alarms and warnings.<br />

4. Per<strong>for</strong>m supplier process <strong>for</strong> In-service Software upgrades <strong>for</strong> Control software on node.<br />

5. Attempt to access resource during operation and note alarms and warnings.<br />

Expected result:<br />

• No loss of traffic or error.<br />

• No major alarms.<br />

• Management system prevents the use of resources which may cause erroneous<br />

conditions during software upgrade.<br />

• Management system clearly and accurately shows the status of:<br />

Cards being upgrade.<br />

Status of trails through network.<br />

A warning to show if resources are unavailable.<br />

Any other comments:<br />

None<br />

TCB019: In-service Software reversion.<br />

Purpose:<br />

To confirm that the switch management system is able to revert back to a previous software<br />

version without generating traffic affecting conditions.<br />

<strong>Test</strong> method:<br />

1. Per<strong>for</strong>m supplier process <strong>for</strong> In-service Software reversion <strong>for</strong> individual interface card.<br />

2. Attempt to access resource during operation and note alarms and warnings.<br />

3. Per<strong>for</strong>m supplier process <strong>for</strong> In-service Software reversion <strong>for</strong> Control software on node.<br />

4. Attempt to access resource during operation and note alarms and warnings.<br />

Expected result:<br />

• No loss of traffic or error.<br />

• No major alarms.<br />

• Management system prevents the uses of resources that may cause erroneous<br />

conditions during software revision.<br />

• Management system clearly and accurately shows the status of:<br />

Cards being upgrade.<br />

Status of trails through network.<br />

A warning to show if resources are unavailable.<br />

Any other comments:<br />

None<br />

END OF BLOCK 17<br />

55

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!