Forum Discussion
EllisD_26132
Nimbostratus
Oct 14, 2009Default route for Route Domain
Can anyone tell me why I cannot add a default route for a non-default route domain on my 10.0.1 HF2 box?
route domain 1 {
description "Front_End"
vlans {
WF_Front_Ext
WF_Front_Int
}
}
self 10.0.41.251%1 {
netmask 255.255.255.0
vlan WF_Front_Ext
allow default
}
self 10.0.42.251%1 {
netmask 255.255.255.0
vlan WF_Front_Int
allow default
}
Trying to add a default route as:
route any%1 {
gateway 10.0.41.1
}
Results in an error "01070330:3: Static route gateway 10.0.41.1 is not directly connected via an interface."
It does allow me to add the route as:
route any%1 {
gateway 10.0.41.1%1
}
But it doesn't appear to work. The documentation on page 10-13 of the "TMOS Management Guide" says that you *don't* need to append "%X" prefix when specifying the gateway for a default route.
Clearly 10.0.41.1 *is* directly connected out of my "WF_Front_Ext" interface vlan......
Any help appreciated!
Thanks,
Ellis
14 Replies
- QH_74273
Nimbostratus
I'm running into the same issue. Any suggestion?
thanks,
QH - EllisD_26132
Nimbostratus
Sorry, no!
In the end I decided not to use route domains but instead to use VLAN group's.
Although this appears to of created another issue with the stand-by device....but that's another story! :-)
Good luck. - kev_245_28249
Nimbostratus
Has anyone risen above this problem? - Josh_Hill_17083
Nimbostratus
I have always had to use the % route domain specification on the back of the gateway address when adding a default route for a route domain. - kev_245_28249
Nimbostratus
Are you meaning that you select 'route' rather than 'gateway' and then configure the route with the %id after it? Also choosing the relevant route domain in the drop down.
Thats what i've done.
Having issues with arp not working. If I put static arp entries in it works for me. - kev_245_28249
Nimbostratus
Using administrative partitions in combination with my route domain sorted my arp issue. - epaalx
Cirrus
Posted By EllisD on 10/14/2009 06:06 AM:
route any%1 {
gateway 10.0.41.1
}
Results in an error "01070330:3: Static route gateway 10.0.41.1 is not directly connected via an interface."
It does allow me to add the route as:
route any%1 {
gateway 10.0.41.1%1
}
But it doesn't appear to work. The documentation on page 10-13 of the "TMOS Management Guide" says that you *don't* need to append "%X" prefix when specifying the gateway for a default route.
_______
Looking at "Adding a standard route for a route domain" section of above document: "If the route you are adding pertains to a partition default route domain, you do not need to indicate the relevant route domain in the route’s IP addresses (using the %ID notation). If the route you are adding pertains to a route domain other than the partition default route domain, you must include the relevant route domain ID."
So, the way I read it is if the default route domain, is specified within partition definition, using "partition name default rd id", then any route you define in this partition without %ID will apply to that route domain.
However, since there can be more than one route domain within a partition to define route for those which isn't default route domain, you'll need to specify %ID. - nitass
Employee
And then we check and test to ping IP Gateway 192.168.208.254 and the result host unreachable you did ping from bigip, didn't you? what command did you use? was it "ping 192.168.208.254%2"? - Taufik_90468
Nimbostratus
Hi Nitass,
Yes I did, I ping from bigip and use command ping 192.168.208.254%2
Thanks.
Best regards,
Taufik- Richard_ShufordRet. EmployeeWhat would happen if you tried "rdexec 2 ping 192.168.208.254" ?
- Sriram_87174
Nimbostratus
Can you check the default route you created is 0.0.0.0%2
Thanks,
Sriram
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
DevCentral Quicklinks
* 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
Discover DevCentral Connects