Network Performance, WAN Optimization

For end to end physcial links:
1. Delay
2. Jitter
3. Loss

For TCP traffic:
1. TCP RTT (Round Trip Time)
2. TCP SRT (Server Response Time)
3. TCP Re-transmission behavior

Tools

1. Cisco QoS + IP SLA 

http://www.cisco.com/en/US/technologies/tk648/tk362/tk920/technologies_white_paper09186a00802d5efe.html

http://www.cisco.com/en/US/docs/ios/12_4/ip_sla/configuration/guide/hsjitter.html#wp1054785

Riverbed, Bluecoat, Ipanema

Reference for configure Cisco 3G card

Some reference about configure Cisco wireless cards:

Understanding and Configuring a HWIC-3G-GSM
http://routing-bits.com/2010/05/12/hwic-3g-gsm/

Configuring 3G Wireless WAN on Modular and Fixed ISRs (HWIC-3G-GSM, HWIC-3G-HSPA, PCEX-3G-HSPA-x)

http://www.cisco.com/en/US/docs/routers/access/1800/1861/software/feature/guide/mrwlsgsm.html#wp1323053

Configuring Dial Backup Using Dialer Watch

http://www.cisco.com/en/US/docs/ios/12_2/dial/configuration/guide/dafbakdw.html

Cisco firmware

http://www.cisco.com/cisco/software/release.html?mdfid=281295483&flowid=7001&softwareid=281285585&release=H1_1_9_3&rellifecycle=&relind=AVAILABLE&reltype=all

Cisco 3G Wireless WAN (GPRS/EDGE/UMTS/HSDPA) High-Speed Wan Interface Card

archive tar /xtract source-url destination-url

microcode reload cellular pa-bay slot gsm modem-provision

 
http://www.cisco.com/en/US/docs/routers/access/1800/1861/software/feature/guide/mrwlsgsm.html

 

PING with ToS

ICMP echo messages are sent to a remote host and are returned in an echo-reply response. The primary use for these messages is to check the availability of the target machine.

1. Host A creates an ICMP echo datagram, using host A's address as the source, and host B's address as the destination.
2. The ICMP echo datagram is transmitted via the network to the destination (host B).
3. The destination system (host B) copies the echo information into a new echo-reply message datagram.
4. The destination system (host B) destroys the original ICMP echo message.
5. The destination machine (host B) now becomes the source of a new echo-reply datagram. Host B places it's own address in the source address field of the IP header, and host A's address in the destination field of the IP header.
6. The datagram is transmitted to the network and is routed to host A.

For this very simple back to back topology, the ToS value has been copied to the new IP diagram (echo-reply). However, this is not always the case especially there are networks between them. The best way is to test your ruler before use them.

R1 ------- Serial ------- R2

.1                                   .2

R1-PE1#ping ip

Target IP address: 1.1.1.2

Repeat count [5]: 

Datagram size [100]: 

Timeout in seconds [2]: 

Extended commands [n]: y

Source address or interface: 

Type of service [0]: 48

Set DF bit in IP header? [no]: 

Validate reply data? [no]: 

Data pattern [0xABCD]: 

Loose, Strict, Record, Timestamp, Verbose[none]: 

Sweep range of sizes [n]: 

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 1.1.1.2, timeout is 2 seconds:

!!!!!

R2 Debug (receives echo-request, and sends reply)

*Oct 10 13:42:54.871: IP: s=1.1.1.1 (Serial1/1), d=1.1.1.2, len 100, stop process pak for forus packet

*Oct 10 13:42:54.871:     ICMP type=8, code=0

*Oct 10 13:42:54.871: ICMP: echo reply sent, src 1.1.1.2, dst 1.1.1.1, topology BASE, dscp 12 topoid 0

R1 Debug

*Oct 10 13:42:54.868: IP: s=1.1.1.2 (Serial1/1), d=1.1.1.1, len 100, stop process pak for forus packet

*Oct 10 13:42:54.868:     ICMP type=0, code=0

*Oct 10 13:42:54.868: ICMP: echo reply rcvd, src 1.1.1.2, dst 1.1.1.1, topology BASE, dscp 12 topoid 0

Ref:
http://www.inetdaemon.com/tutorials/internet/icmp/echo.shtml
http://en.wikipedia.org/wiki/Ping
http://www.inetdaemon.com/tools/ping/how_ping_works.shtml
https://supportforums.cisco.com/thread/2090992

ISDN

