I wouldn't expect it to show any output since the traffic is inbound. If you are trying to figure out what that traffic is, I suggest using netflow ("ip route-cache flow" on the interface). "show ip cache flow" will print out the flows on that interface. I don't know off the top of my head whether you need to configure on main or sub interface, but you can try it both ways. IP accounting is an old feature and netflow is the way to get this data going forward.
If you're worried about RX, then the ip accounting won't help you. You actually already have netflow enabled on that interface ("ip flow ingress"). This is the alternative configuration to "ip route-cache flow" that I mentioned in the previous post.
So, since you already have netflow configured, just run "show ip cache flow" and look for flows on the ATM interface.
"ip flow ingress" will monitor just inbound traffic on that interface. "ip flow egress" will monitor outbound.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...