Asset ID: |
1-72-1378696.1 |
Update Date: | 2017-09-21 |
Keywords: | |
Solution Type
Problem Resolution Sure
Solution
1378696.1
:
SL3000/SL8500 - Not Able to Enable Policy Routing on HBCR-B Card
Related Items |
- Sun StorageTek SL3000 Modular Library System
- Sun StorageTek SL8500 Modular Library System
|
Related Categories |
- PLA-Support>Sun Systems>TAPE>Tape Hardware>SN-TP: SL3000-8500 Library
|
In this Document
Oracle Confidential PARTNER - Available to partners (SUN).
Reason: Confidential for Oracle Support personnel
Created from <SR 3-4859520941>
Applies to:
Sun StorageTek SL3000 Modular Library System - Version All Versions and later
Sun StorageTek SL8500 Modular Library System - Version All Versions and later
Information in this document applies to any platform.
Symptoms
Installed Redundant Electronics on a SL3000, and had network problems:
I was not able to enable policy routing on HBCR-B card.
After having run the network clone command and verified network settings on both cards, I found that ip policy was not enabled on B-card. I tried enabling it (had to be done when b-side was active), and even though the command does not fail ip policy is still disabled when checking. The defined policy routes are intact on both A and B side.
SL3000> network ip policy status
2A:
Policy Rule: DISABLED
2B:
Policy Rule: DISABLED
COMPLETED
SL3000> network ip policy enable dev 2A
SL3000> network ip policy enable dev 2B
SL3000> network ip policy status
2A:
Policy Rule: DISABLED
2B:
Policy Rule: DISABLED
COMPLETED
Both ports on A-side is OK with ip policy enabled.
Both ports on B-side is disabled.
Cause
The below is engineering comments.
********************************
This is likely due to a bug in the network code where multiple network restarts can result in the network manager code (hardware manager) becoming non-responsive. This means the configuration file is written correctly, but the network is NOT restarted. The "network ip policy route show dev XX" command only shows what values have been applied to the routing tables and not the values in the configuration file.
Solution
Work around is below:
You should wait several seconds (say 5-10 secs) before issuing the next CLI command when you see the message below:
"Note: TCP/IP stack reset may take a few seconds after command completion."
If you are entering command using copy/paste. When 2 commands are issued quickly that the network restart hangs are more frequent.
============================
Configure network on HBCR-B manually.
Clone command is not mandatory for RE.
We can configure using any network command after switching to side-B.
Enabling of RE was done without network-problems, since we did all the configuration of HBCR-B manually.
Policy routes works fine.
I would not recommend using the clone command if you are using different mask than 23-mask and if you are using policy routes.
Attachments
This solution has no attachment