Forum Discussion
Nimbostratusmanagement IP and self IP in same network
I am not sure if this question is already been asked in this forum.
I am using BIG-IP-10.x and facing issue while configuring self IP address for vlan because it is in same subnet of management IP and receiving below error
BIGpipe self IP address creation error:
01070392:3: Self IP 10.xx.xx.x1 / 255.255.255.0: This IP shares a network with the management IP (10.xx.xx.x2 / 255.255.255.0).
is there any workaround for this?
Thanks,
- dennypayne
Employee
No, the management port must be on a separate network. The reason is that the management port is simply a NIC that uses an address hosted by the Linux kernel; it is not part of the switch fabric. The rest of the ports are controlled by the tmm kernel(s), so they cannot share address space.
If you don't have a separate management network, then I would just leave mgmt on 192.168.1.245 (assuming you don't use 192.168.1 elsewhere) and configure it through a directly connected laptop. Once you get an address on the switch ports, you can do 99% of the things you need to do in the GUI or CLI from that address (just make sure to leave the default access for port 22 and 443 enabled). About the only thing you really need to be connected to the management port for is to do upgrades.
Denny 
hoolioCirrostratus
You could potentially configure the SCCP IP address on the same subnet as a switch port. See this post (Click here) for details.
Aaron
kevin_50499Posted By msavani on 04/24/2009 5:40 PM
Hi,
I am not sure if this question is already been asked in this forum.
I am using BIG-IP-10.x and facing issue while configuring self IP address for vlan because it is in same subnet of management IP and receiving below error
BIGpipe self IP address creation error:
01070392:3: Self IP 10.xx.xx.x1 / 255.255.255.0: This IP shares a network with the management IP (10.xx.xx.x2 / 255.255.255.0).
is there any workaround for this?
Thanks,- hoolioHi Kevin,
Did you have a question?
Aaron 
GreenbergHi Aaron,
I have a question on this subject.
I'm experiencing the same issues. The Standby Unit won't install configuration from the Active unit (either by a Config Sync or b config install <>).
BIGpipe unknown operation error: 01070391:3: Admin IP 10.15.xx.x / 255.255.254.0: This IP shares a network with a Self IP.
Within the Configuration, there isn't a Self IP within the same network as the MGMT IP Address.
Have you ever encountered this issue?
Chris
nitass_89166Noctilucent
Within the Configuration, there isn't a Self IP within the same network as the MGMT IP Address.
is there route on tmm which covers mgmt subnet?
- GreenbergHi, The MGMT Network is on a /23 but there is a Network Route on TMM which covers this with a /16 network, i.e. MGMT Network 10.1.32.0/23, TMM Route 10.1.0.0/16. Would this be causing the issue?
- nitass_89166i think so.
- GreenbergHi, You were correct. I've "re-subnetted" the Routing Table in TMM to exclude the /23 and it's now working. I've never encountered this before and hopefully the Error Codes are more descriptive in newer versions of the Code. This F5 is running 10.2.3 HF1 but we are upgrading to 11.6 in the near future. It should refer to Routes and NOT Self IPs. Thanks a million for your assistance. Chris
- nitass
Within the Configuration, there isn't a Self IP within the same network as the MGMT IP Address.
is there route on tmm which covers mgmt subnet?
- GreenbergHi, The MGMT Network is on a /23 but there is a Network Route on TMM which covers this with a /16 network, i.e. MGMT Network 10.1.32.0/23, TMM Route 10.1.0.0/16. Would this be causing the issue?
- nitassi think so.
- GreenbergHi, You were correct. I've "re-subnetted" the Routing Table in TMM to exclude the /23 and it's now working. I've never encountered this before and hopefully the Error Codes are more descriptive in newer versions of the Code. This F5 is running 10.2.3 HF1 but we are upgrading to 11.6 in the near future. It should refer to Routes and NOT Self IPs. Thanks a million for your assistance. Chris
- wani
Hi everyone.
I want to resolve same problem.
Can I resolve this problem if tmm interface's self IP is configured with route domain on same management-IP subnet?
ex.
management-IP with default route domain 0
192.168.1.10/24:0
*of course,not specify route domain.
tmm self IP with route domain 20
192.168.1.20/24:20
I don't have test environment.so please show me if it's possible.
