{"id":1007,"date":"2020-04-03T18:31:48","date_gmt":"2020-04-03T15:31:48","guid":{"rendered":"https:\/\/isp-tech.ru\/?p=1007"},"modified":"2021-04-19T23:43:27","modified_gmt":"2021-04-19T20:43:27","slug":"cpu-protection-extreme-summit-x670","status":"publish","type":"post","link":"https:\/\/isp-tech.ru\/en\/cpu-protection-extreme-summit-x670\/","title":{"rendered":"Extreme Summit X670 CPU protection."},"content":{"rendered":"\n

Today we will talk about the CPU protection from broadcast \/ multicast traffic on the Extreme X670<\/a> platform. These considerations are also correct for the X670V.<\/p>\n\n\n\n

X670 family switches are built on the old Trident + and in comparison with classmates – Huawei (S6700-48-EI) or Cisco (N3K-3064<\/a>) practically dont have control plane protection at all.
Extreme have the built-in to XOS feature – dos-protect. However, this feature will not save you in case of broadcast or multicast storm.
Best practice to protect against BUM traffic, is to use the storm-control or rate-limit flood option in XOS. Here we will also get an unpleasant surprise. The X670 G1 platform uses XOS 16.x, in which the rate-limit flood functionality is implemented using tokens with an update interval of 15.625 microseconds. Without going into details, I\u2019ll say right away – the rate-limit flood option will drop legitimate traffic due to the imperfection of the mechanism.
You can read more on the extremenetworks.com<\/a> forum.

The described methods have been successfully used as the last border of CPU protection on L2 aggregate switches. However, best practice is protection on access layer.<\/p>\n\n\n\n

Theory:<\/h2>\n\n\n\n

So, it’s time to figure out what traffic is lifted to CPU:<\/p>\n\n\n\n

Queue 0 : Broadcast and IPv6 packets\nQueue 1 : sFlow packets\nQueue 2 : vMAC destined packets (VRRP MAC and ESRP MAC)\nQueue 3 : L3 Miss packets (ARP request not resolved) or L2 Miss packets (Software MAC learning)\nQueue 4 : Multicast traffic not hitting hardware ipmc table (224.0.0.0\/4 normal IP multicast packets neither IGMP nor PIM)\nQueue 5 : ARP reply packets or packets destined for switch itself\nQueue 6 : IGMP or PIM packets\nQueue 7 : Packets whose TOS field is \"0xc0\" and Ethertype is \"0x0800\", or STP, EAPS, EDP, OSPF packets <\/code><\/pre>\n\n\n\n
When L2 loop occurs, we will get Broadcast, IPV6 and Multicast lifted to CPU.
To dump fraffic hitted CPU and analyze the current situation, you can use this command:<\/p>\n\n\n
\ndebug packet capture on interface Broadcom count 1000\n\n<\/pre><\/div>\n\n\n
Dump will be saved in \/usr\/local\/tmp.
You can use tftp or scp to copy dump to local machine for further analysis.<\/p>\n\n\n
\ntftp put 11.1.1.1 vr "VR-Default"  \/usr\/local\/tmp\/2020-02-10_16-54-22_rx_tx.pcap  2020-02-10_16-54-22_rx_tx.pcap\n\n<\/pre><\/div>\n\n\n
Now we can analyze regular traffic hitting CPU. It is time to build the protection.<\/p>\n\n\n\n
Practice:<\/h2>\n\n\n\n
First, let’s see what will happen with CPU without any protection, if we will generate and flood broadcast and multicast traffic .
Lab scheme:<\/p>\n\n\n\nngg_shortcode_0_placeholder\n\n\n\n
Im using pktgetn linux utility to generate BcMc traffic, and nmap script for to generate IPV6 RA flood.
Multicast traffic and IPV6 RA are generated on the gen1 server, the broadcast is generated on the gen2 server.
The average generation rate is 3Mpps.<\/p>\n\n\n\n
Started traffic generators, here is CPU usage:<\/p>\n\n\n
\nsw2# sh cpu-monitoring | exclude 0.0\n\n      CPU Utilization Statistics - Monitored every 5 seconds\n-----------------------------------------------------------------------\n\nProcess      5   10   30   1    5    30   1    Max           Total\n            secs secs secs min  mins mins hour            User\/System\n            util util util util util util util util       CPU Usage\n            (%)  (%)  (%)  (%)   (%)  (%)  (%)  (%)         (secs)\n-----------------------------------------------------------------------\n\nSystem       52.2 50.3 50.4 47.3 48.9 26.0 13.0 69.7     0.32     964.28 \nmcmgr        39.9 40.4 41.6 43.0 38.6 10.5  5.2 47.1    46.47     356.98 \n\nsw2#top\nLoad average: 6.57 5.38 4.74 4\/208 2905\n  PID  PPID USER     STAT   RSS %MEM CPU %CPU COMMAND\n  1327     2 root     RW       0  0.0   1 41.2 [bcmRX]\n 1543     1 root     R     3852  0.3   0 40.4 .\/mcmgr \n\nsw2# debug hal show device port-info system unit 0 | include cpu\nMC_PERQ_PKT(0).cpu0     :      1,131,571      +62,271           5,776\/s\nMC_PERQ_PKT(4).cpu0     :      187,781        +42,768           5,353\/s\nMC_PERQ_PKT(7).cpu0     :      503            +17\nMCQ_DROP_PKT(0).cpu0    :      174,095,428    +29,103,098       3,298,296\/s\nMCQ_DROP_PKT(4).cpu0    :      78,082,718     +17,834,191       1,021,107\/s\n\nsw2# debug hal show congestion \nCongestion information for Summit type X670-48x since last query\n  CPU congestion present: 12414120\n<\/pre><\/div>\n\n\n
Now, with transit broadcast \/ multicast traffic with about 6Mpps rate, we have 100% CPU load and 10Kpps in the queues on the CPU, everything else is dropped. Real traffic on CPU  queues is many times higher.<\/p>\n\n\n\n
Now let’s move on to the filters and see what we can do.<\/p>\n\n\n\n
To protect Queue 0: Broadcast and IPv6 packets, i will create policy limit-bc-ipv6.<\/p>\n\n\n\n
This config can be used if you are NOT using L3 IPv6 features.<\/strong><\/p>\n\n\n
\nconfigure meter limit-broadcast committed-rate 1000 Pps out-actions drop \n\nsw#show policy limit-bc-ipv6\n\nentry match-v6 { \nif match all { \n    ethernet-type 0x86DD ;\n}\nthen {\n    deny-cpu  ;\n}\n}\nentry match-bc { \nif match all { \n    ethernet-destination-address ff:ff:ff:ff:ff:ff ;\n}\nthen {\n    meter limit-broadcast ;\n}\n}\n<\/pre><\/div>\n\n\n
This policy can be applied to all ports, or only to those where a storm is possible.<\/p>\n\n\n
\nconfigure access-list limit-bc-ipv6 ports 1-48 ingress\n\n<\/pre><\/div>\n\n\n
For a complete simulation, i will create a loop on ports 11 and 12.<\/p>\n\n\n
\nsw2# sh ports 11-12,46-47 utilization \nLink Utilization Averages                            Fri Apr  3 14:55:26 2020\nPort    Link     Rx            Peak Rx        Tx             Peak Tx\n        State    pkts\/sec      pkts\/sec       pkts\/sec       pkts\/sec\n===========================================================================\n11        A       7484877        8725834          7483368         8724075\n12        A       7471259        8710066          7472785         8711816\n46        A       2962834        3716425          7435635         8690736\n47        A       2807846        3931673          7304028         8541282\n\n\n<\/pre><\/div>\n\n\n
3,000 Broadcast packets are lifted to the CPU; the rest is multicast.<\/p>\n\n\n
\nsw2# debug hal show device port-info system unit 0 | include cpu\nMC_PERQ_PKT(0).cpu0     :      2,456,584        +290,921           3,043\/s\nMC_PERQ_PKT(3).cpu0     :      3,104,008        +1,498,923         4,102\/s\nMC_PERQ_PKT(4).cpu0     :      3,125,047        +394,781           4,102\/s\nMC_PERQ_PKT(6).cpu0     :      1,222,571        +135,286           4,090\/s\n<\/pre><\/div>\n\n\n
CPU utilization is still 100%:<\/p>\n\n\n
\nsw2# sh cpu-monitoring \n\n      CPU Utilization Statistics - Monitored every 5 seconds\n-----------------------------------------------------------------------\n\nProcess      5   10   30   1    5    30   1    Max           Total\n            secs secs secs min  mins mins hour            User\/System\n            util util util util util util util util       CPU Usage\n            (%)  (%)  (%)  (%)   (%)  (%)  (%)  (%)         (secs)\n-----------------------------------------------------------------------\n\nSystem       50.3 48.9 46.9 51.4 58.1 31.7 15.8 68.8     0.32    1180.54 \nmcmgr        43.9 43.1 44.8 31.0  6.3  6.3  3.1 48.5    33.33     198.40 \n<\/pre><\/div>\n\n\n
Let’s try to protect CPU from multicast.
To do so, you need to turn off igmp snooping on all vlanes that are facing port,  where the storm occurs.
If igmp snooping is enabled on the vlan, the traffic will be forwarded to the CPU.<\/p>\n\n\n
\nsw2# configure igmp snooping filters per-vlan\nsw2#disable igmp snooping vlan test\nsw2#disable igmp snooping vlan test2\n<\/pre><\/div>\n\n\n
After disabling igmp snooping on looped vlan, only 3000pps of broadcast hits CPU:<\/p>\n\n\n
\nsw2# debug hal show device port-info system unit 0 | include cpu\nMC_PERQ_PKT(0).cpu0     :     4,908,231       +6,352           2,994\/s\nMC_PERQ_PKT(7).cpu0     :     11,214            +3               1\/s\n<\/pre><\/div>\n\n\n
CPU utilization ~ 15%.<\/p>\n\n\n
\nsw2# sh cpu-monitoring | exclude 0.0\n\n      CPU Utilization Statistics - Monitored every 5 seconds\n-----------------------------------------------------------------------\n\nProcess      5   10   30   1    5    30   1    Max           Total\n            secs secs secs min  mins mins hour            User\/System\n            util util util util util util util util       CPU Usage\n            (%)  (%)  (%)  (%)   (%)  (%)  (%)  (%)         (secs)\n-----------------------------------------------------------------------\n\nSystem        9.3 10.5 16.5 13.7  2.7  0.4  0.2 34.1     0.14      18.96 \nhal           3.5  3.7  3.2 10.2  2.0  0.3  0.1 51.5     1.42      10.67 \n<\/pre><\/div>\n\n
\nsw2#top\nMem: 577816K used, 443708K free, 0K shrd, 127032K buff, 157064K cached\nCPU:  0.8% usr 16.5% sys  0.0% nic 69.9% idle  0.0% io  2.6% irq  9.9% sirq\nLoad average: 5.12 2.77 1.10 3\/208 2015\n  PID  PPID USER     STAT   RSS %MEM CPU %CPU COMMAND\n 1329     2 root     SW       0  0.0   1 17.7 [bcmRX]\n\n<\/pre><\/div>\n\n\n
Summing up, i can say that these switches will be good as L2 aggregators or P routers in MPLS networks. If you are planing to use the X670 as combined L3\/L2 switch, protecting CPU will a nightmare.<\/p>\n\n\n\n
UPD(02\/2021)<\/strong>: <\/h2>\n\n\n\n
In ExtremeXOS 16.2.5-Patch1-22 (Apr 2020) storm-control fix was announced:
xos0063205 Even though the traffic rate is below the configured flood rate limit, traffic is dropped.<\/p>\n\n\n\n
But, as usual, it was not completely fixed. 
I will configure action = disable-port log<\/strong> for broadcast and multicast with threshold of 500pps and only log<\/strong> for unknown-destmac with same threshold.<\/p>\n\n\n
\nconfigure port 1 rate-limit flood broadcast 500 out-actions log disable-port\nconfigure port 1 rate-limit flood multicast 500 out-actions log disable-port\nconfigure port 1 rate-limit flood unknown-destmac 500 out-actions log\n<\/pre><\/div>\n\n\n
Fired up traffic generator with random DST MAC pattern and 1000pps rate.

The problem is that action = disable-port is triggered when any type of traffic reaches the threshold. In our case, when the unknown-destmac threshold reaches 500pps, the port should not be turned off. However, the port turns off:<\/p>\n\n\n
\nsw2#sh ports 1 rate-limit flood out-of-profile refresh \n                                  Port Monitor         Fri Feb 12 11:48:33 2021\nPort      Flood Type        Status             Counter\n#--------  ----------------  --------------  ----------\n1         Unknown Dest MAC  Out of profile      109336\n1         Multicast         Out of profile      109336\n1         Broadcast         Out of profile      109336\n\nsw2# sh log\n02\/12\/2021 11:52:14.71 Info:vlan.msgs.portLinkStateDown Port 1 link down\n02\/12\/2021 11:52:14.70 Info:vlan.msgs.FldRateOutActDsblPort Port 1 disabled by Flood Control Rate Limit because the traffic exceeded the configured rate.\n<\/pre><\/div>\n\n\n
Tested on 16.2.5.4 16.2.5.4-patch1-29.
Hopefully this will be fixed in the next releases.<\/p>\n","protected":false},"excerpt":{"rendered":"
Today we will talk about the CPU protection from broadcast \/ multicast traffic on the Extreme X670 platform. These considerations are also correct for the X670V. X670 family switches are built on the old Trident + and in comparison with classmates – Huawei (S6700-48-EI) or Cisco (N3K-3064) practically dont have control plane protection at all.Extreme\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"ngg_post_thumbnail":0,"footnotes":""},"categories":[9],"tags":[27,18],"class_list":["post-1007","post","type-post","status-publish","format-standard","hentry","category-security-extreme-summit","tag-control-plane","tag-extreme-summit"],"yoast_head":"\nExtreme Summit X670 CPU protection - isp-tech.ru<\/title>\n<meta name=\"description\" content=\"Extreme Summit X670 CPU protection. Extreme summit CPU protection against Broadcast\/Multicast traffic.Control plane protection Extreme summit X670\/X670V.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/isp-tech.ru\/en\/cpu-protection-extreme-summit-x670\/\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"admin\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/isp-tech.ru\/cpu-protection-extreme-summit-x670\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/isp-tech.ru\/cpu-protection-extreme-summit-x670\/\"},\"author\":{\"name\":\"admin\",\"@id\":\"https:\/\/isp-tech.ru\/#\/schema\/person\/bfc8f447cee1b54cc04a263ed0673363\"},\"headline\":\"Extreme Summit X670 CPU protection.\",\"datePublished\":\"2020-04-03T15:31:48+00:00\",\"dateModified\":\"2021-04-19T20:43:27+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/isp-tech.ru\/cpu-protection-extreme-summit-x670\/\"},\"wordCount\":1259,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/isp-tech.ru\/#\/schema\/person\/bfc8f447cee1b54cc04a263ed0673363\"},\"keywords\":[\"Control Plane\",\"Extreme Summit\"],\"articleSection\":[\"Security\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/isp-tech.ru\/cpu-protection-extreme-summit-x670\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/isp-tech.ru\/cpu-protection-extreme-summit-x670\/\",\"url\":\"https:\/\/isp-tech.ru\/cpu-protection-extreme-summit-x670\/\",\"name\":\"Extreme Summit X670 CPU protection - isp-tech.ru\",\"isPartOf\":{\"@id\":\"https:\/\/isp-tech.ru\/#website\"},\"datePublished\":\"2020-04-03T15:31:48+00:00\",\"dateModified\":\"2021-04-19T20:43:27+00:00\",\"description\":\"Extreme Summit X670 CPU protection. Extreme summit CPU protection against Broadcast\/Multicast traffic.Control plane protection Extreme summit X670\/X670V.\",\"breadcrumb\":{\"@id\":\"https:\/\/isp-tech.ru\/cpu-protection-extreme-summit-x670\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/isp-tech.ru\/cpu-protection-extreme-summit-x670\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/isp-tech.ru\/cpu-protection-extreme-summit-x670\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"\u0413\u043b\u0430\u0432\u043d\u0430\u044f \u0441\u0442\u0440\u0430\u043d\u0438\u0446\u0430\",\"item\":\"https:\/\/isp-tech.ru\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Extreme Summit X670 CPU protection.\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/isp-tech.ru\/#website\",\"url\":\"https:\/\/isp-tech.ru\/\",\"name\":\"isp-tech.ru\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/isp-tech.ru\/#\/schema\/person\/bfc8f447cee1b54cc04a263ed0673363\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/isp-tech.ru\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\/\/isp-tech.ru\/#\/schema\/person\/bfc8f447cee1b54cc04a263ed0673363\",\"name\":\"admin\",\"logo\":{\"@id\":\"https:\/\/isp-tech.ru\/#\/schema\/person\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Extreme Summit X670 CPU protection - isp-tech.ru","description":"Extreme Summit X670 CPU protection. Extreme summit CPU protection against Broadcast\/Multicast traffic.Control plane protection Extreme summit X670\/X670V.","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:\/\/isp-tech.ru\/en\/cpu-protection-extreme-summit-x670\/","twitter_misc":{"Written by":"admin","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/isp-tech.ru\/cpu-protection-extreme-summit-x670\/#article","isPartOf":{"@id":"https:\/\/isp-tech.ru\/cpu-protection-extreme-summit-x670\/"},"author":{"name":"admin","@id":"https:\/\/isp-tech.ru\/#\/schema\/person\/bfc8f447cee1b54cc04a263ed0673363"},"headline":"Extreme Summit X670 CPU protection.","datePublished":"2020-04-03T15:31:48+00:00","dateModified":"2021-04-19T20:43:27+00:00","mainEntityOfPage":{"@id":"https:\/\/isp-tech.ru\/cpu-protection-extreme-summit-x670\/"},"wordCount":1259,"commentCount":0,"publisher":{"@id":"https:\/\/isp-tech.ru\/#\/schema\/person\/bfc8f447cee1b54cc04a263ed0673363"},"keywords":["Control Plane","Extreme Summit"],"articleSection":["Security"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/isp-tech.ru\/cpu-protection-extreme-summit-x670\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/isp-tech.ru\/cpu-protection-extreme-summit-x670\/","url":"https:\/\/isp-tech.ru\/cpu-protection-extreme-summit-x670\/","name":"Extreme Summit X670 CPU protection - isp-tech.ru","isPartOf":{"@id":"https:\/\/isp-tech.ru\/#website"},"datePublished":"2020-04-03T15:31:48+00:00","dateModified":"2021-04-19T20:43:27+00:00","description":"Extreme Summit X670 CPU protection. Extreme summit CPU protection against Broadcast\/Multicast traffic.Control plane protection Extreme summit X670\/X670V.","breadcrumb":{"@id":"https:\/\/isp-tech.ru\/cpu-protection-extreme-summit-x670\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/isp-tech.ru\/cpu-protection-extreme-summit-x670\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/isp-tech.ru\/cpu-protection-extreme-summit-x670\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"\u0413\u043b\u0430\u0432\u043d\u0430\u044f \u0441\u0442\u0440\u0430\u043d\u0438\u0446\u0430","item":"https:\/\/isp-tech.ru\/"},{"@type":"ListItem","position":2,"name":"Extreme Summit X670 CPU protection."}]},{"@type":"WebSite","@id":"https:\/\/isp-tech.ru\/#website","url":"https:\/\/isp-tech.ru\/","name":"isp-tech.ru","description":"","publisher":{"@id":"https:\/\/isp-tech.ru\/#\/schema\/person\/bfc8f447cee1b54cc04a263ed0673363"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/isp-tech.ru\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":["Person","Organization"],"@id":"https:\/\/isp-tech.ru\/#\/schema\/person\/bfc8f447cee1b54cc04a263ed0673363","name":"admin","logo":{"@id":"https:\/\/isp-tech.ru\/#\/schema\/person\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/isp-tech.ru\/en\/wp-json\/wp\/v2\/posts\/1007","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/isp-tech.ru\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/isp-tech.ru\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/isp-tech.ru\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/isp-tech.ru\/en\/wp-json\/wp\/v2\/comments?post=1007"}],"version-history":[{"count":113,"href":"https:\/\/isp-tech.ru\/en\/wp-json\/wp\/v2\/posts\/1007\/revisions"}],"predecessor-version":[{"id":2813,"href":"https:\/\/isp-tech.ru\/en\/wp-json\/wp\/v2\/posts\/1007\/revisions\/2813"}],"wp:attachment":[{"href":"https:\/\/isp-tech.ru\/en\/wp-json\/wp\/v2\/media?parent=1007"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/isp-tech.ru\/en\/wp-json\/wp\/v2\/categories?post=1007"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/isp-tech.ru\/en\/wp-json\/wp\/v2\/tags?post=1007"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}