Mar 26 19:32:39.557 GMT-3: %BGP-5-ADJCHANGE: neighbor X.X.X.X Up
Mar 26 19:32:40.741 GMT-3: %BGP-5-ADJCHANGE: neighbor X.X.X.X Down BGP Notification sent
Mar 26 19:32:40.741 GMT-3: %BGP-3-NOTIFICATION: sent to neighbor 220.127.116.11 3/11 (invalid or corrupt AS path) 13 bytes 40020A02 041F776F D11C8200 47
Mar 26 19:32:40.741 GMT-3: BGP: X.X.X.X Bad attributes FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 003C 0200 0000 2140 0101 0040 020A 0204 1F77 6FD1 1C82 0047 4003 04C8 DB82 06C0 0706 0047 1060 B336 140F E3F0
Does anyone knows were the problem could be?
Your configuration confirms what I thought. The neighbor sends you an AS-PATH with 8055 as the first ASN, while the peer ASN is 64548. Note that "remove-private-as" is only effective for outbound messages, so doesn't apply here.
Just out of curiosity, what type of device is the neighbor. Route server? In which case in might be ok to accept the update.
If you want to accept the updates despite the first ASN in the AS-PATH doesn't match the peer ASN, you can disable this check with the following command:
router bgp xxx
no bgp enforce-first-as
Hope this helps,