I would like to get some advise in a tag-switching config in order to perform a testing: I have a Cisco 12012 and a Cisco 7507 each with a GigE interface. I would like to establish several tdp sessions using this single interface. I was thinking in creating sub-interfaces and to add a dot1.q vlan tag to each of them and then to configure tag-swithching in all of the sub-interfaces. I wonder if this might work.
I cannot perform this test right now since I have my equipment in different sites so if I am certain of this to work I might transport them.
what Harold pointed out is because in frame-mode MPLS you have one label space per platform (A.B.C.D:0) and there is only one TDP/LDP TCP session per address space.
In case you have an ATM network and configure cell-based MPLS you could end up with several TDP/LDP sessions between two routers.
Anyhow, I am assuming you are not really intersted in several LDP sessions but in MPLS forwarding (label switching) across several interfaces. If my assumption is true, please be aware that you would need 3 routers or - because of penultimate hop popping - you would need MPLS VPN to see labeled packets crossing the interfaces.
In fact what I want to achieve is to establish several (as many as possible) tdp sessions among my 12K and any other Cisco router, so I am not seeking for the label switching functionalities.
Soon after I posted my message I created in my lab a FE back to back connection among two 7507s and configured as I said: sub-interfaces tagged with dot1q and added a /30 in each of them. Afterwards I configured tag-switching in all the subinterfaces and could see that the tdp sessions were created. Certainly I did not verify the TCP sessions linked to the tdp sessiones neither did debugging to see messages but I think that this scenario might work for what I want: to give some stress in tdp sessions to my 12K as I have in production.
Our core is based in 12Ks and runs tag-switching so I am figuring out how to test a migration scenario towards mpls, this is my final goal. I want to observe a 12012´s performance while handling tdp and ldp sessions at the same time. ANY SUGGESTIONS? :)
as written above there will be only one LDP TCP session per neighbor in frame-mode MPLS. So this means you can increase the number of hellos produced, but not really an LDP stress test. What you could do is to take a route generator and flood the IGP with a number of routes equal to the one in your backbone, as for every IP route in IGP LDP has to choose a label and advertise it. Then tear down the session and check what happens.
But generally LDP creates not a lot of stress to your router as it only sends hellos unless IGP changes occur. In this case IGP calculation would presumably stress much more than LDP.
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...