Smiertx Site

BIG-IP has feature persistence profile, it uses for keep existing session on a member. For example : Pool have 2 members (A and B), for example request will redirect to A, but sometimes it can redirected to B for a while, it cause client losing connection to A. How to create persistence profile based on source address. - Go to Local Traffic -> Virtual Servers -> Profiles -> Persistence - Click create to make a new persistence profile - Change Persistence Type to "Source Address Affinity" - Make sure that Parent Profile "source_addr" - Don't forget to give a name to your new profile Assigning Persistence Profile to Virtual Servers. - Go to one of your virtual servers, and then go to tab "Resources" - Assign Default Persistence Profile with your new persistence profile.

How to perform SCCP reboot based on https://support.f5.com/kb/en-us/solutions/public/6000/800/sol6836.html This applied on : BIG-IP LTM 9.4.4, 9.4.3, 9.4.2, 9.4.1, 9.4, 9.3.1, 9.3, 9.2.5, 9.2.4 BIG-IP ASM 9.4.4, 9.4.3, 9.4.2, 9.4.1, 9.4, 9.3.1, 9.3, 9.2.5, 9.2.4 BIG-IP GTM 9.4.4, 9.4.3, 9.4.2, 9.4.1, 9.4, 9.3.1, 9.3, 9.2.5, 9.2.4 Link Controller 9.x 9.4.4, 9.4.3, 9.4.2, 9.4.1, 9.4, 9.3.1, 9.3, 9.2.5, 9.2.4 WebAccelerator 9.4.4, 9.4.3, 9.4.2, 9.4.1, 9.4 The SCCP is a separate sub-system that controls F5 Networks' switch hardware. It may become necessary to reboot the SCCP, if, for example, the installation of a hotfix updates the SCCP firmware package. Rebooting the SCCP F5 Networks recommends performing a clean shutdown of the host system, and reboot the SCCP and host system, by performing the following procedure: 1. Log in to the command line of the BIG-IP system. 2. Reboot the host and SCCP, by typing the following command: # /usr/bin/full_box_reboot Note: The filesys...

How to performing SCCP reboot based on https://support.f5.com/kb/en-us/solutions/public/5000/400/sol5471.html This applied to : BIG-IP LTM 9.2.3, 9.2.2, 9.2, 9.1.2, 9.1.1, 9.1, 9.0.5, 9.0.4, 9.0.3, 9.0.2, 9.0.1, 9.0 BIG-IP ASM 9.2.3, 9.2.2, 9.2 BIG-IP GTM 9.2.3, 9.2.2 Link Controller 9.x 9.2.3, 9.2.2 F5 Networks recommends you perform a clean shutdown of the host system, and reboot the SCCP and host system, by performing the following steps: 1.Log in to the command line of the BIG-IP system. 2.Create the /.sccp_hard_reboot file, by typing the following command: # touch /.sccp_hard_reboot 3.Reboot the host and SCCP, by typing the following command: # reboot Note: The /.sccp_hard_reboot file will no longer exist after the system reboots.

If you found your BIG-IP system failed to load license or it was on un-configured system accidentally. I found that problem too, and that my opinion about that. Main root causes : 1. SOL7036: Linux uptime counter wrap after 497 days back set to zero. This is not a critical issue. This issue was discovered in 1998, and is due to the 32bit counter overflow. Currently, there is no Linux kernel patch available to resolve this issue. 2. SOL7071: The SCCP kernel driver timer wrap causes an I2C read failure. This is the result of a known issue. A timer wrap within the SCCP kernel occurs after 497 days, and resets the timer to O (zero). The timer wrap causes I2C (Inter-Integrated Circuit bus) driver read/write failures because the I2C is unable to correctly handle the kernel timer wrapping. The SMBus then enters a lockup condition, which causes all subsequent I2C read/write communications to fail until the SCCP is rebooted. As a result, the SCCP cannot gather data from the host system on chass...

If you found problem on your BIG-IP 9.2.3 or below version system about chassis fan reporting failure you should not worried too much. We can check with performing this command # b platform PLATFORM INFORMATION -- ------------------- +-> CPU 1 temp 50degC fan speed 10887rpm | | CHASSIS TEMPERATURE | (1) 46degC (2) 42degC (101) -1degC (102) -1degC | | CHASSIS FAN | (101) DOWN! (102) DOWN! (103) DOWN! (104) DOWN! (105) DOWN! | (106) DOWN! | | POWER SUPPLY | (101) active -------------- We also can check at # more /var/log/ltm | grep Chassis -------------- system_check: 010d0005:3: Chassis fan 101: status (0) is bad. -------------- Actually the fan wasn't down, it just a minor bug of BIG-IP, it's code: CR63196. Solutions below : SOL7071: The SCCP kernel driver timer wrap causes an I2C read failure. This is the result of a known issue. A timer wrap within the SCCP kernel occurs after 497 days, and resets the timer...

sometimes we want to load balance with string that contain at URI. for example we want to load balance with this specification : We have 10 server with specific purpose, but we want to join this service at one virtual server. 192.168.0.1 & 192.168.0.2 for data purpose 192.168.0.3 & 192.168.0.4 for download purpose 192.168.0.5 & 192.168.0.6 for mail client purpose 192.168.0.7 & 192.168.0.8 for open source purpose 192.168.0.9 & 192.168.0.10 for default So, create 5 pools with member and port specified. After that create iRule, name this iRule as "lbtry" : when HTTP_REQUEST { switch [HTTP::uri] { /data { pool data_pool } /download { pool dload_pool } /mail { pool mail_pool } /opensource { pool os_pool } default { pool def_pool } } Finally, create virtual server with include iRule "lbtry" without define Default Pool. Now we can load balance based on URI. Thanks to Mas Anang n Mas Taufik for gimme a chance for developing this.

Tagged Interfaces: - use if you want to connect more than 1 Vlan for this interface - A tagged interface is an interface that you assign to a VLAN in a way that causes the system to add a VLAN tag into the header of any frame passing through that interface. - Tagged interfaces are used when you want to assign a single interface to multiple VLANs. Untagged Interfaces: - use if you want to connect only 1 Vlan for this interface

Today, BIG-IP 1500 comes to me need to configure by me. :) When I see at this machine, look small with limited active modules but it's adequate to fulfill my network architecture. Here the machine : Only 1 management port and 4 gigabit ethernet ports. It will used for load balancing 5 redundant servers. First, after you received this machine, check ip address management that show on LCD panel. It usually 192.168.1.245. Just connect a straight utp cable to management port and set your IP on same segment network 192.168.1.0/24. access https://192.168.1.245 with your browser and it will show prompt username and password. Default is "admin" "admin". You will see activate button on web interface and you should click it. Just click next, when it shows "Registration Key". Next window: Step 1 : it will show "dossier validation number" and you need to download or copy it. Step 2 : Access https://activate.f5.com/license/dossier.jsp and copy or upload d...