I've only touched the Local Director a few times but I think you need to consider the following:
1- The Local Director is a bridge. Having the user facing interface in VLAN10 and in network 192.168.1.0, and the server interface in VLAN 20 and in network 192.168.2.0 seems like there may be a conflict there. Consider having the user interface and server interface in the same VLAN.
2- Again, the Local Director acts like a bridge. Having both interfaces of the LD on the same switch and acting as a bridge between the users and the servers will probably not work. Consider having the LD user interface attached to the network switch and then a separate switch just for the servers attach to the other interface of the LD. All traffic to and from the servers will then have to pass through the LD.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...