BenT
Jun 04, 2021Altocumulus
That got it. Thanks!
Have you looked at port-lists and/or policies? For port-lists, the VIPs aren't contained in the virtual, but are in a traffic-matching-criteria object instead. I don't know how difficult it would be to add the logic to show the VIPs for those in bigipreport or any associated policies.
Here is an example config for the port-lists.
net port-list /Common/web_443-8443-8080_ports {
description web_443-8443-8080_ports
ports {
443 { }
8080 { }
8443 { }
}
}ltm pool /Common/pool_vip_portlist_example {
load-balancing-mode least-connections-node
members {
/Common/172.1.2.5:0 {
address 172.1.2.5
}
/Common/172.1.2.6:0 {
address 172.1.2.6
}
}
monitor /Common/https_basic_443
}
ltm traffic-matching-criteria /Common/vip_portlist_example_VS_TMC_OBJ {
destination-address-inline 1.2.3.4
destination-port-list /Common/web_443-8443-8080_ports
protocol tcp
source-address-inline 0.0.0.0
}
ltm virtual /Common/vip_portlist_example {
ip-protocol tcp
pool /Common/pool_vip_portlist_example
profiles {
/Common/fastL4 { }
}
serverssl-use-sni disabled
source-address-translation {
type automap
}
traffic-matching-criteria /Common/vip_portlist_example_VS_TMC_OBJ
translate-address enabled
translate-port enabled
vlans {
/Common/proxy-vlan
}
vlans-enabled
}