Re: [Ubnt_users] upgrading edgemax from 1.7 to 1.8.5 OSPF stops working

[Nathan Babcock]

This did in fact solve my issue.  Verified as of 20 minutes ago. Thank 
you again.



On 7/30/2016 11:49 PM, jesse.dup...@celeritycorp.net wrote:


Glad to help!

Get Outlook for Android <https://aka.ms/ghei36>




On Sat, Jul 30, 2016 at 11:47 PM -0600, <nath...@sswireless.net 
<mailto:nath...@sswireless.net>> wrote:



Jesse,

Thank you for the second look.  That solved my issue.  I
overlooked that probably 20 times as i was trying to understand
what was wrong.  I have now looked at 4 more routers and all their
links and as is the case with this one, 1.7 apparently ignores the
md5 authentication.  I will be disabling this throughout my
network prior to upgrading.  This created a fair amount of
frustration for me.

*- Original Message -*
*From:* jesse.dup...@celeritycorp.net
[mailto:jesse.dup...@celeritycorp.net]
*To:* Ubiquiti Users Group ubnt_users@wispa.org
*Sent:* Sun, 31 Jul 2016 04:37:33 + (UTC)
    *Subject:* Re: [Ubnt_users] upgrading edgemax from 1.7 to 1.8.5
OSPF stops working

Said differently, even though .13 is configured for it, the hello
packet doesn't appear to be reflecting that config.

Get Outlook for Android <https://aka.ms/ghei36>




On Sat, Jul 30, 2016 at 10:27 PM -0600, "Nathan Babcock"
<nath...@sswireless.net> wrote:

13 adn 14 are set to MD5.  Just reverified this.


On 7/30/2016 10:20 PM, Jesse Dupont wrote:

It looks like there is an Authentication Type mismatch.
.13 is set to none whereas .14 is set to MD5.

On Sat, Jul 30, 2016 at 9:49 PM, <nath...@sswireless.net>
wrote:

Good evening.

We had this happen when we reloaded a router at an
active site after a dhcp issue, and we are in the
process of bring up a new site and figured we would
try it on a fresh router without any risk of bringing
a customer down.

We loaded the router with 1.7, as this is the
production firmware we are running across all routers
in our network presently.  Completed config, ospf is
working everything is behaving as expected. Backup
config and then loaded 1.8.5.  As soon as router
reboots, it is no longer accessible.  From the next
router in line, i can ping public interface of new
router, but cannot do anything else(This most likely
due to firewall rules we have in place).  Router is
online, but ospf is no longer working. It is no longer
listed as a registered neighbor and in fact appears
that ospf is turned off as a whole.

Last time we did this on the production router, it was
available locally but ospf did not work.  It appears
this is the case here as well.  Any help would be
greatly appreciated as we need to upgrade our entire
infrastructure to take advantage of the MPLS
configurations for an upcoming project for a
customer.  Thank you in advance!

So to further this, i am working at the site and
trying to resolve this, so far to no end.

Here is th ospf database:

OSPF Router with ID (199.83.117.14) (Process ID 0 VRF
default)
Router Link States (Area 0.0.0.0)

Link ID ADV Router Age Seq# CkSum Link count
199.83.117.14 199.83.117.14 378 0x8005 0xbcad 3

show ip ospf interface eth1
eth1 is up, line protocol is up
Internet Address 199.83.117.14/30
<http://199.83.117.14/30>, Area 0.0.0.0, MTU 1500
Process ID 0, VRF (default), Router ID 199.83.117.14,
Network Type BROADCAST, Cost: 10
Transmit Delay is 1 sec, State DR, Priority 1, TE
Metric 10
Designated Router (ID) 199.83.117.14, Interface
Address 199.83.117.14
No backup designated router on this network
Timer intervals configured, Hello 10, Dead 40, Wait
40, Retransmit 5
Hello due in 00:00:05
Neighbor Count is 0, Adjacent neighbor count is 0
Crypt Sequence Number is 185
Hello received 0 sent 97, DD received 0 sent 0
LS-Req received 0 sent 0, LS-Upd received 0 sent 0
LS-Ack received 0 sent 0, Discarded 0
Message-digest authentication, using default key-id 0

set protocols ospf area 0.0.0.0 area-type normal
set protocols ospf area 0.0.0.0 authentication md5
   

Re: [Ubnt_users] upgrading edgemax from 1.7 to 1.8.5 OSPF stops working

[Scott Lambert]

md5 key-id 0?

I've had issues with EdgeOS when it was configured for the correct md5 key, on 
a different key-id.  Usually in multi-vendor situations.  Try setting up key-id 
1 and 10.

On July 30, 2016 10:49:04 PM CDT, nath...@sswireless.net wrote:
>
>Good evening.
>
>
>
>We had this happen when we reloaded a router at an active site after a
>dhcp issue, and we are in the process of bring up a new site and
>figured we would try it on a fresh router without any risk of bringing
>a customer down.
>
>
>
>We loaded the router with 1.7, as this is the production firmware we
>are running across all routers in our network presently.  Completed
>config, ospf is working everything is behaving as expected.  Backup
>config and then loaded 1.8.5.  As soon as router reboots, it is no
>longer accessible.  From the next router in line, i can ping public
>interface of new router, but cannot do anything else(This most likely
>due to firewall rules we have in place).  Router is online, but ospf is
>no longer working.  It is no longer listed as a registered neighbor and
>in fact appears that ospf is turned off as a whole.
>
>
>
>Last time we did this on the production router, it was available
>locally but ospf did not work.  It appears this is the case here as
>well.  Any help would be greatly appreciated as we need to upgrade our
>entire infrastructure to take advantage of the MPLS configurations for
>an upcoming project for a customer.  Thank you in advance!
>
>
>
>So to further this, i am working at the site and trying to resolve
>this, so far to no end.
>
>
>
>Here is th ospf database:
>
>OSPF Router with ID (199.83.117.14) (Process ID 0 VRF default)
>Router Link States (Area 0.0.0.0)
>
>Link ID ADV Router Age Seq# CkSum Link count
>199.83.117.14 199.83.117.14 378 0x8005 0xbcad 3
>
>
>
>
>
>show ip ospf interface eth1
>eth1 is up, line protocol is up
>Internet Address 199.83.117.14/30, Area 0.0.0.0, MTU 1500
>Process ID 0, VRF (default), Router ID 199.83.117.14, Network Type
>BROADCAST, Cost: 10
>Transmit Delay is 1 sec, State DR, Priority 1, TE Metric 10
>Designated Router (ID) 199.83.117.14, Interface Address 199.83.117.14
>No backup designated router on this network
>Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
>Hello due in 00:00:05
>Neighbor Count is 0, Adjacent neighbor count is 0
>Crypt Sequence Number is 185
>Hello received 0 sent 97, DD received 0 sent 0
>LS-Req received 0 sent 0, LS-Upd received 0 sent 0
>LS-Ack received 0 sent 0, Discarded 0
>Message-digest authentication, using default key-id 0
>
>
>
>
>
>set protocols ospf area 0.0.0.0 area-type normal
>set protocols ospf area 0.0.0.0 authentication md5
>set protocols ospf area 0.0.0.0 network 199.83.117.12/30
>set protocols ospf area 0.0.0.0 network 172.16.106.0/24
>set protocols ospf area 0.0.0.0 network 199.83.117.128/25
>set protocols ospf parameters abr-type cisco
>set protocols ospf parameters router-id 199.83.117.14
>
>
>
>packet capture of ospf on the eth1 interface:
>
>16:28:25.895751 IP (tos 0xc0, ttl 1, id 46663, offset 0, flags [none],
>proto OSPF (89), length 64)
>199.83.117.13  224.0.0.5: OSPFv2, Hello, length 44
>Router-ID 74.116.132.65, Backbone Area, Authentication Type: none (0)
>Options [External]
>Hello Timer 10s, Dead Timer 40s, Mask 255.255.255.252, Priority 1
>Designated Router 199.83.117.13
>16:28:31.569879 IP (tos 0xc0, ttl 1, id 9546, offset 0, flags [DF],
>proto OSPF (89), length 80)
>199.83.117.14  224.0.0.5: OSPFv2, Hello, length 44
>Router-ID 199.83.117.129, Backbone Area, Authentication Type: MD5 (2)
>Key-ID: 0, Auth-Length: 16, Crypto Sequence Number: 0x053a
>Options [External]
>Hello Timer 10s, Dead Timer 40s, Mask 255.255.255.252, Priority 1
>Designated Router 199.83.117.14
>
>
>
>No idea why this isnt working.
>
>
>
>Also checked ps aux and it shows:
>
>root 2126 0.0 0.1 6932 2872 ? Ss 16:02 0:00 /usr/sbin/ospfd -d -P 0
>
>
>
>This thing is just dead in the water...
>
>Any help or guidance would be greatly appreciated.  Thank you.
>
>
>
>
>___
>Ubnt_users mailing list
>Ubnt_users@wispa.org
>http://lists.wispa.org/mailman/listinfo/ubnt_users

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.___
Ubnt_users mailing list
Ubnt_users@wispa.org
http://lists.wispa.org/mailman/listinfo/ubnt_users

Re: [Ubnt_users] upgrading edgemax from 1.7 to 1.8.5 OSPF stops working

[jesse . dupont]

Glad to help!


Get Outlook for Android






On Sat, Jul 30, 2016 at 11:47 PM -0600, <nath...@sswireless.net> wrote:











Jesse,

Thank you for the second look.  That solved my issue.  I overlooked that 
probably 20 times as i was trying to understand what was wrong.  I have now 
looked at 4 more routers and all their links and as is the case with this one, 
1.7 apparently ignores the md5 authentication.  I will be disabling this 
throughout my network prior to upgrading.  This created a fair amount of 
frustration for me.  

- Original Message -
 From: jesse.dup...@celeritycorp.net [mailto:jesse.dup...@celeritycorp.net]
 To: Ubiquiti Users Group ubnt_users@wispa.org
 Sent: Sun, 31 Jul 2016 04:37:33 + (UTC)
 Subject: Re: [Ubnt_users] upgrading edgemax from 1.7 to 1.8.5 OSPF stops 
working




Said differently, even though .13 is configured for it, the hello packet 
doesn't appear to be reflecting that config.


Get Outlook for Android




On Sat, Jul 30, 2016 at 10:27 PM -0600, "Nathan Babcock" 
<nath...@sswireless.net> wrote:
 





13 adn 14 are set to MD5.  Just reverified this.


On 7/30/2016 10:20 PM, Jesse Dupont wrote:

It looks like there is an Authentication Type mismatch. .13 is set to none 
whereas .14 is set to MD5.


On Sat, Jul 30, 2016 at 9:49 PM, <nath...@sswireless.net> wrote:




Good evening.  


 


We had this happen when we reloaded a router at an active site after a dhcp 
issue, and we are in the process of bring up a new site and figured we would 
try it on a fresh router without any risk of bringing a customer down.  


 


We loaded the router with 1.7, as this is the production firmware we are 
running across all routers in our network presently.  Completed config, ospf is 
working everything is behaving as expected.  Backup config and then loaded 
1.8.5.  As soon as router reboots, it is no longer accessible.  From the next 
router in line, i can ping public interface of new router, but cannot do 
anything else(This most likely due to firewall rules we have in place).  Router 
is online, but ospf is no longer working.  It is no longer listed as a 
registered neighbor and in fact appears that ospf is turned off as a whole.  


 


Last time we did this on the production router, it was available locally but 
ospf did not work.  It appears this is the case here as well.  Any help would 
be greatly appreciated as we need to upgrade our entire infrastructure to take 
advantage of the MPLS configurations for an upcoming project for a customer.  
Thank you in advance!
 


So to further this, i am working at the site and trying to resolve this, so far 
to no end.


 


Here is th ospf database:


OSPF Router with ID (199.83.117.14) (Process ID 0 VRF default)
 Router Link States (Area 0.0.0.0)


Link ID ADV Router Age Seq# CkSum Link count
 199.83.117.14 199.83.117.14 378 0x8005 0xbcad 3


 


 


show ip ospf interface eth1
 eth1 is up, line protocol is up
 Internet Address 199.83.117.14/30, Area 0.0.0.0, MTU 1500
 Process ID 0, VRF (default), Router ID 199.83.117.14, Network Type BROADCAST, 
Cost: 10
 Transmit Delay is 1 sec, State DR, Priority 1, TE Metric 10
 Designated Router (ID) 199.83.117.14, Interface Address 199.83.117.14
 No backup designated router on this network
 Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
 Hello due in 00:00:05
 Neighbor Count is 0, Adjacent neighbor count is 0
 Crypt Sequence Number is 185
 Hello received 0 sent 97, DD received 0 sent 0
 LS-Req received 0 sent 0, LS-Upd received 0 sent 0
 LS-Ack received 0 sent 0, Discarded 0
 Message-digest authentication, using default key-id 0


 


 


set protocols ospf area 0.0.0.0 area-type normal
 set protocols ospf area 0.0.0.0 authentication md5
 set protocols ospf area 0.0.0.0 network 199.83.117.12/30
 set protocols ospf area 0.0.0.0 network 172.16.106.0/24
 set protocols ospf area 0.0.0.0 network 199.83.117.128/25
 set protocols ospf parameters abr-type cisco
 set protocols ospf parameters router-id 199.83.117.14


 


packet capture of ospf on the eth1 interface:


16:28:25.895751 IP (tos 0xc0, ttl 1, id 46663, offset 0, flags [none], proto 
OSPF (89), length 64)
 199.83.117.13 > 224.0.0.5: OSPFv2, Hello, length 44
 Router-ID 74.116.132.65, Backbone Area, Authentication Type: none (0)
 Options [External]
 Hello Timer 10s, Dead Timer 40s, Mask 255.255.255.252, Priority 1
 Designated Router 199.83.117.13
 16:28:31.569879 IP (tos 0xc0, ttl 1, id 9546, offset 0, flags [DF], proto OSPF 
(89), length 80)
 199.83.117.14 > 224.0.0.5: OSPFv2, Hello, length 44
 Router-ID 199.83.117.129, Backbone Area, Authentication Type: MD5 (2)
 Key-ID: 0, Auth-Length: 16, Crypto Sequence Number: 0x053a
 Options [External]
 Hello Timer 10s, Dead Timer 40s, Mask 255.255.255.252, Priority 1
 Designated Router 199.83.117.14


 


No idea why this isnt working.


 


Also checked ps aux and it shows:


root 2126 0.0 0.1 6932 2872 ? Ss 

Re: [Ubnt_users] upgrading edgemax from 1.7 to 1.8.5 OSPF stops working

[nathanb]

Jesse,

Thank you for the second look.  That solved my issue.  I overlooked that 
probably 20 times as i was trying to understand what was wrong.  I have now 
looked at 4 more routers and all their links and as is the case with this one, 
1.7 apparently ignores the md5 authentication.  I will be disabling this 
throughout my network prior to upgrading.  This created a fair amount of 
frustration for me.

- Original Message -
 From: jesse.dup...@celeritycorp.net [mailto:jesse.dup...@celeritycorp.net]
 To: Ubiquiti Users Group ubnt_users@wispa.org
 Sent: Sun, 31 Jul 2016 04:37:33 + (UTC)
 Subject: Re: [Ubnt_users] upgrading edgemax from 1.7 to 1.8.5 OSPF stops 
working


Said differently, even though .13 is configured for it, the hello packet 
doesn't appear to be reflecting that config.

Get Outlook for Android




On Sat, Jul 30, 2016 at 10:27 PM -0600, "Nathan Babcock" 
nath...@sswireless.net wrote:



13 adn 14 are set to MD5.  Just reverified this.


On 7/30/2016 10:20 PM, Jesse Dupont wrote:
It looks like there is an Authentication Type mismatch. .13 is set to none 
whereas .14 is set to MD5.


On Sat, Jul 30, 2016 at 9:49 PM, nath...@sswireless.net wrote:

Good evening.



We had this happen when we reloaded a router at an active site after a dhcp 
issue, and we are in the process of bring up a new site and figured we would 
try it on a fresh router without any risk of bringing a customer down.



We loaded the router with 1.7, as this is the production firmware we are 
running across all routers in our network presently.  Completed config, ospf is 
working everything is behaving as expected.  Backup config and then loaded 
1.8.5.  As soon as router reboots, it is no longer accessible.  From the next 
router in line, i can ping public interface of new router, but cannot do 
anything else(This most likely due to firewall rules we have in place).  Router 
is online, but ospf is no longer working.  It is no longer listed as a 
registered neighbor and in fact appears that ospf is turned off as a whole.



Last time we did this on the production router, it was available locally but 
ospf did not work.  It appears this is the case here as well.  Any help would 
be greatly appreciated as we need to upgrade our entire infrastructure to take 
advantage of the MPLS configurations for an upcoming project for a customer.  
Thank you in advance!


So to further this, i am working at the site and trying to resolve this, so far 
to no end.



Here is th ospf database:

OSPF Router with ID (199.83.117.14) (Process ID 0 VRF default)
 Router Link States (Area 0.0.0.0)

Link ID ADV Router Age Seq# CkSum Link count
 199.83.117.14 199.83.117.14 378 0x8005 0xbcad 3





show ip ospf interface eth1
 eth1 is up, line protocol is up
 Internet Address 199.83.117.14/30, Area 0.0.0.0, MTU 1500
 Process ID 0, VRF (default), Router ID 199.83.117.14, Network Type BROADCAST, 
Cost: 10
 Transmit Delay is 1 sec, State DR, Priority 1, TE Metric 10
 Designated Router (ID) 199.83.117.14, Interface Address 199.83.117.14
 No backup designated router on this network
 Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
 Hello due in 00:00:05
 Neighbor Count is 0, Adjacent neighbor count is 0
 Crypt Sequence Number is 185
 Hello received 0 sent 97, DD received 0 sent 0
 LS-Req received 0 sent 0, LS-Upd received 0 sent 0
 LS-Ack received 0 sent 0, Discarded 0
 Message-digest authentication, using default key-id 0





set protocols ospf area 0.0.0.0 area-type normal
 set protocols ospf area 0.0.0.0 authentication md5
 set protocols ospf area 0.0.0.0 network 199.83.117.12/30
 set protocols ospf area 0.0.0.0 network 172.16.106.0/24
 set protocols ospf area 0.0.0.0 network 199.83.117.128/25
 set protocols ospf parameters abr-type cisco
 set protocols ospf parameters router-id 199.83.117.14



packet capture of ospf on the eth1 interface:

16:28:25.895751 IP (tos 0xc0, ttl 1, id 46663, offset 0, flags [none], proto 
OSPF (89), length 64)
 199.83.117.13  224.0.0.5: OSPFv2, Hello, length 44
 Router-ID 74.116.132.65, Backbone Area, Authentication Type: none (0)
 Options [External]
 Hello Timer 10s, Dead Timer 40s, Mask 255.255.255.252, Priority 1
 Designated Router 199.83.117.13
 16:28:31.569879 IP (tos 0xc0, ttl 1, id 9546, offset 0, flags [DF], proto OSPF 
(89), length 80)
 199.83.117.14  224.0.0.5: OSPFv2, Hello, length 44
 Router-ID 199.83.117.129, Backbone Area, Authentication Type: MD5 (2)
 Key-ID: 0, Auth-Length: 16, Crypto Sequence Number: 0x053a
 Options [External]
 Hello Timer 10s, Dead Timer 40s, Mask 255.255.255.252, Priority 1
 Designated Router 199.83.117.14



No idea why this isnt working.



Also checked ps aux and it shows:

root 2126 0.0 0.1 6932 2872 ? Ss 16:02 0:00 /usr/sbin/ospfd -d -P 0



This thing is just dead in the water...

 Any help or guidance would be greatly appreciated.  Thank you.

 ___
 Ubnt_users mailing list
 Ubnt_users

Re: [Ubnt_users] upgrading edgemax from 1.7 to 1.8.5 OSPF stops working

[jesse . dupont]

Said differently, even though .13 is configured for it, the hello packet 
doesn't appear to be reflecting that config.


Get Outlook for Android






On Sat, Jul 30, 2016 at 10:27 PM -0600, "Nathan Babcock" 
 wrote:











  

  
  


13 adn 14 are set to MD5.  Just reverified this.




On 7/30/2016 10:20 PM, Jesse Dupont
  wrote:



  It looks like there is an Authentication Type
mismatch. .13 is set to none whereas .14 is set to MD5.
  

On Sat, Jul 30, 2016 at 9:49 PM, 
  wrote:

  


Good evening.  


 


We had this happen when we reloaded a router at an active
  site after a dhcp issue, and we are in the process of
  bring up a new site and figured we would try it on a fresh
  router without any risk of bringing a customer down.  


 


We loaded the router with 1.7, as this is the production
  firmware we are running across all routers in our network
  presently.  Completed config, ospf is working everything
  is behaving as expected.  Backup config and then loaded
  1.8.5.  As soon as router reboots, it is no longer
  accessible.  From the next router in line, i can ping
  public interface of new router, but cannot do anything
  else(This most likely due to firewall rules we have in
  place).  Router is online, but ospf is no longer working. 
  It is no longer listed as a registered neighbor and in
  fact appears that ospf is turned off as a whole.  


 


Last time we did this on the production router, it was
  available locally but ospf did not work.  It appears this
  is the case here as well.  Any help would be greatly
  appreciated as we need to upgrade our entire
  infrastructure to take advantage of the MPLS
  configurations for an upcoming project for a customer. 
  Thank you in advance!

  




So to further this, i am working at the site and trying
  to resolve this, so far to no end.


 


Here is th ospf database:


OSPF Router with ID (199.83.117.14) (Process ID 0 VRF
  default)

  Router Link States (Area 0.0.0.0)


Link ID ADV Router Age Seq# CkSum Link count

  199.83.117.14 199.83.117.14 378 0x8005 0xbcad 3


 


 


show ip ospf interface eth1

  eth1 is up, line protocol is up

  Internet Address 199.83.117.14/30,
  Area 0.0.0.0, MTU 1500

  Process ID 0, VRF (default), Router ID 199.83.117.14,
  Network Type BROADCAST, Cost: 10

  Transmit Delay is 1 sec, State DR, Priority 1, TE Metric
  10

  Designated Router (ID) 199.83.117.14, Interface Address
  199.83.117.14

  No backup designated router on this network

  Timer intervals configured, Hello 10, Dead 40, Wait 40,
  Retransmit 5

  Hello due in 00:00:05

  Neighbor Count is 0, Adjacent neighbor count is 0

  Crypt Sequence Number is 185

  Hello received 0 sent 97, DD received 0 sent 0

  LS-Req received 0 sent 0, LS-Upd received 0 sent 0

  LS-Ack received 0 sent 0, Discarded 0

  Message-digest authentication, using default key-id 0


 


 


set protocols ospf area 0.0.0.0 area-type normal

  set protocols ospf area 0.0.0.0 authentication md5

  set protocols ospf area 0.0.0.0 network 199.83.117.12/30

  set protocols ospf area 0.0.0.0 network 172.16.106.0/24

  set protocols ospf area 0.0.0.0 network 199.83.117.128/25

  set protocols ospf parameters abr-type cisco

  set protocols ospf parameters router-id 199.83.117.14


 


packet capture of ospf on the eth1 interface:


16:28:25.895751 IP (tos 0xc0, ttl 1, id 46663, offset 0,
  flags [none], proto OSPF (89), length 64)

  199.83.117.13 > 224.0.0.5:
  OSPFv2, Hello, length 44

  Router-ID 74.116.132.65, Backbone Area, Authentication
  Type: none (0)

  Options [External]

  Hello Timer 10s, Dead Timer 40s, Mask 255.255.255.252,
  Priority 1

  Designated Router 199.83.117.13

  16:28:31.569879 IP (tos 0xc0, ttl 1, id 9546, offset 0,
  flags [DF], proto OSPF (89), length 80)

  199.83.117.14 > 224.0.0.5:
  OSPFv2, Hello, length 44

  

