CB, for STP to be detecting a loop, I assume either EX4500#1 is also directly connected to EX4500#3? or does it form a ring with the MX80 bridging between EX4500#1 and EX4500#3?
if there is a physical loop, but not a logical one as I believe you stated all links are p2p VLANs, you could either: -turn the ports into routed ports instead of using RVIs -disable RSTP altogether: if just doing 'delete protocols rstp' doesn't work, it may be because RSTP is on by default...so you could instead do 'set protocols rstp interface all disable' - or modify as necessary -run something like MSTP in the event you have to span VLANs you can have those VLANs block on a certain port but these p2p VLANs will not. The risk I see of turning off STP altogether is if someday down the road you span a VLAN across all of the switches, and create yourself a nice little forwarding loop :) Also, posting pieces of config may help in case there might be some other reason why its not working as expected. Good luck, Will On Dec 1, 2010, at 12:58 AM, juniper-nsp-requ...@puck.nether.net wrote: > > > Message: 9 > Date: Tue, 30 Nov 2010 23:58:01 -0600 > From: c...@packetrail.net > To: juniper-nsp@puck.nether.net > Subject: [j-nsp] Angry EX (STP?) > Message-ID: <ca8730b135365358869ab5b0a2629dd0.squir...@packetrail.net> > Content-Type: text/plain;charset=iso-8859-1 > > > Hello, > > We have three EX4500's in the following configuration: > > > > EX4500#1---------EX4500#2--------EX4500#3 > > | > > | > > MX80 (router) > > > > We are observing xe-0/0/16 on the EX#2 facing the EX#1 site having its > port blocked and unblocked over and over(see log below). I'd prefer to > disable STP, rSTP, lldp and lldp-med, but if I do we see blocking as > well... We are only using point to poing VLANs and there is no physical > possibility of a L2 loop. I have deleted the STP statement, and suspect > rSTP has taken over. > > > > Any ideas as to how to stabilize (or eliminate) our STP, rSTP, lldp, > lldp-med environment? > > > > Thanks in Advance! > > > > CB. > > > > > > Log Snip (yes, it is still Aug 25th in our world. Will fix. ;-) > > > > Aug 25 12:09:37 ALBQ_EX4500 init: lldpd-service (PID 20934) started > Aug 25 12:09:39 ALBQ_EX4500 lldp[20934]: TASK_TASK_BEGIN: Commencing > virtual chassis control daemon, version 10.3R1.9, built builder by > 2010-08-13 12:56:38 UTC > Aug 25 12:09:39 ALBQ_EX4500 /kernel: > Aug 25 12:09:39 ALBQ_EX4500 mib2d[861]: SNMP_TRAP_LINK_DOWN: ifIndex 536, > ifAdminStatus up(1), ifOperStatus down(2), ifName xe-0/0/16 > Aug 25 12:10:05 ALBQ_EX4500 last message repeated 7 times > Aug 25 12:12:06 ALBQ_EX4500 last message repeated 348 times > Aug 25 12:13:14 ALBQ_EX4500 last message repeated 288 times > Aug 25 12:13:19 ALBQ_EX4500 mgd[19934]: UI_DBASE_LOGOUT_EVENT: User > 'xxxxxx' exiting configuration mode > Aug 25 12:13:36 ALBQ_EX4500 mib2d[861]: SNMP_TRAP_LINK_DOWN: ifIndex 536, > ifAdminStatus up(1), ifOperStatus down(2), ifName xe-0/0/16 > Aug 25 12:14:04 ALBQ_EX4500 last message repeated 20 times > Aug 25 12:16:06 ALBQ_EX4500 last message repeated 61 times > Aug 25 12:26:05 ALBQ_EX4500 last message repeated 1679 times > Aug 25 12:35:42 ALBQ_EX4500 last message repeated 1419 times > Aug 25 12:40:15 ALBQ_EX4500 last message repeated 356 times > Aug 25 12:40:15 ALBQ_EX4500 mgd[19934]: UI_DBASE_LOGIN_EVENT: User > 'xxxxxx' entering configuration mode > Aug 25 12:40:15 ALBQ_EX4500 mib2d[861]: SNMP_TRAP_LINK_DOWN: ifIndex 536, > ifAdminStatus up(1), ifOperStatus down(2), ifName xe-0/0/16 > Aug 25 12:40:21 ALBQ_EX4500 last message repeated 10 times > Aug 25 12:41:06 ALBQ_EX4500 last message repeated 2 times > Aug 25 12:41:07 ALBQ_EX4500 mgd[19934]: UI_CHILD_EXITED: Child exited: > PID 20977, status 1, command '/sbin/ifinfo' > Aug 25 12:41:11 ALBQ_EX4500 mib2d[861]: SNMP_TRAP_LINK_DOWN: ifIndex 536, > ifAdminStatus up(1), ifOperStatus down(2), ifName xe-0/0/16 > Aug 25 12:41:11 ALBQ_EX4500 mib2d[861]: SNMP_TRAP_LINK_DOWN: ifIndex 536, > ifAdminStatus up(1), ifOperStatus down(2), ifName xe-0/0/16 > Aug 25 12:41:12 ALBQ_EX4500 mgd[19934]: UI_CHILD_EXITED: Child exited: > PID 20979, status 1, command '/sbin/ifinfo' > Aug 25 12:41:15 ALBQ_EX4500 mib2d[861]: SNMP_TRAP_LINK_DOWN: ifIndex 536, > ifAdminStatus up(1), ifOperStatus down(2), ifName xe-0/0/16 > Aug 25 12:41:35 ALBQ_EX4500 last message repeated 16 times > Aug 25 12:41:36 ALBQ_EX4500 mgd[19934]: UI_DBASE_LOGOUT_EVENT: User > 'xxxxxx' exiting configuration mode > Aug 25 12:41:37 ALBQ_EX4500 mib2d[861]: SNMP_TRAP_LINK_DOWN: ifIndex 536, > ifAdminStatus up(1), ifOperStatus down(2), ifName xe-0/0/16 > Aug 25 12:42:06 ALBQ_EX4500 last message repeated 60 times > Aug 25 12:42:28 ALBQ_EX4500 last message repeated 85 times > Aug 25 12:42:29 ALBQ_EX4500 mgd[19934]: UI_DBASE_LOGIN_EVENT: User > 'xxxxxx' entering configuration mode > Aug 25 12:42:29 ALBQ_EX4500 mib2d[861]: SNMP_TRAP_LINK_DOWN: ifIndex 536, > ifAdminStatus up(1), ifOperStatus down(2), ifName xe-0/0/16 > Aug 25 12:42:35 ALBQ_EX4500 last message repeated 32 times > Aug 25 12:43:07 ALBQ_EX4500 last message repeated 135 times > Aug 25 12:43:07 ALBQ_EX4500 mgd[19934]: UI_DBASE_LOGOUT_EVENT: User > 'xxxxxx' exiting configuration mode > Aug 25 12:43:07 ALBQ_EX4500 mib2d[861]: SNMP_TRAP_LINK_DOWN: ifIndex 536, > ifAdminStatus up(1), ifOperStatus down(2), ifName xe-0/0/16 > Aug 25 12:43:35 ALBQ_EX4500 last message repeated 104 times > > > ------------------------------ > > _______________________________________________ > juniper-nsp mailing list > juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp > > End of juniper-nsp Digest, Vol 97, Issue 1 > ****************************************** _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp