do you know about cisco switch 2950 with osi (13)?
610298
Try\nhttp://www.cisco.com/en/US/products/hw/switches/ps628/prod_release_note09186a0080161e73.html\n\nGood Luck
858124
http://www.cisco.com/en/US/products/hw/routers/ps133/tsd_products_support_series_home.html\nCisco tends to make all the information on a router available for free.  \n\nThe company that sold it to you also wants to keep the relationship open, so you'll buy through them again.  Your rep probably assumes you'll call some for advice on using the unit, because you bought it through them.
891439
you can log on to the rtr using hyperterm and then press ctrl + b to enter rommon mode change the boot mode to 0X2142, reload the rtr.\nenter priv mode copy startup to running config\nchange the pswd\nreset the config register to normal 0x2102\nsave running config to startup\nreload\nand u r done with password reset\nthen if u wish, u may erase the flash.\n\nCommands\nctrl + b\nconfig-register 0x2142\nreload\nena\ncopy start run\nena pas cisco\ncopy run start\nconfig-register 0x2102\nreload\n\nCheers !!
819827
It seems the SBV5220 User Guide is not yet availalble.  I would refer to the next closest product, the SB5101.  It's a cable modem, but not a voice gateway.\n\nOtherwise you can review the SBV5220 Data Sheet.\n\nAnother resource could be the SBV4200 Advanced Voice Gateway
317851
TCP/IP is more efficient and will be faster than IPX/SPX/NetBIOS, but that might not be what you should be looking at first.\n\nDo you have the dual ports configured as a team, and if so, what type of team?  Are you using a switch or a hub between the two servers and how is that configured?  What are the speeds you are getting? \n\nYou want to use link aggregation so the two ports act as one big port.  You best option is 802.3ad dynamic trunking, which your cards support.  The key is that your switch has to support this as well and it needs to be appropriately configured.
716408
u can visit www.Cisco.com
163294
try in the cisco.com web site.\nin the search textbox simply write SNMP...you will find all the specifications about how it works, and how is it used in networks today.
106744
http://www.cisco.com/en/US/customer/products/hw/routers/ps221/prod_configuration_guide09186a008007cfa7.html
807535
http://www.cisco.com/univercd/cc/td/doc/cisintwk/ito_doc/introwan.htm
160600
Keeping it short...\n\nView this PDF:\nhttp://www.itl.nist.gov/div892/pubs/broadnets_wsan.pdf
759091
------/:=====:x:=====:&#92;-----@-------\nL     2Wy                Int             2Wy           Load          N\n\n(Does this answer your question??)\n\nL=Live, 2Wy is a 2 way light switch, int is an intermediate switch, and @ is a light??\n\nConfused?? (never heard of tunnel switching!!?)
497379
One can only functionally position the internet model to the ISO OSI model because basic differences exist such as: \n\nIn the internet protocol suite, a layer represents a reasonable packaging of function. \nThe ISO view, on the other hand, treats layers as rather narrow functional groups, attempting to force modularity by requiring additional layers for additional functions. \n\nIn the TCP/IP protocols, a given protocol can be used by other protocols within the same layer, whereas in the OSI model two separate layers would be defined in such circumstances. Examples of such "horizontal dependencies" are FTP, which uses the same common representation as TELNET on the "application layer," and ICMP, which uses IP for sending its datagrams on the "internetwork" layer. \n\nIn practice, what we are discussing here is the difference between a de jure standard, OSI, and a de facto standard, TCP/IP. The focus in the TCP/IP world is on agreeing on a protocol standard which can be made to work in diverse heterogeneous networks. The focus in the OSI world has always been more on the standard than the implementation of the standard. \n\nEfficiency and feasibility. The OSI norms tend to be prescriptive (for instance the "layer N" must go through "all layers below it"), whereas the TCP/IP protocols are descriptive, and leave a maximum of freedom for the implementers. One of the advantages of the TCP/IP approach is that each particular implementation can use operating system-dependent features, generally resulting in a greater efficiency (fewer CPU cycles, more throughput for similar functions), while still ensuring "interoperability" with other implementations. \nAnother way to see this is that most of the internet protocols have first been developed (coded and tested), before being "described" in an RFC (usually by the implementer) which clearly shows the feasibility of the protocols. \n\n2.14.2 The Internet World and OSI \nThe Department of Defense (DoD), funder of the original ARPANET research, made a statement on OSI in January '88, based on the Government OSI Profile (GOSIP) of April 22, 1987. \n\nThe following is an excerpt from the statement, which is published in RFC 1039 - A DoD Statement on OSI: "... It is intended to adopt the OSI protocols as a full co-standard with the DoD protocols when GOSIP is formally approved as a Federal Information Processing Standard. Two years thereafter, the OSI protocols would become the sole mandatory interoperable protocol suite; however, a capability for interoperation with DoD protocols would be provided for the expected life of systems supporting the DoD protocols. ..." \n\nA lot of study has already been done by the internet world on possible transitions and coexistence of the protocols. The following list is a series of RFCs already issued for that purpose: \n\nRFC 983 - ISO Transport Services on Top of the TCP. \nRFC 1006 - ISO Transport Services on Top of the TCP - Version 3. \nRFC 1039 - A DoD Statement on Open Systems Interconnection Protocols. \nRFC 1069 - Guidelines for the Use of Internet IP Addresses in the ISO Connectionless-Mode Network Protocol. \nRFC 1085 - ISO Presentation Services on Top of the TCP/IP-based Internets. \nRFC 1086 - ISO-TP0 Bridge between TCP and X.25. \nRFC 1090 - SMTP on X.25. \nRFC 1161 - SNMP over OSI. \nRFC 1195 - Use of OSI IS-IS for Routing in TCP/IP and Dual Environments. \nRFC 1238 - CLNS MIB for Use with Connectionless Network Protocol (ISO 8473) and End System to Intermediate System (ISO 9542). \nRFC 1240 - OSI Connectionless Transport Services on top of UDP: Version 1. \nRFC 1308 - Executive Introduction to Directory Services using the X.500 Protocol. \nRFC 1309 - Technical Overview of Directory Services using the X.500 Protocol. \nRFC 1327 - Mapping between X.400 (1988)/ISO 10021 and RFC 822. \nRFC 1328 - X.400 1988 to 1984 Downgrading. \nRFC 1330 - ESCC X.500/X.400 Tas
851605
Hi Jon,\nWhile you're free to surf eBay for older 1700 series routers for example, what you'll want is an 800 series Cisco router.  This is Cisco's newer ISR (Integrated Services Router) that is not only your best bet for a home use broadband access router, but will give you the VPN functionality you need, and you have wireless options as well.  Check out the 851 for currently $399 list price or the 851W for $499 which has dual ethernet and wireless as well.  Both models have a 4-port 10/100 switch and an SPI firewall and IPsec VPN.  You also have 871 and 871W options for a little more.  Check out the link below to compare models based on your needs, this also has links to all the data sheets.  Also, to find a Cisco partner/reseller to buy one in your area, go here: http://tools.cisco.com/WWChannels/LOCATR/jsp/partner_locator.jsp
117712
I am trying to get the answer to the same question. I guess you're in com 110 too. I am stumped on it.
162652
The following varieties of SCSI are currently implemented: \n\nSCSI-1: Uses an 8-bit bus, and supports data rates of 4 MBps \nSCSI-2: Same as SCSI-1, but uses a 50-pin connector instead of a 25-pin connector, and supports multiple devices. This is what most people mean when they refer to plain SCSI. \nWide SCSI: Uses a wider cable (168 cable lines to 68 pins) to support 16-bit transfers. \nFast SCSI: Uses an 8-bit bus, but doubles the clock rate to support data rates of 10 MBps. \nFast Wide SCSI: Uses a 16-bit bus and supports data rates of 20 MBps. \nUltra SCSI: Uses an 8-bit bus, and supports data rates of 20 MBps. \nSCSI-3: Uses a 16-bit bus and supports data rates of 40 MBps. Also called Ultra Wide SCSI. \nUltra2 SCSI: Uses an 8-bit bus and supports data rates of 40 MBps. \nWide Ultra2 SCSI: Uses a 16-bit bus and supports data rates of 80 MBps.
736426
read here \n\nhttp://articles.networktechs.com/58-p1.php\n\ngood luck
431740
depends on the router model/series, memory, etc.\ncheck cisco.com