Thanks Chris for breaking it down. Makes sense.
On Wed, Aug 27, 2014 at 6:14 AM, Chris Marget ch...@marget.com wrote:
On Tue, Aug 26, 2014 at 7:32 PM, Lee Starnes lee.t.star...@gmail.com
wrote:
they are providing an access port for us.
This is un-tagged traffic at the remote site
if I
Thanks Mike.
Lot of great information. Thanks for taking the time to post this. Very
helpful.
-Lee
On Tue, Aug 26, 2014 at 10:56 PM, Mike Hale eyeronic.des...@gmail.com
wrote:
when the handoff is an access port
Because I don't think it's actually configured as an access port. The
behavior
when the handoff is an access port
Because I don't think it's actually configured as an access port. The
behavior of the interface mimics exactly what you had to configure on
yours...that is, a trunk port with a native VLAN defined.
If the configuration is what I think it is, the reason the
Hello,
Been fighting with a carrier about a problem that we are seeing that I have
not been able to get resolved. They are handing off an Metro-E circuit at
one of our remote sites and they are providing an access port for us.
This is un-tagged traffic at the remote site and tagged at our NNI. I
Thanks Mike.
That took care of the problem, but still not sure why I would have to set
the port up as a trunk port when the handoff is an access port. When the
carrier tested the port, they tested it as an access port and then tried to
test it as a trunk port and their test set failed when in
On 8/26/14 7:34 PM, Lee Starnes wrote:
Thanks Mike.
That took care of the problem, but still not sure why I would have to set
the port up as a trunk port when the handoff is an access port. When the
carrier tested the port, they tested it as an access port and then tried to
test it as a trunk
