Network Faults
This section explains how to access network fault information. Network alarms account for problems related to low-level network issues and might occur when the software is unable to communicate with the hardware.
NAT Statistics
Use the following command to display NAT table information.
- show nat
There is also an alarm that occurs when the NAT table usage reaches 90% or greater of its capacity.
Viewing Information from the NAT Table
Display information from the NAT table by using the show nat command along with one of the following subcommands.
Note:
Do not display the entire contents of the NAT table on your screen. The size of the table can interfere with call processing.- by-index:
specify the range of entries to display, up to a maximum of 5024 entries. For
example, to see entries on lines 10 through 50 of the NAT table, enter the
following:
show nat by-index 10 50A Space separates the two numbers defining the range. If you do not specify a range, the system uses the default range of 1 through 200. The range you enter here corresponds to line numbers in the table, and not to the number of the entry itself.
- by-addr:
specify the entries to display according to SA and DA values. For example, to
view entries with an SA of 192.168.112.25 and a DA 101.102.103.104, enter the
following:
show nat by-addr 192.168.112.25 101.102.103.104The system matches these values to the NAT table entries and displays the pertinent information. If no addresses are entered, the system displays all of the table entries (all of the table entries will match).
- in-tabular: Display a specified range of entries in the NAT table display in table form, maximum of 5024 entries. The syntax is modeled on the show nat by-index command: show nat in-tabular <starting entry> <ending entry>
- info: Display general NAT table information. The output is used for quick viewing of a Oracle Communications Session Border Controller’s overall NAT functions, including the maximum number of NAT table entries, the number of used NAT table entries, the length of the NAT table search key, the first searchable NAT table entry address, the length of the data entry, the first data entry address, and whether or not aging and policing are enabled in the NAT table.
- flow-info: Display NAT table
entry debug information. The syntax is:
show nat flow-info <all | by-addr | by-switchid>
Viewing NAT information By Index
The following example shows the output of the show nat by-index command:
ORACLE# show nat by-index 1 2
-------------------------------------------------------------
Total number of entries in the Database = 395
NAT table search address 1, xsmAddr 62580 :
Flow type: Traditional weighted flow
SA_flow_key : 192.168.200.041 SA_prefix : 32
DA_flow_key : 000.000.000.000 DA_prefix : 0
SP_flow_key : 0 SP_prefix : 0
DP_flow_key : 0 DP_prefix : 0
VLAN_flow_key : 0
Protocol_flow_key : 0
Ingress_flow_key : 64
Ingress Slot : 64
Ingress Port : 0
XSA_data_entry : 000.000.000.000
XDA_data_entry : 000.000.000.000
XSP_data_entry : 0
XDP_data_entry : 0
Egress_data_entry : 0
Egress Slot : 0
Egress Port : 0
flow_action : 0X1
optional_data : 0
FPGA_handle : 0xffffffff
assoc_FPGA_handle : 0xffffffff
VLAN_data_entry : 0
host_table_index : 1
Switch ID : 0x00034000
average-rate : 0
weight : 0x10
init_flow_guard : 4294967295
inact_flow_guard : 4294967295
max_flow_guard : 4294967295
q - quit, return - next entry, space - through to the end :Viewing NAT Information By Address
ORACLE# show nat by-addr
sip_key = (null), dip_key = (null)
-- Total number of entries in the NAT table is 407
---------------------------------
NAT table search address 1 :
Flow type: Traditional weighted flow. Weight = 16
SA_flow_key : 192.168.200.041 SA_prefix : 32
DA_flow_key : 000.000.000.000 DA_prefix : 0
SP_flow_key : 0 SP_prefix : 0
DP_flow_key : 0 DP_prefix : 0
VLAN_flow_key : 0
Protocol_flow_key : 0
Ingress_flow_key : 64
Ingress Slot : 64
Ingress Port : 0
XSA_data_entry : 000.000.000.000
XDA_data_entry : 000.000.000.000
XSP_data_entry : 0
XDP_data_entry : 0
Egress_data_entry : 0
Egress Slot : 0
Egress Port : 0
flow_action : 0X1
optional_data : 0
FPGA_handle : 0xffffffff
assoc_FPGA_handle : 0xffffffff
VLAN_data_entry : 0
host_table_index : 1
Switch ID : 0x00034000
average-rate : 0
weight : 0x10
init_flow_guard : 4294967295
inact_flow_guard : 4294967295
max_flow_guard : 4294967295
q - quit, return - next entry, space - through to the end :Viewing NAT Information In Tabular
acmepacket# show nat in-tabular
NAT SA_key DA_key SP_key DP_key VLAN_key ING PROTO WEIGHT
addr=1, sip=0xac100056, dip=0x00000000, SP=0x0000, DP=0x0000, VLAN= 0, Intf=64, proto= 0, weight=0x10
addr=2, sip=0x7f000064, dip=0x00000000, SP=0x0000, DP=0x0000, VLAN=999, Intf=64, proto= 0, weight=0x10
addr=3, sip=0x00000000, dip=0xac100056, SP=0x0000, DP=0x0000, VLAN= 0, Intf= 0, proto= 6, weight=0x9
addr=4, sip=0x00000000, dip=0xac100056, SP=0x0000, DP=0x0000, VLAN= 0, Intf= 0, proto=17, weight=0x9
addr=5, sip=0x00000000, dip=0x7f000064, SP=0x0000, DP=0x13c4, VLAN=999, Intf= 0, proto=17, weight=0xd
addr=6, sip=0x00000000, dip=0xac100058, SP=0x0000, DP=0x13c4, VLAN= 0, Intf= 0, proto=17, weight=0xd
addr=7, sip=0x00000000, dip=0xc0a86458, SP=0x0000, DP=0x13c4, VLAN= 0, Intf= 1, proto=17, weight=0xd
addr=8, sip=0x00000000, dip=0xac100056, SP=0x0000, DP=0x0001, VLAN= 0, Intf= 0, proto= 6, weight=0x63Viewing General NAT Table Information
ORACLE# show nat info
-- NAT table info --
Maximum number of entries : 7768
Number of used entries : 10
Length of search key : 2 (x 64 bits)
First search entry address : 0x0
length of data entry : 4 (x 64 bits)
First data entry address : 0x0
Enable aging : 1
Enable policing : 0Viewing Network Address Translation (NAT) Flow Information
To confirm that network interfaces are properly created, use the show nat flow-info by-addr command to view the NAT flow information table.
The following illustration is a sample NAT flow information table.
ORACLE# show nat flow-info by-add 192.168.225.1
Index Prot Intf:Vlan Src IP:Port Dst IP:Port
------------------------------------------------------------------------------
9 udp I=0/0:33 192.168.225.6:0 192.168.225.1:10006
O=0/0:33 192.168.225.1:10004 192.168.225.4:10000
11 udp I=0/0:33 192.168.225.4:0 192.168.225.1:10004
O=0/0:33 192.168.225.1:10006 192.168.225.6:10000
----------------------------------------------
ORACLE#NAT Table Utilization Alarm
The following table describes the NAT table utilization alarm:
| Alarm Name | Alarm ID | Alarm Severity | Cause(s) | Example Log Message | Actions | |
|---|---|---|---|---|---|---|
| NAT TABLE UTILIZATION | 131102 | MINOR | NAT table usage reached 90% or greater of its capacity. | NAT table usage X% over threshold X% | Contact Oracle Support | apSysMgmtGroupTrap |
TCP and SCTP State Connection Counters
The Oracle Communications Session Border Controller (SBC) can provide systemwide counts of Transmission Control Protocol (TCP) and Stream Control Transmission Protocol (SCTP) states by way of the show ip tcp and show ip sctp commands from the ACLI.
Connections By State:
0 CLOSED
0 LISTEN
0 SYN_SENT
0 SYN_RCVD
0 ESTABLISHED
0 CLOSE_WAIT
0 FIN_WAIT_1
0 CLOSING
0 LAST_ACK
0 FIN_WAIT_2
0 TIME_WAIT
Inbound Socket Connection By State:
0 CLOSED
0 LISTEN
0 SYN_SENT
0 SYN_RCVD
50 ESTABLISHED
0 CLOSE_WAIT
0 FIN_WAIT_1
0 CLOSING
0 LAST_ACK
0 FIN_WAIT_2
0 TIME_WAIT
Outbound Socket Connection By State:
0 CLOSED
0 LISTEN
0 SYN_SENT
0 SYN_RCVD
1 ESTABLISHED
0 CLOSE_WAIT
0 FIN_WAIT_1
0 CLOSING
0 LAST_ACK
0 FIN_WAIT_2
0 TIME_WAIT
Listen Socket Connection By State:
0 CLOSED
2 LISTEN
0 SYN_SENT
0 SYN_RCVD
0 ESTABLISHED
0 CLOSE_WAIT
0 FIN_WAIT_1
0 CLOSING
0 LAST_ACK
0 FIN_WAIT_2
0 TIME_WAIT
IMSAKA Inbound Socket Connection By State:
0 CLOSED
0 LISTEN
0 SYN_SENT
0 SYN_RCVD
0 ESTABLISHED
0 CLOSE_WAIT
0 FIN_WAIT_1
0 CLOSING
0 LAST_ACK
0 FIN_WAIT_2
0 TIME_WAIT
IMSAKA Outbound Socket Connection By State:
0 CLOSED
0 LISTEN
0 SYN_SENT
0 SYN_RCVD
0 ESTABLISHED
0 CLOSE_WAIT
0 FIN_WAIT_1
0 CLOSING
0 LAST_ACK
0 FIN_WAIT_2
0 TIME_WAIT
IMSAKA Listen Socket Connection By State:
0 CLOSED
0 LISTEN
0 SYN_SENT
0 SYN_RCVD
0 ESTABLISHED
0 CLOSE_WAIT
0 FIN_WAIT_1
0 CLOSING
0 LAST_ACK
0 FIN_WAIT_2
0 TIME_WAIT
Number of Connections Counted = 0
Maximum Connection Count = 0
Maximum Number of Connections Supported = 220000- Number of Connections Counted—The current number of connections the system is supporting.
- Maximum Connection Count—The "permax", or highest number of connections the system has supported simultaneously since the last reboot.
- Maximum Number of Connections Supported—The maximum number of connections the system can support simultaneously.
Connections By State:
0 CLOSED
0 BOUND
0 LISTEN
0 COOKIE_WAIT
0 COOKIE_ECHOED
0 ESTABLISHED
0 SHUTDOWN_SENT
0 SHUTDOWN_RECEIVED
0 SHUTDOWN_ACK_SENT
0 SHUTDOWN_PENDING
Number of Connections Counted = 0
Maximum Connection Count = 0
Maximum Number of Connections Supported = 10000The output of the state counters indicates the number of connections currently in each state. The statistics from the counters do not accumulate like many of the other statistics in the show ip command tree. Most states are ephemeral, and you may see many "0" counters for states other than LISTEN and ESTABLISHED.
TCP Connection Tools
Transmission Control Protocol (TCP) connection tools can assist you in gauging performance, identifying potential memory leaks, and debugging connections for performance tracking and improvement.
The show ip tcp command shows the following socket connections by state:
- inbound
- outbound
- listen
- IMS-AKA
The show sipd tcp and show sipd tcp connections commands display counters to track usage. Use the reset sipd command to reset the counters.
TCP and SCTP State Connection Counters
The Oracle Communications Session Border Controller (SBC) can provide systemwide counts of Transmission Control Protocol (TCP) and Stream Control Transmission Protocol (SCTP) states by way of the show ip tcp and show ip sctp commands from the ACLI.
Connections By State:
0 CLOSED
0 LISTEN
0 SYN_SENT
0 SYN_RCVD
0 ESTABLISHED
0 CLOSE_WAIT
0 FIN_WAIT_1
0 CLOSING
0 LAST_ACK
0 FIN_WAIT_2
0 TIME_WAIT
Inbound Socket Connection By State:
0 CLOSED
0 LISTEN
0 SYN_SENT
0 SYN_RCVD
50 ESTABLISHED
0 CLOSE_WAIT
0 FIN_WAIT_1
0 CLOSING
0 LAST_ACK
0 FIN_WAIT_2
0 TIME_WAIT
Outbound Socket Connection By State:
0 CLOSED
0 LISTEN
0 SYN_SENT
0 SYN_RCVD
1 ESTABLISHED
0 CLOSE_WAIT
0 FIN_WAIT_1
0 CLOSING
0 LAST_ACK
0 FIN_WAIT_2
0 TIME_WAIT
Listen Socket Connection By State:
0 CLOSED
2 LISTEN
0 SYN_SENT
0 SYN_RCVD
0 ESTABLISHED
0 CLOSE_WAIT
0 FIN_WAIT_1
0 CLOSING
0 LAST_ACK
0 FIN_WAIT_2
0 TIME_WAIT
IMSAKA Inbound Socket Connection By State:
0 CLOSED
0 LISTEN
0 SYN_SENT
0 SYN_RCVD
0 ESTABLISHED
0 CLOSE_WAIT
0 FIN_WAIT_1
0 CLOSING
0 LAST_ACK
0 FIN_WAIT_2
0 TIME_WAIT
IMSAKA Outbound Socket Connection By State:
0 CLOSED
0 LISTEN
0 SYN_SENT
0 SYN_RCVD
0 ESTABLISHED
0 CLOSE_WAIT
0 FIN_WAIT_1
0 CLOSING
0 LAST_ACK
0 FIN_WAIT_2
0 TIME_WAIT
IMSAKA Listen Socket Connection By State:
0 CLOSED
0 LISTEN
0 SYN_SENT
0 SYN_RCVD
0 ESTABLISHED
0 CLOSE_WAIT
0 FIN_WAIT_1
0 CLOSING
0 LAST_ACK
0 FIN_WAIT_2
0 TIME_WAIT
Number of Connections Counted = 0
Maximum Connection Count = 0
Maximum Number of Connections Supported = 220000- Number of Connections Counted—The current number of connections the system is supporting.
- Maximum Connection Count—The "permax", or highest number of connections the system has supported simultaneously since the last reboot.
- Maximum Number of Connections Supported—The maximum number of connections the system can support simultaneously.
Connections By State:
0 CLOSED
0 BOUND
0 LISTEN
0 COOKIE_WAIT
0 COOKIE_ECHOED
0 ESTABLISHED
0 SHUTDOWN_SENT
0 SHUTDOWN_RECEIVED
0 SHUTDOWN_ACK_SENT
0 SHUTDOWN_PENDING
Number of Connections Counted = 0
Maximum Connection Count = 0
Maximum Number of Connections Supported = 10000The output of the state counters indicates the number of connections currently in each state. The statistics from the counters do not accumulate like many of the other statistics in the show ip command tree. Most states are ephemeral, and you may see many "0" counters for states other than LISTEN and ESTABLISHED.
show sipd tcp connections
The show sipd tcp connections command displays Transmission Control Protocol (TCP) connection information details on remote and local address/port and connection states for analysis. Oracle recommends that you use the command only during non-peak times or maintenance windows.
- sip-interface—Optional parameter that limits output to sockets in the specified sip-interface
- start start—Integer indicating which connection to start displaying. This can be a negative number. When the number selected for the start variable is greater than the number of TCP connections, the system displays nothing.
- start-count start—Integer as per above plus the count integer, specifying how many TCP connections to display from the start.
- all—Display all of the sipd tcp connections. Exercise caution due to the possibility of consuming all CPU time; preferably use during a maintenance window
ORACLE# show sipd tcp connections
sipd tcp connections
Dir Type State Local Address Remote Address sip-interface-id isImsaka
LISTEN TCP_LISTENING 172.16.101.149:5060 net172
in FORKED TCP_CONNECTED 172.16.101.149:5060 172.16.23.100:51678 net172
in FORKED TCP_CONNECTED 172.16.101.149:5060 172.16.23.100:51679 net172
[...]
in FORKED TCP_CONNECTED 172.16.101.149:5060 172.16.23.100:51727 net172
in FORKED TCP_CONNECTED 172.16.101.149:5060 172.16.23.100:51728 net172
in FORKED TCP_CONNECTED 172.16.101.149:5060 172.16.23.100:51729 net172
LISTEN TCP_LISTENING 192.168.101.149:5060 net192
out CONNECT TCP_CONNECTED 192.168.101.149:8192 192.168.23.100:5060 net192
Connections Displayed: 53
Total Connections: 53
show sipd tcp
.
- inbound
- outbound
- listen
- total
- IMS-AKA
ORACLE# show sipd tcp
11:11:54-110
SIP TCP Sockets -- Period -- -------- Lifetime --------
Active High Total Total PerMax High
All States 53 53 108 108 108 53
TCP_INITIAL 0 0 0 0 0 0
TCP_STARTING 0 0 0 0 0 0
TCP_AVAILABLE 0 1 51 51 51 1
TCP_BOUND 0 1 3 3 3 1
TCP_CONNECTED 51 51 51 51 51 51
TCP_CONNECTING 0 1 1 1 1 1
TCP_LISTENING 2 2 2 2 2 2
TCP_DISCONNECT 0 0 0 0 0 0
TCP_CLOSED 0 0 0 0 0 0
----------------------------------------------------------------------
SIP Inbound TCP Sockets -- Period -- -------- Lifetime --------
Active High Total Total PerMax High
All States 50 50 100 100 100 50
TCP_INITIAL 0 0 0 0 0 0
TCP_STARTING 0 0 0 0 0 0
TCP_AVAILABLE 0 1 50 50 50 1
TCP_BOUND 0 0 0 0 0 0
TCP_CONNECTED 50 50 50 50 50 50
TCP_CONNECTING 0 0 0 0 0 0
TCP_LISTENING 0 0 0 0 0 0
TCP_DISCONNECT 0 0 0 0 0 0
TCP_CLOSED 0 0 0 0 0 0
----------------------------------------------------------------------
SIP Outbound TCP Sockets -- Period -- -------- Lifetime --------
Active High Total Total PerMax High
All States 1 1 4 4 4 1
TCP_INITIAL 0 0 0 0 0 0
TCP_STARTING 0 0 0 0 0 0
TCP_AVAILABLE 0 1 1 1 1 1
TCP_BOUND 0 1 1 1 1 1
TCP_CONNECTED 1 1 1 1 1 1
TCP_CONNECTING 0 1 1 1 1 1
TCP_LISTENING 0 0 0 0 0 0
TCP_DISCONNECT 0 0 0 0 0 0
TCP_CLOSED 0 0 0 0 0 0
----------------------------------------------------------------------
SIP Listen TCP Sockets -- Period -- -------- Lifetime --------
Active High Total Total PerMax High
All States 2 2 4 4 4 2
TCP_INITIAL 0 0 0 0 0 0
TCP_STARTING 0 0 0 0 0 0
TCP_AVAILABLE 0 0 0 0 0 0
TCP_BOUND 0 1 2 2 2 1
TCP_CONNECTED 0 0 0 0 0 0
TCP_CONNECTING 0 0 0 0 0 0
TCP_LISTENING 2 2 2 2 2 2
TCP_DISCONNECT 0 0 0 0 0 0
TCP_CLOSED 0 0 0 0 0 0
---------------------------------------------------------------------- ORACLE# show sipd tcp
15:28:51-197
[...]
SIP IMSAKA In TCP Sockets -- Period -- -------- Lifetime --------
Active High Total Total PerMax High
All States 0 0 0 0 0 0
TCP_INITIAL 0 0 0 0 0 0
TCP_STARTING 0 0 0 0 0 0
TCP_AVAILABLE 0 0 0 0 0 0
TCP_BOUND 0 0 0 0 0 0
TCP_CONNECTED 0 0 0 0 0 0
TCP_CONNECTING 0 0 0 0 0 0
TCP_LISTENING 0 0 0 0 0 0
TCP_DISCONNECT 0 0 0 0 0 0
TCP_CLOSED 0 0 0 0 0 0
----------------------------------------------------------------------
SIP IMSAKA Out TCP Sockets -- Period -- -------- Lifetime --------
Active High Total Total PerMax High
All States 0 0 0 0 0 0
TCP_INITIAL 0 0 0 0 0 0
TCP_STARTING 0 0 0 0 0 0
TCP_AVAILABLE 0 0 0 0 0 0
TCP_BOUND 0 0 0 0 0 0
TCP_CONNECTED 0 0 0 0 0 0
TCP_CONNECTING 0 0 0 0 0 0
TCP_LISTENING 0 0 0 0 0 0
TCP_DISCONNECT 0 0 0 0 0 0
TCP_CLOSED 0 0 0 0 0 0
----------------------------------------------------------------------
SIP IMSAKA Listen TCP Sockets -- Period -- -------- Lifetime --------
Active High Total Total PerMax High
All States 1 1 0 2 2 1
TCP_INITIAL 0 0 0 0 0 0
TCP_STARTING 0 0 0 0 0 0
TCP_AVAILABLE 0 0 0 0 0 0
TCP_BOUND 0 0 0 1 1 1
TCP_CONNECTED 0 0 0 0 0 0
TCP_CONNECTING 0 0 0 0 0 0
TCP_LISTENING 1 1 0 1 1 1
TCP_DISCONNECT 0 0 0 0 0 0
TCP_CLOSED 0 0 0 0 0 0
----------------------------------------------------------------------
ARP Statistics
You can use the following command to view ARP statistics:
- show arp statistics
There is also an alarm that occurs when a gateway is unreachable.
Viewing Address Mappings
Display the current Internet-to-Ethernet address mappings in the ARP table by using the show arp command. The first section of this display shows the following information: destination, gateway, flags, reference count, use, and interface. The second section shows the interface, VLAN, IP address, MAC address, timestamp, and type.
The intf (interface) column in the ARP includes both slot and port information. If a value of 0/1 appears, 0 refers to the slot and 1 refers to the port.
ORACLE# show arp
LINK LEVEL ARP TABLE
destination gateway flags Refcnt Use Interface
-------------------------------------------------------------------------
172.30.0.1 00:0f:23:4a:d8:80 405 1 0 wancom0
-------------------------------------------------------------------------
Total ARP Entries = 3
-----------------------
Intf VLAN IP-Address MAC time-stamp type
0/0 0 010.000.045.001 00:00:00:00:00:00 1108462861 invalid
Special Entries:
0/0 0 000.000.000.000 00:00:00:00:00:00 1108462861 gateway
0/0 0 010.000.045.000 00:00:00:00:00:00 1108462861 network
Gateway Status:
Intf VLAN IP-Address MAC time-stamp hb status
0/0 0 010.000.045.001 00:00:00:00:00:00 1108462861 unreachable
-- ARP table info --
Maximum number of entries : 512
Number of used entries : 3
Length of search key : 1 (x 64 bits)
First search entry address : 0x3cb0
length of data entry : 2 (x 64 bits)
First data entry address : 0x7960
Enable aging : 0
Enable policing : 0Gateway Unreachable Alarm
The Oracle Communications Session Border Controller supports polling for and detection of front interface links to the default gateway when monitoring ARP connectivity. Based on configured gateway link parameter, the Oracle Communications Session Border Controller detects connectivity loss, generates an alarm when it loses ARP-connectivity to the front interface gateway, and decrements its health score accordingly.
The GATEWAY UNREACHABLE network-level alarm is generated in the following circumstances:
- If the ARP manager has not
received any ARP messages from a front interface gateway (assigned when the
network interface was configured) within the configured heartbeat time period,
it will send out ARP requests and wait for a reply.
You can set this heartbeat time period when configuring the gateway heartbeat interval for the redundancy element or when configuring the gw heartbeat’s heartbeat field for the network interface element.
- If no reply is received
after retrying (re-sending) ARP requests for a configured number of times.
You can set this retry value when configuring the gateway heartbeat retry field for the redundancy element or the gw heartbeat’s retry count field for the network interface element.
The GATEWAY UNREACHABLE alarm decrements the health score of the Oracle Communications Session Border Controller by the amount you set for either the gateway heartbeat health field of the redundancy element or the gw heartbeat’s health score field for the network interface. The alarm is cleared once a front interface gateway ARP entry is valid again.
After the initial alarm is triggered, the Oracle Communications Session Border Controller continues to attempt to connect to the front interface gateway. It issues ARP requests (retries) every five seconds until front interface gateway ARP connectivity is achieved.
You can set the gateway link failure detection and polling parameters, and the health score decrement (reduction) value for the entire Oracle Communications Session Border Controller by configuring the redundancy element or for each individual network interface by configuring the gw heartbeat for the network interface.
The following table lists information about the GATEWAY UNREACHABLE alarm.
| Alarm Name | Alarm ID | Alarm Severity | Cause(s) | Example Log Message | Actions | Generated Traps |
|---|---|---|---|---|---|---|
| GATEWAY UNREACHABLE | dynamicID | MAJOR | The Oracle Communications Session Border Controller lost ARP connectivity to the front interface gateway. | gateway X.X.X.X unreachable on slot Y port Z subport ZZ (where X.X.X.X is the IPv4 address of the front interface gateway, Y is the front interface slot number, Z is the front interface port number, and ZZ is the subport ID) | Check to see if Gateway IP has changed or is down, show arp and ping test to down gateway | apSysMgmtGatewayUnreachableTrap |
Note:
The value of this alarm changes based on a number of factors. The total alarm ID range falls between 196608 and 262143. The alarm ID is calculated based on a compilation of a hexadecimal number that represents the VLAN ID and the front interface slot/port numbers.System Reboot after Gateway Unreachable Event
Oracle Communications Session Border Controllers in an HA pair can be configured so that after a gateway unreachable event initiates a switchover, the newly standby system (where the event occurred) is rebooted.
In some HA scenarios when a system or NIU-based processor error occurs, and a gateway unreachable condition is experienced, the Oracle Communications Session Border Controller fails-over to its standby as expected. The new standby system will not reboot to recover because only a typical gateway unreachable event occurred. When the HA pair returns to its initial role states, the first Oracle Communications Session Border Controller has never recovered from the NIU error and an outage results from the system or NIU error persisting.
Such scenarios can be mitigated by configuring the reboot=Gateway-Unreachable option in the system-config. This option is disabled by default and must be explicitly configured for use.
The system, network-interface, gw-heartbeat, health-score parameter must be a value other than the default of 0.
The syntax below shows how to set this option.
ORACLE#configure terminal
ORACLE(configure)#system
ORACLE(system)#system-config
ORACLE(system-config)#select
ORACLE(system-config)#options +reboot=Gateway-Unreachable
ORACLE(system-config)#done
This feature contains an additional mechanism to prevent runaway failover-and-reboots.
After the failover, but just prior to the reboot, the system creates a time-stamped logfile indicating that the reboot-and-failover occurred. When the gateway-unreachable alarm is cleared, this file is deleted. When the next gateway unreachable event occurs on an active system, and would otherwise prompt a failover-and-reboot via health score degradation, the system checks for the presence of the logfile. If the logfile's creation date is less than one hour old, the system will failover but not reboot. If the logfile's creation date is greater than or equal to one hour old, the failover-and-reboot will proceed as expected.
View Network Interfaces Statistics
Display statistics for network interfaces by using show interfaces command. The following is an example of the Version S-CZ7.1.2 output:
ORACLE# show interfaces
lo:
Flags: (0x49) UP LOOPBACK TRAILERS ARP RUNNING
Type: LOOPBACK_INTERFACE
inet is: 127.0.0.1 Vlan: 0
Metric is 0:
Maximum Transfer Unit size is 16436
46001 octets received
46001 octets sent
364 packets received
364 packets sent
0 multicast packets received
0 incoming packets discarded
0 outgoing packets discarded
0 incoming errors
0 outgoing errors
0 invalid frames
0 collisions; 0 carrier errors
0 input queue drops
0 output queue drops
wancom0:
Flags: (0x1043) UP BROADCAST MULTICAST TRAILERS ARP RUNNING
Type: GIGABIT_ETHERNET
inet is: 172.30.46.20 Vlan: 0
Netmask: 255.255.0.0
Gateway: 172.30.0.1
Ethernet address is 00:08:25:a2:56:20
Metric is 0:
Maximum Transfer Unit size is 1500
809490537 octets received
775555 octets sent
10768436 packets received
9449 packets sent
73012 multicast packets received
74839 incoming packets discarded
0 outgoing packets discarded
0 incoming errors
0 outgoing errors
0 invalid frames
0 collisions; 0 carrier errors
0 input queue drops
0 output queue drops
left-left (media slot 0, port 0)
Flags: UP BROADCAST MULTICAST ARP RUNNING
Type: GIGABIT_ETHERNET
Admin State: enabled
Auto Negotiation: enabled
Internet address: 192.168.0.10 Vlan: 0
Broadcast Address: 192.168.0.255
Netmask: 255.255.255.0
Gateway: 192.168.0.1
Maximum Transfer Unit size is 1500
Ethernet address is 00:08:25:a2:56:23
Virtual Ethernet address is 00:08:25:a2:56:23
Metric is 0
0 octets received
4668396 octets sent
0 packets received
72942 packets sent
0 non-unicast packets received
0 unicast packets received
0 input discards
0 input unknown protocols
0 input errors
0 output errors
0 collisions; 0 droppedYou can also view key running statistics about the interfaces within a single screen by using the show interfaces [brief] command.
For example:
show interfaces brief
Slt Prt Vlan Interface IP Gateway Adm Oper
Num Num ID Name Address Address Stat Stat
--- --- ---- ---------- ---------------------- ----------------------- ---- ----
- - - lo 127.0.0.1 - up up
- - - wancom0 172.30.46.20/16 172.30.0.1 up up
0 0 0 left-left 192.168.0.10/24 192.168.0.1 up up
--------------------------------------------------------------------------------