Re: snmp traps - send to more than one nms [7:56015]
Umar, I THINK you need to first issue the snmp-server enable command and then issue a separate snmp-server host command for each network management server. KR From: Umar Ahmed Reply-To: Umar Ahmed To: [EMAIL PROTECTED] Subject: snmp traps - send to more than one nms [7:56015] Date: Mon, 21 Oct 2002 13:42:03 GMT All, How do you enable any cisco router to send traps to more than one nms. Rgds, Umar. _ Internet access plans that fit your lifestyle -- join MSN. http://resourcecenter.msn.com/access/plans/default.asp Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=56020t=56015 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Telnet session traversing PIX are timingout [7:53490]
Hi, I have telnet sessions that orginate on the internal side of a PIX to a server on the external side that are timing out (after 60 seconds). Is there a command to increase the timeout period for telnet? If there is what is the max? TIA KR _ Join the worlds largest e-mail service with MSN Hotmail. http://www.hotmail.com Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=53490t=53490 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: Telnet session traversing PIX are timingout [7:53490]
Eddie, There is no VPN involved. I don't think its a MTU problem. I am trying to find a similar command to the IOS Firewall's ip inspect name ... (Inspection rule for CBAC) for the PIX. I need to increase the idle timeout for the telnet application. However, I found your MTU explaination very informative. Someone mentioned to me about a VPN/MTU problem but did not go deeper into the cause. How did you resolve this MTU problem? Is there any writeups on this problem? KR From: Caballero, Eddie To: 'KM Reynolds' , [EMAIL PROTECTED] Subject: RE: Telnet session traversing PIX are timingout [7:53490] Date: Tue, 17 Sep 2002 11:26:07 -0700 I've seen this issue before with SSH timing out over a perfectly good connection without packet loss. The problem was with the MTU size being too small and the packet was getting dropped. The packet was going through a VPN tunnel through the network to a VPN concentrator. Here's an example. The telnet packet was 1435 bytes in size including all the headers. The Router maximum MTU was 1456 for example. So far so good... Looks like it should get through, correct ports are open etc.. Now the VPN encryption adds an extra 25 bytes for example ( I don't have exact numbers). Now you have a packet that is Encapsulated with encryption for a total size of 1460 bytes. Oh and what also happens is the VPN will put a DO NOT Fragment flag on the packet, because of the encryption. Whats going to happen once that packet hits the router with an MTU size of 1456? It gets dropped because the packet is too large. What happens to the telnet or SSH session, is it starts dropping packets and then times out. It doesn't receive and ACK's from the other end and thinks it is timing out. So A. Is there VPN involved? If so, could be MTU issue. B. Check the MTU size.Send some large sized pings over 1400 bytes in size with the Do not Fragment Flag. Find out if and where the MTU is set too low. C. Of course check for packet loss or extreme latency. Welp hopefully this helps from my experiences with this type of issue. Eddie Corio Inc. -Original Message- From: KM Reynolds [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 17, 2002 8:33 AM To: [EMAIL PROTECTED] Subject: Telnet session traversing PIX are timingout [7:53490] Hi, I have telnet sessions that orginate on the internal side of a PIX to a server on the external side that are timing out (after 60 seconds). Is there a command to increase the timeout period for telnet? If there is what is the max? TIA KR _ Join the worlds largest e-mail service with MSN Hotmail. http://www.hotmail.com _ Join the worlds largest e-mail service with MSN Hotmail. http://www.hotmail.com Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=53522t=53490 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
LAN(ADSL) to LAN(ADSL) VPN Router Config [7:47085]
Hi all, I have been trying to search CCO and the archives( think the links are down at the moment) for a IpSec VPN LAN (1720 with ADSL) to LAN (1720 with ADSL) router configuration using Pre-share keys. Can someone post or point where I can find this specfic configuration. I have not configured a ADSL interface and would like to understand this better. K Reynolds _ Join the worlds largest e-mail service with MSN Hotmail. http://www.hotmail.com Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=47085t=47085 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: Switch Design Question [7:39888]
The reason for switch3 is, switch2 ran out of ports when the campus site(switch1) was added. All the equipment is in one room. Switch1 to switch2 is connected via fiber because switch1 is at a remote campus building. The Internet connection is to be added. The reason for having the Internet connection at the location of switch4 is that is the only site that ADSL is available. I was concerned about the traffic that was destined to the Internet gateway from the source switch1. I thought there maybe a bottleneck at the point where data is passed from switch2 to switch3. It seems with this design there should not be any latency issues. If I could ask you another question,(possible future addition) what if switch1 was located on another subnet. The subnet is connected via ISDN(128K). Does anyone see any problems with traffic going across an ISDN link to switch to wireless link to switch to Internet. Thanks KM From: Priscilla Oppenheimer Reply-To: Priscilla Oppenheimer To: [EMAIL PROTECTED] Subject: Re: Switch Design Question [7:39888] Date: Fri, 29 Mar 2002 13:12:32 -0500 Do you know if there was a reason for Switch 3 being in the design? That's what I would try to find out Maybe it was necessary because Switch 2 is located in a wiring closet, whereas Switch 3 and the Wireless Bridge are in the main distribution frame. Or maybe Switch 2 only has fiber-optic ports (not likely, but you never know). Or maybe Switch 3 also connects a server farm. Or maybe the network designer wanted to keep things modular, which is a good idea. Maybe the designer added Switch 3 to try to contain problems related to the wireless bridge being flaky. Or maybe it's there just because that's the equipment that was available and there's no budget for a bigger switch. These days switches are so fast that I don't think you need to be too concerned about the switch adding any noticeable delay. But if there's no good reason for it being there, then you're right to question it. Simplifying the design would have some advantages: fewer devices to fail, a network design that is easier to understand and troubleshoot, etc. If you do buy another switch, you could really go wild and design a topology with more redundancy and fail-over in it! Use all the switches maybe. Priscilla At 09:26 AM 3/29/02, KM Reynolds wrote: Hi All, I am looking at this configuration: [PC]---[Switch1]---Fiber---[Switch2]---[Switch3]---[WirelessBridge]---distance2miles---[WirelessBridge]---[4Switch10Mb]---[Router]---[ISPInternet] The switches are all consist of 10Mb ports. The question. Whould it not be a better design to take out switch2 and switch3 and replace it with one switch with more ports. This would elimate one switch to traverse when the clients are accessing the Internet. Any thoughts on this or if you see other things that may help with the design. TIA KM _ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx Priscilla Oppenheimer http://www.priscilla.com _ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=39943t=39888 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: Switch Design Question [7:39888]
Mark, I should have mentioned, switch1 is at a campus site (100meters), and switch4 is at a remote site. And exactly switch3 was added because they ran out of ports. At the moment there is no problems, however the Internet connection is to be added soon. The reason for putting it at the location of switch4, that is the only location DSL is available. Hope you had a Great Easter KM From: Mark Odette II Reply-To: Mark Odette II To: [EMAIL PROTECTED] Subject: RE: Switch Design Question [7:39888] Date: Fri, 29 Mar 2002 15:59:18 -0500 I was gonna say, perhaps the Switch2 has a Fiber connection, and thus the Switch3 was put in place because of lacking port density. Is it going to be cost effective to by a replacement larger switch with a Fiber port on it -just- so you can consolidate space/hops?? Of course, this is assuming that the distance b/t SW1 and SW2 is more than 100 meters, perhaps between buildings. If this is not the case, and the Fiber is simply providing a Fast Switch-to-Switch uplink and they are within the same closet... I would think that, providing Money is not an issue, than why not consolidate all switches into one big switch. I agree though... if it's just a thang about speed to the 'Net then the Switches are the least of your worries... unless they are old, flaky, begging to be decommissioned so they can RIP :) I guess the big question is, where is each switch Geographically located, and of course... What Problem Are You Trying To Solve?!?! :-) Happy Easter folks! (for those who observe it) Mark -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Howard C. Berkowitz Sent: Friday, March 29, 2002 10:22 AM To: [EMAIL PROTECTED] Subject: Re: Switch Design Question [7:39888] At 9:26 AM -0500 3/29/02, KM Reynolds wrote: Hi All, I am looking at this configuration: [PC]---[Switch1]---Fiber---[Switch2]---[Switch3]---[WirelessBridge]---dista nce2miles---[WirelessBridge]---[4Switch10Mb]---[Router]---[ISPInternet] The switches are all consist of 10Mb ports. The question. Whould it not be a better design to take out switch2 and switch3 and replace it with one switch with more ports. This would elimate one switch to traverse when the clients are accessing the Internet. Any thoughts on this or if you see other things that may help with the design. TIA KM Possibly. But the largest source of delay is probably your Internet link, unless it's 10 Mbps or faster. Some of the questions to answer about replacing the switches: Do the separate switches pass traffic (e.g., printer) that stays in their workgroup? Are there any distance restrictions between switch 2 and 3? Do separate switches help you distinguish between business units? Is the required number of ports due to increase, so you need to add capacity? _ Send and receive Hotmail on your mobile device: http://mobile.msn.com Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=39944t=39888 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Switch Design Question [7:39888]
Hi All, I am looking at this configuration: [PC]---[Switch1]---Fiber---[Switch2]---[Switch3]---[WirelessBridge]---distance2miles---[WirelessBridge]---[4Switch10Mb]---[Router]---[ISPInternet] The switches are all consist of 10Mb ports. The question. Whould it not be a better design to take out switch2 and switch3 and replace it with one switch with more ports. This would elimate one switch to traverse when the clients are accessing the Internet. Any thoughts on this or if you see other things that may help with the design. TIA KM _ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=39888t=39888 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: Multilinking more than two ISDN channels [7:33493]
Steve, I looked into the multilink-group command. On CCO I found documentation titled Configuring MLP on Multiple ISDN BRI Interfaces. This looks like what I was looking for. As per the doc it states to enable multilink PPP on multiple ISDN BRI interfaces, I need to set up a dialer rotary interface and configure it for multilink PPP. Then to configure the BRI interfaces separately and add them to the same rotary group. The example shown is as follows: interface BRI0 no ip address encapsulation ppp dialer idle-timeout 2147483 dialer rotary-group 0 dialer load-threshold 1 either ppp multilink interface BRI1 no ip address encapsulation ppp dialer idle-timeout 2147483 dialer rotary-group 0 dialer load-threshold 1 either ppp multilink interface dialer0 ip address 10.x.x.x 255.255.255.252 encapsulation ppp dialer in-band dialer idle-timeout 2147483 dialer map ip next-hop name hostname broadcast dial-string dialer load-thresold 1 either dialer-group 1 ppp authentication chap ppp multilink It looks like there are number of ways to configure multilink PPP on multiple BRI interfaces, such as multilink bundle and dialer profiles. Thank you for your assistance, by pointing out multilink-group, it helped to find the doc. KM From: Steven A Ridder To: 'KM Reynolds' Subject: RE: Multilinking more than two ISDN channels [7:33493] Date: Mon, 28 Jan 2002 18:27:52 -0500 I thought to bundle interfaces together in a multilink group, you needed the multilink group # command in each interface and apply that to multilink. -Original Message- From: KM Reynolds [mailto:[EMAIL PROTECTED]] Sent: Monday, January 28, 2002 6:04 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Multilinking more than two ISDN channels [7:33493] Below is the config for the single BRI. interface BRI0 no ip address encapsulation ppp dialer pool-member 1 max-link 2 isdn spid1 xxx isdn spid2 xxx isdn switch-type basic-ni ppp multilink interface dialer 1 ip address 10.x.x.x 255.255.255.252 encapsulation ppp dialer remote-name dialer pool 1 dialer idle-timeout 2147483 dialer load-thresold 1 either dialer-group 1 ppp authentication chap If BRI1 was installed. Would you need to configure it the same as BRI0, but change the dialer pool-member 1 max-link to 4? Sounds to easy. From: Steven A. Ridder Reply-To: Steven A. Ridder To: [EMAIL PROTECTED] Subject: Re: Multilinking more than two ISDN channels [7:33493] Date: Mon, 28 Jan 2002 17:27:25 -0500 How are the Bri's in a multilink group? MADMAN wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... Here ya go, an example that I did some time ago, the 12.1 code was buggy. The gist of it is you set up a dialer and attach the bri's via the dialer pool. This may not be on CCO but it works. Dave KM Reynolds wrote: No offence, I just thought I was missing something. I have read your emails in the past, and I do know you know what you are talking about. I aslo know you can bind PRIs, I just haven't heard of multilinking BRIs. I looked in the archives and tried searching the Cisco Web Site, but had no luck. So I thought it was a good question and posted it. KM David Madland Sr. Network Engineer CCIE# 2016 Qwest Communications Int. Inc. [EMAIL PROTECTED] 612-664-3367 Emotion should reflect reason not guide it This config is an ISDN dial backup binding three BRIs together 9/2000 ! ! Last configuration change at 14:54:55 UTC Mon Sep 25 2000 ! NVRAM config last updated at 14:55:07 UTC Mon Sep 25 2000 ! version 12.1 service timestamps debug uptime service timestamps log datetime localtime no service password-encryption ! hostname CL_Spokane ! logging buffered 4096 informational enable password converge*clpriv ! username CL_Bristol password 0 converge*clpriv ! ip subnet-zero ip cef no ip domain-lookup ip host routerA 10.1.254.254 ! ipx routing 0030.945d.35e1 isdn switch-type basic-5ess ! !interface Loopback0 ip address 10.1.253.253 255.255.255.0 ! interface Loopback100 ip address 50.1.1.1 255.255.255.0 ! interface Serial2/0.21 point-to-point description PVC to Bristol ip address 172.31.254.1 255.255.255.0 ipx network AAA frame-relay interface-dlci 21 ! interface BRI3/0 description ISDN CKT#__ ISDN backup to routera's BRI3/0 bandwidth 128 no ip address ip load-sharing per-packet encapsulation ppp dialer pool-member 1 isdn switch-type basic-ni isdn spid1 x xxx isdn spid2 x xxx no fair-queue ppp authentication chap ! interface BRI3/1 description ISDN CKT#__ ISDN backup to Bristol's BRI3/1 bandwidth 128 no ip address ip load-sharing per-packet encapsulation ppp dialer pool-member 1 isdn switch-type
Multilinking more than two ISDN channels [7:33493]
Hi, Is it possible to multilink more than two BRI channels? Currently, installed is a BRI ISDN link between two sites. Using ppp multilink, etc., the two 64kbs channels are aggregated. I am wondering if a second BRI ISDN link was installed between the two sites, it is possible to aggregate BRI0 and BRI1 to basically create a link that is 256kbs? I look forward on reading anyones thoughts on this. KM _ Join the worlds largest e-mail service with MSN Hotmail. http://www.hotmail.com Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=33493t=33493 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: Multilinking more than two ISDN channels [7:33493]
No offence, I just thought I was missing something. I have read your emails in the past, and I do know you know what you are talking about. I aslo know you can bind PRIs, I just haven't heard of multilinking BRIs. I looked in the archives and tried searching the Cisco Web Site, but had no luck. So I thought it was a good question and posted it. KM From: MADMAN Reply-To: [EMAIL PROTECTED] To: KM Reynolds Subject: Re: Multilinking more than two ISDN channels [7:33493] Date: Mon, 28 Jan 2002 15:12:53 -0600 I first answered yes and my point was not only can you bind multiple BRIs, you can even bind PRIs. Trust me I really do know the differance Dave KM Reynolds wrote: Madman, I was talking about 2x BRI interfaces. Please tell me how you get PRI from BRI? KM From: MADMAN Reply-To: [EMAIL PROTECTED] To: KM Reynolds CC: [EMAIL PROTECTED] Subject: Re: Multilinking more than two ISDN channels [7:33493] Date: Mon, 28 Jan 2002 14:41:25 -0600 Yes, hell I once got the opportunity to multilink 4 PRI's. Dave KM Reynolds wrote: Hi, Is it possible to multilink more than two BRI channels? Currently, installed is a BRI ISDN link between two sites. Using ppp multilink, etc., the two 64kbs channels are aggregated. I am wondering if a second BRI ISDN link was installed between the two sites, it is possible to aggregate BRI0 and BRI1 to basically create a link that is 256kbs? I look forward on reading anyones thoughts on this. KM _ Join the worlds largest e-mail service with MSN Hotmail. http://www.hotmail.com [EMAIL PROTECTED] -- David Madland Sr. Network Engineer CCIE# 2016 Qwest Communications Int. Inc. [EMAIL PROTECTED] 612-664-3367 Emotion should reflect reason not guide it _ Join the worlds largest e-mail service with MSN Hotmail. http://www.hotmail.com -- David Madland Sr. Network Engineer CCIE# 2016 Qwest Communications Int. Inc. [EMAIL PROTECTED] 612-664-3367 Emotion should reflect reason not guide it _ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=33505t=33493 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: Multilinking more than two ISDN channels [7:33493]
Below is the config for the single BRI. interface BRI0 no ip address encapsulation ppp dialer pool-member 1 max-link 2 isdn spid1 xxx isdn spid2 xxx isdn switch-type basic-ni ppp multilink interface dialer 1 ip address 10.x.x.x 255.255.255.252 encapsulation ppp dialer remote-name dialer pool 1 dialer idle-timeout 2147483 dialer load-thresold 1 either dialer-group 1 ppp authentication chap If BRI1 was installed. Would you need to configure it the same as BRI0, but change the dialer pool-member 1 max-link to 4? Sounds to easy. From: Steven A. Ridder Reply-To: Steven A. Ridder To: [EMAIL PROTECTED] Subject: Re: Multilinking more than two ISDN channels [7:33493] Date: Mon, 28 Jan 2002 17:27:25 -0500 How are the Bri's in a multilink group? MADMAN wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... Here ya go, an example that I did some time ago, the 12.1 code was buggy. The gist of it is you set up a dialer and attach the bri's via the dialer pool. This may not be on CCO but it works. Dave KM Reynolds wrote: No offence, I just thought I was missing something. I have read your emails in the past, and I do know you know what you are talking about. I aslo know you can bind PRIs, I just haven't heard of multilinking BRIs. I looked in the archives and tried searching the Cisco Web Site, but had no luck. So I thought it was a good question and posted it. KM David Madland Sr. Network Engineer CCIE# 2016 Qwest Communications Int. Inc. [EMAIL PROTECTED] 612-664-3367 Emotion should reflect reason not guide it This config is an ISDN dial backup binding three BRIs together 9/2000 ! ! Last configuration change at 14:54:55 UTC Mon Sep 25 2000 ! NVRAM config last updated at 14:55:07 UTC Mon Sep 25 2000 ! version 12.1 service timestamps debug uptime service timestamps log datetime localtime no service password-encryption ! hostname CL_Spokane ! logging buffered 4096 informational enable password converge*clpriv ! username CL_Bristol password 0 converge*clpriv ! ip subnet-zero ip cef no ip domain-lookup ip host routerA 10.1.254.254 ! ipx routing 0030.945d.35e1 isdn switch-type basic-5ess ! !interface Loopback0 ip address 10.1.253.253 255.255.255.0 ! interface Loopback100 ip address 50.1.1.1 255.255.255.0 ! interface Serial2/0.21 point-to-point description PVC to Bristol ip address 172.31.254.1 255.255.255.0 ipx network AAA frame-relay interface-dlci 21 ! interface BRI3/0 description ISDN CKT#__ ISDN backup to routera's BRI3/0 bandwidth 128 no ip address ip load-sharing per-packet encapsulation ppp dialer pool-member 1 isdn switch-type basic-ni isdn spid1 x xxx isdn spid2 x xxx no fair-queue ppp authentication chap ! interface BRI3/1 description ISDN CKT#__ ISDN backup to Bristol's BRI3/1 bandwidth 128 no ip address ip load-sharing per-packet encapsulation ppp dialer pool-member 1 isdn switch-type basic-ni isdn spid1 x xxx isdn spid2 x xxx no fair-queue ppp authentication chap ! interface BRI3/2 description ISDN CKT#__ ISDN backup to Bristol's BRI3/2 bandwidth 128 no ip address ip load-sharing per-packet encapsulation ppp no ip mroute-cache dialer pool-member 1 isdn switch-type basic-ni isdn spid1 xx xxx isdn spid2 xx xxx no fair-queue ppp authentication chap ! interface BRI3/3 no ip address shutdown isdn switch-type basic-ni ! interface Dialer1 ip address 10.100.200.1 255.255.255.0 ip load-sharing per-packet encapsulation ppp no ip mroute-cache dialer remote-name Router12 dialer pool 1 dialer idle-timeout 60 dialer string 158 dialer string 159 dialer string 156 dialer string 157 dialer string 154 dialer string 155 dialer load-threshold 3 either dialer max-call 6 dialer-group 1 ipx network FBEEF ppp authentication chap ppp multilink ! router eigrp 100 redistribute static network 10.0.0.0 network 172.16.0.0 network 172.31.0.0 no auto-summary no eigrp log-neighbor-changes ! ip classless ip route 0.0.0.0 0.0.0.0 172.31.254.2 ip route 0.0.0.0 0.0.0.0 Dialer1 200 ip route 20.1.1.1 255.255.255.255 Dialer1 no ip http server ! access-list 101 deny eigrp any any access-list 101 permit ip any any dialer-list 1 protocol ip list 101 ! ! ! ! line con 0 transport input none line aux 0 exec-timeout 45 0 password diverge*clterm modem InOut modem autoconfigure type usr_sportster transport input all speed 115200 flowcontrol hardware line vty 0 4 exec-timeout 0 0 password diverge*clterm login ! end CL_Spokane# sho ver Cisco Inte
1924 Switch: Takes long time to ping device after connecting to [7:24645]
Hi, I installed a Catalyst 1924 switch on the LAN. It seems to work ok, however, I am concerned, because when I first plug a device (any device) into a new switch port. It takes a long time (minutes) before I can ping it. After that if I unplug it and reconnect I can ping immediately. Does anyone know if this is normal? Thanks in advance. KM _ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=24645t=24645 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: Directly connected ethernet interface [7:10998]
Exactly, the server is on the ethernet where the bridge is. The router at the remote side does have another ethernet(e1) interface, but it is being used, and any device connected to this e1, I am able to ping, via the ISDN backup link, when I disconnect the wireless. If this e1 was not being used I would have plugged the remote bridge to e1 and segment the wireless bridges. So, it surely looks like I need to add a router to segment the wireless bridges. Or I wonder, I can place a secondary IP address on the remote router, and segment the wireless bridges that way, this way traffic would get to the remote bridge, go to the remote router on the secondary ip, then route/arp to the server. This may work, what do you think? I know adding a secondary address is to be avoided and to be used for only for temporary situations. I am now very curious, on ways to get this to work. However, in the end, for scalability, support and simplicity, I think adding a router or another ethernet interface to the remote router and segment the bridges is the way to proceed. I hope the secondary IP part makes sense. KM From: Priscilla Oppenheimer To: KM Reynolds ,[EMAIL PROTECTED] Subject: Re: Directly connected ethernet interface [7:10998] Date: Wed, 04 Jul 2001 19:00:58 -0700 Well, the parade is over, and now I'm _really_ tired, but, I got to wondering again. What problem are you trying to solve? Why doesn't the EIGRP route go away anyway, even though e1 is still up. The local router should stop hearing EIGRP hellos from the remote router if the wireless link between them is down. Convergence might not be fast (three hellos must fail) but it should still work. You do have a router at the remote side too, don't you? Is it running EIGRP? Oh, I get it. The server is not on the other side of the router at the remote site. It's on a switch on the Ethernet where the bridge is. Can you move the server to the other side of the router? Priscilla At 08:46 PM 7/4/01, KM Reynolds wrote: Oh yes, you all have a holiday. Happy 4TH of July (Everyone). I shall wait to see if any CCIEs reply. If not I think segmenting the wireless bridges is the way to go, I feel bridging is taking a step back. Thanks KM From: Priscilla Oppenheimer To: KM Reynolds ,[EMAIL PROTECTED] Subject: Re: Directly connected ethernet interface [7:10998] Date: Wed, 04 Jul 2001 09:12:25 -0700 Sitting here at Starbucks, using wireless, waiting for the 4th of July parade My brain isn't working too well. The latte wore off hours ago. But it occurs to me that Aironet is bridging, as you know. The routed network doesn't know when a bridged network goes down. Could you do this area of the network with all bridging? Could the ISDN link use bridging also, in other words? I know bridging over ISDN is supported. The convergence might be so slow, however, that you could pull the e1 interface in about the same timeframe (if you knew to do it though.) I can't think of any other solution (besides the one you mentioned of adding a router). It's an interesting design question. Maybe one of the CCIEs on the list will answer. Priscilla At 11:35 AM 7/4/01, KM Reynolds wrote: Hi Everyone, Need you help. I have a server that is on a remote LAN. To ping the server, the traffic goes in the local router(gateway) e0, out e1, to a local Aironet wireless bridge, to the remote Aironet wireless bridge, to a switch, to server. Works great. Currently, there is also a link to the remote site, an ISDN, from the local router to a remote router. We would like to use this ISDN as a backup to wireless connection. The routers are configured to use EIGRP to route between the wireless, and floating routes are set with higher administrative distance so when the EIGRP disappears out of the routing table the floating routes route via the ISDN. All works, when the ethernet (e1) is shutdown. When I disconnect the wireless at the remote, the ISDN comes up. The problem is, the route to the directly connected ethernet LAN is still in the routing table (C 192.168.30.128 255.255.255.128 is directly connected, Ethernet1). So traffic still flows out of e1, and I guess when it reaches the remote wireless bridge, it is discarded, that where the connection is down. Is there anyway around this, is there a way for the e1 to detect the path is down or is my only option to place a router and segment the wireless bridge link. Any help would be great. Thanks KM _ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Priscilla Oppenheimer http://www.priscilla.com _ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Priscilla Oppenheimer http://www.priscilla.com
Re: Directly connected ethernet interface [7:10998]
I am going to advise, the customer(when back from vacation) that if they would like to have an ISDN backup fully working, they need to add a router to separate the wireless bridges. Thanks, I will you all posted as to the solution. KM From: Priscilla Oppenheimer To: KM Reynolds ,[EMAIL PROTECTED] Subject: Re: Directly connected ethernet interface [7:10998] Date: Thu, 05 Jul 2001 09:15:37 -0700 I think the secondary address could work as a workaround. It would be a way to logically place the server on its own network. I think that any solution of that kind is sort of a kludge, though, (no offence). The design should be fixed. It's screwy to have a server sitting on that link between the two sites. Logically that link between e1 on the local router and e0 on the remote router is really a point-to-point wide-area circuit. It just happens to be Ethernet because the Aironet bridges use Ethernet. Placing a server on that link is like placing a server on a WAN link, if that were possible. I agree that the best solution is to segment off that WAN LAN link between the sites. It should be a point-to-point link with no servers. You could add a router, but it would be cheaper to just move that server, wouldn't it? If I have jumped to incorrect conclusions (based on very little data about your actual network), I apologize. Still recovering from Independence Day! ;-) Thanks for bringing this interesting scenario to our attention. Please keep us posted on the solution you decide on. Priscilla At 11:06 AM 7/5/01, KM Reynolds wrote: Exactly, the server is on the ethernet where the bridge is. The router at the remote side does have another ethernet(e1) interface, but it is being used, and any device connected to this e1, I am able to ping, via the ISDN backup link, when I disconnect the wireless. If this e1 was not being used I would have plugged the remote bridge to e1 and segment the wireless bridges. So, it surely looks like I need to add a router to segment the wireless bridges. Or I wonder, I can place a secondary IP address on the remote router, and segment the wireless bridges that way, this way traffic would get to the remote bridge, go to the remote router on the secondary ip, then route/arp to the server. This may work, what do you think? I know adding a secondary address is to be avoided and to be used for only for temporary situations. I am now very curious, on ways to get this to work. However, in the end, for scalability, support and simplicity, I think adding a router or another ethernet interface to the remote router and segment the bridges is the way to proceed. I hope the secondary IP part makes sense. KM From: Priscilla Oppenheimer To: KM Reynolds ,[EMAIL PROTECTED] Subject: Re: Directly connected ethernet interface [7:10998] Date: Wed, 04 Jul 2001 19:00:58 -0700 Well, the parade is over, and now I'm _really_ tired, but, I got to wondering again. What problem are you trying to solve? Why doesn't the EIGRP route go away anyway, even though e1 is still up. The local router should stop hearing EIGRP hellos from the remote router if the wireless link between them is down. Convergence might not be fast (three hellos must fail) but it should still work. You do have a router at the remote side too, don't you? Is it running EIGRP? Oh, I get it. The server is not on the other side of the router at the remote site. It's on a switch on the Ethernet where the bridge is. Can you move the server to the other side of the router? Priscilla At 08:46 PM 7/4/01, KM Reynolds wrote: Oh yes, you all have a holiday. Happy 4TH of July (Everyone). I shall wait to see if any CCIEs reply. If not I think segmenting the wireless bridges is the way to go, I feel bridging is taking a step back. Thanks KM From: Priscilla Oppenheimer To: KM Reynolds ,[EMAIL PROTECTED] Subject: Re: Directly connected ethernet interface [7:10998] Date: Wed, 04 Jul 2001 09:12:25 -0700 Sitting here at Starbucks, using wireless, waiting for the 4th of July parade My brain isn't working too well. The latte wore off hours ago. But it occurs to me that Aironet is bridging, as you know. The routed network doesn't know when a bridged network goes down. Could you do this area of the network with all bridging? Could the ISDN link use bridging also, in other words? I know bridging over ISDN is supported. The convergence might be so slow, however, that you could pull the e1 interface in about the same timeframe (if you knew to do it though.) I can't think of any other solution (besides the one you mentioned of adding a router). It's an interesting design question. Maybe one of the CCIEs on the list will answer. Priscilla At 11:35 AM 7/4/01, KM Reynolds wrote: Hi Everyone, Need you help. I have a server that is on a remote LAN. To ping the server, the traffic goes in the local router(gateway) e0, out e1, to a local Aironet wireless bridge, to the remote Aironet wireless bridge, to a switch, to server
Directly connected ethernet interface [7:10998]
Hi Everyone, Need you help. I have a server that is on a remote LAN. To ping the server, the traffic goes in the local router(gateway) e0, out e1, to a local Aironet wireless bridge, to the remote Aironet wireless bridge, to a switch, to server. Works great. Currently, there is also a link to the remote site, an ISDN, from the local router to a remote router. We would like to use this ISDN as a backup to wireless connection. The routers are configured to use EIGRP to route between the wireless, and floating routes are set with higher administrative distance so when the EIGRP disappears out of the routing table the floating routes route via the ISDN. All works, when the ethernet (e1) is shutdown. When I disconnect the wireless at the remote, the ISDN comes up. The problem is, the route to the directly connected ethernet LAN is still in the routing table (C 192.168.30.128 255.255.255.128 is directly connected, Ethernet1). So traffic still flows out of e1, and I guess when it reaches the remote wireless bridge, it is discarded, that where the connection is down. Is there anyway around this, is there a way for the e1 to detect the path is down or is my only option to place a router and segment the wireless bridge link. Any help would be great. Thanks KM _ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=10998t=10998 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: Directly connected ethernet interface [7:10998]
Oh yes, you all have a holiday. Happy 4TH of July (Everyone). I shall wait to see if any CCIEs reply. If not I think segmenting the wireless bridges is the way to go, I feel bridging is taking a step back. Thanks KM From: Priscilla Oppenheimer To: KM Reynolds ,[EMAIL PROTECTED] Subject: Re: Directly connected ethernet interface [7:10998] Date: Wed, 04 Jul 2001 09:12:25 -0700 Sitting here at Starbucks, using wireless, waiting for the 4th of July parade My brain isn't working too well. The latte wore off hours ago. But it occurs to me that Aironet is bridging, as you know. The routed network doesn't know when a bridged network goes down. Could you do this area of the network with all bridging? Could the ISDN link use bridging also, in other words? I know bridging over ISDN is supported. The convergence might be so slow, however, that you could pull the e1 interface in about the same timeframe (if you knew to do it though.) I can't think of any other solution (besides the one you mentioned of adding a router). It's an interesting design question. Maybe one of the CCIEs on the list will answer. Priscilla At 11:35 AM 7/4/01, KM Reynolds wrote: Hi Everyone, Need you help. I have a server that is on a remote LAN. To ping the server, the traffic goes in the local router(gateway) e0, out e1, to a local Aironet wireless bridge, to the remote Aironet wireless bridge, to a switch, to server. Works great. Currently, there is also a link to the remote site, an ISDN, from the local router to a remote router. We would like to use this ISDN as a backup to wireless connection. The routers are configured to use EIGRP to route between the wireless, and floating routes are set with higher administrative distance so when the EIGRP disappears out of the routing table the floating routes route via the ISDN. All works, when the ethernet (e1) is shutdown. When I disconnect the wireless at the remote, the ISDN comes up. The problem is, the route to the directly connected ethernet LAN is still in the routing table (C 192.168.30.128 255.255.255.128 is directly connected, Ethernet1). So traffic still flows out of e1, and I guess when it reaches the remote wireless bridge, it is discarded, that where the connection is down. Is there anyway around this, is there a way for the e1 to detect the path is down or is my only option to place a router and segment the wireless bridge link. Any help would be great. Thanks KM _ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Priscilla Oppenheimer http://www.priscilla.com _ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=11020t=10998 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Is it possible to configure an ethernet interface to obtain ip [7:10946]
Hello Everyone, I have an 1605 with two ethernet interfaces. Is it possible to configure one of the ethernet interface's so that it connects to the ISP's cable modem, and is able to obtain an IP address via the ISP's DHCP server. I currently have licences for 3 PCs, that obtain an IP when connecting to the ISP via cable. However, I would like to set up a LAN with more devices that do not need Internet access. So I would like to IP the 3 PCs with a private address, and when connecting to the Internet I would like to use the 1605 to NAT and provide the gateway to the Internet. Looking at the archives, I saw a mention about Easy IP, but I don't think this will do the job. Any suggestion would be greatly appriciated, and if anyone knows of another product (I would prefer Cisco) that will allow me to connect in this manner. Thanks so much KM _ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=10946t=10946 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: BRI0 Backup Interface for Ethernet Primary Interface [7:7069]
Thanks for the reply, You are correct on your first point. The post in the archive, by Howard, I realize it does NOT make mention of dial backup. I think this is my error, I need to delete the backup interface command. I think the dial backup is meant for a serial interface (frame relay, X-25,etc.), this is because layer 2 can be detected when it goes down. So I think in the case of ethernet, the alternate is a floating static route. I am not going to show the whole config, cause I think the backup command is the issue. However if you would like to anyway, let me know. I will give this a try tonight(if some maintenance downtime is available) and let you and everyone know how it works out. Thanks again. KM From: ElephantChild To: KM Reynolds CC: [EMAIL PROTECTED] Subject: Re: BRI0 Backup Interface for Ethernet Primary Interface [7:7027] Date: Mon, 4 Jun 2001 11:18:00 +0200 (CEST) My config: interface Ethernet1 backup delay 0 3 backup interface BRI0 router eigrp 10 network 172.26.0.0 ip route 172.20.20.0 255.255.255.0 10.10.9.5 200 That's too skimpy for a reliable diagnostic. Can you post your whole configuration to the list? (Sanitize as necessary.) A few things you may want to try or check: - I don't think you need the backup statements in that case. What triggers dialing using the BRI isn't e1 going down, but traffic to 172.20.20.0/24 after EIGRP removes the route to that through e1. - Is 10.10.9.5 reachable with e1 down? Does pinging it bring up bri0? - When you say bri0 doesn't come up, do you mean when e1 goes down, when the EIGRP route goes away, or when there's traffic for 172.20.20.0/24 and the route's down? On Mon, 4 Jun 2001, KM Reynolds wrote: Hi Everyone, I need to configure a ISDN link as backup for the primary interface. The primary interface is Ethernet1. I researched a numbers of books and they all are talk about serial or frame relay interface as the primary. I was able to search the archives and I found the identical problem that I am encountering. The post stated that yes the BRI0 interface can work as a backup for an ethernet interface. The following is a paste of the post(by Howard Berkowitz): Yes. The key to the solution is to use a low-overhead routing protocol such as OSPF or EIGRP as a layer 3 keepalive mechanism. Set up OSPF or EIGRP to define a path to the destination using the Ethernet. Set up a static route with administrative distance greater than that of the routing protocol (at least 200 is a good idea), with this static route going to the next hop address of the remote ISDN interface. If OSPF or EIGRP stop seeing hellos across the Ethernet, they will drop the route. The static route will now float up into the routing table, and you will get dial-on-demand routing across the ISDN. When OSPF sees its route again, after the Ethernet is back up, the Ethernet route will replace the ISDN in the active routing table, and the inactivity timer on the ISDN will disconnect it. I have followed the instructions, but no luck. When I shutdown the ethernet interface the BRI0 backup interface will not come up. The question I have are: 1. If I administratively shutdown the ethernet interface is that the same as if I disconnected the cable so that the e1 interface will not see a keepalive. 2. I did not see any other treads as to if solution worked. Has anyone run into this situation and has an answer or suggest anything. My config: interface Ethernet1 backup delay 0 3 backup interface BRI0 router eigrp 10 network 172.26.0.0 ip route 172.20.20.0 255.255.255.0 10.10.9.5 200 Lastly, one of the books (Internetworking Troubleshooting by C. Long) stated something about layer 2 and the no keepalive option. It didn't go further on this issue and don't know if I understood it. If someone can explain, it would be much appreciated. Sorry for the long post. TIA -- Someone approached me and asked me to teach a javascript course. I was about to decline, saying that my complete ignorance of the subject made me unsuitable, then I thought again, that maybe it doesn't, as driving people away from it is a desirable outcome. --Me _ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=7069t=7069 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
BRI0 Backup Interface for Ethernet Primary Interface [7:7027]
Hi Everyone, I need to configure a ISDN link as backup for the primary interface. The primary interface is Ethernet1. I researched a numbers of books and they all are talk about serial or frame relay interface as the primary. I was able to search the archives and I found the identical problem that I am encountering. The post stated that yes the BRI0 interface can work as a backup for an ethernet interface. The following is a paste of the post(by Howard Berkowitz): Yes. The key to the solution is to use a low-overhead routing protocol such as OSPF or EIGRP as a layer 3 keepalive mechanism. Set up OSPF or EIGRP to define a path to the destination using the Ethernet. Set up a static route with administrative distance greater than that of the routing protocol (at least 200 is a good idea), with this static route going to the next hop address of the remote ISDN interface. If OSPF or EIGRP stop seeing hellos across the Ethernet, they will drop the route. The static route will now float up into the routing table, and you will get dial-on-demand routing across the ISDN. When OSPF sees its route again, after the Ethernet is back up, the Ethernet route will replace the ISDN in the active routing table, and the inactivity timer on the ISDN will disconnect it. I have followed the instructions, but no luck. When I shutdown the ethernet interface the BRI0 backup interface will not come up. The question I have are: 1. If I administratively shutdown the ethernet interface is that the same as if I disconnected the cable so that the e1 interface will not see a keepalive. 2. I did not see any other treads as to if solution worked. Has anyone run into this situation and has an answer or suggest anything. My config: interface Ethernet1 backup delay 0 3 backup interface BRI0 router eigrp 10 network 172.26.0.0 ip route 172.20.20.0 255.255.255.0 10.10.9.5 200 Lastly, one of the books (Internetworking Troubleshooting by C. Long) stated something about layer 2 and the no keepalive option. It didn't go further on this issue and don't know if I understood it. If someone can explain, it would be much appreciated. Sorry for the long post. TIA KM _ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=7027t=7027 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Fwd: Re: Sending JPEG across an ISDN bridged link brings the [7:4116]
Hi Andy, Thanks for explanation. We are currently looking at upgrading the link. I am also going to suggest to the customer to change from a bridging environment to a routed one. If the two sites are segmented(enable the use of layer 3) it will enable us to implement QOS. I have one last question for you or anyone in the group. The math(in your reply e-mail), I was not going to ask this question because I think I should naturally know this. I understand the File size 2Megabytes is equal to (2*8) 16 Megabits. I do not understand the Transfer time:, how did you arrive to 128 Megabits per second? I am fuzzy on the transfer time formula. If you or someone may explain or point me in the direction where I may learn this, I would be grateful Thank you, KM From: andyh Reply-To: andyh To: [EMAIL PROTECTED] Subject: Re: Sending JPEG across an ISDN bridged link brings the network [7:3786] Date: Wed, 9 May 2001 09:06:53 -0400 let's do the maths: File size: 2MB = 16Mb Transfer time: 16Mb / 128Mb/s = 125 sec - ie a pretty long lime for those used to LAN-type speeds a better explanation would be to try to empty a bucket through a pinhole in the bottom - the point being that the data *will* get through (disregarding application timeouts or similar), whereas you're never going to get a lemon onto a pop bottle without breaking the bottle or splitting the lemon. one possible solution would be to implemet some sort of queueing - prioritize delay-sensitive traffic (interactive sessions and the like), and give large file transfers (ftp, http) a lower priority. Saying that it sounds like you need to get yourself some extra bandwidth - depending upon your needs you might wish to look at leased lines. probably time for you to do the maths as to whether you can justify the expense ;-) Andy - Original Message - From: KM Reynolds To: Sent: Wednesday, May 09, 2001 1:34 AM Subject: Sending JPEG across an ISDN bridged link brings the network to [7:3720] Hi all, Need the groups advice. The network consists of two 1605 routers with 128k ISDN connections in a transparent bridge environment. This network suffers from lockups often,however, not consistently. Yesterday, speaking with a user, he asked me a question. The question was, Why is it when I send a JPEG file to a user located across the ISDN link, the network come to a halt?. I told him that if the JPEG was very large in size ex. 2MB, when it has to cross the ISDN link, its like trying to squeeze a lemon(a small one) into a pop bottle(maybe not a good example, but that is all I could think off). This saturates the ISDN link which is only 128k. Am I correct in my explanation? What would be a good explanation? I am not comfortable with my explanation(maybe I am wrong). I look forward to hearing the groups thoughts, as well as any solutions(change to routing, QOS, etc.) TIA KM _ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] _ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=4116t=4116 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
