Posted on December 10, 2020 4:26 am
 |  Asked by kang Minjun
 |  553 views
Tags:
RESOLVED
0
0
Print Friendly, PDF & Email

Equipment cannot be added in cvp. Please tell me the solution.
I attach the log.

I1209 03:17:45.959601 8 utils.go:404] Command to access vrf on device(s) is cli vrf %s
I1209 03:17:47.145653 8 inventory_helper.go:1176] Device 172.100.100.109 has TerminAttr-v1.8.0-1 installed
I1209 03:17:47.145798 8 inventory_helper.go:1181] v1.8.0-1 >= v1.7.4-1. Skipping TerminAttr installation on 172.100.100.109
I1209 03:17:47.349948 8 utils.go:605] Installed token from CV 172.100.100.30:9910 on device 172.100.100.109
I1209 03:17:48.607344 8 inventory_helper.go:304] Successfully enabled TerminAttr on the device 172.100.100.109
I1209 03:17:48.607402 8 requestHandler.go:105] Waiting for device with ID JPE19051252 to stream data
I1209 03:17:48.607430 8 inventory.go:853] Waiting for device JPE19051252 to stream
I1209 03:17:48.619452 8 processor.go:299] Response &{172.100.100.109_onboardDevice 2020-12-09 03:17:44.666 +0000 UTC 0001-01-01 00:00:00 +0000 UTC processing Enabled TerminAttr, waiting for device to stream 0 JPE19051252 0} successfully written
E1209 03:32:48.607748 8 base.go:257] Error in receiving updates for subscriptions to /inventory/device/ids/JPE19051252: rpc error: code = DeadlineExceeded desc = context deadline exceeded terminating subscription
E1209 03:32:48.608458 8 inventory.go:912] Timed out waiting for device JPE19051252 to stream
I1209 03:32:48.616944 8 processor.go:299] Response &{172.100.100.109_onboardDevice 2020-12-09 03:17:44.666 +0000 UTC 0001-01-01 00:00:00 +0000 UTC failed Timed out waiting for device JPE19051252 to stream 500 0} successfully written

 

Attachments:
0
Posted by Tamas Plugor
Answered on December 10, 2020 1:08 pm

If the device cannot stream to CVP (on TCP 9910) the onboarding will fail. There are a few things you can check:

    • there's no firewall blocking the communication between the switch and CVP on TCP port 9910
    • to test if this works as expected you can run: telnet x.x.x.x 9910 in EOS and see if it connects successfully (note that you have to run this without specifying /source-interface flag
      if the above is validated, you'll have to check the TerminAttr logs, either by running show agent TerminAttr logs or by going to bash and checking the logs in /var/log/agents/, a quick way to do that is to run bash cat /var/log/agents/TerminAttr-`pidof TerminAttr`, that should give you a good indication on what's wrong
    • in case there's no FW in between and the telnet command will fail to connect, it could mean that you are using in-band management, in which case you'll have to set the telnet source and also the -cvsourceip=x.x.x.x

flag in TerminAttr.

To automatically set the cvsourceip upon registering you can follow the steps from https://eos.arista.com/forum/how-to-edit-terminattr-to-use-loopback-interface/

It might be also easier to do a screen share if you get stuck; please feel free to contact TAC at support@arista.com and one of us would be more than happy to help!

Thanks,
Tamas

Post your Answer

You must be logged in to post an answer.