If you want to allow a low-priviledged user on a Cisco router or a Switch to view the Startup Config then this can be done in Routers and Switches running Cisco IOS.
This infact is a simple 2 step procedure as follows:
If you're new here, you may want to subscribe to my RSS feed. Thanks for visiting!
I dont think we need an introduction to the most widely used Remote console utility, PUTTY. Putty support SSH, Telnet, RLogin & RAW connections.
If you telnet or SSH to your Cisco IOS routers or switches or Juniper Firewalls and ofcourse anything that support CLI and SSH or Telnet then one of the things you would prefer to do is to take a backup of the config (Running or Startup) or even capture session text including logs tech information etc. We discussed here about using Hypereterminal to capture text and hence backup and restore config on Cisco IOS Routers and Switches.
When troubleshooting a problem with Access Control lists, one of the things you would want to do is to clear the counters on the ACL matches.
In Cisco IOS, you can clear the ACL Matches counters as follows:
Another beginner tip that can be useful!
When you work on the Cisco Router or Catalyst Switch console, it would be annoying to have the console or terminal (telnet/ssh) logs to pop in between your commands. This can be even more irritating when it is busy switch or a router spitting messages continuously.
With Cisco IOS version 11.2, Cisco introduced the Named ACLs. Named ACLs are Standard or Extended ACLs which are give names instead of a ACL number. Technically, other than giving a name to the ACL there isn't any other difference when it comes to the functionality as in Standard or Extended ACL.
Extended ACLs are advanced than the Standard ACLs. Unlike the Standard Access Lists where it checks only the Source IP Address to control the flow of the packets, Extended ACLs can check the
Source & Destination Address
Protocols (IP,ICMP,TCP,UDP)
Source & Destination ports
While we saw here how to setup a Cisco Router as a Caching/Forwarding DNS Server. We can now look at how to make your Cisco Router as an Authoritative DNS server. When configured as an authoritative name server for its own local host table, the router listens on port 53 for DNS queries and then answers DNS queries using the permanent and cached entries in its own host table.
Careful consideration has to be given as this can consume considerable amount of resources like CPU cycles on the Cisco Router. If you are a small network and realise your Cisco ROuter is under utilised then there is a good business case to turn your router into a DNS server.
Subscribe