Guest Role User Lost Visibility in ASM/WAF Module – LTM Working Fine
Hi community, I'm troubleshooting a strange issue on our F5 BIG-IP and hoping someone has run into this before. Environment: - Module: ASM (WAF) - User Role: Guest - Partition Access: All Partitions Problem: A user with the Guest role and access to all partitions suddenly lost the ability to view any information in the ASM module. When navigating to Security > Application Security > Policies, the table shows "No records to display" — even though policies exist and are active and viewable from other non-guest accounts. The strange part: LTM is working perfectly fine for this user. They can view virtual servers, pools, nodes, etc. without any issue. The problem is isolated to ASM only. Any pointers would be greatly appreciated. Happy to share outputs if needed. Thanks!
How is choosen the master or primary slot of the cluster?
Hi there, I'd like to know how the cluster master slot is choosen? Is there any rule or algorithm to choose the primary slot on boot? I'm wondering why my Viprion has decided this configuration after booting: On the vCMP host: ----------------------------------------- Sys::Cluster: default ----------------------------------------- Address 192.168.16.32/21 Availability available State enabled Reason Cluster Enabled Primary Slot ID 1 Primary Selection Time 11/27/14 09:03:31 ---------------------------------------------------------------------------------------------------------------------- | Sys::Cluster Members | ID Address Availability State Licensed HA Clusterd Reason ---------------------------------------------------------------------------------------------------------------------- | 1 192.168.16.33 available enabled true active running Run | 2 192.168.16.34 available enabled true active running Run | 3 :: unknown disabled false unknown shutdown Slot powered off or empty, manually disabled | 4 :: unknown disabled false unknown shutdown Slot powered off or empty, manually disabled On the guest: ----------------------------------------- Sys::Cluster: default ----------------------------------------- Address 192.168.16.55/21 Availability available State enabled Reason Cluster Enabled Primary Slot ID 2 Primary Selection Time 11/27/14 09:06:27 ---------------------------------------------------------------------------------- | Sys::Cluster Members | ID Address Availability State Licensed HA Clusterd Reason ---------------------------------------------------------------------------------- | 1 :: available enabled true active running Run | 2 :: available enabled true active running Run | 3 :: unknown enabled false unknown shutdown Slot powered off or empty | 4 :: unknown enabled false unknown shutdown Slot powered off or empty I'd expect to see the guest active on slot 1 too, how is this? It doesn't matter that the slot 1 is the active one for the host and slot 2 for the guest?
Viprion slot core reorganization
Hello Everyone, I started working a while ago managing some F5 hosts and guests and I encounter a strange situation. During an upgrade from v13 to v15 of a 1 core per slot vcmp guest I ran into a memory issue and I was unable to upgrade this guest. I was suggested to reconfigure the cores in this vcmp guest to get more memory. My current setup is the following: Viprion Host with 4 slots with 20 cores each. (We have 2 chassis) 18 Of the cores in every slot are used. So I have 2 vcmp guests with one core per slot. I was suggested to reconfigure the vcmp guests using 2 cores in 2 slots so I can get double the memory, moving from 1x4 to 2x2. I read all the manuals regarding resource allocation but I can't seem to understand why will this perform better (aside from the fact that it will have more memory). Is it better to have more cores assigned per slot rather than using all 4 slots? Will it handle the same amount of traffic the same way?
Unable to login F5 guest using admin credentials
I am having a strange issue where I cannot login to the F5 guest using the admin account . I have changed the admin credentials using the root account but the approach does not work .. Is there any workaround for this to get the admin account working again ?
Reboot Blade / Reboot Chassis options in a vCMP Guest
Hi, Which is the difference between "Reboot Blade" and "Reboot Chassis" when we're working at a Guest level? It's clear that from a Guest I'll never be able of affect the real hardware, so I'l never be able of reboot the blade or chassis. When I use this options on a Guest, what is the real effect? I don't have a vCMP test environment, so I can't test it. I guess that any of those options will reboot the Guest, but with any difference between the blade or chassis option? I guess that maybe, "Reboot Blade" at a Guest level will reboot the VM for that Guest on that blade, and "Reboot Chassis" at a Guest level will, maybe, reboot all the VMs for that Guest on all the slots to which that Guest is spanned. I haven't find any documentation about this specific subject, so any help to clarify this will be welcomed :) Thanks.Viprion without vCMP to Viprion with vCMP
hey everyone! We have a viprion in production right now (vCMP not provisioned) and we are planning on activating it. We will be creating the Guests (2 specifically). My question is, is it possible to load the UCS of the current configuration (without vCMP) to the Guests that we will be creating? if possible, am i going to load the full UCS because from what I know, network configurations are configured in the Host level. How should we approach this scenario? Thank you for responding!cannot create VCMP Guest
Hi everyone. we have created a guest with 2 cores unfortunately, it does not have enough memory to activate LTM,ASM and APM that's why we will add another 2 cores. however, we cannot add the other cores, it says that slot1 is a fragmented resource. we tried deleting the guest and create another with 4 cores but got the same error. how to resolve this? thank you
