Jump to content
Калькуляторы

Cisco - Quagga bgp ipv6

Reply to this topic

artplanet   

artplanet
Posted · Report post

Озадачились сделать bgp сессию с quagga (для dns серверов c резервированием)

ipv4 сессия успешно установилась, а вот ipv6 никак не хочет

 

 

Mar 29 14:06:48.127: %BGP_SESSION-5-ADJCHANGE: neighbor 2A07:yyyy::xx IPv6 Unicast topology base removed from session Peer closed the session

Mar 29 14:06:56.364: %BGP_SESSION-5-ADJCHANGE: neighbor 2A07:yyyy::xx IPv6 Unicast topology base removed from session Peer closed the session

Mar 29 14:07:09.735: %BGP_SESSION-5-ADJCHANGE: neighbor 2A07:yyyy::xx IPv6 Unicast topology base removed from session Peer closed the session

Mar 29 14:07:15.053: %BGP-3-NOTIFICATION: sent to neighbor 2A07:yyyy::xx passive 2/7 (unsupported/disjoint capability) 0 bytes

Mar 29 14:07:15.053: %BGP-4-MSGDUMP: unsupported or mal-formatted message received from 2A07:yyyy::xx:

FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 001D 0104 FDDF 00B4 5BD6 4405 00

Mar 29 14:07:17.972: %BGP_SESSION-5-ADJCHANGE: neighbor 2A07:yyyy::xx IPv6 Unicast topology base removed from session Peer closed the session

Mar 29 14:07:33.448: %BGP_SESSION-5-ADJCHANGE: neighbor 2A07:yyyy::xx IPv6 Unicast topology base removed from session Peer closed the session

Mar 29 14:07:46.801: %BGP_SESSION-5-ADJCHANGE: neighbor 2A07:yyyy::xx IPv6 Unicast topology base removed from session Peer closed the session

Mar 29 14:07:58.117: %BGP_SESSION-5-ADJCHANGE: neighbor 2A07:yyyy::xx IPv6 Unicast topology base removed from session Peer closed the session

Mar 29 14:08:09.441: %BGP_SESSION-5-ADJCHANGE: neighbor 2A07:yyyy::xx IPv6 Unicast topology base removed from session Peer closed the session

Mar 29 14:08:23.843: %BGP_SESSION-5-ADJCHANGE: neighbor 2A07:yyyy::xx IPv6 Unicast topology base removed from session Peer closed the session

Mar 29 14:08:31.040: %BGP_SESSION-5-ADJCHANGE: neighbor 2A07:yyyy::xx IPv6 Unicast topology base removed from session Peer closed the session

Mar 29 14:08:42.363: %BGP_SESSION-5-ADJCHANGE: neighbor 2A07:yyyy::xx IPv6 Unicast topology base removed from session Peer closed the session

Mar 29 14:08:43.060: %BGP_SESSION-5-ADJCHANGE: neighbor 2A07:yyyy::xx IPv6 Unicast topology base removed from session Capability changed

Mar 29 14:08:43.060: %BGP-3-NOTIFICATION: sent to neighbor 2A07:yyyy::xx passive 2/8 (no supported AFI/SAFI) 3 bytes 000101

Mar 29 14:08:56.766: %BGP_SESSION-5-ADJCHANGE: neighbor 2A07:yyyy::xx IPv6 Unicast topology base removed from session Peer closed the session

Mar 29 14:09:06.034: %BGP_SESSION-5-ADJCHANGE: neighbor 2A07:yyyy::xx IPv6 Unicast topology base removed from session Peer closed the session

Mar 29 14:09:13.240: %BGP_SESSION-5-ADJCHANGE: neighbor 2A07:yyyy::xx IPv6 Unicast topology base removed from session Peer closed the session

Mar 29 14:09:27.659: %BGP_SESSION-5-ADJCHANGE: neighbor 2A07:yyyy::xx IPv6 Unicast topology base removed from session Peer closed the session

Mar 29 14:09:41.037: %BGP_SESSION-5-ADJCHANGE: neighbor 2A07:yyyy::xx IPv6 Unicast topology base removed from session Peer closed the session

Mar 29 14:09:52.353: %BGP_SESSION-5-ADJCHANGE: neighbor 2A07:yyyy::xx IPv6 Unicast topology base removed from session Peer closed the session

Mar 29 14:10:00.581: %BGP_SESSION-5-ADJCHANGE: neighbor 2A07:yyyy::xx IPv6 Unicast topology base removed from session Peer closed the session

Mar 29 14:10:13.960: %BGP_SESSION-5-ADJCHANGE: neighbor 2A07:yyyy::xx IPv6 Unicast topology base removed from session Peer closed the session

Mar 29 14:10:22.197: %BGP_SESSION-5-ADJCHANGE: neighbor 2A07:yyyy::xx IPv6 Unicast topology base removed from session Peer closed the session

Mar 29 14:10:35.568: %BGP_SESSION-5-ADJCHANGE: neighbor 2A07:yyyy::xx IPv6 Unicast topology base removed from session Peer closed the session

Mar 29 14:10:45.868: %BGP_SESSION-5-ADJCHANGE: neighbor 2A07:yyyy::xx IPv6 Unicast topology base removed from session Peer closed the session

Mar 29 14:10:49.064: %BGP_SESSION-5-ADJCHANGE: neighbor 2A07:yyyy::xx IPv6 Unicast topology base removed from session Capability changed

Mar 29 14:10:49.064: %BGP-3-NOTIFICATION: sent to neighbor 2A07:yyyy::xx passive 2/8 (no supported AFI/SAFI) 3 bytes 000101

 

конфиг cisco

neighbor 2A07:yyyy::xx remote-as 64991

neighbor 2A07:yyyy::xx activate

neighbor 2A07:yyyy::xx send-community

neighbor 2A07:yyyy::xx route-map IN-BGP-ACCESS-IPv6 in

neighbor 2A07:yyyy::xx route-map OUT-BGP-DEFAULT-IPv6 out

 

 

конфиг quagga:

neighbor 2A07:yyyy::zz remote-as 65070

neighbor 2A07:yyyy::zz soft-reconfiguration inbound

 

 

кто сталкивался ?

 

и да - ipv4/ipv6 bgp сессии внутри одного int vlan. но между cisco-cisco такая схема работает.

 

и вот лог с кваги

 

2017/03/29 14:10:49 BGP: message index 8 not found in bgp_notify_open_msg (max is 8)

2017/03/29 14:12:57 BGP: message index 8 not found in bgp_notify_open_msg (max is 8)

2017/03/29 14:14:03 BGP: message index 8 not found in bgp_notify_open_msg (max is 8)

2017/03/29 14:15:36 BGP: message index 8 not found in bgp_notify_open_msg (max is 8)

2017/03/29 14:17:14 BGP: message index 8 not found in bgp_notify_open_msg (max is 8)

2017/03/29 14:19:57 BGP: message index 8 not found in bgp_notify_open_msg (max is 8)

Share this post

Link to post
Share on other sites

v_r   

v_r
Posted · Report post 

router bgp X
neighbor Y::Z remote-as 12345
no neighbor Y::Z activate
address-family ipv6
neighbor Y::Z activate
neighbor Y::Z route-map RM in
neighbor Y::Z route-map RM out

 

Кстати в BGP-сессии на v4 адресах можно анонсировать и v6 префиксы чтобы не поднимать вторую сессию.

Share this post

Link to post
Share on other sites

artplanet   

artplanet
Posted · Report post

это через set ipv6 next-hop, но вопрос как 3750 справиться с большими объемами?

Все же лучше сделать нормально и поднять bgp сессию

Share this post

Link to post
Share on other sites

artplanet   

artplanet
Posted · Report post

победил сам - оказывается в кваге по умолчанию в разделе ipv4 не создается запись вида no neighbor 2A07:yyyy::zz activate

добавил ее в раздел ipv4 и всё заработало

Share this post

Link to post
Share on other sites

v_r   

v_r
Posted · Report post

это через set ipv6 next-hop

Да, через next-hop, решение нестандартное но иногда бывает полезным.

но вопрос как 3750 справиться с большими объемами?

Трафик-то причем? Раут-мап в BGP работает исключительно в control-plane.

Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
Followers 0
Go to topic listing Активное оборудование Ethernet, IP, MPLS, SDN/NFV...