Last active
January 30, 2018 21:36
-
-
Save smurugap/f14b902b7511bf834a2b to your computer and use it in GitHub Desktop.
Contrail: DHCP doesnt work from VM
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1) Check http://<compute-ip>:8085/Snh_ItfReq?name=<tap_name> | |
a. If vif status is not active then it’s a known corner case issue with agent and afaik vrouter-agent restart is the only way to recover. | |
b. if vrf_name/vn_name or other config shows -error- then the configs weren’t downloaded from control-node | |
i. get the active control node via http://<compute-ip>:8085/Snh_AgentXmppConnectionStatusReq? With cfg_controller ‘yes’ | |
ii. Check whether vmi has vmi-ri,vn,instance-ip as neighbor under ifmap in control http://<control-ip>:8083/Snh_IFMapTableShowReq?table_name=virtual-machine-interface | |
iii. If not found, do ‘netstat -antp | grep <control-process-id> | grep 8443’ and find the connected ifmap server | |
iv. On the ifmap-server do ‘curl -uadmin:contrail123 http://127.0.0.1:8095/virtual-machine-interface/<vmi-id> | python -m json.tool’ and check for vn, ri refs | |
v. If refs not found, check for schema.err on the active schema node around the vmi create timestamp. | |
vi. If no errors, check the rabbitmq connection between config and check the vnc_config queue under ‘rabbitmqctl list-queues’ for any undelivered messages |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment