1 ############################################################################################################################
2 # Date: <31/08/2016> Version: <1.1> #
3 ############################################################################################################################
5 Feature:Attach_Procedure_AttachWithIMSI_Wrong_MCC
7 @attach-procedure @Attach_Procedure_AttachWithIMSI_Wrong_MCC @TS_24_301 @24_301_5_5 @24_301_5_5_1_2_2 @TS_24_368 @24_368_4 @24_368-5_4 @Series-0000
9 Scenario: Attach Procedure Failure due to wrong MCC.
11 Given all configured endpoints for SSH are connected successfully
13 Given the steps below will be executed at the end
14 When I stop S1AP simulator on node ABOT
15 When I run the SSH command "sudo service mme_gw restart" on node MME
16 Given the execution is paused for {abotprop.WAIT_10_SEC} seconds
17 Then the ending steps are complete
19 # set ABOT configuration
20 Given that I setup S1AP Simulator with default parameters specified in {abotprop.ABOT.EPC.Defaults} on node ABOT
21 Given that I setup S1AP Simulator with EPC parameter "ABOT.ENB.mobile_country_code=201" on node ABOT
23 # Execute ABOT S1AP Simulator
24 When I run S1AP simulator on node ABOT with 1 UE
26 Given the execution is paused for {abotprop.WAIT_10_SEC} seconds
28 # Validate Test Case Execution at Simulator
29 Then I receive S1AP response on node ABOT and verify the presence of all the following values:
30 | responseResult | existence |
31 | Received s1 setup failure for MME | {string:nocase:present} |