Associations are created in the Network Model portion of the SpectroSERVER database.
An Association is made of a Left-Hand model, a Relation, and a Right-Hand model.
We can see associations in the database by using the Command Line Interface (CLI).
Let us look at the Associations of NewDevice.
We can use the CLI to find the model handle of NewDevice and then look at the associations with NewDevice.
We can see that NewDevice is involved with only 1 association:
112LAN Collects NewDevice
We see that:
Boston Network Collects 112LAN
112LAN Collects Boston_server_switch
112LAN Collects Central_Printer
112LAN Collects Boston_Mail_Server
112LAN Collects NewDevice
If you refer back to the first Picture, you will notice that there is NO association in the database between the 112LAN container and the Boston_1 router.
This is because Boston_1 is an Off-Page Reference in the view. There is a rule within the Universe Heirarcy that forces a model to be associated with only 1 universe container at any 1 instance in time.
Since a device model can only be associated with a single Universe container, it shows up in the 112LAN container as an Off-Page reference so that the connection to the Boston_server_switch can be visualized. (see the first picture)
In addition, if we look at the List tab of the 112LAN container, we notice that it only shows the device models that have a Collects relation with the 112LAN container. (Boston_1 is not shown in this list view because it is involved in a Collects relation with "Boston Network")
Cut, Copy, Paste and Remove simply manipulate Associations.
With this example, we have learned about the nature of LostFound. A device model will be associated with LostFound if it has no Assocations with any other Container. We will revisit this idea later on.
Cut: Removes the model from the existing view and allows it to be pasted.
Paste: Creates an association between the device model and the container. Note: the NewDevice model has consistently stayed in the SS database. The only thing we have done to the database so far has been to change the associations of the NewDevice model.
To investigate "Copy" we need to create another container OUTSIDE of the Universe Heirarchy. Let us create a Static Global Collection, COPY the NewDevice and PASTE it into that container.
Notice after the PASTE, we can see NewDevice simultaniously in both the Test_GC container and the 112LAN container.
But what really happened here? We can see by looking at the associations of NewDevice.
The "COPY" operation does NOT duplicate the NewDevice model.
Copy: Allow the selected device model to be pasted. (The paste operation simply created an association with the Global Collection.)
This means that there is an association beween each of the Global Collections and the NewDevice Model
The important idea here is that the NewDevice model ONLY EXISTS ONCE in the SpectroSERVER Database.
Visualizing in multiple places in the GUI is simply a graphical representation of those multiple associations.
Let us investigate REMOVE by removing Central_Printer and NewDevice from the 112LAN.
Notice that the "pop-up" of the Remove button states ONLY that it will "Remove the selected item in this Topology view".
It makes NO mention of making these item available for Paste. This is the difference between Cut and Remove.
Cut allows for pasting, Remove does not allow for pasting.
Notice that the Central_Printer still has an Assocation with the the port of the Boston_server_switch.
0x100212 Boston_server_switch_Et0/4 Connects_to 0x1001cb Central_Printer
To summarize the actions that manipulate associations:
Cut: Destroys the association with the container and allows the device model to be pasted.
Paste: Creates an association between the device model and the container.
Copy: Allow the selected device model to be pasted.
Remove: Destroys the association with the container and DOES NOT allows the device model to be pasted.
I hope this clarifies Cut, Copy, Paste, Remove and Delete.