Table Of Contents
Cisco AS5850 Universal Gateway
Commissioning GuidelinesInformation About Cisco AS5850 Universal Gateway Commissioning
How to Commission the Cisco AS5850 Universal Gateway
Analyze the System Boot Dialog
Verify the Operating Environment
Inspect the Initial Running Configuration
Explore the Cisco IOS File System
Task 2. Configuring Basic Cisco IOS Software
Configure Host Name, Enable-Secret Password, and Time Stamps
Task 3. Configuring Channelized T1 or E1
Task 4. Configuring Channelized T3
Task 6. Configuring the Serial Interfaces
Task 7. Configuring Ports and Lines
Task 8. Enabling IP Basic Setup
Task 9. Testing Asynchronous EXEC-Shell Connections
Task 10. Configuring GigE Egress
Task 11. Confirming the Final Running Configuration
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Obtaining Technical Assistance
Cisco Technical Support Website
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Cisco AS5850 Universal Gateway
Commissioning Guidelines
These guidelines detail Cisco AS5850 commissioning, from formal functional setup of the equipment, through systematic software configurations, to initial preparation of the system for data/voice call processing, using local-based authentication.
Use this guide in conjunction with these other Cisco AS5850 documents:
•
Cisco AS5850 Universal Gateway Hardware Installation Guide at http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5850/hw_inst/5850hig/
•
Cisco AS5850 Universal Gateway Card Guide at http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5850/hw_inst/5850cg/
•
Cisco AS5850 Operations, Administration, Maintenance, and Provisioning Guide at http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5850/sw_conf/5850oamp/
Contents
•
Information About Cisco AS5850 Universal Gateway Commissioning
•
How to Commission the Cisco AS5850 Universal Gateway
Information About Cisco AS5850 Universal Gateway Commissioning
To build a network using the Cisco AS5850, it is necessary to understand the following:
•
The route-switch-controller (RSC) card
•
Call-processing components
The Cisco AS5850 universal gateway basic interfaces are as follows:
•
Egress connects to the IP backbone
•
Ingress connects from the PSTN
Figure 1 shows the Cisco AS5850 system architecture.
Figure 1 Cisco AS5850 System Architecture
Route-Switch-Controller Card
The route-switch-controller (RSC) card is the main processor card for the universal gateway. It installs in either slot 6 or slot 7 and plugs directly into the backplane, and performs the following functions:
•
Transfers data as Fast Ethernet or Gigabit Ethernet packets encapsulated in proprietary protocol. This connection is also used for management.
•
For egress, can connect to the IP backbone via two Gigabit Ethernet ports (in Figure 1, the RSC card uses GigabitEthernet6/0 or GigabitEthernet6/1 to connect to the IP backbone).
•
Boots and reloads its own Cisco IOS software image.
•
Provides source clocks for use by all feature cards and power supplies. Extracts an external reference clock from an external E1 or T1 signal through a BNC connector on the front panel.
•
Can connect to an external alarm source through a DB-15 serial connector on the front panel.
•
Provides a console port for initial configuration and maintenance.
•
Supports SNMP for management information and enables retrieval of syslog information for troubleshooting.
•
Provides high availability when configured in handover-split mode.
Note
If there are two RSCs in the chassis, they can be configured in classic-split mode or handover-split mode. For more information on configuring the RSC, see the Cisco AS5850 Operations, Administration, Maintenance, and Provisioning Guide at http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5850/sw_conf/ 5850oamp/index.htm.
The Dial Shelf Interconnect Protocol (DSIP) enables communication between RSC and feature cards:
•
Trunk cards connect to the public switched telephone network (PSTN) and fit in slots 0-5 and 8-13 only.
–
In classic-split mode, the RSC card in slot 6 controls slots 0-5; the RSC card in slot 7 controls slots 8-13.
–
In handover-split mode, each RSC can take over the feature cards of the other RSC if that RSC fails.
•
Universal port cards also fit in slots 0-5 and slots 8-13, between the trunk cards and the RSC cards. The universal port card supports voice, modem, or fax connections. Each port can carry one DS0 of network traffic.
Call-Processing Components
As shown in Figure 2, the following components process a call:
•
Client modems and ISDN routers dial in to the universal gateway through the PSTN.
•
Asynchronous PPP calls (analog) connect to ports inside the universal gateway.
•
Each port inside the universal gateway provides a corresponding TTY line and asynchronous interface for terminating character and packet mode services.
•
Asynchronous interfaces clone their configurations from a group-async interface.
•
Synchronous PPP calls (digital) connect to serial interface channels (for example, S0/0:1:23 and S2/0:2:23).
•
Synchronous interfaces clone their configurations from a dialer interface.
Figure 2 Cisco AS5850 Call-Processing Components
One asynchronous PPP call requires the following:
•
1 DS0 channel
•
1 channel in a TDM bus
•
1 integrated modem
•
1 TTY line
•
1 asynchronous interface
One synchronous PPP call requires the following:
•
1 DS0 channel
•
1 serial interface channel
Note
Synchronous PPP calls require HDLC resources. Each T3 trunk card supports 256 HDLC components and each STM1 card supports 512 HDLC components. E1 trunk cards do not have HDLC resource limitations.
How to Commission the Cisco AS5850 Universal Gateway
This section contains the following information:
•
Task 1. Verifying Basic Setup
•
Task 2. Configuring Basic Cisco IOS Software
•
Task 3. Configuring Channelized T1 or E1
•
Task 4. Configuring Channelized T3
•
Task 6. Configuring the Serial Interfaces
•
Task 7. Configuring Ports and Lines
•
Task 8. Enabling IP Basic Setup
•
Task 9. Testing Asynchronous EXEC-Shell Connections
•
Task 10. Configuring GigE Egress
•
Task 11. Confirming the Final Running Configuration
Task 1. Verifying Basic Setup
To verify that basic system components are functioning, see the following sections:
•
Analyze the System Boot Dialog
•
Inspect the Initial Running Configuration
•
Explore the Cisco IOS File System
Analyze the System Boot Dialog
To view the boot sequence through a terminal session, you must have a console connection to the universal gateway before it powers up.
The following boot sequence occurs. Event numbers and comments are inserted in the example to describe the boot sequence.
In this segment, the universal gateway decompresses the system boot image, tests the NVRAM for validity, and decompresses the Cisco OS software image.
System Bootstrap, Version 12.2(2)T, RELEASE SOFTWARE (fc1)Copyright (c) 2000 by cisco Systems, Inc.5850-rsc platform with 524288 Kbytes of main memorySelf decompressing the image : ######################################################################################################################################################################### [OK]Sometimes boot images do not support hardware cards. Error messages look like this sample.
%OIR-3-SEATED: Insert/removal failed
Note
Ignore these messages, but do not ignore error messages that appear after the Cisco IOS software image decompresses.
Self decompressing the image : ######################################################################################################################################################################### [OK]In this segment the following components are detected:
•
Cisco IOS release
•
Available memory
•
Available interfaces
Restricted Rights LegendUse, duplication, or disclosure by the Government issubject to restrictions as set forth in subparagraph(c) of the Commercial Computer Software - RestrictedRights clause at FAR sec. 52.227-19 and subparagraph(c) (1) (ii) of the Rights in Technical Data and ComputerSoftware clause at DFARS sec. 252.227-7013.cisco Systems, Inc.170 West Tasman DriveSan Jose, California 95134-1706Cisco Internetwork Operating System SoftwareIOS (tm) 5850 Software (C5850-P6-M), Version 12.2(20010828:201655)]Copyright (c) 1986-2001 by cisco Systems, Inc.Compiled Tue 28-Aug-01 16:20 byImage text-base: 0x60008960, data-base: 0x6160E000cisco c5850 (R7K) processor (revision 0.12) with 196608K/65536K bytes of memory.R7000 CPU at 259Mhz, Implementation 39, Rev 2.1, 256KB L2, 2048KB L3 CacheLast reset from Mbus resetChannelized E1, Version 1.0.X.25 software, Version 3.0.0.Bridging software.SuperLAT software (copyright 1990 by Meridian Technology Corp).Primary Rate ISDN software, Version 1.1.1 FastEthernet/IEEE 802.3 interface(s)2 Gigabit Ethernet/IEEE 802.3 interface(s)1404 terminal line(s)24 Channelized T1/PRI port(s)2 Channelized T3 port(s)507K bytes of non-volatile configuration memory.32768K bytes of Compact Flash card at slot 0 (Sector size 128K).16384K bytes of Flash internal SIMM (Sector size 256K).
Note
If a hardware card is not recognized, verify that you are running the optimum version of Cisco IOS software. See the hardware-software compatibility matrix, available online (logon required) at http://www.cisco.com/cgi-bin/front.x/Support/HWSWmatrix/hwswmatrix.cgi.
The following system message and prompt appears.
--- System Configuration Dialog ---Would you like to enter the initial configuration dialog? [yes/no]: noBecause the universal gateway has never been configured, the Cisco IOS software cannot find a startup-config file, so abort the configuration dialog. In this example, the Cisco IOS software is configured manually; the automatic setup script is not used. The RSC card auto-detects the state of each card in the chassis.
00:00:09: %MBUS-3-UNKNOWN_REGISTER: Status change message for register 9 in slot 6,value = 200:00:09: %MBUS-3-UNKNOWN_REGISTER: Status change message for register 0 in slot 6,value = 8800:00:09: %MBUS-3-UNKNOWN_REGISTER: Status change message for register 9 in slot 6,value = 000:00:37: %SYS-7-NV_BLOCK_INIT: Initalized the geometry of nvram00:00:42: %LINK-5-CHANGED: Interface FastEthernet6/0, changed state to initializing00:00:42: %LINK-5-CHANGED: Interface GigabitEthernet6/1, changed state to initializing00:00:42: %DSCREDCLK-5-BSWITCHT: Backup clock matched to the active clock reference,slot 3 line 000:00:43: %DSCREDCLK-5-BNORMAL: Backup clock moving to NORMAL to phase lock to theactive clock00:00:43: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet6/0, changedstate to down00:00:43: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet6/1, changedstate to down00:00:45: %LINK-5-CHANGED: Interface GigabitEthernet6/1, changed state to administrativelydown00:00:52: %LINK-3-UPDOWN: Interface FastEthernet6/0, changed state to up00:00:53: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet6/0, changedstate to up00:00:56: %SYS-5-CONFIG_I: Configured from memory by console00:01:15: %LINK-3-UPDOWN: Interface GigabitEthernet6/0, changed state to up00:01:17: %SYS-5-RESTART: System restarted --Cisco Internetwork Operating System SoftwareIOS (tm) 5850 Software (C5850-P6-M), Version 12.1(20001120:130907)[ssangiah-121_5_xv_build 100]Copyright (c) 1986-2000 by cisco Systems, Inc.Compiled Mon 20-Nov-00 05:09 by00:01:17: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet6/0, changedstate to up00:01:17: %SYS-6-BOOTTIME: Time taken to reboot after reload = 209 seconds00:01:17: %OIR-6-REMCARD: Card removed from slot 11, interfaces disabled00:01:17: %OIR-6-REMCARD: Card removed from slot 12, interfaces disabledPress RETURN to get started!Router>Verify the Operating Environment
To verify the operating environment, perform the following steps as appropriate for your system.
Step 1
Power up the Cisco AS5850.
Step 2
Verify that there are no critical grounding, cooling, or power problems.
AS5850# show environmentSlot # Exhaust Sensor Inlet Sensor(deg C) (deg C)0 54.5 37.01 50.5 31.52 32.0 32.54 44.5 35.55 44.0 28.56 26.5 24.57 26.5 24.58 41.5 27.59 40.5 29.010 42.0 29.011 33.5 33.013 47.0 32.0Slot # 3.3V 5V MBUS 5V(mv) (mv) (mv)0 3260 4968 50801 3260 4920 50722 3276 4976 50884 3268 4976 50805 3260 4976 51046 3284 5016 51287 3288 4984 51208 3276 4976 50809 3276 4968 508010 3256 4976 508811 3272 4944 507213 3264 4944 5096Slot # 5.15V MBUS 5V 48V AMP_48 1.60V(mv) (mv) (Volt) (Amp) (mv)24 5520 5136 49 13 164024 RAW 690 642 698 209 41025 5536 5136 50 13 180825 RAW 692 642 712 218 452PEMF slot 24: AC Shelf is normalPEMF slot 24: Blower is normal. (MBUS Port2 returns 8E)PEMF slot 25: AC Shelf is normalPEMF slot 25: Blower is normal. (MBUS Port2 returns 8E)Step 3
Check the Cisco IOS software image, uptime, and restart reason.
AS5850# show versionCisco Internetwork Operating System SoftwareIOS (tm) 5850 Software (C5850-P6-M), Version 12.1(20000624:130156)]Copyright (c) 1986-2000 by cisco Systems, Inc.Compiled Thu 20-Jul-00 09:11 byImage text-base: 0x60008908, data-base: 0x612B0000ROM: System Bootstrap, Version 12.0(20000306:065252) [gclendon-rsc-rommon 104],EROM: 5850 Software (C5850-BOOT-M), Version 12.1(20000624:130156) []AS5850 uptime is 18 hours, 30 minutesSystem returned to ROM by reloadSystem image file is "disk0:c5850-p6-mz"cisco c5850 (R7K) processor with 229376K/32768K bytes of memory.R7000 CPU at 262Mhz, Implementation 39, Rev 1.0, 256KB L2, 2048KB L3 CacheLast reset from unexpected valueChannelized E1, Version 1.0.X.25 software, Version 3.0.0.Bridging software.SuperLAT software (copyright 1990 by Meridian Technology Corp).Primary Rate ISDN software, Version 1.1.1 FastEthernet/IEEE 802.3 interface(s)2 Gigabit Ethernet/IEEE 802.3 interface(s)756 terminal line(s)24 Channelized T1/PRI port(s)1 Channelized T3 port(s)507K bytes of non-volatile configuration memory.
Inspect the Feature Cards
To inspect the feature cards, perform the following steps.
Step 1
Verify that feature cards are up.
AS5850# show chassisSystem is in classic-split mode, RSC in slot 6.Slots owned: 0 1 2 3 4 5Slots configured: 0 1 2 3 4 5Slots owned by other: 8 9 10 11 12 13Slot Board CPU DRAM I/O Memory State ElapsedType Util Total (free) Total (free) Time0 24T1 0%/0% 0( 0%) 0( 0%) Booting 00:00:234 CT3_UP216 0%/0% 0( 0%) 0( 0%) Booting 00:00:235 UP324 0%/0% 0( 0%) 0( 0%) Up 00:00:01System set for auto bootPossible feature-card states include unknown, down, resetting, booting, and up. The Up state means that a card can communicate with the RSC card.
Each universal port card contains its own DRAM memory and performs its own call processing. A normal CPU utilization range is 20-40%.
Step 2
If the feature card does not come up, perform the following troubleshooting steps.
a.
Look for LED lights on the feature card. If the lights are off, try reseating the card.
Note
More more information about the feature card LEDs, see the Cisco AS5850 Universal Gateway Card Guide that shipped with this system.
b.
Verify that the RSC connection to the other cards is up.
AS5850# show dsi6/0 is up, line protocol is upHardware is AmdFE, address is 00b6.eaf4.2b00 (bia 00b6.eaf4.2b00)MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation ARPA, loopback not setUnknown duplex, Unknown Speed, 100BaseTX/FXARP type:ARPA, ARP Timeout 04:00:00Last input 00:00:00, output 00:00:00, output hang neverLast clearing of "show interface" counters neverQueueing strategy:fifoOutput queue 0/600, 0 drops; input queue 0/600, 0 drops1 minute input rate 0 bits/sec, 0 packets/sec1 minute output rate 0 bits/sec, 0 packets/sec45114 packets input, 3795862 bytesReceived 0 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored0 watchdog0 input packets with dribble condition detected22342 packets output, 15268108 bytes, 0 underruns(0/0/0)0 output errors, 0 collisions, 1 interface resets0 output errors, 0 collisions, 1 interface resets0 babbles, 0 late collision, 0 deferred0 lost carrier, 0 no carrier0 output buffer failures, 0 output buffers swapped outInterface 6/0Hardware is AMD LagunaADDR:64FD7E24, FASTSEND:6001ED60, MCI_INDEX:0DIST ROUTE ENABLED:0Route Cache Flag:0LADRF=0x0000 0x0000 0x0000 0x0000CSR0 =0x00000072, CSR3 =0x00001044, CSR4 =0x0000491D, CSR15 =0x00008180CSR80 =0x00009900, CSR114=0x00000000, CRDA =0x16462250, CXDA =0x16465230BCR9 =0x00000001 (full-duplex)CSR5 =0x00000001, CSR7 =0x00000A20, CSR100=0x0000F000, CSR125=0x00005C3CBCR2 =0x00001000, BCR9 =0x00000001, BCR18 =0x000019E0, BCR22 =0x0000FF06BCR25 =0x00000017, BCR26 =0x0000000B, BCR27 =0x00000000, BCR32 =0x00004080BCR4 =0x000000C0, BCR7 =0x00000090, BCR20 =0x00000303, BCR39 =0x00000000BCR33 =0x00004800, BCR34 =0x0000FFFFHW filtering information:Promiscuous Mode Enabled, PHY Addr Enabled, Broadcast Addr EnabledPHY Addr=00B6.EAF4.2B00, Multicast Filter=0x0000 0x0000 0x0000 0x0000amdp2_instance=0x64FD9B70, registers=0x48000000, ib=0x6461D20rx ring entries=512, tx ring entries=512rxring=0x6461D80, rxr shadow=0x64FD9D2C, rx_head=77, rx_tail=0txring=0x6463DC0, txr shadow=0x64FDA558, tx_head=327, tx_tail=327, tx_count=0spurious_idon=0, throttled=0, enabled=0, disabled=0rx_framing_err=0, rx_overflow_err=0, rx_buffer_err=0, rx_bpe_err=0rx_soft_overflow_err=0, rx_no_enp=0, rx_discard=0, rx_miss_count=0tx_one_col_err=0, tx_more_col_err=0, tx_no_enp=0, tx_deferred_err=0tx_underrun_err=0, tx_late_collision_err=0, tx_loss_carrier_err=0tx_exc_collision_err=0, tx_buff_err=0, fatal_tx_err=0 tx_limited=0(0)
Note
Loss of DSIP keepalive messages indicates that there is no communication between the RSC card and the feature cards. After DSIP Hello messages succeed, the backplane Fast Ethernet connection changes its state to Up. Until the interfaces are up, the RSC card and feature cards cannot communicate.
CautionVerify that console logging is disabled. To do so, enter the show logging command and then, if needed, the no logging console command. If logging is enabled, the universal gateway might intermittently freeze up as soon as the console port gets overloaded with log messages.
Messages appear on the console terminal after the feature card is physically removed from slot 12 and reinserted. Approximately 120 seconds elapse before all these messages appear.
AS5850>04:42:13: %ISDN-6-LAYER2DOWN: Layer 2 for Interface Se1/12/0:0:23, TEI 0 changedto down04:42:46: %DSIPPF-5-DS_KEEPALIVE_LOSS: DSIP Keepalive Loss from slot 1204:42:53: %DSIPPF-5-DS_HELLO: DSIP Hello from slot 12 SucceededAS5850>The following boot sequence occurs in the previous example:
•
The feature card takes 15 seconds to boot up. Afterward, the card checks the system inventory.
•
The RSC card loads the appropriate boot images onto the feature cards.
•
More than one minute elapses before the RSC card detects the first DSIP Hello message from the first feature card (in slot 12).
•
The RSC card gives the feature cards the appropriate images.
c.
For advanced troubleshooting of the feature cards after the RSC card is up, open a virtual-console session to the feature card. To end the session, enter Ctrl-C three times.
AS5850# dsip console slave 12Trying Dial shelf slot 12 ...Entering CONSOLE for slot 12Type "^C^C^C" to end this sessionDA-Slot12>DA-Slot12#DA-Slot12#DA-Slot12#Terminate NIP IO session? [confirm][Connection to Dial shelf slot 12 closed by local host]AS5850#
Note
If the show chassis command reports that feature cards are booting for extended periods of time, start debugging from the RSC card by using the following commands:
•
debug dsip transport shows the registered MAC address sent from each feature card.
•
debug dsip trace displays detailed DSIP hello and keepalive messages.
•
debug dsip boot shows whether the RSC card is sending the boot image to the feature cards.
To learn more about these and other Cisco IOS commands, start at http://www.cisco.com/univercd/cc/td/doc/product/software/ and click on your Cisco IOS release.
Use the DSIP Commands
The RSC card communicates with the feature cards using the following:
•
Backplane MBUS
•
Backplane packet bus
•
Backplane Dial Shelf Interconnect Protocol (DSIP)
Note
DSIP commands on the Cisco AS5850 function very much like the DSIP commands for the Cisco AS5800. For the DSIP command reference and other system management functions, see Dial and System Management Commands for the Cisco AS5800 at http://www.cisco.com/univercd/cc/td/doc/product/software/ios113ed/113aa/113aa_2/58cfeats/ c5800uas.htm.
To use the DSIP commands, perform the following steps.
Step 1
To understand how DSIP functions, enter commands from the following example.
Note
Output from the show dsi command differs from that for the show dsip command.
AS5850# show dsipDSIP transport statistics:IPC : input msgs=595876, bytes=54824426; output msgs=80748, bytes=4884676total consumed ipc msgs=653; total freed ipc msgs = 653transmit contexts in use = 10, free = 246, zombie = 0, invalid = 0ipc getmsg failures = 0, ipc timeouts=0core getbuffer failures=0, api getbuffer failures=0dsip test msgs rcvd = 0, sent = 0CNTL : input msgs=18800, bytes=1282416; output msgs=9585, bytes=5215320getbuffer failures=0DATA : input msgs=540, bytes=19440; output msgs=0, bytes=0DSIP Private Buffer Pool Hits = 0DSIP registered addresses:Shelf0 : Master: 0044.efbe.3d37, Status=localDSIP Clients:-------------ID Name0 Console1 Clock2 Modem3 Logger4 TDM5 Trunk6 Async data7 Unused8 Dial shelf manager9 Unused10 Unused11 RSC Red. UI12 Unused13 NextPort14 Signalling15 Unused16 DSIP MIPC17 Marvel Flow Manager18 gigE19 Unused20 Egress Driver21 DSIP TestDSIP local ports:----------------Client:Portname Portid In-Msgs Bytes Last-i/pConsole:Master 10005 0 0 neverClock:Master 10006 1058 245228 00:00:51Modem:Master 10007 2 28 17:35:41Logger:Master 10008 0 0 neverTDM:Master 10009 2 48 17:35:41Trunk:Master 1000A 51432 4319776 00:00:00Async data:Master 1000B 0 0 neverDial shelf manager:Master 1000D 0 0 neverRSC Red. UI:Master 1000E 0 0 neverNextPort:Master 1000F 737 30736 17:35:15Signalling:Master 10010 0 0 neverDSIP MIPC:Master 10011 0 0 neverMarvel Flow Manager:Master 10012 2 8 17:35:40gigE:Master 10013 2 8 17:35:39Egress Driver:Master 10014 25337 3445832 00:00:00DSIP Test:Master 10015 0 0 neverDSIP remote ports:-----------------Client:Portname Portid Out-Msgs Bytes Last-o/p Last-actModem:Slave1 1080007 326 8008 17:35:57 17:36:34NextPort:Slave1 108000A 56 3904 17:35:58 17:36:33Marvel Flow Manager:Slave1 108000D 2 2700 17:36:31 17:36:31gigE:Slave1 108000E 1 12 17:36:30 17:36:30Clock:Slave13 1140006 1 28 17:35:43 17:35:43Modem:Slave13 1140007 218 6280 17:35:15 17:35:43Trunk:Slave13 1140009 8 4512 17:35:43 17:35:43NextPort:Slave13 114000B 38 2608 17:35:16 17:35:42Marvel Flow Manager:Slave1 114000E 2 2700 17:35:41 17:35:41gigE:Slave13 114000F 1 12 17:35:39 17:35:39DSIP ipc queue:---------------There are 0 IPC messages waiting for acknowledgement in the transmit queue.There are 0 messages currently in use by the system.DSIP ipc nodes:---------------There are 3 nodes in this IPC realm.ID Type Name Last LastSent Heard10000 Local IPC Master 0 01080000 DSIP Dial Shelf:Slave1 33 331140000 DSIP Dial Shelf:Slave13 40 40DSIP version information:------------------------Local DSIP major version = 5, minor version = 2All feature boards are running DSIP versions compatible with router shelfLocal clients registered versions:------------------------------------Client Name Major Version Minor VersionConsole 5 2Clock 2 1Modem 1 0Logger No version No versionTDM No version No versionTrunk No version No versionAsync data No version No versionVOICE 0 0Dial shelf No version No versionRSC Red. UI 0 1NextPort 0 0Signalling 1 5DSIP MIPC No version No versionMarvel Flow No version No versiongigE No version No versionEgress Driv No version No versionDSIP Test No version No versionMismatched remote client versions:Step 2
Verify that each feature card's MAC address is registered by DSIP with the show dsip transport command. Unregistered cards cannot communicate with the system. Shelf 0 is the RSC card (master). Shelf 1 is the feature card (slave).
AS5850# show dsip transportDSIP transport statistics:IPC : input msgs=596027, bytes=54838680; output msgs=80772, bytes=4886020total consumed ipc msgs=653; total freed ipc msgs = 653transmit contexts in use = 10, free = 246, zombie = 0, invalid = 0ipc getmsg failures = 0, ipc timeouts=0core getbuffer failures=0, api getbuffer failures=0dsip test msgs rcvd = 0, sent = 0CNTL : input msgs=18804, bytes=1282744; output msgs=9587, bytes=5215440getbuffer failures=0DATA : input msgs=540, bytes=19440; output msgs=0, bytes=0DSIP Private Buffer Pool Hits = 0DSIP registered addresses:Shelf0 : Master: 0044.efbe.3d37, Status=localAS5850#Step 3
Verify that all feature cards are running DSIP versions that are compatible with the RSC card.
AS5850# show dsip versionDSIP version information:------------------------Local DSIP major version = 5, minor version = 2All feature boards are running DSIP versions compatible with router shelfLocal clients registered versions:------------------------------------Client Name Major Version Minor VersionConsole 5 2Clock 2 1Modem 1 0Logger No version No versionTDM No version No versionTrunk No version No versionAsync data No version No versionVOICE 0 0Dial shelf No version No versionRSC Red. UI 0 1NextPort 0 0Signalling 1 5DSIP MIPC No version No versionMarvel Flow No version No versiongigE No version No versionEgress Driv No version No versionDSIP Test No version No versionMismatched remote client versions:-----------------------------------
Note
The show dsip version command also reports mismatched Cisco IOS software versions. No mismatches exist in this example.
Inspect the Initial Running Configuration
The Cisco IOS software creates an initial running configuration. To familiarize yourself with the default settings, inspect the software configuration on the RSC card as follows.
AS5850# show running-configBuilding configuration...Current configuration : 1495 bytes!version 12.2no service single-slot-reload-enableservice timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname AS5850!!redundancymode classic-splitno logging bufferedlogging rate-limit console 10 except errors!!resource-pool disablespe link-info poll voice 5!!ip subnet-zeroip cef distributedno ip finger!!controller T3 0/0cablelength 224!controller T3 1/0cablelength 224!!interface FastEthernet6/0no ip addressip route-cache distributedlogging event link-statusshutdown!interface GigabitEthernet6/0no ip addressip route-cache distributedlogging event link-statusshutdownno negotiation auto!interface GigabitEthernet6/1no ip addressip route-cache distributedlogging event link-statusshutdownno negotiation auto!interface Group-Async0no ip addressip route-cache distributedgroup-range 0/00 4/323!ip kerberos source-interface anyip classlessno ip http server!!line con 0logging synchronoustransport input noneline aux 0line vty 0 4line 0/00 1/215activation-character 0disconnect-character 0modem InOutno modem status-pollno modem log rs232escape-character soft 0escape-character 0hold-character 0line 2/00 4/323activation-character 0disconnect-character 0modem InOutno modem status-pollno modem log rs232escape-character soft 0escape-character 0hold-character 0!endExplore the Cisco IOS File System
Familiarize yourself with the file system and memory storage areas. The Cisco IOS file system provides a consolidated interface to the following:
•
Compact-flash memory file system
•
Network file system (TFTP, rcp, and FTP)
•
Any other endpoint for reading or writing data (such as NVRAM, SPE firmware, the running configuration, ROM, raw system memory, Xmodem, and flash load helper log)
Figure 3 shows the memory locations inside the Cisco AS5850.
Figure 3 Cisco AS5850 Memory Locations
Table 1 describes the memory types on the Cisco AS5850.
To inspect the file system, perform the following steps as appropriate for your system.
Step 1
View the different file storage areas and file management functions. Additionally, verify that you have everything you ordered from manufacturing, such as flash memory. The asterisk (*) near the bottom of the output indicates the current directory.
AS5850# show file systemsFile Systems:Size(b) Free(b) Type Flags Prefixes31916032 14307328 flash rw disk0:- - network rw rcp:- - opaque rw null:- - opaque rw system:- - network rw tftp:520184 481796 nvram rw nvram:* 15990784 11484640 flash rw bootflash: flash:- - network rw ftp:AS5850#Step 2
Display the objects in the system memory directory:
AS5850# dir system:Directory of system:/1 -rw- 51613 <no date> running-config2 dr-x 0 <no date> memory12 dr-x 0 <no date> vfilesNo space information availableAS5850#
Note
Remember to include the trailing colon (:) in the dir commands.
Step 3
Inspect the flash memory. As the chassis boots up, the image is copied, decompressed, and loaded into DRAM memory.
AS5850# pwddisk0:AS5850# dirDirectory of disk0:/3 -rw- 325539 Jan 01 2000 04:33:44 np_6_83_2.spe83 -rw- 8987568 Jan 02 2000 02:45:30 c5850-p6-mz.Aug232278 -rw- 8617256 Jan 01 2000 00:17:16 c5850-p6-mz.Sep531916032 bytes total (13299712 bytes free)Step 4
Inspect the boot flash.
AS5850# dir bootflash:Directory of bootflash:/1 -rw- 1863976 Mar 01 1993 00:05:28 c5850-boot-mz.May2615990784 bytes total (14100676 bytes free)
Note
Keep a backup copy of the RSC Cisco IOS image in boot flash in case compact-flash memory cards are misplaced.
Step 5
Inspect the NVRAM memory on the RSC. Three files are present:
•
The initial boot or startup-config.
•
The private-config. This is a secure file that supports encryption technologies. It is not user accessible.
•
The underlying-config. This is the version of the startup-config that is stored in NVRAM.
AS5850# dir nvram:Directory of nvram:/1 -rw- 739 <no date> startup-config2 ---- 24 <no date> private-config3 -rw- 739 <no date> underlying-config129016 bytes total (128277 bytes free)AS5850#
Verify Memory Usage
Use the show memory summary command to do the following:
•
Verify how memory is used for different processor and I/O memory processes.
•
Identify memory leaks or fragmentation.
–
Memory leaks occur when memory is not released back to the processor. They are indicated by steady decreases of free memory. However, the preferred way to track memory leaks is to monitor the FreeMem variable in the OID MIB.
–
Memory fragmentation is indicated when the largest block of memory is unequal to the free block. Fragmentation increases as the numbers grow further apart.
To determine and calculate memory usage, perform the following steps.
Step 1
Display the memory status report. In the example, the largest memory block is close to the free-memory block. There is no fragmentation.
AS5850# show memory summaryHead Total(b) Used(b) Free(b) Lowest(b) Largest(b)Processor 616CCD20 479408864 44937912 434470952 431866220 431896392I/O E000000 33554432 2633464 30920968 30066928 30132444Processor memoryAlloc PC Size Blocks Bytes What0x60009E3C 172 4 688 Init0x6000F748 432 1080 466560 IDB: Serial Info0x6000F748 436 1 436 IDB: Serial Info0x6000F748 444 1 444 IDB: Serial Info0x60017BE4 2048 1 2048 Init0x60017C10 4096 1 4096 Init0x6001B09C 184 1 184 Init0x600265F0 128 25 3200 RIF Cache0x6006CDFC 176 1086 191136 FIB: FIBIDB0x6006D514 30000 1 30000 FIB: HWIDB MAP TABLE0x6006D6A8 560 1086 608160 FIB: FIBHWIDB0x6006D8CC 30000 1 30000 Init0x6006EF08 1460 1 1460 RemoveReceiveHash Entries0x60071274 1900 1 1900 FIB one path chunk0x60071274 65496 1 65496 FIB one path chunk0x6007CB74 1072 1 1072 FIB: Control Block0x6007CBA0 32 1 32 Init0x6007CE4C 30000 1 30000 FIB: Root-table0x6007CE68 30000 1 30000 FIB: Cblk-table0x6007CED8 144 1 144 FIB ndb0x6007CEF4 384 1 384 FIB rdb0x6007CF30 92 1 92 Init
CautionIf you enter the show memory summary command with the terminal length 0 command enabled, many output screens appear that might interrupt your session.
Table 2 describes the significant fields in the previous display.
Step 2
Convert bytes to megabytes (MB):
•
Total processor memory = 479,408,864 bytes = 457.2 MB
•
Used processor memory = 44,937,912 bytes = 42.9 MB
•
Free processor memory = 434,470,952 bytes = 414.3 MB
Total memory (457.2 MB) = Used memory (42.9 MB) + free memory (414.3 MB)
Step 3
Do some useful memory calculations:
Total Processor = Total RAM - Cisco IOS software (use the show version command to get the MB assigned for all of Cisco IOS software + processor)
cisco c5850 (R7K) processor (revision 0.12) with 491520K/32768K bytes of memory.491520K = 480 MB
+ 32768K = 32 MB
Total = 512 MB (what you purchased)
Verify CPU Utilization
High utilization causes network performance problems. Knowing when the gateway is running at over 50% utilization is critical because the gateway might start dropping packets if an unexpected traffic burst comes through, or if OSPF gets recalculated. Fast switching reduces CPU utilization.
To verify CPU utilization, perform the following steps.
Step 1
Verify CPU utilization.
AS5850# show processes cpuCPU utilization for five seconds: 0%/0%; one minute: 0%; five minutes: 0%PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process1 0 88 0 0.00% 0.00% 0.00% 0 Load Meter2 1856 14859 124 0.00% 0.44% 0.28% 0 Exec3 384 63 6095 0.00% 0.09% 0.04% 0 Check heaps4 0 1 0 0.00% 0.00% 0.00% 0 Chunk Manager5 0 1 0 0.00% 0.00% 0.00% 0 Pool Manager6 0 2 0 0.00% 0.00% 0.00% 0 Timers7 0 2 0 0.00% 0.00% 0.00% 0 Serial Backgroun8 52 6 8666 0.00% 0.00% 0.00% 0 RSC Ucode Downlo9 0 2 0 0.00% 0.00% 0.00% 0 DS OIR Handler o10 0 469 0 0.00% 0.00% 0.00% 0 FB manager11 12





