----- Original Message -----
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 <vtp_domain_name>
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]
