Use configured BGP port number in BGPaaS
Bug #1751394 reported by
Ananth Suryanarayana
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R5.0 |
Fix Committed
|
Undecided
|
sangarshan p | |||
Trunk |
Fix Committed
|
Undecided
|
sangarshan p |
Bug Description
In agent/vrouter, when BGPaaS sessions are NATed to control-node, destination port should not be hard coded to 179. Instead, it should be set to what ever is configured as it is already part of the BgpRouter object that agent apparently already reads.
If we already do get the port number from config, then please close this bug.
Changed in juniperopenstack: | |
assignee: | Hari Prasad Killi (haripk) → sangarshan p (sangarshp) |
To post a comment you must log in.
Review in progress for https:/ /review. opencontrail. org/40631
Submitter: sangarshan p (<email address hidden>)