Both do the same. Older images supported l2tranport with MPLS encap only while the newer ones support xconnect with both l2tpv3 and MPLS with a whole host of other features including interworking, preferred-path, pseudowire redundancy etc.
xconnect is the new command, l2transport is there for backwards compatibility.
From the documentation:
In previous releases of AToM, the command used to configure AToM circuits was mpls l2 transport route. This command has been replaced with the xconnect command.
No new CLI enhancements will be made to the mpls l2transport route command. CLI enhancements will be made to either the xconnect command or pseudowire-class command. Therefore, we recommend that you use the xconnect command to configure AToM circuits.
Configurations from previous releases that use the mpls l2transport route command are still supported.
1. Introduction Internet security is important with the increasing
attacks that are happening every day. Many internet and browsing
security solutions exist, but some are not very easy to use or maybe the
question is how can I enable them? In this referen...
Cisco Software Manager Server API Guide This document describes the
programmatic interfaces, RESTful APIs, which are supported by Cisco
Software Manager Server (CSM Server). Overview CSM Server supports a set
of finite RESTful APIs. The first step to use ...
If you are using Cisco's new linux-based Cisco Software Manager server,
then you probably want to make sure there is a startup service for
it.I'll assume that you've already installed the CSM server on a
systemd-based linux system. The commands given belo...