Gebruiksaanwijzing /service van het product 5500 van de fabrikant Panasonic
Ga naar pagina of 96
Identity Engines Ignition Server Ethernet Routing Switc h 8600 8300 1600 5500 5600 4500 2500 Engineering > Switch User Authentication using Identity Engines Ignition Server Technical Configuration Guide Enterprise Networking Solutions Document Date: October 2009 Document Number: NN48500-589 Document Version: 1.
__________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ 1 Nortel is a recognized lea der in delivering co mmunications cap abilities that enhance the human experience, ignite and po wer global commerce, an d se cure and prote ct the world’s most critical information.
__________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ 2 Abstract Revision Control No Date Version Revised by Remarks 1 10/09/2009 1.
__________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ 3 1.1 RADIUS S UPPORT ON N ORTEL S WITCHES ..........................................................................
__________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ 4 Conventions This section describe s the text, image, and comma nd conventions used in this document. Symbols: Tip – Highlights a configura tion or technical tip.
__________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ 5 1. Overview: RADIUS User Authentication using Identify Engines This document provides the frame work for implem enting user Authenticati on, Authorization, and Accounting for Nortel switches.
__________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ 6 1.3 User Authentication using ERS5600, ERS5500, ERS4500, or ERS2500 The ERS5600, ERS5500, ERS4500, an d ERS250 0 each support two different user a ccess levels which are read-only or read-write.
2. ERS8600 Switch Configuration Example For this configuration example, we will enable RADIUS user authenticatio n on ERS8600-1 using the out-of-band managem ent port.
__________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ 8 2.1 Part 1: Basic AAA Configuation 2.1.1 ERS8600 Configuration Assuming we are usi ng the out-of-band management port.
__________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ 9 2.1.2 ERS 8600 Switch: Verify Operations 2.
2.1.3 IDE Setup 2.1.3.1 Configure an Outbound Attribute on Ignition Serv er for VLAN The following chart display s the outbound attr ibute values required by the ERS8600 for each access level for RADIUS vendo r identifier 1584 (Bay Networks) attribute type 192.
IDE Step 2 – Go to IDE Step 3 – Via the window, type in a name for the attri bute to be used for access priority (i.e. ERS8600-Access-Priori ty as used in this example), click the radio button, select via and via .
IDE Step 4 – Go to IDE Step 5 – Using the Outbound Attribute create d in Step 3, we will first add an attribute value of 1 for read-only-acc ess. Start by entering a name v ia the window (i.
IDE Step 6 – Select the Outbound Attributes na me created in Step 3 (i.e. ERS8600-Access- Priority as used in this example ) via the pull down menu. In the window, enter 1 (i.
IDE Step 7 – Go to again to create the outboun d attribute for rea d-write -access. Using the Outbound Attribute c reated in Step 3, we will add an attribute v alue of 5 for read- write-access.
IDE Step 8 –Select the Outbound Attributes name created in Step 3 (i.e. ERS8600-Access- Priority as used in this example ) via the pull down menu. In the windo w , enter 5 (i.
IDE Step 9 – Go to again to create the outbound a ttribute for read- write-all-access. Usi ng the Outbound Attribute created in Step 3, we will add an attribute value of 6 for read- write-all-access.
IDE Step 10 –Select the Outbound Attributes nam e created in Step 3 (i.e. E RS8600-Access- Priority as used in this example ) via the pull down menu. In the windo w , enter 6 (i.e. value of 6 signifies r ead-write-all- access). Click on twice when done.
2.1.3.2 Add Users For this configuration example, we will add the following users. User Name Access Level 8600ro Read-Only-A ccess 8600rw Read-Write-A ccess 8600rwa Read-Write-A ll-Access IDE Step 1 .
IDE Step 2 – Enter the user name for read-only -access via (i.e. 8600ro as used in this example) and e nter the pass word for this user via and . Click on when done.
IDE Step 3 – Repeat s tep 2 again by clicking on Ne w to add the read-write-acc ess user. Enter the user name for read- write-access via (i.e. 8600r w as used in this example) and enter the pass word for this user via and .
IDE Step 4 – Repeat step 2 for the final time by clicking on New to add the read -write-all- access user. Enter the user name fo r read-write-a ll-access via (i.e. 8600rwa as used in this example) and enter the pass word for this user via and . Click on when done.
2.1.3.3 Add an Access Policy IDE Step 1 – Go to Right-click R and select . Enter a policy name (i.e. ERS8600-Access as used in this example) and click on when do ne __________ ___________ __________.
IDE Step 2 – Click on the policy w e just created, i.e. ERS8600-Access, and click on via the tab __________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ ____.
IDE Step 3 – Under w indow, select __________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ 2 4.
IDE Step 4 – Go to the and click on __________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ 2 5.
IDE Step 5 – Check off the and click on when done. __________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ 2 6.
IDE Step 6 – Go to the tab and click on __________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ 2 7.
IDE Step 7 – Once the windo w pops up, click on First, we will add a rule for read-o nly-access. When the window pops up , w e w ill na me t he rule as shown below __________ ___________ ___________.
IDE Step 8 – Click on to add a new constraint __________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ 2 9.
IDE Step 9 – For this example, we are simply going to look for the read -only-user user-i d. From , select and scroll do wn and select . Select wi t h of and enter the read-only -access user id, i.e. 8600ro as us ed in this example, in the window as shown belo w.
IDE Step 10 – Via , select . From the window , select the output attribute we created previously named and click on the less-than arro w key to move the attribute to t he w indow __________ ________.
IDE Step 11 – Next, we will add a rule for read-write-access. Start by clicking on and whe n t he windo w pops up, add an appropriate nam e for this rule, i.
IDE Step 12 – Click on to add a new constraint __________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ 3 3.
IDE Step 13 – For this example, w e are simply going to look for the read- write-access u ser- id. From , select and scroll do wn and select . Select wi t h of and enter the read -only-access us er id, i.e. as used in this example, in the window as shown belo w.
IDE Step 14 – Via , select . From the windo w, select the output attribute we created previously named and click on the less-than arr ow key to move the attribute to t he w indow __________ ________.
IDE Step 15 – Finally, we w i ll add a rule for read-write-all-acc ess. Start by clicking on and when the windo w pops up, add an appropriate name for this rule, i.
IDE Step 16 – Click on to add a new constraint __________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ 3 7.
IDE Step 17 – For this example, we are simply going to look for the read- write-all-access user-id. From , select and scroll down and select . Select wi t h of and enter the rea d-only-access user id, i.e. as used in this example, in the windo w as shown belo w.
IDE Step 18 – Via , select . From the windo w, select the output attribute we created above na med and click on the less-than arrow key to move the attribute to the wi n d o w __________ ___________.
IDE Step 19 – When completed, y ou can view the complete policy by clicking on the button __________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ ___________.
2.1.3.4 Add the Nortel ERS8600-1 s witch as an RADIUS Authenticator For Ignition Server to process t he No rtel switch RADIUS re quests, each switch must be ad ded as an Authenticator.
IDE Step 2 – Go to -> -> and click on __________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ 4 2.
IDE Step 3 – Enter the settings as shown below making sure y ou select the policy we created previously named via . Leave and checked. Click on when done .
2.1.4 Verification 2.1.4.1 Verify User Authentication You can test user authentication for the ERS8600 users configu red on IDE by entering the user name and password. Step 1 – Via Ignition Dashbo ard, select the IP address of the Ignition Server, click on the tab, go to and select the tab.
Via Dashboard, verify the following information: Option Verify Results If successful, should be displayed 2.1.4.2 Verify user authentication from ERS s witch You can view the authentication detail s via Igni tion Dashboard which prov ides extensive de tails about the device or user.
__________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ 4 6.
__________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ 4 7 At minimum, verify the following items: Option Verify Authentication Result If successful, should be displayed.
__________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ 4 8 2.2 Part 2: ERS8600 Configuration with Specific Commands Disab.
2.2.2 IDE Setup 2.2.2.1 Configure Outbound attributes to de ny ERS8600 CLI commands Using the same base configuratio n from the previous step, we will simple add the CLI commands we wish to deny to the read-write user. In this example, this will apply only to the user .
IDE Step 3 – Via the window, type in a name for the attri bute to be used to restrict CLI commands (i.e. 8600-Command -Access as used in this ex ample), click the radio button, select via and via . Click on w hen done IDE Step 4 – Go to one more time Via the w indo w, type in a name for the attribute to be used to list the CLI commands (i.
IDE Step 5 – Go to IDE Step 6 – Using the Outbound Attribute crea ted in Step 3, we will add a value of 0 to restrict CLI command acces s. Start by entering a nam e via the window (i.
IDE Step 7 – Select the Outbound Attributes name crea ted in Step 3 (i.e. ERS8600- Command-Access as used in this e xample) via the pull down menu. In the window, enter 0 (i.e. value of 0 signifies CLI command restriction). Click on twice when done.
IDE Step 8 – Go to again to create the outbound attribute for de ny access to the CLI co mmand ‘config qos’. Using the Outbound Attribute created in Step 4, we will add a string value of “config qos”. Start by entering a name via the w indo w (i.
IDE Step 9 – Select the Outbound Attributes name crea ted in Step 4 (i.e. ERS8600- Command-List as use d in this example) v ia the pull down menu. In the wi nd o w, e n t e r (i.e. this is the CLI command we wish to restrict). Click on twice w hen done.
IDE Step 10 – Go to again to create the outbound attribute for de ny access to the CLI comm and ‘config filter’. Using the Outbound Attribute created in Step 4, we will add a string value of “config filter”. Start by entering a name via the w indo w (i.
IDE Step 11 – Select th e Outbound Attributes name created in Step 4 (i.e. ERS8600- Command-List as use d in this example) v ia the pull down menu. In the wi n d o w, e nt er (i.e. this is the CLI command we wish to restrict). Click on twice w hen done.
2.2.2.2 Modify the Authorization Policy for the ERS860 0 read-write user IDE Step 1 – Click on the policy created from the prev ious example, i.e. ERS8600-Access, click on the tab, select the via th.
IDE Step 2 – Make sure the read- write-access rule is selected and move all three RADIUS attribute values we just created from the prev ious step from the windo w to the w indow __________ _________.
IDE Step 3 – When compl eted, you can vie w the complete policy by clicking on the button __________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ ___________.
__________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ 6 0 2.2.3 Verification Connect to ERS8600 by using telnet with the read-write user accou nt.
3. ERS5600 Switch Configuration Example For this configuration exa mple, we will enable RADIUS user authenticatio n on ERS500-1 using the switch management po rt.
__________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ 6 2 3.1 ERS5600 Configuration 3.1.1 Enable RADIUS Up to two RADIUS servers are supported on the ERS 5600, 55 00, 4500, or 2500 seri es switches.
3.2 IDE Setup 3.2.1 Configure an Outbound Attribute on Ignition Server for Service-Type The following chart display s the outbound attr ibute values required by the ERS5600, ERS5500, ERS4500, or ERS2500 for each access level usin g RADIUS attribute type 6 (Service-Typ e).
IDE Step 2 – Via the window, type in a name for the attri bute to be used for access priority (i.e. Service-type-ERS as used in this example), click the radio button and select .
IDE Step 5 – Using the Outbound Attribute created in Step 2, we will first add a value of 7 (NAS Prompt) for read -only-access. Start by entering a name via the w indo w (i.
IDE Step 6 – Select the Outbo und Attributes name crea ted in Step 3 (i.e. Service-ty pe-ERS as used in this example) v ia the pull down menu. In the windo w , enter 7 (i.e. value of 7 signifies NAS Pr ompt for read-only - access). Click on twice when done.
IDE Step 7 – Go to again to create the outboun d attribute for rea d-write -access. Using the Outbound Attribute c reated in Step 2, we will add a value of 6 for read- write-access.
IDE Step 8 –Select the Outboun d Attributes name created in Step 2 (i.e. Service-ty pe-ERS as used in this example) v ia the pull down menu. In the window, enter 6 (i.e. v alue of 6 signifies Administrativ e for read- write-access). Click on twice when done.
3.2.2 Add Users For this configuration exa mple, we will add the following users User Name Access Level 5600ro Read-Only-A ccess 5600rwa Read-Write-A ll-Access IDE Step 1 – Star t by going to and cl.
IDE Step 2 – Enter the user name for read-only -access via (i.e. 5600ro as used in this example) and e nter the pass word for this user via and . Click on when done.
IDE Step 3 – Repeat s tep 2 again by clicking on Ne w to add the read-write-acc ess user. Enter the user name for read- write-access via (i.e. 5600r w as used in this example) and enter the pass word for this user via and .
3.2.3 Add Access Policy IDE Step 1 – Go to Right-click R and select . Enter a policy name, i.e. ERS-access as used in this example and click on when done __________ ___________ ____________ ________.
IDE Step 2 – Click on the policy w e just created, i.e. ERS-access, and click on via the tab __________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ ________.
IDE Step 3 – Under w indow, select __________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ 7 4.
IDE Step 4 – Go to the and click on __________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ 7 5.
IDE Step 5 – Check off the and click on when done. __________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ 7 6.
IDE Step 6 – Go to the tab and click on __________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ 7 7.
IDE Step 7 – Once the windo w pops up, click on First, we will add a rule for read-only . When the window pops up, we will name the rule as shown below __________ ___________ ____________ __________.
IDE Step 8 – Click on to add a new constraint __________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ 7 9.
IDE Step 8 – For this example, we are simply going to look for the read -only-user user-i d. From , select and scroll do wn and select . Select wi t h of and enter the read-only -access user id, i.e. 5600ro as us ed in this example, in the window as shown belo w.
IDE Step 9 – Via , select . From the window, select the output attribute we created above named and click on the less-than arrow key to move the attribute to the wi n d o w __________ ___________ __.
IDE Step 10 – Next, we will add a rule for read-write-access. Start by clicking on and when t he windo w pops up, add an appropriate nam e for this rule, i.
IDE Step 11 – Click on to add a new constraint __________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ 8 3.
IDE Step 12 – For this example, we are simply going to look for th e read-write user-id. From , select and scroll do wn and select . Select wi t h of and enter the read-write user id, i.e. 5600r wa as used in this ex ample, in the window as shown below.
IDE Step 13 – Via , select . From the window , select the output attribute we created above na med and click on the less-than arro w key to move the attribute to the wi n d o w __________ __________.
IDE Step 18 – When completed, y ou can view the complete policy by clicking on the button __________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ ___________.
3.2.4 Add the Nortel ERS5600-1 switch as an RADIUS Authenticator For Ignition Server to process t he No rtel switch RADIUS re quests, each switch must be ad ded as an Authenticator. IDE Step 1 – Go to -> For example, we will create ne w container named by right clicking and selecting .
IDE Step 2 – Go to -> -> and click on __________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ 8 8.
IDE Step 3 – Enter the settings as shown below making sure y ou select the policy we created abov e named via . Leave and checked. Click on when done.
3.3 Verification 3.3.1 Verify User Authentication You can test user authentication for the ERS5600 users configu red on IDE by entering the user name and password. Step 1 – Via Ignition Dashbo ard, select the IP address of the Ignition Server, click on the tab, go to and select the tab.
3.3.2 Verify user authentic ation from ERS switch You can view the authentication detail s via Igni tion Dashboard which prov ides extensive de tails about the device or user. Step 1 – In Dashboard, select the IP address of the Ignition S erver and click on the tab, go to a nd select the tab.
__________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ 9 2.
__________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ 9 3 At minimum, verify the following items: Option Verify Authentication Result If successful, should be displayed.
__________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ 9 4 4. Software Baseline Product Minimum Software Level Identity Engines 6.0 . 5. Reference Documentation Document Title Publication Number Description Identity Engines Ignition Server, Release 6.
__________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ ____________ ___________ ___________ 9 5 Contact us If you purchased a service contract for your Nort el product from a di stributor or authorized reseller, contact the techni cal supp ort staff fo r that distributor or reseller for assistance.
Een belangrijk punt na aankoop van elk apparaat Panasonic 5500 (of zelfs voordat je het koopt) is om de handleiding te lezen. Dit moeten wij doen vanwege een paar simpele redenen:
Als u nog geen Panasonic 5500 heb gekocht dan nu is een goed moment om kennis te maken met de basisgegevens van het product. Eerst kijk dan naar de eerste pagina\'s van de handleiding, die je hierboven vindt. Je moet daar de belangrijkste technische gegevens Panasonic 5500 vinden. Op dit manier kan je controleren of het apparaat aan jouw behoeften voldoet. Op de volgende pagina's van de handleiding Panasonic 5500 leer je over alle kenmerken van het product en krijg je informatie over de werking. De informatie die je over Panasonic 5500 krijgt, zal je zeker helpen om een besluit over de aankoop te nemen.
In een situatie waarin je al een beziter van Panasonic 5500 bent, maar toch heb je de instructies niet gelezen, moet je het doen voor de hierboven beschreven redenen. Je zult dan weten of je goed de alle beschikbare functies heb gebruikt, en of je fouten heb gemaakt die het leven van de Panasonic 5500 kunnen verkorten.
Maar de belangrijkste taak van de handleiding is om de gebruiker bij het oplossen van problemen te helpen met Panasonic 5500 . Bijna altijd, zal je daar het vinden Troubleshooting met de meest voorkomende storingen en defecten #MANUAl# samen met de instructies over hun opplosinge. Zelfs als je zelf niet kan om het probleem op te lossen, zal de instructie je de weg wijzen naar verdere andere procedure, bijv. door contact met de klantenservice of het dichtstbijzijnde servicecentrum.
