Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

syslog of standby unit

Trying to figure out why i'm not seeing syslog messages coming from my standby unit of an active/passive pair of 4700 ACE Appliances.

ACE-4710-K9
Version A3(2.4)

I have syslog configured
failover is functioning
i see log messages sent (UDP514) to the syslog server from the primary
Standby logging is enabled.

However, i see no log messages being generated to the syslog.

 

Am I missing something in this scenario?

 

Thanks.

Bruce



 

1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Hi Bruce,Well, i would say it

Hi Bruce,

Well, i would say it depends upon needs and different requirements. There is no such best practice. But there can be many events which happen independently to an individual device and it would make sense to enable logging on it too. But ensure that you don't enable logging levels to very high like 6 or 7 which can actually overwhelm the device sometimes. In any case these levels should only be set while you are troubleshooting the actual problem.

Regards,

Kanwal

9 REPLIES
Cisco Employee

Hi Bruce,If logging standby

Hi Bruce,

If logging standby is enabled then standby should send the logs. Can you try disabling and re-enabling standby logging on ACTIVE? Are you able to ping the syslog server from the standby?

There is one DDTS too in version you are running:

CSCte66425    Syslog not generating level 6 messages

But that is applicable to active, standby and standalone ACE.

Regards,

Kanwal

New Member

Yes - disabled/reenabled

Yes - disabled/reenabled standby logging - no affect

Yes - I can ping the syslog server from the standby unit

Yes - all firewalls in path are open for UDP 514

I performed a quick google search for that bug you reference, and i received no results.  Have a link?

Cisco Employee

Hi Bruce,I tried searching

Hi Bruce,

I tried searching internally here and couldn't find much regarding this. In one issue, clear logging helped. Could you please do "clear logging" and see if starts sending the logs again? Do you also think you can possibly try and reload standby and see if that helps?

Is it a problem with single context or all contexts? I did find few cases in which only few contexts had problem and not all. The issue can also be due to contexts not guaranteed minimum resource.

Kindly check on these things and see if that resolves the issue. Configuration seems to good here.

Regards,

Kanwal

New Member

Kanwal,I cant reload the

Kanwal,

I cant reload the standby.  seems to be some contexts are working, some are not.  example:  admin context, does not appear to be logging, but the user context is...same exact configuration.

Im beging to think this maybe a routing issue out of the ace...is there a mechanism for "sourcing" a specific interface for logging?

also, i'm not familiar with the resource guarantee you mention

The issue can also be due to contexts not guaranteed minimum resource.

 

thanks.

 

 

New Member

Let me pose another question.

Let me pose another question.  Maybe i'm looking at this wrong.

So, with standby logging on, the documentation advises you are increasing the logging by twice as much with an HA pair...which makes sense.  both primary and standby units are logging.

so, maybe the better approach is to log only from the active unit (generally the primary).  but, that begs the question:

if standby logging is disabled, does that imply in a failover scenario, where the secondary unit assumes the role of active, does it then immediately begin logging to the syslog server?

If it does, then probably, the better approach is to keep standby logging disabled.

Bruce

Cisco Employee

Hi Bruce,You are correct in

Hi Bruce,

You are correct in your understanding. But please note that "standby" and "Active" probe real servers independently among other things. So standby can log messages related to events which are independent of ACTIVE like probe failure.

But yes, the standby after becoming ACTIVE should start logging immediately.

Regards,

Kanwal

New Member

ahhh...ok...so, possibly my

ahhh...ok...so, possibly my thought about disabling standby logging may not be appropriate, since we would want to see failed probes and the like from the standby BEFORE a failover occurred...

do you know what best practice is? or is that simply based on your need?

appreciate your continued responses...

 

Cisco Employee

Hi Bruce,Well, i would say it

Hi Bruce,

Well, i would say it depends upon needs and different requirements. There is no such best practice. But there can be many events which happen independently to an individual device and it would make sense to enable logging on it too. But ensure that you don't enable logging levels to very high like 6 or 7 which can actually overwhelm the device sometimes. In any case these levels should only be set while you are troubleshooting the actual problem.

Regards,

Kanwal

Cisco Employee

Hi Bruce,Did you try clear

Hi Bruce,

Did you try clear logging? If not, i would suggest to do the same.

Please do "show logging statistics" in affected contexts and see if the counters like "host" are increasing. Also, please do "show logging queue" and see the below counter's value:

switch/Admin# show logging queue

        Logging Queue length limit : 80 msg(s), 8 msg(s) discarded.
        Current 0 msg on queue, 5 msgs most on queue

By default, logging queue would be 80. If you see it is 0 please increase it.

Also, do "show resource usage" in affected and look at the counter's highlighted below:

switch/Admin# show resource usage
                                                     Allocation
        Resource         Current       Peak        Min        Max       Denied
-------------------------------------------------------------------------------
Context: Admin
  conc-connections              0         42        100    8000000          0
  mgmt-connections              4       1630        100     100000          0
  proxy-connections             0         42          0    1048572          0
  xlates                        0          0          0    1048572          0
  bandwidth                   616     338973    2500000  625000016          0
    throughput                  0     207796    1250000  500000016          0
    mgmt-traffic rate         616     131177    1250000  125000000          0
  connection rate               0        706        100     600000          0
  ssl-connections rate          0          0          0      30000          0
  mac-miss rate                 0          1          0       2000          0
  inspect-conn rate             0          0          0     240000          0
  http-comp rate                0          0          0  786432000          0
  to-cp-ipcp rate               0        534          0       5000          0
  acl-memory                95136      97096          0   99579792          0
  sticky                        2          2          0    4194304          0
  regexp                        0          0          0    1048576          0
  syslog buffer                 0      29696          0    4194304          0
  syslog rate                   0          6          0     100000          0

 

If you see the last counter on right increasing then there is a resource problem. Also, do "show resource allocation" and see if you have any minimum resource guaranteed or not. Generally, if you don't any number in right-most column, you don't need to worry about resource crunch. But it is a good practice to have some minimum guaranteed to each context.

Coming to your question of sending logs from specific interface, i don't see any way of doing it. i guess it will send logs from the interface through which the syslog server is reachable. But you can always make the ACE to define the interface or hostname as a device-id to be included in the log messages it will send, even though the actual interface through which the log sent is different.

 

Regards,

Kanwal

 

 

 

 

133
Views
0
Helpful
9
Replies
CreatePlease to create content