This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Monthly report

Hi,

we have 2 SG310 in Active/passive mode, today in the monthly reports I see something that was bit strange. when looking at the concurrent connections we see the graph stars from end week 04 untill today and it is right becuase in the same day in week 04 we did install the updates and reboot the Sophos so master and slave change palace.

But in the same monthly report when we check the hardware report ie memory, the graph shows form week 01 to week 04 at the same time when the device was rebooted.

is this means that network graphs are Always from the master node and hardware graphs are from pervious master? also in the monthly reports we Always see the node 1 as device name is this normal?

Thanks



This thread was automatically locked due to age.
Parents
  • Today I noticed what appears to be a similar problem across all of my HA (A/P) pairs.

    This seems to be the case for monthly, weekly and daily reports too.

    Having looked into it this seems to have been the case for a while, I have monthly archived reports from 9.356-3 which only show data for the latter part of the month following a failover caused by an upgrade cycle.

     

    The cluster interface does show data which changes from inbound to outbound (as one might expect) when the failover occurs.

    I would expect the reporting to be capable of gathering and display the data from the node that was active.

    As it stands I now realise that a lot of my archived reports do not contain all the data I need them to.

  • Hi RBCJB,

    I think the concurrent connection in the monthly or weekly report shows the Active node information and the hardware shows the information of the previous master. I hope that  someone else can confim this. regarding the name that I see in the monthly report, is normal because this is the name of H/A and in my case is the same as the name of node 1.

    I think the solution to this issue is enabling the option Preferred Master at H/A configuration.

    Also what I dont understand is why there is a very large traffic at eth3? shouldn't this link only be used for sync configuration between 2 devices?  

     

    Thanks

  • AreshAreshi said:

    ...Also what I dont understand is why there is a very large traffic at eth3? shouldn't this link only be used for sync configuration between 2 devices?  

     

    I think the nodes share information about active sessions and this stuff, so the more load you have the more traffic on that port you get.

     

    Best 

    Alex

    -

Reply
  • AreshAreshi said:

    ...Also what I dont understand is why there is a very large traffic at eth3? shouldn't this link only be used for sync configuration between 2 devices?  

     

    I think the nodes share information about active sessions and this stuff, so the more load you have the more traffic on that port you get.

     

    Best 

    Alex

    -

Children