cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
475
Views
5
Helpful
6
Replies
Tomoya Watanabe
Beginner

CDB schema change when upgrading 4.5.3 to 5.5.1

We are planning to upgrade NSO 4.5.3 to 5.5.1 and evaluating migration procedure of service model and NED

 

In our evaluation, we noticed some elements in CDB looks change with following environment and procedure:

 

Old   NSO 4.5.3  NED cisco-ios 6.20.3 (in production network, 2,000 devices, 20,000 over service instances) 

New  NSO5.5.1  NED cisco-ios 6.71

 

  1.  upgrade NSO 4.5.3 to 5.5.1
  2.  re-deploy dry-run each services instances to identify what happens after upgrade NSO
  3.  We expect Nothing is displayed but some differece is displayed in dry-run results.

 

dry-run results(outformat cli) in NSO 5.5.1:

 

user@ncs# test-service 1000 re-deploy dry-run { outformat cli }
cli {
    local-node {
        data  devices {
                   device cisco-ios-device{
                       config {
                           class-map Marking_CS2 {
                               match {
                                   access-group {
                                   }
                               }
                           }
                           class-map Marking_CS4 {
                               match {
                                   access-group {
                                   }
                               }
                           }
                           interface {
                               GigabitEthernet 1/0/1 {
                                   speed-auto {
                                       speed {
                                       }
                                   }
                               }
                           }
                       }
                   }
               }
          }
    }
}
user@ncs#

 

 

We also checked re-deploy dry-run outformat native reults, the results say nothing to perform to devices.

 

dry-run results(outformat native) in NSO 5.5.1:

 

user@ncs# test-service 1000 re-deploy dry-run { outformat native }
native {
}

 

 

We have already cheked YANG files of NED(cisco-ios) but the elements has not changed. However, elements show difference in re-deploy dry-run are only leaf-list element. I guess the architecure of leaf-list has changed from NSO 4.x to NSO 5.x. It means this is not NED version issue.

 

See example below:

 

NSO 4.5.3

 

user@ncs# show running-config devices device cisco-ios-device config ios:class-map Marking_CS2 | display json
{
  "data": {
    "tailf-ncs:devices": {
      "device": [
        {
          "name": "cisco-ios-device",
          "config": {
            "tailf-ned-cisco-ios:class-map": [
              {
                "name": "Marking_CS2",
                "prematch": "match-any",
                "match": {
                  "access-group": {
                    "name": ["Marking_CS2"]
                  }
                }
              }
            ]
          }
        }
      ]
    }
  }
}

NSO 5.5.1

 

 

user@ncs# show running-config devices device cisco-ios-device config class-map Marking_CS2 | display json
{
  "data": {
    "tailf-ncs:devices": {
      "device": [
        {
          "name": "cisco-ios-device",
          "config": {
            "tailf-ned-cisco-ios:class-map": [
              {
                "name": "Marking_CS2",
                "prematch": "match-any",
                "match": {
                  "access-group": {
                    "name": "Marking_CS2"
                  }
                }
              }
            ]
          }
        }
      ]
    }
  }
}

Access-group element is leaf-list. As you can see, leaf-list element is used as List data in NSO 4.5.3, but it is used as String in NSO5.5.1. 

 

 

We would like to know following points:

 

1. Is this affected by leaf-list architecture change or other reason?

2. Should we re-deploy or re-deploy reconcile after upgrading NSO 5.5.3?

 

Regards,

Tomoya Watanabe

1 ACCEPTED SOLUTION

Accepted Solutions

 

Didn't an upgrade to NSO 4.7 as an intermediate step fix the issue?
ENG-19697 is fixed in NSO 4.6.5.

If you need further support or trouble shooting I suggest you
raise a case with TAC.

View solution in original post

6 REPLIES 6
perander
Cisco Employee

It is recommended to upgrade to the latest NSO 4.7 release
and upgrade to a NSO 5.* after that.

Does this behavior prevail after an intermediate upgrade to
NSO 4.7?

Thank you for your response.

 


@perander さんは書きました:

It is recommended to upgrade to the latest NSO 4.7 release
and upgrade to a NSO 5.* after that.

Does this behavior prevail after an intermediate upgrade to
NSO 4.7?


Could you tell me the reason or document regarding this information?

 

 

I was wrong! The CDM migration guide, states that upgrades from
NSO 4.x.y, x >= 5 are supported. However, the leaf-list representation
changed in NSO 4.5 (see ENG-15312).

There are several leaf-list fixes between NSO 4.5 and 4.7 as well.
In particular ENG-19697 might be related:

  - cli: When combining tailf:cli-list-syntax, leaf-list, sibling leafs and 
omitting the tailf:cli-multi-word option the CLI would still consider
the tailf:cli-multi-word to be active. This could create faulty
list-entries in the leaf-list. The CLI has been fixed to check the for
the tailf:cli-multi-word option and otherwise properly create multiple
list-entries.

The cisco-ios YANG model uses tailf:cli-list-syntax for /.../access-group/name.

Thanks.

I've already check the release notes nad I am on same pages.

 

What I want to know is why these difererence is apprering and how I can fix it.

However, I can' t see this URL https://jira-eng-gpk3.cisco.com/jira/browse/ENG-15312.
Could you please right to read this jira issue?

 

Didn't an upgrade to NSO 4.7 as an intermediate step fix the issue?
ENG-19697 is fixed in NSO 4.6.5.

If you need further support or trouble shooting I suggest you
raise a case with TAC.

View solution in original post

Thanks! 

 

I will try to upgrade NSO 4.7.x first and share the results later.