Re: [Ubnt_users] upgrading edgemax from 1.7 to 1.8.5 OSPF stops working

[jesse . dupont]

Well, in the packet details you provided, one if them says that auth type is 
none so that's what made we say that. Maybe the upgrade wipes the key and need 
to remove that part of the config and put it in again?


Get Outlook for Android






On Sat, Jul 30, 2016 at 10:27 PM -0600, "Nathan Babcock" 
 wrote:











  

  
  


13 adn 14 are set to MD5.  Just reverified this.




On 7/30/2016 10:20 PM, Jesse Dupont
  wrote:



  It looks like there is an Authentication Type
mismatch. .13 is set to none whereas .14 is set to MD5.
  

On Sat, Jul 30, 2016 at 9:49 PM, 
  wrote:

  


Good evening.  


 


We had this happen when we reloaded a router at an active
  site after a dhcp issue, and we are in the process of
  bring up a new site and figured we would try it on a fresh
  router without any risk of bringing a customer down.  


 


We loaded the router with 1.7, as this is the production
  firmware we are running across all routers in our network
  presently.  Completed config, ospf is working everything
  is behaving as expected.  Backup config and then loaded
  1.8.5.  As soon as router reboots, it is no longer
  accessible.  From the next router in line, i can ping
  public interface of new router, but cannot do anything
  else(This most likely due to firewall rules we have in
  place).  Router is online, but ospf is no longer working. 
  It is no longer listed as a registered neighbor and in
  fact appears that ospf is turned off as a whole.  


 


Last time we did this on the production router, it was
  available locally but ospf did not work.  It appears this
  is the case here as well.  Any help would be greatly
  appreciated as we need to upgrade our entire
  infrastructure to take advantage of the MPLS
  configurations for an upcoming project for a customer. 
  Thank you in advance!

  




So to further this, i am working at the site and trying
  to resolve this, so far to no end.


 


Here is th ospf database:


OSPF Router with ID (199.83.117.14) (Process ID 0 VRF
  default)

  Router Link States (Area 0.0.0.0)


Link ID ADV Router Age Seq# CkSum Link count

  199.83.117.14 199.83.117.14 378 0x8005 0xbcad 3


 


 


show ip ospf interface eth1

  eth1 is up, line protocol is up

  Internet Address 199.83.117.14/30,
  Area 0.0.0.0, MTU 1500

  Process ID 0, VRF (default), Router ID 199.83.117.14,
  Network Type BROADCAST, Cost: 10

  Transmit Delay is 1 sec, State DR, Priority 1, TE Metric
  10

  Designated Router (ID) 199.83.117.14, Interface Address
  199.83.117.14

  No backup designated router on this network

  Timer intervals configured, Hello 10, Dead 40, Wait 40,
  Retransmit 5

  Hello due in 00:00:05

  Neighbor Count is 0, Adjacent neighbor count is 0

  Crypt Sequence Number is 185

  Hello received 0 sent 97, DD received 0 sent 0

  LS-Req received 0 sent 0, LS-Upd received 0 sent 0

  LS-Ack received 0 sent 0, Discarded 0

  Message-digest authentication, using default key-id 0


 


 


set protocols ospf area 0.0.0.0 area-type normal

  set protocols ospf area 0.0.0.0 authentication md5

  set protocols ospf area 0.0.0.0 network 199.83.117.12/30

  set protocols ospf area 0.0.0.0 network 172.16.106.0/24

  set protocols ospf area 0.0.0.0 network 199.83.117.128/25

  set protocols ospf parameters abr-type cisco

  set protocols ospf parameters router-id 199.83.117.14


 


packet capture of ospf on the eth1 interface:


16:28:25.895751 IP (tos 0xc0, ttl 1, id 46663, offset 0,
  flags [none], proto OSPF (89), length 64)

  199.83.117.13 > 224.0.0.5:
  OSPFv2, Hello, length 44

  Router-ID 74.116.132.65, Backbone Area, Authentication
  Type: none (0)

  Options [External]

  Hello Timer 10s, Dead Timer 40s, Mask 255.255.255.252,
  Priority 1

  Designated Router 199.83.117.13

  16:28:31.569879 IP (tos 0xc0, ttl 1, id 9546, offset 0,
  flags [DF], proto OSPF (89), length 80)

  

Re: [Ubnt_users] upgrading edgemax from 1.7 to 1.8.5 OSPF stops working

[Nathan Babcock]

13 adn 14 are set to MD5.  Just reverified this.


On 7/30/2016 10:20 PM, Jesse Dupont wrote:
It looks like there is an Authentication Type mismatch. .13 is set to 
none whereas .14 is set to MD5.


On Sat, Jul 30, 2016 at 9:49 PM, > wrote:


Good evening.

We had this happen when we reloaded a router at an active site
after a dhcp issue, and we are in the process of bring up a new
site and figured we would try it on a fresh router without any
risk of bringing a customer down.

We loaded the router with 1.7, as this is the production firmware
we are running across all routers in our network presently. 
Completed config, ospf is working everything is behaving as

expected.  Backup config and then loaded 1.8.5.  As soon as router
reboots, it is no longer accessible.  From the next router in
line, i can ping public interface of new router, but cannot do
anything else(This most likely due to firewall rules we have in
place).  Router is online, but ospf is no longer working. It is no
longer listed as a registered neighbor and in fact appears that
ospf is turned off as a whole.

Last time we did this on the production router, it was available
locally but ospf did not work.  It appears this is the case here
as well.  Any help would be greatly appreciated as we need to
upgrade our entire infrastructure to take advantage of the MPLS
configurations for an upcoming project for a customer. Thank you
in advance!

So to further this, i am working at the site and trying to resolve
this, so far to no end.

Here is th ospf database:

OSPF Router with ID (199.83.117.14) (Process ID 0 VRF default)
Router Link States (Area 0.0.0.0)

Link ID ADV Router Age Seq# CkSum Link count
199.83.117.14 199.83.117.14 378 0x8005 0xbcad 3

show ip ospf interface eth1
eth1 is up, line protocol is up
Internet Address 199.83.117.14/30 , Area
0.0.0.0, MTU 1500
Process ID 0, VRF (default), Router ID 199.83.117.14, Network Type
BROADCAST, Cost: 10
Transmit Delay is 1 sec, State DR, Priority 1, TE Metric 10
Designated Router (ID) 199.83.117.14, Interface Address 199.83.117.14
No backup designated router on this network
Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
Hello due in 00:00:05
Neighbor Count is 0, Adjacent neighbor count is 0
Crypt Sequence Number is 185
Hello received 0 sent 97, DD received 0 sent 0
LS-Req received 0 sent 0, LS-Upd received 0 sent 0
LS-Ack received 0 sent 0, Discarded 0
Message-digest authentication, using default key-id 0

set protocols ospf area 0.0.0.0 area-type normal
set protocols ospf area 0.0.0.0 authentication md5
set protocols ospf area 0.0.0.0 network 199.83.117.12/30

set protocols ospf area 0.0.0.0 network 172.16.106.0/24

set protocols ospf area 0.0.0.0 network 199.83.117.128/25

set protocols ospf parameters abr-type cisco
set protocols ospf parameters router-id 199.83.117.14

packet capture of ospf on the eth1 interface:

16:28:25.895751 IP (tos 0xc0, ttl 1, id 46663, offset 0, flags
[none], proto OSPF (89), length 64)
199.83.117.13 > 224.0.0.5 : OSPFv2, Hello, length 44
Router-ID 74.116.132.65, Backbone Area, Authentication Type: none (0)
Options [External]
Hello Timer 10s, Dead Timer 40s, Mask 255.255.255.252, Priority 1
Designated Router 199.83.117.13
16:28:31.569879 IP (tos 0xc0, ttl 1, id 9546, offset 0, flags
[DF], proto OSPF (89), length 80)
199.83.117.14 > 224.0.0.5 : OSPFv2, Hello, length 44
Router-ID 199.83.117.129, Backbone Area, Authentication Type: MD5 (2)
Key-ID: 0, Auth-Length: 16, Crypto Sequence Number: 0x053a
Options [External]
Hello Timer 10s, Dead Timer 40s, Mask 255.255.255.252, Priority 1
Designated Router 199.83.117.14

No idea why this isnt working.

Also checked ps aux and it shows:

root 2126 0.0 0.1 6932 2872 ? Ss 16:02 0:00 /usr/sbin/ospfd -d -P 0

This thing is just dead in the water...

Any help or guidance would be greatly appreciated.  Thank you.


___
Ubnt_users mailing list
Ubnt_users@wispa.org 
http://lists.wispa.org/mailman/listinfo/ubnt_users




--

*_Jesse DuPont_*

Owner / Network Architect

email: jesse.dup...@celeritycorp.net 



cell: 605-340-0651

fax: 305-946-0651

Celerity Networks LLC

PO Box 547

Spearfish, SD  57783

Like us! facebook.com/celeritynetworksllc 



cid:273145916@30122011-11FC



___
Ubnt_users mailing list

Re: [Ubnt_users] upgrading edgemax from 1.7 to 1.8.5 OSPF stops working

[Jesse Dupont]

It looks like there is an Authentication Type mismatch. .13 is set to none
whereas .14 is set to MD5.

On Sat, Jul 30, 2016 at 9:49 PM,  wrote:

> Good evening.
>
>
>
> We had this happen when we reloaded a router at an active site after a
> dhcp issue, and we are in the process of bring up a new site and figured we
> would try it on a fresh router without any risk of bringing a customer
> down.
>
>
>
> We loaded the router with 1.7, as this is the production firmware we are
> running across all routers in our network presently.  Completed config,
> ospf is working everything is behaving as expected.  Backup config and then
> loaded 1.8.5.  As soon as router reboots, it is no longer accessible.  From
> the next router in line, i can ping public interface of new router, but
> cannot do anything else(This most likely due to firewall rules we have in
> place).  Router is online, but ospf is no longer working.  It is no longer
> listed as a registered neighbor and in fact appears that ospf is turned off
> as a whole.
>
>
>
> Last time we did this on the production router, it was available locally
> but ospf did not work.  It appears this is the case here as well.  Any help
> would be greatly appreciated as we need to upgrade our entire
> infrastructure to take advantage of the MPLS configurations for an upcoming
> project for a customer.  Thank you in advance!
>
> So to further this, i am working at the site and trying to resolve this,
> so far to no end.
>
>
>
> Here is th ospf database:
>
> OSPF Router with ID (199.83.117.14) (Process ID 0 VRF default)
> Router Link States (Area 0.0.0.0)
>
> Link ID ADV Router Age Seq# CkSum Link count
> 199.83.117.14 199.83.117.14 378 0x8005 0xbcad 3
>
>
>
>
>
> show ip ospf interface eth1
> eth1 is up, line protocol is up
> Internet Address 199.83.117.14/30, Area 0.0.0.0, MTU 1500
> Process ID 0, VRF (default), Router ID 199.83.117.14, Network Type
> BROADCAST, Cost: 10
> Transmit Delay is 1 sec, State DR, Priority 1, TE Metric 10
> Designated Router (ID) 199.83.117.14, Interface Address 199.83.117.14
> No backup designated router on this network
> Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
> Hello due in 00:00:05
> Neighbor Count is 0, Adjacent neighbor count is 0
> Crypt Sequence Number is 185
> Hello received 0 sent 97, DD received 0 sent 0
> LS-Req received 0 sent 0, LS-Upd received 0 sent 0
> LS-Ack received 0 sent 0, Discarded 0
> Message-digest authentication, using default key-id 0
>
>
>
>
>
> set protocols ospf area 0.0.0.0 area-type normal
> set protocols ospf area 0.0.0.0 authentication md5
> set protocols ospf area 0.0.0.0 network 199.83.117.12/30
> set protocols ospf area 0.0.0.0 network 172.16.106.0/24
> set protocols ospf area 0.0.0.0 network 199.83.117.128/25
> set protocols ospf parameters abr-type cisco
> set protocols ospf parameters router-id 199.83.117.14
>
>
>
> packet capture of ospf on the eth1 interface:
>
> 16:28:25.895751 IP (tos 0xc0, ttl 1, id 46663, offset 0, flags [none],
> proto OSPF (89), length 64)
> 199.83.117.13 > 224.0.0.5: OSPFv2, Hello, length 44
> Router-ID 74.116.132.65, Backbone Area, Authentication Type: none (0)
> Options [External]
> Hello Timer 10s, Dead Timer 40s, Mask 255.255.255.252, Priority 1
> Designated Router 199.83.117.13
> 16:28:31.569879 IP (tos 0xc0, ttl 1, id 9546, offset 0, flags [DF], proto
> OSPF (89), length 80)
> 199.83.117.14 > 224.0.0.5: OSPFv2, Hello, length 44
> Router-ID 199.83.117.129, Backbone Area, Authentication Type: MD5 (2)
> Key-ID: 0, Auth-Length: 16, Crypto Sequence Number: 0x053a
> Options [External]
> Hello Timer 10s, Dead Timer 40s, Mask 255.255.255.252, Priority 1
> Designated Router 199.83.117.14
>
>
>
> No idea why this isnt working.
>
>
>
> Also checked ps aux and it shows:
>
> root 2126 0.0 0.1 6932 2872 ? Ss 16:02 0:00 /usr/sbin/ospfd -d -P 0
>
>
>
> This thing is just dead in the water...
>
> Any help or guidance would be greatly appreciated.  Thank you.
>
> ___
> Ubnt_users mailing list
> Ubnt_users@wispa.org
> http://lists.wispa.org/mailman/listinfo/ubnt_users
>
>


-- 

*Jesse DuPont*

Owner / Network Architect

email: jesse.dup...@celeritycorp.net

cell: 605-340-0651

fax: 305-946-0651

Celerity Networks LLC

PO Box 547

Spearfish, SD  57783

Like us!  facebook.com/celeritynetworksllc

[image: cid:273145916@30122011-11FC]
___
Ubnt_users mailing list
Ubnt_users@wispa.org
http://lists.wispa.org/mailman/listinfo/ubnt_users