Traceability Matrix EIDU

Approx No Of CasesE1 functionality (Copper)BER(Mef,UDP) 4Clock Recovery 1Clock Stability 1Jitter/Wander 2BER with different delay using IP Net Sim 9BER with Packet loss insertion using IPNet Sim 4Pulse maskE1 functionality (Fibre)BER(Mef,UDP)Clock Recovery Clock StabilityJitter/WanderPulse Mask

OAMWebGUI 12Configuration(Link,E1 port) (Create,Modify,Delete) 17Header Config(MEF,UDP) System date & Time Configuration, Save Current configuration,

Restore Factory Configuration,Reboot System, Firmware

Upgrade 7SNMP 21FCAPS/Alarms 40OMC integration 22

IP Tests (Copper) IP Address, Subnet Mask, Gateway, (Management port) 5TDMoIP IP Interface Configuration:- IP Address, GatewayStatic and DHCP mode 1

Switch Configuration: 15Bandwidth ControlQnQMirroringATU Id/VLAN tests 2Delay in n/w 2Packet-loss in n/w 2Background trafficIP-flooding

IP Tests (Fibre)Background trafficIP-floodingMultiplexing of E1-bundles over Cu and Fibre

DiagnosticsE1 port loopback test

Power TestsPoE TestsPower Consumption

EIDU

Load&StabilityEthernet Load 4Multiple bundles/multiple timeslots(All E1 ports) 2Long-term stability 4

StatusE1 port Status config 1E1 link status 2ODU,Management port Ethernet port

StatisticsE1 link statistics single/multiple links 5Switch port statistics(good/Bad frames) 4TOTAL 189

Test Case ID Test Case Title

VNLTS_CONF_TU_001 Root TU to BTS TU link with different Bundle ID.

VNLTS_CONF_TU_002 Root TU to BTS TU link with different Destination IP.

VNLTS_CONF_TU_003 Root TU to BTS TU link with different source UDP ports.

VNLTS_CONF_TU_004 Root TU to BTS TU link with different destination UDP ports.

VNLTS_CONF_TU_005 Root TU to BTS TU link with different E1 ports.

VNLTS_CONF_TU_006 Root TU to BTS TU link with different number of time slots.

VNLTS_CONF_TU_007 Root TU to BTS TU link with CESoPSN as payload.

VNLTS_CONF_TU_008 Root TU to BTS TU link with different payload sizes.

VNLTS_CONF_TU_009 Root TU to BTS TU link with different jitter buffer sizes.

VNLTS_CONF_TU_010 Root TU to BTS TU link when clock recovery is enabled/disabled.

VNLTS_CONF_TU_011 Links between Root and BTS TU remain un-affected in case of any link being

Enabled/Disabled. VNLTS_CONF_TU_012 Addition of new link does not affect existing links between Root and BTS TU.

VNLTS_CONF_TU_013 Deletion of new link does not affect existing links between Root and BTS TU.

VNLTS_CONF_TU_014 Successful updating of link status Table for Root TU and BTS TU.

VNLTS_CONF_TU_015 Successful incrementing of Statistics counters in link statistics table for Root TU and BTS

TU.VNLTS_CONF_TU_016 Root and BTS TU E1 port configuration for different E1 ports.

VNLTS_CONF_TU_017 Root and BTS TU E1 port configuration for different Rx sensitivity.

VNLTS_CONF_TU_018 Successful updating of E1 status Table for Root TU and BTS TU.

VNLTS_CONF_TU_019 Successful configuration of ISP IP with different IP address in IPv4 format at Root TU

and BTS TU.VNLTS_CONF_TU_020 Successful configuration of ISP IP with different IP address in IPv6 format at Root TU

and BTS TU.VNLTS_CONF_TU_021 Successful configuration of BSC IP with different IP address in IPv4 format at Root TU

and BTS TU.VNLTS_CONF_TU_022 Successful configuration of BSC IP with different IP address in IPv6 format at Root TU

and BTS TU.VNLTS_CONF_TU_023 Successful configuration of TDMoIP with different IP address at Root TU and BTS TU.

VNLTS_CONF_TU_024 Successful incrementing of Statistics counters in TU Network statistics table for Root TU

and BTS TU.VNLTS_CONF_TU_025 Contents of System Configuration table is accessible and in-editable

