To elaborate, after enabling ldpd with -vvvv I have observed the
following in the log output:
Mar 3 00:58:37 mpls-gw ldpd[77048]: nbr_fsm: event SESSION CLOSE
resulted in action CLOSE SESSION and changing state for lsr-id
100.92.64.68 from OPERATIONAL to PRESENT
Mar 3 00:58:37 mpls-gw ldpd[77048]: session_close: closing session
with lsr-id 100.92.64.68
Mar 3 00:58:37 mpls-gw ldpd[9902]: label decision engine exiting
Mar 3 00:58:37 mpls-gw ldpd[54245]: kernel routing table decoupled
Mar 3 00:58:37 mpls-gw ldpd[54245]: waiting for children to terminate
Mar 3 00:58:37 mpls-gw ldpd[54245]: ldp engine terminated; signal 10
Mar 3 00:58:37 mpls-gw ldpd[54245]: terminating
On Sun, Mar 3, 2019 at 12:32 AM Henry Bonath <he...@thebonaths.com> wrote:
>
> Hello, I am still working through some issues with trying to use
> OpenBSD as a Virtual MPLS PE in a multi-tenant hosted IaaS
> environment.
>
> I am running OpenBSD 6.4 in a Hyper-V environment.
>
> I recently started seeing one of my LDP adjacencies flapping, so I
> replace that particular P device with a Cisco ASR 920. So currently,
> my OpenBSD machine is OSPF and LDP Neighbors with the ASR 920, which
> connects to a provider circuit, and then terminates to a Cisco router
> at the customer premise running as a PE with a VRF connecting to the
> CE.
>
> Now, I am getting a crash in LDP happening after about 15 minutes:
> ldp engine terminated; signal 10 shows up in /var/log/messages
>
> here's my ldpd.conf:
> =====================
> router-id 100.92.127.120
>
> address-family ipv4 {
> interface hvn0
> }
> =====================
>
> Thanks in advance!
