Re: IPX Routing problem-Conclusion [7:34485]
Does anyone have any idea why this worked??? Setting the RIP and SAP timers on a __LAN__ link should have had no positive effect. It seems like the only perceivable change would be the flapping of remote networks and servers -- assuming that the timers were not modified on the server also. Any thoughts??? - Tom On Tue, 05 Feb 2002 13:21:55 -0500, Fraasch James wrote: > Ah, to be a network engineer!!! The fun!!! > > So here it is, 28 hours later I have fallen across the solution to the > problem I posted yesterday where people were not able to access an IPX > server. Users were actually able to access it but for no more than a > few minutes at a time. > > Had to add the following command to interface that houses the server: > > interface TokenRing1/2 > mac-address 0200.1099.81ca > ip address 172.25.71.200 255.255.255.0 ip directed-broadcast ipx > encapsulation SNAP > ipx network A040 > ipx update interval rip 300 > ipx update interval sap 300 > ring-speed 16 > > IPX update intervals for rip and sap seem to have solved the problem. > > Thought you might want to know. > > Thanks for the help! Now lets just hope I keep my job! Just kidding, I > can blame it on only being with the company a few months. I'm the new > guy, I can make mistakes and not get in troubleI think that's how it > works. > > James > misconduct and Nondisclosure violations to [EMAIL PROTECTED] Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=34500&t=34485 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: IPX Routing problem-Conclusion [7:34485]
The server must be set with the non-standard 300 second timer also? That would be my theory. Priscilla At 02:50 PM 2/5/02, Tom Martin wrote: >Does anyone have any idea why this worked??? Setting the RIP and SAP >timers on a __LAN__ link should have had no positive effect. It seems >like the only perceivable change would be the flapping of remote networks >and servers -- assuming that the timers were not modified on the server >also. > >Any thoughts??? > >- Tom > >On Tue, 05 Feb 2002 13:21:55 -0500, Fraasch James wrote: > > > Ah, to be a network engineer!!! The fun!!! > > > > So here it is, 28 hours later I have fallen across the solution to the > > problem I posted yesterday where people were not able to access an IPX > > server. Users were actually able to access it but for no more than a > > few minutes at a time. > > > > Had to add the following command to interface that houses the server: > > > > interface TokenRing1/2 > > mac-address 0200.1099.81ca > > ip address 172.25.71.200 255.255.255.0 ip directed-broadcast ipx > > encapsulation SNAP > > ipx network A040 > > ipx update interval rip 300 > > ipx update interval sap 300 > > ring-speed 16 > > > > IPX update intervals for rip and sap seem to have solved the problem. > > > > Thought you might want to know. > > > > Thanks for the help! Now lets just hope I keep my job! Just kidding, I > > can blame it on only being with the company a few months. I'm the new > > guy, I can make mistakes and not get in troubleI think that's how it > > works. > > > > James > > misconduct and Nondisclosure violations to [EMAIL PROTECTED] Priscilla Oppenheimer http://www.priscilla.com Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=34506&t=34485 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: IPX Routing problem-Conclusion [7:34485]
was it traversing two separate vendors by the time it hit the server?
I know with 3com and cisco, the defaults for rip and sap updates are
different. 3com defaults to update on change only...where cisco's defaults
are timed. When you connect both vendors together, cisco will send updates
but 3com won't listen...and since 3com doesn't send updates, cisco with time
the values out and clear routes/saps...
-Patrick
>>> "Priscilla Oppenheimer" 02/05/02 03:25PM >>>
The server must be set with the non-standard 300 second timer also? That
would be my theory.
Priscilla
At 02:50 PM 2/5/02, Tom Martin wrote:
>Does anyone have any idea why this worked??? Setting the RIP and SAP
>timers on a __LAN__ link should have had no positive effect. It seems
>like the only perceivable change would be the flapping of remote networks
>and servers -- assuming that the timers were not modified on the server
>also.
>
>Any thoughts???
>
>- Tom
>
>On Tue, 05 Feb 2002 13:21:55 -0500, Fraasch James wrote:
>
> > Ah, to be a network engineer!!! The fun!!!
> >
> > So here it is, 28 hours later I have fallen across the solution to the
> > problem I posted yesterday where people were not able to access an IPX
> > server. Users were actually able to access it but for no more than a
> > few minutes at a time.
> >
> > Had to add the following command to interface that houses the server:
> >
> > interface TokenRing1/2
> > mac-address 0200.1099.81ca
> > ip address 172.25.71.200 255.255.255.0 ip directed-broadcast ipx
> > encapsulation SNAP
> > ipx network A040
> > ipx update interval rip 300
> > ipx update interval sap 300
> > ring-speed 16
> >
> > IPX update intervals for rip and sap seem to have solved the problem.
> >
> > Thought you might want to know.
> >
> > Thanks for the help! Now lets just hope I keep my job! Just kidding, I
> > can blame it on only being with the company a few months. I'm the new
> > guy, I can make mistakes and not get in troubleI think that's how it
> > works.
> >
> > James
> > misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Priscilla Oppenheimer
http://www.priscilla.com
> Confidentiality Disclaimer
This email and any files transmitted with it may contain confidential and
/or proprietary information in the possession of WellStar Health System,
Inc. ("WellStar") and is intended only for the individual or entity to whom
addressed. This email may contain information that is held to be
privileged, confidential and exempt from disclosure under applicable law. If
the reader of this message is not the intended recipient, you are hereby
notified that any unauthorized access, dissemination, distribution or
copying of any information from this email is strictly prohibited, and may
subject you to criminal and/or civil liability. If you have received this
email in error, please notify the sender by reply email and then delete this
email and its attachments from your computer. Thank you.
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=34510&t=34485
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: IPX Routing problem-Conclusion [7:34485]
It is Cisco to Cisco. 7204 to 2600. 'By changing the update interval from 1 minute to 5 minutes you are preventing the route and server from flapping and thereby keeping your connection to the server up.' This is what the Cisco tech said- AFTER I had already put the command in. I am not sure why it worked either. I would have thought with 1 minute SAP and RIP advertisements it would be better than 5 save for the amount of traffic it produces. I understand 'flapping' in the cable modem sense of the word but I hadnt seen it happen in this environment. To me, the flapping means that the cable modem is connecting and disconnecting at random intervals, sometimes due to incorrect power configurations. But in this sense I am gathering that it means the route to the particular server flapped. If that is the case then it would explain why users could intermittently connect to the server. Then the question becomes, why did the flapping occur in the first place? Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=34513&t=34485 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: IPX Routing problem-Conclusion [7:34485]
IIRC, in the config you posted the intervals were changed on a token ring interface. Is that how you have the 7204 and 2600 connected? If so, are they the only devices on the token ring? John >>> "Fraasch James" 2/5/02 1:58:02 PM >>> It is Cisco to Cisco. 7204 to 2600. 'By changing the update interval from 1 minute to 5 minutes you are preventing the route and server from flapping and thereby keeping your connection to the server up.' This is what the Cisco tech said- AFTER I had already put the command in. I am not sure why it worked either. I would have thought with 1 minute SAP and RIP advertisements it would be better than 5 save for the amount of traffic it produces. I understand 'flapping' in the cable modem sense of the word but I hadnt seen it happen in this environment. To me, the flapping means that the cable modem is connecting and disconnecting at random intervals, sometimes due to incorrect power configurations. But in this sense I am gathering that it means the route to the particular server flapped. If that is the case then it would explain why users could intermittently connect to the server. Then the question becomes, why did the flapping occur in the first place? Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=34517&t=34485 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: IPX Routing problem-Conclusion [7:34485]
this should also work:
ipx update interval rip changes-only
ipx update interval sap changes-only
those are on the interface itself
-Patrick
>>> "Fraasch James" 02/05/02 03:58PM >>>
It is Cisco to Cisco. 7204 to 2600.
'By changing the update interval from 1 minute to 5 minutes you are
preventing the route and server from flapping and thereby keeping your
connection to the server up.'
This is what the Cisco tech said- AFTER I had already put the command in. I
am not sure why it worked either. I would have thought with 1 minute SAP
and RIP advertisements it would be better than 5 save for the amount of
traffic it produces.
I understand 'flapping' in the cable modem sense of the word but I hadnt
seen it happen in this environment. To me, the flapping means that the
cable modem is connecting and disconnecting at random intervals, sometimes
due to incorrect power configurations. But in this sense I am gathering
that it means the route to the particular server flapped. If that is the
case then it would explain why users could intermittently connect to the
server. Then the question becomes, why did the flapping occur in the first
place?
> Confidentiality Disclaimer
This email and any files transmitted with it may contain confidential and
/or proprietary information in the possession of WellStar Health System,
Inc. ("WellStar") and is intended only for the individual or entity to whom
addressed. This email may contain information that is held to be
privileged, confidential and exempt from disclosure under applicable law. If
the reader of this message is not the intended recipient, you are hereby
notified that any unauthorized access, dissemination, distribution or
copying of any information from this email is strictly prohibited, and may
subject you to criminal and/or civil liability. If you have received this
email in error, please notify the sender by reply email and then delete this
email and its attachments from your computer. Thank you.
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=34516&t=34485
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: IPX Routing problem-Conclusion [7:34485]
Yup, I made the changes on the TokenRing interface itself, not the WAN interface. The original config I posted listed just one of the routers that was connected via a serial interface (all T1 lines). There are actually 7 serial connections to this and five token rings. Each interface is its own separate network. I think the problem is like this: The Cisco router is looking for RIP and SAP updates every one or three minutes by default. If your server is configured to send out RIP and SAP updates at any interval greater than what Cisco is looking for, then Cisco forgets the route to the server. By matching the Cisco RIP and SAP update interval to whatever is set on the server on the network, there should never be an interval greater than what is allowed to keep the route. As to whether or not this command should be placed on the WAN interfaces or the LAN interface, well, it was already set on all the WAN interfaces so it looks like it has to be set on each interface where a SNA server is located. The only interface that did not have the command was one that went to another network that was all NT, no IPX at all. James Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=34523&t=34485 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: IPX Routing problem-Conclusion [7:34485]
Very interesting. I wonder why someone would tweak those values on the server in the first place. Unless all the devices on a LAN segment are using the same values, problems are going to arise. From the sounds of it, someone changed the server settings and didn't bother to let everyone else know! John >>> "Fraasch James" 2/5/02 2:49:28 PM >>> Yup, I made the changes on the TokenRing interface itself, not the WAN interface. The original config I posted listed just one of the routers that was connected via a serial interface (all T1 lines). There are actually 7 serial connections to this and five token rings. Each interface is its own separate network. I think the problem is like this: The Cisco router is looking for RIP and SAP updates every one or three minutes by default. If your server is configured to send out RIP and SAP updates at any interval greater than what Cisco is looking for, then Cisco forgets the route to the server. By matching the Cisco RIP and SAP update interval to whatever is set on the server on the network, there should never be an interval greater than what is allowed to keep the route. As to whether or not this command should be placed on the WAN interfaces or the LAN interface, well, it was already set on all the WAN interfaces so it looks like it has to be set on each interface where a SNA server is located. The only interface that did not have the command was one that went to another network that was all NT, no IPX at all. James Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=34530&t=34485 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: IPX Routing problem-Conclusion [7:34485]
Well, I wish it was as easy as saying someone tweaked with the timers on the server but for some reason all our servers are set the same way and so all of our routers have to be set the same way as well. Not only that, but if you look at that TokenRing interface, we are using administrative mac-addresses as well, that is, it is not the actual NIC address, it is something else entirely. And we have one OSPF area for over 100 routers that have to keep track of both IP and IPX routes. But hey, that is why I am here, to help clean up 20 years of bad network planning. Thanks again for everyone's help. I learned a ton! Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=34533&t=34485 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
700 in area! Re: IPX Routing problem-Conclusion [7:34485]
I saw the 100 routers in an area and had to share this! I had an instructor a couple of years ago that worked for IBM-Europe. He said they tried to keep European areas for countries. 1 Country = 1 Area. This all came up when another student asked, "what is a good measure for the number of routers in an area." He responded with the above explanation and then said, "but if you run into an East Germany and a West Germany that decide to become an Unified Germany, you could end up with 800, like we did. That is bad!" just sharing! Fraasch James wrote: > Well, I wish it was as easy as saying someone tweaked with the timers on the > server but for some reason all our servers are set the same way and so all > of our routers have to be set the same way as well. Not only that, but if > you look at that TokenRing interface, we are using administrative > mac-addresses as well, that is, it is not the actual NIC address, it is > something else entirely. And we have one OSPF area for over 100 routers that > have to keep track of both IP and IPX routes. But hey, that is why I am > here, to help clean up 20 years of bad network planning. > > Thanks again for everyone's help. I learned a ton! Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=34540&t=34485 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
