05-31-2011 01:02 PM - edited 03-16-2019 05:13 AM
Hey all,
I'm getting a problem with a CUE here: It's a 2821 router ( c2800nm-adventerprisek9-mz.124-25a.bin) and config for the NM-CUE module is the following:
!
interface Service-Engine1/0
ip address 192.168.254.1 255.255.255.252
service-module ip address 192.168.254.2 255.255.255.252
service-module ip default-gateway 192.168.254.1
!
ip forward-protocol nd
ip route 192.168.254.2 255.255.255.255 Service-Engine1/0
!
!
05-31-2011 01:57 PM
Hello Karl,
I never configured the Service Engine interface with "ip address" command as you did. I always bind it with the Loopback interface.
Can you try the follwing:
!
Interface loopback 0
ip address 192.168.254.1 255.255.255.252
!
interface Service-Engine1/0
ip unnumberd loopback 0
service-module ip address 192.168.254.2 255.255.255.252
service-module ip default-gateway 192.168.254.1
no shut
!
ip forward-protocol nd
ip route 192.168.254.2 255.255.255.255 Service-Engine1/0
Let me know what happends.
Best regards,
Nizar
05-31-2011 02:04 PM
Hey Nizar,
Thanks for replying.
I did it already. As far as I know, both ways are allowed - with IP direct at the Service-Engine interface or using the IP unnumbered from a loopback.
I have just did it, anyway:
!
interface Service-Engine1/0
ip unnumbered Loopback0
service-module ip address 192.168.254.2 255.255.255.0
service-module ip default-gateway 192.168.254.1
!
ip forward-protocol nd
ip route 0.0.0.0 0.0.0.0 189.125.7.13
ip route 192.168.254.2 255.255.255.255 Service-Engine1/0
!
!
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++=
Router#ping 192.168.254.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.254.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms
Router#ping 192.168.254.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.254.2, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
Router#
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
So, the problem is still the same, no matter the config I do...
thx,
Karl
05-31-2011 03:25 PM
Hello,
I was looking for the same issue and found one topic which has same issue like yours. they replaced the CUE.
please take a look:
http://www.dslreports.com/forum/r24735852-HW-AIMCUE-card-issues-on-cisco2821
Hope this helps.
Best regards,
Nizar
06-01-2011 04:54 AM
Hi Nizar,
It seems that I have a faulty module. According to the link you posted, I think I'll have to find a way of replacing it =(
Anyway, thanks for replying!
Karl
05-31-2011 03:48 PM
Hi Karl,
What is the output of 'service module service-engine 1/0 status'. Are you able to session to the CUE module?
Chris
06-01-2011 04:47 AM
Hello Chris,
The output is the following:
Router#ping 192.168.254.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.254.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms
Router#ping 192.168.254.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.254.2, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
Router#
06-01-2011 05:13 AM
Hi Karl,
It looks like a defective module:
06-01-2011 05:16 AM
Chris,
This is not a production module. I'm doing some lab with it before putting it on production.
What exactly did you do? Only a reset via CLI? Could you explain me the steps?
Thanks,
Karl
06-01-2011 05:29 AM
Hi Karl,
It was a combination of re-seating the module and running the CLI command I mentioned. I was still able to session into my CUE module (service module service-engine 1/0 session) and was able to reload the OS via. the *** method when the module first booted up. My issue was that the modules OS was corrupted and had to be reloaded.
HTH,
Chris
Please rate helpful posts
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