Accepted Solutions
Hi, something I noticed in my case, is that the management interface in the XR nodes has no configuration and is shutdown. I just created a new sandbox and test it, it worked.
Reviewing the nodes in CML (https://10.10.20.161/) I can see there is a day-0 configuration for the nodes.
However if we go to the XR node, I see the interface is empty
RP/0/RP0/CPU0:core-rtr02#show run int MgmtEth0/RP0/CPU0/0
Mon Jul 3 13:42:49.144 UTC
interface MgmtEth0/RP0/CPU0/0
shutdown
!
RP/0/RP0/CPU0:core-rtr02#If you look closely, you can see the name of the mgmt interfaces are different in the day-0 and in the xr node. One is MgmtEth0/0/CPU0/0 and the other MgmtEth0/RP0/CPU0/0. XR is actually loading this config, but as a preconfigure interface since is not able to find it. I believe this is the result of a recent upgrade to the sandbox.
In my case, this was the issue I was having with the mgmt of the XR nodes when using the NSO reservable sandbox.
To fix it, copy the mgmt configuration that is under the "edit config" tab on the XR node in CML and apply it to the current XR mgmt interface MgmtEth0/RP0/CPU0/0.
Another issue you may find when entering the XR nodes from the console, is that it will ask you for an username & password, in my case I used root/cisco123 but I also configured a cisco/cisco user and pass since NSO is expecting to work with cisco/cisco. Feel free to experiment in NSO to use other credentials for the XR nodes, but if you want to use cisco/cisco for the learning lab you can use the following configuration to the XR nodes.
username cisco
group root-lr
group cisco-support
secret 10 $6$79vo/0mCRUH56/0.$LBYhgKtuzl6zy6DOrCUgHewAQ4VC6084hinDJ1Z81T1m2fOgph0QKNWYqgsjI3.SCuAa0Uk04GE1w6hG1Q1jN.
!I hope this helps, in my case it resolved my issues. I'm also informing the sandbox team about this, so this solution can be applied automatically.
By the way, for this sandbox, if you have issues with resources is better to release your current reservation and create a new one.
Hi, something I noticed in my case, is that the management interface in the XR nodes has no configuration and is shutdown. I just created a new sandbox and test it, it worked.
Reviewing the nodes in CML (https://10.10.20.161/) I can see there is a day-0 configuration for the nodes.
However if we go to the XR node, I see the interface is empty
RP/0/RP0/CPU0:core-rtr02#show run int MgmtEth0/RP0/CPU0/0
Mon Jul 3 13:42:49.144 UTC
interface MgmtEth0/RP0/CPU0/0
shutdown
!
RP/0/RP0/CPU0:core-rtr02#If you look closely, you can see the name of the mgmt interfaces are different in the day-0 and in the xr node. One is MgmtEth0/0/CPU0/0 and the other MgmtEth0/RP0/CPU0/0. XR is actually loading this config, but as a preconfigure interface since is not able to find it. I believe this is the result of a recent upgrade to the sandbox.
In my case, this was the issue I was having with the mgmt of the XR nodes when using the NSO reservable sandbox.
To fix it, copy the mgmt configuration that is under the "edit config" tab on the XR node in CML and apply it to the current XR mgmt interface MgmtEth0/RP0/CPU0/0.
Another issue you may find when entering the XR nodes from the console, is that it will ask you for an username & password, in my case I used root/cisco123 but I also configured a cisco/cisco user and pass since NSO is expecting to work with cisco/cisco. Feel free to experiment in NSO to use other credentials for the XR nodes, but if you want to use cisco/cisco for the learning lab you can use the following configuration to the XR nodes.
username cisco
group root-lr
group cisco-support
secret 10 $6$79vo/0mCRUH56/0.$LBYhgKtuzl6zy6DOrCUgHewAQ4VC6084hinDJ1Z81T1m2fOgph0QKNWYqgsjI3.SCuAa0Uk04GE1w6hG1Q1jN.
!I hope this helps, in my case it resolved my issues. I'm also informing the sandbox team about this, so this solution can be applied automatically.
By the way, for this sandbox, if you have issues with resources is better to release your current reservation and create a new one.
