This falls into the category of extreme nit picking but the remote switch website document says this
"Operators are responsible for the costs of operating their remote switch and the links to the core switch. They must monitor their traffic levels and promptly add capacity to keep the links running congestion-free."
Under this wording, SFN would be responsible for the links to the core switch which would actually be on the MN VoIP switch link in this context and is something I would expect is not within SFN's ability to manage seeing as how SFN, presumably, does not manage MN VoIP's equipment or links.
As I initially stated, this is more nit picking as I would personally interpret the intent of the message on the website to be "remote switch operator egress link(s) towards the core switch" in this context since the SFN switch would have no links of its own to the core switch. I expect the context of tiered remote switches like this was not originally considered when the text was composed/agreed upon and if this topology is permitted, I would suggest the website language be updated to reflect/consider this.
With my described interpretation, I have no objections to the tiered remote-remote-switch setup. If this request is accepted as written, I would suggest MICE consider capping this tiered remote switch approach at 2 deep (as in this case) as a max; I feel it would begin to get cumbersome to manage/track the administrative relationships, troubleshooting, managing the traffic graphing configurations, etc. My cap suggestion is just a starting point off, not something I am adamantly positioned on and possibly this would be better discussed in a separate thread.
I would also think it wise to look at MICE's big brother SIX and see if they have encountered this kind of scenario/request before and if so, what their conclusions were.
________________________________
From: MICE Discuss <[log in to unmask]> on behalf of Richard Laager <[log in to unmask]>
Sent: Friday, September 28, 2018 3:31 PM
To: [log in to unmask]
Subject: Re: [MICE-DISCUSS] South Front Networks, LLC Remote switch request
I'm bringing this remote switch request to the discussion list per our remote switch policy:
http://micemn.net/technical.html
On 09/28/2018 09:25 AM, Jay Hanke wrote:
South Front Networks requests approval to install a MICE Remote Switch in SFN's Albert Lea Datacenter.
South Front proposes the following:
1) SFN will acquire a Juniper QFX5100 or Arista comparable switch dedicated to MICE.
2) SFN will acquire and pay for any required connectivity back to the MN VoIP remote switch, MN VoIP and SFN remote switches will share the existing 40 Gbps MICE link into the main fabric. Both SFN and MN VoIP agree to upgrade capacity as needed on the uplink to the main switch.
3) SFN will initially install 20 Gbps of capacity and will upgrade capacity as needed per the board and technical committee requirements
4) SFN agrees to enforce the MICE technical port rules
5) SFN agrees to coordinate connections to the new remote switch
6) SFN agrees to inform all prospective members that connections going to the SFN MICE Remote switch are not connected directly to MICE.
7) SFN agrees to perform any required configuration and troubleshooting
8) SFN agrees to provide configuration access and snmp access to the MICE technical committee to ease troubleshooting and to provide publicly available graphing.
Thanks!
--
Jay Hanke, President
South Front Networks
[log in to unmask]
Phone 612-204-0000
--
Richard
________________________________
To unsubscribe from the MICE-DISCUSS list, click the following link:
http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
