R&S SMA100B - Resolving Network Connection Failures

Troubleshooting and notifications
R&S
®
SMA100B
751User Manual 1178.3834.02 ─ 09
Remote command:
:SYSTem:ERRor:ALL? on page 715
Each time a SYST:ERR:ALL? query is sent, the error queue is returned and at the
same time cleared.
:SYSTem:ERRor:HISTory:CLEar on page 718
Clears the messages in the "History" view.
15.5 Resolving network connection failures
Several issues may cause failures in the network connection to the instrument. This
section lists the most likely reasons and the recommended solutions.
Common reasons for network connection failures
●
Network connecting cables and cable connectors of poor quality
●
Incompatibility between the network interface of the R&S SMA100B and certain
switches or routers available on the market
●
An invalid IP address assigned to the instrument
Possible solutions to network connection failures
1.
NOTICE! Connecting to the network can cause network failure. Errors can affect
the entire network.
Consult your network administrator before performing the following tasks:
● Connecting the instrument to the network
● Configuring the network
● Changing IP addresses
2. Try out the following to resolve network connection failures:
● Check the network infrastructure. Exchange connecting cables, if obvious dam-
age is visible.
See also "Cable selection and electromagnetic interference (EMI)" on page 29.
● Observe the link status LED on the R&S SMA100B or the connected network
device. The link status LED is located next to the LAN connector.
If a link failure is detected, connect the instrument to a different device port or
to a different network device.
● Check whether the LAN interface and the required LAN services are enabled.
See Chapter 12.4.3, "Configuring LAN services", on page 368.
● If the IP address is set manually (no DHCP) or obtained via the Zeroconf
(APIPA) protocol:
– Check whether the IP address of the instrument is within the network's
address range.
– Check whether the IP address is valid.
See also "IP Address" on page 399.
Resolving network connection failures