Friday, August 14, 2009

WVIC 1MFT-E1 back-to-back for frame relay labs

Hi all,
after my old post "WVIC 1MFT-E1 back-to-back" I've tryed to configure a back-to-back connection between two MFT-E1 in order to use it to emulate a serial connection for frame relay studies.

Obviously, you don't need crossover serial cables, but a crossover Pri cable (RJ-45) as described in the old post ("WVIC 1MFT-E1 back-to-back")
Quick refresh of pins:
1 RX Ring - -> 4 TX Ring -
2 RX Tip + -> 5 TX Tip +
4 TX Ring - -> 1 RX Ring -
5 TX Tip + -> 2 RX Tip +

Well, it was really hard (at least for me) to find how to configure it!

First, let's look on the default config of the MFT E1 controller:


R1#sh run | section controller
controller E1 1/0/0

R1#sh controller e1 1/0/0
E1 1/0/0 is up.
Applique type is Channelized E1 - balanced
No alarms detected.
alarm-trigger is not set
Version info Firmware: 20071129, FPGA: 20, spm_count = 0
Framing is CRC4, Line Code is HDB3, Clock Source is Line.
Data in current interval (89 seconds elapsed):
4 Line Code Violations, 3 Path Code Violations
23 Slip Secs, 0 Fr Loss Secs, 3 Line Err Secs, 0 Degraded Mins
25 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs

R1#show diag 1
Slot 1:
[...NM-HDV installed...]

WIC Slot 0:
E1 (1 Port) Multi-Flex Trunk WAN Daughter Card
Hardware revision 1.0 Board revision B0
Serial number 00000000 Part number 800-04475-03
FRU Part Number VWIC-1MFT-E1=

[....]

HDV firmware: Compiled Fri 19-Nov-04 14:23 by michen
HDV memory size 524280 heap free 193977


then, the necessary steps to configure it as a single E1 DATA connection are:
(this config has to be applied on BOTH sides)
R1#conf t
Enter configuration commands, one per line. End with CNTL/Z.
R1(config)#controller
R1(config)#controller e1 1/0/0
R1(config-controller)#framing crc4 !-- optional, crc4 it's already the default
R1(config-controller)#linecode hdb3 !-- optional, hdb3 it's default too
R1(config-controller)#clock source internal
R1(config-controller)#channel-group 1 timeslots 1-31 speed 64
*Aug 14 19:16:16.119: %CONTROLLER-5-UPDOWN: Controller E1 1/0/0, changed state to up
*Aug 14 19:16:18.119: %LINK-3-UPDOWN: Interface Serial1/0/0:1, changed state to up
*Aug 14 19:16:19.123: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0/0:1, changed state to up

R1#sh run | section controller
controller E1 1/0/0
clock source internal
channel-group 1 timeslots 1-31

