I need some ideas to do the following
I have a SYSLOG file on a Linux machine that picks up a lot of messages from differnet devices like this
Code: Select all
[size=5]Aug 30 15:19:10 192.168.167.190 2424: Aug 30 15:18:44: %PM-4-ERR_DISABLE: psecure-violation error detected on Fa0/3, putting Fa0/3 in err-disable state
Aug 30 15:19:13 192.168.167.190 2427: Aug 30 15:18:46: %LINK-3-UPDOWN: Interface FastEthernet0/3, changed state to down
Aug 30 15:21:10 192.168.167.190 2428: Aug 30 15:20:33: %PM-4-ERR_RECOVER: Attempting to recover from psecure-violation err-disable state on Fa0/3
Aug 30 15:21:15 192.168.167.190 2429: Aug 30 15:20:37: %LINK-3-UPDOWN: Interface FastEthernet0/3, changed state to up
Aug 30 15:24:34 192.168.167.190 2431: Aug 30 15:23:40: %PM-4-ERR_DISABLE: psecure-violation error detected on Fa0/3, putting Fa0/3 in err-disable state
Aug 30 15:24:38 192.168.167.190 2434: Aug 30 15:23:42: %LINK-3-UPDOWN: Interface FastEthernet0/3, changed state to down
Aug 30 15:26:30 192.168.167.190 2435: Aug 30 15:25:24: %PM-4-ERR_RECOVER: Attempting to recover from psecure-violation err-disable state on Fa0/3
ug 31 09:22:25 195.232.212.11 1300: destaddr=194.175.52.150, prot=50, spi=0x30D78D20(819432736), srcaddr=82.154.119.53
Aug 31 07:02:48 dcdw0015.wetter.dematic.de 13727: Aug 31 07:02:47.901: %LINK-3-UPDOWN: Interface FastEthernet4/3, changed state to down
Aug 30 15:26:34 192.168.167.190 2436: Aug 30 15:25:28: %LINK-3-UPDOWN: Interface FastEthernet0/3, changed state to up
Aug 30 15:27:18 192.168.167.190 2438: Aug 30 15:26:09: %PM-4-ERR_DISABLE: psecure-violation error detected on Fa0/3, putting Fa0/3 in err-disable state
Aug 30 15:27:21 192.168.167.190 2441: Aug 30 15:26:11: %LINK-3-UPDOWN: Interface FastEthernet0/3, changed state to down
Aug 30 15:29:26 192.168.167.190 2442: Aug 30 15:28:05: %PM-4-ERR_RECOVER: Attempting to recover from psecure-violation err-disable state on Fa0/3
Aug 30 15:29:30 192.168.167.190 2443: Aug 30 15:28:09: %LINK-3-UPDOWN: Interface FastEthernet0/3, changed state to up
Aug 30 15:29:44 192.168.167.190 2445: Aug 30 15:28:22: %PM-4-ERR_DISABLE: psecure-violation error detected on Fa0/3, putting Fa0/3 in err-disable state
Aug 30 15:29:47 192.168.167.190 2448: Aug 30 15:28:24: %LINK-3-UPDOWN: Interface FastEthernet0/3, changed state to down
Aug 30 15:31:56 192.168.167.190 2449: Aug 30 15:30:21: %PM-4-ERR_RECOVER: Attempting to recover from psecure-violation err-disable state on Fa0/3
Aug 30 15:32:00 192.168.167.190 2450: Aug 30 15:30:25: %LINK-3-UPDOWN: Interface FastEthernet0/3, changed state to up
Aug 30 15:32:01 192.168.167.190 2452: Aug 30 15:30:27: %PM-4-ERR_DISABLE: psecure-violation error detected on Fa0/3, putting Fa0/3 in err-disable state
Aug 30 15:32:03 192.168.167.190 2455: Aug 30 15:30:29: %LINK-3-UPDOWN: Interface FastEthernet0/3, changed state to down
Aug 30 15:33:57 192.168.167.190 2456: Aug 30 15:32:12: %PM-4-ERR_RECOVER: Attempting to recover from psecure-violation err-disable state on Fa0/3
Aug 30 15:34:01 192.168.167.190 2457: Aug 30 15:32:16: %LINK-3-UPDOWN: Interface FastEthernet0/3, changed state to up
Aug 30 15:38:46 192.168.167.190 2459: Aug 30 15:36:43: %PM-4-ERR_DISABLE: psecure-violation error detected on Fa0/3, putting Fa0/3 in err-disable state
Aug 30 15:38:49 192.168.167.190 2461: Aug 30 15:36:45: %LINK-3-UPDOWN: Interface FastEthernet0/3, changed state to down
Aug 30 15:40:47 192.168.167.190 2462: Aug 30 15:38:43: %PM-4-ERR_RECOVER: Attempting to recover from psecure-violation err-disable state on Fa0/3
Aug 30 15:40:51 192.168.167.190 2463: Aug 30 15:38:47: %LINK-3-UPDOWN: Interface FastEthernet0/3, changed state to up
Aug 30 15:41:44 192.168.167.190 2464: Aug 30 15:39:41: %LINK-3-UPDOWN: Interface FastEthernet0/3, changed state to down
Aug 30 15:42:00 192.168.167.190 2465: Aug 30 15:39:56: %LINK-3-UPDOWN: Interface FastEthernet0/3, changed state to up
Aug 30 15:42:09 192.168.167.190 2466: Aug 30 15:40:05: %PM-4-ERR_DISABLE: psecure-violation error detected on Fa0/3, putting Fa0/3 in err-disable state
Aug 30 15:42:11 192.168.167.190 2468: Aug 30 15:40:07: %LINK-3-UPDOWN: Interface FastEthernet0/3, changed state to down
Aug 30 15:43:59 192.168.167.190 2469: Aug 30 15:41:55: %PM-4-ERR_RECOVER: Attempting to recover from psecure-violation err-disable state on Fa0/3
Aug 30 15:44:03 192.168.167.190 2470: Aug 30 15:41:59: %LINK-3-UPDOWN: Interface FastEthernet0/3, changed state to up
Aug 30 15:44:11 192.168.167.190 2471: Aug 30 15:42:08: %PM-4-ERR_DISABLE: psecure-violation error detected on Fa0/3, putting Fa0/3 in err-disable state
Aug 30 15:44:14 192.168.167.190 2473: Aug 30 15:42:10: %LINK-3-UPDOWN: Interface FastEthernet0/3, changed state to down
Aug 30 15:45:58 192.168.167.190 2474: Aug 30 15:43:54: %PM-4-ERR_RECOVER: Attempting to recover from psecure-violation err-disable state on Fa0/3
Aug 30 15:46:02 192.168.167.190 2475: Aug 30 15:43:58: %LINK-3-UPDOWN: Interface FastEthernet0/3, changed state to up[/size]
Code: Select all
Aug 30 15:19:10 192.168.167.190 2424: Aug 30 15:18:44: %PM-4-ERR_DISABLE: psecure-violation error detected on Fa0/3, putting Fa0/3 in err-disable state
Aug 30 15:46:02 192.168.167.190 2475: Aug 30 15:43:58: %LINK-3-UPDOWN: Interface FastEthernet0/3, changed state to up
In other words for this example:
- If there is only a message for Switch 192.168.167.190 Port Fa0/3 that the port is "in err-disable state", then bad condition.
- If there is a message "Interface FastEthernet0/3, changed state to up" too, then all is OK (interface has recovered)
Keep in mind:
- There are multiple Switches and Interfaces.
Is it better to have a HM Agent on that Linux or can HM do that from the W2K3 Server where it is running.
Any hints or ideas are very welcome
Regards
Juergen