Thanks Steve. I would hope GBLX has some sort of SONET protection deployed accross their network. Mohamed On Tue, 27 Jun 2000, Steve Nash wrote:
Rumors are of a GC fiber cut about 15 miles outside of SF.
Mohamed Hirse wrote:
Can someone from Global crossing help explain this problem. There seems to be some sort of internal network problem. Traceroutes attached. This affecting many of GBLX customers.
Thanks Mohamed
route-server.cerf.net>traceroute www.juniper.net
Type escape sequence to abort. Tracing the route to www.juniper.net (207.17.137.30)
1 fe8-0-0.san-bb1.cerf.net (134.24.38.225) [AS 1740] 4 msec 0 msec 0 msec 2 fe0-0-0.san-bb2.cerf.net (134.24.29.102) [AS 1740] 0 msec 4 msec 0 msec 3 so2-1-2-155M.san-bb4.cerf.net (134.24.29.181) [AS 1740] 0 msec 4 msec 0 msec 4 pos3-0-622M.lax-bb5.cerf.net (134.24.29.14) [AS 1740] 4 msec 8 msec 4 msec 5 pos5-0-622M.lax-bb4.cerf.net (134.24.33.169) [AS 1740] 4 msec 8 msec 4 msec 6 pos6-0-622M.sfo-bb3.cerf.net (134.24.29.233) [AS 1740] 72 msec 76 msec 72 msec 7 pos5-0-0-155M.sjc-bb2.cerf.net (134.24.29.22) [AS 1740] 76 msec pos0-0-155M.sjc-bb2.cerf.net (134.24.32.90) [AS 1740] 72 msec pos5-0-0-155M.sjc-bb2.cerf.net (134.24.29.22) [AS 1740] 72 msec 8 * * * 9 pos4-0-2488M.cr1.SNV3.gblx.net (208.50.169.74) [AS 3549] !H !H !H route-server.cerf.net>traceroute www.juniper.net
Type escape sequence to abort. Tracing the route to www.juniper.net (207.17.137.30)
1 fe8-0-0.san-bb1.cerf.net (134.24.38.225) [AS 1740] 0 msec 0 msec 0 msec 2 fe0-0-0.san-bb2.cerf.net (134.24.29.102) [AS 1740] 0 msec 0 msec 4 msec 3 so2-1-2-155M.san-bb4.cerf.net (134.24.29.181) [AS 1740] 0 msec 0 msec 0 msec 4 pos3-0-622M.lax-bb5.cerf.net (134.24.29.14) [AS 1740] 4 msec 8 msec 4 msec 5 pos5-0-622M.lax-bb4.cerf.net (134.24.33.169) [AS 1740] 8 msec 4 msec 8 msec 6 pos6-0-622M.sfo-bb3.cerf.net (134.24.29.233) [AS 1740] 72 msec 72 msec 72 msec 7 pos5-0-0-155M.sjc-bb2.cerf.net (134.24.29.22) [AS 1740] 76 msec pos0-0-155M.sjc-bb2.cerf.net (134.24.32.90) [AS 1740] 76 msec 72 msec 8 * * * 9 pos4-0-2488M.cr1.SNV3.gblx.net (208.50.169.74) [AS 3549] !H !H !H route-server.cerf.net>
-- Steven Nash Director of Network Engineering - North American Region Lightning Internet Services, LLC http://www.lightning.net o:516.248.8400 f:888.935.2698 c:516.779.3007 p:888.935.2698
On Tue, Jun 27, 2000 at 05:16:34PM -0400, Mohamed Hirse wrote:
Thanks Steve. I would hope GBLX has some sort of SONET protection deployed accross their network.
Why - if they have other means of protection, it can be just as good. /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: Geek @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them.
I only said SONET because it's layer one. If you can reroute traffic to other circuits that are terminated on other routers that have APS enabled you can offset any or almost any fiber cut. Unless both Working and Protect get taken out by some strange reason. What do you propose? Mohamed On Tue, 27 Jun 2000, Jesper Skriver wrote:
On Tue, Jun 27, 2000 at 05:16:34PM -0400, Mohamed Hirse wrote:
Thanks Steve. I would hope GBLX has some sort of SONET protection deployed accross their network.
Why - if they have other means of protection, it can be just as good.
/Jesper
-- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: Geek @ AS2109 (A much smaller network ;-)
One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them.
On Tue, Jun 27, 2000 at 05:35:32PM -0400, Mohamed Hirse wrote:
I only said SONET because it's layer one. If you can reroute traffic to other circuits that are terminated on other routers that have APS enabled you can offset any or almost any fiber cut. Unless both Working and Protect get taken out by some strange reason. What do you propose?
Having 2 non-protected diverse routed circuits, both live carrying traffic, but not more than one can carry all the traffic when the other fail ... /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: Geek @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them.
I agree this is an option. How would you control the traffic flow if one link goes down? The APS configuration on the router relies on communication between the router and the ADM. with in the configuration of the router you would label and assign groups to the interface configuration. This would tell the router/interface to respond accordingly when the circuit switches from working to protect. This occurs automatically (most of the most of the time) Are you proposing using some sort of routing mechanism to shift the traffic or will there be intelligence build in to the ADM that would allow the router to switch automatically? Cheers, Mohamed On Wed, 28 Jun 2000, Jesper Skriver wrote:
On Tue, Jun 27, 2000 at 05:35:32PM -0400, Mohamed Hirse wrote:
I only said SONET because it's layer one. If you can reroute traffic to other circuits that are terminated on other routers that have APS enabled you can offset any or almost any fiber cut. Unless both Working and Protect get taken out by some strange reason. What do you propose?
Having 2 non-protected diverse routed circuits, both live carrying traffic, but not more than one can carry all the traffic when the other fail ...
/Jesper
-- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: Geek @ AS2109 (A much smaller network ;-)
One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them.
On Wed, Jun 28, 2000 at 09:13:13AM -0400, Mohamed Hirse wrote:
I agree this is an option. How would you control the traffic flow if one link goes down?
The APS configuration on the router relies on communication between the router and the ADM. with in the configuration of the router you would label and assign groups to the interface configuration. This would tell the router/interface to respond accordingly when the circuit switches from working to protect. This occurs automatically (most of the most of the time)
Are you proposing using some sort of routing mechanism to shift the traffic or will there be intelligence build in to the ADM that would allow the router to switch automatically?
Just use plain routing, or if you feel like it, MPLS TE tunnels ... /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: Geek @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them.
Could this possibly be linked to the Pac Bell fiber cut in San Bruno that took Sean and EMS off-net? -j On Tue, Jun 27, 2000 at 05:16:34PM -0400, Mohamed Hirse wrote:
Thanks Steve. I would hope GBLX has some sort of SONET protection deployed accross their network.
Mohamed
On Tue, 27 Jun 2000, Steve Nash wrote:
Rumors are of a GC fiber cut about 15 miles outside of SF.
Mohamed Hirse wrote:
Can someone from Global crossing help explain this problem. There seems to be some sort of internal network problem. Traceroutes attached. This affecting many of GBLX customers.
Thanks Mohamed
route-server.cerf.net>traceroute www.juniper.net
Type escape sequence to abort. Tracing the route to www.juniper.net (207.17.137.30)
1 fe8-0-0.san-bb1.cerf.net (134.24.38.225) [AS 1740] 4 msec 0 msec 0 msec 2 fe0-0-0.san-bb2.cerf.net (134.24.29.102) [AS 1740] 0 msec 4 msec 0 msec 3 so2-1-2-155M.san-bb4.cerf.net (134.24.29.181) [AS 1740] 0 msec 4 msec 0 msec 4 pos3-0-622M.lax-bb5.cerf.net (134.24.29.14) [AS 1740] 4 msec 8 msec 4 msec 5 pos5-0-622M.lax-bb4.cerf.net (134.24.33.169) [AS 1740] 4 msec 8 msec 4 msec 6 pos6-0-622M.sfo-bb3.cerf.net (134.24.29.233) [AS 1740] 72 msec 76 msec 72 msec 7 pos5-0-0-155M.sjc-bb2.cerf.net (134.24.29.22) [AS 1740] 76 msec pos0-0-155M.sjc-bb2.cerf.net (134.24.32.90) [AS 1740] 72 msec pos5-0-0-155M.sjc-bb2.cerf.net (134.24.29.22) [AS 1740] 72 msec 8 * * * 9 pos4-0-2488M.cr1.SNV3.gblx.net (208.50.169.74) [AS 3549] !H !H !H route-server.cerf.net>traceroute www.juniper.net
Type escape sequence to abort. Tracing the route to www.juniper.net (207.17.137.30)
1 fe8-0-0.san-bb1.cerf.net (134.24.38.225) [AS 1740] 0 msec 0 msec 0 msec 2 fe0-0-0.san-bb2.cerf.net (134.24.29.102) [AS 1740] 0 msec 0 msec 4 msec 3 so2-1-2-155M.san-bb4.cerf.net (134.24.29.181) [AS 1740] 0 msec 0 msec 0 msec 4 pos3-0-622M.lax-bb5.cerf.net (134.24.29.14) [AS 1740] 4 msec 8 msec 4 msec 5 pos5-0-622M.lax-bb4.cerf.net (134.24.33.169) [AS 1740] 8 msec 4 msec 8 msec 6 pos6-0-622M.sfo-bb3.cerf.net (134.24.29.233) [AS 1740] 72 msec 72 msec 72 msec 7 pos5-0-0-155M.sjc-bb2.cerf.net (134.24.29.22) [AS 1740] 76 msec pos0-0-155M.sjc-bb2.cerf.net (134.24.32.90) [AS 1740] 76 msec 72 msec 8 * * * 9 pos4-0-2488M.cr1.SNV3.gblx.net (208.50.169.74) [AS 3549] !H !H !H route-server.cerf.net>
-- Steven Nash Director of Network Engineering - North American Region Lightning Internet Services, LLC http://www.lightning.net o:516.248.8400 f:888.935.2698 c:516.779.3007 p:888.935.2698
-- /--------------------------/ Jason Legate \------------------------\ | jlegate@sitesmith.com | SiteSmith, Inc. | | 24x7 Call Center | http://www.sitesmith.com | | 888.898.7667 | PGP Key ID - 0xA855AAC3 | +---------------------------------+--------------------------------+ | Fingerprint - 2D5F 87A0 26E6 A65B 6837 D100 FB54 A972 A855 AAC3 | \------------------------------------------------------------------/
participants (3)
-
Jason Legate -
Jesper Skriver -
Mohamed Hirse