How do you save a disappearing country?
On the latest episode of Traceroute, we look at how climate change is forcing the island nation of Tuvalu to rethink what it means to be a state. For the island nation of Tuvalu, the effects of climate change are more than a warning; they’re an eviction notice. Estimates vary as to when the small chain of coral islands could vanish beneath the waves, but experts agree that Tuvalu may be uninhabitable long before then, prompting its people to set sail for a new frontier… The metaverse. Within this digital landscape, Tuvalu could potentially preserve its lands, heritage, and governance, effectively pioneering a new model for nationhood, in which a nation and its people exist in two realms—physical and virtual. But how does one go from sand to silicon while maintaining the essence of a culture? And what is the real-world environmental impact of storing a nation’s worth of data? Whether we take Tuvalu’s proposal literally or view it as a symbolic call to action, unpacking the logistics of such an ambitious project offers a glimpse at the expertise required to bring it to life—from tech experts grappling with digital economy governance to cultural preservationists digitizing traditional art and oral histories. The work forces us to ask: Can you really backup a country the way you backup a computer? And if so, what does that mean for the future of nationhood, identity, and the planet itself?Equinix-native Load Balancer-as-a-Service now in public beta
Equinix-native Load Balancer-as-a-Service. It’s now in public beta, and if you have an Equinix Metal account you can take it for a spin free of charge (while in beta) via the console or the Metal API. Making it especially powerful is its use of our global high-speed network backbone. Launch an instance, and your user traffic will automatically get in the internet’s fast lane at the closest location possible! You can read more about that—and generally about the direction of the product—in thisblog post. If you want to spin up a load balancer and feel the magic for yourself, all the details are in the docs. Here’s also a live demo from our recent developer event.Fasten your seatbelts – Traceroute explores the world of flying cars
We were promised flying cars. We were told that by the year 2000, cities would float in the clouds, robots would cut our hair, and there’d be a computer in everyone’s pocket. Well, one out of three ain’t bad. The question is, why? Why did we think the future would bring interstate moving sidewalks, but we ended up with the internet instead? In this episode of Traceroute, we take an in-depth look at why we get the technology we get…and our trail leads to three distinct factors. Helping us unravel the reason behind these factors is Mike Winterfield, Founder of Active Impact Investments, a VC firm that specializes in Green Tech. We also talk with Oliver Walker-Jones of Joby Aviation, one of several companies that are finally making flying cars, who shares his insight as to why it took almost a hundred years to get from the idea of the flying car to the reality of one.Virtual Routing and Forwarding (VRF) is now LIVE!
🚀 Exciting News! You’ve got a simpler way to connect your services deployed across Equinix products. Give Virtual Routing and Forwarding (VRF) a shot and help shape the future of VRF! 🛠️ Configure VRF through the API or UI directly, making connectivity easier than ever! 📚 For more information on what VRF is and how to use it, check out our deploy documentation page: https://deploy.equinix.com/developers/docs/metal/layer2-networking/vrf/ 🗣️ Your feedback matters! Whether it's good or bad, share your thoughts with us. We're eager to hear from you and will use your input to shape the future of VRF. Help us make it even better!The GXI Report: Your Guide to the Future of the Digital Economy
The annual Global Interconnection Index (GXI) is a crystal ball into the future of the digital economy, full of predictions and insights that redefine how we connect and thrive in a digital world. 📈 Bandwidth Growth: Watch as interconnection bandwidth skyrockets at a 34% five-year CAGR, hitting a mind-blowing 33,578 Tbps. ☁️ Multicloud Mastery: By 2025, 85% of global companies will have embraced multicloud strategies across numerous regions. It's the era of cloud without borders, enhancing flexibility and operational resilience. 🌐 Fortune 500's Digital Pivot: By 2025, 90% of Fortune 500 companies will transform into digital providers, both selling and consuming digital services. It's a shift from traditional business models to digital-first strategies. 🔄 Hardware Renaissance: The next few years will witness a doubling in hardware refresh rates, spurred by ever-improving price/performance ratios. By 2026, technology lifecycles will accelerate, keeping pace with innovation demands. 💡 Growth Through Composition: By 2026, 60% of digital growth will be propelled by composable business models, outshining mergers and acquisitions. It’s a paradigm shift towards more agile and adaptable growth strategies. 📊 Subscription Surge: A significant 80% of Enterprise digital infrastructure investment is expected to shift to subscription models by 2026. This marks a strategic move towards operational flexibility and financial predictability. Please reach out to discuss any of these developments!Looking for solutions on Platform Equinix? Try the new Solutions Catalog
Which products need to be combined to solve your infrastructure needs? How do these products work together? Are there best practices? What have other customers done? We heard you loud and clear – you need a way to find the right solutions. Check out the newly launched Solutions Catalog! As this is an evolving catalog, with us adding more resources over time, we need your help: We are looking for beta testers to share their thoughts, feedback (good and bad) with us! Is it easy to navigate? Did you find what you were looking for? Is there information missing? What is working? When would you use it? Take a quick survey or respond in the comments below. What’s Solutions Catalog? Solutions Catalog is more a reference library than anything else and we are positive that it can help you find the right solution. You can go by technology category, discover how other customers have solved business requirements through infrastructure and browse by business motivation to see which solutions help you to address these.Is there a perfect tool to bridge the physical and digital divides?
Stick around as we explore how tech both creates and disrupts our groove, and whether the secret sauce of in-person jams can really translate to the digital world. Part 1 – The Synchrony Paradox In this episode of Traceroute, we delve into a quest for the perfect tool to help bridge the physical and digital divides that increasingly appear between musicians like John and Arman. From California’s Bay Area to the buzzing streets of Hong Kong, we find a host of technologists who, spurred on by the impacts of a global pandemic, are already hard at work tackling the kind of low-latency global networking solutions that just might be the key to keeping the band in one semi-remote piece. But within this particular stack, there lies an even bigger conundrum. Because even if we somehow manifest the right tool for the job, is the magic of this so-called “vibe” even replicable? Or is there another solution altogether? Part 2 - The Synchrony Paradox In part one of our story, we sourced the perfect tool for jamming together from miles apart. Today, we’re gonna take it for a little spin. But between setup delays and spotty internet, a more nuanced issue begins to surface. Because, in navigating the challenges of remote music collaboration, we’re quickly reminded that adapting to new tech is not a one-size-fits-all endeavor. So what are we to do when the tech itself starts to harsh the vibe? And what even is this so-called vibe anyway? How are we supposed to capture it if we don’t know what “it” is? Stick around as we explore how tech both creates and disrupts our groove, and whether the secret sauce of in-person jams can really translate to the digital world.Building Highly Resilient Networks in Network Edge - Part 1 - Architecture
This is first part of a series of posts highlighting the best practices for customers who desire highly resilient networks in Network Edge. This entry will focus on the foundational architecture of Plane A and Plane B in Network Edge and how these building blocks should be utilized for resiliency. For more information on Network Edge and device plane resiliency please refer to the Equinix Docs page here. Dual Plane Architecture Network Edge is built upon astandard data center redundancy architecture with multiple pods that have dedicated power supplies and a dedicated Top of Rack (ToR) switch. It consists of multiple compute planes commonly referred to as Plane A and Plane B for design simplicity Plane A connects to the Primary Fabric network and Plane B connects to the Secondary Fabric network The most important concept for understanding Network Edge resiliency: the device plane determines which Fabric switch is used for device connections. Future posts will dive much deeper in the various ways that Network Edge devices connect to other devices, Clouds and co-location. While referred to as Plane A and Plane B, in reality there are multiple compute planes in each NE pod The actual number varies based on the size of the metro This allows devices to be deployed in a manner where they are not co-mingled on the same compute plane, eliminating compute as a single point of failure Network Edge offers multiple resiliency options that can be summarized as device options and connection options Device options are local and provide resiliency against failures at the compute and device level in the local metro This is analogous to what the industry refers to as ”High Availability (HA)” Connection resiliency is a separate option for customers that require additional resiliency with device connections (DLGs, VCs and EVP-LAN networks). This will be discussed in depth in separate sections. It is common to combine both local resiliency and connection resiliency, but it is not required—ultimately it depends on the customer’s requirements Geo-redundancy is an architecture that expands on local resiliency by utilizing multiple metros to eliminate issues that may affect NE at the metro level (not covered in this presentation) Single Devices Single devices have no resiliency for compute and device failures The first single device is always connected to the Primary Compute Plane * Single devices always make connections over the Primary Fabricnetwork Single devices can convert to Redundant Devices via the anti-affinity feature Anti-Affinity Deployment Option By default single devices have no resiliency However, single devices can be placed in divergent compute planes. This is commonly called anti-affinity and is part of the device creation workflow Checking the "SelectDiverse From" box allows customers to add new devices that are resilient to each other Customers can verify this by viewing their NE Admin Dashboard and sorting their devices by "Plane" This feature allows customer to convert a single device install to Redundant Devices By default, the first single device was deployed on the Primary Fabric The actual compute plane is irrelevant until the 2nd device is provisioned The 2nd device is deployed on the Secondary Fabric AND in a different compute plane than the first device Resilient Device Options These options provide local (intra-metro) resiliency to protect against hardware or power failures in the local Network Edge pod By default, the two virtual devices are deployed in separate compute planes (A and B) In reality there are more than two compute planes, but they are distinct from each other The primary device is connected to thePrimary Fabric network and thesecondary/passive device is connected tothe Secondary Fabric network Redundant Devices Clustered Devices Deployment Two devices, both Active, appearing as two devices in the Network Edge portal. Both devices have all interfaces forwarding Two devices, only one is ever Active. The Passive (non-Active) device data plane is not forwarding WAN Management Both devices get a unique L3 address that is active for WAN management Each node gets a unique L3 address for WAN management as well as a Cluster address that connects to the active node (either 0 or 1) Device Linking Groups None are created at device inception Two are created by default to share config synchronization and failover communication Fabric Virtual Connections Connections can be built to one or both devices Single connections are built to a special VNI that connects to the Active Cluster node only. Customer can create optional, additional secondary connection(s) Supports Geo-Redundancy ? Yes, Redundant devices can be deployed in different metros No, Clustered devices can only be deployed in the same metro Vendor Support All Vendors Fortinet, Juniper, NGINX and Palo Alto The next post will cover the best practices for creating resilient device connections with Device Link Groups and can be found here.Finish the sentence: New Year, new….
Share what's new for you this year - is it new projects, new challenges, new team members, new office chair? For us? New members to welcome to Community! In 2023, we had 1214 new members join the Equinix Community. We're looking forward to keeping you connected in 2024! Welcome our newest members! Be sure to update yourprofile imageandintroduce yourself! aanchala Abbey accesos_salas adajastrzebska aest7 alan AlbertSanchez AleksandrTaranov alewandowski Alexander_Metz AlexFromEileo anaqvi anliew arturkrysiak ASLINE astel AtsushiChiba avanherreweghe balwindersm bobbyvu bpillai Brian-McSweeney bscashman cfarrer Cris_Visi Daniel_moura Dave_Atkins David_Merk deanbarr deepankar DeitrichTC Denise_SV dimitar_todorov dinan DineshGanta dlotterman dmante DMDWGKHNKR6X1KJVZ4D2X7KD drandrewcsmith dudster83 edesilva eho EquinixEu ESOAMERSS Esteban_Arriaza GauthamPai gfarr gsoctx guillermo Ha5dz8 harvexy hector0101 henri henrylau Igor Ilse-Maj InfraOmni ionelpascu Itone jcastro JennyChan jeremydelp jeremynguyenvantu jerome jfaulkner Jigneshkadu jirwin Jthoophany Jules kattard kazuyaawaka Kris_R laurence_man LeonardoPerius Lohit-ifiber london Luiz luoh4_adm maillard malshikh Marck_Koolen marcobes mariokind mashtava matheussoares Melissa-927 meso mhansen mhdawes Michal-Malyszko MikeP mmartinezv MOrange msarni mwardbopp Nando nbaroni ncc nchakira nickzxcv nikcy827 NinaKang nkoli noc-telecom nsambhoo NSayewich odoroodian oonyshko optixcom Osiris Osvaldobn Patricio pdehnert pg69 Piotr PiotrBychowski psb quanqinchaoye Raz rchouchene restapi-admin RFritsch rmu4789 romang2002 rwiederhold s1st3m sbhosale servidata SGillespie sgutierrezjp SilvioDuclos smuell_leitwerk Sofyanrafiq StefanBernauer stoliand Szabolcs tdileo727 tech2work_leandro tfeldpausch ThomasPlonke tirtakusuma tkerstjens tomasz_zwierzchowski Tomoyuki_Saito tprieve vannath vaperez velumani Vgregory01 Victoria VikasNayak vmvictor Wendell_Remington wjwdsky yaaliti Yassine yspancholi Angel 吉岡洋輔 大塚朋宏 박성근
delta sandbox<>prod apis
Hi, We noticed that some APIs aren't available in the sandbox but only in production of the Equinix API. Do we have a way to test this? These APIs seem to be available in the playground-zone These works on Prod but not sandbox: list userports list metros list buyer/connections For example: curl -X GET "$url/ecx/v3/l2/common/metros" -H "accept: application/json" -H "Authorization: Bearer $token" {"fault":{"faultstring":"Invalid API call as no apiproduct match found","detail":{"errorcode":"keymanagement.service.InvalidAPICallAsNoApiProductMatchFound"}}}% curl -X GET "$url/ecx/v3/port/userport" -H "accept: application/json" -H "Authorization: Bearer $token" {"fault":{"faultstring":"Invalid API call as no apiproduct match found","detail":{"errorcode":"keymanagement.service.InvalidAPICallAsNoApiProductMatchFound"}}}% curl -X GET "$url/ecx/v3/l2/buyer/connections" -H "accept: application/json" -H "Authorization: Bearer $token" {"fault":{"faultstring":"Invalid API call as no apiproduct match found","detail":{"errorcode":"keymanagement.service.InvalidAPICallAsNoApiProductMatchFound"}}}%New WorkVisit validation error
We have been using the API /catalog/workvisitv1for a while now and we now have a new validation error that is causing a failure to use the API endpoint: { "error": "Unable to create access request with Equinix. Status code = 400, error = {\"errors\":[{\"code\":\"EQX-161-6119\",\"fields\":[\"\\/attachments\"],\"message\":\"Justification form is mandatory for visiting the IBX : %s. Justification is available to download as part of work visit page in Equinix Customer Portal.\",\"messageParams\":[\"CH3\"]}],\"ticketId\":\"redacted\"}" } This appears to be a new validation error. I haven't seen anything regarding changes to the published API. Do you guys know if this is a bug or a new requirement?Filter "portName" on connection list not working
Hello, for theendpoint GET https://api.equinix.com/ecx/v3/l2/seller/connections I use it with the profileId filter and I get back many results.I go from page to page to list the connection I have on one specific port. I would like to reduce those calls using the filter portName.However the result is always empty : { "isFirstPage": true, "isLastPage": true, "totalCount": 0, "pageSize": 20, "content": [], "pageNumber": 0 } Have anyone succeeded in getting this to work ? Best regards,[sandbox] create l2connections
Hello ! I'm trying to create l2 connection on sandbox but i have some error $ curl -X POST -H "Content-Type: application/json" "https://sandboxapi.equinix.com/ecx/v3/l2/connections" -H "Authorization: Bearer xxxxxx" -d '{ "primaryName": "test_port_crea_1", "primaryPortUUID": "a9d0254e-d856-4a53-b105-7178fede119f", "primaryVlanSTag": 601, "profileUUID": "1bef8e6b-ea90-4757-bb25-c24f9d64387c", "authorizationKey": 444111000222, "speed": 200, "speedUnit": "MB", "notifications": [ "sandboxuser@example-company.com" ], "purchaseOrderNumber": "312456323", "sellerRegion": "us-east-1", "sellerMetroCode": "SV", "namedTag": "Private" }' Returns [{"errorCode":"IC-LAYER2-400","errorMessage":"Required field","moreInfo":"","errorMessageKey":"IC-LAYER2.IC-LAYER2-400","property":"additionalInfo_custBGPAssn"}] I couldn't find documentation about this field on documentation - https://developer.equinix.com/content/api/buyerv3-recommended?view=product-catalog#/Layer%202%20Connections/createConnectionUsingPOST Could you held me ? Best regards LouisIssue with Shipments API
I'm currently getting a 400 response without any sort of indication of what the problem may be. Here is an example request that I am sending with some information redacted: { "ibxLocation": { "cages": [ { "cage": "AM2:1234", "accountNumber": "1234" } ], "ibx": "AM2" }, "customerReferenceNumber": null, "serviceDetails": { "estimatedDateTime": "2019-07-27T00:00:00+00:00", "shipmentDetails": { "noOfBoxes": 3, "trackingNumber": [ "123123123" ], "inboundType": "CARRIER", "description": null, "carrierName": "UPS" } }, "contacts": [ { "contactType": "NOTIFICATION", "userName": "test@test.com", "name": "First Last" }, { "contactType": "ORDERING", "userName": "test@test.com", "name": "First Last" } ] } Please let me know if you need any information so that we can resolve this issue.Permissons Issue
I recevved the above error while trying to add a workvisit request. I'm doing some integration testing and trying to perform some negative tests so my software is able to report failures accurately. The error in itself is not really very informative so if anyone else who has seen this knows the cause I'd love to know! { "errors": [ { "code": "EQX-161-403", "message": "Insufficient permission to access the resource or invoke the request." } ], "ticketId": "190806075245093" }JSON Syntax Error
Hi everyone, I'm trying to create an Azure Express Route connection and when I try to send my POST request body: { "primaryName": "TestName-PRI", "primaryPortUUID": "abcdefghijklmonopqrustuvwxyz", "primaryVlanSTag": 511, "profileUUID": "abcdefghijklmonopqrustuvwxyz", "authorizationKey": "abcdefghijklmonopqrustuvwxyz", "speed": 100, "speedUnit": "MB", "notifications": "abcdefghijklmonopqrustuvwxyz", "sellerRegion": "ADAD", "sellerMetroCode": "xx", "secondaryName": "TestName-SEC", "secondaryPortUUID": "abcdefghijklmonopqrustuvwxyz", "secondaryVlanSTag": 511, "namedTag": "Microsoft", "primaryZSideVlanCTag": "###", "secondaryZSideVlanCTag": "###" } Obviously I will not post content with real data from my company so I filled it in with dummy data. I keep getting back the following error: [ { "errorCode": "IC-LAYER2-401", "errorMessage": "Json syntax error,Please check request body", "moreInfo": "Please refer the contracts for correct fields", "property": "" } ] Am I missing something in the request body?Getting error EQ-4006030 attempting to create a new VeloCloud VNF on Network Edge
I'm attempting to use the "Create-Velocloud SDWAN" item in the Network Edge postman collection on the developer portal. I am receiving the following error when submitting the request: [{"errorCode":"EQ-4006030","errorMessage":"We are unable to process your request.","details":"Please open a support ticket via the ? on the bottom of every page for further assistance., Invalid property 'acl' of bean class [ic.nfv.virtualdevice.model.VirtualDeviceRequestDto]: Bean property 'acl' is not readable or has an invalid getter method: Does the return type of the getter match the parameter type of the setter?","help":"https:///help/error/EQ-4006030","additionalInfo":[{"property":null,"reason":null}]}] here is my message body: { "metroCode": "SV", "deviceTypeCode": "VELOCLOUD-SDWAN", "termLength": "1", "licenseMode": "BYOL", "packageCode": "VeloCloud-2", "virtualDeviceName": "sr-008", "notifications": [ "cp941uatatt.aaa" ], "vendorConfig": { "rootPassword": "myPassw0rd!", "activationKey": "XXX", "controllerFqdn": "vco134-usvi1.velocloud.net" }, "aclDetails": [ { "uuid": "4c23126c-8874-4b36-8ad5-cf778f0b7e7a", "interfaceType": "WAN" } ], "accountNumber": "123456", "version": "3.4.2", "interfaceCount": 8, "deviceManagementType": "SELF-CONFIGURED", "core": 8 } thank you!Error with error format on serviceTokens
Hello I have error with "Error message" of the API. Endpoint: https://api.equinix.com/fabric/v4/serviceTokens/{serviceTokenId} $ curl --request GET --url "https://api.equinix.com/fabric/v4/serviceTokens/e72498f3-xxxx-xxxx-xxxx-87df25f05e5a" --header 'authorization: Bearer xxxx' > Result OK I change only one char to get an unknown service token : $ curl --request GET --url "https://api.equinix.com/fabric/v4/serviceTokens/e72498f3-xxxx-xxxx-xxxx-87df25f05e5b" --header 'authorization: Bearer xxxx' Warning: Binary output can mess up your terminal. Use "--output -" to tell Warning: curl to output it to your terminal anyway, or consider "--output Warning: " to save to a file. The answer is not a readable json. This does not occur with every error. For example the ports endpoints work without error. I try a very simple call which work : $ curl --request GET --url "https://api.equinix.com/fabric/v4/ports/24ce23cd-c42e-4746-8cdd-94cc363a0b3c" --header 'authorization: Bearer xxxxx' > Result OK I change only one letter in the port uuid: $ curl --request GET --url "https://api.equinix.com/fabric/v4/ports/24ce23cd-c42e-4746-8cdd-94cc363a0b3d" --header 'authorization: Bearer xxxxx' {"errorCode":"ERR-PRT-000-00","errorMessage":"System is unable to process the request at this time due to some internal error. Please contact support@equinix.com for more info","moreInfo":"","property":"ERROR"} On this endpoint i have a readable json as expected. On serviceTokens i tried to add many headers - Accept: application/json - Content-Type: application/json But i dont find a solution. The curl i tried are the same as the documentation : - https://developer.equinix.com/catalog/fabricv4#operation/getServiceTokenByUUID Could you check why i have this bad error message ? Best regardsGET ERROR 3005 : INVALID_SESSION_ENTITLEMENT
When I try to get a list of all the alarms, the response of my query is: GET: https://api.equinix.com/alarm/v1/smartview/alarms?accountNo=XXXX&limit=10 Output: { "code": 3005, "message": "3005 : INVALID_SESSION_ENTITLEMENT", "uid": null } Can I get some help?Could you let me know how to get Cage and Cabinet list via API?
Hello I am trying to get Cage and Cabinet list via API but it returns empty results Could you advise how to get the details? Input: curl --request POST \ --url 'https://api.equinix.com/v1/assets/search?sorts=IBX&source=CAGE&exactMatch=false&offset=0&limit=100' \ --header 'accept: application/json' \ --header 'authorization: Bearer xxxxxxx' \ --header 'content-type: application/json' \ --data '{"filter":{"ibxs":["SV2"]}}' Response: { "data": [], "page": { "limit": 90, "offset": 38491869, "total": 0, "sorts": [ "IBX" ] }, "_links": { "next": { "href": "/assets/search?exactMatch=false&offset=38491869&limit=90&source=CABINET&sorts=IBX" }, "previous": { "href": "/assets/search?exactMatch=false&offset=38491869&limit=90&source=CABINET&sorts=IBX" }, "self": { "href": "/assets/search?exactMatch=false&offset=38491869&limit=90&source=CABINET&sorts=IBX" } } }internal 500 error in using API V4
Hi, i have been trying to run this API request and always get: {"errorCode":"IC-999-99","errorMessage":"Internal Error"} Here's what I am sending: curl --location --request GET https://api.equinix.com/ecx/v3/l2/common/metros -H "Content-Type: application/json" -H "Authorization: Bearer --------k2wFtBdLcAb8kTdCOfHM" Could anyone assist or tell me what i'm doing wrong?Unable to filter using "dateRange" for OrderHistory_v1
When filtering with dateRange on the OrderHistory_v1 API i get a statusCode 400 returned. Other filters work fine for me and return expected results I am using the following payload { "filters": { "dateRange": [ "PAST_7_DAYS" ] } } The errors I receive are: code: "EQX-171-1212" path: "/filters/dateRange" message: "instance value (%s) not found in enum (possible values: %s) PAST_7_DAYS" Thank you in advanceZ side cross-connect assets
How do you query what Z-side cross-connects are installed? The /v1/assets/search URI only provides A-side cross-connects and if you attempt to post a query for /v1/assets/{assetNumber} where assetNumber refers to a Z side crossconnect, the API returns: { "errors": [ { "code": "EQX-434-4404", "message": "No Asset found for the Id:4-xxxxxxxxxxxx" } ] } Running searches / queries for A side cross-connects works fine.Fail to get locations from Work Visit API
Hi all, this is the error I'm getting when calling /v1/orders/workvisit/locations { "errors": [ { "code": "EQX-161-500", "message": "The system had encountered an unexpected problem and we are tracking it with error code." } ], "ticketId": "201023052138751" } Any ideas?sandbox api: "Error in getting user's profile"
I requested a bearer token ... no problem. As I try to get the userport with that valid bearer token, I get an error. Did I miss something ? Do I need an extra acceptance from our account manager to use my account in the sandbox ? my curl request: curl -ki --request GET \ --url https://sandboxapi.equinix.com/ecx/v3/port/userport \ --header 'accept: application/json' \ --header 'authorization: Bearer ' \ --header 'content-type: application/json' the http response: HTTP/1.1 500 Internal Server Error with this error body: {"errorCode":"IC-USR-014-01","errorMessage":"Error in getting user's profile"}Sandbox GET L2 Service Profile
Hello, I'm playing around with the Sandbox APIs and stumbled upon this problem. When trying to get a list a services I get this error message: Request GEThttps://sandboxapi.equinix.com/ecx/v3/l2/serviceprofiles/services Result { "fault": { "faultstring": "Invalid API call as no apiproduct match found", "detail": { "errorcode": "keymanagement.service.InvalidAPICallAsNoApiProductMatchFound" } } } In the long run I'd like to implement the Sandbox APIs in our production environment to serve as a kind-of dry-run feature. That means if we start a dry-run of our processes they will point to the Sandbox environment instead of the production APIs. Is it wise to do that or is the data for the Sandbox APIs changing often? I've read somewhere that the Sandbox environment is updated every couple of months. ThanksShipping API v2 list issue
Hi, I am using the API to open inbound orders and I received a call today that the Shipping team cannot scan the tracking numbers and associate them to a ticket. It looks like the API is putting the tracking number string into a list instead of a string which is causing this, ['626467467487', '626467467454', '626467467465', '626467467476']. I have my app posting this in a string format using the catalog on the developer portal. The portal does state that the tracking numbers need to be inside brackets so could that be the reason? "carrierTrackingNumbers": [ "DHL930182000" ], That is the example from the catalog, I believe the brackets are causing the issue here with the Shipping department at the site.Setting up redundant GCP Connections
I'm trying to create a primary and secondary GCP connection. I created a primary connection, however, when I try to create the secondary connection I get the following response: [ { "errorCode": "EQ-3142303", "errorMessage": "Only Primary connection allowed for this CSP", "details": "Given service profile does not allowed redundant connection", "correlationId": "null-0000-103912200151-api", "additionalInfo": [ { "property": "/redundancy/priority" } ] } ] However, if I get the service profile details via the API: https://api.equinix.com/fabric/v4/serviceProfiles/{UUID} in the "metadata" section there is an attribute "redundantProfileId" which lists the profile Id I was using to try and create a redundant connection. Am I misunderstanding this as it seems that since there is a "redundantProfileId" listed that the profile should support redundant connections?Error when setting up multiple connections
I sent a request to setup a primary and secondary connection with the body containing data structured like the following: { "data": [ { "type": "EVPL_VC" }, { "type": "EVPL_VC" } ] } When sending this I get the following error response which is obviously not correct: [ { "errorCode": "EQ-3142501", "errorMessage": "Invalid argument value passed", "details": "Invalid request type", "correlationId": "null-0000-103911409258-api", "additionalInfo": [ { "property": "/type", "reason": "Allowed values: EVPL_VC, EPL_VC, IP_VC, ACCESS_EPL_VC" } ] } ] The typefield in both cases is set to a valid value, EVPL_VC. If I just create a single connection with either of the entries of the data array the connections setup properly.
Discussions
Engage with industry experts, share insights, ask questions, and grow your network.572 Posts
