Not sure if I understand your last post, but one suggestion - before finishing the simulation always double check your config using "sh run" or "sh start"
Peter Mesjar
CCNP, A+ certified
pmesjar@centrum.sk
"The only true wisdom is in knowing you know nothing.
You already wrote them: QoS and STP.
I'll just add - everything about STP, as well as VLANs, basic Security (AAA,802.1x,access-lists), SPAN ...
Check out this:
http://www.cisco.com/warp/public/10/wwtraining/certprog/testing/current_exams/642-811.html
Peter Mesjar
CCNP, A+ certified...
If you need better and centralized control of creating and deleting VLANs, configure VTP (Virtual Trunking Protocol). This way one switch will act as VTP Server, sending VLAN config info to VTP clients and only VTP Server can delete VLANs. However be aware of that even VTP client can erase VLAN...
One more thing - is NVRAM replaceable in 800 series routers? Maybe you would be fine by just replacing the NVRAM with new one than buying the whole router.
Peter Mesjar
CCNP, A+ certified
pmesjar@centrum.sk
"The only true wisdom is in knowing you know nothing.
> Is it a problem that 3 routers are port forwarding? Is there a technical reason why that wont work?
I can't think of any issue if it is configured correctly. To configure port forward on Cisco router I think this should do it for your setup:
ip nat inside source static tcp 10.0.0.4 80...
0x2102 tells the router to look for boot command in NVRAM and - if not specified otherwise by boot command - load IOS from Flash
0x2142 tells the router to boot without loading startup config from NVRAM and load IOS from Flash
Peter Mesjar
CCNP, A+ certified
pmesjar@centrum.sk
"The only true...
Search the net - there are tons of free ones. If you want to pay, there is Testking, Boson... but don't forget experience using real routers!!!
Peter Mesjar
CCNP, A+ certified
pmesjar@centrum.sk
"The only true wisdom is in knowing you know nothing.
Well I guess you had a book for older exam. Check out this one:
http://www.ciscopress.com/title/158705146X#
If you are considering a book, one word - CiscoPress:)
Peter Mesjar
CCNP, A+ certified
pmesjar@centrum.sk
"The only true wisdom is in knowing you know nothing.
You are mixing IP addresses too much. From the routing table I can see you use:
192.168.3.0/30 <-- why? why not rather eg. 192.168.4.8/30?
192.168.4.0/30
192.168.4.4/30
192.168.7.0/24 <-- why? why not rather eg. 192.168.2.0/24?
and why not start from 192.168.0.0?
10.1.3.0/24
10.1.2.0/24...
sorry not:
ip nat inside static tcp 10.1.1.101 3389 192.168.1.2 3389
but:
ip nat inside source static tcp 10.1.1.101 3389 192.168.1.2 3389
Peter Mesjar
CCNP, A+ certified
pmesjar@centrum.sk
"The only true wisdom is in knowing you know nothing.
Would that allow me to map another port to another node using the same 192.x.x.2 addy?"
Yes it will, however your config is wrong. Port forwarding command syntax is:
ip nat inside source static tcp|udp INSIDE-IP INSIDE-PORT OUTSIDE-IP OUTSIDE-PORT
For you:
ip nat inside static tcp 10.1.1.101...
It can take about a minute till switches put their trunked ports up and running, which is not because of trunk config but because of STP. However since you want trunking, you are going to separate users to VLANs, aren't you? So there will also be end host disruption as you will be assigning...
As long as you don't want to allow interVLAN communication and you have at 4 ports on firewall, two for each company, I can't think of any problem with this. But maybe a firewall can be an issue, in which case you will need a separate firewall for each company. However there is absolutely no...
If 192.168.1.3 is not really configured, your Cisco 3661 will not know how to handle packets with this destination address. In other words port forward to fictious IP addresses does not work. How about creating a forward to 192.168.1.2 instead of 192.168.1.3? What masks are you using with...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.