VLAN Configuration and Connectivity Issue on Core Switch (MS 425-32)

[Azar]

Hi All,

We have configured an SVI on the MS 425-32 core switch. A server is connected to the core switch (Port 24) using a fiber patch cord. We assigned a static IP address (10.0.18.8/24, VLAN 18) to the server.

However, when checking the connected device on Port 24, it displays the configured IP but shows VLAN 1 instead of VLAN 18, and we are unable to ping the gateway (10.0.18.1) from the server.

When we change the switch port to an access port, it shows VLAN 61, and we are able to ping the gateway.

Additionally, we have other servers running on the same switch. Their switch ports are configured as trunk ports and can communicate with different VLANs.

The NIC on the server is a Cisco - Intel E810XXVDA2 2x25/10 GbE SFP PCIe NIC

Questions:
1. Does the end server need to support VLAN tagging?
2. What steps should be taken in such a scenario?

Regards,
Azarudeen

[alemabrahao]

Yes, the end server must support VLAN tagging if it is connected to a trunk port on the switch.

Refer to the server's NIC documentation for specific configuration steps and troubleshooting tips.

[Azar]

Hi @alemabrahao,

Thanks for your valuable input.

[michalc]

Hi @Azar,

1. VLAN Tagging is Required if port 24 is a trunk; not needed for access mode.

2. If you'd like to keep the port 24 as trunk you need to configure the server NIC to tag traffic for VLAN 18 and assign 10.0.18.8/24. Unsure which OS you're using on your server so we can't provide more details on how to setup VLAN tag on your server.

[Azar]

Hi @michalc.,

Thanks for your valuable suggestion.

I will share the OS details once I receive them from our concerned team.

Apart from these, is there anything else that needs to be considered?

[PhilipDAth]

Have you configured the server to use a VLAN tag?