VoyenceControl: Blue Coat SG Web Proxy devices fail to pull config after discovery
search cancel

VoyenceControl: Blue Coat SG Web Proxy devices fail to pull config after discovery

book

Article ID: 303566

calendar_today

Updated On:

Products

VMware

Issue/Introduction

Symptoms:



 

Blue Coat SG Web Proxy devices discover, but fail to pull running config with error:

Timeout while waiting for enable prompt
migrateSessionState(): failed to enter enable mode


Environment

VMware Smart Assurance - NCM

Cause

The discovered device does not have a privilege credential associated due to a driver defect.

Resolution

Make the following changes on all device servers.

  1. source /etc/voyence.conf
     
  2. mkdir -p $VOYENCE_HOME/custompackage/bluecoat/sg
     
  3. cp $VOYENCE_HOME/package/bluecoat/sg/cli.inc $VOYENCE_HOME/custompackage/bluecoat/sg
     
  4. vi $VOYENCE_HOME/custompackage/bluecoat/sg/cli.inc
     
  5. Right below the addPromptStates function near the top of this file, add these lines:

    vars {
        var<const> HighestPrivLevel_ = 15;
        var<const> PrivLevels_       = 15;
    }; 
           
    public getMaxEnableModeLevel() {
        retVal = HighestPrivLevel_;
    }
    public getEnableModeLevels() {
        retVal = PrivLevels_;
    }


    Example:
    addPromptStates(var session) {
        # assumes use of *Prompts.xml in package directory
        # remove embedded whitespace from name provided in driver declaration -- no s///
        #  equivalent in DASL, alas...
        var packageName = strreplace(strreplace(PACKAGENAME, " ", "", true), "  ", "", true);
        addPromptStatesXML(session, packageName+"Prompts.xml", packageName, "", "");
        # add any explicit states elsewhere
    }

    vars {
        var<const> HighestPrivLevel_ = 15;
        var<const> PrivLevels_       = 15;
    };
    public getMaxEnableModeLevel() {
        retVal = HighestPrivLevel_;
    }
    public getEnableModeLevels() {
        retVal = PrivLevels_;
    }

    public
    enterEnableMode(var session) {

     
  6. Save and quit this file
     
  7. Restart the voyence service:
    /etc/init.d/voyence restart


Additional Information

$VOYENCE_HOME refers to the home location of VoyenceControl, typically /opt/voyence.