RE: Strange 6500/IPX Issue!! HELP!! [7:47951]

2002-07-02 Thread Frank Merrill

Did you enable portfast or use the 'host' macro to set the user ports on
this switch?  I have seen this, but it was in a situation where the user
machines had there IPX frame type set to auto.  In that case the users
machine would boot up, try and autodetect the IPX frame type in use on the
segment, but since the interface wasn't forwarding yet, he wouldn't see any
IPX frames, and hence it would default to a frame type other than what was
actually being used on the network.
These machiones also had the classic DHCP problems for the same reason.
But, since you have hardcoded the IPX frame type, I'd suspect that maybe he
does his GNS, and if the port isn't forwarding, he just doesn't get a
response, and on a Windows95 machine, it will then go to a secondary login
(if there is one) or just go straight to the desktop.  If IP isn't a
problem, are they using static IP addresses?

Good Luck!



Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=47959&t=47951
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: Strange 6500/IPX Issue!! HELP!! [7:47951]

2002-07-02 Thread Michael Williams

Cisco Breaker wrote:
> Did you disable spanning tree or used portfast on the ports
> which are connected to clients.

Yes.  In my original post, I tried to be as informative as possible, there's
always something that gets left out.  Being a Novell shop (but not much
longer!) we put portfast on all ports going to servers/clients.

Here is the config of one of the ports on the 6509B that's having the issue:

interface FastEthernet6/4
 no ip address
 duplex half
 speed 10
 switchport
 switchport mode access
 spanning-tree portfase

I've toyed with speed/duplex, etc and nothing makes a difference...

However, I did find out something interesting.  While using the SPXping
utility, I found that I can *not* "ping" from the affected machine and get a
response, but if I use SPXping on another machine, I can indeed get a "ping"
response from the affected machine.

Strange. Thanks for your input!

Mike W.


Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=47960&t=47951
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



RE: Strange 6500/IPX Issue!! HELP!! [7:47951]

2002-07-02 Thread Michael Williams

The two PCs I'm experienting with are using hard-coded IPs, however the
results are the same with a DHCP machine.  Portfast is indeed enabled (A
while ago, I learned the hard way about spanning-tree and DHCP/Novell).

Well, and I find myself trying to get more into the Novell process to
understand where the breakdown could be happening.  I know when the PC
boots, it does a GNS and I also know routers will keep a GNS table and can
respond to the GNS requests, but in this case the PCs are in the same VLAN
with the Novell servers.  The Cisco TAC Engr said that if there are Type 4
servers in the subnet (or on that ethernet segment) that the router won't
respond to the GNS requests.

I connected a sniffer and when the PC boots you see 4 GNS requests go out
and never a single response.  Strange since it's in the same VLAN with 30+
Novell servers!!  Like I said tho, the strangest part is that if I connect
the PC to VLAN1 on 6509A (which would have to be L2 switched over 6509B
which would then L2 switch over to the 5513 where the Novell servers are
physically connected) it works like it should.

