Device Groups

[DCIM_Support]

I have devices sorted into device groups, but it seems that every time I browse the groups I find some that are under other groups and when i look at it the group listed for it is the proper one. Why would i see the device in 2 places?

tks dave

(CID:89063915)

[DCIM_Support]

Hi Dave,

If you create a device group and then create another device group below it as a hierarchy will you be able to see devices in both groups. This is expected behavior.

Is this what you are seeing ?

BR

Jesper

(CID:89063935)

[DCIM_Support]

Jesper,

No, that is not what I am seeing. The odd device after being moved to a device group will randomly also display in a upstream window. when I check it does also show as being assigned to the other group and also shows up there but in the map view I can also see it else where. I can clear it by moving to unassigned and back to the proper group but randomly other devices will seem to just missdisplay.

dave

(CID:89063937)

[DCIM_Support]

Hi Dave, welcome to the community! I'd like to ask you to use "add comment" when commenting on an answer instead of using "your answer". Thanks.

(CID:89064041)

[DCIM_Support]

Do you have a discovery set up that puts discovered devices into a group?

(CID:89063951)

[DCIM_Support]

No. These are all manual discoveries that I added to unassigned then sorted to the proper place. It works but some just random show up in 2 groups. I move it again and 2 others break somewhere else.

(CID:89063953)

[DCIM_Support]

Hi Dave,

I'm afraid, this happens mostly when the devices discovered are flying in DHCP. When they reboot themselves or just loose their network configurations for whatsoever reason, they catch new IPs, still leaving behind the old discoveries(with same name). Please clarify on this. It would be helpful if you could help us with some screenshots.

Have a great day!

(CID:89064085)

[DCIM_Support]

All of my devices are static ip assigned. This is not really an orphaned device as much as a rogue copy, both copies are good and you can see everything on the remote device. It is more that the copy shows somewhere in the upstream device folders. But it is always within a parent folder. If you remove either copy from the group the will both be removed. Sometimes you can see it in the client with map view and sometimes it is just on the web client that you can see it. I am only at about 300 devices and did double the cpu, disk and ram and oddly enough that made it worse or the issue gets worst as the device count is increasing. Tks dave

(CID:89064118)

[DCIM_Support]

Dear Dave,

Please help me understand this.  if you have a device group named parent 1 and sub groups under that parent like sub 1.1 and sub 1.2, if you move the device to sub 1.2, the parent 1, may also show this device? If this is the case, that is default. I see this as well. Are you using "Shift" Key while moving the devices into other groups after discovery? Using shift key will actually create a copy of the device & the device would appear in both the groups. A few screen shots to elaborate the issue here would do better 😀

(CID:89064336)

[DCIM_Support]

Yes, If you view devices you will see all sub devices. This is when I view map view that I see the device where it should not be. It is not because of a copy error, after I am done building the device groups there is no devices in other spots. Then as you log in from time to time you see one here and there. I have noticed that it is tied to the utilization of the server. when we were having the CPU issues it was really bad. Now it is just one or 2 per day that I am seeing. I see these in the web view as well as the client but because I see it on one it is not always there on the other... I believe that is more of a cashing issue between the actual client and web view. dave

(CID:89555390)

[DCIM_Support]

Hi Dave, If possible, could you please attach a screenshot showing the problem? I think that would help clarifying the issue.

(CID:89064394)

[DCIM_Support]

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.