RE: More on VLANs
This URL explains it all http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/sw_5_4/msfc/mls. htm#xtocid244531 Patrick -Original Message- From: Ben Hockenhull [mailto:[EMAIL PROTECTED]] Sent: Monday, December 04, 2000 11:22 PM To: Greene, Patrick Cc: [EMAIL PROTECTED] Subject: RE: More on VLANs At 5:22 PM -0500 12/4/00, Greene, Patrick wrote: > > >You need to enable routing for that VLAN interface with the mls command. > > >Example >interface vlan 200 >ip address 10.1.1.1 255.255.255.0 >mls rp vtp-domain >mls rp ip Hmmm. According to the docs, MLS is enabled by default on the MSFC. I did enable mls rp ip on the interface and it had no effect. I was unable to config mls rp vtp-domain as the MSFC muttered something about a null domain. Ben -- Ben Hockenhull [EMAIL PROTECTED] "Revenge is a dish best served with pinto beans and muffins." _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: More on VLANs
Here is the VTP configuration URL http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/sw_5_4/config/vt p.htm#32923 Good luck Here is a good MLS Troubleshooting URL too which may be helpful http://www.cisco.com/warp/public/473/13.html Patrick -Original Message- From: Ben Hockenhull [mailto:[EMAIL PROTECTED]] Sent: Friday, December 08, 2000 2:31 PM To: Greene, Patrick Subject: RE: More on VLANs That would be great! -- Ben Hockenhull [EMAIL PROTECTED] On Fri, 8 Dec 2000, Greene, Patrick wrote: > There's a lot more to this than just typing what I tell you in examples. > Your VTP configuration must be setup on the switch side and the MSFC side. > And yes MLS is enabled at the global level but not at the interface level. > > Would you like the URL's to VTP Configuration too? > > Patrick > > -Original Message- > From: Ben Hockenhull [mailto:[EMAIL PROTECTED]] > Sent: Monday, December 04, 2000 11:22 PM > To: Greene, Patrick > Cc: [EMAIL PROTECTED] > Subject: RE: More on VLANs > > > At 5:22 PM -0500 12/4/00, Greene, Patrick wrote: > > > > > >You need to enable routing for that VLAN interface with the mls command. > > > > > >Example > >interface vlan 200 > >ip address 10.1.1.1 255.255.255.0 > >mls rp vtp-domain > >mls rp ip > > Hmmm. According to the docs, MLS is enabled by default on the MSFC. I did > enable mls rp ip on the interface and it had no effect. I was unable to > config mls rp vtp-domain as the MSFC muttered something about a null domain. > > Ben > > > -- > Ben Hockenhull > [EMAIL PROTECTED] > "Revenge is a dish best served with pinto beans and muffins." > > > _ > FAQ, list archives, and subscription info: > http://www.groupstudy.com/list/cisco.html > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] > > _ > FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] > _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: More on VLANs
There's a lot more to this than just typing what I tell you in examples. Your VTP configuration must be setup on the switch side and the MSFC side. And yes MLS is enabled at the global level but not at the interface level. Would you like the URL's to VTP Configuration too? Patrick -Original Message- From: Ben Hockenhull [mailto:[EMAIL PROTECTED]] Sent: Monday, December 04, 2000 11:22 PM To: Greene, Patrick Cc: [EMAIL PROTECTED] Subject: RE: More on VLANs At 5:22 PM -0500 12/4/00, Greene, Patrick wrote: > > >You need to enable routing for that VLAN interface with the mls command. > > >Example >interface vlan 200 >ip address 10.1.1.1 255.255.255.0 >mls rp vtp-domain >mls rp ip Hmmm. According to the docs, MLS is enabled by default on the MSFC. I did enable mls rp ip on the interface and it had no effect. I was unable to config mls rp vtp-domain as the MSFC muttered something about a null domain. Ben -- Ben Hockenhull [EMAIL PROTECTED] "Revenge is a dish best served with pinto beans and muffins." _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: More on VLANs
At 5:22 PM -0500 12/4/00, Greene, Patrick wrote: > > >You need to enable routing for that VLAN interface with the mls command. > > >Example >interface vlan 200 >ip address 10.1.1.1 255.255.255.0 >mls rp vtp-domain >mls rp ip Hmmm. According to the docs, MLS is enabled by default on the MSFC. I did enable mls rp ip on the interface and it had no effect. I was unable to config mls rp vtp-domain as the MSFC muttered something about a null domain. Ben -- Ben Hockenhull [EMAIL PROTECTED] "Revenge is a dish best served with pinto beans and muffins." _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: More on VLANs
Title: RE: More on VLANs Greene, MLS routing is enabled by default on the 6500 ! The commands you are syggesting is used only if you have an external router , that it will do the MLS (such a 7200 with a 5500 ) ! Ben, If you have enable the Intrface Vlan 200 on the MSFC and assign an IP address on this Interface you should ping your Host on Vlan 200 ! Can you send your config ? ELIASCCNP + VOICE - Original Message - From: Greene, Patrick To: 'Ben Hockenhull' ; [EMAIL PROTECTED] Sent: Tuesday, December 05, 2000 12:22 AM Subject: RE: More on VLANs You need to enable routing for that VLAN interface with the mls command. Example interface vlan 200 ip address 10.1.1.1 255.255.255.0 mls rp vtp-domain mls rp ip Patrick Greene -Original Message- From: Ben Hockenhull [mailto:[EMAIL PROTECTED]] Sent: Monday, December 04, 2000 2:22 PM To: [EMAIL PROTECTED] Subject: More on VLANs Now that I have the native vlan and trunking issue resolved, I'm turning my attention to another problem. I have a host that will reside on a vlan all by itself. I've created the vlan (vlan 200) and configured a fast ethernet port to be a member of that vlan, and attached the host to it. The port is up, and I can ping the host on that vlan from the switch management interface, once I set the management interface to an IP in that vlan, and set the vlan membership of the management port appropriately. However, I am unable to ping the host from inside the MSFC. I've configured a vlan200 interface, assigned it an IP and brought the interface up, but I can't reach the host. Vlan200 is allowed on the ISL trunk to the MSFC. I suspect that this is because I misunderstand something fundamental about how vlans work on the Cat 6500. I further suspect that this is related to the native vlan problem I was having before. If I change the vlan on the host port to the native vlan, and change the vlan interface on the MSFC to the native vlan, I can ping from the MSFC. Therefore, I think that frames from vlan200 are not being forwarded to the MSFC for some reason. The documentation I've read doesn't seem to touch on this too much. Ben -- Ben Hockenhull [EMAIL PROTECTED] _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: More on VLANs
Title: RE: More on VLANs You need to enable routing for that VLAN interface with the mls command. Example interface vlan 200 ip address 10.1.1.1 255.255.255.0 mls rp vtp-domain mls rp ip Patrick Greene -Original Message- From: Ben Hockenhull [mailto:[EMAIL PROTECTED]] Sent: Monday, December 04, 2000 2:22 PM To: [EMAIL PROTECTED] Subject: More on VLANs Now that I have the native vlan and trunking issue resolved, I'm turning my attention to another problem. I have a host that will reside on a vlan all by itself. I've created the vlan (vlan 200) and configured a fast ethernet port to be a member of that vlan, and attached the host to it. The port is up, and I can ping the host on that vlan from the switch management interface, once I set the management interface to an IP in that vlan, and set the vlan membership of the management port appropriately. However, I am unable to ping the host from inside the MSFC. I've configured a vlan200 interface, assigned it an IP and brought the interface up, but I can't reach the host. Vlan200 is allowed on the ISL trunk to the MSFC. I suspect that this is because I misunderstand something fundamental about how vlans work on the Cat 6500. I further suspect that this is related to the native vlan problem I was having before. If I change the vlan on the host port to the native vlan, and change the vlan interface on the MSFC to the native vlan, I can ping from the MSFC. Therefore, I think that frames from vlan200 are not being forwarded to the MSFC for some reason. The documentation I've read doesn't seem to touch on this too much. Ben -- Ben Hockenhull [EMAIL PROTECTED] _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
