FXO ports starting in shut state

[caadoptees]

3640 router with 3 NM-2V slots. Each slot has 2 FXO-2 cards. After a reload/reboot, the first port in each FXO comes up in shutdown state. I can then do:

voice-port 1/0/0
shut
no shut

and they are both operational. I will then save the configuration. I verify that the running config and startup config are the same. Reload/reboot and the first port of the pair is again shutdown. The current config shows it as does the startup config!

Has anyone seen this before?

3640 is running 12.4(25a). Call Manager is 4.1.

 

[burtsbees]

Dod you by chance edit and copy the file over from a text file, or change the config register to 2142 then back? Both will actually put the interfaces in a shut state at startup...

/

tim@tim-laptop ~ $ sudo apt-get install windows
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Couldn't find package windows...Thank Goodness!

 

[burtsbees]

Also, stp maybe? Like, spantree-portfast on the vlan switchports?

/

tim@tim-laptop ~ $ sudo apt-get install windows
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Couldn't find package windows...Thank Goodness!

 

[whykap]

did you have this issue before you upgraded the code? This IOS release is less than a month old, so you might want to try and bump it down a release.
Are you using MGCP or h323 for those ports?
If MGCP are you allowing time for call manager to take control of the router and bring it out of shutdown state?
It can take a few minutes after it is up for everything to stabilize and function properly, including MGCP control of the router by the ccm server.

 

[burtsbees]

Good call---look at the Bug Toolkit on CCO...

/

tim@tim-laptop ~ $ sudo apt-get install windows
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Couldn't find package windows...Thank Goodness!

 

[caadoptees]

Burts, the config has been hand typed, or pasted, not uploaded from a text file. The reg is not 2142 nor have I ever made it so. There is only one port FastEthernet on this router so I don't know if that matters.

Whykap, MGCP. I think it has enough time. It does not seem to do so.

I will try downgrading a step or two.

Thanks for the help you two.

 

[whykap]

Let us know if the downgrade fixed the issue. We are always interested in a fix as we are bound to run into it in the future.

 

[burtsbees]

As long as the config reg was not 2142 right before the problem---after you change it back, on some cards you have to do a shut then a no shut.

This sounds like a buggy IOS...

/

tim@tim-laptop ~ $ sudo apt-get install windows
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Couldn't find package windows...Thank Goodness!