API Connect

 View Only
  • 1.  Getting an error when register a Gateway service - APIC version 10.0.4.0

    Posted Fri September 23, 2022 10:17 AM
    Hi Team
    I am looking for guidance to resolve below issue.
    We have configured Data Power API Gateway for multiple peering object on gateway services external to Kubernetes. When we tried to register a Gateway service in Cloud Manager, we are getting below error.(APIC version 10.0.4.0)

    System Log
    1:09:49 AM apic-gw-service debug 288 0x80e0084c apic-gw-service (default): utils:RestTranslator: Message to be sent in response to APIM: Unable to perform initial registration for API Management. Error: Error: connect ETIMEDOUT 192.168.72.11:443
    1:09:49 AM apic-gw-service error 288 0x88e00127 apic-gw-service (default): Stack trace for previous error: at new RequestError (/root/gateway-director/node_modules/request-promise-core/lib/errors.js:14:15) at Request.plumbing.callback (/root/gateway-director/node_modules/request-promise-core/lib/plumbing.js:87:29) at Request.RP$callback [as _callback] (/root/gateway-director/node_modules/request-promise-core/lib/plumbing.js:46:31) at self.callback (/root/gateway-director/node_modules/request/request.js:185:22) at Request.emit (events.js:400:28) at Request.onRequestError (/root/gateway-director/node_modules/request/request.js:881:8) at ClientRequest.emit (events.js:400:28) at TLSSocket.socketErrorListener (_http_client.js:475:9) at TLSSocket.emit (events.js:400:28) at emitErrorNT (internal/streams/destroy.js:106:8) at emitErrorCloseNT (internal/streams/destroy.js:74:3) at processTicksAndRejections (internal/process/task_queues.js:82:21)
    1:09:49 AM apic-gw-service error 288 0x88e000b3 apic-gw-service (default): Unable to perform initial registration for API Management. Error: RequestError: Error: connect ETIMEDOUT 192.168.72.11:443
    1:09:49 AM apic-gw-service debug 288 0x80e0084c apic-gw-service (default): routes:management-interface:providers:apim:APIMController: A registration event initiated by X-Request-Id: 23a059eeec8de861808c097cfcfb45dd failed to process.
    1:09:49 AM apic-gw-service debug 288 0x80e0084c apic-gw-service (default): lib:management:apim:APIMManager: Removed EXCLUSIVE registration lock: 2803701897-Landlord-apiconnect-pr-apic-dpgw1.nsb.local:ee7cc11f-657c-4050-b408-046747b9b38c:1663909726248:APIManager(register)
    1:09:49 AM apic-gw-service debug 288 0x80e0084c apic-gw-service (default): lib:Flags: Releasing the registration lock: 2803701897-Landlord-apiconnect-pr-apic-dpgw1.nsb.local:ee7cc11f-657c-4050-b408-046747b9b38c:1663909726248:APIManager(register).
    1:09:49 AM apic-gw-service debug 288 0x80e0084c apic-gw-service (default): lib:management:apim:APIMManager: Failed to register APIM instance with Gateway Service.
    1:09:49 AM apic-gw-service error 288 0x88e00127 apic-gw-service (default): Stack trace for previous error: at new RequestError (/root/gateway-director/node_modules/request-promise-core/lib/errors.js:14:15) at Request.plumbing.callback (/root/gateway-director/node_modules/request-promise-core/lib/plumbing.js:87:29) at Request.RP$callback [as _callback] (/root/gateway-director/node_modules/request-promise-core/lib/plumbing.js:46:31) at self.callback (/root/gateway-director/node_modules/request/request.js:185:22) at Request.emit (events.js:400:28) at Request.onRequestError (/root/gateway-director/node_modules/request/request.js:881:8) at ClientRequest.emit (events.js:400:28) at TLSSocket.socketErrorListener (_http_client.js:475:9) at TLSSocket.emit (events.js:400:28) at emitErrorNT (internal/streams/destroy.js:106:8) at emitErrorCloseNT (internal/streams/destroy.js:74:3) at processTicksAndRejections (internal/process/task_queues.js:82:21)
    1:09:49 AM apic-gw-service error 288 0x88e001ff apic-gw-service (default): Unable to get webhook subscription at https://platform-api.pr-apic-mgr.nsb.local/api/cloud/webhooks. Error: RequestError: Error: connect ETIMEDOUT 192.168.72.11:443
    1:08:46 AM apic-gw-service information 288 0x88e0007a apic-gw-service (default): Registering cloud webhook: https://platform-api.pr-apic-mgr.nsb.local/api/cloud/webhooks
    1:08:46 AM apic-gw-service debug 288 0x80e0084c apic-gw-service (default): utils:persistence:lib:RedisClientWrapper: Selecting from table name: backwardscompat
    1:08:46 AM apic-gw-service debug 288 0x80e0084c apic-gw-service (default): lib:management:apim:APIMManager: Storing access_token for catalogId (cloud) with maxAge 25200000ms
    1:08:46 AM apic-gw-service debug 288 0x80e0084c apic-gw-service (default): lib:management:apim:APIMManager: APIm expires_in set to: 28800
    1:08:46 AM apic-gw-service debug 288 0x80e0084c apic-gw-service (default): lib:management:apim:APIMManager: Unable to find access_token in cache for catalogId: cloud
    1:08:46 AM apic-gw-service debug 288 0x80e0084c apic-gw-service (default): lib:management:apim:APIMManager: Forcing a new access_token for catalogId: cloud
    1:08:46 AM apic-gw-service debug 288 0x80e0084c apic-gw-service (default): lib:management:apim:APIMManager: getAccessTokenFromCache - catalogId: cloud webhookId: undefined platformAPIEndpoint: https://platform-api.pr-apic-mgr.nsb.local
    1:08:46 AM apic-gw-service debug 288 0x80e0084c apic-gw-service (default): utils:persistence:lib:RedisClientWrapper: no records found
    1:08:46 AM apic-gw-service debug 288 0x80e0084c apic-gw-service (default): utils:persistence:lib:RedisClientWrapper: Selecting from table name: config
    1:08:46 AM apic-gw-service information 288 0x88e00285 apic-gw-service (default): This peer has the oldest software version in the peer group, setting compatibility level to v10_0_0_0.
    1:08:46 AM apic-gw-service information 288 0x88e00163 apic-gw-service (default): Peer gateways running on same build level. Peer gateway list: {"2710891463-Landlord-apiconnect-pr-apic-dpgw3.nsb.local":{"url":"https://none:5550","gwdhost":"172.22.10.141","heartbeat":"1663909721015","env":"apigateway","version":"IDG.10.0.4.0","build":"337832","builddate":"2021/12/03 12:54:08","compatibility":"10.0.4.0"},"4216933872-Landlord-apiconnect-pr-apic-dpgw2.nsb.local":{"url":"https://none:5550","gwdhost":"172.22.10.140","heartbeat":"1663909724381","env":"apigateway","version":"IDG.10.0.4.0","build":"337832","builddate":"2021/12/03 12:54:08","compatibility":"10.0.4.0"},"2803701897-Landlord-apiconnect-pr-apic-dpgw1.nsb.local":{"url":"https://none:5550","gwdhost":"172.22.10.139","heartbeat":"1663909721969","env":"apigateway","version":"IDG.10.0.4.0","build":"337832","builddate":"2021/12/03 12:54:08","compatibility":"10.0.4.0"}}
    1:08:46 AM apic-gw-service debug 288 0x80e0084c apic-gw-service (default): utils:persistence:lib:RedisClientWrapper: no records found
    1:08:46 AM apic-gw-service debug 288 0x80e0084c apic-gw-service (default): utils:persistence:lib:RedisClientWrapper: Selecting from table name: config
    1:08:46 AM apic-gw-service debug 288 0x80e0084c apic-gw-service (default): lib:Flags: Got the registration lock: 2803701897-Landlord-apiconnect-pr-apic-dpgw1.nsb.local:ee7cc11f-657c-4050-b408-046747b9b38c:1663909726248:APIManager(register).
    1:08:46 AM apic-gw-service debug 288 0x80e0084c apic-gw-service (default): lib:Flags: Waiting for the registration lock: 2803701897-Landlord-apiconnect-pr-apic-dpgw1.nsb.local:ee7cc11f-657c-4050-b408-046747b9b38c:1663909726248:APIManager(register) Timeout: 1000.
    1:08:46 AM apic-gw-service debug 288 0x80e0084c apic-gw-service (default): lib:management:apim:APIMManager: Cloud Registration gateway_service data: {"name":"api-gateway-service","title":"API gateway service","endpoint":"https://pr-apic-dpgw1.nsb.local:3000","api_endpoint_base":"https://pr-apic-dpgw1-fe.nsb.local:443","tls_client_profile_url":"/api/orgs/820e5fa4-dd0a-4f5f-854e-739f962beebb/tls-client-profiles/abc588d3-b091-4be9-9c43-954e4773b983","gateway_service_type":"datapower-api-gateway","visibility":{"type":"public"},"sni":[{"host":"*","tls_server_profile_url":"/api/orgs/820e5fa4-dd0a-4f5f-854e-739f962beebb/tls-server-profiles/c1a0b8ce-38aa-4d17-a6d8-c6b24662678f","tls_server_profile":{"type":"tls_server_profile","api_version":"2.0.0","id":"c1a0b8ce-38aa-4d17-a6d8-c6b24662678f","name":"tls-server-profile-default","version":"1.0.0","title":"Default TLS server profile","summary":"Default TLS server profile for gateway services for API execution","protocols":["tls_v1.2","tls_v1.3"],"ciphers":["TLS_AES_256_GCM_SHA384","TLS_CHACHA20_POLY1305_SHA256","TLS_AES_128_GCM_SHA256","TLS_AES_128_CCM_SHA256","TLS_AES_128_CCM_8_SHA256","ECDHE_ECDSA_WITH_AES_256_GCM_SHA384","ECDHE_RSA_WITH_AES_256_GCM_SHA384","ECDHE_ECDSA_WITH_AES_256_CBC_SHA384","ECDHE_RSA_WITH_AES_256_CBC_SHA384","ECDHE_ECDSA_WITH_AES_256_CBC_SHA","ECDHE_RSA_WITH_AES_256_CBC_SHA","DHE_DSS_WITH_AES_256_GCM_SHA384","DHE_RSA_WITH_AES_256_GCM_SHA384","DHE_RSA_WITH_AES_256_CBC_SHA256","DHE_DSS_WITH_AES_256_CBC_SHA256","DHE_RSA_WITH_AES_256_CBC_SHA","DHE_DSS_WITH_AES_256_CBC_SHA",
    1:08:46 AM apic-gw-service debug 288 0x80e0084c apic-gw-service (default): lib:management:apim:APIMManager: Cloud Registration platform_api_endpoint: https://platform-api.pr-apic-mgr.nsb.local/api
    1:08:46 AM apic-gw-service information 288 0x88e000cc apic-gw-service (default): Validation of cloud registration data completed successfully in 0 ms
    1:08:46 AM apic-gw-service notice 288 0x88e001c2 apic-gw-service (default): Registering API Management instance wi

    ------------------------------
    Nirmalan Rajasingam
    ------------------------------


  • 2.  RE: Getting an error when register a Gateway service - APIC version 10.0.4.0

    Posted Mon September 26, 2022 02:43 AM
    Is your DataPower gateway configured on a 192.168.x.x address?

    Can you ping / ssh to it (assuming you enabled the ssh interface) from a pod in the cluster?

    You need a DNS name (assuming you can reach the gateway); nip.io or xip.io can help you.

    ------------------------------
    Johan Thole
    IT Specialist
    IBM Cloud Nederland BV
    Netherlands
    ------------------------------



  • 3.  RE: Getting an error when register a Gateway service - APIC version 10.0.4.0

    IBM Champion
    Posted Mon September 26, 2022 04:27 AM
    I experienced the same situation and fixed it rebooting the device
    The port was stuck for another service, and after rebooting it the port was free to be used
    Not sure if the scenario here, but it's a try
    Try first, of course, what Johan mentioned below - Which I suppose you did already

    Thanks!

    ------------------------------
    Leandro Takeda
    ------------------------------



  • 4.  RE: Getting an error when register a Gateway service - APIC version 10.0.4.0

    Posted Sun February 26, 2023 09:02 AM

    Hi All...

    I have installed APIC v 10.0.5.2 and trying to add gateway service in cloud manager and getting similar type of error as above. I tried rebooting Datapower as suggested, but, no luck. In addition, I tried to telnet the destination host and port from API manager VM and it is successful.

    The below error is thrown by Datapower when cloud manager returns error

    17:32:36 <type xmlns:dp="http://www.datapower.com/schemas/management" xmlns:env="http://www.w3.org/2003/05/soap-envelope">apic-gw-service</type> <display xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">error</display> 321     0x88e00127 apic-gw-service (default): Stack trace for previous error: at Function.AxiosError.from (/root/gateway-director/node_modules/axios/dist/node/axios.cjs:725:14) at RedirectableRequest.handleRequestError (/root/gateway-director/node_modules/axios/dist/node/axios.cjs:2465:25) at RedirectableRequest.emit (events.js:400:28) at ClientRequest.eventHandlers.<computed> (/root/gateway-director/node_modules/axios/node_modules/follow-redirects/index.js:14:24) at ClientRequest.emit (events.js:400:28) at TLSSocket.socketErrorListener (_http_client.js:475:9) at TLSSocket.emit (events.js:400:28) at emitErrorNT (internal/streams/destroy.js:106:8) at emitErrorCloseNT (internal/streams/destroy.js:74:3) at processTicksAndRejections (internal/process/task_queues.js:82:21)
    17:32:36 <type xmlns:dp="http://www.datapower.com/schemas/management" xmlns:env="http://www.w3.org/2003/05/soap-envelope">apic-gw-service</type> <display xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">error</display> 321     0x88e000b3 apic-gw-service (default): Unable to perform initial registration for API Management. Error: Error: connect ETIMEDOUT 172.20.206.54:443
    17:32:36 <type xmlns:dp="http://www.datapower.com/schemas/management" xmlns:env="http://www.w3.org/2003/05/soap-envelope">apic-gw-service</type> <display xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">error</display> 321     0x88e000de apic-gw-service (default): Unable to obtain access token from https://platform-api.testapimgrsit.testad.com/api/token
    Datapower Gateway registration error in API Cloud manager

    ,



    ------------------------------
    Ashok Beshra
    ------------------------------



  • 5.  RE: Getting an error when register a Gateway service - APIC version 10.0.4.0

    Posted Mon February 27, 2023 10:31 AM

    Hi!

    I was also facing exact same issue which got solved with rebooting device as Leandro Takeda have answered.

    Thanks!



    ------------------------------
    Rajubhai Rathod
    ------------------------------



  • 6.  RE: Getting an error when register a Gateway service - APIC version 10.0.4.0

    Posted Fri March 03, 2023 04:01 AM

    Thank you everyone for your help in analyzing the issue. Actually, the problem in my environment was that port 443 was not opened from Datapower gateway appliance to API Management subsystem and hence it could not push some hook configuration data. The issue is fixed after firewall is provided.



    ------------------------------
    Ashok Beshra
    ------------------------------



  • 7.  RE: Getting an error when register a Gateway service - APIC version 10.0.4.0

    Posted Thu March 09, 2023 03:21 AM

    If you are doing a new install please make sure you upgrade to APIC 10.0.5. ASAP.

    All support for APIC 10.0.4 will stop in a few months time - it is a CD release and so support ends as soon as the next CD release is available (we support the last 2 (which includes 10.0.5), so when the next one comes out support will end for 10.0.4).

    We advise against customers running CD releases in production - please stick to LTS (10.0.5.x) if possible.



    ------------------------------
    Chris Dudley
    ------------------------------