I follow this documentation/procedure :
http://www.cisco.com/c/en/us/td/docs/ios/cable/configuration/guide/12_2s...
And I'm able to capture traffic when I use non-bonding downstream but when I've a modem on bonded DS the same configuration didn't work and can't capture anymore the traffic.
Here the configuration tried :
10K#show cable modem 10.10.26.85 wideband channel
MAC Address IP Address I/F MAC DSxUS Primary
State WB
xxxx.xxce.d99b 10.10.26.85 C8/0/0/U0 w-online 8x1 Wi1/0/0:12
10K#interface Cable8/0/0
cable monitor outbound downstream Wideband-Cable 1/0/0:12
cable monitor outbound interface GigabitEthernet1/2/2 packet-type data docsis
cable monitor incoming interface GigabitEthernet1/2/2 mac-address xxxx.xxce.d99b
cable monitor incoming interface GigabitEthernet1/2/2 mac-address xxxx.xxce.d99f
10K#show cable modem xxxx.xxce.d99b qos
Sfid Dir Curr Sid Sched Prio MaxSusRate MaxBrst MinRsvRate Throughput
State Type
9284 US act 4631 BE 0 0 3044 0 16792
9982 US act 4980 BE 4 0 3044 0 0
9285 DS act N/A BE 0 0 3044 0 80968
9983 DS act N/A BE 4 0 3044 0 0
10K(config-if)#cable monitor incoming interface GigabitEthernet1/2/2 sid 4631
Someone have a working solution or a guess where I fail.
I believe there are limitations for capturing bonded traffic. Not 100% if downstream works, I know that upstream doesn't.
Cisco TAC told us the workaround is to use "cable intercept" command on the bundle interface instead.
The difference between intercepting and cable monitoring is:
1.Cable monitoring will forward raw packets to the outgoing interface.
2.Intercepting will put the raw packets as a UDP data packets, and forwarded it out.