VNLTS_CONF_TU_026 Successful Statistics Configuration with different values at Root TU and BTS TU.

VNLTS_CONF_TU_027 Successful RTC Configuration with different values at Root TU and BTS TU.

VNLTS_CONF_TU_028 Successful OMC IP Configuration with different IP addresses at Root TU and BTS TU

VNLTS_CONF_TU_029 Successful NTP IP Configuration with different IP addresses at Root TU and BTS TU.

VNLTS_CONF_TU_030 Successful up gradation of Firmware software image at Root TU and BTS TU.

VNLTS_CONF_TU_031 Successful Restoration of Factory Default configuration.

VNLTS_CONF_TU_032 Root TU and BTS TU configuration for different Temperature threshold values.

VNLTS_CONF_TU_033 TU Admin State table of Root TU and BTS TU should remain persistent.

VNLTS_CONF_TU_034 Network Interface Configuration table of Root TU and BTS TU should remain persistent.

VNLTS_CONF_TU_035 Link Configuration table of Root TU and BTS TU should remain persistent.

VNLTS_CONF_TU_036 E1 Port Configuration table of Root TU and BTS TU should remain persistent.

VNLTS_CONF_TU_037 Network Configuration table of Root TU and BTS TU should remain persistent.

VNLTS_CONF_TU_038 TU Location Info table of Root TU and BTS TU should remain persistent.

VNLTS_CONF_TU_039 Statistics Configuration table of Root TU and BTS TU should remain persistent.

VNLTS_CONF_TU_040 PoE Control table of Root TU and BTS TU should remain persistent.

VNLTS_CONF_TU_041 RTC Configuration table of Root TU and BTS TU should remain persistent.

VNLTS_CONF_TU_042 Temperature Sensor table of Root TU and BTS TU should remain persistent.

VNLTS_CONF_TU_043 OMC Alarm Configuration table of Root TU and BTS TU should remain persistent.

VNLTS_CONF_TU_044 OMC IP Configuration table of Root TU and BTS TU should remain persistent.

VNLTS_CONF_TU_045 NTP IP Configuration table of Root TU and BTS TU should remain persistent.

VNLTS_FUNC_TU_001 Successful conversion of entire E1 into Ethernet data packets

VNLTS_FUNC_TU_002 Successful conversion of partial E1 into Ethernet data packets

VNLTS_FUNC_TU_003 Successful conversion of entire 2 E1 into Ethernet data packets

VNLTS_FUNC_TU_004 Successful conversion of 2 partial E1 into Ethernet data packets

VNLTS_FUNC_TU_005 Successful conversion of received packet data into corresponding complete E1 in

lossless & delay free IP network.VNLTS_FUNC_TU_006 Successful conversion of received packet data into partial E1 in lossless & delay free IP

network.VNLTS_FUNC_TU_007 Successful conversion of received packet data into complete 2 E1 in lossless & delay

free IP network.VNLTS_FUNC_TU_008 Root TU converts received packet data into corresponding complete E1 in lossless &

delay free IP network for multiple links.VNLTS_FUNC_TU_009 TU converts received packet data into corresponding complete E1 in lossy IP network.

VNLTS_FUNC_TU_010 TU converts received packet data into corresponding partial E1 in lossy IP network.

VNLTS_FUNC_TU_011 Successful conversion of received packet data into corresponding complete E1 in lossy

IP network.VNLTS_FUNC_TU_012 Successful conversion of received packet data into partial E1 in lossy IP network, for

multiple links.

VNLTS_FUNC_TU_013 Successful conversion of received packet data into corresponding complete E1 in delay

network.VNLTS_FUNC_TU_014 Successful conversion of received packet data into partial E1 in delay IP network.

VNLTS_FUNC_TU_015 Successful conversion of received packet data into complete E1 in delay IP network for

multiple links.VNLTS_FUNC_TU_016 Successful conversion of received packet data into partial E1 in delay network for

multiple links.VNLTS_FUNC_TU_017 Successful conversion of received packet data into complete E1 in lossy and delay IP

network.VNLTS_FUNC_TU_018 Successful conversion of received packet data into partial E1 in lossy and delay IP

networkVNLTS_FUNC_TU_019 Successful conversion of received packet data into corresponding complete 2 E1 in lossy

and delay IP network.VNLTS_FUNC_TU_020 Successful conversion of received packet data into partial 2 E1 in lossy and delay

network for multiple links.VNLTS_FUNC_TU_021 Root TU supports maximum of 15 BTS TUs.

VNLTS_ PERFE1_TU_001 Pulse shape of recovered E1 signal remains within defined limit.

VNLTS_ PERFE1_TU_002 BER in recovered E1 remains within defined limit.

VNLTS_ PERFE1_TU_003 BER in recovered partial E1 remains within defined limit.

VNLTS_ PERFE1_TU_004 Bi-directional drop and insert functionality.

VNLTS_ PERFE1_TU_005 Frequency characteristics of recovered E1 data should remain unchanged.

VNLTS_ PERFE1_TU_006 Jitter in received E1 remains within the specified level.

VNLTS_ PERFE1_TU_007 Round trip delay remains within the defined limit.

VNLTS_ PERFE1_TU_008 Wander in received E1 remains within the specified level.

VNLTS_ PERFE1_TU_009 Bit rate accuracy of recovered E1 remains within +/- 50 ppm.

VNLTS_ PERFE1_TU_010 Minimum return loss at the E1 output port of Root and BTS TU is within the defined

limit.VNLTS_LS_TU_001 Root and BTS TU remains operationally stable while carrying 1 E1 data for a link.

VNLTS_LS_TU_002 Root and BTS TU remains operationally stable while carrying 2 E1 data for 2 links.

VNLTS_LS_TU_003 Root and BTS TU remain operationally stable while carrying 2E1 and O&M data for a

link.VNLTS_CONFSNMP_TU_

001

Successful SET and GETBULK operations on TU admin state table

VNLTS_CONFSNMP_TU_

002

Successful SET and GETBULK operation on TDMOIP Network Interface Configuration

tableVNLTS_CONFSNMP_TU_

003

Successful GETBULK operations on TDMOIP Network Interface Statistics table

VNLTS_CONFSNMP_TU_

004

Successful SET and GETBULK operation on E1 port configuration table

VNLTS_CONFSNMP_TU_

005

Successful GETBULK operations on E1 port status table

VNLTS_CONFSNMP_TU_

006

Successful SET and GETBULK operations on Link Configuration Table

VNLTS_CONFSNMP_TU_

007

Successful GETBULK operations on Link Statistics Table

VNLTS_CONFSNMP_TU_

008

Successful GETBULK operations on Link status Table

VNLTS_CONFSNMP_TU_

009

Successful SET and GETBULK operations on Network Configuration Table

VNLTS_CONFSNMP_TU_

010

Successful GETBULK operations on Network Statistics Table

VNLTS_CONFSNMP_TU_

011

Successful GETBULK operations TU Info Table

VNLTS_CONFSNMP_TU_

012

Successful SET and GETBULK operations RTC configuration Table

VNLTS_CONFSNMP_TU_

013

Successful SET and GETBULK operations Temperature Sensor configuration Table

VNLTS_CONFSNMP_TU_

014

Successful SET and GETBULK operations of TU O&M Operations Table

VNLTS_CONFSNMP_TU_

015

Successful GETBULK operations of Software Status Table and BTS TU.

VNLTS_CONFSNMP_TU_

016

Successful SET and GETBULK operations of System OMC Configuration Table

VNLTS_CONFSNMP_TU_

017

Successful SET and GETBULK operations of System OMC Registration Table

VNLTS_CONFSNMP_TU_

018

Successful SET and GETBULK operations of Sector Identification Table

VNLTS_CONFSNMP_TU_

019

Successful GETBULK operations of All the Tables of TU

VNLTS_CONFSNMP_TU_

020

Successful GETNEXT of all the Tables of TU one by one

VNLTS_CONFSNMP_TU_

021

Root and BTS TU OMC configuration for different read community.

VNLTS_CONFSNMP_TU_

022

Root and BTS TU OMC configuration for different write community.

VNLTS_CONFSNMP_TU_

023

Root and BTS TU OMC configuration for different SNMP trap port.

VNLTS_CONFSNMP_TU_

024

Root and BTS TU OMC configuration for different SNMP Agent port.

VNLTS_CONFSNMP_TU_

025

Root and BTS TU OMC configuration for different NEid

