Forum Discussion
How do I configure an F5 LTM VE Lab on my Laptop and drive traffic to it to generate logs?
I have successfully installed the F5 LTM VE Lab on VMWare Fusion 6, but I'm unclear how to configure it so that I can drive traffic through it from my browser (I am open to driving traffic in other ways, such as using blitz.io) with a macro.
I'm unclear on the details of setting up the underlying network to do so.
I have the configuration worksheet, but I'm not clear how to define the IPs and VLAN groups to achieve this objective:
http://support.f5.com/content/kb/en-us/products/big-ip_ltm/manuals/product/configuration_worksheet/_jcr_content/pdfAttach/download/file.res/Configuration_Worksheet_-_BIG-IP_Local_Traffic_Manager.pdf
- TTF888_160708Nimbostratus
The three MAC addresses appear to be matching!
Here are the Mac LTM Interfaces:
- UNINITIALIZED1.1 0:c:29:8c:a7:8b
- UP1.2 0:c:29:8c:a7:95
- UP1.3 0:c:29:8c:a7:9f
Here are the VMware Interfaces:
- MAC1: 00:0C:29:8C:A7:81
- MAC2: 00:0C:29:8C:A7:8B
- MAC3: 00:0C:29:8C:A7:95
- MAC4: 00:0C:29:8C:A7:9F
What error message do you get when you try to remove the self IP?
You only really need two interfaces as you can manage the LTM via the external IP as well (provided that it's not facing the internet).
To allow this you can login to the shell on the LTM and issue this command (do NOT do this to any device connected directly to the internet without issuing any type of packet filter):
modify net self 192.168.239.2 allow-service add { tcp:443 }
Then you can manage the ltm through https://192.168.239.2 (if the vmware+client network settings are correct).
Now, the next step is to do make sure that your mac and LTM share the same network (see my previous post).
Mac config VMNET1 192.168.239.1 Gives the MAC an interface and ip on the external VLAN VMNET8 192.168.41.1 Gives the MAC an interface and ip on the internal VLAN LTM Config: 192.168.239.2 Configure the external VLAN interface in vmware to belong to VMNET1 192.168.41.2 Configure the internal VLAN interface in vmware to belong to VMNET8
When your Macintosh are on the same network as the ltm you should be able to ping the LTM IPs.
/Patrik
This is because you have configured the self IP as a mirroring interface.
To remove it go to Device Management -> Devices -> Click on your device -> Device Connectivity -> Mirroring. Then set the mirroring interface to none on both (unless you'reconfiguring a redundant setup?).
/Patrik
Could you please post the result of this commands:
tmsh show net self field-fmt tmsh show net vlan field-fmt
And on your Macintosh:
ifconfig -a
/Patrik
- TTF888_160708Nimbostratus
lo0: flags=8049 mtu 16384 options=3 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff000000 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 nd6 options=1 gif0: flags=8010 mtu 1280 stf0: flags=0<> mtu 1280 en0: flags=8863 mtu 1500 options=10b ether 40:6c:8f:23:6c:6d media: autoselect (none) status: inactive en1: flags=8863 mtu 1500 ether 70:56:81:8c:41:7f inet 192.168.1.86 netmask 0xffffff00 broadcast 192.168.1.255 media: autoselect status: active fw0: flags=8863 mtu 4078 lladdr 40:6c:8f:ff:fe:7a:d7:3c nd6 options=1 media: autoselect status: inactive en5: flags=8822 mtu 1500 options=60 ether d2:00:17:ad:73:c0 media: autoselect status: inactive p2p0: flags=8843 mtu 2304 ether 02:56:81:8c:41:7f media: autoselect status: inactive vmnet1: flags=8863 mtu 1500 ether 00:50:56:c0:00:01 inet 192.168.77.1 netmask 0xffffff00 broadcast 192.168.77.255 vmnet8: flags=8863 mtu 1500 ether 00:50:56:c0:00:08 inet 192.168.96.1 netmask 0xffffff00 broadcast 192.168.96.255
- TTF888_160708Nimbostratushm, strange it was formatted, i need to try again.
- TTF888_160708Nimbostratus
lo0: flags=8049 mtu 16384 options=3 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff000000 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 nd6 options=1 gif0: flags=8010 mtu 1280 stf0: flags=0<> mtu 1280 en0: flags=8863 mtu 1500 options=10b ether 40:6c:8f:23:6c:6d media: autoselect (none) status: inactive en1: flags=8863 mtu 1500 ether 70:56:81:8c:41:7f inet 192.168.1.86 netmask 0xffffff00 broadcast 192.168.1.255 media: autoselect status: active fw0: flags=8863 mtu 4078 lladdr 40:6c:8f:ff:fe:7a:d7:3c nd6 options=1 media: autoselect status: inactive en5: flags=8822 mtu 1500 options=60 ether d2:00:17:ad:73:c0 media: autoselect status: inactive p2p0: flags=8843 mtu 2304 ether 02:56:81:8c:41:7f media: autoselect status: inactive vmnet1: flags=8863 mtu 1500 ether 00:50:56:c0:00:01 inet 192.168.77.1 netmask 0xffffff00 broadcast 192.168.77.255 vmnet8: flags=8863 mtu 1500 ether 00:50:56:c0:00:08 inet 192.168.96.1 netmask 0xffffff00 broadcast 192.168.96.255
Mark the text and use the preformatted code button (or control k) to get the format with line breaks. You can see a preview below of the post.
/Patrik
- TTF888_160708Nimbostratus
lo0: flags=8049 mtu 16384 options=3 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff000000 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 nd6 options=1 gif0: flags=8010 mtu 1280 stf0: flags=0<> mtu 1280 en0: flags=8863 mtu 1500 options=10b ether 40:6c:8f:23:6c:6d media: autoselect (none) status: inactive en1: flags=8863 mtu 1500 ether 70:56:81:8c:41:7f inet 192.168.1.86 netmask 0xffffff00 broadcast 192.168.1.255 media: autoselect status: active fw0: flags=8863 mtu 4078 lladdr 40:6c:8f:ff:fe:7a:d7:3c nd6 options=1 media: autoselect status: inactive en5: flags=8822 mtu 1500 options=60 ether d2:00:17:ad:73:c0 media: autoselect status: inactive p2p0: flags=8843 mtu 2304 ether 02:56:81:8c:41:7f media: autoselect status: inactive vmnet1: flags=8863 mtu 1500 ether 00:50:56:c0:00:01 inet 192.168.77.1 netmask 0xffffff00 broadcast 192.168.77.255 vmnet8: flags=8863 mtu 1500 ether 00:50:56:c0:00:08 inet 192.168.96.1 netmask 0xffffff00 broadcast 192.168.96.255
- TTF888_160708NimbostratusArghhh...it works in preview: http://cl.ly/image/1u2M0P453R3W
- You need to write something above the code I think. Then a line break or two and then paste the code. :) /Patrik
It's really the VMnet interfaces that's interesting. :)
/Patrik
Please send a screen shot of the self IP config again?
/Patrik
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