09-16-2007 02:47 AM
Hi,
I am using Cisco Works LMS 2.6. If I do a check for discrepancies, I get a Link Trunk / Non Trunk Mismatch, between our 6500 and 4500. These are linked together with fibre and etherchannel.
I cannot seem to find why it's complaining as the trunking of VLANS works OK, and I'm sure the config is OK. Please could you check it below to see if it's correct?
6500:
set port channel 1/12-13 157
set vlan 400 1/1-14,1/16
clear trunk 1/12 1
set trunk 1/12 on dot1q 2-4094
clear trunk 1/13 1
set trunk 1/13 on dot1q 2-4094
set port channel 1/12-13 mode desirable silent
4500:
interface Port-channel2
description Link to Core 1
switchport
switchport trunk encapsulation dot1q
switchport trunk native vlan 400
switchport trunk allowed vlan 2-4094
switchport mode trunk
interface GigabitEthernet1/1
switchport trunk encapsulation dot1q
switchport trunk native vlan 400
switchport trunk allowed vlan 2-4094
switchport mode trunk
channel-group 2 mode desirable
interface GigabitEthernet2/1
switchport trunk encapsulation dot1q
switchport trunk native vlan 400
switchport trunk allowed vlan 2-4094
switchport mode trunk
channel-group 2 mode desirable
I really hope someone can explain this to me. Is it the config, or is Cisco Works sometimes wrong?
Kind regards
James
Solved! Go to Solution.
09-16-2007 08:35 AM
Campus Manager doesn't look at the config to compute trunking status. It does it all via SNMP. For both switches, it will use the vlanTrunkPortDynamicState object from the CISCO-VTP-MIB to determine whether or not the port is trunking. There may be an SNMP issue in one of the versions of code where the trunk status is not being properly reflected via SNMP.
09-16-2007 08:35 AM
Campus Manager doesn't look at the config to compute trunking status. It does it all via SNMP. For both switches, it will use the vlanTrunkPortDynamicState object from the CISCO-VTP-MIB to determine whether or not the port is trunking. There may be an SNMP issue in one of the versions of code where the trunk status is not being properly reflected via SNMP.
09-16-2007 08:43 AM
I have probably been chasing a fault that isn't really there then.
Many thanks for your prompt reply.
James
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide