Hi Cisco Community,
Strange one here. We have deployed 2 x ASR1001-X as cEdge device to onboard a site of around 2000 users onto our SDWAN network. 1 ASR onboards into vManage with no issue and we can see it in the device_ bring_up. The other ASR gives us the BIDNTVRFD error when trying to authorize with vBond but all control connections to vSmart devices and vManage are UP and we can forward traffic and use this ASR as a path for our SDWAN fabric, yet we get errors in the device_bring_up and Authorized by vBond gives us the messages below:
Event Name : security-vedge-entry-added
Event Details : host-name=aaaaa; uuid=ASR1001-X-xxxxxx; serial=xxxxxx
Event Name : security-vedge-entry-added
Event Details : host-name=bbbbb; uuid=ASR1001-X-xxxxxxx; serial=xxxxxxx
Event Name : vbond-reject-vedge-connection
Event Details : host-name=ccccc; uuid=ASR1001-X-xxxxxx; organization-name=yyyyyy; sp-organization-name=yyyyy; reason=ERR_BID_NOT_VERIFIED
Event Name : security-vedge-entry-added
Event Details : host-name=ddddd; uuid=ASR1001-X-xxxxx; serial=xxxxx
Event Name : security-vedge-entry-added
Event Details : host-name=ccccc; uuid=ASR1001-X-xxxxxx; serial=xxxxx
The host-name=ccccc is the same vBond also. Anyone seen anything like this before? Screenshot shows one ASR onboarded (black rectangles hiding info) and 1 ASR still blank.
