Search results for query: *

we want to use the BGAN as a backup for access to the VSAT modem (telnet). But heck, if I can use the BGAN to access the router, from the router I can telnet to the VSAT modem and perform settings changes.

I will have to make a network diagram to make it clear.

I drew out a diagram, it also appears that since the VSAT modem is plugged into eth0, when the BGAN is active, I wouldn't be able to get to the VSAT modem since all packets would be bypassing eth0 and going eth1.

I have one concern. When the VSAT fails and the BGAN takes over, all customer traffic will also get routed over the BGAN in this setup. The BGAN is just supposed to be for out of band access for myself to connect to the network and service the VSAT modem via a telnet to the modem. BGAN...

Version 2 - With ISPKing's fantastic suggestion: Current configuration : 638 bytes ! version 12.3 service timestamps debug datetime msec service timestamps log datetime msec no service password-encryption ! hostname SatRouter ! boot-start-marker boot-end-marker ! ! memory-size iomem 25 no aaa...

floating routes, that is great! I've never used those and would never have thought of it. It will work perfectly because when I shut down the BGAN it will set the port to down/down. I just hooked everything up in a lab and started the config. Don't need any security etc just using it to show...

Does anyone know the best way to approach setting up a 1720 router (IOS v12.3(26)) that has 2 Ethernet WICs and the single built in Ethernet port to switch between the WICs if one goes down? Each WIC will have a different satillite technology connected to it, VSAT for one and BGAN for the...

It worked great in a lab but still had issues in production, I gave up. These examples helped me out tremendously: https://www.cisco.com/en/US/products/ps6120/prod_configuration_examples_list.html

I feel your pain, I spent a month posting on forums and searching out docs on the net trying to get a reverse telnet connection working. It seems its a dying art.... I just went out and bought a few serial to ethernet converters and called it a day.

# sh access-list inside_nat0_outbound access-list inside_nat0_outbound; 11 elements; name hash: 0x467c8ce4 access-list inside_nat0_outbound line 1 extended permit ip 192.168.100.0 255.255.255.0 192.168.200.0 255.255.255.0 (hitcnt=0) 0x7d7921ae access-list inside_nat0_outbound line 2 extended...

yes logs show everything normal. ICMP being built. I even ran packet tracer and it says the traffic is allowed echo to .100 subnet and echo reply back to .101.

For some reason I can connect to my ASA via AnyConnect, once connected I can ping the ASA's IP on my LAN 192.168.100.248 and it replies. But I can't ping or telnet to any other devices like 192.168.100.1 on the same LAN. Funny thing is, if I use the webvpn portal where I setup the SSH/Telnet...

configs were fine. All along turned out to be a hub I didn't know about sitting between our data closet and my ASA. Must have been a duplex mismatch. Such an odd issue.

configs were fine. All along turned out to be a hub I didn't know about sitting between our data closet and my ASA. Must have been a duplex mismatch. Such an odd issue.

here is the loghttp://img709.imageshack.us/img709/6651/121709firewallrulesoncp.png

Here are screenshots of the firewall rules and debug blockshttp://img189.imageshack.us/img189/8672/121709firewallblocksonc.png

we are not polling the ASA's with SNMP, we are polling hosts at the branch office.

here are the configs: ASA Version 8.2(1) ! hostname branch1 enable password 8Ry2YjIyt7RRXU24 encrypted passwd 2KFQnbNIdI.2KYOU encrypted names ! interface Vlan1 nameif inside security-level 100 ip address 192.168.200.248 255.255.255.0 ! interface Vlan2 nameif outside security-level 0 ip...

still working with TAC. One thing is the problem happens when our NMS is polling across the VPN connection via SNMP UDP port 161. Log in the ASA is flooded with deny messages and thats when it gets so over worked it starts dropping packets and I even get Scanning drop rate exceeded messages...

I have an NMS in branch A that polls devices in branch B. The tunnel is up and I can ping across it, access the remote devices ASDM, even RDP into hosts at branch B. But for whatever reason the ASA in branch A keeps denying the UDP port 161 traffic. The default, out of the box ACLs are...