Invalid connections in 3.4 demo data

[tgrusendorf]

I believe there are some invalid connections in the 3.4 demo data. I am finding interfaces which show the endpoint is a module instead of a device interface or circuit provider. These connections also fail a cable trace.

Example:
dmi01-akron-rtr01 GigabitEthernet0/0/0 shows a path endpoint of "Slot 0: EX9200-32XS (1)" which is a module in ncsu-coreswitch1.

If I follow the cable (#7) from GigabitEthernet0/0/0, it connects to a circuit, not to anything that leads to ncsu-coreswitch1.

Running a cable trace on cable #7 results in a Server Error.

dmi01-akron-rtr01 view:

Cable #7 detail:

GigabitEthernet0/0/0 cable trace result: