The physical hardware running the F5 BIG-IP Local Traffic Manager loadblancing software is powerfull, but also quite expensive. For a lab environment you do not need to buy a new hardware, but you can get the F5 BIG-IP Local Traffic Manager Virtual Edition and install it as virtual machine.
That is the way I would like to describe here. I had one spare HP ProLiant DL380p Gen8 so RHEL7 virtualization (KVM) was the first choice.
In short I have to deal with bonding (two cables going to the 2 separate switches), trunk containing 3 vlans, bridges and finally with the F5 configuration itself.
Here are some notes about it...
Do some basic RHEL7 customizations + HP SPP installation:
Configure the libvirt including networking and virtual machine running F5 BIG-IP LTM VE:
That's all. I hope it will save some time.
That is the way I would like to describe here. I had one spare HP ProLiant DL380p Gen8 so RHEL7 virtualization (KVM) was the first choice.
In short I have to deal with bonding (two cables going to the 2 separate switches), trunk containing 3 vlans, bridges and finally with the F5 configuration itself.
Here are some notes about it...
RHEL7 Configuration
Start with network:Do some basic RHEL7 customizations + HP SPP installation:
Configure the libvirt including networking and virtual machine running F5 BIG-IP LTM VE:
BIGIP F5 Virtual Edition
Initial configuration:DNS VIP iApp
LDAP VIP iApp
HTTPS VIP iApp
That's all. I hope it will save some time.
The proper place on bigip to place your ssh keys is in /var/ssh//authorized_keys
ReplyDeleteAlso, DSA SSH keys have generally been seen as less secure than RSA.