ID

(lasciare Test ID Description

vuoto)

The following states for Zone 1 and 2 respectively.

Zone Status is Primary and Standby
TelORB Mode is NetShared for both Zones
7.1 - Zone 2 Smooth Takeover TelORB State is In Use and Ready

The following states for Zone 2 and 1 respectively:

Zone Status is Primary and Standby

7.2 - Giveback executed by Zone 2 TelORB Mode is Takeover and Down
TelORB State is In Use and Ready

The following states for Zone 1 and 2 respectively:

Zone Status is Primary and Standby
TelORB Mode is NetShared for both Zones
7.3 - Zone 2 Hard Takeover TelORB State is In Use and Ready

The following states for Zone 2 and 1 respectively:

TelORB mode is Takeover and Standby
TelORB state is In Use and OutofSync
7.4 - Reconciliation triggered by Zone 1 Zone Status is Primary and Down

The following states for Zone 2 and 1 respectively:

TelORB mode is NetShared for both Zones
TelORB state is In Use and Ready
7.5 - Giveback executed by Zone 2 after RecoZone Status is Primary and Standby

The following states for Zone 1 and 2 respectively:

TelORB mode is NetShared for both Zones
TelORB state is In Use and Ready
Zone Status is Primary and Standby

7.6 - Scheduled Backup and Remote Sync

Link Failure

7.7 - Gx Link Failure on Primary Zone
Node Reboots/Failure
7.9- Standby Zone Reboots
SNMP Trap and Alarms
7.11 - Takeover from Peer Zone
7.12 - Reconciliation Needed
7.13 - Route to peer zone not available
7.14- Connection Lost to peer zone
7.15 - NetRed link deactivated manually
7.16- zone reloaded from backup
The following states for Zone 1 and 2 respectively:
TelORB mode is NetShared for both Zones
TelORB state is In Use and Ready
Zone Status is Primary and Standby
The following states for Zone 1 and 2 respectively:
TelORB mode is NetShared for both Zones
TelORB state is In Use and Ready
Zone Status is Primary and Standby
Two SAPC are configured in a GeoRedundancy
scenario with Zone 1 acting as primary and Zone 2
acting as standby
Two SAPC are configured in a GeoRedundancy
scenario with Zone 1 acting as primary and Zone 2
acting as standby
Two SAPC are configured in a GeoRedundancy
scenario with Zone 1 acting as primary and Zone 2
acting as standby.
Two SAPC are configured in a GeoRedundancy
scenario with Zone 1 acting as primary and Zone 2
acting as standby. The Update Channels are
working in the proper way
Two SAPC are configured in a GeoRedundancy
scenario with Zone 1 acting as primary and Zone 2
acting as standby. The Update Channels are
working in the proper way
Two SAPC are configured in a GeoRedundancy
scenario with Zone 1 acting as primary and Zone 2
acting as standby
Test List name Purpose Expected Results

To observe the behavior of a

smooth takeover by Zone 2
try changing a group, this
and the impact on Gx traffic
will trigger a RAR, then a
GEORED during the transition.
CCR update should be
present, we need to check
if zone2 can handle this
procedure correctlly
To observe the behavior of a
smooth giveback by Zone 2
and the impact on Gx traffic
GEORED during the transition.

To observe the behavior of a

hard takeover by Zone 2
and the impact on Gx traffic
GEORED during the transition

To observe the behavior of

reconciliation by Zone
1 and the impact on Gx traffic
GEORED during the transition

To observe the behavior of a

Giveback by Zone 2
and the impact on both Gx and
GEORED provisioning traffic during the
transition

To observe the following:

Behavior of the zones when
remote synchronization is
performed automatically in
Primary Zone during scheduled
GEORED backup.
Behavior of the zones when
remote synchronization is
performed manually in Primary
Zone.

GEORED
 To observe the following:
Behavior of the zones when one
of the Gx interface towards
primary zone fails.
Behavior of the zones when both
GEORED of the Gx interface towards
primary zone fails.
Impact on Gx traffic during this
failure

GEORED
To observe the following:
Procedures to resume the zone
to normal states after zone
GEORED reload.

GEORED
Verify that in case of smooth
GEORED Takeover and hard Takeover the
Alarm is generated
Verify that in case of hard
GEORED Takeover the Alarm is generated
in standby Zone
Verify that if the OAM
communication between Zone 1
GEORED and Zone 2 is deactivated, the
alarm notification is correctly
triggered
Verify that if both Update
Channel between Zone 1 and
GEORED Zone 2 are deactivated, the
alarm notification is correctly
triggered
Verify that if the Update Channel
between Zone 1 and Zone 2 is
GEORED deactivated manually, the alarm
notification is correctly triggered

Verify that the alarm is raised

GEORED when a Zone Reload is executed
 Test
Note
Result

Verify Session Replication information on both

zones using ldap search command at
subscriber and session level.
Reply this test with active call and HO after
Takeover. Check pass

Verify Session Replication information on both

zones using ldap search command at
subscriber and session level pass

Verify Session Replication information on both

zones using ldap search command at
subscriber and session level
Reply this test with active call and HO after
Takeover. pass

Verify Session Replication information on both

zones using ldap search command at
subscriber and session level
pass

Verify Session Replication information on both

zones using ldap search command at
subscriber and session level pass

Verify Session Replication information on both

zones using ldap search command at
subscriber and session level pass
Verify Session Replication information on both
zones using ldap search command at
subscriber and session level pass

Verify Session Replication information on both

zones using ldap search command at
subscriber and session level pass
 ID
