Monticello FiberNet has pulled up their BGP connection and is getting an "EOF" Error. Can someone please check the config on the Route Servers? Thank you,
On Thu, Aug 28, 2014 at 10:14:39AM -0500, Levi Pederson wrote:
Monticello FiberNet has pulled up their BGP connection and is getting an "EOF" Error. Can someone please check the config on the Route Servers?
I don't have any info about Monticell FiberNet. What's the ASN? Is the gray'd out IPv4 address on the participants page the one you're using? Obviously they aren't configured on the route server end lacking this data. -- Doug McIntyre <merlyn@iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades
Doug, Excellent news. Thought I was going insane! While that may still be up for debate. Info to Follow AS 393466 I am currently using the the IP 206.108.255.108 Thank you, *Levi Pederson* Mankato Networks LLC cell | 612.481.0769 work | 612.787.7392 levipederson@mankatonetworks.net On Thu, Aug 28, 2014 at 10:47 AM, Doug McIntyre <merlyn@iphouse.net> wrote:
On Thu, Aug 28, 2014 at 10:14:39AM -0500, Levi Pederson wrote:
Monticello FiberNet has pulled up their BGP connection and is getting an "EOF" Error. Can someone please check the config on the Route Servers?
I don't have any info about Monticell FiberNet. What's the ASN? Is the gray'd out IPv4 address on the participants page the one you're using?
Obviously they aren't configured on the route server end lacking this data.
-- Doug McIntyre <merlyn@iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades
On Thu, Aug 28, 2014 at 10:50:04AM -0500, Levi Pederson wrote:
Excellent news. Thought I was going insane! While that may still be up for debate. Info to Follow
AS 393466 I am currently using the the IP 206.108.255.108
Okay, route servers are configured for you. The connection is Idle, so you must not be trying to connect right now. Inncidently this is the first 4-byte ASN on the exchange, but I don't think there should be any problems with it. -- Doug McIntyre <merlyn@iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades
Doug, Excellent news Doug. Looks like we're also dealing with an MTU issue. We'll let you know when we're up and passing routes. Thank you, *Levi Pederson* Mankato Networks LLC cell | 612.481.0769 work | 612.787.7392 levipederson@mankatonetworks.net On Thu, Aug 28, 2014 at 12:01 PM, Doug McIntyre <merlyn@iphouse.net> wrote:
On Thu, Aug 28, 2014 at 10:50:04AM -0500, Levi Pederson wrote:
Excellent news. Thought I was going insane! While that may still be up for debate. Info to Follow
AS 393466 I am currently using the the IP 206.108.255.108
Okay, route servers are configured for you. The connection is Idle, so you must not be trying to connect right now.
Inncidently this is the first 4-byte ASN on the exchange, but I don't think there should be any problems with it.
-- Doug McIntyre <merlyn@iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades
Doug, We have fixed the MTU issue on our side. I'm still getting an error stating "unexpected EOF" which indicates a termination after my open packet is sent. Is there an error on your side that would shed some light on this conundrum? Thank you, *Levi Pederson* Mankato Networks LLC cell | 612.481.0769 work | 612.787.7392 levipederson@mankatonetworks.net On Thu, Aug 28, 2014 at 12:01 PM, Doug McIntyre <merlyn@iphouse.net> wrote:
On Thu, Aug 28, 2014 at 10:50:04AM -0500, Levi Pederson wrote:
Excellent news. Thought I was going insane! While that may still be up for debate. Info to Follow
AS 393466 I am currently using the the IP 206.108.255.108
Okay, route servers are configured for you. The connection is Idle, so you must not be trying to connect right now.
Inncidently this is the first 4-byte ASN on the exchange, but I don't think there should be any problems with it.
-- Doug McIntyre <merlyn@iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades
I'm sorry, I had a typo on your IP address, it wasn't what I remembered when typing out the commands. Log showed what you said, and I fixed it up. I get Established now. Sorry for the issue. On Thu, Aug 28, 2014 at 02:11:30PM -0500, Levi Pederson wrote:
We have fixed the MTU issue on our side. I'm still getting an error stating "unexpected EOF" which indicates a termination after my open packet is sent. Is there an error on your side that would shed some light on this conundrum?
Thank you,
*Levi Pederson* Mankato Networks LLC cell | 612.481.0769 work | 612.787.7392 levipederson@mankatonetworks.net
On Thu, Aug 28, 2014 at 12:01 PM, Doug McIntyre <merlyn@iphouse.net> wrote:
On Thu, Aug 28, 2014 at 10:50:04AM -0500, Levi Pederson wrote:
Excellent news. Thought I was going insane! While that may still be up for debate. Info to Follow
AS 393466 I am currently using the the IP 206.108.255.108
Okay, route servers are configured for you. The connection is Idle, so you must not be trying to connect right now.
Inncidently this is the first 4-byte ASN on the exchange, but I don't think there should be any problems with it.
-- Doug McIntyre <merlyn@iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades
-- Doug McIntyre <merlyn@iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades
participants (2)
-
Doug McIntyre -
Levi Pederson