Table Of Contents
Cisco Persistent Storage Device Module Installation and Configuration Note
Understanding How the PSD Works
Format of Datastore Data Files
Configuring and Managing the PSD
PSD Features in Release 1.1(1)
PSD Features in Release 1.0(1)
Installing and Removing the PSD
Configuring the Supervisor for the PSD
Adding the PSD to the Corresponding VLAN
Transfering and Purging Data Files and Datastores
Changing the PSD CLI Passwords
Saving and Restoring Configurations
Configuring the Boot Partitions on the PC Image
Additional PSD Software Commands
User and Privileged EXEC Commands
Standards Compliance Specifications
Berkeley Software Distribution License
Obtaining Technical Assistance
Cisco Persistent Storage Device Module Installation and Configuration Note
WS-SVC-PSD-1
This publication describes how to install and configure the Cisco Persistent Storage Device (PSD) on the Catalyst 6500 series switch. See the "Related Documentation" section for more information about software configuration for the switch.
Note
For translations of the warnings in this publication, see the "Safety Overview" section and refer to the Regulatory Compliance and Safety Information for the Catalyst 6500 series switches.
Contents
This publication consists of these sections:
•
Installing and Removing the PSD
•
Standards Compliance Specifications
•
Obtaining Technical Assistance
Overview
This section describes the Catalyst 6500 and 7600 series PSD, how it operates, and how to manage it, and includes these sections:
•
Understanding How the PSD Works
•
Configuring and Managing the PSD
Understanding How the PSD Works
The Cisco Persistent Storage Device (PSD) provides persistent storage capabilities to Cisco clients, and allows the clients to store data on the PSD's internal hard drive. Release 1.x provides content data records (CDR) backup capabilities for Cisco's Content Services Gateway (CSG). Release 2.0 adds CDR backup capabilities for the Cisco Gateway GPRS Serving Node (GGSN).
A single PSD can support both CSGs and GGSNs. The number of CSGs and GGSNs that can be supported by a single PSD is limited by the traffic load generated by each, as well as the duration of storage that you desire.
Storage and Retrieval on the PSD
Under normal conditions, a Cisco client will send content data records to Mediation Partners' servers. If those servers become unreachable—for any reason—records are then sent to the PSD for safekeeping until contact is re-established with the Charging Gateway (CG). Once contact is re-established, the client retrieves the records from the PSD, and forwards them to the CG.
Storage
Under normal conditions, the PSD provides backup capabilities when necessary—for example, during network outages. The PSD stores the payload from the packet in a queue, and is unaware of the content or format of that data, so that the data can be retrieved exactly as it was sent.
Retrieval
Once the client has determined that it's regular data server is reachable, you issue a CLI command to request that the data files for a given data store be transferred using FTP to a specified URL. You can also restore the configuration to a previously saved version that includes all the IP and application related configuration files. And, you can issue another CLI command to delete transferred files.
Note
The GGSN requires all client Charging Gateways (CG) to send a Node Alive request when they initially startup. The GGSN uses receipt of the Node Alive as an indicator that a CG is now available. Therefore, the GTP' interface on the PSD supports sending Node Alive requests in order to properly support the GGSN.
Datastores
Datastores are locations for a particular client that map to the PSD's hard drive. In this release, you can create up to twenty (20) separate datastores and name them. Twenty datatstores support four MWAM cards in a single chassis with each running five client images, and allows each client to have its own data store. Additionally, datastores have access lists that you can configure to allow specific clients to read and write to specific datastores. Currently, the number of accessors is limited to two (2). The data store access list contains an optional port number in addition to the IP address for each accessor.
When the preferred destination for data becomes unavailable, or during any network outage, data is sent to the PSD and is stored on a "first come, first served" basis. The maximum record storage capability of the PSD is 37 gigabytes, and is allocated as needed.
Format of Datastore Data Files
A data store is comprised of one or more data files. Each data file is composed of multiple records that are constructed of various management related fields, data, and an end-of-record (EOR) indicator. If you need to retrieve data files using FTP (files that are usually corrupt), you will need to understand the format of the data. The following is the format for each record written to a data file:
•
The "Flag" is a 4-byte integer value that indicates the status of the record. This value is used as a 32 bit mask with individual bits having specific meanings. The following bits have assigned values with bit 1 being the least significant (right most bit):
–
Bit 1: Record written—a value of "1" indicates that the record has been completely written to file. A value of "0" indicates that it is an incomplete record, and is probably corrupt.
–
Bit 2: Record acknowledged—a value of "1" indicates that the client has acknowledged that it read the record. A value of "0" indicates that the client has not acknowledged that it read the record.
–
Bit 3:CRC Present—a value of "1" indicates that the Circular Redundancy Check (CRC) field contains a CRC value for the data in this record. A value of "0" indicates the CRC field can be ignored when validating the record.
•
The "CRC" is a 4-byte integer value representing a CRC-32 value.
•
The "Data Length" is a 4-byte integer value representing the length of the Data field.
•
The "Data" is the data the client device has written to the data store.
•
The "EOR" is a one-byte value of 0xFF that indicates the end-of-record.
An End-of-File (EOF) marker follows the last record in a file. This marker is a 4 byte field with a value of 0xFFFFFFFF.
Data files are named with a numeric prefix and a file extension of ".data" (for example, 000000001.data).
Platform and Network Planning
In release 1.x and above, the PSD is implemented as a single linecard that sits in a Catalyst 6500 or 7600 chassis.
The PSD hardware supports the following features:
•
Critical data backup from single failures
•
Internal 40 GB hard disk, with a maximum storage capability of 37 GB.
•
Single module in Catalyst 65xx or 76xx chassis
The typical configuration will be a chassis with up to twenty active co-resident clients and a single PSD serving those clients. The number of PSDs required is determined based on expected network traffic, and the corresponding records that Cisco clients would generate (for example, billing records from a CSG).
Cisco recommends that you consult your sales engineer for specific network planning. You can, however, get a general idea of how many PSDs your network requires by using the following criteria.
To determine the number of PSDs you need, take the maximum value of the following variables:
•
Number of Clients ÷ the maximum number of Datastores per PSD, or
•
Client transmit data rate ÷ the PSD's maximum receive data rate, or
•
(Hours of storage × client transmit data rate) ÷ the max storage per PSD.
Additionally, the following values will be useful to you for network planning:
•
Max datastores per PSD = 20
•
Client transmit rate = 750MB per hour (actual rates will vary)
•
PSD's max receive rate = 640MB per hour
•
Max PSD storage capacity = 37GB
Configuring and Managing the PSD
The PSD is configured and managed by sessioning to the PSD module from IOS on the Supervisor card, or with Telnet when Telnet is enabled. The PSD is then configured using a CLI much like IOS. In addition to a number of administrative and troubleshooting commands on the PSD, there are basic configuration commands that allow you to create and manage datastores on the PSD, and to assign clients that may access (read/write) those datastores. Typically, you would configure a datastore for each client, or pair of redundant clients.
Additionally, you must configure the clients to inform them of the location and presence of a PSD.
New Features in Release 2.0
The following features are new for the PSD Release 2.0:
•
The configuration save command is introduced to save and store PSD configuration files to a specified FTP URL.
•
The datatstore transfer command is introduced to transfer PSD configuration files to a specified FTP URL, and to optionally delete them.
•
The configuration restore command is introduced to restore a PSD using the saved configuration files from the specified FTP URL.
•
The datastore purge command allows you to delete sets of files.
•
The maximum number of data stores is increased to 20 (the equivalent to 4 MWAMs of GGSNs).
•
The same PSD can be shared by a CSG and a GGSN.
PSD Features in Release 1.1(1)
These are the features for the Cisco PSD software release 1.1(1)
•
Support for full capacity of the existing 40GB Hard drive, providing up to 37GB of record storage.
PSD Features in Release 1.0(1)
These are the features for the PSD in software release 1.0(1):
•
The PSD supports up to 3 clients.
•
Call Data Record Backup (CDRB) function to support the Cisco CSG.
•
Data packets (CDRs) are retrievable in the order they were stored on the PSD.
Supported Platforms
•
Catalyst 6500 Switch running IOS
•
Cisco 7600 Internet Router running IOS
Finding Support Information for Platforms and Cisco IOS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.
Supported MIBs, and RFCs
The following sections provide information about the MIBs and RFCs that are supported on the PSD:
MIBs
•
IF-MIB
•
MIB-2
•
HOST-RESOURCE-MIB
RFCs
•
RFC1229—Manage network interfaces
•
RFC1213—Standard network device management
•
RFC1514, RFC2790—Detailed system resources management that provides the ability to see all processes and their utilization. Disk partitions are visible and disk usage is available. You need net-snmp agent for this support.
Front Panel Description
The PSD front panel (see Figure 1) includes a STATUS LED and SHUTDOWN button.
Figure 1 Persistent Storage Device Module
STATUS LED
The STATUS LED indicates the operating states of the PSD. Table 1 describes the LED operation.
SHUTDOWN Button
CautionDo not remove the PSD from the switch until the PSD has shut down completely and the STATUS LED is off. You can corrupt data files, or you can damage the PSD if you remove it from the switch before it completely shuts down.
To avoid corrupting the PSD hard disk, you must correctly shut down the PSD before you remove it from the chassis or disconnect the power. This shutdown procedure is normally initiated by commands entered at the Supervisor engine CLI prompt or the PSD CLI prompt.
If the PSD fails to respond to these commands properly, you can use the SHUTDOWN button on the front panel to initiate the shutdown procedure.
The shutdown procedure may require several minutes. The STATUS LED turns orange when the PSD shuts down.
Conditions That Require Shutdown of a PSD Card
Before you perform any of the following operations, you should shut down the PSD:
•
Physically remove the PSD cards from Cat6500/7600 slots.
•
Manually switch the power off on the Cisco Catalyst 6500 or 7600 boxes.
•
Any other conditions that causes a sudden power interruption of the chassis.
Methods to Shutdown the PSD Card
Use one of the following methods to gracefully power down the PSD cards:
•
In SUP configuration mode, issue the no power enable module mod # command.
•
In SUP exec mode, issue the hw-module module mod # shutdown command.
•
Push the "shutdown" buttom on the faceplate of the PSD card.
•
A software reload of the Supervisor IOS using the reload command in the Supervisor CLI (the whole box reloads).
Specifications
Table 2 describes the specifications for the PSD.
Safety Overview
Safety warnings appear throughout this document in procedures that may harm you if performed incorrectly.
For additional safety information, refer to documents listed in the "Related Documentation" section.
Warning
This warning symbol means danger. You are in a situation that could cause bodily injury. Before you work on any equipment, be aware of the hazards involved with electrical circuitry and be familiar with standard practices for preventing accidents. To see translations of the warnings that appear in this publication, refer to the Regulatory Compliance and Safety Information document that accompanied this device.
Warning
Waarschuwing Dit waarschuwingssymbool betekent gevaar. U verkeert in een situatie die lichamelijk letsel kan veroorzaken. Voordat u aan enige apparatuur gaat werken, dient u zich bewust te zijn van de bij elektrische schakelingen betrokken risico's en dient u op de hoogte te zijn van standaard maatregelen om ongelukken te voorkomen. Voor vertalingen van de waarschuwingen die in deze publicatie verschijnen, kunt u het document Regulatory Compliance and Safety Information (Informatie over naleving van veiligheids- en andere voorschriften) raadplegen dat bij dit toestel is ingesloten.
Warning
Varoitus Tämä varoitusmerkki merkitsee vaaraa. Olet tilanteessa, joka voi johtaa ruumiinvammaan. Ennen kuin työskentelet minkään laitteiston parissa, ota selvää sähkökytkentöihin liittyvistä vaaroista ja tavanomaisista onnettomuuksien ehkäisykeinoista. Tässä julkaisussa esiintyvien varoitusten käännökset löydät laitteen mukana olevasta Regulatory Compliance and Safety Information -kirjasesta (määräysten noudattaminen ja tietoa turvallisuudesta).
Warning
Attention Ce symbole d'avertissement indique un danger. Vous vous trouvez dans une situation pouvant causer des blessures ou des dommages corporels. Avant de travailler sur un équipement, soyez conscient des dangers posés par les circuits électriques et familiarisez-vous avec les procédures couramment utilisées pour éviter les accidents. Pour prendre connaissance des traductions d'avertissements figurant dans cette publication, consultez le document Regulatory Compliance and Safety Information (Conformité aux règlements et consignes de sécurité) qui accompagne cet appareil.
Warning
Warnung Dieses Warnsymbol bedeutet Gefahr. Sie befinden sich in einer Situation, die zu einer Körperverletzung führen könnte. Bevor Sie mit der Arbeit an irgendeinem Gerät beginnen, seien Sie sich der mit elektrischen Stromkreisen verbundenen Gefahren und der Standardpraktiken zur Vermeidung von Unfällen bewußt. Übersetzungen der in dieser Veröffentlichung enthaltenen Warnhinweise finden Sie im Dokument Regulatory Compliance and Safety Information (Informationen zu behördlichen Vorschriften und Sicherheit), das zusammen mit diesem Gerät geliefert wurde.
Warning
Avvertenza Questo simbolo di avvertenza indica un pericolo. La situazione potrebbe causare infortuni alle persone. Prima di lavorare su qualsiasi apparecchiatura, occorre conoscere i pericoli relativi ai circuiti elettrici ed essere al corrente delle pratiche standard per la prevenzione di incidenti. La traduzione delle avvertenze riportate in questa pubblicazione si trova nel documento Regulatory Compliance and Safety Information (Conformità alle norme e informazioni sulla sicurezza) che accompagna questo dispositivo.
Warning
Advarsel Dette varselsymbolet betyr fare. Du befinner deg i en situasjon som kan føre til personskade. Før du utfører arbeid på utstyr, må du vare oppmerksom på de faremomentene som elektriske kretser innebærer, samt gjøre deg kjent med vanlig praksis når det gjelder å unngå ulykker. Hvis du vil se oversettelser av deadvarslene som finnes i denne publikasjonen, kan du se i dokumentet Regulatory Compliance and Safety Information (Overholdelse av forskrifter og sikkerhetsinformasjon) som ble levert med denne enheten.
Warning
Aviso Este símbolo de aviso indica perigo. Encontra-se numa situação que lhe poderá causar danos físicos. Antes de começar a trabalhar com qualquer equipamento, familiarize-se com os perigos relacionados com circuitos eléctricos, e com quaisquer práticas comuns que possam prevenir possíveis acidentes. Para ver as traduções dos avisos que constam desta publicação, consulte o documento Regulatory Compliance and Safety Information (Informação de Segurança e Disposições Reguladoras) que acompanha este dispositivo.
Warning
¡Advertencia! Este símbolo de aviso significa peligro. Existe riesgo para su integridad física. Antes de manipular cualquier equipo, considerar los riesgos que entraña la corriente eléctrica y familiarizarse con los procedimientos estándar de prevención de accidentes. Para ver una traducción de las advertencias que aparecen en esta publicación, consultar el documento titulado Regulatory Compliance and Safety Information (Información sobre seguridad y conformidad con las disposiciones reglamentarias) que se acompaña con este dispositivo.
Warning
Varning! Denna varningssymbol signalerar fara. Du befinner dig i en situation som kan leda till personskada. Innan du utför arbete på någon utrustning måste du varamedveten om farorna med elkretsar och känna till vanligt förfarande för att förebygga skador. Se förklaringar av de varningar som förkommer i denna publikation i dokumentet Regulatory Compliance and Safety Information (Efterrättelse av föreskrifter och säkerhetsinformation), vilket medföljer denna anordning.
Warning
Only trained and qualified personnel should be allowed to install, replace, or service this equipment.
Software Requirements
Table 3 lists the PSD software versions supported by Cisco IOS software.
Hardware Requirements
Table 4 lists the PSD hardware versions supported by Cisco IOS software.
Table 4 PSD Supported Hardware Version
Cisco IOS SoftwareSupervisor Engine 2 with an MSFC2 or Supervisor 720 with an MSFC3
Required Tools
Note
Before installing the PSD, you must install the Catalyst 6500 series switch chassis, and at least one Supervisor engine. For information on installing the switch chassis, refer to the Catalyst 6000 Family Installation Guide.
These tools are required to install the PSD in the Catalyst 6500 series switch:
•
Flat-blade screwdriver
•
Phillips-head screwdriver
•
Wrist strap or other grounding device
•
Antistatic mat or antistatic foam
Whenever you handle the PSD, always use a wrist strap or other grounding device to prevent electrostatic discharge (ESD).
Installing and Removing the PSD
Warning
During this procedure, wear grounding wrist straps to avoid ESD damage to the card. Do not directly touch the backplane with your hand or any metal tool, or you could shock yourself.
All the Catalyst 6500 series family switches support hot swapping, which allows you to install, remove, replace, and rearrange modules without turning off the system power. For more information on removing the PSD from a switch, see the "Removing a Module" section.
CautionDo not remove the PSD from the switch until the PSD has shut down completely and the STATUS LED is orange. You can corrupt data files, or damage the PSD if you remove it from the switch before it completely shuts down.
When the system detects that a module has been installed or removed, the system automatically runs diagnostic and discovery routines, acknowledges the presence or absence of the module, and resumes system operation.
To install and use the PSD, you need to complete the following actions:
•
Perform the initial installation by placing the PSD in a switch.
•
At the switch CLI, session to the PSD CLI and provide a basic configuration.
•
Test network conncectivity by pinging an external client.
This section describes how to install and verify the operation of the PSD in the Catalyst 6500 family switch, and contains the following sections:
Slot Assignments
The Catalyst 6509 switch chassis has nine slots. The module can occupy any slot in the Catalyst 6500 series chassis.
Note
The Catalyst 6509-NEB switch has vertical slots numbered 1 to 9 from right to left. Install the modules with the component side facing to the right.
•
Slot 1 is reserved for the Supervisor engine.
•
Slot 2 can contain an additional redundant Supervisor engine in case the Supervisor engine in slot 1 fails.
•
If a redundant Supervisor engine is not required, slots 2 through 6 on the 6-slot chassis, (slots 2 through 9 on the 9-slot chassis and slots 2 through 13 on the 13-slot chassis) are available for switching modules, or other application modules.
•
Install switching-module filler plates, which are blank switching-module carriers, in the empty slots to maintain consistent airflow through the switch chassis.
Removing a Module
This section describes how to remove an existing module from a chassis slot.
Warning
During this procedure, wear grounding wrist straps to avoid ESD damage to the card. Do not directly touch the backplane with your hand or any metal tool, or you could shock yourself.
Warning
Before you install, operate, or service the system, read the Site Preparation and Safety Guide. This guide contains important safety information you should know before working with the system.
Warning
Invisible laser radiation may be emitted from disconnected fibers or connectors. Do not stare into beams or view directly with optical instruments.
To remove a Supervisor engine or module from the chassis, perform these steps:
Step 1
Disconnect any network interface cables attached to the Supervisor engine or module.
Note
The PSD does not have any interface cable connections. It communicates throught the chassis backplane.
Step 2
Verify that the captive installation screws on all of the modules in the chassis are tight.
This action ensures that the space created by the removed module is maintained.
Note
If the captive installation screws are loose, the electromagnetic interference (EMI) gaskets on the installed modules will push the modules toward the open slot, reducing the opening size and making it difficult to install the replacement module.
Step 3
Loosen the two captive installation screws on the Supervisor engine or module.
Step 4
Depending on the orientation of the slots in the chassis (horizontal or vertical), perform one of the following sets of steps:
Horizontal slots
a.
Place your thumbs on the left and right ejector levers, and simultaneously rotate the levers outward to unseat the module from the backplane connector.
b.
Grasp the front edge of the module and slide the module part of the way out of the slot. Place your other hand under the module to support the weight of the module. Do not touch the module circuitry.
Vertical slots
a.
Place your thumbs on the ejector levers located at the top and bottom of the module, and simultaneously rotate the levers outward to unseat the module from the backplane connector.
b.
Grasp the edges of the module, and slide the module straight out of the slot. Do not touch the module circuitry.
Step 5
Place the module on an antistatic mat or antistatic foam, or immediately reinstall it in another slot.
Step 6
If the slot is to remain empty, install a module filler plate to keep dust out of the chassis and to maintain proper airflow through the chassis.
Warning
Blank faceplates (filler panels) serve three important functions: they prevent exposure to hazardous voltages and currents inside the chassis; they contain electromagnetic interference (EMI) that might disrupt other equipment; and they direct the flow of cooling air through the chassis. Do not operate the system unless all cards and faceplates are in place.
Installing a Module
This section describes how to install modules in the Catalyst 6500 series and Catalyst 6000 family switches.
CautionTo prevent ESD damage, handle modules by the carrier edges only.
Warning
During this procedure, wear grounding wrist straps to avoid ESD damage to the card. Do not directly touch the backplane with your hand or any metal tool, or you could shock yourself.
Warning
Invisible laser radiation may be emitted from disconnected fibers or connectors. Do not stare into beams or view directly with optical instruments.
Warning
Before you install, operate, or service the system, read the Site Preparation and Safety Guide. This guide contains important safety information you should know before working with the system.
To install a Supervisor engine or module in the chassis, perform these steps:
Step 1
Choose a slot for the Supervisor engine or module.
Step 2
Verify that there is enough clearance to accommodate any interface equipment that you will connect directly to the Supervisor engine or module ports. If possible, place modules between empty slots that contain only module filler plates.
Step 3
Verify that the captive installation screws are tightened on all modules installed in the chassis.
This action ensures that the EMI gaskets on all modules are fully compressed in order to maximize the opening space for the new module or the replacement module.
Note
If the captive installation screws are loose, the EMI gaskets on the installed modules will push adjacent modules toward the open slot, reducing the opening size and making it difficult to install the replacement module.
Step 4
Remove the module filler plate by removing the two Phillips pan-head screws from the filler plate.
To remove a module, refer to "Removing a Module" section.
Step 5
Fully open both ejector levers on the new or replacement module. (See Figure 2.)
Figure 2 Positioning the Module in a Horizontal Slot Chassis
Step 6
Depending on the orientation of the slots in the chassis (horizontal or vertical), perform one of these sets of steps:
Horizontal slots
a.
Position the Supervisor engine or module in the slot. (See Figure 2.) Make sure that you align the sides of the module carrier with the slot guides on each side of the slot.
b.
Carefully slide the Supervisor engine or module into the slot until the EMI gasket along the top edge of the module makes contact with the module in the slot above it and both ejector levers have closed to approximately 45 degrees in relation to the module faceplate. (See Figure 3.)
Figure 3 Clearing the EMI Gasket in a Horizontal Slot Chassis
c.
Using the thumb and forefinger of each hand, grasp the two ejector levers and press down to create a small (0.040 inch [1 mm]) gap between the module's EMI gasket and the module above it. (See Figure 3.)
CautionDo not press down too hard on the levers because they can bend and be damaged.
d.
While pressing down, simultaneously close the left and right ejector levers to fully seat the Supervisor engine or module in the backplane connector. The ejector levers are fully closed when they are flush with the module faceplate. (See Figure 4.)
Figure 4 Ejector Lever Closure in a Horizontal Slot Chassis
Note
Failure to fully seat the module in the backplane connector can result in error messages.
e.
Tighten the two captive installation screws on the Supervisor engine or module.
Note
Make sure that the ejector levers are fully closed before tightening the captive installation screws.
Vertical slots
a.
Position the Supervisor engine or switching module in the slot. (See Figure 5.) Make sure that you align the sides of the switching module carrier with the slot guides on the top and bottom of the slot.
Figure 5 Positioning the Module in a Vertical Slot Chassis
b.
Carefully slide the Supervisor engine or module into the slot until the EMI gasket along the right edge of the module makes contact with the module in the slot adjacent to it and both ejector levers have closed to approximately 45 degrees with respect to the module faceplate. (See Figure 6.)
c.
Using the thumb and forefinger of each hand, grasp the two ejector levers and exert a slight pressure to the left, moving the module approximately 0.040 inches (1 mm) to create a small gap between the module's EMI gasket and the module adjacent to it. (See Figure 6.)
Figure 6 Clearing the EMI Gasket in a Vertical Slot Chassis
CautionDo not exert too much pressure on the ejector levers. They will bend and be damaged.
d.
While pressing on the ejector levers, simultaneously close them to fully seat the Supervisor engine or module in the backplane connector. The ejector levers are fully closed when they are flush with the module faceplate. (See Figure 7.)
Figure 7 Ejector Lever Closure in a Vertical Slot Chassis
e.
Tighten the two captive installation screws on the module.
Note
Make sure that the ejector levers are fully closed before tightening the captive installation screws.
Note
For information regarding installation details for the Cisco 7600 Internet Router, go to the following URL: http://www.cisco.com/en/US/products/hw/routers/ps368/products_module_installation_guide_book09186a008007cd9d.html
Verifying the Installation
This section describes how to verify the PSD installation.
Cisco IOS Software
To verify that the system acknowledges the new module and has brought it online, enter the show module [mod-num | all ] command.
This example shows the output of the show module command:
Router#show moduleMod Ports Card Type Model Serial No.--- ----- -------------------------------------- ------------------ -----------1 2 Catalyst 6000 supervisor 2 (Active) WS-X6K-SUP2-2GE SAL06396QLA2 2 Catalyst 6000 supervisor 2 (Standby) WS-X6K-SUP2-2GE SAL061800UB3 48 48 port 10/100 mb RJ45 WS-X6348-RJ-45 SAL06200V6W4 3 Network Analysis Module WS-SVC-NAM-1 SAD064403UB5 3 Persistent Storage Device WS-SVC-PSD-1 SAD060301SU6 3 Persistent Storage Device WS-SVC-PSD-1 SAD060301SVMod MAC addresses Hw Fw Sw Status--- ---------------------------------- ------ ------------ ------------ -------1 0006.d65b.e1bc to 0006.d65b.e1bd 3.10 6.1(3) 7.5(0.94) Ok2 0005.7485.bde8 to 0005.7485.bde9 3.7 6.1(3) 7.5(0.94) Ok3 0009.1243.23cc to 0009.1243.23fb 6.1 5.4(2) 7.5(0.94) Ok4 0002.7ee4.b046 to 0002.7ee4.b04d 1.0 7.2(1) 2.2(1a) Ok5 00e0.b0ff.3630 to 00e0.b0ff.3637 0.101 7.5(0.61) 1.0(1) Ok6 00e0.b0ff.3530 to 00e0.b0ff.3537 0.101 7.5(0.61) 1.0(1) OkMod Sub-Module Model Serial Hw Status--- --------------------------- --------------- --------------- ------- -------1 Policy Feature Card 2 WS-F6K-PFC2 SAL06396LVK 3.3 Ok1 Cat6k MSFC 2 daughterboard WS-F6K-MSFC2 SAL06365RJM 2.5 Ok2 Policy Feature Card 2 WS-F6K-PFC2 SAL061735WF 3.2 Ok2 Cat6k MSFC 2 daughterboard WS-F6K-MSFC2 SAL06131NAL 2.3 OkMod Online Diag Status--- -------------------1 Pass2 Pass3 Pass4 Pass5 Pass6 PassWhen the PSD initially boots, by default it runs a partial memory test. To perform a full memory test, enter the hw-module module module_number reset device:partition mem-test-full command.
A full memory test takes more time to complete than a partial memory test depending on the memory size. Table 5 lists the memory test time and approximate boot time for a partial memory test.
You also can use the hw-module module module_number mem-test-full command in a Cisco IOS system. This example shows how to do a full memory test for module 4:
Router(config)# hw-module module 4 mem-test-full
Note
Cisco recommends that you run a full online diagnostic when you boot your PSD for the first time. You can use the following commands to perform this task:
router# configure terminal diag level completeConfiguring the PSD
See the following sections for configuration tasks for the PSD. Each task in the list is identified as either required or optional.
•
Configuring the Supervisor for the PSD
•
"Adding the PSD to the Corresponding VLAN" section
•
"Initial PSD Configuration" section
•
"Transfering and Purging Data Files and Datastores" section
•
"Administering the PSD" section
There are several external interfaces that are available to configure and manage the PSD. They include the following:
MP (Maintenance Partition) Command Line Interface.
When you boot the MP image (from compact flash), and login to the card, you are presented with a command line interface that allows you to perform activities such as administration tasks, configuration, troubleshooting, and to upgrade the application image.
AP (Application Partition) Command Line Interface.
When you boot the AP image from the hard disk, and login to the card, you are presented with a command line interface that is similar to IOS. The AP commands allow you to configure the PSD, and to display the status of the PSD.
There is a specific subset of the PSD CLI commands for the following tasks:
•
Taking the PSD into service
•
Taking the PSD out of service
•
Creating a data store for a client
•
Deleting a data store
•
Showing PSD related status and datastore information
•
Enabling access to a datastore
•
Disabling access to a datastore
IOS Supervisor Command Line Interface.
This is the command line provided by the IOS image on the Supervisor card. There are IOS commands that allow you to interact with the PSD card. The Supervisor CLI also provides commands by which the CSG or GGSN is configured to communicate with the PSD card.
SNMP interfaces. The SNMP agent on the PSD can be configured and activated. When activated, you can then define a read community string. A network agent with connectivity to the PSD, and knowledge of the SNMP read community string, may issue SNMP get/walk type requests to manage and monitor the PSD.
Configuring the Supervisor for the PSD
Adding the PSD to the Corresponding VLAN
By default, the PSD is in trunking mode with native VLAN 1.
Note
By default the PSD will use vlan1 for its network traffic; however, you can configure the PSD to use another vlan with the persistent-store module command.
Initial PSD Configuration
Before you can use the PSD for data storage, you must log into the PSD root account and configure the following:
•
IP address
•
Subnet mask
•
IP broadcast address
•
IP host name
•
Default gateway
•
Domain name
•
Datastore Creation and Access Control
•
Inservice
•
If applicable, the DNS name server
•
If you are using an external SNMP manager to communicate with the PSD, configure the following:
–
SNMP MIB variables
–
Access control for the SNMP agent
–
System group settings on the PSD
To configure these required parameters for the PSD, follow these steps:
Step 1
Enter this command to verify that the PSD is installed and that the power is on:
Router# show module modStep 2
Establish a console session with the PSD by entering:
Router# session slot module_number processor 1
Note
Sometimes attempts to session into the PSD console from the supervisor fail immediately after startup, or immediately after a PSD restart, even though the "module online" message for the PSD blade has appeared at the supervisor. Always wait 60 seconds after the "module online" message appears on the supervisor for the PSD module before you attempt to session into the PSD from the supervisor.
The hardware and firmware of the PSD performs self-checks on boot up, then notifies the supervisor that the PSD module is online. This results in the "module online" message at the supervisor console. Concurrently, the firmware starts the PSD application on the PSD processors. The PSD application requires about 50 seconds to initialize itself, and the application does not accept session requests from the supervisor until this initialization is complete.
Step 3
At the login prompt, type root to log in to the root account.
Step 4
At the password prompt, type cisco as the root password.
Note
If you have not changed the password from the factory-set default, a warning message displays. If you decide to change the password from the default, see the "Changing the PSD CLI Passwords" section for more information.
Step 5
Configure the IP address and subnet mask by entering:
root@localhost# ip address ip-address subnet-maskStep 6
Configure the IP broadcast address by entering:
root@localhost# ip broadcast broadcast-addressStep 7
Configure the IP host name used in the CLI prompt, show commands, and log messages by entering:
root@localhost# ip host [host-name]Step 8
Configure the default gateway by entering:
root@localhost# ip gateway default-gateway
Note
This gateway should always be the IP address of VLAN1 on the Supervisor.
Step 9
Configure the domain name for the PSD by entering:
root@localhost# ip domain domain-nameStep 10
Configure one or more IP addresses as DNS name servers by entering:
root@localhost# ip nameserver ip-address [ip-address2] [ip-address-3]
Note
The ip nameserver command can accept up to a maximum of three name server addresses (two addresses are optional).
Step 11
Verify the PSD configuration by entering:
root@localhost# show ipStep 12
Configure a datastore for a Cisco client by entering:
root@localhost# datastore create ciscoroot@localhost# datastore access enable cisco 1.2.3.4 port numberroot@localhost# show datastore all or ciscoStep 13
Put the PSD inservice by entering:
root@localhost# in-service
Note
The following steps are optional configuration tasks:
Step 14
Configure the SNMP syslocation MIB variable by entering:
root@localhost# snmp-agent location-string
Note
The MIB variables in Step 13 and Step 14 must be valid DisplayString texts, each with a maximum length of 64 characters.
Step 15
Set the SNMP sysContact MIB variable by entering:
root@localhost# snmp-contact contact-stringStep 16
Set the SNMP sysName MIB variable by entering:
root@localhost# snmp-name name-string
Note
You can delete the SNMP location, SNMP contact, or SNMP name by entering the respective command without any parameters.
Step 17
Set the SNMP agent community string parameter password for read-write access by entering:
root@localhost# snmp-community community-string
Note
Clear the SNMP community string with the snmp delete community command.
Step 18
Verify the SNMP access controls and settings by entering:
root@localhost# show snmpStep 19
Enable telnet access to your PSD module from a remote location by entering:
root@localhost# telnet-server enableAfter completing this configuration, the PSD is ready to use with other Cisco clients.
This example shows how to configure the PSD:
Router# session slot 8 processor 1The default escape character is Ctrl-^, then x.You can also type 'exit' at the remote prompt to end the sessionTrying 127.0.0.81 ... OpenCisco Persistent Storage (WS-SVC-PSD-1)login: rootPassword:Cisco Persistent Storage Device (WS-SVC-PSD-1) Console, 1.0(1)Copyright (C) 2002-2003 by cisco Systems, Inc.WARNING! Default password has not been changed!root@localhost.localdomain# ip address 192.18.12.221 255.255.255.192root@localhost.localdomain# ip host psd1root@psd1.localdomain# ip gateway 192.18.12.193root@psd1.localdomain# ip domain cisco.comroot@psd1.cisco.com# ip nameserver 161.44.11.21root@psd1.cisco.com# show ipIP address: 192.18.12.221Subnet mask: 255.255.255.192IP Broadcast: 192.18.255.255DNS Name: psd1.cisco.comDefault Gateway: 192.18.12.193Nameserver(s): 161.44.11.21FTP Server: disabledTelnet Server: disabledroot@psd1.cisco.com# snmp-agent enableroot@psd1.cisco.com# snmp-agent community readroot@psd1.cisco.com# snmp-agent location "Cisco Lab, Building 10 Lab 4"root@psd1.cisco.com# snmp contact "Lab Admin, 555-1212"root@psd1.cisco.com# show snmp-agentSNMP Agent: psd1.cisco.comstatus: enabledip address: 172.18.12.221community string: readSNMPv1: supportedSNMPv2c: supportedSNMPv3: not-supportedsysDescr: Linux psd1.cisco.com 2.4.18 #1 SMP Wed Jul 16 11:18:19 EDT 2003 i686sysObjectID: OID: enterprises.ucdavis.ucdSnmpAgent.linuxsysContact: Lab Admin, 555-1212sysName: not-configuredsysLocation: Cisco Lab, Building 10 Lab 4root@psd1.cisco.com#
CautionThe PSD does not provide a dynamic method to save and restore your configuration. Additionally, if you need to change PSD modules in the Catalyst chassis, you will need to configure the new module. Cisco recommends that you perform the following procedure to save and store your PSD configuration details:
Step 1
Session into the PSD:
router# session slot slot_num processor processorStep 2
Issue the configuration save command.
Note
You can also issue the following show commands, and copy and paste the various show output into your preferred text editor:
root@localhost.localdomain# show ip
root@localhost.localdomain# show snmp-agent
root@localhost.localdomain# show datastore all .
Save this file in a secure location for backup purposes.
Note
For specific information on how to configure the PSD to communicate with the CSG, refer to the "PSD Configuration for Content Services Gateway" chapter in the Cisco Content Service Gateway Installation and Configuration Guide.
Transfering and Purging










