vCMP host and guest modify management IP
Hi, I need help to modify the management IP of vCMP host and guest and migrate them to new subnet. Existing Setup Two vCMP host on different chassis both having management IP from the same subnet vCMP host 1 management IP: 192.168.1.1/24 vCMP host2 management IP 192.168.1.2/24 There are multiple guest on each of these vcMP host which are in HA setup. They are bridged and have management IP configured within the same subnet as vCMP host. vCMP guest1 management: 192.168.1.3/24 vcMP guest 2 management : 192.168.1.4/24 New Setup I want to move them to new subnet but again both host and guest will be sharing the IP from the same subnet . If the new subnet is 172.19.1.0/24 then : vCMP host 1: 172.19.1.1/24 vCMP host 2 172.19.1.2/24, vCMP guest 1 : 172.19.1.3/24 vCMP guest2: 172.19.1.4/24 My question is can we change the host IP first or guest? Will changing the host IP affect the guest? What is best practice and sequence of steps to follow?Device Discovery on BIG-IQ 5.1
The first step in using a BIG-IQ to manage BIG-IP devices BIG-IQ enables administrators to centrally manage BIG-IP infrastructure across the IT landscape. BIG-IQ discovers, tracks, manages, and monitors physical and virtual BIG-IP devices - in the cloud, on premise, or co-located at your preferred datacenter. Let’s look at how to get BIG-IQ 5.1 to gather the information needed to start managing a BIG-IP device. This gathering process is called Device Discovery. To get started, the first thing is to logon to the BIG-IQ Once in, the first thing you do is let the BIG-IQ know about the BIG-IP device that you want to manage. Here, in Device Management>Inventory>BIG-IP Devices, we’ll click Add Device. Here we’ll need the IP address, user name and password of the device you want to manage. If the device you want to manage is part of a BIG-IP Device Service Cluster (DSC), you’ll probably want to manage that part of its configuration by adding it to a DSC group on the BIG-IQ. After selecting a DSC, tell the BIG-IQ how to handle synchronization when you deploy configuration changes so that when you deploy changes to one device, the other DSC members get the same changes. Best practice is to let BIG-IQ do the sync. Next click Add at the bottom of the page to start the discovery process. Once the device recognizes your credentials, it’ll prompt you to choose the services that you want to manage. You always select LTM, even if you only mange other services because the other services depend on LTM. To finish the device discovery task, click Discover. The BIG-IQ gathers the information it needs for each of the services you requested. This first step takes only a few moments while the BIG-IQ discovers your devices. You are done with discovery once the status update reads, Complete import tasks. Now, we need to import the service configurations that the BIG-IQ needs before we can start managing that BIG-IP device. Click the link that says, Complete import tasks. Next, you’ll begin the process of importing the BIG-IP LTM services for this device. Just like the discovery task, you’ll import LTM first. Click Import. This could take a little time depending on how many LTM objects are defined on this BIG-IP device. When the import finishes, BIG-IQ will display the date and time of when the operation was completed. Now, we repeat the process for the second service provisioned on this device. Importing an access device like BIG-IP APM is slightly different. Part of the import task is to identify the Access Group that this device uses to share its configuration. Whether you’re adding to an existing or creating a new access group, when you’re done entering the name of the group, click Add to start the import process. Here again, the time to process depends on how many BIG-IP APM configuration objects are defined on the device. When the BIG-IP APM services import finishes and the time completed displays, you can simply click Close to complete the task. You can now see that the device has been added to BIG-IQ. That’s it! Now you can start managing the BIG-IP LTM and APM objects on this device. For this article, we only imported LTM and APM objects but the process is the same for all BIG-IP services you manage. Thanks to our TechPubs group and watch the video demo here. ps Related: What is BIG-IQ
ping source address
Hi All, I thought that all management traffic like ping, traceroute or telnet from ltm to any host usually takes management IP address. But yesterday for one issue I found out when doing telnet to server it was taking self IP address of ltm. Please suggest which IP address will be used while trying to ping, traceroute or telnet? Thanks.Load Balance Servers in the same subnet as managment interface eth0
I have a requirement to load balance servers in my management network. This subnet is also where the mgmt. IP of my LTM device resides. When I try to create a self IP in this subnet I get an error. I've tried a few work-arounds such as creating a VIP in a separate subnet however the F5 still uses it's management interface to forward traffic to the server pool. Is there any work-around for this other than dropping the mgmt. interface and managing the F5 via a self IP in this subnet?
