RE: Native VLAN 1 [7:55743]
yes...which is why a new one comes up as default on vlan 1 as the native vlan for all ports... Larry Letterman Network Engineer Cisco Systems Inc. -Original Message- From: [EMAIL PROTECTED] [mailto:nobody;groupstudy.com]On Behalf Of Ken Diliberto Sent: Thursday, October 17, 2002 9:08 PM To: [EMAIL PROTECTED] Subject: RE: Native VLAN 1 [7:55743] Sensing how easy it would be for me to make the same mistake... Does this mean the supervisor will come up with an existing configuration before automatic synchronization takes place? Larry Letterman 10/17/02 09:02AM mad, You are correct, teh second sup is the redundant sup... the config for it is on itself. So when I replaced it the new one was set for vlan 1 and that caused the issue. Larry Letterman Network Engineer Cisco Systems Inc. -Original Message- From: [EMAIL PROTECTED] [mailto:nobody;groupstudy.com]On Behalf Of MADMAN Sent: Thursday, October 17, 2002 7:35 AM To: [EMAIL PROTECTED] Subject: Re: Native VLAN 1 [7:55743] Since the config for the line cards resides on the sup there should be no problem swapping out same line cards, if the native VLAN was changed, the change will be employed on the new card also. When you swapped out a standby sup in your example below I don't quite understand what hapened. The standby sup uplinks are active so what changed?? When you say you swapped out the sceondary sup the redundant sup came up, isn't the secondary sup the redundant sup?? The greater point is though I agrre with Larry, leave the native VLAN as 1, changing it is of no value as far as I can tell. Dave Larry Letterman wrote: I personally changed out a secondary sup card, when I was new in the lan team.. the redundant sup came up with with the trunk port 2/1 config'd for native vlan 1. this caused the vtp management to issue a vlan mismatch...which then started a stp recalc, which caused utilization on the gateway to go up trying to process the bpdu storm, which prevented the network from working correctly... leaving everything in native 1 prevents this Larry Letterman Network Engineer Cisco Systems Inc. -Original Message- From: [EMAIL PROTECTED] [mailto:nobody;groupstudy.com]On Behalf Of Erick B. Sent: Wednesday, October 16, 2002 11:53 PM To: [EMAIL PROTECTED] Subject: Re: Native VLAN 1 [7:55743] Comments inline... --- The Long and Winding Road wrote: Larry Letterman wrote in message news:200210170505.FAA27055;groupstudy.com... Pris, In our 6509's we used to make the native vlan and the data vlan the same and it was something other than 1...if a blade fails and we put in a new one , it defaults to vlan 1 for all ports. If the blade has trunk ports in it, they get set to native vlan 1. The other end is set for something else, this resulted in vlan mismatch in the vtp domain, and in a lot of instances we suffered stp recalcs that took buildings down for periods of time...we subsequently have returned to making native vlan 1 on all trunks and have not had any issues since.. I want to clarify a few items so we fully understand this behavior so next time I need to hot-swap I am prepared to make config changes as well. I thought the running config in RAM (and NVRAM) stayed the same when swapping *same model* blades in the same slot. If this isn't the case, then is some of the config the same and some is defaulted? Can you point us to a cisco doc explaining this behavior? Thank you very much! __ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos More http://faith.yahoo.com -- David Madland CCIE# 2016 Sr. Network Engineer Qwest Communications 612-664-3367 You don't make the poor richer by making the rich poorer. --Winston Churchill Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=55860t=55743 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: Native VLAN 1 [7:55743]
Don't want to beat this to death but if you pull out the redundant sup the primary keeps running the show. After you reinstall the new redundant sup it should sync up with the primary, including the native VLAN info. Dave Priscilla Oppenheimer wrote: Thanks Larry and the others who responded. It's good to know about this potential problem. I hope you didn't mind me getting you embroiled in a discussion. ;-) I figured it would be good for learning, as it was. Priscilla Larry Letterman wrote: mad, You are correct, teh second sup is the redundant sup... the config for it is on itself. So when I replaced it the new one was set for vlan 1 and that caused the issue. Larry Letterman Network Engineer Cisco Systems Inc. -Original Message- From: [EMAIL PROTECTED] [mailto:nobody;groupstudy.com]On Behalf Of MADMAN Sent: Thursday, October 17, 2002 7:35 AM To: [EMAIL PROTECTED] Subject: Re: Native VLAN 1 [7:55743] Since the config for the line cards resides on the sup there should be no problem swapping out same line cards, if the native VLAN was changed, the change will be employed on the new card also. When you swapped out a standby sup in your example below I don't quite understand what hapened. The standby sup uplinks are active so what changed?? When you say you swapped out the sceondary sup the redundant sup came up, isn't the secondary sup the redundant sup?? The greater point is though I agrre with Larry, leave the native VLAN as 1, changing it is of no value as far as I can tell. Dave Larry Letterman wrote: I personally changed out a secondary sup card, when I was new in the lan team.. the redundant sup came up with with the trunk port 2/1 config'd for native vlan 1. this caused the vtp management to issue a vlan mismatch...which then started a stp recalc, which caused utilization on the gateway to go up trying to process the bpdu storm, which prevented the network from working correctly... leaving everything in native 1 prevents this Larry Letterman Network Engineer Cisco Systems Inc. -Original Message- From: [EMAIL PROTECTED] [mailto:nobody;groupstudy.com]On Behalf Of Erick B. Sent: Wednesday, October 16, 2002 11:53 PM To: [EMAIL PROTECTED] Subject: Re: Native VLAN 1 [7:55743] Comments inline... --- The Long and Winding Road wrote: Larry Letterman wrote in message news:200210170505.FAA27055;groupstudy.com... Pris, In our 6509's we used to make the native vlan and the data vlan the same and it was something other than 1...if a blade fails and we put in a new one , it defaults to vlan 1 for all ports. If the blade has trunk ports in it, they get set to native vlan 1. The other end is set for something else, this resulted in vlan mismatch in the vtp domain, and in a lot of instances we suffered stp recalcs that took buildings down for periods of time...we subsequently have returned to making native vlan 1 on all trunks and have not had any issues since.. I want to clarify a few items so we fully understand this behavior so next time I need to hot-swap I am prepared to make config changes as well. I thought the running config in RAM (and NVRAM) stayed the same when swapping *same model* blades in the same slot. If this isn't the case, then is some of the config the same and some is defaulted? Can you point us to a cisco doc explaining this behavior? Thank you very much! __ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos More http://faith.yahoo.com -- David Madland CCIE# 2016 Sr. Network Engineer Qwest Communications 612-664-3367 You don't make the poor richer by making the rich poorer. --Winston Churchill -- David Madland CCIE# 2016 Sr. Network Engineer Qwest Communications 612-664-3367 You don't make the poor richer by making the rich poorer. --Winston Churchill Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=55873t=55743 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: Native VLAN 1 [7:55743]
Ok this just didn't jive with my understanding so I went back to the lab and tried something. I have a 6509 with redundant supII's. On the redundant sup I have a trunk to a 3550 and the native VLAN is 64. I pulled out the active SUP, slot1. The redundant sup came active, all is good. I did a clear config all on the this sup. I then powered off the switch, pulled out the SUP in sot 2 and reinstalled the primry SUP in slot 1. Brought the switch back up and everything looked as I expected. I reinstalled the redundant SUP and after it initialized and synched up with the primary SUP port 2/2 was once again trunking with native VLAN 64. It acted as I thought it would. Dave Larry Letterman wrote: yes...which is why a new one comes up as default on vlan 1 as the native vlan for all ports... Larry Letterman Network Engineer Cisco Systems Inc. -Original Message- From: [EMAIL PROTECTED] [mailto:nobody;groupstudy.com]On Behalf Of Ken Diliberto Sent: Thursday, October 17, 2002 9:08 PM To: [EMAIL PROTECTED] Subject: RE: Native VLAN 1 [7:55743] Sensing how easy it would be for me to make the same mistake... Does this mean the supervisor will come up with an existing configuration before automatic synchronization takes place? Larry Letterman 10/17/02 09:02AM mad, You are correct, teh second sup is the redundant sup... the config for it is on itself. So when I replaced it the new one was set for vlan 1 and that caused the issue. Larry Letterman Network Engineer Cisco Systems Inc. -Original Message- From: [EMAIL PROTECTED] [mailto:nobody;groupstudy.com]On Behalf Of MADMAN Sent: Thursday, October 17, 2002 7:35 AM To: [EMAIL PROTECTED] Subject: Re: Native VLAN 1 [7:55743] Since the config for the line cards resides on the sup there should be no problem swapping out same line cards, if the native VLAN was changed, the change will be employed on the new card also. When you swapped out a standby sup in your example below I don't quite understand what hapened. The standby sup uplinks are active so what changed?? When you say you swapped out the sceondary sup the redundant sup came up, isn't the secondary sup the redundant sup?? The greater point is though I agrre with Larry, leave the native VLAN as 1, changing it is of no value as far as I can tell. Dave Larry Letterman wrote: I personally changed out a secondary sup card, when I was new in the lan team.. the redundant sup came up with with the trunk port 2/1 config'd for native vlan 1. this caused the vtp management to issue a vlan mismatch...which then started a stp recalc, which caused utilization on the gateway to go up trying to process the bpdu storm, which prevented the network from working correctly... leaving everything in native 1 prevents this Larry Letterman Network Engineer Cisco Systems Inc. -Original Message- From: [EMAIL PROTECTED] [mailto:nobody;groupstudy.com]On Behalf Of Erick B. Sent: Wednesday, October 16, 2002 11:53 PM To: [EMAIL PROTECTED] Subject: Re: Native VLAN 1 [7:55743] Comments inline... --- The Long and Winding Road wrote: Larry Letterman wrote in message news:200210170505.FAA27055;groupstudy.com... Pris, In our 6509's we used to make the native vlan and the data vlan the same and it was something other than 1...if a blade fails and we put in a new one , it defaults to vlan 1 for all ports. If the blade has trunk ports in it, they get set to native vlan 1. The other end is set for something else, this resulted in vlan mismatch in the vtp domain, and in a lot of instances we suffered stp recalcs that took buildings down for periods of time...we subsequently have returned to making native vlan 1 on all trunks and have not had any issues since.. I want to clarify a few items so we fully understand this behavior so next time I need to hot-swap I am prepared to make config changes as well. I thought the running config in RAM (and NVRAM) stayed the same when swapping *same model* blades in the same slot. If this isn't the case, then is some of the config the same and some is defaulted? Can you point us to a cisco doc explaining this behavior? Thank you very much! __ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos More http://faith.yahoo.com -- David Madland CCIE# 2016 Sr. Network Engineer Qwest Communications 612-664-3367 You don't make the poor richer by making the rich poorer. --Winston
Re: Native VLAN 1 [7:55743]
Comments inline... --- The Long and Winding Road wrote: Larry Letterman wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... Pris, In our 6509's we used to make the native vlan and the data vlan the same and it was something other than 1...if a blade fails and we put in a new one , it defaults to vlan 1 for all ports. If the blade has trunk ports in it, they get set to native vlan 1. The other end is set for something else, this resulted in vlan mismatch in the vtp domain, and in a lot of instances we suffered stp recalcs that took buildings down for periods of time...we subsequently have returned to making native vlan 1 on all trunks and have not had any issues since.. I want to clarify a few items so we fully understand this behavior so next time I need to hot-swap I am prepared to make config changes as well. I thought the running config in RAM (and NVRAM) stayed the same when swapping *same model* blades in the same slot. If this isn't the case, then is some of the config the same and some is defaulted? Can you point us to a cisco doc explaining this behavior? Thank you very much! __ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos More http://faith.yahoo.com Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=55782t=55743 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: Native VLAN 1 [7:55743]
we chose this route because we have new people from different groups that work oncall. Some of those individuals dont know all the tricks and stp issues. It was easier to use the default config and not have meltdowns due to some one installing a blade and causing a mismatch. Larry Letterman Network Engineer Cisco Systems Inc. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of The Long and Winding Road Sent: Wednesday, October 16, 2002 11:08 PM To: [EMAIL PROTECTED] Subject: Re: Native VLAN 1 [7:55743] Larry Letterman wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... Pris, In our 6509's we used to make the native vlan and the data vlan the same and it was something other than 1...if a blade fails and we put in a new one , it defaults to vlan 1 for all ports. If the blade has trunk ports in it, they get set to native vlan 1. The other end is set for something else, this resulted in vlan mismatch in the vtp domain, and in a lot of instances we suffered stp recalcs that took buildings down for periods of time...we subsequently have returned to making native vlan 1 on all trunks and have not had any issues since.. CL: idle curiousity. as an alternative, can't the replacement blades be preconfigured on another box, then moved to the box in question? this is not meant as a snide remark, or a negative criticism. I think what you are demonstrating is a well known phenomenon, where people back off / out of good ideas and good practice as a matter of expedience and convenience. (And yes, I have been known to have backed off requiring password changes every 30 days because I got tired of, every 30 days, going from user to user to help them log in using a new password.) Larry Letterman Network Engineer Cisco Systems Inc. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 16, 2002 3:49 PM To: [EMAIL PROTECTED] Subject: RE: Native VLAN 1 [7:55743] Larry Letterman wrote: vlan mismatches and major spanning tree recalcs.. Why? Thanks for any more detail you can give. Priscilla Larry Letterman Network Engineer Cisco Systems Inc. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Azhar Teza Sent: Wednesday, October 16, 2002 3:21 PM To: [EMAIL PROTECTED] Subject: Native VLAN 1 [7:55743] When Ports are configured as trunk in Catalyst switches, they still belong to VLAN 1 in native column eventhough the ports can span all VLANs. What's the drawback of changing the port from Native VLAN 1 to some other VLANs? Regards, Teza ___ Join Excite! - http://www.excite.com The most personalized portal on the Web! Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=55783t=55743 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: Native VLAN 1 [7:55743]
I personally changed out a secondary sup card, when I was new in the lan team.. the redundant sup came up with with the trunk port 2/1 config'd for native vlan 1. this caused the vtp management to issue a vlan mismatch...which then started a stp recalc, which caused utilization on the gateway to go up trying to process the bpdu storm, which prevented the network from working correctly... leaving everything in native 1 prevents this Larry Letterman Network Engineer Cisco Systems Inc. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Erick B. Sent: Wednesday, October 16, 2002 11:53 PM To: [EMAIL PROTECTED] Subject: Re: Native VLAN 1 [7:55743] Comments inline... --- The Long and Winding Road wrote: Larry Letterman wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... Pris, In our 6509's we used to make the native vlan and the data vlan the same and it was something other than 1...if a blade fails and we put in a new one , it defaults to vlan 1 for all ports. If the blade has trunk ports in it, they get set to native vlan 1. The other end is set for something else, this resulted in vlan mismatch in the vtp domain, and in a lot of instances we suffered stp recalcs that took buildings down for periods of time...we subsequently have returned to making native vlan 1 on all trunks and have not had any issues since.. I want to clarify a few items so we fully understand this behavior so next time I need to hot-swap I am prepared to make config changes as well. I thought the running config in RAM (and NVRAM) stayed the same when swapping *same model* blades in the same slot. If this isn't the case, then is some of the config the same and some is defaulted? Can you point us to a cisco doc explaining this behavior? Thank you very much! __ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos More http://faith.yahoo.com Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=55787t=55743 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: Native VLAN 1 [7:55743]
I disagree with that. If native vlan is changed on only one end of the link, you will get native vlan mismatch which can be bad. There are some cases when changing native vlans is needed by design. Case in point. A PC is plugged into an IP phone, the configuration of Cat 3524 is below: interface FastEthernet0/1 switchport trunk encapsulation dot1q switchport trunk native vlan 4 switchport mode trunk switchport voice vlan 12 spanning-tree portfast as you can see, the native vlan is changed. The PC will be on vlan 4, the IP phone will be on VL 12. A native vlan is merely a vlan that the port will belong to when in access mode. With 802.1q frames belonging to native vlan are sent non-encapuslated. Hope it helps -Original Message- From: [EMAIL PROTECTED] [mailto:nobody;groupstudy.com] Sent: Wednesday, October 16, 2002 6:49 PM To: [EMAIL PROTECTED] Subject: RE: Native VLAN 1 [7:55743] Larry Letterman wrote: vlan mismatches and major spanning tree recalcs.. Why? Thanks for any more detail you can give. Priscilla Larry Letterman Network Engineer Cisco Systems Inc. -Original Message- From: [EMAIL PROTECTED] [mailto:nobody;groupstudy.com]On Behalf Of Azhar Teza Sent: Wednesday, October 16, 2002 3:21 PM To: [EMAIL PROTECTED] Subject: Native VLAN 1 [7:55743] When Ports are configured as trunk in Catalyst switches, they still belong to VLAN 1 in native column eventhough the ports can span all VLANs. What's the drawback of changing the port from Native VLAN 1 to some other VLANs? Regards, Teza ___ Join Excite! - http://www.excite.com The most personalized portal on the Web! Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=55792t=55743 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: Native VLAN 1 [7:55743]
Since the config for the line cards resides on the sup there should be no problem swapping out same line cards, if the native VLAN was changed, the change will be employed on the new card also. When you swapped out a standby sup in your example below I don't quite understand what hapened. The standby sup uplinks are active so what changed?? When you say you swapped out the sceondary sup the redundant sup came up, isn't the secondary sup the redundant sup?? The greater point is though I agrre with Larry, leave the native VLAN as 1, changing it is of no value as far as I can tell. Dave Larry Letterman wrote: I personally changed out a secondary sup card, when I was new in the lan team.. the redundant sup came up with with the trunk port 2/1 config'd for native vlan 1. this caused the vtp management to issue a vlan mismatch...which then started a stp recalc, which caused utilization on the gateway to go up trying to process the bpdu storm, which prevented the network from working correctly... leaving everything in native 1 prevents this Larry Letterman Network Engineer Cisco Systems Inc. -Original Message- From: [EMAIL PROTECTED] [mailto:nobody;groupstudy.com]On Behalf Of Erick B. Sent: Wednesday, October 16, 2002 11:53 PM To: [EMAIL PROTECTED] Subject: Re: Native VLAN 1 [7:55743] Comments inline... --- The Long and Winding Road wrote: Larry Letterman wrote in message news:200210170505.FAA27055;groupstudy.com... Pris, In our 6509's we used to make the native vlan and the data vlan the same and it was something other than 1...if a blade fails and we put in a new one , it defaults to vlan 1 for all ports. If the blade has trunk ports in it, they get set to native vlan 1. The other end is set for something else, this resulted in vlan mismatch in the vtp domain, and in a lot of instances we suffered stp recalcs that took buildings down for periods of time...we subsequently have returned to making native vlan 1 on all trunks and have not had any issues since.. I want to clarify a few items so we fully understand this behavior so next time I need to hot-swap I am prepared to make config changes as well. I thought the running config in RAM (and NVRAM) stayed the same when swapping *same model* blades in the same slot. If this isn't the case, then is some of the config the same and some is defaulted? Can you point us to a cisco doc explaining this behavior? Thank you very much! __ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos More http://faith.yahoo.com -- David Madland CCIE# 2016 Sr. Network Engineer Qwest Communications 612-664-3367 You don't make the poor richer by making the rich poorer. --Winston Churchill Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=55808t=55743 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: Native VLAN 1 [7:55743]
Larry Letterman wrote in message news:200210170727.HAA2;groupstudy.com... I personally changed out a secondary sup card, when I was new in the lan team.. the redundant sup came up with with the trunk port 2/1 config'd for native vlan 1. this caused the vtp management to issue a vlan mismatch...which then started a stp recalc, which caused utilization on the gateway to go up trying to process the bpdu storm, which prevented the network from working correctly... CL: let he who has never brought a network to its knees cast the first stone :- leaving everything in native 1 prevents this Larry Letterman Network Engineer Cisco Systems Inc. -Original Message- From: [EMAIL PROTECTED] [mailto:nobody;groupstudy.com]On Behalf Of Erick B. Sent: Wednesday, October 16, 2002 11:53 PM To: [EMAIL PROTECTED] Subject: Re: Native VLAN 1 [7:55743] Comments inline... --- The Long and Winding Road wrote: Larry Letterman wrote in message news:200210170505.FAA27055;groupstudy.com... Pris, In our 6509's we used to make the native vlan and the data vlan the same and it was something other than 1...if a blade fails and we put in a new one , it defaults to vlan 1 for all ports. If the blade has trunk ports in it, they get set to native vlan 1. The other end is set for something else, this resulted in vlan mismatch in the vtp domain, and in a lot of instances we suffered stp recalcs that took buildings down for periods of time...we subsequently have returned to making native vlan 1 on all trunks and have not had any issues since.. I want to clarify a few items so we fully understand this behavior so next time I need to hot-swap I am prepared to make config changes as well. I thought the running config in RAM (and NVRAM) stayed the same when swapping *same model* blades in the same slot. If this isn't the case, then is some of the config the same and some is defaulted? Can you point us to a cisco doc explaining this behavior? Thank you very much! __ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos More http://faith.yahoo.com Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=55809t=55743 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: Native VLAN 1 [7:55743]
mad, You are correct, teh second sup is the redundant sup... the config for it is on itself. So when I replaced it the new one was set for vlan 1 and that caused the issue. Larry Letterman Network Engineer Cisco Systems Inc. -Original Message- From: [EMAIL PROTECTED] [mailto:nobody;groupstudy.com]On Behalf Of MADMAN Sent: Thursday, October 17, 2002 7:35 AM To: [EMAIL PROTECTED] Subject: Re: Native VLAN 1 [7:55743] Since the config for the line cards resides on the sup there should be no problem swapping out same line cards, if the native VLAN was changed, the change will be employed on the new card also. When you swapped out a standby sup in your example below I don't quite understand what hapened. The standby sup uplinks are active so what changed?? When you say you swapped out the sceondary sup the redundant sup came up, isn't the secondary sup the redundant sup?? The greater point is though I agrre with Larry, leave the native VLAN as 1, changing it is of no value as far as I can tell. Dave Larry Letterman wrote: I personally changed out a secondary sup card, when I was new in the lan team.. the redundant sup came up with with the trunk port 2/1 config'd for native vlan 1. this caused the vtp management to issue a vlan mismatch...which then started a stp recalc, which caused utilization on the gateway to go up trying to process the bpdu storm, which prevented the network from working correctly... leaving everything in native 1 prevents this Larry Letterman Network Engineer Cisco Systems Inc. -Original Message- From: [EMAIL PROTECTED] [mailto:nobody;groupstudy.com]On Behalf Of Erick B. Sent: Wednesday, October 16, 2002 11:53 PM To: [EMAIL PROTECTED] Subject: Re: Native VLAN 1 [7:55743] Comments inline... --- The Long and Winding Road wrote: Larry Letterman wrote in message news:200210170505.FAA27055;groupstudy.com... Pris, In our 6509's we used to make the native vlan and the data vlan the same and it was something other than 1...if a blade fails and we put in a new one , it defaults to vlan 1 for all ports. If the blade has trunk ports in it, they get set to native vlan 1. The other end is set for something else, this resulted in vlan mismatch in the vtp domain, and in a lot of instances we suffered stp recalcs that took buildings down for periods of time...we subsequently have returned to making native vlan 1 on all trunks and have not had any issues since.. I want to clarify a few items so we fully understand this behavior so next time I need to hot-swap I am prepared to make config changes as well. I thought the running config in RAM (and NVRAM) stayed the same when swapping *same model* blades in the same slot. If this isn't the case, then is some of the config the same and some is defaulted? Can you point us to a cisco doc explaining this behavior? Thank you very much! __ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos More http://faith.yahoo.com -- David Madland CCIE# 2016 Sr. Network Engineer Qwest Communications 612-664-3367 You don't make the poor richer by making the rich poorer. --Winston Churchill Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=55816t=55743 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: Native VLAN 1 [7:55743]
Thanks Larry and the others who responded. It's good to know about this potential problem. I hope you didn't mind me getting you embroiled in a discussion. ;-) I figured it would be good for learning, as it was. Priscilla Larry Letterman wrote: mad, You are correct, teh second sup is the redundant sup... the config for it is on itself. So when I replaced it the new one was set for vlan 1 and that caused the issue. Larry Letterman Network Engineer Cisco Systems Inc. -Original Message- From: [EMAIL PROTECTED] [mailto:nobody;groupstudy.com]On Behalf Of MADMAN Sent: Thursday, October 17, 2002 7:35 AM To: [EMAIL PROTECTED] Subject: Re: Native VLAN 1 [7:55743] Since the config for the line cards resides on the sup there should be no problem swapping out same line cards, if the native VLAN was changed, the change will be employed on the new card also. When you swapped out a standby sup in your example below I don't quite understand what hapened. The standby sup uplinks are active so what changed?? When you say you swapped out the sceondary sup the redundant sup came up, isn't the secondary sup the redundant sup?? The greater point is though I agrre with Larry, leave the native VLAN as 1, changing it is of no value as far as I can tell. Dave Larry Letterman wrote: I personally changed out a secondary sup card, when I was new in the lan team.. the redundant sup came up with with the trunk port 2/1 config'd for native vlan 1. this caused the vtp management to issue a vlan mismatch...which then started a stp recalc, which caused utilization on the gateway to go up trying to process the bpdu storm, which prevented the network from working correctly... leaving everything in native 1 prevents this Larry Letterman Network Engineer Cisco Systems Inc. -Original Message- From: [EMAIL PROTECTED] [mailto:nobody;groupstudy.com]On Behalf Of Erick B. Sent: Wednesday, October 16, 2002 11:53 PM To: [EMAIL PROTECTED] Subject: Re: Native VLAN 1 [7:55743] Comments inline... --- The Long and Winding Road wrote: Larry Letterman wrote in message news:200210170505.FAA27055;groupstudy.com... Pris, In our 6509's we used to make the native vlan and the data vlan the same and it was something other than 1...if a blade fails and we put in a new one , it defaults to vlan 1 for all ports. If the blade has trunk ports in it, they get set to native vlan 1. The other end is set for something else, this resulted in vlan mismatch in the vtp domain, and in a lot of instances we suffered stp recalcs that took buildings down for periods of time...we subsequently have returned to making native vlan 1 on all trunks and have not had any issues since.. I want to clarify a few items so we fully understand this behavior so next time I need to hot-swap I am prepared to make config changes as well. I thought the running config in RAM (and NVRAM) stayed the same when swapping *same model* blades in the same slot. If this isn't the case, then is some of the config the same and some is defaulted? Can you point us to a cisco doc explaining this behavior? Thank you very much! __ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos More http://faith.yahoo.com -- David Madland CCIE# 2016 Sr. Network Engineer Qwest Communications 612-664-3367 You don't make the poor richer by making the rich poorer. --Winston Churchill Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=55826t=55743 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: Native VLAN 1 [7:55743]
Sensing how easy it would be for me to make the same mistake... Does this mean the supervisor will come up with an existing configuration before automatic synchronization takes place? Larry Letterman 10/17/02 09:02AM mad, You are correct, teh second sup is the redundant sup... the config for it is on itself. So when I replaced it the new one was set for vlan 1 and that caused the issue. Larry Letterman Network Engineer Cisco Systems Inc. -Original Message- From: [EMAIL PROTECTED] [mailto:nobody;groupstudy.com]On Behalf Of MADMAN Sent: Thursday, October 17, 2002 7:35 AM To: [EMAIL PROTECTED] Subject: Re: Native VLAN 1 [7:55743] Since the config for the line cards resides on the sup there should be no problem swapping out same line cards, if the native VLAN was changed, the change will be employed on the new card also. When you swapped out a standby sup in your example below I don't quite understand what hapened. The standby sup uplinks are active so what changed?? When you say you swapped out the sceondary sup the redundant sup came up, isn't the secondary sup the redundant sup?? The greater point is though I agrre with Larry, leave the native VLAN as 1, changing it is of no value as far as I can tell. Dave Larry Letterman wrote: I personally changed out a secondary sup card, when I was new in the lan team.. the redundant sup came up with with the trunk port 2/1 config'd for native vlan 1. this caused the vtp management to issue a vlan mismatch...which then started a stp recalc, which caused utilization on the gateway to go up trying to process the bpdu storm, which prevented the network from working correctly... leaving everything in native 1 prevents this Larry Letterman Network Engineer Cisco Systems Inc. -Original Message- From: [EMAIL PROTECTED] [mailto:nobody;groupstudy.com]On Behalf Of Erick B. Sent: Wednesday, October 16, 2002 11:53 PM To: [EMAIL PROTECTED] Subject: Re: Native VLAN 1 [7:55743] Comments inline... --- The Long and Winding Road wrote: Larry Letterman wrote in message news:200210170505.FAA27055;groupstudy.com... Pris, In our 6509's we used to make the native vlan and the data vlan the same and it was something other than 1...if a blade fails and we put in a new one , it defaults to vlan 1 for all ports. If the blade has trunk ports in it, they get set to native vlan 1. The other end is set for something else, this resulted in vlan mismatch in the vtp domain, and in a lot of instances we suffered stp recalcs that took buildings down for periods of time...we subsequently have returned to making native vlan 1 on all trunks and have not had any issues since.. I want to clarify a few items so we fully understand this behavior so next time I need to hot-swap I am prepared to make config changes as well. I thought the running config in RAM (and NVRAM) stayed the same when swapping *same model* blades in the same slot. If this isn't the case, then is some of the config the same and some is defaulted? Can you point us to a cisco doc explaining this behavior? Thank you very much! __ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos More http://faith.yahoo.com -- David Madland CCIE# 2016 Sr. Network Engineer Qwest Communications 612-664-3367 You don't make the poor richer by making the rich poorer. --Winston Churchill Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=55854t=55743 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Native VLAN 1 [7:55743]
When Ports are configured as trunk in Catalyst switches, they still belong to VLAN 1 in native column eventhough the ports can span all VLANs. What's the drawback of changing the port from Native VLAN 1 to some other VLANs? Regards, Teza ___ Join Excite! - http://www.excite.com The most personalized portal on the Web! Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=55743t=55743 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: Native VLAN 1 [7:55743]
vlan mismatches and major spanning tree recalcs.. Larry Letterman Network Engineer Cisco Systems Inc. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Azhar Teza Sent: Wednesday, October 16, 2002 3:21 PM To: [EMAIL PROTECTED] Subject: Native VLAN 1 [7:55743] When Ports are configured as trunk in Catalyst switches, they still belong to VLAN 1 in native column eventhough the ports can span all VLANs. What's the drawback of changing the port from Native VLAN 1 to some other VLANs? Regards, Teza ___ Join Excite! - http://www.excite.com The most personalized portal on the Web! Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=55744t=55743 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: Native VLAN 1 [7:55743]
Larry Letterman wrote: vlan mismatches and major spanning tree recalcs.. Why? Thanks for any more detail you can give. Priscilla Larry Letterman Network Engineer Cisco Systems Inc. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Azhar Teza Sent: Wednesday, October 16, 2002 3:21 PM To: [EMAIL PROTECTED] Subject: Native VLAN 1 [7:55743] When Ports are configured as trunk in Catalyst switches, they still belong to VLAN 1 in native column eventhough the ports can span all VLANs. What's the drawback of changing the port from Native VLAN 1 to some other VLANs? Regards, Teza ___ Join Excite! - http://www.excite.com The most personalized portal on the Web! Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=55746t=55743 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: Native VLAN 1 [7:55743]
Pris, In our 6509's we used to make the native vlan and the data vlan the same and it was something other than 1...if a blade fails and we put in a new one , it defaults to vlan 1 for all ports. If the blade has trunk ports in it, they get set to native vlan 1. The other end is set for something else, this resulted in vlan mismatch in the vtp domain, and in a lot of instances we suffered stp recalcs that took buildings down for periods of time...we subsequently have returned to making native vlan 1 on all trunks and have not had any issues since.. Larry Letterman Network Engineer Cisco Systems Inc. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 16, 2002 3:49 PM To: [EMAIL PROTECTED] Subject: RE: Native VLAN 1 [7:55743] Larry Letterman wrote: vlan mismatches and major spanning tree recalcs.. Why? Thanks for any more detail you can give. Priscilla Larry Letterman Network Engineer Cisco Systems Inc. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Azhar Teza Sent: Wednesday, October 16, 2002 3:21 PM To: [EMAIL PROTECTED] Subject: Native VLAN 1 [7:55743] When Ports are configured as trunk in Catalyst switches, they still belong to VLAN 1 in native column eventhough the ports can span all VLANs. What's the drawback of changing the port from Native VLAN 1 to some other VLANs? Regards, Teza ___ Join Excite! - http://www.excite.com The most personalized portal on the Web! Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=55774t=55743 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: Native VLAN 1 [7:55743]
Larry Letterman wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... Pris, In our 6509's we used to make the native vlan and the data vlan the same and it was something other than 1...if a blade fails and we put in a new one , it defaults to vlan 1 for all ports. If the blade has trunk ports in it, they get set to native vlan 1. The other end is set for something else, this resulted in vlan mismatch in the vtp domain, and in a lot of instances we suffered stp recalcs that took buildings down for periods of time...we subsequently have returned to making native vlan 1 on all trunks and have not had any issues since.. CL: idle curiousity. as an alternative, can't the replacement blades be preconfigured on another box, then moved to the box in question? this is not meant as a snide remark, or a negative criticism. I think what you are demonstrating is a well known phenomenon, where people back off / out of good ideas and good practice as a matter of expedience and convenience. (And yes, I have been known to have backed off requiring password changes every 30 days because I got tired of, every 30 days, going from user to user to help them log in using a new password.) Larry Letterman Network Engineer Cisco Systems Inc. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 16, 2002 3:49 PM To: [EMAIL PROTECTED] Subject: RE: Native VLAN 1 [7:55743] Larry Letterman wrote: vlan mismatches and major spanning tree recalcs.. Why? Thanks for any more detail you can give. Priscilla Larry Letterman Network Engineer Cisco Systems Inc. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Azhar Teza Sent: Wednesday, October 16, 2002 3:21 PM To: [EMAIL PROTECTED] Subject: Native VLAN 1 [7:55743] When Ports are configured as trunk in Catalyst switches, they still belong to VLAN 1 in native column eventhough the ports can span all VLANs. What's the drawback of changing the port from Native VLAN 1 to some other VLANs? Regards, Teza ___ Join Excite! - http://www.excite.com The most personalized portal on the Web! Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=55776t=55743 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
