Hi,
On Sat, Nov 20, 2010 at 04:12:13AM +, David Rothera wrote:
They are moving over to a system where you will only be able to download SW
for devices that you have active service contracts for.
... and have managed to get that service contract attached to the CCO
username that you've
On 20.11.2010 12:26, Gert Doering wrote:
... and have managed to get that service contract attached to the CCO
username that you've used for logging in.
Now this might sound like a minor nit, but for us, it's major pains -
whenever we put a new device under contract, it seems to end up
Quick question - this is for my curiosity rather than anything, as I've
never done this before.
We have a few RAD IP-Mux boxes (E1-IP). They claim to support MPLS, and
allow you to specify an outgoing and incoming MPLS label for a circuit.
They don't seem to support any dynamic protocol e.g.
mpls static binding ipv4 should give you a start. You have to define some
label ranges first.
--
Tassos
Phil Mayers wrote on 20/11/2010 14:43:
Quick question - this is for my curiosity rather than anything, as
I've never done this before.
We have a few RAD IP-Mux boxes (E1-IP). They claim
On 11/20/2010 01:13 PM, Tassos Chatzithomaoglou wrote:
mpls static binding ipv4 should give you a start. You have to define some
label ranges first.
Hmm. I did spot that command, but it didn't seem applicable. Where do
the IPv4 addresses come from? It's a TDM link, not IP.
I was assuming
On Sat, Nov 20, 2010 at 12:26:27PM +0100, Gert Doering wrote:
Now this might sound like a minor nit, but for us, it's major pains -
whenever we put a new device under contract, it seems to end up having
a new contract number, and then the whole team goes and spends non-trivial
amount of time
Dear All,
My setup is (CE1 - CO1 - PE -- P1 - P2 - P3 - PE - CO2 - CE2)
The two PEs have the command no mpls ip propagate-ttl but found that when CE1
traces IP at CE2 the core link between (P2 - P3) is shown !
anyone faced such case or any ideas are welcomed...
hi everybody,
i was monitoring cisco's BGP packets and i realized my cisco's BGP keepalive
packets are being sent out exactly every 60 seconds (with no jitter - with
maximum 0.001 seconds variance).i looked at BGP main RFC (RFC4271) and it says
timers should have jitters and says:
[...]
