Running Packet Trace
There are four steps you take when you use the packet-trace remote feature. For packet-trace local, there are only two.
- Configuring the Oracle® Enterprise Session Border Controller with the trace server information so that the Oracle® Enterprise Session Border Controller knows where to send replicated data. (packet-trace remote only)
- Setting up the capture filter ip proto 4 in your software protocol analyzer if you only want to see the results of the Oracle® Enterprise Session Border Controller packet trace(s). (packet-trace remote only)
- Starting a packet trace.
- Stopping a packet trace.
This section provides information about how to perform all tasks.
Configuring a Trace Server
Trace servers only apply to packet-trace remote. You need to configure a trace server on the Oracle® Enterprise Session Border Controller; this is the device to which the Oracle® Enterprise Session Border Controller sends replicated data. The Oracle® Enterprise Session Border Controller supports one trace server.
To configure a trace server on your Oracle® Enterprise Session Border Controller:
Starting a Remote Packet Trace
You use the start a remote packet trace by entering the appropriate ACLI command with these pieces of information:
- Network interface (name:subport ID combination)
- IP address to be traced; if you do not enter local and/or remote ports when you start the trace, the Oracle® Enterprise Session Border Controller will trace all ports
- (Optional) Local UDP/TCP port on which the Oracle® Enterprise Session Border Controller sends and receives traffic to be traced
- (Optional) Remote UDP/TCP port to which the
Oracle® Enterprise Session Border Controller sends traffic, and from which it receives traffic to be traced; you cannot enter the remote port without specifying a local port
To start a packet trace with local and remote ports specified:
Stopping a Remote Packet Trace
You stop a remote packet trace by entering the appropriate ACLI command with these pieces of information:
- Network interface (name:subport ID combination)
- IP address to be traced
- (Optional) Local UDP/TCP port on which the Oracle® Enterprise Session Border Controller sends and receives traffic to be traced
- (Optional) Remote UDP/TCP port to which the Oracle® Enterprise Session Border Controller sends traffic, and from which it receives traffic to be traced
If the packet trace you want to stop has no entries for local and/or remote ports, then you do not have to specify them.
Starting a Local Packet Trace
You use the start a packet trace by entering the appropriate ACLI command with these pieces of information:
- Network interface (name:subport ID combination)
- (Optional) Enter a tcpdump command line within quotes
Note that the system supports local packet trace on all platforms.