cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1010
Views
5
Helpful
4
Replies

Can we have a trunk link between c3662 & c2950 on 10Mbps /Half Duplex ??

dbshah2000
Level 1
Level 1

Can i have a trunk link with 802.1q encapsulation between c3662 & c2950 on 10Mbps /Half Duplex ??

The reson for 10Mb/Half Duplex is we have a couple of devices ( Bay networks AN routers) whihc talk on ehternet to cisco routers on the same ethernet segment.

At the moment the cisco router is connected to the switch on 100/half & the bay router is connected to the same switch on 10/half.

Thus with this setup, both the routers can ping the switch Management IP, but not each other.

We have no ACLs on the ethernet interface of the BAY Router or on the cisco router.

Both the routers are on SAME ethenet VLAN.

When we ping the other router, we see no ARP as well.

What we feel is this could eb a full duplex/speed issue on cisco and Bay.

But at the same time we cannot change the settings on both the routers to 100/full due to limitations of legacy devices being connected to them.

Any help to this regard will be greatly appreciated

1 Accepted Solution

Accepted Solutions

Roberto Salazar
Level 8
Level 8

dbshah2000:Can i have a trunk link with 802.1q encapsulation between c3662 & c2950 on 10Mbps /Half Duplex ??

>> Yes, you can given you have the right IOS:

802.1Q encapsulation is now available on the built-in 10BaseT Ethernet interfaces of the Cisco 2610, 2611, and 2612 with Cisco IOS software 12.2(2)T and subsequent releases. Although this feature has been available on the Cisco 2600/3600 series since the release of Cisco IOS 12.1(5)T, support was previously limited to Fast Ethernet interfaces only. 802.1Q is not supported on any other Cisco 2600/3600 series 10BaseT Ethernet interface.

http://www.cisco.com/en/US/partner/products/hw/routers/ps259/prod_bulletin09186a00800921e4.html

is the cisco the router currently doing trunking to the 2950? How is it configured? Is the Bay trunking to the 2950 as well? Can you ping from one router to the other router if the connections to the 2950 are not trunking?

View solution in original post

4 Replies 4

arvindchari
Level 3
Level 3

When you do a ping from the cisco router, does the cam table on the switch get populated correctly and does the arp request get forwarded to the appropriate port(s) ?

U could use SPAN to check if frames are being broadcast currently.

nethelper
Level 3
Level 3

Hello,

is the Bay router connected to the 2950 through a trunk link as well ? How is the trunk configured on your 3662 router ?

If all devices are in VLAN 1, try either of the following configurations on your 3662:

interface FastEthernet0/0

ip address 192.168.1.1 255.255.255.0

duplex auto

speed auto

or

interface FastEthernet0/0

no ip address

duplex auto

speed auto

!

interface FastEthernet0/0.1

encapsulation dot1q 1 native

ip address 192.168.1.1 255.255.255.0

Regards,

Nethelper

Roberto Salazar
Level 8
Level 8

dbshah2000:Can i have a trunk link with 802.1q encapsulation between c3662 & c2950 on 10Mbps /Half Duplex ??

>> Yes, you can given you have the right IOS:

802.1Q encapsulation is now available on the built-in 10BaseT Ethernet interfaces of the Cisco 2610, 2611, and 2612 with Cisco IOS software 12.2(2)T and subsequent releases. Although this feature has been available on the Cisco 2600/3600 series since the release of Cisco IOS 12.1(5)T, support was previously limited to Fast Ethernet interfaces only. 802.1Q is not supported on any other Cisco 2600/3600 series 10BaseT Ethernet interface.

http://www.cisco.com/en/US/partner/products/hw/routers/ps259/prod_bulletin09186a00800921e4.html

is the cisco the router currently doing trunking to the 2950? How is it configured? Is the Bay trunking to the 2950 as well? Can you ping from one router to the other router if the connections to the 2950 are not trunking?

HI Thank You all for your very helpful responses.

It turned out to be a different problem altogether.

Actually the Bay Routers are not managed by us.

Thus there was an IP addressing mistake done by the Service provider.

Once they fixed it to belong to the same LAN as out Cisco router, the Ping & other conenctivity worked fine.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: