The device connected to the 1Q trunk must be a trunk
connection. The host on the other end of the trunk link
will not usually respond to your ping when the link is a
trunk. If you want the host to respond you need the link
to be a switchport access type link.
Larry Letterman
Cisco Systems
[EMAIL
Sent: 2/17/02 11:52 PM
Subject: RE: Different type of intervlan routing problem... [7:35595]
The device connected to the 1Q trunk must be a trunk
connection. The host on the other end of the trunk link
will not usually respond to your ping when the link is a
trunk. If you want the host to respond yo
If it helps, think of the host ("Switch" X) as L3 switch on the other end of
the dot1q trunk. Switch Z is a L3 switch (Extreme 48port).
Router A Switch Y --- Switch Z
10.6.200.1 802.1q 10.6.200.3 802.1q 10.6.200.2
|
E: Different type of intervlan routing problem... [7:35595]
If it helps, think of the host ("Switch" X) as L3 switch on the other end of
the dot1q trunk. Switch Z is a L3 switch (Extreme 48port).
Router A Switch Y --- Switch Z
10.6.200.1 802.1q 10.6.
PM
To: '[EMAIL PROTECTED]'
Cc: '[EMAIL PROTECTED]'
Subject: RE: Different type of intervlan routing problem... [7:35595]
If it helps, think of the host ("Switch" X) as L3 switch on the other end of
the dot1q trunk. Switch Z is a L3 switch (Extreme 48port).
A problem I have come across on the 3500XL switches and dot1q trunking is
when the XL switch expected the packets on the native VLAN to be untagged
and the device on the other end of the trunk expects the packets to be
tagged. This prevents communication through the trunk on the native VLAN.
The
:31 PM
To: [EMAIL PROTECTED]
Subject: Re: Different type of intervlan routing problem... [7:35595]
A problem I have come across on the 3500XL switches and dot1q trunking is
when the XL switch expected the packets on the native VLAN to be untagged
and the device on the other end of the trunk expects
7 matches
Mail list logo
