====== Cisco vs. Juniper ====== ===== Command list ===== ^ Cisco Command ^ Juniper Command ^ Co-Ordinating Definition ^ | show ip interface brief | show interface terse | displays the status of interfaces configured for IP | | show interface [intfc] | show interfaces [intfc] detail | displays the interface configuration, status and statistics. | | show controller intfc | show interfaces intfc extensive | displays information about a physical port device | | show interface / incl (proto/Desc) |show interfaces description | displays the interface configuration, status and statistics| |show ip route |show route |displays summary information about entries in the routing table | |show ip bgp summary |show bgp summary | displays the status of all Border Gateway Protocol (BGP) connections | |show ip bgp net mask |show route protocol bgp prefix | will show you how that route is being advertised, look for the first line| |show ip bgp net mask longer-prefixes| show route range prefix|will show you how that route is being advertised, look for the first line| |show ip bgp regexp AS-regexp |show route aspath-regexp "AS-regexp" |displays routes matching the autonomous system (AS) path regular expression| |show ip bgp neighbors neigh received-routes|show route receive-protocol bgp neigh / show route source-gateway neigh protocol bgp |Shows whether a neighbor supports the route refresh capability| |show ip bgp neighbor neigh advertised-routes|show route advertising-protocol bgp neigh|Shows whether a neighbor supports the route refresh capabilty| |show clns neighbors|show isis adjacency|displays both ES and IS neighbors| |show clns interface|show isis interface|shows specific information about each interface| |show ip route isis|show isis routes|displays the current state of the the routing table| |show isis topology|show isis spf|displays a list of all connected routers in all areas| |show ip ospf interface|show ospf neighbor |shows neighbor ID, Priority, IP, & State if the neighbor router, dead time.| |show ip ospf interface|show ospf interface |shows neighbor id, pri, state, dead time, address and interface| |show ip route ospf |show ospf route |display the current state of the routing table| |show ip ospf database |show ospf database |display list of information related to the OSPF database for a specific communication server| |show version |show version, show system uptime |display the system hardware config., software version, and name and source of configuration files and boot images| |show diags |show chasis hardware |displays power-on diagnostics status| |show processes cpu |show system process |displays utilization statistics| |show tech-support |request support info |displays the current software image, configuration, controllers, counters, stacks, interfaces, memory and buffers| |show logging |show log messages |display the state of logging to the syslog| |show route-map name |show policy name |displayall route-maps configured or only the one specified| |show ip prefix-list name |show policy name |display information about a prefix list or prefix list entries| |show ip community-list list |configure, show policy-options community name |display routes that are permitted by BGP community list| |show environment all |show chassis environment |displays temperature and voltage information on the console| |ping dest |ping dest rapid (for cisco like output) / ping dest (for unix like output) |to check to see if a destination is alive| |ping (setting source int) |ping dest bypass-routing |to check to see if a destination is alive| |terminal monitor |monitor start messages |Change console terminal settings| |terminal no monitor |monitor stop |Change console terminal settings| |terminal length 0 |set cli screen-length 0 |sets the length for displaying command output| ===== OSPF ===== Some subtle differences Because OSPF has several checks and balances in regards to neighbor adjacencies, and because those adjacencies are essential for actual routing, their defaults remain the same between the two vendors. These include authentication (except in the case of OSPFv3), hello/dead intervals and area types. One note about authentication: in Cisco IOS when area authentication (either MD5 or Simple) is configured at the protocol level it triggers the bit in the AuType field within the header. This means that without a like configuration on neighboring routers, adjacencies will not be created. Juniper does not, at the protocol level, trigger the AuType bit unless the key is configured within the interface. In the examples below, both configurations will change the AuType to 2 which would satisfy one of the adjacency requirements. Of course if we were trying to get these two to "neighbor-up" it wouldn't work. **Cisco Example** router ospf 1 area 0.0.0.0 authentication message-digest end **Juniper Example** protocols ospf { area 0.0.0.0 { authentication-type md5; interface ge1/0/1.0{ authentication { md5 1 key juniper; } } } } Another difference lies within the functions of stub ABRs. This is a classic difference between routers made for enterprise operations and routers made for the provider industry. In Cisco IOS a stub router which is configured to either allow summary route or inject just one summary (totally stubby) will do just that. In Juniper land, that particular function is optional and must be configured using the "default-metric" command. On broadcast/multi-access media such as Ethernet, OSPF elects a Designated Router (DR) to act as the originator of network advertisements and synchronizing of link-state databases. The election process involves the comparison of OSPF priority values and Router-IDs. On a data link the highest priority wins the election. Each vendor has a default priority and each vendor recognizes that a priority of 0 does not allow that interface to be considered in an election. Cisco has a default priority of 1 and Juniper has a default of 128. This means of course, that if you put Cisco and Juniper on the same broadcast segment, Juniper will by default become the designated router.