| Asset ID: |
1-72-2258535.1 |
| Update Date: | 2017-05-07 |
| Keywords: | |
Solution Type
Problem Resolution Sure
Solution
2258535.1
:
End users experiencing delayed and dropped connections to data base
| Related Categories |
- PLA-Support>Sun Systems>SAND>Network>SN-SND: Sun Network Ethernet Switches
|
In this Document
Created from <SR 3-14547637611>
Applies to:
Exadata X5-2 Half Rack - Version All Versions and later
Information in this document applies to any platform.
Symptoms
End clients experiencing dropped and delayed connections to the data base. tcpdump on eth0 showed that the tns traffic was using
the management .
eth0 tcpdump shows production TNS traffic from remote subnets and connecting the adm02 10.25.64.91
Time Source Destination Protocol Length Info
400 0.000 10.25.92.78 10.25.64.91 TNS 67 Request, Data (6), Data
401 0.000 10.25.64.91 10.25.92.78 TNS 67 Response, Data (6), Data
408 0.000 10.25.92.78 10.25.64.91 TCP 60 41645 > ncube-lm [ACK] Seq=14 Ack=14 Win=169 Len=0
409 0.000 10.25.92.78 10.25.64.91 TNS 94 Request, Data (6), Data
414 0.000 10.25.64.91 10.25.92.78 TCP 1514 [TCP segment of a reassembled PDU]
415 0.000 10.25.64.91 10.25.92.78 TNS 88 Response, Data (6), Data
420 0.000 10.25.92.78 10.25.64.91 TCP 60 41645 > ncube-lm [ACK] Seq=54 Ack=1508 Win=191 Len=0
427 0.000 10.25.92.78 10.25.64.91 TNS 188 Request, Data (6), Data
435 0.000 10.25.64.91 10.25.92.78 TNS 188 Response, Data (6), Data
437 0.000 10.25.92.78 10.25.64.91 TNS 178 Request, Data (6), Data
438 0.000 10.25.64.91 10.25.92.78 TNS 184 Response, Data (6), Data
444 0.000 10.25.92.78 10.25.64.91 TCP 1514 [TCP segment of a reassembled PDU]<-------------------------------Full packets
445 0.000 10.25.92.78 10.25.64.91 TCP 1514 [TCP segment of a reassembled PDU]
Cause
The data base traffic was routing over both the eth0 1 gigabit management network and the bondeth0 network when it should only been routed over the bondeth0 ten gigabit interfaces.
TNS Listener was pointing to both the 10Gb bondeth0 IP and the 1Gb eth0 IP .
LSNRCTL for Linux: Version 12.1.0.2.0 - Production on 10-APR-2017 15:16:04
Copyright (c) 1991, 2014, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER)))
STATUS of the LISTENER
------------------------
Alias LISTENER
Version TNSLSNR for Linux: Version 12.1.0.2.0 - Production
Start Date 27-MAR-2017 16:18:44
Uptime 13 days 22 hr. 57 min. 20 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/app/12.1.0.2/grid/network/admin/listener.ora
Listener Log File /u01/app/oracle/diag/tnslsnr/aaorct01dbadm02/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=LISTENER)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.25.64.91)(PORT=1521)))<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<Bondeth0 10Gb bonded Interface IP
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.25.76.63)(PORT=1521)))<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<Eth0 1 Gb Management Interface IP
Solution
Remove all references to eth0 or the management ethernet network 10.25.76.63 in the listener.ora file, so that TNS traffic will only use the bondeth0 interface.
The Cisco Catalyst 4948* ethernet switches within ExaData racks are only for management traffic not data traffic!
Attachments
This solution has no attachment
