[rancid] Nexus 1000v switch-router

[Charles T. Brooks]

Well, it works with device-type cisco, but not with device-type cisco-nx, so I'm pretty sure the transport layer is fine.

When you use device-type cisco with an NX-os device like a Nexus switch, each time a port is assigned you will get a great deal of spurious output.  This is because the NX-os devices report VLAN configurations like this:


VLAN Name                             Status    Ports
---- -------------------------------- --------- -------------------------------
1    default                          active
100  VLAN0100                         active    Po3, Po4, Po5, Po6, Po7, Po8
                                                Veth1, Veth2, Veth4, Veth7
                                                Veth9, Veth10, Veth13, Veth14
                                                Veth15, Veth16, Veth17, Veth18
                                                Veth21, Veth22, Veth23, Veth24
                                                Veth25, Veth26, Veth29, Veth30
                                                (etc. to arbitrary number of ports)

If, in the example above, I delete virtual ethernet port #2 (Veth2) it will cause changes in roughly 24 lines, because NX-os will rejigger every single line for this vlan by "bumping up" the ports into the four-ports per line form.  Does that make sense?  Anyway, somebody moves one or two ports, and instead of getting the actual one or two line config change I get 40 or fifty lines of noise emailed to all the netadmins.

The cisco-nx device type addresses this problem (although frankly I don't know how;  I suspect it just doesn't do a "show vlan" command).

--Charlie



________________________________________
From: Josh Hildebrand [JHildebrand at newgistics.com]
Sent: Thursday, June 30, 2016 10:57 AM
To: Charles T. Brooks
Subject: RE: Nexus 1000v switch-router

Sounds like an SSH or vty access-list issue, honestly..
Test with "clogin <hostname>" on the command line.. if it doesn't work, then RANCID has no chance of working..

-----Original Message-----
From: Rancid-discuss [mailto:rancid-discuss-bounces at shrubbery.net] On Behalf Of Charles T. Brooks
Sent: Thursday, June 30, 2016 9:34 AM
To: rancid-discuss at shrubbery.net
Subject: [rancid] Nexus 1000v switch-router

Hullo all

  I've poked around the list archives and haven't found any information about using RANCiD with the Cisco 1000V virtualized switch/router.  (Information on that product here - http://www.cisco.com/c/en/us/products/collateral/switches/nexus-1000v-switch-vmware-vsphere/data_sheet_c78-492971.html)

  If I use a device type of "cisco" it works, but has the same minor but annoying problems that you get when monitoring a Nexus 5K with device type cisco.  If I use device type "cisco-nx" it simply does not work at all - after 24 hours I start getting the "unable to connect to device" emails every hour.   Has anyone else run into this yet, or am I the first?

--Charlie

PS:   I implemented rancid with git and gitweb a month ago and set up monitoring and automatic remote git a month or so ago and it's FANTASTIC... saves me a lot of work and the price is right.  Thank you Mr. Heasley and co-conspirators!

--C
       ------------------  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  ---------------

_______________________________________________
Rancid-discuss mailing list
Rancid-discuss at shrubbery.net
http://www.shrubbery.net/mailman/listinfo/rancid-discuss


Confidentiality Notice: This email and any attachments accompanying this electronic transmission may contain confidential and privileged information. The information is intended for the sole use of the intended recipient(s) and entity named above. If you are not the intended recipient, you are hereby notified that any further distribution, disclosure, copying, or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this transmission in error, please notify the sender immediately and destroy all copies of the original message.
       ------------------  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  ---------------