Forum Discussion

Jason_40733's avatar
Jason_40733
Icon for Cirrocumulus rankCirrocumulus
Sep 10, 2013

GTM Pair, one GTM incorrectly shows Virtual Server status as "unknown"

Implemenation Overview: Pair of GTMs. Both running 10.2.1. Call them GTMRIGHT and GTMWRONG. LTM HA pair ( active/passive running 10.2.0 ) containing virtual servers. These are the nodes being ref...
availability
Hem_66900's avatar
Hem_66900
Icon for Cirrus rankCirrus
Sep 11, 2013

1.If you set up iquery properly it should not report different results in GTMs. Verify iqdump < self-ip > from each other GTM to LTM;GTM-GTM as well. Fix it if iquery not set up properly.

 

Compare GTM synchronization setting as well.

 

2.Check iquery options in GTM under server objects where you define LTMs for iquery. usually it comes with the following options.Comapre them on Good & Bad GTMs. service check path SNMP

 

  1. Make sure server object settings are same.

If all 3 options looking good, You can try remove BAD GTM from sync group & add it back.

 

  • Jason_40733's avatar
    Jason_40733
    Icon for Cirrocumulus rankCirrocumulus
    Sep 13, 2013
    The iqdump helped find the issue. All connectivity between systems was excellent. No issues here. However.... our GTMWRONG is running 10.2.1 build 297.. it's big3d shows the following version information when running iqdump. 10.2.1 big3d Version 10.2.0.297.0 linux I am guessing the 10.2.0.297.0 is probably a type-o and should say 10.2.1.297.0. The bigger news is.... GTMRIGHT is showing a different version of Big3d running despite running the same version of software. 10.2.1 big3d Version 10.2.0.1755.0 linux It appears to be running an older version of the big3d than the version of TMM. I verified the binaries available on both systems for big3d. GTMWRONG has consistent file sizes of 3875991 for the binary. GTMRIGHT has one file size in /usr/sbin/big3d of 3875991 and a file size of 3875799 for /shared/bin/big3d. I am guessing the /shared/bin/big3d is the one that might be from the older code version on GTMRIGHT. Hopefully this is the cause of the incorrect monitoring to the other GTM. We are continuing to investigate.