Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1535717.1
Update Date:2017-08-07
Keywords:

Solution Type  Technical Instruction Sure

Solution  1535717.1 :   SL3000/SL8500 - Policy Route Statements Now Support "Network" Destinations  


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
Goal
Fix


Applies to:

Sun StorageTek SL8500 Modular Library System - Version Not Applicable and later
Sun StorageTek SL3000 Modular Library System - Version Not Applicable and later
Information in this document applies to any platform.

Goal

 Policy Route Statements Now Support "Network" Destinations

Fix

  The network policy route statement command has been updated in SL3000 4.0 code and SL8500 8.05 code as follows:

The policy route configuration commands were extended to support network destination routes instead of only host destination routes. 
Here is the new command syntax for the network CLI command (this is from the CLI "help network"):


SL8500> network ip policy route <add|del> <IP_address[/netmask]> dev <device>

Add or Delete static route to policy for device 2A or 2B

The ability to specify the netmask within this command is the new addition.

Examples:

network ip policy route add 192.168.2.45 dev 2B (this defines a single host destination - only command available pre-4.0/8.05 codes)

network ip policy route add 192.168.2.0/24 dev 2B (this defines a network destination from 192.168.2.0 through 192.168.2.255)

network ip policy route add 192.168.2.0/26 dev 2B (this defines a network destination from 192.168.2.0 through 192.168.2.63)

network ip policy route add 192.168.2.64/26 dev 2B (this defines a network destination from 192.168.2.64 through 192.168.2.127)

Note: Valid network subnet beginning and ending addresses must be used as appropriate for the specified netmask.


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback