1.

Diagnostics
1.1 VSATDIAG1 Diagnostic Recent History
Purpose
To verify the ability of VSAT to: - maintain recent history of diagnostics related statistics and problems of last one hour and; - display the same on Web GUI

Dependency
None

Configuration
None

S.No. 1

Test Procedure - Bring up the VSAT - Open VSAT GUI and go to

Advanced => Diagnostics => Current Hour History

Expected Result - Recent diagnostics history, for the last one hour, should show up. There should be two sections. First one is 'Problem' which should display the 'Common Problems' configured and Second section is 'Activity' which will list the status of LAN, Uplink and Downlink traffic. - First row should list minutes with 5minutes interval (default) up to last 1 hours while first column should list problems and traffic activities. - Under 'Problem' section, status should display: 'Red X' in case problem was detected for that particular row in that particular interval. 'Green Tick' in case no problem was detected ' - ' in case status Not available

- Under 'Activity' section, status should display: Single bar ( | ) representing IDLE status Double bars ( || ) representing TYPICAL status Three consecutive bars ( ||| ) as HIGH traffic activity

- Clicking on either status should display the detailed stats for that interval.

1.2 VSATDIAG2 Diagnostic Hourly History

Purpose
To verify the ability of VSAT to: - maintain hourly history of diagnostics related statistics and problems of the last one day and; - display the same on Web GUI

Dependency
None

Configuration
None

S.No. 1

Test Procedure - Bring up the VSAT - Open VSAT GUI and go to

Advanced => Diagnostics => Hourly History

Expected Result - Hourly diagnostics history, for the last 24 hours, should show up. There should be two sections. First one is 'Problem' which should display the 'Common Problems' configured and Second section is 'Activity' which will list the status of LAN, Uplink and Downlink traffic. - First column should list problems and traffic activities while first row should list hours with 1 hour interval (default) up to last 24 hours. - Under 'Problem' section, status should display: 'Red X' in case problem was detected for that particular row in that particular interval. 'Green Tick' in case no problem was detected ' - ' in case status Not available

- Under 'Activity' section, status should display: Single bar ( | ) representing IDLE status Double bars ( || ) representing TYPICAL status Three consecutive bars ( ||| ) as HIGH traffic activity

- Clicking on either status should display the detailed stats for that interval.

1.3 VSATDIAG3 Diagnostic Detailed history of an Hour

Purpose
To verify the ability of VSAT to: - maintain detailed history, of one hour with 5 minute intervals, of diagnostics related statistics and problems of any hour for last one day and; - display the same on Web GUI

Dependency
None

Configuration
None

S.No. 1

Test Procedure - Bring up the VSAT - Open VSAT GUI and go to

Advanced => Diagnostics => Hourly History

Expected Result Hourly diagnostics history, for the last 24 hours, should show up. There should be two sections. First one is 'Problem' which should display the 'Common Problems' configured and Second section is 'Activity' which will list the status of LAN, Uplink and Downlink traffic. - First column should list problems and traffic activities while first row should list hours with 1 hour interval (default) up to last 24 hours.

- Click on any of these hourly links in first row

- Detailed diagnostics history, for given one hour, should show up. - First row should list minutes with 5minutes interval (default) up to last 1 hours while first column should list problems and traffic activities. - Under 'Problem' section, status should display: 'Red X' in case problem was detected for that particular row in that particular interval. 'Green Tick' in case no problem was detected ' - ' in case status Not available

- Under 'Activity' section, status should display: Single bar ( | ) representing IDLE status Double bars ( || ) representing TYPICAL status Three consecutive bars ( ||| ) as HIGH traffic activity

- Clicking on either status should display the detailed stats for that interval.

1.4 VSATDIAG4 Diagnostic Enable/Disable

Purpose
To verify the ability of IPGW to enable or disable the Diagnostics via configuration parameter

Dependency
None

Configuration
None

S.No. 1

Test Procedure - Configure the VSAT terminal with:

diagCfStatsMonEnabled = 2 (Enabled)

Expected Result

- Bring up the VSAT - Open VSAT terminal GUI and go to

Advanced => Diagnostics => Hourly History

- Hourly diagnostics history, for the last 24 hours, should show up.

- Disable the diagnostics support of VSAT by modifying following configuration parameter to :

diagCfStatsMonEnabled =1 (Disabled)

- It should show "Diagnostics is disabled"

- Open VSAT terminal GUI and go to

Advanced => Diagnostics => Hourly History

- Re-enable the diagnostics support by setting the VSAT terminal with:

diagCfStatsMonEnabled = 2 (Enabled)

- Hourly diagnostics history, for the last 24 hours, should show up.

- Bring up the VSAT - Open VSAT terminal GUI and go to

