This question was originally posted on DCIM Support by firstname.lastname@example.org on 2017-08-09
I've created a FOBOT (Let's call it FOBOT A) with "New Port Configurations" to represent different slots in the FOBOT. This FOBOT would represent the end of row distribution frame which connects to the other racks within the row.
The back connections to other FOBOTS are complete. So for example FOBOT A now has back connections to FOBOT B and FOBOT C, each in different rack.
I am trying to connect two devices to each other end to end. So Device B connects to FOBOT B, which then reaches FOBOT A on a back connect. I can do this for Device C and FOBOT C also. However I am having trouble trying to cross connect on the front of FOBOT A within itself, so that the devices are connected, end to end.
Is this possible, or must it be done with different types of objects, or multiple objects? When I use the connect tool it does not appear to let you to connect an object to itself.
This answer was originally posted on DCIM Support by Ed Tarento on 2017-08-09
Yes it is possible. Your final step is to use the Connection Tool to make a connection from your FOBOT A to FOBOT A. In my example I have used RJ45. PPB has ports 1-5 back to back to PPA 1-5 and PPB 6-10 back to back to PPC 6-10.
PPB port 1 connects to PPB port 6
This comment was originally posted on DCIM Support by email@example.com on 2017-08-10
Thanks for the reply. I've setup a similar scenario as you've discussed to demonstrate what I'm running into.
PPB:1 back connect to PPA:1
PPB13: back connect to PPC:1
I can connect the top device to the PPA:1 front and it maps automatically to PPB:1 via I assume the back connect, but I cannot proceed further to do a cross connect within PPB:1 to PPB:13. When using the connect tool in the rack pane I get a not allowed symbol. Also even typing it out in the device route (2nd screenshot) does not give me the option to go in rack to the same patch panel, even though it lists the other patch panels in the rack. Seems like must be doing something blatantly wrong, but don't know what.
Running version 7.4.5, using the patch panels in the pre-existing Genomes.
This comment was originally posted on DCIM Support by Ed Tarento on 2017-08-10
Ah ha, I suspect your old DCO version is what's causing you the issue - my test was 8.x You might confirm my guess by trawling the release notes or contacting SE support (or perhaps someone else might post and confirm)
Discuss challenges in energy and automation with 30,000+ experts and peers.
Find answers in 10,000+ support articles to help solve your product and business challenges.
Find peer based solutions to your questions. Provide answers for fellow community members!