[OpenBGPd <=> Cisco] error in OPEN message, unknown subcode 8

classic Classic list List threaded Threaded
15 messages Options
Reply | Threaded
Open this post in threaded view
|

[OpenBGPd <=> Cisco] error in OPEN message, unknown subcode 8

Laurent Caron (Mobile)
Hi,

I'm trying to establish a peering session with another member of an IX
(France-IX).

On my side I do have 2 OpenBSD (OpenBGPd) boxes.

Config:
group "peering" {
        holdtime                30
        holdtime min            3
        announce                self
        set med                 100
        enforce neighbor-as     yes
        max-prefix              1000
        set community           NO_EXPORT

neighbor    193.105.232.181 {
        descr                   pv4_gw-003_to_ISC
        remote-as               30126
        max-prefix              5
        local-address           193.105.232.145
        announce IPv4           unicast
        announce IPv6           none
    }

neighbor    2001:7f8:54::181    {
        descr                   pv6_gw-003_to_ISC
        remote-as               30126
        max-prefix              5
        local-address           2001:7f8:54::145
        announce IPv4           none
        announce IPv6           unicast
    }
}

In my logs I do observe this:
Oct  9 09:44:40 bgpgw-003 bgpd[17498]: neighbor 193.105.232.181 (pv4_gw-003_to_ISC): state change Idle -> Connect, reason: Start
Oct  9 09:44:40 bgpgw-003 bgpd[17498]: neighbor 193.105.232.181 (pv4_gw-003_to_ISC): state change Connect -> OpenSent, reason: Connection opened
Oct  9 09:44:40 bgpgw-003 bgpd[17498]: neighbor 193.105.232.181 (pv4_gw-003_to_ISC): received notification: error in OPEN message, unknown subcode 8
Oct  9 09:44:40 bgpgw-003 bgpd[17498]: neighbor 193.105.232.181 (pv4_gw-003_to_ISC): state change OpenSent -> Idle, reason: NOTIFICATION received
Oct  9 09:44:43 bgpgw-003 bgpd[17498]: neighbor 2001:7f8:54::181 (pv6_gw-003_to_ISC): state change Idle -> Connect, reason: Start
Oct  9 09:44:43 bgpgw-003 bgpd[17498]: neighbor 2001:7f8:54::181 (pv6_gw-003_to_ISC): state change Connect -> OpenSent, reason: Connection opened
Oct  9 09:44:43 bgpgw-003 bgpd[17498]: neighbor 2001:7f8:54::181 (pv6_gw-003_to_ISC): received notification: error in OPEN message, unknown subcode 8
Oct  9 09:44:43 bgpgw-003 bgpd[17498]: neighbor 2001:7f8:54::181 (pv6_gw-003_to_ISC): state change OpenSent -> Idle, reason: NOTIFICATION received
Oct  9 09:44:44 bgpgw-003 bgpd[17498]: neighbor 2001:7f8:54::181 (pv6_gw-003_to_ISC): state change Idle -> Active, reason: Start
Oct  9 09:44:44 bgpgw-003 bgpd[17498]: neighbor 2001:7f8:54::181 (pv6_gw-003_to_ISC): state change Active -> OpenSent, reason: Connection opened
Oct  9 09:44:44 bgpgw-003 bgpd[17498]: neighbor 2001:7f8:54::181 (pv6_gw-003_to_ISC): state change OpenSent -> OpenConfirm, reason: OPEN message received
Oct  9 09:44:44 bgpgw-003 bgpd[17498]: neighbor 2001:7f8:54::181 (pv6_gw-003_to_ISC): received notification: error in OPEN message, unknown subcode 8
Oct  9 09:44:44 bgpgw-003 bgpd[17498]: neighbor 2001:7f8:54::181 (pv6_gw-003_to_ISC): state change OpenConfirm -> Idle, reason: NOTIFICATION received


On the peer logs we have (peer is a Cisco 7301 running IOS 15.01 shoult
it matter):
Oct  9 2012 18:24:25.731 UTC: BGP: 193.105.232.145 active went from Idle to Active
Oct  9 2012 18:24:25.731 UTC: BGP: 193.105.232.145 open active, local address 193.105.232.181
Oct  9 2012 18:24:25.735 UTC: BGP: ses global 193.105.232.145 (0x6D6FC31C:0) act Remote close.
Oct  9 2012 18:24:25.735 UTC: BGP: ses global 193.105.232.145 (0x6D6FC31C:0) act Reset (Peer closed the session).
Oct  9 2012 18:24:25.735 UTC: BGP: 193.105.232.145 active went from Active to Idle
Oct  9 2012 18:24:25.735 UTC: BGP: nbr global 193.105.232.145 Open active delayed 12288ms (35000ms max, 60% jitter)
Oct  9 2012 18:24:25.735 UTC: BGP: nbr global 193.105.232.145 Active open failed - open timer running

Do you guys (Claudio?) have a clue about it ?

Thanks

Reply | Threaded
Open this post in threaded view
|

Re: [OpenBGPd <=> Cisco] error in OPEN message, unknown subcode 8

Simon Perreault-3
Le 2012-10-10 06:13, Laurent CARON a écrit :
> On my side I do have 2 OpenBSD (OpenBGPd) boxes.

What versions?

> In my logs I do observe this:

A pcap dump would be useful...

> Oct  9 09:44:40 bgpgw-003 bgpd[17498]: neighbor 193.105.232.181 (pv4_gw-003_to_ISC): state change Idle -> Connect, reason: Start
> Oct  9 09:44:40 bgpgw-003 bgpd[17498]: neighbor 193.105.232.181 (pv4_gw-003_to_ISC): state change Connect -> OpenSent, reason: Connection opened
> Oct  9 09:44:40 bgpgw-003 bgpd[17498]: neighbor 193.105.232.181 (pv4_gw-003_to_ISC): received notification: error in OPEN message, unknown subcode 8

FYI, subcode 8 has not yet been assigned by IANA:
http://www.iana.org/assignments/bgp-parameters/bgp-parameters.xml#bgp-parameters-6

...but it is defined in a new draft:
http://tools.ietf.org/html/draft-ietf-idr-bgp-multisession-07#section-5

          8 - Grouping Conflict - values of capability codes used in
          Session Id of the received message cannot be unambiguously
          mapped to a locally configured group

That should provide enough clue to be able to dig at the right place...

Simon
--
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

Reply | Threaded
Open this post in threaded view
|

Re: [OpenBGPd <=> Cisco] error in OPEN message, unknown subcode 8

Laurent Caron (Mobile)
On 10/10/2012 16:40, Simon Perreault wrote:
> What versions?

OpenBSD 5.1 (sorry for not mentionning it).

>
>> In my logs I do observe this:
>
> A pcap dump would be useful...

Here it is:
http://elfe.lncsa.com/get?k=5Rya5Acaq26TqJ9MXG

> FYI, subcode 8 has not yet been assigned by IANA:
> http://www.iana.org/assignments/bgp-parameters/bgp-parameters.xml#bgp-parameters-6
>
>
> ...but it is defined in a new draft:
> http://tools.ietf.org/html/draft-ietf-idr-bgp-multisession-07#section-5
>
>           8 - Grouping Conflict - values of capability codes used in
>           Session Id of the received message cannot be unambiguously
>           mapped to a locally configured group
>
> That should provide enough clue to be able to dig at the right place...

Thanks for the hint.

Reply | Threaded
Open this post in threaded view
|

Re: [OpenBGPd <=> Cisco] error in OPEN message, unknown subcode 8

Simon Perreault-3
Le 2012-10-10 11:51, Laurent CARON a écrit :
>> A pcap dump would be useful...
>
> Here it is:
> http://elfe.lncsa.com/get?k=5Rya5Acaq26TqJ9MXG

The pcap shows that the Cisco box is refusing your OPEN message. It
doesn't like it for some reason. You need to figure out why. Probably
because of the way it's configured. I see no reason to blame either side
so far.

Simon
--
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

Reply | Threaded
Open this post in threaded view
|

Re: [OpenBGPd <=> Cisco] error in OPEN message, unknown subcode 8

Laurent Caron (Mobile)
On 10/10/2012 18:12, Simon Perreault wrote:
> The pcap shows that the Cisco box is refusing your OPEN message. It
> doesn't like it for some reason. You need to figure out why. Probably
> because of the way it's configured. I see no reason to blame either side
> so far.

I've gotten the config on the cisco side which doesn't seem obviously
strange.

  neighbor peer peer-group
  neighbor peer version 4

  neighbor 193.105.232.145 remote-as 49463
  neighbor 193.105.232.145 peer-group peer

address-family ipv4
   neighbor peer send-community
   neighbor peer prefix-list bad-nets-in in
   neighbor peer prefix-list bad-nets-out out
   neighbor peer route-map in-peer in
   neighbor peer route-map out-peer out

route-map in-peer permit 10
  match as-path 190
  set community 3557:340
  set ip next-hop 192.0.2.1

route-map in-peer permit 40
  set community 3557:390

route-map out-peer permit 5
  match ip address prefix-list sys-f-global-nets
  match community 37
  set metric-type internal
  set as-path prepend 3557
  set community no-export

Reply | Threaded
Open this post in threaded view
|

Re: [OpenBGPd <=> Cisco] error in OPEN message, unknown subcode 8

Claudio Jeker
In reply to this post by Laurent Caron (Mobile)
On Wed, Oct 10, 2012 at 05:51:38PM +0200, Laurent CARON wrote:

> On 10/10/2012 16:40, Simon Perreault wrote:
> >What versions?
>
> OpenBSD 5.1 (sorry for not mentionning it).
>
> >
> >>In my logs I do observe this:
> >
> >A pcap dump would be useful...
>
> Here it is:
> http://elfe.lncsa.com/get?k=5Rya5Acaq26TqJ9MXG
>
> >FYI, subcode 8 has not yet been assigned by IANA:
> >http://www.iana.org/assignments/bgp-parameters/bgp-parameters.xml#bgp-parameters-6
> >
> >
> >...but it is defined in a new draft:
> >http://tools.ietf.org/html/draft-ietf-idr-bgp-multisession-07#section-5
> >
> >          8 - Grouping Conflict - values of capability codes used in
> >          Session Id of the received message cannot be unambiguously
> >          mapped to a locally configured group
> >
> >That should provide enough clue to be able to dig at the right place...
>
> Thanks for the hint.

Looking at the pcap I see one strange thing:
17:48:39.910152 193.105.232.181.21798 > 193.105.232.145.179: S [tcp sum ok] 35124087:35124087(0) win 16384 <mss 1460,wscale 0,eol> (DF) [tos 0xc0] [ttl 1] (id 53673, len 48)
17:48:39.910198 193.105.232.145.179 > 193.105.232.181.21798: S [tcp sum ok] 1526797827:1526797827(0) ack 35124088 win 16384 <mss 1460,nop,wscale 3> (DF) (ttl 255, id 63110, len 48)
17:48:39.911212 193.105.232.181.21798 > 193.105.232.145.179: . [tcp sum ok] ack 1 win 16384 (DF) [tos 0xc0] [ttl 1] (id 53674, len 40)
17:48:39.911290 193.105.232.145.179 > 193.105.232.181.21798: F [tcp sum ok] 1:1(0) ack 1 win 2190 (DF) (ttl 64, id 22529, len 40)
17:48:39.912004 193.105.232.181.21798 > 193.105.232.145.179: P [tcp sum ok] 1:59(58) ack 1 win 16384: BGP (OPEN: Version 4, AS #30126, Holdtime 180, ID 192.228.82.16, Option length 29 ((CAP MULTI_PROTOCOL [IPv4 Unicast]) (CAP #128 len 0) (CAP ROUTE_REFRESH) (CAP #131 len 1) (CAP AS4 #30126))) (DF) [tos 0xc0] [ttl 1] (id 53675, len 98)
17:48:39.912023 193.105.232.145.179 > 193.105.232.181.21798: R [tcp sum ok] 1526797828:1526797828(0) win 0 (DF) (ttl 64, id 22749, len 40)
17:48:39.912346 193.105.232.181.21798 > 193.105.232.145.179: . [tcp sum ok] ack 2 win 16384 (DF) [tos 0xc0] [ttl 1] (id 53676, len 40)
17:48:39.912360 193.105.232.145.179 > 193.105.232.181.21798: R [tcp sum ok] 1526797829:1526797829(0) win 0 (DF) (ttl 64, id 50452, len 40)
17:48:39.912980 193.105.232.181.21798 > 193.105.232.145.179: FP [tcp sum ok] 59:59(0) ack 2 win 16384 (DF) [tos 0xc0] [ttl 1] (id 53677, len 40)
17:48:39.912993 193.105.232.145.179 > 193.105.232.181.21798: R [tcp sum ok] 1526797829:1526797829(0) win 0 (DF) (ttl 64, id 29177, len 40)
17:48:39.913417 193.105.232.181.21798 > 193.105.232.145.179: . [tcp sum ok] ack 2 win 16384 (DF) [tos 0xc0] [ttl 1] (id 53678, len 40)
17:48:39.913430 193.105.232.145.179 > 193.105.232.181.21798: R [tcp sum ok] 1526797829:1526797829(0) win 0 (DF) (ttl 64, id 9044, len 40)
 

This connection initiated by the cisco is accepted and immediatly closed.
That looks suspicious (also because nothing is logged in bgpd). Feels like
pf(4) is playing dirty tricks here.
Afterwards the openbgpd initiates the session and the cisco sends back a
NOTIFICATION (maybe because it is still unhappy about the rather
unexpected FIN/RST of the previous session).

If the problem still exists when bgpd is accepting the cisco connection
then we need to have a closer look at the messages.
--
:wq Claudio

Reply | Threaded
Open this post in threaded view
|

Re: [OpenBGPd <=> Cisco] error in OPEN message, unknown subcode 8

Laurent Caron (Mobile)
On 10/10/2012 20:54, Claudio Jeker wrote:

> Looking at the pcap I see one strange thing:
> 17:48:39.910152 193.105.232.181.21798 > 193.105.232.145.179: S [tcp sum ok] 35124087:35124087(0) win 16384 <mss 1460,wscale 0,eol> (DF) [tos 0xc0] [ttl 1] (id 53673, len 48)
> 17:48:39.910198 193.105.232.145.179 > 193.105.232.181.21798: S [tcp sum ok] 1526797827:1526797827(0) ack 35124088 win 16384 <mss 1460,nop,wscale 3> (DF) (ttl 255, id 63110, len 48)
> 17:48:39.911212 193.105.232.181.21798 > 193.105.232.145.179: . [tcp sum ok] ack 1 win 16384 (DF) [tos 0xc0] [ttl 1] (id 53674, len 40)
> 17:48:39.911290 193.105.232.145.179 > 193.105.232.181.21798: F [tcp sum ok] 1:1(0) ack 1 win 2190 (DF) (ttl 64, id 22529, len 40)
> 17:48:39.912004 193.105.232.181.21798 > 193.105.232.145.179: P [tcp sum ok] 1:59(58) ack 1 win 16384: BGP (OPEN: Version 4, AS #30126, Holdtime 180, ID 192.228.82.16, Option length 29 ((CAP MULTI_PROTOCOL [IPv4 Unicast]) (CAP #128 len 0) (CAP ROUTE_REFRESH) (CAP #131 len 1) (CAP AS4 #30126))) (DF) [tos 0xc0] [ttl 1] (id 53675, len 98)
> 17:48:39.912023 193.105.232.145.179 > 193.105.232.181.21798: R [tcp sum ok] 1526797828:1526797828(0) win 0 (DF) (ttl 64, id 22749, len 40)
> 17:48:39.912346 193.105.232.181.21798 > 193.105.232.145.179: . [tcp sum ok] ack 2 win 16384 (DF) [tos 0xc0] [ttl 1] (id 53676, len 40)
> 17:48:39.912360 193.105.232.145.179 > 193.105.232.181.21798: R [tcp sum ok] 1526797829:1526797829(0) win 0 (DF) (ttl 64, id 50452, len 40)
> 17:48:39.912980 193.105.232.181.21798 > 193.105.232.145.179: FP [tcp sum ok] 59:59(0) ack 2 win 16384 (DF) [tos 0xc0] [ttl 1] (id 53677, len 40)
> 17:48:39.912993 193.105.232.145.179 > 193.105.232.181.21798: R [tcp sum ok] 1526797829:1526797829(0) win 0 (DF) (ttl 64, id 29177, len 40)
> 17:48:39.913417 193.105.232.181.21798 > 193.105.232.145.179: . [tcp sum ok] ack 2 win 16384 (DF) [tos 0xc0] [ttl 1] (id 53678, len 40)
> 17:48:39.913430 193.105.232.145.179 > 193.105.232.181.21798: R [tcp sum ok] 1526797829:1526797829(0) win 0 (DF) (ttl 64, id 9044, len 40)
>
>
> This connection initiated by the cisco is accepted and immediatly closed.
> That looks suspicious (also because nothing is logged in bgpd). Feels like
> pf(4) is playing dirty tricks here.
> Afterwards the openbgpd initiates the session and the cisco sends back a
> NOTIFICATION (maybe because it is still unhappy about the rather
> unexpected FIN/RST of the previous session).
>
> If the problem still exists when bgpd is accepting the cisco connection
> then we need to have a closer look at the messages.
>

Hi Claudio,

For reference I did:
- disable pf (pfctl -d)
- take down the bgp session (bgpctl nei pv4_gw-003_to_ISC down)
- tcpdump (tcpdump -w /tmp/cap2.out -Xi bnx2 host 193.105.232.181)
- take up the bgp session (bgpctl nei pv4_gw-003_to_ISC up)
- enable pf back (pfctl -e)

Here is the new capture file (pf disabled):
http://elfe.lncsa.com/get?k=2crqFiFNUZNmKw0jvk0

# bgpctl show neigh pv4_gw-003_to_ISC
BGP neighbor is 193.105.232.181, remote AS 30126
  Description: pv4_gw-003_to_ISC
   BGP version 4, remote router-id 192.228.82.16
   BGP state = Idle
   Last read 00:04:17, holdtime 240s, keepalive interval 80s

   Message statistics:
                   Sent       Received
   Opens                   80          2
   Notifications            0         80
   Updates                  0          0
   Keepalives               2          0
   Route Refresh            0          0
   Total                   82         82

   Update statistics:
                   Sent       Received
   Updates                  0          0
   Withdraws                0          0

   Last error: unknown error code

Thanks

Laurent

Reply | Threaded
Open this post in threaded view
|

Re: [OpenBGPd <=> Cisco] error in OPEN message, unknown subcode 8

Laurent Caron (Mobile)
In reply to this post by Laurent Caron (Mobile)
On Wed, Oct 10, 2012 at 12:13:44PM +0200, Laurent CARON wrote:
> Hi,
>
> I'm trying to establish a peering session with another member of an IX
> (France-IX).
>
> On my side I do have 2 OpenBSD (OpenBGPd) boxes.

(..snip..)

> In my logs I do observe this:
> Oct  9 09:44:40 bgpgw-003 bgpd[17498]: neighbor 193.105.232.181 (pv4_gw-003_to_ISC): state change Idle -> Connect, reason: Start
> Oct  9 09:44:40 bgpgw-003 bgpd[17498]: neighbor 193.105.232.181 (pv4_gw-003_to_ISC): state change Connect -> OpenSent, reason: Connection opened
> Oct  9 09:44:40 bgpgw-003 bgpd[17498]: neighbor 193.105.232.181 (pv4_gw-003_to_ISC): received notification: error in OPEN message, unknown subcode 8
> Oct  9 09:44:40 bgpgw-003 bgpd[17498]: neighbor 193.105.232.181 (pv4_gw-003_to_ISC): state change OpenSent -> Idle, reason: NOTIFICATION received
> Oct  9 09:44:43 bgpgw-003 bgpd[17498]: neighbor 2001:7f8:54::181 (pv6_gw-003_to_ISC): state change Idle -> Connect, reason: Start
> Oct  9 09:44:43 bgpgw-003 bgpd[17498]: neighbor 2001:7f8:54::181 (pv6_gw-003_to_ISC): state change Connect -> OpenSent, reason: Connection opened
> Oct  9 09:44:43 bgpgw-003 bgpd[17498]: neighbor 2001:7f8:54::181 (pv6_gw-003_to_ISC): received notification: error in OPEN message, unknown subcode 8
> Oct  9 09:44:43 bgpgw-003 bgpd[17498]: neighbor 2001:7f8:54::181 (pv6_gw-003_to_ISC): state change OpenSent -> Idle, reason: NOTIFICATION received
> Oct  9 09:44:44 bgpgw-003 bgpd[17498]: neighbor 2001:7f8:54::181 (pv6_gw-003_to_ISC): state change Idle -> Active, reason: Start
> Oct  9 09:44:44 bgpgw-003 bgpd[17498]: neighbor 2001:7f8:54::181 (pv6_gw-003_to_ISC): state change Active -> OpenSent, reason: Connection opened
> Oct  9 09:44:44 bgpgw-003 bgpd[17498]: neighbor 2001:7f8:54::181 (pv6_gw-003_to_ISC): state change OpenSent -> OpenConfirm, reason: OPEN message received
> Oct  9 09:44:44 bgpgw-003 bgpd[17498]: neighbor 2001:7f8:54::181 (pv6_gw-003_to_ISC): received notification: error in OPEN message, unknown subcode 8
> Oct  9 09:44:44 bgpgw-003 bgpd[17498]: neighbor 2001:7f8:54::181 (pv6_gw-003_to_ISC): state change OpenConfirm -> Idle, reason: NOTIFICATION received
>
>
> On the peer logs we have (peer is a Cisco 7301 running IOS 15.01 shoult
> it matter):
> Oct  9 2012 18:24:25.731 UTC: BGP: 193.105.232.145 active went from Idle to Active
> Oct  9 2012 18:24:25.731 UTC: BGP: 193.105.232.145 open active, local address 193.105.232.181
> Oct  9 2012 18:24:25.735 UTC: BGP: ses global 193.105.232.145 (0x6D6FC31C:0) act Remote close.
> Oct  9 2012 18:24:25.735 UTC: BGP: ses global 193.105.232.145 (0x6D6FC31C:0) act Reset (Peer closed the session).
> Oct  9 2012 18:24:25.735 UTC: BGP: 193.105.232.145 active went from Active to Idle
> Oct  9 2012 18:24:25.735 UTC: BGP: nbr global 193.105.232.145 Open active delayed 12288ms (35000ms max, 60% jitter)
> Oct  9 2012 18:24:25.735 UTC: BGP: nbr global 193.105.232.145 Active open failed - open timer running
>
> Do you guys (Claudio?) have a clue about it ?

Hi,

I added a new transit to my network (Level3) and this issue is back
(runnning OpenBSD 5.4 but tried current also).

Nov 25 22:43:55 bgpgw-002 bgpd[24271]: neighbor 2001:450:2001:1001::45
(ev6_gw-002_to_L3): received notification: error in OPEN message,
unknown subcode 8

Do any of you experience the same behavior ?

Thanks

Reply | Threaded
Open this post in threaded view
|

Re: [OpenBGPd <=> Cisco] error in OPEN message, unknown subcode 8

Laurent Caron (Mobile)
On Mon, Nov 25, 2013 at 10:53:24PM +0100, Laurent CARON wrote:
> I added a new transit to my network (Level3) and this issue is back
> (runnning OpenBSD 5.4 but tried current also).
>
> Nov 25 22:43:55 bgpgw-002 bgpd[24271]: neighbor 2001:450:2001:1001::45
> (ev6_gw-002_to_L3): received notification: error in OPEN message,
> unknown subcode 8
>
> Do any of you experience the same behavior ?

Nevermind, it was just a config mistake on my side (announcing ipv4
unicast over the ipv6 session).

Cheers,

Laurent

Reply | Threaded
Open this post in threaded view
|

Re: [OpenBGPd <=> Cisco] error in OPEN message, unknown subcode 8

Andy Lemin
On Tue 03 Dec 2013 18:15:23 GMT, Laurent CARON wrote:

> On Mon, Nov 25, 2013 at 10:53:24PM +0100, Laurent CARON wrote:
>> I added a new transit to my network (Level3) and this issue is back
>> (runnning OpenBSD 5.4 but tried current also).
>>
>> Nov 25 22:43:55 bgpgw-002 bgpd[24271]: neighbor 2001:450:2001:1001::45
>> (ev6_gw-002_to_L3): received notification: error in OPEN message,
>> unknown subcode 8
>>
>> Do any of you experience the same behavior ?
>
> Nevermind, it was just a config mistake on my side (announcing ipv4
> unicast over the ipv6 session).
>
> Cheers,
>
> Laurent
>

Can you provide an example of what you did/fixed in bgpd.conf so when
others google for this error they will have a pointer of what to do :)

Reply | Threaded
Open this post in threaded view
|

Re: [OpenBGPd <=> Cisco] error in OPEN message, unknown subcode 8

Laurent Caron (Mobile)
On 03/12/2013 19:20, Andy wrote:
> Can you provide an example of what you did/fixed in bgpd.conf so when
> others google for this error they will have a pointer of what to do :)

Here it is.

** Note for future readers, don't copy and paste this config snippet as
it does *NOT* work as you would expect it. **

$PEERv6="dead:beef::1"
$MEv6="dead:beef::2"

     neighbor $PEERv6 {
         remote-as               3549
         descr                   ev6_gw-001_to_L3
         local-address           $MEv6
         announce IPv6           none
         announce IPv4           unicast
     }

Reply | Threaded
Open this post in threaded view
|

Re: [OpenBGPd <=> Cisco] error in OPEN message, unknown subcode 8

Janne Johansson-3
2013/12/3 Laurent CARON <[hidden email]>

> ** Note for future readers, don't copy and paste this config snippet as it
> does *NOT* work as you would expect it. **
> $PEERv6="dead:beef::1"
> $MEv6="dead:beef::2"
>

Think of the vegans...


--
May the most significant bit of your life be positive.

Reply | Threaded
Open this post in threaded view
|

Re: [OpenBGPd <=> Cisco] error in OPEN message, unknown subcode 8

Laurent Caron (Mobile)
On 04/12/2013 12:28, Janne Johansson wrote:

> 2013/12/3 Laurent CARON <[hidden email]>
>
>> ** Note for future readers, don't copy and paste this config snippet as it
>> does *NOT* work as you would expect it. **
>> $PEERv6="dead:beef::1"
>> $MEv6="dead:beef::2"
>>
>
> Think of the vegans...
>
>

