Configuring the Junos OS to Enable Larger Delay Buffers for T1, E1, and ds0 Interfaces Configured on Channelized IQ PICs xds0 interfaces configured on channelized IQ PICs are limited to 100,000 microseconds of delay buffer . (The default average packet size on the IQ PIC is 40 bytes.) For these interfaces, it might be necessary to configure a larger buffer size to prevent congestion and packet dropping.
Description Display information about the buffer pool that the Routing Engine uses for local traffic. Local traffic is the routing and management traffic that is exchanged between the Routing Engine and the Packet Forwarding Engine within the router or switch, as well as the routing and management traffic from IP (that is, from OSPF, BGP, SNMP, ping operations, and so on).
The maximum receive threshold specifies the number of milliseconds that a frame received by a radio remains in the buffer memory. To change the maximum receive lifetime, use the following command:MX# set radio-profile profile-name max-rx-lifetime time
System logs provide information about system events that you can use to monitor and troubleshoot the MX and MSS. Event messages for the MX and the attached MPs can be stored or sent to the following destinations: Stored in a local buffer
Security ACLs can filter packets by source address, IP protocol, port type, and other characteristics. When you configure an ACE for a security ACL, MSS stores the ACE in the edit buffer until you commit the ACL to be saved to the permanent configuration. You must commit a security ACL before you can apply it to an authenticated user’s session or map it to a port, VLAN, virtual port, or Distributed MP. Every security ACL must have a name.
Be sure to log the CLI session - the terminal program you are using to access the CLI should have a setting that allows you to capture text or log to file. Do NOT rely upon your cut-and-paste buffer to capture this information.
These updates are processed through the KRT queue. During this state of high activity the socket connection may run out of buffer space. The inbuilt flow control will assure the processing of the updates by repeating attempts to send the update to the KRT queue.
It does so by specifying the operational code of PAUSE in the MAC control frame along with a timer value indicating the duration of the requested PAUSE. This allows the receiving device to recover from any condition that is leading to congestion (i.e. no buffer space remaining to receive additional frames). Once the specifed PAUSE duration expires, the transmitting device can resume the normal tranmission of frames.
This error message indicates that the MX is attempting to add a MAC address to the FDB (Forwarding Database Table) which is already found in the FDB. If this error is found repeatedly in an MX log buffer or contains the MAC address of a client experiencing problems a Trapeze support ticket should be opened for further investigation.
If running Junos release previous to 8.4R1, the issue is by a failure to release the packet buffer memory. If the router is running a Junos release greater than 8.4R1, contact your technical support engineer for assistance. These errors are cosmetic, but will fill the log messages file, and may make the identification of other issues difficult.