If the firmware update doesn't solve the problem, it's time to start
looking closely at the hardware itself.

Kurt

On Wed, Jul 15, 2015 at 9:53 AM, J- P <[email protected]> wrote:
> It is WAY out of date, however, since I was VPN'd in and it was 3am, HP
> suggested not to update it remotely,
> Will do the FW update today.
>
> As far as PRTG goes it was set to the defaults (guru config)
>
>
>
>
>
>> Date: Wed, 15 Jul 2015 09:37:09 -0700
>> Subject: Re: [NTSysADM] PRTG crashed a switch?
>> From: [email protected]
>> To: [email protected]
>
>>
>> We use PRTG, and have both HP and Juniper switches, though ours are 24
>> and 48 port devices, not as large as what you're working with. I've
>> never seen anything like that.
>>
>> I suppose it might be possible, depending on what PRTG was set to do,
>> and how frequently - I just find it unlikely.
>>
>> I'd check the firmware on that switch - is it up to date?
>>
>> Kurt
>>
>> On Wed, Jul 15, 2015 at 9:29 AM, J- P <[email protected]> wrote:
>> > Hi all
>> >
>> > Went onsite yesterday to check out some network issues, so I fired up
>> > PRTG
>> > and let it do its thing.
>> > Later in the evening when I'm home I VPN into the site and after 12
>> > minutes
>> > my vpn drops , I check the public IP internet is up.
>> >
>> > I call the IT mgr and let him know that I cant authenticate, he goes to
>> > the
>> > office and tells me the core switch (240 port procurve) is lit up like
>> > Christmas tree (all lights flashing), no telnet no ssh no ping reply ,
>> > he
>> > does a physical shutdown , and I'm back in , ten minutes later it drops
>> > again this happened 4 times.
>> >
>> > Finally the last time it remains online, they are telling me that this
>> > "has
>> > never happened before" (at least that they know of it was late at night)
>> >
>> > Oh and the logs on the switch only show 2 entries
>> >
>> > 1. First time installation
>> > 2. Warning loss of link on B10
>> >
>> > So is it possible that PRTG caused this, or is likley they've never been
>> > around that late to realize this?
>> >
>>
>>


Reply via email to