To reset a Cisco router to factory default (removing the startup configuration file), perform these steps:
1. To erase the configuration file, issue the erase nvram: command. Reload the router by issuing the reload command. 2. If this does not solve the problem, attempt to break into ROM Monitor (ROMmon) by issuing the break sequence (usually Ctrl and break from the Hyperterminal) from a console connection.
Refer to:
Cisco Standard Break Key Combinations
You should see this ROMmon prompt:
3. Change the configure register value to ignore the startup configuration by issuing the confreg command, as shown in this example:rommon 1>
4. To reload the router, issue the reset command, as shown in this example:rommon 2> confreg 0x2142
5. After the router boots, issue the enable command at the Router > prompt.rommon 3> reset
The prompt changes to Router#, indicating that the router is now in privileged mode.
6. To enter config mode, issue the config terminal command.You should now see a Router(config)# prompt.
7. To change the configure register to recognize the startup configuration, issue the config-register command, as shown in this example:Router (config)# config-register 0x2102
To break out of configuration mode, press Cntl and Z.
To save the blank configuration, issue the copy-running config-startup config command.
notes
A session with Apple's telephone support came up with a solution. My wife hard established an iCloud account but had no signed in. Once she did so, the "plus" sign returned, she could add events by tapping +, double-tapping a date, and by using Siri.
Notes
If the Remote Procedure Call (RPC) service is not listed as a dependency for your Print Spooler Service, you need to inform XP that the Print Spooler service depends on the RPC service.Click Start, Run and in the box enter (including the important space after the equals sign):
sc config spooler depend= RPCSS
Click OK to assign the RPC service to the Print Spooler service, then be sure the RPC Service is running and start your Print Spooler Service.
Notes
Could Not Get Lock /var/lib/apt/lists/lock
Problem:Solution:
When i try to update software packages in Ubuntu i get following error
- E: Could Not Get Lock /var/lib/apt/lists/lock
Run Terminal and type these commands
- sudo rm /var/lib/apt/lists/lock
- sudo apt-get clean
- sudo apt-get update
Notes
Cisco PIX/ASA Causes SMTP Banner Corruption
Traffic inspection rules on a Cisco PIX or ASA firewall will sometimes cause the SMTP banner to appear corrupted.
When testing access to your mail server from outside, you may notice that the SMTP banner looks like this:
This is just a symptom of the problem, which is that the SMTP traffic inspection rule is interfering with the SMTP data stream. Another symptom would be to see email messages destined for this server seemingly stuck in the SMTP queue on a server outside the network. This can ultimately cause delayed and undeliverable mail, especially for larger messages, such as those with attachments.
The resolution for this problem is to disable the traffic inspection rule for SMTP/ESMTP on the Cisco PIX or ASA firewall.
On a PIX, this can be done from the command-line using the “no fixup protocol SMTP 25” command. It can also be disabled from the PIX Device Manager (PDM).
On an ASA, it’s a little different. From the command line (assuming your policy map is named “global_policy” and your class is named “inspection_default”):
CiscoASA(config)#policy-map global_policy
CiscoASA(config-pmap)#class inspection_default
CiscoASA(config-pmap-c)#no inspect esmtpFrom the Adaptive Security Device Manager (ASDM):
1. Go to Security Policy –> Open the inspection rule:
2. Go to the Rule Actions tab and uncheck the box next to ‘ESMTP’
3. Test from outside the PIX/ASA again by telnetting to port 25; your SMTP banner should now look like this (I have masked the name of the server for privacy).
That’s it. I have made it standard practice to just disable this inspection rule on all Cisco ASA firewalls that I deploy to avoid problems.
Notes
HowTo: Elastix DAHDI Trunk Routing with DID
If you have multiple FXO (PSTN) lines into your PBX, it is always nice to be able to route these in-bound calls based on the physical line they arrive upon. Getting this working with DAHDI in Elastix has been driving me up the wall!
This issue has been bugging me for over a week now and I have finally got it to work. I have two trunks connected via FXO modules on a TDM400 card, but I could not get the DID working with them (CLI with BT sorted). But once Asterisk had the call, I could not make Asterisk make a decision with call based on which number/line the caller called. Not the number the caller is calling from, this is CLI or CID, but the number they dialled to make your line ‘ring’.
Asterisk was either saying there was no route and answering the call to say the number you have called is not in service, or just handling the 2 lines in the same way – i.e. it could not tell them apart. Here I detail my findings so you can process lines automatically.
I had most of the configuration right, but I had to hand edit another configuration file to actually to get the changes made via the web interface actually working. Trying to find this last little bit of information on the forums has been maddening to say the least.
Changing the route
First you need to correct the router handler, by changing a setting in a configuration file. There is no graphical interface for this I’m afraid and it is the only file you need to manually edit by a suitable means.
The default setting in this configuration file is ‘from-pstn’ and this needs to be changed to ‘from-zaptel’. You need to edit:
/etc/asterisk/dahdi-channels.conf
You need to find the correct section for your line connection. For me this was lines 3 & 4. Below is the example original settings for my channel 3:
;;; line=”3 WCTDM/4/2 FXSKS”
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 3
callerid=
group=
context=defaultAnd you need to edit this for each channel to become like this:
;;; line=”3 WCTDM/4/2 FXSKS”
signalling=fxs_ks
callerid=asreceived
group=0
context=from-zaptel
channel => 3
callerid=
group=
context=defaultThen save the file back and restart Asterisk.
Marking the Channel DID
The next stage is to assign DID numbers to these channels so a decision can be made on how to process the call based on line ID.
Elastix does not have an interface to the required facility, so you need to un-embed the FreePBX console, details are here.
Once in the FreePBX console, you need to choose ‘ZAP Channel DIDs’ from the menu on the left. You should get a screen similar to:
ZAP DIDs
It is quite simple to complete, needing only 3 bits of information:
- Channel – The DAHDI channel you are assigning the DID to.
- Description – Your description for this allocation. I would suggest an name and a summary of the DID you will be allocating.
- DID: The DID number need to call to make this channel ‘ring’.
An example UK configuration might look like this for channel 3, used to be routed (Inbound Routes) to the sales department for the number: 01234-123456:
ZAP DID Sample
Once completed, you can click ‘Submit Changes’. You need to repeat this for each FXO port you have for inbound calls.
You can then save the changes back and configure the ‘Inbound Routes’ to actually ‘route’ the calls where you want them.
You can actually use almost any number in the DID, but I suggest you use the full number, including the STD, in case you have any ‘out of area’ number. And it generally reduces confusion in the future.
Notes
Figure 2-13 shows the use of source and destination ports. The host on the 10.1.2.0/24 network accesses a single host for both web services and Telnet services. When the host accesses the server for web services, the local address is translated to 209.165.202.129. When the host accesses the same server for Telnet services, the local address is translated to 209.165.202.130.
Figure 2-13 Policy NAT with Different Destination Ports
The syntax for this configuration example follows:
access-list WEB permit tcp 10.1.2.0 255.255.255.0 209.165.201.11 255.255.255.255 eq 80access-list TELNET permit tcp 10.1.2.0 255.255.255.0 209.165.201.11 255.255.255.255 eq 23nat (inside) 1 access-list WEBglobal (outside) 1 209.165.202.129 255.255.255.255nat (inside) 2 access-list TELNETglobal (outside) 2 209.165.202.130 255.255.255.255Limitations
The following configuration limitations apply to policy NAT:
•
Access lists must contain permit statements only. Access lists for policy NAT cannot contain deny statements.
•
nat (inside) 1 access-list mylist-Anat (inside) 2 access-list mylist-AWhereas, the following configuration would not produce an error:
nat (inside) 1 access-list mylist-Anat (inside) 2 access-list mylist-B•
•
•
•
Notes
Figure 1: These are the ports associated with the servers used by iSeries Access for Windows.
Figure 2 lists some common iSeries Access functions and the servers that they utilize. Using Figure 1 and Figure 2, you should be able to determine which ports you need to open on your firewall. Also, these two tables are available on the iSeries Access Web site, in the Information APARs section. Select II12227. This page is kept up-to-date with the latest information on iSeries Access port usage. There could be additions to this table at any time, although it's likely that changes will be seen only on release boundaries.
Notes
if you type in .\ before the username, that will instruct it that you are logging onto the local computer. so for your Administrator example, you would put in .\Administrator
Notes
To reset the SST password:
-sign on as QSECOFR
-use the Change IBM Service Tools Pwd (CHGDSTPWD) command:
CHGDSTPWD PASSWORD(*DEFAULT)
-now go into STRSST, and sign on with user QSECOFR and password QSECOFR
you will be prompted to change the password.You can access a similar hardware listing without going into SST using the Display Hardware Resources (DSPHDWRSC) command:
DSPHDWRSC TYPE(*AHW) OUTPUT(*PRINT)
