I am trying to bring up a port channel using LACP active. Previously, when I would try to bring the ports online it would cause a loopback error. Today I was able to get onsite again and tried configuring it from the edge switch via serial cable. I brought both SFP ports down, and attempted to configure them as a range in hopes of avoiding any loopback errors, but instead I was met with the following:
XXX-YYY-SWT-01(config-if-range)#channel-group 1 mode active
Command rejected: conflicts with IPv6 Snooping (FHS)
% Interface range command failed at TenGigabitEthernet1/1/2
Exiting from range submode without applying rest of the commands in range to avoid unwanted issues
The only things I can find online in relation to this aren't providing much inside other than the obvious, I need to turn off ipv6 snooping. I am having a hard time finding a solution or even how to turn it off. Again, maybe I'm overlooking something.
Other things to highlight/mention are
Cisco IOS XE Software, Version 17.06.05
Cisco IOS Software [Bengaluru], Catalyst L3 Switch Software (CAT9K_IOSXE), Version 17.6.5, RELEASE SOFTWARE (fc2)
Show run int po1:
interface Port-channel1
description TCA-01
switchport trunk allowed vlan 1,5,20,50,80,100,200,950,2110
switchport mode trunk
device-tracking attach-policy MERAKI_POLICY
Show run int Te1/1/1:
interface TenGigabitEthernet1/1/1
description TCA-01
switchport trunk allowed vlan 1,5,20,50,80,100,200,950,2110
switchport mode trunk
auto qos trust
service-policy input AutoQos-4.0-Trust-Cos-Input-Policy
service-policy output AutoQos-4.0-Output-Policy
end
Show run int te1/1/2:
interface TenGigabitEthernet1/1/2
description TCA-01
switchport trunk allowed vlan 1,5,20,50,80,100,200,950,2110
switchport mode trunk
device-tracking attach-policy MERAKI_POLICY
ip flow monitor MERAKI_AVC_IPV4 input
ip flow monitor MERAKI_AVC_IPV4 output
shutdown
ipv6 flow monitor MERAKI_AVC_IPV6 input
ipv6 flow monitor MERAKI_AVC_IPV6 output
auto qos trust
service-policy input AutoQos-4.0-Trust-Cos-Input-Policy
service-policy output AutoQos-4.0-Output-Policy
end
I don't think it is the meraki monitoring that is causing this problem. Any ideas is welcomed!
