ISDN case... [7:72017]
Hi all, I have a problem with my ISDN back up link... the interface in STANDBY mode. TBRS#sho inter bri0 BRI0 is standby mode, line protocol is down Hardware is PQUICC BRI Description: Dialer to Lovisenberg Internet address is 172.21.14.1/24 MTU 1500 bytes, BW 64 Kbit, DLY 2 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation PPP, loopback not set Last input never, output never, output hang never Last clearing of "show interface" counters 00:39:45 Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: weighted fair Output queue: 0/1000/64/0 (size/max total/threshold/drops) Conversations 0/0/16 (active/max active/max total) Reserved Conversations 0/0 (allocated/max allocated) Available Bandwidth 48 kilobits/sec 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 0 packets input, 0 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 0 packets output, 0 bytes, 0 underruns 0 output errors, 0 collisions, 0 interface resets 0 output buffer failures, 0 output buffers swapped out 0 carrier transitions and the configuration is hostname TBRS ! username LDS password 7 15100A0F0F3F3B28213D3E isdn switch-type basic-net3 ! interface BRI0 description Dialer to LDS ip address 172.21.14.1 255.255.255.0 encapsulation ppp dialer idle-timeout 750 dialer map ip 172.21.14.2 name LDS 23225374 dialer-group 1 isdn switch-type basic-net3 ppp authentication chap ppp chap password 7 1307161100191426222A23 ! interface FastEthernet0 ip address 172.20.40.1 255.255.255.0 ip helper-address 100.73.120.16 speed auto no cdp enable ! interface Serial0 backup interface BRI0 ip address 172.20.14.1 255.255.255.252 no fair-queue ! router eigrp 1 redistribute connected redistribute static passive-interface FastEthernet0 network 172.0.0.0 no auto-summary no eigrp log-neighbor-changes ! ip classless ip route 0.0.0.0 0.0.0.0 172.20.14.2 ip route 0.0.0.0 0.0.0.0 172.21.14.2 200 no ip http server ! dialer-list 1 protocol ip permit The other side is configred in the same way. Cheers Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=72017&t=72017 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: Query on MGX8850 [7:71702]
Hi, My answers inline Thanks and Regards Diva- "Vikram JeetSingh" To: [EMAIL PROTECTED] Subject: RE: Query on MGX8850 [7:71702] Sent by: [EMAIL PROTECTED] .com 04/07/2003 22:42 Please respond to "Vikram JeetSingh" Hi Diva, I feel I need some more information on this.. 1. Are all 4 nodes part of the same network, i.e., are the India and UK end nodes back connected? ALL NODES ARE PART OF THE SAME NETWORK BUT ARE NOT BACK CONNECTED. 2. Are they having just 1 IPLC each? YES ONE EACH OF THE IPLCS ARE CONNECTED TO EACH OF THE MGX8850 3. If they are having more than 1 IPLC, are you running PNNI or some other routing protocol on them, or have you done some static mapping? THEY HAVE ONLY ONE IPLC EACH, BUT THEY HAVE BEEN CONFIGURED WITH PNNI 4. Do you mean to say that you have 2 routers running HSRP and they are attached to different FRSMs on FR? And then on in case of one IPLC going down you want the traffic to route through the other IPLC? YES WE HAVE TWO ROUTERS RUNNING HSRP , AND THEY ARE ATTACHED TO TWO DIFFERENT FRSM ON TWO DIFFERENT MGX8850. AND INCASE OF IPLC FAILURE ON ONE MGX , THE ROUTER CONNECTED TO THE FRSM ON THAT MGX 8850 SHOULD DETECT THAT AND THEN THE HSRP SHOULD REDUCE THE PRIORITY. On the last point, as per me it would be better to connect your MGX nodes to each other locally at both the locations and then by running PNNI end-to-end you can route your traffic in case of IPLC failures, and more so if both the nodes are sitting close by. For your traffic routing you can rely upon on some IP routing features. IT IS NOT POSSIBLE TO BACK CONNECT THE MGXs BECAUSE THEY ARE NOT IN ONE SINGLE LOCATION. AND THE CUSTOMER WANTS TO USE ONLY STATIC ROUTES AND NO DYANAMIC PROTOCOL. HTH Vikram -Original Message- From: Divakaran Ullampuzhamana [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 02, 2003 11:10 AM To: [EMAIL PROTECTED] Subject: RE: Query on MGX8850 [7:71702] Hi, Let me expalain my network now. I have two MGX8850s in India on to which one IPLC each are getting connected to the PXm1-e1 card.The other end of the IPLC s are connected similarly to two MGX8850s in UK. We have a FRSM card on each of the MGXs .We have 4 cisco 3745 routers connected using a pair of DTE and DCE cables. The serial interface is configured for framerelay.I have not created any subinterfaces on the serial interface for framelrelay. The routers are configured with HSRP. I would like the HSRP to track the changes in the status of the IPLC and switch over the HSRP active router. Right now, when the IPLc goes down, the FRSM card still shows up and the router serial interfaces shows line protocol up.Thus HSRP , which is tracking the serial interface still assumes that the link is up and hence will not change the state. My objective is :--- The serial interface connected to the FRSM on the MGX should be able to know when the IPLC connected to PXM1-e1 goes down.And the HSRp which is tracking the serial interface should change the state . Thanks and Regards Diva- +91-80-98451 41676 "Vikram JeetSingh" To: [EMAIL PROTECTED] Subject: RE: Query on MGX8850 [7:71702] Sent by: [EMAIL PROTECTED] .com 01/07/2003 18:45 Please respond to "Vikram JeetSingh" HI Diva, I think your query is more towards the FR interfaces than the MGX nodes. As per me, as soon the IPLC or the trunk link on the MGX goes down, it will also make the FR connection down, and same will be reflected on the PVC status in router also. So that should serve your purpose, but then what is your interface configuration, are you using sub-interface or the PVC is configured on to the main interface itself. Let us know about your core objective and some more information, and then may be things take some new turn. HTH Vikram -Original Message- From: Divakaran Ullampuzhamana [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 01, 2003 1:27 PM To: [EMAIL PROTECTED] Subject: Query on MGX88
RE: Cisco catalyst 3548 and Radius [7:71991]
those commands are only there after you enable aaa new model. -Original Message- From: Robert Perez [mailto:[EMAIL PROTECTED] Sent: 07 July 2003 18:03 To: [EMAIL PROTECTED] Subject: Cisco catalyst 3548 and Radius [7:71991] Hi all, I am configuring Radius on a cat 3548 and I do not have the global config "radius" command available. Anyone know what the commands ought to be to create a server, key, etc.. Normally it is Radius-server key, radius-server host.. Can't figure it out.. I have IOS 12.0(5.2)XU Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=72016&t=71991 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
protocol analyzer [7:72018]
someone please tell me web sites about how to understand the outputs of protocol analyzer. any help will be appreciated! Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=72018&t=72018 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: protocol analyzer [7:72018]
You may find the two sites listed at the bottom of http://www.sysdom.org/html/web_links.htm To be of some use. Best regards, Dom Stocqueler SysDom Technologies === IMPORTANT: This email is intended for the use of the individual addressee(s)named above and may contain information that is confidential privileged or unsuitable for overly sensitive persons with low self-esteem, no sense of humour or irrational religious beliefs. If you are not the intended recipient, any dissemination, distribution or copying of this email is not authorised (either explicitly or implicitly) and constitutes an irritating social faux pas. Unless the word absquatulation has been used in its correct context somewhere other than in this warning, it does not have any legal or grammatical use and may be ignored. No animals were harmed in the transmission of this email, although the poodle next door is living on borrowed time, let me tell you. Those of you with an overwhelming fear of the unknown will be gratified to learn that there is no hidden message revealed by reading this warning backwards, so just ignore that Alert Notice from Microsoft. However, by pouring a complete circle of salt around yourself and your computer you can ensure that no harm befalls you and your pets. If you have received this email in error, please add some nutmeg and egg whites and place it in a warm oven for 40 minutes. Whisk briefly and let it stand for 2 hours before icing. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 08 July 2003 10:22 To: [EMAIL PROTECTED] Subject: protocol analyzer [7:72018] someone please tell me web sites about how to understand the outputs of protocol analyzer. any help will be appreciated! Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=72020&t=72018 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: ISDN Port goes to Deactivated mode [7:72023]
Dear all I am having 128 kbps Leased Line with ISDN backup.As the Link goes Down ,ISDN should trigger,however in my case the ISDN link does not come up and goes to deactivated mode.What could be the problem .I have seen that upon removing the ISDN link and inserting back it gives the status as ACTIVE.What could be the problm? Kindly help as I am not able to use backup link due to this reason. I have attached herewitht the log of sh isdn status command for your kind pwerusal Thanks in advance. Regards Piyush router-1#sh ISDN status ISDN BRI0 interface dsl 0, interface ISDN Switchtype = basic-net3 Layer 1 Status: DEACTIVATED Layer 2 Status: TEI = 85, Ces = 1, SAPI = 0, State = TEI_ASSIGNED I_Queue_Len 0, UI_Queue_Len 0 Layer 3 Status: 0 Active Layer 3 Call(s) Activated dsl 0 CCBs = 0 The Free Channel Mask: 0x8003 Total Allocated ISDN CCBs = 0 Send free SMS using the Yahoo! Messenger. Go to http://in.mobile.yahoo.com/new/pc/ Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=72023&t=72023 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: ISDN case... [7:72017]
Hi, This is the detail configuration for both routers LDS# LDS#show run Building configuration... Current configuration : 2939 bytes ! version 12.2 service timestamps debug datetime msec localtime service timestamps log datetime msec localtime service password-encryption service compress-config ! hostname LDS ! boot system flash c3725-is-mz.122-15.T2.bin logging queue-limit 100 ! username TBRS password 7 104C081A0E020207050A21 clock timezone met 1 clock summer-time met recurring last Sun Mar 2:00 last Sun Oct 3:00 ip subnet-zero ! isdn switch-type basic-net3 ! no voice hpi capture buffer no voice hpi capture destination ! mta receive maximum-recipients 0 ! ! interface FastEthernet0/0 ip address 100.73.1.3 255.255.128.0 duplex auto speed auto ! interface Serial1/1 description Link to TBRS ip address 172.20.14.2 255.255.255.252 backup interface BRI2/3 serial restart_delay 0 ! ! interface BRI2/3 description Dialer to TBRS ip address 172.21.14.2 255.255.255.0 encapsulation ppp dialer idle-timeout 750 dialer map ip 172.21.14.1 name TBRS 022193533 dialer-group 1 isdn switch-type basic-net3 ppp authentication chap ppp chap password 7 0509070C2A595E05100B1C ! ! router eigrp 1 redistribute connected redistribute static passive-interface FastEthernet0/0 network 172.0.0.0 network 172.20.11.0 0.0.0.255 network 172.20.12.0 0.0.0.255 network 172.20.13.0 0.0.0.255 network 172.20.14.0 0.0.0.255 network 172.20.15.0 0.0.0.255 no auto-summary no eigrp log-neighbor-changes ! no ip http server ip classless ip route 0.0.0.0 0.0.0.0 100.73.1.1 ip route 172.20.10.0 255.255.255.0 172.20.11.1 ip route 172.20.20.0 255.255.255.0 172.20.12.1 ip route 172.20.30.0 255.255.255.0 172.20.13.1 ip route 172.20.40.0 255.255.255.0 172.20.14.1 ip route 172.20.50.0 255.255.255.0 172.20.15.1 ip route 172.21.14.0 255.255.255.0 172.21.14.1 200 ! dialer-list 1 protocol ip permit ! call rsvp-sync ! mgcp profile default ! dial-peer cor custom ! banner motd ^CCWarning: All unauthorized use will be reported! ^C ! line con 0 exec-timeout 0 0 line aux 0 line vty 0 4 password 7 15130F010D7338303A32212D01 login ! end LDS#show inter bri2/3 BRI2/3 is standby mode, line protocol is down Hardware is BRI Description: Dialer to TBRS Internet address is 172.21.14.2/24 MTU 1500 bytes, BW 64 Kbit, DLY 2 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation PPP, loopback not set Last input 03:41:47, output 03:41:47, output hang never Last clearing of "show interface" counters 01:48:55 Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: weighted fair Output queue: 0/1000/64/0 (size/max total/threshold/drops) Conversations 0/1/16 (active/max active/max total) Reserved Conversations 0/0 (allocated/max allocated) Available Bandwidth 48 kilobits/sec 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 0 packets input, 0 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 0 packets output, 0 bytes, 0 underruns 0 output errors, 0 collisions, 0 interface resets 0 output buffer failures, 0 output buffers swapped out 0 carrier transitions LDS# LDS# The second router TBRS# TBRS#show run Building configuration... Current configuration : 1508 bytes ! version 12.2 service timestamps debug datetime msec localtime service timestamps log datetime msec localtime service password-encryption service compress-config ! hostname TBRS ! enable secret 5 $1$mgUK$3f83im5ZmyjmtPvmYmU331 enable password 7 110A1016141D ! username LDS password 7 15100A0F0F3F3B28213D3E clock timezone met 1 clock summer-time met recurring last Sun Mar 2:00 last Sun Oct 3:00 ip subnet-zero ! isdn switch-type basic-net3 ! ! ! interface BRI0 description Dialer to Lovisenberg ip address 172.21.14.1 255.255.255.0 encapsulation ppp dialer idle-timeout 750 dialer map ip 172.21.14.2 name LDS-R01 23225374 dialer-group 1 isdn switch-type basic-net3 ppp authentication chap ppp chap password 7 1307161100191426222A23 ! interface FastEthernet0 ip address 172.20.40.1 255.255.255.0 ip helper-address 100.73.120.16 speed auto no cdp enable ! interface Serial0 backup interface BRI0 ip address 172.20.14.1 255.255.255.252 no fair-queue ! router eigrp 1 redistribute connected redistribute static passive-interface FastEthernet0 network 172.0.0.0 no auto-summary no eigrp log-neighbor-changes ! ip classless ip route 0.0.0.0 0.0.0.0 172.20.14.2 ip route 0.0.0.0 0.0.0.0 172.21.14.2 200 no ip http server ! ! dialer-list 1 protocol ip permit dialer-list 1 protocol ipx permit banner motd ^CCWarning: All unauthorized use will be reported! ^C ! line con 0 exec-timeout 15 0 line aux 0 line vty 0 4 password 7 0005170B0D0218121D2058411B login ! no scheduler allocate end TBRS# TB
OSPF max Router-LSA links [7:72024]
layer 2 frame has a MTU of 1500 bytes. how does cisco router propagate router-lsa whose size exceed 1500 bytes(more than 122 links in one area)? __ === [EMAIL PROTECTED] (http://bizsite.sina.com.cn) Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=72024&t=72024 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: ISDN case... [7:72017]
This is normal behaviour: if you configure BRI as backup, it will go in standby mode and line protocol goes down. You can avoid this by configuring a dialer interface as backup. Then the dialer interface will go in standby mode, but the BRI stays up!! This is preferred since: 1. some Telco's will lock out your line when it is too long down; 2. you can easily detect if your backup goes down. This won't give any surprises when you really need the backup! So replace this: interface s0 backup interface bri0 By following: interface s0 backup interface dialer 1 interface dialer 1 dialer pool 1 interface bri0 dialer pool-member 1 In your case I would try something like this: interface s0 ip address 172.20.14.1 255.255.255.252 backup interface dialer 1 dialer-list 1 protocol ip permit interface dialer 1 description Dialer to LDS ip address 172.21.14.1 255.255.255.0 encapsulation ppp ppp authentication chap ppp chap password 7 1307161100191426222A23 dialer idle-timeout 750 dialer map ip 172.21.14.2 name LDS 23225374 dialer-group 1 dialer pool 1 interface bri0 isdn switch-type basic-net3 encapsulation ppp ppp authentication chap ppp chap password 7 1307161100191426222A23 dialer pool-member 1 Hope this helps, Eric Brouwers PS Be careful about moving all statements below BRI interface to dialer interface. This is what Cisco says about it: "...Commands that apply before authentication is complete must be configured on the physical (BRI) interface and not on the dialer profile. Dialer profiles do not copy PPP authentication commands (or LCP commands) to the physical interface .." I've never tried the most efficient configuration, that's why there is some redundancy in the config above. Maybe someone else can comment about removing the PPP encaps. and auth. commands from the dialer interface?? Cheers, Eric - Original Message - From: "H T" To: Sent: Tuesday, July 08, 2003 8:36 AM Subject: ISDN case... [7:72017] > Hi all, > I have a problem with my ISDN back up link... the interface in STANDBY mode. > > > TBRS#sho inter bri0 > BRI0 is standby mode, line protocol is down > Hardware is PQUICC BRI > Description: Dialer to Lovisenberg > Internet address is 172.21.14.1/24 > MTU 1500 bytes, BW 64 Kbit, DLY 2 usec, > reliability 255/255, txload 1/255, rxload 1/255 > Encapsulation PPP, loopback not set > Last input never, output never, output hang never > Last clearing of "show interface" counters 00:39:45 > Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 > Queueing strategy: weighted fair > Output queue: 0/1000/64/0 (size/max total/threshold/drops) > Conversations 0/0/16 (active/max active/max total) > Reserved Conversations 0/0 (allocated/max allocated) > Available Bandwidth 48 kilobits/sec > 5 minute input rate 0 bits/sec, 0 packets/sec > 5 minute output rate 0 bits/sec, 0 packets/sec > 0 packets input, 0 bytes, 0 no buffer > Received 0 broadcasts, 0 runts, 0 giants, 0 throttles > 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort > 0 packets output, 0 bytes, 0 underruns > 0 output errors, 0 collisions, 0 interface resets > 0 output buffer failures, 0 output buffers swapped out > 0 carrier transitions > > > and the configuration is > > hostname TBRS > ! > username LDS password 7 15100A0F0F3F3B28213D3E > isdn switch-type basic-net3 > ! > interface BRI0 > description Dialer to LDS > ip address 172.21.14.1 255.255.255.0 > encapsulation ppp > dialer idle-timeout 750 > dialer map ip 172.21.14.2 name LDS 23225374 > dialer-group 1 > isdn switch-type basic-net3 > ppp authentication chap > ppp chap password 7 1307161100191426222A23 > ! > interface FastEthernet0 > ip address 172.20.40.1 255.255.255.0 > ip helper-address 100.73.120.16 > speed auto > no cdp enable > ! > interface Serial0 > backup interface BRI0 > ip address 172.20.14.1 255.255.255.252 > no fair-queue > ! > router eigrp 1 > redistribute connected > redistribute static > passive-interface FastEthernet0 > network 172.0.0.0 > no auto-summary > no eigrp log-neighbor-changes > ! > ip classless > ip route 0.0.0.0 0.0.0.0 172.20.14.2 > ip route 0.0.0.0 0.0.0.0 172.21.14.2 200 > no ip http server > ! > dialer-list 1 protocol ip permit > > > > > The other side is configred in the same way. > > > Cheers Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=72021&t=72017 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: ISDN Port goes to Deactivated mode [7:72022]
Dear all I am having 128 kbps Leased Line with ISDN backup.As the Link goes Down ,ISDN should trigger,however in my case the ISDN link does not come up and goes to deactivated mode.What could be the problem .I have seen that upon removing the ISDN link and inserting back it gives the status as ACTIVE.What could be the problm? Kindly help as I am not able to use backup link due to this reason. I have attached herewitht the log of sh isdn status command for your kind pwerusal Thanks in advance. Regards Piyush router-1#sh ISDN status ISDN BRI0 interface dsl 0, interface ISDN Switchtype = basic-net3 Layer 1 Status: DEACTIVATED Layer 2 Status: TEI = 85, Ces = 1, SAPI = 0, State = TEI_ASSIGNED I_Queue_Len 0, UI_Queue_Len 0 Layer 3 Status: 0 Active Layer 3 Call(s) Activated dsl 0 CCBs = 0 The Free Channel Mask: 0x8003 Total Allocated ISDN CCBs = 0 Send free SMS using the Yahoo! Messenger. Go to http://in.mobile.yahoo.com/new/pc/ Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=72022&t=72022 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: ISDN case... [7:72017]
Hi Eric, Thanks for what you wrote... I want the BRI just for a back up... so the line should stay down all the time when every thing is normal. I want the BRI come up only once the serial go down " in this way we get small bill" :) how about the routing section ? did you had a look at? cheers, Heiman. ""ericbrouwers"" wrote in message news:[EMAIL PROTECTED] > This is normal behaviour: if you configure BRI as backup, it will go in > standby mode and line protocol goes down. You can avoid this by configuring > a dialer interface as backup. Then the dialer interface will go in standby > mode, but the BRI stays up!! This is preferred since: > 1. some Telco's will lock out your line when it is too long down; > 2. you can easily detect if your backup goes down. > This won't give any surprises when you really need the backup! > > So replace this: > interface s0 >backup interface bri0 > > By following: > interface s0 >backup interface dialer 1 > > interface dialer 1 >dialer pool 1 > > interface bri0 >dialer pool-member 1 > > In your case I would try something like this: > > interface s0 >ip address 172.20.14.1 255.255.255.252 >backup interface dialer 1 > > dialer-list 1 protocol ip permit > > interface dialer 1 >description Dialer to LDS >ip address 172.21.14.1 255.255.255.0 >encapsulation ppp >ppp authentication chap >ppp chap password 7 1307161100191426222A23 >dialer idle-timeout 750 >dialer map ip 172.21.14.2 name LDS 23225374 >dialer-group 1 >dialer pool 1 > > interface bri0 >isdn switch-type basic-net3 >encapsulation ppp >ppp authentication chap >ppp chap password 7 1307161100191426222A23 >dialer pool-member 1 > > Hope this helps, > > Eric Brouwers > > PS > Be careful about moving all statements below BRI interface to dialer > interface. This is what Cisco says about it: > > "...Commands that apply before authentication is complete must be configured > on the physical (BRI) interface and not on the dialer profile. Dialer > profiles do not copy PPP authentication commands (or LCP commands) to the > physical interface > .." > > I've never tried the most efficient configuration, that's why there is some > redundancy in the config above. Maybe someone else can comment about > removing the PPP encaps. and auth. commands from the dialer interface?? > > Cheers, > > Eric > > > - Original Message - > From: "H T" > To: > Sent: Tuesday, July 08, 2003 8:36 AM > Subject: ISDN case... [7:72017] > > > > Hi all, > > I have a problem with my ISDN back up link... the interface in STANDBY > mode. > > > > > > TBRS#sho inter bri0 > > BRI0 is standby mode, line protocol is down > > Hardware is PQUICC BRI > > Description: Dialer to Lovisenberg > > Internet address is 172.21.14.1/24 > > MTU 1500 bytes, BW 64 Kbit, DLY 2 usec, > > reliability 255/255, txload 1/255, rxload 1/255 > > Encapsulation PPP, loopback not set > > Last input never, output never, output hang never > > Last clearing of "show interface" counters 00:39:45 > > Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 > > Queueing strategy: weighted fair > > Output queue: 0/1000/64/0 (size/max total/threshold/drops) > > Conversations 0/0/16 (active/max active/max total) > > Reserved Conversations 0/0 (allocated/max allocated) > > Available Bandwidth 48 kilobits/sec > > 5 minute input rate 0 bits/sec, 0 packets/sec > > 5 minute output rate 0 bits/sec, 0 packets/sec > > 0 packets input, 0 bytes, 0 no buffer > > Received 0 broadcasts, 0 runts, 0 giants, 0 throttles > > 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort > > 0 packets output, 0 bytes, 0 underruns > > 0 output errors, 0 collisions, 0 interface resets > > 0 output buffer failures, 0 output buffers swapped out > > 0 carrier transitions > > > > > > and the configuration is > > > > hostname TBRS > > ! > > username LDS password 7 15100A0F0F3F3B28213D3E > > isdn switch-type basic-net3 > > ! > > interface BRI0 > > description Dialer to LDS > > ip address 172.21.14.1 255.255.255.0 > > encapsulation ppp > > dialer idle-timeout 750 > > dialer map ip 172.21.14.2 name LDS 23225374 > > dialer-group 1 > > isdn switch-type basic-net3 > > ppp authentication chap > > ppp chap password 7 1307161100191426222A23 > > ! > > interface FastEthernet0 > > ip address 172.20.40.1 255.255.255.0 > > ip helper-address 100.73.120.16 > > speed auto > > no cdp enable > > ! > > interface Serial0 > > backup interface BRI0 > > ip address 172.20.14.1 255.255.255.252 > > no fair-queue > > ! > > router eigrp 1 > > redistribute connected > > redistribute static > > passive-interface FastEthernet0 > > network 172.0.0.0 > > no auto-summary > > no eigrp log-neighbor-changes > > ! > > ip classless > > ip route 0.0.0.0 0.0.0.0 172.20.14.2 > > ip route 0.0.0.0 0.0.0.0 172.21.14.2 200 > > no ip http server > > ! > > dialer-list 1 pr
Good news and bad news [7:72026]
I recommend taking a look at this article http://www.idg.net/ic_1325908_9677_1-5044.html There is good news and bad news built into it. The bad news first: the tech jobs that many of us in North America used to enter the IT world -- help desk, small networks -- are consolidating and moving overseas for cost reasons. Of course, that's good news for the folks overseas who are just like us in all the important respects -- they're going to have more opportunities to break in. The good news for North America is in the last paragraph: // Wasierski says one key to success is finding a competent integrator and reviewing two of its recent implementations. In his case, the Cisco integrator "had no idea what it was doing," partly because the technology was so new. As a result, vCustomer had to scrap the integrator's work and start over, building the entire system in-house. "That was a learning experience," he says. // The work in North America will be in the design and implementation of the mixed networks. Those who can do the more complex, and deeper, integrations will have work. This article should make clear why Cisco is shifting the newer CCNP and CCDP exam tracks to include more VoIP, security, and IPv6. I thought it was to push sales, and it probably is. But the products have a compelling business case, which means I've got more stuff to learn, and the same 24-hour day to do it in ;-). Annlee Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=72026&t=72026 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
CCDP requirements: pointless to do CID if you don't already [7:72027]
Hi, I'm aiming at CCDP but I don't have BCRAN. Am I correct in thinking that there is no point in me registering for CID before registration finally ends on July 25th - because to go this route to CCDP, BCRAN is also needed - but is no longer available? Therefore better for me to forget CID and go straight to ARCH? Thanks, Shane DISCLAIMER "This e-mail and any attachment thereto may contain information which is confidential and/or protected by intellectual property rights and are intended for the sole use of the recipient(s) named above. Any use of the information contained herein (including, but not limited to, total or partial reproduction, communication or distribution in any form) by other persons than the designated recipient(s) is prohibited. If you have received this e-mail in error, please notify the sender either by telephone or by e-mail and delete the material from any computer". Thank you for your cooperation. For further information about Proximus mobile phone services please see our website at http://www.proximus.be or refer to any Proximus agent. Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=72027&t=72027 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: ISDN Port goes to Deactivated mode [7:72022]
Hi, can you show us your running config of both sides, so we can know where would be the problem? cheers, Heiman. ""Mr piyush shah"" wrote in message news:[EMAIL PROTECTED] > Dear all > I am having 128 kbps Leased Line with ISDN backup.As > the Link goes Down ,ISDN should trigger,however in my > case the ISDN link does not come up and goes to > deactivated mode.What could be the problem .I have > seen that upon removing the ISDN link and inserting > back it gives the status as ACTIVE.What could be the > problm? > Kindly help as I am not able to use backup link due to > this reason. > > I have attached herewitht the log of sh isdn status > command for your kind pwerusal > > Thanks in advance. > > Regards > > > Piyush > > router-1#sh ISDN status > > ISDN BRI0 interface > dsl 0, interface ISDN Switchtype = basic-net3 > Layer 1 Status: > DEACTIVATED > Layer 2 Status: > TEI = 85, Ces = 1, SAPI = 0, State = > TEI_ASSIGNED > I_Queue_Len 0, UI_Queue_Len 0 > Layer 3 Status: > 0 Active Layer 3 Call(s) > Activated dsl 0 CCBs = 0 > The Free Channel Mask: 0x8003 > Total Allocated ISDN CCBs = 0 > > > Send free SMS using the Yahoo! Messenger. Go to > http://in.mobile.yahoo.com/new/pc/ Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=72028&t=72022 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
New MPLS book [7:72029]
is it worth getting the new MPLS book (MPLS and VPN Architectures, Volume II by Ivan & Jim) for the CCIE C&S exams? Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=72029&t=72029 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Maximum segment size in TCP [7:72030]
Hello group, I am facing slow response issue when connecting to Mainframe. This is how my connectivity goes [EMAIL PROTECTED] A ---> FrameRelay(WAN) --> Location B ---> Site to Site VPN (T1) --> [EMAIL PROTECTED] C I have captured the packet using ethereal and found that Source PC TCP Maximum Segment Size is 1456bytes and that of Mainframe is 4056bytes. This slow response issue with mainframe is intermittent. And there is no issue at the mainframe as it works fine when I connect from within the Location C Source side there is no issue since for some other mainframe at Location D, I am getting good response and the Source PC MSS is 1456bytes and that of Mainframe MSS is 536bytes. The only difference in this connectivity is that this mainframe is connected using an framerealy from Location B to Location D (given below) [EMAIL PROTECTED] A ---> FrameRelay(WAN) --> Location B ---> FrameRelay(WAN)--> [EMAIL PROTECTED] D I would like to know whether the MSS Size of 4056bytes from mainframe in the Location C attributes to the slow reponse issue. Is the high MSS size is due to Site-to Site VPN from Location B to C( due to excess header information due to VPN) or something else. Would appreciate your response. TIA, Kum _ Design your holidays. At your convenience. http://www.flexihols.com/2003/index.php Click here. Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=72030&t=72030 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: New MPLS book [7:72029]
the first edition whould be enough to pass the exam, but u will see u will want to get the new book, cause it's a very interesting subject it's (the futur of networking)... ""Muhtari Adanan"" a icrit dans le message de news:[EMAIL PROTECTED] > is it worth getting the new MPLS book (MPLS and VPN Architectures, Volume II > by Ivan & Jim) for the CCIE C&S exams? Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=72031&t=72029 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: CCDP requirements: pointless to do CID if you don't already [7:72032]
Hi, You do not need BCRAN to be CCNP. Just BSCI, Switching and CID. I am also trying to beat the 25th July deadline! Please see: http://www.cisco.com/en/US/learning/le3/le2/le37/le5/learning_certification_ type_home.html Thanks and regards George Murage -Original Message- From: MCMORDIE Shane (BMB) [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 08, 2003 5:21 PM To: [EMAIL PROTECTED] Subject: CCDP requirements: pointless to do CID if you don't already [7:72027] Hi, I'm aiming at CCDP but I don't have BCRAN. Am I correct in thinking that there is no point in me registering for CID before registration finally ends on July 25th - because to go this route to CCDP, BCRAN is also needed - but is no longer available? Therefore better for me to forget CID and go straight to ARCH? Thanks, Shane DISCLAIMER "This e-mail and any attachment thereto may contain information which is confidential and/or protected by intellectual property rights and are intended for the sole use of the recipient(s) named above. Any use of the information contained herein (including, but not limited to, total or partial reproduction, communication or distribution in any form) by other persons than the designated recipient(s) is prohibited. If you have received this e-mail in error, please notify the sender either by telephone or by e-mail and delete the material from any computer". Thank you for your cooperation. For further information about Proximus mobile phone services please see our website at http://www.proximus.be or refer to any Proximus agent. Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=72032&t=72032 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: Maximum segment size in TCP [7:72030]
A host uses the TCP maximum segment size option to specify the max size of TCP segments (packets) that it can accept. In the case where you have the slow response time, the mainframe is saying that its max segment size is 4056 bytes, which means that it can accept packets of that size (with that much payload). This is somewhat non-standard, but I doubt it would cause slow response time. Does the client really try to send such large packets? I doubt it. But that's what you need to look at. How does the client react to the mainframe saying that its MSS is 4056 bytes. If the client is on Ethernet, it can't send such large packets. Also, what sort of PC/mainframe application would try to send such large frames? Most such applications would use much smaller packets. So I doubt that the MSS is the problem The major difference that stands out for the case where there's slow versus good respons time is that the slow response is on a site-to-site VPN link and the fast response is on a Frame Relay WAN. What are the speeds of the two links? I'm not a VPN expert, but I know that VPNs have a lot of overhead and can be slow. Where is the tunneling and encryption happening? Are the devices that are doing that slow? If I were you, I would consider the MSS a misleading clue and focus on telling us more about this slow VPN link. Thanks, Priscilla kuma kk wrote: > > Hello group, > > I am facing slow response issue when connecting to Mainframe. > This is how my > connectivity goes > > [EMAIL PROTECTED] A ---> FrameRelay(WAN) --> Location B ---> Site to > Site VPN (T1) > --> [EMAIL PROTECTED] C > > I have captured the packet using ethereal and found that Source > PC TCP > Maximum Segment Size is 1456bytes and that of Mainframe is > 4056bytes. This > slow response issue with mainframe is intermittent. And there > is no issue at > the mainframe as it works fine when I connect from within the > Location C > > Source side there is no issue since for some other mainframe at > Location D, > I am getting good response and the Source PC MSS is 1456bytes > and that of > Mainframe MSS is 536bytes. The only difference in this > connectivity is that > this mainframe is connected using an framerealy from Location B > to Location > D (given below) > > [EMAIL PROTECTED] A ---> FrameRelay(WAN) --> Location B ---> > FrameRelay(WAN)--> > [EMAIL PROTECTED] D > > I would like to know whether the MSS Size of 4056bytes from > mainframe in the > Location C attributes to the slow reponse issue. Is the high > MSS size is due > to Site-to Site VPN from Location B to C( due to excess header > information > due to VPN) or something else. > > Would appreciate your response. > > TIA, > Kum > > _ > Design your holidays. At your convenience. > http://www.flexihols.com/2003/index.php Click here. > > Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=72033&t=72030 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: ISDN Port goes to Deactivated mode [7:72022]
I have experienced the same problem and would really like to see what the others have to say. While testing, I put my router with a BRI-1B-S/T card behind a PBX with an NTI card and the problem vanished. This led me to believe that the problem has something to do with the telco. I *think* the telco switch may not be able to detect, in a timely fashion that your isdn line is active, because European ISDN switches normally deactivate layer 1 or layer 2 of an idle isdn line. Removing and re-inserting the cable sort of resets the layers 1 and 2. Has the same effect as typing "clear int brix/y" on the router. Regards George Murage -Original Message- From: H T [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 08, 2003 5:49 PM To: [EMAIL PROTECTED] Subject: Re: ISDN Port goes to Deactivated mode [7:72022] Hi, can you show us your running config of both sides, so we can know where would be the problem? cheers, Heiman. ""Mr piyush shah"" wrote in message news:[EMAIL PROTECTED] > Dear all > I am having 128 kbps Leased Line with ISDN backup.As > the Link goes Down ,ISDN should trigger,however in my > case the ISDN link does not come up and goes to > deactivated mode.What could be the problem .I have > seen that upon removing the ISDN link and inserting > back it gives the status as ACTIVE.What could be the > problm? > Kindly help as I am not able to use backup link due to > this reason. > > I have attached herewitht the log of sh isdn status > command for your kind pwerusal > > Thanks in advance. > > Regards > > > Piyush > > router-1#sh ISDN status > > ISDN BRI0 interface > dsl 0, interface ISDN Switchtype = basic-net3 > Layer 1 Status: > DEACTIVATED > Layer 2 Status: > TEI = 85, Ces = 1, SAPI = 0, State = > TEI_ASSIGNED > I_Queue_Len 0, UI_Queue_Len 0 > Layer 3 Status: > 0 Active Layer 3 Call(s) > Activated dsl 0 CCBs = 0 > The Free Channel Mask: 0x8003 > Total Allocated ISDN CCBs = 0 > > > Send free SMS using the Yahoo! Messenger. Go to > http://in.mobile.yahoo.com/new/pc/ Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=72035&t=72022 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
HSRP and IPSEC VPN [7:72034]
Hi, Does anyone know if HSRP would be appropriate in the following scenario? ROUTERA with T1 to corporate office ROUTERB with IPSEC VPN to Corporate only used as a backup path in case the T1 on ROUTERA fails Is there any reason that this will not work or has anyone had experience with this type of situation? -- Dain Deutschman CCNP, CSS-1, MCP, CNA Data Communications Manager New Star Sales and Service, Inc. Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=72034&t=72034 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: HSRP and IPSEC VPN [7:72034]
..that's what I thought...just needed a sanity check! Thanks! ""MADMAN"" wrote in message news:[EMAIL PROTECTED] > If router A anb B share an ethernet then sure HSRP was designed > exactly for this scenerio > >Dave > > Dain Deutschman wrote: > > Hi, > > > > Does anyone know if HSRP would be appropriate in the following scenario? > > > > ROUTERA with T1 to corporate office > > > > ROUTERB with IPSEC VPN to Corporate only used as a backup path in case the > > T1 on ROUTERA fails > > > > > > Is there any reason that this will not work or has anyone had experience > > with this type of situation? > > > -- > David Madland > CCIE# 2016 > Sr. Network Engineer > Qwest Communications > 612-664-3367 > > "Government can do something for the people only in proportion as it > can do something to the people." -- Thomas Jefferson Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=72039&t=72034 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: HSRP and IPSEC VPN [7:72034]
If router A anb B share an ethernet then sure HSRP was designed exactly for this scenerio Dave Dain Deutschman wrote: > Hi, > > Does anyone know if HSRP would be appropriate in the following scenario? > > ROUTERA with T1 to corporate office > > ROUTERB with IPSEC VPN to Corporate only used as a backup path in case the > T1 on ROUTERA fails > > > Is there any reason that this will not work or has anyone had experience > with this type of situation? -- David Madland CCIE# 2016 Sr. Network Engineer Qwest Communications 612-664-3367 "Government can do something for the people only in proportion as it can do something to the people." -- Thomas Jefferson Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=72037&t=72034 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: CCDP requirements: pointless to do CID if you don' [7:72027]
MCMORDIE Shane (BMB) wrote: > > Hi, > > I'm aiming at CCDP but I don't have BCRAN. Am I correct in > thinking > that there is no point in me registering for CID before > registration > finally ends on July 25th - because to go this route to CCDP, > BCRAN is > also needed - but is no longer available? BCRAN is still available. It's still required for CCNP so it has to be available. More here: http://www.cisco.com/warp/public/10/wwtraining/certprog/lan/programs/ccnp.html The real question is can you get CCDP without BCRAN even during this transition period? At some point BCRAN won't be required for CCDP. Has that started already? I think it has. You better ask Cisco and/or check your progress on the tracking system to be sure, though. Good luck! Priscilla > > Therefore better for me to forget CID and go straight to ARCH? > > Thanks, > > Shane > > > DISCLAIMER > > "This e-mail and any attachment thereto may contain information > which is > confidential and/or protected by intellectual property rights > and are intended > for the sole use of the recipient(s) named above. > Any use of the information contained herein (including, but not > limited to, > total or partial reproduction, communication or distribution in > any form) by > other persons than the designated recipient(s) is prohibited. > If you have received this e-mail in error, please notify the > sender either by > telephone or by e-mail and delete the material from any > computer". > > Thank you for your cooperation. > > For further information about Proximus mobile phone services > please see our > website at http://www.proximus.be or refer to any Proximus agent. > > Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=72036&t=72027 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: cisco back to back cable [7:71992]
Perhaps a copy of the configs would be helpful here. -Original Message- From: KW S [mailto:[EMAIL PROTECTED] Sent: Monday, July 07, 2003 12:22 PM To: [EMAIL PROTECTED] Subject: cisco back to back cable [7:71992] Dear All I have a 2501 and 2505 and I am trying to set up a homelab..These 2 routers come with a cable which is a DB60(DTE) and the other end is a DB60(DCE).This is wat that is label on the cable. Anyway, I try to connect this cable to the serial interface of the 2 routers...and both the routers are showing serial is down and line protocol is down. I guess I have used the wrong cable...or maybe I have missed out something. Please comment.. Regards, kws Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=72038&t=71992 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: ISDN case... [7:72017]
Hi Heiman, You won't get a bill: there won't be any ISDN layer 3 call: only your ISDN bearer, so layer 1/2 will come up. Only when your serial goes down, an ISDN call will be made and then you have to pay. Eric - Original Message - From: "H T" To: Sent: Tuesday, July 08, 2003 3:05 PM Subject: Re: ISDN case... [7:72017] > Hi Eric, > Thanks for what you wrote... > > I want the BRI just for a back up... so the line should stay down all the > time when every thing is normal. I want the BRI come up only once the serial > go down " in this way we get small bill" :) > > how about the routing section ? did you had a look at? > > > cheers, > Heiman. > > ""ericbrouwers"" wrote in message > news:[EMAIL PROTECTED] > > This is normal behaviour: if you configure BRI as backup, it will go in > > standby mode and line protocol goes down. You can avoid this by > configuring > > a dialer interface as backup. Then the dialer interface will go in standby > > mode, but the BRI stays up!! This is preferred since: > > 1. some Telco's will lock out your line when it is too long down; > > 2. you can easily detect if your backup goes down. > > This won't give any surprises when you really need the backup! > > > > So replace this: > > interface s0 > >backup interface bri0 > > > > By following: > > interface s0 > >backup interface dialer 1 > > > > interface dialer 1 > >dialer pool 1 > > > > interface bri0 > >dialer pool-member 1 > > > > In your case I would try something like this: > > > > interface s0 > >ip address 172.20.14.1 255.255.255.252 > >backup interface dialer 1 > > > > dialer-list 1 protocol ip permit > > > > interface dialer 1 > >description Dialer to LDS > >ip address 172.21.14.1 255.255.255.0 > >encapsulation ppp > >ppp authentication chap > >ppp chap password 7 1307161100191426222A23 > >dialer idle-timeout 750 > >dialer map ip 172.21.14.2 name LDS 23225374 > >dialer-group 1 > >dialer pool 1 > > > > interface bri0 > >isdn switch-type basic-net3 > >encapsulation ppp > >ppp authentication chap > >ppp chap password 7 1307161100191426222A23 > >dialer pool-member 1 > > > > Hope this helps, > > > > Eric Brouwers > > > > PS > > Be careful about moving all statements below BRI interface to dialer > > interface. This is what Cisco says about it: > > > > "...Commands that apply before authentication is complete must be > configured > > on the physical (BRI) interface and not on the dialer profile. Dialer > > profiles do not copy PPP authentication commands (or LCP commands) to the > > physical interface > > .." > > > > I've never tried the most efficient configuration, that's why there is > some > > redundancy in the config above. Maybe someone else can comment about > > removing the PPP encaps. and auth. commands from the dialer interface?? > > > > Cheers, > > > > Eric > > > > > > - Original Message - > > From: "H T" > > To: > > Sent: Tuesday, July 08, 2003 8:36 AM > > Subject: ISDN case... [7:72017] > > > > > > > Hi all, > > > I have a problem with my ISDN back up link... the interface in STANDBY > > mode. > > > > > > > > > TBRS#sho inter bri0 > > > BRI0 is standby mode, line protocol is down > > > Hardware is PQUICC BRI > > > Description: Dialer to Lovisenberg > > > Internet address is 172.21.14.1/24 > > > MTU 1500 bytes, BW 64 Kbit, DLY 2 usec, > > > reliability 255/255, txload 1/255, rxload 1/255 > > > Encapsulation PPP, loopback not set > > > Last input never, output never, output hang never > > > Last clearing of "show interface" counters 00:39:45 > > > Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 > > > Queueing strategy: weighted fair > > > Output queue: 0/1000/64/0 (size/max total/threshold/drops) > > > Conversations 0/0/16 (active/max active/max total) > > > Reserved Conversations 0/0 (allocated/max allocated) > > > Available Bandwidth 48 kilobits/sec > > > 5 minute input rate 0 bits/sec, 0 packets/sec > > > 5 minute output rate 0 bits/sec, 0 packets/sec > > > 0 packets input, 0 bytes, 0 no buffer > > > Received 0 broadcasts, 0 runts, 0 giants, 0 throttles > > > 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort > > > 0 packets output, 0 bytes, 0 underruns > > > 0 output errors, 0 collisions, 0 interface resets > > > 0 output buffer failures, 0 output buffers swapped out > > > 0 carrier transitions > > > > > > > > > and the configuration is > > > > > > hostname TBRS > > > ! > > > username LDS password 7 15100A0F0F3F3B28213D3E > > > isdn switch-type basic-net3 > > > ! > > > interface BRI0 > > > description Dialer to LDS > > > ip address 172.21.14.1 255.255.255.0 > > > encapsulation ppp > > > dialer idle-timeout 750 > > > dialer map ip 172.21.14.2 name LDS 23225374 > > > dialer-group 1 > > > isdn switch-type basic-net3 > > > ppp authentication chap > > > ppp chap password 7 1307161100191426222
RE: Maximum segment size in TCP [7:72030]
I have seen a similar issue with a VPN connection. The problem was caused when an NT admin wrote a batch file that did a large FTP across the link every 45 minutes. The large volume of traffic caused the router cpu to spike due to the encryp/decryp load… hence slow performance. I would try to check to see if there is a large amount of traffic on the VPN when you are experiencing slow response. Mike kuma kk wrote: > > Hello group, > > I am facing slow response issue when connecting to Mainframe. > This is how my > connectivity goes > > [EMAIL PROTECTED] A ---> FrameRelay(WAN) --> Location B ---> Site to > Site VPN (T1) > --> [EMAIL PROTECTED] C > > I have captured the packet using ethereal and found that Source > PC TCP > Maximum Segment Size is 1456bytes and that of Mainframe is > 4056bytes. This > slow response issue with mainframe is intermittent. And there > is no issue at > the mainframe as it works fine when I connect from within the > Location C > > Source side there is no issue since for some other mainframe at > Location D, > I am getting good response and the Source PC MSS is 1456bytes > and that of > Mainframe MSS is 536bytes. The only difference in this > connectivity is that > this mainframe is connected using an framerealy from Location B > to Location > D (given below) > > [EMAIL PROTECTED] A ---> FrameRelay(WAN) --> Location B ---> > FrameRelay(WAN)--> > [EMAIL PROTECTED] D > > I would like to know whether the MSS Size of 4056bytes from > mainframe in the > Location C attributes to the slow reponse issue. Is the high > MSS size is due > to Site-to Site VPN from Location B to C( due to excess header > information > due to VPN) or something else. > > Would appreciate your response. > > TIA, > Kum > > _ > Design your holidays. At your convenience. > http://www.flexihols.com/2003/index.php Click here. > > Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=72041&t=72030 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: ISDN Port goes to Deactivated mode [7:72022]
Probably layer 1 and 2 are deactivated by the Telco. It's better to use a dialer interface as backup of a serial line. Then L1/2 stays up. Refer to other ISDN thread as well. If you don't want to do that, try to change the TEI negotiation. Cisco's default is TEI negotiation when the router is powered up. TEI negotiation also happens when you reset your interface. So try to configure TEI negotiation on first call for your backup interface only: interface bri0 isdn tei first-call When the serial goes down, the backup makes its first calls and trigger TEI negotiation. I hope ... Let me know, Eric Brouwers - Original Message - From: "George Murage" To: Sent: Tuesday, July 08, 2003 6:52 PM Subject: RE: ISDN Port goes to Deactivated mode [7:72022] > I have experienced the same problem and would really like to see what the > others have to say. > > > While testing, I put my router with a BRI-1B-S/T card behind a PBX with an > NTI card and the problem vanished. > > This led me to believe that the problem has something to do with the telco. > > I *think* the telco switch may not be able to detect, in a timely fashion > that your isdn line is active, because European ISDN switches normally > deactivate layer 1 or layer 2 of an idle isdn line. > > Removing and re-inserting the cable sort of resets the layers 1 and 2. Has > the same effect as typing "clear int brix/y" on the router. > > Regards > George Murage > > -Original Message- > From: H T [mailto:[EMAIL PROTECTED] > Sent: Tuesday, July 08, 2003 5:49 PM > To: [EMAIL PROTECTED] > Subject: Re: ISDN Port goes to Deactivated mode [7:72022] > > Hi, > can you show us your running config of both sides, so we can know where > would be the problem? > > > cheers, > Heiman. > > > > ""Mr piyush shah"" wrote in message > news:[EMAIL PROTECTED] > > Dear all > > I am having 128 kbps Leased Line with ISDN backup.As > > the Link goes Down ,ISDN should trigger,however in my > > case the ISDN link does not come up and goes to > > deactivated mode.What could be the problem .I have > > seen that upon removing the ISDN link and inserting > > back it gives the status as ACTIVE.What could be the > > problm? > > Kindly help as I am not able to use backup link due to > > this reason. > > > > I have attached herewitht the log of sh isdn status > > command for your kind pwerusal > > > > Thanks in advance. > > > > Regards > > > > > > Piyush > > > > router-1#sh ISDN status > > > > ISDN BRI0 interface > > dsl 0, interface ISDN Switchtype = basic-net3 > > Layer 1 Status: > > DEACTIVATED > > Layer 2 Status: > > TEI = 85, Ces = 1, SAPI = 0, State = > > TEI_ASSIGNED > > I_Queue_Len 0, UI_Queue_Len 0 > > Layer 3 Status: > > 0 Active Layer 3 Call(s) > > Activated dsl 0 CCBs = 0 > > The Free Channel Mask: 0x8003 > > Total Allocated ISDN CCBs = 0 > > > > > > Send free SMS using the Yahoo! Messenger. Go to > > http://in.mobile.yahoo.com/new/pc/ Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=72042&t=72022 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: OSPF max Router-LSA links [7:72024]
hebn wrote: > > hello,everyone: >OSPF use raw socket (datagram) to communicate with peers. In > general, layer 2 frame has a MTU of 1500 bytes. >how does cisco router propagate router-lsa whose size exceed > 1500 bytes(more than 122 links in one area)? Well, I don't have a definite answer, but I'll discuss it with you in the hopes of lighting a fire under one of the OSPF experts on this list. Howard? Chuck? Peter? Where's Pamela when we need her? :-) OSPF runs directly above IP. I don't know if that could be called "raw socket" which is a UNIX thing? My perception is that with Cisco IOS, OSPF calls IP with a set of parameters and lets IP handle the rest. So maybe that's sort of raw. I can say this: The OSPF packets I have seen coming out of Cisco routers have the IP fragmentation bit set to "May Fragment." This makes me think that Cisco's OSPF relies on IP to push the bytes into the data-link-layer frame and fragment if necessary. The OSPF RFC (RFC 2178) says this: "OSPF does not define a way to fragment its protocol packets, and depends on IP fragmentation when transmitting packets larger than the network MTU. If necessary, the length of OSPF packets can be up to 65,535 bytes (including the IP header). The OSPF packet types that are likely to be large (Database Description Packets, Link State Request, Link State Update, and Link State Acknowledgment packets) can usually be split into several separate protocol packets, without loss of functionality. This is recommended; IP fragmentation should be avoided whenever possible." Unfortunately, that's not very clear. It implies that the recommended method is for OSPF to split its own protocol packets. But that the method for doing this is undefined and that's OK because OSPF can depend on IP to do fragmentation. Cisco routers tell each other their MTU in database description packets, per RFC 2178. Until recently, if the routers didn't agree on the MTU, they wouldn't become adjacent. A recent IOS version supports telling a router to ignore the other side's MTU so they can still become adjacent. That doesn't answer your question, but maybe there are some hints in the article that discusse the "ip ospf mtu-ignore" feature here: http://www.cisco.com/warp/public/104/12.html ___ Priscilla Oppenheimer www.priscilla.com > __ > > === > [EMAIL PROTECTED] (http://bizsite.sina.com.cn) > > Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=72043&t=72024 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: OSPF max Router-LSA links [7:72024]
At 9:38 PM + 7/8/03, Priscilla Oppenheimer wrote: >hebn wrote: >> >> hello,everyone: > >> OSPF use raw socket (datagram) to communicate with peers. In > > general, layer 2 frame has a MTU of 1500 bytes. I'm not sure I'd call it a strict datagram protocol. In some cases, it's acknowledged datagram, either directly or indirectly acknowledged. In other cases, such as database initialization, there's clearly a connection -- just not a TCP connection. > >how does cisco router propagate router-lsa whose size exceed >> 1500 bytes(more than 122 links in one area)? > >Well, I don't have a definite answer, but I'll discuss it with you in the >hopes of lighting a fire under one of the OSPF experts on this list. Howard? >Chuck? Peter? Where's Pamela when we need her? :-) It's fairly simple in Wellfleet/Bay/Nortel code -- you send multiple LSAs. There's nothing that says all the database entries of one type have to fit in the same LSupdate. Certainly, in a large area, there will need to be more than one LSupdate to convey all the Type 2 LSAs. > >OSPF runs directly above IP. I don't know if that could be called "raw >socket" which is a UNIX thing? My perception is that with Cisco IOS, OSPF >calls IP with a set of parameters and lets IP handle the rest. So maybe >that's sort of raw. I'd have to go look at Moy's or another UNIX based implementation to see how the calling is done. IOS is not UNIX based. Several other vendor implementations run a realtime OS such as VXworks. > >I can say this: The OSPF packets I have seen coming out of Cisco routers >have the IP fragmentation bit set to "May Fragment." This makes me think >that Cisco's OSPF relies on IP to push the bytes into the data-link-layer >frame and fragment if necessary. > >The OSPF RFC (RFC 2178) says this: > >"OSPF does not define a way to fragment its protocol packets, and depends on >IP fragmentation when transmitting packets larger than the network MTU. If >necessary, the length of OSPF packets can be up to 65,535 bytes (including >the IP header). The OSPF packet types that are likely to be large (Database >Description Packets, Link State Request, Link State Update, and Link State >Acknowledgment packets) can usually be split into several separate protocol >packets, without loss of functionality. This is recommended; IP >fragmentation should be avoided whenever possible." > >Unfortunately, that's not very clear. It implies that the recommended method >is for OSPF to split its own protocol packets. But that the method for doing >this is undefined and that's OK because OSPF can depend on IP to do >fragmentation. Fragmentation gets scary when you are doing real-time control plane traffic. > >Cisco routers tell each other their MTU in database description packets, per >RFC 2178. Until recently, if the routers didn't agree on the MTU, they >wouldn't become adjacent. A recent IOS version supports telling a router to >ignore the other side's MTU so they can still become adjacent. > >That doesn't answer your question, but maybe there are some hints in the >article that discusse the "ip ospf mtu-ignore" feature here: > >http://www.cisco.com/warp/public/104/12.html Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=72044&t=72024 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: OSPF max Router-LSA links [7:72024]
The LSA will be fragmented at the IP layer. Thanks, Zsombor At 11:39 AM 7/8/2003 +, hebn wrote: >layer 2 frame has a MTU of 1500 bytes. >how does cisco router propagate router-lsa whose size exceed 1500 >bytes(more than 122 links in one area)? Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=72045&t=72024 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: OSPF max Router-LSA links [7:72024]
At 10:46 PM + 7/8/03, Zsombor Papp wrote: >The LSA will be fragmented at the IP layer. Do you know for certain this is what Cisco's implementation does? The OSPF code is aware of the MTU and can build OSPF packets for it. I don't think you're really going to simplify it by relieving it of the need to keep track of lengths. On the other hand, if you send a LSupdate that is at the MTU, the receiving router can immediately start checking and installing it in the LSDB, without waiting for fragments. This allows some concurrency between OSPF packet transmission and OSPF protocol processing. >At 11:39 AM 7/8/2003 +, hebn wrote: >>layer 2 frame has a MTU of 1500 bytes. >> how does cisco router propagate router-lsa whose size exceed 1500 > >bytes(more than 122 links in one area)? Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=72046&t=72024 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: OSPF max Router-LSA links [7:72024]
The original question (as I understood) was about a single LSA that is larger than 1500 bytes (think Type 1 LSA for a router with 200 interfaces). I can't see how such an LSA could be divided into multiple OSPF messages so the only logical (implementation independent) solution seems to be to fragment the packet at the IP layer. Am I missing something? If you are asking about how LSAs that are individually smaller than 1500 byte are grouped together, then my (moderately educated :) answer is this: IOS defines a constant called MAXOSPFPACKETSIZE to be 1500 bytes and another constant called MAX_OSPF_DATA to be MAXOSPFPACKETSIZE - IPHEADERBYTES - OSPF_HDR_SIZE. The code that transmits the LSAs keeps packing the LSAs into the same packet as long as their total length is below MAX_OSPF_DATA, the net result being that the size of the IP packet can be up to 1500 bytes (and will in fact be close to it if the individual LSAs are not too big) if there are enough LSAs, regardless of the MTU. So for example if you set the IP MTU on an Ethernet interface to 500 bytes, and you have a large enough OSPF database, then you should see a lot of fragmented OSPF packets, regardless of how big the individual LSAs are. I didn't write the code though, so take all this with a grain of salt. :) Thanks, Zsombor At 12:40 AM 7/9/2003 +, Howard C. Berkowitz wrote: >At 10:46 PM + 7/8/03, Zsombor Papp wrote: > >The LSA will be fragmented at the IP layer. > >Do you know for certain this is what Cisco's implementation does? >The OSPF code is aware of the MTU and can build OSPF packets for it. >I don't think you're really going to simplify it by relieving it of >the need to keep track of lengths. > >On the other hand, if you send a LSupdate that is at the MTU, the >receiving router can immediately start checking and installing it in >the LSDB, without waiting for fragments. This allows some concurrency >between OSPF packet transmission and OSPF protocol processing. > > >At 11:39 AM 7/8/2003 +, hebn wrote: > >>layer 2 frame has a MTU of 1500 bytes. > >> how does cisco router propagate router-lsa whose size exceed 1500 > > >bytes(more than 122 links in one area)? Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=72048&t=72024 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: Movie [7:72049]
Please see the attached zip file for details. [GroupStudy removed an attachment of type application/octet-stream which had a name of your_details.zip] Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=72049&t=72049 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: OSPF max Router-LSA links [7:72024]
Howard C. Berkowitz wrote: > > At 10:46 PM + 7/8/03, Zsombor Papp wrote: > >The LSA will be fragmented at the IP layer. > > Do you know for certain this is what Cisco's implementation > does? > The OSPF code is aware of the MTU and can build OSPF packets > for it. > I don't think you're really going to simplify it by relieving > it of > the need to keep track of lengths. Can you think of a good way to test it in a lab?? The RFC says that dividing up the updates is recomended over letting IP do the fragmentation and Cisco is generally good at doing things the recommended way usually. Priscilla > > On the other hand, if you send a LSupdate that is at the MTU, > the > receiving router can immediately start checking and installing > it in > the LSDB, without waiting for fragments. This allows some > concurrency > between OSPF packet transmission and OSPF protocol processing. > > >At 11:39 AM 7/8/2003 +, hebn wrote: > >>layer 2 frame has a MTU of 1500 bytes. > >> how does cisco router propagate router-lsa whose size > exceed 1500 > > >bytes(more than 122 links in one area)? > > Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=72047&t=72024 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
