[41234] in Resnet-Forum
Re: Port per pillow versus port per room
daemon@ATHENA.MIT.EDU (Ward, Sean)
Fri May 20 10:00:49 2016
X-Barracuda-Envelope-From: sward@bellarmine.edu
Content-Language: en-US
Content-Type: multipart/alternative; boundary="_000_295EC4BAD0B03844B532D5A6A340A47C27344A8DBUESFSbellarmin_"
MIME-Version: 1.0
Message-ID: <295EC4BAD0B03844B532D5A6A340A47C27344A8D@BUESFS.bellarmine.edu>
Date: Fri, 20 May 2016 14:00:39 +0000
Reply-To: Resnet Forum <RESNET-L@listserv.nd.edu>
From: "Ward, Sean" <sward@bellarmine.edu>
To: RESNET-L@listserv.nd.edu
In-Reply-To: <F3FC010FD4D5004B96A2286B495CEBB8858BBD5A@ad-oh-mbx03>
--_000_295EC4BAD0B03844B532D5A6A340A47C27344A8DBUESFSbellarmin_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
We had some buildings go up on campus that had one port per suite and tried=
to leverage the wireless, and that went over poorly. As that set of build=
ings went up, additional networking was added to each building, with more w=
ired ports being available in the last building compared to the other three=
.
Sure, some of the wireless issues were likely due to the wireless solution=
at the time and I believe would be less of a concern now that we have Ruck=
us in place, but I would not consider an all-wireless/no-wired option for a=
residence hall, as there's always a need for wired connections. In my exp=
erience, I've never seen a residence hall that had perfect wireless coverag=
e in all the rooms. I would at least lean towards one port per room, if no=
t two on opposite sides of the room; they could be run but not activated. =
If your IT department has no issue with mini-hubs/switches, then that works=
, but might be clunky nowadays.
We have this issue even in our office areas; we use to run one drop per roo=
m but found that the offices got re-arranged enough that we almost always n=
eeded additional ports elsewhere so we are in the habit of two separate dro=
ps per room with typically two ports each, just so we do not have to go bac=
k and try and run more. Not all of them are active, but we can get the use=
rs situated as they want pretty easily.
Sean
___________________________________________
Sean Ward, Manager, Technology Support Center
BELLARMINE UNIVERSITY
From: Resnet Forum [mailto:RESNET-L@LISTSERV.ND.EDU] On Behalf Of Norman My=
ers
Sent: Wednesday, May 18, 2016 18:50
To: RESNET-L@LISTSERV.ND.EDU
Subject: Port per pillow versus port per room
We are in the process of designing a new residence hall and of course costs=
are higher than the budget they put at a minimum to get the project approv=
ed. Now as they look to reduce cost they are trying to reduce port per pil=
low to port per room for hard wire. The main problem here is our wireless =
network (run by campus IT) does not support game consoles and smart TVs. O=
ur sign in requires username and password while most devices only use passw=
ord on the selected network. Looking for feedback on anyone using port per=
room, can it be done without mini switches, hubs etc? I'd especially like=
to hear anyone who talked a project manager out of trying port per room an=
d your arguments.
[University of Oregon]
Norm Myers, Computer Coordinator
University Housing, A Department in the Division of Student Life
University of Oregon
1595 E 15th Avenue, Eugene, OR 97403-1220
p: 541-346-5227
f: 541-346-4268
e: nmyers@uoregon.edu<mailto:nmyers@uoregon.edu>
w: housing.uoregon.edu<http://housing.uoregon.edu/?utm_source=3Dhousig&utm_=
medium=3Demail&utm_campaign=3Dhousig>
connect with us: [Facebook icon] <http://www.facebook.com/UOHousing> [Twitt=
er icon] <http://twitter.com/UOHousing>
NOTICE: This e-mail (including attachments) is covered by the Electronic Co=
mmunications Privacy Act, 18 U.S.C._2510-2521, is confidential and may be p=
rivileged. If you are not the intended recip ient, please be aware that any=
retention, dissemination, distribution, or copying of this communication i=
s prohibited. Please reply to the sender that you have received the message=
in error, and then delete it and any attachments from your system. Thank y=
ou for helping to maintain privacy.
_____________________
___________________________________________________ You are subscribed to t=
he ResNet-L mailing list.
To subscribe, unsubscribe or search the archives, go to http://LISTSERV.ND.=
EDU/archives/resnet-l.html ________________________________________________=
___
___________________________________________________
You are subscribed to the ResNet-L mailing list.
To subscribe, unsubscribe or search the archives,
go to http://LISTSERV.ND.EDU/archives/resnet-l.html
___________________________________________________
--_000_295EC4BAD0B03844B532D5A6A340A47C27344A8DBUESFSbellarmin_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Perpetua;
panose-1:2 2 5 2 6 4 1 2 3 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Perpetua",serif;
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal-compose;
font-family:"Perpetua",serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><a name=3D"_MailEndCompose"><span style=3D"font-fami=
ly:"Perpetua",serif;color:#1F497D">We had some buildings go up on=
campus that had one port per suite and tried to leverage the wireless, and=
that went over poorly. As that set of buildings
went up, additional networking was added to each building, with more wired=
ports being available in the last building compared to the other three.<o:=
p></o:p></span></a></p>
<p class=3D"MsoNormal"><span style=3D"mso-bookmark:_MailEndCompose"><span s=
tyle=3D"font-family:"Perpetua",serif;color:#1F497D"><o:p> </=
o:p></span></span></p>
<p class=3D"MsoNormal"><span style=3D"mso-bookmark:_MailEndCompose"><span s=
tyle=3D"font-family:"Perpetua",serif;color:#1F497D">Sure, s=
ome of the wireless issues were likely due to the wireless solution at the =
time and I believe would be less of a concern now that
we have Ruckus in place, but I would not consider an all-wireless/no-wired=
option for a residence hall, as there’s
<i>always</i> a need for wired connections. In my experience, I’=
;ve never seen a residence hall that had perfect wireless coverage in all t=
he rooms. I would at least lean towards one port per room, if not two=
on opposite sides of the room; they could be run
but not activated. If your IT department has no issue with mini-hubs=
/switches, then that works, but might be clunky nowadays.
<o:p></o:p></span></span></p>
<p class=3D"MsoNormal"><span style=3D"mso-bookmark:_MailEndCompose"><span s=
tyle=3D"font-family:"Perpetua",serif;color:#1F497D"><o:p> </=
o:p></span></span></p>
<p class=3D"MsoNormal"><span style=3D"mso-bookmark:_MailEndCompose"><span s=
tyle=3D"font-family:"Perpetua",serif;color:#1F497D">We have this =
issue even in our office areas; we use to run one drop per room but found t=
hat the offices got re-arranged enough that we almost
always needed additional ports elsewhere so we are in the habit of two sep=
arate drops per room with typically two ports each, just so we do not have =
to go back and try and run more. Not all of them are active, but we c=
an get the users situated as they want
pretty easily. <o:p></o:p></span></span></p>
<p class=3D"MsoNormal"><span style=3D"mso-bookmark:_MailEndCompose"><span s=
tyle=3D"font-family:"Perpetua",serif;color:#1F497D"><o:p> </=
o:p></span></span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"mso-bookmark:_MailEndCompose"><span s=
tyle=3D"font-family:"Perpetua",serif;color:#1F497D">Sean<o:p></o:=
p></span></span></p>
<p class=3D"MsoNormal"><span style=3D"mso-bookmark:_MailEndCompose"><span s=
tyle=3D"font-size:9.0pt;font-family:"Perpetua",serif;color:#1F497=
D"><o:p> </o:p></span></span></p>
<p class=3D"MsoNormal"><span style=3D"mso-bookmark:_MailEndCompose"><span s=
tyle=3D"font-size:9.0pt;font-family:"Perpetua",serif;color:#1F497=
D">___________________________________________
<o:p></o:p></span></span></p>
<p class=3D"MsoNormal"><span style=3D"mso-bookmark:_MailEndCompose"><b><spa=
n style=3D"font-size:9.0pt;font-family:"Perpetua",serif;color:#1F=
497D">Sean Ward</span></b></span><span style=3D"mso-bookmark:_MailEndCompos=
e"><span style=3D"font-size:9.0pt;font-family:"Perpetua",serif;co=
lor:#1F497D">,
Manager, Technology Support Center<o:p></o:p></span></span></p>
<p class=3D"MsoNormal"><span style=3D"mso-bookmark:_MailEndCompose"><span s=
tyle=3D"font-size:9.0pt;font-family:"Perpetua",serif;color:#1F497=
D">BELLARMINE UNIVERSITY<o:p></o:p></span></span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"mso-bookmark:_MailEndCompose"><span s=
tyle=3D"font-family:"Perpetua",serif;color:#1F497D"><o:p> </=
o:p></span></span></p>
<span style=3D"mso-bookmark:_MailEndCompose"></span>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:"=
;Calibri",sans-serif">From:</span></b><span style=3D"font-size:11.0pt;=
font-family:"Calibri",sans-serif"> Resnet Forum [mailto:RESNET-L@=
LISTSERV.ND.EDU]
<b>On Behalf Of </b>Norman Myers<br>
<b>Sent:</b> Wednesday, May 18, 2016 18:50<br>
<b>To:</b> RESNET-L@LISTSERV.ND.EDU<br>
<b>Subject:</b> Port per pillow versus port per room<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:14.0pt;font-family:"Ca=
libri",sans-serif">We are in the process of designing a new residence =
hall and of course costs are higher than the budget they put at a minimum t=
o get the project approved. Now as they look
to reduce cost they are trying to reduce port per pillow to port per room =
for hard wire. The main problem here is our wireless network (run by =
campus IT) does not support game consoles and smart TVs. Our sign in =
requires username and password while most
devices only use password on the selected network. Looking for feedb=
ack on anyone using port per room, can it be done without mini switches, hu=
bs etc? I’d especially like to hear anyone who talked a project=
manager out of trying port per room and your arguments.<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:14.0pt;font-family:"Ca=
libri",sans-serif"><o:p> </o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:"Calibri",sans-serif;color:#1=
F497D"><img width=3D"210" height=3D"40" id=3D"_x0000_i1025" src=3D"http://h=
ousing.uoregon.edu/images/icons/uosig.png" alt=3D"University of Oregon"><br=
>
<br>
Norm Myers, Computer Coordinator<br>
University Housing, A Department in the Division of Student Life<br>
University of Oregon<br>
1595 E 15th Avenue, Eugene, OR 97403-1220<br>
p: 541-346-5227<br>
f: 541-346-4268<br>
e: <a href=3D"mailto:nmyers@uoregon.edu">nmyers@uoregon.edu</a><br>
w: <a href=3D"http://housing.uoregon.edu/?utm_source=3Dhousig&utm_mediu=
m=3Demail&utm_campaign=3Dhousig">
housing.uoregon.edu</a><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto;vertical-align:middle">
<span style=3D"font-family:"Calibri",sans-serif;color:#1F497D">co=
nnect with us: </span>
<a href=3D"http://www.facebook.com/UOHousing" title=3D"Visit UOHousing on F=
acebook"><span style=3D"font-family:"Calibri",sans-serif;text-dec=
oration:none"><img border=3D"0" width=3D"24" height=3D"24" id=3D"_x0000_i10=
26" src=3D"http://housing.uoregon.edu/images/icons/facebook.png" alt=3D"Fac=
ebook icon"></span></a><a href=3D"http://twitter.com/UOHousing" title=3D"Vi=
sit UOHousing on Twitter"><span style=3D"font-family:"Calibri",sa=
ns-serif;text-decoration:none"><img border=3D"0" width=3D"24" height=3D"24"=
id=3D"_x0000_i1027" src=3D"http://housing.uoregon.edu/images/icons/twitter=
.png" alt=3D"Twitter icon"></span></a><span style=3D"font-family:"Cali=
bri",sans-serif;color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:"Calibri",sa=
ns-serif;color:#1F497D">NOTICE: This e-mail (including attachments) is cove=
red by the Electronic Communications Privacy Act,
18 U.S.C._2510-2521, is confidential and may be privileged. If you are not=
the intended recip ient, please be aware that any retention, dissemination=
, distribution, or copying of this communication is prohibited. Please repl=
y to the sender that you have received
the message in error, and then delete it and any attachments from your sys=
tem. Thank you for helping to maintain privacy.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:14.0pt;font-family:"Ca=
libri",sans-serif"><o:p> </o:p></span></p>
<p>_____________________ <o:p></o:p></p>
<p class=3D"MsoNormal">___________________________________________________ =
You are subscribed to the ResNet-L mailing list.
<o:p></o:p></p>
<p>To subscribe, unsubscribe or search the archives, go to <a href=3D"http:=
//LISTSERV.ND.EDU/archives/resnet-l.html" target=3D"_blank">
http://LISTSERV.ND.EDU/archives/resnet-l.html</a> _________________________=
__________________________
<o:p></o:p></p>
</div>
</body>
</html>
___________________________________________________
You are subscribed to the ResNet-L mailing list.
<p>
To subscribe, unsubscribe or search the archives,
go to <a href=3D"http://LISTSERV.ND.EDU/archives/resnet-l.html" target=3D"_blank">http://LISTSERV.ND.EDU/archives/resnet-l.html</a>
___________________________________________________
--_000_295EC4BAD0B03844B532D5A6A340A47C27344A8DBUESFSbellarmin_--
