Cisco Cisco Packet Data Interworking Function (PDIF) Guide De Dépannage
Rulebase Configuration Mode Commands
route priority ▀
Cisco ASR 5000 Series Command Line Interface Reference ▄
OL-22948-01
Analyzer
Common ways to route to the analyzer
TCP destination port or source port is HTTPS (443). Note that HTTP may use the CONNECT method (see RFC
2817), in which case, the subscriber will be upgraded with transport layer security, but the traffic to/from the
chassis will still be HTTP and be passed through the http rather than the secure-http analyzer (assuming that
routing to the http analyzer has been configured).
2817), in which case, the subscriber will be upgraded with transport layer security, but the traffic to/from the
chassis will still be HTTP and be passed through the http rather than the secure-http analyzer (assuming that
routing to the http analyzer has been configured).
UDP destination port or source port is connection-less WSP (9200) or connection-oriented WSP (9201).
Packets are automatically routed here, if you specified ―wsp-connection-oriented‖ as described above.
TCP destination port or source port of the carrier-specific port number for WAP-2 (e.g. one carrier uses 8799); or,
send all HTTP traffic to the wap2 analyzer if the carrier does not use a special port number.
send all HTTP traffic to the wap2 analyzer if the carrier does not use a special port number.
TCP destination port or source port is FTP control (21) or FTP data (20); or, ftp analyzer (for FTP control
packets) dynamically detected an FTP data flow over TCP (tcp dynamic-flow = ftp-data).
packets) dynamically detected an FTP data flow over TCP (tcp dynamic-flow = ftp-data).
FTP and the command name is retr or stor; or, HTTP and the request method is get or post.
WSP content type is application/vnd.wap.mms-message; or, WSP uri contains ―mms‖; or, HTTP content type is
application/vnd.wap.mms-message; or, HTTP uri contains ―mms‖.
application/vnd.wap.mms-message; or, HTTP uri contains ―mms‖.
UDP destination port or source port is SIP (5060).
RTSP or SIP content type is application/sdp
TCP destination port or source port is SMTP (25).
TCP destination port or source port is IMAP (143).
TCP destination port or source port is POP3 (110).
and
RTSP has embedded RTP/RTCP payloads (you need to enable RTP dynamic flow detection to catch those flows);
or, RTSP or SDP (for SDP within SIP) creates an RTP/RTCP flow over UDP (in addition to enabling the
aforementioned dynamic flow detection, you must make sure that UDP packets are routed to the UDP analyzer)
or, RTP/RTCP uses predefined UDP port numbers (e.g. default UDP port numbers of 5004/5005).
or, RTSP or SDP (for SDP within SIP) creates an RTP/RTCP flow over UDP (in addition to enabling the
aforementioned dynamic flow detection, you must make sure that UDP packets are routed to the UDP analyzer)
or, RTP/RTCP uses predefined UDP port numbers (e.g. default UDP port numbers of 5004/5005).
TCP destination port or source port is RTSP (554).
Use the
CLI command to enable detection of the different P2P
applications specified by the
CLI command; that will cause every TCP or UDP packet to
be automatically routed here
Example
The following command assigns a route and rule action with the route priority of 23, a ruledef of
The following command assigns a route and rule action with the route priority of 23, a ruledef of
, and an analyzer
with description as
to the current rulebase: