configure connectivity on nme-cue

My nm-cue died and all we have as a replacement is a nme-cue. I tried to apply the current config from the nm-cue to the nme-cue and I can't ping it from the router to the nme-cue.

This was the working config from the NM-CUE

FastEthernet0/0.20 10.3.3.1 YES NVRAM up up

interface Service-Engine1/0
description $FW_INSIDE$
ip unnumbered FastEthernet0/0.20
service-module ip address 10.3.3.5 255.255.255.0
service-module ip default-gateway 10.3.3.1
!

ip route 10.3.3.5 255.255.255.255 Service-Engine1/0

I applied this on the NME-CUE and it doesn't ping

Cisco website has the config for the NME-CUE as:

Router(config)# interface Service-Engine 1/0
Router(config-if)# ip address 10.0.0.9 255.0.0.0
Router(config-if)# service-module ip address 10.0.0.10 255.0.0.0
Router(config-if)# service-module ip default-gateway 10.0.100.10
Router(config-if)# exit

I could ping from the router the nme-cue with a different subnet following this config but I do not want to place the service engine on another subnet.

I retried it with
interface Service-Engine 1/0
ip unnumbered FastEthernet0/0.20
service-module ip address 10.3.3.5 255.255.255.0
service-module ip default-gateway 10.3.3.1

It didn't mention to add a static route so I left it out. Couldn't ping so I added the static route:

ip route 10.3.3.5 255.255.255.255 Service-Engine1/0

Still can't ping

Any help would be greatly appreciated.

Find more posts tagged with

Comments

pitviper

config looks fine - Have you tried reloading the router (or NME)?

Legacy User

I just reloaded it now. You think it could not ping because theres no software on it? I sessioned into it and found that it was missing software. I can load the software from the service engine boot-loader but it doesn't ping my the host router. Which circles the issue back around since if I can ping my host router then I can ping the tftp server.

I looked up CUE admin guide under the troubleshoot section and seen this:

Problem: I cannot ping the internal address when using the IP unnumbered scheme.
Explanation The IP route table is not correct.
Recommended Action When using IP unnumbered, add a static route that points to the service-engine interface.

I looked over my static route a hundred times considering it may be incorrect but it was the working in the previous nm-cue. I wasn't sure if the configs were any different when using a NME-CUE.

DexterPark

I had a similar issue with a SM-SRE-900-K9, I couldn't ping or session to it. Not sure what the exact steps were to get it working, but what I remember doing is wiping the config on the router and only added the basic commands to get the service-module running. Like setting the IP address for the routers LAN interface which is shared by the service-module when using the "IP unnumbered" command, adding all my service-module commands, and the static route. Another thing, like you I was using a sub-interface for my "unnumbered" command to point at, but I got rid of that too and used the physical interface instead. After doing all that I got it working.

pitviper

Your static route is fine - the odd thing is that it was working with the "other" IPs.

I know the SM modules can be wiped and the software reloaded from the router - Not sure if this is an option on the NME (Never tried).

*EDIT*

Hmm, probably not as it's not mentioned here:

http://www.cisco.com/en/US/docs/voice_ip_comm/unity_exp/rel7_0/install/boothelp.html

pitviper

Working config on an ISM-SRE. Same thing, just different "interface" labeling:

interface GigabitEthernet0/0.20
 description VOICE VLAN
 encapsulation dot1Q 20
 ip address 172.22.81.1 255.255.255.0
 ip nat inside
 ip virtual-reassembly in
!
interface ISM0/0
 ip unnumbered GigabitEthernet0/0.20
 service-module ip address 172.22.81.2 255.255.255.0
 !Application: CUE Running on ISM
 service-module ip default-gateway 172.22.81.1
!
ip route 172.22.81.2 255.255.255.255 ISM0/0

Legacy User

Yea if I set it to another subnet without setting a static route I could ping it fine but I don't want to go changing ip addresses. Then I'd have to carefully change the dial-peers that are pointing to the nm-cue and look over my config to make sure no stone is left unturned. It'll become a huge pain in the ass. But the reality is it should be working with the ip unnumbered command and the static route.

I was getting it ready on a lab 2821 to get the configs all loaded before I pop it in the live unit so there are no routes or anything. We overnighted a nm-cue yesterday because theres no real time to go figure out the nme-cue. I need it up and running yesterday.

Legacy User

Got the replacement in and sure enough everything worked as it should. Of course it came in with software version 2.1 took some time to upgrade but all is well.

My guess the NME-CUE may be defective or something but whatever, thanks to you guys for giving your input.