VNLTS_CONFSNMP_TU_

026

Root and BTS TU OMC configuration for different Periodic Statistics Timer

VNLTS_CONFSNMP_TU_

027

Default community string for SET is private and public for GET

VNLTS_CONFSNMP_TU_

028

Successful Software download and activation process at Root and BTS TU.

VNLTS_ALARM_TU_001 Verification of factory Default alarm raised at Network Element and received at OMC.

VNLTS_ALARM_TU_002 Verification of Hardware Reset alarm raised at Network Element and received at OMC

VNLTS_ALARM_TU_003 Verification of Hot swap alarm raised at Network Element and received at OMC

VNLTS_ALARM_TU_004 Verification of Temperature Threshold alarm raised at Network Element and received

at OMCVNLTS_ALARM_TU_005 Verification of “IP address update successful” alarm raised at Network Element and

received at OMCVNLTS_ALARM_TU_006 Verification of IP address update failure alarm raised at Network Element and received

at OMCVNLTS_ALARM_TU_007 Verification of Image Upgrade Success alarm raised at Network Element and received at

OMCVNLTS_ALARM_TU_008 Verification of “Image Upgrade Failure” alarm raised at Network Element and received

at OMCVNLTS_ALARM_TU_009 Verification of “Unsuccessful image activation” alarm raised at Network Element and

received at OMCVNLTS_ALARM_TU_010 Verification of “successful Image activation” alarm raised at Network Element and

received at OMCVNLTS_ALARM_TU_011 Verification of “Loss of signal “alarm raised and cleared at Network Element and

received at OMCVNLTS_ALARM_TU_012 Verification of “Loss of sync “alarm raised and cleared at Network Element and received

at OMCVNLTS_ALARM_TU_013 Verification of “RAI “alarm raised and cleared at Network Element and received at OMC

VNLTS_ALARM_TU_014 Verification of “LIU “alarm raised and cleared at Network Element and received at OMC

VNLTS_ALARM_TU_015 Verification of “Port Disabled “alarm raised at Network Element and received at OMC

VNLTS_ALARM_TU_016 Verification of “Port Enabled “alarm raised at Network Element and received at OMC

VNLTS_ALARM_TU_017 Verification of “Link Disabled “alarm raised at Network Element and received at OMC

VNLTS_ALARM_TU_018 Verification of “Link Enabled “alarm raised at Network Element and received at OMC

VNLTS_ALARM_TU_019 Verification of “TU Lock “alarm raised at Network Element and received at OMC

VNLTS_ALARM_TU_020 Verification of “TU Unlock “alarm raised at Network Element and received at OMC

VNLTS_ALARM_TU_021 Verification of “Clock recovery disabling “alarm raised at Network Element and received

at OMCVNLTS_ALARM_TU_022 Verification of “Holdover ON “alarm raised and cleared at Network Element and

received at OMCVNLTS_ALARM_TU_023 Verification of “no reply from module “alarm raised at Network Element and received

at OMCVNLTS_DISC_TU_001 Successful Discovery procedure at TU with factory default configuration

VNLTS_DISC_TU_002 Successful Discovery procedure at TU with configured IP address

VNLTS_DISC_TU_003 Unsuccessful Discovery procedure at TU with configured IP address

VNLTS_DISC_TU_004 Unsuccessful Discovery procedure at TU when there is no DHCP response

VNLTS_DISC_TU_005 Successful Discovery procedure at TU after node comes up

VNLTS_DISC_TU_006 Successful Discovery procedure at TU when link is re-established

VNLTS_REG_TU_001 TU initiates Registration procedure, when OMC is up and TU comes up from the down

state for the first timeVNLTS_REG_TU_002 TU initiates Registration procedure, when TU is up and OMC comes up from the down

state for the first timeVNLTS_REG_TU_003 TU is registered when TU goes down and come back up again

VNLTS_REG_TU_004 TU is registered when OMC goes down and comeback again

VNLTS_REG_TU_005 TU waits for the REG_RSP indefinitely

VNLTS_REG_TU_006 TU sends registration request after socket connection is re-established with OMC

VNLTS_REG_TU_007 TU stops the registration process when it receives REG_RSP as failure

VNLTS_REG_TU_008 TU sends registration request after socket connection is established with OMC

