We are having issues building the overlay network and this is due to vedge which with serial-num BOARD-ID-NOT-INITIALISED & token -NA-, We have a copy of the serial number from prechecks. Is it possible to map this on this vedge and how?
Upgrade from 18.x.x to 19.x.x == BEFORE THE UPGRADE rtra# show control local-properties personality vedge sp-organization-name xxxx organization-name xxxx certificate-status Installed root-ca-chain-status Installed certificate-validity Valid <> dns-name xxxx site-id xxxx domain-id 1 protocol dtls tls-port 0 system-ip 1.2.81.1 chassis-num/unique-id abcdefg serial-num abcdefg token -NA- keygen-interval 1:00:00:00 retry-interval 0:00:00:18 no-activity-exp-interval 0:00:00:20 dns-cache-ttl 0:00:02:00 port-hopped TRUE time-since-last-port-hop 9:07:06:15 embargo-check success number-vbond-peers 2 == AFTER UPGRADING rtra# show control local-properties personality vedge sp-organization-name xxxx organization-name xxxx root-ca-chain-status Installed certificate-status Installed certificate-validity Not Installed certificate-not-valid-before Not Applicable certificate-not-valid-after Not Applicable enterprise-cert-status Not-Applicable enterprise-cert-validity Not Applicable enterprise-cert-not-valid-before Not Applicable enterprise-cert-not-valid-after Not Applicable dns-name xxxx site-id xxxx domain-id 1 protocol dtls tls-port 0 system-ip 1.2.81.1 chassis-num/unique-id abcdefg <---- Correct serial-num BOARD-ID-NOT-INITIALISED <---- Missing subject-serial-num N/A enterprise-serial-num No certificate installed token -NA- This is a hardware vedge and request vedge-cloud command is not supported.
rtra# request vedge-cloud activate ? ^ % Invalid input detected at '^' marker. Anyone encountered this issue and is it possible to map again the SN info? Thanks
No comments:
Post a Comment