Forum Discussion
Stefan_Klotz
May 26, 2015Cumulonimbus
In the meanwhile I tried to re-built this setup on a VE on my laptop with the following results:
- First I configured everything in Common (no RD used) -> Logon page loaded correctly
- Then I created a RD and another VS within this RD -> issue as described above occurred again
- Then I change the value for "Parent ID" within the RD from the default "None" to "0" -> Logon page loaded correctly
Both RDs (Common and the new created one) have no routes specified at all and all VLANs are directly connected. From what I read in the documentation this parent ID setting is only required for routing lookup, so it shouldn't matter in our setup at all. But why does it behaving differently with both options?
And according to our production system, is there any risk, when changing the parent ID from "None" to "0"?
Thank you!
Ciao Stefan :)