Managing or unmanaging instance
search cancel

Managing or unmanaging instance

book

Article ID: 327642

calendar_today

Updated On:

Products

VMware Smart Assurance Network Observability

Issue/Introduction

  • Access ports set to Managed are changed to Unmanaged after Smarts IP re-discovery.
  • Juniper EX4200-48T switch with managed / EXPLICITLY_MANAGED ports are changing to unmanaged on re-discovery.
  • Steps to permanently change an access port to managed from unmanaged.

Environment

All Supported Smarts versions

Cause

By default, access ports in Smarts IP are unmanaged during discovery and re-discovery. If you set access ports to managed using the Smarts IP interface and re-discover the ports, the IsManaged attribute will revert to being false and the ManagedState will change from EXPLICITLY_MANAGED back to UNMANAGED.

Resolution

You can manage the access ports so that the object will be explicitly managed and the Smarts IP post-processing code will not unmanage it again. This is achieved by putting the following code into your custom post processing file i.e custom-end-post.asl, calling the manage() function with overwrite parameter set to True:

START {
     ..eol
} do {
     foreach PortName (getInstances("Port")) {
     PortObj = object(PortName);
     PortObj->manage();
     print("Port state set to Manage ->".PortObj->ManagedState);
     }
}

Similar logic can be used for any instance within Smarts.

Another Example to unmanage IP addresses that end in .254:

START {
     .. eol
} do {
      if (nodeObj->CreationClassName == "Router" ){
               foreach IP (nodeObj->getIPs()) {
                       IPObj = object(IP);
                       if ( !IPObj->isNull() && glob("<1-255>.<0-255>.<0-255>.254", IPObj->Address) && IPObj->IsManaged ) {
                            IPObj->unmanage();
                            if ( DEBUG ) { print(me . " Support:". IPObj->Address . " is now unmanaged"); }
                       }
               }
      }
    stop();
}

Additional Information

This workaround would be classified as a customization, and hence please evaluate and test this on UAT/Test environment before introducing this on to the Production environment.