RESTconf issues in IOS-XE

[m-hosaka]

Hi All,

I cannot config the service-policy for the port-channel subinterface using RESTconf in CSR1000V.
Also, There was no service-policy information in the GET even if it was configured in the CLI.
I am trying CSR1000V, IOS-XE16.12.3.

=====================
〇CLI Config
interface Port-channel1.1000
  encapsulation dot1Q 1000
  ip address 100.100.100.1 255.255.255.252 
  service-policy output TEST_policy　★target config

〇Result of GET
{
  "Cisco-IOS-XE-native:Port-channel-subinterface": {
    "Port-channel": [
      {
        "name": "1.1000",
        "encapsulation": {
          "dot1Q": {
            "vlan-id": 1000
          }
        },
        "ip": {
          "address": {
            "primary": {
              "address": "100.100.100.1",
              "mask": "255.255.255.252"
            }
          }
        }
      }
    ]
  }
}

=====================

If service-policy is config to GigabitEthernet subinterface or port-channel, the problem does not occur.

I would like to configure the settings for ASR1001-HX as well. Will the same problem occur for ASR?
Is there any solution to this problem?

[Alex Stevenson]

Hello @m-hosaka,

Welcome! I'm not an expert with this particular technology, although I have worked with this class of router and software previously. Here are my insights:

• Here is the Programmability Configuration Guide, Cisco IOS XE Gibraltar 16.12.x , in case you don't have it.
• I found a bug with the Cisco Bug Search Tool titled Cisco 4451-X reload on applying service-policy, which mentions the CSR1000v specifically.
• I found another bug with the Cisco Bug Search Tool titled .py file check is not done while registering the policy and the error is seen (CSR), which also mentions the CSR1000v and IOS XE 16.

These might not give you the answer you're looking for but at least may give you some ideas and point you in the right direction. I hope this helps.

[m-hosaka · Accepted solution]

Hello alexstev

Thank you for your reply.

When I contacted CIsco TAC, I found that it was not supported.
We have received the answer that this will be implemented in future OS as an enhancement.

[Alex Stevenson]

Thank you for giving us the solution @m-hosaka !