Wait here.
You got JUNOS 9.X to work with Olive? Is it only in QEMU or have someone
actually gotten it to work in VMWare aswell?
Cheers
Patrik
All.
This patched works with the lastest qemu stream,
http://juniper.cluepon.net/index.php/Olive; confirmed working on junos
9.3 :-
Since
Patrick Lynchehaun patr...@lynchehaun.net writes:
Bjørn
Tks for this link.
Got a reply from Sten Weil with an updated link:
http://repo.or.cz/w/qemu/ar7.git?a=blob;f=hw/eepro100.c
The quick/dirty fix below works for mcast traffic with current qemu
cvs.
Yes, but it probably doesn't
I think you got confused with concepts of signaling protocol and lsp istelf.
mpls is foundation of all new technologies that rely on mpls label switching.
but mpls lsp depends on signaling protocols such as rsvp or ldp for the label
swapping. bgp is still the protocol that utilize the lsp (in
AFAIK, JUNOS uses the Adspec field for maximum transmission unit (MTU)
negotiation.
So when an LSP is created across a set of links with different MTU
sizes, the ingress router does not know what the smallest MTU is on the
LSP path. By default, the maximum packet size for the LSP is based on
the
Hi Nalkhande.
Thanks for your help.
MTU information goes inside the PATH message, on object ADSPEC -
Default General Parameters data fragment.
What I need is the command to include in the PATH Message the following
object:
ADSPEC - Guaranteed Service data fragment (described on RFC2210, item
We state we support the rfc, which I believe means we can process a Path
message with such an Adspec, but AFAIK, there is no way to configure the
ingress node to populate a GS based Adspec. JUNOS does mpls QoS via DiffServ
TE, not IntServ.
HTHs
-Original Message-
From:
Dear Folks,
Has this certification been launched??? can any one provide the outline/Info
for this please.
Thanks in advance,
regards,
--
Muhammad Fahad Khan
IT Specialist
Global Technology Services, IBM
fa...@pk.ibm.com
+92-321-2370510
+92-301-8247638
As far as I know, no..
It was created and even beta tested. There are a couple of juniper (and
former juniper) employees walking around with the title but last I heard it
is not available to the public.
Without any inside knowledge I would attribute this to the SRX platform and
the Junos
8 matches
Mail list logo