02-06-2006 08:52 AM - edited 03-03-2019 01:42 AM
I am actually migrating one to the other and I have the sup 720 built and a switch connected and have done some tests. But to exercise this more I was able to create a trunk port on each 6506 and come up and ping different things and all was well. I shutdown the interface on the sup720 overnight just for safety reasons. The next day I tried to bring up the interfae but both sides of the trunk will not come up at all. There was one time the day before that I had a duplex mismatch, but since changing that, I receive no new messages about the port or interface, either side. I did get one message about a vtp version mismatch that I did not receive before, and I corrected, but after that there have been no error messages - or any messages at all. If I disable and enable the port on the sup1A side it just doesn't come up and if I do a shut and no shut on the interface on the sup720 side is just doesn't come up. I have tried different ports and the same result. Nothing appears to be blocked. Both 6506's continue to work except for the trunk port. I reloaded the sup720 (and therefore lost the vtp error message in the log), and it has not re-occurred. Any ideas as to what may have happened or what I can do? thanks.
02-06-2006 09:05 AM
Hello,
can you post the configurations of the trunks ? Since you said that you corrected the VTP version, what did you do to fix it ? Keep in mind that the VTP version must be the same, otherwise there is no communication. The VTP domainn name must be the same as well (case-sensitive). Also, the native VLAN must be the same for both sides of the trunk.
One other thing you could try is to set the ports to ´speed nonegotiate´.
Let me know if you are making progress, otherwise post back what you are running into.
Regards,
Nethelper
02-06-2006 10:43 AM
The native VLAN is Vlan 1. Different IPs of course. The first time that I brought up the trunks I was able to ping and access applications from my test PC and test switch I had connected to the 6506. I received no errors at that time. It was only after I shutdown the interface and started it again that it gave the initial vtp error (which I wish I saved before I rebooted the 6506). I just set the vtp to version 2. The VTP domain name is the same. All the vlans except vlan 1 and my test vlan are shutdown.
The trunks are on the 6506 sup1a-2ge side: ort 3/10 & 3/11
set port speed 3/15 10
set port speed 3/1-3,3/5-7,3/10-11,3/14,3/16,3/20-21,3/23-24,3/35,3/39-47
100
set port duplex 3/1-3,3/5-7,3/10-11,3/14,3/16,3/20-21,3/23-24,3/35,3/39-47
full
set port trap 3/1-48 enable
set port name 3/3 VLAN_20_Phone_Room
set port name 3/4 VLAN_44_Radiolgy_rtr
set port name 3/6 VLAN_16_PBX_Ph_Rm
set port name 3/7 vlan_17_test
set port name 3/10 6506_Trunk_1
set port name 3/11 6506_Trunk_2
set port name 3/14 VLAN_34_Cerner_FWBK
set port name 3/15 VLAN_54_Cerner_Nortl
set port name 3/16 VLAN_34_Cerner_FWBKT
set port name 3/18 VLAN_68_Cerner_Diet
set port name 3/20 VLAN_100_S_router_#1
set port name 3/21 VLAN_100_S_router_#2
set port name 3/23 VLAN_110_cache1
set port name 3/47 VLAN_102_SHMA_Router
set trunk 3/3 nonegotiate dot1q 1-1005
set trunk 3/6 nonegotiate dot1q 1-1005
set trunk 3/7 nonegotiate dot1q 1-1005
set trunk 3/10 nonegotiate dot1q 1-1005
set trunk 3/11 nonegotiate dot1q 1-1005
set trunk 3/18 nonegotiate dot1q 1-1005
set trunk 3/47 nonegotiate dot1q 1-1005
on the sup 720
interface GigabitEthernet1/10
description "6506 trunk #1"
no ip address
speed 100
duplex full
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1-1005
!
interface GigabitEthernet1/11
description "6506 trunk #2"
no ip address
speed 100
duplex full
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1-1005
on both sides the ports and interfaes are notconnect, there is no errdisabled on the ports.
thanks
02-07-2006 03:05 PM
Gi 1/10 & gi 1/11also had switchport mode trunk. I got a resolution through TAC that I had to have some traffic on the switch via a non-trunk port to get the trunk port up. I did put something on a non-trunk port and it appeared to o.k. I did originally have something on a non-trunk port for configuring purposes before I used the switch. So one down.
But the other weird thing is that I made a big mistake in connecting the 2 switches - yes go back to cisco 101 for me - I used a straight-through cable - BUT it DID work with the straight through cable (which is why I didn't catch it - can't possibly be stupidity). The TAC guy said he thought that there was midx sensing on the sup720. Which would explain why it worked, but not why it suddenly didn't work anymore.
Any ideas anyone?
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: