About bino150

Hulk you got it. They had the wrong remote IP on the cisco. Go figure. Thanks again! ... View more

As usual thanks for the great help Hulk. I ran through these procedures and cleared the keys. The connection is active and up. The remote site is still getting the error: 'IKE phase-2 negotiation failed when processing proxy ID. cannot find matching phase-2 tunnel for received proxy ID. received local id: 10.1.2.1/32 type IPv4_address protocol 0 port 0, received remote id: 10.x.x.0/22 type IPv4_subnet protocol 0 port 0. admin@PA-500(active)> show vpn flow tunnel-id 21 tunnel  xxxram:xxxram.9         id:                     21         type:                   IPSec         gateway id:             4         local ip:               69.x.x.x         peer ip:                216.x.x.x         inner interface:        tunnel.4         outer interface:        ethernet1/1         state:                  active         session:                67         tunnel mtu:             1428         lifetime remain:        3405 sec         latest rekey:           195 seconds ago         monitor:                off         monitor packets seen:   0         monitor packets reply:  0         en/decap context:       226         local spi:              BFD74292         remote spi:             B750B977         key type:               auto key         protocol:               ESP         auth algorithm:         SHA1         enc  algorithm:         AES128         proxy-id local ip:      10.1.2.0/32         proxy-id remote ip:     10.x.x.x/24         proxy-id protocol:      0         proxy-id local port:    0         proxy-id remote port:   0         anti replay check:      yes         copy tos:               no         authentication errors:  0         decryption errors:      0         inner packet warnings:  0         replay packets:         0         packets received           when lifetime expired:0           when lifesize expired:0         sending sequence:       0         receive sequence:       0         encap packets:          12005877         decap packets:          14018067         encap bytes:            2596966960         decap bytes:            1891762952         key acquire requests:   236118         owner state:            0         owner cpuid:            s1dp0         ownership:              1 ... View more

Thanks Hulk. ... View more

Thank you for the info guys. Here is the system disc space. it doesn't look too full Filesystem            Size  Used Avail Use% Mounted on /dev/sda3             3.8G  1.7G  1.9G  47% / /dev/sda5             7.6G  2.9G  4.4G  40% /opt/pancfg /dev/sda6             3.8G  1.2G  2.5G  33% /opt/panrepo tmpfs                 963M   67M  896M   7% /dev/shm /dev/sda8             125G   13G  106G  11% /opt/panlogs Here is the logging status> -------------------------------------------------------------------------------- ---------------------------------------------       Type      Last Log Created        Last Log Fwded       Last Seq Num Fwded Last Seq Num Acked         Total Logs Fwded -------------------------------------------------------------------------------- --------------------------------------------- > CMS 0         Not Sending to CMS 0 > CMS 1         Not Sending to CMS 1 >Log Collector         Not Sending to Log Collector Debug log-receiver statistics admin@PA-500(active)> debug log-receiver statistics Server error : An error occured. See dagger.log for information. admin@PA-500(active)> I've tried restart log-receiver several and restart management-server times a few days ago. it did get logging going for system etc but no effect for the traffic log. > debug software trace log-receiver > debug software trace management-server > debug software restart log-receiver if no change still; > debug software restart management-server This all relates back to this post which HULK helped me with.Logging stopped in Pan OS GUI I did do show ntp as well NTP state:     NTP synched to 0.north-america.pool.ntp.org     NTP server 0.north-america.pool.ntp.org connected: True     NTP server 1.north-america.pool.ntp.org connected: True I think a reboot is still needed to resolve this problem. ... View more

Thank you Steven. (and Hulk). You have been very helpful. We intend to reboot the devices. As you mentioned the sync did not resolve the issue. Very odd indeed. All other logs system logs etc are working fine except traffic and some of the threat logs. ... View more

Thank you. ... View more

I think I spoke too soon. We are getting system log info etc. I tried checking just now and I notice the traffic log is not updating or displaying in the monitor. NTP seems to be fine. I ran debug log-receiver statistics and the error "An error occured. See dagger.log for information." still appears. I ran tail output after running debug log-receiver statistics and I see the following KeyError: 'sw.logrcvr.runtime.opcmd' admin@PA-500(active)> tail mp-log dagger.log 2014-07-08 20:44:23.567 -0700 OPCMD: handler "logrcvr_handler.debug_stats" Traceback (most recent call last):   File "/usr/share/dagger/logrcvr.py", line 60, in debug_stats     resp_node = self.sdb.modify(name=op_node_name, object=op_node, timeout=60) KeyError: 'sw.logrcvr.runtime.opcmd' 2014-07-08 20:45:11.212 -0700 OPCMD: handler "logrcvr_handler.debug_stats" Traceback (most recent call last):   File "/usr/share/dagger/logrcvr.py", line 60, in debug_stats     resp_node = self.sdb.modify(name=op_node_name, object=op_node, timeout=60) KeyError: 'sw.logrcvr.runtime.opcmd' Is it possible I need to let the devices re-sync. Is there a command to manually force the devices to resync? ... View more

Hulk thanks so much for the help. The NTP server re-synched and now its showing true so it looks good now. ... View more

Interesting I am showing connected false for NTP admin@PA-500(active)> show ntp NTP state:     NTP synched to LOCAL     NTP server 0.north-america.pool.ntp.org connected: False     NTP server 1.north-america.pool.ntp.org connected: False ... View more

Low and behold the log information is coming through now. I'm still getting the Server error: An error occurred. See dagger.log for information running debug log-receiver statistics from CLI though. ... View more

Think I need to contact support for this. Thanks for the help ... View more

Just logged in again and the error is still coming up. its been a few minutes now, debug log-receiver statisitcs Server error: An error occurred. See dagger.log for information. ... View more

Hulk we still seem to have an issue. I ran both debug software restart log-receiver which did not resolve the issue. Same with debu g software restar t management-server . if I run debug log-receiver statistics I get the following error see dagger log. Do I need to do this plugged in to the cli port directly. I'm doign this via telnet from my workstation on the LAN. ... View more