Forum Discussion

epaalx's avatar
epaalx
Icon for Cirrus rankCirrus
Feb 10, 2012

Inter-partition traffic

Hi F5'ers,

 

I've inherited a multi-Partition configuration (with a single Routing Domain in each), with the Common partition not used for data traffic. In my case, all administrators have access to all Partitions, so there's really no advantage of segregating the configuration using Partitions.

 

 

I now need to have traffic across Routing Domains (particularly, VS in on RD and pool member in another). However, configuration of such is is prevented by the fact that both RDs are in different Partitions.

 

 

My question: is it possible to override inter-Partition restriction, perhaps with a magic DB attribute?

 

R's, Alex

 

 

 

basic
getting started
new to f5
  • nitass's avatar
    nitass
    Icon for Employee rankEmployee
    Feb 10, 2012
    My question: is it possible to override inter-Partition restriction, perhaps with a magic DB attribute?as far as i know, i do not see that kind of db variable.
  • Hamish's avatar
    Hamish
    Icon for Cirrocumulus rankCirrocumulus
    Feb 15, 2012
    If you disable strict segregation I think routing domains will do what you want.

     

     

    H
  • nitass's avatar
    nitass
    Icon for Employee rankEmployee
    Feb 16, 2012
    thanks Hamish! i might be misunderstanding. what i concern is object such as pool resides in different route domain which is in different partition. so, i think we may not be able to select it when configuring virtual server.

    e.g. 

    [root@B3900-R66-S14:Active] config  b vlan list
vlan external {
   tag 3438
   partition par1
   interfaces tagged 1.1
}
vlan internal {
   tag 423
   partition par2
   interfaces tagged 1.1
}
[root@B3900-R66-S14:Active] config  b route domain list
route domain 0 {
   description "Default Route Domain"
}
route domain 1 {
   strict disable
   partition par1
   vlans external
}
route domain 2 {
   strict disable
   partition par2
   vlans internal
}
[root@B3900-R66-S14:Active] config  b self list
self 100.100.100.14%1 {
   netmask 255.255.255.0
   vlan external
   partition par1
   allow default
}
self 200.200.200.14%2 {
   netmask 255.255.255.0
   vlan internal
   partition par2
   allow default
}

[root@B3900-R66-S14:Active] config  b shell write partition par1
[root@B3900-R66-S14:Active] config  b pool foo member 200.200.200.101%2:80 add
BIGpipe pool member creation error:
   0107098a:3: The ip address (200.200.200.101%2) for a node address in partition (par1) references a route domain (2) in a different partition (par2). Objects may only reference objects in the same or the 'Common' partition

    or am i totally lost??
  • Hamish's avatar
    Hamish
    Icon for Cirrocumulus rankCirrocumulus
    Feb 16, 2012
    Sorry, I missed the implication that you were keeping the partitions... I'm not so sure that inter partition stuff is possible (That's kind of why they were implemented IIRC).

     

     

    H