Forum Discussion

Shrikantj's avatar
Shrikantj
Icon for Nimbostratus rankNimbostratus
Apr 20, 2018

Virtual server is showing Down on GTM1 and UP on GTM2

Hi Team,

 

We have 2 GTM and they are in sync. Recently we have configured one VS-using product generic-host. This was UP on both GTM after config. However, we had one recent change for adding certificate for other LTM on both GTM and after that, this VS is down on GTM1 but UP on GTM2. If we disable the config on GTM1, its replicates the same on GTM2 and vice a versa. but this VS is only UP on GTM2 and down on GTM1. Can you please check below logs on GTM1 and help. We tried to use: bigstart restart big3d on GTM1 but same issue.

 

LOGS on GTM1:

 

10.156.50.11 is VS 10.156.40.119- is Self IP of GTM1

 

SNMP_TRAP: Pool /Common/Pool_mypool member GNOC1_SEP_GW1_VS (ip:port=10.156.50.11:7070) state chage green --> red ( Monitor /Common/Tcp_7070 from /Common/GTM1 : no reply from big3d /Common/GTM1(10.156.40.119): timed out)

 

  • LOGS on GTM1:

    Monitor instance /Common/Tcp_7070 10.156.50.11:7070 UP --> DOWN from /Common/GTM1 (no reply from big3d /Common/GTM1(10.156.40.119): timed out) SNMP_TRAP: VS GNOC1_GW1_VS (ip:port=10.156.50.11:7070) (Server /Common/GTM1_SEP_GW1) state change green --> red ( Monitor /Common/Tcp_7070 from /Common/GTM1 : no reply from big3d /Common/GTM1(10.156.40.119): timed out) SNMP_TRAP: Server /Common/GNOC1_SEP_GW1 (ip=10.156.50.11) state change green --> red (No enabled VS available) SNMP_TRAP: Pool /Common/Pool_mypool member GNOC1_SEP_GW1_VS (ip:port=10.156.50.11:7070) state chage green --> red ( Monitor /Common/Tcp_7070 from /Common/GTM1 : no reply from big3d /Common/GTM1(10.156.40.119): timed out)

     

    Server list:

     

    gtm server /Common/GNOC1 addresses { 10.156.50.11 { device-name /Common/GNOC1_SEP_GW1 } } datacenter /Common/GNOC1_WAN monitor /Common/Tcp_7070 product generic-host virtual-servers { GNOC1_SEP_GW1_VS { destination 10.156.50.11:7070 } }

     

    POOL:

     

    gtm pool a /Common/Pool_mypool { members { /Common/GNOC1_SEP_GW1:GNOC1_SEP_GW1_VS { member-order 0 } } monitor /Common/Tcp_7070

     

    WIDE IP: gtm wideip a /Common/SEP.xx { pools { /Common/Pool_mypool { order 0 } } }

     

  • we had one recent change for adding certificate for other LTM on both GTM

    Do you mean you created a LTM server object to the GTM config and ran bigip_add? Is that LTM in the same datacenter as the generic host which is offline? GTM assigns monitors to other bigips to run so it could be that the LTM is performing the monitoring and cannot reach the generic host.

     

    What versions are the GTMs and LTM? You may need to run big3d_install to make them all compatible.

     

    Troubleshooting BIG-IP GTM monitors

     

    Overview of the BIG-IP DNS big3d_install, bigip_add, and gtm_add utilities (11.x - 13.x)

     

    Overview of big3d version management

     

  • This issue was related mcpd process, the sysytem was not working as expected. MCPD rebuild and reboot resolved the issue.