Layer7 API Management

Expand all | Collapse all

Gateway v10 & Portal 4.5 - error while Enrollment

  • 1.  Gateway v10 & Portal 4.5 - error while Enrollment

    Posted 11-30-2020 04:07 AM
      |   view attached
    Hello All,

    I am trying to enroll Gateway v10 with Portal 4.5, while enrollment I am getting below error,

    Note: Error attached as text file.

    Checks done:
    1- Private key alias - ssl (present)
    2- Shared Portal Resource - Installed while installing OTK 4.4 solution kit

    What can be cause of failure and how can I resolve this?

    Unable to enroll: RESTMAN failed with result: <class com.l7tech.policy.assertion.AssertionStatus: 0=FINE:No Error>, httpStatus: 409, body: <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <l7:Item xmlns:l7="http://ns.l7tech.com/2010/04/gateway-management">
    <l7:Name>Bundle mappings</l7:Name>
    <l7:Type>BUNDLE MAPPINGS</l7:Type>
    <l7:TimeStamp>2020-11-30T00:58:13.425-08:00</l7:TimeStamp>
    <l7:Link rel="self" uri="/1.0/bundle"/>
    <l7:Resource>
    <l7:Mappings>
    <l7:Mapping action="NewOrExisting" actionTaken="UsedExisting" srcId="0000000000000000ffffffffffffec76" targetId="0000000000000000ffffffffffffec76" targetUri="/1.0/folders/0000000000000000ffffffffffffec76" type="FOLDER">
    <l7:Properties>
    <l7:Property key="FailOnNew">
    <l7:BooleanValue>true</l7:BooleanValue>
    </l7:Property>
    </l7:Properties>
    </l7:Mapping>
    <l7:Mapping action="Delete" actionTaken="Ignored" srcId="8369c60dcdf7fc3281ff0e8239f2245e" type="SERVER_MODULE_FILE"/>
    <l7:Mapping action="NewOrUpdate" actionTaken="Ignored" srcId="69c60df0e823fc3239f2c81f245e8df7" type="SERVER_MODULE_FILE"/>
    <l7:Mapping action="NewOrUpdate" actionTaken="Ignored" srcId="e8df70e8269c60df81f2453fc3239f2c" type="SERVER_MODULE_FILE"/>
    <l7:Mapping action="NewOrUpdate" actionTaken="CreatedNew" srcId="69c60df0e823fc3239f2c81f245e8df7" targetId="69c60df0e823fc3239f2c81f245e8df7" targetUri="/1.0/serverModuleFiles/69c60df0e823fc3239f2c81f245e8df7" type="SERVER_MODULE_FILE"/>
    .
    .
    <l7:Mapping action="NewOrUpdate" actionTaken="CreatedNew" srcId="0744d7453720999acaa7a04311e4cf7c" targetId="0744d7453720999acaa7a04311e4cf7c" targetUri="/1.0/clusterProperties/0744d7453720999acaa7a04311e4cf7c" type="CLUSTER_PROPERTY">
    <l7:Properties>
    <l7:Property key="MapBy">
    <l7:StringValue>name</l7:StringValue>
    </l7:Property>
    </l7:Properties>
    </l7:Mapping>
    .
    .
    <l7:Mapping action="NewOrUpdate" actionTaken="CreatedNew" srcId="b4cf444ea1a0d97635e332116c4e0af9" targetId="b4cf444ea1a0d97635e332116c4e0af9" targetUri="/1.0/policies/b4cf444ea1a0d97635e332116c4e0af9" type="POLICY"/>


  • 2.  RE: Gateway v10 & Portal 4.5 - error while Enrollment

    Broadcom Employee
    Posted 12-04-2020 10:44 AM
    Hi,

    Have you looked at the corresponding policy that is causing conflict?
    What is the name of the policy? Please be sure that there is no global policy published before enrollment. 

                <l7:Mapping action="NewOrUpdate" errorType="UniqueKeyConflict" srcId="b4bff64ea3a845db60b78151a87dc1e2" type="POLICY">
                    <l7:Properties>
                        <l7:Property key="ErrorMessage">
                            <l7:StringValue>(name) (internalTag, type)  must be unique</l7:StringValue>



  • 3.  RE: Gateway v10 & Portal 4.5 - error while Enrollment

    Broadcom Employee
    Posted 12-04-2020 10:45 AM
    Hi,

    Have you looked at the corresponding policy that is causing conflict?
    What is the name of the policy? Please be sure that there is no global policy published before enrollment. 

                <l7:Mapping action="NewOrUpdate" errorType="UniqueKeyConflict" srcId="b4bff64ea3a845db60b78151a87dc1e2" type="POLICY">
                    <l7:Properties>
                        <l7:Property key="ErrorMessage">
                            <l7:StringValue>(name) (internalTag, type)  must be unique</l7:StringValue>



  • 4.  RE: Gateway v10 & Portal 4.5 - error while Enrollment

    Posted 12-08-2020 06:20 AM
    Hello Mert,

    The issue got resolved.

    Reboot was required on the second node of the cluster. After which I was able to enroll portal with gateway.

    Regards,
    Aniket