Hi, as I can't find anything in the documentation and on google, but maybe I just search wrong. Can the line length of vtysh be changes? It looks like its wrapping lines at 80 columns which makes it harder to parse the output in shell script. Jens -- ---------------------------------------------------------------------------- | Delbrueckstr. 41 | 12051 Berlin, Germany | +49-151-18721264 | | http://blog.quux.de | jabber: jenslink@quux.de | --------------- | ----------------------------------------------------------------------------
Output in VTYSH is controlled by the individual command handlers; afaik there is no global wrapping, we just generally try to keep output to 80 chars. But it sounds like you're seeing hard wrapping somewhere; example? On Fri, Apr 24, 2020, 7:45 AM Jens Link <lists@quux.de> wrote:
Hi,
as I can't find anything in the documentation and on google, but maybe I just search wrong.
Can the line length of vtysh be changes? It looks like its wrapping lines at 80 columns which makes it harder to parse the output in shell script.
Jens --
---------------------------------------------------------------------------- | Delbrueckstr. 41 | 12051 Berlin, Germany | +49-151-18721264 | | http://blog.quux.de | jabber: jenslink@quux.de | --------------- |
----------------------------------------------------------------------------
_______________________________________________ frog mailing list frog@lists.frrouting.org https://lists.frrouting.org/listinfo/frog
Quentin Young <qlyoung@cumulusnetworks.com> writes:
Output in VTYSH is controlled by the individual command handlers; afaik there is no global wrapping, we just generally try to keep output to 80 chars. But it sounds like you're seeing hard wrapping somewhere; example?
Hope the mail client doesn't make it worse but it looks something like this: vtysh -c "show bgp ipv6 2001;db8::/32 longer-prefixes [...] Network Next Hop Metric LocPrf Weight Path *> 2001:db8::/48 fe80::e6aa:5dff:aaaa:bbbb 0 65536 65537 65638 i Each entry is split into tree line: Network, Nexthop and the rest. Jens -- ---------------------------------------------------------------------------- | Delbrueckstr. 41 | 12051 Berlin, Germany | +49-151-18721264 | | http://blog.quux.de | jabber: jenslink@quux.de | --------------- | ----------------------------------------------------------------------------
Am 24.04.2020 um 17:47 schrieb Jens Link <lists@quux.de>:
Quentin Young <qlyoung@cumulusnetworks.com> writes:
Output in VTYSH is controlled by the individual command handlers; afaik there is no global wrapping, we just generally try to keep output to 80 chars. But it sounds like you're seeing hard wrapping somewhere; example?
Hope the mail client doesn't make it worse but it looks something like this:
vtysh -c "show bgp ipv6 2001;db8::/32 longer-prefixes
[...]
Network Next Hop Metric LocPrf Weight Path *> 2001:db8::/48 fe80::e6aa:5dff:aaaa:bbbb 0 65536 65537 65638 i
Each entry is split into tree line: Network, Nexthop and the rest.
Jens
Hi Jens, do you know that you can add ‚json‘ to many commands for appropriate output? Best Regards Jan
Jan Marquardt <jm@artfiles.de> writes: Hi,
do you know that you can add ‚json‘ to many commands for appropriate output?
yes but then I have to pipe the output through jq or something similar. For now I pipping into another grep which is totally fine for my use case. Jens -- ---------------------------------------------------------------------------- | Delbrueckstr. 41 | 12051 Berlin, Germany | +49-151-18721264 | | http://blog.quux.de | jabber: jenslink@quux.de | --------------- | ----------------------------------------------------------------------------
I see the same behavior with just a simple `show bgp ipv6 uni` output: *> 2c0f:fc89:807f::/48 ::ffff:4113:867a 0 15096 6939 3257 8452 36992 i This was an attempt to make everything fit within a 80 column display I would guess since v6 routes are clearly going to be quite long. This is just part of the normal bgp v6 route display. donald On Fri, Apr 24, 2020 at 11:45 AM Jens Link <lists@quux.de> wrote:
Quentin Young <qlyoung@cumulusnetworks.com> writes:
Output in VTYSH is controlled by the individual command handlers; afaik there is no global wrapping, we just generally try to keep output to 80 chars. But it sounds like you're seeing hard wrapping somewhere; example?
Hope the mail client doesn't make it worse but it looks something like this:
vtysh -c "show bgp ipv6 2001;db8::/32 longer-prefixes
[...]
Network Next Hop Metric LocPrf Weight Path *> 2001:db8::/48 fe80::e6aa:5dff:aaaa:bbbb 0 65536 65537 65638 i
Each entry is split into tree line: Network, Nexthop and the rest.
Jens -- ---------------------------------------------------------------------------- | Delbrueckstr. 41 | 12051 Berlin, Germany | +49-151-18721264 | | http://blog.quux.de | jabber: jenslink@quux.de | --------------- | ----------------------------------------------------------------------------
_______________________________________________ frog mailing list frog@lists.frrouting.org https://lists.frrouting.org/listinfo/frog
participants (4)
-
Donald Sharp -
Jan Marquardt -
Jens Link -
Quentin Young