Oracle Communications Diameter Signaling Router (DSR)
 

PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec DSR
 

In this Document

Symptoms

Changes

Cause

Solution

References

Created from <SR 3-16849517641>

Applies to:

Symptoms

TVOE XMI address is not accessible directly. Guests hosted on TVOE currently carry traffic across the XMI network without impairment.

Changes

No known change may be remembered; TVOE XMI is rarely used so it is possible to go undetected for an indefinite term if the guest traffic remains OK. 

One known trigger may be 'shortcut' server replacement procedure where the disk drives from the failed server are retained and re-used in the replacement server in an attempt to avoid re-building the host and guest application servers (standard method).  This is not a supported server (blade/rack-mount) replacement method but has been known to be used by operators and may be [or may appear to be] sometimes successful.

Cause

If the XMI interface displays an old MAC (hardware) address assigned in 'ifconfig,' the bridge link may to fail.   If linked directly to the bond, the guests hosted by this TVOE may not be affected.

Solution

Verify the condition, then update interface and MAC association via netAdm.

Verification:

1. Log into the TVOE host server as admusr via iLO interface or using another valid path (control and/or IMI networks if responsive).
2. Using the 'ifconfig' command, check HWaddr values associated with the physical interfaces (ethXX) and bond normally associated with XMI. If the HWaddr shown for XMI interface does not match, the bridge between XMI and the bond/interfaces may have been broken.
3. Further verify the netAdm view of the xmi interface using the command below:
     [admusr@tvoe ~]$  sudo netAdm query --type=Bridge --name=xmi
If the output has no entry for 'Bridge interface,' and the same 'Hwaddr:' value as shown from 'ifconfig' output in (2) for XMI appears, and if this hardware address is different from the address shown for ethXX & bond normally associated with XMI, use the resolution below to correct.

Resolution:

1. Associate the bond and XMI bridge interfaces via netAdm (Note: replace <bondX> with the bond that *should* be associated with XMI; i.e. bond0):
     [admusr@tvoe ~]$  sudo netAdm set --type=Bridge --name=xmi --bridgeInterfaces=<bondX>
2. Update the MAC (Hardware Address) associated to the XMI bridge:
     [admusr@tvoe ~]$  sudo netAdm set --type=Bridge --name=xmi --updateMAC

After executing the above successfully, the XMI interface should be responsive externally and available for use.

References

This solution has no attachment