Upgrade vShield App to NSX Firewall

 
Unfortunately I am having issues in my lab, so I was unable to perform the upgrade of the virtual wires to logical switches, which is a prerequisite to upgrade the Firewall. I was getting the following error, and I am currently investigating to see what might be causing it. If anyone has any feedback or resolves this issue please let me know. Luckily, the steps to upgrade the NSX firewall are fairly simple, so I will go through the steps at the bottom.
 
2
 

2015-05-26 18:57:22.805 GMT  WARN http-nio-127.0.0.1-7441-exec-1 RemoteInvocationTraceInterceptor:87 - Processing of VsmHttpInvokerServiceExporter remote call
 resulted in fatal exception: com.vmware.vshield.vsm.nwfabric.facade.NetworkPrepFacade.modifyFeature
com.vmware.vshield.vsm.nwfabric.exception.NetworkFabricException:
core-services:7005:Invalid service id : {0}
        at com.vmware.vshield.vsm.nwfabric.service.impl.NetworkPrepServiceImpl.modifyFeature_aroundBody6(NetworkPrepServiceImpl.java:148)
        at com.vmware.vshield.vsm.nwfabric.service.impl.NetworkPrepServiceImpl$AjcClosure7.run(NetworkPrepServiceImpl.java:1)
        at org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:149)
        at com.vmware.vshield.vsm.aspects.security.VsmSecuredAspect.secureCheck(VsmSecuredAspect.java:105)
        at com.vmware.vshield.vsm.aspects.security.VsmSecuredAspect.ajc$inlineAccessMethod$com_vmware_vshield_vsm_aspects_security_VsmSecuredAspect$com_vmware
_vshield_vsm_aspects_security_VsmSecuredAspect$secureCheck(VsmSecuredAspect.java:1)

 
Log into the vSphere Client and Navigate to Networking & Security -> Installation -> Host Preparation and ujnder the Firewall tab you should see a button surrounded in green with the word Upgrade
 
1
 

3 Comments

  1. Matt Larson -  July 30, 2015 - 3:09 pm 212

    Hi Sean,

    Were you able to resolve this issue? Running into the same thing going from 6.1.2 to 6.1.4. It’s a lab, of course.

    Thanks,

    Matt

    Reply
  2. Matt Larson -  July 31, 2015 - 12:36 pm 213

    Solved it…I had neglected to upgrade the controllers from the NSX Manager section of the Management page.

    Reply
    • Sean Whitney -  August 3, 2015 - 12:08 pm 217

      Hi Matt,

      Good info, thanks for sharing!

      Sean

      Reply

Leave A Comment

Your email address will not be published. Required fields are marked (required):

Back to Top