Jathan McCollum
Jathan McCollum
@mdetrez Can you please tell me on which Cisco hardware platform and OS version you're experiencing this? I'd like to try to reproduce it and debug it for myself. What...
Unfortunately this is a known issue w/ `trigger.contrib.docommand` that we have yet to rectify! See: #152 Thanks for reporting this.
We really need a design doc around this. Not just for vendor support, but also breaking out the ssh, telnet, and driver functionality into separate modules as well.
Yes, you are correct. I think there's already that condition, but maybe I'm wrong? Ref: https://github.com/trigger/trigger/blob/develop/trigger/netdevices/loaders/filesystem.py#L153
Ohhhh yeah. I remember that now. Ugh.
There are two flags that attempt to modify this behavior, but I seem to recall there being some more flaws to them working as intended: ``` -d, --include-disabled include disabled...
Yeah this came up in https://github.com/trigger/trigger/issues/257, item 4.
However, on a device I have that has an unnumbered interface, `-u/--include-unnumbered` does seem to work as expected: ``` $ gnng juniper-fw1 --include-unnumbered DEVICE: juniper-fw1 Interface | Addresses | Subnets...
@supertylerc "ip unnumbered" although I don't think the distinction is really that well-defined. It's pretty much "any interface without an IP address".
Patch provided by Greg: ``` diff tacacsrc.py patch > +from trigger.netdevices import NetDevices + +def get_realm(device): + nd = NetDevices() + dev = nd[device] + return dev.realm + @@ -122,7...