This message was deleted.

It sounds like you're just kind of creating IPs without telling the ADC how to handle them. When adding resources on a new segment you need to create a VLAN on the ADC, create a SNIP for that segment, bind that SNIP to that VLAN, then bind that VLAN to the network interface (or channel) that connects that segment to your actual network.

I did all of this. But still doesn't work.

There is, you have to tag the VLANs you are sending across the channel from the switch, configure the ADC with the same VLAN tags and ensure it's configured to tag that traffic.

I will have to google that. I did see a route I created has a downed state. I am going to troubleshoot that. Thank you Mike.

Is this Physical or Virtual? I'm assuming physical as you mention LACP? (Maybe mistyped as LCAP?, Or something I don't know).

Yup Mistyped. It is on a Physical SDX. I haven't had a chance to look at the tagging yet, but I am kind of a noob when it comes to the network part of things.

No, but your switch config needs to match what you set on the SDX. So the SDX can do this two ways, it can add a second adapter using the LACP interface which is on a tagged VLAN or you can tag a VLAN inside the NetScaler instance on the single interface. Either way you need the VLANs tagged on your switch side on the port channel/LACP interface.

The Netscaler is across the country and I would have to fight for some SFPs and Fiber. Otherwise, I would rather have the traffic isolated.

In that case, go down the tagging route. Tag the VLANs on the switch side for the LACP interface and then you can just tag them in the SDX config and pass another adapter through to the VPX instance(s).