2011-05-16 03:30 PM
A customer is reporting what appears to be larger than normal amounts of traffic between their DFM server and their storage systems and is wondering if the type/frequency of data that is transferred has changed in the 4.x release or with DOT 8.x.
We don't have any prior data to compare with, but on a recent network report, there were many monthly transfers that stuck out. For example, 3 storage systems transferred >100GB, >60GB, and >65GB, respectively to the DFM server over the month.
The only two things that happened over the month are they upgraded to DOT 8.0.1 and they upgraded DFM to 4.0.
They are going to open a case but I thought I'd check in case anyone had an idea.
2011-05-17 05:09 AM
I am looking for the below data from you :
1. On DOT 8.01 - Are you running 7-mode or c-mode ??
2. On DFM 4.0 - Are you running only operations manager ? or you do have other products enabled (Perf. Advisor, Prov. Manager, Prot. Manager) ??
2011-05-17 06:55 AM
Thanks for your assistance.
In terms of 8.0.1, they are running 7-mode.
Also, they are only running Operations Manager; they are not running
Performance Advisor, Provisioning Manager, or Protection Manager.
2011-05-17 07:48 AM
Do those filers act as destination for snapvault/snapmirror relationships ?
Is protection manger/bizcon licenesed in the dfm server ?
If both these are true, what's the file sizes of the snapmirrorlog* files in the filer ?
2011-05-17 08:09 AM
I’m not sure about this but will ask them.
Just curious – is this something that would have been enabled when upgrading from 3.8 to 4.0 or has it always been enabled.
2011-05-17 08:26 AM
2011-05-17 08:40 AM
I know of nothing in particular that changed between 7.x and 8.0.1 which would cause DFM to transfer more data.
I suggest using a packet tracer (e.g. Wireshark) to collect some traffic between one of the 8.0.1 systems and a system which has lower traffic.It'll take some elbow grease to figure this out but that will give you the raw data. I'd start by trying to identify whether SNMP or ZAPI traffic is the cause (or something else entirely). Based on what you find, we can dig into the details.