Imanager source address type Network

I am trying to add a range of ip address as a filter exception through
iManagers NBM filter management snap-in. If I add an individual host or
use "any address" it works fine, however, if I select "Network" as the
Source Address type (or destination address type), when I click next
nothing happens (I.E. responds as if next was not clicked).
I have tried various combinations for the address and subnet, but none
seem to work. What I THINK belongs there is:
Network
10.117.12.0
255.255.255.0
Is this a known bug, or am I just missing something obvious? Is there a
workaround?
Thanks for any help you can provide.
BM 3.8sp4 on NW 6.5 sp5 (plus post patches).
Daryl

In article <V9WNg.2780$[email protected]>, Caterina
Luppi wrote:
> i've the VAGUE recollection of this being reported as a bug.
>
I have exactly the same vague recollection, and offer the same excuse
for not using iManager for filtering!
Craig Johnson
Novell Support Connection SysOp
*** For a current patch list, tips, handy files and books on
BorderManager, go to http://www.craigjconsulting.com ***

Similar Messages

PL/SQL Network Address Type Functions

Hi,
I'm wondering if anyone knows of a PL/SQL package(s) that provides similar capabilities as the following postgreSQL network address type functions:
http://www.sql.org/sql-database/postgresql/manual/functions-net.html
I don't see anything in the standard Oracle 10g packages, so I'm wondering if anyone else has dealt with this problem and posted the package.
Thanks,
- Greg.

I think the easiest way of getting some of this functionality would be to write a PL/SQL wrapper to a Java Stored Procedure that implements calls to the Java InetAddress class. It doesn't haven't the full set of operators but I'm not sure what 'less than' actually means in the context of an IP address . If you really need them you could always extend the InetAddress class to implement such tests.
Cheers, APC

NI XNET in LabView: Transmitting source address along with signal

Hi all!
Does anyone know a way to transmit a user-determined source address along with a specific signal (J1939)? I'm outputting a signal from CVI with nxWriteSignalSinglePoint and reading it with CANalyzer, which says that the source address is NULL (254). Is there a way to set this or would I have to transmit the whole frame (maybe doing the raw bits format)? Thanks in advance!

Hey BLowery,
Given that this is a more XNET-oriented question, I would recommend asking this type of question on the Embedded Networks forum page rather than the CVI Forum since that's where user dealing with CAN and J1939 reside.
Embedded Networks Forum:
http://forums.ni.com/t5/Automotive-and-Embedded-Networks/bd-p/30
However, if you are wanting to be able to specify the source address manually in the 29-bit extended arbitration ID, as J1939 requires, it wouldn't be too hard, but you can't do it with Signal session. A Signal session uses the CAN database file to determine the ID and parameters of the frame to be sent automatically, and you simply provide the signal data. To be able to edit the ID yourself, a Frame Stream session that doesn't rely on a database would be required, since it would allow you to provide the ID manually.
I recommend taking a look a this white paper, which shows how to use XNET with the J1939 standard. In the sample code that they provide, there is an example using a Frame Out Stream session which edits the ID manually based on the user's input.
http://www.ni.com/example/31215/en/
Regards,
Ryan

Match source-address and url

I have an existing policy-map with vip and port 80. Now I need to do:
1. Match pool of ip address and url /abc then redirect to url /abc1
2. If url is ok but ip is out of the pool then redirect to url /abc2
It's probably possible to achieve but I have problem with mixing class maps (L4 and L7). Please advice how to do it.
Thank you.

HI Kamil,
Something like below. Please try and let me know if it helps.
rserver redirect red
webhost-redirection www.abc1.com
inservice
rserver redirect red1
webhost-redirection www.abc2.com
inservice
serverfarm redirect red
rserver red
    inservice
serverfarm redirect red1
rserver red1
    inservice
class-map type http loadbalance match-all url
2 match http url abc
4 match source-address 2.2.2.2 255.255.255.0
class-map type http loadbalance match-all url1
2 match http url abc
policy-map type loadbalance first-match url
class url
    serverfarm red
class url1
    serverfarm red1
class class-default
    serverfarm xxxx
Regards,
Kanwal
Note: Please mark answers if they are helpful

AAA Source addressing

Is their a way to set the source address for TACACS?
I have about 170 remote sites that I want to use my ACS server (Ver. 3.3) for Autentication/Authorization. I am using 1918 addressing at the remote locations, and at the corporate office. The ACS server is inside the Corporate network, and I am telnetting to the 10.address inside interface of the router at the remote site. It looks for the tacacs server, but does not find it, and fails back to use the local password.
I can ping the IP address of the tacacs server doing a ping with the source IP of the Inside ethernet, and the IP address of the loopback, on the remote router.

OK, 16 pages down in the forum, I finally found my answer.
Use the command:
ip tacacs source-interface

Maintaining Service Arrangement for Employees: Address type-ID not availabl

Hello,
I´m facing the following problem while implementing CRM Service via Best Practices for CRM V1.70:
Building Block Configuration Guide C26 CRM SERVICE:
Section 3.3.3 WFM Core Settings:
3.3.3.1 Maintaining Service Arrangements for Employee
Assignment Block u2018Service Arrangementsu2019:
In Assignment block Location there is no address type-ID u2018XXDEFAULTu2019 for adress source u2018Organizationu2019. Thus I receive the following error message: u2018Enter a valid address usage typeu2019. Address type-ID u2018XXDEFAULTu2019 is only available for adress source u2018Individualu2019.
What exactly do I have to do in order to make address type-ID u2018XXDEFAULTu2019 also available for adress source u2018Organizationu2019.
Thanks in advance.
Best regards,
AEV

Hi,
I am facing similar problem what did you do to resolve it.
Thanks in advance.
Rahul

How is NTP reply routed when requesting router uses loopback as source address

The Cisco NTP Best Practices White Paper and DISA STIGs recommend setting the NTP source address to a loopback interface (e.g. "ntp source loopback0").
But this only seems to work if the requesting (NTP client) router is the default gateway for the NTP server.
Specifically, the NTP server will attempt to reply to the requesting router's loopback-based source address (taken from the NTP request packet). Since that address will always be non-local from the perspective of the NTP server, the NTP server will encapsulate the reply in a Layer 2 frame addressed to its default gateway. If the gateway was the source of the original NTP request, that should work. But in most other situations that gateway won't know how to reach a loopback-based address, and will discard the reply.
I have verified this in tests with routers running both 12.4 and 15.1 releases (and NTP debugging enabled). When the NTP source is a loopback address, NTP replies never reach the requesting router. With the default NTP source address (i.e. based on the exit interface) everything works fine.
Obviously, you could employ workarounds, such as static routes or injecting loopback addresses into your routing protocols. But that seems uglier than leaving NTP source addresses at their defaults.
Why is this "best practice" so commonly advocated without mention of some significant caveats regarding routing? Am I missing something?
Thanks,
Mark

Michel:
Thanks for the response. Actually, I understand what kind of routing workarounds could allow NTP to function in spite of this "best practice." But I am mystified as to why a Cisco "NTP best practice" paper (http://www.cisco.com/en/US/tech/tk869/tk769/technologies_white_paper09186a0080117070.shtml) and various security policies would call for setting a loopback address as the NTP source when that practice will often cause more problems than it solves.
The stability of a loopback address is nice when that address is used to uniquely identify the platform for a routing protocol or syslog. A loopback-based source address can also simplify ACL management, since that address won't change if an interface or link failure forces the router to send traffic from a different interface. But I keep seeing security configuration guides/policies that call for also using a loopback address as the source for two-way protocols, such as FTP and NTP. That just doesn't make sense to me when you balance the routing implications against the limited security benefits (stable device identification, simplified ACL maintenance, and obfuscation of device addresses).
I was hoping to learn that some obscure command might allow me to control which NTP exchanges use the loopback-based source address. For example, the loopback source address would work fine on outgoing NTP broadcasts (and probably in replies from NTP servers). But I would prefer that NTP client requests use a source address based on the exit interface. That way replies can be routed back to the client without cluttering up routing tables with routes to loopback addresses.
So far, it looks like I'll need to chalk this up to poor coordination between the network security and network administration communities.
Thanks again,
Mark

Source address as 0.0.0.0

We are getting Critical incidents in MARS with source address as 0.0.0.0 What does this mean and what action can be taken ?

Source address= 0.0.0.0 means that there's no Source IP information. Since there are lots of different
event types with source address= 0.0.0.0 , then you need to post what the exact event is
to help you out.

Sources addresses need be changed.

I have a case which is showed in attachments.That is in pix outside interface changed the sourecs addresses as illustrate.How can I config the pix.
the changed sources addresses doesn't in the same network with the pix outside interface's.

Hi
i feel you want to change the source ip of the packets coming from outside world especially from the 3 networks mentioned in ur figure.
i feel you can make use of ip nat source outside source list command to modify the same.
But do remember you can configure this up in your router also refer this link for more info on the same..
http://cisco.com/en/US/tech/tk648/tk361/technologies_configuration_example09186a0080093f8e.shtml
regds

WRVS4400N - eth0: received packet with own address as source address

I am using a WRVS4400N as my primary router for a small office. I get the following message repeated over and over in my logs. This seems to happen for 2 or 3 days and then it will go away for about a week and then come back. Does anyone know what is causing this? The best I can tell I don't have any IP conflicts on the network and most of the time the network has very little traffic other than 2 or 3 computers surfing the web.
Jan 3 16:48:09 - eth0: received packet with own address as source address
Jan 3 16:48:09 - eth0: received packet with own address as source address
Jan 3 16:48:15 - eth0: received packet with own address as source address
Jan 3 16:48:27 - eth0: received packet with own address as source address
Jan 3 16:48:51 - eth0: received packet with own address as source address

any news on this issue?
I am getting more and more messages (20+/day) - hundreds this month.
Now Coming every 10 minutes - HELP
eth0: received packet with own address as source address
Done everything, now waiting for input from Cisco.
Please, anyone as Cisco got any answers?
1:38 AM [email protected] WRVS4400N Security Log [6B:C6:FD]
12:36 AM [email protected] WRVS4400N Security Log [6B:C6:FD]
2:38 AM [email protected] WRVS4400N Security Log [6B:C6:FD]
3:38 AM [email protected] WRVS4400N Security Log [6B:C6:FD]
4:38 AM [email protected] WRVS4400N Security Log [6B:C6:FD]
5:38 AM [email protected] WRVS4400N Security Log [6B:C6:FD]
6:38 AM [email protected] WRVS4400N Security Log [6B:C6:FD]
7:38 AM [email protected] WRVS4400N Security Log [6B:C6:FD]
8:38 AM [email protected] WRVS4400N Security Log [6B:C6:FD]

How to Change Source system type of ECC6.0 in BW system

Hi BW Experter,
   I connected ECC6.0 PRD system with BI7.0 PRD system , the connection is successful,
but the source system type of ECC6.0 PRD is not collect . The ECC6.0 PRD is as a
BW system type in the source system list of bw system .
   I found that Tcode RSA1 has ever been run in PRD ECC6.0 , So I did a connection testing of
ECC6.0 QA with BI7.0 PRD .
     Step 1. Connect ECC6.0 QA with BI7.0 PRD , ECC6.0 QA was as SAP system type in source system list of bw system .
     Step 2. Run tcode RSA1 in QA ECC6.0
     Step 3. Delete connection of ECC6.0 QA with BI7.0 PRD .
     Step 4. Connect ECC6.0 QA with BI7.0 PRD again , ECC6.0 QA was as SAP system type in source system list of bw system .
   I want to know how to change ECC6.0 PRD source system type to SAP .
If it can't been change to SAP ,Is there any impact when ECC6.0 PRD is as bw system type in source system .
Thank you for your help .

I got the soulution from note: 1087980 - ECC Source systems appearing in BI folder
Summary
Symptom
Source system connection for an ECC system appears in the BI folder, rather than in SAP folder, as expected.
Other terms
Wrong folder,RSA1, RSBASIDOC, RSAP_BIW_DISCONNECT
Reason and Prerequisites
Transaction RSA1 was inadvertently used on an ECC system , thereby creating a 'Myself' source system entry in RSBASIDOC table
Solution
This is just a display issue and does not cause any operational issues. Therefore, it need not be corrected, especially if the ECC system in question is used as a BI system as well.
If it is absolutely required that the ECC source system appear in the correct folder, perform the following steps.
1. Check that an entry with SRCTYPE 'M' exists in table RSBASIDOC table of ECC source system.
2. Note the values for SLOGSYS and RLOGSYS. It should be same.
3. Run the function module RSAP_BIW_DISCONNECT in the ECC system.
   NOTE: Never run that function module in a BI system!
4. Enter the following values :
I_BIW_LOGSYS   <RLOGSYS> as noted in step 2
I_OLTP_LOGSYS <SLOGSYS> as noted in step 2
I_FORCE_DELETE <X>
< DO NOT ENTER ANY VALUE IN THE FIELD - RFC target sys !!!!! >
5. Go to RSA1-> Source systems in the BI system connected to the ECC system.
6. Select the ECC source system and select RESTORE in the right click menu.
Now the ECC system should appear in the SAP folder.
If running RSAP_BIW_DISCONNECT results in an error like OTHER_ERROR, please check if a valid RFC connection exists in transaction sm59.
If the myself source system connection cannot be deleted in any case, log a service marketplace message with SAP Support.
Edited by: fang frank on Jul 15, 2009 8:31 AM

Source port type for BPELProcess does not match target port type for EJB

Hi gurus,
I have a problem with calling EJBs from a 11.1.1.3 composite. The following summarizes the issue:
- there are several EJBs within the same package deployed on a WLS server.
- these beans have method names that are the same, for example create(), delete() etc.
- using the EJB Service Adapter I have created 3 References, one for each of the 3 beans I need to invoke in a BPEL process.
- each bean is imported into the project with their own *.wsdl *Ref.wsdl files.
- each wsdl imports a namespace based on the java package name
- now i have 3 wsdls, importing the same namespace and namespace conflicts arise.
At this point I'm thinking, 'no problem, just change the namespaces manually'
- whenever i try to change the namespace that JDev gives the Reference components I end up with the compilation error:
Source port type for "BPELProcess" does not match target port type for "EJBRef"
It seems that the namespace must be the same as the package name, even though I resolved all the references to the new namespaces and ensure they all match.
The problem appears to be in the BPELProcess.componentType file.
<reference name="HelloEJBRef" ui:wsdlLocation="HelloEJBRef.wsdl">
<interface.wsdl interface="http://package.workspace.com/HelloEJB#wsdl.interface(HelloEJB)"/>
</reference>
If the namespace (text before the #) is changed at all from the default, even if it matches the wsdl, results in the port type mismatch error above.
Any ideas?
btw, running SOA 11.1.1.3, JDev 10.1.1.3, EJB 3.0

Hi gurus,
I have a problem with calling EJBs from a 11.1.1.3 composite. The following summarizes the issue:
- there are several EJBs within the same package deployed on a WLS server.
- these beans have method names that are the same, for example create(), delete() etc.
- using the EJB Service Adapter I have created 3 References, one for each of the 3 beans I need to invoke in a BPEL process.
- each bean is imported into the project with their own *.wsdl *Ref.wsdl files.
- each wsdl imports a namespace based on the java package name
- now i have 3 wsdls, importing the same namespace and namespace conflicts arise.
At this point I'm thinking, 'no problem, just change the namespaces manually'
- whenever i try to change the namespace that JDev gives the Reference components I end up with the compilation error:
Source port type for "BPELProcess" does not match target port type for "EJBRef"
It seems that the namespace must be the same as the package name, even though I resolved all the references to the new namespaces and ensure they all match.
The problem appears to be in the BPELProcess.componentType file.
<reference name="HelloEJBRef" ui:wsdlLocation="HelloEJBRef.wsdl">
<interface.wsdl interface="http://package.workspace.com/HelloEJB#wsdl.interface(HelloEJB)"/>
</reference>
If the namespace (text before the #) is changed at all from the default, even if it matches the wsdl, results in the port type mismatch error above.
Any ideas?
btw, running SOA 11.1.1.3, JDev 10.1.1.3, EJB 3.0

Javax.mail.NoSuchProviderException: No provider for Address type: rfc822

Use JavaMail 1.2 send Mail Errors:
"javax.mail.NoSuchProviderException: No provider for Address type: rfc822"
Why?
Can you supply a stmp server name?
Thanks.

[skyask],
Honestly, I am not very sure where the JVM is located for the WebLogic 5.1 application server. You probably need to contact your local BEA rep office for support.
The jar file for the JavaMail API is either mail.jar (contains the API libraries) or mailapi.jar (contains the API libraries and all the providers), so I guess if you search the WebLogic directories, you might be able to locate it.
It also depends on the OS platform that you are working on and the WebLogic installation documentation may give a clue or two where the .jar files for optional Java packages are found.
HTH.
Allen Lai
Developer Technical Support
SUN Microsystems
http://www.sun.com/developers/support/

Is it possible to use HTTPS in HTTP recv adapter using Address type as URL

Hi All,
If some one who has tried HTTPS communication using HTTP receiver adapter using URL address as Address type can you please guide me what are the steps need to be done.
Address type is a parameter in HTTP adapter setup .
Regards,
Reddy

Use the below code to get the reference of EntityManagerImpl and get the reference of Session from EntityManagerImpl and then you can call the Stored Procedure.
private EntityManagerImpl emImpl;
emImpl = (EntityManagerImpl)Persistence. createEntityManagerFactory("TFDModel").createEntityManager();
Session session= emImpl.getActiveSession();
StoredProcedureCall call = new StoredProcedureCall();
call.setProcedureName("CONVERT_FEET_TO_METERs");
call.addNamedInOutputArgumentValue(
"LENGTH", // procedure parameter name
new Integer(100), // in argument value
"LENGTH", // out argument field name
Integer.class // Java type corresponding to type returned by procedure
ValueReadQuery query = new ValueReadQuery();
query.setCall(call);
Integer metricLength = (Integer) session.executeQuery(query);
Regards,
Vinay

HTTPS communication using HTTP receiver adapter URL address as Address Type

Hi All,
If some one who has tried HTTPS communication using HTTP receiver adapter using URL address as Address type can you please guide me what are the steps need to be done.
Note : Address type is a parameter in HTTP adapter setup .
Regards,
Reddy

Hi,
Check this,
Configurations in Integration Directory
The plain HTTP adapter gives the receiver system the following specifications:
 Specifications for addressing using a URL address:
Target host, service number, and path prefix including query string:
http://<hostname:port>/<path>?<query-string>
You can identify the target host (HTTP port) of a SAP Web Application Server using
the
ICM monitor
Host and port of the HTTP proxy (optional if there is a firewall between the plain
HTTP adapter and the receiver system)
Authentication data for the receiver system.
See also: transaction Display and Maintain RFC Destinations (SM59).
 Specifications for addressing using an HTTP destination:
HTTP destination
 Parameters from the communication channel for technical routing
Content type (the entry text/XML is expected as default)
Specifies the format that the message contents (the payload) should have.
Optional header fields for the receiver-specific protocol
Attributes for the query string
1. Sender party
2. Sender service
3. Receiver Interface
4. Message ID
5. Quality of service
6. Queue ID
All attributes are selected except for the queue ID. If you do not want a value to be
transferred to the receiver, deselect it. The queue ID is only required if the quality of
service is EOIO.
Specifications for payload manipulation
XML code (default UFT-8)
Specifies the character set.
URL escaping
Presents the XML in a URL-enabled format. Special characters that could be
interpreted as control characters are replaced with escape characters (masked).
Prolog
Enhances the payload for particular servers (optional, see below).
Epilog
Enhances the payload for particular servers (optional, see below).
Enhancing the Payload
Regards
Seshagiri

Imanager source address type Network

Similar Messages

Maybe you are looking for