[rancid] Cisco 3650 IOS-XE active VLAN port state changes
Piegorsch, Weylin William
weylin at bu.edu
Sat Nov 23 21:50:06 UTC 2019
You can also develop a custom type that doesn't call "show vlan".
Also, I've had this occur twice in the past.
- One time was happening campus-wide. I dug into it hard, and after a good amount of effort found out there was something actually happening based on a misunderstanding I had about native VLANs work in IOS. In other words: (a) I learned something, and (b) I found I had an actual misconfiguration.
- The other time it turned out that there was a hardware fault on the ASIC (we're actually still using that particular Catalyst 3508).
On 11/22/19, 8:08 PM, "on at LEFerguson.com" <on at LEFerguson.com> wrote:
Yeah, this is something I keep meaning to change as well. I haven't done it, but I think you can just put something like
next if (^!VLAN:);
in showVLAN in ios.pm. You'll see similar checks. But I also just want to put a plug in that this is a good candidate for a rancid option. I would think that people fall into two camps -- those who declare VLAN's by interface (and so are not likely to want to see the changes as interfaces change) and those who do not (who might).
Just a thought...
From: Rancid-discuss [mailto:rancid-discuss-bounces at shrubbery.net] On Behalf Of Troy Beisigl
Sent: Friday, November 22, 2019 7:58 PM
To: rancid-discuss at shrubbery.net
Subject: [rancid] Cisco 3650 IOS-XE active VLAN port state changes
We are seeing an issue on several WS-C3650-48PS (IOS-XE) switches whereby almost every rancid check shows changes that are solely the port showing active or inactive on a particular vlan. Is there some way to ignore that? This appears to happen when a port state changes. An example of what we see each time is below.
- !VLAN: 10 VLAN0010 active Gi1/0/3, Gi1/0/4, Gi1/0/5, Gi1/0/6, Gi1/0/7, Gi1/0/8, Gi1/0/9, Gi1/0/10, Gi1/0/11
- !VLAN: Gi1/0/13, Gi1/0/14, Gi1/0/15, Gi1/0/16, Gi1/0/17, Gi1/0/18, Gi1/0/19, Gi1/0/20
- !VLAN: Gi1/0/21, Gi1/0/22, Gi1/0/23, Gi1/0/24, Gi1/0/25, Gi1/0/26, Gi1/0/27, Gi1/0/28
- !VLAN: Gi1/0/29, Gi1/0/30, Gi1/0/31, Gi1/0/32, Gi1/0/33, Gi1/0/34, Gi1/0/35, Gi1/0/36
- !VLAN: Gi1/0/37, Gi1/0/38, Gi1/0/39, Gi1/0/40, Gi1/0/41, Gi1/0/42, Gi1/0/43, Gi1/0/44
- !VLAN: Gi1/0/45, Gi1/0/46, Gi1/0/47, Gi2/0/1, Gi2/0/2, Gi2/0/3, Gi2/0/4, Gi2/0/5, Gi2/0/6
- !VLAN: Gi2/0/7, Gi2/0/8, Gi2/0/9, Gi2/0/10, Gi2/0/11, Gi2/0/12, Gi2/0/13, Gi2/0/14
+ !VLAN: 10 VLAN0010 active Gi1/0/2, Gi1/0/3, Gi1/0/4, Gi1/0/5, Gi1/0/6, Gi1/0/7, Gi1/0/8, Gi1/0/9, Gi1/0/10
+ !VLAN: Gi1/0/11, Gi1/0/13, Gi1/0/14, Gi1/0/15, Gi1/0/16, Gi1/0/17, Gi1/0/18, Gi1/0/19
+ !VLAN: Gi1/0/20, Gi1/0/21, Gi1/0/22, Gi1/0/23, Gi1/0/24, Gi1/0/25, Gi1/0/26, Gi1/0/27
+ !VLAN: Gi1/0/28, Gi1/0/29, Gi1/0/30, Gi1/0/31, Gi1/0/32, Gi1/0/33, Gi1/0/34, Gi1/0/35
+ !VLAN: Gi1/0/36, Gi1/0/37, Gi1/0/38, Gi1/0/39, Gi1/0/40, Gi1/0/41, Gi1/0/42, Gi1/0/43
+ !VLAN: Gi1/0/44, Gi1/0/45, Gi1/0/46, Gi1/0/47, Gi2/0/1, Gi2/0/2, Gi2/0/3, Gi2/0/4, Gi2/0/5
Rancid-discuss mailing list
Rancid-discuss at shrubbery.net
More information about the Rancid-discuss