Forum Discussion
Route Domain Issue
Hello all,
I want to let the traffic from client @ non-default route domain "RD 95", to be able to communicate with server @ default route domain "0", so i did the following configuration:
1- create 2 VLANs. 2- create the non-default RD, and disabled "strict isolate" at both RDs "0 & 95" 3- create self IP for both Vlans, e.g 1.1.1.1 & 2.2.2.2%95 4- create pool member e.g 1.1.1.190 5- create VS, source 0.0.0.0%95/0 Destination: 2.2.2.154%95/32
But the connection didn't complete, when i tried to troubleshoot it using tcpdump, i can see the following 1- the client traffic hits the VS successfully, but there's no traffic goes to the pool member?! 2- also i'm seeing that the server-vlan self IP trying to communicate with the VIP (both not in the same RD), i don't know why?
actually i don't know what i missed, although if I created the same design but the client in default RD, and the server in the non-default, i don't face any problem and the traffic pass as normal.
2 Replies
- cjunior
Nacreous
is not this a network routing issue? if you run "rdexec 95 ip route get 1.1.1.190" and "rdexec 95 ping 1.1.1.190", what happens? [ ] Could you paste config snippets of both items here?
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com