VMware Networking Community
Saroj2018
Contributor
Contributor

Error in UI: Unable to fetch inventory information for HW GW during "Manager Hardware Bindings"

Hi ,

      Does anybody knows at what scenario this error is displayed on NSX vSphere UI.

my Physical Switch(HW Gateway)(New Switch NOT yet certified by VMWare -In POC Stage) is connected to NSX controller and is UP and Running.

During the "Hardware Bindings" an Error is Seen like: Unable to fetch inventory information for "HW Gateway".

Can anyone tell when does this error is ideally seen.

Thanks,

Saroj

0 Kudos
6 Replies
singho
VMware Employee
VMware Employee

Could you please conform which NSX Version do you have.

This problem is about ToR switch port inventory, it is fix in controller side and ToR agent.

based on assumption that switch port is unique, current port name is unique key for port entity, but different ports can use same name, so some port is overwritten in controller.

Thanks

0 Kudos
Saroj2018
Contributor
Contributor

Attaching a snapshot of error for detail.

0 Kudos
Saroj2018
Contributor
Contributor

Thanks ,

             Singho

My NSX Manager's version is 6.3.4

     NSX vShpere version is 6.0.0

     NSX Controller version is 6.3.7

Could you have a look at snapshot attached  by me.

Regards,
Saroj

0 Kudos
singho
VMware Employee
VMware Employee

Could you please refer 6.4.2 and 6.3.7 Release Notes:-

Issue 2134192: Error is thrown when there is no port on the switch

If a physical switch on a hardware gateway has no port, NSX throws an error when trying to get the port from the switch. You will see the error, "Unable to fetch inventory information" while trying to get the port.

### Workaround: Create at least one port on the switch.

Hope it helps.

Thanks,

Omkar Singh

0 Kudos
Saroj2018
Contributor
Contributor

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

0 Kudos
Douglas178
Contributor
Contributor

This problem is about ToR switch port inventory, it is fix in controller side and ToR agent.

based on assumption that switch port is unique, current port name is unique key for port entity, but different ports can use same name, so some port is overwritten in controller.


Kodi Apk

0 Kudos