LISTSERV mailing list manager LISTSERV 16.0

Help for MICE-DISCUSS Archives


MICE-DISCUSS Archives

MICE-DISCUSS Archives


MICE-DISCUSS@LISTS.IPHOUSE.NET


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

MICE-DISCUSS Home

MICE-DISCUSS Home

MICE-DISCUSS  December 2019

MICE-DISCUSS December 2019

Subject:

Re: WiscNet Remote Switch / Dedicated Remote Switches

From:

Chris Wopat <[log in to unmask]>

Reply-To:

MICE Discuss <[log in to unmask]>

Date:

Tue, 3 Dec 2019 15:03:16 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (105 lines)

Hi folks, thanks for the lively discussion so far. A few notes and  
comments about the more recent technical part of the discussion. 
 
In our shared switch scenario, we intend to limit mac addresses per our  
downstream customers on the MICE vlan itsself, not per physical interface. 
 
This seems fairly standard, we would hope that as many as possible are  
already doing this. We would advocate this as a requirement for all  
customer-facing ports on all switches, remote or otherwise, dedicated or  
not dedicated. 
 
We would also welcome an mac limit on the Arista Core set to something  
reasonable facing us and other remote switches as well. The current  
non-remote switch limit of 5 would work perfectly fine in our scenario.  
Perhaps a limit per remote switch based on N+something should also be  
enforced as long as it's not a large burden on the MICE operators. 
 
We also use BGP session culling, it's deactivated by default. We'd  
activate on the MICE vlan during maintenance. 
 
#### Junos config example for mac limits #### 
 
interfaces { 
     ae0 { 
	description "WiscNet Router"; 
         unit 100 { 
             description "MICE :RP:"; 
             vlan-id 100; 
         } 
     } 
     et-0/0/25 { 
         description "MICE Arista Core"; 
         unit 0 { 
             family ethernet-switching { 
                 interface-mode access; 
                 vlan { 
                     members 100; 
                 } 
             } 
         } 
     } 
} 
 
vlans { 
     vlan-100 { 
         description "MICE Peering"; 
         vlan-id 100; 
         interface ae0.100; 
         inactive: forwarding-options { 
            /* based on https://tinyurl.com/junos-bgp-culling */ 
             filter { 
                 input CullBGP-MICE; 
                 output CullBGP-MICE; 
             } 
         } 
         switch-options { 
             interface ae0.100 { 
                 interface-mac-limit { 
                     1; 
                     packet-action drop-and-log; 
                 } 
             } 
         } 
     } 
} 
 
 
As far as graphing per-vlan, this works well on Q5 based systems such as  
our Juniper QFX10k. This + buffers is part of the reason we chose this  
platform instead of a cheap Broadcom device. This is also a part of the  
reason we would prefer to *not* shove a cheap Broadcom/chinaswitch  
device in the middle. 
 
We also support SNMP polling per interface. In our case we'd expose just  
the MICE interfaces using views. 
 
630 below is a subinterface's snmp ifIndex. 1.10, 1.11, etc are  
ifOctests, ifUcastPkts, and so on for that interface. This is manual,  
but with only a handful of interfaces, totally do-able: 
 
snmp { 
     view view-mice { 
         oid .1 exclude; 
         oid .1.3.6.1.2.1.2.2.1.10.630 include; 
         oid .1.3.6.1.2.1.2.2.1.11.630 include; 
         oid .1.3.6.1.2.1.2.2.1.13.630 include; 
         oid .1.3.6.1.2.1.2.2.1.14.630 include; 
         oid .1.3.6.1.2.1.2.2.1.16.630 include; 
         oid .1.3.6.1.2.1.2.2.1.17.630 include; 
         oid .1.3.6.1.2.1.2.2.1.18.630 include; 
         oid .1.3.6.1.2.1.2.2.1.19.630 include; 
         oid .1.3.6.1.2.1.2.2.1.20.630 include; 
     } 
     community wiscnet-mice { 
         view view-mice; 
         authorization read-only; 
     } 
} 
 
Cheers, 
--  
Chris Wopat 
Network Engineer, WiscNet 
[log in to unmask]   608-210-3965 

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010

ATOM RSS1 RSS2



LISTS.IPHOUSE.NET

CataList Email List Search Powered by the LISTSERV Email List Manager