192.168.x.x is a private address scheme, so you can take 192.168.1.x/24 or 192.168.2.x/24 and so on.
You also mention static addresses, but I assume you mean external addresses. This doesn't really matter because you are already doing NAT/PAT (network address translation, port address...
You can do floating default routes with track statements, like this:
!
ip sla monitor 100
type echo protocol ipIcmpEcho 10.100.7.1 source-interface FastEthernet0/1
timeout 500
frequency 3...
interface Gigx/x
description Trunk to Core
switchport trunk encapsulation dot1q
switchport mode trunk
You'll also need to add it to you your VTP domain.
Yeah a 1700 should work fine. Reliable Static Routing Backup is what I recommended, and as long as you have it setup right (pinging the next-hop of your default-gateway) it works really awesome.
1900 is much older and is just a 'simple' switch. 2900 series allows you to break up the switch into numerous virtual-lans. Also, I think the 1900 was only 10mbs, whereas the 2900 is 10/100.
Wow Burt, this is the first time I've ever seen you post a question. Anyways, have you run a port scan on that port from the outside to see if maybe it's being blocked by your ISP?
Depending on what kind of routers you have, you can probably get away with some floating static routes with some track statements. Let us know what kind router(s) you have
We have HSRP running on our corp switches (4500's) with multiple vlans. Every other vlan is set to be primary each switch:
SWITCH 1:
Vl1 1 100 P Active local 172.20.1.3 172.20.1.1
Vl100 1 90 Standby 192.168.100.203 local 192.168.100.201...
You can set up policy routing for that. However, there is the possibility that if the link goes down on one of those routes, then the users will be black holed.
When reading access-lists always remember that they are written "FROM" first, followed by who they are going "TO"
So, in the first acl it reads:
Permit tcp FROM anywhere equaling WWW, TO anywhere.
the second acl reads a bit different:
Permit tcp FROM anywhere, TO anywhere equaling WWW.
There are a couple of programs that will do it (like solarwinds). However, if you are inheriting this network I'd suggest you wipe out all of the old passwords and start out fresh. This is definitly a security issue.
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.