Configuring Dial Backup with Dialer Profiles

Configure a Dialer Interface

To configure the dialer interface that will be used as an intermediary between a physical interface that will function as backup interface and the interfaces that will use the backup, use the following commands beginning in global configuration mode:

Step	Command	Purpose
1	interface dialer number	Create a dialer interface.
2	ip unnumbered loopback0	Specify IP unnumbered loopback.
3	encapsulation ppp	Specify PPP encapsulation.
4	dialer remote-name username	Specify the remote router's CHAP authentication name.
5	dialer string dial-string	Specify the remote destination to call.
6	dialer pool number	Specify the dialing pool to use for calls to this destination.
7	dialer-group group-number	Assign the dialer interface to a dialer group.

Configure a Physical Interface to Function as Backup

To configure the physical interface that is to function as backup, use the following commands beginning in global configuration mode:

Step	Command	Purpose
1	interface type number	Specify the interface.
2	encapsulation ppp	Specify PPP encapsulation.
3	dialer pool-member number	Make the interface a member of the dialing pool that the dialer interface will use; make sure the number arguments have the same value.
4	ppp authentication chap	Specify CHAP authentication.

Configure Interfaces to Use a Backup Interface

To configure one or more interfaces to use a backup interface, use the following commands beginning in global configuration mode:

Step	Command	Purpose
1	interface type number	Specify the interface to be backed up.
2	ip unnumbered loopback0	Specify IP unnumbered loopback.
3	backup interface dialer number	Specify the backup interface.
4	backup delay enable-delay disable-delay	Specify delay between the physical interface going down and the backup being enabled, and between the physical interface coming back up and the backup being disabled.

 

Dialer Profile for ISDN BRI Backing Up Two Leased Lines Example

The following example shows the configuration of a site that backs up two leased lines using one BRI. Two dialer interfaces are defined. Each serial (leased line) interface is configured to use one of the dialer interfaces as a backup. Both of the dialer interfaces use dialer pool 1, which has physical interface BRI 0 as a member. Thus, physical interface BRI 0 can back up two different serial interfaces and can make calls to two different sites.

interface dialer0

 ip unnumbered loopback0

 encapsulation ppp

 dialer remote-name Remote0

 dialer pool 1

 dialer string 5551212

 dialer-group 1

interface dialer1

 ip unnumbered loopback0

 encapsulation ppp

 dialer remote-name Remote1

 dialer pool 1

 dialer string 5551234

 dialer-group 1

interface bri 0

 encapsulation PPP

 dialer pool-member 1

 ppp authentication chap

interface serial 0

 ip unnumbered loopback0

 backup interface dialer 0

 backup delay 5 10

interface serial 1

 ip unnumbered loopback0

 backup interface dialer1

 backup delay 5 10

Ref:

http://www.cisco.com/en/US/docs/ios/12_0/dial/configuration/guide/dcdbakdp.html 

Bidirectional Forwarding Detection

BFD is a detection protocol designed to provide fast forwarding path failure detection times for all media types, encapsulations, topologies, and routing protocols. In addition to fast forwarding path failure detection, BFD provides a consistent failure detection method for network administrators. Because the network administrator can use BFD to detect forwarding path failures at a uniform rate, rather than the variable rates for different routing protocol hello mechanisms, network profiling and planning will be easier, and reconvergence time will be consistent and predictable. 

A maximum 100 sessions per line card are supported for the distributed Cisco 12000 series Internet router. The minimum hello interval is 50 ms with up to three Max retries for a BFD control packet to be received from a remote system before a session with a neighbor is declared down. 

Configuring BFD Support for BGP 

SUMMARY STEPS

interface FastEthernet 0/1

 ip address 1.1.1.1 255.255.255.0

 bfd interval 50 min_rx 50 multiplier 3

1. enable

2. configure terminal

3. router bgp as-tag

4. neighbor ip-address fall-over bfd

5. end

6. show bfd neighbors [details]

7. show ip bgp neighbor 

Configuring BFD Support for IS-IS for One or More Interfaces 

SUMMARY STEPS

1. enable

2. configure terminal

3. interface type number

4. isis bfd [disable]

5. end

6. show bfd neighbors [details]

7. show clns interface 

Ref:

http://www.cisco.com/en/US/docs/ios/12_0s/feature/guide/fs_bfd.html#wp1153100 

http://www.cisco.com/en/US/docs/ios-xml/ios/iproute_bfd/configuration/12-2sr/Bidirectional_Forwarding_Detection.html#GUID-5EF281D7-048D-42C6-81F8-D50524CE24AD

 

QinQ vlan rewrite

1. ES port on Cisco 3750Metro

interface FastEthernet1/0/1

 description ***** To Customer A inner VLAN 10 *****

 switchport access vlan 2001             ! This will be the outer VLAN tag

 switchport mode dot1q-tunnel

!

interface FastEthernet1/0/2

description ***** To  Customer B inner VLAN 20 *****

 switchport access vlan 2002             ! This will be the outer VLAN tag

 switchport mode dot1q-tunnel

!

interface GigabitEthernet1/1/2

 description **** upstream link ****

 switchport trunk allowed vlan 2001-2024,

 switchport mode trunk

 switchport vlan mapping internal dot1q-tunnel 2001 10 external dot1q-tunnel 2200 10

 switchport vlan mapping internal dot1q-tunnel 2002 20 external dot1q-tunnel 2200 20

!

2. Flexible VLAN Tag Rewrite.(ES/ES+ card on 7600)


Ref: http://ccie-in-3-months.blogspot.com/2009/06/evc-flexible-vlan-tag-rewrite.html


3. Configuring the VLAN ID Rewrite Feature for the Cisco 12000 Series Routers


PE1

interface GigabitEthernet0/0.2

encapsulation dot1Q 2

no ip directed-broadcast

no cdp enable

xconnect 5.5.5.5 2 encapsulation mpls

remote circuit id 3

PE2

interface GigabitEthernet3/0.2

 encapsulation dot1Q 3

 no ip directed-broadcast

 no cdp enable

 xconnect 3.3.3.3 2 encapsulation mpls

  remote circuit id 2

Ref: 

http://www.cisco.com/en/US/docs/ios/12_0s/feature/guide/atom25s.html#wp1279134 

http://www.cisco.com/en/US/docs/ios/12_0s/feature/guide/qinq.html#wp1043332

http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_any_transport.html#wp1047047 

Configuring SPAN and RSPAN

You can analyze network traffic passing through ports or VLANs by using SPAN to send a copy of the traffic to another port on the switch that has been connected to a SwitchProbe device or other Remote Monitoring (RMON) probe or security device. SPAN mirrors received or transmitted (or both) traffic on a source port and received traffic on one or more source ports or source VLANs, to a destination port for analysis. 

Creating a SPAN Session and Specifying Ports to Monitor

This example shows how to set up a SPAN session, session 1, for monitoring source port traffic to a destination port. First, any existing SPAN configuration for session 1 is cleared, and then bidirectional traffic is mirrored from source port 1 to destination port 10.

Switch(config)# no monitor session 1

Switch(config)# monitor session 1 source interface fastEthernet0/1

Switch(config)# monitor session 1 destination interface fastEthernet0/10 
encapsulation dot1q

Switch(config)# end 

Configuring RSPAN 

Creating an RSPAN Session 

This example shows how to clear any existing RSPAN configuration for session 1, configure RSPAN session 1 to monitor multiple source interfaces, and configure the destination RSPAN VLAN and the reflector-port.

Switch(config)# no monitor session 1

Switch(config)# monitor session 1 source interface fastEthernet0/10 tx

Switch(config)# monitor session 1 source interface fastEthernet0/2 rx

Switch(config)# monitor session 1 source interface fastEthernet0/3 rx

Switch(config)# monitor session 1 source interface port-channel 102 rx

Switch(config)# monitor session 1 destination remote vlan 901 reflector-port 
fastEthernet0/1

Switch(config)# end

 

Creating an RSPAN Destination Session 

This example shows how to configure VLAN 901 as the source remote VLAN and port 5 as the destination interface:

Switch(config)# monitor session 1 source remote vlan 901

Switch(config)# monitor session 1 destination interface fastEthernet0/5

Switch(config)# end

 

Creating an RSPAN Destination Session and Enabling Ingress Traffic 

This example shows how to configure VLAN 901 as the source remote VLAN and how to configure the destination port for ingress traffic on VLAN 5 by using a security device that supports 802.1Q encapsulation:

Switch(config)# monitor session 1 source remote vlan 901

Switch(config)# monitor session 1 destination interface fastEthernet0/5 ingress vlan 5

Switch(config)# end

 

Ref: http://www.cisco.com/en/US/docs/switches/lan/catalyst3550/software/release/12.1_13_ea1/configuration/guide/swspan.html#wp1036816