为什么 bgp 打开和通知数据包只在 ODL 中流动

Question

我需要与路由反射器运行 odl 和我的路由器建立 bgp 会话，到目前为止我已经完成了以下操作。安装了 opendaylight karaf，氮气版本。

已安装 bgp 功能（功能：安装 odl-restconf odl-bgpcep-bgp、odl-bgpcep-bgp）。使用高级 rest 客户端配置参数，直到官方网站 (http://docs.opendaylight.org/en/stable-nitrogen/user-guide/bgp-user-guide.html) 之后的 bgp 对等部分。当我检查我的路由器的状态时，我看到 bgp 状态处于活动状态并且在 wireshark 中 bgp 开放数据包由路由器发送并且 odl 正在发送连接拒绝通知。还有一个 tcp 数据包发送，ODL 设置了重置标志。我启用了调试选项并检查了 karaf 日志，上面写着 .

(org.opendaylight.protocol.bgp.parser.BGPDocumentedException: BGP peer with ip: IpAddress [_ipv4Address=Ipv4Address [_value=10.10.10.2]] 未配置，检查已配置的对等点： StrictBGPPeerRegistry{peers=[]} 在 org.opendaylight.protocol.bgp.rib.impl.AbstractBGPSessionNegotiator.startNegotiation(AbstractBGPSessionNegotiator.java:103)[117:org.opendaylight.bgpcep.bgp-rib-impl:0.8.1] 在 org.opendaylight.protocol.bgp.rib.impl.AbstractBGPSessionNegotiator.channelActive(AbstractBGPSessionNegotiator.java:278)[117:org.opendaylight.bgpcep.bgp-rib-impl:0.8.1] 2018-01-04 16:46:44,191 |调试 | ntLoopGroup-10-3 |摘要BGPSessionNegotiator | 117 - org.opendaylight.bgpcep.bgp-肋骨植入物 - 0.8.1 |在通道上开始会话协商 [id: 0xc90a1a8a, L:/10.10.10.1:179 - R:/10.10.10.2:51732] 2018-01-04 16:46:44,191 |错误 | ntLoopGroup-10-3 | BGPDocumentedException | 111 - org.opendaylight.bgpcep.bgp-解析器-api - 0.8.1 |错误 = CONNECTION_REJECTED

简而言之，我想知道以下内容，

1) 为什么 bgp 通知是由 odl 发送的，同时拒绝连接和 Tcp 设置了重置标志的数据包发送 ?

2) 为什么没有名为 (41-bgp-example) 的文件 generated.Still 我手动创建并配置了它但没有效果。

3) 我怎样才能进一步到达路由反射器，有什么不对劲或者我错过了什么吗？

下面是我提到的文件 (41-bgp-example)

<?xml version="1.0" encoding="UTF-8"?>
<!-- vi: set et smarttab sw=4 tabstop=4: -->
<!--
      Copyright (c) 2013 Cisco Systems, Inc. and others.  All rights reserved.
 This program and the accompanying materials are made available under the
 terms of the Eclipse Public License v1.0 which accompanies this distribution,
 and is available at http://www.eclipse.org/legal/epl-v10.html
-->
<snapshot>
    <required-capabilities>
        <capability>urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:cfg?module=odl-bgp-rib-cfg&amp;revision=2013-07-01</capability>
        <capability>urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:spi?module=odl-bgp-rib-spi-cfg&amp;revision=2013-11-15</capability>
        <capability>urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:impl?module=odl-bgp-rib-impl-cfg&amp;revision=2013-04-09</capability>
        <capability>urn:opendaylight:params:xml:ns:yang:controller:bgp:topology:provider?module=odl-bgp-topology-provider-cfg&amp;revision=2013-11-15</capability>
        <capability>urn:opendaylight:params:xml:ns:yang:controller:bgp:reachability:ipv6?module=odl-bgp-treachability-ipv6-cfg&amp;revision=2013-11-15</capability>
        <capability>urn:opendaylight:params:xml:ns:yang:controller:bgp:reachability:ipv4?module=odl-bgp-treachability-ipv4-cfg&amp;revision=2013-11-15</capability>
        <capability>urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding?module=opendaylight-md-sal-binding&amp;revision=2013-10-28</capability>
        <capability>urn:opendaylight:params:xml:ns:yang:controller:md:sal:dom?module=opendaylight-md-sal-dom&amp;revision=2013-10-28</capability>
        <capability>urn:opendaylight:params:xml:ns:yang:controller:netty?module=netty&amp;revision=2013-11-19</capability>
        <capability>urn:opendaylight:params:xml:ns:yang:controller:protocol:framework?module=protocol-framework&amp;revision=2014-03-13</capability>
        <capability>urn:opendaylight:params:xml:ns:yang:controller:topology?module=odl-topology-api-cfg&amp;revision=2013-11-15</capability>
        <capability>urn:opendaylight:params:xml:ns:yang:controller:bgp-openconfig-spi?module=odl-bgp-openconfig-spi-cfg&amp;revision=2015-09-25</capability>
    </required-capabilities>
    <configuration>

        <data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
            <modules xmlns="urn:opendaylight:params:xml:ns:yang:controller:config">
                <module>
                    <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:protocol:framework">prefix:timed-reconnect-strategy-factory</type>
                    <name>example-reconnect-strategy-factory</name>
                    <min-sleep>1000</min-sleep>
                    <max-sleep>180000</max-sleep>
                    <sleep-factor>2.00</sleep-factor>
                    <connect-time>5000</connect-time>
                    <timed-reconnect-executor>
                        <type xmlns:netty="urn:opendaylight:params:xml:ns:yang:controller:netty">netty:netty-event-executor</type>
                        <name>global-event-executor</name>
                    </timed-reconnect-executor>
                </module>

                <module>
                    <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:impl">prefix:bgp-peer-acceptor</type>
                    <name>bgp-peer-server</name>

                    <!--Default parameters-->
                    <!-- <binding-address>127.0.0.1</binding-address> -->

                    <!--Default binding-port 179-->
                    <!-- <binding-port>1790</binding-port> -->

                    <accepting-bgp-dispatcher>
                        <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:impl">prefix:bgp-dispatcher</type>
                        <name>global-bgp-dispatcher</name>
                    </accepting-bgp-dispatcher>
                    <accepting-peer-registry>
                        <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:impl">prefix:bgp-peer-registry</type>
                        <name>global-bgp-peer-registry</name>
                    </accepting-peer-registry>

                </module>


                <module>
                   <type xmlns:x="urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:impl">x:bgp-application-peer</type>
                   <name>example-bgp-peer-app</name>
                   <bgp-peer-id>10.10.10.2</bgp-peer-id>
                   <target-rib>
                     <type xmlns:x="urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:impl">x:rib-instance</type>
                     <name>example-bgp-rib</name>
                   </target-rib>
                   <application-rib-id>example-app-rib</application-rib-id>
                   <data-broker>
                     <type xmlns:sal="urn:opendaylight:params:xml:ns:yang:controller:md:sal:dom">sal:dom-async-data-broker</type>
                     <name>pingpong-broker</name>
                   </data-broker>
                </module>



                <!--
                     A single BGP peer. Note this section is deactivated because a misconfigured peer
                     tends to log rather nasty error messages.
                     For TCP-MD5 support, make sure the dispatcher associated with the rib has
                     "md5-channel-factory" attribute set and then add a "password" attribute here.
                     Note that the peer has to have the same password configured, otherwise the
                     connection will not be established.
                     If peer role is not present, default value "ibgp" will be used (allowed values are also "ebgp" and
                     "rr-client").
                   -->

                <module>
                    <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:impl">prefix:bgp-peer</type>
                    <name>example-bgp-peer</name>
                    <host>10.10.10.1</host>
                    <holdtimer>180</holdtimer>
                    <peer-role>ibgp</peer-role>
                    <rib>
                        <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:impl">prefix:rib-instance</type>
                        <name>example-bgp-rib</name>
                    </rib>
                    <peer-registry>
                        <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:impl">prefix:bgp-peer-registry</type>
                        <name>global-bgp-peer-registry</name>
                    </peer-registry>
                    <advertized-table>
                        <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:impl">prefix:bgp-table-type</type>
                        <name>ipv4-unicast</name>
                    </advertized-table>
                    <advertized-table>
                        <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:impl">prefix:bgp-table-type</type>
                        <name>ipv6-unicast</name>
                    </advertized-table>
                    <advertized-table>
                        <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:impl">prefix:bgp-table-type</type>
                        <name>linkstate</name>
                    </advertized-table>
                    <advertized-table>
                        <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:impl">prefix:bgp-table-type</type>
                        <name>ipv4-flowspec</name>
                    </advertized-table>
                    <advertized-table>
                        <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:impl">prefix:bgp-table-type</type>
                        <name>ipv6-flowspec</name>
                    </advertized-table>
                    <advertized-table>
                        <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:impl">prefix:bgp-table-type</type>
                        <name>labeled-unicast</name>
                    </advertized-table>
                </module>

                <module>
                    <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:impl">prefix:rib-impl</type>
                    <name>example-bgp-rib</name>
                    <rib-id>example-bgp-rib</rib-id>
                    <local-as>65530</local-as>
                    <bgp-rib-id>10.10.10.2</bgp-rib-id>
                    <!-- if cluster-id is not present, it's value is the same as bgp-id -->
                    <!-- <cluster-id>192.0.2.3</cluster-id> -->
                    <local-table>
                        <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:impl">prefix:bgp-table-type</type>
                        <name>ipv4-unicast</name>
                    </local-table>
                    <local-table>
                        <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:impl">prefix:bgp-table-type</type>
                        <name>ipv6-unicast</name>
                    </local-table>
                    <local-table>
                        <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:impl">prefix:bgp-table-type</type>
                        <name>linkstate</name>
                    </local-table>
                    <local-table>
                        <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:impl">prefix:bgp-table-type</type>
                        <name>ipv4-flowspec</name>
                    </local-table>
                    <local-table>
                        <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:impl">prefix:bgp-table-type</type>
                        <name>ipv6-flowspec</name>
                    </local-table>
                    <local-table>
                        <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:impl">prefix:bgp-table-type</type>
                        <name>labeled-unicast</name>
                    </local-table>
                    <extensions>
                        <type xmlns:ribspi="urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:spi">ribspi:extensions</type>
                        <name>global-rib-extensions</name>
                    </extensions>
                    <bgp-dispatcher>
                        <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:impl">prefix:bgp-dispatcher</type>
                        <name>global-bgp-dispatcher</name>
                    </bgp-dispatcher>
                    <data-provider>
                        <type xmlns:binding="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding">binding:binding-async-data-broker</type>
                        <name>pingpong-binding-data-broker</name>
                    </data-provider>
                    <dom-data-provider>
                        <type xmlns:sal="urn:opendaylight:params:xml:ns:yang:controller:md:sal:dom">sal:dom-async-data-broker</type>
                        <name>pingpong-broker</name>
                    </dom-data-provider>
                    <codec-tree-factory>
                        <type xmlns:binding="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding">binding:binding-codec-tree-factory</type>
                        <name>runtime-mapping-singleton</name>
                    </codec-tree-factory>
                    <session-reconnect-strategy>
                        <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:protocol:framework">prefix:reconnect-strategy-factory</type>
                        <name>example-reconnect-strategy-factory</name>
                    </session-reconnect-strategy>
                    <tcp-reconnect-strategy>
                        <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:protocol:framework">prefix:reconnect-strategy-factory</type>
                        <name>example-reconnect-strategy-factory</name>
                    </tcp-reconnect-strategy>
                    <openconfig-provider>
                        <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:bgp-openconfig-spi">prefix:bgp-openconfig-provider</type>
                        <name>openconfig-bgp</name>
                    </openconfig-provider>
                </module>
                <module>
                    <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:bgp:reachability:ipv4">prefix:bgp-reachability-ipv4</type>
                    <name>example-ipv4-topology</name>
                    <data-provider>
                        <type xmlns:binding="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding">binding:binding-async-data-broker</type>
                        <name>pingpong-binding-data-broker</name>
                    </data-provider>
                    <local-rib>
                        <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:cfg">prefix:rib</type>
                        <name>example-bgp-rib</name>
                    </local-rib>
                    <topology-id>example-ipv4-topology</topology-id>
                </module>
                <module>
                    <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:bgp:reachability:ipv6">prefix:bgp-reachability-ipv6</type>
                    <name>example-ipv6-topology</name>
                    <data-provider>
                        <type xmlns:binding="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding">binding:binding-async-data-broker</type>
                        <name>pingpong-binding-data-broker</name>
                    </data-provider>
                    <local-rib>
                        <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:cfg">prefix:rib</type>
                        <name>example-bgp-rib</name>
                    </local-rib>
                    <topology-id>example-ipv6-topology</topology-id>
                </module>
                <module>
                    <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:bgp:topology:provider">prefix:bgp-linkstate-topology</type>
                    <name>example-linkstate-topology</name>
                    <data-provider>
                        <type xmlns:binding="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding">binding:binding-async-data-broker</type>
                        <name>pingpong-binding-data-broker</name>
                    </data-provider>
                    <local-rib>
                        <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:cfg">prefix:rib</type>
                        <name>example-bgp-rib</name>
                    </local-rib>
                    <topology-id>example-linkstate-topology</topology-id>
                </module>
            </modules>

            <services xmlns="urn:opendaylight:params:xml:ns:yang:controller:config">
                <service>
                    <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:protocol:framework">prefix:reconnect-strategy-factory</type>
                    <instance>
                        <name>example-reconnect-strategy-factory</name>
                        <provider>/config/modules/module[name='timed-reconnect-strategy-factory']/instance[name='example-reconnect-strategy-factory']</provider>
                    </instance>
                </service>
                <service>
                    <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:topology">prefix:topology-reference</type>
                    <instance>
                        <name>example-ipv4-topology</name>
                        <provider>/config/modules/module[name='bgp-reachability-ipv4']/instance[name='example-ipv4-topology']</provider>
                    </instance>
                </service>
                <service>
                    <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:cfg">prefix:rib</type>
                    <instance>
                        <name>example-bgp-rib</name>
                        <provider>/config/modules/module[name='rib-impl']/instance[name='example-bgp-rib']</provider>
                    </instance>
                </service>
                <service>
                    <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:impl">prefix:rib-instance</type>
                    <instance>
                        <name>example-bgp-rib</name>
                        <provider>/config/modules/module[name='rib-impl']/instance[name='example-bgp-rib']</provider>
                    </instance>
                </service>
                <service>
                    <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:topology">prefix:topology-reference</type>
                    <instance>
                        <name>example-ipv6-topology</name>
                        <provider>/config/modules/module[name='bgp-reachability-ipv6']/instance[name='example-ipv6-topology']</provider>
                    </instance>
                </service>
                <service>
                    <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:topology">prefix:topology-reference</type>
                    <instance>
                        <name>example-linkstate-topology</name>
                        <provider>/config/modules/module[name='bgp-linkstate-topology']/instance[name='example-linkstate-topology']</provider>
                    </instance>
                </service>
            </services>
        </data>
    </configuration>
</snapshot>

enter code here

Answer 1

得到前几个问题的答案

1) 为什么 bgp 通知由 odl 发送并拒绝连接，而 Tcp 数据包发送时设置了重置标志？

ans:- 因为 peer 没有正确地 configured.Using rest client，配置没有完全成功，所以手动编辑文件 protocols-config.xml(在路径 /etc/opendaylight/bgp) 之后成功了。

2) 为什么没有名为 (41-bgp-example) 的文件 generated.Still 我手动创建并配置了它但没有效果。

ans:不会生成文件，因为对于氮版本，配置子系统已经更改，因此必须遵循使用 REST。

为什么 bgp 打开和通知数据包只在 ODL 中流动

Why bgp open and notification packets is only flowing in ODL

tcp

bgp

apache-karaf

opendaylight