Aruba 3810M Switch - can't see devices outside of subnet

[ADAMBINGLEY]

Hi there.
Today I installed a new 10g SFP+ network card into a HPE DL380 G9 server that runs OEL 7.1 (ORACLE Enterprise Linux)
The aim was to upgrade the current 1gig network to 2x10gig...
Installation went as expected and the network card was successfully plugged into the correct ports on the Aruba 3810M.

Firstly, only one port was connected.
Port one on the Network Card was plugged into port 5 on the aruba 3810 which has VLAN50 untagged, FYI VLAN50s gateway is on the core switch.
The network card successfully pulled from DHCP which is on another subnet.

However, the new interface can only ping addresses on its own subnet...
The subnet is 10.10.50.0/24 - for example it can ping 10.10.50.1 (gw) and 10.10.50.50 (ESXi host) But cannot ping 10.10.1.1 (core) or 10.10.9.5 (dns), devices outside the 10.10.50.0/24 subnet can't see the new interface either.
Other devices on the same subnet work perfectly, for example 10.10.50.50 Can ping 10.10.1.1 and visaversa.

This is a second network card in the DL380G9 and it is plugged into the 3810m switch, there is also a 1gig Ethernet port plugged into another edge switch which works fine the subnet for that is 10.10.9.0/24

Any assistance would be extremely grateful as we are stumped.

[parnassus]

You wrote: "Other devices on the same subnet work perfectly, for example 10.10.50.50 Can ping 10.10.1.1 and visaversa." so this behaviour means that (a) VLAN 50 is correctly transported over the uplink to your Core Switch (which is responsible for IP Routing - is this assumption correct? - and which act as an home for all VLANs that need be routed each others) and (b) VLAN 50 is correctly routed - by your Core Switch - to other existing VLANs (respectively those with 10.10.1.0/24 and 10.10.9.0/24 subnets).

So a question: what are network settings of your 10G port with respect to the same setting of your 1G port - which is working - on 10.10.9.0/24?

Can you share Aruba 3810M sanitized running config?