I also had a similar problem a few years back where an HP blade was powered
down and creating a spanning tree loop in the network. The solution was to
remove and replace that particular blade.
-----Original Message-----
From: nobody_at_groupstudy.com [mailto:nobody_at_groupstudy.com] On Behalf Of
Jeremy Garver
Sent: Thursday, October 02, 2014 6:37 PM
Cc: ccielab_at_groupstudy.com
Subject: Re: Cisco-HP ?
I had this problem quite a few years back. I was stumped at first because it
was most likely a bridging loop, but I was confused at the source since I
thought I had all the switches accounted for and STP was enabled. I found it
because the server guys decided to use the outage to perform maintenance on
the Blade Chassis. As soon as they shut it down; everything went back to
normal on my core.
At the time I didn't know that much about spanning-tree, so I just turned on
spanning-tree on the HP as I found out at that time that HP Procurves do not
have STP enabled by default.
I never had the problem again and I have never been back into an HP chassis
switch. Plenty of other HP Procurves, though. The newer H3C switches by HP
do come with STP enabled by default at least, but they are still a pain.
If I had it to do now; I would handle it the same way Marc suggested and
enable MST everywhere and make sure that your cores are root; dividing the
VLANs accordingly across the cores (one core handling root for half the
VLANs and the other core handling root for the other half). That is,
assuming that you have dual cores. Everyone should, but not everyone can
afford them; especially when using Ci$co.
On Thu, Oct 2, 2014 at 8:38 PM, marc abel <marcabel_at_gmail.com> wrote:
> Filtering BPDUs is likely to make the problem worse, not better.
>
> On Thu, Oct 2, 2014 at 7:35 PM, kapilatrish <kapilatrish_at_hotmail.com>
> wrote:
>
> > If cisco says its a spanning tree issue can't you filter the bpdus
> > on the port?
> >
> >
> > Sent from Samsung Mobile
> >
> > -------- Original message --------
> > From: Cisco Fanatic <ebay_products_at_hotmail.com>
> > Date:02/10/2014 7:48 PM (GMT-05:00)
> > To: ccielab_at_groupstudy.com
> > Subject: Cisco-HP ?
> >
> > This is really getting to my nerves. I have a WS-C4500X-16SFP+
> > switch connected to HP Blade and we already had 2 outages in the past
week.
> > HP is saying that they don't see an issue on their blades and Cisco
> > TAC
> is
> > saying it's to do with HP blade which is running VMs that is causing
> > spanning tree issues.
> > Please I needs some insight into this from people who have worked on
> > HP
> and
> > Cisco platform.
> > Are there any know interoperability issues between Cisco and HP?
> > Also, is there a best practice design which explain how to connect
> > Cisco with HP Blade Servers?
> > Yuri
> >
> >
> > Blogs and organic groups at http://www.ccie.net
> >
> > ____________________________________________________________________
> > ___ Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
> >
> >
> > Blogs and organic groups at http://www.ccie.net
> >
> > ____________________________________________________________________
> > ___ Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
> >
> >
> >
> >
> >
> >
> >
> >
>
>
> --
> Marc Abel
> CCIE #35470
> (Routing and Switching)
>
>
> Blogs and organic groups at http://www.ccie.net
>
> ______________________________________________________________________
> _ Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
Received on Fri Oct 03 2014 - 06:32:48 ART
This archive was generated by hypermail 2.2.0 : Sat Nov 01 2014 - 08:31:30 ART