December 2016 - mice-discuss - lists.micemn.net

Re: RR#2 cable?

by Justin Krejci

Assuming it is the same problem as before, does it just need a new SFP or a new RJ45 end on the cable? US Internet would be happy to donate either as needed. ________________________________________ From: MICE Discuss [MICE-DISCUSS(a)LISTS.IPHOUSE.NET] on behalf of Doug McIntyre [merlyn(a)IPHOUSE.NET] Sent: Monday, December 19, 2016 5:55 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] RR#2 cable? Sure, in the MICE cabinet (which I'm not sure of the number, it is in the row parallel against the back wall in Suite 100 farthest way from the entry door, in the top of a 1/3rd cabinet with MICE name on a label..) On the EX4550 switch (there's only one EX4550 switch, it is the 1U fiber switch), in port ge-2/0/0 (ie. the first port), is a copper SFP (again, the only one there is). All that needs to happen is to push that copper cross-connect in, the spring action has probably pushed it just a little too far out for good contact. That is what it was last time. And I think in general we should probably move that copper connection back to the copper switches, but for now, just pushing it in would be good to go. On Mon, Dec 19, 2016 at 05:42:33PM -0600, Dean Bahls wrote: > We have someone going down there in about an hour or two. He's never been > in that cabinet so if you have VERY EXPLICIT instructions, we can have him > do it. > > Lemme know. > > Dean > > > -----Original Message----- > From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Doug > McIntyre > Sent: Monday, December 19, 2016 5:37 PM > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > Subject: [MICE-DISCUSS] RR#2 cable? > > Anybody close to 511 today? > > Looks like the cable has snaked its way out again for RR#2. > > Dec 19 17:04:19 micemn-02 kernel: bge1: link state changed to DOWN > > The machine is up and talking back on the mgmt link. It is link down on both > the switch and the machine for the link into the switch stack. > > I'm sure if somebody goes and pushes on the cable again it'll be link up. > > Looks like that cable and that copper-SFP aren't too compatico. > It might be better to not have switch diversity for them. > > -- > Doug McIntyre <merlyn(a)iphouse.net> > ~.~ ipHouse ~.~ > Network Engineer/Provisioning/Jack of all Trades -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

Dec. 19, 2016

Re: RR#2 cable?

by Doug McIntyre

Sure, in the MICE cabinet (which I'm not sure of the number, it is in the row parallel against the back wall in Suite 100 farthest way from the entry door, in the top of a 1/3rd cabinet with MICE name on a label..) On the EX4550 switch (there's only one EX4550 switch, it is the 1U fiber switch), in port ge-2/0/0 (ie. the first port), is a copper SFP (again, the only one there is). All that needs to happen is to push that copper cross-connect in, the spring action has probably pushed it just a little too far out for good contact. That is what it was last time. And I think in general we should probably move that copper connection back to the copper switches, but for now, just pushing it in would be good to go. On Mon, Dec 19, 2016 at 05:42:33PM -0600, Dean Bahls wrote: > We have someone going down there in about an hour or two. He's never been > in that cabinet so if you have VERY EXPLICIT instructions, we can have him > do it. > > Lemme know. > > Dean > > > -----Original Message----- > From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Doug > McIntyre > Sent: Monday, December 19, 2016 5:37 PM > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > Subject: [MICE-DISCUSS] RR#2 cable? > > Anybody close to 511 today? > > Looks like the cable has snaked its way out again for RR#2. > > Dec 19 17:04:19 micemn-02 kernel: bge1: link state changed to DOWN > > The machine is up and talking back on the mgmt link. It is link down on both > the switch and the machine for the link into the switch stack. > > I'm sure if somebody goes and pushes on the cable again it'll be link up. > > Looks like that cable and that copper-SFP aren't too compatico. > It might be better to not have switch diversity for them. > > -- > Doug McIntyre <merlyn(a)iphouse.net> > ~.~ ipHouse ~.~ > Network Engineer/Provisioning/Jack of all Trades -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

Dec. 19, 2016

Re: RR#2 cable?

by Dean Bahls

We have someone going down there in about an hour or two. He's never been in that cabinet so if you have VERY EXPLICIT instructions, we can have him do it. Lemme know. Dean -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Doug McIntyre Sent: Monday, December 19, 2016 5:37 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] RR#2 cable? Anybody close to 511 today? Looks like the cable has snaked its way out again for RR#2. Dec 19 17:04:19 micemn-02 kernel: bge1: link state changed to DOWN The machine is up and talking back on the mgmt link. It is link down on both the switch and the machine for the link into the switch stack. I'm sure if somebody goes and pushes on the cable again it'll be link up. Looks like that cable and that copper-SFP aren't too compatico. It might be better to not have switch diversity for them. -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

Dec. 19, 2016

RR#2 cable?

by Doug McIntyre

Anybody close to 511 today? Looks like the cable has snaked its way out again for RR#2. Dec 19 17:04:19 micemn-02 kernel: bge1: link state changed to DOWN The machine is up and talking back on the mgmt link. It is link down on both the switch and the machine for the link into the switch stack. I'm sure if somebody goes and pushes on the cable again it'll be link up. Looks like that cable and that copper-SFP aren't too compatico. It might be better to not have switch diversity for them. -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

Dec. 19, 2016

UG 22 Minutes

by Richard Laager

Draft minutes available here: http://micemn.net/files/MICE%20UG%2022%20-%20Minutes.pdf If you have any corrections, please let me know. -- Richard

Dec. 19, 2016

Re: MICE UG Reminder

by Richard Laager

On 12/12/2016 10:51 AM, Jason Hanke wrote: > The MICE Users Group is Wednesday. > > There is a proposal for new port fees on the docket. > > Please RSVP here: > > https://www.facebook.com/events/179450035795693/ I have attached the agenda for UG 22 and the minutes from UG 21. Remote Conferencing: 952-562-5400 passcode MICE (6423) -- Richard

Dec. 12, 2016

Re: MICE UG Reminder

by Jeremy Lumby

I do not have a Facebook account to RSVP, and clicking on the link asks me to sign in, however count me as being there. From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Jason Hanke Sent: Monday, December 12, 2016 10:51 AM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] MICE UG Reminder The MICE Users Group is Wednesday. There is a proposal for new port fees on the docket. Please RSVP here: https://www.facebook.com/events/179450035795693/ -- Jay Hanke CTO Neutral Path Communications 3 Civic Center Plaza, Suite 204 Mankato, MN 56001 (507) 327-2398 mobile jayhanke(a)neutralpath.net 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

Dec. 12, 2016

MICE UG Reminder

by Jason Hanke

The MICE Users Group is Wednesday. There is a proposal for new port fees on the docket. Please RSVP here: https://www.facebook.com/events/179450035795693/ -- Jay Hanke CTO Neutral Path Communications 3 Civic Center Plaza, Suite 204 Mankato, MN 56001 (507) 327-2398 mobile jayhanke(a)neutralpath.net www.neutralpath.net

Dec. 12, 2016

Re: MN VoIP Remote Switch

by Doug McIntyre

On Fri, Dec 09, 2016 at 10:07:03AM -0600, Jason Hanke wrote: > Please allocate xe-2/0/7 to the MN VoIP remote switch. Per the new policy > for remote switches, please provision the initial port as a single member > LAG. Sure, all set, allocated LAG group ae15 for this, and have xe-2/0/7 made to be the single member of this LAG. -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

Dec. 9, 2016

MN VoIP Remote Switch

by Jason Hanke

Please allocate xe-2/0/7 to the MN VoIP remote switch. Per the new policy for remote switches, please provision the initial port as a single member LAG. Welcome aboard! -- Jay Hanke CTO Neutral Path Communications 3 Civic Center Plaza, Suite 204 Mankato, MN 56001 (507) 327-2398 mobile jayhanke(a)neutralpath.net www.neutralpath.net

Dec. 9, 2016