AFDDN.BEACH@GUNTER-ADAM.AF.MIL (06/02/89)
Anybody got a quick answer to this and I'll owe you a beer.
We're installing cisco MGS gateways at different sites on Milnet and
occasionally a problem crops up with exchanging EGP updates with the
"new" core buttergates. Essentially there seems to be an infinite
cycling up and down between the gateways with the core never sending an
update.
A brief example of the exchanges follows. Our gateway is sending updates
and the real interesting part of it is that if the PSN our gateway is
on gets reset, the problem clears up immediately.
I would very much appreciate any hints, suggestions, or detailed technical
explanations.
Darrel B.
Ex***********
EGP: from 26.19.0.222 to 26.20.0.16, version=2, asystem=44429, sequence=3965
Type=REACH, Code=HELLO, Status=1 (UP)
EGP: 26.6.0.103 going from DOWN to UP
EGP: from 26.19.0.222 to 26.6.0.103, version=2, asystem=44429, sequence=2258
Type=POLL, Code=0, Status=1 (UP), Net=26.0.0.0
EGP: from 26.19.0.222 to 26.6.0.103, version=2, asystem=44429, sequence=192
Type=UPDATE, Code=0, Status=129 (UP), IntGW=1, ExtGW=0, Net=26.0.0.0
Network 26.0.0.0 via 26.19.0.222 in 0 hops
Network 132.61.0.0 via 26.19.0.222 in 0 hops
EGP: from 26.19.0.222 to 26.6.0.103, version=2, asystem=44429, sequence=2259
Type=REACH, Code=HELLO, Status=1 (UP)
EGP: 26.20.0.16 going from UP to DOWN
EGP: from 26.19.0.222 to 26.20.0.16, version=2, asystem=44429, sequence=3965
Type=REACH, Code=HELLO, Status=2 (DOWN)
EGP: from 26.20.0.16 to 26.19.0.222, version=2, asystem=164, sequence=398
Type=POLL, Code=0, Status=1 (UP), Net=26.0.0.0
EGP: 26.20.0.16 state is DOWN, bad type 2 when down
EGP: 26.6.0.103 going from UP to DOWN
EGP: from 26.19.0.222 to 26.6.0.103, version=2, asystem=44429, sequence=2259
Type=REACH, Code=HELLO, Status=2 (DOWN)
EGP: from 26.6.0.103 to 26.19.0.222, version=2, asystem=164, sequence=199
Type=POLL, Code=0, Status=1 (UP), Net=26.0.0.0
EGP: 26.6.0.103 state is DOWN, bad type 2 when down
EGP: from 26.19.0.222 to 26.20.0.16, version=2, asystem=44429, sequence=3965
Type=REACH, Code=HELLO, Status=2 (DOWN)
EGP: from 26.20.0.16 to 26.19.0.222, version=2, asystem=164, sequence=3965
Type=REACH, Code=I-HEARD-YOU, Status=1 (UP)
EGP: from 26.20.0.16 to 26.19.0.222, version=2, asystem=164, sequence=399
Type=POLL, Code=0, Status=1 (UP), Net=26.0.0.0
EGP: 26.20.0.16 state is DOWN, bad type 2 when down
EGP: from 26.19.0.222 to 26.6.0.103, version=2, asystem=44429, sequence=2259
Type=REACH, Code=HELLO, Status=2 (DOWN)
EGP: from 26.6.0.103 to 26.19.0.222, version=2, asystem=164, sequence=2259
Type=REACH, Code=I-HEARD-YOU, Status=1 (UP)
EGP: from 26.6.0.103 to 26.19.0.222, version=2, asystem=164, sequence=200
Type=POLL, Code=0, Status=1 (UP), Net=26.0.0.0
EGP: 26.6.0.103 state is DOWN, bad type 2 when down
EGP: 26.20.0.16 going from DOWN to UP
EGP: from 26.19.0.222 to 26.20.0.16, version=2, asystem=44429, sequence=3965
Type=POLL, Code=0, Status=1 (UP), Net=26.0.0.0
EGP: from 26.19.0.222 to 26.20.0.16, version=2, asystem=44429, sequence=309
Type=UPDATE, Code=0, Status=129 (UP), IntGW=1, ExtGW=0, Net=26.0.0.0
Network 26.0.0.0 via 26.19.0.222 in 0 hops
Network 132.61.0.0 via 26.19.0.222 in 0 hops
EGP: from 26.19.0.222 to 26.20.0.16, version=2, asystem=44429, sequence=3966
Type=REACH, Code=HELLO, Status=1 (UP)
EGP: 26.6.0.103 going from DOWN to UP
EGP: from 26.19.0.222 to 26.6.0.103, version=2, asystem=44429, sequence=2259
Type=POLL, Code=0, Status=1 (UP), Net=26.0.0.0
EGP: from 26.19.0.222 to 26.6.0.103, version=2, asystem=44429, sequence=192
Type=UPDATE, Code=0, Status=129 (UP), IntGW=1, ExtGW=0, Net=26.0.0.0
Network 26.0.0.0 via 26.19.0.222 in 0 hops
Network 132.61.0.0 via 26.19.0.222 in 0 hops
EGP: from 26.19.0.222 to 26.6.0.103, version=2, asystem=44429, sequence=2260
Type=REACH, Code=HELLO, Status=1 (UP)
EGP: 26.20.0.16 going from UP to DOWN
EGP: from 26.19.0.222 to 26.20.0.16, version=2, asystem=44429, sequence=3966
Type=REACH, Code=HELLO, Status=2 (DOWN)
EGP: from 26.20.0.16 to 26.19.0.222, version=2, asystem=164, sequence=400
Type=POLL, Code=0, Status=1 (UP), Net=26.0.0.0
EGP: 26.20.0.16 state is DOWN, bad type 2 when down
EGP: 26.6.0.103 going from UP to DOWN
EGP: from 26.19.0.222 to 26.6.0.103, version=2, asystem=44429, sequence=2260
Type=REACH, Code=HELLO, Status=2 (DOWN)
EGP: from 26.6.0.103 to 26.19.0.222, version=2, asystem=164, sequence=201
Type=POLL, Code=0, Status=1 (UP), Net=26.0.0.0
EGP: 26.6.0.103 state is DOWN, bad type 2 when down
EGP: from 26.19.0.222 to 26.20.0.16, version=2, asystem=44429, sequence=3966
Type=REACH, Code=HELLO, Status=2 (DOWN)
EGP: from 26.20.0.16 to 26.19.0.222, version=2, asystem=164, sequence=3966
Type=REACH, Code=I-HEARD-YOU, Status=1 (UP)
EGP: from 26.20.0.16 to 26.19.0.222, version=2, asystem=164, sequence=401
Type=POLL, Code=0, Status=1 (UP), Net=26.0.0.0
EGP: 26.20.0.16 state is DOWN, bad type 2 when down
EGP: from 26.19.0.222 to 26.6.0.103, version=2, asystem=44429, sequence=2260
Type=REACH, Code=HELLO, Status=2 (DOWN)
EGP: from 26.6.0.103 to 26.19.0.222, version=2, asystem=164, sequence=2260
Type=REACH, Code=I-HEARD-YOU, Status=1 (UP)
EGP: from 26.6.0.103 to 26.19.0.222, version=2, asystem=164, sequence=202
Type=POLL, Code=0, Status=1 (UP), Net=26.0.0.0
EGP: 26.6.0.103 state is DOWN, bad type 2 when down
EGP: 26.20.0.16 going from DOWN to UP
EGP: from 26.19.0.222 to 26.20.0.16, version=2, asystem=44429, sequence=3966
Type=POLL, Code=0, Status=1 (UP), Net=26.0.0.0
EGP: from 26.19.0.222 to 26.20.0.16, version=2, asystem=44429, sequence=309
Type=UPDATE, Code=0, Status=129 (UP), IntGW=1, ExtGW=0, Net=26.0.0.0
Network 26.0.0.0 via 26.19.0.222 in 0 hops
Network 132.61.0.0 via 26.19.0.222 in 0 hops
EGP: from 26.19.0.222 to 26.20.0.16, version=2, asystem=44429, sequence=3967
Type=REACH, Code=HELLO, Status=1 (UP)
EGP: 26.6.0.103 going from DOWN to UP
EGP: from 26.19.0.222 to 26.6.0.103, version=2, asystem=44429, sequence=2260
Type=POLL, Code=0, Status=1 (UP), Net=26.0.0.0
EGP: from 26.19.0.222 to 26.6.0.103, version=2, asystem=44429, sequence=192
Type=UPDATE, Code=0, Status=129 (UP), IntGW=1, ExtGW=0, Net=26.0.0.0
Network 26.0.0.0 via 26.19.0.222 in 0 hops
Network 132.61.0.0 via 26.19.0.222 in 0 hops
EGP: from 26.19.0.222 to 26.6.0.103, version=2, asystem=44429, sequence=2261
Type=REACH, Code=HELLO, Status=1 (UP)
EGP: 26.20.0.16 going from UP to DOWN
EGP: from 26.19.0.222 to 26.20.0.16, version=2, asystem=44429, sequence=3967
Type=REACH, Code=HELLO, Status=2 (DOWN)
EGP: from 26.20.0.16 to 26.19.0.222, version=2, asystem=164, sequence=402
Type=POLL, Code=0, Status=1 (UP), Net=26.0.0.0
*****************************
This gones on until the PSN (C-30) is reset, at which point updates from
the core begin coming in.
We've tried using a range of AS numbers, including much lower ones, but
nothing except resetting the PSN seems tp work.
-------brescia@BBN.COM (Mike Brescia) (06/03/89)
We're installing cisco MGS gateways at different sites on Milnet and
occasionally a problem crops up with exchanging EGP updates with the
"new" core buttergates. Essentially there seems to be an infinite
cycling up and down between the gateways with the core never sending an
update.
A brief example of the exchanges follows. Our gateway is sending updates
and the real interesting part of it is that if the PSN our gateway is
on gets reset, the problem clears up immediately.
*******
This gones on until the PSN (C-30) is reset, at which point updates from
the core begin coming in.
... nothing except resetting the PSN seems tp work.
-------
Darrel,
This sounds like an X.25 type of problem, involving x.25 window size, x.25
packet size, and resources in the local PSN. I recall a similar problem where
a system could not get an egp update through when using a packet size of 128
and a window of 2. Try to get the packet size to 512 or 1024, and the window
size 7 (or at least 4 for 1024 byte packets). Note that the EGP update is
sent as 3 1004 byte IP fragments (oh, well, the 3rd is shorter, but it's
growing). The total IP datagram size is around 2800 to 2900 bytes.
Also, make sure you have assurance from Cisco that you have latest revision of
code.
Please send further notes to "gw-fire@bbn.com" if appears to be a core
gateway problem instead of a host-psn interconnect problem.
Regards,
Mike Bresciaalmquist@JESSICA.STANFORD.EDU (Philip Almquist) (06/12/89)
Mike, > We're installing cisco MGS gateways at different sites on Milnet and > occasionally a problem crops up with exchanging EGP updates with the > "new" core buttergates. Essentially there seems to be an infinite > cycling up and down between the gateways with the core never sending an > update. > > This gones on until the PSN (C-30) is reset, at which point updates from > the core begin coming in. > ... nothing except resetting the PSN seems tp work. > > This sounds like an X.25 type of problem, involving x.25 window size, x.25 > packet size, and resources in the local PSN. This same problem (or at least a very similar one) can occur in 1822-connected gateways, or at least it could when Stanford lost its PSN connection in March. At the time, cisco looked at it and Steve Atlas put in some patches into the Butterflies to make them work properly in passive mode, but the problem was still unsolved when the PSN's plug got pulled. Philip PS: It seems that even when things are "working" that EGP connectivity between ciscos and Butterflies is not as robust as one might like. I observe in the SRI ARPANet gateway this morning: neighbor uptime j/k ---------------------------- 10.6.0.22 2:08 3 10.2.0.68 2:46 2 Ideally, one would hope that the uptime of the peer relationships would be roughtly equal to the uptime of the gateway (ie, 2 weeks instead of 2 hours) and that j/k = 4.