Smarts IP: What happens when we tell smarts to explicitly unmanage a port
search cancel

Smarts IP: What happens when we tell smarts to explicitly unmanage a port

book

Article ID: 331815

calendar_today

Updated On:

Products

VMware Smart Assurance

Environment

VMware Smart Assurance - SMARTS

Resolution

When we tell an IP  Domain to NOT manage a port (through dmctl or GUI), two properties are set on the port.
 
1: isManaged: Set to false
2: Managed_State: Set to "EXPLICITLY_UNMANAGED".

 
For troubleshooting purposes, we have shown what to look for in the logs.

NOTE: You will have to set the discovery debug commands to on and then you will see this type of activity in the domain log:

[2016/05/03 15:15:06 +026ms] t@2648770880 Discovery #14
ASL_MSG-*-ASLP-discovery/ic-if-state.asl: discovery/ic-if-state.asl: insert 4, EXPLICITLY_MANAGED to GA_StringDictionary::Discovery-Interface-ManagementState-Table-2648770880

.
.
.
[2016/05/03 15:15:06 +029ms] t@2648770880 Discovery #14
ASL_MSG-*-ASLP-discovery/ic-if-state.asl: Description: GigabitEthernet0/2 -> 4|EXPLICITLY_MANAGED|FULLDUPLEX:ETHERLIKE_MIB

.
.
.
[2016/05/03 15:15:18 +197ms] t@2648770880 Discovery #14




ASL_MSG-*-ASLP-discovery/ic-end-if-state.asl: Description: GigabitEthernet0/2 -> 4|EXPLICITLY_MANAGED|FULLDUPLEX:ETHERLIKE_MIB


NOTE: The above comments are because of the  ic-post-port-manager.asl which is the script responsible for managing and un-managing ports.