Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Cisco Community
- :
- About WiressFriendly
Stats
Member since
09-16-2017
21
Posts
0
Helpful
0
Solutions
Created by
WiressFriendly
in Switching
in Switching
10-27-2017
02:51 PM
10-27-2017
02:51 PM
Okay, thanks anyway.
Do you have other option ideas for async tunneling? I don't like UDP idea too much, maybe any other options available, based on TCP? SDLC or Frame Relay maybe?
... View more
Created by
WiressFriendly
in Switching
in Switching
10-27-2017
02:04 PM
10-27-2017
02:04 PM
Tried, but same error. How about to configure everyting else first? Like a few lines in serial interface with my notes? Maybe problem is there.
... View more
Created by
WiressFriendly
in Switching
in Switching
10-27-2017
01:45 PM
10-27-2017
01:45 PM
I run:
2811_1# show ver
Cisco IOS Software, 2800 Software (C2800NM-ADVENTERPRISEK9-M), Version 15.1(4)M12a, RELEASE SOFTWARE (fc1)
...
ROM: System Bootstrap, Version 12.4(13r)T, RELEASE SOFTWARE (fc1)
... View more
Created by
WiressFriendly
in Switching
in Switching
10-27-2017
01:04 PM
10-27-2017
01:04 PM
Of course I took config example from PDF you provided. I chosen P2P option, because it fit my application (from description). Unfortunately, that's file has nothing on serial interfaces configuration (this part is omitied at all for some reason). So, I have to set it by my own. But I am not a Cisco guru. For example, I am not sure what shall I do with these lines?
interface serial 0/2/0 -- this line remains unchanged
physical-layer async -- this line remains unchanged
encapsulation bstun -- this line remains unchanged
asp role ... -- but this line?
bstun group 103 -- but this line?
bstun route all tcp 192.168.168.x -- but this line?
Also I come across with this thing:
2811_2#udptn 192.168.1.143
% udptn connections not permitted from this terminal
... View more
Created by
WiressFriendly
in Switching
in Switching
10-27-2017
12:37 PM
10-27-2017
12:37 PM
Hi Georg! Why not? But what encapsulations you see for UDPTN?
interface serial 0/2/0
physical-layer async
no ip address
encapsulation ?
clock rate 9600
shut
no shut
exit
!
line 0/2/0
speed 9600
no session-timeout
transport output udptn
dispatch-timeout 10000
dispatch-character 13
modem in
autocommand udptn 192.168.1.144
interface serial 0/2/0
physical-layer async
no ip address
encapsulation ?
shut
no shut
exit
!
!
line 0/2/0
speed 9600
no session-timeout
transport output udptn
dispatch-timeout 10000
dispatch-character 13
modem in
autocommand udptn 192.168.1.143
... View more
Created by
WiressFriendly
in Switching
in Switching
10-27-2017
08:28 AM
10-27-2017
08:28 AM
Hi all!
I have created seral port extender over IP based on Cisco 28xx routers and HWIC-1T + CAB-SS-232FC/MT cables pair.
Here is a picture of my network setup
BSTUN protocol is used in asynchronous mode (yes, I need async). I took this Cisco's sample https://www.cisco.com/c/en/us/support/docs/ip/serial-tunnel-stun/41983-bstun-41983.html and applied to my routers. Both routers in the same LAN, connected to the same unmanaged switch. Each interface can ping each other. So, no any IP connectivity/latency/packet loss problems at all.
My config part related to this "extender" looks like this:
bstun peer-name 192.168.168.145
bstun protocol-group 103 async-generic
!
interface loopback1
ip address 192.168.168.145 255.255.255.255
!
interface serial 0/2/0
physical-layer async
encapsulation bstun
asp role secondary
bstun group 103
bstun route all tcp 192.168.168.146
!
line34
modem DTR-active
speed 9600 < routing part omitted >
bstun peer-name 192.168.168.146
bstun protocol-group 103 async-generic
!
interface loopback1
ip address 192.168.168.146 255.255.255.255
!
interface serial 0/2/0
physical-layer async
encapsulation bstun
asp role primary
bstun group 103
bstun route all tcp 192.168.168.145
!
line34
modem DTR-active
speed 9600
< routing part omitted >
I got working terminal to terminal "messaging" at 9600 bps, and one of serial apps works well too. But most of serial applications (which are 9600 async too!) fails via this serial "extender". I tried many apps, that works absolutely stable on real COM ports and tried many, 5 as minimum. And they are all fails - they try to communicate, send some data, but finally shows timeout, error or doesn't do what expected on the remote side.
I started investigating in direction of commands used to configure such kind lf lines. I read a lot about serial troubleshooting. And I've tried to issue every found command step by step (with checking result after each command issue). But no luck. Here is a list of commands I've applied to ascyn line 34 (s0/2/0):
speed 9600
stopbits 1
databits 8
flowcontrol none | software | hardware
parity none
no motd-banner
no exec-banner
no vacant-message
exec-timeout 0 0
no flush-at-activation
special-character-bits 8
transport input all
transport output all
escape-character none | break | default
modem inout
exec | no exec
no activation-character
session-timeout 0
No luck.
After that I started doing serial port sniffing (by using MS PORTMON) to find dfferencies in data exchange via local COM port and network COM port. And I found a reason in a second! Because all of IRP_MJ_READ request has TIMEOUT status instead of SUCCESS (when local serial port used). And also request length is zero (no data) instead of useful data. Here are portions of PORTMON logs from different setups:
Cisco serial extension
Local com port
19 0.00003131 IRP_MJ_WRITE Serial0 SUCCESS Length 1: F0
20 0.00000411 IOCTL_SERIAL_GET_COMMSTATUS Serial0 SUCCESS
21 0.04243267 IRP_MJ_READ Serial0 SUCCESS Length 1: F0
22 0.00002310 IRP_MJ_WRITE Serial0 SUCCESS Length 1: 02
23 0.00000359 IOCTL_SERIAL_GET_COMMSTATUS Serial0 SUCCESS
24 0.04407666 IRP_MJ_READ Serial0 SUCCESS Length 1: 02
25 0.00004157 IRP_MJ_WRITE Serial0 SUCCESS Length 1: 00
26 0.00000411 IOCTL_SERIAL_GET_COMMSTATUS Serial0 SUCCESS
27 0.04361267 IRP_MJ_READ Serial0 SUCCESS Length 1: 00
28 0.00003952 IRP_MJ_WRITE Serial0 SUCCESS Length 1: F2
29 0.00000308 IOCTL_SERIAL_GET_COMMSTATUS Serial0 SUCCESS
30 0.04404176 IRP_MJ_READ Serial0 SUCCESS Length 1: F2
31 0.00000308 IOCTL_SERIAL_GET_COMMSTATUS Serial0 SUCCESS
32 0.05498560 IRP_MJ_READ Serial0 TIMEOUT Length 0:
33 0.00000359 IOCTL_SERIAL_GET_COMMSTATUS Serial0 SUCCESS
34 0.05494403 IRP_MJ_READ Serial0 TIMEOUT Length 0:
35 0.00000411 IOCTL_SERIAL_GET_COMMSTATUS Serial0 SUCCESS
36 0.05492658 IRP_MJ_READ Serial0 TIMEOUT Length 0:
37 0.00000359 IOCTL_SERIAL_GET_COMMSTATUS Serial0 SUCCESS
38 0.05493582 IRP_MJ_READ Serial0 TIMEOUT Length 0:
39 0.00000411 IOCTL_SERIAL_GET_COMMSTATUS Serial0 SUCCESS
40 0.05493274 IRP_MJ_READ Serial0 TIMEOUT Length 0:
41 0.00000359 IOCTL_SERIAL_GET_COMMSTATUS Serial0 SUCCESS
19 0.00003028 IRP_MJ_WRITE Serial0 SUCCESS Length 1: F0
20 0.00000308 IOCTL_SERIAL_GET_COMMSTATUS Serial0 SUCCESS
21 0.00553711 IRP_MJ_READ Serial0 SUCCESS Length 1: F0
22 0.00002772 IRP_MJ_WRITE Serial0 SUCCESS Length 1: 02
23 0.00000411 IOCTL_SERIAL_GET_COMMSTATUS Serial0 SUCCESS
24 0.00545858 IRP_MJ_READ Serial0 SUCCESS Length 1: 02
25 0.00002669 IRP_MJ_WRITE Serial0 SUCCESS Length 1: 00
26 0.00000359 IOCTL_SERIAL_GET_COMMSTATUS Serial0 SUCCESS
27 0.00548219 IRP_MJ_READ Serial0 SUCCESS Length 1: 00
28 0.00002926 IRP_MJ_WRITE Serial0 SUCCESS Length 1: F2
29 0.00000411 IOCTL_SERIAL_GET_COMMSTATUS Serial0 SUCCESS
30 0.01288655 IRP_MJ_READ Serial0 SUCCESS Length 1: F2
31 0.00000257 IOCTL_SERIAL_GET_COMMSTATUS Serial0 SUCCESS
32 0.00000257 IRP_MJ_READ Serial0 SUCCESS Length 1: F0
33 0.00000205 IOCTL_SERIAL_GET_COMMSTATUS Serial0 SUCCESS
34 0.00000205 IRP_MJ_READ Serial0 SUCCESS Length 1: 03
35 0.00000205 IOCTL_SERIAL_GET_COMMSTATUS Serial0 SUCCESS
36 0.00000205 IRP_MJ_READ Serial0 SUCCESS Length 1: 01
37 0.00000154 IOCTL_SERIAL_GET_COMMSTATUS Serial0 SUCCESS
38 0.00000205 IRP_MJ_READ Serial0 SUCCESS Length 1: 53
39 0.00000205 IOCTL_SERIAL_GET_COMMSTATUS Serial0 SUCCESS
40 0.00000257 IRP_MJ_READ Serial0 SUCCESS Length 1: 47
41 0.00002053 IRP_MJ_WRITE Serial0 SUCCESS Length 1: F0
I believe that there is a some setting/trick in Cisco, because all of my serial apps works fine via Moxa NPorts serial-to-Ethernet adapters (they are async only). With no any manual settings, just IP settings and everything works fine.
But I need to run Cisco.
Any ideas, guys?
... View more
Labels:
Created by
WiressFriendly
in Other Network Architecture Subjects
in Other Network Architecture Subjects
10-19-2017
07:37 AM
10-19-2017
07:37 AM
Dear Paolo!
Do you know software which can connect Cisco ISR and provide a link between virtual COM port and Cisco AUX?
... View more
Created by
WiressFriendly
in Other Network Architecture Subjects
in Other Network Architecture Subjects
10-19-2017
01:55 AM
10-19-2017
01:55 AM
Thanks a lot Jim, you're right. Issue resolved.
... View more
Created by
WiressFriendly
in Other Network Architecture Subjects
in Other Network Architecture Subjects
10-15-2017
04:19 PM
10-15-2017
04:19 PM
So guys, I have some progress. I got link working in pseudowire mode, but not in STUN. In the both cases I did a mistake in bench test configuration. STUN and pseudowire provides synchronous link and they doesn't supports asynchronous comms (what is commonly used by PC port). In this case, one device must provide clocking and another device must listen to it and take to account. So, to test setup of such kind, you must have 2 devices that supports synchronous coms and one of them can provide clocking. Test software (like WinSSD) and loopback plug will NOT work.
Here is working config fit pseudowire mode:
2811_1
2811_2
pseudowire-class link1
pseudowire-class link1
encapsulation l2tpv3
encapsulation l2tpv3
ip local interface FastEthernet0/0
ip local interface FastEthernet0/0
exit
exit
interface Serial0/3/0
interface Serial0/3/0
no ip address
no ip address!no fair-queuexconnect 192.168.1.143 100 pw-class link1
clock rate 9600
!
no fair-queue
!
xconnect 192.168.1.144 100 pw-class link1
!
It's tested and works fine.
Current problem - I still can't get working the same link in STUN mode. Here is config based on Cisco and it doesn't work:
2811_1
2811_2
conf term
conf term
stun peer-name 192.168.168.143
stun peer-name 192.168.168.144
stun protocol-group 101 basic
stun protocol-group 101 basic
stun protocol-group 102 basic
stun protocol-group 102 basic
interface serial 0/3/0
interface serial 0/3/0
no ip address
no ip address
encapsulation stun
encapsulation stun
stun group 101
stun group 101
stun route all tcp 192.168.1.144
stun route all tcp 192.168.1.143
no shut
no shut
interface serial 0/2/0
interface serial 0/2/0
encapsulation stun
encapsulation stun
stun group 102
stun group 102
stun route all tcp 192.168.1.144
stun route all tcp 192.168.1.143
no shut
no shut
interface loopback 0
interface loopback 0
ip address 192.168.168.143 255.255.255.0
ip address 192.168.168.144 255.255.255.0
no shut
no shut
int lo 0
int lo 0
ip address 192.168.168.143 255.255.255.255
ip address 192.168.168.144 255.255.255.255
ip route 192.168.168.144 255.255.255.255 192.168.1.144
ip route 192.168.168.143 255.255.255.255 192.168.1.143
end
end
And have no ideas why it can't provide working link setup that is hooked/wired properly (hardware setup/wiring is the same as was used for pseudowire).
But now STUN shows a lot of debug data and packet counters grow.
R1:
2811_1#show stun
This peer: 192.168.168.143
Serial0/2/0 (group 102 [basic])
state rx_pkts tx_pkts drops
all TCP 192.168.1.144 closed 0 0 0
Serial0/3/0 (group 101 [basic])
state rx_pkts tx_pkts drops
all TCP 192.168.1.144 closed 81563 326257 192
R2:
2811_2#show stun
This peer: 192.168.168.144
Serial0/2/0 (group 102 [basic])
state rx_pkts tx_pkts drops
all TCP 192.168.1.143 closed 0 0 0
Serial0/3/0 (group 101 [basic])
state rx_pkts tx_pkts drops
all TCP 192.168.1.143 closed 80568 322283 633
I am plugged to serial 0/3/0 interfaces of course. Both interfaces are up/up and can ping each other.
STUN debug output is attached.
Any ideas please how to run link in STUN mode? Thanks!
... View more
Created by
WiressFriendly
in Other Network Architecture Subjects
in Other Network Architecture Subjects
10-09-2017
03:30 AM
10-09-2017
03:30 AM
Rick,
Serial ports always up stay up until infinitely until I de-key DTR or close serial port at PC.
Now I am digging in other direction. I found out, that different serial port test software gives me FRAME errors (and other kind of errors, like garbage in RX window) at the PC end. PC port speed and Cisco's DTE port correspondence to clock rate doesn't matter. Looks like 2811_2's DCE port doesn't provide clocking for some reason. Could it be due to missed clocking off modem (DCE port of 2811_1)? Because I do not send any clocking to that's port, because there is only test plug connected.
Another important thing. Looks like STUN is for synchronous serial links only due to SDLC frames usage (where S is Synchronous). I think that I need to supply sync or set Cisco to do that internally.
Here is my updated block diagram with notes. I drawn some clouds with comments and thoughts. And now I need to clarify those, especially big blue one.
What do you think about?
... View more
10-08-2017
09:33 AM
Hi Alex! Thanks for your config. It's very interesting. But unfortunately, it' doesn't work for me. 2 issues: 1. I can't use ip address 10.1.1.0 255.255.255.0 even when ip subnet-zero command issued. So, I migrated to ip address 10.1.1.1 255.255.255.0 (for Router A) and ip address 10.1.1.2 255.255.255.0 (Router B). 2. Host 10.255.255.253 can't be reached from A. Host 10.255.255.254 can't be reached from B. Finally, config doesn't work.Could you please look into? Thanks!
Here are my current configs:
ROUTER A
ROUTER B
hostname ROUTER-A
hostname ROUTER-B
ip subnet-zero
ip subnet-zero
interface loopback 100
interface loopback 100
desc *** LOOPBACK 100 FOR STUN PEERING ***
desc *** LOOPBACK 100 FOR STUN PEERING ***
ip address 10.255.255.254 255.255.255.255
ip address 10.255.255.253 255.255.255.255
no ip red
no ip red
no ip directed-broadcast
no ip directed-broadcast
!
!
stun peer-name 10.255.255.254
stun peer-name 10.255.255.253
stun protocol-group 100 basic
stun protocol-group 100 basic
!
!
interface Serial0/0
interface Serial0/0
desc *** LINK TO ROUTER B ***
desc *** LINK TO ROUTER A ***
bandwidth 2048
bandwidth 2048
ip address 10.255.255.1 255.255.255.252
ip address 10.255.255.2 255.255.255.252
no ip directed-broadcast
no ip directed-broadcast
no ip mroute-cache
no ip mroute-cache
!
!
interface Serial0/1
interface Serial0/1
desc *** STUN LINK TO MY OLD BOX A - THIS IS THE DCE END ***
desc *** STUN LINK TO MY OLD BOX B - THIS IS THE DCE END ***
no ip address
no ip address
no ip directed-broadcast
no ip directed-broadcast
encapsulation stun
encapsulation stun
no ip mroute-cache
no ip mroute-cache
clockrate 9600
clockrate 9600
stun group 100
stun group 100
stun route all interface serial 0/0 direct
stun route all interface serial 0/0 direct
!
!
interface fast 0/0
interface fast 0/0
desc *** LAN ON ROUTER A ***
desc *** LAN ON ROUTER B ***
ip address 10.1.1.1 255.255.255.0
ip address 10.1.1.2 255.255.255.0
!
!
ip route 10.255.255.253 255.255.255.255 10.255.255.2 name LOOPBACK-B
ip route 10.255.255.254 255.255.255.255 10.255.255.1 name LOOPBACK-A
ip route 10.1.1.0 255.255.255.0 10.255.255.2 name LAN-B
ip route 10.1.1.0 255.255.255.0 10.255.255.1 name LAN-A
... View more
Created by
WiressFriendly
in Other Network Architecture Subjects
in Other Network Architecture Subjects
10-07-2017
02:51 PM
10-07-2017
02:51 PM
This is what I see on R2 when I debug serial ports. Looks like nothing bad with S0/3/0, and only S0/2/0 is in trouble (as must be, because I haven't connected any cables to it).
*Oct 7 22:06:32.404: DCE idb->dte_interface = DCE *Oct 7 22:06:32.404: Dscc4(Serial0/3/0): DTR is up. 2811_2# *Oct 7 22:06:34.404: %LINK-3-UPDOWN: Interface Serial0/3/0, changed state to up *Oct 7 22:06:35.404: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/3/0, changed state to up 2811_2# *Oct 7 22:06:56.792: Serial0/2/0: attempting to restart *Oct 7 22:06:56.792: gt96k_mbrd_serial_mode_reg_init:: was DCE, now set to DCE 2811_2# *Oct 7 22:07:26.800: Serial0/2/0: attempting to restart *Oct 7 22:07:26.800: gt96k_mbrd_serial_mode_reg_init:: was DCE, now set to DCE 2811_2# *Oct 7 22:07:56.800: Serial0/2/0: attempting to restart *Oct 7 22:07:56.800: gt96k_mbrd_serial_mode_reg_init:: was DCE, now set to DCE 2811_2# *Oct 7 22:08:26.808: Serial0/2/0: attempting to restart *Oct 7 22:08:26.808: gt96k_mbrd_serial_mode_reg_init:: was DCE, now set to DCE
PC is keeping S0/3/0 port up and sending test data on 9600 or 115200 speeds. R2's S0/3/0 port configured for clock speed 9600 or 115200 respectively. PC serial test programs configured for the same speed.
Looks like is must work with STUN/IP connectivity/routing.
... View more
Created by
WiressFriendly
in Other Network Architecture Subjects
in Other Network Architecture Subjects
10-07-2017
01:35 PM
10-07-2017
01:35 PM
Here is block diagram of my setup. Is it correct? Especially, cables used, port modes (DCE vs DTW), serial ports used? I run config #2 provided by other member by link.
... View more
Created by
WiressFriendly
in Other Network Architecture Subjects
in Other Network Architecture Subjects
10-07-2017
11:29 AM
10-07-2017
11:29 AM
Hi Rick!
Thanks for your reply.
I am not sure about your advice. Because as I see, all peer routing targeted to address of remote router. Or, if I am wrong, can you copy/paste one of two config examples, change what is needed and show me changed data with some highlighting?
And what do you think about local serial port test? How to check that serial port works fine, can accept data, etc.? It would be better to fing some packet counter. To ensure that both ports able to communicate properly and wired properly?
And one important thing. Clocking has nothing on port status. Up/up statuses are easy to get just by changing DTR state to level (e.g. by suppling +7..12VAC to pin #4 on DB9 or pin#20 on DB-25 ). I did this trick and get in console these messages:
*Oct 7 18:52:29.708: %LINK-3-UPDOWN: Interface Serial0/3/0, changed state to down
*Oct 7 18:52:30.708: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/3/0, changed state to down
Do you have ideas how to diag serial port locally or link 2 serial ports on router locally (with no STUN involved)?
Thanks!
... View more
Created by
WiressFriendly
in Other Network Architecture Subjects
in Other Network Architecture Subjects
10-06-2017
01:41 PM
10-06-2017
01:41 PM
Hi Rick!
Thanks for your response and desire to help. Really appreciate it!
I tried 2 different configs, including full Cisco's example with my addressing:
2811_1
2811_2
conf term
conf term
stun peer-name 192.168.168.143
stun peer-name 192.168.168.144
stun protocol-group 9 basic
stun protocol-group 9 basic
stun protocol-group 13 basic
stun protocol-group 13 basic
!
!
interface serial 0/3/0
interface serial 0/3/0
no ip address
no ip address
encapsulation stun
encapsulation stun
stun group 9
stun group 9
stun route all tcp 192.168.1.144
stun route all tcp 192.168.1.143
no shut
no shut
!
!
interface serial 0/2/0
interface serial 0/2/0
encapsulation stun
encapsulation stun
stun group 13
stun group 13
stun route all tcp 192.168.1.144
stun route all tcp 192.168.1.143
no shut
no shut
!
!
interface loopback 0
interface loopback 0
ip address 192.168.168.143 255.255.255.0
ip address 192.168.168.144 255.255.255.0
no shut
no shut
Because loopback interfaces were not able to reach each other, I added these lines:
int lo 0 ip address 192.168.168.143 255.255.255.255 ip route 192.168.168.144 255.255.255.255 192.168.1.144 end
int lo 0 ip address 192.168.168.144 255.255.255.255 ip route 192.168.168.143 255.255.255.255 192.168.1.143 end
After that loopback interfaces become responsible for ping over network. But serial link still isn't working.
After that I tried another config which come from this board marked as solved in that's thread: https://supportforums.cisco.com/t5/wan-routing-and-switching/serial-tunneling/m-p/1876895/thread-id/184901
Here is a version with my addressing:
hostname 2811_1
hostname 2811_2
interface loopback 0
interface loopback 0
desc *** LOOPBACK 0 FOR STUN PEERING ***
desc *** LOOPBACK 0 FOR STUN PEERING ***
ip address 192.168.168.143 255.255.255.255
ip address 192.168.168.144 255.255.255.255
no ip redirect
no ip redirect
no ip directed-broadcast
no ip directed-broadcast
exit
exit
stun peer-name 192.168.168.143
stun peer-name 192.168.168.144
stun protocol-group 100 basic
stun protocol-group 100 basic
!
!
interface Serial0/3/0
interface Serial0/3/0
desc *** LINK TO ROUTER 2811_2 ***
desc *** LINK TO ROUTER 2811_1 ***
ip address 192.168.168.149 255.255.255.252
ip address 192.168.168.150 255.255.255.252
no ip directed-broadcast
no ip directed-broadcast
no shut
no shut
interface Serial0/2/0
interface Serial0/2/0
desc *** STUN LINK - THIS IS THE DCE END ***
desc *** STUN LINK - THIS IS THE DCE END ***
no ip address
no ip address
no ip directed-broadcast
no ip directed-broadcast
encapsulation stun
encapsulation stun
no ip mroute-cache
no ip mroute-cache
clockrate 9600
clockrate 9600
stun group 100
stun group 100
stun route all interface serial 0/3/0 direct
stun route all interface serial 0/3/0 direct
no shut
no shut
interface fast 0/0
interface fast 0/0
desc *** LAN ON ROUTER 2811_1 ***
desc *** LAN ON ROUTER 2811_2 ***
ip address 192.168.1.143 255.255.255.0
ip address 192.168.1.144 255.255.255.0
!
!
ip route 192.168.168.144 255.255.255.255 192.168.168.150 name LOOPBACK-2811_2
ip route 192.168.168.143 255.255.255.255 192.168.168.149 name LOOPBACK-2811_1
ip route 192.168.1.144 255.255.255.255 192.168.168.150 name LAN-2811_2
ip route 192.168.1.143 255.255.255.255 192.168.168.149 name LAN-2811_1
But still no luck :(
About your question. I am using regular PC with hardware COM port. It's 100% working and tested. I run WinSSD program there and use special serial test plug at remote end:
Also I use Cisco DCE cable on PC side and DTE cable on other side (where I connect test plug).
With no routers inserted in the "serial line path" (just PC, serial cables, adapters and plug), all test passes with no issues. Via routers WinSSD shows no connectivity and no sync:
Sending Test Pattern ( 55 - AA hex )
Error - Timeout! Check connector.
PC port settings are standard:
BPS: 9600
Data bits: 8
Parity: None
Stop bits: 1
Flow control: None
With the last config I used serial0/3/0 interfaces at the both routers. Cisco 72-1430-01 (CAB-SS-232FC) DCE cable was used to connect PC. Cisco 72-1431-01 (CAB-SS-232MT) DTE cable was used to connect other side (test plug in my case).
When I connect test plug, I see that local serial interface become active (up status and green LED). When press Port - Open in WinSSD, I see how local serial interface become active too (up status and green LED). So, both serial interfaces up and running before I run any tests.
Any other tests (not WinSSD) also fails and it's predictable, because packet counters in STUN links always shows all zeros in RX/TX lines.
Do you have other ideas after that? I really need them because I am not very good with Cisco.
... View more
Created by
WiressFriendly
in Switching
10-27-2017
10-27-2017
Okay, thanks anyway. Do you have other option ideas for async tunneling?
I don't like UDP idea too m...
Created by
WiressFriendly
in Switching
10-27-2017
10-27-2017
Tried, but same error. How about to configure everyting else first? Like
a few lines in serial inter...
Created by
WiressFriendly
in Switching
10-27-2017
10-27-2017
I run: 2811_1# show ver Cisco IOS Software, 2800 Software
(C2800NM-ADVENTERPRISEK9-M), Version 15.1(...
Created by
WiressFriendly
in Switching
10-27-2017
10-27-2017
Of course I took config example from PDF you provided. I chosen P2P
option, because it fit my applic...
Created by
WiressFriendly
in Switching
10-27-2017
10-27-2017
Hi Georg! Why not? But what encapsulations you see for UDPTN? interface
serial 0/2/0 physical-layer ...
Created by
WiressFriendly
in Switching
10-27-2017
10-27-2017
Hi all! I have created seral port extender over IP based on Cisco 28xx
routers and HWIC-1T + CAB-SS-...
Created by
WiressFriendly
in Other Network Architecture Subjects
10-19-2017
10-19-2017
Dear Paolo! Do you know software which can connect Cisco ISR and provide
a link between virtual COM ...
Created by
WiressFriendly
in Other Network Architecture Subjects
10-19-2017
10-19-2017
Thanks a lot Jim, you're right. Issue resolved.
Created by
WiressFriendly
in Other Network Architecture Subjects
10-15-2017
10-15-2017
So guys, I have some progress. I got link working in pseudowire mode,
but not in STUN. In the both c...
Created by
WiressFriendly
in Other Network Architecture Subjects
10-09-2017
10-09-2017
Rick, Serial ports always up stay up until infinitely until I de-key DTR
or close serial port at PC....
10-08-2017
Hi Alex! Thanks for your config. It's very interesting. But
unfortunately, it' doesn't work for me.2...
Created by
WiressFriendly
in Other Network Architecture Subjects
10-07-2017
10-07-2017
This is what I see on R2 when I debug serial ports. Looks like nothing
bad with S0/3/0, and only S0/...
Created by
WiressFriendly
in Other Network Architecture Subjects
10-07-2017
10-07-2017
Here is block diagram of my setup. Is it correct? Especially, cables
used, port modes (DCE vs DTW), ...
Created by
WiressFriendly
in Other Network Architecture Subjects
10-07-2017
10-07-2017
Hi Rick! Thanks for your reply. I am not sure about your advice. Because
as I see, all peer routing ...
Created by
WiressFriendly
in Other Network Architecture Subjects
10-06-2017
10-06-2017
Hi Rick! Thanks for your response and desire to help. Really appreciate
it! I tried 2 different conf...
Public Statistics
| Date Registered | 09-16-2017 02:33 PM |
| Date Last Visited | 12-24-2017 05:27 PM |
| Total Messages Posted | 21 |
