Debug F5 monitor response from the server

It is quite simple to see if a pool member failed it’s health check by checking the pool status via GUI/CLI and the ltm logs also give you more information on the time lines when the pool went down/up;

cd /var/log
cat ltm | grep

But what if you’ve configured a custom health monitor for a particular pool and now that pool is down and you know it’s the monitor that is failing it. You’ve verified that the F5 is indeed sending the F5 monitor traffic to the nodes. You run some captures on the interface or on an intermediary firewall and see the node is sending replies as well. Now, what if you want to check the contents of the server’s response during that time from the F5 itself?

So here’s the step-by-step instructions you need to follow to effectively get that information;

Continue reading

Transferring licenses after RMA (Cisco)

Our ASR 1001 had a hardware failure with the SPA Interface Processor  and we had to file an RMA for it. Once we got the device to the data center and started loading up the config, we realized it required the ‘advipservices’ and ‘ipsecurity’ licenses which were being used on the old router. After speaking to the licensing support team, they explained to us that we can get a license transfer in this case as this is a replacement device. We gave the serial number of the old router and the new router with the RMA and SR number that was raised with them and she sent us a .lic file that can be loaded on the new ASR router.

If you have been looking for this, here’s another way to get this done; (A phone call to Cisco is definitely a better option with the below information handy)

Continue reading

Licensing your BIG-IP

Licensing is the first thing you would want to do when configuring your BIG-IP for the very first time. Below are two methods with which you can accomplish this.

Automatic method

Use this method if your BIG-IP has internet access.

1. BIG-IP generates a ‘dossier’. The dossier contains the hardware information of your system and the registration key which is pre-populated on the BIG-IP.
2. BIG-IP then sends the dossier to the F5 License Server.
3. If the dossier is valid, the License Server sends a license file back to BIG-IP.
4. BIG-IP stores the bigip.license file in the /config directory.

All this is done by the BIG-IP without any manual intervention.

Manual method

Use this method if your BIG-IP does not have direct internet access or is blocked by a Continue reading