Skip to main content
cmaheu
Staff
cmaheu
Staff
December 30, 2020

Technical Tip: Host assumes adapter record role after manually adding Vendor OUI

  • December 30, 2020
  • 0 replies
  • 1044 views

Description
Unable to manually add Vendor OUI without specifying a role.  Consequently, the host record assumes the role of the OUI entry, potentially affecting the matching of any policies based on host role.

Scope
Version: 8.6

Solution

Remove role from newly created OUI entry.  Contact Support for assistance.
 
 


Workaround:

1. Login to appliance CLI as root
2. Make a copy of /bsc/campusMgr/ui/ROOT/VendorOuiActions.jsp
cp /bsc/campusMgr/ui/ROOT/VendorOuiActions.jsp /bsc/campusMgr/ui/ROOT/temp.jsp
3. Edit /bsc/campusMgr/ui/ROOT/VendorOuiActions.jsp  
 
Look for:
        if(errorStr == null){
             if(vc == null){
                 vc = new VendorCode();
             }
             vc.setRole(role);
             vc.setVendorAlias(vendorAlias);
             vc.setVendorName(vendorName);

(Should be around line 233)

Change
vc.setRole(role);

To
vc.setRole(null);

4. Save file.
5. From the Administration UI, Navigate to System > Settings > Identification > Vendor OUI.
6. Select the new Vendor OUI entry and click Modify.
7. Press OK (do not make any changes).
8. Validate that the NAC-Default role is no longer set for OUI entry.
9. From the CLI, copy the original file back in place.
cp /bsc/campusMgr/ui/ROOT/temp.jsp /bsc/campusMgr/ui/ROOT/VendorOuiActions.jsp

Related Articles

Technical Tip: Host fails to register or multiple host records are created

Terms & ConditionsAccessibility statement