Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
LTM virtual servers that are in a non-zero route domain (RD) named using special characters, might be incorrectly marked down by GTM.
GTM marks those LTM virtual servers down.
-- LTM virtual servers with a '.' (dot) or ';' (semi-colon) in the name. -- Configured in a non-zero RD.
This workaround involves changing the GTM config. To make the config work properly, the GTM must be configured with 1 (one) server stanza for each RD on the LTM system that has virtual servers. The following example configuration creates 3 virtual servers, 1 for each RD. Each server then discovers and probes only the virtual servers in the RD. (NOTE: Remove the 'expose-route-domains yes' option from the server stanza. If that remains 'on', then each server lists all of the virtual servers on the LTM, creating duplicates. Furthermore, virtual servers in an RD that does not match the server's RD, are marked down. For the following example: -- on server 10.5.76.239 in route domain 0, all virtual servers in RD1 and RD2 will be red (marked down). -- on server 10.10.10.39 in route domain 1, all virtual servers in RD0 and RD2 will be red. -- on server 10.10.11.39 in route domain 2, all virtual servers in RD0 and RD1 will be red.) For example: 1. If the LTM system is configured with the following self IP addresses (that is, 3 self IP addresses in default RD, RD1, and RD2): net self 10.5.76.239 { address 10.5.76.239/24 allow-service all traffic-group traffic-group-local-only vlan vlan-576 } net self 10.10.11.39%2 { address 10.10.11.39%2/24 allow-service { default } traffic-group traffic-group-local-only vlan vlan-3273 } net self 10.10.10.39%1 { address 10.10.10.39%1/24 allow-service { default } traffic-group traffic-group-local-only vlan vlan-3270 } 2. There are the following virtual servers in each RD: ltm virtual vs.rd0.dottest { destination 10.5.76.39:http ip-protocol tcp mask 255.255.255.255 pool p1 profiles { tcp { } } vlans-disabled } ltm virtual vs.rd1.dottest { destination 10.10.10.39%1:http ip-protocol tcp mask 255.255.255.255 pool p1 profiles { tcp { } } vlans-disabled } ltm virtual vs.rd2.dottest { destination 10.10.11.39%2:http ip-protocol tcp mask 255.255.255.255 pool p2 profiles { tcp { } } vlans-disabled } 3. The GTM must be configured as follows: gtm server /Common/B3600-R18-S39-RD0.lab.ss.example.com { addresses { 10.5.76.239 { device-name B3600-R18-S39.lab.ss.example.com } } datacenter /Common/DC1 monitor /Common/bigip virtual-server-discovery enabled } gtm server /Common/B3600-R18-S39-RD1.lab.ss.example.com { addresses { 10.10.10.39 { device-name B3600-R18-S39.lab.ss.example.com } } datacenter /Common/DC1 monitor /Common/bigip virtual-server-discovery enabled } gtm server /Common/B3600-R18-S39-RD2.lab.ss.example.com { addresses { 10.10.11.39 { device-name B3600-R18-S39.lab.ss.example.com } } datacenter /Common/DC1 monitor /Common/bigip virtual-server-discovery enabled }
LTM virtual servers that are in a non-zero RD named using special characters, are no longer incorrectly marked down by GTM.