Posts

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

Call forward - Busy tone - 7960 phone

So as it appears another issue with call forwards : Scenario : 7960 phone not correctly forwarding calls even though the call forward all was set correctly. Looking into the Forward no answer timers and the service parameters there wasn't anything unusual from the basic scenario. So I took a look at Cisco's general problems that come up with a 7960 and found the link below: http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a00809b3b06.shtml If we take a look at the solution its asking us to do the following : In order to resolve this problem, complete these steps to reset the  MaxForwardsToDn  counter: Go off hook on the phonethat has the high counter and register it to CCM: Enter  **##*30  from the dialpad in order to enable the phone to accept the code. Go off hook again on the same Cisco IP phone, and enter  **##*35  from the dialpad in order to clear the  MaxForwardsToDn counters. Complete calls to the IP Phone in order to veri

Extension Mobility Login Unavailable (22)

Image
" Extension Mobility Login Unavailable (22) " When configuring extension mobility for a Call Manager environment. Generally when getting the above error you need to enable EM under the actual device.

Change ASDM for ASA 5510

Image
So I got a quick case to just update the ASDM on an ASA Firewall. This one is pretty simple and can be done multiple ways through cli, current asdm, or a mix of both. I'll just do a mix of both. The ASDM upgrade is from version 631 to 713. *** Before you start make sure you download the newest ASDM version that is compatible with your ASA version. show version  1. Login to ASDM 2. Go to Tools > File Management  3. Transfer the file from the local PC to the Disk0 in the ASA 4. Go to CLI to remove / verify  the OLD asdm image  sh run asdm asdm image disk0:/asdm-631.bin no asdm image disk0:/asdm-631.bin 5. Make the new image the ASDM image asdm image disk0:/asdm-713.bin 6. Verify changes

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=0 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=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

Base Configuration Netflow and Flexible Netflow Template Version 9

BASE Flexible Netflow Template (3750 w/ module) ----------------------------------        flow record RECORD1 match ipv4 source address match ipv4 destination address collect counter bytes long collect packets long flow exporter EXPORT1 destination <IPADDRESS> transport udp <PORT#> flow monitor MONITOR1 record RECORD1 exporter EXPORT1 BASE Netflow Template (Router) ------------------------------------ ip flow-export source < Interface > ip flow-export version 9 ip flow-export destination <IP Address>  <Port Number>   ip flow-cache timeout active <Time in Minutes>

Error: Contact Administrator - CUCM Corporate Directory

Image
Error: Contact Administrator The above error may come up when using the "Directory" button on your Cisco Phone. This can be resolved a couple ways.  One is to try configuring the Corporate Directory Service from the previous DNS identifier: Change to :   http://x.x.x.x:8080/ccmcip/xmldirectory.jsp   X.X.X.X = IP Address of CUCM Publisher Server  Make sure you "SAVE" the IP Phone Services Configuration Another method is to make a service with the same "http" field above and name it Corp Directory and subscribe it to the enterprise.