The customer has configured various VLANs on the switch trunk port. The switch trunk port is connected to the SSR interface (bond interface) which is also configured as a trunk port. Whenever the customer connects a device to the trunk port of the SSR, it is assigned an IP-Address from a different VLAN rather than an IP-Address from the VLAN it is assigned to.

Devices are receiving an IP-Address from a different VLAN as compared to the VLAN they are assigned to

When the customer connects the device to the SSR and expects that it can receive an IP-Address from multiple VLANs, we need to first check if the port is configured as a trunk port and if the required networks are assigned to the interface.

Once we have verified whether the networks are assigned to the interface, we will check if the DHCP server is working correctly. To do so, we can either check the DHCP related logs in SSR or we can connect a different device to the same trunk port to check whether the device is assigned an IP-Address from the assigned VLAN.

If the device is getting assigned a proper IP-Address from the assigned VLAN, then we need to check the port profile for the trunk port on the switch side. The port profile for the trunk port on the switch side needs to allow the assignment of the IP-Addresses from all the VLANs. If the VLAN is missing in the port profile for the trunk port, then add the VLAN to the trunk port and save the changes.

Once the changes have been committed on the switch, you can either revoke the existing lease for the device from the MIST GUI or you can restart the device to check if it gets the IP-Address assigned from the proper VLAN.