[BGPCEP-746] Too much BGP-IPv4 Flow Specification routes cause ODL dead Created: 16/Jan/18 Updated: 24/Jan/23 |
|
| Status: | Open |
| Project: | bgpcep |
| Component/s: | BGP |
| Affects Version/s: | Carbon |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Low |
| Reporter: | Yang Bingbign | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | pick-next, pt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Description |
3.The picture is how to post IPv4 Flow Specification routing.
3.1 Protocol Configuration Method: POST Content-Type: application/xml <protocol xmlns="http://openconfig.net/yang/network-instance"> <name>bgp-example</name> <identifier xmlns:x="http://openconfig.net/yang/policy-types">x:BGP</identifier> <bgp xmlns="urn:opendaylight:params:xml:ns:yang:bgp:openconfig-extensions"> <global> <config> <router-id>202.109.207.75</router-id> <as>65110</as> </config> <afi-safis> <afi-safi> <afi-safi-name xmlns:x="http://openconfig.net/yang/bgp-types">x:IPV4-UNICAST</afi-safi-name> </afi-safi> <afi-safi> <afi-safi-name xmlns:x="http://openconfig.net/yang/bgp-types">x:IPV6-UNICAST</afi-safi-name> </afi-safi> <afi-safi> <afi-safi-name>IPV4-FLOW</afi-safi-name> </afi-safi> <afi-safi> <afi-safi-name>IPV6-FLOW</afi-safi-name> </afi-safi> <afi-safi> <afi-safi-name>IPV4-L3VPN-FLOW</afi-safi-name> </afi-safi> <afi-safi> <afi-safi-name>IPV6-L3VPN-FLOW</afi-safi-name> </afi-safi> </afi-safis> </global> </bgp></protocol>
3.2 BGP flowspec Peer Method: POST Content-Type: application/xml Request Body: <neighbor xmlns="urn:opendaylight:params:xml:ns:yang:bgp:openconfig-extensions"><neighbor-address>202.101.99.249</neighbor-address> <timers> <config> <hold-time>90</hold-time> <connect-retry>10</connect-retry> </config> </timers> <transport> <config> <remote-port>179</remote-port> <passive-mode>false</passive-mode> </config> </transport> <config> <peer-type>EXTERNAL</peer-type> <peer-as>65130</peer-as> </config><afi-safis> <afi-safi> <afi-safi-name xmlns:x="http://openconfig.net/yang/bgp-types">x:IPV4-UNICAST</afi-safi-name> </afi-safi> <afi-safi> <afi-safi-name xmlns:x="http://openconfig.net/yang/bgp-types">x:IPV6-UNICAST</afi-safi-name> </afi-safi> <afi-safi> <afi-safi-name>IPV4-FLOW</afi-safi-name> </afi-safi> <afi-safi> <afi-safi-name>IPV6-FLOW</afi-safi-name> </afi-safi> <afi-safi> <afi-safi-name>IPV4-L3VPN-FLOW</afi-safi-name> </afi-safi> <afi-safi> <afi-safi-name>IPV6-L3VPN-FLOW</afi-safi-name> </afi-safi> </afi-safis></neighbor>
3.3 BGP Application Peer and programmable RIB(I created it as soon as post one routing.Using different neighbor-address. ) Method: POST Content-Type: application/xml Request Body: <neighbor xmlns="urn:opendaylight:params:xml:ns:yang:bgp:openconfig-extensions"> <neighbor-address>10.25.1.9</neighbor-address> <config> <peer-group>application-peers</peer-group> </config></neighbor> URL: http://202.109.207.77:8181/restconf/config/bgp-rib:application-rib/10.25.1.9 /tables/bgp-types:ipv4-address-family/bgp-flowspec:flowspec-subsequent-address-family/bgp-flowspec:flowspec-routes Method: POST Content-Type: application/xml <flowspec-route xmlns="urn:opendaylight:params:xml:ns:yang:bgp-flowspec"> <attributes> </attributes> |