Replication SEPMs

I need a solution

Hello everyone,

I have two remote site-A and site-B with 1MB link. I would to set up a replication partner in Site-A which will replicate the data from SEPM 14 in site-B. the sem5.db in site-B is around 20GB.

I would like to know that how much time would it take approximately for the replication to complete as I install SEPM in site-A as a replication partner???

And what do I need to make sure that the initial replication cycle should be completed sucuessfuly as the SEPM is installed in site-A

Thanks

0

Related:

  • No Related Posts

Proxy rebooted unexpectedly

I need a solution

Hi Team,

Our proxy rebooted unxpectedly twice on 19th and 20th April.  Proxy has produced minicontect file with below details. Did not find anything more from proxy logs. May i conform it is related to known bug ?

Running Version: SGOS 6.6.5.9, Release id: 201969
Produced on Friday April 20 2018 14:32:40
Size on disk is 272724992 bytes.

Minicontext produced on: 2018-04-20 14:32:40+00:00UTC
Minicontext version: 1.5
ProxySG Appliance: Version 6.6.5.9.201969
Architecture: x86_64
Kernel: Multiprocessor
System image flags: Customer, Optimized, Non-GDB, 64-bit

Hardware exception code: 0x0
Software exception code: 0x11
Page fault linear address: 0x0
Process group: “”
Process: “” in “kernel.exe” at .text+0x1249cca
Register context:
      RIP              RSP              RBP              RDI
0000000001249CCA 0000000000000011 0000000001D08DA0 0000000000000011 
      RSI              RDX              RCX              RBX
000000000000041D 0000000000000000 0000000000000007 0000000001ACEA00 
      RAX              R8               R9               R10
0000000001ACE980 0000000000000008 0000000000000007 0000000000000000 
      R11              R12              R13              R14
0000000001C7B4E0 0000000000000011 00000000013A07C7 0000000001AD6760 
      R15             RFLAGS       CS   SS
000059FB455928B9 0000000001ACEA00 1D08DA0 FFFFFFFF 
Call Stack:
System data:
0000  23 20 57 61 74 63 68 64 6F 67 20 68 61 73 20 6E   # Watchdog has n
0010  6F 74 20 62 65 65 6E 20 72 65 73 65 74 20 6F 6E   ot been reset on
0020  20 70 72 6F 63 65 73 73 6F 72 20 30 2E 0A 23 20    processor 0..# 
0030  41 63 74 75 61 6C 20 4C 65 6E 67 74 68 20 6F 66   Actual Length of
0040  20 77 64 20 69 6E 74 65 72 76 61 6C 20 33 30 20    wd interval 30 
0050  73 65 63 6F 6E 64 73 2E 0A 23 20 45 78 70 65 63   seconds..# Expec
0060  74 65 64 20 4C 65 6E 67 74 68 20 6F 66 20 77 64   ted Length of wd
0070  20 69 6E 74 65 72 76 61 6C 20 33 30 20 73 65 63    interval 30 sec
0080  6F 6E 64 73 0A 23 20 50 72 6F 63 65 73 73 6F 72   onds.# Processor
0090  20 30 20 73 61 77 20 33 30 30 30 20 74 69 63 6B    0 saw 3000 tick
00A0  73 20 64 75 72 69 6E 67 20 77 64 20 69 6E 74 65   s during wd inte
00B0  72 76 61 6C 20 65 78 70 65 63 74 65 64 20 33 30   rval expected 30
00C0  30 30 2E 0A                                       00..
Core Header:

Running Version: SGOS 6.6.5.9, Release id: 201969
Produced on Thursday April 19 2018 11:02:00
Size on disk is 272205312 bytes.

Minicontext produced on: 2018-04-19 11:02:00+00:00UTC
Minicontext version: 1.5
ProxySG Appliance: Version 6.6.5.9.201969
Architecture: x86_64
Kernel: Multiprocessor
System image flags: Customer, Optimized, Non-GDB, 64-bit

Hardware exception code: 0x0
Software exception code: 0x11
Page fault linear address: 0x0
Process group: “”
Process: “” in “kernel.exe” at .text+0x1249cca
Register context:
      RIP              RSP              RBP              RDI
0000000001249CCA 0000000000000011 0000000001D08DA0 0000000000000011 
      RSI              RDX              RCX              RBX
