Transport Slicing - Need possible values for hub-rt & spoke-rt: When we tried to provide the value for hub-rt ; spoke-rt in conneciton groups it resulted in below error,{  "ietf-restconf:errors": {    "error": [      {        "error-type": "application",        "error-tag": "malformed-message",        "error-path": "/ietf-network-slice-service:network-slice-services",        "error-message": "invalid value for: hub-rt in /ietf-nss:network-slice-services/ietf-nss:slice-service[ietf-nss:service-id='Test-Dedic-530']/ietf-nss:connection-groups/ietf-nss:connection-group[ietf-nss:connection-group-id='Default']/ietf-nss-cisco:vpn-target/ietf-nss-cisco:hub-rt: "import" is an invalid value."      }    ]  }}Kindly let us know the possible values.Thanks,Naveen
Hi Naveen,hub-rt and spoke-rt for NSS has the following type definition:<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"><pre class="code-java">typedef route-distinguisher { type string {  pattern     +     +     +     +     +     +     +     +     +   +     +     +     +     +     +   +     +     +     +     +     +     +     +   ;  tailf:info "0:2-octet-asn:4-octet-number         1:4-octet-ipv4addr:2-octet-number         2:4-octet-asn:2-octet-number"; }}</pre></div></div>So the input for these hub-rt and spoke-rt should be in the following format:<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"><pre class="code-java">0:2-octet-asn:4-octet-number 1:4-octet-ipv4addr:2-octet-number 2:4-octet-asn:2-octet-number</pre></div></div>Let me know if you have any other questions.Thanks,Isaac KimHi Issac,Can you provide one sample value.Thanks,NaveenHi Naveen,One example value can be "0:65001:100"Thanks,Isaac Kim