Advanced => Diagnostics => Hourly History

1.5 VSATDIAG5 Diagnostics - Problem Detection

Purpose
To verify the ability of VSAT diagnostics feature to detect pre-defined problems and indicate them via Web GUI example - Association, TCP Acceleration

Dependency
None

Configuration
None

S.No. 1

Test Procedure - Bring up the VSAT terminal - Connect the downlink cable from VSAT to IPGW - Once the VSAT is associated with IPGW, wait for a complete short interval. - Now open VSAT GUI and go to
Advanced => Diagnostics => Current Hour History

Expected Result Recent diagnostics history, for the last one hour, should show up. - Verify that the column(s) of row showing "Association" should display "Green Tick" indicating Good Status. Verify the same by clicking on the Green Tick which should open up detailed stats. - Detailed stats for 'Downlink' should display its status as GOOD:
--------------------------------------------------------------Downlink Diagnostic Statistics --------------------------------------------------------------Status GOOD

-Now Plug-out the downlink cable from VSAT to IPGW - Atleast wait for a complete short interval. - Now open VSAT GUI and go to
Advanced => Diagnostics => Current Hour History

- Verify that the column(s) of row showing "Association" should display "Red X" indicating Bad Status. Verify the same by clicking on the Red X which should open up detailed stats. - Detailed stats for association should display its status as BAD.
--------------------------------------------------------------Downlink Diagnostic Statistics --------------------------------------------------------------Status BAD

Repeat the required procedure for rest of the diagnostics stats.

- Observation should be similar to the one mentioned above.

1.6 VSATDIAG6 Diagnostics - Traffic 'Activity'

Purpose
To verify the ability of VSAT diagnostics feature to analyze the traffic stats for LAN, Uplink & Downlink and display them via Web GUI

Dependency
None

Configuration
None

S.No. 1

Test Procedure - Bring up the VSAT terminal - Configure the LAN thresholds for parameters diagCfLanTxActThreshMin=100 diagCfLanTxActThreshMax=130 - Connect the LAN cable to VSAT - Do some activity like ping or terminal webpage opening etc. - Now open VSAT GUI and go to
Advanced => Diagnostics => Current Hour History

Expected Result Recent diagnostics history, for the last one hour, should show up. - The column of row showing "LAN Tx" should display bar(s) indicating traffic Status either | , | | or |||. Verify the same by clicking on the bar which should open up detailed stats. - Detailed stats for 'LAN Tx' should display its 'Activity' status as IDLE for |, TYPICAL for || and HIGH for |||. This should be verified in following sense: If Rate < diagCfLanTxActThreshMin then IDLE If Rate > diagCfLanTxActThreshMin and Rate < diagCfLanTxActThreshax then TYPICAL If Rate > diagCfLanTxActThreshMax then HIGH
Bytes 11.85K Packets 105 Rate 0.32Kbps Activity HIGH

Interface LAN Tx

-Now Plug-out the LAN cable from VSAT - After pulling out cable atleast wait for a complete short interval. - Now open VSAT GUI and go to
Advanced => Diagnostics => Current Hour History

- Verify that the column(s) of row showing "LAN Tx" should display | indicating Idle Status as no packets were transferred. Verify the same by clicking on the | which should open up detailed stats. - Detailed stats for 'LAN Tx' should display its packets count as zero.

Repeat the similar procedure for rest of the 'Traffic' Activity.

- Observation should be similar to the one mentioned above.

1.7 VSATDIAG7 Diagnostic Log File Problem History

Purpose
To verify the ability of VSAT to: - maintain hourly history of diagnostics related statistics and problems of the last one day in the csv files; - display the same on Web GUI under 'Archived Hourly Hours' link

Dependency
None

Configuration
None

S.No. 1

Test Procedure - Bring up the VSAT - Open VSAT GUI and go to Advanced => Diagnostics => Archived Hourly Hours - Click on any of the link to display the hourly history date stored in the file.

Expected Result - Hourly diagnostics history, for the number of records stored in that file should show up. There should be two sections. First one is 'Problem' which should display the 'Common Problems' configured and Second section is 'Activity' which will list the status of LAN, Uplink and Downlink traffic. - First column should list problems and traffic activities while first row should list hours with 1 hour interval (default) up to last 24 hours. - Under 'Problem' section, status should display: 'Red X' in case problem was detected for that particular row in that particular interval. 'Green Tick' in case no problem was detected ' - ' in case status Not available

- Under 'Activity' section, status should display: Single bar ( | ) representing IDLE status Double bars ( || ) representing TYPICAL status Three consecutive bars ( ||| ) as HIGH traffic activity

- Clicking on either status should display the detailed stats for that interval.