Forum Discussion
NimbostratusGTM wrong discovery of virtual server
HI everyone ,
not sure if this is a bug in GTM (10.2.4),
we have 2 LTMs per DC (assuming DC A and DC B) , i was configuring a new service and accidentally i created the VIP example (1.1.1.1) on DC B LTM instead on DC A LTM, as 1.1.1.x is the VIP range for DC A, by the time i realised my mistake and deleted the wrongly created LTM config on DC B and corrected it by creating 1.1.1.1 on DC A LTM ,
now strangely GTM has already discovered that VIP and still thinks 1.1.1.1 belongs to DC B as this still shows under GTM - Servers - LTM B - virtual servers (tab) , although i have correctly created it on DC A LTM by creating it there ,
how do i make GTM know that 1.1.1.1 VIP belongs to DC A than DC B ,
virtual server discovery setting is set to enabled (no delete )
any advice/help much appreciated
thanks in advance solmon
2 Replies
VernonWellsEmployee
At least part of the issue is the "no delete" for Virtual Server discovery. By using that, you've instructed GTM not to delete Virtual Servers that are removed on the target system. (See SOL13994: Configuring virtual server and link auto-discovery (11.x), particularly the notes in blue). You will need to manually delete that Virtual Server entry on DC B.
solmonHI Vernon
thanks for the reply , as i mentioned the VS was deleted and created on the correct LTM DC A but still GTM thinks the VS object belongs to LTM in DC B ,
any other thoughts anyone ?