(lasciare vuoto) Test ID Description

8.1 Root Password change

Connection to SAPC node to the

primary IO address with pssword
authentication with mast user.
User change from mast to root
with public certificate
authentication. root password
change.

8.2 User(s)Password change performed by Super user

Connection to SAPC via super

user on O&M VIP port 31310.
Password change procedure for
jambala user and other users
(admin/mss)

8.3 Password access with Mast and Super user

Connection to SAPC via mast on

IO and super on O&M VIP with
password authentication

8.4 IO trusted access with Jambala user

Connection to SAPC via jambala

on IO with public key
authentication

8.5 Admins user leves differences (admin1/admin2) in

CMBrowser & GUI access
Access differences in logging via
admin1/admin2 users
 Configure the FTU transfer job for
SAPC,TSP and Diamter file
8.9- Independent FTU transfer between Redundant Zones counters. Verify that each zone
create and transfer its relative
counters.
Verify the access to BSP CLI
8.10 - Access to BSP CLI

verification of alarms

8.13- BSP alarm verification

Check that dbn_stat script can be

8.14 - dbn_stat verification invoked from an external machine
usinf a specific user
8.15 SAPC counters verification: KPI, traffic counters
Check the measurement files,
generated inside the following
path:
/opt/telorb/axe/tsp/NM/PMF/report
erLogs/
 Test List name Purpose Preparation

Check that SAPC node supports root mast user configuration preparation of key
password change when coming from mast couple pubblic-private for mast user on
user and check that the pubblic certificate primary IO.
authentication has been supported.

28 Security Management Test List

Check that SAPC supports password change admin<X>, mss, ecc.. users configuration,
procedure for different users on the O&M VIP check on reachability of 31310 port on the
connection O&M VIP

28 Security Management Test List

Check that SAPC supports password admin<X>, mss, ecc.. users configuration
authentication

28 Security Management Test List

Check that SAPC supports public key admin<X>, mss, ecc.. users configuration
authentication

28 Security Management Test List

Check that SAPC supports both access levels admin<X>, mss, ecc.. users configuration
(adim2/admin1)
28 Security Management Test List
O&M Verify the correct behaviour of FTU transfer.

O&M Verify that is possible to perform BSP basic

configuration trough its dedicated CLI
O&M Verify the format and the proper generation of
BSP8100 alarms. For Example the following
alarms can be tested:
-appInterfaceAlarm (no route to APP)
- bspNotRedundantAlarm (one or more
switch blades are locked )
- externalLinkAlarm (The alarm is raised
when a fault with external link has been
detected)
-externalNtpReferenceUnavailableAlarm
(The alarm is issued when external time
reference is unavailable.)

O&M Verify BackupFormatter and DBEPARSER

output

O&M Check the correct creation of

measurements file.
Check the format of all the folloowing files:
sapc, sapc-global, platform, and the 2
diameters
Check the most common counters
 Created
Specific Expected Requirem Obsolete N sort Priority
Note Date
Input Results (optional) ent Ref. (Yes/No) (optional) (optional)

password Check that

change after the
procedure password
change
executed by
mast, root
user can
connect via
the
password
previously
chosen by
mast user.

request Check that

changeOwn after
Password password
request change
change<use executed,
r_name>Pa the different
ssword users can
authenticate
via ralted
chosen
password.

Check that
different
users can
authenticate
via
password
anthenticati
on

Check that
different
users can
authenticate
via public
key
anthenticati
on

Check that
different
admin users
have
differente
access level PASS
ON-
GOING

ON-
GOING
 ID
(lasc
iare
vuot Test ID Description Test List name
o)

Verify BSP platform resilience when

a CMXB board is out of service. In
normal condition both CMXB (right
and left) handle OSPF connectivity
1.1 CMXB fault Resilience
towards PE. When a CMXB is out of
service all traffic type (O&M, Traffic,
NBI, ecc...) should be handled by the
other CMXB

Verify BSP platform resilience when

1.2 SCXB fault the active SCXB board (0-0) is out of Resilience
service.

A web browser is available

1.3 - Ethernet interface
GEORED
fault

A web browser is available

1.4 - Vip Ospf Unavailable
GEORED
Gateway
 Preparati Specific
#VALUE! Purpose
on Input

Check: Check:
-verify Traffic VIP connectivity -verify Traffic VIP connectivity
-verify O&M VIP connectivity -verify O&M VIP connectivity
-verify NBI adrress connectivity -verify NBI adrress connectivity
-Verify that on-going diameter -Verify that on-going diameter
sessions are not impacted by the sessions are not impacted by the
fault fault
-Verify that new Diameter session are -Verify that new Diameter session
correctly handled by the other CMXB are correctly handled by the other
CMXB

Check: Check:
-verify Traffic VIP connectivity -verify Traffic VIP connectivity
-verify O&M VIP connectivity -verify O&M VIP connectivity
-verify NBI adrress connectivity -verify NBI adrress connectivity
(dmxractive address switch from (dmxractive address switch from
primary SCXB to standby SCXB) primary SCXB to standby SCXB)

Verify that if an Ethernet interface fault

occurs, the alarm notification is correctly
triggered
Verify that if an Ethernet interface fault
occurs, the alarm "Vip Ospf Unavailable
Gateway" is correctly triggered.
 Requirem Obsolete N sort
Note Created Date (optional)
ent Ref. (Yes/No) (optional)

pass

pass

To be done (Alarm can be

generated on SAPC, but need
SNMP ready)
To be done (Alarm can be
generated on SAPC, but need
SNMP ready)
 Priority
(optional)