cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
282
Views
0
Helpful
4
Replies
khgrant
Cisco Employee

Juniper to Cisco - Config. Migration.

 

Can one use NCS or netsim to convert Juniper device configuration to ASR9K/IOSXR ?

 

 

Best Regards,

Kamal

 

1 ACCEPTED SOLUTION

Accepted Solutions
khgrant
Cisco Employee

 

Kamal,

 

 

Nabil is right on the device manager level. There's no easy way to do a translation there, because it's very hard in general to infer the operator's intent with the configuration, so that we can translate into the same intent on the other device.

 

 

If we also have a service on the service manager, however, the situation typically gets a lot better. Then we do have a representation of the operator intent. Then it's simply a matter of making the service application capable of using Cisco and Juniper devices. With this in place, you can easily switch between device types, as we do in our demos.

 

 

In some cases, we have built service applications (with service reconciliation) just to be able to do what you ask, switch from one device type to another. This is not only useful for Juniper to Cisco, but also from one Cisco device type to another.

 

 

Best Regards,

 

/jan

 

View solution in original post

4 REPLIES 4
khgrant
Cisco Employee

 

Kamal,

 

 

 

I don't think this is possible in netsim or NCS. Data follows the YANG schema format.

 

 

If two devices have the same YANG model then it's obvious. If they implement standard modules and differ on some modules, you can copy the config under the standard modules using NETCONF.

 

 

 


Nabil Michraf

 

khgrant
Cisco Employee

 

Kamal,

 

 

Nabil is right on the device manager level. There's no easy way to do a translation there, because it's very hard in general to infer the operator's intent with the configuration, so that we can translate into the same intent on the other device.

 

 

If we also have a service on the service manager, however, the situation typically gets a lot better. Then we do have a representation of the operator intent. Then it's simply a matter of making the service application capable of using Cisco and Juniper devices. With this in place, you can easily switch between device types, as we do in our demos.

 

 

In some cases, we have built service applications (with service reconciliation) just to be able to do what you ask, switch from one device type to another. This is not only useful for Juniper to Cisco, but also from one Cisco device type to another.

 

 

Best Regards,

 

/jan

 

View solution in original post

khgrant
Cisco Employee

 

Hi Nabil,

 

 

I’m not quite sure, I agree.

 

Since Yang model is representation of syntactic configuration of device with controlled sequencing (for IOS).

 

One can (no so simply) define service which will “map” configuration in Junos to configuration in IOS/XR and apply it to IOS/XR device.

 

For example:

 

In Junos:

 

snmp {

……….

trap-group qf-traps {

destination-port 155;

targets {

192.168.0.100;

}

}

}

 

Can be translated into something like that

 

snmp-server host 192.168.0.100 traps v2c port 155 community iosxr

 

In IOS/XR

 

 

Thanks,

 

Steven S

khgrant
Cisco Employee

 

Hi!

 

In the classical nso mpls vpn demo I usually demo this by changing the topology. Move the cpe connected to pe2 (juniper) to another pe. Redeploy the service, voila!

Mvh stefan

 

Content for Community-Ad

This widget could not be displayed.