Printer FriendlyEmail Article Link

Why ARP is not resolved when I ran SGW Nodal test case on LSonSTC (version 10.381)?

Answer

When the ARPs are not resolved, most likely the ARPS for the SGW user IP and the Network Host next hop are not configured correctly.

If the PDN GW Emulation is enabled in SGW Nodal test case:
S1U User IP Address = S1 User SUT field
S1U Peer Interface = eNodeB User Node Next Hop (used to ARP actual interface)
S5 User Interface = PDN GW Next Hop Address (used to ARP the peer tunnel interface)
S5 User Tunnel Destination Address = Network Host Next Hop (work around to set actual Address)
 
If PDN GW emulation NOT Enabled (works as expected):
S1U User IP Address = S1 User SUT field
S1U Peer Interface = eNodeB User Node Next Hop (used to ARP actual interface)
SGi interface = Network Host Next Hop (used to ARP the PDN SGi interface)
 
And there are two things could cause the ARP issue. One, the GlueServer is not ready or running. Two, the interfaces on the DUT are not up.
Anytime the user recycles the TestServer from the GUI (this actually starts and stops the GlueServer), the user should wait around one minute from the time the TestServer gets to the Ready State. The GlueServer has to reserve the ports before a test can be run. One could verify the GlueServer has reserved all the ports by checking out the GlueServer logs. The logs are found /home/spcoast/TestCase/BOF/logs directory.   The file name format of the corresponding GlueServer process is MainServerLog_[DATE]-[TIMESTAMP]-[PID]. But typically waiting a minute or so is sufficient to ensure the GlueServer has reserved the ports.

Product : LSonSTC,Landslide