From: Rajagopal S (raj_ccie@yahoo.com)
Date: Mon Aug 11 2003 - 10:48:30 GMT-3
Hi Micheal,
Yes.. I have tested.. the child switch can ping the VLAN's configured on the core switch without IP routing enabled..
The child switch need not be layer 3 enabled. It knows the VLAN IP from the core switch through the trunks configured.
DC_3550#ping
Protocol [ip]:
Target IP address: 172.16.20.4 (VLAN 200 on the core switch which is routing enabled)
Repeat count [5]:
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]: y
Source address or interface: 5.5.5.5 (VLAN 800 on this child switch)
Type of service [0]:
Set DF bit in IP header? [no]:
Validate reply data? [no]:
Data pattern [0xABCD]:
Loose, Strict, Record, Timestamp, Verbose[none]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.20.4, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms
IP routing table:
DC_3550#sh ip route
Default gateway is not set
Host Gateway Last Use Total Uses Interface
ICMP redirect cache is empty
Ip routing has been disabled on this switch and no layer 3 information available.
Cheers
Raj
Michael Popovich <michael625@cox.net> wrote:
Have you tested this??
In my experience Brian is right. Without ip routing enabled there is no
connected routes showing in the switch so it is just plainly a L2
switch. In which case you will NOT get packets to cross vlan boundaries.
MP
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Rajagopal S
Sent: Saturday, August 09, 2003 5:49 AM
To: Brian Dennis; 'Larry Letterman'; 'Peng Zheng';
ccielab@groupstudy.com
Subject: RE: Cat 3550
HI all,
The basic IP addresses for all vlan's should be configured on th VTP
server and the L2 fiber/copper links should be trunked between these
switches.
In this case, IP routing need not be enabled on the child switches, as
it carries only L2 information to the VTP server. The VTP server will
know to put the traffic on L3 to the child switches.
In this case, we need not enable "ip routing" on the vtp client switch
and routing will happen with the directly connected routes on both the
switches.
Hope this clarifies !!
Raj
Brian Dennis wrote:
3. Configure cat1 and cat2 such that hosts on vlan 19,
20, 21 can communicate to each other.
Solution: enable "ip routing".
When you enable "ip routing" on the switches they will have connected
routes in their routing table for the subnets configured on the VLAN
interfaces. Without "ip routing" the switches will not forward (aka
route) packets between VLAN interface.
Brian Dennis, CCIE #2210 (R&S/ISP-Dial/Security)
bdennis@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Larry Letterman
Sent: Saturday, August 09, 2003 2:08 AM
To: 'Brian Dennis'; 'Peng Zheng'; ccielab@groupstudy.com
Subject: RE: Cat 3550
I don't see any where in that email about connected routes or a
connection to a router..
One can assume that a router connection is there..if it is not then
routing will need to
Be enabled on the 3550's....
Larry Letterman
Cisco Systems
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Brian Dennis
Sent: Saturday, August 09, 2003 1:59 AM
To: 'Peng Zheng'; ccielab@groupstudy.com
Subject: RE: Cat 3550
Since both switches will have connected routes to the 3 VLANs, what will
a routing protocol advertise that the switches don't already know about?
Just enable "ip routing" on the switches for the third task to allow the
switches to forward packets between the VLAN interfaces. Also make sure
that the VLANs are trunked. Technically you could have three interfaces
between the switches each in one of the VLANs as opposed to trunking the
VLANs ;-)
Brian Dennis, CCIE #2210 (R&S/ISP-Dial/Security)
bdennis@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Peng Zheng
Sent: Friday, August 08, 2003 7:04 PM
To: ccielab@groupstudy.com
Subject: Cat 3550
1. Config cat1 vlan 19 with IP 10.10.19.8/24, Vlan 20
with IP 10.10.20.8/24 and Vlan 21 with IP
10.10.21.8/24.
2. Config cat2 vlan 19 with IP 10.10.19.9/24, Vlan 20
with IP 10.10.20.9/24 and Vlan 21 with IP
10.10.21.9/24.
3. Configure cat1 and cat2 such that hosts on vlan 19,
20, 21 can communicate to each other.
It's easy for the first two. For the third one, I
think I must configure routing protocol on these
Vlans.
But I can not find related configs in the solution.
Below are configs related to routing and these Vlans:
------------------------------------------
interface FastEthernet0/19
switchport access vlan 19
no ip address
spanning-tree portfast
!
interface FastEthernet0/20
switchport access vlan 20
no ip address
spanning-tree portfast
!
interface FastEthernet0/21
switchport access vlan 21
no ip address
spanning-tree portfast
!
interface FastEthernet0/22
switchport trunk encapsulation isl
switchport trunk allowed vlan 1,2,15,19-21,1001-4094
switchport mode trunk
no ip address
spanning-tree vlan 19 cost 4
!
interface FastEthernet0/23
switchport trunk encapsulation isl
switchport trunk allowed vlan 1,2,15,19-21,1001-4094
switchport mode trunk
no ip address
spanning-tree vlan 20 cost 4
!
interface FastEthernet0/24
switchport trunk encapsulation isl
switchport trunk allowed vlan 1,2,15,19-21,1001-4094
switchport mode trunk
no ip address
spanning-tree vlan 21 cost 4
!
interface GigabitEthernet0/1
no switchport
ip address 10.10.89.8 255.255.255.0
!
interface GigabitEthernet0/2
no ip address
!
interface Vlan1
no ip address
shutdown
!
interface Vlan15
ip address 150.50.15.8 255.255.255.0
ip ospf authentication message-digest
ip ospf message-digest-key 1 md5 hello
!
interface Vlan19
ip address 10.10.19.8 255.255.255.0
no ip redirects
standby timers 5 15
standby 1 ip 10.10.19.100
standby 1 priority 200
standby 1 preempt
standby 2 ip 10.10.19.200
standby 2 timers 5 15
standby 2 priority 100
!
interface Vlan20
ip address 10.10.20.8 255.255.255.0
no ip redirects
standby timers 5 15
standby 1 ip 10.10.20.100
standby 1 priority 200
standby 1 preempt
standby 2 ip 10.10.20.200
standby 2 timers 5 15
standby 2 priority 100
!
interface Vlan21
ip address 10.10.21.8 255.255.255.0
no ip redirects
standby 1 ip 10.10.21.100
standby 1 timers 5 15
standby 1 priority 200
standby 1 preempt
standby 2 ip 10.10.21.200
standby 2 timers 5 15
standby 2 priority 100
!
router ospf 100
log-adjacency-changes
network 150.50.15.0 0.0.0.255 area 0
!
-------------------------------------------------
I don't know how these vlans communicate to each
other.
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
This archive was generated by hypermail 2.1.4 : Tue Sep 02 2003 - 18:53:57 GMT-3