R1#sh controllers e1
E1 1/0/0 is up.
Applique type is Channelized E1 - balanced
No alarms detected.
alarm-trigger is not set
Version info Firmware: 20071129, FPGA: 20, spm_count = 0
Framing is CRC4, Line Code is HDB3, Clock Source is Internal.
Data in current interval (619 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
81 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
81 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Total Data (last 4 15 minute intervals):
5 Line Code Violations, 3294 Path Code Violations,
908 Slip Secs, 2 Fr Loss Secs, 3 Line Err Secs, 0 Degraded Mins,
909 Errored Secs, 0 Bursty Err Secs, 2 Severely Err Secs, 24 Unavail Secs

R1#sh run interface serial 1/0/0:1
Building configuration...

Current configuration : 46 bytes
!
interface Serial1/0/0:1
no ip address
end

R1#


As you can see, an interface Serial is created, then, you can use it as a traditional serial interface, bandwidth is 31 channels x 64k = 1984Kbps.

In addition, depending on how many NVRAM is allocated to your HDV (see show diag under "HDV memory size") you can create multiple serial interfaces by reducing the number of channels on channel-group.

eg:

R1#conf t
Enter configuration commands, one per line. End with CNTL/Z.
R1(config)#controller e1 1/0/0
R1(config-controller)#no channel-group 1 timeslots 1-31
% Not all config may be removed and may reappear after reactivating the logical-interface/sub-interfaces
R1(config-controller)#channel-group 1 timeslots 1-8 speed 64
*Aug 14 19:35:29.475: %LINK-3-UPDOWN: Interface Serial1/0/0:1, changed state to up
*Aug 14 19:35:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0/0:1, changed state to up
R1(config-controller)#channel-group 2 timeslots 9-16 speed 64
R1(config-controller)#
*Aug 14 19:35:41.303: %LINK-3-UPDOWN: Interface Serial1/0/0:2, changed state to up
*Aug 14 19:35:42.303: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0/0:2, changed state to up

R1#sh run int serial 1/0/0:1 | beg int
interface Serial1/0/0:1
no ip address
end

R1#sh run int serial 1/0/0:2 | beg int
interface Serial1/0/0:2
no ip address
end

R1#sh diag 1 | beg WIC
WIC Slot 0:
E1 (1 Port) Multi-Flex Trunk WAN Daughter Card
Hardware revision 1.0 Board revision B0
Serial number 00000000 Part number 800-04475-03
FRU Part Number VWIC-1MFT-E1=

[...]

HDV firmware: Compiled Fri 19-Nov-04 14:23 by michen
HDV memory size 524280 heap free 625

R1#


note the "HDV memory size 524280 heap free 625", displayed if the MFT is installed into a NM-HDV module, doesn't allow you to create more channel-groups (unless you have channels 17-31 unallocated) because your HDV free memory is insufficent.... it you try this, you'll receive an error message like:

R1#conf t
Enter configuration commands, one per line. End with CNTL/Z.
R1(config)#controller e1 1/0/0
R1(config-controller)#channel-group 3 timeslots 17-31 speed 64
Channel setup failed!!! s:t:c 1:0:3
HDV slot 1 DRAM size 524280 free 625 need 124992

%Insufficient resources to create channel group
R1(config-controller)#



If the MFT-E1 is installed on a HVic standard slot, the error is similar:


R2(config)#controller e1 0/2/0
R2(config-controller)#channel-group 1 timeslots 1-8 speed 64
*Aug 14 19:37:25.797: %LINK-3-UPDOWN: Interface Serial0/2/0:1, changed state to up
*Aug 14 19:37:26.797: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/2/0:1, changed state to up
R2(config-controller)#channel-group 2 timeslots 9-16 speed 64
*Aug 14 19:37:32.937: %LINK-3-UPDOWN: Interface Serial0/2/0:2, changed state to up
*Aug 14 19:37:33.937: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/2/0:2, changed state to up
R2(config-controller)#channel-group 3 timeslots 17-24 speed 64
%Channel-groups per port limit exceeded
%Insufficient resources to create channel group


Now we have two serial interfaces on each router, we can use them for frame relay, even with the "trick" of creating two vrfs on one router, to simulate a point-to-point topology, with the router without vrfs acting as fr switch.

eg:
R1#sh run
[...]
!-- only relevant parts displayed...
!
ip vrf one
rd 1:1
!
ip vrf two
rd 2:2
!
controller E1 1/0/0
clock source internal
channel-group 1 timeslots 1-8
channel-group 2 timeslots 9-16
!
interface Serial1/0/0:1
ip vrf forwarding one
ip address 172.16.0.1 255.255.255.0
encapsulation frame-relay
frame-relay interface-dlci 102
!
interface Serial1/0/0:2
ip vrf forwarding two
ip address 172.16.0.2 255.255.255.0
encapsulation frame-relay
frame-relay interface-dlci 201
!
!
!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!-- on the other side, only relevant parts
!
R2#sh run
!
frame-relay switching
!
controller E1 1/0/0
clock source internal
channel-group 1 timeslots 1-8
channel-group 2 timeslots 9-16
!
!
interface Serial1/0/0:1
no ip address
encapsulation frame-relay
no frame-relay inverse-arp
frame-relay intf-type dce
clock rate 512000
frame-relay route 102 interface Serial1/0/0:2 201
!
interface Serial1/0/0:2
no ip address
encapsulation frame-relay
no frame-relay inverse-arp
frame-relay intf-type dce
clock rate 512000
frame-relay route 201 interface Serial1/0/0:1 102


let's verify it:
R1#sh ip route | beg Gateway
Gateway of last resort is not set

!--global routing table is completely empty

R1#sh ip route vrf one | beg Gateway
Gateway of last resort is not set

172.16.0.0/24 is subnetted, 1 subnets
C 172.16.0.0 is directly connected, Serial1/0/0:1

R1#sh ip route vrf two | beg Gateway
Gateway of last resort is not set

172.16.0.0/24 is subnetted, 1 subnets
C 172.16.0.0 is directly connected, Serial1/0/0:2

R1#ping vrf one 172.16.0.2

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.0.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 12/12/16 ms

R1#ping vrf two 172.16.0.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.0.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 12/13/16 ms
R1#


Now we can enjoy Frame Relay labs with cheap hand-made Rj-45 cables (but with expensive VWIC MFT-E1 cards ;-) )

2 comments:

sysfail said...

Hi there,

Interesting post. I was building myself a frame relay lab with VWIC, but I found the inconvenient limitation of the channel groups...I have tried several combintions but I can't make more than 2 channels per port. However cisco doc talks about "2 or more channels". Do you know if it is possible? or why is it limited?

thanks in advance!

Marco Rizzi said...

Hi Sysfail,

I've read "2 or more channels" too, but there's another older document (Document ID: 8017) titled "Understanding 1-Port and 2-Port E1 Multiflex Trunk Voice/WAN Interface Cards (VWICs)" that say:
"Support is available for two channel groups on one port"...
no more than two, it's referred to old 2600/3600 series, but i guess that VWIC still unchanged ;-(.

(it will be great to have a lot of serials and a vrf each...)

Marco