after a hard reset and set the default user / password i use the default ip for ethernet0 and set ethernet4 to dhcp when i use the sdm to ping i can ping from 10.10.10.1 to 126.96.36.199 i can also ping from 188.8.131.52 to 184.108.40.206 but can't seem to ping from 10.10.10.1 to 220.127.116.11 i have no firewall configured i have a default route 0.0.0.0 0.0.0.0 Ethernet4
a 6ya Technician can help you resolve that issue over the phone in a minute or two.
Best thing about this new service is that you are never placed on hold and get to talk to real repair professionals here in the US. click here to Talk to a Technician (only for users in the US for now) and get all the help you need. Goodluck!
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
The total sum of the Inside/Outside/ and pool address add up to 5,265. Subtract 10% and multiply by 260 to get the gender aspect of the original formula. Move the Network address to Google and download the residual code offered by the program that appears in the open window. Enter the code in the appropriate space provided and this will solve the problem by late 2015.
The long answer: You will need a device that will handle call control. That can be an ISR router (gen2 example: Cisco 1900, 2900, or 3900 series) that runs Call Manager Express, or a Cisco UC5XX Box (or even full blown CUCM, though you will still need an ISR to get out to the PSTN). The switch will work great for the infrastructure side of things though. It is capable of layer 3 routing, voice VLANs, QoS, and PoE. But you WILL need something for call control.
You cannot connect two separate ISPs unless you have a router with two WAN ports
For redundancy, is BGP an option? It is very unlikely that two ISPs will
permit your router to form any interior routing protocol neighborships
with their routers for the purpose of link failure recovery.
A very basic (and usually undesirable) alternative is to configure a
static default route to one ISP, and a floating static default route to
the other ISP. The syntax for that in your case might be:
ip route 0.0.0.0 0.0.0.0 Ethernet0 1
ip route 0.0.0.0 0.0.0.0 Serial1 2
The problem here is that there is only physical link failure detection
(ie: if someone yanks the cable connected to Ethernet0, it will switch
over correctly, but if the ISP's equipment beyond the direct physical
connection goes down, it won't switch over at all).
I'm assuming the serial and ethernet connections themselves are
provisioned already though, correct? If not, as long as you're very
specific about what you're trying to do (ie: as others said,
encapsulation type in use, clock rate, etc.), then if you want you can
email me the info and I might be able to design something for you.
with a dialer interface:
interface Dialer0 description $FW_OUTSIDE$ ip unnumbered Ethernet0 ip access-group sdm_dialer0_in in no ip redirects no ip unreachables no ip proxy-arp encapsulation ppp ip route-cache flow dialer pool 1 dialer-group 1 ppp authentication chap callin ppp chap hostname xxxxxxxxxxxxxxx ppp chap password xxxxxxxxxxxxxxxxxxx
You seem to have the last resort (o.o.o.o) set to VLAN1 which is set as an inside interface.
Is VLAN1 connected to the outside router or internet backbone?
If not, change the last resort to the outside Ethernet port.