VNLTS_REG_TU_009 TU waits for the CONFIG_RSP indefinitely

VNLTS_REG_TU_010 TU sends CONFIG_STATUS (CMD_FAILED) to OMC; when SNMP read Community value

is nullVNLTS_REG_TU_011 TU sends CONFIG_STATUS (CMD_FAILED) to OMC; when SNMP write Community value

is nullVNLTS_REG_TU_012 TU sends CONFIG_STATUS (CMD_FAILED) to OMC; if Bind fails

VNLTS_REG_TU_013 TU sends CONFIG_STATUS (CMD_FAILED) to OMC; if login to FTP server at OMC fails

VNLTS_REG_TU_014 TU sends REG_REQ only when all its processes are successfully up

VNLTS_REG_TU_015 TU sends REG_REQ only when all its processes are successfully up

VNLTS_REG_TU_016 Successful Registration procedure when no sector information is available

VNLTS_REG_TU_017 Successful Registration procedure when sector information is available

VNLTS_REG_TU_018 Successful Discovery and Registration procedure when there is change in sector

informationVNLTS_REG_TU_019 Successful Registration procedure at TU with configured IP address

VNLTS_REG_TU_020 Verification of Add node process in case of successful Get Bulk operation

VNLTS_REG_TU_021 Verification of transfer of Performance/Alarm log file

VNLTS_FTP_TU_001 Successful Alarm Reconciliation.

VNLTS_FTP_TU_002 Successful Periodic Performance files transfer.

VNLTS_FTP_TU_003 Successful Periodic Alarm files transfer.

VNLTS_FTP_TU_004 Verify TU retries thrice for File Transfer in case of Checksum Failure.

VNLTS_FTP_TU_005 TU resends PERIODIC_PERF_RESP when FILE_INTEGRITY_RSP is not received in time

VNLTS_FTP_TU_006 Verify TU maintains Transaction Id

VNLTS_FTP_TU_007 Successful Periodic Performance file transfer at every expiry of the timer

VNLTS_FTP_TU_008 Successful Periodic Alarm file transfer at every expiry of the timer

VNLTS_FTP_TU_009 TU saves history of all traps in the Alarm log File

VNLTS_FTP_TU_010 Instantaneous File Transfer from TU

TDMOIP_FUNC_TC_001 Check TU link behaviour with 100mts Ethernet cable conncted between TU@BSC and

PCTDMOIP_FUNC_TC_002 BERT for TU@BSC and TU@BTS Connected back to back with a 100mts Ethernet cable

TDMOIP_FUNC_TC_003 Check TU@BSC behaviour when E1+Ethernet traffic is pumped

TDMOIP_FUNC_TC_004 Check TU@BSC behaviour when 100Mbps of Ethernet traffic is pumped

TDMOIP_FUNC_TC_005 Check impact on TU@BSC when ethernet link is gets disrupted for sometime and comes

back TDMOIP_FUNC_TC_006 TU should retain date and Time (as that of OMC) after Reboot and registration

TDMOIP_FUNC_TC_007 Check wthether there is any impact on BERT result while EIC switchover happens

TDMOIP_FUNC_TC_008 Check wthether there is any impact on Ethernet Traffic while EIC switchover happens

TDMOIP_FUNC_TC_009 Check wthether there is any impact on E1+Ethernet traffic while EIC switchover

happens

TDMOIP_FUNC_TC_010 Successful Managed Switch Parameter Modification

TDMOIP_FUNC_TC_011 Check Managed Ethernet Switch Reset

TDMOIP_FUNC_TC_012 Successful Managed Switch DHCP enable

TDMOIP_FUNC_TC_013 Verify 100Mbps CPLD loopback

TDMOIP_FUNC_TC_014 Verify Port Configuration for ODU Port

TDMOIP_FUNC_TC_015 Verify Port Configuration for TDMOIP Port(maxim port)

TDMOIP_FUNC_TC_016 Verify Port Configuration for ISP Port

TDMOIP_FUNC_TC_017 Verify Different link modes of Port Configuration and it's impact on E1

TDMOIP_FUNC_TC_018 Check AuthState parameter in Port Configuration Table

TDMOIP_FUNC_TC_019 Check Mirror Direction parameter in Port Configuration Table

TDMOIP_FUNC_TC_020 Check PortDotqMode parameter in Port Configuration Table

