Basic Connectivity Verification

Basic Connectivity Verification

Before troubleshooting rConfig-specific issues, confirm the rConfig server can reach the device on the network and the management protocol is accepting connections.

Network Layer Testing

Run all of the following commands from the rConfig server itself, not a workstation, so the network path matches what rConfig will actually use.

Step 1: Ping device (if ICMP permitted):

ping -c 4 192.168.1.1

Successful ping confirms:

• Device is powered on and connected to network
• Routing exists between rConfig server and device
• Firewall permits ICMP (if configured)

Note

ICMP (ping) is not required for rConfig to download configurations. Some networks block ICMP for security reasons. If ping fails but you know the device is reachable, proceed to next step.

Step 2: Test port connectivity:

Test SSH port (22):

telnet 192.168.1.1 22
nc -zv 192.168.1.1 22

Test Telnet port (23):

telnet 192.168.1.1 23
nc -zv 192.168.1.1 23

Test custom SSH port (e.g., 2222):

nc -zv 192.168.1.1 2222

Successful port test displays “Connection succeeded” or prompt from device. Connection refused indicates:

• Service not running on device
• Firewall blocking port
• Wrong port configured
• Device not listening on tested interface

Step 3: Verify routing and traceroute:

traceroute 192.168.1.1
mtr 192.168.1.1

Trace output identifies where packets stop if connectivity fails. Look for:

• Timeouts at specific hops indicating routing issues
• Firewall ACLs blocking traffic
• Asymmetric routing causing return traffic loss

Resolution for network connectivity failures:

• Verify device management interface has IP address and is administratively up
• Check firewall rules on all devices between rConfig server and target device
• Confirm routing tables include routes to device management networks
• Verify VLANs and VRFs configured correctly for management traffic
• Review access control lists (ACLs) on intermediate devices

Service Availability Testing

After confirming network connectivity, verify the management protocol service is accessible.

SSH availability test:

ssh [email protected]

Successful SSH test displays:

• SSH version banner
• Host key fingerprint
• Password or authentication prompt

SSH failures may indicate:

• SSH service not enabled on device
• SSH version mismatch (SSHv1 vs SSHv2)
• Host key issues
• Cipher or algorithm negotiation failures

Telnet availability test:

telnet 192.168.1.1

Successful Telnet test displays:

• Login prompt
• Banner or message of the day

Telnet failures indicate:

• Telnet service disabled
• VTY lines not configured
• Access class restrictions

SNMP availability test (for SNMP-enabled devices):

snmpwalk -v 2c -c public 192.168.1.1 system

Successful SNMP test returns system information. Failures indicate:

• SNMP not enabled
• Community string incorrect
• SNMP ACLs blocking access
• Wrong SNMP version configured

Next Step

Once basic reachability and service availability are confirmed, move on to Authentication Verification to validate credentials.