dead:potatoes:burn:in:hell::1 ? ;)

Reply | Threaded
Open this post in threaded view
|

Re: [OpenBGPd <=> Cisco] error in OPEN message, unknown subcode 8

sven falempin
1bad::f00d


On Wed, Dec 4, 2013 at 4:34 PM, Laurent CARON <[hidden email]>wrote:

> On 04/12/2013 12:28, Janne Johansson wrote:
>
>> 2013/12/3 Laurent CARON <[hidden email]>
>>
>>  ** Note for future readers, don't copy and paste this config snippet as
>>> it
>>> does *NOT* work as you would expect it. **
>>> $PEERv6="dead:beef::1"
>>> $MEv6="dead:beef::2"
>>>
>>>
>> Think of the vegans...
>>
>>
>>
> dead:potatoes:burn:in:hell::1 ? ;)
>
>


--
---------------------------------------------------------------------------------------------------------------------
() ascii ribbon campaign - against html e-mail
/\

Reply | Threaded
Open this post in threaded view
|

Re: [OpenBGPd <=> Cisco] error in OPEN message, unknown subcode 8

Alexander Hall
In reply to this post by Janne Johansson-3
Janne Johansson <[hidden email]> wrote:

>2013/12/3 Laurent CARON <[hidden email]>
>
>> ** Note for future readers, don't copy and paste this config snippet
>as it
>> does *NOT* work as you would expect it. **
>> $PEERv6="dead:beef::1"
>> $MEv6="dead:beef::2"
>>
>
>Think of the vegans...

Don't get me started on "mekmitasdigoat"... ;-)