Re: [j-nsp] Speed/Duplex Issue
Did you hard-code the speed/duplex setting on both the Juniper and Cisco switches, or just the Juniper's? We've been happy with auto-nego'ing all connections, including with upstreams. Life has been much easier going that route. I can't remember the last time anything good came out of hard-coding these settings, or when we last did that, for that matter. The Cisco's (customer equipment) were already hard coded as per our instructions at the time. Coming from the Cisco world we had a lot of issues with auto-neg towards various makes/models of switch vendors. Anyways, we're fixed now after understanding Juniper's approach to auto-neg ... thanks...;) Paul ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
[j-nsp] Speed/Duplex Issue
Hi folks... We just cut in another couple of EX4200's into production overnight. These are the first deployments that don't have pure GigE ports - several ports 100/full. When I did the configuration I set the ether-options for 100/full ... most of the ports are facing Cisco switches. All the ports that were hard coded would not come up at all - the minute I removed the ether-options they came up and appear to be ok. Is this normal? Also, I'm wondering how you verify what duplex the port is running at? Sorry for basic question but for the life of me I can't find this in the output or the docs...;) Paul ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Speed/Duplex Issue
On Tuesday 23 March 2010 08:50:01 pm Paul Stewart wrote: When I did the configuration I set the ether-options for 100/full ... most of the ports are facing Cisco switches. All the ports that were hard coded would not come up at all - the minute I removed the ether-options they came up and appear to be ok. Did you hard-code the speed/duplex setting on both the Juniper and Cisco switches, or just the Juniper's? We've been happy with auto-nego'ing all connections, including with upstreams. Life has been much easier going that route. I can't remember the last time anything good came out of hard-coding these settings, or when we last did that, for that matter. Is this normal? Also, I'm wondering how you verify what duplex the port is running at? Sorry for basic question but for the life of me I can't find this in the output or the docs...;) [edit] t...@lab# run show interfaces ge-0/1/3 | match Duplex Link-level type: Ethernet, MTU: 9014, Speed: 1000mbps, Duplex: Full-Duplex, MAC-REWRITE Error: None, Loopback: Disabled, Source filtering: Disabled, Flow control: Enabled [edit] t...@lab# The above is taken off an EX3200. Cheers, Mark. signature.asc Description: This is a digitally signed message part. ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
