SYNTAX HELPER
The CLI has a built-in syntax helper. If you are unsure of the complete syntax for a particular command, enter as much of the command as possible and press [Return]. The syntax helper provides a list of options for the remainder of the command. The syntax helper also provides assistance if you have entered an incorrect command.
COMMAND COMPLETION WITH SYNTAX HELPER
ExtremeWare provides command completion by way of the [Tab] key. If you enter a partial command, pressing the [Tab] key posts a list of available options, and places the cursor at the end of the command.
ABBREVIATED SYNTAX
Abbreviated syntax is the most unambiguous, shortest allowable abbreviation of a command or parameter. Typically, this is the first three letters of the command.
When using abbreviated syntax, you must enter enough characters to make the command unambiguous and distinguishable to the switch.
COMMAND SHORTCUTS
All named components of the switch configuration must have a unique name.
Components are named using the create command. When you enter a command to configure a named component, you do not need to use the whole keyword of the component. For example, to create a VLAN, you must enter a unique VLAN name:
create vlan engineering
Once you have created the VLAN with a unique name, you can then eliminate the keyword vlan from all other commands that require the name to be entered. For example, instead of entering the switch command
config vlan engineering delete port 1:3,4:6
you could enter the following shortcut:
config engineering delete port 1:3,4:6
Similarly, on the Summit switch, instead of entering the command
config vlan engineering delete port 1-3,6
you could enter the following shortcut:
config engineering delete port 1-3,6
SUMMIT SWITCH NUMERICAL RANGES
Commands that require you to enter one or more port numbers on a Summit switch use the parameter
port 1-3
You can add additional port numbers to the list, separated by a comma:
port 1-3,6,8
NAMES
All named components of the switch configuration must have a unique name. Names must begin with an alphabetical character and are delimited by white space, unless enclosed in quotation marks.
Basics of the Web Browser interface
Each switch has a built in HTTP server that drives the web based GUI interface. To access the GUI interface simply open a web browser and point to the IP Address of the switch. Now the switch has an easy point and click means of configuration.
Things to do with ports on an Extreme switch
Resetting Back to Factory Configs.
To reset the switch back to factory configs, and keep the user account informantion type the command:
Unconf switch
To rest the switch back to factory configs and remove the users account information type the command:
Unconf switch all
Mirroring Ports
Port mirroring configures to the switch to copy all traffic associated with one or more ports. The monitor port can then be connected to a Sniffer or RMON probe for analysis. The traffic filter can be defined based on one of the following criteria:
Physical port – All data that traverses that port, regardless of the VLAN, is copied to the mirror port
VLAN – All data that traverses the VLAN, regardless of the physical port, is copied to the mirror port.
Virtual Post – All data specific to a VLAN on a specific port is copied to the mirror port.
Note: The port you configure to be the mirror port must be active prior to enabling it for mirroring.
The following example selects port 3 as the mirror port and sends all traffic coming into out of port 1 to the mirror port
enable mirroring to port 3
config mirroring add port 1
The following example sends all traffic for the Default VLAN to the mirror port
config mirroring add vlan default
The following example sends all traffic coming into and out of port 1 and the Default VLAN to the mirror port.
config mirroring add port 1 vlan default
To disable mirroring:
Disable mirroring
Naming Ports
You can name switch ports in order to keep track of what is plugged in to them, or for personal records.
To name a port type the command:
Config port
To reset port name type:
unconfig port
Setting Speed and Duplex on a port
To set a port for 100Meg full duplex type the command:
Config port
To set a port for 10Meg Half duplex type the command:
Config port
To reset the port able to auto negotiation type the command:
Config port
Looking at Port Errors
Note: If you want to look at all ports, simply leave out the port number and the switch will display all ports. Also you can specify port groups. (i.e. port 1-19, 20,34,46, etc)
Show port
Show port
Show port
Show port
Show port
Show port
Show port
Show port
Configuring VLANS on an Extreme Switch
With all switches from Extreme Networks there is no need to create a “router interface” in order to use VLANS. Since every port can be a router and the routing mechanism is built into the switch fabric, VLAN configuration has become incredibly easy. When the switch is first started up our of the box, there is a single VLAN called “Default” (VLAN 1) and contains all ports on the switch. If you desire to add ports to other VLANS, you must first delete the port out of the VLAN they are in. (for security purposes).
VLAN Basics
Creating a VLAN
Type the command:
Create vlan
Giving the VLAN an IP Address
Type the command:
Config vlan
Adding ports to that VLAN
Type the command:
Config vlan
Deleting ports out of a VLAN
Type the command:
Config vlan
Assigning tags and designating Trunk (uplink) ports
Be default when you add ports to a VLAN, they are added untagged. Most user ports will be untagged. The reason for adding tags to ports is to allow multiple VLAN traffic to traverse those ports, as with trunk ports. Trunk ports (or Uplinks) can contain several thousand VLANS on a single link. This is useful if you have more than one VLAN at an edge switch. In order to have more than one VLAN on a uplink you will need to add an 802.1q tag to port. Please be aware that Cisco’s VLAN numbers should be the same as a standard 802.1q tag number. (I.e. if you want to trunk a Cisco switch using Vlan500 and Vlan600 to another standards based switch, the VLAN tags should match up. Tag 500 and Tag 600 should be on that trunk)
Adding a 802.1q tag to a VLAN
Type the command:
Config vlan
Making a port a “trunk” port
Type the command:
Config vlan
How to load share ports (aka Fast Etherchannel)
To define a load sharing group, you assign a group of ports to a single logical port number.
To enable or disable loadsharing use the following commands.
Enable sharing
To disable sharing:
Disable sharing
For example
Enable sharing 2 grouping 2-8
Routing on an Extreme Networks switch
Every switch from Extreme is a layer 3 switch. To enable routing, obviously you need more than 1 VLAN with an IP address on the switch. Once you have your desired number of VLANS created, with their own unique IP address, you issue a single command to enable routing.
How to turn on routing
Type the command:
Enable ipforwarding
Note: you can also turn on or off routing for any single vlan on the switch.
(i.e. enable ipforwarding vlan
You are now routing between VLANS.
Routing Protocols (getting routing to work with other switches)
All Extreme Networks switches support static routes, Rip v1/v2, OSPF, BGP and IS-IS. Just like any router you must use a routing protocol in order for routers/switches to share routing information.
Turning on OSPF
Type the command:
config ospf add vlan
This adds each VLAN to the OSPF Area 0
You can also add all the VLANS by typing the command:
Config ospf add vlan all area 0.0.0.0
Now you enable OSPF by typing:
Enable OSPF
You now have OSPF running on your switch.
The following is a sample configuration:
create vlan HQ_10_0_2
create vlan HQ_10_0_3
create vlan LA_161_48_2
create vlan Chi_160_26_26
config vlan HQ_10_0_2 ipaddress 10.0.2.1 255.255.255.0
config vlan HQ_10_0_3 ipaddress 10.0.3.1 255.255.255.0
config vlan LA_161_48_26 ipaddress 161.48.2.26 255.255.255.0
config vlan Chi_160_26_26 ipaddress 160.26.2.1 255.255.255.0
create ospf area 0.0.0.5
create ospf area 0.0.0.6
enable ipforwarding
config ospf area 0.0.0.6 stub nosummary stub-default-cost 10
config ospf add vlan LA_161_48_2 area 0.0.0.6
config ospf add vlan Chi_160_26_26 area 0.0.0.5
config ospf add virtual-link 160.26.25.1 0.0.0.5
config ospf add vlan all
enable ospf
Thursday, November 15, 2007
Basic’s of the CLI
This paper will address the following issues:
What is Frame Relay?
How does Frame Relay differ from other techniques?
What is Frame Relay useful for?
How does frame relay fit in the U.S. Internet strategy?
Mixing Frame Relay with other technologies
Pros and Cons of Frame Relay
Technical aspects of installing and running frame
Items one through six will address general overviews of frame; item 7 will be a technical discussion related to equipment installation and setup that is probably only interesting for the technical staff involved in this area.
1. What is Frame Relay?
Frame relay is a technique used to transport data from locations to location, just like T-1 lines or ISDN connections do. In frame relay, there are a number of locations on the network that can send and receive data. These connections are known as Ports. Each location that needs access to the frame system, needs to have one of these ports.
Every port in a Frame Relay system has an Address. This address is Unique to the port at that specific location. The port is connected to the equipment that handles the Data on one side, to the Frame Relay Cloud on the other side.
The equipment that handles the data can send data out the frame relay port. This happens in the form of Packets, or Frames. Each frame is built up of two parts; the actual Data and the Control block. These frames are sent over Virtual Connections.
The frame network itself should be imagined as a cloud. Every Frame Relay Access Port runs into this Cloud. Inside the cloud, there are a lot of different ways to get from one port to another. These ways are all interconnected by Frame Switches. These switches can make informed decisions on the traffic flow over each part of each route. Together, they figure out what router to send a packet over to get it fast and reliable from the source to the destination port.
Let's for example say that we have two sites connected to a frame relay network, and we wish to send data from site A to site B. The diagram would look like this:
What happens INSIDE the Frame Cloud is not known, and does not matter to us. What we do is simply address data as Going to B or Going to A. So, at this point, things work pretty much the same as they would on a dedicated line between A and B. When we add a Location C, things get more interesting:
Now, the three sites can simply talk to each other by passing packets with the correct addresses. In a conventional setup with leased or dialup lines, this would have meant that either each site would have to have two lines, or that traffic would have to pass through two sites. Not in frame relay, the cloud takes care of all of this!
What the cloud does for us, is form 'Virtual Connections'. The way this is done, is simple. Each connection from one site to another is defined. For example, we say there is a connection from site A to site B. From site A to site C, etc. Each end of each connection is given a number that identifies it, this is called a Data link Connection Identifier, or DCLI. For everyone in the above diagram to be able to talk to everyone directly, these are the virtual connections that would be needed:
This means that everyone can talk to each other by simply stating the address and DLCI number of the line they want to talk over. This will get the data across the Virtual Connection.
Now keep in mind that all the data for all virtual connections arrives over one line, in one port! This means that the Equipment itself takes care of picking the data apart and putting the correct packets in the correct directions. these virtual connections come in two flavors, being Fixed and On Demand.
The fixed variety is referred to as a Private Virtual Circuit, or PVC. A PVC is setup by the carrier that carries the frame-data from A to B. Simply addressing the data with a port address and DLCI will get it over the Frame Cloud to the right port.
the On Demand variety is called a Switched Virtual Circuit or SVC. This type of circuit is brought up when needed, just like making a phonecall. If A wants to setup an SVC to B, it will send a control packet in LAPD format, which will bring up a SVC. Both sides will be assigned a temporary DLCI, and they are now ready to talk.
The multiple DCLI's coming into or going out of one location are all handled, as said before by one port into the frame network. This port comes in over a traditional form of media, it can be dialup, ISDN to T-1 or higher bandwidth. Let's say for example that all ports in our network have a 512 Kilobit bandwidth. If A and B start sending data to C at the same time, the total combined bandwidth will be 512+512 = 1024Kilobits. Since C only has a 512 Kbit port, we have a problem! Frame Relay uses a technique called Statistical Multiplexing to fix this; each of the two gets a fair share of the bandwidth. The rest of the data is temporarily buffered in the Frame Relay Cloud. It will be sent as soon as possible, when the dataflow lets off a little.
The risk in this is of course that the dataflow may not let off; if the buffers fill up and there is nowhere to go, the frame relay cloud will drop the data. In our uses, this is no problem, since the protocols running over frame will re-send the data anyway. It is however something to consider, since it may cause slowdowns in the network.
2. How does Frame Relay differ from other Techniques?
The biggest difference in frame Relay from other techniques is the use of Virtual Connections rather than Static Connections. As shown before, each location can have one port into a Frame Relay Network. From this port, it can have multiple Virtual Connections to various locations. It can make multiple redundant connections possible through the use of PVC's between various routers, without having to use multiple physical links.
Also, since Frame relay is not media specific, and offers a way to buffer speed differences, it can make a good interconnect medium between various devices that run at various speeds.
The multiplexed nature of Frame Relay facilitates especially the transmission of Bursty Traffic. In a traditional fixed-bandwidth multiple connection scenario, a lot of bandwidth will be wasted at most times, since it is not actually being used. The bandwidth on frame is shared, allowing for multiple bursts to be handled sequentially, therefor allowing better utilization of bandwidth. The chance of congestion is however also greater, since the bandwidth in the Frame Relay Port may become a bottleneck.
frame Relay pricing is where things really get different: From the above discussion we know there are two elements to Frame Relay, the Access Port and the Private Virtual Circuits. Per port, we can feed as many circuits as we please (up to the equipment's limit..). The price of the port depends on it's bandwidth. A bigger port costs more money. The price of a PVC is fixed, and not dependent on bandwidth or usage. Data sent over the Frame Connection is not subject to additional charges. The interesting part about this pricing is that there is NO DISTANCE CHARGE involved! A Frame Relay Access Port is expensive. Two frame ports between two cities are usually also more expensive than a direct T-1 as long as there is only a one or two LATA Hop, say for example Knoxville to Nashville. However, when you feed multiple cities and Hop multiple Lata's, a Frame solution is an attractive one. In local traffic, Frame becomes attractive when you feed a large number of connections, at Fractional T-1 bandwidth generally 8 or more.
3. What is frame relay useful for?
Frame Relay can be used for various types of connections. It should be seen as a flexible protocol that lies on the Data Level of the Connections between routers. It can currently be used effectively for carrying all sorts of data, up to speeds of about 4 megabits per second.
Due to the implementation and cost of frame relay, it is most suitable for permanent or semi-permanent connections. It is not desirable as of yet to access frame relay on a dialup basis for economical purposes.
For a number of U.S. Internet clients, use of Frame Relay may allow for the connection of various remote sites using one technology. It is possible to connect the clients router to Frame Relay and access Internet Services over this circuit. At the same time, if the customer has other Frame Relay ports available in different locations, the same port may be used to connect to Wide Area offices the client has. This integrated approach can be attractive for both parties; from one Frame port, U.S. Internet can connect multiple customers. At the same time, the client can connect to multiple remote locations using the one port. Although there is a greater chance of connection then when dedicated lines are used, the economical advantage will in most cases compensate for this.
4. How does frame relay fit in the U.S. Internet strategy?
Initially, U.S. internet is deploying Frame Relay ports for some of the long distance connections required to connect to remote Points of Presence. The cost of these ports is substantial, and the equipment required to operate successfully in this architecture is only now (September 1995) being deployed.
Sprint has been chosen as our frame Relay provider. Initially, we will operate with roughly 1.5 megabit of access bandwidth out of two locations (Knoxville and Nashville). The POP's in Alabama, Chattanooga, Memphis, Johnson City, Clarksville and Pittsburgh, PA will all come on-line on this frame relay system. Several PVC's will be installed to allow for redundant hookups between the various locations.
In a later stage, we may start offering clients access to the network over frame Relay. In this scenario, clients in remote cities where we do not have bandwidth available to service them would be helped by getting in to the Frame cloud, and connecting into one of U.S. Internet's routers.
5. Mixing Frame Relay with Other Technologies.
Frame Relay is nearly a protocol that describes how packets of data move from one location to another; it does not concern itself with the issues of how packets get to and from the frame network. Several techniques can be used to get data in a frame port. U.S. Internet will initially be using Dedicated Fractional T-1 connections to connect to the Frame Cloud.
Next, access over High Speed Modem and ISDN will be investigated. it is technically possible to connect to a Frame cloud using an ISDN connection, then become a part of the frame network, and connect to U.S. Internet's services. Currently, cost of technology and cost of service are prohibitive factors in this scenario, but companies requiring more complicated Wide Area Solutions including internet may wish to look into this option.
6. Pro's and Cons of Frame Relay.
PRO: In many scenario's involving long haul, high speed connections, it is cheaper than dedicated lines.
PRO: There is a cheap solution to incorporate redundancy in the network.
PRO: Mixed speeds can be converted, traffic bursts can be buffered.
PRO: Less hardware is needed to for the same amount of connections
CON: There may be jams; no guaranteed bandwidth
CON: In a point-to-point scenario it is not economically feasible.
CON: In short haul, it is not economically feasible.
7. Technical Aspects of Installing and Running Frame.
The connection to the Frame Relay Network will be made over dedicated T-1 connections. These connections will terminate in a DSU at U.S. Internet, just like a T-1 does. The device used to handle the special frame signaling is called a Frame Relay Access Device, or FRAD. In our case, this function will be performed by the software in our Cisco routers.
In the POPs, 2500's or 4000's will serve as the FRAD, in the NOC's, the 4500's will take care of the FRAD functionality. For implementation of Sub-interface Routing, they will also function as a Frame Switch.
Attached is the Cisco documentation regarding Internet Technologies and Frame relay, a more general and detailed overview of the technology, and Frame Relay Configuration, which goes into the exact configuration strategies and commands in greater details. These documents, as well as many others, are also available on the World Wide Web.
Configuring EIGRP
Before configuring EIGRP, or any IP routing protocol, IP routing must be enabled on the router. To do this first enter global configuration mode. Then enter the command:
ip routing
If you forget to do this you will get an error when you try to enable the EIGRP protocol.
Now from the global configuration prompt type:
router eigrp ASnumber
The Autonomous System number for the EIGRP network is 1565. This will create an EIGRP routing process on the router. It will also give you a new prompt, the router configuration prompt:
routername(config-router)#
From this prompt you can enter configuration commands to define the EIGRP process for this router. To get back to this prompt to reconfigure EIGRP at a later time simply type router eigrp ASnumber again.
You now need to tell the router which networks it should advertise routes for. This is done with the command
network network_address
where network_address is the IP address for the network you wish to add. For example:
eigrp3(config-router)#network 156.156.128.0
Would tell the router to advertise the network 156.156.128.0. You should use the network command for each of the networks that the router is connected to and is a part of the EIGRP network.
Unless this router is the exit router it will not know how to get to locations outside of the AS. In order to reach these destinations we need to give the router a default route over which the router will send packets that it does not have a route for in the routing table. Type exit to return to global configuration mode. We will now add a static route to the routing table using the command
ip route prefix mask address
where prefix is the address of the network you are creating a route for, mask is the mask for this network, and address is the IP address of the interface you are routing the packets to. For all of the eigrp routers except the exit router (the one connected to the core) use the following command to create the default route.
eigrp2(config)# ip route 0.0.0.0 0.0.0.0 156.156.15.1
You have now completed a basic configuration of EIGRP on the router! There are many more configuration options available to you, such as modifying the metrics for each of the interfaces, adjusting the timers and delays for when updates are sent, routes are declared invalid, etc. You can also turn on or off various features such as authentication and split-horizon. To find out more about other commands just type a question mark at the router configuration prompt or read the references listed at the end of the page.
It would be a good idea to save your configuration! To do this type the following at the privileged mode prompt:
write
This will save the currently running configuration to the NVRAM. If the router gets rebooted for some reason ( it shouldn't happen, but it could!) it will use the configuration that is stored in the NVRAM. So save often!
You can view the currently running configuration by typing:
write terminal
This will print the configuration to the screen, but it will not save it.
Verifying Your EIGRP configuration
Once you have configured EIGRP on all four of the routers in the AS and enabled the interfaces you will want to verify that your setup is indeed working.
One easy way to check and see if the packets are getting routed is to ping interfaces on other routers. This done by typing:
ping address
This command can be used at either the user mode or privileged mode prompts. You should be able to get a reply to a ping from every interface on each of the routers. This a simple way to verify that you can reach the other routers within the network.
You can also view the routers current routing table by using the command:
show ip route
This command can be used at either the user mode or privileged mode prompts. The command will give you a table listing all of the routes currently in the routing table. Each entry in the table tells you the following:
The protocol the route was received from - for EIGRP it will be a D. C means that it is directly connected to the router.
Route Type
Destination Address - The address of the remote network the route is for.
Administrative Distance
Metric
Address of the Next Hop
Interface used to reach the Next Hop
There are several useful subcommands as well:
show ip route eigrp ASnumber
This command will only show the EIGRP routes in the table.
show ip route network
This command will give detailed routing information about the specified network.
Another useful source of information is the command series show ip eigrp
This will give you lots of information about the EIGRP process running on the router. You can explore the various commands on your own by typing:
show ip eigrp ?
Configuring RIP
Before configuring RIP, or any IP routing protocol, IP routing must be enabled on the router. To do this first enter global configuration mode. Then enter the command:
ip routing
If you forget to do this you will get an error when you try to enable the RIP protocol.
Now from the global configuration prompt type:
router rip
This will create a RIP routing process on the router. It will also give you a new prompt, the router configuration prompt:
routername(config-router)#
From this prompt you can enter configuration commands to define the RIP process for this router. To get back to this prompt to reconfigure RIP at a later time simply type router rip again.
You now need to tell the router which networks it should advertise routes for. This is done with the command
network network_address
where network_address is the IP address for the network you wish to add. For example:
rip2(config-router)#network 156.156.128.0
Would tell the router to advertise the network 156.156.128.0. You should use the network command for each of the networks that the router is connected to and is a part of the RIP network.
Unless this router is the exit router it will not know how to get to locations outside of the AS. In order to reach these destinations we need to give the router a default route over which the router will send packets that it does not have a route for in the routing table. Type exit to return to global configuration mode. We will now add a static route to the routing table using the command
ip route prefix mask address
where prefix is the address of the network you are creating a route for, mask is the mask for this network, and address is the IP address of the interface you are routing the packets to. For all of the eigrp routers except the exit router (the one connected to the core) use the following command to create the default route.
rip2(config)# ip route 0.0.0.0 0.0.0.0 156.156.11.1
You have now completed a basic configuration of RIP on the router! There are many more configuration options available to you, such as modifying the metrics for each of the interfaces, adjusting the timers and delays for when updates are sent, routes are declared invalid, etc. You can also turn on or off various features such as authentication and split-horizon. To find out more about other commands just type a question mark at the router configuration prompt or read the references listed at the end of the page.
It would be a good idea to save your configuration! To do this type the following at the privileged mode prompt:
write
This will save the currently running configuration to the NVRAM. If the router gets rebooted for some reason ( it shouldn't happen, but it could!) it will use the configuration that is stored in the NVRAM. So save often!
You can view the currently running configuration by typing:
write terminal
This will print the configuration to the screen, but it will not save it.
Verifying Your RIP configuration
Once you have configured RIP on all four of the routers in the AS and enabled the interfaces you will want to verify that your setup indeed working.
One easy way to check and see if the packets are getting routed is to ping interfaces on other routers. This done by typing:
ping address
This command can be used at either the user mode or privileged mode prompts. You should be able to get a reply to a ping from every interface on each of the routers. This a simple way to verify that you can reach the other routers within the network.
You can also view the routers current routing table by using the command:
show ip route
This command can be used at either the user mode or privileged mode prompts. The command will give you a table listing all of the routes currently in the routing table. Each entry in the table tells you the following:
The protocol the route was received from - for RIP it will be an R. C means that it is directly connected to the router.
Route Type - for RIP this wil probably be blank
Destination Address - The address of the remote network the route is for.
Administrative Distance
Metric
Address of the Next Hop
Interface used to reach the Next Hop
There are several useful subcommands as well:
show ip route rip
This command will only show the RIP routes in the table.
show ip route network
This command will give detailed routing information about the specified network.
Another useful source of information is the command series show ip rip
This will give you lots of information about the RIP process running on the router. You can explore the various commands on your own by typing:
show ip rip
Wednesday, November 14, 2007
Cisco Router Copy Commands
Save the current configuration from DRAM to NVRAM - copy running-config startup-config
Merge NVRAM configuration to DRAM - copy startup-config running-config
Copy DRAM configuration to a TFTP server - copy runing-config tftp
Merge TFTP configuration with current router configuration held in DRAM - copy tftp runing-config
Backup the IOS onto a TFTP server - copy flash tftp
Upgrade the router IOS from a TFTP server - copy tftp flash
Cisco Router Debug Commands
Enable debug for RIP - debug ip rip
Enable summary IGRP debug information - debug ip igrp events
Enable detailed IGRP debug information - debug ip igrp transactions
Debug IPX RIP debug - ipx routing activity
Debug IPX SAP - debug IPX SAP
Enable debug for CHAP or PAP - debug ppp authentication
Switch all debugging off - no debug all ,undebug all
Router Show Commands >
View version information - show version
View current configuration (DRAM) - show running-config
View startup configuration (NVRAM) - show startup-config
Show IOS file and flash space - show flash
Shows all logs that the router has in its memory - show log
View the interface status of interface e0 - show interface e0
Overview all interfaces on the router - show ip interfaces brief
View type of serial cable on s0 - show controllers 0 (note the space between the 's' and the '0')
Display a summary of connected cdp devices - show cdp neighbor
Display detailed information on all devices- show cdp entry *
Display current routing protocols -show ip protocols
Display IP routing table- show ip route
Display access lists, this includes the number of displayed matches -show access-lists
Check the router can see the ISDN switch -show isdn status
Check a Frame Relay PVC connections -show frame-relay pvc
show lmi traffic stats- show frame-relay lmi
Display the frame inverse ARP table- show frame-relay map
Basic Router Commands.......
Set a console password to cisco Router(config)#line con 0
Router(config-line)#login
Router(config-line)#password cisco
Set a telnet password Router(config)#line vty 0 4
Router(config-line)#login
Router(config-line)#password cisco
Stop console timing out Router(config)#line con 0
Router(config-line)#exec-timeout 0 0
Set the enable password to cisco Router(config)#enable password cisco
Set the enable secret password to peter.
This password overrides the enable password and is encypted within the config file
Router(config)#enable secret peter
Enable an interface Router(config-if)#no shutdown
To disable an interface Router(config-if)#shutdown
Set the clock rate for a router with a DCE cable to 64K Router(config-if)clock rate 64000
Set a logical bandwidth assignment of 64K to the serial interface Router(config-if)bandwidth 64 (Note that the zeroes are not missing )
To add an IP address to a interface Router(config-if)#ip addr 10.1.1.1 255.255.255.0
To enable RIP on all 172.16.x.y interfaces Router(config)#router rip
Router(config-router)#network 172.16.0.0
Disable RIP Router(config)#no router rip
To enable IRGP with a AS of 200, to all interfaces Router(config)#router igrp 200
Router(config-router)#network 172.16.0.0
Disable IGRP Router(config)#no router igrp 200
Static route the remote network is 172.16.1.0, with a mask of 255.255.255.0, the next hop is 172.16.2.1, at a cost of 5 hops Router(config)#ip route 172.16.1.0 255.255.255.0 172.16.2.1 5
Disable CDP for the whole router Router(config)#no cdp run
Enable CDP for he whole router Router(config)#cdp run
Disable CDP on an interface Router(config-if)#no cdp enable
ISDN........
ISDN, which stands for Integrated Services Digital Network, is a system of digital phone connections which has been available for over a decade. This system allows voice and data to be transmitted simultaneously across the world using end-to-end digital connectivity.
With ISDN, voice and data are carried by bearer channels (B channels) occupying a bandwidth of 64 kb/s (bits per second). Some switches limit B channels to a capacity of 56 kb/s. A data channel (D channel) handles signaling at 16 kb/s or 64 kb/s, depending on the service type. Note that, in ISDN terminology, "k" means 1000 (103), not 1024 (210) as in many computer applications (the designator "K" is sometimes used to represent this value); therefore, a 64 kb/s channel carries data at a rate of 64000 b/s. A new set of standard prefixes has recently been created to handle this. Under this scheme, "k" (kilo-) means 1000 (103), "M" (mega-) means 1000000 (106), and so on, and "Ki" (kibi-) means 1024 (210), "Mi" (mebi-) means 1048576 (220), and so on.
(An alert reader pointed out some inconsistencies in my use of unit terminology throughout this Tutorial. He also referred me to a definitive web site. As a result, I have made every effort to both conform to standard terminology, and to use it consistently. I appreciate helpful user input like this!)
There are two basic types of ISDN service: Basic Rate Interface (BRI) and Primary Rate Interface (PRI). BRI consists of two 64 kb/s B channels and one 16 kb/s D channel for a total of 144 kb/s. This basic service is intended to meet the needs of most individual users.
PRI is intended for users with greater capacity requirements. Typically the channel structure is 23 B channels plus one 64 kb/s D channel for a total of 1536 kb/s. In Europe, PRI consists of 30 B channels plus one 64 kb/s D channel for a total of 1984 kb/s. It is also possible to support multiple PRI lines with one 64 kb/s D channel using Non-Facility Associated Signaling (NFAS).
H channels provide a way to aggregate B channels. They are implemented as:
H0=384 kb/s (6 B channels)
H10=1472 kb/s (23 B channels)
H11=1536 kb/s (24 B channels)
H12=1920 kb/s (30 B channels) - International (E1) only
To access BRI service, it is necessary to subscribe to an ISDN phone line. Customer must be within 18000 feet (about 3.4 miles or 5.5 km) of the telephone company central office for BRI service; beyond that, expensive repeater devices are required, or ISDN service may not be available at all. Customers will also need special equipment to communicate with the phone company switch and with other ISDN devices. These devices include ISDN Terminal Adapters (sometimes called, incorrectly, "ISDN Modems") and ISDN Routers.