In Topology builder Building group by "isManaged" criteria does not work.

Hi,

i did try myself and it does work!
you must be careful with the selected target class and also the isManaged statement must be compared to 'TRUE' or 'FALSE' be careful with upper and lower cases in SMARTS some stuff might not work ...
And you will get your new group in the groups tab ...

cheers

Fernando

pd. don't forget to save the group and regroup it

Hi,
with "true" All Ok, and we observe ALL object list including Unmanaged ???!!!!!
but with "false" does't want to work.

well,

The attributte used is the one in SAM not the one in AM-PM.
SAM's behaviour for this attribute does not rely on the status of the same attribute in AM-PM. this the explanation on SAM's admin guide

IsManaged Boolean Determines if the system is monitored by Global
Manager. Note that unmanaged elements do not
appear in the Global Manager topology.

So, if the element is in the SAM Topology the status os isManaged will be TRUE.
The only way to change that is through dmctl as follows

From /SAM/smarts/bin, issue command:
./dmctl -s invoke manage
To get run the following command:
./dmctl -s getI Interface
Likewise, to unmanage an interface run the following command:
./dmctl -s invoke unmanage
To check the status, issue command:
./dmctl -s get class:: ::IsManaged

example

./dmctl -s INCHARGE-SA invoke Switch::Switch1 unmanage

this will set up the status of your swith in SAM to unamaged and the value of IsManaged to FALSE

I did test it and it works, the only issue is that you have to write a small script in order to do so, but you can trigger it throug the console using the server actions too

cheers

Fernando