DYNES-Deployments

[Chris Griffin <>]

Hi Jorge,
        Your dynes vlan range for FIU is 700-719.

Tnx
Chris
-- 
Chris Griffin                           

Sr. Network Engineer - CCNP             Phone: (352) 273-1051
CNS - Network Services                  Fax:   (352) 392-9440
University of Florida/FLR               Gainesville, FL 32611



On Apr 24, 2013, at 6:00 PM, "Jorge L. Rodriguez" 
<>
 wrote:

> Hi Shawn
> 
> Thanks for the quick response. I am not sure what range of VLANs I allow 
> DYNES to use. As far as I know this was not something I had anything to do 
> with personally. VLAN 704 is not one I am familiar with and in fact wasn't 
> on any of my ports a couple of months ago. I do know that somethings were 
> changing with the switch configuration as of a few weeks back. For example, 
> the last time I logged into the FDT server I couldn't connect to the WAN 
> because something upstream had changed the 6248's configuration that I 
> manually set. I left it like that because James at FIU was working on 
> something. Just today I hopped back on the systems and low and behold 
> things were working again. Apparently whatever broke my connectivity 
> restored it. But as I mentioned now there is this VLAN 704 that I don't 
> think was there before... It would be nice to understand whats going on but 
> honestly I haven't sat down and read the DYNES documentation so it may be 
> something I should already know... Finals' are over now so I'll likely have 
> a little more time now.  
> 
> Regarding the new dual switch configuration. Since the 6248 switch only has 
> 4 ports and two of those are needed to bridge to the 8132 I am limited to 
> how I can configure things. If DYNES software isn't up on the 8132s yet we 
> could instead leave the 6249 in place and instead use two of the ports to 
> bridging, and the remaining two for the uplink and the public facing 
> interface on the FDT server. If DYNES doesn't need access to the private 
> (VLAN 1) on the FDT then this is probably best the easiest thing to do for 
> all of us. Later if it becomes necessary to extend DYNES circuits beyond 
> the one + one on the 6248 we can turn over the 8132 to DYNEs. I don't mind 
> either way. 
> 
> Jorge
> 
> 
> On 24-Apr-13 05:38 PM, Shawn McKee wrote:
>> Hi Jorge,
>> 
>> I'm not sure about VLAN 704.  What range of VLANs do you allow DYNES to 
>> use?
>> 
>> In your new configuration, DYNES needs a way to get any circuit created to 
>> the port the FDT box connects to.   The FDT agent will setup the 
>> appropriate connection from the FDT box end.  We need to make sure that 
>> either DYNES controls the 8132 or some configuration is put in place to 
>> guarantee the connectivity (on the right VLAN) and the bandwidth between 
>> the FDT server and the 6248.  
>> 
>> The easiest thing to do may be to put the 8132 under control of DYNES.  
>> However I am not sure we have any access to an 8132 to verify DYNES 
>> software can appropriately configure it.  I expect it would be pretty 
>> straightforward though, since we do support 8024 switches already.   If 
>> the 8132 were the "new" DYNES switch you could move the uplink over to it 
>> and then the 6248 wouldn't have to be involved in setting up DYNES 
>> circuits (unless you want to extend them there as well).
>> 
>> Maybe others on the list have comments or suggestions.
>> 
>> Thanks,
>> 
>> Shawn
>> 
>> On Wed, Apr 24, 2013 at 3:36 PM, Jorge L. Rodriguez 
>> <>
>>  wrote:
>> Guys,
>> 
>> I need some advise regarding the DYNES endsite here at FIU. We need to 
>> increase the number of 10 GbE ports on the site and am moving forward with 
>> a purchase of a new Dell 8132 switch. I plan to connect this guy up with 
>> the existing DYNES 6248 as described below. Since this will affect the 
>> topology I wanted to first verify with the group to see if there is 
>> something I need to consider before I pull the trigger on the purchase. 
>> The current and planned configuration is shown below for your 
>> consideration.
>> 
>> I also have a question regarding the VLAN configuration currently on the 
>> 6248. It seems that a new VLAN 704 has shown up that I don't remember 
>> being there before. Is this indeed something new or has it always been 
>> there?
>> 
>> The current and planned configuration are listed beloe
>> 
>> CURRENT with the single DYNES 6248:
>> 1. 6248: XG1 <---> FDT server on VLAN 1 (private)
>> 2. 6248: XG2 <---> FDT server on VLAN 503 (public)
>> 3. 6248: XG3 <---> No connection on VLAN 704
>> 4. 6248: XG4 <---> uplink to campus no VLAN defined
>> 
>> All ports are configured with in VLAN mode "Access" except the uplink to 
>> the WAN it is instead set to "Trunk"
>> 
>> ------------------------------------------------------------------------------------------------------
>> The new proposed configuration with the old DYNES 6248 and the proposed 
>> 8132.
>> 
>> 1. 6248: XG1 <---> 8132: XG1 one end of the TwinAx Direct Attached Cable
>> 2. 6248: XG2 <---> 8132: XG2 one end of the TwinAx Direct Attached Cable
>> 3. 6248: XG3 <---> No connection on VLAN 704
>> 4. 6248: XG4 <---> uplink to campus
>> 
>> 1. 8132: XG1 <---> FDT server on VLAN 1 (private)
>> 2. 8132: XG2 <---> FDT server on VLAN 503 (public)
>> 3. 8132: XG3 <---> 6248: XG1 the other end of the DAC
>> 4. 8132: XG4 <---> 6248: XG2 the other end of the DAC
>> 5. 8132: 1g1 <---> DGT server on VLAN 1 (private) over Cat6e @10Gb
>> 6. 8132: 1g2 <---> DGT server on VLAN 503 (public) over Cat6e @ 10Gb
>> 
>> Jorge
>> 
>