CLEANACCESS Archives

August 2006

CLEANACCESS@LISTSERV.MIAMIOH.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Nagle, Benjamin D" <[log in to unmask]>
Reply To:
Perfigo SecureSmart and CleanMachines Discussion List <[log in to unmask]>
Date:
Fri, 18 Aug 2006 15:13:01 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (45 lines)
Changing the mananged subnets didn't work, but what it appears to have
been was that the spanning-tree priority on my dirty vlan was not set
properly.  After it was set to the correct priority everything started
working again.

Thanks for the reply though Alok!

Ben
 

> -----Original Message-----
> From: Perfigo SecureSmart and CleanMachines Discussion List 
> [mailto:[log in to unmask]] On Behalf Of Alok 
> Agrawal (alagrawa)
> Sent: Wednesday, August 16, 2006 10:30 AM
> To: [log in to unmask]
> Subject: Re: OOB VG problem
> 
> Hi Ben,
> >From your config below, it looks like vlans 71,83 are the clean vlans
> and vlans 171,183 is the untrusted/dirty vlans.
> 
> In your Managed subnet, we have the vlans configured as the 
> clean vlans.
> Managed subnet is for the vlans that exist on the dirty side, 
> hence delete the configured managed subnet and configure new 
> managed subnets with the vlan as vlan171 and vlan183 instead 
> and see if that helps. 
> 
> Currently configured MANGAGED SUBNETS:
> > 172.16.246.127/255.255.254.0 - Main Subnet (-1) 
> > 10.1.8.10/255.255.255.0 TEST 1 (Vlan 71) 
> 10.1.10.10/255.255.255.0 TEST 
> > 2 (VLAN 83)
> 
> Change this to
> 172.16.246.127/255.255.254.0 - Main Subnet (-1) 
> 10.1.8.10/255.255.255.0 TEST 1 (Vlan 171) 
> 10.1.10.10/255.255.255.0 TEST 2 (VLAN 183)
> 
> regards
> -Alok
> 
> 

ATOM RSS1 RSS2