I'm probably doing something completely wrong, or missing something very small, but I have to fix this.. I have a Windows server with a dual adapter lag to a core switch. The server has a static IP on the lag, and the default route is on the same subnet. Due to an unforseen reason, I've had to temporarily enable NFS for this server and attach some storage to another server (VMware). In order to do this, I created a private subnet just for this connection and added an IP on this subnet as an alias on the lag interface. This NFS subnet should obviously not be routed, but the server is now deciding to use the new NFS subnet IP as the source for new routed flows instead of the original IP that is on the same subnet as the default route. How do I prevent this? Or should I not be using an alias to create a storage network, however temporary, in the first place?
No comments:
Post a Comment