Hello,
When I give the command:
show fabric channel-counters
I get the following result:
slot channel rxErrors txErrorstxDrops lbusDrops
1 0 0 0 0 66239
1 1 0 0 0 65535
2
If you cannot ping the SVI try this: Create a bridge and assign the IP to the
associated BVI. Then associate the int Vlan1 with the bridge-group.
Greets
Am Mittwoch, 21. November 2007 14:01 schrieb Gabor Ivanszky:
Hello,
can you actually ping the 851's Vlan 1 interface? If the physical
I have gear in Amsterdam and in San Jose. Pushing log files from
Amsterdam to San Jose through rsync seems to top out at 7Mbps even
Is rsync using ssh to move the data? ssh has its own windowing
issues. There's a high perf fix for that which you should be able
to find via google.
Peter Lothberg [EMAIL PROTECTED] writes:
I have gear in Amsterdam and in San Jose. Pushing log files from
Amsterdam to San Jose through rsync seems to top out at 7Mbps even
Is rsync using ssh to move the data? ssh has its own windowing
issues. There's a high perf fix for that
I have gear in Amsterdam and in San Jose. Pushing log files from
Amsterdam to San Jose through rsync seems to top out at 7Mbps even
Is rsync using ssh to move the data? ssh has its own windowing
issues. There's a high perf fix for that which you should be able
to find via google.
Hi,
My Google-fu is failing me..
Scenario:
FastEthernet0 (NAT inside), IP 10.20.20.1/24
Tunnel1 (NAT outside), IP 172.16.0.1/24
DMVPN environment with EIGRP
Performing static source address translation from hosts in
10.20.20.0/24 to 192.168.20.x
interface FastEthernet0
ip address 10.20.20.1
New to me... never been working by translating internal IP to 'external IP
which is not directly connected to the router...'
If this work pretty well, it'd be good and some ideas might come up later...
rgs
a. rahman isnaini r.sutan
- Original Message -
From: Dale Shaw [EMAIL
I changed the ip route .. commands to..
ip route 192.168.20.5 255.255.255.255 Null0 name NAT
.. and it continues to work as expected. This is cleaner, but I'm
still interested in more elegant solutions. I've seen the add-route
parameter, but it doesn't appear to support /32s, and only seems to
Hello Dale:
Would it be possible to announce the aggregate with a tie-down route
similar to BGP? So, instead of a bunch of /32's, just use:
ip route 192.168.20.0 255.255.255.0 null0 250
I would assume that will propagate into OSPF and, when the traffic for
that network returns to your
