I have the following configuration on the Cisco IOS
 
!
interface Integrated-Service-Engine1/0
 ip unnumbered FastEthernet0/1
 ip virtual-reassembly
 service-module ip address 192.168.15.156 255.255.255.0
 service-module ip default-gateway 192.168.15.155
 no keepalive
end
 
The AXP has the following configuraiton for the Eth0 and Eth1
 
interface eth0
 ip address 192.168.15.156 255.255.255.0
 exit

interface eth1
 ip address 155.56.132.138 255.255.255.248
 exit
 
show ip route on the AXP shows the following:
se-10-10-10-100# sh ip route
Main Routing Table:
           DEST            GATE                      MASK IFACE
   192.168.15.0         0.0.0.0                  255.255.255.0 eth0 
        0.0.0.0         192.168.15.155         0.0.0.0 eth0 
 155.56.132.138         0.0.0.0               255.255.255.248 eth1 
 
I need the AXP to point to the default-gateway of 155.56.132.142, however the Cisco AXP does not allow that, since the default-gateway can only be defined on the Cisco IOS interface Integrated-Service-Engine1/0.
 
Is there a way to define a separate default-gateway for the outgoing traffic ?
 
se-10-10-10-100# conf t
Enter configuration commands, one per line.  End with CNTL/Z.
se-10-10-10-100(config)# ip route 0.0.0.0 0.0.0.0  155.56.132.142
Route already exists
se-10-10-10-100(config)# no ip route 0.0.0.0 0.0.0.0 192.168.15.155
The default route cannot be removed
se-10-10-10-100(config)#
Eglin#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
Eglin(config)#int integrated-Service-Engine 1/0
Eglin(config-if)#service-module ip default-gateway  155.56.132.142
 Default gateway is not reachable for service-module Integrated-Service-Engine1/0

Eglin(config-if)#
 
It seems like the IOS cannot be used to set the eth1 for default-gateway and only eth0 can be used as the default-gateway. This reflects on the application and application does not have the permissions to define any routes.
 
Any ideas ?
 

Yes, I have the same issue. The need is as the following.
I use the AXP as a remote network monitoring system. I want it collect the NM data through the eth0 and I will connect the eth1 to the DMZ. So the NAT let me access the AXP from Internet. So I should use the eth1 as the default gateway interface. The topo as the following.

|-------------|
|   Internet   |
|-------------|

  |

|-------------|
|     FW       |
|-------------|

                                                  DMZ  |
  |eth1
|-------------|
|     AXP      |
|-------------|
  eth0  |
 |

|-------------|
| Internal Net|
|-------------|
If it can support the default-gateway on eth1 that't great. If it can not I can only use one more router ethernet interface as the unnumbered interface for AXP to connect NAT while the GE on the AXP is not used.
I think this kind of need is there in many customer environments. Can Cisco support it in the future?

Thank you! Yes I will send it as an enhancement request.