[rancid] Nexus 1000v switch-router

[Charles T. Brooks]

Correction to previous email:  inverting the VTP logic *does* result in the 5Ks having "show vlan" output in their rancid config files.  So, since that's apparently the desired behavior you'll probably want to keep that.

I'll probably take the "show vlan" command out of my own config, since I find it generates too much noise in my infrastructure and I've got all the vlan information in "show running-config" anyway.

The other change, though, (return -1 on invalid command) broke all Nexus backups.  You don't want that one!

--Charlie
________________________________________
From: Rancid-discuss [rancid-discuss-bounces at shrubbery.net] on behalf of Charles T. Brooks
Sent: Tuesday, July 05, 2016 12:21 PM
To: heasley
Cc: rancid-discuss at shrubbery.net
Subject: Re: [rancid] Nexus 1000v switch-router

Inverting the VTP logic and changing the return for "Invalid Command" to -1 resulted in all nexus switch backups failing, but I am very new to rancid so I wasn't sure that was actually happening until after 24 hours, at which point I started getting emails about it.

I reverted the change to the VTP logic and kept the other change, and that didn't fix it, so I did the vice-versa, and that restored the original behavior - 5K are backed up, 1Kv are not.

One thing I can say regarding the VTP stuff - on a Nexus 5K, there are exactly zero references to VTP in the configuration if you do not have "feature vtp" turned on.  So, testing for VTP operating mode should probably be something that only happens *after* testing for feature vtp.  The 1000v does not have feature vtp at this time, so it will always fail this test, unless a later release of the software brings the feature in.

BTW, the Nexus 5000 has 40 available features.   The Nexus 1000V has 16.   Of these, only 10 are the same on both devices; attached is a text file containing the list of features for each (linux/unix raw text, newlines only).

At this point I figure I'll make a new NX-os device type strictly for virtual devices, that eliminates the hardware probing.  I need to make one for the Ironport mail hub anyway, so I already have to learn how ;).

Thanks,
--Charlie

________________________________________
From: heasley [heas at shrubbery.net]
Sent: Friday, July 01, 2016 6:38 PM
To: Charles T. Brooks
Subject: Re: [rancid] Nexus 1000v switch-router

Fri, Jul 01, 2016 at 09:55:49PM +0000, Charles T. Brooks:
> OK, I'm not sure what's going on, so bear with me....  I made these changes to rancid 3.4.1 on RHEL 7:
>
> [root at git ~]# diff /usr/share/perl5/vendor_perl/rancid/nxos.pm /usr/share/perl5/vendor_perl/rancid/nxos.pm.2016-06-29
>
> 103c103
> <     $DO_SHOW_VLAN = 1;
> ---
> >     $DO_SHOW_VLAN = 0;
> 339c339
> <       return(-1) if (/\% Invalid command at /); # CTB for Heasley
> ---
> >       return(1) if (/\% Invalid command at /);
> 663,664c663,664
> <       if (!/^VTP Operating Mode\s+:\s+(Transparent|Server)/) {
> <           $DO_SHOW_VLAN = 0;
> ---
> >       if (/^VTP Operating Mode\s+:\s+(Transparent|Server)/) {
> >           $DO_SHOW_VLAN = 1;
>
> I then changed the device-type for the Cisco 1000v from "cisco" to "cisco-nx" and let it run the usual hourly scheduled stuff.
>
> Rancid correctly reported the change of device type via email, and /var/log/maillog is all copacetic.  However, it does not show any changes in the archive other than the line in router.db, nor have I been mailed any diffs.
>
>  I will let it run over the weekend and report back Tuesday.

are there errors in the group log?  is the timestamp on the saved file
being updated?
       ------------------  CONFIDENTIALITY NOTICE  ---------------

  This message, including any attachments, is for the sole use of the
intended recipient(s) and may contain privileged confidential information
protected by law. Any unauthorized review, use, disclosure or distribution
of this message is prohibited. If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of this message.

       ------------------  CONFIDENTIALITY NOTICE  ---------------
       ------------------  CONFIDENTIALITY NOTICE  ---------------

  This message, including any attachments, is for the sole use of the
intended recipient(s) and may contain privileged confidential information
protected by law. Any unauthorized review, use, disclosure or distribution
of this message is prohibited. If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of this message.

       ------------------  CONFIDENTIALITY NOTICE  ---------------