Cisco Cisco Application Extension Platform for SRE

Ping the Cisco 280x ISR side of the ISE1/0 interface (router side): 

bash-2.05b# ping 192.168.2.1 

PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.

64 bytes from 192.168.2.1: icmp_seq=1 ttl=255 time=2.31 ms

64 bytes from 192.168.2.1: icmp_seq=2 ttl=255 time=0.822 ms

64 bytes from 192.168.2.1: icmp_seq=3 ttl=255 time=0.799 ms

[2]+  Stopped  ping 192.168.2.1

bash-2.05b# 

Ping your FTP server, where your Cisco AXP package files are located:

bash-2.05b# ping 192.168.1.1 

PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.

64 bytes from 192.168.1.1: icmp_seq=1 ttl=254 time=3.59 ms

64 bytes from 192.168.1.1: icmp_seq=2 ttl=254 time=1.68 ms

[1]+  Stopped 

ping 192.168.1.1

bash-2.05b# 

The ping in this step proves that your application environment has IP network connectivity through the 
Cisco 280x ISR to your FTP server's interface.

Because your prompt is a standard Linux shell prompt, it appears as if you are logged into a Linux 
machine with your own root (/) directory. 

Begin working with your application and see your working vserver environment, network connectivity, 
and general Linux environment.

To exit the Linux shell environment in your virtual instance, type the following:

bash-2.05b# exit 

se-Module(exec-tcptrace)> exit 

se-Module> exit <enter>

2800_w_axp# 

You are now back to the Cisco 280x ISR prompt. 

For details on developing applications, see the 

For details on configuring the router and application service module, see the 

.

If you want to have a consistent set of time stamps required for logs and development authorization 
between the Cisco 280x ISR and the Cisco AXP service module, you must configure the AXP service 
module to receive its NTP clock source from the router. See the “Configuring the NTP Server Source” 
section in the 

Cisco AXP User Guide.