OK, First off if this is a bad idea just say so and move on, I don't want to
start a giant flame war :) Also forgive me for this being a little long winded.
Working with a customer of mine who is actually doing a very nice switching
replacement. All switches are Cisco 3750X or Cisco 3560X and
source isn't one of them.
-Original Message-
From: cisco-nsp-boun...@puck.nether.net
[mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Blake Pfankuch
Sent: 27 July 2012 1:51 PM
To: cisco-nsp@puck.nether.net
Subject: [c-nsp] Point to Point T1's and vlan nightmares
OK, First off
.
-Original Message-
From: cisco-nsp-boun...@puck.nether.net
[mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Blake Pfankuch
Sent: 27 July 2012 1:51 PM
To: cisco-nsp@puck.nether.net
Subject: [c-nsp] Point to Point T1's and vlan nightmares
OK, First off if this is a bad idea just say so
Message-
From: cisco-nsp-boun...@puck.nether.net
[mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Blake Pfankuch
Sent: 27 July 2012 1:51 PM
To: cisco-nsp@puck.nether.net
Subject: [c-nsp] Point to Point T1's and vlan nightmares
OK, First off if this is a bad idea just say so
On 7/27/2012 5:38 PM, Oliver Garraux wrote:
Preventing duplicate VLAN numbers sounds like it could be better
solved through process changes rather than technical changes. Maybe a
wiki or a spreadsheet, or a single person that's in charge of
assigning new VLAN's.
(Not trying to be
: [c-nsp] Point to Point T1's and vlan nightmares
Preventing duplicate VLAN numbers sounds like it could be better solved
through process changes rather than technical changes. Maybe a wiki or a
spreadsheet, or a single person that's in charge of assigning new VLAN's.
(Not trying
