RE: 3640 SNAT cannot use TCP to talk to peers, not compatible

From: Mike Kraus \(mikraus\) (mikraus@cisco.com)
Date: Sat Jul 07 2007 - 17:15:42 ART


Here's the history on this, CSCek29860 was issued because there were
some software-induced crashes in the way the SNAT previously functioned.
As the code was rewritten, TCP support was removed. It was found that
UDP provided a more scalable solution, and there was no real reason to
provide two different methods of transport. So, as a result, it is now
UDP only.

As mentioned, in the lab, you aren't going to run into this as an issue
(since all the routers should be at the same IOS version, so would have
the same capabilities). In the real world, you're right, you'd want to
go UDP to get the best results, and have backwards compatibility.

This was fixed in:
12.4(10.1)T
12.4(9.18)M
12.4(9)T1
12.4(8a)M
12.4(7b)M

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Antonio Soares
Sent: Saturday, July 07, 2007 2:47 PM
To: johngibson1541@yahoo.com; ccielab@groupstudy.com
Subject: RE: 3640 SNAT cannot use TCP to talk to peers, not compatible
with older 12.3 routers

I got the same error:
++++++++++++++++++++++++++++++++
R6#sh ver | inc IOS
Cisco IOS Software, 3700 Software (C3725-ADVENTERPRISEK9-M), Version
12.4(12), RELEASE SOFTWARE (fc1) R6#
++++++++++++++++++++++++++++++++
R6(config)#ip nat stateful ?
  id Specify Stateful NAT ID unique per router

R6(config)#ip nat stateful i
R6(config)#ip nat stateful id ?
  <1-2147483647> Stateful NAT id number

R6(config)#ip nat stateful id 1 ?
  <cr>

R6(config)#ip nat stateful id 1
R6(config-ipnat-snat)#?
IP Stateful NAT configuration commands:
  backup Configure backup's ip address
  exit Exit from IP Stateful NAT primary mode
  no Negate or set default values of a command
  primary Configure primary's ip address
  redundancy Define redundancy group name

R6(config-ipnat-snat)#
*Jul 7 18:10:13.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface
NVI0, changed state to up R6(config-ipnat-snat)#re
R6(config-ipnat-snat)#redundancy HSRP R6(config-ipnat-snat-red)#?
IP Stateful NAT Redundancy mode configuration commands:
  as-queuing Disable asymmetric process for this redundancy group
  exit Exit from IP Stateful NAT Redundancy config mode
  mapping-id Configure mapping-id for this redundancy group
  no Negate or set default values of a command
  protocol Select transport protocol for this redundancy group

R6(config-ipnat-snat-red)#pro
R6(config-ipnat-snat-red)#protocol ?
  tcp Transmission Control Protocol
  udp User Datagram Protocol

R6(config-ipnat-snat-red)#protocol t
R6(config-ipnat-snat-red)#protocol tcp ?
  <cr>

R6(config-ipnat-snat-red)#protocol tcp
TCP is deprecated, switching to UDP protocol by default
R6(config-ipnat-snat-red)#
++++++++++++++++++++++++++++++++
So the default is now UDP instead of TCP.
In the lab we will have 12.4 so this won't be an issue. I think :)
++++++++++++++++++++++++++++++++

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
johngibson1541@yahoo.com
Sent: sabado, 7 de Julho de 2007 20:18
To: ccielab@groupstudy.com
Subject: 3640 SNAT cannot use TCP to talk to peers, not compatible with
older 12.3 routers

Appreciate any response,

my 3640 is c3640-ik9o3s-mz.124-8a.bin

the 12.3 router is 2600, which doesn't have choices with the transport
layer.

my 3640 refuses to use TCP:

Rack2R6(config-ipnat-snat)#redundancy NAT_2.2.35.3
Rack2R6(config-ipnat-snat-red)#protocol ?
  tcp Transmission Control Protocol
  udp User Datagram Protocol

Rack2R6(config-ipnat-snat-red)#protocol tcp TCP is deprecated, switching
to UDP protocol by default Rack2R6(config-ipnat-snat-red)#^Z Rack2R6#wr
*Mar 1 08:32:52.295: %SYS-5-CONFIG_I: Configured from console by
console Rack2R6#show run | be nat Stat ip nat Stateful id 1
     redundancy NAT_2.2.35.3
         mapping-id 10
         interface Ethernet1/0.356
         protocol udp
...

John



This archive was generated by hypermail 2.1.4 : Sat Aug 18 2007 - 08:17:40 ART