• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 455
  • Last Modified:

VPN log question

I do not know if a problem we are having is VPN related or not for sure.  I do not believe so, but just wanted to find out if anyone sees anything that could cause a hiccup or other problem here.  This is the time frame the problem occurred:

2011-09-13 06:42:08      Local7.Debug      172.18.9.2      6184: 004437: Sep 13 06:42:08.161: ISAKMP: set new node -1862200461 to QM_IDLE      
2011-09-13 06:42:08      Local7.Debug      172.18.9.2      6185: 004438: Sep 13 06:42:08.161: ISAKMP:(0:72:HW:2):Sending NOTIFY DPD/R_U_THERE protocol 1
2011-09-13 06:42:08      Local7.Debug      172.18.9.2      6186:       spi 1185528184, message ID = -1862200461
2011-09-13 06:42:08      Local7.Debug      172.18.9.2      6187: 004439: Sep 13 06:42:08.161: ISAKMP:(0:72:HW:2): seq. no 0x55C8AF24
2011-09-13 06:42:08      Local7.Debug      172.18.9.2      6188: 004440: Sep 13 06:42:08.161: ISAKMP:(0:72:HW:2): sending packet to 1.1.1.1 my_port 500 peer_port 500 (I) QM_IDLE      
2011-09-13 06:42:08      Local7.Debug      172.18.9.2      6189: 004441: Sep 13 06:42:08.161: ISAKMP:(0:72:HW:2):purging node -1862200461
2011-09-13 06:42:08      Local7.Debug      172.18.9.2      6190: 004442: Sep 13 06:42:08.161: ISAKMP:(0:72:HW:2):Input = IKE_MESG_FROM_TIMER, IKE_TIMER_IM_ALIVE
2011-09-13 06:42:08      Local7.Debug      172.18.9.2      6191: 004443: Sep 13 06:42:08.165: ISAKMP:(0:72:HW:2):Old State = IKE_P1_COMPLETE  New State = IKE_P1_COMPLETE
2011-09-13 06:42:08      Local7.Debug      172.18.9.2      6192:
2011-09-13 06:42:08      Local7.Debug      172.18.9.2      6193: 004444: Sep 13 06:42:08.181: ISAKMP (0:268435528): received packet from 1.1.1.1 dport 500 sport 500 Global (I) QM_IDLE      
2011-09-13 06:42:08      Local7.Debug      172.18.9.2      6194: 004445: Sep 13 06:42:08.181: ISAKMP: set new node -2026734930 to QM_IDLE      
2011-09-13 06:42:08      Local7.Debug      172.18.9.2      6195: 004446: Sep 13 06:42:08.189: ISAKMP:(0:72:HW:2): processing HASH payload. message ID = -2026734930
2011-09-13 06:42:08      Local7.Debug      172.18.9.2      6196: 004447: Sep 13 06:42:08.189: ISAKMP:(0:72:HW:2): processing NOTIFY DPD/R_U_THERE_ACK protocol 1
2011-09-13 06:42:08      Local7.Debug      172.18.9.2      6197:       spi 0, message ID = -2026734930, sa = 46B1A69C
2011-09-13 06:42:08      Local7.Debug      172.18.9.2      6198: 004448: Sep 13 06:42:08.189: ISAKMP:(0:72:HW:2): DPD/R_U_THERE_ACK received from peer 1.1.1.1, sequence 0x55C8AF24
2011-09-13 06:42:09      Local7.Debug      172.18.9.2      6199: 004449: Sep 13 06:42:08.189: ISAKMP:(0:72:HW:2):deleting node -2026734930 error FALSE reason "Informational (in) state 1"
2011-09-13 06:42:09      Local7.Debug      172.18.9.2      6200: 004450: Sep 13 06:42:08.189: ISAKMP:(0:72:HW:2):Input = IKE_MESG_FROM_PEER, IKE_INFO_NOTIFY
2011-09-13 06:42:09      Local7.Debug      172.18.9.2      6201: 004451: Sep 13 06:42:08.189: ISAKMP:(0:72:HW:2):Old State = IKE_P1_COMPLETE  New State = IKE_P1_COMPLETE
2011-09-13 06:42:09      Local7.Debug      172.18.9.2      6202:
2011-09-13 06:42:59      Local7.Debug      172.18.9.2      6203: 004452: Sep 13 06:42:58.189: ISAKMP:(0:72:HW:2):purging node -2026734930

2011-09-13 07:08:32      Local7.Debug      172.18.9.2      6204: 004453: Sep 13 07:08:31.969: ISAKMP: set new node 1039383918 to QM_IDLE      
2011-09-13 07:08:32      Local7.Debug      172.18.9.2      6205: 004454: Sep 13 07:08:31.969: ISAKMP:(0:72:HW:2):Sending NOTIFY DPD/R_U_THERE protocol 1
2011-09-13 07:08:32      Local7.Debug      172.18.9.2      6206:       spi 1185528184, message ID = 1039383918
2011-09-13 07:08:32      Local7.Debug      172.18.9.2      6207: 004455: Sep 13 07:08:31.969: ISAKMP:(0:72:HW:2): seq. no 0x55C8AF25
2011-09-13 07:08:32      Local7.Debug      172.18.9.2      6208: 004456: Sep 13 07:08:31.969: ISAKMP:(0:72:HW:2): sending packet to 1.1.1.1 my_port 500 peer_port 500 (I) QM_IDLE      
2011-09-13 07:08:32      Local7.Debug      172.18.9.2      6209: 004457: Sep 13 07:08:31.969: ISAKMP:(0:72:HW:2):purging node 1039383918
2011-09-13 07:08:32      Local7.Debug      172.18.9.2      6210: 004458: Sep 13 07:08:31.969: ISAKMP:(0:72:HW:2):Input = IKE_MESG_FROM_TIMER, IKE_TIMER_IM_ALIVE
2011-09-13 07:08:32      Local7.Debug      172.18.9.2      6211: 004459: Sep 13 07:08:31.973: ISAKMP:(0:72:HW:2):Old State = IKE_P1_COMPLETE  New State = IKE_P1_COMPLETE
2011-09-13 07:08:32      Local7.Debug      172.18.9.2      6212:
2011-09-13 07:08:32      Local7.Debug      172.18.9.2      6213: 004460: Sep 13 07:08:32.005: ISAKMP (0:268435528): received packet from 1.1.1.1 dport 500 sport 500 Global (I) QM_IDLE      
2011-09-13 07:08:32      Local7.Debug      172.18.9.2      6214: 004461: Sep 13 07:08:32.005: ISAKMP: set new node -128614880 to QM_IDLE      
2011-09-13 07:08:32      Local7.Debug      172.18.9.2      6215: 004462: Sep 13 07:08:32.009: ISAKMP:(0:72:HW:2): processing HASH payload. message ID = -128614880
2011-09-13 07:08:32      Local7.Debug      172.18.9.2      6216: 004463: Sep 13 07:08:32.009: ISAKMP:(0:72:HW:2): processing NOTIFY DPD/R_U_THERE_ACK protocol 1
2011-09-13 07:08:32      Local7.Debug      172.18.9.2      6217:       spi 0, message ID = -128614880, sa = 46B1A69C
2011-09-13 07:08:32      Local7.Debug      172.18.9.2      6218: 004464: Sep 13 07:08:32.009: ISAKMP:(0:72:HW:2): DPD/R_U_THERE_ACK received from peer 1.1.1.1, sequence 0x55C8AF25
2011-09-13 07:08:33      Local7.Debug      172.18.9.2      6219: 004465: Sep 13 07:08:32.009: ISAKMP:(0:72:HW:2):deleting node -128614880 error FALSE reason "Informational (in) state 1"
2011-09-13 07:08:33      Local7.Debug      172.18.9.2      6220: 004466: Sep 13 07:08:32.009: ISAKMP:(0:72:HW:2):Input = IKE_MESG_FROM_PEER, IKE_INFO_NOTIFY
2011-09-13 07:08:33      Local7.Debug      172.18.9.2      6221: 004467: Sep 13 07:08:32.009: ISAKMP:(0:72:HW:2):Old State = IKE_P1_COMPLETE  New State = IKE_P1_COMPLETE
2011-09-13 07:08:33      Local7.Debug      172.18.9.2      6222:
2011-09-13 07:09:23      Local7.Debug      172.18.9.2      6223: 004468: Sep 13 07:09:22.009: ISAKMP:(0:72:HW:2):purging node -128614880
0
B1izzard
Asked:
B1izzard
  • 2
1 Solution
 
fgasimzadeCommented:
I can nothing wrong in this log
0
 
B1izzardAuthor Commented:
My only concern was this where it says 'purging node'.  We had an issue which may or may not have been related at about this time which is why I ask.  So I will presume by your response that this is normal:

2011-09-13 06:42:59      Local7.Debug      172.18.9.2      6203: 004452: Sep 13 06:42:58.189: ISAKMP:(0:72:HW:2):purging node -2026734930

2011-09-13 07:08:32      Local7.Debug      172.18.9.2      6204: 004453: Sep 13 07:08:31.969: ISAKMP: set new node 1039383918 to QM_IDLE      
0
 
B1izzardAuthor Commented:
Thanks.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Improved Protection from Phishing Attacks

WatchGuard DNSWatch reduces malware infections by detecting and blocking malicious DNS requests, improving your ability to protect employees from phishing attacks. Learn more about our newest service included in Total Security Suite today!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now