The reason that you can not access the router via telnet or via SDM is that the router has no active IP address for you to access. The only interface that is configured with an IP address is also shutdown:
ip address 172.26.0.1 255.255.0.0
If you will no shutdown the interface then you should find that telnet, or SSH, or SDM should work.
 I am not sure how, but when I saw the original post I did not see that there had been responses. After my response posted then I see that Mark has already responded with the same observation of the shutdown interface that I made (sorry for the duplication).
Anand - if you would post the output of "show ip interface brief" it would help us to understand what is happening here and to clarify the status of the interfaces.
Thanks for the additional information. It clearly shows that the interfaces are up / up and therefore are available. There obviously have been some config changes (no interface shutdown and the second interface has an address). Are you still having the problem with telnet and SDM? If so then the questions that Mark raised about are you able to ping the router from the PC become important.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...