Hi Omkar,
Thanks for the info. and reply. Will do check with the release versions.
Physical_Port table
_uuid description name port_fault_status vlan_bindings vlan_stats
------------------------------------ ----------- ------- ----------------- ------------- ----------
595997a6-7d0a-4de4-acdc-52213fc6ba94 "" "1/1/2" [] {} {}
Physical_Switch table
_uuid description management_ips name ports switch_fault_status tunnel_ips tunnels
------------------------------------ ----------- ------------------- ----- -------------------------------------- ------------------- ----------------- -------
51043e11-74ed-400b-a0de-49562929408d "" ["192.xx.xx.xx"] "PS0" [595997a6-7d0a-4de4-acdc-52213fc6ba94] [] ["192.xx.xx.xx"] []
sw-tor:/home/admin#
sw-tor:/home/admin# vtep-ctl list-ports PS0
1/1/2
Actually when i am not even seeing the physical switch- PS0 in <switch field> under HW VTEP during the "Hardware Bindings".
Looks like the NSX controller is NOT able to fetch and populate the switch with "the configured physical switch and also its configured physical port".
what i am seeing from the debug logs on switch's ovsdb-server that.
SWitch(ovsdb-server)---------------------------NSXcontroller(ovsdb-client).
1. SSL handshake between the two and connection is UP after putting sw-certificate at NSX controller.
2. Then NSX controller requests the get-schema from OVDB-Client of Switch.
Switch replies with complete hardware_vtep(1.3) schema to ovsdb-client.
3. The when i go for hardware binding and switches under HW VTEP does get populated even though PS0 is configured with port.
Could you please let me know the exact working procedure of NSX to SW-Gateway(HW VTEP) interaction, So that i can where is is failing.
Thanks,
Saroj