Cisco Cisco ASR 5700 Guide De Dépannage
Access Tech: Other Access Network Peer ID: n/a
callid: 4a6ae475 msid: n/a
Card/Cpu: 2/0 Sessmgr Instance: 329
state: Connected FA address: 66.174.112.72
connect time: Mon May 18 23:45:54 2015 call duration: 00h10m28s
idle time: 00h02m23s idle time left: n/a
session time left: 23h49m32s
ip address: 10.251.88.68
ip pool name: MIP_Private
ha-service name: HA1
source context: HA destination context: XGWout
Acct-session-id: A414F3F6
RADIUS Auth Server IP: 198.51.100.1 RADIUS Acct Server IP: n/a
NAS IP Address: 10.208.148.135 Nexthop IP Address: 209.165.200.230
active input acl: ECS_ACL active output acl: ECS_ACL
ECS Rulebase: 201 Firewall-and-Nat Policy: MIP
Nat Realm: MIP_NAT_Int Nat ip address: 170.200.132.0 (on-demand) (MIP_NAT_Int04)
Nexthop ip address: 209.165.200.230
Nat port chunks allocated[start - end]: (1 chunk) [6464 - 6495]
Max NAT port chunks used: 1
HA binding care-of-addr(s): 203.0.113.1
MIPHA binding 1: Care-of-Address: 203.0.113.1
FA Address/Port: 203.0.113.1/434
Home-Address: 10.251.88.68 HA-Address: 203.0.113.2
Lifetime: 02h00m00s Remaining Life: 01h49m32s
Revocation Negotiated: Yes Revocation I Bit Negotiated: Yes
MN-HA-Key-Present: TRUE MN-HA-SPI:300
FA-HA-Key-Present: TRUE FA-HA-SPI:8832
Proxy DNS Intercept List: ROAMINGDNS
Downlink CSS Information
Service/ACL Names: /ECS_ACL
downlink pkts to svc: 229 downlink pkts from svc: 229
Uplink CSS Information
Service/ACL Names: /ECS_ACL
uplink pkts to svc: 254 uplink pkts from svc: 252
input pkts: 254 output pkts: 229
input bytes: 24088 output bytes: 129012
Non-Subscriber specific commands
Although the commands “show port npu counters” and “show port datalink counters” apply to an
entire interface, if trying to see if the system is processing data for a particular subscriber out the
egress interface (see mention above of limitation of monitor subscriber), and the the subscriber
can be controlled, then try to send very large packets through the network, and see if the interface
counters increment by the number of packets sent in the short window during which they are
sent. Being able to do this with confidence in the results requires making sure the counters for the
packet size chosen are not normally incrementing very frequently before running the test.
entire interface, if trying to see if the system is processing data for a particular subscriber out the
egress interface (see mention above of limitation of monitor subscriber), and the the subscriber
can be controlled, then try to send very large packets through the network, and see if the interface
counters increment by the number of packets sent in the short window during which they are
sent. Being able to do this with confidence in the results requires making sure the counters for the
packet size chosen are not normally incrementing very frequently before running the test.