Cisco Switches?

Skilldibop said:
Companies use cisco because they are the most refined and well balanced on the market. The IOS is standardised so everyone knows how to use it.
They never break/stop. I've seen 2600s with uptime well in excess of 1000 days.
Where other companies produce the odd outstanding product, Cisco have entire series' that are tried and tested to be absolutely bullet proof.
The biggest selling point is the scalability of their products.
They also developed things like RIP and RIPv2 which are cisco propriatory dynamic routing protocols which can be used in addition to industry standards.
They just go one better than anyone else and so if it's mission critical it'll be Cisco.


Since when was RIP a cisco propriatory protocol ?

http://www.ietf.org/rfc/rfc1058.txt

EIGRP yes, RIP no.
 
I don't agree with some of that statement. I deploy Cisco kit all the time and have always got at least one TAC case open for an RMA at any one time.
Constant trouble would indicate YOU are doing something wrong.

Since when was RIP a cisco propriatory protocol ?

http://www.ietf.org/rfc/rfc1058.txt

EIGRP yes, RIP no.

If your knowledge is as integral as that document....
A document in which a passage states that RIP responds to infastructure changes. This is a characteristic of a link state routing protocol, which RIP is not, RIP sends out updates at fixed time intervals whatever happens. This can lead to false information being propigated in large networks and is why you use EIGRP or single area OSPF in such scenarios. That's lesson one on Link state routing in CCNA.

After research "Open standard RIP" (developed from several variants incuding Cisco propriatory RIP) came about in 1996. RIP had been about in proriatory forms LONG before then.
 
Last edited:
Skilldibop said:
Constant trouble would indicate YOU are doing something wrong.

If it was me physically deploying the kit I would agree but I have a team of field engineers accross Europe who actually plug the kit in, I just monitor it remotely and do the test and turnup.

When you take into account the amount of kit we have it's not surprising really. I am talking Tier1 carrier here not an office LAN or anything.
 
Skilldibop said:
Constant trouble would indicate YOU are doing something wrong.



If your knowledge is as integral as that document....
A document in which a passage states that RIP responds to infastructure changes. This is a characteristic of a link state routing protocol, which RIP is not, RIP sends out updates at fixed time intervals whatever happens. This can lead to false information being propigated in large networks and is why you use EIGRP or single area OSPF in such scenarios. That's lesson one on Link state routing in CCNA.

After research "Open standard RIP" (developed from several variants incuding Cisco propriatory RIP) came about in 1996. RIP had been about in proriatory forms LONG before then.


RIP is not a Cisco propriatory protocol, it was produced in the 80s by "A Gang of 5" namely Cisco, Xerox DECnet, Intel and someone else..
Cisco has had input into all major routing protocols but they are still ietf, with the exception of EIGRP which is Cisco propriatory but also licensed to Juniper.

Cisco have always had it nailed down with routers, i've worked on everything from little 800s all the way up to the GSR12000s and the platform is solid reliable and secure. I wouldn't say the same for their switches, which are overpriced and not as higher performing as a Foundry Big iron or something else.. HP procurves are also a lot better value for money,, but then again if you work in a big Cisco house like me, its always easier to have an across the board vendor for support and knowledge.
 
pdw8 said:
I am talking Tier1 carrier here not an office LAN or anything.

Agreed TAC cases and RMA's are the norm on Cisco or any other networking kit when you get into this arena, been there, done that and still have many of the T-shirts ;)

HEADRAT
 
Back
Top Bottom