Netonix Forums

Not sure what's going on here, but hopefully someone can help:

CCR <copper> WS-10-250-AC <fiber> WS-26-400-IDC <200 mile fiber transport> CCR
100.65.36.1 > 100.65.36.12 > 100.65.36.15 > 100.65.36.9

I'm assuming that the Web GUI of the WS is doing it's thing, but I can't ssh or telnet into either device to verify that they're even listening on ports 22 or 23.

Also, not sure what's going on, but the 400-IDC seems to be having issues with ICMP. I'd like to blame it on Layer-1 issues, but I can't prove it. To get started, here's a ping all the way through both switches to a device 200 miles away:

[troy@PK_CORE] > ping 100.65.36.9 count=5
SEQ HOST SIZE TTL TIME STATUS
0 100.65.36.9 56 64 9ms
1 100.65.36.9 56 64 4ms
2 100.65.36.9 56 64 4ms
3 100.65.36.9 56 64 4ms
4 100.65.36.9 56 64 4ms
sent=5 received=5 packet-loss=0% min-rtt=4ms avg-rtt=5ms max-rtt=9ms

It can even push some decent bandwidth end-to-end (transmitting from the other end).

[admin@other_router] > tool bandwidth-test 100.65.36.1 duration=30s direction=transmit
status: done testing
duration: 31s
tx-current: 299.9Mbps
tx-10-second-average: 299.9Mbps
tx-total-average: 299.9Mbps
random-data: no
direction: transmit
tx-size: 1500

First, let's test the first switch. Connected via 1G Copper. No interface errors on either the CCR or the switch:

[troy@PK_CORE] > /sys ssh user=admin 100.65.36.12
connectHandler: Connection timed out

Welcome back!
[troy@PK_CORE] > /sys telnet 100.65.36.12
Trying 100.65.36.12...


telnet: Unable to connect to remote host: Connection timed out

Welcome back!
[troy@PK_CORE] > ping 100.65.36.12
SEQ HOST SIZE TTL TIME STATUS
0 100.65.36.12 56 64 0ms
1 100.65.36.12 56 64 0ms
2 100.65.36.12 56 64 0ms
3 100.65.36.12 56 64 0ms
4 100.65.36.12 56 64 0ms
sent=5 received=5 packet-loss=0% min-rtt=0ms avg-rtt=0ms max-rtt=0ms

Next up, is the 2nd switch. Connection is via a single mode, bi-directional SFP on either end. Neither switch shows any interface errors here either.

You'll notice that this switch is running RC. It was on 1.4.9, I downgraded it to 1.4.8, then upgraded it to 1.5.0rc4. Behavior repeats on all 3 versions.

[troy@PK_CORE] > /sys ssh user=admin 100.65.36.15
connectHandler: Connection timed out

Welcome back!
[troy@PK_CORE] > /sys telnet 100.65.36.15
Trying 100.65.36.15...
telnet: Unable to connect to remote host: Connection timed out

Welcome back!
[troy@PK_CORE] > ping 100.65.36.15
SEQ HOST SIZE TTL TIME STATUS
0 100.65.36.15 timeout
1 100.65.36.15 56 64 537ms
2 100.65.36.15 timeout
3 100.65.36.15 timeout
4 100.65.36.15 56 64 177ms
5 100.65.36.15 timeout
6 100.65.36.15 56 64 894ms
7 100.65.36.15 56 64 0ms
sent=8 received=4 packet-loss=50% min-rtt=0ms avg-rtt=402ms max-rtt=894ms

Just to follow up. I defaulted the WS-26-400-IDC and reconfigured. Same weird behavior on ICMP. It is, however, accepting ssh/telnet connections, which I suppose is progress. Still running 1.5.0rc4.

Code: Select all

 [troy@PK_CORE] > ping 100.65.36.15
 SEQ HOST SIZE TTL TIME STATUS
 0 100.65.36.15 56 64 767ms
 1 100.65.36.15 timeout
 2 100.65.36.15 timeout
 3 100.65.36.15 56 64 459ms
 4 100.65.36.15 timeout
 5 100.65.36.15 timeout
 6 100.65.36.15 56 64 130ms
 7 100.65.36.15 timeout
 8 100.65.36.15 56 64 893ms
 9 100.65.36.15 56 64 0ms
 10 100.65.36.15 timeout
 11 100.65.36.15 56 64 846ms
 12 100.65.36.15 56 64 0ms
 13 100.65.36.15 timeout
 14 100.65.36.15 56 64 887ms
 15 100.65.36.15 56 64 0ms
 16 100.65.36.15 timeout
 17 100.65.36.15 56 64 746ms
 18 100.65.36.15 56 64 0ms
 19 100.65.36.15 timeout
 sent=20 received=11 packet-loss=45% min-rtt=0ms avg-rtt=429ms max-rtt=893ms

 

Code: Select all

 [troy@PK_CORE] > /sys telnet 100.65.36.15
Trying 100.65.36.15...
Connected to 100.65.36.15.
Escape character is '^]'.
PEAK.SW.36.15 login: admin
Password:


BusyBox v1.19.4 (2017-03-07 13:42:37 EST) built-in shell (ash)
Enter 'help' for a list of built-in commands.

PEAK.SW.36.15#
PEAK.SW.36.15#
PEAK.SW.36.15# ping 100.65.36.1
PING 100.65.36.1 (100.65.36.1): 56 data bytes
64 bytes from 100.65.36.1: seq=0 ttl=64 time=1814.219 ms
64 bytes from 100.65.36.1: seq=1 ttl=64 time=814.821 ms
64 bytes from 100.65.36.1: seq=2 ttl=64 time=1.935 ms
64 bytes from 100.65.36.1: seq=3 ttl=64 time=1518.530 ms
64 bytes from 100.65.36.1: seq=4 ttl=64 time=519.048 ms

--- 100.65.36.1 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 1.935/933.710/1814.219 ms
PEAK.SW.36.15#