Switch Port management - Recording Who/what connected
New question posed recently was how the system can be used to record the switch port a specific asset is connected to.
Our legacy system we defined each switch port and the outlet ports in the building and recorded which outlet port was connected to which switch port.
We then allocated an asset to an outlet port. So by association we could determine which switch/switch port an asset was connected.
So if we had a switch issue we could proactively advise impacted users for instance and arrange appropriate time to move them if needed.
Also if a pair of workstations are moved we just update the link for the workstation to floor port and the switchport allocation remains unaffected.
The two ways i've come up with in SDP are
Using additional fields seems easy BUT I don't believe we can ensure that the same port or outlet are used more than once.
Components seems a very visual way of doing it but more long winded.
Neither way offer a relationship/heirarchy so moving assets means more work than previously.
Anyone any recommendations about how they've tackled the issue, even if it is using alternative application to record that info, although I'm keen not to have to go off and develop a small access/sql based solution just for this unless I really have to.
Regards,
Andy
Our legacy system we defined each switch port and the outlet ports in the building and recorded which outlet port was connected to which switch port.
We then allocated an asset to an outlet port. So by association we could determine which switch/switch port an asset was connected.
So if we had a switch issue we could proactively advise impacted users for instance and arrange appropriate time to move them if needed.
Also if a pair of workstations are moved we just update the link for the workstation to floor port and the switchport allocation remains unaffected.
The two ways i've come up with in SDP are
-
Asset Additional Fields
-
Asset Components
Using additional fields seems easy BUT I don't believe we can ensure that the same port or outlet are used more than once.
Components seems a very visual way of doing it but more long winded.
Neither way offer a relationship/heirarchy so moving assets means more work than previously.
Anyone any recommendations about how they've tackled the issue, even if it is using alternative application to record that info, although I'm keen not to have to go off and develop a small access/sql based solution just for this unless I really have to.
Regards,
Andy