NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

StreamlineTech's avatar
Jun 28, 2024

Slow SQL and Application Response on L3 network

To give a brief explanation.

 

Netgear M4300-12X12F ProSAFE > Core sw

Aruba Instant On 1930 48G Class4 PoE 4SFP/SFP+ 370W Switch JL686A > User Switches

 

Server network > 192.168.16.0 direct Connected 10Gbe to Core (untagged) core is router 192.168.0.254 vlan16

End user connected to Aruba 10.0.24.0\0 (1GB) Core is Router on 10.0.24.1 

Netgear to Aruba 10Gbps (fiber) (vlan24) 

End user connected on 1Gbps

 

 

Test 1

User slow response on odbc connection to SQL server from 10.0.24.0  (30 – 90 sec)

 

Test 2.

Test VM fast ODBC connection to SQL on 192.168.16.0 network (1sec) - Separate server from SQL

 

Test 3.

If I add user to vlan 192.168.16.0 using the same equipment not changing pysical port but adding user to vlan 16.

ODBC connection is fast (1 sec)

 

Test 3.

0n 10.0.24.0 – Copy of files – Normal – Ping >1ms app launch normal. 

 

I am not sure where to start looking as there is no latency, copies from the server on 5GB+ files are immediate and fast (800+MBps)

SQL is slow when routing thru the core switch between Lan’s

Applications are slow to communicate with SQL servers. 

No network storm detected.

I did not set up any security on the core SW.

 

Any advice as to what i can test or check. 

 

4 Replies

  • schumaku's avatar
    schumaku
    Guru - Experienced User

    Something to challenge support 24/7 proAVdesign@netgear.com by e-mail please.

     

    I'll challenge a moderator to move this thread to the Managed Switches section btw, too. 

     

    Regards,

    -Kurt.

    • StreamlineTech's avatar
      StreamlineTech
      Aspirant

      Only our local distribution support as the product support has expired.

      But will give them a shout. 

      • BrianL's avatar
        BrianL
        NETGEAR Moderator

        Hi StreamlineTech,

         

        Just keep the thread active on what happens with the investigation of the support team.

         

         

        Kind regards,

         

        BrianL