Skip to content Skip to sidebar Skip to footer
Home / Gms or Syslog Server Name Lookup Failed- Try Again in 60 Secs

Gms or Syslog Server Name Lookup Failed- Try Again in 60 Secs

Post a Comment

Troubleshooting steps for unit down condition issues in GMS

03/26/2020 1,075 People found this article helpful seventy,774 Views

Description

This commodity describes the troubleshooting steps for unit down status bug in GMS.

Resolution

GMS determines the firewall status up/blue or down/red based on the heartbeat syslogs sent past the unit every one infinitesimal. Past default GMS is configured to mark the unit of measurement every bit down after three missed heartbeat syslogs which means that the unit status will be changed to down after 3 minutes of potential firewall or advice failure.

Stride one: Verify that SonicWall unit sends heartbeats messages to GMS.

Change GMS settings to "Transport heartbeats messages only".

Image

Image


If yous see packets generated by SonicWall in the packet capture for UDP 514 it means that the firewall is sending heartbeats.

Note: Heartbeat message is sent every threescore seconds.

Step two: Set logging level to Inform in Firewall.

Image

NOTE: If information technology is fix to anything college than "Inform" heartbeats probably are non sent as logging level is to shallow.

Step 3: Verify that GMS receives syslogs from this unit.

Follow KB: https://www.sonicwall.com/en-us/back up/noesis-base/170502803883459

NOTE: Yous tin too type "Sersial number of the firewall and m=96 in "Filter" Field.
Case: SN=0017c5qwerty AND m=96.  In instance of a distributed setup with multiple Agent servers, login to the specific Amanuensis Server and check for Syslog messages under GMSVP\syslogs folder, for a Virtual appliance the location is /opt/GMSVP/syslogs

Step four: If GMS doesn't receive heartbeats and device sends them this is probably some kind of networking effect or an issue with Windows fifrewall or any other security sotftware running on GMS server blocking UDP 514 traffic.


Step five: If GMS receives heartbeats and yet marks unit as down expect some time and attempt restarting GMS services. If issue persists, contact SonicWall Technical Back up Squad.

Encounter Also:

How to change threshold interval of the missing heartbeats syslogs on the GMS

https://www.sonicwall.com/en-us/support/knowledge-base/170502973678536

Related Manufactures

  • On-Prem NSM-how to add a firewall to a tenant apply Zero Impact
  • On-Prem NSM–how to motility a firewall from a tenant to some other
  • App-IDs showing in SonicWall NSM reports instead of protocol names

Categories

  • Direction and Reporting > GMS

Was This Article Helpful?

YESNO

Article Helpful Class

Article Not Helpful Form

obriencompearid.blogspot.com

Source: https://www.sonicwall.com/support/knowledge-base/troubleshooting-steps-for-unit-down-status-issues-in-gms/170502262660912/

Post a Comment for "Gms or Syslog Server Name Lookup Failed- Try Again in 60 Secs"