Yeah for Solarwinds, it’s not cheap but it’s not stupidly expensive neither … 
in comparison to the words “BMC” and “Remedy” ;)

> On Dec 12, 2016, at 8:08 PM, Josh Baird <joshba...@gmail.com> wrote:
> 
> Sorry - you were probably referring to BMC,  not Solarwinds.
> 
> BMC, last time I looked, was indeed stupid expensive.
> 
> On Dec 12, 2016, at 8:03 PM, Josh Baird <joshba...@gmail.com 
> <mailto:joshba...@gmail.com>> wrote:
> 
>> Not for a large 'enterprise,' and the required horsepower really isn't 
>> *that* bad for NPM/NCM/NFA.
>> 
>> On Dec 12, 2016, at 7:49 PM, Josh Reynolds <j...@kyneticwifi.com 
>> <mailto:j...@kyneticwifi.com>> wrote:
>> 
>>> Stupid $ :(
>>> 
>>> On Dec 12, 2016 6:24 PM, "Paul Stewart" <p...@paulstewart.org 
>>> <mailto:p...@paulstewart.org>> wrote:
>>> Very cool!
>>> 
>>> 
>>>> On Dec 12, 2016, at 7:20 PM, Josh Reynolds <j...@kyneticwifi.com 
>>>> <mailto:j...@kyneticwifi.com>> wrote:
>>>> 
>>>> Sounds similar to our pending NMS...
>>>> 
>>>> BMC TrueSight spread across around 8,000 VMs + netapps + infra.
>>>> 
>>>> On Dec 12, 2016 6:14 PM, "Paul Stewart" <p...@paulstewart.org 
>>>> <mailto:p...@paulstewart.org>> wrote:
>>>> It really depends …. so in our case, it’s running a dedicated web 
>>>> interface and a pair of pollers.  The SQL backend is clustered serving 
>>>> other systems besides just Solarwinds - it’s a *large* cluster running MS 
>>>> SQL Enterprise and NetApp SAN….  it was already existing for other 
>>>> internal systems we utilize….
>>>> 
>>>> Previous job, with Solarwinds, we ran 3 dedicated polling engines, a 
>>>> dedicated web front end, and a dedicated server with SQL Standard on the 
>>>> backend
>>>> 
>>>> The variables are polling frequency (we are 5 minutes), number of 
>>>> nodes/interfaces/volumes etc…. and to some degree number of users hitting 
>>>> the web interface.  Also, reports can put a load on the system depending 
>>>> on their complexity and how often they run.
>>>> 
>>>> Cheers,
>>>> Paul
>>>> 
>>>>> On Dec 12, 2016, at 7:02 PM, Josh Reynolds <j...@kyneticwifi.com 
>>>>> <mailto:j...@kyneticwifi.com>> wrote:
>>>>> 
>>>>> How big of a windows server farm does it take to scale that thing 
>>>>> horizontally?
>>>>> 
>>>>> On Dec 12, 2016 5:49 PM, "Paul Stewart" <p...@paulstewart.org 
>>>>> <mailto:p...@paulstewart.org>> wrote:
>>>>> Rancid at moment - moving to Solarwinds NCM which does pretty much the 
>>>>> same but with a whole bunch of reporting and compliance options, plus 
>>>>> integration with existing network monitoring 
>>>>> 
>>>>>> On Dec 12, 2016, at 3:57 PM, That One Guy /sarcasm 
>>>>>> <thatoneguyst...@gmail.com <mailto:thatoneguyst...@gmail.com>> wrote:
>>>>>> 
>>>>>> reviving an old thread
>>>>>> 
>>>>>> I put our beta on the network, within 5 minutes of downloading, every 
>>>>>> device we want backups for is backed up, we arent a big shop so its less 
>>>>>> than 50.
>>>>>> 
>>>>>> Even our Fortigates
>>>>>> 
>>>>>> I really like this
>>>>>> 
>>>>>> alot
>>>>>> 
>>>>>> And I hate everything
>>>>>> 
>>>>>> On Mon, May 30, 2016 at 1:58 AM, Eric Kuhnke <eric.kuh...@gmail.com 
>>>>>> <mailto:eric.kuh...@gmail.com>> wrote:
>>>>>> Rancid for Cisco and juniper and foundry.
>>>>>> 
>>>>>> Ubnt ptp radios get their config manually backed up before deployment 
>>>>>> and after each firmware upgrade. Configs saved on a file server and on 
>>>>>> mediawiki instance.
>>>>>> 
>>>>>> Same with other ptp links.
>>>>>> 
>>>>>> On May 27, 2016 4:13 PM, "SmarterBroadband" <li...@smarterbroadband.com 
>>>>>> <mailto:li...@smarterbroadband.com>> wrote:
>>>>>> Interested to hear what people use for automatic backups of their 
>>>>>> network equipment configs.
>>>>>> 
>>>>>>  
>>>>>> 
>>>>>> Mikrotik, Cisco, Zyxel, Ubiquity, Netonix etc…
>>>>>> 
>>>>>>  
>>>>>> 
>>>>>> We currently use Rancid. 
>>>>>> 
>>>>>>  
>>>>>> 
>>>>>> What do you use?
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> -- 
>>>>>> If you only see yourself as part of the team but you don't see your team 
>>>>>> as part of yourself you have already failed as part of the team.
>>>>> 
>>>> 
>>> 

Reply via email to