000000000000041D 0000000000000000 0000000000000007 0000000001ACEA00 
      RAX              R8               R9               R10
0000000001ACE980 0000000000000008 0000000000000007 0000000000000000 
      R11              R12              R13              R14
0000000001C7B4E0 0000000000000011 00000000013A07C7 0000000001AD6760 
      R15             RFLAGS       CS   SS
004468FEF7B56597 0000000001ACEA00 1D08DA0 FFFFFFFF 
Call Stack:
System data:
0000  23 20 57 61 74 63 68 64 6F 67 20 68 61 73 20 6E   # Watchdog has n
0010  6F 74 20 62 65 65 6E 20 72 65 73 65 74 20 6F 6E   ot been reset on
0020  20 70 72 6F 63 65 73 73 6F 72 20 30 2E 0A 23 20    processor 0..# 
0030  41 63 74 75 61 6C 20 4C 65 6E 67 74 68 20 6F 66   Actual Length of
0040  20 77 64 20 69 6E 74 65 72 76 61 6C 20 33 30 20    wd interval 30 
0050  73 65 63 6F 6E 64 73 2E 0A 23 20 45 78 70 65 63   seconds..# Expec
0060  74 65 64 20 4C 65 6E 67 74 68 20 6F 66 20 77 64   ted Length of wd
0070  20 69 6E 74 65 72 76 61 6C 20 33 30 20 73 65 63    interval 30 sec
0080  6F 6E 64 73 0A 23 20 50 72 6F 63 65 73 73 6F 72   onds.# Processor
0090  20 30 20 73 61 77 20 33 30 30 30 20 74 69 63 6B    0 saw 3000 tick
00A0  73 20 64 75 72 69 6E 67 20 77 64 20 69 6E 74 65   s during wd inte
00B0  72 76 61 6C 20 65 78 70 65 63 74 65 64 20 33 30   rval expected 30
00C0  30 30 2E 0A                                       00..

Regards,

Anoop

0

Related:

  • No Related Posts

Using DCS:SA 6.7 Policies with Nessus Scanner – Policy Translation Error despite policies being OK on other servers

I need a solution

Hi,

I’m experiencing an odd problem… In DCS:SA  6.7, when pushing policies which are OK on all other systems I’m finding that the Nessus scanner systems fail with Policy Translation errors with my IPS policies.

I know that the policies are fine (as they are pushed out successfully elsewhere) it’s just the Nessus servers experiencing this. 

Any ideas what  could cause this and why it’s exclusive to the Nessus scanner systems?

Any advice/insights will be very much appreciated.

Kev

0

Related:

  • No Related Posts

It is not possible to decrypt this message because your keyring does not contain usable private keys(s) corresponding to any of the above public keys

I need a solution

I have recently downloaded a trial of the Symantec Encryption Desktop software. Before purchasing we are testing to make sure it work as needed. I have created, zipped and sent the PGP keys to a vendor. They used the keys to encrypt a document and send back to me; however, I can not seem to decrypt the file.

I get this error: It is not possible to decrypt this message because your keyring does not contain usable private keys(s) corresponding to any of the above public keys

I searched for forum and it seems this has happened to other users but I did not find a solution posted.

Anyone able to help?

0

Related:

  • No Related Posts

for proxy SG S400 -Max CA count limit reached , getting error ‘you can only configure 500 CA certficatae’

I need a solution

For Bluecoat S400-30, under configuration>SSL>CA certificate > we are unable to add new CA cert when we try 

getting error ‘you can only  configure 500 CA certficatae’.

Is there way to know if all our current 500 CA certs are valid? and how to add new CA cert if we reached the maximum limit?

0

Related:

  • No Related Posts

Messages from Messagelabs to our domain are being delayed / fail

I need a solution

Dear Messagelabs,

We have a number of clients who over the last week have been unable to email us as the emails are delayed with the error: –

This message has not yet been delivered. Microsoft Exchange will continue to try delivering the message on your behalf.

All the clients are usings Messagelabs, so there appears to be a common factor between all the clients.

Our domain is 44communications.co.uk

Please can you check your servers to see why our domain will not resolve / receive emials from your servers.

Many thanks

0

Related:

  • No Related Posts