Ive been through this myself. The short of it is that you will need a
VPLS instance for each VLAN you wish to carry on SRX.
I dont remember the exact details, but the MX do some "magic" to
automatically carry multiple VLANs through a single VPLS instance,
whereas the SRX do not.
Try as you
Martin T writes:
>Thanks! So as I understand, the general idea is that it doesn't matter
>much for Junos if the command is executed in the CLI or from the
>remote(management server) NETCONF manager, i.e. Junos is basically
>built around the NETCONF? However, local calls(for example if one
>
> Looks like an implementation issue. Our UI infrastructure allows
> our programmers to define completion functions to list acceptable
> values. Some schmuck's coded the completion function as this "sh -c show
> route summary| ..." command.
>
> This is definitely not typical. More typically,
Martin T writes:
>While I understand the idea of namespace in XML, then what is the
>point of those statements in SLAX scripts? In addition, how does the
>"version" statement work?
The version statement indicates the version of SLAX being used. It
also confirms that the input is in fact a slax
Luke Flemington writes:
>The Junos configuration file is also represented as an XML file.
Just to be clear, the JUNOS config database is a object database. The
objects are describes by data models in such a way that we can render
them into XML, but the database is not an XML database. It's a
Stepan Kucherenko writes:
>Sometimes it does strange stuff with SSH internally though. Example:
>
>Let's say I do " show route table ?" at a router.
>
>Logs show:
>
>mgd[62935]: UI_CHILD_START: Starting child '/bin/sh'
>mgd[68498]: UI_AUTH_EVENT: Authenticated user 'root' at permission level
Hi,
I am trying to pass multiple VLAN via single VPLS routing instance and
assume separate learning domain for every single VLAN. I tried knob
"vlan-id all" under routing instance without success. O MX series it
works, it create multiple learning domain, on SRX 240 (second site) nope
and same MAC
On 24/12/2015 09:10, Phil Shafer wrote:
The real value is that the API comes for free, since it's using the
same internal plumbing. This means that when a feature ships in
the CLI, it's immediately available in the API. No lag. No
additional cost. No missing bits. It's literally all there
8 matches
Mail list logo
