Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2097701

Summary:	MetaLLB: Validation unable to create BGPPeers with spec.peerASN Value in OCP 4.10
Product:	OpenShift Container Platform	Reporter:	Immanuvel <imm>
Component:	Networking	Assignee:	Federico Paolinelli <fpaoline>
Networking sub component:	Metal LB	QA Contact:	Arti Sood <asood>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	unspecified	CC:	bzvonar, fpaoline, pibanezr
Version:	4.10	Keywords:	Reopened
Target Milestone:	---
Target Release:	4.12.0
Hardware:	x86_64
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-01-17 19:50:02 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2109943

Description Immanuvel 2022-06-16 11:01:40 UTC

Description of problem:

Customer has installed metallb operator and trying to configure BGPPeer  , but they are having issues with creating it with below error message 

Error "Invalid value: 4247584822: spec.peerASN in body should be less than or equal to 65535" for field "spec.peerASN"

They are not able to create PeerBGB because customer's  ASN value seems to be out of range. just installed the metalLB operator but not able to configure yet

They are using 4 byte ASN (4247584822) on their Cisco Routers, since  peer cannot understand 4 byte, they are  converting  4 byte to 2 byte AS which will be in decimal format (64813.54)

 Peer ASN configured in the DC Gateway are:
2-Byte AS Number: 64813.54
4-Byte AS Number: 4247584822

ASN on Cisco ASR Router cannot be changed, as it is in production supporting thousands on Pods.

It looks like 2-Byte AS is a  kind of legacy numbering and when asked on FRR channel seems like we we don't have 4 bytes support and asked for Asdot fmt maybe something can be added in the next  OCP releases

Version-Release number of selected component (if applicable):

OCP 4.10

How reproducible:
Depends on the environment and infra used (Cisco routers)

Steps to Reproduce:
1.
2.
3.

Actual results:

Giving  Error 


Expected results:

Either 2 byte AS format or 4 Byte should be supported 

Additional info:

We had some discussions in forum-bgp regarding this topic FYR , below link

https://coreos.slack.com/archives/C01EH16NFPZ/p1654519132159399

Comment 1 Mohamed Mahmoud 2022-06-16 18:21:48 UTC

metallb BGP stack only support 2 bytes plain AS format, customers wanted to peer with metallb need adhere to the same format
there is no plan to support either 2 bytes dot AS format nor 4 bytes ASN at the moment.

Comment 2 Federico Paolinelli 2022-07-04 20:58:42 UTC

Reopening this as we are going to introduce the support for 4 bytes asn.

Comment 7 errata-xmlrpc 2023-01-17 19:50:02 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.12.0 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:7399