ISR4431 NIM-4MFT-T1/E1

[leyakhath muhammed]

How can configure ISRs 43XX(16.09.05) and 44XX (16.06.05) communicate with NIM-4MFT-T1/E1  

cisco 4331/Cisco IOS XE Software, Version 16.09.05
controller T1 0/1/0
framing esf
fdl both
clock source network
linecode b8zs
cablelength short 110
channel-group 1 timeslots 1-4
loopback remote esf line csu
Interface IP-Address OK? Method Status Protocol
GigabitEthernet0/0/0 unassigned YES NVRAM down down
GigabitEthernet0/0/1 unassigned YES NVRAM administratively down down
GigabitEthernet0/0/2 unassigned YES NVRAM down down
Serial0/1/0:1 192.168.10.5 YES manual down down
Serial0/1/1:1 unassigned YES unset down down

cisco 4431/Cisco IOS XE Software, Version 16.06.05
controller T1 0/1/0
framing esf
fdl both
clock source network
linecode b8zs
cablelength short 110
channel-group 1 timeslots 1-4
loopback remote esf line csu
Interface IP-Address OK? Method Status Protocol
GigabitEthernet0/0/0 unassigned YES NVRAM down down
GigabitEthernet0/0/1 unassigned YES NVRAM administratively down down
GigabitEthernet0/0/2 unassigned YES NVRAM down down
Serial0/1/0:1 192.168.10.3 YES manual down down
Serial0/1/1:1 unassigned YES unset down down

Router#sh int Serial0/1/0:1
Serial0/1/0:1 is down, line protocol is down
Hardware is NIM-4MFT-T1/E1
Internet address is 192.168.10.11/24
MTU 1500 bytes, BW 256 Kbit/sec, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation HDLC, crc 16, loopback not set
Keepalive set (10 sec)
Last input never, output 00:08:09, output hang never
Last clearing of "show interface" counters never
Input queue: 0/375/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 unknown protocol drops
0 output buffer failures, 0 output buffers swapped out
2 carrier transitions alarm present
Timeslot(s) Used:1-4, subrate: 64Kb/s, transmit delay is 0 flags

Thanks

[Flavio Miranda]

@leyakhath muhammed 

You can read all the feature this NIM have on the following link

Products - Cisco 4000 Series Integrated Services Router T1/E1 Voice and WAN Network Interface Modules Data Sheet - Cisco

Answering you question, No, you can not communicate between router using this board.  This Board is meant to connect the router to Telephone System.

You can connect the router to BBX using T1/E1 for voice traffic only.

Data Features

NIM data features follow:

●   T1/E1 or fractional T1/E1 network interface

●   n x 64 kbps or n x 56 kbps, nonchannelized data rates (T1: n = 1 to 24, E1: n = 1 to 31)

●   Standards-based, including ANSI T1.403 and AT&T Publication 62411

●   Non-Facility Associated Signaling (NFAS) on one single module is supported. NFAS across multiple NIM modules is not supported.

NIM data features do not include Dial on Demand Routing (DDR).

[leyakhath muhammed]

Please let me know which NIM for routing is supported between  4300 and 4400.

[Flavio Miranda]

Cisco offers four types of Ethernet WAN modules:

●     Cisco 1-Port Gigabit Ethernet WAN Network Interface Module (NIM-1GE-CU-SFP) (Figure 1)

●     Cisco 2-Port Gigabit Ethernet WAN Network Interface Module (NIM-2GE-CU-SFP) (Figure 1)

●     Cisco 6-Port High-Density Gigabit Ethernet WAN Service Module (SM-X-6X1G) (Figure 2)

●     Cisco 4-Port High-Density Gigabit or 1-Port 10 Gigabit Ethernet WAN Service Module (SM-X-4X1G-1X10G) (Figure 3)

[Elliot Dierksen]

I see one problem immediately. You have both sides configured to use the network as the clock source. That will cause slips in a back to back configuration. One side has to use an internal clock, and the other side will use network to recover the clock from the other side.

Second, are you using a T1/E1 crossover cable? That would be crossing 1-2 and 4-5. This is different from an ethernet crossover which crosses 1-2 and 3-6.

[Richard Burts]

@Flavio Miranda makes the point " This Board is meant to connect the router to Telephone System". And it is an accurate statement about the primary intent. But it does not mean that other implementations are not possible. Many time in lab environments I have connected back to back serial connections. And if properly configured it will work.

@Elliot Dierksen makes 2 very good points. Normally the serial card gets clocking from the telco to which it is connected. But when operating back to back one of the devices must supply clocking. That part is pretty easy to fix. The issue about cable type is more of a challenge. It certainly looks like you could use a standard RJ45 cable for a back to back serial connection. But the serial connection uses a different pinout and you need a special cable to do back to back connections.

[Elliot Dierksen]

The virtual serial interface is created from the "channel-group " group command on the T1 controller (:X tag matches channel group #). If it were a physical serial interface you would still need to have a DCE (provides clock) to DTE (receives clock) cabling arrangement. The DCE side would need the clock rate set.