Is the MICE Looking Glass down? When I telnet or SSH to it, I get no prompt. Kind regards, Frank
On Fri, Nov 03, 2017 at 09:15:09AM +0000, Frank Bulk wrote:
Is the MICE Looking Glass down? When I telnet or SSH to it, I get no prompt.
Hmm, doesn't seem to be. Works for me. (both ssh & telnet). Which hostname are you using? $ ssh rviews@lg.micemn.net C ********************************************************************** MICE MN BGP Route Views http://www.micemn.net/ This router has views of the full routing table from the route reflectors of the MICEMN peering point in Minneapolis, MN, USA. The list of participants are located at http://www.micemn.net/participants.html Login with username 'rviews' to access the router via telnet/ssh. ********************************************************************** micemn-lg>show ip route Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2 i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2 ia - IS-IS inter area, * - candidate default, U - per-user static route o - ODR, P - periodic downloaded static route Gateway of last resort is 216.250.183.14 to network 0.0.0.0 B 204.221.17.0/24 [20/25] via 206.108.255.121, 2d20h B 203.221.22.0/24 [20/474] via 206.108.255.52, 3w1d B 192.170.106.0/24 [20/474] via 206.108.255.52, 7w0d B 199.16.214.0/24 [20/95] via 206.108.255.52, 2w0d B 194.50.241.0/24 [20/1265] via 206.108.255.52, 5d19h B 202.70.142.0/24 [20/474] via 206.108.255.52, 3w1d B 202.49.249.0/24 [20/260] via 206.108.255.52, 7w0d B 196.223.25.0/24 [20/960] via 206.108.255.52, 1d23h B 203.18.218.0/24 [20/474] via 206.108.255.52, 3w1d B 202.154.83.0/24 [20/474] via 206.108.255.52, 7w0d B 203.190.112.0/24 [20/1970] via 206.108.255.52, 1d07h B 199.5.199.0/24 [20/90] via 206.108.255.52, 3w1d B 208.66.148.0/24 [20/308] via 206.108.255.52, 5w3d B 203.142.67.0/24 [20/1970] via 206.108.255.52, 17:42:42 B 199.96.161.0/24 [20/265] via 206.108.255.52, 1d14h B 192.189.123.0/24 [20/81] via 206.108.255.52, 4w3d B 192.83.149.0/24 [20/482] via 206.108.255.52, 2w3d ... -- Doug McIntyre <merlyn@iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades
Yeah, that seems like a bad idea. Generally speaking, folks should never really be carrying the MICE /24 in their IGP’s anyway. It’s a bad idea, and can be harmful. Not carrying it (and using next-hop-self) protects both you and MICE. The IXP prefix shouldn’t, in theory, really be reachable from any device not directly connected in to that /24. Does MICE itself have general use transit available for website, OOB, graphing servers, etc, where this LG (or at least 1 leg of it) could live instead? -- Andrew Hoyos hoyosa@gmail.com
On Nov 3, 2017, at 10:30 AM, Steve Howard <showard@paulbunyan.net> wrote:
Note that the IP address for the Looking Glass is within the MICE IP space and probably does not have connectivity to the global internet. Perhaps something to look at in the future?
On 11/03/2017 07:39 AM, Doug McIntyre wrote:
On Fri, Nov 03, 2017 at 09:15:09AM +0000, Frank Bulk wrote:
Is the MICE Looking Glass down? When I telnet or SSH to it, I get no prompt.
Hmm, doesn't seem to be. Works for me. (both ssh & telnet). Which hostname are you using?
$ ssh rviews@lg.micemn.net C
**********************************************************************
MICE MN BGP Route Views
This router has views of the full routing table from the route reflectors
of the MICEMN peering point in Minneapolis, MN, USA. The list of participants are located at http://www.micemn.net/participants.html
Login with username 'rviews' to access the router via telnet/ssh. **********************************************************************
micemn-lg>show ip route Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2 i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2 ia - IS-IS inter area, * - candidate default, U - per-user static route o - ODR, P - periodic downloaded static route
Gateway of last resort is 216.250.183.14 to network 0.0.0.0
B 204.221.17.0/24 [20/25] via 206.108.255.121, 2d20h B 203.221.22.0/24 [20/474] via 206.108.255.52, 3w1d B 192.170.106.0/24 [20/474] via 206.108.255.52, 7w0d B 199.16.214.0/24 [20/95] via 206.108.255.52, 2w0d B 194.50.241.0/24 [20/1265] via 206.108.255.52, 5d19h B 202.70.142.0/24 [20/474] via 206.108.255.52, 3w1d B 202.49.249.0/24 [20/260] via 206.108.255.52, 7w0d B 196.223.25.0/24 [20/960] via 206.108.255.52, 1d23h B 203.18.218.0/24 [20/474] via 206.108.255.52, 3w1d B 202.154.83.0/24 [20/474] via 206.108.255.52, 7w0d B 203.190.112.0/24 [20/1970] via 206.108.255.52, 1d07h B 199.5.199.0/24 [20/90] via 206.108.255.52, 3w1d B 208.66.148.0/24 [20/308] via 206.108.255.52, 5w3d B 203.142.67.0/24 [20/1970] via 206.108.255.52, 17:42:42 B 199.96.161.0/24 [20/265] via 206.108.255.52, 1d14h B 192.189.123.0/24 [20/81] via 206.108.255.52, 4w3d B 192.83.149.0/24 [20/482] via 206.108.255.52, 2w3d
...
To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
On Fri, Nov 03, 2017 at 11:01:49AM -0500, Andrew Hoyos wrote:
Does MICE itself have general use transit available for website, OOB, graphing servers, etc, where this LG (or at least 1 leg of it) could live instead?
ipHouse has donated some transit for MICE use in the past. It can still keep doing that if this is desired to be moved to a transitable IP address. -- Doug McIntyre <merlyn@iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades
Seems to me that putting a port on the LG server on the same network as the MICE web site wouldn’t be a bad plan if there’s appropriate physical proximity to make this easy. Owen
On Nov 3, 2017, at 10:30 , Doug McIntyre <merlyn@IPHOUSE.NET> wrote:
On Fri, Nov 03, 2017 at 11:01:49AM -0500, Andrew Hoyos wrote:
Does MICE itself have general use transit available for website, OOB, graphing servers, etc, where this LG (or at least 1 leg of it) could live instead?
ipHouse has donated some transit for MICE use in the past. It can still keep doing that if this is desired to be moved to a transitable IP address. -- Doug McIntyre <merlyn@iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades
On Thursday, November 9, 2017 1:02pm, "DeLong, Owen" <00000005a669d12e-dmarc-request@LISTS.IPHOUSE.NET> said:
Seems to me that putting a port on the LG server on the same network as the MICE web site wouldn’t be a bad plan if there’s appropriate physical proximity to make this easy.
Owen
The MICE web site hosting is donated/provided by us, but we are not directly on the exchange, our connection to MICE is provided by IPHouse's peering on MICE. So I don't see that working for the LG. -- Nevin Lyne -- Founder & Director of Technology -- Arcustech, LLC. - arcustech.com -- Gippy's Internet Solutions, LLC. - enginehosting.com
There is an old Cisco router in place now as the LG router. If a network topology change is being considered for the router, it seems like it would be a good time to swap over the *new* router, the one Jeremy and I mounted (less old hardware, less old IOS, and a bit more beefy hardware specs) a few months ago into the MICE cabinet with essentially a duplicate config. It can obviously handle multi-homing so one gig interface could be on the MICE network (as it currently sits) and one gig interface could go somewhere else (eg iphouse, USI, etc) with full Internet reachability. Especially given the bandwidth needs of such a router are quite minimal, I doubt anyone would have problems with donation. Heck, could even spin up a separate MICE VLAN for this second interface in order to just use existing cross-connects if so desired. Side note, changing out the router may require a few tweaks to the current traffic graphing scripts used for BGP route collections and what not, possibly other things/record keeping might be needed as well: DNS records, device/network documentation, some ACL's on the router for the possible new Interface being used, other things my tired brain isn't conceiving at the moment, etc. ________________________________________ From: MICE Discuss [MICE-DISCUSS@LISTS.IPHOUSE.NET] on behalf of Nevin Lyne [nevin@ENGINEHOSTING.COM] Sent: Thursday, November 09, 2017 1:14 PM To: MICE-DISCUSS@LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Looking glass On Thursday, November 9, 2017 1:02pm, "DeLong, Owen" <00000005a669d12e-dmarc-request@LISTS.IPHOUSE.NET> said:
Seems to me that putting a port on the LG server on the same network as the MICE web site wouldn’t be a bad plan if there’s appropriate physical proximity to make this easy.
Owen
The MICE web site hosting is donated/provided by us, but we are not directly on the exchange, our connection to MICE is provided by IPHouse's peering on MICE. So I don't see that working for the LG. -- Nevin Lyne -- Founder & Director of Technology -- Arcustech, LLC. - arcustech.com -- Gippy's Internet Solutions, LLC. - enginehosting.com
That would be great if a *new* router could be put in place. The old one wouldn't have to be turned down until the graphing stuff is all worked out with the new one. Frank -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Justin Krejci Sent: Thursday, November 09, 2017 11:04 PM To: MICE-DISCUSS@LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Looking glass There is an old Cisco router in place now as the LG router. If a network topology change is being considered for the router, it seems like it would be a good time to swap over the *new* router, the one Jeremy and I mounted (less old hardware, less old IOS, and a bit more beefy hardware specs) a few months ago into the MICE cabinet with essentially a duplicate config. It can obviously handle multi-homing so one gig interface could be on the MICE network (as it currently sits) and one gig interface could go somewhere else (eg iphouse, USI, etc) with full Internet reachability. Especially given the bandwidth needs of such a router are quite minimal, I doubt anyone would have problems with donation. Heck, could even spin up a separate MICE VLAN for this second interface in order to just use existing cross-connects if so desired. Side note, changing out the router may require a few tweaks to the current traffic graphing scripts used for BGP route collections and what not, possibly other things/record keeping might be needed as well: DNS records, device/network documentation, some ACL's on the router for the possible new Interface being used, other things my tired brain isn't conceiving at the moment, etc. ________________________________________ From: MICE Discuss [MICE-DISCUSS@LISTS.IPHOUSE.NET] on behalf of Nevin Lyne [nevin@ENGINEHOSTING.COM] Sent: Thursday, November 09, 2017 1:14 PM To: MICE-DISCUSS@LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Looking glass On Thursday, November 9, 2017 1:02pm, "DeLong, Owen" <00000005a669d12e-dmarc-request@LISTS.IPHOUSE.NET> said:
Seems to me that putting a port on the LG server on the same network as the MICE web site wouldn't be a bad plan if there's appropriate physical proximity to make this easy.
Owen
The MICE web site hosting is donated/provided by us, but we are not directly on the exchange, our connection to MICE is provided by IPHouse's peering on MICE. So I don't see that working for the LG. -- Nevin Lyne -- Founder & Director of Technology -- Arcustech, LLC. - arcustech.com -- Gippy's Internet Solutions, LLC. - enginehosting.com
participants (7)
-
Andrew Hoyos -
DeLong, Owen -
Doug McIntyre -
Frank Bulk -
Justin Krejci -
Nevin Lyne -
Steve Howard