06-21-2010 08:46 AM - edited 03-04-2019 08:51 AM
Hi - My customer has had a NM-4E1-IMA working in a 2800 router fine;
Cisco IOS Software, 2800 Software (C2800NM-ENTSERVICESK9-M), Version 12.4(4)T, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2005 by Cisco Systems, Inc.
Compiled Thu 27-Oct-05 11:24 by ccai
ROM: System Bootstrap, Version 12.3(8r)T7, RELEASE SOFTWARE (fc1)
System returned to ROM by error - a System Error, PC 0x4143CC9C at 13:38:00 BST Wed Jun 16 2010
System restarted at 13:39:05 BST Wed Jun 16 2010
System image file is "flash:c2800nm-entservicesk9-mz.124-4.T.bin"
This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
If you require further assistance please contact us by sending email to
export@cisco.com.
Cisco 2811 (revision 53.51) with 249856K/12288K bytes of memory.
Processor board ID
2 FastEthernet interfaces
4 ATM interfaces
3 Channelized E1/PRI ports
1 ATM/Voice AIM
DRAM configuration is 64 bits wide with parity enabled.
239K bytes of non-volatile configuration memory.
62720K bytes of ATA CompactFlash (Read/Write)
Configuration register is 0x2102
He's installed it in a 2620, and althought the card is recognised, the E1 interfaces don't show up in the sh ver
------------------ show version ------------------
Cisco Internetwork Operating System Software
IOS (tm) C2600 Software (C2600-JS-M), Version 12.2(46a), RELEASE SOFTWARE (fc1)
Copyright (c) 1986-2007 by cisco Systems, Inc.
Compiled Wed 11-Jul-07 20:22 by pwade
Image text-base: 0x8000808C, data-base: 0x81478264
ROM: System Bootstrap, Version 12.1(3r)T2, RELEASE SOFTWARE (fc1)
Manchester-ATM-2 uptime is 4 minutes
System returned to ROM by reload
System image file is "flash:c2600-js-mz.122-46a.bin"
cisco 2620 (MPC860) processor (revision 0x600) with 58368K/7168K bytes of memory.
Processor board ID (836313172)
M860 processor: part number 0, mask 49
Bridging software.
X.25 software, Version 3.0.0.
SuperLAT software (copyright 1990 by Meridian Technology Corp).
TN3270 Emulation software.
Basic Rate ISDN software, Version 1.1.
1 FastEthernet/IEEE 802.3 interface(s)
1 ISDN Basic Rate interface(s)
4 ATM network interface(s)
32K bytes of non-volatile configuration memory.
16384K bytes of processor board System flash (Read/Write)
Configuration register is 0x2102
We have tried it with a couple of different versions of code - current version is 12.2 Enterprise plus - Software advisor says it just needs anything with a 'plus' featureset.
Any ideas anyone?
Cheers, Dom
06-28-2010 07:17 AM
Hello!
The "4 ATM network interface(s)" in show ver above could actually be the reprecentation
of those 4 ATM E1 ports of the NM-4E1-IMA as per datasheet:
What is the problem with those ports actually?
What does "show inv" and/or "sh diag" shows?
Thanks,
Sergey
06-28-2010 07:46 AM
Hi Sergey - Thanks for your mail.
The interface wont come up whereas it comes up fine on the 2800 - the relavant config is below;
interface ATM1/0
no ip address
shutdown
no atm ilmi-keepalive
scrambling-payload
impedance 120-ohm
!
interface ATM1/1
no ip address
no atm ilmi-keepalive
ima-group 0
no scrambling-payload
impedance 120-ohm
!
interface ATM1/2
no ip address
no atm ilmi-keepalive
scrambling-payload
impedance 120-ohm
!
interface ATM1/3
no ip address
no atm ilmi-keepalive
scrambling-payload
impedance 120-ohm
!
interface ATM1/IMA0
no ip address
no atm ilmi-keepalive
ima differential-delay-maximum 50
!
interface ATM1/IMA0.241 point-to-point
bandwidth 1920
ip address x.x.x.x 255.255.255.252
ip wccp 51 redirect out
ip wccp 51 redirect in
pvc 2/41
vbr-nrt 1920 1920 1
encapsulation aal5snap
!
sh diag recognises the card;
Slot 0:
C2620 1FE Mainboard Port adapter, 2 ports
Port adapter is analyzed
Port adapter insertion time unknown
EEPROM contents at hardware discovery:
Hardware Revision : 6.0
PCB Serial Number : JAD05390AXV (836313172)
Part Number : 73-2843-10
RMA History : 00
RMA Number : 0-0-0-0
Board Revision : B0
Deviation Number : 0-0
EEPROM format version 4
EEPROM contents (hex):
0x00: 04 FF 40 00 94 41 06 00 C1 17 4A 41 44 30 35 33
0x10: 39 30 41 58 56 20 28 38 33 36 33 31 33 31 37 32
0x20: 29 82 49 0B 1B 0A 04 00 81 00 00 00 00 42 42 30
0x30: 80 00 00 00 00 FF FF FF FF FF FF FF FF FF FF FF
0x40: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x50: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
WIC Slot 1:
BRI S/T - 2186 WAN daughter card
Hardware revision 1.3 Board revision A0
Serial number 25942436 Part number 800-01833-03
Test history 0x0 RMA number 00-00-00
Connector type Wan Module
EEPROM format version 1
EEPROM contents (hex):
0x20: 01 07 01 03 01 8B D9 A4 50 07 29 03 00 00 00 00
0x30: 50 00 00 00 01 09 18 01 FF FF FF FF FF FF FF FF
Slot 1:
IMA 4 port E1 Port adapter, 4 ports
Port adapter is analyzed
Port adapter insertion time unknown
EEPROM contents at hardware discovery:
Hardware Revision : 1.0
Top Assy. Part Number : 800-03968-03
Board Revision : D0
Deviation Number : 0-0
Fab Version : 05
PCB Serial Number : JAB06010BUW
RMA Test History : 00
RMA Number : 0-0-0-0
RMA History : 00
EEPROM format version 4
EEPROM contents (hex):
0x00: 04 FF 40 00 BE 41 01 00 C0 46 03 20 00 0F 80 03
0x10: 42 44 30 80 00 00 00 00 02 05 C1 8B 4A 41 42 30
0x20: 36 30 31 30 42 55 57 03 00 81 00 00 00 00 04 00
0x30: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x40: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x50: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
sh int below;
ATM1/IMA0 is down, line protocol is down
Hardware is ATM IMA
MTU 4470 bytes, sub MTU 4470, BW 1920 Kbit, DLY 20000 usec,
reliability 0/255, txload 1/255, rxload 1/255
Encapsulation ATM, loopback not set
Encapsulation(s): AAL5
255 maximum active VCs, 1024 VCs per VP, 0 current VCCs
VC idle disconnect time: 300 seconds
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: Per VC Queueing
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 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 output buffer failures, 0 output buffers swapped out
ATM1/IMA0.241 is down, line protocol is down
Hardware is ATM IMA
Internet address is x.x.x.x/30
MTU 4470 bytes, BW 1920 Kbit, DLY 20000 usec,
reliability 0/255, txload 1/255, rxload 1/255
Encapsulation ATM
0 packets input, 0 bytes
0 packets output, 0 bytes
0 OAM cells input, 0 OAM cells output
AAL5 CRC errors : 0
AAL5 SAR Timeouts : 0
AAL5 Oversized SDUs : 0
AAL5 length violation : 0
AAL5 CPI Error : 0
Cheers, Dom
06-29-2010 04:51 AM
Hi Dom,
Are E1s without IMA groups comes online fine (show contr atm1/1)?
Did you tried two NM E1 ports connected by an E1 cable?
You migth try to use a hard loop E1 to check if the port is correct.
The pinout to create a E1 loop is the indicated on the following link:
http://www.cisco.com/en/US/tech/tk713/tk628/technologies_tech_note09186a008010059a.shtml#topic1
On that case you could test locally the port itself. If that is going fine,
next step could be to connect two E1 ports on the NM module and test locally if
IMA interfaces are correctly created.
Thanks,
Sergey
06-29-2010 07:47 AM
Hi Sergey - My customer has jusy contacted me to say that they have resolved it.
I think they were hitting bug CSCdu38436
Thanks for your help on this
Cheers, Dom
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide