{"id":125,"date":"2017-09-08T15:28:09","date_gmt":"2017-09-08T13:28:09","guid":{"rendered":"http:\/\/netgab.net\/web\/?p=125"},"modified":"2017-09-08T15:32:07","modified_gmt":"2017-09-08T13:32:07","slug":"cisco-wlc-pitfalls-not-using-lag","status":"publish","type":"post","link":"https:\/\/netgab.net\/web\/2017\/09\/08\/cisco-wlc-pitfalls-not-using-lag\/","title":{"rendered":"Cisco WLC: Pitfalls when not using LAG"},"content":{"rendered":"<p>Since the very early days of AireOS WLCs, Cisco strongly recommends the usage of <strong>LAG<\/strong> (aka &#8220;static port channels&#8221; aka &#8220;static EtherChannels&#8221; aka &#8220;mode on channels&#8221;)\u00a0 to uplink the WLCs to the rest of the network.<\/p>\n<p>The logical management\/RMI interface,\u00a0 optionally AP manager interface and dynamic interfaces are assigned to the <strong>L<\/strong>ink <strong>A<\/strong>ggregation <strong>G<\/strong>roup. All physical network ports are assinged to the <strong>LAG<\/strong>. It&#8217;s only possible to create ONE LAG. To get high availability in terms of uplink switch failures, it is recommeded to distribute the LAG links to different switch chassis. Thus, a switch that supports multi-chassis channels (e.g VSS, stacks) are recommended by Cisco.<\/p>\n<p>However sometimes it is not possible to use LAG, because the WLC must be connected to different physical switches. A good example is a WLC, that must have an INSIDE port for CAPWAP, management access and maybe internal WLANs and a separated EXTERNAL port for all the &#8220;evil&#8221; dynamic Interfaces (e.g. Internet WLANs).<\/p>\n<p>In this case, link redundancy is not possible with LAGs, because all ports are assigned to ONE LAG and therefore, the WLC cannot be connected to different physical switches \/ switch stacks \/ VSSs. However, link redundancy can be achived by using a primary \/ backup port assigned.<\/p>\n<p>For example on a 5508 WLC, port 1 (active) and port 2 (backup) are used for a redundant INSIDE connection and port 3 (active) and port 4 (backup) are used for the EXTERNAL connection.<\/p>\n<p>How do you solve the problem with a 5520 WLC, which has only two physical ports? The simplest approach is, not using the active\/backup port feature and achive redundancy using SSO (two WLC boxes) as illustrated in the following figure:<\/p>\n<div id=\"attachment_132\" style=\"width: 969px\" class=\"wp-caption alignleft\"><img loading=\"lazy\" decoding=\"async\" aria-describedby=\"caption-attachment-132\" class=\"wp-image-132 size-full\" src=\"http:\/\/netgab.net\/web\/wp-content\/uploads\/2017\/09\/5520_SSO_noLAG_1.png\" alt=\"5520 SSO without LAG\" width=\"959\" height=\"599\" srcset=\"https:\/\/netgab.net\/web\/wp-content\/uploads\/2017\/09\/5520_SSO_noLAG_1.png 959w, https:\/\/netgab.net\/web\/wp-content\/uploads\/2017\/09\/5520_SSO_noLAG_1-300x187.png 300w, https:\/\/netgab.net\/web\/wp-content\/uploads\/2017\/09\/5520_SSO_noLAG_1-768x480.png 768w\" sizes=\"auto, (max-width: 959px) 100vw, 959px\" \/><p id=\"caption-attachment-132\" class=\"wp-caption-text\">5520 SSO without LAG<\/p><\/div>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>The idea behind it is simple: The physical ports of the WLCs are distributed over different switches. If any switch or connection towards the active WLC fails, the SSO cluster converges and wlc2 will become active.<\/p>\n<p>This is only true for connections, that are considered in the SSO algorithm. The only interfaces \/ ports, that are relevant for SSO operation are:<\/p>\n<ul>\n<li>RP port (dedicated interface)<\/li>\n<li>RMI interface (same network port as management interface)<\/li>\n<\/ul>\n<p>A dynamic interface failure is not relevant for SSO operation.<\/p>\n<p>Long story short: If port 2 (dynamic interface on active WLC) fails, which could happen for a cable failure or switch failure on the right side in the example above, the SSO cluster won&#8217;t converge and wlc2 won&#8217;t take over.<\/p>\n<p>What happens is a blackhole scenario. All the APs are still associated to wlc1 and the CAPWAP control and data sessions terminate at wlc1. However WLANs, which are mapped to dynamic interfaces to port 2 won&#8217;t work properly any more. The wireless users won&#8217;t be bridged to the wired network.<\/p>\n<p>Other networking platforms (e.g. Cisco ASA) solve this problem by monitoring additional interfaces within the redundancy configuration (configurable). A failure of these monitored interfaces result in a HA switchover. Another example are HSRP and VRRP priority penalties in case certain interfaces goes down.<\/p>\n<p>So take care when using the combination of:<\/p>\n<ul>\n<li>No LAG<\/li>\n<li>Connection the different switching domains<\/li>\n<li>High availability (e.g. SSO and plain old N+1)<\/li>\n<li>No backup interfaces<\/li>\n<\/ul>\n<p>I know it&#8217;s kinda exotic and special &#8230;. &#8230;.. but we love corner cases, because they always break our necks \ud83d\ude42<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Since the very early days of AireOS WLCs, Cisco strongly recommends the usage of LAG (aka &#8220;static port channels&#8221; aka &#8220;static EtherChannels&#8221; aka &#8220;mode on channels&#8221;)\u00a0 to uplink the WLCs to the rest of the network. The logical management\/RMI interface,\u00a0 optionally AP manager interface and dynamic interfaces are assigned to [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":136,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[1],"tags":[17,14,16,9,15],"class_list":["post-125","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","tag-17","tag-lag","tag-sso","tag-wlan","tag-wlc"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.3 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Cisco WLC: Pitfalls when not using LAG - NetGab - The daily networking madness<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/netgab.net\/web\/2017\/09\/08\/cisco-wlc-pitfalls-not-using-lag\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Cisco WLC: Pitfalls when not using LAG - NetGab - The daily networking madness\" \/>\n<meta property=\"og:description\" content=\"Since the very early days of AireOS WLCs, Cisco strongly recommends the usage of LAG (aka &#8220;static port channels&#8221; aka &#8220;static EtherChannels&#8221; aka &#8220;mode on channels&#8221;)\u00a0 to uplink the WLCs to the rest of the network. The logical management\/RMI interface,\u00a0 optionally AP manager interface and dynamic interfaces are assigned to [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/netgab.net\/web\/2017\/09\/08\/cisco-wlc-pitfalls-not-using-lag\/\" \/>\n<meta property=\"og:site_name\" content=\"NetGab - The daily networking madness\" \/>\n<meta property=\"article:published_time\" content=\"2017-09-08T13:28:09+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2017-09-08T13:32:07+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/netgab.net\/web\/wp-content\/uploads\/2017\/09\/steel-cables-187861_1280.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1280\" \/>\n\t<meta property=\"og:image:height\" content=\"853\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"joe\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"joe\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"3 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/netgab.net\\\/web\\\/2017\\\/09\\\/08\\\/cisco-wlc-pitfalls-not-using-lag\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/netgab.net\\\/web\\\/2017\\\/09\\\/08\\\/cisco-wlc-pitfalls-not-using-lag\\\/\"},\"author\":{\"name\":\"joe\",\"@id\":\"https:\\\/\\\/netgab.net\\\/web\\\/#\\\/schema\\\/person\\\/b3c8a779d0a772a9b047559d7bba4ccd\"},\"headline\":\"Cisco WLC: Pitfalls when not using LAG\",\"datePublished\":\"2017-09-08T13:28:09+00:00\",\"dateModified\":\"2017-09-08T13:32:07+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/netgab.net\\\/web\\\/2017\\\/09\\\/08\\\/cisco-wlc-pitfalls-not-using-lag\\\/\"},\"wordCount\":563,\"commentCount\":0,\"image\":{\"@id\":\"https:\\\/\\\/netgab.net\\\/web\\\/2017\\\/09\\\/08\\\/cisco-wlc-pitfalls-not-using-lag\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/netgab.net\\\/web\\\/wp-content\\\/uploads\\\/2017\\\/09\\\/steel-cables-187861_1280.jpg\",\"keywords\":[\"5520\",\"LAG\",\"SSO\",\"wlan\",\"WLC\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/netgab.net\\\/web\\\/2017\\\/09\\\/08\\\/cisco-wlc-pitfalls-not-using-lag\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/netgab.net\\\/web\\\/2017\\\/09\\\/08\\\/cisco-wlc-pitfalls-not-using-lag\\\/\",\"url\":\"https:\\\/\\\/netgab.net\\\/web\\\/2017\\\/09\\\/08\\\/cisco-wlc-pitfalls-not-using-lag\\\/\",\"name\":\"Cisco WLC: Pitfalls when not using LAG - NetGab - The daily networking madness\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/netgab.net\\\/web\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/netgab.net\\\/web\\\/2017\\\/09\\\/08\\\/cisco-wlc-pitfalls-not-using-lag\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/netgab.net\\\/web\\\/2017\\\/09\\\/08\\\/cisco-wlc-pitfalls-not-using-lag\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/netgab.net\\\/web\\\/wp-content\\\/uploads\\\/2017\\\/09\\\/steel-cables-187861_1280.jpg\",\"datePublished\":\"2017-09-08T13:28:09+00:00\",\"dateModified\":\"2017-09-08T13:32:07+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/netgab.net\\\/web\\\/#\\\/schema\\\/person\\\/b3c8a779d0a772a9b047559d7bba4ccd\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/netgab.net\\\/web\\\/2017\\\/09\\\/08\\\/cisco-wlc-pitfalls-not-using-lag\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/netgab.net\\\/web\\\/2017\\\/09\\\/08\\\/cisco-wlc-pitfalls-not-using-lag\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/netgab.net\\\/web\\\/2017\\\/09\\\/08\\\/cisco-wlc-pitfalls-not-using-lag\\\/#primaryimage\",\"url\":\"https:\\\/\\\/netgab.net\\\/web\\\/wp-content\\\/uploads\\\/2017\\\/09\\\/steel-cables-187861_1280.jpg\",\"contentUrl\":\"https:\\\/\\\/netgab.net\\\/web\\\/wp-content\\\/uploads\\\/2017\\\/09\\\/steel-cables-187861_1280.jpg\",\"width\":1280,\"height\":853,\"caption\":\"Feature image\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/netgab.net\\\/web\\\/2017\\\/09\\\/08\\\/cisco-wlc-pitfalls-not-using-lag\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/netgab.net\\\/web\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Cisco WLC: Pitfalls when not using LAG\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/netgab.net\\\/web\\\/#website\",\"url\":\"https:\\\/\\\/netgab.net\\\/web\\\/\",\"name\":\"NetGab - The daily networking madness\",\"description\":\"Networking at its best ... and worst\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/netgab.net\\\/web\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/netgab.net\\\/web\\\/#\\\/schema\\\/person\\\/b3c8a779d0a772a9b047559d7bba4ccd\",\"name\":\"joe\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/32b66c7321ea985e8c54f9975e87605df70ac5e4167a1e4153d91d72c67cf150?s=96&d=retro&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/32b66c7321ea985e8c54f9975e87605df70ac5e4167a1e4153d91d72c67cf150?s=96&d=retro&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/32b66c7321ea985e8c54f9975e87605df70ac5e4167a1e4153d91d72c67cf150?s=96&d=retro&r=g\",\"caption\":\"joe\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Cisco WLC: Pitfalls when not using LAG - NetGab - The daily networking madness","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/netgab.net\/web\/2017\/09\/08\/cisco-wlc-pitfalls-not-using-lag\/","og_locale":"en_US","og_type":"article","og_title":"Cisco WLC: Pitfalls when not using LAG - NetGab - The daily networking madness","og_description":"Since the very early days of AireOS WLCs, Cisco strongly recommends the usage of LAG (aka &#8220;static port channels&#8221; aka &#8220;static EtherChannels&#8221; aka &#8220;mode on channels&#8221;)\u00a0 to uplink the WLCs to the rest of the network. The logical management\/RMI interface,\u00a0 optionally AP manager interface and dynamic interfaces are assigned to [&hellip;]","og_url":"https:\/\/netgab.net\/web\/2017\/09\/08\/cisco-wlc-pitfalls-not-using-lag\/","og_site_name":"NetGab - The daily networking madness","article_published_time":"2017-09-08T13:28:09+00:00","article_modified_time":"2017-09-08T13:32:07+00:00","og_image":[{"width":1280,"height":853,"url":"https:\/\/netgab.net\/web\/wp-content\/uploads\/2017\/09\/steel-cables-187861_1280.jpg","type":"image\/jpeg"}],"author":"joe","twitter_card":"summary_large_image","twitter_misc":{"Written by":"joe","Est. reading time":"3 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/netgab.net\/web\/2017\/09\/08\/cisco-wlc-pitfalls-not-using-lag\/#article","isPartOf":{"@id":"https:\/\/netgab.net\/web\/2017\/09\/08\/cisco-wlc-pitfalls-not-using-lag\/"},"author":{"name":"joe","@id":"https:\/\/netgab.net\/web\/#\/schema\/person\/b3c8a779d0a772a9b047559d7bba4ccd"},"headline":"Cisco WLC: Pitfalls when not using LAG","datePublished":"2017-09-08T13:28:09+00:00","dateModified":"2017-09-08T13:32:07+00:00","mainEntityOfPage":{"@id":"https:\/\/netgab.net\/web\/2017\/09\/08\/cisco-wlc-pitfalls-not-using-lag\/"},"wordCount":563,"commentCount":0,"image":{"@id":"https:\/\/netgab.net\/web\/2017\/09\/08\/cisco-wlc-pitfalls-not-using-lag\/#primaryimage"},"thumbnailUrl":"https:\/\/netgab.net\/web\/wp-content\/uploads\/2017\/09\/steel-cables-187861_1280.jpg","keywords":["5520","LAG","SSO","wlan","WLC"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/netgab.net\/web\/2017\/09\/08\/cisco-wlc-pitfalls-not-using-lag\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/netgab.net\/web\/2017\/09\/08\/cisco-wlc-pitfalls-not-using-lag\/","url":"https:\/\/netgab.net\/web\/2017\/09\/08\/cisco-wlc-pitfalls-not-using-lag\/","name":"Cisco WLC: Pitfalls when not using LAG - NetGab - The daily networking madness","isPartOf":{"@id":"https:\/\/netgab.net\/web\/#website"},"primaryImageOfPage":{"@id":"https:\/\/netgab.net\/web\/2017\/09\/08\/cisco-wlc-pitfalls-not-using-lag\/#primaryimage"},"image":{"@id":"https:\/\/netgab.net\/web\/2017\/09\/08\/cisco-wlc-pitfalls-not-using-lag\/#primaryimage"},"thumbnailUrl":"https:\/\/netgab.net\/web\/wp-content\/uploads\/2017\/09\/steel-cables-187861_1280.jpg","datePublished":"2017-09-08T13:28:09+00:00","dateModified":"2017-09-08T13:32:07+00:00","author":{"@id":"https:\/\/netgab.net\/web\/#\/schema\/person\/b3c8a779d0a772a9b047559d7bba4ccd"},"breadcrumb":{"@id":"https:\/\/netgab.net\/web\/2017\/09\/08\/cisco-wlc-pitfalls-not-using-lag\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/netgab.net\/web\/2017\/09\/08\/cisco-wlc-pitfalls-not-using-lag\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/netgab.net\/web\/2017\/09\/08\/cisco-wlc-pitfalls-not-using-lag\/#primaryimage","url":"https:\/\/netgab.net\/web\/wp-content\/uploads\/2017\/09\/steel-cables-187861_1280.jpg","contentUrl":"https:\/\/netgab.net\/web\/wp-content\/uploads\/2017\/09\/steel-cables-187861_1280.jpg","width":1280,"height":853,"caption":"Feature image"},{"@type":"BreadcrumbList","@id":"https:\/\/netgab.net\/web\/2017\/09\/08\/cisco-wlc-pitfalls-not-using-lag\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/netgab.net\/web\/"},{"@type":"ListItem","position":2,"name":"Cisco WLC: Pitfalls when not using LAG"}]},{"@type":"WebSite","@id":"https:\/\/netgab.net\/web\/#website","url":"https:\/\/netgab.net\/web\/","name":"NetGab - The daily networking madness","description":"Networking at its best ... and worst","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/netgab.net\/web\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/netgab.net\/web\/#\/schema\/person\/b3c8a779d0a772a9b047559d7bba4ccd","name":"joe","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/32b66c7321ea985e8c54f9975e87605df70ac5e4167a1e4153d91d72c67cf150?s=96&d=retro&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/32b66c7321ea985e8c54f9975e87605df70ac5e4167a1e4153d91d72c67cf150?s=96&d=retro&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/32b66c7321ea985e8c54f9975e87605df70ac5e4167a1e4153d91d72c67cf150?s=96&d=retro&r=g","caption":"joe"}}]}},"jetpack_featured_media_url":"https:\/\/netgab.net\/web\/wp-content\/uploads\/2017\/09\/steel-cables-187861_1280.jpg","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p8dgKr-21","_links":{"self":[{"href":"https:\/\/netgab.net\/web\/wp-json\/wp\/v2\/posts\/125","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/netgab.net\/web\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/netgab.net\/web\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/netgab.net\/web\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/netgab.net\/web\/wp-json\/wp\/v2\/comments?post=125"}],"version-history":[{"count":4,"href":"https:\/\/netgab.net\/web\/wp-json\/wp\/v2\/posts\/125\/revisions"}],"predecessor-version":[{"id":134,"href":"https:\/\/netgab.net\/web\/wp-json\/wp\/v2\/posts\/125\/revisions\/134"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/netgab.net\/web\/wp-json\/wp\/v2\/media\/136"}],"wp:attachment":[{"href":"https:\/\/netgab.net\/web\/wp-json\/wp\/v2\/media?parent=125"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/netgab.net\/web\/wp-json\/wp\/v2\/categories?post=125"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/netgab.net\/web\/wp-json\/wp\/v2\/tags?post=125"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}