TDMOIP_FUNC_TC_021 Check macFlowControl parameter in Port Configuration Table

TDMOIP_FUNC_TC_022 Check all the parameters in PortBWTable

TDMOIP_FUNC_TC_023 Check all the parameters in PortQinQ Table

TDMOIP_FUNC_TC_024 Check all the parameters in VLANConfigTable

TDMOIP_FUNC_TC_025 Check whether TU@BSC is able to connect to two or more different subnet ips through

internet portTDMOIP_FUNC_TC_026 Verify that no more than 16 Vlans can be created in TU@BSC

TDMOIP_FUNC_TC_027 Check all the parameters in PortStatus Table

TDMOIP_FUNC_TC_028 Check all the parameters in PortStatics Table

TDMOIP_FUNC_TC_029 Check all the parameters in PortStatics Secondary Good Table

TDMOIP_FUNC_TC_030 Check all the parameters in PortStaticsBadFrames Table

TDMOIP_FUNC_TC_031 Check all the parameters in PortAccesslist Table

TDMOIP_FUNC_TC_032 Verify that ALM_ID_SWITCH_ETH_LINK is received at OMC when the Ethernet Cable is

removed from SGSN/ISP/ODU port of M4 Chasis.TDMOIP_FUNC_TC_033 Verify ALM_ID_BOND_PORT_SWAP is received at OMC when the Ethernet cable is

swapped from SGSN1 to SGSN2 or vice versaTDMOIP_FUNC_TC_034 Check Switch VLAN functionality with multiple VLAN's and Ethernet traffic.

TDMOIP_FUNC_TC_035 Check Configuration Save & Reboot functionality .

TDMOIP_FUNC_TC_036 Check Factory default settings of Switch.

TDMOIP_FUNC_TC_037 Check TU throughput with 90% load

TDMOIP_FUNC_TC_038 Check TU throughput with 120% load

TDMOIP_FUNC_TC_039 Verifying card location From Chasis View at OMC

TDMOIP_FUNC_TC_040 Verifying TU Card revision in Bootloader & Linux version at OMC

TDMOIP_FUNC_TC_041 Verifying N/W statistics gets ftped to OMC

TDMOIP_FUNC_TC_042 Verifying N/W interaface statictics Report at OMC

TDMOIP_FUNC_TC_043 Verify BSC0/BSC1 is cannot locked from OMC

TDMOIP_FUNC_TC_044 Verify system(EIC,BSC) cannot be access from ODU or through any Node after ODU

TDMOIP_FUNC_TC_045 Verifying TU CPU/BSC0/BSC1/Maxim not accesible from ISP port when it is unlocked

TDMOIP_FUNC_TC_046 Validate all the statistics(eg- N/W interface statistics) appearing at OMC are exactly the

same as that of webgui TDMOIP_FUNC_TC_047 Check TU behaviour and statistics when packets are getting dropped in between

TU@BSC and TU@BTS TDMOIP_FUNC_TC_048 Check TU behaviour and statistics when packets are getting delayed in between

TU@BSC and TU@BTS TDMOIP_FUNC_TC_049 Check TU behaviour and statistics when duplicate packets are appearing in between

TU@BSC and TU@BTS TDMOIP_FUNC_TC_050 Check wthether there is any impact on BERT result while ICC switchover happens

TDMOIP_FUNC_TC_051 Check wthether there is any impact on Ethernet Traffic while ICC switchover happens

TDMOIP_FUNC_TC_052 Check wthether there is any impact on E1+Ethernet traffic while ICC switchover

happens TDMOIP_FUNC_TC_053 Successful Managed Switch DHCP disable

TDMOIP_FUNC_TC_054 Check Ethernet traffic on all the ports with different traffic and different packet size.

TDMoIP_Alarm_TC_002 ALM_ID_HARDWARE_RESET: Hard reboot the TU and check for HARDWARE_RESET

from the OMCTDMoIP_Alarm_TC_003 ALM_ID_HOTSWAP: Plug out the TU BSC from the Chasy and check for the Hotswap

alarmTDMoIP_Alarm_TC_006 ALM_ID_IMAGE_UPGRADE: Check for the Image Upgrade alarm for the TU from the

OMCTDMoIP_BERT_TC-001 BERT Test for 24 Links.

TDMoIP_CS_TC_004 Remove E1 Link for 2 minutes, connect it back and check the clock status.

TDMoIP_ColdStart_TC_0

01

Powered on the TU BTS after BSC TU successfully powered ON.

TDMoIP_Fact_Default_T

C_001

Test Factory Default will work successfully for TU BSC and TU BTS.

TU_Config_TC_001 Successful Link configuration and Modification for Broadcast Packets and Data Packets.

TU_Config_TC_008 Create more than one Broadcast Link,check TU BSC behavior.(Repeat for TU BTS)

TU_Config_TC_010 Check TU BTS behavior while Broadcast Link is disabled at TU BTS only.(other TU BTS

are working fine).TU_Config_TC_011 Lock/Unlock the Broadcast Link at TU BSC while Traffics are going ON.

TU_Config_TC_012 Lock the broadcast link of TU@BTS and check the behavior of other TU’s.

TDMoIP_PC_TC_001 Power Cycle the TDMoIP units and WITS units while traffic going on and verify link up

TU_Rob_TC_002 Check there is no impact in BERT Test result while one the TU is hotswaped(no traffic

going on this TU, only links configured).TU_Rob_TC_006 Successful system initialisation with Root RU connected(ODU interface connected in

both TU).TU_Rob_TC_017 Check the impact On Chain1 when TU@BSC at Chain 2 is jacked out and Vice Versa

REGR_OMCT_Registratio

n_TC_012

Check the Registration Procedure while adding a new Node and Traffic was going on in

other nodes.TDMOIP_SWDL_001 Successful S/w upgradation and downgrade using OMC-T for All Nodes.

TDMoIP_Alarm_TC_005 ALM_ID_ETH_LINK: Check for the ETH LINK alarm from the OMC for the TU

TDMoIP_Alarm_TC_008 ALM_ID_WATCHDOG_RESET: Kill some process and check for the WATCHDOG RESET

alarm for the TU from the OMCTDMoIP_Alarm_TC_010 ALM_ID_MAXIM_PORT_LINE_ERR: Check for the Port line ERR and its clear alarm for

the TU from the OMC TDMoIP_Alarm_TC_020 ALM_ID_INTERNAL_ERROR: Check for the Internal Error alarm for the TU from the OMC

TDMoIP_Alarm_TC_022 ALM_ID_INFO_ALARM: Check for the Info alarm for the TU from the OMC

TU_SAN_TC_003 Successful E1 Port and Link Configuration done in TDMoIP units using OMC-T.

TDMoIP_CS_TC_006 Insert Delay in between the Links to check the Clock stability.

TU_Config_TC_007 Check TU behavior when Broad cast Link Timeslot and Payload Link Timeslots are

configured as same.TDMoIP_Rob_TC-003 Powered OFF/ON Chassis back to back for 15-20 times, Check the behaviour and check

the alarms from the OMCTDMoIP_Rob_TC-004 Disable EIC Card in chasis, check the behaviour and check the alarms from the OMC

TU_Rob_TC_004 Check there is no impact in BERT Test result while EIC card hot swaped(no tsi done for

this EIC).TU_Rob_TC_010 Check the impact in BERT Test result while PS card hotswaped.(check for both PS card).

TxSys_Perf_TC_003 Generate reports for TDMoIP Units (back to Back) from the OMC

TxSys_Perf_TC_004 Generate reports for WITS Units (back to Back) from the OMC

REGR_OMC-

T_CONF_002

Successful Modification of different parameters for TDMoIP Units from OMC-T

REGR_OMC-

T_CONF_004

Verify Same inventory details(more than 1) for same node.

REGR_OMC-

T_CONF_007

Range Check of OMC-T Registration Config parameters

EIDU Functionality EIDU Sub Functionality

OAM Configuration(Link,E1 port) (Create,Modify,Delete)













Status E1 link status

Statistics E1 link statistics single/multiple links



Status E1 link status

IP Tests (Copper) IP Address, Subnet Mask, Gateway, (Management

port)


port)


port)


port)


port)Statistics E1 link statistics single/multiple links




Couldn't Map Couldn't Map


OAM System date & Time Configuration, Save Current

configuration, Restore Factory

Configuration,Reboot System, Firmware Upgrade




OAM Webgui

OAM Webgui

OAM Webgui

OAM Webgui

OAM Webgui

OAM Webgui

OAM Webgui

OAM Webgui

OAM Webgui



OAM Webgui



E1 functionality

(Copper) BER(Mef,UDP)

E1 functionality


E1 functionality


E1 functionality






E1 functionality

(Copper)

BER with Packet loss insertion using IPNet Sim

E1 functionality

(Copper)


E1 functionality

(Copper)


E1 functionality

(Copper)


E1 functionality

(Copper) BER with different delay using IP Net Sim

E1 functionality


E1 functionality


E1 functionality


E1 functionality


E1 functionality


E1 functionality


E1 functionality




E1 functionality


E1 functionality




E1 functionality

(Copper) Jitter/Wander

Switch ConfigurationDelay in n/w

E1 functionality

(Copper) Jitter/Wander



Load&Stability Long-term stability



OAM SNMP

OAM SNMP

OAM SNMP

OAM SNMP

OAM SNMP

OAM SNMP

OAM SNMP

OAM SNMP

OAM SNMP

OAM SNMP

OAM SNMP



OAM SNMP

OAM SNMP

OAM SNMP

OAM SNMP

OAM SNMP

OAM SNMP




OAM SNMP

OAM SNMP

OAM SNMP



OAM

System date & Time Configuration, Save Current



OAM




OAM FCAPS/Alarms

OAM FCAPS/Alarms


OAM FCAPS/Alarms

OAM FCAPS/Alarms

OAM FCAPS/Alarms

OAM FCAPS/Alarms

OAM FCAPS/Alarms

OAM FCAPS/Alarms

OAM FCAPS/Alarms

OAM FCAPS/Alarms

OAM FCAPS/Alarms

OAM FCAPS/Alarms

OAM FCAPS/Alarms

OAM FCAPS/Alarms

OAM FCAPS/Alarms

OAM FCAPS/Alarms

OAM FCAPS/Alarms

OAM FCAPS/Alarms

OAM FCAPS/Alarms

OAM FCAPS/Alarms

OAM FCAPS/Alarms







OAM OMC integration

OAM OMC integration

OAM OMC integration

OAM OMC integration


OAM OMC integration

OAM OMC integration

OAM OMC integration


OAM OMC integration

OAM OMC integration

OAM OMC integration

OAM OMC integration

OAM OMC integration

OAM OMC integration

OAM OMC integration

OAM OMC integration

OAM OMC integration

OAM OMC integration

OAM OMC integration

OAM FCAPS/Alarms

OAM FCAPS/Alarms

OAM FCAPS/Alarms

OAM FCAPS/Alarms

OAM FCAPS/Alarms

OAM FCAPS/Alarms

OAM FCAPS/Alarms

OAM FCAPS/Alarms

OAM FCAPS/Alarms

OAM FCAPS/Alarms

OAM FCAPS/Alarms



Load&Stability Ethernet Load



OAM Webgui




Switch Configuration
















Switch Configuration ATU Id/VLAN tests

Status E1 port Status config

Statistics Switch port statistics(good/Bad frames)




OAM FCAPS/Alarms

OAM FCAPS/Alarms

Switch Configuration ATU Id/VLAN tests

OAM




OAM




Load&Stability Multiple bundles/multiple timeslots(All E1 ports)

Load&Stability Multiple bundles/multiple timeslots(All E1 ports)


OAM WebGUI







Switch Configuration Packet-loss in n/w

Switch Configuration Delay in n/w

Switch Configuration Packet-loss in n/w




IP Tests (Copper) Static and DHCP mode


OAM FCAPS/Alarms


OAM FCAPS/Alarms

Load&Stability Long-term stabilityE1 functionality

(Copper) Clock Recovery




Configuration,Reboot System, Firmware Upgrade E1 functionality

(Copper) BER(Mef,UDP) E1 functionality











OAM FCAPS/Alarms


OAM FCAPS/Alarms

OAM FCAPS/Alarms

OAM FCAPS/Alarms

OAM SNMPE1 functionality

(Copper) BER with different delay using IP Net SimE1 functionality

(Copper) Clock Stability





OAM OMC integration

OAM OMC integration

OAMOMC integration


OAMOMC integration

Traceability Matrix EIDU

Documents

Transcript of Traceability Matrix EIDU