RSTP and LAGs

When ports are placed into a LAG the LAG configuration is what is used. The individual port configurations are not used at all. So any configuration change you make to a port that is participating in a LAG will not affect that port until the port is no longer in a LAG.

If you can post up the running config, we can help look through it and see if there are any areas of improvement. Also, what kind of discarding are you seeing? Is it a steady percentage of packet loss,or complete network connectivity drop. Is it all the time, or only when certain tasks are being performed on the network?

Thanks

I think you answered my question. If the port-channel config over rides anything in the individual ports, then I am good. Though to close the loop, pertinent config and some diags.

interface ethernet 1/g1
channel-group 1 mode auto
description 'LAG 1'
mtu 9216
exit

!
interface ethernet 1/g2
channel-group 1 mode auto
description 'LAG 1'
mtu 9216
exit
!

interface ethernet 1/g19
channel-group 2 mode auto
description 'LAG 2'
mtu 9216
exit
!
interface ethernet 1/g20
channel-group 2 mode auto
description 'LAG 2'
mtu 9216
exit

!
interface ethernet 2/g1
channel-group 1 mode auto
description 'LAG 1'
mtu 9216

exit
!
interface ethernet 2/g2
channel-group 1 mode auto
description 'LAG 1'
mtu 9216
exit

!

interface ethernet 2/g19
channel-group 2 mode auto
description 'LAG 2'
mtu 9216
exit
!
interface ethernet 2/g20
channel-group 2 mode auto
description 'LAG 2'
mtu 9216

interface port-channel 1
switchport mode trunk
switchport trunk allowed vlan add 1,15,30,75,90,120,135
mtu 9216
exit
!
interface port-channel 2
switchport mode trunk
switchport trunk allowed vlan add 1,15,30,75,90,120,135
mtu 9216
exit
!

console#show interfaces port-channel

Channel Ports Hash Algorithm Type
------- ----------------------------- -------------------
ch1 Active: 1/g1, 1/g2, 2/g1, 3
2/g2
ch2 Active: 1/g19, 1/g20, 3
2/g19, 2/g20

console#show spanning-tree < With only pertinent info

Spanning tree :Enabled - BPDU Flooding :Disabled - Portfast BPDU filtering :Disabled - mode :rstp
CST Regional Root: 80:00:5C:26:0A:9E:BC:C8
Regional Root Path Cost: 0
ROOT ID
Address 00:23:8A:5A:4C:00
Path Cost 205000
Root Port ch1
Hello Time 2 Sec Max Age 20 sec Forward Delay 15 sec TxHoldCount 6 sec
Bridge ID
Priority 32768
Address 5C:26:0A:9E:BC:C8
Hello Time 2 Sec Max Age 20 sec Forward Delay 15 sec
Interfaces

Name State Prio.Nbr Cost Sts Role PortFast Restricted
------ -------- --------- ---------- ---- ----- -------- -------
1/g1 Enabled 128.1 0 FWD Disb No No
1/g2 Enabled 128.2 0 FWD Disb No No

1/g19 Enabled 128.19 0 FWD Disb No No
1/g20 Enabled 128.20 0 FWD Disb No No

2/g1 Enabled 128.53 0 FWD Disb No No
2/g2 Enabled 128.54 0 FWD Disb No No

2/g19 Enabled 128.71 0 FWD Disb No No
2/g20 Enabled 128.72 0 FWD Disb No No

ch1 Enabled 96.626 5000 FWD Root No No 

ch2 Enabled 96.627 5000 DSC Altn No No

What was throwing me off was that the member ports of ch2 show as forwarding where as ch2 is itself is blocking. I was thinking perhaps I had some conflict. So I can safely ignore the member ports as their status essentially doesn't count, only the LAG status does, correct?

Now to figure out why Solarwinds wants to show discards on Alt and Backup ports as legitimate errors....

Correct we want to pay attention to the port channel here. Do channel 1 and 2 connect to the same device? Or maybe channel 2 connection is creating a loop in the network?

Roger that, thanks for the clarification.