I've dug around on Novell's website, and found a document saying that not
only Spanning Tree, but also Trunk negotiation (which is 'auto' by default)
and PAgP (which is only active if you have the link set as a member of an
etherchannel, so it doesn't apply here) can all interfere with Novell's
login process.

Again, thanks for your comments, and keep 'em coming...

Mike W.


Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=47961&t=47951
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



RE: Strange 6500/IPX Issue!! HELP!! [7:47951]

2002-07-02 Thread Michael Williams

I found I was mis-typing a MAC address portion of the IPX address.  So, I
have a PC in VLAN1 that can't communicate with Novell, but it can send *and*
receive "pings" with the SPXping utility.

My bad.

Mike W.


Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=47963&t=47951
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: Strange 6500/IPX Issue!! HELP!! [7:47951]

2002-07-02 Thread Cisco Breaker

Did you disable spanning tree or used portfast on the ports which are
connected to clients. We have a customer that had the same issue and we
changed the client ports on the 6500's to portfast.
Here is the link.

http://www.cisco.com/warp/public/473/12.html

Best regards,

Cisco Breaker

""Michael Williams""  wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> Okay we have two 6509s with Sup2/MSFC2 running Native IOS 12.1(8b)E7,
> and a Cat5513 running CatOS 4.5(2) with RSM running IOS 11.3(3a)WA4(5).
We
> have 6509A connected via a Gig trunk (ISL) to 6509B and 6509B connects to
> the 5513 via a 4-link FastEtherchannel trunk (ISL).  Most of our Novell
> servers are connected to the 5513 and ALL Novell servers reside in VLAN1.
> All VLANs are trunked between all 3 switches.  The RSM in the 5500 handles
> all IPX routing for all VLANs and the two 6500s do no IPX routing.  IP
> Routing for the various VLANs are spread around the 6500s/5513 with HSRP.
> Our standard PC image has Win95 with Netware Client 3.2 (I believe)
> installed. IPX frame type under Windows is set to 802.3. Under normal
> circumstances, the PC boots, and comes up to the Novell login.
>
> Issue:
>
> * If the PC is connected to 6509B in any other VLAN except 1, you get a
> Novell login and IPX works fine.
>
> * If you connect a PC to 6509B in VLAN1, and boot, you get no Novell
login.
>   You can, from the RSM in the 5513, so an IPX ping with standard Novell
> Echos and it is successful.
>   But I also have a utility that runs in a DOS window under Windows called
> SPXping.  Using SPXping, I cannot ping to or from said PC.
>
> * If I move that PC to either 6509A or 5513, and reboot, it comes up fine
> and SPXping works fine. (remember that 6509A has to go through 6509B to
> reach the Novell servers on the 5513)
> * If the PC is connected to either 6509A or 5513, boots up and you login
to
> Novell, you can then move the connection to 6509B and it works fine until
> the PC is rebooted.
>
> * IP is not affected in any way no matter which switch the PC connects to
> (which seems to imply a L3 IPX issue, but 6509B isn't running any L3 IPX
and
> should, from an IPX perspective, act as a L2 switch only for PCs connected
> to it)
>
> Any input is appreciated!!  I about to tear my hair out over this (and
> so is the TAC engr)
>
> Thanks!
> Mike W.




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=47952&t=47951
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



RE: Strange 6500/IPX Issue!! HELP!! [7:47951]

2002-07-02 Thread Wes

Michael,

  Shot in the dark - I've seen very strange issues like this with trunk
mismatches.  You've probably got a trunk between the two switches.  Make
sure your native VLANs match, make sure that every VLAN permitted on the
trunk is permitted on both sides.  On a similar vein, all trunk ports should
have similar characteristics (I go with 100, full, desirable trunking,
desirable channeling; regardless, just make sure it's the same both sides)

  Also, if you've got links bundled, try bringing down one of the links for
a bit, then try the other(s).  Switches load balance via MACs, if you've got
a uni-directional link or something, packets from the same machine will
usually transit the same wire every time - physical port/cable problems
might appear to be associated with only certain machines because of this.

  Best guess for now.  Good luck!
  --Wes


Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=47964&t=47951
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: Strange 6500/IPX Issue!! HELP!! [7:47951]

2002-07-02 Thread Michael L. Williams

Wes,

Thanks for your reply.  As you can imagine I've been through the ringer so
far with this one =)

We checked all of the trunks for native VLAN, speed, duplex, etc...  All
checks out.  This is also supported by the fact that IP works fine (all IP
routing for VLAN1 is handled by the RSM in the 5513, which means anything
plugged into 6509A or 6509B that leaves the IP subnet must travel those
trunk links to hit the RSM and get routed.

One interesting note:  In an attempt to find out anything new, I took a Dell
desktop with integrated NIC, etc (my test machines and the machines having
the problem so far have been IBM 300PL with integrated NIC), and when the
Dell is connected to 6509B (the one with the "problem") it boots and gets
the Novell login, which automatically points to the hardware or the image on
that IBM.  However, that same IBM, when connected to 6509A works fine, which
kinda discounts that theory.

I'm going crazy here!!

Another interesting thing to note:  If I connect the PC (the IBM) to a 2900,
then connect the 2900 to 6509B, the client still doesn't receive the Novell
login.  However, if I connect the PC to a hub and connect the hub to 6509B
then the PC boots and gets the Novell login everytime.

I gotta be missing something..  I watched the 'sho mac int fas'
closely and upon booting the IBM's MAC address isn't seen by the switch for
12-15 seconds after you see "Starting Windows 95".  The MAC address on the
Dell becomes visible within about 3 seconds after "Starting Windows 95".
However I'm sure part of that can be attributed to the fact the IBM is a
200MHz -vs- 900MHz on the Dell (and the Dell I'm sure has newer faster
drives, etc)

But everytime I start to form a theory about something to do with the PC, my
co-worker goes "Yeah, but it works on the other 6509" and everytime I
form a theory that it could be something wrong with 6509B he goes, "Yeah,
but the Dell works on it".. I can't win!!!

Thanks again to all who have replied...

Mike W.

"Wes "  wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> Michael,
>
>   Shot in the dark - I've seen very strange issues like this with trunk
> mismatches.  You've probably got a trunk between the two switches.  Make
> sure your native VLANs match, make sure that every VLAN permitted on the
> trunk is permitted on both sides.  On a similar vein, all trunk ports
should
> have similar characteristics (I go with 100, full, desirable trunking,
> desirable channeling; regardless, just make sure it's the same both sides)
>
>   Also, if you've got links bundled, try bringing down one of the links
for
> a bit, then try the other(s).  Switches load balance via MACs, if you've
got
> a uni-directional link or something, packets from the same machine will
> usually transit the same wire every time - physical port/cable problems
> might appear to be associated with only certain machines because of this.
>
>   Best guess for now.  Good luck!
>   --Wes




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=47967&t=47951
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



RE: Strange 6500/IPX Issue!! HELP!! [7:47951]

2002-07-03 Thread Daniel Cotts

Seems as if all the bases have been covered. Is there any difference between
the cards on 6509A and 6509B? Does the 6509 support the "set port host"
macro? I believe that it sets spanning tree portfast enabled, trunking to
off and PAgP to off. According to Cisco LAN Switching page 314 "..when you
enable PAgP (Port Aggregation Protocol) on a link where Spanning Tree is
active, Spanning Tree takes about 18 more seconds to converge" I believe
that is also true if spanning tree is set to portfast.
I'd suggest comparing the configs of the two switches line by line. How is
your VTP domain configured?

> -Original Message-
> From: Michael L. Williams [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, July 02, 2002 5:33 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Strange 6500/IPX Issue!! HELP!! [7:47951]
> 
> 
> Wes,
> 
> Thanks for your reply.  As you can imagine I've been through 
> the ringer so
> far with this one =)
> 
> We checked all of the trunks for native VLAN, speed, duplex, 
> etc...  All
> checks out.  This is also supported by the fact that IP works 
> fine (all IP
> routing for VLAN1 is handled by the RSM in the 5513, which 
> means anything
> plugged into 6509A or 6509B that leaves the IP subnet must 
> travel those
> trunk links to hit the RSM and get routed.
> 
> One interesting note:  In an attempt to find out anything 
> new, I took a Dell
> desktop with integrated NIC, etc (my test machines and the 
> machines having
> the problem so far have been IBM 300PL with integrated NIC), 
> and when the
> Dell is connected to 6509B (the one with the "problem") it 
> boots and gets
> the Novell login, which automatically points to the hardware 
> or the image on
> that IBM.  However, that same IBM, when connected to 6509A 
> works fine, which
> kinda discounts that theory.
> 
> I'm going crazy here!!
> 
> Another interesting thing to note:  If I connect the PC (the 
> IBM) to a 2900,
> then connect the 2900 to 6509B, the client still doesn't 
> receive the Novell
> login.  However, if I connect the PC to a hub and connect the 
> hub to 6509B
> then the PC boots and gets the Novell login everytime.
> 
> I gotta be missing something..  I watched the 'sho mac int fas'
> closely and upon booting the IBM's MAC address isn't seen by 
> the switch for
> 12-15 seconds after you see "Starting Windows 95".  The MAC 
> address on the
> Dell becomes visible within about 3 seconds after "Starting 
> Windows 95".
> However I'm sure part of that can be attributed to the fact 
> the IBM is a
> 200MHz -vs- 900MHz on the Dell (and the Dell I'm sure has newer faster
> drives, etc)
> 
> But everytime I start to form a theory about something to do 
> with the PC, my
> co-worker goes "Yeah, but it works on the other 6509" and 
> everytime I
> form a theory that it could be something wrong with 6509B he 
> goes, "Yeah,
> but the Dell works on it".. I can't win!!!
> 
> Thanks again to all who have replied...
> 
> Mike W.
> 
> "Wes "  wrote in message
> [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> > Michael,
> >
> >   Shot in the dark - I've seen very strange issues like 
> this with trunk
> > mismatches.  You've probably got a trunk between the two 
> switches.  Make
> > sure your native VLANs match, make sure that every VLAN 
> permitted on the
> > trunk is permitted on both sides.  On a similar vein, all 
> trunk ports
> should
> > have similar characteristics (I go with 100, full, 
> desirable trunking,
> > desirable channeling; regardless, just make sure it's the 
> same both sides)
> >
> >   Also, if you've got links bundled, try bringing down one 
> of the links
> for
> > a bit, then try the other(s).  Switches load balance via 
> MACs, if you've
> got
> > a uni-directional link or something, packets from the same 
> machine will
> > usually transit the same wire every time - physical 
> port/cable problems
> > might appear to be associated with only certain machines 
> because of this.
> >
> >   Best guess for now.  Good luck!
> >   --Wes




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=47989&t=47951
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



RE: Strange 6500/IPX Issue!! HELP!! [7:47951]

2002-07-03 Thread Priscilla Oppenheimer

At 06:20 PM 7/2/02, Michael Williams wrote:
>The two PCs I'm experienting with are using hard-coded IPs, however the
>results are the same with a DHCP machine.  Portfast is indeed enabled (A
>while ago, I learned the hard way about spanning-tree and DHCP/Novell).
>
>Well, and I find myself trying to get more into the Novell process to
>understand where the breakdown could be happening.  I know when the PC
>boots, it does a GNS and I also know routers will keep a GNS table

Routers keep a Service Advertising Protocol (SAP) table. Does the 5513 show 
the servers in its SAP table? What does show ipx servers display? (That's 
how you look at the SAP table.)

>and can
>respond to the GNS requests, but in this case the PCs are in the same VLAN
>with the Novell servers.  The Cisco TAC Engr said that if there are Type 4
>servers in the subnet (or on that ethernet segment) that the router won't
>respond to the GNS requests.
>
>I connected a sniffer and when the PC boots you see 4 GNS requests go out
>and never a single response.

Can you put a Sniffer on the other side of the 5513 where the servers 
reside? Or is there some sort of troubleshooting that you can do on the 
server to determine if the GNS really made it to the server? It sure seems 
like the router is neither responding NOR forwarding the GNS to the servers!

Does the router know about the servers? (What does show ipx servers display?)

>  Strange since it's in the same VLAN with 30+
>Novell servers!!  Like I said tho, the strangest part is that if I connect
>the PC to VLAN1 on 6509A (which would have to be L2 switched over 6509B
>which would then L2 switch over to the 5513 where the Novell servers are
>physically connected) it works like it should.

Who responds? The router or one of the servers?

Are you absolutely sure that the PC on 6509B is connected to a port in 
VLAN1? Can you move it to a different port? It seems like it's on a messed 
up port.

But then again, you said the Dell works on that same port.


>I've dug around on Novell's website, and found a document saying that not
>only Spanning Tree, but also Trunk negotiation (which is 'auto' by default)
>and PAgP (which is only active if you have the link set as a member of an
>etherchannel, so it doesn't apply here) can all interfere with Novell's
>login process.

Yes, definitely turn all this off on the port that connects the PC. They 
make the port take a long time to start forwarding.

I can see why this is driving you nuts!

I think we can help more if you tell us more about the results of show 
commands on the 5513 and its IPX config.

Good luck. Please keep us posted. Thanks.

Priscilla


>Again, thanks for your comments, and keep 'em coming...
>
>Mike W.


Priscilla Oppenheimer
http://www.priscilla.com




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=48002&t=47951
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



RE: Strange 6500/IPX Issue!! HELP!! [7:47951]

2002-07-03 Thread Michael Williams

Priscilla,

Thanks for your input.  When I do a 'show ipx servers' it indeed shows the
gamut of 1500+ IPX entries (which is normal).

As far as putting a sniffer on the "other side" of the 5513 where the
servers reside, that was also a request by the TAC engr, but unfortunately,
the 5513 *is* the other side and most of the servers connect into VLAN1 on
that switch.  And, again unfortunately, we have a small number of servers
that hang off of the other 6509, so even if I sniff all of VLAN1 IPX traffic
on the 5513, there's a chance that the server that responds is hanging off
of VLAN1 on 6509A and my capture wouldn't see the response anyway (which
could be misleading to say the least).

As far as a possible bad port, we've tried many ports on every linecard and
get the same results (and even took some of those linecards and put them in
6509A and everything works fine, so we're moving away from the possibility
the linecard is the problem).

I did some more experimentation this morning.  I took a 2950 switch,
configured Fas0/1 for the PC, configured Fas0/48 and uplinked that port
(using a x-over of course =) into a port on 6509B (the one that shows the
problem).  I connected the PC to the 2950, booted, no Novell.  I then
disconnected the uplink (Fas0/48) then threw a GBIC into the 2950 and the
6509B (since 6509A works and connects to 6509B via a GBIC, I wanted to see
if using a GBIC into the 6509B from the 2950 would make a difference over
standard FastEthernet).  So I connected the fiber from the 2950 GBIC to the
6509 GBIC, rebooted the PC. nada. still nothing.  I yanked that very
same GBIC from 6509B and plugged into 6509A, rebooted the PC, and BAM! 
Novell!

The ONLY way I can get this PC to boot to Novell while connected to 6509B is
to connect to a hub, then connect the hub to a port on 6509B.  WTF?!?!?

And yes, the Dell works everytime whether plugged directly into a FastE port
on 6509B, 6509A, a hub or switch connected to either 6509A/B.

So again, it seems everything points to the IBM but IT WORKS ON 6509A!!  I'm
going to try to get some driver updates or something for the NIC on the IBM
just to see if that fixes it, but these IBM PCs are like P200 or
P2-233/266s, and running Win95 I seriously doubt there's been a driver
update for these integrated NICs for years.

Thanks again for all inputs!  Keep it coming!

I figure at this point, I've gotten myself and one co-worker, a TAC engr,
many very capable people (from groupstudy) and at least 4-5 CCIEs thinking
about this problem, and we STILL can't find a solution.

The workaround for now is just simply not to connect any Novell related
PCs/servers into that 6509 while we migrate to a Win2K platform and are all
IP at that point. Geez

Mike W.


Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=48015&t=47951
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



RE: Strange 6500/IPX Issue!! HELP!! [7:47951]

2002-07-03 Thread Peter Walker

Mike

Just a thought, but have you tried setting a gns-response-delay on your 
router.  From what I remember reading in my support exam study (I have NO 
ipx experience), this can be used to "compensate for the slow CPU or 
network adapter card of the client, which would otherwise miss a quicker 
response".

It just seems from your other emails that this may match your symptoms and 
perhaps the difference between connecting to switch a vs switch b is just a 
tiny bit of latency that is enough to allow the old machines / cards to get 
the response.

Like I said, I have no IPX experience and this is just a shot in the dark 
based on something I remember reading.

Regards

Peter




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=48030&t=47951
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



RE: Strange 6500/IPX Issue!! HELP!! [7:47951]

2002-07-03 Thread Kris Keen

6509 A
 |
 | 
 |
 |
6509B - > 5513  NOVELL SERVERS

So anything connected to 5513 can see the Novell Servers?
So anything connected to 6509B can see Novell Servers?

Can anything see the Novell Servers from the 6509A?

Where does the VLAN's come into this?
You say the 5513 has an RSM? I persume your novell servers are all in
different vlans??
Does your 6509A have full IPX Route/Sap Tables?
Does your 6509B have full IPX Route/Sap Tables?

Can you confirm IPX Routes are present on ALL switches? And therefore, SAPs?

Cheers


We use Novell 5 at work, along with 6509's in your same setup but your 5513
is our 3548, and we use Routing also but its done on the MSFC in the 6509




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=48065&t=47951
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: Strange 6500/IPX Issue!! HELP!! [7:47951]

2002-07-06 Thread Michael L. Williams

Your diagram is correct as far as connections go.  Most of the Novell
servers are connected to the 5513, but all are in VLAN 1.  The 5513 RSM does
all IPX routing for all VLANs.  All VLANs are trunked between all switches.
There aren't any IPX routes on either of the 6509s as IPX routing isn't
enabled on them.  As far as IPX is concerned, the 6509s are just L2
switches.

Mike W.

"Kris Keen"  wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> 6509 A
>  |
>  |
>  |
>  |
> 6509B - > 5513  NOVELL SERVERS
>
> So anything connected to 5513 can see the Novell Servers?
> So anything connected to 6509B can see Novell Servers?
>
> Can anything see the Novell Servers from the 6509A?
>
> Where does the VLAN's come into this?
> You say the 5513 has an RSM? I persume your novell servers are all in
> different vlans??
> Does your 6509A have full IPX Route/Sap Tables?
> Does your 6509B have full IPX Route/Sap Tables?
>
> Can you confirm IPX Routes are present on ALL switches? And therefore,
SAPs?
>
> Cheers
>
>
> We use Novell 5 at work, along with 6509's in your same setup but your
5513
> is our 3548, and we use Routing also but its done on the MSFC in the 6509




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=48252&t=47951
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]