Ironport S380 - Port Channel for P1/P2 - & - Bypass Traffic Mechanism

Dear Team,
One of my customer has purchased WSA S380.
1. He has a requirement to bundle P1/P2 Ports and create a port-channel in a switch. Is it Possible ?  If No, then what can be the Solution ?
2.  Also, Is it possible to detect failover, means if our WSA will go down then will it able to bypass the traffic ?  If yes then please explain how can we achieve that ?
Thanks.
Milin

1. no, you can't port channel the WSA.
2. It depends on how you get the traffic to the WSA.  Are you using transparent redirection (eg WCCP), then yes, when the WSA goes down, it will be detected and traffic will quit being redirected to it.   If you're using explicit redirection, it won't be detected, unless you have 2 WSAs and you cluster them.
Once you get the first WSA up and running, you can request a virtual license and install a vWSA and use that for fail over...

Similar Messages

  • One or two LAG port-channel for 5508 v7.4 in HA setup?

    Hi group
    I have a question regarding LAG in HA setup; do you configure two port-channel, one for each controller or, only one port-channel for both?
    I have a stack of 3 x 3750x, and 2 x 5508 with each two Gigabit uplink in use.
    Active controler (5508-1) is connected to stack switch 1 and stack switch 2.
    Standby controller (5508-2) is connected to stack switch 2 and stack switch 3.
    I cannot find any documentation or guidelines for configurations of LAG in HA setup.
    P.S. my question is not how to configure LAG or LACP, it only if you use one port-channel consist of 4 gigabit ports, or you have two with each 2 gigabit port to each controller.
    TIA,
    Peter

    Thanks Stephen for your reply.
    The switch doesn’t see which of the two port-channel that is on the active controller right?
    If WLC01 is the active one in PO1 and standby is WLC02 in PO2, the MAC of the active controller (WLC01) will be sending on PO1.
    When failover to standby, the MAC of WLC02 will be sending on PO2. As I see it, it is same IP address (management IP address of WLC01) but different MAC address – from WLC02.
    So why could it not be one Port-channel, both controller will use one and same config when it become active?
    TIA
    Peter

  • Port channel WLC 5508 and 3750

    Hi All,
    I want to configure Port channel for WLC 5508 and cisco 3750 Stack Switch. What changes I need to make on WLC and where?
    Thanks
    Jagdev

    Thanks Chris,
    LAG is enable on WLC, and Port channel is configured on 3750, Please see the configration and Port channel status below:-
    (Cisco Controller) >show lag summary
    LAG Enabled
    interface Port-channel14
    description Port Channel to WLC001
    switchport trunk encapsulation dot1q
    switchport mode trunk
    end
    sh etherchannel 14 summary
    Flags:  D - down        P - bundled in port-channel
            I - stand-alone s - suspended
            H - Hot-standby (LACP only)
            R - Layer3      S - Layer2
            U - in use      f - failed to allocate aggregator
            M - not in use, minimum links not met
            u - unsuitable for bundling
            w - waiting to be aggregated
            d - default port
    Number of channel-groups in use: 14
    Number of aggregators:           14
    Group  Port-channel  Protocol    Ports
    ------+-------------+-----------+-----------------------------------------------
    14     Po14(SD)        LACP      Gi1/0/22(I) Gi2/0/22(I)
    sh run int g1/0/22
    Building configuration...
    Current configuration : 209 bytes
    interface GigabitEthernet1/0/22
    description Trunk to WLC001 DistPort1
    switchport trunk encapsulation dot1q
    switchport trunk native vlan 254
    switchport mode trunk
    channel-group 14 mode active
    end
    sh run int g2/0/22
    Building configuration...
    Current configuration : 209 bytes
    interface GigabitEthernet2/0/22
    description Trunk to WLC001 DistPort2
    switchport trunk encapsulation dot1q
    switchport trunk native vlan 254
    switchport mode trunk
    channel-group 14 mode active
    end

  • FabricPath vPC port-channel err-disabled CE Vlan?

    I have a pair of Nexus 56128 configured with fabric path and vpc+. The Nexus pair has UCS connected downstream using vpc port-channels. When a Vlan is in mode fabricpath, it's ok for the vpc+ peer-link and the vpc port-channel to UCS. However when I changed the vlan to classic Ethernet, it's err-diabled in the vpc port-channels.
    Is this the normal behavior of fabric path domain? In other words, CE Vlans and fabric path Vlans cannot use the same Layer 2 path, correct?
    If I need to transport CE Vlans and fabric path Vlans from Nexus (fabric path vpc+) to UCS, I have to use a separate non-vpc port-channel for the CE Vlans between each Nexus and UCS?
    Thanks

    I have a pair of Nexus 56128 configured with fabric path and vpc+. The Nexus pair has UCS connected downstream using vpc port-channels. When a Vlan is in mode fabricpath, it's ok for the vpc+ peer-link and the vpc port-channel to UCS. However when I changed the vlan to classic Ethernet, it's err-diabled in the vpc port-channels.
    Is this the normal behavior of fabric path domain? In other words, CE Vlans and fabric path Vlans cannot use the same Layer 2 path, correct?
    If I need to transport CE Vlans and fabric path Vlans from Nexus (fabric path vpc+) to UCS, I have to use a separate non-vpc port-channel for the CE Vlans between each Nexus and UCS?
    Thanks

  • 6880X VSS Port-Channel

    Hi
    I was trying to configure two 6800x switches as a VSS pair, Ive done this on 4500x switches before and worked a treat. when setting up a L2 port-channel, for some reason it puts the ports into routed mode and does not allow me to build a L2 port-channel.
    So I add the following config for the port-channel
    Interface port-channel 10
    Description VSL_Link
    switchport
    switch virtual link 2
    no shut
    Interface range Tengig 1/1 – 1/2
    Description VSL_Link
    switchport mode trunk
    channel-group 10 mode on
    Now as soon as I type the channel-group 10 mode on, it gives an error
    "Command rejected  (Port-channel10): Either port is L2 and port-channel is L3, or vice-versa"
    I managed to create a L2 port-channel on a 4500x, will the 6800x only allow me to create a l3 port channel. 

    Hi 
    I tried this config on the 4500x and it worked, now I have also added the switchport mode trunk command to both the port-channel and interface and still getting the same error. 
    When I do sh int status, the ports are showing as routed
    I cleared the config and first set both interface as trunks, then when I do the channel-group 10 mode on command, it accepts the command an automatically creates the port-channel, but the interfaces show as routed.
    This is my first time using a 6880x, when i logged into it, the default hostname is set to Router. I was expecting it to be named Switch, not that the hostname affects the config but makes me wonder, is the config different for the 6880x as opposed to other L3 switches

  • ASR 1001 OTV Port-Channel

    I saw in the release notes that 3.10 for the ASR 1001 supports port-channel for the internal otv interface.  I upgraded to that release and it lets me use a port-channel interface, but it won't let me use the serivce instance command on the L2 interface.  I can add the channel-group command but not any otv commands.  Has anyone seen this yet?
    Thanks,
    Tom

    Hi tom,
    Not sure if you have resolved this issue, but, I hope you are configuring the port-channel with all the service-instance configurations. If yes, and you are getting into issues, please do post the output of the issue, we can have a look at the same.

  • Port-channel Problem between Fabric Interconnect and N7K vPC

    Dear all,
    I have a problem with Port-channel Uplink between Fabric Interconnect with N7K using vPC
    This is my network topology for UCS Deployment
    In N7K I has configured vPC for red link and green link, at Fabric Interconnect A I has configured Port-Channel with member is Port 1 and Port 2, uplink is red link. At Fabric Interconnect B, I has configured Port-Channel with member is Port 1 and Port 2, uplink is green link.
    The show interface port-channel on N7K is good, every port-channel is up and have all member. But At Fabric Interconnnect, when I see on UCS Manager, the status of Port-Channel on Fabic A and Fabric B is fault with Additional Info: No operational member. Although all link is link up and I has status of Port-Channel is enable on UCS Manager. When I see the Properties of Port 1, Port 2 on Port-channel, I see the membership status is : individual. This mean port-channel is not up and no membership in this configuration. I want to using port-channel for load balance and plus more bandwidth for uplink to 20Gig. I don't understand why ?
    Please help me resolve this problem, I has send the capture screen of UCS Manager when I show status of Port-channel and Port-member in port-channel in attach items.
    Anyone can help me to resolve this, thanks you very much. Please reference attach items for more detail about fault.
    Thanks,
    Trung.

    Thanks Matthew very much,
    I has resolved this problem. The reason of problem is miss match protocol of port-channel between N7K and Fabric Interconnect. The Fabric Interconnect always use LACP protocol, but N7K using Port-channel mode on, that why the port-channel failed. I has configured LACP for port-channel in N7K, it has resolved the problems.
    Thanks,
    Trung.

  • Why don't channel-group numbers match on a VSS port-channel link?

    Hi All,
    I have two 6509's that are VSS'd together via four 10gig links on each side. The configuration was done before I started this job, but in reviewing the configs I see that the 10gbps VSS heartbeat links are port-channeled together on each side, but one side is channel-group 2, while the other end of the bundle is channel-group 1.
    I thought that channel-group numbers needed to match on both ends of the port-channel for it to form correctly?
    I'm guessing that this has to happen because the switches are virtually one, so you can't put all 8 links into the same channel-group number or there would be nothing to connect to on the other side. Therefore, the "switch virtual link #" command is the real code that tells the switch where the other end of the link is, regardless of channel-group number, correct?

    Dean,
    The channel-group number does not have to be the same on each end. The four ports on switch A have to be in the same channel-group, and the four ports on switch B have to be in the same channel-group, but there's no communication across that line about what the channel-group is called. It's just a name. From a design standpoint it is nice to have them the same on both sides, but it's not always simple to allow for that in the design of a network.
    -Jameson

  • PIN GROUP, Port Channel

    Hi, Cisco Gurus:
    Need your authoritative take on the following: Ethernet and FC is all End-Host Mode.
    1. If client is using FC Port Channel on all of the FC Uplinks for the 2 Fabric Interconnects with a SINGLE VSAN on each FI, MUST THEY USE SAN PIN GROUP? Currently, they are pinning the vHBA template to this SAN Pin Group. vHBA-Fabric A pins to FC-PIN-GROUP-A and vice-versa,
    2.
    If FC Port Channel is being used as in 1, from WHICH UCSM option should the VSAN be created?
    Should VSAN be STILL created under the Individual Fabric A and B as before?
    Or
    It have to be Global VSAN or Dual VSAN outside the Fabric A or Fabric B?
    3.If client is using Ethernet Port Channel for each Fabric Interconnet or each fabric, must they use LAN PIN GROUP?
    Currently, they are pinning the vNIC template to this Pin Group (Fabric A & B). vNICA-Fabric A pins to LAN-PIN-GROUP-A and vice-versa.
    Something which I have SELDOM SEE before.
    As usual, I know it is easy meat for Cisco gurus. Thanks, PAL.
    So Long.
    SiM

    All VSANs in the screenshot above are Global.  Notice they're not created under the Fabric A/ B section.
    Unlike "VLANs", which are almost always Global and normally accessible from each Fabric Interconnect, VSANs are different.  Best practice for storage has keeping each SAN Fabric separate.  Keeping this in mind, does it make more sense to create VSANs as global or under their respective Fabric interconnects? (Under the separate Fabric Inteconnects of course.  The only use case for using Global VSANs is as Craig pointed out - when there is a single Storage switch northbound that both Fabric Interconnects uplink to.
    Where this gets confusing is when you're assigning vHBA's to a VSAN. 
    Ex. 
    Let's say, as your customer has done, they've created their two VSAN 10 and 20 as "Global".  For comparison sake I've also created VSAN 100 just under Fabric-A and VSAN 200 just under Fabric-B. Their VSANs would looks like:
    Now, when creating an vHBA under your service profile, you need to assign it to a VSAN.  Take a look:
    So depending which Fabric (A/B) they want the vHBA connected to the options will change.  You can see that by creating the VSANs 10 and 20 as "Global" they appear when either Fabric is selected - Conversly you can see the two 100 and 200 I created under each Fabric, only appear when that fabric is selected.
    So what?  Well if your upstream SAN switches only use one of the respective VSANs configured and only connect to one Fabric Interconnect, then you can potentially "blackhole" your storage traffic by assigning it to the wrong Fabric Interconnect.  Creating the VSANs only under the appropriate Fabric Interconnect prevents this possibility.
    SAN Port-Channels have no bearing on this.  All a SAN Port Channel does is make mulitple FC Uplinks appear as one - which requires SAN Port Channels configured upstream also.  Leaving the FC Uplinks as individual just lets UCS dynamically pin virtual interfaces across the FC uplinks in a round-robin fashion.
    In your case you have no need for Pin-Groups either.  As Jeremy pointed out, unless you have a specific need for them, it's safer to not use them.
    Regards,
    Robert

  • Port-channel / Trunking / VSAN

    Hi all,
    I have a quick question...
    I enabled trunking for all vsans and created a port-channel. I want to use this port-channel for all my vsans.
    Does it matter in which vsan I add my port-channel?
    If it doesn't matter why can I assign a port-channel to a vsan?
    Cheers,
    Mike

    Mike,
    It should be the same configuration on both sides for the port-channel to come up. The reason why you can assign a port-channel to a VSAN is that if you are using an E port then it depends on the matching port-channel VSAN to come up.
    TE Port functionality is specific to MDS for enhanced ISL capabilities. E ports can be used for non-cisco switches to make the trunk work seamlessly as an E port.
    You can refer to the following for more info:
    http://www/en/US/docs/storage/san_switches/mds9000/sw/rel_3_x/configuration/guides/cli_3_4_x/trnk.html
    http://www/en/US/docs/storage/san_switches/mds9000/sw/rel_3_x/configuration/guides/cli_3_4_x/pc.html
    Hope this helps.
    - Nikhil

  • Port-channel disoblige

    Hi Folks,
    We have a trouble in port-channel for an interface with point-point link, assigning ip to that interface possibly can make a ping,, whereas bringing the same interface to port channel assigning those same IP and try pinging to each other, unfortunately can't ping.
    switch 1#
    interface Ethernet2/20
      speed 1000
      duplex full
      bandwidth 1000000
      udld disable
      channel-group 2
      no shutdown
    switch 2#
    interface Ethernet2/37
      speed 1000
      duplex full
      bandwidth 1000000
      channel-group 2
      no shutdown
    switch 1#
    Command: show running-config interface port-channel2
    Time: Fri Dec 27 09:49:3 2013
    version 6.0(1)
    interface port-channel2
      speed 1000
      duplex full
      ip address 1.2.3.1/30  --> altered ip
    switch 2#
    Command: show running-config interface port-channel2
    Time: Fri Dec 27 09:50:48 2013
    version 6.2(2)
    interface port-channel2
      speed 1000
      duplex full
      ip address 1.2.3.2/30 --> altered ip
    Please review and suggest us some valuable recommendation to overcome this issue.

    What switch is this? Generally, to create a L3 etherchannel, you'll need to configure "no switchport" on the physical interfaces before you can use an address on the port channel interface.
    HTH,
    John
    *** Please rate all useful posts ***

  • Port channeling a node between two 2248's

    I have one Nexus 7009 with a pair of 2248's attached via port channels.  I have several devices, a Cisco wireless lan controller, ESX servers, etc which I have multihomed to my current 6500's.  I want to create port channels for these devices across the pair of 2248's.  Currently have been working with the config for the WLC.  I can create the port channel on the N7k with no problem as a trunk, and I am able to configure the first port to use the port channel, but when I add the second port I receive the following message:
    command failed: port not compatible [Members in multiple FEX]
    Thus I am unable to add the second interface.  I assume I will run into the same problem with the ESX's as they have six 1 Gb interfaces in a port channel.  I am new to the Nexus world and this is my first Nexus switch being moved into production.  I have seen several post that are similiar but not really an answer.  Does anybody have any idea as to what I am doing wrong.  Thanks in advance.

    Hi,
    If I understand what you're trying to do correctly, then you're not doing anything wrong, but the topology you're trying to use is unsupported.
    If you refer to the diagrams shown in Nexus 7000 Fex Supported/Not Supported Topologies then I believe you're trying to configure the topology shown on the last of the three pictures, labeled number 11. I don't know the exact details as to why this isn't a supported topology, but sadly it isn't.
    As you only have a single Nexus 7000, the only option you would seem to have at this stage is to use an active/standby topology as shown in the first and second picture on the diagram labeled number five.
    Regards

  • 2960x port channel bandwidth command workaround

    Folks:
    I am looking for a work around - Currently I have a four member 2960x switch stack - I have Ten 1/0/1 and Ten 3/0/1 in a port-channel; however, when I try to set the 'bandwidth' on PO1 interface to 20000000 I receive an error, which corresponds being out of range, due to the links being 10Gbps.
    Is there a work around so my PO1 interface reflects the correct bandwidth?
    Switch I am using and version of software
    Switch Ports Model              SW Version            SW Image
    *    1 52    WS-C2960X-48TD-L   15.0(2)EX5            C2960X-UNIVERSALK9-M
    Thank you
    JJ

    The tx-/rxload is probably the least of your problems. Assuming we're talking about a L2 port-channel the interface BW is base for spanning tree cost calculation. With a BW 10000000 kbit/s STP would consider the port-channel equal to a single 10GE link and could possibly decide to block your port-channel for a less favorable link.
    That being said, the port-channel is supposed to have the correct BW corresponding to the number of bundled links without any need for manual user configuration.
    I suppose it is either a software bug or there is an interface not bundled correctly. 
    Post the result of 'show etherc sum' here to check.
    Regards

  • Administration port - network channel for admin traffic

    I am trying to configure a separate channel for Administration traffic on weblogic. I followed the oracle docos and configured the SSL, domain wide admin port, server listen address, ‘admin’ channel.
    The issue is admin traffic in not happening through the newly created channel.
    L2 network is not getting used. I can’t see any activity in the monitoring tab of new Channel. Also the netstat is showing that the port 9101/9102 is getting used on the 192.168.100.218 and not on 10.254.252.849.
    I also tried by setting up the newly created channel weight as 51, but no luck.
    Is JMX connectivity related to admin channel?
    Any help is highly appreciated. Thanks.
    Ipconfig:
    Admin: adminserver701.mycompany.internal, 192.168.100.238, 10.254.252.808
    Managed: appserver701.mycompany.internal, :192.168.100.218, 10.254.252.849
    Domain wide admin port: 9101
    Admin:
    Listen address –> adminserver701.mycompany.internal
    Channel –> admin -> 10.254.252.808/9101
    Startup -> -Dweblogic.admin.ListenAddress=admin://10.254.252.808:9101
    Managed:(appserver701)
    Listen address –> appserver701.mycompany.internal
    Admin port override: 9102
    Channel –> admin -> 10.254.252.849/9102
    Startup -> -Dweblogic.admin.ListenAddress=admin://10.254.252.849:9102
    AdminServer Logs:
    ####<Feb 18, 2013 1:53:33 PM EST> <Info> <JMX> <adminserver701.mycompany.internal> <soa_as> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361159613346> <BEA-149512> <JMX Connector Server started at service:jmx:iiop://adminserver701.mycompany.internal:9101/jndi/weblogic.management.mbeanservers.runtime .>
    ####<Feb 18, 2013 1:53:33 PM EST> <Info> <JMX> <adminserver701.mycompany.internal> <soa_as> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361159613353> <BEA-149512> <JMX Connector Server started at service:jmx:iiop://adminserver701.mycompany.internal:9101/jndi/weblogic.management.mbeanservers.edit .>
    ####<Feb 18, 2013 1:53:33 PM EST> <Info> <JMX> <adminserver701.mycompany.internal> <soa_as> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361159613367> <BEA-149512> <JMX Connector Server started at service:jmx:iiop://adminserver701.mycompany.internal:9101/jndi/weblogic.management.mbeanservers.domainruntime .>
    ####<Feb 18, 2013 1:53:36 PM EST> <Notice> <Server> <adminserver701.mycompany.internal> <soa_as> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361159616699> <BEA-002613> <Channel "DefaultAdministration" is now listening on 192.168.100.238:9101 for protocols admin, ldaps, https.>
    ####<Feb 18, 2013 1:53:36 PM EST> <Notice> <Server> <adminserver701.mycompany.internal> <soa_as> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361159616700> <BEA-002613> <Channel "Channel-0" is now listening on 10.254.252.808:9101 for protocols admin, ldaps, https.>
    ####<Feb 18, 2013 1:55:12 PM EST> <Notice> <Server> <adminserver701.mycompany.internal> <soa_as> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <cd259038c7dcf5a8:-26ac3ba0:13ceb6f767d:-8000-000000000000001a> <1361159712920> <BEA-002613> <Channel "Default" is now listening on 192.168.100.238:7001 for protocols iiop, t3, ldap, snmp, http.>
    ####<Feb 18, 2013 1:55:12 PM EST> <Notice> <Server> <adminserver701.mycompany.internal> <soa_as> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <cd259038c7dcf5a8:-26ac3ba0:13ceb6f767d:-8000-000000000000001a> <1361159712920> <BEA-002613> <Channel "DefaultSecure" is now listening on 192.168.100.238:7002 for protocols iiops, t3s, ldaps, https.>
    ManagedServer Logs:
    ####<Feb 18, 2013 2:54:19 PM EST> <Info> <JMX> <appserver701.mycompany.internal> <adp_ms01> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361163259911> <BEA-149512> <JMX Connector Server started at service:jmx:iiop://appserver701.mycompany.internal:9102/jndi/weblogic.management.mbeanservers.runtime .>
    ####<Feb 18, 2013 2:54:20 PM EST> <Notice> <Server> <appserver701.mycompany.internal> <adp_ms01> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361163260350> <BEA-002613> <Channel "Channel-0" is now listening on 10.254.252.849:9102 for protocols admin, CLUSTER-BROADCAST-SECURE, ldaps, https.>
    ####<Feb 18, 2013 2:54:20 PM EST> <Notice> <Server> <appserver701.mycompany.internal> <adp_ms01> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361163260350> <BEA-002613> <Channel "DefaultAdministration" is now listening on 192.168.100.218:9102 for protocols admin, CLUSTER-BROADCAST-SECURE, ldaps, https.>
    ####<Feb 18, 2013 2:54:58 PM EST> <Notice> <Server> <appserver701.mycompany.internal> <adp_ms01> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <d3208ed6c2482016:-46ac5fed:13ceba69a8e:-7ffe-000000000000000e> <1361163298045> <BEA-002613> <Channel "DefaultSecure" is now listening on 192.168.100.218:7102 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
    ####<Feb 18, 2013 2:54:58 PM EST> <Notice> <Server> <appserver701.mycompany.internal> <adp_ms01> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <d3208ed6c2482016:-46ac5fed:13ceba69a8e:-7ffe-000000000000000e> <1361163298045> <BEA-002613> <Channel "Default" is now listening on 192.168.100.218:7101 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
    AdminServer logs update while starting managed:
    ####<Feb 18, 2013 2:54:57 PM EST> <Info> <JMX> <adminserver701.mycompany.internal> <soa_as> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <cd259038c7dcf5a8:-26ac3ba0:13ceb6f767d:-8000-0000000000000162> <1361163297488> <BEA-149506> <Established JMX Connectivity with adp_ms01 at the JMX Service URL of service: jmx:admin://appserver701.mycompany.internal:9102 /jndi/weblogic.management.mbeanservers.runtime.>
    Admin Server :
    [oracle@adminserver701 bin]$ netstat -an | grep 9101
    tcp 0 0 10.254.252.808:9101 0.0.0.0:* LISTEN
    tcp 0 0 192.168.100.238:9101 0.0.0.0:* LISTEN
    tcp 0 0 192.168.100.238:9101 192.168.100.218:59038 ESTABLISHED
    I am wondering if the JMX connectivity is using the server listen address (adminserver701.mycompany.internal) which will by default resolve to 192.168.100.238. Is there a way to force JMX to use 10.254.252.808?

    Hi
    For first question the answer is no. With the administration port, you enable the SSL between the admin server and Node manager-managed Servers. You can still use the web console.
    For teh second question, you can use ANT or can use the WLS Scripting ..you can get more details in dev2dev.bea.com
    Jin

  • Load-balancing Algorithm for NX-OS Port Channels

    Hi, all
    I do not understand description of port-channel load-balance ethernet command.
    switch(config)# port-channel load-balance ethernet ?
      destination-ip         Destination IP address
      destination-mac        Destination MAC address
      destination-port       Destination TCP/UDP port
      source-dest-ip         Source & Destination IP address (includes l2)
      source-dest-ip-only    Source & Destination IP addresses only
      source-dest-mac        Source & Destination MAC address
      source-dest-port       Source & Destination TCP/UDP port (includes l2 and l3)
      source-dest-port-only  Source & Destination TCP/UDP port only
      source-ip              Source IP address
      source-mac             Source MAC address
      source-port            Source TCP/UDP port
    Please tell me what the following descriptions mean.
      Source & Destination IP address (includes l2)
      Source & Destination TCP/UDP port (includes l2 and l3)
    What are the meaning of "includes l2" and "includes l2 and l3" ?
    Thank you for your cooperation in advance.

    Hi Satoru,
    On the Nexus 5000/6000 platforms, all FEXs will inherit the global hashing algorithm from the parent device.
    On the Nexus 7000 platform, hashing algorithms can be assigned on a per FEX basis (all load balancing changes must be made from the Admin VDC):
    N7K-A(config)# port-channel load-balance src-dst ip-l4port fex 134
    Any FEX without a hashing algorithm configured with inherit the global hash. Making changes to the modular/global hash will not alter FEX specific hashing algorithms.
    To verify the configuration applied you can use this command:
    N5K_A# show port-channel load-balance
    On the Nexus 7000, the per FEX algorithm can be checked by appending the ‘fex <#>’ to the end of the command in the Admin VDC or the FEX’s respective VDC:
    N7K-A(config)# show port-channel load-balance fex 134
    Regards,
    Richard

Maybe you are looking for