On Fri, Mar 9, 2018 at 8:32 PM, Phil Shafer wrote:
> Martin T writes:
>>However, the actual point of my question was, that where do "show ipv6
>>neighbors" and similar commands take the column names and the answer
>>seems to be, that this is hard-coded in the binary. For example
Martin T writes:
>However, the actual point of my question was, that where do "show ipv6
>neighbors" and similar commands take the column names and the answer
>seems to be, that this is hard-coded in the binary. For example
>nd6info in case of "show ipv6 neighbors".
No, this isn't true. The CLI
Martin T writes:
>http://xml.juniper.net/junos/16.1R2/junos;>
>
>
>IPv6 Address
>
>2001:db8:cfe:0:192:168:222:55
>
One of the goals of the API was to keep "meta data" out of the data,
both to make it simpler and to keep the size
Hey Martin,
I get what you're saying, but I think the problem is backwards. CLI is
opinionated, CLI mangles the backend data.
So you should rather complain why CLI isn't used the right words.
I understand what you're saying, but I don't agree it makes sense. It
would add work, as you still
On Fri, Mar 9, 2018 at 2:25 PM, Saku Ytti wrote:
> Ah.
>
> Your point is that the strings are different? CLI says 'Rtr' tag says
> 'isrouter'?
>
> I can't relate this being a problem, sorry. The data is there, you can
> classify and reprint it as you wish.
>
> On 9 March 2018 at
Ah.
Your point is that the strings are different? CLI says 'Rtr' tag says
'isrouter'?
I can't relate this being a problem, sorry. The data is there, you can
classify and reprint it as you wish.
On 9 March 2018 at 12:37, Martin T wrote:
> On Thu, Mar 8, 2018 at 11:51 AM,
On Thu, Mar 8, 2018 at 11:51 AM, Saku Ytti wrote:
> Hey Phil,
>
> I'm hijacking this for a bit.
>
> You have | display json and xml, I assume json was relatively modest
> amount of work, as you have formal source of data, so someone only
> needed to write translator, without being
Hey Phil,
I'm hijacking this for a bit.
You have | display json and xml, I assume json was relatively modest
amount of work, as you have formal source of data, so someone only
needed to write translator, without being aware of all context to
support | display json, which also means, no one needs
Martin T writes:
>I have noticed that certain commands executed on CLI provide some
>additional information over corresponding RPCs. For example "show ipv6
>neighbors" or "show system storage" on CLI show column names while XML
>output does not contain this data. Why is that so?
Both the CLI and
Hey Martin,
I don't follow you, the 'column' names are not needed, as they are in the tags?.
y...@r21.labxtx01.us.bb> show ipv6 neighbors
IPv6 Address Linklayer Address State Exp Rtr
Secure Interface
fe80::290:69ff:fefb:b7f3 00:90:69:fb:b7:f3 reachable 12 yes no
10 matches
Mail list logo