For those of you which perform some Aurora Tango tests (BERT, RFC 2544) you may know that a couple of these testers are really expensive ! The principle of these test is to place a tester in loopback and another is test mode. By means of this, you are able to qualify an Ethernet link (direct, Q-in-Q, VPLS, Xconnect).
During my readings of mailing-lists such as cisco-nsp or others, someone posts an URL to a really awesome Linux program : etherate. With modern CPU platform you are able to supply a throughput until 1G, and this program give you the possibility to test your L2 circuits.
You can do some tests by using it such as :
root@Loop_Host# etherate -r
To give some features :
root@pluton:~/COMPILE/Etherate-master# ./etherate -h Usage info; [Mode] [Destination] [Source] [Options] [Other] [Mode] By default run in transmit mode, not receive -r Change to receive (listening) mode. [Destination] -d Without this we default to 00:00:5E:00:00:02 as the TX host and :01 as the RX host. Specify a custom desctination MAC address, -d 11:22:33:44:55:66 [Source] Specify a custom source MAC address, -s 11:22:33:44:55:66 -i Set interface by name. Without this option we guess which interface to use. -I Set interface by index. Without this option we guess which interface to use. -l List interface indexes (then quit) for use with -i option. -s Without this we default to 00:00:5E:00:00:01 as the TX host and :02 as the RX host. [Options] -a Ack mode, have the receiver ack each frame during the test (This will significantly reduce the speed of the test). -b Number of bytes to send, default is 0, default behaviour is to wait for duration. Only one of -t, -c or -b can be used, both override -t, -b overrides -c. -c Number of frames to send, default is 0, default behaviour is to wait for duration. -e Set a custom ethertype value the default is 0x0800 (IPv4). -f Frame payload size in bytes, default is 1500 (1514 bytes is the expected size on the wire with headers). -m Max bytes per/second to send, -m 125000 (1Mbps). -t Transmition duration, integer in seconds, default is 30. [Other] -v Add an 802.1q VLAN tag. By default none is in the header. If using a PCP value with -p a default VLAN of 0 is added. -p Add an 802.1p PCP value from 1 to 7 using options -p 1 to -p 7. If more than one value is given, the highest is used. Default is 0 if none specified. (If no 802.1q tag is set the VLAN 0 will be used). -q Add an outter Q-in-Q tag. If used without -v, 1 is used for the inner VLAN ID. #NOT IMPLEMENTED YET# -o Add an 802.1p PCP value to the outer Q-in-Q VLAN tag. If no PCP value is specified and a Q-in-Q VLAN ID is, 0 will be used. If no outer Q-in-Q VLAN ID is supplied this option is ignored. -o 1 to -o 7 like the -p option above. #NOT IMPLEMENTED YET# -x Display examples. #NOT IMPLEMENTED YET# -V|--version Display version -h|--help Display this help text root@pluton:~/COMPILE/Etherate-master#
I really hope and try to help so that this project goes to his end. It could be really great to have L2 tests as this one as we have with bwping and iperf on L3/L4 layer of OSI model.
No more to say : http://www.gns3.com
For those of you which follow BSD branches :
Have fun with this great software
To beeing keep updated : this new routers seems really well : IOS XE (IOSd over Linux, virtualization, …).
You can learn more about them on : http://lostintransit.se/2014/10/04/cisco-adds-new-routers-in-the-isr-4000-family/
Have fun to read this great article…
It was holidays with family for two weeks. It was really peaceful.
Come back to CCIE studies and some blog posts begin of september.
Hope to see you soon on this blog.
It is been a while that I read some papers about EVC, flexible matching, … But I have not found a good paper explaining EVC and a way to understanding well except to cisco configuration guide.
This figure is exactly what I searched for. This example is simple but enough to understand well how it works.
My misunderstanding was about « ingress » and « symmetric » : I didn’t understand, but now with the figure that it is clear that :
When a frame comes from the xconnect :
You can ask me : « Ok this is really complicated your configuration, why don’t you use xxxx » ?
Where xxx is :
int gi 0/2 switchport trunk encapsulation dot1q switchport trunk allow vlan 10 switchport mode trunk int vl 10 xconnect 192.168.1.1 33 encapsulation mpls
I will reply : « Have you declare your vlan 100 on your switch ? What does it involve for the scalability ? »
=> Yes, you understand well : you are limited by the number of vlans.
=> With EVC : the « encapsulation dot1q 10″ is local to the port. So no limitation.
=> Yes it is really great !!!!!
I urge you to read these papers :
BFD is a mecanism which give you access to a fast switchover for IGP, EBGP, … It is a RFC protocol : RFC5880.
BFD is a UDP protocol.
BFD is in use on a segment, when a protocol needs it (such as : OSPF). It is configured by interface and called in protocol configuration.
When BFD detect a failure it informs upper protocols and helps to make a better / quick convergence.
You can configure BFD like :
Then you enable it on IGP configuration :
router ospf 1 network 0.0.0.0 255.255.255.255 area 0 bfd all-interfaces
BFD initialization works with a 4-state’s automate. These states are :
ADMIN-DOWN : as it says the system want to hold the session DOWN by an administrative point of view : « I want to keep this session DOWN, so calm down and shut up as long as I say! »
DOWN : says that the session has just been created, administratively or operationnaly it maintains the state to DOWN until we receive a BFD DOWN control datagram from the other side : « We are agree that the session is DOWN, we can go on and try to initialize it! »
INIT : We come from DOWN state. Both systems are communicating. Until we receive an INIT or UP, we keep in INIT and send BFD INIT datagram.
UP : Ok both sides are agreed on INIT/UP we finalize the session and go together to UP states. We are UP until we detect it fails or ADMIN DOWN state is said to me ! So at TX interval we send Control packet with UP state until we detect a problem or been administratively set to DOWN.
BFD is aware of different authentication methods such as simple passowrd, MD5, SHA1.
Timers negotiation :
Timers are continually negotiated during the session by means of sending BFD Control datagram where :
So each side can adjust their timers and this at any time of the session life.
To identify between multiple sessions between two systems, a discriminator (A unique ID). When we receive a BFD datagram with my discriminator, I know it is for __this session and I can compute it correctly.
Echo function :
This function is a way to detect and transmit packets/test forwarding plane : We send BFD echo packet with :
We can use Echo function only when BFD Control session is UP. After this, we can slow down sending BFD Control packet and only base failure detection by means of Echo function. We detect failure by using number of failure on a row as BFD Control Packets.
We can use BFD without this function only with BFD Control.
R1 (conf-if)# no bfd echo
Lab test :
You can find a cloudshark pcap trace here : https://www.cloudshark.org/captures/94617b9dc969
It consists of an BFD session initialization (you can find in the pcap by adding the filter : ‘bfd’). Then an outage has been produced by removing vlan on SW1 on the trunk (frame 249 : « Diag : Echo function failed »). And then allow it again on the trunk to reform the BFD session).
R1#show bfd neighbors details IPv4 Sessions NeighAddr LD/RD RH/RS State Int 188.8.131.52 1/1 Up Up Et0/1.13 Session state is UP and using echo function with 500 ms interval. Session Host: Software OurAddr: 184.108.40.206 Handle: 1 Local Diag: 0, Demand mode: 0, Poll bit: 0 MinTxInt: 1000000, MinRxInt: 1000000, Multiplier: 3 Received MinRxInt: 1000000, Received Multiplier: 3 Holddown (hits): 0(0), Hello (hits): 1000(30) Rx Count: 31, Rx Interval (ms) min/max/avg: 1/1000/857 last: 681 ms ago Tx Count: 32, Tx Interval (ms) min/max/avg: 1/999/840 last: 363 ms ago Elapsed time watermarks: 0 0 (last: 0) Registered protocols: OSPF Uptime: 00:00:26 Last packet: Version: 1 - Diagnostic: 0 State bit: Up - Demand bit: 0 Poll bit: 0 - Final bit: 0 C bit: 0 Multiplier: 3 - Length: 24 My Discr.: 1 - Your Discr.: 1 Min tx interval: 1000000 - Min rx interval: 1000000 Min Echo interval: 500000 R1#
Or on ASR9K or CRS plateform :
show bfd session
Hope this help,
Surfing the web I have found this app for smartphone : networktools he.net.
It is really great
To understand well path through new chassis such as ASR9K, you could see this video (from Cisco Live 2014) and this blog post written by Ivan Pepelnjak, CCIE#1354. You could make a join between VOQ for QOS and LPTS/VOIP for ASR9K.