@pete-s
So, I think we may go down the route of just replacing the single socket CPU. I was seeing listings for that CPU around $550 through one of our partners. Ram configuration is already to spec for that CPU at single rank 8GB 2400 MT/s. That should get us through until June of 2023 when the system and cough.... vendor should be kicked to the curb.
@pete-s
So, I think we may go down the route of just replacing the single socket CPU. I was seeing listings for that CPU around $550 through one of our partners. Ram configuration is already to spec for that CPU at single rank 8GB 2400 MT/s. That should get us through until June of 2023 when the system and cough.... vendor should be kicked to the curb.
@pete-s
Got it. With the CPU's under $1,000 a piece and the ram usage being so low we could easily upgrade the existing systems for about 2-3K each. Again, the initial concern that the district will have to deal with is that the system is coming up on EOL.
For sure! We would definitely want to spec it out appropriately. At least, purchasing newer compute nodes... I'm thinking about just using the SAN and just ACL'ing it off so its not routable outside a certain VLAN. Its already got 16TB's of storage and you can DAS to it too with expansion shelves. I'm hoping that adding it to our current infrastructure is a last resort that I would fight.
@pete-s
Thanks for the multiple responses.
From my understanding... Xeon chips do not come with Intel QuickSync thus the thoughts of adding a GPU and to reduce the need for a larger CPU https://www.intel.com/content/www/us/en/support/articles/000034104/processors/intel-xeon-processors.html#:~:text=None of the Intel
,Intel Quick Sync Video. I'm not sure what the CPU limits are for the 2017 version of xProtect are, if any.
From a licensing perspective that is not a concern as we are under multiple academic agreements where licensing is minimal in cost or is part of a multi year agreement... If we are sticking with Windows a core count doesn't apply for us. So, what we would be looking at is cost/performance and whatever limitations the xProtect 2017 version have, if any.
I'm not totally sure if the board is single socket only but it may very well be dual... I'm assuming I can just replace that single socket of CPU with the one suggested and just replace the existing ram with the proper spec'd ram and ram channel configuration for that CPU. That would allow us room to purchase the same setup on the other side to expand if needed.
Hi all...
We have an external vendor that's providing us security camera services which I believe could be better. In saying that, we are hitting roadblocks with expansions to our surveillance on our campus due to their suggestions to a previous set of leaders that were passive. With that said I'm trying to apply a bandage until we can go through our budgeting process to acquire funds.
What we have:
HP ProLiant ML350 Gen9 (Intel Xeon E5-2609 v4, 32GB Ram, 4TB of internal storage) with Mobile Server, xProtect Service Channel, and xProtect 2017 R3. Total of 58 cameras with an estimated projection of 150-200 through 7 buildings
HP ProLiant ML350 Gen9 (Intel Xeon E5-2609 v4, 32GB Ram, 4TB of internal storage) with Recording Server.
Cameras range in megapixel from 2.1 to 12
Ingested bandwidth ranges from 70-115 mbps depending on motion
Solutions:
The only problem I see is that both the 3 servers in our cluster and the physical camera servers need replaced by 2023-2024 which is right around the corner. Its another story but the idea was to eventually to consolidate our 4 physical servers into a VM cluster with 4 or 5 servers total and add more storage to the HP MSA (only using 6 bays out of the 24).