BigIP Report Old

Luc:

That's a symptom of broken java scripts. Have you updated the web files? If you have, please do a full "re-install"? If that does not work, please let me know the output of the console in Chrome?

Paul:

Ah, I **_think_** I took that into considerations for that, but will double check tomorrow.

/Patrik

Turns out it was a ID 10 T error ... incorrect permissions on the json folder because I decided I wanted to share it. DERP. Chrome Console pointed me in the right direction :)

I guess I should add some javascript exceptions too. A very large part of the Powershell script consists of error prevention and pre checks but the web front end contains none. :)

/Patrik

Paul, here's the snippet I'd like you to run. Please note the comments I've made in the output section at the bottom, there's a question mark in it for you to answer (if you can).

Configuration
$User = "user"
$Password = "password"
$BigIP = "10.10.10.10"

Allow TLS1.2
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12

Initialize Snapin
if ( (Get-PSSnapin | Where-Object { $_.Name -eq "iControlSnapIn"}) -eq $null ){
    Add-PSSnapIn iControlSnapIn
}

Connect to the BigIP
$Success = Initialize-F5.iControl -HostName $BigIP -Username $User -Password $Password

Get an iControl Handle
$F5 = Get-F5.iControl

$f5.LocalLBVirtualServer.get_profile("/Partition/VIP-name")

            profile_type             profile_context profile_name
            ------------             --------------- ------------
       PROFILE_TYPE_HTTP    PROFILE_CONTEXT_TYPE_ALL /Common/http
 PROFILE_TYPE_CLIENT_SSL PROFILE_CONTEXT_TYPE_CLIENT /Common/sslprofile
        PROFILE_TYPE_TCP    PROFILE_CONTEXT_TYPE_ALL /Common/tcp
PROFILE_TYPE_WEBSECURITY    PROFILE_CONTEXT_TYPE_ALL /Common/websecurity <-- Not sure where this comes from, but it seems like an indication that ASM is enabled?
    PROFILE_TYPE_UNKNOWN    PROFILE_CONTEXT_TYPE_ALL /Partition/ASM_test_policy <-- This policy's real name is "test_policy". "ASM_" as added by the API (or configuration). This caused me a lot of grief when the writing the new version. :)

1. How does the profile names look to you? Is there a prefix?
2. Do you also have a profile type called "PROFILE_TYPE_WEBSECURITY" for every VIP with an ASM policy?

/Patrik

Security Policy Disabled

              $f5.LocalLBVirtualServer.get_profile("/Common/vipname.domain.com")

          profile_type            profile_context profile_name             
          ------------            --------------- ------------             
     PROFILE_TYPE_HTTP   PROFILE_CONTEXT_TYPE_ALL /Common/http             
     PROFILE_TYPE_CLIENT_SSL ...ILE_CONTEXT_TYPE_CLIENT /Common/vipname.domain.com
     PROFILE_TYPE_SERVER_SSL ...ILE_CONTEXT_TYPE_SERVER /Common/vipname.domain.com
     PROFILE_TYPE_TCP   PROFILE_CONTEXT_TYPE_ALL /Common/tcp              

Security Policy Enabled:

$f5.LocalLBVirtualServer.get_profile("/Common/vipname.domain.com")
Exception calling "get_profile" with "1" argument(s): "There is an error in 
XML document (50, 79)."
At line:20 char:1
+ 
$f5.LocalLBVirtualServer.get_profile("/Common/vipname.domain.com")
+ 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : InvalidOperationException

Now that does not look promising at all. When running the actual report and listing $Global:virtualservers, do you get any profiles at all on the virtual servers that has ASM policies assigned to them?

/Patrik

Oh, and could you please try the same procedure on more devices?

/Patrik

Version 4.3.4 changes:

Fixed a mistake when referring to the wrong setting in the column settings (thanks to Paul Dawson for reporting it).

/Patrik

I've tried 2 different LB's and 2 different virtual servers with different virtual server names, one with asm_vsname and one without. I've also tried with different asm policynames such as asm_policyname and just TEMPLATE. Still no joy. I don't see asmpolicy being populated in $Global:virtualservers.

Ok, then it would look like it's not possible with version 11.6. :(

/Patrik