T1 VWIC3 not coming up - 15.0 IOS

So I'm working on a T1 for a PRI circuit. Low and behold the t1 doesn't want to come up.

A couple of the tests that I did were:

1. Loop-back test
2. T1 Card / Configuration reset
3. Telephone vendor switch their Meta Switch


Throughout testing we were not able to get the T1 to stay up. It would come up and then go down. Come up and then go down.


T1 OUTPUT:

 ISDN Se0/1/0:23 Q921: User RX <- RRp sapi=0 tei=0 nr=0 ISDN Se0/1/0:23 Q921: User TX -> RRf sapi=0 tei=0 nr=0ISDN Se0/1/0:23 Q921: User RX <- RRp sapi=0 tei=0 nr=0ISDN Se0/1/0:23 Q921: User TX -> RRf sapi=0 tei=0 nr=0%CONTROLLER-5-UPDOWN: Controller T1 0/1/0, changed state to down (LOF detected) ISDN Se0/1/0:23 Q931: L3_ShutDown: Shutting down ISDN Layer 3 ISDN Se0/1/0:23 Q931: Ux_DLRelInd: DL_REL_IND received from L2 %MARS_NETCLK-3-HOLDOVER: Entering Holdover for Controller T1 0/1/0%LINK-3-UPDOWN: Interface Serial0/1/0:23, changed state to down %MARS_NETCLK-3-HOLDOVER_TRANS: Holdover timer exceeded for Controller T1 0/1/0 %MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 1 to priority 10

Router#sh isdn status

Global ISDN Switchtype = primary-niISDN Serial0/1/0:23 interface        dsl 0, interface ISDN Switchtype = primary-ni    Layer 1 Status:        ACTIVE    Layer 2 Status:        TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED    Layer 3 Status:        0 Active Layer 3 Call(s)    Active dsl 0 CCBs = 0    The Free Channel Mask:  0x807FFFFF    Number of L2 Discards = 0, L2 Session ID =    Total Allocated ISDN CCBs = 0
Router#show isdn statusGlobal ISDN Switchtype = primary-niISDN Serial0/1/0:23 interface        dsl 0, interface ISDN Switchtype = primary-ni    Layer 1 Status:        DEACTIVATED    Layer 2 Status:        TEI = 0, Ces = 1, SAPI = 0, State = TEI_ASSIGNED    Layer 3 Status:        0 Active Layer 3 Call(s)    Active dsl 0 CCBs = 0    The Free Channel Mask:  0x00000000    Number of L2 Discards = 0, L2 Session ID =     Total Allocated ISDN CCBs = 0
Router# %CONTROLLER-5-UPDOWN: Controller T1 0/1/0, changed state to uping ISDN Se0/1/0:23 Q921: L2_EstablishDataLink: sending SABME ISDN Se0/1/0:23 Q921: User TX -> SABMEp sapi=0 tei=0 ISDN Se0/1/0:23 Q921: User RX <- BAD FRAME(0x00017F)ISDN Se0/1/0:23 Q921: User TX -> SABMEp sapi=0 tei=0 ISDN Se0/1/0:23 Q921: User RX <- BAD FRAME(0x00017F) %LINK-3-UPDOWN: Interface Serial0/1/0:23, changed state to up ISDN Se0/1/0:23 Q921: User TX -> SABMEp sapi=0 tei=0 ISDN Se0/1/0:23 Q921: User TX -> SABMEp sapi=0 tei=0 ISDN Se0/1/0:23 Q921: User RX <- BAD FRAME(0x00017F) ISDN Se0/1/0:23 Q931: Ux_DLRelInd: DL_REL_IND received from L2 %CONTROLLER-5-UPDOWN: Controller T1 0/1/0, changed state to down (LOS detected) ISDN Se0/1/0:23 Q931: L3_ShutDown: Shutting down ISDN Layer 3%LINK-3-UPDOWN: Interface Serial0/1/0:23, changed state to down %CONTROLLER-5-UPDOWN: Controller T1 0/1/0, changed state to up ISDN Se0/1/0:23 Q921: L2_EstablishDataLink: sending SABME ISDN Se0/1/0:23 Q921: User TX -> SABMEp sapi=0 tei=0 %CONTROLLER-5-UPDOWN: Controller T1 0/1/0, changed state to down (LOF detected) ISDN Se0/1/0:23 Q931: L3_ShutDown: Shutting down ISDN Layer 3 ISDN Se0/1/0:23 Q931: Ux_DLRelInd: DL_REL_IND received from L2
So after some long hours of troubleshooting. There is a nifty little command :


                                    microcode reload controller {t1 | e1| j1} {slot / sub slot}

                           microcode reload controller t1 0 1


 Microcode reload controller reloads the firmware of the VWIC card without reloading the Cisco IOS on the chassis or device in use. For example the  2921 router. 

Comments

  1. ChupiJanuary 25, 2017 at 10:34 AM

    I tested the microcode reload on a Cisco C5850 Voice Gateway running IOS 12.4(15)T7. Shutting down the Serial interface and re-enabling would not bring the problematic PRI up. I had to reload the Cisco to re-initialize all PRI's. Although the command syntax is slightly different on 12.4, using the microcode reload, I was able to reload the T1/T3 controllers without having to reboot the Cisco.

    ReplyDelete

Post a Comment

Popular posts from this blog

HULC LED PROCESS - 3750 High CPU

Image
If you're looking at a switch and you see the HULC LED Process running high. The HULC LED process does some of the following tasks: 1. Check link status on every port 2. If the switch supports POE, it checks to see if there is a power device 3. Transceiver checks 4. Fan status updates 5. Set LED ports 6. Check on temperature status Overall the HULC LED Process is a monitoring process running. During looking into this I turned off all non-used ports since it checks the link status. Then I made sure the environment was good. Two Cisco Bugs: http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCsi78581 http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtn42790
Read more

Cisco Tomcat High CPU Utilization 99 percent

Image
So a client was experience slow web interface usage to their calling node. As well RTMT was shooting off the alert. The alert is for Call Process CPU Node Pegging.  The culprit tomcat! Cisco Tomcat Service -  In enterprise edition this is a web server service. In the business edition (BE Servers) this uses the web server and unity utilizes the service as well. Log in to each call manager node and issue the following command: show process load cpu **OUTPUT** top - 08:55:48 up 340 days, 4:03, 1 user, load average: 4.64, 3.25, 2.98  Tasks: 142 total, 2 running, 140 sleeping, 0 stopped, 0 zombie  Cpu(s): 16.3%us, 3.4%sy, 0.0%ni, 80.1%id, 0.1%wa, 0.0%hi, 0.2%si, 0.0%st  Mem: 4016964k total, 3856400k used, 160564k free, 29904k buffers  Swap: 2064280k total, 1664k used, 2062616k free, 598124k cached  PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND  8065 tomcat 25 0 2317m 1.9g 22m S 99.4 50.4 358084:37 tomcat  1 root 15 ...
Read more