Did they plug in a switch or a router? Was it a loop? Are there loop mitigation techniques in place to automatically shutdown offending ports? When would you suggest that it's safe to come back online? On 2/19/14 4:40 PM, "Jay Hanke" <jayhanke@MANKATONETWORKS.NET> wrote:
HCMC turned up peering this afternoon, l2 has been up for several days.
I think the timing was maybe 20 minutes prior to issue.
On Wed, Feb 19, 2014 at 2:03 PM, Richard Laager <rlaager@wiktel.com> wrote:
Can someone look at the route server logs and see who the new IPv4 peer was that showed up just before this problem started?
-- Richard
########################################################################
To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
-- Jay Hanke CTO, CCIE #19093 Mankato Networks LLC PO Box 54 619 S Front St Mankato, MN 56001-3838 Google 530-618-2398 jayhanke@mankatonetworks.net http://www.mankatonetworks.com http://www.neutralpath.net
########################################################################
To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1